12:36 <colo> can I send keystorkes to kodi when I have a shell on its host?

12:37 <colo> (need to enter a FAIRLY LONG oath token into an add-on dialog, and don't want to attach a kbd for that if I do not have to)

12:44 <colo> ok, I edited the respective XML. but I would still be interested to know if this is possible.

13:41 <LEBot> [slack] <chewitt> You can use “kodi-remote” for a virtual keyboard, but this does not support copy/paste to the GUI

14:00 <colo> chewitt, so there is no command that I can execute on the shell like (a hypothetical) `kodi-kbd-keypress B`, that would make it appear to a running kodi instance just like shift+b had been pressed on a physical keyboard, or that an uppercase B was entered by the kodi-provided on-screen kbd?

14:17 <Forage> Good afternoon. Can anyone tell me where/how the /flash partition can be accessed on a RPi 4?

14:18 <Forage> (by ssh)

14:19 <colo> Forage, not sure I understand your question, but both `df` and `mount` should show you the source device and target mountpoint of filesystems in your system

14:21 <Forage> When toggling the firmware update setting in the settings files are supposed to be places on the /flash partition, but this partition is nowhere to be found

14:21 <Forage> placed*

14:22 <colo> I don't have LE10 ond an RPi4 operational at the moment. what does `df -h /flash/` on the shell yield for you?

14:22 <Forage> "No such file or directory"

14:23 <Forage> The settings does "something", as boot messages are shown on reboot afterwards

14:23 <Forage> but I can't read the messages as fast and I kind find what it did

14:25 <Forage> (the firmware update isn't working)

14:30 <colo> Forage, maybe you can find the messages in the journal? `journalctl` will show

14:34 <Forage> god I feel like an idiot...thanks for bringing me to that conclusion colo

14:34 <Forage> the journal pointed out to me that I've been connecting to the wrong RPi...

14:39 <Forage> Is there a way to log the boot messages shown at the same time as the logo though? Or pause that screen?

14:51 <colo> lol, that's a nice resolution ;)

14:51 <colo> I don't think/know if that is possible, sorry

15:10 <Forage11> Ok, partially sorted: https://forum.libreelec.tv/thread/25365-rpi-firmware-in-10-0-2-not-updating continuing the discussion over there to help out others as well

15:12 <diederik> Forage11: in the kernel parameters, there usually is a 'quiet' option. If you remove that, you'll see the boot messages

17:45 <Forage11> diederik: I can see them, but they disappear too fast to be able to read them