Bug 891003 - Windows 8 is unable to fully save remote profile
Summary: Windows 8 is unable to fully save remote profile
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: samba
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Andreas Schneider
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-31 16:55 UTC by Chaim Frenkel
Modified: 2015-02-18 13:51 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-18 13:48:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Events from the Application Event Log reporting the windows errors. (3.71 KB, text/plain)
2012-12-31 16:55 UTC, Chaim Frenkel
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Samba Project 9678 0 None None None Never

Description Chaim Frenkel 2012-12-31 16:55:39 UTC
Created attachment 670859 [details]
Events from the Application Event Log reporting the windows errors.

Description of problem:

When logging out from a Windows 8 machine, Error displayed is: Windows cannot update your profile completely. 

Version-Release number of selected component (if applicable):
samba-3.6.9-96.fc17.1.x86_64

How reproducible:

Consistent

Steps to Reproduce:
1. Create new windows user (old user can be used, but this ensures that windows creates all permissions)

2. Log in to new account

3. Log out of new account

  
Actual results:

Message appears on screen.
Errors are in Event Log.

Expected results:

No errors.

Additional info:

The new user was supplied with an empty writeable home directory. Profile.V2 was created and managed by windows 8.

Comment 1 Guenther Deschner 2013-01-02 17:04:28 UTC
Are you using "profile acls = yes" on the share where you plan to store the profiles ?

Comment 2 Chaim Frenkel 2013-01-16 13:00:02 UTC
That doesn't appear to be the problem. My profile storing has worked for my XP and Win7 machines. It is only with Win8 that the problem appeared.

In addition, most of the files appear to be written correctly, only a few of the files appear to fail.

Comment 3 Guenther Deschner 2013-01-18 11:22:41 UTC
I tested with win8 and "profile acls = yes" and I could not see a problem.

Could you create a network trace during the failed update of your roaming profile so we get a better idea about which files are failing ?

Comment 4 Fedora End Of Life 2013-07-03 22:30:37 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

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.

Comment 5 dijuremo 2013-07-31 18:13:02 UTC
This is a bug in Samba, see:

https://bugzilla.samba.org/show_bug.cgi?id=9678

Comment 6 Fedora End Of Life 2013-08-01 00:28:28 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

Comment 7 Fedora End Of Life 2015-01-09 22:02:52 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 8 Fedora End Of Life 2015-02-18 13:48:24 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 9 Guenther Deschner 2015-02-18 13:51:05 UTC
Should be fixed with the current update.


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