[Akonadi] [Bug 358467] on session start mysqld goes into 100% CPU and is not killable

2016-01-25 Thread Matthias Apitz via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358467 Matthias Apitz changed: What|Removed |Added CC||g...@unixarea.de -- You

[Akonadi] [Bug 358467] New: on session start mysqld goes into 100% CPU and is not killable

2016-01-24 Thread Matthias Apitz via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358467 Bug ID: 358467 Summary: on session start mysqld goes into 100% CPU and is not killable Product: Akonadi Version: 1.13.0 Platform: FreeBSD Ports OS: FreeBSD

[kde] [Bug 356331] KDE Power Management System init failed!

2015-12-12 Thread Matthias Apitz via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356331 --- Comment #3 from Matthias Apitz --- I think, we can close this issue here; Seems to be really a hald problem, and not a KDE4 problem; right now it occured again and qdbus only says: $ qdbus --system :1.2

[kde] [Bug 356331] KDE Power Management System init failed!

2015-12-09 Thread Matthias Apitz via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356331 --- Comment #2 from Matthias Apitz --- I have had it today again and the situation re/ hald is like this in the moment of 'startx': 885 - Ds 0:00,01 /usr/local/sbin/hald 890 - I0:00,03 hald-runner 764 v0- I0:00,01

[kde] [Bug 356331] New: KDE Power Management System init failed!

2015-12-06 Thread Matthias Apitz via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356331 Bug ID: 356331 Summary: KDE Power Management System init failed! Product: kde Version: 4.14.1 Platform: FreeBSD Ports OS: FreeBSD Status: UNCONFIRMED Severity:

[kde] [Bug 356331] KDE Power Management System init failed!

2015-12-06 Thread Matthias Apitz via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356331 Matthias Apitz changed: What|Removed |Added CC||g...@unixarea.de -- You