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 459353 - crash in Rhythmbox Music Player: Listening music Jamendo
crash in Rhythmbox Music Player: Listening music Jamendo
Status: RESOLVED DUPLICATE of bug 436456
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-22 22:13 UTC by Benjamin Blanco
Modified: 2007-07-24 22:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Benjamin Blanco 2007-07-22 22:13:34 UTC
What were you doing when the application crashed?
Listening to music through Jamendo on Rhythmbox. Just randomly crashes... The music even keeps playing until I close bug buddy. This is on an Inspiron 8100 laptop, in case that's not included in the bug report.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-27.fc7 #1 SMP Tue Jul 17 17:13:26 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Bluecurve

Memory status: size: 342929408 vsize: 342929408 resident: 180592640 share: 33497088 rss: 180592640 rss_rlim: 4294967295
CPU usage: start_time: 1185141612 rtime: 14727 utime: 14051 stime: 676 cutime:7 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 -1209087440 (LWP 4900)]
[New Thread -1374930032 (LWP 6758)]
[New Thread -1364440176 (LWP 6757)]
[New Thread -1353950320 (LWP 6756)]
[New Thread -1234957424 (LWP 6755)]
[New Thread -1332970608 (LWP 6754)]
[New Thread -1260151920 (LWP 6750)]
[New Thread -1387267184 (LWP 6747)]
[New Thread -1247978608 (LWP 4907)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1209087440 (LWP 4900))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 PyErr_Restore
    from /usr/lib/libpython2.5.so.1.0
  • #5 PyErr_Clear
    from /usr/lib/libpython2.5.so.1.0
  • #6 ??
    from /usr/lib/python2.5/site-packages/gtk-2.0/gnomevfs/_gnomevfs.so
  • #7 ??
    from /usr/lib/python2.5/site-packages/gtk-2.0/gnomevfs/_gnomevfs.so
  • #8 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #9 ??
  • #10 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (29 sec old) ---------------------
warning: .dynamic section for "/usr/lib/libgdk-x11-2.0.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libpangocairo-1.0.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libcairo.so.2" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/librsvg-2.so.2" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-07-24 12:15:05 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 436456 ***
Comment 2 Benjamin Blanco 2007-07-24 18:12:41 UTC
(In reply to comment #1)
> 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 436456 ***
> 

Sorry about that, didn't see it before... Seems like a lot of work - keeping up with all those duplicates. Did they all just pop up recently?
Comment 3 Jonathan Matthew 2007-07-24 22:58:02 UTC
Most of the rhythmbox bugs reported in the last few months have been duplicates of bug 436456 and bug 434003.  It doesn't take long to deal with each individual duplicate, but it adds up.  Still, we can't expect people to search bugzilla before submitting an automated crash report, and we'd rather have a pile of duplicates than have new bugs go unreported.