In a previous question I was instructed to download pythom, pycharm and the latest chrome driver. My version of chrome is 105.0.5192.102. But, when I look at the drivers page I can only find up to 105.0.5192.52.
Sorry for the question, I"m very new to all of this and have no idea what I am doing. THanks for any help!
Related
I've been using Atom for years on my Mac. I know it has been end-of-lifed by its dev team. I haven't installed anything new on it like plugins for many months. After the latest MacOS update, I get this popup when trying to open it:
Does anyone know if there is a way to tell if my copy has somehow become corrupted, or if this is a false positive?
Many thanks!
OK I found out that github revoked the Apple code signing certificate and is now enforcing that. I found the answer on the Atom blog. So, I was able to download an older version and it works well.
thanks for the info, i think it's the best time to find alternatives on text editors since Atom has been officially sunset (Sublime text?)
If you want the current installation to continue working:
$ xattr -cr /Applications/Atom.app
I'm not sure what the security risks of this are.
You might consider the Pulsar fork of the Atom project: https://pulsar-edit.dev/
I can't fully vouch for it because I'm just starting to use it, but it looks and feels the same to me.
Tried a few recommendations but nothing worked.
I think that it is a version issue.
Please advise if you can use auto complete.
Note this install on a windows 11.
autocompletion works on an install of a previous version on a different computer
BTW it would be nice to know where previous releases are stored.
Suddenly, today, the font that R uses in its gui window looks like this:
How can I get it to look nice again?
Note:
I do not want to specify fonts in plots.
I'm on a Mac under OS 10.9.5 using R 3.0.2.
Hmm, I don't know what the problem was, but updating R to the most recent version turned on antialiasing again:
As David Arenburg noted in a comment above, the problem might have been caused by remote access: I accessed this laptop from my desktop iMac yesterday to do a backup. Also I'm currently building fonts with FontForge, and the problem might be related to this (unfinished fonts lying around somewhere).
Anyway, the new installation did it (for the moment). If anyone knows how to analyse and solve this problem without installing, please post an answer.
For some time now I have been struggling with the differences between the Mac and Windows version of Safari. Sadly, my develop-setup requires me to work on Windows (although I do work on a MBP), so I can't change stuff and look how it affects the rendering of the page. Updating the online testing environment every time I make a change is silly.
The solution renders fine in Chrome (Windows+Mac), Firefox (Windows+Mac) and.. Even Internet Explorer.
So, my question is: is there a way to make Safari on Windows behave as if it were on OS X?
Thanks in advance :)
You could install a virtual machine running OSX:
http://www.macbreaker.com/2014/05/os-x-mavericks-in-virtualbox-with-niresh.html
I'm not sure how else you would be able to do it through windows.
I have this jailbroken iPhone 3G with iOS version 4.2.1 (the latest supported version). When I connect it to Xcode 4.2, Xcode starts copying the debug symbols. It stops copying towards the end of the process, and shows the following error:
Xcode has encountered an unexpected error (0xC002)
No such file or directory, at ‘/SourceCache/DTDeviceKit/DTDeviceKit-867/DTDeviceKit/DTDeviceKit_Utilities.m:864’
Anybody experiencing anything similar?
I know I should try and restore the phone, but I'm asking just in case anybody can come up with a solution that doesn't involve restoring it.
In this post on mactechnews.de, one guy reports the same problem -- with no solution, so far.
Alright, after a lot of testing and digging up the filesystem... I solved it.
It turns out that there are just a few files that are not downloaded from the device (for reasons still unknown). They are related to the dyld cache (don't really know what this is and what it's for). Here are the steps to make your 4.2.1 device debuggable in XCode 4.2 and 4.3.x:
Close Xcode
Go to: ~/Library/Developer/Xcode/iOS DeviceSupport/4.2.1 (8C148)/Symbols/System/Library/Caches/com.apple.dyld/ Note: if you don't have this folder, run Xcode, connect your device, and wait until the error 0xC002 appears in Organizer - the folder should be created by that time.
Create 3 empty files there called:
.copied_dyld_shared_cache_armv6
.processed_dyld_shared_cache_armv6
dyld_shared_cache_armv6
Run Xcode and enjoy the light next to your device eventually go green:)
Or, for the terminal lovers:
cd ~/Library/Developer/Xcode/iOS\ DeviceSupport/4.2.1\ \(8C148\)/Symbols/System/Library/Caches/com.apple.dyld/
touch .copied_dyld_shared_cache_armv6
touch .processed_dyld_shared_cache_armv6
touch dyld_shared_cache_armv6
This is obviously a hack but it works perfectly for debugging and I haven't noticed any side-effects so far.
Enjoy!
Small update:
I tested it on my snow leopard hackintosh, with the Xcode 4.2 (most recent to date) and although the device is active in the organizer and it is possible to run the app on the device, i get black screen on launch. It gets installed but apparently debugger cannot get attached. I had the same problem with 4.0.2, when the 0xC002 problem didn't yet occur so I think it's unrelated and might even not happen to others. Nevertheless, 0xC002 is still solved.
On my main development machine with Lion and Xcode 4.3.2, device is perfectly debuggable.
The answer above (https://stackoverflow.com/a/9944892/1390251) works, basically,
but for newer versions of Xcode you probably need to rename the files as follows,
having them end with '7' instead of '6':
touch .copied_dyld_shared_cache_armv7
touch .processed_dyld_shared_cache_armv7
touch dyld_shared_cache_armv7
If not sure, you can keep both sets of files (...6 and ...7)
in the relevant folder (can also be 5.1.1 for that matter)
and it should work.
(have tested it on iPhone 4 with iOS v5.1.1 genuine)
It seems that you cannot debug apps on iOS 4.2.1. I tried several restores to iOS 4.2.1 with same effect. Downgrading to iOS 4.0 was the only thing that worked.
The reason for whole problem is that iOS 4.2.1 is not supported in XCode, according to this website.
Error in Xcode getting debugging info from 5.0.1 iphone
solved, see the link to archive with iOS5.0.1 debug info
download & unpack to "~/Library/Developer/xCode/iOS DeviceSupport/" & be happy =)
I fixed this bug in![enter image description here][1] this way:
I duplicate the 5.1.1(9B206), rename it to 5.1.1(9A405)[my ios device is this version], then the error is gone.