xfce4-panel and compiz
Foxy
foxy at on-the-hill.me.uk
Sat Mar 18 18:17:59 CET 2006
Jasper Huijsmans wrote:
> Foxy schreef:
>
>> Jasper Huijsmans wrote:
>>
>>> Foxy schreef:
>>>
>>>
>>>> I decided to play with compiz and xorg-aiglx and it works nicely with
>>>> xfce. The only problem is xfce4-panel. It looks like it starts too early
>>>> because I can see it during splash screen, but then crashes so I have to
>>>> start it manually. I use a script to start compiz-aiglx which goes like
>>>> this:
>>>>
>>>>
>>>>
>>>>> #!/bin/bash
>>>>> /usr/bin/gnome-window-decorator-aiglx &
>>>>> LIBGL_ALWAYS_INDIRECT=TRUE /usr/bin/compiz-aiglx --replace decoration
>>>>> wobbly fade minimize cube rotate zoom scale move resize place switcher
>>>>> opaquefocus opacity &
>>>>>
>>>>>
>>>> Is it possible to fix xfce4-panel?
>>>>
>>>>
>>> With no other information, very unlikely...
>>>
>>> Are there any error messages?
>>>
>>> Jasper
>>>
>>> _______________________________________________
>>> Xfce mailing list
>>> Xfce at xfce.org
>>> http://foo-projects.org/mailman/listinfo/xfce
>>> http://www.xfce.org
>>>
>>>
>> no, no error messages. I log in into my account, see the running mouse
>> (Balou splash screen), while the messages about programmes launched are
>> running at the bottom of the screen, the upper panel appears with the
>> plugins on it. Then it disappears and I have a xfdesktop and compiz. So
>> I run 'xfce4-panel &' from terminal and everything is up and running. It
>> looks like it starts too early. I have no idea how to get an error
>> message as I do not have anything up when it starts and crashes.
>>
>
> Messages can usually be found in ~/.xsession-errors or /var/log/XOrg.0.log .
>
>
> _______________________________________________
> Xfce mailing list
> Xfce at xfce.org
> http://foo-projects.org/mailman/listinfo/xfce
> http://www.xfce.org
>
here it is, .xsession-error
> /etc/gdm/PreSession/Default: Registering your session with wtmp and utmp
> /etc/gdm/PreSession/Default: running: /usr/bin/sessreg -a -w
> /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l
> ":0" "alex"
> /etc/gdm/Xsession: Beginning session setup...
> /usr/bin/startxfce4: X server already running on display :0
> /etc/xdg/xfce4/xinitrc: line 54: xscreensaver: command not found
>
> (xfdesktop:4338): libxfcegui4-CRITICAL **: netk_workspace_get_number:
> assertion `NETK_IS_WORKSPACE (space)' failed
>
> libxfcegui4-ERROR **: file netk-pager.c: line 274
> (netk_pager_size_request): assertion failed: (pager->priv->n_rows > 0)
> aborting...
>
> (xfce4-cpugraph-plugin:4344): Gdk-WARNING **: GdkWindow 0xe00030
> unexpectedly destroyed
>
> (xfce4-cpugraph-plugin:4344): Gdk-WARNING **: GdkWindow 0xe0002f
> unexpectedly destroyed
>
> (xfce4-cpugraph-plugin:4344): Gdk-WARNING **: GdkWindow 0xe00003
> unexpectedly destroyed
>
> (xfce4-fsguard-plugin:4345): Gdk-WARNING **: GdkWindow 0x1000030
> unexpectedly destroyed
>
> (xfce4-fsguard-plugin:4345): Gdk-WARNING **: GdkWindow 0x100002f
> unexpectedly destroyed
>
> (xfce4-fsguard-plugin:4345): Gdk-WARNING **: GdkWindow 0x1000003
> unexpectedly destroyed
>
> (xfce4-fsguard-plugin:4346): Gdk-WARNING **: GdkWindow 0x1200030
> unexpectedly destroyed
>
> (xfce4-fsguard-plugin:4346): Gdk-WARNING **: GdkWindow 0x120002f
> unexpectedly destroyed
>
> (xfce4-fsguard-plugin:4346): Gdk-WARNING **: GdkWindow 0x1200003
> unexpectedly destroyed
>
> (xfce4-menu-plugin:4352): Gdk-WARNING **: GdkWindow 0x1a00003
> unexpectedly destroyed
>
> (xfce4-verve-plugin:4353): Gdk-WARNING **: GdkWindow 0x1c00003
> unexpectedly destroyed
>
> (xfce4-netload-plugin:4355): Gdk-WARNING **: GdkWindow 0x1e00003
> unexpectedly destroyed
>
> (xfce4-battery-plugin:4354): Gdk-WARNING **: GdkWindow 0x2000003
> unexpectedly destroyed
>
> (xfce4-mixer-plugin:4356): Gdk-WARNING **: GdkWindow 0x2200003
> unexpectedly destroyed
> The program 'gaim' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadWindow (invalid Window parameter)'.
> (Details: serial 486 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.)
>
> (xfce4-xfapplet-plugin:4347): Gdk-WARNING **: GdkWindow 0x1800003
> unexpectedly destroyed
>
> (xfce4-xfapplet-plugin:4347): Bonobo-CRITICAL **:
> bonobo_widget_new_control_from_objref: assertion `control !=
> CORBA_OBJECT_NIL' failed
>
> (xfce4-xfapplet-plugin:4347): Bonobo-CRITICAL **:
> bonobo_widget_get_control_frame: assertion `BONOBO_IS_WIDGET
> (bonobo_widget)' failed
>
> (xfce4-xfapplet-plugin:4347): Bonobo-CRITICAL **:
> bonobo_control_frame_get_popup_component: assertion
> `BONOBO_IS_CONTROL_FRAME (control_frame)' failed
>
> (xfce4-xfapplet-plugin:4347): Bonobo-CRITICAL **:
> bonobo_control_frame_get_control_property_bag: assertion `frame !=
> NULL' failed
>
> (xfce4-xfapplet-plugin:4347): Bonobo-CRITICAL **:
> bonobo_ui_component_freeze: assertion `BONOBO_IS_UI_COMPONENT
> (component)' failed
>
> (xfce4-xfapplet-plugin:4347): Bonobo-CRITICAL **:
> bonobo_ui_component_get_container: assertion `BONOBO_IS_UI_COMPONENT
> (component)' failed
>
> (xfce4-xfapplet-plugin:4347): Bonobo-WARNING **: Component must be
> associated with a container first see bonobo_component_set_container
>
> (xfce4-xfapplet-plugin:4347): Bonobo-CRITICAL **:
> bonobo_ui_component_add_verb_full: assertion `BONOBO_IS_UI_COMPONENT
> (component)' failed
>
> (xfce4-xfapplet-plugin:4347): Bonobo-CRITICAL **:
> bonobo_ui_component_add_verb_full: assertion `BONOBO_IS_UI_COMPONENT
> (component)' failed
>
> (xfce4-xfapplet-plugin:4347): Bonobo-CRITICAL **:
> bonobo_ui_component_add_verb_full: assertion `BONOBO_IS_UI_COMPONENT
> (component)' failed
>
> (xfce4-xfapplet-plugin:4347): Bonobo-CRITICAL **:
> bonobo_ui_component_add_verb_full: assertion `BONOBO_IS_UI_COMPONENT
> (component)' failed
>
> (xfce4-xfapplet-plugin:4347): Bonobo-CRITICAL **:
> bonobo_ui_component_add_verb_full: assertion `BONOBO_IS_UI_COMPONENT
> (component)' failed
>
> (xfce4-xfapplet-plugin:4347): Bonobo-CRITICAL **:
> bonobo_ui_component_add_verb_full: assertion `BONOBO_IS_UI_COMPONENT
> (component)' failed
>
> (xfce4-xfapplet-plugin:4347): Bonobo-CRITICAL **:
> bonobo_ui_component_thaw: assertion `BONOBO_IS_UI_COMPONENT
> (component)' failed
> 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 189 error_code 3 request_code 129 minor_code 2)
> (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.)
>
> ** (orage:4362): WARNING **: xfical_internal_file_open: lical->file
> already open
>
>
> ** (orage:4362): WARNING **: xfical_file_open: lical->file is now open
>
>
> ** (orage:4362): WARNING **: xfical_internal_file_open: lical->file
> already open
>
>
> ** (orage:4362): WARNING **: xfical_file_open: lical->file is now open
>
>
> (devilspie:4367): Wnck-WARNING **: Columns = 0 rows = 0 in
> _NET_DESKTOP_LAYOUT makes no sense
>
>
> ** (orage:4362): WARNING **: xfical_internal_file_open: lical->file
> already open
>
>
> ** (orage:4362): WARNING **: xfical_file_open: lical->file is now open
>
> /usr/bin/compiz-aiglx: No stencil buffer. Clipping of transformed
> windows is not going to be correct when screen is transformed.
> Window Title: 'xfce4-session'; Application Name: 'xfce4-session';
> Class: 'Xfce4-session'; Geometry: 1x1+0+0
>
> (gnome-window-decorator-aiglx:4368): Wnck-WARNING **: Columns = 0 rows
> = 0 in _NET_DESKTOP_LAYOUT makes no sense
>
> Window Title: 'compiz-aiglx'; Application Name: 'compiz-aiglx'; Class:
> ''; Geometry: 1x1+-100+-100
>
> ** (orage:4362): WARNING **: xfical_internal_file_open: lical->file
> already open
>
>
> ** (orage:4362): WARNING **: xfical_file_open: lical->file is now open
>
> Window Title: 'Run program'; Application Name: 'xfrun4'; Class:
> 'Xfrun4'; Geometry: 400x103+312+332
> Window Title: 'compiz-aiglx'; Application Name: 'compiz-aiglx'; Class:
> ''; Geometry: 1x1+-100+-100
> Window Title: 'xffm-iconview'; Application Name: 'xffm-iconview';
> Class: 'Xffm-iconview'; Geometry: 440x436+65+128
> Xlib: sequence lost (0x109aa > 0x9dd) in reply type 0x0!
> The program 'xffm-iconview' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadImplementation (server does not implement operation)'.
> (Details: serial 2474 error_code 17 request_code 20 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.)
> Window Title: 'compiz-aiglx'; Application Name: 'compiz-aiglx'; Class:
> ''; Geometry: 1x1+-100+-100
> Generating icon-module cache. This may take a bit...
> Icon-module cache complete!
More information about the Xfce
mailing list