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 379938 - crash in Sound: was clicking to open apl...
crash in Sound: was clicking to open apl...
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: 2006-11-27 22:33 UTC by brechtverhaeghe
Modified: 2006-12-08 03:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description brechtverhaeghe 2006-11-27 22:33:53 UTC 
Version: 2.16.1

What were you doing when the application crashed?
was clicking to open aplication


Distribution: openSUSE 10.2 (X86-64) Beta1
Gnome Release: 2.16.1 2006-10-24 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 186527744 vsize: 186527744 resident: 3653632 share: 10846208 rss: 14499840 rss_rlim: -1
CPU usage: start_time: 1164666763 rtime: 17 utime: 16 stime: 1 cutime:0 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 47104098680832 (LWP 7116)]
(no debugging symbols found)
0x00002ad74486fc25 in waitpid () from /lib64/libpthread.so.0

+ Trace 89852

Thread 1 (Thread 47104098680832 (LWP 7116))

  • #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-28 15:54:11 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!







Comment 2


André Klapper





          2006-12-08 03:11:47 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 363005 ***