On Tue, Sep 3, 2019 at 7:57 AM John Pilkington <johnpilk222@xxxxxxxxx> wrote: > > On 03/09/2019 15:00, Rex Dieter wrote: > > Rex Dieter wrote: > > > >> 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) > > > > I'm officially out of ideas and have exhausted my developer-fu trying to > > make sense of these traces. > > > > Any other ideas or suggestions? > > > > -- Rex > > Thanks for looking at this. > > I'm not seeing the conttinuing repeats anymore, but can still provoke 2 > instances by closing dolphin; mainly I use konqueror as FM. There was a > bunch of kde-settings updates around the time the repeats stopped. FWIW > I get a vaguely similar notification on booting kubuntu 18.04, and I > still suspect it might have something to do with having used kdesu with > konqueror, or maybe SystemSettings, in the past. ISTR that in 'buntu > the apology comes from konq. > > There's also something probably self-inflicted in my System Settings > launcher, which can't find plasma-systemsettings. I can launch it from > the search thingy. > > John > Yep, closing dolphin produces the errors on demand :) Ya!! (That was only half sarcastic. Producing an error on demand helps debug alot) If I do that while running journalctl -f I get the following ---------- Sep 03 09:54:56 tlaptop kwin_x11[2342]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 28593, resource id: 132120582, major code: 15 (QueryTree), minor code: 0 Sep 03 09:54:56 tlaptop kwin_x11[2342]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 28680, resource id: 134217739, major code: 18 (ChangeProperty), minor code: 0 Sep 03 09:54:56 tlaptop kwin_x11[2342]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 28684, resource id: 132120593, major code: 18 (ChangeProperty), minor code: 0 Sep 03 09:54:56 tlaptop systemd[1]: Started Process Core Dump (PID 6655/UID 0). Sep 03 09:54:56 tlaptop systemd[1]: Started Process Core Dump (PID 6660/UID 0). Sep 03 09:54:56 tlaptop systemd[1]: Started Process Core Dump (PID 6664/UID 0). Sep 03 09:54:56 tlaptop plasmashell[2351]: QQuickItem::stackAfter: Cannot stack StatusNotifierItem_QMLTYPE_290(0x5559ad270a50, parent=0x5559a9c04560, geometry=0,0 0x0) after StatusNotifierItem_QMLTYPE_290(0x7f31500435e0), which must be a sibling Sep 03 09:54:56 tlaptop systemd-coredump[6662]: Process 6645 (file.so) of user 1000 dumped core. Stack trace of thread 6645: #0 0x00007f34363cffa5 _ZN6QMutex4lockEv (libQt5Core.so.5) #1 0x00007f34365c17e6 _ZN10QTextCodec14codecForLocaleEv (libQt5Core.so.5) #2 0x00007f343644da09 _ZN7QString20fromLocal8Bit_helperEPKci (libQt5Core.so.5) #3 0x00007f3436521928 _ZN14QStandardPaths16writableLocationENS_16StandardLocationE (libQt5Core.so.5) #4 0x00007f3437fe5861 _ZL20startProcessInternaliPPKcbb (libKF5Crash.so.5) #5 0x00007f3437fe6322 _ZN6KCrash12startProcessEiPPKcb (libKF5Crash.so.5) #6 0x00007f3437fe67d5 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5) #7 0x00007f343565e9c0 .annobin_sigaction.c (libc.so.6) ---------- and then the STace trace repeated twice more with just the begginning number changing. Troy _______________________________________________ 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
