LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Desktop
User Name
Password
Linux - Desktop This forum is for the discussion of all Linux Software used in a desktop context.

Notices


Reply
  Search this Thread
Old 11-06-2008, 09:31 PM   #1
scott.anderson
Member
 
Registered: Mar 2005
Location: Natick, MA
Distribution: Redhat EL 5.2, Fedora 8
Posts: 30

Rep: Reputation: 15
very slow desktop login for some users in fedora 8


I have several desktop computers running Fedora 8. I'm able to login from the console in a reasonable amount of time (about 30 seconds before the desktop icons appear and the Fedora menu is active). However, I have one user (and there may be others) for whom login on certain Fedora 8 machines is *very* slow. I timed it at 90 seconds for the desktop icons to appear and another 60 seconds before the Fedora menu was active. SSHing as this user is quick, so it's nothing to do with authentication and such. It's the very same hardware and software (the very same machine) that is quick for me and many other accounts, so it appears to be a problem just with his account.

I'm at something of a loss as to how to even approach debugging this. I did notice some errors involving DBUS in his ~/.xsession-errors file, but I don't know if they are relevant. I've appended the file here in case anyone sees something there that is helpful.

I'd be grateful if anyone could help me make some progress on this error.

Thanks,

Scott

SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/16851,unix/unix:/tmp/.ICE-unix/16851

** (gnome-session:16851): WARNING **: Failed to start sound.

Window manager warning: Failed to read saved session file /home/fturbak/.metacity/sessions/default1.ms: Failed to open file '/home/fturbak/.metacity/sessions/default1.ms': No such file or directory
Connection failure: Connection refused

** (gnome-panel:16998): WARNING **: Unkown action type 'suspend' from /apps/panel/objects/object_0/action_type
Traceback (most recent call last):
File "/usr/share/sampler/first-time/first-time", line 7, in <module>
Main.main()
File "/usr/share/sampler/first-time/Main.py", line 15, in main
File "/usr/share/sampler/first-time/Service.py", line 22, in unique
File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 218, in __new__
Traceback (most recent call last):
File "/usr/bin/nautilus", line 12, in <module>
'build-distribution': 'fedora-8-i386'}
File "/usr/share/sampler/wrapper/Main2.py", line 36, in main
File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 218, in __new__
libnotify-Message: Unable to get session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
system-config-printer-applet: unable to initialize pynotify
could not attach to desktop process
libnotify-Message: Unable to get session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
libnotify-Message: Unable to get session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
mainloop=mainloop)
mainloop=mainloop)
File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 107, in __new__
File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 107, in __new__
bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 121, in __new__
File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 121, in __new__
bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Traceback (most recent call last):
File "/usr/share/sampler/first-time/first-time", line 7, in <module>
Main.main()
File "/usr/share/sampler/first-time/Main.py", line 15, in main
File "/usr/share/sampler/first-time/Service.py", line 22, in unique
File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 218, in __new__
mainloop=mainloop)
File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 107, in __new__
bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 121, in __new__
bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
I/O error : Permission denied
libnotify-Message: Unable to get session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error: unable to initialize pynotify
Traceback (most recent call last):
File "/usr/bin/gnome-panel", line 12, in <module>
'build-distribution': 'fedora-8-i386'}
File "/usr/share/sampler/wrapper/Main2.py", line 37, in main
File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 240, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 236, in __init__
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 174, in activate_name_owner
return self.get_name_owner(bus_name)
File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 351, in get_name_owner
's', (bus_name,), utf8_strings=True)
File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 603, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nm-applet:17018): WARNING **: <WARN> applet_dbus_manager_start_service(): Could not acquire the NetworkManagerUserSettings service.
Message: 'Connection ":1.227" is not allowed to own the service "org.freedesktop.NetworkManagerUserSettings" due to security policies in the configuration file'


(nm-applet:17018): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Unable to connect to yum-updatesd. Please ensure that the yum-updatesd
package is installed and that the service is running.
ALSA lib control.c:909snd_ctl_open_noupdate) Invalid CTL front:0
ALSA lib control.c:909snd_ctl_open_noupdate) Invalid CTL front:0
system-config-printer-applet: failed to start NewPrinterNotification service
 
Old 11-15-2008, 08:20 PM   #2
jiobo
Member
 
Registered: Nov 2008
Posts: 180

Rep: Reputation: 36
Had a problem like that with an older Fedora...fixed it by removing the user. Guess that might not help you. You can try to remove the user, reboot, then add the user again. Backup any user files first, though.

Have you checked for any errors when that user logs in? Are all users with the same permissions and groups?
 
Old 11-15-2008, 10:22 PM   #3
mrclisdue
Senior Member
 
Registered: Dec 2005
Distribution: Slackware
Posts: 1,134

Rep: Reputation: 277Reputation: 277Reputation: 277
I had that problem a few times over the course of 3 or 4 years when I used fedora. It was Gnome's fault. I no longer use Fedora or Gnome, but iirc, the user has to rename the .gnome2 file (or directory?), ie .gnome2bak, and start fresh, keeping .gnome2bak as reference....

I'm *pretty* sure it's .gnome2, but since I don't have gnome to verify....

hth,
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Desktop effects on Fedora slow down the video players. deepumnit Linux - Software 4 01-11-2008 11:24 PM
Slow Linux Growth among Desktop users ? rvijay Linux - General 15 06-28-2006 04:31 AM
Struggling to setup a Debian/etch desktop: LDAP users and LOCAL users jferrando Linux - Networking 1 05-05-2006 03:44 PM
System uncleanly shut down, ran e2fsck, very slow start & slow desktop brakthepoet Linux - Newbie 1 07-02-2004 01:55 PM
Root desktop is fast, Users are slow BajaNick Linux - General 5 02-10-2004 08:22 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Desktop

All times are GMT -5. The time now is 12:57 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration