Bug 514799 - Plasmashell hangs when browsing the System section of the application menu if the Dolphin entry is present due to an unavailable non-mounted NFS folder
Summary: Plasmashell hangs when browsing the System section of the application menu if...
Status: REPORTED
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (other bugs)
Version First Reported In: 6.5.5
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2026-01-18 17:53 UTC by bummer
Modified: 2026-01-20 16:40 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
New crash information added by DrKonqi (92.96 KB, text/plain)
2026-01-18 17:53 UTC, bummer 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description bummer 2026-01-18 17:53:02 UTC 
Application: plasmashell (6.5.5)

ApplicationNotResponding [ANR]: false
Qt Version: 6.9.3
Frameworks Version: 6.22.0
Operating System: Linux 6.18.5-100.fc42.x86_64 x86_64
Windowing System: X11
Distribution: "Fedora Linux 42 (KDE Plasma Desktop Edition)"
DrKonqi: 6.5.5 [CoredumpBackend]

-- Information about the crash:
When browsing the application menu, menu panes open and close, but with the system menu, the menus freeze and the whole taskbar, plasmashell and desktop become unresponsive until I restart using “systemctl restart --user plasma-plasmashell”. Here I must wait for the stop request to time out before SIGABRT is sent to plasmashell. At this point, we get a cope dump from plasmashell.
With plasmashell frozen, I can still cycle apps using Meta-Tab shortcuts and I can move windows.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#5  __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
#6  0x00007fd1ee67d71c in __internal_syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=a5@entry=8, a6=a6@entry=0, nr=271) at cancellation.c:49
#7  0x00007fd1ee67d764 in __syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=a5@entry=8, a6=a6@entry=0, nr=271) at cancellation.c:75
#8  0x00007fd1ee6f7786 in __GI_ppoll (fds=fds@entry=0x5644d87e73f0, nfds=nfds@entry=4, timeout=<optimized out>, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:42
#9  0x00007fd1ed7ff890 in ppoll (__fds=0x5644d87e73f0, __nfds=4, __timeout=0x0, __ss=0x0) at /usr/include/bits/poll2.h:101
#10 g_main_context_poll_unlocked (priority=<optimized out>, context=0x7fd1d4000c80, timeout_usec=<optimized out>, fds=0x5644d87e73f0, n_fds=4) at ../glib/gmain.c:4632
#11 g_main_context_iterate_unlocked (context=context@entry=0x7fd1d4000c80, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4309
#12 0x00007fd1ed7ff953 in g_main_context_iteration (context=0x7fd1d4000c80, may_block=1) at ../glib/gmain.c:4379
#13 0x00007fd1ef0104ed in QEventDispatcherGlib::processEvents (this=0x7fd1d4000b70, flags=...) at /usr/src/debug/qt6-qtbase-6.9.3-1.fc42.x86_64/src/corelib/kernel/qeventdispatcher_glib.cpp:399
#14 0x00007fd1eed07243 in QEventLoop::exec (this=this@entry=0x7fd1dadd6730, flags=..., flags@entry=...) at /usr/src/debug/qt6-qtbase-6.9.3-1.fc42.x86_64/src/corelib/global/qflags.h:77
#15 0x00007fd1eee2844d in QThread::exec (this=this@entry=0x7fd1f077ccc0 <QGlobalStatic<QtGlobalStatic::Holder<(anonymous namespace)::Q_QGS__q_manager> >::instance()::holder>) at /usr/src/debug/qt6-qtbase-6.9.3-1.fc42.x86_64/src/corelib/thread/qthread.cpp:664
#16 0x00007fd1f06ca721 in QDBusConnectionManager::run (this=0x7fd1f077ccc0 <QGlobalStatic<QtGlobalStatic::Holder<(anonymous namespace)::Q_QGS__q_manager> >::instance()::holder>) at /usr/src/debug/qt6-qtbase-6.9.3-1.fc42.x86_64/src/dbus/qdbusconnectionmanager.cpp:145
#17 0x00007fd1eeec6166 in operator() (__closure=<optimized out>) at /usr/src/debug/qt6-qtbase-6.9.3-1.fc42.x86_64/src/corelib/thread/qthread_unix.cpp:435
#19 QThreadPrivate::start (arg=0x7fd1f077ccc0 <QGlobalStatic<QtGlobalStatic::Holder<(anonymous namespace)::Q_QGS__q_manager> >::instance()::holder>) at /usr/src/debug/qt6-qtbase-6.9.3-1.fc42.x86_64/src/corelib/thread/qthread_unix.cpp:395
#20 0x00007fd1ee680f14 in start_thread (arg=<optimized out>) at pthread_create.c:448
#21 0x00007fd1ee7042ec in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78


Reported using DrKonqi
Comment 1 bummer 2026-01-18 17:53:03 UTC 
Created attachment 188649 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Akseli Lahtinen 2026-01-19 09:13:11 UTC 
Can you clarify what do you mean with "System menu?" Do you mean the "Places" tab in the application launcher?

Looking at the backtrace I see following:

Thread 3 (Thread 0x7fd1e8dd6300 (LWP 134857)):
#0  statx (fd=-100, path=0x5644e1fa6890 "/mnt/nfs/Documents8", flags=256, mask=2681, buf=0x7fffe9350aa0) at ../sysdeps/unix/sysv/linux/statx.c:28
#1  0x00007fd1ee0b254d in LSTAT (path=<optimized out>, buff=0x7fffe9350aa0, details=...) at /usr/src/debug/kf6-kio-6.22.0-1.fc42.x86_64/src/core/../kioworkers/file/stat_unix.h:45
#2  KFileItemPrivate::init (this=0x5644df063860) at /usr/src/debug/kf6-kio-6.22.0-1.fc42.x86_64/src/core/kfileitem.cpp:251
#3  0x00007fd1ee0b2d61 in KFileItemPrivate::ensureInitialized (this=<optimized out>) at /usr/src/debug/kf6-kio-6.22.0-1.fc42.x86_64/src/core/kfileitem.cpp:223
#4  KFileItem::isDir (this=this@entry=0x7fffe9350d00) at /usr/src/debug/kf6-kio-6.22.0-1.fc42.x86_64/src/core/kfileitem.cpp:1446
#5  0x00007fd1ee0b2d93 in KFileItem::isFile (this=0x7fffe9350d00) at /usr/src/debug/kf6-kio-6.22.0-1.fc42.x86_64/src/core/kfileitem.cpp:1462
#6  KFileItem::isFile (this=this@entry=0x7fffe9350d00) at /usr/src/debug/kf6-kio-6.22.0-1.fc42.x86_64/src/core/kfileitem.cpp:1456
#7  0x00007fd0f9769e5c in Kicker::recentDocumentActions (service=<optimized out>) at /usr/src/debug/plasma-workspace-6.5.5-1.fc42.x86_64/applets/kicker/actionlist.cpp:309
#8  0x00007fd0f9772f7f in AppEntry::actions (this=0x5644de56f9c0) at /usr/src/debug/plasma-workspace-6.5.5-1.fc42.x86_64/applets/kicker/appentry.cpp:331
#9  0x00007fd0f976f55a in AppsModel::data (this=this@entry=0x5644de5605a0, index=<optimized out>, role=role@entry=265) at /usr/src/debug/plasma-workspace-6.5.5-1.fc42.x86_64/applets/kicker/appsmodel.cpp:165
#10 0x00007fd0f978e1bb in ForwardingModel::data (this=<optimized out>, index=<optimized out>, role=265) at /usr/src/debug/plasma-workspace-6.5.5-1.fc42.x86_64/applets/kicker/forwardingmodel.cpp:95
#11 0x00007fd1edada05e in QModelIndex::data (this=0x7fffe93512b0, arole=265) at /usr/include/qt6/QtCore/qabstractitemmodel.h:519
#12 QQmlDMAbstractItemModelData::value (this=0x5644e1b54150, role=265) at /usr/src/debug/qt6-qtdeclarative-6.9.3-2.fc42.x86_64/src/qmlmodels/qqmldmabstractitemmodeldata.cpp:226
#13 0x00007fd1edada716 in QQmlDMAbstractItemModelData::metaCall (this=<optimized out>, call=<optimized out>, id=<optimized out>, arguments=0x7fffe93513d0) at /usr/src/debug/qt6-qtdeclarative-6.9.3-2.fc42.x86_64/src/qmlmodels/qqmldmabstractitemmodeldata.cpp:30


> "/mnt/nfs/Documents8"

Do you have network folder share there? That might explain the freezing.
Comment 3 bummer 2026-01-19 09:32:42 UTC 
System Menu refers to the part of the Application Menu that is labeled System. There’s also Office, Utilities, etc. They are automatically created and populated when software is installed, and of of course manually.

Using the “Edit Applications…” option, I was able to narrow it down to the Dolphin entry in the System group. After I removed that, it stopped freezing. I couldn’t find any suspicious menu item properties for Dolphin, though. 
Also, the Application Menu alternatives (like Application Dashboard and Launcher) did not have any problems presenting the Dolphin item.
Dolphin, when started directly from the Task Manager (where it is pinned), starts normally.

The nfs folder is not available, since the NAS is refers to is off. The folder is on autofs, not being accessed and doesn’t show in Dolphin itself when I run Dolphin. Not sure why it should affect the Application Menu.
Comment 4 Akseli Lahtinen 2026-01-19 12:56:38 UTC 
(In reply to bummer from comment #3)
> System Menu refers to the part of the Application Menu that is labeled
> System. There’s also Office, Utilities, etc. They are automatically created
> and populated when software is installed, and of of course manually.
> 
> Using the “Edit Applications…” option, I was able to narrow it down to the
> Dolphin entry in the System group. After I removed that, it stopped
> freezing. I couldn’t find any suspicious menu item properties for Dolphin,
> though. 
> Also, the Application Menu alternatives (like Application Dashboard and
> Launcher) did not have any problems presenting the Dolphin item.
> Dolphin, when started directly from the Task Manager (where it is pinned),
> starts normally.
> 
> The nfs folder is not available, since the NAS is refers to is off. The
> folder is on autofs, not being accessed and doesn’t show in Dolphin itself
> when I run Dolphin. Not sure why it should affect the Application Menu.

Interesting.. What I think is going on is that something is trying to access the NFS folder from the Dolphin right click menu (If you right-click Dolphin icon, then it shows recent files). If the NFS folder is there, maybe it gets all kinds of confused..

Will need to investigate this further, thanks!
Comment 5 bummer 2026-01-19 20:53:43 UTC 
(In reply to Akseli Lahtinen from comment #4)

> Interesting.. What I think is going on is that something is trying to access
> the NFS folder from the Dolphin right click menu (If you right-click Dolphin
> icon, then it shows recent files). If the NFS folder is there, maybe it gets
> all kinds of confused..

well in that case: When I right-click the Dolphin icon in the task bar, I get what I see in the places list in a regular Dolphin windows. Followed by the Remote and Recent submenus. The NAS with its NFS folder hasn’t been used for some days, many reboots ago, and it doesn’t appear in any of these lists, nor is there any freeze-up when playing with Dolphin once open.