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 479749 - crash in Volume Control: Clicked on the mute micr...
crash in Volume Control: Clicked on the mute micr...
Status: RESOLVED DUPLICATE of bug 478485
Product: gnome-applets
Classification: Other
Component: mixer
unspecified
Other All
: High critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-24 09:26 UTC by Kjartan Maraas
Modified: 2007-10-04 16:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Kjartan Maraas 2007-09-24 09:26:23 UTC 
What were you doing when the application crashed?
Clicked on the mute microphone button under recording.


Distribution: Fedora release 7.91 (Rawhide)
Gnome Release: 2.20.0 2007-09-17 (Red Hat, Inc)
BugBuddy Version: 2.20.0

System: Linux 2.6.23-0.195.rc7.git3.fc8 #1 SMP Sat Sep 22 08:33:35 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 65708032 vsize: 65708032 resident: 16044032 share: 11935744 rss: 16044032 rss_rlim: 4294967295
CPU usage: start_time: 1190622720 rtime: 37 utime: 27 stime: 10 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/mixer_applet2'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208161696 (LWP 2408)]
[New Thread -1223726192 (LWP 2420)]
0x0012d402 in __kernel_vsyscall ()

+ Trace 165022

Thread 1 (Thread -1208161696 (LWP 2408))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 364
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 672
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 google_breakpad::ExceptionHandler::HandleException
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 <signal handler called>
  • #9 cb_notify_message
    at applet.c line 1246
  • #10 marshal_VOID__MINIOBJECT
    at gstbus.c line 161
  • #11 IA__g_closure_invoke
    at gclosure.c line 490
  • #12 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #13 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #14 IA__g_signal_emit
    at gsignal.c line 2243
  • #15 gst_bus_async_signal_func
    at gstbus.c line 975
  • #16 gst_bus_source_dispatch
    at gstbus.c line 701
  • #17 IA__g_main_context_dispatch
    at gmain.c line 2061
  • #18 g_main_context_iterate
    at gmain.c line 2694
  • #19 IA__g_main_loop_run
    at gmain.c line 2898
  • #20 bonobo_main
    at bonobo-main.c line 311
  • #21 bonobo_generic_factory_main_timeout
    at bonobo-generic-factory.c line 411
  • #22 bonobo_generic_factory_main
    at bonobo-generic-factory.c line 368
  • #23 panel_applet_factory_main_closure
    at panel-applet.c line 1754
  • #24 panel_applet_factory_main
    at panel-applet.c line 1778
  • #25 main
    at load.c line 340
  • #26 __libc_start_main
    from /lib/libc.so.6
  • #27 _start
  • #0 __kernel_vsyscall 


----------- .xsession-errors (57 sec old) ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: NM appeared
** (nm-applet:2318): WARNING **: Found connection Auto to activate at /org/freedesktop/NetworkManagerSettings/0.
error getting update info:  No network available
error getting update info:  No network available
error getting update info:  No network available
error getting update info:  No network available
error getting update info:  No network available
error getting update info:  No network available
--------------------------------------------------
Comment 1 Kjartan Maraas 2007-10-04 16:40:52 UTC 
Patch in bug 478485 fixes this for me. Marking as duplicate.

*** This bug has been marked as a duplicate of 478485 ***