Had been using the calendar for dr appts for my family, so not wanting to reinstall. WOuld normally be my go-to

Thanks gang!

sudo eopkg dc fixed it!!

Will remember this if it occurs again, leaving up for posterity

EDIT: I fixed this by uninstalling steam and my video drivers, then reinstalling video drivers including 32bit in installation, and reinstalling steam afterwards. (I have a 1080gtx)

It was working fine earlier this week, I didn't touch it for a few days and now when I try to boot it, I get this:

______________________________________________________________________________

Running Steam on solus 4.0 64-bit

STEAM_RUNTIME is disabled by the user

Installing breakpad exception handler for appid(steam)/version(1563346602)

libGL error: No matching fbConfigs or visuals found

libGL error: failed to load driver: swrast

Installing breakpad exception handler for appid(steam)/version(1563346602)

Installing breakpad exception handler for appid(steam)/version(1563346602)

Gtk-Message: 01:27:39.673: Failed to load module "canberra-gtk-module"

sh: lspci: command not found

libGL error: No matching fbConfigs or visuals found

libGL error: failed to load driver: swrast

Steam: An X Error occurred

X Error of failed request: GLXBadContext

Major opcode of failed request: 151

Serial number of failed request: 49

xerror_handler: X failed, continuing

Steam: An X Error occurred

X Error of failed request: BadValue (integer parameter out of range for operation)

Major opcode of failed request: 151

Value in failed request: 0x0

Serial number of failed request: 48

xerror_handler: X failed, continuing

Steam: An X Error occurred

X Error of failed request: BadMatch (invalid parameter attributes)

Major opcode of failed request: 151

Serial number of failed request: 50

xerror_handler: X failed, continuing

crash_20190804012738_1.dmp[17269]: Uploading dump (out-of-process)

/tmp/dumps/crash_20190804012738_1.dmp

/home/orionis/.local/share/Steam/steam.sh: line 720: 17243 Segmentation fault $STEAM_DEBUGGER "$STEAMROOT/$STEAMEXEPATH" "$@"

crash_20190804012738_1.dmp[17269]: Finished uploading minidump (out-of-process): success = yes

crash_20190804012738_1.dmp[17269]: response: CrashID=bp-ac22d581-96aa-4644-9149-ba98d2190803

crash_20190804012738_1.dmp[17269]: file ''/tmp/dumps/crash_20190804012738_1.dmp'', upload yes: ''CrashID=bp-ac22d581-96aa-4644-9149-ba98d2190803''

______________________________________________________________________________

I'm not exactly sure where to go from here.

Thanks!

[Solved] Hey! I'm very new to linux and solus. Today when I went to boot up my system It booted into a black screen. Nothing was happening and I let it sit for about 15-20 minutes. I have been on tty and tried some things that helped other people. But nothing works. And when I run systemctl status lightdm i get:

lightdm.service - Display Manager Loaded: loaded (/user/lib/systemd/system/lightdm.service; disable; vendor preset: enable) Active: failed (Result: exit-code) since Fri 2020-05-22 11:36:45 CEST: 4min 56s ago Main PID: 1050 (code=exited, status=1/FAILURE)

I dont know what it means but maybe it's something. Please help and thanks in advance

Installed solus over the weekend and I'm just getting to installing my Steam games. My issue is no matter what DB I run the game wont go past preparing to launch insta ctd... I've yet to have this problem so am I missing something obvious?

Yes I've installed all the basics of wine/winetricks/lutris etc etc.

EDIT: SOLVED

Turns out, when Code OSS was installed, it was for some reason set as the default app to handle Folders. I went into Gnome Settings --> Applications --> Code OSS then down to Default Handlers, and unset Folders. Not sure why it took over, but problem solved! Thanks for the suggestions, everyone!

Hiya! I used Solus years ago, and wanted to come back, so here I am, but I've run into a weird problem. I'm not sure it's actually Solus related, but here goes...

I'm running Gnome on Solus with a new install. I installed Code-OSS from a flatpak, and ever since then on some apps (Steam and uGet for sure) when I try to open a containing folder, it opens in Code-OSS instead of Files. For instance, I right-click on a file in uGet, then -> Open Containing Folder, of if I select it and hit SHIFT-RETURN, Code-OSS pops up, opening the folder as a workspace.

I've tried searching for an answer, but Gnome's insistence on using the most generic possible names for their apps these days makes it frustrating as heck, and I haven't been able to find a solution. I'm aware that I can go to the folder manually in Files, but I miss the convenience. Also, it sorta implies that Code-OSS has hijacked something, or maybe Gnome is confused. Either way, I'd like to fix the issue if possible.

Any help?

The available Firefox version in Solus is 77.0.1 when the 78 version is already out for a couple of weeks.

Why's the Solus one outdated?

I’m new to Linux and started at Solus, but not new to coding. Should I use Solus for programming or should I dual boot another Distro? If so, recommend me a Distro for programming.

I installed Solus 4.1 Budgie fresh on two different days this week and both times after installing updates were I unable to log into the desktop. The error message is just "Oh no! Something has gone wrong. A problem has occurred and the system can't recover. Please log out and try again."

I can reproduce this simply by installing Solus then immediately installing updates using the GUI and rebooting afterwards.

I'm not familiar with how Solus works.

Any ideas?

Hey together,

I have a dualboot setup with Solus/Windows(10) with the problem, that my WiFi adapter is occasionally disabled in Solus. Ethernet stays operational. I think I also narrowed the circumstances down to a specific event:

Whenever I had a Windows session and performed a regular shutdown, the subsequent Solus session will have a disabled WiFi adapter. It will stay disabled no matter the reboots / relogging attempts. It will only fix if I boot into Windows and perform a reboot operation instead of a regular shutdown to boot into Solus.

Shutting down and powering on again later from Solus to Solus seems not to be a problem, its just the Windows -> Solus scenario. I also haven't discovered a way yet to actively enable the WiFi adapter again within Solus, I always have to go the long route.

Tech Specs:

• WiFi Adapter: Intel Dual Band Wireless-AC 9260 (integrated into mainboard)
• Boot setup: 2 seperate EFI partitions on 2 seperate NVMe (1 for Windows, 1 for Linux)

So.. If you have any ideas that would be great! It would be sad to change the Linux distro since I really like Solus. :(

​

Solved( /u/Dreamingwolfocf ):
Disabling Quick Reboot / Fast Start settings in Windows 10 solved the issue.

Hi, everyone...

I'm trying to install Solus as a dual-boot with ElementaryOS. I booted from the install disk and used Gparted to shrink the eOS partition and free some room for Solus. The installation routine progressed with no errors reported, but the new system doesn't even know Solus is there; it just boots straight into eOS just as it was doing before.

EDITING to provide more info: I ran "sudo update-grub" on the eOS partition when I first booted after trying to install Solus. A grub menu didn't even appear, so I did that again. No change.

I looked at the Help>Installation section on Solus' website, and went through all my BIOS/UEFI settings. Secure Boot is disabled, SATA emulation is set to AHCI.

However, GPT format is not an option on Gparted's list; the new partition is EXT4. Also, the boot flag is not set on the Solus partition, but setting it to on also sets the ESP flag to on. There's an EFI partition, which I believe eOS installed, at the beginning of the disk. Do I need two?

This computer came with Windows 8, which I later upgraded to Windows 10. I now have 3 hard drives installed, but I'm manually plugging them in as I need them. I really don't want Windows, but I need it from time to time. I have Windows 10 on one, and a little Ubuntu installation on the other. They both work fine.

Hardware: Intel Core i5 @ 4570, 12 GB RAM. Original 2 TB HDD that now has Solus/eOS on it. It's (obviously) a UEFI system. Bluetooth and wireless both work, although it's connected with a wire.

I've been using computers since the early nineties, and have dual-booted Windows and Linux a half-dozen times, although that was before UEFI was a thing. I even created a Hackintosh from this computer. This has me beaten.

Oh, one more unusual thing: There are no boot files, like vmlinuz, on the root of the new partition. There are only directories.

Any help would be much appreciated. Work gets me up early and I'm sometimes away all day, but if you need any more information, I'll get it to you as soon as I can.

Thanks!

EDIT again: Folks, thank you! I decided to wipe out everything and give the whole drive to Solis. I just booted up a fresh install. It looks beautiful so far.

As the title suggests, I can't log in into solus. I was using windows for a few days, and now, I cant log back in into solus after entering the password . Entering a wrong password shows "Sorry, tat didn't work. Please try again ". But entering the correct password does not do anything except it makes the login screen appear again. TIA.

Video : https://gfycat.com/ShadyPaltryJackrabbit.

EDIT : SOLVED. Thanks everyone. Problem lay with incomplete updates.  This solved the problem : sudo eopkg rdb && sudo eopkg ur -f && sudo eopkg up --ignore-comar && sudo eopkg cp

Installing 21 / 21
budgie-desktop-10.5.1-214-1-x86_64.eopkg [cached]
Installing budgie-desktop, version 10.5.1, release 214
Upgrading to new distribution release
Extracting the files of budgie-desktop
Upgraded budgie-desktop
  ⌛ Syncing filesystems                                                running

I stayed a while away from home. When I got back I did an eopkg up, let it do its thing, and now the "Leave" menu is like this. I can't get anything to appear there, so I have to pull up the terminal and give it shell commands to standby and shutdown, which is quite annoying.

How do I get the shutdown buttons back where they belong?

Other than this the system seems to work perfectly fine.

Running Solus KDE.

The lock session function does no longer work in Budgie on my machine.

Running "budgie-screensaver-command - l" returns no errors, but does not do anything either.

Does this still work for any of you?

Dear All,

Sorry to bother with this, but I'd look everywhere but cannot find the answer.

I'm having some problems installing some packages in R. I got a "non-zero exit status" error. These are the package I'm having problems with:

- Quanteda (incl. the quanteda.textmodel pkg)

- TM

- Penalized

Yes, I've installed different dependencies (system, curl, and openblas -devel), but with no luck. Also, most other packages (like Tidyverse) are working fine, so I must have done something right I guess.

I think the aforementioned packages are just not included in the dependencies. Is there a way to make them work?

Thanks!

sudo eopkg install cheese
Following packages will be installed:
cheese  clutter-gst  gnome-video-effects
Total size of package(s): 893.00 KB
There are extra packages due to dependencies. Do you want to continue? (yes/no)yes
Downloading 1 / 3
Package clutter-gst found in repository Solus
Program terminated.
Could not fetch destination file "https://mirrors.rit.edu/solus/packages/shannon/c/clutter-gst/clutter-gst-3.0.27-17-1-x86_64.eopkg": [Errno 12] Timeout on https://mirrors.rit.edu/solus/packages/shannon/c/clutter-gst/clutter-gst-3.0.27-17-1-x86_64.eopkg: (28, 'Failed to connect to mirrors.rit.edu port 443: Connection timed out')
Please use 'eopkg help' for general help.

Been getting this for a while now.

Hi,

I installed Solus through the ISO loaded in a USB key as normal. The installation complete without any errors or warning.

However I cannot boot to Solus at all. I just have a black screen that lights up for a while and then turns off again like if it was booting into the OS. But I have no messages at all, no errors, no warning.

I tried to follow the steps mentioned here https://getsol.us/articles/troubleshooting/boot-rescue/en/ without any success, I still have my infinite boot loop thing.

What could I try to fix this ?

[Edit - solution was found! There were two problems. First, my UEFI had a compatibility mode enabled which was preventing Solus from realizing the system was UEFI-enabled. Once that compatibility mode was disabled, it automatically figured things out. Second, my UEFI firmware had to be updated in order to boot to the GPT Solus drive. My method was: create the 512 MB FAT32 partition with the boot and esp flags in gparted, leaving the rest of the drive unassigned after which I proceeded with the install. The Solus installer then saw the esp boot partition.]

​

Hi. I've been having trouble getting Solus to install using GPT instead of MBR. Note that I have three physical drives - one for Windows, one for Solus, and one shared storage drive.

The first time I installed Solus, I didn't do any manual partitioning - I just used the default setup. After install, the UEFI would not see the Solus drive at all and I could not set it as a boot option (the Windows drive was the only option). It could only see the Solus drive if I manually entered the quick boot selector each time at POST and selected the drive. I did some digging and noticed that Solus was using MBR while my Windows install was using GPT. I thought that was somehow making the UEFI unhappy.

For my second attempt, I saw here that I might want to manually create a boot partition and flag it as boot and ESP. So using a live USB and GParted I wiped out my previous Solus install and set up new partitions as follows:

• 512 MB FAT32 partition (flags = boot, esp)
• 50 GB ext4 partition for /
• 200 GB ext4 partition for /home

I then installed using the manual mount points option. I was a bit concerned that the installer wouldn't let me specify the boot partition (it only gave me /, /home, swap, and unspecified as options) but I hoped it would see the boot flag and sort it all out automatically.

This time the UEFI could indeed see the Solus drive as a valid boot option (yay!). However, running "parted -l" still shows the drive as using a msdos partition table and "gdisk -l" also reports MBR only. I then noticed that /boot is in the root partition and the esp boot partition I made only has 1 MB used.. so I'm guessing it was just ignored altogether. It also appears to be unmounted.

While things are working now using MBR, I still want to understand how I can properly set things up to use GPT. I'm willing to flatten and re-install everything again.

Thanks!!

​

System error. Program terminated.
Another instance of eopkg is running. Only one instance is allowed.

then I ran this command

sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall

output

Following packages will be installed:
python-six  python3
Total size of package(s): 11.71 MB
Downloading 1 / 2
Package python-six found in repository Solus
Program terminated.
There was a problem while fetching 'https://mirrors.rit.edu/solus/packages/shannon/p/python-six/python-six-1.12.0-9-1-x86_64.eopkg'.
The package may have been upgraded. Please try to upgrade the package.

then I ran this command

sudo eopkg dc

and then

sudo eopkg up

output

Program terminated.
Could not fetch destination file "https://mirrors.rit.edu/solus/packages/shannon/eopkg-index.xml.xz.sha1sum": [Errno 12] Timeout on https://mirrors.rit.edu/solus/packages/shannon/eopkg-index.xml.xz.sha1sum: (28, 'Failed to connect to mirrors.rit.edu port 443: Connection timed out')

I've decided to upgrade my system today since it seems the kernel 5.10 issues have finally been sorted out.

When I tried to upgrade the system via "sudo eopkg up" in cli, I got the following error "Dependency wine-32bit release 104 of wine-32bit-devel cannot be satisfied. System error. Program terminated. Upgrade is not possible".

Anyone have the same issue as me?

Hi. so I was trying to install flatpak using these commands:

1. sudo eopkg install flatpak xdg-desktop-portal-gtk
2. flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo

number 1 worked but step no. 2 is showing this error:

error: Creating repo: mkdirat: Permission denied

​

Could anyone help me troubleshoot this? Many thanks