GNOME Bugzilla – Bug 691561
Rhythmbox crashes when fullscreen visualization is enabled
Last modified: 2014-08-25 18:34:54 UTC
When I try to maximize the visualization in Rhythmbox 2.97 it simply crashes: http://youtu.be/R2ITxUZX1Uw I use Debian Wheezy AMD64, more info: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677562 Hope this can be fixed before Wheezy is released, thanks anyway!
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
It's not much... Nothing happens when the program freezes, could this maybe a deadlock of some kind? I had to kill the application myself because it was not responding. Starting program: /usr/bin/rhythmbox [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe0efa700 (LWP 1307)] [New Thread 0x7fffd783c700 (LWP 1308)] [New Thread 0x7fffd591d700 (LWP 1309)] [Thread 0x7fffd591d700 (LWP 1309) exited] [Thread 0x7fffe0efa700 (LWP 1307) exited] [Thread 0x7ffff7fae9c0 (LWP 1304) exited] [Inferior 1 (process 1304) exited normally] (gdb) run Starting program: /usr/bin/rhythmbox [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe0efa700 (LWP 1326)] [New Thread 0x7fffd783c700 (LWP 1327)] [New Thread 0x7fffd591d700 (LWP 1328)] [New Thread 0x7fffceb97700 (LWP 1329)] [New Thread 0x7fffcbff9700 (LWP 1331)] [New Thread 0x7fffca0a1700 (LWP 1332)] [Thread 0x7fffca0a1700 (LWP 1332) exited] [New Thread 0x7fffca0a1700 (LWP 1333)] [New Thread 0x7fffc969d700 (LWP 1334)] [Thread 0x7fffc969d700 (LWP 1334) exited] [Thread 0x7fffd591d700 (LWP 1328) exited] [New Thread 0x7fffd591d700 (LWP 1335)] [New Thread 0x7fffc969d700 (LWP 1336)] [New Thread 0x7fffc1f8f700 (LWP 1337)] [New Thread 0x7fffc178e700 (LWP 1338)] [New Thread 0x7fffc0b64700 (LWP 1339)] (rhythmbox:1325): GLib-GObject-CRITICAL **: g_value_get_uint: assertion `G_VALUE_HOLDS_UINT (value)' failed [New Thread 0x7fffc0363700 (LWP 1340)] [New Thread 0x7fffbfb62700 (LWP 1341)] [Thread 0x7fffbfb62700 (LWP 1341) exited] [New Thread 0x7fffbfb62700 (LWP 1342)] [New Thread 0x7fffbe15d700 (LWP 1343)] [Thread 0x7fffbe15d700 (LWP 1343) exited] [Thread 0x7fffe0efa700 (LWP 1326) exited] [Thread 0x7fffc969d700 (LWP 1336) exited] [Thread 0x7fffd591d700 (LWP 1335) exited] [Thread 0x7fffca0a1700 (LWP 1333) exited] [Thread 0x7fffcbff9700 (LWP 1331) exited] [Thread 0x7fffceb97700 (LWP 1329) exited] [Thread 0x7fffc178e700 (LWP 1338) exited] [Thread 0x7fffc0363700 (LWP 1340) exited] [Thread 0x7fffc0b64700 (LWP 1339) exited] [Thread 0x7fffc1f8f700 (LWP 1337) exited] [Thread 0x7fffd783c700 (LWP 1327) exited] [Thread 0x7ffff7fae9c0 (LWP 1325) exited] Program terminated with signal SIGKILL, Killed. The program no longer exists.
I forgot to run 'bt' after the SIGKILL: (gdb) bt
+ Trace 231395
Does this still happen with rhythmbox 2.99(.1)?
(In reply to comment #4) > Does this still happen with rhythmbox 2.99(.1)? Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!