Created attachment 2057195 [details]
File: proc_pid_status

Created attachment 2057196 [details]
File: maps

Created attachment 2057197 [details]
File: limits

Created attachment 2057198 [details]
File: cgroup

Created attachment 2057199 [details]
File: environ

Created attachment 2057200 [details]
File: open_fds

Created attachment 2057201 [details]
File: mountinfo

Created attachment 2057202 [details]
File: os_info

Created attachment 2057203 [details]
File: cpuinfo

Created attachment 2057204 [details]
File: core_backtrace

Created attachment 2057205 [details]
File: dso_list

Created attachment 2057206 [details]
File: backtrace

not sure what happened. i may have done something wrong by using dnf command line and installing / deinstalling something.


reporter:       libreport-2.17.15
backtrace_rating: 4
rootdir:        /
kernel:         6.12.4-200.fc41.x86_64
type:           CCpp
cgroup:         0::/user.slice/user-1001.slice/user/background.slice/plasma-gmenudbusmenuproxy.service
crash_function: qAbort
cmdline:        /usr/bin/gmenudbusmenuproxy
package:        plasma-workspace-6.2.4-1.fc41
reason:         gmenudbusmenuproxy killed by SIGABRT
xsession_errors: 
journald_cursor: s=eceb0c336e974ea39ea7048c7f105e78;i=37b3b0;b=fe6fb4474f254aa3842237fcbdd365f5;m=181139fdb;t=629c9d809b1f8;x=c916937f78712031
uid:            1001
comment:        not sure what happened. i may have done something wrong by using dnf command line and installing / deinstalling something.
executable:     /usr/bin/gmenudbusmenuproxy
runlevel:       5 3

i have reorted many bugs - hope it helps. i'm afraid though, cuz i musta have had an error in my way of using and setting up my system with the DNF4 and later DNF5 package system, I might have produced a lot of useless errors? (back then i had many crashes of various SW every day.) cuz now that i reinstalled some packages i have hardly any error at all any more. i am still reporting of course, still hoping it helps. just wanted to let you know that i figure i'll be spamming less maybe now :-)

kindest regards,
Markus

Per its counterpart report at https://bugs.kde.org/show_bug.cgi?id=500038#c0:

> I searched for the "Switch User" menu entry because it isn't listed by default in Kicker's favourites section. When I selected it, a window appeared momentarily, before the shell crashed.
> 
> Immediately, Dr Konqi appeared. 15s afterward, when it had restarted, I saw a notification that GNOME Abrt had caught it too, and I shall share the URI to its logs when they become available (it's slower to process them than Konqi is).


reporter:       libreport-2.17.15
type:           CCpp
reason:         plasmashell killed by SIGABRT
journald_cursor: s=06106dadbac546c19504e2cb07ea322d;i=32a501;b=5e87687dee33447d88a5a5696d44b14d;m=8557dd8cf;t=62e0e76cb8fb8;x=73a64cad29e349c9
executable:     /usr/bin/plasmashell
cmdline:        /usr/bin/plasmashell --no-respawn
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/plasma-plasmashell.service
rootdir:        /
uid:            1000
kernel:         6.12.11-200.fc41.x86_64
package:        plasma-workspace-6.3.0-1.fc41
runlevel:       N 5
dso_list:       /usr/bin/plasmashell plasma-workspace-6.3.0-1.fc41.x86_64 (Fedora Project) 1739357672
backtrace_rating: 4
crash_function: qAbort

(In reply to Markus Nicolussi from comment #14)  
> i have reorted many bugs - hope it helps. i'm afraid though, cuz i musta
> have had an error in my way of using and setting up my system with the DNF4
> and later DNF5 package system, I might have produced a lot of useless
> errors? (back then i had many crashes of various SW every day.) cuz now that
> i reinstalled some packages i have hardly any error at all any more. i am
> still reporting of course, still hoping it helps. just wanted to let you
> know that i figure i'll be spamming less maybe now :-)

You're doing God's work by reporting all that you can. If they didn't want the reports, they wouldn't make Abrt so wonderfully simple to use.

> OS: Unspecified

Anyway, you might want to set the OS to Linux - for some reason, Abrt doesn't do so, and I've yet to report that deficiency of it myself.

Please see https://bugs.kde.org/show_bug.cgi?id=500208#c0:~:text=about%20the%20crash:-,Invoking%20Firefox%20with%20the%20%22Switch,not%20seem%20to%20be%20reproducible.,-%2D%2D%20Backtrace%20(Reduced):

> Invoking Firefox with the "Switch User" modal window open caused Plasma Shell to crash.


reporter:       libreport-2.17.15
type:           CCpp
reason:         krunner killed by SIGABRT
journald_cursor: s=a2d6d580caa24cf3a9483be7f85033e4;i=2f968;b=3544ca03c97a4c89860576f5419864cb;m=7822e070;t=62e466d0c4cfb;x=f6d9fc6926130200
executable:     /usr/bin/krunner
cmdline:        /usr/bin/krunner --daemon
cgroup:         0::/user.slice/user-1000.slice/user/background.slice/plasma-krunner.service
rootdir:        /
uid:            1000
kernel:         6.12.13-200.fc41.x86_64
package:        plasma-workspace-6.3.0-1.fc41
runlevel:       N 5
backtrace_rating: 4
crash_function: qAbort

The counterpart to https://bugs.kde.org/show_bug.cgi?id=500209#c0:~:text=A%20duplicate%20of%20https://bugs.kde.org/show_bug.cgi?id=500038%23c0%2C%20encountered%20whilst%20attempting%20to%20reproduce%20https://bugs.kde.org/show_bug.cgi?id=500208%23c0%20(in%20KRunner).


reporter:       libreport-2.17.15
type:           CCpp
reason:         plasmashell killed by SIGABRT
journald_cursor: s=a2d6d580caa24cf3a9483be7f85033e4;i=30620;b=3544ca03c97a4c89860576f5419864cb;m=119f6293e;t=62e470edf95ca;x=a15a9a61ee22ea20
executable:     /usr/bin/plasmashell
cmdline:        /usr/bin/plasmashell --no-respawn
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/plasma-plasmashell.service
rootdir:        /
uid:            1000
kernel:         6.12.13-200.fc41.x86_64
package:        plasma-workspace-6.3.0-1.fc41
backtrace_rating: 4
runlevel:       N 5
crash_function: qt_assert(char const*, char const*, int)
comment:        The counterpart to https://bugs.kde.org/show_bug.cgi?id=500209#c0:~:text=A%20duplicate%20of%20https://bugs.kde.org/show_bug.cgi?id=500038%23c0%2C%20encountered%20whilst%20attempting%20to%20reproduce%20https://bugs.kde.org/show_bug.cgi?id=500208%23c0%20(in%20KRunner).

Wayland has crashed after connecting a Dell Docking Station (TB16)


reporter:       libreport-2.17.15
type:           CCpp
reason:         gmenudbusmenuproxy killed by SIGABRT
journald_cursor: s=2f2903e839b04099aebe0e67e67ac2ee;i=1acc16;b=ad3a048c026d4cdb85f8550d47f1f520;m=1163006483;t=62f752ab05e5b;x=5dca54249c609c74
executable:     /usr/bin/gmenudbusmenuproxy
cmdline:        /usr/bin/gmenudbusmenuproxy
cgroup:         0::/user.slice/user-1333.slice/user/background.slice/plasma-gmenudbusmenuproxy.service
rootdir:        /
uid:            1333
kernel:         6.13.5-200.fc41.x86_64
package:        plasma-workspace-6.3.2-1.fc41
runlevel:       N 5
xsession_errors: 
backtrace_rating: 4
crash_function: qAbort
comment:        Wayland has crashed after connecting a Dell Docking Station (TB16)

Wayland has crashed after connecting a Dell Docking Station (TB16)


reporter:       libreport-2.17.15
type:           CCpp
reason:         xembedsniproxy killed by SIGABRT
journald_cursor: s=2f2903e839b04099aebe0e67e67ac2ee;i=1acc18;b=ad3a048c026d4cdb85f8550d47f1f520;m=116300864a;t=62f752ab08022;x=1904f0fb2682bde7
executable:     /usr/bin/xembedsniproxy
cmdline:        /usr/bin/xembedsniproxy
cgroup:         0::/user.slice/user-1333.slice/user/background.slice/plasma-xembedsniproxy.service
rootdir:        /
uid:            1333
kernel:         6.13.5-200.fc41.x86_64
package:        plasma-workspace-6.3.2-1.fc41
runlevel:       N 5
backtrace_rating: 4
crash_function: qAbort
comment:        Wayland has crashed after connecting a Dell Docking Station (TB16)

plasma and wayland has crashed during yum update
my laptop has connected to dell dock with 3 screens


reporter:       libreport-2.17.15
type:           CCpp
reason:         plasma-fallback-session-restore killed by SIGABRT
journald_cursor: s=2f2903e839b04099aebe0e67e67ac2ee;i=1c7bcd;b=937f5286519e4a80b0a75e173eee157a;m=279be5e813;t=62fee1b335286;x=c1ca94cbfcd4cc41
executable:     /usr/libexec/plasma-fallback-session-restore
cmdline:        /usr/libexec/plasma-fallback-session-restore
cgroup:         0::/user.slice/user-1333.slice/user/app.slice/app-org.kde.plasma\x2dfallback\x2dsession\x2drestore
rootdir:        /
uid:            1333
kernel:         6.13.5-200.fc41.x86_64
package:        plasma-workspace-6.3.2-1.fc41
runlevel:       N 5
xsession_errors: 
backtrace_rating: 4
crash_function: qAbort

plasma and wayland has crashed during yum update
my laptop has connected to dell dock with 3 screens


reporter:       libreport-2.17.15
type:           CCpp
reason:         kcminit killed by SIGABRT
journald_cursor: s=2f2903e839b04099aebe0e67e67ac2ee;i=1c6b96;b=937f5286519e4a80b0a75e173eee157a;m=278f48e196;t=62fee0e964c09;x=66f0651d72f704ee
executable:     /usr/bin/kcminit
cmdline:        /usr/bin/kcminit_startup
cgroup:         0::/user.slice/user-1333.slice/user/session.slice/plasma-kcminit.service
rootdir:        /
uid:            1333
kernel:         6.13.5-200.fc41.x86_64
package:        plasma-workspace-6.3.2-1.fc41
runlevel:       N 5
backtrace_rating: 4
crash_function: qAbort

plasma and wayland has crashed during yum update
my laptop has connected to dell dock with 3 screens


reporter:       libreport-2.17.15
type:           CCpp
reason:         ksplashqml killed by SIGABRT
journald_cursor: s=2f2903e839b04099aebe0e67e67ac2ee;i=1c6bad;b=937f5286519e4a80b0a75e173eee157a;m=278f49c0b0;t=62fee0e972b24;x=c7d59f5ec7e0452
executable:     /usr/bin/ksplashqml
cmdline:        /usr/bin/ksplashqml
cgroup:         0::/user.slice/user-1333.slice/user/background.slice/plasma-ksplash.service
rootdir:        /
uid:            1333
kernel:         6.13.5-200.fc41.x86_64
package:        plasma-workspace-6.3.2-1.fc41
runlevel:       N 5
xsession_errors: 
backtrace_rating: 4
crash_function: qAbort

plasma and wayland has crashed during yum update
my laptop has connected to dell dock with 3 screens


reporter:       libreport-2.17.15
type:           CCpp
reason:         ksmserver killed by SIGABRT
journald_cursor: s=2f2903e839b04099aebe0e67e67ac2ee;i=1c6c3b;b=937f5286519e4a80b0a75e173eee157a;m=278f4fcebb;t=62fee0e9d392e;x=17f2bdb028c8078d
executable:     /usr/bin/ksmserver
cmdline:        /usr/bin/ksmserver
cgroup:         0::/user.slice/user-1333.slice/user/session.slice/plasma-ksmserver.service
rootdir:        /
uid:            1333
kernel:         6.13.5-200.fc41.x86_64
package:        plasma-workspace-6.3.2-1.fc41
runlevel:       N 5
xsession_errors: 
backtrace_rating: 4
crash_function: qAbort

(In reply to kevinleroy from comment #24)
> plasma and wayland has crashed during yum update

Why on Earth are you still using YUM in 2025? That's two symlinks behind – we're at DNF5 now.

This message is a reminder that Fedora Linux 41 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '41'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 41 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

https://bugzilla.redhat.com/show_bug.cgi?id=2325351#c15 continues to reproduce, for me.

Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15.

Fedora Linux 41 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

I continue to reproduce this. However, per https://discussion.fedoraproject.org/t/why-has-abrt-silently-ceased-to-enumerate-coredumpctls-entries/172903/3, can't submit it via Abrt (yet).