this post was submitted on 26 Nov 2023
109 points (95.8% liked)

Linux

48003 readers
977 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

I broke some packages and I need help figuring out how to fix it.
I run Nobara and usually update via "Nobara Package Manager", however it ran into a problem:

Could not depsolve transaction; 1 problem detected:
Problem: The operation would result in removing the following protected packages: nobara-amdgpu-config

I found the solution on Nobara projects site: sudo dnf update --exclude=nobara-login --refresh && sudo dnf update --refresh
That did result in several packages begin updated, I just skimmed through the list but I remember some mesa stuff. After a reboot some apps render like in the picture - missing characters or missing text all together and flickering artefacts. I run things pretty out-of-the-box so not sure what I've done that has lead up to this, just care about gaming.

How can I troubleshoot this? Thanks in advance

you are viewing a single comment's thread
view the rest of the comments
[–] Makka@lemmy.one 1 points 11 months ago

Yeah I forgot to mention that I'll not be using dnf manually but rely on nobara-sync. But I must stress that I already did that before this issue, BUT I followed advice on nobaras own website where the solution was to use dnfand I still ended up with this problem. The real issue was still my own though, I should have upgraded to Nobara 38 before trying the workarounds, since 37 isn't supported any more.