Bug 1275844

Summary: [abrt] kwrite: __kernel_vsyscall(): kwrite killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: kateAssignee: Than Ngo <than>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: jreznik, kevin, ltinkl, rdieter, rnovacek, than
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/25d9665dcb2c92a9b00a47d12e70e41f88447305
Whiteboard: abrt_hash:96ca9db31b78901aa56e9b5107cce06511fbb87b;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-27 22:49:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Adam Williamson 2015-10-27 22:47:08 UTC 
Description of problem:
Testing crash reporting while suffering from #1256456. This is an artificially induced crash, it is not a valid crash report.

Version-Release number of selected component:
kwrite-15.08.1-1.fc23

Additional info:
reporter:       libreport-2.6.2
backtrace_rating: 3
cmdline:        /bin/kwrite
crash_function: __kernel_vsyscall
executable:     /usr/bin/kwrite
global_pid:     1986
kernel:         4.2.3-300.fc23.i686
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 2 (6 frames)
 #0 __kernel_vsyscall
 #1 poll at ../sysdeps/unix/syscall-template.S:84
 #3 _xcb_conn_wait at xcb_conn.c:459
 #4 xcb_wait_for_event at xcb_in.c:648
 #5 QXcbEventReader::run at qxcbconnection.cpp:1214
 #6 QThreadPrivate::start at thread/qthread_unix.cpp:331
Comment 1 Adam Williamson 2015-10-27 22:47:13 UTC 
Created attachment 1087075 [details]
File: backtrace
Comment 2 Adam Williamson 2015-10-27 22:47:15 UTC 
Created attachment 1087076 [details]
File: cgroup
Comment 3 Adam Williamson 2015-10-27 22:47:16 UTC 
Created attachment 1087077 [details]
File: core_backtrace
Comment 4 Adam Williamson 2015-10-27 22:47:18 UTC 
Created attachment 1087078 [details]
File: dso_list
Comment 5 Adam Williamson 2015-10-27 22:47:20 UTC 
Created attachment 1087079 [details]
File: environ
Comment 6 Adam Williamson 2015-10-27 22:47:21 UTC 
Created attachment 1087080 [details]
File: limits
Comment 7 Adam Williamson 2015-10-27 22:47:23 UTC 
Created attachment 1087081 [details]
File: maps
Comment 8 Adam Williamson 2015-10-27 22:47:25 UTC 
Created attachment 1087082 [details]
File: mountinfo
Comment 9 Adam Williamson 2015-10-27 22:47:26 UTC 
Created attachment 1087083 [details]
File: open_fds
Comment 10 Adam Williamson 2015-10-27 22:47:27 UTC 
Created attachment 1087084 [details]
File: proc_pid_status
Comment 11 Adam Williamson 2015-10-27 22:47:29 UTC 
Created attachment 1087085 [details]
File: var_log_messages
Comment 12 Adam Williamson 2015-10-28 00:47:04 UTC 
Another user experienced a similar problem:

Testing crash report with updated libreport/abrt, not a genuine report.

reporter:       libreport-2.6.3
backtrace_rating: 3
cmdline:        kwrite
crash_function: __kernel_vsyscall
executable:     /usr/bin/kwrite
global_pid:     2490
kernel:         4.2.3-300.fc23.i686
package:        kwrite-15.08.1-1.fc23
reason:         kwrite killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 13 Kevin Kofler 2015-10-29 01:04:56 UTC 
Now, artificial or not, why does this kwrite crash reach ABRT to begin with? All crashes (and that includes "crashes" from something like "killall -SIGSEGV kwrite") in KDE GUI apps should be caught by DrKonqi and never get to ABRT!
Comment 14 Adam Williamson 2015-10-29 01:08:57 UTC 
I don't think I've seen a KDE crash handler in all my 23 Final testing, all crashes (including the ones we fixed as blockers) went to abrt.
Comment 15 Adam Williamson 2015-10-29 01:09:56 UTC 
neither kde-runtime-drkonqi nor plasma-workspace-drkonqi is in 23 Final RC6 KDE 32-bit live.
Comment 16 Adam Williamson 2015-10-29 01:10:42 UTC 
'drkonq' doesn't appear in comps-f23.xml.in or spin-kickstarts.
Comment 17 Kevin Kofler 2015-10-29 01:20:56 UTC 
Which sounds like a bad bug in the spin kickstarts which is going to get us flooded with bug reports that should go upstream instead. :-(

This regression was introduced when Rex Dieter removed the hard dependency on DrKonqi to allow users to work around bugs in DrKonqi that way.