[kmail2] [Bug 482507] New: Crash when opening local outbox e-mail that failed to send
https://bugs.kde.org/show_bug.cgi?id=482507 Bug ID: 482507 Summary: Crash when opening local outbox e-mail that failed to send Classification: Applications Product: kmail2 Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: lethbridgeja...@gmail.com Target Milestone: --- Application: kmail (5.24.4 (23.08.4)) Qt Version: 5.15.12 Frameworks Version: 5.115.0 Operating System: Linux 6.6.13-gentoo x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: I made a mistake in my e-mail where the from address did not match the SMTP account that was trying to send it. Naturally the server reject sending and KMail immediatly notified me the "E-mail Sending Failed". I did the typical thing one would when one sees an email hasn't been send and tried to open it from the local outbox with a double click. This caused a crash to desktop The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 0x7f264fed9232 in ??? () at /usr/lib64/libQt5Core.so.5 #5 0x7f2650095f9c in QCoreApplicationPrivate::lockThreadPostEventList(QObject*) () at /usr/lib64/libQt5Core.so.5 #6 0x7f2650096729 in QCoreApplication::postEvent(QObject*, QEvent*, int) () at /usr/lib64/libQt5Core.so.5 #7 0x7f26500c6f94 in ??? () at /usr/lib64/libQt5Core.so.5 #8 0x7f26592eef6e in ??? () at /usr/lib64/libkmailprivate.so.5 #9 0x7f26500c6f94 in ??? () at /usr/lib64/libQt5Core.so.5 #10 0x7f26511a03f3 in KJob::result(KJob*, KJob::QPrivateSignal) () at /usr/lib64/libKF5CoreAddons.so.5 #11 0x7f26511a18bb in ??? () at /usr/lib64/libKF5CoreAddons.so.5 #12 0x7f26500befb5 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #13 0x7f2650b6320e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #14 0x7f2650093f28 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #15 0x7f26500974a3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #16 0x7f26500e5fc3 in ??? () at /usr/lib64/libQt5Core.so.5 #17 0x7f264bd10e22 in ??? () at /usr/lib64/libglib-2.0.so.0 #18 0x7f264bd14017 in ??? () at /usr/lib64/libglib-2.0.so.0 #19 0x7f264bd1463c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #20 0x7f26500e5ac6 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #21 0x7f265009294b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #22 0x7f265009accd in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #23 0x55809b082b54 in ??? () #24 0x7f264f845f0a in ??? () at /usr/lib64/libc.so.6 #25 0x7f264f845fc5 in __libc_start_main () at /usr/lib64/libc.so.6 #26 0x55809b083111 in ??? () [Inferior 1 (process 2403) detached] The reporter indicates this bug may be a duplicate of or related to bug 471223. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 482442] After update to plasma 6, akonadi can't start because mysql configuration is missing/faulty
https://bugs.kde.org/show_bug.cgi?id=482442 Carlos De Maine changed: What|Removed |Added CC||carlosdema...@gmail.com --- Comment #5 from Carlos De Maine --- have fixed a packaging error which should mean that all the apparmor files are installed. building now but plasma 6.0.1 just started as well so could take a while - https://invent.kde.org/neon/kde/akonadi/-/commit/2ebb2156dda19bed3d0795d95fa24a78e32193b6 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 482442] After update to plasma 6, akonadi can't start because mysql configuration is missing/faulty
https://bugs.kde.org/show_bug.cgi?id=482442 --- Comment #4 from Joshua J. Kugler --- In /etc/apparmor.d/, I ran: sudo aa-complain ./mariadbd_akonadi sudo aa-complain ./mysqld_akonadi Akonadi is up and running now. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 482442] After update to plasma 6, akonadi can't start because mysql configuration is missing/faulty
https://bugs.kde.org/show_bug.cgi?id=482442 --- Comment #3 from Joshua J. Kugler --- In trying to invoke mysqld directly: $ /usr/sbin/mysqld --defaults-file=/home/jkugler/.local/share/akonadi/mysql.conf --datadir=/home/jkugler/.local/share/akonadi/db_data/ --socket=/run/user/1000/akonadi/mysql.socket --pid-file=/run/user/1000/akonadi/mysql.pid MariaDB starts and runs without issue. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 482442] After update to plasma 6, akonadi can't start because mysql configuration is missing/faulty
https://bugs.kde.org/show_bug.cgi?id=482442 --- Comment #2 from Joshua J. Kugler --- Seems this bug had a similar error (Permission denied): https://bugs.kde.org/show_bug.cgi?id=427618 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 482442] After update to plasma 6, akonadi can't start because mysql configuration is missing/faulty
https://bugs.kde.org/show_bug.cgi?id=482442
Joshua J. Kugler changed:
What|Removed |Added
CC||jos...@joshuakugler.com
--- Comment #1 from Joshua J. Kugler ---
Similar problems. Fresh install. Installed kmail, had to manually install
akonadi-backend-mysql. Akonadi still won't start.
$ akonadictl start
org.kde.pim.akonadictl: Starting Akonadi Server...
org.kde.pim.akonadictl:done.
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: Failed to detect mysqld version!
org.kde.pim.akonadiserver: Could not start database server!
org.kde.pim.akonadiserver: executable: "/usr/sbin/mysqld"
org.kde.pim.akonadiserver: arguments:
QList("--defaults-file=/home/jkugler/.local/share/akonadi/mysql.conf",
"--datadir=/home/jkugler/.local/share/akonadi/db_data/",
"--socket=/run/user/1000/akonadi/mysql.socket",
"--pid-file=/run/user/1000/akonadi/mysql.pid")
org.kde.pim.akonadiserver: process error: "execve: Permission denied"
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited
normally...
Tried sudo aa-complain /usr/bin/akonadiserver and got the error "ERROR: Include
file /etc/apparmor.d/local/mariadbd_akonadi not found"
Currently stuck. :)
--
You are receiving this mail because:
You are the assignee for the bug.
[akregator] [Bug 475128] akregator / kmail : can't restore / reduce to tray
https://bugs.kde.org/show_bug.cgi?id=475128 Arek Guzinski changed: What|Removed |Added CC||ker...@ag.de1.cc --- Comment #1 from Arek Guzinski --- Same thing here on current neon -- but only with akregator. Works fine in kmail. Maybe it's fixed there and that fix can be applied to akregator? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 374426] HTML email is unreadable with dark theme
https://bugs.kde.org/show_bug.cgi?id=374426 Sebastian Turzański changed: What|Removed |Added CC||dpba...@wp.pl --- Comment #4 from Sebastian Turzański --- I confirm in Plasma 6 24.02 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 482447] KMail crash at startup
https://bugs.kde.org/show_bug.cgi?id=482447 Anton K changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Anton K --- It seems that the problem is somehow related to the amd gpu, I tried to update the driver, and now it works. I don't have a file right now: /opt/amdgpu/lib/x86_64-linux-gnu/libva.so.2 maybe I have an amd gpu installed somehow wrong, I haven't figured it out yet, but everything seems to work. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 482447] KMail crash at startup
https://bugs.kde.org/show_bug.cgi?id=482447 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 482447] New: KMail crash at startup
https://bugs.kde.org/show_bug.cgi?id=482447 Bug ID: 482447 Summary: KMail crash at startup Classification: Applications Product: kmail2 Version: 6.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: misc Assignee: kdepim-bugs@kde.org Reporter: kvanton@yandex.ru Target Milestone: --- SUMMARY Crash of the program during startup. But I get notifications about new mail. I don't remember if this happened immediately after switching to plasma 6, but it looks like it happened after some kind of update, because it used to work. STEPS TO REPRODUCE 1. start kmail OBSERVED RESULT start the program EXPECTED RESULT crash the program SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.5-060505-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION (gdb) run Starting program: /usr/bin/kmail [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe13ff640 (LWP 10852)] [New Thread 0x7fffdbfff640 (LWP 10853)] [New Thread 0x7fffdb7fe640 (LWP 10854)] [New Thread 0x7fffd97ff640 (LWP 10855)] [New Thread 0x7fffd8ffe640 (LWP 10856)] [New Thread 0x7fffc67ff640 (LWP 10857)] [New Thread 0x7fffc5ffe640 (LWP 10858)] [New Thread 0x7fffc57fd640 (LWP 10859)] [New Thread 0x7fffc4ffc640 (LWP 10860)] [New Thread 0x7fffa640 (LWP 10861)] [New Thread 0x7fffaf7fe640 (LWP 10862)] [Thread 0x7fffaf7fe640 (LWP 10862) exited] [Thread 0x7fffa640 (LWP 10861) exited] [Thread 0x7fffc4ffc640 (LWP 10860) exited] [Thread 0x7fffc57fd640 (LWP 10859) exited] [New Thread 0x7fffc57fd640 (LWP 10863)] [New Thread 0x7fffc4ffc640 (LWP 10864)] [New Thread 0x7fffa640 (LWP 10865)] [New Thread 0x7fffaf7fe640 (LWP 10866)] [New Thread 0x7fffaeffd640 (LWP 10867)] [New Thread 0x7fffae7fc640 (LWP 10868)] [New Thread 0x7fffadffb640 (LWP 10869)] [New Thread 0x7fffad7fa640 (LWP 10870)] [Thread 0x7fffad7fa640 (LWP 10870) exited] [Thread 0x7fffadffb640 (LWP 10869) exited] [Thread 0x7fffae7fc640 (LWP 10868) exited] [Thread 0x7fffaeffd640 (LWP 10867) exited] qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "stateChanged" : Type not registered with QtDBus in parameter list: QNetworkManagerInterface::NMState qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "connectivityChanged" : Type not registered with QtDBus in parameter list: QNetworkManagerInterface::NMConnectivityState qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "deviceTypeChanged" : Type not registered with QtDBus in parameter list: QNetworkManagerInterface::NMDeviceType qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "meteredChanged" : Type not registered with QtDBus in parameter list: QNetworkManagerInterface::NMMetered [New Thread 0x7fffaeffd640 (LWP 10871)] [New Thread 0x7fffae7fc640 (LWP 10872)] [Detaching after fork from child process 10875] [Detaching after fork from child process 10877] [New Thread 0x7fffadffb640 (LWP 10879)] [New Thread 0x7fffad7fa640 (LWP 10881)] [Detaching after fork from child process 10882] [Detaching after fork from child process 10883] [Detaching after fork from child process 10884] [New Thread 0x7fff97bff640 (LWP 10887)] [New Thread 0x7fff973fe640 (LWP 10888)] [New Thread 0x7fff96bfd640 (LWP 10889)] [New Thread 0x7fff963fc640 (LWP 10890)] [New Thread 0x7fff95bfb640 (LWP 10891)] [New Thread 0x7fff953fa640 (LWP 10892)] [New Thread 0x7fff94bf9640 (LWP 10893)] [New Thread 0x7fff77fff640 (LWP 10895)] [New Thread 0x7fff777fe640 (LWP 10894)] [New Thread 0x7fff6640 (LWP 10896)] [New Thread 0x7fff76ffd640 (LWP 10897)] [New Thread 0x7fff767fc640 (LWP 10898)] [New Thread 0x7fff75ffb640 (LWP 10899)] [New Thread 0x7fff757fa640 (LWP 10900)] warning: Missing auto-load script at offset 0 in section .debug_gdb_scripts of file /lib/x86_64-linux-gnu/libadblockplugin.so.6. Use `info auto-load python-scripts [REGEXP]' to list them. [New Thread 0x7fff66dff640 (LWP 10908)] [Thread 0x7fff66dff640 (LWP 10908) exited] [New Thread 0x7fff66dff640 (LWP 10909)] [New Thread 0x7fff74ff9640 (LWP 10910)] [Thread 0x7fff74ff9640 (LWP 10910) exited] [Thread 0x7fff66dff640 (LWP 10909) exited] [New Thread 0x7fff66dff640 (LWP 10911)] [New Thread 0x7fff74ff9640 (LWP 10912)] [Thread 0x7fff74ff9640 (LWP 10912) exited] [Thread 0x7fff66dff640 (LWP 10911) exited] [New Thread 0x7fff66dff640 (LWP 10913)] [New Thread 0x7fff74ff9640 (LWP 10914)] [Thread 0x7fff74ff9640 (LWP 10914) exited] [Thread 0x7fff66dff640 (LWP 10913) exited] [New Thread 0x7fff66dff640 (LWP 10915)] [New Thread 0x7fff74ff9640 (LWP 10916)] kf.config.core: Watching absolute paths is not supported "/usr/share/color-schemes/BreezeDark.colors" [New Thread 0x7fff6f7fe640 (LWP 10925)]
[kmail2] [Bug 482445] kmail font rendering broken on plasma 6 and HiDPI (scaled) display
https://bugs.kde.org/show_bug.cgi?id=482445 --- Comment #2 from Adam Pigg --- Id like to add to this. I run my desktop at 125%, in wayland, and attached a screenshot, scaled 300% in gimp. The font rendering issue only seems to affect the kmail message pane, other text in plasma6 is fine. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 482445] kmail font rendering broken on plasma 6 and HiDPI (scaled) display
https://bugs.kde.org/show_bug.cgi?id=482445 Adam Pigg changed: What|Removed |Added CC||a...@piggz.co.uk --- Comment #1 from Adam Pigg --- Created attachment 166416 --> https://bugs.kde.org/attachment.cgi?id=166416=edit Kmail font rendering 125% scale, wayland, blown 300% no filter -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 482445] kmail font rendering broken on plasma 6 and HiDPI (scaled) display
https://bugs.kde.org/show_bug.cgi?id=482445 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 482445] New: kmail font rendering broken on plasma 6 and HiDPI (scaled) display
https://bugs.kde.org/show_bug.cgi?id=482445 Bug ID: 482445 Summary: kmail font rendering broken on plasma 6 and HiDPI (scaled) display Classification: Applications Product: kmail2 Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: k...@kn0x.org Target Milestone: --- Created attachment 166415 --> https://bugs.kde.org/attachment.cgi?id=166415=edit screenshot of a test email in kmail SUMMARY On Plasma 6, font rendering is broken when reading emails using kmail on a scaled (hidpi) display. Please see attached screenshot for a beautiful preview. All other components of kmail scale and render fine. STEPS TO REPRODUCE 1. Use wayland (not tested on X11) 2. Configure display scaling (only tested on 125% and 150%) 3. Open an email in kmail. Both HTML and text format are affected OBSERVED RESULT Blurred, unhinted fonts EXPECTED RESULT Clean, well rendered and hinted fonts. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 22.04 (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Graphics platform: Wayland kmail version: 6.0.0 (24.02.0) -- You are receiving this mail because: You are the assignee for the bug.
