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 584764 - crash in Workspace Switcher: Opening the workspace ch...
crash in Workspace Switcher: Opening the workspace ch...
Status: RESOLVED DUPLICATE of bug 472773
Product: gnome-panel
Classification: Other
Component: workspace switcher
2.26.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-06-03 19:37 UTC by scott.parkerson
Modified: 2009-06-03 21:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description scott.parkerson 2009-06-03 19:37:15 UTC
Version: 2.26.1

What were you doing when the application crashed?
Opening the workspace chooser preferences.


Distribution: Unknown
Gnome Release: 2.26.1 2009-04-14 (Foresight Linux)
BugBuddy Version: 2.26.0

System: Linux 2.6.29.2-3-fl.smp.gcc4.1.x86.i686 #1 SMP Thu Apr 30 15:18:31 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10601000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Foresight
Icon Theme: Tango
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 72851456 vsize: 72851456 resident: 13901824 share: 10096640 rss: 13901824 rss_rlim: 18446744073709551615
CPU usage: start_time: 1243946271 rtime: 4424 utime: 3974 stime: 450 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6ecc710 (LWP 7274)]
0xb7fdc424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6ecc710 (LWP 7274))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 wncklet_connect_while_alive
    at wncklet.c line 183
  • #8 display_properties_dialog
    at workspace-switcher.c line 997
  • #9 ??
    from /usr/lib/libbonoboui-2.so.0
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
    from /usr/lib/libbonoboui-2.so.0
  • #14 malloc
    from /lib/libc.so.6
  • #15 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #16 bonobo_closure_invoke_va_list
    from /usr/lib/libbonobo-2.so.0
  • #17 bonobo_closure_invoke
    from /usr/lib/libbonobo-2.so.0
  • #18 ??
    from /usr/lib/libbonoboui-2.so.0
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #0 __kernel_vsyscall


---- Critical and fatal warnings logged during execution ----

** Wnck **: wnck_screen_get_workspace_count: assertion `WNCK_IS_SCREEN (screen)' failed 


----------- .xsession-errors (497 sec old) ---------------------
https://twitter.com/statuses/update.json
Response: 200 (https://twitter.com/statuses/update.json)
** (evolution:5188): DEBUG: EI:mail_new_notify
** (evolution:5188): DEBUG: MAIL SERVER: Count changed: 1
** (evolution:5188): DEBUG: EI: mail_read_notify
** (evolution:5188): DEBUG: MAIL SERVER: Count changed: 0
https://twitter.com/statuses/friends_timeline.json
Response: 200 (https://twitter.com/statuses/friends_timeline.json?since_id=2019969373&count=200)
Get 11 tweets
https://twitter.com/statuses/replies.json
Response: 200 (https://twitter.com/statuses/replies.json?since_id=2017835232&count=200)
Get 0 tweets
https://twitter.com/direct_messages.json
Response: 200 (https://twitter.com/direct_messages.json?since_id=151640905&count=200)
Get 0 tweets
--------------------------------------------------
Comment 1 Philip Withnall 2009-06-03 21:14:46 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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