Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: Santa on 2015/07/01, 19:46:51
-
Hello,
the person in charge of KDE in debian made some uploads to sid of packages which belong to Plasma 5. This is breaking KDE SC 4 while at the same time plasma 5 isn't available in debian sid.
I also have reasons to think that his intention is making plasma 5 available soon, however I'm not completely sure because since Ieft the debian qt/kde "team" this kind of things are being done unnanounced.
Since the person in charge of KDE in debian seems to insist in breaking KDE SC 4 and it's not very feasible to fix all the continuous incoming breakages and Plasma 5 will be uploaded to sid sooner or later: in a few hours or days the plasma 5 packages available in the kdenext/kde-frameworks repository will be moved to kdenext/unstable.
Fortunately our Plasma 5 packages are reasonably mature although not perfect. Note that they are available here in siduction for more than a year, thing which allowed us to improve the packaging and be ready for this little apocalypse.
What to do to "survive" gracefully:
Option a: Do NOT dist-upgrade and stay with KDE SC 4 for a while; if you already upgraded some packages that you shouldn't the breakages can be undone, you can ask for help here. This option is only reasonable as a temporary solution while you find some free time to go for the option b or c, see below.
Option b: Install Plasma 5 in other hard disk/partition; grab a siduction indiansummer iso, install it and upgrade to Plasma 5 following the instructions here: https://community.kde.org/Plasma/InstallingNext#siduction
Option c: Make backup and upgrade your existing Plasma 4 installation to Plasma 5. Instructions here: https://community.kde.org/Plasma/InstallingNext#siduction
Keep in mind that you may need to reconfigure some programs or things in Plasma.
I would recommend you the Option b. It's the option I did for myself and I'm now writing this message from my new Plasma 5 installation.
Cheers.
EDIT #1 (Friday, 3 July 23:12 zulu)
The KDE Packages were copied from kdenext/kde-frameworks to kdenext/unstable as announced above; this way Plasma 5 becomes the default for siduction.
-
in a few hours or days the plasma 5 packages available in the kdenext/kde-frameworks repository will be moved to kdenext/unstable.
Does this mean that option C will happen automatically? (except that if you dist-upgrade now without frameworks things will break)
What is this second one I also have and does it change things for me?
deb http://packages.siduction.org/kdenext unstable main
deb http://packages.siduction.org/kdenext/ experimental-snapshots main
Is the difference between option B and C just that the upgrade is with default config settings?
-
https://lists.debian.org/debian-kde/2015/06/msg00040.html (https://lists.debian.org/debian-kde/2015/06/msg00040.html)
edit, forgot that you have to shift to view July's posts.
https://lists.debian.org/debian-kde/2015/07/msg00000.html
-
Why does it try to use the older package instead of the newer one?
The following packages have unmet dependencies:
plasma-desktop-data : Breaks: kde-workspace-data (< 4:5.0.0) but 4:4.11.13-2.1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
$ apt-cache policy kde-workspace-data
kde-workspace-data:
Installed: 4:4.11.13-2.1
Candidate: 4:5.3.2-siduction1
Version table:
4:5.3.2-siduction1 0
500 http://packages.siduction.org/kdenext/ kde-frameworks/main amd64 Packages
4:4.11.13-90r2 0
500 http://packages.siduction.org/kdenext/ unstable/main amd64 Packages
*** 4:4.11.13-2.1 0
100 /var/lib/dpkg/status
4:4.11.13-2 0
500 http://http.debian.net/debian/ unstable/main amd64 Packages
$ apt-cache policy plasma-desktop-data
plasma-desktop-data:
Installed: (none)
Candidate: 4:5.3.2-siduction1
Version table:
4:5.3.2-siduction1 0
500 http://packages.siduction.org/kdenext/ kde-frameworks/main amd64 Packages
These are the sources:
deb http://packages.siduction.org/base unstable main
deb-src http://packages.siduction.org/base unstable main
deb http://packages.siduction.org/extra unstable main contrib non-free
deb-src http://packages.siduction.org/extra unstable main contrib non-free
deb http://packages.siduction.org/user unstable main contrib non-free
deb-src http://packages.siduction.org/user unstable main contrib non-free
deb http://packages.siduction.org/fixes unstable main contrib non-free
deb-src http://packages.siduction.org/fixes unstable main contrib non-free
deb http://packages.siduction.org/kdenext unstable main
deb http://packages.siduction.org/kdenext kde-frameworks main
-
Is there a way to uninstall KDE completely?
-
in a few hours or days the plasma 5 packages available in the kdenext/kde-frameworks repository will be moved to kdenext/unstable.
Does this mean that option C will happen automatically? (except that if you dist-upgrade now without frameworks things will break)
if you have kdenextunstable in your sources-list, yes. But still I can abort the merge of kdenext/kde-frameworks into kdenext/unstable depending on the breakages of this week.
What is this second one I also have and does it change things for me?
deb http://packages.siduction.org/kdenext (http://packages.siduction.org/kdenext) unstable main
deb http://packages.siduction.org/kdenext/ (http://packages.siduction.org/kdenext/) experimental-snapshots main
The second line in your sources.list is/was a place where I was making available releases of kde a few days before they were officially released in order to get you the chance to test them a bit in advance. Nope, it doesn't change things for you.
Is the difference between option B and C just that the upgrade is with default config settings?
The main difference is that you can keep your old system and check how it was configured to configure the new plasma 5 in a similar way; also you can migrate your settings without hurries and eventually stay with KDE SC 4 in case I revert my decision of merging kdenext/kde-frameworks into kdenext/unstable.
Why does it try to use the older package instead of the newer one?
The following packages have unmet dependencies:
plasma-desktop-data : Breaks: kde-workspace-data (< 4:5.0.0) but 4:4.11.13-2.1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
[snip]
Could you please paste the output of "apt-mark showhold" and "apt-cache policy kde-workspace-data"?
-
Hi @vayu,
The following packages have unmet dependencies:
plasma-desktop-data : Breaks: kde-workspace-data (< 4:5.0.0) but 4:4.11.13-2.1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
From manjaro forum, Change from kde4 to plasma 5
https://forum.manjaro.org/index.php?topic=18225.0 (https://forum.manjaro.org/index.php?topic=18225.0)
2. Remove everything that depends on kdebase-workspace
sudo pacman -R $(LANG=C pacman -Qi kdebase-workspace | grep "Req" | sed -e 's/Required By : //g')
And remove kdebase-workspace too
sudo pacman -R kdebase-workspace
siduction is not arch based, and the pacman hints don't work here. But your error has to do with old kdebase-workspace stuff, so perhaps give this suggestion a try and remove all old kdebase-workspace stuff before upgrading to plasma 5.
Kind regards,
Holger
-
wäre jemand so nett und könnte das alles nochmal kurz in deutsch zusammenfassen? Bei mir läuft Plasma5 schon und will natürlich nicht böse in irgendwas reinschlittern .. ;)
-
Hallo @reddark,
wenn bei Dir schon plasma 5 läuft, kannst Du, was kf5 und plasma angeht, meiner Meinung nach aktualisieren und Dich dabei entspannt zurück lehnen :-)
Ich habe vor wenigen Minuten ein Dist-Upgrade gemacht, und die Aktualisierung auf Plasma 5.3.2 und aktuelles kf5 ist bei mir sauber durch gelaufen.
Viele Grüße,
Holger
-
alles klar ... danke ;)
-
I installed plasma5 using option c and as per Santa's instructions.
I haven't had much time to play but it seems OK at the moment except that the search function of the Kstart menu seems to be missing.
The systemsettings upgrade still fails with my enGB locale in fact it fails with any other locale than US and, I suspect, DE (I haven't tried the latter as my German is poor). There is a bug report #790702 for someone osiing the Itailian locale which seems to back up this assertion. Switching to US locale allows the upgrade without errors.
Incidentally systems settings is now named systemsettings5 so fthis I had to allow for this as I'm attempting to maintain my old desktop setup.
If anything else crops up I'll post again.
-
1072 upgraded, 298 newly installed, 15 to remove and 0 not upgraded
I used Option B, a clean install of Indian Summer. It seems to have worked, I have a working KDE installation. The search function of the KStart Menu works fine here as both the Launcher and the Menu.
I'm not quite sure how to ask the question. I don't see a way in systemsettings to change any of the splash screens/backgrounds. What does it take to get siduction back? Summer Breeze is just not quite my cup of tea.
Thanks to everyone for their efforts.
-
Why does it try to use the older package instead of the newer one?
The following packages have unmet dependencies:
plasma-desktop-data : Breaks: kde-workspace-data (< 4:5.0.0) but 4:4.11.13-2.1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
[snip]
Could you please paste the output of "apt-mark showhold" and "apt-cache policy kde-workspace-data"?
Thanks. I used apt-cache rdepends and and-get remove until the du went through then reinstalled whatever I removed. Everything is working well.
-
ghstryder:
It's in Appearance>Workspace Them>Splash Screen.
Trouble is there doesn't appear to be any easy way of importing new splash screens.
Unusually for KDE there seems to me to be less configuration options with each new release of the desktop. I reckon not having the option to have different backgrounds for virtual desktops will drive a lot of people to downgrade to KDE4.
-
Sorry, I should have stated that in my post. I found where I thought I'd make the change, but as you say, no apparent way to make the change, or import a new theme/page. It's good to know it wasn't just my install, thanks for the response.
Other than that, things are pretty much working. Dropbox syncs, but there is no icon in the tray and the notifier doesn't work.
-
Hmm. It is the little things that count for me.
A few plasmoids that are important to me will not be converted to Plasma 5. For example wicd-kde or veromix-kde and some others. Having an eye on lxqt now.
Here is a quick overview:
http://developer.kde.org/~cfeck/portingstatus.html
-
After reading the posts regarding kde-workspace I verified that I did not have kdebase-workspace-bin (which should only be a transitional package to kde-workspace-bin), but already had the latter one.
Activating kdenext to follow "Option c" I saw during dist-upgrade these lines scrolling:
...
kde-workspace-bin (4:5.3.2-siduction1) wird eingerichtet
kdebase-workspace-bin (4:4-11-13-90r2) wird eingerichtet
...
So here too 'something' pulls in that 90r2-versioned kdebase-workspace-bin, removing it after D-U removes siduction-art-ksplash-december as well.
-
@harakiri: LXQt will be great someday - but it will not solve any of your KDE problems - we have at least no plasmoids, no plasma etc - only a light and fast DE that is still under heavy development.
-
Is there an option d) . . . . to not d-u till debian sid catches up. Or is this not an option due to the piecemeal way things are being uploaded?
-
Hi,
Is there an option d) . . . . to not d-u till debian sid catches up. Or is this not an option due to the piecemeal way things are being uploaded?
Short answer: I would say this is not an option due "to the piecemeal way things are uploaded" and several other reasons.
Long answer:
Well, if you are not using kdenext already you can try to do that. But you have a problem, and it's the following million dollar question "When do I know when debian sid catched up?"
I can't reply to that question, only the person in charge of KDE in debian can, because in addition to "the piecemeal way things are being uploaded" the packages they are attempting to upload are a port of kubuntus packaging. My packages are a port of kubuntu's packaging too, but they have some changes compared with the packages from debian:
- Allow you to dist-upgrade from KDE SC 4 without problems
- Allow you to use the packages in a system without the "install recommends automatically" enabled (and this is the default for siduction so far)
- Fix the problems described here by early siduction testers (thanks for the feedback guys!) http://forum.siduction.org/index.php?topic=5587.0 (http://forum.siduction.org/index.php?topic=5587.0)
- kio-mtp works (i.e. you can plugin your android phone and see the files)
- Allow you to use yakuake in Plasma 5
Also note that all the complete KDE Sofware stack is available in kdenext with their needed dependencies; they are right now more than 300 source packages developed with the help of an automation tool I wrote (kubuntu's people have one too). The automation tools we have are very specific to the distribution and I don't know if they have one in debian which would work properly for frameworks/plasma5/kde-applications or not.
So, given all the issues I have explained above they might take some time to catch up. As I said I don't know when they would be ready, if you really want to stay with debian's packaging the best thing is that you ask them to write a mail to debian-kde@lists.alioth.org notifying that everything is fine again, good luck with that.
One thing more, any problem with debian's packaging? you should ask the debian kde guy. Any problem with kdenext's packages? As a kdenext user you are under my protection and you can ask me; and talking about that there are a couple of reasons to not include your proposed option d in my advice post:
- if you ask people from debian and they find out you are not using debian but siduction they may refuse to help you
- at the same time you won't get support from me for debian's packages
- due to all the things I have explained above in this post, your proposed option d) doesn't fit in my definition of "What to do to 'survive' gracefully"
Still, if you want to continue to use debian's kde packaging, that's your choice, but as I said you should ask debian's people for help, not me.
P.S. I would like to reply to more stuff in this thread but I don't have much time right now.
-
only one thing:
Allow you to use the packages in a system with the "install recommends automatically" enabled (and this is the default for siduction so far)
siduction don't install recommends per default
-
Thanks for your comprehensive answer santa! I'll go with c)!
-
only one thing:
Allow you to use the packages in a system with the "install recommends automatically" enabled (and this is the default for siduction so far)
siduction don't install recommends per default
I meant without, post edited, thanks.
-
Allow you to dist-upgrade from KDE SC 4 without problems
I can't tell you enough how much I appreciate this! My system is running great with SC 5 upgraded from SC 4. Thank you.
-
I will second that. Thank you Santa. My system is doing everything it needs to do right now. This seems pretty tame compared to the KDE 3 -> 4 transition. I haven't seen anyone threaten to jump off a cliff or predict the world would end.
For the rest of the Siduction crew - I just did a clean install of Indian Summer on a SSD, then made the switch to KDE5. I had tripped the multiarch switch, so those packages were included, but that du involved almost 1500 packages. I clearly remember days when I would have broken out in a sweat at the very thought. This pretty much completed while I went for a cup of coffee and made a phone call. Kudos to each and every one of you.
-
@Santa
Thank you for that post, which explained not only what the options are, but also the consequences and the context.
I now -belatedly even from someone from Berne region- understood what you actually do! Thanks!
best, gnasch
-
@Santa, thanks for all your work for our distro. Since yesterday I have converted two systems from KDE 4 to Plasma 5, for my own use. It is usable, for sure. Couple of points for others who are considering it:
- It seems cleaner to (after upgrading) delete the existing user(s), including the contents of his home folder, and then make the user again for Plasma 5. This way the old config files don't fight Plasma 5 configs.
- kdesu/kdesudo does not work, but gksu does.
- In systemsettings, the Autostart function is not actually working, although it does move scripts to ~/.config. You'll have to write a .desktop file in ~/.config/autostart to run your autostart scripts.
- You can't click the desktop and then type the command like KDE 4, but Alt-F2 still launches krunner.
Thanks again -- I'm surviving gracefully today! ;D
-
@dibl: Do you use the repository kdenext?
-
- In systemsettings, the Autostart function is not actually working, although it does move scripts to ~/.config. You'll have to write a .desktop file in ~/.config/autostart to run your autostart scripts.
- You can't click the desktop and then type the command like KDE 4, but Alt-F2 still launches krunner.
in my test installation (in virtualbox, indiansummer amd64 -kdenext - with kde-full (kde-plasma 5.3.2, Qt 5.4.2) both is working.
The prog set in autostart is running after login and the context-menu after right-click the desktop shows on top the function "Befehl ausführen" "run command", witch launches krunner
@ Santa -thx for your work !
-
I am actually loving this and over time, I know it will improve even better.
I have been running this for a few days now kinda testing the waters.
I run both conky & wbar without problems, well, my configs have no problems.
It's actually been a smooth transition and I thank you Santa ;)
-
@dibl: Do you use the repository kdenext?
Yes, kde-frameworks in kdenext.
-
in my test installation (in virtualbox, indiansummer amd64 -kdenext - with kde-full (kde-plasma 5.3.2, Qt 5.4.2) both is working.
The prog set in autostart is running after login and the context-menu after right-click the desktop shows on top the function "Befehl ausführen" "run command", witch launches krunner
@ Santa -thx for your work !
After I had the first challenge with setting a script to run on startup, I searched online and found this (https://en.opensuse.org/SDB:KDE_Plasma_5), which says that it is a known issue and can be worked around by using a .desktop file, so that is what I did to resolve it. Maybe I didn't try enough. My conky runs with no issue, after I manually launched it one time, but it does not appear in Startup and Shutdown/Autostart under systemsettings.
-
- In systemsettings, the Autostart function is not actually working, although it does move scripts to ~/.config. You'll have to write a .desktop file in ~/.config/autostart to run your autostart scripts.
- You can't click the desktop and then type the command like KDE 4, but Alt-F2 still launches krunner.
in my test installation (in virtualbox, indiansummer amd64 -kdenext - with kde-full (kde-plasma 5.3.2, Qt 5.4.2) both is working.
The prog set in autostart is running after login and the context-menu after right-click the desktop shows on top the function "Befehl ausführen" "run command", witch launches krunner
@ Santa -thx for your work !
Hello,
I've made following experience:
When trying to ad a script to Autostart, it will be ignored, but adding a program to autostart works.
Off topic: Na Jürgen, doch neugierig geworden auf kf5? ;D
Kind regards,
Holger
-
of course my fault, I started a program and not a script...
----
OT: Hallo Holger - bei (ohne hold)
115 aktualisiert, 107 neu installiert, 1 zu entfernen und 0 nicht aktualisiert
muss ich ja mal schauen,, was passiert, allerdings in einer vm - läuft soweit. Umwerfend Neues oder Besseres habe ich aber noch nicht entdeckt ;-) ....
-
Hi,
Like one hour ago the packages from kdenext/kde-frameworks were copied to kdenext/unstable, first post edited.
More stuff is coming to siduction soon, please stay tuned.
-
Santa:
So we can remove the kde-frameworks repo from the sources list?
-
Santa:
So we can remove the kde-frameworks repo from the sources list?
If you are already have kdenext/unstable, yes you can remove it from your sources.list
I have updated the installation instructions here:
https://community.kde.org/Plasma/InstallingNext#siduction (https://community.kde.org/Plasma/InstallingNext#siduction)
-
I have updated the installation instructions here:
https://community.kde.org/Plasma/InstallingNext#siduction (https://community.kde.org/Plasma/InstallingNext#siduction)
The instructions refer to sddm-kcm I found it as:
$ apt-cache search sddm
kde-config-sddm - KCM module for SDDM
Meanwhile, I couldn't get sddm to work. It would hang with a black screen after login. After ctrl f1 I entered dpkg-reconfigure sddm, and set it to kdm, then rebooted and it strangely went into sddm and worked. Then I did dpkg-reconfigure again and set it to sddm and it broke again. Then I set it to kdm and it was still broken. I uninstalled sddm and now I'm back in with kdm. Searching google, I could only find conflicting ideas of how to set the dm.
Then uninstalled kdm and had only sddm installed, but that didn't work either. Yet it did one time work so something must be stopping it from starting X. I tried deleting ~/.Xauthority. Does anyone know the steps involved in making sure the startup to sddm works?
-
I notice that systemd has disappeared from systemsettings although kcmsystemd is installed. Can't see any substitute amongst kf5 packages. It this somethng we have to wait for?
-
there is systemadm in systemsettings on my kde test installation
-
there is systemadm in systemsettings on my kde test installation
What "kde test installation" do you have ?
with
500 http://packages.siduction.org/kdenext/ unstable/main amd64 Packages
piper@x1:~$ apt-cache policy systemadm
N: Unable to locate package systemadm
Unless your using systemd-ui which is in the sid branch
-
Hi,
I notice that systemd has disappeared from systemsettings although kcmsystemd is installed. Can't see any substitute amongst kf5 packages. It this somethng we have to wait for?
You are right, we had a package available in siduction but not in debian to provide that kcm. Fortunately there is a frameworks based version, but we need to package it. So I think you will get it back.
I have updated the installation instructions here:
https://community.kde.org/Plasma/InstallingNext#siduction (https://community.kde.org/Plasma/InstallingNext#siduction)
The instructions refer to sddm-kcm I found it as:
$ apt-cache search sddm
kde-config-sddm - KCM module for SDDM
Meanwhile, I couldn't get sddm to work. It would hang with a black screen after login. After ctrl f1 I entered dpkg-reconfigure sddm, and set it to kdm, then rebooted and it strangely went into sddm and worked. Then I did dpkg-reconfigure again and set it to sddm and it broke again. Then I set it to kdm and it was still broken. I uninstalled sddm and now I'm back in with kdm. Searching google, I could only find conflicting ideas of how to set the dm.
Then uninstalled kdm and had only sddm installed, but that didn't work either. Yet it did one time work so something must be stopping it from starting X. I tried deleting ~/.Xauthority. Does anyone know the steps involved in making sure the startup to sddm works?
It seems you are right, I'm busy with other stuff but I will investigate it. Lasts test I have been doing were done with lightdm and kdm, thanks for noticing.
-
i don't know the current state of sddm - sddm was ok for native english speakers and only for them - because the keyboard and language settings in the greeter don't work nice last time i had a look - so until these things are fixed and sddm is more mature then now i would recommend lightdm.
And by the way - i would be happy to switch away from lightdm to sddm, if sddm really work without problems - but that wasn't the case in the last 2 years. So lightdm will be the DM of choice in siduction and sddm will remain not used and not official supported.
-
....
What "kde test installation" do you have ?
with
500 http://packages.siduction.org/kdenext/ unstable/main amd64 Packages
Hi piper
inxi -Sr
System: Host: siductionkde5 Kernel: 4.1.1-towo.1-siduction-amd64 x86_64 (64 bit) Desktop: KDE 5
Distro: siduction 14.1.0 Indian Summer - kde (-full) (201411230337)
Repos: Active apt sources in file: /etc/apt/sources.list.d/debian.list
deb http://http.debian.net/debian/ unstable main contrib non-free
Active apt sources in file: /etc/apt/sources.list.d/siduction.list
deb http://packages.siduction.org/base unstable main
deb http://packages.siduction.org/extra unstable main
deb http://packages.siduction.org/fixes unstable main
deb http://packages.siduction.org/kdenext unstable main
deb http://packages.siduction.org/kdenext kde-frameworks main
piper@x1:~$ apt-cache policy systemadm
N: Unable to locate package systemadm
yes I know - but
ls -l /usr/bin/system*
-rwxr-xr-x 1 root root 163224 Jun 6 21:55 /usr/bin/systemadm
and it works
-
Hello Alf,
since my switch to kf5 and plasma5 with siduction I use sddm without any problems, same situation with Antergos, Manjaro and Netrunner. I've a german localised system and sddm also "speaks" german with me :)
Kind regards,
Holger
-
Dann stell das mal im Greeter um - der Fall ist wirklich nicht weit hergeholt, wir haben einen gemischtsprachigen Haushalt
Edit: Noch schicker wird es, wenn wie bei uns die Lokalisierung mal abḱackt - das hat änderbar zu sein, ansonsten ist dieses Teil nicht reif für den täglichen distributionsweiten Einsatz.
Edit zum Edit: Lassen wir sddm erst mal in debian ankommen und warten die ersten begeisternden Fehlermeldungen ab.
-
yes I know - but
Code: [Select] (http://javascript:void(0);)ls -l /usr/bin/system*
-rwxr-xr-x 1 root root 163224 Jun 6 21:55 /usr/bin/systemadm and it works
I believe everyone should have this
piper@x1:~$ ls -l /usr/bin/system*
-rwxr-xr-x 1 root root 163224 Jun 6 15:55 /usr/bin/systemadm
-rwxr-xr-x 1 root root 1409008 Jun 28 06:23 /usr/bin/systemd-analyze
-rwxr-xr-x 1 root root 35328 Jun 28 06:23 /usr/bin/systemd-cat
-rwxr-xr-x 1 root root 281808 Jun 28 06:23 /usr/bin/systemd-cgls
-rwxr-xr-x 1 root root 68208 Jun 28 06:23 /usr/bin/systemd-cgtop
-rwxr-xr-x 1 root root 64088 Jun 28 06:23 /usr/bin/systemd-delta
-rwxr-xr-x 1 root root 35320 Jun 28 06:23 /usr/bin/systemd-detect-virt
-rwxr-xr-x 1 root root 23096 Jun 6 15:55 /usr/bin/systemd-gnome-ask-password-agent
-rwxr-xr-x 1 root root 515304 Jun 28 06:23 /usr/bin/systemd-nspawn
-rwxr-xr-x 1 root root 43512 Jun 28 06:23 /usr/bin/systemd-path
-rwxr-xr-x 1 root root 343248 Jun 28 06:23 /usr/bin/systemd-run
-rwxr-xr-x 1 root root 339152 Jun 28 06:23 /usr/bin/systemd-stdio-bridge
-rwxr-xr-x 1 root root 27776 Jun 26 15:37 /usr/bin/systemmonitor
-rwxr-xr-x 1 root root 124176 Jun 26 14:09 /usr/bin/systemsettings5
in cli --> systemadm
works no problem
Who else has systemadm in systemsettings5 ?
-
Hello Alf,
since my switch to kf5 and plasma5 with siduction I use sddm without any problems, same situation with Antergos, Manjaro and Netrunner. I've a german localised system and sddm also "speaks" german with me (http://forum.siduction.org/Smileys/default/smiley.gif)
Kind regards,
Holger
I too have no problems with sddm, since kdm is dead and has been for a while, never had it installed to begin with.
apt-get install sddm kde-config-sddm sddm-theme-breeze sddm-theme-circles sddm-theme-elarun sddm-theme-maldives sddm-theme-maui
Is all I did, no problems
Like I said on irc
"<piper> no problems at all with sddm, rebooted twice with each theme, 5 themes , now to customize it ;) "
-
All seems like pretty.
I've taken option "c". without a problem. ;D
Thank you all, who support this theme, especially santa.
sepps
-
@piper: sddm has improved in the last few month a lot - but is far from mature - to sum it up: if it works ok - it works ok - if not, bad luck. There are some corner cases i pointet out yesterday in irc, i see no movement in these bugs. Mostly these things are about language and keyboard settings, default values and missed functionality. All these things are in the bugtracker of sddm and need to be addressed - and the sddm team will address them sooner or later.
-
@piper: sddm has improved in the last few month a lot - but is far from mature - to sum it up: if it works ok - it works ok - if not, bad luck. There are some corner cases i pointet out yesterday in irc, i see no movement in these bugs. Mostly these things are about language and keyboard settings, default values and missed functionality. All these things are in the bugtracker of sddm and need to be addressed - and the sddm team will address them sooner or later.
I agree that it is not mature enough and that at this point in development is no way ready to be default by siduction
However :) (you knew that was coming) this is sid, for some of us, we like to try new things or to break things or perhaps both at the same time ;)
For some that have a sense of adventure and know that your system can unfold to not booting, cause you to drink, smoke, swear more than normal, shit, sddm might be for you, :)
-
Hi,
I have updated the installation instructions here:
https://community.kde.org/Plasma/InstallingNext#siduction (https://community.kde.org/Plasma/InstallingNext#siduction)
The instructions refer to sddm-kcm I found it as:
$ apt-cache search sddm
kde-config-sddm - KCM module for SDDM
Meanwhile, I couldn't get sddm to work. It would hang with a black screen after login. After ctrl f1 I entered dpkg-reconfigure sddm, and set it to kdm, then rebooted and it strangely went into sddm and worked. Then I did dpkg-reconfigure again and set it to sddm and it broke again. Then I set it to kdm and it was still broken. I uninstalled sddm and now I'm back in with kdm. Searching google, I could only find conflicting ideas of how to set the dm.
Then uninstalled kdm and had only sddm installed, but that didn't work either. Yet it did one time work so something must be stopping it from starting X. I tried deleting ~/.Xauthority. Does anyone know the steps involved in making sure the startup to sddm works?
I have updated sddm syncing with latest kubuntu's package, please re-test. Also the installation instructions were updated.
Thank you very much for the feedback.
-
I have updated sddm syncing with latest kubuntu's package, please re-test. Also the installation instructions were updated.
Thank you very much for the feedback.
Works great now! kdm has been purged. Thanks! It took a bit of work but I feel all fresh up to date and modern with my new KDE. I once compiled my own kdevelop and associated libraries, knowing what it took to do that, I can't imagine doing the whole KDE. Thanks!
-
Works great now! kdm has been purged. Thanks! It took a bit of work but I feel all fresh up to date and modern with my new KDE. I once compiled my own kdevelop and associated libraries, knowing what it took to do that, I can't imagine doing the whole KDE. Thanks!
Glad you got this solved :)
-
What a mess >:(
Nach dem DU von gestern laufen diverse Anwendung nicht mehr z.B. Icedove, Iceweasel nur über den Launcher, Korganizer ohne Kalender usw. usw.
Die Kontrolleiste ist leer.
Das Erscheinungsbild (Symbole usw. ) wie aus der Urzeit des PC anno 1980 !
bevo
-
What a mess >:(
Nach dem DU von gestern laufen diverse Anwendung nicht mehr...
Wie exakt bist Du denn der Anleitung aus dem ersten Post (https://community.kde.org/Plasma/InstallingNext#siduction) des Threads gefolgt? Nur kdenext aktiviert oder wie im Link vorgeschlagen auch kde-standard (re)installiert?
-
Nichts dergleichen >:(
Oh well
bevo
-
Hinsichtlich KDE geht es in Debian grade ziemlich rund (siehe auch hier (http://forum.siduction.org/index.php?topic=5650.msg46065#msg46065)). Da das Kind nunmal in den Brunnen gefallen ist gibt es eigentlich nur die Möglichkeit a) per Backup das System zurückzusetzen und kein D-U oder b) (bevorzugt) in den sources.list kdenext zu aktivieren und erneut zu aktualiseren. Die Grundsätzlich Stoßrichtung ist vorwärts, auch wenns grad knirscht, und zurzeit ist Upgrade-Warnings lesen (und D-U-output versuchen zu interpretieren) extrem empfohlen. :-\
{ Short summary of last posts for EN readers: dist-upgrade without kdenext rendered bevos system nearly unusable, advice is to either revert with a system-backup and hold off d-u or move forwards with kdenext. }
-
Ja, da habe ich geschlafen :-[
bevo
-
Dropbox syncs, but there is no icon in the tray and the notifier doesn't work.
There is a known issue (http://blog.martin-graesslin.com/blog/2014/06/where-are-my-systray-icons/) with the Plasma 5 panel, and quite a few packages can't park an icon or notifier on the panel. Radiotray is useless, for example, and skype will park a launcher, but the "signed in" and the other notifier icon of skype do not park, so you have to use the window menu to sign out. I would suppose the same problem is affecting dropbox. I followed the guidance on the blog to try to remediate the issue, but ..... :(
-
Dropbox syncs, but there is no icon in the tray and the notifier doesn't work.
I had this problem with synergy and claws mail and I have it solved. I'm sorry I'm busy now, I'll come back and describe in detail how I did it. There's a package in the repository wmsystemtray, together with window rules that can get it working. I managed to make the rules so that there's a little spot on the bottom of my screen where the icons go right next to my panel. It works great and doesn't look obtrusive.
-
Thanks vayu and dibl.
I'm in no hurry, the important part works, and since my first post the pop-up notification started working.
I read the upgrade instructions, and carefully made the changes. I had a phone call somewhere in there and managed to forget the part that read 'install kde-standard'. That made a bit of a difference in things, as you might imagine. :-[
-
Hi,
a few minutes ago the KDE Frameworks libraries were updated to 5.12, I don't expect them to break anything, but if you experience any issue let me know.
EDIT: Please dist-upgrade if possible outside a kde session, otherwise you might not be able to reboot.
-
All went smooth here ;)
-
+! So far.
One exception, the extra sddm themes (ie. circles,elarum,maldives, maui) are no longer available for selection in systemsettings > Workspace Theme > Splash Screen. Before the du I had to tinker with a file in ./config (can't remember which at the moment) to get them selectable so the du must have overwritten that file.
If I find anything else lI'll et you know. anyway thanks again Sant for making the transition relatively painless.
Edit: At logout the maui splash was available for login but it and the others weren't available in in systemsettings. So the config wasn't overwritten. So I guess there is a still a problem with systemsettings.
-
All good here. I had klipper running and I notice that klipper was replaced with the KDE clipboard. Certainly not an issue.
-
+! So far.
One exception, the extra sddm themes (ie. circles,elarum,maldives, maui) are no longer available for selection in systemsettings > Workspace Theme > Splash Screen. Before the du I had to tinker with a file in ./config (can't remember which at the moment) to get them selectable so the du must have overwritten that file.
If I find anything else lI'll et you know. anyway thanks again Sant for making the transition relatively painless.
Edit: At logout the maui splash was available for login but it and the others weren't available in in systemsettings. So the config wasn't overwritten. So I guess there is a still a problem with systemsettings.
No problem here --> systemsettings --> Startup and Shutdown
I never had to tinker with any config file ever.
(http://pipersid.net/myshit/linux/images/thumb-snapshot1.png) (http://pipersid.net/myshit/linux/images/snapshot1.png)
-
Thanks piper.
I was looking in the wrong place!
Alas enior moments are coming thick and fast these days.
-
Thanks piper.
I was looking in the wrong place!
Alas enior moments are coming thick and fast these days.
Yeah, 5 times for me in 10 minutes :)
-
With today's du, I have a dropbox icon residing in the tray, so that issue is resolved.
-
@ghstryder,
have you installed wmsystemtray as prerequisite for dropbox tray icon?
I do not see it in the tray on my machine :(
Greetings
Tom
-
I installed nautilus-dropbox. Other than that I have not done a thing specifically for dropbox.
-
@ghstryder,
have you installed wmsystemtray as prerequisite for dropbox tray icon?
I do not see it in the tray on my machine :(
Greetings
Tom
For dropbox to be working on ghstryder's system one of two things must have changed. Either dropbox updated it's system tray notification to the new style, or KDE updated to include the old style. I haven't experimented to see if my applications that require the old notification style are now working without wmsystemtray.
I'm using wmsystemtray for synergy and claws mail. When you run wmsystemtray, it will open as a regular window. Once it is running and open, then if you run a program with the old style sytemtray notifications, they will deposit their icon in the wmsystemtray window. That's how it works, they don't go in the task bar.
What you can do to make it more usable and convenient is use window rules in KDE systemsettings to make the window have no decorations or titles. You can make it have no focus, and you can make it smalll, and way in the corner next to your taskbar. I added a black background and a slight transparency as well, so against my dark desktop wallpaper it blends nicely next to the main taskbar. It looks and works very well.
(http://oneofthesevenbillion.com/web/wmsystemtray.jpg)
-
I also made a script to start it automatically. I named it startapps. It's in my home directory and has the properties set to executable.
#!/bin/bash
/usr/bin/wmsystemtray --non-wmaker --bgcolor black &
Then I put a file named startapps.desktop in my ~/.config/autostart directory.
[Desktop Entry]
Categories=Utility
Comment[en_US]=Start wmsystemtray synergy and knotes
Comment=Start wmsystemtray synergy and knotes
Exec=~/startapps
GenericName[en_US]=
GenericName=
Icon=application-atom+xml
MimeType=
Name[en_US]=Startapps
Name=Startapps
NoDisplay=false
Path=
StartupNotify=false
Terminal=false
TerminalOptions=
Type=Application
X-DBUS-ServiceName=
X-DBUS-StartupType=unique
X-KDE-SubstituteUID=false
X-KDE-Username=
Then in systemsettings under window rules, I created a new rule. I named it "settings for wmsystemtray" I used detect window properties to get many of these settings, then I tweaked them until I got what I wanted.
On the first tab Window matching;
Under Window class I have:
Exact match: wmsystemtray0 wmsystemtray
All the window types are selected.
Window title: Substring Match: wmsystemtray
On the second tab Size and Position:
Position: Force then I have an x,y coordinate appropriate for my screen size, for me on the 1920,180 screen to put it in the lower right corner as the photo shows is 1746,1051
Size: Force 170,29
Desktop has Force: All desktops
All else on that tab is left alone.
On the third tab Arrangement and Access I have:
Keep below, Force: Yes
Skip taskbar, Force: Yes
Skip Pager, Force: Yes
Skip switcher, Force: Yes
On the last tab Appearance & Fixes:
No titlebar and frame, Force: Yes
Active opacity, Force: 40%
Focus stealing prevention, Force: Extreme
Window type, Force: Normal Window
None of this is necessary if the latest KDE includes the old style taskbar notifications. If it doesn't or on a KDE that doesn't, I'm very happy with how this workaround works for me.
-
I just upgraded three systems using option 'C'. Worked without any real problems.
I do note a few small issues with the new plasma:
- startup time from login to desktop seems to be a little longer than before
- no way to make the clock in the panel display in 24-hour format
- it doesn't restore saved sessions properly, and if you have windows open on several desktops they all get restored to the first desktop.
-
I just upgraded three systems using option 'C'. Worked without any real problems.
I do note a few small issues with the new plasma:
- startup time from login to desktop seems to be a little longer than before
- no way to make the clock in the panel display in 24-hour format
- it doesn't restore saved sessions properly, and if you have windows open on several desktops they all get restored to the first desktop.
What does this show ?
apt-cache policy kde-standard
-
I have three problems (today DU):
(1) The session is not storred correctly, at next login all windows are are placed within the first virtual workspace rather than nicely spreaded over the different workspaces.
(2) kmix does not start:
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
(3)The volume switches to maximum after some activities, but can be decreased by alsamixer.
Any hints?
-
(2) kmix does not start:
I had this problem after the upgrade to 5.13. To solve it I copied /usr/share/applications/kmix.desktop to ~/.config/autostart
-
I installed kde-standard which pulls in a number of other kde apps. This seems to have fixed the problem with the long pause before it gets to the desktop when I first login. Desktop startup is quite snappy now.
(3)The volume switches to maximum after some activities, but can be decreased by alsamixer.
I also experience this. For example I go into regional settings/formats. Make a change. Click Apply and I get blasted by a beep. Set volume down to a reasonable level. Go back into formats make a change and click Apply. It sets volume back to 100% and blasts me again.
-
I just upgraded using method c. Now all my Icons in the taskbar are lost and HPLIB Status Service is yelling "No system tray dedected on this system. Unable to start, exiting".
-
I just upgraded using method c. Now all my Icons in the taskbar are lost and HPLIB Status Service is yelling "No system tray dedected on this system. Unable to start, exiting".
Do you have kde-standard installed? Did you try with a fresh user account?
-
HPLIB Status Service is yelling "No system tray dedected on this system. Unable to start, exiting".
What I posted above is the fix for the system tray problem.
-
I installed kde-standard which pulls in a number of other kde apps. This seems to have fixed the problem with the long pause before it gets to the desktop when I first login. Desktop startup is quite snappy now.
(3)The volume switches to maximum after some activities, but can be decreased by alsamixer.
I also experience this. For example I go into regional settings/formats. Make a change. Click Apply and I get blasted by a beep. Set volume down to a reasonable level. Go back into formats make a change and click Apply. It sets volume back to 100% and blasts me again.
Maybe this is the flat_volumes problem? :
http://forum.siduction.org/index.php?topic=5300.0
http://www.reddit.com/r/linux/comments/2rjiaa/horrible_decisions_flat_volumes_in_pulseaudio_a/
Ciao, Martin
-
Do you have kde-standard installed? Did you try with a fresh user account?
I have installed kde-full after d-u. I will check it with a new temporary account.
-
Thank you Horo!! My eardrums thank you as well. I had assumed the volume issue was new and would get fixed at some point. I never managed the right combination of search terms to see that post.
-
Setting "flat-volume=no" fixed the volume problem.
I'm finding that some aspects of plasma5 are less flexible and less user-friendly that before. For example, I like the time to display in 24-hour format. Previously it was very easy to set this. Now there is no straight-forward way to accomplish this. The only way, apparently, is to select "detailed settings" and set time to some particular country. So instead of 6 or 8 different choices there are 150 or so countries to choose from. A step backwards for sure.
If I set my time format choice to United Kingdom I get the 24-hour time format, but it also changes the calendar so that the week starts on Monday. There doesn't seem to be any way to just change the format for time.
-
Hello @hightime,
trying to change time format is annoying, I have similar issues with it.
But keep in mind that kf5 and plasma5 are under strong developement, I'm sure, that a lot of features, we had with KDE4, aren't canceled in new kf5, they aren't implemented yet.
Kind regards,
Holger