Version: Unbekannt (using KDE 3.3.0, Arch Linux) Compiler: gcc version 3.4.1 OS: Linux (i686) release 2.6.8.1 Open kcmnotify, go to "playback options", enable "external player" and type into the textfield: aplay. As soon as I type the p, kcmshell prints "getötet" (i18n(killed)) to the screen and exits immediately. Something similar happened while I was saving a file in umbrello. File->Save As->browsed through some pathes->finally wanted to type in a filename and after a few letters the program just disappeared without kcrash starting.
I was able to reproduce the crash in umbrello one or two times after that, maybe it has something to do with the folders I went in containing umlauts.
I can successfully open and save files in folders with characters than contain umlauts using Umbrello.
me too, I have no idea if that caused it, it works in other folders that contain umlauts but in this specific one it didn't. Am Mittwoch, 8. September 2004 21:23 schrieb Jonathan Riddell: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=88824 > > > > > ------- Additional Comments From jr jriddell org 2004-09-08 21:23 ------- > I can successfully open and save files in folders with characters than > contain umlauts using Umbrello.
Can you show the "ls -al" output of the directory in question?
Cant reproduce with 3.3.2, Im not sure if I am trying in the right folder, so the problem may still exist. I mark as RESOLVED until/if it happens again.
I have also found this problem in the save as or open dialog of Kate and Kwrite. Konqueror also exhibits the problem when trying to save a page. After a variable number of letters typed the whole application crashs. This is both with KDE 3.3.2 and 3.4.1 under Gentoo. If started from konsole, kwrite and konqueror throw a message "Killed" after crashing, but Kate does not. The crash handler never appears.
These problems started after an update for qt, xorg and glibc. I reverted all the three of them to check which was the responsible. Finally, it turns out that it was glibc 2.3.5 and everything works fine in stable Gentoo with glibc-2.3.4.20040808-r1 and kde 3.4.1