Problems with 3.5.8 fc8 x86_64

[Eli Wapniarski]

Hey Everyone.

First an aside. Anyone have any idea why my rhgb screen doesn't show when I
boot my computer. I do have rhgb installed

To the issue at hand.

Hi Rex

I've been working with 3.5.8 on fc8 x86_64 and have run into serveral problems
that I have been unable to resolve.

FIRST
---------
When I log off a session I get the following

startkde: Shutting down...
klauncher: Exiting on signal 1
process 7466: arguments to dbus_message_new_method_call() were incorrect,
assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c
line 1074.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Last DCOP call before KDED crash was from application 'DCOPServer'
to object '', function 'applicationRemoved(QCString)'.
KCrash: Application 'kded' crashing...
Warning: connect() failed: : No such file or directory
KCrash cannot reach kdeinit, launching directly.
startkde: Running shutdown scripts...
startkde: Done.

waiting for X server to shut down


SECOND
-------------
With alsa-plugins-oss and / or alsa-plugins-pulseaudio

The kdesound server will only run with Open Sound System which of course is an
emulation.

Or the sound system crashes after loading because the CPU is overloaded.


Eli
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[José Matos]

Post by Eli Wapniarski
Hey Everyone.
First an aside. Anyone have any idea why my rhgb screen doesn't show when I
boot my computer. I do have rhgb installed

Is the rhgb argument given in grub (/etc/grub.conf)? If you have removed it
once it will not be there anymore.

title Fedora (2.6.23.8-62.fc8)
root (hd0,0)
kernel /vmlinuz-2.6.23.8-62.fc8 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.23.8-62.fc8.img

This is what I have because I decided that I don't care about graphical boot.
To restore the default behaviour I have to add rhgb in the end of the kernel
line. Something like

title Fedora (2.6.23.8-62.fc8)
root (hd0,0)
kernel /vmlinuz-2.6.23.8-62.fc8 ro root=/dev/VolGroup00/LogVol00 rhgb
initrd /initrd-2.6.23.8-62.fc8.img

I may want to add there "quiet" as well.

I hope this helps.

[Eli Wapniarski]

Post by José Matos

Post by Eli Wapniarski
Hey Everyone.
First an aside. Anyone have any idea why my rhgb screen doesn't show when
I boot my computer. I do have rhgb installed

Is the rhgb argument given in grub (/etc/grub.conf)? If you have removed it
once it will not be there anymore.

The rhgb command is in place.

Eli
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[Eli Wapniarski]

Post by Eli Wapniarski

Post by José Matos

Post by Eli Wapniarski
Hey Everyone.
First an aside. Anyone have any idea why my rhgb screen doesn't show
when I boot my computer. I do have rhgb installed

Is the rhgb argument given in grub (/etc/grub.conf)? If you have removed
it once it will not be there anymore.

The rhgb command is in place.
Eli

OK... I found the reason. Its a bug

https://bugzilla.redhat.com/show_bug.cgi?id=378251

What is it with Redhat / Fedora and the number 8 anyway. First the horrible
release Redhat 8 and now Fedora 8. Which seems to be plenty buggy?

hmmph.

Eli
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[José Matos]

Post by Eli Wapniarski
What is it with Redhat / Fedora and the number 8 anyway. First the horrible
release Redhat 8 and now Fedora 8. Which seems to be plenty buggy?
hmmph.

I disagree on both accounts. Oh well... :-)

Post by Eli Wapniarski
Eli

[Eli Wapniarski]

Post by José Matos

Post by Eli Wapniarski
What is it with Redhat / Fedora and the number 8 anyway. First the
horrible release Redhat 8 and now Fedora 8. Which seems to be plenty
buggy?
hmmph.

I disagree on both accounts. Oh well... :-)

Post by Eli Wapniarski
Eli

--

Don't tell me that you liked the fact that in Redhat 8 kmenu didn't work and
you were stuck with the organization of gnome's menu structure which could
only be edited through text files. It was absolutely wonderful when
kde-redhat came around.

Now. rhgb doesn't work properly. kded and dbus don't talk to each other
properly, alsa-plugins-oss and alsa-plugins-pulseaudio and arts don't talk to
each other properly. Java (albeit a know java problem -- but worked in Fedora
upto 7 without a workaround -- not a kde problem suddenly doesn't work
properly on a dual screen system. See
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6532373). These are the
problems that I've found and I found them right from the get go. I don't know
about the ones that I haven't found. Sorry this time, and I'm a big Fedora
fan, this release was sloppy. And I still recommend Fedora to all my friends.

I really hope that this isn't a repeat of "since this the latest it must be
the greatest."

"We wil server no wine before its time" - Ernst and Julio Gallo Commericial

Eli
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[Rex Dieter]

Post by Eli Wapniarski
Don't tell me that you liked the fact that in Redhat 8 kmenu didn't work
and you were stuck with the organization of gnome's menu structure which
could only be edited through text files.

Yeah, suckage for sure. A good example of a feature/idea that was good in
principle, but lacked execution and comitment/resources to ensure that it
worked properly.

Post by Eli Wapniarski
Now. rhgb doesn't work properly.

rhgb works just fine for a vast majority of users, just not those using
nvidia's binary driver, atm.

Post by Eli Wapniarski
kded and dbus don't talk to each other properly,

Looking into it... but currently, no concrete problems have yet been
identified as a consequence of the shutdown warnings/errors you saw, right?

Post by Eli Wapniarski
alsa-plugins-oss and alsa-plugins-pulseaudio and arts don't talk
to each other properly.

Can't speak for oss, but pulseaudio is certainly a new technology, so does
have quite a few rough edges. Fortunately, kde/pulseaudio support in f8 is
optional, and can easily be disabled.

Post by Eli Wapniarski

Post by Eli Wapniarski
Java (albeit a know java problem -- but worked in

Fedora upto 7 without a workaround -- not a kde problem suddenly doesn't
work properly on a dual screen system. See
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6532373).

And what do you suggest in cases like this? Consider that oss/fedora
developers have no real way of properly debugging this.

-- Rex


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[Michael Blandford]

Post by Rex Dieter

Post by Eli Wapniarski
Don't tell me that you liked the fact that in Redhat 8 kmenu didn't work
and you were stuck with the organization of gnome's menu structure which
could only be edited through text files.

Yeah, suckage for sure. A good example of a feature/idea that was good in
principle, but lacked execution and comitment/resources to ensure that it
worked properly.

Post by Eli Wapniarski
Now. rhgb doesn't work properly.

rhgb works just fine for a vast majority of users, just not those using
nvidia's binary driver, atm.

rhgb is working fine for me with F8 on x86_64 with NVidia drivers. I am
using version 100.14.11 patched for 2.6.23 from atrpms.

Michael


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[Rex Dieter]

Post by Eli Wapniarski
OK... I found the reason. Its a bug
https://bugzilla.redhat.com/show_bug.cgi?id=378251
What is it with Redhat / Fedora and the number 8 anyway. First the horrible
release Redhat 8 and now Fedora 8. Which seems to be plenty buggy?

closed-source sucks, eh? Why are you placing blame solely on fedora
here, and not nvidia?

-- Rex


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[Rex Dieter]

Post by Rex Dieter

Post by Eli Wapniarski
OK... I found the reason. Its a bug
https://bugzilla.redhat.com/show_bug.cgi?id=378251
What is it with Redhat / Fedora and the number 8 anyway. First the
horrible release Redhat 8 and now Fedora 8. Which seems to be plenty
buggy?

closed-source sucks, eh? Why are you placing blame solely on fedora
here, and not nvidia?

Sorry, that came off as way too crabby. (fwiw, crabbiness induced by
reading way too many flames/complaints about nvidia drivers and/or sun java
not working on f8, and somehow that's 100% fedora's fault/blame).

Let's try again...

Before complaining to/about fedora in cases like this, consider the dynamics
of oss vs not, and that at least some (I'd argue most/all, but I'll settle
for some) blame rests with the vendor providing those incompatible,
closed-sourced, propietary solutions. And, are you complaining as
vociferously to *them* about your troubles?

-- Rex


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[Eli Wapniarski]

Post by Rex Dieter

Post by Eli Wapniarski
OK... I found the reason. Its a bug
https://bugzilla.redhat.com/show_bug.cgi?id=378251
What is it with Redhat / Fedora and the number 8 anyway. First the
horrible release Redhat 8 and now Fedora 8. Which seems to be plenty
buggy?

closed-source sucks, eh? Why are you placing blame solely on fedora
here, and not nvidia?

(I didn't take it as crabby). I agree about the closed source sucks. Be that as it may. I've looked in the forums and there is no mention of these or any other similar problem at NVidia. And besides that I had got xorg, kernel, rhgb, java, in Fedora 7 everything worked. Now in Fedora 8 two things related to the graphics system don't. Albeit one of them is not NVidia or an xorg problem per se but a java problem with a workaround available (phew), cause it involved my backups.

Then tired, coming home from work dealing with Management, Users, Windows workstations and servers and then trying to find out where the source of my personal desktop headaches are coming from as I expect a smooth transition for my Fedora servers, that I'm responsible for, as I have since the beginning of the Fedora cycle.

Knee jerk emotional reaction as to what changed from working to none working. Well guess what. It was Fedora 7 to Fedora 8. Forgive me if I sound crabby. :)

Eli

[Eli Wapniarski]

Post by Rex Dieter

Post by Eli Wapniarski
OK... I found the reason. Its a bug
https://bugzilla.redhat.com/show_bug.cgi?id=378251
What is it with Redhat / Fedora and the number 8 anyway. First the
horrible release Redhat 8 and now Fedora 8. Which seems to be plenty
buggy?

closed-source sucks, eh? Why are you placing blame solely on fedora
here, and not nvidia?

Oh and by the rhgb behavior also showed up after I've upgraded 7 to 8 on my vm
installation of fedora at work. So, I have a hard time believing that its a
NVidia problem per se.

Eli
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[Rex Dieter]

Post by Eli Wapniarski

Post by Rex Dieter

Post by Eli Wapniarski
OK... I found the reason. Its a bug
https://bugzilla.redhat.com/show_bug.cgi?id=378251
What is it with Redhat / Fedora and the number 8 anyway. First the
horrible release Redhat 8 and now Fedora 8. Which seems to be plenty
buggy?

closed-source sucks, eh? Why are you placing blame solely on fedora
here, and not nvidia?

Oh and by the rhgb behavior also showed up after I've upgraded 7 to 8 on my vm
installation of fedora at work. So, I have a hard time believing that its a
NVidia problem per se.

I've seen rhgb fail a couple of times too on minimal and/or livecd
setups. Without looking into it much myself, it would appear that it is
missing some Requires (a 'yum groupinstall base-x' fixed it both times
for me).

-- Rex

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[Eli Wapniarski]

Post by Rex Dieter
I've seen rhgb fail a couple of times too on minimal and/or livecd
setups. Without looking into it much myself, it would appear that it is
missing some Requires (a 'yum groupinstall base-x' fixed it both times
for me).

I tried that. It didn't work.

:(

But.... OK... I got it to work and resolved my Java issue at the same time.

:)

I backed up xorg.conf deleted the original file and run setup. and then X
configuation.

Wouldn't you know it garbage appeared on the monitor connected to my analog
port. So I removed the one connected to the DVI port rebooted and ran setup
again.

And it worked. It detected my nv card and was able to display. I rebooted the
computer and whadya know, rhgb worked. Why I needed to unplug one of monitors
to configure X is well counter intuitive. Especially since I've been so
accustomed to things working right out of the box. But I digresss.

So I reinstalled the nvidia drivers rebooted and rhgb worked. So. I
reconfigured twinview rebooted and rhgb worked.

Compared the newly created xorg.conf with my backup. The file section was
empty and the module section only was loading glx. I copied over the original
module section, rebooted and rhgb worked.

Copied over the original file section which contains

Section "Files"
RgbPath "/usr/lib64/X11/rgb"
FontPath "unix/:7100"
EndSection

rebooted and rhgb did not work.

So I commented out the FontPath line so the file seciton looked like

Section "Files"
RgbPath "/usr/lib64/X11/rgb"
# FontPath "unix/:7100"
EndSection

rhgb worked and my java app worked (without the work around).

Thanks all for indulging my little rant.

This is one that makes me go hmmm.

Now, test my other two desktop installations before I start tackling server
issues like why ypbind won't bind at boot time. And the only way I can get it
too work is to run restart from rc.local or the command line. But that's not
a kde-redhat issue either. But still it makes me go hmmm.

Eli
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[Eli Wapniarski]

Post by Eli Wapniarski
Now, test my other two desktop installations before I start tackling server
issues like why ypbind won't bind at boot time. And the only way I can get
it too work is to run restart from rc.local or the command line. But that's
not a kde-redhat issue either. But still it makes me go hmmm.
Eli

The second desktop now works. The third one will have to wait till I get to
work.

But that looks like that is that.

Eli
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[Eli Wapniarski]

Post by Eli Wapniarski

Post by Eli Wapniarski
Now, test my other two desktop installations before I start tackling
server issues like why ypbind won't bind at boot time. And the only way I
can get it too work is to run restart from rc.local or the command line.
But that's not a kde-redhat issue either. But still it makes me go hmmm.
Eli

The second desktop now works. The third one will have to wait till I get to
work.
But that looks like that is that.
Eli

Third Desktop is now working after removing the fontpath line out of
xorg.conf.

Anyone have an explanation?

Eli
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[Rex Dieter]

Post by Eli Wapniarski
Hey Everyone.
First an aside. Anyone have any idea why my rhgb screen doesn't show when I
boot my computer. I do have rhgb installed
To the issue at hand.
Hi Rex
I've been working with 3.5.8 on fc8 x86_64 and have run into serveral problems
that I have been unable to resolve.
FIRST
---------
When I log off a session I get the following
startkde: Shutting down...
klauncher: Exiting on signal 1
process 7466: arguments to dbus_message_new_method_call() were incorrect,
assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c
line 1074.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Last DCOP call before KDED crash was from application 'DCOPServer'
to object '', function 'applicationRemoved(QCString)'.
KCrash: Application 'kded' crashing...
Warning: connect() failed: : No such file or directory
KCrash cannot reach kdeinit, launching directly.
startkde: Running shutdown scripts...
startkde: Done.
waiting for X server to shut down

Never seen this. I'll have to see if I can reproduce.

Post by Eli Wapniarski
SECOND
-------------
With alsa-plugins-oss and / or alsa-plugins-pulseaudio
The kdesound server will only run with Open Sound System which of course is an
emulation.
Or the sound system crashes after loading because the CPU is overloaded.

You can disable kde/pulseaudio integration by:
yum remove kde-settings-pulseaudio alsa-plugins-pulseaudio

-- Rex


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[Eli Wapniarski]

Post by Rex Dieter
yum remove kde-settings-pulseaudio alsa-plugins-pulseaudio

I've done that.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/