🖨️
-
️ My new printer stopped working under #LinuxMint the other day. Re-adding it resulted in a general error message.
Finally found the solution:
In the printer's "location" field, I had specified "Mein Büro" ("My office" in German). And Cups does not like umlauts in that field.
After removing the "ü", the printer worked.
Maybe this information will be helpful to someone, at some point.
@duke_of_germany love these kinds of nonsensical bugs thatll leave u pullin out ur hair
-
️
My new printer stopped working under #LinuxMint the other day. Re-adding it resulted in a general error message.
Finally found the solution:
In the printer's "location" field, I had specified "Mein Büro" ("My office" in German). And Cups does not like umlauts in that field.
After removing the "ü", the printer worked.
Maybe this information will be helpful to someone, at some point.
Herzog von Deutschland,
that is a bug. Especially these comment fields, description and location, should accept UTF-8 text, as many people want to fill them in their language, even worse for those who speak Greek, Hindi, ... (In German one can still work around with "Mein Buero", but this also only if one gets a clear error message so that one knows that the problem is the non-ASCII character in this field).
So please report a bug on
https://github.com/OpenPrinting/cups/issues/ -
Und wenn der Bug dann gefixed ist, dann kannst du natürlich auch "Scheiße" in das "Description"-Feld schreiben, aber dann solttest Du wirklich darüber nachdenken, ob Du dir besser einen anderen Drucker (z. B. mit weniger Cartridge-DRM) anschaffen solltest ...
-
@duke_of_germany keine cüps!
@dbat
Kein ÜTF-8!
@duke_of_germany -
@duke_of_germany keine cüps!
CUPS ist ja "Common Unix Printing System". Damit ist das Problem hier, dass die Amerikaner den Deutschen beim Betriebssystem-erstellen zuvor gekommen sind. Sonst hätte es Ünix geheissen und dann hätten wir auch CÜPS und es wäre von Anfang an auch an UTF-8 für Description und Location gedacht worden.
Beim drucken von Textdateien wurde übrigens schon viele Jahre UTF-8 unterstützt.
-
️
My new printer stopped working under #LinuxMint the other day. Re-adding it resulted in a general error message.
Finally found the solution:
In the printer's "location" field, I had specified "Mein Büro" ("My office" in German). And Cups does not like umlauts in that field.
After removing the "ü", the printer worked.
Maybe this information will be helpful to someone, at some point.
@duke_of_germany Way back in 2013, Fedora had a release codenamed “Schrödinger's Cat”, which led to a *TON* of incidental code fixes for stuff that broke in the presence of umlauts. Clearly there is still work to do.
-
️
My new printer stopped working under #LinuxMint the other day. Re-adding it resulted in a general error message.
Finally found the solution:
In the printer's "location" field, I had specified "Mein Büro" ("My office" in German). And Cups does not like umlauts in that field.
After removing the "ü", the printer worked.
Maybe this information will be helpful to someone, at some point.
@duke_of_germany
Man schreibt das ja auch Bureau!
-
@duke_of_germany Das ist so lustig!! Wie hast du die Lösung gefunden- es scheint so random
@daniel @duke_of_germany
Das Umlaute-Problem sollte man immer auf dem Schirm haben. Bin geläutert seit dem Bug bei der LUKS-Verschlüsselung von Silverblue; im Installer mit auf deutsch eingestellter Tastatur eingerichtet, keine Chance beim Neustart, weil im Gegensatz zu Fedora Workstation die englischsprachige Eingabe fest aktiviert war und sich nicht ändern ließ.
Workaround unpraktisch, mittlerweile aber gefixt. Verwende in Passwort-Phrasen seither trotzdem nur noch ue etc. 
-
@itisiboller @duke_of_germany schei?e encoding
-
Und wenn der Bug dann gefixed ist, dann kannst du natürlich auch "Scheiße" in das "Description"-Feld schreiben, aber dann solttest Du wirklich darüber nachdenken, ob Du dir besser einen anderen Drucker (z. B. mit weniger Cartridge-DRM) anschaffen solltest ...
-
️
My new printer stopped working under #LinuxMint the other day. Re-adding it resulted in a general error message.
Finally found the solution:
In the printer's "location" field, I had specified "Mein Büro" ("My office" in German). And Cups does not like umlauts in that field.
After removing the "ü", the printer worked.
Maybe this information will be helpful to someone, at some point.
@duke_of_germany Apparently, processing Ünicode is hard.
-
️
My new printer stopped working under #LinuxMint the other day. Re-adding it resulted in a general error message.
Finally found the solution:
In the printer's "location" field, I had specified "Mein Büro" ("My office" in German). And Cups does not like umlauts in that field.
After removing the "ü", the printer worked.
Maybe this information will be helpful to someone, at some point.
@duke_of_germany It pisses me off to no end that in 2026 stuff like this still happens. And it's not just Linux, I've had work-related Windows and Mac incidents just like this.
-
️
My new printer stopped working under #LinuxMint the other day. Re-adding it resulted in a general error message.
Finally found the solution:
In the printer's "location" field, I had specified "Mein Büro" ("My office" in German). And Cups does not like umlauts in that field.
After removing the "ü", the printer worked.
Maybe this information will be helpful to someone, at some point.
@duke_of_germany I suspect it's because it's not a professional printer, that's why it works with "Mein Zuhause" in that field.
-
R relay@relay.mycrowd.ca shared this topic
-
️
My new printer stopped working under #LinuxMint the other day. Re-adding it resulted in a general error message.
Finally found the solution:
In the printer's "location" field, I had specified "Mein Büro" ("My office" in German). And Cups does not like umlauts in that field.
After removing the "ü", the printer worked.
Maybe this information will be helpful to someone, at some point.
@duke_of_germany FFS. Unicode and UTF-8 have been around for how many decades??
-
R relay@relay.publicsquare.global shared this topic
️
