Re: Notebook's password input jammed at SDDM login after screen lock:
Masaru Nomiya <[email protected]>
| Newsgroups | gmane.linux.suse.general |
|---|---|
| Message-ID | <[email protected]> |
Hello, In the Message; Subject : Re: Notebook's password input jammed at SDDM login after screen lock: Message-ID : <[email protected]> Date & Time: Fri, 21 Aug 2026 09:09:58 -0500 [PJ] == -pj via openSUSE Users <[email protected]> has written: PJ> On 8/21/26 7:25 AM, Masaru Nomiya wrote: [...] MN> > Why don't you try switching from amdgpu back to radeon? PJ> I can certainly try this. Could you explain the best way to do PJ> so? I can consult notes but figured to ask here also due to my PJ> inexperience. PJ> I notice also that entering the password at SDDM sometimes PJ> results in no dots resulting from the password keystrokes but PJ> pressing the 'enter key' reults in unlocking. Although this can PJ> be very slow and sluggish. It's true -- it's a bit of a stretch to think this is caused by the driver. So, I looked into it and found this information, though its a bit outdated. https://github.com/sddm/sddm/issues/1289 It's true that problems with sddm can be a real headache.... Anyway, choud you show this results? $ cat /etc/sddm.conf.d/sddm.conf Best Regards. -- Masaru Nomiya mail-to: nomiya @ ab.auone-net.jp "At first glance, AI generates code that appears correct, but it may contain issues. For example, it is not uncommon for the AI to generate code that malfunctions under specific conditions, contains security vulnerabilities, or is based on outdated implementation patterns. To identify these issues, a basic understanding of programming, algorithms, and design is required." --"Is "being able to write code" enough to survive?" (in JP)--