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 494501 - crash in Window Selector:
crash in Window Selector:
Status: RESOLVED DUPLICATE of bug 420713
Product: gnome-panel
Classification: Other
Component: window selector
2.18.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-07 08:47 UTC by swikon
Modified: 2007-11-13 08:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description swikon 2007-11-07 08:47:06 UTC
Version: 2.18.0

What were you doing when the application crashed?
							



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 59539456 vsize: 59539456 resident: 7651328 share: 5013504 rss: 7651328 rss_rlim: 4294967295
CPU usage: start_time: 1194397387 rtime: 2889 utime: 2575 stime: 314 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209051424 (LWP 2618)]
(no debugging symbols found)
0x0062a402 in __kernel_vsyscall ()

Thread 1 (Thread -1209051424 (LWP 2618))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 cairo_rectangle
    from /usr/lib/libcairo.so.2
  • #5 ??
    from /usr/lib/libwnck-1.so.18
  • #6 ??
    from /usr/lib/libwnck-1.so.18
  • #7 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #8 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #9 ??
    from /lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #12 ??
    from /usr/lib/libwnck-1.so.18
  • #13 ??
    from /usr/lib/libwnck-1.so.18
  • #14 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #15 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #16 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #17 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #18 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #19 ??
    from /lib/libglib-2.0.so.0
  • #20 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #21 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #22 bonobo_generic_factory_main_timeout
    from /usr/lib/libbonobo-2.so.0
  • #23 bonobo_generic_factory_main
    from /usr/lib/libbonobo-2.so.0
  • #24 panel_applet_factory_main_closure
    from /usr/lib/libpanel-applet-2.so.0
  • #25 panel_applet_factory_main
    from /usr/lib/libpanel-applet-2.so.0
  • #26 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (21416 sec old) ---------------------
16: 1f 40  0 84 11  3  f 29 
24: 3c 53  d 74 9a 21 3c  d 
32: a5 4c b7 fb 7f 95  f a0 
40: 7c 4e 7d 5b f2 4f  0 81 
48: 26 6d 47 58 b3 2c  1 53 
56:  0  0  0  1  0  0  0  0 
64:  0  0  0  0  0  0  0  0 
72:  0  0  0  0  0  0  0  0 
80:  0  0  0 6b  0 6b  0  0 
88:  0  0  0  1  0  0 26 6d 
96: 7f  0  0  1  0  0  0  0 
104:  0  f a2  0  2  0  0  0 
112: ff  0  1  0  0  0 23  1 
120:  
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Vincent Untz 2007-11-13 08:53:44 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 ***