Bug 2001798 - Endless crashing loop with kdeinit5
Summary: Endless crashing loop with kdeinit5
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: kf5-baloo
Version: epel8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-07 08:27 UTC by Julius Schwartzenberg
Modified: 2022-08-23 00:40 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)
DRKonqi crash information (2.64 KB, text/plain)
2021-09-07 08:27 UTC, Julius Schwartzenberg
no flags Details

Description Julius Schwartzenberg 2021-09-07 08:27:05 UTC
Created attachment 1821091 [details]
DRKonqi crash information

Description of problem:
When I start KDE Plasma instead of having working KDE applications, there's a constant stream of kdeinit5 crashes.

Version-Release number of selected component (if applicable):
5.68

How reproducible:
Maybe something special in my user settings triggers this. I just need to start things through 'startx' to reproduce this.

Steps to Reproduce:
1. Install KDE Plasma
2. startx

Actual results:
Constant pop-ups of kdeinit5 crashes

Expected results:
Stable KDE Plasma environment

Additional info:
See the attached stacktrace from the DRKonqi dialog.

Comment 1 Julius Schwartzenberg 2021-09-07 16:02:52 UTC
I'm also observing baloo_file_extr behavior as I use the rest of the desktop:

MiB Mem :  31866.9 total,    189.3 free,  31049.8 used,    627.8 buff/cache
MiB Swap:  32168.0 total,      0.0 free,  32168.0 used.     79.2 avail Mem

 647701 julius  39  19  309.1g  25.7g      0 R   0.4  82.7 177:33.17 baloo_file_extr

This makes the system unusable until the process is killed.

Comment 2 Fedora Admin user for bugzilla script actions 2022-08-23 00:40:13 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.


Note You need to log in before you can comment on or make changes to this bug.