[kile] [Bug 491899] regression 2.9.94: --line option no longer works when kile is already running.
https://bugs.kde.org/show_bug.cgi?id=491899 --- Comment #2 from Christian Saemann --- Same on latest openSUSE. Unfortunately strong impact on productivity. Also, running "kile --line 100 file.tex&" twice in terminal leads to the following output: qt.dbus.integration: QDBusConnection: couldn't handle call to setLine, no slot matched qt.dbus.integration: QDBusConnection: couldn't handle call to setLine, no slot matched qt.dbus.integration: Could not find slot MainAdaptor::setLine -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 491899] regression 2.9.94: --line option no longer works when kile is already running.
https://bugs.kde.org/show_bug.cgi?id=491899 Christian Saemann changed: What|Removed |Added CC||christian.saem...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 428262] New: Problem in Syntax Highlighting LaTeX
https://bugs.kde.org/show_bug.cgi?id=428262 Bug ID: 428262 Summary: Problem in Syntax Highlighting LaTeX Product: kile Version: 2.9.93 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: michel.lud...@kdemail.net Reporter: christian.saem...@gmx.de Target Milestone: --- Syntax highlighting is in math mode after \end{equation} when using resizebox in equation. STEPS TO REPRODUCE 1. Enter the following lines somewhere in a LaTeX file \begin{equation} \resizebox{\hsize}{!}{ $\begin{pmatrix} 3 \end{pmatrix}$}~. \end{equation} Hello 2. The editor highlighting is that of math mode after this, i.e. "Hello" is highlighted as math. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 399693] New: Standard Calendar changed after update
https://bugs.kde.org/show_bug.cgi?id=399693 Bug ID: 399693 Summary: Standard Calendar changed after update Product: korganizer Version: 5.9.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: christian.saem...@gmx.de Target Milestone: --- After each update, KOrganizer resets the standard calendar to another calendar in my list. That often leads to me adding private appointments to a group calendar which is very annoying. I'm on the openSUSE Tumbleweed packages, not sure if this is a KOrganizer or openSUSE issue. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 376799] Spectacle crashes kwin
https://bugs.kde.org/show_bug.cgi?id=376799 Christian Saemann changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 376799] Spectacle crashes kwin
https://bugs.kde.org/show_bug.cgi?id=376799 --- Comment #2 from Christian Saemann --- Thanks for the reply. I've just tested with spectacle 17.12.1, and everything seems to be working fine now. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 374738] Moving emails from a local folder to another duplicates mails
https://bugs.kde.org/show_bug.cgi?id=374738 Christian Saemann changed: What|Removed |Added CC||christian.saem...@gmx.de --- Comment #1 from Christian Saemann --- I do encounter a very similar problem (Kmail 5.5.0, latest openSUSE Tumbleweed rpms). If I move certain emails from my inbox via drag and drop into another folder, they appear there, but they reappear in the inbox after I select another folder and then again the inbox. This only happens to certain emails, others move without a duplicate appearing. If it happens to an email once, I can reliably reproduce this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378737] Plasma freezes on closing several Okular windows simultaneously from task bar
https://bugs.kde.org/show_bug.cgi?id=378737 Christian Saemann changed: What|Removed |Added CC||christian.saem...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378737] New: Plasma freezes on closing several Okular windows simultaneously from task bar
https://bugs.kde.org/show_bug.cgi?id=378737 Bug ID: 378737 Summary: Plasma freezes on closing several Okular windows simultaneously from task bar Product: plasmashell Version: 5.9.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: christian.saem...@gmx.de CC: plasma-b...@kde.org Target Milestone: 1.0 I usually have 10-20 Okular windows open at the same time. When I close them simultaneously by right clicking on the collapsed Okular entry in the task bar and selecting "Close", plasma freezes sometimes. I then have to kill it and restart it to get back to a working system. The error seems to occur mostly after starting the computer with a few restored Okular windows that were opened by the browser and that could not be restored properly (temp-file no longer available after boot, etc.) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 377856] Kate Project plugin does not add 'search in project' on startup
https://bugs.kde.org/show_bug.cgi?id=377856 Christian Saemann changed: What|Removed |Added CC||christian.saem...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 377856] New: Kate Project plugin does not add 'search in project' on startup
https://bugs.kde.org/show_bug.cgi?id=377856 Bug ID: 377856 Summary: Kate Project plugin does not add 'search in project' on startup Product: kate Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: christian.saem...@gmx.de Target Milestone: --- When I open a file of a project, kate adds the project tab to the bar with "Documents" and "File Browser" on the left. It doesn't add the "in project" option to the global search&replace tab accessible via the button on the bottom of the window. Instead, I have to deactivate the project plugin and reactivate it in settings in order to get this option. I'm running Kate 16.12.3-1.1 from openSUSE Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 376808] Akonadi stuck on retrieving folder content, ItemFetchJob Stuck, Failed: Multiple Merge Candidates
https://bugs.kde.org/show_bug.cgi?id=376808 --- Comment #4 from Christian Saemann --- In case this helps: I've just had to clear the cache of a folder once more, so this still happens in 16.12.2. It seems to be connected to filtering: the folder contains newsletters, which are put there by a filter rule upon receipt. I can't see anything special about the filter I use, though. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 376562] Dual screen: 2nd screen does not wake up
https://bugs.kde.org/show_bug.cgi?id=376562 --- Comment #2 from Christian Saemann --- Thanks for your reply. My Xorg.0.log contains the following line: [10.354] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20160711 I'm on kernel 4.8.11-1-default. Please let me know if there's anything else you'd like to know. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 376808] Akonadi stuck on retrieving folder content, ItemFetchJob Stuck, Failed: Multiple Merge Candidates
https://bugs.kde.org/show_bug.cgi?id=376808 --- Comment #3 from Christian Saemann --- Thanks for your quick reply, this fixed it. I should have probably googled more thoroughly. BTW: You mentioned in the blog post that this bug should be fixed in 16.12.1, I experienced it on 16.12.2 (openSUSE Tumbleweed packages). -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 376808] Akonadi stuck on retrieving folder content, ItemFetchJob Stuck, Failed: Multiple Merge Candidates
https://bugs.kde.org/show_bug.cgi?id=376808 Christian Saemann changed: What|Removed |Added CC||christian.saem...@gmx.de Platform|Other |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 376808] Akonadi stuck on retrieving folder content, ItemFetchJob Stuck, Failed: Multiple Merge Candidates
https://bugs.kde.org/show_bug.cgi?id=376808 --- Comment #1 from Christian Saemann --- Created attachment 104168 --> https://bugs.kde.org/attachment.cgi?id=104168&action=edit akonadiconsole job tracker -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 376808] New: Akonadi stuck on retrieving folder content, ItemFetchJob Stuck, Failed: Multiple Merge Candidates
https://bugs.kde.org/show_bug.cgi?id=376808 Bug ID: 376808 Summary: Akonadi stuck on retrieving folder content, ItemFetchJob Stuck, Failed: Multiple Merge Candidates Product: Akonadi Version: 5.4.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Maildir Resource Assignee: kdepim-b...@kde.org Reporter: christian.saem...@gmx.de Target Milestone: --- Created attachment 104167 --> https://bugs.kde.org/attachment.cgi?id=104167&action=edit akonadiconsole debugger I've got a mail folder into which a filter is moving newsletters upon arrival. Something might have gone wrong when filtering, but a few of the emails appear twice. When I click on an unread email in the folder, kmail gets stuck on "retrieving folder content". I had applied akonadictl fsck and akonadictl vacuum previously, but this doesn't change the situation. I've attached pictures from akonadiconsole's debugger and job tracker. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 376799] Spectacle crashes kwin
https://bugs.kde.org/show_bug.cgi?id=376799 Christian Saemann changed: What|Removed |Added CC||christian.saem...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 376799] New: Spectacle crashes kwin
https://bugs.kde.org/show_bug.cgi?id=376799 Bug ID: 376799 Summary: Spectacle crashes kwin Product: Spectacle Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: christian.saem...@gmx.de Target Milestone: --- When I take a screenshot, spectacle occasionally crashes kwin_x11, and I have to restart it from a terminal. In the terminal, I can see the following output after such a crash: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5313, resource id: 52428804, major code: 18 (ChangeProperty), minor code: 0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 20900, resource id: 65011717, major code: 18 (ChangeProperty), minor code: 0 The X11 connection broke: Maximum allowed requested length exceeded (code 4) XIO: fatal IO error 2 (Datei oder Verzeichnis nicht gefunden) on X server ":0" after 421661 requests (421661 known processed) with 0 events remaining. The X11 connection broke: Maximum allowed requested length exceeded (code 4) XIO: fatal IO error 2 (Datei oder Verzeichnis nicht gefunden) on X server ":0" after 421661 requests (421661 known processed) with 0 events remaining. kwin_x11 & [2] 20874 [1] Exit 1 kwin_x11 I'm very happy to do further testing and provide further information if helpful. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 376562] New: Dual screen: 2nd screen does not wake up
https://bugs.kde.org/show_bug.cgi?id=376562 Bug ID: 376562 Summary: Dual screen: 2nd screen does not wake up Product: KScreen Version: 5.9.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: se...@kde.org Reporter: christian.saem...@gmx.de Target Milestone: --- When the two screens have been switched off by power management, only the primary screen is woken up again. A quick switch to a different tty screen (ctrl+alt+F2) and back fixes the problem. Possibly related: Plugging in an external screen freezes the primary one, again switching tty and back fixes the issue. Finally: Unplugging the external screen during operations seems to lead to problems with the graphics driver: the display will occasionally get distorted with white flashes on parts of screen (as if quickly switched off and on or so) and only a reboot fixes this. I'm on latest Tumbleweed packages, MacBook Pro 11,2 with Intel Iris Pro 5200 Graphics. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 376562] Dual screen: 2nd screen does not wake up
https://bugs.kde.org/show_bug.cgi?id=376562 Christian Saemann changed: What|Removed |Added CC||christian.saem...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 375149] Kmail deletes emails from folder after switching to folder
https://bugs.kde.org/show_bug.cgi?id=375149 Christian Saemann changed: What|Removed |Added CC||christian.saem...@gmx.de --- Comment #10 from Christian Saemann --- I've had the same problem and it was definitely related to filtering. I had to disable the filter agent in akonadi console and delete/setup again all filter rules. During this process, I noticed that the target folders under "filter action" were sometimes not set correctly (i.e. the textbox was empty). If I clicked on the button to set the folder, however, the correct folder was selected. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 375714] Crash on akonadictl stop (while filteragent was hanging)
https://bugs.kde.org/show_bug.cgi?id=375714 Christian Saemann changed: What|Removed |Added CC||christian.saem...@gmx.de --- Comment #2 from Christian Saemann --- I'm experiencing the same bug. I'm happy to provide reports and do some testing, if this is helpful. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 375653] New: Cannot rename folders in local maildir resource
https://bugs.kde.org/show_bug.cgi?id=375653 Bug ID: 375653 Summary: Cannot rename folders in local maildir resource Product: Akonadi Version: 5.4.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Maildir Resource Assignee: kdepim-b...@kde.org Reporter: christian.saem...@gmx.de Target Milestone: --- I've just noticed that my current version of KMail (5.4.1, latest openSUSE Tumbleweed packages 16.12.1-1.1) doesn't allow me to change folder names any more (via folder properties). It just seems to ignore any changes I enter after clicking ok. This is most likely an Akonadi problem, because the same happens also in the browser of Akonadi Console. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 375653] Cannot rename folders in local maildir resource
https://bugs.kde.org/show_bug.cgi?id=375653 Christian Saemann changed: What|Removed |Added Platform|Other |openSUSE RPMs CC||christian.saem...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368060] Replying to html email that has a PDF attachment creates junk in the reply
https://bugs.kde.org/show_bug.cgi?id=368060 Christian Saemann changed: What|Removed |Added CC||christian.saem...@gmx.de --- Comment #6 from Christian Saemann --- Can confirm this bug with png attachments as well as the workaround from comment 1, on Kmail 5.3.0, latest packages from opensuse Tumbleweed. This is a rather annoying bug in everyday use of kmail. I'm happy to test/provide more details if this is helpful. It seems that it doesn't recognize the mime type of the attachment. It simply quotes the binary content of the attachment, and produces many lines as e.g.: > ÷$÷É_]±ÓN"2Î<ðDÀ?Âwr:½®*Tá©Äoù¶ü|_ -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 369485] New: Kmail crashes randomly at startup (struggle to connect to Akonadi)
https://bugs.kde.org/show_bug.cgi?id=369485 Bug ID: 369485 Summary: Kmail crashes randomly at startup (struggle to connect to Akonadi) Product: kmail2 Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: christian.saem...@gmx.de When starting kmail or kmail in kontact after booting up, it randomly crashes. The UI appears, a message box says: (translating from German) "A severe error occured in the e-mail-program. The program is terminated." Clicking on OK closes kmail. (It seems that new mails etc. are downloaded in the background.) Starting 4-5 times seems to guarantee to get kmail up running. My impression (and from the result listed below) is that it's struggling to connect to Akonadi. Reproducible: Sometimes Steps to Reproduce: 1. start kmail or kontact Actual Results: Kmail/Kontact crashes. The output to a terminal when the crash happens: Pass a valid window to KWallet::Wallet::openWallet(). void AdblockManager::reloadConfig() false AdBlock::AdblockManager(0x1f4fb40) 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: log_akonadicore: Invalid command, the world is going to end! QIODevice::read (QLocalSocket): device not open org.kde.akonadi.ETM: Subtree: 141 QSet(387, 386, 389, 388, 391, 390, 393, 392, 395, 394, 397, 396, 399, 398, 497, 496, 499, 498, 501, 500, 503, 502, 505, 504, 507, 506, 509, 508, 511, 510, 481, 480, 483, 482, 485, 484, 487, 486, 489, 488, 491, 490, 493, 492, 495, 494, 465, 464, 467, 466, 469, 468, 471, 470, 473, 472, 475, 474, 477, 476, 479, 478, 449, 448, 451, 450, 453, 452, 455, 454, 457, 456, 459, 458, 461, 460, 463, 462, 561, 560, 563, 562, 565, 564, 567, 566, 569, 568, 571, 570, 573, 572, 575, 574, 545, 544, 547, 546, 549, 548, 551, 550, 553, 552, 555, 554, 557, 556, 559, 558, 529, 528, 531, 530, 533, 532, 535, 534, 537, 536, 539, 538, 541, 540, 543, 542, 513, 512, 515, 514, 517, 516, 519, 518, 521, 520, 523, 522, 525, 524, 527, 526, 577, 576, 583, 585, 584, 587, 586, 588, 177, 179, 178, 181, 180, 183, 182, 185, 184, 187, 186, 189, 188, 191, 190, 145, 147, 146, 149, 148, 151, 150, 153, 152, 155, 154, 157, 156, 158, 141, 241, 240, 243, 242, 245, 244, 247, 246, 249, 248, 251, 250, 253, 252, 255, 254, 225, 224, 227, 226, 229, 228, 231, 230, 233, 232, 235, 234, 237, 236, 239, 238, 209, 208, 211, 210, 213, 212, 215, 214, 217, 216, 219, 218, 221, 220, 223, 222, 193, 192, 195, 194, 197, 196, 199, 198, 201, 200, 203, 202, 205, 204, 207, 206, 305, 304, 307, 306, 309, 308, 311, 310, 313, 312, 315, 314, 317, 316, 319, 318, 289, 288, 291, 290, 293, 292, 295, 294, 297, 296, 299, 298, 301, 300, 303, 302, 273, 272, 275, 274, 277, 276, 279, 278, 281, 280, 283, 282, 285, 284, 287, 286, 257, 256, 259, 258, 261, 260, 263, 262, 265, 264, 267, 266, 269, 268, 271, 270, 369, 368, 371, 370, 373, 372, 375, 374, 377, 376, 379, 378, 381, 380, 383, 382, 353, 352, 355, 354, 357, 356, 359, 358, 361, 360, 363, 362, 365, 364, 367, 366, 337, 336, 339, 338, 341, 340, 343, 342, 345, 344, 347, 346, 349, 348, 351, 350, 321, 320, 323, 322, 325, 324, 327, 326, 329, 328, 331, 330, 333, 332, 335, 334, 433, 432, 435, 434, 437, 436, 439, 438, 441, 440, 443, 442, 445, 444, 447, 446, 417, 416, 419, 418, 421, 420, 423, 422, 425, 424, 427, 426, 429, 428, 431, 430, 401, 400, 403, 402, 405, 404, 407, 406, 409, 408, 411, 410, 413, 412, 415, 414, 385, 384) org.kde.akonadi.ETM: Fetch job took 148 msec org.kde.akonadi.ETM: was collection fetch job: collections: 422 org.kde.akonadi.ETM: first fetched collection: "Lokale Ordner" log_akonadicore: "" log_akonadicore: Failed SpecialCollectionsRequestJob::slotResult "Verbindung zum Akonadi-Dienst kann nicht hergestellt werden." log_mailcommon: "Im E-Mail-Programm ist ein schwerwiegender Fehler aufgetreten. Das Programm wird beendet." org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: Fetch job took 258 msec org.kde.akonadi.ETM: was collection fetch job: collections: 8 org.kde.akonadi.ETM: first fetched collection: "Search" org.kde.akonadi.ETM: Fetch job took 46 msec org.kde.akonadi.ETM: was collection fetch job: collections: 0 org.kde.akonadi.ETM: collection: "Admin - done" org.kde.akonadi.ETM: collection: "Admin - todo" org.kde.akonadi.ETM: collection: "Family" org.kde.akonadi.ETM: collection: "Geschäftliches" org.kde.akonadi.ETM: collection: "My Research Projects - done" org.kde.akonadi.ETM: collection: "My Research Projects - todo" org.kde.akonadi.ETM: collection: "Other Academic, Travel - done" org.kde.akonadi.ETM: collection: "Other Academic, Travel - todo" org.kde.akonadi.ETM: collection: "Private" org.kde.akonadi.ETM: collection: "Teaching, Mentoring, PhDs - done" org.kde.akonadi.ETM: c
[kontact] [Bug 368323] New: Applying a filter crashed Kmail and Kontact
https://bugs.kde.org/show_bug.cgi?id=368323 Bug ID: 368323 Summary: Applying a filter crashed Kmail and Kontact Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: christian.saem...@gmx.de Application: kontact (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.25.0 Operating System: Linux 4.7.0-2-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I applied a filter (by using the hotkey) which is supposed to move an email to a folder - Unusual behavior I noticed: Kmail/Kontact crashed - Custom settings of the application: My Akonadi setup seems to be problematic. 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 0x7facfda17940 (LWP 18422))] Thread 43 (Thread 0x7fab51134700 (LWP 18627)): #0 0x7facf626509f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7faced9d4129 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7faced9d4840 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7faced9d4a10 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7faced9d15cd in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7facf625f474 in start_thread () at /lib64/libpthread.so.0 #6 0x7facfa3b83ed in clone () at /lib64/libc.so.6 Thread 42 (Thread 0x7fab51ff9700 (LWP 18593)): #0 0x7facf626509f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabe3248163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fabe357e781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7facf625f474 in start_thread () at /lib64/libpthread.so.0 #4 0x7facfa3b83ed in clone () at /lib64/libc.so.6 Thread 41 (Thread 0x7fab527fa700 (LWP 18592)): #0 0x7facf626509f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabe3248163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fabe357e781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7facf625f474 in start_thread () at /lib64/libpthread.so.0 #4 0x7facfa3b83ed in clone () at /lib64/libc.so.6 Thread 40 (Thread 0x7fab4a7fa700 (LWP 18591)): #0 0x7facf626509f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabe3248163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fabe357e781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7facf625f474 in start_thread () at /lib64/libpthread.so.0 #4 0x7facfa3b83ed in clone () at /lib64/libc.so.6 Thread 39 (Thread 0x7fab52ffb700 (LWP 18590)): #0 0x7facf626509f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabe3248163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fabe357e781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7facf625f474 in start_thread () at /lib64/libpthread.so.0 #4 0x7facfa3b83ed in clone () at /lib64/libc.so.6 Thread 38 (Thread 0x7fab537fc700 (LWP 18589)): #0 0x7facf626509f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabe3248163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fabe357e781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7facf625f474 in start_thread () at /lib64/libpthread.so.0 #4 0x7facfa3b83ed in clone () at /lib64/libc.so.6 Thread 37 (Thread 0x7fab53ffd700 (LWP 18588)): #0 0x7facf626509f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabe3248163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fabe357e781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7facf625f474 in start_thread () at /lib64/libpthread.so.0 #4 0x7facfa3b83ed in clone () at /lib64/libc.so.6 Thread 36 (Thread 0x7faba09b2700 (LWP 18587)): #0 0x7facf626509f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabe3247011 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fabe357e781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7facf625f474 in start_thread () at /lib64/libpthread.so.0 #4 0x7facfa3b83ed in clone () at /lib64/libc.so.6 Thread 35 (Thread 0x7fabb61b8700 (LWP 18586)): #0 0x7facf626509f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabe354da6b in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fabe354daa9 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7facf625f474 in start_thread () at /lib64/libpthread.so.0 #4 0x7facfa3b83ed in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7faba3140700 (LWP 18524)): #0 0x7facf5653019 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7facf560eff2 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7facf560f14c in g_main_context_it
[Akonadi] [Bug 340813] sometimes two copies of mysqld are running with Akonadi
https://bugs.kde.org/show_bug.cgi?id=340813 Christian Saemann changed: What|Removed |Added CC||christian.saem...@gmx.de --- Comment #9 from Christian Saemann --- I'm not sure if this helps, but I also run into situations where Akonadi seems to initiate two mysqld processes. This is with the latest KDE packages (16.08) from openSUSE Tumbleweed. The first one is just after startup, I can often read and browse emails for 10 seconds or so, then kmail says akonadi is not running properly. I then have to killall mysqld and restart akonadi. The second one, and this happens reliably each time, is when I initiate an email search, having deleted all prior search folders. Kmail states that it can't connect to akonadi-service, and stops working properly. After this, I always have two mysqld processes running. akonadiserver.error.old contains just one line: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) If there's any additional specific error logs or debug information you'd like to see, just let me know. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 368150] New: Kontact crashes when email is moved to a folder
https://bugs.kde.org/show_bug.cgi?id=368150 Bug ID: 368150 Summary: Kontact crashes when email is moved to a folder Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: christian.saem...@gmx.de Application: kontact (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.25.0 Operating System: Linux 4.7.0-2-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I tried to move a message from the inbox (pop3-server, so locally stored) into another folder. - Custom settings of the application: I'm having problems with my akonadi installation, akonadi seems to be restarting regularly in the background. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f03471d0940 (LWP 2540))] Thread 80 (Thread 0x7f00f77fd700 (LWP 2864)): #0 0x7f0343b69a1d in poll () at /lib64/libc.so.6 #1 0x7f033edc9036 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f033edc914c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f03446acaeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f034465476a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f034447a3b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f034447f2d8 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f033fa19474 in start_thread () at /lib64/libpthread.so.0 #8 0x7f0343b723ed in clone () at /lib64/libc.so.6 Thread 79 (Thread 0x7f013a7fb700 (LWP 2862)): #0 0x7f0343b65a7d in read () at /lib64/libc.so.6 #1 0x7f033ee0bc70 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f033edc8b06 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f033edc8fd4 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f033edc914c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f03446acaeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f034465476a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f034447a3b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f034447f2d8 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f033fa19474 in start_thread () at /lib64/libpthread.so.0 #10 0x7f0343b723ed in clone () at /lib64/libc.so.6 Thread 78 (Thread 0x7f015eb25700 (LWP 2860)): #0 0x7f0343b69a1d in poll () at /lib64/libc.so.6 #1 0x7f033edc9036 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f033edc914c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f03446acaeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f034465476a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f034447a3b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f034447f2d8 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f033fa19474 in start_thread () at /lib64/libpthread.so.0 #8 0x7f0343b723ed in clone () at /lib64/libc.so.6 Thread 77 (Thread 0x7f00f47f7700 (LWP 2858)): #0 0x7f0343b65a7d in read () at /lib64/libc.so.6 #1 0x7f033ee0bc70 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f033edc8b06 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f033edc8fd4 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f033edc914c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f03446acaeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f034465476a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f034447a3b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f034447f2d8 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f033fa19474 in start_thread () at /lib64/libpthread.so.0 #10 0x7f0343b723ed in clone () at /lib64/libc.so.6 Thread 76 (Thread 0x7f00f4ff8700 (LWP 2856)): #0 0x7f033ee0d034 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f033edc857c in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f033edc8f5b in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f033edc914c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f03446acaeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f034465476a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f034447a3b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f034447f2d8 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f033fa19474 in start_thread () at /lib64/libpthr
[krunner] [Bug 368091] New: KRunner crashes (most likely due to problems interacting with akonadi
https://bugs.kde.org/show_bug.cgi?id=368091 Bug ID: 368091 Summary: KRunner crashes (most likely due to problems interacting with akonadi Product: krunner Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: christian.saem...@gmx.de Application: krunner (5.7.4) Qt Version: 5.6.1 Frameworks Version: 5.25.0 Operating System: Linux 4.7.0-2-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I just typed "Kontact" in KRunner to start Kontact. Sometimes it works the first time, sometimes KRunner crashes, but if I keep deleting characters and retyping them, in particular when typing fast, KRunner seems to crash reliably. - Unusual behavior I noticed: Crash. - Custom settings of the application: I have currently quite a bit of problems with akonadi (running KDE 16.08), so I'm almost certain it's due to a problem of KRunner getting responses from akonadi. In particular, akonadi restarts regularly when I read email, so it seems that KRunner is struggling with getting reliable answers to search requests. The crash can be reproduced every time. -- Backtrace: Application: krunner (krunner), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f63355a78c0 (LWP 11436))] Thread 22 (Thread 0x7f616247d700 (LWP 11464)): #0 0x7f632eb33eac in __lll_lock_wait () at /lib64/libpthread.so.0 #1 0x7f632eb2dba6 in pthread_mutex_lock () at /lib64/libpthread.so.0 #2 0x7f63353fbf0d in tls_get_addr_tail () at /lib64/ld-linux-x86-64.so.2 #3 0x7f63316341ed in () at /usr/lib64/libQt5Core.so.5 #4 0x7f632eb2b474 in start_thread () at /lib64/libpthread.so.0 #5 0x7f6330f3e3ed in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f62b6746700 (LWP 11462)): #0 0x7f632e1fb019 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f632e1b6ff2 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f632e1b714c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f6331861aeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f633180976a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f633162f3b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f63316342d8 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f632eb2b474 in start_thread () at /lib64/libpthread.so.0 #8 0x7f6330f3e3ed in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f62b77fe700 (LWP 11460)): #0 0x7f632eb3109f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f633163518b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f630b595ec0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f630b59a068 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f630b59503d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f630b59a0c2 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f630b59503d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f630b597f09 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f63316342d8 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f632eb2b474 in start_thread () at /lib64/libpthread.so.0 #10 0x7f6330f3e3ed in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f62b7fff700 (LWP 11459)): #0 0x7f632eb3109f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f633163518b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f630b595ec0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f630b59a068 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f630b59503d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f630b59a0c2 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f630b59503d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f630b59a0c2 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f630b59503d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f630b59a0c2 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f630b59503d in ThreadWeaver::Weaver::applyForWork(Thread
[kontact] [Bug 367560] New: Kmail crashes when moving folder
https://bugs.kde.org/show_bug.cgi?id=367560 Bug ID: 367560 Summary: Kmail crashes when moving folder Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: christian.saem...@gmx.de Application: kontact (5.2.3) Qt Version: 5.6.1 Frameworks Version: 5.24.0 Operating System: Linux 4.7.0-2-default x86_64 Distribution: "openSUSE Tumbleweed (20160813) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I've being moving a folder of emails (containing a non-empty subfolder) by using the popup menu "move folder". I've tried two more times and it crashes each time. - Unusual behavior I noticed: Kmail/Kontact crashes immediately. - Custom settings of the application: My mail folders and email collection is rather large and came from various previous installs and exports/imports. Some of these exports/imports might not have been completed properly, i.e. the Akonadi representation of the data might not be fully correct. Nevertheless, I wouldn't expect a crash. 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 0x7f22b56f4900 (LWP 5503))] Thread 28 (Thread 0x7f21d9db7700 (LWP 5573)): #0 0x7f22b2ba0409 in QMutex::unlock() () at /usr/lib64/libQt5Core.so.5 #1 0x7f22b2dd5191 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f22aac1e5a9 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #3 0x7f22aac1ef7b in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f22aac1f16c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f22b2dd5aeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f22b2d7d76a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f22b2ba33b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f22b2ba82d8 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f22ab442474 in start_thread () at /lib64/libpthread.so.0 #10 0x7f22b229c3ed in clone () at /lib64/libc.so.6 Thread 27 (Thread 0x7f21da5b8700 (LWP 5567)): #0 0x7f22b2293a1d in poll () at /lib64/libc.so.6 #1 0x7f22aac1f056 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f22aac1f16c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f22b2dd5aeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f22b2d7d76a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f22b2ba33b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f22b2ba82d8 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f22ab442474 in start_thread () at /lib64/libpthread.so.0 #8 0x7f22b229c3ed in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7f21dbfff700 (LWP 5551)): #0 0x7f22b22939f0 in poll () at /lib64/libc.so.6 #1 0x7f22aac1f056 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f22aac1f16c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f22b2dd5aeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f22b2d7d76a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f22b2ba33b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f22b2ba82d8 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f22ab442474 in start_thread () at /lib64/libpthread.so.0 #8 0x7f22b229c3ed in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7f21e8f89700 (LWP 5549)): #0 0x7f22b2293a1d in poll () at /lib64/libc.so.6 #1 0x7f22aac1f056 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f22aac1f16c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f22b2dd5aeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f22b2d7d76a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f22b2ba33b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f22b2ba82d8 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f22ab442474 in start_thread () at /lib64/libpthread.so.0 #8 0x7f22b229c3ed in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f21e978a700 (LWP 5547)): #0 0x7f22b2293a1d in poll () at /lib64/libc.so.6 #1 0x7f22aac1f056 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f22aac1f16c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f22b2dd5aeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f22b2d7d76a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f22b2ba33b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f22b2ba82d8 in (