GNOME Bugzilla – Bug 325034
Don't display extra partitions on ipods
Last modified: 2007-11-18 18:36:31 UTC
Distribution: Ubuntu 5.10 (breezy) Package: rhythmbox Severity: critical Version: GNOME2.12.1 0.9.x Gnome-Distributor: Ubuntu Synopsis: Crash on Startup Bugzilla-Product: rhythmbox Bugzilla-Component: CORBA interface Bugzilla-Version: 0.9.x BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: TAs rhythmbox loads up, a crash occurs. I have my iPod currently connected and I haven't tried to restart my computer. Steps to reproduce the crash: 1. Start rhythmbox Expected Results: Crash forcing rhythmbox to quit How often does this happen? Every time, however, I haven't restarted my computer Additional Information: Debugging Information: 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) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225468224 (LWP 21534)] [New Thread -1235407952 (LWP 21536)] [New Thread -1227015248 (LWP 21535)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 64818
Thread 1 (Thread -1225468224 (LWP 21534))
------- Bug created by bug-buddy at 2005-12-27 02:18 -------
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.
Hi James, I've kinda figured out part of the problem. I had linux on my ipod and it seems that even after I installed it, it left an ext3 partition on it. When I unmount the linux partition from my computer and run rhythmbox the problem doesn't occur anymore. However, if the ext3 partition is mounted rhythmbox crashes. I'll try to get the debug info up if you still think this problem is worth dealing with. I'm planning on maybe just reformatting my ipod anyways. Thanks, James. Josh
Oops installed on my last comment is supposed to say uninstalled. Josh
Getting a backtrace would be very handy. I fairly sure I can guess what the problem is anyway: when using HAL, rb_ipod_is_volume_ipod will return TRUE for every partition on the ipod, not just the one with the DB. It probably shouldn't do this, since we only want to load the one that contains the DB.
Ok I'll get that backtrace and debugging symbols up as soon as I can. I'll even leave the linux partition to see if the crash still occurs after make the changes with rb_ipod_is_volume_ipod.
Hi James, Here's what I got using gdb with bug buddy to get stack traces. I'm not sure if this actually has debugging symbols.
+ Trace 65235
Thread 1 (Thread -1225066816 (LWP 10357))
I'm fairly sure that this has been fixed in cvs by other changes, so shouldn't occur. We shouldn't display sources for volumes with a db, though.
Retitling bug.
Moving to "Removable Media" component.
Josh, is that still happening with CVS HEAD ?
If RB is build against HAL, it uses the result of hal_udi_is_ipod, without checking for the db file. hal_udi_is_ipod simply checks whether the device that is the parent of the volume is an iPod, so extra volumes that are on an iPod (which have no db file) are also detected. Basically, we should look for the db file (or use some libgpod function) even when HAL says it's an ipod.
Created attachment 63547 [details] [review] Look for the iPod database even if we are using HAL This makes the iPod source always tests if an iPod database is available even if hal is used (HAL is only used to filter out non-iPod volumes). We should test for some other file though if we want to be able to support empty iPods.
Looks good. I'm not sure how we want to check for an ipod that has no volumes with a db file.
The DB file is not there when an iPod is empty, but some files are automatically added by the iPod firmware even if they are removed (eg there's a DeviceInfo file or whatever it's named containing the iPod serial number and things like that which is always present from my experience).
I committed that, hopefully that will fix the problem, feel free to reopen if you are still having issues (this has been committed after the 0.9.4 release).
I know this is listed as FIXED. However, I recently added an ext3 partition to my iPod and Rhythmbox is displaying both the vfat partition and the new (currently empty) ext3 partition. This is under v0.9.6, which based on the comments in this thread should have the correction applied.