Please Present Performance of Plucky Puffin Kubuntu 25.04

[acheron]

Qt 6.8.3 and Plasma 6.3.4 updates should be arriving in plucky

[claydoh]

adaptive sync enabled in the live session

Yes, the live session has a bit more of a safe/generic graphics setup, which might affect this.

https://iso.qa.ubuntu.com/qatracker/...7051/testcases

[tenplus1]

The latest 25.04 build runs well on most systems but having adaptive sync enabled in the live session causes black screens to appear on many amd systems when showing the try/install screen, this makes it look as if kubuntu isnt running properly.

[cookiemuncher]

My experience with Kubuntu 25.04 has been top class - until I enabled 'Sleep' under power management. When the session is resumed, I get the following pics. This is with nvidia-driver version 570. I need to log out and then log back in again to restore the display to normal.

System:
 Host: kubuntu2504 Kernel: 6.14.0-11-generic arch: x86_64 bits: 64
 Desktop: KDE Plasma v: 6.3.3 Distro: Kubuntu 25.04 (Plucky Puffin)
Machine:
 Type: Desktop Mobo: TBYTE model: H510-VH serial: <superuser required>
   UEFI: American Megatrends LLC. v: TEH51A01 date: 09/15/2022
CPU:
 Info: 6-core model: 11th Gen Intel Core i5-11400 bits: 64 type: MT MCP
   cache: L2: 3 MiB
 Speed (MHz): avg: 1305 min/max: 800/4400 cores: 1: 1305 2: 1305 3: 1305
   4: 1305 5: 1305 6: 1305 7: 1305 8: 1305 9: 1305 10: 1305 11: 1305 12: 1305
Graphics:
 Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] driver: nvidia v: 570.86.16
 Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
   compositor: kwin_wayland driver: X: loaded: nvidia
   unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia,nvidia-nvswitch
   resolution: 1: 1920x1080~60Hz
 API: EGL v: 1.5 drivers: nvidia
   platforms: gbm,wayland,x11,surfaceless,device
 API: OpenGL v: 4.6.0 vendor: nvidia v: 570.86.16 renderer: NVIDIA GeForce
   GTX 1060 6GB/PCIe/SSE2
 API: Vulkan v: 1.4.304 drivers: N/A surfaces: xcb,xlib,wayland
 Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
   de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
   wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr

​

[acheron]

https://kubuntu.org/news/kubuntu-plu...beta-released/

[NoWorries]

For some time now I have been getting the annoying message every time I login:

"IBus notification
IBus should be called from the desktop session in Wayland for KDE"

I decided to see if anyone else had this problem and I found a solution at:

https://www.reddit.com/r/archlinux/c...method_global/

The solution is very simple and is given here:

im-config -n none

I am now very pleased to say that this solution works very well and I no longer get the IBus Notification.

[NoWorries]

Just 1 Month before the Release of Plucky Puffin 25.04

After 5 months of hard work by the developers, we now have only 1 month before the official release. There have been a multitude of updates which have maintained overall system stability. I certainly hope that you have found this to be the case. The table below shows only the key system updates over the past month.

	1 Month Ago	1 Month To Go
KDE Plasma Version	6.3.0	6.3.3
KDE Frameworks Version	6.11	6.11.0
QT Version	6.8.2	6.8.2
Application Version	4:24.12.1	4:24.12.3
Kernel Version	6.12.0-16-generic	6.14.0-10-generic

As you can see, all versions in this list have been advanced with the exception of KDE Frameworks and QT Version. My favourite calendar Kontact is now available and for me it now works. Has anyone on this forum been able to get Kontact to also work for them?

The developers have done a great job at getting Plucky Puffin to this level of performance and I look forward to seeing what transpires in the next month.

[NoWorries]

Well Kontact can now be installed but I get the following screen.

$ kontact
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_3D_FEATURES
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CAPSET_QUERY_FIX
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_RESOURCE_BLOB
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_HOST_VISIBLE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CROSS_DEVICE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CONTEXT_INIT
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_SUPPORTED_CAPSET_IDs
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_EXPLICIT_DEBUG_NAME
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_FENCE_PASSING
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_GUEST_HANDLE
MESA: error: DRM_IOCTL_VIRTGPU_GET_CAPS failed with Permission denied
MESA: error: DRM_IOCTL_VIRTGPU_CONTEXT_INIT failed with Permission denied, continuing without context...
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during initial connection!
org.kde.pim.akonadiserver: executable: "/usr/sbin/mysqld"
org.kde.pim.akonadiserver: arguments: QList("--defaults-file=/home/aurora/.local/share/akonadi/mysql.conf", "-
-datadir=/home/aurora/.local/share/akonadi/db_data/", "--socket=/run/user/1000/akonadi/mysql.socket", "--pid-f
ile=/run/user/1000/akonadi/mysql.pid")
org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: ""
org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Unknown error"
org.kde.pim.akonadiserver: See "/home/aurora/.local/share/akonadi/db_data/mysql.err" for more details
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally...
beginResetModel called on Akonadi::TodoModel(0x5d935b684ee0, name = "TodoModel") without calling endResetModel
first
beginResetModel called on QIdentityProxyModel(0x5d935b6a76f0) without calling endResetModel first
beginResetModel called on TodoViewSortFilterProxyModel(0x5d935b687d20) without calling endResetModel first
endResetModel called on Akonadi::TodoModel(0x5d935b684ee0, name = "TodoModel") without calling beginResetModel
first
endResetModel called on QIdentityProxyModel(0x5d935b6a76f0) without calling beginResetModel first
endResetModel called on TodoViewSortFilterProxyModel(0x5d935b687d20) without calling beginResetModel first
org.kde.pim.akonadicore: Job error:  "" for collection: QList()
org.kde.pim.akonadicore: Job error:  "" for collection: QList()
org.kde.pim.messagelist: Failed to load tags  ""
org.kde.pim.kmail: ""
org.kde.pim.mailcommon: failed to retrieve tags  ""
org.kde.pim.akonadicalendar: Search failed:  ""
org.kde.pim.akonadicore: Failed to fetch tags:  ""
org.kde.pim.akonadicore: Job error:  "" for collection: QList()

​

I just hope that someone on this forum can make sense of this. All help would be appreciated.

[acheron]

KDE PIM packages have been in an in-between state for a while transitioning from Qt5 -> Qt6 based release, with some of the Qt6 (24.12.x) ones stuck in the proposed pocket waiting for some archive admin intervention to help them migrate to the release pocket. This seems to have now happened last night.

[claydoh]

libkpim6pimcommon6 is still in development

No, it is not. It is the current official release of the PIM stack that Kontact is a part of. I suspect a partial version mis-match in the packaging, for whatever reason. 24.12.2 is not the same thing as 24.12.2.-1, for example,in terms of packaging, even if the contents are actually fine.

I am wondering why the developers don't provide version 23 for Kontact

Sure, IF this was doable on the current Plasma and Qt stack, AND this was a final release. This is more of a bookkeeping thing that seems to need to be fixed, but of course without asking why, we won't know what the issue is, or what the holdup is.

It is also entirely possible that you have a weird or odd combination of packages and updates that are causing the dependency hell due to the nature of the development cycle. I saw that more than once per-cycle when I used to run the pre-releases as my daily OS for a number of years.

Might be worth spinning up a Vm or boot to a live session and see if installing Kontact shows the same conflicts in a fresh install from the current image


BUTT:
Take a look here

The package is missing, so it isn't going to work until that is sorted. It is listed as a dependency for Kontact.
In Neon, libkpim6pimcommon6 is a 'dummy' transitional package, and only needed for upgrades and isn't mandatory, so perhaps Kubuntu is still in the process of converting things over and sorting this all out from the packages --which are initially imported from Debian.

Since Kontact itself is just a wrapper for things like Kmail and Kaddressbook, do these individuals parts still work if launched from the menus? I imagine not, but worth a go.

[NoWorries]

No idea. Either kontact is behind or libkpim6pimcommon6 is? I can't tell, and its all greek to me still.
Report a bug, or poke a kubuntu dev on irc/telegram.

From my quick investigation, libkpim6pimcommon6 is still in development. Because of this, I am wondering why the developers don't provide version 23 for Kontact and when version 24 is sorted out it can be updated. I just hope that version 24 is not a profound change which makes all of Kontact Version 23 files incompatible.

[claydoh]

No idea. Either kontact is behind or libkpim6pimcommon6 is? I can't tell, and its all greek to me still.
Report a bug, or poke a kubuntu dev on irc/telegram.

[NoWorries]

You really need to use apt so we can see the actual full errors and relevant messaging behind what you show in the image. This tells us nothing useful, unfortunately.

Many thanks very much for your suggestion and I hope this helps:

sudo apt install kontact
[sudo] password:  
Solving dependencies... Error!  
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
kontact : Depends: kdepim-runtime but it is not going to be installed
          Depends: libkpim6pimcommon6 (>= 4:24.12.2) but it is not installable
          Depends: libkpim6pimcommon6-24.12 but it is not installable
          Recommends: accountwizard but it is not going to be installed
          Recommends: akregator but it is not going to be installed
          Recommends: kaddressbook but it is not going to be installed
          Recommends: kmail but it is not going to be installed
          Recommends: korganizer but it is not going to be installed
Error: Unable to correct problems, you have held broken packages.
Error: The following information from --solver 3.0 may provide additional context:
  Unable to satisfy dependencies. Reached two conflicting decisions:
  1. kontact:amd64=4:24.12.2-1 is selected for install
  2. kontact:amd64 Depends libkpim6pimcommon6 (>= 4:24.12.2)
     but none of the choices are installable:
     [no choices]

​

Well this is the list from apt and I hope it makes sense to hep sort out the problems I am having.

[claydoh]

You really need to use apt so we can see the actual full errors and relevant messaging behind what you show in the image. This tells us nothing useful, unfortunately.

[NoWorries]

Looks like I will have to wait for next week. I could not locate akonadictl in synaptic. It looks like the problems are with Kontact Version 24 as Version 23 works on my other systems.

In my frustration, I decided to reinstall 25.04 and that made my attempt to install Kontact produce a dependency problem. The graphic attached shows the error.

It is now 5 days and I have been patiently waiting for Kontact. I use it frequently for all my appointments and other activities which are no longer available to me. I just hope that it is available soon.

Does anyone know when it will be available?