Weird Time Bug

no matter what i do in system prefs, date and time in menubar always displays GMT time, all files (when info is displayed) display GMT time
I am in LA and this problem happened before when set to "Los Angeles PST" but disappeared when set to "Vancouver PST"; I then reset to "LA PST" after a couple of months and was fine; now computer is acting up again; no recent installs that may have altered the system
The correct time is displayed in the Date & Time pref pane, tried both manual and sync to apple.com and the menu bar won't correct itself
If I go to date and time in menu bar and click "open date & time...." does not do anything.
Toggled clock in menu bar on and off via "Clock" tab in date & time, no change; same with 24 hour clock; same with clock in window instead of menu bar; same in analog
repaired disk permissions
performed smc reset
not sure which preferences file to delete....
scrren shot posted below- any ideas?
http://web.mac.com/jtrapanese/iWeb/JoeComposer.com/TIME%20PICS.html
Macbook Pro Mac OS X (10.4.8) 2gb ram

I am having a similar issue. I am trying to set the clock to EDT, but it always snaps back to GMT. I have tried some of the fixes concerning Parallels (which has the correct local time) but they don't work. I also did the SMC reset with no change.
MacBook Pro 17" 2.33 Ghz 2 GB RA Mac OS X (10.4.9) Parallels Build 3188

Similar Messages

Stacks weird visual bug

Hi,
I'm running Leopard 10.5.3 on a 1Ghz iMac G4 which came with a GeForce4 MX graphics card. I've been using stacks from the beginning (and loving it) but every time I use it, a weird visual bug is triggered; basically white semi-transparent rectangles appear along the edges. You can find a screenshot of this at http://picasaweb.google.com/luis.beca/StacksBug/photo#5206710255993309346. Any clues as to why this is happening or how to solve it?
I should point out that I have been stuck with this problem from the very beginning, not just the latest Leopard version 10.5.3. I have an Intel MacBook Pro where this is not an issue.
Many thanks in advance
Luís
PS - How can I submit this to Apple?

I think you can thank Apple for this. See this discussion.
Photoshop CC: MacOS 10.10 Yosemite: Graphics driver problem
Nancy O.

Weird subtitle bugs

I'm running into several weird subtitle bugs in Encore 2.0. My project is a 33 minute training video with 4 subtitle tracks - English, Chinese, Spanish and Russian. I know the project was initially created in 1.5, but I don't remember if the subtitles were imported before or after the conversion.
The first is that some of the subtitles that have been edited are showing the original version of the subtitle. In most cases, if I go back to the edited version in the timeline and add a space at the end, it seems to update to the new version of the subtitle.
The other issue is that in many cases, the subtitles are staying on the screen longer than they should be. In one instance, the subtitle stayed on the screen for about 15 seconds more than it should.
Any comments or suggestions?
This will be the last project for me in Encore - I just can't afford to spend multiple days working around Encore and its "features"
Thanks,
David

Experienced the same subtitling "bugs" you described.
Opened a ver. 1.5 project in ver. 2. Then once in ver. 2, I revised some text in several subtitle clips. The revisions were displayed o.k. during preview, but when I built a new DVD Volume from ver.2, and tested the playback in WinDVD software player, it was the "old" subtitles that were displayed!!!!!
Apparently, the Encore 2 programmers overlooked a crucial subroutine in their coding. If i'm not mistaken, when you type-in or edit a subtitle clip, the program module that runs is something like a wordprocessor that works with the native fonts and formatting; the text in a subtitle clip is later rendered by Encore as a masked bitmap file overlaid onto the main video when you turn on the subtitles when you build the DVD volume (it's like in Photoshop where a text layer will be editable until you rasterize it, in which case the "text" becomes a bitmap image which you can no longer text-edit). I guessed that the edited subtitle clips were not being re-rendered by Encore. So, to work around this, I created/added new subtitle clips next to the "old" one and re-typed the text with the incorporated revisions, then deleted the "old" clip and repositioned the recently added/created clip. Afterwards, the subtitles with the corrected text displayed properly when I played back a re-built DVD volume.
But although this "work-around" works, it would simply be too bothersome if you had to revise hundreds of subtitle clips!!!!! A situation I later found myself confronted with!
What I did, then, was I duplicated the original subtitle track (which Encore failed to re-render properly) on which I had done the revisions; then, once the duplicate subtitle track had been pasted by Encore on the timeline, I deleted the original track and re-built a new DVD Volume. This time, all the revised subtitle clips were displayed correctly when I played back the volume in the software DVD player.
Nevertheless, I hope Adobe becomes aware of this bug and implement the appropriate fixes.

AIX 6/7 U.S. Daylight Savings Time bug

I saw announcements this past Friday and yesterday about daylight savings time bug on IBM AIX and thought this news might be important to pass around, as the time changes in the U.S. this coming weekend, and the fix requires a system reboot.
Possible Action Required: System time may not change properly at DST start/end dates on AIX 7.1 and AIX 6.1
[http://www-01.ibm.com/support/docview.wss?uid=isg3T1013017&myns=pwraix61&myne=E|http://www-01.ibm.com/support/docview.wss?uid=isg3T1013017&myns=pwraix61&myne=E]

> Apparently, this is far more complicated than either of us might think. I've heard that from several people.
I don't want to simply sound argumentative (I'm NOT attacking you in any way here), but without some sort of specific evidence of why this would be a complicated issue to fix, I have difficulty believing this. It's easy to say "it's more complicated than you would think," but where is the evidence of this? Where is the statement from Adobe saying that they know about this issue? Where are the examples from the people you refer to that explain why Lr can't do with dozens of other apps -- many of them FREE -- can do without this problem? Are we really supposed to believe that displaying the date/time correctly is so complicated that it's going to take Adobe over a YEAR to fix it?
We're talking about displaying some text from a standard tag. When it comes to this sort of application, it doesn't get much simpler than this. Lr doesn't have to "calculate" anything -- it just has to display the data in this field. How is this any different than displaying the data from any other field. Why is Lr applying an "adjustment" to a field that doesn't need it? Exactly what is the theory behind this being difficult?
Thanks for your feedback,
Larry

Particular .time bug

Hi,
I noticed a bug. Don't know if it's RTMFP related. When a
publisher is publishing, a subscriber listens. After a while, the
subscriber stops viewing the stream by invoking .play(false) on the
stream, which stops the streams (invokes the NetStream.Play.Stop on
the publisher side (first maybe odd thing). Then, the publisher
stops publishing by invoking the .close() method on his stream. The
publisher then decides to republish the same stream and does so.
The subscriber then suddenly has the stream playing without really
being in the state of asking it. Also, the .time property of the
subscriber is in the 4079999.001 or so values.. which really isn't
true. It's been on for about 485 seconds. Seems like the .time
property gets substracted by about 2 000 000 ms or so.
Don't know how many bugs are in this description, but the
.time weirdness seems the most visible and unexpected/manageable
(except to close the subscriber stream and restart it). The fact
that the stream starts by itself after invoking the .play(false) on
it, seems also a bit odd.
PS: I need to use the .play(false) method, because it doesn't
leave spawned NetStreams on the publisher stream when it starts
republishing. Vs using .close() everytime the subscriber wants to
stop receiving the stream at a given time. I also decided to not
use the .pause() method because it doesn't seem to pause properly
the data stream/bandwidth on the publisher.info side.
Regards
Fredz

Yes, it refers to Infrastructure (UCS Manager, FI and IOM). You could just upgrade the infrastructure to 2.2.3d and leave your Servers at 2.2.1d
Table 2 Mixed Cisco UCS Releases Supported
of the release notes.
CSCuo30572
Intel v2 processors no longer cause PSOD with Microsoft Windows 2008 R2 VM guests.
2.1(3a)A
2.2(2c)A

Can you reproduce this weird playlist bug???

I see this on Windows 7 and Windows 8.   Spotify desktop app.   Curious if it happens for other people, or on any other platforms.
1. Create a new empty playlist
2. Add six albums each with at least 10 tracks. I drag and drop the albums to the playlist, one at a time. You should now have at least 60 tracks in the playlist.
3. Use the default playlist sorting method, By that I mean, don't sort the playlist by song, artist, album name, or date. Should be the order you added the albums.
4. Scroll to the bottom of the playlist and highlight all of the tracks in the last album. Select the first track in the album with the mouse and then hold CTRL while you arrow down or mouse click to select the rest of the tracks.
5. Now drag the selected album up to move the tracks above the second to last album.   You're effectively swapping the bottom two albums in the playlist.
^^^ At this point I get an error message about adding duplicate tracks to the playlist. Which is strange because I have not added any new tracks, I'm only reordering them.
6. Now create another new empty playlist.
7. Select all of the tracks in the first playlist. CTRL-A works.   And drag and drop them to the new playlist
^^^ Notice the new playlist now has TWO copies of each album!   If the first playlist had 60 tracks, this one has 120!!!
Weird, eh?   Very frustrating when I make playlists of full albums....

Bug reproduced with LibreOffice 3.5.1.2 on Arch x86_64 here.
officeuser wrote:Can you also reproduce the bug? Can you create a gdb log of the bug according to these instructions?
I'm afraid I can't. At step 3, when I try to run base within gdb I get no further than the "Database assistant" dialog. Base freezes as soon as the main window is opened when running in gdb.

N80 - SMS time bug with Vodafone Italy SIM

This mobile (even with the lastest 4.0623.0.42 firmware) has a bug regarding the time of SMS with Vodafone Italy SIMs.
Timestamp of the messages is forwarded of 2 hours.
For example, if a friend sends me a SMS at 20:00, when I look at the details of the message received in my phone it shows 22:00.
This bug has been confirmed by many other people, a little search on google confirms that
Hope that Nokia can fix asap, a 500€ phone shouldn't have such a bug :/
EDIT:removed linkMessage Edited by jams on 24-Oct-2006
09:15 AM

i confirm this too.
same problem on my nokia 3250. its a pretty annoying problem
only workaround is to set your timezone to iceland but keep your current local time configured. it will work.
List of Nokia phones I've used: 3310, 3315, 3200, 6600,3250, N73 ME, N95 8GB, 5800 XpressMusic and Nokia X6 16 GB (currently using this).

Weird Time Issue

We're experiencing a weird issue with our unity server. The time on our unity server is ahead by one hour, yet our callmanager server is on time. If I go into windows time and correct the time on the unity server, I am unable to dial into the voicemail from any of our phones. If i change it back to being an hour ahead, the voicemail works again. Has anybody run into something similar to this before?

Hi Brett,
Have you looked into using NTP?
How To Configure Time Synchronization for Cisco CallManager and Cisco Unity
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_configuration_example09186a008009470f.shtml
Hope this helps!
Rob

Weird AudioFileStreamParseBytes() bug

This is driving me batty. I'm using AudioFileStreamParseBytes() to parse data from an mp3 Shoutcast stream and then hand it off to the Audio queue for playback. The code works fine for all the Shoutcast streams I've tested, except for one - and of course the one that doesn't work is the one I really need to work.
From what I've been able to determine, AudioFileStreamParseBytes() is frequently getting confused by the mp3 stream. It's an MPEG-1 layer 3 VBR stream, at 44100, with an average bitrate of 80. The stream also includes a CRC-16 checksum in each MP3 frame. The stream is being generated by a Barix Instreamer 100 (in case that matters). The stream also plays fine via iTunes.
I'm cross-referencing the stream data with a network sniffer and can confirm I am receiving valid mp3 frames from the Shoutcast server. I also can confirm this identical valid collection of frames is being passed to AudioFileStreamParseBytes(). However, when AudioFileStreamParseBytes() calls my packet callback function with the parsed data, it will frequently skip a valid mp3 frame header and will instead think some data in the middle of the frame (which happens to start with FF) is the mp3 frame header.
Has anyone seen anything like this? The problem is so frequent it occasionally will happen on the very first frame, causing the AudioFileStream logic to misidentify the type of stream (usually resulting in an incorrect frequency or file type).
I'm tempted to just bypass using the AudioFileStream and load the mp3 frame into the AudioQueue directly from my TCP stream, but I thought using the AudioFileStream was supposed to offer some better error handling in case data transmission is temporarily interrupted. As it seems right now, however, the AudioFileStream is introducing errors of its own - at least with this one problematic Shoutcast stream.

Oddly, the problem with AudioFileStreamParseBytes() only exists when compiled for a Mac OS target. If I run the same code on an iPhone (either via the simulator or a real iPhone device) the function parses the MP3 stream just fine.
Weird...
Fortunately, my real target is the iPhone (I was just doing initial development on a Mac since I thought the audio stream debugging would be easier/faster - silly me!), so I guess I don't really mind this bug anymore.

Weird, random bug.

Has this happened to anyone else here?
I open Photoshop and load in a document. If I try to paint with the brush, the brush leaves a single circular dab where I click on the screen, and doesn't move from there. That is, each time I try to draw a stroke, it just puts a single dab at the start of the stroke and that's it.
If I try to make a marquee selection, it creates a marquee with the upper left corner at the upper left corner of the image, and the lower right corner where I clicked the mouse, and will not resize the marquee as I drag. If create a new layer from the selected region and try to drag it across the screen, it always snaps back to where it started as soon as I let go the mouse. If I nudge it with the arrow keys, it moves to a different position as expected, but then when I try to drag it again, it snaps back to its last position.
This bug crops up at random, and disappears at random. Just now it disappeared when I tried using my mouse, instead of the Wacom tablet, to paint.

Sounds like it could be a Wacom driver issue or Wacom hardware malfunction. Make sure you have the latest Wacom driver.
You need to give details in order to get help.
CLICK HERE
for advice on how to ask your question correctly for quicker answers. Thanks!

How can I resolve this weird timeline bug ?

Hi !
I'm currently editing a feature film, using Premiere Pro CS6. This means a lot (a loooooooot) of clips, audio et video. But for a few days now, I encounter a strange bug, occuring exclusively on the audio part of the timeline... The problem being very hard to describe (especially for a french frog like me :-) ), I made a screen print of it : http://www.flickr.com/photos/95364114@N02/8694919869/in/photostream . So three problems here :
- The audio clips does not always match the video clips, visually I mean (when I play them, they do match).
- The vertical red lines occurs when I move the red reading tape (sorry, I don't know the english word for it)
- The horizontal black lines, occuring when I scroll up and down through the audio tracks.
The thing is, if I click in the video track when this problem happens, sometimes everything comes back to normal, other times it doesn't. And even if it comes back to normal, it will happen again whenever I move through the timeline... It's more of a visual problem : if I read the clips, they are just as I edited them. But it's still a very annoying problem whenever I want to check a part of the movie, or trim a clip or whatever...
If anyone knows any solution to this, it would be more than great !
PS : Oh, and it's apparently not a project size problem : the project's weight was 200 Mo, I cleaned it up, and it's now weighing 85 Mo... but the issue still occurs !

Nvidia site lists the current driver for GTS 450 (Win7 64)
as 314.22, Release Date:2013.03.25.
http://www.nvidia.com/Download/index.aspx?lang=en-us
http://www.nvidia.com/object/win8-win7-winvista-64bit-314.22-whql-driver.html

Very Weird Time Capsule Volume

I just began using a 27" iMac yesterday, and when I tried to backup to my external drive, got a message saying I was out of space, actually that I had 49.8g space available on the external, and needed 85g for the backup. So I tossed the oldest backup, freeing 120g. Tried again, same message; I tossed another day's backup, same message. I then repaired the disk. Same results as before. No matter how many days I toss, I have the same available space on the external, which is insufficient. I feel like just disconnecting it, buying a new one and starting anew, but I thought I'd ask here if anyone can see something I've not thought of. Applecare is good, but they can only go so far, I've found. Sometimes electronics just get too weird to figure, and hundreds of brains on a forum may be the key to this. Thanks for any contributions you may make.

NicksGrandad wrote:
My apologies, now that you've pointed this out, I look and can't find a "Time Machine" forum
For future reference, there are actually two of them: one in the Leopard section, one under +Snow Leopard.+
And I'm afraid I know the answer to this, but just exactly how did you "toss" the oldest backup, and why do you think that freed 120 GB?
The list of "backups" on my external volume are approximately 120gb each. I trashed those, so that's "toss".
Do you mean you deleted them via the Finder? If so, that's a problem.
Unfortunately, Apple doesn't do a very god job of warning folks not to do that; it can corrupt your backups. Repair them, per #A5 in Time Machine - Troubleshooting (or use the link in *User Tips* at the top of the +Time Machine+ forum).
Ordinarily, you shouldn't have to delete backups, but you can do it safely via Time Machine. See #12 in Time Machine - Frequently Asked Questions (or use the link in *User Tips* at the top of the +Time Machine+ forum).
You didn't gain much space because of the way Time Machine works. After the first full backup, it only copies what's changed since the last one. But by using "hard links" to the things that didn't change, each backup is a snapshot of the way your entire system looked. So all the things that didn't change get counted when the Finder calculates the size of each backup folder. If that sounds weird, it is! See How Time Machine works its Magic for a (hopefully) better explanation.
I ordered another external drive from LaCie today, so the old one is going into the closet in case I need something from it eventually; probably not going to happen, but I'm not willing to erase it and face possible loss of something critical.
Ah, good plan. If your backup volume isn't at least 2.2 times the size of the data it's backing-up, Time Machine would have deleted all but the last backup, but still not had enough room, and failed.
And you can always view or restore from the old set, via the +*Browse ...+* option, in #17 of the FAQ.

Task Sequence Application deployment - maximum run time bug

Hi there,
we install sophos antivirus during the task sequence and though i specified a maximum run time of 15 minutes the installation of sophos app takes about 2 hours during the task sequence.
is this a known bug that the maximum run time is being ignored?
Best,
Sebastian

The Max allowed run time does not intend to limit the application running duration. It is for Maintenance Window.
http://technet.microsoft.com/en-us/library/bb680462.aspx
Juke Chou
TechNet Community Support

Weird resizing bug with Fluxbox + Xcompmgr.

I'm using fluxbox and xcompmgr today, trying it out again after a while with openbox. Every time I resize a window, it seems like xcompmgr is failing to resize the dropshadow it leaves behind it, or other times it will just show the contents of the window in the space they used to occupy.
Screens:
http://i30.tinypic.com/2mnm638.png
http://i31.tinypic.com/2niz2us.png
Any ideas would be great, I used fluxbox for quite a while and had no problems like this!

I have same bug ....but doesn't have a solution for....anyone else?

Fix for iTunes Video "Stop Time" bug created by iTunes 10.5

You can set the Start Time point on a video, but the Stop Time does not work the video keeps on playing. Any Fix yet???
>>>>
There was a bug introduced in a late iTunes 10.4 or early in 10.5 that prevents Stop Time for being recognized...the video will keep playing past the "Stop Time" you've designated. It doesn't matter if you're running Snow Leopard or Lion. The bug affects videos only (music videos, movies, TV shows).
>>>>>>

More info: After I upgraded to 10.6.7, I first noticed the problem. Downgraded to 10.6.6 and it worked again. Upgraded to 10.6.8 when it was released to see if this had the issue fixed - but it didn't, iTunes failed to stop on time again (only music videos).
Just downgraded to 10.6.6 and it still doesn't work!!! Now I'm really screwed and confused. HELP!

Weird Time Bug

Similar Messages

Maybe you are looking for