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 396355 - crash in Rhythmbox Music Player: Launching after ripping ...
crash in Rhythmbox Music Player: Launching after ripping ...
Status: RESOLVED DUPLICATE of bug 359083
Product: rhythmbox
Classification: Other
Component: general
0.9.7
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-14 08:48 UTC by Kirk Bridger
Modified: 2007-01-30 09:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Kirk Bridger 2007-01-14 08:48:37 UTC 
What were you doing when the application crashed?
Launching after ripping a CD which resulted in two missing files


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

Memory status: size: 259469312 vsize: 259469312 resident: 53633024 share: 18137088 rss: 53633024 rss_rlim: -1
CPU usage: start_time: 1168764466 rtime: 525 utime: 434 stime: 91 cutime:4 cstime: 0 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 47083225887712 (LWP 24540)]
[New Thread 1124362576 (LWP 24569)]
[New Thread 1115703632 (LWP 24557)]
(no debugging symbols found)
0x00002ad266172eef in waitpid () from /lib/libpthread.so.0

+ Trace 101979

Thread 1 (Thread 47083225887712 (LWP 24540))

  • #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 g_assert_warning
    from /usr/lib64/libglib-2.0.so.0
  • #8 rhythmdb_property_model_new
  • #9 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #10 g_signal_chain_from_overridden
    from /usr/lib64/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #13 rhythmdb_query_model_new
  • #14 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #15 g_signal_chain_from_overridden
    from /usr/lib64/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #18 g_hash_table_foreach
    from /usr/lib64/libglib-2.0.so.0
  • #19 rhythmdb_load
  • #20 rhythmdb_shutdown
  • #21 g_source_get_current_time
    from /usr/lib64/libglib-2.0.so.0
  • #22 g_main_context_dispatch
    from /usr/lib64/libglib-2.0.so.0
  • #23 g_main_context_check
    from /usr/lib64/libglib-2.0.so.0
  • #24 g_main_loop_run
    from /usr/lib64/libglib-2.0.so.0
  • #25 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #26 main
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


Jonathan Matthew





          2007-01-14 21:41: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


Kirk Bridger





          2007-01-18 06:09:15 UTC
        



Sorry to report that the repository I'm using to get the latest version of RB (Janvitus AMD64 repo) doesn't include the dbg version of the application.  So I'm unable to install rhythmbox-dbg (it is an older version and thinks the newer RB version is actually too old and thus has no install candidate.

Unless there were some other debugging packages you wanted me to try, I'm afraid this might have to be closed?






Comment 3


Alex Lancaster





          2007-01-30 09:20:19 UTC
        



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 359083 ***