https://bugs.kde.org/show_bug.cgi?id=493145
kde.tinker...@passinbox.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kde.tinker...@passinbox.com
--- Comment #28 from kde.tinker...@passinbox.com ---
I can add some additional information to this to help possibly narrow down the
cause of the issue. My setup is a bit complicated and I have noticed this issue
on my Laptop (Machine A) but not my Desktop (Machine B) both running the same
OS and software versions. Both Machine A and B are plugged into the same lvl1
Techs KVM that connects to 2 1440p monitors and other devices. As I mentioned I
can login fine with my Desktop (Machine B) but the Laptop (Machine A)
experiences this issue until I unplug it from the dock. Once unplugged from my
laptop Dock I can login no problem.
Logs from when I attempted to login this morning
Oct 18 08:27:39 titan-laptop teams-for-linux[9663]: 08:27:39.110 ›
GetSystemIdleState => IdleTimeout: 300s, IdleTimeoutPollInterval: 10s,
ActiveCheckPollInterval: 2s, IdleTime: 0s, IdleState: 'locked'
Oct 18 08:27:41 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128:
TypeError: Property 'startAuthenticating' of object Friday, October 18, 2024 is
not a function
Oct 18 08:27:43 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280:
TypeError: Property 'respond' of object Friday, October 18, 2024 is not a
function
Oct 18 08:27:44 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128:
TypeError: Property 'startAuthenticating' of object Friday, October 18, 2024 is
not a function
Oct 18 08:27:47 titan-laptop systemd[1]:
dbus-:1.4-org.kde.powerdevil.backlighthelper@2.service: Deactivated
successfully.
Oct 18 08:27:49 titan-laptop teams-for-linux[9663]: 08:27:49.112 ›
GetSystemIdleState => IdleTimeout: 300s, IdleTimeoutPollInterval: 10s,
ActiveCheckPollInterval: 2s, IdleTime: 0s, IdleState: 'locked'
Oct 18 08:27:49 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280:
TypeError: Property 'respond' of object Friday, October 18, 2024 is not a
function
Oct 18 08:27:52 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280:
TypeError: Property 'respond' of object Friday, October 18, 2024 is not a
function
Oct 18 08:27:54 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128:
TypeError: Property 'startAuthenticating' of object Friday, October 18, 2024 is
not a function
Oct 18 08:27:55 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128:
TypeError: Property 'startAuthenticating' of object Friday, October 18, 2024 is
not a function
Oct 18 08:27:59 titan-laptop teams-for-linux[9663]: 08:27:59.114 ›
GetSystemIdleState => IdleTimeout: 300s, IdleTimeoutPollInterval: 10s,
ActiveCheckPollInterval: 2s, IdleTime: 0s, IdleState: 'locked'
Oct 18 08:27:59 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280:
TypeError: Property 'respond' of object ⢀?瘂
Oct 18 08:28:02 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280:
TypeError: Property 'respond' of object ⢀?瘂
Oct 18 08:28:02 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280:
TypeError: Property 'respond' of object ⢀?瘂
Oct 18 08:28:02 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280:
TypeError: Property 'respond' of object ⢀?瘂
Oct 18 08:28:02 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280:
TypeError: Property 'respond' of object ⢀?瘂
Oct 18 08:28:02 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280:
TypeError: Property 'respond' of object ⢀?瘂
Oct 18 08:28:03 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280:
TypeError: Property 'respond' of object ⢀?瘂
Oct 18 08:28:03 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280:
TypeError: Property 'respond' of object ⢀?瘂
Oct 18 08:28:03 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280:
TypeError: Property 'respond' of object ⢀?瘂
Oct 18 08:28:03 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280:
TypeError: Property 'respond' of object ⢀?瘂
Oct 18 08:28:03 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280:
TypeError: Property 'respond' of object ⢀?瘂
Oct 18 08:28:03 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280:
TypeError: Property 'respond' of object ⢀?瘂
Oct 18 08:28:03 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280:
TypeError: Property 'respond' of object ⢀?瘂
Oct 18 08:28:04 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280:
TypeError: Property 'respond' of object ⢀?瘂
Oct 18 08:28:09 titan-laptop teams-for-linux[9663]: 08:28:09.116 ›
GetSystemIdleState => IdleTimeout: 300s, IdleTimeoutPollInterval: 10s,
ActiveCheckPollInterval: 2s, IdleTime: 0s, IdleState: 'locked'
Oct 18 08:28:11 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280:
TypeError: Property 'respond' of object ⢀?瘂
Oct 18 08:28:15 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128:
TypeError: Property 'startAuthenticating' of object ⢀?瘂
Oct 18 08:28:16 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128:
TypeError: Property 'startAuthenticating' of object ⢀?瘂
Oct 18 08:28:17 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128:
TypeError: Property 'startAuthenticating' of object ⢀?瘂
Oct 18 08:28:19 titan-laptop teams-for-linux[9663]: 08:28:19.118 ›
GetSystemIdleState => IdleTimeout: 300s, IdleTimeoutPollInterval: 10s,
ActiveCheckPollInterval: 2s, IdleTime: 0s, IdleState: 'locked'
Oct 18 08:28:19 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128:
TypeError: Property 'startAuthenticating' of object ⢀?瘂
Oct 18 08:28:21 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128:
TypeError: Property 'startAuthenticating' of object
1,0,0,0,0,1,0,0,0,0,1,0,0,0,0,1 is not a function
Oct 18 08:28:25 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128:
TypeError: Property 'startAuthenticating' of object
1,0,0,0,0,1,0,0,0,0,1,0,0,0,0,1 is not a function
Oct 18 08:28:26 titan-laptop kscreenlocker_greet[70170]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128:
TypeError: Property 'startAuthenticating' of object
1,0,0,0,0,1,0,0,0,0,1,0,0,0,0,1 is not a function
```
However looking at the journalCTL logs from before the login attempt\ and I am
getting some additional errors. I have a error from the Kernel relating to
Intel graphics drivers and possibly DRM.
Oct 18 08:28:47 titan-laptop kernel: i915 0000:00:02.0: [drm] *ERROR*
[CRTC:100:pipe A] mismatch in infoframes.enable (expected 0x00000000, found
0x00000004)
Oct 18 08:28:47 titan-laptop kernel: ------------[ cut here ]------------
Oct 18 08:28:47 titan-laptop kernel: i915 0000:00:02.0: [drm] pipe state
doesn't match!
Oct 18 08:28:47 titan-laptop kernel: WARNING: CPU: 14 PID: 2609 at
drivers/gpu/drm/i915/display/intel_modeset_verify.c:223
intel_modeset_verify_crtc+0x4ae/0x550 [i915]
Oct 18 08:28:47 titan-laptop kernel: Modules linked in: vhost_net vhost
vhost_iotlb tap tun udp_diag tcp_diag inet_diag cmac nls_utf8 cifs rdma_cm
iw_cm ib_cm ib_core nls_ucs2_utils>
Oct 18 08:28:47 titan-laptop kernel: snd_hda_codec_generic snd_soc_hda_codec
snd_hda_ext_core snd_soc_core iwlmvm ac97_bus snd_pcm_dmaengine snd_compress
snd_hda_intel uvcvideo x86>
Oct 18 08:28:47 titan-laptop kernel: firmware_attributes_class
dell_wmi_descriptor wmi_bmof processor_thermal_wt_req snd mtd typec_ucsi
intel_skl_int3472_tps68470 i2c_mux cfg80211 >
Oct 18 08:28:47 titan-laptop kernel: rtsx_pci_sdmmc sha512_ssse3 sha256_ssse3
mmc_core drm_buddy sha1_ssse3 intel_gtt aesni_intel serio_raw nvme gf128mul
i2c_algo_bit atkbd crypto_>
Oct 18 08:28:47 titan-laptop kernel: CPU: 14 UID: 1000 PID: 2609 Comm:
kwin_wayland Tainted: G W OE 6.11.3-3-cachyos #1
1400000003000000474e5500e91c5d6a11fba825
Oct 18 08:28:47 titan-laptop kernel: Tainted: [W]=WARN, [O]=OOT_MODULE,
[E]=UNSIGNED_MODULE
Oct 18 08:28:47 titan-laptop kernel: Hardware name: Dell Inc. XPS 15
9510/0C6CP1, BIOS 1.31.0 07/12/2024
Oct 18 08:28:47 titan-laptop kernel: RIP:
0010:intel_modeset_verify_crtc+0x4ae/0x550 [i915]
Oct 18 08:28:47 titan-laptop kernel: Code: ff ff 48 8b 7b 08 e8 61 21 9b d2 48
8b 4b 08 48 8b 51 50 48 85 d2 75 03 48 8b 11 48 c7 c7 50 a2 ca c1 48 89 c6 e8
d2 48 03 d2 <0f> 0b e9 b>
Oct 18 08:28:47 titan-laptop kernel: RSP: 0018:ffffa7780fc27978 EFLAGS:
00010246
Oct 18 08:28:47 titan-laptop kernel: RAX: b128c257e0dc4d00 RBX:
ffff898acfb54000 RCX: 0000000000000027
Oct 18 08:28:47 titan-laptop kernel: RDX: 00000000ffffefff RSI:
0000000000000002 RDI: ffff899a0f721a48
Oct 18 08:28:47 titan-laptop kernel: RBP: ffff898acfb64e00 R08:
0000000000000fff R09: ffffffff95a59e90
Oct 18 08:28:47 titan-laptop kernel: R10: 0000000000002ffd R11:
0000000000000004 R12: ffff898e959a6000
Oct 18 08:28:47 titan-laptop kernel: R13: ffff898e959a0000 R14:
ffff898e959a6000 R15: ffff898afe359800
Oct 18 08:28:47 titan-laptop kernel: FS: 000073e2f69a0f80(0000)
GS:ffff899a0f700000(0000) knlGS:0000000000000000
Oct 18 08:28:47 titan-laptop kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Oct 18 08:28:47 titan-laptop kernel: CR2: 0000736bdc4b31c0 CR3:
0000000152724002 CR4: 0000000000f72ef0
Oct 18 08:28:47 titan-laptop kernel: PKRU: 55555554
Oct 18 08:28:47 titan-laptop kernel: Call Trace:
Oct 18 08:28:47 titan-laptop kernel: <TASK>
Oct 18 08:28:47 titan-laptop kernel: ? __warn+0xd0/0x1c0
Oct 18 08:28:47 titan-laptop kernel: ? intel_modeset_verify_crtc+0x4ae/0x550
[i915 1400000003000000474e550067e9e103415ab20f]
Oct 18 08:28:47 titan-laptop kernel: ? report_bug+0x144/0x1f0
Oct 18 08:28:47 titan-laptop kernel: ? handle_bug+0x42/0x70
Oct 18 08:28:47 titan-laptop kernel: ? exc_invalid_op+0x1a/0x50
Oct 18 08:28:47 titan-laptop kernel: ? asm_exc_invalid_op+0x1a/0x20
Oct 18 08:28:47 titan-laptop kernel: ? intel_modeset_verify_crtc+0x4ae/0x550
[i915 1400000003000000474e550067e9e103415ab20f]
Oct 18 08:28:47 titan-laptop kernel: ? intel_modeset_verify_crtc+0x4ae/0x550
[i915 1400000003000000474e550067e9e103415ab20f]
Oct 18 08:28:47 titan-laptop kernel: intel_atomic_commit_tail+0xaf2/0x12d0
[i915 1400000003000000474e550067e9e103415ab20f]
Oct 18 08:28:47 titan-laptop kernel: ? __flush_workqueue+0x4c9/0x550
Oct 18 08:28:47 titan-laptop kernel: intel_atomic_commit+0x2e7/0x320 [i915
1400000003000000474e550067e9e103415ab20f]
Oct 18 08:28:47 titan-laptop kernel: drm_atomic_commit+0xc0/0xf0
Oct 18 08:28:47 titan-laptop kernel: ? __pfx___drm_printfn_info+0x10/0x10
Oct 18 08:28:47 titan-laptop kernel: drm_mode_atomic_ioctl+0x621/0xc50
Oct 18 08:28:47 titan-laptop kernel: ? __pfx_drm_mode_atomic_ioctl+0x10/0x10
Oct 18 08:28:47 titan-laptop kernel: drm_ioctl_kernel+0xbf/0x100
Oct 18 08:28:47 titan-laptop kernel: drm_ioctl+0x355/0x4d0
Oct 18 08:28:47 titan-laptop kernel: ? __pfx_drm_mode_atomic_ioctl+0x10/0x10
Oct 18 08:28:47 titan-laptop kernel: ? syscall_exit_to_user_mode+0x97/0xc0
Oct 18 08:28:47 titan-laptop kernel: __x64_sys_ioctl+0x73/0xc0
Oct 18 08:28:47 titan-laptop kernel: do_syscall_64+0x88/0x170
Oct 18 08:28:47 titan-laptop kernel: ? __x64_sys_ioctl+0x97/0xc0
Oct 18 08:28:47 titan-laptop kernel: ? syscall_exit_to_user_mode+0x97/0xc0
Oct 18 08:28:47 titan-laptop kernel: ? do_syscall_64+0x94/0x170
Oct 18 08:28:47 titan-laptop kernel: ? clear_bhb_loop+0x25/0x80
Oct 18 08:28:47 titan-laptop kernel: ? clear_bhb_loop+0x25/0x80
Oct 18 08:28:47 titan-laptop kernel: ? clear_bhb_loop+0x25/0x80
Oct 18 08:28:47 titan-laptop kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e
Oct 18 08:28:47 titan-laptop kernel: RIP: 0033:0x73e30732b24f
Oct 18 08:28:47 titan-laptop kernel: Code: 00 48 89 44 24 18 31 c0 c7 04 24 10
00 00 00 48 8d 44 24 60 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00
00 00 0f 05 <89> c2 3d 0>
Oct 18 08:28:47 titan-laptop kernel: RSP: 002b:00007ffcf7301fd0 EFLAGS:
00000246 ORIG_RAX: 0000000000000010
Oct 18 08:28:47 titan-laptop kernel: RAX: ffffffffffffffda RBX:
00005fff9efa41a0 RCX: 000073e30732b24f
Oct 18 08:28:47 titan-laptop kernel: RDX: 00007ffcf73020c0 RSI:
00000000c03864bc RDI: 0000000000000017
Oct 18 08:28:47 titan-laptop kernel: RBP: 00007ffcf73020c0 R08:
000073e2a002c9cc R09: 000073e2a002c9cc
Oct 18 08:28:47 titan-laptop kernel: R10: 000073e2a002c770 R11:
0000000000000246 R12: 00000000c03864bc
Oct 18 08:28:47 titan-laptop kernel: R13: 0000000000000017 R14:
00005fff991cf020 R15: 000000000000002d
Oct 18 08:28:47 titan-laptop kernel: </TASK>
Oct 18 08:28:47 titan-laptop kernel: ---[ end trace 0000000000000000 ]---
And additionally Joplin had a core-dump just a moment earlier than this driver
issue. It is strange that this issue is happening with KDE but only on my Intel
machine with a Dock. Hopefully these details help
--
You are receiving this mail because:
You are watching all bug changes.
