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 350317 - crash on Rhythmbox Music Player
crash on Rhythmbox Music Player
Status: RESOLVED DUPLICATE of bug 348455
Product: rhythmbox
Classification: Other
Component: general
0.9.5
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-07 18:26 UTC by Timothy Brownawell
Modified: 2006-08-09 09:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Timothy Brownawell 2006-08-07 18:26:28 UTC
What were you doing when the application crashed?
accidental "unsafe device removal" of the external drive that the library is on, while it was playing music from there


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.90 2006-07-24 (Ubuntu)
BugBuddy Version: 2.15.90

Memory status: size: 247980032 vsize: 0 resident: 247980032 share: 0 rss: 62652416 rss_rlim: 0
CPU usage: start_time: 1154887262 rtime: 0 utime: 305430 stime: 0 cutime:284218 cstime: 0 timeout: 21212 it_real_value: 0 frequency: 7

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 -1227405648 (LWP 16117)]
[New Thread -1440928864 (LWP 4028)]
[New Thread -1432536160 (LWP 4027)]
[New Thread -1424143456 (LWP 4026)]
[New Thread -1415750752 (LWP 4025)]
[New Thread -1407358048 (LWP 4024)]
[New Thread -1398965344 (LWP 4023)]
[New Thread -1390572640 (LWP 4022)]
[New Thread -1308673120 (LWP 4021)]
[New Thread -1332151392 (LWP 4020)]
[New Thread -1350636640 (LWP 4019)]
[New Thread -1375814752 (LWP 3923)]
[New Thread -1359029344 (LWP 3921)]
[New Thread -1342243936 (LWP 3198)]
[New Thread -1367422048 (LWP 3121)]
[New Thread -1291859040 (LWP 2975)]
[New Thread -1317065824 (LWP 2949)]
[New Thread -1283466336 (LWP 16378)]
(no debugging symbols found)
0x080db339 in rhythmdb_query_model_reapply_query ()

Thread 14 (Thread -1342243936 (LWP 3198))

  • #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 gst_file_src_get_type
    from /usr/lib/gstreamer-0.10/libgstcoreelements.so
  • #5 gst_base_src_get_type
    from /usr/lib/libgstbase-0.10.so.0
  • #6 gst_base_src_get_type
    from /usr/lib/libgstbase-0.10.so.0
  • #7 gst_pad_get_range
    from /usr/lib/libgstreamer-0.10.so.0
  • #8 gst_pad_pull_range
    from /usr/lib/libgstreamer-0.10.so.0
  • #9 gst_ghost_pad_new_no_target
    from /usr/lib/libgstreamer-0.10.so.0
  • #10 gst_pad_get_range
    from /usr/lib/libgstreamer-0.10.so.0
  • #11 gst_pad_pull_range
    from /usr/lib/libgstreamer-0.10.so.0
  • #12 gst_type_find_element_get_type
    from /usr/lib/gstreamer-0.10/libgstcoreelements.so
  • #13 gst_pad_get_range
    from /usr/lib/libgstreamer-0.10.so.0
  • #14 gst_pad_pull_range
    from /usr/lib/libgstreamer-0.10.so.0
  • #15 gst_ogg_demux_plugin_init
    from /usr/lib/gstreamer-0.10/libgstogg.so
  • #16 gst_task_set_lock
    from /usr/lib/libgstreamer-0.10.so.0
  • #17 g_thread_pool_push
    from /usr/lib/libglib-2.0.so.0
  • #18 g_thread_create_full
    from /usr/lib/libglib-2.0.so.0
  • #19 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #20 clone
    from /lib/tls/i686/cmov/libc.so.6

Comment 1 Alex Lancaster 2006-08-07 19:50:52 UTC
What version were you running?  Can you set the version on the bug?
Comment 2 Timothy Brownawell 2006-08-07 23:42:43 UTC
version is 0.9.5-1ubuntu3
Comment 3 Jonathan Matthew 2006-08-09 09:30:50 UTC
This bug was recently fixed in gstreamer core (not yet in a release).

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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