kcmshell4
 

I'm having fun setting up the one kde program I tolerate on my boxes, k3b. k3bsetup (a script) has this lineI'm embarrassed for kcmshell4 (or a workaround for it) and it seems to be trying to drag me into installing most of kde base (for libs and stuff). No Sir!

Is there a workaround, or do I ditch k3b and go looking for another cd burning program?

I think that kcmshell4 command is actually loading /usr/lib64/kde4/kcm_k3bsetup.so. I might be wrong on that, though. But if that's the case, then yes, you'll need all the libraries and stuff.

Thanks for the reply. I feared as much, hence the question. Goodbye k3b.

:-D.
Hello XFBURN - add-on to xfce and quite enough for my needs, thank you

I am not sure I understand your problem.

From what I know, k3bsetup is not used nowadays. Nowadays kde 4.x/solid do not need this to detect your hardware because hal has been deprecated in favour of plain udev. Hence my question: are you using an up to date version of k3b? In any case, if you are happy with xfburn then it's ok, but I am just curious.

k3bsetup changes permissions on the devices and applications that k3b uses, AFAIK it's not used to detect hardware.

I think business_kid wanted to install only the k3b package, but k3bsetup requires kcmshell4, part of kdebase-runtime, which in turn requires other KDE packages.

The concrete purpose of k3bsetup is not too relevant. My point is that's perfectly possible to live without it (Gentoo does so) and kcmshell is not a dependency of k3b. I am still not clear if the problem is that the involved distro pushes these deps or if it is the OP who thinks that k3bsetup is really a must-have. If your distro is telling you otherwise, then it's either outdated of the dep tree is buggy.

I assure you k3b is fully functional with only these. As you see, kcmshell is not in the list. Strictly speaking you could even run it without the icons and without kcddb (I did, not too nice though). Probably also without knotify, but I didn't try that. You definitely need kdelibs, that's evident.

Yes, I agree with you on that. As I said, k3bsetup only changes permissions on certain files and devices so k3b operates properly, and that can be done manually if necessary.

I think kcmshell4 is a dependency of k3bsetup, not k3b per se. The k3bsetup dialog is a kcmshell4 module: /usr/lib(64)/kde4/kcm_k3bsetup.so. So in order to run k3bsetup, kcmshell4 is needed. I don't know of another way of running k3bsetup without kcmshell4, but perhaps there is.

And, as you point out, k3b is fully functional without it.

I don't think there's another way of running k3bsetup. What the Gentoo k3b ebuild does is to print this message after installing k3b, and maybe it's worth checking:

Your distro might use a different group or whatever, you can check that usually by doing "ls -l /dev/cdrw", or whatever your recording device is. Once you know the group that owns the device node all you have to do is to add yourself to that group (usermod --append -G group username) and restart all your login sessions (or just reboot).

Well, the original poster (me) definitely doesn't have kcmshell4.

Just for the laugh, I tried k3b from a terminal. Contrary to previous experience, it staggered into life with a page full of errors from things beginning with 'k', 'Q' and 'G'. It can't find anything, parse anything,and returns a string of errors from QPainter. Strewth!

I forget what I did to get it this way. I think I have exploded a package, copied out a single library, and deleted that package again. It still crapped out (after I did this) last time. Now it works. Thanks for all the 'kGems' of wisdom.

Here's one you guys might have an idea on. I decided to use k3b - to clone a freebie video dvd.

It made a 6.7Gig .iso and we fell over predictably :-O? I'm not expecting copy protection.

k3b offers info when it fails. Can you paste it here?

Does it successfully create the ISO and then fail? Does it start burning the image and fails in the middle?

Not really.

k3b makes the iso (in the 'copy medium' menu), and sits up and has a window saying "Insert a DVD or Blue-Ray disk". This conveniently ignores the fact that it's a dvd writer, not a blue ray. I get the choice of Load, Eject, or Cancel. Load does nothing and says nothing. Eject Ejects. Cancel deletes the iso and goes away. Here's the terminal outputLoop mounting the iso shows this:
All those 1.0 Gigs are kind of suspicious, but it otherwise looks reasonable. I have worked on cd manufacturing machines in a former life and know how to judge the size visually, and this one if FULL FULL. Every cylinder seems used. It also has subtitles in 8 languages.

EDIT: Startup errors may be relevant, and here they are:[QUOTE]k3b
QGtkStyle was unable to detect the current GTK+ theme.
k3b(2151)/kdeui (KIconLoader): Error: standard icon theme "oxygen" not found!

k3b(2151)/kdeui (KIconLoader): Unable to access index when trying to discard cache
kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kded4.so
QGtkStyle was unable to detect the current GTK+ theme.
kded(2159)/kdeui (KIconLoader): Error: standard icon theme "oxygen" not found!

QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kbuildsycoca4.so
kbuildsycoca4 running...
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kconf_update.so
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QMetaObject::invokeMethod: No such method K3b::Application::loadCommandLineOptionsForNewInstance()
bash-4.1$ k3b(2151)/kdeui (kdelibs): Attempt to use QAction "view_projects" with KXMLGUIFactory!
k3b(2151)/kdeui (kdelibs): Attempt to use QAction "view_dir_tree" with KXMLGUIFactory!
k3b(2151)/kdeui (kdelibs): Attempt to use QAction "view_contents" with KXMLGUIFactory!
k3b(2151)/kdeui (kdelibs): Attempt to use QAction "location_bar" with KXMLGUIFactory!
kdeinit4: preparing to launch /usr/lib/kde4/kio_file.so
kdeinit4: preparing to launch /usr/lib/kde4/kio_file.so
kdeinit4: preparing to launch /usr/lib/kde4/kio_file.so
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
k3b(2151)/kdecore (services) KMimeTypeFactory::parseMagic: Now parsing "/usr/share/mime/magic"
k3b(2151)/kdecore (services) KMimeTypeFactory::parseMagic: Now parsing "/home/dec/.local/share/mime/magic"[QUOTE]

So, from what I understand, it just sits there waiting for a disk forever, is that correct?

Sorry if this is too obvious, but I prefer to ask for obvious things before ignoring them to discover a year later that it was a silly thing: did you try putting the disk in your drive and closing it manually? If the drive is able to work with double layer DVDs (I assume you already checked that) then k3b should detect that you just inserted a blank disk, and start burning it.

Another thing you should check is that the udev service is running. Or, if you use a pre-2.x release of k3b, then make sure that hal is running as well.

Another thing you could try is this: k3b supports several backends when it comes to burning disks. Most notably, cdrkit(wodim) vs. cdrtools. I don't know what the status for these is in your distro, but you will have better or worse luck with one or the other depending on the hardware you use, program versions, etc. So you might want to check that, if the obvious thing fails.

In any case, double check the releases of cdrtools/cdrkit and dvd+rw-tools, and google a bit around for minimal versions of these needed for dual layer DVD support.

Oh, the terminal output you posted seems ok to me.

In Slackware 13.37, the files kcmshell4, knotify4.desktop and org.kde.knotify.service are provided by the package kdebase-runtime.

The oxygen theme is in package oxygen-icons.

All the files above are provided by the kdelibs package.

@business_kid, it seems to me you removed from your system several core KDE packages, and without them k3b simply won't work properly.

But maybe that's what you want, right? ;)

Yes. I have no problem with you asking the obvious - that's how people get to the bottom of things.

Yes, all this is good. If I close the drive, it stays there. If I don't I have Verbatim Lightscribe DVDs and they are 70 minutes (=4.7 G), with a pretty surface for lightscribing on the other side. and I'm not really surprised it isn't burning them with a 6.7G iso. What I am surprised at it that dd from a readable disk returns 6.7G! Is this some sort of a crazy error, is something being read twice?

No reason to suspect udev, which is working & running. I have k3b-2.0.0, cdrdao-1.2.3, cdrtools-3.01a02, & dvd+rw-7.1. The caveat is that there has been an upgrade, and if slackware dropped one of those packages or moved it, I might be looking at an old version. I just feel like someone who has poured a litre out of a pint bottle, and can't get it back in :-/.