Application: kile (2.1.0) KDE Platform Version: 4.8.2 (4.8.2) Qt Version: 4.8.1 Operating System: Linux 3.2.0-24-generic x86_64 Distribution: Ubuntu 12.04 LTS Relevant stack trace: #6 QUrl::isEmpty (this=0x9d) at io/qurl.cpp:4278 #7 0x00000000005b3f18 in ?? () #8 0x00000000005b445f in ?? () #9 0x00000000004dd089 in _start () Reproducible: Always Steps to Reproduce: 1. Open Kile 2. Open a project (new or existing) 3. Close Kile Actual Results: Kile appears to close, but a segmentation fault 11 is caught by the crash handler. Expected Results: Kile should close silently. If I knew which debug symbols to install I would be able to provide a better report.
Additionally only project address is written to [KFileDialog Settings] Recent Files[$e]=... in ~/.kde/share/config/kilerc and no other open file and project state information is recorded. The project and its files are not re-opened when opening the next instance of Kile
Can you upgrade to Kile 2.1.2 and check whether this fixes the problem? Thanks.
Sure can you recommend a deb repository to use? On Sun, May 6, 2012 at 4:32 AM, Michel Ludwig <michel.ludwig@kdemail.net>wrote: > https://bugs.kde.org/show_bug.cgi?id=299342 > > Michel Ludwig <michel.ludwig@kdemail.net> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #2 from Michel Ludwig <michel.ludwig@kdemail.net> --- > Can you upgrade to Kile 2.1.2 and check whether this fixes the problem? > Thanks. > > -- > You are receiving this mail because: > You reported the bug. >
Unfortunately, I'm not very familiar with Ubuntu/Debian. The only thing I can suggest would be to compile Kile 2.1.2 from the source files. You can find instructions for doing so here: http://kile.sourceforge.net/help.php#compile
Will do, I might take the time to step through some breakpoints in kdevelop. On Mon, May 7, 2012 at 2:48 PM, Michel Ludwig <michel.ludwig@kdemail.net>wrote: > https://bugs.kde.org/show_bug.cgi?id=299342 > > --- Comment #4 from Michel Ludwig <michel.ludwig@kdemail.net> --- > Unfortunately, I'm not very familiar with Ubuntu/Debian. > > The only thing I can suggest would be to compile Kile 2.1.2 from the source > files. You can find instructions for doing so here: > > http://kile.sourceforge.net/help.php#compile > > -- > You are receiving this mail because: > You reported the bug. >
Hi all, I have the same experience as Aaron Sheldon. Why wait? A dev only has to create a project in kile and end kile to confirm or deny the bug. Aaron needs to set up a development environment. And his last message was from 7th of May.
(In reply to comment #6) > I have the same experience as Aaron Sheldon. > > Why wait? A dev only has to create a project in kile and end kile to confirm > or deny the bug. > > Aaron needs to set up a development environment. And his last message was > from 7th of May. Well, upgrade to 2.1.2 and you will (probably) see that the problem is gone!
After several hours of installing kile, development environments and kdev4 I finally got to testing it and the problem did not persist to level 2.1.2. I tested it from kdevelop in stead of calling the binary: I expect the result is the same. Having both a ubuntu installed kile 2.1.0 and the compiled 2.1.2, the binary might be calling the wrong libraries. For that reason I tested from kdevelop so I can be reasonably sure the environment is coherent. P.S. For the short term and on ubuntu, this is not a workaround as ubuntu only provides version 2.1.0 when you install kile. The workaround is to close the project before ending kile. People will have to do that while ubuntu moves to a newer version of kile.
uhm, the version I tested might be something other that 2.1.2. Although the initial screen flashed version 2.1 on it, the help indicates the source is version 2.9.60: so I am a little confused what version of Kile I tested. I got this version using git clone a few days ago, so it should pretty close to the current version of kile.
You tested the "master" branch which will become Kile 3 (the splash screen hasn't been updated yet). If you still want to verify that it works in the upcoming version 2.1.3, you have to do "git checkout 2.1" and then recompile Kile again. This bug report can now be closed then.