multiple problems with gnome

[Nick Hudson]

Hmm thats intresting... I will test it out and see what happens.  Thanks
for the info.

Nick


On Fri, 2003-10-17 at 17:31, Carl R. Powers wrote:
> Except for the new gnome path problem in /etc/profile, this seems to be a
> continuation of the gnome login problems I've experienced since gdm-2.4.4.0
> but which for me, now seem to be fixed.   I've had to fall back to  
> gdm-2.4.1.5
> until now.  After fixing the path, I recompiled gnome-session-2.4.1, gnome-
> desktop-2.4.1.1, and gdm-2.4.4.3, all from a command login.  Now all play
> well together on 2 different machines.  Update of gnome-session and gnome-
> desktop seem to be the key.
> 
> Carl Powers
> 
> Yoav Avitzour wrote:
> 
> >It worked for me.
> >
> >Mike, after you change /etc/profile, make sure you kill gdm completely
> >(look at: ps -A | grep gdm), then run bonobo-slay and make sure there
> >are no more running bonobo processes before you restart gdm (again check
> >with something like: ps -A | grep bonobo)
> >
> >That's how it worked for me.
> >
> >Yoav
> >
> >On Fri, 2003-10-17 at 00:58, Mike Burney wrote:
> >  
> >
> >>Nick,
> >>
> >>Doesn't change anything for me.  I still get the same errors.
> >>
> >>Mike
> >>
> >>On Thu, 2003-10-16 at 22:14, Nick Hudson wrote:
> >>    
> >>
> >>>Yeah the problem seems to exist because gdm for some reaosn use the
> >>>/etc/profile to read your set PATH.  You need to add
> >>>/opt/lunar/gnome/2.4/bin to you PATH= .... in your /etc/profile file. 
> >>>It should read something of the sort:
> >>>
> >>># global bash profile. This file is processed for all interactive
> >>>shells                                                                            # this is the minimum and given by init to start scripts (so a good start)
> >>>PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin:/opt/lunar/gnome/2.4/bin
> >>>
> >>>Now this fixed it for me, please let me know if it doesnt for you.
> >>>
> >>>Nick
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>On Thu, 2003-10-16 at 10:55, Yoav Avitzour wrote:
> >>>      
> >>>
> >>>>Hi,
> >>>>
> >>>>Since the partial upgrade to 2.4.1 my desktop suffers from several
> >>>>problems. First, when logging in, I get a window with a message that
> >>>>gnome-settings-daemon could not be started. If I try regular login, it
> >>>>gets stuck at this point, and I need to kill the X server (see
> >>>>.xsession-errors file below). If I try failsafe login, I get the same
> >>>>message, but I can login. I can then run manually the
> >>>>control-settings-daemon without a problem, but I cannot load ANY applet
> >>>>to the panel. I just get a series of messages like:
> >>>>
> >>>>The panel encountered a problem while loading "OAFIID:GNOME_GDictApplet"
> >>>>Details: Child process did not give an error message, unknown failure
> >>>>occurred
> >>>>
> >>>>
> >>>>Any ideas ?
> >>>>
> >>>>Thanks,
> >>>>
> >>>>Yoav
> >>>>
> >>>>
> >>>>Here is my .xsession-errors:
> >>>>
> >>>>/etc/X11/gdm/PreSession/Default: Registering your session with wtmp and
> >>>>utmp
> >>>>/etc/X11/gdm/PreSession/Default: running: /usr/bin/X11/sessreg -a -w
> >>>>/var/log/wtmp -u /var/run/utmp -x "/var/gdm/:0.Xservers" -h ""
> >>>>/etc/X11/gdm/Xsession: Beginning session setup...
> >>>>/etc/X11/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent --
> >>>>/opt/lunar/gnome/2.4/bin/gnome-session
> >>>>SESSION_MANAGER=local/gutman:/tmp/.ICE-unix/19824
> >>>>Gnome-Message: gnome_execute_async_with_env_fds: returning -1
> >>>>Gnome-Message: gnome_execute_async_with_env_fds: returning -1
> >>>>Gnome-Message: gnome_execute_async_with_env_fds: returning -1
> >>>>Gnome-Message: gnome_execute_async_with_env_fds: returning -1
> >>>>Gnome-Message: gnome_execute_async_with_env_fds: returning -1
> >>>>Gnome-Message: gnome_execute_async_with_env_fds: returning -1
> >>>>Gnome-Message: gnome_execute_async_with_env_fds: returning -1
> >>>>
> >>>>(evolution:19867): GLib-GObject-WARNING **: gsignal.c:2010: instance
> >>>>`0x837fa18' has no handler with id `2869'
> >>>>The application 'gnome-session' lost its connection to the display :0.0;
> >>>>most likely the X server was shut down or you killed/destroyed
> >>>>the application.
> >>>>
> >>>>
> >>>>_______________________________________________
> >>>>lunar mailing list
> >>>>lunar at lunar-linux.org
> >>>>http://dbguin.lunar-linux.org/mailman/listinfo/lunar
> >>>>        
> >>>>
> >>>______________________________________________________________________
> >>>
> >>>_______________________________________________
> >>>lunar mailing list
> >>>lunar at lunar-linux.org
> >>>http://dbguin.lunar-linux.org/mailman/listinfo/lunar
> >>>      
> >>>
> >>_______________________________________________
> >>lunar mailing list
> >>lunar at lunar-linux.org
> >>http://dbguin.lunar-linux.org/mailman/listinfo/lunar
> >>    
> >>
> >
> >_______________________________________________
> >lunar mailing list
> >lunar at lunar-linux.org
> >http://dbguin.lunar-linux.org/mailman/listinfo/lunar
> >
> >  
> >
> 
> 
> _______________________________________________
> lunar mailing list
> lunar at lunar-linux.org
> http://dbguin.lunar-linux.org/mailman/listinfo/lunar
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lunar-linux.org/pipermail/lunar/attachments/20031017/9deac670/attachment.bin