shure, sorry
https://bugs.kde.org/show_bug.cgi?id=394180
im not 100% shure that this will work with nvidia, but i think it will

5.13 maybe will fix this issue, it seems that there was a bug in kde that force dpi in system settings did now work, ist will be fixed in 5.13.

I can confirm the small text, but i prefer the smaller text over the original one xD

12 (the keyboard shortcuts):

indeed, the white frame is gone in 5.12

In T5701#104446, @ikey wrote:

Proof I actually tested this :P

Sorry bout that guys.

In T5704#104103, @folcred wrote:

Don't know what to make of the user icon problem, I simply can't reproduce it. In my daily and the 3 different VMs I have for testing, they all work as expected. Guess we'll have to wait and see if anyone else can duplicate it.

The folder view problem I think may be an upstream one. In the journal I get a warning about not having a containment. I believe all widgets have to have a container, something they're inside of. That way things like keystrokes and mouse actions are localized to them, and only passed through if the event isn't used by them. With the folder view it seems like the mouse actions are being fed to the desktop first, then the widget icons. To me that smacks of something in the code rather than some setting somewhere.

Tried searching for a bug report, but couldn't find anything relevant. I suppose we'll have to see what it's like when sunnyflunk gets all the 5.12 updates done, see if it's still there.

In T5718#104189, @folcred wrote:

I thought you likely would have chosen the keyboard during install, had to ask to be sure.

Looks like we have an installer bug. I'll have to try and get with @ikey and see what he thinks, I believe the installation toolkit is his domain.

Thanks for the information @domacs, it's a big help.

Edit: I should have checked first @domacs, it is a known bug, listed under "Unbreak Now!", so it's a priority one the team is aware of.

In T5718#104107, @folcred wrote:

I'm a bit surprised it wasn't set when you did the install. Did you choose the German keyboard then?

There's a couple of options. If you run localectl list-keymaps | grep de in a terminal, it will give you a list of all the German keymaps the system has installed. Pick the one you want from the list and then:

• To make it temporary while you're in a tty - loadkeys <keymap>
• To make it permanent - sudo localectl set-keymap --no-convert <keymap>. The "--no-convert" bit keeps it from trying to change the X11 keymap too.

You'll have to restart the system for the permanent one to take effect. It creates a file /etc/vconsole.conf that gets read by systemd on boot.

In T5718#104104, @folcred wrote:

What does it say in /etc/locale.conf?

the gui problem is fixed since the last update, but in tty (strg + shift + f2 for example) the keyboard is still us

In T5704#104065, @folcred wrote:

On the user image issue, can you check permissions for your /home/<username> folder? When you create a user image, it gets stored in your home folder as a file named .face and a symlink to it named .face.icon. Perhaps the scm is having trouble writing to it?

With the wifi issue, that was going to be my next suggestion, storing the password. The problem is, the passwords are stored in the user's kwallet. Normally with login, kwallet is opened (if it's set that way) and then networkmanager is started. With autologin the opposite seems to happen, networkmanager is started first, and because kwallet hasn't been started yet, there's no password. Once the desktop is fully loaded if you click on networkmanager it will work because everything is then loaded.

Storing the password allows the system to log into the network instead of the user, which means the network is already up when the user starts the desktop. Not the most secure way of connecting, but it's the price paid for autologin. If you're the only user on the machine it shouldn't be too much of a risk, but it's certainly not ideal. There's been a lot of discussion (read 'argument') about this, with a lot of finger-pointing. If you do a little googling you'll see what I mean. I would think it should be as easy a fix as making sure kwallet starts first and is fully loaded before staring the network manager, but I'd have to do some digging to find out if that's even possible. Lots of bits and pieces involved, kwallet, networkmanager, pam, logind, etc..

As to the icon problem, yeah it does it here too. For now I'd say change the button to show the Plasma desktop from right-click to middle-click, unless you use the middle-click paste a lot. I'll see what I can find about that this evening.

i found something else, i installed steam an right click on the desktop icon opens 2 menus, the context menu for the icon and the plasma desktop menu and they overlay each other, i have this behavior for folders too.

In T5704#104022, @folcred wrote:

@domacs, on your item 2, have you tried using any of the default images from the gallery? I'm not able to reproduce the problem here, so I'd like to know what steps you've tried. If you're using an image, have you selected an area in it to use? What format is the image, .jpg, .png?

With item 3, do you have All users may connect to this network activated in the general settings? I can't reproduce because I don't have wifi, but there's some pretty standard stuff to look for that might help. Figure to start at the basics and then work from there.

I have 3 issues left, nothing major and i am not shure that all of them are special to solus kde.

1. shutdown needs really long, when shutting down with the plasma options, shuttuing down with terminal is normal speed
2. i cant change the user icon in the setting, it asks for the password, but it always shows the default
3. this is a very special one i think, i have enabled auto login and kde wallet without a password and every time on bootup, the first automatic connect to a wifi network is not working, the second try works and manually choosing a network works too

In T5701#103774, @sunnyflunk wrote:

In T5701#103773, @domacs wrote:

should it work now with the last update?

No, I was awaiting confirmation that my summary of the issue was the issue being faced (though I see I didn't phrase it as a question with a question mark).

should it work now with the last update?

In T5704#103387, @sunnyflunk wrote:

In T5704#103284, @domacs wrote:

You are right, it is out of the box better then in other distros, but for example the k menu, i think the animation is still slow, but maybe it is just my feeling und the speed schouldnt be too fast in the defaults, at least we have th option to change it to our preference :-)

Basically as the default, (which really needs to based on 60Hz as the most common setup), increasing the animation speed one notch makes it lose it's slide (which to me is a key part of the animation). If you have a high Hz monitor, then speeding it up would still look good, but on 60Hz I think this is best. I could tweak it slightly, I just chose the speed in the middle of the two around it.

In T5704#103283, @sunnyflunk wrote:

In T5704#103279, @domacs wrote:

suggestion:

I don't know what other people think, but i always like speed up the animation speed in the compositor settings, i think plasma feeld more smooth this way.

They are faster than default, but too fast and the animation isn't smooth (looks really bad and you're better off making them instant). I thought I'd hit the timing right with what the default is set to

I don't know what other people think, but i always like speed up the animation speed in the compositor settings, i think plasma feeld more smooth this way.

Okay, i understand that this is part of early acess, i just wanted to point it out, that it won't be forgotten for the final iso :-)
thank you for your hard work!

i have the same problem, i installed the nvidia driver with the doflicky tool and was left with a black screen, the only thing i tried was nvidia-xconfig, but this dit not help, i was left with a flickering curder on a black screen.