RMS addresses the free software community
https://www.fsf.org/news/rms-addresses-the-free-software-community
https://redd.it/mpi3lx
@r_linux
https://www.fsf.org/news/rms-addresses-the-free-software-community
https://redd.it/mpi3lx
@r_linux
www.fsf.org
RMS addresses the free software community
Submitted bug report yesterday: fixed in less than 24h – Open Source rulez!
I’ve already thanked the two involved people by private mail, but I think it’s important to thank all those package maintainers and open source developers for their hard work – thus this post.
# Here is my story:
I did submit a bug report on my Linux distributions bug tracker as of Yesterday noon about a really annoying bug in the video editor Kdenlive which started to occur with the newest KDE-Plasma version (btw. I use Arch).
* [https://bugs.archlinux.org/task/70409](https://bugs.archlinux.org/task/70409)
The first (reflexive?) reaction was: This is an upstream bug; file it upstream. However I didn’t read this reply until late morning today.
Nevertheless in the meantime the Arch package maintainer obviously decided to not wait for me to open this bug upstream but (I guess) he talked to the Kdenlive developers by himself.
And one of the Kdenlive developers was like: Hold my beer.
So this early morning some minutes after 7 AM (imagine that, 7 AM!!) he did a patch upstream which addressed a possible QT5 regression:
* [https://invent.kde.org/multimedia/kdenlive/commit/f86dbde2.patch](https://invent.kde.org/multimedia/kdenlive/commit/f86dbde2.patch)
Shortly after, around 8 AM (imagine – in the middle of the night!!) the Arch package maintainer included this fix into the Kdenlive package:
* [https://github.com/archlinux/svntogit-packages/commit/874bb3c20425871f202e7fa4fe43e7f14586b2e2#diff-3e341d2d9c67be01819b25b25d5e53ea3cdf3a38d28846cda85a195eb9b7203a](https://github.com/archlinux/svntogit-packages/commit/874bb3c20425871f202e7fa4fe43e7f14586b2e2#diff-3e341d2d9c67be01819b25b25d5e53ea3cdf3a38d28846cda85a195eb9b7203a)
All the time I wasn’t aware of all this but sleeping like a baby. I did a "pacman -Syu" (Arch Linux package update command) around 10:30 AM and there was a Kdenlive package update popping in.
Hmm – it wouldn’t possible address my bug report, would it? But imagine my surprise: It was!!
Kdenlive worked fine again. I still couldn’t believe this was because of my bug report so I started looking at the package build (something like an srpm source). And then I just reconstructed the timeline from above… What an amazing stunt by those two people (Antonio the package maintainer and Jean-Baptiste the developer).
All this on a Sunday/early Monday! Much too unhealthy early in the morning!
And this is my experience from a lot of open source bug reports I did. Well – perhaps not this fast but anyway.
So a big Thank You to all those open source developers and package maintainers which in most cases working in their spare time just for the phun of it! Thank you guys!
## Now: Imagine the same with a commercial solution (I have this often enough in my job):
1. Check if your support contract really covers this kind of problem. Else you are on your own.
2. Try to explain it to their support. They want you to do a lot of senseless things just to make sure the “protocol” is correct. 1 week for this, after a lot of email ping pong (“your /var/log/messages file has the wrong format!!”).
3. Eventually the support will tell you that your current \[insert lib here\] version is not supported. Backport it (and live with the security problems) or: You are on your own.
4. If you can convince the support that your problem is valid you may eventually speak to a dev. The dev will send you test versions (“please try this version with a fix in it!”). The test versions won’t work at all. After some incarnations of more or less non working test versions you realize, the dev works on MacOS all the time. You convince him of installing Linux in a VM. After a while he proudly tells you, he is on Ubuntu 18.04 now. Before you complain that he should at least use 20.04 you remember that your company uses RHEL7, so 18.04 is better but not quite right. But now the dev is going on vacation for a month and a substitute is taking over, but he doesn’t realize your problem at all plus he is on Windows. … If things go really smooth you’ll have a solution
I’ve already thanked the two involved people by private mail, but I think it’s important to thank all those package maintainers and open source developers for their hard work – thus this post.
# Here is my story:
I did submit a bug report on my Linux distributions bug tracker as of Yesterday noon about a really annoying bug in the video editor Kdenlive which started to occur with the newest KDE-Plasma version (btw. I use Arch).
* [https://bugs.archlinux.org/task/70409](https://bugs.archlinux.org/task/70409)
The first (reflexive?) reaction was: This is an upstream bug; file it upstream. However I didn’t read this reply until late morning today.
Nevertheless in the meantime the Arch package maintainer obviously decided to not wait for me to open this bug upstream but (I guess) he talked to the Kdenlive developers by himself.
And one of the Kdenlive developers was like: Hold my beer.
So this early morning some minutes after 7 AM (imagine that, 7 AM!!) he did a patch upstream which addressed a possible QT5 regression:
* [https://invent.kde.org/multimedia/kdenlive/commit/f86dbde2.patch](https://invent.kde.org/multimedia/kdenlive/commit/f86dbde2.patch)
Shortly after, around 8 AM (imagine – in the middle of the night!!) the Arch package maintainer included this fix into the Kdenlive package:
* [https://github.com/archlinux/svntogit-packages/commit/874bb3c20425871f202e7fa4fe43e7f14586b2e2#diff-3e341d2d9c67be01819b25b25d5e53ea3cdf3a38d28846cda85a195eb9b7203a](https://github.com/archlinux/svntogit-packages/commit/874bb3c20425871f202e7fa4fe43e7f14586b2e2#diff-3e341d2d9c67be01819b25b25d5e53ea3cdf3a38d28846cda85a195eb9b7203a)
All the time I wasn’t aware of all this but sleeping like a baby. I did a "pacman -Syu" (Arch Linux package update command) around 10:30 AM and there was a Kdenlive package update popping in.
Hmm – it wouldn’t possible address my bug report, would it? But imagine my surprise: It was!!
Kdenlive worked fine again. I still couldn’t believe this was because of my bug report so I started looking at the package build (something like an srpm source). And then I just reconstructed the timeline from above… What an amazing stunt by those two people (Antonio the package maintainer and Jean-Baptiste the developer).
All this on a Sunday/early Monday! Much too unhealthy early in the morning!
And this is my experience from a lot of open source bug reports I did. Well – perhaps not this fast but anyway.
So a big Thank You to all those open source developers and package maintainers which in most cases working in their spare time just for the phun of it! Thank you guys!
## Now: Imagine the same with a commercial solution (I have this often enough in my job):
1. Check if your support contract really covers this kind of problem. Else you are on your own.
2. Try to explain it to their support. They want you to do a lot of senseless things just to make sure the “protocol” is correct. 1 week for this, after a lot of email ping pong (“your /var/log/messages file has the wrong format!!”).
3. Eventually the support will tell you that your current \[insert lib here\] version is not supported. Backport it (and live with the security problems) or: You are on your own.
4. If you can convince the support that your problem is valid you may eventually speak to a dev. The dev will send you test versions (“please try this version with a fix in it!”). The test versions won’t work at all. After some incarnations of more or less non working test versions you realize, the dev works on MacOS all the time. You convince him of installing Linux in a VM. After a while he proudly tells you, he is on Ubuntu 18.04 now. Before you complain that he should at least use 20.04 you remember that your company uses RHEL7, so 18.04 is better but not quite right. But now the dev is going on vacation for a month and a substitute is taking over, but he doesn’t realize your problem at all plus he is on Windows. … If things go really smooth you’ll have a solution
bugs.archlinux.org
FS#70409 : Kdenlive problems on plasma-desktop 5.21.4-1 (mouse over on sliders change slider values)
Flyspray, a Bug Tracking System written in PHP.
after 3 months. Paid support is all about this.
## how to do a bug report the right way
Now – please don’t think an open source bug report is always a breeze like the one I described. Before you spam your favorite projects with bug reports please do:
* Check if your problem is already solved upstream.
* Check if your problem is already addressed by another bug report.
* Check if you might instead want a feature request. Think about it!
Only then start writing it!
When doing an bug report use clear language. Use a clear structure (most bug trackers give you a structure, you “just” have to fill it out), that’s usually: A short denoscription, version numbers and how to reproduce the bug. Don’t tell unnecessary details. The developers/maintainers will ask for it when it matters. Keep it short!
Be prepared to help! That means you should know how to anonymise a log efficiently, how to deal with a .patch, how to compile from git, so you can try things out and report back. If you unable to operate on this level but really want to do a bug report anyway – tell this (very!) soon! No developer wants to explain how to apply a patch to you.
And not at least: Be friendly. You may be annoyed by the bug but please remember. Most of the open source people are not paid for it. They do that in their spare time. They may be in more stress than you right now. They may be female (so you oughta behave!!). Remembering all that will help you to stay friendly!
That’s all (sry for the wall of text).
TL'DR: Got a bug fixed in less than 24 hours what would take 3 months in corporate world. And if you do bug reports, keep it short and clear. Be friendly.
https://redd.it/mpkft5
@r_linux
## how to do a bug report the right way
Now – please don’t think an open source bug report is always a breeze like the one I described. Before you spam your favorite projects with bug reports please do:
* Check if your problem is already solved upstream.
* Check if your problem is already addressed by another bug report.
* Check if you might instead want a feature request. Think about it!
Only then start writing it!
When doing an bug report use clear language. Use a clear structure (most bug trackers give you a structure, you “just” have to fill it out), that’s usually: A short denoscription, version numbers and how to reproduce the bug. Don’t tell unnecessary details. The developers/maintainers will ask for it when it matters. Keep it short!
Be prepared to help! That means you should know how to anonymise a log efficiently, how to deal with a .patch, how to compile from git, so you can try things out and report back. If you unable to operate on this level but really want to do a bug report anyway – tell this (very!) soon! No developer wants to explain how to apply a patch to you.
And not at least: Be friendly. You may be annoyed by the bug but please remember. Most of the open source people are not paid for it. They do that in their spare time. They may be in more stress than you right now. They may be female (so you oughta behave!!). Remembering all that will help you to stay friendly!
That’s all (sry for the wall of text).
TL'DR: Got a bug fixed in less than 24 hours what would take 3 months in corporate world. And if you do bug reports, keep it short and clear. Be friendly.
https://redd.it/mpkft5
@r_linux
reddit
Submitted bug report yesterday: fixed in less than 24h – Open...
I’ve already thanked the two involved people by private mail, but I think it’s important to thank all those package maintainers and open source...
Blurred a default GNOME wallpaper and added a white Arch logo. Thoughts? I'm semi-new to photo editing so this is kinda new to me.
https://redd.it/mple5k
@r_linux
https://redd.it/mple5k
@r_linux
Arcan: Introducing Pipeworld: Spreadsheet Dataflow Computing
https://arcan-fe.com/2021/04/12/introducing-pipeworld/
https://redd.it/mpok60
@r_linux
https://arcan-fe.com/2021/04/12/introducing-pipeworld/
https://redd.it/mpok60
@r_linux
Arcan
Introducing Pipeworld: Spreadsheet Dataflow Computing
Now for something completely different. In the spiritual vein of One Night in Rio: Vacation photos from Plan9 and AWK for multimedia, here is a tool that is the link that ties almost all the projec…
3d/skeuomorphic Plank dock theme for Linux?
I have been looking for a while. And if anybody on here knows where I could find one, please let me know.
Thank you.
Ps: I need to add extra text on the bottom so the auto mod doesn’t remove my post for the 4th time for being too short.
https://redd.it/mpr8ot
@r_linux
I have been looking for a while. And if anybody on here knows where I could find one, please let me know.
Thank you.
Ps: I need to add extra text on the bottom so the auto mod doesn’t remove my post for the 4th time for being too short.
https://redd.it/mpr8ot
@r_linux
reddit
3d/skeuomorphic Plank dock theme for Linux?
I have been looking for a while. And if anybody on here knows where I could find one, please let me know. Thank you. Ps: I need to add extra...
Do we have AMD vs Nvidia Driver CPU overhead issues on linux?
Hello, I recently feel into a couple of youtube videos of hardware unboxed talking about driver overhead issues that Nvidia drivers where causing in CPU bound games. I did not find any discussion if this behavior exists on Linux.
What I was specifically curious about is if AMD uses hardware scheduling over software scheduling on Linux, or if both Nvidia and AMD GPUs uses software scheduling?
Edit: This is the video I refer to quite interesting numbers, thought some setups benchmarked are not realistic. https://www.youtube.com/watch?v=G03fzsYUNDU
https://redd.it/mptq3o
@r_linux
Hello, I recently feel into a couple of youtube videos of hardware unboxed talking about driver overhead issues that Nvidia drivers where causing in CPU bound games. I did not find any discussion if this behavior exists on Linux.
What I was specifically curious about is if AMD uses hardware scheduling over software scheduling on Linux, or if both Nvidia and AMD GPUs uses software scheduling?
Edit: This is the video I refer to quite interesting numbers, thought some setups benchmarked are not realistic. https://www.youtube.com/watch?v=G03fzsYUNDU
https://redd.it/mptq3o
@r_linux
YouTube
Nvidia Driver Investigation [Part 2] Owners of Old CPUs Beware
Gigabyte Aorus 6700 XT Elite: https://www.gigabyte.com/Graphics-Card/GV-R67XTAORUS-E-12GD
Support us on Patreon: https://www.patreon.com/hardwareunboxed
Join us on Floatplane: https://www.floatplane.com/channel/HardwareUnboxed
Buy relevant products from…
Support us on Patreon: https://www.patreon.com/hardwareunboxed
Join us on Floatplane: https://www.floatplane.com/channel/HardwareUnboxed
Buy relevant products from…
Learn Linux Through Man Pages
https://hackingpassion.com/learn-linux-through-man-pages/?fbclid=IwAR2-Km5PeR-d0Hr6fJ39GQ-G_-UdjbZ-CW375EKjhiVVfNPcmAnsalqqXzg
https://redd.it/mo9rls
@r_linux
https://hackingpassion.com/learn-linux-through-man-pages/?fbclid=IwAR2-Km5PeR-d0Hr6fJ39GQ-G_-UdjbZ-CW375EKjhiVVfNPcmAnsalqqXzg
https://redd.it/mo9rls
@r_linux
Hackingpassion
Learn Linux Through Man Pages
How cool would it be to learn Linux through the man pages To make it even more fun, I made this noscript with various options and with a cool retro terminal.
1650Ti Nvidia Kernel upgrade failure
apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n\] Y
Setting up initramfs-tools (0.136ubuntu6.4) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-5.8.0-48-generic (5.8.0-48.54\~20.04.1) ...
I: /boot/initrd.img.old is now a symlink to initrd.img-5.8.0-48-generic
Setting up linux-image-5.8.0-49-generic (5.8.0-49.55\~20.04.1) ...
I: /boot/initrd.img is now a symlink to initrd.img-5.8.0-49-generic
Processing triggers for initramfs-tools (0.136ubuntu6.4) ...
update-initramfs: Generating /boot/initrd.img-5.8.0-45-generic
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_ta.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sdma.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/vgubuntu-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.8.0-45-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation noscript subprocess returned error exit status 1
Processing triggers for linux-image-5.8.0-48-generic (5.8.0-48.54\~20.04.1) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.8.0-48-generic
...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.8.0-48-generic
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_ta.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sdma.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/vgubuntu-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.8.0-48-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.8.0-48-generic (--configure):
installed linux-image-5.8.0-48-generic package post-installation noscript subprocess returned error exit status 1
Processing triggers for linux-image-5.8.0-49-generic (5.8.0-49.55\~20.04.1) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.8.0-49-generic
...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating
apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n\] Y
Setting up initramfs-tools (0.136ubuntu6.4) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-5.8.0-48-generic (5.8.0-48.54\~20.04.1) ...
I: /boot/initrd.img.old is now a symlink to initrd.img-5.8.0-48-generic
Setting up linux-image-5.8.0-49-generic (5.8.0-49.55\~20.04.1) ...
I: /boot/initrd.img is now a symlink to initrd.img-5.8.0-49-generic
Processing triggers for initramfs-tools (0.136ubuntu6.4) ...
update-initramfs: Generating /boot/initrd.img-5.8.0-45-generic
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_ta.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sdma.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/vgubuntu-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.8.0-45-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation noscript subprocess returned error exit status 1
Processing triggers for linux-image-5.8.0-48-generic (5.8.0-48.54\~20.04.1) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.8.0-48-generic
...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.8.0-48-generic
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_ta.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sdma.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/vgubuntu-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.8.0-48-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.8.0-48-generic (--configure):
installed linux-image-5.8.0-48-generic package post-installation noscript subprocess returned error exit status 1
Processing triggers for linux-image-5.8.0-49-generic (5.8.0-49.55\~20.04.1) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.8.0-49-generic
...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating
/boot/initrd.img-5.8.0-49-generic
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_ta.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sdma.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/vgubuntu-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.8.0-49-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.8.0-49-generic (--configure):
installed linux-image-5.8.0-49-generic package post-installation noscript subprocess returned error exit status 1
Errors were encountered while processing:
initramfs-tools
linux-image-5.8.0-48-generic
linux-image-5.8.0-49-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@wallets-TUF-Gaming:\~#
https://redd.it/mpwmrp
@r_linux
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_ta.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sdma.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/vgubuntu-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.8.0-49-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.8.0-49-generic (--configure):
installed linux-image-5.8.0-49-generic package post-installation noscript subprocess returned error exit status 1
Errors were encountered while processing:
initramfs-tools
linux-image-5.8.0-48-generic
linux-image-5.8.0-49-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@wallets-TUF-Gaming:\~#
https://redd.it/mpwmrp
@r_linux
reddit
1650Ti Nvidia Kernel upgrade failure
apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 to...
Tilix theme for using in bright light conditions
I use my computer in the sun alot. I'm struggling to find a theme with colors that are easy to read.Most of the light theme uses a really bright colors of pink or yellow, which I'm unable to read. Recommendations?
https://redd.it/mpy8l2
@r_linux
I use my computer in the sun alot. I'm struggling to find a theme with colors that are easy to read.Most of the light theme uses a really bright colors of pink or yellow, which I'm unable to read. Recommendations?
https://redd.it/mpy8l2
@r_linux
reddit
Tilix theme for using in bright light conditions
I use my computer in the sun alot. I'm struggling to find a theme with colors that are easy to read.Most of the light theme uses a really bright...
Linux newbie - torrenting software?
I am not very tech savvy but I’ve recently downloaded Linux on VM for work as I’m learning OSINT
I am also interested in using it to torrent movies and music seeing as it’s on my personal (not work) laptop and seems safer than doing it on my usual operating system
I tried downloading soulseek for music but couldn’t work it out on the command terminal and I’d also like to get utorrent or something similar - can anyone help me?
https://redd.it/mpyf3x
@r_linux
I am not very tech savvy but I’ve recently downloaded Linux on VM for work as I’m learning OSINT
I am also interested in using it to torrent movies and music seeing as it’s on my personal (not work) laptop and seems safer than doing it on my usual operating system
I tried downloading soulseek for music but couldn’t work it out on the command terminal and I’d also like to get utorrent or something similar - can anyone help me?
https://redd.it/mpyf3x
@r_linux
reddit
Linux newbie - torrenting software?
I am not very tech savvy but I’ve recently downloaded Linux on VM for work as I’m learning OSINT I am also interested in using it to torrent...
CentOS is just shifted its life cycle position. CentOS is not dead
### Insteаd оf the wоrkflоw оrder being:
Fedоrа
↓
Red Hаt’s internаl develорment рrосess
↓
RHEL
↓
СentОS Linux
### Current Development Process:
Fedоrа
↓
СentОS Streаm
↓
RHEL
https://redd.it/mpy5x8
@r_linux
### Insteаd оf the wоrkflоw оrder being:
Fedоrа
↓
Red Hаt’s internаl develорment рrосess
↓
RHEL
↓
СentОS Linux
### Current Development Process:
Fedоrа
↓
СentОS Streаm
↓
RHEL
https://redd.it/mpy5x8
@r_linux
reddit
CentOS is just shifted its life cycle position. CentOS is not dead
### Insteаd оf the wоrkflоw оrder being: Fedоrа **↓** Red Hаt’s internаl develорment рrосess **↓** RHEL **↓** СentОS ...
A Call To Action For Linux Developers!
Yesterday I made a post asking people what they didn't like or wanted changed about Linux as a whole, this includes everything from the kernel to a specific distro or desktop. In this post I will outline some of the most prevalent problems people came up with, ranked in order of most discussed to least discussed. I am hoping that this post will serve as a call to arms for Linux developers (myself included) to solve this problems so we can improve the Linux experience as a whole.
​
Disclaimer: this most is merely a study of the data collected off of my previous post and an outline of what Linux "needs" most. Personally I believe Linux is nowhere near "complete" but these problems are the first step in forever improving it.
​
1. Audio and Bluetooth
one of the most common answers I received was people having trouble with Bluetooth or having problems with audio as a whole, I know that PipeWire is becoming more and more advanced and may overtake PulseAudio soon but audio and Bluetooth are definitely both places to focus on especially with many new Bluetooth and wireless audio devices being released.
​
2. GPU/Graphics issues
the second most common issue I received was graphics and GPU driver issues, a lot of this is out of our control with proprietary drivers being released and without Linux support. but optimization and perfecting what we do have is the key to a more enjoyable and usable Linux experience with less graphical based issues.
​
3. End User Experience and Cosmetic Polish
I understand this issue is mostly solving itself with the release of things like gnome40 and the endless amounts of customization artists and designers but many aspects of Linux can be made easier for the end user while still retaining the benefits their counterparts provide ie. using the terminal is very fast and efficient but very daunting for new users. this problem could mostly be solved through better documentation and support as well as making Linux feel less like a large en devour and more like a simple upgrade.
​
4. Accessibility and Hardware support
the final problem that I received commonly was issues related to accessibility and hardware support such as fingerprint readers, ID scanners, and even non external hardware like hard drives and sound chips. one of the most important things we can do to make Linux more common on the desktop would be removing many of the issues that unearth themselves right out of the box (especially in large companies using Linux on many workstation example: hospitals using badge scanners) solving this issue would result in more user friendly and less complicated setup and optimization.
5. Polish
On an important side note I think polishing the Linux experience both visually and with small quality of life updates is very important as it gives Linux a good first impression.
Important Links and Resources:
Linux Wiki how to submit patches how to submit drivers
https://redd.it/mq0phi
@r_linux
Yesterday I made a post asking people what they didn't like or wanted changed about Linux as a whole, this includes everything from the kernel to a specific distro or desktop. In this post I will outline some of the most prevalent problems people came up with, ranked in order of most discussed to least discussed. I am hoping that this post will serve as a call to arms for Linux developers (myself included) to solve this problems so we can improve the Linux experience as a whole.
​
Disclaimer: this most is merely a study of the data collected off of my previous post and an outline of what Linux "needs" most. Personally I believe Linux is nowhere near "complete" but these problems are the first step in forever improving it.
​
1. Audio and Bluetooth
one of the most common answers I received was people having trouble with Bluetooth or having problems with audio as a whole, I know that PipeWire is becoming more and more advanced and may overtake PulseAudio soon but audio and Bluetooth are definitely both places to focus on especially with many new Bluetooth and wireless audio devices being released.
​
2. GPU/Graphics issues
the second most common issue I received was graphics and GPU driver issues, a lot of this is out of our control with proprietary drivers being released and without Linux support. but optimization and perfecting what we do have is the key to a more enjoyable and usable Linux experience with less graphical based issues.
​
3. End User Experience and Cosmetic Polish
I understand this issue is mostly solving itself with the release of things like gnome40 and the endless amounts of customization artists and designers but many aspects of Linux can be made easier for the end user while still retaining the benefits their counterparts provide ie. using the terminal is very fast and efficient but very daunting for new users. this problem could mostly be solved through better documentation and support as well as making Linux feel less like a large en devour and more like a simple upgrade.
​
4. Accessibility and Hardware support
the final problem that I received commonly was issues related to accessibility and hardware support such as fingerprint readers, ID scanners, and even non external hardware like hard drives and sound chips. one of the most important things we can do to make Linux more common on the desktop would be removing many of the issues that unearth themselves right out of the box (especially in large companies using Linux on many workstation example: hospitals using badge scanners) solving this issue would result in more user friendly and less complicated setup and optimization.
5. Polish
On an important side note I think polishing the Linux experience both visually and with small quality of life updates is very important as it gives Linux a good first impression.
Important Links and Resources:
Linux Wiki how to submit patches how to submit drivers
https://redd.it/mq0phi
@r_linux
reddit
What is a problem/minor pet peeve you have with Linux that you...
Just a disclaimer: when I say “Linux” I mean everything from a problem you have with the kernel to a typo in a man page or even an OS specific...