Message: previous - next
Month: April 2012

Re: [trinity-devel] kwrite/kate - why is 3.5.12 not affected (help analyzing)

From: Darrell Anderson <humanreadable@...>
Date: Sun, 29 Apr 2012 13:31:53 -0700 (PDT)
>   As I work to downgrade my R14 test boxes to
> troubleshoot what caused the kate/kwrite crash, I ran into a question I would like to get
> your thoughts on. All my day-to-day boxes run fully updated Archlinux (with
> one openSuSE box), and TDE 3.5.12 as the desktop (3.5.10 on SuSE).
>   If the crash is due to an Arch update -- "They why do
> kate/kwrite continue to function normally in 3.5.12?"
>   It just strikes me that 3.5.12 would be much more
> susceptible to break due to Arch updates that R14. Would we not expect to see this same
> crash in 3.5.12 if this was due to an Arch update?
>   What say the experts? If this was Arch, wouldn't 3.5.12 have broken too?

I can't speak for the experts. I can share that today I tried to run kwrite in my fresh Trinity build in Slackware Current 32-bit. Current is not raw bleeding edge (libpng 1.4.9), but is quite recent with most apps and uses gcc 4.7.

Kwrite won't work. Kate does.

I noticed the problem when I tried to launch kwrite through Konqueror to edit a text file. Kwrite started to open, a window "frame" appeared and then toast. I could not log out. I had to use Ctrl-Alt-Delete.

I started a new session. This time I started kwrite from the mini cli. No problems. Likewise from the menu. But opening through konqueror resulted in a freeze.

When I tried opening a file from within kwrite, the moment I started performing any cursor movements, the app froze and Ctrl-Alt-Backspace to the rescue.

I exited the session. I renamed the kwriterc file and removed the ksycoca cache and started a new session. Same results.

Interestingly, I have no problems using kate. I edited several files.

I disabled the Trinity compositing just in case. No difference.

This is a not a total session freeze. I could open konsole and konqueror. I could not logout but I did not try all methods. Possibly only the Ctrl-Alt-Delete shortcut was affected.

I'm unsure where we go next. We both experience kwrite issues but not kate issues. Gcc 4.7 is common but what else? NVidia? Slackware 13.1 uses xorg-server 1.7.7, Both Slackware 13.37 and Current use xorg-server 1.9.5.

I did not perform any exhaustive testing, therefore no conclusions. This all happened in a real machine and not a virtual machine. I have not tested with Current 64-bit (I haven't yet tried to build).

I use Trinity GIT in Slackware 13.1 quite a bit and never noticed anything like this. I have not noticed this with my recent Slackware 13.37 builds, but that means little because I haven't been looking for this kind of thing. That is, I don't know whether I have even used kate/kwrite in those systems because I just started building them. I will have to test more.

The only thing I can offer at this point is kwrite is toast in Slackware Current 32-bit.

Unless somebody has some clever suspicions to narrow the debugging, this could take a long while to unfold.