This tag is for tasks that do lack an assigned project.
So the desktop would need use V-Sync when no full screen app is running, so that the screen is refreshing at it maximum rate?
Sun, Aug 2
I just want to add: I did a few tests back in May, and rechecked yesterday:
- autofs 5.1.3-3 as published initially (downloaded from https://packages.getsol.us/shannon/a/autofs/, no longer available) worked, and still works
- autofs 5.1.3-3 re-built from the tag on current main crashes
- 5.1.6-4, 5.1.3-5, 5.1.6-6 crash
Sat, Aug 1
Thu, Jul 30
I think this is an issue with clang as compiling it without clang=yes did not have this problem. Once I have verified this (with yet another build of this monster) I will submit a package upgrade that should resolve it.
Tue, Jul 28
I have updates to my issue. I think the culprit is KDE plasma's lock screen. I tried "loginctl unlock-sessions" and I was able to access my session. Is there any fix to this? It's not a big problem for me though I'd like for it to be fixed if possible.
Building 2.33 locally didn't resolve this, I'm still testing but as it takes so long to build it'll take me a while. I might ask the developer though as I can't see why this would be a Solus issue.
Sun, Jul 26
Oh, and in case anyone was wondering what happens if you remove perl. It actually looks pretty safe from a clean install:
The following script (based on the link by @hashhsah) works as a replacement for c_rehash:
alternatively, we could avoid the dependency on perl by replacing the call to c_hash in ssl.toml (usysconf) by a small bash script.
Fri, Jul 24
Thu, Jul 23
We don't need yet another task about this. File your stuff on the existing one...
Wed, Jul 22
You did something do your system, this wasn't caused by python-qtpy it's not possible. The error and view you are getting happens when sddm doesn't find its needed theme. This is the base sddm theme as a fallback you are seeing with the error info
excuse me but i think i couldn't express myself well since English is not my native language. what i want to say;
i am using plasma
i just want to install "PyQt5"
tried to install it in fresh-installed solus
this didn't happen in previous times( about 4 months ago and before)
what i think is "python-pyqt" package is now needs extra dependencies related to GTK packages
I do not recomend installing QT and GTK desktops in the same time and I'm not going to support it! As you can see installing Budgie conflicts or deleted some needed fails regarding Plasma (Breeze theme error), so uninstall Budgie and check for broken packages and reinstall them.
Tue, Jul 21
Mon, Jul 20
Thanks, but unfortunately none of it works.
Sun, Jul 19
A few days after I posted my previous reply, I decided to reinstall and the issue remains there. I've read that people with non-turing GPUs are not having issues and as I mentioned before previous glx version 440.100 didn't present the same problematic, so my 2 cents are on faulty NVIDIA drivers... but I know nothing, I'm no programmer but a curious linux user willing to learn something new everyday. Thanks for supporting my doubts.
I'm not using this OS but I'm having the same issue so hopefully it's okay if I post.
Sat, Jul 18
They found a few fixes for similar issues here, including forcing a language or running through Lutris https://forum.manjaro.org/t/rise-of-the-tomb-raider-does-not-launch/136930/18
Hope it helps
Fri, Jul 17
Hey, thanks for answering but I've tried with the three branches offered by the solus team (beta, developer and glx) and the result has been always the same. Something fishy must've happened with my installation and I don't really want to start from scratch. I run "sudo eopkg check" to verify no package was broken and no issues were found. I delete cache and remove orphan packages (dc and rmo) in hopes that some packages had corrupted and messed with something but nothing has changed. I really have no idea what might be happening. I have the plasma version BTW, could it be that plasma is still buggy?
Just in case you are interested:
nvidia-glx-driver-32bit is installed.
I don't have any other idea, but do you have 32bit driver installed? Depending on your driver version this is nvidia-glx-driver-32bit or nvidia-beta-driver-32bit
I do not have many steam games that run on Linux.
But Black Mesa runs without problems.
I just recently bought Rise of the Tomb Raider. It never started on Solus.
Is this the only Steam game that causes problems?
Has this game worked before for you?
Could you try launching whole Steam from the command line and launch the game from there?
I know Enigmail is depcrecated with version 78 of Thunderbird. However, I had the assumption to still be able to read my encrypted messages...
You could uninstall the current drivers and try with nvidia beta current or nvidia developer current.
Changing the settings in the Linux Steam Integration did not help.
Problem still occurs with the 450.57 drivers.
I don't know if older drivers do not have this issue.
I have a GTX 1660 super and it keeps happening! It works perfectly under windows 10. I now keep getting a black screen and cursor on screen when resuming from sleep. I do not know what might be happening. I guess I'll move to different binaries and try from there.
Hmm that is weird..i just updated to 450.57 version from today's sync..can't able to reproduce and works from my end !
NVIDIA GTX 970
Please file your issue upstream with the autofs devs then
No, package-management is eopkg. The current sol repo is not related to any current or future sol codebase. sol will be developed internally in a private Phab repo first, then when it is ready it will be made available as open source software and said repo will be publically accessible.
Hello, still the same issue exist even if it's marked as closed. It always exist while doing a fresh Solus installation and sometimes while installing packages on fresh installed, up-to-date Solus system (after general upgrade).
- What Desktop Environment are you using?
- Is your Solus installation on the unstable or stable branch?
- Is your system fully updated to the last sync (Friday 10th)?
Thu, Jul 16
Have you tried different options in "Linux Steam Integration", e.g. disable "Use native runtime"?
This appears to be fixed by a reboot.