Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: Santa on 2015/10/01, 17:35:44
-
Hi,
after the debian's switch to GCC 5 kdenext was updated today providing new KDE packages. So right now there is:
KDE Frameworks 5.14
Plasma 5.4.1
KDE Applications 15.08.1 (except for kdepim which is 4.14.x, previous one was 4.4.x)
So, assuming you have kdenext in your sources.list:
What is suposed to work out of the box:
1) dist-upgrading with apt (not aptitude) from a siduction KDE with kdenext last upgraded before July 31 2015 (date of the debian/ubuntu switch to GCC 5)
2) dist-upgrading with apt (not aptitude) a fresh new indiansummer installation following the instructions https://community.kde.org/Plasma/InstallingNext#siduction (https://community.kde.org/Plasma/InstallingNext#siduction)
What is, probably, NOT going to work out of the box:
3) dist-upgrading now from a siduction KDE last upgraded after July 31 (date of the debian/ubuntu switch to GCC 5)
What is NOT going to work:
4) dist-upgrading with aptitude from a siduction KDE last upgraded after July 31 (date of the debian/ubuntu switch to GCC 5). The reason for this is that after the GCC 5 transition many package libraries had to be renamed from libfooX to libfooXv5 where libfooXv5 conflicts with libfooXv5 because they share the same files (example https://packages.qa.debian.org/x/xapian-core/news/20150802T172039Z.html (https://packages.qa.debian.org/x/xapian-core/news/20150802T172039Z.html)). This is a very undesirable situation because it confuses package managers (they have problems to figure out that libfooXv5 is a replacement for libfooX). It was feasible to tweak some packages to make it work properly with apt, but not feasible for aptitude.
So if you find issues or have doubts please post:
- Here if you are in case 1) 2) and 3) for KDE issues not related to kdepim
- In this other thread if you are in case 1) 2) and 3) and you have issues specific of kdepim (http://forum.siduction.org/index.php?topic=5800.0 (http://forum.siduction.org/index.php?topic=5800.0))
- For the case 4) just use apt this time. You can continue to use aptitude if you like it more after dist-upgrading today. However remember that apt is the recommended package manager for siduction.
If you are in other case such as not having kdenext in your sources.list please post somewhere else. As a friendly reminder, we have subforums for software support:
http://forum.siduction.org/index.php?board=61.0 (http://forum.siduction.org/index.php?board=61.0)
and experiments (such as doing things not actually supported):
http://forum.siduction.org/index.php?board=57.0 (http://forum.siduction.org/index.php?board=57.0)
-
I am in 4 case and I can see that with the update of some packages like: libakonadi-kde4, libsyndication4 or soprano-daemon, libstreamanalyzer0v5, apt ask to remove many package of kde.
-
Hi Santa,
I don`t know what happens in the last two day`s, but today here many packages would be removed - with and without kdenext. My system is siduction "Riders on the storm" kde-full upgraded to plasma 5 in june/juli - last apt-get dist-upgrade was on 30.07.2015 - works without problems
apt-get dist-upgrade -s :
29.09.15 with kdenext
1348 aktualisiert, 164 neu installiert, 139 zu entfernen und 19 nicht aktualisiert
01.10.15 with kdenext
898 aktualisiert, 48 neu installiert, 684 zu entfernen und 162 nicht aktualisiert
01.10.15 without kdenext
904 aktualisiert, 43 neu installiert, 659 zu entfernen und 161 nicht aktualisiert
thx for your work !
edit: apt-cache policy kdepim
kdepim:
Installiert: 4:4.14.5+really4.4.11.1+l10n-0r2.1
Installationskandidat: 4:4.14.10-2
Versionstabelle:
4:4.14.10-2 0
500 http://http.debian.net/debian/ unstable/main amd64 Packages
-
All seemed to go well during the dist-upgrade. Except for a grave bug report for kwin and I had to do one -f install. I stopped sddm and shifted to multi-user.target to do the upgrade.
So far I haven't unearthed any problem while using KDE since the upgrade. I haven't shutdown and rebooted yet; so fingers crossed!
I'm in the 3) camp due to a reinstallation, dist-upgrade a few days ago. The installation was due in large part because something in a systemd upgrade left my beloved very, very old installation in too much of a mess.
Edit: Forget to offer my thanks to Santa.
-
Hi,
did the d-u right now, I was in 3), dist-upgraded 31. of Juli the last time, kde-next enabled.
Half of my system was gone after d-u, had to manually purge a few libs and apps and then reinstall dolphin, kamil and kde-standard.
After that my system is working again, all settings kept, just lost my emails :(
To say it clear: This was my own fault, I d-u-ed two days after Santas warning.
Thanks for your work Santa, my system is in a far better condition as the one I updated without the kde-next repo.
here is my history.log and dpkg.log for those who have a similar situation. hth.
http://paste.siduction.org/20151001184607
http://paste.siduction.org/20151001185356
Greets
ayla
-
This is the way things look here today. Thanks to everyone involved.
# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
cpp-5 gcc-5-base libatomic1 libcilkrts5 libgcc1 libgfortran3 libgomp1 libitm1 liblsan0 libquadmath0 libstdc++6
libtsan0 libubsan0
0 upgraded, 0 newly installed, 0 to remove and 13 not upgraded.
LibreOffice is at 5.0.2.2. The only thing I have not been able to get back (that I have noticed) is Yakuake due to a couple of dependencies, and that is hardly an emergency.
This was a fresh install of Indian Summer in mid-July with kde-next enabled.
-
As always Thanks a llot Santa.
You are doing a great job!
I am still waiting... Last DU 20th of July.
Maybe I should wait a little longer... Lets see :-D
-
Hi,
did a du a few minutes ago, on a system in state 1)+a few packages installed in the meantime.
All in all du went very smooth, but a few packages had to go (e.g. plasma-widgets-workspace, kile).
Some packages
libksgrd4 libkworkspace4abi2 libplasma-geolocation-interface4 libplasmaclock4abi4 libplasmagenericshell4 libprocesscore4abi1 libprocessui4a libtaskmanager4abi4 libweather-ion6 plasma-dataengines-workspace
are newer in sid than in kde-next, so i managed to get them back by "downgrading" to kde-next.
But kile seems to be gone, for now, because
libnepomuk4 libnepomukutils4 libnepomukquery4a
are not installable, as they depend on a non-existant version (=4:4.14.3-siduction1) of
libkdecore5 libkdeui5
(4:4.14.12-siduction1.2.1 available)
Everything else seems to be working, i guess.
Thanks for your hard work, Santa!
-
Hello,
nice to have a repo with current kf5 and plasma5 stuff. I'll try following:
1. Installing last nox iso / or xorg iso without further de stuff
2. adding kdenext repo
3. Installing kde-standard and additional stuff.
Prefering to kdepim stuff: I'm lucky with very fast and also full featured claws mail but okay, I'll give kdepim another try for comparing with claws mail.
I'll give feedback how kf5 works.
Kind regards,
Holger
-
kile came back today. Thanks :)
-
@Mte90, @jure: you mentioned several packages to be removed. That is kind of expected, because
after the GCC 5 transition many package libraries had to be renamed from libfooX to libfooXv5
Please take a closer look on apt output if the ones to be removed have canditates in the newly installed section with similar names +v5. (And additionally, perhaps some packages might be completely obsolete now).
For me all went well with a system mostly being case 1) with a bit of 3) : a kdenext already on KF5/Plasma5, stopped DU around 29th july, but tried updating some stuff with help of aptitude's solver which worked somehow but left the system in a state I was not really sure about. I expected a real mess today, but there was only one error around kactivities-stuff, got solved by 'dpkg --configure -a' followed by 'apt-get install -f'. System up-to-date now. So in case what Santa called "probably not going to work out of the box" I was lucky ;)
-
Hi, first of all:
Indeed there was a small issue preventing yakuake and kile from being installed, this was fixed yesterday in the night by a kdelibs update. Thanks for noticing.
Regarding people in the situation 3) I plan to work on some things to make the dist-upgrade work a bit more out of the box, so if you are in this situation you might want to hold the dist-upgrade a few days to get something smoother.
All in all du went very smooth, but a few packages had to go (e.g. plasma-widgets-workspace, kile).
Some packages
libksgrd4 libkworkspace4abi2 libplasma-geolocation-interface4 libplasmaclock4abi4 libplasmagenericshell4 libprocesscore4abi1 libprocessui4a libtaskmanager4abi4 libweather-ion6 plasma-dataengines-workspace
are newer in sid than in kde-next, so i managed to get them back by "downgrading" to kde-next.
In general, when the package manager wants to remove lib* packages it's ok because:
a) the programs you have installed don't use it anymore
b) the library is replaced by a newer version (e.g. apt wants to remove libwhatever4 while at the same time libwhatever5 is installed)
Regarding the libraries you have mentioned, they fit in a), they are from the previous version of plasma from KDE SC 4 (obsolete).
At this point the only doubt would be plasma-dataengines-workspace, but this package is from KDE SC 4 too.
So, except for kile, which is fixed now, you can safely remove all those lib* packages and plasma-dataengines-workspace, you won't lose anything in your plasma 5 desktop.
Prefering to kdepim stuff: I'm lucky with very fast and also full featured claws mail but okay, I'll give kdepim another try for comparing with claws mail.
Regarding kdepim keep in mind than the one right now in debian sid and siduction is still based on kdelibs 4 and at some point (probably in the next few months) it would be replaced by the newer one based on KDE Frameworks. Thanks as allways for your valuable feedback.
@Mte90, @jure: you mentioned several packages to be removed. That is kind of expected, because after the GCC 5 transition many package libraries had to be renamed from libfooX to libfooXv5
Please take a closer look on apt output if the ones to be removed have canditates in the newly installed section with similar names +v5. (And additionally, perhaps some packages might be completely obsolete now).
Regarding this, Mte90's case seems like something expected while jure's seems to have been experiencing a temporary problem. Could you please both paste the output of apt-get dist-upgrade? (so we can check if you are hitting a problem or not)
-
apt-get install libplasma3=4:4.14.12-siduction1.3.1 libkio5=4:4.14.12-siduction1.3.1 libstreamanalyzer0v5 libstreams0v5[code]
With that command and remove of plasma-dataengines-workspace now the upgrade have no problem (also with the remove) and i can install other 70 packages but i have other many packages.
[code]
root@siduction:/home/mte90# apt-get dist-upgrade
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze
Lettura informazioni sullo stato... Fatto
Calcolo dell'aggiornamento... Fatto
I seguenti pacchetti saranno RIMOSSI:
digikam-private-libs gimp kscreensaver libakonadi-dev libboost-atomic1.55-dev libboost-chrono1.55-dev libboost-context1.55-dev libboost-coroutine1.55-dev libboost-dev
libboost-filesystem1.55-dev libboost-serialization1.55-dev libboost-system1.55-dev libboost1.55-dev libgegl-0.2-0 libgimp2.0 libgstreamer0.10-dev libhighgui2.3
libicu-dev libkexiv2-11 libkgeomap2 libmagickcore5-extra libmarblewidget21 libopencv-calib3d2.3 libopencv-contrib2.3 libopencv-features2d2.3 libopencv-highgui2.3
libopencv-legacy2.3 libopencv-objdetect2.3 libopenexr6 libopenimageio1.2 libopenimageio1.3 libopenimageio1.4 libopenimageio1.5 libsmokebase3 libsmokeqtwebkit4-3
libxml2-dev libxslt1-dev plasma-scriptengine-ruby plasma-scriptengines ruby-kde4 ruby-plasma ruby-qt4-webkit sane xsane
I seguenti pacchetti NUOVI saranno installati:
libde265-0 libkexiv2-11v5 libkvkontakte1 libmediawiki1 libopencv-calib3d2.4v5 libopencv-contrib2.4v5 libopencv-features2d2.4v5 libopencv-gpu2.4v5 libopencv-highgui2.4v5
libopencv-legacy2.4v5 libopencv-objdetect2.4v5 libopencv-ocl2.4v5 libopencv-stitching2.4v5 libopencv-superres2.4v5 libopencv-ts2.4v5 libopencv-videostab2.4v5
libopenexr6v5 libsmokebase3v5
I seguenti pacchetti sono stati mantenuti alla versione attuale:
cpp-5 g++-5 gcc-5 gcc-5-base gcc-5-base:i386 libasan2 libatomic1 libcc1-0 libcilkrts5 libcrypto++-dev libgcc-5-dev libgcc1 libgcc1:i386 libgfortran3 libgomp1
libgomp1:i386 libitm1 liblsan0 libmpx0 libquadmath0 libstdc++-5-dev libstdc++6 libstdc++6:i386 libtsan0 libubsan0
I seguenti pacchetti saranno aggiornati:
digikam digikam-data frei0r-plugins gmic-zart gstreamer1.0-plugins-bad kde-runtime kdegraphics-thumbnailers kipi-plugins kipi-plugins-common libastro1
libgstreamer-plugins-bad1.0-0 libmagickcore-6.q16-2-extra libokularcore6 libopencv-calib3d2.4 libopencv-contrib2.4 libopencv-core2.4 libopencv-features2d2.4
libopencv-flann2.4 libopencv-gpu2.4 libopencv-highgui2.4 libopencv-imgproc2.4 libopencv-legacy2.4 libopencv-ml2.4 libopencv-objdetect2.4 libopencv-ocl2.4
libopencv-photo2.4 libopencv-stitching2.4 libopencv-superres2.4 libopencv-ts2.4 libopencv-video2.4 libopencv-videostab2.4 libopencv2.4-java libopencv2.4-jni
libopenexr-dev libqtruby4shared2 libsmokekdecore4-3 libsmokekdeui4-3 libsmokekfile3 libsmokekhtml3 libsmokekio3 libsmokeknewstuff2-3 libsmokeknewstuff3-3
libsmokekparts3 libsmokektexteditor3 libsmokekutils3 libsmokenepomuk3 libsmokeplasma3 libsmokeqtcore4-3 libsmokeqtdbus4-3 libsmokeqtgui4-3 libsmokeqtnetwork4-3
libsmokeqtopengl4-3 libsmokeqtsql4-3 libsmokeqtsvg4-3 libsmokeqtxml4-3 libsmokesolid3 okular plasma-scriptengine-javascript ruby-qt4
59 aggiornati, 18 installati, 44 da rimuovere e 25 non aggiornati.
È necessario scaricare 44,0 MB di archivi.
Dopo quest'operazione, verranno liberati 217 MB di spazio su disco.
-
Hi Mte90,
apt-get install libplasma3=4:4.14.12-siduction1.3.1 libkio5=4:4.14.12-siduction1.3.1 libstreamanalyzer0v5 libstreams0v5[code]
With that command and remove of plasma-dataengines-workspace now the upgrade have no problem (also with the remove) and i can install other 70 packages but i have other many packages.
[code]
root@siduction:/home/mte90# apt-get dist-upgrade
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze
Lettura informazioni sullo stato... Fatto
Calcolo dell'aggiornamento... Fatto
I seguenti pacchetti saranno RIMOSSI:
digikam-private-libs gimp kscreensaver libakonadi-dev libboost-atomic1.55-dev libboost-chrono1.55-dev libboost-context1.55-dev libboost-coroutine1.55-dev libboost-dev
libboost-filesystem1.55-dev libboost-serialization1.55-dev libboost-system1.55-dev libboost1.55-dev libgegl-0.2-0 libgimp2.0 libgstreamer0.10-dev libhighgui2.3
libicu-dev libkexiv2-11 libkgeomap2 libmagickcore5-extra libmarblewidget21 libopencv-calib3d2.3 libopencv-contrib2.3 libopencv-features2d2.3 libopencv-highgui2.3
libopencv-legacy2.3 libopencv-objdetect2.3 libopenexr6 libopenimageio1.2 libopenimageio1.3 libopenimageio1.4 libopenimageio1.5 libsmokebase3 libsmokeqtwebkit4-3
libxml2-dev libxslt1-dev plasma-scriptengine-ruby plasma-scriptengines ruby-kde4 ruby-plasma ruby-qt4-webkit sane xsane
I seguenti pacchetti NUOVI saranno installati:
libde265-0 libkexiv2-11v5 libkvkontakte1 libmediawiki1 libopencv-calib3d2.4v5 libopencv-contrib2.4v5 libopencv-features2d2.4v5 libopencv-gpu2.4v5 libopencv-highgui2.4v5
libopencv-legacy2.4v5 libopencv-objdetect2.4v5 libopencv-ocl2.4v5 libopencv-stitching2.4v5 libopencv-superres2.4v5 libopencv-ts2.4v5 libopencv-videostab2.4v5
libopenexr6v5 libsmokebase3v5
I seguenti pacchetti sono stati mantenuti alla versione attuale:
cpp-5 g++-5 gcc-5 gcc-5-base gcc-5-base:i386 libasan2 libatomic1 libcc1-0 libcilkrts5 libcrypto++-dev libgcc-5-dev libgcc1 libgcc1:i386 libgfortran3 libgomp1
libgomp1:i386 libitm1 liblsan0 libmpx0 libquadmath0 libstdc++-5-dev libstdc++6 libstdc++6:i386 libtsan0 libubsan0
I seguenti pacchetti saranno aggiornati:
digikam digikam-data frei0r-plugins gmic-zart gstreamer1.0-plugins-bad kde-runtime kdegraphics-thumbnailers kipi-plugins kipi-plugins-common libastro1
libgstreamer-plugins-bad1.0-0 libmagickcore-6.q16-2-extra libokularcore6 libopencv-calib3d2.4 libopencv-contrib2.4 libopencv-core2.4 libopencv-features2d2.4
libopencv-flann2.4 libopencv-gpu2.4 libopencv-highgui2.4 libopencv-imgproc2.4 libopencv-legacy2.4 libopencv-ml2.4 libopencv-objdetect2.4 libopencv-ocl2.4
libopencv-photo2.4 libopencv-stitching2.4 libopencv-superres2.4 libopencv-ts2.4 libopencv-video2.4 libopencv-videostab2.4 libopencv2.4-java libopencv2.4-jni
libopenexr-dev libqtruby4shared2 libsmokekdecore4-3 libsmokekdeui4-3 libsmokekfile3 libsmokekhtml3 libsmokekio3 libsmokeknewstuff2-3 libsmokeknewstuff3-3
libsmokekparts3 libsmokektexteditor3 libsmokekutils3 libsmokenepomuk3 libsmokeplasma3 libsmokeqtcore4-3 libsmokeqtdbus4-3 libsmokeqtgui4-3 libsmokeqtnetwork4-3
libsmokeqtopengl4-3 libsmokeqtsql4-3 libsmokeqtsvg4-3 libsmokeqtxml4-3 libsmokesolid3 okular plasma-scriptengine-javascript ruby-qt4
59 aggiornati, 18 installati, 44 da rimuovere e 25 non aggiornati.
È necessario scaricare 44,0 MB di archivi.
Dopo quest'operazione, verranno liberati 217 MB di spazio su disco.
So, for your case I'm seeing 2 problems (not related to kde and therefore "out of my jurisdiction"):
1. gimp being removed
2. libstdc++6 and others on hold
Probably this happens because you have libstdc++6 installed with multiarch both for amd64 and i386. When you have a library installed that way it's usually required to have the exact same version for both architectures (at least for ) so when a new version is uploaded to sid the dist-upgrade won't work properly until it's built for both architectures. The libstdc++6 package is built from the gcc-5 source package, and as you can see here:
https://buildd.debian.org/status/package.php?p=gcc-5&suite=unstable
the package is being built for i386 while I'm writing this post (the status will change with time obviously).
Also if you type "apt-cache policy libstdc++6:amd64" and "apt-cache policy libstdc++6:i386" I presume you will get different versions.
So, recommended way of proceeding: do "apt-get update" from time to time and when "apt-cache policy libstdc++6:amd64" and "apt-cache policy libstdc++6:i386" report the exact same version try to dist-upgrade again. Probably it will work fine, but if it doesn't feel free to post here again (even while this is not KDE specific problem).
Regards.
-
perfect thanks for the suggestions!
-
Hi
I attached the output of apt-get dist-upgrade from 14:30 UTC
2 days ago "164 new installed, 139 removed" and today "48 new installed, 677 removed"
-
Hi jure,
Hi
I attached the output of apt-get dist-upgrade from 14:30 UTC
2 days ago "164 new installed, 139 removed" and today "48 new installed, 677 removed"
So you have libtsc++6 installed both for amd64 and i386 too; my advice is the same I gave Mte90: do "apt-get update" from time to time and when "apt-cache policy libstdc++6:amd64" and "apt-cache policy libstdc++6:i386" report the exact same version try to dist-upgrade again. If you have further issues after that, please post again so we can find out if there are further problems beyond libstdc++6 not being built yet for i386.
-
I made a dist-upgrade and the most works fine but if I shut down I have a black screeen and nothing goes. So I must go to a tty and make there a shutdown. Do I miss a packet in kde?
-
in addition to Santa i would suggest to think about multiarch et al. Do you really need multiarch or i386 based programms in this installation - can the same or sufficient functionality be archived with a vm? if so, i would suggest a virtual machine with the needed programs - in my case it was only teamviewer what i need to support others - o.k. i use a win10 vm for that - skype would be another item - but i use a different machine for that right now or my cell phone directly :).
After these descisions i now have a i386-free main installation which is pure fun as i only has to watch out for the 'normal' transition things 8)
-
Oh, my. I mistakenly did the unsupported "apt-get upgrade" - I misread some of the last posts here mentioning "apt-get update" while on my smartphone, tried issuing that command and everything seemed OK, so I went with it. It occurred to me only after things were installing already that I remember reading something on this forum regarding "apt-get upgrade"... :-\
The reason I didn't simply go with dist-upgrade was that it wanted to remove a lot of stuff like plasma-desktop, kde-workspace, dolphin and a bunch of other kde stuff, along with apps like ardour, audacity, vlc, inkscape etc.
And I think I should be under case 1) as I didn't do a DU after July 29, but I did do a couple of selected manual upgrades like "apt-get install linux-image..." and also some system stuff like mesa libs, even of some kf5 stuff etc.
So I'm not sure if what I'm experiencing is due to any of what I did (wrong), as I explained above, but here are my experiences trying to DU this system.
After apt-get upgrade, there were still some, albeit less stuff that DU would remove, so I selectively did some installs that didn't seem to remove half of my system at once, only some libs that were replaced.
At the end, I got "stuck" with libtag: I couldn't install libtag1v5 without first manually removing libtag1c2a which took most of the KDE with it (at that point I went with it, because I couldn't start KDE anymore anyway), but I reinstalled most of it back with kde-standard, bringing back the rest manually.
One of the packages I had to reinstall manually was kscreen and that gave me problems until I figured out which package is causing it and removed it. With kscreen installed, I'd get a black screen after logging in (either on dock, connected with an external monitor or off the dock and an external monitor). The only thing I'd see after "systemctl start sddm.service" is the KDE splash screen with the progress bar and after that completed, it all went dark.
Without kscreen I can see my desktop, but now I rely upon xrandr to configure my display and at first I thought there was a bug in KDE causing the panel's settings not to be respected (windows would go under panel, even if that wasn't allowed), trying to offset the display using xrandr made everything "magically" work again, even after reverting the offset, so I'm not sure what all of that was about.
Everything else seems to be in order now.
After going through all of this, the latest DU at the moment wants to remove gtk3-engines-oxygen and I'm not sure I should let that go (I use quite a few gtk apps under KDE and I do want them integrated nicely, I did use the Oxygen theme prior to KF5, I'm on Breeze now):
The following packages will be REMOVED:
gtk3-engines-oxygen
The following NEW packages will be installed:
libgck-1-0 libgcr-3-common libgcr-base-3-1
The following packages have been kept back:
dmeventd dmsetup libdevmapper-event1.02.1 libdevmapper1.02.1 liblvm2app2.2 liblvm2cmd2.02 lvm2
The following packages will be upgraded:
firmware-zd1211 gir1.2-gtk-3.0 gvfs gvfs-backends gvfs-bin gvfs-common gvfs-daemons gvfs-libs isc-dhcp-client isc-dhcp-common libcap2 libcap2-bin libgail-3-0 libgtk-3-0 libgtk-3-bin libgtk-3-common libhttpclient-java
libhttpcore-java libhttpmime-java libjna-java libjna-jni
21 upgraded, 3 newly installed, 1 to remove and 7 not upgraded.
Need to get 27.0 MB of archives.
UPDATE: OK, after checking https://tracker.debian.org/pkg/oxygen-gtk3 I guess that's gone now (removed from unstable and testing), so I might as well let go it to?
-
With a d-u -dV, the only package I'll miss is gimp. With kdenext, will gimp reinstall after removal?
-
drd: gimp is installable on my category 3) machine and seems to work fine although I haven't had time to give it a thorough test.
That said I've had a some other difficulties
After yesterday's du containing a libsystemd upgrade etc. my desktop and keyboard froze althougth the mouse was still usable. A hard reset was needed. After that the machine booted to desktop with no problems.
I need Krita but it is still not installable because of unmet dependencies ie.
krita : Depends: calligra-libs (= 1:2.8.6+dfsg-siduction1.4) but it is not going to be installed
Depends: libilmbase6 (>= 1.0.1) but it is not installable
Depends: libopenexr6 (>= 1.6.1) but it is not installable
CPU~Quad core AMD Phenom 9650 (-MCP-) speed/max~1150/2300 MHz Kernel~4.2.2-towo.1-siduction-amd64 x86_64 Up~29 min Mem~987.8/7989.8MB HDD~250.1GB(64.8% used) Procs~194 Client~Shell inxi~2.2.28
-
Do NOT dist-upgrade after July 31 until you find here further instructions, we will keep you posted.
1) dist-upgrading with apt (not aptitude) from a siduction KDE with kdenext last upgraded before July 29
I did the last du before the migration at 31th July, so I expected I'm still in 1)
After I ran a du recenty, X doesn't start.
With init 5 nothing happens, with startx a new console opens with a rectangle behind the login prompt.
System: Host: siductionbox Kernel: 4.2.2-towo.1-siduction-amd64 x86_64 (64 bit gcc: 5.2.1) Console: tty 1
Distro: siduction 13.2.1 December - kde - (201401272125)
Machine: Mobo: MSI model: 870-C45(FX) V2 (MS-7715) v: 1.0 Bios: American Megatrends v: V3.1 date: 04/16/2012
CPU: Dual core AMD Athlon II X2 260 (-MCP-) cache: 2048 KB
flags: (lm nx sse sse2 sse3 sse4a svm) bmips: 12805
clock speeds: max: 3200 MHz 1: 2500 MHz 2: 1900 MHz
Graphics: Card: NVIDIA GF119 [GeForce GT 520] bus-ID: 01:00.0
Display Server: X.org 1.17.2 drivers: nouveau (unloaded: fbdev,vesa)
tty size: 200x75 Advanced Data: N/A for root out of X
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driver: r8169 v: 2.3LK-NAPI port: e800 bus-ID: 02:00.0
IF: eth0 state: down mac: 8c:89:a5:9d:09:cd
Drives: HDD Total Size: 2136.5GB (26.6% used) ID-1: /dev/sdb model: ST1000DM003 size: 1000.2GB temp: 32C
ID-2: /dev/sda model: Samsung_SSD_840 size: 120.0GB temp: 0C
ID-3: /dev/sdc model: SAMSUNG_HD103SI size: 1000.2GB temp: 23C
ID-4: USB /dev/sdd model: Cruzer size: 16.0GB temp: 0C
Partition: ID-1: / size: 110G used: 7.8G (8%) fs: ext3 dev: /dev/sda1
ID-2: /home size: 721G used: 430G (63%) fs: ext4 dev: /dev/sdb1
Info: Processes: 125 Uptime: 3 min Memory: 274.3/7987.4MB Init: systemd runlevel: 5 Gcc sys: 4.9.3
Client: Shell (bash 4.3.421) inxi: 2.2.28
google-chrome.list:deb http://dl.google.com/linux/chrome/deb/ stable main
misc.list:deb-src http://ftp.spline.de/pub/siduction/kdenext unstable main
misc.list:deb http://packages.siduction.org/kdenext unstable main
siduction.list:deb http://ftp.spline.de/pub/siduction/base unstable main
siduction.list:deb http://ftp.spline.de/pub/siduction/extra unstable main contrib
siduction.list:deb http://ftp.spline.de/pub/siduction/fixes unstable main
root@siductionbox:~# dpkg -l | grep kwin
rc kwin 4:5.3.2-siduction1 amd64 KDE window manager
ii kwin-data 4:5.4.1-siduction1.4.3 all KDE window manager data files
ii kwin-style-breeze 4:5.4.1-siduction1.4 amd64 KWin Breeze Style
rc libkwin4-effect-builtins1 4:5.3.2-siduction1 amd64 KDE window manager effect builtins library
rc libkwineffects1abi5 4:4.11.22-3 amd64 library used by effects for the KDE window manager
ii libkwineffects6 4:5.4.1-siduction1.4.3 amd64 KDE window manager effects library
rc libkwinglesutils1 4:4.11.22-3 amd64 library with OpenGL/ES utilities for the KDE window manager
rc libkwinglutils1abi2 4:4.11.22-3 amd64 library with OpenGL utilities for the KDE window manager
ii libkwinglutils6 4:5.4.1-siduction1.4.3 amd64 KDE window manager gl utils library
ii libkwinxrenderutils6 4:5.4.1-siduction1.4.3 amd64 KDE window manager render utils library
root@siductionbox:~# apt-get install --reinstall kwin-x11 --install-recommends
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
nicht erstellt wurden oder Incoming noch nicht verlassen haben.
Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen:
Die folgenden Pakete haben unerfüllte Abhängigkeiten:
kwin-x11 : Hängt ab von: kwin-common (= 4:5.4.1-siduction1.4.3) soll aber nicht installiert werden
E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene defekte Pakete.
root@siductionbox:~# apt-get install kwin-x11 kwin-common
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
nicht erstellt wurden oder Incoming noch nicht verlassen haben.
Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen:
Die folgenden Pakete haben unerfüllte Abhängigkeiten:
kwin-common : Hängt ab von: qml-module-org-kde-kquickcontrolsaddons soll aber nicht installiert werden
Hängt ab von: qml-module-qtmultimedia soll aber nicht installiert werden
Hängt ab von: kio soll aber nicht installiert werden
Hängt ab von: libkf5declarative5 (>= 5.0.0) soll aber nicht installiert werden
Hängt ab von: libkf5kcmutils5 (>= 4.96.0) soll aber nicht installiert werden
Hängt ab von: libkf5newstuff5 (>= 4.95.0) soll aber nicht installiert werden
Hängt ab von: libkf5notifications5 (>= 4.96.0) soll aber nicht installiert werden
Hängt ab von: libkf5plasma5 (>= 5.2.0) soll aber nicht installiert werden
Hängt ab von: libkwin4-effect-builtins1 soll aber nicht installiert werden
E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene defekte Pakete.
What can I do?
Btw, the eth0 enty in interfaces was removed after du
-
Hi,
UPDATE: OK, after checking https://tracker.debian.org/pkg/oxygen-gtk3 (https://tracker.debian.org/pkg/oxygen-gtk3) I guess that's gone now (removed from unstable and testing), so I might as well let go it to?
Yes. By the way, the apt-get upgrade done by mistake moved you to the case 3), I'm glad you could sort the thing out.
I made a dist-upgrade and the most works fine but if I shut down I have a black screeen and nothing goes. So I must go to a tty and make there a shutdown. Do I miss a packet in kde?
I doubt you miss any packet, this seems more like a kde bug, but do you have kde-standard or kde-full installed?
For the record shutdown works properly here.
With a d-u -dV, the only package I'll miss is gimp. With kdenext, will gimp reinstall after removal?
Like clubex said gimp is installable after dist-upgrading, so you could go ahead and reinstall it once you have dist-upgraded if that's what you want to know.
I need Krita but it is still not installable because of unmet dependencies
Fixed, just do "apt-get update" and try again please.
Do NOT dist-upgrade after July 31 until you find here further instructions, we will keep you posted.
1) dist-upgrading with apt (not aptitude) from a siduction KDE with kdenext last upgraded before July 29
I did the last du before the migration at 31th July, so I expected I'm still in 1)
Indeed the correct date is July 31, not July 29, edited first post fixing the typo. So yes, you are in case 1)
After I ran a du recenty, X doesn't start.
With init 5 nothing happens, with startx a new console opens with a rectangle behind the login prompt.
[snip]
What can I do?
Btw, the eth0 enty in interfaces was removed after du
While you are in a situation where the dist-upgrade is suposed to work "out of the box", I'm inclined to think the dist-upgrade didn't finish successfully for your particular case, leaving you a system not completely updated. The reason why I suspect this is this thing you have posted:
kwin 4:5.3.2-siduction1 amd64 KDE window manager
ii kwin-data 4:5.4.1-siduction1.4.3 all KDE window manager data files
kwin should have been updated to 4:5.4.1-siduction1.4.3 after the upgrade, so something went wrong in the dist-upgrade.
So before trying anything else could you please try "apt-get dist-upgrade" and "apt-get -f dist-upgrade" and post the corresponding output of both commands?
-
Krita is now installable.
Thanks Santa.
-
I doubt you miss any packet, this seems more like a kde bug, but do you have kde-standard or kde-full installed?
I have kde-full. As workarround I shutdown from Konsole.
-
Santa:
When we have successfully upgraded should we stop using the kdenext repo?
-
I apt-get dist-upgraded my i386 Notebook - Firestarter - with kdenext (last upgrade on 31.07.15) without any problems, incl. new kernel and nvidia 340.93..
1153 aktualisiert, 139 neu installiert, 2 durch eine ältere Version ersetzt, 67 zu entfernen und 1 nicht aktualisiert
thx to Santa for the good job !
-
Hi Santa,
I got a lot of new pakages with the du, but it seems it didn't complete.
A second run (incl. update) provided nothing.
root@siductionbox:~# apt-get dist-upgrade
:
Es wurden 323 MB in 26 min 7 s geholt (206 kB/s).
Lese Changelogs... Fertig
Extrahiere Vorlagen aus Paketen: 100%
Vorkonfiguration der Pakete ...
(Lese Datenbank ... 158682 Dateien und Verzeichnisse sind derzeit installiert.)
:
Trigger für siduction-dynamic-dms (2014.08.13) werden verarbeitet ...
root@siductionbox:~#
root@siductionbox:~# apt-get -f dist-upgrade
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Edit:
tried another du:
root@siductionbox:~# apt-get -f dist-upgrade
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
Die folgenden Pakete werden aktualisiert (Upgrade):
libaudit-common libaudit1
2 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 62,0 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 1.024 B Plattenplatz freigegeben.
Möchten Sie fortfahren? [J/n]
Holen: 1 http://http.debian.net/debian/ unstable/main libaudit-common all 1:2.4.4-4 [14,8 kB]
Holen: 2 http://http.debian.net/debian/ unstable/main libaudit1 amd64 1:2.4.4-4 [47,2 kB]
Es wurden 62,0 kB in 1 s geholt (38,4 kB/s).
Lese Changelogs... Fertig
(Lese Datenbank ... 165305 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../libaudit-common_1%3a2.4.4-4_all.deb ...
Entpacken von libaudit-common (1:2.4.4-4) über (1:2.4.4-3) ...
Trigger für man-db (2.7.3-1) werden verarbeitet ...
Trigger für siduction-dynamic-dms (2014.08.13) werden verarbeitet ...
libaudit-common (1:2.4.4-4) wird eingerichtet ...
(Lese Datenbank ... 165305 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../libaudit1_1%3a2.4.4-4_amd64.deb ...
Entpacken von libaudit1:amd64 (1:2.4.4-4) über (1:2.4.4-3+b1) ...
libaudit1:amd64 (1:2.4.4-4) wird eingerichtet ...
Trigger für libc-bin (2.19-22) werden verarbeitet ...
root@siductionbox:~#
-
Hi,
I doubt you miss any packet, this seems more like a kde bug, but do you have kde-standard or kde-full installed?
I have kde-full. As workarround I shutdown from Konsole.
So you shouldn't be missing any package to make kde work properly, I would recommend you to ask in the kde forums (they will know better than me what you could try), since it seems a KDE bug/problem, but note that I can't reproduce it.
Santa:
When we have successfully upgraded should we stop using the kdenext repo?
Nope. Addind and removing the kdenext repository depending on the day is just a recipe to break your system.
Hi Santa,
I got a lot of new pakages with the du, but it seems it didn't complete.
A second run (incl. update) provided nothing.
[snip]
Ok, then try "dpkg --configure -a" and paste the output please.
-
There is no output
root@siductionbox:~# dpkg --configure -a
root@siductionbox:~#
-
[Half Off-Topic] Just a small hint for creating outputs: If you put a small "LANG=C " in front of your commands, the output will probably be turned to english language without the need to change locale or other stuff in your system. That makes it easier for international supporters to follow what apt and such want to tell us ;), and you can do it only when you create output for forums or paste-services, not in your normal life. Example
LANG=C dpkg --configure -a
LANG=C apt-get install -f
LANG=C apt dist-upgrade
[/OT]
-
Penyelam, from your output regarding kwin yesterday I think you miss some packages, do you have
kwin-common
kwin-data
kwin-style-breeze
kwin-x11 ?
-
There is no output
root@siductionbox:~# dpkg --configure -a
root@siductionbox:~#
Ok, let's go back to your first post (where you say kwin-x11 is not installable for you): whats the output of this?
LANG=C apt-get -o "Debug::pkgProblemResolver=true" install --reinstall kwin-x11 --install-recommends
-
root@siductionbox:~# LANG=C apt-get -o "Debug::pkgProblemResolver=true" install --reinstall kwin-x11 --install-recommends
Reading package lists... Done
Building dependency tree
Reading state information... Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
The following extra packages will be installed:
kwin-common libkf5newstuff5 libkwin4-effect-builtins1 qml-module-qtmultimedia
Suggested packages:
kwin-addons
The following NEW packages will be installed:
kwin-common kwin-x11 libkf5newstuff5 libkwin4-effect-builtins1 qml-module-qtmultimedia
0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 1993 kB of archives.
After this operation, 9563 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://packages.siduction.org/kdenext/ unstable/main libkf5newstuff5 amd64 5.14.0-siduction1.4 [191 kB]
Get:2 http://http.debian.net/debian/ unstable/main qml-module-qtmultimedia amd64 5.4.2-3 [70.6 kB]
Get:3 http://packages.siduction.org/kdenext/ unstable/main libkwin4-effect-builtins1 amd64 4:5.4.1-siduction1.4.3 [283 kB]
Get:4 http://packages.siduction.org/kdenext/ unstable/main kwin-common amd64 4:5.4.1-siduction1.4.3 [1431 kB]
Get:5 http://packages.siduction.org/kdenext/ unstable/main kwin-x11 amd64 4:5.4.1-siduction1.4.3 [18.2 kB]
Fetched 1993 kB in 16s (123 kB/s)
Selecting previously unselected package qml-module-qtmultimedia:amd64.
(Reading database ... 165304 files and directories currently installed.)
Preparing to unpack .../qml-module-qtmultimedia_5.4.2-3_amd64.deb ...
Unpacking qml-module-qtmultimedia:amd64 (5.4.2-3) ...
Selecting previously unselected package libkf5newstuff5:amd64.
Preparing to unpack .../libkf5newstuff5_5.14.0-siduction1.4_amd64.deb ...
Unpacking libkf5newstuff5:amd64 (5.14.0-siduction1.4) ...
Selecting previously unselected package libkwin4-effect-builtins1.
Preparing to unpack .../libkwin4-effect-builtins1_4%3a5.4.1-siduction1.4.3_amd64.deb ...
Unpacking libkwin4-effect-builtins1 (4:5.4.1-siduction1.4.3) ...
Selecting previously unselected package kwin-common.
Preparing to unpack .../kwin-common_4%3a5.4.1-siduction1.4.3_amd64.deb ...
Unpacking kwin-common (4:5.4.1-siduction1.4.3) ...
Selecting previously unselected package kwin-x11.
Preparing to unpack .../kwin-x11_4%3a5.4.1-siduction1.4.3_amd64.deb ...
Unpacking kwin-x11 (4:5.4.1-siduction1.4.3) ...
Processing triggers for siduction-dynamic-dms (2014.08.13) ...
Setting up qml-module-qtmultimedia:amd64 (5.4.2-3) ...
Setting up libkf5newstuff5:amd64 (5.14.0-siduction1.4) ...
Setting up libkwin4-effect-builtins1 (4:5.4.1-siduction1.4.3) ...
Setting up kwin-common (4:5.4.1-siduction1.4.3) ...
Processing triggers for siduction-dynamic-dms (2014.08.13) ...
Setting up kwin-x11 (4:5.4.1-siduction1.4.3) ...
Processing triggers for libc-bin (2.19-22) ...
root@siductionbox:~#
-
root@siductionbox:~# LANG=C apt-get -o "Debug::pkgProblemResolver=true" install --reinstall kwin-x11 --install-recommends
Reading package lists... Done
Building dependency tree
Reading state information... Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
The following extra packages will be installed:
kwin-common libkf5newstuff5 libkwin4-effect-builtins1 qml-module-qtmultimedia
Suggested packages:
kwin-addons
The following NEW packages will be installed:
kwin-common kwin-x11 libkf5newstuff5 libkwin4-effect-builtins1 qml-module-qtmultimedia
0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 1993 kB of archives.
After this operation, 9563 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://packages.siduction.org/kdenext/ unstable/main libkf5newstuff5 amd64 5.14.0-siduction1.4 [191 kB]
Get:2 http://http.debian.net/debian/ unstable/main qml-module-qtmultimedia amd64 5.4.2-3 [70.6 kB]
Get:3 http://packages.siduction.org/kdenext/ unstable/main libkwin4-effect-builtins1 amd64 4:5.4.1-siduction1.4.3 [283 kB]
Get:4 http://packages.siduction.org/kdenext/ unstable/main kwin-common amd64 4:5.4.1-siduction1.4.3 [1431 kB]
Get:5 http://packages.siduction.org/kdenext/ unstable/main kwin-x11 amd64 4:5.4.1-siduction1.4.3 [18.2 kB]
Fetched 1993 kB in 16s (123 kB/s)
Selecting previously unselected package qml-module-qtmultimedia:amd64.
(Reading database ... 165304 files and directories currently installed.)
Preparing to unpack .../qml-module-qtmultimedia_5.4.2-3_amd64.deb ...
Unpacking qml-module-qtmultimedia:amd64 (5.4.2-3) ...
Selecting previously unselected package libkf5newstuff5:amd64.
Preparing to unpack .../libkf5newstuff5_5.14.0-siduction1.4_amd64.deb ...
Unpacking libkf5newstuff5:amd64 (5.14.0-siduction1.4) ...
Selecting previously unselected package libkwin4-effect-builtins1.
Preparing to unpack .../libkwin4-effect-builtins1_4%3a5.4.1-siduction1.4.3_amd64.deb ...
Unpacking libkwin4-effect-builtins1 (4:5.4.1-siduction1.4.3) ...
Selecting previously unselected package kwin-common.
Preparing to unpack .../kwin-common_4%3a5.4.1-siduction1.4.3_amd64.deb ...
Unpacking kwin-common (4:5.4.1-siduction1.4.3) ...
Selecting previously unselected package kwin-x11.
Preparing to unpack .../kwin-x11_4%3a5.4.1-siduction1.4.3_amd64.deb ...
Unpacking kwin-x11 (4:5.4.1-siduction1.4.3) ...
Processing triggers for siduction-dynamic-dms (2014.08.13) ...
Setting up qml-module-qtmultimedia:amd64 (5.4.2-3) ...
Setting up libkf5newstuff5:amd64 (5.14.0-siduction1.4) ...
Setting up libkwin4-effect-builtins1 (4:5.4.1-siduction1.4.3) ...
Setting up kwin-common (4:5.4.1-siduction1.4.3) ...
Processing triggers for siduction-dynamic-dms (2014.08.13) ...
Setting up kwin-x11 (4:5.4.1-siduction1.4.3) ...
Processing triggers for libc-bin (2.19-22) ...
root@siductionbox:~#
So now you have just installed kwin; install kde-standard and reboot. Does it work now?
-
Hi there,
todays DU went flawlessly with kdenext enabled, last DU before GCC-5-Transition.
Thank you very much, Santa and all involved
LG
jd
-
Hi,
dto - after libstdc++6 i386/amd64 have the same version, I dist-upgraded my pc with kdenext (Riders on the Storm "upgraded" to plasma 5 before the transition started) without ANY error !
1521 updated, 181 new installed, 97 removed and 1 not updated
thx to Santa & all involved
-
Hi Santa,
yes it works now :) :) :)
Thanks a lot
Just a question: how can I start X at boot automatically?
inittab seems not to work in systemd
-
Hi,
thanks for providing packages for a smooth uprgrade to kde plasma 5!
I upgraded without any problems except that the dolphin service menus are no longer displayed on a right click.
I copied my service menus from ~ /.kde/share/kde4/services/ServiceMenus/ to ~/.local/share/kservices5/ServiceMenus/, but that didn't do any difference.
Could it be related to the fact, that plasma-scriptengine-ruby is no longer installable?
Greetings
cs
-
...
Just a question: how can I start X at boot automatically?
inittab seems not to work in systemd ...
For some reason on your system it seems as if graphical.target (=runlevel5.target ~ init 5) is not the default (test it with systemctl get-default). You can set it with systemctl set-default graphical.target
systemctl enable graphical.target That should create the proper symlink (on my system there is lrwxrwxrwx 1 root root 36 Mär 27 2014 /etc/systemd/system/default.target -> /lib/systemd/system/runlevel5.target).
-
[...]
Just a question: how can I start X at boot automatically?
inittab seems not to work in systemd
Hi Penyelam,
you can do this:
# systemctl set-default grapical.target
-
@der_bud @bluelupo
Danke,
funktioniert aber leider nicht
root@siductionbox:~# systemctl set-default graphical.target
root@siductionbox:~# systemctl enable graphical.target
The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
-
Hi,
....
I upgraded without any problems except that the dolphin service menus are no longer displayed on a right click.
I copied my service menus from ~ /.kde/share/kde4/services/ServiceMenus/ to ~/.local/share/kservices5/ServiceMenus/, but that didn't do any difference.
Could it be related to the fact, that plasma-scriptengine-ruby is no longer installable?
...
I had the same problem and found the solution here https://forum.kde.org/viewtopic.php?f=223&t=128621 (https://forum.kde.org/viewtopic.php?f=223&t=128621)
ln -s /usr/share/kde4/servicetypes/konqpopupmenuplugin.desktop /usr/share/kservicetypes5/works for me
-
@Jure:
Great, that works for me, too! You saved my day!
....
I upgraded without any problems except that the dolphin service menus are no longer displayed on a right click.
I copied my service menus from ~ /.kde/share/kde4/services/ServiceMenus/ to ~/.local/share/kservices5/ServiceMenus/, but that didn't do any difference.
Could it be related to the fact, that plasma-scriptengine-ruby is no longer installable?
...
I had the same problem and found the solution here https://forum.kde.org/viewtopic.php?f=223&t=128621 (https://forum.kde.org/viewtopic.php?f=223&t=128621)
ln -s /usr/share/kde4/servicetypes/konqpopupmenuplugin.desktop /usr/share/kservicetypes5/works for me
-
Great, thx, that saved my day too ;)
here are the related bugreports,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800080
https://bugs.kde.org/show_bug.cgi?id=350769
-
Last d-u: 30.07.2015
Did a d-u few Hours before - without any Problem with kde-next!
Nice work! Thanks a lot!
-
I doubt you miss any packet, this seems more like a kde bug, but do you have kde-standard or kde-full installed?
For the record shutdown works properly here.
I found the solution. The guilty program was iceweasel aurora. When I purged it and installed iceweasel from experimental the errror was away. I'm happy now. Thank you for your excellent work.
-
I ran a new du, I fear it didn't finish.
Instead the K-menu there is now the message:
Fehler beim Laden der QML-Datei: file:///usr/
share/plasma/plasmoids/
org.kde.plasma.kickoff/contents/ui/
Kickoff.qum:27:1:module
"org.kde.plasma.private.kickoff" is not installed
-
I ran a new du, I fear it didn't finish.
Did it finish - or did it not finish?
Do or do not - there is no try! (or i fear it didnt finish)
How you made the d-u?
aptitude? -> known not to work
So, assuming you have kdenext in your sources.list:
What is suposed to work out of the box:
1) dist-upgrading with apt (not aptitude) from a siduction KDE with kdenext last upgraded before July 31 2015 (date of the debian/ubuntu switch to GCC 5)
2) dist-upgrading with apt (not aptitude) a fresh new indiansummer installation following the instructions https://community.kde.org/Plasma/InstallingNext#siduction (https://community.kde.org/Plasma/InstallingNext#siduction)
apt -> worked for me flawlessly in runlevel 3
System: Host: ccsbox Kernel: 4.2.3-towo.1-siduction-amd64 x86_64 (64 bit gcc: 5.2.1)
Desktop: KDE Plasma 5.4.1 (Qt 5.4.2)
Distro: siduction 12.2.0 Riders on the Storm - kde - (201212092131)
Machine: Mobo: ASRock model: 990FX Extreme9 Bios: American Megatrends v: P1.70 date: 06/04/2014
CPU: Octa core AMD FX-9590 Eight-Core (-MCP-) cache: 16384 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 75067
clock speeds: max: 4700 MHz 1: 1400 MHz 2: 1400 MHz 3: 4700 MHz 4: 1400 MHz 5: 1400 MHz 6: 1400 MHz
7: 1400 MHz 8: 1400 MHz
Memory: Array-1 capacity: 32 GB devices: 4 EC: None
Device-1: A1_DIMM0 size: 4 GB speed: 533 MHz type: DDR3 part: CMP8GX3M2A1600C9
Device-2: A1_DIMM1 size: 4 GB speed: 533 MHz type: DDR3 part: CMP8GX3M2A1600C9
Device-3: A1_DIMM2 size: 4 GB speed: 533 MHz type: DDR3 part: CMP12GX3M3A1600C9
Device-4: A1_DIMM3 size: 4 GB speed: 533 MHz type: DDR3 part: CMP12GX3M3A1600C9
Graphics: Card: NVIDIA GK110 [GeForce GTX 780] bus-ID: 01:00.0
Display Server: X.Org 1.17.2 driver: nvidia Resolution: 1680x1050@59.88hz
GLX Renderer: GeForce GTX 780/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 346.82 Direct Rendering: Yes
Audio: Card-1 NVIDIA GK110 HDMI Audio driver: snd_hda_intel bus-ID: 01:00.1
Card-2 Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA) driver: snd_hda_intel bus-ID: 00:14.2
Sound: Advanced Linux Sound Architecture v: k4.2.3-towo.1-siduction-amd64
Network: Card: Intel 82583V Gigabit Network Connection driver: e1000e v: 3.2.5-k port: 9000 bus-ID: 0a:00.0
IF: enp10s0 state: up speed: 100 Mbps duplex: full mac: 00:00:00:00:00:00
Drives: HDD Total Size: 8757.7GB (38.2% used) ID-1: /dev/sda model: WDC_WD30EZRX size: 3000.6GB
ID-2: /dev/sdb model: OCZ size: 256.1GB ID-3: /dev/sdc model: ST5000NM0024 size: 5001.0GB
ID-4: /dev/sdd model: SAMSUNG_HD501LJ size: 500.1GB
Optical: /dev/sr0 model: HL-DT-ST BD-RE BH16NS40 rev: 1.03 dev-links: cdrom,cdrw,dvd,dvdrw
Partition: ID-1: / size: 219G used: 33G (16%) fs: ext4 dev: /dev/sdb1
label: N/A uuid: bllaaaaaaaaaaahhhhhhhhhhhhhh
ID-2: /home size: 4.6T used: 2.7T (62%) fs: ext4 dev: /dev/sdc1
label: N/A uuid: bllaaaaaaaaaaahhhhhhhhhhhhhh
ID-3: swap-1 size: 17.18GB used: 0.00GB (0%) fs: swap dev: /dev/sdb2
label: N/A uuid: bllaaaaaaaaaaahhhhhhhhhhhhhh
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 28.5C mobo: 33.0C gpu: 0.0:27C
Fan Speeds (in rpm): cpu: N/A fan-1: 0 fan-2: 0 fan-3: 0 fan-4: 0 fan-5: 0
Info: Processes: 235 Uptime: 4:02 Memory: 1805.8/16007.6MB Init: systemd runlevel: 5 Gcc sys: 5.2.1
Client: Shell (bash 4.3.421) inxi: 2.2.28
-
@CCarpenter
that was just a suspicion because a module is missing.
During the du was nothing peculiar.
Of course I ran it in runlevel 3 with apt-get
-
It works :)
I already tried to install plasma-desktop one or two hours ago, but it fails.
Recently, after another du the install finished successfully.
-
It works :)
I already tried to install plasma-desktop one or two hours ago, but it fails.
Recently, after another du the install finished successfully.
Nice to hear. I hope i did not offend you!
-
D-U successful here. Booted to desktop at least, I haven't used it much yet.
siduction December last d-u in July.
Edit: This is with kdenext.
Thanks you Santa and all the dev team for wonderful work. ;)
-
New version of gimp came in so took the plunge and d-u went with no issues
-
d-u sucessful here also. May I say a big "THANK YOU" for the great work? ;D
-
Hi Santa,
unfortunately I wasn't so lucky. Can you please have a look at:
http://forum.siduction.org/index.php?topic=5810.0
Two questions:
Did I do anything wrong, and if so what did I do wrong?
Can I do anything or is a new install necessary?
Thanks, C
-
Hi all,
my inst is a case 3 one with kdenext. I attached a file containing the d-u logs after 31 July. I think the transiition to gcc5 has started or is finalized on my box.
Before now starting the adventure called "d-u":
1) Can I downgrade packages in order to become a case 1 installation and have a flawless d-u after?
2) Or shall I just start d-u and ask for help/support here later?
What is the best way documenting the d-u while in init 3 in order to be prepared to deliver information in case of fail?
Thanks in advance!
-
1 is not an option, 2 is best performed while in IRC.
greetz
devil
-
PERFECT!
Hi all,
the d-u on my box went smoothly and finished perfect. Congratulatios to the team and all who contributed!
This is worth a Caledonia Edradour 12 y old Single Malt alternatively a comparable donation.
Please tell me your choice per PM.
Thanks!
-
Hi all,
after the smooth big d-u another d-u -s provides me now:
Die folgenden Pakete sind zurückgehalten worden:
gcc-5-base:i386 libatomic1:i386 libgcc1:i386 libgomp1:i386
libgraphicsmagick3 libitm1:i386 libmpx0:i386 libquadmath0:i386
Die folgenden Pakete werden aktualisiert (Upgrade):
binutils default-jre default-jre-headless gir1.2-gtk-3.0 java-common
libgtk-3-0 libgtk-3-bin libgtk-3-common libqxt-core0 libqxt-gui0
python-pkg-resources python3-pkg-resources
12 aktualisiert, 0 neu installiert, 0 zu entfernen und 8 nicht aktualisiert.
[code]
Sorry for LANG=C not working.
Do i have to obey something or act in any way on the holdbacks "zurückgehalten" on the gcc5_i386 packs listed above?
-
Hi all,
after the smooth big d-u another d-u -s provides me now:
Die folgenden Pakete sind zurückgehalten worden:
gcc-5-base:i386 libatomic1:i386 libgcc1:i386 libgomp1:i386
libgraphicsmagick3 libitm1:i386 libmpx0:i386 libquadmath0:i386
Die folgenden Pakete werden aktualisiert (Upgrade):
binutils default-jre default-jre-headless gir1.2-gtk-3.0 java-common
libgtk-3-0 libgtk-3-bin libgtk-3-common libqxt-core0 libqxt-gui0
python-pkg-resources python3-pkg-resources
12 aktualisiert, 0 neu installiert, 0 zu entfernen und 8 nicht aktualisiert.
[code]
Sorry for LANG=C not working.
Do i have to obey something or act in any way on the holdbacks "zurückgehalten" on the gcc5_i386 packs listed above?
That's a temporary problem with multiarch systems which happens every time a new GCC version is uploaded to sid. Today a new GCC package revision was uploaded and it's probably not yet available for i386 for you, see:
http://forum.siduction.org/index.php?topic=5801.msg47619#msg47619
-
I did some du in the last days and everything worked fine.
I really appreciate the good job done, thanks a lot.
But there are still some minor issues:
- KMail: I've to enter the passwords each time when I start KMail.
The password-field in the Account Settings says "Wallet disabled in system settings"
But in Settings-System Settings-Account Details the "Enable KDE wallet subsytem" box is checked. - KOrganizer: I use several calendar, the edit-dialog doesn't allow to change the calendar for an existing event.
- K-Menu - History: "clean documents" is missing, only "clean application" is there.
- K-Menu: in "Application Launcher Settings" I checked "Show 'Recently installed'", but they are not shown.
- I'd like to have different wallpapers in the Virtual Desktops. Will this feature enabled again?