[akregator] [Bug 383710] akregator always crashed on next login "with start with the system"

2018-02-10 Thread K G
https://bugs.kde.org/show_bug.cgi?id=383710 --- Comment #14 from K G <go...@wp.pl> --- This fix do not prevent from corrupting feeds. In my case it was happening sometimes after akregator crash. It only make akregator usable with global menu. it avoids akregator crashing 100% times.

[akregator] [Bug 383710] akregator always crashed on next login "with start with the system"

2018-02-09 Thread K G
https://bugs.kde.org/show_bug.cgi?id=383710 --- Comment #12 from K G <go...@wp.pl> --- Created attachment 110493 --> https://bugs.kde.org/attachment.cgi?id=110493=edit The simplest fix -- You are receiving this mail because: You are watching all bug changes.

[akregator] [Bug 383710] akregator always crashed on next login "with start with the system"

2018-02-09 Thread K G
https://bugs.kde.org/show_bug.cgi?id=383710 --- Comment #11 from K G <go...@wp.pl> --- Created attachment 110492 --> https://bugs.kde.org/attachment.cgi?id=110492=edit Trace of double initialisation -- You are receiving this mail because: You are watching all bug changes.

[akregator] [Bug 383710] akregator always crashed on next login "with start with the system"

2018-02-09 Thread K G
https://bugs.kde.org/show_bug.cgi?id=383710 --- Comment #10 from K G <go...@wp.pl> --- I'm not sure if it's relevant for this bug but it is for sure relevant to bug 384975 marked as duplicate. The problem is that akregator kpart is initialized twice, recursively. (See attached trace #45

[akregator] [Bug 383710] akregator always crashed on next login "with start with the system"

2018-02-09 Thread K G
https://bugs.kde.org/show_bug.cgi?id=383710 --- Comment #9 from K G <go...@wp.pl> --- I'm not sure if it's relevant for this bug but it is for sure relevant to bug 384975 marked as duplicate. The problem is that akregator kpart is initialized twice, recursively. (See attached trace #45

[akregator] [Bug 383710] akregator always crashed on next login "with start with the system"

2017-10-22 Thread K G
https://bugs.kde.org/show_bug.cgi?id=383710 --- Comment #8 from K G <go...@wp.pl> --- from bug 384975 Steps to reproduce bug: Turn on global menu. Turn on Akregator Select any feed in Akregator Boom - Crash -- You are receiving this mail because: You are watching all bug changes.

[akregator] [Bug 384975] Akregator crash after selecting feed.

2017-10-19 Thread K G
https://bugs.kde.org/show_bug.cgi?id=384975 K G <go...@wp.pl> changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUP

[akregator] [Bug 384975] Akregator crash after selecting feed.

2017-10-04 Thread K G
https://bugs.kde.org/show_bug.cgi?id=384975 --- Comment #2 from K G <go...@wp.pl> --- I've figured out, that crash appears only if global menu is active. After disabling global menu in widget style Akregator stops crashing. -- You are receiving this mail because: You are watching a

[akregator] [Bug 384975] Akregator crash after selecting feed.

2017-10-04 Thread K G
https://bugs.kde.org/show_bug.cgi?id=384975 --- Comment #1 from K G <go...@wp.pl> --- I've figured out, that crash appears only if global menu is active. After disabling global menu in widget style Akregator stops crashing. -- You are receiving this mail because: You are watching a

[akregator] [Bug 384975] New: Akregator crash after selecting feed.

2017-09-22 Thread K G
https://bugs.kde.org/show_bug.cgi?id=384975 Bug ID: 384975 Summary: Akregator crash after selecting feed. Product: akregator Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED

[kwin] [Bug 378960] Block around cursor does not update with nvidia proprietary

2017-06-26 Thread K G
https://bugs.kde.org/show_bug.cgi?id=378960 K G <go...@wp.pl> changed: What|Removed |Added CC||go...@wp.pl --- Comment #2 from K