Bug 361846 - Akregator Crashes When Adding a New Feed
Summary: Akregator Crashes When Adding a New Feed
Status: RESOLVED FIXED
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: drkonqi
Depends on:
Blocks:
 
Reported: 2016-04-16 10:15 UTC by kdebugs.anon134
Modified: 2016-08-15 03:49 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 kdebugs.anon134 2016-04-16 10:15:27 UTC
Application: akregator (5.1.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.20-11-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
1)  In the column labeled "Feeds", I right-clicked on the folder named "All Feeds".
2)  I clicked the option labeled "Add Feed".
3)  I entered the address "https://news.opensuse.org/feed" into the text box labeled "Feed URL", then clicked the button labeled "OK".
4)  Akregator crashed.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f95e3cd6840 (LWP 2270))]

Thread 3 (Thread 0x7f95b7503700 (LWP 2298)):
#0  0x00007f95df9f8bbd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f95d89b7e64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f95d89b7f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f95e0541d8b in QEventDispatcherGlib::processEvents (this=0x7f95b00008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x00007f95e04e8d53 in QEventLoop::exec (this=this@entry=0x7f95b7502d90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x00007f95e030a61a in QThread::exec (this=<optimized out>) at thread/qthread.cpp:503
#6  0x00007f95e030f32f in QThreadPrivate::start (arg=0x1a50470) at thread/qthread_unix.cpp:331
#7  0x00007f95d8edc0a4 in start_thread (arg=0x7f95b7503700) at pthread_create.c:309
#8  0x00007f95dfa00fed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f95b591b700 (LWP 3094)):
#0  0x00007f95df9f8bbd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f95d89b7e64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f95d89b7f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f95e0541d8b in QEventDispatcherGlib::processEvents (this=0x7f95a8002fd0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x00007f95e04e8d53 in QEventLoop::exec (this=this@entry=0x7f95b591ad50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x00007f95e030a61a in QThread::exec (this=<optimized out>) at thread/qthread.cpp:503
#6  0x00007f95dde36de7 in ?? () from /usr/lib64/libKF5KIOCore.so.5
#7  0x00007f95e030f32f in QThreadPrivate::start (arg=0x7f95de0ba020) at thread/qthread_unix.cpp:331
#8  0x00007f95d8edc0a4 in start_thread (arg=0x7f95b591b700) at pthread_create.c:309
#9  0x00007f95dfa00fed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f95e3cd6840 (LWP 2270)):
[KCrash Handler]
#6  ref (this=<optimized out>) at ../../src/corelib/arch/qatomic_x86_64.h:121
#7  QList (this=0x7f9592b19458 <QPrinterInfoPrivate::shared_null+24>) at ../../src/corelib/tools/qlist.h:121
#8  QPrinterInfoPrivate (name=..., this=0x7f9592b19440 <QPrinterInfoPrivate::shared_null>) at painting/qprinterinfo_p.h:71
#9  __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at painting/qprinterinfo.cpp:35
#10 _GLOBAL__sub_I_qprinterinfo.cpp(void) () at painting/qprinterinfo.cpp:163
#11 0x00007f95e3b3a8ea in call_init (l=<optimized out>, argc=argc@entry=3, argv=argv@entry=0x7ffeb4c91ed8, env=env@entry=0x7ffeb4c91ef8) at dl-init.c:78
#12 0x00007f95e3b3a9d3 in call_init (env=0x7ffeb4c91ef8, argv=0x7ffeb4c91ed8, argc=3, l=<optimized out>) at dl-init.c:36
#13 _dl_init (main_map=main_map@entry=0x23caf80, argc=3, argv=0x7ffeb4c91ed8, env=0x7ffeb4c91ef8) at dl-init.c:126
#14 0x00007f95e3b3eb08 in dl_open_worker (a=a@entry=0x7ffeb4c8e6b8) at dl-open.c:566
#15 0x00007f95e3b3a7a4 in _dl_catch_error (objname=objname@entry=0x7ffeb4c8e6a8, errstring=errstring@entry=0x7ffeb4c8e6b0, mallocedp=mallocedp@entry=0x7ffeb4c8e6a7, operate=operate@entry=0x7f95e3b3e830 <dl_open_worker>, args=args@entry=0x7ffeb4c8e6b8) at dl-error.c:187
#16 0x00007f95e3b3e2fb in _dl_open (file=0x23c6460 "/usr/lib64/gstreamer-1.0/libgstqtvideosink.so", mode=-2147483646, caller_dlopen=<optimized out>, nsid=-2, argc=3, argv=0x7ffeb4c91ed8, env=0x7ffeb4c91ef8) at dl-open.c:650
#17 0x00007f95d6de502b in dlopen_doit (a=a@entry=0x7ffeb4c8e8d0) at dlopen.c:66
#18 0x00007f95e3b3a7a4 in _dl_catch_error (objname=0x1886130, errstring=0x1886138, mallocedp=0x1886128, operate=0x7f95d6de4fd0 <dlopen_doit>, args=0x7ffeb4c8e8d0) at dl-error.c:187
#19 0x00007f95d6de55dd in _dlerror_run (operate=operate@entry=0x7f95d6de4fd0 <dlopen_doit>, args=args@entry=0x7ffeb4c8e8d0) at dlerror.c:163
#20 0x00007f95d6de50c1 in __dlopen (file=file@entry=0x23c6460 "/usr/lib64/gstreamer-1.0/libgstqtvideosink.so", mode=mode@entry=2) at dlopen.c:87
#21 0x00007f95c82c59a1 in _g_module_open (bind_local=1, bind_lazy=0, file_name=<optimized out>) at gmodule-dl.c:97
#22 g_module_open (file_name=0x23c6410 "/usr/lib64/gstreamer-1.0/libgstqtvideosink.so", flags=G_MODULE_BIND_LOCAL) at gmodule.c:573
#23 0x00007f95ca93231a in gst_preset_default_save_presets_file (preset=0x0) at gstpreset.c:799
#24 0x0000000000000000 in ?? ()

Possible duplicates by query: bug 350096, bug 348548, bug 347679, bug 344106, bug 337469.

Reported using DrKonqi
Comment 1 Laurent Montel 2016-04-25 05:25:55 UTC
I can't reproduce it in last version.
could you verify with kdepim 5.1 or 5.2 ?
thanks
Comment 2 kdebugs.anon134 2016-08-15 03:49:34 UTC
(In reply to Laurent Montel from comment #1)
> I can't reproduce it in last version.
> could you verify with kdepim 5.1 or 5.2 ?
> thanks

As of Akregator Version 4.14.10, I can no longer reproduce this problem.  It seems to work correctly now.