[Bug 278261] Re: two xscreens - gnome panel crashes
We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help. ** Changed in: libxcb (Ubuntu) Status: Incomplete = Expired -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
Hi TJ, thanks for all the analysis work. Can you test to see if this issue was still afflicting lucid (and/or maverick). If it is, is libx11 still the right package or should it be filed against a different package? ** Changed in: libxcb (Ubuntu) Status: Confirmed = Incomplete -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
** Tags added: intrepid -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
I believe I've managed to identify the issue here. It is dependent on my having correctly navigated the register variable identification. Gdb is supposed to report which register the variable is stored in using info address dpy but this reports Symbol dpy is a variable with multiple locations - not exactly helpful. I then looked at all the registers (info registers) and saw that rbx and rdi contained the same value. I took a leap of faith and assumed this was the dpy pointer. Examining the structure there the values seem to make sense in the context of a Display pointer (which is a typedef of the true _XDisplay). The breakpoint was triggered after trying to open a program via a custom launcher on screen 1 (DISPLAY=:0.1). In XDefineCursor(Display dpy, Window w, Cursor c) the values in the dpy structure show: (gdb) print ((Display *)$rbx)-proto_major_version $14 = 11 (gdb) print ((Display *)$rbx)-proto_minor_version $15 = 0 (gdb) print ((Display *)$rbx)-vendor $16 = 0x204cbc0 The X.Org Foundation (gdb) print ((Display *)$rbx)-nscreens $11 = 2 (gdb) print ((Display *)$rbx)-display_name $12 = 0x2032c50 :0.0 (gdb) print ((Display *)$rbx)-default_screen $13 = 0 Notice that display_name is :0.0 when it should be :0.1. This suggests that the GDK_WINDOW_XDISPLAY and subsidiary macros in the GTK package are not delivering the correct result. Because the issue is limited to custom launchers on display :0.1 it looks likely the problem is higher up the call stack; most likely in gnome-panel itself. -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
Having just patched glib to fix bug #290935 dual screen all panels end up on one screen at startup I'm using dual screens again and hit this bug whilst using compiz cube and nvidia drivers. Metacity /apps/metacity/general/compositing_manager = false. Running gnome-panel from within gdb shows the following stack-trace when gnome-panel crashes after clicking on a custom launcher on the gnome- panel on screen 1. This doesn't crash using the 'standard' menu items on screen 1. (Screen 1 is the *second* screen). The problem seems to originate from: #21 0x7f50f90ed5b2 in gdk_window_new () from /usr/lib/libgdk-x11-2.0.so.0 ... #27 0x7f50f95a0516 in gtk_widget_realize () from /usr/lib/libgtk-x11-2.0.so.0 #28 0x0042d509 in xstuff_zoom_animate () #29 0x00442919 in launcher_launch () gdb --args gnome-panel --sync (gdb) run Starting program: /usr/bin/gnome-panel --sync [Thread debugging using libthread_db enabled] ... ** (gnome-panel:9749): DEBUG: Adding applet 40. [New Thread 0x7f50e2384950 (LWP 9796)] [New Thread 0x7f50e1b83950 (LWP 9797)] The program 'gnome-panel' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 18571 error_code 8 request_code 1 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.) Program received signal SIGPIPE, Broken pipe. [Switching to Thread 0x7f50fad887d0 (LWP 9749)] 0x7f50f6f7022c in __libc_writev (fd=33, vector=0x1cc1d80, count=1) at ../sysdeps/unix/sysv/linux/writev.c:46 46 ../sysdeps/unix/sysv/linux/writev.c: No such file or directory. in ../sysdeps/unix/sysv/linux/writev.c (gdb) bt #0 0x7f50f6f7022c in __libc_writev (fd=33, vector=0x1cc1d80, count=1) at ../sysdeps/unix/sysv/linux/writev.c:46 #1 0x7f50f9dd84e6 in write_data_T (cnx=0x1cf9170, qw=0x7fff02dca510) at linc-connection.c:1048 #2 0x7f50f9dd99ff in link_connection_writev (cnx=0x1cf9170, vecs=0x1cc1d80, nvecs=1, opt_write_opts=0x0) at linc-connection.c:1244 #3 0x7f50f9db834e in giop_connection_close (cnx=0x1cf9170) at giop-connection.c:54 #4 0x7f50f9db8371 in giop_connection_dispose (obj=0x1cf9170) at giop-connection.c:68 #5 0x7f50f79fb690 in IA__g_object_run_dispose (object=0x1cf9170) at /tmp/buildd/glib2.0-2.20.1/gobject/gobject.c:789 #6 0x7f50f9dd7da0 in link_connections_close () at linc-connection.c:1655 #7 0x7f50f9db8919 in giop_shutdown () at giop.c:658 #8 0x7f50f9dbcf7f in CORBA_ORB_shutdown (orb=0x161d1c0, wait_for_completion=1 '\001', ev=0x7fff02dca620) at corba-orb.c:1238 #9 0x7f50f9dbd0cd in CORBA_ORB_destroy (orb=0x21, ev=0x7fff02dca620) at corba-orb.c:1257 #10 0x7f50f9dbe692 in shutdown_orb () at corba-orb.c:306 #11 0x7f50f6ec86ed in *__GI_exit (status=1) at exit.c:75 #12 0x7f50f910bc21 in ?? () from /usr/lib/libgdk-x11-2.0.so.0 #13 0x7f50f74625b4 in _XError () from /usr/lib/libX11.so.6 #14 0x7f50f74698f9 in ?? () from /usr/lib/libX11.so.6 #15 0x7f50f7469fd8 in _XReply () from /usr/lib/libX11.so.6 #16 0x7f50f745de13 in XSync () from /usr/lib/libX11.so.6 #17 0x7f50f745dfcb in ?? () from /usr/lib/libX11.so.6 #18 0x7f50f743f0cf in XDefineCursor () from /usr/lib/libX11.so.6 #19 0x7f50f9119588 in ?? () from /usr/lib/libgdk-x11-2.0.so.0 #20 0x7f50f9118f98 in ?? () from /usr/lib/libgdk-x11-2.0.so.0 #21 0x7f50f90ed5b2 in gdk_window_new () from /usr/lib/libgdk-x11-2.0.so.0 #22 0x7f50f95b04f8 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #23 0x7f50f79f927d in IA__g_closure_invoke (closure=0x15e3c60, return_value=0x0, n_param_values=1, param_values=0x2199560, invocation_hint=0x7fff02dcacc0) at /tmp/buildd/glib2.0-2.20.1/gobject/gclosure.c:767 #24 0x7f50f7a0e723 in signal_emit_unlocked_R (node=0x15e3cd0, detail=0, instance=0x2162090, emission_return=0x0, instance_and_params=0x2199560) at /tmp/buildd/glib2.0-2.20.1/gobject/gsignal.c:3177 #25 0x7f50f7a10432 in IA__g_signal_emit_valist (instance=0x2162090, signal_id=value optimized out, detail=0, var_args=0x7fff02dcaea0) at /tmp/buildd/glib2.0-2.20.1/gobject/gsignal.c:2980 #26 0x7f50f7a10953 in IA__g_signal_emit (instance=0x21, signal_id=30154112, detail=1) at /tmp/buildd/glib2.0-2.20.1/gobject/gsignal.c:3037 #27 0x7f50f95a0516 in gtk_widget_realize () from /usr/lib/libgtk-x11-2.0.so.0 #28 0x0042d509 in xstuff_zoom_animate () #29 0x00442919 in launcher_launch () #30 0x7f50f79f927d in IA__g_closure_invoke (closure=0x1efefd0, return_value=0x0, n_param_values=1, param_values=0x21994a0, invocation_hint=0x7fff02dcb280) at
[Bug 278261] Re: two xscreens - gnome panel crashes
I neglected to install the libgtk ebug symbols for the previous back- trace. Here's a summary of the key parts that I'm focusing on: #19 0x7fd66d49a588 in gdk_window_x11_set_cursor (window=0x148f960, cursor=0x0) at /build/buildd/gtk+2.0-2.16.1/gdk/x11/gdkwindow-x11.c:2912 #20 0x7fd66d499f98 in _gdk_window_new (parent=0x105f000, attributes=0x7fff7714ce50, attributes_mask=value optimized out) at /build/buildd/gtk+2.0-2.16.1/gdk/x11/gdkwindow-x11.c:904 #21 0x7fd66d46e5b2 in IA__gdk_window_new (parent=0x105f000, attributes=0x7fff7714ce50, attributes_mask=736) at /build/buildd/gtk+2.0-2.16.1/gdk/gdkwindow.c:379 #22 0x7fd66d9314f8 in gtk_window_realize (widget=0x1ba8ea0) at /build/buildd/gtk+2.0-2.16.1/gtk/gtkwindow.c:4788 #23 0x7fd66bd7a27d in IA__g_closure_invoke (closure=0x1073160, return_value=0x0, n_param_values=1, param_values=0x1a7d340, invocation_hint=0x7fff7714d040) at /tmp/buildd/glib2.0-2.20.1/gobject/gclosure.c:767 #24 0x7fd66bd8f723 in signal_emit_unlocked_R (node=0x10731d0, detail=0, instance=0x1ba8ea0, emission_return=0x0, instance_and_params=0x1a7d340) at /tmp/buildd/glib2.0-2.20.1/gobject/gsignal.c:3177 #25 0x7fd66bd91432 in IA__g_signal_emit_valist (instance=0x1ba8ea0, signal_id=value optimized out, detail=0, var_args=0x7fff7714d220) at /tmp/buildd/glib2.0-2.20.1/gobject/gsignal.c:2980 #26 0x7fd66bd91953 in IA__g_signal_emit (instance=0x24, signal_id=24437312, detail=1) at /tmp/buildd/glib2.0-2.20.1/gobject/gsignal.c:3037 #27 0x7fd66d921516 in IA__gtk_widget_realize (widget=0x1ba8ea0) at /build/buildd/gtk+2.0-2.16.1/gtk/gtkwidget.c:3322 #28 0x0042d509 in xstuff_zoom_animate () #29 0x00442919 in launcher_launch () Looking at gdk_window_new() its parameters break down as: (gdb) print parent $18 = (GdkWindow *) 0x11c3000 (gdb) print /x attributes_mask $17 = 0x2e0 (GDK_WA_TYPE_HINT | GDK_WA_CURSOR | GDK_WA_Y | GDK_WA_X ) (gdb) print attributes-title $1 = (gchar *) 0x0 (gdb) print attributes-event_mask $2 = 64514 (gdb) print attributes-x $3 = 0 (gdb) print attributes-y $4 = 30946192 (gdb) print attributes-width $5 = 200 (gdb) print attributes-height $6 = 200 (gdb) print attributes-wclass $7 = GDK_INPUT_OUTPUT (gdb) print attributes-window_type $9 = GDK_WINDOW_TEMP (gdb) print attributes-cursor $10 = (GdkCursor *) 0x1d82560 (gdb) print attributes-wmclass_name $11 = (gchar *) 0x1d84850 gnome-panel (gdb) print attributes-wmclass_class $12 = (gchar *) 0x1d848a0 Gnome-panel (gdb) print attributes-override_redirect $13 = 18706784 (gdb) print attributes-type_hint $14 = GDK_WINDOW_TYPE_HINT_NORMAL (gdb) print /x attributes-cursor-type $28 = 0x11cffd0 Not clear what this indicates, but: #19 0x7fd66d49a588 in gdk_window_x11_set_cursor (window=0x148f960, cursor=0x0) at /build/buildd/gtk+2.0-2.16.1/gdk/x11/gdkwindow-x11.c:2912 indicates cursor = GDK_X_CURSOR. Adding the libx11-6 debug symbols shows: #11 0x7f4c174806ed in *__GI_exit (status=1) at exit.c:75 #12 0x7f4c196c3c21 in gdk_x_error (display=value optimized out, error=value optimized out) at /build/buildd/gtk+2.0-2.16.1/gdk/x11/gdkmain-x11.c:645 #13 0x7f4c17a1a5b4 in _XError (dpy=0x1a427f0, rep=0x2672fc0) at ../../src/XlibInt.c:2931 #14 0x7f4c17a218f9 in process_responses (dpy=0x1a427f0, wait_for_first_event=0, current_error=0x7fff23383058, current_request=17837) at ../../src/xcb_io.c:207 #15 0x7f4c17a21fd8 in _XReply (dpy=0x1a427f0, rep=0x7fff233830a0, extra=0, discard=1) at ../../src/xcb_io.c:457 #16 0x7f4c17a15e13 in XSync (dpy=0x1a427f0, discard=0) at ../../src/Sync.c:48 #17 0x7f4c17a15fcb in _XSyncFunction (dpy=0x20) at ../../src/Synchro.c:37 #18 0x7f4c179f70cf in XDefineCursor (dpy=0x1a427f0, w=20972868, cursor=0) at ../../src/DefCursor.c:48 #19 0x7f4c196d1588 in gdk_window_x11_set_cursor (window=0x247e640, cursor=0x0) at /build/buildd/gtk+2.0-2.16.1/gdk/x11/gdkwindow-x11.c:2912 -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
Looking at the libx11-dev package source code I see that the 'Display'
value is optimized out into a register variable, which is a pain since
that is likely key to the bug and doesn't show up in gdb output.
libx11/src/DefCursor.c:
int
XDefineCursor (
register Display *dpy,
Window w,
Cursor cursor)
{
This function is called from
gtk+2.0-2.16.1/gdk/x11/gdkwindow-x11.c::gdk_window_x11_set_cursor()
if (!GDK_WINDOW_DESTROYED (window))
{
XDefineCursor (GDK_WINDOW_XDISPLAY (window),
GDK_WINDOW_XID (window),
xcursor);
if (cursor)
impl-cursor = gdk_cursor_ref (cursor);
}
Which comes from:
#define GDK_WINDOW_XDISPLAY(win) (GDK_SCREEN_X11 (GDK_WINDOW_SCREEN
(win))-xdisplay)
#define GDK_SCREEN_X11(object) (G_TYPE_CHECK_INSTANCE_CAST
((object), GDK_TYPE_SCREEN_X11, GdkScreenX11))
#define GDK_WINDOW_SCREEN(win)(GDK_DRAWABLE_IMPL_X11
(((GdkWindowObject)
win)-impl)-screen)
--
two xscreens - gnome panel crashes
https://bugs.launchpad.net/bugs/278261
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
** Changed in: libxcb (Ubuntu) Status: Incomplete = Confirmed -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
I still experience this problem in Ubuntu Jausty as well as Intrepid. The Gnome fix didn't help for me, since it still occurs on Jausty with Gnome 2.26 The program 'gnome-panel' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 26711 error_code 8 request_code 1 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.) -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
I just experienced this error. If I enable compiz and use the second screen I get a box with only error when I click on a gnome-panel icon on my second desktop. If I kill gnome-panel, disable compiz (effects=none) and try again it still crashes, logging off and on after disabling compiz my system is working correctly. Intrepid, I have either nvidia 177 or 173 (no idea, I keep switching) my .xsession-errors ends like this (I don't have bluetooth so I think they are not important) alarm-queue.c:531 (load_alarms) alarm-queue.c:560 (load_alarms) - Setting Call backs alarm-queue.c:1985 (alarm_queue_add_async) - 0x1c78b00 alarm-queue.c:594 (load_alarms_for_today) - From Wed Mar 25Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2a00024 (Music Play) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. ALSA lib ../../../src/pcm/pcm.c:2156:(snd_pcm_open_conf) Cannot open shared library /usr/lib32/alsa-lib/libasound_module_pcm_bluetooth.so ALSA lib ../../../src/pcm/pcm.c:2156:(snd_pcm_open_conf) Cannot open shared library /usr/lib32/alsa-lib/libasound_module_pcm_bluetooth.so ALSA lib ../../../src/pcm/pcm.c:2156:(snd_pcm_open_conf) Cannot open shared library /usr/lib32/alsa-lib/libasound_module_pcm_bluetooth.so ALSA lib ../../../src/pcm/pcm.c:2156:(snd_pcm_open_conf) Cannot open shared library /usr/lib32/alsa-lib/libasound_module_pcm_bluetooth.so ALSA lib ../../../src/pcm/pcm.c:2156:(snd_pcm_open_conf) Cannot open shared library /usr/lib32/alsa-lib/libasound_module_pcm_bluetooth.so ALSA lib ../../../src/pcm/pcm.c:2156:(snd_pcm_open_conf) Cannot open shared library /usr/lib32/alsa-lib/libasound_module_pcm_bluetooth.so PID TTY TIME CMD 9528 ?00:00:02 pulseaudio PID TTY TIME CMD ERROR: whilst scanning summary file -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
I tried the fix mentioned by Nico-S (in comment #33), and it works. Thanks! -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
Same problem, attached xsession-errors kernel: 2.6.27-4-generic Ubuntu: Intrepid(8.10) Gnome: 2.24.1 nvidia-drivers: 180.22 gnome-panel: Panel 2.24.1 ** Attachment added: xsession-errors http://launchpadlibrarian.net/21899983/xsession-errors -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
I also experience this issue with gnome-panel and 2 X screens, in combination with nvidia 177 drivers, running Ubuntu Intrepid. I attached the output of lspci -vvnn ** Attachment added: lspci -vvnn http://launchpadlibrarian.net/21711003/lspci.txt -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
I also get this: The program 'gnome-panel' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 12030 error_code 8 request_code 1 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.) Locking assertion failure. Backtrace: #0 /usr/lib/libxcb-xlib.so.0 [0xb6fa97c7] #1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x2e) [0xb6fa996e] #2 /usr/lib/libX11.so.6 [0xb762d619] #3 /usr/lib/libX11.so.6(XCreateWindow+0x26) [0xb7623bc6] #4 /usr/lib/libgdk-x11-2.0.so.0 [0xb7a115e5] #5 /usr/lib/libgdk-x11-2.0.so.0(gdk_window_new+0x34) [0xb79e1474] #6 /usr/lib/libgtk-x11-2.0.so.0 [0xb7c9a446] #7 /usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x84) [0xb77aa3d4] #8 /usr/lib/libgobject-2.0.so.0 [0xb779b3c9] #9 /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0xd8) [0xb779cb78] #10 /usr/lib/libgobject-2.0.so.0 [0xb77b28ee] #11 /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x7dc) [0xb77b47ac] #12 /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x26) [0xb77b4c26] #13 /usr/lib/libgtk-x11-2.0.so.0(gtk_widget_realize+0xb1) [0xb7c89251] #14 /usr/lib/libgtk-x11-2.0.so.0 [0xb7c9adc8] #15 /usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x84) [0xb77aa3d4] #16 /usr/lib/libgobject-2.0.so.0 [0xb779b3c9] #17 /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x1ab) [0xb779cc4b] #18 /usr/lib/libgobject-2.0.so.0 [0xb77b28ee] #19 /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x7dc) [0xb77b47ac] -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
note: it only occurs when I add a application launcher to the gnome panel on the 2nd X screen and click/start that launcher. This seems to happen with any application I try to launch from the gnome-panel launchers on the 2nd X screen -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
When I start a new gnome-panel myself (on the 2nd X screen) the problem seems solved. As reported above, when the gnome-panel crashed, a error popup (without text) is displayed on the 1st X screen. When I killall -9 gnome-panel, it restarts by itself, and still crashes with the reported behaviour. However when I start a new gnome-panel myself, from the 2nd X screen the problem no longer exists. This may indicate a error with gnome-panel trying to attach to the wrong X screen. -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
When doing the above, the problem moves to the 1st X screen. If gnome- panel is started from the 2nd X screen, using launchers from the 1st X screen causes the crash. The other way around, if gnome-panel is started from the 1st X screen, using launchers from the 2nd X screen causes the crash. -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
Hi, I resolved the problem on my computer. It was an interaction with metacity, linked to the /apps/metacity/general/compositing_manager key. If it is true then some visuals effects are done without compiz, but it has to be set to false to remove my problems. The question is : where is the bug ? In Metacity/compiz or in other used libs ? Thanks to all, Nicolas. -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
another 'weird' behaviour: if I add a application launcher to my desktop on the 2nd X screen, and I double click that launcher on the 2nd X screen desktop, the application appears on the 1st X screen. Only starting applications from the applications menu on the 2nd X screen seems to work properly. -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
I don't seem to have that key in my gconf and still experience the issue -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
[This is an automated message] Hi tdomhan, Please attach the output of `lspci -vvnn` too. ** Changed in: libxcb (Ubuntu) Status: New = Incomplete -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
I'm not sure if this will help, but I'm experiencing something eerily similar. I'm on Hardy using Gnome. I have two screens. I'm working on a Qt 4.5 app. When I launch the app on the first screen, things at first seem ok. However, if I move the window (even a couple pixels), then Gnome tries to reposition the window offsetting the window a couple pixels, then tries to do it again and again and the entire system crawls to a near halt. I was watching processes (top) and it went something like this: - gnome-panel 77% - Xorg 40% - metacity ~20% - my app ~20% Btw, I have two AMD CPUs. -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
By the way, this ONLY happens when I move the main window (derived from QMainWindow). It does not happen if I move the Open File dialog or other popup dialog. -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
Please disregard my last two comments. This was a bug on my part. -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
Here is my ~/xsession-errors trace : (gnome-panel:6538): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24 (gnome-panel:6538): Gdk-WARNING **: /build/buildd/gtk+2.0-2.14.4/gdk/x11/gdkdrawable-x11.c:878 drawable is not a pixmap or window The program 'gnome-panel' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 7227 error_code 8 request_code 1 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.) Locking assertion failure. Backtrace: #0 /usr/lib/libxcb-xlib.so.0 [0x7f6596a469fc] #1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x17) [0x7f6596a46b77] #2 /usr/lib/libX11.so.6 [0x7f659c3478c0] #3 /usr/lib/libX11.so.6(XCreateWindow+0x44) [0x7f659c33e704] #4 /usr/lib/libgdk-x11-2.0.so.0 [0x7f659dfe8b1f] #5 /usr/lib/libgdk-x11-2.0.so.0(gdk_window_new+0xe) [0x7f659dfb9f8e] #6 /usr/lib/libgtk-x11-2.0.so.0 [0x7f659e471528] #7 /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0xbf) [0x7f659c8d81af] #8 /usr/lib/libgobject-2.0.so.0 [0x7f659c8ed878] #9 /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x7b8) [0x7f659c8ef608] #10 /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x83) [0x7f659c8efb33] #11 /usr/lib/libgtk-x11-2.0.so.0(gtk_widget_realize+0x96) [0x7f659e461b66] #12 /usr/lib/libgtk-x11-2.0.so.0 [0x7f659e471da8] #13 /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x16d) [0x7f659c8d825d] #14 /usr/lib/libgobject-2.0.so.0 [0x7f659c8ed878] #15 /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x7b8) [0x7f659c8ef608] #16 /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x83) [0x7f659c8efb33] #17 /usr/lib/libgtk-x11-2.0.so.0(gtk_widget_show+0x8c) [0x7f659e462b2c] #18 gnome-panel [0x44567c] #19 /usr/lib/libORBit-2.so.0 [0x7f659ea6c21d] -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
kernel: 2.6.27-9-generic Ubuntu: Intrepid(8.10) nvidia-drivers: 177.8 Gnome: gnome-panel: 1:2.24.1-0ubuntu2.1 ProblemType: Bug Architecture: x86_64 (Intel(R) Core(TM)2 Duo CPU T8300) DistroRelease: Ubuntu 8.10 NonfreeKernelModules: nvidia Hi, First of all, thanks to all ubunutu developers and debuggers for their wonderfull work. I have the same problem, and I will try to give some other information. First, notice that I don't use Compiz. Next, on my laptop, this problem can, sometimes, be by-passed. It is sometimes sufficient to launch an application from the first desktop, to enable to launch another app from the second one. After what there is no more freeze of the gnome-panel, but the CPU is still used with 100% by gnome-panel (more precisely, each core is used with 100% by each of the two gnome panels). I will try to install the debug tools described previously. Thanks, Nicolas. Thanks -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
I ran into this same problem on 2 machines I updated today. I also ran into the 177 vs 173 problem. Downgrading to 173 fixed the second screen desktop. I run independent screens like most people writing here. When I use an application launcher in the gnome panel to launch something the gnome-panel becomes non-responsive and consumes 100% of one cpu. 'killall'ing it brings up another gnome-panel which works so long as I do not launch something from the screen 1 gnome-panel. I can launch things from the gnome menu successfully, but launching from an custom application launcher causes the lockup. -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
Hi guys I am in the same boat.. running Ibex using nvidia 177 and tried 173 drivers.. any progress been made yet? -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
As Sebastien said the the crash is one in libxcb, rejecting the gnome- panel task. ** Changed in: gnome-panel (Ubuntu) Status: Confirmed = Invalid -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
** Changed in: gnome-panel (Ubuntu) Status: New = Confirmed -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
Your latest comment indicate that it hangs could you lease try to obtain a backtrace of the hang http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem. ** Changed in: gnome-panel (Ubuntu) Status: Confirmed = Incomplete -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
Ok, I am stuck with a silly problem, please forgive me because this the first time I attempt to debug. From the instruction given here: http://wiki.ubuntu.com/DebuggingProgramCrash Which points to here: https://wiki.ubuntu.com/Backtrace I followed the instructions in section Already running programs until after step 4. I proceed to reproduce the problem. Then, in step 5, it said press ctrl+c because the program is frozen. But pressing ctrl+c then caused gdb to quit entirely to bash prompt. Therefore, I am unable to proceed to step 6. -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
Ok, I saw these in the .xsession-errors: ICEDTEAPLUGIN_DEBUG = (null) The program 'gnome-panel' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 22028 error_code 8 request_code 1 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.) Locking assertion failure. Backtrace: #0 /usr/lib/libxcb-xlib.so.0 [0x7f2fb18d39fc] #1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x17) [0x7f2fb18d3b77] #2 /usr/lib/libX11.so.6 [0x7f2fb71d48c0] #3 /usr/lib/libX11.so.6(XCreateWindow+0x44) [0x7f2fb71cb704] #4 /usr/lib/libgdk-x11-2.0.so.0 [0x7f2fb8e75b1f] #5 /usr/lib/libgdk-x11-2.0.so.0(gdk_window_new+0xe) [0x7f2fb8e46f8e] #6 /usr/lib/libgtk-x11-2.0.so.0 [0x7f2fb92fe528] #7 /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0xbf) [0x7f2fb77651af] #8 /usr/lib/libgobject-2.0.so.0 [0x7f2fb777a878] #9 /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x7b8) [0x7f2fb777c608] #10 /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x83) [0x7f2fb777cb33] #11 /usr/lib/libgtk-x11-2.0.so.0(gtk_widget_realize+0x96) [0x7f2fb92eeb66] #12 /usr/lib/libgtk-x11-2.0.so.0 [0x7f2fb92feda8] #13 /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x16d) [0x7f2fb776525d] #14 /usr/lib/libgobject-2.0.so.0 [0x7f2fb777a878] #15 /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x7b8) [0x7f2fb777c608] #16 /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x83) [0x7f2fb777cb33] #17 /usr/lib/libgtk-x11-2.0.so.0(gtk_widget_show+0x8c) [0x7f2fb92efb2c] #18 gnome-panel [0x44567c] #19 /usr/lib/libORBit-2.so.0 [0x7f2fb98f921d] -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
the crash seems to be a libxcb one ** Changed in: libxcb (Ubuntu) Sourcepackagename: gnome-panel = libxcb Assignee: Ubuntu Desktop Bugs (desktop-bugs) = (unassigned) Status: Incomplete = New ** Changed in: libxcb (Ubuntu) Importance: Medium = Low ** Changed in: libxcb (Ubuntu) Importance: Low = Medium -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
I changed to nvidia 173 driver, gnome-panel problem still occurs. -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
** Changed in: gnome-panel (Ubuntu) Status: Invalid = Confirmed -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
I downgraded to the 173 nvidia drivers as suggested by revgazza and the desktop is fully shown on external monitor. However, the gnome-panel's 100% consuming bug still remains. -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
Happens for me with or without Compiz activated. Also Nautilus refuses to open windows on Screen 1 (they always open on Screen 0) Beginning to regret having upgraded to Intrepid. This is seriously affecting my productivity. -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
botticchio, your problem happened for me using the 177 nvidia-drivers. Using the 173 drivers fixes the problem -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
I am seeing the same problem as reported by user chewearn. However, it only seems to happen when I have compiz activated. kernel: 2.6.27-7-generic Ubuntu: Intrepid(8.10) Gnome: 2.24.1 nvidia-drivers: 177 gnome-panel: 1:2.24.1-0ubuntu2 compiz: 1:0.7.8-0ubuntu4.1 In addition, I don't know if it is related to this problem, but on the external monitor the desktop is cut, as shown in the attached image. When I disable compiz the external desktop is fully shown, even though nautilus windows opened in the external desktop are shown on screen 1. The other applications are correctly opened on screen 2 (external). ** Attachment added: external_monitor.jpg http://launchpadlibrarian.net/19508606/external_monitor.jpg -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
I am seeing the same problem. kernel: 2.6.27-7-generic x86_64 Ubuntu: Intrepid(8.10) Gnome: 2.24.1 nvidia-drivers: 177 gnome-panel: 1:2.24.1-0ubuntu2 Two monitors, separate X screens. If I click on a panel application launcher on screen 2, gnome-panel stop responding and consumed 100% CPU. An empty dialogbox appeared in screen 1 with title Error. killall gnome-panel brought things back. /var/crash directory is empty. It looks like the application launchers in screen 2 thought they are in screen 1 (if you right-click on the application launcher icon in screen 2 and select properties, the Properties dialog appeared in screen 1). -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
the problem is that crashes is the wrong word, it just doesn't respond anymore. a error window is shown, though this is not being filled with any information(so a empty window with error as the title) /var/crash is therefore empty. though this bug seems to not be there on every bootup. I can't see a pattern until now on when it's there and when not. I am sorry I can't tell more, I will add something/open a new bug as I find out something new. -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit. If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report. I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding. ** Changed in: gnome-panel (Ubuntu) Importance: Undecided = Medium Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs) Status: New = Invalid -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/18222465/Dependencies.txt -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
furthermore I got 3 gnome-panel processes, that are the top 3 CPU consuming processes, being 80% all the time -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278261] Re: two xscreens - gnome panel crashes
after this bug occurs I got another gnome-panel process the 3 CPU consuming processes were active even though the bug described wasn't produced yet btw. A killall gnome-panel results in a normal gnome-panel process that uses nearly no CPU, and the bug described above is not there anymore. Though this bug is there after the next restart. -- two xscreens - gnome panel crashes https://bugs.launchpad.net/bugs/278261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
