Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handling RPM installation from second instance makes first instance behave ugly #144

Open
moceap opened this issue Dec 20, 2016 · 3 comments
Labels

Comments

@moceap
Copy link

moceap commented Dec 20, 2016

When open Yumex-dnf , and then install local package from file manager through Yumex-dnf ..

After finishing installing local package Yumex-dnf abnormally closed !!! even main window that opened even before opening local package!

@genodeftest
Copy link
Collaborator

Is there any backtrace (python calls it "traceback") you could provide? You might want to look in your syslogs, e.g. with `journalctl --since=2016-12-20" and search for "yumex" or "python" or "traceback". Also ABRT (the automated bug reporting tool) might be of help.

Do you have steps to reproduce?

@moceap
Copy link
Author

moceap commented Dec 23, 2016

Step to reproduce (explained) :

  1. Open Yumex
  2. Go File manager (like nautilus)
  3. Install local package by yumex

Then first yumex (1.) closed !!!

@genodeftest genodeftest changed the title Yumex-dnf abnormally closed Handling RPM installation from command line into existing instance is ugly Dec 23, 2016
@genodeftest genodeftest changed the title Handling RPM installation from command line into existing instance is ugly Handling RPM installation from second instance makes first instance behave ugly Dec 23, 2016
@genodeftest genodeftest added the UI label Dec 23, 2016
@genodeftest
Copy link
Collaborator

I can't reproduce the bug. The first yumex-dnf instance is not getting closed, it just gets the RPM via DBus from the second instance. The first yumex-dnf instance is throwing away all temporary data like "which application is marked for removal" though, which may look like it is closed. This definitely is a bug, but there is no crash and no unintended close. User experience needs to be improved on this a lot.

It also breaks dnfdaemon, so yumex-dnf can't restart. Should get fixed in dnfdaemon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants