elitebiber Posted October 29, 2013 Share Posted October 29, 2013 Hi there, I found a bug on OS X 10.9. When I lock the display with Alfred command and login back I can't open Alfred anymore. The UI seems to recognize the command but the input window is not visible. I work with several Spaces and already checked if Alfred comes up on any other screen. I have Alfred 2.1 (218) with the Powerpack. Link to comment
jdfwarrior Posted October 29, 2013 Share Posted October 29, 2013 Hi there, I found a bug on OS X 10.9. When I lock the display with Alfred command and login back I can't open Alfred anymore. The UI seems to recognize the command but the input window is not visible. I work with several Spaces and already checked if Alfred comes up on any other screen. I have Alfred 2.1 (218) with the Powerpack. When you migrated to Mavericks did you perform a clean install or perform an upgrade? I'm wondering if this is another issue caused by Apple's not-so-perfect upgrade. I've noticed lots of friends and others (not just with Alfred) mentioning issues with things after the Mavericks upgrade that users who performed a fresh install didn't experience. I am one of the users that performed a clean install and can't seem to replicate your issue right now. One thing we like to try when there are weird issues is for users to create a new user account, log into it, and see if they can still replicate the issue on a new account. Can you verify whether you have the same issue on a new user account? Link to comment
elitebiber Posted October 29, 2013 Author Share Posted October 29, 2013 The Problem seems to be a bigger issue in Mavericks itself. In some cases every open application is positioned in the upper left or upper right corner and can't be moved away from there. The only solution i've found so far is to kill all affected apps and restart them. I did a clean install of Mavericks. Link to comment
Andrew Posted October 29, 2013 Share Posted October 29, 2013 This sounds like an issue outside of Alfred's control… I'm going to move this to the help forum to see if anybody else can offer you a solution, Link to comment
Alec Posted November 6, 2013 Share Posted November 6, 2013 I too have this exact issue. It seems to only happen after using Alfred's "Lock" feature, and seems to affect Chrome, Adium and tools I use for shortcuts (Divvy, Shortcat). Link to comment
jdfwarrior Posted November 7, 2013 Share Posted November 7, 2013 I too have this exact issue. It seems to only happen after using Alfred's "Lock" feature, and seems to affect Chrome, Adium and tools I use for shortcuts (Divvy, Shortcat). Could you try creating a new user account and logging in there to see if you still have the same issue? I am unable to replicate the issue running the current version of Alfred and Mavericks Link to comment
brettnak Posted November 12, 2013 Share Posted November 12, 2013 I'm also having this problem. It doesn't happen every single time I lock from alfred, but it does happen often. Maybe about 40 - 50 percent of the time. Here's the apple discussion about this issue for anyone interested. https://discussions.apple.com/thread/5516275 Link to comment
Andrew Posted November 12, 2013 Share Posted November 12, 2013 I'm also having this problem. It doesn't happen every single time I lock from alfred, but it does happen often. Maybe about 40 - 50 percent of the time. Here's the apple discussion about this issue for anyone interested. https://discussions.apple.com/thread/5516275 Thanks for the link - lets hope Apple get this fixed! Have you tried a new user account on your Mac like somebody suggested on there? Link to comment
Andrew Posted November 13, 2013 Share Posted November 13, 2013 Btw, for users experiencing this issue, it might be worth turning off the lock command in Alfred and using the screensaver command instead (change the keyword to lock, and set OS X to need a password to when the screensaver becomes active). Link to comment
Alec Posted November 13, 2013 Share Posted November 13, 2013 Btw, for users experiencing this issue, it might be worth turning off the lock command in Alfred and using the screensaver command instead (change the keyword to lock, and set OS X to need a password to when the screensaver becomes active). In addition, shift + ctrl + eject/power is a nice way of triggering screensaver which doesn't cause this issue. Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now