appreciation post

So I've been thinking about picking up one of those auxiliary screens that plug into your USB c connector to like monitor stuff.

I asked on r/Linux questions if anybody has used any of those auxiliary screens. You know a little 9 in 12 in ones that you can put in your computer or under your screen etc.

Has anybody done it in Ubuntu or Kuuntu?

I saw there is a package that you can install, and I know I'm going to get my ass kicked doing it! I've been getting my ass kicked since 1997 using Linux!

My ask is has anybody else done this and is there a quasi simpler way to do this.

TYIA

yesterday on ubuntu 26.04.1 lts fresh install with secureboot on automatically installed the nvidia 595 open drivers during the setup, it was a hassle-free experience, is it the same for kubuntu 26.04?

Hello, like the title says, every once in a while, seemingly randomly, my screen will go black for a few seconds. It's almost as if the display cable was disconnected for a second and then plugged back in. I'm not really sure how to troubleshoot this and I'm not sure if it's a kubuntu issue or a kde or and nvidia driver issue or something else.

My system is:

7800x3d

rtx 4070

kubuntu 26.04

It's infrequent which makes it a bit harder, but what can I do to troubleshoot this? Thanks.

After upgrading from 24.04 LTS to 26.04 LTS last week I've run into an issue with the nvidia driver not being installed properly.

• uname -a shows the active kernel as 7.0.0-1015-oem
• kernel 7.0.0-38-generic is also installed

When running ubuntu-driver install it detects that nvidia-driver-580 should be installed and goes ahead with the installation.

However, it builds it for kernel 7.0.0-38-generic (i.e. not the currently running kernel 7.0.0-1015-oem), but then updates the initramfs for 7.0.0-1015-oem:

``` Loading new nvidia/580.178.04 DKMS files... Building for 7.0.0-38-generic Building for architecture x86_64

Building initial module nvidia/580.178.04 for 7.0.0-38-generic ... Signing module /var/lib/dkms/nvidia/580.178.04/build/nvidia.ko ... Installing /lib/modules/7.0.0-38-generic/updates/dkms/nvidia.ko.zst ... update-initramfs: Generating /boot/initrd.img-7.0.0-1015-oem ```

In the end there are no modules in /lib/modules/7.0.0-1015-oem but instead in /lib/modules/7.0.0-38-generic.

Does anyone have an idea to get out of this place?

PS: I don't know why the -oem kernel is installed or used.
PPS: When I boot the -generic kernel, the nvidia driver is loaded.

Hei, I'm wondering if anyone else is experiencing issues with suspend (to ram) or with locked sessions? On my machine, each time a my displays go into stand-by and/or put machine into suspend, I can' t resume from it and I have to do a hard reboot.

I've had claude take a look at the logs and it came up with this:

1. When the screens turn off (30 s after locking, from TurnOffDisplayIdleTimeoutWhenLockedSec=30 in ~/.config/powerdevilrc), your MSI MPG 274URDFW goes into standby. It drops its DisplayPort link and its built-in USB hub. Linux sees that as the monitor being unplugged.

2. KWin then reconfigures the outputs. Inside the NVIDIA driver, that call waits on the GPU's on-board firmware processor (GSP), and the firmware never answers.

3. KWin gets stuck inside the kernel. The nvidia-modeset thread then blocks behind it (INFO: task nvidia-modeset blocked … likely last held by task kwin_wayland).

4. All display output is frozen. Ctrl+Alt+F2 needs the same stuck driver, so it can't work either. The machine itself is still running: the kernel kept logging after each freeze.

It then recommends to downgrade to nvidia-driver-610 version ..

I'm currently on: Kubuntu 26.04.1 LTS / 7.0.0-38-generic / nvidia-driver-615-open

With 26.10 coming this week I was looking at what the update has, it does seem interesting enough to try it. I'm currently in 26.04LTS

Are there any downsides or risks when switching to an interim version? I'm aware you can't go back to LTS so my plan was to keep updating until the next LTS version comes out and so on.

What are the major differences between the interim and LTS? or is it just more of a background thing?

My computer is my normal daily PC where I watch, browse, download and game.

During my experience whit KDE plasma, I always wanted to make a custom task switcher. I have looked through the tutorial on [KDE.org](http://KDE.org), and sailed the web in search of a more in depth explanation for it, or something that is close to what I would want, but at the end it was only time lost.

Are custom task switchers unpopular?

Is there a more in depth tutorial online?

Thank you for your support.

As it states in the title, the firmware that kubuntu ships with won't update past 2021***

sudo apt install firmware-iwlwifi
firmware-iwlwifi is already the newest version (20210315-3).

As you can see, that's quite outdated. That said it was working last night but this isn't the first time this issue showed up.

The temporary fix is to pull the deb from here and install from the directory but it would be nice if there was an official fix for this. (I have yet to figure out how to add the one thing into the sources list but that's a later problem)

Edit: I did notice that the above conflicts with linux-firmware so I have removed that and still am running into issues with it not working or being picked up in lspci though the blutooth works fine.... Onto the network manager I suppose..

Since I landed on Kubuntu a few months ago as my distro of choice, I've had the option to run it with Wayland or x11. At first I ran Wayland but found that some of the apps I use weren't running right. So thru a little online research I found out that I could choose between the older x11 and the newer Wayland. Since I started using x11 everything has run right even as Kubuntu itself has been updated. I'm using a MSI Gf65 thin with a 10th gen i5 and a GTX 1650 Max Q for graphics. I mostly game on Steam, surf the web using Firefox, and dabble a bit with OBS and audacity.

I was using the edit application to change the icon for Firefox, and while I was in the Menu Editor, I accidently clicked on delete. Now I can't find the Firefox application anywhere when I click on Application Launcher. Can someone help me fix this please? Thanks.

I installed Kubuntu on a Dell XPS 13 9350 using a 64GB USB drive,I ran into an issue during my first installation attempt because my old 8GB USB drive was only USB 2.0, so I got a new 64GB USB 3.0 drive and flashed it using BalenaEtcher. I then set up Kubuntu to see what it was like—this was my first time installing it on actual hardware, as I had previously only used virtual machines—and I'm dual-booting it with Windows 10.

posser(joke) :D

I have set this on After rebooting but it is more annoying than immediately. Does it an actual difference?
Also do you create Timeshift backups before big updates?

I was attempting to disable/remove 3rd party packages to fix my noble to resolute upgrade as per my previous post: https://www.reddit.com/r/Kubuntu/comments/1x28fc3/task_manager_refuses_to_load/

I tried to follow this tutorial https://dredyson.com/fix-how-to-disable-non-ubuntu-repositories-and-remove-third-party-packages-in-under-5-minutes-the-complete-quick-fix-guide-that-actually-works/ https://dredyson.com/fix-how-to-disable-non-ubuntu-repositories-and-remove-third-party-packages-in-under-5-minutes-the-definitive-quick-fix-guide-that-actually-works/

It got my OS into a state where it couldn't get past the splash.

I tried to fix it with recovery mode (mostly dpgk option and in terminal apt update/upgrade/autoremove and attempting to restore my original package state with apt install $(cat ~/third_party_packages_backup.txt)). But now I cannot advance beyond picture above state.

Curious if anyone has used it yet?

Recently I fresh-installed Kubuntu 26.04.1 LTS (7.0.0-38-generic + Wayland) on my ThinkPad P14s Gen 5 AMD. I list what I fixed below:

Firstly, Wayland Picture-in-Picture protocol is still pending as of now, so Firefox PIP is basically unusable on KDE Plasma 6.6.6.

You have to add a window rule to regain the X11-equivalent experience. The following makes PIP windows on top of other windows and allows multiple ones to coexist:

Secondly, when you run AppImage applications, you may see the error message dlopen(): error loading libfuse.so.2. The reason is that the dependency package is not installed by default. Therefore, the quick fix is to execute sudo apt install libfuse2t64.

Thirdly, after I set scale to 150% in Display Configuration, VLC's menu bar seems a little larger compared to the one in Dolphin:

So you need to add the environment variable QT_SCALE_FACTOR=0.75 (0.75 is perfect in my case, YMMV) in KDE Menu Editor:

Lastly, if you find the system tray is blurry to your eyes like the upper one in the screenshot, append QT_SCALE_FACTOR_ROUNDING_POLICY=Round in ~/.profile and log out. The default value in Qt 6 is PassThrough (read the official Qt6 documentation for more).

Hopefully the post is helpful.

This is after an upgrade to the newest lts. 26.04.1 this also occurs on a fresh live boot usb.

Cpu: amd ryzen 5000 series

Gpu : 6700xt

I've already tried reinstalling the gpu drivers. What are my next troubleshooting steps?

Ps. Pc also occasionally freezes shortly after boot

Edit.

Live boot usb works properly on seperate pc. Amd ryzen 5800x3d Radeon 7900xtx

Is there any way this isn't the gpu dieing?