gtk-window-decorator doesn't start on resuming from suspend

Bug #1027076 reported by Colan Schwartz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Compiz
New
Undecided
Unassigned
compiz (Ubuntu)
New
Undecided
Unassigned

Bug Description

After resuming from suspend, all of my window title bars disappear, and it is not possible to perform any window operations. I have been able to work around this by running "gtk-window-decorator --replace &" in an open terminal to bring everything back.

When reporting this bug, I was asked whether this was a Compiz or Unity problem. I picked Compiz because there wasn't an "I don't know" option. This could be wrong; I really have no idea.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: compiz-gnome 1:0.9.7.8-0ubuntu1.2
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
Uname: Linux 3.2.0-27-generic x86_64
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,move,snap,vpswitch,gnomecompat,place,imgpng,grid,regex,mousepoll,resize,animation,wall,session,workarounds,unitymtgrabhandles,expo,fade,ezoom,scale,unityshell]
Date: Fri Jul 20 09:13:31 2012
DistUpgraded: 2012-05-13 13:05:19,880 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gtk-window-decorator
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 003: ID 5986:0241 Acer, Inc BisonCam, NB Pro
MachineType: System76, Inc. Lemur UltraThin
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-27-generic root=UUID=552496e2-92cc-4e0f-87c0-322edc0cb632 ro quiet splash vt.handoff=7
SourcePackage: compiz
UpgradeStatus: Upgraded to precise on 2012-05-13 (67 days ago)
dmi.bios.date: 11/11/2010
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: CALPELLACRB.86C.0000.X.0000000000
dmi.board.asset.tag: Tag 12345
dmi.board.name: Lemur UltraThin
dmi.board.vendor: System76, Inc.
dmi.board.version: lemu2
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: lemu2
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrCALPELLACRB.86C.0000.X.0000000000:bd11/11/2010:svnSystem76,Inc.:pnLemurUltraThin:pvrlemu2:rvnSystem76,Inc.:rnLemurUltraThin:rvrlemu2:cvnSystem76,Inc.:ct10:cvrlemu2:
dmi.product.name: Lemur UltraThin
dmi.product.version: lemu2
dmi.sys.vendor: System76, Inc.
version.compiz: compiz 1:0.9.7.8-0ubuntu1.2
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2

Revision history for this message
Colan Schwartz (colan) wrote :
tags: added: compiz-0.9
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Could you please try getting a stack trace so we can know the offending region of code? To get a stack trace...

1. env DISPLAY=:0 gdb /usr/bin/gtk-window-decorator
2. (gdb) break _exit
3. (gdb) run --sync --replace
4. Trigger the bug.
5. (gdb) bt
6. Copy the output from gdb and paste it here.

Changed in compiz (Ubuntu):
status: New → Incomplete
Changed in compiz:
status: New → Incomplete
Revision history for this message
Colan Schwartz (colan) wrote :

The "env DISPLAY=:0" didn't work from Terminator so I dropped it:

colan@crane[Mon 23 1:19]% gdb /usr/bin/gtk-window-decorator
GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2) 7.4-2012.04
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.launchpad.net/gdb-linaro/>...
Reading symbols from /usr/bin/gtk-window-decorator...(no debugging symbols found)...done.
(gdb) break _exit
Function "_exit" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y

Breakpoint 1 (_exit) pending.
(gdb) run --sync --replace
Starting program: /usr/bin/gtk-window-decorator --sync --replace
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffef5c1700 (LWP 4324)]
[New Thread 0x7fffedd4f700 (LWP 4325)]
[New Thread 0x7fffe76e0700 (LWP 4326)]
The program 'gtk-window-decorator' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 28225 error_code 3 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.)

Breakpoint 1, 0x00007ffff507f3d0 in _exit () from /lib/x86_64-linux-gnu/libc.so.6

Changed in compiz:
status: Incomplete → New
Changed in compiz (Ubuntu):
status: Incomplete → New
Revision history for this message
Colan Schwartz (colan) wrote :

(gdb) bt
#0 0x00007ffff507f3d0 in _exit () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007ffff4ffc980 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#2 0x00007ffff4ffc9a5 in exit () from /lib/x86_64-linux-gnu/libc.so.6
#3 0x00007ffff6bcb75e in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
#4 0x00007ffff76d336f in _XError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#5 0x00007ffff76d0311 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#6 0x00007ffff76d1297 in _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#7 0x00007ffff76b6ec4 in XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#8 0x0000000000416ff5 in get_frame_type ()
#9 0x0000000000414478 in event_filter_func ()
#10 0x00007ffff6bc1e26 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
#11 0x00007ffff6bc3bd6 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
#12 0x00007ffff6bc3c7e in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
#13 0x00007ffff5b16d53 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007ffff5b170a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007ffff5b1749a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007ffff6f4e2f7 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#17 0x000000000040ad50 in main ()

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1019337, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.