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 423345 - crash in Sound: nothing . I open soun ca...
crash in Sound: nothing . I open soun ca...
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-03-27 14:28 UTC by pellegrino
Modified: 2007-03-27 19:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description pellegrino 2007-03-27 14:28:02 UTC 
Version: 2.16.0

What were you doing when the application crashed?
nothing . I open soun card detection


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 261869568 vsize: 261869568 resident: 11542528 share: 8060928 rss: 11542528 rss_rlim: -1
CPU usage: start_time: 1175002024 rtime: 12 utime: 8 stime: 4 cutime:1 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496418784 (LWP 4488)]
(no debugging symbols found)
0x0000003e6160d935 in waitpid () from /lib64/libpthread.so.0

+ Trace 122613

Thread 1 (Thread 46912496418784 (LWP 4488))

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






Comment 1


Jens Granseuer





          2007-03-27 19:40:55 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 ***