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 421630 - crash in Sound: Nothing
crash in Sound: Nothing
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-22 20:36 UTC by jimsmith
Modified: 2007-03-22 20:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description jimsmith 2007-03-22 20:36:53 UTC 
Version: 2.16.0

What were you doing when the application crashed?
Nothing


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 26247168 vsize: 0 resident: 26247168 share: 0 rss: 10547200 rss_rlim: 0
CPU usage: start_time: 1174595811 rtime: 0 utime: 33 stime: 0 cutime:28 cstime: 0 timeout: 5 it_real_value: 0 frequency: 4

Backtrace was generated from '/usr/bin/gnome-sound-properties'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208178464 (LWP 3406)]
(no debugging symbols found)
0x009f2402 in __kernel_vsyscall ()

+ Trace 121253

Thread 1 (Thread -1208178464 (LWP 3406))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 main
  • #0 __kernel_vsyscall 






Comment 1


Jens Granseuer





          2007-03-22 20:56: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 ***