This is a repost.  I sent it last night and it appears it got lost
along the way.  My appologies if you get more than one copy.

John

__________________________



And yet more!  (This is endlessly entertaining ;)

The startup wav will launch upon reboot, if I log in as root.  But,
never again in that boot session.

I've tried killing esd, clearing out lock files, temp files, etc.

Still baffled

On Mon, Mar 06, 2000 at 11:31:32PM -0500, John P. Verel wrote:
> Here's some more on this problem.  
> 
> -  The startup wav fails only in Gnome, but not in KDE.
> -  The wav file works fine in the Gnome control center setup and test.
> -  All other sound work fine in Gnome.
> -  I get the following message in my .xsession-errors log:
> 
> SESSION_MANAGER=local/CV150607-A:/tmp/.ICE-unix/1351,tcp/CV150607-A:1103
> esd: Esound sound daemon already running or stale UNIX socket
> /tmp/.esd/socket
> This socket already exists indicating esd is already running.
> Exiting...
> xscreensaver-command: no screensaver is running on display :0.0
> xscreensaver disabling server builtin screensaver.
> xscreensaver: you can re-enable it with "xset s on".
> subshell.c: couldn't get terminal settings: Inappropriate ioctl for
> device
> 
> GnomeUI-WARNING **: Could not open help topics file NULL
> 
> Gtk-CRITICAL **: file gtkcontainer.c: line 730 (gtk_container_remove):
> assertion `widget->parent == GTK_WIDGET (container)' failed.
> 
> Gtk-WARNING **: invalid cast from `(unknown)' to `GtkWidget'
> 
> Gtk-CRITICAL **: file gtkwidget.c: line 3500 (gtk_widget_get_style):
> assertion `GTK_IS_WIDGET (widget)' failed.
> 
> Gtk-CRITICAL **: file gtkctree.c: line 5130
> (gtk_ctree_node_set_foreground): assertion `GTK_IS_CTREE (ctree)'
> failed.
> 
> 
> Is the reference to the Esound daemon provide a clue?
> 
> Thanks.
> 
> John
> 
> On Sun, Mar 05, 2000 at 11:53:00PM -0500, John P. Verel wrote:
> > For no reason I can discern, Gnome has stopped playing any startup wav
> > file I may select.  Worked fine yesterday...not working today.  I'm
> > baffled!  Any thoughts?
> > 
> > Jo
> > 
> > 
> > -- 
> > To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> > as the Subject.


Reply via email to