@tomocafe is this still an issue? It has been a long time since there was an update to this task, and there have been many updates since this issue was opened. Thanks.

@dlukes is this still an issue? It has been a long time since there was an update to this task, and there have been many updates since this issue was opened. Thanks.

Closing, as cups now runs as a systemd service

@solusitor , I just tested with a Budgie VM by setting my keyboard input to Russian and locking the session. At the unlock prompt, I was able to change input back to English and unlock the session. Can you confirm if this works for you or if the bug is still present? Thanks.

@dinhnamhihi, is this still an issue? It has been a long time since there was an update to this task, and there have been many updates since this issue was opened.

So, after rebooting with 1.11.37, Element connected just fine. Updated the system (including Element 1.11.38) and no problems since. Closing the task.

Note that we've changed the default umask to be slightly more strict since this issue was posted, yet the change has not affected ypkg and eopkg negatively as far as I can tell.

I cannot reproduce:

This is unfortunately not going to happen until ldc (the dlang compiler) supports llvm 16.

Oh, and can you update to the latest Element (1.11.38)?

A couple of things to look at:

@Staudey I collected the libraries you specified and tested megaglest. With the modified version of ftgl, everything is assembled without errors and works (megaglest). I have adjusted the library's IUP stack so that everything matches the necessary dependencies. In general, I have everything ready. I am ready to provide my library build scripts.

@jakes, does this issue still happen with an up to date Solus installation? There have been many updates and bug fixes since this issue was last updated.

The issue of the screen turning black when the mouse is in the lower part of the screen is Solus specific as far as I know. At least it doesn't ocur with Debian nor MX on my PC.
However it occur less often with kernel 6.3.12 than with previous ones (and never with 4.14).

@hyphens, does this issue still happen with an up to date Solus installation? There have been many updates and bug fixes since this issue was last updated.

@axaxs, does this issue still happen with an up to date Solus installation? There have been many updates and bug fixes since this issue was last updated.

Hey @joebonrichie , is this still an issue on your system?

In the time since this issue was opened, we have started the process of retiring the MATE edition. You can read about that and our reasoning on the announcement on our blog. I am closing this task.

I'm closing this out, due to its age, and the problem not being Solus specific (the problem also occurs on ubuntu). Please file a new issue if there is still a problem. Thanks for your understanding.

After the latest sync, the auto login doesn't work again. Should I open another ticket? The lightdm folder still exists and has a lightdm.conf in it with an autologin-user set

Resolved by fe6741231037

As announced in our Solus 4.4 blog post we are deprecating our MATE edition and so this issue will not be addressed.

As announced in our Solus 4.4 blog post we are deprecating our MATE edition and so this issue will not be addressed.

As announced in our Solus 4.4 blog post we are deprecating our MATE edition and so this issue will not be addressed.

GFU

Closing

Given that the Reddit API is now paid for, and that upstream targets flatpak, I am not going to be packaging this.

Resolved by D14275

I am no longer able to reproduce this in Budgie. I was able to create a user, with a password, and then delete the user.
Please file a new bug if this is an issue.

vba-m is always tested against newer wxwidgets typically, so it should be alright, next version that's upcoming also fixes a few things... Mainly wayland side

R3184:fc27e597df0f

Resolved R3184:27192528e526

R403:1689d0a69eca

Sorry, I'm 5 distros down the road since filing this bug report, I'm no longer on Solus, have no way to test it.

@cavaughan, is this still an issue? It has been a long time since there was an update to this task, and there have been many updates since this issue was opened.

@The_Linux_Gooroo, is this still an issue? It has been a long time since there was an update to this task, and there have been many updates since this issue was opened.

@ThanosApostolou, is this still an issue? It has been a long time since there was an update to this task, and there have been many updates since this issue was opened.

@joebonrichie , is this still an issue? I'm using fingerprints to unlock my Plasma session, but I don't know what the status of polkit is.

@BillDietrich - is this still happening for you? I am not able to reproduce the bug with Akregator 5.23.2.
Also installed on my system, xdg-desktop-portal-kde, version: 5.27.6

This problem hasn't been confirmed since Solus3. Closing.

Closing