After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 386044 - crash in Sound: just running it
crash in Sound: just running it
Status: RESOLVED DUPLICATE of bug 363005
Product: gnome-control-center
Classification: Core
Component: Sound
2.16.x
Other All
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-14 23:39 UTC by scott
Modified: 2006-12-23 04:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description scott 2006-12-14 23:39:24 UTC 
Version: 2.16.1

What were you doing when the application crashed?
just running it


Distribution: Gentoo Base System version 1.12.6
Gnome Release: 2.16.1 2006-11-17 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 19550208 vsize: 0 resident: 19550208 share: 0 rss: 10891264 rss_rlim: 0
CPU usage: start_time: 1166110720 rtime: 0 utime: 38 stime: 0 cutime:34 cstime: 0 timeout: 4 it_real_value: 0 frequency: 11

Backtrace was generated from '/usr/bin/gnome-sound-properties'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225972048 (LWP 20101)]
0xb7f5b410 in ?? ()

+ Trace 94272

  • #0 ??
  • #1 ??
  • #2 ?? 






Comment 1


Bruno Boaventura





          2006-12-15 15:49:08 UTC
        



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!







Comment 2


André Klapper





          2006-12-23 04:00:26 UTC
        



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.


*** This bug has been marked as a duplicate of 363005 ***