Skip to content

Ipscan not working in Bullseye #1045

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
feadog1 opened this issue Oct 12, 2021 · 18 comments
Closed

Ipscan not working in Bullseye #1045

feadog1 opened this issue Oct 12, 2021 · 18 comments
Labels
Upstream Bug something isn't working that can only be fixed upstream

Comments

@feadog1
Copy link

feadog1 commented Oct 12, 2021

Angry ip scanner not running under bullseye rpi-os rpi4.
Error message " failed to load native code. Cannot load 64bit swt libraries on 32 bit JVM"

While I know bullseye is not fully supported, it would be nice to see this working as in Buster.
Thanks

@Botspot
Copy link
Owner

Botspot commented Oct 12, 2021

Is your bullseye OS 32-bit or 64-bit?

@feadog1
Copy link
Author

feadog1 commented Oct 12, 2021

Its 32 bit armv7l. Rpios Buster upgraded to bullseye.

@norambna
Copy link

norambna commented Jan 2, 2022

Hi! I got the same problem on a freshly installed Raspberry Pi OS Bullseye 32-bit.

@Itai-Nelken
Copy link
Contributor

@cycool29
Copy link
Contributor

cycool29 commented Jan 4, 2022

Reported to Angry IP Scanner repo: angryip/ipscan#322

You may consider commenting there to say it's affecting you.

@PabloI75
Copy link

Hello, same here, I have a fresh install and an update from Buster both same result as the first comment here. Any updates / solution? thanks!!

@cycool29
Copy link
Contributor

cycool29 commented Jan 17, 2022

I got it working, see angryip/ipscan#322 (comment).

For anyone who urges to use Angry IP Scanner on Bullseye ARM32, enter this command for a temporary fix:

cd "$(mktemp -d)"
wget http://ftp.us.debian.org/debian/pool/main/s/swt4-gtk/libswt-gtk-4-java_4.10.0-3_$(dpkg --print-architecture).deb http://ftp.us.debian.org/debian/pool/main/s/swt4-gtk/libswt-gtk-4-jni_4.10.0-3_$(dpkg --print-architecture).deb http://ftp.us.debian.org/debian/pool/main/s/swt4-gtk/libswt-cairo-gtk-4-jni_4.10.0-3_$(dpkg --print-architecture).deb
sudo apt install ./*.deb
sudo apt-mark hold libswt-cairo-gtk-4-jni libswt-gtk-4-java libswt-gtk-4-jni
cd -

@theofficialgman Do you know where we can report the broken SWT packages to Raspbian?

@theofficialgman
Copy link
Collaborator

the launchpad is the official place to report it https://bugs.launchpad.net/raspbian

you can see what process they want you to use here: https://www.raspbian.org/RaspbianBugs

I guess if the debian buster ones work then its actually a bug with raspbian packages for it. the version for those packages is the same in the raspbian repo as the debian buster repo http://archive.raspbian.org/raspbian/pool/main/s/swt4-gtk/ , so its not that they are out of date or anything

@theofficialgman
Copy link
Collaborator

edit: oh I see you are referring to an issue only occurring on bullseye, the debian bullseye packages for swt are at version 4.17 while the raspbian bullseye packages are still at 4.13, so they are out of date, it might just be a matter of updating those in the repo and then everything might work

@feadog1
Copy link
Author

feadog1 commented Jan 17, 2022

Great work and thanks for the temporary fix.

@cycool29
Copy link
Contributor

edit: oh I see you are referring to an issue only occurring on bullseye, the debian bullseye packages for swt are at version 4.17 while the raspbian bullseye packages are still at 4.13, so they are out of date, it might just be a matter of updating those in the repo and then everything might work

Maybe SWT on 4.17 is not supported on armhf, since there doesn't even have armhf packages on https://packages.debian.org.

@PabloI75
Copy link

Thanks for the temp fix cycool29!! it worked for me when I apply the fix on a system where Angry ip scanner was previously installed, but now I have applied the fix before installing it and it doesn't let me install it, stating:
Failed to install file: A package could not be found that allows the action to complete...

@theofficialgman
Copy link
Collaborator

Maybe SWT on 4.17 is not supported on armhf, since there doesn't even have armhf packages on https://packages.debian.org.

I checked the ubuntu launchpad to see if armhf was still in their buildscript and it is, but its failing on anything newer than 4.18 (no ubuntu release uses 4.17). you can see the buildlog from the 4.18 and the errors it is encountering on armhf here: https://launchpadlibrarian.net/557787289/buildlog_ubuntu-hirsute-armhf.swt4-gtk_4.18.0-2_BUILDING.txt.gz

in both cases, on ubuntu and debian, the Debian Java Maintainers are the ones responsible for this package
https://launchpad.net/~pkg-java-maintainers
their email for contacting is here: pkg-java-maintainers@lists.alioth.debian.org

@theofficialgman
Copy link
Collaborator

theofficialgman commented Jan 17, 2022

did more searching and it looks like they are already aware:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962915
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960769

the issue is because upstream stopped supporting 32bit alltogether in 4.10 for ALL eclipse projects. it managed to continue building just fine until the 4.15 release when code was changed and 32bit building actually broke

@theofficialgman
Copy link
Collaborator

theofficialgman commented Jan 17, 2022

raspbian bullseye is basically supplying 4.13 on armhf even when its unsupported upstream. they should either revert to 4.10.0-3 on bullseye, or make sure to apply this patch to their 4.13 build: https://sources.debian.org/patches/swt4-gtk/4.10.0-3/0004-Use-is64-defined-for-build.patch/

and yes I checked, raspbian bullseye IS missing that patch on their build for 4.13.0-1, it might not be possible, but it definitely won't work without it at all (as you have seen)

@theofficialgman theofficialgman added the Upstream Bug something isn't working that can only be fixed upstream label Feb 3, 2022
Repository owner deleted a comment from Anouomgharbivsseagjdzzvz May 6, 2022
@theofficialgman
Copy link
Collaborator

checking in on old issues. unfortunatly raspbian maintainers have been entirely unresponsive (as is normal with them). a bug report was created 8 months ago with no responses https://bugs.launchpad.net/raspbian/+bug/1962099

for anyone that forgot, this is because this #1045 (comment)

@theofficialgman
Copy link
Collaborator

32bit support removed in pi-apps since this is going nowhere and will not get better
65dc9e2

@theofficialgman theofficialgman closed this as not planned Won't fix, can't repro, duplicate, stale May 19, 2023
@Abdullaalali
Copy link

I got it working, see angryip/ipscan#322 (comment).

For anyone who urges to use Angry IP Scanner on Bullseye ARM32, enter this command for a temporary fix:

cd "$(mktemp -d)"

wget http://ftp.us.debian.org/debian/pool/main/s/swt4-gtk/libswt-gtk-4-java_4.10.0-3_$(dpkg --print-architecture).deb http://ftp.us.debian.org/debian/pool/main/s/swt4-gtk/libswt-gtk-4-jni_4.10.0-3_$(dpkg --print-architecture).deb http://ftp.us.debian.org/debian/pool/main/s/swt4-gtk/libswt-cairo-gtk-4-jni_4.10.0-3_$(dpkg --print-architecture).deb

sudo apt install ./*.deb

sudo apt-mark hold libswt-cairo-gtk-4-jni libswt-gtk-4-java libswt-gtk-4-jni

cd -

@theofficialgman Do you know where we can report the broken SWT packages to Raspbian?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Upstream Bug something isn't working that can only be fixed upstream
Projects
None yet
Development

No branches or pull requests

8 participants