Hi,
I have searched the forums, but for some reason K3B is not recognising the blank CD placed into the drive when i select BURN, yet it does display the CD-R detrails - empty, space etc. in the relevant window.
As such how do i allow the K3B program to burn the files - error message is “Please insert a suitable medium”.
Thanks and regards,
Richard.
On 2014-08-29 13:56, shadders wrote:
>
> Hi,
>
> I have searched the forums, but for some reason K3B is not recognising
> the blank CD placed into the drive when i select BURN, yet it does
> display the CD-R detrails - empty, space etc. in the relevant window.
You could try “dvd+rw-mediainfo”.
> As such how do i allow the K3B program to burn the files - error message
> is “Please insert a suitable medium”.
It can say that if what you are going to burn does not fit (830 MB in a
600 MB CD, for instance). Or if the media is not really unused: even an
aborted burn inutilizes a disk, unless it is a rewritable one.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
hi,
all CD/DVD writers are not equal, it all depends on the frequency of the laser they use
hence CDs and DVDs may work on one burner but not on another
suggest trying a CD/DVD from another manufacturer
btw trying to re-burn a rewritable on my DVD burner was given up as hopeless years ago.
hth
Hi All.
Thanks for replying. I have tried different media - Verbatim and Sony - one was the CD-R and the other was a DVD-R and still did not recognise.
Is this a K3B Setup issue - from the menu ?. (Settings -> Setup System Permissions)
The size of the files is less than the capacity of the CD-R.
The drive can read obviously - displays the blank CD-=R information no issue - but cannot write - so it this a permissions issue somewhere buried deep in the system ?.
Thanks and regards,
Richard.
Hi,
I tried :
You could try “dvd+rw-mediainfo”.
And there was no response to state an empty disk in the system - although K3B picked up the empty CD-R.
I then ran K3B as root and this works.
As such - is a permissions issue - have seen internet forums stating you need to add yourself to permissions - in ideas how to do that ?.
Thanks and regards,
Richard.
As //dev/srX is normally owned by root:cdrom (with rw permissions for owner and group), you could add your user to the cdrom group.
But you should not have to.
The logged in user should get permissions to access the device automatically.
Please post the output of:
getfacl /dev/sr*
On 2014-08-30 15:06, shadders wrote:
> I then ran K3B as root and this works.
>
> As such - is a permissions issue - have seen internet forums stating you
> need to add yourself to permissions - in ideas how to do that ?.
Did you perhaps change the security settings in YaST from easy to secure?
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Use k3b 2.0.80+git* from Packman. It helps you via Settings -> Configure K3b… -> Programs -> Permissions. Also make sure you are member of “cdrom” group.
JHi Wolfi,
Thanks - i tried the command and received the following :
getfacl /dev/sr*
getfacl: Removing leading ‘/’ from absolute path names
user::rw-
user:surfing:rw-
group::rw-
mask::rw-
other::—
I think i have access to the relevant group- account is surfing.
Can you confirm this ?. Thanks.
Regards,
Richard.
Hi Jobermayr,
i have v2.0.2 - using the standard repositories - so could not see the permissions in the programs icon in the K3B setup.
I can see the permissions in he Settings -> Setup System Permissions menu - the CD drive has permissions root.cdrom - so i think this is the issue - but cannot change - i assume i have to run as root to change, or modify a configuration file ?.
Thanks and regards,
Richard.
Hi Carlos,
Not sure if i have changed - do not think i have - how would i change - had a quick check but could not see. Thanks.
Regards,
Richard.
On 2014-08-31 22:16, shadders wrote:
> I can see the permissions in he Settings -> Setup System Permissions
> menu - the CD drive has permissions root.cdrom - so i think this is the
> issue - but cannot change - i assume i have to run as root to change, or
> modify a configuration file ?.
Those permissions are correct, I have the same. I do not need to burn
anything now, but it appears to work. At least, I do get media info.
Check this. Start up YaST, and on the “security and users section”,
activate the “Security center and hardening” module. On the window you
get, you should see a list on the left panel, and the last item should
be labelled “Miscellaneous settings”. Click that, and on the right hand
panel the top entry should be “File permissions: easy”.
It that is set to “secure”, then you have to fight against the system to
do things.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Right. The user has full access to the device file. So it should actually work.
And adding the user to the cdrom group would not change anything because of that.
Btw, I do have the same here as well, and K3b works absolutely fine without changing anything.
Check this. Start up YaST, and on the “security and users section”,
activate the “Security center and hardening” module. On the window you
get, you should see a list on the left panel, and the last item should
be labelled “Miscellaneous settings”. Click that, and on the right hand
panel the top entry should be “File permissions: easy”.
It that is set to “secure”, then you have to fight against the system to
do things.
That’s correct as well.
There do exist other privileges (“capabilities”) that are not reflected in file system permissions.
So the security settings might indeed interfere.
Setting the burning tools to suid root (as jobermayer suggested) should work around this as well, but is considered a security issue, by (open)SUSE’s security team at least.
You have to switch k3b to the Packman version though to have that “Permissions” tab available that allows you to do this. (again, jobermayr did write this)
Or just install k3b-codecs, that should do that switch automatically.
The main problem with this is that the change might get lost when you install updates.
Another thing that might help is to install the original cdrecord from the multimedia:apps repo. The default cdrkit is just an outdated fork.
As written above (and by jobermayr), this is only available in the Packman version of k3b.
I can see the permissions in he Settings -> Setup System Permissions menu - the CD drive has permissions root.cdrom - so i think this is the issue - but cannot change - i assume i have to run as root to change, or modify a configuration file ?.
No.
As also written already, the device file does have the correct permissions. And this cannot be changed easily because device files are created dynamically on boot (by udev).
So that part of K3b’s settings doesn’t actually work on openSUSE, at least the changes get lost when you reboot.
You could create an udev rule, or run “chmod”/“chown” on every boot to change those permissions/ownership, but again this is not necessary. Your user does have rw permissions, the same as root.
And if that wasn’t the case, adding your user to the group “cdrom” would give you the necessary permissions.
Hi All,
Apologies for not replying sooner - will check out this suggestions.
Regards,
Richard.
On 2014-09-01 07:46, wolfi323 wrote:
>
> robin_listas;2662245 Wrote:
>> Those permissions are correct, I have the same. I do not need to burn
>> anything now, but it appears to work. At least, I do get media info.
> Right. The user has full access to the device file. So it should
> actually work.
> And adding the user to the cdrom group would not change anything because
> of that.
>
> Btw, I do have the same here as well, and K3b works absolutely fine
> without changing anything.
Ah, the trick is this - I forgot:
Telcontar:~ # getfacl /dev/sr0
getfacl: Removing leading '/' from absolute path names
# file: dev/sr0
# owner: root
# group: cdrom
user::rw-
user:cer:rw- <----
group::rw-
mask::rw-
other::---
Telcontar:~ #
That’s why my user (cer) has write access to the DVD. The ACL gets
automatically set on login to the user sitting in front of the computer
I don’t know exactly what mechanism does this on 13.1. I think it was
policykit and pam, and it will change to systemd, or has already
changed, or it is in midway.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Yes, systemd-logind manages ACLs now. AFAIU, the groups of device ‘classes’ managed this way are determined by udev rules in ‘/usr/lib/udev/rules.d/70-uaccess.rules’. (Hence 'TAG+=“uaccess” is applied accordingly.) This means that administrators can add or remove devices as they sit fit with custom rules if desired.
I have been experiencing the same issue regarding k3b recently. I have followed all available advice I could find on the web, but without success. I could burn DVDs as root user, but since I never burned disks as root user I kept looking for a solution.
This is how I solved my problem. I cannot explain it, and it may seem random, but…
I run k3b as regular user, hit the Burn button, clicked on the Misc. tab. and I found that the Multisession mode was set to auto. I changed it to No Multisession, and Voilà! k3b could now recognise the blank DVD-R and I could burn my project.
Hope this helps.
Hi shelleyfrank,
Yes - i found this out this week - after having to burn a disk- do not need to be a root user either - change from finalise session (this seems to be my default) to no multi session - and the DVD/CD can be burnt.
Thanks for the reply.
Regards,
Shadders.