Rex Dieter wrote: > Rex Dieter wrote: > >> John Pilkington wrote: >> >>> With fully updated F29 I'm suddenly seeing this. 'Please report' but >>> reporting and debugging seem broken for this. I wonder if it's related >>> to historic enabling of kdesu and perhaps the kannolo repo? >> >> I'm able to reproduce, but I'm at a loss where the problem comes from. >> >> I tried building kf5-5.61.0 locally, and the problem remained. >> >> I see it's been reported, >> https://bugzilla.redhat.com/show_bug.cgi?id=1746465 >> https://bugzilla.redhat.com/show_bug.cgi?id=1743895 >> >> and upstream at >> https://bugs.kde.org/show_bug.cgi?id=411441 > > I think I've found one workaround, at least after some initial testing, if > you set > KDE_DEBUG=1 > in your environment, which effectively disabled drkonqi crash reporter, > then the kdeinit errors stop happening. > > I set that in /etc/xdg/plasma-workspace/env/env.sh, adding the line: > export KDE_DEBUG=1 So, that only hides the crashes, my journalctl still includes entries like Process ... (file.so) of user ... dumped core. Stack trace of thread ...: #0 0x000000000000 n/a (n/a) -- Rex _______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@xxxxxxxxxxxxxxxxxxxxxxx
