Request fix for timezone related bugs

To Adobe Lightroom employees...
Even the new release of LR3 still has age old timezone bugs which are likely infuriating for anyone who shoots in more than a single timezone.
Problem 1: LR ignores camera metadata relating to timezone.
Solution 1: Include a time/date panel in the importer dialog. If camera metadata is present, use it to set defaults. Provide options for shifting both the time and the timezone (e.g. can shift 2010-01-01T01:05:06+01:00 to become 2010-01-01T01:02:03-02:00). This info can be stored in LR database and in exported XMP data.
Problem 2: LR exports incorrect timezone data.
Solution 2: Due to EXIF limitations this cannot be guaranteed correct. Provide an option to export EXIF date/time using a specified timezone (origination/computer/other).
Other problems: File renaming issues relating to timezones, sorting in grid view, etc.
Solutions: If every file has an assigned timezone, all these should become moot points, as information is held to get it right.
The bottom line is that most timezone issue have been present since Lightroom was initially released, and numerous people are frustrated with having purchased a leading product with a glaring set of bugs which corrupt valuable metadata, and interrupt workflow. Providing fixes for these bugs and facilities for handling them sensibly and gracefully, along with default options to provide the current behaviors, allows for the best of both worlds. Date/time are key bits of metadata for any photo, and an inability to handle this properly in one of the leading brands of software is, quite frankly, inexcusable. New features keep being included, yet important basic functionality such as this gets left aside; please prioritize this for the next release to appease many long-suffering, paying customers.
Stan

I too wish that Lightroom would handle date/times with time zones and let users manipulate them. LR 3 consistently ignores time zones; see this post for details:
http://forums.adobe.com/message/2931846#2931846
I think the root cause of this mess is that the EXIF standard, defined in 1998, doesn't support time zones (hard to believe that a standards committee would make such a basic mistake). Even though Adobe's XMP standard requires the use of time zones, LR ignores them!

Similar Messages

Do we have a fix for the justification bug in cfdocument for CF8?

Do we have a fix for the justification bug in cfdocument for CF8?

For IDocs it is [ABAP->Data Transfers|ABAP Connectivity;.
The rest...not sure. Maybe there as well, or XI? Other suggestions?
Thomas

[svn:fx-trunk] 12294: * Fix for error reporting bug.

Revision: 12294
Revision: 12294
Author:   [email protected]
Date:     2009-11-30 13:25:28 -0800 (Mon, 30 Nov 2009)
Log Message:
Fix for error reporting bug. The bug was caused by a warning being
reported during one compilation and then an error being reported in
a following compilation. Due to the warning, the Source's logger
was disconnected instead of being nulled out during the first
compilation. Then in the second compilation, we weren't reassigning
the logger, so the disconnected logger was being left in place. As
a result, it was throwing off expected error counts and caused an
assert to fire.
QE notes: There is probably an easier way to reproduce the assertion
          that George hit without having to create multiple projects
          and without having to manually copy SWC's around. I didn't
          realize this until I had a fix, though. One key aspect that
          George didn't note and might not have realized, is that the
          variable needs to cause a warning, so leaving off a
          namespace works, but making it public, private, etc doesn't.
Doc notes:
Bugs: SDK-24314
Reviewer: Corey
Tests run: checkintests
Is noteworthy for integration: fixes FB issue
Code-level description of changes:
Modified setLogger() to always reassign logger.
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24314
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/Source.java

Is there a fix for the Heartbleed bug for iMac, iPad, iPod?

I just read an article that Google has come out with a fix for PC users to download so they will not be affected by the Heartbleed bug. I was wondering if Apple has come out with a security fix of their own yet?

MsAnnieB2 wrote:
I just read an article that Google has come out with a fix for PC users to download so they will not be affected by the Heartbleed bug.
I've searched for this on Google, but have not found anything. Can you tell me more? If they have found a solution for PC's then there is a good chance it can be made to work with Macs.
I was wondering if Apple has come out with a security fix of their own yet?
Although the information you were given is the best available at this time, it really don't feel it adequately answered your question.
As far as I have been able to find out, all computer users are equally impacted by this issue and there is no way to protect yourself other than to stay off of secure sites until they have told you they are safe. Don't even go onto those sites to change your password until you know that they are safe.

Fix for "color shift" bug

I have discovered the fix for the iPhoto color shift bug (at least with OS X 10.3.9). For those who tried the solution of renaming the Generic RGB Profile, this idea was heading down the right track, but ultimately is not the answer (nor did it even work for me).
When you import photos into iPhoto 5, it does not assign a color profile to the pictures. Then when you edit one using the internal editor and go to save it, iPhoto sees there is no embedded color profile and thus it automatically embeds the Generic RGB Profile, and if that is not the color profile you are using for your screen (and it most likely is not), you will then notice that the colors of your original image have been altered.
Before I tell you the simple solution to this, I HIGHLY RECOMMEND that you create a custom color profile for your Mac. You can use the included OS X one under System Preferences | Displays | Color | Calibrate, but I personally find this one difficult to use and it doesnt offer very good end results for me. The color profile creation program that works the best for me is SuperCal. This program is a little gem and after you use it, it will seem like someone gave you a brand new display. The program is free to download, but after seeing how well it works, I hope some of you will pay the $19 registration fee. On a side note, when creating your color profile, I suggest you use a gamma setting of 2.2 (not the default Mac setting of 1.8). This will make your screen match most scanners, digital cameras, printers, web images, photo labs, etc. (which are all based on sRGB which has a gamma setting of 2.2).
SuperCal can be downloaded here
http://www.bergdesign.com/supercal/
Okay, now youve created your calibrated color profile (lets call it SuperCal) so pictures will now be accurate on your screen. So now heres the fix for the color shift bug its really so simple. Go into Applications | Utilities | ColorSync Utility. Under the Preferences icon, change the RGB Default from Generic RGB Profile to your new SuperCal one. Voila! Thats all there is to it. Now when iPhoto saves an edited picture, it will embed your custom color profile. So what was once a hated annoyance now actually becomes a feature so that all of your saved pictures will perfectly match your screen.
Since the Mac is supposed to be the easiest to use computer around, Apple should fix this so that when you change the color profile for your display, OS X also changes it for file embedding, but as it stands it 10.3.9, you must change this in both places manually.

I appreciate the tip to use gamma 2.2. I'd been wondering about that.
However, as others have mentioned, tagging your photos with a monitor profile is not the way to go.
The othe thing is that under Tiger, ColorSync Utility does not have a preferences section. It only has a devices section.
It is as if iPhoto doesn't know about any profile attached to any picture, whether it's from a camera, scanner, or PhotoShop, and there seems to be no way to tell it which profile to use.
And even after replacing the Generic RGB profile with the same one the images are tagged (by renaming the other profile Generic RGB), iPhoto still displays the images with more saturation and somewhat darker.
This is on an Apple Studio 17" CRT very carefully calibrated with SuperCal.
So I have to come to the conclusion that others have in other threads -- if you're concerned about good color accuracy, don't edit the color balance of your images in iPhoto. Leave that to PhotoShop.

GC spin fix for 5.0 bug (6262235 or 2128236)... when?

We're interested in the fix for bug:
Bug ID: 6262235; Synopsis: NMethodSweeper::sweep takes a long time (mostly in nmethod::cleanup_inline_caches)
on Java 5. The bug is apparently fixed on 1.4.2_09 according to the rel notes and the bug itself notes (1.4.2_09(b02) (Bug ID:2125853)) blah blah. But another bug Bug ID: 2128236 notes that it is fixed in "5.0u6(b02)".
Can someone tell me what that nomenclature means "5.0u6(b02)"? (Seems like it might be saying "coming in 5.0 update 6..)
Chris

Yup, that it.

Fix for Unity connection bug CSCtl41495

Hi,
I need a fix for this bug but don't see any of the following versions available under Unity Connection download page. The current release I am having is 8.0.3 ES22 and would like to stay on 8.0.3 release.
Fixed-In
8.5(1.0)ES17
8.6(0.99981.1)
8.0(3)ES25
8.0(3.23028.1)
8.6(0.18)
8.6(0.96000.132)
8.6(0.96000.53
Can someone clarify when the next full version 8.0(3.23028.1) would be available for download on CCO? Or can recommend any other version available on CCO which has a fix for this bug. I checked the release notets of available versions, couldn't see it fixed in any of them.
Thanks,
inner_silience

Hi,
This has been ported back to 8.0(3). If you open a TAC case, we can publish you the latest 8.0(3)ES27 that contains the fix.
Hope that helps,
Brad

Fix for folder selection bug?

Does anyone know if there is a fix for Dreamweaver CS4 for this problem?
When setting site preferences it sets a folder as one level above the folder you have chosen.
I saw this problem posted by someone else so I know it's not just my machine.
More information:
Running Vista 64bit
Also so the problem on Windows 7 64bit

Same issue here too Win 7 32 bit/DW CS4.
No fix yet available. Just workarounds.
http://forums.adobe.com/thread/478327

Cant find a fix for 3gs maps bug. Any ideas?

Hi
I have been searching for a fix for the maps app on my 3gs 16gb
It was fine until I updated to os4
Now it puts me a long way off and wont follow me on a journey.
I've looked at loads of forums and found plenty of users with the same problem but no solution.
Any clever people out there with a solution for me or do I need a new phone?
Thanks

If you are interested in all the gory details, here's the threads I was talking about:
https://community.verizonwireless.com/message/920801#920801
https://community.verizonwireless.com/thread/790390
https://community.verizonwireless.com/thread/790925

Any fix for the .svg-bug coming up soon?

Hi,
please drop a line if you also encounter issues while implementing an .svg in MUSE.
It’s supposed to work. But the dimensions don’t. At least on my desktop:
It’s particularly critical in layout-mode, as a clear view is required in order to design the page. Positioning the logo here becomes quite a problem. It’s supposed to display in 400 x 150 px, but MUSE seems to bug.
I’d like to use sharp vectors instead of pixel-based-workaround-files like .png.
The fix is on my whish list for Christmas. What about you?
G

I just signed up for FIOS and am not experiencing your problem (had enough other ones instead).
Go to mail preferences ~ click on a mail account ~ click on the advanced tab. The only settings that worked for me were: port 110 SSL OFF, authentication: Authenticated POP (APOP). If I remember correctly when I first set this up another window opened and I typed in my password and never had to do that again.
Hope this helps.

Netcfg's HEAD fixed a ppp-related bug; why isn't it released?

I was having problem using netcfg's ppp feature, when I found this bug report and this git commit. The fix is pretty straightforward and useful indeed, so I wonder why it hasn't been released after nearly half a year. Are there good reasons for this, or the maintainer just forgot or is too busy?

xiaq wrote:I was having problem using netcfg's ppp feature, when I found this bug report and this git commit. The fix is pretty straightforward and useful indeed, so I wonder why it hasn't been released after nearly half a year. Are there good reasons for this, or the maintainer just forgot or is too busy?
The last 6 words most likely sums it up. Alternatively it may be that this single fix isn't worth cutting a release for. In any case, emailing the maintainer may help.

A fix for ProKit-related crashes on open/save (Logic et. al)

OK, here's the deal. I recently upgraded my Mac Pro from Leopard to Snow Leopard (mainly to get ready for Lion, I've been running SL on my MacBook Pro for ages). I never had any problems with Logic 8 (or Final Cut Studio 5.1 for that matter) on my MBP running SL. But after upgrading my Mac Pro, I would get nothing but crashes any time I tried to bring up an Open or Save dialog box in any of Apple's pro apps. The crash log would always show something like this:
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0   libobjc.A.dylib                         0x91795917 objc_msgSend + 23
1   com.apple.AppKit                        0x95e11649 -[NSView _recursiveBreakKeyViewLoop] + 219
2   com.apple.AppKit                        0x95e10a2b -[NSWindow dealloc] + 641
3   com.apple.AppKit                        0x961ab298 -[NSSavePanel _bonafiedDealloc] + 75
4   com.apple.CoreFoundation                0x931779d8 CFRelease + 152
5   com.apple.CoreFoundation                0x931a45bd _CFAutoreleasePoolPop + 253
6   com.apple.Foundation                    0x95942f9f NSPopAutoreleasePool + 393
7   com.apple.Foundation                    0x95942d8a -[NSAutoreleasePool drain] + 130
8   com.apple.AppKit                        0x95c66539 -[NSApplication run] + 627
9   com.apple.prokit                        0x009bb3f6 NSProApplicationMain + 326
10 com.apple.WaveBurner                    0x000027fa 0x1000 + 6138
11 com.apple.WaveBurner                    0x00002721 0x1000 + 5921
After pulling my hair out for hours, I finally solved the problem. I discovered that there was a /System/Library/PrivateFrameworks/ProKit.framework as well as a /S/L/PF/ProKit(SnowLeopard).framework folder on my Mac Pro. However, on my MBP, there was only the expected ProKit.framework folder.
So, (via the Terminal, sudo mv, etc.) I renamed ProKit.framework to ProKitFOO.framework and renamed ProKit(SnowLeopard).framework to ProKit.framework. Boom! Everything started working fine.
I Googled for a fix like this for hours earlier, so here's hoping that this might end up helping someone else out there, perhaps thinking of upgrading to SL to make way for Lion. Don't ask me why this ProKit installation was goofy, but at least now there may be a workaround.

Hey, thanks!
I was having the exact same problems in Final Cut Studio 2
Motion crashes/closes on 'save as' or export.
DVD studio pro crashes on import.
Soundtrack Pro crashes on save as.
Final cut pro 6 was the only one that worked fine. Not sure about LiveType, havn't used that in like 4 years.
JUST A WARNING:
Final Cut Pro X will not open after this fix!
Any ideas of how to get both FCS2 and FCPX working on the same machine in Snow Leopard? I like editing in FCPX (for my needs it's faster) but I still need DVDSP. :/
Any point upgrading to FCS3 or will that crash as well?
---------------Or is there an alternative to DVD SP that's free or not too expensive????------------------
For those that need it, here's the reverse process:
(This worked just fine for me to reverse the process and get FCPX to work again, HOWEVER, I am NOT qualified to give this advice, I am not a programmer or developer! - do the following at your own risk.)
Open Terminal and enter the 4 lines below and press 'enter' after each line:
cd /System/Library/PrivateFrameworks/
sudo mv ProKit.framework "ProKit(SnowLeopard).framework"
sudo mv ProKitFOO.framework ProKit.framework
exit
I hope that's been helpful to someone.
Nitsan.

Fix for UI Rendering Bugs (status bar, safari, othe windows "over zoomed")?

Anyone else seen these visual bugs in the UI:
* In vertical mode only the clock is displayed in the status bar. The contents of the status bar are "zoomed in" so much that the signal strength icon on the left and the battery indicator on the right are off the screen and out of view. Neither have ever been displayed (in vertical orientation) since I got the phone two days ago. The characters are over-sized and fuzzy, even clipped across the top of the screen.
* When a dialog box comes up on top of the current application (e.g. prompt to join a WiFi network), only a fraction of the dialog fits on the screen. The UI of the dialog is zoomed in too far, the text is large and fuzzy. The application UI below (seen through the transparency of the dialog) appears okay.
* After a settings reset, Safari works okay for a few minutes, but eventually gets zoomed in so far that the URL field at the top and the button bar across the bottom are no longer visible.
* Switching back and forth from vertical to horizontal (e.g. in music or Safari) sometimes shows the full status bar as expected (signal indicator, time, battery) and sometimes shows only the time (zoomed and fuzzy). Sometimes no status bar is displayed at all (black).
I've tried...
* resetting settings
* resetting settings & removing all data
* full factory default/software restore
None of this helps. Any ideas? Is this a software bug, or is there potentially some hardware defect causing the software to act so whacky?
Thanks for any help/pointers.
HP Windows Vista

Apple has confirmed that my phone has some defect and should be replaced. Thanks.

Is there a fix for the freak bug for us poor users of ios 7.1.2

The silence from Apple is deafening, does anybody know if Apple have any plans to roll out a patch for ios 7.1.2 ?

ipad2_guy wrote:
25% of us are running iOS 6 & iOS 7. A lot of people still run Android 4.0-4.4. Same for Windows Vista & 7. And Firefox/Chrome/IE still receive updates for all those platforms. But for iOS, not only is the latest (8.2) the greatest, it's the only game in town. If I had known that in 2011, I would not have purchased my iPad & iPhone. Apple needs to step up and offer security support for those folks (early adopters) who got them here today.
For Android the patch is in the hands of the carriers and device makers.
Millions of users still run Windows XP and currently there is no plans for a patch
The Chrome browser is not affected but the mobile browser on Android is. The company said Tuesday that it has developed a patch for the Android operating system’s browser and has provided it to “partners,” meaning the companies that make most Android devices. It will be up to those companies to deploy it. Security experts have long complained that crucial updates can take months – or never arrive at all – because Google does not control the process of delivering patches to devices running Android.
As you can see, this isn't only Apple that does not immediately (if ever) patch no longer supported versions of their software.

[svn] 3233: Fix for bug related to see tag, [Exclude] metadata, and extra lines in mxml examples block.

Revision: 3233
Author: [email protected]
Date: 2008-09-16 12:57:29 -0700 (Tue, 16 Sep 2008)
Log Message:
Fix for bug related to see tag, [Exclude] metadata, and extra lines in mxml examples block.
Bugs: SDK-16886
QA: Yes
Doc:
Reviewed By: Pete F
Tests: checkintests
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-16886
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

Request fix for timezone related bugs

Similar Messages

Maybe you are looking for