|
Post by snugbug on Apr 8, 2021 1:13:19 GMT
On my search for what's working on Bodhi 6 or not, I installed Open Visual TraceRoute, but it doesn't run. I know, it doesn't support Java 11, so I have both Java 11 and 8 installed. I did the same as I usually do in any other distro (successfully!) and that's running this command
sudo update-alternatives --config java So, I switched to Java 8, before I started the app, but the app didn't run.
Then, I opened the terminal and moved to
/usr/share/OpenVisualTraceRoute and started the app with the following command
./ovtr_run_as_root.sh But this is what I got as a terminal output:
/usr/share/OpenVisualTraceRoute$ ./ovtr_run_as_root.sh localuser:root being added to access control list ./ovtr_run_as_root.sh: 7: [: libpcap.so.0.8: unexpected operator starting OpenVisualTraceroute... 01:01:18.487 [main] INFO org.leo.traceroute.Main - Open Visual Traceroute 1.7.1 01:01:18.570 [main] INFO org.leo.traceroute.install.Env - Java run-time version: 1.8.0_282 01:01:18.572 [main] INFO org.leo.traceroute.install.Env - NASA World Wind Java v2.1.0 01:01:18.572 [main] INFO org.leo.traceroute.install.Env - 01:01:18.587 [main] INFO org.leo.traceroute.install.Env - OS:Linux / arch:amd64 01:01:18.591 [main] INFO org.leo.traceroute.install.Env - Loading /usr/share/OpenVisualTraceRoute/native/linux/x64/libjpcap.so 01:01:18.596 [main] ERROR org.leo.traceroute.Main - Uncaught error java.lang.UnsatisfiedLinkError: /usr/share/OpenVisualTraceRoute/native/linux/x64/libjpcap.so: libpcap.so.0.8: Cannot open shared-object-file: File or directory not found at java.lang.ClassLoader$NativeLibrary.load(Native Method) ~[na:1.8.0_282] at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1934) ~[na:1.8.0_282] at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1817) ~[na:1.8.0_282] at java.lang.Runtime.load0(Runtime.java:810) ~[na:1.8.0_282] at java.lang.Runtime.load(Runtime.java:798) ~[na:1.8.0_282] at org.leo.traceroute.install.Env.initEnv(Env.java:327) ~[org.leo.traceroute.jar:na] at org.leo.traceroute.Main.main(Main.java:67) ~[org.leo.traceroute.jar:na] localuser:root being removed from access control list
Is this due to the beta of Bodhi 6 or have I done anything wrong?
|
|
enigma9o7
Crew Member
Posts: 1,427
Likes: 1,336
|
Post by enigma9o7 on Apr 8, 2021 5:55:27 GMT
I'm not famniliar with this software at all without trying, but by the name of the file, I think you're supposed to run it as root.
sudo ./ovtr_run_as_root.sh
|
|
|
Post by ylee on Apr 8, 2021 9:37:39 GMT
I have not taken the time to test this but looking at the output, does the below file exist:
/usr/share/OpenVisualTraceRoute/native/linux/x64/libjpcap.so If it exists perhaps you need to install libpcap0.8.
|
|
|
Post by Hippytaff on Apr 8, 2021 14:31:16 GMT
Tried replicating this and had the same issues initially, but got it working like this. I downloaded the deb file from sourceforge.net/projects/openvisualtrace/Installed with I pulled in all the depends with changed to java8 as described in the opening post, then installed libpcap0.8 as suggested by ylee and this seems to work. It opens at least. I'm not familiar with the application.
|
|
|
Post by snugbug on Apr 8, 2021 15:06:27 GMT
@ enigma9o7 Because of the sudo privileges required for this app, that script creates a password query for my sudo password and then starts the app, On other distros, all I have to do is to make sure that /usr/share/OpenVisualTraceRoute/ovtr_run_as_root.sh is the command of the launcher. @ ylee I installed that package and then the app was working, but without the 3D globe. I thought, to get that globe working and since the missing package is installed now, let's reinstall the app, I uninstalled the app using Gdebi, but suddenly Gdebi doesn't work anymore. I double-click the DEB and Gdebi appears. I hit install of that DEB, then Gdebi just disappears from the screen and there's no installation. I don't know were I broke Gdebi or why it is broken. If I knew what step was causing Gdebi to break, I might be able to avoid that step, but since I don't know, I keep on running into this again and again in some kind of an endless loop. All I can say is, until yesterday, it used to work perfectly. The policykit is installed and enabled in the startup apps, but I cannot install eSudo, because that's not available for Bodhi 6. How can I make Gdebi work again?
@ Hippytaff That's what it looked like here, too, but I tried to get the 3D globe, because the globe in that app is supposed to look almost like the one in Google Earth, but now there's no app and no working Gdebi anmore.
EDIT: Usually, there's a 3D/2D button in the app, which is currently missing. In the upper right corner of the app, there's a log available, which is notifying me, that there's no graphics card with 3D support found. Since I have another distro called MX Linux on that computer, where the app is working fine, this cannot be true. Instead, there's an OpenGL driver missing. I don't know, what packages are required to fix this, but I guess, these packages are not implemented into Bodhi 6, yet.
|
|
|
Post by snugbug on Apr 9, 2021 1:15:15 GMT
DEB's are working again. When I start a DEB, I'm asked for the sudo password, and the installation is executed. I went to the .desktop file of gdebi and changed the Exec line from
Exec=gdebi-gtk %f ..........to............ Exec=gksudo gdebi-gtk %f
I don't have the slightest clue as for when or why this is happening. All I can say it seems to be absolutely randomly and I would really like to find out why it is happenin from time to time.
|
|
enigma9o7
Crew Member
Posts: 1,427
Likes: 1,336
|
Post by enigma9o7 on Apr 9, 2021 1:35:08 GMT
I know hippytaff suggested alternate method of install, but I always install with apt so it handles dependencies for me and dont have to use dpkg to fix broken stuff etc, then it gets the recommends as well as dependencies so everything works right. This is general case still have'nt tried this app. But if i download a deb, I cd ~/Downloads sudo apt install ./filename.deb
which always works right. gdebi works right when it works, but sometimes it says it cannot install things that apt works for. using dpkg directly allows you to break things so i personally avoid it.
|
|
|
Post by snugbug on Apr 9, 2021 4:04:06 GMT
I know there are different methods to install DEB's, I just wanted to have the one with Gdebi back.
As for Open Visual TraceRoute, do you know what packages I need to install OpenGL properly? The log file claims the graphics card doesn't support the required OpenGL features, which cannot be true, because in other distros like MX, on the same computer, the app is working perfectly. I assume there are some packages missing to have OpenGL fully supported. Do you have an idea what packages I might have to add?
|
|
enigma9o7
Crew Member
Posts: 1,427
Likes: 1,336
|
Post by enigma9o7 on Apr 9, 2021 4:07:13 GMT
I know there are different methods to install DEB's, I just wanted to have the one with Gdebi back. As for Open Visual TraceRoute, do you know what packages I need to install OpenGL properly? The log file claims the graphics card doesn't support the required OpenGL features, which cannot be true, because in other distros like MX, on the same computer, the app is working perfectly. I assume there are some packages missing to have OpenGL fully supported. Do you have an idea what packages I might have to add?
No. But I know where I'd start sudo apt install mesa-utils glxinfo | grep OpenGL inxi -G to get some details you could share here.
What it actually means more likely is your graphics *driver* doesnt support it. Either that, or the new version of software requires a newer version of opengl than the previous. That definitely happens sometimes. Blender did that, wont start without ogl 3.3. obs did that, wont start without gl 2.1. minitube did that, now requires gl2.1 also or just plays sound but no video. Retroarch wont even start on gl1.3 anymore, but forutunately there's a command line option to let it keep working. etc etc.
|
|
|
Post by Hippytaff on Apr 9, 2021 7:22:09 GMT
I know hippytaff suggested alternate method of install, but I always install with apt so it handles dependencies for me and dont have to use dpkg to fix broken stuff etc, then it gets the recommends as well as dependencies so everything works right. This is general case still have'nt tried this app. But if i download a deb, I cd ~/Downloads sudo apt install ./filename.deb Using apt is probably a better idea than dpkg, then you can skip the —fix-broken install bit. I didn’t think about it much, just went ahead and did it to see if I could get it to work which it did I guess. Seems the graphics card issue is preventing the full functionality desired, which I see is under investigation 🙂
|
|
|
Post by snugbug on Apr 9, 2021 19:08:32 GMT
sudo apt install mesa-utils glxinfo | grep OpenGL inxi -G to get some details you could share here.
What it actually means more likely is your graphics *driver* doesnt support it. Either that, or the new version of software requires a newer version of opengl than the previous. That definitely happens sometimes. Blender did that, wont start without ogl 3.3. obs did that, wont start without gl 2.1. minitube did that, now requires gl2.1 also or just plays sound but no video. Retroarch wont even start on gl1.3 anymore, but forutunately there's a command line option to let it keep working. etc etc.
I used to have Bodhi 5.1 on that computer and I still have MX 19.4 there. In all of these installations, Open Visual Traceroute, which is version 1.7.1 everywhere, is running fine, so the hardware should be ok. Only in Bodhi 6 there's this openGL problem.
mesa-utils 8.4.0-1build1 is installed already and this is the output of the glxinfo command:
glxinfo | grep OpenGL OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) HD Graphics 5500 (BDW GT2) OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.2.6 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.2.6 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.2.6 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions:
And the inxi command: inxi -G Graphics: Device-1: Intel HD Graphics 5500 driver: i915 v: kernel Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] driver: radeon v: kernel Display: x11 server: X.Org 1.20.9 driver: intel resolution: 1366x768~60Hz OpenGL: renderer: Mesa Intel HD Graphics 5500 (BDW GT2) v: 4.6 Mesa 20.2.6
I don't know what's the point in having two graphics, but the computer came with this cconfiguration. I used to have a tearing in videos the other day, and I created the file
/usr/share/X11/xorg.conf.d/20-intel.conf
containing the following configuration:
Section "Module" Load "dri3" EndSection
Section "Device" Identifier "Intel Graphics" Driver "intel" Option "DRI" "3" EndSection
The tearing is gone, so the Intel graphics is the one in use, I think.
Since my last post, I installed several more apps, they all seem to be ok, so I very much like Bodhi 6 already, just as it is until now. Open Visual TraceRoute is so far the only one that doesn't work properly.
|
|
enigma9o7
Crew Member
Posts: 1,427
Likes: 1,336
|
Post by enigma9o7 on Apr 9, 2021 21:07:18 GMT
I have an idea, but only an idea. In an unrelated thread, someone mentioned the Linux 5.x kernel has known issues with many intel gpu's that use the i915 kernel driver. With bodhi 5, were you using the standard bodhi 5 provided kernel (i think its 4.15) or had you upgraded (or installed originally) the hwe kernel? The hwe kernel is now at 5.4, the exact same kernel being used for bodhi 6. Any chance this could be a possibility (based on which kernel you were using for bl5 and mx)... If this turns out to be the actual issue, you could use Bodhi 6 with an earlier kernel. As an unrelated experiment I installed 4.19LTS kernel on Bodhi 6 in a virtual machine a couple weeks ago and it seems to be fine, but I am no expert on this kinda thing, I did it purely as an experiment, there may be problems later I dunno about that someone more knowledgeable than me can probably understands, but seems to work perfectly, and can still chose to boot the new kernel from grub if desired.
If you decide to pursue that route, I recommend a program called "mainline" to install it. It also has the ability to notify you of updates (as it gets kernels direct from kernel.ubuntu.com not apt downloading from repository, it wont see updates as part of apt update).
sudo add-apt-repository ppa:cappelikan/ppa sudo apt install mainline Note you have to change a setting to show 4.x kernels, by default it only shows 5.x. I hadn't started that vm recently as I've been testing from newer ISO, but just opened it now to take a screenshot of the app, and it notified me a kernel update is available, so it's working Check the top right of the screen, that came up automatically.
|
|
|
Post by snugbug on Apr 10, 2021 3:45:08 GMT
I don't remember what particular kernel I was using in Bodhi 5.1, but I definitely started with the default one for 5.1, but then I always tried to have the same as the latest one for Mint. So when I stopped using Bodhi 5.1 it must have been some kernel of the 5.4.x series I guess. I tried two kernels, of the 4.18 and 4.19, the latest ones, but I didn't notice any differences to the 5.4.0. Since I found another app last night, which doesn't work in Bodhi 6 properly, either, I'm sorry to say, I have to give up on Bodhi 6 and I'm going to return to 5.1 instead. Oh, and this other app is called ClipGrab, which has to be compiled from its source code. It does work on Bodhi 5.1, but not in 6.0. What's happening in 6.0 is, I compile it, I move the resulting clipgrab file to /usr/bin and create the launcher in /usr/share/applications. Then I start it and first it looks quite well, but then it is trying to download youtube-dl, not sure if it succeeds. After that in ClipGrab the Search tab appears, where some clips should be offered, but there are only some dots turning round and round forever and when I look at the "About ClipGrab" tab, there should be some information about the youtube-dl version and the Python version. Usually those version numbers are in brackets, but these brackets are empty. I really would have liked to help you a bit with the development of Bodhi 6, but I have to confess, that's way too difficult for me, sorry. I don't even know if it's about some missing packages in Bodhi 6 because of its beta state, or some mistakes I may have done.
EDIT: I fogot to tell you, there might also be an issue with creating the grub in Bodhi 6 when the default kernel is used. Usually, the bootloader of Bodhi is in the bodhi folder of EFI, but to have something neutral for a multiboot, I tried to create this one:
sudo grub-install --bootloader-id=linboot
but there was no grub found, and I had to boot with a SuperGrub stick to fix this. Creating grub that way was only sucessful with the 4.18.20 kernel.
|
|