"Announce the time" doesn't work after restart, even the box is checked...

Hi all,
System: OSX 10.8.2 Mountain Lion
Machine: Macbook Pro 13.3" with Retina display
I checked the box saying "Announce the time" in Date and Time Preferences, and it did pretty well after I first checked it.
However, every time after I restart my macbook, it doesn't announce the time any more!
I go to Date and Time Preferences, the box "Announce the time" is still checked, but not working!
(And I am sure my macbook is not in a silent mode and I even increase the volume.)
Why so? Please help.

Thank you for replying, @pennbank.
I reset and it worked well as when I checked the option the very first time. However, when I restart the computer, it won't announce the time... I have to uncheck the option and check the option so it will work.
But I am really tired of check and uncheck the option whenever I restart my computer...

Similar Messages

IMac - Display doesn´t work after restart

My iMac 21 Display doesn´t work after restart. If I turn it off and 1 hour later I want use it again the iMac shows the white screen with the mac logo and then the display goes off. I connected an external display to check if the iMac was ON and with the external display I can login and do everything but the iMac Display doesn´t work .
If I turn it off and wait 3 or 4 hours and then turn it back on the display works OK.
This is very strange behavior I have spent hours and hours trying to fine the solution or a similar issue but nothing so I am looking help here at apple.com
BTW When I bougth the iMac 21 there were some spots over the display so the display was replaced by the provider. The warranty has expired by now.

To tell you the truth, I don't know if they have to repalce the LCD panel or what they do for a bad backlight. In this reality of block or assembly replacement it probably involves repalcing the panel and not the backlight component. Don't know what it would cost. You'd have to ask that of a service center.

Assign To "All Desktops" doesn't work after restart

Is anyone else having this problem?
I have several apps that I have assigned to show on "All Desktops"; however, after I do a restart, and these apps are magically restored, though they still claim to be assigned to "All Desktops" they only appear on the first desktop.
I have to then assign them to "This Desktop" and back again to "All Desktops" before they will actually display on all desktops.
Though I seldom restart, it is annoying to have to go through the apps and re-set their display settings each time.
I don't know if it is possibly part of the problem, but all the apps I have set to "All Desktops" I display on my second monitor (I do this so I can have things like Safari on my second monitor, and always available, no matter what I am working in on my main display).

This thread offers a solution, but it's vague and too broad: https://discussions.apple.com/message/16190593#16190593
I don't want to delete all my preferences and have to set them up again. So I did some research and I think I figured out a more targeted solution. The preferences file for Spaces in Lion is located here: ~/Library/Preferences/com.apple.spaces.plist
For some reason, ~/Library is hidden by default in Lion, so to get there you'll have to unhide it. Enter this command in Terminal: chflags nohidden ~/Library
Then, to open and edit that file, you'll need to download the XCode tools, here: http://itunes.apple.com/us/app/xcode/id448457090?mt=12
Finally, you'll want to open spaces.plist, find the line that refers to the application you're having trouble with, e.g.:
"com.apple.finder" = "3C65046B-FA18-4983-9219-8140A2B81A41";
Change that long string of letters to "AllSpaces". Save the file and restart and (I hope) that should do it. Will report back when I've tried this. Still waiting for the rather large XCode application to download from the App Store.

Burning a new CD-RW works first time, doesn't work after erase

Hello all,
My problem has a little twist that I couldn't find a solution to after spending a
few hours digging in all the forums.
I have never been able to re-use a stack of Sony CD-RW disks (p/n CDRW650L
rated for 1X, 2X, and 4X drives).
I can burn them fine the first time but doing an erase renders them unuseable.
I've been using a utility called CD-Erase that came bundled on this iMac G4.
I recently learned that I can (should?) erase from the Disk Utility app -
however, this didn't work either.
Is there a known list of incompatible CD-RW 's ?
I have yet to try another mfgr since I ASSUME I can trust name brands,
especially if the CD-RW and the drive are both made by Sony.
Details of my internal drive:
Manufacturer: SONY
Model: SONY DVD RW DW-U10A
Revision: A43h
Serial Number: EA59142B
Drive Type: CD-RW/DVD-RW
Disc Burning: Apple Supported/Shipped
Removable Media: Yes
Detachable Drive: No
Protocol: ATAPI
Unit Number: 0
Socket Type: Internal
Thanks in advance,
Craig
iMac G4 17-inch flat panel Mac OS X (10.3.9) DSL
iMac G4 Mac OS X (10.3.9) DSL

I'm unfamiliar with the disc erase utility you mention; and it may be
partially responsible for the results you are getting. Have you tried
other disc recording utilities to see if you can get better results?
The only one I've tried, and it worked successfully to erase and record
on a previously used CD-RW (the first disc I've burned) was an easily
used disc recording utility called "Burn 1.6u" and there may be a newer
version of this out, now. Seems to me I checked and found a link online
again to get a newer version from the source: http://burn-osx.sourceforge.net/
Hope this helps; and if it does, please post back. Could be the issue is
only in the erase cd utility you have. It may be making mistakes.

Mail and iCal doesn't work after restart

Hello, after rebooting my Macbook Air I can't use Mail and iCal, which is starting automatically in the background. Please help me. Thanks

Try these things:
First, restart the computer, test. If the problem persists:
Test in a new user; if the problem persists, reinstall your OS (boot up the computer holding "option". Click Recovery HD, then click "reinstall Mac OS X". This will not delete your data, but I'd recommend a backup beforehand anyway, just in case). You can also click "Disk Utility" in the Recovery HD, and attempt to repair your boot disk (Macintosh HD), and restart and test before reinstalling.
If the problem does not happen in a new user, try pulling the preference lists for the two programs. You can find these by clicking Finder, going to the Go menu, hold option and click Library. Click Preferences, then scroll down to "com.apple.mail.plist" and "com.apple.ical.plist". There should be a few of each, pull these to the trash. Restart and test. If the problem still happens:
Safe boot the computer by starting up holding Shift. Test. If the problem still happens, there is some interference from a third-party program, and you might need to disable or uninstall it. You can disable third-party items on startup by going to Apple menu>System Preferences>Users and Groups, then clicking "login items", and removing (not un-checking) the third-party programs from the list. I'd remove anything that isn't absolutely necessary to start up when the computer launches. Note: This does not delete or uninstall a program, but only prevents it from opening when the computer first boots up.
Restart and test.
If the problem still happens, reply and list the steps you have done.
Good luck!

Responsibility rules : Agent determination only works after restarting the WF

Hi Experts,
We are facing a very strange issue related to agent determination in one of our custom workflow:
For agent determination we are using a responsibility rule with two parameters "Company code" and "Plant".
The responsibility rule works well and returns the agents for all the company code.
Recently I have added few company codes to this responsibility rule in the same way we used to maintain and simulate it . It returns the correct agent for newly added company codes but at run time the agent determination is getting failed and the WF goes into an error because of it. However when i restart the WF via SWPR it works well and the agent determination works well either.
This is only happening for newly added company codes the old ones agent determination work well at the run-time.
Pls suggest what could cause this problem. If there is a problem in responsibility rule then why it works after restarting from SWPR.
Thanks in advance. The helpful/correct answers will be rewarded.
Regards,
Him

Hi Rick,
Thanks for replying.
1. Can you replicate this problem in the test system?
Yes I could replicate this issue in test system and it works fine there.
2. Is this a true responsibility rule or does e.g. a function module get called?
We have a responsibility where several responsibilities have been added with two parameters "company codes" and "plant". Every responsibility has a POSITION assigned into it and this position contains the related users.
This responsibility rule is getting called in one other rule with FM. Here in this another rule we are calling the responsibility rule by using the standard FM RH_GET_ACTORS to fill the ACTOR_TAB.
I have tried to simulate both the rules and it returned correct agents but failing at run time.
Regards,
Him

IMessage doesn't work after the installation of the update 5.1

iMessage doesn't work after the installation of the update 5.1

I am unsure whether my issue relates to updating to OS5.1 but seems coincidental that I have only had the problem for the last few days since updating.
I can use iMessage without a problem although some messages are delayed in being sent or received recently. However, I can no longer send MMS picture messages. I have spoken to my provider who has been through all their relevant settings checks. I have restarted the phone (iPhone 3GS), I have tried turning off iMessage to send MMS but still nothing works.
I've had no issue sending MMS picture messages since owning the phone right up until a few days ago.
Has anyone else experienced this or does anyone have any suggestions on anything else I can try please?
Thanks
Jo

My phone is being a real pain! Time doesn't work, can't sign into iMessage and only some apps work! It also kicks me off the wifi! This is not my connections problem, it happens everywhere! Apple is terrible! Phone also freezes a lot!

My phone is being a real pain! Time doesn't work, can't sign into iMessage and only some apps work! It also kicks me off the wifi! This is not my connections problem, it happens everywhere! Apple is terrible! Phone also freezes! What should I do!?

Did you try the basics from the manual?
Restart, reset, restore

After instal OX Maverics Face Time doesn't work

I do not know why but after upload my OX Maverics Face Time doesn't work. It's impossiblo to signe in.
id apple and password are both correct.
why?

Hello matteo.coletti,
It sounds like you are having some trouble signing into FaceTime on your Mac. I would try the troubleshooting steps in this article named:
FaceTime for Mac: Troubleshooting FaceTime
http://support.apple.com/kb/ts4185
Activating FaceTime for Mac
Use your Apple ID to register and use FaceTime. FaceTime registration validates your Apple ID and email address for use with FaceTime.
If you are unable to activate FaceTime, try the following:
Sign in to FaceTime for Mac using a valid Apple ID. After you validate the email address for use with FaceTime, other FaceTime users can connect to you using that email address. If you encounter issues registering or using an Apple ID account:
Ensure that you have an active Internet connection.
Verify that you are using a valid Apple ID at appleid.apple.com. You can also create an Apple ID or reset your password from this website.
Check that your email address is verified in FaceTime > Preferences.If FaceTime > Preferences shows your email status as "verifying," follow the instructions in the verification email that was sent to complete the process.
Toggle FaceTime off and on in FaceTime > Preferences.
If still unable to Sign In follow the instructions in FaceTime, Game Center, Messages on OS X: Troubleshooting Sign in
Troubleshooting FaceTime for Mac
You can make FaceTime calls using the FaceTime app. You can call FaceTime users whose contact information is in Contacts. You can add contacts and edit contact information in either FaceTime or Contacts. To place a video call, you may use a phone number or email address.
If you encounter issues making or receiving FaceTime calls, try the following:
Verify that FaceTime is enabled in FaceTime > Preferences.If the issue persists, or if you see the message "Waiting for Activation", try toggling FaceTime off and then on.
Verify that the Date, Time, and Time Zone are set correctly:
From the Apple () menu, choose System Preferences > Date & Time > Date & Time.
Enable "Set Automatically".
Click the Time Zone tab and confirm the closest city is correct.
Verify that both parties are connected to an active broadband Internet connection.
See Mac OS X: Troubleshooting a cable modem, DSL, or LAN Internet connection.
Consult Using FaceTime behind a firewall for necessary ports to open in firewalls, security software and routers.
If you encounter issues using a Wi-Fi network, use standard Wi-Fi network troubleshooting to resolve interference and other issues.
Verify the phone number or email address being used is the correct one activated for FaceTime.You can verify that you are using a valid Apple ID at appleid.apple.com. You can also create an Apple ID or reset your password from this website.
Otherwise, could you elaborate a bit on any error messages or prompts you are getting?
Thank you for using Apple Support Communities.
Regards,
Sterling

The date and time is not working after setting it to current date and goes back to may,26 2011

the date and time is not working after setting it to current date and goes back to may,26 2011; 2 PM . I bought my ipod tocuh 4th gen on july 18th

On the iPod, make sure your Calendar is set to Gregorian (Settings > General > International > Calendar). Also make sure your date and time on your computer is correct as well as the Time Zones on both.

IPhoto 8.1.2 doesn't work after reinstalled the OS 10.6.8?

iPhoto 8.1.2 doesn't work after reinstalled OS 10.6.8?

To re-install iPhoto
1. Put the iPhoto.app in the trash (Drag it from your Applications Folder to the trash)
2. Download it from the App Store to reinstall It's on your Purchases List* there.
For older versions that have been installed from Disk you'll need these additional steps:
2a: On 10.5: Go to HD/Library/Receipts and remove any pkg file there with iPhoto in the name.
2b: On 10.6: Those receipts may be found as follows: In the Finder use the Go menu and select Go To Folder. In the resulting window type
/var/db/receipts/
2c: on 10.7 or later they're at
/private/var/db/receipts
A Finder Window will open at that location and you can remove the iPhoto pkg files.
3. Re-install.
If you purchased an iLife Disk, then iPhoto is on it.
If iPhoto was installed on your Mac when you go it then it’s on the System Restore disks that came with your Mac. Insert the first one and opt to ‘Install Bundled Applications Only.
*Sometimes iPhoto is not visible on the Purchases List. it may be hidden. See this article for details on how to unhide it.
http://support.apple.com/kb/HT4928
One question often asked: Will I lose my Photos if I reinstall?
iPhoto the application and the iPhoto Library are two different parts of the iPhoto programme. So, reinstalling the app should not affect the Library. BUT you should always have a back up before doing this kind of work. Always.

Imessage doesn't work after the installation of the update 6.0

imessage doesn't work after the installation of the update 6.0

iMessage will not work until it's activated.
Switch iMessage OFF. Double tap Home button and delete Messages in multitask-bar.
Do a reset (Hold Sleep/Wake and Home buttons about 10 secs or more till Apple logo appears, ignore the Slide to Power Off that appears)
Note: You will not lose any data.
Switch iMessage back ON.

Fit the window with mouse doesn't work after new update 10.9.2

Hi, I could fit a windows using my mouse wheel or two finger(on trackpad), doesn't work after I set up new Mavericks update(10.9.2) I'm using Haswell rMBP. Can anyone help me please? Thanks a lot. (Also, minimize with mouse wheel doesn't work too.)

Doesn't anyone having this issue?

Touch ID doesn't work after ios 7.1.1 update

Touch id doesn't work after ios 7.1.1 update..
Why????

After IOS update, you first have to use passcode.
Passcode is needed when
After restarting your iPhone 5s
When more than 48 hours have elapsed from the last time you unlocked your iPhone 5s
To enter the Touch ID & Passcode setting

[Solved] Network doesn't work after hibernate?

Hello! This is my first legit Linux install so excuse me if I'm a bit slow. I installed Arch last night and everything went smoothly. However, after I tested out hibernate on my machine, the network doesn't seem to work. Just prior to the hibernate, I installed Pidgin and Skype but they worked alright, so I think that the hibernate caused a problem on eth0.
I have an Asus P8Z68-V Pro motherboard with an Intel 82579V Gigabit Ethernet Controller that's using the e1000e driver. Running "dmesg | grep e1000e" says that it is up.
I'm not entirely clear here, but from reading, I think that I have several ways of connecting to the network, including network, dhcpcd, networkmanager, and wicd. I am using wicd so I did the following (or at least I think I am only using wicd):
#rc.d stop network
#rc.d stop dhcpcd
#rc.d stop networkmanager
Similarly, I put a ! in front of network in rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# Note: Using "localtime" is discouraged, using "" makes hwclock fall back
# to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# Note: if unset, the value in /etc/localtime is used unchanged
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="America/New_York"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
# Replace every !module by an entry as on the following line in a file in
# /etc/modprobe.d:
# blacklist module
# See "man modprobe.conf" for details.
MODULES=()
# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30
# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"
# Scan for BTRFS volumes at startup
USEBTRFS="no"
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="Vicious"
# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
# Wired network setup
# - interface: name of device (required)
# - address: IP address (leave blank for DHCP)
# - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
# - broadcast: broadcast address (ignored for DHCP) (optional)
# - gateway: default route (ignored for DHCP)
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=
interface=eth0
address=
netmask=
broadcast=
gateway=
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"
# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
# If something other takes care of your hardware clock (ntpd, dual-boot...)
# you should disable 'hwclock' here.
DAEMONS=(hwclock syslog-ng dbus !network netfs crond wicd)
Restarting eth0 through wicd-cli still did not work. I also tried resuscitating the network via instructions on the configure network page before trying to focus solely on wicd.
I found a few similar problems on the forums by searching "wicd hibernate" and tried several solutions but they did not work. Several problems seem to be that the network doesn't work after a suspend because I guess the stuff in RAM did not get saved? But people were able to restart the network by running "/usr/lib/wicd/autoconnect.py" and I wasn't able to get this to work. As a final effort, I added "resume" into mkinitcpio.conf and placed the machine into sleep again to see if it may magically reset something but of course this did not happen .
mkinitcpio.conf:
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run first, so it may be used to
# override the actual binaries used in a given hook.
# (Existing files are NOT overwritten if already added)
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options
# like so:
# FILES="/etc/modprobe.d/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
## This is identical to the above, except the old ide subsystem is
## used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev pata mdadm encrypt filesystems"
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata scsi sata resume filesystems usbinput"
# COMPRESSION
# Use this to compress the initramfs image. With kernels earlier than
# 2.6.30, only gzip is supported, which is also the default. Newer kernels
# support gzip, bzip2 and lzma. Kernels 2.6.38 and later support xz
# compression.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
Not sure if my fstab.conf is useful but if this has something to do with settings getting "lost" in swap, here it is. Linux is on an SSD and HDD (sda and sdc) and Windows 7 is on a HDD (sdb).
fstab.conf:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /tmp tmpfs nodev,nosuid,noatime,size=2000M,mode=1777 0 0
/dev/sda1 / ext4 defaults,noatime,discard 0 1
/dev/sda2 /home ext4 defaults,noatime,discard 0 2
/dev/sdc1 /boot ext4 defaults 0 1
/dev/sdc2 /var ext4 defaults 0 0
/dev/sdc3 swap swap defaults 0 0
/dev/sdc4 /media/data ext4 defaults 0 0
shm /dev/shm tmpfs nodev,nosuid,size=10G 0 0
Is wicd causing these problems or did I configure something else improperly? Would appreciate any help to get eth0 up again!
Last edited by TheBigCow7 (2011-09-13 17:57:20)

Ok, I think I've made some progress! Hibernate definitely affects my network connection. Could this be a kernel 3.0 problem?
I noticed that ifconfig showed eth0 without an inet addr, just an inet6 addr for the longest time. e1000e seemed to be loading up ok. I'm not certain here, but I think that meant the dhcp settings didn't stick, or something along those lines.
Trying to use dhcpcd like the instructions here did not work. By some chance, one attempt did work and while it did, I downloaded and installed dhclient. After that one successful attempt, renewing the DHCP lease via dhcpcd did not work again.
Luckily though, I found that running "dhclient eth0" worked. My DHCP settings seemed to have somehow gotten messed up after my initial, problematic hibernate to the point where none would stick, even after a reboot. Manually typing in "dhclient eth0" would get eth0 working, so I decided to add it to the bottom of /etc/rc.local, like in the example on the networking page.
Now, eth0 works after a boot. However, after the daemons load up during the boot process, my computer takes a long time to get to the login prompt (this is relatively speaking, since I am on a SSD and the boot process used to be blazing fast before). I'm pretty sure it's because I added "dhclient eth0" to /etc/rc.local.
I should say that even with these changes, after a hibernate, my eth0 still does not work and if it weren't for the edit to /etc/rc.local, eth0's inet settings would still not stick after a reboot (that is to say, the hibernate does do something to my network settings).
Is this the correct/most efficient way to fix my DHCP problem? Can I fix my "eth0 after hibernate" issue? Also, can I make my DHCP settings boot up without changes to /etc/rc.local so that I can get a fast boot again (still not sure how it was able to work before without my edit)?

"Announce the time" doesn't work after restart, even the box is checked...

Similar Messages

Maybe you are looking for