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 415918 - crash in System Monitor: Listening to an MP3. Se...
crash in System Monitor: Listening to an MP3. Se...
Status: RESOLVED DUPLICATE of bug 354559
Product: system-monitor
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-08 02:20 UTC by thebillywayne
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description thebillywayne 2007-03-08 02:20:36 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Listening to an MP3.  Selected "Twice as Big" or similar from Options menu.  Player disappeared.  Had to shut down with System Monitor.



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 36724736 vsize: 0 resident: 36724736 share: 0 rss: 14573568 rss_rlim: 0
CPU usage: start_time: 1173320348 rtime: 0 utime: 124 stime: 0 cutime:102 cstime: 0 timeout: 22 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 -1225659904 (LWP 10570)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 116771

Thread 1 (Thread -1225659904 (LWP 10570))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gtk_tree_model_get_valist
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 gtk_tree_model_get
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 sexy_tree_view_new
    from /usr/lib/libsexy.so.2
  • #7 g_source_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 ??
  • #13 ??
  • #14 _IO_stdin_used
  • #15 ??
  • #16 ??
  • #17 ??
  • #0 __kernel_vsyscall 






Comment 1


thebillywayne





          2007-03-08 02:42:23 UTC
        



This bug report makes it appear as though it is the system monitor that had the bug.  It isn't.  It is XMMS.  I closed XMMS with the System Monitor and the Bug Report application appeared.  The bug is not with the System Monitor.  That works fine.  The bug is with XMMS.  






Comment 2


Susana





          2007-03-09 12:26:43 UTC
        



Thanks for taking the time to report this bug.

Sounds like you're having two different bugs. If you had a bug in XMMS than please report that to the XMMS bug tracker. This report is about a crash in gnome-system-monitor due to a problem in libsexy.

This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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