On Sat, May 10, 2008 at 04:13:31PM +0200, Sven Arvidsson wrote:
> > urxvt: perl extension 'mark-urls' not found in perl library search path
> > urxvt: perl extension 'mark-urls' not found in perl library search path
> > 
> > A bit strange is the host name lookup failure on localhost, because 
> > /etc/hosts
> > contains valid entries for localhost.
> > 
> > [EMAIL PROTECTED] ~ % grep localhost /etc/hosts
> > 127.0.0.1   localhost
> > ::1     ip6-localhost ip6-loopback
> > 
> > But as /etc/hosts hasn't been changed (for example by
> > network-manager-gnome) I guess that is not related.
> 
> Hi,
> 
> That's very interesting, there have been several bug reports about gdm
> crashing on the first login, but so far no one have made the connection
> to gnome-session.
> 
> I wonder if others who have reported this also find this limited to
> gnome-session and if there's a common configuration?

Before logging in, this is what my .xsession-errors looks like:
/etc/gdm/Xsession: Beginning session setup...
SESSION_MANAGER=local/pc2:/tmp/.ICE-unix/2896
** Message: another SSH agent is running at:
/tmp/ssh-HirHMz2896/agent.2896

** (gnome-settings-daemon:2968): WARNING **: Error in setting vertical scroll

** (gnome-settings-daemon:2968): WARNING **: Error in setting horizontal scroll
xrdb:  "*Label.background" on line 220 overrides entry on line 150
xrdb:  "*Text.background" on line 226 overrides entry on line 191
xrdb:  "*Label.foreground" on line 232 overrides entry on line 151
xrdb:  "*Text.foreground" on line 238 overrides entry on line 192
Window manager warning: Failed to read saved session file 
/home/kurt/.metacity/sessions/default0.ms: Failed to open file 
'/home/kurt/.metacity/sessions/default0.ms': No such file or directory
seahorse nautilus module initialized
Initializing gnome-mount extension

(gnome-panel:2982): Gtk-WARNING **: gtk_widget_size_allocate(): attempt
to allocate widget with width -9 and height 24
** Message: Got disconnected from the session message bus; retrying to 
reconnect every 10 seconds


But that's still an old file, from the last succesful login.

The login attempt that restarted gdm didn't log anything to that file.


Kurt




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to