Bug 17056

Is this problem still present?

(In reply to Samuel VERSCHELDE from comment #1)
> Is this problem still present?

Yes it is

Please attach the output of rpm -qa | grep kernel

I just clicked on the update icon and received this message:

Sorry, the following package cannot be selected:

- kernel-desktop-latest-4.1.13-2.mga5.x86_64

I allowed all the updates to install, then quit the update process.
Then I went to Mageia Control Panel and selected update, and received:

Sorry, the following package cannot be selected:

- kernel-desktop-latest-4.1.13-2.mga5.x86_64 (due to conflicts with kernel-desktop-4.1.13-2.mga5-1-1.mga5.x86_64)

So, I pasted the message into Google and came here to post this.
The output of rpm -qa | grep kernel is 

[ken@localhost ~]$ rpm -qa | grep kernel
kernel-firmware-20150722-1.mga5
kernel-desktop-3.17.2-3.mga5-1-1.mga5
kernel-desktop-3.19.2-1.mga5-1-1.mga5
kernel-desktop-3.19.0-6.mga5-1-1.mga5
kernel-desktop-3.18.3-1.mga5-1-1.mga5
kernel-desktop-3.19.1-1.mga5-1-1.mga5
kernel-desktop-3.19.6-2.mga5-1-1.mga5
kernel-desktop-3.18.2-1.mga5-1-1.mga5
kernel-desktop-latest-3.19.8-2.mga5
lib64kplatokernel13-2.8.7-1.mga5
kernel-desktop-3.19.0-1.mga5-1-1.mga5
kernel-desktop-3.19.3-1.mga5-1-1.mga5
kernel-desktop-3.19.6-1.mga5-1-1.mga5
kernel-desktop-3.19.0-2.mga5-1-1.mga5
kernel-desktop-3.19.0-5.mga5-1-1.mga5
kernel-desktop-3.18.3-2.mga5-1-1.mga5
kernel-desktop-3.19.7-1.mga5-1-1.mga5
kernel-desktop-3.19.2-2.mga5-1-1.mga5
kernel-desktop-3.19.0-4.mga5-1-1.mga5
kernel-desktop-3.19.0-0.rc7.3.mga5-1-1.mga5
kernel-desktop-3.19.1-2.mga5-1-1.mga5
kernel-desktop-3.19.4-1.mga5-1-1.mga5
kernel-desktop-3.19.8-2.mga5-1-1.mga5
kernel-desktop-3.19.8-1.mga5-1-1.mga5
kernel-desktop-3.19.0-3.mga5-1-1.mga5
kernel-desktop-3.19.7-2.mga5-1-1.mga5
kernel-desktop-3.19.0-0.rc7.2.mga5-1-1.mga5
kernel-firmware-nonfree-20151018-1.mga5.nonfree
kernel-userspace-headers-4.1.13-2.mga5
kernel-desktop-3.19.4-2.mga5-1-1.mga5
[ken@localhost ~]$ 

Yes, this error has been ignored for a while. I used the Mageia 5 betas for quite a while, then, conveniently for me, did not do a clean install when the final version shipped.  I suspect there is a manual fix to clear up this error, but I have been too busy with school to investigate it.  The error is consistent, though, with each update, whether suggested or requested.

CC: (none) => kmmos1

In Comment 4 I was working on an HP Pavilion Core i3 desktop. I just switched to a Dell Latitude 6520 laptop, clicked on the upgrade icon, and completed the upgrade without messages.  I received the new kernel, restarted the machine, and now am updating this bug report.

The output is:
[ken@localhost ~]$ rpm -qa | grep kernel
kernel-desktop-4.1.12-1.mga5-1-1.mga5
kernel-userspace-headers-4.1.13-2.mga5
kernel-firmware-20150722-1.mga5
kernel-desktop-4.1.13-2.mga5-1-1.mga5
kernel-firmware-nonfree-20151018-1.mga5.nonfree
kernel-desktop-3.19.8-3.mga5-1-1.mga5
kernel-desktop-4.1.8-1.mga5-1-1.mga5
kernel-desktop-latest-4.1.13-2.mga5
[ken@localhost ~]$ 

This laptop is dual boot with Windows 7, as is the HP, but this machine received a fresh install of Version 5 shortly after its release.

I am also working on an HP Pavilion Touchsmart 14 Sleekbook. I have been using the Mageia 5 betas. How do I do a clean install and install the shipped final version?

(In reply to Barry McCabe from comment #6)
> I am also working on an HP Pavilion Touchsmart 14 Sleekbook. I have been
> using the Mageia 5 betas. How do I do a clean install and install the
> shipped final version?

You do have the final version, but since you went through steps that other users haven't went through, it's possible that issues like this one arise. Usually it's OK, we try to make sure the system is in good shape for beta testers too, but if you really want a clean Mageia 5 system, the best way is to reinstall.

In order to fix your issue, you likely will have to run, as root:

urpmi --auto-update

The cause of you issue is probably that some packages on your system are not to the exact version we shipped in Mageia 5, and the graphical updater won't update them if the media they are in is not flagged as an update source. urpmi --auto-update should update these packages and fix the issue.

Closing as fixed hoping my comment #8 solved the issue for the users.

Status: NEW => RESOLVED
Resolution: (none) => FIXED