KDSKBENT, eggcups and gnome volume manager errors!

[dishawjp]

I just ran a "diff" and "cmp" on my old "dumpkeys" output and the new one, so it looks like the command:
dumpkeys | loadkeys -v --unicode
run as root didn't change anything <one REALLY HUGE sigh of relief>

[Void Main]

So I am curious if the error goes away if you temporarily comment that line out in your /bin/unicode_start script? Comment out the "dumpkeys | loadkeys --unicode" just to see if that is indeed what is giving the error message.

[dishawjp]

So I am curious if the error goes away if you temporarily comment that line out in your /bin/unicode_start script? Comment out the "dumpkeys | loadkeys --unicode" just to see if that is indeed what is giving the error message

That did indeed eliminate the error message! Of course, I doubt that it's good to leave that line commented out for too long... it has to be there for a reason.

Next step? Or just uncomment the line and wait for some sort of a fix to be put out? It's not nearly as troublesome as the other problems were, the eggcups and gnome volume manager errors adn the constant loss of 3D on booting.

What do you recommend?

[Void Main]

All it is is keyboard mapping for UTF8 and if you don't notice any keys not working properly there is no harm in leaving it commented out, at least until we figure out why it's doing it. It's totally up to you though. I have seen in that bugzilla thread where someone commented it out and had no ill effects. I would be willing to be the guys posting here would know what to do:

http://mail.nl.linux.org/linux-utf8/200 ... 00216.html

Those messages are pretty old...

[dishawjp]

Voidmain,

Thanks for everything here. I'm going to remove the comment on that line for now. It doesn't to be doing any harm by being there and I do hope that this will be picked up by others and corrected in the near future. If there is a patch and I have the line commented out, there's a chance that the patch won't "take." At least that's what I'm telling myself based on no knowledge whatsoever.

Anyway, thanks again and if there are any new developments on this, I'll pass them along to you and the list.

Jim

[dishawjp]

To anyone following this thread, I did find this:

http://www.redhat.com/archives/fedora-l ... 05723.html

in the Fedora List today. It explains a bit about the Gnome Volume Manager and eggcups issues I had. Evidently the reason that they went away is that prelink must have run. I thought that I had "fixed" it by messing with my nVidia drivers and the xorg configurations. Looks like I was wrong... again.

But the important thing is that the fix is simple and developers are aware of the issue.

Jim Dishaw

[Void Main]

Ahhh, I have had one or two other issues that were fixed by doing a prelink. I can't for the life of me remember what they are now though. That is a very good tip to keep in mind. I want to say I was getting a segfault from apt-get after upgrading it and doing a prelink fixed it.

[dishawjp]

Until about an hour or so ago, I thought that prelink was there *only* to speed the execution of programs. I found another thread on the Fedora List today that discusses this as well. I would never have guessed that this could be a fix for problems discovered after updating.

"Live and learn" as they say.

I think I've done about 2 hours of work today supplemented by about 4 hours of reading up on FC3 issues. I sure hope that nobody's monitoring what I'm doing with this computer

Jim

[Void Main]

I think I've done about 2 hours of work today supplemented by about 4 hours of reading up on FC3 issues. I sure hope that nobody's monitoring what I'm doing with this computer :-)

If you worked at the company I work at then it would be "me" that is doing the monitoring. You would be safe. :)