KDE Partition Manager stopped working. (Needs “xcb-cursor0” or “libxcb-cursor0”?)

Support Software & Applications
1

On my main computer (Asus MB, Ryzen 7 5700G CPU, integrated AMD Radeon graphics, Manjaro Linux, KDE Plasma 6.3.6 desktop), KDE Partition manager has stopped working. I just noticed this tonight (10/27/2025).

When I try launching it through the GUI, the main window launches, but the scan of the first detected device freezes at 0%. Neither the scan nor the app can be easily aborted; the application has to be closed forcefully through System Monitor “Close Application”. (Clicking the “X” does nothing.)

When I try launching it from Konsole, I get some interesting messages:

%partitionmanager
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
qt.qpa.plugin: Could not load the Qt platform plugin “xcb” in “” even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: wayland, eglfs, wayland-egl, minimalegl, offscreen, vkkhrdisplay, vnc, linuxfb, minimal, xcb.
Aborted (core dumped) partitionmanager

I cannot find the “xcb-cursor0” or “libxcb-cursor0” packages in any of the repositories. So, is there a solution to this problem? (Other than the obvious work-around of using GPartEd, which does seem to work.)

2

The only thing that I can suggest is that you try re-installing the xcb-util-cursor package:

pamac reinstall xcb-util-cursor

That package contains the following files:

pacman -Ql xcb-util-cursor  
xcb-util-cursor /usr/
xcb-util-cursor /usr/include/
xcb-util-cursor /usr/include/xcb/
xcb-util-cursor /usr/include/xcb/xcb_cursor.h
xcb-util-cursor /usr/lib/
xcb-util-cursor /usr/lib/libxcb-cursor.so
xcb-util-cursor /usr/lib/libxcb-cursor.so.0
xcb-util-cursor /usr/lib/libxcb-cursor.so.0.0.0
xcb-util-cursor /usr/lib/pkgconfig/
xcb-util-cursor /usr/lib/pkgconfig/xcb-cursor.pc
xcb-util-cursor /usr/share/
xcb-util-cursor /usr/share/licenses/
xcb-util-cursor /usr/share/licenses/xcb-util-cursor/
xcb-util-cursor /usr/share/licenses/xcb-util-cursor/LICENSE

The xcb-util-cursor package was recently updated:

paclog --grep=xcb-util-cursor  
[2023-11-09T08:41:04+1100] [ALPM] upgraded xcb-util-cursor (0.1.4-1 -> 0.1.5-1)
[2025-09-03T22:21:36+1000] [ALPM] upgraded xcb-util-cursor (0.1.5-1 -> 0.1.6-1)

The same package version is in all 3 Manjaro branches:

mbn info xcb-util-cursor -q | grep -Ev 'Name|Repository|Packager'
Branch         : archlinux
Version        : 0.1.6-1
Build Date     : Wed 03 Sep 2025 04:32:08 
Branch         : unstable
Version        : 0.1.6-1
Build Date     : Wed 03 Sep 2025 04:32:08 
Branch         : testing
Version        : 0.1.6-1
Build Date     : Wed 03 Sep 2025 04:32:08 
Branch         : stable
Version        : 0.1.6-1
Build Date     : Wed 03 Sep 2025 04:32:08

mbn can be found in the manjaro-check-repos package

Edit: I can also confirm that partitionmanager opens without any issues on my Testing branch system. The only xcb-cursor files on my system are those contained in the xcb-util-cursor package:

locate xcb-cursor 
/usr/lib/libxcb-cursor.so
/usr/lib/libxcb-cursor.so.0
/usr/lib/libxcb-cursor.so.0.0.0
/usr/lib/pkgconfig/xcb-cursor.pc
3

I remember a while back - in fact as far back as plasma 6 RC - something similar with partition manager.

Having the issue at the current stable branch points to - my guess - an issue with the theme used on the affected system.

The message you quote, is even more interesting as it points to the next release 6.5 - which was released very recently.

Back when Plasma 6 was in RC state - the issue was - if I recall correct - related to kpmcore.

On a fully updated Plasma 6.5 on unstable branch there is no issues

kinfo 
 $ kinfo
Operating System: Manjaro Linux 
KDE Plasma Version: 6.5.0
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.5-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen Threadripper PRO 5945WX 12-Cores
Memory: 128 GiB of RAM (125.6 GiB usable)
Graphics Processor: AMD Radeon RX 7900 XTX

partitionmanager has only minor difference between branches

partitionmanger repo info 
 $ mbn info partitionmanager -q
Branch         : archlinux
Name           : partitionmanager
Version        : 25.08.2-1
Repository     : extra
Build Date     : Wed 08 Oct 2025 23:20:47 
Packager       : Antonio Rojas <arojas@archlinux.org>
Branch         : unstable
Name           : partitionmanager
Version        : 25.08.2-1
Repository     : extra
Build Date     : Wed 08 Oct 2025 23:20:47 
Packager       : Antonio Rojas <arojas@archlinux.org>
Branch         : testing
Name           : partitionmanager
Version        : 25.08.2-1
Repository     : extra
Build Date     : Wed 08 Oct 2025 23:20:47 
Packager       : Antonio Rojas <arojas@archlinux.org>
Branch         : stable
Name           : partitionmanager
Version        : 25.08.1-1
Repository     : extra
Build Date     : Tue 09 Sep 2025 15:22:41 
Packager       : Antonio Rojas <arojas@archlinux.org>

The same is true for kpmcore

kpmcore repo info 
 $ mbn info kpmcore -q
Branch         : archlinux
Name           : kpmcore
Version        : 25.08.2-1
Repository     : extra
Build Date     : Wed 08 Oct 2025 20:09:54 
Packager       : Antonio Rojas <arojas@archlinux.org>
Branch         : unstable
Name           : kpmcore
Version        : 25.08.2-1
Repository     : extra
Build Date     : Wed 08 Oct 2025 20:09:54 
Packager       : Antonio Rojas <arojas@archlinux.org>
Branch         : testing
Name           : kpmcore
Version        : 25.08.2-1
Repository     : extra
Build Date     : Wed 08 Oct 2025 20:09:54 
Packager       : Antonio Rojas <arojas@archlinux.org>
Branch         : stable
Name           : kpmcore
Version        : 25.08.1-1
Repository     : extra
Build Date     : Tue 09 Sep 2025 12:54:19 
Packager       : Antonio Rojas <arojas@archlinux.org>

EDIT: 2025-10-28T06:31:00Z

On my stable branch based laptop - using default breeze theme - partition manager launched with no hickups.

4

Ok, I tried those suggestions as root from Konsole, but it didn’t solve the issue:

> %pacman -S xcb-util-cursor
> Job start time: 02:26:21 AM
> warning: xcb-util-cursor-0.1.6-1 is up to date – reinstalling
> resolving dependencies…
> looking for conflicting packages…
>
> Packages (1) xcb-util-cursor-0.1.6-1
>
> Total Download Size:   0.01 MiB
> Total Installed Size:  0.03 MiB
> Net Upgrade Size:      0.00 MiB
>
> :: Proceed with installation? \[Y/n\] Y
> :: Retrieving packages…
> xcb-util-cursor-0.1.6-1-x86_64                                                        11.3 KiB  36.3 KiB/s 00:00 \[--------------------------------------------------------------------\] 100%
> (1/1) checking keys in keyring                                                                                    \[--------------------------------------------------------------------\] 100%
> (1/1) checking package integrity                                                                                  \[--------------------------------------------------------------------\] 100%
> (1/1) loading package files                                                                                       \[--------------------------------------------------------------------\] 100%
> (1/1) checking for file conflicts                                                                                 \[--------------------------------------------------------------------\] 100%
> (1/1) checking available disk space                                                                               \[--------------------------------------------------------------------\] 100%
> :: Running pre-transaction hooks…
> (1/1) Creating Timeshift snapshot before upgrade…
> ==> skipping timeshift-autosnap due skipRsyncAutosnap in /etc/timeshift-autosnap.conf set to TRUE.
> :: Processing package changes…
> (1/1) reinstalling xcb-util-cursor                                                                                \[--------------------------------------------------------------------\] 100%
> :: Running post-transaction hooks…
> (1/3) Arming ConditionNeedsUpdate…
> (2/3) Refreshing PackageKit…
> (3/3) Checking which packages need to be rebuilt
>
> BASH on Manjaro Linux root@Excalibur Tue 2025-10-28, 02:26:44 AM
> \~
> %partitionmanager
> Job start time: 02:31:23 AM
> qt.qpa.xcb: could not connect to display
> qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
> qt.qpa.plugin: Could not load the Qt platform plugin “xcb” in “” even though it was found.
> This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
>
> Available platform plugins are: wayland, eglfs, wayland-egl, minimalegl, offscreen, vkkhrdisplay, vnc, linuxfb, minimal, xcb.
>
> Aborted                    (core dumped) partitionmanager
>
> BASH on Manjaro Linux root@Excalibur Tue 2025-10-28, 02:31:23 AM
> \~
> %partitionmanager &
> Job start time: 02:32:33 AM
> \[1\] 81114
>
> BASH on Manjaro Linux root@Excalibur Tue 2025-10-28, 02:32:33 AM
> \~
> %qt.qpa.xcb: could not connect to display
> qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
> qt.qpa.plugin: Could not load the Qt platform plugin “xcb” in “” even though it was found.
> This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
>
> Available platform plugins are: wayland, eglfs, wayland-egl, minimalegl, offscreen, vkkhrdisplay, vnc, linuxfb, minimal, xcb.
>
> ^C
> \[1\]+  Aborted                    (core dumped) partitionmanager
>
> BASH on Manjaro Linux root@Excalibur Tue 2025-10-28, 02:32:54 AM
> \~
> %mbn --help
> Job start time: 02:33:41 AM
> bash: mbn: command not found…
>
> BASH on Manjaro Linux root@Excalibur Tue 2025-10-28, 02:33:41 AM
> \~
> %pacman -S manjaro-check-repos
> Job start time: 02:34:35 AM
> resolving dependencies…
> looking for conflicting packages…
>
> Packages (3) pyalpm-0.10.12-1  tree-2.2.1-1  manjaro-check-repos-0.9.10-2
>
> Total Download Size:   0.23 MiB
> Total Installed Size:  0.79 MiB
>
> :: Proceed with installation? \[Y/n\] Y
> :: Retrieving packages…
> tree-2.2.1-1-x86_64                                                                   40.6 KiB  94.9 KiB/s 00:00 \[--------------------------------------------------------------------\] 100%
> pyalpm-0.10.12-1-x86_64                                                               64.2 KiB   127 KiB/s 00:01 \[--------------------------------------------------------------------\] 100%
> manjaro-check-repos-0.9.10-2-any                                                     126.9 KiB   214 KiB/s 00:01 \[--------------------------------------------------------------------\] 100%
> Total (3/3)                                                                          231.7 KiB   334 KiB/s 00:01 \[--------------------------------------------------------------------\] 100%
> (3/3) checking keys in keyring                                                                                    \[--------------------------------------------------------------------\] 100%
> (3/3) checking package integrity                                                                                  \[--------------------------------------------------------------------\] 100%
> (3/3) loading package files                                                                                       \[--------------------------------------------------------------------\] 100%
> (3/3) checking for file conflicts                                                                                 \[--------------------------------------------------------------------\] 100%
> (3/3) checking available disk space                                                                               \[--------------------------------------------------------------------\] 100%
> :: Processing package changes…
> (1/3) installing pyalpm                                                                                           \[--------------------------------------------------------------------\] 100%
> (2/3) installing tree                                                                                             \[--------------------------------------------------------------------\] 100%
> (3/3) installing manjaro-check-repos                                                                              \[--------------------------------------------------------------------\] 100%
> :: Running post-transaction hooks…
> (1/4) Arming ConditionNeedsUpdate…
> (2/4) Refreshing PackageKit…
> (3/4) Updating icon theme caches…
> (4/4) Updating the desktop file MIME type cache…
>
> BASH on Manjaro Linux root@Excalibur Tue 2025-10-28, 02:34:39 AM
> \~
> %mbn info xcb-util-cursor -q | grep -Ev ‘Name|Repository|Packager’
> Job start time: 02:35:14 AM
>
> Error: BranchNotFoundError: local repo “archlinux” not found ! (use command “update”) 🤕
>
> BASH on Manjaro Linux root@Excalibur Tue 2025-10-28, 02:35:14 AM
> \~
> %mbn update
> Job start time: 02:36:11 AM
> :: Branch: archlinux
> :: Synchronizing package databases…
> core                                                                                 117.2 KiB  79.2 KiB/s 00:01 \[####################################################################\] 100%
> extra                                                                                  8.0 MiB  3.86 MiB/s 00:02 \[####################################################################\] 100%
> :: Branch: unstable
> :: Synchronizing package databases…
> core                                                                                 147.7 KiB   172 KiB/s 00:01 \[####################################################################\] 100%
> extra                                                                                  8.6 MiB  5.10 MiB/s 00:02 \[####################################################################\] 100%
> multilib                                                                             145.7 KiB   231 KiB/s 00:01 \[####################################################################\] 100%
> :: Branch: testing
> :: Synchronizing package databases…
> core                                                                                 147.7 KiB   227 KiB/s 00:01 \[####################################################################\] 100%
> extra                                                                                  8.6 MiB  5.74 MiB/s 00:02 \[####################################################################\] 100%
> multilib                                                                             147.5 KiB   224 KiB/s 00:01 \[####################################################################\] 100%
> :: Branch: stable
> :: Synchronizing package databases…
> core                                                                                 146.0 KiB  1553 KiB/s 00:00 \[####################################################################\] 100%
> extra                                                                                  8.6 MiB  24.9 MiB/s 00:00 \[####################################################################\] 100%
> multilib                                                                             149.2 KiB  5.40 MiB/s 00:00 \[####################################################################\] 100%
>
> BASH on Manjaro Linux root@Excalibur Tue 2025-10-28, 02:36:24 AM
> \~
> %mbn info xcb-util-cursor -q | grep -Ev ‘Name|Repository|Packager’
> Job start time: 02:36:37 AM
> Branch         : archlinux
> Version        : 0.1.6-1
> Build Date     : Tue 02 Sep 2025 11:32:08
> Branch         : unstable
> Version        : 0.1.6-1
> Build Date     : Tue 02 Sep 2025 11:32:08
> Branch         : testing
> Version        : 0.1.6-1
> Build Date     : Tue 02 Sep 2025 11:32:08
> Branch         : stable
> Version        : 0.1.6-1
> Build Date     : Tue 02 Sep 2025 11:32:08
>
> BASH on Manjaro Linux root@Excalibur Tue 2025-10-28, 02:36:39 AM
> \~
> %

I think the reason is, that provides “libxcb-cursor.so”, but does not provide “libxcb-cursor0.so”, which is what KDE Partition Manager appears to be asking for.

Mod edit:- Please avoid pasting code or command output within anything other than a pre-formatted text enclosure. Quoted text is not appropriate in this context. Corrected on your behalf, one time only. No charge.

5

Well, this system is running “Breeze” as its “global theme”, and the only “customizations” to that are that “Application Style” is set to “Fusion” and “Window Decorations” are set to “Oxygen”. But that’s easy enough to test, I’ll set those two to “Breeze” and see what happens….

Nope. Launching KDE Partition Manager from GUI still causes it to freeze at 0% while scanning first detected device, and neither scan nor app can be aborted, necessitating using “Quit Application” in “System Monitor”. And trying to launch KDE Partition Manager from Konsole also still crashes:

BASH on Manjaro Linux root@Excalibur Tue 2025-10-28, 02:48:50 AM
~
%qt.qpa.xcb: could not connect to display
qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
qt.qpa.plugin: Could not load the Qt platform plugin “xcb” in “” even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: wayland, eglfs, wayland-egl, minimalegl, offscreen, vkkhrdisplay, vnc, linuxfb, minimal, xcb.

^C
[1]+ Aborted (core dumped) partitionmanager

BASH on Manjaro Linux root@Excalibur Tue 2025-10-28, 02:49:02 AM
~
%

So until something can be installed that provide the “xcb-cursor0” (whatever that is) being asked-for, this isn’t going to work.

Hmmm. Maybe this is an X11 thing? I’ll be right back, after re-launching session as Wayland.

Back, in Wayland. Nope, doesn’t work in Wayland either. I’ll try this in my other Manjaro computers and see what happens.

1 Like
6

Error and Warning messages often suggest a course of action. Have you considered removing partitionmanager and installing it again?

pacman -Rns partitionmanager
pacman -Syu partitionmanager
2 Likes
7

There is a lot of references to this error message on the interweb - I can’t say if those provide any further insight into the subject

https://sx.nix.dk/search?q=qt.qpa.plugin%3A+From+6.5.0%2C+xcb-cursor0+or+libxcb-cursor0+is+needed+to+load+the+Qt+xcb+platform+plugin

I figured this much - the reference to 6.5 is not Plasma 6.5 as I initially thought but a reference to Qt 6.5

The only references I could find.. matches @scotty65 's comment

 $ pamac search -f xcb-cursor
/usr/lib/libxcb-cursor.so is owned by xcb-util-cursor
/usr/lib/libxcb-cursor.so.0 is owned by xcb-util-cursor
/usr/lib/libxcb-cursor.so.0.0.0 is owned by xcb-util-cursor
/usr/lib/pkgconfig/xcb-cursor.pc is owned by xcb-util-cursor

Your idea that it could be related to X11 could be right - I am using Wayland - I have been for years..

1 Like
8

I discovered that I was chasing a pair of wild geese!

Firstly, I determined that my Asus notebook (also running Manjaro/Plasma/X11) runs KDE Partition Manager with no problem from the GUI. When I try launching it as root from Konsole, it fails with that weird “xcb-cursor0” error. However, if I launch Partition Manager from Konsole as my regular user, it works fine! Apparently, KDE Partition Manager can’t be launched from Konsole as root, only as regular user. That explains the bogus “xcb-cursor0” nonsense.

Back on the problem computer, if I launch KDE Partition Manager from either GUI, or from Konsole (as regular user), the program launches then immediately freezes at 0% on scanning first detected device. However, that’s not forever; I inadvertently left the “crashed” (or so I thought) program running, and after 11 minutes it completed its scan.

So the real issue is that on this one machine only, KDE Partition manager is taking a long time (11 minutes, instead of 1 second as it should) to scan devices. Unknown why that is. (Problem brewing with with of my devices?) Oddly, Gnome’s Partition Manager (GPartEd) runs the same scan in 1 second. Odd.

9

One thing I have found is that the KDE partition manager hangs like that if I have a USB-connected disc that’s handling a lot of I/O when I launch it. Presumably because the partition manager just can’t get the bandwidth it needs to scan the disc.

Though one other problem I had with it in the past was that it opened up and just stopped dead. Eventually I realised that the password dialogue had opened up behind the main window, so it was just waiting for my input. Creating a window rule that forced the password dialogue to the front solved that.

2 Likes
10

Avoid running graphical applications as root. See Running GUI applications as root - ArchWiki

5 Likes
11

OH!!! I tried that, and the scan time just dropped from 11 minutes to 20 seconds! I think it wasn’t the app itself, but one of its prerequisites, because I already tried simply “uninstall and reinstall the app” and it didn’t work. But when I also erased and reinstalled the dependencies, then it worked!

3 Likes
12

When you launch a GUI application as root - from a virtual terminal - information about the screen will be missing.

So not nonsense - it is normal when the application in question is not designed for launching as root from the console.

But you failed to provide that info - that you were trying to launch it that way - and that lack of information sent your fellow forum members on a wild goose chase.

It emphasise the necessity of providing all information - in this case it is not a bug in the system but …

2 Likes
13

No, I did not; you simply failed to notice.

“Providing all information“ would take infinite time to research, infinite time to write, and infinite time to read. This is not possible. So I provide pertinent information instead. Persons needing further specific info need only ask.

Yes, nonsense, because it’s a red herring, having nothing to with the actual problem. The real problem was that there was a problem with one of prerequisites of KDE Partition Manager on the problem machine, fixed by uninstalling not only the app, but also its prerequisites, then re-installing them. User “soundofthunder” suspected this, and that suspicion was right. I’m pretty sure it was the “smartmon” plugin, to be more specific. Now working correctly.

Tip: Attempting to find causes and cures for problems is generally more productive than attempting to find someone to blame.

14

I am sorry to say - there is absolutely no info on how you tried to launch partitionmanager except from the command itself which only points to a zsh default prompt.

I have been been banging my head on a similar issue with my rescue ISO which boots to commandline and I wanted to create a new graphical session as root - similar messages - I even tried variations of setting the screen and some environment - but in the end I failed - same message.

And being able to provide a meaningful answer will always depend on the information provided - if you had told us you were trying to launch partitionmanager from a virtual terminal as root - I would have said - don’t - there is no screen available - therefore the attempt will fail.

Instead I wrote it of as a possible theme issue, as I could not replicate your issue on a default system.

I don’t know where you got that idea. It is absolute waste of time trying to troubleshoot an issue which cannot be replicated with the information given.

15

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.