Bug 1828911 - Dnf dragora crashes immediately after repos checking
Summary: Dnf dragora crashes immediately after repos checking
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: dnfdragora
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Neal Gompa
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-28 15:00 UTC by antonio montagnani
Modified: 2021-05-25 17:19 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-25 17:19:28 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
log of su- (4.62 KB, text/plain)
2020-04-29 05:16 UTC, antonio montagnani
no flags Details
after reinstallation (4.76 KB, text/plain)
2020-04-30 13:06 UTC, antonio montagnani
no flags Details

Description antonio montagnani 2020-04-28 15:00:48 UTC
Description of problem:
dnfdragora crashes, window is closed after checking repos, i.e. after all lines are at 100%

Version-Release number of selected component (if applicable):
2.0.0-2.fc32

How reproducible:
always

Steps to Reproduce:
1.just start dnfdragora and wait
2.
3.

Actual results:
immediate crash

Expected results:
it should workas expected

Additional info:
I am running 5.6.7-300.fc32 kernel but same behaviour with 5.6.6-300.fc32

Comment 1 Mik Nerts 2020-04-28 20:33:29 UTC
I've just upgraded from 31 to (Fedora) 32 and I have the exact same issue, but if I execute, in a terminal window, "sudo dnfdragora" then it will not crash and behaves as expected!

Comment 2 antonio montagnani 2020-04-29 05:14:01 UTC
su
Password: 
[root@fujitsu antonio]# dnfdragora
dnfdaemon client failure [g-io-error-quark: Error sending credentials: Error sending message: Broken pipe (44)]
Try again using a login shell (i.e. "su -")


I am not a sudoer but with su - it works (see attached file)

Comment 3 antonio montagnani 2020-04-29 05:16:01 UTC
Created attachment 1682691 [details]
log of su-

see attached file for using su -

Comment 4 Norbert Jurkeit 2020-04-30 10:31:08 UTC
I ran into the same issue after a fresh installation of F32, but with retaining the existing /home partition. Deleting file ~/.config/dnfdragora.yaml which was created by an earlier version solved the issue for me.

Comment 5 antonio montagnani 2020-04-30 13:06:28 UTC
Created attachment 1683307 [details]
after reinstallation

I removed & reinstalled dnfdragora. Now even if I use su- UI is closed after a while. My F32 is updated to few minutes ago

Comment 6 antonio montagnani 2020-04-30 13:43:08 UTC
(In reply to Norbert Jurkeit from comment #4)
> I ran into the same issue after a fresh installation of F32, but with
> retaining the existing /home partition. Deleting file
> ~/.config/dnfdragora.yaml which was created by an earlier version solved the
> issue for me.


yes, it solved the crash, I had to >dnf clean all before having dnfdragora working as expected. I do not know that this happens also in a fresh installation, my systems were upgraded from F31. Tnx for the tip

Comment 7 Mik Nerts 2020-05-01 02:45:55 UTC
(In reply to Norbert Jurkeit from comment #4)
> I ran into the same issue after a fresh installation of F32, but with
> retaining the existing /home partition. Deleting file
> ~/.config/dnfdragora.yaml which was created by an earlier version solved the
> issue for me.

Thank you!
I can confirm that by doing the same, on my PC, the problem was resolved!

Comment 8 Fedora Program Management 2021-04-29 16:53:05 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Ben Cotton 2021-05-25 17:19:28 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.