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 372164 - crash in Rhythmbox Music Player: Swich from FluxBox to Bl...
crash in Rhythmbox Music Player: Swich from FluxBox to Bl...
Status: RESOLVED FIXED
Product: rhythmbox
Classification: Other
Component: general
0.9.6
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
: 399170 416140 (view as bug list)
Depends on: 449858
Blocks:
 
 
Reported: 2006-11-07 20:18 UTC by lorenco
Modified: 2009-06-11 21:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description lorenco 2006-11-07 20:18:00 UTC 
What were you doing when the application crashed?
Swich from FluxBox to BlackBox window manager....


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

Memory status: size: 88764416 vsize: 0 resident: 88764416 share: 0 rss: 25042944 rss_rlim: 0
CPU usage: start_time: 1162930572 rtime: 0 utime: 148 stime: 0 cutime:138 cstime: 0 timeout: 10 it_real_value: 0 frequency: 4

Backtrace was generated from '/usr/bin/rhythmbox'

(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 -1228274000 (LWP 4165)]
[New Thread -1238963296 (LWP 4211)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 84106

Thread 1 (Thread -1228274000 (LWP 4165))

  • #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 gdk_x11_display_get_xdisplay
    from /usr/lib/libgdk-x11-2.0.so.0
  • #5 egg_tray_icon_new_for_screen
  • #6 gdk_x11_drawable_get_xdisplay
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 gdk_events_pending
    from /usr/lib/libgdk-x11-2.0.so.0
  • #8 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #9 _gdk_events_init
    from /usr/lib/libgdk-x11-2.0.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 main
  • #0 __kernel_vsyscall 






Comment 1


Alex Lancaster





          2006-11-07 22:26:27 UTC
        



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. Thanks in advance!







Comment 2


André Klapper





          2006-12-06 00:20:23 UTC
        



Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!







Comment 3


Alex Lancaster





          2007-01-23 12:13:48 UTC
        



*** Bug 399170 has been marked as a duplicate of this bug. ***






Comment 4


Alex Lancaster





          2007-03-08 22:22:19 UTC
        



*** Bug 416140 has been marked as a duplicate of this bug. ***






Comment 5


Alex Lancaster





          2007-03-08 22:22:47 UTC
        



Re-opening because of the presence of dupes.






Comment 6


Alex Lancaster





          2007-03-08 22:23:14 UTC
        



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. Thanks in advance!







Comment 7


Mark Tiefenbruck





          2007-07-08 21:48:09 UTC
        



This is a libegg problem. You can find a patch to fix it in bug #449858.






Comment 8


Christoph Wurm





          2009-06-11 21:45:29 UTC
        



No activity for nearly two years. Last comment indicates a fix has been released. Closing as FIXED.