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 374236 - crash in Sound: tryed to open Sound in K...
crash in Sound: tryed to open Sound in K...
Status: RESOLVED DUPLICATE of bug 374264
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-11-12 11:05 UTC by Cruel
Modified: 2006-11-13 10:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Cruel 2006-11-12 11:05:35 UTC 
Version: 2.16.1

What were you doing when the application crashed?
tryed to open Sound in Kontrolcenter


Distribution: openSUSE 10.2 (X86-64) Beta2
Gnome Release: 2.16.1 2006-11-07 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 187293696 vsize: 187293696 resident: 3715072 share: 11177984 rss: 14893056 rss_rlim: -1
CPU usage: start_time: 1163329467 rtime: 13 utime: 12 stime: 1 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/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 47814890758048 (LWP 6239)]
(no debugging symbols found)
0x00002b7cc3095c25 in waitpid () from /lib64/libpthread.so.0

+ Trace 85731

Thread 1 (Thread 47814890758048 (LWP 6239))

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






Comment 1


André Klapper





          2006-11-13 10:34:03 UTC
        



Thanks for taking the time to report this bug.
This particular bug is the same bug as bug 374264, but the maintainers need more information to fix the bug. Could you please answer the questions in bug 374264 in order to help the developers?


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