Bug 1298775

Description of problem:

When application is frozen and force quit is used in the desktop environment at user level, the dnfdaemon-system process might still be running. When restarting yumex-dnf it will ask to close the running process, in which it fails and dies without error message. Process is owned by root thus root privileges are needed to close it which yumex-dnf doesn't try to obtain. 

Also in the dialog box in which it says Yum Extender is already running it lists the process id of the previous Yum Extender while in fact this process id is not running anymore!


Version-Release number of selected component (if applicable):

4.1.4-1.fc22


How reproducible:

Do something to freeze the user interface and close it via desktop environment by answering yes to the question: "Application frozen, do you want to quit it?" or use kill -9 <yumex-dnf pid> to reproduce. Try to start yumex-dnf again afterwards.


Steps to Reproduce:

1. Start yumex-dnf as administrative user on desktop
2. Open console and use ps command to find the the process id of yumex-dnf
3. Execute kill -9 <process id>
4. Use ps command again to verify <process id> is in fact closed
5. Start yumex-dnf again and notice the <process id> mentioned as running
6. Answer yes to the question if yumex-dnf should quit it


Actual results:

Zero.


Expected results:

The yumex-dnf GUI. (by having yumex-dnf elevate privileges and/or close proper pid)


Additional info:

When yumex-dnf is ran from console, no more than the following output is presented: "method return sender=:1.202 -> dest=:1.212 reply_serial=2"