abrt version: 1.1.13 architecture: i686 cmdline: /usr/bin/python -OO /usr/bin/gmixer -d comment: Just upgraded to Fedora 14 from 13 and upon initial reboot from the upgrade (using DVD image of install) crash occurred. component: gmixer executable: /usr/bin/gmixer kernel: 2.6.35.6-45.fc14.i686 package: gmixer-1.3-17.fc13 reason: gmixer:39:<module>:ImportError: No module named gtktrayicon release: Fedora release 14 (Laughlin) time: 1288920567 uid: 500 backtrace ----- gmixer:39:<module>:ImportError: No module named gtktrayicon Traceback (most recent call last): File "/usr/bin/gmixer", line 39, in <module> from gtktrayicon import TrayIcon ImportError: No module named gtktrayicon Local variables in innermost frame: gtk: <module 'gtk' from '/usr/lib/python2.7/site-packages/gtk-2.0/gtk/__init__.pyo'> signal: <module 'signal' (built-in)> __builtins__: <module '__builtin__' (built-in)> __file__: '/usr/bin/gmixer' traceback: <module 'traceback' from '/usr/lib/python2.7/traceback.pyo'> gettext: <module 'gettext' from '/usr/lib/python2.7/gettext.pyo'> __package__: None sys: <module 'sys' (built-in)> locale: <module 'locale' from '/usr/lib/python2.7/locale.pyo'> pygtk: <module 'pygtk' from '/usr/lib/python2.7/site-packages/pygtk.pyo'> gobject: <module 'gobject' from '/usr/lib/python2.7/site-packages/gtk-2.0/gobject/__init__.pyo'> __name__: '__main__' os: <module 'os' from '/usr/lib/python2.7/os.pyo'> __doc__: None OptionParser: <class optparse.OptionParser at 0x9b92f8c> ConfigParser: <module 'ConfigParser' from '/usr/lib/python2.7/ConfigParser.pyo'>
Created attachment 457982 [details] File: backtrace
Why have you got python 2.7 in F13?
(In reply to comment #2) > Why have you got python 2.7 in F13? Update gmixer to the f14 version.
Stange, something seems to go strange in gnome, because this is the second bug, where there is initial confusion, when rebooting after the upgrade... -> CC'ing the python maintainer, he might have a look to this. Closing as a dub of 649507, because gnome is doing something wrong there too... *** This bug has been marked as a duplicate of bug 649507 ***