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 355754 - crash in Sound: Just opened it and error...
crash in Sound: Just opened it and error...
Status: RESOLVED DUPLICATE of bug 355319
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-09-13 10:53 UTC by knedlik
Modified: 2006-09-13 11:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description knedlik 2006-09-13 10:53:40 UTC 
Version: 2.16.0

What were you doing when the application crashed?
Just opened it and error message appeared :(


Distribution: Gentoo Base System version 1.12.4
Gnome Release: 2.16.0 2006-09-13 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 107581440 vsize: 107581440 resident: 14405632 share: 10158080 rss: 14405632 rss_rlim: -1
CPU usage: start_time: 1158159146 rtime: 27 utime: 24 stime: 3 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 47092752698480 (LWP 23384)]
0x00002ad4a1a7c8f5 in waitpid () from /lib/libpthread.so.0

+ Trace 72251

Thread 1 (Thread 47092752698480 (LWP 23384))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 main
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


Karsten Bräckelmann





          2006-09-13 11:10:33 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 355319 ***