Language Selection

English French German Italian Portuguese Spanish

openSUSE 10.2 Alpha 5 Report

Filed under
Reviews
SUSE
-s

openSUSE 10.2 alpha 5 was released a couple of days ago, and I've been testing various aspects since its install. Coincidently, I decided to download the dvd version this time only to find out later that it was the only version available. Quite honestly, my decision was really made by distrowatch, when it was the first link in their announcement. Forgetting that I usually do deltas, I right clicked, copied, and pasted their link into a terminal for wget. For whatever reason I chose it, DVD format is the next best way to go. It makes for a much more pleasant install than a 5 cd change-out. But more importantly, what did we find after the install?

Before we get to the system, let's talk a bit more about the install. When last we left our open source heros, they had changed the installer from a full screen view to a windowed view with a background in the planning stages. I've yet to hear the reason for this change, but this release we find a lovely background now in place. It matches the new splash screens found throughout the system and introduced last released. It's not an exact carbon copy, but it's a very good match.

Also new this release (I think) is now the option to install to a lvm. Reiserfs was still the default filesystem. I don't think we see any changes to the Software Manager Pattern categories this time. Remember we saw last time the change of installing all software before that initial reboot. Another new little option is the ability to replicate users from one installed system to your new install during the user setup phase. Unfortunately I didn't get to test this new option because my trigger finger was a bit too itchy and when I backed up, the option was gone. But I will test it next time.

The install went well except for that same kde_imaging package keeping some kde rpms from installing, testing the internet connection, and the registration (or online update setup) step. The release notes didn't contain any information at this point either.

        

After boot we find the newly tagged KDE 3.5.5, that shoots an error about dbus not starting. Trying to start it results in the output that is already running. Trying to start yast2 (or anything requiring root priviledges) from the menu is still broken as well as administrator mode in kcontrol.

Gnome is at version 2.16.1. Xorg is version 7.1 and the kernel is 2.6.18. There weren't too many cosmetic changes this time as we were introduced to the new kde menu last release and gnome's new menu release before last.

As registration fails, there isn't a remote rpm repository set up for the online updates and trying to add one manually fails here with the message that it can't read the source format. The basic software manager seems to function properly as much as can be tested by installing additional packages from the install cd (dvd).

        

The list of known bugs shows some significant regression. It currently contains:

  • Registration fails

  • After logging in to KDE, a popup window will inform you that dbus is not running. Just ignore the message - dbus is running
  • Suspend to disk will fail with an error message "The resume device configured in /etc/suspend.conf". (fixed powersave package should be in factory by monday, until then you can edit /etc/suspend.conf and put your resume device from the resume=... boot parameter there. However, the fixed package is better).
  • The x86-64 uses nearly double the disk space for installed packages than usual. It looks like a bug in binutils stripping the binaries
  • Instead of /dev/hd for IDE disks using Intel ICHx chipsets the libata interfaces are used and disks show up as /dev/sd
  • zen-updater always shows patterns to update
  • It's not possible to start applications via kdesu, eg yast2. Workaround: use "su" in a shell.
  • The bootloader configuration on BIOS-based RAID (so-called FakeRAID) systems fails.
  • gnome-screensaver does not accept the correct password. Workaround: Kill the gnome-screensaver process.
  • CD changing does not work, you cannot install with changing of physical media. We will therefore release instead of CD images only a DVD iso!
  • There's no PowerPC distribution this time.


Some rpm version highlights this release include:

  • kernel-source-2.6.18-9.i586.rpm

  • xorg-x11-7.1-27.i586.rpm
  • qt3-3.3.6-21.i586.rpm
  • gtk2-2.10.3-7.i586.rpm
  • kdebase3-3.5.5-3.i586.rpm
  • gnome-desktop-2.16.1-2.i586.rpm
  • gcc-4.1.3-13.noarch.rpm
  • MozillaFirefox-1.5.0.7-5.i586.rpm
  • OpenOffice_org-2.0.4-9.i586.rpm
  • gimp-2.2.13-5.i586.rpm
  • Full RPMList


Alpha 5 changelog highlights include:

++++ kdebase3:

- update 3_5_BRANCH.diff to include kicker minipager fixlets
- update to 3.5.5 release tarball

++++ arts:

- update to 1.5.5 release tarball

++++ beagle-index:

- bump Version: to reflect right distro version and last sync

++++ gnome-desktop:

- update to version 2.16.1
- updated translations

++++ kernel-source:

- Update to 2.6.18
- remove CONFIG_USB_DEVICEFS as it's insecure and we handle /dev/bus/usb
properly.
- patches.drivers/libata-add-ata-drivers
Backport libata drivers.
- patches.drivers/libata-acpi-update
Update ACPI support for libata.

++++ openssl:

- update to 0.9.8d

++++ openssh:

- fixed DoS by CRC compensation attack detector [#206917] (dos-fix.patch)
- fixed client NULL deref on protocol error

++++ xgl-hardware-list:

- Add new cards tested by Bryan.

++++ cups:

- CUPS 1.2.4 fixes a number of web interface, scheduler, and CUPS API issues.

++++ OpenOffice_org:

- updated to snapshot ood680-m4 (2.0.4-rc2)

++++ alsa:

- updated to ALSA 1.0.13rc2:

++++ Mesa:

- updated to Mesa 6.5.1

++++ Full changelog since Alpha 4.


As one can see from the changelog that the developers have been typing their fingers to the bone even if it doesn't show a lot on the surface. This release contains a lot of under-the-hood bug fixes, patches, and version upgrades. I wish I could say it seemed to be working better, but it seems a lot of the problems encountered with alpha 4 were still present and some new ones introduced with alpha 5. Not to fear though as it's still early in the development process. My report might read like a laundry list of negative issues, but even with all these problems, an alpha of openSUSE is still much more stable and reliable than a lot of others' finals. If history repeats itself, there will be several betas and several rcs before the expected public release on Thu, Dec 7. Although officially, there are only two betas (expected on Thu, Oct 26 and Thu, Nov 9) and one release candidate (on Thu, Nov 23) planned at this time with Goldmaster being scheduled for Thu, Nov 30.

Alpha 4 Report.


Windowed installer screen change

-- from your review --
"... they had changed the installer from a full screen view to a windowed view with a background in the planning stages. I've yet to hear the reason for this change, but this release we find a lovely background now in place."

Think I can offer a good reason for this installer change. I recently got a new HP dv6000 laptop with 15.4" 1280x800 WXGA screen resolution. When I previously loaded openSUSE 10.1 the old full screen installer stretched everything - oval clock icon, stretched fonts, etc. Today I loaded openSUSE 10.2 Alpha5 and the new floating installer window displays everything in it's correct aspect - crisp fonts, correct icons, etc. BTW, that new subtle twisted swirl design background pattern is a perfect match to my HP Imprint case design swirls... NICE!

So far Aplha5 is working great (Gnome only load) - glitch in CUPs printing ("too many levels of symbolic links") - I'll play with that some more. Everything else appears to be 100% for my purposes. And that earlier Alsa Intel 82801G laptop sound chip nasty volume problem is FIXED NOW!!! Kind of nice to play with the new menu format from SLED 10 - so far it hasn't been a problem.

Good work from the openSUSE crew - and they have 60 days left to keep polishing... I have high hopes for 10.2

re: Windowed installer

Quote:
Today I loaded openSUSE 10.2 Alpha5 and the new floating installer window displays everything in it's correct aspect - crisp fonts, correct icons, etc.

Wonderful. Thanks for your input. That is probably why. Well, I'm glad to see it then. I knew they had a reason. Big Grin

Quote:
BTW, that new subtle twisted swirl design background pattern is a perfect match to my HP Imprint case design swirls... NICE!

lol. You can't beat that. Works great, looks great, and it matches the hardware! Big Grin

----
You talk the talk, but do you waddle the waddle?

10.2 Alpha 5

Tried to install and could not get past the language selection screen.
Mouse icon flew all over the screen.
Repeted tabbing (Gentle)just managed to get the Next button highlighted and then nothing. Just froze.

Cd checksums all Ok.

Re downloaded CD 1 and tried again, same thing.

AMD 64 ,heaps of mem harddrive etc.

Oh well will just have to wait a bit longe Sad

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Programming: WebAssembly, Mozilla GFX, Qt and Python

  • WebAssembly for speed and code reuse

    Imagine translating a non-web application, written in a high-level language, into a binary module ready for the web. This translation could be done without any change whatsoever to the non-web application's source code. A browser can download the newly translated module efficiently and execute the module in the sandbox. The executing web module can interact seamlessly with other web technologies—with JavaScript (JS) in particular. Welcome to WebAssembly. As befits a language with assembly in the name, WebAssembly is low-level. But this low-level character encourages optimization: the just-in-time (JIT) compiler of the browser's virtual machine can translate portable WebAssembly code into fast, platform-specific machine code. A WebAssembly module thereby becomes an executable suited for compute-bound tasks such as number crunching. Which high-level languages compile into WebAssembly? The list is growing, but the original candidates were C, C++, and Rust. Let's call these three the systems languages, as they are meant for systems programming and high-performance applications programming. The systems languages share two features that suit them for compilation into WebAssembly. The next section gets into the details, which sets up full code examples (in C and TypeScript) together with samples from WebAssembly's own text format language.

  • Mozilla GFX: moz://gfx newsletter #47

    Hi there! Time for another mozilla graphics newsletter. In the comments section of the previous newsletter, Michael asked about the relation between WebRender and WebGL, I’ll try give a short answer here. Both WebRender and WebGL need access to the GPU to do their work. At the moment both of them use the OpenGL API, either directly or through ANGLE which emulates OpenGL on top of D3D11. They, however, each work with their own OpenGL context. Frames produced with WebGL are sent to WebRender as texture handles. WebRender, at the API level, has a single entry point for images, video frames, canvases, in short for every grid of pixels in some flavor of RGB format, be them CPU-side buffers or already in GPU memory as is normally the case for WebGL. In order to share textures between separate OpenGL contexts we rely on platform-specific APIs such as EGLImage and DXGI. Beyond that there isn’t any fancy interaction between WebGL and WebRender. The latter sees the former as a image producer just like 2D canvases, video decoders and plain static images.

  • The Titler Revamp: QML Producer in the making

    At the beginning of this month, I started testing out the new producer as I had a good, rough structure for the producer code, and was only facing a few minor problems. Initially, I was unclear about how exactly the producer is going to be used by the titler so I took a small step back and spent some time figuring out how kdenlivetitle worked, which is the producer in use. Initially, I faced integration problems (which are the ones you’d normally expect) when I tried to make use of the QmlRenderer library for rendering and loading QML templates – and most of them were resolved by a simple refactoring of the QmlRenderer library source code. To give an example, the producer traditionally stores the QML template in global variables which is taken as a character pointer argument (which is, again, traditional C) The QmlRenderer lib takes a QUrl as its parameters for loading the Qml file, so to solve this problem all I had to do was to overload the loadQml() method with one which could accommodate the producer’s needs – which worked perfectly fine. As a consequence, I also had to compartmentalise (further) the rendering process so now we have 3 methods which go sequentially when we want to render something using the library ( initialiseRenderParams( ) -> prepareRenderer( ) -> renderQml( ) ) [...] The problem was resolved (thank you JB) finally and it was not due to OpenGL but it was simply because I hadn’t created an QApplication for the producer (which is necessary for qt producers). The whole month’s been a steep curve, definitely not easy, but, I enjoyed it! Right now, I have a producer which is, now, almost complete and with a little more tweaking, will be put to use, hopefully. I’m still facing a few minor issues which I hope to resolve soon and get a working producer. Once we get that, I can start work on the Kdenlive side. Let’s hope for the best!

  • How to Make a Discord Bot in Python

    In a world where video games are so important to so many people, communication and community around games are vital. Discord offers both of those and more in one well-designed package. In this tutorial, you’ll learn how to make a Discord bot in Python so that you can make the most of this fantastic platform.

  • Qt Visual Studio Tools 2.4 RC Released

    The Visual Studio Project System is widely used as the build system of choice for C++ projects in VS. Under the hood, MSBuild provides the project file format and build framework. The Qt VS Tools make use of the extensibility of MSBuild to provide design-time and build-time integration of Qt in VS projects — toward the end of the post we have a closer look at how that integration works and what changed in the new release. Up to this point, the Qt VS Tools extension managed its own project settings in an isolated manner. This approach prevented the integration of Qt in Visual Studio to fully benefit from the features of VS projects and MSBuild. Significantly, it was not possible to have Qt settings vary according to the build configuration (e.g. having a different list of selected Qt modules for different configurations), including Qt itself: only one version/build of Qt could be selected and would apply to all configurations, a significant drawback in the case of multi-platform projects. Another important limitation that users of the Qt VS Tools have reported is the lack of support for importing Qt-related settings from shared property sheet files. This feature allows settings in VS projects to be shared within a team or organization, thus providing a single source for that information. Up to now, this was not possible to do with settings managed by the Qt VS Tools.

Screenshots/Screencasts: 10 GNU/Linux Distros (Screenshots) and New Screencast/Video of Endeavour OS 2019.08.17

  • 10 Linux distros: From different to dangerous

    One of the great benefits of Linux is the ability to roll your own. Throughout the years, individuals, organizations, and even nation states have done just that. In this gallery, we're going to showcase some of those distros. Be careful, though. You may not want to load these, or if you do, put them in isolated VMs. We're not kidding when we say they could be dangerous.

  • Endeavour OS 2019.08.17 Run Through

    In this video, we are looking at Endeavour OS 2019.08.17.

A Cycle of Renewal, Broken: How Big Tech and Big Media Abuse Copyright Law to Slay Competition

In 1950, a television salesman named Robert Tarlton put together a consortium of TV merchants in the town of Lansford, Pennsylvania to erect an antenna tall enough to pull down signals from Philadelphia, about 90 miles to the southeast. The antenna connected to a web of cables that the consortium strung up and down the streets of Lansford, bringing big-city TV to their customers — and making TV ownership for Lansfordites far more attractive. Though hobbyists had been jury-rigging their own "community antenna television" networks since 1948, no one had ever tried to go into business with such an operation. The first commercial cable TV company was born. The rise of cable over the following years kicked off decades of political controversy over whether the cable operators should be allowed to stay in business, seeing as they were retransmitting broadcast signals without payment or permission and collecting money for the service. Broadcasters took a dim view of people using their signals without permission, which is a little rich, given that the broadcasting industry itself owed its existence to the ability to play sound recordings over the air without permission or payment. The FCC brokered a series of compromises in the years that followed, coming up with complex rules governing which signals a cable operator could retransmit, which ones they must retransmit, and how much all this would cost. The end result was a second way to get TV, one that made peace with—and grew alongside—broadcasters, eventually coming to dominate how we get cable TV in our homes. By 1976, cable and broadcasters joined forces to fight a new technology: home video recorders, starting with Sony's Betamax recorders. In the eyes of the cable operators, broadcasters, and movie studios, these were as illegitimate as the playing of records over the air had been, or as retransmitting those broadcasts over cable had been. Lawsuits over the VCR continued for the next eight years. In 1984, the Supreme Court finally weighed in, legalizing the VCR, and finding that new technologies were not illegal under copyright law if they were "capable of substantial noninfringing uses." Read more

Software, HowTos and Storage

  • Pause Music When Locking The Screen And Resume On Unlock For Spotify, Rhythmbox, Others

    When you lock your computer screen (without suspending the system), most desktop audio players continue playback in the background, sometimes not emitting any sound ¹. Due to this you may unintentionally skip parts of podcasts or songs in a playlist, etc. Enter pause-on-lock, a Bash script that pauses your music player when you lock the screen and resumes playback once the screen is unlocked. pause-on-lock works on Unity, GNOME, Cinnamon and MATE desktop environments, and by default it supports Spotify and Rhythmbox. With the help of playerctl (a command line controller for controlling media players that support the MPRIS D-Bus interface), this script can extend its supported music players to many others, including Audacious, VLC, Cmus, and others.

  • Easy Way to Screen Mirroring Android on Ubuntu!

    Screen Mirroring is one of the features found on smartphones, one of which is on Android. This feature serves to display the smartphone to a computer. This is very useful for example when used for demo applications that you make, or maybe for other things related to smartphones. In Ubuntu, we can do screen mirroring with applications available on Android, for example is AirDroid which can be used for screen mirroring through a browser. But I feel less optimal when using this instant method. Because there is a lag between activity on the smartphone and on the monitor screen on the computer, and the results are less than optimal. What might be the cause because it is opened through a browser and uses wi-fi? (Personal question). I am looking for another application for screen mirroring on Ubuntu, and one of the very good applications is Scrcpy. This application can be used for screen mirroring without a root device.

  • Command line quick tips: Searching with grep
  • How to Install Cezerin on Debian 9
  • How to Create a Bootable USB Stick from the Ubuntu Terminal
  • How to Install Git on Debian 10
  • How to Copy/Move a Docker Container to Another Host
  • Six practical use cases for Nmap
  • The Next Stage of Flash Storage: Computational Storage
  • NAS upgrade

    At some point in the future I hope to spend a little bit of time on the software side of things, as some of the features of my set up are no longer working as they should: I can't remote-decrypt the main disk via SSH on boot, and the first run of any backup fails due to some kind of race condition in the systemd unit dependencies. (The first attempt does not correctly mount the backup partition; the second attempt always succeeds).

  • Storage Concepts And Technologies Explained In Detail