Akregator doesn't start up (Intrepid)

[targon]

Binary package hint: akregator

Since the last KDE crash, Akregator fails to start up. When started from the console, it displays the following messages and then terminates without ever showing a window or anything else:

me@kubuntu:~$ akregator
akregator(15573) Akregator::PluginManager::query: Plugin trader constraint: "[X-KDE-akregator-framework-version] == 2 and [X-KDE-akregator-plugintype] == 'storage' and [X-KDE-akregator-rank] > 0"
akregator(15573) Akregator::PluginManager::createFromService: Trying to load: "akregator_mk4storage_plugin"
akregator(15573) Akregator::PluginManager::dump: PluginManager Service Info:
---------------------------
name : "Metakit storage backend"
library : "akregator_mk4storage_plugin"
desktopEntryPath : "akregator_mk4storage_plugin.desktop"
X-KDE-akregator-plugintype : "storage"
X-KDE-akregator-name : "metakit"
X-KDE-akregator-authors : ("Frank Osterfeld")
X-KDE-akregator-rank : "255"
X-KDE-akregator-version : "1"
X-KDE-akregator-framework-version: "2"
Object::connect: No such signal Akregator::SubscriptionListView::signalContextMenu(K3ListView*,Akregator::TreeNode*,QPoint)
Object::connect: (sender name: 'feedtree')
Object::connect: (receiver name: 'akregator_view')
Object::connect: No such signal Akregator::SubscriptionListView::signalDropped(KUrl::List&,Akregator::TreeNode*,Akregator::Folder*)
Object::connect: (sender name: 'feedtree')
Object::connect: (receiver name: 'akregator_view')
akregator(15573) Akregator::SelectionController::setUp:
akregator(15573) Akregator::SelectionController::setUp:
Object::connect: No such slot Akregator::ArticleListView::slotPaletteOrFontChanged()
akregator(15573) Akregator::SelectionController::setUp:
akregator(15573) Akregator::SubscriptionListView::loadHeaderSettings: 0 244
akregator(15573) Akregator::SubscriptionListView::loadHeaderSettings: 1 100
akregator(15573) Akregator::SubscriptionListView::loadHeaderSettings: 2 0
Object::disconnect: Unexpected null parameter
akregator(15573) Akregator::FeedList::readFromOpml: loading OPML feed "opml"
akregator(15573) Akregator::FeedList::readFromOpml: measuring startup time: START
akregator(15573) Akregator::Backend::FeedStorageMK4Impl::FeedStorageMK4Impl: "http://some.feed"
[...]
akregator(15573) Akregator::Backend::FeedStorageMK4Impl::FeedStorageMK4Impl: "http://some.feed"
akregator(15573) Akregator::FeedList::readFromOpml: measuring startup time: STOP, 93 ms
akregator(15573) Akregator::FeedList::readFromOpml: Number of articles loaded: 3221
akregator(15573) Akregator::SelectionController::setUp:
akregator(15573) Akregator::SubscriptionListView::loadHeaderSettings: 0 244
akregator(15573) Akregator::SubscriptionListView::loadHeaderSettings: 1 100
akregator(15573) Akregator::SubscriptionListView::loadHeaderSettings: 2 0
me@kubuntu:~$

Description: Ubuntu intrepid (development branch)
Release: 8.10
KDEPIM 4:4.1.2-0ubuntu1
AKregator 4:4.1.2-0ubuntu1

[Harald Sitter (apachelogger)]

Please run
  strace akregator --nofork > ~/akregator.strace 2>&1
don't move the mouse cursor a lot while doing this. If you think it stopped doing something special (like your harddisk stops spinning), press ctrl+c and attach the file akregator.strace to this bug

Also do
  kdebugdialog -> select all
  akregator --nofork > ~/akregator.console 2>&1
press again Ctrl+C if the process doesn't exist automagically and attach the file akregator.console to this report.

If you didn't have to do Ctrl+C both times, it is very likely that akregator crashed, in this case please do
  sudo apt-get install kdepim-dbg
  gdb /usr/bin/akregator
    run
   (wait for the crash to happen)
    bt
A couple of lines with references to .cpp files should be spit out, please save everything after the bt command in akregator.gdb and attach it as well.
You can leave gdb with the command
   quit

Some of these files might include senisble data, so if you want, I can turn this bug into a private one, so it is only accessible to Ubuntu developers and the Ubuntu bug squad. Or you just check the files and strip such data, which is not preferrable as it might easily happen that you remove essential debugging data.

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!