API tools faq
paste
suedunham

Plasma screen lock reawakening log

suedunham
Jun 25th, 2026
28
0
Never
3
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 16.87 KB | Software | 0 0
raw download clone embed print report
  1. Jun 25 10:48:21 kase kernel: Freezing user space processes
  2. Jun 25 10:48:21 kase kernel: Freezing user space processes completed (elapsed 0.002 seconds)
  3. Jun 25 10:48:21 kase kernel: OOM killer disabled.
  4. Jun 25 10:48:21 kase kernel: Freezing remaining freezable tasks
  5. Jun 25 10:48:21 kase kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
  6. Jun 25 10:48:21 kase kernel: printk: Suspending console(s) (use no_console_suspend to debug)
  7. Jun 25 10:48:21 kase kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
  8. Jun 25 10:48:21 kase kernel: ACPI: EC: interrupt blocked
  9. Jun 25 10:48:21 kase kernel: ACPI: EC: interrupt unblocked
  10. Jun 25 10:48:21 kase kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.49.4
  11. Jun 25 10:48:21 kase kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
  12. Jun 25 10:48:21 kase kernel: i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads
  13. Jun 25 10:48:21 kase kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
  14. Jun 25 10:48:21 kase kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
  15. Jun 25 10:48:21 kase kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled
  16. Jun 25 10:48:21 kase kernel: nvme nvme0: 12/0/0 default/read/poll queues
  17. Jun 25 10:48:21 kase kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
  18. Jun 25 10:48:21 kase kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
  19. Jun 25 10:48:21 kase kernel: OOM killer enabled.
  20. Jun 25 10:48:21 kase kernel: Restarting tasks: Starting
  21. Jun 25 10:48:21 kase kernel: Restarting tasks: Done
  22. Jun 25 10:48:21 kase kernel: efivarfs: resyncing variable state
  23. Jun 25 10:48:21 kase kernel: efivarfs: finished resyncing variable state
  24. Jun 25 10:48:21 kase kernel: random: crng reseeded on system resumption
  25. Jun 25 10:48:21 kase systemd-sleep[39724]: System returned from sleep operation 'suspend'.
  26. Jun 25 10:48:21 kase kernel: PM: suspend exit
  27. Jun 25 10:48:21 kase kernel: tlp: vm.laptop_mode is deprecated. Ignoring setting.
  28. Jun 25 10:48:21 kase systemd[1]: user.slice: Unit now thawed.
  29. Jun 25 10:48:21 kase systemd[1]: user-1000.slice: Unit now thawed.
  30. Jun 25 10:48:21 kase systemd[1]: [email protected]: Unit now thawed.
  31. Jun 25 10:48:21 kase systemd-sleep[39724]: Successfully thawed unit 'user.slice'.
  32. Jun 25 10:48:21 kase systemd[1]: session-2.scope: Unit now thawed.
  33. Jun 25 10:48:21 kase systemd[1]: systemd-suspend.service: Deactivated successfully.
  34. Jun 25 10:48:21 kase systemd[1]: Finished System Suspend.
  35. Jun 25 10:48:21 kase systemd[1]: Stopped target Sleep.
  36. Jun 25 10:48:21 kase systemd[1]: Reached target Suspend.
  37. Jun 25 10:48:21 kase systemd-logind[1175]: Operation 'suspend' finished.
  38. Jun 25 10:48:21 kase systemd[1]: Stopped target Suspend.
  39. Jun 25 10:48:21 kase org_kde_powerdevil[1874]: [ 2016][84029.885605] (ldbus_handle_message)Received dbus signal PrepareForSleep(false=resume)
  40. Jun 25 10:48:21 kase NetworkManager[1173]: <info> [1782398901.9091] manager: sleep: wake requested (sleeping: yes enabled: yes)
  41. Jun 25 10:48:21 kase NetworkManager[1173]: <info> [1782398901.9092] device (wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
  42. Jun 25 10:48:21 kase rtkit-daemon[1514]: Resuming known real-time threads.
  43. Jun 25 10:48:21 kase rtkit-daemon[1514]: Successfully made thread 2718 of process 2549 owned by '1000' RT at priority 10.
  44. Jun 25 10:48:21 kase rtkit-daemon[1514]: Successfully made thread 1973 of process 1964 owned by '1000' RT at priority 20.
  45. Jun 25 10:48:21 kase rtkit-daemon[1514]: Successfully made thread 1964 of process 1964 owned by '1000' high priority at nice level -11.
  46. Jun 25 10:48:21 kase rtkit-daemon[1514]: Successfully made thread 1767 of process 1760 owned by '1000' RT at priority 20.
  47. Jun 25 10:48:21 kase rtkit-daemon[1514]: Successfully made thread 1760 of process 1760 owned by '1000' high priority at nice level -11.
  48. Jun 25 10:48:21 kase rtkit-daemon[1514]: Successfully made thread 1765 of process 1762 owned by '1000' RT at priority 20.
  49. Jun 25 10:48:21 kase rtkit-daemon[1514]: Resumed scheduling 6 threads.
  50. Jun 25 10:48:21 kase NetworkManager[1173]: <info> [1782398901.9345] device (wlp0s20f3): set-hw-addr: set MAC address to C6:F3:6D:CF:FB:5D (scanning)
  51. Jun 25 10:48:21 kase systemd[1]: Started dbus-:[email protected].
  52. Jun 25 10:48:22 kase kscreenlocker_greet[39597]: pam_unix(kde:auth): unexpected response from failed conversation function
  53. Jun 25 10:48:22 kase kscreenlocker_greet[39597]: pam_unix(kde:auth): conversation failed
  54. Jun 25 10:48:22 kase kscreenlocker_greet[39597]: pam_unix(kde:auth): auth could not identify password for [edj]
  55. Jun 25 10:48:22 kase kernel: iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
  56. Jun 25 10:48:22 kase kernel: iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
  57. Jun 25 10:48:22 kase kernel: iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
  58. Jun 25 10:48:22 kase kernel: iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
  59. Jun 25 10:48:22 kase kernel: iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
  60. Jun 25 10:48:22 kase NetworkManager[1173]: <info> [1782398902.1315] device (p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
  61. Jun 25 10:48:22 kase NetworkManager[1173]: <warn> [1782398902.1316] device (p2p-dev-wlp0s20f3): error setting IPv4 forwarding to '1': Resource temporarily unavailable
  62. Jun 25 10:48:22 kase NetworkManager[1173]: <info> [1782398902.1320] manager: NetworkManager state is now CONNECTED_LOCAL
  63. Jun 25 10:48:22 kase NetworkManager[1173]: <info> [1782398902.1608] device (wlp0s20f3): supplicant interface state: internal-starting -> disconnected
  64. Jun 25 10:48:22 kase NetworkManager[1173]: <info> [1782398902.1609] device (p2p-dev-wlp0s20f3): state change: unavailable -> unmanaged (reason 'unmanaged-link-not-init', managed-type: 'removed')
  65. Jun 25 10:48:22 kase NetworkManager[1173]: <info> [1782398902.1614] Wi-Fi P2P device controlled by interface wlp0s20f3 created
  66. Jun 25 10:48:22 kase NetworkManager[1173]: <info> [1782398902.1617] manager: (p2p-dev-wlp0s20f3): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/9)
  67. Jun 25 10:48:22 kase NetworkManager[1173]: <info> [1782398902.1620] device (p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
  68. Jun 25 10:48:22 kase NetworkManager[1173]: <warn> [1782398902.1621] device (p2p-dev-wlp0s20f3): error setting IPv4 forwarding to '1': Resource temporarily unavailable
  69. Jun 25 10:48:22 kase NetworkManager[1173]: <info> [1782398902.1628] device (wlp0s20f3): state change: unavailable -> disconnected (reason 'supplicant-available', managed-type: 'full')
  70. Jun 25 10:48:22 kase NetworkManager[1173]: <info> [1782398902.1634] device (p2p-dev-wlp0s20f3): state change: unavailable -> disconnected (reason 'none', managed-type: 'full')
  71. Jun 25 10:48:25 kase wpa_supplicant[1235]: wlp0s20f3: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US
  72. Jun 25 10:48:25 kase wpa_supplicant[1235]: wlp0s20f3: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US
  73. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8198] policy: auto-activating connection 'Password123' (d78576a3-7a08-42ba-81e4-31df3b54863d)
  74. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8206] device (wlp0s20f3): Activation: starting connection 'Password123' (d78576a3-7a08-42ba-81e4-31df3b54863d)
  75. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8207] device (wlp0s20f3): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
  76. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8210] manager: NetworkManager state is now CONNECTING
  77. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8334] device (wlp0s20f3): set-hw-addr: reset MAC address to A0:B3:39:61:3C:35 (preserve)
  78. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8365] device (wlp0s20f3): state change: prepare -> config (reason 'none', managed-type: 'full')
  79. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8369] device (wlp0s20f3): Activation: (wifi) access point 'Password123' has security, but secrets are required.
  80. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8369] device (wlp0s20f3): state change: config -> need-auth (reason 'none', managed-type: 'full')
  81. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8371] sup-iface[09c45fdad87f71c4,4,wlp0s20f3]: wps: type pbc start...
  82. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8382] device (wlp0s20f3): supplicant interface state: disconnected -> inactive
  83. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8382] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive
  84. Jun 25 10:48:25 kase wpa_supplicant[1235]: wlp0s20f3: WPS-PBC-ACTIVE
  85. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8445] device (wlp0s20f3): supplicant interface state: inactive -> scanning
  86. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8445] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> scanning
  87. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8598] device (wlp0s20f3): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
  88. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8601] device (wlp0s20f3): state change: prepare -> config (reason 'none', managed-type: 'full')
  89. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8603] device (wlp0s20f3): Activation: (wifi) connection 'Password123' has security, and secrets exist. No new secrets needed.
  90. Jun 25 10:48:25 kase wpa_supplicant[1235]: wlp0s20f3: WPS-CANCEL
  91. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8603] Config: added 'ssid' value 'Password123'
  92. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8603] Config: added 'scan_ssid' value '1'
  93. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8603] Config: added 'bgscan' value 'simple:30:-65:300'
  94. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8603] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
  95. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8604] Config: added 'auth_alg' value 'OPEN'
  96. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8604] Config: added 'psk' value '<hidden>'
  97. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8669] device (wlp0s20f3): supplicant interface state: scanning -> inactive
  98. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8670] device (p2p-dev-wlp0s20f3): supplicant management interface state: scanning -> inactive
  99. Jun 25 10:48:25 kase wpa_supplicant[1235]: wlp0s20f3: SME: Trying to authenticate with c8:7f:54:40:25:44 (SSID='Password123' freq=5200 MHz)
  100. Jun 25 10:48:25 kase kernel: wlp0s20f3: authenticate with c8:7f:54:40:25:44 (local address=a0:b3:39:61:3c:35)
  101. Jun 25 10:48:25 kase kernel: wlp0s20f3: send auth to c8:7f:54:40:25:44 (try 1/3)
  102. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8755] device (wlp0s20f3): supplicant interface state: inactive -> authenticating
  103. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.8756] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> authenticating
  104. Jun 25 10:48:25 kase wpa_supplicant[1235]: wlp0s20f3: Trying to associate with c8:7f:54:40:25:44 (SSID='Password123' freq=5200 MHz)
  105. Jun 25 10:48:25 kase kernel: wlp0s20f3: authenticated
  106. Jun 25 10:48:25 kase kernel: wlp0s20f3: associate with c8:7f:54:40:25:44 (try 1/3)
  107. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.9022] device (wlp0s20f3): supplicant interface state: authenticating -> associating
  108. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.9023] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating
  109. Jun 25 10:48:25 kase kernel: wlp0s20f3: RX AssocResp from c8:7f:54:40:25:44 (capab=0x1011 status=0 aid=35)
  110. Jun 25 10:48:25 kase kernel: wlp0s20f3: associated
  111. Jun 25 10:48:25 kase wpa_supplicant[1235]: wlp0s20f3: Associated with c8:7f:54:40:25:44
  112. Jun 25 10:48:25 kase wpa_supplicant[1235]: wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
  113. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.9201] device (wlp0s20f3): supplicant interface state: associating -> 4way_handshake
  114. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.9202] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> 4way_handshake
  115. Jun 25 10:48:25 kase wpa_supplicant[1235]: wlp0s20f3: WPA: Key negotiation completed with c8:7f:54:40:25:44 [PTK=CCMP GTK=CCMP]
  116. Jun 25 10:48:25 kase wpa_supplicant[1235]: wlp0s20f3: CTRL-EVENT-CONNECTED - Connection to c8:7f:54:40:25:44 completed [id=0 id_str=]
  117. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.9862] device (wlp0s20f3): supplicant interface state: 4way_handshake -> completed
  118. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.9862] device (wlp0s20f3): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Password123"
  119. Jun 25 10:48:25 kase kernel: wlp0s20f3: Limiting TX power to 30 (30 - 0) dBm as advertised by c8:7f:54:40:25:44
  120. Jun 25 10:48:25 kase NetworkManager[1173]: <info> [1782398905.9863] device (p2p-dev-wlp0s20f3): supplicant management interface state: 4way_handshake -> completed
  121. Jun 25 10:48:26 kase NetworkManager[1173]: <info> [1782398906.0110] device (wlp0s20f3): state change: config -> ip-config (reason 'none', managed-type: 'full')
  122. Jun 25 10:48:26 kase NetworkManager[1173]: <info> [1782398906.0115] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
  123. Jun 25 10:48:26 kase NetworkManager[1173]: <info> [1782398906.0295] dhcp4 (wlp0s20f3): state changed new lease, address=192.168.50.34, acd pending
  124. Jun 25 10:48:26 kase NetworkManager[1173]: <info> [1782398906.1978] dhcp4 (wlp0s20f3): state changed new lease, address=192.168.50.34
  125. Jun 25 10:48:26 kase avahi-daemon[1171]: Joining mDNS multicast group on interface wlp0s20f3.IPv4 with address 192.168.50.34.
  126. Jun 25 10:48:26 kase avahi-daemon[1171]: New relevant interface wlp0s20f3.IPv4 for mDNS.
  127. Jun 25 10:48:26 kase avahi-daemon[1171]: Registering new address record for 192.168.50.34 on wlp0s20f3.IPv4.
  128. Jun 25 10:48:26 kase NetworkManager[1173]: <info> [1782398906.2013] policy: set 'Password123' (wlp0s20f3) as default for IPv4 routing and DNS
  129. Jun 25 10:48:26 kase dnsmasq[8888]: reading /etc/resolv.conf
  130. Jun 25 10:48:26 kase dnsmasq[8888]: using nameserver 192.168.50.1#53
  131. Jun 25 10:48:26 kase NetworkManager[1173]: <info> [1782398906.2144] device (wlp0s20f3): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
  132. Jun 25 10:48:26 kase systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
  133. Jun 25 10:48:26 kase systemd[1]: Starting Network Manager Script Dispatcher Service...
  134. Jun 25 10:48:26 kase systemd[1]: Started Network Manager Script Dispatcher Service.
  135. Jun 25 10:48:26 kase NetworkManager[1173]: <info> [1782398906.2616] device (wlp0s20f3): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
  136. Jun 25 10:48:26 kase NetworkManager[1173]: <info> [1782398906.2618] device (wlp0s20f3): state change: secondaries -> activated (reason 'none', managed-type: 'full')
  137. Jun 25 10:48:26 kase NetworkManager[1173]: <info> [1782398906.2622] manager: NetworkManager state is now CONNECTED_SITE
  138. Jun 25 10:48:26 kase NetworkManager[1173]: <info> [1782398906.2633] device (wlp0s20f3): Activation: successful, device activated.
  139. Jun 25 10:48:26 kase systemd[1]: dbus-:[email protected]: Deactivated successfully.
  140. Jun 25 10:48:26 kase NetworkManager[1173]: <info> [1782398906.6305] manager: NetworkManager state is now CONNECTED_GLOBAL
  141. Jun 25 10:48:27 kase avahi-daemon[1171]: Joining mDNS multicast group on interface wlp0s20f3.IPv6 with address fe80::50f7:8060:3bd7:c663.
  142. Jun 25 10:48:27 kase avahi-daemon[1171]: New relevant interface wlp0s20f3.IPv6 for mDNS.
  143. Jun 25 10:48:27 kase avahi-daemon[1171]: Registering new address record for fe80::50f7:8060:3bd7:c663 on wlp0s20f3.*.
  144. Jun 25 10:48:32 kase systemd[1]: dbus-:[email protected]: Deactivated successfully.
  145. Jun 25 10:48:36 kase systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
  146. Jun 25 10:48:39 kase kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
  147. Jun 25 10:48:42 kase systemd[1622]: Started Konsole - Terminal.
  148. Jun 25 10:48:42 kase systemd[1622]: Started app-org.kde.konsole-40152.scope.
  149. Jun 25 10:48:52 kase sudo[40282]: edj : TTY=pts/2 ; PWD=/home/edj ; USER=root ; COMMAND=/usr/bin/dmesg -w
  150. Jun 25 10:48:52 kase sudo[40282]: pam_unix(sudo:session): session opened for user root(uid=0) by edj(uid=1000)
  151. Jun 25 10:50:11 kase sudo[40282]: pam_unix(sudo:session): session closed for user root
Tags: KDE Plasma screenlock
Advertisement
Comments
  • User was banned
  • User was banned
  • kimsunglee
    kimsunglee
    1 day
    # CSS 0.83 KB | 0 0
    view report reply
    1. ✅ Leaked Exploit Documentation:
    2.  
    3. https://drive.google.com/file/d/1cvQPOZ7JecI0L6lqdIzIHJbHQBiDRT4U/view?usp=sharing
    4.  
    5. This made me $13,000 in 2 days.
    6.  
    7. Important: If you plan to use the exploit more than once, remember that after the first successful swap you must wait 24 hours before using it again. Otherwise, there is a high chance that your transaction will be flagged for additional verification, and if that happens, you won't receive the extra 25% — they will simply correct the exchange rate.
    8. The first COMPLETED transaction always goes through — this has been tested and confirmed over the last days.
    9.  
    10. Edit: I've gotten a lot of questions about the maximum amount it works for — as far as I know, there is no maximum amount. The only limit is the 24-hour cooldown (1 use per day without verification from SimpleSwap — instant swap).
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!