Same on KDE/X11 
2 Likes
Gnome GDM is borked, switched to lightdm, enlightenment…
Please create a Support thread with more details if gdm 41.0+r15+g23ebe617-1 did not help.
EDIT: I’d you have an NVIDIA GPU and are using linux515 5.15.2-1, boot 5.14 for now until 5.15.2-2 is released to the testing branch.
EDIT: 5.15.2-2 is live.
I don’t usually report when everything is working (I just click the proper poll option in first post), but yeah, KDE with Nvidia (video-nvidia) and kernel 5.15 on Xorg, absolutely no issue. As people say it is broken I confirm it is not, issue is specific to their system so maybe they should share more relevant info.
3 Likes
We pushed some more packages to this one …
User philip created a snapshot of branch 'unstable' to 'testing'.
- testing community x86_64: 6 new and 7 removed package(s)
- testing core x86_64: 3 new and 3 removed package(s)
- testing extra x86_64: 13 new and 13 removed package(s)
:: Different overlay package(s) in repository community x86_64
-------------------------------------------------------------------------------
PACKAGE 2021-11-13 2021-11-14
-------------------------------------------------------------------------------
cinnamon 5.0.7-1 5.0.7-2
:: Different sync package(s) in repository community x86_64
-------------------------------------------------------------------------------
PACKAGE 2021-11-13 2021-11-14
-------------------------------------------------------------------------------
cinnamon-desktop 5.0.0-1 5.0.0-2
jami-daemon 20211004-4 20211104-1
jami-gnome 20211004-1 20211101-1
jami-qt 20211004-2 20211104-1
libjamiclient 20211004-1 20211104-1
mkinitcpio-systemd-tool 36-1 37-1
:: Different overlay package(s) in repository core x86_64
-------------------------------------------------------------------------------
PACKAGE 2021-11-13 2021-11-14
-------------------------------------------------------------------------------
linux515 5.15.2-1 5.15.2-2
linux515-headers 5.15.2-1 5.15.2-2
:: Different sync package(s) in repository core x86_64
-------------------------------------------------------------------------------
PACKAGE 2021-11-13 2021-11-14
-------------------------------------------------------------------------------
dialog 1:1.3_20210621-1 1:1.3_20211107-1
:: Different overlay package(s) in repository extra x86_64
-------------------------------------------------------------------------------
PACKAGE 2021-11-13 2021-11-14
-------------------------------------------------------------------------------
linux515-acpi_call 1.1.0-5 1.1.0-6
linux515-bbswitch 0.8-5 0.8-6
linux515-broadcom-wl 6.30.223.271-5 6.30.223.271-6
linux515-nvidia-390xx 390.144-5 390.144-6
linux515-nvidia-470xx 470.86-2 470.86-3
linux515-nvidia 495.44-6 495.44-7
linux515-r8168 8.049.02-5 8.049.02-6
linux515-rtl8723bu 20210806-4 20211104-1
linux515-tp_smapi 0.43-5 0.43-6
linux515-vhba-module 20211023-5 20211023-6
linux515-virtualbox-host-modules 6.1.28-5 6.1.28-6
linux515-zfs 2.1.1-5 2.1.1-6
:: Different sync package(s) in repository extra x86_64
-------------------------------------------------------------------------------
PACKAGE 2021-11-13 2021-11-14
-------------------------------------------------------------------------------
gnome-screenshot 40.0-2 41.0-1
3 Likes
Installed the latest patches and everything worked fine with 5.15.2-2. Thanks!
that fixed it, thanks
version kernel 5.15.2-1 is ok
I use KDE and decided for “no”, so far I have not seen any issues.
1 Like
The latest updates added to this update have fixed the problem of not being able to enter a wayland session with KDE but there are further issues. Plasma is VERY laggy - I’m talking up to 1 minute of delay from clicking the Application Launcher icon to seeing the Application Launcher on screen. I’m running Linux 5.15 with Nvidia 495.
3 Likes
Bluetooth still doesn’t work with kernel 5.15. Maybe this helps:
$ journalctl -p 3 -xb
-- Journal begins at Sat 2021-03-27 23:05:36 CET, ends at Sun 2021-11-14 11:19:47 CET. --
Nov 14 11:16:12 ostfriesland kernel: Bluetooth: hci0: command 0xfc05 tx timeout
Nov 14 11:16:12 ostfriesland kernel: Bluetooth: hci0: Reading Intel version command failed (-110)
Nov 14 11:18:00 ostfriesland gdm-password][873]: gkr-pam: unable to locate daemon control file
Nov 14 11:18:27 ostfriesland gdm-launch-environment][555]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Edit: When running Kernel 5.14 only the last two lines apear
Changing orientation (90degrees, 180 degrees, etc) of screen results in freeze of kde dm … ctrl+alt+fx to refresh output - but still not able to interact.
running through kvm, so might be a virtualization issue? virtio gpu
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xrandr: XRandR::setConfig
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xrandr: Requested screen size is QSize(1080, 1920)
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xrandr: Needed CRTCs: 1
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xrandr: Actions to perform:
Primary Output: false
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xrandr: Change Screen Size: true
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xrandr: Old: QSize(1920, 1080)
Intermediate: QSize(1920, 1920)
New: QSize(1080, 1920)
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xrandr: Disable outputs: false
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xrandr: Change outputs: true
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xrandr: (63)
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xrandr: Enable outputs: false
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xrandr: RRSetScreenSize
DPI: 96.0946
Size: QSize(1920, 1920)
SizeMM: QSize(507, 507)
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xrandr: RRSetCrtcConfig (change output)
Output: 63 ( "Virtual-1" )
CRTC: 62
Pos: QPoint(0,0)
Mode: 76 KScreen::Mode(Id: "76" , Size: QSize(1920, 1080) @ 50 )
Rotation: KScreen::Output::Left
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xrandr: Result: 0
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xrandr: XRandROutput 63 update
m_connected: 0
m_crtc XRandRCrtc(0x560e31929500)
CRTC: 62
MODE: 76
Connection: 0
Primary: true
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xrandr: RRSetScreenSize
DPI: 96.0946
Size: QSize(1080, 1920)
SizeMM: QSize(285, 507)
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xrandr: XRandR::setConfig done!
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: RRScreenChangeNotify
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: Window: 41943045
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: Root: 1321
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: Rotation: "Rotate_0"
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: Size ID: 65535
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: Size: 1920 1920
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: SizeMM: 507 507
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: RRNotify_CrtcChange
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: CRTC: 62
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: Mode: 76
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: Rotation: "Rotate_90"
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: Geometry: 0 0 1920 1080
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: RRScreenChangeNotify
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: Window: 41943045
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: Root: 1321
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: Rotation: "Rotate_90"
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: Size ID: 65535
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: Size: 1920 1920
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: SizeMM: 507 507
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: RRNotify_CrtcChange
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: CRTC: 62
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: Mode: 76
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: Rotation: "Rotate_90"
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: Geometry: 0 0 1920 1080
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: RRScreenChangeNotify
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: Window: 41943045
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: Root: 1321
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: Rotation: "Rotate_90"
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: Size ID: 65535
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: Size: 1920 1080
nov. 14 11:19:23 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xcb.helper: SizeMM: 507 285
nov. 14 11:19:23 manjaro-testbranch spice-vdagent[824]: display: failed to call GetCurrentState from mutter over DBUS
nov. 14 11:19:23 manjaro-testbranch spice-vdagent[824]: error message: Cannot invoke method; proxy is for the well-known name org.gnome.Mutter.DisplayConfig without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
nov. 14 11:19:23 manjaro-testbranch spice-vdagent[824]: display: failed to call GetCurrentState from mutter over DBUS
nov. 14 11:19:23 manjaro-testbranch spice-vdagent[824]: error message: Cannot invoke method; proxy is for the well-known name org.gnome.Mutter.DisplayConfig without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
nov. 14 11:19:23 manjaro-testbranch spice-vdagent[824]: display: failed to call GetCurrentState from mutter over DBUS
nov. 14 11:19:23 manjaro-testbranch spice-vdagent[824]: error message: Cannot invoke method; proxy is for the well-known name org.gnome.Mutter.DisplayConfig without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
nov. 14 11:19:23 manjaro-testbranch spice-vdagent[824]: display: failed to call GetCurrentState from mutter over DBUS
nov. 14 11:19:23 manjaro-testbranch spice-vdagent[824]: error message: Cannot invoke method; proxy is for the well-known name org.gnome.Mutter.DisplayConfig without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
nov. 14 11:19:23 manjaro-testbranch plasmashell[713]: trying to show an empty dialog
nov. 14 11:19:23 manjaro-testbranch kernel: input: spice vdagent tablet as /devices/virtual/input/input7
nov. 14 11:19:23 manjaro-testbranch systemsettings5[1110]: kf.coreaddons: KPluginFactory could not load the plugin "/usr/lib/qt/plugins/kcms/kcm_kscreen.so"
nov. 14 11:19:23 manjaro-testbranch kernel: input: spice vdagent tablet as /devices/virtual/input/input8
nov. 14 11:19:24 manjaro-testbranch kernel: input: spice vdagent tablet as /devices/virtual/input/input9
nov. 14 11:19:24 manjaro-testbranch kscreen_backend_launcher[803]: kscreen.xrandr: Emitting configChanged()
nov. 14 11:19:24 manjaro-testbranch kcminit[1173]: Initializing "kcm_mouse" : "kcminit_mouse"
nov. 14 11:19:24 manjaro-testbranch kwin_x11[662]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 25555, resource id: 77594629, major code: 18 (ChangeProperty), minor code: 0
nov. 14 11:19:35 manjaro-testbranch spice-vdagentd[913]: Error getting active session: No data available
nov. 14 11:19:35 manjaro-testbranch spice-vdagentd[913]: Error getting active session: No data available
nov. 14 11:19:35 manjaro-testbranch spice-vdagentd[913]: closed vdagent virtio channel
nov. 14 11:19:40 manjaro-testbranch systemd[1]: Started Getty on tty2.
nov. 14 11:19:40 manjaro-testbranch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
nov. 14 11:19:40 manjaro-testbranch kernel: audit: type=1130 audit(1636885180.719:75): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
nov. 14 11:19:43 manjaro-testbranch spice-vdagentd[913]: opening vdagent virtio channel
nov. 14 11:19:43 manjaro-testbranch kernel: input: spice vdagent tablet as /devices/virtual/input/input10
nov. 14 11:19:43 manjaro-testbranch spice-vdagentd[913]: Set max clipboard: 104857600
nov. 14 11:19:43 manjaro-testbranch spice-vdagentd[913]: Set max clipboard: 104857600
nov. 14 11:19:43 manjaro-testbranch spice-vdagent[824]: Received Graphics Device Info:
nov. 14 11:19:43 manjaro-testbranch spice-vdagent[824]: Device /dev/dri/card0 is at /sys/devices/pci0000:00/0000:00:01.0/virtio0/drm/card0
nov. 14 11:19:43 manjaro-testbranch spice-vdagent[824]: Found card '/sys/devices/pci0000:00/0000:00:01.0/virtio0/drm/card0' with Vendor ID 0x10, Device ID 0x1af4
nov. 14 11:19:43 manjaro-testbranch spice-vdagent[824]: Mapping connector Virtual-1 to display #0
nov. 14 11:19:43 manjaro-testbranch spice-vdagent[824]: Device /dev/dri/card0 is at /sys/devices/pci0000:00/0000:00:01.0/virtio0/drm/card0
nov. 14 11:19:43 manjaro-testbranch spice-vdagent[824]: Found card '/sys/devices/pci0000:00/0000:00:01.0/virtio0/drm/card0' with Vendor ID 0x10, Device ID 0x1af4
nov. 14 11:19:43 manjaro-testbranch spice-vdagent[824]: Found matching X Output: name=Virtual-1 id=63
nov. 14 11:19:43 manjaro-testbranch spice-vdagent[824]: Adding graphics device info: channel_id: 0 monitor_id: 0 device_address: pci/0000/01.0, device_display_id: 0 xrandr output ID: 63
nov. 14 11:19:43 manjaro-testbranch spice-vdagent[824]: display: failed to call GetCurrentState from mutter over DBUS
nov. 14 11:19:43 manjaro-testbranch spice-vdagent[824]: error message: Cannot invoke method; proxy is for the well-known name org.gnome.Mutter.DisplayConfig without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
Frameworks got updated at Arch. We might pull that also to see if it helps…
libkmod: kmod_config_parse: /etc/modprobe.d/tuxedo_io.conf line 1: ignoring bad line starting with 'tuxedo_io'
libkmod: kmod_config_parse: /etc/modprobe.d/tuxedo_io.conf line 2: ignoring bad line starting with 'tuxedo_keyboard'
Got these on image builds. Seems to be a new file, and these are the only 2 lines. Seems harmless.
Can other Tuxedo users confirm?
Is there a way to go back to xdg-desktop-portal-gtk then?
I had kernels 5.14.18-1 and 5.15.2-2, now I using the 5.14 to avoid the blank screen.
I use Gnome
Edit: Fixed Thank you
Okay, I did the following:
1)
sudo pacman -R xdg-desktop-portal-gnome
sudo pacman -S xdg-desktop-portal-gtk
Then I reinstall the kernel 5.15-2-2
reboot and fixed.
No blank screen, everything looks fine.
Now I’m back using 5.14.18-1 and 5.15.2-2 where 5.15.2-2 is running
What is the difference between xdg-desktop-portal-gtk and extra/xdg-desktop-portal-gnome ?
Thanks to y’all for your help
1 Like
Now reinstall xdg-desktop-portal-gnome since you’re using GNOME. It depends on xdg-desktop-portal-gtk >=1.10.0-2 anyway, so you’ll still have that installed. Read the descriptions and look at the dependencies if you want to know the difference.
1 Like
Should be fixed with tuxedo-keyboard 3.0.9-4.
1 Like
@omano maybe you do not use nvidia_drm.modeset=1, or you do use it but you installed the latest package from yesterday.
I use modeset, and I had to remove it to make it work before the last package. Now I installed it, and set DRM back, and everything is working again as expected.
For me, this specific issue is fixed…