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 431277 - crash in Sound:
crash in Sound:
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: 2007-04-19 08:33 UTC by erunix
Modified: 2007-04-19 16:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description erunix 2007-04-19 08:33:14 UTC 
Version: 2.16.2

What were you doing when the application crashed?



Distribution: Slackware Slackware 11.0.0
Gnome Release: 2.16.3 2007-03-03 (Dropline GNOME)
BugBuddy Version: 2.16.0

Memory status: size: 10969088 vsize: 0 resident: 20324352 share: 0 rss: 10969088 rss_rlim: 0
CPU usage: start_time: 1177032607 rtime: 0 utime: 65 stime: 0 cutime:61 cstime: 0 timeout: 4 it_real_value: 0 frequency: 17

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 16384 (LWP 2521)]
(no debugging symbols found)
0x40681608 in waitpid () from /lib/libpthread.so.0

+ Trace 128974

Thread 1 (Thread 16384 (LWP 2521))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 __pthread_sighandler
    from /lib/libpthread.so.0
  • #4 <signal handler called>
  • #5 main
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


Jens Granseuer





          2007-04-19 16:15:29 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 363005 ***