| View previous topic :: View next topic |
| Author |
Message |
paintchip
n00b
Joined: 02 Jan 2010
Posts: 58
|
 Posted: Tue Nov 14, 2023 12:55 pm Post subject: KDE - Need to Run Startx Twice for Applications to Work |
 |
|
Hey all,
I ran into a strange problem shortly after upgrading a couple of weeks ago. When I first log in and run KDE with startx, it starts, but no applications will open. It’s like they start to open then crash, but I don’t see anything about it in the logs. Then, if I go to another virtual terminal and run startx, KDE runs as expected and everything works. It doesn't matter which virtual terminal I do the first startx from either.
I don't see anything in the list of updates that would have broken KDE or X, nor could I find any errors in the Xorg log. Also, strangely, if I allow startx to run automatically on login (with the line below in my .bash_profile), KDE doesn’t start at all (or does so after failing for minutes). I'm definitely stumped and would appreciate any help I can get 
| Code: | | [[ -t 0 && $(tty) == /dev/tty1 && ! $DISPLAY ]] && exec startx |
No errors in Xorg.log, but I did see this in syslog:
| Code: | | dbus-daemon[1402]: [system] Activated service 'net.hadess.PowerProfiles' failed: Launch helper exited with unknown return code 1 |
These are the applications that were updated before the issue started happening. I may have also compiled a new kernel on the same day, but rolling back kernels hasn't fixed the issue.
| Code: |
sys-apps/hwdata-0.374
app-office/libreoffice-l10n-7.5.6.2
sys-apps/systemd-utils-254.5-r1
net-dns/libidn2-2.3.4-r1
dev-python/typing-extensions-4.8.0
dev-libs/libsodium-1.0.19-r1
media-libs/harfbuzz-8.2.0
dev-python/setuptools-scm-8.0.4
dev-python/trove-classifiers-2023.9.19
dev-python/urllib3-2.0.6
app-text/poppler-23.09.0
net-libs/libvncserver-0.9.14-r1
kde-apps/kitinerary-23.04.3
app-crypt/keysmith-23.04.3
app-crypt/gpgme-1.22.0
sys-apps/smartmontools/smartmontools-7.4
sys-apps/iproute2-6.5.0
sys-fs/zfs-kmod-2.1.13
sys-fs/zfs/zfs-2.1.13
sys-fs/btrfs-progs/btrfs-progs-6.5.2
www-client/chromium-118.0.5993.88
media-video/ffmpeg-6.0-r9
www-client/icecat-115.4.0
media-video/obs-studio-29.1.3-r2
app-office/libreoffice-7.5.6.2
app-editors/vim/vim-9.0.1627 |
And just in case this might be GPU related, I have a GPU: Radeon 6850M XT that I was never able to get to sleep properly. Otherwise everything has been working fine for a while now.
https://forums.gentoo.org/viewtopic-t-1163225-highlight-.html |
|
| Back to top |
|
 |
finoderi
Tux's lil' helper
Joined: 29 Oct 2021
Posts: 79
|
| Posted: Tue Nov 14, 2023 4:18 pm Post subject: |
|
|
Copy xinitrc from /etc/X11/xinit/ to your /home folder as .xinitrc and add following lines to the end of the file: | Code: | export XDG_SESSION_TYPE=x11
export DESKTOP_SESSION=plasma
exec dbus-run-session startplasma-x11 |
As for the 'Activated service 'net.hadess.PowerProfiles' failed' - that's a side effect of nobody giving a shit. But it's harmless. |
|
| Back to top |
|
|
APolozov
Apprentice
Joined: 28 Sep 2006
Posts: 194
Location: Voronezh, Russia
|
| Posted: Tue Nov 14, 2023 4:31 pm Post subject: |
|
|
The same thing for me. But my GPU is 1050Ti (with nvidia-drivers) + wayland session.
If I manualy run "plasma_sesion" all thing working, but start is wery slow.
_________________
Excuse my bad English, I only study it. |
|
| Back to top |
|
|
paintchip
n00b
Joined: 02 Jan 2010
Posts: 58
|
| Posted: Tue Nov 14, 2023 7:18 pm Post subject: |
|
|
| finoderi wrote: | Copy xinitrc from /etc/X11/xinit/ to your /home folder as .xinitrc and add following lines to the end of the file: | Code: | export XDG_SESSION_TYPE=x11
export DESKTOP_SESSION=plasma
exec dbus-run-session startplasma-x11 |
As for the 'Activated service 'net.hadess.PowerProfiles' failed' - that's a side effect of nobody giving a shit. But it's harmless. |
Thanks for the suggestion. Unfortunately copying over .xinitrc and adding those lines didn't fix the issue.
APolozov - Did it also happen around an update for you? |
|
| Back to top |
|
|
finoderi
Tux's lil' helper
Joined: 29 Oct 2021
Posts: 79
|
| Posted: Tue Nov 14, 2023 8:03 pm Post subject: |
|
|
| paintchip wrote: | | Thanks for the suggestion. Unfortunately copying over .xinitrc and adding those lines didn't fix the issue. |
Check if dbus is in the default runlevel. If not then | Code: | | # rc-update add dbus |
|
|
| Back to top |
|
|
paintchip
n00b
Joined: 02 Jan 2010
Posts: 58
|
| Posted: Tue Nov 14, 2023 8:43 pm Post subject: |
|
|
| finoderi wrote: | | paintchip wrote: | | Thanks for the suggestion. Unfortunately copying over .xinitrc and adding those lines didn't fix the issue. |
Check if dbus is in the default runlevel. If not then | Code: | | # rc-update add dbus |
|
Thanks for another helpful suggestion.
It was actually under Dynamic Runlevel: needed/wanted. I changed it to default, but it didn't work and I can't seem to set it to the other run level. Hopefully that won't hurt anything.
I was actually able to figure out the issue based on another problem i had in the past. I noticed that for a split second after I start KDE (the first time), I can sometimes open an application, then it stops. It seemed a lot like a problem I had in the past related to my hostname getting changed by NM, which broke KDE because of the Xorg MIT auth cookie being hostname locked. My hostname looked fine, but /etc/conf.d/hostname had been changed back to localhost. Once I set it to my hostname things started working again. NM was just connecting to my network so fast that I didn't notice it was the cause.
The only thing that still isn't working is automatically starting KDE on login. Starting it manually works normally, but if I startx from my bash profile, I see the following errors in the Xorg logs. It's almost as if X is trying to start before everything is properly loaded.
| Code: |
[ 8.470] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 8.470] (EE) open /dev/dri/card0: No such file or directory
[ 8.470] (WW) Falling back to old probe method for modesetting
[ 8.470] (EE) open /dev/dri/card0: No such file or directory
[ 8.470] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 8.470] (EE) Screen 0 deleted because of no matching config section.
[ 8.470] (II) UnloadModule: "modesetting"
[ 8.470] (EE) Device(s) detected, but none match those in the config file.
[ 8.470] (EE)
Fatal server error:
[ 8.470] (EE) no screens found(EE)
[ 8.470] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 8.470] (EE) Please also check the log file at "/home/rick/.local/share/xorg/Xorg.0.log" for additional information.
[ 8.470] (EE)
[ 8.471] (EE) Server terminated with error (1). Closing log file.
|
|
|
| Back to top |
|
|
APolozov
Apprentice
Joined: 28 Sep 2006
Posts: 194
Location: Voronezh, Russia
|
| Posted: Tue Nov 14, 2023 9:19 pm Post subject: |
|
|
| paintchip wrote: |
APolozov - Did it also happen around an update for you? |
Yes, the first time it happened a few weeks ago, the partial removal of KDE config files temporarily helped, today it happened again (were updated "egl-wayland, vlc, nvidia-drivers", nothing from plasma).
_________________
Excuse my bad English, I only study it. |
|
| Back to top |
|
|
paintchip
n00b
Joined: 02 Jan 2010
Posts: 58
|
| Posted: Tue Nov 14, 2023 9:34 pm Post subject: |
|
|
| APolozov wrote: | | paintchip wrote: |
APolozov - Did it also happen around an update for you? |
Yes, the first time it happened a few weeks ago, the partial removal of KDE config files temporarily helped, today it happened again (were updated "egl-wayland, vlc, nvidia-drivers", nothing from plasma). |
Is it anything like what I was experiencing in this thread? I didn't notice this time because NM was connecting to the network so fast, but the windows crashing part of my issue was cased by the hostname not matching what the xorg auth was looking for. I'm not sure if Wayland uses a similar auth process or not, though. |
|
| Back to top |
|
|
APolozov
Apprentice
Joined: 28 Sep 2006
Posts: 194
Location: Voronezh, Russia
|
| Posted: Wed Nov 15, 2023 5:53 am Post subject: |
|
|
I don't use 'auth' at all and have autologon by sddm (which runs plasmawayland for me).
After reboot I see black screen with mouse pointer but plasma hotkey works (I can start Krunner, which runs plasma_session).
_________________
Excuse my bad English, I only study it. |
|
| Back to top |
|
|
paintchip
n00b
Joined: 02 Jan 2010
Posts: 58
|
| Posted: Wed Nov 15, 2023 5:18 pm Post subject: |
|
|
| APolozov wrote: | I don't use 'auth' at all and have autologon by sddm (which runs plasmawayland for me).
After reboot I see black screen with mouse pointer but plasma hotkey works (I can start Krunner, which runs plasma_session). |
That's a bit different than the issue I was having. Once you start plasma_session from krunner, things work normally? |
|
| Back to top |
|
|
APolozov
Apprentice
Joined: 28 Sep 2006
Posts: 194
Location: Voronezh, Russia
|
| Posted: Thu Nov 16, 2023 6:27 am Post subject: |
|
|
| paintchip wrote: |
That's a bit different than the issue I was having. Once you start plasma_session from krunner, things work normally? |
Yes, all things work, but in log file I see the same string "[dbus-daemon] [system] Activated service 'net.hadess.PowerProfiles' failed: Launch helper exited with unknown return code 1" (dbus runned and working), and I don't find any other errors.
_________________
Excuse my bad English, I only study it. |
|
| Back to top |
|
|
finoderi
Tux's lil' helper
Joined: 29 Oct 2021
Posts: 79
|
| Posted: Thu Nov 16, 2023 7:28 am Post subject: |
|
|
May be we should have started from the beginning.
What 'never able to get to sleep properly' means? Hibernation doesn't work? I have RX6600, never had any issues with sleep to RAM or hibernation.
Does dmesg output contain any errors? What kernel do you use?
How do you start KDE? With SDDM? Then you don't need .xinitrc.
And probably this command would be better to start Xorg: | Code: | if shopt -q login_shell; then
[[ -f ~/.bashrc ]] && source ~/.bashrc
[[ -t 0 && $(tty) == /dev/tty1 && ! $DISPLAY ]] && exec startx
fi |
|
|
| Back to top |
|
|
APolozov
Apprentice
Joined: 28 Sep 2006
Posts: 194
Location: Voronezh, Russia
|
| Posted: Thu Nov 16, 2023 10:01 am Post subject: |
|
|
I have no sleep, no hibernation. My home desktop work 24/7 and able to rebooting only after upgrading kernel or nvidia-drivers (last time ago), I have "world" updated every day, kernel+plasma+all installed parts of xorg is current stable version.
Dmesg have no error (exclude that string), graphics enviroment starting automaticaly by "display-manager" on "default" (yes SDDM + wayalnd session) and don't using ".xinitrc", all configs were tuned many month ago and worked perfectly.
But last two month I have that trouble twice after upgrading and rebooting.
Due to a rare reboot, I can't track down the specific package that is causing the problem.
I do not want to again delete plasma configs and configure everything again without understanding the problem.
_________________
Excuse my bad English, I only study it. |
|
| Back to top |
|
|
finoderi
Tux's lil' helper
Joined: 29 Oct 2021
Posts: 79
|
| Posted: Thu Nov 16, 2023 7:00 pm Post subject: |
|
|
| APolozov wrote: | | I have no sleep, no hibernation. |
I meant this: | paintchip wrote: | | I have a GPU: Radeon 6850M XT that I was never able to get to sleep properly. |
I'm not sure you have the same problem but who knows.
I had some problems with KDE in the past on my father's PC where Arch was installed. Everything have been working fine for two years and then after a major KDE update everything outside the shell was gone. Xorg refused to start no matter what I tried. I had to wipe out KDE completely and install it from scratch. So yeah, KDE devs are funny guys. |
|
| Back to top |
|
|
paintchip
n00b
Joined: 02 Jan 2010
Posts: 58
|
| Posted: Fri Nov 17, 2023 7:28 am Post subject: |
|
|
Good point Finoderi. The problems might be more related than I thought.
Apolozov, I'm curious, do you also have issues with your compositor on KDE/Kwin? I started having issues with it crashing a couple of months ago (around the time you started having trouble) and the black screen on startup sounds a lot like what happens to me when the compositor crashes on startup.
Can you try not allowing the compositor to start when the system starts in order to see if it's causing your problems.
System Settings > Hardware > Display and Monitor > Compositor -> Uncheck "Enable Compositor on Startup." Also see if there is a warning about it crashing. The message I get is "OpenGL compositing has crashed kwin in the past. This was most likely due to a driver bug." |
|
| Back to top |
|
|
APolozov
Apprentice
Joined: 28 Sep 2006
Posts: 194
Location: Voronezh, Russia
|
| Posted: Fri Nov 17, 2023 12:03 pm Post subject: |
|
|
| paintchip wrote: |
System Settings > Hardware > Display and Monitor > Compositor -> Uncheck "Enable Compositor on Startup." Also see if there is a warning about it crashing. The message I get is "OpenGL compositing has crashed kwin in the past. This was most likely due to a driver bug." |
I have'nt such an option or checkbox in "Compositor", only dropboxlist "latency" and checkbox "Reduce latency by allowing screen tearing...."
Maybe it's because of wayland session?
_________________
Excuse my bad English, I only study it. |
|
| Back to top |
|
|
APolozov
Apprentice
Joined: 28 Sep 2006
Posts: 194
Location: Voronezh, Russia
|
| Posted: Fri Nov 24, 2023 5:16 pm Post subject: |
|
|
I found where my plasma writes errors.
cat ~/.local/share/sddm/wayland-session.log
| Code: |
org.kde.startup: not a reply org.freedesktop.locale1 QDBusMessage(type=Error, service="org.freedesktop.DBus", error name="org.freedesktop.DBus.Error.ServiceUnknown", error message="The name org.freedesktop.locale1 was not provided by any .service files", signature="s", contents=("The name org.freedesktop.locale1 was not provided by any .service files") )
dbus-daemon[2687]: [session uid=1000 pid=2687] Activating service name='org.kde.KSplash' requested by ':1.0' (uid=1000 pid=2691 comm="/usr/bin/startplasma-wayland")
kdeinit5: preparing to launch '/usr/lib64/libexec/kf5/klauncher'
kdeinit5: Launched KLauncher, pid = 2709, result = 0
No backend specified, automatically choosing drm
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
OpenGL version string: 3.1.0 NVIDIA 535.129.03
OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 535.129.3
GPU class: Unknown
OpenGL version: 3.1
GLSL version: 1.40
Linux kernel version: 6.1.57
Requires strict binding: no
GLSL shaders: yes
Texture NPOT support: yes
Virtual Machine: no
kwin_xkbcommon: XKB: [XKB-489] ru:314:21: numeric keysym "0x10004d5" (16778453)
kwin_xkbcommon: XKB: [XKB-489] ru:314:34: numeric keysym "0x10004d4" (16778452)
kwin_xkbcommon: XKB: [XKB-489] ru:325:21: numeric keysym "0x10004d5" (16778453)
kwin_xkbcommon: XKB: [XKB-489] ru:325:34: numeric keysym "0x10004d4" (16778452)
kwin_xkbcommon: XKB: [XKB-489] ru:334:49: numeric keysym "0x10004f3" (16778483)
kwin_xkbcommon: XKB: [XKB-489] ru:334:62: numeric keysym "0x10004f2" (16778482)
kwin_xkbcommon: XKB: [XKB-489] ru:335:49: numeric keysym "0x10004d7" (16778455)
kwin_xkbcommon: XKB: [XKB-489] ru:335:62: numeric keysym "0x10004d6" (16778454)
kwin_xkbcommon: XKB: [XKB-489] ru:336:49: numeric keysym "0x10004d1" (16778449)
kwin_xkbcommon: XKB: [XKB-489] ru:336:62: numeric keysym "0x10004d0" (16778448)
kwin_xkbcommon: XKB: [XKB-489] ru:337:49: numeric keysym "0x10004ab" (16778411)
kwin_xkbcommon: XKB: [XKB-489] ru:337:62: numeric keysym "0x10004aa" (16778410)
kwin_xkbcommon: XKB: [XKB-489] ru:353:21: numeric keysym "0x10004dd" (16778461)
kwin_xkbcommon: XKB: [XKB-489] ru:353:34: numeric keysym "0x10004dc" (16778460)
kwin_xkbcommon: XKB: [XKB-489] ru:354:21: numeric keysym "0x10004e7" (16778471)
kwin_xkbcommon: XKB: [XKB-489] ru:354:34: numeric keysym "0x10004e6" (16778470)
kwin_xkbcommon: XKB: [XKB-489] ru:355:21: numeric keysym "0x10004f5" (16778485)
kwin_xkbcommon: XKB: [XKB-489] ru:355:34: numeric keysym "0x10004f4" (16778484)
kwin_xkbcommon: XKB: [XKB-489] ru:356:21: numeric keysym "0x10004e5" (16778469)
kwin_xkbcommon: XKB: [XKB-489] ru:356:34: numeric keysym "0x10004e4" (16778468)
kwin_xkbcommon: XKB: [XKB-489] ru:357:21: numeric keysym "0x10004df" (16778463)
kwin_xkbcommon: XKB: [XKB-489] ru:357:34: numeric keysym "0x10004de" (16778462)
kwin_xkbcommon: XKB: [XKB-489] ru:494:32: numeric keysym "0x10004a1" (16778401)
kwin_xkbcommon: XKB: [XKB-489] ru:494:56: numeric keysym "0x10004a0" (16778400)
kwin_xkbcommon: XKB: [XKB-489] ru:496:32: numeric keysym "0x10004ab" (16778411)
kwin_xkbcommon: XKB: [XKB-489] ru:496:56: numeric keysym "0x10004aa" (16778410)
kwin_xkbcommon: XKB: [XKB-489] ru:498:32: numeric keysym "0x1000499" (16778393)
kwin_xkbcommon: XKB: [XKB-489] ru:498:56: numeric keysym "0x1000498" (16778392)
kwin_wayland_drm: Failed to create gamma blob! Недопустимый аргумент
dbus-daemon[2687]: [session uid=1000 pid=2687] Successfully activated service 'org.kde.KSplash'
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Could not resolve keysym XF86CameraAccessEnable
> Warning: Could not resolve keysym XF86CameraAccessDisable
> Warning: Could not resolve keysym XF86CameraAccessToggle
> Warning: Could not resolve keysym XF86NextElement
> Warning: Could not resolve keysym XF86PreviousElement
> Warning: Could not resolve keysym XF86AutopilotEngageToggle
> Warning: Could not resolve keysym XF86MarkWaypoint
> Warning: Could not resolve keysym XF86Sos
> Warning: Could not resolve keysym XF86NavChart
> Warning: Could not resolve keysym XF86FishingChart
> Warning: Could not resolve keysym XF86SingleRangeRadar
> Warning: Could not resolve keysym XF86DualRangeRadar
> Warning: Could not resolve keysym XF86RadarOverlay
> Warning: Could not resolve keysym XF86TraditionalSonar
> Warning: Could not resolve keysym XF86ClearvuSonar
> Warning: Could not resolve keysym XF86SidevuSonar
> Warning: Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
kdeinit5: opened connection to :1
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported maximum keycode 708, clipping.
> X11 cannot support keycodes above 255.
> Warning: Could not resolve keysym XF86CameraAccessEnable
> Warning: Could not resolve keysym XF86CameraAccessDisable
> Warning: Could not resolve keysym XF86CameraAccessToggle
> Warning: Could not resolve keysym XF86NextElement
> Warning: Could not resolve keysym XF86PreviousElement
> Warning: Could not resolve keysym XF86AutopilotEngageToggle
> Warning: Could not resolve keysym XF86MarkWaypoint
> Warning: Could not resolve keysym XF86Sos
> Warning: Could not resolve keysym XF86NavChart
> Warning: Could not resolve keysym XF86FishingChart
> Warning: Could not resolve keysym XF86SingleRangeRadar
> Warning: Could not resolve keysym XF86DualRangeRadar
> Warning: Could not resolve keysym XF86RadarOverlay
> Warning: Could not resolve keysym XF86TraditionalSonar
> Warning: Could not resolve keysym XF86ClearvuSonar
> Warning: Could not resolve keysym XF86SidevuSonar
> Warning: Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
Initializing "/usr/lib64/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Initializing "/usr/lib64/qt5/plugins/plasma/kcms/systemsettings/kcm_mouse.so"
Initializing "/usr/lib64/qt5/plugins/plasma/kcms/systemsettings/kcm_style.so"
kdeinit5: Got SETENV 'GTK_RC_FILES=/etc/gtk/gtkrc:/home/pan/.gtkrc:/home/pan/.config/gtkrc' from launcher.
kdeinit5: Got SETENV 'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/pan/.gtkrc-2.0:/home/pan/.config/gtkrc-2.0' from launcher.
org.kde.plasma.session: process job "kcminit_startup" finished with exit code 0
dbus-daemon[2687]: [session uid=1000 pid=2687] Activating service name='org.kde.ActivityManager' requested by ':1.8' (uid=1000 pid=2771 comm="/usr/bin/kded5")
Installing the delayed initialization callback.
dbus-daemon[2687]: [session uid=1000 pid=2687] Successfully activated service 'org.kde.ActivityManager'
Qt: Session management error: networkIdsList argument is NULL
kdeinit5: Got SETENV 'SESSION_MANAGER=local/pan-homlin:@/tmp/.ICE-unix/2781,unix/pan-homlin:/tmp/.ICE-unix/2781' from launcher.
kdeinit5: Got SETENV 'SESSION_MANAGER=local/pan-homlin:@/tmp/.ICE-unix/2781,unix/pan-homlin:/tmp/.ICE-unix/2781' from launcher.
Initializing "/usr/lib64/qt5/plugins/plasma/kcms/systemsettings/kcm_kgamma.so"
Xlib XKB extension major= 1 minor= 0
X server XKB extension major= 1 minor= 0
KXMessages used on non-X11 platform! This is an application bug.
New PolkitAgentListener 0x55b49fd39cf0
Adding new listener PolkitQt1::Agent::Listener(0x55b49fd4a9c0) for 0x55b49fd39cf0
Listener online
Authentication agent result: true
Checking screens: available: (QScreen(0x5648d77a7810, name="HDMI-A-1")) redundant: QHash() fake: QSet() all: (QScreen(0x5648d77a7810, name="HDMI-A-1"))
kf.plasma.quick: Applet preload policy set to 1
org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
org.kde.powerdevil: org.kde.powerdevil.backlighthelper.brightness failed
Схема «org.gnome.desktop.a11y.applications» отсутствует
Initializing "/usr/lib64/qt5/plugins/plasma/kcms/systemsettings/kcm_touchpad.so"
Delayed initialization.
QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.18'
Reloading the khotkeys configuration
Version 2 File!
true
Imported file "/usr/share/khotkeys/defaults.khotkeys"
Imported file "/usr/share/khotkeys/kde32b1.khotkeys"
Imported file "/usr/share/khotkeys/konqueror_gestures_kde321.khotkeys"
org.kde.powerdevil: Handle button events action could not check for screen configuration
org.kde.powerdevil: The profile "AC" tried to activate "DimDisplay" a non-existent action. This is usually due to an installation problem, a configuration problem, or because the action is not supported
org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Known activities: ("5b779dec-38ea-4bce-a137-3f1a43e2ef38")
Initializing "/usr/lib64/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
No provider of eglDestroyImageKHR found. Requires one of:
EGL_KHR_image
EGL_KHR_image_base
EGL 15
The Wayland connection broke. Did the Wayland compositor die?
The Wayland connection broke. Did the Wayland compositor die?
The Wayland connection broke. Did the Wayland compositor die?
The Wayland connection broke. Did the Wayland compositor die?
The Wayland connection broke. Did the Wayland compositor die?
The Wayland connection broke. Did the Wayland compositor die?
The Wayland connection broke. Did the Wayland compositor die?
The Wayland connection broke. Did the Wayland compositor die?
The Wayland connection broke. Did the Wayland compositor die?
(EE) failed to read Wayland events: Broken pipe
kdeinit5: KLauncher died unexpectedly.
kdeinit5: preparing to launch '/usr/lib64/libexec/kf5/klauncher'
kdeinit5: Launched KLauncher, pid = 2960, result = 0
kdeinit5: PID 2709 terminated.
No backend specified, automatically choosing drm
The X11 connection broke (error 1). Did the X11 server die?
The X11 connection broke (error 1). Did the X11 server die?
The X11 connection broke (error 1). Did the X11 server die?
The X11 connection broke (error 1). Did the X11 server die?
kdeinit5: Fatal IO error: client killed
kdeinit5: sending SIGHUP to children.
kdeinit5: sending SIGTERM to children.
kdeinit5: Exit.
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
OpenGL version string: 3.1.0 NVIDIA 535.129.03
OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 535.129.3
GPU class: Unknown
OpenGL version: 3.1
GLSL version: 1.40
Linux kernel version: 6.1.57
Requires strict binding: no
GLSL shaders: yes
Texture NPOT support: yes
Virtual Machine: no
kwin_xkbcommon: XKB: [XKB-489] ru:314:21: numeric keysym "0x10004d5" (16778453)
kwin_xkbcommon: XKB: [XKB-489] ru:314:34: numeric keysym "0x10004d4" (16778452)
kwin_xkbcommon: XKB: [XKB-489] ru:325:21: numeric keysym "0x10004d5" (16778453)
kwin_xkbcommon: XKB: [XKB-489] ru:325:34: numeric keysym "0x10004d4" (16778452)
kwin_xkbcommon: XKB: [XKB-489] ru:334:49: numeric keysym "0x10004f3" (16778483)
kwin_xkbcommon: XKB: [XKB-489] ru:334:62: numeric keysym "0x10004f2" (16778482)
kwin_xkbcommon: XKB: [XKB-489] ru:335:49: numeric keysym "0x10004d7" (16778455)
kwin_xkbcommon: XKB: [XKB-489] ru:335:62: numeric keysym "0x10004d6" (16778454)
kwin_xkbcommon: XKB: [XKB-489] ru:336:49: numeric keysym "0x10004d1" (16778449)
kwin_xkbcommon: XKB: [XKB-489] ru:336:62: numeric keysym "0x10004d0" (16778448)
kwin_xkbcommon: XKB: [XKB-489] ru:337:49: numeric keysym "0x10004ab" (16778411)
kwin_xkbcommon: XKB: [XKB-489] ru:337:62: numeric keysym "0x10004aa" (16778410)
kwin_xkbcommon: XKB: [XKB-489] ru:353:21: numeric keysym "0x10004dd" (16778461)
kwin_xkbcommon: XKB: [XKB-489] ru:353:34: numeric keysym "0x10004dc" (16778460)
kwin_xkbcommon: XKB: [XKB-489] ru:354:21: numeric keysym "0x10004e7" (16778471)
kwin_xkbcommon: XKB: [XKB-489] ru:354:34: numeric keysym "0x10004e6" (16778470)
kwin_xkbcommon: XKB: [XKB-489] ru:355:21: numeric keysym "0x10004f5" (16778485)
kwin_xkbcommon: XKB: [XKB-489] ru:355:34: numeric keysym "0x10004f4" (16778484)
kwin_xkbcommon: XKB: [XKB-489] ru:356:21: numeric keysym "0x10004e5" (16778469)
kwin_xkbcommon: XKB: [XKB-489] ru:356:34: numeric keysym "0x10004e4" (16778468)
kwin_xkbcommon: XKB: [XKB-489] ru:357:21: numeric keysym "0x10004df" (16778463)
kwin_xkbcommon: XKB: [XKB-489] ru:357:34: numeric keysym "0x10004de" (16778462)
kwin_xkbcommon: XKB: [XKB-489] ru:494:32: numeric keysym "0x10004a1" (16778401)
kwin_xkbcommon: XKB: [XKB-489] ru:494:56: numeric keysym "0x10004a0" (16778400)
kwin_xkbcommon: XKB: [XKB-489] ru:496:32: numeric keysym "0x10004ab" (16778411)
kwin_xkbcommon: XKB: [XKB-489] ru:496:56: numeric keysym "0x10004aa" (16778410)
kwin_xkbcommon: XKB: [XKB-489] ru:498:32: numeric keysym "0x1000499" (16778393)
kwin_xkbcommon: XKB: [XKB-489] ru:498:56: numeric keysym "0x1000498" (16778392)
kwin_wayland_drm: Failed to create gamma blob! Недопустимый аргумент
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Could not resolve keysym XF86CameraAccessEnable
> Warning: Could not resolve keysym XF86CameraAccessDisable
> Warning: Could not resolve keysym XF86CameraAccessToggle
> Warning: Could not resolve keysym XF86NextElement
> Warning: Could not resolve keysym XF86PreviousElement
> Warning: Could not resolve keysym XF86AutopilotEngageToggle
> Warning: Could not resolve keysym XF86MarkWaypoint
> Warning: Could not resolve keysym XF86Sos
> Warning: Could not resolve keysym XF86NavChart
> Warning: Could not resolve keysym XF86FishingChart
> Warning: Could not resolve keysym XF86SingleRangeRadar
> Warning: Could not resolve keysym XF86DualRangeRadar
> Warning: Could not resolve keysym XF86RadarOverlay
> Warning: Could not resolve keysym XF86TraditionalSonar
> Warning: Could not resolve keysym XF86ClearvuSonar
> Warning: Could not resolve keysym XF86SidevuSonar
> Warning: Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported maximum keycode 708, clipping.
> X11 cannot support keycodes above 255.
> Warning: Could not resolve keysym XF86CameraAccessEnable
> Warning: Could not resolve keysym XF86CameraAccessDisable
> Warning: Could not resolve keysym XF86CameraAccessToggle
> Warning: Could not resolve keysym XF86NextElement
> Warning: Could not resolve keysym XF86PreviousElement
> Warning: Could not resolve keysym XF86AutopilotEngageToggle
> Warning: Could not resolve keysym XF86MarkWaypoint
> Warning: Could not resolve keysym XF86Sos
> Warning: Could not resolve keysym XF86NavChart
> Warning: Could not resolve keysym XF86FishingChart
> Warning: Could not resolve keysym XF86SingleRangeRadar
> Warning: Could not resolve keysym XF86DualRangeRadar
> Warning: Could not resolve keysym XF86RadarOverlay
> Warning: Could not resolve keysym XF86TraditionalSonar
> Warning: Could not resolve keysym XF86ClearvuSonar
> Warning: Could not resolve keysym XF86SidevuSonar
> Warning: Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
dbus-daemon[2687]: [session uid=1000 pid=2687] Activating service name='org.a11y.Bus' requested by ':1.23' (uid=1000 pid=2896 comm="/usr/lib64/firefox/firefox --sm-client-id 1014113e")
dbus-daemon[2687]: [session uid=1000 pid=2687] Successfully activated service 'org.a11y.Bus'
dbus-daemon[2687]: [session uid=1000 pid=2687] Activating service name='org.kde.krunner' requested by ':1.22' (uid=1000 pid=2959 comm="/usr/bin/kwin_wayland --wayland-fd 7 --socket wayl")
dbus-daemon[2687]: [session uid=1000 pid=2687] Successfully activated service 'org.kde.krunner'
dbus-daemon[2687]: [session uid=1000 pid=2687] Activating service name='org.kde.ActivityManager' requested by ':1.25' (uid=1000 pid=3155 comm="/usr/bin/krunner")
dbus-daemon[2687]: [session uid=1000 pid=2687] Successfully activated service 'org.kde.ActivityManager'
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
QCommandLineParser: argument list cannot be empty, it should contain at least the executable name
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeinit5: preparing to launch '/usr/lib64/libexec/kf5/klauncher'
kdeinit5: Launched KLauncher, pid = 3211, result = 0
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeinit5: opened connection to :1
Initializing "/usr/lib64/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Initializing "/usr/lib64/qt5/plugins/plasma/kcms/systemsettings/kcm_mouse.so"
Initializing "/usr/lib64/qt5/plugins/plasma/kcms/systemsettings/kcm_style.so"
org.kde.plasma.session: process job "kcminit_startup" finished with exit code 0
Installing the delayed initialization callback.
Qt: Session management error: networkIdsList argument is NULL
kdeinit5: Got SETENV 'SESSION_MANAGER=local/pan-homlin:@/tmp/.ICE-unix/3249,unix/pan-homlin:/tmp/.ICE-unix/3249' from launcher.
kdeinit5: Got SETENV 'SESSION_MANAGER=local/pan-homlin:@/tmp/.ICE-unix/3249,unix/pan-homlin:/tmp/.ICE-unix/3249' from launcher.
Initializing "/usr/lib64/qt5/plugins/plasma/kcms/systemsettings/kcm_kgamma.so"
Initializing "/usr/lib64/qt5/plugins/plasma/kcms/systemsettings/kcm_touchpad.so"
Xlib XKB extension major= 1 minor= 0
Known activities: ("5b779dec-38ea-4bce-a137-3f1a43e2ef38")
Delayed initialization.
Reloading the khotkeys configuration
Version 2 File!
Qt: Session management error: Could not open network socket
true
Imported file "/usr/share/khotkeys/defaults.khotkeys"
Imported file "/usr/share/khotkeys/kde32b1.khotkeys"
Imported file "/usr/share/khotkeys/konqueror_gestures_kde321.khotkeys"
org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
org.kde.powerdevil: org.kde.powerdevil.backlighthelper.brightness failed
KXMessages used on non-X11 platform! This is an application bug.
New PolkitAgentListener 0x55c192cc95d0
Adding new listener PolkitQt1::Agent::Listener(0x55c192cc7fc0) for 0x55c192cc95d0
Listener online
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Qt: Session management error: Could not open network socket
X server XKB extension major= 1 minor= 0
Authentication agent result: true
kscreen.kded: PowerDevil SuspendSession action not available!
Checking screens: available: (QScreen(0x560f2d30c940, name="HDMI-A-1")) redundant: QHash() fake: QSet() all: (QScreen(0x560f2d30c940, name="HDMI-A-1"))
Схема «org.gnome.desktop.a11y.applications» отсутствует
org.kde.powerdevil: Handle button events action could not check for screen configuration
org.kde.powerdevil: The profile "AC" tried to activate "DimDisplay" a non-existent action. This is usually due to an installation problem, a configuration problem, or because the action is not supported
org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
kf.plasma.quick: Applet preload policy set to 1
Initializing "/usr/lib64/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
OpenGL version string: 3.1.0 NVIDIA 535.129.03
OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 535.129.3
GPU class: Unknown
OpenGL version: 3.1
GLSL version: 1.40
X server version: 1.23.2
Linux kernel version: 6.1.57
Requires strict binding: no
GLSL shaders: yes
Texture NPOT support: yes
Virtual Machine: no
ZoomConfig::instance called after the first use - ignoring
WindowViewConfig::instance called after the first use - ignoring
SlidingPopupsConfig::instance called after the first use - ignoring
SlideConfig::instance called after the first use - ignoring
OverviewConfig::instance called after the first use - ignoring
KscreenConfig::instance called after the first use - ignoring
DesktopGridConfig::instance called after the first use - ignoring
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:265:13: QML SelectableLabel: Binding loop detected for property "implicitWidth"
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout
QObject::connect: No such slot DesktopProtocol::_k_slotRedirection(KIO::Job *, QUrl)
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
file:///home/pan/.local/share/plasma/plasmoids/org.kde.kargos/contents/ui/main.qml:208:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
QObject::connect: signal not found in OrgKdeActivityManagerResourcesLinkingInterface
QObject::connect: signal not found in OrgKdeActivityManagerResourcesLinkingInterface
QObject::connect: signal not found in OrgKdeActivityManagerResourcesLinkingInterface
QObject::connect: signal not found in OrgKdeActivityManagerResourcesLinkingInterface
Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion
QObject::connect: signal not found in OrgKdeActivityManagerResourcesLinkingInterface
QObject::connect: signal not found in OrgKdeActivityManagerResourcesLinkingInterface
QObject::connect: signal not found in OrgKdeActivityManagerResourcesLinkingInterface
QObject::connect: signal not found in OrgKdeActivityManagerResourcesLinkingInterface
QObject::connect: signal not found in OrgKdeActivityManagerResourcesLinkingInterface
QObject::connect: signal not found in OrgKdeActivityManagerResourcesLinkingInterface
file:///home/pan/.local/share/plasma/plasmoids/org.kde.kargos/contents/ui/FirstLinesRotator.qml:225:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout
Both point size and pixel size set. Using pixel size.
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/Tooltip.qml:78:9: QML GridLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth"
Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/ThumbnailStrip.qml"
Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationHeader.qml"
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/PulseAudio.qml:9:1: module "org.kde.plasma.private.volume" is not installed
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:18:1: QML MouseArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth"
org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout
Both point size and pixel size set. Using pixel size.
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
kf5idletime_wayland: This plugin does not support polling idle time
QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
QObject::connect: No such slot DesktopProtocol::_k_slotRedirection(KIO::Job *, QUrl)
QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
file:///home/pan/.local/share/plasma/plasmoids/org.kde.kargos/contents/ui/FullRepresentation.qml:168:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
[Parent 3327, Main Thread] WARNING: Failed to call GetIdletime(): GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.Mutter.IdleMonitor was not provided by any .service files
: 'glib warning', file /var/tmp/portage/www-client/firefox-120.0/work/firefox-120.0/toolkit/xre/nsSigHandlers.cpp:187
** (firefox:3327): WARNING **: 20:10:33.604: Failed to call GetIdletime(): GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.Mutter.IdleMonitor was not provided by any .service files
This plugin does not support raise()
This plugin does not support raise()
Error Opening file /usr/share/GeoIP/GeoIP.dat
This plugin does not support raise()
Registering ":1.45/StatusNotifierItem" to system tray
QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
This plugin does not support raise()
This plugin does not support raise()
This plugin does not support raise()
This plugin does not support raise()
This plugin does not support raise()
This plugin does not support raise()
This plugin does not support raise()
This plugin does not support raise()
This plugin does not support raise()
This plugin does not support raise()
This plugin does not support raise()
QString::arg: 2 argument(s) missing in org.kde.konsole
org.kde.konsole.profile: Could not load profile from "/home/pan/.kde4/share/apps/konsole/Shell.profile"
org.kde.konsole.profile: Profile "Оболочка командной строки" has an invalid parent "/home/pan/.kde4/share/apps/konsole/Shell.profile"
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/PipeWireThumbnail.qml:11:1: module "org.kde.pipewire" is not installed
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/PipeWireThumbnail.qml:11:1: module "org.kde.pipewire" is not installed
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/PipeWireThumbnail.qml:11:1: module "org.kde.pipewire" is not installed
This plugin does not support raise()
This plugin does not support raise()
This plugin does not support raise()
|
_________________
Excuse my bad English, I only study it. |
|
| Back to top |
|
|
Xharlie
n00b
Joined: 21 May 2017
Posts: 15
|
| Posted: Wed Oct 23, 2024 2:21 pm Post subject: Solved? |
|
|
Did you ever find a solution? I think I am running into the same problem.
I'm sure it has something to do with dbus. I'm using `greetd` and, if I log in to KDE Plasma under wayland, then logout, then log in to it directly with `startx`, then Plasma works fine. Otherwise, Plasma's shell appears and looks good but no applications will run.
Intriguingly, applications from the previous session *will* be restarted and they actually work. But nothing can be launched. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
