Siduction Forum

Quote from: hendrikL on 2026/08/28, 07:31:37I have no issues to run a siduction-iso in qemu/kvm. Which grafik-card did you choose. QXL? if so test other like virtio ...

Interesting, I switch from QXL to Virtio and it seems to be working. I'm not sure what's change, this VM has been running for a couple years now with this configuration. Other than regularly d-u. 

I had similar problem this morning but only one app affected Tuta mail. Looking at Kwallet setting "use secret service" had been selected ( previously off) which looks like it disables access to passwords from KeePassXC, I unselected secret service and it seems to be working OK again

Ich habe keine Ahnung, was es mit diesem login keyring auf sich hat. Es hat weder etwas mit dem Netzwerk noch mit einem Passwortmanager zu tun. Die Meldung erscheint nachdem ich mich eingeloggt habe und ich muss mein login Passwort nochmal eingeben, ansonsten kann ich nicht weiterarbeiten. Das Problem habe ich übrigens sowohl auf dem Desktop Rechner als auch auf dem Laptop seit einem der letzten Upgrades.
Anscheinend wurde vorher dieser keyring automatisch beim Anmelden entsperrt, was jetzt wohl nicht mehr so ist.

I have no issues to run a siduction-iso in qemu/kvm. Which grafik-card did you choose. QXL? if so test other like virtio ...

I'v been having this issue since later 6.18 siduction kernels on a KVM-Qemu installed system. System seems to boot without issue. I'm presented with the Lightdm login screen but the system freezes. Occasionally I get a couple characters in and once in a while I can fully login but again the system freezes forcing a hard reset. I suspect it's something to do with the kernel because I installed the Liquorix kernel(and updated it) and this issue doesn't present itself when booting any Liquorix kernel. I've progressively updated the kernels as they became available in hope it was just a quirk but the issue remains, again, only with Siduction kernels.
Anybody else having issues with KVM-Qemu and siduction kernels?

EDIT: I just installed linux-image-7.1.10+deb14-amd64 and it also works fine.

Verstehe ich jetzt nicht richtig. Hast du einen Passwort-Manager?
Wird das Netzwerk/Wi-Fi nicht entsperrt, oder was wird nicht entsperrt?

Hallo,
seit einem der letzten Updates bekomme ich nach dem Hochfahren und Einloggen des Rechners immer die Meldung "The login keyring did not get unlocked when you logged into your computer" und ich muss mein login Passwort nochmal eingeben. Vorher war das Entsperren automatisch beim Anmelden erfolgt. Kann man das irgendwo einstellen?

I moved it to upgrade-warnings, it could affect other systems too!

This topic has been moved to upgrade warnings.

Well, I used to have the same problem.

I investigate spare time to, hopefully, solve it.

In short, the culprit is firewalld.

Quote: https://userbase.kde.org/KDEConnect#firewalld

[...]

If your firewall is firewalld, you can open the necessary ports with:

sudo firewall-cmd --permanent --zone=home --add-service=kdeconnect
sudo firewall-cmd --reload

Note
This allows KDE Connect to be accessed from outside while you're in the "home" zone. A zone can be assigned to your WiFi connection in network settings. For safety, you should rather avoid running KDE Connect in "public" zone.

But it doesn't work because the home-zone wasn't active.

# firewall-cmd --get-active-zones
docker
  interfaces: docker0
libvirt
  interfaces: virbr0
public (default
  interfaces: wlan0

No home zone active!

So I had to activate that zone to get it working.

firewall-cmd --permanent --zone=home --change-interface=wlan0
I am using a laptop connected via Wi-Fi/wlan0 to the Network/Internet.

# firewall-cmd --get-active-zones
docker
  interfaces: docker0
home
  interfaces: wlan0
libvirt
  interfaces: virbr0
public (default)

Don't forget to reload firewalld.

Here is my home.xml

# cat /etc/firewalld/zones/home.xml
<?xml version="1.0" encoding="utf-8"?>
<zone>
  <short>Home</short>
  <description>For use in home areas. You mostly trust the other computers on networks to not harm your computer. Only selected incoming connections are accepted.</description>
  <service name="ssh"/>
  <service name="mdns"/>
  <service name="samba-client"/>
  <service name="dhcpv6-client"/>
  <service name="kdeconnect"/>
  <masquerade/>
  <forward/>
</zone>