[Bug] Not running on one of the supported Live systems about go-appimage

[probonopd]

What if I just want to use the new appimaged because you already deprecated the old one ?
I don't exactly have a choice here, I need this program.

Well, it's not like the old one stopped working or anything - I am just not spending time on it anymore.

But I hear you... glad that you volunteer to test this thing on a non-Live system for the first time. Next build should remove the restriction.

[KaKi87]

Well, it seems you were right, because it was a nuclear bomb indeed. A minute after appimaged started, my whole start menu was gone, all my GUI programs seem to have been wiped and stop, it's a joke xD It's actually working very well. I had some appimage files in my Downloads directory, so appimaged notified me and they've been automatically added to my start menu. Then I downloaded a new one through wget and as soon as it ended, it was added too. Your software is working, stop restricting its access ^^

[probonopd]

Hello, as long as it is a Live ISO system it should work. (If not, post here and I will fix it immediately.) At this time, since the software is still experimental, it will run only on Live systems, but once it has been well-tested there it will be easy to remove this restriction.

Derivatives of Ubuntu, Debian, Deepin, Fedora, openSUSE,... should all work.

[KaKi87]

With all due respect, what the hell ?

Using appimaged in a live system defeats the purpose of enabling AppImage integration into the start menu which is meant for use in a daily basis.

Plus, since when does unstable software are prohibited for non-live usage ?

And, how accurate is the testing experience if it cannot be performed non-live ?

This is very ridiculous.

[probonopd]

Using appimaged in a live system defeats the purpose of enabling AppImage integration into the start menu which is meant for use in a daily basis.

Why? I use nothing but Live systems as my daily driver. To learn all about my setup, have a look at https://www.youtube.com/watch?v=0sRYL9IzkRQ

Plus, since when does unstable software are prohibited for non-live usage ?

I just want to ensure that it is not damaging anything as long as it is really bleeding-edge...

[KaKi87]

I use nothing but Live systems as my daily driver

Then how do you preserve apps, apps data and preferences, system settings and everything, drivers, etc., at each restart ?

I just want to ensure that it is not damaging anything as long as it is really bleeding-edge

Why do this while no one else does ?
Using unstable software is all about taking risks and as a user I assume that, you don't have the right to refuse it to me.

[probonopd]

I keep all of my apps as AppImages. I have a script that runs at runtime that does all the settings/configuration for me. I store my files online or on external media. Everything else is discarded at every reboot, which I love because it always gives me a clean new system.

Using unstable software is all about taking risks and as a user I assume that, you don't have the right to refuse it to me.

I am hearing you, so you say I should remove the restriction and you would not blame me if your computer ends up in flames?

On the other hand, isn't it easy to launch a Live ISO e.g., from USB or in a virtual machine to try something out?

[KaKi87]

What if I just want to use the new appimaged because you already deprecated the old one ?
I don't exactly have a choice here, I need this program.

[KaKi87]

I should remove the restriction and you would not blame me if your computer ends up in flames?

It's not on you, that's what's the MIT license is for :

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND

[KaKi87]

Regarding your way of life, I'm incompatible to it : everytime I have to reinstall a PC or a smartphone, must I spend 2 entire days reconfiguring everything.
I can't afford resetting everything.
Each tiny bit of cache, log, history, is necessary for me.

[probonopd]

Looking forward to your feedback on how it is working on a non-Live Linux Mint system.

[KaKi87]

We may want to go back to the more restrictive behavior in the future

What the hell ?

[probonopd]

If you can positively report back that it works on your specific distribution, it will go on the whitelist. :)

[KaKi87]

Why wouldn't it ?
Why are you speaking like if there was a nuclear bomb hidden in the program ???

[probonopd]

My philosophy is that it is broken unless someone tested it and found out it is not broken.

[probonopd]

Thank you very much for testing @KaKi87, highly appreciated.

I'm running Linux Mint

Which version and which desktop environment are you running?

[KaKi87]

Cinnamon. I can't remember the version, I'll check it out tomorrow at the office.

[KaKi87]

Cinnamon version : 4.4.8.

[probonopd]

Thanks @KaKi87. So it's Linux Mint 19.3 Cinnamon, correct? It would be great if you could post the result of cat /etc/os-release. Thanks 👍

[KaKi87]

See? #72 - it's not working for a user trying to run on a distribution that I have never intended this to run on.

It doesn't mean his computer was destroyed like if appimaged exploded like a nuclear bomb.

This situation is normal.

He's sharing his experience with you so that you can fix support for his system.

That's how open source development works.

[probonopd]

Here we go:
#258

Exactly as predicted.

We should put back the message so that the daemon only runs on supported (and tested) systems, imho.

Testing and supporting every Linux distribution is almost impossible, simply because there are so many and they are all different in subtle ways.

(This is what ultimately drove me away from Linux and toward FreeBSD: There is only one "distribution "that you have to support.)

[KaKi87]

Hello,

I'm still using appimaged to this day on multiple Mint & Ubuntu computers that are working fine.

Testing and supporting every Linux distribution is almost impossible

No one says you have to.

Also,

Cannot see volumes come and go

What does that mean ? Personally I don't get it.

[probonopd]

appimaged does not know how to get informed about disks that are attached and unattached to the computer on this operating system.

[probonopd]

I'm still using appimaged to this day on multiple Mint & Ubuntu computers that are working fine.

Then these should have been added to the whitelist.

No one says you have to.

But it leads to bug reports just like #258 when in fact that OS never was even tested.

[KaKi87]

appimaged does not know how to get informed about disks that are attached and unattached to the computer on this operating system.

Ok, got it.

Then these should have been added to the whitelist.

How could I have been able to report that the app works on these if these weren't whitelisted in the first place ?

See, this concept of yours doesn't make any sense.

But it leads to bug reports just like #258 when in fact that OS never was even tested.

Which is normal.

Now you can choose to fix or not to fix.

And in the second case you can even create a blacklist and put that distro in it if you want.

But please forget the whitelist.

[probonopd]

How could I have been able to report that the app works on these if these weren't whitelisted in the first place ?

We might have added something like --unsupported-distribution-just-for-testing or something like that.

People should know which systems this has been tested on.

[KaKi87]

People should know which systems this has been tested on.

In the README.

Not like this.