We use 'git reset' to move back in time. I don't know whether a git reset deletes files or only moves to where HEAD is being pointed.

I don't know how this is supposed to work. I ran 'git reset --hard'. When I viewed the top level with git log, the newest date was April 10. Seemed okay to me. After my previous two builds and testing I wondered whether that truly reset the source files. I changed to the tdebase directory and again ran git log. The most recent commit was from a few days ago. So I did a git reset there too and in tdelibs.

Try this: git reset --hard HEAD git checkout <hash> That should do the trick!

Execute those two commands from within each module, e.g.: cd tdebase/ git reset --hard HEAD git checkout <hash> <build/install>

kedit is an orphan text editor, installed as part of tdeutils and does not use any k*parts of any kind. Off topic, I wish we would update kedit to use the same shortcuts and dialogs and nominal behavior to provide consistency. Sounds like an enhancement request. :-) I have backups but they won't help us. :-) I did not start building Slackware Current until a few days ago. The package backups I have all are for Slackware 13.1 32-bit. The kwrite problem I witness here never surfaced in my 13.1 (or 13.37) builds. Only Slackware Current is affected. We use 'git reset' to move back in time. I don't know whether a git reset deletes files or only moves to where HEAD is being pointed. Would one of the GIT gurus help with this? Yet even if git reset deletes files then that is a nominal price to pay to resolve this problem. After the problem is narrowed we resync to restore up to date. Start at 4/4 to bisect the alleged bad time frame. Both kate and kwrite are part of the core packages. To save time, build only the core packages (TQt3->tdebase), install and run quick tests. For me, all I need do is start kwrite and move the cursor a few lines. :-) Using git reset requires the commit hash number. Use the Commit Patches web page (or 'git log') to determine the last commit on a desired date. The last commit for 4/4 was 9e172fa7a1e93cc77e09616eb793b823d29ebaec. The syntax is like this: cd $GIT_DIR_TOP_LEVEL git reset --hard 9e172fa7a1e93cc77e09616eb793b823d29ebaec git log The 'git log' command is needed only to verify the reset took place. If the kwrite/kate problem perists then continue with another git reset at 4/1 and repeat. After determining the problem occurs with commits for a specific day, then start bisecting the commits for that day. I'll start with the last commit for 4/10 (0a4d85561846548aab970994d2787c4eaa14bba7) to confirm your proposed time period. If I can't confirm then the story gets more complicated. If I can't confirm the problem with that reset then I will start bisecting commits in the other direction. Considering that building the core packages is about a 1 to 1-1/2 hours, this could take a while. This has to be a clean rebuild each time. Don't try to mix and match. Uninstall everything, build, test, uninstall everything, build, test.... With that said, if this is a gcc 4.7 conflict and not a specific patch commit, then this test plan is unlikely to expose anything. That is, the problem should persist regardless of how far back we go in time. That in itself will help some, although the gcc gurus will have to help. We do this independently. That way hopefully we arrive at the same conclusion. Darrell ---------------------------------------------------------------------

Seems there is indeed a problem before that date. Ignore my previous post as your time frame seems credible again. :-) Tim, The problem I see with kwrite is I can't scroll through to the end of a basic text file. The file I am using is 232 lines long. Hardly a mammoth. Yet whether I scroll one line at a time with the Down arrow key, use Page Down, or use Ctrl-End, kwrite freezes and stops responding. At this point I'm not set up to do backtraces. I don't see any classic crash anyway. The app just freezes. Curiously, kate does not do this. I tested kate with the Memory Usage buffer set at 16 and at 512 (maximum). No difference. Kate behaves for me. Darrell

I have a lot of things outside the project suddenly pulling at me, which doesn't help and certainly added to today's stress. The ebb and flow of life. The best approach is to take care of those things. I don't expect to help for a few days but I'll keep tabs on the emails as best I can.

I'm sure this won't be the last time we need to reset the sources for debugging purposes. If you get through this ordeal without losing your mind then perhaps a short wiki how-to would be nice. :-)

I'll just post tqtinterface -> tdebase to cut down the size. tqt3 is a bit large for my little connection. (tdelibs and tdebase are big enough) If needed, I can post tqt3, let me know. This will save the git download time and worry about submodule updates, etc... (~8 min per date to download)