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 417138 - crash in Sound: It may well have been wh...
crash in Sound: It may well have been wh...
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-11 17:02 UTC by michael.brownhill
Modified: 2007-03-11 19:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description michael.brownhill 2007-03-11 17:02:18 UTC 
Version: 2.16.0

What were you doing when the application crashed?
It may well have been when I was playing with Amorak. I am knew to Linux much of it makes no sense to me. 


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: 117018624 vsize: 117018624 resident: 15532032 share: 11177984 rss: 15532032 rss_rlim: -1
CPU usage: start_time: 1173632489 rtime: 33 utime: 30 stime: 3 cutime:2 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 46961125072480 (LWP 6047)]
(no debugging symbols found)
0x00002ab5fbc6cd35 in waitpid () from /lib64/libpthread.so.0

+ Trace 117739

Thread 1 (Thread 46961125072480 (LWP 6047))

  • #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-03-11 19:21:00 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 ***