Summary: | crash when view difference is selected after file has changed on disk | ||
---|---|---|---|
Product: | [Applications] kate | Reporter: | BORGULYA Gábor <bugs2> |
Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
BORGULYA Gábor
2005-06-16 21:42:24 UTC
KILE crashes in the same way. The KDE crash handler does not get activated. I wonder why I have not seen a report in bugs.g.o... Can't reproduce. This only happens if you don't have kompare installed (emerge kompare helps on gentoo). And yeah, I don't think it produces a signal, it just quits kde horizon ath cx, Thank you for the tip. However, kompare seems to be already emerged. Carsten, Do you mean that I should have filed this bug report in bugs.gentoo.org? Or I still should? >This only happens if you don't have kompare installed (emerge kompare helps on gentoo). Well, I tried that before and no - a kwrite window opened, showing a unified diff. Borgulya: There are lot of ways you can screw a Gentoo installation, when you do not know exactly what you do. When you are not sure, if a problem relates to KDE itself or your local Gentoo installation, please file bugs at bugs.g.o. We may point you here, but most often the problem is local to the users box (mixed libraries compiled with gcc-3.3 and 3.4 or whatever). And that's nothing kde.org developers want to have anything to do with. >Do you mean that I should have filed this bug report in bugs.gentoo.org? Or I still should? Your first try should be asking for help in forums.g.o or the gentoo-user mailinglist then bugs.g.o, unless you're sure it needs to be fixed upstream. I installed KDE 3.4.1 the following simple way: #ACCEPT_KEYWORDS="~x86" use="debug" emerge kde-meta kile That is why it did not come to my mind that the problem could be gentoo-related. I don't think I screwed my Gentoo installation. Anyway, thanks for clarifying that this bug is a Gentoo bug. And thank you for bringing my attention to the Gentoo forums. k, than away with it ;) |