GNOME Bugzilla – Bug 527666
Crash in applet_scroll at workspace-switcher.c line 259
Last modified: 2020-11-06 20:20:21 UTC
Version: 2.22.1.2 What were you doing when the application crashed? Distribution: Fedora release 8 (Werewolf) Gnome Release: 2.22.1 2008-04-08 (Red Hat, Inc) BugBuddy Version: 2.22.0 System: Linux 2.6.25-0.218.rc8.git7.fc9.i686 #1 SMP Wed Apr 9 20:35:56 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10499901 Selinux: No Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 60420096 vsize: 60420096 resident: 14508032 share: 10469376 rss: 14508032 rss_rlim: 4294967295 CPU usage: start_time: 1207981885 rtime: 36 utime: 29 stime: 7 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/wnck-applet' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb7f7b730 (LWP 8111)] 0x0012e416 in __kernel_vsyscall ()
+ Trace 195010
Thread 1 (Thread 0xb7f7b730 (LWP 8111))
----------- .xsession-errors (169 sec old) --------------------- ** (gsynaptics-init:7964): WARNING **: Using synclient Unknown parameter CoastingSpeedThreshold Initializing nautilus-image-converter extension seahorse nautilus module initialized Connection failure: Connection refused ** (nautilus:7952): WARNING **: Unable to add monitor: Not supported Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. could not attach to desktop process Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2400003 (Google Des) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
*** Bug 528189 has been marked as a duplicate of this bug. ***
*** Bug 534033 has been marked as a duplicate of this bug. ***
*** Bug 531410 has been marked as a duplicate of this bug. ***
*** Bug 595586 has been marked as a duplicate of this bug. ***
*** Bug 595464 has been marked as a duplicate of this bug. ***
*** Bug 603888 has been marked as a duplicate of this bug. ***
*** Bug 609906 has been marked as a duplicate of this bug. ***
*** Bug 613107 has been marked as a duplicate of this bug. ***
bug 613107 has better traces against 2.28.x so reopening the bug
*** Bug 624626 has been marked as a duplicate of this bug. ***
last dupe in 2.30.x
*** Bug 625253 has been marked as a duplicate of this bug. ***
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years. If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-panel/-/issues/ Thank you for reporting this issue and we are sorry it could not be fixed.