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 427906 - crash in Sound:
crash in Sound:
Status: RESOLVED DUPLICATE of bug 418768
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: 2007-04-09 15:48 UTC by Stephan Haller
Modified: 2007-04-09 17:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Stephan Haller 2007-04-09 15:48:40 UTC 
Version: 2.16.2

What were you doing when the application crashed?



Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.16.2 2007-04-07 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 109826048 vsize: 109826048 resident: 13713408 share: 9977856 rss: 13713408 rss_rlim: -1
CPU usage: start_time: 1176133686 rtime: 18 utime: 17 stime: 1 cutime:3 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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 47940454532704 (LWP 21405)]
0x00002b9a009bcdf5 in waitpid () from /lib/libpthread.so.0

+ Trace 126304

Thread 1 (Thread 47940454532704 (LWP 21405))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 __libc_start_main
    from /lib/libc.so.6
  • #5 ??
  • #6 ??
  • #7 ??
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


Jens Granseuer





          2007-04-09 17:54:27 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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