I’m trying to diagnose a serious failure, NOT THE SUBJECT OF THIS POST, that stops me from using F36, and in the course of investigating that I found that some recent change has caused a coredump of xdg-desktop-portal-kde every time the GUI starts in F35 or F36.
In F35, that seems to be symptom free after getting the coredump. xdg-desktop-portal-kde is running (I assume a different instance of it, but I haven’t investigated that yet in detail).
Core was generated by `/usr/libexec/xdg-desktop-portal-kde'.
Program terminated with signal SIGABRT, Aborted.
warning: Section `.reg-xstate/1503' in core file too small.
#0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
44 return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0;
[Current thread is 1 (Thread 0x7f467ec159c0 (LWP 1503))]
(gdb) where
#0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1 0x00007f4680e8ec73 in __pthread_kill_internal (signo=6, threadid=<optimized out>) at pthread_kill.c:78
#2 0x00007f4680e3e986 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#3 0x00007f4680e287f4 in __GI_abort () at abort.c:79
#4 0x00007f46816b14d5 in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
#5 QMessageLogger::fatal (this=this@entry=0x7ffe4b83fd10, msg=msg@entry=0x7f46829585a7 "%s") at global/qlogging.cpp:893
#6 0x00007f468256341b in init_platform (argv=<optimized out>, argc=<optimized out>, platformThemeName=..., platformPluginPath=...,
pluginNamesWithArguments=...) at kernel/qguiapplication.cpp:1254
#7 QGuiApplicationPrivate::createPlatformIntegration (this=0x5559a9add6e0) at kernel/qguiapplication.cpp:1477
#8 0x00007f46825638c8 in QGuiApplicationPrivate::createEventDispatcher (this=<optimized out>) at kernel/qguiapplication.cpp:1494
#9 0x00007f46818aeab1 in QCoreApplicationPrivate::init (this=this@entry=0x5559a9add6e0) at kernel/qcoreapplication.cpp:835
#10 0x00007f4682565c83 in QGuiApplicationPrivate::init (this=this@entry=0x5559a9add6e0) at kernel/qguiapplication.cpp:1523
#11 0x00007f46833b431d in QApplicationPrivate::init (this=0x5559a9add6e0) at kernel/qapplication.cpp:513
#12 0x00007f46833b4400 in QApplication::QApplication (this=this@entry=0x7ffe4b83ffa0, argc=@0x7ffe4b83ff6c: 1, argv=<optimized out>,
_internal=_internal@entry=331525) at kernel/qapplication.cpp:501
#13 0x00005559a8affad3 in main (argc=<optimized out>, argv=<optimized out>)
at /usr/src/debug/xdg-desktop-portal-kde-5.25.5-1.fc36.x86_64/src/xdg-desktop-portal-kde.cpp:27
I’m using the oldest architecture (340) closed source nvidia driver. That is the only driver that can work with my display card (nouveau can’t). That is probably a factor in this problem.
Do you know what this failure indicates?
I haven’t yet read about xdg-desktop-portal and don’t know where it fits in. I’m using sddm and kde and x11 (wayland crashes this system because of that old display card and I dislike gnome).
Any suggestions about steps for further diagnoses would be appreciated.
I got a reply to this issue while it was still an off-topic drift in my earlier thread:
I think the bug discussed there has a good chance of being the bug I’m asking about in this thread. But I can’t follow that linked discussion well enough to gain any actual insight from it.