[akregator] [Bug 350139] New: Akregator Crashes when open specific article
https://bugs.kde.org/show_bug.cgi?id=350139 Bug ID: 350139 Summary: Akregator Crashes when open specific article Product: akregator Version: unspecified Platform: Debian stable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: shoalcre...@gmail.com Application: akregator (4.14.1) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.16.0-4-amd64 x86_64 Distribution: Debian GNU/Linux 8.1 (jessie) -- Information about the crash: Every time I clicked on one specific article in the article list, Akregator would immediately crash. Article url: https://www.lewrockwell.com/2015/07/no_author/us-police-kill-more-in-days/ The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0a23c5d7c0 (LWP 20470))] Thread 2 (Thread 0x7f09fee1d700 (LWP 20478)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x7f0a211d4c44 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f0a211c7c7d in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x7f0a211d470f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f0a1b6400a4 in start_thread (arg=0x7f09fee1d700) at pthread_create.c:309 #5 0x7f0a206e604d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f0a23c5d7c0 (LWP 20470)): [KCrash Handler] #6 0x7f0a20635107 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #7 0x7f0a206364e8 in __GI_abort () at abort.c:89 #8 0x7f0a2062e226 in __assert_fail_base (fmt=0x7f0a20764ce8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f0a09e883b8 "j >= 0", file=file@entry=0x7f0a09e88350 "jas_image.c", line=line@entry=1387, function=function@entry=0x7f0a09e884d0 "jas_image_chclrspc") at assert.c:92 #9 0x7f0a2062e2d2 in __GI___assert_fail (assertion=0x7f0a09e883b8 "j >= 0", file=0x7f0a09e88350 "jas_image.c", line=1387, function=0x7f0a09e884d0 "jas_image_chclrspc") at assert.c:101 #10 0x7f0a09e591bf in jas_image_chclrspc () from /usr/lib/x86_64-linux-gnu/libjasper.so.1 #11 0x7f0a0a0ab4e4 in ?? () from /usr/lib/kde4/plugins/imageformats/kimg_jp2.so #12 0x7f0a21dc7fc4 in QImageReader::read(QImage*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #13 0x7f0a1dbf0497 in ?? () from /usr/lib/libkhtml.so.5 #14 0x7f0a1dbe76a2 in ?? () from /usr/lib/libkhtml.so.5 #15 0x7f0a1dae85e1 in ?? () from /usr/lib/libkhtml.so.5 #16 0x7f0a212f371c in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #17 0x7f0a21785152 in KJob::result(KJob*) () from /usr/lib/libkdecore.so.5 #18 0x7f0a217851a0 in KJob::emitResult() () from /usr/lib/libkdecore.so.5 #19 0x7f0a20226b3b in KIO::SimpleJob::slotFinished() () from /usr/lib/libkio.so.5 #20 0x7f0a20227f61 in KIO::TransferJob::slotFinished() () from /usr/lib/libkio.so.5 #21 0x7f0a212f371c in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #22 0x7f0a202d2448 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /usr/lib/libkio.so.5 #23 0x7f0a202cf3ad in KIO::SlaveInterface::dispatch() () from /usr/lib/libkio.so.5 #24 0x7f0a202c1efe in KIO::Slave::gotInput() () from /usr/lib/libkio.so.5 #25 0x7f0a212f371c in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #26 0x7f0a201ed2f9 in ?? () from /usr/lib/libkio.so.5 #27 0x7f0a212f7e11 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #28 0x7f0a21cff48c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #29 0x7f0a21d05fa8 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #30 0x7f0a22a771aa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #31 0x7f0a212de71d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #32 0x7f0a212e1fc1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #33 0x7f0a2130dbd3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #34 0x7f0a1b151c5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x7f0a1b151f48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #36 0x7f0a1b151ffc in g_main_context_iteration () from /li
[Bug 131710] Kmail does not remember sender identity in folders for IMAP accounts
https://bugs.kde.org/show_bug.cgi?id=131710 Brice Hunt changed: What|Removed |Added CC||shoalcre...@gmail.com --- Comment #9 from Brice Hunt 2009-10-26 23:25:13 --- I experience the same bug in KMail 1.12.2 (KDE 4.3.2) in Debian Unstable (Sid). Since I have only one IMAP account, I set my corresponding Identity for that account as default and tell all IMAP folders to use the default account. -- 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 181551] Add arguments for command generating signature
https://bugs.kde.org/show_bug.cgi?id=181551 Brice Hunt changed: What|Removed |Added CC||shoalcre...@gmail.com --- Comment #2 from Brice Hunt 2009-10-23 02:34:04 --- Or you could just use customized templates. -- 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 211492] switching identity in composer window does not switch signature
https://bugs.kde.org/show_bug.cgi?id=211492 Brice Hunt changed: What|Removed |Added CC||shoalcre...@gmail.com --- Comment #1 from Brice Hunt 2009-10-23 02:05:34 --- UPDATE: I have determined more specifically when the behavior is exhibited. Whenever using direct input from the "fortune" program to create the signature, KMail gets stuck on that signature and won't change when the identity changes. It also seems to exhibit the behavior when getting input from a bash script. This has nothing to do if the identity is the default or not. Test this by calling fortune directly for an identity's signature. Load the compose window and try to change to and from the identity that call's fortune. Follow this up by calling fortune from the command line and redirecting the output to a file, like this: $ fortune > sig.txt Then change the identity to read the file or even run "cat sig.txt". Kmail stops exhibiting the erratic behavior when changing identities. This tells me that there is probably something in the direct output of the fortune program (e.g. a stream control character) that KMail is picking up and inserting into the signature, causing it to no longer recognize the signature properly. It also seems to exhibit the behavior whenever running a bash script to extract the signature. I am not sure if this is something new with a more recent version of fortune or if it is something that has changed with KMail. The workaround that I use is to set a cron job that outputs a fortune cookie to a signature file every so often. Then, from KMail, load the signature file for the identity that uses the fortune cookie. -- 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 211492] New: switching identity in composer window does not switch signature
https://bugs.kde.org/show_bug.cgi?id=211492 Summary: switching identity in composer window does not switch signature Product: kmail Version: 1.12.2 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: shoalcre...@gmail.com Version: 1.12.2 (using 4.3.2 (KDE 4.3.2), Debian packages) Compiler: cc OS:Linux (i686) release 2.6.30-2-686 To reproduce this problem, create multiple identities, each one with a different signature. Set the program to automatically insert signatures. Then click the toolbar button to compose a new message. The default profile's signature is automatically inserted, as it should. In the composer window, choose "View->Identity" to show the identity field if it is not already shown. Switch to a different identity in the composer window by using the drop-down in the identity field. The signature does not change. It should automatically change to the new identity's signature, but it does not. It gets better. In the composer window, delete the default signature and use "Attach->Append Signature" to insert the current identity's signature. Now switch back to the default identity in the identity field. The signature switches back to the default. It appears that a function is not being called somewhere or the automatic signature insertion is only being applied to the default identity. This worked perfectly in KMail that came with KDE 3.5.*. It could work perfectly now. If the bug can be found and fixed, that would save me several clicks per email and I would be quite grateful. In the meanwhile, once %SIGNATURE is usable in custom templates in current distros, there are ways I could work around this particular inconvenience with custom templates. Until then, I'm stuck with deleting and attaching signatures. BTW, I have purged kmail settings in my home directory and tried with a from scratch rebuild of my kmail settings. It didn't solve the problem. This is caused by some logic error from somewhere within the program. -- 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
