Bug#780588: kate: crash when I try to open/save a .bash/.sh file
Hey,
I can't reproduce the issue for bash/sh files unter 4.14.2 . From your
backtrace I would say, you have brocken syntax-highlight for these kind of
files. Please have a look at the syntax highlight settings.
Regads,
sandro
--
Am Montag, 16. März 2015, 12:47:46 schrieb Pablo:
> Package: kate
> Version: 4:4.8.4-1
> Severity: important
>
> Dear Maintainer,
>
> * What led up to the situation?
> Bash scripting.
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
> * What was the outcome of this action?
> * What outcome did you expect instead?
>
> As the subject says, Kate crash when I try to save/open any file with .bash
> or .sh extension. Kwrite doesn't show this issue. gdb generates this trough
> the KDE assitant: http://pastebin.com/ZXduj7uj
>
>
> -- System Information:
> Debian Release: 7.8
> APT prefers stable-updates
> APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
> Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages kate depends on:
> ii kate-data 4:4.8.4-1
> ii katepart 4:4.8.4-1
> ii kde-runtime 4:4.8.4-2
> ii libc6 2.13-38+deb7u8
> ii libkateinterfaces4 4:4.8.4-1
> ii libkdecore5 4:4.8.4-4+deb7u1
> ii libkdeui5 4:4.8.4-4+deb7u1
> ii libkfile4 4:4.8.4-4+deb7u1
> ii libkio5 4:4.8.4-4+deb7u1
> ii libknewstuff2-4 4:4.8.4-4+deb7u1
> ii libknewstuff3-4 4:4.8.4-4+deb7u1
> ii libkparts4 4:4.8.4-4+deb7u1
> ii libktexteditor4 4:4.8.4-4+deb7u1
> ii libplasma3 4:4.8.4-4+deb7u1
> ii libqt4-dbus 4:4.8.2+dfsg-11
> ii libqt4-qt3support 4:4.8.2+dfsg-11
> ii libqt4-sql 4:4.8.2+dfsg-11
> ii libqt4-xml 4:4.8.2+dfsg-11
> ii libqtcore4 4:4.8.2+dfsg-11
> ii libqtgui4 4:4.8.2+dfsg-11
> ii libstdc++6 4.7.2-5
>
> kate recommends no packages.
>
> Versions of packages kate suggests:
> ii aspell 0.60.7~20110707-1
> ii ispell 3.3.02-6
> ii khelpcenter4 4:4.8.4-2
> ii konsole 4:4.8.4-2
>
> -- no debconf information
Reply to: