K3b: Difference between revisions

Nika03 (talk | contribs)
WIP - Creation of the article
Nika03 (talk | contribs)
m Categories
 
(4 intermediate revisions by the same user not shown)
Line 34: Line 34:
== Post-Installation ==
== Post-Installation ==
After the reboot, open K3b for post installation configuration within the software.
After the reboot, open K3b for post installation configuration within the software.
[[File:K3b Post-Installation - Opening K3b Configuration dialog.png|alt=Settings >> Configure K3b...|left|thumb|474x474px|1. Open the K3b Configuration dialog]]
----Within the K3b settings, paths to the external programs have to be tweaked to the ones that work with K3b out of the box in case that hasn't been the case after the installation.
 
First, navigate to the settings via the toolbar by clicking ''"Settings"'', and on the bottom of the list ''"Configure K3b..."''.
 
Alternatively, you can use the shortcut: <code>Ctrl + Shift + ,</code>[[File:K3b Post-Installation - Opening K3b Configuration dialog.png|alt=Settings >> Configure K3b...|thumb|468x468px|1. Open the K3b Configuration dialog|none]]
----Within the settings, the paths for each path must be set in a following priority depending on if they're present:
# <code>/run/wrappers/</code>
# <code>/run/current-system/</code>
# <code>/nix/store/</code>
 
Under <code>/run/wrappers/</code>, the executables have all the permissions necessary to run under K3b. Using paths other than that may cause errors, such as ''"'''cdrecord has no permission to open the device'''"''.
 
There isn't much difference between using <code>/run/current-system/</code> and <code>/nix/store/</code>, except that <code>/run/current-system/</code> is a link to the current version of the executable and <code>/nix/store/</code> directly points to a specific version installed.
 
Seeing programs that don't have a wrapper or a <code>current-system</code> link doesn't necessarily mean that there's something wrong however. Everything should work fine regardless. [[File:K3b Post-Installation - Setup External Programs.png|alt=Programs >> Programs |thumb|564x564px|2. Set the paths to the proper programs |none]]
----The permissions the external programs have are very important, as they may not have the access to the optical drive(s) to perform the operations.
 
If there are any programs listed under the ''"Permissions"'' tab that have ''"New permissions"'' listed that aren't ''"no change"'', it may be wise to remount <code>/nix/store/</code> to change the permissions to make sure that things are set.
 
Run this line in your shell to remount <code>/nix/store/</code> with read/write permissions so that K3b can change these if necessary:<syntaxhighlight lang="bash">
sudo mount -o remount,rw /nix/store
</syntaxhighlight>Then click ''"Change Permissions..."''. A dialog for the superuser password will open, and after entering it, the permissions to the programs will be set to the correct values.
 
In case of any permission issues later on, this step can be done more than once.[[File:K3b Post-Installation - Setting external program permissons.png|alt=Programs >> Permissions|thumb|564x564px|3. Check and set the permissions of the external programs as necessary|none]]
 
[[Category:Applications]]
[[Category:KDE]]