Version: 1.1.2 (using KDE 3.4.2-1.0.fc3.kde, Fedora) Compiler: gcc version 3.4.3 20050227 (Red Hat 3.4.3-22.fc3) OS: Linux (i686) release 2.6.10-1.770_14.rhfc3.at Some feeds (such as the Google mail Atom feed) require the user to be authenticated. Allowing a username and password to be specified for a feed would allow Akregator to load feeds like this. In order to keep things secure, it might be a good idea to attempt to load these feeds via HTTPS, falling back to HTTP if this is not available.
The feed's URL should (and will, if the server admins aren't completely nuts) indicate if HTTP or HTTPS (SSL) is required. And by the way: I definitely would like to see that feature, too! :-)
Yep, Akregator should support authentication better. Right now it's broken. It only works when you logged in for the site in konqueror. If you are not logged in, fetching just fails.
Somehow related to Bug 130529.
When I try to load a feed that requires authentication (LiveJournal for example) and I am NOT logged in via Konqueror, Akregator throws a SIGSEVG and loads up the KDE Crash Handler. This can be easily replicated if anyone needs to see the traceback.
David: Yes, a backtrace would be useful. Please also tell us your Akregator version and general KDE(libs) version. Do you use "load the full website when reading articles" option for the feed in question? I am aware that it doesn't work, but crashes were never reported.
On Saturday 31 March 2007 02:23:45 am Frank Osterfeld wrote: > http://bugs.kde.org/show_bug.cgi?id=110419 > ------- Additional Comments From frank.osterfeld kdemail net 2007-03-31 > 09:23 ------- David: Yes, a backtrace would be useful. Please also tell us > your Akregator version and general KDE(libs) version. Do you use "load the > full website when reading articles" option for the feed in question? I am > aware that it doesn't work, but crashes were never reported. I am using Akregator 1.2.6 on KDE 3.5.6 on FreeBSD 6.2-RELEASE-p3 I do use the load full website option. A test to see what happens with that option unchecked properly got a 403 Forbidden error when I click on the "full story" link. The traceback is below. I hope it proves helpful. David [New LWP 103480] [Switching to LWP 103480] 0x29efaf23 in nanosleep () from /lib/libc.so.6 #0 0x29efaf23 in nanosleep () from /lib/libc.so.6 #1 0x29e40ae3 in _nanosleep () from /lib/libpthread.so.2 #2 0x29ed5df9 in sleep () from /lib/libc.so.6 #3 0x29e363fe in sleep () from /lib/libpthread.so.2 #4 0x292f86e6 in KCrash::startDrKonqi () from /usr/local/lib/libkdecore.so.6 #5 0x292f8a8c in KCrash::defaultCrashHandler () from /usr/local/lib/libkdecore.so.6 #6 0x29e3df5d in sigaction () from /lib/libpthread.so.2 #7 0xbfbfff94 in ?? () #8 0x0000000b in ?? () #9 0xbfbfda50 in ?? () #10 0xbfbfd790 in ?? () #11 0x00000000 in ?? () #12 0x29e3da24 in sigaction () from /lib/libpthread.so.2 #13 0x286399b6 in KHTMLPart::qt_invoke () from /usr/local/lib/libkhtml.so.6 #14 0x2a2bbd03 in Akregator::Viewer::qt_invoke () from /usr/local/lib/kde3/libakregatorpart.so #15 0x2a2c383b in Akregator::ArticleViewer::qt_invoke () from /usr/local/lib/kde3/libakregatorpart.so #16 0x297e2618 in QObject::activate_signal () from /usr/X11R6/lib/libqt-mt.so.3 #17 0x28cdfbef in KIO::Job::result () from /usr/local/lib/libkio.so.6 #18 0x28cdfc8e in KIO::Job::emitResult () from /usr/local/lib/libkio.so.6 #19 0x28ce1959 in KIO::SimpleJob::slotFinished () from /usr/local/lib/libkio.so.6 #20 0x28ce716d in KIO::TransferJob::slotFinished () from /usr/local/lib/libkio.so.6 #21 0x28ce23c5 in KIO::TransferJob::qt_invoke () from /usr/local/lib/libkio.so.6 #22 0x297e2684 in QObject::activate_signal () from /usr/X11R6/lib/libqt-mt.so.3 #23 0x297e2cf5 in QObject::activate_signal () from /usr/X11R6/lib/libqt-mt.so.3 #24 0x28ccf2fc in KIO::SlaveInterface::finished () from /usr/local/lib/libkio.so.6 #25 0x28cd1c3e in KIO::SlaveInterface::dispatch () from /usr/local/lib/libkio.so.6 #26 0x28cd07b5 in KIO::SlaveInterface::dispatch () from /usr/local/lib/libkio.so.6 #27 0x28cccd24 in KIO::Slave::gotInput () from /usr/local/lib/libkio.so.6 #28 0x28ccd089 in KIO::Slave::qt_invoke () from /usr/local/lib/libkio.so.6 #29 0x297e2684 in QObject::activate_signal () from /usr/X11R6/lib/libqt-mt.so.3 #30 0x297e2bb8 in QObject::activate_signal () from /usr/X11R6/lib/libqt-mt.so.3 #31 0x29ae5e7d in QSocketNotifier::activated () from /usr/X11R6/lib/libqt-mt.so.3 #32 0x297fb724 in QSocketNotifier::event () from /usr/X11R6/lib/libqt-mt.so.3 #33 0x29786075 in QApplication::internalNotify () from /usr/X11R6/lib/libqt-mt.so.3 #34 0x2978620a in QApplication::notify () from /usr/X11R6/lib/libqt-mt.so.3 #35 0x29267a2a in KApplication::notify () from /usr/local/lib/libkdecore.so.6 #36 0x2977a95b in QEventLoop::activateSocketNotifiers () from /usr/X11R6/lib/libqt-mt.so.3 #37 0x2973768c in QEventLoop::processEvents () from /usr/X11R6/lib/libqt-mt.so.3 #38 0x2979a4cb in QEventLoop::enterLoop () from /usr/X11R6/lib/libqt-mt.so.3 #39 0x2979a424 in QEventLoop::exec () from /usr/X11R6/lib/libqt-mt.so.3 #40 0x297853b0 in QApplication::exec () from /usr/X11R6/lib/libqt-mt.so.3 #41 0x080512c6 in main ()
*** Bug 150075 has been marked as a duplicate of this bug. ***
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.