[korganizer] [Bug 483823] New event button does not use currently selected date as default
https://bugs.kde.org/show_bug.cgi?id=483823 Nick changed: What|Removed |Added CC||mobile.har...@outlook.com --- Comment #1 from Nick --- Just tried to duplicate this on Neon but korganiser crashes when I execute step 2! Bug report raised. If I can get past step 2 I'll report back. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 483737] akregator icon, in systray does not follow dark breeze theme.
https://bugs.kde.org/show_bug.cgi?id=483737 Nick changed: What|Removed |Added CC||mobile.har...@outlook.com --- Comment #2 from Nick --- Created attachment 167641 --> https://bugs.kde.org/attachment.cgi?id=167641=edit Confirmed Confirmed on Neon 6.0.2 / Wayland / Akregator .deb 24.02.1. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 483364] akonadiconsole crashes after trying to restart server
https://bugs.kde.org/show_bug.cgi?id=483364 --- Comment #3 from Nick --- OK - understood. It would be helpful if someone can duplicate this to allow the devs to reliably reproduce the issue at will. I'll leave this here for now in case anyone with more expertise than me can take a look. Thanks. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 483365] akonadiconsole wants QSQLITE3, while only QSQLITE is available
https://bugs.kde.org/show_bug.cgi?id=483365 Nick changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||mobile.har...@outlook.com Status|REPORTED|NEEDSINFO --- Comment #2 from Nick --- Hi. Thanks for raising this. Can you please provide a full list of commands you are issuing to cause this, plus any associated apps which need to be installed? I will then try to duplicate this. Thanks, Nick -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 483364] akonadiconsole crashes after trying to restart server
https://bugs.kde.org/show_bug.cgi?id=483364 Nick changed: What|Removed |Added CC||mobile.har...@outlook.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Nick --- Hi - thanks for raising this. Can you please provide a full list of commands you issued to cause this, plus any apps installed relating to this? I will then try to duplicate it. Thanks, Nick. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 482398] New: Akonadi EWS doesn't seem to pull the tags from EWS
https://bugs.kde.org/show_bug.cgi?id=482398 Bug ID: 482398 Summary: Akonadi EWS doesn't seem to pull the tags from EWS Classification: Frameworks and Libraries Product: Akonadi Version: 6.0.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: EWS Resource Assignee: kdepim-bugs@kde.org Reporter: ygxnpj...@mozmail.com CC: c...@carlschwan.eu, kri...@op.pl Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Create a Category in MS Outlook 365 2. Assign a category to the email 3. Redownload the email/Refresh the directory OBSERVED RESULT The tag is not assigned to the email. However, when I assign a tag via KMail it is pushed to the server (and is visible in MS Outlook) EXPECTED RESULT I can see that the email has a tag assigned to it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Let me know how I can help debug it :) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 475412] akonadi_mail_dispatcher_agent closed unexcpectedly
https://bugs.kde.org/show_bug.cgi?id=475412 --- Comment #1 from Nick --- Any news ? Tx -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 475412] New: akonadi_mail_dispatcher_agent closed unexcpectedly
https://bugs.kde.org/show_bug.cgi?id=475412 Bug ID: 475412 Summary: akonadi_mail_dispatcher_agent closed unexcpectedly Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Mail Dispatcher Agent Assignee: kdepim-bugs@kde.org Reporter: ndor...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: akonadi_maildispatcher_agent (5.22.3 (22.12.3)) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 5.14.21-150500.53-default x86_64 Windowing System: X11 Distribution: "openSUSE Leap 15.5" DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: post upgrade to opensuse leap 155; many of KDE settings/functions fail 1. the autostart settings + app launcher settings fail [ ~/.config/autostart ] 2. send and email link ... it complains ... Thanks The crash can be reproduced every time. -- Backtrace: Application: akonadi_maildispatcher_agent (akonadi_maildispatcher_agent), signal: Segmentation fault [KCrash Handler] #4 0x7fca4631a4d0 in MailTransport::TransportAttribute::transportId() const () at /usr/lib64/libKF5MailTransportAkonadi.so.5 #5 0x55647dac15af in () #6 0x7fca4535b4db in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #7 0x7fca457bd53c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #8 0x7fca457c42ff in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #9 0x7fca45327043 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #10 0x7fca45329a61 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #11 0x7fca4538a2e3 in () at /usr/lib64/libQt5Core.so.5 #12 0x7fca41e6f82b in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #13 0x7fca41e6fbd0 in () at /usr/lib64/libglib-2.0.so.0 #14 0x7fca41e6fc5c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #15 0x7fca4538998c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #16 0x7fca453258aa in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #17 0x7fca4532f0e7 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #18 0x7fca4627e0cd in Akonadi::AgentBase::init(Akonadi::AgentBase&) () at /usr/lib64/libKF5AkonadiAgentBase.so.5 #19 0x55647dab21b5 in () #20 0x7fca447dc24d in __libc_start_main () at /lib64/libc.so.6 #21 0x55647daad9da in () [Inferior 1 (process 14984) detached] Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 343186] Timeout trying to get lock on start of kmail
https://bugs.kde.org/show_bug.cgi?id=343186 --- Comment #11 from Nick --- Forget my previous comment, the text below is relevant to the error: >Nov 27 10:14:39 pnp akonadiserver[49834]: org.kde.pim.akonadiserver.search: >Search "kmail2-1974024246-SearchSession" done (without remote search) >Nov 27 10:14:40 pnp akonadiserver[49834]: org.kde.pim.akonadiserver: Error >while handling command FetchCollections on connection >akonadi_maildir_resource_1 (0x55bdd1c68fc0) >Nov 27 10:14:44 pnp kmail[49783]: org.kde.pim.akonadicore: Timeout trying to >get lock. Check who has acquired the name "org.kde.pim.SpecialCollections" on >DBus, using qdbus or qdbusviewer. >Nov 27 10:14:44 pnp kmail[49783]: org.kde.pim.akonadicore: Failed to get lock: >"Timeout trying to get lock." >Nov 27 10:14:44 pnp kmail[49783]: org.kde.pim.mailcommon: "The Email program >encountered a fatal error and will terminate now.\nThe error was:\nTimeout >trying to get lock." -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 343186] Timeout trying to get lock on start of kmail
https://bugs.kde.org/show_bug.cgi?id=343186 --- Comment #10 from Nick --- This was in the syslog about the time the error occured, may not be relevant but thought I'd document it. >Nov 27 10:22:55 pnp akonadiserver[49834]: org.kde.pim.akonadiserver.search: >Executing search "searchUpdate-1669544575" >Nov 27 10:22:55 pnp akonadiserver[49834]: org.kde.pim.akonadiserver: DATABASE >ERROR: >Nov 27 10:22:55 pnp akonadiserver[49834]: org.kde.pim.akonadiserver: Error >code: "2014" >Nov 27 10:22:55 pnp akonadiserver[49834]: org.kde.pim.akonadiserver: DB >error: "Commands out of sync; you can't run this command now" >Nov 27 10:22:55 pnp akonadiserver[49834]: org.kde.pim.akonadiserver: Error >text: "Commands out of sync; you can't run this command now QMYSQL3: Unable to >store statement results" -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 343186] Timeout trying to get lock on start of kmail
https://bugs.kde.org/show_bug.cgi?id=343186 --- Comment #9 from Nick --- I'm running 5.21.2 on KDE Neon (ubuntu 22.04). Hopefully it's just a very obscure minor issue. Just odd I've never seen it before. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 343186] Timeout trying to get lock on start of kmail
https://bugs.kde.org/show_bug.cgi?id=343186 Nick changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED CC||nick.craig@gmail.com --- Comment #8 from Nick --- I just had this error occur after I started kmail which then exited after acknowledging the message. Restarted kmail and seems to be working ok. Strange, I've never seem that error before and I use kmail on a daily basis. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 382216] Lots of old emails [ days, weeks ] are received over and over again even if they are deleted/moved to trash
https://bugs.kde.org/show_bug.cgi?id=382216 --- Comment #5 from Nick --- (In reply to Bug Janitor Service from comment #4) > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least > 15 days. Please provide the requested information as soon as > possible and set the bug status as REPORTED. Due to regular bug > tracker maintenance, if the bug is still in NEEDSINFO status with > no change in 30 days the bug will be closed as RESOLVED > WORKSFORME > due to lack of needed information. > > For more information about our bug triaging procedures please read the > wiki located here: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > If you have already provided the requested information, please > mark the bug as REPORTED so that the KDE team knows that the bug is > ready to be confirmed. > > Thank you for helping us make KDE software even better for everyone! Hello, It is a while since these events happened . Since then my machine as well as KDE/Kmail2 were upgraded . Now I use opensuse leap 15.4 and kmail /kontact is at level 5.19.3(21.12.3 ) With very few exceptions [ response time ] I haven't noticed the symptoms reported in 2017 . So I cannot recreate the 2017 failures . I still have problems with akonadictl fsck message regarding records with no RID. It is possible to have akonadictl fsck repair option that will [re]move the affected emails to another directory ... i.e. TB_handled_by_the_user ? The we can decide about them . If this comment helps, as far as I am concerned this bug can be closed . Thank you for your support . Best regards, Nick -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372976] dialog's editorial confusion on password storage
https://bugs.kde.org/show_bug.cgi?id=372976 --- Comment #5 from Nick Levinson --- I don't have KMail on a laptop anymore and I can't test it, so I wouldn't say WORKSFORME. To say that a program is not available and that the user should use it is essentially contradictory and if KMail still says that then someone should correct it. Maybe someone else can check what KMail says now, or at least apply a LATER or similar label. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 449062] google groupware - cannot add calendar
https://bugs.kde.org/show_bug.cgi?id=449062 Nick changed: What|Removed |Added CC||nikkmo...@gmail.com --- Comment #2 from Nick --- I have had the same issue. I did have the calendar connected and all of a sudden it deleted all of the events from my calendar and from then has not been able to display the calendars. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 21.10 (available in About System) Kernel Version 5.13.0-27 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 KOrganizer Version: 5.19.1 Platform: Kubuntu Backports PPA -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 446751] Akonadi POP3 Resource failed to connect to pop3 gmail
https://bugs.kde.org/show_bug.cgi?id=446751 --- Comment #19 from Nick --- KDE Neon updated with latest patch, receiving pop3 email without problem. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 446751] Akonadi POP3 Resource failed to connect to pop3 gmail
https://bugs.kde.org/show_bug.cgi?id=446751 --- Comment #11 from Nick --- This issue is also being duplicated here: https://bugs.kde.org/show_bug.cgi?id=446751 https://bugs.kde.org/show_bug.cgi?id=446972 -- You are receiving this mail because: You are the assignee for the bug.
[kmailtransport] [Bug 446972] Kmail stopped receiving email (in multiple pop3 accounts) after kde gear update 21.12
https://bugs.kde.org/show_bug.cgi?id=446972 Nick changed: What|Removed |Added CC||nick.craig@gmail.com --- Comment #1 from Nick --- Same problem duplicated: https://bugs.kde.org/show_bug.cgi?id=446751 https://bugs.kde.org/show_bug.cgi?id=446972 I have the same problem. Cannot receive pop3 accounts since 21.12 update. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 446949] kmail cannot access gmail account
https://bugs.kde.org/show_bug.cgi?id=446949 --- Comment #3 from Nick --- Another duplicate https://bugs.kde.org/show_bug.cgi?id=446972 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 446949] kmail cannot access gmail account
https://bugs.kde.org/show_bug.cgi?id=446949 --- Comment #2 from Nick --- This looks like a duplicate https://bugs.kde.org/show_bug.cgi?id=446751 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 446751] Akonadi POP3 Resource failed to connect to pop3 gmail
https://bugs.kde.org/show_bug.cgi?id=446751 Nick changed: What|Removed |Added CC||nick.craig@gmail.com --- Comment #10 from Nick --- I'm also seeing this same problem since upgrade to kmail Version 5.19.0 (21.12.0) KDE Neon 5.23.4: Unable to receive pop3 email org.kde.pim.pop3resource: == ERROR DURING POP3 SYNC == org.kde.pim.pop3resource: "Unable to login to the server \"pop.gmail.com\".\nCould not login to pop.gmail.com.\n\nThe server terminated the connection immediately." org.kde.pim.pop3resource: UID list from server is not valid. "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." org.kde.pim.pop3resource: == ERROR DURING POP3 SYNC == org.kde.pim.pop3resource: "Unable to login to the server \"pop.gmail.com\".\nCould not login to pop.gmail.com.\n\nThe server terminated the connection immediately." org.kde.pim.pop3resource: UID list from server is not valid. "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 446949] kmail cannot access gmail account
https://bugs.kde.org/show_bug.cgi?id=446949 --- Comment #1 from Nick --- Also the password isn't getting saved in the kdewallet. I can open the kdewallet but when I look at the passwords in mailtransport the password hasn't been saved. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 446949] New: kmail cannot access gmail account
https://bugs.kde.org/show_bug.cgi?id=446949 Bug ID: 446949 Summary: kmail cannot access gmail account Product: kmail2 Version: 5.19.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: nick.craig@gmail.com Target Milestone: --- SUMMARY *** I've been running kmail and accessing my gmail account for years, however after a recent update a few days ago I get the following message "Unable to login to the server "pop.gmail.com". Could not login to pop.gmail.com. The server terminated the connection immediately. " I've tried generating a new app password, multiple times, checked all the server info, still can't receive emails. However here's the odd thing. I can send emails via the gmail account. This all started happening after the recent KDE neon upgrade to 5.23.4. My gmail password is stored in my KDEwallet which I can login to and see the passwords. Re-entering the password manually still doesn't work. *** STEPS TO REPRODUCE Use an existing gmail account that's already setup in kmail2 and try to receive email. Gmail server disconnects immediately. OBSERVED RESULT Cannot receive gmail emails but can send via gmail smtp. EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-41-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-2670QM CPU @ 2.20GHz Memory: 15.6 GiB of RAM Graphics Processor: GeForce GTX 570M/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 403067] Akonadi crash in akonadi_maildir_resource
https://bugs.kde.org/show_bug.cgi?id=403067 Nick changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #6 from Nick --- I can confirm that I've not experienced this bug in the following version of KDE Neon that I'm currently using. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon Ubuntu 18.04/5.19 (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 412606] kmail segmentation fault after having clicked on a mailto:sa...@company.com link in firefox or chrome browser as long as kmail is not already running.
https://bugs.kde.org/show_bug.cgi?id=412606 Nick changed: What|Removed |Added Summary|kmail segmentation fault|kmail segmentation fault |after having clicked on a |after having clicked on a |mailto:sa...@company.com|mailto:sa...@company.com |link in firefox browser.|link in firefox or chrome ||browser as long as kmail is ||not already running. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 412606] kmail segmentation fault after having clicked on a mailto:sa...@company.com link in firefox browser.
https://bugs.kde.org/show_bug.cgi?id=412606 --- Comment #1 from Nick --- Important note. If kmail is already running you won't get a segmentation fault. You need to close all instances of kmail and then click on a mailto: link in a webpage. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 412606] New: kmail segmentation fault after having clicked on a mailto:sa...@company.com link in firefox browser.
https://bugs.kde.org/show_bug.cgi?id=412606 Bug ID: 412606 Summary: kmail segmentation fault after having clicked on a mailto:sa...@company.com link in firefox browser. Product: kmail2 Version: 5.12.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: nick.craig@gmail.com Target Milestone: --- Application: kmail (5.12.1) Qt Version: 5.12.3 Frameworks Version: 5.62.0 Operating System: Linux 4.15.0-65-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: Was using the Firefox browser and clicked on a link on a web page "sa...@company.com". A dialogue box opens with a list of possible applications to use of which kmail was one of them. I highlighted kmail, clicked the 'open link' button and kmail crashed with a segmentation fault. 100% reproducable. The kmail segmentation fault also happens if I use the Chrome browser. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2188adcbc0 (LWP 2957))] Thread 20 (Thread 0x7f211a7fc700 (LWP 3004)): #0 0x7f21bc1409f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f211a7fb908) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f21bc1409f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f211a7fb8b8, cond=0x7f211a7fb8e0) at pthread_cond_wait.c:502 #2 0x7f21bc1409f3 in __pthread_cond_wait (cond=0x7f211a7fb8e0, mutex=0x7f211a7fb8b8) at pthread_cond_wait.c:655 #3 0x7f21a68cca49 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f21a68cd478 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f21a68cd50f in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f21a688dfc8 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f21a68907f6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f21a6890b34 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f21a68cf561 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f21bc13a6db in start_thread (arg=0x7f211a7fc700) at pthread_create.c:463 #11 0x7f21bc47388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f211affd700 (LWP 3003)): #0 0x7f21bc4826ac in __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 #1 0x7f21bc484474 in ___fprintf_chk (fp=0x7f21bc73f8b0 <_IO_stdfile_2_lock>, flag=1, format=0x7f219c1ac6a8 "[%s] %s\n") at fprintf_chk.c:30 #2 0x7f219c1949ad in event_logv_ () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #3 0x7f219c194b44 in event_warn () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #4 0x7f219c19646c in () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #5 0x7f219c18c114 in event_base_loop () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #6 0x7f21a68d2db4 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f21a686d2db in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f21a689f311 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f21a68cf561 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f21bc13a6db in start_thread (arg=0x7f211affd700) at pthread_create.c:463 #11 0x7f21bc47388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f211b7fe700 (LWP 3001)): #0 0x7f21bc140ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f211b7fd710, expected=0, futex_word=0x7f211b7fd8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f21bc140ed9 in __pthread_cond_wait_common (abstime=0x7f211b7fd7b0, mutex=0x7f211b7fd8a8, cond=0x7f211b7fd8d0) at pthread_cond_wait.c:533 #2 0x7f21bc140ed9 in __pthread_cond_timedwait (cond=0x7f211b7fd8d0, mutex=0x7f211b7fd8a8, abstime=0x7f211b7fd7b0) at pthread_cond_wait.c:667 #3 0x7f21a68ccb17 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f21a68cd46a in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f21a68cd552 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f21a688dfb1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f21a68904c7 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f21a6890ab4 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f21a68cf561 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f21bc13a6db in start_thread (arg=0x7f211b7fe700) at pthread_create.c:463 #11 0x7f21bc47388f in clone () at
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #56 from Nick --- (In reply to Brendon Higgins from comment #54) > For the record (because Daniel's blog post claims otherwise), existing users > can indeed be affected by this: I've had two GMail accounts accessed from > three serparate machines all start refusing logins over the last few weeks, > at different times. It seems like some kind of expiry happens, at which > point logins start failing. PLAIN works for me, fortunately. > > Feels like Google's really skirting anticompetitive/antitrust territory > here. But maybe I'd have a different opinion given a bit more transparency > on what they were actually asking for. Either way, thanks for going to bat > for us, Daniel! I can also confirm that existing accounts definitely can be affected. Mine has been configured for a long time and only about 3 weeks ago it started denying me access. I was able to switch to PLAIN authentication using an app specific password though. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 410700] kmail no longer allows addition of gmail account
https://bugs.kde.org/show_bug.cgi?id=410700 Nick changed: What|Removed |Added CC||futurepi...@gmx.us -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 Nick changed: What|Removed |Added CC||futurepi...@gmx.us -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 410138] Strange characters displayed in emails when viewed as html or plain text, when there should be a quote character
https://bugs.kde.org/show_bug.cgi?id=410138 Nick changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REOPENED|RESOLVED --- Comment #10 from Nick --- Ok, closed again as not a bug ! hopefully. In Settings->configure kmail->appearance->general there is a setting called override character encoding. This was set to Cyrillic(IBM866). Switching 'override character encoding' to 'auto' now means that 'auto' encoding is retained after kmail is shutdown and restarted. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 410138] Strange characters displayed in emails when viewed as html or plain text, when there should be a quote character
https://bugs.kde.org/show_bug.cgi?id=410138 --- Comment #9 from Nick --- ok, so if you change encoding to auto then reboot the system OR simply exit kmail your encoding will revert back to Cyrillic(IBM866) with the incorrect display of special characters in emails. So it would appear that when I change encoding to auto it doesn't seem to be saved. Is there a setting somewhere that sets default encoding to Cyrillic(IBM866) ? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 410138] Strange characters displayed in emails when viewed as html or plain text, when there should be a quote character
https://bugs.kde.org/show_bug.cgi?id=410138 Nick changed: What|Removed |Added Resolution|NOT A BUG |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #8 from Nick --- Re-opened. I just found encoding in kmail has switched back to Cyrillic(IBM866) all on it's own !. I'm the only person who has access to this system. So something is switching encoding from 'auto' to specifically Cyrillic(IBM866). I've rebooted the system so need to investigate whether the switch from auto to Cyrillic(IBM866) occurs after a reboot. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 410138] Strange characters displayed in emails when viewed as html or plain text, when there should be a quote character
https://bugs.kde.org/show_bug.cgi?id=410138 --- Comment #6 from Nick --- In the email header for the above simple email I have Content-Type: text/plain; charset="iso-8859-1" So it's like the kmail code that displays the email is using the wrong character encoding to render the text correctly. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 410138] Strange characters displayed in emails when viewed as html or plain text, when there should be a quote character
https://bugs.kde.org/show_bug.cgi?id=410138 --- Comment #5 from Nick --- So kmail manages to display the correct character when composing the email but not when viewing the email, however that same email when viewed in gmail displays the copyright symbol correctly. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 410138] Strange characters displayed in emails when viewed as html or plain text, when there should be a quote character
https://bugs.kde.org/show_bug.cgi?id=410138 --- Comment #4 from Nick --- Here's another easy way to reproduce the problem by sending yourself an email containing a special character such as the copyright symbol. To insert a special character, from the menu edit->insert special character. select European Latin 1 supplement. Click on the copyright symbol. The copyright symbol correctly appears in your composed email but after you have sent that email to yourself and view it in kmail the copyright symbol is now a й If you view that same email in gmail the copyright symbol is displayed correctly. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 410138] Strange characters displayed in emails when viewed as html or plain text, when there should be a quote character
https://bugs.kde.org/show_bug.cgi?id=410138 --- Comment #3 from Nick --- Again, here's a direct copy of the rendered text in a HTML email hereтАЩs a cool little email exclusive for your weekend тАУ weтАЩre trimming 15% off your takeaway*. And thatтАЩs whether you order Friday, Saturday or Sunday. Tuck in! and here's what that specific section of the email source looks like. here=E2=80=99s a cool little email exclusive fo= r your weekend =E2=80=93 we=E2=80=99re trimming 15% off your takeaway*. And= that=E2=80=99s whether you order Friday, Saturday or Sunday. Tuck in! Notice the =E2=80=99 where there should be a ` or ' -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 410138] Strange characters displayed in emails when viewed as html or plain text, when there should be a quote character
https://bugs.kde.org/show_bug.cgi?id=410138 --- Comment #2 from Nick --- This is not just the incorrect display of quote characters but also the copyright character and I would imagine lots of other non alpha numeric characters. I'm not exactly sure when this bug appeared but I think it might have been after a recent update. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 410138] Strange characters displayed in emails when viewed as html or plain text, when there should be a quote character
https://bugs.kde.org/show_bug.cgi?id=410138 --- Comment #1 from Nick --- Created attachment 121695 --> https://bugs.kde.org/attachment.cgi?id=121695=edit Email properly rendered in gmail, correctly showing ' character -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 410138] New: Strange characters displayed in emails when viewed as html or plain text, when there should be a quote character
https://bugs.kde.org/show_bug.cgi?id=410138 Bug ID: 410138 Summary: Strange characters displayed in emails when viewed as html or plain text, when there should be a quote character Product: kmail2 Version: 5.11.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: misc Assignee: kdepim-bugs@kde.org Reporter: nick.craig@gmail.com Target Milestone: --- Created attachment 121694 --> https://bugs.kde.org/attachment.cgi?id=121694=edit email in HTML view showing odd character (circled) instead of ' character SOFTWARE/OS VERSIONS KDE NEON Linux/KDE Plasma: Neon 5.16.3 KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60.0 Qt Version: 5.12.3 Kernel 4.15.0-55-generic 64bit SUMMARY When displaying some emails (either HTML or text mode) you get some strange looking characters inserted amongst the text as shown below. Here's an extract... notice the '┬' character 4th line up from the bottom and 2nd line up from the bottom. Images not loading? Click Here to view this newsletter in your browser.(http://emailclick.imlgrouponthenet.net/profile/S-23344@aawG9tsEOImiTXAR1Zm2UUCtJMmysgmQ6-mvyV8oq5U.@11) EPDT's July 2019 issue is now available, in print & digital editions! Read the digital issue(http://emailclick.imlgrouponthenet.net/email/S-23344@1068604@aawG9tsEOImiTXAR1Zm2UUCtJMmysgmQ6-mvyV8oq5U.@) now or register to receive the print magazine(http://emailclick.imlgrouponthenet.net/email/S-23344@1068605@aawG9tsEOImiTXAR1Zm2UUCtJMmysgmQ6-mvyV8oq5U.@) each month. This monthтАЩs issue(http://emailclick.imlgrouponthenet.net/email/S-23344@1068606@aawG9tsEOImiTXAR1Zm2UUCtJMmysgmQ6-mvyV8oq5U.@) contains features on Electromechanical technologies and Mil/Aero applications, as well as EPDT's twice-yearly IoT & Industry 4.0 supplement(http://emailclick.imlgrouponthenet.net/email/S-23344@1068607@aawG9tsEOImiTXAR1Zm2UUCtJMmysgmQ6-mvyV8oq5U.@). ┬а (http://emailclick.imlgrouponthenet.net/email/S-23344@1068608@aawG9tsEOImiTXAR1Zm2UUCtJMmysgmQ6-mvyV8oq5U.@) ┬а ┬а Inside EPDT's July issue: Take a look at the two attachment pictures. One picture is the HTML version of the above email. The other is how it is rendered properly in gmail. STEPS TO REPRODUCE Just look through your emails for odd looking characters OBSERVED RESULT See one of the attachments, I have circled the strange character where there should be a ' character. EXPECTED RESULT See one of the attachments for the HTML email rendered correctly in gmail. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 408354] If default maildir folder is changed a new set of folders are stored under "/home/$user/file:"
https://bugs.kde.org/show_bug.cgi?id=408354 --- Comment #5 from Nick --- On the same computer I created a new user. I then changed the default location of the maildir folder from /home/[user]/.local/share/local-mail to a folder called /home/[user]/emails. Both locations are on the same partition. No symbolic links are involved. kmail (or akonadi) then creates a directory file:/home/[user]/emails/inbox Even more oddly the ..inbox/ folder that contains the subdirectories new, cur and tmp, if you look inside new you will find another subdirectory called file: This path in full is shown here. This is created by either kmail or Akonadi. /home/marmite/file:/home/marmite/local-mail/inbox/new/file:/home/marmite/local-mail/inbox/new/new -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 408354] If default maildir folder is changed a new set of folders are stored under "/home/$user/file:"
https://bugs.kde.org/show_bug.cgi?id=408354 --- Comment #4 from Nick --- I'll do a fresh install and see if I can find specifically what triggers this problem. One thing that is most likely different from the average install is that /home/nick/Data is a symbolic link to /media/nick/Data_sdb. /media/nick/Data_sdb is mounted at boot to /dev/sdb3 The df entry looks like this: /dev/sdb3591G 556G 4.8G 100% /media/nick/Data_sdb (I know the partition is at 100%) And the /etc/fstab entry is: UUID=329dc068-a4ed-45fd-9b0b-0ef09ca926ee /media/nick/Data_sdb ext4 defaults 0 2 My initial thoughts are that this symbolic linking and use of a different partition 'may' have something to do with the problem. So my plan would be to start with a working install using the default maildir location, then change to a valid maildir folder on a different directory. Not forgetting the symbolic link. I'll update you if I can reproduce this on a fresh install. Just to note, I have tried deleting /home/nick/.local/share/akonadi and letting it rebuild but it still would not index the emails. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 408354] If default maildir folder is changed a new set of folders are stored under "/home/$user/file:"
https://bugs.kde.org/show_bug.cgi?id=408354 --- Comment #2 from Nick --- That's great!. Thank You. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 408354] New: If default maildir folder is changed a new set of folders are stored under "/home/$user/file:"
https://bugs.kde.org/show_bug.cgi?id=408354 Bug ID: 408354 Summary: If default maildir folder is changed a new set of folders are stored under "/home/$user/file:" Product: kmail2 Version: 5.11.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: nick.craig@gmail.com Target Milestone: --- Created attachment 120604 --> https://bugs.kde.org/attachment.cgi?id=120604=edit Dialog box where you change the maildir folder If the default maildir folder is changed using the dialog box as shown in the attached snapshot then kmail fails to use that folder but creates a new folder under your home directory in a folder called "file:" Example: If you enter /home/nick/Data/local-mail as the folder containing your maildir files, kmail instead creates and uses /home/nick/file:/home/nick/Data/local-mail.directory/ which of course isn't where your maildir folders and files are ! Why is kmail creating a subdirectory called "file:" in your home directory ? The problem this creates is that any old emails that are in /home/nick/Data/local-mail don't get indexed or displayed by kmail. Also because kmail insists on creating a file: subdirectory in your home folder and storing new email there you can't have all your emails on a different partition to your home folder. KDE INFO KDE Neon 5.15 User Edition Plasma 5.15.5 Frameworks 5.58.0 QT 5.12.0 Kernel 4.15.0-50 OS 64 Bit -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 406856] Found 3734 items without RID.; Item "30024" has RID and is dirty.
https://bugs.kde.org/show_bug.cgi?id=406856 --- Comment #8 from Nick --- Martin, After the "remoteId is null" clean I tried to import some records/messages that had "remoteId" issues [ based on pimitemtable I found out their associated collectionid [ i.e. a dir under Local Folders ]. The import was done into a new folder called "Import_from_archive" . It went fine and it created the entire folder stuctures existing under "Inbox" . Then I MOVED the contents of the imported emails into the old folder . After that everything under the folder "Import_from_archive" was deleted . Stop kmail , start kmail the issue akonadictl fsck Gues what ? The "Item has not RID" was back . Cleaned the null RIDs again and repeat the import . The only diffrence was to COPY from imported structure in the old structure . Stop kmail , start kmail the issue akonadictl fsck Gues what ?No "Item has not RID" !!! That means thet the move is a physical move of data whereas copy involves some logical processing that recreaates the messages/records . With this procedure I am very confident that only a few emails were lost . I do not know who's doing the move and who's doing the copy . Thanks, Nick -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 406856] Found 3734 items without RID.; Item "30024" has RID and is dirty.
https://bugs.kde.org/show_bug.cgi?id=406856 --- Comment #7 from Nick --- Created attachment 119696 --> https://bugs.kde.org/attachment.cgi?id=119696=edit akonadictl_fsck_vacuum_after_NULL-RID_cleanup.txt -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 406856] Found 3734 items without RID.; Item "30024" has RID and is dirty.
https://bugs.kde.org/show_bug.cgi?id=406856 --- Comment #5 from Nick --- Martin, akonadictl version is 5.7.3 kdepim is at level 17.12.3 The levels of all akonadi/kmail/etc installed software and the reports od akonadictl fsck| vacuum are provided as attachments. After the "remoteId is NULL" cleanup I noticed that all those annoyng messages "wait until ..." are gone . I checked my email at the interner provider server and there are no emails there . The IP tech support told me that with IMAP after an email is received by the client[laptop] it is deleted from the server . So I did not understand why the kmail client was checking remote server . Now it appears that kmail/akonadi tries to solve that NULL remoteId . akonadictl fsck's message ' Item "28761" has no RID.' is wrong . That item with id=28761 HAS an RID but its value is set to NULL . It is very strange/misleading message and the culprit seems to be akonadictl and/or kmail because they do not interpret correctly database/table/record's contents . Thanks, Nick -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 406856] Found 3734 items without RID.; Item "30024" has RID and is dirty.
https://bugs.kde.org/show_bug.cgi?id=406856 --- Comment #6 from Nick --- Created attachment 119695 --> https://bugs.kde.org/attachment.cgi?id=119695=edit akonadi_kmail_kontact_mariadb_installed_software_levels.txt -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 389607] akonadictl fsck: Show more helpful messages
https://bugs.kde.org/show_bug.cgi?id=389607 --- Comment #8 from Nick --- Hello Martin, Thank you for your email and your comments . I agree that some emails may be lost . I took the time to try making/finding some correlations with what the user sees . - First of all I converted to IMAP as per ip provider's tech-support . So the database contains records from the "old" [maildir? ] system and the new "IMAP" system . Also I had to move the database from my old machine to a new one [ in fact entire /home from old was transfered to the new machine ] So the same userid had acceess to the emails immediately after opensuse leap 15.0 was installed on the new machine ]. I do not know if these changes have any impact [ the hostname was chaged ] - Based on the way akonadictl presents its resulst it(akonadictl) is NOT a user friendly tool . On the contrary the actual reporting scares the user with those messages "no RID" or "dirty" or "records removed from data base and moved in lost-and-found" without at least to ask the user if [s]he wants/agrees with that move . I looked closely to pimitemtable and it seems that the column remoteId is nullable [ i.e. accepts an undefinned/unidentified/unknowm value ]. I believe that the hub of all these issues is not with the database server but with akonadi because switching between MariaDB and Postgresql does not stop the isses from happening. These problems in kmail-database are inherited from the time when kmail was using sqlite . In my humble opinion, the database server does what is told/comanded by the interface between the user and the database---that is akonadi---. It is strange that a such important item as remoteId was translated in a datamodel that accepts it as being nullable . That allows that any event that is not controlled by the code inserts/updates a record as having remoteId NULL, and from this all users' complaints . This assumption does not match the reality . I would like to know how it comes that receiving an email---which has a sender and a receiver--- is recorded in the database with a remoteId of NULL value ? I provide below some info collected from my machine before c;eaning up the records with RID NULl in pimitemtable . You van notice that that record had a valid collectionId but has invalid remoteId . I checked that many other emails with valid remoteId pointer to the same collection Id . I tend to agree with you that . `` However it also could be that Akonadi just messes up big time like in storing the items into remote storage, but somehow failing to store the remote ID or whatever. `` I believe that KDE development should have a look at kmail-database-datamodel if it matches technical-requirements and/or ifv akonadi handles the email requests properly . Also it is very dificult for the user to find any item that is wrong using kmail and not to dig in databse tables . That's the role of akonadictl and/or what ever any USER ORIENTED tools . I believe that akonadikconsole is too powerful for the casual user . At the same time akonadi seem to keep their cards close to the vest . making easy for developers to point to user errors . The users have had it for too long asking and asking and asking and nothing to be done . Thank you, Nick = info from my machine = -- describe pimitemtable -- Field TypeNullKey Default Extra id bigint(20) NO PRI NULLauto_increment rev int(11) NO 0 remoteIdvarbinary(255) YES MUL NULL remoteRevision varbinary(255) YES NULL gid varbinary(255) YES MUL NULL collectionIdbigint(20) YES MUL NULL mimeTypeId bigint(20) YES MUL NULL datetimetimestamp NO current_timestamp() atime timestamp NO current_timestamp() dirty tinyint(1) YES NULL sizebigint(20) NO 0 -- select count(*) from pimitemtable -- count(*) 8691 Record without RID as reported by akonadictl fsck [ 38264 item ... RID ] 38264 5 NULLNULLNULL123 4 2019-04-05 01:12:16 2019-04-05 01:12:16 1 81206 collectionId 123 is one of directories under "Local Folders -- describe pimitemflagrelation -- Field TypeNullKey Default Extra PimItem_id bigint(20) NO PRI NULL Flag_id bigint(20) NO PRI NULL -- select count(*) from pimitemflagrelation -- count(*) 13859 Records associated with id 38264 [ from pimitemtable ] 38264 1 38264 5 38264 12 38264 13 -- describe parttable -- Field TypeNullKey Default Extra id bigint(20
[Akonadi] [Bug 406856] Found 3734 items without RID.; Item "30024" has RID and is dirty.
https://bugs.kde.org/show_bug.cgi?id=406856 --- Comment #3 from Nick --- Hello Martin, Thank you for your email and your comments . I agree that some emails may be lost . I took the time to try making/finding some correlations with what the user sees . - First of all I converted to IMAP as per ip provider's tech-support . So the database contains records from the "old" [maildir? ] system and the new "IMAP" system . Also I had to move the database from my old machine to a new one [ in fact entire /home from old was transfered to the new machine ] So the same userid had acceess to the emails immediately after opensuse leap 15.0 was installed on the new machine ]. I do not know if these changes have any impact [ the hostname was chaged ] - Based on the way akonadictl presents its resulst it(akonadictl) is NOT a user friendly tool . On the contrary the actual reporting scares the user with those messages "no RID" or "dirty" or "records removed from data base and moved in lost-and-found" without at least to ask the user if [s]he wants/agrees with that move . I looked closely to pimitemtable and it seems that the column remoteId is nullable [ i.e. accepts an undefinned/unidentified/unknowm value ]. I believe that the hub of all these issues is not with the database server but with akonadi because switching between MariaDB and Postgresql does not stop the isses from happening. These problems in kmail-database are inherited from the time when kmail was using sqlite . In my humble opinion, the database server does what is told/comanded by the interface between the user and the database---that is akonadi---. It is strange that a such important item as remoteId was translated in a datamodel that accepts it as being nullable . That allows that any event that is not controlled by the code inserts/updates a record as having remoteId NULL, and from this all users' complaints . This assumption does not match the reality . I would like to know how it comes that receiving an email---which has a sender and a receiver--- is recorded in the database with a remoteId of NULL value ? I provide below some info collected from my machine before c;eaning up the records with RID NULl in pimitemtable . You van notice that that record had a valid collectionId but has invalid remoteId . I checked that many other emails with valid remoteId pointer to the same collection Id . I tend to agree with you that . `` However it also could be that Akonadi just messes up big time like in storing the items into remote storage, but somehow failing to store the remote ID or whatever. `` I believe that KDE development should have a look at kmail-database-datamodel if it matches technical-requirements and/or ifv akonadi handles the email requests properly . Also it is very dificult for the user to find any item that is wrong using kmail and not to dig in databse tables . That's the role of akonadictl and/or what ever any USER ORIENTED tools . I believe that akonadikconsole is too powerful for the casual user . At the same time akonadi seem to keep their cards close to the vest . making easy for developers to point to user errors . The users have had it for too long asking and asking and asking and nothing to be done . Thank you, Nick = info from my machine = -- describe pimitemtable -- Field TypeNullKey Default Extra id bigint(20) NO PRI NULLauto_increment rev int(11) NO 0 remoteIdvarbinary(255) YES MUL NULL remoteRevision varbinary(255) YES NULL gid varbinary(255) YES MUL NULL collectionIdbigint(20) YES MUL NULL mimeTypeId bigint(20) YES MUL NULL datetimetimestamp NO current_timestamp() atime timestamp NO current_timestamp() dirty tinyint(1) YES NULL sizebigint(20) NO 0 -- select count(*) from pimitemtable -- count(*) 8691 Record without RID as reported by akonadictl fsck [ 38264 item ... RID ] 38264 5 NULLNULLNULL123 4 2019-04-05 01:12:16 2019-04-05 01:12:16 1 81206 collectionId 123 is one of directories under "Local Folders -- describe pimitemflagrelation -- Field TypeNullKey Default Extra PimItem_id bigint(20) NO PRI NULL Flag_id bigint(20) NO PRI NULL -- select count(*) from pimitemflagrelation -- count(*) 13859 Records associated with id 38264 [ from pimitemtable ] 38264 1 38264 5 38264 12 38264 13 -- describe parttable -- Field TypeNullKey Default Extra id bigint(20
[Akonadi] [Bug 406856] Found 3734 items without RID.; Item "30024" has RID and is dirty.
https://bugs.kde.org/show_bug.cgi?id=406856 Nick changed: What|Removed |Added CC||ndor...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 406856] Found 3734 items without RID.; Item "30024" has RID and is dirty.
https://bugs.kde.org/show_bug.cgi?id=406856 --- Comment #1 from Nick --- I did a little bit of work with akonadi database and realized that all items with remoteId null are in pimitemtable with references to parttable and pimitemflagrelation , I got to akonadi database via sokket then issued the commands : select "akonadi database status of NULL RemoteId before clean up "; select count(*) from akonadi.pimitemtable where remoteId is NULL ; select count(*) from akonadi.parttable where pimItemId in ( select id from pimitemtable where remoteId is null ) ; select count(*) from akonadi.pimitemflagrelation where PimItem_id in ( select id from pimitemtable where remoteId is null ) ; -- delete from akonadi.pimitemflagrelation where PimItem_id in ( select id from pimitemtable where remoteId is null ) ; delete from akonadi.parttable where pimItemId in ( select id from pimitemtable where remoteId is null ) ; delete from akonadi.pimitemtable where remoteId is NULL ; -- select "akonadi database status of NULL RemoteId after clean up "; select count(*) from akonadi.pimitemtable where remoteId is NULL ; select count(*) from akonadi.parttable where pimItemId in ( select id from pimitemtable where remoteId is null ) ; select count(*) from akonadi.pimitemflagrelation where PimItem_id in ( select id from pimitemtable where remoteId is null ) ; After that the akonadictl fsck appears clean . -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 389607] akonadictl fsck: Show more helpful messages
https://bugs.kde.org/show_bug.cgi?id=389607 --- Comment #6 from Nick --- Similar issues . akonadi fsck / vacuum reports many issues/messages but did not give to the user any hints on how to solve them . What about having an option akonadictl fix [ noRID | dirtyRID ...etc ] ? Such tool will reduce the number of bugs reported by akonadictl fsck Also, what about telling the users : 1) procedures of fixing issues 2) procedures of getting rid on unnnecessary messages and/or 3) procedures of cleaning up the akonadi db of "dead" records and above all 4) how the user should access akonadi mysql db which is handled [ start/stp] by akonadi . See bug 406856 recently opened Thanks . Nick -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 389607] akonadictl fsck: Show more helpful messages
https://bugs.kde.org/show_bug.cgi?id=389607 Nick changed: What|Removed |Added CC||ndor...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 406856] New: Found 3734 items without RID.; Item "30024" has RID and is dirty.
https://bugs.kde.org/show_bug.cgi?id=406856 Bug ID: 406856 Summary: Found 3734 items without RID.; Item "30024" has RID and is dirty. Product: Akonadi Version: 5.7.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libakonadi Assignee: kdepim-bugs@kde.org Reporter: ndor...@gmail.com Target Milestone: --- SUMMARY After switching to IMAP akonadi fsck reports thousands of messages `Item "." has no RID.` as well as that one item is dirty . Is there any procedure to clean up the akonadi mysql data base to get rid of those messagews ? It seems that akonadi handles the connection to mysql . How a user can access akonadi mysql database and run any solutions KDE team suggets ? STEPS TO REPRODUCE 1. at will wunning akonadictl fsck 2. 3. OBSERVED RESULT Thousand of Item "." has no RID. messages Found 3734 items without RID. Item "30024" has RID and is dirty. Found 1 dirty items. EXPECTED RESULT No such messages SOFTWARE/OS VERSIONS Linux/KDE Plasma: leap 15.0 (available in About System) KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.45.0 Qt Version: ? ADDITIONAL INFORMATION [akonadi fsck/vacuum/status output ] 2019/04/23-18:39:42 ; Start /Common_Bin/akonadi_utils.sh akonadictl fsck Looking for resources in the DB not matching a configured resource... Looking for collections not belonging to a valid resource... Checking collection tree consistency... Looking for items not belonging to a valid collection... Looking for item parts not belonging to a valid item... Looking for item flags not belonging to a valid item... Looking for overlapping external parts... Verifying external parts... Found 5906 external files. Found 5906 external parts. Found no unreferenced external files. Checking size treshold changes... Found 0 parts to be moved to external files Found 0 parts to be moved to database Looking for dirty objects... Collection "Search" (id: 1) has no RID. Collection "OpenInvitations" (id: 151) has no RID. Collection "DeclinedInvitations" (id: 152) has no RID. Collection "Import_from_archive" (id: 160) has no RID. Found 4 collections without RID. Item "28761" has no RID. . Item "33803" has no RID. Item "33804" has no RID. Item "38264" has no RID. Found 3734 items without RID. Item "30024" has RID and is dirty. Found 1 dirty items. Looking for rid-duplicates not matching the content mime-type of the parent collection Checking Local Folders Checking Notes Checking Personal Calendar Checking Search Checking ndordea@IMAP Checking DeclinedInvitations Checking OpenInvitations Checking Alarm_Templates . Migrating parts to new cache hierarchy... Checking search index consistency... Skipping virtual Collection 1 Checking Collection 2 search index... Checking Collection 3 search index... Checking Collection 4 search index... . Checking Collection 150 search index... Skipping virtual Collection 151 Skipping virtual Collection 152 Checking Collection 153 search index... Checking Collection 255 search index... Flushing collection statistics memory cache... Consistency check done. akonadictl vacuum vacuuming database, that'll take some time and require a lot of temporary disk space... optimizing table SchemaVersionTable... optimizing table ResourceTable... optimizing table CollectionTable... optimizing table MimeTypeTable... optimizing table PimItemTable... optimizing table FlagTable... optimizing table PartTypeTable... optimizing table PartTable... optimizing table CollectionAttributeTable... optimizing table TagTypeTable... optimizing table TagTable... optimizing table TagAttributeTable... optimizing table TagRemoteIdResourceRelationTable... optimizing table RelationTypeTable... optimizing table RelationTable... optimizing table PimItemFlagRelation... optimizing table PimItemTagRelation... optimizing table CollectionMimeTypeRelation... optimizing table CollectionPimItemRelation... vacuum done akonadictl status Akonadi Control: running Akonadi Server: running Akonadi Server Search Support: available (Remote Search) Available Agent Types: akonadi_akonotes_resource, akonadi_archivemail_agent, akonadi_birthdays_resource, akonadi_contacts_resource, akonadi_davgroupware_resource, akonadi_ews_resource, akonadi_ewsmta_resource, akonadi_facebook_resource, akonadi_followupreminder_agent, akonadi_googlecalendar_resource, akonadi_googlecontacts_resource, akonadi_ical_resource, akonadi_icaldir_resource, akonadi_imap_resource, akonadi_indexing_agent, akonadi_invitations_agent, akonadi_kalarm_dir_resource, akonadi_kalarm_resource, akonadi_knut_resource, akonadi_kolab_resource, akonadi_maildir_resource, akonadi_maildispatcher_agent, akonadi_mailfilter_agent, akonadi_mbox_resource, akonadi_migration_agent, akonadi_mixedmaildir_resource, akonadi_newmailnotifier_agent,
[kmail2] [Bug 406104] New: Kmail crashes when you try to run it
https://bugs.kde.org/show_bug.cgi?id=406104 Bug ID: 406104 Summary: Kmail crashes when you try to run it Product: kmail2 Version: 5.10.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: nick.craig@gmail.com Target Milestone: --- Application: kmail (5.10.3) Qt Version: 5.12.0 Frameworks Version: 5.55.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: Just clicked on the kmail icon, kmail crashed. Not sure if it makes any difference but I also use the kmail resource that allows you to link you gmail contacts to kde so that all my contacts are available to kmail. The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f55a5cdcbc0 (LWP 26520))] Thread 24 (Thread 0x7f5583bd9700 (LWP 26625)): #0 0x7f55d91df0b4 in __GI___libc_read (fd=24, buf=0x7f5583bd87d0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f55ccb15cd0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f55ccad1027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f55ccad14e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f55ccad164c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f55d9b2615b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f557c005290, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f55d9ac764a in QEventLoop::exec(QFlags) (this=this@entry=0x7f5583bd89e0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f55d98ef41a in QThread::exec() (this=) at thread/qthread.cpp:531 #8 0x7f55d98f0bc2 in QThreadPrivate::start(void*) (arg=0x55fb89ebbe00) at thread/qthread_unix.cpp:361 #9 0x7f55d8eb76db in start_thread (arg=0x7f5583bd9700) at pthread_create.c:463 #10 0x7f55d91f088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7f548700 (LWP 26586)): #0 0x7f55ccb17049 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f55ccad10c6 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f55ccad15c0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f55ccad164c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f55d9b2615b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f5488000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f55d9ac764a in QEventLoop::exec(QFlags) (this=this@entry=0x7f548fffe9e0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f55d98ef41a in QThread::exec() (this=) at thread/qthread.cpp:531 #7 0x7f55d98f0bc2 in QThreadPrivate::start(void*) (arg=0x55fb8d11b990) at thread/qthread_unix.cpp:361 #8 0x7f55d8eb76db in start_thread (arg=0x7f548700) at pthread_create.c:463 #9 0x7f55d91f088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7f551a3ee700 (LWP 26585)): #0 0x7f55d8ebd9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f55bf0c8fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f55d8ebd9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f55bf0c8f68, cond=0x7f55bf0c8f90) at pthread_cond_wait.c:502 #2 0x7f55d8ebd9f3 in __pthread_cond_wait (cond=0x7f55bf0c8f90, mutex=0x7f55bf0c8f68) at pthread_cond_wait.c:655 #3 0x7f55bedd2844 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f55bedd2889 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f55d8eb76db in start_thread (arg=0x7f551a3ee700) at pthread_create.c:463 #6 0x7f55d91f088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f5521fe6700 (LWP 26572)): #0 0x7f55d8ebded9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f5521fe5710, expected=0, futex_word=0x7f5521fe58f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f55d8ebded9 in __pthread_cond_wait_common (abstime=0x7f5521fe57b0, mutex=0x7f5521fe58a8, cond=0x7f5521fe58d0) at pthread_cond_wait.c:533 #2 0x7f55d8ebded9 in __pthread_cond_timedwait (cond=0x7f5521fe58d0, mutex=0x7f5521fe58a8, abstime=0x7f5521fe57b0) at pthread_cond_wait.c:667 #3 0x7f55c3b10177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f55c3b10ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f55c3b10bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f55c3ace851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f55c3ad16b6 in () at
[kontact] [Bug 404588] New: Unable to create a calendar event from email
https://bugs.kde.org/show_bug.cgi?id=404588 Bug ID: 404588 Summary: Unable to create a calendar event from email Product: kontact Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: calendar Assignee: kdepim-bugs@kde.org Reporter: mobile.har...@gmail.com Target Milestone: --- SUMMARY I am running KDE Neon 5.14.5 and Kontact 5.10.1. I have two GMail accounts configured in Kontact including their associated calendars configured. I wish to drag an email to the calendar to create a new event but this does not currently work. STEPS TO REPRODUCE 1I want to create a new calendar event from an email, so I drag the mail from my inbox onto the Calendar icon on the left-hand side. According to this page (https://docs.kde.org/stable5/en/pim/kontact/side-pane-drag-and-drop.html) OBSERVED RESULT The event subject looks as follows: "akonadi:?item=45620=message/rfc822=55" I also do not get any of the email body transferred into the event body, making the feature pretty useless overall. EXPECTED RESULT I should get a new calendar event with the subject populated with the same subject from the email. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.15 KDE Plasma Version: 5.15.0 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 Kernel Version: 4.18.0-15-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 7.5 GiB of RAM ADDITIONAL INFORMATION Another user reports this problem exists on Neon Dev Stable too. See this forum thread for more details: https://forum.kde.org/viewtopic.php?f=215=156828=248f8696ef3b37d0a5b54bd1836a0937=411109#p409937 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 403067] Akonadi crash in akonadi_maildir_resource
https://bugs.kde.org/show_bug.cgi?id=403067 --- Comment #4 from Nick --- Created attachment 117734 --> https://bugs.kde.org/attachment.cgi?id=117734=edit useful debug info - akonadi maildir crash, segmentation fault. I installed the debug symbols so that hopefully the information in this attached file is useful. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 403067] Akonadi crash in akonadi_maildir_resource
https://bugs.kde.org/show_bug.cgi?id=403067 --- Comment #3 from Nick --- The crash occurs every time I click on the 'Check Mail' button in kmail. Despite the crash new mail appears in the inbox. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 403067] Akonadi crash in akonadi_maildir_resource
https://bugs.kde.org/show_bug.cgi?id=403067 --- Comment #2 from Nick --- Created attachment 117390 --> https://bugs.kde.org/attachment.cgi?id=117390=edit Snapshot of initial error message -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 403067] Akonadi crash in akonadi_maildir_resource
https://bugs.kde.org/show_bug.cgi?id=403067 Nick changed: What|Removed |Added CC||nick.craig@gmail.com --- Comment #1 from Nick --- Created attachment 117389 --> https://bugs.kde.org/attachment.cgi?id=117389=edit backtrace akonadi_maildir_resource segmentation fault -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 403067] New: Akonadi crash in akonadi_maildir_resource
https://bugs.kde.org/show_bug.cgi?id=403067 Bug ID: 403067 Summary: Akonadi crash in akonadi_maildir_resource Product: Akonadi Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Maildir Resource Assignee: kdepim-bugs@kde.org Reporter: nick.craig@gmail.com Target Milestone: --- Created attachment 117379 --> https://bugs.kde.org/attachment.cgi?id=117379=edit KDebugdialog output SUMMARY After starting kmail I get a akonadi maildir_resource segmentation fault. It occurs every time. I'm using a gmail contacts resource. Only starting happening after upgrading to KDE Neon 18.04 Plasma 5.14.5, did not happen in 16.04LTS KDE Neon Plasma 5.12.7 Typcally a crash window pops up containing the text (summary, for full text see attachment) mentions a segmentation fault to do with akonadi_maildir_resource and summary from kdebugdialog (see attachement for full text) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = akonadi_maildir_resource path = /usr/bin pid = 26298 KCrash: Arguments: /usr/bin/akonadi_maildir_resource --identifier akonadi_maildir_resource_0 KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 18.04/5.14.5 (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.53.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 402822] akonadi_control crash after opening KMail
https://bugs.kde.org/show_bug.cgi?id=402822 Nick changed: What|Removed |Added CC||nick.craig@gmail.com --- Comment #2 from Nick --- Created attachment 117378 --> https://bugs.kde.org/attachment.cgi?id=117378=edit Output of Kdebugdialog multiple crashes shown Typical crash (see attachments for full text) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = akonadi_maildir_resource path = /usr/bin pid = 24861 KCrash: Arguments: /usr/bin/akonadi_maildir_resource --identifier akonadi_maildir_resource_0 KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 397634] Is it possible to define a port for akonadi mariadb database ?
https://bugs.kde.org/show_bug.cgi?id=397634 Nick changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Nick --- Thank you to all who commented on my questions. Also, I apologize for my late response . I am in process of analyzing Daniel's comments/recommendations then deciding how to proceed . I hope that this will help me to alleviate / eliminate those "waiting for update/read/etc" that happens quite often inn Kmail5 . For the time being I will change tje status of this ticket to REPORTED . Thanks again to everybody . Regards, Nick -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 397634] New: Is it possible to define a port for akonadi mariadb database ?
https://bugs.kde.org/show_bug.cgi?id=397634 Bug ID: 397634 Summary: Is it possible to define a port for akonadi mariadb database ? Product: Akonadi Version: 5.8.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: ndor...@gmail.com Target Milestone: --- Hello , This is not a bug. It is a request for information . A). The only way of accessing kmail mysql /mariadb data base is via mysql -h localhost -S /tpm/akonadi-x.T2YTcF/mysql.socket B). I tried to get more info via Percoma tools B.1). pt-mysql-summary --host localhost --socket /tmp/akonadi-rocco.T2YTcF/mysql.socket # Percona Toolkit MySQL Summary Report ### System time | 2018-08-19 17:07:09 UTC (local TZ: CDT -0500) # Instances ## Port Data Directory Nice OOM Socket = == === == 00 /home//.local/share/akonadi/db_data/ 00 /tmp/akonadi-.T2YTcF/mysql.socket # MySQL Executable ### Path to executable | /usr/sbin/mysqld Has symbols | No # Report On Port 0 ### User | @ Time | 2018-08-19 12:07:09 (CDT) Hostname | SuSE4.dom Version | 10.2.15-MariaDB openSUSE package Built On | Linux x86_64 Started | 2018-08-19 06:57 (up 0+05:09:31) Databases | 5 Datadir | /home//.local/share/akonadi/db_data/ Processes | 6 connected, 1 running Replication | Is not a slave, has 0 slaves connected Pidfile | /tmp/akonadi-.T2YTcF/mysql.pid (exists) # Processlist B.2) pt-mysql-summary --host localhost --user root --password # Percona Toolkit MySQL Summary Report ### System time | 2018-08-19 17:11:51 UTC (local TZ: CDT -0500) # Instances ## Port Data Directory Nice OOM Socket = == === == 00 /home//.local/share/akonadi/db_data/ 00 /tmp/akonadi-.T2YTcF/mysql.socket # MySQL Executable ### Path to executable | /usr/sbin/mysqld Has symbols | No # Report On Port 3306 User | root@localhost Time | 2018-08-19 12:11:51 (CDT) Hostname | SuSE4Rocco Version | 10.2.15-MariaDB openSUSE package Built On | Linux x86_64 Started | 2018-08-19 06:54 (up 0+05:17:25) Databases | 6 Datadir | /var/lib/mysql/ Processes | 1 connected, 1 running Replication | Is not a slave, has 0 slaves connected Pidfile | /var/lib/mysql/SuSE4.pid (does not exist) # Processlist C.) I would like to use adminer and/or any mysql workbench to have access to akonadi database . Unfortunately the only options to define a database connection are : host port user password The only option I know is that mysql user name = akonadi Base : ~./config/akonadi/akonadiserverrc [Debug] Tracer=null [%General] Driver=QMYSQL [QMYSQL] Host= Name=akonadi Options="UNIX_SOCKET=/tmp/akonadi-.T2YTcF/mysql.socket" ServerPath=/usr/sbin/mysqld StartServer=true D.) Questions : 1. What are the akonadi's password and port of akonadi mariaDB database ? 2. Is it appropriate/recommended to switch akonadi MariaDB from internal to external ? 3. Is it possible to move the MariaDB akonadi database to the system's location /var/log/mysql or any other/better one ? [ I have disk space issues and I have hard time to move the entire /home to another location ] 4. Is it possible/recommended to switch from MariaDB 10.2.15 to Oracle's mysql 8.0.2 community data server ? [ Unfortunately these two database servers can not coexist on the same machine ] 5. If it is possible what would be the procedure [ dump from MariaDB and import ... ? ] Thank you very much Nick -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 390798] Akonadi EWS failed to authenticate with Exchange Server
https://bugs.kde.org/show_bug.cgi?id=390798 Nick Berg changed: What|Removed |Added CC||nick.be...@gmail.com --- Comment #16 from Nick Berg --- What is the best way to apply this patch to fix this issue? I am on Kubuntu 18.04. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 352701] Kontact forgets how to download messages
https://bugs.kde.org/show_bug.cgi?id=352701 --- Comment #10 from Nick <nick.craig@gmail.com> --- And if you have rebuild your database but find new mail isn't showing up in the inbox then this is the fix. You will need to correct the destination folders in any filters you created in kmail as they are now probably pointing to the wrong folders. In kmail [Settings]>[Configure Filters] and if the filter uses a 'move into folder' action, check it's moving to the correct folder. This also applies to any account destination folders, ie my gmail pop3 account was saving into a zoneminder folder I'd created. In kmail, [Settings]>[Configure Kmail]>[Accounts]>[Receiving Tab] click on your account, check destination folder. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 352701] Kontact forgets how to download messages
https://bugs.kde.org/show_bug.cgi?id=352701 --- Comment #9 from Nick <nick.craig@gmail.com> --- BTW I'm running KDE Neon LTS 5.8 KDE Plasma Version 5.8.7 KDE Frameworks Version 5.38.0 QT Version 5.7.1 Kernel Version 4.10.0-33-generic OS Type 64-bit Processors 8x Intel Core I7 @ 2.2GHz Memory 16GB -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 352701] Kontact forgets how to download messages
https://bugs.kde.org/show_bug.cgi?id=352701 --- Comment #8 from Nick <nick.craig@gmail.com> --- Interesting Quote You should execute mysql_upgrade each time you upgrade MySQL. https://dev.mysql.com/doc/refman/5.7/en/mysql-upgrade.html -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 352701] Kontact forgets how to download messages
https://bugs.kde.org/show_bug.cgi?id=352701 --- Comment #7 from Nick <nick.craig@gmail.com> --- Doing a more /var/log/apt/history.log | grep mysql I can see that akonadi-backend-mysql was updated just before I started getting this problem. I'm almost certain that's what messed up the mysql database and was the answer to run mysql_upgrade as described here ? https://dev.mysql.com/doc/refman/5.5/en/performance-schema-build-configuration.html At least I'm feeling a little more confident about the akonadi-backend-mysql update having triggered this problem. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 352701] Kontact forgets how to download messages
https://bugs.kde.org/show_bug.cgi?id=352701 --- Comment #6 from Nick <nick.craig@gmail.com> --- Interesting regarding the mysql performance schema issue. I do remember doing a very large update prior to this problem that maybe includeded a mysql update. Could the fix have been as simple as running mysql_upgrade as described below ? If you install MySQL over a previous installation that was configured without the Performance Schema (or with an older version of the Performance Schema that may not have all the current tables), run mysql_upgrade after starting the server to ensure that the performance_schema database exists with all current tables. Then restart the server. One indication that you need to do this is the presence of messages such as the following in the error log: [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure ... -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 352701] Kontact forgets how to download messages
https://bugs.kde.org/show_bug.cgi?id=352701 --- Comment #5 from Nick <nick.craig@gmail.com> --- Regarding the native table has the wrong structure error. Here's a link that references this mysql error here https://dev.mysql.com/doc/refman/5.5/en/performance-schema-build-configuration.html -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 352701] Kontact forgets how to download messages
https://bugs.kde.org/show_bug.cgi?id=352701 --- Comment #4 from Nick <nick.craig@gmail.com> --- This fixed it for me .. (until the next time the akonadi database gets corrupted) This involves removing the old akonadi database and letting akonadi construct and reindex a new one. First exit kmail then as normal user akonadi stop mv /home/jbloggs/.local/share/akonadi /home/jbloggs/.local/share/akonadi.orig (This is where akonadi stores it's mysql database) akonadi start You may get the following messages, but then nothing while it's reindexing. akonadictl start Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) nick@nick-X681X:~/.local/share$ /usr/bin/mysqlcheck: Got error: 1049: Unknown database 'akonadi' when selecting the database Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) "No file selected." org.kde.pim.akonadicore: Failed SpecialCollectionsRequestJob::slotResult "Failed to fetch the resource collection." org.kde.pim.maildispatcher: Failed to get outbox folder. Retrying in: 5000 org.kde.pim.akonadicore: Failed to request resource "akonadi_maildir_resource_0" : "Failed to fetch the resource collection." org.kde.pim.akonadicore: Failed SpecialCollectionsRequestJob::slotResult "Failed to fetch the resource collection." org.kde.pim.akonadicore: Failed to request resource "akonadi_maildir_resource_0" : "Failed to fetch the resource collection." org.kde.akonadi.ETM: GEN true false false org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: org.kde.akonadi.ETM: Fetch job took 31 msec org.kde.akonadi.ETM: was collection fetch job: collections: 0 org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: Fetch job took 39 msec org.kde.akonadi.ETM: was collection fetch job: collections: 2 org.kde.akonadi.ETM: first fetched collection: "Search" org.kde.akonadi.ETM: Fetch job took 2 msec org.kde.akonadi.ETM: was collection fetch job: collections: 0 org.kde.akonadi.ETM: GEN true false false org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: org.kde.akonadi.ETM: Fetch job took 39 msec org.kde.akonadi.ETM: was collection fetch job: collections: 0 org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: Fetch job took 42 msec org.kde.akonadi.ETM: was collection fetch job: collections: 2 org.kde.akonadi.ETM: first fetched collection: "Search" org.kde.akonadi.ETM: Fetch job took 1 msec org.kde.akonadi.ETM: was collection fetch job: collections: 0 Pass a valid window to KWallet::Wallet::openWallet(). "Unable to fetch item from backend (collection -1) : Unable to retrieve item from resource: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." To completely reindex akonadi may take a considerable time especially if you have tens of thousands of emails. In my case it's still indexing after an hour. However I can access my emails during this time. looking at the process list with 'top' mysqld shows at 70-95% on my system during this reindexing period. If it all goes ok then remove the backup you made. rm /home/jbloggs/.local/share/akonadi.orig I don't use kontact or any Calendar so can't comment on what will happen to any data you've entered in those apps however if like me you just use kmail then this worked fine. In kmail it retained the various folders and filters I'd created. And it now works without getting the annoying please wait retrieving folder contents. Because I made a backup of the original database I noticed that there were a few mysql errors in the log, reproduced below. In particular the error that stands out is this one (with lots of variations.. but basically native table has the wrong structure. [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure more mysql.err 170915 0:46:57 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB. 170915 0:46:57 [Note] InnoDB: Using mutexes to ref count buffer pool pages 170915 0:46:57 [Note] InnoDB: The InnoDB memory heap is disabled 170915 0:46:57 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 170915 0:46:57 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 170915 0:46:57 [Note] InnoDB: Compressed tables use zlib 1.2.8 170915 0:46:57 [Note] InnoDB: Using Linux native AIO 170915 0:46:57 [Note] InnoDB: Using CPU crc32 instructions 170915 0:46:57 [Note] InnoDB: Initializing buffer pool, size = 128.0M 170915 0:46:57 [Note] InnoDB: Completed initialization of buffer pool 170915 0:46:57 [Note] InnoDB: Highest supported file format is Barracuda.
[kontact] [Bug 352701] Kontact forgets how to download messages
https://bugs.kde.org/show_bug.cgi?id=352701 Nick <nick.craig@gmail.com> changed: What|Removed |Added CC||nick.craig@gmail.com --- Comment #3 from Nick <nick.craig@gmail.com> --- And me, I get this same error. Retrieving folder contents please wait. This bug has been around for years. Kmail/akonadi has been working for me ok for a couple of months but now I just get this inability to read a email. Perhaps it's related to quantity of emails stored that makes it more likely to trigger this bug ? Who knows :-/ In the past I think I've deleted the akonadi database file and configs and started again but it's such a pain to keep doing that. Looking at the logs this seems to be the problem "Cannot connect to agent instance with identifier 'akonadi_maildir_resource_0', error message: ''" -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 381519] remove duplicates options do not work
https://bugs.kde.org/show_bug.cgi?id=381519 Nick <ndor...@gmail.com> changed: What|Removed |Added CC||ndor...@gmail.com --- Comment #2 from Nick <ndor...@gmail.com> --- Same issue Application: kmail (5.6.1) Qt Version: 5.9.1 Frameworks Version: 5.37.0 Operating System: Linux 4.4.85-22-default x86_64 Distribution: "openSUSE Leap 42.3" Get the message "Cannot move message. Unable to retrieve item from resource [ LRCONFLICT ] resource akonadi_maildir_resource_0 tries to modify item 131057() (in collection 738) with dirty payload, aborting STORE . It happens very often, lots of emails are lost . -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 384629] kmail2 crash [ after start, try to open a folder, possibly bad item in non-trash folder ]
https://bugs.kde.org/show_bug.cgi?id=384629 --- Comment #1 from Nick <ndor...@gmail.com> --- Similar to 384606 . The crash happens due to other folder than Trash . In that folder [ XYZ ] there was only an email without the suffix :2,S The same procedure like 384606 [ delete the bad record ] . The contents of that folder is provided below ~/.local/share/akonadi_maildir_resource_0/.inbox.directory/XYZ/cur> clear ~/.local/share/akonadi_maildir_resource_0/.inbox.directory/XYZ/cur> ls -al | wc -l 126 ~/.local/share/akonadi_maildir_resource_0/.inbox.directory/XYZ/cur> ls -al | grep "dom" | wc -l 123 ~/.local/share/akonadi_maildir_resource_0/.inbox.directory/XYZ/cur> ls -al | grep "dom:2," | wc -l 122 ~/.local/share/akonadi_maildir_resource_0/.inbox.directory/XYZ/cur> ls -al | grep dom | grep -v ":2," | wc -l 1 ~/.local/share/akonadi_maildir_resource_0/.inbox.directory/XYZ/cur> ls -al | grep dom | grep -v ":2," -rw-r--r-- 1 rocco users 9114 Sep 12 11:04 1505232271.R262.SuSE4Rocco.dom -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 384629] New: kmail2 crash [ after start, try to open a folder, possibly bad item in non-trash folder ]
https://bugs.kde.org/show_bug.cgi?id=384629 Bug ID: 384629 Summary: kmail2 crash [ after start, try to open a folder, possibly bad item in non-trash folder ] Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ndor...@gmail.com Target Milestone: --- Application: kmail (5.6.1) Qt Version: 5.9.1 Frameworks Version: 5.37.0 Operating System: Linux 4.4.85-22-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: Start kmail2 , it comes up without issues. Try to open a [ not Trash ] folder that indicates new emails, ... Kmail2 crashes immediately ... [ similar to 384606 crash trying to empty Trash] -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3efd28a940 (LWP 6317))] Thread 24 (Thread 0x7f3de983f700 (LWP 6425)): #0 0x7f3efa3d528d in read () at /lib64/libc.so.6 #1 0x7f3eee3dc750 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f3eee39be49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f3eee39c2a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f3eee39c42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f3efaceb13b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f3efac98c2b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f3efaadd02a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f3efaae174d in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #9 0x7f3eefe78744 in start_thread () at /lib64/libpthread.so.0 #10 0x7f3efa3e1aad in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f3dea09f700 (LWP 6424)): #0 0x7f3eefe7d0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3ee4c1c609 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f3ee4c1ce77 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f3ee4c1e230 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f3ee4c1a86d in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f3eefe78744 in start_thread () at /lib64/libpthread.so.0 #6 0x7f3efa3e1aad in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f3e6b8af700 (LWP 6423)): #0 0x7f3eefe7d0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3ee09e3b6b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f3ee09e3b99 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f3eefe78744 in start_thread () at /lib64/libpthread.so.0 #4 0x7f3efa3e1aad in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f3e77fff700 (LWP 6361)): #0 0x7f3efa3d920d in poll () at /lib64/libc.so.6 #1 0x7f3edd9c40a1 in () at /usr/lib64/libpulse.so.0 #2 0x7f3edd9b576c in pa_mainloop_poll () at /usr/lib64/libpulse.so.0 #3 0x7f3edd9b5dde in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7f3edd9b5e90 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7f3edd9c4006 in () at /usr/lib64/libpulse.so.0 #6 0x7f3ed83cf408 in () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #7 0x7f3eefe78744 in start_thread () at /lib64/libpthread.so.0 #8 0x7f3efa3e1aad in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f3e7cff9700 (LWP 6360)): #0 0x7f3eefe7d468 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3ee4c4b7e2 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f3ee4c12f9e in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f3ee4beec18 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f3ee4beaf52 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f3ee4c06998 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f3ee4c1e5b6 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f3ee4c1a86d in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f3eefe78744 in start_thread () at /lib64/libpthread.so.0 #9 0x7f3efa3e1aad in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f3e7d7fa700 (LWP 6359)): #0 0x7f3eefe7d0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3ee5482b5d in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f3ee4c1e230 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f3ee4c1a86d in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f3eefe78744 in start_thread () at /lib64/libpthread.so.0 #5 0x7f3efa3e1aad in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7f3e7dffb700 (LWP 6358)): #0 0x7f3eefe7d0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3ee4c12f0a in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f3ee4c12fc4 in () at
[kmail2] [Bug 384606] kmail2 crash [ right click in Trash ; see contents for 1-2 seconds, then crashed ]
https://bugs.kde.org/show_bug.cgi?id=384606 Nick <ndor...@gmail.com> changed: What|Removed |Added CC||ndor...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 384606] kmail2 crash [ right click in Trash ; see contents for 1-2 seconds, then crashed ]
https://bugs.kde.org/show_bug.cgi?id=384606 --- Comment #1 from Nick <ndor...@gmail.com> --- 1) Something similar was reported via 384525 [ not sure if the backtrace is ok because at that time DrKonki did not collected/find the necessary info ] 2). As in 384525, [ stop akonadi, then I deleted all trash records WITHOUT the suffix :2,[S|PS] . Start akonadi, start kmail, right click on Trash folder, empty the folder woth out any problem. So those pesky records without any suffix is the root cause. Any method of checking the kmail database and fixing those items ? 3). This was the contents of Trash folder [ Immediately after crash ] . /.local/share/akonadi_maildir_resource_0/trash/cur> ls -al total 296 drwxr-xr-x 5 rocco users 4096 Sep 11 18:39 . drwxr-xr-x 5 rocco users 4096 Aug 24 2016 .. -rw-r--r-- 1 rocco users 32246 Sep 11 12:10 1505149858.R651.SuSE4Rocco.dom:2,S -rw-r--r-- 1 rocco users 68833 Sep 11 12:41 1505151673.R461.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 58340 Sep 11 17:48 1505170098.R550.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 54138 Sep 11 17:59 1505170733.R286.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 12350 Sep 11 17:59 1505170734.R431.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 41509 Sep 11 18:04 1505171050.R33.SuSE4Rocco.dom drwxr-xr-x 2 rocco users 4096 Oct 3 2016 cur drwxr-xr-x 2 rocco users 4096 Oct 3 2016 new drwxr-xr-x 2 rocco users 4096 Oct 3 2016 tmp ~/.local/share/akonadi_maildir_resource_0/trash/new> ls -al total 2740 drwxr-xr-x 5 rocco users 4096 Sep 11 19:18 . drwxr-xr-x 5 rocco users 4096 Aug 24 2016 .. -rw-r--r-- 1 rocco users 24033 Sep 11 11:40 1505148047.R723.SuSE4Rocco.dom:2,S -rw-r--r-- 1 rocco users 17063 Sep 11 11:40 1505148048.R291.SuSE4Rocco.dom:2,S -rw-r--r-- 1 rocco users 64953 Sep 11 11:50 1505148650.R310.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 59545 Sep 11 11:50 1505148651.R989.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 8800 Sep 11 12:00 1505149254.R835.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 12802 Sep 11 12:10 1505149858.R784.SuSE4Rocco.dom:2,S -rw-r--r-- 1 rocco users 33851 Sep 11 12:16 1505150161.R955.SuSE4Rocco.dom:2,S -rw-r--r-- 1 rocco users 108129 Sep 11 12:26 1505150766.R257.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 69838 Sep 11 12:31 1505151068.R651.SuSE4Rocco.dom:2,S -rw-r--r-- 1 rocco users 77035 Sep 11 12:36 1505151371.R461.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 20275 Sep 11 12:41 1505151672.R728.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 22433 Sep 11 12:46 1505151975.R751.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 9847 Sep 11 12:51 1505152277.R690.SuSE4Rocco.dom:2,S -rw-r--r-- 1 rocco users 28914 Sep 11 13:01 1505152883.R915.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 9687 Sep 11 13:06 1505153185.R855.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 18760 Sep 11 13:11 1505153487.R599.SuSE4Rocco.dom:2,S -rw-r--r-- 1 rocco users 28600 Sep 11 13:16 1505153791.R200.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 30014 Sep 11 13:16 1505153791.R975.SuSE4Rocco.dom:2,S -rw-r--r-- 1 rocco users 57365 Sep 11 13:46 1505155613.R988.SuSE4Rocco.dom:2,S -rw-r--r-- 1 rocco users 52066 Sep 11 13:56 1505156216.R841.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 8208 Sep 11 14:01 1505156517.R566.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 16392 Sep 11 14:07 1505156819.R541.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 40251 Sep 11 14:17 1505157423.R384.SuSE4Rocco.dom:2,S -rw-r--r-- 1 rocco users 15856 Sep 11 14:32 1505158327.R494.SuSE4Rocco.dom:2,S -rw-r--r-- 1 rocco users 11652 Sep 11 14:37 1505158630.R158.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 133410 Sep 11 14:37 1505158630.R479.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 93268 Sep 11 14:52 1505159535.R703.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 9937 Sep 11 15:02 1505160138.R377.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 133688 Sep 11 15:12 1505160741.R460.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 38249 Sep 11 15:17 1505161044.R985.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 73112 Sep 11 15:42 1505162550.R637.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 11965 Sep 11 16:07 1505164057.R983.SuSE4Rocco.dom:2,S -rw-r--r-- 1 rocco users 87245 Sep 11 16:07 1505164058.R947.SuSE4Rocco.dom:2,S -rw-r--r-- 1 rocco users 57815 Sep 11 16:22 1505164963.R615.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 29529 Sep 11 17:03 1505167378.R562.SuSE4Rocco.dom:2,S -rw-r--r-- 1 rocco users 33966 Sep 11 17:13 1505167982.R799.SuSE4Rocco.dom:2,S -rw-r--r-- 1 rocco users 66991 Sep 11 17:18 1505168288.R31.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 68701 Sep 11 17:33 1505169192.R327.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 43060 Sep 11 17:33 1505169192.R528.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 71616 Sep 11 17:53 1505170410.R529.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 103654 Sep 11 18:09 1505171370.R945.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 87195 Sep 11 18:15 1505171677.R955.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 60602 Sep 11 18:15 1505171678.R124.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 191932 Sep 11 18:30 1505172623.R346.SuSE4Rocco.dom:2,S -rw-r-
[kmail2] [Bug 384606] New: kmail2 crash [ right click in Trash ; see contents for 1-2 seconds, then crashed ]
https://bugs.kde.org/show_bug.cgi?id=384606 Bug ID: 384606 Summary: kmail2 crash [ right click in Trash ; see contents for 1-2 seconds, then crashed ] Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ndor...@gmail.com Target Milestone: --- Application: kmail (5.6.1) Qt Version: 5.9.1 Frameworks Version: 5.37.0 Operating System: Linux 4.4.85-22-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: I intended to empty the Trash . Right click, I saw some entries and immediately crashed. Tried this 2-3 times . The same behaviour. Got the contents of local-trash .. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcd9e7db940 (LWP 18959))] Thread 28 (Thread 0x7fcc85b8f700 (LWP 19286)): #0 0x7fcd913cd468 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fcd8619b7e2 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fcd861714f6 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fcd86171742 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fcd8616a86d in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fcd913c8744 in start_thread () at /lib64/libpthread.so.0 #6 0x7fcd9b931aad in clone () at /lib64/libc.so.6 Thread 27 (Thread 0x7fcc86797700 (LWP 19106)): #0 0x7fcd913cd468 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fcd8619b7e2 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fcd861714f6 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fcd86171742 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fcd8616a86d in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fcd913c8744 in start_thread () at /lib64/libpthread.so.0 #6 0x7fcd9b931aad in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7fcc8a5be700 (LWP 19096)): #0 0x7fcd9b92920d in poll () at /lib64/libc.so.6 #1 0x7fcd8f8ec314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fcd8f8ec42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fcd9c23b13b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fcd9c1e8c2b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fcd9c02d02a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fcd9c03174d in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #7 0x7fcd913c8744 in start_thread () at /lib64/libpthread.so.0 #8 0x7fcd9b931aad in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7fcc8adbf700 (LWP 19095)): #0 0x7fcd913cd0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fcd8616c609 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fcd8616ce77 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fcd8616e230 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fcd8616a86d in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fcd913c8744 in start_thread () at /lib64/libpthread.so.0 #6 0x7fcd9b931aad in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7fcc8b647700 (LWP 19094)): #0 0x7fcd913cd0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fcd8616c609 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fcd8616ce77 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fcd8616e230 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fcd8616a86d in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fcd913c8744 in start_thread () at /lib64/libpthread.so.0 #6 0x7fcd9b931aad in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7fcd0c8e7700 (LWP 19093)): #0 0x7fcd913cd0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fcd81f33b6b in () at /usr/lib64/libQt5Script.so.5 #2 0x7fcd81f33b99 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fcd913c8744 in start_thread () at /lib64/libpthread.so.0 #4 0x7fcd9b931aad in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7fcd19ffb700 (LWP 19007)): #0 0x7fcd7990ea54 in pa_pstream_unref () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #1 0x7fcd7990efc7 in () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #2 0x7fcd7990f84a in () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #3 0x7fcd7ef05a14 in pa_mainloop_dispatch () at /usr/lib64/libpulse.so.0 #4 0x7fcd7ef05dea in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #5 0x7fcd7ef05e90 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #6 0x7fcd7ef14006 in () at /usr/lib64/libpulse.so.0 #7 0x7fcd7991f408 in () at
[kmail2] [Bug 384525] kmail2 crash after I selected something then tried to copy the selected data
https://bugs.kde.org/show_bug.cgi?id=384525 Nick <ndor...@gmail.com> changed: What|Removed |Added CC||ndor...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 384525] kmail2 crash after I selected something then tried to copy the selected data
https://bugs.kde.org/show_bug.cgi?id=384525 --- Comment #1 from Nick <ndor...@gmail.com> --- After the crash the attempt to create the bug [ with yes I know what I was doing at the crash time ] I got a window with the following info : Results of the Analyzed Crash details This report does not contain enough information for the developers, so the automated bug reporting process is not enabled for this crash. If you wish, you can go back and change your answers * The crash information was not generated because it was needed * The information you can provide is not considered helpful enough in this case So I got back and I selected an option only to be able of reporting a crash . Is it any way of Fixing DrKonqi to accept ANY crash that happened . It seems that DrKonqi classifies crashes in the good and bad one. Due to that classification, the bad crashes are not reported because the users are frustrated by the implication that the crash happened but the automaton DrKonqi is not smart enough to find out WHY the crash happened . As a user I am at loss because many times in the past I cancelled the bug reporting . Lately kmail2 behaves strangely crashing when running under kontact or by itself The crashes are so often that all debuginfo packages [ akonadi, kmail, kontact,kdepim ] are activated . The crashes are very frequent and initiated from different angles : 1) crash due to "empty trash" Yesterday I tried to create a bug the same window described above ... select trash folder with the intent to empty it it crashed . After that I analyzed what was in the trash . See below ~/.local/share/akonadi_maildir_resource_0/trash/cur> ls -al * -rw-r--r-- 1 rocco users 75599 Sep 8 12:51 1504893060.R32.SuSE4Rocco.dom:2,S -rw-r--r-- 1 rocco users 71433 Sep 8 12:51 1504893061.R374.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 53269 Sep 8 12:51 1504893061.R62.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 49224 Sep 8 12:51 1504893061.R892.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 34680 Sep 8 12:51 1504893061.R937.SuSE4Rocco.dom -rw-r--r-- 1 rocco users 68641 Sep 8 12:51 1504893063.R226.SuSE4Rocco.dom I noticed that in other folders all items are in format nn.R[rr|rrr].SuSe4Rocco.dom:2,S or nn.R[rr|rrr].SuSe4Rocco.dom:2,PS So, I did i) stop akonadictl ii) delete all trash items without the suffix :2,[S|PS] iii) start akonadictl iv) stat kmail2 v) go to trash, see what it is in it [ only one item !!! ] vi) go back select trash folder select empty done. 2) crash due to "remove duplicated" Similar to item 1). above . go to the "problem" folder check the cur/new/tmp to see its contents I found many of items without the suffix :2,[S|PS] delete them . voila the kmail behave properly till another special crash happens 3) move to trash is not complete In some folders I want to select unread then after analyzing them [ subject, from, etc ] it I want to delete all of them . edit+select all messages sometimes works sometimes select all messages is greyed out . That is the signal that there is at least an item that does not have the magic suffix :2,[PS|S] . Then I apply the same method even if some emails are lost [ Again DrKonqi is not impress with the crash ] 4) select some messages and use Move to trash . Some of them are grayed out ---> another angle of missing the suffix Select one of them .. crash . DrKonqi is not impress 5) If kmail2 is running under kontact, DrKonqi reports kontact as the culprit ... So I stopped running kmail2 under kontact to make sure that the crashes are created by hmail2 . Questions : 1) Is there any method of verifying the kmail database [ in opensuse MariaDB ] 2) Although some of kde help indicates that after akonadictl stop , with the exception of "grep --color=auto mysql", you should not see any output from ps -ux | grep mysql That's not the case . How is it possible to stop akonadi database ? 3) in the same category kquitapp kmail | kontact does not work . 4) is there any procedure of eliminating all bad items OR fixing the responsible agent of making sure that they correctly process the emails we receive . 5) There are many KDE repos . Is there any web page that explains what repos should be used . There are so many Qt5, Qt5.x, LTS, KF5, etc . 6) Many times after a maintenance/upgrade there are crashes due to the mismatch in akonadi [ some agents fail to start ] but they are seen as kmail2 crash . In 384286 it was a "knotact/kmail" but the root cause what akonadi failures . Is it possible to have an akonadi crash rather than pointing to kmail2 having agents offline ? Is it possible to enhance the pre-requisites, co-requisites of packaging to stop installing conflicting packages ? I hope that KDE team will come with some solutions/answers/fixes soon . Thank you for your help and support . Nick -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 384525] New: kmail2 crash after I selected something then tried to copy the selected data
https://bugs.kde.org/show_bug.cgi?id=384525 Bug ID: 384525 Summary: kmail2 crash after I selected something then tried to copy the selected data Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ndor...@gmail.com Target Milestone: --- Application: kmail (5.6.1) Qt Version: 5.9.1 Frameworks Version: 5.37.0 Operating System: Linux 4.4.85-22-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: " I selected something then tried to copy the selected data " -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f68d8268940 (LWP 1675))] Thread 28 (Thread 0x7f67be657700 (LWP 1812)): #0 0x7f68cae5b468 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f68bfc297e2 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f68bfbff4f6 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f68bfbff742 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f68bfbf886d in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f68cae56744 in start_thread () at /lib64/libpthread.so.0 #6 0x7f68d53bfaad in clone () at /lib64/libc.so.6 Thread 27 (Thread 0x7f67bee58700 (LWP 1811)): #0 0x7f68cae5b468 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f68bfc297e2 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f68bfbff4f6 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f68bfbff742 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f68bfbf886d in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f68cae56744 in start_thread () at /lib64/libpthread.so.0 #6 0x7f68d53bfaad in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7f67c47e4700 (LWP 1757)): #0 0x7f68c93bb8b4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f68c937a223 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f68c937a42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f68d5cc913b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f68d5c76c2b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f68d5abb02a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f68d5abf74d in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #7 0x7f68cae56744 in start_thread () at /lib64/libpthread.so.0 #8 0x7f68d53bfaad in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7f67c4fe5700 (LWP 1756)): #0 0x7f68cae5b0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f68bfbfa609 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f68bfbfae77 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f68bfbfc230 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f68bfbf886d in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f68cae56744 in start_thread () at /lib64/libpthread.so.0 #6 0x7f68d53bfaad in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f6846795700 (LWP 1755)): #0 0x7f68cae5b0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f68bb9c1b6b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f68bb9c1b99 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f68cae56744 in start_thread () at /lib64/libpthread.so.0 #4 0x7f68d53bfaad in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f68577fe700 (LWP 1711)): #0 0x7f68d53b328d in read () at /lib64/libc.so.6 #1 0x7f68b337e931 in pa_read () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #2 0x7f68b89933be in pa_mainloop_prepare () at /usr/lib64/libpulse.so.0 #3 0x7f68b8993dd2 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7f68b8993e90 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7f68b89a2006 in () at /usr/lib64/libpulse.so.0 #6 0x7f68b33ad408 in () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #7 0x7f68cae56744 in start_thread () at /lib64/libpthread.so.0 #8 0x7f68d53bfaad in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f6857fff700 (LWP 1710)): #0 0x7f68cae5b468 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f68bfc297e2 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f68bfbf0f9e in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f68bfbccc18 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f68bfbc8f52 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f68bfbe4998 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f68bfbfc5b6 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7
[kontact] [Bug 384286] mail dispacher is ofline so mails can not be sent
https://bugs.kde.org/show_bug.cgi?id=384286 Nick <ndor...@gmail.com> changed: What|Removed |Added CC||ndor...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 384286] mail dispacher is ofline so mails can not be sent
https://bugs.kde.org/show_bug.cgi?id=384286 --- Comment #1 from Nick <ndor...@gmail.com> --- Hello, I just analyzed the messages displayed by akonadictl start and I noticed that all agents that were not able to start failed due to some mismatch between kmai and kdepim . Kmail was at 17.08.0 whereas kdepim was at 17.04.2 level. After fixing the ver issue everything look fine . The messages are provided below. Could you please direct me to some kde page that describes the different repos available to us the users. Also how is it possible to get installed packages that are conflicting between them . Is this due to packaging ? AS far as I ma concerned this ticket can be closed . Thank you , Nick -- akonadictl start messages . akonadictl start Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) akonadi.collectionattributetable OK akonadi.collectionmimetyperelation OK akonadi.collectionpimitemrelation OK akonadi.collectiontableOK akonadi.flagtable OK akonadi.mimetypetable OK akonadi.parttable OK akonadi.parttypetable OK akonadi.pimitemflagrelationOK akonadi.pimitemtable OK akonadi.pimitemtagrelation OK akonadi.relationtable OK akonadi.relationtypetable OK akonadi.resourcetable OK akonadi.schemaversiontable OK akonadi.tagattributetable OK akonadi.tagremoteidresourcerelationtable OK akonadi.tagtable OK akonadi.tagtypetable OK Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) /usr/bin/akonadi_akonotes_resource: symbol lookup error: /usr/bin/akonadi_akonotes_resource: undefined symbol: _ZN7Akonadi3Job16doHandleResponseExRKNS_8Protocol7CommandE /usr/bin/akonadi_maildir_resource: symbol lookup error: /usr/bin/akonadi_maildir_resource: undefined symbol: _ZN7Akonadi3Job16doHandleResponseExRKNS_8Protocol7CommandE /usr/bin/akonadi_maildispatcher_agent: symbol lookup error: /usr/bin/akonadi_maildispatcher_agent: undefined symbol: _ZN7Akonadi3Job16doHandleResponseExRKNS_8Protocol7CommandE /usr/bin/akonadi_migration_agent: symbol lookup error: /usr/bin/akonadi_migration_agent: undefined symbol: _ZN7Akonadi3Job16doHandleResponseExRKNS_8Protocol7CommandE org.kde.pim.akonadicontrol: ProcessControl: Application '/usr/bin/akonadi_akonotes_resource' returned with exit code 127 (Unknown error) org.kde.pim.akonadicontrol: ProcessControl: Application '/usr/bin/akonadi_maildir_resource' returned with exit code 127 (Unknown error) org.kde.pim.akonadicontrol: ProcessControl: Application '/usr/bin/akonadi_maildispatcher_agent' returned with exit code 127 (Unknown error) org.kde.pim.akonadicontrol: ProcessControl: Application '/usr/bin/akonadi_migration_agent' returned with exit code 127 (Unknown error) /usr/bin/akonadi_akonotes_resource: symbol lookup error: /usr/bin/akonadi_akonotes_resource: undefined symbol: _ZN7Akonadi3Job16doHandleResponseExRKNS_8Protocol7CommandE org.kde.pim.akonadicontrol: ProcessControl: Application '/usr/bin/akonadi_akonotes_resource' returned with exit code 127 (Unknown error) /usr/bin/akonadi_migration_agent: symbol lookup error: /usr/bin/akonadi_migration_agent: undefined symbol: _ZN7Akonadi3Job16doHandleResponseExRKNS_8Protocol7CommandE /usr/bin/akonadi_maildir_resource: symbol lookup error: /usr/bin/akonadi_maildir_resource: undefined symbol: _ZN7Akonadi3Job16doHandleResponseExRKNS_8Protocol7CommandE org.kde.pim.akonadicontrol: ProcessControl: Application '/usr/bin/akonadi_maildir_resource' returned with exit code 127 (Unknown error) org.kde.pim.akonadicontrol: ProcessControl: Application '/usr/bin/akonadi_migration_agent' returned with exit code 127 (Unknown error) /usr/bin/akonadi_maildispatcher_agent: symbol lookup error: /usr/bin/akonadi_maildispatcher_agent: undefined symbol: _ZN7Akonadi3Job16doHandleResponseExRKNS_8Protocol7CommandE org.kde.pim.akonadicontrol: ProcessControl: Application '/usr/bin/akonadi_maildispatcher_agent' returned with exit code 127 (Unknown error) /usr/bin/akonadi_akonotes_resource: symbol lookup error: /usr/bin/akonadi_akonotes_resource: undefined symbol: _ZN7Akonadi3Job16doHandleResponseExRKNS_8Protocol7CommandE org.kde.pim.akonadicontrol: ProcessControl: Application '/usr/bin/akonadi_akonotes_resource' returned with exit code 127 (Unknown error) /usr/bin/akonadi_migration_agent: symbol lookup error: /usr/bin/akonadi_migration_agent: undefined symbol: _ZN7Akonadi3Job16doHandleResponseExRKNS_8Protocol7CommandE org.kde.pim.akonadicontrol: ProcessControl: Application '/u
[kontact] [Bug 384286] New: mail dispacher is ofline so mails can not be sent
https://bugs.kde.org/show_bug.cgi?id=384286 Bug ID: 384286 Summary: mail dispacher is ofline so mails can not be sent Product: kontact Version: 5.6.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ndor...@gmail.com Target Milestone: --- Application: kontact (5.6.0) Qt Version: 5.9.1 Frameworks Version: 5.37.0 Operating System: Linux 4.4.79-19-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: -System Opensuse Leap 42.3 After upgrade from Leap 42.2 Kontact starts but kmail reports "Mail dispatcher is offline so mails can not be sent " in config kmail the account is ready the maildir : unable to start [ Trying to restrat it does nothing] The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb52250e780 (LWP 8494))] Thread 25 (Thread 0x7fb3f48c4700 (LWP 8743)): #0 0x7fb5190128b4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fb518fd11cd in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb518fd142c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb51fa8013b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb51fa2dc2b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb51f87202a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fb51f87674d in () at /usr/lib64/libQt5Core.so.5 #7 0x7fb51aed5744 in start_thread () at /lib64/libpthread.so.0 #8 0x7fb51ef5eaad in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7fb41729b700 (LWP 8536)): #0 0x7fb518fd0d8d in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #1 0x7fb518fd12a8 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb518fd142c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb51fa8013b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb51fa2dc2b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb51f87202a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fb51f87674d in () at /usr/lib64/libQt5Core.so.5 #7 0x7fb51aed5744 in start_thread () at /lib64/libpthread.so.0 #8 0x7fb51ef5eaad in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7fb417a9c700 (LWP 8535)): #0 0x7fb51ef5228d in read () at /lib64/libc.so.6 #1 0x7fb519011750 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb518fd0e49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb518fd12a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fb518fd142c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fb51fa8013b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fb51fa2dc2b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fb51f87202a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7fb51f87674d in () at /usr/lib64/libQt5Core.so.5 #9 0x7fb51aed5744 in start_thread () at /lib64/libpthread.so.0 #10 0x7fb51ef5eaad in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7fb418924700 (LWP 8534)): #0 0x7fb51ef5620d in poll () at /lib64/libc.so.6 #1 0x7fb518fd1314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb518fd142c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb51fa8013b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb51fa2dc2b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb51f87202a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fb51f87674d in () at /usr/lib64/libQt5Core.so.5 #7 0x7fb51aed5744 in start_thread () at /lib64/libpthread.so.0 #8 0x7fb51ef5eaad in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7fb4a3003700 (LWP 8530)): #0 0x7fb51aeda0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb509700b6b in () at /usr/lib64/libQt5Script.so.5 #2 0x7fb509700b99 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fb51aed5744 in start_thread () at /lib64/libpthread.so.0 #4 0x7fb51ef5eaad in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7fb4a3804700 (LWP 8527)): #0 0x7fb51aeda0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb50fde1609 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fb50fde1e77 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fb50fde3230 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fb50fddf86d in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fb51aed5744 in start_thread () at /lib64/libpthread.so.0 #6
[kmail2] [Bug 382216] Lots of old emails [ days, weeks ] are received over and over again even if they are deleted/moved to trash
https://bugs.kde.org/show_bug.cgi?id=382216 --- Comment #2 from Nick <ndor...@gmail.com> --- Created attachment 106561 --> https://bugs.kde.org/attachment.cgi?id=106561=edit BugID-383216_A view at the email types I have to deal with.txt Counts of the amount of old emails I receive , mostly of them older than one week the majority if them from June 2017 . -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 382216] Lots of old emails [ days, weeks ] are received over and over again even if they are deleted/moved to trash
https://bugs.kde.org/show_bug.cgi?id=382216 Nick <ndor...@gmail.com> changed: What|Removed |Added CC||ndor...@gmail.com --- Comment #1 from Nick <ndor...@gmail.com> --- Created attachment 106546 --> https://bugs.kde.org/attachment.cgi?id=106546=edit akonadictl_status_fsck_vacuum_restart.txt -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 382216] New: Lots of old emails [ days, weeks ] are received over and over again even if they are deleted/moved to trash
https://bugs.kde.org/show_bug.cgi?id=382216 Bug ID: 382216 Summary: Lots of old emails [ days, weeks ] are received over and over again even if they are deleted/moved to trash Product: kmail2 Version: 5.5.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: ndor...@gmail.com Target Milestone: --- Created attachment 106544 --> https://bugs.kde.org/attachment.cgi?id=106544=edit kmail-related-packages-installed.txt Hello, I use opensuse leap 42.2 with kde , kmail2, plasma5, kontact, akonadi, mariadb . uname -a Linux .dom 4.4.74-18.20-default #1 SMP Fri Jun 30 19:01:19 UTC 2017 (b5079b8) x86_64 x86_64 x86_64 GNU/Linux The levels of kmail, akonadi... packages are provided in one of the attachments. For several week I noticed that some emails are received again even if they are deleted/moved to trash and the settings of account is set to not keeping emails longer than 7 days . In the last 2 weeks the issue has become more annoying . Yesterday I applied the latest maintenance available via zypper up and it touched the kmail, akonadi packages . After rebooting the machine I start receiving hundreds of emails with date back to 10-June-2017 . I thought that id they are moved to trash that will stop . I was mistaken ... they appeared again and again regardless if the emails were moved to trash or simply deleted . To alleviate this aggravation I created a filter to direct all emails with date before July 7 2017 into a new folder . All other filters which started receiving some where from 10 to 80/90 emails were changed to direct the emails in the above described folder . akonadictl fsck and/or vacuum has no effect on this issue . I noticed hundreds of lines " Item .. has no RID " . akonadictl listings are provided below because I was able to attach only one attachment . Questions : 1. Is there any way to check the mysql [ i.e. maridb ] database used by kmail2 ? If there is , could you please give me some info/procedures ? 2). How could I get rid of all those "Item . has no RID." ? Is it possible ? 3). It seems that potentially the existing database id toasted . What would be the procedure for a) full backup of the existing kmail2/akonadi environment b) total removal of the existing kmail2/akonadi environment c) creating a brand new kmail2/akonadi env d) migrating the emails from the backup (a) to the new env . I hope that there are some "kmail/akonadi/mariadb" solutions . Thank you, Nick Dordea - akonadictl_status_fsck_vacuum_restart.txt <user@hostname>:~> akonadictl status Akonadi Control: running Akonadi Server: running Akonadi Server Search Support: available (Remote Search) Available Agent Types: akonadi_akonotes_resource, akonadi_archivemail_agent, akonadi_birthdays_resource, akonadi_contacts_resource, akonadi_davgroupware_resource, akonadi_followupreminder_agent, akonadi_googlecalendar_resource, akonadi_googlecontacts_resource, akonadi_ical_resource, akonadi_icaldir_resource, akonadi_imap_resource, akonadi_indexing_agent, akonadi_invitations_agent, akonadi_kalarm_dir_resource, akonadi_kalarm_resource, akonadi_knut_resource, akonadi_kolab_resource, akonadi_maildir_resource, akonadi_maildispatcher_agent, akonadi_mailfilter_agent, akonadi_mbox_resource, akonadi_migration_agent, akonadi_mixedmaildir_resource, akonadi_newmailnotifier_agent, akonadi_notes_agent, akonadi_notes_resource, akonadi_openxchange_resource, akonadi_pop3_resource, akonadi_sendlater_agent, akonadi_tomboynotes_resource, akonadi_vcard_resource, akonadi_vcarddir_resource You have new mail in /var/spool/mail/ <user@hostname>:~> akonadictl fsck Looking for resources in the DB not matching a configured resource... Looking for collections not belonging to a valid resource... Checking collection tree consistency... Looking for items not belonging to a valid collection... Looking for item parts not belonging to a valid item... Looking for item flags not belonging to a valid item... Looking for overlapping external parts... Verifying external parts... Found 1554 external files. Cleaning up missing external file: /home//.local/share/akonadi/file_db_data/85/311685_r0 for item: 79413 on part: 311685 Found 1550 external parts. Found unreferenced external file: /home//.local/share/akonadi/file_db_data/06/313706_r1 Found unreferenced external file: /home//.local/share/akonadi/file_db_data/35/314735_r3 Found unreferenced external file: /home//.local/share/akonadi/file_db_data/85/311685_r1 Found unreferenced external file: /home//.local/share/akonadi/file_db_data/23/330323_r1 Moved 4 unreferenced files to lost+found. Checking size treshold changes... Found 0 parts to b
[kmail2] [Bug 381955] kmail hangs or causes desktop to hang when used with Nouveau graphics driver
https://bugs.kde.org/show_bug.cgi?id=381955 --- Comment #1 from Nick <nick.craig@gmail.com> --- Created attachment 106431 --> https://bugs.kde.org/attachment.cgi?id=106431=edit syslog output when kmail 5.5.2 causes kmail/desktop to hang -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 381955] New: kmail hangs or causes desktop to hang when used with Nouveau graphics driver
https://bugs.kde.org/show_bug.cgi?id=381955 Bug ID: 381955 Summary: kmail hangs or causes desktop to hang when used with Nouveau graphics driver Product: kmail2 Version: 5.5.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: nick.craig@gmail.com Target Milestone: --- System Config, KDE Neon LTS 5.8.7, Nouveau driver. Nvidia GeForce GTX570M, kmail 5.5.2. Kmail will become unresponsive when attempting to scroll or click left on an email. Sometimes just the controls/buttons in kmail will be unreponsive but sometimes the whole desktop will become unreponsive and freeze, requiring a ALT-SYSRq RSEIUB command to reboot system, ALT-F1 not working. If instead I use the Nvidia 375 driver the problem disappears, so this problem seems to be related to the use of the Nouveau driver. syslog reports the following errors.. Jul 2 23:02:30 nick-X681X kernel: [12787.488155] nouveau :01:00.0: kmail[8229]: Unknown handle 0x002c Jul 2 23:02:30 nick-X681X kernel: [12787.488159] nouveau :01:00.0: kmail[8229]: validate_init Jul 2 23:02:30 nick-X681X kernel: [12787.488161] nouveau :01:00.0: kmail[8229]: validate: -2 Jul 2 23:02:33 nick-X681X kernel: [12790.327435] nouveau :01:00.0: gr: TRAP ch 17 [005f1f4000 kmail[8229]] Jul 2 23:02:33 nick-X681X kernel: [12790.327448] nouveau :01:00.0: gr: GPC0/TPC0/TEX: 8041 Jul 2 23:02:33 nick-X681X kernel: [12790.327456] nouveau :01:00.0: gr: GPC0/TPC1/TEX: 8041 Jul 2 23:02:33 nick-X681X kernel: [12790.327464] nouveau :01:00.0: gr: GPC0/TPC2/TEX: 8041 Jul 2 23:02:33 nick-X681X kernel: [12790.327472] nouveau :01:00.0: gr: GPC0/TPC3/TEX: 8041 Jul 2 23:02:33 nick-X681X kernel: [12790.327481] nouveau :01:00.0: gr: GPC1/TPC0/TEX: 8041 Jul 2 23:02:33 nick-X681X kernel: [12790.327489] nouveau :01:00.0: gr: GPC1/TPC1/TEX: 8041 Jul 2 23:02:33 nick-X681X kernel: [12790.327498] nouveau :01:00.0: gr: GPC1/TPC2/TEX: 8041 Jul 2 23:02:33 nick-X681X kernel: [12790.327513] nouveau :01:00.0: fifo: read fault at 0002a0a000 engine 00 [PGRAPH] client 01 [GPC1/TEX] reason 02 [PAGE_NOT_PRESENT] on channel 17 [005f1f4000 kmail[8229]] Jul 2 23:02:33 nick-X681X kernel: [12790.327516] nouveau :01:00.0: fifo: gr engine fault on channel 17, recovering... Jul 2 23:03:33 nick-X681X kernel: [12850.755747] nouveau :01:00.0: kmail[8229]: failed to idle channel 17 [kmail[8229]] Jul 2 23:03:48 nick-X681X kernel: [12865.757800] nouveau :01:00.0: kmail[8229]: failed to idle channel 17 [kmail[8229]] It also generates a second different error on some occasions ie a FIFO read fault at 0001afa00 engine 00 [PGRAPH] client 01 [GPC1/TEX] reason 02 [Page not present] on channel 5. This error tends to hang the entire desktop, hence why I have attached a photo of the tail -f /var/log/syslog output. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 379955] kontact 17.04.0-19.5 fails to start lmail client 17.04.0.25.5 due to undefined symbols
https://bugs.kde.org/show_bug.cgi?id=379955 --- Comment #3 from Nick <ndor...@gmail.com> --- Could you please give me an email for the distro problem ? Thanks - However , it seems that the KDE packaging is the issue . After I did some checking of the versions of the KDE/akonadi/libKF5 components and updating them [ manually ! ] to be at the same level I got the kontact working again . Here is what I've done .. Continued to check [ via yast ] some version between different components like kleopatra5 16.08.2.-1.1 libkleo 17.04.1-47.1 then upgrade to kleopatra 17.04.1-21.1 which triggered the upgrade kleopatra-lang 17.04.1-21.1 I discovered many more in the same category . All point to KDE packaging . I use Software Update" wizard to get notifications when updates are available. Then , I use sudo zypper -up l to updatae/upgrade my machine . It is supposed that the zypper resolves the inter-packages relationships and selects the packages that match those relationships . Explaining why kleopatra remains at 16.8 level while libkleo is upgraded to 17.04 point to the correctness of inter-packages relationships' definitions . I noticed that some undefined symbols were resolved and another new ones were the new culprits [ mainly in libKF5* packages ] . I continued with this process until both kontact/kmail failed without displying an error window . Starting them from konsole gave the below symptmos . that point now to akonadi ! The messages are provided at the end of this file. I did the same thing, as above, for akonadi [ some packages were at 16.8 other at 17.04 ] and I got allmost of them to 17.04 version . After many yast updates finally I got kontact stating as before . ps -ef | grep kontact 1028 4647 0 15:44 ?00:00:00 http.so [kdeinit5] http local:/run/user/1000/klauncherTJ4648.1.slave-socket local:/run/user/1000/kontactP28986.5.slave-socket 1029 4647 0 15:44 ?00:00:00 http.so [kdeinit5] http local:/run/user/1000/klauncherTJ4648.1.slave-socket local:/run/user/1000/kontactV28986.6.slave-socket 1031 4647 0 15:44 ?00:00:00 http.so [kdeinit5] http local:/run/user/1000/klauncherTJ4648.1.slave-socket local:/run/user/1000/kontactM28986.7.slave-socket 1033 4647 0 15:44 ?00:00:00 http.so [kdeinit5] http local:/run/user/1000/klauncherTJ4648.1.slave-socket local:/run/user/1000/kontactr28986.8.slave-socket 1038 4647 0 15:44 ?00:00:00 http.so [kdeinit5] http local:/run/user/1000/klauncherTJ4648.1.slave-socket local:/run/user/1000/kontactb28986.9.slave-socket 1039 4647 0 15:44 ?00:00:00 http.so [kdeinit5] http local:/run/user/1000/klauncherTJ4648.1.slave-socket local:/run/user/1000/kontactf28986.10.slave-socket 1052 4647 0 15:44 ?00:00:00 http.so [kdeinit5] https local:/run/user/1000/klauncherTJ4648.1.slave-socket local:/run/user/1000/kontactg28986.11.slave-socket 1055 4647 0 15:44 ?00:00:00 http.so [kdeinit5] https local:/run/user/1000/klauncherTJ4648.1.slave-socket local:/run/user/1000/kontactz28986.12.slave-socket 28986 4647 0 15:20 ?00:00:14 /usr/bin/kontact <uname@hostname>:~> kontact [0518/104345:ERROR:nss_util.cc(839)] After loading Root Certs, loaded==false: NSS error code: -8018 org.kde.pim.webengineviewer: It's not necessary to check database now org.kde.akonadi.ETM: GEN true false false org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: org.kde.pim.webengineviewer: Database already initialized. It's a bug in code if you call it twice. "Tag 'a' is not defined in message {<__kuit_internal_top__>For more information about using Akregator, check the For more information about using Akregator, check the KMail has many powerful features that are described in th...}." "Tag 'br' is not defined in message {<__kuit_internal_top__>Thank you,The KMail Team}." kontact: symbol lookup error: /usr/lib64/libKF5LibkdepimAkonadi.so.5: undefined symbol: _ZNK4KPIM15ProgressManager12progressItemERK7QString <uname@hostname>:~> kmail Pass a valid window to KWallet::Wallet::openWallet(). org.kde.pim.webengineviewer: It's not necessary to check database now [0518/104422:ERROR:nss_util.cc(839)] After loading Root Certs, loaded==false: NSS error code: -8018 this does not work on a KActionCollection containing actions! org.kde.akonadi.ETM: GEN true false false org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: "Tag 'a' is not defined in message {<__kuit_internal_top__>KMail has many powerful features that are described in th...}." "Tag 'br' is not defined in message {<__kuit_internal_top__>Thank you,The KMail Team}." kmail: symbol lookup error: /usr/lib64_ZNK4KPIM15ProgressManager12progressItemERK7QString/libKF5LibkdepimAkonadi.so.5: undefined symbol: _ZNK4KPIM15ProgressManager12progressItemERK7QString -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 379955] kontact 17.04.0-19.5 fails to start lmail client 17.04.0.25.5 due to undefined symbols
https://bugs.kde.org/show_bug.cgi?id=379955 --- Comment #1 from Nick <ndor...@gmail.com> --- The full error message is as follows : Can not load part for Mail Can not load library /usr/lib64/qt5/plugins/kmailpart.so ( libKF5MessageViewer.so.5 undefined symbol _ZTIN13Transport1 error ) 2nd test pointed to another undefined symbol /usr/lib64/libkmailprivate.so.5 undefined symbol _ZTIN3kleo17KeySelectionComboE I noticed that many of libKF% entries in yast were pointining to version 16 rather than 17 . I upgraded those at level 16 to their equivalent in ver 17 shutdown / restart I got a different symbol /usr/lib64/libkmailprivate.so.5 undefined symbol _ZN10MailCommon24FavoriteCollectionWidget15NewTabRequestedEb Checked /usr/lib64/libkmailprivate.so.5 it is a link ls -al /usr/lib64/libkmailprivate.so.5 lrwxrwxrwx 1 root root 24 May 17 13:21 /usr/lib64/libkmailprivate.so.5 -> libkmailprivate.so.5.5.0 Thanks Nick -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 379955] New: kontact 17.04.0-19.5 fails to start lmail client 17.04.0.25.5 due to undefined symbols
https://bugs.kde.org/show_bug.cgi?id=379955 Bug ID: 379955 Summary: kontact 17.04.0-19.5 fails to start lmail client 17.04.0.25.5 due to undefined symbols Product: kontact Version: 5.5.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ndor...@gmail.com Target Milestone: --- Application: kontact (5.5.0) Qt Version: 5.7.1 Frameworks Version: 5.34.0 Operating System: Linux 4.4.62-18.6-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - After did a maintenance via zypper up -l, among other things , kontact5 was upgraded to kontact 17.04.0.19.5 and kmail5 was upgraded to kmail 17.04.0.25.5 . zypper ps -s indicated that many appl should be restarted . After shutdown / restart when I tried to start kcontact [ that starts kmail ] failed with the message : /usr/lib64/qt5/plugins/kmailpart.so ( libKF5MessageViewer.so.5 undefined symbol _ZTIN13Transport1 error ) Environmental info : Operating system openSuSE Leap 42.2 kontact 17.04.0-19.5 kmail 17.04.0-25.5 libKF5MessageViewer.so.5 part of messagelib 16.08.3-19.1 Using yast I noticed that there is another messagelib available 17.04.0-45.2 message lib was upgraded to 17.04. version [ same as messagelib_lang !!! ] After update. shutdown/restart Try again to start kontact .. it fails again by the symptom is changed .. The new message points to /usr/lib64/libkmailprivate.so.5 undefined symbol _ZTIN3kleo17KeySelectionComboE It is clear that we have an issue with uncomplete and/or contradictory packaging . After replying OK to app icons displaying the above message ] kontact failed Please note that the maintenamce methos is exclusively based on rpm . Please let me know if you have any other questions and/or info . Thank you for your help. Nick The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2bab6577c0 (LWP 23152))] Thread 24 (Thread 0x7f2a8213f700 (LWP 23233)): #0 0x7f2ba3fed0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2b9b09bfb9 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f2b9b09c739 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f2b9b09cf40 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f2b9b0999ac in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f2ba3fe8744 in start_thread () at /lib64/libpthread.so.0 #6 0x7f2ba8129d3d in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f2a8823e700 (LWP 23232)): #0 0x7f2ba3fed0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2b9b09bfb9 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f2b9b09c739 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f2b9b09cf40 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f2b9b0999ac in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f2ba3fe8744 in start_thread () at /lib64/libpthread.so.0 #6 0x7f2ba8129d3d in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f2a898eb700 (LWP 23206)): #0 0x7f2ba1eb57d4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f2ba1e739e8 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2ba1e74230 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2ba1e7442c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f2ba8c469eb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2ba8bf62db in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f2ba8a3bfca in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f2ba8a407f9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f2ba3fe8744 in start_thread () at /lib64/libpthread.so.0 #9 0x7f2ba8129d3d in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f2b2ddbf700 (LWP 23192)): #0 0x7f2ba3fed0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2b94f53acb in () at /usr/lib64/libQt5Script.so.5 #2 0x7f2b94f53af9 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f2ba3fe8744 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2ba8129d3d in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f2b2efee700 (LWP 23188)): #0 0x7f2ba3fed0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2b9ab8fa70 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f2b9ab79b48 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f2b9ab79be7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f2b9ab75a2a in () at /usr/lib64/libQt5WebEngineCore.so.5 #5
[kmail2] [Bug 372973] missing Help handbook
https://bugs.kde.org/show_bug.cgi?id=372973 --- Comment #8 from Nick Levinson <nick_levin...@yahoo.com> --- I'm following up other there: https://bugzilla.opensuse.org/show_bug.cgi?id=1018970 Thank you for your work. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372973] missing Help handbook
https://bugs.kde.org/show_bug.cgi?id=372973 --- Comment #6 from Nick Levinson <nick_levin...@yahoo.com> --- GUI/CLI followup (especially @Burkhard Lueck): Apparently, KHelpCenter is available but only through a command line interface (https://forums.opensuse.org/showthread.php/391430-Khelpcenter-for-OpenSuSE-where-do-I-find-it?p=1848523#post1848523) or the KDE Plasma Workspace (one graphical user interface), not the Gnome or IceWM desktop environment GUIs. I asked about the CLI preference at a forum (https://forums.opensuse.org/showthread.php/521603-why-need-CLI-console-to-use-GUI-KMail-Help?p=2803654#post2803654) before I knew it worked in KDE's DE but no one replied. Why isn't KHelpCenter working in whatever GUI desktop environment we happen to be using? Are you getting it in any GUI other than KDE? If not, then this may need an enhancement request somewhere, probably first within KDE to make KHelpCenter compatible with a competitor's GUI. An alternative would be a message that, instead of saying essentially that we can't use the help, would say to switch DEs. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372973] missing Help handbook
https://bugs.kde.org/show_bug.cgi?id=372973 --- Comment #5 from Nick Levinson <nick_levin...@yahoo.com> --- I didn't remove it, as far as I know. I install everything in a distro, even stuff I don't want, specifically to preclude any dependency failure. I can ask a forum about why it might be missing. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 323455] "Filter account is missing" after KMail startup
https://bugs.kde.org/show_bug.cgi?id=323455 Nick <futurepi...@gmx.us> changed: What|Removed |Added CC||futurepi...@gmx.us -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372976] dialog's editorial confusion on password storage
https://bugs.kde.org/show_bug.cgi?id=372976 --- Comment #2 from Nick Levinson <nick_levin...@yahoo.com> --- No, the first two sentences need editing. No objection to the edit you propose, but it still leaves the first two sentences in conflict with each other. Would deleting the second sentence from the original text mean that the remaining text (with your edit) would accurately describe the facts and the options for the user? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372974] need to see dialog's bottom buttons
https://bugs.kde.org/show_bug.cgi?id=372974 --- Comment #3 from Nick Levinson <nick_levin...@yahoo.com> --- My screen is 768 pixels high. I don't remember another app having this effect. Regardless, 768 is not very short, the fonts are not unusually large, and the title bar hardly seems big enough to account for the buttons at the bottom being entirely out of view so as to force users to guess. Not all users are geeks. Even if we were using a cell phone's browser, the buttons or other indicia of equivalent functionality should be visible to users. -- You are receiving this mail because: You are the assignee for the bug.