GNOME Bugzilla – Bug 354559
crash in sexy_tree_view_new (show_tooltip at sexy-tree-view.c:281)
Last modified: 2008-07-18 12:22:07 UTC
Version: 2.15.91 What were you doing when the application crashed? Trying to use visualizations in amarok 1.4.2 Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 75362304 vsize: 0 resident: 75362304 share: 0 rss: 16080896 rss_rlim: 0 CPU usage: start_time: 1157514344 rtime: 0 utime: 2962 stime: 0 cutime:1348 cstime: 0 timeout: 1614 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 -1224956240 (LWP 29815)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 71700
Thread 1 (Thread -1224956240 (LWP 29815))
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Could you please start gnome-system-monitor in a terminal like this : $ GNOME_SYSTEM_MONITOR_DEBUG= gnome-system-monitor Thanks.
*** Bug 360816 has been marked as a duplicate of this bug. ***
*** Bug 360913 has been marked as a duplicate of this bug. ***
*** Bug 364436 has been marked as a duplicate of this bug. ***
*** Bug 365693 has been marked as a duplicate of this bug. ***
*** Bug 365961 has been marked as a duplicate of this bug. ***
*** Bug 365964 has been marked as a duplicate of this bug. ***
*** Bug 366127 has been marked as a duplicate of this bug. ***
As i recall it, xine was freezed - maybe because of a faulty video stream (I record DVB-T and sometimes the BER gets too high). I then tried to kill xine with pkill xine and killall xine, without success. After that i started the System Monitor and killed xine. That did go well, but then the bugtracer showed up. Hope that helped. Many greetings. /A
*** Bug 366465 has been marked as a duplicate of this bug. ***
*** Bug 367974 has been marked as a duplicate of this bug. ***
*** Bug 368724 has been marked as a duplicate of this bug. ***
*** Bug 370472 has been marked as a duplicate of this bug. ***
*** Bug 370603 has been marked as a duplicate of this bug. ***
*** Bug 370631 has been marked as a duplicate of this bug. ***
*** Bug 370854 has been marked as a duplicate of this bug. ***
*** Bug 371891 has been marked as a duplicate of this bug. ***
*** Bug 372701 has been marked as a duplicate of this bug. ***
*** Bug 372633 has been marked as a duplicate of this bug. ***
*** Bug 373394 has been marked as a duplicate of this bug. ***
*** Bug 374280 has been marked as a duplicate of this bug. ***
*** Bug 374392 has been marked as a duplicate of this bug. ***
For the record, system-monitor code is : model = gtk_tree_store_new (NUM_COLUMNS, G_TYPE_STRING, /* Process Name */ G_TYPE_STRING, /* User */ G_TYPE_STRING, /* Status */ G_TYPE_STRING, /* VM Size */ G_TYPE_STRING, /* Resident Memory */ G_TYPE_STRING, /* Writable Memory */ G_TYPE_STRING, /* Shared Memory */ G_TYPE_STRING, /* X Server Memory */ G_TYPE_UINT, /* % CPU */ G_TYPE_STRING, /* CPU time */ G_TYPE_STRING, /* Started */ G_TYPE_INT, /* Nice */ G_TYPE_UINT, /* ID */ G_TYPE_STRING, /* Security Context */ G_TYPE_STRING, /* Arguments */ G_TYPE_STRING, /* Memory */ GDK_TYPE_PIXBUF, /* Icon */ G_TYPE_POINTER, /* ProcInfo */ G_TYPE_STRING /* Sexy tooltip */ ); proctree = create_proctree(GTK_TREE_MODEL(model)); -> static GtkWidget * create_proctree(GtkTreeModel *model) { GtkWidget *proctree; GtkWidget* (*new)(void); void (*set_column)(void*, guint); if (load_symbols("libsexy.so", "sexy_tree_view_new", &new, "sexy_tree_view_set_tooltip_label_column", &set_column, NULL)) { proctree = new(); gtk_tree_view_set_model(GTK_TREE_VIEW(proctree), model); set_column(proctree, COL_TOOLTIP); } else { proctree = gtk_tree_view_new_with_model(model); } return proctree; }
*** Bug 375896 has been marked as a duplicate of this bug. ***
Moving to sexy, trying to get some help. Attached stacktraces are not very usefull. bugbuddy doesn't even tell us the signal type that made system-monitor halt (segfault, sigill, sigfpe ?)
*** Bug 376327 has been marked as a duplicate of this bug. ***
*** Bug 376464 has been marked as a duplicate of this bug. ***
*** Bug 376887 has been marked as a duplicate of this bug. ***
*** Bug 376890 has been marked as a duplicate of this bug. ***
*** Bug 376900 has been marked as a duplicate of this bug. ***
*** Bug 377336 has been marked as a duplicate of this bug. ***
*** Bug 377967 has been marked as a duplicate of this bug. ***
*** Bug 378302 has been marked as a duplicate of this bug. ***
*** Bug 378444 has been marked as a duplicate of this bug. ***
*** Bug 378688 has been marked as a duplicate of this bug. ***
*** Bug 379124 has been marked as a duplicate of this bug. ***
*** Bug 379076 has been marked as a duplicate of this bug. ***
*** Bug 379005 has been marked as a duplicate of this bug. ***
*** Bug 379306 has been marked as a duplicate of this bug. ***
*** Bug 379375 has been marked as a duplicate of this bug. ***
*** Bug 379606 has been marked as a duplicate of this bug. ***
*** Bug 379648 has been marked as a duplicate of this bug. ***
is there anyone who cares about libsexy ? else i just drop it in next.
*** Bug 379910 has been marked as a duplicate of this bug. ***
*** Bug 380290 has been marked as a duplicate of this bug. ***
*** Bug 380725 has been marked as a duplicate of this bug. ***
*** Bug 381597 has been marked as a duplicate of this bug. ***
*** Bug 381550 has been marked as a duplicate of this bug. ***
*** Bug 381835 has been marked as a duplicate of this bug. ***
*** Bug 382135 has been marked as a duplicate of this bug. ***
*** Bug 382342 has been marked as a duplicate of this bug. ***
*** Bug 382454 has been marked as a duplicate of this bug. ***
*** Bug 382873 has been marked as a duplicate of this bug. ***
*** Bug 383579 has been marked as a duplicate of this bug. ***
*** Bug 384565 has been marked as a duplicate of this bug. ***
*** Bug 385469 has been marked as a duplicate of this bug. ***
*** Bug 384594 has been marked as a duplicate of this bug. ***
*** Bug 386645 has been marked as a duplicate of this bug. ***
*** Bug 387053 has been marked as a duplicate of this bug. ***
*** Bug 387382 has been marked as a duplicate of this bug. ***
*** Bug 387747 has been marked as a duplicate of this bug. ***
*** Bug 388064 has been marked as a duplicate of this bug. ***
*** Bug 388239 has been marked as a duplicate of this bug. ***
*** Bug 388446 has been marked as a duplicate of this bug. ***
*** Bug 388559 has been marked as a duplicate of this bug. ***
*** Bug 388793 has been marked as a duplicate of this bug. ***
*** Bug 389127 has been marked as a duplicate of this bug. ***
*** Bug 389403 has been marked as a duplicate of this bug. ***
*** Bug 389596 has been marked as a duplicate of this bug. ***
*** Bug 390550 has been marked as a duplicate of this bug. ***
*** Bug 390582 has been marked as a duplicate of this bug. ***
*** Bug 390897 has been marked as a duplicate of this bug. ***
*** Bug 391037 has been marked as a duplicate of this bug. ***
*** Bug 391129 has been marked as a duplicate of this bug. ***
*** Bug 391774 has been marked as a duplicate of this bug. ***
*** Bug 392168 has been marked as a duplicate of this bug. ***
*** Bug 393656 has been marked as a duplicate of this bug. ***
*** Bug 394064 has been marked as a duplicate of this bug. ***
*** Bug 394085 has been marked as a duplicate of this bug. ***
*** Bug 394671 has been marked as a duplicate of this bug. ***
*** Bug 395949 has been marked as a duplicate of this bug. ***
*** Bug 395991 has been marked as a duplicate of this bug. ***
*** Bug 397486 has been marked as a duplicate of this bug. ***
*** Bug 396168 has been marked as a duplicate of this bug. ***
*** Bug 399201 has been marked as a duplicate of this bug. ***
*** Bug 388894 has been marked as a duplicate of this bug. ***
*** Bug 399407 has been marked as a duplicate of this bug. ***
*** Bug 399819 has been marked as a duplicate of this bug. ***
*** Bug 400456 has been marked as a duplicate of this bug. ***
*** Bug 400531 has been marked as a duplicate of this bug. ***
*** Bug 400884 has been marked as a duplicate of this bug. ***
*** Bug 401169 has been marked as a duplicate of this bug. ***
*** Bug 401242 has been marked as a duplicate of this bug. ***
*** Bug 401400 has been marked as a duplicate of this bug. ***
*** Bug 400376 has been marked as a duplicate of this bug. ***
*** Bug 401422 has been marked as a duplicate of this bug. ***
*** Bug 401455 has been marked as a duplicate of this bug. ***
*** Bug 402241 has been marked as a duplicate of this bug. ***
*** Bug 402407 has been marked as a duplicate of this bug. ***
*** Bug 402451 has been marked as a duplicate of this bug. ***
I am not quite sure, but it looks like the registration of a new Gtype (here sexy_tree_view_get_type()) is not allowed in a plugin (if dependent on an shared parent). my first 2 cents
*** Bug 403693 has been marked as a duplicate of this bug. ***
*** Bug 403919 has been marked as a duplicate of this bug. ***
*** Bug 404406 has been marked as a duplicate of this bug. ***
*** Bug 404528 has been marked as a duplicate of this bug. ***
*** Bug 405191 has been marked as a duplicate of this bug. ***
*** Bug 405919 has been marked as a duplicate of this bug. ***
*** Bug 406151 has been marked as a duplicate of this bug. ***
*** Bug 406187 has been marked as a duplicate of this bug. ***
*** Bug 404140 has been marked as a duplicate of this bug. ***
*** Bug 407664 has been marked as a duplicate of this bug. ***
*** Bug 408730 has been marked as a duplicate of this bug. ***
*** Bug 408890 has been marked as a duplicate of this bug. ***
*** Bug 408893 has been marked as a duplicate of this bug. ***
*** Bug 409998 has been marked as a duplicate of this bug. ***
*** Bug 410099 has been marked as a duplicate of this bug. ***
*** Bug 410236 has been marked as a duplicate of this bug. ***
*** Bug 410376 has been marked as a duplicate of this bug. ***
*** Bug 407164 has been marked as a duplicate of this bug. ***
*** Bug 410809 has been marked as a duplicate of this bug. ***
*** Bug 411036 has been marked as a duplicate of this bug. ***
benoit (comment #43): dropping seems adequate. :-/ will try to poke the maintainers directly to get some feedback...
*** Bug 411258 has been marked as a duplicate of this bug. ***
Dear reporters, unfortunately, the provided stack traces are missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some additional debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance for helping to get this bug fixed! [1] Please install the following debug packages: Ubuntu 6.10: libgtk2.0-0-dbg, libglib2.0-0-dbg, and libsexy2-dbgsym (available at http://people.ubuntu.com/~pitti/ddebs/pool/main/ ) Fedora Core 6: gtk2-debuginfo, glib2-debuginfo, and libsexy-debuginfo. OpenSuSE 10.2: gtk2-debuginfo, glib2-debuginfo, and libsexy-debuginfo, all available at http://download.opensuse.org/distribution/10.2/repo/debug/suse/i586/. More details can be found here: http://live.gnome.org/GettingTraces
*** Bug 411669 has been marked as a duplicate of this bug. ***
*** Bug 411679 has been marked as a duplicate of this bug. ***
*** Bug 411760 has been marked as a duplicate of this bug. ***
*** Bug 412307 has been marked as a duplicate of this bug. ***
*** Bug 411967 has been marked as a duplicate of this bug. ***
*** Bug 412057 has been marked as a duplicate of this bug. ***
*** Bug 412389 has been marked as a duplicate of this bug. ***
*** Bug 413439 has been marked as a duplicate of this bug. ***
*** Bug 413531 has been marked as a duplicate of this bug. ***
*** Bug 413684 has been marked as a duplicate of this bug. ***
*** Bug 412998 has been marked as a duplicate of this bug. ***
*** Bug 414337 has been marked as a duplicate of this bug. ***
*** Bug 414754 has been marked as a duplicate of this bug. ***
*** Bug 407198 has been marked as a duplicate of this bug. ***
*** Bug 415434 has been marked as a duplicate of this bug. ***
*** Bug 415831 has been marked as a duplicate of this bug. ***
*** Bug 415918 has been marked as a duplicate of this bug. ***
*** Bug 416395 has been marked as a duplicate of this bug. ***
*** Bug 416095 has been marked as a duplicate of this bug. ***
*** Bug 416232 has been marked as a duplicate of this bug. ***
*** Bug 416676 has been marked as a duplicate of this bug. ***
Using Ubuntu 6.10, I installed the two debug packages mentioned above that were in the official repositories (libgtk2.0-0-dbg, libglib2.0-0-dbg). However, when I tried to install libsexy2-dbgsym from the website given, I got the following error: dpkg: dependency problems prevent configuration of libsexy2-dbgsym: libsexy2-dbgsym depends on libsexy2 (= 0.1.10-1ubuntu2); however: Version of libsexy2 on system is 0.1.10-0ubuntu2. I assume that this is a simple naming error, so I will uncompress it to the correct place and try to reproduce the crash. I don't think I will be able to, since I wasn't doing anything specific, but I'll try my best.
Hi a_aijazi, thanks for your feedback. The error you get when you try to install is because the -dbgsym package is for a different version of the libsexy2 package (-1ubuntu2, instead of -0ubuntu2 which is installed). You probably just have to upgrade the libsexy2 package. If there are no updates available, please complain to Ubuntu. Hope this helps.
*** Bug 417474 has been marked as a duplicate of this bug. ***
*** Bug 417499 has been marked as a duplicate of this bug. ***
*** Bug 418317 has been marked as a duplicate of this bug. ***
*** Bug 418489 has been marked as a duplicate of this bug. ***
*** Bug 418783 has been marked as a duplicate of this bug. ***
*** Bug 418794 has been marked as a duplicate of this bug. ***
*** Bug 418938 has been marked as a duplicate of this bug. ***
*** Bug 418865 has been marked as a duplicate of this bug. ***
*** Bug 419319 has been marked as a duplicate of this bug. ***
*** Bug 419398 has been marked as a duplicate of this bug. ***
*** Bug 421558 has been marked as a duplicate of this bug. ***
*** Bug 421623 has been marked as a duplicate of this bug. ***
*** Bug 421636 has been marked as a duplicate of this bug. ***
*** Bug 423371 has been marked as a duplicate of this bug. ***
*** Bug 423967 has been marked as a duplicate of this bug. ***
I don't really know what's going on here, but comment #101 sounds like a good lead. Does it crash if you link with libsexy as a build-time dependency rather than dlopening it?
*** Bug 427435 has been marked as a duplicate of this bug. ***
*** Bug 427498 has been marked as a duplicate of this bug. ***
*** Bug 427686 has been marked as a duplicate of this bug. ***
before this, my computer always stuck when i use it...then when i change my usb port mouse to ps2 port mouse...its not happen again. i think maybe this bug are related to usb port mouse
*** Bug 428070 has been marked as a duplicate of this bug. ***
*** Bug 428243 has been marked as a duplicate of this bug. ***
*** Bug 428815 has been marked as a duplicate of this bug. ***
*** Bug 429334 has been marked as a duplicate of this bug. ***
*** Bug 429759 has been marked as a duplicate of this bug. ***
*** Bug 429579 has been marked as a duplicate of this bug. ***
*** Bug 430507 has been marked as a duplicate of this bug. ***
*** Bug 430631 has been marked as a duplicate of this bug. ***
*** Bug 430641 has been marked as a duplicate of this bug. ***
*** Bug 431392 has been marked as a duplicate of this bug. ***
*** Bug 431348 has been marked as a duplicate of this bug. ***
*** Bug 431724 has been marked as a duplicate of this bug. ***
*** Bug 432041 has been marked as a duplicate of this bug. ***
*** Bug 432178 has been marked as a duplicate of this bug. ***
*** Bug 432834 has been marked as a duplicate of this bug. ***
*** Bug 432852 has been marked as a duplicate of this bug. ***
*** Bug 433848 has been marked as a duplicate of this bug. ***
*** Bug 434249 has been marked as a duplicate of this bug. ***
*** Bug 434331 has been marked as a duplicate of this bug. ***
*** Bug 434722 has been marked as a duplicate of this bug. ***
*** Bug 434934 has been marked as a duplicate of this bug. ***
*** Bug 435699 has been marked as a duplicate of this bug. ***
*** Bug 436896 has been marked as a duplicate of this bug. ***
*** Bug 437106 has been marked as a duplicate of this bug. ***
*** Bug 421763 has been marked as a duplicate of this bug. ***
*** Bug 422807 has been marked as a duplicate of this bug. ***
*** Bug 422836 has been marked as a duplicate of this bug. ***
*** Bug 422840 has been marked as a duplicate of this bug. ***
*** Bug 423899 has been marked as a duplicate of this bug. ***
*** Bug 424297 has been marked as a duplicate of this bug. ***
*** Bug 426287 has been marked as a duplicate of this bug. ***
*** Bug 432428 has been marked as a duplicate of this bug. ***
(In reply to comment #163) > I don't really know what's going on here, but comment #101 sounds like a good > lead. Does it crash if you link with libsexy as a build-time dependency rather > than dlopening it? > 1) it would be really nice to have some instructions to reproduce the bug - personnaly I never could reproduce it. 2) regarding GObject types registragition, let's involve an "expert"! Tim, could you please help us to avoid another 200 bugs in the next 6 months here? Furthermore, that would be helpful to anyone that use shared object using GObject without any further consideration. thanks!
(In reply to comment #201) > (In reply to comment #163) > > I don't really know what's going on here, but comment #101 sounds like a good > > lead. Does it crash if you link with libsexy as a build-time dependency rather > > than dlopening it? > > > > 1) it would be really nice to have some instructions to reproduce the bug - > personnaly I never could reproduce it. you have dozens of duplicates here, try to get a reproduction description out of only *one* of the reporters. > 2) regarding GObject types registragition, let's involve an "expert"! > > Tim, could you please help us to avoid another 200 bugs in the next 6 months > here? i don't think there's any generic GObject help i could give here. however looking at some of the reports, you should try to nail and fix the warnings from Bug 372633, then the bug flood most probably will stop (i.e. glib is already telling you what went wrong). > Furthermore, that would be helpful to anyone that use shared object using > GObject without any further consideration. that sounds like you're looking for general advice on writing shared modules, for that, see: http://www.imendio.com/files/guadec2006/Mitch-GModule.pdf
Nevertheless it would still be great to get a better stacktrace with debug symbols from one of the reporters here. Could anybody please install some additional debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance for helping to get this bug fixed! [1] Please install the following debug packages: Ubuntu 6.10: libgtk2.0-0-dbg, libglib2.0-0-dbg, and libsexy2-dbgsym (available at http://people.ubuntu.com/~pitti/ddebs/pool/main/ ) Fedora Core 6: gtk2-debuginfo, glib2-debuginfo, and libsexy-debuginfo. OpenSuSE 10.2: gtk2-debuginfo, glib2-debuginfo, and libsexy-debuginfo, all available at http://download.opensuse.org/distribution/10.2/repo/debug/suse/i586/. More details can be found here: http://live.gnome.org/GettingTraces
*** Bug 445759 has been marked as a duplicate of this bug. ***
*** Bug 446834 has been marked as a duplicate of this bug. ***
*** Bug 441065 has been marked as a duplicate of this bug. ***
*** Bug 395391 has been marked as a duplicate of this bug. ***
*** Bug 433524 has been marked as a duplicate of this bug. ***
*** Bug 429681 has been marked as a duplicate of this bug. ***
dear libsexy maintainers, a nice trace from bug 433524:
+ Trace 142409
*** Bug 419140 has been marked as a duplicate of this bug. ***
*** Bug 370735 has been marked as a duplicate of this bug. ***
gtk_tree_model_get(model, &iter, tree_view->priv->tip_label_column, &text, -1); less dups, but nevertheless not fixed in trunk (if http://osiris.chipx86.com/svn/osiris-misc/ lists the trunk).
*** Bug 461964 has been marked as a duplicate of this bug. ***
*** Bug 464109 has been marked as a duplicate of this bug. ***
*** Bug 471382 has been marked as a duplicate of this bug. ***
*** Bug 473642 has been marked as a duplicate of this bug. ***
*** Bug 480150 has been marked as a duplicate of this bug. ***
*** Bug 479215 has been marked as a duplicate of this bug. ***
No duplicate so far. closing as OBSOLETE
No duplicate since system-monitor no longer uses libsexy.