GNOME Bugzilla – Bug 491853
crash in Volume Control:
Last modified: 2007-10-31 02:28:14 UTC
What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Bluecurve-Tangerine Icon Theme: NoiaWarm Memory status: size: 284844032 vsize: 284844032 resident: 20176896 share: 15949824 rss: 20176896 rss_rlim: 18446744073709551615 CPU usage: start_time: 1193781389 rtime: 11 utime: 6 stime: 5 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/mixer_applet2' (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 46912496361136 (LWP 4194)] (no debugging symbols found) 0x000000301720d945 in waitpid () from /lib64/libpthread.so.0
+ Trace 174003
Thread 1 (Thread 46912496361136 (LWP 4194))
----------- .xsession-errors (38 sec old) --------------------- Initializing nautilus-open-terminal extension Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Window manager warning: Lost connection to the display ':0.0'; most likely the X server was shut down or you killed/destroyed the window manager. ** Message: drive = 0 ** Message: volume = 0 CalDAV Eplugin starting up ... (evolution:4214): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one (evolution:4214): e-utils-WARNING **: Plugin 'Spamassassin junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0' ** (evolution:4214): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4214): DEBUG: mailto URL program: evolution --------------------------------------------------
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 463147 ***