Why would xfce4-panel suddenly not be started at boot/login?

[Lampersperger Andreas]

Hello Rich,

On Wed, 20 Jan 2010, Chris G wrote:

>> Starting xfce4-panel manually from the command line gets things working OK
>> but why isn't it getting started automatically in the normal way?  What
>> starts it?


>  We see this infrequently. Using alt-f2 and entering 'xfce4-panel &' not
>only invokes the panel but has it restored to the session manager for the
>next time. If you are running it in the background when you restart it the
>session manager should add it to the tools to be restored the next time.

Is there a entry to this error in bugzilla? 
I can reproduce this error by typing

 init 3
 rm -rf /usr/var/cache/fontconfig 
 rm -rf /home/user/.fontconfig
 init 5

on my old 400Mhz Celeron hardware. Following error
messages occur when the panel is not starting:

xfdesktop[5117]: starting up
xfce4-settings-helper is already running

(xfce4-session:5097): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GObject'

(xfce4-session:5097): GLib-GObject-CRITICAL **: g_object_steal_data: assertion `G_IS_OBJECT (object)' failed

(xfce4-menu-plugin:5137): Gdk-WARNING **: GdkWindow 0x1200003 unexpectedly destroyed

(orageclock:5138): Gdk-WARNING **: GdkWindow 0x1800003 unexpectedly destroyed
The program 'xfce4-menu-plugin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 161 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'orageclock' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 161 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

** (xfwm4:5111): WARNING **: Cannot get window attributes for window (0xa00019)

Andreas

-----Original Message-----
From: xfce-bounces at xfce.org [mailto:xfce-bounces at xfce.org] On Behalf Of Rich Shepard
Sent: Mittwoch, 20. Januar 2010 15:44
To: XFCE general discussion list
Subject: Re: Why would xfce4-panel suddenly not be started at boot/login?


Rich
_______________________________________________
Xfce mailing list
Xfce at xfce.org
http://foo-projects.org/mailman/listinfo/xfce
http://www.xfce.org

-------------- next part --------------
-------------------------------------------------------------------------------------------------------
Registergericht: Traunstein / Registry Court: HRB 275 ? Sitz / Head Office: Traunreut
Aufsichtsratsvorsitzender / Chairman of Supervisory Board: Rainer Burkhard
Gesch?ftsf?hrung / Management Board: Thomas Sesselmann (Vorsitzender / Chairman),
Michael Grimm, Matthias Fauser

E-Mail Haftungsausschluss / E-Mail Disclaimer: http://www.heidenhain.de/disclaimer