Stuck in "loop" or "hang" after login

Running a MacBook Pro with 10.5.4 and Filevault on (company policy, so turning it off isn't an option). Sometimes after I start up the computer I will get to the logon screen enter my password and the computer will hang. The background doesn't change to my user backgrounds and I need to do a hard reset.
I've tried disk repair, permissions repair, running fsck -fy in single user mode, amongst other things. Some other suggestions, like deleting preferences files don't work because FileVault is enabled.
Thoughts on other things to try?

I just had this problem and couldn't find a solution online, so for the record (I'm presuming it's too late for you) here is what worked for me.
First the symptom: upon booting I could get to the login screen with no issues. I could login to accounts that didn't have filevault enabled, but not the account with it (it would hang after login, never changing to my desktop background).
First workaround: Logged in as root and manually opened the username.sparsebundle file (under Users/.username), using the FileVault password. At this point I could see that all the files were intact, and access them. Then I got a warning from Sophos Antivirus that a file needed to be moved to the infected folder and I had to enter a password for it. After that, login worked fine. But after the next logout I had the same problem.
Final workaround: Turning off Sophos (not just the moving of files but also active scanning) solved the problem. Best guess is that Sophos is trying to move files before login and doesn't have the permission to move them to the right place but you can't see that it's needing that feedback so it just stalls indefinitely.
I note that another user with this problem also had Sophos installed (see topic "Can't login after enabling FileVault"). I only had the problem after transferring a bunch of old email to my machine (with windows viruses in some of the attachments). Of course these caused my mac no threat, but this combined with the need for a password for file movement triggered the weird behavior.

Similar Messages

User Stuck at Applying User Setting after Login

I have windows server 2008r2 remote desktop environment. All my users stuck at Applying User Setting after login. I disabled remote desktop network interface for some time, then enabled and all fine. Checked logs in detail and nothing unusual found.
Could anyone assist to avoid recurrence of issue.
Rox_Star

Hi,
Thanks for your comment.
Sorry for late response. How is everything going on?
Does both the issue happens on same server? Is that same server with domain joined?
The above question relates to your other post.
Server stucks at Applying Computer Settings after every reboot
From the issue it seems that DNS server is not getting properly communicate for the server and due to that reason you are getting slow connection response from the DC to connect. If you are using DHCP in your network, you need to check the DHCP server setting
also for properly assigned IP address to the server. You can run “ipconfig /all” and check the DNS setting on your affected server.
In addition to above one, you can edit the registry setting for a test and check the result.
1. Open registry editor with regedit
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP
3. On the Edit menu, point to New, and then click
Multi-string Value.
4. Type DependOnService, and then press ENTER.
5. Right-click DependOnService, and then click Modify.
6. In the Value data box, type CRYPTSVC, and then click OK.
7. Exit Registry Editor.
8. Restart the computer.
Actually there is Hotfix (KB 2379016) for server 2008 but you can try this solution for server 2008 R2.
Hope it helps!
Thanks.
Dharmesh Solanki

MacBook Pro, 10.6.3 hangs after login with external monitor

Howdy:
This is a weird one and if this isn't the correct forum, please let me know.
I have a two year old MBP that I use 99% of the time with a 30" Apple monitor. It has always worked well. Now, if it is attached to the monitor and I log in, the machine just hangs after I put in the password. It does this also in the troubleshooting "blank" account I have. If I shut the machine down and detach the monitor and external drives, it logs me in nicely. (I'm using it now)
I have restarted from the 10.6 install disk and repaired permissions twice. I have reloaded 10.6 and then did the updatede to 10.6.3. I have used Disk Utility and TechToolPro to repair everything and both say all is okay. Still the problem persists. However, when I reloaded 10.6 and updated it, it logged me in with the monitor once and then when I logged out to restart it, it stopped again.
Could it be a problem with 10.6.3 and external monitors? I don't think so as it worked for a while with it before this started.
The only connection I can find is the monitor.
Does anyone have any clue what is going wrong and what I might do to fix it? Thanks

I need to hang my head in shame. The solution, once found was simple and took only seconds and it was merely a software conflict. I should have gotten that one myself but didn't, because, believe it or not, I didn't think the software was running and I simply forgot about it to begin with.
It turns out, I had Intego Software's Virus Barrier on my computer and it was running. I knew I had it, but thought I had disabled it because it was forever throwing a hissy fit every time my Apple TV checked in. Last week, I updated it without thinking. Apparently, that re-enabled it and it was rejecting the internal process change from the machine-wide log-in screen to the account log-in screen.
The point is I should have remembered that I had updated it and I didn't. If I had recalled the change, I would have zeroed in on that before I spent hours at the Genius Bar, befuddling everyone. On the other hand, it was nice to take my 30" monitor for a nice outing.

Very slow boot and hanging after login.

About 2 days ago I put my Mac to sleep by closing the lid. The next day, after waking it up and logging in, I opened Firefox. Then I got the beachbubble which lasted for awhile but then firefox opened. Then I closed Firefox because the beachbubble had me worried, but after closing it I got another beachbubble. I held the power button on my macbook because the whole OS seemed locked up.
Now whenever I boot, I stay at the apple logo screen for atleast 10 minutes, then when I finally reach login, whenever I click on something I get a beachbubble for awhile. If I do login, it seems to hang at the default wallpaper screen, but I can move my mouse.
I don't remember updating or installing anything that might cause problems like this, but I'd like to do a time machine restore back a couple days, however I can't get to my desktop.
Thanks in advance.
I did try resetting the PRAM and NVRAM, twice atleast, I tried Safe Boot, I tried Verbose and Single-User mode. With my experience I couldn't do much in either, however I did type"exit" in Single-User mode, and when "DSMOS has arrived.", nothing happened.
Oh, and I can't boot with only power without the battery, because I have a non-removeable battery, atleast, only Apple is supposed to touch it.

Restart the system from the SL disc you have. If you aren't sure how to do that put it into the DVD drive and restart the computer holding down the Option key, when it comes up choose the disc in the DVD drive. If it attempts to install let it until it gets to the choose language. Once you are on that screen then click the Utilities menu and choose Disk Utility. Once DU is running then choose the internal HD and look for the S.M.A.R.T status. If it says Verified that is a good sign, if it says anything else kiss the HD goodbye. I hope you have a good back up of your system because you will need to replace the internal HD. If the machine is still covered by warranty or AppleCare then contact Apple and arrange for a repair. If the S.M.A.R.T status says the internal HD is Verified then choose Repair Disk, you may have to run this numerous times for it to be repaired.

MBP hangs after login screen with Circle with line through it

Recently, my MBP (Model A1278, MB990LL/A) started doing the "folder with blinking question mark" at start up as if it couldn't find the startup disk.
I held Option at startup and chose the Macintosh HD that it found. After selecting, it brings me to my username/login. I type in the PW and hit enter and the screen turns gray and I see the Apple logo in the middle with spinning gear below it. (All good so far, as this sequence is the same sequence as my other MBP). After about 1min of gear spinning though, the Apple logo changes to a Circle with a line through it. It never logs in and I never see the desktop.
Troubleshooting I've done:
1. Pulled out the HDD, plugged it up to my OTHER MBP and ran Disk Utility on the whole drive. Found no errors.
2. Put the HDD in question in my OTHER MBP and booted into my user account just fine. All the way to Desktop, no problems.
3. Took my WORKING HDD from my OTHER MBP and put it in the MBP in question and tried to boot, did the same thing. Circle with line after logging in.
4. Tried to run Apple Hardware Test from boot cd by holding D but nothing happens. Just gray screen to infinity.
5. Replaced the trackpad from my OTHER MBP just for fun
Any ideas? I'm usually pretty good at this stuff, but this one has me stumped.
Thank you!!!

No luck. I can't do a Safe Reboot, nor can I reset the NVRAM/PRAM. When I power on either 1 of 2 things happen. A) Nothing, grey screen until folder with flashing question mark or B) When it decides to, it finds my HDD and goes to login screen but after entering pw and hitting submit, I get the Apple logo for a minute then replaces with a Circle w/ Line.
Can't hold Shift at reboot, can't hold c to boot from DVD (have to hold Option and choose DVD), can't hold D and boot the Apple Hardware Test DVD.
Does anyone know of a way to reset the NVRAM/PRAM manually? Is there a CMOS battery like on a windows PC or something similar that I can remove to reset? Command+Option+P+R does not work, it reads that I've pressed Option and gives me the Startup Disk Manager screen to select a drive to boot from.
Thanks

Gnome 3.4 sometimes hangs after login

I've been experiencing this issue about 1/3 of the time I have booted my computer since the upgrade to Gnome 3.4. Sometimes I get an unresponsive desktop, where I can move the mouse, but nothing else happens. I am able to switch to tty1, login as root, and restart gdm, which works. Does anyone have suggestions? Any log files I should look at when this happens?

hadrons123 wrote:I don't know. Is there any particular advantage in keeping gdm?
Nothing... it is just a quirk of mine. If i have gnome, i'd rather install gdm over lxdm. However, if lxdm is better than gdm, there's no problem by trying it. Btw, i love lxde. It's just amazing how uncomplicated it is.
Regards,
Jaime

After the latest updat to Mavericks 10.9.3, my imac continues to loop back to the login screen...Suggestions??? THANK YOU VERY MUCH!

After the latest updat to Mavericks 10.9.3, my imac continues to loop back to the login screen...Suggestions??? THANK YOU VERY MUCH!

1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.
2. If you don't already have a current backup, back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.
There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
3. Below are instructions to run a UNIX shell script, a type of program. All it does is to collect information about the state of the computer. That information goes nowhere unless you choose to share it. However, you should be cautious about running any kind of program (not just a shell script) at the request of a stranger. If you have doubts, search this site for other discussions in which this procedure has been followed without any report of ill effects. If you can't satisfy yourself that the instructions are safe, don't follow them. Ask for other options.
Here's a summary of what you need to do, if you choose to proceed:
☞ Copy a line of text in this window to the Clipboard.
☞ Paste into the window of another application.
☞ Wait for the test to run. It usually takes a few minutes.
☞ Paste the results, which will have been copied automatically, back into a reply on this page.
The sequence is: copy, paste, wait, paste again. You don't need to copy a second time. Details follow.
4. You may have started the computer in "safe" mode. Preferably, these steps should be taken in “normal” mode, under the conditions in which the problem is reproduced. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual. If you can only test in safe mode, do that.
5. If you have more than one user, and the one affected by the problem is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.
6. The script is a single long line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, though you may not see all of it in the browser window, and you can then copy it. If you try to select the line by dragging across the part you can see, you won't get all of it.
Triple-click anywhere in the line of text below on this page to select it:
PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/libexec;clear;cd;p=(Software Hardware Memory Diagnostics Power FireWire Thunderbolt USB Fonts 51 4 1000 25 5120 KiB/s 1024 85 \\b%% 20480 1 MB/s 25000 ports 'com.autodesk.AutoCad com.evenflow.dropbox com.google.GoogleDrive' DYLD_INSERT_LIBRARIES\ DYLD_LIBRARY_PATH -86 ` route -n get default|awk '/e:/{print $2}' ` 25 N\\/A down up 102400 25600 recvfrom sendto CFBundleIdentifier 25 25 25 1000 MB );N5=${#p[@]};p[N5]=` networksetup -listnetworkserviceorder|awk ' NR>1 { sub(/^$[0-9]+$ /,"");n=$0;getline;} $NF=="'${p[45]}')" { sub(/.$/,"",$NF);print n;exit;} ' `;f=('\n%s: %s\n' '\n%s\n\n%s\n' '\nRAM details\n%s\n' %s\ %s '%s\n\t(%s)\n' );S0() { echo ' { q=$NF+0;$NF="";u=$(NF-1);$(NF-1)="";gsub(/^ +| +$/,"");if(q>='${p[$1]}')printf("%s (UID %s) is using %s '${p[$2]}'",$0,u,q);} ';};s=(' /^ *$|CSConfigDot/d;s/^ */ /;s/[-0-9A-Fa-f]{22,}/UUID/g;s/(ochat)\.[^.]+(\..+)/\1\2/;/Shared/!s/\/Users\/[^/]+/~/g ' ' s/^ +//;5p;6p;8p;12p;' ' {sub(/^ +/,"")};NR==6;NR==13&&$2<'${p[10]} ' 1s/://;3,6d;/[my].+:/d;s/^ {4}//;H;${ g;s/\n$//;/s: [^EO]|x([^08]|02[^F]|8[^0])/p;} ' ' 5h;6{ H;g;/P/!p;} ' ' ($1~/^Cy/&&$3>'${p[11]}')||($1~/^Cond/&&$2!~/^N/) ' ' /:$/{ s/ *:$//;x;s/\n//;/Apple|Capacity:|Genesy|Intel|SMSC/d;s/\n.*//;/\)$/p;};/^ *(V.+ [0N]|Man).+ /{ s/ 0x.... //;s/[()]//g;s/(.+: )(.+)/ (\2)/;H;} ' ' s/^.*C/C/;H;${ g;/No th|pms/!p;} ' '/= [^GO]/p' '{$1=""};1' ' /Of/!{ s/^.+is |\.//g;p;} ' ' $0&&!/:/;END { if(NR<100)print "com.apple.";} ' ' $3~/[0-9]:[0-9]{2}$/ { gsub(/:[0-9:a-f]{14}/,"");} { print|"tail -n'${p[12]}'";} ' ' NR==2&&$4<='${p[13]}' { print $4;} ' ' END { $2/=256;if($2>='${p[15]}')print int($2) } ' ' NR!=13{next};{sub(/[+-]$/,"",$NF)};'"`S0 21 22`" 'NR==2'"`S0 37 17`" ' NR!=5||$8!~/[RW]/{next};{ $(NF-1)=$1;$NF=int($NF/10000000);for(i=1;i<=3;i++){$i="";$(NF-1-i)="";};};'"`S0 19 20`" 's:^:/:p' '/\.kext\/(Contents\/)?Info\.plist$/p' ' s/^.{52}//;s/ .+//p ' ' /Launch[AD].+\.plist$/;END{if(NR<100)print "/System/";} ' '/\.xpc\/(Contents\/)?Info\.plist$/p' ' NR>1&&!/0x|\.[0-9]+$|com\.apple\.launchctl\.(Aqua|Background|System)$/ { print $3;} ' ' /\.(framew|lproj)|\):/d;/plist:|:.+(Mach|scrip)/s/:[^:]+//p ' '/root/p' ' !/\/Contents\/.+\/Contents|Applic|Autom|Frameworks/&&/Lib.+\/Info.plist$/;END{if(NR<100)print "/System/"};' '/^\/usr\/lib\/.+dylib$/p' '/\/etc\/(auto_m|hosts[^.]|peri)/s/^\.\/[^/]+//p' ' /\/(Contents\/.+\/Contents|Frameworks)\//d;p;' 's/\/(Contents\/)?Info.plist$//;p' ' { gsub("^| ","||kMDItem'${p[35]}'=");sub("^.."," ") };1 ' p '{print $3"\t"$1}' 's/\'$'\t''.+//p' 's/1/On/p' '/Prox.+: [^0]/p' '$2>'${p[9]}'{$2=$2-1;print}' ' BEGIN { i="'${p[26]}'";M1='${p[16]}';M2='${p[18]}';M3='${p[31]}';M4='${p[32]}';} !/^A/ { next;} /%/ { getline;if($5<M1) a="user "$2"%, system "$4"%";} /disk0/&&$4>M2 { b=$3" ops/s, "$4" blocks/s";} $2==i { if(c) { d=$3+$4+$5+$6;next;};if($4>M3||$6>M4) c=int($4/1024)" in, "int($6/1024)" out";} END { if(a) print "CPU: "a;if(b) print "I/O: "b;if(c) print "Net: "c" (KiB/s)";if(d) print "Net errors: "d" packets/s";} ' ' /r\[0\] /&&$NF!~/^1(0|72\.(1[6-9]|2[0-9]|3[0-1])|92\.168)\./ { print $NF;exit;} ' ' !/^T/ { printf "(static)";exit;} ' '/apsd|OpenD/!s/:.+//p' ' (/k:/&&$3!~/(255\.){3}0/ )||(/v6:/&&$2!~/A/ ) ' ' /lR/ { if($2<='${p[25]}')print $2;} ' ' BEGIN { FS=":";} $3~/(sh|ng|ic)$/ { n=split($3,a,".");sub(/_2[01].+/,"",$3);b=b"\n"$2" "$3" "a[n]" "$1;c=c$1;} END { d="sort|tail -n'${p[38]}'";print b|d;close(d);if(c)print("\n\t* Code injection");} ' ' NR!=4{next} {$NF/=10240} '"`S0 27 14`" ' END { if($3~/[0-9]/)print$3;} ' ' BEGIN { L='${p[36]}';} !/^[[:space:]]*(#.*)?$/ { l++;if(l<=L) f=f"\n "$0;} END { F=FILENAME;if(!F) exit;if(!f) f="\n [N/A]";"file -b "F|getline T;if(T!~/^(A.+ E.+ text$|POSIX sh.+ text ex)/) F=F" ("T")";printf("\nContents of %s\n%s\n",F,f);if(l>L) printf("\n ...and %s more line(s)\n",l-L);} ' ' BEGIN{FS="= "} /Path/{print $2} ' ' /^ +B/{ s/.+= |(-[0-9]+)?\.s.+//g;p;} ' ' END{print NR} ' ' /id: N|te: Y/{i++} END{print i} ' ' /:/{$0="'"${p[28]}"'"};1;' '/ en/!s/\.//p' ' NR!=13{next};{sub(/[+-M]$/,"",$NF)};'"`S0 39 40`" );c1=(system_profiler pmset\ -g nvram fdesetup find syslog df vm_stat sar ps sudo\ crontab sudo\ iotop top pkgutil PlistBuddy whoami cksum kextstat launchctl sudo\ launchctl crontab 'sudo defaults read' stat lsbom mdfind ' for i in ${p[24]};do ${c1[18]} ${c2[27]} $i;done;' defaults\ read scutil sudo\ dtrace sudo\ profiles sed\ -En awk /S*/*/P*/*/*/C*/*/airport networksetup mdutil );c2=(com.apple.loginwindow\ LoginHook '-c Print /L*/P*/loginw*' '-c Print L*/P*/*loginit*' '-c Print L*/Saf*/*/E*.plist' '~ $TMPDIR.. $ -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 $' '.??* -path .Trash -prune -o -type d -name *.app -print -prune' '-c Print\ :'${p[35]}' 2>&1' '-c Print\ :Label 2>&1' '{/,}L*/{Con,Pref}* -type f ! -size 0 -name *.plist -exec plutil -s {} \;' "-f'%N: %l' Desktop L*/Keyc*" therm sysload boot-args status "-F '\$Time \$Message' -k Sender kernel -k Message Req 'Beac|caug|dead[^bl]|FAIL|GPU |hfs: Ru|inval|jnl:|last value [1-9]|n Cause: -|NVDA$|pagin|proc: t|Roamed|rror|ssert|Thrott|tim(ed? ?|ing )o|WARN' -k Message Rne 'Goog|ksadm|SMC:' -o -k Sender fseventsd -k Message Req 'SL'" '-du -n DEV -n EDEV 1 10' 'acrx -o comm,ruid,%cpu' '-t1 10 1' '-f -pfc /var/db/*/*.{BS,Bas,Es,OSXU,Rem}*.bom' '{/,}L*/Lo*/Diag* -type f \( -exec grep -lq "^Thread c" {} \; -exec printf \* \; -o -true $ -execdir stat -f:%Sc:%N -t%F {} \;' '-L {/{S*/,},}L*/Lau* -type f' '-L /{S*/,}L*/StartupItems -type f -exec file {} +' '-L /S*/L*/{C*/Sec*A,E}* {/,}L*/{A*d,Compon,Ex,In,iTu,Keyb,Mail/B,P*P,Qu*T,Scripti,Sec,Servi,Spo}* -type f -name Info.plist' '/usr/lib -type f -name *.dylib' `awk "${s[31]}"<<<${p[23]}` "/e*/{auto_master,{cron,fs}tab,hosts,{launchd,sysctl}.conf} /usr/local/etc/periodic/*/* .launchd.conf" list getenv /Library/Preferences/com.apple.alf\ globalstate --proxy '-n get default' -I --dns -getdnsservers -getinfo\ "${p[N5]}" -P -m\ / '' -n1 '-R -l1 -n1 -o prt -stats command,uid,prt' '--regexp --only-files --files com.apple.pkg.*|sort|uniq' -kl -l -s\ / '-R -l1 -n1 -o mem -stats command,uid,mem' );N1=${#c2[@]};for j in {0..8};do c2[N1+j]=SP${p[j]}DataType;done;N2=${#c2[@]};for j in 0 1;do c2[N2+j]="-n ' syscall::'${p[33+j]}':return { @out[execname,uid]=sum(arg0) } tick-10sec { trunc(@out,1);exit(0);} '";done;l=(Restricted\ files Hidden\ apps 'Elapsed time (s)' POST Battery Safari\ extensions Bad\ plists 'High file counts' User Heat System\ load boot\ args FileVault Diagnostic\ reports Log 'Free space (MiB)' 'Swap (MiB)' Activity 'CPU per process' Login\ hook 'I/O per process' Mach\ ports kexts Daemons Agents launchd Startup\ items Admin\ access Root\ access Bundles dylibs Apps Font\ issues Inserted\ dylibs Firewall Proxies DNS TCP/IP RSSI Profiles Root\ crontab User\ crontab 'Global login items' 'User login items' Spotlight Memory );N3=${#l[@]};for i in 0 1 2;do l[N3+i]=${p[5+i]};done;N4=${#l[@]};for j in 0 1;do l[N4+j]="Current ${p[29+j]}stream data";done;A0() { id -G|grep -qw 80;v[1]=$?;((v[1]==0))&&sudo true;v[2]=$?;v[3]=`date +%s`;clear;};for i in 0 1;do eval ' A'$((1+i))'() { v=` eval "${c1[$1]} ${c2[$2]}"|'${c1[30+i]}' "${s[$3]}" `;[[ "$v" ]];};A'$((3+i))'() { v=` while read i;do [[ "$i" ]]&&eval "${c1[$1]} ${c2[$2]}" \"$i\"|'${c1[30+i]}' "${s[$3]}";done<<<"${v[$4]}" `;[[ "$v" ]];};A'$((5+i))'() { v=` while read i;do '${c1[30+i]}' "${s[$1]}" "$i";done<<<"${v[$2]}" `;[[ "$v" ]];};';done;A7(){ v=$((`date +%s`-v[3]));};B2(){ v[$1]="$v";};for i in 0 1;do eval ' B'$i'() { v=;((v['$((i+1))']==0))||{ v=No;false;};};B'$((3+i))'() { v[$2]=`'${c1[30+i]}' "${s[$3]}"<<<"${v[$1]}"`;} ';done;B5(){ v[$1]="${v[$1]}"$'\n'"${v[$2]}";};B6() { v=` paste -d: <(printf "${v[$1]}") <(printf "${v[$2]}")|awk -F: ' {printf("'"${f[$3]}"'",$1,$2)} ' `;};B7(){ v=`grep -Fv "${v[$1]}"<<<"$v"`;};C0(){ test "$v"&&echo "$_";};C1() { [[ "$v" ]]&&printf "${f[$1]}" "${l[$2]}" "$v";};C2() { v=`echo $v`;[[ "$v" != 0 ]]&&C1 0 $1;};C3() { v=`sed -E "$s"<<<"$v"`&&C1 1 $1;};for i in 1 2;do for j in 2 3;do eval D$i$j'(){ A'$i' $1 $2 $3; C'$j' $4;};';done;done;A0;{ A2 0 $((N1+1)) 2;C0;A1 0 $N1 1;C0;B0;C2 27;B0&&! B1&&C2 28;D12 15 37 25 8;A1 0 $((N1+2)) 3;C0;D13 0 $((N1+3)) 4 3;D22 0 $((N1+4)) 5 4;for i in 0 1 2;do D13 0 $((N1+5+i)) 6 $((N3+i));done;D13 1 10 7 9;D13 1 11 8 10;D22 2 12 9 11;D12 3 13 10 12;D23 4 19 44 13;D23 5 14 12 14;D22 6 36 13 15;D22 7 37 14 16;D23 8 15 38 17;D22 9 16 16 18;B1&&{ D22 11 17 17 20;for i in 0 1;do D22 28 $((N2+i)) 45 $((N4+i));done;};D22 12 44 54 45;D22 12 39 15 21;A1 13 40 18;B2 4;B3 4 0 19;A3 14 6 32 0;B4 0 5 11;A1 17 41 20;B7 5;C3 22;B4 4 6 21;A3 14 7 32 6;B4 0 7 11;B3 4 0 22;A3 14 6 32 0;B4 0 8 11;B5 7 8;B1&&{ A2 19 26 23;B7 7;C3 23;};A2 18 26 23;B7 7;C3 24;A2 4 20 21;B7 6;B2 9;A4 14 7 52 9;B2 10;B6 9 10 4;C3 25;D13 4 21 24 26;B4 4 12 26;B3 4 13 27;A1 4 22 29;B7 12;B2 14;A4 14 6 52 14;B2 15;B6 14 15 4;B3 0 0 30;C3 29;A1 4 23 27;B7 13;C3 30;D23 24 24 32 31;D13 25 37 32 33;A1 23 18 28;B2 16;A2 16 25 33;B7 16;B3 0 0 34;B2 21;A6 47 21&&C0;B1&&{ D13 21 0 32 19;D13 10 42 32 40;D22 29 35 46 39;};D23 14 1 48 42;D12 34 43 53 44;D22 0 $((N1+8)) 51 32;D13 4 8 41 6;D12 26 28 35 34;D13 27 29 36 35;A2 27 32 39&&{ B2 19;A2 33 33 40;B2 20;B6 19 20 3;};C2 36;D23 33 34 42 37;D22 32 31 43 38;D23 20 42 32 41;D23 14 2 48 43;D13 4 5 32 1;D22 4 4 50 0;D13 14 3 49 5;D23 22 9 37 7;A7;C2 2;} 2>/dev/null|pbcopy;exit 2>&-
Copy the selected text to the Clipboard by pressing the key combination command-C.
7. Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Click anywhere in the Terminal window and paste by pressing command-V. The text you pasted should vanish immediately. If it doesn't, press the return key.
8. If you see an error message in the Terminal window such as "syntax error," enter
exec bash
and press return. Then paste the script again.
9. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. In most cases, the difference is not important. If you don't know the password, or if you prefer not to enter it, press the key combination control-C or just press return three times at the password prompt. Again, the script will still run.
If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.
10. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, there will be nothing in the Terminal window and no indication of progress. Wait for the line
[Process completed]
to appear. If you don't see it within half an hour or so, the test probably won't complete in a reasonable time. In that case, close the Terminal window and report the results. No harm will be done.
11. When the test is complete, quit Terminal. The results will have been copied to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.
At the top of the results, there will be a line that begins with "Model Identifier." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "Process completed" message to appear in the Terminal window. Please wait for it and try again.
If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.
12. When you post the results, you might see the message, "You have included content in your post that is not permitted." It means that the forum software has misidentified something in the post as a violation of the rules. If that happens, please post the test results on Pastebin, then post a link here to the page you created.
Note: This is a public forum, and others may give you advice based on the results of the test. They speak only for themselves, and I don't necessarily agree with them.
Copyright © 2014 by Linc Davis. As the sole author of this work, I reserve all rights to it except as provided in the Use Agreement for the Apple Support Communities website ("ASC"). Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

Oracle AS control hangs after user login - AIX 5.3

Hi,
We are engaged with a customer who deploys OracleAS 10.1.2.0.2 on AIX 5.3. After installation, AS control hangs after user logins. This issue is addressed in release note and metalink doc365725.1. We followed the guide in metalink to do the modification and we can access AS control successfully after that. However, due to some other reasons, we restart the AIX, and after that AS control hangs again. This is quite strange. Does anyone meet with this symptom before? How can we resolve this issue?
Thanks in advance.
Sindhiya V.

Thanks everyone for the response and help.
I completed the task yesterday with the permission method. However, I think I found the solution after completion. The trick lies at the oraInst.loc file. It lies at /etc directory for my case (AIX 5.3).
If you do a opatch lsinventory, it shows you the Central Inventory location and the location of orainst.loc. For my case, it is pointing to /oracle/DE1/920_64/inventory. Therefore, even though I am logging in as oraqa1 with all env and oracle settings correct, it still points to DE1 inventory.
I think modifying the Central inventory location in oraInst.loc will solve this problem.

HT3964 My MacBook Air running on Snow Leopard gets extremely slow (almost like a hang, except if you wait about half an hr, it actually moves) after login interface. sometimes it never gets past the background. Cannot log back in.

My MacBook Air running on Snow Leopard gets extremely slow (almost like a hang, except if you wait about half an hr, it actually moves) after login interface. Sometimes it never gets past the background of the homepage, desktop doesn't seem to load. After multiple forced shut downs and left to run for hours, sometimes the desktop loads but the dock does not respond when applications are opened. The computer is then unable to shut down normally. Forced shut downs are necessary most times. Time machine backup takes extremely long, and attempts to use the time machine to bring the laptop back to the time befiore the problem arose was met with extremely slow and hung time machine function.
Please help!

There isn't much besides a failing hard drive or other hardware fault that can cause those symptoms. Run the Apple Hardware Test, or just take it to an Apple Store for testing.

How do I fix Mountain Lion issue after login where Keychain Access attempts to open, hanging up with "application not responding" message?

How do I fix Mountain Lion issue after login where Keychain Access attempts to open, hanging up with "application not responding" message?

You could try booting into Safe Mode to see if that will help. And "Repair Permissions" in Disk Utility.
Have you got Keychain set to open on Login or is it attempting to open on it's own.

Audigy 2: Windows XP hang at login after new drivers instal

Hi All,
I have found that after installing the latest version of the Audigy 2 drivers (<span class="Apple-style-span">SBAX_PCDRV_LB_2_8_000) on my Windows XP SP2, sound works just before you reboot after installation. After the installation reboot, and after you enter your password at the login screen, you hear the logon-sound, and after that XP freezes.
I have booted into Safe mode and disabled all startup items, and Windows then boots normally. However, when I try to narrow down the fault by selecti'vely re-enabling some of the Startup items, it then hangs again (no matter which ones I enable).
So far, the only successful startup config consists of only the CT startup items being enabled.
If I enable ANYTHING (even a single different item each time) else Windows hangs again.
The only solution is to select "Restore last good known configuration" before Windows boots up. Undoing the driver installation using System restore, does NOT help.
Anyone with any ideas?
Thanks?

UPDATE: Just updated to SP3 and guess what? Windows hangs at login as before, despite the fact that I was using the older, up to now fully working, drivers.
Solution? Simple! Throw the card in the bin, and enable the onboard soundcard. END of problems! These people at Creative are completely USELESS...Not wasting any more of my time on their crappy products (and programming).
++?
Hi there,
Thanks for the reply; I have already gone back to?<span class="Apple-style-span">SBAX_WBUP2_LB_2_09_006<span class="Apple-style-span">?which seems to be working OK.
The point is however that part of the new release does not work, and I am convinced that it is related to some 'helper' application and not the main driver itself.
Anyone else having similar trouble?
Thanks?
Message Edited by lordbyte on 08-02-2008 02:04 PM

Macbook pro stuck/hangs at login screen ??

Macbook pro stuck/hangs at login screen and no any controls while i restart last time..3 days before i found many solutions but no one is perfect like PRAM/SCM format command option+p+r and other many but no any perfect solution which can fixed my issue..please help me asap i am so much upset for that coz i am developer and there is many of the data , i also run windows on it win 7 so now i am running with that i have latest 2011 mac OSX 10.7.5 with Core i5 ,4GB, 320 GB so please help me to resolve this issue i am waiting thanks in advan
Regards,
Muneeb
Developer
<Email Edited by Host>

Macbook pro stuck/hangs at login screen and no any controls while i restart last time..3 days before i found many solutions but no one is perfect like PRAM/SCM format command option+p+r and other many but no any perfect solution which can fixed my issue..please help me asap i am so much upset for that coz i am developer and there is many of the data , i also run windows on it win 7 so now i am running with that i have latest 2011 mac OSX 10.7.5 with Core i5 ,4GB, 320 GB so please help me to resolve this issue i am waiting thanks in advan
Regards,
Muneeb
Developer
<Email Edited by Host>

Stuck on white screen after login

My 13" macbook pro is stuck on the white screen "after" the user login page. It started happening after installing the latest update then gave me a "start up disc is full error also. I know to clean up unnecessary files but can't do that when it's stuck before I can get to a point where I can access them. Any Ideas and help would be great.
Thanks
RH

Try a PRAM reset:
Power off, power on holding the following keys:
OPTION+COMMAND+P+R
Continue to hold thee keys till you here the start chime 2 times hen release.

MacBook Pro mid 2013 13' gets stuck on White screen after login.

I'm in safe mode right now. I Booted it up in Safe Mode by holding down the shift key during startup. What do I do now to not get the white/grey screen during startup after login?

Mac OS X: Gray screen appears during startup
If the grey screen occurs when you boot normally (not safe mode) try bypassing your Login Items by holding a Shift key in the same manner during login (i.e. not during boot). If you can log in, you effectively isolated the problem to one of more of your Login Items.

New iMac is stuck on grey apple screen after restart from Migration Assistant

New iMac is stuck on grey apple screen after startup. It is a 3.4GHz Quad-core Intel Core i5 running OS 10.9.4. The problem occurred after a migration from my older 2009 iMac which is running Snow Leopard 10.6.6. When the restart occurred from Migration Assistant, the new computer will not boot up to the login screen. Disk utility did not solve problem. Followed instructions for a soft reinstall of Mavericks but that also did not solve problem. Any suggestions?

Take each of these steps that you haven't already tried. Stop when the problem is resolved.
Step 1
The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
Step 3
Sometimes a startup failure can be resolved by resetting the NVRAM.
Step 4
If you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
Step 5
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 6
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
Step 7
If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
Start up in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 8
Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
Step 9
If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.
Step 10
Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 11
Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
Step 12
This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 13
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

Stuck in "loop" or "hang" after login

Similar Messages

Maybe you are looking for