1645585 – akregator killed by SIGSEGV

Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1645585 - akregator killed by SIGSEGV

Summary: akregator killed by SIGSEGV

Keywords:
Status:	CLOSED EOL
Alias:	None
Product:	Fedora
Classification:	Fedora
Component:	akregator
Sub Component:
Version:	29
Hardware:	x86_64
OS:	Linux
Priority:	unspecified
Severity:	medium
Target Milestone:	---
Assignee:	Rex Dieter
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2018-11-02 15:10 UTC by Talha Khan
Modified:	2019-11-27 21:21 UTC (History)
CC List:	4 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2019-11-27 21:21:04 UTC
Type:	Bug
Embargoed:
Dependent Products:

Attachments	(Terms of Use)
akregator gdb backtrace (51.25 KB, text/plain) 2018-12-04 21:30 UTC, Talha Khan	no flags	Details
View All

Links
System	ID	Private	Priority	Status	Summary	Last Updated
KDE Software Compilation	371511	0	NOR	RESOLVED	kontact/akregator crashes while trying to open a link from the list (middle click)	2020-10-18 21:08:51 UTC

Description Talha Khan 2018-11-02 15:10:37 UTC

Description of problem:

Akregator randomly crashes during use. Previously, abrt did not catch the crashes, but this time it reported the crash with the reason:

akregator killed by SIGSEGV


Version-Release number of selected component (if applicable):

akregator-18.08.1-1.fc29

How reproducible:

Use akregator

Steps to Reproduce:
1. Open akregator 
2. Use like normal, including opening a few of the feed links in a new tab.
3.

Actual results:

akregator crashes and automatically closes. When you run it again, it asks if you want to restore your session.

Expected results:

No crash

Additional info:

The results were uploaded to:
URL=https://retrace.fedoraproject.org/faf/dumpdirs/new/ccpp-2018-11-02-09:33:39.961449-3796.tar.gz

Journalctl output:


Nov 02 09:33:36 hostname.localdomain kernel: Chrome_IOThread[3838]: segfault at 4800000001 ip 00007ffbd1f6423f sp 00007ffb44ff69b0 error 4 in libgcc_s-8-20181011.so.1[7ffbd1f57000+12000]
Nov 02 09:33:36 hostname.localdomain kernel: Code: 09 c1 84 d2 78 e5 c6 85 72 01 00 00 01 4e 8d 04 0b 41 0f b6 44 24 01 49 83 c4 01 e9 64 fd ff ff 0f 1f 00 49 8b 85 98 00 00 00 <80> 38 48 75 9c 48 ba c7 c0 0f 00 00 00 0f 05 48 39 50 01 >
Nov 02 09:33:36 hostname.localdomain systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Nov 02 09:33:36 hostname.localdomain systemd[1]: Started Process Core Dump (PID 4421/UID 0).
Nov 02 09:33:36 hostname.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@0-4421-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?>
Nov 02 09:33:37 hostname.localdomain plasmashell[1372]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:119:22: Unable to assign [undefined] to QQmlListModel*
Nov 02 09:33:37 hostname.localdomain plasmashell[1372]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:113: ReferenceError: appIcon is not defined
Nov 02 09:33:38 hostname.localdomain systemd-coredump[4422]: Core file was truncated to 2147483648 bytes.
Nov 02 09:33:39 hostname.localdomain abrt-dump-journal-core[1081]: Failed to obtain all required information from journald
Nov 02 09:33:39 hostname.localdomain systemd-coredump[4422]: Process 3796 (akregator) of user 1000 dumped core.
                                                             
                                                             Stack trace of thread 3838:
                                                             #0  0x00007ffbd1f6423f n/a (n/a)
Nov 02 09:33:39 hostname.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@0-4421-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? >
Nov 02 09:33:39 hostname.localdomain kwin_x11[1366]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 36190, resource id: 123731988, major code: 15 (QueryTree), minor code: 0
Nov 02 09:33:40 hostname.localdomain kwin_x11[1366]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 36223, resource id: 37748822, major code: 18 (ChangeProperty), minor code: 0
Nov 02 09:33:41 hostname.localdomain kmail[3687]: qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 32784, resource id: 121634887, major code: 130 (Unknown), minor code: 3
Nov 02 09:33:41 hostname.localdomain kmail[3687]: qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 32798, resource id: 121634887, major code: 130 (Unknown), minor code: 3
Nov 02 09:33:41 hostname.localdomain kmail[3687]: qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 32802, resource id: 121634887, major code: 130 (Unknown), minor code: 3
Nov 02 09:33:43 hostname.localdomain abrtd[768]: Size of '/var/spool/abrt' >= 5000 MB (MaxCrashReportsSize), deleting old directory 'ccpp-2018-11-01-13:53:00.153286-4621'
Nov 02 09:33:45 hostname.localdomain plasmashell[1372]: QQuickItem::stackAfter: Cannot stack StatusNotifierItem_QMLTYPE_284(0x560fca673cc0, parent=0x560fc818aa90, geometry=0,0 0x0) after StatusNotifierItem_QMLTYPE_284(0x560fca7b03a0), w>
Nov 02 09:33:46 hostname.localdomain kdeinit5[4507]: kf5.kio.core: finished() called after error()! Please fix the "kio_http" KIO slave
Nov 02 09:33:50 hostname.localdomain plasmashell[1372]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 17672, resource id: 102760501, major code: 141 (Unknown), minor code: 3
Nov 02 09:33:51 hostname.localdomain kwin_x11[1366]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40888, resource id: 125829120, major code: 18 (ChangeProperty), minor code: 0
Nov 02 09:33:51 hostname.localdomain kwin_x11[1366]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40902, resource id: 125829121, major code: 18 (ChangeProperty), minor code: 0
Nov 02 09:33:52 hostname.localdomain abrt-server[4432]: Error: No segments found in coredump './coredump'
Nov 02 09:33:52 hostname.localdomain abrt-server[4432]: Can't open file 'core_backtrace' for reading: No such file or directory
Nov 02 09:33:56 hostname.localdomain abrt-notification[4623]: Process 3796 (akregator) crashed in ??()

Comment 1 Talha Khan 2018-11-06 14:03:37 UTC

Here is the std out/err when running akregator from terminal, and crashes without alerting abrt:

Crash 1:

[1:25:1106/090036.552526:ERROR:render_media_log.cc(30)] MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: no supported streams"}
[1:1:1106/090036.911797:ERROR:render_media_log.cc(30)] MediaEvent: PIPELINE_ERROR DEMUXER_ERROR_NO_SUPPORTED_STREAMS
Received signal 11 SEGV_MAPERR 000000000000
#0 0x7f9de2f86dae <unknown>
#1 0x7f9de2f86ec0 <unknown>
#2 0x7f9de2f874f7 <unknown>
#3 0x7f9de7e985c0 <unknown>
  r8: 00007f9d5affa8c8  r9: 00007f9d5affa8d0 r10: 00007f9d3894a8a0 r11: 00007f9d5affa7c0
 r12: 00007f9d38822aa0 r13: 000055a057420880 r14: 00007f9d5affa8c8 r15: 00007f9d38989930
  di: 000055a057420880  si: 00007f9d5affa8c0  bp: 00007f9d5affa9d0  bx: 00007f9d388b5200
  dx: 0000000000000001  ax: 000055a056ad2a50  cx: 0000000000000002  sp: 00007f9d5affa858
  ip: 0000000000000000 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000014
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.



Crash 2:

[1:25:1106/090104.187817:ERROR:render_media_log.cc(30)] MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: no supported streams"}
[1:1:1106/090104.272255:ERROR:render_media_log.cc(30)] MediaEvent: PIPELINE_ERROR DEMUXER_ERROR_NO_SUPPORTED_STREAMS
Received signal 11 SEGV_ACCERR 55d79f624830
#0 0x7f014f9d8dae <unknown>
#1 0x7f014f9d8ec0 <unknown>
#2 0x7f014f9d94f7 <unknown>
#3 0x7f01548ea5c0 <unknown>
#4 0x55d79f624830 <unknown>
  r8: 00007f00b2ffba68  r9: 00007f00b2ffba70 r10: 00007f00a40008d0 r11: 00007f00b2ffb960
 r12: 00007f00a4875070 r13: 000055d79f1a39b0 r14: 00007f00b2ffba68 r15: 00007f00a478f010
  di: 000055d79f1a39b0  si: 00007f00b2ffba60  bp: 00007f00b2ffbb70  bx: 00007f00a47915b0
  dx: 0000000000000001  ax: 000055d79e886910  cx: 0000000000000002  sp: 00007f00b2ffb9f8
  ip: 000055d79f624830 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000015
 trp: 000000000000000e msk: 0000000000000000 cr2: 000055d79f624830
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Comment 2 Rex Dieter 2018-11-06 14:24:32 UTC

Based on that, looks like akregator is trying to display some html content with embedded media (video most likely) and it's crashing  down in qt5-qtwebengine's media/ffmpeg code somewhere.

Can you post the output of:

rpm -q qt5-qtwebengine qt5-qtwebengine-freeworld

please?

Comment 3 Talha Khan 2018-11-06 15:09:19 UTC

Hello Rex,

Thanks for replying. Here's the output:

qt5-qtwebengine-5.11.2-2.fc29.x86_64
package qt5-qtwebengine-freeworld is not installed

looks like I need to install qt5-qtwebengine-freeworld?

Comment 4 Rex Dieter 2018-11-06 17:56:41 UTC

You don't need to install it, but it may be a worthwhile test.

Comment 5 Talha Khan 2018-11-06 20:12:50 UTC

I installed the package, but it is still crashing, even when there is no web page tab opened. Here's the latest output:

[1:22:1106/151142.813717:ERROR:adm_helpers.cc(73)] Failed to query stereo recording.
[1:1:1106/151143.728841:ERROR:BudgetService.cpp(160)] Unable to connect to the Mojo BudgetService.
Received signal 11 SEGV_MAPERR 558500000065
#0 0x7f96d35cc7fe <unknown>
#1 0x7f96d35cc910 <unknown>
#2 0x7f96d35ccf47 <unknown>
#3 0x7f96d83135c0 <unknown>
#4 0x7f96d203c0dc <unknown>
#5 0x7f96d3ad1b46 <unknown>
#6 0x7f96d3c2221b <unknown>
#7 0x7f96d293d2ce <unknown>
#8 0x7f96d293dfad <unknown>
#9 0x7f96d293e19a <unknown>
#10 0x7f96d29378be <unknown>
#11 0x7f96d29391df <unknown>
#12 0x7f96d2926f25 <unknown>
#13 0x7f96d2926830 <unknown>
#14 0x7f96d35cd2a8 <unknown>
#15 0x7f96d35edb0a <unknown>
#16 0x7f96d35ee5bf <unknown>
#17 0x7f96d35ee73a <unknown>
#18 0x7f96d35f1132 <unknown>
#19 0x7f96d36103ab <unknown>
#20 0x7f96d27269ba <unknown>
#21 0x7f96d2726e67 <unknown>
#22 0x7f96d36332a8 <unknown>
#23 0x7f96d362ebc1 <unknown>
#24 0x7f96d069158e start_thread
#25 0x7f96d83d8513 __GI___clone
  r8: 00007f962f7fc4a8  r9: 00007f962f7fc4b0 r10: 00007f961c0008d0 r11: 00007f962f7fc3a0
 r12: 00007f961c96d040 r13: 000055852c472570 r14: 00007f962f7fc4a8 r15: 00007f961c88c560
  di: 000055852c472570  si: 00007f962f7fc4a0  bp: 00007f962f7fc5b0  bx: 00007f961ca3c800
  dx: 0000000000000001  ax: 0000558500000005  cx: 0000000000000002  sp: 00007f962f7fc440
  ip: 00007f96d203c0dc efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000558500000065
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Comment 6 Talha Khan 2018-11-07 14:11:43 UTC

Output from another crash:

Received signal 11 SEGV_ACCERR 562a99443710
#0 0x7fdb095577fe <unknown>
#1 0x7fdb09557910 <unknown>
#2 0x7fdb09557f47 <unknown>
#3 0x7fdb0e29e5c0 <unknown>
#4 0x562a99443710 <unknown>
  r8: 00007fda75ff94a8  r9: 00007fda75ff94b0 r10: 00000000ffffffff r11: 00007fda75ff93a0
 r12: 00007fda5894fb50 r13: 0000562a9898ec80 r14: 00007fda75ff94a8 r15: 00007fda58930f10
  di: 0000562a9898ec80  si: 00007fda75ff94a0  bp: 00007fda75ff95b0  bx: 0000562a99882150
  dx: 0000000000000001  ax: 0000562a99443690  cx: 0000000000000002  sp: 00007fda75ff9438
  ip: 0000562a99443710 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000015
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000562a99443710
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Comment 7 Talha Khan 2018-11-07 16:07:31 UTC

Akregator crashed again when closing a web page tab. This time it was caught by abrt. I had to upload for analysis. Here was the result:

-- Running report_EmergencyAnalysis ---
Compressing data
Sending /var/tmp/ccpp-2018-11-07-11:00:27.342110-20050.tar.gz to https://retrace.fedoraproject.org
Successfully created https://retrace.fedoraproject.org/faf/dumpdirs/new/ccpp-2018-11-07-11:00:27.342110-20050.tar.gz

Here's the std out/err output:

libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
[1:26:1107/110021.485740:ERROR:adm_helpers.cc(73)] Failed to query stereo recording.
Received signal 11 SEGV_MAPERR 000000000060
Segmentation fault (core dumped)

Comment 8 Talha Khan 2018-11-26 16:21:18 UTC

Upgraded akregator to 18.08.3. 
Crashed when closing a web page tab. Here's the output from std err/out:

ibpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
KCrash: Application 'akregator' crashing...
KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
amdgpu: The CS has been rejected, see dmesg for more information (-9).
amdgpu: buffer list creation failed (-9)
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
QSocketNotifier: Invalid socket 149 and type 'Read', disabling...
QSocketNotifier: Invalid socket 94 and type 'Read', disabling...
QSocketNotifier: Invalid socket 70 and type 'Read', disabling...
QSocketNotifier: Invalid socket 174 and type 'Read', disabling...
QSocketNotifier: Invalid socket 155 and type 'Read', disabling...
QSocketNotifier: Invalid socket 224 and type 'Read', disabling...
The X11 connection broke (error 1). Did the X11 server die?

Comment 9 Talha Khan 2018-11-26 16:22:59 UTC

This is the dmesg output for amdgpu:

[    3.558882] [drm] amdgpu kernel modesetting enabled.
[    3.580266] fb: switching to amdgpudrmfb from EFI VGA
[    3.580430] amdgpu 0000:04:00.0: enabling device (0006 -> 0007)
[    3.581776] amdgpu 0000:04:00.0: VRAM: 256M 0x000000F400000000 - 0x000000F40FFFFFFF (256M used)
[    3.581777] amdgpu 0000:04:00.0: GART: 1024M 0x000000F500000000 - 0x000000F53FFFFFFF
[    3.581921] [drm] amdgpu: 256M of VRAM memory ready
[    3.581923] [drm] amdgpu: 3072M of GTT memory ready.
[    4.465883] amdgpu: [powerplay] dpm has been enabled
[    4.467060] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3
[    4.524555] fbcon: amdgpudrmfb (fb0) is primary device
[    4.524562] amdgpu 0000:04:00.0: fb0: amdgpudrmfb frame buffer device
[    4.537624] amdgpu 0000:04:00.0: ring 0(gfx) uses VM inv eng 4 on hub 0
[    4.537627] amdgpu 0000:04:00.0: ring 1(comp_1.0.0) uses VM inv eng 5 on hub 0
[    4.537629] amdgpu 0000:04:00.0: ring 2(comp_1.1.0) uses VM inv eng 6 on hub 0
[    4.537631] amdgpu 0000:04:00.0: ring 3(comp_1.2.0) uses VM inv eng 7 on hub 0
[    4.537633] amdgpu 0000:04:00.0: ring 4(comp_1.3.0) uses VM inv eng 8 on hub 0
[    4.537634] amdgpu 0000:04:00.0: ring 5(comp_1.0.1) uses VM inv eng 9 on hub 0
[    4.537635] amdgpu 0000:04:00.0: ring 6(comp_1.1.1) uses VM inv eng 10 on hub 0
[    4.537637] amdgpu 0000:04:00.0: ring 7(comp_1.2.1) uses VM inv eng 11 on hub 0
[    4.537638] amdgpu 0000:04:00.0: ring 8(comp_1.3.1) uses VM inv eng 12 on hub 0
[    4.537640] amdgpu 0000:04:00.0: ring 9(kiq_2.1.0) uses VM inv eng 13 on hub 0
[    4.537641] amdgpu 0000:04:00.0: ring 10(sdma0) uses VM inv eng 4 on hub 1
[    4.537643] amdgpu 0000:04:00.0: ring 11(vcn_dec) uses VM inv eng 5 on hub 1
[    4.537644] amdgpu 0000:04:00.0: ring 12(vcn_enc0) uses VM inv eng 6 on hub 1
[    4.537646] amdgpu 0000:04:00.0: ring 13(vcn_enc1) uses VM inv eng 7 on hub 1
[    4.537647] amdgpu 0000:04:00.0: ring 14(vcn_jpeg) uses VM inv eng 8 on hub 1
[    4.541317] [drm] Initialized amdgpu 3.27.0 20150101 for 0000:04:00.0 on minor 0
[  663.396309] amdgpu: [powerplay] dpm has been enabled
[  663.448519] amdgpu 0000:04:00.0: ring 0(gfx) uses VM inv eng 4 on hub 0
[  663.448522] amdgpu 0000:04:00.0: ring 1(comp_1.0.0) uses VM inv eng 5 on hub 0
[  663.448524] amdgpu 0000:04:00.0: ring 2(comp_1.1.0) uses VM inv eng 6 on hub 0
[  663.448527] amdgpu 0000:04:00.0: ring 3(comp_1.2.0) uses VM inv eng 7 on hub 0
[  663.448529] amdgpu 0000:04:00.0: ring 4(comp_1.3.0) uses VM inv eng 8 on hub 0
[  663.448531] amdgpu 0000:04:00.0: ring 5(comp_1.0.1) uses VM inv eng 9 on hub 0
[  663.448534] amdgpu 0000:04:00.0: ring 6(comp_1.1.1) uses VM inv eng 10 on hub 0
[  663.448536] amdgpu 0000:04:00.0: ring 7(comp_1.2.1) uses VM inv eng 11 on hub 0
[  663.448538] amdgpu 0000:04:00.0: ring 8(comp_1.3.1) uses VM inv eng 12 on hub 0
[  663.448541] amdgpu 0000:04:00.0: ring 9(kiq_2.1.0) uses VM inv eng 13 on hub 0
[  663.448543] amdgpu 0000:04:00.0: ring 10(sdma0) uses VM inv eng 4 on hub 1
[  663.448545] amdgpu 0000:04:00.0: ring 11(vcn_dec) uses VM inv eng 5 on hub 1
[  663.448548] amdgpu 0000:04:00.0: ring 12(vcn_enc0) uses VM inv eng 6 on hub 1
[  663.448550] amdgpu 0000:04:00.0: ring 13(vcn_enc1) uses VM inv eng 7 on hub 1
[  663.448552] amdgpu 0000:04:00.0: ring 14(vcn_jpeg) uses VM inv eng 8 on hub 1

Comment 10 Talha Khan 2018-11-27 16:00:31 UTC

Crashed when clicking on a link in one of my feeds:

std out/err:

KCrash: Application 'akregator' crashing...
KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
QSocketNotifier: Invalid socket 149 and type 'Read', disabling...
QSocketNotifier: Invalid socket 151 and type 'Read', disabling...
QSocketNotifier: Invalid socket 153 and type 'Read', disabling...
QSocketNotifier: Invalid socket 154 and type 'Read', disabling...
QSocketNotifier: Invalid socket 157 and type 'Read', disabling...
QSocketNotifier: Invalid socket 173 and type 'Read', disabling...
The X11 connection broke (error 1). Did the X11 server die?

I also got a notification "akregator closed unexpectedly", which is better than before. This isn't for abrt, but for akregator, and there are buttons asking me to report the bug and restart the application. The details that appear after opening the notification are:
Executable: akregator PID: 10144 Signal: Segmentation fault (11) Time: 11/27/18 10:50:44

These are the events in journalctl up to the crash, not sure if they are related:

ov 27 10:49:27 myhost.localdomain akregator[9014]: QSocketNotifier: Invalid socket 12 and type 'Read', disabling...
Nov 27 10:49:27 myhost.localdomain akregator[9014]: QSocketNotifier: Invalid socket 63 and type 'Read', disabling...
Nov 27 10:49:27 myhost.localdomain akregator[9014]: QSocketNotifier: Invalid socket 61 and type 'Read', disabling...
Nov 27 10:49:27 myhost.localdomain kwin_x11[1358]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 30301, resource id: 132120583, major code: 15 (QueryTree), minor code: 0
Nov 27 10:49:27 myhost.localdomain kwin_x11[1358]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 30399, resource id: 132120610, major code: 18 (ChangeProperty), minor code: 0
Nov 27 10:49:36 myhost.localdomain plasmashell[1371]: QQuickItem::stackAfter: Cannot stack StatusNotifierItem_QMLTYPE_296(0x561198f53350, parent=0x561196d7cad0, geometry=0,0 0x0) after StatusNotifierItem_QMLTYPE_296(0x5611988c5310), w>
Nov 27 10:49:37 myhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=suc>
Nov 27 10:50:16 myhost.localdomain systemd[1]: Starting system activity accounting tool...
Nov 27 10:50:16 myhost.localdomain systemd[1]: Started system activity accounting tool.
Nov 27 10:50:16 myhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sysstat-collect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=>
Nov 27 10:50:16 myhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sysstat-collect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?>
Nov 27 10:50:41 myhost.localdomain plasmashell[1371]: kde.dataengine.notifications`: Notification to send to backend contains invalid XML:  "Opening and ending tag mismatch." line 1 col 128
Nov 27 10:50:41 myhost.localdomain plasmashell[1371]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:113: ReferenceError: appIcon is not defined
Nov 27 10:50:44 myhost.localdomain kwin_x11[1358]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 58964, resource id: 127926292, major code: 15 (QueryTree), minor code: 0
Nov 27 10:50:44 myhost.localdomain plasmashell[1371]: QQuickItem::stackAfter: Cannot stack StatusNotifierItem_QMLTYPE_296(0x561198821f80, parent=0x561196d7cad0, geometry=0,0 0x0) after StatusNotifierItem_QMLTYPE_296(0x561198f53350), w>
Nov 27 10:50:44 myhost.localdomain plasmashell[1371]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:113: ReferenceError: appIcon is not defined

Comment 11 Talha Khan 2018-11-27 17:57:33 UTC

I also tried reporting the bug but could not get a backtrace. The message is:
The debugger has quit unexpectedly.

The report is as follows:

Application: akregator (5.9.3)

Qt Version: 5.11.1
Frameworks Version: 5.52.0
Operating System: Linux 4.19.3-300.fc29.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
<In detail, tell us what you were doing  when the application crashed.>

-- Backtrace:
A useful backtrace could not be generated

Report to https://bugs.kde.org/

Comment 12 Talha Khan 2018-12-04 21:30:15 UTC

Created attachment 1511471 [details]
akregator gdb backtrace

I used GDB as directed here (https://fedoraproject.org/wiki/StackTraces) to obtain a stack trace. Hopefully this helps.

Comment 13 Rex Dieter 2018-12-07 14:30:58 UTC

Possible the symptoms match this upstream bug,
https://bugs.kde.org/show_bug.cgi?id=371511

Comment 14 Rex Dieter 2019-03-03 14:30:48 UTC

Reportedly fixed in 18.12.x release of akregator

Comment 15 Fedora Update System 2019-03-03 14:32:33 UTC

akonadi-calendar-tools-18.12.2-1.fc29 akonadi-import-wizard-18.12.2-1.fc29 akonadiconsole-18.12.2-1.fc29 akregator-18.12.2-1.fc29 grantlee-editor-18.12.2-1.fc29 kaddressbook-18.12.2-1.fc29 kalarm-18.12.2-1.fc29 kdepim-addons-18.12.2-1.fc29 kdepim-apps-libs-18.12.2-1.fc29 kdepim-runtime-18.12.2-1.fc29 kf5-akonadi-calendar-18.12.2-1.fc29 kf5-akonadi-contacts-18.12.2-1.fc29 kf5-akonadi-mime-18.12.2-1.fc29 kf5-akonadi-notes-18.12.2-1.fc29 kf5-akonadi-search-18.12.2-1.fc29 kf5-akonadi-server-18.12.2-1.fc29 kf5-calendarsupport-18.12.2-1.fc29 kf5-eventviews-18.12.2-1.fc29 kf5-grantleetheme-18.12.2-1.fc29 kf5-incidenceeditor-18.12.2-1.fc29 kf5-kalarmcal-18.12.2-1.fc29 kf5-kblog-18.12.2-1.fc29 kf5-kcalendarcore-18.12.2-1.fc29 kf5-kcalendarutils-18.12.2-1.fc29 kf5-kcontacts-18.12.2-1.fc29 kf5-kdav-18.12.2-1.fc29 kf5-kidentitymanagement-18.12.2-1.fc29 kf5-kimap-18.12.2-1.fc29 kf5-kitinerary-18.12.2-1.fc29 kf5-kldap-18.12.2-1.fc29 kf5-kmailtransport-18.12.2-1.fc29 kf5-kmbox-18.12.2-1.fc29 kf5-kmime-18.12.2-1.fc29 kf5-kontactinterface-18.12.2-1.fc29 kf5-kpimtextedit-18.12.2-1.fc29 kf5-kpkpass-18.12.2-1.fc29 kf5-ksmtp-18.12.2-1.fc29 kf5-ktnef-18.12.2-1.fc29 kf5-libgravatar-18.12.2-1.fc29 kf5-libkdepim-18.12.2-1.fc29 kf5-libkleo-18.12.2-1.fc29 kf5-libksieve-18.12.2-1.fc29 kf5-mailcommon-18.12.2-1.fc29 kf5-mailimporter-18.12.2-1.fc29 kf5-messagelib-18.12.2-1.fc29 kf5-pimcommon-18.12.2-1.fc29 kleopatra-18.12.2-1.fc29 kmail-18.12.2-1.fc29 kmail-account-wizard-18.12.2-1.fc29 knotes-18.12.2-1.fc29 kontact-18.12.2-1.fc29 korganizer-18.12.2-1.fc29 libkgapi-18.12.2-1.fc29 mbox-importer-18.12.2-1.fc29 pim-data-exporter-18.12.2-1.fc29 pim-sieve-editor-18.12.2-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-366290d49d

Comment 16 Fedora Update System 2019-03-05 15:20:52 UTC

akonadi-calendar-tools-18.12.2-1.fc29, akonadi-import-wizard-18.12.2-1.fc29, akonadiconsole-18.12.2-1.fc29, akregator-18.12.2-1.fc29, grantlee-editor-18.12.2-1.fc29, kaddressbook-18.12.2-1.fc29, kalarm-18.12.2-1.fc29, kdepim-addons-18.12.2-1.fc29, kdepim-apps-libs-18.12.2-1.fc29, kdepim-runtime-18.12.2-1.fc29, kf5-akonadi-calendar-18.12.2-1.fc29, kf5-akonadi-contacts-18.12.2-1.fc29, kf5-akonadi-mime-18.12.2-1.fc29, kf5-akonadi-notes-18.12.2-1.fc29, kf5-akonadi-search-18.12.2-1.fc29, kf5-akonadi-server-18.12.2-1.fc29, kf5-calendarsupport-18.12.2-1.fc29, kf5-eventviews-18.12.2-1.fc29, kf5-grantleetheme-18.12.2-1.fc29, kf5-incidenceeditor-18.12.2-1.fc29, kf5-kalarmcal-18.12.2-1.fc29, kf5-kblog-18.12.2-1.fc29, kf5-kcalendarcore-18.12.2-1.fc29, kf5-kcalendarutils-18.12.2-1.fc29, kf5-kcontacts-18.12.2-1.fc29, kf5-kdav-18.12.2-1.fc29, kf5-kidentitymanagement-18.12.2-1.fc29, kf5-kimap-18.12.2-1.fc29, kf5-kitinerary-18.12.2-1.fc29, kf5-kldap-18.12.2-1.fc29, kf5-kmailtransport-18.12.2-1.fc29, kf5-kmbox-18.12.2-1.fc29, kf5-kmime-18.12.2-1.fc29, kf5-kontactinterface-18.12.2-1.fc29, kf5-kpimtextedit-18.12.2-1.fc29, kf5-kpkpass-18.12.2-1.fc29, kf5-ksmtp-18.12.2-1.fc29, kf5-ktnef-18.12.2-1.fc29, kf5-libgravatar-18.12.2-1.fc29, kf5-libkdepim-18.12.2-1.fc29, kf5-libkleo-18.12.2-1.fc29, kf5-libksieve-18.12.2-1.fc29, kf5-mailcommon-18.12.2-1.fc29, kf5-mailimporter-18.12.2-1.fc29, kf5-messagelib-18.12.2-1.fc29, kf5-pimcommon-18.12.2-1.fc29, kleopatra-18.12.2-1.fc29, kmail-18.12.2-1.fc29, kmail-account-wizard-18.12.2-1.fc29, knotes-18.12.2-1.fc29, kontact-18.12.2-1.fc29, korganizer-18.12.2-1.fc29, libkgapi-18.12.2-1.fc29, mbox-importer-18.12.2-1.fc29, pim-data-exporter-18.12.2-1.fc29, pim-sieve-editor-18.12.2-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.

Comment 17 Ben Cotton 2019-10-31 19:51:37 UTC

This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 18 Ben Cotton 2019-11-27 21:21:04 UTC

Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.