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 356210 - crash in Rhythmbox Music Player: Loading my shared music ...
crash in Rhythmbox Music Player: Loading my shared music ...
Status: RESOLVED DUPLICATE of bug 352494
Product: rhythmbox
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-09-16 01:53 UTC by Andrew Conkling
Modified: 2006-09-16 12:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Andrew Conkling 2006-09-16 01:53:00 UTC 
What were you doing when the application crashed?
Loading my shared music over NFS


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 140652544 vsize: 0 resident: 140652544 share: 0 rss: 54996992 rss_rlim: 0
CPU usage: start_time: 1158369114 rtime: 0 utime: 42147 stime: 0 cutime:40577 cstime: 0 timeout: 1570 it_real_value: 0 frequency: 4

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
0xffffe410 in __kernel_vsyscall ()

+ Trace 72452

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 ?? 






Comment 1


Alex Lancaster





          2006-09-16 09:13:13 UTC
        



Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Also, please set the "Version" field, so we know what version of rhythmbox you are running.






Comment 2


Alex Lancaster





          2006-09-16 09:44:27 UTC
        



Is this the same as bug #352494?  If so, that bug is fixed, but you'll need to upgrade to CVS or wait until 0.9.6 is released to see the error. 

If it is in CVS still, you should re-open the old bug, rather than open a new one.






Comment 3


Andrew Conkling





          2006-09-16 12:55:10 UTC
        



OK, that makes sense.  I'm running 0.9.5-1ubuntu5 on Ubuntu Edgy, so I suppose I'm already seeing that bug's fix?

Interesting thing is that I couldn't get any better; this crash is actually making my gdb crash too. O_o

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