Description of problem: Yumex crashed immediately after logged into KDE. The crash was detected by abrt. Version-Release number of selected component (if applicable): 3.0.14-1 How reproducible: unsure Steps to Reproduce: 1. log into KDE 2. 3. Actual results: crash Expected results: no crash Additional info:
Created attachment 869477 [details] backtrace
Created attachment 869478 [details] analyzer
Created attachment 869479 [details] cmdline
Created attachment 869480 [details] environ
Created attachment 869481 [details] event_log
abrt 2.1.12 kernel 3.13.4-200.fc20.x86_64 yum 3.4.3-137.fc20.noarch
Does it happen every time or just this time ?
I don't know how to reproduce and will watch it for some time cause I do not login newly and often due to suspending and locking only.
OK, this is an issues seen many times before, and there is many ways it can occours. It happens when the pipe the yumex gui uses to exchange infomation with the root yumex backend there is doing the package actions. Sometimes the pipe dies and communication is lost and python makes an IOError 5 when the gui tries to read/write to the pipe. It is solved in yumex-nextgen there is using a DBus service instead, there is much easier to handle.
*** This bug has been marked as a duplicate of bug 801860 ***
*** This bug has been marked as a duplicate of bug 881860 ***
(In reply to Tim Lauridsen from comment #11) > > *** This bug has been marked as a duplicate of bug 881860 *** Was has Yumex to do with JBOSS on RHEL???
(In reply to Raphael Groner from comment #12) > (In reply to Tim Lauridsen from comment #11) > > > > *** This bug has been marked as a duplicate of bug 881860 *** > > Was has Yumex to do with JBOSS on RHEL??? Nothing, just a typo, 881860 is the right one, 801860 was the typo *** This bug has been marked as a duplicate of bug 881860 ***