For anyone arriving at this thread looking for MakeMKV for Solus, the snap is now released to "stable" channel and it's working like a charm!

In T7010#146208, @betterunborn wrote:

Very old thread, but does this still apply?

I just built & installed makemkv 1.14.3 from source. Build dependencies are system.devel, qt5-devel and ffmpeg-devel (4.1.1), no problem at all.

Also I can see no functional restriction so far.

This issue needs further investigation. I have 3 separate Solus installs and each has (and has had) the same issue. It's getting a little wearying to keep reinstalling snapd or reloading apparmor, etc.

In T6573#141732, @Girtablulu wrote:

Which snap?

Yeah systems are always fully updated.

I almost opened another bug report for this issue. I reinstalled snapd and got my snaps running again. They fail to run (apparmor DENIED...) after I reboot or logout. I can reinstall the snap or reinstall snapd but this seems as though it might deserve some further attention.

In T7277#137482, @Girtablulu wrote:

32-bit nvidia driver installed?

In T6020#136955, @kyrios123 wrote:

I'm not sure what you're referring to as far as an expiring license. My MakeMKV license has no expiration.

Unlike what MakeMKV says on its web site, you can't use all functionalities for free during 30-days trial period. The application is shipped with a demo license that expires on a given date. When the license is expired either you purchase a new license or you install a newer version of MakeMKV.

This means that if you install the application today and the license expires tomorrow, after a few hours the application will stop working and if you install it tomorrow it won't work at all. This is not a 30-day trial and for the user experience, this terrible IMO.

And when this happen, either you have to purchase a license or... as a user you're stuck and there is nothing you can do apart from waiting.. and here comes the 2nd issue: it is not normal that upstream dictates when the application must be updated. Solus has its own publication rules. If Solus can't insure that an application in its repository works fine, then the application shouldn't be offered in the repository !

In T6020#134308, @DataDrake wrote:

We also removed it because their licensing is cumbersome. Having something stop working between syncs because a license expires is not OK.

We can close this as this issue doesn't necessarily apply anymore. That is, unless you want to leave it open for others who may experience the same issue.

Once you start Android studio, it will install all your tools in your home folder under ~/Android/Sdk/platform-tools

In T6020#125984, @JoshStrobl wrote:

I deprecated it because it was blocking ffmpeg 4 stack upgrade and wouldn't function properly against it, it's practically limping along in development. It's not being re-introduced into the repo.

In T4419#125939, @LostSouls wrote:

Can this task being reopened?

Second time (yesterday/today) that my desktop froze: kwin_x11 running 'hot' (100%). Had to restart.

In T6020#125873, @joebonrichie wrote:

MakeMKV has now been deprecated from the repo.

sudo snap install android-studio --classic

Just gonna bump this. I've experienced the same issue since install and haven't found a fix (that works) yet.

I can confirm this issue & workaround.

In T272#104448, @Snuggle wrote:

In T272#100705, @Moilleadoir wrote:

For anyone finding this thread Clementine is available as a snap.

snap install clementine

The snap looks god-awful. It has a Windows 98 theme. ):
Waiting on the qt5 branch, too! ?

Recommend this package be "snapped". Will prevent many of the issues presented here. Looking into possibility of doing so. Stand by for update.

As per m-delvalle, issue resolved.

Can confirm same bug:

NO SOUND! Kids were sleeping. I thought a video demonstrating the differences might be better.

In T710#11636, @ikey wrote:

Handbrake is a horror show.. @kz6fittycent side-by-side screenshots might help here :D

Winff is a little easier to navigate, light weight and can convert a number of codecs to a number of other codecs. Handbrake can too but it's a little more daunting maybe for a new user.

The issue remains. Telegram is NOT trying to force an update (as I am on the latest). It is requiring a new setup after reboot (random reboot at that). I thought you'd fixed it, too. However, the issue is apparently something different. I've been using Telegram on Linux (several distros) for some time now and this issue is "Solus only". I am not sure what is happening. Would you like any additional information?