Description of problem:
Upgraded F20 --> F21 via 'fedup'
Succsessfully compleated distrosync
Update notification appeared informing of an update and I attempted to install via it.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 repo_internalize_trigger at /usr/src/debug/hawkey-85826ee4905b0422e3490fc2aa1b6d9bd6a302b2/py3/src/repo.c:60
#1 repo_internalize_all_trigger at /usr/src/debug/hawkey-85826ee4905b0422e3490fc2aa1b6d9bd6a302b2/py3/src/repo.c:52
#2 solve at /usr/src/debug/hawkey-85826ee4905b0422e3490fc2aa1b6d9bd6a302b2/py3/src/goal.c:256
#3 hy_goal_run_all_flags at /usr/src/debug/hawkey-85826ee4905b0422e3490fc2aa1b6d9bd6a302b2/py3/src/goal.c:789
#4 hy_goal_run_flags at /usr/src/debug/hawkey-85826ee4905b0422e3490fc2aa1b6d9bd6a302b2/py3/src/goal.c:775
#5 hif_goal_depsolve at hif-goal.c:58
#6 hif_transaction_depsolve at hif-transaction.c:1076
#7 pk_backend_transaction_run at pk-backend-hif.c:2299
#8 pk_backend_update_packages_thread at pk-backend-hif.c:3156
#9 pk_backend_job_thread_setup at pk-backend-job.c:815
Created attachment 997200 [details]
Created attachment 997201 [details]
Created attachment 997202 [details]
Created attachment 997203 [details]
Created attachment 997204 [details]
Created attachment 997205 [details]
Created attachment 997206 [details]
Created attachment 997207 [details]
Created attachment 997208 [details]
Created attachment 997209 [details]
Created attachment 997210 [details]
*** Bug 1215440 has been marked as a duplicate of this bug. ***
Looks like it's crashing in repo_internalize_trigger() in hawkey, dereferencing NULL hrepo. Reassigning to hawkey.
Kalev, attach the test case which fails in hawkey, please. We have never encountered this traceback in DNF.
I don't know how to reproduce it; it's just an abrt crash.
wintonian, you reported this, do you know how to reproduce it?
Blimey, given the fast paced world of Fedora I'm thinking about upgrading to F22 now. :-)
I'm fairly sure I just did a normal fedup upgrade from F20-21 using the Fedora wiki guide as I normally do i.e.
sudo update fedup
sudo fedup --network 21 --product=nonproduct (I use KDE)
Reboot choosing "System Upgrade" from grub (and issue LUKS password at prompt)
When upgrade has finished:
sudo rpm --rebuilddb
sudo yum distro-sync --setopt=deltarpm=0
If memory serves me right the update notification appeared in the notification bar (don't remember what the package was) and I hit "install" that is the point the crash occurred.
I assume I then ran "sudo yum update" as I don't recall it being a problem as such and passed it off as one of those freak unexplained crashes that never reoccur.
I'm pretty sure I don't have a disk image from that far back, but I'll have a look and if I do find one I might see if I can recreate it.
Sorry that's probably not much help.
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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'
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 21 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.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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
Thank you for reporting this bug and we are sorry it could not be fixed.