[Stable Update] 2017-04-02 - Mesa-Stack, Kernels, Plasma, Firefox

Normally manjaro-system should take care of this. If you still have a problem with this you can either delete those files or use the not recommended --force option of pacman to install {lib32-}libglvnd.

2 Likes

My feedback: All working well here.
Manjaro Gellivara with kernel 4.9.20, XFCE 4.12 and no problem with graphic.
Branch: Repository Stable
Used the command sudo pacman -Syyu as usual.

1 Like

10 posts were split to a new topic: Help me find a solution to get my system or at least my data back

To all beginners, let's not forget:

1 - don't rush with the update, wait, see what happened to others and what they did to mitigate the problems. I'm beginner, I will wait with my update.

2 - always make a backup of your disk - use clonezilla. Have spare or portable HDD and save the backup on it. If something goes wrong, restore partitions and all will be back as before system update.

6 Likes

I updated my two Manjaro systems without issue.


My general advice for people who seem to regularly run into update issues:

  • Make regular system backups.
  • Always use pacman in a TTY session to update your system.
  • Read the update's forum thread carefully to find out how to handle conflict replacements.
  • Never fall behind on updates.

By following these general rules I've never once had an issue updating my Manjaro machines. Seriously, not once.

7 Likes

Thanks kainonergon, your postings helped me to fix my system

To sum up:
ctrl-alt-f2 -> root shell
pacman -Sy manjaro-keyring
pacman -S manjaro-system
pacman -S lib32-mesa
pacman -Syu mhwd

7 Likes

--force did the job.. thanks.. everything working. tanks. :heart_eyes:

1 Like

How did you know I was looking for a tutorial :stuck_out_tongue_winking_eye:

1 Like

I also had problems with this update.

I did as usual, updating manjaro-keyring first and only after its conclusion running the pacman command. However after the reboot I was stuck with the blank screen and the cursor blinking on the top left. But thanks to @master_andreas that published the link with the solution I managed to login in tty2 and run pacman -Syu again.

After the whole process finished and another reboot, I was back to my normal login screen.

Apparently everything is working fine again.

Thanks everybody for the tips to solve the problem.

2 Likes

Update stopped shortly after the start with a "key missing" error. Nvidia lib symlinks had already been deleted by it, so my system hang, and restart got me to the console.
After I reinstalled all the keyring packages separately I could continue, but got lib32-libglvnd issue next. I've deleted files it didn't like manually.
Only third update finished successfully, and system was booting to X-server again.

1 Like

lib32 stack was making update impossible and i got stuck in bootloop.
after mhwd-chroot i force removed the two packages that was stopping the update.
after then smooth update and system booted just fine.

2 Likes

Never fall behind on updates.

Maybe this is an off topic question but I was already wondering what the possible consequences would/could be if I chose not to install an update and then a few days/weeks later install everything together with the next update or even multiple updates together.

I never thought of this, thanks for mentioning it. I will start updating my system this way if it is better, safer way!

None at all.
In fact, did you know that the downloadable images are way out of date? No problem to skip an update, I do that at times...
and...not really that off topic :slight_smile:
Edit - to ad to @AlManja - weeks...that's playing with matches...very short matches...
Skipping one update cannot hurt, but the longer the more the risks...

First I need to point out, this is my guessing. Generally probably not a good idea. I updated once Manjaro OpenRC that was not run on old and forgotten computer after almost 12 months and after a few overwritten conflicts it worked normal. But generally, longer you wait, better chances that something may go wrong. Few updates together shouldn't make a difference (most of the time) but better not playing with the fire. Plus you would not have latest security patches on your system making it vulnerable for attacks which is a problem on it's own.

1 Like

You are making a good point I didn't think about. But waiting too long may start putting your system at risk by not being patched for vulnerabilities.

1 Like

It can occasionally complicate things. Usually there is no problem in waiting a few days, or even a few months. But if you are trying to upgrade your installation that hasn't been touched for over a year, you might run into weird issues due to any major system changes.


I always recommend it because updates can occasionally interrupt your desktop instance and crash the updater during the update process. I've seen at least one occasion in the past year where this issue caused a lot of problems for people on the stable channel.

2 Likes

Update worked well on my desktop, but broke on my laptop.

Same issue as described before:

  • conflict regarding lib32-mesa on the second phase of the update
  • no other application can start
  • black screen upon forced reboot

I had to chroot from a live USB, following this thread: How to save your Manjaro installation when it breaks
(Only difference is i used gparted instead of lsblk in order to find the right partition to mount. Can't we have the labels with it?)
And then:

sudo pacman -Syyuu (fails because of conflict)
sudo pacman -S lib32-mesa
sudo pacman -S mhwd
sudo pacman -Syu

Then reboot. :slight_smile:

If it can help, here are my specs for my desktop (update worked) ...

System:    Host: CManj-maycne Kernel: 4.4.59-1-MANJARO x86_64 (64 bit gcc: 6.3.1)
           Desktop: Xfce 4.12.3 (Gtk 2.24.31) Distro: Manjaro Linux
Machine:   Device: desktop Mobo: MSI model: Z77A-G45 (MS-7752) v: 1.0
           BIOS: American Megatrends v: V2.6 date: 09/04/2012
CPU:       Quad core Intel Core i5-3470 (-MCP-) cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 25608
           clock speeds: max: 3600 MHz 1: 2142 MHz 2: 2093 MHz 3: 2060 MHz
           4: 2254 MHz
Graphics:  Card: NVIDIA GK104 [GeForce GTX 660 Ti] bus-ID: 01:00.0
           Display Server: X.Org 1.19.3 driver: nvidia
           Resolution: 1920x1080@60.00hz
           GLX Renderer: GeForce GTX 660 Ti/PCIe/SSE2
           GLX Version: 4.5.0 NVIDIA 375.39 Direct Rendering: Yes
Audio:     Card-1 Intel 7 Series/C216 Family High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 NVIDIA GK104 HDMI Audio Controller
           driver: snd_hda_intel bus-ID: 01:00.1
           Sound: Advanced Linux Sound Architecture v: k4.4.59-1-MANJARO
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: d000 bus-ID: 03:00.0
           IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 8251.6GB (59.4% used)
           ID-1: /dev/sdb model: Samsung_SSD_840 size: 250.1GB
           ID-2: /dev/sda model: WDC_WD20EZRZ size: 2000.4GB
           ID-3: /dev/sdd model: ST4000DM000 size: 4000.8GB
           ID-4: /dev/sdc model: ST2000DM001 size: 2000.4GB
Partition: ID-1: / size: 49G used: 32G (66%) fs: ext4 dev: /dev/sdb2
           ID-2: /home size: 1.8T used: 1.5T (88%) fs: ext4 dev: /dev/sda1
           ID-3: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 0.0:35C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 176 Uptime: 4:06 Memory: 2929.0/7933.0MB
           Init: systemd Gcc sys: 6.3.1
           Client: Shell (bash 4.4.121) inxi: 2.3.8

... the specs for my laptop (update failed).

System:    Host: ROG-73JH Kernel: 4.4.59-1-MANJARO x86_64 (64 bit gcc:
6.3.1)
           Desktop: Xfce 4.12.3 (Gtk 2.24.31) Distro: Manjaro Linux
Machine:   Device: laptop System: ASUSTeK product: G73Jh v: 1.0
           Mobo: ASUSTeK model: G73Jh v: 1.0
           BIOS: American Megatrends v: G73Jh.213 date: 01/27/2011
Battery    BAT0: charge: 0.0 Wh 0.0% condition: 73.9/78.0 Wh (95%)
           model: ASUSTek status: Charging
CPU:       Quad core Intel Core i7 Q 720 (-HT-MCP-) cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips:
12775
           clock speeds: max: 1600 MHz 1: 1066 MHz 2: 933 MHz 3: 1066
MHz
           4: 1066 MHz 5: 1466 MHz 6: 933 MHz 7: 1066 MHz 8: 933 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Broadway XT [Mobility
Radeon HD 5870]
           bus-ID: 01:00.0
           Display Server: X.Org 1.19.3 driver: radeon
           Resolution: 1920x1080@60.01hz
           GLX Renderer: Gallium 0.4 on AMD JUNIPER (DRM 2.43.0 /
4.4.59-1-MANJARO, LLVM 3.9.1)
           GLX Version: 3.0 Mesa 17.0.2 Direct Rendering: Yes
Audio:     Card-1 Intel 5 Series/3400 Series High Definition Audio
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 Advanced Micro Devices [AMD/ATI] Juniper HDMI Audio
[Radeon HD 5700 Series]
           driver: snd_hda_intel bus-ID: 01:00.1
           Sound: Advanced Linux Sound Architecture v: k4.4.59-1-
MANJARO
Network:   Card-1: Qualcomm Atheros AR9285 Wireless Network Adapter
(PCI-Express)
           driver: ath9k bus-ID: 03:00.0
           IF: wls1 state: down mac: <filter>
           Card-2: Qualcomm Atheros AR8131 Gigabit Ethernet
           driver: atl1c v: 1.0.1.1-NAPI port: a000 bus-ID: 04:00.0
           IF: ens5 state: up speed: 1000 Mbps duplex: full mac:
<filter>
Drives:    HDD Total Size: 1004.2GB (23.6% used)
           ID-1: /dev/sda model: ST9500325AS size: 500.1GB
           ID-2: /dev/sdb model: ST9500325AS size: 500.1GB
           ID-3: USB /dev/sdc model: Storage_Media size: 4.0GB
Partition: ID-1: / size: 71G used: 22G (31%) fs: ext4 dev: /dev/sda6
           ID-2: /home size: 459G used: 188G (42%) fs: ext4 dev:
/dev/sdb5
           ID-3: swap-1 size: 13.12GB used: 0.00GB (0%) fs: swap dev:
/dev/sda5
Sensors:   System Temperatures: cpu: 44.0C mobo: N/A gpu: 58.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 211 Uptime: 13 min Memory: 712.2/5897.1MB
           Init: systemd Gcc sys: 6.3.1
           Client: Shell (bash 4.4.121) inxi: 2.3.8
2 Likes

No issues here. Hope the OpenGL GLX issue got fixed with this patch.
Thanks Manjaro team !

Well, that was unrecoverable. At least not recoverable by me. Copied my data off of the drive and I'm reinstalling.

Lesson learned: always image drive before updating.

@philm: Here's what went wrong... I always read the forum before updating, but I made the mistake thinking that I could safely update manjaro-system and keyrings before updating the packages, and before looking at the forum. Guess this was a rather tricky update then...

2 Likes

Forum kindly sponsored by