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 366118 - 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: 2006-10-28 06:39 UTC by anko
Modified: 2006-12-08 03:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description anko 2006-10-28 06:39:32 UTC
Version: 2.16.0

What were you doing when the application crashed?
したことは
管理の「サウンドカードの検出」を起動しようとしましたが起動できず、そのままサウンド設定の「サウンド」を起動しようとしました。

追伸
NECのLaVieLL700です。FC5の時も同様にサウンドカードを認識しませんでしたが、「サウンドカードの検出」の画面は出ました。今回は画面すら出ません。


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: 37634048 vsize: 0 resident: 37634048 share: 0 rss: 15745024 rss_rlim: 0
CPU usage: start_time: 1162017275 rtime: 0 utime: 17 stime: 0 cutime:15 cstime: 0 timeout: 2 it_real_value: 0 frequency: 1

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 -1209059104 (LWP 2495)]
(no debugging symbols found)
0x00766402 in __kernel_vsyscall ()

Thread 1 (Thread -1209059104 (LWP 2495))

  • #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 Baptiste Mille-Mathias 2006-10-28 15:12:50 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 André Klapper 2006-12-08 03:13:24 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 ***