#
✕ nick:the_eye
#asahi · 2025-06-25 21:03
the_eyeso it drains rather quickly, probably
#asahi · 2025-06-25 21:03
the_eyeI presume at this point no power saving functions are active as no plasma is running
#asahi · 2025-06-25 21:03
the_eyeas far as I can surmise: plugging it in turns it on. It then boots until it gets to the screen where I need to input my disk encryption password
#asahi · 2025-06-25 21:02
the_eyeoh, here's another hardware-related (I think?) question. Scenario: My MacBook Pro (M2) is shut down, powered off. I think "oh, tomorrow I'll be going on a railway trip so best fully charge it first" so I plug the magsafe plug in. I unplug it in the morning. a few hours later I finally board the train, open the laptop and find the battery completely empty.
#asahi · 2025-06-25 18:00
the_eyeso wait .. this means (in general) there might be differences between the 3 usb-c ports on an MBP2 in terms of what works and when?
#asahi · 2025-06-24 21:49
the_eyealso not caused by the usb-c to -a adapter not being present during boot. anything I try now, it still works. So I can only assume that one of the system updates I installed yesterday changed _something_ and after rebooting into MacOS and back into linux it works again? this is just.. baffling
#asahi · 2025-06-24 21:44
the_eyenope, a fresh boot is not it. hmm. different idea.
#asahi · 2025-06-24 21:41
the_eyeI mean it's not that it works only once or something, I just connected it again and it still works. Hmmm. lemme reboot this Macbook and see if that makes it break again.
#asahi · 2025-06-24 21:39
the_eyeIs there any sane explanation for this?
#asahi · 2025-06-24 21:38
the_eyeso next up I reboot into MacOS. Connect, hit button, it connects (same as yesterday). I reboot back into Asahi. Connect, hit button, it automounts.
#asahi · 2025-06-24 21:38
the_eyesteps, nothing works. It's not SELinux, it's not that ModemManager is running, nothing.
#asahi · 2025-06-24 21:38
the_eyetrying to determine whether I'm going crazy over here: Is there any basis that might explain why I'm seeing the following pattern: I'm trying to (again, made some changes) flash a firmware to this small embedded board. Same as two days ago, I connect it to my MacBook Pro, hit the button that makes it connect and ... it won't mount. I go wtf this worked 2 days ago. Try to retrace my
#asahi · 2025-06-24 14:16
the_eyethanks, ok. then I'll just get a usb-c one
#asahi · 2025-06-24 13:57
the_eyelike e.g. if I buy a thunderbolt dock (thinking in the future-proofing direction, only want to buy a really good one once), would that work, just in a dininished way, or will it just not work at all?
#asahi · 2025-06-24 13:56
the_eyedo these things generally have some kind of fallback usb-c mode?
#asahi · 2025-06-24 13:56
the_eyeso completely different question, this one hardware related. I have an M2 MacBook Pro. If I read the asahi feature support table correctly, I can see that there is currently no support for Thunderbolt and probably won't be any time soon (as the feature is labelled TBA). Since I'm an idiot and don't know hardware very well: does this mean thunderbolt periphery just won't work at all or
#asahi · 2025-06-23 17:58
the_eyebut if I just run locale, it only spits out the standard en_US.UTF-8 things. /etc/locale.conf also only contains those. So I wonder where kioworker gets the idea that I have this ANSI something character encoding?
#asahi · 2025-06-23 17:57
the_eyehere's another thing that vexes me: journal is full of entries that look like the following: "kioworker[13939]: Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8. Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead. If this causes problems, reconfigure your locale. See the locale(1) manual for more information."
#asahi · 2025-06-22 21:47
the_eye(so I have a watch that looks like an F91W but shows the time in beats ("Swatch Internet Time). And also does things that are more useful than that but I am a person who was young and optimistic in the 90s, so..)
#asahi · 2025-06-22 21:45
the_eye(also: can whole-heartedly recommend Sensor Watch and Sensor Watch Pro, they're a brilliant idea that works well - a board that replaces the innards of a Casio F91W or A158, turning into a thing you can modify/program. Has a temperature sensor and an accelerometer, battery lasts at least a year if not more)
#asahi · 2025-06-22 21:43
the_eyemany thanks for the help chaos_princess jannau!
#asahi · 2025-06-22 21:42
the_eyewell I've disabled it for now at least
#asahi · 2025-06-22 21:38
the_eyejannau: at least on the Ubuntu MicroPC - no. Arch Thinkpad is ancient and would take a few minutes to find/boot, so I'll check that sometime tomorrow, I guess
#asahi · 2025-06-22 21:30
the_eyejannau: that made it work right away! Many thanks!
#asahi · 2025-06-22 21:25
the_eyeyep, doing that now as I'm logging into asahi again
#asahi · 2025-06-22 21:23
the_eyechaos_princess: step one: under macos, it mounts right away (after I clicked "yes" on whether I wanted to allow it)
#asahi · 2025-06-22 21:16
the_eyeright, let me reboot and report back
#asahi · 2025-06-22 21:16
the_eyewill take a minute..
#asahi · 2025-06-22 21:15
the_eyedidn't think of that TBH
#asahi · 2025-06-22 21:15
the_eyechaos_princess: ah, worth a try
#asahi · 2025-06-22 21:15
the_eyeon the Ubuntu machine udisks just automounts the thing
#asahi · 2025-06-22 21:14
the_eyenope, little x86 thingy, GPD MicroPC running ubuntu with a MATE desktop
#asahi · 2025-06-22 21:13
the_eyedmesg tells me that at this point the device has reset itself
#asahi · 2025-06-22 21:12
the_eyeit runs for a while, then the board LED stops blinking (i.e. the board times out) and the mount command fails with "mount: /mnt: fsconfig system call failed: /dev/sda: Can't open blockdev."
#asahi · 2025-06-22 21:09
the_eyesudo mount -t vfat /dev/sda /mnt
#asahi · 2025-06-22 21:08
the_eyeinfos: https://paste.in-ulm.de/?0e4b62e82e6c0e0a#BWMVNr9BGbau2pTFSNVhG2TdcKv79RY4tCUfB35Gs81C and a journal paste: https://paste.in-ulm.de/?1ec5a0270a853a30#GhqpNA71Ya3SohS1EyPgqoSZhkbhSkyFuFkTXizBJuxQ
#asahi · 2025-06-22 21:07
the_eyechaos_princess: yeah. it's just this not-really-a-drive that you copy the firmware to to flash the thing
#asahi · 2025-06-22 21:07
the_eye(the new Sensor Watch Pro, in case anyone is curious - had the non-Pro already, absolutely loving it)
#asahi · 2025-06-22 21:06
the_eyejust sda, yeah
#asahi · 2025-06-22 21:06
the_eye(the device in question is an embedded board that offers this drive to flash a firmware to) - the same device mounts fine on a ubuntu or arch system
#asahi · 2025-06-22 21:05
the_eyeany hints where I should start poking? It's not SELinux related as sudo setenforce 0 doesn't change the behaviour
#asahi · 2025-06-22 21:05
the_eyeGDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sda at /run/media/eye/WATCHBOOT: fsconfig system call failed: /dev/sda: Can't open blockdev" whereas in journal I'm seeing messages about "udisksd[1509]: Couldn't find existing drive object for device /sys/devices/platform/soc/b02280000.usb/xhci-hcd.3.auto/usb1/1-1/1-1:1.2/host0/target0:0:0/0:0:0:0/block/sda"
#asahi · 2025-06-22 21:05
the_eyeI seem to be having some trouble that might just be fedora related, not sure, I'm not that used to fedora (normally an ARCH guy). I have here a very basic external drive that the system refuses to mount either via the graphical mounter or udisksctl or a manual sudo mount. The drive shows up in journalctl as /dev/sda but then mount times out. udisksctl says "Error mounting /dev/sda:
#asahi · 2025-06-19 15:25
the_eyeweirdly joins in with threads I had been reading on mastodon about how accessiblity is kinda shit these days on linux desktops
#asahi · 2025-06-19 15:21
the_eyew00t, it has stopped! and journal is quiet again! also, I've removed the keycombo for starting orca
#asahi · 2025-06-19 15:12
the_eyeThat the Screenreader (from what I understand how it would work) would need to scroll browser Windows all the way to the bottom kinda seems to make sense? So I just need to figure out how to stop the Screenreader and how to not accidentally start it again..
#asahi · 2025-06-19 15:11
the_eyeBecause the screenshot utility only came up on the second try.
#asahi · 2025-06-19 15:08
the_eye+s (because windows), I may have misfingered...
#asahi · 2025-06-19 15:08
the_eyehttps://bugs.kde.org/show_bug.cgi?id=499004 - this is a problem with screenreader, which apparently can be started with meta+alt+s. and I _think_ that earlier, when I wanted to make a screenshot of something, for which I have configured meta+SHIFT
#asahi · 2025-06-19 15:07
the_eyebut I _think_ I just found it

plus ›