Bug 179579 - The application Akregator (akregator) crashed and caused the signal 11 (SIGSEGV) at startup and will not open, After Upgrade from OpenSuse 11.0 to 11.1 (x86_64)
Summary: The application Akregator (akregator) crashed and caused the signal 11 (SIGSE...
Status: RESOLVED WORKSFORME
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-01-04 10:31 UTC by clint
Modified: 2018-10-21 04:37 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description clint 2009-01-04 10:31:57 UTC
Version:           4.1.3-3.11 (using KDE 4.1.3)
OS:                Linux
Installed from:    SuSE RPMs

Application: Akregator (akregator), signal SIGSEGV
[?1034h(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0x00007f1a8532e33a in QString::fromLatin1_helper(char const*, int) ()
   from /usr/lib64/libQtCore.so.4
#6  0x00007f1a71d62020 in ?? ()
   from /usr/lib64/kde4/akregator_mk4storage_plugin.so
#7  0x00007f1a72350861 in Akregator::Feed::loadArticles() ()
   from /usr/lib64/kde4/akregatorpart.so
#8  0x00007f1a72353bdc in Akregator::Feed::fromOPML(QDomElement, Akregator::Backend::Storage*) () from /usr/lib64/kde4/akregatorpart.so
#9  0x00007f1a7235eee5 in Akregator::FeedList::parseChildNodes(QDomNode&, Akregator::Folder*) () from /usr/lib64/kde4/akregatorpart.so
#10 0x00007f1a7235f11e in Akregator::FeedList::parseChildNodes(QDomNode&, Akregator::Folder*) () from /usr/lib64/kde4/akregatorpart.so
#11 0x00007f1a7235f7a2 in Akregator::FeedList::readFromOpml(QDomDocument const&) () from /usr/lib64/kde4/akregatorpart.so
#12 0x00007f1a723a82fe in Akregator::MainWidget::loadFeeds(QDomDocument const&, Akregator::Folder*) () from /usr/lib64/kde4/akregatorpart.so
#13 0x00007f1a723a5566 in ?? () from /usr/lib64/kde4/akregatorpart.so
#14 0x00007f1a7239eff4 in ?? () from /usr/lib64/kde4/akregatorpart.so
#15 0x00007f1a7239e28c in ?? () from /usr/lib64/kde4/akregatorpart.so
#16 0x00007f1a7239e2ed in ?? () from /usr/lib64/kde4/akregatorpart.so
#17 0x000000000040afd7 in _start ()
Comment 1 FiNeX 2009-01-05 01:50:53 UTC
Hi! Can you explain how to reproduce the crash?

If you can reproduce it, you should install the debug enabled packages and provide a new backtrace. Read this page for the instructions:

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Thanks!
Comment 2 clint 2009-01-05 23:26:34 UTC
(In reply to comment #1)

Unable to reproduce crash exactly as occurred as akregator crashed on startup producing the KDE crash dialog from which I obtained the previously added backtrace. Since then akregator does not start and the error is not reproduced on restart. When running akregator from desktop it simply produces the bouncing cursor and then dissappears. I was also unable to locate -debuginfo rpms for akregator. Below is the strace and gdb output:

zebluey@linux-blqj:~> gdb akregator
GNU gdb (GDB; openSUSE 11.1) 6.8.50.20081120-cvs
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
For bug reporting instructions, please see:
<http://bugs.opensuse.org/>...
(no debugging symbols found)
(gdb) run
Starting program: /usr/bin/akregator 
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
.
.
.
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')
Object::connect: No such slot Akregator::ArticleListView::slotPaletteOrFontChanged()
KCrash: Application 'akregator' crashing...
sock_file=/home/zebluey/.kde4/socket-linux-blqj/kdeinit4__0
akregator(10474): Communication problem with  "akregator" , it probably crashed. 
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " 


Program exited with code 0377.


zebluey@linux-blqj:~> strace -f -ttt -o strace.log akregator
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')
Object::connect: No such slot Akregator::ArticleListView::slotPaletteOrFontChanged()
KCrash: Application 'akregator' crashing...
sock_file=/home/zebluey/.kde4/socket-linux-blqj/kdeinit4__0
akregator(10521): Communication problem with  "akregator" , it probably crashed. 
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "

Hope that helps!
Comment 3 Dario Andres 2009-05-17 01:10:00 UTC
Have you experienced the same crash recently with an updated KDE version? Thanks
Comment 4 Dario Andres 2009-06-26 16:28:30 UTC
Marking as NEEDSINFO
Comment 5 Andrew Crouthamel 2018-09-19 04:39:34 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-10-21 04:37:54 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!