Main menu
You are here
No gui showing up, no link made (Ubuntu)
Hello,
I am a little puzzled because when I launch qmidinet from the console, no gui is appearing, and there is no error message. I see with Qjackctl that an Alsa port is created but I am unable to send data to a second Linux box on my local network (the 2 machines are connected thru a simple Ethernet cable, without any router).
The first computer runs Ubuntu 20.04 and the second Ubuntu 18.04, I tried the default bundled version of qmidinet then the appimage build v0.9.1 on both computer but it gives the same result. Yet the 2 Ethernet interfaces have MULTICAST enabled (ifconfig) and the kernel is compiled with the option (CONFIG_IP_MULTICAST=y)
I know very little about multicast I admit, could the kernel still be the problem ? I'm using the "lowlat" kernel from Ubuntu
$ cat /proc/version
Linux version 5.4.0-52-lowlatency (buildd@lgw01-amd64-060) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #57-Ubuntu SMP PREEMPT Thu Oct 15 12:05:45 UTC 2020
Or are there any other things to check ?
re. No gui showing up, no link made (Ubuntu)
hi,
qmidinet exposes itself as a GUI as a system-tray icon, though if your desktop environment doesn't support one, and gnome is infamously prone to just that by default, then you're left with the console or command line interface (cli) alone (ie. --no-gui)...
please refer to the cli options, as listed in `
qmidinet --help` or `man qmidinet`.hth.
cheers
re. No gui showing up, no link made (Ubuntu)
OK, I am using KDE. That would explain that. Good news, I was just able to make qmidinet work for the first time ! :)
The problem is on my first PC the default interface parameter "all" apparently fails. I have to add the option "-i eth3". The second PC is a not affected by that but has may be a simpler network configuration. For the record here are my ifconfig outputs for both PC:
PC1: Ubuntu 20.04
eth2: flags=4099 mtu 1500
ether 00:1e:8c:f2:90:a5 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 18 memory 0xf7c00000-f7c20000
eth3: flags=4163 mtu 1500
inet 192.168.1.4 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::2c57:e3f6:7c28:8265 prefixlen 64 scopeid 0x20
ether 00:1e:8c:f2:90:a1 txqueuelen 1000 (Ethernet)
RX packets 4769802 bytes 7120281410 (7.1 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 567973 bytes 84345294 (84.3 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xf7e00000-f7e20000
lo: flags=73 mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Boucle locale)
RX packets 241 bytes 23236 (23.2 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 241 bytes 23236 (23.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163 mtu 1500
inet 192.168.43.173 netmask 255.255.255.0 broadcast 192.168.43.255
inet6 fe80::eb:8cec:38e3:8ac2 prefixlen 64 scopeid 0x20
ether 48:51:b7:aa:67:ca txqueuelen 1000 (Ethernet)
RX packets 86315 bytes 83523572 (83.5 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 66814 bytes 7542322 (7.5 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
PC2: Ubuntu 18.04
enp3s0: flags=4163 mtu 1500
inet 192.168.1.3 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::70ee:85ef:1dcb:c73c prefixlen 64 scopeid 0x20
ether 00:24:1d:2e:aa:0b txqueuelen 1000 (Ethernet)
RX packets 573750 bytes 82501425 (82.5 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4823692 bytes 7181908063 (7.1 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73 mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Boucle locale)
RX packets 187016 bytes 6859187086 (6.8 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 187016 bytes 6859187086 (6.8 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Perhaps you have a better idea than me why auto detection doesn't work with the first PC. BTW. wlan0 is for my smartphone 4G access but is not used to connect to the second PC. I use manual configuration for IP (192.168.1.4 and 192.168.1.3 on the 2 PCs).
Add new comment