with three inputs (-i flag) -- a video file, and two audio files.
The streams are explicitly mapped into the result, counting the inputs from 0 -- i.e. -map 0:v maps input 0 (the first file) as video (v) to the output file and -map 1:a maps the next input as audio (a), etc.
It sets the metadata for the audio tracks -metadata:s:a:0 language=jpn sets the first audio track (again counting from 0...) to Japanese; the second metadata option sets the next audio track to English.
-c:v copy specifies that the video codec should be copied directly (i.e. don't re-encode -- remove this if you DO need to re-encode)
-c:a copy specifies that the audio codec should be copied directly (i.e. don't re-encode -- remove this if you DO need to re-encode)
output.mp4 -- finally, list the name of the file you want the result written into.
Work on a KF5 release had already started years ago and was mostly completed. With the recent revival of the project, it made sense to take things one step at a time and complete the KF5 port first.
So I wanted to give Klevernotes a try tonight but:
it doesn’t show up in Discover when searching for any of the terms Klevernotes, Klever Notes, or just klever. On the command line apt search klevernotes returns an empty result set.
the install on Linux link on apps.kde.org/klevernotes/ doesn’t work either. It opens Discover but yields the error message Could not open appstream://org.kde.klevernotes because it was not found in any available software repositories. Please report this issue to the packagers of your distribution.
I tried building it myself via the instructions on the GitHub repo but got stuck among the way. Building binaries is a bit beyond my expertise unfortunately.
I’m on Kubuntu 22.04 with KDE Plasma 5.24.7 in case that matters. Can also file an official bug report as the error message suggests if you advocate for it.
Thanks you for wanting to give it a try, and also to explain the issue clearly without being agressive, that really nice to see.
Klevernotes is a new project (± 1 year old) and doesn’t have a package right now (working on flatpak). So it’s pretty normal to not find it in Discover nor apt.
You guessed it right, you need to compile the project to test it.
I can try to guide you on how to use kde-src build to build klevernotes, but that might be a bit overkill since it will build every dependencies (useful for devs, a bit less for user). Or I can let you know when the flatpak is ready.
For your unit files, you have Wants in the [Install] section. That is not correct. Wants belong in the [Unit] section. The [Install] section is where you define WantedBys. You may want to read the man page for systemd.unit.
To interact with user services, you do have to always use systemctl --user.
If you put your user unit files in /etc/systemd/user, they're accessible to all users. If a particular user wants to enable the service, they can run systemctl --user enable $service. Defining the unit in ~/.config/systemd will mean only the one user will be able to start the service. Defining the unit in /etc/systemd/system indicates it is not a user service but a system service.
Every user can enable services from /etc/systemd/user for their account. If the user doesn't log in, their instance of the service won't start. There is a way to have user services launch without logging in, but that would obviously be nonsensical for desktop services.
I don't think systemd would find units in /etc/systemd/user/KDE. Look at the mess that is /usr/lib/systemd/system. Organization doesn't seem to be a thing.
I am still a bit confused about systemd services, timers, units, targets and whatever but slowly getting there.
Also do you know how dbus activation would make sense, if it is already used in some ways and if it should be?
I think nearly all these services should run as user ones. I will fix their Wants entry and try to enable them again. Then see if some are dependencies of others, and the other way around on what they depend (like graphical.target, network-online.target, network.target etc).
Also I feel something with accessibility can be improved here, as orca and kaccess may be invoked intelligently (and otherwise dont bother users).
I think systemd targets work opposite to your expectation. The Wants in [unit] define the things that that unit needs to already be available. For instance, you might add Wants=network.target to the unit for nginx so that it won't try to start until the network is available. When I wrote a unit to start my company's application, I also had Wants=postgresql.service to ensure that the database came up before the application. Remember that sysyemd tries to run as many things in parallel as it can. This is one thing that makes it much faster than classic sysvinit which started things sequentially. But it means race conditions can occur. You use Wants to break those races where necessary. The targets that you'd specify in WantedBy in [install] more closely resemble SysV runlevels. You might want to read how runlevels used to work in SysV, in order to understand systemd targets.
Requires: If a unit "requires" another unit, it means that the former cannot function properly without the latter being active. If the required unit fails, the dependent unit will also fail.
Wants: As mentioned earlier, "wants" implies a weaker dependency. If a unit wants another unit, it will start if the wanted unit is activated, but it won't fail if the wanted unit fails.
Sounds like most of the services actually have Requires and not Wants.
So Wants is more used to indicate in what "wave" a service should run. Quite nice!
I fixed them and edited the post. There now is a Github repo for the script, and guess what? Most services still run, so there are at least 2 mechanisms to start them. What a mess
I have a big gaming desktop and at first it felt kinda slow, but then I found out it was happening because of the previous plasma 5 config messing with things, and the variable refresh rate affecting the mouse cursor movement.
Sorry for this. I didn’t check that old laptop till yesterday to check for other issues unrelated to Plasma, which was when I discovered that the fan died.
I’m running Plasma 5 on my i5 5200U on iGPU on X11 and it’s pretty much stable and solid (it’s not riced a lot though), isn’t Plasma 6 still pre-release?
Sorry for this. I didn’t check that old laptop till yesterday to check for other issues unrelated to Plasma, which was when I discovered that the fan died.
Don’t create a social media hype of something before discussing it with Plasma devs. That’s obviously going to antagonise people, and puts us in an awkward situation afterwards.
Looks like this “vote” is not really official and blindsided the devs a bit.
discuss.kde.org
Top