[kmail2] [Bug 483987] New: "Reply all" protection: ask for confirmation before replying to a potentially large number of recipients
https://bugs.kde.org/show_bug.cgi?id=483987 Bug ID: 483987 Summary: "Reply all" protection: ask for confirmation before replying to a potentially large number of recipients Classification: Applications Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: fisc...@unix-ag.uni-kl.de Target Milestone: --- Similar to the existing "Check Before Send Mail" plugin, Kmail should warn and ask for an extra confirmation if an email is about to be sent to a potentially large number of recipients. Criteria to test for: - Number of recipients in To, CC, and BCC fields is about a certain threshold - A mail address previously configured by the user as a "distribution address" is used. A "distribution address" would be a mail address like "every...@example.com", where the mail server then takes are to distribute the mail to a large number of recipients. Those check should not be limited to cases when the user chooses "reply all". Even a 'normal' reply to a distribution address should trigger a warning. Implementation detail/suggestion: Before sending, KMail or Akonadi counts the number of mail addresses (To, CC, BBC). Every mail address which is in the list of known distribution addresses counts 1000 (or any sufficiently large number). The threshold for a warning is 10. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 473593] New: Ability to mark calendars as read-only independent of backend
https://bugs.kde.org/show_bug.cgi?id=473593 Bug ID: 473593 Summary: Ability to mark calendars as read-only independent of backend Classification: Frameworks and Libraries Product: Akonadi Version: 5.23.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: fisc...@unix-ag.uni-kl.de CC: c...@carlschwan.eu Target Milestone: --- Currently, the UI (e.g. Akonadi Console, "Folder Properties" on a calendar) offers no option to mark a calendar as read-only, i.e. to disallow changes or removal of events or adding new events. This should be implemented independent of the backend, irrespective of whether it is a local calendar or a DAV resource. Background: in my groupware server account, I have several calendars: one for events I maintain (add/edit events) and several that are subscriptions to external calendar feeds which are read-only. Either the groupware server does not relay the information which calendars are read-only, or Akonadi does not interpret this information correctly. At least in KOrganizer, changes can be made to calendars that are technically read-only. To block those changes, the user should have the choice to mark a calendar read-only even if changes are technically possible, e.g. to avoid accidental changes to calendars. The Folder Properties dialog has a "ACL" tab, but it warns to make changes here. Even if my request can be "solved" by making changes here, it sounds like a dangerous path and it deters users from making the changes. Instead, there should be a simple checkbox in the "General" tab next to the "custom icon" setting that allows the user to make the calendar read-only (or not). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 467439] New: Crash when selecting multiple mails while pressing Ctrl
https://bugs.kde.org/show_bug.cgi?id=467439 Bug ID: 467439 Summary: Crash when selecting multiple mails while pressing Ctrl Classification: Applications Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: fisc...@unix-ag.uni-kl.de Target Milestone: --- After first filtering mails in the list of mails for a keyword and while selecting (mouse cursor) several of the found mails while pressing Ctrl, KMail crashed: Using Fedora 37, the following program/library versions were used: KMail 22.12.3 KF5 KMime 22.12.3 Q5 5.15.8 Frameworks 5.103.0 Output on command line up to crash: kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP [New Thread 0x7fff36ffd6c0 (LWP 12933)] [New Thread 0x7fff367fc6c0 (LWP 12934)] [New Thread 0x7fff35ffb6c0 (LWP 12935)] [New Thread 0x7fff357fa6c0 (LWP 12936)] qt.qpa.wayland: Wayland does not support QWindow::requestActivate() [New Thread 0x7fff1e1bd6c0 (LWP 12942)] [New Thread 0x7fff1d9bc6c0 (LWP 12943)] [Detaching after fork from child process 12947] [Detaching after fork from child process 12949] [Detaching after fork from child process 12951] [New Thread 0x7fff0bbff6c0 (LWP 12953)] [New Thread 0x7fff0abbe6c0 (LWP 12956)] [New Thread 0x7fff09f2d6c0 (LWP 12957)] [New Thread 0x7fff0970c6c0 (LWP 12958)] [New Thread 0x7fff08f0b6c0 (LWP 12959)] [New Thread 0x7ffef3fff6c0 (LWP 12960)] [Thread 0x7fff57fff6c0 (LWP 12908) exited] [Thread 0x7fff767fc6c0 (LWP 12904) exited] [Thread 0x7fff777fe6c0 (LWP 12902) exited] [New Thread 0x7fff767fc6c0 (LWP 13009)] [New Thread 0x7fff777fe6c0 (LWP 13010)] qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x56efca90) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x56efca90) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x5702e190) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x56e4b8b0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents [New Thread 0x7fff57fff6c0 (LWP 13019)] [Detaching after fork from child process 13095] Recognized the following URL or filename: "https://fortimail.his.se/releasecontrol?release=1%3Athomas.fischer%40his.se%3AMTY3ODk1OTc0Mi4zNTIwXzU4NTkxMF8xMDkxNDAuMTcwNTczI1EjMzJHOUIyVDQwMjk0MTQwMDAwLCNGI1MjNTY2Njc2I0U%3D%3Aver%3A2%3A01%3A01%3A59cbce3b04f7780ddb461e6fdf6f90f3f0f58606; Using Firefox executable "/usr/bin/firefox" [Thread 0x7fff57fff6c0 (LWP 13019) exited] [New Thread 0x7fff57fff6c0 (LWP 13197)] [Detaching after fork from child process 13210] Recognized the following URL or filename: "https://fortimail.his.se/releasecontrol?release=1%3Athomas.fischer%40his.se%3AMTY3ODk1OTc0Mi4zNTIwXzU4NTkxMF8xMDkxNDAuMTcwNTczI1EjMzJHOUIyVDQwMjk0MTQwMDAwLCNGI1MjNTY2Njc2I0U%3D%3Aver%3A2%3A01%3A01%3A59cbce3b04f7780ddb461e6fdf6f90f3f0f58606; Using Firefox executable "/usr/bin/firefox" qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the current topmost grabbing popup,
[kmail2] [Bug 467436] New: Crash when moving mails between folders
https://bugs.kde.org/show_bug.cgi?id=467436 Bug ID: 467436 Summary: Crash when moving mails between folders Classification: Applications Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: fisc...@unix-ag.uni-kl.de Target Milestone: --- After observing regular crashes in KMail when moving mails between folders (via context menu, then "Move to", on mail in list of mails), I ran kmail via gdb with debuginfod enabled. Akonadi is no affected by crash, I still get popups on incoming mails even after KMail had crashed. Version numbers of concerned programs/libraries: KMail 22.12.3, Fedora release 1.fc37 QWayand 5.15.8, Fedora release 1.fc37 KF5 KXmlGui 5.103.0, Fedora release 1.fc37 Most recent output in terminal before crash: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/6”" "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/5”" [Thread 0x7fff75bfb6c0 (LWP 9496) exited] kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP [Thread 0x7fff773fe6c0 (LWP 9633) exited] [Thread 0x7fff753fa6c0 (LWP 8215) exited] qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x571e1880) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x571e1880) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x571e1880) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x7fff6c0678b0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x7fff6c0678b0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x571e7000) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents [New Thread 0x7fff753fa6c0 (LWP 11224)] [New Thread 0x7fff773fe6c0 (LWP 11225)] [New Thread 0x7fff75bfb6c0 (LWP 11226)] [New Thread 0x7ffeecbfc6c0 (LWP 11326)] [New Thread 0x7ffeebbfa6c0 (LWP 11328)] [New Thread 0x7ffeec3fb6c0 (LWP 11327)] [New Thread 0x7ffeeb3f96c0 (LWP 11329)] [New
[kontact] [Bug 463450] Application: Kontact (kontact), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=463450 Thomas Fischer changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #1 from Thomas Fischer --- I may have encountered the same or a very similar problem. I have kmail crashing several times a day when moving mails between folders (via context menu in mail list) on a Fedora Linux KDE spin system that is not even one week old. I ran the kmail binary via gdb with debuginfod enabled to get the following output. The first few lines may be older and not directly related to the crash: qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x570d4e70) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x5737bdf0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x570d4e70) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x56bbb930) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents [Thread 0x7ffee9bff6c0 (LWP 32407) exited] [Thread 0x7fff66c0 (LWP 32406) exited] [Thread 0x7fff75ffb6c0 (LWP 29371) exited] Downloading separate debug info for /usr/lib64/qt5/plugins/kf5/FrameworkIntegrationPlugin.so Downloading separate debug info for /usr/lib64/libcanberra-0.30/libcanberra-pulse.so [New Thread 0x7fff75ffb6c0 (LWP 32420)] [Detaching after fork from child process 32421] [Detaching after fork from child process 32423] [New Thread 0x7fff66c0 (LWP 32426)] [Detaching after fork from child process 32427] [Thread 0x7fff66c0 (LWP 32426) exited] org.kde.pim.messagelist: Requested invariant for storage row index 3809 not found in history org.kde.pim.messagelist: Requested invariant for storage row index 3809 not found in history org.kde.pim.messagelist: Requested invariant for storage row index 3809 not found in history org.kde.pim.messagelist: Requested invariant for storage row index 3809 not found in history org.kde.pim.messagelist: Requested invariant for storage row index 3809 not found in history [New Thread 0x7fff66c0 (LWP 32471)] [New Thread 0x7ffee9bff6c0 (LWP 32472)] [New Thread 0x7ffeea7ff6c0 (LWP 32473)] qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x570d4e70) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x7fff6003f460) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x570d4e70) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x5729bca0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents malloc(): unaligned fastbin chunk detected Thread 1 "kmail" received signal SIGABRT, Aborted. __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 Downloading source file /usr/src/debug/glibc-2.36-9.fc37.x86_64/nptl/pthread_kill.c 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7fffee2afec3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x7fffee25fa76 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x7fffee2497fc in __GI_abort () at abort.c:79 #4 0x7fffee2a408e in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fffee3bd465 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 #5 0x7fffee2b9b9c in malloc_printerr (str=str@entry=0x7fffee3c0400 "malloc(): unaligned fastbin chunk detected") at malloc
[kmail2] [Bug 461810] New: Crash with malloc(): mismatching next->prev_size (unsorted)
https://bugs.kde.org/show_bug.cgi?id=461810
Bug ID: 461810
Summary: Crash with malloc(): mismatching next->prev_size
(unsorted)
Classification: Applications
Product: kmail2
Version: unspecified
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: kdepim-bugs@kde.org
Reporter: fisc...@unix-ag.uni-kl.de
Target Milestone: ---
Since an update on ArchLinux in late October, KMail crashes quite often when
moving mails between folders, e.g. when sorting mails form Inbox to some other
folder. According to the package manager, both kmail and Akonadi have the
version number 22.08.3-1.
To collect information, I stopped Akonadi (akonadictl stop) and restarted it in
a console to see any relevant debug output during a crash. Same with kmail. No
special settings for extra debug output e.g. via kdebugsettings were made.
Akonadi made only some initial output but nothing later or during a crash.
kmail, however, gave the following output. I think but are not sure that the
output up to the last "DispatchModeAttribute" was before the crash.
Error loading text-to-speech plug-in "speechd"
org.kde.pim.mailtransportakonadi: Item doesn't have DispatchModeAttribute.
d->folderTreeWidget->selectedCollection() Collection ID: 199remote ID:
"AAMkADdjYzdhYjJkLTBjNGItNDRhZS05NjZjLWIxNzY5OTI2MTllNwAuAAA5OWMvCOhAR7niCe/yxRIKAQCzEcl00IXvRLelEuHv21iGxUoQAAA="
name: "Personal"
url: QUrl("akonadi:?collection=199")
parent: 38
"AAMkADdjYzdhYjJkLTBjNGItNDRhZS05NjZjLWIxNzY5OTI2MTllNwAuAAA5OWMvCOhAR7niCe/yxRIKAQCzEcl00IXvRLelEuHv21iGxTaMAAA="
resource: "akonadi_ews_resource_0"
rights: QFlags(AllRights)
contents mime type: ("message/rfc822", "inode/directory")
isVirtual: false
CachePolicy:
inherit: true
interval: -1
timeout: -1
sync on demand: false
local parts: ()
CollectionStatistics:
count: 3620
unread count: 1
size: 561984064
org.kde.pim.mailtransportakonadi: Item doesn't have DispatchModeAttribute.
malloc(): mismatching next->prev_size (unsorted)
*** KMail got signal 6 (Exiting)
*** Dead letters dumped.
malloc(): unaligned fastbin chunk detected
Let me know if I should try to re-create the crash with some additional debug
settings enabled.
--
You are receiving this mail because:
You are the assignee for the bug.
[kmail2] [Bug 461810] Crash with malloc(): mismatching next->prev_size (unsorted)
https://bugs.kde.org/show_bug.cgi?id=461810 --- Comment #1 from Thomas Fischer --- Just restarted kmail. It crashed again when moving a mail (context menu to move mail to another folder). This time, the output was different: malloc(): unaligned tcache chunk detected *** KMail got signal 6 (Exiting) *** Dead letters dumped. malloc(): unaligned tcache chunk detected malloc(): unaligned tcache chunk detected Unable to start Dr. Konqi Re-raising signal for core dump handling. -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 453805] Text of event reminders does not use local timezone
https://bugs.kde.org/show_bug.cgi?id=453805 Thomas Fischer changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #2 from Thomas Fischer --- (In reply to David E. Narvaez from comment #1) > Forget about the timezone: it does not even say what day the event is. I have not tested it myself yet, but it looks like commit 2b832b9d08e4eaca0825 added the date if the event is on another day. https://invent.kde.org/pim/akonadi-calendar/-/commit/2b832b9d08e4eaca08258e4f372e92a18fed035e The missing time zone information is not fixed, as the time is formatted as "QLocale::NarrowFormat" which is supposed to format a time in the shortest possible way, basically guaranteeing that no time zone will be shown. https://doc.qt.io/qt-5/qlocale.html#FormatType-enum Maybe the code can be refactored to format time differently (longer) if the event's time zone differs from the current time zone? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409224] kmail with >=mariadb-10.4.6: not able to refresh email list: Unable to append status flags
https://bugs.kde.org/show_bug.cgi?id=409224 Thomas Fischer changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #10 from Thomas Fischer --- On Arch Linux and maybe other Linux distributions, the socket FSO 'mysql.socket' is not located in /tmp/akonadi-*/ but in /run/user/*/akonadi/default/ instead. Thus, the two commands to run become: mysql -S /run/user/$(id -u)/akonadi/default/mysql.socket -e 'create database mysql' && mysql_upgrade -S /run/user/$(id -u)/akonadi/default/mysql.socket At least for me, after running both commands KMail/Akonadi starts fetching and listing mails again. (In reply to Piotr from comment #7) > Workaround wasn't working for me: > > piorek@dreadnought ~ $ mysql_upgrade > --socket=/tmp/akonadi-piorek.XX/mysql.socket > Version check failed. Got the following error when calling the 'mysql' > command line client > ERROR 1049 (42000): Unknown database 'mysql' > FATAL ERROR: Upgrade failed > > Had to create DB mysql first (CREATE DATABASE mysql;). This fixed the > problem and upgrade succeeded. Looks like KMail is working fine so far. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 310437] Wish for a ActiveSync resource in akonadi for full Exchange compatibility
https://bugs.kde.org/show_bug.cgi?id=310437 Thomas Fischer <fisc...@unix-ag.uni-kl.de> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #8 from Thomas Fischer <fisc...@unix-ag.uni-kl.de> --- *** This bug has been confirmed by popular vote. *** -- 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 359063] Plain text version of html-only message is not respecting encoding specified in html message
https://bugs.kde.org/show_bug.cgi?id=359063 --- Comment #4 from Thomas Fischer <fisc...@unix-ag.uni-kl.de> --- Created attachment 97245 --> https://bugs.kde.org/attachment.cgi?id=97245=edit Simple Perl script that sends a mail with HTML and quoted-printable iso-8859-1 content -- 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 359063] Plain text version of html-only message is not respecting encoding specified in html message
https://bugs.kde.org/show_bug.cgi?id=359063 --- Comment #2 from Thomas Fischer <fisc...@unix-ag.uni-kl.de> --- Created attachment 97157 --> https://bugs.kde.org/attachment.cgi?id=97157=edit Before rendering HTML code, showing rendering issues with iso-8859-1/quoted-printable-encoded HTML text -- 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 359063] Plain text version of html-only message is not respecting encoding specified in html message
https://bugs.kde.org/show_bug.cgi?id=359063 Thomas Fischer <fisc...@unix-ag.uni-kl.de> changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #1 from Thomas Fischer <fisc...@unix-ag.uni-kl.de> --- I may have the same problem. My observation is as follows: The user receives a HTML-only mail in an European language (which makes use of non-ASCII characters code 128-255 such as åäö), the mail is quoted-printable encoded. My test case mail's source code looks like this: abc123=E5=E4=F6ABC123=C5=C4=D6 The relevant mail headers look like this: Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="iso-8859-1" This mail should look like this when correctly displayed: abc123åäö ABC123ÅÄÖ I'll attach two screen shots. One will reproduce how the mail is displayed in "non-HTML" mode, where a box is show for the use to "click here" to render the HTML code. The second screen shot reproduces the output of just this render. Please observe the incorrect rendering in the first screenshot. -- 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 359063] Plain text version of html-only message is not respecting encoding specified in html message
https://bugs.kde.org/show_bug.cgi?id=359063 --- Comment #3 from Thomas Fischer <fisc...@unix-ag.uni-kl.de> --- Created attachment 97158 --> https://bugs.kde.org/attachment.cgi?id=97158=edit After confirming that HTML code should be rendered -- 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 339724] New: Stay in directory for several file attachment operations
https://bugs.kde.org/show_bug.cgi?id=339724 Bug ID: 339724 Summary: Stay in directory for several file attachment operations Product: kmail2 Version: 4.14.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: fisc...@unix-ag.uni-kl.de When attaching a file, the file open dialog starts in the current user's home (at least in my case). The user changes to the directory where the file to be attached resides, selects the file, and confirms/closes the dialog. When attaching the second file, the file open dialog starts again in the user's home directory. It would improve usability, if the file open dialog for attachments directly continues in the directory of the last attachment. It would suffice if the last directory is only memorized for the currently composed mail. For future mail compositions, the file open dialog may start again in the user's home directory. 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
[Akonadi] [Bug 327216] New: First moving mails to folder and then opening folder shows only moved mails, not older/other mails
https://bugs.kde.org/show_bug.cgi?id=327216 Bug ID: 327216 Summary: First moving mails to folder and then opening folder shows only moved mails, not older/other mails Classification: Unclassified Product: Akonadi Version: 1.10.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: IMAP resource Assignee: er...@kde.org Reporter: fisc...@unix-ag.uni-kl.de CC: kdepim-bugs@kde.org, vkra...@kde.org Using an Micosoft Exchange mail server through IMAP, I am sorting my mails into subfolders through KMail. After having moved some mails to this subfolder and then visiting the folder, KMail shows only the just moved mails, but not any other mail in this folder. For reproduction, it is important to not open the folder before that in KMail. Folders where no mails have been moved to show all mails as expected. The list of mails does not change even then refreshing the list through F5 (fresh this folder). Stopping and starting Akonadi through akonadictl makes all mails appear as expected. This bug did not exist in KDE 4.10.x, but I cannot recall when I first observed it in the 4.11.x releases. Reproducible: Always -- 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 234264] crashed after adding account
https://bugs.kde.org/show_bug.cgi?id=234264 Thomas Fischer fisc...@unix-ag.uni-kl.de changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #22 from Thomas Fischer fisc...@unix-ag.uni-kl.de --- Hello Laurent, got a backtrace in 4.9.3 in Gentoo Linux: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library /lib/libthread_db.so.1. [Current thread is 1 (Thread 0xb0a97980 (LWP 2918))] Thread 3 (Thread 0xaf3b2b40 (LWP 2922)): #0 0xb7736424 in __kernel_vsyscall () #1 0xb5860f2c in pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:169 #2 0xb5e21fab in __pthread_cond_wait (cond=0xb3d8c0d0, mutex=0xb3d8c0b8) at forward.c:139 #3 0xb364c4be in ?? () from /usr/lib/qt4/libQtWebKit.so.4 #4 0xb364c4fb in ?? () from /usr/lib/qt4/libQtWebKit.so.4 #5 0xb585cd66 in start_thread (arg=0xaf3b2b40) at pthread_create.c:305 #6 0xb5e1581e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133 Thread 2 (Thread 0xaea89b40 (LWP 2923)): #0 0xb585f1cb in __pthread_mutex_lock (mutex=0xae100550) at pthread_mutex_lock.c:113 #1 0xb5e221b5 in pthread_mutex_lock (mutex=0xae100550) at forward.c:182 #2 0xb443267b in g_mutex_lock () from /usr/lib/libglib-2.0.so.0 #3 0xb43f5acf in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #4 0xb43f5f80 in ?? () from /usr/lib/libglib-2.0.so.0 #5 0xb43f60d2 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #6 0xb6156d16 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/qt4/libQtCore.so.4 #7 0xb61238ab in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/qt4/libQtCore.so.4 #8 0xb6123b5f in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/qt4/libQtCore.so.4 #9 0xb600ef20 in QThread::exec() () from /usr/lib/qt4/libQtCore.so.4 #10 0xb600efe4 in QThread::run() () from /usr/lib/qt4/libQtCore.so.4 #11 0xb6011506 in ?? () from /usr/lib/qt4/libQtCore.so.4 #12 0xb585cd66 in start_thread (arg=0xaea89b40) at pthread_create.c:305 #13 0xb5e1581e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133 Thread 1 (Thread 0xb0a97980 (LWP 2918)): [KCrash Handler] #7 0xb4d6ff84 in MailTransport::AddTransportDialog::accept (this=0x9049a40) at /usr/src/debug/kde-base/kdepimlibs-4.9.3/kdepimlibs-4.9.3/mailtransport/addtransportdialog.cpp:145 #8 0xb7412227 in KDialog::slotButtonClicked (this=0x9049a40, button=4) at /usr/src/debug/kde-base/kdelibs-4.9.3/kdelibs-4.9.3/kdeui/dialogs/kdialog.cpp:885 #9 0xb74123f9 in KDialog::qt_static_metacall (_o=0x9049a40, _c=QMetaObject::InvokeMetaMethod, _id=33, _a=0xbfa5f088) at /usr/src/debug/kde-base/kdelibs-4.9.3/kdelibs-4.9.3_build/kdeui/kdialog.moc:167 #10 0xb613d7ea in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/qt4/libQtCore.so.4 #11 0xb6142700 in QSignalMapper::mapped(int) () from /usr/lib/qt4/libQtCore.so.4 #12 0xb614293f in QSignalMapper::map(QObject*) () from /usr/lib/qt4/libQtCore.so.4 #13 0xb6142a73 in QSignalMapper::map() () from /usr/lib/qt4/libQtCore.so.4 #14 0xb6142f64 in ?? () from /usr/lib/qt4/libQtCore.so.4 #15 0xb613d7ea in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/qt4/libQtCore.so.4 #16 0xb6b21d6e in QAbstractButton::clicked(bool) () from /usr/lib/qt4/libQtGui.so.4 #17 0xb680635a in ?? () from /usr/lib/qt4/libQtGui.so.4 #18 0xb68079bb in ?? () from /usr/lib/qt4/libQtGui.so.4 #19 0xb6807c0c in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/qt4/libQtGui.so.4 #20 0xb643625d in QWidget::event(QEvent*) () from /usr/lib/qt4/libQtGui.so.4 #21 0xb6806e40 in QAbstractButton::event(QEvent*) () from /usr/lib/qt4/libQtGui.so.4 #22 0xb68ab8e5 in QPushButton::event(QEvent*) () from /usr/lib/qt4/libQtGui.so.4 #23 0xb63d9a55 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/qt4/libQtGui.so.4 #24 0xb63df9d8 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/qt4/libQtGui.so.4 #25 0xb74d93bd in KApplication::notify (this=0xbfa61384, receiver=0x9049790, event=0xbfa5fa48) at /usr/src/debug/kde-base/kdelibs-4.9.3/kdelibs-4.9.3/kdeui/kernel/kapplication.cpp:311 #26 0xb61253d5 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/qt4/libQtCore.so.4 #27 0xb63dae67 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointerQWidget, bool) () from /usr/lib/qt4/libQtGui.so.4 #28 0xb6466dd3 in ?? () from /usr/lib/qt4/libQtGui.so.4 #29 0xb6465646 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/qt4/libQtGui.so.4 #30 0xb648fb96 in ?? () from /usr/lib/qt4/libQtGui.so.4 #31 0xb43f5cbf in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #32 0xb43f5fdb in ?? () from /usr/lib/libglib-2.0.so.0 #33 0xb43f60d2
[Bug 303861] Can't write CalDav items from korganizer
https://bugs.kde.org/show_bug.cgi?id=303861 Thomas Fischer fisc...@unix-ag.uni-kl.de changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #34 from Thomas Fischer fisc...@unix-ag.uni-kl.de --- I can confirm that bug is fixed indeed: Using Kontact 4.9.3 + Davmail, I can add calendar events to a MS Exchange server calendar. -- 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 309946] KMail forgets reply or forward status in mails
https://bugs.kde.org/show_bug.cgi?id=309946 --- Comment #2 from Thomas Fischer fisc...@unix-ag.uni-kl.de --- Created attachment 75193 -- https://bugs.kde.org/attachment.cgi?id=75193action=edit Before-after screenshot of the overlay icon -- 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 309946] KMail forgets reply or forward status in mails
https://bugs.kde.org/show_bug.cgi?id=309946 --- Comment #4 from Thomas Fischer fisc...@unix-ag.uni-kl.de --- Yes, I forgot to mention this. MS Exchange via IMAP: * OK The Microsoft Exchange IMAP4 service is ready. -- 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 309946] KMail forgets reply or forward status in mails
https://bugs.kde.org/show_bug.cgi?id=309946 --- Comment #6 from Thomas Fischer fisc...@unix-ag.uni-kl.de --- It's a problem from imap. Ok, so it is on KMail's side and not Exchange? Known bug Was this bug been filed previously? How can I help to fix it? -- 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 309946] New: KMail forgets reply or forward status in mails
https://bugs.kde.org/show_bug.cgi?id=309946 Bug ID: 309946 Severity: normal Version: 4.9.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: KMail forgets reply or forward status in mails Classification: Unclassified OS: Linux Reporter: fisc...@unix-ag.uni-kl.de Hardware: Other Status: UNCONFIRMED Component: general Product: kmail2 When replying to or forwarding emails, KMail does not properly set the status for this mail. A small reply or forward icon is set as an overlay on the mail's icon directly after sending the forward/reply, but this icon gets cleared as soon as one changes the mail folder. In the mail's source view, there is neither a status, nor a x-status set. Below, this is the header of a sent mail which was a reply to another mail: From: AA To: BB Subject: Re: Restfull webservice Date: Mon, C Message-ID: Organization: E X-KMail-Identity: 1608138006 User-Agent: KMail/4.9.3 (Linux/3.6.6-1-ARCH; KDE/4.9.3; x86_64; ; ) In-Reply-To: References: GG MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 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 309946] KMail forgets reply or forward status in mails
https://bugs.kde.org/show_bug.cgi?id=309946 --- Comment #1 from Thomas Fischer fisc...@unix-ag.uni-kl.de --- Created attachment 75192 -- https://bugs.kde.org/attachment.cgi?id=75192action=edit Example of an email and its reply, missing the small reply overlay icon -- 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 305662] Messages are kept unread even after marking them as read.
https://bugs.kde.org/show_bug.cgi?id=305662 Thomas Fischer fisc...@unix-ag.uni-kl.de changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #2 from Thomas Fischer fisc...@unix-ag.uni-kl.de --- I have observed similar problems with one of my IMAP accounts. In my case, it was a UW imap server. What is yours? Would be interesting to know if the problem is specific to a certain server (or revision). -- 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 259574] conflict resolution box appears a lot
https://bugs.kde.org/show_bug.cgi?id=259574 Thomas Fischer fisc...@unix-ag.uni-kl.de changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #53 from Thomas Fischer fisc...@unix-ag.uni-kl.de --- I can confirm this problem on ArchLinux, using KMail/Kontact that comes along KDE 4.9.1 (most recent stable as of writing). The ArchLinux installation is brand new (inside a virtual machine) and has therefore no legacy configuration files. No fancy mail setup (e.g. using SpamAssassin) has been set up. The IMAP server is UW-IMAP 2007b~dfsg-4+lenny3, the mailbox contains just about 10 mails. The conflict resolution box appears when marking several mails as read (KMail is configured to *not* mark mails as read automatically when clicking on them in the list, but only when the user performs the Mark mail as read action) and immediately thereafter selecting/clicking on one of those mails in the list. My guess is that the status change from Unread to Read is not yet transferred to the mail server, but the clicking on the mail triggers fetching the mail from the server. Thus, both versions differ when one is read (the local one) and the other is unread (the newly fetched one). As a step towards fixing this bug, I would like to see the difference between both mails visualized better. A previous comment remarked the different widths of both emails in the conflict box, which makes it hard to spot the actual difference. Is using the widget from Kompare or KDiff3 an option? For developers (and for bug reports), the difference should be provided in a diff-like format. -- 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 288202] New: Components under Kontact forget custom keyboard shortcuts when switching between components
https://bugs.kde.org/show_bug.cgi?id=288202 Summary: Components under Kontact forget custom keyboard shortcuts when switching between components Product: kontact Version: 4.7.2 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: fisc...@unix-ag.uni-kl.de Version: 4.7.2 (using KDE 4.7.3) OS:Linux Most components (KMail, Contacts, ...) allow to configure keyboard shortcuts via Settings - Configure Shortcuts. Settings made there, however, seem only last as long as one does not switch to another component, e.g. from KMail to Contacts. For example, take an action that has no shortcut yet, such as Mark Mail as Read, and assign Ctrl+R to it. Close dialog with OK and onfirm that the keyboard shortcut is working on a real email. Switch to Feeds (aKregator) or Contacts and switch immediately back to Mail. Go to the keyboard settings dialog: the configured shortcut is gone. The same problem exist for keyboard shortcuts configured in other components as well, such as Contacts. It looks like a problem more general to Kontact and how components are handled than a KMail-specific problem. Reproducible: Always Steps to Reproduce: Steps to Reproduce: see above description Actual Results: Actual Results: see above description Expected Results: Actual Results: see above description Kontact 4.7.3, which wasn't in the list of available versions to choose from. -- 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 278737] mails marked as read show unread upon next folder refresh
https://bugs.kde.org/show_bug.cgi?id=278737 Thomas Fischer fisc...@unix-ag.uni-kl.de changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #4 from Thomas Fischer fischer unix-ag uni-kl de 2011-12-04 14:51:10 --- I got a similar problem: In my process of sorting mails, I manually mark messages as read (I disabled automatic marking as read) and move them to another folder on the same IMAP server. Pressing Check Mail for manual refresh makes the mail re-appear in the INBOX -- unread. At the same time, the same mail resides in the folder where I moved it to -- unread as well. Seems to a bug where local operations (mark emails as read, move between folders) on a (remote) mail folder is not propagated to the server if a manual check is done. My guess is that uploading local changes is delayed/deferred for performance reasons. However, once the user triggers a manual check, those change should be flushed to the server before fetching the remote mail folder's current state. -- 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 278020] KMail cannot send e-mail via SMTP
https://bugs.kde.org/show_bug.cgi?id=278020 Thomas Fischer fisc...@unix-ag.uni-kl.de changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #30 from Thomas Fischer fischer unix-ag uni-kl de 2011-10-28 07:40:48 --- I can confirm this problem with a Sabayon Linux installation (KMail 4.7.2) and that the fix from comments #20 (Online=true) and #21 (akonadictl restart) works. -- 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 284772] Akonadi-Crash while trying out IMAP server settings
https://bugs.kde.org/show_bug.cgi?id=284772 --- Comment #2 from Thomas Fischer fischer unix-ag uni-kl de 2011-10-27 18:46:07 --- Created an attachment (id=64948) -- (http://bugs.kde.org/attachment.cgi?id=64948) Compress stdout+stderr output of akonadiconsole -- 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 284772] Akonadi-Crash while trying out IMAP server settings
https://bugs.kde.org/show_bug.cgi?id=284772 --- Comment #3 from Thomas Fischer fischer unix-ag uni-kl de 2011-10-27 18:51:07 --- More tests on this subject. This is how I got today's crash: 1. Stopped Akonadi via akonadictl stop (checked with ... status that it is actually stopped) 2. Started AkonadiConsole. Chose native configuration for IMAP account and actually got a combination, where Akonadi claimed to be connected to IMAP server 3. Switch to AkonadiConsole's second tab (browser) 4. Picked an arbitrary folder on the IMAP server; though not sure if it was there from a previous attempt or freshly fetched. Selected Synchronize Folder (F5). 5. Crash. Attachment 64948 is the compressed output of akonadiconsole (stdout+stderr) from this session. The crash dialog's backtrace is as follows: Application: Akonadi Console (akonadiconsole), signal: Aborted [Current thread is 1 (Thread 0xb1d18710 (LWP 3214))] Thread 3 (Thread 0xb0c6db70 (LWP 3216)): #0 0xb7745424 in __kernel_vsyscall () #1 0xb5547fa1 in select () at ../sysdeps/unix/syscall-template.S:82 #2 0xb69c1dd4 in QProcessManager::run (this=0xb6b238b0) at io/qprocess_unix.cpp:245 #3 0xb68e4427 in QThreadPrivate::start (arg=0xb6b238b0) at thread/qthread_unix.cpp:320 #4 0xb4e67b4c in start_thread (arg=0xb0c6db70) at pthread_create.c:301 #5 0xb554e94e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133 Thread 2 (Thread 0xb0464b70 (LWP 3221)): #0 0xb7745424 in __kernel_vsyscall () #1 0xb4e6bebc in pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169 #2 0xb555af27 in __pthread_cond_wait (cond=0xb4e34770, mutex=0xb4e34758) at forward.c:139 #3 0xb494521c in WTF::TCMalloc_PageHeap::scavengerThread (this=0xb4e2f680) at wtf/FastMalloc.cpp:2378 #4 0xb4945259 in WTF::TCMalloc_PageHeap::runScavengerThread (context=0xb4e2f680) at wtf/FastMalloc.cpp:1497 #5 0xb4e67b4c in start_thread (arg=0xb0464b70) at pthread_create.c:301 #6 0xb554e94e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133 Thread 1 (Thread 0xb1d18710 (LWP 3214)): [KCrash Handler] #7 0xb7745424 in __kernel_vsyscall () #8 0xb54afdca in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #9 0xb54b12dc in abort () at abort.c:92 #10 0xb68d9068 in qt_message_output (msgType=QtFatalMsg, buf=0x904d978 ASSERT: \!resId.isEmpty()\ in file /var/tmp/portage/kde-base/kdepimlibs-4.7.2/work/kdepimlibs-4.7.2/akonadi/agentmanager.cpp, line 402) at global/qglobal.cpp:2282 #11 0xb68d91ff in qt_message (msgType=value optimized out, msg=0xb6a59768 ASSERT: \%s\ in file %s, line %d, ap=0xbfdfdbe4 *\343d\267\370\341d\267\222\001) at global/qglobal.cpp:2328 #12 0xb68d92fc in qFatal (msg=0xb6a59768 ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2511 #13 0xb68d9549 in qt_assert (assertion=0xb764e32a !resId.isEmpty(), file=0xb764e1f8 /var/tmp/portage/kde-base/kdepimlibs-4.7.2/work/kdepimlibs-4.7.2/akonadi/agentmanager.cpp, line=402) at global/qglobal.cpp:2027 #14 0xb754aecb in Akonadi::AgentManager::synchronizeCollection (this=0x897eea0, collection=..., recursive=false) at /var/tmp/portage/kde-base/kdepimlibs-4.7.2/work/kdepimlibs-4.7.2/akonadi/agentmanager.cpp:402 #15 0xb761cf61 in Akonadi::StandardActionManager::Private::slotSynchronizeCollection() () from /usr/lib/libakonadi-kde.so.4 #16 0xb761a2a0 in Akonadi::StandardActionManager::qt_metacall (this=0x8988b18, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfdfde08) at /var/tmp/portage/kde-base/kdepimlibs-4.7.2/work/kdepimlibs-4.7.2_build/akonadi/standardactionmanager.moc:155 #17 0xb69f0083 in QMetaObject::metacall (object=0x8988b18, cl=QMetaObject::InvokeMetaMethod, idx=13, argv=0xbfdfde08) at kernel/qmetaobject.cpp:237 #18 0xb6a03450 in QMetaObject::activate (sender=0x89e5560, m=0xb61baad8, local_signal_index=1, argv=0x0) at kernel/qobject.cpp:3278 #19 0xb580fc22 in QAction::triggered (this=0x89e5560, _t1=false) at .moc/debug-shared/moc_qaction.cpp:263 #20 0xb58110d9 in QAction::activate (this=0x89e5560, event=QAction::Trigger) at kernel/qaction.cpp:1257 #21 0xb5ce3857 in QMenuPrivate::activateCausedStack (this=0x8bbdbf0, causedStack=..., action=0x89e5560, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:993 #22 0xb5cea5d2 in QMenuPrivate::activateAction (this=0x8bbdbf0, action=0x89e5560, action_e=QAction::Trigger, self=value optimized out) at widgets/qmenu.cpp:1085 #23 0xb5cedb64 in QMenu::mouseReleaseEvent (this=0x8bbb358, e=0xbfdfe7d4) at widgets/qmenu.cpp:2306 #24 0xb66e157d in KMenu::mouseReleaseEvent (this=0x8bbb358, e=0xbfdfe7d4) at /var/tmp/portage/kde-base/kdelibs-4.7.2/work/kdelibs-4.7.2/kdeui/widgets/kmenu.cpp:464 #25 0xb5879140 in QWidget::event (this=0x8bbb358, event=0xbfdfe7d4) at kernel/qwidget.cpp:8259 #26 0xb5cec0da in QMenu::event (this=0x8bbb358, e=0xbfdfe7d4) at widgets/qmenu.cpp:2415 #27 0xb581837f in QApplicationPrivate::notify_helper (this=0x883fe50, receiver=0x8bbb358, e=0xbfdfe7d4) at kernel/qapplication.cpp:4462 #28 0xb582050a
[Bug 284772] Akonadi-Crash while trying out IMAP server settings
https://bugs.kde.org/show_bug.cgi?id=284772 --- Comment #1 from Thomas Fischer fischer unix-ag uni-kl de 2011-10-24 19:40:52 --- I continued to figure out how to configure my mail account without crashing Akonadi. This time, I used akonadiconsole to access the IMAP folder's configuration dialog (the same one accessible from within KMail). Both in this and in the previous crash report, Akonadi crashes as Q_ASSERT/Q_ASSERT_X is violated, therefore one can deduce that I compiled most of KDE/KMail/Kontact/Akonadi with debugging enabled. Although Q_ASSERTs are only enabled in debug releases, a programmer should still not use them too often for conditions that occur quite often as my case ... This time, I got this crash report: Application: Akonadi Console (akonadiconsole), signal: Aborted [Current thread is 1 (Thread 0xb1cea710 (LWP 3694))] Thread 2 (Thread 0xb0c2eb70 (LWP 3697)): #0 0xb7717424 in __kernel_vsyscall () #1 0xb4e3debc in pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169 #2 0xb552cf27 in __pthread_cond_wait (cond=0xb4e06770, mutex=0xb4e06758) at forward.c:139 #3 0xb491721c in WTF::TCMalloc_PageHeap::scavengerThread (this=0xb4e01680) at wtf/FastMalloc.cpp:2378 #4 0xb4917259 in WTF::TCMalloc_PageHeap::runScavengerThread (context=0xb4e01680) at wtf/FastMalloc.cpp:1497 #5 0xb4e39b4c in start_thread (arg=0xb0c2eb70) at pthread_create.c:301 #6 0xb552094e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133 Thread 1 (Thread 0xb1cea710 (LWP 3694)): [KCrash Handler] #7 0xb7717424 in __kernel_vsyscall () #8 0xb5481dca in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #9 0xb54832dc in abort () at abort.c:92 #10 0xb68ab068 in qt_message_output (msgType=QtFatalMsg, buf=0x9293f78 ASSERT: \!resId.isEmpty()\ in file /var/tmp/portage/kde-base/kdepimlibs-4.7.2/work/kdepimlibs-4.7.2/akonadi/agentmanager.cpp, line 402) at global/qglobal.cpp:2282 #11 0xb68ab1ff in qt_message (msgType=value optimized out, msg=0xb6a2b768 ASSERT: \%s\ in file %s, line %d, ap=0xbfc65714 *\003b\267\370\001b\267\222\001) at global/qglobal.cpp:2328 #12 0xb68ab2fc in qFatal (msg=0xb6a2b768 ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2511 #13 0xb68ab549 in qt_assert (assertion=0xb762032a !resId.isEmpty(), file=0xb76201f8 /var/tmp/portage/kde-base/kdepimlibs-4.7.2/work/kdepimlibs-4.7.2/akonadi/agentmanager.cpp, line=402) at global/qglobal.cpp:2027 #14 0xb751cecb in Akonadi::AgentManager::synchronizeCollection (this=0x8b0dfa0, collection=..., recursive=false) at /var/tmp/portage/kde-base/kdepimlibs-4.7.2/work/kdepimlibs-4.7.2/akonadi/agentmanager.cpp:402 #15 0xb75eef61 in Akonadi::StandardActionManager::Private::slotSynchronizeCollection() () from /usr/lib/libakonadi-kde.so.4 #16 0xb75ec2a0 in Akonadi::StandardActionManager::qt_metacall (this=0x8d36508, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfc65938) at /var/tmp/portage/kde-base/kdepimlibs-4.7.2/work/kdepimlibs-4.7.2_build/akonadi/standardactionmanager.moc:155 #17 0xb69c2083 in QMetaObject::metacall (object=0x8d36508, cl=QMetaObject::InvokeMetaMethod, idx=13, argv=0xbfc65938) at kernel/qmetaobject.cpp:237 #18 0xb69d5450 in QMetaObject::activate (sender=0x8d395d8, m=0xb618cad8, local_signal_index=1, argv=0x0) at kernel/qobject.cpp:3278 #19 0xb57e1c22 in QAction::triggered (this=0x8d395d8, _t1=false) at .moc/debug-shared/moc_qaction.cpp:263 #20 0xb57e30d9 in QAction::activate (this=0x8d395d8, event=QAction::Trigger) at kernel/qaction.cpp:1257 #21 0xb5cb5857 in QMenuPrivate::activateCausedStack (this=0x8d7f5e0, causedStack=..., action=0x8d395d8, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:993 #22 0xb5cbc5d2 in QMenuPrivate::activateAction (this=0x8d7f5e0, action=0x8d395d8, action_e=QAction::Trigger, self=value optimized out) at widgets/qmenu.cpp:1085 #23 0xb5cbfb64 in QMenu::mouseReleaseEvent (this=0x8d7cce0, e=0xbfc66304) at widgets/qmenu.cpp:2306 #24 0xb66b357d in KMenu::mouseReleaseEvent (this=0x8d7cce0, e=0xbfc66304) at /var/tmp/portage/kde-base/kdelibs-4.7.2/work/kdelibs-4.7.2/kdeui/widgets/kmenu.cpp:464 #25 0xb584b140 in QWidget::event (this=0x8d7cce0, event=0xbfc66304) at kernel/qwidget.cpp:8259 #26 0xb5cbe0da in QMenu::event (this=0x8d7cce0, e=0xbfc66304) at widgets/qmenu.cpp:2415 #27 0xb57ea37f in QApplicationPrivate::notify_helper (this=0x89cfe90, receiver=0x8d7cce0, e=0xbfc66304) at kernel/qapplication.cpp:4462 #28 0xb57f250a in QApplication::notify (this=0xbfc67c58, receiver=0x8d7cce0, e=0xbfc66304) at kernel/qapplication.cpp:4023 #29 0xb65e36ec in KApplication::notify (this=0xbfc67c58, receiver=0x8d7cce0, event=0xbfc66304) at /var/tmp/portage/kde-base/kdelibs-4.7.2/work/kdelibs-4.7.2/kdeui/kernel/kapplication.cpp:311 #30 0xb69bab15 in QCoreApplication::notifyInternal (this=0xbfc67c58, receiver=0x8d7cce0, event=0xbfc66304) at kernel/qcoreapplication.cpp:731 #31 0xb57ee012 in sendSpontaneousEvent (receiver=0x8d7cce0, event=0xbfc66304, alienWidget=0x0, nativeWidget
[Bug 284772] New: Akonadi-Crash while trying out IMAP server settings
https://bugs.kde.org/show_bug.cgi?id=284772
Summary: Akonadi-Crash while trying out IMAP server settings
Product: kontact
Version: 4.7.2
Platform: Compiled Sources
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: fisc...@unix-ag.uni-kl.de
Application: kontact (4.7.2)
KDE Platform Version: 4.7.2 (4.7.2) (Compiled from sources)
Qt Version: 4.7.3
Operating System: Linux 2.6.39-gentoo-r3-tf i686
Distribution (Platform): Gentoo Packages
-- Information about the crash:
I recently upgrade from KDE 4.6.5 to 4.7.2 and created a new account to avoid
interference with old settings. To read my emails, I added an IMAP account to
Kontact/KMail, but as I was not sure about which authentication settings to use
(the automatically detected settings did not work either), I tried various
settings.
One thing that was odd was that Kontact asked me repeatedly about my KWallet
password. Connecting did not work, as I got a dialog asking me if I want to
reconfigure this account or try again (or cancel). Trying out various
combinations of connection settings, I got this crash eventually.
As a site note, the list view in the tab for receiving email configuration has
a layout problem with the button on retrieval options if there is a message in
the list view which is too long to be shown in the given space in one line.
-- Backtrace:
Application: Kontact (kontact), signal: Aborted
[Current thread is 1 (Thread 0xb22fe710 (LWP 32449))]
Thread 2 (Thread 0xb1203b70 (LWP 32463)):
#0 0xb7719424 in __kernel_vsyscall ()
#1 0xb4387ebc in pthread_cond_wait () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2 0xb616af27 in __pthread_cond_wait (cond=0xb6042770, mutex=0xb6042758) at
forward.c:139
#3 0xb5b5321c in WTF::TCMalloc_PageHeap::scavengerThread (this=0xb603d680) at
wtf/FastMalloc.cpp:2378
#4 0xb5b53259 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=0xb603d680) at wtf/FastMalloc.cpp:1497
#5 0xb4383b4c in start_thread (arg=0xb1203b70) at pthread_create.c:301
#6 0xb615e94e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133
Thread 1 (Thread 0xb22fe710 (LWP 32449)):
[KCrash Handler]
#7 0xb7719424 in __kernel_vsyscall ()
#8 0xb60bfdca in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#9 0xb60c12dc in abort () at abort.c:92
#10 0xb6e2c068 in qt_message_output (msgType=QtFatalMsg, buf=0x998cc10 ASSERT:
\parentCollection != m_rootCollection\ in file
/var/tmp/portage/kde-base/kdepimlibs-4.7.2/work/kdepimlibs-4.7.2/akonadi/entitytreemodel_p.cpp,
line 635) at global/qglobal.cpp:2282
#11 0xb6e2c1ff in qt_message (msgType=value optimized out, msg=0xb6fac768
ASSERT: \%s\ in file %s, line %d, ap=0xbfe77c84
`\332\240\264\300\330\240\264{\002) at global/qglobal.cpp:2328
#12 0xb6e2c2fc in qFatal (msg=0xb6fac768 ASSERT: \%s\ in file %s, line %d)
at global/qglobal.cpp:2511
#13 0xb6e2c549 in qt_assert (assertion=0xb4a0da60 parentCollection !=
m_rootCollection, file=0xb4a0d8c0
/var/tmp/portage/kde-base/kdepimlibs-4.7.2/work/kdepimlibs-4.7.2/akonadi/entitytreemodel_p.cpp,
line=635) at global/qglobal.cpp:2027
#14 0xb4952447 in Akonadi::EntityTreeModelPrivate::retrieveAncestors
(this=0x94a0fe8, collection=...) at
/var/tmp/portage/kde-base/kdepimlibs-4.7.2/work/kdepimlibs-4.7.2/akonadi/entitytreemodel_p.cpp:635
#15 0xb4955e84 in Akonadi::EntityTreeModelPrivate::monitoredCollectionAdded
(this=0x94a0fe8, collection=..., parent=...) at
/var/tmp/portage/kde-base/kdepimlibs-4.7.2/work/kdepimlibs-4.7.2/akonadi/entitytreemodel_p.cpp:730
#16 0xb494721c in Akonadi::EntityTreeModel::qt_metacall (this=0x93ca3c0,
_c=QMetaObject::InvokeMetaMethod, _id=19, _a=0xbfe77f34) at
/var/tmp/portage/kde-base/kdepimlibs-4.7.2/work/kdepimlibs-4.7.2_build/akonadi/entitytreemodel.moc:161
#17 0xb6f43083 in QMetaObject::metacall (object=0x93ca3c0,
cl=QMetaObject::InvokeMetaMethod, idx=43, argv=0xbfe77f34) at
kernel/qmetaobject.cpp:237
#18 0xb6f56450 in QMetaObject::activate (sender=0x9476310, m=0xb4acb594,
local_signal_index=6, argv=0x0) at kernel/qobject.cpp:3278
#19 0xb498de7e in Akonadi::Monitor::collectionAdded (this=0x9476310, _t1=...,
_t2=...) at
/var/tmp/portage/kde-base/kdepimlibs-4.7.2/work/kdepimlibs-4.7.2_build/akonadi/monitor.moc:211
#20 0xb499161d in Akonadi::MonitorPrivate::emitCollectionNotification
(this=0x94749f0, msg=..., col=..., par=..., dest=...) at
/var/tmp/portage/kde-base/kdepimlibs-4.7.2/work/kdepimlibs-4.7.2/akonadi/monitor_p.cpp:590
#21 0xb49937c8 in Akonadi::MonitorPrivate::emitNotification (this=0x94749f0,
msg=...) at
/var/tmp/portage/kde-base/kdepimlibs-4.7.2/work/kdepimlibs-4.7.2/akonadi/monitor_p.cpp:281
#22 0xb490a90e in Akonadi::ChangeRecorderPrivate::emitNotification
(this=0x94749f0, msg=...) at
/var/tmp/portage/kde-base/kdepimlibs-4.7.2/work/kdepimlibs-4.7.2/akonadi/changerecorder_p.h:60
#23
[Bug 44880] would like to be able to strip tags from html messages
https://bugs.kde.org/show_bug.cgi?id=44880 --- Comment #16 from Thomas Fischer fischer unix-ag uni-kl de 2011-08-08 12:16:18 --- (In reply to comment #15) Is there anyway this could be made using QtWebKit? To my knowledge no, as WebKit is made for graphical presentation of HTML code and you still would need some translation step. Using lynx would avoid re-inventing the wheel. If not then the program used should be configurable as some might have another text mode browser installed. That would be possible. My patch so far is just a proof-of-concept and can be expanded. My idea would be to keep it automagically if possible, i.e automatically falling back to e.g. links2 if lynx is not available. And what is the real usecase for this? HTML display only uses html elements present in the actual mail and executes no scripts or does any access to the internet without being told so by the user. It is not only about malicious HTML code, but also about really badly formatted HTML code such as spam, mails from people with bad taste regarding fonts and colors, purists who despise any formatting at all, but like to keep a basic text structure etc. -- 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 44880] would like to be able to strip tags from html messages
https://bugs.kde.org/show_bug.cgi?id=44880 --- Comment #14 from Thomas Fischer fischer unix-ag uni-kl de 2011-08-07 12:30:22 --- Created an attachment (id=62637) -- (http://bugs.kde.org/attachment.cgi?id=62637) Prototype patch to integrate lynx in KMail This is a patch which uses lynx to render HTML code to plain text. I had no recent kdepim libraries installed (hacked at DS 2011), but the concept should be clear. If there is interest in such a solution, I will look into refining it. -- 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 259358] Re-ordering folders via drag drop not working anymore
https://bugs.kde.org/show_bug.cgi?id=259358 Thomas Fischer fisc...@unix-ag.uni-kl.de changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #7 from Thomas Fischer fischer unix-ag uni-kl de 2011-06-26 08:52:14 --- Bug 275756 is most likely a duplicate of this one. Can someone confirm that and change the other bug's status? My 2 ct to this bug: It would be a small improvement if special folders like Inbox, Drafts, or Trash would be excluded from the normal sorting and always shown at the top, i.e. directly under the node representing the mail server. -- 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 259355] kmail terminates during startup with Failed to fetch the resource collection.
https://bugs.kde.org/show_bug.cgi?id=259355 Thomas Fischer fisc...@unix-ag.uni-kl.de changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #6 from Thomas Fischer fischer unix-ag uni-kl de 2011-06-23 18:00:54 --- I confirm Frédéric's comment #5, happens on my system, too. Going to attach output from stdout/stderr. -- 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 259355] kmail terminates during startup with Failed to fetch the resource collection.
https://bugs.kde.org/show_bug.cgi?id=259355 --- Comment #7 from Thomas Fischer fischer unix-ag uni-kl de 2011-06-23 18:02:33 --- Created an attachment (id=61282) -- (http://bugs.kde.org/attachment.cgi?id=61282) Ouput on stdout/stderr when error occurrs. Error occurred on a Gentoo Linux system with KMail 4.6.0 and KDE 4.6.3 and Qt 4.7.3. -- 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 259355] kmail terminates during startup with Failed to fetch the resource collection.
https://bugs.kde.org/show_bug.cgi?id=259355 --- Comment #8 from Thomas Fischer fischer unix-ag uni-kl de 2011-06-23 18:24:21 --- Additional information: When the message box appeared, I used gdb to attach to the kmail process to get this backtrace: #0 0xb76e7424 in __kernel_vsyscall () #1 0xb5eb6bac in poll () from /lib/libc.so.6 #2 0xb45bef90 in g_poll () from /usr/lib/libglib-2.0.so.0 #3 0xb45b2b16 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0xb45b2dfd in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0xb61f0ba6 in QEventDispatcherGlib::processEvents (this=0x9052ae8, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #6 0xb6500a2c in QGuiEventDispatcherGlib::processEvents (this=0x9052ae8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #7 0xb61bf5ff in QEventLoop::processEvents (this=0xbfbc6a80, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece or DW_OP_bit_piece. ) at kernel/qeventloop.cpp:149 #8 0xb61bfa25 in QEventLoop::exec (this=0xbfbc6a80, flags=...) at kernel/qeventloop.cpp:201 #9 0xb69ca7dc in QDialog::exec (this=0x920c240) at dialogs/qdialog.cpp:552 #10 0xb743364c in KMessageBox::createKMessageBox (dialog=0x920c240, icon=..., text=..., strlist=..., ask=..., checkboxReturn=0x0, options=..., details=..., notifyType=QMessageBox::Critical) at /var/tmp/portage/kde-base/kdelibs-4.6.3-r2/work/kdelibs-4.6.3/kdeui/dialogs/kmessagebox.cpp:337 #11 0xb7433f2b in KMessageBox::createKMessageBox (dialog=0x920c240, icon=QMessageBox::Critical, text=..., strlist=..., ask=..., checkboxReturn=0x0, options=..., details=...) at /var/tmp/portage/kde-base/kdelibs-4.6.3-r2/work/kdelibs-4.6.3/kdeui/dialogs/kmessagebox.cpp:152 #12 0xb7434dcd in KMessageBox::errorListWId (parent_id=0, text=..., strlist=..., caption=..., options=...) at /var/tmp/portage/kde-base/kdelibs-4.6.3-r2/work/kdelibs-4.6.3/kdeui/dialogs/kmessagebox.cpp:847 #13 0xb7434f68 in KMessageBox::error (parent=0x0, text=..., caption=..., options=...) at /var/tmp/portage/kde-base/kdelibs-4.6.3-r2/work/kdelibs-4.6.3/kdeui/dialogs/kmessagebox.cpp:814 #14 0xb509bdce in MailCommon::Kernel::emergencyExit (this=0x90f7b40, reason=...) at /var/tmp/portage/kde-base/kmail-4.6.0-r1/work/kmail-4.6.0/mailcommon/mailkernel.cpp:193 #15 0xb509bea7 in MailCommon::Kernel::createDefaultCollectionDone (this=0x90f7b40, job=0x92c5bf0) at /var/tmp/portage/kde-base/kmail-4.6.0-r1/work/kmail-4.6.0/mailcommon/mailkernel.cpp:158 #16 0xb509c30a in MailCommon::Kernel::qt_metacall (this=0x90f7b40, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfbc7058) at /var/tmp/portage/kde-base/kmail-4.6.0-r1/work/kmail-4.6.0_build/mailcommon/mailkernel.moc:82 #17 0xb61c8093 in QMetaObject::metacall (object=0x90f7b40, cl=QMetaObject::InvokeMetaMethod, idx=6, argv=0xbfbc7058) at kernel/qmetaobject.cpp:237 #18 0xb61db460 in QMetaObject::activate (sender=0x92c5bf0, m=0xb72d1528, local_signal_index=3, argv=0xfdfc) at kernel/qobject.cpp:3278 #19 0xb718ce94 in KJob::result (this=0x92c5bf0, _t1=0x92c5bf0) at /var/tmp/portage/kde-base/kdelibs-4.6.3-r2/work/kdelibs-4.6.3_build/kdecore/kjob.moc:194 #20 0xb718d274 in KJob::emitResult (this=0x92c5bf0) at /var/tmp/portage/kde-base/kdelibs-4.6.3-r2/work/kdelibs-4.6.3/kdecore/jobs/kjob.cpp:312 #21 0xb5502292 in Akonadi::TransactionSequence::slotResult (this=0x92c5bf0, job=0x96bb4b8) at /var/tmp/portage/kde-base/kdepimlibs-4.6.3/work/kdepimlibs-4.6.3/akonadi/transactionsequence.cpp:132 #22 0xb54ed4bc in Akonadi::SpecialCollectionsRequestJob::slotResult (this=0x92c5bf0, job=0x96bb4b8) at /var/tmp/portage/kde-base/kdepimlibs-4.6.3/work/kdepimlibs-4.6.3/akonadi/specialcollectionsrequestjob.cpp:366 #23 0xb5501d7c in Akonadi::TransactionSequence::qt_metacall (this=0x92c5bf0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfbc7308) at /var/tmp/portage/kde-base/kdepimlibs-4.6.3/work/kdepimlibs-4.6.3_build/akonadi/transactionsequence.moc:76 #24 0xb54ed769 in Akonadi::SpecialCollectionsRequestJob::qt_metacall (this=0x92c5bf0, _c=QMetaObject::InvokeMetaMethod, _id=35, _a=0xbfbc7308) at /var/tmp/portage/kde-base/kdepimlibs-4.6.3/work/kdepimlibs-4.6.3_build/akonadi/specialcollectionsrequestjob.moc:73 #25 0xb5363d73 in Akonadi::SpecialMailCollectionsRequestJob::qt_metacall (this=0x92c5bf0, _c=QMetaObject::InvokeMetaMethod, _id=35, _a=0xbfbc7308) at /var/tmp/portage/kde-base/kdepimlibs-4.6.3/work/kdepimlibs-4.6.3_build/akonadi/kmime/specialmailcollectionsrequestjob.moc:64 #26 0xb61c8093 in QMetaObject::metacall (object=0x92c5bf0, cl=QMetaObject::InvokeMetaMethod, idx=35, argv=0xbfbc7308) at kernel/qmetaobject.cpp:237 #27 0xb61db460 in QMetaObject::activate (sender=0x96bb4b8, m=0xb72d1528, local_signal_index=3, argv=0xfdfc) at kernel/qobject.cpp:3278 #28 0xb718ce94 in KJob::result (this=0x96bb4b8, _t1=0x96bb4b8) at /var/tmp/portage/kde-base/kdelibs-4.6.3-r2/work/kdelibs-4.6.3_build/kdecore/kjob.moc:194 #29 0xb718d274 in KJob
[Bug 259355] kmail terminates during startup with Failed to fetch the resource collection.
https://bugs.kde.org/show_bug.cgi?id=259355 --- Comment #9 from Thomas Fischer fischer unix-ag uni-kl de 2011-06-23 18:45:36 --- As this problem did not occur on a freshly-created user on the same system, I deduced that this problem was most likely due to an old configuration setting which is not (no longer) properly supported. Removing Akonadi's settings (directories) inside ~/.config/ and ~/.local/share fixed seems to fix this problem. -- 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 250709] KMail: please use KWallet for GPG encryption/signing
https://bugs.kde.org/show_bug.cgi?id=250709 Thomas Fischer fisc...@unix-ag.uni-kl.de changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #2 from Thomas Fischer fischer unix-ag uni-kl de 2011-05-09 10:40:27 --- Expected Results: KWallet provides the passphrase or the user is prompted to open KWallet I would like to suggest an alternative path here. Instead of making KMail take care of all the password handling and GnuPG communication without pinentry, write a new pinentry application called pinentry-kwallet, which works just like pinentry-qt or pinentry-gtk, but instead of asking the user for a password, it would look into the wallet first. This approach would have two advantages: First, it does not require any changes in KMail. Second, it would work for all application using gpg+pinentry, such as Thunderbird. Programming the pinentry-kwallet application should not be too difficult if one starts from pinentry-qt, as Qt already supports dbus which can be used to query the password from KWallet's storage. Volunteers? ;-) Maybe make it a junior job ... -- 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 184324] Crash at Imap access / while starting [[QTreeWidgetItem::*], KMail::FolderView::slotFolderExpanded]
https://bugs.kde.org/show_bug.cgi?id=184324 Thomas Fischer fisc...@unix-ag.uni-kl.de changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #34 from Thomas Fischer fischer unix-ag uni-kl de 2011-04-19 22:52:05 --- I assume this is the same problem, therefore a more recent backtrace (KDE 4.6.2, KDEPIM 4.4.10, Gentoo Linux): Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #7 0xad8d29dc in QListData::size (this=0x884af30) at /usr/include/qt4/QtCore/qlist.h:94 #8 0xad93cfbe in KMail::FolderView::slotFolderExpanded (this=0x89fea88, item=0x884af18) at /var/tmp/portage/kde-base/kmail-4.4.10-r1/work/kmail-4.4.10/kmail/folderview.cpp:2471 #9 0xad9454cf in KMail::FolderView::qt_metacall (this=0x89fea88, _c=QMetaObject::InvokeMetaMethod, _id=149, _a=0xbfa0d138) at /var/tmp/portage/kde-base/kmail-4.4.10-r1/work/kmail-4.4.10_build/kmail/folderview.moc:234 #10 0xad94afc9 in KMail::MainFolderView::qt_metacall (this=0x89fea88, _c=QMetaObject::InvokeMetaMethod, _id=149, _a=0xbfa0d138) at /var/tmp/portage/kde-base/kmail-4.4.10-r1/work/kmail-4.4.10_build/kmail/mainfolderview.moc:70 #11 0xb62e40d3 in QMetaObject::metacall (object=0x89fea88, cl=QMetaObject::InvokeMetaMethod, idx=149, argv=0xbfa0d138) at kernel/qmetaobject.cpp:237 #12 0xb62f74a0 in QMetaObject::activate (sender=0x89fea88, m=0xb719c7d0, local_signal_index=6, argv=0x884af30) at kernel/qobject.cpp:3278 #13 0xb6e4a988 in QTreeWidget::itemExpanded (this=0x89fea88, _t1=0x884af18) at .moc/debug-shared/moc_qtreewidget.cpp:242 #14 0xb6e4b9d7 in QTreeWidgetPrivate::_q_emitItemExpanded (this=0x89febb0, index=...) at itemviews/qtreewidget.cpp:2272 #15 0xb6e565fe in QTreeWidget::qt_metacall (this=0x89fea88, _c=QMetaObject::InvokeMetaMethod, _id=21, _a=0xbfa0d3a8) at .moc/debug-shared/moc_qtreewidget.cpp:155 #16 0xb76031d7 in KPIM::TreeWidget::qt_metacall (this=0x89fea88, _c=QMetaObject::InvokeMetaMethod, _id=109, _a=0xbfa0d3a8) at /var/tmp/portage/kde-base/libkdepim-4.4.10/work/libkdepim-4.4.10_build/libkdepim/moc_treewidget.cpp:74 #17 0xb76757df in KPIM::FolderTreeWidget::qt_metacall (this=0x89fea88, _c=QMetaObject::InvokeMetaMethod, _id=109, _a=0xbfa0d3a8) at /var/tmp/portage/kde-base/libkdepim-4.4.10/work/libkdepim-4.4.10_build/libkdepim/foldertreewidget.moc:74 #18 0xad94547b in KMail::FolderView::qt_metacall (this=0x89fea88, _c=QMetaObject::InvokeMetaMethod, _id=109, _a=0xbfa0d3a8) at /var/tmp/portage/kde-base/kmail-4.4.10-r1/work/kmail-4.4.10_build/kmail/folderview.moc:200 #19 0xad94afc9 in KMail::MainFolderView::qt_metacall (this=0x89fea88, _c=QMetaObject::InvokeMetaMethod, _id=109, _a=0xbfa0d3a8) at /var/tmp/portage/kde-base/kmail-4.4.10-r1/work/kmail-4.4.10_build/kmail/mainfolderview.moc:70 #20 0xb62e40d3 in QMetaObject::metacall (object=0x89fea88, cl=QMetaObject::InvokeMetaMethod, idx=109, argv=0xbfa0d3a8) at kernel/qmetaobject.cpp:237 #21 0xb62f74a0 in QMetaObject::activate (sender=0x89fea88, m=0xb719bdb0, local_signal_index=0, argv=0x884af30) at kernel/qobject.cpp:3278 #22 0xb6e05492 in QTreeView::expanded (this=0x89fea88, _t1=...) at .moc/debug-shared/moc_qtreeview.cpp:201 #23 0xb6e1680a in QTreeViewPrivate::expand (this=0x89febb0, item=21, emitSignal=true) at itemviews/qtreeview.cpp:2884 #24 0xb6e18519 in QTreeView::expand (this=0x89fea88, index=...) at itemviews/qtreeview.cpp:758 #25 0xb6e190a5 in QTreeView::setExpanded (this=0x884af30, index=..., expanded=true) at itemviews/qtreeview.cpp:825 #26 0xb6e523f7 in QTreeWidget::setItemExpanded (this=0x89fea88, item=0x884af18, expand=true) at itemviews/qtreewidget.cpp:3141 #27 0xad948110 in QTreeWidgetItem::setExpanded (this=0x0, aexpand=128) at /usr/include/qt4/QtGui/qtreewidget.h:409 #28 0xad9446a2 in KMail::FolderView::restoreItemStates (this=0x89fea88) at /var/tmp/portage/kde-base/kmail-4.4.10-r1/work/kmail-4.4.10/kmail/folderview.cpp:389 #29 0xad944d8f in KMail::FolderView::reload (this=0x89fea88, openFoldersForUpdate=false) at /var/tmp/portage/kde-base/kmail-4.4.10-r1/work/kmail-4.4.10/kmail/folderview.cpp:671 #30 0xadb48235 in KMMainWidget::readConfig (this=0x8925db8) at /var/tmp/portage/kde-base/kmail-4.4.10-r1/work/kmail-4.4.10/kmail/kmmainwidget.cpp:602 #31 0xadb492c3 in KMMainWidget::KMMainWidget (this=0x8925db8, parent=0x8804280, aGUIClient=0x84c49d4, actionCollection=0x84bf7c8, config=...) at /var/tmp/portage/kde-base/kmail-4.4.10-r1/work/kmail-4.4.10/kmail/kmmainwidget.cpp:241 #32 0xadeb8e0e in KMailPart::KMailPart (this=0x84c49b0, parentWidget=0x83cf348, parent=0x83cf348, __in_chrg=value optimized out, __vtt_parm=value optimized out) at /var/tmp/portage/kde-base/kmail-4.4.10-r1/work/kmail-4.4.10/kmail/kmail_part.cpp:112 #33 0xadeba72b in KPluginFactory::createPartInstanceKMailPart (parentWidget=0x83cf348, parent=0x83cf348, args=...) at /usr/include/kpluginfactory.h:479 #34 0xb6647dc9
[Bug 261559] KMail stopped recognizing KWallet for password for specific SMTP server
https://bugs.kde.org/show_bug.cgi?id=261559 Thomas Fischer fisc...@unix-ag.uni-kl.de changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 --- Comment #7 from Thomas Fischer fischer unix-ag uni-kl de 2011-04-10 11:21:37 --- *** This bug has been confirmed by popular vote. *** -- 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 270256] New: At Kontact's startup, it asks for password, then crashes
https://bugs.kde.org/show_bug.cgi?id=270256 Summary: At Kontact's startup, it asks for password, then crashes Product: kmail2 Version: unspecified Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: fisc...@unix-ag.uni-kl.de Version: unspecified (using KDE 4.6.1) OS:Linux After recently changing my IMAP account's password, I edited/removed some of kmail's entries from KWallet. Now, at the startup of Kontact, a password dialog pops up and asks me for my password (BTW, the dialog does not say for which of my accounts, I can only guess). After entering the password, checking to store password (not checking does not make a difference) and pressing OK, KMail/Kontact crashes immediately. The crash dialog looks like this: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #7 qobject_castQTreeModel* (this=0x922d2c8, item=0x922e6a8, expand=false) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:366 #8 treeModel (this=0x922d2c8, item=0x922e6a8, expand=false) at ../../include/QtGui/private/../../../src/gui/itemviews/qtreewidget_p.h:222 #9 QTreeWidget::setItemExpanded (this=0x922d2c8, item=0x922e6a8, expand=false) at itemviews/qtreewidget.cpp:3140 #10 0xad8d8050 in QTreeWidgetItem::setExpanded (this=0xcee6, aexpand=false) at /usr/include/qt4/QtGui/qtreewidget.h:409 #11 0xad8d45e2 in KMail::FolderView::restoreItemStates (this=0x8f68b78) at /var/tmp/portage/kde-base/kmail-4.4.9/work/kmail-4.4.9/kmail/folderview.cpp:389 #12 0xad8d4ccf in KMail::FolderView::reload (this=0x8f68b78, openFoldersForUpdate=false) at /var/tmp/portage/kde-base/kmail-4.4.9/work/kmail-4.4.9/kmail/folderview.cpp:671 #13 0xadad7ee5 in KMMainWidget::readConfig (this=0x9307700) at /var/tmp/portage/kde-base/kmail-4.4.9/work/kmail-4.4.9/kmail/kmmainwidget.cpp:595 #14 0xadad8f66 in KMMainWidget::KMMainWidget (this=0x9307700, parent=0x8fe8b08, aGUIClient=0x8bdef3c, actionCollection=0x8bf4c88, config=...) at /var/tmp/portage/kde-base/kmail-4.4.9/work/kmail-4.4.9/kmail/kmmainwidget.cpp:234 #15 0xade44e0e in KMailPart::KMailPart (this=0x8bdef18, parentWidget=0x89eb9c8, parent=0x89eb9c8, __in_chrg=value optimized out, __vtt_parm=value optimized out) at /var/tmp/portage/kde-base/kmail-4.4.9/work/kmail-4.4.9/kmail/kmail_part.cpp:112 #16 0xade4672b in KPluginFactory::createPartInstanceKMailPart (parentWidget=0x89eb9c8, parent=0x89eb9c8, args=...) at /usr/include/kpluginfactory.h:479 #17 0xb638dd19 in KPluginFactory::create (this=0x8bf4730, iface=0xb5c78e00 KParts::ReadOnlyPart, parentWidget=0x89eb9c8, parent=0x89eb9c8, args=..., keyword=...) at /var/tmp/portage/kde-base/kdelibs-4.6.1-r2/work/kdelibs-4.6.1/kdecore/util/kpluginfactory.cpp:203 #18 0xb751f616 in KPluginFactory::createKParts::ReadOnlyPart (this=0x8bf4730, parent=0x89eb9c8, args=...) at /usr/include/kpluginfactory.h:503 #19 0xb751e17b in KontactInterface::Core::createPart (this=0x89eb9c8, libname=0x8c38928 kmailpart) at /var/tmp/portage/kde-base/kdepimlibs-4.6.1/work/kdepimlibs-4.6.1/kontactinterface/core.cpp:87 #20 0xb7520cb6 in KontactInterface::Plugin::loadPart (this=0x8c1ba68) at /var/tmp/portage/kde-base/kdepimlibs-4.6.1/work/kdepimlibs-4.6.1/kontactinterface/plugin.cpp:152 #21 0xade6dd62 in KMailPlugin::createPart (this=0x8c1ba68) at /var/tmp/portage/kde-base/kmail-4.4.9/work/kmail-4.4.9/kontact/plugins/kmail/kmail_plugin.cpp:179 #22 0xb75206cd in KontactInterface::Plugin::part (this=0x8c1ba68) at /var/tmp/portage/kde-base/kdepimlibs-4.6.1/work/kdepimlibs-4.6.1/kontactinterface/plugin.cpp:191 #23 0xb76bbe22 in Kontact::MainWindow::selectPlugin (this=0x89eb9c8, plugin=0x8c1ba68) at /var/tmp/portage/kde-base/kontact-4.4.9/work/kontact-4.4.9/kontact/src/mainwindow.cpp:778 #24 0xb76bba29 in Kontact::MainWindow::loadSettings (this=0x89eb9c8) at /var/tmp/portage/kde-base/kontact-4.4.9/work/kontact-4.4.9/kontact/src/mainwindow.cpp:944 #25 0xb76c100c in Kontact::MainWindow::initObject (this=0x89eb9c8) at /var/tmp/portage/kde-base/kontact-4.4.9/work/kontact-4.4.9/kontact/src/mainwindow.cpp:210 #26 0xb76c17d8 in Kontact::MainWindow::MainWindow (this=0x89eb9c8, __in_chrg=value optimized out, __vtt_parm=value optimized out) at /var/tmp/portage/kde-base/kontact-4.4.9/work/kontact-4.4.9/kontact/src/mainwindow.cpp:146 #27 0x0804b7cd in KontactApp::newInstance (this=0xbfe0f2a0) at /var/tmp/portage/kde-base/kontact-4.4.9/work/kontact-4.4.9/kontact/src/main.cpp:136 #28 0xb71041cb in KUniqueApplicationAdaptor::newInstance (this=0x8a3b4d8, asn_id=..., args=...) at /var/tmp/portage/kde-base/kdelibs-4.6.1-r2/work/kdelibs-4.6.1/kdeui/kernel/kuniqueapplication.cpp:436 #29 0xb7104883 in KUniqueApplicationAdaptor::qt_metacall (this=0x8a3b4d8, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfe0e758) at
[Bug 44880] would like to be able to strip tags from html messages
https://bugs.kde.org/show_bug.cgi?id=44880 Thomas Fischer fisc...@unix-ag.uni-kl.de changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #13 from Thomas Fischer fischer unix-ag uni-kl de 2010-12-01 13:50:46 --- A feature such as with lynx -dump would be nice. Lynx converts everything to plain text, but considers HTML formatting, e.g. for list environments. BTW, what is KDE's or Kontact's policy on using external programs like lynx? I.e. it would be easy to check during run-time to see if lynx is available and use it to render an HTML text, but fall back to the current behavior if it was not available. -- 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 251161] wrong date sort order in `find messages' window
https://bugs.kde.org/show_bug.cgi?id=251161
Thomas Fischer fisc...@unix-ag.uni-kl.de changed:
What|Removed |Added
CC||fisc...@unix-ag.uni-kl.de
--- Comment #3 from Thomas Fischer fischer unix-ag uni-kl de 2010-11-23
13:27:56 ---
The problem is that the list widget uses a lexicographical comparison by
default. To solve this issue, instead of using QTreeWidgetItem objects to
represent search results, a new class has to derived here which re-implements
the sorting function (more specifically, how two entries are compared).
My idea would be as follows (not compiled, not tested, may not work at all!):
const int ColumnDate=2;
class MatchListViewItem : public QTreeWidgetItem
{
private:
MatchListView *parent;
public:
MatchListViewItem(MatchListView *p)
: QTreeWidgetItem(p), parent(p)
{
// empty
};
bool operator( const QTreeWidgetItem other ) const
{
switch(parent-sortColumn()) {
case ColumnDate:
return
QDate::fromString(text(ColumnDate)).operator(QDate::fromString(other.text(ColumnDate)));
default:
return QTreeWidgetItem::operator(other);
}
}
};
In function SearchWindow::slotAddMsg, use this class instead of QTreeWidgetItem
when adding more results.
Maybe I'll test and refine this code later today...
--
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 251161] wrong date sort order in `find messages' window
https://bugs.kde.org/show_bug.cgi?id=251161 --- Comment #4 from Thomas Fischer fischer unix-ag uni-kl de 2010-11-23 21:33:53 --- (In reply to comment #3) The problem is that the list widget uses a lexicographical comparison by default. To solve this issue, instead of using QTreeWidgetItem objects to represent search results, a new class has to derived here which re-implements the sorting function (more specifically, how two entries are compared). [...] In function SearchWindow::slotAddMsg, use this class instead of QTreeWidgetItem when adding more results. Maybe I'll test and refine this code later today... My simple code above would not work, as the date strings are localized and not easy to compare. A better implementation would be to use nice model/view approach which has already been implemented in trunk and 4.5beta1 (not tested myself, yet). Therefore I propose to close this bug as soon as Kontact / KMail 4.5 becomes stable. Maybe mark this bug until then as WONTFIX? -- 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 175144] crash instantly at startup
https://bugs.kde.org/show_bug.cgi?id=175144 Thomas Fischer fisc...@unix-ag.uni-kl.de changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #37 from Thomas Fischer fischer unix-ag uni-kl de 2010-05-17 10:23:12 --- Same problem here. May be a duplicate of bug 156292. My KDE/Kontact packages are compiled with some more debug information, so not all variables are optimized away in contrast to comment #28 Application: Kontact (kontact), signal: Aborted [KCrash Handler] #6 0xb7813424 in __kernel_vsyscall () #7 0xb44ea6e0 in raise () from /lib/libc.so.6 #8 0xb44ebf15 in abort () from /lib/libc.so.6 #9 0xb4887045 in qt_message_output (msgType=QtFatalMsg, buf=0x926eb80 ASSERT: \!privateObject-q\ in file /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kio/kio/kdbusservicestarter.cpp, line 54) at global/qglobal.cpp:2250 #10 0xb48871e7 in qt_message (msgType=QtFatalMsg, msg=0xb4a01748 ASSERT: \%s\ in file %s, line %d, ap=0xbfb25e04 \035$\353\265\334\\353\265\066) at global/qglobal.cpp:2296 #11 0xb48872e0 in qFatal (msg=0xb4a01748 ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2479 #12 0xb488752a in qt_assert (assertion=0xb5eb241d !privateObject-q, file=0xb5eb22dc /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kio/kio/kdbusservicestarter.cpp, line=54) at global/qglobal.cpp:2013 #13 0xb5d7b4fd in KDBusServiceStarter (this=0x8fe36a8) at /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kio/kio/kdbusservicestarter.cpp:54 #14 0xb7064bb5 in ServiceStarter (this=0x8fe36a8, pluginList=0x926bd90) at /var/tmp/portage/kde-base/kontact-4.4.3/work/kontact-4.4.3/kontact/src/mainwindow.cpp:91 #15 0xb705f524 in MainWindow (this=0x926bd48, __in_chrg=value optimized out, __vtt_parm=value optimized out) at /var/tmp/portage/kde-base/kontact-4.4.3/work/kontact-4.4.3/kontact/src/mainwindow.cpp:136 #16 0x0804b8a0 in KontactApp::newInstance (this=0xbfb27c28) at /var/tmp/portage/kde-base/kontact-4.4.3/work/kontact-4.4.3/kontact/src/main.cpp:136 #17 0xb597550e in KUniqueApplicationAdaptor::newInstance (this=0x8edf5a0, asn_id=..., args=...) at /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kdeui/kernel/kuniqueapplication.cpp:454 #18 0xb59755a5 in KUniqueApplicationAdaptor::qt_metacall (this=0x8edf5a0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfb26118) at /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3_build/kdeui/kuniqueapplication_p.moc:81 #19 0xb478f2df in QDBusConnectionPrivate::deliverCall (this=0x8e74fd0, object=0x8edf5a0, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:904 #20 0xb4790661 in QDBusConnectionPrivate::activateCall (this=0x8e74fd0, object=0x8edf5a0, flags=337, msg=...) at qdbusintegrator.cpp:809 #21 0xb4790d04 in QDBusConnectionPrivate::activateObject (this=0x8e74fd0, node=..., msg=..., pathStartPos=16) at qdbusintegrator.cpp:1383 #22 0xb4791252 in QDBusActivateObjectEvent::placeMetaCall (this=0x926aa28) at qdbusintegrator.cpp:1477 #23 0xb49a773a in QObject::event (this=0xbfb27c28, e=0x926aa28) at kernel/qobject.cpp:1240 #24 0xb4995dec in QCoreApplication::event (this=0xbfb27c28, e=0x926aa28) at kernel/qcoreapplication.cpp:1533 #25 0xb4c43f2b in QApplication::event (this=0xbfb27c28, e=0x926aa28) at kernel/qapplication.cpp:2353 #26 0xb4c4169f in QApplicationPrivate::notify_helper (this=0x8e81c58, receiver=0xbfb27c28, e=0x926aa28) at kernel/qapplication.cpp:4300 #27 0xb4c481f4 in QApplication::notify (this=0xbfb27c28, receiver=0xbfb27c28, e=0x926aa28) at kernel/qapplication.cpp:4265 #28 0xb597124e in KApplication::notify (this=0xbfb27c28, receiver=0xbfb27c28, event=0x926aa28) at /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kdeui/kernel/kapplication.cpp:302 #29 0xb49961d1 in QCoreApplication::notifyInternal (this=0xbfb27c28, receiver=0xbfb27c28, event=0x926aa28) at kernel/qcoreapplication.cpp:704 #30 0xb49970f0 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x8e5d9c8) at kernel/qcoreapplication.h:215 #31 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8e5d9c8) at kernel/qcoreapplication.cpp:1345 #32 0xb4997350 in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1238 #33 0xb49c33f3 in QCoreApplication::sendPostedEvents (s=0x8e83590) at kernel/qcoreapplication.h:220 #34 postEventSourceDispatch (s=0x8e83590) at kernel/qeventdispatcher_glib.cpp:276 #35 0xb408b95e in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #36 0xb408ed31 in ?? () from /usr/lib/libglib-2.0.so.0 #37 0x08e83510 in ?? () #38 0x in ?? () -- 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
[Bug 156292] Crash after starting the second time [assert, KDBusServiceStarter, ServiceStarter, ..., KontactApp::newInstance]
https://bugs.kde.org/show_bug.cgi?id=156292 Thomas Fischer fisc...@unix-ag.uni-kl.de changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #16 from Thomas Fischer fischer unix-ag uni-kl de 2010-05-17 10:25:53 --- Same problem here with Gentoo + KDE 4.4.3. Bug report 175144 has some technical hints in comment #28, but it may be no longer valid (from March 2009). Application: Kontact (kontact), signal: Aborted [KCrash Handler] #6 0xb7813424 in __kernel_vsyscall () #7 0xb44ea6e0 in raise () from /lib/libc.so.6 #8 0xb44ebf15 in abort () from /lib/libc.so.6 #9 0xb4887045 in qt_message_output (msgType=QtFatalMsg, buf=0x926eb80 ASSERT: \!privateObject-q\ in file /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kio/kio/kdbusservicestarter.cpp, line 54) at global/qglobal.cpp:2250 #10 0xb48871e7 in qt_message (msgType=QtFatalMsg, msg=0xb4a01748 ASSERT: \%s\ in file %s, line %d, ap=0xbfb25e04 \035$\353\265\334\\353\265\066) at global/qglobal.cpp:2296 #11 0xb48872e0 in qFatal (msg=0xb4a01748 ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2479 #12 0xb488752a in qt_assert (assertion=0xb5eb241d !privateObject-q, file=0xb5eb22dc /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kio/kio/kdbusservicestarter.cpp, line=54) at global/qglobal.cpp:2013 #13 0xb5d7b4fd in KDBusServiceStarter (this=0x8fe36a8) at /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kio/kio/kdbusservicestarter.cpp:54 #14 0xb7064bb5 in ServiceStarter (this=0x8fe36a8, pluginList=0x926bd90) at /var/tmp/portage/kde-base/kontact-4.4.3/work/kontact-4.4.3/kontact/src/mainwindow.cpp:91 #15 0xb705f524 in MainWindow (this=0x926bd48, __in_chrg=value optimized out, __vtt_parm=value optimized out) at /var/tmp/portage/kde-base/kontact-4.4.3/work/kontact-4.4.3/kontact/src/mainwindow.cpp:136 #16 0x0804b8a0 in KontactApp::newInstance (this=0xbfb27c28) at /var/tmp/portage/kde-base/kontact-4.4.3/work/kontact-4.4.3/kontact/src/main.cpp:136 #17 0xb597550e in KUniqueApplicationAdaptor::newInstance (this=0x8edf5a0, asn_id=..., args=...) at /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kdeui/kernel/kuniqueapplication.cpp:454 #18 0xb59755a5 in KUniqueApplicationAdaptor::qt_metacall (this=0x8edf5a0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfb26118) at /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3_build/kdeui/kuniqueapplication_p.moc:81 #19 0xb478f2df in QDBusConnectionPrivate::deliverCall (this=0x8e74fd0, object=0x8edf5a0, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:904 #20 0xb4790661 in QDBusConnectionPrivate::activateCall (this=0x8e74fd0, object=0x8edf5a0, flags=337, msg=...) at qdbusintegrator.cpp:809 #21 0xb4790d04 in QDBusConnectionPrivate::activateObject (this=0x8e74fd0, node=..., msg=..., pathStartPos=16) at qdbusintegrator.cpp:1383 #22 0xb4791252 in QDBusActivateObjectEvent::placeMetaCall (this=0x926aa28) at qdbusintegrator.cpp:1477 #23 0xb49a773a in QObject::event (this=0xbfb27c28, e=0x926aa28) at kernel/qobject.cpp:1240 #24 0xb4995dec in QCoreApplication::event (this=0xbfb27c28, e=0x926aa28) at kernel/qcoreapplication.cpp:1533 #25 0xb4c43f2b in QApplication::event (this=0xbfb27c28, e=0x926aa28) at kernel/qapplication.cpp:2353 #26 0xb4c4169f in QApplicationPrivate::notify_helper (this=0x8e81c58, receiver=0xbfb27c28, e=0x926aa28) at kernel/qapplication.cpp:4300 #27 0xb4c481f4 in QApplication::notify (this=0xbfb27c28, receiver=0xbfb27c28, e=0x926aa28) at kernel/qapplication.cpp:4265 #28 0xb597124e in KApplication::notify (this=0xbfb27c28, receiver=0xbfb27c28, event=0x926aa28) at /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kdeui/kernel/kapplication.cpp:302 #29 0xb49961d1 in QCoreApplication::notifyInternal (this=0xbfb27c28, receiver=0xbfb27c28, event=0x926aa28) at kernel/qcoreapplication.cpp:704 #30 0xb49970f0 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x8e5d9c8) at kernel/qcoreapplication.h:215 #31 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8e5d9c8) at kernel/qcoreapplication.cpp:1345 #32 0xb4997350 in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1238 #33 0xb49c33f3 in QCoreApplication::sendPostedEvents (s=0x8e83590) at kernel/qcoreapplication.h:220 #34 postEventSourceDispatch (s=0x8e83590) at kernel/qeventdispatcher_glib.cpp:276 #35 0xb408b95e in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #36 0xb408ed31 in ?? () from /usr/lib/libglib-2.0.so.0 #37 0x08e83510 in ?? () #38 0x in ?? () -- 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
[Bug 236530] New: PATCH: Propose useful filename when saving self-test report
https://bugs.kde.org/show_bug.cgi?id=236530 Summary: PATCH: Propose useful filename when saving self-test report Product: Akonadi Version: 4.4 Platform: Gentoo Packages OS/Version: unspecified Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: vkra...@kde.org ReportedBy: fisc...@unix-ag.uni-kl.de CC: kdepim-bugs@kde.org Version:(using KDE 4.4.2) Installed from:Gentoo Packages This simple patch proposes a useful filename when saving reports from the Akonadi selftest. It is similar to DrKonqi which proposes a filename based on crash application name and date/time. -- 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 236530] PATCH: Propose useful filename when saving self-test report
https://bugs.kde.org/show_bug.cgi?id=236530 --- Comment #1 from Thomas Fischer fischer unix-ag uni-kl de 2010-05-06 10:32:38 --- Created an attachment (id=43297) -- (http://bugs.kde.org/attachment.cgi?id=43297) Patch to propose default filename for saved selftest report -- 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 219976] Crash clicking on URL in Kontact/Feeds into new tab [assert, khtml::RenderBlock::layoutBlock]
https://bugs.kde.org/show_bug.cgi?id=219976 Thomas Fischer fisc...@unix-ag.uni-kl.de changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #3 from Thomas Fischer fischer unix-ag uni-kl de 2010-03-17 12:43:37 --- I got a very similar crash when following a youtube.com. My system is Gentoo, too, using KDE 4.3.5 Application: Konqueror (kdeinit4), signal: Aborted [Current thread is 1 (Thread 0xb5884700 (LWP 14006))] Thread 3 (Thread 0xadd2fb70 (LWP 25122)): #0 0xb78df424 in __kernel_vsyscall () #1 0xb761d402 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb76bb3b0 in QWaitConditionPrivate::wait (this=0x9d12c5c, mutex=0x9d12c58, time=3) at thread/qwaitcondition_unix.cpp:85 #3 QWaitCondition::wait (this=0x9d12c5c, mutex=0x9d12c58, time=3) at thread/qwaitcondition_unix.cpp:159 #4 0xb76afaec in QThreadPoolThread::run (this=0x9d58a38) at concurrent/qthreadpool.cpp:140 #5 0xb76ba379 in QThreadPrivate::start (arg=0x9d58a38) at thread/qthread_unix.cpp:248 #6 0xb761941f in start_thread () from /lib/libpthread.so.0 #7 0xb5ec379e in clone () from /lib/libc.so.6 Thread 2 (Thread 0xaca7db70 (LWP 25139)): #0 0xb78df424 in __kernel_vsyscall () #1 0xb5ebc931 in select () from /lib/libc.so.6 #2 0xb779b054 in QProcessManager::run (this=0xb78dd890) at io/qprocess_unix.cpp:245 #3 0xb76ba379 in QThreadPrivate::start (arg=0xb78dd890) at thread/qthread_unix.cpp:248 #4 0xb761941f in start_thread () from /lib/libpthread.so.0 #5 0xb5ec379e in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb5884700 (LWP 14006)): [KCrash Handler] #6 0xb78df424 in __kernel_vsyscall () #7 0xb5e1d6e0 in raise () from /lib/libc.so.6 #8 0xb5e1ef15 in abort () from /lib/libc.so.6 #9 0xb5e1690e in __assert_fail () from /lib/libc.so.6 #10 0xb1e1fda6 in khtml::RenderBlock::layoutBlock (this=0xe159db4, relayoutChildren=false) at /var/tmp/portage/kde-base/kdelibs-4.3.5/work/kdelibs-4.3.5/khtml/rendering/render_block.cpp:749 #11 0xb1e2001b in khtml::RenderBlock::layout (this=0xe159db4) at /var/tmp/portage/kde-base/kdelibs-4.3.5/work/kdelibs-4.3.5/khtml/rendering/render_block.cpp:736 #12 0xb1d0b69d in khtml::RenderObject::layoutIfNeeded (this=0xe159db4) at /var/tmp/portage/kde-base/kdelibs-4.3.5/work/kdelibs-4.3.5/khtml/rendering/render_object.h:477 #13 0xb1e1f171 in khtml::RenderBlock::layoutBlockChildren (this=0xe159c54, relayoutChildren=false) at /var/tmp/portage/kde-base/kdelibs-4.3.5/work/kdelibs-4.3.5/khtml/rendering/render_block.cpp:1555 #14 0xb1e1fb63 in khtml::RenderBlock::layoutBlock (this=0xe159c54, relayoutChildren=false) at /var/tmp/portage/kde-base/kdelibs-4.3.5/work/kdelibs-4.3.5/khtml/rendering/render_block.cpp:835 #15 0xb1e2001b in khtml::RenderBlock::layout (this=0xe159c54) at /var/tmp/portage/kde-base/kdelibs-4.3.5/work/kdelibs-4.3.5/khtml/rendering/render_block.cpp:736 #16 0xb1d0b69d in khtml::RenderObject::layoutIfNeeded (this=0xe159c54) at /var/tmp/portage/kde-base/kdelibs-4.3.5/work/kdelibs-4.3.5/khtml/rendering/render_object.h:477 #17 0xb1e1b97a in khtml::RenderBlock::insertFloatingObject (this=0xe159bd0, o=0xe159c54) at /var/tmp/portage/kde-base/kdelibs-4.3.5/work/kdelibs-4.3.5/khtml/rendering/render_block.cpp:1954 #18 0xb1e1cdd1 in khtml::RenderBlock::handleFloatingChild (this=0xe159bd0, child=0xe159c54, marginInfo=..., handl...@0xbfcdaaab) at /var/tmp/portage/kde-base/kdelibs-4.3.5/work/kdelibs-4.3.5/khtml/rendering/render_block.cpp:998 #19 0xb1e1edd6 in khtml::RenderBlock::handleSpecialChild (this=0xe159bd0, child=0xe159c54, marginInfo=..., compactInfo=..., handl...@0xbfcdaaab) at /var/tmp/portage/kde-base/kdelibs-4.3.5/work/kdelibs-4.3.5/khtml/rendering/render_block.cpp:971 #20 0xb1e1effe in khtml::RenderBlock::layoutBlockChildren (this=0xe159bd0, relayoutChildren=true) at /var/tmp/portage/kde-base/kdelibs-4.3.5/work/kdelibs-4.3.5/khtml/rendering/render_block.cpp:1518 #21 0xb1e1fb63 in khtml::RenderBlock::layoutBlock (this=0xe159bd0, relayoutChildren=true) at /var/tmp/portage/kde-base/kdelibs-4.3.5/work/kdelibs-4.3.5/khtml/rendering/render_block.cpp:835 #22 0xb1e2001b in khtml::RenderBlock::layout (this=0xe159bd0) at /var/tmp/portage/kde-base/kdelibs-4.3.5/work/kdelibs-4.3.5/khtml/rendering/render_block.cpp:736 #23 0xb1d0b69d in khtml::RenderObject::layoutIfNeeded (this=0xe159bd0) at /var/tmp/portage/kde-base/kdelibs-4.3.5/work/kdelibs-4.3.5/khtml/rendering/render_object.h:477 #24 0xb1e1f171 in khtml::RenderBlock::layoutBlockChildren (this=0xe13a9a0, relayoutChildren=true) at /var/tmp/portage/kde-base/kdelibs-4.3.5/work/kdelibs-4.3.5/khtml/rendering/render_block.cpp:1555 #25 0xb1e1fb63 in khtml::RenderBlock::layoutBlock (this=0xe13a9a0, relayoutChildren=true) at /var/tmp/portage/kde-base/kdelibs-4.3.5/work/kdelibs-4.3.5/khtml/rendering/render_block.cpp:835 #26 0xb1e56702 in khtml::RenderLayer
[Bug 126999] kmail crashes when deleting IMAP messages
https://bugs.kde.org/show_bug.cgi?id=126999 Thomas Fischer fisc...@unix-ag.uni-kl.de changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #17 from Thomas Fischer fischer unix-ag uni-kl de 2009-12-23 20:29:42 --- (In reply to comment #16) Seems to be fixed in 4.3. Can anybody else confirm? Not fixed. I get the same crash as in you described in comment #8: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0xb4cb4786 in memcpy () from /lib/libc.so.6 #7 0x0aba0290 in ?? () #8 0xb4f5fb1d in QListData::detach2 () from /usr/lib/qt4/libQtCore.so.4 #9 0xb0c71ec2 in QListKMMessage*::detach_helper (this=0xbf9a5fac) at /usr/include/qt4/QtCore/qlist.h:524 #10 0xb0ecabfc in KMail::FolderJob::msgList (this=0xaba2218) at /var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/folderjob.cpp:120 #11 0xb0db34f5 in KMAcctImap::ignoreJobsForMessage (this=0xa1e6d10, msg=0xce2f280) at /var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/kmacctimap.cpp:215 #12 0xb0dc5a50 in KMFolderImap::ignoreJobsForMessage (this=0xa1a0c58, msg=0xce2f280) at /var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/kmfolderimap.cpp:1564 #13 0xb0e86d3a in KMMoveCommand::execute (this=0xa890220) at /var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/kmcommands.cpp:2095 #14 0xb0e956c3 in KMCommand::slotPostTransfer (this=0xa890220, result=KMCommand::OK) at /var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/kmcommands.cpp:274 #15 0xb0e95783 in KMCommand::qt_metacall (this=0xa890220, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbf9a627c) at /var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2_build/kmail/kmcommands.moc:87 #16 0xb0e95ce9 in KMMoveCommand::qt_metacall (this=0xa890220, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbf9a627c) at /var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2_build/kmail/kmcommands.moc:1706 #17 0xb0e95d97 in KMTrashMsgCommand::qt_metacall (this=0xa890220, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbf9a627c) at /var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2_build/kmail/kmcommands.moc:1758 #18 0xb504a2c3 in QMetaObject::metacall () from /usr/lib/qt4/libQtCore.so.4 #19 0xb5058683 in QMetaObject::activate () from /usr/lib/qt4/libQtCore.so.4 #20 0xb0e7d956 in KMCommand::messagesTransfered (this=0xa890220, _t1=KMCommand::OK) at /var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2_build/kmail/kmcommands.moc:102 #21 0xb0e9547a in KMCommand::transferSelectedMsgs (this=0xa890220) at /var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/kmcommands.cpp:368 #22 0xb0e967ad in KMCommand::slotStart (this=0xa890220) at /var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/kmcommands.cpp:266 #23 0xb0e95790 in KMCommand::qt_metacall (this=0xa890220, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbf9a64a8) at /var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2_build/kmail/kmcommands.moc:86 #24 0xb0e95ce9 in KMMoveCommand::qt_metacall (this=0xa890220, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbf9a64a8) at /var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2_build/kmail/kmcommands.moc:1706 #25 0xb0e95d97 in KMTrashMsgCommand::qt_metacall (this=0xa890220, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbf9a64a8) at /var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2_build/kmail/kmcommands.moc:1758 #26 0xb504a2c3 in QMetaObject::metacall () from /usr/lib/qt4/libQtCore.so.4 #27 0xb5058683 in QMetaObject::activate () from /usr/lib/qt4/libQtCore.so.4 #28 0xb5060b04 in ?? () from /usr/lib/qt4/libQtCore.so.4 #29 0xb5060c5b in ?? () from /usr/lib/qt4/libQtCore.so.4 #30 0xb5054dd6 in QObject::event () from /usr/lib/qt4/libQtCore.so.4 #31 0xb553b8b8 in QApplicationPrivate::notify_helper (this=0x9ce5660, receiver=0xae4f5c8, e=0xbf9a6a6c) at kernel/qapplication.cpp:4242 #32 0xb554410c in QApplication::notify (this=0xbf9a6cf8, receiver=0xae4f5c8, e=0xbf9a6a6c) at kernel/qapplication.cpp:4207 #33 0xb5ed127a in KApplication::notify (this=0xbf9a6cf8, receiver=0xae4f5c8, event=0xbf9a6a6c) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kdeui/kernel/kapplication.cpp:302 #34 0xb5043af1 in QCoreApplication::notifyInternal () from /usr/lib/qt4/libQtCore.so.4 #35 0xb5074703 in ?? () from /usr/lib/qt4/libQtCore.so.4 #36 0xb5070d55 in ?? () from /usr/lib/qt4/libQtCore.so.4 #37 0xb443102e in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #38 0xb4434221 in ?? () from /usr/lib/libglib-2.0.so.0 #39 0x09ce6f10 in ?? () #40 0x00c8 in ?? () #41 0x0a088ac8 in ?? () #42 0x0012 in ?? () #43 0x0017 in ?? () #44 0x0002 in ?? () #45 0xb44c93b8 in ?? () from /usr/lib/libglib-2.0.so.0 #46 0xb44c93e0 in ?? () from /usr/lib/libglib-2.0.so.0 #47 0xbf9a6b64 in ?? () #48 0xb44c93e0 in ?? () from /usr/lib/libglib-2.0.so.0 #49
[Bug 163071] Crash when deleting messages from inbox
https://bugs.kde.org/show_bug.cgi?id=163071 Thomas Fischer fisc...@unix-ag.uni-kl.de changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #117 from Thomas Fischer fischer unix-ag uni-kl de 2009-12-23 20:37:30 --- Can confirm bug on Gentoo Linux with KDE 4.3.4 and matching Kontact (KMail 1.12.2) -- 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 171555] kmail forgets shortcuts assigned via Settings Configure shortcuts
https://bugs.kde.org/show_bug.cgi?id=171555 Thomas Fischer fisc...@unix-ag.uni-kl.de changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #9 from Thomas Fischer fischer unix-ag uni-kl de 2009-10-23 09:09:09 --- (In reply to comment #4) I had a similar problem myself the other day. I solved it by removing ~/.kde/share/apps/kmail/kmail.rc (for KMail) ~/.kde/share/apps/kmail/kmail_part.rc (for Kontact). worth a try anyway I can confirm that in my case this work-around helped. Following Sven's approach, I noticed that the version number switched from 412 to 414 between my old config file and the new file created next time by KMail/Kontact. Using the old config file with changing the version number only worked, too. -- 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 193557] Randomly, saved attachments from Kmail are empty (0bytes)
https://bugs.kde.org/show_bug.cgi?id=193557 Thomas Fischer fisc...@unix-ag.uni-kl.de changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #5 from Thomas Fischer fischer unix-ag uni-kl de 2009-08-25 14:46:53 --- Sometimes i can solve this by clicking on another message and then on the message i'm interested in. or using 'save all..' in the 'description' subwindow at bottom. I can confirm the same behavior and changing between messages may improve the situation. If you are working on an IMAP folder, maybe the problem is related to a general synchronization problem as observed in bug 203868. I don't remember seeing either this bug or bug 203868 in earlier versions of KMail/Kontact, so I might got introduced in KMails 1.11.x (KDE 4.2.x) cycle... BTW, I'm using Gentoo Linux with KDE 4.2.4 and KMail 1.11.4 (Kontact 1.4.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 203868] New: Inconsistency between header info in message list and message view
https://bugs.kde.org/show_bug.cgi?id=203868 Summary: Inconsistency between header info in message list and message view Product: kmail Version: 1.11.4 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: fisc...@unix-ag.uni-kl.de Version: 1.11.4 (using KDE 4.2.4) Compiler: gcc (Gentoo 4.3.2-r3 p1.6, pie-10.1.5) 4.3.2 CFLAGS=-O2 -march=prescott -pipe OS:Linux Installed from:Gentoo Packages When accessing an IMAP account (not DIMAP), for some mails the message list view does not show all header information properly (e.g. subject), whereas the message view for the same email displays all information correctly. In my example, for some emails the subject is shown as (No Subject) and the date is set to Unknown. Clicking on the mail (thus showing it in the message view) updates the date to the correct value, whereas the subject stays (No Subject). It is not obvious why some mails are affected and others not. Corruption of the IMAP database can be excluded as when accessing the IMAP account via webmail no problems occur. Screenshot visualizing behavior will be attached to bugreport. -- 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 203868] Inconsistency between header info in message list and message view
https://bugs.kde.org/show_bug.cgi?id=203868 --- Comment #1 from Thomas Fischer fischer unix-ag uni-kl de 2009-08-14 19:41:55 --- Created an attachment (id=36152) -- (http://bugs.kde.org/attachment.cgi?id=36152) Screenshot visualizing inconsistency -- 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 165841] IMAP resources not working
https://bugs.kde.org/show_bug.cgi?id=165841 Thomas Fischer fisc...@unix-ag.uni-kl.de changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #11 from Thomas Fischer fischer unix-ag uni-kl de 2009-02-19 18:31:52 --- FYI, this bug still appears in KMail 1.10.0 (KDE 4.2.0). The work-around as proposed in comment #1 in bug 150790 (adding TheIMAPResourceAccount=xxx to config/kmailrc) fixes the problem. -- 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
