[Stable Update] 2026-05-27 - Kernels, NVIDIA, Firefox, Thunderbird, Mesa, Blender

Announcements Stable Updates
71

I think that is an inaccurate description. Orphaned packages are those that were installed as a dependency to some other package(s), but at the moment, no currently installed package depends on them. Pacman database keeps track in what capacity a package was installed. That is, was the package installed explicitly (the user requested that package name directly) or was the package installed as a dependency (the user requested some other package but it forced this package’s installation too).

So a package can be installed without being dependent on other packages or have any dependencies of its own, and still it’s not an orphan if it was installed explicitly. Also an orphan can have dependencies of its own and still be and orphan.

2 Likes
72

4 posts were split to a new topic: " Cannot open access to console, the root account is locked." following 2026-05-27 Stable Update

73

A post was merged into an existing topic: " Cannot open access to console, the root account is locked." following 2026-05-27 Stable Update

74

A post was merged into an existing topic: “Cannot open access to console, the root account is locked.” following 2026-05-27 Stable Update

75

Since the update I have now encountered a crash twice within 24h. I am not able to force it, but it happens when the session auto locks and the screen to unlock is shown. It is not possible to switch to a terminal and restart since the screen is frozen. Running manjaro stable with KDE on a amd 7800xt. From my (very limited) understanding there seems to be a problem with amdgpu. Thanks in advance. Pls let me know if further info or testing is required.

output from journalctl at that point: 
Mai 30 18:11:03 computer org_kde_powerdevil[1334]: [  1491][8807.923047] Udev event detected

Mai 30 18:11:03 computer org_kde_powerdevil[1334]: [  1491][8807.923103] Udev_Event_Detail
Mai 30 18:11:03 computer ksecretd[1004]: There are no outputs - creating placeholder screen
Mai 30 18:11:03 computer org_kde_powerdevil[1334]: [  1491][8807.923103]    prop_subsystem:  drm
Mai 30 18:11:03 computer kactivitymanagerd[1330]: There are no outputs - creating placeholder screen
Mai 30 18:11:03 computer org_kde_powerdevil[1334]: [  1491][8807.923103]    prop_action:     change
Mai 30 18:11:03 computer pamac-tray-plasma[1567]: There are no outputs - creating placeholder screen
Mai 30 18:11:03 computer org_kde_powerdevil[1334]: [  1491][8807.923103]    prop_connector:  124
Mai 30 18:11:03 computer dolphin[6715]: There are no outputs - creating placeholder screen
Mai 30 18:11:03 computer org_kde_powerdevil[1334]: [  1491][8807.923103]    prop_devname:    /dev/dri/card1
Mai 30 18:11:03 computer polkit-kde-authentication-agent-1[1333]: There are no outputs - creating placeholder screen
Mai 30 18:11:03 computer org_kde_powerdevil[1334]: [  1491][8807.923103]    prop_devmode:    (null)
Mai 30 18:11:03 computer konsole[4188]: There are no outputs - creating placeholder screen
Mai 30 18:11:03 computer org_kde_powerdevil[1334]: [  1491][8807.923103]    prop_hotplug:    1
Mai 30 18:11:03 computer kscreenlocker_greet[12411]: There are no outputs - creating placeholder screen
Mai 30 18:11:03 computer org_kde_powerdevil[1334]: [  1491][8807.923103]    prop_major:      226
Mai 30 18:11:03 computer kded6[1250]: There are no outputs - creating placeholder screen
Mai 30 18:11:03 computer org_kde_powerdevil[1334]: [  1491][8807.923103]    prop_minor:      1
Mai 30 18:11:03 computer plasmashell[1305]: requesting unexisting screen available rect -1
Mai 30 18:11:03 computer org_kde_powerdevil[1334]: [  1491][8807.923103]    sysname:         card1
Mai 30 18:11:03 computer org_kde_powerdevil[1334]: There are no outputs - creating placeholder screen
Mai 30 18:11:03 computer org_kde_powerdevil[1334]: [  1491][8807.923103]    syspath:         /sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/0000:03:00.0/drm/card1
Mai 30 18:11:03 computer msm_kde_notifier[1551]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mai 30 18:11:03 computer org_kde_powerdevil[1334]: [  1491][8807.923103]    attr_name:       (null)
Mai 30 18:11:03 computer kdeconnectd[1552]: There are no outputs - creating placeholder screen
Mai 30 18:11:03 computer org_kde_powerdevil[1334]: [  1491][8807.923103] prop_connector = 124 -> /dev/i2c-9
Mai 30 18:11:03 computer xdg-desktop-portal-kde[1640]: There are no outputs - creating placeholder screen
Mai 30 18:11:03 computer org_kde_powerdevil[1334]: [  1491][8807.923103] prop_connector = 124 -> card1-DP-3
Mai 30 18:11:03 computer plasmashell[1305]: There are no outputs - creating placeholder screen
Mai 30 18:11:03 computer org_kde_powerdevil[1334]: [  1491][8807.923129] (dw_watch_display_connections) Time since last return from sleep = 8808464158363 ns = 8808464 ms
Mai 30 18:11:03 computer systemd[992]: Started dbus-:1.2-org.kde.KSplash@4.service.
Mai 30 18:11:03 computer plasmashell[1305]: <Unknown File>: QML ToolTipDialog: Exposed with no visual parent. Window positioning broken.
Mai 30 18:11:03 computer kernel: ------------[ cut here ]------------
Mai 30 18:11:03 computer kernel: !(false)
Mai 30 18:11:03 computer kernel: WARNING: drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:315 at dal_gpio_service_open+0x196/0x210 [amdgpu], CPU#13: kworker/13:1H/484
Mai 30 18:11:03 computer kernel: Modules linked in: rfcomm snd_seq_dummy snd_hrtimer snd_seq qrtr cmac algif_hash algif_skcipher af_alg bnep nct6683 vfat fat r8153_ecm cdc_ether usbnet mt7921e mt7921_common mt792x_lib mt76_connac_lib mt76 amd_atl intel_rapl_msr intel_rapl_common snd_hda_codec_atihdmi btusb snd_hda_codec_hdmi b>
Mai 30 18:11:03 computer kernel:  drm_display_helper cdrom nvme_core aesni_intel ccp video cec nvme_keyring nvme_auth hkdf wmi
Mai 30 18:11:03 computer kernel: CPU: 13 UID: 0 PID: 484 Comm: kworker/13:1H Not tainted 7.0.10-1-MANJARO #1 PREEMPT(full)  566ba636deb7082f128dd87f76270b8ca76878d6
Mai 30 18:11:03 computer kernel: Hardware name: Micro-Star International Co., Ltd. MS-7D75/MAG B650 TOMAHAWK WIFI (MS-7D75), BIOS 1.Q0 05/19/2026
Mai 30 18:11:03 computer kernel: Workqueue: events_highpri dm_irq_work_func [amdgpu]
Mai 30 18:11:03 computer kernel: RIP: 0010:dal_gpio_service_open+0x196/0x210 [amdgpu]
Mai 30 18:11:03 computer kernel: Code: 6c 24 04 48 8b 40 18 2e 2e 2e ff d0 8b 74 24 04 48 89 45 08 49 8b 54 24 30 48 89 c7 48 8b 52 30 2e 2e 2e ff d2 e9 14 ff ff ff <0f> 0b b8 03 00 00 00 4c 8b 6c 24 20 48 8b 5c 24 08 4c 8b 64 24 18
Mai 30 18:11:03 computer kernel: RSP: 0018:ffffccc900703968 EFLAGS: 00010202
Mai 30 18:11:03 computer kernel: RAX: ffff8c4b0bcaa5d8 RBX: 0000000000000001 RCX: 0000000000000000
Mai 30 18:11:03 computer kernel: RDX: ffffccc901e17660 RSI: 0000000000000002 RDI: ffff8c4b0bf89040
Mai 30 18:11:03 computer kernel: RBP: ffff8c4b05c8a100 R08: 0000000000000100 R09: 0000000000000000
Mai 30 18:11:03 computer kernel: R10: ffff8c4b00eab540 R11: 0000000000000000 R12: ffff8c4b00e84c00
Mai 30 18:11:03 computer kernel: R13: 0000000000000002 R14: ffff8c4b05c8a100 R15: ffff8c4b0fdb0df8
Mai 30 18:11:03 computer kernel: FS:  0000000000000000(0000) GS:ffff8c5a408a6000(0000) knlGS:0000000000000000
Mai 30 18:11:03 computer kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mai 30 18:11:03 computer kernel: CR2: 00007f812f6f1fe0 CR3: 00000001372d3000 CR4: 0000000000f50ef0
Mai 30 18:11:03 computer kernel: PKRU: 55555554
Mai 30 18:11:03 computer kernel: Call Trace:
Mai 30 18:11:03 computer kernel:  <TASK>
Mai 30 18:11:03 computer kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Mai 30 18:11:03 computer kernel:  dal_ddc_open+0x56/0x150 [amdgpu f8b2dca1d6c0641254752586c6bc5d59136cff7c]
Mai 30 18:11:03 computer kernel:  acquire+0x63/0x200 [amdgpu f8b2dca1d6c0641254752586c6bc5d59136cff7c]
Mai 30 18:11:03 computer kernel:  dce_aux_transfer_raw+0x88/0x7a0 [amdgpu f8b2dca1d6c0641254752586c6bc5d59136cff7c]
Mai 30 18:11:03 computer kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Mai 30 18:11:03 computer kernel:  dm_dp_aux_transfer+0x118/0x2c0 [amdgpu f8b2dca1d6c0641254752586c6bc5d59136cff7c]
Mai 30 18:11:03 computer kernel:  drm_dp_dpcd_access+0xc0/0x170 [drm_display_helper 519e1229ab0120ea2d983252a35fceb6c7e7e3a2]
Mai 30 18:11:03 computer kernel:  drm_dp_dpcd_write+0x8d/0xe0 [drm_display_helper 519e1229ab0120ea2d983252a35fceb6c7e7e3a2]
Mai 30 18:11:03 computer kernel:  dm_helpers_dp_write_dpcd+0x2b/0x40 [amdgpu f8b2dca1d6c0641254752586c6bc5d59136cff7c]
Mai 30 18:11:03 computer kernel:  core_link_write_dpcd+0x9e/0xe0 [amdgpu f8b2dca1d6c0641254752586c6bc5d59136cff7c]
Mai 30 18:11:03 computer kernel:  dpcd_set_source_specific_data+0x12d/0x1b0 [amdgpu f8b2dca1d6c0641254752586c6bc5d59136cff7c]
Mai 30 18:11:03 computer kernel:  retrieve_link_cap+0xe5/0xf10 [amdgpu f8b2dca1d6c0641254752586c6bc5d59136cff7c]
Mai 30 18:11:03 computer kernel:  ? dal_gpio_close+0x1e/0x30 [amdgpu f8b2dca1d6c0641254752586c6bc5d59136cff7c]
Mai 30 18:11:03 computer kernel:  ? dm_helpers_is_dp_sink_present+0x3b/0x50 [amdgpu f8b2dca1d6c0641254752586c6bc5d59136cff7c]
Mai 30 18:11:03 computer kernel:  detect_link_and_local_sink+0xe76/0x13a0 [amdgpu f8b2dca1d6c0641254752586c6bc5d59136cff7c]
Mai 30 18:11:03 computer kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Mai 30 18:11:03 computer kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Mai 30 18:11:03 computer kernel:  ? dm_read_reg_func+0x5c/0x100 [amdgpu f8b2dca1d6c0641254752586c6bc5d59136cff7c]
Mai 30 18:11:03 computer kernel:  link_detect+0x40/0x590 [amdgpu f8b2dca1d6c0641254752586c6bc5d59136cff7c]
Mai 30 18:11:03 computer kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Mai 30 18:11:03 computer kernel:  ? dcn10_get_hpd_state+0x4d/0x80 [amdgpu f8b2dca1d6c0641254752586c6bc5d59136cff7c]
Mai 30 18:11:03 computer kernel:  handle_hpd_irq_helper+0x277/0x300 [amdgpu f8b2dca1d6c0641254752586c6bc5d59136cff7c]
Mai 30 18:11:03 computer kernel:  process_one_work+0x19c/0x3a0
Mai 30 18:11:03 computer kernel:  worker_thread+0x1b1/0x310
Mai 30 18:11:03 computer kernel:  ? __pfx_worker_thread+0x10/0x10
Mai 30 18:11:03 computer kernel:  kthread+0xe1/0x120
Mai 30 18:11:03 computer kernel:  ? __pfx_kthread+0x10/0x10
Mai 30 18:11:03 computer kernel:  ret_from_fork+0x2bc/0x350
Mai 30 18:11:03 computer kernel:  ? __pfx_kthread+0x10/0x10
Mai 30 18:11:03 computer kernel:  ret_from_fork_asm+0x1a/0x30
Mai 30 18:11:03 computer kernel:  </TASK>
Mai 30 18:11:03 computer kernel: ---[ end trace 0000000000000000 ]---

Edit: Sorry for the formatting of the log. Somehow it shows it correctly in the preview, but in the thread it becomes one line.

76

Your best option is probably to fall back to kernel 6.18 LTS.

1 Like
77

Your best option is probably to fall back to kernel 6.18 LTS.

Will try that and see if it happens again. But I was running v7.0.3 before and did not encounter this problem.

78

Incomplete, rather than inaccurate.

However, yes, it’s possible that a package that has no dependencies and is not a dependent of any other package can be installed, and not be an Orphan.

This would be a non-dependent package, often installed explicitly – by their very nature such packages cannot be described as orphan, and in context of my response they were not mentioned; omitted, as they were not an example of an orphan.

Nonetheless, post edited for clarity.

2 Likes
79

It says: With the Plasma 6.6.6 point release there are some notable fixes such as for a possible KWin crash when a monitor is rapidly power-cycled, fixing a clipboard-related issue causing XWayland-based apps to lag or freeze after locking the screen, and other bugs.

This might be the case for you, since your trace shows that all displays were lost during a display event. It shows several times: “There are no outputs - creating placeholder screen”.

80

Hi,
Something similar is happening here. In Nautilus under GNOME, file previews are broken, and the same goes for the wallpaper.

Manjaro Linux
DISTRIB_ID="ManjaroLinux"
DISTRIB_RELEASE="26.1.0-pre"
DISTRIB_CODENAME="Bian-May"
DISTRIB_DESCRIPTION="Manjaro Linux"
Manjaro Linux
NAME="Manjaro Linux"
PRETTY_NAME="Manjaro Linux"
ID=manjaro
ID_LIKE=arch
BUILD_ID=rolling
ANSI_COLOR="32;1;24;144;200"
HOME_URL="https://manjaro.org/"
DOCUMENTATION_URL="https://wiki.manjaro.org/"
SUPPORT_URL="https://forum.manjaro.org/"
BUG_REPORT_URL="https://manjaro.org/help/"
PRIVACY_POLICY_URL="https://manjaro.org/privacy-policy/"
LOGO=manjarolinux

Kernel: 6.6.141-1-MANJARO #1 SMP PREEMPT_DYNAMIC Sat May 23 16:02:08 UTC 2026 x86_64 GNU/Linux

lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) <-- using this (Mesa Intel(R) HD Graphics 3000 (SNB GT2)
01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 540M] (rev a1)

Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text

81

2nd generation Intel gpu = mesa problem with the current version. Downgrade mesa. (manjaro-downgrade mesa)

I have added this to the known problems.

And next time please look at your post before/after posting. It looked and still looks like :poop: I fixed the shouting at least, but it will be of great use to you to read the tutorials “how to ask for help” and “how to provide system information”.

82

With this setup, which hook performs the encryption unlocking? Isn’t hook sd-encrypt required for that? Or is adding just hook systemd actually sufficient?

83

Much obliged for the explanation. So I shouldn’t remove the AUR packages pre-update? Also, is it possible to switch to Unstable without a reinstall of the distro?

84

sudo pacman-mirrors --api --set-branch unstable

From the Manpage:
-B, -S, --set-branch BRANCH
Permanent change branch, using stable, testing or unstable.

2 Likes
85

That’s correct; as was explained by others, I think.

Indeed, it is.

The following Wiki page should provide all you need to successfully switch branches; and also back again, if needed.

2 Likes
86

@fonic SystemD-encrypt cannot work without systemd. :grinning_face: It’s a combination. You either take the left column or the right column of the table in the arch wiki (obligatory reading links :wink:)

2 Likes
87

That’s exactly why I mentioned this. The list I quoted seems to omit sd-encrypt and should be updated accordingly.

88

I’ll add it. I just copied my hooks in the “problems” and forgot i don’t use encryption. :wink:

1 Like
90

Comments above the HOOKS=(...) line also give examples of usage with encryption.

cat /etc/mkinitcpio.conf
91

To me it seems this problem with MT7922 wasn’t fixed in the latest kernel (or something around it). Bluetooth still doesn’t work for me.

1 Like