Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
i do recommend trying out a twm at some point, just to say u did it
First time I've been introduced to Hyprland (because I can't be fucking bothered to run a tiling window manager).
Sounds pretty interesting.
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)
Try runningSo 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
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./var/lib/dkms/amdgpu/6.12.12-2202139.24.04/build/make.log)Did you check the log its telling you to look in?Perhaps one of you who's more autistic than me can help me parse this output and find a solution.
Assuming you mean by using tasksel or just installing the metapackage for it with apt, I can't see why not.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 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 pagesAssuming you mean by using tasksel or just installing the metapackage for it with apt, I can't see why not.
Hi, Brodie! I may not be the guy.
Brodie made a video specifically for the guy in this thread that constantly talks about wayland screensavers
Imagine something as simple as a screensaver being your biggest challenge as a developer. The final boss called Blank Screen.Brodie made a video specifically for the guy in this thread that constantly talks about wayland screensavers
This one hit the boys gamer chat just right. Keep em coming.made these quickly
View attachment 8588919
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.Imagine something as simple as a screensaver being your biggest challenge as a developer. The final boss called Blank Screen.
I have no intention of listening to that subhuman gay retard, but suggesting that only supporting basic screen blanking is 'normal' is just wrong.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.
What doesn't 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.
KDE since version 4 or so?What doesn't support screensavers at all?
KDE since version 4 or so?
