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 405680 - crash in Sound: Trying to configure soun...
crash in Sound: Trying to configure soun...
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-02-08 10:19 UTC by jmvanham
Modified: 2007-02-08 16:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description jmvanham 2007-02-08 10:19:38 UTC
Version: 2.16.0

What were you doing when the application crashed?
Trying to configure sound in system preferences.
the nessage was: gnome-sound-properties have crashed.
Please advise
TIA
Joep van Ham


Distribution: Mandriva Linux release 2007.0 (Official) for x86_64
Gnome Release: 2.16.0 2006-09-05 (Mandriva)
BugBuddy Version: 2.16.0

Memory status: size: 125100032 vsize: 125100032 resident: 16867328 share: 12038144 rss: 16867328 rss_rlim: -1
CPU usage: start_time: 1170929877 rtime: 16 utime: 14 stime: 2 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 47144844434816 (LWP 7308)]
(no debugging symbols found)
0x00002ae0c1d67d35 in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 47144844434816 (LWP 7308))

  • #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

Comment 1 Jens Granseuer 2007-02-08 16:52:23 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 ***