[akregator] [Bug 336417] Akregator crashes when being closed

2016-04-11 Thread Mauro47 via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=336417

Mauro47  changed:

   What|Removed |Added

 CC||msovr...@yahoo.it

-- 
You are receiving this mail because:
You are watching all bug changes.


[akregator] [Bug 336417] Akregator crashes when being closed

2016-04-11 Thread Mauro47 via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=336417

--- Comment #37 from Mauro47  ---
Created attachment 98340
  --> https://bugs.kde.org/attachment.cgi?id=98340=edit
New crash information added by DrKonqi

akregator (4.14.1) on KDE Platform 4.14.2 using Qt 4.8.6

- What I was doing when the application crashed: 
I simply closed the application. No problem when the application was open and
running

-- Backtrace (Reduced):
#7  0x7fb63503ff62 in Akregator::Frame::signalCompleted(Akregator::Frame*)
() from /usr/lib/libakregatorprivate.so.4
#8  0x7fb63503581b in
Akregator::Frame::slotSetState(Akregator::Frame::State) () from
/usr/lib/libakregatorprivate.so.4
#9  0x7fb61a38f3c7 in Akregator::MainWidget::slotFetchingStopped() () from
/usr/lib/kde4/akregatorpart.so
[...]
#11 0x7fb635035449 in Akregator::FetchQueue::slotAbort() () from
/usr/lib/libakregatorprivate.so.4
#12 0x7fb6350354ca in Akregator::FetchQueue::~FetchQueue() () from
/usr/lib/libakregatorprivate.so.4

-- 
You are receiving this mail because:
You are watching all bug changes.


[akregator] [Bug 336417] Akregator crashes when being closed

2016-03-11 Thread Luigi Toscano via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=336417

--- Comment #36 from Luigi Toscano  ---
(In reply to Alexis Kauffmann from comment #34)
> This problem is, apparently, NOT FIXED, since it happens here every time I
> close Akregator. Here is the "two-star" backtrace I am getting in the hope
> it helps:

Alexis, the bug here was definitely resolved in kdepim version 4.14.3. Which
version of kdepim do you use?

-- 
You are receiving this mail because:
You are watching all bug changes.


[akregator] [Bug 336417] Akregator crashes when being closed

2016-03-11 Thread Alexis Kauffmann via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=336417

Alexis Kauffmann  changed:

   What|Removed |Added

 CC||l...@gehspace.com

--- Comment #34 from Alexis Kauffmann  ---
This problem is, apparently, NOT FIXED, since it happens here every time I
close Akregator. Here is the "two-star" backtrace I am getting in the hope it
helps:

Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7f26cd049471 in isSignalConnected (signal_index=7, this=0x9) at
kernel/qobject_p.h:237
#7  QMetaObject::activate (sender=0x2c21360, m=m@entry=0x7f26cf088900
,
local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x739a5c90)
at kernel/qobject.cpp:3472
#8  0x7f26cee6ef62 in Akregator::Frame::signalCompleted (this=, _t1=0x2c21360) at moc_frame.cpp:200
#9  0x7f26cee6481b in Akregator::Frame::slotSetState (this=,
state=state@entry=Akregator::Frame::Completed) at
../../../akregator/src/frame.cpp:94
#10 0x7f26b44353c7 in Akregator::MainWidget::slotFetchingStopped
(this=0x7e5090) at ../../../akregator/src/mainwidget.cpp:808
#11 0x7f26cd04971c in QMetaObject::activate (sender=sender@entry=0x882690,
m=m@entry=0x7f26cf088940 ,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at
kernel/qobject.cpp:3567
#12 0x7f26cee6e9e3 in Akregator::FetchQueue::signalStopped
(this=this@entry=0x882690) at moc_fetchqueue.cpp:126
#13 0x7f26cee64449 in Akregator::FetchQueue::slotAbort
(this=this@entry=0x882690) at ../../../akregator/src/fetchqueue.cpp:68
#14 0x7f26cee644ca in Akregator::FetchQueue::~FetchQueue (this=0x882690,
__in_chrg=) at ../../../akregator/src/fetchqueue.cpp:50
#15 0x7f26cee64539 in Akregator::FetchQueue::~FetchQueue (this=0x882690,
__in_chrg=) at ../../../akregator/src/fetchqueue.cpp:53
#16 0x7f26cee63389 in Akregator::Kernel::~Kernel (this=0x7f26cf08a718
, __in_chrg=) at
../../../akregator/src/kernel.cpp:66
#17 0x7f26cc39cb29 in __run_exit_handlers (status=0, listp=0x7f26cc70a5a8
<__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#18 0x7f26cc39cb75 in __GI_exit (status=) at exit.c:104
#19 0x7f26cc386b4c in __libc_start_main (main=0x407240 ,
argc=5, argv=0x739a5fd8, init=, fini=,
rtld_fini=, stack_end=0x739a5fc8) at libc-start.c:321
#20 0x004079fd in _start ()

-- 
You are receiving this mail because:
You are watching all bug changes.