PINCE not starting Surface Pro 8 Ubuntu 22.04 about pince

[LovisR]

i installed it like half an hour before i opened the issua

[PauloAxcel]

I had the same error as you. What appears to be the issue is that you have multiple python versions installed at the same time. In my case, I add anaconda3 and then another python version in the usr/bin. What I did was to delete the anaconda3 directory, delete PINCE and install again PINCE. After that, everything ran fine!

I just followed these instructions on how to uninstall anaconda

https://stackoverflow.com/questions/22585235/python-anaconda-how-to-safely-uninstall

and this one to find how many python versions do I have installed

https://askubuntu.com/questions/1257144/python-package-gi-is-not-found-although-python3-gi-is-installed

Might not be the same issues though, but for me, it worked, and I had exactly the same error message as you!
Hope it helps!

[LovisR]

also i do have python3-gi installed

[brkzlr]

Post output of install_pince.sh

[LovisR]

sh install_pince.sh
[sudo] password for lovis: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
libcairo2-dev is already the newest version (1.16.0-5ubuntu2).
libgirepository1.0-dev is already the newest version (1.72.0-1).
libtool is already the newest version (2.4.6-15build2).
libxcb-randr0-dev is already the newest version (1.14-3ubuntu3).
libxcb-shape0-dev is already the newest version (1.14-3ubuntu3).
libxcb-xinerama0-dev is already the newest version (1.14-3ubuntu3).
libxcb-xkb-dev is already the newest version (1.14-3ubuntu3).
libxcb-xtest0-dev is already the newest version (1.14-3ubuntu3).
pkg-config is already the newest version (0.29.2-1ubuntu3).
libxcb-cursor0 is already the newest version (0.1.1-4ubuntu1).
qt6-l10n-tools is already the newest version (6.2.4-1).
gdb is already the newest version (12.1-0ubuntu1~22.04).
python3-dev is already the newest version (3.10.6-1~22.04).
python3-pip is already the newest version (22.0.2+dfsg-1ubuntu0.3).
python3-venv is already the newest version (3.10.6-1~22.04).
The following packages were automatically installed and are no longer required:
  libexo-2-0 libexo-common libflashrom1 libftdi1-2 libllvm13 libllvm13:i386
  libxfce4panel-2.0-4 libxfce4ui-2-0 libxfce4ui-common libxfce4util-bin
  libxfce4util-common libxfce4util7 libxfconf-0-3 xfconf
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
Requirement already satisfied: pyqt6 in ./.venv/PINCE/lib/python3.9/site-packages (6.5.2)
Requirement already satisfied: pexpect in ./.venv/PINCE/lib/python3.9/site-packages (4.8.0)
Requirement already satisfied: distorm3 in ./.venv/PINCE/lib/python3.9/site-packages (3.5.2)
Requirement already satisfied: keystone-engine in ./.venv/PINCE/lib/python3.9/site-packages (0.9.2)
Requirement already satisfied: pygdbmi in ./.venv/PINCE/lib/python3.9/site-packages (0.11.0.0)
Requirement already satisfied: keyboard in ./.venv/PINCE/lib/python3.9/site-packages (0.13.5)
Requirement already satisfied: pygobject in ./.venv/PINCE/lib/python3.9/site-packages (3.44.1)
Requirement already satisfied: PyQt6-sip<14,>=13.4 in ./.venv/PINCE/lib/python3.9/site-packages (from pyqt6) (13.5.2)
Requirement already satisfied: PyQt6-Qt6>=6.5.0 in ./.venv/PINCE/lib/python3.9/site-packages (from pyqt6) (6.5.2)
Requirement already satisfied: ptyprocess>=0.5 in ./.venv/PINCE/lib/python3.9/site-packages (from pexpect) (0.7.0)
Requirement already satisfied: pycairo>=1.16.0 in ./.venv/PINCE/lib/python3.9/site-packages (from pygobject) (1.24.0)
WARNING: You are using pip version 22.0.4; however, version 23.2.1 is available.
You should consider upgrading via the '/home/lovis/PINCE/.venv/PINCE/bin/python3 -m pip install --upgrade pip' command.
Downloading libscanmem
Entering libscanmem directory
Recompile libscanmem? [y/n]
y
+ running libtoolize ...
+ running aclocal ...
+ running autoheader ... 
+ running autoconf ... 
+ running automake ... 
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports the include directive... yes (GNU style)
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for wchar.h... yes
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking whether _XOPEN_SOURCE should be defined... no
checking for _Bool... yes
checking for stdbool.h that conforms to C99... yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... mt
checking if mt is a manifest tool... no
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for getline... yes
checking for secure_getenv... yes
checking for fcntl.h... yes
checking for limits.h... yes
checking for stddef.h... yes
checking for sys/ioctl.h... yes
checking for sys/time.h... yes
checking for size_t... yes
checking for working alloca.h... yes
checking for alloca... yes
checking for working strtod... yes
checking for int8_t... yes
checking for int16_t... yes
checking for int32_t... yes
checking for int64_t... yes
checking for uint8_t... yes
checking for uint16_t... yes
checking for uint32_t... yes
checking for uint64_t... yes
checking for off_t... yes
checking for pid_t... yes
checking for size_t... (cached) yes
checking for ssize_t... yes
checking whether byte ordering is bigendian... no
configure: Linux detected
checking for /proc/self/maps... yes
checking for /proc/self/mem... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for GNU libc compatible malloc... yes
checking for GNU libc compatible realloc... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
(CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash '/home/lovis/PINCE/libscanmem-PINCE/missing' autoheader)
rm -f stamp-h1
touch config.h.in
cd . && /bin/bash ./config.status config.h
config.status: creating config.h
config.status: config.h is unchanged
make  all-am
make[1]: Entering directory '/home/lovis/PINCE/libscanmem-PINCE'
make[1]: Leaving directory '/home/lovis/PINCE/libscanmem-PINCE'
Exiting libscanmem directory
Updating 'i18n/ts/it_IT.qm'...
    Generated 27 translation(s) (14 finished and 13 unfinished)
    Ignored 434 untranslated source text(s)
Updating 'i18n/ts/zh_CN.qm'...
    Generated 461 translation(s) (461 finished and 0 unfinished)

PINCE has been installed successfully!
Now, just run 'sh PINCE.sh' from terminal

[brkzlr]

@korcankaraokcu I don't remember exactly why we didn't add it but I think maybe we should add PyGObject to pip's package list as we're explicitly importing gi?

EDIT: Nevermind ^ I missed the PyGObject entry in the file.

Or maybe do a double check and see if the issues we were having with GTK are gone so we can remove this line and get rid of the gi dependency.

[brkzlr]

@LovisR Could you try running a version check on /home/lovis/PINCE/.venv/PINCE/bin/python3?

From your logs I'm seeing that Python 3 should be 3.10 but pip's packages are on 3.9 so it might be a version mismatch.

[LovisR]

/home/lovis/PINCE/.venv/PINCE/bin/python3 --version
Python 3.9.12

[brkzlr]

Did you have PINCE installed for some time? If yes, does this still happen if you purge the folder and re-download/re-install PINCE?
Otherwise I'm not sure why there would be different python versions between your distro package manager and pip's.

@korcankaraokcu You might be able to give it a better look as you have a VM of Ubuntu.

[korcankaraokcu]

We use that import as a fix for some systems, try to get rid of that import and run PINCE again. Lines 21 and 26

[LovisR]

just to be sure, do you mean to remove lines 21 and 26 of PINCE.sh?

[korcankaraokcu]

just to be sure, do you mean to remove lines 21 and 26 of PINCE.sh?

yeah

[LovisR]

i tried removing those lines from Pince.sh, but that didnt work, and returned following error

sh PINCE.sh
Traceback (most recent call last):
  File "/home/lovis/PINCE/PINCE.py", line 22, in <module>
    import gi
ModuleNotFoundError: No module named 'gi'

then i thought you might have ment the PINCE.py file, where i removed the lines that imported/required GI, and got the following error back

sh PINCE.sh
Traceback (most recent call last):
  File "/home/lovis/PINCE/PINCE.py", line 28, in <module>
    from PyQt6.QtGui import QIcon, QMovie, QPixmap, QCursor, QKeySequence, QColor, QTextCharFormat, QBrush, QTextCursor, \
ModuleNotFoundError: No module named 'PyQt6'

[korcankaraokcu]

then i thought you might have ment the PINCE.py file

Yeah, mb. I meant the py file. I've read that too fast

ModuleNotFoundError: No module named 'PyQt6'

That's impossible. You've literally installed it:
Requirement already satisfied: pyqt6 in ./.venv/PINCE/lib/python3.9/site-packages (6.5.2)

Maybe @brkzlr is right on the issue

From your logs I'm seeing that Python 3 should be 3.10 but pip's packages are on 3.9 so it might be a version mismatch.

Try to use the same version with pip while launching PINCE

[brkzlr]

If those are installed and it won't work then my guess is that venv fails to activate @korcankaraokcu

Basically line 28 or 33 of PINCE.sh.

Either user's shell doesn't support the way we activate it or the preserve-env flag used to fix Ubuntu/Debian failed.

[vitalNohj]

when i try starting Pince with sh PINCE.sh the console returns

Traceback (most recent call last):
  File "/home/lovis/PINCE/PINCE.py", line 21, in <module>
    import gi
ModuleNotFoundError: No module named 'gi'

I have the same issue with a Surface Book on Ubuntu 22.04.
Are you running the surface kernel patch too?