1. is known and fixed in sync thanks to @folcred
2. I did once turn this off. However, not sure about making it default. What actually happens when it times out? Does it do your command or just exit? Reducing the time I think would be a good option/compromise
3. I kinda grew to like single click. Having it double click seems more desirable for people who multi-desktop (why would you use anything else?)
4. I thought splash screen was off by default, it's meant to be for that reason

Only one that could possibly change is qbittorrent vs ktorrent. I've not used either to be honest, so have no opinion at this stage.

Timer for (2) can be reduced to 5 seconds and be good enough. If that feels too fast, maybe 10. Need more votes.

As for (3), its just years and years and years of muscle memory. Also, every other Solus edition behaves otherwise.

Splash screen indeed showed up on second boot, not first. IIRC, it was off in validation ISO too, so was kinda surprised it showed up.

I haven't seen any splash screen show up in my install, nor in any of the VM's I spun up today. Kinda weird you're seeing it @whatever.

Dolphin has the little "+" and "-" icons that show up when you hover over folders/files to select them without opening. You can also use the CTRL key with the mouse to select items. I actually prefer single-click I'm old and use to it from years of KDE use. Plus I'm just old and have a hard time double-clicking anything. I set single click in GTK desktops too. It can be switched in Settings, but I don't know if I'd make it default. Maybe once it goes public and gets a lot more user feedback it can be decided then.

The problem with character rendering in Dolphin is a bug with how 17.12 apps and the KDE frameworks set the default language. I found a temporary workaround for the whole Plasma system @sunnyflunk, it's in another task. I also linked the phabricator page where it's been recently fixed, but I don't know if it's been pushed to the frameworks master yet.

This is the task with the workaround and link in it: https://dev.solus-project.com/T5694

Okay, I went digging, and splash screen is ON. I am positive I did not do that manually. Can we confirm that? Also font issue in dolphin is upstream issue then?

Well, I have my main install on metal, on a spare drive, and three VM's installed for tests, and it's not set on any of them. I have no idea what would cause it to randomly come on either. Maybe something else being set/unset triggered it?

Yeah, the font issue is an upstream bug. Somewhere along the line they changed the syntax for identifying the overall language setting, but didn't make the needed change in the frameworks to make use of it, to properly identify the language the user selected. I would think the fix will be in the next frameworks release. For now it's pretty easy to work around by manually changing a couple files and restarting.

Maybe I need more coffee before I setup a new install. Alright, edited description to mirror this info.

This article by one of the Plasma devs is an honest look at what they known they need to fix in Plasma. A big one is GHNS, which suffers from the same problems Gnome's extensions do. Many are outdated, lots are badly made, etc. It's worthwhile reading, as it's gives just some of the bigger issues facing Plasma, and as far as Solus is concerned, shows what is upstream issues and nothing to do with Solus' spin.

Redshift is again an upstream bug, as mentioned here. Changes to the pre-5.12 series broke something in it.

Desktop cube is likely a driver or some other setting mismatch. I enabled it to test, and it works fine here. I have an AMD Rx-550 running the open source driver. I don't game so it's all I need and doesn't give me trouble.

I have HD3000. Driver trouble is unheard of for me. But anyhow, where can I look for help about it?

Can you confirm dolphin services and external widgets?

I'll edit for redshift.

Sunnyflunk may have already patched your desktop cube problem here. If you read the comments from the dev in the patch, it's sounds very much like what you're describing @whatever. Especially if you have icons on the desktop (the current default setting) and are using the mouse to move the cube. I would suggest to see if it's still a problem after the next sync.

The problems with GHNS is pretty well known, it's been around since the early Plasma 4 days. A quick googling will bring back thousands of examples like this one I just grabbed from the first page of results. They acknowledge the problem in the article I linked earlier. Basically, when a service or widget is installed, it's suppose to create it's own folder in a default location and then trigger a refresh so the add widget panel or Dolphin knows it's there. But that doesn't always happen. Usually it's caused by a badly-written widget/service, or some change in Qt that wasn't updated by the widget/service author. Same problem Gnome has always had with extensions.

If it installed correctly, sometimes you can make it show up by closing and reopening Dolphin in the case of a service. Sometimes restarting Plasma will do the same for a widget. Not always, especially if it didn't install where it was suppose to, or not at all. Thing is, it's an upstream bug. There's little that can be done about it until they find a way of getting all the widget/service devs to follow some standard protocol or practice.

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.

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

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

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 :-)

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#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.

of course, you are absolutely right, i did not think about the refresh rate.

After the updates synced this morning, I created a new VM to test. Installed the updates before attempting to change anything, then rebooted the VM to ensure the updates were applied.

• Languages now work correctly, user settings are being written to the configs and applied on next login.
• The default user account now shows up in the User Manager
• Screen artifacts when using the desktop cube appear to be gone.

The only issue I found was when changing the language, if you don't click on "Apply" and close or change the dialog to something else, you're not asked if you want to apply the change, as in most dialogs. The change just doesn't get applied.

@folcred

• Dolphin still has artifacts for me
• Screen artifact for desktop cube is still here, after update and reboot.

2. https://github.com/KDE/kde-workspace/blob/257b997132217fd73a1b3be14db49735b64235e7/plasma-workspace/ksmserver/themes/default/main.qml#L163 to patch. At the moment I'm thinking 10.

3. No plan to change at this time,
4. Unlikely to happen. It's not trying to be consistent with other versions. The versions bring different experiences and functions.

10s is fine.

I like default icons already, this should be one less change for me.

As for single click select, you're the decision maker. I really have no idea how many people would prefer that, but I guess its just one toggle I can always flip on install.

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

but mostly it works fine for me, i am really exited for solus 4.
one questien left maybe would you say it is better to reinstall when solus 4 get released or just update the pre release

I am pretty busy atm, I'll see if I can find time to test these out.

As for shutdown times, I agree. Even I'm resorting to sudo poweroff because 30s is too long. But, @sunnyflunk is thinking to reduce it down to 10. Personally, I'd be happier with 5, because there are loads of ways to make it stop, even in 5s, but only one way to get it get it faster, which is by clinking that exact button.

Just my 2c.

As for (3), its just years and years and years of muscle memory. Also, every other Solus edition behaves otherwise.

Just to chime in on this one, I plan on using Nautilus' single-click behavior as a default for Solus GNOME for Solus 4. It's something I've used for years and frankly I don't understand the necessity for multiple clicks (most people using selection for a specific folder are using right click anyways, or drag-selection for selecting multiple items).

@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.

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.

yes, i choose the Konqui picture from the gallery, after chossing the picture it is displayed in the system settings, but after clicking on apply, the picture is back to the default.

all users may connect to this network did not fix the problem, but
store password for all users did fix it
but im not shure what the problem exactly is, the password is now stored unencrypted, so maybe it is a problem with the encryption? or is it more of of user management problem?

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.

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.

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.

the user icon stuff:
the permissions are all right,
the link is createt, but the .face file is not,
i got this message from the terminal:
QDBusConnection: name 'org.freedesktop.Accounts' had owner '' but we thought it was ':1.106'
But this seems to be a problem only for my main user, i created a new one and the new user did not have this problem.
EDIT:
the new user works better, the picture is shown in the system settings, but nowhere else, there was no .face file created and no .face.icon link.
i copied the icon i wanted from the gallery to my /home and named it .face, now it is shown everywhere. but after choosing an other one in system settings and applying it, the .face file get deleted and the default icon is back.
BUT i think nobody will really need this feature, so it should not be a problem if it is not working 100% for everybody ;-)

the wifi stuff:
security is not a big problem for me on this machine i installed solus plasma on, so the optin is working fine for me at least.i will google this topic next weekend :)

the icon problem:
thanks for the workaround, but i personally dont use desktop icons, so ne problem for me, i just wanted to point it out because i know other people will use desktop icons.

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 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.

Both Problems, the user icon settings one and the double context menu in folder view are fixed since the 5.12 update.

Sorry to interfer this thread, but I do not want to create a new issue just to report some missing icons like vscode's one.

@whatever, I had the same problem with VLC, both full-screen and windowed. Looking for a reason, I found VLC isn't detecting the correct video decoder. The default "Automatic" doesn't seem to detect it. In my case (AMD GPU) setting it to "vdpau" in both Video > Output and Input/Codecs > Hardware-accelerated decoding fixed the problem. I believe with Intel one needs to use va-api or some such.

Why it detects the correct driver in Gnome and not Plasma, I just don't know. Oddly it wasn't a problem with the last version of VLC, so I'm inclined to think something changed with it, but what I have no idea.

@mrkucho, I checked the package for VSCode, and there's no icon in it! I looked for it on VSCode's github, can't find it there either! I have a feeling someone goofed on their github. For now, you can grab the latest icon here. Just place it in /usr/share/icons and it should show up in the menu, etc.

@folcred va-api isn't listed in Video > Output. I also set Hardware-accelerated decoding to va-api and tried matching with every option under Video > Output, no dice. I have HD3000 integrated graphics, which should be fine, because it has been so far. This is with latest update with rebuilt VLC this morning. Anything else I can try?

Are you quitting and restarting VLC after switching outputs? Most settings won't take effect until it's restarted.

You can install the driver from the repos @whatever, but I really don't know why you should have to, or even whether it will solve the problem. If it's working under Gnome (I'm assuming you have both DE's installed) it should work under Plasma. Where the problem originates (VLC?, Plasma?, kwin?, SDDM?, codecs?) is going to be a bugger to find. Just look at the VLC changelog! My guess is either VLC or kwin introduced an incompatibility with the latest versions, but so far I've been unable to find what's causing it.

In my case I've always installed vdpau, it drastically cuts back on how much my CPUs are worked during video playback. In yours you've never needed a driver before, and still don't under Gnome, so I don't see installing one as actually fixing anything, more like a band-aid.

In T5704#104549, @mrkucho wrote:

Sorry to interfer this thread, but I do not want to create a new issue just to report some missing icons like vscode's one.

vscode now has an icon

That's the new icon? I saw that in their GitHub, thought "No, that can't be the right icon, doesn't look anything like it."

The older one is certainly a lot nicer. Believe their art department may want to rethink that one.

That's the new icon?

That's the icon for the open source version. Can't ship Microsoft's official logo for VS Code (most icon themes have a Visual Studio Code icon, fortunately, just not the KDE ones).

Suggestion: Add the power button widget to the panel, next to the clock (right side?), and change the default leave option to turn off the computer. I feel this adds a slightly neater way of shutting down the computer.

Currently to add the power button widget I do the following: click panel settings > add widgets > select lock / logout > drag and drop onto panel next to clock > right click icon > unselect lock, and it now just displays the power icon. Then change the default leave (system settings > startup and shutdown > desktop session > default leave > turn off computer).

In T5704#104837, @sunnyflunk wrote:

In T5704#104549, @mrkucho wrote:

Sorry to interfer this thread, but I do not want to create a new issue just to report some missing icons like vscode's one.

vscode now has an icon

Still missing here. I installed it for first time on this setup, all updated, and no icon still.

Still missing here. I installed it for first time on this setup, all updated, and no icon still.

Because we haven't synced to stable. Things go to unstable first. Wait until our Friday sync.

12 (the keyboard shortcuts):

I like the ALT Key as my window-management-key, here some examples:
alt + b = hide window borders
alt + numpad 4 = pin window to left side
alt + numpad 1 = pin window to lower left side
alt + numpad 5 = maximize window
and so on..

i don't know if other people do that or like that.

What's up with the AppIndicators? It doesn't display an Indicator for Qbittorrent, OBS, VLC and many more programs? Is there some library missing or something... It works on KDE Neon

In T5704#105964, @MaCroX95 wrote:

What's up with the AppIndicators? It doesn't display an Indicator for Qbittorrent, OBS, VLC and many more programs? Is there some library missing or something... It works on KDE Neon

By default it doesn't show all tray icons, qbittorrent and vlc show up fine for me, but they are hidden by default. However, the system tray seems to be broken after some action. Was this comparison done on 5.12?

In T5704#106009, @sunnyflunk wrote:

In T5704#105964, @MaCroX95 wrote:

What's up with the AppIndicators? It doesn't display an Indicator for Qbittorrent, OBS, VLC and many more programs? Is there some library missing or something... It works on KDE Neon

By default it doesn't show all tray icons, qbittorrent and vlc show up fine for me, but they are hidden by default. However, the system tray seems to be broken after some action. Was this comparison done on 5.12?

Can you unhide the hidden icons, for some reason it doesn't show the entries for myself so QBitTorrent icon stays hidden and theres's no way I can unhide it.

In T5704#106018, @MaCroX95 wrote:

In T5704#106009, @sunnyflunk wrote:

In T5704#105964, @MaCroX95 wrote:

What's up with the AppIndicators? It doesn't display an Indicator for Qbittorrent, OBS, VLC and many more programs? Is there some library missing or something... It works on KDE Neon

By default it doesn't show all tray icons, qbittorrent and vlc show up fine for me, but they are hidden by default. However, the system tray seems to be broken after some action. Was this comparison done on 5.12?

Can you unhide the hidden icons, for some reason it doesn't show the entries for myself so QBitTorrent icon stays hidden and theres's no way I can unhide it.

That's kinda what I was talking about (it seems little to do with vlc, qbittorrent)...On a clean boot, you can see the entries and VLC will show up, then it enters this broken state where it won't show new systray icons till you remove/readd the widget. The blank entries seems the easiest way to tell that it's in that broken state. I need a comparison of apples with apples. If you compare to another distro that wasn't running 5.12, then that's not telling much (it certainly didn't used to do this).

In T5704#105962, @domacs wrote:

12 (the keyboard shortcuts):

I like the ALT Key as my window-management-key, here some examples:
alt + b = hide window borders
alt + numpad 4 = pin window to left side
alt + numpad 1 = pin window to lower left side
alt + numpad 5 = maximize window
and so on..

i don't know if other people do that or like that.

I went for

alt + up/down = max/min-imize. It clashes with desktop zoom control, but I didn't have use for that so that sufficed.

Also,

ctrl + alt + left/right = previous/next desktop

ctrl + meta + left/right = move current window to previous/next desktop

There are quite a few more, but my keyboard habit are a bit weird, so I'd rather others pitched in.

@JoshStrobl , vscode icon is present now, but doesn't show up on titlebar, there it still has generic X11 icon.

In T5704#106038, @whatever wrote:

In T5704#105962, @domacs wrote:

12 (the keyboard shortcuts):

I like the ALT Key as my window-management-key, here some examples:
alt + b = hide window borders
alt + numpad 4 = pin window to left side
alt + numpad 1 = pin window to lower left side
alt + numpad 5 = maximize window
and so on..

i don't know if other people do that or like that.

I went for

alt + up/down = max/min-imize. It clashes with desktop zoom control, but I didn't have use for that so that sufficed.

Also,

ctrl + alt + left/right = previous/next desktop

ctrl + meta + left/right = move current window to previous/next desktop

There are quite a few more, but my keyboard habit are a bit weird, so I'd rather others pitched in.

If there aren't generic keys that one would expect, then how does one discover what they are? It would make sense to use Meta-Left/Right (as is common) however, these keys are already assigned in Plasma.

In T5704#106037, @sunnyflunk wrote:

That's kinda what I was talking about (it seems little to do with vlc, qbittorrent)...On a clean boot, you can see the entries and VLC will show up, then it enters this broken state where it won't show new systray icons till you remove/readd the widget. The blank entries seems the easiest way to tell that it's in that broken state. I need a comparison of apples with apples. If you compare to another distro that wasn't running 5.12, then that's not telling much (it certainly didn't used to do this).

A quick look at the tracker and I could find these two which seemed to be reproducible when it's in that state:

https://bugs.kde.org/show_bug.cgi?id=390106
https://bugs.kde.org/show_bug.cgi?id=390163

In T5704#106041, @sunnyflunk wrote:

In T5704#106037, @sunnyflunk wrote:

That's kinda what I was talking about (it seems little to do with vlc, qbittorrent)...On a clean boot, you can see the entries and VLC will show up, then it enters this broken state where it won't show new systray icons till you remove/readd the widget. The blank entries seems the easiest way to tell that it's in that broken state. I need a comparison of apples with apples. If you compare to another distro that wasn't running 5.12, then that's not telling much (it certainly didn't used to do this).

A quick look at the tracker and I could find these two which seemed to be reproducible when it's in that state:

https://bugs.kde.org/show_bug.cgi?id=390106
https://bugs.kde.org/show_bug.cgi?id=390163

Sorry man, I can't give you apples to apples comparrison because I've been using Solus KDE ISO since it was already on 5.12, but I can tell you that behavior is really strange. When I first boot up the PC and go to system tray settings I can edit the entries, but when I once close the systray settings it seems to lose the entries and upon closing the applications appindicators get lost and when I open the tray settings again it shows 0 entries. It might be a bug with KDE, I'm not sure... It's kinda big issue for us who use appindicators a lot but I have Plasma ISO on my ultrabook, on my desktop PC I'm using the Gnome ISO because Nvidia doesn't play well with KDE Plasma so I can wait for the fix no problem, and also help you troubleshoot the issue. If there's anything I can help with please let me know!

@sunnyflunk windows uses

ctr + meta +left/right

Gnome uses

ctr + alt +left/right for desktop switching.

Even then, plasma on Solus has only 1 desktop by default, and user has to opt for more manually. I am not certain whether this is optimal, but we need more votes on it.

As for window min/max-imize, I'm almost sure alt/meta + up/down can be considered standard. Again, more people need to see and voice their preferences.

Probably a survey of sorts for all kinds of small kinks to see what the majority of would be plasma Solus users think?

In T5704#106041, @sunnyflunk wrote:

In T5704#106037, @sunnyflunk wrote:

That's kinda what I was talking about (it seems little to do with vlc, qbittorrent)...On a clean boot, you can see the entries and VLC will show up, then it enters this broken state where it won't show new systray icons till you remove/readd the widget. The blank entries seems the easiest way to tell that it's in that broken state. I need a comparison of apples with apples. If you compare to another distro that wasn't running 5.12, then that's not telling much (it certainly didn't used to do this).

A quick look at the tracker and I could find these two which seemed to be reproducible when it's in that state:

https://bugs.kde.org/show_bug.cgi?id=390106
https://bugs.kde.org/show_bug.cgi?id=390163

I dunno man, these don't look like it. Besides I can confirm this is new with 5.12. But, it's not perfectly reproducible. I have only seen this happen once, and a logout fixed that.

In T5704#106075, @whatever wrote:

In T5704#106041, @sunnyflunk wrote:

In T5704#106037, @sunnyflunk wrote:

That's kinda what I was talking about (it seems little to do with vlc, qbittorrent)...On a clean boot, you can see the entries and VLC will show up, then it enters this broken state where it won't show new systray icons till you remove/readd the widget. The blank entries seems the easiest way to tell that it's in that broken state. I need a comparison of apples with apples. If you compare to another distro that wasn't running 5.12, then that's not telling much (it certainly didn't used to do this).

A quick look at the tracker and I could find these two which seemed to be reproducible when it's in that state:

https://bugs.kde.org/show_bug.cgi?id=390106
https://bugs.kde.org/show_bug.cgi?id=390163

I dunno man, these don't look like it. Besides I can confirm this is new with 5.12. But, it's not perfectly reproducible. I have only seen this happen once, and a logout fixed that.

They are reproducable, and I can confirm that same happens on my dad's KDE Neon w Plasma 5.12... So it's definitely not a Solus issue, it has something to do with the new Plasma.

In T5704#106081, @MaCroX95 wrote:

They are reproducable, and I can confirm that same happens on my dad's KDE Neon w Plasma 5.12... So it's definitely not a Solus issue, it has something to do with the new Plasma.

I heard some chatter on the IRC logs today about upping the priority of https://bugs.kde.org/show_bug.cgi?id=383828 which may be the cause (the other bugs being the symptons), so I'll follow and backport.

In T5704#106194, @sunnyflunk wrote:

In T5704#106081, @MaCroX95 wrote:

They are reproducable, and I can confirm that same happens on my dad's KDE Neon w Plasma 5.12... So it's definitely not a Solus issue, it has something to do with the new Plasma.

I heard some chatter on the IRC logs today about upping the priority of https://bugs.kde.org/show_bug.cgi?id=383828 which may be the cause (the other bugs being the symptons), so I'll follow and backport.

Great to hear that the bug is being worked on :)

There is also a bug where Baloo file indexer keeps crashing, which I don't know if it's Solus or Plasma related as well.

Here is the screenshot of the Baloo error that I was talking about :) It's quite frequent.

In T5704#106249, @MaCroX95 wrote:

Here is the screenshot of the Baloo error that I was talking about :) It's quite frequent.

Putting in baloo and crash in the bug tracker brought up a number of hits, particularly for crashing on startup if you want to take a look. I'm not sure if they cover what you are experiencing

I've not been able to reproduce the crash, but doing some testing in a VM have had baloo seem to go crazy and never stop indexing. Found that it seems to be choking on hidden folders. I believe it's trying to index things like .cache, .config, .local, .mozilla etc., and any .git folders a user might have. It hasn't happened on my daily-driver, and the only difference I found is I have that set to not index hidden folders. Adding the setting to baloofilerc and restarting it seems to cure it.

• In a terminal run balooctl disable.
• Delete the index in ~/.local/share/baloo.
• Edit ~/.config/baloofilerc and under the heading [General] add the line index hidden folders=false, then change the line first run=false to first run=true, then save.
• In the terminal run balooctl enable.

It restarts the indexer and should rebuild the index, minus any hidden folders. That seems to have cured it from running amok in my test VMs, but I don't know if it will cure the crashing problem, I haven't been able to reproduce that. Someone else will have to test it and see.

I've been using the Patreon KDE ISO for pver a week now and I've noticed two things which I didn't see here.
One is that I cannot add a panel to the second monitor, if I try it just goes to another position on the first screen.
The second is every time I insert a USB stick in, when it comes up on device notifier and I click on 'open with file manager' I get a popup saying:
"Error -- KIO Client
Malformed URL"

Then I click okay and it goes away, if I go to Device notifier and click 'open with file manager' this time it opens with no error. This happens with different memory sticks and I tested ISO on an old laptop before putting it on my main machine and got the same error.

Both of those issues are upstream bugs in Plasma @padraig. And sadly, they're both quite old ones at that.

There's a possible workaround for the monitor issue, which is explained in this video. It's an older video (2016), and I don't have dual monitors to test, but it should still work. I imagine this one has a real pain to sort out, as it doesn't seem to affect all dual monitor users. It's very random.

The second one is also upstream, and also quite old. The latest report about it I could find is here. It was marked duplicate of another report, which was from 2016 and apparently still not resolved. I can confirm it does the same for me, the workaround for it I use is simply close the dialog, then click on the device manager icon in the tray, select the USB and 'open in filemanager' again. Then it works.

Ah right, sorry, I should have checked that first. I used KDE Neon for a while until about a year ago and didn't remember either of them, but at the time I didn't use a second monitor often. Hopefully they'll be resolved at some stage then.

In general I'm very happy with KDE on Solus anyway, not sure I'll stick with it as I like Budgie too but I've been using KDE since about 2011 so wanted to run it again for a while!

My battery widget is stuck to "1:57 Remaining" . The % is correct, but the timer never changes.
Not sure when happened but I remember that this used to be ok.

Thank you for the amazing work on KDE and Solus!

I don't have a battery so I can't test this @Brandywine, is this the "Battery Time" widget from the kde store, or the built-in one from the system tray? IIRC the default one in the system tray doesn't show time, just percentage.

I can say that the one from the store is possibly broken. I see it hasn't been updated since August of last year, and both KDE's frameworks and Qt have had many changes since then. Chances are the mechanism it uses to calculate time has changed in the underlying libraries and unless it gets updated it won't work anymore. It's a problem both GNOME and Plasma have with extensions and widgets. If the authors don't keep up with core changes, they break.

Hello @folcred , I investigated and I can say that the bugged "battery widged" is, in fact, the system tray.

A picture is worth 1000 words :)

A picture is worth 1000 words :)

Yes it is. Unfortunately I'm on a desktop, so don't have a battery and can't try to duplicate/troubleshoot it. A search of KDE's bugtracker however found this which is likely relevant.

It could be something with how Solus handles power management, or it could be something with how the KDE frameworks interpret it. I think this is going to be one of those things where we'll need to see how many others report it, and whether it's distro agnostic (and a problem with Plasma) or specific to Solus.

When I start a new session, KDE does not remember the windows that were open despite "Restore previous session" being selected in System Settings -> Startup and Shutdown -> Desktop Session.
Reading a little about this, it seems I have no ~/.config/session/ directory. I can create this but it makes no difference. Does anyone else have this issue?

I have not had this issue with other distributions, however, the machine I installed Solus KDE on had previously been running a Kubuntu LTS with KDE 4 on it, so it's possible I need to remove some other configuration files from the home directory.

@padraig KDE4 and Plasma 5 do not like each other at all. This is actually how I got involved with Kubuntu as I was seeking help trying to restore my desktop after moving to Plasma 5. Basically I would suggest you create a new user, let Plasma create all its files and move anything else you need over to it. That was the only workable upgrade path at the time (14.04 LTS > 14.10+)

@clivejo Thanks, I'll try that so. Yeah I knew they didn't really like each other but I hoped removing the ~/.kde directory would be enough.

@sunnyflunk could you add the "minimize all apps" widget to right corner of the panel and/or add a global keyboard shortcut do do the same? I know there's CTRL+F12 but that's not "minimizing", it's a "show temporarily the desktop" feature which is the macOS behavior. I'd prefer the Windows behavior. Windows minimizes all apps with META+D, it's pretty handy imho.

Also, Firefox detects DejaVu as the default font, which is clearly not, it's Noto Sans.

For about the third time after an update Dolphin will give the following error on opening:
Unable to create io-slave. klauncher said: Error loading '/usr/lib64/qt5/plugins/kf5/kio/file.so'.

This also happens if I got to open a file with Gwenview, Okular, etc. Previously I resolved this by rebooting which I have not done yet this time, however ideally I would be able to update without rebooting.

Does this happen anybody else and is there a better way to resolve it than rebooting?