This tag is for tasks that do lack an assigned project.
Submitted D10048 to fix the missing translation files.
Just a wild guess, what GPU and drivers are you using. That could explain why newest Proton doesn't work, maybe try beta or stable instead if you are on Nvidia?
Fri, Nov 27
You are welcome!
Glad I was able to help.
Thank you so much for all the help, that was it! Turns out the GitHub CLI (gh) completions I was loading in my .bashrc were malformed, causing the file to be unable to load.
From the lightdm.log:
[+51.51s] DEBUG: Session pid=1425: Logging to .xsession-errors [+51.79s] DEBUG: Activating VT 7 [+51.79s] DEBUG: Activating login1 session 1 [+51.79s] DEBUG: Seat seat0 changes active session to [+51.79s] DEBUG: Seat seat0 changes active session to 1 [+51.79s] DEBUG: Session 1 is already active [+61.38s] DEBUG: Session pid=1425: Exited with return value 2
The last line here indicates that something went wrong with the process with pid=1425.
Can you check if ~/.xsession-errors file has anything in it?
Thu, Nov 26
Oh, you're using Flatpak Steam? Maybe try the Solus dist of Steam and see if that changes results.
I did some additional testing with GloriousEggroll's custom Proton builds and found:
Works on my machine (Proton 5.13-2). 5.13-1 didn't work on my system at first, but that turned out to be an issue with pressure-vessel. Maybe open an issue on the pressure vessel github repo?
Just finished trying to install the latest lts kernel and corresponding NVIDIA drivers to see if it would make a difference, but the exact same problem happens regardless.
I've had similar issues when installing Solus on one of my machines a few months ago. With a wired connection instead of Wifi but, as confirmed on IRC, the cause was the same:
The installer names the machine solus but later the local DHCP server suggest another name. Unfortunately the installer's DHCP client accepts that name (and renames the host).
But as the magic cookie is linked to the hostname, renaming the machine prevents starting a new graphical windows. Already running ones are not affected.
I'm not too sure what I'm looking for, but there don't seem to be any errors. The only one that jumped out to me was an xkbcomp error in the X server logs, but even that one it says is non-fatal. I've attached all the logs I found in /var/log/lightdm (minus the ones suffixed with .old).
I installed Solus on a laptop who had the issue.
At first login on Budgie, I connected to a network and the issue didn't happen.
Is it maybe worth installing the lts kernels, uninstalling all my old NVIDIA drivers and installing the latest lts ones?
You would also need to install linux-lts and boot into that kernel to try.
Wed, Nov 25
@palto42 Given there has been an update to libcloudproviders and there's been considerable amount of time for it to mature, I'm going to give the cloudproviders support a shot, starting with R3740:f85e3b165ca0: Update to 3.0.3.
Yeah, all my drivers are for the current stream of kernels. Is it maybe worth installing the lts kernels, uninstalling all my old NVIDIA drivers and installing the latest lts ones?
You can also check if the installed drivers are for the -current kernel and not for -lts -- see table at https://getsol.us/articles/troubleshooting/boot-management/en/#installing-an-alternative-kernel.
At first, clr-boot-manager list-kernels listed both kernels I had installed (5.6.13-153 and 5.6.19-159), with the latest one selected. Unfortunately, even at that, I wasn't able to log in. I always returned right back to the login screen after a few seconds. (Also, as an aside, on my ESP I had a third kernel, something like 5.4.6. For some reason, that one wasn't showing up in the output of list-kernels).
So, the way I worked around the issue initially, before fixing boot partition, is I manually copied configs for the new kernel from /boot directory to boot partition and then changed the kernel via clr-boot-manager to the new one.
For me right now this is what clr-boot-manager list-kernels shows:
$ sudo clr-boot-manager list-kernels * com.solus-project.current.5.6.19-159 com.solus-project.current.5.6.19-158
with the current 159 release selected.
Can you check if the new kernel shows up on your system?
If it shows up but not selected (not marked with the *), then you can try to boot into it following https://getsol.us/articles/troubleshooting/general-troubleshooting/en/#boot-into-previous-kernel.
Then if it successfully boots and you can login into DE, you can switch permanently to this kernel by running:
sudo clr-boot-manager update
My understanding is that it switches default kernel to the currently booted one.
Thanks! I had exactly the same issues with my /boot directory being filled with the newer kernels, while my EFI partition had the outdated kernels.
Tue, Nov 24
Thanks for this! After running this command, it does turn out that there's a mismatch between the kernel versions. I am running 5.6.13-153, but the latest I have installed is 5.6.19-159.
I had similar issue a while ago after a kernel update (linux-current package).
In my case I was booting into wrong kernel, which I discovered by running following command from https://getsol.us/articles/troubleshooting/general-troubleshooting/en/#display-manager-wont-start
eopkg info linux-current | head -n2; uname -a
Can you check if the above command (or the one for linux-lts) shows two matching kernel versions?
Sun, Nov 22
Sat, Nov 21
Wed, Nov 18
Sun, Nov 15
Update: Here's a video that depicts the issue I experience (not my video, AMD hardware, very old release of Solus): Screen Tearing on Solus 22.214.171.124
GPU: AMD RX5700XT
Games = all. Even steam big picture flickers when the screen in Freesync mode. So maybe this is something that triggers when an app tries to take fullscreen. Compositor enabled/disabled changes nothing.
Sat, Nov 14
I'd rather not change those settings for everyone since it is more likely to break working systems than just fix yours.
If you can get me a PCI Id or a USB ID, I can check compatibility.
The only reason we ship netcat is for compatibility. I see no reason to package the BSD version when there are other applications like socat that are actively maintained and support what you are looking to do.
What GPU do you have? Which games? Freesync is not widely supported on Linux yet.
Thu, Nov 12
I think I only mentioned it to TraceyC on IRC, so I put it here as well: hplip-3.20.9 does work on Gentoo Linux.
I did what TraceyC suggested and installed older versions of hplip:
Wed, Nov 11
Please file a valid package update request in accordance with https://getsol.us/articles/packaging/request-a-package-update/en/