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
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ronald van Haren (pressh)
Andrea Scarpino (BaSh)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

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.
   log.txt (202.6 KiB)
This task depends upon

Closed by  Ronald van Haren (pressh)
Thursday, 05 June 2014, 14:13 GMT
Reason for closing:  Not a bug
Comment by Andreas Radke (AndyRTR) - Tuesday, 03 June 2014, 20:16 GMT
Please downgrade libxcursor to see if this is a duplicate of  FS#40658 .
Comment by cfr (cfr42) - Tuesday, 03 June 2014, 21:56 GMT
Thanks. I downgraded libxcursor and rebooted. Unfortunately, that doesn't help so I don't think it is a duplicate. I also rebuilt the only plugin I'm using which is not from the official repos (klatexformula) but that has not helped either. I am still getting essentially the same segmentation fault regardless.
Comment by Ronald van Haren (pressh) - Wednesday, 04 June 2014, 17:48 GMT
Did you find a reliable way to replicate this? I can't seem to get it crash in the first few minutes of fiddling around, but I'm not sure in what time frame it crashes for you?

Are you sure the crashes are related to the latest update you did, and did not happen before?

Anybody else able to replicate this?
Comment by cfr (cfr42) - Wednesday, 04 June 2014, 18:16 GMT
I'm sure they did not happen before. I'm not sure if it was that particular update. I restarted my machine since the kernel had been updated. So it might be an update from the previous few days which only started to affect things following reboot. That's all I can think. Somebody on the thread I linked reported crashes beginning following update at the end of last week which made me assume it was a bug. I'm going to reinvestigate my config. Maybe the update doesn't like something in my config. (I kind of went through this before but I was not 100% thorough.)
Comment by cfr (cfr42) - Wednesday, 04 June 2014, 22:03 GMT
So I tried removing kilerc completely and starting fresh. This worked fine while I just configured Kile but as soon as I edited a file, I got the segmentation fault again.

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'.
Comment by cfr (cfr42) - Wednesday, 04 June 2014, 22:25 GMT
I am starting to suspect the one plugin I use which is not from the repos. I rebuilt this but I am still suspicious. I managed to generate some other console output by eliminating my config and opening kile passing a filename. The output from just before the crash mentions KLFKtePluginView. Searching the net doesn't turn up anything but the 'KLF' is suggestive of KLaTeXFormula. I'm currently testing this theory.

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.
Comment by cfr (cfr42) - Thursday, 05 June 2014, 14:12 GMT
Apologies but I think this bug report is erroneous. I stripped everything back, uninstalled KLaTeXFormula and so far, I seem able to edit in Kile without causing crashes. I'm sorry for generating unnecessary noise.

Loading...