Then i guess it's ok/safe to add your repo for a long time, meaning that before "KDE4" is stopped we'll have time to take a bit of rest/hear about it

another thing : if i want to close firefox or thunderbird it freezes my screen, this is more disturbing with thunderbird for i need to close session to be able to use the pc which forces firefox to quit too quickly.
Is this due to a brand new plasma , or is it the driver ?

It's unlikely that it's due to Plasma, probably some other issue exposed lower in the stack.

it looks like there's a bug in firefox https://bugzilla.mozilla.org/show_bug.cgi?id=1083071

Hello

i can't have numlock On on my keyboard so far, despite i set it On in Bios and system settings/hardware/input device/keyboard/hardware (Turn On after KDE startup). I usually just turn it On there.

i'm using logitech illuminated keyboard :
Bus 004 Device 002: ID 046d:c318 Logitech, Inc. Illuminated Keyboard

Is this something known ? How can i fix this please ?

Thanks

manchette wrote:Is this something known ? How can i fix this please ?

Seems to be a more general problem in 13.2:
https://bugzilla.opensuse.org/show_bug.cgi?id=901916
And others have asked similar things in the openSUSE forums.

Anyway, this doesn't seem to be specific at all to Plasma5.

I do have the same problem on one of my systems (fresh installation of 13.1 and upgraded to 13.2) even in KDE4, whereas NumLock is turned on as expected on my other system which I upgrade since 11 years (SuSE 8.1).
I have not yet found out what the difference is, but I'm investigating (a bit difficult, since the systems are 50 km apart... ). I haven't tried the settings in KDE yet though, so I don't know whether this works or not here. But others have reported it not to work.

You should be able to turn on NumLock by running "numlockx on". Maybe run that in a login script, see Systemsettings->Startup and Shutdown->Autostart as a workaround.

Hi, It's great to know that it looks like it's not coming from kde.

manchette wrote:Hi, It's great to know that it looks like it's not coming from kde.

Well, that bug is about configuring NumLock system-wide in /etc/sysconfig/keyboard.

I tried KDE's settings now, and it works as expected in KDE4.
But in Plasma5 this setting has no effect.
So it seems that's a regression or missing feature in Plasma5, the setting doesn't seem to be applied on login.

Btw, a workaround to fix the system-wide setting is to add the config file /etc/sysconfig/keyboard to the initrd manually (and set KBD_NUMLOCK there as desired). You can do this by running dracut with the -I switch.
Something like this:

Code: Select all

sudo dracut -I /etc/sysconfig/keyboard --force --force-drivers "pata_via sata_via ata_generic"

You can see the parameters normally used for dracut on your system in /var/log/YaST2/mkinitrd.log (the first line).

wolfi323 wrote:But in Plasma5 this setting has no effect.
So it seems that's a regression or missing feature in Plasma5, the setting doesn't seem to be applied on login.

There's even a bug report about that already:
https://bugs.kde.org/show_bug.cgi?id=339643

hi,
i used a shell script for "numlockx on" as you sugested, it's ok like that. It should be started using the "pre kde startup option.
Thanks