The Linux Thread - The Autist's OS of Choice

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account

First time I've been introduced to Hyprland (because I can't be fucking bothered to run a tiling window manager).



Sounds pretty interesting.
 
Last edited:


First time I've been introduced to Hyprland (because I can't be fucking bothered to run a tiling window manager).



Sounds pretty interesting.
i do recommend trying out a twm at some point, just to say u did it
u can install it alongside ur current de and just swap to it in the dm
 
So Linux Mint 22.3 is failing to install the most up to date version of the Linux kernel available, apparently due to broken dependencies. Perhaps one of you who's more autistic than me can help me parse this output and find a solution.

Code:
Setting up linux-image-6.17.0-14-generic (6.17.0-14.14~24.04.1) ...
Setting up linux-headers-6.17.0-14-generic (6.17.0-14.14~24.04.1) ...
/etc/kernel/header_postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.17.0-14-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area...
'make' KERNELVER=6.17.0-14-generic............(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.17.0-14-generic (x86_64)
Consult /var/lib/dkms/amdgpu/6.12.12-2202139.24.04/build/make.log for more infor
mation.
dkms autoinstall on 6.17.0-14-generic/x86_64 failed for amdgpu(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
 * dkms: autoinstall for kernel 6.17.0-14-generic
   ...fail!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
dpkg: error processing package linux-headers-6.17.0-14-generic (--configure):
 installed linux-headers-6.17.0-14-generic package post-installation script subp
rocess returned error exit status 11
dpkg: dependency problems prevent configuration of linux-headers-generic-hwe-24.
04:
 linux-headers-generic-hwe-24.04 depends on linux-headers-6.17.0-14-generic; how
ever:
  Package linux-headers-6.17.0-14-generic is not configured yet.

dpkg: error processing package linux-headers-generic-hwe-24.04 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic-hwe-24.04:
 linux-generic-hwe-24.04 depends on linux-headers-generic-hwe-24.04 (= 6.17.0-14
.14~24.04.1); however:
  Package linux-headers-generic-hwe-24.04 is not configured yet.

dpkg: error processing package linux-generic-hwe-24.04 (--configure):
 dependency problems - leaving unconfigured
Processing triggers for linux-image-6.17.0-14-generic (6.17.0-14.14~24.04.1) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.17.0-14-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area...
'make' KERNELVER=6.17.0-14-generic............(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.17.0-14-generic (x86_64)
Consult /var/lib/dkms/amdgpu/6.12.12-2202139.24.04/build/make.log for more infor
mation.
dkms autoinstall on 6.17.0-14-generic/x86_64 failed for amdgpu(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
 * dkms: autoinstall for kernel 6.17.0-14-generic
   ...fail!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: error processing package linux-image-6.17.0-14-generic (--configure):
 installed linux-image-6.17.0-14-generic package post-installation script subpro
cess returned error exit status 11
Errors were encountered while processing:
 linux-headers-6.17.0-14-generic
 linux-headers-generic-hwe-24.04
 linux-generic-hwe-24.04
 linux-image-6.17.0-14-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)

Attempting to apt --fix-broken install does not work, nor does trying to force updates. Seeing "amdgpu" in the logs, I tried removing and reinstalling graphics drivers. But not only did that fail to help, it broke my screen resolution on reboot and I had to revert with Timeshift.
 
So Linux Mint 22.3 is failing to install the most up to date version of the Linux kernel available, apparently due to broken dependencies. Perhaps one of you who's more autistic than me can help me parse this output and find a solution
Try running dpkg --configure -a and see if the information in this (looks to be recent and virtually the same as your issue) and its answer helps solve your problem.

Edit: It looks like the amdgpu DKMS module is installed and its specifically the module that's having an issue. Looks like it could be out of date. Might want to at least read through the build log (/var/lib/dkms/amdgpu/6.12.12-2202139.24.04/build/make.log)

Edit 2: Looks like you have the standard driver from ROCm 6.4.4; For the kernel you're trying to install, it comes with the in-tree kernel module, which should work fine in place of the DKMS driver. If I'm correctly guessing what you have installed, you should be able to uninstall the DKMS driver, ensure the in-tree amdgpu module can load (and isn't blacklisted), and then after that you probably want to update any ROCm libraries to the latest.
 
Last edited:
lmao why do you HATE Nvidia, for me the experience between an Nvidia desktop and an AMD laptop is that Nvidia is only slightly second class.
Graphics drives have *only* broken twice from updates on arch but that could just be arch linux being stupid. I only use the two for gaming and haven't noticed anything too different other than waydroid, so someone more nerdy could some and say muh software doesnt work on Nvidia. Waydroid on AMD is so seemless you should try it out if you sell your 5080.

At least arch didn't break my bootloader after trying to load up cities skylines (thanks mint)
 
I have a question. I'm at a point where I'd be using my ubuntu headless server as my desktop (or basically plugging it into my tv) as I don't have any other computers capable of being used for Steam games and such. Can I just install cinnamon desktop without it breaking my netplan setup and such?
 
I have a question. I'm at a point where I'd be using my ubuntu headless server as my desktop (or basically plugging it into my tv) as I don't have any other computers capable of being used for Steam games and such. Can I just install cinnamon desktop without it breaking my netplan setup and such?
Assuming you mean by using tasksel or just installing the metapackage for it with apt, I can't see why not.
 
Assuming you mean by using tasksel or just installing the metapackage for it with apt, I can't see why not.
I did have to switch to Networkmanager from networkd which required a reboot, installed xorg and cinnamon-core and it seems to function but sound is a little distorted and I get wicked screen tearing just scrolling through web pages

sound playback is horrible, like really bad stutter

maybe i should just backup all mt docker images and everythign I need and do a clean install with LMDE or something

And now my server keeps on going to sleep and such. A sorta easy fix, but there's going to be all sorts of little problems cropping up and since this is clearly not working and I have so much tech debt littering the OS from other things I've tried that fuck it, I nuked the OS drive and installed Debian 13. so far all my backups for docker netplan and fstab seems to be working fine, but rsync didn't copy over my .compose folder but I did have a version from an older backup so i'm going through it section by section readding my apps
 
Last edited:

Brodie made a video specifically for the guy in this thread that constantly talks about wayland screensavers
Hi, Brodie! I may not be the guy.
I just want you to know you are a fat faggot who loves to suck tranny cock. Never change, because this will cost you harshly in the future, once you won't be able to toe the line.
 
Imagine something as simple as a screensaver being your biggest challenge as a developer. The final boss called Blank Screen.
The blank screen thing has been around in wayland for long enough to say it's nothing new. The thing people complain about on wayland, or the guy in the thread (I can't remember the username of the person that would bring it up), is that the devs that have made screensavers/screenlocks for wayland didn't recreate the functionality of xscreensaver. For the elaborate animated screensavers, and that kind of thing. They only added the normal screenlock behavior, or blanking (to avoid burn in, or save power). I can't remember the desktop they were complaining about, likely kde if I had to guess like brodie mentions in the video. They saw it as pointless to add the extra stuff. Which I personally agree with actually. But I'm someone that likes using slock on xorg, and other suckless tools. So my opinions aren't going to be the same as that users.
 
The blank screen thing has been around in wayland for long enough to say it's nothing new. The thing people complain about on wayland, or the guy in the thread (I can't remember the username of the person that would bring it up), is that the devs that have made screensavers/screenlocks for wayland didn't recreate the functionality of xscreensaver. For the elaborate animated screensavers, and that kind of thing. They only added the normal screenlock behavior, or blanking (to avoid burn in, or save power). I can't remember the desktop they were complaining about, likely kde if I had to guess like brodie mentions in the video. They saw it as pointless to add the extra stuff. Which I personally agree with actually. But I'm someone that likes using slock on xorg, and other suckless tools. So my opinions aren't going to be the same as that users.
I have no intention of listening to that subhuman gay retard, but suggesting that only supporting basic screen blanking is 'normal' is just wrong.

Screensavers have been supported on real, workable GUI systems since the 1980s. I use i3lock myself, but that doesn't mean I have to pretend it's normal to break things and not support screensavers at all.
 
I have no intention of listening to that subhuman gay retard, but suggesting that only supporting basic screen blanking is 'normal' is just wrong.

Screensavers have been supported on real, workable GUI systems since the 1980s. I use i3lock myself, but that doesn't mean I have to pretend it's normal to break things and not support screensavers at all.
What doesn't support screensavers at all?
 
KDE since version 4 or so?
1771826875769.png

here I just looked this up, got this. The xscreensaver people are doing the work to add wayland support finally. But as far as I know literally anyone could have made a wayland screensaver tool, but no one has because as far as I can tell no one cares enough to do that work themselves. Which is why I asked what doesn't have any screensaver support.
 
Back
Top Bottom