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

Linux Devices/Open Hardware

  • Site.js and Pi

    Chatting about Pi, on a Pi, with a chat server running on Site.js on the same Pi.

  • This MicroATX Motherboard is Based on Phytium FT2000/4 Arm Desktop SoC @ 3.0 GHz
  • Rikomagic R6 Review – Part 1: Android Mini Projector’s Unboxing and First Boot

    Rikomagic R6 is a mini Android projector that looks like a vintage radio, or depending on your point of view a mini vintage television.

  • Brief on Behalf of Amicus Curiae Open Source Hardware Association in Curver Luxembourg, SARL v. Home Expressions Inc., No. 18-2214 (Fed. Cir.)

    Curver Luxembourg, SARL v. Home Expressions Inc. is a case of first impression for the Court of Appeals for the Federal Circuit. The question on appeal is whether a design patent’s scope is tied to the article of manufacture disclosed in the patent. In this amicus brief, the Open Source Hardware Association (“OSHWA”) explains the potential effects on open source hardware development, and design practice generally, of untethering design patent protection from the article of manufacture disclosed in the patent. A large percentage of open-source hardware combines both ornamental and functional elements, and industrial design routinely involves applying design concepts from disparate fields in novel ways. To engage in this practice, open-source hardware designers need to know the universe of available source material and its limits. Further, understanding the licensing requirements of open-source hardware begins with understanding how the elements that make up that hardware may or may not be protected by existing law. Accordingly, while many creators of open-source hardware do not seek patent protection for their own creations, an understandable scope of design patent protection is nonetheless essential to their ability to collaborate with other innovators and innovate lawfully. The brief argues that the District Court in the case—and every district court that has considered the issue—correctly anchored the patented design to the article of manufacture when construing the patent. The brief explains that anchoring the patented design to the disclosed article of manufacture is the best approach, for several reasons. Connecting the patented design to the disclosed article of manufacture calibrates the scope of design patent protection to the patentee’s contribution over the prior art. It avoids encumbering the novel and nonobvious application of prior designs to new articles of manufacture, a fundamental and inventive practice of industrial design. It aligns the scope of design patent protection with its purpose: encouraging the inventive application of a design to an article of manufacture. This balances protection for innovative designs with later innovators’ interest in developing future designs. Finally, anchoring the patented design to the disclosed article of manufacture helps fulfill design patent law’s notice function by clarifying the scope of protection.

Graphics: Gallium3D and AMDGPU

  • Gallium3D's Mesa State Tracker Sees "Mega Cleanup" For NIR In Mesa 19.3

    AMD developer Marek Olšák has landed a "mega cleanup" to the Gallium3D Mesa state tracker code around its NIR intermediate representation handling. As part of getting the NIR support in good enough shape for default usage by the RadeonSI driver, Marek has been working on a number of clean-ups involving the common Gallium / Mesa state tracker code for NIR.

  • AMDGPU DC Looks To Have PSR Squared Away - Power-Savings For Newer AMD Laptops

    It looks like as soon as Linux 5.5 is where the AMDGPU kernel driver could be ready with Panel Self Refresh (PSR) support for enabling this power-savings feature on newer AMD laptops. While Intel's Linux driver stack has been supporting Panel Self Refresh for years, the AMD support in their open-source Linux driver code has been a long time coming. We've seen them working towards the support since Raven Ridge and now it appears the groundwork has been laid and they are ready to flip it on within the Display Core "DC" code.

today's howtos and programming bits

  • CentOS 8 Package Management with DNF on the Command Line
  • AdamW’s Debugging Adventures: “dnf is locked by another application”
  • Managing user accounts with Cockpit
  • Download Ubuntu 19.10 ISO image to install on VirtualBox VM
  • GNU poke: Dealing with alternatives - Unions in Poke

    Computing with data whose form is not the most convenient way to be manipulated, like is often the case in unstructured binary data, requires performing a preliminary step that transforms the data into a more convenient representation, usually featuring a higher level of abstraction. This step is known in computer jargon as unmarshalling, when the data is fetch from some storage or transmission media or, more generally, decoding. Once the computation has been performed, the result should be transformed back to the low-level representation to be stored or transmitted. This is performed in a closing step known as marshalling or, more generally, encoding. Consider the following C program whose purpose is to read a 32-bit signed integer from a byte-oriented storage media at a given offset, multiply it by two, and store the result at the same offset.

  • Android NDK r21 moves to beta

    Android announced that NDK r21 is now in beta. Android NDK is a toolset for implementing parts of an app in native code. The release — which is the first long term support release — includes improved defaults for better security and performance. One of the key features in the release is an update to GNU Make to version 4.2, which provides a number of bug fixes, and enables ‘–output-sync’ to avoid interleaving output with error messages, the team explained. This is enabled by default with ndk-build. Additionally, GDB, the GNU project debugger, has been updated to version 8.3, which includes fixes for debugging modern Intel CPUs.

  • What is the history behind C Programming and Unix?

    If you think C programming and Unix are unrelated, then you are making a big mistake. Back in the 1970s and 1980s, if the Unix engineers at Bell Labs had decided to use another programming language instead of C to develop a new version of Unix, then we would be talking about that language today. The relationship between the two is simple; Unix is the first operating system that is implemented with a high-level C programming language, got its fame and power from Unix. Of course, our statement about C being a high-level programming language is not true in today’s world. This article is an excerpt from the book Extreme C by Kamran Amini. Kamran teaches you to use C’s power. Apply object-oriented design principles to your procedural C code. You will gain new insight into algorithm design, functions, and structures. You’ll also understand how C works with UNIX, how to implement OO principles in C, and what multiprocessing is.

Server: Mirantis, Containers, GraalVM and Pensando

  • Mirantis Partners With OpenStack Foundation to Support Upgraded COA Exam

    “With the OpenStack market forecasted to grow to $7.7 billion by 2022 according to 451 research, the demand for Certified OpenStack Administrators is clearly strong and set to continue growing for many years to come,” said Mark Collier, COO of the OpenStack Foundation. “We are excited to collaborate with Mirantis, who has stepped up to provide the resources needed to manage the COA, including the administration of the vendor-neutral OpenStack certification exam.”

  • How to use containers with an eye on security

    Containers are all the rage. With good reason. With containers, your company’s apps and service deployments become considerably more agile, more reliable, and even more secure. This is true for software development companies (who develop apps and services for other businesses), as well as companies looking to roll out web-based and mobile applications with an unheard of speed and reliability. But with any new technology, comes hurdles. One of the biggest hurdles for any business is security. Data breaches have become rampant and it’s on the shoulders of every company to do everything in their power to make sure they are rolling out technology that is as secure as possible. This idea should certainly be applied to containers. But what can you do to use containers security? Fortunately, there are a few steps that you can take from the very beginning.

  • GraalVM: Clearing up confusion around the term and why Twitter uses it in production

    What does the “umbrella term” GraalVM stand for? We interviewed Chris Thalinger (Twitter) at JAX London 2019. Hear what he has to say about the meaning of Graal and how it can benefit Twitter as well as the environment.

  • Pensando Systems Exits Stealth Mode With Plans To Take On Amazon AWS

    While normally we don't cover hardware start-ups on Phoronix, Pensando Systems has just exited stealth and given their focus will be heavily involved with Linux and in fact already have their first kernel driver mainlined. After announcing a $145 million (USD) Series-C round, Pensando Systems exited "stealth" and revealed the first details of what they are trying to achieve with this company led by many ex-Cisco staff. [...] Pensando has been on our radar since as I wrote about last month when they were just a stealth networking startup they already upstreamed their first Linux kernel driver. In the Linux 5.4 kernel is a Pensando "Ionic" driver for a family of network adapters. In this week's press release, Pensando didn't specifically call out Ionic but presumably is the backbone to their hardware. Now that they are beginning to talk about their ambitions, hopefully we see more Linux kernel patches from them soon.