|
Bugzilla – Full Text Bug Listing |
| Summary: | KDE mounting feature doesn't allow special chars | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Marcel Hilzinger <marcel> |
| Component: | KDE | Assignee: | E-mail List <kde-maintainers> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | dkukawka, lnussel, suse-beta |
| Version: | Beta 4 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Marcel Hilzinger
2006-02-21 17:04:57 UTC
The hal script that actually does the mounting does allow umlauts in theory. In practice there are several places that prevent it. I've sent a mail to the hal list with a patch to fix the script. The fdi file that sets the desired_mount_point also needs to be fixed to not filter non-ascii characters so the default mountpoint is set properly. After fixing both places the device gets mounted to a mountpoint with umlauts. KDE is not able to enter that directory via the media:/ slave though. Looks like it has some UTF-8 problem. but that won't make it into 10.1 - btw: the whatsthis help for the properties slave indicates that there is no guarantee that the wished mount point is taken. I disabled the warning on invalid mount points as I would have to duplicate the check from the hal script and that was too unsafe for my taste. mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy) mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy) mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy) Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED. In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;( |