Arch Linux

poptrek

Member

Registered: 2022-07-11

Posts: 13

Missing Config file? KDE Wayland

I have the below two errors which are causing kaccess and the associated programs to fill the memory. Not sure what the error is but some googling suggests that I am missing an X11 config file. Yet I am running Wayland. I only installed the xorg-wayland package. Do I need to generate the X11 directory and config file? What would be the best option for this? Running Linux kernel did an Syu update yesterday

Jul 11 09:38:40 Desktop01 kaccess[1027]: qt.qpa.xcb: QXcbConnection: XCB error: 148 (Unknown), sequence: 64622, resource id: 0, major code: 140 (Unknown), minor code: 20
Jul 11 09:38:40 Desktop01 kaccess[1027]: qt.qpa.xcb: QXcbConnection: XCB error: 148 (Unknown), sequence: 64627, resource id: 8208, major code: 140 (Unknown), minor code: 20

I also have another error but I believe it is unrelated. This is causing the mentioned monitor to turn off and on when screen power saving feature is turned on. Every min or so. If anyone has ideas on how to fix this would be great. As right now I am just turning the monitor off manually. System AMD Radeon 6650 with this monitor on display port and the 2nd monitor on HDMI(The 2nd monitor works fine).

Jul 11 09:38:30 Desktop01 xdg-desktop-portal-kde[1463]: xdp-kde-wayland-integration: Adding output:
Jul 11 09:38:30 Desktop01 xdg-desktop-portal-kde[1463]: xdp-kde-wayland-integration:     manufacturer:  "Ancor Communications Inc"
Jul 11 09:38:30 Desktop01 xdg-desktop-portal-kde[1463]: xdp-kde-wayland-integration:     model:  "ASUS VS247/DALMTF003971"
Jul 11 09:38:30 Desktop01 xdg-desktop-portal-kde[1463]: xdp-kde-wayland-integration:     resolution:  QSize(1920, 1080)
Jul 11 09:38:30 Desktop01 plasmashell[37738]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:70:5: QML Connections: Detected function "onConfigurationChanged" in
 Connections element. This is probably intended to be a signal handler but no signal of the target matches the name.
Jul 11 09:38:30 Desktop01 plasmashell[37738]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:70:5: QML Connections: Detected function "onRepaintNeeded" in Connec
tions element. This is probably intended to be a signal handler but no signal of the target matches the name.
Jul 11 09:38:30 Desktop01 plasmashell[37738]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:67: TypeError: Cannot read property 'wallpaper' of null
Jul 11 09:38:30 Desktop01 plasmashell[37738]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:71: TypeError: Cannot read property 'wallpaper' of null
Jul 11 09:38:30 Desktop01 plasmashell[37738]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Jul 11 09:38:30 Desktop01 plasmashell[37738]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Jul 11 09:38:30 Desktop01 kscreenlocker_greet[4388]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Jul 11 09:38:30 Desktop01 kscreenlocker_greet[4388]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: Unable to assign [undefined] to bool
Jul 11 09:38:30 Desktop01 plasmashell[37738]: qt.gui.icc: fromIccProfile: failed minimal tag size sanity
Jul 11 09:38:30 Desktop01 kscreenlocker_greet[4388]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Jul 11 09:38:31 Desktop01 flatpak[1199]: [2022-07-11 09:38:31.835] [164] (device_info_linux.cc:45): NumberOfDevices
Jul 11 09:38:34 Desktop01 flatpak[1199]: [2022-07-11 09:38:34.838] [164] (device_info_linux.cc:45): NumberOfDevices
Jul 11 09:38:37 Desktop01 flatpak[1199]: [2022-07-11 09:38:37.838] [164] (device_info_linux.cc:45): NumberOfDevices
Jul 11 09:38:40 Desktop01 NetworkManager[450]: <info>  [1657546720.1490] dhcp4 (enp5s0): state changed new lease, address=192.168.50.168
Jul 11 09:38:40 Desktop01 xdg-desktop-portal-kde[1463]: xdp-kde-wayland-integration: Removing output:
Jul 11 09:38:40 Desktop01 xdg-desktop-portal-kde[1463]: xdp-kde-wayland-integration:     manufacturer:  "Ancor Communications Inc"
Jul 11 09:38:40 Desktop01 xdg-desktop-portal-kde[1463]: xdp-kde-wayland-integration:     model:  "ASUS VS247/DALMTF003971"
Jul 11 09:38:40 Desktop01 plasmashell[37738]: file:///usr/share/plasma/wallpapers/org.kde.potd/contents/ui/main.qml:45: TypeError: Cannot read property 'configuration' of null
Jul 11 09:38:40 Desktop01 plasmashell[37738]: file:///usr/share/plasma/wallpapers/org.kde.potd/contents/ui/main.qml:36: TypeError: Cannot read property 'configuration' of null
Jul 11 09:38:40 Desktop01 plasmashell[37738]: file:///usr/share/plasma/wallpapers/org.kde.potd/contents/ui/main.qml:20: TypeError: Cannot read property 'configuration' of null
Jul 11 09:38:40 Desktop01 plasmashell[37738]: file:///usr/share/plasma/wallpapers/org.kde.potd/contents/ui/main.qml:24: TypeError: Cannot read property 'configuration' of null
Jul 11 09:38:40 Desktop01 kwin_wayland[814]: QMetaProperty::read: Unable to handle unregistered datatype 'KWin::SessionState' for property 'KWin::EffectsHandlerImpl::sessionState'

logothete

Member

Registered: 2022-01-06

Posts: 44

Re: Missing Config file? KDE Wayland

Xorg-xwayland is basically what it says on the tin -- an xserver that wayland runs so that you can run non-wayland programs. That X11 config  directory/file (I assume you mean you have no /etc/X11) will auto-generate if you log in with an xorg session once.

poptrek

Member

Registered: 2022-07-11

Posts: 13

Re: Missing Config file? KDE Wayland

Yeah. I was looking more into. According to the KDE arch wiki I can suppress the debug message by not logging it. Not sure if that would stop the memory being filled up. I can't seem to find anything regarding the second issue. There was a bug 5 years ago about physically powering off the monitor then back would cause a crash. Yet I have something different where the computer is commanding the DP monitor off then back on. Unfortunately the only logs I have are in my initial post. I did a hard drive upgrade and I am give gnome a whirl. I would still like to know if anyone has any thoughts so if go back to KDE I might have some idea how to fix it. I will see if gnome has the same issue

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,267

Re: Missing Config file? KDE Wayland

That message is normal as soon as something on an X server/client closes a window and the async nature of Xorg may or may not relay that information to the client/Window manager in time. That is mostly a debug message that should have no relation to "memory filling up". What makes you surmise that? Which measurement are you reading? FWIW I have no such issues on KDE Wayland here

poptrek

Member

Registered: 2022-07-11

Posts: 13

Re: Missing Config file? KDE Wayland

I was using KDE's system monitor program plus the desktop widget. System monitor was stating Kaccess, Accessibility plus a few others were all consuming the same amount of ram and after two days they where each at 4 or so GiB with about 75% of 32GB of ram used up according to the desktop widget. I didn't think to check top or htop as I never had any doubt to system monitor.

On the weird monitor issue. it seems to be hardware came back to gnome with none of the monitors turned off.  I guess this removes that issue from this thread.