rhythmbox freezes on startup when samba share not available

Bug #31122 reported by Alan Claunch
20
Affects Status Importance Assigned to Milestone
Rhythmbox
Expired
Medium
rhythmbox (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

On Dapper (up to date as of 2-10-06) Rhythmbox freezes on startup. No controls work and after several attempts to close, the notification "application is not responding" appears.

Rhythmbox version 0.9.3.1-0ubuntu1

No messages appear if started from the terminal but requires a -HUP to quit.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. Could you get a backtrace when that happens, you can use gdb for that:
- gdb ($pidof rhythmbox)
(gdb) thread apply all bt

Do you have any message if you start if from the command line?

Changed in rhythmbox:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
Alan Claunch (aclaunch) wrote :
Download full text (27.3 KiB)

There are no messages from the command line. Here is the gdb info:

Thread 13 (Thread -1215607888 (LWP 3237)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0x47500eec in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0x47dbf5dc in ?? () from /usr/lib/libgthread-2.0.so.0
#3 0x0835ed30 in ?? ()
#4 0x082923d0 in ?? ()
#5 0xb78b4324 in ?? ()
#6 0x00000004 in ?? ()
#7 0x00000000 in ?? ()

Thread 12 (Thread -1224000592 (LWP 3238)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0x472c6904 in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0x47499658 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#3 0x47499b28 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#4 0x4bde370e in link_thread_io_context () from /usr/lib/libORBit-2.so.0
#5 0x474b24a2 in g_static_private_free () from /usr/lib/libglib-2.0.so.0
#6 0x474fe341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7 0x472d052e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 11 (Thread -1233298512 (LWP 3246)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0x47500c76 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0x4f2a03a0 in gnome_vfs_get_file_mime_type_fast ()
   from /usr/lib/libgnomevfs-2.so.0
#3 0x4f2a13af in gnome_vfs_module_callback_invoke ()
   from /usr/lib/libgnomevfs-2.so.0
#4 0x4f2a00e2 in gnome_vfs_get_file_mime_type_fast ()
   from /usr/lib/libgnomevfs-2.so.0
#5 0x4f28f0e7 in gnome_vfs_daemon_set_current_daemon_client_call ()
   from /usr/lib/libgnomevfs-2.so.0
#6 0x4f28460d in ?? () from /usr/lib/libgnomevfs-2.so.0
#7 0x0853cdbc in ?? ()
#8 0x08558381 in ?? ()
#9 0x0855947c in ?? ()
#10 0xb67d4ea8 in ?? ()
#11 0xb67d5008 in ?? ()
#12 0x0855947c in ?? ()
#13 0xb67d4e38 in ?? ()
#14 0x4bdda42a in ORBit_POA_setup_root () from /usr/lib/libORBit-2.so.0
#15 0x4bdda42a in ORBit_POA_setup_root () from /usr/lib/libORBit-2.so.0
#16 0x4bddef91 in ORBit_OAObject_invoke () from /usr/lib/libORBit-2.so.0
#17 0x4bdcbf64 in ORBit_small_invoke_adaptor () from /usr/lib/libORBit-2.so.0
#18 0x4bdda747 in ORBit_POAObject_post_invoke () from /usr/lib/libORBit-2.so.0
#19 0x4bddadae in ORBit_POAObject_post_invoke () from /usr/lib/libORBit-2.so.0
#20 0x4bdc6761 in giop_thread_queue_process () from /usr/lib/libORBit-2.so.0
#21 0x4bdc852d in giop_recv_buffer_get () from /usr/lib/libORBit-2.so.0
#22 0x4bdcbcc5 in ORBit_small_invoke_stub () from /usr/lib/libORBit-2.so.0
#23 0x4bdcbe96 in ORBit_small_invoke_stub_n () from /usr/lib/libORBit-2.so.0
#24 0x4bddd6be in ORBit_c_stub_invoke () from /usr/lib/libORBit-2.so.0
#25 0x4f285d77 in GNOME_VFS_AsyncDaemon_GetFileInfo ()
   from /usr/lib/libgnomevfs-2.so.0
#26 0x4f29181c in gnome_vfs_daemon_convert_to_corba_file_info ()
   from /usr/lib/libgnomevfs-2.so.0
#27 0x4f28d363 in gnome_vfs_get_file_info_uri_cancellable ()
   from /usr/lib/libgnomevfs-2.so.0
#28 0x4f2976fb in gnome_vfs_job_get_count () from /usr/lib/libgnomevfs-2.so.0
#29 0x4f295deb in gnome_vfs_is_primary_thread ()
   from /usr/lib/libgnomevfs-2.so.0
#30 0x474b4305 in g_thread_pool_free () from /usr/lib/libglib-2.0.so.0
#31 0x474b24a2 in g_static_private_free () from /usr/lib/libglib-2.0.so.0
#32...

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you get a backtrace with libgnomevfs2-0-dbg installed?

Revision history for this message
Alan Claunch (aclaunch) wrote :

This is after libgnomevfs2-0-dbg installed:

(gdb) file rhythmbox
Reading symbols from /usr/bin/rhythmbox...(no debugging symbols found)...done.
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(gdb) thread apply all bt
(gdb) run rhythmbox
Starting program: /usr/bin/rhythmbox rhythmbox
(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)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208502592 (LWP 4666)]
[New Thread -1215710288 (LWP 4674)]
[New Thread -1224102992 (LWP 4675)]
[New Thread -1224553552 (LWP 4678)]
[New Thread -1232946256 (LWP 4679)]
[Thread -1232946256 (LWP 4679) exited]
[Thread -1224553552 (LWP 4678) exited]
[New Thread -1241338960 (LWP 4681)]
[Thread -1241338960 (LWP 4681) exited]
[New Thread -1241338960 (LWP 4683)]
[New Thread -1224553552 (LWP 4686)]
[New Thread -1232946256 (LWP 4687)]
[New Thread -1250579536 (LWP 4689)]
[New Thread -1258972240 (LWP 4691)]
[New Thread -1267364944 (LWP 4693)]
[New Thread -1275757648 (LWP 4696)]
[New Thread -1284150352 (LWP 4698)]
[New Thread -1292543056 (LWP 4700)]
[New Thread -1300935760 (LWP 4702)]

Couldn't get registers: No such process.
(gdb)
Cannot fetch general-purpose registers for thread -1215710288: generic error

Revision history for this message
Sebastien Bacher (seb128) wrote :

The new log has no backtrace, could you try to "gdb -p $(pidof rhythmbox)"? Could you try to run "rhythmbox -d" too and not where it hangs exactly?

Revision history for this message
Alan Claunch (aclaunch) wrote :

Very interesting: if I run "rhythmbox -d" I get a huge output and it all works. Actually I have to run it about 3-4 times and then it works; the first time it starts and then freezes, the second time it gets further and freezes and then it works fine. I tried redirecting the output from "rhythmbox -d" to a file but the times it freezes there is no output. When it finally works there is a huge text output (about 2.5M); I could try to send it to you if you need but I don't know how to attach it to this page. As for the gdb,

aclaunch@moria:~$ gdb rhythmbox
GNU gdb 6.4-debian
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) run 17053
Starting program: /usr/bin/rhythmbox 17053
(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)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 2004526784 (LWP 17133)]
[New Thread 1997278128 (LWP 17141)]
[New Thread 1988885424 (LWP 17142)]
[New Thread 1988434864 (LWP 17150)]
[New Thread 1980042160 (LWP 17152)]
[Thread 1980042160 (LWP 17152) exited]
[Thread 1988434864 (LWP 17150) exited]
[New Thread 1971649456 (LWP 17154)]
[Thread 1971649456 (LWP 17154) exited]
[New Thread 1971649456 (LWP 17156)]
[New Thread 1988434864 (LWP 17159)]
[New Thread 1980042160 (LWP 17160)]
[New Thread 1962408880 (LWP 17161)]
[New Thread 1954016176 (LWP 17162)]
[Thread 1971649456 (LWP 17156) exited]
[Thread 1988434864 (LWP 17159) exited]
[Thread 1980042160 (LWP 17160) exited]
[Thread 1962408880 (LWP 17161) exited]
[Thread 1954016176 (LWP 17162) exited]
[New Thread 1988434864 (LWP 17175)]
[Thread 1988434864 (LWP 17175) exited]
[New Thread 1988434864 (LWP 17194)]
[Thread 1988434864 (LWP 17194) exited]
[New Thread 1962408880 (LWP 17195)]
[Thread 1997278128 (LWP 17141) exited]
[Thread 1962408880 (LWP 17195) exited]
                                                  ((**** My note, I stopped application as it was active and nothing else was happening))

Program exited normally.
Couldn't get registers: No such process.
(gdb)

Alan

Revision history for this message
Alan Claunch (aclaunch) wrote :

I *think* the problem was that I had rhythmbox audio sources on Samba connected drives that were not mounted i.e. rhythmbox starts up, tries to connect to network drive with shared music and hangs at the point of initiating password dialog and Samba connect.As a test I deleted my rhythmbox playlists.xml and rhythmdb.xml files and it started fine; I then added audio sources on my local drive and again it worked fine. I redeleted the xml files and added a Samba mounted drive to the source list and after a while (there are about 2000 songs in the directory) it was added to the list. I then unmounted the Samba volume and restarted rhythmbox and again it was fine. But, I then rebooted and when I restarted rhythmbox it hung/froze presumably trying to connect to the unmounted Samba volume referenced in playlist.xml or rhythmdb.xml.I remounted the Samba volume and restarted rhythmbox and again it found the appropriate playlist and was fine.

Hope this helps. Maybe this is not truly a bug but rather a function of rhythmbox interacting with Samba.

Alan

Revision history for this message
Sebastien Bacher (seb128) wrote :

That's an useful information. I've forwarded the bug upstream: http://bugzilla.gnome.org/show_bug.cgi?id=335476

Changed in rhythmbox:
status: Needs Info → Unconfirmed
Revision history for this message
Hidde Brugmans (hcbrugmans-deactivatedaccount) wrote :

upstream bug notes that improvements have been made in cvs since the last release and asks if you can test with a cvs checkout.

Revision history for this message
xtknight (xt-knight) wrote :

I have the same problem with rhythmbox, even when Samba shares are not mounted. I can stop the service (/etc/init.d/samba stop), and it will still happen. It's not until I disable the samba service in Administration->Services and reboot that the problem is solved.

I don't have music added off of a samba share either. VMware also freezes on File->Open, and I have never added a file off of samba shares to VMware. One time, my GNOME desktop also refused to start. Samba is freezing a lot of apps.

dmesg:
[82755.018586] smb_add_request: request [ffff81000b51fe40, mid=171] timed out!
[82785.102403] smb_add_request: request [ffff81000b51fe40, mid=172] timed out!

NFS seems to have similar problems. "Unmounting remote filesystems..." will freeze at reboot. Occasionally, the samba service will take 20 minutes to init.d restart as well.

Changed in rhythmbox:
status: Needs Info → Rejected
Revision history for this message
Sebastien Bacher (seb128) wrote :

Does anybody has the issue with rhythmbox 0.9.5?

Changed in rhythmbox:
status: Unconfirmed → Needs Info
Revision history for this message
Daniel Holbach (dholbach) wrote :

Your bug lacks information we would need to investigate further. We
are now going to close the bug - please reopen if you have more
information at hand.

Changed in rhythmbox:
status: Needs Info → Rejected
Changed in rhythmbox:
importance: Unknown → Medium
status: Invalid → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.