[kmail2] [Bug 388015] Kmail doesn't get content from the external editor
https://bugs.kde.org/show_bug.cgi?id=388015 Laurent Montelchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #4 from Laurent Montel --- Ok you need to use "gvim -f %f" it avoids that gvim forks So it was not a kmail bug but a missing gvim option -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388015] Kmail doesn't get content from the external editor
https://bugs.kde.org/show_bug.cgi?id=388015 --- Comment #3 from Laurent Montel--- yep gedit works/ kate works/kwrite works so indeed I don't know if we need to add a special flag to gvim if we want that it works. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388015] Kmail doesn't get content from the external editor
https://bugs.kde.org/show_bug.cgi?id=388015 --- Comment #2 from Laurent Montel--- it's a problem with gvim... -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388015] Kmail doesn't get content from the external editor
https://bugs.kde.org/show_bug.cgi?id=388015 Laurent Montelchanged: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- it seems that kwrite %f work fine. -- You are receiving this mail because: You are the assignee for the bug.
[kleopatra] [Bug 388022] New: An error occurred: Kleopatra: Could not open file "E:\Buffalotech\ISO\electrum-3.0.3-portable.exe" for reading: Input/output error (218136625)
https://bugs.kde.org/show_bug.cgi?id=388022 Bug ID: 388022 Summary: An error occurred: Kleopatra: Could not open file "E:\Buffalotech\ISO\electrum-3.0.3-portable.exe" for reading: Input/output error (218136625) Product: kleopatra Version: 3.0.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: aheine...@intevation.de Reporter: ffalcon...@gmail.com CC: kdepim-bugs@kde.org, m...@kde.org Target Milestone: --- Created attachment 109444 --> https://bugs.kde.org/attachment.cgi?id=109444=edit Screen capture of error Error when trying to Decrypt / Verify the electrum-3.0.3-portable.exe.asc file -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 Timichanged: What|Removed |Added CC||eagle.bugs.kde.org@airpost. ||net -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 --- Comment #12 from Urs Joss--- Same here: Archlinux. Failing to send to mail.gmx.net with the previously working configuration SSL/Plain on port 465, with or without attachment. In my case I had to switch to TLS and port 587 to get it back up. Interestingly the autodetect option switches back to SSL/465 and removes the tick in checkbox 'server requires authentication'. I don't know how the previous version of kmail behaved with this functionality, I haven't used it for quite some time. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 Urs Josschanged: What|Removed |Added CC||tschent...@gmx.ch -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 David E. Narvaezchanged: What|Removed |Added CC||david.narv...@computer.org --- Comment #11 from David E. Narvaez --- (In reply to dcg from comment #10) > I fixed it by going to the outgoing account configuration -> advanced, then > click "autodetect". It changed my cypher option from SSL to TLS and also the > port. That made it work. > > It's as if the configuration had been changed or something. I can confirm this workaround. I don't understand why would the settings change after an update. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 Fabian Vogtchanged: What|Removed |Added CC||fab...@ritter-vogt.de -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 388019] Korganizer crashes when choosing enter new event.
https://bugs.kde.org/show_bug.cgi?id=388019 caxilb...@iasinfo.com changed: What|Removed |Added Summary|Kontact crashes when|Korganizer crashes when |choosing enter new event. |choosing enter new event. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 388019] New: Kontact crashes when choosing enter new event.
https://bugs.kde.org/show_bug.cgi?id=388019 Bug ID: 388019 Summary: Kontact crashes when choosing enter new event. Product: korganizer Version: 5.7.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: caxilb...@iasinfo.com Target Milestone: --- Application: korganizer (5.7.0) Qt Version: 5.10.0 Frameworks Version: 5.40.0 Operating System: Linux 4.4.103-36-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: Every time I attempt to enter a new event, new to do, or new journal the program crashes. This repeats every time. The crash can be reproduced every time. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fde83bf8940 (LWP 4133))] Thread 4 (Thread 0x7fde57fff700 (LWP 4139)): #0 0x7fde7f47b20d in poll () from /lib64/libc.so.6 #1 0x7fde7559e314 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fde7559e42c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fde7ffb1dab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fde7ff5d83b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fde7fd9af3a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fde7fd9fbff in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #7 0x7fde773c2744 in start_thread () from /lib64/libpthread.so.0 #8 0x7fde7f483aad in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fde5c861700 (LWP 4136)): #0 0x7fde755df899 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7fde7559d969 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7fde7559e230 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fde7559e42c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7fde7ffb1dab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fde7ff5d83b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7fde7fd9af3a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7fde7fd9fbff in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #8 0x7fde773c2744 in start_thread () from /lib64/libpthread.so.0 #9 0x7fde7f483aad in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fde5da79700 (LWP 4135)): #0 0x7fde773c9a7c in __lll_lock_wait () from /lib64/libpthread.so.0 #1 0x7fde773c47fb in pthread_mutex_lock () from /lib64/libpthread.so.0 #2 0x7fde76e28e4c in ?? () from /usr/X11R6/lib64/libGL.so.1 #3 0x7fde76e2dd81 in ?? () from /usr/X11R6/lib64/libGL.so.1 #4 0x7fde76e2e298 in ?? () from /usr/X11R6/lib64/libGL.so.1 #5 0x7fde6f3d4102 in ?? () from /usr/lib64/tls/libnvidia-tls.so.384.98 #6 0x7fde755de750 in ?? () from /usr/lib64/libglib-2.0.so.0 #7 0x7fde7559de49 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #8 0x7fde7559e2a8 in ?? () from /usr/lib64/libglib-2.0.so.0 #9 0x7fde7559e42c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #10 0x7fde7ffb1dab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #11 0x7fde7ff5d83b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #12 0x7fde7fd9af3a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #13 0x7fde7e969875 in ?? () from /usr/lib64/libQt5DBus.so.5 #14 0x7fde7fd9fbff in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #15 0x7fde773c2744 in start_thread () from /lib64/libpthread.so.0 #16 0x7fde7f483aad in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fde83bf8940 (LWP 4133)): [KCrash Handler] #6 EventViews::AgendaView::placeDecorations (this=this@entry=0x184d740, decoList=..., date=..., labelBox=labelBox@entry=0x18ab550, forWeek=forWeek@entry=false) at /usr/src/debug/eventviews-17.12.0/src/agenda/agendaview.cpp:1136 #7 0x7fde7da6e9b6 in EventViews::AgendaView::createDayLabels (this=this@entry=0x184d740, force=force@entry=true) at /usr/src/debug/eventviews-17.12.0/src/agenda/agendaview.cpp:1265 #8 0x7fde7da6f76b in EventViews::AgendaView::init (this=this@entry=0x184d740, start=..., end=...) at /usr/src/debug/eventviews-17.12.0/src/agenda/agendaview.cpp:839 #9 0x7fde7da6fd38 in EventViews::AgendaView::AgendaView (this=0x184d740, start=..., end=..., isInteractive=, isSideBySide=, parent=) at /usr/src/debug/eventviews-17.12.0/src/agenda/agendaview.cpp:722 #10 0x7fde7e4acb79 in IncidenceEditorNG::ResourceManagement::ResourceManagement (this=0x1828bb0, parent=) at /usr/src/debug/incidenceeditor-17.12.0/src/resourcemanagement.cpp:142 #11
[kmail2] [Bug 387931] KMail 5.7.0 is missing the message structure option
https://bugs.kde.org/show_bug.cgi?id=387931 --- Comment #5 from Till Schäfer--- I use it as an end user, e.g. to verify that a newsletter format of my wordpress instance is correct. I also think, that "toolbar" \subseteq "menu" is a typical pattern and therefore is the expectation of users. Thus, having items randomly appearing only for the on or the other place will only create more confusion. I also do not think that this menu item is very confusing for other users. Alternatively it may be possible to hide advanced features and only show them if you choose the advanced mode? I.e. similar to the vlc approach. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388015] New: Kmail doesn't get content from the external editor
https://bugs.kde.org/show_bug.cgi?id=388015 Bug ID: 388015 Summary: Kmail doesn't get content from the external editor Product: kmail2 Version: 5.7.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: hi-an...@yandex.ru Target Milestone: --- Steps to reproduce: 1. Open plugins settings, and set as an external editor "gvim %f". 2. Save the settings and restart KMail. 3. Press Ctrl+n to open a new mail; it should trigger the editor. 4. Type "test" in the editor, save, and quit. Expected: The "test" text should appear in the mail Actual: The typed content never appears. Additional info: It's a pretty important functional because typing a text in KMail natively is annoying due to this qt bug https://bugreports.qt.io/browse/QTBUG-64360 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 dcgchanged: What|Removed |Added CC||dieg...@gmail.com --- Comment #10 from dcg --- I got an error too. I fixed it by going to the outgoing account configuration -> advanced, then click "autodetect". It changed my cypher option from SSL to TLS and also the port. That made it work. It's as if the configuration had been changed or something. -- You are receiving this mail because: You are the assignee for the bug.
[frameworks-kio] [Bug 386420] kio crash while fetching most feeds
https://bugs.kde.org/show_bug.cgi?id=386420 Christophe Giboudeauxchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Christophe Giboudeaux --- *** This bug has been marked as a duplicate of bug 386364 *** -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 avlaschanged: What|Removed |Added CC||jsar...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #80 from Steven Haigh--- Just to give this a nudge, I still see this with 17.12 on Fedora 27. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 Rex Dieterchanged: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 --- Comment #9 from jread--- (In reply to jread from comment #8) > My error is not a socket error but a connection interrupted error, but this > bug is linked from bug 387926 which is closed as resolved. > > My laptop with 17.08 on still works absolutely fine Sorry incorrect bug, I referenced this one. I meant Bug 388005 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 --- Comment #8 from jread--- My error is not a socket error but a connection interrupted error, but this bug is linked from bug 387926 which is closed as resolved. My laptop with 17.08 on still works absolutely fine -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 Daniel Vrátilchanged: What|Removed |Added CC||dvra...@kde.org --- Comment #7 from Daniel Vrátil --- Socket Error 1 is ConnectionRefusedError, which means it's a problem on the server. Have you checked your SSL/TLS/port settings? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 --- Comment #6 from Rex Dieter--- For an extra data point, setting up a new google account after kmail-17.12.0 installation seems fine (for me, on my fedora 27 box) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 jreadchanged: What|Removed |Added CC||jon.r...@engo-scs.co.uk --- Comment #5 from jread --- I have a problem sending mail too. I am using Antergos and have just updated to KMail 17.12 this morning. It fails using GMail and also my own hosted server for my business running Postfix/Dovecot. I have tried sending a plain text message with no attachments. My own server authenticates using STARTTLS on port 587, I believe my GMail is using SSL on port 465. My mail.log file just reports that the connection was lost after STARTTLS. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 373443] Mail Dispatcher Agent spins at 100% CPU after upgrade from 4:16.08.2+p16.04+git20161117.2322-0 to 4:16.08.3+p16.04+git20161207.0319-0
https://bugs.kde.org/show_bug.cgi?id=373443 Mike Goodwinchanged: What|Removed |Added CC||m...@mgoodwin.net -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 Rex Dieterchanged: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388005] Impossible to send emails : "Connection to server interrupted".
https://bugs.kde.org/show_bug.cgi?id=388005 Rex Dieterchanged: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 Christophe Giboudeauxchanged: What|Removed |Added Status|CONFIRMED |UNCONFIRMED Ever confirmed|1 |0 Version|5.7.0 |unspecified --- Comment #4 from Christophe Giboudeaux --- Not enough information : - which smtp servers were tested ? - which authentication method ? - was it a plain text / html message ? Did it contain attachments ? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 kmichanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||kamika...@web.de Version|unspecified |5.7.0 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 kmichanged: What|Removed |Added CC||tro...@free.fr --- Comment #3 from kmi --- *** Bug 388005 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388005] Impossible to send emails : "Connection to server interrupted".
https://bugs.kde.org/show_bug.cgi?id=388005 kmichanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from kmi --- *** This bug has been marked as a duplicate of bug 387926 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388005] Impossible to send emails : "Connection to server interrupted".
https://bugs.kde.org/show_bug.cgi?id=388005 Steven Haighchanged: What|Removed |Added CC||net...@crc.id.au --- Comment #1 from Steven Haigh --- On a similar note, using Fedora 27 + 17.12 kmail, I get the following error with smtp.gmail.com: "Failed to transport message. Server error" I can't find any way to display what the error actually is - but this was working prior to the 17.12 update. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388005] Impossible to send emails : "Connection to server interrupted".
https://bugs.kde.org/show_bug.cgi?id=388005 kmichanged: What|Removed |Added CC||kamika...@web.de Summary|Impossible to send emails : |Impossible to send emails : |"Connection to serveur |"Connection to server |interrupted". |interrupted". -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 387923] Calendar from DAVGroupware resource crashes KOrganizer
https://bugs.kde.org/show_bug.cgi?id=387923 --- Comment #4 from Metko--- I'd love to, but it's hard to imagine how. One would need a copy of my calendar in owncloud, which should be imported to an owncloud account in the test setup. Would you be able to do this? Some observations that may help instead: 1) As I wrote above, exporting and re-importing the calendar solved the crashing behavior. However, todos were not imported (due to a malfunction of the import function), so the calendar contents is not identical. Interestingly, if you look at the stack trace above, you see that thread 1 crashed upon displaying a todo. 2) Previously I found a temporary solution by running the current version of korganizer with the (old) 17.04 version of libKF5eventview. The most recent korganizer version is not compatible with that version though, which is why this solution stopped working (and which made me file this bug). But it's another indication that the bug most likely is in the code for viewing an event. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387931] KMail 5.7.0 is missing the message structure option
https://bugs.kde.org/show_bug.cgi?id=387931 --- Comment #4 from Laurent Montel--- For me it's not a end user feature. It's for power user feature. If we want to clean up menu we don't need to add more extra menu entry for power user. There is a shortcut for it, and we can add it from toolbar if we want. Otherwise it's not necessary to try to simplify kmail if we keep some power user feature in menu, for sure I don't use by default this feature. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387931] KMail 5.7.0 is missing the message structure option
https://bugs.kde.org/show_bug.cgi?id=387931 Daniel Vrátilchanged: What|Removed |Added Resolution|WONTFIX |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 CC||dvra...@kde.org --- Comment #3 from Daniel Vrátil --- I don't think that's acceptable - we can't just have some options "hidden" in the toolbar, especially when they are not enabled by default and not accessible from the menu at all. I had to actually look into the source code to find where the option is, that's simply not something we can expect our users to do... IMO toolbars should be like "favorites". They should contain actions from menus that are very often used by users so that they can just click on the button in the toolbar instead of having to open the menu to get to those actions, but toolbars should *never* hide additional actions that are not accessible from the menu. There's just *NO WAY* users will ever find those options. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 388007] New: Korganizer synchronization
https://bugs.kde.org/show_bug.cgi?id=388007 Bug ID: 388007 Summary: Korganizer synchronization Product: Akonadi Version: 5.4.3 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: he...@stark-jena.de Target Milestone: --- Application: akonadiserver (5.4.3) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.9.56-server-1.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: - Custom settings of the application: The korganizer database is stored in a dropbox. I was able to detect synchronization problems with simultaneous access to the dropbox of multiple computers. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7943f0b800 (LWP 1249))] Thread 33 (Thread 0x7f78b7fff700 (LWP 1303)): #0 0x7f794b456ff8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f794cd58d46 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f794cd54764 in QThreadPoolThread::run() () at /lib64/libQt5Core.so.5 #3 0x7f794cd57ff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #4 0x7f794b45166d in start_thread () at /lib64/libpthread.so.0 #5 0x7f794c459e4d in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7f78e4ff9700 (LWP 1302)): #0 0x7f794b456ff8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f794cd58d46 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f794cd54764 in QThreadPoolThread::run() () at /lib64/libQt5Core.so.5 #3 0x7f794cd57ff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #4 0x7f794b45166d in start_thread () at /lib64/libpthread.so.0 #5 0x7f794c459e4d in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7f78e57fa700 (LWP 1301)): #0 0x7f794b456ff8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f794cd58d46 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f794cd54764 in QThreadPoolThread::run() () at /lib64/libQt5Core.so.5 #3 0x7f794cd57ff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #4 0x7f794b45166d in start_thread () at /lib64/libpthread.so.0 #5 0x7f794c459e4d in clone () at /lib64/libc.so.6 Thread 30 (Thread 0x7f78e5ffb700 (LWP 1300)): #0 0x7f794b456ff8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f794cd58d46 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f794cd54764 in QThreadPoolThread::run() () at /lib64/libQt5Core.so.5 #3 0x7f794cd57ff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #4 0x7f794b45166d in start_thread () at /lib64/libpthread.so.0 #5 0x7f794c459e4d in clone () at /lib64/libc.so.6 Thread 29 (Thread 0x7f78e67fc700 (LWP 1299)): #0 0x7f794b456ff8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f794cd58d46 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f794cd54764 in QThreadPoolThread::run() () at /lib64/libQt5Core.so.5 #3 0x7f794cd57ff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #4 0x7f794b45166d in start_thread () at /lib64/libpthread.so.0 #5 0x7f794c459e4d in clone () at /lib64/libc.so.6 Thread 28 (Thread 0x7f78e6ffd700 (LWP 1289)): #0 0x7f794c44992d in read () at /lib64/libc.so.6 #1 0x7f7946825073 in () at /usr/lib64/nvidia-current/tls/libnvidia-tls.so.384.98 #2 0x7f79494b7690 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #3 0x7f794947379e in g_main_context_check () at /lib64/libglib-2.0.so.0 #4 0x7f7949473c38 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #5 0x7f7949473d9c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #6 0x7f794cf6de2b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f794cf1949a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #8 0x7f794cd533bc in QThread::exec() () at /lib64/libQt5Core.so.5 #9 0x7f794cd57ff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7f794b45166d in start_thread () at /lib64/libpthread.so.0 #11 0x7f794c459e4d in clone () at /lib64/libc.so.6 Thread 27 (Thread 0x7f78e77fe700 (LWP 1287)): #0 0x7f794c44e00d in poll () at /lib64/libc.so.6 #1 0x7f7949473c94 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f7949473d9c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f794cf6de2b in QEventDispatcherGlib::processEvents(QFlags) () at
[korganizer] [Bug 387923] Calendar from DAVGroupware resource crashes KOrganizer
https://bugs.kde.org/show_bug.cgi?id=387923 Laurent Montelchanged: What|Removed |Added CC||mon...@kde.org --- Comment #3 from Laurent Montel --- Could you provide some testcase please ? -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 387923] Calendar from DAVGroupware resource crashes KOrganizer
https://bugs.kde.org/show_bug.cgi?id=387923 --- Comment #2 from Metko--- (In reply to Metko from comment #1) > Solved the problem by exporting all calendar entries and importing them to a > newly created (CalDav-owncloud-) calendar. Beware! Korganizer's import function does not import todos! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388005] New: Impossible to mail emails : "Connection to serveur interrupted".
https://bugs.kde.org/show_bug.cgi?id=388005 Bug ID: 388005 Summary: Impossible to mail emails : "Connection to serveur interrupted". Product: kmail2 Version: 5.7.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: tro...@free.fr Target Milestone: --- Since tha KDE Applications 17.12 update on Archlinux, I cannot sent emails anymore with Kmail, it says "Connection to the serveur interrupted". I did not change anything to my previously working configuration. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388005] Impossible to send emails : "Connection to serveur interrupted".
https://bugs.kde.org/show_bug.cgi?id=388005 tro...@free.fr changed: What|Removed |Added Summary|Impossible to mail emails : |Impossible to send emails : |"Connection to serveur |"Connection to serveur |interrupted". |interrupted". -- You are receiving this mail because: You are the assignee for the bug.