GNOME Bugzilla – Bug 443136
crash in Rhythmbox Music Player: I was trying to import m...
Last modified: 2007-06-03 10:43:59 UTC
What were you doing when the application crashed? I was trying to import my music into the rhythmbox library Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 111538176 vsize: 111538176 resident: 31674368 share: 16363520 rss: 31674368 rss_rlim: 4294967295 CPU usage: start_time: 1180764087 rtime: 473 utime: 439 stime: 34 cutime:2 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 -1208538576 (LWP 3888)] [New Thread -1287103600 (LWP 3941)] [New Thread -1297593456 (LWP 3938)] [New Thread -1266123888 (LWP 3927)] [New Thread -1245144176 (LWP 3897)] (no debugging symbols found) 0x0074f402 in __kernel_vsyscall ()
+ Trace 137443
Thread 2 (Thread -1287103600 (LWP 3941))
----------- .xsession-errors (178 sec old) --------------------- LIMIT 1' Executing reader on sql ' SELECT * FROM Tracks WHERE Uri = :uri OR TrackID = :uri LIMIT 1' Executing reader on sql 'INSERT INTO Tracks (TrackID, Uri, MimeType, Artist, Performer, AlbumTitle, ASIN, Label, Title, Genre, Year, DateAddedStamp, TrackNumber, TrackCount, Duration, Rating, NumberOf Executing reader on sql ' SELECT TrackID FROM Tracks WHERE Uri = :uri LIMIT 1' ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 434003 ***