FS#40665 - [kile] (and maybe Kate) reliably seg faulting following latest updates to stable (2014-06-03)
Attached to Project:
Arch Linux
Opened by cfr (cfr42) - Tuesday, 03 June 2014, 17:24 GMT
Last edited by Ronald van Haren (pressh) - Thursday, 05 June 2014, 14:13 GMT
Opened by cfr (cfr42) - Tuesday, 03 June 2014, 17:24 GMT
Last edited by Ronald van Haren (pressh) - Thursday, 05 June 2014, 14:13 GMT
|
Details
Description:
Following system update today (2014-06-03), Kile reliably crashes with a segmentation fault. What triggers the crash is somewhat less reliable. Initially just starting the application was enough. I fiddled with kilerc to get around this but the crashes persist when editing files or when trying to recover data following a crash. Sample 'Developer information' from Kile (attached) ['username' and 'computername' are substituted for my actual user name and computer name in the above.] Additional info: possibly related forum thread: https://bbs.archlinux.org/viewtopic.php?id=182319 updated just prior to crash (but I also restarted due to kernel upgrade): ffmpeg (1:2.2.2-3 -> 1:2.2.3-1) gdk-pixbuf2 (2.30.7-1 -> 2.30.8-1) gnome-icon-theme-symbolic (3.12.0-1 -> 3.12.0-2) gnome-icon-theme (3.12.0-1 -> 3.12.0-2) libxcursor (1.1.14-1 -> 1.1.14-2) linux (3.14.4-1 -> 3.14.5-1) linux-docs (3.14.4-1 -> 3.14.5-1) linux-headers (3.14.4-1 -> 3.14.5-1) Steps to reproduce: Update and try to use Kile as usual. |
This task depends upon
FS#40658.Are you sure the crashes are related to the latest update you did, and did not happen before?
Anybody else able to replicate this?
So then I tried scrapping kilerc again. This time, all I did was open Kile, OK the regeneration of tools dialogue and dismiss the tips-on-startup. Then I opened the same project and tried typing in the same place. Again, segmentation fault. (Although other things trigger it, typing in this spot in this file in this project seems pretty reliable. However, I worked on this file in Kile just fine until the crashes started and I can edit it fine in other editors. Also, it happens with editing other files, too. Just this is the one I was working on so this is the one I'm most familiar with the triggers for the crashes. It does seem there is something about the context in the file although I've no idea what or why Kile should care about the contents. That is, typing in certain places in the file seems to immediately cause a seg fault whereas typing somewhere else, I might be able to write a whole sentence before seeing a crash. The file is not large (~13K), is a regular .tex file created and edited in Kile in UTF-8 encoding. It is just plain text. file describes it as a 'LaTeX 2e document, ASCII text, with very long lines'.
Thanks for turning my posted code into an attachment. But please note that it actually contains two things: developer info from the crash reporter and sample console output. So it should probably be two attachments.