Strange Yosemite Glitches

Hi,
Ever since updating my Late 09 iMac to 10.10 I've noticed a few annoying issues. Though small are causing me a headache.
The first one is that my iMacs network name keeps changing by the day. It was 'iMac' now its 'iMac (2)' to the be followed with an ever increasing number. Every time I rename it it just renames its self again a few days after. Its causing a few issues on my network as well.
The second its that I'm using my flagged iPhone library as my screen saver, however 10.10 forgets this after a few hours and sets it to a the default nature images. I have reset my screensaver countless times today and it just forgets it after a few hours.
The third and most annoying is that since updating to 10.10 my recovery partition has remained 10.9. Which means I cannot recover my computer from that drive. How do you update the recovery drive?
Any help on any of these issue would be great.
Thanks

Similar Messages

Strange graphical glitch on 55TL515

I'm getting a strange graphical glitch occasionally on my 55TL515. When the glitch appears, it will reoccur every 20 seconds or so. I've discovered one way to make this disappear temporarily, but I'd like a permanent fix. Let me describe my living room setup for a second...
I currently have the TV connected by itself to one outlet. The second socket is currently empty.
In another outlet, I have a filled power bar plugged in. The power bar contains my stereo, xbox, pc, macbook, external hdd, and router.
When the glitch appears, if I unplug this power bar and reconnect it, the glitch disappears. I don't understand why this is. They aren't even in the same outlet (they used to be, until i started messing around with this problem). I've tested different HDMI cords, all of the HDMI inputs, and have seen this glitch when using both my pc and my xbox on this tv.
Can anyone provide a possible solution to this? I don't want to keep everything unplugged as I use them all frequently. Could it be the power bar? Is it actually a problem with the tv? Please take a look at this youtube video and see what you think. Thanks.
http://www.youtube.com/watch?v=ehR4cALs8co&feature=youtu.be

I get the same issue...typically this happens if I connect my laptop through a VGA cable. I've tried everything from changing my video card settings(resolution, refresh rate, etc...) but I get the same exact graphical glitch. Any luck on figuring this out?
Also, do you ever get thin lines that roll/move up the screen? I would get those occasionally and it had something to do with the digital switching inside the laptop power supply(the laptop power supply was on the same outlet) and was causing this problem so moving it to another power outlet or circuit breaker helped, but I still get the graphical glitch you have.

Strange graphical glitch in Select Columns

I've noticed a strange graphical glitch in the Select Columns region of an interactive report when using IE7 or 8.
When a column is selected (other than the first or last) and sent to the Bottom or Top the change doesn't actually show until the mouse is moved over the Display in Report List. If the Apply button is clicked, then the column ordering is set correctly.
I'm using Apex 3.1 and was wondering if anyone else has noticed.
Thanks,
Simon

alright.. once again a nvidia isssue... the nv driver does paint it correctly

Shattered glass strange graphical glitch

I've been having this strange thing happen every once in a while on my imac. Sometimes when randomly when you move the mouse the screen changes to look like multicolored slivers. the only way I can describe it is as multicolored "shattered glass". As you move the mouse it changes colors and such. The only work around I've discovered so far is to open dashboard several times and it disappears. Any help is appreciated.

I get the same issue...typically this happens if I connect my laptop through a VGA cable. I've tried everything from changing my video card settings(resolution, refresh rate, etc...) but I get the same exact graphical glitch. Any luck on figuring this out?
Also, do you ever get thin lines that roll/move up the screen? I would get those occasionally and it had something to do with the digital switching inside the laptop power supply(the laptop power supply was on the same outlet) and was causing this problem so moving it to another power outlet or circuit breaker helped, but I still get the graphical glitch you have.

Strange graphical glitch in kde4 [SOLVED]

hi... as the topic says i came across this strange looking issue in kde:
http://carnager.dyndns.org/~carnager/glitch.png
this is without 3d acceleration. Also affected are text input fields, where sometimes the written text is messed up.
Last edited by Rasi (2008-08-25 08:10:30)

alright.. once again a nvidia isssue... the nv driver does paint it correctly

OS X Yosemite Glitches in PS. HELP!

After my recent upgrade to OS X Yosemite, I'm experiencing frequent and consistent glitches in PS. 1. The healing brush is painfully slow. 2. I can no longer toggle between foreground and background colors using the "X" key. I've tried resetting my tools to no avail. These issues are most definitely related to the upgrade as they presented immediately afterward and were not present before. This having a very negative effect on my workflow. Any suggestions?

Thank you Chris. CS 6 (Master Collection) 13.0.6 x 64. Haven't had any other issues with OS X Yosemite. I like all the other improvements that have come with it and would really hate to downgrade. Hoping it's a PS compatibility issue with Adobe that will be resolved soon.
More specifically on the above problems:
Healing brush - delays after each stroke. Brush remains visible (as a black mark) without revealing the result until I move to a new area/stroke. Prior to OS X, updates were immediately visible, without delay, after stroking the healing brush.
Foreground/Background Toggle using keyboard shortcut of "X" - I typically use this when painting on a layer mask. Worked flawlessly prior to OS X. Now, I have to manually toggle foreground/background or click on different tool and then back to the brush again, before "X" will act as a shortcut to toggle foreground/background.

OS X yosemite glitches NEED HELP

Once I've up graded to OS X Yosemite Ive noticed multiple problems:
I can only start my computer in SAFE MODE (computer does not work normally)
When the loading screen comes up it FREEZES (everything freezes)
when logging in (freezes)
after typing my password the loading bar doesnt even load all the way and it freezes
when on safe mode half my screen is blinking
also no sound
I've restarted my computer countless times, same thing over and over I cannot use my computer. anyone know what I should do? this is tiring
not sure if im the only one with this problem but hope someone can help

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.
Don't be put off by the complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.
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. As I wrote above, it changes nothing. It doesn't send or receive any data on the network. All it does is to generate a human-readable report on the state of the computer. That report goes nowhere unless you choose to share it. If you prefer, you can act on it yourself without disclosing the contents to me or anyone else.
You should be wondering whether you can believe me, and whether it's safe to run a program at the behest of a stranger. In general, no, it's not safe and I don't encourage it.
In this case, however, there are a couple of ways for you to decide whether the program is safe without having to trust me. First, you can read it. Unlike an application that you download and click to run, it's transparent, so anyone with the necessary skill can verify what it does.
You may not be able to understand the script yourself. But variations of the script have been posted on this website thousands of times over a period of years. The site is hosted by Apple, which does not allow it to be used to distribute harmful software. Any one of the millions of registered users could have read the script and raised the alarm if it was harmful. Then I would not be here now and you would not be reading this message.
Nevertheless, if you can't satisfy yourself that these instructions are safe, don't follow them. Ask for other options.
4. 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.
5. 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.
6. 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.
7. 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 SerialATA 4 1000 25 5120 KiB/s 1024 85 \\b%% 20480 1 MB/s 25000 ports ' com.clark.\* \*dropbox \*genieo\* \*GoogleDr\* \*k.AutoCAD\* \*k.Maya\* vidinst\* ' 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 ' com.adobe.AAM.Updater-1.0 com.adobe.CS4ServiceManager com.adobe.CS5ServiceManager com.adobe.fpsaud com.adobe.SwitchBoard com.apple.AirPortBaseStationAgent com.apple.installer.osmessagetracing com.apple.SafariNotificationAgent com.apple.usbmuxd com.apple.xprotectupdater com.google.keystone.agent com.google.keystone.daemon com.microsoft.office.licensing.helper com.oracle.java.Helper-Tool com.oracle.java.JavaUpdateHelper ' ' 879294308 3627668074 1083382502 1274181950 1855907737 464843899 1233118628 2636415542 842973933 4019080058 3301885676 891055588 998894468 695903914 1443423563 ' 51 5120 files );N5=${#p[@]};p[N5]=` networksetup -listnetworkserviceorder|awk ' NR>1 { sub(/^$[0-9]+$ /,"");n=$0;getline;} $NF=="'${p[26]}')" { 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=(' s/[0-9A-Za-z._]+@[0-9A-Za-z.]+\.[0-9A-Za-z]{2,4}/EMAIL/g;/faceb/s/(at\.)[^.]+/\1NAME/g;/\/Shared/!s/(\/Users\/)[^ /]+/\1USER/g;s/[-0-9A-Fa-f]{22,}/UUID/g;' ' s/^ +//;/de: S|[nst]:/p;' ' {sub(/^ +/,"")};/er:/;/y:/&&$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/) ' ' /:$/{ N;/:.+:/d;s/ *://;b0'$'\n'' };/^ *(V.+ [0N]|Man).+ /{ s/ 0x.... //;s/[()]//g;s/(.+: )(.+)/ (\2)/;H;};$b0'$'\n'' d;:0'$'\n'' x;s/\n\n//;/Apple[ ,]|Genesy|Intel|SMSC/d;s/\n.*//;/\)$/p;' ' s/^.*C/C/;H;${ g;/No th|pms/!p;} ' '/= [^GO]/p' '{$1=""};1' ' /Of/!{ s/^.+is |\.//g;p;} ' ' $0&&!/ / { n++;print;} END { split("'"${p[41]}"'",b);for(i in b) print b[i];if(n<10) 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{next}'"`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}(.+) <.+/\1/p' ' /Launch[AD].+\.plist$/ { n++;print;} END { split("'"${p[41]}"'",b);for(i in b) print b[i]".plist";if(n<200) 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$/ { n++;print;} END { if(n<1100) print "/System/";} ' '/^\/usr\/lib\/.+dylib$/p' ' /Temp|emac/{next};/(etc|Preferences|Launch[AD].+)\// { sub(".(/private)?","");n++;print;} END { split("'"${p[41]}"'",b);split("'"${p[42]}"'",c);for(i in b) print b[i]".plist\t"c[i];if(n<500) print "Launch";} ' ' /\/(Contents\/.+\/Contents|Frameworks)\/|\.wdgt\/.+\.([bw]|plu)/d;p;' 's/\/(Contents\/)?Info.plist$//;p' ' { gsub("^| |\n","\\|\\|kMDItem'${p[35]}'=");sub("^...."," ") };1 ' p '{print $3"\t"$1}' 's/\'$'\t''.+//p' 's/1/On/p' '/Prox.+: [^0]/p' '$2>'${p[43]}'{$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|BKAg|OpenD/!s/:.+//p' ' (/k:/&&$3!~/(255\.){3}0/ )||(/v6:/&&$2!~/A/ ) ' ' $1~"lR"&&$2<='${p[25]}';$1~"li"&&$3!~"wpa2";' ' BEGIN { FS=":";p="uniq -c|sed -E '"'s/ +\$[0-9]+\$\$.+\$/\\\2 x\\\1/;s/x1$//'"'";} { n=split($3,a,".");sub(/_2[01].+/,"",$3);print $2" "$3" "a[n]$1|p;b=b$1;} END { close(p);if(b) 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]";"cksum "F|getline C;split(C, A);C="checksum "A[1];"file -b "F|getline T;if(T!~/^(AS.+ (En.+ )?text(, with v.+)?$|(Bo|PO).+ sh.+ text ex|XM)/) F=F" ("T", "C")";else F=F" ("C")";printf("\nContents of %s\n%s\n",F,f);if(l>L) printf("\n ...and %s more line(s)\n",l-L);} ' ' s/^ ?n...://p;s/^ ?p...:/-'$'\t''/p;' 's/0/Off/p' ' END{print NR} ' ' /id: N|te: Y/{i++} END{print i} ' ' / / { print "'"${p[28]}"'";exit;};1;' '/ en/!s/\.//p' ' NR!=13{next};{sub(/[+-M]$/,"",$NF)};'"`S0 39 40`" ' $10~/\(L/&&$9!~"localhost" { sub(/.+:/,"",$9);print $1": "$9;} ' '/^ +r/s/.+"(.+)".+/\1/p' 's/(.+\.wdgt)\/(Contents\/)?Info\.plist$/\1/p' 's/^.+\/(.+)\.wdgt$/\1/p' ' /l: /{ /DVD/d;s/.+: //;b0'$'\n'' };/s: /{ /V/d;s/^ */- /;H;};$b0'$'\n'' d;:0'$'\n'' x;/APPLE [^:]+$/d;p;' ' /^find: /d;p;' "`S0 44 45`" ' BEGIN{FS="= "} /Path/{print $2} ' ' /^ *$/d;s/^ */ /;' ' /:/d;/\./p;' '/\.appex\/Contents\/Info\.plist$/p' );c1=(system_profiler pmset\ -g nvram fdesetup find syslog df vm_stat sar ps sudo\ crontab sudo\ iotop top pkgutil 'PlistBuddy 2>&1 -c "Print' 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 sudo\ lsof test osascript\ -e );c2=(com.apple.loginwindow\ LoginHook '" /L*/P*/loginw*' "'tell app \"System Events\" to get properties of login items'|tr , \\\n" 'L*/Ca*/com.ap*.Saf*/E*/* -d 1 -name In*t -exec '"${c1[14]}"' :CFBundleDisplayName" {} \;|sort|uniq' '~ $TMPDIR.. $ -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 $' '.??* -path .Trash -prune -o -type d -name *.app -print -prune' :${p[35]}\" :Label\" '{/,}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 'bad |Beac|caug|corru|dead[^bl]|FAIL|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:|suhel| VALI|ver-r|xpma' -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/r*/com.apple.*.{BS,Bas,Es,J,OSXU,Rem,up}*.bom' '{/,}L*/Lo*/Diag* -type f -regex .\*[cght] ! -name .?\* ! -name \*ag \( -exec grep -lq "^Thread c" {} \; -exec printf \* \; -o -true $ -execdir stat -f:%Sc:%N -t%F {} \;|sort -t: -k2 |tail -n'${p[38]} '/S*/*/Ca*/*xpc* >&- ||echo No' '-L /{S*/,}L*/StartupItems -type f -exec file {} +' '-L /S*/L*/{C*/Sec*A,Ex}* {/,}L*/{A*d,Ca*/*/Ex,Co{mpon,reM},Ex,In{p,ter},iTu*/*P,Keyb,Mail/B,Pr*P,Qu*T,Scripti,Sec,Servi,Spo,Widg}* -path \\*s/Resources -prune -o -type f -name Info.plist' '/usr/lib -type f -name *.dylib' `awk "${s[31]}"<<<${p[23]}` "/e*/{auto,{cron,fs}tab,hosts,{[lp],sy}*.conf,mach_i*/*,pam.d/*,ssh{,d}_config,*.local} {,/usr/local}/etc/periodic/*/* /L*/P*{,/*}/com.a*.{Bo,sec*.ap}*t {/S*/,/,}L*/Lau*/*t .launchd.conf" list getenv /Library/Preferences/com.apple.alf\ globalstate --proxy '-n get default' -I --dns -getdnsservers\ "${p[N5]}" -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' '+c0 -i4TCP:0-1023' com.apple.dashboard\ layer-gadgets '-d /L*/Mana*/$USER&&echo On' '-app Safari WebKitDNSPrefetchingEnabled' "+c0 -l|awk '{print(\$1,\$3)}'|sort|uniq -c|sort -n|tail -1|awk '{print(\$2,\$3,\$1)}'" 'L*/P*/com.ap*.p*.ext*.*.*t -exec '"${c1[14]}"' :displayOrder" {} \;' );N1=${#c2[@]};for j in {0..9};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 XPC\ cache Startup\ items Admin\ access Root\ access Bundles dylibs Apps Font\ issues Inserted\ dylibs Firewall Proxies DNS TCP/IP Wi-Fi Profiles Root\ crontab User\ crontab 'Global login items' 'User login items' Spotlight Memory Listeners Widgets Parental\ Controls Prefetching SATA Descriptors appexes );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 >&-;date '+Start time: %T %D%n';};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() { [[ "$v" ]]&&sed -E "$s"<<<"$v";};C1() { [[ "$v" ]]&&printf "${f[$1]}" "${l[$2]}" "$v"|sed -E "$s";};C2() { v=`echo $v`;[[ "$v" != 0 ]]&&C1 0 $1;};C3() { v=`sed -E "${s[63]}"<<<"$v"`&&C1 1 $1;};for i in 1 2;do for j in 0 2 3;do eval D$i$j'(){ A'$i' $1 $2 $3; C'$j' $4;};';done;done;{ A0;D20 0 $((N1+1)) 2;D10 0 $N1 1;B0;C2 27;B0&&! B1&&C2 28;D12 15 37 25 8;A1 0 $((N1+2)) 3;C0;D13 0 $((N1+3)) 4 3;D23 0 $((N1+4)) 5 4;D13 0 $((N1+9)) 59 50;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 35 49 61 51;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;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;B3 4 0 65;A3 14 6 32 0;B4 0 16 11;A1 4 50 64;B7 16;C3 52;D13 24 24 32 31;D13 25 37 32 33;A2 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 62 42;D12 34 43 53 44;D12 22 20 32 25;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;B1&&D23 35 45 55 46;D23 32 31 43 38;D12 36 47 32 48;D13 20 42 32 41;D13 37 2 48 43;D13 4 5 32 1;D13 4 3 60 5;D12 26 48 49 49;B3 4 22 57;A1 26 46 56;B7 22;B3 0 0 58;C3 47;D22 4 4 50 0;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.
8. 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.
9. If you see an error message in the Terminal window such as "Syntax error" or "Event not found," enter
exec bash
and press return. Then paste the script again.
10. 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.
11. 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 what happened. No harm will be done.
12. 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 the words "Start time." 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.
13. When you post the results, you might see an error message on the web page: "You have included content in your post that is not permitted," or "You are not authorized to post." That's a bug in the forum software. Please post the test results on Pastebin, then post a link here to the page you created.
14. 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.

Strange Graphical Glitches For Both Arch and Archbang

So here is the issue. In 3 diffrent arch installs and my new archbang install, I have been plagued by a strange glitch that seems to persist. This glitch has a few diffrent varitations, the most prevalent being the screen wrapping from an uncentered end to the other side. Here are some pictures to clarify.
Arch
====
http://imgur.com/qOJWdR5
http://imgur.com/ECU4FpU
Archbang
=======
http://imgur.com/kGqG1Y7
The other variations of the error are as follows:
==============================
-A flickering screen after grub bootup, highly distorted.
-A black screen after grub bootup and intitial system processes.
-The same error, but with the rift closer to the middle of the screen.
-A normal bootup
Here are some system specs as well
===================
Ram- 4 gigs of corsair vengance
Cpu- AMD Phenom II x4 965
Graphics card- Raedon HD6670
The screen for my mint and archbang live usbs are just fine. The screen during the initial install is usually just fine as well. I am postulating that this error is arch-specific, as my old ubuntu and mint installs never had this problem. I am also curious because for my arch installs, even before I installed graphics drivers and mesa and whatnot, I still would get the error. Other then this strange glitch, my arch based operating systems would work just fine and dandy.
Here are some fixes I tried
==================
-Adjusting my monitor- This seemingly obvious fix did abslolutely nothing. It would move the screen over, but a black space would appear where the screen was, almost as if I tried doing the same thing with a fixed screen..
-Installing a display manager (this was in arch)- The screen was still glitched over
-Trying a new monitor- The same glitch happened, although both monitors are the exact same Dell monitor, and the only distinguishing feature is the size.
Here are some theories I have
====================
-The most likely issue is my graphics card itself, as Raedon and Linux tend to have issues as I have heard.
-A corrupted iso file in my live usb (this is highly unlikely since most of the arch install process is done via downloading files from the web). However I used the same flashdrive for both live usbs. I made the archbang one by formatting the previous arch live usb (in FAT32) and then using the dd method.
-A possible monitor size issue, but I feel as though this is highly unlikely
-A corrupted HDD (this is just me grasping at straws, therefore this possibilty is possible, but highly unlikely as other symptoms would have presented themselves).
Does anybody have any idea what to do at this point?

fak9r wrote:
I'm having a very similar problem. I tried installing Arch on a laptop of mine I'm not really using anymore, and every time I'm either trying to startx or startxfce4 my screen looks like this: http://imgur.com/7wZohhw.png (sorry for the blurry image).
As you can see only roughly 40% of the screen are drawn at the top of the monitor, whereas the bottom 60% are artifacts. Note that the system is perfectly responsive, the right click context menu opens up etc. It is safe to assume that this is not a hardware error since the device was running a Win7 installation flawlessly just 2 hours ago. The laptop in question is a stock ASUS X7BJN with a built-in Nvidia GTX 425M graphics card. I tried switching from proprietary Nvidia drivers to the nouveau ones, however all that does is forcing the X server to terminate on startup (no devices detected, etc.). Forcing vesa in the boot options didn't help either.
I can't even play around with the xorg.conf since this will lead me to the same error as above (no devices), I have to delete xorg.conf every time I want to get X running in the first place.
Hooking up an external monitor and trying to move the alignment did nothing for me, same as OP. Unforunately the solution proposed here won't work for me since I don't have an AMD card.
While I do not know much about nvidia graphics cards, I do know that the command that I entered into the grub boot (and made persistant through other means) was a command that edited the power profile of my graphics card. It was suggested to me earlier to edit the power profile, but it didn't work because I didn't mkconfig the changes. However, it would have (in theory) worked. Perhaps you need to find a way to edit your nvidia graphcis driver power profile, and tinker with it until you find a setting that works.

Strange screen "glitch," during start-up.

I am a little concerned about my brand new MBP, though everything else seems to be working fine.
When I start-up and the grey apple screen comes up, and the gear icon finishes spinning, as the screen switches to blue, there is a strange glitch. The screen flashes briefly, and the apple appears for a millisecond, offset an inch or so to the right, and then the start-up finishes normally.
There is also a similar "glitch,' when starting up in Vista on the MBP's bootcamp partition.
Windows starts up, but as the final screen loads after logging in, the screen flashes off/on very briefly before Vista finishes loading it's welcome folder, window.
Again, everything else seems to be working fine. Hardware tests show all is normal, no permissions errors, no disk utility repairs needed, and no problem files found with Diskwarrior.
I have also previously run an archive and install of Leopard, to deal with another earlier issue. Still the glitch...
Anyone else experience this, or have any answers.

i just experienced something similar. BRAND NEW MBP with tons of problems running leopard. my computer ran out of power completely last night because i forgot my power adaptor, so when i plugged it in this morning, and opened the case, i saw a totally gray screen that lasted for about 15 seconds, when it flashed into my desktop with all the applications i had opened when it lost power, HOWEVER, it was also grayed out with a strange meter (much like the ones that pop up for brightness or volume) filling slowing in white. After about 15 seconds of that, the screen un-grayed and looked normal EXCEPT for the top toolbar with the time, power, etc had a ton of tiny black glitchy lines through it and i couldn't see any of the information. the rainbow pinwheel was turning and turning forever and ever when that stopped and i was able to click on the desktop. at that time the glitchness disappeared and everything went back to "normal". Except for the fact that my keyboard stopped working! and i had to reboot. the black glitchy lines worry me.

Very strange Yosemite/Macbook Pro crash

Last night I tried to wake my Macbook, as usual, from sleep by typing in may password. The computer stayed on the lock screen. Eventually I decided to reboot, but then the progress bar at startup would reach about 1/3 and just hang. I tried the following (in this order):
* PRAM reset. Did not help
* Reinstalled Yosemite - it took forever (almost 90 min) and still would not start (1/3 progress bar)
* Eventually tried a restore from Time Machine. That ran overnight but seems to have fixed the problem.
Does anybody know:
* What might have caused the initial crash?
* Why a re-install would not work?
* Another (quicker) way that I might have tried to get my system back?

OK - It happened again.
It seems to sop somewhere around 802.11 setup. The last messages I receive are:
IO80211Interface::efiNVRAMPublished()
bpfAttach len 64 dlt 12
So far I can recover using an NVRAM reset. Apple Hardware Dignostics claim no errors.

Strange Screen Glitches Starting Up

Sometimes when I power on my MacBook Pro, the screen is blank or has strange vertical lines in it. I think the LCD screen is bad. If you lightly press on the bottom corner of the screen, the problem usually goes away. If you lightly press on the bottom corner when it's fine, sometimes it will make the screen go blank and have the lines. Is this a known problem? I'm afraid to send it in for repair and have them not be able to reproduce the problem, as it only happens sometimes. I have included a link to a picture I took of the screen messed up.
http://img393.imageshack.us/img393/9965/nonamekv0.jpg

Welcome to Apple Discussions!
There actually is a similar thread called "Strange Vertical Stripes" which you might want to look at, although your vertical stripes look different from the ones I saw posted last time I looked. But your issue could be related, as I think the others happened in the same way as yours did. This is a huge thread and you might want to take a look at it. There has been some thought that it might be fixable with a firmware update but I don't really know. You might run the extended version of the Apple Hardware Test to see if anything shows up--if you get an error code, that would be something very specific to tell Apple.
Good luck!

Strange Software Glitch With Bluetooth

Okay, this is hardly a big deal but thought someone at apple would want to know... if I am in my car and I go to email search and begin typing in the search box, the car's bluetooth activates and thinks I am having a phone conversation. When I click out of the search box the call "hangs up." I do not use a bluetooth headset so I do not know if it has a similar effect there.
PS Apologies if someone has already posted on this subject. I did not find it when I did a search.
PPS No, I do not email when I am driving but noticed it when I was in the parking lot waiting for someone.

Got it now. Thanks for taking the time to explain. Sorry to be so dense.
Now, I do some DivX compression and most Projects are over that Duration. To date, I've never seen a problem with them, nor have I heard of any client having this issue. Though I might have missed it, especially if my Sequence looked good in PrPro and then my DVD looked good. I might have shipped the DivX with similar glitches, but would think that one client would have yelled at me, if I had the same thing. Have not done any H.264 compression yet, but will now keep an eye out.
I am assuming that you're using the DivX Corp's Pro encoder to do the compression to that CODEC. I do know that they have a couple of newer versions, than what I've got. You might want to check your version numbers against what is being offered on their site. If you're using some other program to do the compression, you might want to try the DivX Corp's encoder. That would still not explain why/how you get this in both encoding schemes though. Just thinking aloud.
Good luck, and if I run across similar, especially if there is a fix, or a workaround, I'll post to this thread.
Hunt

Strange Yosemite Invisible vs Pink/Rose color in whole system where transparency exist

I have retina 13" late 2013 and 10.9.My display start showing transparency icons and content like rose color .Call suport but after all types of reseting everything posible I was thinking that after I upgrade system to Yosemite will solve the problem.But like you see in the picture it is ROSE/PINK again.
Any sugestion please.

I have retina 13" late 2013 and 10.9.My display start showing transparency icons and content like rose color .Call suport but after all types of reseting everything posible I was thinking that after I upgrade system to Yosemite will solve the problem.But like you see in the picture it is ROSE/PINK again.
Any sugestion please.

Strange Graphics Glitches Occurring Randomly

For the past 10 months or so, I've been getting these random screen anomalies on my monitor. They normally don't appear until after the computer has been turned on for awhile. The longer the computer is on, the more frequent they appear. They almost always occur when a new window from an application is created. They remain in the same position even if I scroll up and down. The only way I can get rid of them is if I close the window and open a new one. I've had this occur in both Leopard and Snow Leopard including the 10.6.3 update.
Does anyone know what's causing this? Is it my graphics card or a software issue? I've repaired permissions and run Diskwarrior but that doesn't seem to make a difference. I have a 2006 Mac Pro.
Here is a capture of one of the glitches in the lower left of my iTunes window.
http://dl.dropbox.com/u/538897/forums/graphics_glitch.jpg

I'm getting the same thing. I did the Disk troubleshooting and everything came up ok. Then I thought maybe it was a OS thing, so I upgraded to Snow Leopard. Didn't help. Now I'm thinking of upgrading video cards.
My display goes black some times, and the OS freezes. Don't know if maybe that is video related as well.
We'll see. Can't wait to hear and answer on this problem.

Strange Audio Glitch With Volume Adjust

When I hit the volume keys on the keyboard to adjust the volume, there is a delay that I do not get when doing the same with my desktop system. There is also an audible click on the audio when the volume is adjusted. If I go to audio preferences and then use the same keys to adjust the volume, the click and delay goes away. When I leave audio preferences the problem is still fixed for at least awhile. Rebooting brings back the annoying click and delay and I think it comes back after awhile whether the computer is rebooted or not. I have experimented with turning the audible response to volume changes on and off and this has no effect on the problem other than the problem goes away because sound preferences have been opened to make the change and not because of what the setting is. I think the problem must have to do with the sound source being opened and closed whether the audible response is set or not. When sound preferences are opened, it's as if a different routine is being used when the volume keys are pressed and it continues to be used until that piece of code gets purged from RAM memory when it hasn't been used for awhile.
I'm just curious if anyone has this issue as well.

Ah, the ever popular "feature" explanation.
I can accept that it is a result of attempting to implement a feature but the way it is working on my machine indicates that this "feature" is poorly implemented.
Well designed computer programming anticipates users actions as best as possible and makes things work as best for the current situation. Most Apple programming is a perfect example of how to do this correctly. When I hit a key to change the volume, it's reasonable to think that there's a good chance that I will hit the key again because once might not change the volume sufficiently enough. Instead, what I get is the sound channel turning on and off for every key press, no matter how quickly I press the key. This happens even if I do not have an audible response selected. Should sound be turned on when there isn't any sound to be played? I don't think this should be necessary for changing the volume if you do not have an audible response set.
Now this is how I feel this should actually work:
Sound, when running from battery should be handled like a disk drive or a screen. If it is not used for a set amount of time then it should be turned off and turned back on only if it is needed again. Hitting the volume keys when no sound is playing might set a shorter time limit before the sound is turned off but the "on" time should be sufficiently long enough to hit a volume key again without requiring the sound to be turned off and on on each press.
Remember how I mentioned that the sound problem would go away, maybe even for days if I opened the sound preferences? This would indicate to me that under this situation, the sound is not actually being turned off after a reasonable amount of time. Under certain situations, it doesn't stay on long enough and others, it stays on too long. If I am right about it happening during sound playback, then it's really messing up by turning off and then on when it clearly doesn't need to.
I am pretty sure that I have had the issue while plugged into power and at least once while iTunes was playing. Certainly when sound is already playing this shouldn't occur. For some reason, I can't seem to get the issue to surface again, but I think that it just might take some time after rebooting sometimes for it to happen again. I will post more on this when it happens again.

Strange Yosemite Glitches

Similar Messages

Maybe you are looking for