Description of problem: $ dnfdragora --update-only Skipped exception: <[Errno 2] No such file or directory: '/home/jamundson/dnfdragora.yaml'> Skipped exception: <[Errno 2] No such file or directory: './dnfdragora.yaml'> <_M_> [ui] YPath.cc:49 YPath(): Given filename: libyui-qt.so.7 <_M_> [ui] YSettings.cc:73 progDir(): progDir: "" <_M_> [ui] YPath.cc:65 YPath(): Preferring subdir: <_M_> [ui] YPath.cc:66 YPath(): Subdir given with filename: <_M_> [ui] YPath.cc:67 YPath(): Looking for: libyui-qt.so.7 <_M_> [ui] YPath.cc:138 lsDir(): Looking in /usr/lib64/yui <_M_> [ui] YPath.cc:121 YPath(): Could NOT find libyui-qt.so.7 by looking recursive inside /usr/lib64/yui <_M_> [ui] YPath.cc:49 YPath(): Given filename: libyui-gtk.so.7 <_M_> [ui] YSettings.cc:73 progDir(): progDir: "" <_M_> [ui] YPath.cc:65 YPath(): Preferring subdir: <_M_> [ui] YPath.cc:66 YPath(): Subdir given with filename: <_M_> [ui] YPath.cc:67 YPath(): Looking for: libyui-gtk.so.7 <_M_> [ui] YPath.cc:138 lsDir(): Looking in /usr/lib64/yui <_M_> [ui] YPath.cc:118 YPath(): Found libyui-gtk.so.7 in /usr/lib64/yui <_M_> [ui] YPath.cc:49 YPath(): Given filename: libyui-gtk.so.7 <_M_> [ui] YSettings.cc:73 progDir(): progDir: "" <_M_> [ui] YPath.cc:65 YPath(): Preferring subdir: <_M_> [ui] YPath.cc:66 YPath(): Subdir given with filename: <_M_> [ui] YPath.cc:67 YPath(): Looking for: libyui-gtk.so.7 <_M_> [ui] YPath.cc:138 lsDir(): Looking in /usr/lib64/yui <_M_> [ui] YPath.cc:118 YPath(): Found libyui-gtk.so.7 in /usr/lib64/yui <_M_> [ui] YUI.cc:76 YUI(): This is libyui 3.2.8 <_M_> [ui] YUI.cc:77 YUI(): Creating UI without threads <_M_> [gtk] YGUI.cc:164 checkInit(): Style "/usr/share/libyui/theme/current/wizard/style.css" <_M_> [gtk] YGUI.cc:186 checkInit(): Style "/usr/share/libyui/theme/current/wizard/style.css" not found. Ignoring style <WRN> [gtk] YGUtils.cc:543 loadPixbuf(): Could not load icon: /usr/share/libyui/theme/icons/32x32/apps/yast.png <WRN> [gtk] YGUtils.cc:543 loadPixbuf(): Reason: Failed to open file '/usr/share/libyui/theme/icons/32x32/apps/yast.png': No such file or directory <_M_> [ui] YUI.cc:230 topmostConstructorHasFinished(): Running without threads <_M_> [ui] YPath.cc:49 YPath(): Given filename: libyui-qt.so.7 <_M_> [ui] YSettings.cc:73 progDir(): progDir: "" <_M_> [ui] YPath.cc:65 YPath(): Preferring subdir: <_M_> [ui] YPath.cc:66 YPath(): Subdir given with filename: <_M_> [ui] YPath.cc:67 YPath(): Looking for: libyui-qt.so.7 <_M_> [ui] YPath.cc:138 lsDir(): Looking in /usr/lib64/yui <_M_> [ui] YPath.cc:121 YPath(): Could NOT find libyui-qt.so.7 by looking recursive inside /usr/lib64/yui <_M_> [ui] YPath.cc:49 YPath(): Given filename: libyui-gtk.so.7 <_M_> [ui] YSettings.cc:73 progDir(): progDir: "" <_M_> [ui] YPath.cc:65 YPath(): Preferring subdir: <_M_> [ui] YPath.cc:66 YPath(): Subdir given with filename: <_M_> [ui] YPath.cc:67 YPath(): Looking for: libyui-gtk.so.7 <_M_> [ui] YPath.cc:138 lsDir(): Looking in /usr/lib64/yui <_M_> [ui] YPath.cc:118 YPath(): Found libyui-gtk.so.7 in /usr/lib64/yui <_M_> [ui] YPath.cc:49 YPath(): Given filename: libyui-mga-gtk.so.7 <_M_> [ui] YSettings.cc:73 progDir(): progDir: "" <_M_> [ui] YPath.cc:65 YPath(): Preferring subdir: <_M_> [ui] YPath.cc:66 YPath(): Subdir given with filename: <_M_> [ui] YPath.cc:67 YPath(): Looking for: libyui-mga-gtk.so.7 <_M_> [ui] YPath.cc:138 lsDir(): Looking in /usr/lib64/yui <_M_> [ui] YPath.cc:118 YPath(): Found libyui-mga-gtk.so.7 in /usr/lib64/yui <_M_> [ew] YExternalWidgets.cc:37 YExternalWidgets(): Creating Libyui External Widgets object <_M_> [gtk] YMGA_GCBTable.cc:415 YMGA_GCBTable(): Slection mode 2 <_M_> [gtk] YMGA_GCBTable.cc:434 YMGA_GCBTable(): columns 6 tot 6 [snip] (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458833920 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (python3:337): Gtk-WARNING **: Allocating size to YGtkAdjSize 0x55d458871eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 187, in __call__ return getattr(self.proxy, self.method)(*args) RecursionError: maximum recursion depth exceeded while calling a Python object Fatal Python error: Cannot recover from stack overflow. Current thread 0x00007fbdf7eba700 (most recent call first): File "/usr/lib64/python3.6/site-packages/yui.py", line 5571 in setValue File "/usr/lib/python3.6/site-packages/dnfdragora/progress_ui.py", line 77 in set_progress File "/usr/lib/python3.6/site-packages/dnfdragora/dnf_backend.py", line 229 in on_RPMProgress File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 556 in handle_dbus_signals File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 228 in _on_g_signal File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 187 in __call__ File "/usr/lib64/python3.6/site-packages/yui.py", line 5571 in setValue File "/usr/lib/python3.6/site-packages/dnfdragora/progress_ui.py", line 77 in set_progress File "/usr/lib/python3.6/site-packages/dnfdragora/dnf_backend.py", line 229 in on_RPMProgress File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 556 in handle_dbus_signals File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 228 in _on_g_signal File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 187 in __call__ File "/usr/lib64/python3.6/site-packages/yui.py", line 5571 in setValue File "/usr/lib/python3.6/site-packages/dnfdragora/progress_ui.py", line 77 in set_progress File "/usr/lib/python3.6/site-packages/dnfdragora/dnf_backend.py", line 229 in on_RPMProgress File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 556 in handle_dbus_signals File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 228 in _on_g_signal File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 187 in __call__ File "/usr/lib64/python3.6/site-packages/yui.py", line 5571 in setValue File "/usr/lib/python3.6/site-packages/dnfdragora/progress_ui.py", line 77 in set_progress File "/usr/lib/python3.6/site-packages/dnfdragora/dnf_backend.py", line 229 in on_RPMProgress File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 556 in handle_dbus_signals File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 228 in _on_g_signal File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 187 in __call__ File "/usr/lib64/python3.6/site-packages/yui.py", line 5571 in setValue File "/usr/lib/python3.6/site-packages/dnfdragora/progress_ui.py", line 77 in set_progress File "/usr/lib/python3.6/site-packages/dnfdragora/dnf_backend.py", line 229 in on_RPMProgress File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 556 in handle_dbus_signals File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 228 in _on_g_signal File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 187 in __call__ File "/usr/lib64/python3.6/site-packages/yui.py", line 5571 in setValue File "/usr/lib/python3.6/site-packages/dnfdragora/progress_ui.py", line 77 in set_progress File "/usr/lib/python3.6/site-packages/dnfdragora/dnf_backend.py", line 229 in on_RPMProgress File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 556 in handle_dbus_signals File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 228 in _on_g_signal File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 187 in __call__ File "/usr/lib64/python3.6/site-packages/yui.py", line 5571 in setValue File "/usr/lib/python3.6/site-packages/dnfdragora/progress_ui.py", line 77 in set_progress File "/usr/lib/python3.6/site-packages/dnfdragora/dnf_backend.py", line 229 in on_RPMProgress File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 556 in handle_dbus_signals File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 228 in _on_g_signal File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 187 in __call__ File "/usr/lib64/python3.6/site-packages/yui.py", line 5571 in setValue File "/usr/lib/python3.6/site-packages/dnfdragora/progress_ui.py", line 77 in set_progress File "/usr/lib/python3.6/site-packages/dnfdragora/dnf_backend.py", line 229 in on_RPMProgress File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 556 in handle_dbus_signals File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 228 in _on_g_signal File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 187 in __call__ File "/usr/lib64/python3.6/site-packages/yui.py", line 5571 in setValue File "/usr/lib/python3.6/site-packages/dnfdragora/progress_ui.py", line 77 in set_progress File "/usr/lib/python3.6/site-packages/dnfdragora/dnf_backend.py", line 229 in on_RPMProgress File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 556 in handle_dbus_signals File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 228 in _on_g_signal File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 187 in __call__ File "/usr/lib64/python3.6/site-packages/yui.py", line 5571 in setValue File "/usr/lib/python3.6/site-packages/dnfdragora/progress_ui.py", line 77 in set_progress File "/usr/lib/python3.6/site-packages/dnfdragora/dnf_backend.py", line 229 in on_RPMProgress File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 556 in handle_dbus_signals File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 228 in _on_g_signal File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 187 in __call__ File "/usr/lib64/python3.6/site-packages/yui.py", line 5571 in setValue File "/usr/lib/python3.6/site-packages/dnfdragora/progress_ui.py", line 77 in set_progress File "/usr/lib/python3.6/site-packages/dnfdragora/dnf_backend.py", line 229 in on_RPMProgress File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 556 in handle_dbus_signals File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 228 in _on_g_signal File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 187 in __call__ File "/usr/lib64/python3.6/site-packages/yui.py", line 5571 in setValue File "/usr/lib/python3.6/site-packages/dnfdragora/progress_ui.py", line 77 in set_progress File "/usr/lib/python3.6/site-packages/dnfdragora/dnf_backend.py", line 229 in on_RPMProgress File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 556 in handle_dbus_signals File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 228 in _on_g_signal File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 187 in __call__ File "/usr/lib64/python3.6/site-packages/yui.py", line 5571 in setValue File "/usr/lib/python3.6/site-packages/dnfdragora/progress_ui.py", line 77 in set_progress File "/usr/lib/python3.6/site-packages/dnfdragora/dnf_backend.py", line 229 in on_RPMProgress File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 556 in handle_dbus_signals File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 228 in _on_g_signal File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 187 in __call__ File "/usr/lib64/python3.6/site-packages/yui.py", line 5571 in setValue File "/usr/lib/python3.6/site-packages/dnfdragora/progress_ui.py", line 77 in set_progress File "/usr/lib/python3.6/site-packages/dnfdragora/dnf_backend.py", line 229 in on_RPMProgress File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 556 in handle_dbus_signals File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 228 in _on_g_signal File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 187 in __call__ File "/usr/lib64/python3.6/site-packages/yui.py", line 5571 in setValue File "/usr/lib/python3.6/site-packages/dnfdragora/progress_ui.py", line 77 in set_progress File "/usr/lib/python3.6/site-packages/dnfdragora/dnf_backend.py", line 229 in on_RPMProgress File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 556 in handle_dbus_signals File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 228 in _on_g_signal File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 187 in __call__ File "/usr/lib64/python3.6/site-packages/yui.py", line 5571 in setValue File "/usr/lib/python3.6/site-packages/dnfdragora/progress_ui.py", line 77 in set_progress File "/usr/lib/python3.6/site-packages/dnfdragora/dnf_backend.py", line 229 in on_RPMProgress File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 556 in handle_dbus_signals File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 228 in _on_g_signal File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 187 in __call__ File "/usr/lib64/python3.6/site-packages/yui.py", line 5571 in setValue File "/usr/lib/python3.6/site-packages/dnfdragora/progress_ui.py", line 77 in set_progress File "/usr/lib/python3.6/site-packages/dnfdragora/dnf_backend.py", line 229 in on_RPMProgress File "/usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py", line 556 in handle_dbus_signals ... Aborted (core dumped) Version-Release number of selected component: dnfdragora-1.0.0-11.git20170401.b97db68.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/python3 /usr/bin/dnfdragora --update-only crash_function: Py_FatalError executable: /usr/bin/python3.6 global_pid: 337 kernel: 4.11.0-0.rc4.git0.1.fc26.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 Py_FatalError at /usr/src/debug/Python-3.6.0/Python/pylifecycle.c:1490 #3 _Py_CheckRecursiveCall at /usr/src/debug/Python-3.6.0/Python/ceval.c:651 #4 _PyObject_FastCallDict at /usr/src/debug/Python-3.6.0/Objects/abstract.c:2290 #5 _PyObject_CallMethodId at /usr/src/debug/Python-3.6.0/Objects/abstract.c:2624 #6 flush_std_files at /usr/src/debug/Python-3.6.0/Python/pylifecycle.c:548 #7 Py_FatalError at /usr/src/debug/Python-3.6.0/Python/pylifecycle.c:1469 #8 _Py_CheckRecursiveCall at /usr/src/debug/Python-3.6.0/Python/ceval.c:651 #9 _PyEval_EvalFrameDefault at /usr/src/debug/Python-3.6.0/Python/ceval.c:1003 #10 _PyEval_EvalCodeWithName at /usr/src/debug/Python-3.6.0/Python/ceval.c:4119 #11 _PyFunction_FastCallDict at /usr/src/debug/Python-3.6.0/Python/ceval.c:5021
Created attachment 1268964 [details] File: backtrace
Created attachment 1268965 [details] File: cgroup
Created attachment 1268966 [details] File: core_backtrace
Created attachment 1268967 [details] File: dso_list
Created attachment 1268968 [details] File: environ
Created attachment 1268969 [details] File: limits
Created attachment 1268970 [details] File: maps
Created attachment 1268971 [details] File: mountinfo
Created attachment 1268972 [details] File: namespaces
Created attachment 1268973 [details] File: open_fds
Created attachment 1268974 [details] File: proc_pid_status
Created attachment 1268975 [details] File: var_log_messages
This problem has already been reported; further investigation showed, that it is coming from the libyui-gtk-backend. *** This bug has been marked as a duplicate of bug 1436451 ***
libyui-qt-2.47.1-1.fc25 libyui-ncurses-2.48.1-1.fc25 libyui-mga-qt-1.0.3-0.7.gitb508e88.20140119.fc25 libyui-mga-ncurses-1.0.2-0.7.git026f2e6.20131215.fc25 libyui-mga-gtk-1.0.2-0.8.git22f2cf6.20131215.fc25 libyui-mga-1.0.8-0.6.gita6a160e.20160313.fc25 libyui-gtk-2.44.8-2.fc25 libyui-3.2.9-1.fc25 dnfdragora-1.0.0-18.git20170411.6098816.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-249b0d135b
libyui-qt-2.47.1-1.fc26 libyui-ncurses-2.48.1-1.fc26 libyui-mga-qt-1.0.3-0.7.gitb508e88.20140119.fc26 libyui-mga-ncurses-1.0.2-0.7.git026f2e6.20131215.fc26 libyui-mga-gtk-1.0.2-0.8.git22f2cf6.20131215.fc26 libyui-mga-1.0.8-0.6.gita6a160e.20160313.fc26 libyui-gtk-2.44.8-2.fc26 libyui-3.2.9-1.fc26 dnfdragora-1.0.0-18.git20170411.6098816.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-25e38f541d
dnfdragora-1.0.0-18.git20170411.6098816.fc25, libyui-3.2.9-1.fc25, libyui-gtk-2.44.8-2.fc25, libyui-mga-1.0.8-0.6.gita6a160e.20160313.fc25, libyui-mga-gtk-1.0.2-0.8.git22f2cf6.20131215.fc25, libyui-mga-ncurses-1.0.2-0.7.git026f2e6.20131215.fc25, libyui-mga-qt-1.0.3-0.7.gitb508e88.20140119.fc25, libyui-ncurses-2.48.1-1.fc25, libyui-qt-2.47.1-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-249b0d135b
dnfdragora-1.0.0-18.git20170411.6098816.fc26, libyui-3.2.9-1.fc26, libyui-gtk-2.44.8-2.fc26, libyui-mga-1.0.8-0.6.gita6a160e.20160313.fc26, libyui-mga-gtk-1.0.2-0.8.git22f2cf6.20131215.fc26, libyui-mga-ncurses-1.0.2-0.7.git026f2e6.20131215.fc26, libyui-mga-qt-1.0.3-0.7.gitb508e88.20140119.fc26, libyui-ncurses-2.48.1-1.fc26, libyui-qt-2.47.1-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-25e38f541d
dnfdragora-1.0.0-19.git20170411.3662635.fc26 libyui-3.2.9-1.fc26 libyui-gtk-2.44.8-2.fc26 libyui-mga-1.0.8-0.6.gita6a160e.20160313.fc26 libyui-mga-gtk-1.0.2-0.8.git22f2cf6.20131215.fc26 libyui-mga-ncurses-1.0.2-0.7.git026f2e6.20131215.fc26 libyui-mga-qt-1.0.3-0.7.gitb508e88.20140119.fc26 libyui-ncurses-2.48.1-1.fc26 libyui-qt-2.47.1-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-25e38f541d
dnfdragora-1.0.0-19.git20170411.3662635.fc25 libyui-3.2.9-1.fc25 libyui-gtk-2.44.8-2.fc25 libyui-mga-1.0.8-0.6.gita6a160e.20160313.fc25 libyui-mga-gtk-1.0.2-0.8.git22f2cf6.20131215.fc25 libyui-mga-ncurses-1.0.2-0.7.git026f2e6.20131215.fc25 libyui-mga-qt-1.0.3-0.7.gitb508e88.20140119.fc25 libyui-ncurses-2.48.1-1.fc25 libyui-qt-2.47.1-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-249b0d135b
dnfdragora-1.0.0-19.git20170411.3662635.fc25, libyui-3.2.9-1.fc25, libyui-gtk-2.44.8-2.fc25, libyui-mga-1.0.8-0.6.gita6a160e.20160313.fc25, libyui-mga-gtk-1.0.2-0.8.git22f2cf6.20131215.fc25, libyui-mga-ncurses-1.0.2-0.7.git026f2e6.20131215.fc25, libyui-mga-qt-1.0.3-0.7.gitb508e88.20140119.fc25, libyui-ncurses-2.48.1-1.fc25, libyui-qt-2.47.1-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-249b0d135b
dnfdragora-1.0.0-19.git20170411.3662635.fc26, libyui-3.2.9-1.fc26, libyui-gtk-2.44.8-2.fc26, libyui-mga-1.0.8-0.6.gita6a160e.20160313.fc26, libyui-mga-gtk-1.0.2-0.8.git22f2cf6.20131215.fc26, libyui-mga-ncurses-1.0.2-0.7.git026f2e6.20131215.fc26, libyui-mga-qt-1.0.3-0.7.gitb508e88.20140119.fc26, libyui-ncurses-2.48.1-1.fc26, libyui-qt-2.47.1-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-25e38f541d
dnfdragora-1.0.0-19.git20170411.3662635.fc26 libyui-3.2.9-1.fc26 libyui-gtk-2.44.8-3.fc26 libyui-mga-1.0.8-0.6.gita6a160e.20160313.fc26 libyui-mga-gtk-1.0.2-0.8.git22f2cf6.20131215.fc26 libyui-mga-ncurses-1.0.2-0.7.git026f2e6.20131215.fc26 libyui-mga-qt-1.0.3-0.7.gitb508e88.20140119.fc26 libyui-ncurses-2.48.1-2.fc26 libyui-qt-2.47.1-2.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-25e38f541d
dnfdragora-1.0.0-19.git20170411.3662635.fc25 libyui-3.2.9-1.fc25 libyui-gtk-2.44.8-3.fc25 libyui-mga-gtk-1.0.2-0.8.git22f2cf6.20131215.fc25 libyui-mga-ncurses-1.0.2-0.7.git026f2e6.20131215.fc25 libyui-mga-qt-1.0.3-0.7.gitb508e88.20140119.fc25 libyui-ncurses-2.48.1-2.fc25 libyui-qt-2.47.1-2.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-249b0d135b
dnfdragora-1.0.0-19.git20170411.3662635.fc25, libyui-3.2.9-1.fc25, libyui-gtk-2.44.8-3.fc25, libyui-mga-gtk-1.0.2-0.8.git22f2cf6.20131215.fc25, libyui-mga-ncurses-1.0.2-0.7.git026f2e6.20131215.fc25, libyui-mga-qt-1.0.3-0.7.gitb508e88.20140119.fc25, libyui-ncurses-2.48.1-2.fc25, libyui-qt-2.47.1-2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-249b0d135b
dnfdragora-1.0.0-19.git20170411.3662635.fc25 libyui-3.3.0-1.fc25 libyui-bindings-1.1.1-13.fc25 libyui-gtk-2.44.8-4.fc25 libyui-mga-1.0.8-0.7.gita6a160e.20160313.fc25 libyui-mga-gtk-1.0.2-0.9.git22f2cf6.20131215.fc25 libyui-mga-ncurses-1.0.2-0.8.git026f2e6.20131215.fc25 libyui-mga-qt-1.0.3-0.8.gitb508e88.20140119.fc25 libyui-ncurses-2.48.1-3.fc25 libyui-qt-2.47.1-3.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-249b0d135b
dnfdragora-1.0.0-19.git20170411.3662635.fc26, libyui-3.2.9-1.fc26, libyui-gtk-2.44.8-3.fc26, libyui-mga-1.0.8-0.6.gita6a160e.20160313.fc26, libyui-mga-gtk-1.0.2-0.8.git22f2cf6.20131215.fc26, libyui-mga-ncurses-1.0.2-0.7.git026f2e6.20131215.fc26, libyui-mga-qt-1.0.3-0.7.gitb508e88.20140119.fc26, libyui-ncurses-2.48.1-2.fc26, libyui-qt-2.47.1-2.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-25e38f541d
dnfdragora-1.0.0-19.git20170411.3662635.fc26 libyui-3.3.1-1.fc26 libyui-bindings-1.1.1-13.fc26 libyui-gtk-2.44.8-4.fc26 libyui-mga-1.0.8-0.7.gita6a160e.20160313.fc26 libyui-mga-gtk-1.0.2-0.9.git22f2cf6.20131215.fc26 libyui-mga-ncurses-1.0.2-0.8.git026f2e6.20131215.fc26 libyui-mga-qt-1.0.3-0.8.gitb508e88.20140119.fc26 libyui-ncurses-2.48.1-3.fc26 libyui-qt-2.47.1-3.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-25e38f541d
dnfdragora-1.0.0-19.git20170411.3662635.fc24 libyui-3.3.1-1.fc24 libyui-bindings-1.1.2-1.fc24 libyui-gtk-2.44.8-4.fc24 libyui-mga-1.0.8-0.7.gita6a160e.20160313.fc24 libyui-mga-gtk-1.0.2-0.9.git22f2cf6.20131215.fc24 libyui-mga-ncurses-1.0.2-0.8.git026f2e6.20131215.fc24 libyui-mga-qt-1.0.3-0.8.gitb508e88.20140119.fc24 libyui-ncurses-2.48.1-3.fc24 libyui-qt-2.47.1-3.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-9226fb42a0
dnfdragora-1.0.0-19.git20170411.3662635.fc24, libyui-3.3.1-4.fc24, libyui-bindings-1.1.2-1.fc24, libyui-gtk-2.44.8-4.fc24, libyui-mga-1.0.8-0.7.gita6a160e.20160313.fc24, libyui-mga-gtk-1.0.2-0.9.git22f2cf6.20131215.fc24, libyui-mga-ncurses-1.0.2-0.8.git026f2e6.20131215.fc24, libyui-mga-qt-1.0.3-0.8.gitb508e88.20140119.fc24, libyui-ncurses-2.48.1-3.fc24, libyui-qt-2.47.1-3.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-9226fb42a0
dnfdragora-1.0.0-19.git20170411.3662635.fc25, libyui-3.3.1-4.fc25, libyui-bindings-1.1.2-1.fc25, libyui-gtk-2.44.8-4.fc25, libyui-mga-1.0.8-0.7.gita6a160e.20160313.fc25, libyui-mga-gtk-1.0.2-0.9.git22f2cf6.20131215.fc25, libyui-mga-ncurses-1.0.2-0.8.git026f2e6.20131215.fc25, libyui-mga-qt-1.0.3-0.8.gitb508e88.20140119.fc25, libyui-ncurses-2.48.1-3.fc25, libyui-qt-2.47.1-3.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-249b0d135b
dnfdragora-1.0.0-19.git20170411.3662635.fc26, libyui-3.3.1-4.fc26, libyui-bindings-1.1.2-1.fc26, libyui-gtk-2.44.8-4.fc26, libyui-mga-1.0.8-0.7.gita6a160e.20160313.fc26, libyui-mga-gtk-1.0.2-0.9.git22f2cf6.20131215.fc26, libyui-mga-ncurses-1.0.2-0.8.git026f2e6.20131215.fc26, libyui-mga-qt-1.0.3-0.8.gitb508e88.20140119.fc26, libyui-ncurses-2.48.1-3.fc26, libyui-qt-2.47.1-3.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-25e38f541d
dnfdragora-1.0.0-19.git20170411.3662635.fc26, libyui-3.3.1-4.fc26, libyui-bindings-1.1.2-1.fc26, libyui-gtk-2.44.8-4.fc26, libyui-mga-1.0.8-0.7.gita6a160e.20160313.fc26, libyui-mga-gtk-1.0.2-0.9.git22f2cf6.20131215.fc26, libyui-mga-ncurses-1.0.2-0.8.git026f2e6.20131215.fc26, libyui-mga-qt-1.0.3-0.8.gitb508e88.20140119.fc26, libyui-ncurses-2.48.1-3.fc26, libyui-qt-2.47.1-3.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
dnfdragora-1.0.0-19.git20170411.3662635.fc24, libyui-3.3.1-4.fc24, libyui-bindings-1.1.2-1.fc24, libyui-gtk-2.44.8-4.fc24, libyui-mga-1.0.8-0.7.gita6a160e.20160313.fc24, libyui-mga-gtk-1.0.2-0.9.git22f2cf6.20131215.fc24, libyui-mga-ncurses-1.0.2-0.8.git026f2e6.20131215.fc24, libyui-mga-qt-1.0.3-0.8.gitb508e88.20140119.fc24, libyui-ncurses-2.48.1-3.fc24, libyui-qt-2.47.1-3.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
dnfdragora-1.0.0-19.git20170411.3662635.fc25, libyui-3.3.1-4.fc25, libyui-bindings-1.1.2-1.fc25, libyui-gtk-2.44.8-4.fc25, libyui-mga-1.0.8-0.7.gita6a160e.20160313.fc25, libyui-mga-gtk-1.0.2-0.9.git22f2cf6.20131215.fc25, libyui-mga-ncurses-1.0.2-0.8.git026f2e6.20131215.fc25, libyui-mga-qt-1.0.3-0.8.gitb508e88.20140119.fc25, libyui-ncurses-2.48.1-3.fc25, libyui-qt-2.47.1-3.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 1512910 has been marked as a duplicate of this bug. ***