https://bugs.kde.org/show_bug.cgi?id=346118
--- Comment #89 from lld.pa...@gmail.com --- Hi, I deeply appreciate your interest and response in this matter, I'm really not an expert, I can hardly understand what you wrote, and I can simply understand programming code, going through it, but that's about it... I am a dedicated linux user, I am as "expert" as that can take me, without investing any more extra time on it. I am a network engineer, so linux is a natural choice/environment for me. Anyway, I'm afraid I can't help you much, unless you specify files and logs that you need, or further config details. What I can tell you, is that after I read your mail, I performed all offered upgrades in my system, and then tried it again. Just before I write this mail: 1. Disconnect manually from Network Manager GUI my work cable Ethernet connection. 2. Choose a wifi connection, select, then "connect". It automatically produced a crash. 3. Once I see the menu bars again, I open the NM again, and select my VPN profile to connect at work (the Wifi is an external connection). As soon as I select it, it crashes again: Graphical interface goes, and comes back: Same visual effect as if "Explorer" process has crashed in Windows. You see your desktop background empty, with nothing on it for a short while, then things come back again. 4. Give up, disconnect VPN and WiFi, connect back to Ethernet connection : To be honest, I was expecting another crash, but it didn't. It seems to go back to Wired Ethernet, OK. However, applications of wifi and VPN profiles make the GUI crash. If I could bet money on it, I would bet that wifi doesn't always fail, but aplication of VPN profile still always does. Curiously enough, (it doesn't always occur, but) some of the times, when the crash occurs, Thunderbird goes as well. However, this does not occur always, this is why I cannot insist on it, I just mention it in case it provides a hint. If you need any further info from my system, please do not hesitate to ask, I'd be happy to provide as much info as I can. But once I opened the bug through the reporting tool, I do not keep reporting, because I do not want to stuff the system with duplicate info. Kind Regards, Panos K On 18/04/16 18:37, via KDE Bugzilla wrote: > https://bugs.kde.org/show_bug.cgi?id=346118 > > --- Comment #88 from madc...@atlas.cz --- > Thanks for pointing me to this bug. I did a little investigation on my own, > although I'm not sure how useful it was. I discovered a few things. > > Dave's "debug 2" patch appears to be wrong. The patch leads to this code: > > for (int i = 0; i < signalIndexes.count(); ++i) > qDebug() << "DAVE notifying delegates"; > QMetaObject::activate(item, signalIndexes.at(i), 0); > > which I assume is supposed to look like this instead: > > qDebug() << "DAVE notifying delegates"; > for (int i = 0; i < signalIndexes.count(); ++i) > QMetaObject::activate(item, signalIndexes.at(i), 0); > > > I believe that's what's caused the odd behavior noticed by Alexander. > > I modified the patch and replaced qDebug() with fputs(), hoping that if there > is a threading issue the simpler nature of fputs() might not mess with the > timing too much to mask the problem. qt5-declarative package with my patch > still crashes the plasma for me with the following output in the terminal. To > trigger the crash I had my laptop connect to network "labak" and once the link > was up I tried to connect to another available network: > > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > Currrent active notifications: QHash() > Guessing partOf as: 0 > New Notification: "labak" "Connection 'labak' activated." -1 & Part of: 0 > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > DAVE notifying delegates > KCrash: Attempting to start /usr/bin/plasmashell from kdeinit > sock_file=/run/user/1000/kdeinit5__0 > KCrash: Application 'plasmashell' crashing... > KCrash: Attempting to start /usr/lib/drkonqi from kdeinit > sock_file=/run/user/1000/kdeinit5__0 > QSocketNotifier: Invalid socket 8 and type 'Read', disabling... > QSocketNotifier: Invalid socket 18 and type 'Read', disabling... > zsh: suspended (signal) plasmashell > -- You are receiving this mail because: You are watching all bug changes.
