[Bug 38955] Re: blank location in database entry causes abort
I'm using Ubuntu 6.06. The circumstances were somewhat rare, but yes, a blank location can be written during normal use. I added a file and Rhythmbox crashed while adding the file, presumably part-way through, hence the missing location element. However, since Rhythmbox will not start at all until the database is fixed, I'd say patch it -- newer users that don't know where to look or what to change could be very bewildered. If I can reproduce the situation in which Rhythmbox writes the blank location, I will open a bug for that. -- blank location in database entry causes abort https://launchpad.net/bugs/38955 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 36302] Re: Volume keyboard shortcut fails to increase volume
angel12: As far as I can tell in GNOME right now, you can't. This is a bug and may or may not already be filed. GNOME uses some magic from ALSA to determine which channel is the master channel, so it may also be a bug with your soundcard driver. This bug refers to the inability to raise the volume, despite lowering it working fine and affecting the correct channel. -- Volume keyboard shortcut fails to increase volume https://launchpad.net/bugs/36302 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 36302] Re: Volume keyboard shortcut fails to increase volume
I've already reported this on upstream a little less than a week ago, before I knew about Launchpad. Please don't chew me out too bad. http://bugzilla.gnome.org/show_bug.cgi?id=336783 -- Volume keyboard shortcut fails to increase volume https://launchpad.net/malone/bugs/36302 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 22393] Re: Keyboard shortcuts don't work with Rhythmbox
The code for the keyboard shortcuts capplet is supposed to warn before a regular-character (a-z) key is assigned. This is likely an issue when triggering the shortcut, rather than assigning it. The output of this command may be useful in debugging this issue: gconftool -a /apps/gnome_settings_daemon/keybindings -- Keyboard shortcuts don't work with Rhythmbox https://launchpad.net/malone/bugs/22393 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 38955] blank location in database entry causes abort
Public bug reported: Affects: rhythmbox (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed Description: Steps to reproduce: 1. Modify an entry (or create one) in your rhythmdb.xml library file (specifically ~/.gnome2/rhythmbox/rhythmdb.xml) so it has a blank location tag. For example: entry type=song titleTitle/title genreRock/genre artistSo and So/artist albumBest of So and So/album duration181/duration file-size2898513/file-size location/location mountpointfile:mountpoint mtime1139182965/mtime first-seen1143761201/first-seen last-seen1144632181/last-seen rating2.50/rating play-count1/play-count last-played1144199177/last-played bitrate128/bitrate date731947/date mimetypeapplication/x-id3/mimetype /entry 2. Start Rhythmbox. Result: Abort and crash. Expected result: Skip file and continue. Output from rhythmbox --debug: [loading library business] [0x10102cd8] [queue_stat_uri] rhythmdb.c:1789 (23:05:00): queueing stat for RhythmDB-ERROR **: file rhythmdb.c: line 1790 (queue_stat_uri): assertion failed: (uri *uri) Backtrace (really useless, sorry, I can't find the debugging symbols package): (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) (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) [Thread debugging using libthread_db enabled] [New Thread 805528320 (LWP 7845)] [New Thread 815740144 (LWP 7853)] [New Thread 816002288 (LWP 7854)] [New Thread 824595696 (LWP 7857)] [New Thread 832984304 (LWP 7858)] (rhythmbox:7845): Rhythmbox-WARNING **: Unable to start mDNS browsing [Thread 832984304 (LWP 7858) exited] [Thread 824595696 (LWP 7857) exited] [New Thread 843052272 (LWP 7860)] [Thread 843052272 (LWP 7860) exited] RhythmDB-ERROR **: file rhythmdb.c: line 1790 (queue_stat_uri): assertion failed: (uri *uri) aborting... [New Thread 843052272 (LWP 7861)] Program received signal SIGABRT, Aborted. [Switching to Thread 805528320 (LWP 7845)] 0x0e4e7708 in raise () from /lib/libc.so.6 (gdb) thread apply all bt Thread 7 (Thread 843052272 (LWP 7861)): #0 0x0f478544 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x0f478528 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0x0f478528 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #3 0x0f478528 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #4 0x0f478528 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #5 0x0f478528 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #6 0x0f478528 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 Previous frame inner to this frame (corrupt stack?) Thread 6 (Thread 843052272 (LWP 7861)): #0 0x0f478544 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x0f478528 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0x0f478528 in pthread_cond_timedwait@@GLIBC_2.3.2 () ---Type return to continue, or q return to quit--- from /lib/libpthread.so.0 #3 0x0f478528 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #4 0x0f478528 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #5 0x0f478528 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #6 0x0f478528 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 Previous frame inner to this frame (corrupt stack?) Thread 3 (Thread 816002288 (LWP 7854)): #0 0x0e57e1a8 in poll () from /lib/libc.so.6 #1 0x0e57e190 in poll () from /lib/libc.so.6 #2 0x0e57e190 in poll () from /lib/libc.so.6 #3 0x0e57e190 in poll () from /lib/libc.so.6 #4 0x0e57e190 in poll () from /lib/libc.so.6 #5 0x0e57e190 in poll () from /lib/libc.so.6 #6 0x0e57e190
