After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 451187 - crash in Show Desktop: Drug the Window title in...
crash in Show Desktop: Drug the Window title in...
Status: RESOLVED DUPLICATE of bug 420713
Product: gnome-panel
Classification: Other
Component: show-desktop-button
2.18.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-26 09:09 UTC by Takanori MATSUURA
Modified: 2007-06-26 09:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Takanori MATSUURA 2007-06-26 09:09:28 UTC 
Version: 2.18.2

What were you doing when the application crashed?
Drug the Window title in wnck applet.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 309719040 vsize: 309719040 resident: 11948032 share: 7942144 rss: 11948032 rss_rlim: 18446744073709551615
CPU usage: start_time: 1182817787 rtime: 530 utime: 450 stime: 80 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/wnck-applet'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496368896 (LWP 25879)]
(no debugging symbols found)
0x0000003d99c0d865 in waitpid () from /lib64/libpthread.so.0

+ Trace 143804

Thread 1 (Thread 46912496368896 (LWP 25879))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_object_unref
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 cairo_rectangle
    from /usr/lib64/libcairo.so.2
  • #4 g_object_unref
    from /usr/lib64/libwnck-1.so.18
  • #5 g_object_unref
    from /usr/lib64/libwnck-1.so.18
  • #6 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #7 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #10 g_object_unref
    from /usr/lib64/libwnck-1.so.18
  • #11 g_object_unref
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #12 g_object_unref
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #13 g_object_unref
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #14 g_object_unref
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #15 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #16 g_object_unref
    from /lib64/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #18 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #19 bonobo_generic_factory_main_timeout
    from /usr/lib64/libbonobo-2.so.0
  • #20 panel_applet_factory_main_closure
    from /usr/lib64/libpanel-applet-2.so.0
  • #21 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors (7045 sec old) ---------------------
Loading x11 FrontEnd module ...
GTK Panel of SCIM 1.4.5
Starting SCIM as daemon ...
SCIM has been successfully launched.
Smart Common Input Method 1.4.5
SESSION_MANAGER=local/sx-lx3.protein.net:/tmp/.ICE-unix/25624
Initializing nautilus-open-terminal extension
ウィンドウ・マネージャの警告: ディスプレイ ':0.0' への接続が切れました。
おそらくＸサーバがシャットダウンしたか、
ウィンドウ・マネージャが強制終了/破棄されたようです。
core: bindWindow(): XGetWindowAttributes() returned non-success.Window: 0x2C03BBB
(gnome-terminal:28513): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
--------------------------------------------------
Comment 1 Vincent Untz 2007-06-26 09:39:38 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 420713 ***