[Bug 1134688] New: Bug with German Umlauts on desktop
http://bugzilla.opensuse.org/show_bug.cgi?id=1134688 Bug ID: 1134688 Summary: Bug with German Umlauts on desktop Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: 64bit OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs@opensuse.org Reporter: office@hantsch.co.at QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I use openSUSE Leap 15.0 with KDE/Plasma5. The same problem exists also on openSuSE 42.x My system wide locale settings are: de_DE@euro (German, no UTF8). All files/folders (their names) are correctly encoded in iso-8859-1. Since Plasma5 I experience the following mis-behavior, while this smoothly worked on KDE4 (openSuSE 13.x): I am able to open Dolphin. Inside Dolphin I can navigate without any problem into folders having German Umlauts in their names. I also can click a file with German Umlauts in its name. I also can copy/paste and/or drag/drop such files/folders from Dolphin directly onto the desktop. Everything is fine here. I am also able to right-click such file/folder on the desktop to rename it (this also works as it should). When trying to click such file/folder on the desktop (to open it), I get an error: (translated German->English by me): "This command cannot be executed. The file or folder <.....> does not exist" Surprisingly the correct filename is showing up in <....>! As an example, a testing filename is: /home/rainer/Desktop/miniLÖT-Deckel.pdf (notice the "Ö" inside the file name. When renaming the file (right-click -> rename) to i.e. miniLOeT-Deckel.pdf, I am able to open the file afterwards. This happens with any kind of file/folder (also symlinks, etc..., even over NFS mounts). converting the entire system (and also all servers) is no option. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1134688 http://bugzilla.opensuse.org/show_bug.cgi?id=1134688#c1 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at Severity|Critical |Normal --- Comment #1 from Wolfgang Bauer <wbauer@tmo.at> --- I can confirm that here, even with the latest Qt5/Plasma/KF5 versions. But, it is in no way "Critical" IMO... UTF is the norm since years, so this is rather an edge case, and it only affects the desktop as you write. Also, right-clicking and "Open with xxx" works fine here too, so you could use that as workaround. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1134688 http://bugzilla.opensuse.org/show_bug.cgi?id=1134688#c2 --- Comment #2 from Rainer Hantsch <office@hantsch.co.at> --- Well, imagine the following: You have servers with many TBytes of data. Everything iso-8859-1 based. And you use over years symlinks to several points in this data structure, everything is fine. Then you get "forced" to use a new Leap 15 because new software is not working on openSuSE 13.2 any more. You install a new OS and re-use the /home path to not loose all desktop settings, and voila, a problem here, a problem there, ... Finally you end up with creating symlinks from important folders with German Umlauts in their name -> names with translated Umlauts (Ü -> Ue), only to get it somehow working again. -> NOT CRITICAL? - I see it different, it stops me from productively working About "norm"... You should view it from this point: KDE/Plasma is literally a GUEST on the underlaying OS. It is a huge program collection, running on the OS, means, I can use the OS also without KDE/Plasma. And this OS _perfectly_ supports many different encodings, one of them is iso-8859-1. So the logical consequence is: Declaring UFT8 as "norm" is a bit keen. In best case I will accept that it is _ANOTHER_ encoding in the long line of others. So it also has to be able to fully support other encodings, too. It is ok, if it internally only works with UTF8. But it definitely has to support any encoding of the underlaying OS, when it accesses something there. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1134688 http://bugzilla.opensuse.org/show_bug.cgi?id=1134688#c3 Rainer Hantsch <office@hantsch.co.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Leap 15.0 |Leap 15.2 --- Comment #3 from Rainer Hantsch <office@hantsch.co.at> --- I need to updatemy meanwhile 2 years old bug report. Meanwhile it is openSUSE 15.2 (2 releases later). Talking to people at #kde, this bug IS MEANWHILE FIXED by KDE people, so it is now on openSUSE to roll out the fixed version of KDE/Plasma. In Leap 15.2 the situation became even harder. While in 15.0 and 15.1 only the Desktop itself was not working properly, in 15.2 also Dolphin causes same troubles. Problem description: The entire OS is configured to run with locales de_DE@euro This is necessary because most systems cooperating with my servers, are microcontroller systems, not able to support UTF-8. This also includes development systems I use for them. -> So it is lots better to run the entire system on iso-8859-15. When a file with German Umlauts in its filename is stored on Desktop, it is correctly displayed. But when I try to access it, I always get an "File does not exist" error. The funny thing: Even in this error message the filename is correctly displayed! Now, with Leap 15.2, the situation became even worser: While it was possible in Leap 15.1 to open such file by "open-with" or by navigating to it using Dolphin and then click it in Dophin, even this does not work any more in Leap 15.2 Please make the fixed version of KDE/Plasma available in Online Updates of Leap 15.2. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1134688 http://bugzilla.opensuse.org/show_bug.cgi?id=1134688#c4 Fabian Vogt <fabian@ritter-vogt.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fabian@ritter-vogt.de, | |office@hantsch.co.at Flags| |needinfo?(office@hantsch.co | |.at) --- Comment #4 from Fabian Vogt <fabian@ritter-vogt.de> --- Please try duping to https://build.opensuse.org/package/show/home:Vogtinator:boo1134688/kio.openS..., it includes the fix for https://bugs.kde.org/show_bug.cgi?id=432406. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1134688 http://bugzilla.opensuse.org/show_bug.cgi?id=1134688#c6 --- Comment #6 from Rainer Hantsch <office@hantsch.co.at> --- Hello, Fabian Vogt. I have tried to do this upgrade in a virtual machine (to test first). Sadly I had no success, I have difficulties with how to do this "dup". Can you, please, tell me the particular steps? I do not want to break the entire KDE because I am doing something wrong. Can I add your fix as a new repository (and how)? Or how shall I do it? Thanky in advance. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1134688 http://bugzilla.opensuse.org/show_bug.cgi?id=1134688#c7 --- Comment #7 from Fabian Vogt <fabian@ritter-vogt.de> --- (In reply to Rainer Hantsch from comment #6)
Can you, please, tell me the particular steps? I do not want to break the entire KDE because I am doing something wrong.
Can I add your fix as a new repository (and how)? Or how shall I do it?
zypper ar https://download.opensuse.org/repositories/home:/Vogtinator:/boo1134688/open... boo1134688 zypper -v dup --from boo1134688 After testing or when the update is released, zypper rr boo1134688 -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com