https://bugs.kde.org/show_bug.cgi?id=378513
--- Comment #22 from Alexey A Nikitin ---
I noticed that I still get similar stack trace on exiting Kontact with
Akregator embedded in it if I exit it while it's minimized to tray:
Thread 1 (Thread 0x7fc49d7cd900 (LWP 4503)):
[KCrash Handle
https://bugs.kde.org/show_bug.cgi?id=378513
--- Comment #17 from Alexey A Nikitin ---
(In reply to Matthijs from comment #16)
> The issue Alexey A Nikitin describes does not appear to be the same as my
> issue, since I did not disable the menubar.
If the stack trace is (nearly) the same c
https://bugs.kde.org/show_bug.cgi?id=378513
--- Comment #15 from Alexey A Nikitin ---
Oh, completely forgot to mention - this is on Ubuntu 16.04 with KDE Neon User
repos, Akregator and Kontact versions 5.5.2.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=378513
--- Comment #14 from Alexey A Nikitin ---
I suspect some of the menu code (in particular the article menu) is written in
such a way that whenever menubar is disabled that causes a) the article menu to
stop working and b) Akregator to crash on either
https://bugs.kde.org/show_bug.cgi?id=378513
--- Comment #13 from Alexey A Nikitin ---
I think I found what triggers the crash. Akregator doesn't seem to like the
Title bar button Menubar style, as soon as I switched from Title bar button to
In application Akregator stopped crashing, on swit
https://bugs.kde.org/show_bug.cgi?id=378513
Alexey A Nikitin changed:
What|Removed |Added
CC||moonwal...@syrius.us
--- Comment #12 from
