買了一台低階筆電 ASUS X553M
安裝了 openSUSE 13.2 KDE
一切都像以往一樣熟悉...

只有在 fn + f5 ， fn + f6 控制螢幕亮度時不生效
查詢 google 後也順利解決了
在 kernel 啟動參數中加上

video.use_native_backlight=1 acpi_osi=

編輯

/etc/X11/xorg.conf.d/20-intel.conf

內容為

Section "Device"
        Identifier "card0"
        Driver "Intel"
        Option "Backlight" "intel_backlight"
        BusID "PCI:0:2:0"
EndSection

A new version of mdds is out, and this time, we’ve decided to bump up the version to 1.0.0. As always, you can download it from the project’s main page.

Here is the highlight of this release.

First off, C++11 is now a hard requirement starting with this release. It’s been four years since the C++11 standard was finalized. It’s about time we made this a new baseline.

Secondly, we now have an official API documentation. It’s programatically generated from the source code documentation via Doxygen, Sphinx and Breathe. Huge thanks to the contributors of the aforementioned projects. You guys make publishing API documentation such a breathe (no pun intended).

This release has finally dropped mixed_type_matrix which has been deprecated for quite some time now in favor of multi_type_matrix.

The multi_type_vector data structure has received some performance optimization thanks to patches from William Bonnet.

Aside from that, there is one important bug fix in sorted_string_map, to fix false positives due to incorrect key matching.

API versioning

One thing I need to note with this release is the introduction of API versioning. Starting with this release, we’ll use API versions to flag any API-incompatible releases. Going forward, anytime we introduce an API-incompatible change, we’ll use the version of that release as the new API version. The API version will only contain major and minor components i.e. API versions can be 1.0, 1.2, 2.1 etc. but never 1.0.6, for instance. That also implies that we will never introduce API-incompatible changes in the micro releases.

The API version will be a part of the package name. For example, this release will have a package name of mdds-1.0 so that, when using tools like pkg-config to query for compiler/linker flags, you’ll need to query for mdds-1.0 instead of simply mdds. The package name will stay that way until we have another release with an API-incompatible change.

Disclaimer: I am aware that python does not allow easy installation of 2 libraries in parallel. It is just an example.

Let’s say you have an upstream requirement "needs pyfoo >= 1.6.0 but smaller than 2". Sounds easy right? Our naive solution will be:

Requires: python-pyfoo >= 1.6.0
Requires: python-pyfoo < 2

so far … so good. If your repository has only one version of pyfoo available we will probably get the package you want. now lets say we have more than one version available.

In OBS we use source tarballs everywhere to build rpms (and debs) from.

This has at least two major downsides:

1. Storing all old tar files takes up a lot of disk space
2. OBS workflows with .tar files and patches are rather different and somewhat disconnected from the git workflows we usually use everywhere else these days. E.g. for the SUSE OpenStack Cloud team we have a “trackupstream” jenkins job, that pulls the latest git version into a tarball once every day.

Fedora already keeps their metadata in git, but only a hash of the tarball.

So as one first step, I used two rather different projects to see how different the space usage would be. On the slow side I used 20 gtk2 tarballs from the last 5 years and on the fast side, I used 31 openstack-nova tarballs from Cloud:OpenStack:Master project from the last 5 months.
I used scripts that uncompressed each tarball, added it to a git repo and used git gc to trigger git’s compression.

Here are the resulting cumulative size graphs:

The raw numbers after 20 tarballs: for nova the ratio is 89772:7344 = 12.2 and for gtk2 the ratio is 296836:53076 = 5.6

What do you think: would it be worth the effort to use more git in our OBS workflows?

Do we care about being able to reproduce the original tarballs? While this is possible, it has some challenges in differing file-ordering, timestamps, file-ownerships and compression levels.
Or would it be enough if OBS converted a tarball into a signed commit (so it cannot be forged without people being able to notice)?

Do you know of a tool that can uncompress tarballs in a way that allows to track the content as single files, and allows to later re-create the original verbatim tarball, such that upstream signatures would still match?

It is already a week since I am back from the great LibreOffice Conference in Aarhus. I enjoyed it a lot - talked to lots of people [eg. met Heiko for the first time in person - after having spent quite some time with him over hangouts :-)], listened to many nice presentations, gave my talks, and - even managed to find some time for the late night's hacking. Oh, and the train there and back was a good choice too - I have travelled with Stanislav who's translating & managing the Czech translations; and on the way back we have also met Jos.

Before I tell you about the Table Styles in Writer, the feature I was working on, let me share the slides from my presentations. First of all, I presented work of my GSoC students, Nathan Yee and Krisztian Pinter, during the GSoC panel:

Click the slide to see the presentation.

Then I talked about the recent achievements & plans of the LibreOffice Design team:

Click the slide to see the presentation.

Then on Thursday, I talked about what we have done in VCL, our graphics toolkit, to be able to make our rendering double-buffered:

Click the slide to see the presentation.

 

Table Styles in Writer

And now - the Table Styles in Writer. It is a feature that we have missed for a long time. In LibreOffice, we have the Table -> AutoFormat..., but applies the formatting only once; after you modify the table (like insert rows / columns) later, you basically destroy the look of the table.

During summer 2013, Alex Ivan was working on implementing the table styles as GSoC project. I rebased his work to the current master, and made it to work again. Unfortunately, the approach there turned out to be very aggressive - the changes first destroyed the Table AutoFormat feature, and then started building the Table Styles. This means that we could merge that only after we have the import and export for Table Styles - but the GSoC work did not get that far.

I reconsidered the approach, and tried to find a way that implements the core of the Table Styles functionality without destroying the Table AutoFormat - and it worked :-)

I have pushed the results to master. Now, when you apply the Table AutoFormat in Writer, it behaves as a Table Style: When you insert more rows/columns, they still keep the correct formatting, similarly deleting, or splitting tables keeps the table formatted. Direct formatting is applied over the style too, and you can clear it via "Clear Direct Formatting".

 

Further work

Loading/saving is not implemented though, so once you save the table with Table Style, it turns into a "normal" AutoFormat - the next time you open it, you see the formatting, but it is "static", ie. works as before the Table Styles work.

I hope to get the load/save done before 5.1; and there's also lots to be improved in the UI of Table Styles - but I believe the current state is already an improvement, and a step in the right direction.

There's a tutorial how to create an openSUSE Tumbleweed SD card with MATE. You can follow this tutorial without installing MATE but keep it headless. You can download the image from openSUSE-Tumbleweed-BananaPi-headless-20150927.tar.xz (username: root, password: linux) and continue this tutorial.

Here we'll see how to install ownCloud on openSUSE for Banana Pi M1.

At the end of this tutorial will be a link to the image with ownCloud. Please use an SD card minimum 2GB and re-partition the SD card or use a USB stick to save ownCloud data directory.

Let's start with the procedure.

1. Install ownCloud from the repository. Choose the repository because you can have automatic updates.


Don't be scared because this is factory repository. This is the official from ownCloud and it's the only one that is for ARM boards.

This will install all nessesary files. It will install apache2 and mariadb. At the end, it'll ask you if you want to see info about seting up mariadb.


Regarding the servers apache and mariadb. If you're the only one user for ownCloud and don't have problem with speed, then you can use sqlite. If you have more users for the instance, then it's better to use mariadb. It's the same with apache. For lighter installations, you can use lighttpd or ngnix. Here I used apache2 but about database, it's up to you. You can either use sqlite or setup a mariadb darabase.

To setup a mariadb database, follow the commands.


2. Change the file php.ini.


and change the strings (you can search by pressing control+w).


3. Start the webserver.


4. Create the data directory

It is recommended to use a data directory located on another partition of your SD card or a USB stick. The image requires minimum 2GB SD card, so you won't have enough storage to save your data.

Let's say you have a USB and you mounted under /mnt/USB folder. Create a directory and also give the right permissions.


5. Final ownCloud installation.

Open your browser to the IP of your Banana Pi


Set a username/password for administrator. Choose a username other than admin, root, administrator, superuser because of your safety.
Then you have to set the date folder (remember our example is /mnt/USB/owncloud_data)
Choose if you want mariadb or sqlite.

If it's mariadb, then you should create the database


DATABASE: owncloudb
USER: ocuser
PASSWORD: dbpass
HOST: localhost

and you're all set.

You can download the file openSUSE-Tumbleweed-20150930-BananaPi-ownCloud-8.1.3.tar.xz and just setup ownCloud as described on fifth step.

Who those, who won’t use terminal to compile program I’ve created tao-makefile-ui.

Tao-makefile-ui is a simple tool, which aims allow to go through each step of compiling program in graphical user interface. Program will run autogen.sh, configure and make. It allows to select make target and save targets list to file. It also allows to change variables of Makefile.

There’s package for OpenSUSE. You can watch the video demonstrating tao-makefile-ui here

Thanks!

AMD Catalyst 15.9 (fglrx 15.201.1151) wurde veröffentlicht und unterstützt Grafikkarten ab Radeon HD 5000 und höher. Das Skript makerpm-amd-15.9.sh steht ab sofort zum Download zur Verfügung und unterstützt openSUSE 11.4, 12.1, 12.2, 12.3, 13.1, 13.2 und Tumbleweed sowie bis Kernel 4.2 (offiziell nur bis Kernel 3.19).

Wichtiger Hinweis: Die erste Beta-Version von openSUSE Leap (zukünftige openSUSE 42.1) wurde vor wenigen Tagen veröffentlicht. Jedoch wurde der AMD Treiber noch nicht an die neue Version angepasst. Dazu werde ich mich in den nächsten Tagen näher beschäftigen und ein weiteres Update bereitstellen.

Ein weiterer Hinweis: Nach einigen Experimenten mit dem GNOME Desktopmanager konnte ich ihn nicht zum Laufen bringen. Da scheint tatsächlich etwas im Argen zu sein. Hierzu werde ich die AMD Entwickler kontaktieren. Als Workaround empfehle ich für GNOME einen anderen Desktopmanager wie z.B. lightdm bis das Problem behoben ist.

[UPDATE 09.11.2015]
Das Packaging Script wurde aktualisiert. Es wird ab sofort openSUSE Leap 42.1 und Kernel 4.3 unterstützt. Have a lot of fun!
[/UPDATE 09.11.2015]

Gelöste Probleme:

• [425910] Driver installation sometimes fails on Ubuntu 14.04.3
• [424450] Company of Heroes® 2 – Game crashes while running the performance test
• [424794] Middle-earth: Shadow of Mordor – Corruption observed in game
• [424882] DIRT® Showdown – Corruption observed in game
• [425234] DIRT® Showdown – Game crashes after the loading screen
• [424802] DOTA 2 – Application hang observed while exiting the game
• [424255] AMD Catalyst Installer removing EGL links resulting in Xserver/Xorg load failure
• [423471] Unable to switch desktop mode after installing AMD Catalyst driver
• [423735] Renaming Counter-Strike: GO and other Steam game binary improves performance

Bekanntes Problem:

• [419960]: Vari-Bright on some configurations is not decreasing brightness as expected

Link: AMD Catalyst 15.9 Release Notes

Folgende Steam-Spiele habe ich getestet und laufen mit diesem Treiber (Fettdruck = Neu):

• A Bird Story
• A Virus Named TOM
• AaaaaAAaaaAAAaa…
• Age of Wonders III
• AI War: Fleet Command
• Amnesia: The Dark Descent
• Anomaly 2
• Anomaly Defenders
• Anomaly Korea
• Antichamber
• Aquaria
• Avadon: The Black Fortress
• Awesomenauts
• Bastion
• Battle Group 2
• Beatbuddy: Tale of the Guardians
• BIT.TRIP Presents… Runner 2: Future Legend of Rhythm
• Borderlands 2
• Breach & Clear
• Bridge Constructor
• Bridge Constructor Playground
• Broken Sword: Director’s Cut
• Broken Sword 2 – the Smoking Mirror: Remastered
• Broken Sword 5 – the Serpent’s Curse
• Brütal Legend
• Cave Story+
• Cities in Motion 2
• Cities: Skylines
• Closure
• Cogs
• Costume Quest
• Counter-Strike: Global Offensive
• Creeper World III: Arc Eternal
• Crusader Kings II
• Cubemen
• Cubemen 2
• Darwinia
• DeadCore
• Defcon
• Defense Grid 2
• Distance
• Duke Nukem 3D: Megaton Edition
• Dungeon Defenders
• Dust: An Elysian Tail
• Dustforce
• Eets Munchies
• Euro Trucker Simulator
• Europa Universalis IV
• FEZ
• From The Depths
• Frozen Synapse
• FTL: Faster Than Light
• Galcon Fusion
• Galcon Legends
• Game Dev Tycoon
• Gemini Rue
• Gratuitous Space Battles
• Guacamelee! Gold Edition
• Half-Life 2: Deathmatch
• Half-Life 2: Lost Coast
• Halfway
• Hero Academy
• HOARD
• Hotline Miami
• Ironclad Tactics Deluxe
• Ittle Dew
• Jack Lumber
• Jagged Alliance – Back in Action
• Joe Danger 2: The Movie
• Kerbal Space Program
• Killing Floor
• Kinetic Void
• Kingdom Rush
• Knights of Pen and Paper +1 Edition
• Legend of Grimrock
• LIMBO
• Little Inferno
• LUFTRAUSERS
• Lux Delux
• Mark of the Ninja
• Metro: Last Light Redux
• Mini Metro
• Monaco: What’s Yours Is Mine
• Monstrum
• Multiwinia
• Natural Selection 2
• Nihilumbra
• Nightside
• Not The Robots
• Nuclear Dawn
• Organ Trail: Director’s Cut
• Painkiller Hell & Damnation
• Planet Explorers
• Portal
• Portal 2
• Postal 2
• Prison Architect
• Project Zomboid
• Psychonauts
• Puddle
• Ravensword: Shadowlands
• Rising World
• Rochard
• Rocketbirds: Hardboiled Chicken
• Sanctum 2
• Savage Lands
• Savant – Ascent
• Serious Sam 3: BFE
• Shadow Warrior Classic Redux
• Shadowrun Returns
• Shank 2
• Shatter
• Sid Meier’s Civilization® V
• Sir, You Are Being Hunted
• Skulls of the Shogun
• Small World 2
• Snapshot
• Solar 2
• Solar Flux
• Space Hulk
• Space Pirates and Zombies
• Spec Ops: The Line
• Splice
• Starmade
• Stealth Bastard Deluxe
• Strike Suit Zero
• Superbrothers: Sword & Sworcery EP
• Surgeon Simulator 2013
• Survivor Squad
• Syder Arcade
• Symphony
• Tetrobot and Co.
• The Bard’s Tale
• The Book of Unwritten Tales
• The Book of Unwritten Tales: The Critter Chronicles
• The Bridge
• The Last Federation
• The Raven – Legacy of a Master Thief
• The Shivah
• The Swapper
• The Witcher 2: Assassins of Kings Enhanced Edition
• Thomas Was Alone
• Ticket to Ride
• Titan Attacks
• Toast Time
• To the Moon
• Toki Tori 2+
• Torchlight II
• Train Fever
• Transistor
• Trine 2: Complete Story
• Tropico 5
• Unity of Command: Stalingrad Campaign + DLC
• Uplink
• VVVVVV
• Waking Mars
• Wargame: Airland Battle
• Wargame: European Escalation
• Wargame: Red Dragon
• Wizorb
• Worms Reloaded
• XCOM: Enemy Unknown
• X-Plane 10 Global (64-bit)
• Zen Bound 2

Eine kleine Bitte habe ich: Wenn irgendwelche Probleme mit dem Treiber auftauchen, scheut euch nicht mir zu berichten (Ich nehme deutsche und englische Bugreports gerne entgegen). Ich werde versuchen, soweit es mir möglich ist, den gemeldeten Fehler zu reproduzieren. Zusammen mit den nötigen System-Informationen werde ich mich direkt an die richtige Stelle bei AMD wenden, um den Bug in der nächsten Treiber-Version beheben zu lassen. Danke schön.

Für Benutzer älterer AMD Grafikkarten (Radeon HD Serie 2000 – 4000) wird dringend die Installation dieses Treibers abgeraten. openSUSE bringt bereits für ältere Grafikkarten den freien Radeon-Treiber mit. Um regelmäßig Verbesserungen am freien Radeon-Treiber zu erhalten, ist die Installation eines neuen Kernel unumgänglich.

Downloads:

• Skript: makerpm-amd-15.9.sh
• SHA1: makerpm-amd-15.9.sh.sha1

Installationsanleitung:
http://de.opensuse.org/SDB:AMD/ATI-Grafiktreiber#Installation_via_makerpm-amd-Skript

Installation guide (English):
http://en.opensuse.org/SDB:AMD_fglrx#Building_the_rpm_yourself

Über das makerpm-amd-Skript

Das Skript makerpm-amd-15.9.sh ist sehr mächtig, robust und läuft vollautomatisch. Der AMD-Installer wird automatisch heruntergeladen, falls er nicht schon im Verzeichnis liegt. Zudem wird geprüft, ob die Grafikkarte vom Treiber unterstützt wird. Auf Wunsch wird nach dem Bau des RPM-Packages der fglrx-Treiber installiert.

Folgende Argumente können dem Skript übergeben werden:

-b	Nur das RPM-Package bauen (Standard)
-c <type>	Nur X-Server konfigurieren. Monitor-Typ: single = 1 Monitor, dual = 2 Monitore (Wichtig: Nur ausführen, wenn es Probleme mit der Standardkonfiguration des X-Servers auftreten)
-d	Nur den AMD-Installer downloaden
-i	Das RPM-Package bauen und installieren bzw. updaten
-igf/–install-gdm-fix	installiert einen Fix, um den Treiber mit dem GNOME Desktopmanager (gdm) läuffähig zu machen
-kms <yes|no>	Kernel-Mode-Setting (KMS) aktivieren oder deaktivieren
-nohw	Hardware-Erkennung explizit ausschalten. (z.B. beim Bau in einer VM)
-old2ddriver <yes|no>	den alten 2D-Treiber aktivieren oder deaktivieren
-r|–report	erstellt ein Report und speichert diese in eine Datei namens amd-report.txt
-u|–uninstall	entfernt AMD Catalyst restlos vom System. Zuerst wird das fglrx-Package (falls vorhanden) vom System deinstalliert. Danach werden vorhandene AMD-Dateien und -Verzeichnisse entfernt. Hinweis: Falls das Rebuild-Skript installiert wurde, wird es ebenfalls entfernt und das Initskript /etc/init.d/xdm wiederhergestellt.
-ugf/–uninstall-gdm-fix	entfernt den Fix, dass den Treiber mit dem GNOME Desktopmanager (gdm) läuffähig macht
-ur|–uploadreport	wie Option –report nur zusätzlich wird der Report auf einem NoPaste-Service sprunge.us hochgeladen und gibt bei Erfolg den Link zurück.
-h	Die Hilfe anzeigen lassen
-V	Version des Skript anzeigen

Hilfe, es funktioniert nicht!

Bitte haltet folgende Regel ein:

1. Bei der Eingabe der Befehle auf mögliche Tippfehler überprüfen.
2. Möglicherweise ist die Lösung für das Problem im Wiki vorhanden.
3. In Kommentaren lesen, ob eine Lösung zu einem Problem bereits existiert.

Wenn keines der o.g. Regel greift, dann könnt ihr mit eurem Anliegen an mich wenden. Damit ich euch helfen kann, müsst ihr erst vorarbeiten. Bitte ladet euch das Skript makerpm-amd-15.9.sh herunter und erstellt einen Report von eurem System in der Konsole:

su -c 'sh makerpm-amd-15.9.sh -ur'

Das Skript lädt das Report auf sprunge.us hoch und gibt anschließend einen Link aus. Diesen Link postet ihr in eurem Kommentar zusammen mit einer Beschreibung zu eurem Problem an mich. Ich werde mir euren Report anschauen und Hilfestellung geben, wo evtl. das Problem liegen könnte.

Feedbacks sind wie immer willkommen.

Любопытно, но готового пакета с Popcorn-Time для OpenSUSE не нашлось во всей OBS. В сети имеется установочный скрипт, который по идее должен ставить приложение, но скрипт, увы, устарел и больше не работает. Если вы хотите поставить Popcorn-Time вручную, то это сделать совсем не сложно. Но гораздо удобнее всё же воспользоваться обновлённым скриптом, который я сделал. Скрипт протестирован на OpenSUSE 13.2 64 bit.

Скачать.