Opensuse 12.2 seemed like too much of a hybrid of old and new systems, such as systemd being introduced but only being used in parallel with the old sysvinit which retained control of many functions of the process. There are other examples of similar 'transitions' with multiple systems governing a single process.
Opensuse 12.3 will be most greatly appreciated if it completes this transition of these many new technologies leaving a stable and coherent base on which to build.
Chief amongst this bifurcated and inconsistent systems is package updating, specifically, the fact that suse has two largely separate systems for the process that conflict with each other:
This needs to be sorted out, leaving one coherent system to govern the package update process!
When the solution for this problem is being pondered it needs to weigh in the requirments of the new apper/appstream based opensuse app-store that really needs to finally arrive with 12.3:
Lots of fine work has been done to create the prerequisites of an opensuse app-store, not least of which was changes to packagekit i believe, now is the time to see the fruits of that labour.
With that said, other updates I like to see from opensuse 12.3 in march are; KDE 4.10, kernel 3.7, further Owncloud integration, and a green opensuse theme.
Looking forward to it.
Last edited by Jedibeeftrix; 11-09-2012 at 03:18 AM.
Hmm, a Software Center... Well, good luck with that. It would be worthless to me, but new users would definitely appreciate one. (Also, "App Store" is a poor name, as nothing is sold there, and also copyright.)
The problem isn't with packagekit, the problem is with Apper. Removing apper cures the issue. You do not have to uninstall Packagekit as there is nothing to call on it if you remove apper. If you have been with openSUSE long enough you should also remember that their various attempts at having a applet check updates and tie up the system extends well back for years and years and well before PackageKit was even implemented and as far back as 9.3 when they were using redcarpet.If you don't beleive me look at the huge number of threads on the forums, the bug trackers and the mailing lists!
Ok moderator go stick your head back in the Fedora kool-aide.
My computer is triple boot. Windows (for very rare occasions when I need it), then two linux installs (each has boot, root and var partitions).
Normally I snapshot one linux over the top of the other before I do a system upgrade of one version to the next. Trying to upgrade 12.1 to 12.2 ended up with a broken system, wouldn't boot and start everything up, and dependencies got into such a state I couldn't upgrade or downgrade. So I wiped that attempt clean and installed from scratch.
At the moment the first linux install is a fresh 12.2, and it tends to crash because of problems with the video driver - not only does it not suspend, it locks up solid. I can't control screen brightness either.
The second linux install is a mature 12.1+tumbleweed with a self-built optimised kernel, and is rock solid, and suspends and resumes perfectly. I can control screen brightness too. I selectively allow package upgrades as I don't want it to break, I only upgrade non-core stuff!
12.2 looks nicer, is further through the systemd transition, and has a lot of improvements, but I am disappointed in the suspend/resume problem, especially as 12.1 was problem free practically out of the box.
This cycle of good release, OK release and poor release seems typical of SuSE - things are just settling down when some sub-system is ripped out and a new one put in which doesn't fully work till the next major release. PulseAudio, I'm remembering you! KDE3.5 to 4, remember that? Plasmoid desktop stuff? This is why I now dual-boot.
At work the standard is fedora desktops and centos on the servers. I did a simple routine update on fedora and now X11 hangs. Fortunately that machine is dual boot, and the 2nd OS is osuse12.2 which is working OK. My boss probably thinks I am running Fedora with a green theme ;-)
I've seen systems presenting a login prompt without a login beeing possible unless you wait for 5 seconds until network authentification was working.
To me systemd is dead on arrival. A major regression to be removed from the system.
What's the use of a system that boots within 10 seconds but is only partially functional afterwards?