[Update] 2016-02-21 - Kernels, KDE, Pamac, Firefox, Thunderbird, Lumina, Intel

[LA-MJ]

I seem to be stuck at this oxygen icon error as shown in the post by others. Working with a live cd was promising except for the update part. I got the very same errors as on my main hard drive. So, I will need some further direction in order to get this resolved. Any and all help will be appreciated. Thanks, David.

What kind of errors? You will get nowhere with descriptions, people need data. What commands did you run and what was the output?

[jonathon]

If you have issues starting with updates from 5th March, you should be posting in this thread: https://forum.manjaro.org/index.php?topic=31804.0

[david.moser@skytex.net]

I cannot be certain which update this issue strated with, but here is the output from trying to perform a standard update:

Code: [Select]

:: Proceed with installation? [Y/n] y
(127/127) checking keys in keyring                                [####################################] 100%
(127/127) checking package integrity                              [####################################] 100%
(127/127) loading package files                                   [####################################] 100%
(127/127) checking for file conflicts                             [####################################] 100%
error: failed to commit transaction (conflicting files)
oxygen-icons: /usr/share/icons/oxygen/128x128/mimetypes/fonts-package.png exists in filesystem
oxygen-icons: /usr/share/icons/oxygen/16x16/mimetypes/fonts-package.png exists in filesystem
oxygen-icons: /usr/share/icons/oxygen/22x22/mimetypes/fonts-package.png exists in filesystem
oxygen-icons: /usr/share/icons/oxygen/32x32/mimetypes/fonts-package.png exists in filesystem
oxygen-icons: /usr/share/icons/oxygen/48x48/mimetypes/fonts-package.png exists in filesystem
oxygen-icons: /usr/share/icons/oxygen/64x64/mimetypes/fonts-package.png exists in filesystem
Errors occurred, no packages were upgraded.
Thanks,
David

[oberon]

@david.moser@skytex.net try

Code: [Select]

sudo pacman -Su --force oxygen-icons and then perform the update again.

[jonathon]

You can find whether the files are owned by a package:

pacman -Qo /usr/share/icons/oxygen/64x64/mimetypes/fonts-package.png

If they are not owned by a package, you can decide whether to force an overwrite with pacman, or just delete the files from disk.

Also, web search "pacman exists in filesystem" would get you similar answers.

Edit: or just do what oberon said.

[david.moser@skytex.net]

oberon, Yes! That fixed the oxygen icon issue.
First I ran: sudo pacman-mirrors -g and updated the mirrors
next I ran : sudo pacman -Syy to sync the sources
then the great: sudo pacman -Su --force oxygen-icon command

The updates went through............

Thanks again!!! david

[minjaro]

What is the most up to date kernel AND cryptsetup version I can install without losing access to my fully encrypted hard drive?

[jonathon]

What is the most up to date kernel AND cryptsetup version I can install without losing access to my fully encrypted hard drive?

That has been fixed, so 4.4.5/4.5rc7 and 1.7.1-1.

[minjaro]

Thanks for replying.

From a fresh install if I upgrade using:

sudo pacman -Syuv

Why does pacman report that the kernel & cryptsetup will be upgraded to linux41-4.1.19.-1 & 1.7.1-1 respectively?

Is this version combination ok to install or will it break access to full disk encryption?

How can I get my os to install the most up to date versions you listed?

I was under the impression that when using pacman -Syuv the most up to date stable versions of all software get pulled for installation. Am I wrong?

[scachemaille]

The combo you told should be OK as it's the last in the repos.i don't know why Jonathon talk about cryptsetup 1.7.2 as it's not even in unstable.  The last version is 1.7.1-1. and checking forum about the problem was about cryptsetup 1.7.0. so all should be fine..
to be sure before to boot after update install a new kernel (ex: 4.4) like this certainly one of them will boot and if both kernel run fine on your hardware it's always a good idea to have 2 kernel in case of update problem with one of the kernel

Code: [Select]

sudo mhwd-kernel -i linux44

[jonathon]

Why does pacman report that the kernel & cryptsetup will be upgraded to linux41-4.1.19.-1 & 1.7.1-1 respectively?

I was under the impression that when using pacman -Syuv the most up to date stable versions of all software get pulled for installation. Am I wrong?

All the latest versions of installed software. If you have kernel 4.1 installed it will update to the latest version of kernel 4.1. There are many kernels available - your post did not specify which one you were running, hence the "most up-to-date", as in the newest, is now kernel 4.5. You might want to read around as to why there are different kernels available (and maybe what the kernel does).

i don't know why Jonathon talk about cryptsetup 1.7.2 as it's not even in unstable.  The last version is 1.7.1-1.

No idea. Edited.

[minjaro]

Thanks for the encouragement and advice scachemaille.

After 1st upgrading cryptsetup to 1.7.1-1, I then upgraded my kernel to 4.1.19.-1 & also installed 4.4.5-1.

I don't know if cryptsetup 1.7.1-1 & my original kernel 4.1.15 would have worked together because I didn't reboot until I upgraded to & installed the above mentioned kernels.

What I can objectively confirm is that decryption is working at boot with both the 4.1.19.-1 & 4.4.5-1 kernels.

[yottie]

I had never used chroot before, so at the beggining it was difficult for me to follow the instructions from the Arch wiki. But this made it really easy and I could finally install a new kernel, everything is working back again! No system reinstalling, no starting all over again... Thank you so much!! And thaks to the team and everyone for making such a wonderful community.

Thank you so much omnimoon. I had a set-up with Uefi and with the homeddisk on a separate partition, so my mounts concerned sda4 and sda3, but otherwise it worked in one go.
Thanks again.
Y.