GNOME Bugzilla – Bug 164783
/usr/bin/gnome-volume-control crashes when changing volume settings
Last modified: 2005-01-21 02:08:06 UTC
Distribution: Debian testing/unstable Package: gnome-media Severity: normal Version: GNOME2.8.1 unspecified Gnome-Distributor: Ubuntu Synopsis: /usr/bin/gnome-volume-control crashes when changing volume settings Bugzilla-Product: gnome-media Bugzilla-Component: CDDBSlave2 Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: /usr/bin/gnome-volume-control crashes when i scroll fastly through the options (till for example somewhere near the end) Steps to reproduce the crash: 1. open volume control, and make sure you have a lot of options in there 2. take the scrollbar, and give it a fast swoosh to somewhere near the end, that's it 3. Expected Results: being able to scroll to the end of the settings (as fast as humanly possible) to change them How often does this happen? always Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-volume-control' (no debugging symbols found)...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (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)...(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)...[Thread debugging using libthread_db enabled] [New Thread 1088365312 (LWP 5009)] (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)...(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)...0xffffe410 in __kernel_vsyscall ()
+ Trace 54761
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-01-20 20:18 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-media". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was y.tilstra@quicknet.nl. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. It would be great if you could provide a better stack trace (see http://bugzilla.gnome.org/getting-traces.cgi for more info) in bug 156921. Matches the stack trace in bug 162435, which has been marked as a duplicate of 156921. *** This bug has been marked as a duplicate of 156921 ***