[Akonadi] [Bug 422309] New: Akonadi dies after suspend to RAM
https://bugs.kde.org/show_bug.cgi?id=422309 Bug ID: 422309 Summary: Akonadi dies after suspend to RAM Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: aria...@dereferenced.org Target Milestone: --- After suspending to RAM, akonadi-server 20.04 falls over with MySQL errors and crashes on Alpine Linux edge. Monitoring the debug log yields: org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL" org.kde.pim.akonadicore: "QLocalSocket: Remote closed" "/run/user/1000/akonadi/akonadiserver-cmd.socket"org.kde.pim.akonadiserver: Database error: Cannot open database. org.kde.pim.akonadiserver: Last driver error: "QMYSQL: Unable to connect" org.kde.pim.akonadiserver: Last database error: "Lost connection to MySQL server at 'reading authorization packet', system error: 9" org.kde.pim.akonadicore: "QLocalSocket: Remote closed" "/run/user/1000/akonadi/akonadiserver-cmd.socket"org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket: Remote closed" QSocketNotifier: Invalid socket 17 and type 'Read', disabling... org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket: Remote closed" QSocketNotifier: Invalid socket 13 and type 'Read', disabling... QSocketNotifier: Invalid socket 15 and type 'Read', disabling... org.kde.pim.akonadicore: "QLocalSocket: Remote closed" "/run/user/1000/akonadi/akonadiserver-cmd.socket" org.kde.pim.akonadicore: "QLocalSocket: Remote closed" "/run/user/1000/akonadi/akonadiserver-cmd.socket" org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket: Remote closed" org.kde.pim.akonadiserver: DATABASE ERROR while PREPARING QUERY: org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket: Remote closed" KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = akonadiserver path = /usr/bin pid = 7984 KCrash: Arguments: /usr/bin/akonadiserver KCrash: Attempting to start /usr/lib/libexec/drkonqi org.kde.pim.akonadiserver: Database error: Cannot open database. QSqlQuery::exec: database not open org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL" org.kde.pim.akonadiserver: Database error: Cannot open database. org.kde.pim.akonadiserver: Last driver error: "QMYSQL: Unable to connect" org.kde.pim.akonadiserver: Last database error: "Got packets out of order" QSqlQuery::exec: database not open org.kde.pim.akonadicore: "QLocalSocket: Remote closed" "/run/user/1000/akonadi/akonadiserver-cmd.socket"QSocketNotifier: Invalid socket 35 and type 'Read', disabling... org.kde.pim.akonadiserver: Last driver error: "QMYSQL: Unable to open database 'akonadi'" org.kde.pim.akonadiserver: Last database error: "Lost connection to MySQL server during query" QSqlQuery::exec: database not open org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL" org.kde.pim.akonadiserver: DATABASE ERROR while PREPARING QUERY: org.kde.pim.akonadiserver: Error code: "2006" org.kde.pim.akonadiserver: Database error: Cannot open database. org.kde.pim.akonadiserver: DB error: "MySQL server has gone away" The MySQL server appears to be alive: localhost:~$ mysql -S ~/.local/share/akonadi/socket-localhost-default/mysql.socket Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 257 Server version: 10.4.13-MariaDB MariaDB Server Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]> show databases; ++ | Database | ++ | akonadi| | information_schema | | mysql | | performance_schema | | test | ++ 5 rows in set (0.000 sec) Restarting the service fails... petrie:~$ akonadictl restart org.kde.pim.akonadicontrol: Service ":1.146" owner changed from "" to ":1.146" org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_migration_agent' exited normally... org.kde.pim.kimap: Received BYE: "Logging out " org.kde.pim.kimap: close org.kde.pim.kimap: close org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_indexing_agent" stopped unexpectedly ( "Process crashed" ) org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_indexing_agent' crashed. No restart! org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_archivemail_agent" stopped unexpectedly ( "Process crashed" ) org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_archivemail_agent' crashed. No restart! org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_newmailnotifier_agent" stopped unexpectedly ( "Process crashed" ) org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_newmailnotifier_agent'
[Breeze] [Bug 419651] single-click activation logic breaks with selectable QAbstractListView widgets
https://bugs.kde.org/show_bug.cgi?id=419651 --- Comment #6 from Ariadne Conill --- Regarding going against the platform: I think single-click activation makes sense for navigational tasks, but it doesn't make sense for other tasks. For example, not only is this a problem in Audacious, but two different friends who use Amarok also said they find the single-click behaviour annoying there, since clicking on a song makes it play immediately when single-click mode is enabled. In an audio player, a common pattern is to select a bunch of tracks and enqueue them to a separate playlist or play queue. With the single-click behaviour, doing this is quite counter-intuitive. So, in Audacious, we attach a QProxyStyle to our subclassed audqt::TreeView widgets that suppresses the single-click activation for those widgets. I think, therefore, what makes most sense is to have a flag on the widgets that provides a hint as to what the purpose of the widget is. That seems to also be in line with how Qt provides other hints. Then you either hint the widgets where single-click activation is useful (like navigation), or you hint the widgets where single-click activation is counter-intuitive (like playlists). For something like a playlist, the single-click activation pattern doesn't make much sense, doesn't match any other popular platform (Audacious does target Mac, Windows, etc too), but as previously stated does seem useful for navigation. So, that is what I propose doing. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 419651] single-click activation logic breaks with selectable QAbstractListView widgets
https://bugs.kde.org/show_bug.cgi?id=419651 --- Comment #4 from Ariadne Conill --- The client in question behaves appropriately under all platforms other than KDE Plasma 5.18, including KDE Plasma 5.16. Don't worry, we have already made a hotfix release for users who use Audacious that got broken by Plasma 5.18. As it stands, KDE Plasma 5.18 completely broke Audacious, in a way far more severe than GNOME ever did to us. As it also stands, any other client which depends on the activate signal to behave sanely in a situation where a listview is selectable is also broken by this: you can't select items without also activating them. The documentation also does not say that hooking activate means you will have lists that cannot be selected in a usable way under KDE Plasma 5.18. Not all Qt apps are KDE apps. Please don't break our apps. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 419651] single-click activation logic breaks with selectable QAbstractListView widgets
https://bugs.kde.org/show_bug.cgi?id=419651 Ariadne Conill changed: What|Removed |Added Ever confirmed|0 |1 Resolution|INTENTIONAL |--- Status|RESOLVED|REOPENED --- Comment #2 from Ariadne Conill --- I understand that single-click activation in general is intended behaviour of the Breeze style. I do not believe that single-click activation on a selectable list is intended behaviour. That doesn't make any sense, because it makes selecting items impossible. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 419651] New: single-click activation logic breaks with selectable QAbstractListView widgets
https://bugs.kde.org/show_bug.cgi?id=419651 Bug ID: 419651 Summary: single-click activation logic breaks with selectable QAbstractListView widgets Product: Breeze Version: 5.18.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: QStyle Assignee: unassigned-b...@kde.org Reporter: aria...@dereferenced.org Target Milestone: --- In a selectable QAbstractListView widget, the first click should select the item. A second click should then activate it. Until Plasma 5.18, this was the case. In Audacious, we have worked around this bug by installing a QProxyStyle which forcefully disables the single-click activation logic on the playlist widget. https://github.com/audacious-media-player/audacious-plugins/commit/bd1b29fbfe9d85bc3a99586044ce62d95f3f55fd This regression does not exist in other QStyles, such as the Adwaita style. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Alpine edge (kernel 5.4.30) KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.