Bug 2273853

Created attachment 2025653 [details]
File: proc_pid_status

Created attachment 2025654 [details]
File: maps

Created attachment 2025655 [details]
File: limits

Created attachment 2025656 [details]
File: environ

Created attachment 2025657 [details]
File: open_fds

Created attachment 2025658 [details]
File: mountinfo

Created attachment 2025659 [details]
File: os_info

Created attachment 2025660 [details]
File: cpuinfo

Created attachment 2025661 [details]
File: core_backtrace

Created attachment 2025662 [details]
File: dso_list

Created attachment 2025663 [details]
File: var_log_messages

Created attachment 2025664 [details]
File: backtrace

Occurred immediately subsequent to automatic user login (itself obviously immediately subsequent to system+OS initialization).


reporter:       libreport-2.17.15
type:           CCpp
reason:         baloo_file killed by SIGSEGV
journald_cursor: s=89fb6a9bc3bf49ac898315f32a5d8f9e;i=c4ad8;b=a675ef69dd5c4f979c765adc8c3d194d;m=331b47b3;t=61570403853f0;x=91b472f9e71ce852
executable:     /usr/libexec/kf6/baloo_file
cmdline:        /usr/libexec/kf6/baloo_file
cgroup:         0::/user.slice/user-1000.slice/user/background.slice/kde-baloo.service
rootdir:        /
uid:            1000
kernel:         6.8.4-300.fc40.x86_64
package:        kf6-baloo-file-6.0.0-3.fc40
runlevel:       N 5
comment:        Occurred immediately subsequent to automatic user login (itself obviously immediately subsequent to system+OS initialization).
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler

At Fedora OS launch


reporter:       libreport-2.17.15
type:           CCpp
reason:         baloo_file killed by SIGSEGV
journald_cursor: s=7be6ac2cc72043e68c517432e0090ac8;i=15a6e9c;b=dbe93580491e4791962423ec3c7cda95;m=1d117f9c;t=617b1d7541657;x=60708dcc81510a7a
executable:     /usr/libexec/kf6/baloo_file
cmdline:        /usr/libexec/kf6/baloo_file
cgroup:         0::/user.slice/user-1000.slice/user/background.slice/kde-baloo.service
rootdir:        /
uid:            1000
kernel:         6.8.8-300.fc40.x86_64
package:        kf6-baloo-file-6.1.0-1.fc40
runlevel:       N 5
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler
comment:        At Fedora OS launch

Uncertain. Problem happend when the machine was idle and went to sleep or was awaken from sleep.

Probably unrelated: I see x wndows driver VM errors causing the display not to wait from sleep and forcing a hard reset. May not be related or might be one causes the other.


reporter:       libreport-2.17.15
type:           CCpp
reason:         baloo_file killed by SIGSEGV
journald_cursor: s=e229cdb11d9c404698a263f61ee4adbd;i=9069;b=8a98fb26214a45819b5040541fe9b7e7;m=17bc9a46;t=622b605ea8f47;x=d49258ab3e1c5de
executable:     /usr/libexec/kf6/baloo_file
cmdline:        /usr/libexec/kf6/baloo_file
cgroup:         0::/user.slice/user-1000.slice/user/background.slice/kde-baloo.service
rootdir:        /
uid:            1000
kernel:         6.10.10-200.fc40.x86_64
package:        kf6-baloo-file-6.6.0-1.fc40
runlevel:       N 5
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler

My backtrace: https://retrace.fedoraproject.org/faf/reports/1100063/

This message is a reminder that Fedora Linux 40 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13.
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 '40'.

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 40 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.

Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13.

Fedora Linux 40 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.