Bug 543593 - tsclient erroneously lowercases username/homedir for preferences
Summary: tsclient erroneously lowercases username/homedir for preferences
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: tsclient
Version: 12
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Christopher Brown
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-02 17:28 UTC by Alex Rovner
Modified: 2010-12-04 02:21 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 473540
Environment:
Last Closed: 2010-12-04 02:21:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Alex Rovner 2009-12-02 17:28:22 UTC
+++ This bug was initially created as a clone of Bug #473540 +++

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):


How reproducible:


Steps to Reproduce:
1. log in
2. start tsclient
3. add remote server entry
4. exit app
5. start app - all entries lost

  
Actual results:

tsclient must be lowercasing the dirname - don't :-)




Expected results:


Additional info:

--- Additional comment from jhaar.nz on 2009-05-04 16:28:48 EDT ---

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.

Jason

--- Additional comment from fedora-triage-list on 2009-11-18 04:25:10 EDT ---


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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

--- Additional comment from alexrovner on 2009-12-02 12:26:10 EDT ---

This happens in FC12 as well...

Comment 1 Alex Rovner 2009-12-02 17:30:53 UTC
This affects ONLY users using WINDBIND as stated above. I have verified by launching tsclient from the terminal that this is infact is the issue:

** (tsclient:23282): WARNING **: Failed to save connection information for: cwsvn, Failed to create file '/home/contextweb/arovner/.config/tsclient/connections/cwsvn.tsc.R9YD4U': No such file or directory


Notice that contextweb is lowercased. Supposed to be:

/home/CONTEXTWEB/arovner/.config/tsclient/connections/cwsvn.tsc.R9YD4U

Comment 2 Christopher Brown 2010-07-04 18:24:17 UTC
Thanks for the bug report - I will take a look.

Comment 3 Bug Zapper 2010-11-04 04:34:53 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2010-12-04 02:21:35 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.


Note You need to log in before you can comment on or make changes to this bug.