[Software] Skilled Study of Kubuntu 26.10 Stonking Stingray

[NoWorries]

I was able to download 26.10 (Stonking Stingray) from the site
https://cdimage.ubuntu.com/kubuntu/releases/26.10.

Kubuntu 26.10 is currently under active development and has not yet reached its final, stable release (expected in October 2026).

I got my 26.10 iso on the 3rd June 2026. I have not had any problems with it. My current Info Center is shown below.


I hope this encourages you to try this new system. From the name it has, I am expecting to see a large and impressive system.

All the very best to those on this forum who are willing to give this new system some skilled study.

[kc1di]

Been running 26:10 from Live disc. Working quite well. But haven't done and install yet. Will continue testing and installing some programs I use. But my browser choice work well no problem.

My system

inxi -Fxxzr
System:
 Kernel: 7.0.0-14-generic arch: x86_64 bits: 64 compiler: gcc v: 15.2.0
 Desktop: KDE Plasma v: 6.7.0 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
   Distro: Kubuntu 26.10 (Stonking Stingray) base: Ubuntu
Machine:
 Type: Laptop System: Dell product: Latitude 5310 v: N/A
   serial: <superuser required> Chassis: type: 10 serial: <superuser required>
 Mobo: Dell model: 0RGVGG v: A00 serial: <superuser required> part-nu: 099F
   Firmware: UEFI vendor: Dell v: 1.31.0 date: 02/02/2026
Battery:
 ID-1: BAT0 charge: 16 Wh (100%) condition: 16/60 Wh (26.6%) volts: 7.71
   min: 7.6 model: BYD DELL N2K6208 serial: <filter> charging: status: full
   control: start: 75% end: 80% cycles: N/A
 Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M325
   serial: <filter> charge: 55% (should be ignored) status: discharging
CPU:
 Info: quad core model: Intel Core i5-10310U bits: 64 type: MT MCP
   arch: Comet/Whiskey Lake note: check rev: C cache: L1: 256 KiB L2: 1024 KiB
   L3: 6 MiB
 Speed (MHz): avg: 400 min/max: 400/4400 cores: 1: 400 2: 400 3: 400 4: 400
   5: 400 6: 400 7: 400 8: 400 bogomips: 35199
 Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
 Device-1: Intel CometLake-U GT2 [UHD Graphics] vendor: Dell driver: i915
   v: kernel arch: Gen-9.5 ports: active: eDP-1 empty: DP-1,HDMI-A-1
   bus-ID: 00:02.0 chip-ID: 8086:9b41
 Device-2: Realtek Integrated_Webcam_HD driver: uvcvideo type: USB rev: 2.0
   speed: 480 Mb/s lanes: 1 bus-ID: 1-6:3 chip-ID: 0bda:5532
 Display: wayland server: Xwayland v: 24.1.12 compositor: kwin_wayland
   driver: gpu: i915 display-ID: 0
 Monitor-1: eDP-1 model: AU Optronics 0x212d res: 1920x1080 hz: 60 dpi: 166
   diag: 336mm (13.2")
 API: EGL v: 1.5 platforms: device: 0 drv: iris device: 1 drv: swrast gbm:
   drv: iris surfaceless: drv: iris wayland: drv: iris x11: drv: iris
 API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 26.0.3-1ubuntu1
   glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics (CML GT2)
   device-ID: 8086:9b41 display-ID: :0.0
 API: Vulkan v: 1.4.341 surfaces: N/A device: 0 type: integrated-gpu
   driver: mesa intel device-ID: 8086:9b41 device: 1 type: cpu
   driver: mesa llvmpipe device-ID: 10005:0000
 Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
   de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo,
   xdpyinfo, xprop, xrandr
Audio:
 Device-1: Intel 400 Series Family On-Package HD Audio vendor: Dell
   driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:02c8
 API: ALSA v: k7.0.0-14-generic status: kernel-api
 Server-1: PipeWire v: 1.6.4 status: active with: 1: pipewire-pulse
   status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
 Device-1: Intel 400 Series Family On-Package CNVi WiFi driver: iwlwifi
   v: kernel bus-ID: 00:14.3 chip-ID: 8086:02f0
 IF: wlo1 state: up mac: <filter>
 Device-2: Intel 400 Series Family On-Package GbE vendor: Dell
   driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:0d4e
 IF: eno2 state: down mac: <filter>
Bluetooth:
 Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
   speed: 12 Mb/s lanes: 1 bus-ID: 1-10:4 chip-ID: 8087:0026
 Report: hciconfig ID: hci0 rfk-id: 2 state: down
   bt-service: enabled,running rfk-block: hardware: no software: yes
   address: <filter>
Drives:
 Local Storage: total: 355.94 GiB used: 1.68 GiB (0.5%)
 ID-1: /dev/mmcblk0 model: 00000 size: 59.62 GiB type: Removable
   serial: <filter>
 ID-2: /dev/nvme0n1 vendor: SK Hynix model: BC511 NVMe 256GB
   size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 26.9 C
 ID-3: /dev/sda vendor: SanDisk model: Ultra size: 57.84 GiB type: USB
   rev: 3.0 spd: 5 Gb/s lanes: 1 serial: <filter>
Partition:
 ID-1: / size: 7.65 GiB used: 1.15 GiB (15.0%) fs: overlay source: ERR-102
Swap:
 Alert: No swap data was found.
Sensors:
 System Temperatures: cpu: 54.0 C pch: 45.0 C mobo: N/A
 Fan Speeds (rpm): N/A
Repos:
 Packages: 2314 pm: dpkg pkgs: 2303 pm: snap pkgs: 11
 Active apt repos in: /etc/apt/sources.list
   1: deb http://archive.ubuntu.com/ubuntu/ stonking main restricted universe multiverse
   2: deb http://security.ubuntu.com/ubuntu/ stonking-security main restricted universe multiverse
   3: deb http://archive.ubuntu.com/ubuntu/ stonking-updates main restricted universe multiverse
 Active apt repos in: /etc/apt/sources.list.d/cdrom.sources
   1: deb file:///cdrom stonking main restricted
Info:
 Memory: total: 16 GiB note: est. available: 15.31 GiB used: 3.68 GiB (24.0%)
 Processes: 253 Power: uptime: 52m wakeups: 1 Init: systemd v: 259
   default: graphical
 Compilers: N/A Shell: Bash v: 5.3.9 running-in: konsole inxi: 3.3.40

​

[tenplus1]

I've been testing this release since the repo's became available and to date everything ran just fine until 2 days ago, when I did the usual morning update and found out that my system would no longer shut down... I couldn't press ESC to see what was happening or change to a tty console, and the only way to shut down my system was to CTRL+ALT_GR+O... Any ideas ?

Operating System: Kubuntu 26.10
KDE Plasma Version: 6.7.3
KDE Frameworks Version: 6.28.0
Qt Version: 6.10.2
Kernel Version: 7.1.5-070105-generic (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840HS w/ Radeon 780M Graphics
Memory: 32 GiB of RAM (23.2 GiB usable)
Graphics Processor: AMD Radeon 780M Graphics
Manufacturer: AZW
Product Name: GTR
System Version: V21

[claydoh]

. Any ideas ?

Running a pre-pre-alpha system?

The usual caveats apply here. System-level components do and will change, daily, or more often. Incomplete uploads to the archive, missing parts that didn't build and are being troubleshooted (troubleshot?) , and just plain old bugs and mistakes.

[tenplus1]

claydoh - A fresh install fixed whatever was broken with the latest update that stalled the shutdown process.

[claydoh]

claydoh - A fresh install fixed whatever was broken with the latest update that stalled the shutdown process.

This sort of ...fix... can be common at this stage, but so can just waiting a day and updating again, sometimes. It's like a box of chocolates

[life0riley]

I used this image from June 22nd.
https://cdimage.ubuntu.com/kubuntu/r...se/snapshot-2/

I installed in QEMU-KVM without issues. I thought I was having update errors and realized I have to uncheck file:/cdrom/ - Stonking (main restricted) in the Discover settings.

I use the terminal and follow up with Discover to update. No major breakage to report.

Discover appears to be stuck fetching updates. It really isn't because I can still click the refresh button.

[claydoh]

Discover appears to be stuck fetching updates. It really isn't because I can still click the refresh button.

A known bug in Discover's snap backend in Plasma 6.7. This was fixed in neon (at least on my two systems) but still seems to affect Fedora users. it could also be hanging in the firmware update checks as well, but that doesn't seem to be specific to any distro or Plasma version as far as I can tell. It eventually times out though. The snap backend problem sticks around.

You can try disabling snap in the settings, but you might need to actually uninstall plasma-discover-backend-snap for the moment. Snaps should still self update, else update them in the command line.

[life0riley]

A known bug in Discover's snap backend in Plasma 6.7. This was fixed in neon (at least on my two systems) but still seems to affect Fedora users. ....

For now, I'll update snaps in the command line.

sudo snap refresh

I found two KDE bug reports, 521682 and 500513, but both of those are in confirmed status. Is there another bug report that shows it was resolved?