Date modified timestamps resetting on login (mouse user preferences reset)

Hi,
Using network accounts on 10.8.2 off a 10.8.2 server.
All files in user directory have 'date modified' timestamps reset to login time.
This occures for all users.
This I believe is also causing mouse user preferences to be reset on login.
Has anyone come across this problem?
I migrated from 10.7.4 Server to 10.8 Server
Any ideas anyone?

Hi
I am just "happy" to see that I'm not the only one having the exact same trouble.
The "date modified" resets to last login time, user preferences (particularly some of the trackpad, keyboard and dock prefs) are thrown away and in part reset to some default values.
My setup is various iMacs with their HomeDirectories on the server, all machines with 10.8.2 (Server) installed.
Could Apple help?

Similar Messages

User preferences resetting to default...

After a log out or a restart my wife's macbook pro (not the new model) all user visual prefs are lost. Goes back to deafult desktop, dock deafult, etc.not what I have just set.
FYI: User folder is on a 2nd internal hard drive (disk player removed). Checked that ML is using this as teh user folder, it is. Even reselected it, restarted, changed prefs, logged out and back to defaults.... something is not right. Thanks (upgraded from Lion).

Hmmm, no one else. Okay...
I eventually fixed it, those it was semi laborious...
The permission problem(created in upgrading to ML) was in the user library(hit go in the menu by holding the option key to reveal library ). I had to go in by hand, command "i" on folders, opening the info window, unlocked it w/ password and changed the permissions - I had to add the actual user (admin no less)and then select "read and write" access to the folder. It was a bit tedious as plenty of the folders (and inside content) had the red "-" sign revealing the permission problem. Obviously I decided against aborting the account and cleaned it up instead. Less data transfer that way.

OD 10.8 All dates modified for home folders & files changes on login

We upgraded our network server to 10.8 recently, and now whenever a user logs on, all the files & folders in their home reset the date modified to the login time. It's the most bizarre glitch I've ever seen.
Possibly, but not likely related, their mouse settings (or at least natural scrolling setting) are not retained.
Has anyone else encountered this weird behavior? New accounts/imported accounts are all effected. Doesnt matter if they login from a 10.7 or 10.8 machine. OS is up to date on both the clients and server.

Has anyone else encountered this weird behavior?
Date modified timestamps resetting on login

Detection Method of Date Modified fails due to copied files date modified change

I've been working through an issue for some time now and I think it's a bug with SCCM 2012 SP1. I've built literally 50 deployments in "Application Management" in SCCM 2012, but I've been chasing my tail on a few of them throwing the
"succeeded but couldn't detect" error. The few that have given me problems are all copying text files and then detect the modified date to verify that the file is there. All worked when I initially built them in Windows 8 but are now failing
randomly...even on a machine where they previously worked and I deleted the files to test the deployment again.
What I'm doing:
My java deployment requires policies which we control with the Deployment.config, deployment.properties and java.policy files. A simple script creates the directories and copies the files. I then create a deployment type for this "ConfigFileCopy.cmd"
and create a detection rule for each file that I am moving over. The detection rule looks for a "date modified" date between the beginning and end of the date for the day I modified the file. This allows me to modify the files to change our
java policies and then redeploy them with the "new" modified date as the detection rule, which forces the update.
The problem:
When I first created my deployment, everything worked pretty well. The files copy out and the script runs successfully. There were some minor tweaks I need to make to my scripts, so I did and then updated the content for the deployment type. I believe this
is where things go a little wonky. At this point, my deployment starts failing with the "0x87D00324" error.
Looking through the logs, everything looks good. The reason configuration manager is failing on detecting the modified date for those files, as it turns out, is because the modified dates don't meet the criteria. So that part is properly failing the detection.
The problem is that the modified dates are correct on the server but not the client. Looking in c:\windows\ccmcache, I can see multiple folders....presumably one for each version of the application that I updated. Looking at any of the newer content folders
for this app, the modified dates are the date and time the file was copied out to the workstation, which is incorrect as the file hasn't been modified during that process.
The odd part, is that this doesn't happen EVERY time on EVERY machine. My primary desktop is windows 8.1 and received the files correctly and installed without issue. My test win 8.1 laptop initially received them correctly, but then as I refined the scripts
it began picking up the wrong modified dates and started failing.
I found a similar issue to this existed in SCCM 2007 (http://support.microsoft.com/kb/2276865) so I suspect that this is truly just a bug that hasn't been addressed (or maybe is fixed in R2). Unfortunately
we have business reasons we can't upgrade to R2 at this time so I'm hoping someone has experienced this and has some sort of work around that might get me by for now. If someone can confirm it is fixed in R2, that would help my case to upgrade as well.
I can work around the issue by changing my logic to detect any date greater than a specific date. But I shouldn't have to do that and I'm concerned there are scenarios I haven't thought of that will cause unexpected behavior or failures with that.

This outlines the behavior. It's apparently by design.
"SCCM has a habit of changing the ‘Date Modified’ timestamp of all files it delivers when it detects an ‘upgrade’ of the source files for that application. It typically does not touch the timestamp
of the source files if it delivers a brand new install to a client that has never received the software, however if a single file in the source folder is changed for that application, then SCCM tries to use a previous version of the application in the cache
(C:\windows\ccmcache) and only downloads the new file that has change. This results in all files having their ‘Data Modified’ timestamp changing (except for the brand new file). Therefore determining if that application has delivered
successfully using ‘Date Modified’ timestamps is not recommended. The key to seeing this process in action is looking at the file properties in the
C:\windows\ccmcache\<sccm code> folder for that application, particularly before and after a file is updated in the original source SCCM application folder."
http://blog.kloud.com.au/tag/sccm/

When does Date Modified field update in cmc XI3.1

In CMC > users and groups
there is a Date Modified field, When does it update? Is there any document describe that?
For example
I have test that when I edit a user's properties the Date Modified fields update.
When a user log onto CMC, some time the logon times is update as Date Modified
some times is not? Why does this happen?

Hello,
If you update the the properties of the group or the user then the last modified date will change to the current date/time. What kind of user do you have, Enterprise, Windows NT, Windows Active Directory or LDAP. Sometimes a user doesn't exist until they actually log on to the CMS then their Last Modified date would change. Have you consistantly seen this happen with a specific user, if so can you reproduce this on demand.
Jorge

No user preferences to delete

This troubleshooting basics page:
http://support.apple.com/kb/HT3659
reads:
Delete the User Preferences
You can resolve many issues by restoring Soundtrack Pro to its original settings. This will not impact your project files. To reset your Soundtrack Pro user preference settings to their original state:
Quit Soundtrack Pro if it is open.
In the Finder, go to ~/Library/Preferences. Note: The tilde (~) represents your Home folder.
Remove the "com.apple.soundtrackpro.plist" file from the Preferences folder.
Go to ~/Library/Application Support/Soundtrack Pro.
Remove the "EffectsCache.plist" file from the Soundtrack Pro folder.
Go to ~/Library/Application Support/Soundtrack Pro/Layouts.
Remove the "Soundtrack Pro.saved.moduleLayout" file from the Layouts folder.
Go to ~/Library/Caches.
Remove the "com.apple.audiounits.cache" from the Caches folder.
However, I cannot find any of these files. I fear this means the app is corrupt. Please advise!
Thank you!

This troubleshooting basics page:
http://support.apple.com/kb/HT3659
reads:
Delete the User Preferences
You can resolve many issues by restoring Soundtrack Pro to its original settings. This will not impact your project files. To reset your Soundtrack Pro user preference settings to their original state:
Quit Soundtrack Pro if it is open.
In the Finder, go to ~/Library/Preferences. Note: The tilde (~) represents your Home folder.
Remove the "com.apple.soundtrackpro.plist" file from the Preferences folder.
Go to ~/Library/Application Support/Soundtrack Pro.
Remove the "EffectsCache.plist" file from the Soundtrack Pro folder.
Go to ~/Library/Application Support/Soundtrack Pro/Layouts.
Remove the "Soundtrack Pro.saved.moduleLayout" file from the Layouts folder.
Go to ~/Library/Caches.
Remove the "com.apple.audiounits.cache" from the Caches folder.
However, I cannot find any of these files. I fear this means the app is corrupt. Please advise!
Thank you!

In my opinion, the real solution is for Apple to offer us a choice of the photo sort order in ITunes. My preference would be filename, perhaps with options to choose the Date Taken attribute, file timestamp or date modified filestamp (EXIF date fields as

I tryed to sort my pictures with buying Apps and following suggestion from apple, but without any success. In my opinion, the real solution is for Apple to offer us a choice of the photo sort order in ITunes. My preference would be filename, perhaps with options to choose the Date Taken attribute, file timestamp or date modified filestamp.

Not a problem when using iPhoto on a Mac, which the transfer of photos is primarily based on - not manually managing photo storage as seems to be common with Windoze.
The same should be available with a supported photo management app on a PC.
http://support.apple.com/kb/HT4221

Need to Clarify: Reset Windows Login Password can hack to CSS data?

Dear ThinkPad fans
Until now, we both know that we can find many ways to pass over and reset Windows Login Screen. So my question is if they can use tools to reset my Windows Login Passwords, can they use reseted pass phrases to discover my CSS data?
Any can clarify to me? Thank a lot.
Using: ThinkPad W500 - Windows 7 Ultimate 64 bit.

Welcome to the community.
I don't think you'll get much discussion on this topic as any techinical info might be used for nefarious purposes. Anything posted remotely useful for those purposes might also be at risk of moderation per the Community guidelines here:
http://forums.lenovo.com/t5/Welcome-FAQs/Lenovo-Community-Participation-Rules/m-p/1
Specifically:
No posts shall include instructions or directions intended to subvert security measures, including passwords, locking mechanisms, fingerprint scans, etc, or to subvert safety measures. Nor shall any posts provide descriptions to the location of, nor direct links to content related to these topics.
Regards.
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество
Community Resources: Participation Rules • Images in posts • Search (Advanced) • Private Messaging
PM requests for individual support are not answered. If a post solves your issue, please mark it so.
X1C3 Helix X220 X301 X200T T61p T60p Y3P • T520 T420 T510 T400 R400 T61 Y2P Y13
I am not a Lenovo employee.

Date modified/Date Created/Date Added(timestamp) - not showing the actual date?

In finder, none of the date info seems to be accurate.
By example, I just downloaded a new app from a website (onyx in this case), todays date is Nov 13th and when I install the new app (i.e. drag and drop into Apps folders) in finder the Date modified says Nov. 1st, Date created says October 31. Should one of these columns not reflect the true date that the app actually got onto my mac? I understand that one of these clumns probably relfects the info contained within the downloaded app, but surely one column can tell me that I installed this app on November 13! The "Last opened" columns is the only "accurate" date column I have. (as I write this however, i've noticed that the 'Date Added column does say "Today").
I gues my question is what columne reflect what the file itself has imbedded in it, and what relfects the actions i've done (I.e. installed the app on Nov 13)
Any help would be very much appreciated. Note sure if this is somehting more worrisome or not, but i've had it for a while with no major issues other than frsutration of not understanding this. i'm on 10.7.2

The Date Modified column for the Applications folder itself will reflect the actual installation date. The others aren't supposed to.
(61530)

Why does Bridge always sort images by rating instead of by date modified?

Why does Bridge always sort images by rating instead of by date modified?
This drives me bonkers. Everytime I look for an image I've been working on, I go to Bridge and I'm always presented with the images sorted by rating instead of by date.
Then I click on the microscopic sized, extremely tiny arrow that allows one to choose 'sort by date modified' and I resort them to find the file I need. So that's always 3 extra clicks to find the image.
WHY can't Bridge sort images by date modified and STAY that way every time I come back?
Thanks for any help.
I know I could just keep the recent files rated the highest, but still, I'm wondering if there's a way to make it work the way I'd like it to work?
jn
p.s. Note to Adobe: Please make the selection button for sorting images arrow larger than a fraction of the size of the period at the end of this sentence. Thanks.

WHY can't Bridge sort images by date modified and STAY that way every time I come back?
By default it does stay at the latest selected sort order so this could mean it is due to your install.
First of all try to reset the preferences for Bridge, hold down option key while restarting Bridge and choose reset preferences. This sets it all to default. First try if the problem is solved then set prefs again to your own custom wishes.
Also check and repair permissions for the OSX itself (Apple has disk utility in the utility folder for this job, and there are other 3th party applications)
And be sure to have the latest update for Bridge. (Bridge CS5 should be 4.0.5.11)
In addition to the method Tai Lao pointed you already to there is a third option, use right click mouse button in content window and the pop up menu has also the sort option at the bottom of the row

Upload file last modified timestamp

Hello there! This is my first time posting!
I'm trying to upload a remote file with HTML form and JDBC (and save as a BLOB in the database).
Is there a way to get the last modified timestamp of this remote file?
If so, how?
Thanks!
Regards,
Wilson

That makes it a much tougher problem. I know that JSP won't give you what you need. You may be able to write a signed JavaScript to do the job, but I have never seen a successful implementation of signed JavaScript. You may be able to access some COM object, but then you would not be platform independent. The answer may possibly come with an Applet, although I have never used Applet technology in the real world, so I am not familiar enough with it to show you the way.
So, short of getting the user to key in the date time as part of their form submission, this one has me stuck.
Sorry I can't be of more help.

Possible fix for Word2004 "Date Modified" issue

I'm not sure if anyone else is still dealing with this problem - we discussed it a year ago here:
http://discussions.apple.com/thread.jspa?messageID=7610823
But just in case there's someone else out there with the problem - I think I've found a fix (requiring OSX Server 10.5, tested on OSX Server 10.5.6)
The problem:
When you have a Word 2004 file (whatever.doc) stored on a server (10.4.0-10.5.6) then you have an annoying Date Modified issue. Whenever someone who is not the owner simply opens the file, the Date Modified date updates. When the owner of the file opens it, the date does not change. So by simply opening the document (and making no changes, and not re-saving it) you trigger an update of the Date Modified field.
More info can be found following the link above.
Well. I think I've found a work-around that's better then the current "Have everyone login as the same user" one.
In OSX Server, setup the permissions for the share with group as "read only" - so the POSIX permissions only give non-owners read-only access. (Everyone should also be RO or None)
Then you need to apply a Custom ACL. You want to give them Read & Write, but then edit the Write permissions to not allow Write Attributes and Write Extended Attributes.
So the ACL is:
[ ] Administration
[Y] Read
[-] Write
--[ ] Write Attributes
--[ ] Write Extended Attributes
--[Y] Create Files (Write Data)
--[Y] Create Folder (Append Data)
--[Y] Delete
--[Y] Delete Subfolders and Files
[Y] Inheritance
Obviously this means your users cannot write attributes - so for photos and other files where meta-data is critical, this is not a great idea. But for the vast majority of shares, this is fine - they can still "read and write" all the files and folders, but the Date Modified problem does not arise.
I'd be interested to see if this works for anyone else. Please let me know
Charles

Interesting and understood. I always tell people/clients that want to use dates either date created but definitely date modified to add that into the name of the file or call them revisions each time, ie:
lawsuitJamesrev2
or
lawsuitJames_5_1209
Reason being is depending on the backup system or worse yet disaster recovery you might not see or be able to see modified dates. IF the file is labeled as shown above it makes it easier. Again each person is different but from experience this works best as well as sorting. Also law firms I worked with have a number system since they needed to follow regulations on how to secure content. Again just ideas...hope you find an answer and pass it on

"Date Modified" for all files being changed if "Automatically write to XMP" is on

Recently upgraded from LR3 (v3.4.1) from LR2 on OSX 10.6.8 and have always had Catalog Settings > Automatically write changes into XMP turned on.
When browsing existing JPG files in my Library (no Develop changes, no keywording, no Presets, no Import), LR3 is writing to disk — i.e., when I look at files in Finder, almost every viewed file’s “Date Modified” is being set to today’s date and time. (It actually creates a .swp file, then changes it's name back to .jpg)
This is really bad, as it's making it impossible for me to use Finder to figure out when I last worked with a file, it is triggering needless Time Machine and Backblaze backups, and unnecessarily churning my disk.
If I turn off "Automatically write..." this behavior stops. Per David Marx at thelightroomlab.com, I tried turning off this preference, manually doing a "Save Metadata to File" for all files, letting that complete, then turning the preference back on. This does not solve the problem.
Per a suggestion at photoshop.com, I used ExifTool to see what changes LR was writing to a sample file; from the diff below, you can see that LR is adding a bunch of new fields as well as moving other fields around. But my point is that LR3 should never overwrite a file on disk if all I am doing is browsing thru them.
Is anyone else seeing this? Any ideas would be greatly appreciated!
-- David
diff Exif5609_original Exif5609_update
2c2
< FileName: DSC_5609_original.JPG
> FileName: DSC_5609_update.JPG
5,6c5,6
< FileModifyDate: 2009:11:27 21:32:54-08:00
< FilePermissions: rwxr-xr-x
> FileModifyDate: 2011:08:07 22:06:47-07:00
> FilePermissions: rw-r--r--
27a28,29
> ShutterSpeedValue: 1/200
> ApertureValue: 7.1
55d56
< SerialNumber: 3209521
75d75
< Lens: 18-200mm f/3.5-5.6
185,188d184
< UserComment:
< SubSecTime: 00
< SubSecTimeOriginal: 00
< SubSecTimeDigitized: 00
211a208,299
> XMPToolkit: Adobe XMP Core 5.2-c004 1.136881, 2010/06/10-18:11:35
> CreatorTool: Ver.1.00
> MetadataDate: 2011:08:07 22:06:47-07:00
> SerialNumber: 3209521
> LensInfo: 18-200mm f/3.5-5.6
> Lens: 18.0-200.0 mm f/3.5-5.6
> ImageNumber: 26634
> RawFileName: DSC_5609.JPG
> SavedSettingsName: Import
> SavedSettingsType: Snapshot
> SavedSettingsParametersVersion: 6.4.1
> SavedSettingsParametersProcessVersion: 5.0
> SavedSettingsParametersWhiteBalance: As Shot
> SavedSettingsParametersIncrementalTemperature: 0
> SavedSettingsParametersIncrementalTint: 0
> SavedSettingsParametersExposure: 0.00
> SavedSettingsParametersShadows: 0
> SavedSettingsParametersBrightness: 0
> SavedSettingsParametersContrast: 0
> SavedSettingsParametersSaturation: 0
> SavedSettingsParametersSharpness: 0
> SavedSettingsParametersLuminanceSmoothing: 0
> SavedSettingsParametersColorNoiseReduction: 0
> SavedSettingsParametersChromaticAberrationR: 0
> SavedSettingsParametersChromaticAberrationB: 0
> SavedSettingsParametersVignetteAmount: 0
> SavedSettingsParametersShadowTint: 0
> SavedSettingsParametersRedHue: 0
> SavedSettingsParametersRedSaturation: 0
> SavedSettingsParametersGreenHue: 0
> SavedSettingsParametersGreenSaturation: 0
> SavedSettingsParametersBlueHue: 0
> SavedSettingsParametersBlueSaturation: 0
> SavedSettingsParametersFillLight: 0
> SavedSettingsParametersVibrance: 0
> SavedSettingsParametersHighlightRecovery: 0
> SavedSettingsParametersClarity: 0
> SavedSettingsParametersDefringe: 0
> SavedSettingsParametersHueAdjustmentRed: 0
> SavedSettingsParametersHueAdjustmentOrange: 0
> SavedSettingsParametersHueAdjustmentYellow: 0
> SavedSettingsParametersHueAdjustmentGreen: 0
> SavedSettingsParametersHueAdjustmentAqua: 0
> SavedSettingsParametersHueAdjustmentBlue: 0
> SavedSettingsParametersHueAdjustmentPurple: 0
> SavedSettingsParametersHueAdjustmentMagenta: 0
> SavedSettingsParametersSaturationAdjustmentRed: 0
> SavedSettingsParametersSaturationAdjustmentOrange: 0
> SavedSettingsParametersSaturationAdjustmentYellow: 0
> SavedSettingsParametersSaturationAdjustmentGreen: 0
> SavedSettingsParametersSaturationAdjustmentAqua: 0
> SavedSettingsParametersSaturationAdjustmentBlue: 0
> SavedSettingsParametersSaturationAdjustmentPurple: 0
> SavedSettingsParametersSaturationAdjustmentMagenta: 0
> SavedSettingsParametersLuminanceAdjustmentRed: 0
> SavedSettingsParametersLuminanceAdjustmentOrange: 0
> SavedSettingsParametersLuminanceAdjustmentYellow: 0
> SavedSettingsParametersLuminanceAdjustmentGreen: 0
> SavedSettingsParametersLuminanceAdjustmentAqua: 0
> SavedSettingsParametersLuminanceAdjustmentBlue: 0
> SavedSettingsParametersLuminanceAdjustmentPurple: 0
> SavedSettingsParametersLuminanceAdjustmentMagenta: 0
> SavedSettingsParametersSplitToningShadowHue: 0
> SavedSettingsParametersSplitToningShadowSaturation: 0
> SavedSettingsParametersSplitToningHighlightHue: 0
> SavedSettingsParametersSplitToningHighlightSaturation: 0
> SavedSettingsParametersSplitToningBalance: 0
> SavedSettingsParametersParametricShadows: 0
> SavedSettingsParametersParametricDarks: 0
> SavedSettingsParametersParametricLights: 0
> SavedSettingsParametersParametricHighlights: 0
> SavedSettingsParametersParametricShadowSplit: 25
> SavedSettingsParametersParametricMidtoneSplit: 50
> SavedSettingsParametersParametricHighlightSplit: 75
> SavedSettingsParametersSharpenRadius: +1.0
> SavedSettingsParametersSharpenDetail: 25
> SavedSettingsParametersSharpenEdgeMasking: 0
> SavedSettingsParametersPostCropVignetteAmount: 0
> SavedSettingsParametersGrainAmount: 0
> SavedSettingsParametersLensProfileEnable: 0
> SavedSettingsParametersLensManualDistortionAmount: 0
> SavedSettingsParametersPerspectiveVertical: 0
> SavedSettingsParametersPerspectiveHorizontal: 0
> SavedSettingsParametersPerspectiveRotate: 0.0
> SavedSettingsParametersPerspectiveScale: 100
> SavedSettingsParametersConvertToGrayscale: False
> SavedSettingsParametersToneCurveName: Linear
> SavedSettingsParametersCameraProfile: Embedded
> SavedSettingsParametersCameraProfileDigest: D6AF5AEA62557FCE88BC099788BBD3CC
> SavedSettingsParametersLensProfileSetup: LensDefaults
> SavedSettingsParametersToneCurve: 0, 0, 255, 255
> IPTCDigest: d41d8cd98f00b204e9800998ecf8427e
228,230d315
< SubSecCreateDate: 2009:11:27 21:32:54.00
< SubSecDateTimeOriginal: 2009:11:27 21:32:54.00
< SubSecModifyDate: 2009:11:27 21:32:54.00
http://feedback.photoshop.com/photoshop_family/topics/lr3_date_modified_for_all_files_bein g_updated_when_browsing_photos_if_catalog_settings_automatically_write_changes_into_xmp_is /replies/6313647

clvrmnky wrote:
davidpope007 wrote:
Then when LR3 loaded my old LR2 images into memory, it "dirtied" the in-memory copy of the file by adding in these new LR3 XMP fields. Then, because I had "Automatically write XMP" on, it said "I better write these changes to disk".
Yuck. As a former software engineer, this is very bad software engineering.
It should wait until the user dirties the file (via Develop, keywords, etc.) before presuming to add a bunch of metadata fields that are unique to the new version of LR3.
Well, I'm a current software developer, and this is, really, a perfectly reasonable thing to do. It is a reasonable trade-off for a convenient feature required by a small subset of users.
Yes, in most cases the in-memory copy should "never" be dirtied unless the user makes a gesture of some sort, but like I said earlier, this option (once set by the user) sets up the situation where this gesture becomes implicit. This is a clear trade-off for the sake of convenience. And if the XMP is out of date and needs to be updated en masse, so be it.
The fact is, there is no easy way around this. Do we save up /every/ dirty buffer somehow until you make a gesture that /might/ require the XMP to be up-to-date before acting on that gesture? Now we have to worry about unflushed buffers if something goes wrong and the app exits. Do we save the buffers to the DB? Now we have to block some calls to make another blocking call to flush some or all of those to DB, and then write some or all of it out to one or more files. In what order? What if there is a gesture to have X files with up-to-date XMP and some or all of those are in unflushed buffers, unflushed DB writes or we have to wait for the DB.
As you can see, this is a transactionality nightmare, and the easiest and safest thing to get what the user wants (i.e., up-to-date XMP for the purpose of talking to a third-party XMP aware app) is to simply update the sidecar or XMP block in an atomic manner using the correct file IO. The file will have to change at some point, so it may as well be now.
[Thanks to both of you for your detailed replies. I am aware of the need for tradeoffs so when you say the approach taken is quite reasonable, I do believe you. I also apologize in advance for the length of the following and am extremely aware of the time it must have taken you to compose the above replies, but I'm going to add a bit more, if only for my own piece of mind and in hopes of coming up with a solution for my workflow.]
From my naive point of view, I was expecting the answer to be simply "don't raise the XMPDirtyFlag upon reading in a file". Obviously if your architecture requires you to "upgrade to latest XMP format" upon read, and another part of the system auto-detects "out of date XMP", then it's going to write those changes to disk.
But it didn't need to be designed that way. LR obviously has mechanisms to know when a user has made a change to XMP so it is able to write XMP changes to disk only when necessary.
The promise (to me) of "Automatically Write XMP changes to disk" was to auto-save my changes, and not those made for any internal (i.e., XMP versioning related) changes.
Perhaps the premise is that it is LR3's job to update an individual file's XMP to the latest version so that other XMP-aware apps can make use of it? I would argue that those third-party XMP-aware apps already have to know how to deal with all prior versions of XMP, so LR3 should just leave well enough alone.
You asked if my problem with your approach was that it was "inelegant"; not at all, it is based on my own perception of what I need from my workflow, so let me describe that so maybe we can find a better way:
* Part of the appeal of LR to me is that it preserves my original file as it came off the memory card, allowing me to move to a different workflow/toolset in 2025 if I choose to do so
* However, with all of changes contained in a single database file, I'm concerned about rare (but possible) corruption, so to mitigate this risk, I let LR backup my database weekly and it's also backed up continuously in the cloud via Backblaze
* Even with backups of the database, there is still a chance that I could lose changes made to individual files (e.g., LR corrupts the DB and I have to go back to last week's DB)
* Thus the appeal of the "auto-write to XMP" flag -- that way critical changes (develop, crop, keywords) are saved on a per-file basis; I liked the "automatic" part of this (as opposed to a manual save) because then I don't have to teach others in my family how to manually save XMP changes
* A nice side-effect of this setting is now when I use Finder to find a file and double-click on it to edit it in Photoshop, all my develop changes are right there; (in other words, I like the flexibility of not having to fire up LR in order to just invoke PS from within it); also when I use Bridge I see all the keywords there
* So with LR2, I had gotten used to what I thought was the best of all worlds -- autosave of changes at the file level via XMP + raw negatives untouched (i.e., Date Modified == the date I took the picture); this allows me to use operating-system-level tools -- Finder -- to locate/search for files
* Now I upgrade to LR3 and I'm finally now understanding that a concept "XMP versioning" is going to result in changes to many, but not all my files. (That's something else that's annoying about this issue -- I open up the Grid and browse a folder of files, and only seemingly random ones I've cursored over seem to get written to disk -- if it's so urgent that LR3 update the XMP, then it should do it for all the files in the catalog or at least in that directory)
Here's a screenshot from Finder of what I see everytime I look at this folder:
* So now I have to assume that each new version of XMP and/or LR is going to touch my files on disk. Sigh.
* What I don't like about this is that it is ruining the promise of "untouched raw negative". Yes, the image data is untouched -- which I agree is most of the benefit; but the file has been touched.
* Perhaps you might empathize a bit more if you imagined that someone went thru all your source code or Word files and randomly changed the date to "today" because you upgraded compilers or moved to Word 2011.
I agree all of this would be solved by having an XMP sidecar file for JPGs, but you indicate that's not going to happen.
You've also alluded to the solution of "resetting the Date Modifed" to it's original value -- which I believe is what Finder does when you move or copy a file -- but that that is fraught with issues as well. I believe you when you say there are issues, but again the naive part of me wonders why that soultion would be so bad...
I just thought of another potential solution -- turning on Date Created in Finder -- but it turns out that's changed, too.
I am really at a loss as to what to do and would welcome your suggestions.
Thanks again and kind regards,
-- David

Tried to reset a login keychain but got the error: Unable to obtain authorization for this operation.

There was a user account established on my computer when I bought it. I later added an admin account. I realized that I did not have the password to the original account. Using the admin account, I changed the password for the user account. I then realized that I now couldn't access the keychain. I followed the instructions to reset a login keychain. Opened Keychain Access, selected Preferences, clicked Reset Login Keychain, typed the new password I'd created for the account but received the following error. Unable to obtain authorization for this operation. I cannot find a user/library/keychain folder so I can't delete the user keychain file. How can I reset the keychain?

A lot longer ago than that. PowerPC apps haven't been supported since Lion, 10.7.x.
You may have just purchased the game, but the developers obviously haven't kept up to date with the requirements for newer versions of the Mac OS.
You have three options, depending on how old your Mac is.
1) If it were ever able to boot directly to Snow Leopard, you could create a separate partition and install SL onto that partition. Make sure to turn on the option during the installation to install Rosetta. That is OS X's PPC emulator.
2) If your Mac is too new to install Snow Leopard, then you can purchase and install Snow Leopard Server within a VM, such as Parallels, VirtualBox, or Vmware.
3) Use a separate older Mac for running outdated software.

Accessing explorer view updates modified timestamp only on e-mails (.msg) in SharePoint 2013

Hi All,
We've recently discovered that when users are accessing explorer view in various libraries on SharePoint, libraries which hold emails (.msg) are automatically updating all email modified timestamps with the time explorer was accessed and presenting modified
by as the user who initiated explorer view as well.
It is not all documents, only emails (.msg). This happens every time without fail: When accessing a library in explorer view, right clicking and selecting refresh (or adding a new document to the library via explorer) triggers all emails to have their modified
stamp updated. It creates a single version at the time of refresh if version control is on.
Here is the log in the scenario where I refreshed a library in explorer view which has only one email called pings.msg and it has had its modified timestamp updated to the time of refresh:
Medium Entering monitored scope (Request (PROPFIND:http://...:80/sites/ICT/Shared%20Documents/desktop.ini)). Parent No
Medium Name=Request (PROPFIND:http://...:80/sites/ICT/Shared%20Documents/desktop.ini)
Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=0#.w|domain\me, ClaimsCount=29
Medium HTTP Request method: PROPFIND
Medium HTTP request depth header: 0
Medium Overridden HTTP request method: PROPFIND
Medium HTTP request URL: /sites/ICT/Shared%20Documents/desktop.ini
Medium HTTP request translate header: f
High [Forced due to logging gap, cached @ 09/12/2014 13:07:41.30, Original Level: Verbose] WOPI is disabled because no discovery data are found.
High [Forced due to logging gap, Original Level: Verbose] SPRequestModule.PreSendRequestHeaders
Medium Leaving Monitored Scope (Request (PROPFIND:http://...:80/sites/ICT/Shared%20Documents/desktop.ini)). Execution Time=12.1815063087627
Medium Leaving Monitored Scope (Request (POST:http://...:80/sites/edrms/_vti_bin/sitedata.asmx:GetContentEx")). Execution Time=428.478759171906
Medium Name=Task: SessionManager.PerformOngoingRequestDepartures
Medium Entering monitored scope (Request (GET:http://...:80/sites/ICT/Shared%20Documents/Pings.msg)). Parent No
Medium Name=Request (GET:http://...:80/sites/ICT/Shared%20Documents/Pings.msg)
Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=0#.w|domain\me, ClaimsCount=29
Medium HTTP Request method: GET
Medium Overridden HTTP request method: GET
Medium HTTP request URL: /sites/ICT/Shared%20Documents/Pings.msg
Medium HTTP request translate header: f
Medium Spent 0 ms to bind 81408 byte file stream
Medium Spent 16 ms to send 81408 byte file stream
Medium Leaving Monitored Scope (Request (GET:http://...:80/sites/ICT/Shared%20Documents/Pings.msg)). Execution Time=19.2898818145882
Medium Entering monitored scope (Request (HEAD:http://...:80/sites/ICT/Shared%20Documents/Pings.msg)). Parent No
Medium Name=Request (HEAD:http://...:80/sites/ICT/Shared%20Documents/Pings.msg)
Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=0#.w|domain\me, ClaimsCount=29
Medium HTTP Request method: HEAD
Medium Overridden HTTP request method: HEAD
Medium HTTP request URL: /sites/ICT/Shared%20Documents/Pings.msg
Medium Leaving Monitored Scope (Request (HEAD:http://...:80/sites/ICT/Shared%20Documents/Pings.msg)). Execution Time=7.43690888087732
High [Forced due to logging gap, cached @ 09/12/2014 13:07:41.35, Original Level: Verbose] SQL connection time: 0.0458857201124724
High [Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity
Medium Entering monitored scope (Request (PUT:http://...:80/sites/ICT/Shared%20Documents/Pings.msg)). Parent No
Medium Name=Request (PUT:http://...:80/sites/ICT/Shared%20Documents/Pings.msg)
Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=0#.w|domain\me, ClaimsCount=29
Medium HTTP Request method: PUT
Medium Overridden HTTP request method: PUT
Medium HTTP request URL: /sites/ICT/Shared%20Documents/Pings.msg
Medium HTTP request translate header: f
Medium Spent 0 ms to read 81408 byte file stream
Medium |No zip central directory found
Medium Information Rights Management (IRM): The email address of the requesting user is successfully set to IRM.
Medium Information Rights Management (IRM): The IRM status of the document [Shared Documents/Pings.msg] is: untried (-1), the return values is: 0x0.
High Leaving Monitored Scope (EnsureListItemsData). Execution Time=22.2785298131466
Medium Spent 16 ms to parse
Medium |No zip central directory found
Medium |Nothing to commit
Any ideas on how to stop this behaviour?

Probably you have an antivirus that scan these files when you are open the library in Explorer View.
Try to configure the antivirus for exclude location.
Hope helps.
http://valygreavu.com/

Date modified timestamps resetting on login (mouse user preferences reset)

Similar Messages

Maybe you are looking for