[kmail2] [Bug 397825] [Wayland] Message viewer displays only a black rectangle
https://bugs.kde.org/show_bug.cgi?id=397825 Robert Riemann changed: What|Removed |Added CC||rob...@riemann.cc --- Comment #21 from Robert Riemann --- I am on opensuse Tumbleweed and when I use Plasma Wayland (native/full), I also get either a black window or the window behind kmail. I am on Kontact version 5.15.3 (20.08.3). Name : kmail Version: 20.08.3-1.1 Arch : x86_64 Vendor : openSUSE Installed Size : 6.0 MiB Installed : Yes (automatically) Status : up-to-date Source package : kmail-20.08.3-1.1.src Name : libwayland-server0/client0 Version: 1.18.0-1.4 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 428762] Akonadi is asking for gmail authentication every 10ish minutes?
https://bugs.kde.org/show_bug.cgi?id=428762 Robert Riemann changed: What|Removed |Added CC||rob...@riemann.cc --- Comment #23 from Robert Riemann --- Same issue since I updated yesterday my opensuse tumbleweed to VERSION_ID="20201227" (from /etc/os-release) -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 457110] New: privacy: Google Maps opens when user click on address
https://bugs.kde.org/show_bug.cgi?id=457110 Bug ID: 457110 Summary: privacy: Google Maps opens when user click on address Product: kontact Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: contacts Assignee: kdepim-bugs@kde.org Reporter: rob...@riemann.cc Target Milestone: --- This is a feature request. When I add to contacts an address and then browse later to that contact, I find in the contact overview the address and can click on it. This opens the address on Google Maps. I think it is against the spirit of free software and KDE to redirect the user without prior opt-in to Google Maps. Hence, I suggest that we make this configurable as we do already for phone numbers and SMS. Maybe it is an option to use the geo: URI handler instead and configure the behaviour on OS level? Alternatively, we could offer: 1. open in Marble 2. open on OpenStreetMap 3. open using a self-configured URL -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 338054] New: recipient is marked invalid because of at in caption and mail in brackets
https://bugs.kde.org/show_bug.cgi?id=338054 Bug ID: 338054 Summary: recipient is marked invalid because of at in caption and mail in brackets Product: kmail2 Version: 4.11.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: rob...@riemann.cc I wanted to send a mail to: a...@listes.what.ever and I couldn't because this recipient doesn't pass validation. I believe that this should pass and consider thus the validation as malformed. What is your opinion about this? I think I got mails with a recipient like this. Reproducible: Always Steps to Reproduce: 1. just put "a...@listes.what.ever " in the recipient list 2. try to send the mail 3. an alert pops out and the mail doesn't get sent Actual Results: cannot send mail Expected Results: recipient should be valid -- 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 78816] Hashcash support for Kmail
https://bugs.kde.org/show_bug.cgi?id=78816 Robert Riemann changed: What|Removed |Added CC||rob...@riemann.cc --- Comment #20 from Robert Riemann --- I don't have any idea of the source code of kmail2, but I guess that this would be a nice junior job: - add a checkmark option to the mail editor dialog (tab meta data) to enable the hashcash challenge. - optionally: provide a spin to determine the work load (how many zeros to find) - study the hashtag code from existing projects and 'copy'n'paste' it to the right place in kmail2's code. If I find a free day, I could even imagine to do it my self (I haven't made yet my hands dirty with kmail development). -- 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 78816] Hashcash support for Kmail
https://bugs.kde.org/show_bug.cgi?id=78816 --- Comment #21 from Robert Riemann --- a kmail related resource of the hashcash project: http://www.hashcash.org/mail/mua/kmail/ -- 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
[kontact] [Bug 341093] New: kontact crashes during session restore after restart due to power outage
https://bugs.kde.org/show_bug.cgi?id=341093 Bug ID: 341093 Summary: kontact crashes during session restore after restart due to power outage Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: rob...@riemann.cc Application: kontact (4.14.2) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.16.6-2-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" - What I was doing when the application crashed: I logged in to KDE and kontact restarted (session restore) and crashed immediately - Unusual behavior I noticed: The desktop was not shut-down correctly, because of a power outage (battery em Reproducible: Didn't try -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0ccb143800 (LWP 3783))] Thread 5 (Thread 0x7f0cad833700 (LWP 3887)): #0 0x7f0cc277005f in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f0cc5f01686 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f0cc5f016b9 in () at /usr/lib64/libQtWebKit.so.4 #3 0x7f0cc276c0a4 in start_thread (arg=0x7f0cad833700) at pthread_create.c:309 #4 0x7f0cc86df7fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7f0c6cf10700 (LWP 3891)): #0 0x7f0cc277005f in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f0cc5c73e7d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f0cc5f291e6 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x7f0cc276c0a4 in start_thread (arg=0x7f0c6cf10700) at pthread_create.c:309 #4 0x7f0cc86df7fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7f0c59a68700 (LWP 4205)): #0 0x7f0cc86d73cd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f0cc21a0be4 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f0cc21a0cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f0cc8e5a0de in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f0c540008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #4 0x7f0cc8e2be6f in QEventLoop::processEvents(QFlags) (this=this@entry=0x7f0c59a67de0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f0cc8e2c165 in QEventLoop::exec(QFlags) (this=this@entry=0x7f0c59a67de0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f0cc8d290bf in QThread::exec() (this=) at thread/qthread.cpp:538 #7 0x7f0cc8d2b79f in QThreadPrivate::start(void*) (arg=0x1f044d0) at thread/qthread_unix.cpp:349 #8 0x7f0cc276c0a4 in start_thread (arg=0x7f0c59a68700) at pthread_create.c:309 #9 0x7f0cc86df7fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f0c51271700 (LWP 4386)): #0 0x7f0cc86d73cd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f0cc21a0be4 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f0cc21a0cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f0cc8e5a0de in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f0c480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #4 0x7f0cc8e2be6f in QEventLoop::processEvents(QFlags) (this=this@entry=0x7f0c51270da0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f0cc8e2c165 in QEventLoop::exec(QFlags) (this=this@entry=0x7f0c51270da0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f0cc8d290bf in QThread::exec() (this=this@entry=0x65f11a0) at thread/qthread.cpp:538 #7 0x7f0cc8e0d783 in QInotifyFileSystemWatcherEngine::run() (this=0x65f11a0) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x7f0cc8d2b79f in QThreadPrivate::start(void*) (arg=0x65f11a0) at thread/qthread_unix.cpp:349 #9 0x7f0cc276c0a4 in start_thread (arg=0x7f0c51271700) at pthread_create.c:309 #10 0x7f0cc86df7fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f0ccb143800 (LWP 3783)): [KCrash Handler] #6 0x7f0c5d6d2da3 in Akregator::Feed::slotAddToFetchQueue(Akregator::FetchQueue*, bool) () at /usr/lib64/libakregatorprivate.so.4 #7 0x7f0c5d6e82e8 in Akregator::Folder::slotAddToFetchQueue(Akregator::FetchQueue*, bool) () at /usr/lib64/libakregatorprivate.so.4 #8 0x7f0cc8e411fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=0x2a7c590, m=, local_signal_index=, argv=0x0) at kernel/qobject.cpp:3576 #9 0x7f0cc8e453b1 in QObject::event(QEvent*) (this=0x2a7c590, e=) at kernel/qobject.cpp:1193 #10 0x7f0cc983b76c in QApplicationPrivate::n
[kmail2] [Bug 255104] KMail fails to start with: Could not create collection
https://bugs.kde.org/show_bug.cgi?id=255104 Robert Riemann changed: What|Removed |Added CC||rob...@riemann.cc --- Comment #15 from Robert Riemann --- I ran into the same issue with a new install of KDE with 4.14.3. The proposed work-around via akonadiconsole worked for me. -- 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
[kontact] [Bug 344085] New: kontact crashed when changing printer settings
https://bugs.kde.org/show_bug.cgi?id=344085 Bug ID: 344085 Summary: kontact crashed when changing printer settings Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: rob...@riemann.cc Application: kontact (4.14.4) KDE Platform Version: 4.14.4 Qt Version: 4.8.6 Operating System: Linux 3.16.7-7-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: - I opened a mail in html mode. - I open the printing dialog - I chosed a printer and changed the printer settings. - I changed the printer and wanted to change again its settings (the table view) Kontact crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2474a37800 (LWP 2837))] Thread 6 (Thread 0x7f2456bc6700 (LWP 2864)): #0 0x7f246c05405f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f246f7e5686 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f246f7e56b9 in () at /usr/lib64/libQtWebKit.so.4 #3 0x7f246c0500a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2471fc47fd in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f24162ab700 (LWP 2886)): #0 0x7f246c05405f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f246f557e7d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f246f80d1e6 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x7f246c0500a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2471fc47fd in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f2402a3a700 (LWP 3224)): #0 0x7f246bac68e9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f246ba84299 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f246ba84b03 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f246ba84cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f247273f0de in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f2472710e6f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f2472711165 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #7 0x7f247260e0bf in QThread::exec() () at /usr/lib64/libQtCore.so.4 #8 0x7f247261079f in () at /usr/lib64/libQtCore.so.4 #9 0x7f246c0500a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f2471fc47fd in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f23f1b9a700 (LWP 17880)): #0 0x7f246c05405f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2472610c86 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f24735f8996 in () at /usr/lib64/libQtGui.so.4 #3 0x7f247261079f in () at /usr/lib64/libQtCore.so.4 #4 0x7f246c0500a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f2471fc47fd in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f2401ae9700 (LWP 17881)): #0 0x7f2471fbc3cd in poll () at /lib64/libc.so.6 #1 0x7f246ba84be4 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f246ba84cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f247273f0de in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7f2472710e6f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f2472711165 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f247260e0bf in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7f24726f2783 in () at /usr/lib64/libQtCore.so.4 #8 0x7f247261079f in () at /usr/lib64/libQtCore.so.4 #9 0x7f246c0500a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f2471fc47fd in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f2474a37800 (LWP 2837)): [KCrash Handler] #5 0x7f24735aa8eb in () at /usr/lib64/libQtGui.so.4 #6 0x7f2473664989 in () at /usr/lib64/libQtGui.so.4 #7 0x7f2473664a73 in QItemSelection::indexes() const () at /usr/lib64/libQtGui.so.4 #8 0x7f247366a798 in () at /usr/lib64/libQtGui.so.4 #9 0x7f247366af29 in () at /usr/lib64/libQtGui.so.4 #10 0x7f24727261fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #11 0x7f24735ae502 in () at /usr/lib64/libQtGui.so.4 #12 0x7f24735ae6f3 in () at /usr/lib64/libQtGui.so.4 #13 0x7f24735b0139 in () at /usr/lib64/libQtGui.so.4 #14 0x7f24727261fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/li
[kontact] [Bug 346774] New: kontact crashes when I click on link in vcard mail
https://bugs.kde.org/show_bug.cgi?id=346774 Bug ID: 346774 Summary: kontact crashes when I click on link in vcard mail Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: rob...@riemann.cc Application: kontact (4.14.6) KDE Platform Version: 4.14.6 Qt Version: 4.8.6 Operating System: Linux 3.16.7-7-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I got an invitation mail including a meeting.ics file. The rendered inline attachment offers some actions to respond like 'Accept', 'Decline', 'Check my calender'. I clicked on 'my calender' and Kontact crashed. I just restarted the app and clicked again and was redirected to the Kontact Calender app. So I couldn't repoduce this. However, I hope that the backtrace is usefull. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9a65d92800 (LWP 4487))] Thread 4 (Thread 0x7f9a47af4700 (LWP 4500)): #0 0x7f9a5d3a205f in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9a60b42686 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f9a60b426b9 in () at /usr/lib64/libQtWebKit.so.4 #3 0x7f9a5d39e0a4 in start_thread (arg=0x7f9a47af4700) at pthread_create.c:309 #4 0x7f9a6332406d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7f9a071d9700 (LWP 4513)): #0 0x7f9a5d3a205f in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9a608b4e7d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f9a60b6a1e6 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x7f9a5d39e0a4 in start_thread (arg=0x7f9a071d9700) at pthread_create.c:309 #4 0x7f9a6332406d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f99f3928700 (LWP 4760)): #0 0x7fff0b7fcd16 in () #1 0x7f99 in () #2 0x in ()#3 0x in ()#4 0x in ()#5 0x in ()#6 0x7fff7f99 in () #7 0x63a9e000 in () #8 0x in ()#9 0x63330cad7f99 in () #10 0x7fff7f9a in () #11 0x639c3d47 in () #12 0x027631a07f9a in () #13 0x in ()#14 0x25267f99 in () #15 0x in () Thread 1 (Thread 0x7f9a65d92800 (LWP 4487)): [KCrash Handler] #5 0x7f9a63274187 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #6 0x7f9a63275538 in __GI_abort () at abort.c:78 #7 0x7f9a639652b4 in qt_message_output(QtMsgType, char const*) (msgType=msgType@entry=QtFatalMsg, buf=) at global/qglobal.cpp:2359 #8 0x7f9a63965439 in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, msg=0x7f99fd213708 "Fatal Error: Accessed global static '%s *%s()' after destruction. Defined at %s:%d", ap=ap@entry=0x7fff0b6b5168) at global/qglobal.cpp:2405 #9 0x7f9a63965c44 in qFatal(char const*, ...) (msg=) at global/qglobal.cpp:2588 #10 0x7f99fd166224 in MailCommon::Kernel::self() () at /usr/lib64/libmailcommon.so.4 #11 0x7f99fd1ab870 in MailCommon::FolderCollection::writeConfig() const () at /usr/lib64/libmailcommon.so.4 #12 0x7f99fd1ac072 in MailCommon::FolderCollection::~FolderCollection() () at /usr/lib64/libmailcommon.so.4 #13 0x7f99fd1ac0e9 in MailCommon::FolderCollection::~FolderCollection() () at /usr/lib64/libmailcommon.so.4 #14 0x7f99fd1aa9a4 in () at /usr/lib64/libmailcommon.so.4 #15 0x7f9a63276bf9 in __run_exit_handlers (status=255, listp=0x7f9a635e05a8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 #16 0x7f9a63276c45 in __GI_exit (status=) at exit.c:104 #17 0x7f9a63f14c1b in () at /usr/lib64/libkdecore.so.5 #18 0x00404087 in _start () Possible duplicates by query: bug 335011. Reported using DrKonqi -- 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 404790] New: delete expired messages permanently: extra confirm dialogue
https://bugs.kde.org/show_bug.cgi?id=404790 Bug ID: 404790 Summary: delete expired messages permanently: extra confirm dialogue Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: rob...@riemann.cc Target Milestone: --- This is a wishlist item to avoid unintentional batch deleting of mails. I configured the expiration of some IMAP folders in KMail2 for the first time. There are two options: 1) Move expired message to … 2) Delete expired messages permanently (default) If the user (me) forgets to configure a folder for (1) and presses directly on the button "save settings and expire", than messages are permanently lost. Henceforth, I suggest to add a security question dialogue popping up when (2) is still selected, asking if one really has the intention to delete mails permanently. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 418356] New: Kontact crashes when I clicked on the button "Answer All" in mail view
https://bugs.kde.org/show_bug.cgi?id=418356 Bug ID: 418356 Summary: Kontact crashes when I clicked on the button "Answer All" in mail view Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: rob...@riemann.cc Target Milestone: --- Application: kontact (5.13.1 (19.12.1)) Qt Version: 5.14.0 Frameworks Version: 5.66.0 Operating System: Linux 5.4.13-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was reading a text mail and clicked then on answer all. Before the mail composer window opened, the app crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6d81592ac0 (LWP 1842))] Thread 25 (Thread 0x7f6d47fff700 (LWP 26431)): #0 0x7f6d8fc919ca in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6d8a5ef756 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x921b in () #3 0x073f3b55 in () #4 0x91fa in () #5 0x073f4edd in () #6 0x in () Thread 24 (Thread 0x7f6d5e7fc700 (LWP 20875)): #0 0x7f6d8fc919ca in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6d8a5ef756 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x9223 in () #3 0x077ae59e in () #4 0x9202 in () #5 0x077ae986 in () #6 0x in () Thread 23 (Thread 0x7f6cea1e2700 (LWP 20845)): #0 0x7f6d922a1abf in poll () at /lib64/libc.so.6 #1 0x7f6d85cd34f2 in () at /usr/lib64/libpulse.so.0 #2 0x7f6d85cc4e39 in pa_mainloop_poll () at /usr/lib64/libpulse.so.0 #3 0x7f6d85cc54bf in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7f6d85cc5570 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7f6d85cd3439 in () at /usr/lib64/libpulse.so.0 #6 0x7f6d8411ac78 in () at /usr/lib64/pulseaudio/libpulsecommon-13.0.so #7 0x7f6d8fc8af2a in start_thread () at /lib64/libpthread.so.0 #8 0x7f6d922ac38f in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f6cea9e3700 (LWP 17432)): #0 0x7f6d8f1f0600 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f6d8f1a486d in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f6d8f1a521b in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f6d8f1a540f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f6d90ebebdb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f6d90e66d5b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f6d90c9263e in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f6d90c93708 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f6d8fc8af2a in start_thread () at /lib64/libpthread.so.0 #9 0x7f6d922ac38f in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f6d04c70700 (LWP 10884)): #0 0x7f6d922a6f39 in syscall () at /lib64/libc.so.6 #1 0x7f6d90c958b1 in QSemaphore::acquire(int) () at /usr/lib64/libQt5Core.so.5 #2 0x7f6d8fdc4714 in () at /usr/lib64/libQt5Network.so.5 #3 0x7f6d90c93708 in () at /usr/lib64/libQt5Core.so.5 #4 0x7f6d8fc8af2a in start_thread () at /lib64/libpthread.so.0 #5 0x7f6d922ac38f in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f6d05471700 (LWP 8770)): #0 0x7f6d922a1abf in poll () at /lib64/libc.so.6 #1 0x7f6d8f1a52ee in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f6d8f1a540f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f6d90ebebdb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f6d90e66d5b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f6d90c9263e in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f6d90c93708 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f6d8fc8af2a in start_thread () at /lib64/libpthread.so.0 #8 0x7f6d922ac38f in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f6d06ffe700 (LWP 2757)): #0 0x7f6d8f1f0604 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f6d8f1a4811 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f6d8f1a521b in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f6d8f1a540f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f6d90ebebdb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f6d90e66d5b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f6d90c9263e in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7
[kontact] [Bug 382936] New: Kontact/Kmail crashes on lunch
https://bugs.kde.org/show_bug.cgi?id=382936 Bug ID: 382936 Summary: Kontact/Kmail crashes on lunch Product: kontact Version: 5.4.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: rob...@riemann.cc Target Milestone: --- Application: kontact (5.4.2) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.1-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Sometimes my computer freezes (Thinkpad running opensuse) and I decide to do a hard reboot. Afterwards, Kontact got autostarted and freezed. I did right afterwards a normal reboot and got the same behaviour. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ffae8c60e00 (LWP 4855))] Thread 26 (Thread 0x7ff9b6e80700 (LWP 5060)): #0 0x7ffadf350f49 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7ffadf30ad89 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7ffadf30b7bb in () at /usr/lib64/libglib-2.0.so.0 #3 0x7ffadf30b9ac in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7ffae61bc18b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7ffae6165aea in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7ffae5f93813 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7ffae5f984c8 in () at /usr/lib64/libQt5Core.so.5 #8 0x7ffae1525454 in start_thread () at /lib64/libpthread.so.0 #9 0x7ffae568e37f in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7ff9b7681700 (LWP 5057)): #0 0x7ffae568566d in poll () at /lib64/libc.so.6 #1 0x7ffadf30b896 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ffadf30b9ac in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7ffae61bc18b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7ffae6165aea in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7ffae5f93813 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7ffae5f984c8 in () at /usr/lib64/libQt5Core.so.5 #7 0x7ffae1525454 in start_thread () at /lib64/libpthread.so.0 #8 0x7ffae568e37f in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7ff9b8511700 (LWP 5007)): #0 0x7ffae61bb8eb in () at /usr/lib64/libQt5Core.so.5 #1 0x7ffadf30ad7d in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7ffadf30b7bb in () at /usr/lib64/libglib-2.0.so.0 #3 0x7ffadf30b9ac in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7ffae61bc18b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7ffae6165aea in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7ffae5f93813 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7ffae5f984c8 in () at /usr/lib64/libQt5Core.so.5 #8 0x7ffae1525454 in start_thread () at /lib64/libpthread.so.0 #9 0x7ffae568e37f in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7ffa4effd700 (LWP 4940)): #0 0x7ffae152b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ffad233a974 in () at /usr/lib64/libQt5Script.so.5 #2 0x7ffad233a9b9 in () at /usr/lib64/libQt5Script.so.5 #3 0x7ffae1525454 in start_thread () at /lib64/libpthread.so.0 #4 0x7ffae568e37f in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7ffa4f7fe700 (LWP 4934)): #0 0x7ffae152b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ffad84ac609 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7ffad84acc49 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7ffad84ace00 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7ffad84a999c in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7ffae1525454 in start_thread () at /lib64/libpthread.so.0 #6 0x7ffae568e37f in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7ffa4700 (LWP 4904)): #0 0x7ffae152b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ffad84ac609 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7ffad84acc49 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7ffad84ace00 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7ffad84a999c in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7ffae1525454 in start_thread () at /lib64/libpthread.so.0 #6 0x7ffae568e37f in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7ffa98ff9700 (LWP 4903)): #0 0x7ffae568e973 in epoll_wait () at /lib64/libc.so.6 #1 0x7ffad036b7c8 in () at /usr/lib64/libevent-2.1.so.6
[kmail2] [Bug 464972] Kmail cannot properly compose html
https://bugs.kde.org/show_bug.cgi?id=464972 Robert Riemann changed: What|Removed |Added CC||rob...@riemann.cc -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 464972] Kmail cannot properly compose html
https://bugs.kde.org/show_bug.cgi?id=464972 --- Comment #2 from Robert Riemann --- Is this linked to or a duplicate of https://bugs.kde.org/show_bug.cgi?id=344099 ? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 394784] KMAIl 5.8.1: Reply to HTML-mail in text mode includes content from last mail
https://bugs.kde.org/show_bug.cgi?id=394784 Robert Riemann changed: What|Removed |Added CC||rob...@riemann.cc --- Comment #15 from Robert Riemann --- I cannot reproduce this with 5.23.3 (23.04.3) on opensuse Tumbleweed. Can this be closed? -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 473673] New: Calendar Reminders: I click on "remind in 1 hour" and get the same reminder 30 seconds afterwards.
https://bugs.kde.org/show_bug.cgi?id=473673 Bug ID: 473673 Summary: Calendar Reminders: I click on "remind in 1 hour" and get the same reminder 30 seconds afterwards. Classification: Applications Product: kontact Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: calendar Assignee: kdepim-bugs@kde.org Reporter: rob...@riemann.cc Target Milestone: --- Created attachment 161133 --> https://bugs.kde.org/attachment.cgi?id=161133&action=edit todo item screenshot in Kontact STEPS TO REPRODUCE 1. I create my todo items using the Android Tasks.org app for e.g. next Tuesday 2. I wait until Wednesday and get obviously a reminder "Task due" 3. I click on "Remind in 1 hour" OBSERVED RESULT 30 seconds later, I get the reminder again EXPECTED RESULT I only get the reminder 1 hour later. SOFTWARE/OS VERSIONS Linux/KDE Plasma: opensuse Tumbleweed as of 22 August 2023 (available in About System) KDE Plasma Version: 23.04.3 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION I sync my todo items with Nextcloud between my android phone and KDE opensuse computer. I attach a video proof and a screenshot of the todo event in Kontact. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 473673] Calendar Reminders: I click on "remind in 1 hour" and get the same reminder 30 seconds afterwards.
https://bugs.kde.org/show_bug.cgi?id=473673 --- Comment #1 from Robert Riemann --- Created attachment 161134 --> https://bugs.kde.org/attachment.cgi?id=161134&action=edit video showing the problem -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 486836] New: more privacy for event invitees when sending out calendar invitees or share ICS files
https://bugs.kde.org/show_bug.cgi?id=486836 Bug ID: 486836 Summary: more privacy for event invitees when sending out calendar invitees or share ICS files Classification: Applications Product: korganizer Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: invitations Assignee: kdepim-bugs@kde.org Reporter: rob...@riemann.cc Target Milestone: --- I tagged this as a feature request. However, in some regions with strict privacy laws demanding "data minimisation" and privacy by default, this could be interpreted as a legal obligation that would merit a classification as bug. SUMMARY KOrganizer allows to share event details with invitees using two ways: 1. add people as participants 2. right click on event and click on "send as iCalendar..." In both cases, the names and mail addresses of invitees are revealed to other invitees, thus impacting their privacy. Note that in all cases, the actual contact data sharing is not made transparent to the event organiser. STEPS TO REPRODUCE 1. create a new event 2. add two people as invitees 3. see that each invitee can see in the email all other invitees 4. go back to Korganiser and click right on an event in the month view, choose in the context menu "send as iCalendar" and add two mail addresses 5. find in the sent mail folder that both mail addresses are in the "to" instead of "bcc" OBSERVED RESULT Invitees see mail addresses and names of other invitees. EXPECTED RESULT Invitees can only see mail addresses and names of other invitees if the event organiser has made an explicit choice to share this data. Linux/KDE Plasma: 6.0 I am using Kontact flatpak 6.0.2 from the fedora repository. According to some Matrix channel, the fedora flatpak is built the same way like the KDE kontact flatpak on flathub. ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 486837] New: upon new contact creation, KAddressbook always warns: Location was not saved. Do you want to close editor?
https://bugs.kde.org/show_bug.cgi?id=486837 Bug ID: 486837 Summary: upon new contact creation, KAddressbook always warns: Location was not saved. Do you want to close editor? Classification: Applications Product: kaddressbook Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: rob...@riemann.cc Target Milestone: --- Created attachment 169358 --> https://bugs.kde.org/attachment.cgi?id=169358&action=edit screenshot with warning message SUMMARY When I create a new contact or edit an existing contract, I get the following warning even though I have not touched any location-related elements in the contact card: "Location was not saved. Do you want to close editor?" STEPS TO REPRODUCE 1. create a new contact in an addressbook (I use a carddav remote addressbook) 2. add a name and an email address 3. click save 4. see the warning: Location was not saved. Do you want to close editor? OBSERVED RESULT I get a warning that I have to accept. EXPECTED RESULT I only get such a warning if I have changed the location fields. SOFTWARE/OS VERSIONS I am using the fedora repository flatpak of kontact in version 6.0.2. ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 486838] New: flatpak: file dialogue to add attachment has by default no read permission to any files
https://bugs.kde.org/show_bug.cgi?id=486838 Bug ID: 486838 Summary: flatpak: file dialogue to add attachment has by default no read permission to any files Classification: Applications Product: kmail2 Version: 6.0.2 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: rob...@riemann.cc Target Milestone: --- Recently, I switched to Kinoite 40 and installed Kontact as flatpak from the fedora flatpak repository. It is now in version 6.0.2. When I try to draft an email and click on 'add attachment', a file picker opens that cannot see any files. I have then reconfigured the flatpak permissions and added manually create access to all user files and /tmp. I would expect Kmail/Kontact to possess the necessary permissions by default. Reproducible: Always Steps to Reproduce: 1. install fedora kontact flatpak 2. create a new email 3. try to add an attachment using the file picker Actual Results: notice that no file can be selected in file picker Expected Results: I can choose any file from the system in the file picker Down-stream bug report for the Fedora project: https://bugzilla.redhat.com/show_bug.cgi?id=2279924 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 355342] composer mangles mail text on forwarding or edit as new
https://bugs.kde.org/show_bug.cgi?id=355342 Robert Riemann changed: What|Removed |Added CC||rob...@riemann.cc --- Comment #4 from Robert Riemann --- I suggest to close this as no info was provided and nobody complaint since 2017! -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 287540] Webkit based mail composer
https://bugs.kde.org/show_bug.cgi?id=287540 Robert Riemann changed: What|Removed |Added CC||rob...@riemann.cc --- Comment #8 from Robert Riemann --- Blogilo is unmaintained for 6 years according to https://invent.kde.org/unmaintained/blogilo . I suggest to close this feature request. Personally, I also think that html editing is not on par yet with other mail composers, but I wonder if this report is well suited to track this. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 487203] New: flatpak: cannot open kmail mail attachments with default apps or any other app
https://bugs.kde.org/show_bug.cgi?id=487203 Bug ID: 487203 Summary: flatpak: cannot open kmail mail attachments with default apps or any other app Classification: Applications Product: kontact Version: 6.0.2 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: rob...@riemann.cc Target Milestone: --- Created attachment 169601 --> https://bugs.kde.org/attachment.cgi?id=169601&action=edit first dialogue happens when clicking on pdf attachment, second one when clicking on open with SUMMARY I have Kontact with Kmail installed as Flatpak from fedora flatpak repository. When I receive pdfs as attachment, I cannot open them with okular without saving them first to disk. Same issue for any other attachment types. STEPS TO REPRODUCE 1. receive an email with pdf attachment (or other file) 2. click on them for open 3. notice that okular is not an option and app chooser is basically empty OBSERVED RESULT Cannot open with okular EXPECTED RESULT flatpak aplication chooser portal opens and permits to open file with okular ADDITIONAL INFORMATION Related Discussion at https://discussion.fedoraproject.org/t/evolution-flatpak-cant-open-pdf-from-attachments-when-composing-email/24230 Related flatpak bug concerning composing mails with attachment: while granting kontact access to all system files may be good workaround, it would be better to rely on the flatpak open file portal: https://bugs.kde.org/show_bug.cgi?id=486838 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 341941] Reply from the same address the message was sent to
https://bugs.kde.org/show_bug.cgi?id=341941 Robert Riemann changed: What|Removed |Added CC||rob...@riemann.cc --- Comment #1 from Robert Riemann --- I think we should distinguish between two slightly different situations: 2) few non-changing recipients (cake of the bug reporter) Create separate identities for each email address and configure the appropriate SMTP sender. Kmail switch to the respective identity when replying to mails. Furthermore, the identity chooser can also be enabled in the composer view, so that users get an easy drop-down selection field to overwrite the identity on a case-by-case (here email) basis. 2) many non-stable recipients due to the use of sub addressing, e.g. myname+onlinesh...@host.com or mycompany+clie...@host.com Here, it is likely not feasible to setup identities for each sub address. Note that there is no common standard for sub addresses. Sometimes it is "+", sometimes it is "-". Hence, detection is non-trivial. As (1) solves the issue of the bug reporter and (2) is somewhat different, I suggest to either close this bug report as solved or change the title to be explicit that this bug report covers now rather (2). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 394782] Feature Request: Reply with HTML
https://bugs.kde.org/show_bug.cgi?id=394782 Robert Riemann changed: What|Removed |Added CC||rob...@riemann.cc --- Comment #6 from Robert Riemann --- Laurent stated in 2021 that this feature/edge case won't be implemented. Should it be closed as wontfixed? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 411591] Different defaults for reply and forward modes
https://bugs.kde.org/show_bug.cgi?id=411591 Robert Riemann changed: What|Removed |Added CC||rob...@riemann.cc --- Comment #1 from Robert Riemann --- No reaction since 2019. I suggest two work arounds for easy access to "reply to all..." 1) the hotkey by default is "A". Just type a and you can reply to all. 2) you can customise the toolbar and add next/instead of "reply..." the tool button "reply to all". I suggest to close this bug report as INTENTIONAL/WORKSFORME. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 256477] Find replies to a message
https://bugs.kde.org/show_bug.cgi?id=256477 Robert Riemann changed: What|Removed |Added CC||rob...@riemann.cc -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 487203] flatpak: cannot open kmail mail attachments with default apps or any other app
https://bugs.kde.org/show_bug.cgi?id=487203 --- Comment #1 from Robert Riemann --- I have switched to the flatpak from the flathub repository at https://github.com/flathub/org.kde.kontact . Same problem with the version 5.24.4 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 231925] New: account data akonadi googledata
https://bugs.kde.org/show_bug.cgi?id=231925 Summary: account data akonadi googledata Product: kontact Version: 4.4.1 Platform: openSUSE RPMs OS/Version: unspecified Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: robert.riem...@physik.hu-berlin.de Version:(using KDE 4.4.1) Installed from:openSUSE RPMs I am not sure if this is the right place to report bugs for akonadi... The akonadi googledata modules require in its settings the account information. There is a little hint, that to the given username "@gmail.com" will be append, but the german google mail accounts have the prefix "@googlemail.com" due to patent issues. Either the hint is misleading or it is wrong. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 231925] account data akonadi googledata
https://bugs.kde.org/show_bug.cgi?id=231925 --- Comment #2 from Robert Riemann 2010-06-16 01:47:44 --- is this fixed already in recent kde? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 273949] Akonadi Resource always seen as readonly
https://bugs.kde.org/show_bug.cgi?id=273949 Robert Riemann changed: What|Removed |Added CC||salout...@googlemail.com -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 294911] New: Kmail crashes on start (while Akonadi is misbehaving)
https://bugs.kde.org/show_bug.cgi?id=294911 Summary: Kmail crashes on start (while Akonadi is misbehaving) Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: salout...@googlemail.com Application: kmail (4.8.0) KDE Platform Version: 4.8.00 (4.8.0 "release 2" Qt Version: 4.8.0 Operating System: Linux 3.1.9-1.4-desktop x86_64 Distribution: "openSUSE 12.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I logged into my KDE system. KMail got autostarted to restore the session. - Unusual behavior I noticed: Akonadi doesn't seem to work. Starting akonadiconsole gives: "/usr/bin/akonadiconsole(5166)" Soprano: "org.freedesktop.DBus.Error.ServiceUnknown - The name org.kde.nepomuk.services.nepomukstorage was not provided by any .service files" The crash can be reproduced some of the time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #6 Private (other=..., this=0x7fffae8bef10) at kernel/qvariant.h:356 #7 QVariant::QVariant (this=0x7fffae8bef10, p=...) at kernel/qvariant.cpp:1411 #8 0x7fea4a1182a8 in QDBusPendingReplyData::argumentAt (this=0x7fffae8bef70, index=0) at qdbuspendingreply.cpp:270 #9 0x7fea4874dec9 in argumentAt<0> (this=0x7fffae8bef70) at /usr/include/QtDBus/qdbuspendingreply.h:176 #10 operator QDBusPendingReplyTypes::Select<0, QDBusObjectPath, void, void, void, void, void, void, void>::Type (this=0x7fffae8bef70) at /usr/include/QtDBus/qdbuspendingreply.h:186 #11 Akonadi::ChangeNotificationDependenciesFactory::createNotificationSource (this=, parent=0xafe918) at /usr/src/debug/kdepimlibs-4.8.0/akonadi/changenotificationdependenciesfactory.cpp:39 #12 0x7fea486e0049 in Akonadi::MonitorPrivate::connectToNotificationManager (this=0xaa57d0) at /usr/src/debug/kdepimlibs-4.8.0/akonadi/monitor_p.cpp:79 #13 0x7fea4875d60c in Akonadi::Monitor::Monitor (this=0xafe918, parent=) at /usr/src/debug/kdepimlibs-4.8.0/akonadi/monitor.cpp:45 #14 0x7fea454c3d6d in MessageViewer::ViewerPrivate::ViewerPrivate (this=0xafe6e0, aParent=0xa96820, mainWindow=0xa4d650, actionCollection=0x8b1690) at /usr/src/debug/kdepim-4.8.0/messageviewer/viewer_p.cpp:202 #15 0x7fea454ac2da in MessageViewer::Viewer::Viewer (this=0xa96820, aParent=, mainWindow=0xa4d650, actionCollection=0x8b1690, aFlags=) at /usr/src/debug/kdepim-4.8.0/messageviewer/viewer.cpp:50 #16 0x7fea4daef3af in KMReaderWin::KMReaderWin (this=0xaa9b70, aParent=, mainWindow=0xa4d650, actionCollection=, aFlags=) at /usr/src/debug/kdepim-4.8.0/kmail/kmreaderwin.cpp:106 #17 0x7fea4db4b628 in KMMainWidget::createWidgets (this=0xa4d650) at /usr/src/debug/kdepim-4.8.0/kmail/kmmainwidget.cpp:1058 #18 0x7fea4db4c1a5 in KMMainWidget::KMMainWidget (this=0xa4d650, parent=, aGUIClient=0xa4e1f0, actionCollection=, config=...) at /usr/src/debug/kdepim-4.8.0/kmail/kmmainwidget.cpp:249 #19 0x7fea4dab6fe5 in KMMainWin::KMMainWin (this=0xa4e190, __in_chrg=, __vtt_parm=) at /usr/src/debug/kdepim-4.8.0/kmail/kmmainwin.cpp:65 #20 0x7fea4db01407 in KMKernel::openReader (this=0x7fffae8c2a50, onlyCheck=false) at /usr/src/debug/kdepim-4.8.0/kmail/kmkernel.cpp:561 #21 0x7fea4db026e8 in KMKernel::action (this=0x7fffae8c2a50, mailto=, check=false, to=..., cc=..., bcc=..., subj=..., body=..., messageFile=..., attachURLs=..., customHeaders=...) at /usr/src/debug/kdepim-4.8.0/kmail/kmkernel.cpp:1300 #22 0x7fea4db031df in KMKernel::handleCommandLine (this=0x7fffae8c2a50, noArgsOpensReader=true) at /usr/src/debug/kdepim-4.8.0/kmail/kmkernel.cpp:477 #23 0x00403457 in KMailApplication::newInstance (this=0x7fffae8c2b20) at /usr/src/debug/kdepim-4.8.0/kmail/main.cpp:85 #24 0x7fea4e775f42 in ?? () from /usr/lib64/libkdeui.so.5 #25 0x7fea4e775fc4 in ?? () from /usr/lib64/libkdeui.so.5 #26 0x7fea4e77610b in ?? () from /usr/lib64/libkdeui.so.5 #27 0x7fea4a0dbf6b in QDBusConnectionPrivate::deliverCall (this=0x64c260, object=0x80d8b0, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:947 #28 0x7fea4a0dd07d in QDBusConnectionPrivate::activateCall (this=0x64c260, object=0x80d8b0, flags=337, msg=...) at qdbusintegrator.cpp:850 #29 0x7fea4a0dda9b in QDBusConnectionPrivate::activateObject (this=0x64c260, node=..., msg=..., pathStartPos=) at qdbusintegrator.cpp:1423 #30 0x7fea4a0ddb8b in QDBusActivateObjectEvent::placeMetaCall (this=0xa48400) at qdbusintegrator.cpp:1537 #31 0x7fea4d6df926 in QObject::event (this=0x7fffae8c2b20, e=) at kernel/qobject.cpp:1204 #32 0x7fea4ca4fd84 in QApplication::event(QEvent*) () from /usr/lib64/libQtGui.so.4 #33 0x7fea4ca4be84 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #34 0x7fea4ca50d03 in QApplica
[Bug 295872] Kmail 4.8.1 crashes when reading email GMail IMAP folder
https://bugs.kde.org/show_bug.cgi?id=295872 Robert Riemann changed: What|Removed |Added CC||salout...@googlemail.com -- 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
[Bug 295872] Kmail 4.8.1 crashes when reading email GMail IMAP folder
https://bugs.kde.org/show_bug.cgi?id=295872 --- Comment #2 from Robert Riemann --- Created attachment 69567 --> https://bugs.kde.org/attachment.cgi?id=69567&action=edit New crash information added by DrKonqi kmail (4.8.0) on KDE Platform 4.8.1 (4.8.1) "release 478" using Qt 4.8.0 - What I was doing when the application crashed: When the application crashed, I was just reading my gmail account. I also have big folders (inbox, kde mailinglist, etc.). -- Backtrace (Reduced): #13 0x7f267721c558 in QByteArray::realloc (this=0x7f26040203e8, alloc=65504) at tools/qbytearray.cpp:1452 #14 0x7f267721c679 in QByteArray::resize (this=0x7f26040203e8, size=32768) at tools/qbytearray.cpp:1420 #15 0x7f2674d0f986 in reserve (bytes=2, this=0x7f2604002d70) at ../../src/corelib/tools/qringbuffer_p.h:158 #16 QAbstractSocket::writeData (this=, data=0x7f26130ee62c "\021", size=2) at socket/qabstractsocket.cpp:2315 #17 0x7f26772aa82f in QIODevice::write (this=0x7f26040180c0, data=0x7f26130ee62c "\021", maxSize=) at io/qiodevice.cpp:1370 -- 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
[Bug 296896] New: KMail crashes when clicking a mail
https://bugs.kde.org/show_bug.cgi?id=296896 Bug ID: 296896 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: KMail crashes when clicking a mail Classification: Unclassified OS: Linux Reporter: salout...@googlemail.com Hardware: openSUSE RPMs Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.0) KDE Platform Version: 4.8.1 (4.8.1) "release 478" Qt Version: 4.8.0 Operating System: Linux 3.1.9-1.4-desktop x86_64 Distribution: "openSUSE 12.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I have a disconnected IMAP (GMail) resource. The KDE folder holds more than 1e3 mails. I just clicked one mail of the more recent and the application crashed. Konsole Output: kmail2(10210) MessageList::Core::ModelPrivate::findMessageParent: Circular In-Reply-To reference loop detected in the message tree kmail2(10210) MessageList::Core::ModelPrivate::viewItemJobStepInternalForJobPass1Fill: Circular In-Reply-To reference loop detected in the message tree kmail2(10210) MessageList::Core::ModelPrivate::findMessageParent: Circular In-Reply-To reference loop detected in the message tree kmail2(10210)/kdeui (KWindowInfo) KWindowInfo::state: Pass NET::WMState to KWindowInfo kmail2(10210)/kdeui (KWindowInfo) KWindowInfo::state: Pass NET::WMState to KWindowInfo *** glibc detected *** kmail: double free or corruption (fasttop): 0x7f9ddc0811e0 *** *** KMail got signal 11 (Exiting) *** Dead letters dumped. === Backtrace: = /lib64/libc.so.6(+0x766d6)[0x7f9e4b0546d6] /usr/lib64/libQtDBus.so.4(+0x5a54e)[0x7f9e4913054e] -- Backtrace: Application: KMail (kmail), signal: Aborted [Current thread is 1 (Thread 0x7f9e4dd79780 (LWP 10210))] Thread 5 (Thread 0x7f9e2fa8a700 (LWP 10214)): #0 0x7f9e48ec4e6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9e3f57dc12 in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7f9e3f57dc49 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x7f9e48ec0f05 in start_thread () from /lib64/libpthread.so.0 #4 0x7f9e4b0b910d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f9e2f189700 (LWP 10215)): #0 0x7f9e48ec411f in __pthread_mutex_unlock_usercnt () from /lib64/libpthread.so.0 #1 0x7f9e43297a8c in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f9e43297f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f9e4c715956 in QEventDispatcherGlib::processEvents (this=0x7f9e280008c0, flags=) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f9e4c6e5682 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f9e4c6e58d7 in QEventLoop::exec (this=0x7f9e2f188e00, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f9e4c5e6537 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x7f9e4c5e955b in QThreadPrivate::start (arg=0xcc30d0) at thread/qthread_unix.cpp:298 #8 0x7f9e48ec0f05 in start_thread () from /lib64/libpthread.so.0 #9 0x7f9e4b0b910d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f9e2ce6d700 (LWP 21593)): [KCrash Handler] #10 0x7f9e4b054a30 in malloc_consolidate () from /lib64/libc.so.6 #11 0x7f9e4b055bf3 in _int_malloc () from /lib64/libc.so.6 #12 0x7f9e4b05883e in malloc () from /lib64/libc.so.6 #13 0x7f9e4c5eb558 in QByteArray::realloc (this=0x7f9ddc07bc28, alloc=65504) at tools/qbytearray.cpp:1452 #14 0x7f9e4c5eb679 in QByteArray::resize (this=0x7f9ddc07bc28, size=32768) at tools/qbytearray.cpp:1420 #15 0x7f9e4a0dd986 in reserve (bytes=2, this=0x7f9ddc015790) at ../../src/corelib/tools/qringbuffer_p.h:158 #16 QAbstractSocket::writeData (this=, data=0x7f9e2ce6c62c "\021", size=2) at socket/qabstractsocket.cpp:2315 #17 0x7f9e4c67982f in QIODevice::write (this=0x7f9ddc05bd80, data=0x7f9e2ce6c62c "\021", maxSize=) at io/qiodevice.cpp:1370 #18 0x7f9e3cca8bd5 in ?? () from /usr/lib64/libsopranoclient.so.1 #19 0x7f9e3ccafd6a in ?? () from /usr/lib64/libsopranoclient.so.1 #20 0x7f9e3ccb18b3 in ?? () from /usr/lib64/libsopranoclient.so.1 #21 0x7f9e43e9c64c in ?? () from /usr/lib64/libnepomuk.so.4 #22 0x7f9e43e88eb3 in ?? () from /usr/lib64/libnepomuk.so.4 #23 0x7f9e43e897bc in ?? () from /usr/lib64/libnepomuk.so.4 #24 0x7f9e43e9f7e3 in Nepomuk::Resource::property(QUrl const&) const () from /usr/lib64/libnepomuk.so.4 #25 0x7f9e472060ca in MessageCore::NepomukResourceRetrieverRunnable::run (this=0x69c84f0) at /usr/src/debug/kdepim-4.8.1/messagecore/asyncnepomukresourceretriever.cpp:47 #26 0x7f9e4c5dcd12 in QThreadPoolThread::run (this=0xe72d00) at concurrent/qthreadpool.cpp:107 #27 0x7f9e4c5e955b in QThreadPrivate::start (arg=0xe72d00) at thread/qthread_unix.cpp:298 #28 0x7f9e48ec0f05 in start_thread () from /lib64/libpthread.so.0 #29 0x7f9e4b
[Bug 297830] New: rearrange semicolon-separated addressee after pasting from clipboard
https://bugs.kde.org/show_bug.cgi?id=297830 Bug ID: 297830 Severity: wishlist Version: 4.8.0 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: rearrange semicolon-separated addressee after pasting from clipboard Classification: Unclassified OS: Linux Reporter: salout...@googlemail.com Hardware: Other Status: UNCONFIRMED Component: composer Product: kmail2 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 Build Identifier: When copy-pasting a list of adressee into the kmail2 composer, all mail adresses stays in one line. It would be a significant improvement to have the devided into several lines because: - this wouldn't need scrolling in the linedit (more clearly) - you can easiliy delete one single mail adress afterwards - does the adressee counter works for multiple adressee per line? Reproducible: Always -- 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
[Bug 297830] rearrange semicolon-separated addressee after pasting from clipboard
https://bugs.kde.org/show_bug.cgi?id=297830 Robert Riemann changed: What|Removed |Added Keywords||junior-jobs -- 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
[Bug 297831] New: uncollaps list of addressee in kmail2 composer
https://bugs.kde.org/show_bug.cgi?id=297831 Bug ID: 297831 Severity: wishlist Version: 4.8.0 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: uncollaps list of addressee in kmail2 composer Classification: Unclassified OS: Linux Reporter: salout...@googlemail.com Hardware: Other Status: UNCONFIRMED Component: composer Product: kmail2 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 Build Identifier: When adding a already saved collection of addressee (organized via the kmail adress book), only the name of the collection is presented in the adressee lineedits. I would suggest to make these collections uncollapsable in the composer and attach checkboxes to each line to be able to modifiy the list on a per-mail basis. Reproducible: Always -- 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
[Bug 296896] KMail crashes when clicking a mail
https://bugs.kde.org/show_bug.cgi?id=296896 Robert Riemann changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Robert Riemann --- Seems to be resolved in KDE 4.8.2. -- 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
[Bug 273949] Akonadi Resource always seen as readonly
https://bugs.kde.org/show_bug.cgi?id=273949 --- Comment #43 from Robert Riemann --- Has this been resolved in 4.8.2? I'm still having problems with my contacts resources. -- 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
[Bug 273949] Akonadi Resource always seen as readonly
https://bugs.kde.org/show_bug.cgi?id=273949 --- Comment #47 from Robert Riemann --- (In reply to comment #45) > yep, i reported this nearly a year ago and still nothing - whats the whole > point of bugreports then? > its a shame that kdepim gets no developer love, some akonadi and nepomuk > hype but failing in very basic use cases, unlike Dear developers, please be aware, that not everyone thinks this way. Dear Simon, please be aware, that this is a non-profit project. There is no other motivation than fun and and respect of others. It doesn't help anybody to show up with frustration. If you want to discuss more about this, please conact me via mail. I think there are similar cases in KDE where everything has been already said to such situations. Beside this, you are completely right. This is really an annoying bug. So let's do it this way: I'm going to donate 15€ (i.e. for a pizza) to the developer who fixes this bug. He might decide to redirect the donation to KDE e.V. It's not much, but I'm just a student. If nobody joins me and there is still no progress/interest, I might raise the donation. Best, Robert -- 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
[Bug 281856] New: Akregator crashes if I try to view a specific blogpost using the embeded browser
https://bugs.kde.org/show_bug.cgi?id=281856 Summary: Akregator crashes if I try to view a specific blogpost using the embeded browser Product: akregator Version: 4.7.0 Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: internal browser AssignedTo: kdepim-bugs@kde.org ReportedBy: salout...@googlemail.com Version: 4.7.0 (using KDE 4.7.0) OS:Linux The following blogpost (it's actually my own blog) was part of planetkde (and a ruby equivalent). When clicking on this feed item to get it shown in the embedded browser view, the whole app crashes immediately. http://salout.github.com/blog/2011/09/11/kubeplayer_kde_plasma_active.html The problem could be repoduced by other users (see comments of this blog post). Feed containing this blog post for testing purposes: http://salout.github.com/kde.xml Reproducible: Always Steps to Reproduce: - Add a feed containing this blog post - Click on the feed item "Kubeplayer running on KDE Plasma Active powered ExoPC tablet" Actual Results: Crashing Expected Results: not crashing ;) -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 281856] Akregator crashes if I try to view a specific blogpost using the embeded browser
https://bugs.kde.org/show_bug.cgi?id=281856 --- Comment #2 from Robert Riemann 2011-09-12 09:17:06 --- I thought about that, of course, but I didn't compile akregator and don't know how to install debugsymbols for opensuse 11.4 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 281856] Akregator crashes if I try to view a specific blogpost using the embeded browser
https://bugs.kde.org/show_bug.cgi?id=281856 --- Comment #5 from Robert Riemann 2011-09-12 11:00:08 --- I could NOT reproduce the problem on my Laptop with Akregator 1.6.6 KDE 4.6.0 using GStreamer Backend. I will try it from my desktop PC again this evening. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 281856] Akregator crashes if I try to view a specific blogpost using the embeded browser
https://bugs.kde.org/show_bug.cgi?id=281856 --- Comment #6 from Robert Riemann 2011-09-12 16:28:31 --- Created an attachment (id=63590) --> (http://bugs.kde.org/attachment.cgi?id=63590) backtrace -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 281856] Akregator crashes if I try to view a specific blogpost using the embeded browser
https://bugs.kde.org/show_bug.cgi?id=281856 --- Comment #7 from Robert Riemann 2011-09-12 16:31:10 --- Seems to be related to phonon backend. After switching from xine to gstreamer Akregator doesn't crash anymore. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 285307] New: KAdressbook crashes when saving new contact
https://bugs.kde.org/show_bug.cgi?id=285307 Summary: KAdressbook crashes when saving new contact Product: kaddressbook Version: unspecified Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: salout...@googlemail.com CC: to...@kde.org Application: kaddressbook (4.7.2) KDE Platform Version: 4.7.2 (4.7.2) Qt Version: 4.7.4 Operating System: Linux 3.1.0-rc9-1-desktop x86_64 Distribution: "openSUSE 12.1 RC 1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: ι opened a new contact card, filled in just a name and saved it. Immedialty afterwards, KAdressBook crashed. - Custom settings of the application: I activated one adressbook std.vcf in .kde4/share/apps/kabc/std.vcf. Also remarkable: My Adressbook seems to be empty, but there are contacts defined in std.vcf. The crash can be reproduced every time. -- Backtrace: Application: Adressbuch (kaddressbook), signal: Aborted [KCrash Handler] #6 0x7f251221dd95 in raise () from /lib64/libc.so.6 #7 0x7f251221f2ab in abort () from /lib64/libc.so.6 #8 0x7f251284cf2d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/libstdc++.so.6 #9 0x7f251284b0d6 in ?? () from /usr/lib64/libstdc++.so.6 #10 0x7f251284b103 in std::terminate() () from /usr/lib64/libstdc++.so.6 #11 0x7f251284b246 in __cxa_rethrow () from /usr/lib64/libstdc++.so.6 #12 0x7f2512bf8bb6 in QEventLoop::exec (this=, flags=) at kernel/qeventloop.cpp:214 #13 0x7f2512bfcc47 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064 #14 0x004050dd in main (argc=, argv=) at /usr/src/debug/kdepim-4.7.2/kaddressbook/main.cpp:52 Possible duplicates by query: bug 285299, bug 285292, bug 285236, bug 285204, bug 285197. Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 277705] KMail crashes if nepomuk is enabled
https://bugs.kde.org/show_bug.cgi?id=277705 Robert Riemann changed: What|Removed |Added CC||salout...@googlemail.com --- Comment #33 from Robert Riemann --- Deactivating Nepomuk also "solved" my KMail-Crashing problems. -- 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
[Bug 295218] KMail freezes when GPG doesn't respond
https://bugs.kde.org/show_bug.cgi?id=295218 Robert Riemann changed: What|Removed |Added CC||salout...@googlemail.com --- Comment #3 from Robert Riemann --- I experienced the same problem. In my university network, the port for PGP keyserver search seems to be blocked. The result is a freezing kmail, which only gets usable again after a timeout (from kpgp?) has expired. -- 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
[Bug 298911] Reply to decrypted mail quotes encrypted text
https://bugs.kde.org/show_bug.cgi?id=298911 Robert Riemann changed: What|Removed |Added CC||salout...@googlemail.com --- Comment #4 from Robert Riemann --- I think it's weird to have the PGP Signature in the respond text as well. So this affects not only encrypted mails, but also signed mails. Any progress on this bug so far? -- 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
