Kubuntu Forums - Kubuntu Forums .Net

More Nebula...

StarWolf — Mon, 25 May 2026 12:04:50 GMT

Link to non colored https://www.opendesktop.org/p/2360615/

Colored link https://www.opendesktop.org/p/2360616/

libkf6activities Package

cchipdive — Mon, 25 May 2026 00:10:59 GMT

So I'm trying to install libkf6activities and apt is not finding it at all. Can anyone give me a package? (OS is Kubuntu 26.04 LTS)

Security cameras with Kubuntu?

Qqmike — Sun, 24 May 2026 22:54:21 GMT

I'm new to all this. Just investigating, pre-purchase.
Suppose you set up a couple solar, WiFi, home security cameras.
Two leading companies are Eufy and Reolink.

Option#1 is to totally use your cell phone(s) to do everything --
view live/recorded footage from the camera(s); get firmware updates on-line using the camera's app. Correct?

Option #2 -- and this is my question --
Using your Kubuntu OS, are you able to view live/recorded footage through Firefox or Chromium?
(You can do this with Windows OSs.)
The on-line searches I've seen are not real clear on this.
Some users in [camera] "community" websites indicate they are not able to do so with Linux (Ubuntu).

Atheros wifi adapter keeps dropping in 26.04

zpiatek — Sun, 24 May 2026 21:42:25 GMT

I'm sharing an issue I submitted at https://bugs.launchpad.net/ubuntu/+bug/2154089.

Hello, I need to report a bug in K/Ubuntu 26.04 running on a Dell Inspiron 2350.

This PC runs fine with K/Ubuntu 25.10 and previous versions, but when I try 26.04, the wifi adapter will drop after a few second, then connect again. The cycle repeats.
A popup on the screen reads:

Network Management
Wireless Interface (wlp4so)
Authorization supplicant timed out.

I tried to file an apport when I ran ubuntu-bug but the connection problem won't allow it.

The wifi adapter is a Qualcomm Atheros QCA 95565/AR9565 wireless adapter. The kernel driver is ath9k.

I tried running a few commands when I researched the problem in https://launchpad.net/ubuntu, but didn't see one posted for 26.04.

Again, this runs fine on Kubuntu 25.10 and previous. Could this be a Linux 7 issue?

Any help would be greatly appreciated, and thank you in advance!

deleting read-only USB partition

papapenguin — Sun, 24 May 2026 19:56:20 GMT

I made a backup using Kup on a USB drive (so I can update to 26.04).

Now I can't access that USB nor write a new backup to it. I can't mount it, remount it or delete it via GParted or Partition Manager.

It seems like it's never been mounted...

donald@donald:~$ sudo mkfs.ext4 /dev/sda1 #For ext4
mke2fs 1.47.0 (5-Feb-2023)
/dev/sda1 contains a ext4 file system
last mounted on /media/donald/0dbeacc9-c3d7-4d6a-912a-d5283bd3da78 on Mon Dec 1 13:30:24 2025
Proceed anyway? (y,N) y
/dev/sda1: Read-only file system while setting up superblock

donald@donald:~$ sudo fdisk -l

Device BootStart End Sectors SizeIdType
/dev/sda1 18944 484362239 484343296 231G 83 Linux

Thank you to our contributors

Snowhog — Sat, 23 May 2026 21:21:35 GMT

Contributors to KFN are of two types: Members who actively engage in trying to help others with their issues, and members who contribute financially towards KFN to ensure it remains online. Both are much appreciated.

Members who actively engage in trying to help others are what makes KFN what it is; a community sharing a common bond in their use of, and support of, Kubuntu Linux in particular, and Linux in general.

Members who are able to express their belief in the value of keeping KFN online by supporting us with their hard earned dollars via purchases of our Paid Subscriptions are especially appreciated.

KFN started making Paid Subscriptions available on 19 March 2012. That was 14-years ago. In that time, members who have stepped up to support us with purchases of Paid Subscriptions have contributed $9,722.00 dollars to KFNs continuing expenses. This is the result of 203 individual purchases (just shy of 15 Paid Subscriptions purchases per year) and just shy of $695.00 annually.

I've said this before, but it goes without saying: Keeping an online presence doesn't come cheap. The biggest expense is our hosting costs (Linode). The next biggest expense is the license fees for using vBulletin. Additional costs come from equipment for off-line backups (the Cloud isn't the total panacea it is touted to be). Our host, Open Source, isn't "making money" from Paid Subscriptions. Funds raised go explicitly to maintaining KFN on-line.

[Software]Virtual Keyboard at SDDM Login Screen

Snowhog — Sat, 23 May 2026 19:15:56 GMT

The button is present, but clicking on it does nothing. Is Virtual Keyboard only supported on a Touch Screen devices? I've Googled on this, and tried the several 'fixes', none of which resulted in bringing up a Virtual Keyboard on the SDDM Login Screen. I don't need one, but it would be nice, given the button is presented, if it actually worked.

Snap / Deus?

Shibblet — Fri, 22 May 2026 19:41:39 GMT

I just noted something... "snap", upside down, looks like "deus."

Make of this what you will.

Bluetooth issues on Kubuntu 26.04

element18 — Fri, 22 May 2026 18:34:37 GMT

Hello everyone,

A bit of background: just recently made the decision to switch from Windows 11 to Linux, and I settled on Kubuntu. I installed Kubuntu 26.04 on my recently purchased laptop. It feels very modern, snappy, and a joy to use as a complete Linux beginner. Installation was straightforward except for one small but important issue. Bluetooth does not seem to be working properly, if at all, prompting me to make my first post on this forum. Although I can see the bluetooth option, whenever I hit the switch to turn it on, it still says disabled. In the bluetooth configuration tool, there is no difference between the enabled and disabled state as the panel simply displays "disabled".

Here is the inxi output:

Code:

System:
  Host: afloresrLIN Kernel: 7.0.0-15-generic arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.6.4 Distro: Kubuntu 26.04 LTS (Resolute Raccoon)
Machine:
  Type: Laptop System: LENOVO product: 21QA0036US v: ThinkPad X9-14 Gen 1
    serial: 
  Mobo: LENOVO model: 21QA0036US v: SDK0T76576 WIN
    serial:  Firmware: UEFI vendor: LENOVO
    v: N4DET39W (1.22 ) date: 02/11/2026
Battery:
  ID-1: BAT0 charge: 30.3 Wh (54.6%) condition: 55.5/55.1 Wh (100.7%)
    volts: 11.68 min: 11.7
CPU:
  Info: 8-core model: Intel Core Ultra 7 268V bits: 64 type: MCP cache:
    L2: 14 MiB
  Speed (MHz): avg: 1108 min/max: 400/5000:4900:3700 cores: 1: 1108 2: 1108
    3: 1108 4: 1108 5: 1108 6: 1108 7: 1108 8: 1108
Graphics:
  Device-1: Intel Lunar Lake [Intel Arc Graphics 130V / 140V] driver: xe
    v: kernel
  Display: wayland server: Xwayland v: 24.1.10 compositor: kwin_wayland
    driver: gpu: xe resolution: 2880x1800~120Hz
  API: EGL v: 1.5 drivers: iris,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 26.0.3-1ubuntu1
    renderer: Mesa Intel Graphics (LNL)
  API: Vulkan v: 1.4.341 drivers: intel,llvmpipe surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo,
    xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Lunar Lake IPU driver: N/A
  Device-2: Intel Lunar Lake-M HD Audio driver: sof-audio-pci-intel-lnl
  API: ALSA v: k7.0.0-15-generic status: kernel-api
  Server-1: PipeWire v: 1.6.2 status: active
Network:
  Device-1: Intel BE201 320MHz driver: iwlwifi
  IF: wlp0s20f3 state: up mac: 80:13:16:1f:24:3a
Bluetooth:
  Device-1: Intel driver: btintel_pcie
  Report: hciconfig ID: hci0 rfk-id: 1 state: down
    bt-service: enabled,running rfk-block: hardware: no software: yes
    address: 00:00:00:00:00:00
Drives:
  Local Storage: total: 953.87 GiB used: 12.63 GiB (1.3%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZAL81T0HFLB-00BLL
    size: 953.87 GiB
Partition:
  ID-1: / size: 334.38 GiB used: 12.62 GiB (3.8%) fs: ext4 dev: /dev/nvme0n1p6
  ID-2: /boot/efi size: 1022 MiB used: 8.1 MiB (0.8%) fs: vfat
    dev: /dev/nvme0n1p5
Swap:
  ID-1: swap-1 type: file size: 512 MiB used: 0 KiB (0.0%) file: /swapfile
Sensors:
  System Temperatures: cpu: 40.0 C mobo: N/A
  Fan Speeds (rpm): fan-1: 0 fan-2: 0
Info:
  Memory: total: 32 GiB note: est. available: 30.87 GiB used: 4.74 GiB (15.4%)
  Processes: 425 Uptime: 6h 13m Shell: Bash inxi: 3.3.40

I also found similar post, but on older Ubuntu support forms. One user requested info from the command

Code:

 sudo dmesg | grep -i bluetooth

which is quite long:

Code:

[    2.831725] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
[    2.915741] Bluetooth: Core ver 2.22
[    2.924668] NET: Registered PF_BLUETOOTH protocol family
[    2.924675] Bluetooth: HCI device and connection manager initialized
[    2.924681] Bluetooth: HCI socket layer initialized
[    2.924683] Bluetooth: L2CAP socket layer initialized
[    2.924692] Bluetooth: SCO socket layer initialized
[    3.131283] Bluetooth: hci0: Device revision is 0
[    3.131286] Bluetooth: hci0: Secure boot is enabled
[    3.131287] Bluetooth: hci0: OTP lock is disabled
[    3.131288] Bluetooth: hci0: API lock is enabled
[    3.131288] Bluetooth: hci0: Debug lock is disabled
[    3.131289] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    3.131290] Bluetooth: hci0: Bootloader timestamp 2023.33 buildtype 1 build 45995
[    3.131837] Bluetooth: hci0: Found device firmware: intel/ibt-0190-0291-iml.sfi
[    3.131840] Bluetooth: hci0: Boot Address: 0x30098800
[    3.131840] Bluetooth: hci0: Firmware Version: 107-8.26
[    3.191602] Bluetooth: hci0: Waiting for firmware download to complete
[    3.191606] Bluetooth: hci0: Firmware loaded in 58366 usecs
[    3.193842] Bluetooth: hci0: Waiting for device to boot
[    3.193873] Bluetooth: hci0: Device booted in 2208 usecs
[    3.193874] Bluetooth: hci0: Waiting for device transition to d0
[    3.193875] Bluetooth: hci0: Device moved to D0 in 0 usecs
[    3.194165] Bluetooth: hci0: dsbr: enable: 0x01 value: 0x0b
[    3.196522] Bluetooth: hci0: Found device firmware: intel/ibt-0190-0291-pci.sfi
[    3.196531] Bluetooth: hci0: Boot Address: 0x10000800
[    3.196533] Bluetooth: hci0: Firmware Version: 107-8.26
[    3.219792] Bluetooth: hci0: Received gp1 mailbox interrupt
[    3.363859] Bluetooth: hci0: Received gp1 mailbox interrupt
[    3.379643] Bluetooth: hci0: Received gp1 mailbox interrupt
[    3.390905] Bluetooth: hci0: Received gp1 mailbox interrupt
[    3.400159] Bluetooth: hci0: Received gp1 mailbox interrupt
[    3.449742] Bluetooth: hci0: Received gp1 mailbox interrupt
[    3.449883] Bluetooth: hci0: Received gp1 mailbox interrupt
[    3.453865] Bluetooth: hci0: Received gp1 mailbox interrupt
[    3.454150] Bluetooth: hci0: Received gp1 mailbox interrupt
[    3.457536] Bluetooth: hci0: Received gp1 mailbox interrupt
[    3.457673] Bluetooth: hci0: Received gp1 mailbox interrupt
[    3.763998] Bluetooth: hci0: Received gp1 mailbox interrupt
[    3.764503] Bluetooth: hci0: Received gp1 mailbox interrupt
[    3.797153] Bluetooth: hci0: Waiting for firmware download to complete
[    3.797156] Bluetooth: hci0: Firmware loaded in 586554 usecs
[    3.832880] Bluetooth: hci0: Received gp1 mailbox interrupt
[    3.832913] Bluetooth: hci0: Controller in error state
[    4.709061] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    4.709069] Bluetooth: BNEP filters: protocol multicast
[    4.709074] Bluetooth: BNEP socket layer initialized
[    6.850639] Bluetooth: hci0: Timeout (3000 ms)  on alive interrupt, alive context: intel_reset1
[    6.850660] Bluetooth: hci0: Failed to send frame (-62)
[    6.850661] Bluetooth: hci0: sending frame failed (-62)
[    6.850680] Bluetooth: hci0: Failed to send Intel Reset command
[    6.850691] Bluetooth: hci0: Intel Soft Reset failed (-62)
[    6.850696] Bluetooth: hci0: Firmware download retry count: 1
[    6.889198] Bluetooth: hci0: Device revision is 0
[    6.889205] Bluetooth: hci0: Secure boot is enabled
[    6.889207] Bluetooth: hci0: OTP lock is disabled
[    6.889208] Bluetooth: hci0: API lock is enabled
[    6.889208] Bluetooth: hci0: Debug lock is disabled
[    6.889209] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    6.889211] Bluetooth: hci0: Bootloader timestamp 2023.33 buildtype 1 build 45995
[    6.889541] Bluetooth: hci0: Found device firmware: intel/ibt-0190-0291-iml.sfi
[    6.889544] Bluetooth: hci0: Boot Address: 0x30098800
[    6.889545] Bluetooth: hci0: Firmware Version: 107-8.26
[    6.944220] Bluetooth: hci0: Waiting for firmware download to complete
[    6.944241] Bluetooth: hci0: Firmware loaded in 53416 usecs
[    6.946563] Bluetooth: hci0: Waiting for device to boot
[    6.946566] Bluetooth: hci0: Device booted in 2248 usecs
[    6.946569] Bluetooth: hci0: Waiting for device transition to d0
[    6.946570] Bluetooth: hci0: Device moved to D0 in 1 usecs
[    6.947150] Bluetooth: hci0: dsbr: enable: 0x01 value: 0x0b
[    6.951402] Bluetooth: hci0: Found device firmware: intel/ibt-0190-0291-pci.sfi
[    6.951425] Bluetooth: hci0: Boot Address: 0x10000800
[    6.951429] Bluetooth: hci0: Firmware Version: 107-8.26
[    6.964659] Bluetooth: hci0: Received gp1 mailbox interrupt
[    6.964785] Bluetooth: hci0: Received gp1 mailbox interrupt
[    6.992169] Bluetooth: hci0: Received gp1 mailbox interrupt
[    7.051268] Bluetooth: hci0: Received gp1 mailbox interrupt
[    7.051435] Bluetooth: hci0: Received gp1 mailbox interrupt
[    7.434444] Bluetooth: hci0: Received gp1 mailbox interrupt
[    7.434612] Bluetooth: hci0: Received gp1 mailbox interrupt
[    7.539240] Bluetooth: hci0: Waiting for firmware download to complete
[    7.539253] Bluetooth: hci0: Firmware loaded in 574065 usecs
[    7.575058] Bluetooth: hci0: Received gp1 mailbox interrupt
[    7.575089] Bluetooth: hci0: Controller in error state
[   10.562724] Bluetooth: hci0: Timeout (3000 ms)  on alive interrupt, alive context: intel_reset1
[   10.562736] Bluetooth: hci0: Failed to send frame (-62)
[   10.562738] Bluetooth: hci0: sending frame failed (-62)
[   10.562784] Bluetooth: hci0: Failed to send Intel Reset command
[   10.562788] Bluetooth: hci0: Intel Soft Reset failed (-62)
[   10.609016] Bluetooth: hci0: Received hw exception interrupt
[   10.609050] Bluetooth: hci0: Received gp1 mailbox interrupt
[   10.610174] Bluetooth: hci0: Unsupported cnvi 0x00000000
[   10.611239] Bluetooth: hci0: Received gp1 mailbox interrupt
[   10.611290] Bluetooth: hci0: Controller in error state
[   11.066877] Bluetooth: hci0: Timeout (500 ms) on tx completion
[   11.066934] Bluetooth: hci0: Failed to send frame (-62)
[   11.066935] Bluetooth: hci0: sending frame failed (-62)
[   11.066983] Bluetooth: hci0: Failed to read MSFT supported features (-62)

Any help is appreciated.

[Post-Install]Desktop link icons clone after restart

Scorpa54 — Fri, 22 May 2026 15:52:45 GMT

After a restart my desktop icons clone themselves. They all work, there is just 2 of them. I move the articles from the desktop folder to the public folder and the clones remain on the desktop but do not function. restart with empty desktop folder and the clones disappear. move the links from the public folder back to the desktop folder and all is well until I restart. Rinse and repeat

[Software]Onboard virtual keyboard

INVICTRA — Fri, 22 May 2026 15:03:04 GMT

Latest Onboard version works OK. The problem is it can only send key-strokes to applications running under Xwayland. AI says it might be blocked from sending key-strokes to desktop or Wayland apps by the newer and stricter kwin in Plasma 6.
I mainly use it for my browser. The workaround currently is to start my browser under Xwayland.

Does anyone have a workaround?

[Post-Install]x11... a traumatic ecperience

Scorpa54 — Fri, 22 May 2026 01:33:31 GMT

I have installed the x11 desktop but when I log out and tab my way through, there is no cursor, to select that session I get my wallpaper and no cursor or navigation panels of any sort which leaves me with one option, hard reboot. I have tried multiple times with the same effect.

[SOLVED]Goes to sleep even though...

Scorpa54 — Thu, 21 May 2026 22:26:56 GMT

I've just installed (fresh) and have quite a few quirks. Let's tackle this one first. I've been into power management and turned "suspend session" to do nothing and "display and brightness" to never and when I leave for some time and come back I find a lock screen. There is another setting "other settings" that says "when inactive" and a selection of times that is defaulted to "run after 10 minutes" that I have no idea what to do with.

Everyone Needs AI, Right?

Shibblet — Thu, 21 May 2026 18:39:13 GMT

Just read an article on ombubuntu.co.uk called: Ubuntu is Getting AI Features in 2026 – Here's What's Planned

I am starting to feel the line between integrated AI, and non-integrated AI becoming blurred.

Why do these major companies (Canonical, Microsoft, etc.) believe that AI needs to be integrated into the OS?

In Microsoft's case, they are forcing users to deal with CoPilot. It "can" be removed, but it's not as simple as clicking on "Uninstall."
I'd imagine that Canonical will allow it to be "opt-out," as in easily removable... but not 100% sure.

Regardless of the integration... what are the reasons for this? I mean, some of us don't want or need an AI companion in our OS... so why force it?

[Post-Install]Seeking ideas with power outage prep and protection on multiple systems. NFS and Power settings

oshunluvr — Thu, 21 May 2026 16:27:44 GMT

This will cover several different areas including power control and networking. This is about my office setup and three systems. First the story. It's a bit long so feel free to move on to another thread...

I have a desktop PC running either KDEneon (for now) or Kubuntu 26.04, a media server running Ubuntu Server 24.04, and a Raspberry Pi running Raspbian 12 (bookworm). The Pi only runs a torrent server and uses NFSv4 to retrieve and store files on the media server. The desktop also has the servers NFS shares mounted.

The desktop has a large UPS and the server and Pi share a smaller one. The server and desktop both shut themselves down after a few minutes of power loss. The Pi is not configured to do that. Also, two routers are on the same UPS as the server and Pi. The modem has its own UPS.

This week there was a power outage at 4am and power was restored at 6:30am - I slept through it. My only indication that anything had happened was I sat down at my desk and discovered my PC was off. I normally leave it running unless I know I'm going to be gone for several days. At this point I still did not know the power had failed so I just assumed I shut it down the night before and had forgotten.

Issue #1:
When I powered up the desktop and logged in, it was lagging to the point of being barely usable but nothing in "top" looked out of place.. So first I rolled back to the previous days snapshot but the results were not different. Long story short: it was two NFS mounts causing the lag because the server was off and I hadn't noticed that yet. They were mounted with "hard" as one of the options and I assume systemd was continually re-attempting the mounts.

I never turn off the server so that was my first clue that something larger had happened. Restoring power to the server "fixed" the desktop lag.

Issue #2:
Once the server was back up, using a browser on the desktop I logged into Transmission (a torrent server) that runs on the Pi and the page was all errors. So I ssh'd into the Pi and transmission was running but the NFS mounts were not available - obviously because the server had been off. So I manually remounted them and restarted Transmission and everything was running normally.

Note that the Pi was still powered up and never shut down. I assume the UPS had more than enough battery to keep the Pi up and running for the 2.5 hours power was down.

The goal:
What I would like is to create a setup where these issues do not occur when a power outage happens. I believe it would require a sequential ending of some services and shutdown times for each of the devices, and I'm not sure where to start.

I guess somehow triggering a shutdown of the Pi, then the desktop, then finally the server. This would eliminate the failing of Transmission and the NFS mounts causing problems. Re. the NFS mounts I did change "hard" to "soft" but I haven't tested to see it that helps the lagging issue.

So I guess first thing is to figure out how to trigger the Pi to shutdown. I have ssh/rsh access from my desktop PC to the Pi so I can send a poweroff to the Pi with some trigger. Then power down the desktop before the server.

All the UPSs a Cyberpower so I'll start there...

Any suggestions are welcome.