I successfully installed red-app in Ubuntu Mate 20.04 and was able to download a few videos and sound files from YouTube. The following day, after ‘apt update’ and ‘apt upgrade’ the app would not load at all and I have not been able to get it to run since then. If I enter ‘red-app’ into a terminal I get the following error message:
"qt.qpa.plugin: Could not find the Qt platform plugin “xcb” in “”
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Aborted (core dumped)"
I have successfully installed red-app into a VirtualBox Ubuntu Gnome 20.04 VM running under Ubuntu Mate 20.04 and downloaded a sound file.
Anyone else had this problem or got any suggestions.
Actually doesn’t even install on my up-to-date Ubuntu 20.04 workstation. It remains stuck here:
$ sudo snap install red-app
Automatically connect eligible plugs and slots of snap "red-app" /
From /var/log/syslog:
May 3 00:00:36 hostname snapd[1195]: api.go:985: Installing snap "red-app" revision unset
May 3 00:00:38 hostname systemd[1]: Reloading.
May 3 00:00:38 hostname systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly.
May 3 00:00:38 hostname systemd[1]: Mounting Mount unit for red-app, revision 15...
May 3 00:00:38 hostname systemd[1]: Mounted Mount unit for red-app, revision 15.
May 3 00:00:38 hostname kernel: [11296.515983] audit: type=1400 audit(1588502918.964:153): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap-update-ns.red-app" pid=15284 comm="apparmor_parser"
May 3 00:00:39 hostname kernel: [11296.558432] audit: type=1400 audit(1588502919.008:154): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.red-app.red-app" pid=15285 comm="apparmor_parser"
May 3 00:00:39 hostname dbus-daemon[2163]: [session uid=165978 pid=2163] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.0' (uid=165978 pid=2159 comm="/usr/libexec/tracker-miner-fs " label="unconfined")
May 3 00:00:39 hostname systemd[2147]: Starting Tracker metadata extractor...
May 3 00:00:39 hostname tracker-extract[15292]: Set scheduler policy to SCHED_IDLE
May 3 00:00:39 hostname tracker-extract[15292]: Setting priority nice level to 19
May 3 00:00:39 hostname dbus-daemon[2163]: [session uid=165978 pid=2163] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
May 3 00:00:39 hostname systemd[2147]: Started Tracker metadata extractor.
May 3 00:00:44 hostname boltd[15096]: power: got event for guard '2' (10)
May 3 00:00:44 hostname boltd[15096]: power: guard '2' for 'fwupd' deactivated
May 3 00:00:44 hostname boltd[15096]: power: shutdown scheduled (T-20,00s)
May 3 00:00:44 hostname boltd[15096]: power: state changed: supported/wait
May 3 00:00:49 hostname systemd[2147]: tracker-extract.service: Succeeded.
May 3 00:01:04 hostname boltd[15096]: power: setting force_power to OFF
May 3 00:01:04 hostname boltd[15096]: power: state changed: supported/off
May 3 00:01:09 hostname tracker-store[15031]: OK
May 3 00:01:09 hostname systemd[2147]: tracker-store.service: Succeeded.
I have to interrupt the installation process, which yields:
May 3 00:04:09 hostname dbus-daemon[2163]: [session uid=165978 pid=2163] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.0' (uid=165978 pid=2159 comm="/usr/libexec/tracker-miner-fs " label="unconfined")
May 3 00:04:09 hostname systemd[2147]: Starting Tracker metadata database store and lookup manager...
May 3 00:04:09 hostname dbus-daemon[2163]: [session uid=165978 pid=2163] Successfully activated service 'org.freedesktop.Tracker1'
May 3 00:04:09 hostname systemd[2147]: Started Tracker metadata database store and lookup manager.
May 3 00:04:09 hostname systemd[1]: snap-red\x2dapp-15.mount: Succeeded.
May 3 00:04:09 hostname systemd[2147]: snap-red\x2dapp-15.mount: Succeeded.
May 3 00:04:09 hostname systemd[1]: Reloading.
May 3 00:04:10 hostname systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly.
May 3 00:04:10 hostname snapd[1195]: handlers.go:495: Reported install problem for "red-app" as already-reported
May 3 00:04:39 hostname tracker-store[15492]: OK
May 3 00:04:39 hostname systemd[2147]: tracker-store.service: Succeeded.
Note this message:
snapd[1195]: handlers.go:495: Reported install problem for "red-app" as already-reported.
Do you see similar messages in /var/log/syslog?
no, sorry
in my case red-app installs successfully but will not run and gives the error message already mentioned
Perhaps it’s best to contact the developer. I cannot find any sources, there’s this GitHub repo but it’s empty except for a README and LICENSE file - with GNU General Public License v2.0??
Yes, I’ve been in touch with the developer, Keshav Bhatt, who was very kind spending time with an exchange of some 35 emails helping me understand how snaps work and suggesting I try this and that but to no avail which is how I end up posting on this forum.
I’ve come to the conclusion that redd-app currently will not work on Ubuntu Mate 20.04 for some obscure reason but it certainly works on Ubuntu Gnome in a VM. I shall try it in a full install of Ubuntu Gnome 20.04 just to make sure.
