PDFtk Server seems to be hanging indefinitely on MacOS Sierra. Looks similar to the problem it had on El Capitan.
I'm trying to run this command:
pdftk test1.pdf test2.pdf cat output out.pdf verbose
And am getting no output, just an indefinite hang. Same with every other command I've tried.
PDFtk --version:
pdftk 2.02 a Handy Tool for Manipulating PDF Documents
Copyright (c) 2003-13 Steward and Lee, LLC - Please Visit: www.pdftk.com
This is free software; see the source code for copying conditions. There is
NO warranty, not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Has anyone managed to find any workarounds for this?
Use this version:
https://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/pdftk_server-2.02-mac_osx-10.11-setup.pkg
Although it’s prepared for El Capitan (10.11), it also works on Big Sur (11), Catalina (10.15), Mojave (10.14), High Sierra (10.13), and Sierra (10.12).
Related
I have a problem with VS Code: whenever I code, debug, or run the code on my physical device using Flutter, it gets very slow, freezes, and shows "Windows is not responding: Reopen!" I disabled all the extensions, but nothing worked. I even tried some commands like deleting the user directory and disabling the extensions, but I still faced the same issue. I deleted the cache in AppData/Roaming/code, but still no luck. I also deleted the code file, and the same issue still exists! I even did this: -Open the Command Palette (Ctrl+Shift+P). Run the Preferences: Configure Runtime Arguments -Add "disable-hardware-acceleration": true. -Restart VS Code. I have looked it up all over the internet, and nothing worked! Please help me! these are the extntion:
Device Specifications:
Device name BadriyaHaddad
Processor Intel(R) Core(TM) i5-3230M CPU # 2.60GHz 2.60 GHz
Installed RAM 12.0 GB (11.9 GB usable)
Device ID 7B1CE693-8DEC-426E-B6FB-54CC3FADE82A
Product ID 00331-10000-00001-AA635
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
Windows Specifications:
Edition Windows 10 Pro
Version 22H2
Installed on 11/27/2022
OS build 19045.2364
Experience Windows Feature Experience Pack 120.2212.4190.0
enter image description here
In brief: How do I change the path to gdb to point to the right location?
Details
I know this topic is a quite common one, but I am desperate. I installed eclipse CDT on my MacOS High Sierra. Then after some time of searching I found out how to install the GDB debugger including code-signing. So I installed gdb 8.1 at /usr/local/bin (forgot which method I exactly used). It all seemed fine (gdb --version in console etc.) but then I found out that gdb 8.1 does not work under MacOS.
The way out of my dilemma seemed this post: https://stackoverflow.com/a/49104154/1552080
which created a parallel installation of gdb at /usr/local/Cellar/gdb/8.0.1/bin.
I did all the code signing stuff and entered the path to gdb 8.0.1. Furthermore I entered the new path in the eclipse debugger settings and modified my .bash_profile to point to the 8.0.1 location.
Nevertheless, eclipse seemed to point to the gdb 8.1 location /usr/local/bin. That's why I deleted the 8.1 gdb executable. Since then I always get an error message:
"Error with command: /usr/local/bin/gdb --version Cannot run program
"/usr/local/bin/gdb": Unknown reason"
Obviously, eclipse still looks in the wrong place for a debugger.
Maybe it is important to mention that when installing gdb 8.1 I did some trick in the save mode (see point 14 of https://gist.github.com/gravitylow/fb595186ce6068537a6e9da6d8b5b96d)
any help appreciated
2018-05-13, Update: the error above still persists after I copied the gdb 8.0.1 executable to the location /usr/local/bin
I am using OdroidXu4 armv7 board, ubuntu 16.04. Dont know why my all menu disappear, but the files on desktop can still be operated.
I followed https://itsfoss.com/how-to-fix-no-unity-no-launcher-no-dash-in-ubuntu-12-10-quick-tip/ to reinstall ubuntu-destop or unity, but it didn't work.
Then I used the command below
dconf reset -f /org/compiz
setsid unity
The menu flashed a while then disappeared again, returned error:
file /dev/mali0 is not of a compatible version (user 10.6, kernel 10.1)
ERROR: The DDK is not compatible with any of the Mali GPUs on the system.
The DDK was built for 0x620 r0p1 status range [0..15], but none of the GPUs
matched:
file /dev/mali0 is not of a compatible version (user 9.0, kernel 8.0)
I was confused with the "GPUs", because I didn't have any GPU.
How to fix the problem, thanks for your help
I was using Ubuntu 16.04.In my case unity, launcher and even terminal is not working.I followed the steps as described in https://www.itsmearunchandel.co.in/linux/ubuntu/how-to-reset-ubuntu-desktop.html .
1. Go to command line mode, press Ctrl+Alt+F1
2. Give username and password.
3. Run the commands as described in the link.
This way my issue was resolved.
I am trying to use the java_kernel for jupyter (https://github.com/Bachmann1234/java9_kernel and issue 24 therein). It works fine on a Mac OSX box. But on Linux (debian), the Java shell is not starting up.
I think I tracked it down to a call like this one:
ptyprocess.PtyProcess.spawn(["/home/jupyterhub/java/jdk-9/bin/java", "-jar", "/home/jupyterhub/java/kulla/kulla.jar"])
Reading pexpect code (https://github.com/pexpect/ptyprocess/blob/master/ptyprocess/ptyprocess.py), I would expect to end up in an exec call, having the child process running python replaced by java. However, this does not happen, ps -fu shows a python child process.
I'm guessing there is some subtle difference between pty handling on linux and osx that causes the differences here?
java-9/jshell as such work from the command line.
Any help much appreciated!
Best,
Holger
There seems to be a change in the way that later versions of jdk-9 deal with terminals on Linux. I reverted to jdk-9.ea+100 and that seems to work.
I am using nsight eclipse edition for mac to debug my cuda code. I was able to run cuda-gdb all fine from a terminal but was not able to use the debug function in Nsight. Whenever I started to debug, an error window pops up saying "Error in final launch sequence
Connection is shut down". My OS is Mac Lion (10.7.4).
I understand the big thing in Cuda 5.0 is the interactive debugging with eclipse but sadly I won't be able to use it unless I switch to Windows or Linux. If anybody has seen this or knows a workaround for this, please let me know and your help will be very much appreciated.
Thank you!
I'm afraid you've hit a known issue in CUDA 5.0 Toolkit. Due to some last-minute change, cuda-gdb (which is a shell script) is not entirely valid in Mac OS X. To remedy the problem:
Edit cuda-gdb shell script.
Make line #!/bin/sh the first line in this script.
Save the changes
We apologize for inconvenience. This (and many other) issues will be fixed in the upcoming CUDA 5.0 RC release.
I had this problem in linux recently.
Error in final launch sequence Connection is shut down which means nsight can not start debugger correctly.
first you have to make sure you can run cuda-gdb in terminal. just type cuda-gdb in terminal, if it says like cuda-gdb cannot find some lib in /usr/lib, just download or relink it. after you done this , rerun cuda-gdb in terminal, it should work fine. then you can use nsight debugging tool.