I've searched for a similar problem on google but didn't find exactly what I face. I've ever uploaded dSYMs in Firebase before and used the same command
/path/to/pods/directory/FirebaseCrashlytics/upload-symbols -gsp /path/to/GoogleService-Info.plist -p ios /path/to/dSYMs
, but when I try to do it again on other days, now it says that:
[1] 13901 illegal hardware instruction -gsp -p ios /Users/jeffry_sandy/Downloads/appDsyms.zip~
(number 13901 keep changing whenever I try to upload the file), I'm using Mac OS Monterey, and XCode Version 12.5 (12E262).
I use the same format before that works with me, I still didn't understand what this illegal hardware meant, I try to run as admin, and still doesn't work. Can anyone help me please..
Related
So i was trying to install the XP Pen Driver for my Deco 01 v2 graphics tablet on my Linux Mint 19.2 Tina when i came to encounter the following error:
./Pentablet_Driver: /usr/lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5.10' not found (required by ./Pentablet_Driver)
I went on to install qt 5.10, still the same error. Others suggested to just change the path wth sudo gedit /etc/ld.so.conf.d/randomLibs.conf which didn't change a thing.
Link to drivers:
https://www.xp-pen.com/download-440.html
The manufacturer has a page describing how to set up their software on Linux with pictures. However, when following them, you end up with a folder name somewhere along the line that has spaces in it, which causes issues.
So a modified set of instructions might look like this:
Connect your XP-Pen product to the computer.
Download the Linux Beta driver from XP-Pen official website.
When the download is complete, extract the compressed folder.
Rename the extracted folder to something without spaces.
Inside the renamed folder is another compressed folder which should be extracted.
Inside the final extracted folder, ensure "Pentablet_Driver.sh" has execution permissions by right clicking on it and going to "Properties->Permissions" and verifying that "Allow executing file as program" is checked.
Open the terminal. (CTRL+ALT+T)
Type "sudo ", then drag Pentablet_Driver.sh from the file browser onto the terminal.
Type the password to complete.
Make sure that you write exactly
sudo ./Pentablet_Driver.sh
instead
sudo ./Pentablet_Driver
I had the same error until I noticed that I forgot to add .sh at the end.
I am learning to program in Python and Rust. On different versions of Ubuntu these programs compiled and ran perfectly. Now that I have a dedicated Fedora 30 KDE system, every time I try and build a program, I get a warning: Failed to load module "appmenu-gtk-module"
I have tried looking this up and have re/installed anything GTK on my system. The programs otherwise function well, but no menus are drawn. I was also trying things in GNOME and hit the same thing.
I am also using QT. Those programs also build and run fine, but again, no menu.
I'm going bonkers with this. Any help is appreciated.
The appmenu-gtk module is not packaged on Fedora. (GNOME doesn't support them anyway.)
The real questions are:
Why is it configured to load? Did you copy or share GTK config files from an Ubuntu system? You should remove this module from your settings.
Even with improper configs I don't believe this should result in menus not appearing. It should just fail to load and work as normal. How is your application using menus?
I finally got so fed up with getting this error that I went full nerd-diagnosis, and ran this command to find out which file contained the errant reference to the appmenu-gtk (the package that would provide this is not installable on my system either).
(Replace "dolphin" with the command that is giving you the error.)
strace -e openat,access dolphin 2>&1 |grep -v ENOENT |awk '/appmenu-gtk/ {exit} !/appmenu-gtk/ {print}'|cut -d '"' -f2 |sort|uniq|xargs grep appmenu-gtk 2>/dev/null
This will then give you a list of files which contain the line appmenu-gtk, and in my case it was ~/.config/gtk-3.0/settings.ini. From there I just commented it out, and that gets rid of the error message (not sure if this will fix your problem of not having any menus, but you might just be able to edit that line to fix it in another way if commenting it out doesn't work).
I've been struggling with signing a Qt app. We updated our code to the newest 5.4 which I think is RC1? I follow the instructions on this page to make sure that the frameworks were structured properly. Each framework and plugin has been signed individually, and this got me further than I have gotten before:
https://www.qt.io/blog/2014/10/29/an-update-on-os-x-code-signing
But now after I sign the app, codesign says it's validated:
codesign --verify --deep --verbose=2 myapp.app
returns
// the following 2 lines are repeated for all libraries and plugins
-- prepared: path/to/object
-- validated: path/to/object
myapp.app/: valid on disk
myapp.app/: satisfies its Designated Requirement
This looks right, but I still get the 'unknown developer' alert, and when I run:
spctl -a -t exec -vv myapp.app
It says
myapp.app: rejected
From apple's page, the codesign verify and the spctl -a -t -vv are supposed to be identical, but I get different results.
I'm not sure what else to try, and none of these commands seem to give me any more detailed information on exactly what's going on.
Had the same problem, but only on a specific machine. spctl accepted the same .app on other machines.
The problem machine was a recent installation.
Solved by setting System Preferences > Security & Privacy > Allow apps downloaded from: > Anywhere.
Recently I wanted to try the gvim7.2 for its wonderful support of CSCOPE and installed it from my company's installation directory. However, when I execute it - I get a segmentation fault and the message looks thus,
Vim: Caught deadly signal SEGV
Vim: Finished.
Segmentation fault (core dumped)
When I was searching for this issue in the online forums, I found general complaints about the reproducibility of the issue. Any insights on this would be greatly appreciated.
I have had crashes with incompatible shared libraries for Python3 IIRC.
I never got ultisnips working on Ubuntu Natty 64 for that very reason.
Removing the plugin made vim start normally (probably by not loading the incompatible library in the first place).
You may disable your plugins and reenable them one by one to see whether Python is the culprit, or test directly:
gvim -u NONE +'python3 print "test"'
On my box:
Fatal Python error: take_gil: NULL tstate
Vim: Caught deadly signal ABRT
Vim: Finished.
Conversely,
gvim -u NONE +'python2 print "test"'
Works correctly
This surely took me a long time to debug, I indeed went through the painful process of manually disabling every plugin that I had installed and yet the same error kept popping up.
[Solution] : It turned out that the gvim is tightly bound to the graphics settings used. We use a citrix client to remote login into UNIX servers and develop from there. As per my colleague's suggestion - I changed the color settings to "True Color 24 bit" and voila!!, things worked perfectly.
One of the classic examples of the times when we get hit by totally unsuspecting source of bugs!
Anyways, thanks for all your suggestions - I learned a lot :).
Try verbose logging,
vim -V10/tmp/vim.log
You can also try running strace to see where it is bombing,
strace vim
It's possible that it's a permissions issue, but that's a guess.
try starting Vim like so:
$ vim -u NONE
which will disable all plugins to see if the problem still persists.
If it starts OK, move all the plugins from Vim's runtime directory (usually):
~/.vim/
on Linux & add them back one by one until the seg fault occurs.
Can be a tedious process especially as there may be a conflict between two or more plugins & in that case, it hard to ascertain when exactly they clash, but nine times out of ten, it usually gets you to the root of the problem.
I am trying to start working with OpenCL. I have two NVidia graphics card, I installed "developer driver" as well as SDK from NVidia website. I compiled the demos but when I run
./oclDeviceQuery
I see:
OpenCL SW Info:
Error -1001 in clGetPlatformIDs Call
!!!
How can I fix it? Does it mean my nvidia cards cannot be detected? I am running Ubuntu 10.10 and X server works properly with nvidia driver.
I am pretty sure the problem is not related to file permissions as it doesn't work with sudo either.
In my case I have solved it by installing nvidia-modprobe package available in ubuntu (utopic/multiverse). And the driver itself (v346) was installed from https://launchpad.net/~mamarley/+archive/ubuntu/nvidia
Concretely, I have installed nvidia-opencl-icd-346, nvidia-libopencl1-346, nvidia-346-uvm, nvidia-346 and libcuda1-346. Not sure if they are all needed for OpenCL.
This is a result of not installing the ICD portion of Nvidia's openCL runtime. The ICD profile will instruct your application of the different openCL implementations installed on the system as multiple implementations from different vendors can coexist. Whe your application does not find the ICD information it gives the Error -1001.
Run your program as root. In case of success: you have trouble with cl_khr_icd- extension to load the vendor driver.
If you not running X11, you have to create device files manually or by (boot-)script:
ERROR: clGetPlatformIDs -1001 when running OpenCL code (Linux)
Same problem for me on a Linux system. Solution is to add the user to the video group:
# sudo usermod -aG video your-user-name
Since I just spend a couple of hours on this, I thought I would share:
I got the error because I was connected to the machine per remote desktop (mstsc). On the machine itself everything worked fine.
I have been told that it should work with TeamViewer by the way.
Dont know if you ever solved this problem, but I had the same issue and solved it in this post: ERROR: clGetPlatformIDs -1001 when running OpenCL code (Linux)
Hope it helps!
I have solved it in Ubuntu 13.10 saucy for intel opencl by created link:
sudo ln -s /opt/intel/opencl-1.2-3.2.1.16712/etc/intel64.icd /etc/OpenCL/vendors/nvidia.icd
I just ran into this problem on ubuntu 14.04 and I could not find ANY working answers anywhere online including this thread (though this was the first to show up on google). What ended up working for me was to remove ALL previous nvidia software and then to reinstall it using the .run file provided on the nvidia website. Installing the components through apt-get seems to fail for some reason.
1) Download CUDA .run file: https://developer.nvidia.com/cuda-downloads
2) Purge all previous nvidia packages
sudo apt-get purge nvidia-*
3) Install all run file components (you will likely have to stop X or restart in recovery mode to run this)
sudo sh cuda_X.X.XX_linux.run
This is because OpenCL has the same brain damaged one library per vendor setup that OpenGL has. A likely reason for the -1001 error is that you have compiled with a different library than the linker is trying to dynamically load.
So see if this is the problem run:
$ ldd oclDeviceQuery
...
libOpenCL.so.1 => important path here (0x00007fe2c17fb000)
...
Does the path point towards the NVidia-provided libOpenCL.so.1 file? If it doesn't, you should recompile the program with an -L parameter pointing towards the directory containing NVidia's libOpenCL.so.1. If you can't do that, you can override the linker's path like this:
$ LD_LIBRARY_PATH=/path/to/nvidias/lib ./oclDeviceQuery
For me, I was missing the CUDA OpenCL library, Running sudo apt install cuda-opencl-dev-12-0 solved it.
You should get number of platforms, allocate the memory for platforms, again get this platforms and then create context from this platform. There is good example:
http://developer.amd.com/support/KnowledgeBase/Lists/KnowledgeBase/DispForm.aspx?ID=71
This might be due to querying clGetPlatformIDs by multiple threads at the same time