Rhythmbox hang during launch

Thanks for your bug report.
Could you please try to obtain a backtrace by following the instructions on http://wiki.ubuntu.com/DebuggingProgramCrash.
This will greatly aid us in tracking down your problem.
Thanks

Hi Carlo,

I have tried to follow the instructions but my bug report is not about a crash. Rhythmbox just hang so it's difficult to capture a backtrace with infos (plus i'm a newbie so i'm not very apt to provide interresting informations).
Anyway hereunder is my gdb-rhythmbox file and i provide a video (animated GIF) with my actions.
You can look at this animated GIF and see Rhythmbox hang (it stop after 1317 tracks but there is more than 5000 tracks in my collection !)

here the animated GIF

The problem is due to libgnomeui, duplicate from #35586

What ?

Bug number #35586 is about opening/previewing multi-layered GIF image !!

This bug (#71208) is about a Rhythmbox freeze when i try to launch it.
I just send a multi-layered GIF as a mean to see my actions during the Rhythmbox launch (the freeze, the kill of Rhythmbox...etc etc).

I'ts a sort of video, a screen recording of my actions, but this GIF have nothing in common with the real bug : Rhythmbox freeze when i launch it !

And on what do you think that rhythmbox is freezing? On the pointed GIF

You can try to run that command:
- gdb --args gst-launch-0.10 -t filesrc location=/path/to/animated/gif ! decodebin ! fakesink

you will notice that it eats CPU too and doesn't print the information about the song. That comment is basically what rhythmbox is doing to get the title, artist, etc on a song. Now try on a normal song, you will see it works fine. Once you have noted it's eating CPU and not working fine you can do <Ctrl-C> on the gdb prompt and then type "thread apply all bt" and look on what's doing, it's using the gdk gif decoder

Does it make sense to you now? If you still disagree could you give some explanation of why?

ah, read the bug too fast, I though it was hanging due to the gif you attached. Could you run rhythmbox -d and note what's it doing when hanging? It's likely it's chocking on some file stored on your disk (like that gif file you attached to the bug)

Haaaa !! It's scary to run Rhythmbox with the -do option !
There is a lot of lines in my terminal.

Here you can see a screenshot of the terminal :

http://static.flickr.com/111/317243391_a94b41904b_o.png

And here you can see another screenshot of the terminal (2 minutes later) :

http://static.flickr.com/122/317243393_5867bc1e64_o.png

As you can see in the first screenshot the process is about the 450th track and in the second screenshot the process is about the 1500th track.
2 minutes for approximatively 1000 tracks !

I recall you that i have 5000 music tracks on my hard disc...does it mean i have to wait 10 minutes for the opening of Rhythmbox ?

Sorry it's the -d option and not the -do option.

rhythmbox should run immediatly and keep updating the library in background. Are your files on a local partition? Does the "hang" go away if you wait for it to load everything?

>> <i>Are your files on a local partition?</i>

Yes. My music files are on /home/patrick/mes_musiques on my laptop hard disc/

>> <i>Does the "hang" go away if you wait for it to load everything?</i>

Yes !!!
I launch Rhythmbox, i wait 9 minutes and 26 seconds and suddenly everything is ok !
I've tried to apt-get remove purge rhythmbox and to reinstall but there is no difference after this try.

This hang seems to be a problem only for me (local problem) so i think i will wait for the feisty release and reinstall my system.

Grrr

correction : the path is /home/patrick/mes_musiques/

on my laptop hard disc

Hello Oliver. Please explain how is this bug the same. patrick_g describes a hang while your backtrace describes a segmentation fault.

marking unconfirmed, probably an upstrem problem to forward by something getting the bug

Very similar problem. Feisty with all updates applied as of 16 March 2007. The music collection is 11,000 MP3s, 80Gb on a Samba share on a Linksys Slug. Rhythmbox hangs during startup when the collection check reaches around either 2048 or 4096 songs. Kill it, Delete the XML files and it then starts fine. Run the scan and it completes. Close down and restart rhythmbox and it again hangs at around the same place. Under Edgy, Rhythmbox managed fine, scanning the same library and restarting fine after the library has been scanned.

On Edgy I had perhaps similar problems with Amarok refusing to fully scan the whole library. Under Feisty this seems to be cured but now Rhythmbox has caught the cold. I wonder if this is all related to libtag (or is it taglib).

I can also reproduce this bug. I'm happy to help provide more info if necessary.

Some additional info. Rhythmbox 0.9.8 up to date Feisty as of 24 Mar 07. 11,000 song lib on samba.

If I click in the artist part of the collection before rhythmbox starts scanning, it starts up correctly. If I leave "All" highlighted, it hangs. I have "Watch my library for new tracks" turned off but Rhythmbox is still accessing the samba share across the network during startup. It's almost as though it's the display of the albums under ALL in the right hand pane which is freezing the startup. Clicking on an artist limits this to a handful whereas ALL tries and fails to display

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Also this report is one that should be reproducable with the live environment of the Desktop CD of the development release - Gutsy Gibbon. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed release. You can find out more about the development release at [WWW] http://www.ubuntu.com/testing/ ; Thanks in advance.

Hi Pedro,

When i test with Gutsy Tribe 4 everything is OK and there is no problem here on my laptop.
At least for me this bug is fixed.

thank you for the update, closing the bug