Bug 769790

Summary: Online Update with All Patches crashes
Product: [openSUSE] openSUSE 12.1 Reporter: James Rome <jamesrome>
Component: YaST2Assignee: Ladislav Slezák <lslezak>
Status: RESOLVED INVALID QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P5 - None CC: meissner, tgoettlicher
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: The Yast2 log
My repositories
whole YaSt2 directory

Description James Rome 2012-07-03 13:38:48 UTC
Created attachment 497264 [details]
The Yast2 log

User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20100101 Firefox/13.0.1

I have not been seeing the lastest security updates for 12.1 (e.g., the kernel and mysql), so I told Yast2 Online Update to display "All Patches" and sure enough, there they are. But every time I press Accept, Yast2 crashes as soon as the next screen is displayed.

The logs have:
Jul  3 09:32:54 jarfx dbus[1369]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Jul  3 09:32:54 jarfx dbus-daemon[1369]: dbus[1369]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Jul  3 09:32:54 jarfx dbus-daemon[1369]: (packagekitd:5939): PackageKit-Zypp-DEBUG: zypp_backend_initialize
Jul  3 09:32:54 jarfx dbus[1369]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Jul  3 09:32:54 jarfx dbus-daemon[1369]: dbus[1369]: [system] Successfully activated service 'org.freedesktop.PackageKit'

Reproducible: Always

Steps to Reproduce:
1. Run Online update. No patches are displayed.
2. Select "All Patches"
3.  Press "Accept"
4. It crashes.


Expected Results:  
Installed the patches
Comment 1 James Rome 2012-07-03 13:41:49 UTC
Also, I tried to install the kernel patch manually as per 
openSUSE-SU-2012:0812-1: moderate: Kernel update
This fails too:
zypper in -t patch openSUSE-2012-357
PackageKit is blocking zypper. This happens if you have an updater applet or other software management application using PackageKit running.
Tell PackageKit to quit? [yes/no] (no): y
Jul  3 09:39:11 jarfx dbus-daemon[1369]: (packagekitd:6165): PackageKit-Zypp-DEBUG: zypp_backend_destroy
Loading repository data...
Reading installed packages...
'openSUSE-2012-357' not found in package names. Trying capabilities.
No provider of 'patch:openSUSE-2012-357' found.
Resolving package dependencies...

Nothing to do.
Comment 2 James Rome 2012-07-03 13:44:00 UTC
Created attachment 497266 [details]
My repositories

Am I missing a repository?
Comment 3 Marcus Meissner 2012-07-03 14:21:01 UTC
the update repository is added.

run:

zypper refresh
zypper patch
Comment 4 James Rome 2012-07-03 14:29:39 UTC
Alas, that did not help.

#zypper refresh
Repository 'Updates for openSUSE 12.1 12.1-1.4' is up to date.
Repository 'nVidia Graphics Drivers' is up to date.
Repository 'openSUSE BuildService - GNOME:Apps' is up to date.
Repository 'openSUSE BuildService - KDE:KDE3' is up to date.
Repository 'openSUSE BuildService - LibreOffice' is up to date.
Repository 'openSUSE BuildService - KDE:UpdatedApps' is up to date.
Repository 'openSUSE BuildService - Database' is up to date.
Repository 'openSUSE BuildService - Mozilla' is up to date.
Retrieving repository 'openSUSE BuildService - Java:packages' metadata [\]
File 'repomd.xml' from repository 'openSUSE BuildService - Java:packages' is signed with an unknown key 'F7B4039CC2C0E8D4'. Continue? [yes/no] (no): yes
Invalid answer 'zypper patchyes'. Enter 'y' for 'yes' or 'n' for 'no' if nothing else works for you. [yes/no] (no): y  
Retrieving repository 'openSUSE BuildService - Java:packages' metadata [done]
Building repository 'openSUSE BuildService - Java:packages' cache [done]
Repository 'openSUSE BuildService - devel:languages:perl' is up to date.
Repository 'openSUSE BuildService - PHP' is up to date.
Repository 'openSUSE BuildService - devel:languages:python' is up to date.
Repository 'libdvdcss repository' is up to date.
Repository 'Packman Repository' is up to date.
Repository 'openSUSE-12.1-Debug' is up to date.
Repository 'openSUSE-12.1-Update-Debug' is up to date.
Repository 'openSUSE-12.1-Non-Oss' is up to date.
Repository 'openSUSE-12.1-Oss' is up to date.
Repository 'openSUSE-12.1-Source' is up to date.All repositories have been refreshed.

jarfx:/var/log/YaST2 # zypper patch
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Nothing to do.

 # zypper in -t patch openSUSE-2012-357
Loading repository data...
Reading installed packages...
'openSUSE-2012-357' not found in package names. Trying capabilities.
No provider of 'patch:openSUSE-2012-357' found.
Resolving package dependencies...

Nothing to do.
Comment 5 James Rome 2012-07-03 14:35:38 UTC
Also, my kernel is definitely NOT up to date:
jarfx:/var/log/YaST2 # ls /boot
backup_mbr  boot.readme                grub    initrd-3.1.10-1.9-desktop  symvers-3.1.10-1.9-desktop.gz   System.map-3.1.10-1.9-desktop  vmlinuz
boot        config-3.1.10-1.9-desktop  initrd  message                    sysctl.conf-3.1.10-1.9-desktop  vmlinux-3.1.10-1.9-desktop.gz  vmlinuz-3.1.10-1.9-desktop
Comment 6 Marcus Meissner 2012-07-03 14:53:30 UTC
the update repo is not yet published after the release.

please just wait a bit.
Comment 7 Marcus Meissner 2012-07-03 14:53:57 UTC
actually it was published now.. please test again
Comment 8 James Rome 2012-07-03 16:47:10 UTC
It worked for the kernel, but not for the other updates, such as mysql. After a reboot, Yast2 Online Update still crashes if I select all patches.
Comment 10 James Rome 2012-07-06 12:21:43 UTC
Created attachment 497643 [details]
whole YaSt2 directory
Comment 11 James Rome 2012-07-06 12:22:23 UTC
Could it be that this is normal behavior (the window disappearing) if there is nothing to do?
Comment 12 Ladislav Slezák 2012-07-20 10:17:36 UTC
(In reply to comment #11)
> Could it be that this is normal behavior (the window disappearing) if there is
> nothing to do?

Yes, this is expected when there are no applicable patches - all patches already installed or not applicable (patches for packages which are not installed).

"All Patches" is actually a filter for displaying, it has nothing to do with patch installation. If there is something to install you would see it in "Needed patches".

The log contains this message:
2012-07-05 10:11:43 <1> jarfx(12872) [YCP] clients/online_update_select.ycp:90 All preselected patches: 0                                                                                      

The bug report is INVALID.