Broken symlinks in /usr/share/gnome/help/user-guide/en_GB/
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-user-docs (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
In /usr/share/
$ ls -l /usr/share/
total 28
drwxr-xr-x 2 root root 12288 2011-05-26 11:39 figures
lrwxrwxrwx 1 root root 21 2011-05-26 11:39 glossary.xml -> ../en_AU/
lrwxrwxrwx 1 root root 21 2011-05-26 11:39 gosbasic.xml -> ../en_AU/
lrwxrwxrwx 1 root root 63 2011-05-26 11:39 goscustdesk.xml -> /usr/share/
lrwxrwxrwx 1 root root 28 2011-05-26 11:39 goseditmainmenu.xml -> ../en_AU/
lrwxrwxrwx 1 root root 63 2011-05-26 11:39 gosfeedback.xml -> /usr/share/
lrwxrwxrwx 1 root root 24 2011-05-26 11:39 gosnautilus.xml -> ../en_AU/
lrwxrwxrwx 1 root root 24 2011-05-26 11:39 gosoverview.xml -> ../en_AU/
lrwxrwxrwx 1 root root 21 2011-05-26 11:39 gospanel.xml -> ../en_AU/
lrwxrwxrwx 1 root root 28 2011-05-26 11:39 gosstartsession.xml -> ../en_AU/
lrwxrwxrwx 1 root root 60 2011-05-26 11:39 gostools.xml -> /usr/share/
lrwxrwxrwx 1 root root 62 2011-05-26 11:39 user-guide.xml -> /usr/share/
$ ls /usr/share/
gostools.xml user-guide.xm
A simple fix is to replace the broken links with ones to the equivalent en_AU files, as is done for the other files that don't have an en_GB version.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gnome-user-guide-en 2.30.0+
ProcVersionSign
Uname: Linux 2.6.32-35-generic i686
Architecture: i386
Date: Wed Nov 23 10:19:03 2011
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
PackageArchitec
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.utf8
SHELL=/bin/bash
SourcePackage: gnome-user-docs
Thank you for submitting this issue and helping to make Ubuntu better.
I investigated this some tonight and I believe it was fixed in Natty, when the documents package rolled to 3.0. The specific files and symlinks were replaced with a new structure at that point. (The bug did still exist in Maverick). I did not find a specific changelog entry that shows where this was fixed, so per policy, I am marking it as Invalid.