[04:53] <lucidblu> Hello
[08:26] <skramer> Hi guys, I used to connect from my PC (22.04) via xrdp to another (also 22.04) without any problems. Since yesterday, however, I am stuck after Plasma desktop comes up. While mouse is still moving, I can not click anything nor does keyboard input work. Local login on the other PC works, though. Any ideas how to fix this?
[08:28] <skramer> It seems to hang in early stages - folders on Desktop don't evven get their symbols for "Pictures" etc., just plain folder symbols
[08:49] <weedmic> skramer: during this "stuck" period, can you do "alt + F2" and type konsole? or is that included?
[08:59] <skramer> weedmic: For whatever reason, that only triggers the keybindings on this machine, not on the remote
[09:00] <weedmic> skramer: try using remmina on the host machine.  that is what I use when ssh won't do., or wait for help with xrdp.
[09:02] <skramer> weedmic: Will do both ;-) Thank you
[09:03] <weedmic> Qapla!
[09:14] <alkisg> skramer: reboot the target PC, sometimes xrdp has stale processes. Or do a `killall -u your-user` via ssh
[09:38] <skramer> alksig: Unfortuantely still the same result...
[09:39] <skramer> alksig: Rebootet few times since yesterday. But even the killall -u does not change anything
[09:43] <skramer> alksig: What is "interesting": I can do a 'ps aux' in the ssh session, but an 'ls -a' does not show any reaction...
[10:09] <user|5> hello
[12:37] <BluesKaj> Hi all
[14:16] <mmikowski> demon_blade: https://kfocus.org/wf/recovery.html#bkm_recover_from_busybox
 0.201849] ACPI BIOS Error (bug): Failure creating named object [\ADBG], AE ALREADY EXISTS (20220331/dswload2-326)
 0.2018611 ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (202203 31/psobject-220)
 [ 0.212726] ACPI BIOS Error (bug): Could not resolve symbol [SB.PC00.I2C1.T PL11, AE NOT FOUND (20220331/dswload2-162) 0.212730] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/ps
 object-220)
 [ 1.851278] pcieport 0000:00:1c.0: pciehp: Cannot get irq -1 for the hotplug
 controller
[16:02] <mmikowski> Skramer: IMO, you almost certainly have a file system that is inaccessible. Perhaps broken nfs or file permission issues.
 How do i fix it? Should i try to clean install the os again? (re @IrcsomeBot: <mmikowski> Skramer: IMO, you almost certainly have a file system that is inaccessible. Perhaps broken nfs or file permission issues.)
[16:20] <mmikowski> It really depends on your setup. It's start by directly testing in your remote system if possible. My guess is the issue is there and may be independent of any remote connection.
[17:17] <mmikowski> Skramer ^^ :)
[18:37] <cloud> hey guys
[18:38] <cloud> for some reason i couldnt install konversation from command line
[18:38] <cloud> but when i installed konversation-data it installed bother konversation-data and konversation
[18:39] <cloud> intresting happened to me
[18:40] <alkisg> $ apt show konversation-data | grep Recommends
[18:40] <alkisg> Recommends: konversation (>= 21.12.3-0ubuntu1)
[18:40] <alkisg> cloud: it recommends konversation, so it's normal that it installed it
[18:40] <alkisg> While about the "some reason it failed" error, we'd need to see the exact message...
[19:38] <mmikowski> endo_kenji: You may have wires crossed. The boot errors you are seeing are warnings from the kernel and result from BIOS issues, and they often aren't significant (but not always). You can investigate them independently, and you can even effectively "patch" acpi tables, but that is typically beyond mere mortals. If your system is working as
[19:38] <mmikowski> expected and your find the symbols are not concerning, you can minimize them by using a log_level boot parameter. You can *probably* ignore the hotplug warning too if you aren't using hotplug.
[19:39] <mmikowski> endo_kenji: *We may have our wires crossed :)