[kmail2] [Bug 484104] New: KMail will not start with libzxing2 2.2.1-1xneon+22.04+jammy+release+build12
https://bugs.kde.org/show_bug.cgi?id=484104 Bug ID: 484104 Summary: KMail will not start with libzxing2 2.2.1-1xneon+22.04+jammy+release+build12 Classification: Applications Product: kmail2 Version: 6.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jos...@joshuakugler.com Target Milestone: --- SUMMARY With the recent upgrade of libzxing to 2.2.1-1xneon+22.04+jammy+release+build12 KMail fails to start, throwing this error: kmail: error while loading shared libraries: libZXing.so.3: cannot open shared object file: No such file or directory STEPS TO REPRODUCE 1. Upgrade to libzxing2 2.2.1-1xneon+22.04+jammy+release+build12 2. Try to start KMail OBSERVED RESULT Fails to start, with given error message. EXPECTED RESULT KMail starts SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Neon (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Downgrading to 2.1.0-0xneon+22.04+jammy+release+build8 fixed the issue. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 482568] Links don't convert cursor to a hand, and don't open when clicked
https://bugs.kde.org/show_bug.cgi?id=482568 --- Comment #3 from Joshua J. Kugler --- But even in non-HTML messages, cursor still does not convert to a hand. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 482568] Links don't convert cursor to a hand, and don't open when clicked
https://bugs.kde.org/show_bug.cgi?id=482568 --- Comment #2 from Joshua J. Kugler --- Oddly enough, text converted to links (such as in a non-html message) can simply be clicked. Images/links in an HTML message must be right-clicked. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 483060] Akonadi sending UTC timestamps as local time to MySQL (and this failing around DST change) - QMYSQL bug?
https://bugs.kde.org/show_bug.cgi?id=483060 --- Comment #7 from Joshua J. Kugler --- (In reply to Christophe Marin from comment #2) > Duplicate of 483061? That's quite funny. Mine is even the very next bug filed after this one. :) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 483060] Akonadi sending UTC timestamps as local time to MySQL (and this failing around DST change) - QMYSQL bug?
https://bugs.kde.org/show_bug.cgi?id=483060 --- Comment #6 from Joshua J. Kugler --- When I was debugging this, someone in the #maria IRC channel said: > As a workaround SQL mode flag ALLOW_INVALID_DATES should help, but it is > better to store the UTC values properply as UTC. So, there is that...but that does seem ugly. Can you even specify a TZ on a TIMESTAMP column in MySQL/MariaDB (it's been too long since I've actively used MySQL). Another idea: have Akonadi set the client time zone to UTC when it connects. BUT: I don't know what that might do to the times it returns in other queries, so would require investigation, and if code would have to be changed elsewhere. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 483061] Akonadi server does not declare UTC times as UTC
https://bugs.kde.org/show_bug.cgi?id=483061 --- Comment #1 from Joshua J. Kugler --- It occurred to me this could also cause a problem with receiving e-mail. The "datetime" column is also a timestamp, and if Akonadi gets an e-mail that was sent between 2AM and 3AM UTC on a daly light savings change day, it could throw an error when trying to store it. Possibly resulting in data loss? I'm not sure. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 483061] New: Akodani server does not declare UTC times as UTC, resulting in brief denial of service
https://bugs.kde.org/show_bug.cgi?id=483061 Bug ID: 483061 Summary: Akodani server does not declare UTC times as UTC, resulting in brief denial of service Classification: Frameworks and Libraries Product: Akonadi Version: 6.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: jos...@joshuakugler.com CC: c...@carlschwan.eu Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Try to access e-mail in a time when you are going to "spring forward" and it generates an atime with a time between 2AM and 3AM. OBSERVED RESULT KMail hangs and gets the dreaded "Retrieving folder contents" hang. This error is seen in the logs: Error text: "Incorrect datetime value: '2024-03-10 02:15:10' for column `akonadi`.`pimitemtable`.`datetime` at row 1 QMYSQL: Unable to execute statement" This tipped me off: https://linustechtips.com/topic/1028839-mariadb-need-help-incorrect-datetime-value-2018-03-25-022324/ Conclusion: Akonadi is inserting time as UTC, but not declaring it UTC, and the DB server is saying "That's not a valid time in my time zone!" (I'm currently in Americas/Anchorage). Yes, I also am a programmer. Yes, I also hate date/time math. EXPECTED RESULT Message loads. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Neon all packages up to date (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Now that is after 2024-03-10 03:00:00 UTC, I can once again access my e-mails. :) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 482568] New: Links don't convert cursor to a hand, and don't open when clicked
https://bugs.kde.org/show_bug.cgi?id=482568 Bug ID: 482568 Summary: Links don't convert cursor to a hand, and don't open when clicked Classification: Applications Product: kmail2 Version: 6.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: jos...@joshuakugler.com Target Milestone: --- SUMMARY Hovering over a link no longer makes the cursor a hand, and clicking on the link doesn't open the link. Right clicking and selecting "Open URL" *does* work. STEPS TO REPRODUCE 1. Get e-mail 2. Hover over link 3. Click OBSERVED RESULT No "hand" cursor, link doesn't open in browser EXPECTED RESULT Cursor turns into a hand, and link opens. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon, latest packages (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 482442] After update to plasma 6, akonadi can't start because mysql configuration is missing/faulty
https://bugs.kde.org/show_bug.cgi?id=482442 --- Comment #4 from Joshua J. Kugler --- In /etc/apparmor.d/, I ran: sudo aa-complain ./mariadbd_akonadi sudo aa-complain ./mysqld_akonadi Akonadi is up and running now. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 482442] After update to plasma 6, akonadi can't start because mysql configuration is missing/faulty
https://bugs.kde.org/show_bug.cgi?id=482442 --- Comment #3 from Joshua J. Kugler --- In trying to invoke mysqld directly: $ /usr/sbin/mysqld --defaults-file=/home/jkugler/.local/share/akonadi/mysql.conf --datadir=/home/jkugler/.local/share/akonadi/db_data/ --socket=/run/user/1000/akonadi/mysql.socket --pid-file=/run/user/1000/akonadi/mysql.pid MariaDB starts and runs without issue. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 482442] After update to plasma 6, akonadi can't start because mysql configuration is missing/faulty
https://bugs.kde.org/show_bug.cgi?id=482442 --- Comment #2 from Joshua J. Kugler --- Seems this bug had a similar error (Permission denied): https://bugs.kde.org/show_bug.cgi?id=427618 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 482442] After update to plasma 6, akonadi can't start because mysql configuration is missing/faulty
https://bugs.kde.org/show_bug.cgi?id=482442
Joshua J. Kugler changed:
What|Removed |Added
CC||jos...@joshuakugler.com
--- Comment #1 from Joshua J. Kugler ---
Similar problems. Fresh install. Installed kmail, had to manually install
akonadi-backend-mysql. Akonadi still won't start.
$ akonadictl start
org.kde.pim.akonadictl: Starting Akonadi Server...
org.kde.pim.akonadictl:done.
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: Failed to detect mysqld version!
org.kde.pim.akonadiserver: Could not start database server!
org.kde.pim.akonadiserver: executable: "/usr/sbin/mysqld"
org.kde.pim.akonadiserver: arguments:
QList("--defaults-file=/home/jkugler/.local/share/akonadi/mysql.conf",
"--datadir=/home/jkugler/.local/share/akonadi/db_data/",
"--socket=/run/user/1000/akonadi/mysql.socket",
"--pid-file=/run/user/1000/akonadi/mysql.pid")
org.kde.pim.akonadiserver: process error: "execve: Permission denied"
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited
normally...
Tried sudo aa-complain /usr/bin/akonadiserver and got the error "ERROR: Include
file /etc/apparmor.d/local/mariadbd_akonadi not found"
Currently stuck. :)
--
You are receiving this mail because:
You are the assignee for the bug.
[kmail2] [Bug 475256] New: Crash when searching for messages
https://bugs.kde.org/show_bug.cgi?id=475256 Bug ID: 475256 Summary: Crash when searching for messages Classification: Applications Product: kmail2 Version: unspecified Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jos...@joshuakugler.com Target Milestone: --- Application: kmail (5.24.1 (23.08.1)) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.4.6-76060406-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: I tried to search for a specific string in all folders, "complete message." After finding what seemed like way too many messages (given the string; but that's another issue) KMail simply crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KMail (kmail), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139982423506048) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=139982423506048) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=139982423506048, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7f503b642476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f503b6287f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7f503baa2b9e in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x7f503baae20c in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #11 0x7f503baae277 in std::terminate() () from /lib/x86_64-linux-gnu/libstdc++.so.6 #12 0x7f503baae4d8 in __cxa_throw () from /lib/x86_64-linux-gnu/libstdc++.so.6 #13 0x7f5039e6bb3d in ?? () from /lib/x86_64-linux-gnu/libKPim5AkonadiCore.so.5 #14 0x7f5045903fa2 in ?? () from /lib/x86_64-linux-gnu/libkmailprivate.so.5 #15 0x7f5045931b41 in ?? () from /lib/x86_64-linux-gnu/libkmailprivate.so.5 #16 0x7f5045932aa2 in ?? () from /lib/x86_64-linux-gnu/libkmailprivate.so.5 #17 0x7f5039f8145e in Akonadi::EntityTreeModel::data(QModelIndex const&, int) const () from /lib/x86_64-linux-gnu/libKPim5AkonadiCore.so.5 #18 0x7f503c086b99 in QSortFilterProxyModel::data(QModelIndex const&, int) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f503d00aeae in QAbstractItemDelegate::helpEvent(QHelpEvent*, QAbstractItemView*, QStyleOptionViewItem const&, QModelIndex const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f503cff50d9 in QAbstractItemView::viewportEvent(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f503c0bcbda in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f503cd6c752 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f503cd753e1 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f503c0bce7a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f503cd72239 in QApplication::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7f503cd6c763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7f503c0bce7a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f503c11569b in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7f503c115fe4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7f50372bed3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7f5037314258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 0x7f50372bc3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x7f503c116368 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7f503c0bb79b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x7f503c0c3d44 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #36 0x56419bda2dbb in ?? () #37 0x7f503b629d90 in __libc_start_call_main (main=main@entry=0x56419bda1cb0, argc=argc@entry=3, argv=argv@entry=0x7ffc3dcc5ba8) at ../sysdeps/nptl/libc_start_call_main.h:58 #38 0x7f503b629e40 in __libc_start_main_impl (main=0x56419bda1cb0, argc=3, argv=0x7ffc3dcc5ba8, init=, fini=, rtld_fini=, stack_end=0x7ffc3dcc5b98) at ../csu/libc-start.c:392 #39 0x56419bda3915 in ?? () [Inferior 1 (process 964605) detached] The reporter indicates this bug may be a duplicate of or related to bug 472052. Reported using DrKonqi -- You are receiving this
[kmail2] [Bug 450550] K-Mail does not print images in an e-mail
https://bugs.kde.org/show_bug.cgi?id=450550 Joshua J. Kugler changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #5 from Joshua J. Kugler --- This is fixed as of (and maybe before) KMail Version 5.23.1 (23.04.1). I was just able to print an e-mail with all images included. This worked both with hitting Ctrl-P while the mail displayed in the main window, and opening the message in a separate window and hitting Ctrl-P. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 450550] K-Mail does not print images in an e-mail
https://bugs.kde.org/show_bug.cgi?id=450550 --- Comment #3 from Joshua J. Kugler --- Not an exact duplicate, as that bug said "Wherever a graphic image is in an email, it gets replaced with blank space in the printout." This may be related to a security setting. I have K-Mail configured to show all graphics when it displays e-mail. However, if I open the e-mail in a separate window, I get a message that says: """ Note: This HTML message may contain external references to images etc. For security/privacy reasons external references are not loaded. If you trust the sender of this message then you can load the external references for this message by clicking here. """ And all the images are broken image icons. I went through all the security settings and couldn't find any additional settings that allowed images in separate windows or when printing. I wonder if some (hidden?) setting is prevent it from fetching images during a print. There is no print preview, so I can't check that. way. Even if I click the link to load images in the external window, it still prints with broken image icons. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 450550] K-Mail does not print images in an e-mail
https://bugs.kde.org/show_bug.cgi?id=450550 --- Comment #1 from Joshua J. Kugler --- This bug has been around for quite a while. I found this when googling: https://www.reddit.com/r/kde/comments/eu0wjo/kmail_print_image/ -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 450550] New: K-Mail does not print images in an e-mail
https://bugs.kde.org/show_bug.cgi?id=450550 Bug ID: 450550 Summary: K-Mail does not print images in an e-mail Product: kmail2 Version: 5.13.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: jos...@joshuakugler.com Target Milestone: --- SUMMARY K-Mail does not print the images in an e-mail. "Print background color and images" is checked in Settings -> Misc -> Printing STEPS TO REPRODUCE 1. Get an e-mail with images referenced remotely 2. Print OBSERVED RESULT "Broken image" icon in print out EXPECTED RESULT E-mail printed with images viewable as when viewed in Kmail SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.18.8 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 376333] KMail crashed while opening on KDE Neon distribution (fresh install)
https://bugs.kde.org/show_bug.cgi?id=376333 Joshua J. Kugler changed: What|Removed |Added CC||jos...@joshuakugler.com --- Comment #1 from Joshua J. Kugler --- This bug is going on three years, and I'm still hitting it. I just installed Neon (neon-user-20191226-1116.iso). Logged in. Installed Kmail. Started it. New profile dialog came up, and then it put up a dialog box: The Email program encountered a fatal error and will terminate now. The error was: Invalid parent Letting KMail die, and starting it again seems to let it proceed, but it did fail on both fresh installs I tried. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 297930] Kmail hangs on "Retrieving folder contents ... please wait"
https://bugs.kde.org/show_bug.cgi?id=297930 Joshua J. Kugler <jos...@joshuakugler.com> changed: What|Removed |Added CC||jos...@joshuakugler.com --- Comment #19 from Joshua J. Kugler <jos...@joshuakugler.com> --- Just hit this problem today. KMail Version: 5.1.3 KDE Plasma Version: 5.6.5 KDE Frameworks Version: 5.23.0 Qt Version: 5.5.1 Thanks Dimitris for the work-around! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 323294] error "Could not move message" after pop3 filter
https://bugs.kde.org/show_bug.cgi?id=323294 --- Comment #8 from Joshua J. Kugler <jos...@joshuakugler.com> --- Are there KDE 5.x packages for Ubuntu 14.04? I'm still on 14.04, since it is LTS. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 306954] Sometimes get "could not move message" when trying to delete messages.
https://bugs.kde.org/show_bug.cgi?id=306954 --- Comment #7 from Joshua J. Kugler <jos...@joshuakugler.com> --- I still get this constantly on KMail version 4.14.3 (KDE 4.14.13). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 323294] error "Could not move message" after pop3 filter
https://bugs.kde.org/show_bug.cgi?id=323294 --- Comment #6 from Joshua J. Kugler <jos...@joshuakugler.com> --- I still get this constantly on KMail version 4.14.3 (KDE 4.14.13). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 323294] error "Could not move message" after pop3 filter
https://bugs.kde.org/show_bug.cgi?id=323294 --- Comment #5 from Joshua J. Kugler <jos...@joshuakugler.com> --- I still get this constantly on KMail version 4.14.3 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 333514] Maildir items are never expired from Akonadi cache because of Baloo
https://bugs.kde.org/show_bug.cgi?id=333514 Joshua J. Kugler <jos...@joshuakugler.com> changed: What|Removed |Added CC||jos...@joshuakugler.com --- Comment #20 from Joshua J. Kugler <jos...@joshuakugler.com> --- I am also seeing this issue KDE 4.14.2. It is making files_db_data is 4.8G and over 243,000 files. Should we open a new bug? -- 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 333514] Maildir items are never expired from Akonadi cache because of Baloo
https://bugs.kde.org/show_bug.cgi?id=333514 --- Comment #22 from Joshua J. Kugler <jos...@joshuakugler.com> --- Thanks for the command. After further resarch (and talking to dvratil on #akonadi) it seems I may be hitting this bug https://bugs.kde.org/show_bug.cgi?id=341884 I'm on Kubuntu, so I'll see what I can do to get the latest packages. -- 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 339937] HTML messages do not display, despite Prefer HTML to plain text being checked
https://bugs.kde.org/show_bug.cgi?id=339937 --- Comment #2 from Joshua J. Kugler jos...@joshuakugler.com --- Please close this bug as not a bug. Somehow, one folder got it's default view set to plain text. Not sure how that happened. -- 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 339937] HTML messages do not display, despite Prefer HTML to plain text being checked
https://bugs.kde.org/show_bug.cgi?id=339937 Joshua J. Kugler jos...@joshuakugler.com changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #3 from Joshua J. Kugler jos...@joshuakugler.com --- Is not a bug. :) -- 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 339937] HTML messages do not display, despite Prefer HTML to plain text being checked
https://bugs.kde.org/show_bug.cgi?id=339937 --- Comment #1 from Joshua J. Kugler jos...@joshuakugler.com --- Still present in 4.14.2. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 339937] New: HTML messages do not display, despite Prefer HTML to plain text being checked
https://bugs.kde.org/show_bug.cgi?id=339937 Bug ID: 339937 Summary: HTML messages do not display, despite Prefer HTML to plain text being checked Product: kmail2 Version: 4.14.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: misc Assignee: kdepim-bugs@kde.org Reporter: jos...@joshuakugler.com I am running KDE 4.14.1 In my security settings, Prefer HTML to plain text is checked. However, whenever I get an HTML e-mail, and open it, I see the HTML, and get a message that says: Note: This is an HTML message. For security reasons, only the raw HTML code is shown. If you trust the sender of this message then you can activate formatted HTML display for this message by clicking here. I should not have to click that every time, given my configuration. -- 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 339937] HTML messages do not display, despite Prefer HTML to plain text being checked
https://bugs.kde.org/show_bug.cgi?id=339937 Joshua J. Kugler jos...@joshuakugler.com changed: What|Removed |Added Version|4.14.0 |4.14.1 -- 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 335162] New: KMail hangs while trying to delete a message with calendar information
https://bugs.kde.org/show_bug.cgi?id=335162 Bug ID: 335162 Summary: KMail hangs while trying to delete a message with calendar information Classification: Unclassified Product: kmail2 Version: 4.13 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jos...@joshuakugler.com I am pulling messages down from an Exchange server via POP. Every time I try to delete a message that is a calendar event (update, invite, cancellation) KMail hangs, the Moving Messages progress bar (or rather, slider, since it doesn't update on progress) keeps going back and forth, and now any message I try to access says Retrieving Folder Contents Please wait... I have to restart Akonadi to get Kmail to function again, and when I do the message is still there. Digging into the file system, I see the message is still in the FolderName/new directory. Reproducible: Always Steps to Reproduce: 1. get a message that is a caldendar update 2. try to delete it 3. Actual Results: KMail hangs Expected Results: Deletes message -- 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 335162] KMail hangs while trying to delete a message with calendar information
https://bugs.kde.org/show_bug.cgi?id=335162 --- Comment #1 from Joshua J. Kugler jos...@joshuakugler.com --- Discovered this also happens when I just view the message, then try to view another message. -- 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 335162] KMail hangs while trying to delete a message with calendar information
https://bugs.kde.org/show_bug.cgi?id=335162 --- Comment #2 from Joshua J. Kugler jos...@joshuakugler.com --- Created attachment 86757 -- https://bugs.kde.org/attachment.cgi?id=86757action=edit A message showing the behavior -- 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 323294] error Could not move message after pop3 filter
https://bugs.kde.org/show_bug.cgi?id=323294 Joshua J. Kugler jos...@joshuakugler.com changed: What|Removed |Added CC||jos...@joshuakugler.com --- Comment #3 from Joshua J. Kugler jos...@joshuakugler.com --- Still an issue in 4.13. -- 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 325612] When filter modifies identity on incoming mail, FROM header is rewritten
https://bugs.kde.org/show_bug.cgi?id=325612 --- Comment #2 from Joshua J. Kugler jos...@joshuakugler.com --- Thank you very much! Do you have a link for this change? -- 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 325612] New: When filter modifies identity on incoming mail, FROM header is rewritten
https://bugs.kde.org/show_bug.cgi?id=325612 Bug ID: 325612 Summary: When filter modifies identity on incoming mail, FROM header is rewritten Classification: Unclassified Product: kmail2 Version: 4.11.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: misc Assignee: kdepim-bugs@kde.org Reporter: jos...@joshuakugler.com I just upgraded 4.11.2 today. I have four filters, one for each of my POP accounts, that are like this: Criteria: Size in bytes 0 Advanced: Apply this filter - from checked accounts only Each filter is then configured to set an identity on the e-mail that corresponds to that POP account. After upgrading today, this filter is rewriting the FROM header of **ALL** incoming e-mail to be that of the e-mail in the identity. For example, when I get e-mail from my personal POP account, the filter runs Set Identity To the Personal identity, and then all incoming e-mail is FROM Joshua J. Kugler jos...@com regardless of who sent the message. The work-around (and the confirmation) is disabling the filter, and the retrieving messages from the POP account. Then FROM lines will stay correct. -- 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
[akregator] [Bug 323585] New: Akregator crashes when displaying some web sites
https://bugs.kde.org/show_bug.cgi?id=323585 Bug ID: 323585 Summary: Akregator crashes when displaying some web sites Classification: Unclassified Product: akregator Version: 4.11 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jos...@joshuakugler.com Application: akregator (4.11) KDE Platform Version: 4.11.00 Qt Version: 4.8.2 Operating System: Linux 3.2.0-51-generic x86_64 Distribution: Ubuntu 12.04.2 LTS -- Information about the crash: I was browsing the web sites in the planet turbobears feed. http://planet.turbogears.org/rss20.xml I had opened the last three articles, and suddenly the application crashed. Never seen it happen before in Akregator. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7ffbfe56b7c0 (LWP 2736))] Thread 4 (Thread 0x7ffbd8e01700 (LWP 3328)): #0 0x7ffbfb0b8313 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7ffbf5b1c036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ffbf5b1c164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffbfbccc926 in QEventDispatcherGlib::processEvents (this=0x7ffbd4002df0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7ffbfbc9be62 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7ffbfbc9c0b7 in QEventLoop::exec (this=0x7ffbd8e00d90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7ffbfbb9b077 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7ffbfbc7bb6f in QInotifyFileSystemWatcherEngine::run (this=0x33a87b0) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7ffbfbb9e09b in QThreadPrivate::start (arg=0x33a87b0) at thread/qthread_unix.cpp:307 #9 0x7ffbf5fe8e9a in start_thread (arg=0x7ffbd8e01700) at pthread_create.c:308 #10 0x7ffbfb0c3ccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 3 (Thread 0x7ffbd9da2700 (LWP 10792)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:215 #1 0x7ffbfbb9e50f in wait (time=3, this=0x1812530) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=optimized out, mutex=0x18124a8, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7ffbfbb9168f in QThreadPoolThread::run (this=0x52775b0) at concurrent/qthreadpool.cpp:141 #4 0x7ffbfbb9e09b in QThreadPrivate::start (arg=0x52775b0) at thread/qthread_unix.cpp:307 #5 0x7ffbf5fe8e9a in start_thread (arg=0x7ffbd9da2700) at pthread_create.c:308 #6 0x7ffbfb0c3ccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x in ?? () Thread 2 (Thread 0x7ffbd12da700 (LWP 10793)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:215 #1 0x7ffbfbb9e50f in wait (time=3, this=0x1812530) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=optimized out, mutex=0x18124a8, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7ffbfbb9168f in QThreadPoolThread::run (this=0x23c9fe0) at concurrent/qthreadpool.cpp:141 #4 0x7ffbfbb9e09b in QThreadPrivate::start (arg=0x23c9fe0) at thread/qthread_unix.cpp:307 #5 0x7ffbf5fe8e9a in start_thread (arg=0x7ffbd12da700) at pthread_create.c:308 #6 0x7ffbfb0c3ccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x in ?? () Thread 1 (Thread 0x7ffbfe56b7c0 (LWP 2736)): [KCrash Handler] #6 0x7ffbf82b646a in type (this=0x7ffbd8eb6b80) at ../../kjs/value.h:452 #7 KJS::cloneInternal (exec=0x7ec85e0, ctx=0x7ec85c0, in=0x7ffbd8eb6b80, path=...) at ../../khtml/ecma/kjs_data.cpp:37 #8 0x7ffbf82b6913 in KJS::encapsulateMessageEventData (exec=0x7ec85e0, ctx=optimized out, data=optimized out) at ../../khtml/ecma/kjs_data.cpp:117 #9 0x7ffbf82b6b05 in KJS::DelayedPostMessage::execute (this=0x8a911e0, w=optimized out) at ../../khtml/ecma/kjs_data.cpp:169 #10 0x7ffbf826839b in KJS::Window::afterScriptExecution (this=0x7ffbd92e0b40) at ../../khtml/ecma/kjs_window.cpp:1549 #11 0x7ffbf826f4f4 in KJS::WindowQObject::timerEvent (this=0x5a7aa70) at ../../khtml/ecma/kjs_window.cpp:2704 #12 0x7ffbfbcb6679 in QObject::event (this=0x5a7aa70, e=optimized out) at kernel/qobject.cpp:1157 #13 0x7ffbfc69c7b4 in notify_helper (e=0x7fff37794ea0, receiver=0x5a7aa70, this=0x13f5230) at kernel/qapplication.cpp:4556 #14 QApplicationPrivate::notify_helper (this=0x13f5230, receiver=0x5a7aa70, e=0x7fff37794ea0) at
[kmail2] [Bug 312460] Kmail can not show correct number of unread mails
https://bugs.kde.org/show_bug.cgi?id=312460 Joshua J. Kugler jos...@joshuakugler.com changed: What|Removed |Added CC||jos...@joshuakugler.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 312460] Kmail can not show correct number of unread mails
https://bugs.kde.org/show_bug.cgi?id=312460 --- Comment #12 from Joshua J. Kugler jos...@joshuakugler.com --- Also still present in version 4.10.1. -- 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 299968] Filters aren't applied on incoming mails
https://bugs.kde.org/show_bug.cgi?id=299968 Joshua J. Kugler jos...@joshuakugler.com changed: What|Removed |Added CC||jos...@joshuakugler.com --- Comment #22 from Joshua J. Kugler jos...@joshuakugler.com --- I have upgraded to 4.10.1. Filters are working much better! I still have one account, however, where the incoming messages are are not filtered until I do a manual filtering. This is the same account that is not getting it's identity set properly. I have a filter for this account to set the identity, and a couple upgrades ago, the filter broke, setting it to a different identity in my config. What information do you need from me to trouble shoot this? -- 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 306954] Sometimes get could not move message when trying to delete messages.
https://bugs.kde.org/show_bug.cgi?id=306954 --- Comment #2 from Joshua J. Kugler jos...@joshuakugler.com --- This also happens on certain folders. For example, every time I enter an inbox folder for one of my accounts, i get several (a couple dozen?) notices that it can't move messages. When the process runs to sync the local folders (or when I restart Akonadi), I can get several dozen such notices. -- 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 306954] Sometimes get could not move message when trying to delete messages.
https://bugs.kde.org/show_bug.cgi?id=306954 --- Comment #3 from Joshua J. Kugler jos...@joshuakugler.com --- By the way, this is still present in 4.10.0 -- 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 309775] New: Crash on checking IMAP mail
https://bugs.kde.org/show_bug.cgi?id=309775 Bug ID: 309775 Severity: crash Version: 4.9 Priority: NOR CC: kdepim-bugs@kde.org, vkra...@kde.org Assignee: er...@kde.org Summary: Crash on checking IMAP mail Classification: Unclassified OS: Linux Reporter: jos...@joshuakugler.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: IMAP resource Product: Akonadi Application: akonadi_imap_resource (4.9) KDE Platform Version: 4.9.2 Qt Version: 4.8.2 Operating System: Linux 3.2.0-32-generic x86_64 Distribution: Ubuntu 12.04.1 LTS -- Information about the crash: I was checking mail on an Exchange 2010 server, and did not see the accept certificate dialog right away (it popped up in the background. After clicking accept, IMAP crashed. -- Backtrace: Application: Intel of type IMAP E-Mail Server (akonadi_imap_resource), signal: Bus error Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f1050354780 (LWP 6796))] Thread 4 (Thread 0x7f103c8be700 (LWP 16448)): #0 0x7f104b34f05d in __pthread_mutex_unlock_usercnt (mutex=optimized out, decr=optimized out) at pthread_mutex_unlock.c:52 #1 __pthread_mutex_unlock (mutex=0x7f102c009d90) at pthread_mutex_unlock.c:290 #2 0x7f104a86b5d1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f104a83002a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f104a830164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f104f767906 in QEventDispatcherGlib::processEvents (this=0x7f102c0304d0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f104f736e42 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f104f737097 in QEventLoop::exec (this=0x7f103c8bdde0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f104f636057 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #9 0x7f104e36ac39 in KIMAP::SessionThread::run (this=0x1e50730) at ../../kimap/sessionthread.cpp:181 #10 0x7f104f63907b in QThreadPrivate::start (arg=0x1e50730) at thread/qthread_unix.cpp:307 #11 0x7f104b34be9a in start_thread (arg=0x7f103c8be700) at pthread_create.c:308 #12 0x7f104bcf0cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #13 0x in ?? () Thread 3 (Thread 0x7f1036630700 (LWP 31733)): #0 0x7f104b34f05d in __pthread_mutex_unlock_usercnt (mutex=optimized out, decr=optimized out) at pthread_mutex_unlock.c:52 #1 __pthread_mutex_unlock (mutex=0x7f103800e100) at pthread_mutex_unlock.c:290 #2 0x7f104a86b5d1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f104a82f83b in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f104a82ff5b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f104a830164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f104f767906 in QEventDispatcherGlib::processEvents (this=0x7f1038011ae0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #7 0x7f104f736e42 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #8 0x7f104f737097 in QEventLoop::exec (this=0x7f103662fdd0, flags=...) at kernel/qeventloop.cpp:204 #9 0x7f104f636057 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #10 0x7f104f716b4f in QInotifyFileSystemWatcherEngine::run (this=0x20d0670) at io/qfilesystemwatcher_inotify.cpp:248 #11 0x7f104f63907b in QThreadPrivate::start (arg=0x20d0670) at thread/qthread_unix.cpp:307 #12 0x7f104b34be9a in start_thread (arg=0x7f1036630700) at pthread_create.c:308 #13 0x7f104bcf0cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #14 0x in ?? () Thread 2 (Thread 0x7f102bcab700 (LWP 31797)): #0 0x7f104bce5303 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f104a830036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f104a830164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f104f767906 in QEventDispatcherGlib::processEvents (this=0x7f101c00bc30, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f104f736e42 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f104f737097 in QEventLoop::exec (this=0x7f102bcaade0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f104f636057 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f104e36ac39 in KIMAP::SessionThread::run (this=0x1d31130) at ../../kimap/sessionthread.cpp:181 #8 0x7f104f63907b in QThreadPrivate::start (arg=0x1d31130) at thread/qthread_unix.cpp:307 #9 0x7f104b34be9a in start_thread
[Bug 290903] stream of notifications stating that mail account: There is currently no session to the IMAP server available after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=290903 Joshua J. Kugler jos...@joshuakugler.com changed: What|Removed |Added CC||jos...@joshuakugler.com --- Comment #9 from Joshua J. Kugler jos...@joshuakugler.com --- Also happening in KDE 4.9.1. Not only after resume, but in this case it's the network link going down, trying to connect to the IMAP server, then the network link goes back up, and it tries again, and gets the stream of messages. -- 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 306954] New: Sometimes get could not move message when trying to delete messages.
https://bugs.kde.org/show_bug.cgi?id=306954 Bug ID: 306954 Severity: normal Version: 4.9.1 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Sometimes get could not move message when trying to delete messages. Classification: Unclassified OS: Linux Reporter: jos...@joshuakugler.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: commands and actions Product: kmail2 Sometimes when deleting a message from a folder, the notifier will tell me something like: Local Folders: Could not move message '1347770754.R673.hosanna'. and it leaves that message in the folder. Trying to delete again gives me the same message. I have hit shift-delete to delete the message, so it's not transferred to the trash. This also can happen when trying to filter messages, but I suspect it relates to not being able to delete the source message. -- 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 306954] Sometimes get could not move message when trying to delete messages.
https://bugs.kde.org/show_bug.cgi?id=306954 Joshua J. Kugler jos...@joshuakugler.com changed: What|Removed |Added CC||jos...@joshuakugler.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 304866] New: filter agent crashes when trying to filter messages
https://bugs.kde.org/show_bug.cgi?id=304866 Bug ID: 304866 Severity: crash Version: 4.9 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: filter agent crashes when trying to filter messages Classification: Unclassified OS: Linux Reporter: jos...@joshuakugler.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: Mail Filter Agent Product: Akonadi Application: akonadi_mailfilter_agent (4.9) KDE Platform Version: 4.9.00 Qt Version: 4.8.1 Operating System: Linux 3.2.0-27-generic x86_64 Distribution: Ubuntu 12.04 LTS -- Information about the crash: I had selected all the messages in a folder, and selected apply all filters. It filtered a couple hundred, then crashed. I tried again, and it crashed again right away. The crash can be reproduced every time. -- Backtrace: Application: Mail Filter Agent (akonadi_mailfilter_agent), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [KCrash Handler] #6 0x7f4f002a1500 in typeinfo for KMime::Headers::BasePrivate () from /usr/lib/libkmime.so.4 #7 0x7f4f02218dff in MailCommon::FilterActionRewriteHeader::process (this=optimized out, context=...) at ../../mailcommon/filter/filteractionrewriteheader.cpp:76 #8 0x7f4f02245d1c in MailCommon::MailFilter::execActions (this=0x23c7350, context=..., stopIt=@0x7fff8a44803f: false) at ../../mailcommon/filter/mailfilter.cpp:141 #9 0x00411615 in FilterManager::process (this=0x2327f00, mailFilters=..., item=..., requestedPart=optimized out, set=FilterManager::Explicit, account=false, accountId=...) at ../../mailfilteragent/filtermanager.cpp:524 #10 0x00411d69 in FilterManager::Private::slotItemsFetchedForFilter (this=0x2336460, items=...) at ../../mailfilteragent/filtermanager.cpp:136 #11 0x7f4f006b0281 in QMetaObject::activate (sender=0x266ae30, m=optimized out, local_signal_index=optimized out, argv=0x7fff8a4483c0) at kernel/qobject.cpp:3547 #12 0x7f4f00d68522 in Akonadi::ItemFetchJob::itemsReceived (this=optimized out, _t1=...) at ./itemfetchjob.moc:106 #13 0x7f4f00d695dc in timeout (this=0x25df580) at ../../akonadi/itemfetchjob.cpp:71 #14 Akonadi::ItemFetchJob::qt_static_metacall (_o=optimized out, _c=optimized out, _id=optimized out, _a=optimized out) at ./itemfetchjob.moc:57 #15 0x7f4f006b0281 in QMetaObject::activate (sender=0x25d4c40, m=optimized out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3547 #16 0x7f4f006b5179 in QObject::event (this=0x25d4c40, e=optimized out) at kernel/qobject.cpp:1157 #17 0x7f4efee44894 in notify_helper (e=0x7fff8a448bc0, receiver=0x25d4c40, this=0x22aef50) at kernel/qapplication.cpp:4559 #18 QApplicationPrivate::notify_helper (this=0x22aef50, receiver=0x25d4c40, e=0x7fff8a448bc0) at kernel/qapplication.cpp:4531 #19 0x7f4efee49713 in QApplication::notify (this=0x7fff8a448ea0, receiver=0x25d4c40, e=0x7fff8a448bc0) at kernel/qapplication.cpp:4420 #20 0x7f4f017ad456 in KApplication::notify (this=0x7fff8a448ea0, receiver=0x25d4c40, event=0x7fff8a448bc0) at ../../kdeui/kernel/kapplication.cpp:311 #21 0x7f4f0069be9c in QCoreApplication::notifyInternal (this=0x7fff8a448ea0, receiver=0x25d4c40, event=0x7fff8a448bc0) at kernel/qcoreapplication.cpp:876 #22 0x7f4f006cd1f2 in sendEvent (event=0x7fff8a448bc0, receiver=optimized out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #23 QTimerInfoList::activateTimers (this=0x22b0720) at kernel/qeventdispatcher_unix.cpp:611 #24 0x7f4f006cac0d in timerSourceDispatch (source=optimized out) at kernel/qeventdispatcher_glib.cpp:186 #25 timerSourceDispatch (source=optimized out) at kernel/qeventdispatcher_glib.cpp:180 #26 0x7f4ef81c9d53 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7f4ef81ca0a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7f4ef81ca164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7f4f006cb3bf in QEventDispatcherGlib::processEvents (this=0x225ead0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #30 0x7f4efeeecd5e in QGuiEventDispatcherGlib::processEvents (this=optimized out, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #31 0x7f4f0069ac82 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #32 0x7f4f0069aed7 in QEventLoop::exec (this=0x7fff8a448e20, flags=...) at kernel/qeventloop.cpp:204 #33 0x7f4f0069ff67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148 #34 0x7f4f00cbeb76 in Akonadi::AgentBase::init (r=0x24bed80) at ../../akonadi/agentbase.cpp:550 #35 0x004160a6 in Akonadi::AgentBase::initMailFilterAgent (argc=optimized out, argv=optimized out) at /usr/include/akonadi/agentbase.h:342 #36 0x7f4efe3c776d in __libc_start_main (main=0x40b290 main(int,
[Bug 304866] filter agent crashes when trying to filter messages
https://bugs.kde.org/show_bug.cgi?id=304866 --- Comment #1 from Joshua J. Kugler jos...@joshuakugler.com --- Addendum: after the filter agent crashes, mail will no longer filter, and I have to restart Akonadi to get filtering working again. -- 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 304866] filter agent crashes when trying to filter messages
https://bugs.kde.org/show_bug.cgi?id=304866 --- Comment #2 from Joshua J. Kugler jos...@joshuakugler.com --- Another addendum. It seems if I get mail filter running, I can filter one message at a time. But if I select too many to filter, and then hit 'Ctrl-J' it dies. -- 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 304866] filter agent crashes when trying to filter messages
https://bugs.kde.org/show_bug.cgi?id=304866 Joshua J. Kugler jos...@joshuakugler.com changed: What|Removed |Added CC||jos...@joshuakugler.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 304866] filter agent crashes when trying to filter messages
https://bugs.kde.org/show_bug.cgi?id=304866 --- Comment #4 from Joshua J. Kugler jos...@joshuakugler.com --- Created attachment 73070 -- https://bugs.kde.org/attachment.cgi?id=73070action=edit New crash information added by DrKonqi akonadi_mailfilter_agent (4.9) on KDE Platform 4.9.00 using Qt 4.8.1 I was trying to filter by hand (i.e. Ctrl-J) and selected a block of messages (eight) and hit Ctrl-J. and the mail filter crashed. -- Backtrace (Reduced): #6 0x7fd2b6250500 in typeinfo for KMime::Headers::BasePrivate () from /usr/lib/libkmime.so.4 #7 0x7fd2b81c7dff in MailCommon::FilterActionRewriteHeader::process (this=optimized out, context=...) at ../../mailcommon/filter/filteractionrewriteheader.cpp:76 #8 0x7fd2b81f4d1c in MailCommon::MailFilter::execActions (this=0x13aa4b0, context=..., stopIt=@0x7fff727bdbdf: false) at ../../mailcommon/filter/mailfilter.cpp:141 #9 0x00411615 in FilterManager::process (this=0x1301590, mailFilters=..., item=..., requestedPart=optimized out, set=FilterManager::Explicit, account=false, accountId=...) at ../../mailfilteragent/filtermanager.cpp:524 #10 0x00411d69 in FilterManager::Private::slotItemsFetchedForFilter (this=0x12fcbd0, items=...) at ../../mailfilteragent/filtermanager.cpp:136 -- 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 304866] filter agent crashes when trying to filter messages
https://bugs.kde.org/show_bug.cgi?id=304866 Joshua J. Kugler jos...@joshuakugler.com changed: What|Removed |Added Severity|crash |critical --- Comment #5 from Joshua J. Kugler jos...@joshuakugler.com --- Changing to critical importance because it renders filtering unusable. With over 100 filters, I heavily rely on filtering to work properly. -- 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 288025] New: KMail crashed when I tried to reply to a message.
https://bugs.kde.org/show_bug.cgi?id=288025 Summary: KMail crashed when I tried to reply to a message. Product: kmail2 Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: jos...@joshuakugler.com Application: kmail (1.13.6) KDE Platform Version: 4.7.2 (4.7.2) Qt Version: 4.7.2 Operating System: Linux 2.6.38-13-generic i686 Distribution: Ubuntu 11.04 -- Information about the crash: I was viewing some messages. I hit delete, then hit left-arrow (previous message), and then hit 'r' for reply. KMail crashed when I hit r. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0xb78b19b0 (LWP 18127))] Thread 3 (Thread 0xb6171b70 (LWP 18129)): #0 0x06164610 in __i686.get_pc_thunk.bx () from /lib/i386-linux-gnu/libpthread.so.0 #1 0x06168337 in pthread_mutex_lock () from /lib/i386-linux-gnu/libpthread.so.0 #2 0x05b31616 in pthread_mutex_lock () from /lib/i386-linux-gnu/libc.so.6 #3 0x08cd5080 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x08cd592b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0x03c61304 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 #6 0x08cfe2df in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0x06165e99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #8 0x05b2373e in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 2 (Thread 0xb39e0b70 (LWP 18130)): #0 0x00110416 in __kernel_vsyscall () #1 0x05b14f76 in poll () from /lib/i386-linux-gnu/libc.so.6 #2 0x08ce584b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x08cd51af in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x08cd5524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0x02810577 in QEventDispatcherGlib::processEvents (this=0x99576b0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x027e2289 in QEventLoop::processEvents (this=0xb39e0220, flags=...) at kernel/qeventloop.cpp:149 #7 0x027e2522 in QEventLoop::exec (this=0xb39e0220, flags=...) at kernel/qeventloop.cpp:201 #8 0x026ec2a0 in QThread::exec (this=0x9291d00) at thread/qthread.cpp:492 #9 0x027c3fdb in QInotifyFileSystemWatcherEngine::run (this=0x9291d00) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x026eeda2 in QThreadPrivate::start (arg=0x9291d00) at thread/qthread_unix.cpp:320 #11 0x06165e99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #12 0x05b2373e in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 1 (Thread 0xb78b19b0 (LWP 18127)): [KCrash Handler] #7 0x00a9a82e in KMCommand::slotStart (this=0xc765b50) at ../../kmail/kmcommands.cpp:265 #8 0x00aa1f2b in KMCommand::qt_metacall (this=0xc765b50, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x9515938) at ./kmcommands.moc:92 #9 0x00aa27c2 in KMReplyToCommand::qt_metacall (this=0xc765b50, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0x9515938) at ./kmcommands.moc:946 #10 0x027e96ba in QMetaObject::metacall (object=0xc765b50, cl=QMetaObject::InvokeMetaMethod, idx=8, argv=0x9515938) at kernel/qmetaobject.cpp:237 #11 0x027f3e16 in QMetaCallEvent::placeMetaCall (this=0xd7fe380, object=0xc765b50) at kernel/qobject.cpp:535 #12 0x027f83b7 in QObject::event (this=0xc765b50, e=0xd7fe380) at kernel/qobject.cpp:1226 #13 0x00fd1d24 in QApplicationPrivate::notify_helper (this=0x9121d90, receiver=0xc765b50, e=0xd7fe380) at kernel/qapplication.cpp:4462 #14 0x00fd68ce in QApplication::notify (this=0xbfa5910c, receiver=0xc765b50, e=0xd7fe380) at kernel/qapplication.cpp:3862 #15 0x005b5b9a in KApplication::notify (this=0xbfa5910c, receiver=0xc765b50, event=0xd7fe380) at ../../kdeui/kernel/kapplication.cpp:311 #16 0x027e30bb in QCoreApplication::notifyInternal (this=0xbfa5910c, receiver=0xc765b50, event=0xd7fe380) at kernel/qcoreapplication.cpp:731 #17 0x027e6c79 in sendEvent (receiver=0x0, event_type=0, data=0x90bbf28) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #18 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x90bbf28) at kernel/qcoreapplication.cpp:1372 #19 0x027e6e0d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1265 #20 0x028103c4 in sendPostedEvents (s=0x910af40) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220 #21 postEventSourceDispatch (s=0x910af40) at kernel/qeventdispatcher_glib.cpp:277 #22 0x08cd4aa8 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #23 0x08cd5270 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #24 0x08cd5524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #25 0x0281053c in QEventDispatcherGlib::processEvents (this=0x90bba80, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #26 0x010881e5 in
[Bug 287953] New: KMail crashed when trying to send an e-mail
https://bugs.kde.org/show_bug.cgi?id=287953 Summary: KMail crashed when trying to send an e-mail Product: kmail2 Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: jos...@joshuakugler.com Application: kmail (1.13.6) KDE Platform Version: 4.7.2 (4.7.2) Qt Version: 4.7.2 Operating System: Linux 2.6.38-13-generic i686 Distribution: Ubuntu 11.04 -- Information about the crash: I had replied to an e-mail, and when I hit ctrl-enter to send the e-mail, the entire KMail application crashed. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0xb77189b0 (LWP 1919))] Thread 4 (Thread 0xb610eb70 (LWP 1932)): #0 0x00d58416 in __kernel_vsyscall () #1 0x0091af76 in poll () from /lib/i386-linux-gnu/libc.so.6 #2 0x0535e84b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x0534e1af in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x0534e92b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0x03c28304 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 #6 0x053772df in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0x082e7e99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #8 0x0092973e in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 3 (Thread 0xb4cdcb70 (LWP 2123)): #0 0x02b8ad41 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0x00aa0dd8 in do_gettime () at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0x00b6d4f2 in updateCurrentTime (this=0xb3500524, tm=...) at kernel/qeventdispatcher_unix.cpp:339 #4 QTimerInfoList::timerWait (this=0xb3500524, tm=...) at kernel/qeventdispatcher_unix.cpp:442 #5 0x00b6bd32 in timerSourcePrepareHelper (src=value optimized out, timeout=0xb4cdc06c) at kernel/qeventdispatcher_glib.cpp:136 #6 0x00b6bdcd in timerSourcePrepare (source=0xb35004f0, timeout=value optimized out) at kernel/qeventdispatcher_glib.cpp:169 #7 0x0534cfd4 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0x0534de63 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0x0534e524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #10 0x00b6c577 in QEventDispatcherGlib::processEvents (this=0xa09ace8, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #11 0x00b3e289 in QEventLoop::processEvents (this=0xb4cdc220, flags=...) at kernel/qeventloop.cpp:149 #12 0x00b3e522 in QEventLoop::exec (this=0xb4cdc220, flags=...) at kernel/qeventloop.cpp:201 #13 0x00a482a0 in QThread::exec (this=0xa369998) at thread/qthread.cpp:492 #14 0x00b1ffdb in QInotifyFileSystemWatcherEngine::run (this=0xa369998) at io/qfilesystemwatcher_inotify.cpp:248 #15 0x00a4ada2 in QThreadPrivate::start (arg=0xa369998) at thread/qthread_unix.cpp:320 #16 0x082e7e99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #17 0x0092973e in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 2 (Thread 0xb6a9db70 (LWP 20131)): #0 0x02b8ad41 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0x00aa0dd8 in do_gettime () at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0x00b6d4f2 in updateCurrentTime (this=0xb35009cc, tm=...) at kernel/qeventdispatcher_unix.cpp:339 #4 QTimerInfoList::timerWait (this=0xb35009cc, tm=...) at kernel/qeventdispatcher_unix.cpp:442 #5 0x00b6bd32 in timerSourcePrepareHelper (src=value optimized out, timeout=0xb6a9d06c) at kernel/qeventdispatcher_glib.cpp:136 #6 0x00b6bdcd in timerSourcePrepare (source=0xb3500998, timeout=value optimized out) at kernel/qeventdispatcher_glib.cpp:169 #7 0x0534cfd4 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0x0534de63 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0x0534e524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #10 0x00b6c577 in QEventDispatcherGlib::processEvents (this=0xb35047c8, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #11 0x00b3e289 in QEventLoop::processEvents (this=0xb6a9d220, flags=...) at kernel/qeventloop.cpp:149 #12 0x00b3e522 in QEventLoop::exec (this=0xb6a9d220, flags=...) at kernel/qeventloop.cpp:201 #13 0x00a482a0 in QThread::exec (this=0xc45ec20) at thread/qthread.cpp:492 #14 0x00b1ffdb in QInotifyFileSystemWatcherEngine::run (this=0xc45ec20) at io/qfilesystemwatcher_inotify.cpp:248 #15 0x00a4ada2 in QThreadPrivate::start (arg=0xc45ec20) at thread/qthread_unix.cpp:320 #16 0x082e7e99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #17 0x0092973e in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 1 (Thread 0xb77189b0 (LWP 1919)): [KCrash Handler] #7 0x0112b82e in KMCommand::slotStart (this=0xcd16b50) at ../../kmail/kmcommands.cpp:265 #8 0x01132f2b in KMCommand::qt_metacall
[Bug 287953] KMail crashed when trying to send an e-mail
https://bugs.kde.org/show_bug.cgi?id=287953 --- Comment #1 from Joshua J. Kugler joshua joshuakugler com 2011-12-01 03:00:25 --- When I restarted KMail, the message was in the outbox, unsent. It sent OK. -- 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 282575] New: KJS crash (and then Akregator crashes)
https://bugs.kde.org/show_bug.cgi?id=282575 Summary: KJS crash (and then Akregator crashes) Product: akregator Version: 1.6.6 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: jos...@joshuakugler.com Application: akregator (1.6.6) KDE Platform Version: 4.7.00 (4.7.0) Qt Version: 4.7.2 Operating System: Linux 2.6.38-11-generic i686 Distribution: Ubuntu 11.04 -- Information about the crash: An article was loading in Akregator and then Akregator crashed. The traceback indicated it was something to do with KJS. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault [Current thread is 1 (Thread 0xb7761730 (LWP 1865))] Thread 2 (Thread 0xb579fb70 (LWP 2036)): #0 0x0206bd41 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0x044e5dd8 in do_gettime () at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0x045b24f2 in updateCurrentTime (this=0x92ebb04, tm=...) at kernel/qeventdispatcher_unix.cpp:339 #4 QTimerInfoList::timerWait (this=0x92ebb04, tm=...) at kernel/qeventdispatcher_unix.cpp:442 #5 0x045b0d32 in timerSourcePrepareHelper (src=value optimized out, timeout=0xb579f0bc) at kernel/qeventdispatcher_glib.cpp:136 #6 0x045b0dcd in timerSourcePrepare (source=0x92ebad0, timeout=value optimized out) at kernel/qeventdispatcher_glib.cpp:169 #7 0x04ccdfd4 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0x04ccee63 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0x04ccf524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #10 0x045b1577 in QEventDispatcherGlib::processEvents (this=0x932d7d8, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #11 0x04583289 in QEventLoop::processEvents (this=0xb579f270, flags=...) at kernel/qeventloop.cpp:149 #12 0x04583522 in QEventLoop::exec (this=0xb579f270, flags=...) at kernel/qeventloop.cpp:201 #13 0x0448d2a0 in QThread::exec (this=0x9fa1d38) at thread/qthread.cpp:492 #14 0x04564fdb in QInotifyFileSystemWatcherEngine::run (this=0x9fa1d38) at io/qfilesystemwatcher_inotify.cpp:248 #15 0x0448fda2 in QThreadPrivate::start (arg=0x9fa1d38) at thread/qthread_unix.cpp:320 #16 0x08364e99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #17 0x00c5173e in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 1 (Thread 0xb7761730 (LWP 1865)): [KCrash Handler] #7 0xb67eb410 in type (exec=0x12da2b20, ctx=0x12da2b10, in=0xb3ffa980, path=...) at ../../kjs/value.h:452 #8 KJS::cloneInternal (exec=0x12da2b20, ctx=0x12da2b10, in=0xb3ffa980, path=...) at ../../khtml/ecma/kjs_data.cpp:37 #9 0xb67eb824 in KJS::encapsulateMessageEventData (exec=0x12da2b20, ctx=0x12da2b10, data=0xb3ffa980) at ../../khtml/ecma/kjs_data.cpp:117 #10 0xb67eba1e in KJS::DelayedPostMessage::execute (this=0xbc6ba30, w=0xb468) at ../../khtml/ecma/kjs_data.cpp:169 #11 0xb679bbdb in KJS::Window::afterScriptExecution (this=0xb468) at ../../khtml/ecma/kjs_window.cpp:1327 #12 0xb67c5c69 in KJS::JSEventListener::handleEvent (this=0xae8e680, evt=...) at ../../khtml/ecma/kjs_events.cpp:121 #13 0xb65db46f in DOM::EventTargetImpl::handleLocalEvents (this=0xa7106d0, evt=0xde93298, useCapture=false) at ../../khtml/xml/dom2_eventsimpl.cpp:62 #14 0xb65b34b7 in DOM::NodeImpl::dispatchGenericEvent (this=0xa7106d0, evt=0xde93298) at ../../khtml/xml/dom_nodeimpl.cpp:469 #15 0xb65b3766 in DOM::NodeImpl::dispatchEvent (this=0xa7106d0, evt=0xde93298, exceptioncode=@0xbf9e7dac, tempEvent=true) at ../../khtml/xml/dom_nodeimpl.cpp:401 #16 0xb65b4fad in DOM::NodeImpl::dispatchHTMLEvent (this=0xa7106d0, _id=16, canBubbleArg=false, cancelableArg=false) at ../../khtml/xml/dom_nodeimpl.cpp:520 #17 0xb6635aa8 in DOM::HTMLPartContainerElementImpl::slotEmitLoadEvent (this=0xa7106c8) at ../../khtml/html/html_objectimpl.cpp:133 #18 0xb65b3674 in DOM::NodeImpl::dispatchWindowEvent (this=0xba23b0c, evt=0x11ac22a8) at ../../khtml/xml/dom_nodeimpl.cpp:548 #19 0xb66128c5 in DOM::HTMLDocumentImpl::close (this=0xba23b00) at ../../khtml/html/html_documentimpl.cpp:237 #20 0xb6516712 in KHTMLPart::checkEmitLoadEvent (this=0xc9b47e8) at ../../khtml/khtml_part.cpp:2483 #21 0xb65286de in KHTMLPart::slotFinishedParsing (this=0xc9b47e8) at ../../khtml/khtml_part.cpp:2207 #22 0xb6547750 in KHTMLPart::qt_metacall (this=0xc9b47e8, _c=QMetaObject::InvokeMetaMethod, _id=22, _a=0xbf9e7fcc) at ./khtml_part.moc:281 #23 0x0458a6ba in QMetaObject::metacall (object=0xc9b47e8, cl=QMetaObject::InvokeMetaMethod, idx=37, argv=0xbf9e7fcc) at kernel/qmetaobject.cpp:237 #24 0x0459a4ff in QMetaObject::activate (sender=0xba23b00, m=0xb6a7e6ec, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3287 #25 0xb65a0557 in DOM::DocumentImpl::finishedParsing (this=0xba23b00) at ./dom_docimpl.moc:85 #26 0xb65a05b1 in
[Bug 254750] Crash when MDN request acknowledged [KMMessage::headerField, KMMessage::identityUoid, KMMessage::createMDN]
https://bugs.kde.org/show_bug.cgi?id=254750 Joshua J. Kugler jos...@joshuakugler.com changed: What|Removed |Added CC||jos...@joshuakugler.com -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 254750] Crash when MDN request acknowledged [KMMessage::headerField, KMMessage::identityUoid, KMMessage::createMDN]
https://bugs.kde.org/show_bug.cgi?id=254750 --- Comment #4 from Joshua J. Kugler joshua joshuakugler com 2011-09-19 22:25:07 --- Created an attachment (id=63785) -- (http://bugs.kde.org/attachment.cgi?id=63785) New crash information added by DrKonqi kmail (1.13.6) on KDE Platform 4.7.00 (4.7.0) using Qt 4.7.2 I received an e-mail that requested a delivery notification. I clicked ignore and KMail crashed. -- Backtrace (Reduced): #8 0x00f75810 in KMMessage::createMDN (this=0xb13c4f0, a=KMime::MDN::ManualAction, d=KMime::MDN::Displayed, allowGUI=true, m=...) at ../../kmail/kmmessage.cpp:1141 #9 0x0103e9bf in KMReaderWin::slotTouchMessage (this=0x8a8e8d8) at ../../kmail/kmreaderwin.cpp:1889 #10 0x01048003 in KMReaderWin::qt_metacall (this=0x8a8e8d8, _c=QMetaObject::InvokeMetaMethod, _id=37, _a=0xbfe16a6c) at ./kmreaderwin.moc:210 [...] #13 0x005392f7 in QTimer::timeout (this=0x8a8e960) at .moc/release-shared/moc_qtimer.cpp:134 #14 0x004f23ee in QTimer::timerEvent (this=0x8a8e960, e=0xbfe16f8c) at kernel/qtimer.cpp:271 -- 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 280257] Akregator crashes after startup
https://bugs.kde.org/show_bug.cgi?id=280257 --- Comment #4 from Joshua J. Kugler joshua joshuakugler com 2011-08-28 20:23:14 --- Could you please provide an explanation? This bug has been resolved as a duplicate of a bug that was closed over three years ago. If it is still appearing, how can it be a duplicate of a closed bug? -- 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 280305] Akregator crashed trying to read an article
https://bugs.kde.org/show_bug.cgi?id=280305 --- Comment #2 from Joshua J. Kugler joshua joshuakugler com 2011-08-28 20:23:16 --- Could you please provide an explanation? This bug has been resolved as a duplicate of a bug that was closed over three years ago. If it is still appearing, how can it be a duplicate of a closed bug? -- 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 280305] Akregator crashed trying to read an article
https://bugs.kde.org/show_bug.cgi?id=280305 --- Comment #4 from Joshua J. Kugler joshua joshuakugler com 2011-08-28 21:09:02 --- (In reply to comment #3) hm? bug 163573 is still opened Sigh...chalk one up to reading too fast (or not reading). I saw resolved on the bug marked duplicate, and didn't read the NEW status on 163573. Sorry about that. A little more context on my report(s): after restarting Akregator a few times, it finally stopped crashing, and I've been using it for a while now with no new crashes. When it first started crashing, it was reading files from an old version of Akregator (KDE 3.5.x). Maybe once it upgraded everything, it was all OK. -- 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 280257] New: Akregator crashes after startup
https://bugs.kde.org/show_bug.cgi?id=280257 Summary: Akregator crashes after startup Product: akregator Version: 1.6.6 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: jos...@joshuakugler.com Application: akregator (1.6.6) KDE Platform Version: 4.7.00 (4.7.0) Qt Version: 4.7.2 Operating System: Linux 2.6.38-10-generic i686 Distribution: Ubuntu 11.04 -- Information about the crash: - What I was doing when the application crashed: The application had started, and was updating the feeds. I was adjusting the column widths (name, unread, total) when the crash happened. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault [Current thread is 1 (Thread 0xb782b730 (LWP 23945))] Thread 2 (Thread 0xb4a1ab70 (LWP 23947)): #0 0x00b95d41 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0x01a02dd8 in do_gettime () at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0x01acf4f2 in updateCurrentTime (this=0x8b7a8cc, tm=...) at kernel/qeventdispatcher_unix.cpp:339 #4 QTimerInfoList::timerWait (this=0x8b7a8cc, tm=...) at kernel/qeventdispatcher_unix.cpp:442 #5 0x01acdd32 in timerSourcePrepareHelper (src=value optimized out, timeout=0xb4a1a0bc) at kernel/qeventdispatcher_glib.cpp:136 #6 0x01acddcd in timerSourcePrepare (source=0x8b7a898, timeout=value optimized out) at kernel/qeventdispatcher_glib.cpp:169 #7 0x0521efd4 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0x0521fe63 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0x05220524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #10 0x01ace577 in QEventDispatcherGlib::processEvents (this=0x8a868c0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #11 0x01aa0289 in QEventLoop::processEvents (this=0xb4a1a270, flags=...) at kernel/qeventloop.cpp:149 #12 0x01aa0522 in QEventLoop::exec (this=0xb4a1a270, flags=...) at kernel/qeventloop.cpp:201 #13 0x019aa2a0 in QThread::exec (this=0x8aa7b80) at thread/qthread.cpp:492 #14 0x01a81fdb in QInotifyFileSystemWatcherEngine::run (this=0x8aa7b80) at io/qfilesystemwatcher_inotify.cpp:248 #15 0x019acda2 in QThreadPrivate::start (arg=0x8aa7b80) at thread/qthread_unix.cpp:320 #16 0x00dede99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #17 0x03fb373e in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 1 (Thread 0xb782b730 (LWP 23945)): [KCrash Handler] #7 0x07accd83 in c4_Handler::GetBytes (this=0xce37598, index_=1930, buf_=..., copySmall_=false) at ../../../../akregator/plugins/mk4storage/metakit/src/handler.cpp:53 #8 0x07ad954b in c4_Sequence::Get (this=0x9a1eef0, index_=1930, propId_=-31304, buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:319 #9 0x07ad6ceb in GetData (this=0x9a2078c, row_=1930, col_=21, buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:421 #10 c4_View::GetItem (this=0x9a2078c, row_=1930, col_=21, buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/view.cpp:225 #11 0x07ad1125 in c4_HashViewer::GetItem (this=0x9a20788, row_=1930, col_=21, buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/remap.cpp:352 #12 0x07ac54ba in DoGet (this=0x9a10df0, index_=1930, length_=@0xbfc3c50c) at ../../../../akregator/plugins/mk4storage/metakit/src/custom.cpp:148 #13 c4_CustomHandler::Get (this=0x9a10df0, index_=1930, length_=@0xbfc3c50c) at ../../../../akregator/plugins/mk4storage/metakit/src/custom.cpp:58 #14 0x07accd86 in c4_Handler::GetBytes (this=0x9a10df0, index_=1930, buf_=..., copySmall_=false) at ../../../../akregator/plugins/mk4storage/metakit/src/handler.cpp:53 #15 0x07ad9c40 in c4_Sequence::SetAt (this=0xca1b2f0, index_=0, newElem_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:98 #16 0x07ad7cc9 in c4_Row::operator= (this=0xbfc3c648, rowRef_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/view.cpp:1008 #17 0x07ade230 in Akregator::Backend::FeedStorageMK4Impl::setStatus (this=0x9917cc0, guid=..., status=0) at ../../../../akregator/plugins/mk4storage/feedstoragemk4impl.cpp:394 #18 0x032aeeb1 in Akregator::Article::setStatus (this=0x8a73418, stat=0) at ../../../akregator/src/article.cpp:367 #19 0x032bef48 in Akregator::Feed::fetch (this=0x9a1fde8, followDiscovery=false) at ../../../akregator/src/feed.cpp:586 #20 0x032d053d in Akregator::FetchQueue::fetchNextFeed (this=0x87c1500) at ../../../akregator/src/fetchqueue.cpp:91 #21 0x032d05d2 in Akregator::FetchQueue::feedDone (this=0x87c1500, f=0xc7b4e78) at ../../../akregator/src/fetchqueue.cpp:126 #22 0x032d0688 in Akregator::FetchQueue::slotFetchError (this=0x87c1500, f=0xc7b4e78) at ../../../akregator/src/fetchqueue.cpp:105 #23 0x032d098f in Akregator::FetchQueue::qt_metacall
[Bug 280257] Akregator crashes after startup
https://bugs.kde.org/show_bug.cgi?id=280257 Joshua J. Kugler jos...@joshuakugler.com changed: What|Removed |Added CC||jos...@joshuakugler.com -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 280257] Akregator crashes after startup
https://bugs.kde.org/show_bug.cgi?id=280257 --- Comment #1 from Joshua J. Kugler joshua joshuakugler com 2011-08-17 10:15:05 --- Created an attachment (id=62892) -- (http://bugs.kde.org/attachment.cgi?id=62892) New crash information added by DrKonqi akregator (1.6.6) on KDE Platform 4.7.00 (4.7.0) using Qt 4.7.2 Same as last time. I had just started Akregator (with existing feeds: archive used to belong to a KDE 3.5 version of akregator), and it crashed while updating. -- Backtrace (Reduced): #8 0x098ca9e8 in c4_String::c4_String (this=0xbfa55dcc, p=0x80808080 Address 0x80808080 out of bounds) at ../../../../akregator/plugins/mk4storage/metakit/src/string.cpp:129 #9 0x098cd4a9 in c4_Property::c4_Property (this=0xbfa55e1c, type_=73 'I', name_=0x80808080 Address 0x80808080 out of bounds) at ../../../../akregator/plugins/mk4storage/metakit/src/view.cpp:1100 #10 0x098c156a in c4_IntProp (prop_=..., seq_=...) at ../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:524 #11 f4_CreateFormat (prop_=..., seq_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:1228 #12 0x098c1c04 in c4_HandlerSeq::CreateHandler (this=0xa26ed00, prop_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/handler.cpp:131 --- Comment #2 from Joshua J. Kugler joshua joshuakugler com 2011-08-17 10:15:05 --- Created an attachment (id=62893) -- (http://bugs.kde.org/attachment.cgi?id=62893) New crash information added by DrKonqi akregator (1.6.6) on KDE Platform 4.7.00 (4.7.0) using Qt 4.7.2 Same as last time. I had just started Akregator (with existing feeds: archive used to belong to a KDE 3.5 version of akregator), and it crashed while updating. -- Backtrace (Reduced): #8 0x098ca9e8 in c4_String::c4_String (this=0xbfa55dcc, p=0x80808080 Address 0x80808080 out of bounds) at ../../../../akregator/plugins/mk4storage/metakit/src/string.cpp:129 #9 0x098cd4a9 in c4_Property::c4_Property (this=0xbfa55e1c, type_=73 'I', name_=0x80808080 Address 0x80808080 out of bounds) at ../../../../akregator/plugins/mk4storage/metakit/src/view.cpp:1100 #10 0x098c156a in c4_IntProp (prop_=..., seq_=...) at ../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:524 #11 f4_CreateFormat (prop_=..., seq_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:1228 #12 0x098c1c04 in c4_HandlerSeq::CreateHandler (this=0xa26ed00, prop_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/handler.cpp:131 -- 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 280257] Akregator crashes after startup
https://bugs.kde.org/show_bug.cgi?id=280257 --- Comment #1 from Joshua J. Kugler joshua joshuakugler com 2011-08-17 10:15:05 --- Created an attachment (id=62892) -- (http://bugs.kde.org/attachment.cgi?id=62892) New crash information added by DrKonqi akregator (1.6.6) on KDE Platform 4.7.00 (4.7.0) using Qt 4.7.2 Same as last time. I had just started Akregator (with existing feeds: archive used to belong to a KDE 3.5 version of akregator), and it crashed while updating. -- Backtrace (Reduced): #8 0x098ca9e8 in c4_String::c4_String (this=0xbfa55dcc, p=0x80808080 Address 0x80808080 out of bounds) at ../../../../akregator/plugins/mk4storage/metakit/src/string.cpp:129 #9 0x098cd4a9 in c4_Property::c4_Property (this=0xbfa55e1c, type_=73 'I', name_=0x80808080 Address 0x80808080 out of bounds) at ../../../../akregator/plugins/mk4storage/metakit/src/view.cpp:1100 #10 0x098c156a in c4_IntProp (prop_=..., seq_=...) at ../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:524 #11 f4_CreateFormat (prop_=..., seq_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:1228 #12 0x098c1c04 in c4_HandlerSeq::CreateHandler (this=0xa26ed00, prop_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/handler.cpp:131 --- Comment #2 from Joshua J. Kugler joshua joshuakugler com 2011-08-17 10:15:05 --- Created an attachment (id=62893) -- (http://bugs.kde.org/attachment.cgi?id=62893) New crash information added by DrKonqi akregator (1.6.6) on KDE Platform 4.7.00 (4.7.0) using Qt 4.7.2 Same as last time. I had just started Akregator (with existing feeds: archive used to belong to a KDE 3.5 version of akregator), and it crashed while updating. -- Backtrace (Reduced): #8 0x098ca9e8 in c4_String::c4_String (this=0xbfa55dcc, p=0x80808080 Address 0x80808080 out of bounds) at ../../../../akregator/plugins/mk4storage/metakit/src/string.cpp:129 #9 0x098cd4a9 in c4_Property::c4_Property (this=0xbfa55e1c, type_=73 'I', name_=0x80808080 Address 0x80808080 out of bounds) at ../../../../akregator/plugins/mk4storage/metakit/src/view.cpp:1100 #10 0x098c156a in c4_IntProp (prop_=..., seq_=...) at ../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:524 #11 f4_CreateFormat (prop_=..., seq_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:1228 #12 0x098c1c04 in c4_HandlerSeq::CreateHandler (this=0xa26ed00, prop_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/handler.cpp:131 -- 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 280305] New: Akregator crashed trying to read an article
https://bugs.kde.org/show_bug.cgi?id=280305 Summary: Akregator crashed trying to read an article Product: akregator Version: 1.6.6 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: jos...@joshuakugler.com Application: akregator (1.6.6) KDE Platform Version: 4.7.00 (4.7.0) Qt Version: 4.7.2 Operating System: Linux 2.6.38-10-generic i686 Distribution: Ubuntu 11.04 -- Information about the crash: Akgregator had started, and had successfully retrieved all the feeds. I had adjusted column widths in the feed list, and then clicked on a feed, sorted by date, scrolled to the top, and clicked on an article. Akregator crashed. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault [Current thread is 1 (Thread 0xb78aa730 (LWP 30827))] Thread 2 (Thread 0xb4a9bb70 (LWP 30830)): #0 0x00b95416 in __kernel_vsyscall () #1 0x03a26f76 in poll () from /lib/i386-linux-gnu/libc.so.6 #2 0x019d384b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x019c31af in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x019c3524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0x0099c577 in QEventDispatcherGlib::processEvents (this=0x8f95430, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x0096e289 in QEventLoop::processEvents (this=0xb4a9b270, flags=...) at kernel/qeventloop.cpp:149 #7 0x0096e522 in QEventLoop::exec (this=0xb4a9b270, flags=...) at kernel/qeventloop.cpp:201 #8 0x008782a0 in QThread::exec (this=0x927e818) at thread/qthread.cpp:492 #9 0x0094ffdb in QInotifyFileSystemWatcherEngine::run (this=0x927e818) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x0087ada2 in QThreadPrivate::start (arg=0x927e818) at thread/qthread_unix.cpp:320 #11 0x00cb3e99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #12 0x03a3573e in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 1 (Thread 0xb78aa730 (LWP 30827)): [KCrash Handler] #7 0x083574d5 in c4_Property::c4_Property (this=0xbfee709c, type_=73 'I', name_=0x0) at ../../../../akregator/plugins/mk4storage/metakit/src/view.cpp:1106 #8 0x0834b56a in c4_IntProp (prop_=..., seq_=...) at ../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:524 #9 f4_CreateFormat (prop_=..., seq_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:1228 #10 0x0834bc04 in c4_HandlerSeq::CreateHandler (this=0xaee31d8, prop_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/handler.cpp:131 #11 0x08358624 in c4_Sequence::PropIndex (this=0xaee31d8, prop_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:292 #12 0x08358707 in c4_Sequence::Set (this=0xaee31d8, index_=244, prop_=..., buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:325 #13 0x08355d3a in SetData (this=0xaed6f0c, row_=244, col_=21, buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:426 #14 c4_View::SetItem (this=0xaed6f0c, row_=244, col_=21, buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/view.cpp:231 #15 0x08351472 in c4_HashViewer::SetItem (this=0xaed6f08, row_=244, col_=21, buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/remap.cpp:366 #16 0x0834347d in DoSet (this=0xaee6768, index_=244, buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/custom.cpp:154 #17 c4_CustomHandler::Set (this=0xaee6768, index_=244, buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/custom.cpp:69 #18 0x08358c74 in c4_Sequence::SetAt (this=0xaeee690, index_=244, newElem_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:104 #19 0x0835d277 in SetAt (this=0xaeba9e8, guid=..., status=8) at ../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:89 #20 Akregator::Backend::FeedStorageMK4Impl::setStatus (this=0xaeba9e8, guid=..., status=8) at ../../../../akregator/plugins/mk4storage/feedstoragemk4impl.cpp:396 #21 0x022e7eb1 in Akregator::Article::setStatus (this=0xbfee746c, stat=1) at ../../../akregator/src/article.cpp:367 #22 0x022eb711 in Akregator::ArticleModifyJob::doStart (this=0xc644530) at ../../../akregator/src/articlejobs.cpp:145 #23 0x022ebc51 in Akregator::ArticleModifyJob::qt_metacall (this=0xc644530, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0xbfee756c) at ./articlejobs.moc:180 #24 0x009756ba in QMetaObject::metacall (object=0xc644530, cl=QMetaObject::InvokeMetaMethod, idx=26, argv=0xbfee756c) at kernel/qmetaobject.cpp:237 #25 0x009854ff in QMetaObject::activate (sender=0x9f6e180, m=0xaa9188, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3287 #26 0x0098b4d7 in QSingleShotTimer::timeout (this=0x9f6e180) at .moc/release-shared/qtimer.moc:82 #27 0x0098b58c in QSingleShotTimer::timerEvent (this=0x9f6e180) at kernel/qtimer.cpp:308 #28
