konqueror crashed with signal 5 in g_main_context_dispatch()

[milan prask]

after few clicks konqueror crashed, it's happened many times (fault confirmed)

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: konqueror 4:16.04.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
Uname: Linux 4.8.0-19-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sun Oct 2 22:09:12 2016
ExecutablePath: /usr/bin/konqueror
InstallationDate: Installed on 2016-07-18 (75 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421)
ProcCmdline: /usr/bin/konqueror --silent
ProcEnviron:
 LANGUAGE=cs_CZ
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: kde-baseapps
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: konqueror crashed with signal 5 in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 ik_source_read_some_events.isra () from /tmp/apport_sandbox_z7ltyW/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ik_source_dispatch () from /tmp/apport_sandbox_z7ltyW/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /tmp/apport_sandbox_z7ltyW/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_iterate.isra () from /tmp/apport_sandbox_z7ltyW/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_iteration () from /tmp/apport_sandbox_z7ltyW/lib/x86_64-linux-gnu/libglib-2.0.so.0

[Marc Deslauriers (mdeslaur)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.