Friendly evaluate Kubuntu 25.10 Questing Quokka

[NoWorries]

I have finally resolved how to start a new topic on this forum as I previously started this topic under an existing topic "Name for Kubuntu 25.10"

So as usual this new distribution is located at:
https://cdimage.ubuntu.com/kubuntu/daily-live/current/

and it has been there since the 4/05/25.

I installed it and it is working very well. You will find my initial comments at post 2 dated 4th May. I have all my applications installed and working, also I have this system networked with my other Laptop which has the previous Kubuntu distribution installed.

Being a new distribution, there are many updates and the current Info Centre is:




The only problem that I currently have is that I cannot scale some images with my cursor. Dolphin and other applications I have total cursor control but with System Settings and Info Centre I can only change the width a little.

I am keenly looking forward to the development of 25.10.

[tenplus1]

A fresh install or 25.10 worked fine on my main desktop, my only issue was that Adaptive Sync was enabled by default and caused the screen to flicker black during the boot into the Try or Install screen, this should be OFF by default to let the user enable it if needed.

[NoWorries]

While Questing Quokka has a few months to go before its release, there are for me two applications which totally fail. The first is Kdenlive:

:~$ kdenlive
kdenlive: error while loading shared libraries: libopentimelineio.so: cannot open shared object file: No such file or directory

The second is Kazam which can be launched but after finishing and saving the recorded video, no image or sound is recorded. The startup for Kazam is only shown below.

~$ kazam
WARNING Kazam - Failed to correctly detect operating system.

** (kazam:11995): WARNING **: 16:14:28.859: Binding '<Super><Ctrl>R' failed!

** (kazam:11995): WARNING **: 16:14:28.859: Binding '<Super><Ctrl>F' failed!

** (kazam:11995): WARNING **: 16:14:28.859: Binding '<Super><Ctrl>P' failed!

** (kazam:11995): WARNING **: 16:14:28.859: Binding '<Super><Ctrl>W' failed!

** (kazam:11995): WARNING **: 16:14:28.859: Binding '<Super><Ctrl>Q' failed!

(kazam:11995): libayatana-appindicator-WARNING **: 16:14:28.864: libayatana-appindicator is deprecated. Please use libayatana-appindicator-glib in newly written code.
/usr/lib/python3/dist-packages/kazam/app.py:145: Warning: value "((GtkIconSize) 32)" of type 'GtkIconSize' is invalid or out of range for property 'icon-size' of type 'GtkIconSize'
self.builder.add_from_file(os.path.join(prefs.data dir, "ui", "kazam.ui"))

(kazam:11995): Gtk-WARNING **: 16:14:28.900: Can't set a parent on widget which has a parent

(kazam:11995): Gtk-WARNING **: 16:14:28.902: Can't set a parent on widget which has a parent​

I decided to not show all the setting up and saving of the video recording as all the damage is done by not starting correctly.

[NoWorries]

I am now very pleased to report that both kdenlive and kazam both work very well on X11. On Wayland, only kdenlive works, ie I can launch it and it plays a previously edited video. However on Waylnd, the kazam saved file has a black video screen while the audio now plays. So progress has been made, and from the current rate of progress I hope it is not long before kazam works on Wayland. In the mean time, I know that X11 provides a solution to video recording and editing.

[acheron]

FYI, the X11 plasma session is no longer installed by default in Questing 25.10. If you wish to have an X11 session available in SDDM then make sure the package plasma-session-x11 is installed.

[tenplus1]

Since removing x11 login session, on boot into desktop I've been getting 100% cpu usage from fusermount3 for 20-30 seconds then it stops. Any ideas what's changed ?

[claydoh]

Since removing x11 login session, on boot into desktop I've been getting 100% cpu usage from fusermount3 for 20-30 seconds then it stops. Any ideas what's changed ?

1. So you yourself removed the existing x11 login session? (its removal from the ISO as a defualt package should not affect current installs, nor remove the relevant package)
2. Does this happen when you switch back to an x11 session? It is not likley related to the display protocol, but you never know.
3. being fusermount, it may be related to things you have mounting or starting up at login (restoring something from the previous desktop session)? A Flatpak/snap, or some extra service (rclone or docker or something similar, perhaps. Rclone sparks a memory, but that would be quite a while ago.)
4. The usual pre-beta caveats and disclaimers

[tenplus1]

claydoh - The system update removed the x11 login session itself, and everything worked fine on wayland session beforehand, was just curious why fusermount3 decided to hog one of the cpu cores for some time after login. I will try disabling snap and flatpak to see if that makes a difference.

[claydoh]

Might be worth rolling back to a previous state (if possible) and see the full list of changes.

If you are not using any snaps (firefox, for example) then it probably isn't from that.

I am not seeing it here, but I haven't actually looked for it. And I have not updated that laptop since Friday or thereabouts anyway.

[claydoh]

I can't reproduce it, fusermount isn't running at login here.

On my main KDE neon system, it IS at login, and post-login, as I have one flatpak app (ktailctl) loading at login, and it is what provides the KDE file picker in Gnome/GTK apps (or vice-versa) , mostly in snap and flatpak apps, but also in 'normal' apps as well.


fwiw, the x11 is not removed when updating, only if you do cleanup via autoremove and allow it. Unless discover does this? (I don't think so -- I use it for regular updates daily) None of the small updates I saw today seem related to xdg or fuse, but the layers can go deep.