shaked_coffee

cross-posted from: https://feddit.it/post/9251429

I was previously using PopOS! 22.04 on my tuxedo laptop and I'd installed on it Howdy to take advantage of the IR camera and have a windows hello alike face recognition feature.

Everything was working fine, but after some time GNOME 46 and its new goodies were too tempting to stick with Pop's old GNOME version (at least for me) and therefore I switched to Ubuntu 24.04

However, when I tried to install howdy using the PPAs as I did with Pop I noticed it wasn't working because of some changes that were made regarding on how Python is managed, and I couldn't find a solution for that. Looking at howdy's GitHub issues, there are a lot of them talking about this problem that seems to be started with 23.x versions already, but having so many issues created a bit too much confusion to me and I didn't manage to find a working solution from there.

Is there anyone here using Howdy on Ubuntu 24.04? How have you managed to install it?

I was previously using PopOS! 22.04 on my tuxedo laptop and I'd installed on it Howdy to take advantage of the IR camera and have a windows hello alike face recognition feature.

Everything was working fine, but after some time GNOME 46 and its new goodies were too tempting to stick with Pop's old GNOME version (at least for me) and therefore I switched to Ubuntu 24.04

However, when I tried to install howdy using the PPAs as I did with Pop I noticed it wasn't working because of some changes that were made regarding on how Python is managed, and I couldn't find a solution for that. Looking at howdy's GitHub issues, there are a lot of them talking about this problem that seems to be started with 23.x versions already, but having so many issues created a bit too much confusion to me and I didn't manage to find a working solution from there.

Is there anyone here using Howdy on Ubuntu 24.04? How have you managed to install it?

I recently finished the episode of The Verge's podcast #Decoder with the interview to Bluesky's CEO and it seems a quite interesting project. At the beginning I wasn't looking really into it because of their choice of using a new protocol instead of the existing ActivityPub, but after listening to her and the reasons behind this choice maybe I'll give them a chance.

What do you think? Do you use it alongside with the fediverse?

Since I recently set up a decently powerful homelab, with a bunch of services running on docker behind traefik, I thought it would have been cool to try out selfhosting a matrix homeserver for personal use (at the beginning it will be just me, potentially it will extend to some friends and/or a small organization of around 20 people working together). At first I was thinking about going with Dendrite, but then I've seen it still doesn't support Threads, nor Matrix 1.5 API and that despite the announcement of a couple of months ago its repo hasn't yet be moved to the new element-hq GitHub as it happened with Synapse. This made it seem kinda like a "2nd class citizen" compared to Synapse, and therefore made me think if the latter would have been a better option to selfhost. And then I bumped into Conduit.rs so now I have 3 option to be undecided about!

Therefore, here I am asking for your preferences and advices: which is your favourite one / which one would you recommend for my use-case?

In the last months, the battery of my S2 tablet was draining really quickly, untill it died and I wasn’t able to recharge it. So, I thought that the battery was dead (it served me for a bunch of years so it could have been acceptable) and I ordered on Amazon a new battery to replace it.

After replacing the battery, though, the tablet turned on saying the new battery was at 50% and, when plugged in, it was acting as if it was charging. Apart from the fact that it wasn’t charging the battery that instead was quickly draining even if plugged in.

Obviously I tried cleaning the charging port, changing cable, changing power adapter, changing socket on the wall, but nothing worked. So I assumed that the new battery they sent me was broken and I purchased a new one but when it arrived: exactly same situation.

Could it be that I was very unlucky and I got a broken new battery twice? Or maybe the problem is somewhere else? Did anyone encounter a similar issue?

I’m finally moving my selfhosting experiments from a VPS to a physical machine in my house but, since I don’t have a static IP address, I opted to use the dynamic dns service offered by Cloudflare.

On their official website I’ve seen suggested ddclient but I haven’t find that much information on which labels should I add to set it up. Therefore, I’ve also found this docker image that seems pretty clean and easy to set up, but the video talking about it was of 3 years ago and I’ve seen that the github repository has been archived last year…

Which option (not necessarily among the two above) do you prefer to set up your Dynamic DNS with Cloudflare? (I don’t know if this can be an important information to add or not, but the Linux server I’m using is running NixOS)

My team wanted to start using Trello to better organize the work we have to do and, since I believe it's much easier to start using foss software from the beginning rather then switching to it after years of using something else, I wanted to suggest now a different option, possibly selfhosted.

I've seen online that there is Focalboard that seems to be what we are looking for but I've seen it recently switched from being backed by mattermost team to be community-driven and I didn't found enough documentation on how to install it with docker on an arm server... Does anyone use it? Is it a good option or there are better ones? And if you're using it, could you help me spinning it up?

Looks like a new model for the Fairphone has been announced! What do you think about it?

Personally I love the fairphone project but after having tried GrapheneOS on my Pixel 6a it would be hard to move to a different OS

UPDATE:

After some more testing, trying to disable one by one the entries on proc/acpi/wakeup and comparing them with the output of lspci, I think I found out that the problem is related with the PCIE components that idk why send a wake-up signal to the system every time it enters sleep mode. As a temporary fix, I created a service that runs a script to disable those four lines every time I start / reboot the system, waiting for a proper fix in a future kernel update. Here are the two files I created:

/etc/systemd/system/disable-PCIE-wakeup.service:

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/local/bin/disable-PCIE-wakeup.sh

[Install]
WantedBy=multi-user.target

/usr/local/bin/disable-PCIE-wakeup.sh:

#!/bin/sh
for i in $(cat /proc/acpi/wakeup | grep RP | grep enabled | grep S4 | awk '{print $1}'); 
  do 
    echo $i > /proc/acpi/wakeup; 
  done

(and after creating those files, I enabled the new service with sudo systemctl enable disable-PCIE-wakeup.service)

ORIGINAL POST:

Some time ago I posted on Fedora Discussion because my Fedora system (MSI Summit e16 flip running Fedora 38) started having problems with sleep mode after a kernel update (actually, starting from kernel 6.3.x and with all later versions).

Unfortunately I didn't receive that many replies there, so I tried to troubleshoot by myself and I found out that what's causing this problem is probably an internal device of the laptop that is supposed to be used to wake up the laptop from sleep (like the touchpad or the fingerprint reader? idk) and that instead is misfunctioning and waking it up immediately after it reached the sleep state. I'm saying so because I tried to temporarily disable all the lines in /proc/acpi/wakeup using this simple script below that I found somewhere online and, after doing that until the next time I reboot, the laptop stays asleep as expected.

So now my question is: how do I isolate which device is causing the problem? And how can I permanently fix this issue? I suspect that the problematic device could be the fingerprint reader since it was unsupported up until Fedora 38 and doesn't still work properly since it keeps forgetting the fingerprints I add... is there a way for me to disable it completely and try to see if it fixes the issue?

(I’m not sure about if this is the proper place to ask questions like this, or if I should report this issue somewhere else, since it seems more a kernel issue. Recommendations about better place to ask it are welcomed 🙃)

As the title says, today I noticed that instead of the "OpenStreetMap contributor" overlay I'm used to see on Moovit maps there is the Google logo, which makes me think that they moved from OpenStreetMap data to google's.

Is there any article about this? And especially about why? One of the main reasons I was using moovit over Google Transit was because since there is still no valid foss transit app at least they where contributing to foss maps...