Filebot update using Snapd not working - can't access /media folder

Support for Ubuntu and other Linux distros
Post Reply
User avatar
Mustang
Posts: 9
Joined: 07 Aug 2017, 15:50

Filebot update using Snapd not working - can't access /media folder

Post by Mustang » 11 Aug 2017, 00:48

I recently updated Filebot from 4.7.5 to 4.7.9 on my Ubuntu 16.04 home server. The previous version was working just fine, actually it was working awesome. I got tired of the pop up window saying there was a new version, so decided to update Filebot. Boy has that turned into a frustrating event.

I couldn't find a .deb package to update because you have to install Filebot using Snapd now. I figured that would be easy enough.

First, I used the following to remove the old version. I didn't receive any errors and all indicated it was removed successfully

Code: Select all

sudo apt remove filebot
Then I used the following to install Filebot using Snapd. I didn't receive any errors and everything seemed to go fine.

Code: Select all

sudo snap install filebot
I saw the sticky'd post in the forums about accessing folders outside /home folder, so I ran the following:

Code: Select all

sudo snap connect filebot:removable-media
I then checked the connection to make sure it was entered properly. I ran the following command and verified it was good to go.

Code: Select all

snap interfaces
Slot                      Plug
:account-control          -
:alsa                     -
:autopilot-introspection  -
:avahi-observe            -
:bluetooth-control        -
:browser-support          -
:camera                   -
:classic-support          -
:core-support             core:core-support-plug
:cups-control             -
:dcdbas-control           -
:docker-support           -
:firewall-control         -
:framebuffer              -
:fuse-support             -
:gsettings                filebot
:hardware-observe         -
:hardware-random-control  -
:hardware-random-observe  -
:home                     filebot
:io-ports-control         -
:joystick                 -
:kernel-module-control    -
:kubernetes-support       -
:libvirt                  -
:locale-control           -
:log-observe              -
:lxd-support              -
:modem-manager            -
:mount-observe            -
:netlink-audit            -
:netlink-connector        -
:network                  filebot
:network-bind             filebot
:network-control          -
:network-manager          -
:network-observe          -
:network-setup-control    -
:network-setup-observe    -
:ofono                    -
:opengl                   filebot
:openvswitch              -
:openvswitch-support      -
:optical-drive            -
:physical-memory-control  -
:physical-memory-observe  -
:ppp                      -
:process-control          -
:pulseaudio               filebot
:raw-usb                  -
:removable-media          filebot
:screen-inhibit-control   -
:shutdown                 -
:snapd-control            -
:system-observe           -
:system-trace             -
:time-control             -
:timeserver-control       -
:timezone-control         -
:tpm                      -
:uhid                     -
:unity7                   filebot
:upower-observe           -
:x11                      filebot
Here is my Filebot info:

Code: Select all

filebot -script fn:sysinfo
FileBot 4.7.9 (r4986)
JNA Native: 5.1.0
MediaInfo: 0.7.82
7-Zip-JBinding: 9.20
Chromaprint: 1.2.0
Extended Attributes: OK
Unicode Filesystem: OK
GVFS: PlatformGVFS [/run/user/1000/gvfs]
Script Bundle: 2017-05-15 (r500)
Groovy: 2.4.10
JRE: OpenJDK Runtime Environment 1.8.0_121
JVM: 64-bit OpenJDK 64-Bit Server VM
CPU/MEM: 4 Core / 1 GB Max Memory / 26 MB Used Memory
OS: Linux (amd64)
Package: SNAP
uname: Linux GatorServer 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:38:41 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Done
Unfortunately, I still can't access my files which are located in my /media folder. It's quite frustrating to move from a perfectly working system to one that no longer works, just by updating to the newest version.

Do you have any other suggestions, because I'd like to get Filebot working again?

Thanks in advance.

User avatar
rednoah
The Source
Posts: 12153
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Filebot update using Snapd not working - can't access /media folder

Post by rednoah » 11 Aug 2017, 04:54

You can ask the snapd team about how to report and debug confinement issues.

I'd just use --devmode to disable confinement completely if that's causing trouble for you:

Code: Select all

sudo snap install filebot --devmode

PS: Legacy deb packages are available on sourceforge in the download section.
My (very excellent) support depends on Windows Store and Mac App Store sales and PayPal donations. Paying users, donors and everyone who contributes to FileBot in one way or another will get the very best support.

Image

Please read the FAQ and How to Request Help. Donate if you'd like some extra developer love. :ugeek:

User avatar
Mustang
Posts: 9
Joined: 07 Aug 2017, 15:50

Re: Filebot update using Snapd not working - can't access /media folder

Post by Mustang » 11 Aug 2017, 16:51

Yes, installing in devmode might work, but doesn't that defeat the purpose of distributing your software via an application like Snapd. From what I understand, this will remove all the security features inherit to Snapd software, which itself is a big selling point.

BTW, I can't find Filebot version 4.7.9 on Launchpad.net :( I guess I can just reinstall an older version from the standard Ubuntu distribution, but I'd rather use the latest and greatest version.

Just curious... why did you shift to Snapd for distribution if it doesn't completely work correctly? (not trying to be an arse, just trying to have a conversation) We can blame Snapd for not implementing the software correctly, but in the end, it's your software, isn't it?

I'll give devmode a shot. I don't intend on installing any other Snapd software for the time being, so it shouldn't an issue for now.

Thanks rednoah! :D

User avatar
rednoah
The Source
Posts: 12153
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Filebot update using Snapd not working - can't access /media folder

Post by rednoah » 11 Aug 2017, 19:07

It works correctly for me and mostly everyone else as far as I know.

No idea why the /media plug doesn't work on your particular machine. Maybe there's a reason. Maybe it's a bug. IDK. ;)

Ubuntu doesn't support anything other than snapd for 3rd party developers.

All the tradition Debian packages are maintained by official Ubuntu maintainers. I am not, so I can't publish Debian packages via the official sources.
My (very excellent) support depends on Windows Store and Mac App Store sales and PayPal donations. Paying users, donors and everyone who contributes to FileBot in one way or another will get the very best support.

Image

Please read the FAQ and How to Request Help. Donate if you'd like some extra developer love. :ugeek:

User avatar
Mustang
Posts: 9
Joined: 07 Aug 2017, 15:50

Re: Filebot update using Snapd not working - can't access /media folder

Post by Mustang » 21 Aug 2017, 19:54

I got it working with devmode.

I'll reach out to the snapd folks and try to find out why the /media plug isn't working.

Thanks again rednoah. Great product!

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests