[kmail2] [Bug 359647] New: changing desktop and focus on kmail5 give crash
https://bugs.kde.org/show_bug.cgi?id=359647 Bug ID: 359647 Summary: changing desktop and focus on kmail5 give crash 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: br...@ioda-net.ch Application: kmail (5.1.1) Qt Version: 5.5.1 Operating System: Linux 4.5.0-rc4-2.gea92baf-default x86_64 Distribution: "openSUSE Tumbleweed (20160212) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: after coming back (30 minutes) I changed my desktop from 4 to 3 where kmail was running. Clicking on kmail give me this crash after closing korganizer and kaddressbook. The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcf0623e940 (LWP 3605))] Thread 26 (Thread 0x7fcee04ff700 (LWP 3640)): #0 0x7fcf0327b49d in poll () at /lib64/libc.so.6 #1 0x7fcef620a432 in _xcb_conn_wait (__timeout=-1, __nfds=1, __fds=0x7fcee04feb80) at /usr/include/bits/poll2.h:46 #2 0x7fcef620a432 in _xcb_conn_wait (c=c@entry=0x1c07050, cond=cond@entry=0x1c07090, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:459 #3 0x7fcef620c007 in xcb_wait_for_event (c=0x1c07050) at xcb_in.c:693 #4 0x7fcee2858e29 in QXcbEventReader::run() (this=0x1c14270) at qxcbconnection.cpp:1229 #5 0x7fcf03b8294f in QThreadPrivate::start(void*) (arg=0x1c14270) at thread/qthread_unix.cpp:331 #6 0x7fcef96134a4 in start_thread () at /lib64/libpthread.so.0 #7 0x7fcf03283ded in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7fceddff1700 (LWP 3712)): #0 0x7fcef961bcfc in __lll_lock_wait () at /lib64/libpthread.so.0 #1 0x7fcef9615bb2 in pthread_mutex_lock () at /lib64/libpthread.so.0 #2 0x7fcef812af2c in () at /usr/X11R6/lib64/libGL.so.1 #3 0x7fcef812fe01 in () at /usr/X11R6/lib64/libGL.so.1 #4 0x7fcef81302ab in () at /usr/X11R6/lib64/libGL.so.1 #5 0x7fceed3340f1 in () at /usr/lib64/tls/libnvidia-tls.so.361.28 #6 0x7fcef9138290 in g_wakeup_acknowledge (__nbytes=16, __buf=0x7fceddff0ab0, __fd=) at /usr/include/bits/unistd.h:44 #7 0x7fcef9138290 in g_wakeup_acknowledge (wakeup=0x7fced80015b0) at gwakeup.c:210 #8 0x7fcef90f5dc4 in g_main_context_check (context=context@entry=0x7fced9b0, max_priority=2147483647, fds=fds@entry=0x7fced00013c0, n_fds=n_fds@entry=1) at gmain.c:3632 #9 0x7fcef90f6238 in g_main_context_iterate (context=context@entry=0x7fced9b0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3837 #10 0x7fcef90f639c in g_main_context_iteration (context=0x7fced9b0, may_block=may_block@entry=1) at gmain.c:3901 #11 0x7fcf03da752b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fced8e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #12 0x7fcf03d5163a in QEventLoop::exec(QFlags) (this=this@entry=0x7fceddff0c90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #13 0x7fcf03b7db1c in QThread::exec() (this=) at thread/qthread.cpp:503 #14 0x7fcf03b8294f in QThreadPrivate::start(void*) (arg=0x1dc4a90) at thread/qthread_unix.cpp:331 #15 0x7fcef96134a4 in start_thread () at /lib64/libpthread.so.0 #16 0x7fcf03283ded in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7fcedd16c700 (LWP 3830)): #0 0x7fcef961bcfc in __lll_lock_wait () at /lib64/libpthread.so.0 #1 0x7fcef9615bb2 in pthread_mutex_lock () at /lib64/libpthread.so.0 #2 0x7fcef812af2c in () at /usr/X11R6/lib64/libGL.so.1 #3 0x7fcef812fe01 in () at /usr/X11R6/lib64/libGL.so.1 #4 0x7fcef81302ab in () at /usr/X11R6/lib64/libGL.so.1 #5 0x7fceed3340f1 in () at /usr/lib64/tls/libnvidia-tls.so.361.28 #6 0x7fcef9138290 in g_wakeup_acknowledge (__nbytes=16, __buf=0x7fcedd16bab0, __fd=) at /usr/include/bits/unistd.h:44 #7 0x7fcef9138290 in g_wakeup_acknowledge (wakeup=0x7fced00025a0) at gwakeup.c:210 #8 0x7fcef90f5dc4 in g_main_context_check (context=context@entry=0x7fced40009b0, max_priority=2147483647, fds=fds@entry=0x7fced40013c0, n_fds=n_fds@entry=1) at gmain.c:3632 #9 0x7fcef90f6238 in g_main_context_iterate (context=context@entry=0x7fced40009b0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3837 #10 0x7fcef90f639c in g_main_context_iteration (context=0x7fced40009b0, may_block=may_block@entry=1) at gmain.c:3901 #11 0x7fcf03da752b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fced40008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #12 0x7fcf03d5163a in QEventLoop::exec(QFlags) (this=this@entry=0x7fcedd16bc90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #13
[Akonadi] [Bug 351814] Kmail 15.08 will not sync Outlook365 IMAP Folders
https://bugs.kde.org/show_bug.cgi?id=351814 --- Comment #27 from Jan-Matthias Braun--- Hi! I do have the impression that this issue came back with 15.12.: My outlook imap is not syncing anymore. Does somebody else see the same behaviour? Can the fix somehow have evaded going into 15.12 or should I open a new bug report? All the best, Jan -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 354056] Deleted emails stay, but greyed out
https://bugs.kde.org/show_bug.cgi?id=354056 Sebastian Gruenerchanged: What|Removed |Added CC||sgrue...@uni-potsdam.de --- Comment #20 from Sebastian Gruener --- I can confirm this on Kmail 5.1.2, Akonadi 5.1.51, KDE Framework 5.19, Qt 5.5.1 (Packages from Opensuse Tumbleweed) I encounter this bug with 2 of my 3 imap-accounts, unfortunately I don't know which software they are using. This bug is reproducible even after deleting akonadi-databases[1] If I add the accounts again, Akonadi even builds it's indexes with greyed-out e-mails. They seem to be deleted in my webmail-interface. These emails can't be accessed through kmail (they're just showing up). I can't access them via browser-tab in akonadiconsole either (because of this bug: https://bugs.kde.org/show_bug.cgi?id=355229) BUT: In akonadiconsole DB-Browser-Tab "pimitemtable" there are entries with remoteID-values that are not shown/indexed by Thunderbird [2] . The big question now is, why is Akonadi indexing mails, that Thunderbird/$Webmail isn't? [1] https://docs.kde.org/trunk5/en/kdepim/kmail/clean-start-after-a-failed-migration.html [2] In Thunderbird you can sort mails and show "Order Recieved", which I think is the same number as is the remoteID in akonadi. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 358696] KF5's kaddressbook crashes when adding a contact that has a birthday
https://bugs.kde.org/show_bug.cgi?id=358696 --- Comment #3 from eric--- Created attachment 97344 --> https://bugs.kde.org/attachment.cgi?id=97344=edit Trace of addressbook right after adding a contact with a birthday. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 355229] akonadiconsole browser does not show any resource entries
https://bugs.kde.org/show_bug.cgi?id=355229 Sebastian Gruenerchanged: What|Removed |Added CC||sgrue...@uni-potsdam.de --- Comment #3 from Sebastian Gruener --- I can confirm this with akonadiconsole 0.99, Akonadi 5.1.51, KDE Framework 5.19, Qt 5.5.1 (Packages from Opensuse Tumbleweed) -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 358696] KF5's kaddressbook crashes when adding a contact that has a birthday
https://bugs.kde.org/show_bug.cgi?id=358696 ericchanged: What|Removed |Added CC||pro...@gmx.net --- Comment #2 from eric --- This still happens with KF-5.19.0 and akonadi/korganizer/kaddressbook-15.12.2. Kaddressbook will crash after creating/importing a contact with a birthday and/or anniversary, when contact has no birthday or anniversary no crash will happen. After this crash kaddressbook and korganizer are not usable anymore, because kaddressbook will always crash when started, and korganizer will crash when selecting the to-do or event view or when adding a new to-do or event. Korganizer is only usable when it is only used for viewing the monthly/weekly/daily calendar. This all is tested on a completely empty (newly created) home directory and also tested with both the MySQL (MariaDB) and SQLite3 database engines. Other information: Qt-5.5.1, Glibc-2.22, the system is 32bits and the filesystem is BtrFS with zlib compression. The backtrace is said to be unusable, but I'll attach anyway. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 359393] Kmail message list doesnt show pictures/images in message body
https://bugs.kde.org/show_bug.cgi?id=359393 naughtyp...@openmailbox.orgchanged: What|Removed |Added CC||naughtyp...@openmailbox.org -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs