GNOME Bugzilla – Bug 110106
Error when using Xwindows Server running from Win2K
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-panel Severity: normal Version: 2.0.6 Synopsis: Error when using Xwindows Server running from Win2K Bugzilla-Product: gnome-panel Bugzilla-Component: Panel BugBuddy-GnomeVersion: 2.0 (2.0.3) Description: Description of Problem: When launching gnome-panel after issuing export DISPLAY=xxx:0 and entering gnome-panel, panel appears and then followed by gnome bug reports request. Telnet session reports -bash-2.05b$ export DISPLAY=192.168.0.90:0 -bash-2.05b$ export DISPLAY=192.168.0.2:0 -bash-2.05b$ gnome-panel system-tray-applet-ERROR **: file obox.c: line 107 (get_class): should not aborting... Xlib: extension "RENDER" missing on display "192.168.0.2:0.0". Xlib: extension "RENDER" missing on display "192.168.0.2:0.0". Steps to reproduce the problem: 1. export DISPLAY=xxx.xxx.xxx.xxx:0 2. gnome-panel 3. Actual Results: system-tray-applet-ERROR **: file obox.c: line 107 (get_class): should not aborting... Xlib: extension "RENDER" missing on display "192.168.0.2:0.0". Xlib: extension "RENDER" missing on display "192.168.0.2:0.0". Expected Results: How often does this happen? Fails upon second ans subsequant use. First time after a "boot\ works ok Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found)...(no debugging symbols found)...[New Thread 8192 (LWP 15609)] 0x420ae169 in wait4 () from /lib/i686/libc.so.6
+ Trace 35636
Thread 1 (Thread 8192 (LWP 15609))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-04-06 12:02 ------- The original reporter (alfarre@attglobal.net) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, gnome-panel-maint@bugzilla.gnome.org.
You're the latest victim of the infamous vertical panel crasher bug. See Havoc's comment in bug 94625 for where you can get fixed packages. *** This bug has been marked as a duplicate of 94625 ***