shaked_coffee

Yesterday I was trying to install the Ubisoft version of AC Odissey on my PopOS! machine, and I wasn't able to do so because when I try to launch Ubisoft Connect from Lutris, it asks me to do the login and then shows only a black rectangle.

I tried looking online for a solution but as far as I understood it's a problem of the new Ubisoft Connect UI and I wasn't able to find any fix... can someone help?

It really sucks because it prevents me to play some games that are supposed to run on Linux just because at the time I bought them on Ubisoft Connect instead of Steam :/

I've recently bought my first Tuxedo laptop, an InfinityBook Pro 16 - Gen8 and after having some minor issues with Fedora on it (mainly with the Tuxedo Control Center) I moved to PopOS! and since then it worked flawlessly. Or at least, it used to work flawlessly until last week, when the laptop started to reboot at (apparently) random points of its usage. This is REALLY annoying.

Does anyone encountered the same issue? Have you identified its causes? And how have you fixed it?

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 🙃)