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 429385 - crash in Sound: 刚开机！
crash in Sound: 刚开机！
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-04-13 14:43 UTC by xuejunjunaaa
Modified: 2007-04-13 18:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description xuejunjunaaa 2007-04-13 14:43:23 UTC 
Version: 2.16.0

What were you doing when the application crashed?
刚开机！


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: 289341440 vsize: 289341440 resident: 17604608 share: 11345920 rss: 17604608 rss_rlim: -1
CPU usage: start_time: 1176475388 rtime: 16 utime: 13 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 46912686077376 (LWP 16224)]
(no debugging symbols found)
0x00002aaab1305935 in waitpid () from /lib64/libpthread.so.0

+ Trace 127483

Thread 1 (Thread 46912686077376 (LWP 16224))

  • #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
  • #0 waitpid
    from /lib64/libpthread.so.0 






Comment 1


Jens Granseuer





          2007-04-13 18:25:57 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 ***