[00:00] <ThomasWard[m]> stupid question: any output logs in syslog?
[00:00] <ThomasWard[m]> snap logs don't always go to stderr
[00:00] <ThomasWard[m]> because confinement, etc.
[00:00] <ThomasWard[m]> just, you know, snaps being snaps.
 "killall freeshow" <- pass -9 in there for a nuclear strike on all processes too (SIGKILL)
[00:01] <OvenWerks> ThomasWard[m]: theres nothing running in ps x
[00:01] <ThomasWard[m]> (I'm late to the discussion sorry)
[00:03] <OvenWerks> reboot did not fix :)
[00:16] <OvenWerks> rm -r ~/snap/freeshow
[00:16] <OvenWerks> that worked
[00:18] <Eickmeyer> Sounds like the prefs got corrupted then.
[00:21] <OvenWerks> Ok, I have a show, I have songs selected. I have added a slide (which sounds wrong... but where do I pull in a song from?
[00:21] <OvenWerks> I would think I can pull in a chordpro file and it would split it into slides automatically
[00:22] <OvenWerks> (just from using openlp)
[00:25] <OvenWerks> Ok, I have pulled it in as a text file. so import. There is no import songs... no direct import from a website
[00:25] <OvenWerks> It does not know how to deal with chordpro files
[00:26] <Eickmeyer> Ah, bummer. Well, it was worth a shot.
[00:27] <Eickmeyer> I think direct import from a website is on the roadmap, but it's just one dev, so it'll take time.
[00:28] <OvenWerks> timers is the problem. when I click on the timers button it frezzes.
[00:29] <OvenWerks> freezes
[00:33] <OvenWerks> Eickmeyer: snap removed. I think openlp is much nicer than what I have seen so far... I am not thrilled with that either :) but it works, it is easier to use (I think anyway) and it directly import lyrics from file or Inet
[00:34] <Eickmeyer> Yeah, that's fair.
[00:34] <OvenWerks> of course the main thing is freezing is not acceptable
[00:35] <Eickmeyer> Right. Perhaps could you report that to the dev? https://github.com/vassbo/freeshow/issues
[00:35] <OvenWerks> (or going into a mode where most actions are turned off with no obvious way of getting out)
[00:35] <Eickmeyer> I honestly am not in an environment anymore where I can use it regularly, I just want to make sure it's available so people can test and use it.
[00:36] <Eickmeyer> BTW, I can duplicate that bug.
[00:38] <OvenWerks> I suspect there is a keystroke or button that turns the timer off... I just don't know what.
[00:39] <OvenWerks> Eickmeyer: https://freeshow.app/docs/styling is a good page to have in general
[00:40] <Eickmeyer> Oh, absolutely. I've seen so many churches completely miss this.
[00:40] <OvenWerks> lyricue is the oldest and has lots of good things about it, but it's server client setup is not obviously easy to set up
[00:41] <OvenWerks> openLP seems to be the next most mature of the bunch
[00:43] <OvenWerks> opensong is easier to use, I think, but not as nice in the long run.
[00:50] <OvenWerks> opensong is much easier to use actually, but it is limited in what it can do it seems.
[01:05] <OvenWerks> sessioncharts comes up fg/bg both white
[01:41] <Eickmeyer> OvenWerks: Using the webapp or...?
[01:44] <OvenWerks> the snap... actually I can't tell if there is anything at all in there I am just assuming there is something there because of changing cursor or whatever. I did try changing system themes to see if that would help. The webapp is broken in a different way. It opts out on chordpro files it doesn't like commands in. It should ignore things it doesn't know and show everything else.
[01:44] <OvenWerks> so both are bad.
[01:46] <Eickmeyer> The snap hasn't seen an update in over a year, so I'm not surprised by that.
[01:47] <OvenWerks> Yeah, the web page says to prefer the webap I suppose it can be run locally too?
[01:47] <OvenWerks> but the webapp doesn't work anyway.
[01:47] <OvenWerks> so back to anbox I guess
[01:49] <Eickmeyer> The web app only runs locally in a Chromium-based browser, I guess.
[01:53] <OvenWerks> Ah, I should try it in chromium?
[01:56] <Eickmeyer> Might work better.
[01:57] <OvenWerks> nope, I can't even import local files (no error) not added to the songs list.
[01:59] <Eickmeyer>  ¯\_(ツ)_/¯
[02:00] <OvenWerks> So far my experience with snap applications has not been stellar...
[02:01] <OvenWerks> I suspect that is about the included libs. Whatever is not included has to use system libs
[02:02] <OvenWerks> FF has the resources to test on enough different ystems to catch that stuff I guess.
[02:04] <OvenWerks> So effectively snap encourages a dev to spend even less time keeping up with other software deveopment that they depend on.
[02:11] <Eickmeyer> Not exactly. Snaps roll-up a core of the OS followed by any of their dependent libs. They use no outside libs at all.
[02:12] <OvenWerks> What I would expect but the quality of snap apps has been (so far) not exceptional.
[02:13] <OvenWerks> FF has been pretty good aside from the anoying your app will up date in 14 days so you better close it over and over again.
[02:14] <OvenWerks> (maybe they have fixed that, I haven't seen one in a bit on this machine)
[02:15] <Eickmeyer> "The snap file format is a single compressed filesystem using the SquashFS format with the extension .snap. This filesystem contains the application, libraries it depends on, and declarative metadata. This metadata is interpreted by snapd to set up an appropriately shaped secure sandbox for that application. After installation, the snap is mounted
[02:15] <Eickmeyer> by the host operating system and decompressed on the fly when the files are used."
[02:17] <Eickmeyer> When you see that prompt, you can close it, open a terminal, "sudo snap refresh" and be done. They're actively working on a fix.
[02:18] <Eickmeyer> But yes, the Webapp capabilities of the Chromium snap are lacking, for sure.
[02:18] <Eickmeyer> I think the best workaround for that is installing the chromium snap via "sudo snap install chromium --classic" to put it in classic confinement, which disables a lot of the sandboxing.
[04:17] <OvenWerks> Eickmeyer: linux-oem-22.04b boots. and my touchscreen/stylis works
[04:18] <OvenWerks> :)
[04:18] <Eickmeyer> Oh, perfect!
[04:33] <OvenWerks> ok, back to anbox :P https://docs.anbox.io/userguide/install_kernel_modules.html says 
[04:33] <OvenWerks> Starting with Ubuntu 19.04 binder and ashmem are now build with the standard Ubuntu kernel (>= 5.0) and you don’t have to install the modules from the PPA anymore.
[04:34] <OvenWerks> then it says:$ sudo modprobe ashmem_linux
[04:34] <OvenWerks> $ sudo modprobe binder_linux
[04:34] <OvenWerks> the first one fails but the seond one is ok.
[04:35] <OvenWerks> Now you should have two new nodes in your systems /dev directory: /dev/ashmem and /dev/binder
[04:36] <OvenWerks> nope.
[04:39] <OvenWerks> https://salsa.debian.org/kernel-team/linux/blob/master/debian/patches/debian/android-enable-building-ashmem-and-binder-as-modules.patch says: Update:
[04:39] <OvenWerks> In upstream commit 721412ed3d titled "staging: remove ashmem" the ashmem
[04:39] <OvenWerks> driver was removed entirely. Secondary commit message:
[04:39] <OvenWerks> Consequently, the ashmem part of this patch has been removed.
[04:39] <OvenWerks> "The mainline replacement for ashmem is memfd, so remove the legacy
[04:39] <OvenWerks> code from drivers/staging/"
[04:40] <OvenWerks> Eickmeyer: so does that mean it will work or not?
[04:40] <Eickmeyer> I don't know about anbox. I've never had luck with it.
[04:47]  * OvenWerks is begining to see why
[04:47] <OvenWerks> i may be playing with wine next :p
[04:54] <arraybolt3> OvenWerks: Don't forget about Waydroid.
[04:55] <OvenWerks> arraybolt3: I did not know that existed
[04:55] <arraybolt3> OvenWerks: 
[04:55] <arraybolt3> It requires Wayland, but works pretty well in my experience.
[04:55] <OvenWerks> ah,
[04:55] <arraybolt3> It's supposedly based on Anbox, but works way better and uses a newer version of Android under the hood.
[04:55] <arraybolt3> (I just loaded it into Weston and called it a day :P)
[04:56] <OvenWerks> does ubuntustudio even have wayland in it?
[04:56] <arraybolt3> OvenWerks: Not by default, but I think you can install kwin_wayland (if you like playing with fire that is).
[04:56] <Eickmeyer> Not yet, but you can get it with "sudo apt install plasma-wayland-session" or something like that.
[05:07] <OvenWerks> anbox is no good it depends on modules that can't be used/ no longer exist.
[05:10] <OvenWerks> Eickmeyer: close but that is not the package
[05:13] <OvenWerks> plasma-workspace-wayland?
[05:14] <arraybolt3> OvenWerks: That looks like it to me, the description says "This package contains the Wayland session."
[05:20] <Eickmeyer> OvenWerks: Yes.
[05:28] <OvenWerks> https://github.com/anbox/anbox/issues/2042 says anbox is effectively dead (unless it is being run on an outdated kerenl
[05:28] -ubottu:#ubuntustudio-devel- Issue 2042 in anbox/anbox "ashmem being removed in upstream and Debian kernels" [Open]
[06:14] <OvenWerks> wayland displaays things funny
[06:14] <OvenWerks> many of my saved settings are gone too. :P
[06:21] <OvenWerks> waydroid uses lineage
[19:28] <OvenWerks> Waydroid successfully installed. The two apps I need are both available for it. (I actually only needed one of two)