[Stable Update] 2022-07-29 - Kernels, Cinnamon, Haskell, Python, Virtualbox, Mesa

Announcements Stable Updates
,
16

Sorry, I am never sure whether we are supposed to reply or start a new post.

With today’s update I had an error and the upgrade could not be completed. It seemed that python-beautifulsoup4 already existed (“file already exists”) for a number of associated files.

These were not installed by pip. Their location was “/usr/lib/python3.10/site-packages/bs4/tests/”

My solution was to remove them through pacmac and the application that was dependent on them, in this case calibre ebook manager.

After this action the update completed normally with no errors.
SOLVED

17

I saw this again after reboot:

18

How soon is this fix likely to make it to Manjaro? I’m debating on not updating until this one has been fixed. (Yes I know there’s a workaround, I just don’t care to do it.)

1 Like
19

I still see KDE menu misplaced on my screen after writing that workaround. Am I supposed to delete the menu panel and create another one hopping everything is going to be Ok?

20

According to Branch Compare, qt5-wayland has been updated but I’m not at my computer to test. Can you confirm?

21

Wake up from suspend are very slow on 5.18.14
It recognizes no mouse / keyboard inputs.
Stuck at lockscreen
5.18.15 does not have a fix for that.

1 Like
22

Tested and confirmed. Updated my original post.

1 Like
23

@ufo_driver @Gquirt @gjoe @CarlLaFong It has landed. Got it on my machine and everything is back to normal. No need for the workaround.

3 Likes
24

A post was split to a new topic: Gnome-control-center segfault after update

25

Can I just say that I love how on top of things the Manjaro team is? Even when there’s a small issue I’ve never not seen it fixed within a day or two.

Buy some merch. They deserve the support and the advertising! (For the record, I have a Manjaro draft hoodie and I love it.)

10 Likes
26

A post was merged into an existing topic: VisualBoyAdvance-M no longer opening roms after last stable update

27

After the July 29 stable Update my Virtualbox crashed. NS_Error_Failure

28

Install latest Extension Pack.

30

ok this works.

thank you !

31

A post was split to a new topic: Failed to load steamui.so

32

Same thing happened to me Virtualbox no longer works.

33

I’m not super concerned but Firefox segfaults on start

[Sat Jul 30 17:00:23 2022] firefox[2367]: segfault at d8 ip 00007fd504389814 sp 00007fffdfe33158 error 4 in libX11.so.6.4.0[7fd50437a000+8b000]
[Sat Jul 30 17:00:23 2022] Code: 84 00 00 00 00 00 f3 0f 1e fa 8b 47 1c c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 8b 47 74 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa <48> 8b 87 d8 00 00 00 c3 0f 1f 40 00 f3 0f 1e fa 48 63 f6 48 c1 e6

Beyond that it works as usual

34

Ok, I am not exactly sure how, but after running the update yesterday after the software manager notified me of a number of updated packages, my system tried to come back up using the real time kernel, which basically caused all kinds of booting issues. I was using 5.15 LTS when performing the update, so is there any way to determine why my system was using the real time kernel after the update? This was on a machine installed at 21.3.5 and only a week or two old, so really had no history with any previous kernels.

I had to manually uninstall the kernel and manually install 5.18.14 afterwards. I also uninstalled virtualbox as the “watchdog: BUG soft lockup” error seemed to indicate issues with “vboxdrv(0E+”, but noticed when manually installing 5.18.14 that the software manager added virtuabox elements back again, although my software manager doesn’t show any at this point.

All in all a pretty confusing upgrade for a semi-knowledgeable user.

35

Because you manually installed it at some point. It could have been by accident.

36

So this particular install is my first Manjaro experience, having come from using Garuda for the last 6+ months. I installed a few weeks ago from the available .iso and updated when notified. I know 5.15 LTS was the version I was running yesterday, and I haven’t touched one button in that section of the system manager. If I did anything to cause this, I have no recollection of doing that.

Based on your idea, I wonder if I didn’t add the RT kernel as an option during the initial install, and didn’t realize the ramification of doing so. Is there an option during the live installer to choose the RT kernel?