very strongly implied by subsequent posts and self research before and after own install
1 Like
It could just be due to original poster’s lack of knowledge? 
1 Like
I would say … don’t do that. In particular, if you do do that and it doesn’t work then uninstall it and go again with a more standard approach.
Edit: To elaborate on that … this goes to the core of the question that I originally asked as to whether the installer itself creates the directory and file(s), or the directory and file(s) are created on first run. In general, the former is “badness” and it will malfunction in scenarios such as having a separate admin user.
1 Like
All “sudo apt…” installs are essentially done by root and executables, including goodvibes are usually in /usr/bin. libraries, documentation, etc have their own standard locations, but distros, packagers, and programmers might have their own ideas of where things go.
I have been unable to find where the contents of stations.xml come from. Maybe they are built into the executable or it gets downloaded.
The bash command
which goodvibes
is a good way to pinpoint it, although there is always a risk that it is not in $PATH and has to be launched by tapping an icon.
I did
sudo find / -name \*goodvibes\*
to find all things goodvibes.
(I don’t see why having to toggle WYSIWYG to close a block doesn’t count as a discourse regression.)
2 Likes
I noticed when I first installed it on the L5, the app had some included stations loaded but did not create the ~/.local/share/goodvibes/stations.xml. That folder and file are present on my computers, and I know I didn’t manually create them, so either:
- it normally happens at installation (but not on the L5 for some reason), or maybe
- it gets created only after you add a new station…?
If I remember correctly, I did purge and reinstall on a computer to verify the creation of the folder/file, though, and it was created. EDIT: Just did this again, and I think it only gets created after adding a new station.
On a positive, unrelated note: although Goodvibes doesn’t have an “export stations list” option, you can just copy that stations.xml file to a new install and repopulate all your saved favorites.
2 Likes
So it should work fine regardless of whether you have an admin user.
2 Likes
On a whim, I tried launching goodvibes from a Terminal, which worked. I then provoked a crash by tapping a station and the result is attached, which might be helpful for the developer or packager.
1 Like
Which version of the application are you running?
This appears to be issue: Crash when playing station from touchscreen devices (Debian 11, version 0.6.2-1) which was fixed in v0.7.2.
I’m guessing you are installing from PureOS Byzantium repos? PureOS Byzantium pacakges v0.6.2.
Try running version v0.7.2 or higher.
4 Likes
For me, it got added when I exited without crashing.
1 Like
That’s the same error I posted.
1 Like
What version does crimson package?
Maybe @amarok could feasibly reflash to crimson.
1 Like
Crimson packages Goodvibes v0.7.6
Upgrading an entire OS to get a newer version of a single application seems a bit extreme to me, especially as the upgrade would be to a pre-release developement version of the OS. While some things may be fixed, it’s likely to introduce addition problems which may have some impact on general usability.
For what it’s worth, I built the source from the Crimson repo on Byzantium and it works fine with regard to this issue, selecting stations by touching them directly works as expected, no crash.
Only the source of the application from Crimson is required, all the dependencies from byzantium are of suitable/usable versions.
3 Likes
I completely agree with your general concerns, although some customers may consider having to build a program from source to be likewise extreme (too hard / make a mistake due to lack of assumed knowledge / scary / unable to resolve build problems if they arise / …).
I took into account that @amarok has publicly stated that he is not using the Librem 5 as his main phone (yet) and therefore may be better able to accept any unrelated regressions.
It is always possible to image the current byzantium install before reflashing to crimson - leaving the option to back out of the reflash if crimson is too problematic.
3 Likes
I get that many people will want to stay clear of compiling sources, personally however, I’d be less concerned about someone with little to no prior knowledge or experience attempting to compile an application than I would about them working with drive images.
PureOS inherits all of Debian’s tooling and Debian provides tools that can ease and simplify compiling from source, resolving denpendencies, etc,., particularly if you’re doing a straightforward build from Debian sources just from a newer version.
2 Likes