KDE 4.3 is now unmasked for amd64

[Veldrin]

Actually, Veldrin, now that you bring the subject up ... can you please outline that easy method to run SystemSettings ? There is no such trivial method in my custom installation, which is basically a kdebase-meta with some extra packages. root is not allowed to log in and there is no GUI for running system settings as root.

I am very curious how I (the user) am expected to do this. The way I did was to find the name of the binary, then try to run the app from a root login. This is a non-trivial operation, since the term "System Settings" is not represented in the file system, so it can only be found by some kind of heuristics.

Gentoo could easily help this by adding a "System-wide settings" button to the System menu.

//

GK gave you already my secondary version - run it by kdesu. (But to me, this is the ugly solution)

The alternative - or so i thought - was to use the good ole run as different user, that they reincorporated. To do that, open krunner, type the entire commnd (i.e systemsettings) and the hi the appearing wrench, check run an different user, and provide the required credentials.

The disadvantage of both variants, is that root access is required. (But so, is if you have the administrator button.)

cheers.
V.

[BlackEye]

How can I upgrade from 4.2 to 4.3 without too much trouble?
Do I need to manually download all the *-4.3 Files from http://git.overlays.gentoo.org/gitweb/? ... ree;f=sets ?
And afterwards manually keywording all the kde 4.3 stuff by my own?
Isn't there an easier step?

[bekkra]

Thanks for the ideas about running commands as root. I am familiar with several ways of doing my maintenance chores, but I see that I failed to make my point. The interesting user interaction problem is that what you see is not what you have.

KDE presents the settings as "System settings", but you cannot "run" this as root. Since the GUI lacks the quirks for doing this ( where even the Windows post-XP right-click-holding-modifier-and-get-the-run-as-option actually does the work ), the interesting point is that both of the solutions fail on the first critical point: the user must find the executable that is run to present the window named "System settings".

This problem is generic to most GUI systems as they all rely on file systems for storing executables, so that the file system limitations and conventions frame the module names. KDE could help this in several ways; I was looking for some idea about how we - the normal users - were imagined to find a suitable solution.

But thanks again guys, I have since chosen an even uglier solution. I collect the most often used maintenance stuff and set them up in sudo to be independant on the GUI. This is smooth and just as robust as the entire sudo stuff is.

//

[joefish]

Hi Blackeye,

Here's what worked for me:

Assuming you used sets to install 4.2, then:
- Go to that link you have there, and where it says "snapshot" up the top, download one of the compressed files there. It'll have all the sets directories in it, without having to download them all individually.
- Uncompress that into your sets directory (/etc/portage/sets)
- Download the keywords file - wget -O /etc/portage/package.keywords/kde-4.3 'http://git.overlays.gentoo.org/gitweb/? ... 3.keywords' (this command works if you have a package.keywords directory; you could also download the file then add it's contents to your keyword file if you're using that method).
- Install kde from sets like you normally would. i.e 'emerge @kde/kdebase-4.3' etc. Portage will figure out that 4.2 needs to be removed (at least it did for me. I'm not using the -kdeprefix flag).

Hope that helps.

Edit: See also some tips here - http://www.linuxized.com/2009/08/kde-4- ... ade-guide/

[d2_racing]

I am genuinely impressed. The update installed 116 packages and uninstalled quite a few on my system. Everything merged without the slightest glitch.

Nice work, KDE team, really well done !

//

Me too, 4 hours later and I'm running Kde 4.3.0 at work

[BlackEye]

Hi joefish,

thanks a lot for your help! This was really helpful for me. I'll start to upgrade to 4.3 now

PS: I've megatons of

Code: Select all

  ('ebuild', '/', 'kde-base/kdebase-kioslaves-4.3.0', 'merge') pulled in by
    kde-base/kdebase-kioslaves:4.3 required by @kdebase-4.3
    >=kde-base/kdebase-kioslaves-4.3.0:4.3[-kdeprefix] required by ('ebuild', '/', 'kde-base/kdebase-startkde-4.3.0', 'merge')
    >=kde-base/kdebase-kioslaves-4.3.0:4.3[-kdeprefix] required by ('ebuild', '/', 'kde-base/konqueror-4.3.0-r1', 'merge')

  ('installed', '/', 'kde-base/kioclient-4.2.4', 'nomerge') pulled in by
    kde-base/kioclient:4.2 required by @world
    >=kde-base/kioclient-4.2.4:4.2[-kdeprefix] required by ('installed', '/', 'kde-base/plasma-workspace-4.2.4', 'nomerge')

  ('installed', '/', 'kde-base/solid-4.2.4', 'nomerge') pulled in by
    kde-base/solid:4.2 required by @world
    >=kde-base/solid-4.2.4:4.2[-kdeprefix] required by ('installed', '/', 'kde-base/powerdevil-4.2.4', 'nomerge')
    >=kde-base/solid-4.2.4:4.2[-kdeprefix] required by ('installed', '/', 'kde-base/ksmserver-4.2.4', 'nomerge')
    (and 2 more)

  ('installed', '/', 'kde-base/soliduiserver-4.2.4', 'nomerge') pulled in by
    >=kde-base/soliduiserver-4.2.4:4.2[-kdeprefix] required by ('installed', '/', 'kde-base/plasma-workspace-4.2.4', 'nomerge')
    kde-base/soliduiserver:4.2 required by @world

  ('installed', '/', 'kde-base/kdedglobalaccel-4.2.4', 'nomerge') pulled in by
    kde-base/kdedglobalaccel:4.2 required by @world
    >=kde-base/kdedglobalaccel-4.2.4:4.2[-kdeprefix] required by ('installed', '/', 'kde-base/kdebase-startkde-4.2.4', 'nomerge')

... man

PS: My Problem is, that I emerged @kdepackage-4.2 the last time. I need to remove these packages from world_sets and then simply emerge @kdebase and such...

[Gh0str1d3r]

another trick is to rightclick the K-menu button, K-menu editor and there copy the systemsettings link and edit "advanced -> run as" root.

Of course, it works with kdesu systemsettings, but with krunner it does not work for me. And furthermore, you have to type the whole word without tab autocomplete to get the tool wrench. So as said before, if kde should address gui-only computer noobs, it should have a button for it.

[EasterParade]

we unmasked it for amd64

KDE-4.3 unmasked? Are you sure? It isn' t unmasked here, synced only yesterday.
It' s in portage alright but not unmasked.

[d2_racing]

Are you running inside the ~arch or you use /etc/portage/package.keywords ?

[smurfer]

Hello,

I had the same question. What about kdelibs and some others on packages.gentoo.org?

Bye smurfer

[EasterParade]

Are you running inside the ~arch or you use /etc/portage/package.keywords ?

d2_racing, I have a kde keywords file in /etc/portage/package.keywords directory. But even without it , meaning
before I` ve put it in there, portage let me emerge phonon as a new aquisition.
I`m running 3.5.10 at the moment but try to maintain generally stable if possible.

[d2_racing]

Ok I see, because I'm running with a ~amd64 box and I'm running Kde 4.3.0 right now, so maybe your /etc/portage/package.keywords need a little tweak.

[scoop_yo]

Hi, up to now I have kde 4.2 and used the meta packages method to install it.
I don't use kdeprefix.

Today, I did

emerge --sync && emerge --metadata
and replace kde 4.2 keywords with today's package.keywords
for kde 4.3 in my /etc/portage/package.keywords.

Problem is, that when I try to emerge the 4.3 meta I get the error
that all the 4.2.4 packages are blocking the 4.3 ones. (the Block messages are in red )
Also all the 4.3 packages seem to want to go to a new slot!

How can I avoid the new slot collision and cleanly upgrade from the 4.2
to 4.3 ? Should I uninstall the 4.2 kde meta ?
Even if i remove the 4.2 info from the var/lib/portage/world file
I still get the new slot for kde 4.3 meta packages but now the block messages are
in blue, which makes them easy to resolve I think.

Any ideas ? I didn't find a solution in the docs or this topic (..meaning that I did a bit of search first )


PS: Before I did all the above changes still with kde 4.2 to my package.keywords
portage was complaining with red Blocking message that 4.2.4 is blocking kde 4.3
I guess I am missing something here.
My gentoo installation is about a month old, pretty fresh I'd say

[EasterParade]

@scoop_yo

Even if i remove the 4.2 info from the var/lib/portage/world file
I still get the new slot for kde 4.3 meta packages but now the block messages are
in blue, which makes them easy to resolve I think.

Looks good as blue blocks resolve themselves or rather portage does it.
That's how I understand this passage in the upgrade guide:

Upgrade Troubleshooting

If you’re trying to upgrade from KDE 4.2, but portage gives you nice little blocks, there are a few things you can check:

* Make sure you’ve synced the tree and/or kde-testing overlay (if using it)
* Make sure the unmask/keyword files are correct and up-to-date
* Check that you don’t have any 4.2 versioned kde-base/* items in /var/lib/portage/world
* Check that you don’t have any 4.2 versioned sets in /var/lib/portage/world_sets
* emerge -avDuN world — you’ll probably get some messy output but all blocks should be automatically resolved

@d2_racing
I did tweak my package.keywords and had to add qca-2.0.2; which one of the three masked versions suggested by
portage should be used? The most recent?
And about kdelibs already mentioned by smurfer: looks like I have to add kdelibs-4.3.0 to it as well. My now running emerge of kde-4.3 emerged kdelibs-3.5.10-r6.

EDIT I just witness the emerge of kdelibs-4.3.0 although kdelibs-3.5.10-r6 compiled a few minutes ago. Something messy here?

[scoop_yo]

@scoop_yo

Even if i remove the 4.2 info from the var/lib/portage/world file
I still get the new slot for kde 4.3 meta packages but now the block messages are
in blue, which makes them easy to resolve I think.

Looks good as blue blocks resolve themselves or rather portage does it.
That's how I understand this passage in the upgrade guide:

Upgrade Troubleshooting

If you’re trying to upgrade from KDE 4.2, but portage gives you nice little blocks, there are a few things you can check:

* Make sure you’ve synced the tree and/or kde-testing overlay (if using it)
* Make sure the unmask/keyword files are correct and up-to-date
* Check that you don’t have any 4.2 versioned kde-base/* items in /var/lib/portage/world
* Check that you don’t have any 4.2 versioned sets in /var/lib/portage/world_sets
* emerge -avDuN world — you’ll probably get some messy output but all blocks should be automatically resolved

It isn't so clear in the docs, but should I manually edit /var/lib/portage/world
and delete all the 4.2 kde-base/* ? In my case it's only kde-base/kde-meta:4.2
So my best guess is that

* Check that you don’t have any 4.2 versioned kde-base/* items in /var/lib/portage/world

doesn't mean that I should unmerge kde-base/kde-meta:4.2 but rather delete the appropriate line in world
and portage will somehow replace it with 4.3 version, right ?

I could try it before I ask but there are a lot of packages that need to be emerged and for
that I wouldn't like to make any errors and emerge kde again. It really takes a lot of time

[EasterParade]

scoop_yo, a lot of real experts are running around here and I am not one of' em but I`d guess

doesn't mean that I should unmerge kde-base/kde-meta:4.2 but rather delete the appropriate line in world
and portage will somehow replace it with 4.3 version, right ?

that you are right on track with this. Should be fine.

What I often do when I am not 100% sure is trial and error on the interpretation I give to what a howto
or guide suggests and in this case I am pretty certain you can trust your assumption.

Congrats to your new install and good luck.

[EasterParade]

Compile went through just fine but I cannot start kde4.

Code: Select all

$DISPLAY not set or cannot connect to X server

What could cause it?
Do I have to use xdm and kdm? Never did it before and just doesn' t want it.
Should I delete the old .kde and .kde3 directories in home? There is a .kde4 directory, empty.

EDIT: I don' t want to put another post from me in here. You know, I' ve honestly not believed that I would need a
.xinitrc file for the kde-user. I have another user on the system running E17. That one' s got a .xinitrc. Up to now
the kde-user never needed one.
Everything works fine, kde starts and now I go exploring. Thanks and sorry for all those silly questions.

[devsk]

Does the upgrade from 4.2 to 4.3 work without problems?
Does it migrate my 4.2 settings? O do I need to wipe ~/.kde4[.2]?

That's the only thing keeping me away from it. The pain of setting everything up to my liking after I move to 4.3.

[pdw_hu]

Does the upgrade from 4.2 to 4.3 work without problems?
Does it migrate my 4.2 settings? O do I need to wipe ~/.kde4[.2]?

That's the only thing keeping me away from it. The pain of setting everything up to my liking after I move to 4.3.

1. Did for me.
2. Did for me.

:)

[EasterParade]

Kde-4.3 is running here and doing fine.
There are some things that don' t work as expected
but I am still exploring. I know kde-3.5, have used it for years and this is a totally different look and feel.
And some packages have been left over from 3.5.10 that have drawn in kdelibs-3.5.10 which I should get
rid of, mostly things that kde4 doesn' t have at all or yet.

Additionally there are use-flags and packages in package.use that seem obsolete for kde4.
But I am not sure about what I could throw out and what I should leave unmolested.

Now where do I post questions dealing with a working installation? I don' t want to force
them on this thread.

Good luck to all those who are about to migrate to kde4!

[devsk]

Does the upgrade from 4.2 to 4.3 work without problems?
Does it migrate my 4.2 settings? O do I need to wipe ~/.kde4[.2]?

That's the only thing keeping me away from it. The pain of setting everything up to my liking after I move to 4.3.

1. Did for me.
2. Did for me.

Did you 'emerge' update while logged in KDE or did you do it from console? That has worked in the past but with 4.3 going on top of 4.2 and package removal etc. going on, I am not sure if desktop will continue to function or cause some corruption in some settings.

[cjubon]

Also the Gentoo KDE Guide is properly updated

Just found out that the link "grab them as a tar.bz2 archive" in the first paragraph of section "Using sets" is still the old one.

Thanks for all the work! kde-4.3 hit the tree for x86 today !

[tampakrap]

Also the Gentoo KDE Guide is properly updated

Just found out that the link "grab them as a tar.bz2 archive" in the first paragraph of section "Using sets" is still the old one.

Thanks for all the work! kde-4.3 hit the tree for x86 today !

My nickname is with a K like KDE

[devsk]

Also the Gentoo KDE Guide is properly updated

Just found out that the link "grab them as a tar.bz2 archive" in the first paragraph of section "Using sets" is still the old one.

Thanks for all the work! kde-4.3 hit the tree for x86 today !

My nickname is with a K like KDE

LOL....he really made it crap... This is perfect! ROFLMAO...

[cjubon]

Sorry