~proycon

Eindhoven, the Netherlands

https://proycon.anaproy.nl

  • 🐧 FOSS software enthusiast
  • 🎓 Research Sofware Engineer, Natural Language Processing
  • 🐍 Python, 🌊 C, C++, 🦀 Rust, 🐚 Shell
  • 🔐 Privacy and Security
  • 📱 Sxmo co-maintainer
  • 🏡 Home automation
  • 🌍 Language enthusiast

See my homepage at https://proycon.anaproy.nl for further details and contact info.


#540 Make sure all core contributors have access to core projects 14 days ago

Comment by ~proycon on ~mil/sxmo-tickets

On 23-01-19 01:50, ~phartman wrote:

btw can you add my luc.edu e-mail address to sxmo-devel so I can flag things as closed/etc. via e-mail. I think I'm entered with my gmail.com account. Catch me on #sxmo for details.

I think we need Miles (~mla) to do that. Poking him on IRC may be quickest?

#9 Thumbnail mode a month ago

Comment by ~proycon on ~exec64/imv

This is high on my wishlist as well, the issue back on github was https://github.com/eXeC64/imv/issues/38, in which the main developer already expressed some ideas on implementing this. Would love to hear if anyone is working on it (otherwise I might have a try myself).

#542 feedbackd causes notification leds to not function a month ago

Comment by ~proycon on ~mil/sxmo-tickets

I opened an issue for this at Alpine Linux to discuss how we can best resolve this permission conflict between feedbackd and sxmo-utils: https://gitlab.alpinelinux.org/alpine/aports/-/issues/14466

#542 feedbackd causes notification leds to not function a month ago

on ~mil/sxmo-tickets

December 15, 2022 5:55 AM, "~proycon" outgoing@sr.ht wrote:

On the Pinephone A64, megapixels 1.6.0 pulls in feedbackd as a dependency. With feedbackd installed there are continuous messages in tinydm.log about permission denied:

/usr/bin/sxmo_led.sh: line 69: can't create /sys/class/leds/red:indicator/brightness: Permission

Ah, good catch! This is new. Sxmo sets up udev rules to set the proper permissions for these. The key is that the user should be in the 'video' group. But it seems feedbackd changes the group of these leds to 'feedbackd'. So we have a conflict here we should settle.

(Adding your user manually to the feedbackd group should bypass the issue).

I confirm that adding the user to the feedbackd group does fix the led issue.

Thanks proycon.

Mark

#542 feedbackd causes notification leds to not function a month ago

Comment by ~proycon on ~mil/sxmo-tickets

On the Pinephone A64, megapixels 1.6.0 pulls in feedbackd as a dependency. With feedbackd installed there are continuous messages in tinydm.log about permission denied:

/usr/bin/sxmo_led.sh: line 69: can't create /sys/class/leds/red:indicator/brightness: Permission

Ah, good catch! This is new. Sxmo sets up udev rules to set the proper permissions for these. The key is that the user should be in the 'video' group. But it seems feedbackd changes the group of these leds to 'feedbackd'. So we have a conflict here we should settle.

(Adding your user manually to the feedbackd group should bypass the issue).

#540 Make sure all core contributors have access to core projects 2 months ago

Comment by ~proycon on ~mil/sxmo-tickets

On 22-11-16 10:02, ~anjan wrote:

~stacyharper, ~phartman, and I ~anjan need read and write access to the wvkbd and wayout repositories.

Cc: ~proycon

Right! wvkbd on srht was already set properly. Wayout wasn't yet, added you all now. Also checked clickclack.

For github jjsullivan5196/wvkbd we might have to poke John Sullivan if we're not all in there as I can't access the repo settings either.

--

Maarten van Gompel

proycon@anaproy.nl https://proycon.anaproy.nl https://github.com/proycon

GnuPG key: 0x39FE11201A31555C XMPP: proycon@anaproy.nl Matrix: @proycon:matrix.anaproy.nl Telegram: proycon IRC: proycon (libera.chat + oftc) Mastodon: https://social.anaproy.nl/@proycon (@proycon@social.anaproy.nl) Keyoxide: https://keyoxide.org/8AC624881EF2AC30C0E68E2C39FE11201A31555C

#540 Make sure all core contributors have access to core projects 2 months ago

on ~mil/sxmo-tickets

On 22-11-16 10:02, ~anjan wrote:

~stacyharper, ~phartman, and I ~anjan need read and write access to the wvkbd and wayout repositories.

Cc: ~proycon

Right! wvkbd on srht was already set properly. Wayout wasn't yet, added you all now. Also checked clickclack.

For github jjsullivan5196/wvkbd we might have to poke John Sullivan if we're not all in there as I can't access the repo settings either.

--

Maarten van Gompel

proycon@anaproy.nl https://proycon.anaproy.nl https://github.com/proycon

GnuPG key: 0x39FE11201A31555C XMPP: proycon@anaproy.nl Matrix: @proycon:matrix.anaproy.nl Telegram: proycon IRC: proycon (libera.chat + oftc) Mastodon: https://social.anaproy.nl/@proycon (@proycon@social.anaproy.nl) Keyoxide: https://keyoxide.org/8AC624881EF2AC30C0E68E2C39FE11201A31555C

#540 Make sure all core contributors have access to core projects 2 months ago

on ~mil/sxmo-tickets

#484 bemenu height default to 30 from 20 8 months ago

Comment by ~proycon on ~mil/sxmo-tickets

I'm also still in favour of increasing the default yes, even though the tap-and-hold technique of course helps a lot.

--

Maarten van Gompel (proycon) https://proycon.anaproy.nl

#484 bemenu height default to 30 from 20 11 months ago

Comment by ~proycon on ~mil/sxmo-tickets

On 22-02-28 06:07, ~phartman wrote:

For a little while now, I've bumped the bemenu height to 30 from 20. This seems like a reasonable default. What does everyone think? I found 20 too prone to fat-fingering. This also feels closer to the dmenu defaults.

I haven't really tried 30 yet but I had indeed also contemptlated raising the default; in spite of having pretty slim fingers, it's fairly error-prone indeed.

--

Maarten van Gompel (proycon) https://proycon.anaproy.nl