GNOME Bugzilla – Bug 362217
crash in System Monitor: changing themes .. to "E...
Last modified: 2007-07-19 15:30:04 UTC
Version: 2.16.1 What were you doing when the application crashed? changing themes .. to "Edge" Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 808259584 vsize: 0 resident: 808259584 share: 0 rss: 779055104 rss_rlim: 0 CPU usage: start_time: 1160857012 rtime: 0 utime: 439 stime: 0 cutime:272 cstime: 0 timeout: 167 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-system-monitor' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1224930816 (LWP 7494)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 76340
Thread 1 (Thread -1224930816 (LWP 7494))
*** Bug 364413 has been marked as a duplicate of this bug. ***
*** Bug 364497 has been marked as a duplicate of this bug. ***
Multiple duplicates. Moving state to "NEW".
*** Bug 365594 has been marked as a duplicate of this bug. ***
*** Bug 367193 has been marked as a duplicate of this bug. ***
I have a wild guess that this is because librsvg's RsvgHandle object is now a proper GObject in 2.16, registered via g_type_register_static(). However, the type is ultimately instantiated from a plugin, which would call g_type_module_register_type(). Maybe this is causing wonky-ness. See also bug 357406. CC'ing Tim Janik, since GObject is a black box to me.
I believe that this is fixed in 2.16.1, which should be out shortly.
*** Bug 359889 has been marked as a duplicate of this bug. ***
*** Bug 370595 has been marked as a duplicate of this bug. ***
*** Bug 380638 has been marked as a duplicate of this bug. ***
*** Bug 375849 has been marked as a duplicate of this bug. ***
*** Bug 389221 has been marked as a duplicate of this bug. ***
*** Bug 414380 has been marked as a duplicate of this bug. ***
*** Bug 407537 has been marked as a duplicate of this bug. ***
*** Bug 458024 has been marked as a duplicate of this bug. ***