Week 13, 2026

Harvey

We are not the developers of discover so we did not choose the wording and your suggestion would be inaccurate with default settings, it does not wait to apply updates on reboot. The update is installed and you should reboot to make sure everything is loaded properly.

The only difference is Linux never used to tell you when you should reboot and relied on people knowing when they should reboot, however 99% of people do not know and would encounter issues they would not have if they just rebooted.

So even if I was the developer behind discover, I would not be changing this. Don't wanna reboot? great don't but don't post about any issues you encounter until you encounter them after a reboot.

JayC

Teggs As a fairly recent Windows convert, I thought that tools like Discover and Gnome software would be something that would ease the transition. I was wrong. Just too much weird behavior and bugs. The worst part there is not really anything the Solus team can do about it. I moved to Solseek and never looked back at this point. Maybe one day Discover will get there.

brent

JayC I thought that tools like Discover and Gnome software would be something that would ease the transition.

those things have their strengths (good reading, colors and pictures) but never really package management material for many. I see this in the Arch forums too. In Linux the 'transition' you refer is usually to the terminal (the terminal is easy and friendly and can 'ease the transition' if one adapts) or things like yast and other management GUIs specific to a distro. Solseek is exclusive to Solus andmore comprehensive than the terminal and easier in many ways. That you came from WIN and easily using Solseek is a great transition you made to me.

snowee

Solus Budgie on Nvidia.

After this week's sync, I'm unable to start any Steam game on Proton.
Steam starts fine, but clicking on "Play" button doesn't launch any game, I tried starting up 3 different games, none works.
The "Play" button changes to "Stop" button, but nothing else happens.

Restarting Steam doesn't help.

UPDATE : when I removed the "mangohud" command from Steam Launch Options, games can start normally.
under steam proton launch options -
DXVK_FRAME_RATE=120 MANGOHUD=1 %command% --> game starts normally with MangoHUD enabled
DXVK_FRAME_RATE=120 mangohud %command% --> doesn't start up (previously it used to work, one sync ago)
Certain games refuse to start with the MANGOHUD=1 argument, whereas other games can.
Can anyone replicate my findings?

on Heroic, I can start up a game, I can hear the sound but nothing appears on screen.
My Heroic has no mangohud enabled by default.
This happened after this week's sync, so it could be due to some software that was updated.
When I attempt to start up a game, I can hear the sound, but the screen window is blank, after alt-tabbing a few times, I can get it to resize itself to a smaller window, but there is no graphics at all, whilst the sound is proceeding correctly. Is it some kind of rendering or graphical issue?

snowee

snowee
I did a little further investigation into my issue of Heroic Games Launcher not being able to launch games properly on full-screen mode, which start occurring after last week's sync.

I checked the logs of the games and it displayed this particular line in red "012c:err:d3d:wined3d_debug_callback 0288CB10: "GL_INVALID_FRAMEBUFFER_OPERATION error generated. Operation is not valid because a bound framebuffer is not framebuffer complete"

Above error means MAME's Direct3D/OpenGL rendering is failing because the framebuffer (render target) is incomplete—Wine can't properly translate MAME's Windows D3D calls to Linux OpenGL/Vulkan drivers.
What Causes It

Texture/depth buffer mismatch: MAME tries render-to-texture operations incompatible with your GPU drivers (NVIDIA/AMD/Intel)
DXVK/WineD3D conflict: Proton GE's Vulkan layer fails fallback to OpenGL
Incomplete FBO: Framebuffer attachments (color/depth/stencil) don't match formats/sizes

By passing the PROTON_USE_WINED3D=1 as an additional Environment Variable, I managed to solve the issue completely. This is equivalent to disabling Vulkan and forcing the usage of WineD3D.

In addition, running these same games using Steam Proton (v9.0.4) and Dosbox Staging plays perfectly well.

This leads me to believe that there might be some underlying issue with Heroic Launcher's implementation of Vulkan/DXVK/Wine..

zed

Update Perfect as usual !!
You have my sincerest thanks for that 🙂

elusian

After the update my games from Steam were hitting very low FPS.

To check whether it was the update or not I reverted it with eopkg hs -t, but that broke eopkg.

 [✓] Syncing filesystems                                                success
 [✓] Updating dynamic library cache                                     success
 [✓] Updating hwdb                                                      success
 [✓] Updating system users                                              success
 [✓] Reloading systemd configuration                                    success
 [✓] Updating systemd system service preset: fwupd.service              success
 [✓] Updating systemd system service preset: fwupd-refresh.service      success
 [✓] Updating systemd system service preset: switcheroo-control.service success
 [✓] Updating systemd system service preset: fwupd-refresh.timer        success
 [✓] Compiling glib-schemas                                             success
 [✓] Updating icon theme cache: hicolor                                 success
 [✓] Updating desktop database                                          success
 [✓] Updating manpages database                                         success
 [✓] Reloading udev rules                                               success
 [✓] Applying udev rules                                                success
System error. Program terminated.
Please use 'eopkg help' for general help.
Use --debug to see a traceback.

Now in eopkg hs I see a transaction for the revert, but asking for info for some packages crashes eopkg

$ eopkg info switcheroo-control
Program terminated.
Unable to read file (/var/lib/eopkg/package/switcheroo-control-3.0-4/metadata.xml): [Errno 2] No such file or directory: '/var/lib/eopkg/package/switcheroo-control-3.0-4/metadata.xml'
Please use 'eopkg help' for general help.

and so does eopkg check

$ sudo eopkg check
... many lines ...
Program terminated.
Unable to read file (/var/lib/eopkg/package/proton-vpn-gtk-app-4.15.1-35/files.xml): [Errno 2] No such file or directory: '/var/lib/eopkg/package/proton-vpn-gtk-app-4.15.1-35/files.xml'
Please use 'eopkg help' for general help.

eopkg rdb

$ eopkg rdb
[sudo] password for elusiani:
Rebuild eopkg databases? (yes/no)y
Disabling keyboard interrupts for file operations.
Rebuilding the FilesDB...
Adding packages to FilesDB /var/lib/eopkg/info/files.db:
.............................Program terminated.
Program terminated.
Unable to read file (/var/lib/eopkg/package/proton-vpn-gtk-app-4.15.1-35/files.xml): [Errno 2] No such file or directory: '/var/lib/eopkg/package/proton-vpn-gtk-app-4.15.1-35/files.xml'
Unable to read file (/var/lib/eopkg/package/proton-vpn-gtk-app-4.15.1-35/files.xml): [Errno 2] No such file or directory: '/var/lib/eopkg/package/proton-vpn-gtk-app-4.15.1-35/files.xml'
Please use 'eopkg help' for general help.

(I really hope I did not make things worse with this last command...)
and in general checking for updates

eopkg lu --debug
DEBUG: RepoDB initialized in 0.00010156631469726562.
DEBUG: InstallDB initialized in 0.003700733184814453.
DEBUG: PackageDB initialized in 0.19634056091308594.
System error. Program terminated.
<class 'FileNotFoundError'>: [Errno 2] No such file or directory: '/var/lib/eopkg/package/proton-vpn-gtk-app-4.15.1-35/metadata.xml'
Please use 'eopkg help' for general help.

Traceback:
  File "/tmp/onefile_111414_1774786131_927526/eopkg.py3", line 89, in <module>
  File "/tmp/onefile_111414_1774786131_927526/eopkg.py3", line 85, in main
  File "/tmp/onefile_111414_1774786131_927526/pisi/cli/pisicli.py", line 132, in run_command
  File "/tmp/onefile_111414_1774786131_927526/pisi/cli/listupgrades.py", line 64, in run
  File "/tmp/onefile_111414_1774786131_927526/pisi/api.py", line 262, in list_upgradable
  File "/tmp/onefile_111414_1774786131_927526/pisi/operations/upgrade.py", line 472, in is_upgradable
  File "/tmp/onefile_111414_1774786131_927526/pisi/db/installdb.py", line 160, in get_version_and_distro_release

Edit:
Since only eopkg seemed broken I rebooted. eopkg is still broken, but at least the game work now.
I think the update to switcheroo-control somehow made game run on the iGPU instead of the nvidia one.

Rgib

Everything is OK after the sync. I notice that borg have been updated, but it is not on the list of this week changes. I like to read changelogs before update my system. Is there a way to read the history of a package with eopkg, github or other ?

Solarmass

Rgib there is a link for "The full list of updated packages" in OP.
There is eopkg history command

Rgib

Solarmass I ask the question because borg is not in the full list of updated packages. eopkg history give me the history of updates in my system. I'm searching for the changelog. Exemple with calibre , I can read in the full list of updates : "Rebuild for libstemmer". But in few week, if I wonder "When did they update calibre, and why ?" How can I know that ? I suppose I can use eopkg history and then search the forum for the corresponding sync, but it doesn't feel very reliable

Solarmass

paracetamol looks like this fixed tearing on AMD system! 🥳

alfisya

Rgib Try eopkg blame packagename. Does it fit your usecase?

Rgib

alfisya Thank you, this is exactly what I was searching

« Previous Page