I’ve been using opensuse 12.1 for a good while, and really like it, but would now like to try the stable version of 12.2. The last time, when I installed 12.1, I used the live rpm CD for 64-bit systems with KDE to install. Now the installation page shows only the DVD and some add-ons. Will the DVD boot live? Does it have the option of which desktop to use? Or is there a LiveCD version with just the KDE on it? Thanks for any help.
George aka MoeNeigh
**See: **software.opensuse.org: Download openSUSE 12.2. Looks like you can select 64-bit for the KDE live CD.
On 02/21/2013 08:16 PM, MoeNeigh wrote:
>
> I’ve been using opensuse 12.1 for a good while, and really like it, but
> would now like to try the stable version of 12.2. The last time, when I
> installed 12.1, I used the live rpm CD for 64-bit systems with KDE to
> install. Now the installation page shows only the DVD and some add-ons.
> Will the DVD boot live? Does it have the option of which desktop to use?
> Or is there a LiveCD version with just the KDE on it? Thanks for any
> help.
there are three recommended/approved methods of moving from 12.1 to 12.2:
http://tinyurl.com/35p966c
http://tinyurl.com/93uemsr
http://tinyurl.com/7l4m2td
only the last of those three require an install DVD, the first two do
not require any kind of install media…
the download page for openSUSE 12.2 is here:
http://software.opensuse.org/
it includes exactly the same possibilities of DVD or Live CDs as were
available for 12.1
the DVD will not boot to a live session…
in all of those three methods you can read that upgrades are not
guaranteed to be successful, back up first.
–
dd
openSUSE®, the “German Engineered Automobile” of operating systems!
http://tinyurl.com/DD-Caveat
Thanks for that info. I see the KDE option is for the operating system with kde destop. At first, I thought it was some kind of add-on.
Hi!
Just an idea: why don’t you wait just a couple of weeks longer and then install 12.3 ?
Good luck
Mike
On 2013-02-21 21:26, ratzi wrote:
> Hi!
>
> Just an idea: why don’t you wait just a couple of weeks longer and then
> install 12.3 ?
Because now 12.2 is stable and cozy, most problems ironed out after
months of reports, and 12.3 is not? :-p
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
I just tried the LiveCD of 12.2 for a little bit, and found that old problem of kpackagekit trying to interfere with software management. I can’t remember how I got past that, but I now just use a terminal and check by using “zypper up” twice a week for updates. If I wish to continue doing the same in 12.2, how do I get past kpackagekit? I don’t use apper either. I kept getting some unnecessary update notification that wouldn’t stop appearing using apper.
I see here in 12.1 in software management that both apper and packagekit are checked as installed. So they are still there, but they don’t bother me when I update using zypper. Still, I can’t for the life of me remember how I was able to stop interference from packagekit and apper.
So are they (kpackagekit and apper) still a problem in 12.2?
On 02/21/2013 03:06 PM, MoeNeigh wrote:
>
> I just tried the LiveCD of 12.2 for a little bit, and found that old
> problem of kpackagekit trying to interfere with software management. I
> can’t remember how I got past that, but I now just use a terminal and
> check by using “zypper up” twice a week for updates. If I wish to
> continue doing the same in 12.2, how do I get past kpackagekit? I don’t
> use apper either. I kept getting some unnecessary update notification
> that wouldn’t stop appearing using apper.
>
> I see here in 12.1 in software management that both apper and
> packagekit are checked as installed. So they are still there, but they
> don’t bother me when I update using zypper. Still, I can’t for the life
> of me remember how I was able to stop interference from packagekit and
> apper.
>
> So are they (kpackagekit and apper) still a problem in 12.2?
My experience is that under 12.2, kpackagekit quit when zypper asked it to. If
you find a problem, uninstall the offendors.
lwfinger, Thanks. Hopefully, just continuing to use zypper will solve the problem.
To get rid of apper and packagekit stuff just do:
zypper rm apper
zypper rm *packagekit*
The PackageKit-blocking-zypper issue seems to be solved or less annoying in forthcoming 12.3. I’ve not noticed in 12.3 RC1 such a rubbish as in 12.2.
However, I will always delete apper/packagekit in future versions. All I need is zypper.
Apper /packagekit works well on 12.2, it didn’t on 12.1. Apper provides a notifier, and convenient updater if you want it. I recently did a new install of 12.2 from liveCD. I found the easiest way to proceed from the liveCD desktop, immediately it is ready with network connected, hit the install icon before Apper/packagekit starts (to notify of updates). Then just ignore KDE notifier telling you its blocked (by YaST installer).
Once the installer finishes after its reboot, there will be many packages waiting to be installed to complete the installation. Go to YaST > Software Management > Installation Summary and Accept to get those packages installed. After that, you will need to update the system. Be prepared for a big download, including KDE to 4.8.5, and many others patches/updates.
One other thing I noticed today when I tried to play audio requiring AAC 4 codec. With Apper/Packagekit installed, not only did it offer to find it, but actually succeeded in finding all the right gstreamer plugins and dependencies, and installed them. The audio worked. That’s the first time I’ve ever seen that offer complete successfully on openSUSE (with Packman repo enabled of course). 
That happens after a new install. But then it doesn’t happen again for a month. So it is not that big a problem.
What I do, is go to:
“Configure Desktop” → “Startup and Shutdown” → “Service Manager”
and I uncheck the box for “Apper” so that it never automatically starts. I use Yast online updates for updating. And I periodically run “zypper up” for other updates (mostly from packman).
That avoids the problem of packagekit blocking Yast.
My recent new install of 12.2 didn’t have any problem like that, including the original long running initialization (packagekit’s) that caused trouble for some early users.
Probably due to immediate use of YaST to complete the installation, and even swifter use of Online Update to install the package management fixes, and then all the rest. After that no issues, except after a day or two for KDE (4.8.5) desktop start failure, requiring deletion of .kde4 hidden directory to recover.