Welcome to Planet openSUSE

This is a feed aggregator that collects what openSUSE contributors are writing in their respective blogs.

To have your blog added to this aggregator, please read the instructions.


Friday
21 July, 2017



face

Dear Tumbleweed users and hackers,

What a luck I did not get around to write the review last week – I’d have a hard time this week otherwise. As you certainly realized, we did not have a snapshot for a long time already (in fact 0712 is currently the last release). Since the last review of two weeks ago, there have been 5 snapshots released (0707, 0708, 0709, 0710 and 0712) Let’s focus on what those snapshots delivered, then I’ll try to give some information of why we stalled for 10 days now.

  • Qt 5.9.1
  • libzypp: dup defaults now to –allow-no-vendor-change
  • wine 2.12
  • Mesa 17.1.4
  • NetworkManager 1.8.2
  • All the nice things the YaST Team is blogging about

with snapshot 0712 I was approached by SUSE internally for a small ‘break’, as SLE15 did not keep up with building on the linked infrastructure (mainly due to archs building slower than x86_64 does, like aarch64 and s390x). So I basically granted them the weekend until July 17, by when the internal infrastructure was indeed ready and we wanted to resume Tumbleweed snapshots. Of course, we had been working a lot on the Staging areas and were ready for quite some massive changes on Monday (for the 0717 snapshot)

Among the interesting things there were:

  • Linux kernel 4.12
  • ruby 2.4 as default, with ruby 2.2 and ruby 2.3 being removed from the repositories

Turns out, one of our bots had a mistake and the removal of ruby 2.2 would have disrupted our users: the bot did not flag the removal of ruby 2.2 in the product and as a consequence, ruby 2.4 moving to be default would have conflicted with the old ruby 2.2 package. Nothing we wanted to see shipped to our users. Once the bot was fixed, we had a new snapshot coming up, 0719. The issues seen with the ruby migration were all gone, but now kernel 4.12 started to show its face: an installation running on a RAID10 setup simply started locking up. Of course, the kernel team is looking into that and as soon as a patch is ready, we will be able to ship 4.12. Until then, and to unblock Tumbleweed, we reverted back to kernel 4.11.8 (the one shipped in 0712 already). This is currently building – but I’m not yet daring to make a statement if this will be released or not. Time (and openQA) will tell.

In any case, staging work is still moving along in parallel too, and we are also preparing these updates:

  • Mozilla Firefox 52.2.1esr
  • KDE Applications 17.04.3
  • Libreoffice5.4.02, with google online capabilities, enabled
  • Linux kernel 4.12.x, that won’t crash RAID10 setups

If you have updates you want to see in Tumbleweed (or new packages) don’t be shy, speak up and help out with the packaging work.


face

Having publicly running web application always brings challenges in terms of security and in generally in handling untrusted data. Security wise Weblate has been always quite good (mostly thanks to using Django which comes with built in protection against many vulnerabilities), but there were always things to improve in input validation or possible information leaks.

When Weblate has joined HackerOne (see our first month experience with it), I was hoping to get some security driven core review, but apparently most people there are focused on black box testing. I can certainly understand that - it's easier to conduct and you need much less knowledge of the tested website to perform this.

One big area where reports against Weblate came in was authentication. Originally we were mostly fully relying on default authentication pipeline coming with Python Social Auth, but that showed some possible security implications and we ended up with having heavily customized authentication pipeline to avoid several risks. Some patches were submitted back, some issues reported, but still we've diverged quite a lot in this area.

Second area where scanning was apparently performed, but almost none reports came, was input validation. Thanks to excellent XSS protection in Django nothing was really found. On the other side this has triggered several internal server errors on our side. At this point I was really happy to have Rollbar configured to track all errors happening in the production. Thanks to having all such errors properly recorded and grouped it was really easy to go through them and fix them in our codebase.

Most of the related fixes have landed in Weblate 2.14 and 2.15, but obviously this is ongoing effort to make Weblate better with every release.

Filed under: Debian English SUSE Weblate


Wednesday
19 July, 2017


face

openSUSE-Heroes LogoMike Tyson might have said it best when he said “everyone has a plan ‘till they get punched in the mouth.”

Tyson’s point is that plans change, especially in the moment of executing a plan and that’s exactly what the openSUSE Heroes did with updating the wikis; minus the punch in the mouth.

Yesterday evening the Heroes planned to move and update some of the localized wikis. Things worked better and faster than expected, and in the end, the openSUSE Heroes moved all 18 localized wikis from Provo to Nuremberg and updated them to MediaWiki 1.27.

This means all openSUSE wikis are now running on MediaWiki 1.27 and support the features announced for the English wiki last week.

Christian Boltz, a humble openSUSE Hero with the power to mass migrate wikis, didn’t have time to change the <feed> tags to the new <rss> tags in all the wikis, which he plans to do in the next few days. Boltz did express a challenge to see what other superhuman powers exist.

“I won’t complain if someone is faster and does it in some of the wikis,” Botlz wrote in an email to the openSUSE Project mailing list.

Use the search to find pages containing “<feed”, and check https://en.opensuse.org/Help:RSS_feeds for the <rss> syntax.

Here is more information for those who are interested in statistics:

  • Moving 18 wikis in about 6 hours means about 20 minutes per wiki – can someone beat this?
  • During the move, the Heroes wrote about 500 lines on IRC to coordinate everything.
  • This helped to keep the read-only time of each wiki short. On average, each wiki was read-only for 30 minutes (again, can someone beat this?
  • The Heroes moved about 10 GB of uploaded files and 1.6 GB of mysql dumps from Provo to Nuremberg yesterday, which was sometimes “funny” because  the server in Provo limits the connection to 10 MB.

Have fun with the updated wikis and the upcoming openSUSE Leap 42.3!


face

We did it again! Yesterday, on 19th of July 2017, we had an extended deployment time because of an issue during the deployment. Though this time it "only" took 15 minutes;-) This sucks and that's why we want to give you some insight in what happened. Problems/Timeline 19-07-2017 12:37 UTC – We installed the newest OBS packages from our Unstable project and ran the migrations. 12:40 UTC – Installation and migration finished. We checked the...


Tuesday
18 July, 2017


Michael Meeks: 2017-07-18 Tuesday.

21:13 UTCmember

face
  • Mail chew, paperwork, lunch, build slides & projections, commerical call, did some memory profiling; always nice to spot a stray 1Gb of RAM allocated in error.
  • Really pleased to notice that ARM release their v8a machine-readable architecture spec/ - have always been irritated in the past to see gcc/as, valgrind, llvm, mono, etc. write their own hand-coded machine-code parsers / generators - would love those to be auto-generated from some decent descriptions for all of the modern, relevant CPU architectures.

face
Yesterday I got an invitation to the opendev conference (September 7-8, 2017) from the OpenStack foundation. The conference is about edge computing. 

While the topic itself is very interesting I was surprised that the opendev will be held in the U.S. (San Francisco, CA). I thought the foundation would have learned a lesson from the Boston summit this year. And as far as I understood it they decided to have currently no summits in the U.S. anymore until the political climate changed to allow risk free travel for all community members (see Kurt Garloff's talk at DOST around 8:45min). But it seems this applies only to the summits, very inconsistent! Some people would call it slightly duplicitous.

In light of the OpenStack Foundation's decision I'm still proud about the Ceph community. They decided with a clear statement to not held any event in the U.S. that requires travel for community members from foreign countries while there is the risk to potentially suffer harassment, digital privacy violations, or rejection at the border.

Monday
17 July, 2017


Michael Meeks: 2017-07-17 Monday.

21:00 UTCmember

face
  • Mail chew; product & consultancy calls, paperwork, board call, partner call. Played a little with Samuel at lunch & dinner.

face

Many people are anxiously awaiting for the release of openSUSE Leap 42.3 next week, but before the release arrives, you can prepare for a Release Party to celebrate the upcoming achievement with members of the open-source and openSUSE community.

Host your own Release Party. If you don’t know how to do this, there is a list of five steps to have a successful release party. Plus more details are listed below on how to have a fantastic party.

Selecting a good date and having some goodies to pass out to the party requires a bit of planning. The checklist below can help with planning the release party. If you plan on having a party, email ddemaio (at) suse.de well before the party to get some goodies to hand out to the party people. Please include “Leap 42.3 Party” in the subject line and include a mailing address and phone number.

checklist:

Find a date

The date of a party is best during a weekend (because it’s easier for people to join, since most people work during the week), but we all function differently. Find two alternative dates for the party if you want and use http://www.doodle.com/ to find a common date that works for most people.

Find a place

A cafe, bar or Linux group meetup location are all great places to have an event. A coffee and cake release party is just as fun as a beer and pizza release party.

Cake

It is not necessary to have a cake, but it sure is a lot of fun. You can also have openSUSE Cookies. On the Launch Party wiki page, there are two Release Parties list so far. One release party is in Nuremberg, Germany, on August 3 starting at 4 p.m. The other party is listed for FrOSCon and both will have a cake.

Pictures, pictures, pictures

Bring one or more cameras to take pictures or videos and post them to social media. Tag openSUSE on the photos you post on Twitter, Google +, Facebook or Diaspora.

Swag

PromoDVDs, webcam covers and stickers – If we can get it to you without too much red tape from governments, we will; just email ddemaio (at) suse.de with Release Party.

IMPORTANT TIP: Schedule your release party on the wiki and have a lot of fun!


Sunday
16 July, 2017


Michael Meeks: 2017-07-16 Sunday.

21:00 UTCmember

face
  • Got babes up, fine cooked breakfast with the wider family & friends, packed the car, bid 'byes, set off home via Sue's with T&B&S. Good to see the other nephews briefly, home - got unpacked, and T&B&S. to sleep.

Saturday
15 July, 2017


Michael Meeks: 2017-07-15 Saturday.

21:00 UTCmember

face
  • Up, enjoyed watching the extraordinary preparations of hair, faces, dresses for a slew of young beauties. Set off for the wedding venue, went rather slowly so as to be on time, arrived. A lovely, moving service. Off to Wyck Hill House for a fine reception - babes played quartet for light music; fine food, speeches, toasts - much dancing & chatting with interesting people until rather late.

Friday
14 July, 2017


Michael Meeks: 2017-07-14 Friday.

21:00 UTCmember

face
  • Everyone up early, quartet practice, out for a run with J. Mail chew. Set off early to collect babes from All Saints & Soham, drove at length to Swindon to stay at David & Gillian's house before Robert & Amelia's wedding. Fine food, home & company, lots of preparation - bouquet making, and so on. Up late drinking port & enjoying cheese with David.

face

openSUSE-Heroes LogoYou might have noticed some normally unwanted activity over the last weeks affecting the openSUSE infrastructure – resulting in reduced availability or downtime of the provided services.

Today we are happy to announce that most of the infrastructure work is done and the openSUSE Heroes together with the SUSE-IT team achieved a lot – ready to welcome openSUSE Leap 42.3 in time!

There might be still the one or the other small issue – but we expect that the majority of services will be stable for now (until we prove something different ;-)

The very good news: while Leap 42.3 is approaching, a couple of machines hosting openSUSE services are already using the latest 42.3 release in production!

That is what we call testing!

So while the Heroes lean back now and let the dust settle for a moment, we are really looking forward to the next steps that are on our TODO  list.

What was done in detail?

  1. SUSE-IT created a new network, which will allow the heroes to administrate all the servers on their own in the future.
  2. Two new load balancers (based on Leap 42.3) and a new login server (on 42.3 – a second will follow soon) were setup in this new network, ready to serve requests and handle authentication.
  3. The setup a new (42.3, you know) openVPN machine to allow the Heroes to get connected directly into “their” new network is mostly done, too.
  4. Moved over 30 virtual machines into this new network, adapting configurations, firewalls and all the other stuff that was needed.
  5. SUSE-IT also exchanged an important switch for us, that will allow all the servers above to connect to the outside with up to 10 Gigabit per second.
  6. The english openSUSE wiki was moved from Provo to Nuremberg, including a version upgrade and other big enhancements. A big THANK YOU here to our board member Christian Boltz, who also provided the requested Salt profiles to make the move of the next wikis even more easy!
  7. We forgot something in this list, for sure. So be prepared for more news soon :-)

 


face

Today, we will start a logo competition for openSUSE.Asia Summit 2017, which is going to be held in Tokyo, Japan. A logo is an essential material for the successful summit. As you have seen, the former openSUSE.Asia summits logos reflect the communities where the summit took place. Following tradition, we will have logo competition to collect great logos for this year’s summit.

The competition is open now and ends on August 14. The organizing team will send a “Geeko Mystery Box” as an appreciation for the best logo design.

Deadline: Monday, August 14

The Rules of the Contest are as follows:

  • The logo should be licensed under CC-BY-SA 4.0 and allow everyone to use the logo without attribution (BY) if your work is used as the logo of openSUSE.Asia Summit 2017. Note that the attribution is going to be shown on the summit website.
  • Design should be original and not copied.
  • Both monochromes and color formats are essential for submission.
  • Submissions must be in SVG format.
  • Design should reflect the openSUSE community in Asia.
  • The logo should avoid the following things:
    • Brand names or trademarks of any kind.
    • Illustrations that may consider inappropriate, offensive, hateful, tortuous, defamatory, slanderous or libelous.
    • Sexually explicit or provocative images.
    • Violence or weapons.
    • Alcohol, tobacco, or drug use imagery.
    • Discrimination based on race, gender, religion, nationality, disability, sexual orientation or age.
    • Bigotry, racism, hatred or harm against groups or individuals
    • Religious, political, or nationalist imagery.
  • The logo should follow “openSUSE Project Trademark Guidelines” published at https://en.opensuse.org/File:OpenSUSE_Trademark_Guidelines.pdf
  • The branding guidelines will be helpful to design your logo (optional)
    https://opensuse.github.io/branding-guidelines/

Please submit your design to opensuse-asia-17-contact@googlegroups.com with the following entries:

  • Vector file of the design with SVG format ONLY.
  • Bitmap of design in attachment — image size: 256*256 px at least, PNG format.
  • Less than 512 KB.
  • Your name and mail address to contact

The openSUSE.Asia Summit Committee will decide on the logos, subject to the condition, that the logo meets all the requirements. The final decision will be made by the openSUSE.Asia Summit Committee and it may not be the highest scored design.

We recommend the artist to use Inkscape, a powerful, free and open source vector graphics tool for all kinds of design.


face

Here we go again with a new report from the YaST trenches. This time with the storage reimplementation as the clear star of the show.

Storage reimplementation: the proposal adapts, you succeed

As we have announced in our previous sprints and as you probably already know, the YaST team is working hard to rewrite the whole storage stack on time for SLE15 and openSUSE Leap 15. As part of this reimplementation we have designed a brand new storage proposal that automagically offers the user the best combination of partitions and LVM volumes based on the current configuration of the system and the user preferences.

The storage proposal in action

When we are working with very small disks or with special technologies like DASD (which doesn’t accept more than three partitions by device), the storage proposal might not be able to generate a valid initial proposal honoring the initial requirements of the product (e.g. creating a separate home partition and enabling btrfs snapshots for the root partition in the openSUSE Leap case). Now the proposal is not limited to fail when it is not possible to satisfy the default product requirements. Before giving up, the new system looks for alternatives, like discarding the separate home partition or disabling snapshots. Moreover, now the proposal is able to automatically adjust the size requirements not only for root, but also for swap and home. And, of course, the guided setup continues there for fine tuning the proposal settings.

Desktop selection improvements

As our usual readers also know, we recently introduced a more fair desktop selection screen for openSUSE, both Leap 42.3 and Tumbleweed. We used part of the latest sprint to implement some feedback we gathered about the wording and behavior of that dialog.

Revamped desktop selection screen

That feedback gathering included some discussions on how to make user experience nicer after selecting one of the user interfaces available through the “custom” option. As a result, the awesome openSUSE crew created a new mechanism for selecting the default window manager on each graphical login, so YaST can delegate the details to the maintainers of those alternative interfaces.

How everything works now? Glad you asked. 🙂

If the user select KDE or GNOME in the YaST dialog, /etc/sysconfig/windowmanager is configured to point to that desktop by default. If the “custom” option is selected, then YaST does not enforce any interface in that file and the new mechanism comes into play. It relies in the default.desktop file, which defines the default window manager and can be managed by the common update-alternatives workflow. Meaning it can be easily tweaked by the package maintainers and by the users, specially since YaST includes a nice module for managing alternatives.

Storage reimplementation: improvements in the expert partitioner

Although, as explained above, we keep improving the storage automatic proposal to support more and more situations, we cannot ignore that flexibility and adaptability have always been two of the flagships of (open)SUSE. And one of the most prominent examples is the YaST Expert Partitioner.

As


Thursday
13 July, 2017


Michael Meeks: 2017-07-13 Thursday.

21:00 UTCmember

face
  • Mail chew, sync. with Eloy, partner call, got a few minutes of hacking in somehow. ESC call, left for music lessons, quartet practice, dropped M. straight back to her play with H. babes at home, back for a fine Aladdin play. Put babes to bed, wired up new lounge light, bed.

face

This past week’s openSUSE Tumbleweed snapshots have produced several fixes and improvements, including some for KDE users and those using AMD hardware.

Mesa 17.1.4 was among the most interesting packages in snapshot  20170710.

The update to Mesa brought an AMD drivers fix for the proper generation of Surrogate ID (SID) Tables and an RadeonSI improvements related to the Polaris 12 chip. Grep’s update to 3.1 makes it search for plain-text data sets faster. The snapshot also prepared for the 4.12 Linux Kernel with an update to linux-glibc-devel 4.12; Linux Kernel is expected to land in Tumbleweed before the end of the week. A fix for a “stupid” crash, according to the change log, with verbose mode and tone generation came with the update of mpg123 1.25.1 and the Newt library for color text mode and widget based user interfaces received improved handling of long strings.

Snapshot 20170709 brought very small changes to Wine and AqBanking. Wine 2.12 had performance improvements with async I/O and started MSI user interface support with the update to the newest version.

The 20170708 snapshot had a big change to libzypp 16.13.0. The new version update hides the switch of the default for zypper dup; after this update, zypper dup will default to –no-allow-vendor-change, which has been the recommended way for Tumbleweed for a long time now, according to an email post on the openSUSE Factory Mailing List from Dominique Leuenberger. That is if the user did not change /etc/zypp/zypp.conf -.

Snapshot 20170708 also provided several changes with dhcp 4.3.5, which now conducts a ping check (if ping checks are enabled) prior to offering an abandoned lease to a client; plus many, many more changes, bug fixes and improvements. Qt 5.9.1 libraries were a major part of the snapshot and included a few patches ARM and a patch to workaround a crash if compiled with GNU Compiler Collection 7; more info can be found in the release announcement. The update to the desktop calculator qalculate 0.9.12 made fixes to unit parsing in adaptive parsing mode as well as other build fixes. System administrators should checkout the updated version of the diagnostic, debugging and instructional userspace utility for Linux strace  4.18, which implemented basic decoding of netlink attributes.

AppStream 0.11.1 became available in the repositories in snapshot 20170707. The new AppStream contains refactoring of the XML/YAML parsers and some other changes that are more invasive and implementing read/write support for content ratings is one of the many new features added in the new version. The spell check dictionary for the German language received a bunch of new words the update to igerman98 version 20161207 and pitivi, a free and open-source video editor for Linux, updated to version 0.98.1, which provided a bug fix release to ensure compatibility with GStreamer.

Most of the updated packages associated with the 20170706 snapshot


face
A short reminder: the "Call for Presentations" deadline for  the next OpenStack Summit in Sydney, Australia (November 6-8, 2017) is less an a day away. 
If you would like to present in Sydney submit your proposal till July 14, 2017 at 11:59pm PDT (July 15, 2017 at 6:59am UTC).

Wednesday
12 July, 2017


Michael Meeks: 2017-07-12 Wedesday.

21:00 UTCmember

face
  • Mail, some patch review; poked at product features, pricing, bugs, sync. with Philippe.

face


As every year, also this year, I will be going to KDE’s yearly world summit, Akademy. This year, it will take place in Almería, Spain. In our presentation “Plasma: State of the Union“, Marco and I will talk about what’s going on in your favorite workspace, what we’ve been working on and what cool features are coming to you, and what our plans for the future are. Topics we will cover range Wayland, web browser integration, UI design, mobile and release and support planning. Our presentation will take place on Saturday at 11:05, right after the key note held by Robert Kaye. If you can’t make it to Spain next week, there will likely be video recordings, which I will post here as soon as they’re widely available.

Haste luego!


Tuesday
11 July, 2017


Michael Meeks: 2017-07-11 Tuesday.

21:00 UTCmember

face
  • Mail, admin, more mail, commercial call.

face

Escribí un artículo, Legacy Systems as Old Cities (Los Sistemas Heredados como Ciudades Viejas), para la revista The Recompiler. A 20 de años de su existencia, ¿es GNOME un sistema heredado? ¿Es diferente del software heredado para mainframes porque "todo el mundo" puede modificarlo? El software que vive por mucho tiempo, ¿tiene los mismos patrones de cambio que las ciudades y artefactos físicos? ¿Podemos aprender de los oficios de construcción y del urbanismo para mantener software a largo plazo? ¿Podemos convertir el software heredado en una buena herencia?

El artículo original en inglés está aquí.

Además, me permito esta oportunidad para recomendar la revista The Recompiler. Es la revista técnica más agradable que leo hoy en día. También tienen un podcast, que es excelente.

Aquí va una traducción al español del artículo.

Los Sistemas Heredados como Ciudades Viejas

Los sistemas heredados (legacy systems) tienen mala reputación entre los computólogos. Casi nadie quiere trabajar en software para mainframes en COBOL. Cuando compras un boleto de avión en persona, toda la mecanografía intensa que hace el agente de viajes se debe a SABRE, un sistema heredado que se usa para buscar y reservar boletos de avión; y uno puede pensar que la comisión que cobran los agentes de viajes se debe precisamente al trabajo que cuesta aprender a usar ese software. Puede ser que conozcamos historias de terror sobre una compañía tristona que simplemente no puede abandonar Windows 95, o Windows 3.1, porque tienen una pieza de infraestructura crítica que jamás se actualizó para correr sobre un sistema más nuevo.

Es difícil imaginarse tener la posibilidad de controlar el destino de esos sistemas. Son Demasiado Grandes Para Morir, y están plenamente fuera del alcance de la "gente de todos los días".

Pero, ¿qué hay de los sistemas heredados que están más cerca de nosotros? ¿Qué hay, en específico, del software libre que tiene una larga historia?

Hace unos 20 años leí un librito maravilloso que se llamaba "20 Años de Unix", y en ese entonces no era precisamente una edición reciente. En ese tiempo yo estaba involucrado en la creación del proyecto GNOME, el cual casi 20 años después puede presumir de ser ubicuo en el mundo del software libre, y que es parte del núcleo de los escritorios Linux. Puedes ver cómo se ve GNOME en esta página — hay un pantallazo general del escritorio ahí.

El GIMP (GNU Image Manipulation Program) es de 1995, y en ese tiempo el GIMP usaba Motif como biblioteca para su interfase gráfica. Aun entonces se consideraba a Motif como software heredado, indeseable y propietario. Los autores del GIMP escribieron desde cero otra biblioteca para interfases gráficas (GUIs), una biblioteca libre y llamada GTK+, de la cual salió GNOME en 1997. En 1998 ó 1999


face

From time to time, I will get a request for help with someone with their computer problems. Most of the time it is to fix a Windows issue but I don't do Windows. A coworker brought me his laptop and asked for Linux to be installed on it. He expressed his dislike for Windows 10 and all the background nonsense with advertising going on.

Normally, I would set someone up with Leap, but seeing as how I work with the guy, I thought I would see how installing Tumbleweed would go for him. I have had such a good experience with Tumbleweed, I wanted to see how it would work for a Linux newbie. I realize there was a bit of a risk putting a rolling release on a completely-new-to-Linux dude but as he is a coworker of which I know well, so troubleshooting would not be an issue and he was fine with the added complexity. If I didn't put Linux on this, the machine was going to end up in the garbage.

Specifications

AMD Quad-Core E2-6110 @ 1.50 Ghz
AMD Radeon R2 Graphics
16GB DDR3L Memory
1000 GB HDD

He upgraded the RAM from the original 4GB to improve performance for Windows 10 but he claimed it didn't improve the system.

Install Process

The fist thing I had to do was to change the boot order. In order to get into the BIOS/UEFI configuration I had to hit
F2 to enter Setup.

Changed the boot order to look to USB first. I will change this back but it is good to know that UEFI boot works no problem with openSUSE Tumbleweed. I didn't have to disable secure boot either.

After the install was complete, everything worked but the wifi adapter and the touchpad. The wifi adapter is the Broadcom BCM3142. Since I was performing the installation in a location that I didn't have Ethernet access, I had to tether the newly Linuxed machine to my Dell Latitude E6440 to access the internet.

Installing the driver was no problem. It was as simple as add the Packman repository and install the broadcom-wl driver:

sudo zypper --gpg-auto-import-keys ar -f http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/ Packman
sudo zypper ref
sudo zypper in broadcom-wl

Touchpad problems

The touchpad in the machine was not recognized by KDE Plasma. There was no input at all from the touchpad. I found it really odd as this was the first time I have experience this. I was determined to get it working for my coworker as he was quite enthusiastic about this operating system upgrade.

Doing a little digging on the Internet, I discovered that the touchpad was an Elantech Touchpad but oddly didn't show up even when I ran in command line:

xinput

I was very puzzled and after about an hour of additional information it looked like this touchpad driver should have been included since Linux Kernel 3.16. I didn

face

Members of the openSUSE will host a 3D Design and Printing Workshop in Nuremberg on Sept. 10 from 9:30 a.m. to 4 p.m at SUSE Headquarter.

The workshop, which as 60 spots available, will focus on teaching attendees on how to design and print 3D objects with open source tools like InkScape (easy enough for Kids) and FreeCAD.

“We will have a lot of fun at this workshop,” said Adrian Schroeter, an openSUSE member. “No matter the attendees experience of 3D design and printing, this workshop will give them the tools to make something and be creative. Plus, everybody gets the chance to take their own piece in printed form home.”

Those who are interested  are encouraged to attend the workshop that will teach both beginner and advanced level designing. Kids accompanied by an adult are welcomed to attend.

Attendees will learn about further tools needed for 3D printing and should come with a 3D model or STereoLithography file to modify. Attendees can find existing models at http://www.thingiverse.com.

There will be two LulzBot 3D Printers that were supplied by AlephObjects that people will be able to use for printing their projects.

Attendees should come with a laptop and have an openSUSE distribution installed or could also use openSUSE Leap from the Microsoft store . A list of tools for 3D design and printing can be found at https://en.opensuse.org/openSUSE:Science_Mechanical_engineering.

The workshop will try to support both German or English languages.

Please register at events.opensuse.org with your email address to receive more information before the workshop.


face

I just realized that I only tweeted about this a couple of months ago, but never blogged about it. Shame on me!

I wrote an article, Legacy Systems as Old Cities, for The Recompiler magazine. Is GNOME, now at 20 years old, legacy software? Is it different from mainframe software because "everyone" can change it? Does long-lived software have the same patterns of change as cities and physical artifacts? Can we learn from the building trades and urbanism for maintaining software in the long term? Could we turn legacy software into a good legacy?

You can read the article here.

Also, let me take this opportunity to recommend The Recompiler magazine. It is the most enjoyable technical publication I read. Their podcast is also excellent!

Update 2017/06/10 - Spanish version of the article, Los Sistemas Heredados como Ciudades Viejas


Monday
10 July, 2017


Michael Meeks: 2017-07-10 Monday.

21:00 UTCmember

face
  • Up early, quartet practice with H. and N. ran home from school with J. Mail chew, gerrit review, more mail. Product call, consultancy call, mail chew.

face

The English openSUSE wiki has been moved and updated  successfully. If you encounter any issue, please let us know by mail to admin(@)opensuse.org.

On July 11, the MediaWiki instance hosted behind en.opensuse.org was set to read only, with some slight downtimes.

The reason for the downtime was the move of the wiki from the old Provo cluster to the new Nuremberg opensuse network.

Together with the move, the wiki was updated from MediaWiki 1.22 to 1.27, and the VM hosting it from an old SLE version to openSUSE Leap 42.3 (yes, we are eating our own dogfood!)

New features are:

–    including files directly from github -> https://en.opensuse.org/Help:GitHub_inclusion

–    namespace-specific boilerplates (page templates) when creating new pages -> https://en.opensuse.org/Help:MultiBoilerplate

–    better search (elasticsearch) – now searching all namespaces, but with different weight

–    login is now done using the Auth_remoteuser extension – but still with your openSUSE login

–    support for several map providers

–    switched extension for RSS feed integration (this needs adjustments on the pages that include RSS feeds) -> https://en.opensuse.org/Help:RSS_feeds

–    watching a category (when pages get added to or removed from it) is now part of MediaWiki core

–    removal of Hermes notifications – MediaWiki’s own notifications work much better

Please be patient while we are doing the update. We’ll update this article and the status.opensuse.org webpage, plus we’ll send a followup mail to the opensuse-announce mailinglist when everything is done.

After updating the English wiki, we will let the dust settle for some days, and plan to update the localized wikis next week.


face

Here are the results the OBS frontend team has achieved in the last two weeks (2017-06-26 to 2017-07-07). Releases Release of OBS 2.8.2 We released another version of our OBS stable release, which fixes a bug that could cause trigger rebuild, wipe binaries and abort build commands to operate on linked projects. Features KIWI repositories editor We have been working on this feature for a while and now finished the first step. The KIWI repository...


Sunday
09 July, 2017


Michael Meeks: 2017-07-09 Sunday.

21:00 UTCmember

face
  • Up lateish; off to All Saints for Miriam's leaving service; and picnic lunch & school graduation ceremony; ringing the bell as they leave - only E. left now.
  • Home; set too at E's room making it suitable for Tom, Becky & Samuel next week. Played with babes variously, tried to separate H's rather broken S4 display from the frame assembly for N's phone-of-pieces - nearly (but not quite) succeeding (accidentally severed the connector in the process - bother).
  • Dinner, put babes to bed; admired Chris & Allison's extension.

Saturday
08 July, 2017


Michael Meeks: 2017-07-08 Saturday.

21:00 UTCmember

face
  • Up lateish, cleaned the home with J., mended the hoover, worked on un-completed task list. H. swiming with Alex & Madeline, Vive playing on their return. Dis-assembled part of E's bunk-bed. BBQ, practiced Quartet late, put babes to bed. Stayed up mending J's phone with N., and H. installing a new screen.

Older blog entries ->