I just tried burning a image to a dvd
The process loads in k3b and just never gets beyond the starting process of preparing the burn
A new phenomenon
k3b etc from Packman
This is a problem with the Packman port of K3B to Plasma5. To burn an ISO you need to replace the Packman version of K3B with the Opensuse Tumbleweed version (obviously losing the codecs package),
Yes it does
I get a warning during setting up a process that the DVD drive is already in use by other applications (it lists a stack of kde backend stuff), recommending quitting these, blah blah… which obviously you can’t. I just select ‘Continue’ to ignore it and it does it’s job.
I wasn’t referring to that warning message - as you say it is just a case of selecting the ‘continue’ option.
There was a recent posting about K3B (from Packman) being unable to burn an ISO. The problem being that it just hung. The Opensuse version (included with Tumbleweed) will burn an ISO. Myself I just use an earlier version of K3B from Packman before they made the changes.
Has the iso image burning problem been resolved?
I’ll not be trying again for a week or so
But I will reply back when I do
No still not working.
Quite funny LEAP works, last time I checked, would expect to be the same version. So maybe
it has nothing to do with k3b as such but more the dependencies.
Bo
What backend used?
How to see?
Bo
Maybe not an issue any more but you do need to be member of cdrom group. Any how look in settings
No luck here still
hi there,
this issue is still happening. 
but i have a workaround for this issue:
i downloaded the 3 k3b packages (k3b,lang,codecs) from packman, but the version made for Leap 42.1 from:
http://packman.inode.at/suse/openSUSE_Leap_42.1/Essentials
where k3b has version 2.0.80+git20160102.1831 instead of the 2.9.90+git20160111.2358-11.3 for tumbleweed.
and this version does not have this bug (it has something to do with qt and an “invalid url” error) but works also on tumbleweed (at least it started and found the iso image, and was able to calculate the md5sum, while the version 2.9.90 failed here).
please try.
Makes sense! Thanks for investigating, maybe you should write about the problem on the packman mailinglist. Could be nice to do a diff of the two sources to locate the actual error.
Bo
It has been reported already:
http://lists.links2linux.de/pipermail/packman/2016-May/014406.html
Though another reminder might still be a good idea anyway.
And/or maybe even better, file a bug report at http://bugs.kde.org/.
Packman only packages the latest available upstream version as-is.
Though the Packman packager is one of the main developers of k3b currently AFAIK.
Could be nice to do a diff of the two sources to locate the actual error.
Probably not that easy.
2.9.90 is the KDE Frameworks5 port while 2.0.80 is a development snapshot of the KDE4 version, there are likely a lot of other changes.
Wouldn’t it makes sense for the Packman manager to downgrade the package until the problems is resolved?
It is after all a git snapshot it is based on now. 
Maybe somebody who uses Tumbleweed should write on the Packman list (I am on LEAP so I wouldn’t even be able to test,
since the version here runs fine)
Bo