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 377553 - crash in Rhythmbox Music Player: Skipping tracks forward....
crash in Rhythmbox Music Player: Skipping tracks forward....
Status: RESOLVED DUPLICATE of bug 361681
Product: rhythmbox
Classification: Other
Component: general
0.9.6
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
: 380528 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-11-20 22:29 UTC by sonojm
Modified: 2006-12-10 00:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description sonojm 2006-11-20 22:29:26 UTC 
What were you doing when the application crashed?
Skipping tracks forward...


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

Memory status: size: 348622848 vsize: 348622848 resident: 43794432 share: 17174528 rss: 43794432 rss_rlim: -1
CPU usage: start_time: 1164056390 rtime: 70578 utime: 68877 stime: 1701 cutime:8 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47644248380384 (LWP 6780)]
[New Thread 1183111504 (LWP 10305)]
[New Thread 1090525520 (LWP 10303)]
[New Thread 1149540688 (LWP 10302)]
[New Thread 1166326096 (LWP 10280)]
[New Thread 1082132816 (LWP 9769)]
[New Thread 1199896912 (LWP 9767)]
[New Thread 1191504208 (LWP 7695)]
[New Thread 1124362576 (LWP 6810)]
[New Thread 1107310928 (LWP 6803)]
(no debugging symbols found)
0x00002b5505a30eef in waitpid () from /lib/libpthread.so.0

+ Trace 88084

Thread 1 (Thread 47644248380384 (LWP 6780))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib/libc.so.6
  • #4 abort
    from /lib/libc.so.6
  • #5 g_logv
    from /usr/lib64/libglib-2.0.so.0
  • #6 g_log
    from /usr/lib64/libglib-2.0.so.0
  • #7 ??
    from /usr/lib64/libgthread-2.0.so.0
  • #8 gst_audio_sink_get_type
    from /usr/lib64/libgstaudio-0.10.so.0
  • #9 ??
  • #10 g_object_unref
    from /usr/lib64/libgobject-2.0.so.0
  • #11 gst_base_audio_sink_get_type
    from /usr/lib64/libgstaudio-0.10.so.0
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 g_object_unref
    from /usr/lib64/libgobject-2.0.so.0
  • #16 gst_message_new_eos
    from /usr/lib64/libgstreamer-0.10.so.0
  • #17 gst_mini_object_unref
    from /usr/lib64/libgstreamer-0.10.so.0
  • #18 gst_bus_pop
    from /usr/lib64/libgstreamer-0.10.so.0
  • #19 g_main_context_dispatch
    from /usr/lib64/libglib-2.0.so.0
  • #20 g_main_context_check
    from /usr/lib64/libglib-2.0.so.0
  • #21 g_main_loop_run
    from /usr/lib64/libglib-2.0.so.0
  • #22 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #23 main
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


James "Doc" Livingston





          2006-11-21 08:23:28 UTC
        



Is this reproducable? If so, could you run "rhythmbox" from a terminal and see what the assertion message it prints out before crashing is?






Comment 2


André Klapper





          2006-11-30 03:13:41 UTC
        



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






Comment 3


mathias





          2006-11-30 16:55:57 UTC
        



The bug is reproducible. Here are the assertion messages :


** (rhythmbox:8075): CRITICAL **: Resources for ring buffer 0x2aaac8dc4e50 still acquired

GThread-ERROR **: file gthread-posix.c: line 250 (): error 'Périphérique ou ressource occupé' during 'pthread_cond_destroy ((pthread_cond_t *) cond)'
aborting...


In fact, it seems that during the forward skipping, the rhythmbox window is not responding to the system messages (it becomes black & white, sometime colorfull again, and again black & white, untill it's closed), but it's perfectly working. If the forward skip stop soon enough, the operation follows well. But after too long, the system decide to stop the program (it's a supposition, I know nothing of the internal function of this, as I am new to linux) and open the bug buddy window.






Comment 4


James "Doc" Livingston





          2006-12-10 00:32:18 UTC
        




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