You are not logged in.
Pages: 1
I'm getting the follwoing error when trying to run k3b:
k3b: error while loading shared libraries: libkcmutils.so.4: cannot open shared object file: No such file or directory
It's true that this file doesn't exist, however kdelibs is installed & up to date.
Any ideas?
Last edited by clearloon (2010-08-24 12:05:31)
Offline
I am having a similar problem . When I updated K3b today from 2.0.0 to 2.0.1-1 . K3b will not run . I have tryed to uninstall and reinstall still wont work . I get no error . I am running 4.4.5 . That is all the info I have .
Offline
I can conform that this came after latest update of K3B to 2.0.1-1
Should i submit bug?
"The flesh knows it suffers even when the mind has forgotten."
Offline
k3b starts up fine for me, and I don't seem to have that file anywhere either. What version of k3b do you have? Mine is 2.0.0-2
Offline
k3b starts up fine for me, and I don't seem to have that file anywhere either. What version of k3b do you have? Mine is 2.0.0-2
You are running the older one that still works. The new K3b is 2.0.1-1 and it came out today and does not work .
Offline
I can confirm this bug. Just installed k3b 2.0.1-1 today and it doesn't start up at all. I'm running KDE 4.4.5.
uname -a ==>Linux Galicja 2.6.35-ARCHMOD #1 PREEMPT Mon Aug 2 16:14:56 CEST 2010 x86_64 Genuine Intel(R) CPU 575 @ 2.00GHz GenuineIntel GNU/Linux
Offline
It happens the same on my machine too
Offline
Offline
i don't get it why nobody reported on the bugtracker. i've seen it in the forums and in the ml earlier today but no bug report.
that is clearly a packaging issue as k3b was built in testing and that soname is a part of kdelibs 4.5
Give what you have. To someone, it may be better than you dare to think.
Offline
Bug reports only get filed when people file them, not when you complain about people not filing them...
Offline
Anyone tried to build k3b 2.0.1 using kdelibs 4.4.5 via ABS? Unfortunately, I cannot sync ABS from my current location. :-/
Since 4.5.0 is supposed going to enter [extra] soon, I can see why they built it using kdelibs 4.5. I guess KDEMod users do not have to worry about this "bug"
Last edited by ssri (2010-08-20 04:58:12)
Offline
I read dev mailing list about KDE 4.5 in testing. KDE 4.5 will hit extra soon. There is no major bugs for now. Best thing for k3b is to downgrade.
"The flesh knows it suffers even when the mind has forgotten."
Offline
Bug reports only get filed when people file them, not when you complain about people not filing them...
This is poor packaging, not a bug.
Offline
This is poor packaging, not a bug.
Quite right, I just built a package of version 2.0.1 from ABS with kdelibs 4.4.5 and it starts up and burns discs just fine. Here's the x86_64 package if anyone wants it: http://sharebee.com/0ba933b4.
Last edited by ssri (2010-08-20 05:24:37)
Offline
SSRI, when you install this.. will it affect a pacman -Syyu? or anything on the system itself (before 4.5 becomes final i mean) in other words will there be anything going wrong from installing this this way instead of with a normal update via pacman?
"Sometimes you comfort the afflicted, other times you AFFLICT the COMFORTABLE"
Offline
SSRI, when you install this.. will it affect a pacman -Syyu? or anything on the system itself (before 4.5 becomes final i mean) in other words will there be anything going wrong from installing this this way instead of with a normal update via pacman?
It shouldn't affect pacman -Syyu unless the maintainer releases 2.0.1-2 or the k3b team releases 2.0.2 and it gets packaged for 4.5.0 again. So long as the version remains at 2.0.1-1 and you are using kde 4.4.5, then you should be fine. Obviously, when kde 4.5.0 hits extra and you choose to upgrade, you should also reinstall k3b 2.0.1-1 that is built using kdelibs 4.5.0, the one currently on extra. I guess one should stick with what they have when in doubt. As for k3b 2.0.1, it is nice to see that they finally implemented drag-and-drop from dolphin.
Last edited by ssri (2010-08-20 09:33:14)
Offline
Just to let everyone having this problem, that the problem has been fixed in k3b-2.0.1-2. So, update to this version to sort it out.
Regards! ;-)
Offline
Pages: 1