Bug 567346 - gpk-update-viewer does not install updates if there is any dependency issue, and does not correctly report this
Summary: gpk-update-viewer does not install updates if there is any dependency issue, ...
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-packagekit   
(Show other bugs)
Version: 13
Hardware: All Linux
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
Whiteboard: https://fedoraproject.org/wiki/Common...
Keywords: CommonBugs
Depends On:
Blocks: F13Beta, F13BetaBlocker
TreeView+ depends on / blocked
Reported: 2010-02-22 17:34 UTC by Kamil Páral
Modified: 2013-01-10 05:44 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-04-06 16:31:22 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
bug demonstration video (1.46 MB, video/ogg)
2010-02-22 17:34 UTC, Kamil Páral
no flags Details
system logs (55.64 KB, application/x-gzip)
2010-02-22 17:34 UTC, Kamil Páral
no flags Details
pkmon output (18.24 KB, text/plain)
2010-02-22 17:45 UTC, Kamil Páral
no flags Details
pkmon --verbose (59.53 KB, text/plain)
2010-02-26 21:13 UTC, James Laska
no flags Details
yum update log (14.22 KB, text/plain)
2010-03-01 16:01 UTC, Josef Skladanka
no flags Details
system logs when langpack plugin installed (277.67 KB, application/x-gzip)
2010-03-03 12:23 UTC, He Rui
no flags Details
yum's interpretation of the troublesome update set (10.26 KB, text/plain)
2010-03-24 15:08 UTC, Adam Williamson
no flags Details

Description Kamil Páral 2010-02-22 17:34:13 UTC
Created attachment 395521 [details]
bug demonstration video

Description of problem:
gpk-update-viewer does not show changelogs for packages, it just displays "Loading..." indefinitely. Also when a package is updated, it is reported as successfully updated, but it is not updated for real and it again shows in the list. Also there is a crash when running the gpk-update-viewer after an update. Please see attached video.

Version-Release number of selected component (if applicable):
I used nightly live image desktop-x86_64-20100221.16.iso available from
http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/. The Rawhide repository was enabled. SELinux was in permissive mode.

How reproducible:

Steps to Reproduce:
1. Show list of updates
2. Select one, try to watch changelog
3. Try to update one package, then run gpk-update-viewer again
Actual results:
Changelog is not displayed, it crashed on second run, does not update packages.

Expected results:
Changelog is displayed, no crash is observed on second run, updated package if not falsely reported as updated.

Additional info:

Comment 1 Kamil Páral 2010-02-22 17:34:31 UTC
Created attachment 395522 [details]
system logs

Comment 2 Kamil Páral 2010-02-22 17:45:56 UTC
Created attachment 395524 [details]
pkmon output

Here is 'pkmon --verbose' output when I did exactly what is seen on the video (tried to update anaconda package).

Also I would like to note that when I try to update all the packages, the gpk-update-viewer just waits indefinitely, I have to press Quit.

Comment 3 Jesse Keating 2010-02-23 02:26:21 UTC
Any progress on this?

Comment 4 Kamil Páral 2010-02-23 08:58:40 UTC
Still a problem in desktop-x86_64-20100222.19.iso.

Comment 5 James Laska 2010-02-24 18:49:05 UTC
I'm seeing this to after a fresh install of F-13-Alpha-RC2 using a newly created user account.

No packages are listed when searching or selecting package groups in gpk-application.  I manually started 'pkmon --verbose' from a terminal window, and then gpk-application appears to show packages.

Could it be that pkmon crashed or failed to start?

Comment 6 Jesse Keating 2010-02-25 19:11:44 UTC
This is fixed in gnome-packagekit and PackageKit Working their way through testing now.

Comment 7 James Laska 2010-02-26 14:32:38 UTC
(In reply to comment #6)
> This is fixed in gnome-packagekit and PackageKit Working their way through
> testing now.    

Still seeing problems testing after a fresh default install of F-13-Alpha-RC4-{i386,x86_64}.

This bug is in MODIFIED, yet there is no indication what version it's fixed in.  Hard to tell if the correct fix is included in RC4.

Comment 8 Nathanael Noblet 2010-02-26 19:27:55 UTC
I can confirm the bug as well in RC4-i386

Comment 9 Nathanael Noblet 2010-02-26 20:36:15 UTC
Oddly enough when I install F13 on real hardware I get the changelog/update information showing up, but the installation portion still fails...

Comment 10 James Laska 2010-02-26 20:57:00 UTC
I've retested on bare metal (i386 and x86_64), and after install ... I am able to login and apply software updates without error.

Comment 11 James Laska 2010-02-26 21:01:38 UTC
(In reply to comment #10)
> I've retested on bare metal (i386 and x86_64), and after install ... I am able
> to login and apply software updates without error.    

Correction, it says "Updates installed", but gnome-packagekit hasn't done anything.  It shows the same updates available when restarting, and yum check-update lists the same updates still.


Comment 12 James Laska 2010-02-26 21:13:00 UTC
Created attachment 396676 [details]
pkmon --verbose

Comment 13 Adam Williamson 2010-02-27 01:15:41 UTC
This is okay for me, I installed RC4 from the desktop live spin into an x86-64 virt-manager VM. Ran the update application. It correctly displayed all updates, with changelogs, and installed them. It then correctly showed that no more updates were available, when run again.

Comment 14 Josef Skladanka 2010-03-01 10:29:53 UTC
I just tried on RC4 inside KVM virtual x86-64 machine (installed, not live-cd) and the bug described above does not exhibit. The changelogs are correctly shown, and once the update is installed, it's not proposed to me any more.

Comment 15 Kamil Páral 2010-03-01 11:52:51 UTC
As of today, on installed F13 Alpha RC 4 it shows changelogs and I also managed to install a single update just fine. However, when I tried to install all available updates, it again reported "All updates were installed." when nothing really happened.

I believe the problem may be connected to the current state of repository (sometime it works, sometime it doesn't). For example as of today the dependencies are broken for gimp and for openoffice.org. It may be relevant to gpk-update-viewer behaviour.

Comment 16 Josef Skladanka 2010-03-01 16:01:53 UTC
Created attachment 397099 [details]
yum update log

So I tried to upload all packages, and the beahaviour is the same as Kamil describes in #15. GUI tool says "All updates installed" but nothing really happens.

When I run yum-update, it ends with broken dependencies (log attached).

I belive, that gpk-update-viewer just is not able to digest this kind of faulty yum-update, so it says everything was installed, even though it was not.

Comment 17 Josef Skladanka 2010-03-01 16:02:46 UTC
sry guys - s/upload all packages/update all packages/ in #16

Comment 18 Kamil Páral 2010-03-01 17:16:03 UTC
I have tested this thoroughly and I am absolutely positive that the problem happens only when gpk-update-viewer tries to update a package with broken dependencies. All other packages are updated just fine, but if in the set is a package with broken dependencies, then it almost immediately reports "Updates were installed." and quits (without installing anything). Case solved. (Now only to fix the problem).

Comment 19 Nathanael Noblet 2010-03-01 21:55:15 UTC
I would  agree with the above assessment. I wasn't sure what I had done to fix my problem but I did run a yum update manually and removed open office that had problems and then was able to update the system later.. I didn't put 2 and 2 together because lots happened between the removal of open office and a second attempt at updating the system...

Comment 20 Adam Williamson 2010-03-02 04:43:59 UTC
Is it as simple as that it's no longer doing the equivalent of --skip-broken by default? PK has always done this in the past (in contrast to yum).

I've just started seeing this issue, after having two days of successful updates with PK yesterday and the day before, so definitely some transience to this issue.

Comment 21 Adam Williamson 2010-03-02 04:59:13 UTC
I think I can confirm Kamil's diagnosis. I did a 'yum upgrade' (well, actually 'yum --disableabunchofrepos upgrade' because Fusion still isn't working for F13, but hey) and it complained about kipi-plugins. So I removed that package, verified that 'yum upgrade' didn't complain any more and would have gone ahead, then ran the PK updater. Now it's working properly (in the middle of downloading packages ATM, didn't go that far before). So I believe Kamil's right: it doesn't work right if there's any dependency problems in the update set. It doesn't appear to do --skip-broken , and it obviously doesn't report the result correctly (it doesn't tell you there was a dependency problem and it couldn't do the update, it just claims it did the update).

Comment 22 Kamil Páral 2010-03-02 08:38:55 UTC
Also the yum-langpacks plugin may be part of the problem. See bug #569352.

Comment 23 Kamil Páral 2010-03-02 09:00:46 UTC
Today I have again seen gpk-update-viewer not displaying changelogs. After I have installed a single update it started to work.
Also for some reason I was able to apply all available updates via gpk-update-viewer, even though yum was showing me broken dependencies (??).

Weirder and weirder every day.

Comment 24 James Laska 2010-03-02 15:01:34 UTC
Moving back into ASSIGNED until we have a better understanding about the nature of the problem and where attempts to resolve the issue have been made.  

I've contacted Richard Hughes on #fedora-devel to see if has any insight into getting to the root of this problem.  Richard, is there information QA can provide to help isolate this failure?

Comment 25 Richard Hughes 2010-03-02 18:38:44 UTC
(In reply to comment #24)
> Richard, is there information QA can
> provide to help isolate this failure?    

Does this bug ever happen if the yum-langpacks plugin is not installed?

Comment 26 He Rui 2010-03-03 07:44:58 UTC
yum-langpacks is in Group package 'Base' under 'Base system' Category at software selection step of anaconda. 

Today I installed RC4-i386 with yum-langpacks installed by default. To narrow down the cause, when I executed gpk-update-viewer, I only installed openoffice packages which were supposed to have problems. But actually they got installed successfully without this issue happening. After installation, the package list in GUI is updated automatically and doesn't contain openoffice any more. Openoffice packages have been updated (view by 'rpm -qa') and when I 'yum update' again, there are no broken dependencies and everything seems right...

Comment 27 He Rui 2010-03-03 12:23:23 UTC
Created attachment 397546 [details]
system logs when langpack plugin installed

Wow, my test result may get this issue more complicated... I installed RC4-i386 with yum-langpacks by default. This time I selected all updates to be installed. It took ages to download the packages and then asked me for authentication. After that, it shows "updates were installed" quickly without really updating. When I click ok, "segmentation fault" shown on console. Then I restarted gpk-update-viewer. But it's grey and nothing was displayed in the forms. 

So I rebooted pc and started gpk-update-viewer. I didn't do anything before this but it was able to update all packages without error.

/var/log/ is attached.

Comment 28 James Laska 2010-03-03 13:36:07 UTC
Same result for me now.  This problem is certainly a fun one :(

1. I installed a default Fedora-13-Alpha-RC4-x86_64 system (which includes yum-langpacks).  
2. After install, I created a new local user in firstboot
3. Login as new local user
4. Run gpk-update-viewer, and attempt to update

As expected, I was prompted for priv. escalation and the update proceeded as intended.  I think kparal was accurate in stating the this bug seems to be triggered by some condition present in the repos, which may be related to, or contributed by, yum-langpacks.

I'll continue attempting to retest this issue.  For now, I think we should begin documenting this behavior for any Alpha users.  Suggested workarounds include:

1. Removing yum-langpacks ?
2. Or, using yum from the command-line ?

Comment 29 Richard Hughes 2010-03-03 13:54:27 UTC
(In reply to comment #28)
> Suggested workarounds include:

1. Removing yum-langpacks
2. Include http://lists.baseurl.org/pipermail/yum-devel/2010-March/006695.html in yum-utils f13-stable
3. Ensuring the repos do not have depsolve problems


Comment 30 Tim Lauridsen 2010-03-03 14:19:36 UTC
> 2. Include http://lists.baseurl.org/pipermail/yum-devel/2010-March/006695.html
> in yum-utils f13-stable

yum, not yum-utils :)

Comment 31 James Laska 2010-03-03 21:37:13 UTC
Prepared a CommonBugs entry attempting to explain the problem and suggested work arounds at https://fedoraproject.org/wiki/Common_F13_bugs#yum-langpacks

Comment 32 James Laska 2010-03-04 01:42:17 UTC
Moving to F13Beta per discussion at F-13-Alpha Readiness meeting.  For details, please see meeting minutes (http://meetbot.fedoraproject.org/fedora-meeting/2010-03-04/f-13-alpha-eng-readiness.2010-03-04-01.00.html).

Comment 33 Paul W. Frields 2010-03-04 15:35:02 UTC
A fix was ACK'd by skvidal and is in the yum 3.2.x tree:


Comment 34 Adam Williamson 2010-03-09 16:23:56 UTC
I'm hitting this bug today without yum-langpacks installed at all :(

the current update set as reported by yum is http://fpaste.org/XNEw/ .

If I try to install updates via gnome-packagekit, I get the 'quickly reports all updates installed, nothing is actually done' symptom.

[root@adam Download]# rpm -qa | grep yum

[root@adam Download]# rpm -qa | grep -i packagekit

Fedora Bugzappers volunteer triage team

Comment 35 Adam Williamson 2010-03-12 17:17:05 UTC

Fedora Bugzappers volunteer triage team

Comment 36 Adam Williamson 2010-03-12 17:18:48 UTC
Updating to match latest experience. AFAICT, this happens whenever there is any dependency issue in the pending update set. PK is supposed to do the equivalent of yum --skip-broken to avoid this, but this doesn't appear to be working. When you hit this bug, yum --skip-broken can install the updates, but gpk-update-viewer runs, completes very quickly and claims the update was completed, without actually updating any package.

This is a Beta blocker as it actually matches an Alpha criterion, we only did not consider it an Alpha blocker as we incorrectly thought yum-langpacks had to be installed to trigger it.

Comment 37 Adam Williamson 2010-03-18 16:01:39 UTC
Richard pushed an update he thought should fix this - gnome-packagekit-2.29.92-0.1.20100315git.fc13.x86_64 . However, with that installed (and packagekitd and gpk-update-icon restarted), I am seeing this problem again with today's update set.

Even more oddly, this time yum isn't showing any kind of dependency problem; I wouldn't have to use --skip-broken to complete the update, it seems.

Fedora Bugzappers volunteer triage team

Comment 38 Adam Williamson 2010-03-18 16:02:18 UTC
Richard, your remote login to my system should still be available if you want to take a look, poke me on IRC if you need any privileges.

Comment 39 Adam Williamson 2010-03-19 17:21:47 UTC
for the record, here's the list of updates at present:

 bodhi-client                     noarch 0.7.4-1.fc13    updates-testing   16 k
 cheese                           x86_64 2.29.92-2.fc13  updates-testing  430 k
 cheese-libs                      x86_64 2.29.92-2.fc13  updates-testing  4.1 M
 dosfstools                       x86_64 3.0.9-2.fc13    updates-testing   77 k
 dvb-apps                         x86_64 1.1.1-21.fc13   updates-testing  257 k
 ghostscript                      x86_64 8.71-9.fc13     updates-testing  4.5 M
 ghostscript-cups                 x86_64 8.71-9.fc13     updates-testing   44 k
 gnome-disk-utility               x86_64 2.30.0-1.fc13   updates-testing  273 k
 gnome-disk-utility-libs          x86_64 2.30.0-1.fc13   updates-testing  1.0 M
 gnome-disk-utility-ui-libs       x86_64 2.30.0-1.fc13   updates-testing  103 k
 gnome-icon-theme                 noarch 2.29.2-2.fc13   updates-testing  8.0 M
 libarchive                       x86_64 2.8.3-1.fc13    updates-testing  127 k
 libssh                           x86_64 0.4.2-1.fc13    updates-testing  105 k
 nautilus-sendto                  x86_64 2.28.3-1.fc13   updates-testing  163 k
 openldap                         x86_64 2.4.21-5.fc13   updates-testing  231 k
 openldap-clients                 x86_64 2.4.21-5.fc13   updates-testing  155 k
 openldap-devel                   x86_64 2.4.21-5.fc13   updates-testing  1.0 M
 phonon                           x86_64 4.4.0-1.fc13    updates-testing  155 k
 phonon-backend-xine              x86_64 4.4.0-1.fc13    updates-testing  156 k
 phonon-devel                     x86_64 4.4.0-1.fc13    updates-testing   69 k
 system-config-network            noarch 1.6.0-2.fc13    updates-testing  320 k
 system-config-network-tui        noarch 1.6.0-2.fc13    updates-testing  1.2 M
 udisks                           x86_64 1.0.0-1.fc13    updates-testing  172 k
 udisks-devel                     x86_64 1.0.0-1.fc13    updates-testing   68 k
 wxPython                         x86_64 updates-testing  8.5 M

Fedora Bugzappers volunteer triage team

Comment 40 Richard Hughes 2010-03-23 11:02:45 UTC
Adam, could you try this build please: http://koji.fedoraproject.org/koji/taskinfo?taskID=2069483 -- thanks.

Comment 41 Adam Williamson 2010-03-23 21:39:44 UTC
unfortunately f13 rolled on since then, and I had an update set of 54 packages today which installed successfully with the old PackageKit - but only after failing once and then listing '108' updates, which were the same 54 updates listed twice. Running the update process a second time with gpk-update-viewer in that odd state seemed to work.

Anyway, I'll install that build and let you know if I see any problems with it, at least.

Fedora Bugzappers volunteer triage team

Comment 42 Adam Williamson 2010-03-24 15:07:18 UTC
Hitting the bug again with today's update set :(. yum sees a dependency issue. gpk-update-viewer does the classic behaviour from above - runs through dep checks then jumps straight to 'All updates were installed successfully' without downloading or installing anything. yum output will be attached. hughsie, your login to my system is still valid.

Comment 43 Adam Williamson 2010-03-24 15:08:39 UTC
Created attachment 402329 [details]
yum's interpretation of the troublesome update set

Comment 44 Adam Williamson 2010-03-24 15:10:56 UTC
actually, I still seem to be running old PackageKit (not the build hughsie mentioned above), even though I was sure I updated it yesterday. That makes this a good test: I'll install the updated PackageKit stuff, and reboot and try again.


Comment 45 Adam Williamson 2010-03-24 15:23:57 UTC
looking good with the new PK - it's downloading packages, didn't do that before. will update if it completes.

Fedora Bugzappers volunteer triage team

Comment 46 Adam Williamson 2010-03-24 15:37:42 UTC
With the new PK, the update does run. The list of available packages goes quite wiggy during the process, though - half-way through, every update in the list is duplicated. When the update process completes, the 'A restart is required.' dialog pops up, but appears to be broken - you can't click anything. On further investigation, it turns out this is because another error dialog is blocking it, but is *behind* it: it has no window title and the text 'Could not get update details (newline) No results were returned.', and a Close button. There are two of these, I think. Closing both takes you back to the gpk-update-viewer window, which by now is saying 'There are 94 updates available' in bold at the top and '188 update selected' in the bottom right, and showing each one of 94 updates twice (for a total of 188). Even though all the updates have been installed. Quitting and restarting correctly shows just one update, the one which has the dependency issue and so wasn't installed.

So it more or less works, but it's rough :)

Comment 47 Adam Williamson 2010-03-25 18:30:55 UTC
Preparing for blocker review tomorrow - I've been using the above PK build for a couple of days without issues other than those described above. Despite the roughness, this is certainly better than without the fixes. I think we should pull this build in for Beta if no-one else has problems with it.

We may also need yum 3.2.27-2...changelog is '- broke searching in PK, this patch fixes it.'

Fedora Bugzappers volunteer triage team

Comment 48 Jesse Keating 2010-03-25 23:49:07 UTC
Setting to ON_QA, there is a build going into updates-testing.

Comment 49 Luo Bin 2010-03-28 17:15:43 UTC
I do have the same problem!
Fedora 13

Comment 50 Adam Williamson 2010-03-30 15:50:50 UTC
I'm happy with closing this once the newer PackageKit is in dist-f13, it's been working okay here. Anyone object?

Fedora Bugzappers volunteer triage team

Comment 51 Adam Williamson 2010-04-06 16:31:22 UTC
okay, no-one objected. clsoing.

Fedora Bugzappers volunteer triage team

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