Updated the request to reflect the correct package update instructions.

Confirmed that resolved the error.

I have a new drive and so far this seems to be hardware related as the problem is no longer. Marking as invalid as the error was not related to the OS.

This is preliminary but I believe I might have a bad drive and ordered a new one, going to test this out on an microSD until then, but this maybe a fluke issue.

ok was able to chroot, but clr-boot-manager fails to update

This error is back and happening on both the 3.9999 and 4.0 kernels.
I am struggling to chroot the lvm encrypted device.

Some success though I may have gone one step too far...

@JoshStrobl Thanks for merging this, initially I thought they were unrelated.

This is partially fixed, the

nautilus

it had a broken dependent

tracker

That is resolved and working but the

clr-boot-manager

is throwing the bus error

I was able to fix the tracker issue by reinstall it and that fixed the nautilus issue in the other ticket, but still have the clr-boot-manager udpate bus error

Sharing the output of both commands below.

In T7668#145605, @Girtablulu wrote:

You did check for any broken packages? Specially if you say it happens when you used the "Budgie Shutdown Applet" this appelt maybe broke something

In T7668#145579, @Girtablulu wrote:

Eopkg dc
Eopkg up
Eopkg it --reinstall clr-boot-manager

Anyone able to take a look at this?

Adding this as I did a reinstall of linux-current and noticed this

That would be correct, my apologies i missed that line on that page.

Thanks can you add how to pull up the UEFI menu on boot?
THis might be a good thing to add to the FAQ or some place

I followed the extension install instructions but no luck. i think it would be good to package this some how.

That seems very likely, I put it up here so if others run into it that there is an approach on it.

In T7427#140470, @JoshStrobl wrote:

Sure thing. Do sudo eopkg install https://packages.getsol.us/unstable/c/clipit/clipit-1.4.2-8-1-x86_64.eopkg

Thanks, are there instructions to revert one specific package? since that update had a large amount.

@DataDrake Thanks, I updated and the system boots well.

@DataDrake Great! I am not familiar with how to use unstable in Solus (former Debian user). Where can I find instructions on using unstable?

In T6601#119185, @DataDrake wrote:

Looks like we need this patch: https://marc.info/?l=ibm-acpi-devel&m=152974495020350&w=2

I'll get it into unstable later today.

@NoCodeForOldMen Thanks for sharing this, I am not able to test it out fully but maybe someone can as you suggest. One followup question have you also had problems with the touch screen going black and not responding after trying to wake it up? I am not sure if it is related to this but there is this ticket as well https://dev.solus-project.com/T4351

I cannot test this anymore, as i migrated back to debian, but prior to march 10 I was still having this problem.

maybe it is worth adding this is a touch screen as well and it continues to not respond from a suspend state, the computer is heard coming on but there is no screen response.

I am not having that success at all. Daily basis system will not wake and have to do a forced power down.

In T717#11520, @JoshStrobl wrote:

We already have Franz via third-party which can achieve this. Please use that.

I would like to offer myself as a tester if/when there is a build of this available. It is something I miss from debian

I am also having this issue with Intel Video
glxinfo | grep OpenGL
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.1
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 17.3.1
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 17.3.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

Adding my experience running on Thinkpad 13

This is happening to me, I am new to the solus OS, coming from debian. This has happened twice to me after intentionally hibernating or after it slips into hibernation. I am running on a Lenovo Thinkpad 13. On debian I never had the issue. Wonder if it is hardware specific.

@kyrios123 my apologies I misread it completely... thanks

@krios123 this is now about two years old is there any work around?