Language Selection

English French German Italian Portuguese Spanish

openSUSE 10.2 RC 1 Report

Filed under
Reviews
SUSE
-s

We're in the homestretch now. The only planned release candidate of openSUSE 10.2 was released a few days ago and final is expected to be released to the public on December 7. From this point on only showstopper and security bugfixes get integrated, so we are able to get a real good idea of 10.2 from this rc. I must say, from what I've seen, this is going to be a great release.

This time around I thought it might be fun to test the upgrade procedure. Granted it was only from beta 2 to rc 1, but it went without a hitch (unless the few app glitches were due to the upgrade). With the system resulting from an upgrade, all hardware was already configured and as such, everything worked. This enabled the internet test and the downloading of release notes as well as the online update configuration to be successful. As stated in the changelog, ext3 is now the default filesystem.

The update process is much more simplified than a fresh install, only requiring a fraction of the steps. This time the selection splash screen presented at first boot of the install DVD was the old Pingus modification. I'd forgotten all about that one, but I guess it's fitting for the time of year. I booted the install disk several times, and it appeared each time. I gotta say, I think I prefer animated penguins in santa caps to the big lizard photo. The next busy splash is a bit updated from our last report, as are all the splash screens. There isn't a big change, but the ends of the wisps seem to diverge or flare out a bit more. The color scheme has remained the same.

Once at the desktop we finally see a new openSUSE wallpaper. As suspected, it does indeed match the new splash screens. It's not an exact copy and may not be the final incarnation, but at this point it's a non-distracting background with just a hint of pattern on top of the blue foundation. It's very typical of default wallpapers found in both KDE and openSUSE.

As this is the release candidate that incorporated only serious bug fixes and last minute documentation, we didn't find any surprises. Actually, that may not be exactly so. I was quite suprised at the performance increase experienced this release. I suppose it could be contributed to disabling verbose bug reporting, but it's quite noticeable. For example, OpenOffice.org opened too fast to catch a screenshot of its splash screen.

I did experience a couple of glitches with the apps. The first one was banshee would not open. It bailed out at the splash screen. Another problematic application was gnucash. Again, it just wouldn't open only giving a quick glimpse of the splash before its crash and burn. Everything else seemed to function well in the minimal testing received here. Both KDE and Gnome seemed to behave really well too. The software managers worked as designed as far as could be tested (by installing and uninstalling a few packages). We did experience some difficulty when trying to install iceWM due to conflicting files.

        

        

Andreas Jaeger said of this release, "The areas that we had to work hardest on were the bootloader configuration and our software management stack."

He further explains, "For our software management stack we now have two different user interfaces: The ZENworks Linux interface introduced in SUSE Linux 10.1 with the commands rug and zen-updater - and the new software management tools zypper and opensuse-updater. Zypper accepts most of the commands that rug does with the same syntax. The applet opensuse-updater can talk to the zmd daemon or use directly the package management library without a running daemon. During installation the ZENworks tools are installed by default with the "Enterprise Software Management (ZENworks Linux Management)" pattern, the other one is name "openSUSE Software Management" and can be used alternatively."



RPM Highlights:

  • kernel-default-2.6.18.2-23

  • xorg-x11-7.2-23
  • gcc-4.1.3-28
  • kdebase3-3.5.5-63
  • gnome-desktop-2.16.1-25
  • qt3-3.3.7-11
  • libqt4-4.2.1-17
  • gtk2-2.10.6-12
  • OpenOffice_org-2.0.4-35
  • MozillaFirefox-2.0-19
  • gimp-2.2.13-26
  • amarok-1.4.4-27
  • blender-2.42a-23
  • gaim-1.5.0-84
  • dbus-1-1.0.0-6
  • Full RPMList


Changelog Highlights:

++++ release-notes:

- 10.2.9:
* New Default File System: ext3. .

++++ gnome-main-menu:

- Use package-manager instead of zen-updater.
- Dropped recommends: zen-updater.

++++ compiz:

- Patch gnome-xgl-settings to use the new package-manager
abstraction.

++++ kdebase3-SuSE:

- don't start greeter on every login
- update splash screen preview picture
- invalidate splash screen cache to ensure new one gets shown
- update of splash screen artwork for 10.2
- trigger the kmenu when the greeter closes to avoid focus handling
locks

++++ sax2:

- sometimes usb mice were missed

++++ qtcurve-gtk2:

- fix gtk-window-decorator crash

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

- updated (optional) intel modesetting driver (git_2006-11-21)
* Enable second SDVO channel. Rework SDVO support so that it
can deal with two channels correctly, also save/restore all
connected output timings.
* Set configured values for screen virtual size and initial
frame. Computation for virtual size and initial frame origin
is quite broken in xf86 common code.

++++ yast2-printer:

- remote printers are allowed to modify

++++ OpenOffice_org:

- updated ooo-build to version 2.0.4.7:
* wrong calculation in Calc, r1c1 stuff
* searching for JREs

++++ evolution:

- update to version 2.8.2
- translation updates

++++ f-spot:

- Fix picasa web export.

++++ openSUSE-release:

- Not anymore beta...

++++ suseRegister:

- fix parameter List when --no-hw-data is given

++++ planmaker:

- Update to latest version from Softmaker

++++ xcdroast:

- fix dvd burning

++++ yast2-scanner:

- V 2.14.9
- Fixed creation of interface_and_usbid_string in the model_items
list (set interface_and_usbid_string to the empty string if
the scanner has neither SCSI nor USB).
- Using better syntax for the model preselection code
(regarding access integer values in term types).

++++ cups:

- Upgrade to 1.2.7 (another bugfix version)

++++ Full Changelog


Most Annoying Bugs:

  • opensuseupdater opens its window on every desktop login. fix, as root: 'echo "NotShowIn=KDE;" >>/opt/kde3/share/autostart/opensuseupdater.desktop'

  • grub crashes with default proposal & dmraid

Release Notes Highlights:

  • Switch from Firefox version 1.5 to version 2 is a major update. Some themes and extensions will not work anymore. Default keybindings are changed.

  • The "cdrecord" package has been dropped from the distribution. The new "wodim" package can be used.
  • The update of CUPS from version 1.1 to 1.2 carries incompatible changes. It is not possible to convert the printer configuration from the previous CUPS versions automatically.
  • Experts can now rely on YaST for configuring LVM (Logical Volume Manager) and EVMS (Enterprise Volume Management).
  • The X.Org system is installed in /usr. Adjust your programs if needed.
  • The suspend framework switched from powersaved to pm-utils.
  • Full Release Notes


As you can see things seem to be shaping up quite nicely. The Most Annoying Bug list consists of only two items. The changelog contained many bug fixes and also a few version upgrades. The Release Notes are practically complete for the 10.2 release. System operations are becoming more refined with only minimal problems and the glitches of previous final release are just about massaged out of the new software manager. The system itself is looking very slick as well. It appears we are in for a great release this time. No matter your stance on the political issues with Novell lately, the efforts of the openSUSE developers are very apparent and are worthy of note. I find this release candidate looking great and functioning even better. I'm very much looking forward to the final due in just about two weeks. We at Tuxmachines plan on reporting our experiences upgrading from 10.1 as well as a fresh install.

openSUSE 10.2 Beta 2 Report

More in Tux Machines

Calibre 5.0 Ebook Manager Released with Text Highlighting Support, Dark Mode

Coming almost a year after the Calibre 4.0 series, Calibre 5.0 is here with some major changes. This include the ability to highlight text in the E-book viewer, which is one of the most requested feature for this powerful ebook manager. Users will be able to use colors when highlighting text in ebooks, as well as to use all sorts of text formatting and styles, including strikethrough and underline. In addition, you can even add notes to your highlights. All the highlights will be stored in the respective EPUB file, which makes them easy to share. In addition, you can browse all your highlights in the Calibre library using the Browse annotations tool. Read more

Android Leftovers

Compute module and dev kit aim Snapdragon 865 at AR/VR

Lantronix has launched 50 x 29mm “Open-Q 865XR SOM” and $995 dev kit that runs Android 10 on a 15-TOPS NPU equipped Snapdragon 865 with 6GB LPDDR5, 802.11ax, and triple MIPI-CSI interfaces. Intrinsyc, a subsidiary of Lantronix, has introduced an IoT-oriented compute module and development kit based on Qualcomm’s Snapdragon 865 (SXR2130P) SoC. The $445 Open-Q 865XR SOM and $995 Open-Q 865XR SOM Development Kit follow Intrinsyc’s more smartphone-oriented Snapdragon 865 Mobile HDK. The Open-Q 865XR targets imaging intensive embedded applications including Augmented Reality/Virtual Reality (AR/VR) applications in AI machine learning, medical, gaming, logistics and retail sectors. Read more

Programming: Git and Qt

  • Understand the new GitLab Kubernetes Agent

    GitLab's current Kubernetes integrations were introduced more than three years ago. Their primary goal was to allow a simple setup of clusters and provide a smooth deployment experience to our users. These integrations served us well in the past years but at the same time its weaknesses were limiting for some important and crucial use cases.

  • GitLab Introduces the GitLab Kubernetes Agent

    The GitLab Kubernetes Agent (GKA), released in GitLab 13.4, provides a permanent communication channel between GitLab and the cluster. According to the GitLab blog, it is designed to provide a secure solution that allows cluster operators to restrict GitLab's rights in the cluster and does not require opening up the cluster to the Internet.

  • Git Protocol v2 Available at Launchpad

    After a few weeks of development and testing, we are proud to finally announce that Git protocol v2 is available at Launchpad! But what are the improvements in the protocol itself, and how can you benefit from that? The git v2 protocol was released a while ago, in May 2018, with the intent of simplifying git over HTTP transfer protocol, allowing extensibility of git capabilities, and reducing the network usage in some operations. For the end user, the main clear benefit is the bandwidth reduction: in the previous version of the protocol, when one does a “git pull origin master”, for example, even if you have no new commits to fetch from the remote origin, git server would first “advertise” to the client all refs (branches and tags) available. In big repositories with hundreds or thousands of refs, this simple handshake operation could consume a lot of bandwidth and time to communicate a bunch of data that would potentially be discarded by the client after. In the v2 protocol, this waste is no longer present: the client now has the ability to filter which refs it wants to know about before the server starts advertising it.

  • Qt Desktop Days 7-11 September

    We are happy to let you know that the very first edition of Qt Desktop Days 2020 was a great success! Having pulled together the event at very short notice, we were delighted at the enthusiastic response from contributors and attendees alike.

  • Full Stack Tracing Part 1

    Full stack tracing is a tool that should be part of every software engineer’s toolkit. It’s the best way to investigate and solve certain classes of hard problems in optimization and debugging. Because of the power and capability it gives the developer, we’ll be writing a series of blogs about it: when to use it, how to get it set up, how to create traces, and how to interpret results. Our goal is to get you capable enough to use full stack tracing to solve your tough problems too. Firstly, what is it? Full stack tracing is tracing on the full software stack, from the operating system to the application. By collecting profiling information (timing, process, caller, API, and other info) from the kernel, drivers, software frameworks, application, and JavaScript environments, you’re able to see exactly how the individual components of a system are interacting. That opens up areas of investigation that are impossible to achieve with standard application profilers, kernel debug messages, or even strategically inserted printf() commands. One way to think of full stack tracing is like a developer’s MRI machine that allows you to look into a running system without disturbing it to determine what is happening inside. (And unlike other low-level traces that we’ve written about before, full stack tracing provides a simpler way to view activity up and down the entire software stack.)