Hello again, lovely people. I hope you are well today.
I wish I understood the nature of the problem better, or I’d have given this a more descriptive title.
Known Symptoms:
GreenWithEnvy says this:
Summary
Flameshot doesn’t work (says it can’t take screenshots)
Calibre (official repository) won’t load up
I hadn’t updated my stuff in a while, but I did a big* update with who knows what all in it (4-5 days ago maybe). Sometimes when there’s a big update with something, my GreenWithEnvy will have issues for a day or so (until “something” is updated again).
I didn’t see anything that was a known issue that screamed the same thing I was experiencing, so I wasn’t sure if this was something that was being worked on and is a problem for others, or what.
Nvidia GTX1080ti
Thanks, guys! If I need some data for you, let me know. Probably will need a command on how to retrieve it, too.
GreenWithEnvy (gwe) is not currently being maintained (I am assuming you did rebuild it after the latest update). The latest comment from its AUR (en) - gwe page:
Unfortunately GWE has had no maintainer for a long time at this point. I’ve moved on to using nvidia_oc for X + Wayland overclocking and coolercontrol for controlling fan speeds.
Has both GUI and webinterface (can be configured also remotely!), can be run as a systemd service at boot. Custom fan curves, more fine tuned fan hysteresis control, and many more.
pamac search coolercontrol
coolercontrold-bin 2.0.1-1 AUR
A program to monitor and control your cooling devices: daemon (binary release)
coolercontrold 2.0.1-1 AUR
A program to monitor and control your cooling devices. This package contains the CoolerControl service
daemon.
coolercontrol-liqctld 2.0.1-1 AUR
liquidctl daemon for CoolerControl
coolercontrol-bin 2.0.1-1 AUR
A program to monitor and control your cooling devices (binary release)
coolercontrol 2.0.1-1 AUR
A program to monitor and control your cooling devices
I’m not sure why Flameshot is not working, however it could be due to a missing optional dependency. Do you have xdg-desktop-portal & xdg-desktop-portal-gnome installed on your system?
pamac info flameshot
Name : flameshot
Version : 12.1.0-6
Description : Powerful yet simple to use screenshot software
URL : https://github.com/flameshot-org/flameshot
Licenses : GPL-3.0-or-later
Repository : extra
Installed Size : 2.9 MB
Groups : --
Depends On : qt5-svg hicolor-icon-theme kguiaddons5
Optional Dependencies : gnome-shell-extension-appindicator: for system tray icon if you are using Gnome
grim: for wlroots wayland support
xdg-desktop-portal: for wayland support, you will need the implementation for your wayland desktop environment [Installed]
qt5-imageformats: for additional export image formats (e.g. tiff, webp, and more) [Installed]
Provides : --
Replaces : --
Conflicts With : --
Packager : Robin Candau <antiz@archlinux.org>
Build Date : Thu 27 Mar 2025 09:10:18
Validated By : MD5 Sum SHA-256 Sum Signature
I’m afraid I can’t provide any advice on Calibre not starting/loading up. Maybe try running calibre from a terminal and see if there are any useful error messages.
GreenWithEnvy, I have the Flatpak for it, it seems. It was working before I did that huge bundle of updates (and in the past, it has broken frequently with updates, but usually seems to straighten out quickly). I’ve always assumed something nvidia updated, broke something, then something else figured it out and updated something else later.
I appreciate you mentionining it’s not maintained. I’ll keep that in mind going forward if it doesn’t come back. I really only use it to see my GPU temp in the toolbar. I’ll def look into coolercontrol, too!
I do indeed seem to have xdg-desktop-portal and the -gnome one.
Good call on running it from terminal. Now I have one more troubleshooting trick up my sleeve in the future.
The output in terminal is fairly gibberish to me, but it gets to:
File…, line 106, in msgpack_loads import msgpack
Then "ModuleNotFoundError: No module named ‘msgpack’
I went to the repository, and I saw a msgpack-c as the closest thing, so I installed it, but no change.
I’m not sure if it’s generally helpful to the troubleshooting of what’s going on here. I use “sticky” from the official repository, and its settings were so that it would automatically start at startup and open in the toolbar (at the top, near the power button).
Since the update, it’s opening, but it’s opening with the gear icon in my task bar (on the left) instead.
It isn’t bothering me as much as the others, so I wasn’t thinking about it as much, but I wasn’t sure if it was broken for the same reason that flameshot, etc were.
I don’t know what the difference between Wayland or X11 are, but it seems like it’s a big deal. I don’t know if that session type has something to do with the issues or not*.
Just wanted to add this in case it was somehow useful/related.
Yes, and yes. I have the official repo Calibre, and it has the official repo python-msgpack as you mentioned.
~ calibre ✔
Traceback (most recent call last):
File "/usr/bin/calibre", line 20, in <module>
from calibre.gui_launch import calibre
File "/usr/lib/calibre/calibre/__init__.py", line 39, in <module>
initialize_calibre()
File "/usr/lib/calibre/calibre/startup.py", line 135, in initialize_calibre
set_translators()
File "/usr/lib/calibre/calibre/utils/localization.py", line 317, in set_translators
q = translator_for_lang(lang)
File "/usr/lib/calibre/calibre/utils/localization.py", line 232, in translator_for_lang
mpath = get_lc_messages_path(lang)
File "/usr/lib/calibre/calibre/utils/localization.py", line 126, in get_lc_messages_path
if lang in available_translations():
File "/usr/lib/calibre/calibre/utils/localization.py", line 24, in available_translations
stats = msgpack_loads(f.read())
File "/usr/lib/calibre/calibre/utils/serialize.py", line 106, in msgpack_loads
import msgpack
ModuleNotFoundError: No module named 'msgpack'
I’ve been digging through this Flameshot Wayland help link you provided (thank you again on that).
I ran it as a shell script as it mentioned, then Gnome gave me a prompt about giving it permission to take screenshots:
~ sh -c -- "QT_QPA_PLATFORM=wayland flameshot gui" ✔ 14s
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
flameshot: info: Screenshot aborted.
It says I should be able to change something in “the privacy settings,” but I don’t seem to be able to/anything about it. I can’t get it to reproduce the prompt, so the exact wording isn’t something I remember, but it seemed more about being able to revoke its rights there.
That command seems to open the program directly into the screenshot mode, then I take the screenshot, and then it terminates the program. (Did this with flameshot closed to see).
I’ve tried it while Flameshot is running, to see if it would give it continuous permissions afterwards somehow, but it seems to also still be unable to capture still.
Between what the link said and what I’m seeing, it would appear as if Gnome updated something that revoked permission for Flameshot to take screenshots. They don’t seem to be too clear either about what that is, so I’m not very hopeful we’re going to know, either. So, that might be a lost cause until those guys get the opportunity to figure it out and work through it.
I switched it to “Gnome with xorg” instead of “Gnome.”
I’m not sure what the difference is between it and the “classic” variety, nor do I understand the difference between xorg and wayland either.
I’m assuming when I updated, something decided to automatically switch me from xorg to wayland without realizing it, and going forward, I suppose I need to ensure that it stays on xorg, though, again, I’m not sure what the implications are other than it seeming to work better.
Take a look at this file: /etc/gdm/custom.conf. There, you can disable Wayland by editing the file.
Wayland and X11 are “display protocols”. Wayland will replace X11 in the future entirely. Open Source drivers (AMD/INTEL) have good support for Wayland, but Nvidia has still bad support for Wayland, and therefore you need to rely on X11 when using Nvidia.
I opened the aforementioned file, “edit as admin,” removed the “#” in front of the Wayland line, and saved it.
Gotcha! So, Wayland will probably be better in the long run, but it’s just not workable for the time being until nvidia supports it better. And eventually, when that day comes, anything very old that was only built for X11 will just become unworkable.
Thanks for your time and expertise. It was very helpful and also enlightening. Have a great rest of your day/week!
