https://bugs.kde.org/show_bug.cgi?id=364809
--- Comment #8 from Michael Weghorn <m.wegh...@posteo.de> --- I just experimented a bit. When I use an invalid locale, I can reproduce the message given in the bug report when printing: $ export LC_ALL=foobar bash: warning: setlocale: LC_ALL: cannot change locale (foobar): No such file or directory $ locale locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory LANG=en_GB.utf8 LANGUAGE=en_GB:en LC_CTYPE="foobar" LC_NUMERIC="foobar" LC_TIME="foobar" LC_COLLATE="foobar" LC_MONETARY="foobar" LC_MESSAGES="foobar" LC_PAPER="foobar" LC_NAME="foobar" LC_ADDRESS="foobar" LC_TELEPHONE="foobar" LC_MEASUREMENT="foobar" LC_IDENTIFICATION="foobar" LC_ALL=foobar $ okular kindergeldänderung3.pdf [...] lpr: Bad job-name value: "job-name": Bad name value "Ver�nderungsmitteilung" - bad UTF-8 sequence (RFC 2911 section 4.1.2). As mentioned in my previous comment, the output of the 'locale' command might be very helpful to see whether the problem you are experiencing might also have to do with incorrect locale settings. -- You are receiving this mail because: You are watching all bug changes.