[SOLVED]crash during system update, xorg-x11 not working, only wayland

colegu · 2024-03-11 15:48:53

hi all,

a little bit of context. yesterday i did a full system update (it was a big one, but didn't bother to look actually, kde5 - > plasma 6 among others), and in the meantime i opened up wine to play some WoW.
after some time, i changed the window to see how the update is going. but after a couple of seconds the system froze, and since i'm using nvidia drivers i could not switch to cli and check things from there, so i had to power off ..

upon reboot the GUI was not working, so i had to boot up with a live USB to discover that the system was a complete mess. half of the files in /usr were empty, so i had to reinstall everything from scratch, with the owerwrite option.
after some fiddling i managed to boot up my system back to GUI, but it only works with wayland. if i select in sddm that i want plasma + xorg, the system freezes and i have to power off manually .
i did reinstall all xorg related stuff, and xf86 (pacman -Qqn | grep xf86 ) stuff but i might be missing something. i even grabbed the latest 6.8 kernel, reinstalled nvidia-dkms and the like but it still doesnt work

i really want xorg back since wayland and keyboard shortcuts are a mess to configure (didn't figure out how), xmodmap does not work (can't remap the keyboard layout using custom key bindings ) , and I dont get the same FPS in WoW (this i can live with) )

any advice would be highly appreciated
thanks

Last edited by colegu (2024-03-16 15:09:52)

V1del · 2024-03-12 16:05:38

Post the output of

sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files'

in doubt reinstall the ones mentioned there.

If that doesn't fix it, after a failed bootup and plasma x11 startup attempt, post

sudo journalctl -b

https://wiki.archlinux.org/title/List_o … n_services

FWIW something you should do in general and in order to enable the TTY on nvidia (and in fact enable proper wayland support should that still be something you want to test) is to add nvidia-drm.modeset=1 to your kernel parameters.

colegu · 2024-03-12 17:37:51

hi, and thank you for your comment.

surprisingly the command you pointed only gives some configuration files at the output, and some UIDs mismatch since i do all the compiling under /usr/src under my normal user instead of root.

I have the mode setting set up with underscore instead of dash, should that be the issue?

[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux6.8.0 root=/dev/nvme0n1p3 rw resume=/dev/nvme0n1p2 loglevel=3 nvidia_drm.modeset=1 intel_iommu=on
[    0.038760] Kernel command line: BOOT_IMAGE=/vmlinuz-linux6.8.0 root=/dev/nvme0n1p3 rw resume=/dev/nvme0n1p2 loglevel=3 nvidia_drm.modeset=1 intel_iommu=on
[    2.050200] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  550.54.14  Thu Feb 22 01:25:25 UTC 2024
[    2.442861]  processor_thermal_rfim nvidia_drm(PO+) cryptd drm_display_helper snd_hda_cs_dsp_ctls snd_intel_dspcfg xhci_pci mdio_devres processor_thermal_rapl intel_lpss_pci ttm cs_dsp iwlwifi xhci_hcd snd_hda_codec mei_me intel_rapl_common intel_lpss intel_gtt nvidia_wmi_ec_backlight snd_soc_cs35l41_lib ucsi_acpi libphy nvidia_modeset(PO) snd_hwdep rtsx_pci regmap_i2c usbcore processor_thermal_wt_req idma64 spi_intel_pci snd_hda_core typec_ucsi spi_intel i2c_algo_bit cfg80211 i2c_i801 mei virt_dma processor_thermal_power_floor usb_common i2c_smbus processor_thermal_mbox roles mfd_core serial_multi_instantiate i2c_hid_acpi i2c_hid int3403_thermal pinctrl_tigerlake int3400_thermal int340x_thermal_zone acpi_thermal_rel pinctrl_intel pkcs8_key_parser nvidia_uvm(PO) nvidia(PO) i2c_dev crypto_user fuse loop nfnetlink efivarfs dmi_sysfs ip_tables x_tables ipv6
[    2.881344] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DP-2
[    2.890428] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DP-2

I'll try the X11 login and post the journalctl results soon.

thanks

colegu · 2024-03-12 17:54:54

http://0x0.st/HhUV.txt

the system crashed before the boot process starting at Mar 12 19:39:46. unfortunately i did not see anything useful inspecting the logs. but most probably i'm missing something.

onemyndseye · 2024-03-12 17:59:27

** Message Deleted **

Last edited by onemyndseye (2024-03-20 17:59:15)

colegu · 2024-03-12 18:20:06

this usually hapens if clementine and other kde apps are not closed properly. so it's expected to see dumps like that when booting the system after a failed plasma/x11 initialization

but yes, after the update the logs are much messier than with kde5, and there's also a kernel trace there, so most probably i'll go with the good ol 6.7.3 instead of 6.8

seth · 2024-03-12 20:24:24

Mar 12 19:39:05 njordr systemd-logind[2868]: New session 4 of user bogdan.
Mar 12 19:39:05 njordr systemd[1]: Started Session 4 of User bogdan.
Mar 12 19:39:05 njordr sddm-helper[53856]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Mar 12 19:39:05 njordr sddm-helper[53863]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Mar 12 19:39:05 njordr sddm-helper[53856]: Writing cookie to "/tmp/xauth_KtjXLq"
Mar 12 19:39:05 njordr sddm-helper[53856]: Starting X11 session: "" "/usr/share/sddm/scripts/Xsession \"/usr/bin/startplasma-x11\""
Mar 12 19:39:05 njordr sddm-helper[53769]: [PAM] Closing session
Mar 12 19:39:05 njordr sddm-helper[53769]: pam_unix(sddm-greeter:session): session closed for user sddm
Mar 12 19:39:05 njordr sddm-helper[53769]: [PAM] Ended.
Mar 12 19:39:05 njordr sddm[3197]: Session started true
Mar 12 19:39:05 njordr sddm[3197]: Auth: sddm-helper exited successfully
Mar 12 19:39:05 njordr sddm[3197]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS
Mar 12 19:39:05 njordr systemd[1]: session-c1.scope: Deactivated successfully.
Mar 12 19:39:05 njordr systemd[1]: session-c1.scope: Consumed 1.552s CPU time.
Mar 12 19:39:05 njordr systemd-logind[2868]: Session c1 logged out. Waiting for processes to exit.
Mar 12 19:39:05 njordr systemd-logind[2868]: Removed session c1.
Mar 12 19:39:05 njordr systemd[3351]: Reloading requested from client PID 53865 ('startplasma-x11')...
Mar 12 19:39:05 njordr systemd[3351]: Reloading...
Mar 12 19:39:05 njordr systemd-xdg-autostart-generator[53881]: Exec binary '/home/bogdan/.config/old-autostart-scripts/_xmodmap.desktop' does not exist: Permission denied
Mar 12 19:39:05 njordr systemd-xdg-autostart-generator[53881]: /home/bogdan/.config/autostart/_xmodmap.desktop.desktop: not generating unit, error parsing Exec= line: Permission denied
Mar 12 19:39:05 njordr systemd[3351]: Reloading finished in 47 ms.
Mar 12 19:39:05 njordr systemd[3351]: Started dbus-:1.2-org.kde.KSplash@1.service.
Mar 12 19:39:05 njordr systemd[3351]: Submitting pending crash events was skipped because of an unmet condition check (ConditionPathExistsGlob=/home/bogdan/.cache/drkonqi/sentry-envelopes/*).
Mar 12 19:39:05 njordr systemd[3351]: Reached target Session services which should run early before the graphical session is brought up.
Mar 12 19:39:05 njordr systemd[3351]: Starting KDE Config Module Initialization...
Mar 12 19:39:05 njordr systemd[3351]: Starting KDE Global Shortcuts Server...
Mar 12 19:39:05 njordr systemd[3351]: Starting Baloo File Indexer Daemon...
Mar 12 19:39:05 njordr systemd[3351]: kde-baloo.service: Skipped due to 'exec-condition'.
Mar 12 19:39:05 njordr systemd[3351]: Condition check resulted in Baloo File Indexer Daemon being skipped.
Mar 12 19:39:05 njordr systemd[3351]: Starting Portal service...
Mar 12 19:39:05 njordr systemd[3351]: Started KDE Global Shortcuts Server.
Mar 12 19:39:05 njordr systemd[3351]: Starting flatpak document portal service...
Mar 12 19:39:05 njordr systemd[3351]: Starting sandboxed app permission store...
Mar 12 19:39:05 njordr kcminit_startup[53899]: Initializing  "/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_style.so"
Mar 12 19:39:05 njordr systemd[3351]: Started sandboxed app permission store.
Mar 12 19:39:05 njordr systemd[3351]: Started flatpak document portal service.
Mar 12 19:39:05 njordr rtkit-daemon[3421]: Supervising 0 threads of 0 processes of 0 users.
Mar 12 19:39:05 njordr rtkit-daemon[3421]: Supervising 0 threads of 0 processes of 0 users.
Mar 12 19:39:05 njordr rtkit-daemon[3421]: Supervising 0 threads of 0 processes of 0 users.
Mar 12 19:39:05 njordr kcminit_startup[53899]: Initializing  "/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_mouse.so"
Mar 12 19:39:05 njordr kcminit_startup[53899]: Initializing  "/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Mar 12 19:39:06 njordr systemd[3351]: Started KDE Config Module Initialization.
Mar 12 19:39:06 njordr systemd[3351]: Starting KDE Session Management Server...
Mar 12 19:39:06 njordr systemd[3351]: Started Unlock kwallet from pam credentials.
Mar 12 19:39:06 njordr systemd[3351]: Starting KDE Daemon 6...
Mar 12 19:39:06 njordr systemd[3351]: Starting KDE Window Manager...
Mar 12 19:39:06 njordr pam_kwallet_init[53942]: 2024/03/12 19:39:06 socat[53942] W address is opened in read-write mode but only supports read-only
Mar 12 19:39:06 njordr systemd[3351]: Started KDE Daemon 6.
Mar 12 19:39:06 njordr systemd[3351]: Starting KDE Configuration Module Initialization (Phase 1)...
Mar 12 19:39:06 njordr kded6[53939]: QDBusObjectPath: invalid path "/modules/kded_plasma-welcome"
Mar 12 19:39:06 njordr kded6[53939]: kf.dbusaddons: The kded module name "kded_plasma-welcome" is invalid!
Mar 12 19:39:06 njordr kcminit_startup[53899]: Initializing  "/usr/lib/qt6/plugins/plasma/kcms/systemsettings_qwidgets/kcm_kgamma.so"
Mar 12 19:39:06 njordr kded6[53939]: kf.coreaddons: The plugin "/usr/lib/qt6/plugins/kaccounts/daemonplugins/kaccounts_kio_webdav_plugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed
Mar 12 19:39:06 njordr kcminit_startup[53899]: Initializing  "/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_touchpad.so"
Mar 12 19:39:06 njordr kcminit_startup[53899]: kcm_touchpad: Using X11 backend
Mar 12 19:39:06 njordr systemd[3351]: Finished KDE Configuration Module Initialization (Phase 1).
Mar 12 19:39:06 njordr systemd[3351]: Started KDE Session Management Server.
Mar 12 19:39:06 njordr systemd[3351]: Starting KDE Plasma Workspace...
Mar 12 19:39:06 njordr kwin_x11[53940]: kwin_core: parsing edid failed
Mar 12 19:39:06 njordr systemd[3351]: Started KDE Window Manager.
Mar 12 19:39:06 njordr kded6[53939]: org.kde.plasma.printmanager.kded: unable to register service to dbus
Mar 12 19:39:06 njordr NetworkManager[2834]: <info>  [1710265146.4450] agent-manager: agent[f794e95ffcc43adb,:1.261/org.kde.plasma.networkmanagement/1000]: agent registered
Mar 12 19:39:06 njordr kded6[53939]: QDBusObjectPath: invalid path "/modules/plasma-session-shortcuts"
Mar 12 19:39:06 njordr kded6[53939]: kf.dbusaddons: The kded module name "plasma-session-shortcuts" is invalid!
Mar 12 19:39:06 njordr kded6[53939]: kcm_touchpad: Using X11 backend
Mar 12 19:39:06 njordr systemd[3351]: Starting KActivityManager Activity manager Service...
Mar 12 19:39:06 njordr kwin_x11[53940]: OpenGL vendor string:                   Intel
Mar 12 19:39:06 njordr kwin_x11[53940]: OpenGL renderer string:                 Mesa Intel(R) Graphics (ADL GT2)
Mar 12 19:39:06 njordr kwin_x11[53940]: OpenGL version string:                  4.6 (Compatibility Profile) Mesa 24.0.2-arch1.2
Mar 12 19:39:06 njordr kwin_x11[53940]: OpenGL shading language version string: 4.60
Mar 12 19:39:06 njordr kwin_x11[53940]: Driver:                                 Intel
Mar 12 19:39:06 njordr kwin_x11[53940]: GPU class:                              Unknown
Mar 12 19:39:06 njordr kwin_x11[53940]: OpenGL version:                         4.6
Mar 12 19:39:06 njordr kwin_x11[53940]: GLSL version:                           4.60
Mar 12 19:39:06 njordr kwin_x11[53940]: Mesa version:                           24.0.2
Mar 12 19:39:06 njordr kwin_x11[53940]: Requires strict binding:                yes
Mar 12 19:39:06 njordr kwin_x11[53940]: Virtual Machine:                        no
Mar 12 19:39:06 njordr kwin_x11[53940]: Timer query support:                    yes
Mar 12 19:39:06 njordr systemd[3351]: Started KDE Plasma Workspace.
Mar 12 19:39:06 njordr systemd[3351]: Reached target KDE Plasma Workspace Core.
Mar 12 19:39:06 njordr systemd[3351]: Starting Consume pending crashes using DrKonqi...
Mar 12 19:39:06 njordr systemd[3351]: Started Proxies GTK DBus menus to a Plasma readable format.
Mar 12 19:39:06 njordr systemd[3351]: Starting KDE PolicyKit Authentication Agent...
Mar 12 19:39:06 njordr systemd[3351]: Starting Powerdevil...
Mar 12 19:39:06 njordr systemd[3351]: Starting Xdg Desktop Portal For KDE...
Mar 12 19:39:06 njordr systemd[3351]: Started Handle legacy xembed system tray icons.
Mar 12 19:39:06 njordr systemd[3351]: Started Xdg Desktop Portal For KDE.
Mar 12 19:39:06 njordr systemd[1]: Started dbus-:1.2-org.kde.powerdevil.discretegpuhelper@1.service.
Mar 12 19:39:06 njordr systemd[1]: Started dbus-:1.2-org.kde.powerdevil.chargethresholdhelper@1.service.
Mar 12 19:39:06 njordr systemd[1]: Started dbus-:1.2-org.kde.powerdevil.backlighthelper@23.service.
Mar 12 19:39:07 njordr systemd[3351]: Started KDE PolicyKit Authentication Agent.
Mar 12 19:39:07 njordr polkit-kde-authentication-agent-1[54035]: New PolkitAgentListener  0x55a8964c0930
Mar 12 19:39:07 njordr polkit-kde-authentication-agent-1[54035]: Adding new listener  PolkitQt1::Agent::Listener(0x55a8964c0250) for  0x55a8964c0930
Mar 12 19:39:07 njordr polkit-kde-authentication-agent-1[54035]: Listener online
Mar 12 19:39:07 njordr polkitd[2956]: Registered Authentication Agent for unix-session:4 (system bus name :1.275 [/usr/lib/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Mar 12 19:39:07 njordr polkit-kde-authentication-agent-1[54035]: Authentication agent result: true
Mar 12 19:39:15 njordr systemd[1]: Stopping User Manager for UID 969...

Doesn't look like a failure.

if i select in sddm that i want plasma + xorg, the system freezes and i have to power off manually .

How freezing frozen is it really? Can you still switch the VT (ctrl+alt+F3)?
Can you suspend the compositor (SHIFT+Alt+F12)?
Can you log into an X11 session w/ a fresh user account?
(b/c of the edid error:) https://wiki.archlinux.org/title/KDE#Un … lution_set ?

And please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

colegu · 2024-03-13 04:56:31

http://0x0.st/HhdC.txt xorg.log

if i login with my normal user i can't do anything after plasma/x11 attempts to start. switch to VT doesn't work regardless of what DE i use. I suspect it is a nvidia thing (even though i have modesetting enabled). shift alt f12 doesn't do anything. the screen is completely blank and the mouse cursor appears for a while and then disappears completely. the only thing i can do after this is ctrl + alt + del which sometimes work, sometimes doesn't do anything so i have to long press the power button.

unexpectedly, login to X11 with a fresh user seemed to be working, although the kde interface had like 3 different taskbars at the bottom of the screen overlapping each other. but at least it worked. so it seems that during the crash there are some
corrupted thing in my home dir as well. i'll try to restore a backup and see how that works

thanks a lot @seth for the insight!

colegu · 2024-03-13 06:35:18

with the freshly created user, the X11/plasma experience is utterly unusable. taskbar is flickering, icons on the taskbar are much larger than expected, and only thing that seem to be working are click commands. no typing. if i try to type in a command in the launch searchbar i simply cannot. launching directly plasma/x11 creates several overlapping taskbars and a black desktop background. if i relaunch it with wayland only then i get a background and a single taskbar when relaunching x11, albeit not rendered properly and with a lot of flickering happening.

seth · 2024-03-13 08:20:22

[     4.757] (EE) AIGLX error: dlopen of /usr/lib/dri/i965_dri.so failed (/usr/lib/dri/i965_dri.so: cannot open shared object file: No such file or directory)
[     4.757] (EE) AIGLX error: unable to load driver i965
[     4.860] (II) IGLX: Loaded and initialized swrast
[     4.860] (II) GLX: Initialized DRISWRAST GL provider for screen 0

Start by removing xf86-video-intel, report back (obviously this will have no impact on the wayland situation)

As for your exising user, please post a system journal after attempting to log into that.

sudo journalctl -b | curl -F 'file=@-' 0x0.st

colegu · 2024-03-13 08:46:13

with the test user, after I removed the video-intel driver, i managed to login into plasma/x11, and managed to open up konsole and write a command. however, after several seconds the whole screen froze, and i'm only able to switch back to my wayland/plasma VT where the main user was logged in.

http://0x0.st/HhRl.txt - journalctl -b

http://0x0.st/HhRF.txt - xorg log corresponding to the plasma/x11 session that worked for couple of seconds and then crashed

edit: after the first crash i re-logged with the freshly created user back into plasma/x11 and everything seems to be working fine now... I might try to try with my main user and see what happens..

later edit: i managed to login to plasma/x11 with my main user, after 1 minute of kde trying to load it's stuff, (the background showed the kde gear spinning for some time. followed by a blank screen and then my normal DE env.)
i wander what will happen at the next logoff/logon, is the DE will show up quicker.
even later edit: nope. unfortunately it still takes 2 minutes to login into plasma/x11 - xorg log http://0x0.st/Hh7Z.txt
systemd log http://0x0.st/Hh7q.txt is soo full of errors...trying to get something useful out of it

once again, many thanks for you kind assistance

Last edited by colegu (2024-03-13 09:06:31)

seth · 2024-03-13 09:00:54

i'm only able to switch back to my wayland/plasma VT

The parallel wayland/X11 sessions might be an issue here.

As for the long login time, https://bbs.archlinux.org/viewtopic.php … 5#p2156595 ?

colegu · 2024-03-13 09:11:43

systemctl --user mask plasma-ksplash.service

this definitely improves startup, but it is still way slower than wayland( which takes like 1-2 seconds to load). x11 now loads roughly in 20 seconds or so.. way more reasonable than before, but not optimal still

seth · 2024-03-13 13:25:00

Mar 13 10:58:31 njordr sddm[3121]: Message received from greeter: Login
…
Mar 13 10:58:31 njordr systemd-logind[2749]: New session 10 of user bogdan.
…
Mar 13 10:58:32 njordr kwin_x11[30496]: kwin_core: parsing edid failed
Mar 13 10:58:32 njordr systemd[3324]: Started KDE Window Manager.
Mar 13 10:58:32 njordr kwin_x11[30496]: OpenGL vendor string:                   Intel
Mar 13 10:58:32 njordr kwin_x11[30496]: OpenGL renderer string:                 Mesa Intel(R) Graphics (ADL GT2)
…
^, file:///usr/share/kwin/effects/cube/contents/ui/ScreenView.qml:9:1: module "QtQuick3D" is not installed
…
Mar 13 10:58:32 njordr systemd[3324]: Started Portal service.
…
Mar 13 10:58:57 njordr kwin_x11[30496]: KActivities: FATAL ERROR: Failed to contact the activity manager daemon
…
Mar 13 10:59:24 njordr systemd[3324]: Starting KDE Session Restoration...
Mar 13 10:59:24 njordr (n-script)[30750]: app-login\x2dscript@autostart.service: Failed to execute /home/bogdan/bin/login-script: Exec format error
Mar 13 10:59:24 njordr systemd[3324]: app-at\x2dspi\x2ddbus\x2dbus@autostart.service: Skipped due to 'exec-condition'.
Mar 13 10:59:24 njordr systemd[3324]: Condition check resulted in AT-SPI D-Bus Bus being skipped.
Mar 13 10:59:24 njordr systemd[3324]: app-login\x2dscript@autostart.service: Main process exited, code=exited, status=203/EXEC
Mar 13 10:59:24 njordr systemd[3324]: app-login\x2dscript@autostart.service: Failed with result 'exit-code'.
Mar 13 10:59:24 njordr systemd[3324]: Failed to start login-script.

What is /home/bogdan/bin/login-script ?
Disable its autostart.

Mar 13 10:58:57 njordr kwin_x11[30496]: KActivities: FATAL ERROR: Failed to contact the activity manager daemon

is 25s after the session started, ie. a dbus timeout and you've plenty of

Mar 13 10:58:32 njordr plasmashell[30521]: kde.plasmashell: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.

pacman -Qikk kactivitymanagerd

and

Mar 13 10:58:32 njordr plasmashell[30521]: kde.plasmashell: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.

looks sketchy.

echo $DBUS_SESSION_BUS_ADDRESS

colegu · 2024-03-13 14:38:03

resuming from suspend to ram in plasma/x11 is a nightmare. the screen begins to flicker for a couple of minutes, the DE can be seen intermittently for a couple of seconds followed by long periods of blank screen. in the end, normal operation is resumed, but this is annoying af, since it's faster to boot the system (21 seconds til the DE loads, compared to at least a minute of flickering screens)

I really don't get it with these updates, i remember back in the day when they made kmail2 completely unusable with the baloo akonadi shit. i simply deleted kmail and returned to the good old annoying webmail (what a horrible experience).

What is /home/bogdan/bin/login-script ?
Disable its autostart.

something that i tried to use to automatically lock the screen after hibernate/suspend. which did not work anyways, but forgot to disable it. i'm commenting it's contents now

pacman -Qikk kactivitymanagerd
Name            : kactivitymanagerd
Version         : 6.0.1-1
Description     : System service to manage user activities and track the usage patterns
Architecture    : x86_64
URL             : https://kde.org/plasma-desktop/
Licenses        : LGPL-2.0-or-later
Groups          : plasma
Provides        : None
Depends On      : gcc-libs  glibc  kconfig  kcoreaddons  kcrash  kglobalaccel  ki18n  kio  kservice  kwindowsystem  kxmlgui  qt6-base
Optional Deps   : None
Required By     : plasma-workspace
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 786.59 KiB
Packager        : Antonio Rojas <arojas@archlinux.org>
Build Date      : Wed 06 Mar 2024 01:02:10 PM EET
Install Date    : Mon 11 Mar 2024 07:19:20 AM EET
Install Reason  : Installed as a dependency for another package
Install Script  : No
Validated By    : Signature

kactivitymanagerd: 238 total files, 0 altered files

echo $DBUS_SESSION_BUS_ADDRESS
unix:path=/run/user/1000/bus

again, thank you for your kind assistance, i'm really appreciating it!

Mar 13 10:58:32 njordr plasmashell[30521]: kde.plasmashell: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.

this is strange, i mean the timestamp. cause at that time plasmashell was up and running. however, after resuming from suspend to ram, once i had to restart plasmashell alltogether since the process crashed after the repeated flickering...

did not check if activitymanager was running though...

Mar 13 16:27:16 njordr kwin_x11[3417]: kwin_core: XCB error: 152 (BadDamage), sequence: 57409, resource id: 18899625, major code: 143 (DAMAGE), minor code: 3 (Subtract)
Mar 13 16:27:44 njordr kwin_x11[3417]: kwin_core: XCB error: 152 (BadDamage), sequence: 61406, resource id: 18899988, major code: 143 (DAMAGE), minor code: 3 (Subtract)
Mar 13 16:27:55 njordr kwin_x11[3417]: kwin_core: XCB error: 152 (BadDamage), sequence: 63311, resource id: 18900157, major code: 143 (DAMAGE), minor code: 3 (Subtract)
Mar 13 16:28:16 njordr kwin_x11[3417]: kwin_core: XCB error: 152 (BadDamage), sequence: 1285, resource id: 18900497, major code: 143 (DAMAGE), minor code: 3 (Subtract)
Mar 13 16:28:26 njordr kwin_x11[3417]: kwin_core: XCB error: 152 (BadDamage), sequence: 3232, resource id: 18900660, major code: 143 (DAMAGE), minor code: 3 (Subtract)
Mar 13 16:28:39 njordr kwin_x11[3417]: kwin_core: XCB error: 152 (BadDamage), sequence: 6252, resource id: 18900905, major code: 143 (DAMAGE), minor code: 3 (Subtract)
Mar 13 16:30:01 njordr kwin_x11[3417]: kwin_core: XCB error: 152 (BadDamage), sequence: 18528, resource id: 18902080, major code: 143 (DAMAGE), minor code: 3 (Subtract)
Mar 13 16:30:09 njordr kwin_x11[3417]: kwin_core: XCB error: 152 (BadDamage), sequence: 20594, resource id: 18902214, major code: 143 (DAMAGE), minor code: 3 (Subtract)

plenty of these errors happening after resuming from suspend to ram. seems that i'm not the only one getting this

Mar 13 16:25:07 njordr kglobalacceld[3360]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY'
Mar 13 16:25:07 njordr kglobalacceld[3360]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY'
Mar 13 16:25:07 njordr kglobalacceld[3360]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY'
Mar 13 16:25:07 njordr kglobalacceld[3360]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY'
Mar 13 16:25:07 njordr kglobalacceld[3360]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY'

hundreds of lines like this one fill the journal... which is strange, cause i've been using my xmodmap file for ages, since kde version 2.*
however, most of my keyboard shortcuts which worked on kde5 are not working in plasma6 anymore..

Last edited by colegu (2024-03-13 14:48:18)

seth · 2024-03-13 15:09:19

the screen begins to flicker for a couple of minutes, the DE can be seen intermittently for a couple of seconds followed by long periods of blank screen.

Screenlocker? Your script?

kactivitymanager and $DBUS_SESSION_BUS_ADDRESS actually look fine, XCB error can just be kwin trying to handle a gone window (plasma desktop window)

B/c of kf.windowsystem.keyserver.x11:

setxkbmap -print -query; xmodmap -pm

and post your xmodmap file.

most of my keyboard shortcuts which worked on kde5 are not working in plasma6 anymore

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
An inconclusive list of examples would probably suffice (shortcut and what it's supposed to do)

colegu · 2024-03-13 16:13:53

seth wrote:

the screen begins to flicker for a couple of minutes, the DE can be seen intermittently for a couple of seconds followed by long periods of blank screen.
Screenlocker? Your script?

screenlocker is set to automatically lock the screen after waking from sleep and after 35 minutes of inactivity.. i'm not sure this causes the problem since after each wake up from suspend the screen is not locked, it just flickers. maybe x11 tries to lock it but is failing, hence the flickering.. i'll disable this and see what happens

B/c of kf.windowsystem.keyserver.x11:
setxkbmap -print -query; xmodmap -pm
and post your xmodmap file.

clear Mod4
keycode 17 = 8 asterisk multiply periodcentered
keycode 21 = equal plus dagger plusminus
keycode 24 = q Q acircumflex adiaeresis
keycode 25 = w W ediaeresis ae
keycode 26 = e E e Greek_epsilon
keycode 27 = r R Greek_rho Greek_omega
keycode 28 = t T U021B Greek_tau
keycode 29 = y Y thorn Greek_theta
keycode 30 = u U udiaeresis uacute
keycode 31 = i I icircumflex iacute
keycode 32 = o O odiaeresis oslash
keycode 33 = p P p Greek_pi 
keycode 38 = a A abreve aring
keycode 39 = s S U0219 scaron
keycode 41 = f F Greek_phi Greek_psi
keycode 40 = d D Greek_delta partialderivative
keycode 42 = g G g Greek_gamma
keycode 43 = h H Greek_chi Greek_zeta 
keycode 44 = j J Greek_xi twosuperior 
keycode 45 = k K Greek_eta twosuperior 
keycode 46 = l L Greek_sigma Greek_lambda 
keycode 52 = z Z degree zcaron
keycode 53 = x X ssharp ediaeresis
keycode 54 = c C ccaron ccedilla
keycode 55 = v V integral nabla
keycode 56 = b B Greek_beta Greek_alpha
keycode 57 = n N n Greek_nu
keycode 58 = m M mu eth
keycode 133 = Mode_switch
add Mod4 = Mode_switch
keycode 115 = End
keycode 156 = XF86AudioPlay
keycode 134 = Print

most of my keyboard shortcuts which worked on kde5 are not working in plasma6 anymore
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
An inconclusive list of examples would probably suffice (shortcut and what it's supposed to do)

sorry,
for example ctrl+alt+x is still functioning as a launcher for konsole
yet, xf8audioplay does not work with clementine anymore. but this is really the last of my issues

seth · 2024-03-13 17:09:22

clear Mod4
keycode 133 = Mode_switch
add Mod4 = Mode_switch

That's the meta (windows, super) key, you're mapping it to altgr…

xf8audioplay does not work with clementine anymore

Sounds like https://bbs.archlinux.org/viewtopic.php?id=293520

colegu · 2024-03-13 17:09:27

https://streamable.com/kj99ln

this is a sample of the screen flickering

seth · 2024-03-13 17:20:18

wrt the video, check the system journal after that - either kwin or plasmashell will show up there.
Most likely it's the compositor (since some konsole windows also disappear), SHIFT+Alt+F12 would probably end that.

V1del · 2024-03-13 17:22:10

The shortcut bug with clementine should be fixed in 6.0.2 currently in testing: https://bugs.kde.org/show_bug.cgi?id=482712

That flickering looks like fallout from

[    2.881344] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DP-2
[    2.890428] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DP-2

which could be a bug with the monitor/the nvidia driver

colegu · 2024-03-13 18:21:01

seth wrote:

clear Mod4
keycode 133 = Mode_switch
add Mod4 = Mode_switch
That's the meta (windows, super) key, you're mapping it to altgr…
xf8audioplay does not work with clementine anymore
Sounds like https://bbs.archlinux.org/viewtopic.php?id=293520

indeed, it's a simple mapping that i'm doing here, nothing fancy, so i don't expect that this crashes x11 the way it does.

i'll take a look at the link you mentioned, but at the moment i have to sort out first the flickering thing, which is the most annoying part.
thanks

V1del wrote:

The shortcut bug with clementine should be fixed in 6.0.2 currently in testing: https://bugs.kde.org/show_bug.cgi?id=482712
That flickering looks like fallout from
[    2.881344] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DP-2
[    2.890428] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DP-2
which could be a bug with the monitor/the nvidia driver

the same nvidia driver works well with wayland. no flickering there. no flickering with the same nvidia driver using kde5/x11.

seth wrote:

wrt the video, check the system journal after that - either kwin or plasmashell will show up there.
Most likely it's the compositor (since some konsole windows also disappear), SHIFT+Alt+F12 would probably end that.

shift-alt-f12 doens't do anything when the flicker happens ... the system is completely frozen during that time. once several flickering cycles happen, everything gets back to normal. but it usually take a minute to settle, which is quite annoying..

Last edited by colegu (2024-03-13 18:26:53)

seth · 2024-03-13 20:35:12

X11 is running on the intel chip and according to the xorg log you posted in http://0x0.st/HhdC.txt nothing is attached to the nvidia one either.

Try to disable the screenlocker (also for suspending the system) and post an updated Xorg log and the system journal after waking from an S3 to the flicker
https://wiki.archlinux.org/title/Xorg#General

sudo journalctl -b | curl -F 'file=@-' 0x0.st

colegu · 2024-03-14 06:49:05

http://0x0.st/HFPK.txt
http://0x0.st/HFPP.txt

disabled completely the screen locking. booted up, everything went fine (albeit a slow load of X11 when compared to wayland). closed the lid, a suspend was triggered, opened the lid, clicked a key, screen went on. everything fine. no flicker. then locked the screen and flickering began. then grabbed the systemd and xorg logs and pasted them above.

i'm however puzzled as to why the xf86-intel driver does not work and i need to rely on glamor instead? if the intel driver is installed then x11 loading will result in a completely blank screen, with the only option to poweroff the machine. previously i had the intel driver installed, with the same kernel that i'm using now, and everything was fine. indeed, upgrading the a newer kernel resulted in random crashes that occured after a resume from suspend/hibernate, but i did not have the time to look into these issues, so ireturned to 6.7.3 which i'm also using now.

seth · 2024-03-14 09:19:25

why the xf86-intel driver does not work

Being phased out, you still can use it w/ ancient hardware and mesa-amber or middle-age hardware and using "Option DRI "iris"" explcitily, https://wiki.archlinux.org/title/Intel_ … ecent_GPUs but on newest HW it basically doesn't work anymore at all.

The only thing that show up in your journal is kglobalacceld throwing a complete tantrum because

Mar 14 08:39:41 njordr kglobalacceld[3367]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY'

you've completely mapped way the meta modifier.
I'd recommend to use the xkb option(s) I mentioned in your other thread and see whether that calms the daemon … and what impact that has on the screen locker.

Does

xset dpms force off

cause the "flicker" also?
(Though from your video showing the mouse cursor to remain, I don't think so)

Arch Linux

#1 2024-03-11 15:48:53

[SOLVED]crash during system update, xorg-x11 not working, only wayland

#2 2024-03-12 16:05:38

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#3 2024-03-12 17:37:51

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#4 2024-03-12 17:54:54

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#5 2024-03-12 17:59:27

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#6 2024-03-12 18:20:06

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#7 2024-03-12 20:24:24

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#8 2024-03-13 04:56:31

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#9 2024-03-13 06:35:18

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#10 2024-03-13 08:20:22

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#11 2024-03-13 08:46:13

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#12 2024-03-13 09:00:54

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#13 2024-03-13 09:11:43

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#14 2024-03-13 13:25:00

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#15 2024-03-13 14:38:03

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#16 2024-03-13 15:09:19

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#17 2024-03-13 16:13:53

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#18 2024-03-13 17:09:22

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#19 2024-03-13 17:09:27

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#20 2024-03-13 17:20:18

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#21 2024-03-13 17:22:10

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#22 2024-03-13 18:21:01

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#23 2024-03-13 20:35:12

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#24 2024-03-14 06:49:05

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

#25 2024-03-14 09:19:25

Re: [SOLVED]crash during system update, xorg-x11 not working, only wayland

Board footer