So after deactivating conda, compilation works, but I get no icons:
I guess this is because I’m running kubuntu, and I have some GTK icon library missing. Any idea which one? Source mentions hicolor, but I already have that installed.
I have successfully compiled and run Elektroid on a fresh Kubuntu 19.10 installation.
The only thing I noticed is that gettext was not installed, so I added it to the dependencies.
Notice that even the window icons are not showed in your screenshot so your issue might be somewhere else. However, I’m listing here the “icon” packages in that fresh installation in case it helps.
$ apt list --installed | grep icon
adwaita-icon-theme/eoan,eoan,now 3.34.0-1ubuntu1 all [installed,automatic]
apt-config-icons-hidpi/eoan,eoan,now 0.12.9-1 all [installed,automatic]
apt-config-icons-large-hidpi/eoan,eoan,now 0.12.9-1 all [installed,automatic]
apt-config-icons-large/eoan,eoan,now 0.12.9-1 all [installed,automatic]
apt-config-icons/eoan,eoan,now 0.12.9-1 all [installed,automatic]
breeze-icon-theme/eoan,eoan,now 4:5.62.0-0ubuntu1 all [installed,automatic]
gtk-update-icon-cache/eoan,now 3.24.12-1ubuntu1 amd64 [installed,automatic]
hicolor-icon-theme/eoan,eoan,now 0.17-2 all [installed,automatic]
humanity-icon-theme/eoan,eoan,now 0.6.15 all [installed,automatic]
libkf5akonadicontact-data/eoan,eoan,now 4:19.04.3-0ubuntu1 all [installed,automatic]
libkf5akonadicontact5abi1/eoan,now 4:19.04.3-0ubuntu1 amd64 [installed,automatic]
libkf5emoticons-bin/eoan,now 5.62.0-0ubuntu1 amd64 [installed,automatic]
libkf5emoticons-data/eoan,eoan,now 5.62.0-0ubuntu1 all [installed,automatic]
libkf5emoticons5/eoan,now 5.62.0-0ubuntu1 amd64 [installed,automatic]
libkf5iconthemes-bin/eoan,now 5.62.0-0ubuntu1 amd64 [installed,automatic]
libkf5iconthemes-data/eoan,eoan,now 5.62.0-0ubuntu1 all [installed,automatic]
libkf5iconthemes5/eoan,now 5.62.0-0ubuntu1 amd64 [installed,automatic]
libkpimgapicontacts5/eoan,now 19.04.3-0ubuntu1 amd64 [installed,automatic]
libtext-iconv-perl/eoan,now 1.7-6 amd64 [installed,automatic]
1 Like
Nope, I have all those installed 
Oh well, no big drama, it works, just not as pretty 
It would be really nice to have a resizable interface. I quite often can’t read the whole file name of some of my samples.
The window is currently resizable but not all components inside are. The only problematic component is the task list which is sometimes to narrow to be useful but I guess you’re talking about the file lists. I’m working on this at the moment.
Besides, in case you didn’t try already, take a look at a preinstalled application called “GNOME/GTK Application Style”. Maybe you can fix the icon issue by tweaking it.
Yeah, that did it, changing the icon theme away from Breeze to e.g. Adwaita or Humanity fixed it.
Oh yeah, I can maximise it by right-clicking on the top bar (hadn’t noticed that before), but I can’t find any resize handles. Maybe there’s something screwy with the GTK window decorations on my system.
Version 1.1 is out.
It includes recursive transfers and deletions, German support, a resizable task list and a lot of fixes and improvements.
I hope you enjoy it.
6 Likes
this is awesome - what do you use to load the sysex files?
Thanks!
I’m currently working to add this feature. It will be ready in some days.
In the meantime, this topic covers SysEx transmission and it’s what I would use.
1 Like
no rush - will test it in elektroid
Compiled it in Raspbian Buster but it doesn’t start, also doesn’t catch interrupts. Same for elektroid-cli. What am I doing wrong @DG2? 
As I tried executing the /usr/local/share/applications/elektroid file it said:
“The textfile “Elektroid” seems to be executable.”
That’s weird.
I have no clue about what’s going on but perhaps it’s related to the target architecture of your compiler toolchain.
On my PC, this is the compiled binary info.
$ file /usr/local/bin/elektroid
/usr/local/bin/elektroid: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=bf32ac845f0b1c9e9a2e48c2eda444edd442c0ca, with debug_info, not stripped
On yours, the architecture should be the Raspberry one (armel or armhf, not sure which).
Have you tried to compile and run another program using the same toolchain?
Am I even doing it right?
I opened up the terminal and typed ‘elektroid’ (same with ‘elektroid-cli ld’ for example).
The compiled binary info on my raspi:
pi@raspberrypi:~ $ file /usr/local/bin/elektroid
/usr/local/bin/elektroid: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV),
dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 3.2.0,
BuildID[sha1]=5c4e1ddc4132b1404dcfd16d995d0cb303d111fb, with debug_info,
not strippedCould you compare this to the output of, let’s say, file /bin/bash to see if there are any differences?
Besides, run elektroid -v -v to see if it ouputs anything.
Maybe you can try to list the libraries used by your own binary with ldd to check if any does not match your architecture. Perhaps, run it under gdb; it might say something.
I’m out of ideas, sorry.
1 Like
I forgot to mention that Elektroid made its way into Debian Sid some days ago. 
Here are the details and there is even an arm64 package. It might work for you.
3 Likes
I’ll try it out asap. I appreciate your help!!! 
I tried to install it with:
sudo dpkg -i /home/pi/Downloads/elektroid_1.1-1_arm64.deb
and it gives me the error:
package architecture (amd64) does not match system (armhf)
I have a Raspberry Pi 3 Model B v1.2 (2015) with a Quad Core 1.2GHz Broadcom BCM2837 SoC (ARM Cortex-A53 1200 MHz 64bit CPU)
So I found out that the raspi has an armhf (armv7l) architecture. Which elektroid package could work? (Sorry for the noob question 
)
Great news ! Not that it was difficult to compile but hey… an apt install is still easier.
1 Like
I’m currently on debian buster (yes, I switched from Ubuntu to Debian)
1 Like