Rhythmbox freezes when changing track information.

Bug #121948 reported by encompass
4
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: rhythmbox

I right click and go to properties of a file...
then delete the genre which is "3" and put that number in the track area.
I click forward to go to the next track... (Close does the same error)
The window does not move to the new information.
The information does not ever change.
And rhythmbox crashes and needs to be killed.

I get a similar feeling when I do this...
Open the properties of a song..
close the window without changing any data
open the properties of another file...
same crash...

I have tried on only ogg files for now.

I got this information, but I don't think this is very useful... what can I do to help a little more...
=============================================================================
======================Debug - - - - =============================================
=============================================================================
skunkyjay@essence:~$ gdb rhythmbox
GNU gdb 6.6-debian
Copyright (C) 2006 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) rhythmbox
Undefined command: "rhythmbox". Try "help".
(gdb) run
Starting program: /usr/bin/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)
[Thread debugging using libthread_db enabled]
[New Thread -1230354736 (LWP 7026)]
(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)
(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)
(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)
(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)
[New Thread -1246008432 (LWP 7032)]
[New Thread -1254401136 (LWP 7033)]
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(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)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread -1246008432 (LWP 7032) exited]
[Thread -1254401136 (LWP 7033) exited]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

(rhythmbox:7026): Rhythmbox-WARNING **: Unable to start mDNS browsing: MDNS service is not running
(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)
[New Thread -1254401136 (LWP 7034)]
[New Thread -1246008432 (LWP 7035)]
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread -1272775792 (LWP 7036)]
[Thread -1254401136 (LWP 7034) exited]
[Thread -1246008432 (LWP 7035) exited]
[Thread -1272775792 (LWP 7036) exited]
[New Thread -1272775792 (LWP 7037)]
[New Thread -1246008432 (LWP 7038)]
[New Thread -1254401136 (LWP 7039)]
[New Thread -1285555312 (LWP 7040)]
[New Thread -1293948016 (LWP 7041)]
[Thread -1272775792 (LWP 7037) exited]
[Thread -1246008432 (LWP 7038) exited]
[Thread -1254401136 (LWP 7039) exited]
[Thread -1293948016 (LWP 7041) exited]
[New Thread -1293948016 (LWP 7045)]
[New Thread -1254401136 (LWP 7046)]
[New Thread -1246008432 (LWP 7047)]
[Thread -1293948016 (LWP 7045) exited]
[New Thread -1272775792 (LWP 7048)]
[New Thread -1293948016 (LWP 7049)]
[New Thread -1302340720 (LWP 7050)]
[New Thread -1310733424 (LWP 7051)]
[New Thread -1319126128 (LWP 7052)]
[New Thread -1327518832 (LWP 7053)]
[New Thread -1335911536 (LWP 7054)]
[New Thread -1344304240 (LWP 7055)]
[New Thread -1352696944 (LWP 7056)]
[Thread -1352696944 (LWP 7056) exited]
[New Thread -1352696944 (LWP 7057)]
[Thread -1352696944 (LWP 7057) exited]
[Thread -1254401136 (LWP 7046) exited]
[Thread -1246008432 (LWP 7047) exited]
[Thread -1272775792 (LWP 7048) exited]
[Thread -1293948016 (LWP 7049) exited]
[Thread -1302340720 (LWP 7050) exited]
[Thread -1310733424 (LWP 7051) exited]
[Thread -1319126128 (LWP 7052) exited]
[Thread -1327518832 (LWP 7053) exited]
[Thread -1335911536 (LWP 7054) exited]
[Thread -1344304240 (LWP 7055) exited]
[New Thread -1302340720 (LWP 7063)]
(no debugging symbols found)
(no debugging symbols found)
[Thread -1302340720 (LWP 7063) exited]

Program received signal SIGINT, Interrupt.
[Switching to Thread -1230354736 (LWP 7026)]
0xffffe410 in __kernel_vsyscall ()
(gdb) thread apply all bt

Thread 10 (Thread -1285555312 (LWP 7040)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb6f18f59 in fork () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7cbd7e4 in fork () from /lib/tls/i686/cmov/libpthread.so.0
#3 0xb70647d9 in ?? () from /usr/lib/libglib-2.0.so.0
#4 0xb35ff0e8 in ?? ()
#5 0xb7cb7bf0 in pthread_mutex_unlock ()
   from /lib/tls/i686/cmov/libpthread.so.0
#6 0xb7064ffa in g_spawn_async_with_pipes () from /usr/lib/libglib-2.0.so.0
#7 0xb7ebb9a9 in ?? () from /usr/lib/librhythmbox-core.so.0
#8 0x00000000 in ?? ()

Thread 1 (Thread -1230354736 (LWP 7026)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7cbadae in __lll_mutex_lock_wait ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7cb6aac in _L_mutex_lock_51 () from /lib/tls/i686/cmov/libpthread.so.0
#3 0xb7cb649d in pthread_mutex_lock () from /lib/tls/i686/cmov/libpthread.so.0
#4 0xb7ebbebe in rb_metadata_can_save () from /usr/lib/librhythmbox-core.so.0
#5 0x080af7ba in ?? ()
#6 0x0820cf00 in ?? ()
#7 0x085bd354 in ?? ()
---Type <return> to continue, or q <return> to quit---
#8 0xbfc9e2e8 in ?? ()
#9 0x080f0378 in ?? ()
#10 0x080af789 in ?? ()
#11 0x080f0378 in ?? ()
#12 0xbfc9e2e8 in ?? ()
#13 0x080ad9a0 in rhythmdb_entry_is_editable ()
Backtrace stopped: frame did not save the PC
(gdb)

=====
This was after pressing control-c in gdb

Revision history for this message
Justin Payne (neolithium82) wrote :

Thanks for taking the time to report the bug to help make Ubuntu better. I've tested this on Gutsy, and haven't been able to reproduce the result, though I did review the debug that you provided (Thank you for that). I suspect that it may be due to avahi-daemon either not being installed, or not active as a service on your system. Perhaps you may need to install that package, or ensure that it is in your services and running, and try again.

Should the result persist, can you also provide the Ubuntu version number that you are running, along with the Rhythmbox build you are using?

Changed in rhythmbox:
assignee: nobody → jbeerwart
status: New → Incomplete
Changed in rhythmbox:
assignee: jbeerwart → nobody
Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you get a backtrace (https://wiki.ubuntu.com/Backtrace) with libglib2.0-0-dbg libgtk2.0-0-dbg rhythmbox-dbg installed?

Changed in rhythmbox:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
Revision history for this message
encompass (encompass) wrote :

Thanks for taking the time to report the bug to help make Ubuntu better.
***Your welcome
I've tested this on Gutsy, and haven't been able to reproduce the result, though I did review the debug that you provided (Thank you for that). I suspect that it may be due to avahi-daemon either not being installed, or not active as a service on your system. Perhaps you may need to install that package, or ensure that it is in your services and running, and try again.
***Every time I boot... It tells me that I can't use it because I am on a .local domain. Heck... with I could fix that one!
Should the result persist, can you also provide the Ubuntu version number that you are running, along with the Rhythmbox build you are using?
***Feisty, default rhythmbox with that install.

Revision history for this message
encompass (encompass) wrote :

And now for the requested backtrace... the program does not "crash" so I have to kill the program. Lets hope we got some useful information.
I have the files that have errors. I will try to find one that I DON'T get the error on. Then I will anylise the difference.

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

The backtrace has no debug information, and if it's not crashing the title is misleading and should be changed

Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in rhythmbox:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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