[korgac] [Bug 273450] Reminders should be preselected when they pop up
https://bugs.kde.org/show_bug.cgi?id=273450 Filipus Klutiero changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED CC||chea...@gmail.com --- Comment #1 from Filipus Klutiero --- I am almost sure I recently observed the same issue. However, I just had a reminder popup, and it was already selected, so unless this is an intermittent bug, it seems this issue is solved. I do not remember having this frustration recently - that is probably an indication that the issue was solved when I upgraded from Debian 9 to Kubuntu 19.04, which uses KOrganizer 5.10.3. I am assuming this was solved and marking this as resolved. If you re-open this ticket, please indicate an affected version. -- You are receiving this mail because: You are the assignee for the bug.
[korgac] [Bug 379026] reminder shows dialog for past events
https://bugs.kde.org/show_bug.cgi?id=379026 Filipus Klutiero changed: What|Removed |Added CC||chea...@gmail.com --- Comment #1 from Filipus Klutiero --- Thanks for reporting Martin, Has your reminders popped up "yesterday", so that you got duplicate reminders? Or has they failed to popup yesterday? -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 360934] Korganiser does not show reminders
https://bugs.kde.org/show_bug.cgi?id=360934 Filipus Klutiero changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||chea...@gmail.com --- Comment #2 from Filipus Klutiero --- I indeed cannot see a difference with ticket #344679. Luis, if this still happens, please report on https://bugs.kde.org/show_bug.cgi?id=344679 *** This bug has been marked as a duplicate of bug 344679 *** -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 344679] All event reminders fail to trigger alerts/popups/notifications
https://bugs.kde.org/show_bug.cgi?id=344679 Filipus Klutiero changed: What|Removed |Added CC||luis.de.so...@protonmail.ch --- Comment #12 from Filipus Klutiero --- *** Bug 360934 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 409875] KMail crashes on mail with Itinerary content
https://bugs.kde.org/show_bug.cgi?id=409875 --- Comment #1 from Nicolas Fella --- Update: It happens on both Wayland and X11, but not on KMail 5.11.2, only master -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 409875] New: KMail crashes on mail with Itinerary content
https://bugs.kde.org/show_bug.cgi?id=409875 Bug ID: 409875 Summary: KMail crashes on mail with Itinerary content Product: kmail2 Version: Git (master) Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: nicolas.fe...@gmx.de Target Milestone: --- Created attachment 121564 --> https://bugs.kde.org/attachment.cgi?id=121564=edit Backtrace SUMMARY STEPS TO REPRODUCE 1. Open email with extracted booking information 2. Move cursor above extracted information OBSERVED RESULT KMail crashes SOFTWARE/OS VERSIONS KDE Plasma Version: master KDE Frameworks Version: master Qt Version: 5.13.0 ADDITIONAL INFORMATION Wayland session Happens for all DB emails I tested. Didn't happen with Ryanair -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 398847] Kaddressbook not parsing gmail contacts
https://bugs.kde.org/show_bug.cgi?id=398847 Colin J Thomson changed: What|Removed |Added CC|colin.thom...@g6avk.co.uk | -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 81778] KMail should not always reply to mailing lists by default
https://bugs.kde.org/show_bug.cgi?id=81778 gjditchfi...@acm.org changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #17 from gjditchfi...@acm.org --- Correction: the message in attachment "List-Post and Reply-To" has a "Mail-followup-to" header, and KMail 5.7.3 sets the "To" address to that, as it should. As far as I can tell, KMail no longer has this bug. Does anyone know of a case where replies to lists are handled incorrectly? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409224] kmail with >=mariadb-10.4.6: not able to refresh email list: Unable to append status flags
https://bugs.kde.org/show_bug.cgi?id=409224 LonelyWoolf changed: What|Removed |Added CC||lonelywo...@live.ru --- Comment #9 from LonelyWoolf --- Same problem. I think, that akonadi should check versions of mysql and run mysql_upgrade. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409853] akonadiserver runs dbinitializer even when db is already filled with data and dies
https://bugs.kde.org/show_bug.cgi?id=409853 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at --- Comment #3 from Wolfgang Bauer --- Looks similar to bug#409753. Seems to be caused by the PostgreSQL fix. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409753] Duplicate column name 'version' QMYSQL
https://bugs.kde.org/show_bug.cgi?id=409753 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org --- Comment #1 from Antonio Rojas --- According to downstream reports, this is a regression from 74aed9542ba1ff1e6e93a550c42869647c4eba8e -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409234] akonadi with qt5 5.13 is unable to initialize database when using the PostgreSQL backend
https://bugs.kde.org/show_bug.cgi?id=409234 --- Comment #4 from Antonio Rojas --- This causes a regression in mysql for some users: https://bugs.kde.org/show_bug.cgi?id=409753 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409853] akonadiserver runs dbinitializer even when db is already filled with data and dies
https://bugs.kde.org/show_bug.cgi?id=409853 --- Comment #2 from Christophe Giboudeaux --- critical is used for very specific bugs. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 409248] Kmail crashes once restarted.
https://bugs.kde.org/show_bug.cgi?id=409248 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 401739 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 401739] Kmail crashes while open on fresh start system, attempting to reopen it results in the completely empty application window, no mailbox or mail message available
https://bugs.kde.org/show_bug.cgi?id=401739 Christoph Feck changed: What|Removed |Added CC||staka...@eclipso.eu --- Comment #12 from Christoph Feck --- *** Bug 409248 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 409344] KMail crashes when closing a message opened twice or more
https://bugs.kde.org/show_bug.cgi?id=409344 Christoph Feck changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO --- Comment #1 from Christoph Feck --- Please add the backtrace for the crash. For more information, please read https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 409317] Kmail crashes when clicking on the account (left bar) after inital creation of the account
https://bugs.kde.org/show_bug.cgi?id=409317 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Christoph Feck --- Crash is in the nouveau OpenGL driver. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 409289] The akonadi information management service is not working
https://bugs.kde.org/show_bug.cgi?id=409289 Christoph Feck changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Severity|crash |major Status|REPORTED|NEEDSINFO --- Comment #1 from Christoph Feck --- Please provide the akonadi server log. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409853] akonadiserver runs dbinitializer even when db is already filled with data and dies
https://bugs.kde.org/show_bug.cgi?id=409853 --- Comment #1 from Mathias Homann --- this completely breaks all pim functionality for existing setups - I don't think this should be "normal" -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409853] akonadiserver runs dbinitializer even when db is already filled with data and dies
https://bugs.kde.org/show_bug.cgi?id=409853 Christophe Giboudeaux changed: What|Removed |Added Severity|critical|normal -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409341] Unable to start stable version of akonadi server or file bug report (Fedora 30)
https://bugs.kde.org/show_bug.cgi?id=409341 --- Comment #5 from Christophe Giboudeaux --- Is there a message from apparmor in the dmesg output? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409341] Unable to start stable version of akonadi server or file bug report (Fedora 30)
https://bugs.kde.org/show_bug.cgi?id=409341 Christoph Feck changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO --- Comment #4 from Christoph Feck --- The crash report lacks debug symbol information. Please ask for help in a forum of your distribution how to provide these. See also https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409853] New: akonadiserver runs dbinitializer even when db is already filled with data and dies
https://bugs.kde.org/show_bug.cgi?id=409853 Bug ID: 409853 Summary: akonadiserver runs dbinitializer even when db is already filled with data and dies Product: Akonadi Version: 5.11.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- on my desktop workstation, akonadi is configured to use a central mysql database on a database server (~ is on NFS, 'nuff said). Since 5.11.3 akonadi dies after the first setup, due to dbinitializer in this configuration not realizng that the DB is already initialized. STEPS TO REPRODUCE 1. do a fresh akonadi configuration using a mysql database on a different machine via tcp/ip, set up some akonadi agents as usual - imap, webdav calendar, google, etc 2. wait for akonadi to fill with data 3. log out (and maybe restart your desktop workstation to make sure all akonadi processes are stopped) 4. log back in OBSERVED RESULT akonadiserver is not running EXPECTED RESULT akonadiserver should be running SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION when running "akonadiserver --verbose" on a commandline: lemmy@kumiko:~> akonadiserver --verbose org.kde.pim.akonadiserver: Akonadi control process not found - aborting. org.kde.pim.akonadiserver: If you started akonadiserver manually, try 'akonadictl start' instead. org.kde.pim.akonadiserver: Starting up the Akonadi Server... org.kde.pim.akonadiserver: Found mysql_install_db: "/usr/bin/mysql_install_db" org.kde.pim.akonadiserver: Found mysqlcheck: "/usr/bin/mysqlcheck" org.kde.pim.akonadiserver: Using mysqld: "/usr/sbin/mysqld" org.kde.pim.akonadiserver: Database "lemmy_akonadi" opened using driver "QMYSQL" org.kde.pim.akonadiserver: Running DB initializer org.kde.pim.akonadiserver: checking table "SchemaVersionTable" org.kde.pim.akonadiserver: "ALTER TABLE SchemaVersionTable ADD COLUMN version INTEGER NOT NULL DEFAULT 0" org.kde.pim.akonadiserver: "\nSql error: Duplicate column name 'version' QMYSQL: Unable to execute query\nQuery: ALTER TABLE SchemaVersionTable ADD COLUMN version INTEGER NOT NULL DEFAULT 0" org.kde.pim.akonadiserver: Unable to initialize database. org.kde.pim.akonadiserver: terminating connection threads org.kde.pim.akonadiserver: terminating service threads org.kde.pim.akonadiserver: Shutting down "NotificationManager" ... org.kde.pim.akonadiserver: stopping db process lemmy@kumiko:~> akonadiserver --version akonadiserver 5.11.3 lemmy@kumiko:~> Observe the dbinitializer trying to add a column to a table where that column already exists. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 409851] New: "Import key" link in mails with attached PGP key doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=409851 Bug ID: 409851 Summary: "Import key" link in mails with attached PGP key doesn't do anything Product: kmail2 Version: 5.11.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: akreuzk...@web.de Target Milestone: --- Importing an attached PGP key from a received mail is not possible currently. The key is displayed correctly as a pgp key and a link to import the key is offered. Clicking on that link doesn't do anything, though. I couldn't find any way around it, like a way to save the key to the harddisk. In encrypted mails, not even the mail source code helps. I don't have debug symbols available, unfortunately, so I can't verify, if ApplicationPgpKeyUrlHandler::handleClick is being called or not... STEPS TO REPRODUCE 1. Receive an email with an attached PGP key, you don't have yet. 2. Open the mail and scroll down to the "OpenPGP Key" section. 3. Click on "Import key" and wonder why nothing happens at all. OBSERVED RESULT No visible reaction whatsoever, the key does not appear in kleopatra's key list afterwards EXPECTED RESULT Kleopatra opens, importing the key. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 -- You are receiving this mail because: You are the assignee for the bug.
