Jump to content


Photo

Eggcups causing Gnome to die.


  • Please log in to reply
13 replies to this topic

#1 Cardinal

Cardinal

    member

  • Members
  • 193 posts

Posted 23 November 2004 - 04:42 PM

Hi gents. After using Kde for a while I decided to jump back in to Gnome only to be greeted by these two errors;




Clicking restart or close results in an endless cycle of error prompts, they don't go away. I have not done any serious system editing, the last thing I remember doing in gnome was running yum.

Any ideas guys?

#2 egorgry

egorgry

    enthusiast

  • Members
  • 315 posts

Posted 23 November 2004 - 06:58 PM

switch to a console using ctrl alt f1 login in and kill the processes manually. ps -ef | grep -i egg to find the eggcups proccess. Then just kill the pid. DO the same form the other process and restart X (you will need to be root) with pkill X or pkill gdm.

#3 SoulNothing

SoulNothing

    enthusiast

  • Members
  • 309 posts

Posted 23 November 2004 - 11:21 PM

all right this happened to me as well i tried all the stuff that egorgry said and nothing happened i had just updated gnome and thought that was what it was so i uninstalled gnome and reinstalled it nothing
anyhow keep us posted as to what happens because this has happened on four of my gnome fedora core 3 installs

#4 campem

campem

    stranger

  • Members
  • 2 posts

Posted 26 November 2004 - 07:02 PM

I'm having the same problem. Fedora Core 3 freshly installed & updated and nothing fancy going on as I'm a newbie. The errors don't go in a loop for me, after about 20 close clicks I get to the desktop but it's not fully operationnal, ie file browser doesn't work. I'm able to launch a Terminal Window though.

#5 difen

difen

    stranger

  • Members
  • 1 posts

Posted 26 November 2004 - 10:15 PM

I had the same problem... and found a possible fixed on bugzilla. See http://bugzilla-test...g.cgi?id=151307 comment #13.

try as root>
prelink /usr/lib/libdbus*so*

worked for me, but xmms won't launch after it (I did try and install mp3 drivers for it)

PS. Please let us know if it works for you

#6 campem

campem

    stranger

  • Members
  • 2 posts

Posted 27 November 2004 - 01:19 AM

Works great! Xmms with MP3 works to!

Thank you very much!

#7 tjl_25

tjl_25

    stranger

  • Members
  • 4 posts

Posted 30 November 2004 - 03:45 AM

I tried the prelink command and it said that prelink is not a valid commnand. Any suggestions?

Thanks

#8 egorgry

egorgry

    enthusiast

  • Members
  • 315 posts

Posted 30 November 2004 - 05:46 AM

sounds like you need prelink installed.

http://rpm.pbone.net...3.i386.rpm.html

#9 tjl_25

tjl_25

    stranger

  • Members
  • 4 posts

Posted 30 November 2004 - 06:00 AM

I installed prelink but it still won't recognize it as a command.

#10 egorgry

egorgry

    enthusiast

  • Members
  • 315 posts

Posted 30 November 2004 - 06:10 AM

are you root? if not try it as the root user. If you are still having problems try the whereis command.
whereis prelink That will tell you if it's in path.

The output looks something like this. In this example I'm looking for the ls command.
Quote:
[11/29/04][greg@otis:~]$ whereis ls
ls: /bin/ls /usr/share/man/man1/ls.1.gz


I've never used or installed prelink or fedora so maybe someone else can jump in and school my Debian using butt. wink the stuff above should be universal and helpfull either way.

#11 tjl_25

tjl_25

    stranger

  • Members
  • 4 posts

Posted 30 November 2004 - 06:13 AM

This is what i get when i do "whereis prelink". I've been trying to do it under root, it won't work under root or a regular user.

prelink: /usr/sbin/prelink /etc/prelink.conf /etc/prelink.cache /usr/share/man/man8/prelink.8.gz


#12 egorgry

egorgry

    enthusiast

  • Members
  • 315 posts

Posted 30 November 2004 - 06:20 AM

I'd try executing the command using the full path to it. So...
/usr/sbin/prelink /usr/lib/libdbus*so*

#13 tjl_25

tjl_25

    stranger

  • Members
  • 4 posts

Posted 30 November 2004 - 06:30 AM

That worked. Thanks a lot.

#14 egorgry

egorgry

    enthusiast

  • Members
  • 315 posts

Posted 30 November 2004 - 06:50 AM

no problem. You should have /usr/sbin in your path for root though. if you feel like resolving this for other things that may need to execute out of /usr/sbin then edit your .profile for root. by adding the line :/usr/sbin the end of the PATH= statement in .profile.

You can see what is defined in your path by typing echo $PATH

I also thought of one more thing. how did you gain root access using su or su - su can carry over your users profile that may have caused your problem. It's a common problem with HPUX if you use su - you are get roots profile without question.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

IPB Skin By Virteq