Announcement

**claydoh** · Jan 04, 2016, 07:34 PM

the -ci ppas are taking stuff directly from raw untested KDE git, and as such they do get stuffed up at times, let alone that things are always changing. And Wayland support is very very early for plasma to begin with. It is very likely that some update to X package breaks or needs an updated Y, but Y hasn't been built or is still waiting in a queue, or waiting for Z, lol

You are kinda on your own here, as what you are seeing is rather to be expected. There are no other ppas to add that will make it "better"

And then I looked more at your sources list......

why do you mix Xenial and Wily and Vivid ppa repos

This likely, most likely to break stuff than using the kubuntu-ci ppa. If you used the add-apt-repository command to add ppas, this sort of thing would not happen.

I don't think I have ever seen so many ppas used on one system, one that runs with any sort of reliability. Did you add *all* of them, lol!

**claydoh** · Jan 04, 2016, 08:09 PM

Jeebus! You have added them all!!!!

?!!!!!

!!!!

??!!!!!

Did you even read anything about what each ppa is for?
What are your goals, specific to KDE (I cannot comment much on the other repos you have added)

I would seriously consider starting over. Seriously.

Use the add-apt-repository tool to add ppas, which will make sure you are not mixing *bunut versions.

For Kubuntu Vivid and forward:
kubuntu-backports
gets you the latest Plasma, Applications, and Frameworks that we have available. This is what 99.5% of users need. We get updated versions after they are built for the next, in-development Kubuntu version.

The kubuntu-ci repos are for developers and the braver users who want to try out the latest, freshest, unpasteurized, un-homogenized milk, directly from the cow's teats. You need one, either of the stable of unstable branches. But only one. This is likely why you have the symbols errors in your OP - the different packages and versions from each branch are competing with each other, and that doesn't even account for competing *buntu version packages.

You don't need any others. Especially the staging ppas, as these are holding places where packages are incomplete, and move to their proper ppa when finished.

read each ppa's page before adding them, so you can see any warnings or descriptions. the add-apt-repository tool will also show you these before it proceeds.

Yes, we have too many kubuntu ppas all lumped together.

**SimonAndric** · Jan 05, 2016, 06:34 PM

Hello!

First thank you for your replies

amm... so it prob a packaging issue, which will be resolved with the next update. ihope

Am...and second...well..i thought im doing it the right way...i never read anywhere (but its also true, that never really checked), that using vivid/precise/wily/xenial,... is that much bad --- because, i thought, the system always goes to install the newet packages..it means, the newest are probably in xenial ---unless if the author of certain PPA's newest "distribution" is less than xenial. And dw, my plasma 5 is for "playing around" i have my kubuntu trusty which is "trusty only". I wish all the PPA's im using whad their packages in xenial, but they dont, and if i want for example the newest inkscape or the newest qcad or the newest vlc, rtc ..i have no other choice but to add, the "newest" distribution that PPa supports,..ist that true.... and if not, why kubuntu/linux allows such behaviour at all (to not ot put restrictions of such behaviour). You have to know i migrated to kubuntu from my win_xp 6 yrs ago (my first was karmic koala), and ive been doing it like this from the beginning... whenever the system went, i started from scratch - first year it was around 20-30 of those,..last year "just" 3 or 4...so i guess im improving

but now i have a question --- all the time i have to go to "ppa.launchpad.net/..." to see for each of the the PPA's separately, if they are already "xenial" or not... so then i can by hand update it in my sources.list... is there a way, that this would happen automatically... when PPA becomes more new, it automaticalyl becomes changed in my sources.list --- and sometimes the author of certain PPA also changes the name of their PPA --- again all of a sudden some place becomes unavailable, and some new PPA folder is created...

i just wanted the newest stuff... newest plasma5, newest graphic drivers, newest linux packages, newest apps...

ps. about "kubuntu-ci" PPA -- the most updates are coming from that one... i have the whole repo in xenial and then again in wily... so when some fPPA folder goest to xenial, it will sample the newest stuff from there, --- otherwise, i might have missed when the PPA folder migrated to xenial and im still getting old packages....

i hope i could explain why i have a such sources.list... but if i can as to make it more organized and still get "the nnewest stuff" and also use the program "add-apt-repository" which, if i can be honest i never used,... because i thought is easier to copy/paste the deb and deb-src in sources.list and then run "launchpad-getkeys" app to get GPG keys automatically.... but agian... there is so much things i dont know... and i know,...my way is not exactly the "mainstream" way... and therefore is wrong.. please help me to go to the right way

nice day
and thank you

Simon

**SimonAndric** · Jan 05, 2016, 06:38 PM

i also appologize for that many typos .... i wanted to repair them, then my session became logged out (very fast it becames logged out...much faster than for example bugs.kde.org) i had to log back in, and in the confusion (because at first i thought i lost all this big writing) i already submitted it... i hope still you can read & understand it..somehow...

sorry

Simon

**Qqmike** · Jan 05, 2016, 06:40 PM

then my session became logged out (very fast it becames logged out.

When you log in, under your user name there is a check box that says Remember Me. If you check that box, you should be OK and not be logged out so fast.

**claydoh** · Jan 05, 2016, 07:41 PM

it is not likely a packaging issue - it is the fact that you are running, in this case, fresh, raw,untested, unreleased code coming from multiple -ci repos that are updated independently, where one may have changes that the other(s) do not get, or have different version names, as that is based on the date/time of the build. Consider kubuntu-ci pre-pre-pre-alpha versions of KDE's software.

Vivid, Wily, Xenial are not 100% compatible as each one will have differing underlying systems, such as Qt libraries and the like, and also can and will have often vastly differing sets of dependencies due to this. Apt does not really know or care about which release you are running. You probably have been simply lucky because one -ci repo contains the most dominant Plasma versions and the dependency differences in Plamsa between 15.10 and 16.04 are relatively small currently.

Do note that the -ci repos do NOT contain release versions of Plasma, they are pulls directly form the working development git and automatically packaged, and are updated at least daily, so yes, you are going to have the most updates from these, and frequent bugs on top of breakages when packages fail to build due to the constant changes in the code.

If you want the latest, official plasma version that Kubuntu has released, the kubuntu-backports is where you will get it.

If you want the bleeding edge, always in flux, often not working, unreleased code, then pick ONE of the kubntu-ci repos. ONE. And there can be no real support for this due to the fluidity of the code

That's all you need. Nothing else.

And make sure you use nothing other than your actual kubuntu version. Sure, not all ppa owners have repos set up for Xenial - many people don't add them until very near or after the official release, and sometimes they are not needed immediately. Most ppas are run by individuals, who may not have the need, desire, or time to update things as much as people might want.

I heartily recommend using the add-apt-repository tool over manually editing your sources.list, as not only does it automatically set the ppa to your *buntu version, it also keeps each one in it's own file located in /etc/apt/sources.list.d
This also allows the usage of the ppa-purge tool, and allows for safer upgrades when a new *buntu is released, as it disables the ppas found in that directory during the process.

**claydoh** · Jan 05, 2016, 07:44 PM

Originally posted by SimonAndric View Post

i also appologize for that many typos .... i wanted to repair them, then my session became logged out (very fast it becames logged out...much faster than for example bugs.kde.org) i had to log back in, and in the confusion (because at first i thought i lost all this big writing) i already submitted it... i hope still you can read & understand it..somehow...

sorry

Simon

You're fine

Look at my rambling above lol!

Announcement

Sometimes after updating my kwin_x11 nor kwin_wayland doesnt want to start

[PLASMA 5] Sometimes after updating my kwin_x11 nor kwin_wayland doesnt want to start

Comment

Comment

Comment

Comment

Comment

Comment

Comment