Language Selection

English French German Italian Portuguese Spanish

openSUSE 10.2 Alpha 3 Report

Filed under
Reviews
SUSE
-s

Well, openSUSE 10.2 Alpha 3 is in our midst and Tuxmachines is here to keep you posted. This release we tested both an upgrade and a fresh install. We found this to be a very interesting release to say the least. It's an alpha to be sure to say the most.

Ok, let's expand on the most. My first interest was in the upgrade procedure - would it complete and provide an equal system to a fresh install? Then one has to decide to update from outside the system through the installer or from within the system with yast2 software manager (system update). Since I had had some questions from users concerning the update feature, I decided to test that method. So from my alpha2 install I defined my new alpha 3 repository and let the system update. The online update didn't show any updates until about 1/2 way through the update through the software manager. The software manager found over 300 packages to update and afterwards, the online update still found 13 more. After all the updates installed with no errors and a reboot, I discovered that didn't work out real well. X wouldn't start at all and yast2 at the commandline seg faulted. There had been some dependency issues and I was asked how to handle them. I used my best judgement, but perhaps this could have contributed to the failure. I decided not to waste much more time here and to test a fresh install.

There were some changes in the installer. I'd forgotten to check the most annoying bugs list before testing, but the graphical installer was working. You might recall my mentioning the new boot screen last report, and it is still that close-up photo of a lizard. The first new element spotted was at the license agreement screen. On the "you know this is beta and we aren't responsible yadda yadda" screen, the new naming convention is apparent. This release was officially tagged as openSUSE 10.1.1 Alpha 3.

There were the now familiar Validation Check Failure errors when the setup system began to start. It also complained about No Checksum Found for every setup file it loaded. Checking "don't show this screen again" checkbox didn't have the desire effect and I had to agree to each and file individually. Thank goodness it was only about a dozen or so of them. I hoped this wouldn't happen on each and every package we were going to install.

The software package selection section has changed this release. Instead of the previous selections categories, we now have "patterns." Similar in nature, but extremely slimmed down, this might make the install a faster process, but it results in a much smaller system. You can still go into the time-consuming Package Groups to choose all your favorites and must-haves such as the kernel-source, but by default we now see a scaled-down setup similar to the following:

  • Base Technologies

    • openSUSE Base System

    • Novell AppArmor
  • Graphical Environments
    • Gnome Desktop Environment

    • KDE Desktop Environment
    • X Window System
  • Primary Functions
    • Graphics (contains only gimp)

    • Gnome Graphics (ex.: eog and f-spot)
    • KDE Graphics (ex.: gimp, kdegraphics-kamera, and gwenview)
    • Print Server (ex.: cups and samba)
    • DHCP and DNS Server
  • Development
    • Basis Development (ex.: gcc, cvs, automake, and ncurses)

    • C/C++ Development (ex.: electricfence, boost, and ltrace)

This yielded a system size less than half of my past SUSE Linux installs. Looking on the good side, it does combat the accusation of being "bloated." This step finished par for the course and we were soon ready for the final configurations.

Hostname, root password, and network configurations are as we remember. Testing the network connection returned a success while the online update setup failed. Next came Users, clean-up, and Release Notes. The Release Notes contained no information.

Backing up to the bootloader configuration for a minute, I had someone ask about auto-detection of other Linux system by the installer. You can about surmize the Linux systems installed on my machine by taking a look at the original content list. I have 22 different various Linux and BSD-clone installs including SLED 10r3 and a couple of older SUSE installs on hdb. The openSUSE bootloader configuration detected four of them. It found Kate OS 3.0b1 which it identified as Debian, Kate OS 3.0 which it identified as Ubuntu, DreamLinux 2.0 which it called Ubuntu, and PCLOS .93a which it called Linux. I don't usually let new systems install a bootloader, and as such makes little difference to me. I just thought this was a bit interesting and worth mentioning. It's possible that the DreamLinux kernel could identify itself as Ubuntu, but I doubt very seriously that the Kate OS developers base anything on Debian or Ubuntu.

Next was the final hardware configuration. This step has either changed some or was having problems. I was used to a long list of hardware to adjust or accept including things such as graphics, tv card, and sound, but this time it only detected and offered my printer and sound. Finishing up the install it started the installed system and X.

Here's where things got real interesting. I have to draw the parallel between some of the "bugs" found in openSUSE as also found in Mandriva 2007 Beta 1. Many if not all of the same X bugs I complained about in my article on Mandriva were also found in openSUSE 10.2 alpha 3. The ugly fonts were present in both, sluggish performance under vesa, and excessive cpu usage wer found in both. openSUSE added limited screen resolution and no nv support. I say no nv support because although I edited my xorg.conf file by hand to make the change to nv, my changes were ignored. I couldn't try to configure X by yast as I was stuck in this "we need to install xorg-x11-server-glx" loop. I suspect this is all related to using Xorg 7.1.1 (7.1.99.2). I did a quick check for Xorg bugs relating to these issues, but all I found were nvidia proprietary driver listings. I might do a more thorough search later. As slow as Xorg moves, I fear continuing problems throughout the 10.2 lifespan for nvidia card users. Hopefully it's just one or two specific chipsets.

    

The next issue cropped up when I wanted to take screenshots of the new wallpaper. This release brings a lovely variation on the blue wispy wallpapers we've seen in (open)SUSE lately. Did I mention the new KDE starting splash? This too is new this release. It's a really nice royal blue background with the a new openSUSE logo.


There was no ksnapshot in the menu. Knowing I had a scaled-down install, my first instinct was to fire-up yast2 and look for missing KDE packages. But whoops, my root password wouldn't work - several times. I found I could sudo /sbin/yast2 and get the ascii version, but not until after sudo passwd and discovering my password rememberance wasn't the problem.

The graphical yast2 would start from the commandline as well. The software manager in Yast itself seems to be functioning pretty good this release. I couldn't find a scanner config under Hardware and discovered I had to install Yast-scanner. Come on, really. That should not be one of the "extras." However, after install of said package, scanner detection and operation was as desired.

        

In attempting to test Gnome, I found no option for it in the login manager. Using console login, it could be started from the command prompt. Upon start I got two errors. One was "There was an error starting the GNOME Settings Daemon" and "Power Manager did not start." But otherwise we find Gnome 2.12.2 with the signature customized SUSE Gnome menu system.

        

On the desktop we discover that the Firefox icon is inoperative. Trying to start Firefox at the commandline we find out that it's seg faulting.

Some RPM version highlights this release include:

  • OpenOffice_org-2.0.3-3

  • MozillaFirefox-1.5.0.6-2
  • xorg-x11-7.1-11
  • kdebase3-3.5.4-3
  • gnome-desktop-2.12.2-26
  • kernel-source-2.6.18_rc4-2
  • gcc-4.1.3-3
  • Full RPMList


Some Changelog highlights can include:

++++ bitstream-vera:

- install into /usr/share/fonts/truetype

++++ xorg-x11-Xvnc:

- created package

++++ coreutils:

- Move sux to %{_bindir}.

++++ dejavu:

- BuildRequires: xorg-x11-devel is necessary to detect Xorg X11R7.

++++ filesystem:

- Add /usr/share/fonts and remove /usr/X11R6/lib/X11/fonts

++++ kernel-default:

- patches.fixes/kbuild-fix-external-module: kbuild fixes for
2.6.18.
- rpm/kernel-source.spec.in: don't remove include/config/*
for building external modules.
- Update kdb patches.

++++ xorg-x11-driver-video:

- updated i810/intel driver to release 1.6.3

++++ Crystalcursors:

- fix for Xorg 7.1 (move to /usr/share/icons)

++++ gimp:

- Changed branding to SuSE Linux 10.2.

++++ gnome2-SuSE:

- Updated to SuSE Linux 10.2 branding.

++++ kdebase3-SuSE:

- artwork update for openSUSE 10.2

++++ hal:

- disables following patches for STABLE/SL10.2Alpha3, they cause a
segmenatation fault in the STABLE tree:
- hal-performance-properties2.diff
- hal-performance-properties_fix_compiler_warnings.diff
- disabled SLE10 specific patch for DBUS

++++ Full Changelog since Alpha 2.

Well, it was time to check out the Most Annoying Bugs list to see if there was any mention of a workaround for the X issue among others. It came as no real surprize to find most of my issues listed. The most annoying bug list contains:

  • YaST does not allow X11 configuration since it asks for non-existant xorg-x11-server-glx Bug #198250. Note: I could run X11 nevertheless and logged into both KDE and GNOME
  • zen-updater always shows patterns to update Bug #198379
  • f-spot does not work Bug #198377
  • gnome-wm does not handle X11R7 Bug #197093
  • Firefox does not start Bug #197928
  • Registration fails with an internal server error Bug #198381
  • applications using python-gtk are broken, e.g. smart-gui Bug #198391
  • kde su does not accept correct password Bug #198408
  • Most kernel module packages are not build against the new 2.6.18rc4 kernel. If you need them, I advise to wait for their update. The Xen packages are not adjusted either.
  • The change of branding (from "SUSE Linux 10.1" to "openSUSE 10.2") is not complete.
  • X Server fails to start with error message "could not open default font 'fixed'", because SaX2 writes wrong font path entries into /etc/X11/xorg.conf. Replace /usr/lib/X11/fonts with /usr/share/fonts/ as workaround. Bug #198653


I didn't check f-spot, and I don't mess with zen. I didn't get the "X server fails due to fixed font" problem with the fresh install, but perhaps this was the issue with the upgrade. Everything else on the list was spot-on.

I think the biggest issue is with this Xorg version. If developers insist upon using it, there are going to be a lot of unhappy users. I've experienced issues to a smaller degree with a couple of other distros as well using later 7.1 versions. I'm all for bleeding edge and don't mind minor breakage here and there, but the X server is one thing that needs to function fairly properly. I'm afraid like with Mandriva, this issue just spoils the whole experience and labels this release as not download-worthy. I'm not sure what other graphic chipset will have a problem, but nvidia is definitely one of them.

10.2 Alpha 2 Report.


More in Tux Machines

Today in Techrights

today's leftovers

  • iTWire - Microsoft to reduce global workforce
  • Microsoft Faces Two Lawsuits For Aggressive Windows 10 Upgrade Campaign
    The series of lawsuits against Microsoft doesn’t seem to terminate sooner.
  • Controlling access to the memory cache
    Access to main memory from the processor is mediated (and accelerated) by the L2 and L3 memory caches; developers working on performance-critical code quickly learn that cache utilization can have a huge effect on how quickly an application (or a kernel) runs. But, as Fenghua Yu noted in his LinuxCon Japan 2016 talk, the caches are a shared resource, so even a cache-optimal application can be slowed by an unrelated task, possibly running on a different CPU. Intel has been working on a mechanism that allows a system administrator to set cache-sharing policies; the talk described the need for this mechanism and how access to it is implemented in the current patch set.
  • Why Blockchain Matters
    If your familiarity with Bitcoin and Blockchain is limited to having heard about the trial of Silk Road’s Ross Ulbricht, you can be forgiven -- but your knowledge is out of date. Today, Bitcoin and especially Blockchain are moving into the mainstream, with governments and financial institutions launching experiments and prototypes to understand how they can take advantage of the unique characteristics of the technology.
  • Our Third Podcast, with Cybik, is Out Now
    Cybik comes back on how he came to know and use Linux in the first place, his gaming habits, how he got involved into the Skullgirls port, and shares with us his outlook on the Linux gaming landscape. The podcast is just an hour long and you can either download it below, and use our RSS feed (that has the additional benefit of making it easy for you to get new episodes from now on):
  • GSoC: final race and multi-disc implementation
    It’s been a while since I wrote a post here. A lot has happened since then. Now Gnome-games fully supports PlayStation games, with snapshoting capabilities. The next thing I’m working on is multi-disc support, specially for PlayStation titles. So far, there’s a working propotity although a lot needs to be re-engineered and polished. This last part of the project has involved working both in UI, persistance and logic layers.
  • This Week in GTK+ – 11
    In this last week, the master branch of GTK+ has seen 22 commits, with 6199 lines added and 1763 lines removed.
  • [Solus] Replacement of Release Schedule
    In the not so distant past, Solus followed a static point release model. Our most current release at this time is 1.2, with a 1.2.1 planned to drop in the near future. However, we also recently announced our move to a rolling release model. As such, these two schools of thought are in contradiction of one another.
  • First release of official ArchStrike ISO files! [Ed: last week]
  • July ’16 security fixes for Java 8
    On the heels of Oracle’s July 2016 security updates for Java 8, the icedtea folks have released version 3.1.0 of their build framework so that I could create packages for OpenJDK 8u101_b13 or “Java 8 Update 101 Build 13” (and the JRE too of course).
  • Pipelight update
    I decided to do an update of my “pipelight” package. I had not looked at it for a long time, basically because I do not use it anymore, but after I upgraded my “wine” package someone asked if I could please write up what could be done for wine-pipelight. As you know, pipelight is a Linux plugin wrapper for Mozilla-compatible browsers which lets you install and use Windows plugins on Linux. This configuration enables you to access online services which would otherwise be unavailable to you on a Linux platform. The pipelight plugin wrapper uses wine to load the Windows software.
  • Red Hat, Inc. (NYSE:RHT) Current Analyst Ratings
  • Friday Session Wrap for Red Hat, Inc. (NYSE:RHT)
  • Fedora @ EuroPython 2016 - event report
  • Android 7.0 Nougat could be release as soon as next month
  • Android gains anti-spam caller ID feature
  • Amazon Cloud Revenue Hits $2.9B
  • ServerMania – Discover High Availability Cloud Computing, powered by OpenStack
    Cloud computing is fast growing in the world of computer and Internet technology, many companies, organizations and even individuals are opting for shared pool of computing resources and services. For starters, Cloud computing is a type of Internet-based computing where users consume hosted services on shared server resources. There are fundamentally three types of cloud computing available today: private, public and hybrid cloud computing.

Leftovers: OSS and Sharing

  • Student survey data shows Open Source training uptake amongst women and young people remains extreme
    Future Cert, the UK and Ireland representative for the LPI (Linux Professional Institute), is calling for more awareness of Open Source software training amongst the under 21s and especially women, which the industry is so desperately in need of. New figures from a recent Future Cert student survey reveals that the number of women and young people taking LPI Certification in Open Source computing remains extremely low. Of those questioned, 98% were male, and just 2% were female, taking an LPI exam. This figure is significantly less than an already low figure of around 15% to 17% of women in IT careers in general. It raises the question, what does the industry need to do to make an Open Source career attractive to women?
  • Quality in open source: testing CRIU
    Checkpoint/Restore In Userspace, or CRIU, is a software tool for Linux that allows freezing a running application (or part of it) and checkpointing it to disk as a collection of files. The files can then be used to restore and run the application from the point where it was frozen. The distinctive feature of the CRIU project is that it is mainly implemented in user space. Back in 2012, when Andrew Morton accepted the first checkpoint/restore (C/R) patches to the Linux kernel, the idea to implement saving and restoring of running processes in user space seemed kind of crazy. Yet, four years later, not only is CRIU working, it has also attracted more and more attention. Before CRIU, there had been other attempts to implement checkpoint/restore in Linux (DMTCP, BLCR, OpenVZ, CKPT, and others), but none were merged into the mainline. Meanwhile CRIU survived, which attests to its viability. Some time ago, I implemented support for the Test Anything Protocol format into the CRIU test runner; creating that patch allowed me to better understand the nature of the CRIU testing process. Now I want to share this knowledge with LWN readers. [...] The CRIU tests are quite easy to use and available for everyone. Moreover, the CRIU team has a continuous-integration system that consists of Patchwork and Jenkins, which run the required test configurations per-patch and per-commit. Patchwork also allows the team to track the status of patch sets to make the maintainer's work easier. The developers from the team always keep an eye on regressions. If a commit breaks a tree, the patches in question will not be accepted.
  • Open-source Wire messenger gets encrypted screen-sharing
    Chat app Wire has been rapidly adding feature as of late as it looks to gain some traction against the myriad of competitors out there. The latest trick in its arsenal is screen sharing. Now you can click on the new screen-sharing button to, well, share your screen during a call (if you’re on a desktop, that is). It works during group chats too and, as with all Wire communications, is encrypted end-to-end. Wire believes it’s the first messaging app to include end-to-end encryption.
  • SPI board election results are available
    Software in the Public Interest (SPI) has completed its 2016 board elections. There were two open seats on the board in addition to four board members whose terms were expiring. The six newly elected members of the board are Luca Filipozzi, Joerg Jaspert, Jimmy Kaplowitz, Andrew Tridgell, Valerie Young, and Martin Zobel-Helas. The full results, including voter statistics, are also available.
  • SFK 2016 - Call for Speakers
    Software Freedom Kosova is an annual international conference in Kosovo organized to promote free/libre open source software, free culture and open knowledge, now in its 7th edition. It is organized by FLOSSK, a non governmental, not for profit organization, dedicated to promote software freedom and related philosophies.
  • Microsoft's Next Open Source Target Could Be PowerShell: Report
  • Open-source drug discovery project advances drug development
  • The First-Ever Test of Open-Source Drug-Discovery
  • Open-Source Drug Discovery a Success
  • CNS - Open-Source Project Spurs New Drug Discoveries
    Medicines for Malaria Venture, a nonprofit group based in Geneva, Switzerland, distributed 400 diverse compounds with antimalarial activity — called the Malaria Box — to 200 labs in 30 nations in late 2011. The findings from subsequent studies and analyses were published Thursday in the journal PLOS Pathogens. Distributing the Malaria Box to various labs enabled scientists to analyze the compounds and develop findings that have led to more than 30 new drug-development projects for a variety of diseases. As a stipulation to receiving the samples, the various research groups had to deposit the information from their studies in the public domain.
  • Wire and Launchkit go open source, a water flow monitoring system, and more news
  • Apache, astsu, Biscuit, Python, Puppet 4, systemd & more!
  • The Onion Omega2: The Latest Router Dev Board
  • Build a $700 open source bionic prosthesis with new tutorial by Nicolas Huchet of Bionico
    The 3D printing community has already successfully taken over the market for cosmetic prostheses, as fantastic initiatives like E-NABLE have proven. But the world of bionics is a different place and just a handful of makers have gone there with any form of success, such as the very inspiring Open Bionics. But even 3D printed bionic prostheses are definitely within our reach, as French open source fanatic Nicolas Huchet of Bionico has proven. Though by no means a making expert himself, he 3D printed his own open source bionic hand during a three month residency at FabLab Berlin and has now shared all the files – including an extensive tutorial – online. This means you can now 3D print your very own bionic prosthesis at home for just $700.
  • BCN3D Technologies develops open source 3D printed 'Moveo' robotic arm for schools
    Designed from scratch and developed by BCN3D engineers in collaboration with the Generalitat de Catalunya’s Departament d’Ensenyament (Department of Education), the BCN3D Moveo is an Arduino Mega 2560-powered, 3D printed robotic arm which could enable schools and colleges in Spain and elsewhere to teach students the basics of robotics, mechanical design, and industrial programming. When the Departament d’Ensenyament approached BCN3D one year ago regarding the possibility of an educative robotics project, the tech organization jumped at the chance to get on board.

Security Leftovers