Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: Santa on 2013/07/07, 21:54:04
-
Hello,
KDE SC 4.10.5 core packages are now available in kdenext/unstable, to use it,
make sure you have this line in any of your sources.list files:
deb http://packages.siduction.org/kdenext unstable main
The kdepim 4.10 is mostly untested (however the upgrades are suposed to work)
and it's available here:
deb http://packages.siduction.org/kdenext kdepim-ng main
Cheers.
-
Hello santa,
no problems with kde 4.10.5 on amd64.
A smooth dist-upgrade and overall good performance.
Thanks for all the work you are doing for siduction.
musca
-
du went well - Gwenview has problems with the kipi-plugins. Batch-resizing pics is freezing kde completly!
-
Thanks Santa. Upgrade went smoothly and no problems in operation so far.
-
Thanks Santa. Upgraded yesterday, everything (that I need) is working well.
-
Yep, all good here too, thanks
-
I've have a new error warning coming up after the update to 4.10.5, which, didn't happen in 4.10.4. This is on a Firestarter installation.
Error reads: Nepomuk Semantic Desktop needs the Virtuoso RDF server to store its data. Installing the Virtuoso Soprano plugin is mandatory for using Nepomuk.
I have viruoso-minimal installed, along with virtuoso-opensource-6.1-bin and virtuoso-opensource-6.1-common. Am I missing something? Should I have virtuoso server installed, or is there a config somewhere that I'm missing?
-
I've have a new error warning coming up after the update to 4.10.5, which, didn't happen in 4.10.4. This is on a Firestarter installation.
Error reads: Nepomuk Semantic Desktop needs the Virtuoso RDF server to store its data. Installing the Virtuoso Soprano plugin is mandatory for using Nepomuk.
I have viruoso-minimal installed, along with virtuoso-opensource-6.1-bin and virtuoso-opensource-6.1-common. Am I missing something? Should I have virtuoso server installed, or is there a config somewhere that I'm missing?
Perhaps a newer version of Virtuoso needed? There is 6.1.6 in experimental while sid has 6.1.4
-
Thanks DeepDayze. I'll keep an eye on that. But the fact that I seem to be the only one reporting the error, makes me think it might be a configuration problem. It's still a fairly new Firestarter install, I just have to see if anything I installed could be interfering. I already checked services and some configs, I just need the time to look a little deeper.
-
Thanks DeepDayze. I'll keep an eye on that. But the fact that I seem to be the only one reporting the error, makes me think it might be a configuration problem. It's still a fairly new Firestarter install, I just have to see if anything I installed could be interfering. I already checked services and some configs, I just need the time to look a little deeper.
What if you try stopping then restarting virtuoso in a terminal to see what error messages get displayed? That can give clues as to what the problem is
-
No luck. It seems like nepomuk and virtuoso aren't running, even though I can see in the config that all parts should be autostarted. Oh well, won't have time to play with it again till Thursday. It's funny, I can't find any errors in the log files. It's just so weird.
-
No luck, for me too.
I only got the error message, that the installation of nepomuk is not complete.
First i checked if virtuoso is running and it is running.
/etc/init.d/virtuoso-opensource-6.1 status
[ ok ] Checking status of Virtuoso OpenSource Edition 6.1: virtuoso-opensource-6.1 running.
What is installed
ii libnepomuk4 4:4.10.5-0r0 amd64
ii libnepomukcore4 4:4.10.5-90r0 amd64
ii libnepomukquery4a 4:4.10.5-0r0 amd64
ii libnepomukutils4 4:4.10.5-0r0 amd64
ii libnepomukwidgets4 4:4.10.5-0r0 amd64
ii libsmokenepomuk3 4:4.8.4-1+b1 amd64
ii nepomuk-core-data 4:4.10.5-90r0 all
ii nepomuk-core-runtime 4:4.10.5-90r0 amd64
ii virtuoso-minimal 6.1.6+dfsg1-3~pre1 all
ii virtuoso-opensource 6.1.6+dfsg1-3~pre1 all
ii virtuoso-opensource-6.1 6.1.6+dfsg1-3~pre1 amd64
ii virtuoso-opensource-6.1-bin 6.1.6+dfsg1-3~pre1 amd64
ii virtuoso-opensource-6.1-common 6.1.6+dfsg1-3~pre1 amd64
ii virtuoso-vad-rdfmappers 6.1.6+dfsg1-3~pre1 all
Is something missing?
System: Host: hhl.atelier.net Kernel: 3.10-0.towo-siduction-amd64 x86_64 (64 bit)
Desktop: KDE 4.10.5 Distro: siduction gefrickel
hendrikL
edit: I made a Test with a new user, there i get the same error message like GoinEasy9
-
@GoinEasy9, @hendrikL,
yesterday after updating the same problem with incomplete nepomuk packages occurred.
Only after upgrading the two packages$ dpkg -l *soprano* | grep ^ii
ii libsoprano4 2.9.2+dfsg.1-3 amd64 libraries for the Soprano RDF framework
ii soprano-daemon 2.9.2+dfsg.1-3 amd64 daemon for the Soprano RDF framework to experimental all went well.
Good luck
Tom
-
A fix for this is being built. Please don't mix kdenext with random packages from experimental, it's just asking for problems.
-
hi,
A fix for this is being built. Please don't mix kdenext with random packages from experimental, it's just asking for problems.
ACK
Please do an apt-get update && apt-get dist-upgrade -d switch to init 3 and make a apt-get dist-upgrade.
Fixed packages are pulled and working fine for me. thx santa for your work.
greetings hendrikL
-
Ah, so I wasn't the only one. Thank you all for the response.
Thank You Santa, for recognizing and working on a fix.
-
Ah, so I wasn't the only one. Thank you all for the response.
Thank You Santa, for recognizing and working on a fix.
Indeed you weren't the only one, but went under the radar because the problem appeared after an (apparently harmless) virtuoso upgrade, not in the initial kde 4.10.5 upgrade; in fact I realized because of your post. Thanks!
More news - KDE SC 4.10.5 is now being uploaded to sid by Debian. I recommend you very much to use (or keep using) kdenext to avoid breakages.
-
KDE SC 4.10.5 installed and working fine here...thanks Santa for the fix and the update.
After KDE 4.10.5 packages are fully uploaded to unstable in the coming days, should we then disable kdenext?
-
Confirmed. After dist-upgrade no more errors. Thanks again, Santa.
-
Only thing I discovered is Digikam camera import does not work. Camera is a Kodak Easyshare c1505 which is detected properly but the import option does nothing.
-
After KDE 4.10.5 packages are fully uploaded to unstable in the coming days, should we then disable kdenext?
No, you shouldn't, there are still few issues in the debian packages so a few packages have a higher version than the debian version, also there is some extra stuff like kio-mtp and kscreen, not packaged in debian. Also kdepim is being kept at 4.4.11 and is just optional to install the newer 4.10.x using kdenext/kdepim-ng. Once the newer kdepim is tested enough and we get our isos ready for that, we will move on to the new version.
And in any case in one month or so the kde 4.11.0 is going to be released, so perhaps would be available in kdenext.
-
Alright thanks Santa
-
Last time I looked, I couldn't find kio-mtp. Thanks for including it. Installing and using it gets me an option to open it up in Dolphin, but, like Fedora and openSUSE I get the "Your phone needs to be rooted" error. But, unlike the others, I can't get Digikam to download the pictures in siduction. It may be that they're on Digikam 3.2 and we're still using 3.1, or, more likely, I'm still missing something in the setup. I tried mtp and ptp with Digikam.
kio-mtp hasn't been touched since March. I guess the recent Google changes haven't been dealt with yet.
Or it might mean that libmtp needs some love.