Please assist / test KDE upgrade for Tumbleweed

Here’s a quote from Greg k-h on the mailing list:

opensuse-factory] tumbleweed testing for KDE 4.6



I’ve got it all building finally, and it seems to work for me, with the
one exception of there not being any konqueror-plugins-lang package
being generated by anything in the KDE:Release:46 repo, so you can’t
update the konqueror-plugins package.

I’d appreciate some testers if at all possible before I push it to the
main Tumbleweed repository.

The repo is at:
openSUSE:Tumbleweed:KDE

Please test and let me know if it works or not for you.

thanks,

greg k-h

You would be helping if you trialled the upgrade and reported your results to the mailing list (or if you’re not list friendly, put your experiences in this thread). How to run/test the upgrade is in the next post. C’mon guys, be adventurous.

I added this repo:

http://download.opensuse.org/repositories/openSUSE:/Tumbleweed:/KDE/openSUSE_Tumbleweed/

Called it KDE_TW
Disabled all other repos except this test repo and Tumbleweed
and ran

zypper dup --from KDE_TW

you’ll get this dependency message:

Problem: konqueror-plugins-lang-4.3.1-11.14.2.noarch requires konqueror-plugins = 4.3.1, but this requirement cannot be provided
  deleted providers: konqueror-plugins-4.3.1-11.14.2.x86_64
 Solution 1: deinstallation of konqueror-plugins-lang-4.3.1-11.14.2.noarch
 Solution 2: keep obsolete konqueror-plugins-4.3.1-11.14.2.x86_64
 Solution 3: break konqueror-plugins-lang by ignoring some of its dependencies

I selected option 2 to keep (i.e. to not update) the Konqueror plugins

The upgrade went completely smoothly. Afterwards the DE was in disarray due to old KDE programs running so I rebooted. At the prompt I had to select the session to be KDE (plasma) and logged on easily. So far the KDE version (4.6.2 r1) is running very nicely.

Thanks for testing.

You shouldn’t have had to reboot, but a simple logout/login should have solved the
problem of running older libraries at the moment.

But anyway, glad it’s working for you, if there are no other problems reported in the
next few days, I’ll move it to the main Tumbleweed repo.

thanks,

greg k-h

Thanks… that would be an easy option…

On 04/16/2011 05:06 PM, gregkh wrote:
>
> You shouldn’t have had to reboot, but a simple logout/login should have
> solved the problem of running older libraries at the moment.

still a lot of folks around here with hard to break, old habits…


CAVEAT: http://is.gd/bpoMD
[NNTP via openSUSE 11.3 + KDE4.5.5 + Thunderbird3.1.8]
Q: Why do you upgrade?
A: Because the Gecko is always greener on the other side!
So said k428 in http://is.gd/Pwc3xq

I tried the logout/login method first. It commenced the KDE startup but then flipped back to the login screen again, then commenced KDE again, the flipped again, endless loop. So then I rebooted.

Hmmm… 0 points for tact on that one DD…

I only ran into one problem: after upgrading to Tumbleweed KDE, I logged out but could not login again. So I logged in once with the KDE failsafe option; after that I’ve had no problems.

I’m running 32-bit Tumbleweed in a VirtualBox VM. (on a Windows Vista laptop)

That’s very promising, good job.

I’ll test this in the morning.

Thanks for the hard work!

On 04/16/2011 10:06 PM, swerdna wrote:
>
> I tried the logout/login method first. It commenced the KDE startup but
> then flipped back to the login screen again, then commenced KDE again,
> the flipped again, endless loop. So then I rebooted.

there is a good clue for the bug hunters…and, i think more than one
is seeking the answer to the “login screen again” bug…

on your other rock (re tact): rebooting is an old habit and hard to
break, a recognition of fact which should not cause anyone to get their
feelings hurt…

and, with this post i see that more and more rebooting may come to be
needed here also…sigh.


CAVEAT: http://is.gd/bpoMD
[NNTP via openSUSE 11.3 + KDE4.5.5 + Thunderbird3.1.8]
Q: Why do you upgrade?
A: Because the Gecko is always greener on the other side!
So said k428 in http://is.gd/Pwc3xq

I can only enter desktop by using kde plasma workspace (failsafe) in the session type. All progs seem to be working OK. To me it looks no different from normal desktop.

Tumbleweed KDE 4.6.1 to 4.6.2 using new Tumbleweed KDE repo

Followed swerdna’s lead on the konq plugins option 2

89 packages to upgrade, 33 to downgrade, 122 to change vendor.

OS: Linux 2.6.38-18-desktop x86_64
Current user: patacer@ACER5251.site
System: openSUSE 11.4 (x86_64)
KDE: 4.6.2 (4.6.2) “release 1”

Reboot was required for Konq to report the new KDE

Restart from desktop and now have what seems to be a working 4.6.2 DE

I notice kpackagekit seems completely broken after this update.

Before it would open and look like it was working. I could change settings but when trying to update it would fail with the known proxy error.

Now kdesu kpackagekit gives an empty grey dialog window with only the ‘help’ and ‘defaults’ buttons at the bottom.

All my other regular apps seem to work fine:

firefox
thunderbird
wine
VMWare Workstation

By the time I finished my above post re kpackagekit an update icon appeared in the taskbar and kpackagekit report a slew of packages needing update.

I am updating them now.

Just more weird kpackagekit behavior!

I would not use KPackagekit with Tumbleweed because I feel a finer grained scrutiny is needed when updating Tumbleweed (just a personal opinion). I usually run “zypper dup -D etc” and if I see anything out of the ordinary with the proposal that zypper_dup makes, I switch to the Yast GUI and have a good look.

Now that you’ve made your first login and re-established the login session preference, are you back with the full session type or are you still stuck in using failsafe?

Re the rebooting (or re-login sees to be all that’s needed): re-logging/booting seems a small price to pay, do you think it really needs a bug report?

Re the tact: I’m cool, no problem.

Thanks for that advice :slight_smile:

On 04/19/2011 12:36 AM, swerdna wrote:
> Re the rebooting (or re-login sees to be all that’s needed):
> re-logging/booting seems a small price to pay, do you think it really
> needs a bug report?

yes…there are several threads in install/boot/login where folks have
faced the problem/symptom of logging in (on the green screen) and
moments later being presented with a new demand for log in…sometimes
it is a terminal login, sometimes another green screen log in…

i’ve not yet seen “the solution” to what i called (in my previous post)
“the ‘login screen again’ bug”…

the fact that you ‘fixed’ it with a reboot, while logout-login didn’t
might give the bug hunters a new place to look for a clue to fix.


CAVEAT: http://is.gd/bpoMD
[openSUSE 11.3 + KDE4.5.5 + Thunderbird3.1.8 via NNTP]
A Penguin Being Tickled - http://www.youtube.com/watch?v=0GILA0rrR6w