[kmail2] [Bug 395752] kmail keeps hiding the toolbar upon restart
https://bugs.kde.org/show_bug.cgi?id=395752 --- Comment #3 from dS810 --- @Stefano: You can enable it on menu item "Settigs -> Toolbar" -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 395752] kmail keeps hiding the toolbar upon restart
https://bugs.kde.org/show_bug.cgi?id=395752 --- Comment #2 from Stefano --- Another thing that I didn't noticed before, is that the status bar is vanished and I can't find how to make it visible again. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 395752] kmail keeps hiding the toolbar upon restart
https://bugs.kde.org/show_bug.cgi?id=395752 dS810 changed: What|Removed |Added Ever confirmed|0 |1 CC||artem.anuf...@live.de Status|UNCONFIRMED |CONFIRMED --- Comment #1 from dS810 --- Confirm. Same behaviour here after last update. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388033] Kmail crashes after changing default trash folder of IMAP account
https://bugs.kde.org/show_bug.cgi?id=388033 --- Comment #2 from Yury Gubich --- Same solution fixed kmail for me -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 395752] New: kmail keeps hiding the toolbar upon restart
https://bugs.kde.org/show_bug.cgi?id=395752 Bug ID: 395752 Summary: kmail keeps hiding the toolbar upon restart Product: kmail2 Version: 5.8.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: erist...@cryptolab.net Target Milestone: --- Created attachment 113511 --> https://bugs.kde.org/attachment.cgi?id=113511=edit kmail2rc diffs This started happening recently on my Arch Linux install. Plasma: 5.13.1 Frameworks: 5.47.0 Qt: 5.11.1 Steps to reproduce: - Launch kmail The toolbar is hidden - Enable the toolbar - Close kmail - Open kmail The toolbar is hidden again. Looking at kmail2rc I see four changes between launches. See attached diff. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388033] Kmail crashes after changing default trash folder of IMAP account
https://bugs.kde.org/show_bug.cgi?id=388033 Yury Gubich changed: What|Removed |Added CC||arhange...@bk.ru --- Comment #1 from Yury Gubich --- *** Bug 395726 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 395726] KMail crashes with some message about initializing trash source
https://bugs.kde.org/show_bug.cgi?id=395726 Yury Gubich changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Yury Gubich --- *** This bug has been marked as a duplicate of bug 388033 *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 395394] Kontact crashes in Kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=395394 Christophe Giboudeaux changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from Christophe Giboudeaux --- indeed *** This bug has been marked as a duplicate of bug 395678 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 395678] cannot start kmail in plasma-wayland
https://bugs.kde.org/show_bug.cgi?id=395678 Christophe Giboudeaux changed: What|Removed |Added CC||sh...@sorbom.com --- Comment #3 from Christophe Giboudeaux --- *** Bug 395394 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 395743] New: akonadi crashes at akonadictl fsck
https://bugs.kde.org/show_bug.cgi?id=395743 Bug ID: 395743 Summary: akonadi crashes at akonadictl fsck Product: Akonadi Version: 5.7.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: s_dibb...@web.de Target Milestone: --- Application: akonadiserver (5.7.3) Qt Version: 5.9.5 Frameworks Version: 5.46.0 Operating System: Linux 4.15.0-23-generic x86_64 Distribution: Ubuntu 18.04 LTS -- Information about the crash: - What I was doing when the application crashed: running "akonadictl fsck" - Unusual behavior I noticed: akonadi crashed already twice at login, but started then and worked (kmail ran and worked as expected) On sending an email, akonadi crashed again. Restarted the server by "akonadictl start", which produced no (obvious) errors. Running "akonadictl fsck" lead to a new crash and does so hence, while "akonadictl start" works most of the times. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f70153a2800 (LWP 1231))] Thread 31 (Thread 0x7f6f81ffb700 (LWP 1397)): #0 0x7f7013044bf9 in __GI___poll (fds=0x7f6f7c020870, nfds=1, timeout=123810) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f70104d8439 in g_main_context_poll (priority=, n_fds=1, fds=0x7f6f7c020870, timeout=, context=0x7f6f7c01c5c0) at ../../../../glib/gmain.c:4204 #2 g_main_context_iterate (context=context@entry=0x7f6f7c01c5c0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../../glib/gmain.c:3898 #3 0x7f70104d854c in g_main_context_iteration (context=0x7f6f7c01c5c0, may_block=may_block@entry=1) at ../../../../glib/gmain.c:3964 #4 0x7f7013baa90b in QEventDispatcherGlib::processEvents (this=0x7f6f7c01c4f0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f7013b4f9ea in QEventLoop::exec (this=this@entry=0x7f6f81ffada0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f701396e22a in QThread::exec (this=) at thread/qthread.cpp:515 #7 0x7f701397316d in QThreadPrivate::start (arg=0x55b409c893c0) at thread/qthread_unix.cpp:368 #8 0x7f7011c1e6db in start_thread (arg=0x7f6f81ffb700) at pthread_create.c:463 #9 0x7f701305188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 30 (Thread 0x7f6f997fa700 (LWP 1383)): #0 0x7f7013044bf9 in __GI___poll (fds=0x7f6f7c004a10, nfds=1, timeout=122810) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f70104d8439 in g_main_context_poll (priority=, n_fds=1, fds=0x7f6f7c004a10, timeout=, context=0x7f6f7c000bf0) at ../../../../glib/gmain.c:4204 #2 g_main_context_iterate (context=context@entry=0x7f6f7c000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../../glib/gmain.c:3898 #3 0x7f70104d854c in g_main_context_iteration (context=0x7f6f7c000bf0, may_block=may_block@entry=1) at ../../../../glib/gmain.c:3964 #4 0x7f7013baa90b in QEventDispatcherGlib::processEvents (this=0x7f6f7c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f7013b4f9ea in QEventLoop::exec (this=this@entry=0x7f6f997f9da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f701396e22a in QThread::exec (this=) at thread/qthread.cpp:515 #7 0x7f701397316d in QThreadPrivate::start (arg=0x55b409c81ff0) at thread/qthread_unix.cpp:368 #8 0x7f7011c1e6db in start_thread (arg=0x7f6f997fa700) at pthread_create.c:463 #9 0x7f701305188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 29 (Thread 0x7f6f99ffb700 (LWP 1378)): #0 0x7f70130400b4 in __GI___libc_read (fd=112, buf=buf@entry=0x7f6f99ffab90, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f701051c960 in read (__nbytes=16, __buf=0x7f6f99ffab90, __fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44 #2 g_wakeup_acknowledge (wakeup=0x7f6f840039b0) at ../../../../glib/gwakeup.c:210 #3 0x7f70104d7f27 in g_main_context_check (context=context@entry=0x7f6f88000bf0, max_priority=2147483647, fds=fds@entry=0x7f6f88003ce0, n_fds=n_fds@entry=1) at ../../../../glib/gmain.c:3681 #4 0x7f70104d83e0 in g_main_context_iterate (context=context@entry=0x7f6f88000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../../glib/gmain.c:3900 #5 0x7f70104d854c in g_main_context_iteration (context=0x7f6f88000bf0, may_block=may_block@entry=1) at ../../../../glib/gmain.c:3964 #6 0x7f7013baa90b in QEventDispatcherGlib::processEvents (this=0x7f6f88000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f7013b4f9ea in QEventLoop::exec (this=this@entry=0x7f6f99ffada0, flags=..., flags@entry=...) at
[kmail2] [Bug 395733] New: does not load external content
https://bugs.kde.org/show_bug.cgi?id=395733 Bug ID: 395733 Summary: does not load external content Product: kmail2 Version: 5.8.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: 1...@maksimo.de Target Milestone: --- Helo, does not load external content. Hook is set. I have already deleted the settings. Uninstalled the program. Everything completely new installed and furnished. No success, content is not loaded. Every time you have to do an extra click to load. Error occurred after update. Therefore, first switched to Thunderbird and hope that the error will quickly abolish. Thanks and regards Google translator -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 395726] New: KMail crashes with some message about initializing trash source
https://bugs.kde.org/show_bug.cgi?id=395726 Bug ID: 395726 Summary: KMail crashes with some message about initializing trash source Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: arhange...@bk.ru Target Milestone: --- Hello, I have 4 imap accounts configured in my kmail. Last thing I did - set trash folders to imap folders from my local trash folder. Now every time I try to open KMail - it crashes and closes KMail not even letting me to acces my imap settings. Error message tells that it was imposible to initialize trash source for imap account with ID 3, i don't even know how to find out which account is it about. Please guide me - what do I need to provide to help? -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 373348] Korganizer doesn't fetch events from Google
https://bugs.kde.org/show_bug.cgi?id=373348 dbrandon.john...@gmail.com changed: What|Removed |Added CC||dbrandon.john...@gmail.com --- Comment #2 from dbrandon.john...@gmail.com --- I'm seeing this in Korganizer as well (17.12). What is really annoying is the PIM extension in the calendar widget shows all the events and details. This tells me the data is there it just isn't being displayed in the calendar app. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 395417] I've to restart akonadi several times during day for get Google IMAP access refreshing
https://bugs.kde.org/show_bug.cgi?id=395417
--- Comment #2 from Michel ---
Akonadi log before I've to restart akonadi :
64 NO mailbox selected READ-ONLY "
org.kde.pim.imapresource: Expunge failed: "Échec de Purger. Le serveur a
répondu : A05 NO mailbox selected READ-ONLY "
org.kde.pim.imapresource: Expunge failed: "Échec de Purger. Le serveur a
répondu : A000101 NO mailbox selected READ-ONLY "
QIODevice::write (KTcpSocket): device not open
[SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
![SASL-XOAUTH2] - filling prompts
![SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
!org.kde.pim.imapresource: Expunge failed: "Échec de Purger. Le serveur a
répondu : A04 NO mailbox selected READ-ONLY "
org.kde.pim.kimap: sasl_client_step failed with: -1 "SASL(0): successful
result: "
org.kde.kgapi.raw: Requesting token refresh:
"client_id=xxx.apps.googleusercontent.com_secret=x_token=1/WhsduCBILIoC2bXcDr1kPTzP1NhJEi4OK8vVGZfx6x2AYRHP_xJ7tM8IWdBjr6qp_type=refresh_token"
org.kde.kgapi: Queued QUrl("https://accounts.google.com/o/oauth2/token;)
org.kde.kgapi: KGAPI2::AuthJob(0x7f803c0204f0) Dispatching request to
QUrl("https://accounts.google.com/o/oauth2/token;)
org.kde.kgapi.raw:
"client_id=xxx.apps.googleusercontent.com_secret=xxO_token=1/XXX2AYRHP_xJ7tM8IWdBjr6qp_type=refresh_token"
org.kde.kgapi: Received reply from
QUrl("https://accounts.google.com/o/oauth2/token;)
org.kde.kgapi: Status code: 200
org.kde.kgapi.raw: "{\n \"access_token\" :
\"ya29.Gl3iBcqs7CwzyXXXlqAb9Mg5UNJi8bKoId38pwPa76w-9whoIXfw6i6Tkp1QdoItz14TarnpDsk\",\n
\"expires_in\" : 3600,\n \"id_token\" :
\"X-uloczRZpNrsNYzXZPAdZAkGdn3JVbLe9fdqWxeAQEk5mjJxT9xpIvKc6dULa_4EtiaqRSWQhPqCXFGLnxJrjb5_CvZI8TfY5HefyvXM5u4qJ5UYFhsIdEMp0ZyPxqBm1uvtMnG8LalaKL8zbLPH_w9f6J_Rl2jJro1XuAvDmIgTAmPVblUII5JJwfjFOCyBqspi9ox7bOI40EODVtLMgR1YcI0KKiqQ2ip03QkiFUU87rURkX6TkxliX9w6w\",\n
\"token_type\" : \"Bearer\"\n}"
org.kde.kgapi:
qt.network.ssl: QSslSocket::startClientEncryption: cannot start handshake on
non-plain connection
org.kde.pim.imapresource: Expunge failed: "Échec de Purger. Le serveur a
répondu : A000104 NO mailbox selected READ-ONLY "
org.kde.pim.imapresource: Expunge failed: "Échec de Purger. Le serveur a
répondu : A000135 NO mailbox selected READ-ONLY "
org.kde.pim.imapresource: Expunge failed: "Échec de Purger. Le serveur a
répondu : A000231 NO mailbox selected READ-ONLY "
org.kde.pim.kimap: Connection to server lost 0
org.kde.pim.imapresource: Session login cancelled
[SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
![SASL-XOAUTH2] - filling prompts
![SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
!org.kde.pim.imapresource: Expunge failed: "Échec de Purger. Le serveur a
répondu : A000262 NO mailbox selected READ-ONLY "
org.kde.pim.imapresource: Expunge failed: "Échec de Purger. Le serveur a
répondu : A000358 NO mailbox selected READ-ONLY "
org.kde.pim.kimap: Connection to server lost 0
"Item query returned empty result set"
"Item query returned empty result set"
"Item query returned empty result set"
--
You are receiving this mail because:
You are on the CC list for the bug.
