Well, the problem still exists that, when you exit normally from yumex-dnf, something is often left in a state that blocks starting it again. But, I've just found that running: yumex-dnf --exit will "tell session dbus services used by yumex to exit" and seems to remove the lock preventing the tool from opening. DW On 10/16/2015 12:13 PM, Paul Cartwright wrote: > > > On 10/16/2015 01:04 PM, Doug Wyatt wrote: >> Thanks for your reply ... >> >> However, /var/cache/dnf/metadata_lock.pid does not exist; >> if there was a dnf lock file, I would have expected it to >> prevent the 'dnf install ...' which I ran w/o problem. Also, >> there do not appear to be any relevant *.pid files in /var/run. > I just ran yumex-dnf & found this file in /var/cache/dnf : > -rw-r--r-- 1 root root 4 Oct 16 13:10 metadata_lock.pid > > I also do NOT have a .pid file in var/run associated with dnf.. > sorry.. not sure what to do now.. > I had that problem before & I think even logging out didn't help, I had > to reboot.. > >> >> DW >> >> On 10/16/2015 4:58 AM, Paul Cartwright wrote: >>> >>> On 10/16/2015 04:38 AM, Doug Wyatt wrote: >>>> I ran yumex-dnf a few times, then the last time I got the message: >>>> >>>> dnf is locked by another process >>>> yum extender will exit >>>> [ OK ] >>>> >>>> and, it exits. >>>> >>>> I can run dnf install successfully, and rpm -i also works. >>>> >>>> Can anyone suggest where the lock might be? >>>> >>> https://ask.fedoraproject.org/en/question/76157/failed-to-obtain-the-transaction-lock-logged-in-as-root/ >>> >>> >>> |rm /var/cache/dnf/metadata_lock.pid| >>> >>> >>> >>> > -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
