Bug 1002700

Summary: Error reported after a failed attempt to upgrade to the latest kernel
Product: [Fedora] Fedora Reporter: stephen
Component: kde-settingsAssignee: Rex Dieter <rdieter>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 19CC: dvratil, jgrulich, jreznik, kevin, long, ltinkl, mbriza, rdieter, rnovacek, smparrish, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-30 04:06:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description stephen 2013-08-29 18:13:06 UTC
Description of problem:

Kernel update failed with kde-settings duplication error

Version-Release number of selected component (if applicable):


How reproducible:

Every time at present


Steps to Reproduce:
1.Run Jum Update
2.
3.

Actual results:

yum update
Loaded plugins: fastestmirror, langpacks, refresh-packagekit
Dropbox                                                                     |  951 B  00:00:00     
adobe-linux-x86_64                                                          |  951 B  00:00:00     
google-earth                                                                |  951 B  00:00:00     
rpmfusion-free-updates                                                      | 3.3 kB  00:00:00     
rpmfusion-free-updates-debuginfo                                            | 2.7 kB  00:00:00     
rpmfusion-free-updates-source                                               | 2.7 kB  00:00:00     
rpmfusion-nonfree-updates                                                   | 3.3 kB  00:00:00     
rpmfusion-nonfree-updates-debuginfo                                         | 2.7 kB  00:00:00     
rpmfusion-nonfree-updates-source                                            | 2.7 kB  00:00:00     
skype                                                                       | 1.2 kB  00:00:00     
updates/19/x86_64/metalink                                                  |  30 kB  00:00:00     
updates-debuginfo/19/x86_64/metalink                                        |  28 kB  00:00:00     
updates-source/19/x86_64/metalink                                           |  29 kB  00:00:00     
Loading mirror speeds from cached hostfile
 * fedora: www.mirrorservice.org
 * fedora-debuginfo: www.mirrorservice.org
 * fedora-source: www.mirrorservice.org
 * rpmfusion-free: mirrors.coreix.net
 * rpmfusion-free-debuginfo: mirrors.coreix.net
 * rpmfusion-free-source: mirrors.coreix.net
 * rpmfusion-free-updates: mirrors.coreix.net
 * rpmfusion-free-updates-debuginfo: mirrors.coreix.net
 * rpmfusion-free-updates-source: mirrors.coreix.net
 * rpmfusion-nonfree: mirrors.coreix.net
 * rpmfusion-nonfree-debuginfo: mirrors.coreix.net
 * rpmfusion-nonfree-source: mirrors.coreix.net
 * rpmfusion-nonfree-updates: mirrors.coreix.net
 * rpmfusion-nonfree-updates-debuginfo: mirrors.coreix.net
 * rpmfusion-nonfree-updates-source: mirrors.coreix.net
 * updates: www.mirrorservice.org
 * updates-debuginfo: www.mirrorservice.org
 * updates-source: www.mirrorservice.org
Resolving Dependencies
--> Running transaction check
---> Package kernel.x86_64 0:3.10.9-200.fc19 will be installed
---> Package kernel-devel.x86_64 0:3.10.9-200.fc19 will be installed
---> Package kernel-headers.x86_64 0:3.10.6-200.fc19 will be updated
---> Package kernel-headers.x86_64 0:3.10.9-200.fc19 will be an update
---> Package kernel-modules-extra.x86_64 0:3.10.9-200.fc19 will be installed
---> Package kmod-nvidia-3.10.4-300.fc19.x86_64.x86_64 1:319.32-2.fc19 will be updated
---> Package kmod-nvidia-3.10.4-300.fc19.x86_64.x86_64 1:319.32-2.fc19.1 will be an update
--> Finished Dependency Resolution
--> Running transaction check
---> Package kernel.x86_64 0:3.10.4-300.fc19 will be erased
--> Processing Dependency: kernel-uname-r = 3.10.4-300.fc19.x86_64 for package: 1:kmod-nvidia-3.10.4-300.fc19.x86_64-319.32-2.fc19.1.x86_64
---> Package kernel-devel.x86_64 0:3.10.4-300.fc19 will be erased
---> Package kernel-modules-extra.x86_64 0:3.10.4-300.fc19 will be erased
--> Finished Dependency Resolution
Error: Package: 1:kmod-nvidia-3.10.4-300.fc19.x86_64-319.32-2.fc19.1.x86_64 (rpmfusion-nonfree-updates)
           Requires: kernel-uname-r = 3.10.4-300.fc19.x86_64
           Removing: kernel-3.10.4-300.fc19.x86_64 (@updates)
               kernel-uname-r = 3.10.4-300.fc19.x86_64
           Installed: kernel-3.10.5-201.fc19.x86_64 (@updates)
               kernel-uname-r = 3.10.5-201.fc19.x86_64
           Installed: kernel-3.10.6-200.fc19.x86_64 (@updates)
               kernel-uname-r = 3.10.6-200.fc19.x86_64
           Available: kernel-3.9.5-301.fc19.x86_64 (fedora)
               kernel-uname-r = 3.9.5-301.fc19.x86_64
           Installing: kernel-3.10.9-200.fc19.x86_64 (updates)
               kernel-uname-r = 3.10.9-200.fc19.x86_64
           Available: kernel-debug-3.9.5-301.fc19.x86_64 (fedora)
               kernel-uname-r = 3.9.5-301.fc19.x86_64.debug
           Available: kernel-debug-3.10.9-200.fc19.x86_64 (updates)
               kernel-uname-r = 3.10.9-200.fc19.x86_64.debug
 You could try using --skip-broken to work around the problem
** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
kde-settings-kdm-19-23.1.fc19.noarch is a duplicate with kde-settings-kdm-19-23.fc19.noarch



Expected results:

New kernel installed for the system 


Additional info:

Why is kde-settings getting in the way of a kernel upgrade - hopefully its a simple yum database error and can be fixed ???

Comment 1 Rex Dieter 2013-08-30 04:06:55 UTC
This is an rpmfusion nvidia kernel module problem, not a fedora one.  Nothing we can do about that, sorry.

Comment 2 stephen 2013-08-30 09:54:39 UTC
(In reply to Rex Dieter from comment #1)
> This is an rpmfusion nvidia kernel module problem, not a fedora one. 
> Nothing we can do about that, sorry.

ok thanks - I will try and go via that route.

Comment 3 Kevin Kofler 2013-08-31 22:51:34 UTC
As for the warning you're seeing (which is NOT what is causing your transaction to fail):

> ** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
> kde-settings-kdm-19-23.1.fc19.noarch is a duplicate with kde-settings-kdm-19-23.fc19.noarch

see bug #989145. (In short: It is already fixed in the new package, but the problem is with uninstalling the old package (even on upgrades), so we cannot really fix it. You have to remove the old package with "rpm -e --noscripts kde-settings-kdm-19-23.1.fc19.noarch". But as I said, the real problem is the kmod-nvidia one.)

Comment 4 stephen 2013-09-01 10:23:01 UTC
Hi thanks for the pointers, I did an rpm -qa | grep kde-settings-kdm to see what I have installed and it gave me two answers,

kde-settings-kdm-19-23.fc19.noarch
kde-settings-kdm-19-23.1.fc19.noarch

Isn't kde-settings-kdm-19-23.1.fc19.noarch newer than the kde-settings-kdm-19-23.fc19.noarch, or have a missed the point ??, so if that's true, would I not be better off getting rid of the older package. again have I missed the point and the .1 version is the erroneous package ?

I appreciate that this isn't your problem and I realise your time is valuable, but I don't what to commit to something that would or could stop me from using my system. I am just not sure as to how to proceed now, but if I don't resolve this, the problem will just reappear somewhere later down the line for me. I would appreciate some advise please.

Comment 5 stephen 2013-09-01 10:24:37 UTC
I did try to create an account to report the bug on the rpm-fusion site but I have had nothing back from the site as to activating my account....

Comment 6 Kevin Kofler 2013-09-02 18:01:45 UTC
Uh, yes, I made a mistake there, you should indeed remove the older of the duplicate packages, not the newer one. The linked bug report contains the correct workaround:
rpm -e --noscripts kde-settings-kdm-19-23.fc19
Sorry for the confusion.