[kdevelop] [Bug 369631] KDevelop crashed at startup

2016-10-03 Thread Afief Halumi via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369631 --- Comment #10 from Afief Halumi --- @Kevin I don't recall there being a specific file, but I was a bit distracted by things in my own code when it happened, so I'll take another look after the new year's celebrations are over.

[kdevelop] [Bug 369631] KDevelop crashed at startup

2016-10-03 Thread Afief Halumi via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369631 --- Comment #7 from Afief Halumi --- Is there a way to tell which file KDevelop was processing when it crashes? As far as I understand it processes all my files in the background to support better code navigation, so if the

[kdevelop] [Bug 369631] KDevelop crashed at startup

2016-10-02 Thread Afief Halumi via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369631 --- Comment #5 from Afief Halumi --- Unfortunately it isn't a free/public, it's a rather convoluted more than 20 years old codebase in some dire need for refactoring. If I had to guess I'd say the second bug somehow pollutes the

[kdevelop] [Bug 369631] KDevelop crashed at startup

2016-10-02 Thread Afief Halumi via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369631 --- Comment #3 from Afief Halumi --- I seem to be getting the same crash multiple times today (may have something to do wit the branch of the code I'm wroking with). This time it was a clean startup which cleared the cache due to

[kdevelop] [Bug 369631] KDevelop crashed at startup

2016-10-02 Thread Afief Halumi via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369631 --- Comment #2 from Afief Halumi --- The next startup gave me a popup about a possible cache corruption, so it fixed itself. -- You are receiving this mail because: You are watching all bug changes.

[kdevelop] [Bug 369631] New: KDevelop crashed at startup

2016-10-02 Thread Afief Halumi via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369631 Bug ID: 369631 Summary: KDevelop crashed at startup Product: kdevelop Version: 5.0.1 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: crash

[kdevelop] [Bug 368105] Wrong type is deduced for type auto

2016-09-05 Thread Afief Halumi via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368105 --- Comment #2 from Afief Halumi --- My bad, turns out I only got int* because the example didn't compile in the sample code. I was a bit too hasty trying to create a synthethic example from my work code. Sorry about that. I cannot

[kdevelop] [Bug 368105] New: Wrong type is deduced for type auto

2016-09-01 Thread Afief Halumi via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368105 Bug ID: 368105 Summary: Wrong type is deduced for type auto Product: kdevelop Version: 5.0.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal

[kdevelop] [Bug 368067] New: Wrong declaration is caught when class name as template parameter

2016-08-31 Thread Afief Halumi via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368067 Bug ID: 368067 Summary: Wrong declaration is caught when class name as template parameter Product: kdevelop Version: 5.0.0 Platform: Appimage OS: Linux

[frameworks-kidletime] [Bug 328987] Power saving should not trigger if joystick is in use

2015-12-17 Thread Afief Halumi via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=328987 --- Comment #9 from Afief Halumi --- Would donating a gamepad to a developer help or is this issue too far out of scope for KIdleTime? The input-devices in systemsettings seems to be aware of of the joysticks and be able to get their

[Powerdevil] [Bug 356636] New: Joystick input doesn't prevent screen from turning off

2015-12-13 Thread Afief Halumi via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356636 Bug ID: 356636 Summary: Joystick input doesn't prevent screen from turning off Product: Powerdevil Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED