Red Hat Bugzilla – Bug 473540
tsclient erroneously lowercases username/homedir for preferences
Last modified: 2014-06-18 05:10:43 EDT
Description of problem:
I'm using winbind to allow "Windows" account logins. Works well - you log in as DOMAIN/username, and pam_mkhomedir auto-creates the homedir of /home/DOMAIN/username
Anyway, tsclient stores its configs (at least $HOME/.config/tsclient/connections/new-connection.tsc) after it lowercases the $HOME value! i.e it tries to write to /home/domain/username/.config/tsclient instead of /home/DOMAIN/username/.config/tsclient
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. log in
2. start tsclient
3. add remote server entry
4. exit app
5. start app - all entries lost
tsclient must be lowercasing the dirname - don't :-)
I've just upgraded to FC11-preview and it's still happening. A quick fix is to simply create a symlink between /home/DOMAIN and /home/domain - but tsclient is definitely at fault here.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
This happens in FC12 as well...
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.