Re: Dell Latitude 5400 + plasma - keyboard?
> > Have you tried just going in the Shortcut settings in Plasma and > manually assigning the keys that you want? That way, it doesn't really > matter what Plasma thinks the keys are because you are directly entering > them in the settings dialog. > > Settings -> Shortcuts -> Shortcuts -> Power Management Yes, I did. But no success. But as I mentioned in a former post: I think, it is not a problem with X or the window-manager, it is a general problem. Because without running X and only in console, the function keys do not work, too. It has something to do with acpi, whilst acpi_listen showing correct results. Whatever, the problem is not X or wm related, it is a system-problem. Best regards Hans
Re: Dell Latitude 5400 + plasma - keyboard?
Hans writes: > No, I am running Plasma in X as well as XFCE. I am no friend of Wayland, so I > avoiding it. > > Best > > Hans >> So is this a difference between Wayland and X then? You run Plasma in >> Wayland and XFCE in X since it only runs in X? Have you tried just going in the Shortcut settings in Plasma and manually assigning the keys that you want? That way, it doesn't really matter what Plasma thinks the keys are because you are directly entering them in the settings dialog. Settings -> Shortcuts -> Shortcuts -> Power Management -- this is my clever sig.
Re: Dell Latitude 5400 + plasma - keyboard?
>> On Wed 05 Feb 2025 at 11:38:00 (-0500), Hans wrote: > No, thwe problem is, the windowmanager or the system itself does not > recognize the code or suppresses it somehow. Are you running under X or Wayland? If X, try running "xev" and pressing the keys to see what the system thinks you're doing. If Wayland, "xev" might work; you could also try "wshowkeys". -- Karl Vogel I don't speak for anyone but myself I got a dog and named him 'Stay'. Now, I go 'Come here, Stay!' After a while the dog went insane and wouldn't move at all. --Steven Wright
Re: Dell Latitude 5400 + plasma - keyboard?
There is indeed a difference.
Thisis the output for Plasma:
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwertz)" };
xkb_types { include "complete" };
xkb_compat{ include "complete" };
xkb_symbols { include
"pc+de+inet(evdev)+compose(lwin)+terminate(ctrl_alt_bksp)"
};
xkb_geometry { include "dell(latitude)"};
And here it is for XFCE:
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwertz)" };
xkb_types { include "complete" };
xkb_compat{ include "complete" };
xkb_symbols { include
"pc+de+inet(evdev)+compose(lwin)+terminate(ctrl_alt_bksp)"
};
xkb_geometry { include "pc(pc104)" };
};
As we can see, in Plasma it is dell, and in XFCE it is pc104. However, due to
this, I tried setting
the keyboard to "pc104" in Plasma, but the issue stays. The function keys are
not recognized as
described in my first mail.
Maye it is a bug in Plasma? Who knows
Hans
> On 05/02/2025 18:57, Hans wrote:
> > In console and in Plasma the Brightness can not be adjusted, but in XFCE
> > it
> > can. However, I could not get, which keyboard setting XFCE is using, does
> > pne know?
>
> Save output of the following command executed in XFCE and KDE
>
> setxkbmap -print
>
> and compare it to settings from /etc/default/keyboard. What symbols are
> reported by "xev" in both DE when you press Fn keys?
>
> Perhaps you can just uncheck "configure layouts" for keyboard in KDE
> system settings.
Re: Dell Latitude 5400 + plasma - keyboard?
No, I am running Plasma in X as well as XFCE. I am no friend of Wayland, so I avoiding it. Best Hans > So is this a difference between Wayland and X then? You run Plasma in > Wayland and XFCE in X since it only runs in X?
Re: Dell Latitude 5400 + plasma - keyboard?
Hans writes: > In console and in Plasma the Brightness can not be adjusted, but in XFCE it > can. However, I could not get, which keyboard setting XFCE is using, does pne > know? So is this a difference between Wayland and X then? You run Plasma in Wayland and XFCE in X since it only runs in X?
Re: Dell Latitude 5400 + plasma - keyboard?
On 05/02/2025 18:57, Hans wrote: In console and in Plasma the Brightness can not be adjusted, but in XFCE it can. However, I could not get, which keyboard setting XFCE is using, does pne know? Save output of the following command executed in XFCE and KDE setxkbmap -print and compare it to settings from /etc/default/keyboard. What symbols are reported by "xev" in both DE when you press Fn keys? Perhaps you can just uncheck "configure layouts" for keyboard in KDE system settings.
Re: Dell Latitude 5400 + plasma - keyboard?
Hi Cindy, I am aware of the settings in BIOS. That is not the problem. As I already mentioned, the change of primary and secondary function is working. (I called this "level" change, maybe it was not teh correct expresion). No, thwe problem is, the windowmanager or the system itself does not recognize the code or suppresses it somehow. Do not know, what really happens. Hans > Hi.. In case you haven't found it yet, some laptops (not all) have a > BIOS setting that changes that function. Some of those laptops that do > have that setting don't always word it in a way that intuitively > indicates that is what you're changing and how you're changing it. > > If that setting exists, it might take changing it a couple times to hit > the combination one wants. My quick Internet search brought up this > blurb that fits my memory recall for the last time I changed my own: > > +++ BEGIN INTERNET SEARCH RESULT +++ > > To change the Fn function on a Dell Latitude 5400, navigate to the BIOS > by pressing "F2" during startup, then go to "POST Behavior" > "Fn Lock > Options" where you can enable or disable the Fn Lock feature, which will > toggle the primary behavior of the function keys using the "Fn + Esc" > combination. > Key points: > > Access BIOS: Press "F2" when the Dell logo appears during boot. > > Navigation: Go to "POST Behavior" > "Fn Lock Options". > Toggle Fn Lock: Enable or disable the "Fn Lock" option to change the > default function key behavior. > > +++ ENG INTERNET SEARCH RESULT +++ > > DISCLAIMER: Those unsolicited AI answers sometimes unintentionally warp > their directions. I'm just hoping that blurb hits close enough to the > right path to help others find that setting. > > Best wishes... > > Cindy :)
Re: Dell Latitude 5400 + plasma - keyboard?
On Wed, 2025-02-05 at 12:57 +0100, Hans wrote: > Dear list, > > is anyone by chance using a Dell Latitude 5400 with Plasma? > > I am looking for the keyboard setting for Debian wuith this hardware. > The > problem is, the Function-keys are not working. > > Not working means: The second level do not work like "volume > higher/lower" > "brightness" and so on. Hi.. In case you haven't found it yet, some laptops (not all) have a BIOS setting that changes that function. Some of those laptops that do have that setting don't always word it in a way that intuitively indicates that is what you're changing and how you're changing it. If that setting exists, it might take changing it a couple times to hit the combination one wants. My quick Internet search brought up this blurb that fits my memory recall for the last time I changed my own: +++ BEGIN INTERNET SEARCH RESULT +++ To change the Fn function on a Dell Latitude 5400, navigate to the BIOS by pressing "F2" during startup, then go to "POST Behavior" > "Fn Lock Options" where you can enable or disable the Fn Lock feature, which will toggle the primary behavior of the function keys using the "Fn + Esc" combination. Key points: Access BIOS: Press "F2" when the Dell logo appears during boot. Navigation: Go to "POST Behavior" > "Fn Lock Options". Toggle Fn Lock: Enable or disable the "Fn Lock" option to change the default function key behavior. +++ ENG INTERNET SEARCH RESULT +++ DISCLAIMER: Those unsolicited AI answers sometimes unintentionally warp their directions. I'm just hoping that blurb hits close enough to the right path to help others find that setting. Best wishes... Cindy :) -- Talking Rock, Pickens County, Georgia, USA * runs with birdseed! *
Re: Dell Latitude 5400 + plasma - keyboard?
Some checks showed, that obviously the events are read correct, if I see this corect. Please see: $ acpi_listen button/mute MUTE 0080 K button/volumedown VOLDN 0080 K button/volumeup VOLUP 0080 K 9DBB5994-A997- 00d0 button/f20 F20 0080 K 9DBB5994-A997- 00d0 video/brightnessdown BRTDN 0087 9DBB5994-A997- 00d0 9DBB5994-A997- 00d0 video/brightnessup BRTUP 0086 Looks like they are not interpreted somehow. Hans
