Created attachment 317857 [details] Screenshot showing the problem on a Fedora 9 system See the screenshot attached. Whatever the error that stops packages being installed, the notification windows should appear just once, and not pile up on top of each other. At the moment a new one appears about once a second and one disappears about once a second, so the corner of the screen is a queue of flashing and vanishing messages. Pressing 'Cancel update' or 'Do not show this again' has no effect. (PS it says 'More information is available in the detailed report' but there is no link or button to click to view that report - but that might deserve a separate bug. Let me know if there is some logfile that I can send.) I don't have to do anything special to produce this error - it just happens after I boot the system and log in. It only started recently after some package updates were installed.
Attaching an additional screenshot showing another case where the notification windows pile up. I have moved some of them away from the centre of the screen: in all about 90 of them are open.
Created attachment 320143 [details] Screenshot showing endless 'authorization could not be obtained' messages I believe these 'authorization could not be obtained' messages may be produced when you log in, then use the user switcher to log in as someone else, then after some time go back to your original session. The bug is not that authorization couldn't be obtained, or any other reason why packages could not be installed. The bug is that messages keep popping up on top of each other rather than just reporting the problem once.
Just got the same problem with Fedora 10. I've got automatic updates switched on, and am using RPMfusion to get the ATI driver. Obviously the RPMfusion guys have uploaded a new version of the driver and the corresponding kernel package hasn't hit my Fedora mirror yet: tore@wrath:~$ sudo yum upgrade Loaded plugins: changelog, refresh-packagekit Existing lock /var/run/yum.pid: another copy is running as pid 18561. Another app is currently holding the yum lock; waiting for it to exit... Setting up Upgrade Process Resolving Dependencies --> Running transaction check ---> Package kmod-fglrx.i686 0:9.2-2.fc10.1 set to be updated --> Processing Dependency: kmod-fglrx-2.6.27.19-170.2.35.fc10.i686 >= 9.2-2.fc10.1 for package: kmod-fglrx --> Running transaction check ---> Package kmod-fglrx-2.6.27.19-170.2.35.fc10.i686.i686 0:9.2-2.fc10.1 set to be updated --> Processing Dependency: kernel-uname-r = 2.6.27.19-170.2.35.fc10.i686 for package: kmod-fglrx-2.6.27.19-170.2.35.fc10.i686 --> Finished Dependency Resolution kmod-fglrx-2.6.27.19-170.2.35.fc10.i686-9.2-2.fc10.1.i686 from rpmfusion-nonfree-updates-testing has depsolving problems --> Missing Dependency: kernel-uname-r = 2.6.27.19-170.2.35.fc10.i686 is needed by package kmod-fglrx-2.6.27.19-170.2.35.fc10.i686-9.2-2.fc10.1.i686 (rpmfusion-nonfree-updates-testing) Error: Missing Dependency: kernel-uname-r = 2.6.27.19-170.2.35.fc10.i686 is needed by package kmod-fglrx-2.6.27.19-170.2.35.fc10.i686-9.2-2.fc10.1.i686 (rpmfusion-nonfree-updates-testing) If the automatic upgrade applet runs into this situation it should just keep retrying and retrying every second (and spamming warnings), but back off for a while before it retries, IMHO. Turning off automatic updates helps. Tore
Does this still happen with the version in fedora rawhide, or the version of the Fedora 11 beta live cd? Thanks.
This still occurs with Fedora 10 - I will try Fedora 11 shortly (as soon as I can get preupgrade working...).
Any luck on that F11 testing?
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. 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 WONTFIX if it remains open with a Fedora 'version' of '9'. 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 prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Updating version to 10 since it does occur on Fedora 10. I haven't seen it since upgrading to Fedora 11, but will try to reproduce it.