MX Linux Forum

No, it does not crash. It simply discards everything behind the first of those characters. Check the amount of lines you can see in QSI and in a text editor.


Since the early days of UNIX, the null byte (0x00) was used to represent the end of a string. Because UNIX (and the Linux kernel) is ...

I also managed to copy the part of the syslog that contains those null characters, please find it attached as well.

By the way, something partially connected for the wish list. It would be great if QSI could translate the Escape-sequences for colours to coloured text as well (such as the ...

I tried you log.file you posted in #1 it doesn't crash. OK some "chars" like "null"-char/bytes are not properly filtered.
But no crash .

No, it does not crash. It simply discards everything behind the first of those characters. Check the amount of lines you can see in QSI and in a text ...

AFAIR shell scripts ought to call "their" shell in the first line anyway (e.g. "#!/bin/bash"), or am I mistaken there? If you check the system scripts in /etc/init.d you'll see that most of them begin #! /bin/sh or #! /bin/sh -e
They expect /bin/sh to be set to a Posix compliant shell. It ...

Apart from boot.log I found:

- user.log
- opensnitchd.log (Opensnitch is however nothing you provide, thus I see it als "for sake of completeness only" ;-) )
- syslog
- kern.log
- /cups/access_log

I think that's it - opening each log file in the same instance of Kate lets you search for the ...

Apart from boot.log I found:

- user.log
- opensnitchd.log (Opensnitch is however nothing you provide, thus I see it als "for sake of completeness only" ;-) )
- syslog
- kern.log
- /cups/access_log

I think that's it - opening each log file in the same instance of Kate lets you search for the ...

if it helps, here is a list of all the occurrences I found so far:

boot.log: one between the text "Setting sensors limits..." and "done", one between "Starting cgroup management daemon: cgmanager" and "Setting up console font and keymap...done.", one between "Starting Web Services Dynamic ...

I wonder if the issue is using fish as your default shell instead of bash or dash.
Fish isn't fully Posix compliant so some system shell scripts may not be running as intended.


Hm, does not seem so... I switched the default shell back to bash by doing a chsh -s /usr/bin/bash for both my user ...

I wonder if the issue is using fish as your default shell instead of bash or dash.
Fish isn't fully Posix compliant so some system shell scripts may not be running as intended.


Thanks for pointing that out! Let me try switching system standard back to bash, reboot a couple of times and come ...

Apart from boot.log I found:

- user.log
- opensnitchd.log (Opensnitch is however nothing you provide, thus I see it als "for sake of completeness only" ;-) )
- syslog
- kern.log
- /cups/access_log

I think that's it - opening each log file in the same instance of Kate lets you search for the ...