Kubuntu Forums - Forum

MS Edge opens but freezes

JamesKB — Sat, 15 Aug 2026 01:56:18 GMT

Dell Studio XPS 8100 with a 1 TB ssd, 16GB ram
OS: Kubuntu 26.04

I installed microsoft-edge-stable_151.0.4129.86-1_amd64.debb. It opens but then freezes. All I can do is close it. It never asks if I want to sync my shortcuts across all my devices. I cannot enter a url in the address bar. Nothing works. All I can do is close it. Ideas?

Thank you for your time.
--
James

[System]Bullet Proof KDE

Snowhog — Fri, 14 Aug 2026 14:34:22 GMT

Ref: KDE, Kubuntu Focus and Techpaladin introduce “Bullet Proof KDE”, a KDE suite with three years of support

1. Does one get this only with a fresh installation, or does it come in with an upgrade to Kubuntu 26.04 LTS?

2. Is there a way to identify; to know; that you do have this?

KDE, Kubuntu Focus and Techpaladin introduce “Bullet Proof KDE”, a KDE suite with three years of support

claydoh — Fri, 14 Aug 2026 09:57:35 GMT

KDE, Kubuntu Focus and Techpaladin introduce “Bullet Proof KDE”, a KDE suite with three years of support

Kubuntu Focus, Techpaladin Software, and KDE e.V. announced today the "bullet-proof KDE Software initiative”, designed to provide a minimum of three years of bug fixes and security updates for Plasma 6.6 LTS and related KDE software. The goal is to provide the capability and stability that professionals, companies, and public institutions require to replace proprietary operating systems with one that respects their autonomy, privacy, and security.

A $100K Commitment for Stability and Reliability
To spearhead this initiative, Kubuntu Focus has committed over $100K in direct payments to Techpaladin, KDE e.V. and developers over 3 years. This funds the continuous improvement and support of Plasma 6.6 LTS (Long-Term Support) and the associated Frameworks libraries and Gear apps. It also includes payments to KDE e.V. to sponsor three additional nodes on their continuous integration (CI) infrastructure to validate KDE software on Kubuntu 26.04 LTS over the support period. Together with Kubuntu and the Focus team, they are already identifying, improving, and releasing bug and security fixes.

Why This Matters
Users wanting the KDE desktop can select a distribution featuring the newest release or one providing an older release. While the newest release may bring new features and fixes for old bugs, it can also introduce new bugs and regressions — a risk for all new software. If a user selects a distribution with a fixed KDE release, it can be quite stable, but if that release is no longer supported, it may not receive security or bug fixes. This initiative offers an option that provides the best of both: a stable, sponsored KDE release with active security and bug fixes throughout the 3-year Kubuntu 26.04 LTS support period.

Where to Get It
The "bullet-proof KDE Software Suite” is currently distributed with Kubuntu 26.04 LTS. However, the open-source initiative is designed as a collaborative effort, and other vendors are encouraged to sponsor, distribute, and contribute to this project to further strengthen the ecosystem. Interested parties can contact: contact@techpaladinsoftware.com or bizdev@kfocus.org.

Full press release HERE

Nate Graham's post What a real LTS looks like: Kubuntu 26.04

tl;dr KDE, Kubuntu Focus, and Techpaladin bring back an LTS version with Plasma 6.6, providing three years' support on not only Plasma, but Frameworks and KDE gear as well. And guess who is pretty much the only place that as it at the moment.

[Hardware]Is there a way too force hardware to fail, instead of interminable retries?

jlittle — Wed, 12 Aug 2026 21:25:31 GMT

I've been recovering mostly pictures from old CD-ROMs, using an old (about twenty years) DVD drive.

My problem is that when CDs can't be read, the device keeps retrying, and the only way to stop it is to shutdown. Even a reboot can fail to stop the drive retrying endlessly.

Is there a way to force an error on the device? The shutdown sequence does so.

anyone else having issues with the last update?

skyfishgoo — Wed, 12 Aug 2026 17:25:13 GMT

had to restore from a timeshift snapshot after applying this update in discover.... two most likely suspects are highlighted.

[Software]Solid-action: Can we choose the file type ?

alkderito — Wed, 12 Aug 2026 16:06:45 GMT

Hello,

Is it possible to select the file type in Solid-Action where it says “Opposable” in the photo ?

[SOLVED]Upgrade from 25.10 failing to boot with memory error - and no keyboard/mouse after fixing boot issue

oshunluvr — Wed, 12 Aug 2026 15:19:46 GMT

I have been attempting to upgrade my laptop from 25.10 Kubuntu to 26.04 three times so far with no success. Each time I get

Code:

error: out of memory. Press any key to continue..._

followed by

Code:

KERNEL PANIC... VFS: Unable to mount root fs on UUID=..."

AI is, as always totally useless.

Attempting booting into recovery mode the results are the same with an additional message of "Loading initial ramdisk..." prior to the above errors.

My belief is that initramfs is failing to load (the "out of memory" error) thus, the boot drive cannot be mounted and used (the kernel panic).

The initrd.img prior to upgrade is 222mb and after 298.3mb. These are both quite large IME but this machine has an nVidia video card so the dkms drivers take up some space. By comparison, my desktop PC with an AMD video card has a 70mb initrd,img.

The laptop specs:

Lenovo Yoga 730-15IKB
Intel i7-8550u
16GB RAM
1tb Samsung nvme
secure boot disabled.

I have seen/heard about this error before, but it's been many years. Thanks to a working, fresh 26.04 install, I have the ability to roll-back to the un-updated 25.10, but after three tries I'm searching for a final solution. I'd prefer to use an upgraded install rather than having to redo everything on a new install.

I currently am not using the nvidia and instead are using the built-in Intel video to save battery life so I'm considering just removing the nVIdia drivers altogether and re-upgrading, but that's a temporary hack, not a solution.

Is it possible that the/boot/efi partition size is an issue? It's currently 256mb w/217mb available but the initrd.img on the working 25.10 install is over the available size also at 222mb.

[Pre-Install]Translation problem on the livecd with Kubuntu 26.04

alkderito — Wed, 12 Aug 2026 11:47:01 GMT

Hello,

I don’t understand on the live cd of the previous version it was the same on 3 versions at least.

When you arrive at the selection of the language in the livecd of Kubuntu, you have the choice of the language that appears but when you select the French language, here is what puts in the image that I present here :

Normally, the buttons and registration should be in French, I think. He had the same problem with the previous LTS version. Do you have any idea?

[System]How can I make the blurred background image on the login screen transparent?

greenster — Wed, 12 Aug 2026 11:30:27 GMT

How can I make the blurred background image on the login screen transparent?

Moving from openSUSE Leap to Kubuntu (and to Wayland)

anandrajan — Tue, 11 Aug 2026 16:06:40 GMT

I’ve been running SUSE/openSUSE since late 2003 (following a Linux journey that began with Slackware in 1995 and then RedHat in 1996). With openSUSE transitioning toward ALP (which I affectionately call the alien linux platform), I decided to switch my primary workstation to Kubuntu 26.04 LTS. Here are my installation impressions and a question regarding Wayland vs. X11.

Hardware:

Motherboard: ASUS Prime X299-A II
GPU: NVIDIA GeForce RTX 4090
Storage: NVMe M.2 (2TB)
CPU / Network: Standard high-end desktop configuration

Installation Impressions: I was previously running openSUSE Leap 15.6 on the 2TB NVMe drive. I booted the Kubuntu 26.04 installer aiming to expand my / partition (formatted as ext4). While the GUI partitioning step offered repartitioning options, the layout changes didn't take, so I opted to reuse the existing partition structure while explicitly leaving /home unformatted.

I stuck with the open-source Nouveau driver during the installation. At the very end of the installation process, the monitor showed line artifacts and began blinking during session teardown. I had to trigger a manual reboot and expected to re-do the install, but to my pleasant surprise, the base system installed successfully! My /home directory remained intact, and after booting in, I immediately installed the proprietary NVIDIA 595.84 drivers.

The Wayland / Gamma / SDDM Friction: Out of the box, Kubuntu 26.04 defaulted to Plasma 6 on Wayland. Coming from openSUSE (where I relied on nvdock), I immediately hit a wall: under Wayland, hardware color ramps and gamma adjustments inside nvidia-settings and kgamma are unavailable. At the ripe young age of 65, default display brightness without fine-grained gamma correction is a dealbreaker for my eyes.

Furthermore, logging out from the Wayland session produced a black screen with two unrendered, unreadable icon outlines (< and another symbol)—a result of KWin's logout greeter overlay failing to render cleanly over the display manager handoff.

Question for the Community: Since Kubuntu 26.04 ships Wayland-only by default on the ISO, what is the officially recommended procedure to install and switch back to a native Plasma (X11) session?

Specifically:

Which meta-packages (plasma-workspace-x11, xorg, etc.) should be pulled from the universe repositories for a clean X11 desktop?
Is X11 still recommended for users who require hardware gamma controls (kgamma/nvidia-settings) and rock-solid session teardowns on modern NVIDIA GPUs until Wayland compositor protocols mature?

Thanks for any insight!

AMD A8-7680 APU wont play nice so im stuck in safe graphics mode

Old and Confused — Mon, 10 Aug 2026 11:35:42 GMT

Ok so its a fresh install of 26 04 lts had to do it in safe graphics mode. All installed no issue. Reboot got past the logo and black screen nothing no f keys or anything i could think of would work. Had to hard reset and Held shift key and modified the boot to nomodeset this got me to the log in and I changed the nano grub settings to the same. I can boot in now but the resolution is 800/600 and nothing fits on the screen LOL Help. Contrary to above I have no idea what im doing what little i know is from weeks of google and note taking LOL please explain a simply as you can as this may as well be in klingon for all i can understand.

Interesting ffmpeg vs. NFS vs. Kdialog behavior while using a VM.

oshunluvr — Sun, 09 Aug 2026 19:46:55 GMT

TL/DR: Re-encoding some mkv and mp4 videos on a VM using ffmpeg via a Dolphin service menu, The source and target file locations were on a NFS server connected to a Kubuntu26.04 VM using QEMU/KVM. The encoding completed successfully, but the VM (via kdialog) never acknowledged the task was finished even though the resulting output files were "closed" successfully. I'm kinda curious where the "break" occurred.

The setup: My desktop PC running KDEneon. A QEMU/KVM virtual machine on the desktop re-encoding files using ffmpeg. Both the PC and VM are accessing the files on my server via NFS v4.2.

The reason: I'm trying to re-encoding several hundred mp4 files and convert a few dozen other mkv to mp4 - primarily to reduce storage usage. ffmpeg keeps crashing on KDEneon if I try to process more than 2-3 files at a time. while also using Handbrake. I decided to try a newer version of ffmpeg to see if that worked better. KDEneon has a much older version of ffmpeg than Kubuntu 26.04 (6.1.1-3ubuntu5 vs. 8.0.1-2ubuntu2 ) but I didn't want to mess about trying to upgrade ffmpeg on KDEneon. So I decided to try using Kubuntu 26.04 in a VM. All of this was additionally complicated as I was simultaneously using Handbrake to also help complete this task on y PC (but not on the VM - yet ). I have enough CPU and RAM to encode more than one file at a time but Handbrake only does one at a time. So I thought I might speed things up by having ffmpeg directly re-encoding the files that were simple enough not to need special settings.

What I did: I already had an updated Kubuntu 26.04 VM so I added my Dolphin Service Menu that I wrote to make this task easier to the VM. I then mounted the NFS file system from the server on the VM. This enabled me to operate in the VM just as I has been on my desktop. I selected a few files and launched ffmpeg. The kdialog progress box popped open and encoding commenced as expected.

The results: The files on both machines (real and virtual) were encoded as expected, but for some reason - only on the VM - the kdialog box never closed as it does on the desktop machine. I verified the output files were viewable and thus "closed" my ffmpeg, but the dialog remained open on the VM as though the files were still being processed.

The question: What causes kdailog to not receive the signal that ffmpeg is done when using it on the VM? Is it the ffmpeg version difference, a difference in how NFS is mounted, or some other wrench in the works?

More detail:
Here's the Dolphin service menu contents:

Code:

[Desktop Entry]
Type=Service
Icon="/usr/share/icons/breeze/mimetypes/32/video-mp4.svg"
X-KDE-ServiceTypes=KonqPopupMenu/Plugin
MimeType=video/*;
Actions=g-copy;g-rate24;g-rate28;
Encoding=UTF-8

[Desktop Action g-copy]
Name=Re-encode Video
Icon=/usr/share/icons/breeze/mimetypes/32/video-mp4.svg
Exec=dbusRef=$(kdialog --icon "/usr/share/icons/breeze/actions/24/convert.svg" --title="Conversion ffmpeg" --progressbar " Converting $(basename %f) " 0); fn=%u; ffmpeg -i %u -y -vcodec libx265 "${fn%.*}"-conv.mp4; qdbus $dbusRef close; kdialog --title "Conversion complete" --passivepopup "$(basename %f) converted to MP4";

[Desktop Action g-rate24]
Name=Re-encode w/rate 24
Icon=/usr/share/icons/breeze/mimetypes/32/video-mp4.svg
Exec=dbusRef=$(kdialog --icon "convert.svg" --title="Conversion ffmpeg" --progressbar " Converting $(basename %f) " 0); fn=%u; ffmpeg -i %u -y -vcodec libx265 -crf 24 "${fn%.*}-24".mp4; qdbus $dbusRef close; kdialog --title "Conversion complete" --passivepopup "$(basename %f) converted to MP4";

[Desktop Action g-rate28]
Name=Re-encode w/rate 28
Icon=/usr/share/icons/breeze/mimetypes/32/video-mp4.svg
Exec=dbusRef=$(kdialog --icon "convert.svg" --title="Conversion ffmpeg" --progressbar " Converting $(basename %f) " 0); fn=%u; ffmpeg -i %u -y -vcodec libx265 -crf 28 "${fn%.*}-28".mp4; qdbus $dbusRef close; kdialog --title "Conversion complete" --passivepopup "$(basename %f) converted to MP4";

This allows me to select a video file and either convert it to mp4 (action "g-copy"), re-encode it using the .H265 rate of "24" ( action "g-rate24" - smaller than default), or re-encode it using the .H265 rate of "28" (action "g-rate28 - much smaller than default). All 3 options work as I desire.

The main PC has the NFS shared mounted via fstab. The VM is manually mounted because I didn't need it to access the NFS server all the time.

The only difference - other than the KDEneon version of ffmpeg crashing randomly - is the kdialog on the native KDEneon system closes when the file is done and messages me when each file is complete. The VM does not acknowledge that the file encoding is done. I have to manually verify the destination file is OK by launching it VLC, then "cancel" the action on the VM using the kdialog box.

Mount options on server:

Code:

server:/Videos on /shared/Videos type nfs4 (rw,noatime,nodiratime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,soft,fatal_neterrors=none,proto=tcp,nconnect=16,timeo=20,retrans=5,sec=sys,clientaddr=192.168.1.199,local_lock=none,addr=192.168.1.250)

Mount options on VM:

Code:

server:/Videos on /shared/Videos type nfs4 (rw,noatime,nodiratime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,fatal_neterrors=none,proto=tcp,nconnect=16,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.199,local_lock=none,addr=192.168.1.250)

The above almost Identical.

Currently testing the VM running six simultaneous conversions at once.

funny linux memes

die.boer — Sun, 09 Aug 2026 08:11:50 GMT

some memes , cause i'm bored ...

[RESOLVED]Kubuntu boot screen?

JamesKB — Sun, 09 Aug 2026 00:18:54 GMT

OS: Kubuntu 26.04
Kubuntu is installed
Kubuntu is the only OS installed
KDE Plasma ver 6.6.4

Every time I boot my computer I get a strange message. I don't know if this is normal. It displays for 30-60 seconds then displays the normal login screen.

This is the message on a black screen and white text:

>>Checking Media Presence.......
>>Media Present......
>>Start PXE over IPv4.

Is this normal?

Thanks for your time.
--
James

[Software]Launcher Error

GerardV — Sat, 08 Aug 2026 00:50:22 GMT

My install, 26.04 with backports enabled has developed this strange error where the Application Launcher will slowly resize itself to its full length without me touching it.
I can drag it back and it will stay there, but will do the same thing the next time.
The system is up to date and i have removed and and re-installed the launcher.
Anyone else seeing this?