Week 17, 2026

DinimixisDEMZ

Mmm... I can't logout from my account...

Lucien_Lachance

DinimixisDEMZ
gsettings set org.gnome.shell always-show-log-out true
paste that in a terminal

DinimixisDEMZ

Lucien_Lachance Thank's!!

cornbean

EbonJaeger Can confirm that falcond is fixed now 🔥

brent

Xoph ust keep in mind that you have to check Matrix to make sure something like the kernel isn't going in and try and update during that as it can cause some serious problems.

what are the chances of this happening I wonder?

Harvey

brent

Extremely fucking high. If you don't want to be in the channel and checking the topic before updating then do not use the unstable repo.

brent

Harvey Extremely fucking high. If you don't want to be in the channel and checking the topic before updating then do not use the unstable repo.

Well, allow me to dust that account off then, and monitor from another tab 😄 . Not a fan of those odds.

brent

@Xoph Harvey

My account and PW were fine. Which channel/room am I watching for the kernel/unstable testing news?
![
](https://)

Harvey

brent

packaging

Solarmass

brent packaging room in the Matrix

brent

thank you both

SethStorm666

Works fine on Gnome, although half of the extensions I'm using broke. LOL 😃
Just have to wait for the maintainers of those extensions to fix it. Oh well...

mkl

SethStorm666 although half of the extensions I'm using broke.

The ever-turning wheel 😉

paracetamol

This update broke flameshot for me under X11 (Openbox). Attempt to launch it from a keyboard shortcut leaves the following in the system journal:

kwi 26 17:43:32 mach /usr/lib64/gdm/gdm-x-session[4062]: "No Qt translation found for English"
kwi 26 17:43:32 mach /usr/lib64/gdm/gdm-x-session[4062]: "No Qt translation found for English"
kwi 26 17:43:32 mach /usr/lib64/gdm/gdm-x-session[2397]: WARNING: Icon 'flameshot' not found in icon_path
kwi 26 17:43:32 mach /usr/lib64/gdm/gdm-x-session[4062]: flameshot: warning: If the useGrimAdapter setting is not enabled, the dbus protocol will be used. It should be noted that using the dbus protocol under wayland is not recommended. It is recommended to enable the useGrimAdapter setting in flameshot.ini to activate the grim-based general wayland screenshot adapter

Trying to run it from a command line produces this:

"No Qt translation found for English"
"No Qt translation found for English"
flameshot: warning: If the useGrimAdapter setting is not enabled, the dbus protocol will be used. It should be noted that using the dbus protocol under wayland is not recommended. It is recommended to enable the useGrimAdapter setting in flameshot.ini to activate the grim-based general wayland screenshot adapter

The program does not exit after this, but at the same time doesn't prompt me for anything. The clipboard is also empty.

My config looks like this:

❯ bat -p ~/.config/flameshot/flameshot.ini
[General]
contrastOpacity=188
savePath=/home/paracet/Pictures/Screenshots

Following advice from the troubleshooting section of the official docs I set these two options in the flameshot.ini (even though, as I understand, they are related to Wayland and not X11):

disabledGrimWarning=true
useGrimAdapter=true

With this I do manage to get a save dialog to pop up prompting me to choose destination. Accepting causes an error pop up to show saying:

Save Error

Error trying to save <path here>

I tried picking multiple directories, ensuring I have enough room on disk and write permissions, but no luck.

Removing the useGrimAdapter=true but leaving disabledGrimWarning=true produces just the warning about the english translation missing and hangs, no popups.

I had no problems with flameshot until this sync and from what I'm seeing, the flameshot version in the repos has not changed.

paracetamol

paracetamol Today I "woke up" to a not working Visual Studio Code and logs of coredumps during attempted launch in the system journal. On a hunch I logged back to GNOME and both Visual Studio Code and Flameshot work without a hitch there.

So I think this is GDM no longer playing nice with an X11 window manager. Oh well, I suppose I am back on GNOME then.

Axios

Thats why I stopped using Gnome way back when and the crashing they caused during updates at times.

BuzzPCSOS

A quick reach out for help. Running sudo eopkg check returns Linux-current broken.
Choosing to reinstall and rebooting goes without an issue but Linux-current still shows as broken.
Looked on another updated PC and the package is fine there. Any suggestions of what to do next would be welcome. FWIW I have already tried
sudo eopkg dc sudo eopkg rmo sudo eopkg rdb sudo eopkg check sudo eopkg up -y
in that order.
I have also tried booting into LTS, uninstalling current and then reinstalling. This also didn't work.
Edit: I have since checked on a 3rd PC which is also showing Linux-current as broken. The only PC I have that is showing healthy was the first PC to be updated. Could this be a Repo corruption or maybe my ISP sending me a cached copy?
For info this is showing up on Plasma although eopkg and Linux-current should be pretty universal.

brent

BuzzPCSOS Is the OS functional? does eopkg check (no sudo) give a different result? If you are on unstable is this an unstable thing? (I was warned about this last night in this very thread).

top of head

BuzzPCSOS

brent Thanks for the reply.
Everything seems to boot and run OK.
I have got 2 Plasma laptops and a Plasma Slate all running a mostly standard install on stable. Any modifications tend to get copied between all three so not sure why only two should be showing the error.
Running eopkg check without sudo returns mostly the same results except for some packages being unavailable due to no admin access.

Axios

BuzzPCSOS How many kernels you have on your machine
sudo clr-boot-manager list-kernels

BuzzPCSOS

Axios I will take a look in the morning, brain is on a go-slow because it needs a rest.
paracetamol that is reassuring even though I have never seen that behaviour on any of my PCs before. Makes me wonder more, why on two but not on the third?
I will look some more after some sleep.

BuzzPCSOS

Axios How many kernels you have on your machine

I have
com.solus-project.current.6.18.23-334
com.solus-project.lts.6.18.23-284
Currently booting on the LTS so that I could uninstall then reinstall current. It shows up as broken even after doing so.
As everything seems to work regardless I will go back onto current and see how it goes.
Many thanks to you, @paracetamol and @brent for scratching your heads along with me

paracetamol

I thought linux-current being reported as broken is a normal thing? You can search the forum archive to see folks encountering that and being told not to worry about it. FWIW mine is also reported as broken, but my machine works just fine.

brent

BuzzPCSOS that is reassuring even though I have never seen that behaviour on any of my PCs before

I do agree with paracetamol that this was 'a thing' (broken kernel) as I've seen it in some posts although I really didn't commit the hows/whys to memory...or whatever the devs said about it...I don't think I would like to see that in my output either.
sudo eopkg checkfor me, just now, says linux-current is OK.

BuzzPCSOS why on two but not on the third?

there's gotta be a variable in the haystack 🙂

« Previous Page Next Page »