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 350836 - crash on Sound
crash on Sound
Status: RESOLVED DUPLICATE of bug 351002
Product: gnome-control-center
Classification: Core
Component: Sound
2.15.x
Other All
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-11 03:06 UTC by thanate
Modified: 2006-08-12 10:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description thanate 2006-08-11 03:06:30 UTC 
What were you doing when the application crashed?
try to start the sound preference


Distribution: Debian testing/unstable
Gnome Release: 2.15.91 2006-08-09 (GARNOME)
BugBuddy Version: 2.15.90

Memory status: size: 23736320 vsize: 0 resident: 23736320 share: 0 rss: 12976128 rss_rlim: 0
CPU usage: start_time: 1155265500 rtime: 0 utime: 71 stime: 0 cutime:64 cstime: 0 timeout: 7 it_real_value: 0 frequency: 10

Backtrace was generated from '/home/boat/garnome/bin/gnome-sound-properties'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1226070336 (LWP 2389)]
0xb705820e in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 70220

Thread 1 (Thread -1226070336 (LWP 2389))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_segv_handle
    from /home/boat/garnome/lib/libgnomeui-2.so.0
  • #2 ??
  • #3 __after_morecore_hook
    from /lib/tls/libc.so.6
  • #4 ??
  • #5 ??
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0 






Comment 1


Christian Kirbach





          2006-08-11 10:04:48 UTC
        



hmm corrupt trace?

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.







Comment 2


thanate





          2006-08-12 06:47:38 UTC
        



(In reply to comment #1)
> hmm corrupt trace?
> 
> Thanks for the bug report. Unfortunately, that stack trace is not very useful
> in determining the cause of the crash. Can you get us one with debugging
> symbols? Please see http://live.gnome.org/GettingTraces for more information on
> how to do so.
> 

Hi, I resubmitted this bug as Bug 351002. Hopefully with more useful info
this time.






Comment 3


Kjartan Maraas





          2006-08-12 10:14:34 UTC
        



Marking this as a duplicate then.

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