1 <?xml version=
"1.0" encoding=
"utf-8"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/' xmlns:
atom=
"http://www.w3.org/2005/Atom">
4 <title>Petter Reinholdtsen
</title>
5 <description></description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
7 <atom:link href=
"http://people.skolelinux.org/pere/blog/index.rss" rel=
"self" type=
"application/rss+xml" />
10 <title>Sales number for the Free Culture translation, first half of
2016</title>
11 <link>http://people.skolelinux.org/pere/blog/Sales_number_for_the_Free_Culture_translation__first_half_of_2016.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sales_number_for_the_Free_Culture_translation__first_half_of_2016.html
</guid>
13 <pubDate>Fri,
5 Aug
2016 22:
45:
00 +
0200</pubDate>
14 <description><p
>As my regular readers probably remember, the last year I published
15 a French and Norwegian translation of the classic
16 <a href=
"http://www.free-culture.cc/
">Free Culture book
</a
> by the
17 founder of the Creative Commons movement, Lawrence Lessig. A bit less
18 known is the fact that due to the way I created the translations,
19 using docbook and po4a, I also recreated the English original. And
20 because I already had created a new the PDF edition, I published it
21 too. The revenue from the books are sent to the Creative Commons
22 Corporation. In other words, I do not earn any money from this
23 project, I just earn the warm fuzzy feeling that the text is available
24 for a wider audience and more people can learn why the Creative
25 Commons is needed.
</p
>
27 <p
>Today, just for fun, I had a look at the sales number over at
28 Lulu.com, which take care of payment, printing and shipping. Much to
29 my surprise, the English edition is selling better than both the
30 French and Norwegian edition, despite the fact that it has been
31 available in English since it was first published. In total,
24 paper
32 books was sold for USD $
19.99 between
2016-
01-
01 and
2016-
07-
31:
</p
>
34 <table border=
"0">
35 <tr
><th
>Title / language
</th
><th
>Quantity
</th
></tr
>
36 <tr
><td
><a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">Culture Libre / French
</a
></td
><td align=
"right
">3</td
></tr
>
37 <tr
><td
><a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Fri kultur / Norwegian
</a
></td
><td align=
"right
">7</td
></tr
>
38 <tr
><td
><a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">Free Culture / English
</a
></td
><td align=
"right
">14</td
></tr
>
41 <p
>The books are available both from Lulu.com and from large book
42 stores like Amazon and Barnes
&Noble. Most revenue, around $
10 per
43 book, is sent to the Creative Commons project when the book is sold
44 directly by Lulu.com. The other channels give less revenue. The
45 summary from Lulu tell me
10 books was sold via the Amazon channel,
10
46 via Ingram (what is this?) and
4 directly by Lulu. And Lulu.com tells
47 me that the revenue sent so far this year is USD $
101.42. No idea
48 what kind of sales numbers to expect, so I do not know if that is a
49 good amount of sales for a
10 year old book or not. But it make me
50 happy that the buyers find the book, and I hope they enjoy reading it
51 as much as I did.
</p
>
53 <p
>The ebook edition is available for free from
54 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">Github
</a
>.
</p
>
56 <p
>If you would like to translate and publish the book in your native
57 language, I would be happy to help make it happen. Please get in
63 <title>Vitenskapen tar som vanlig feil igjen - relativt feil
</title>
64 <link>http://people.skolelinux.org/pere/blog/Vitenskapen_tar_som_vanlig_feil_igjen___relativt_feil.html
</link>
65 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Vitenskapen_tar_som_vanlig_feil_igjen___relativt_feil.html
</guid>
66 <pubDate>Mon,
1 Aug
2016 16:
00:
00 +
0200</pubDate>
67 <description><p
>For mange år siden leste jeg en klassisk tekst som gjorde såpass
68 inntrykk på meg at jeg husker den fortsatt, flere år senere, og bruker
69 argumentene fra den stadig vekk. Teksten var «The Relativity of
70 Wrong» som Isaac Asimov publiserte i Skeptical Inquirer i
1989. Den
71 gir litt perspektiv rundt formidlingen av vitenskapelige resultater.
72 Jeg har hatt lyst til å kunne dele den også med folk som ikke
73 behersker engelsk så godt, som barn og noen av mine eldre slektninger,
74 og har savnet å ha den tilgjengelig på norsk. For to uker siden tok
75 jeg meg sammen og kontaktet Asbjørn Dyrendal i foreningen Skepsis om
76 de var interessert i å publisere en norsk utgave på bloggen sin, og da
77 han var positiv tok jeg kontakt med Skeptical Inquirer og spurte om
78 det var greit for dem. I løpet av noen dager fikk vi tilbakemelding
79 fra Barry Karr hos The Skeptical Inquirer som hadde sjekket og fått OK
80 fra Robyn Asimov som representerte arvingene i Asmiov-familien og gikk
81 igang med oversettingen.
</p
>
83 <p
>Resultatet,
<a href=
"http://www.skepsis.no/?p=
1617">«Relativt
84 feil»
</a
>, ble publisert på skepsis-bloggen for noen minutter siden.
85 Jeg anbefaler deg på det varmeste å lese denne teksten og dele den med
86 dine venner.
</p
>
88 <p
>For å håndtere oversettelsen og sikre at original og oversettelse
89 var i sync brukte vi git, po4a, GNU make og Transifex. Det hele
90 fungerte utmerket og gjorde det enkelt å dele tekstene og jobbe sammen
91 om finpuss på formuleringene. Hadde hosted.weblate.org latt meg
92 opprette nye prosjekter selv i stedet for å måtte kontakte
93 administratoren der, så hadde jeg brukt weblate i stedet.
</p
>
98 <title>Techno TV broadcasting live across Norway and the Internet (#debconf16, #nuug) on @frikanalen
</title>
99 <link>http://people.skolelinux.org/pere/blog/Techno_TV_broadcasting_live_across_Norway_and_the_Internet___debconf16___nuug__on__frikanalen.html
</link>
100 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Techno_TV_broadcasting_live_across_Norway_and_the_Internet___debconf16___nuug__on__frikanalen.html
</guid>
101 <pubDate>Mon,
1 Aug
2016 10:
30:
00 +
0200</pubDate>
102 <description><p
>Did you know there is a TV channel broadcasting talks from DebConf
103 16 across an entire country? Or that there is a TV channel
104 broadcasting talks by or about
105 <a href=
"http://beta.frikanalen.no/video/
625529/
">Linus Torvalds
</a
>,
106 <a href=
"http://beta.frikanalen.no/video/
625599/
">Tor
</a
>,
107 <a href=
"http://beta.frikanalen.no/video/
624019/
">OpenID
</A
>,
108 <a href=
"http://beta.frikanalen.no/video/
625624/
">Common Lisp
</a
>,
109 <a href=
"http://beta.frikanalen.no/video/
625446/
">Civic Tech
</a
>,
110 <a href=
"http://beta.frikanalen.no/video/
625090/
">EFF founder John Barlow
</a
>,
111 <a href=
"http://beta.frikanalen.no/video/
625432/
">how to make
3D
112 printer electronics
</a
> and many more fascinating topics? It works
113 using only free software (all of it
114 <a href=
"http://github.com/Frikanalen
">available from Github
</a
>), and
115 is administrated using a web browser and a web API.
</p
>
117 <p
>The TV channel is the Norwegian open channel
118 <a href=
"http://www.frikanalen.no/
">Frikanalen
</a
>, and I am involved
119 via
<a href=
"https://www.nuug.no/
">the NUUG member association
</a
> in
120 running and developing the software for the channel. The channel is
121 organised as a member organisation where its members can upload and
122 broadcast what they want (think of it as Youtube for national
123 broadcasting television). Individuals can broadcast too. The time
124 slots are handled on a first come, first serve basis. Because the
125 channel have almost no viewers and very few active members, we can
126 experiment with TV technology without too much flack when we make
127 mistakes. And thanks to the few active members, most of the slots on
128 the schedule are free. I see this as an opportunity to spread
129 knowledge about technology and free software, and have a script I run
130 regularly to fill up all the open slots the next few days with
131 technology related video. The end result is a channel I like to
132 describe as Techno TV - filled with interesting talks and
133 presentations.
</p
>
135 <p
>It is available on channel
50 on the Norwegian national digital TV
136 network (RiksTV). It is also available as a multicast stream on
137 Uninett. And finally, it is available as
138 <a href=
"http://beta.frikanalen.no/
">a WebM unicast stream
</a
> from
139 Frikanalen and NUUG. Check it out. :)
</p
>
144 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
145 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
146 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
147 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
148 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
149 to be a slight challenge. Here is the recipe if I ever need to do it
150 again. It all started by me wanting to try the recipe to set up
151 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
152 hardened Android installation
</a
> from the Tor project blog on a
153 device I had access to. It is a old mobile phone with a broken
154 microphone The initial idea had been to just
155 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
156 CyanogenMod on it
</a
>, but did not quite find time to start on it
157 until a few days ago.
</p
>
159 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
160 loader (press volume down and power at the same time), (
2) select
161 'fastboot
' before (
3) connecting the device via USB to a Linux
162 machine, (
4) request the device identifier token by running
'fastboot
163 oem get_identifier_token
', (
5) request the device unlocking key using
164 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
165 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
167 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
168 or newer, and the device I was working on had
2.00.0027. This
169 apparently can be easily fixed by downloading a Windows program and
170 running it on your Windows machine, if you accept the terms Microsoft
171 require you to accept to use Windows - which I do not. So I had to
172 come up with a different approach. I got a lot of help from AndyCap
173 on #nuug, and would not have been able to get this working without
176 <p
>First I needed to extract the hboot firmware from
177 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
178 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
179 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
180 project named unruu
</a
> using libunshield. The unshield tool did not
181 recognise the file format, but unruu worked and extracted rom.zip,
182 containing the new hboot firmware and a text file describing which
183 devices it would work for.
</p
>
185 <p
>Next, I needed to get the new firmware into the device. For this I
186 followed some instructions
187 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
188 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
189 machine with Debian testing:
</p
>
192 adb reboot-bootloader
193 fastboot oem rebootRUU
194 fastboot flash zip rom.zip
195 fastboot flash zip rom.zip
197 </pre
></p
>
199 <p
>The flash command apparently need to be done twice to take effect,
200 as the first is just preparations and the second one do the flashing.
201 The adb command is just to get to the boot loader menu, so turning the
202 device on while holding volume down and the power button should work
205 <p
>With the new hboot version in place I could start following the
206 instructions on the HTC developer web site. I got the device token
210 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
213 <p
>And once I got the unlock code via email, I could use it like
217 fastboot flash unlocktoken Unlock_code.bin
218 </pre
></p
>
220 <p
>And with that final step in place, the phone was unlocked and I
221 could start stuffing the software of my own choosing into the device.
222 So far I only inserted a replacement recovery image to wipe the phone
223 before I start. We will see what happen next. Perhaps I should
224 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
229 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
230 <link>http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html
</link>
231 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html
</guid>
232 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
233 <description><p
>For a while now, I have wanted to test
234 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
235 said to provide end to end encrypted communication and several of my
236 friends and family are already using it. As I by choice do not own a
237 mobile phone, this proved to be harder than expected. And I wanted to
238 have the source of the client and know that it was the code used on my
239 machine. But yesterday I managed to get it working. I used the
240 Github source, compared it to the source in
241 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
242 Signal Chrome app
</a
> available from the Chrome web store, applied
243 patches to use the production Signal servers, started the app and
244 asked for the hidden
"register without a smart phone
" form. Here is
245 the recipe how I did it.
</p
>
247 <p
>First, I fetched the Signal desktop source from Github, using
250 git clone https://github.com/WhisperSystems/Signal-Desktop.git
253 <p
>Next, I patched the source to use the production servers, to be
254 able to talk to other Signal users:
</p
>
257 cat
&lt;
&lt;EOF | patch -p0
258 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
259 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
260 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
265 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
266 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
267 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
268 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
270 window.getSocketStatus = function() {
271 if (messageReceiver) {
272 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
273 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
274 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
277 'use strict
';
278 - var BUILD_EXPIRATION =
0;
279 + var BUILD_EXPIRATION =
1474492690000;
281 window.extension = window.extension || {};
286 <p
>The first part is changing the servers, and the second is updating
287 an expiration timestamp. This timestamp need to be updated regularly.
288 It is set
90 days in the future by the build process (Gruntfile.js).
289 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
291 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
292 script to launch Signal in Chromium.
</p
>
299 --proxy-server=
"socks://localhost:
9050" \
300 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
303 <p
> The script start the app and configure Chromium to use the Tor
304 SOCKS5 proxy to make sure those controlling the Signal servers (today
305 Amazon and Whisper Systems) as well as those listening on the lines
306 will have a harder time location my laptop based on the Signal
307 connections if they use source IP address.
</p
>
309 <p
>When the script starts, one need to follow the instructions under
310 "Standalone Registration
" in the CONTRIBUTING.md file in the git
311 repository. I right clicked on the Signal window to get up the
312 Chromium debugging tool, visited the
'Console
' tab and wrote
313 'extension.install(
"standalone
")
' on the console prompt to get the
314 registration form. Then I entered by land line phone number and
315 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
316 repeated the verification code three times. After entering the number
317 into the verification code field in the form, I could start using
318 Signal from my laptop.
320 <p
>As far as I can tell, The Signal app will leak who is talking to
321 whom and thus who know who to those controlling the central server,
322 but such leakage is hard to avoid with a centrally controlled server
323 setup. It is something to keep in mind when using Signal - the
324 content of your chats are harder to intercept, but the meta data
325 exposing your contact network is available to people you do not know.
326 So better than many options, but not great. And sadly the usage is
327 connected to my land line, thus allowing those controlling the server
328 to associate it to my home and person. I would prefer it if only
329 those I knew could tell who I was on Signal. There are options
330 avoiding such information leakage, but most of my friends are not
331 using them, so I am stuck with Signal for now.
</p
>
336 <title>The new
"best
" multimedia player in Debian?
</title>
337 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
338 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
339 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
340 <description><p
>When I set out a few weeks ago to figure out
341 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
342 multimedia player in Debian claimed to support most file formats /
343 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
344 the various players claimed support for. The range was from
55 to
130
345 MIME types. I suspect most media formats are supported by all
346 players, but this is not really reflected in the MimeTypes values in
347 their desktop files. There are probably also some bogus MIME types
348 listed, but it is hard to identify which one this is.
</p
>
350 <p
>Anyway, in the mean time I got in touch with upstream for some of
351 the players suggesting to add more MIME types to their desktop files,
352 and decided to spend some time myself improving the situation for my
353 favorite media player VLC. The fixes for VLC entered Debian unstable
354 yesterday. The complete list of MIME types can be seen on the
355 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
356 player MIME type support status
</a
> Debian wiki page.
</p
>
358 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
359 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
360 kmplayer. I am sure some of the other players desktop files support
361 several of the formats currently listed as working only with vlc,
362 toten and parole.
</p
>
364 <p
>A sad observation is that only
14 MIME types are listed as
365 supported by all the tested multimedia players in Debian in their
366 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
367 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
368 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
369 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
370 it sad that video/ogg and video/webm is not supported by all the media
371 players in Debian. As far as I can tell, all of them can handle both
377 <title>A program should be able to open its own files on Linux
</title>
378 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
379 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
380 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
381 <description><p
>Many years ago, when koffice was fresh and with few users, I
382 decided to test its presentation tool when making the slides for a
383 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
384 wrote the first draft of the slides, saved the result and went to bed
385 the day before I would give the talk. The next day I took a plane to
386 the location where the meeting should take place, and on the plane I
387 started up koffice again to polish the talk a bit, only to discover
388 that kpresenter refused to load its own data file. I cursed a bit and
389 started making the slides again from memory, to have something to
390 present when I arrived. I tested that the saved files could be
391 loaded, and the day seemed to be rescued. I continued to polish the
392 slides until I suddenly discovered that the saved file could no longer
393 be loaded into kpresenter. In the end I had to rewrite the slides
394 three times, condensing the content until the talk became shorter and
395 shorter. After the talk I was able to pinpoint the problem
&ndash;
396 kpresenter wrote inline images in a way itself could not understand.
397 Eventually that bug was fixed and kpresenter ended up being a great
398 program to make slides. The point I
'm trying to make is that we
399 expect a program to be able to load its own data files, and it is
400 embarrassing to its developers if it can
't.
</p
>
402 <p
>Did you ever experience a program failing to load its own data
403 files from the desktop file browser? It is not a uncommon problem. A
404 while back I discovered that the screencast recorder
405 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
406 browser would refuse to open. No video player claimed to understand
407 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
408 returning the application/ogg MIME type, which no video player I had
409 installed listed as a MIME type they would understand. I asked for
410 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
411 behavour
</a
> and use the MIME type video/ogg instead. I also asked
412 several video players to add video/ogg to their desktop files, to give
413 the file browser an idea what to do about Ogg Theora files. After a
414 while, the desktop file browsers in Debian started to handle the
415 output from gtk-recordmydesktop properly.
</p
>
417 <p
>But history repeats itself. A few days ago I tested the music
418 system Rosegarden again, and I discovered that the KDE and xfce file
419 browsers did not know what to do with the Rosegarden project files
420 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
421 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
422 included in the next upload. To increase the chance of me remembering
423 how to fix the problem next time some program fail to load its files
424 from the file browser, here are some notes on how to fix it.
</p
>
426 <p
>The file browsers in Debian in general operates on MIME types.
427 There are two sources for the MIME type of a given file. The output from
428 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
429 shared MIME type registry (under /usr/share/mime/). The file MIME
430 type is mapped to programs supporting the MIME type, and this
431 information is collected from
432 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
433 desktop files
</a
> available in /usr/share/applications/. If there is
434 one desktop file claiming support for the MIME type of the file, it is
435 activated when asking to open a given file. If there are more, one
436 can normally select which one to use by right-clicking on the file and
437 selecting the wanted one using
'Open with
' or similar. In general
438 this work well. But it depend on each program picking a good MIME
440 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
441 MIME type registered with IANA
</a
>), file and/or the shared MIME
442 registry recognizing the file and the desktop file to list the MIME
443 type in its list of supported MIME types.
</p
>
445 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
446 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
447 Shared MIME database
</a
> look like this:
</p
>
449 <p
><blockquote
><pre
>
450 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
451 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
452 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
453 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
454 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
455 &lt;glob pattern=
"*.rg
"/
&gt;
456 &lt;/mime-type
&gt;
457 &lt;/mime-info
&gt;
458 </pre
></blockquote
></p
>
460 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
461 (it is a gzipped XML file). Note, it is much better to use an
462 official MIME type registered with IANA than it is to make up ones own
463 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
465 <p
>The desktop file of the rosegarden program failed to list
466 audio/x-rosegarden in its list of supported MIME types, causing the
467 file browsers to have no idea what to do with *.rg files:
</p
>
469 <p
><blockquote
><pre
>
470 % grep Mime /usr/share/applications/rosegarden.desktop
471 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
472 X-KDE-NativeMimeType=audio/x-rosegarden-composition
474 </pre
></blockquote
></p
>
476 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
477 MimeType= line.
</p
>
479 <p
>If you run into a file which fail to open the correct program when
480 selected from the file browser, please check out the output from
481 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
482 MIME type is registered somewhere under /usr/share/mime/ and check
483 that some desktop file under /usr/share/applications/ is claiming
484 support for this MIME type. If not, please report a bug to have it
490 <title>Tor - from its creators mouth
11 years ago
</title>
491 <link>http://people.skolelinux.org/pere/blog/Tor___from_its_creators_mouth_11_years_ago.html
</link>
492 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Tor___from_its_creators_mouth_11_years_ago.html
</guid>
493 <pubDate>Sat,
28 May
2016 14:
20:
00 +
0200</pubDate>
494 <description><p
>A little more than
11 years ago, one of the creators of Tor, and
495 the current President of
<a href=
"https://www.torproject.org/
">the Tor
496 project
</a
>, Roger Dingledine, gave a talk for the members of the
497 <a href=
"http://www.nuug.no/
">Norwegian Unix User group
</a
> (NUUG). A
498 video of the talk was recorded, and today, thanks to the great help
499 from David Noble, I finally was able to publish the video of the talk
500 on Frikanalen, the Norwegian open channel TV station where NUUG
501 currently publishes its talks. You can
502 <a href=
"http://frikanalen.no/se
">watch the live stream using a web
503 browser
</a
> with WebM support, or check out the recording on the video
504 on demand page for the talk
505 "<a href=
"http://beta.frikanalen.no/video/
625599">Tor: Anonymous
506 communication for the US Department of Defence...and you.
</a
>".
</p
>
508 <p
>Here is the video included for those of you using browsers with
509 HTML video and Ogg Theora support:
</p
>
511 <p
><video width=
"70%
" poster=
"http://simula.gunkies.org/media/
625599/large_thumb/
20050421-tor-frikanalen.jpg
" controls
>
512 <source src=
"http://simula.gunkies.org/media/
625599/theora/
20050421-tor-frikanalen.ogv
" type=
"video/ogg
"/
>
513 </video
></p
>
515 <p
>I guess the gist of the talk can be summarised quite simply: If you
516 want to help the military in USA (and everyone else), use Tor. :)
</p
>
521 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
522 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
523 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
524 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
525 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
526 system
</a
> is a user-focused solution in Debian for handling hardware
527 related packages. The idea is to have a database of mappings between
528 hardware and packages, and pop up a dialog suggesting for the user to
529 install the packages to use a given hardware dongle. Some use cases
530 are when you insert a Yubikey, it proposes to install the software
531 needed to control it; when you insert a braille reader list it
532 proposes to install the packages needed to send text to the reader;
533 and when you insert a ColorHug screen calibrator it suggests to
534 install the driver for it. The system work well, and even have a few
535 command line tools to install firmware packages and packages for the
536 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
538 <p
>The system was initially written using aptdaemon, because I found
539 good documentation and example code on how to use it. But aptdaemon
540 is going away and is generally being replaced by
541 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
542 so Isenkram needed a rewrite. And today, thanks to the great patch
543 from my college Sunil Mohan Adapa in the FreedomBox project, the
544 rewrite finally took place. I
've just uploaded a new version of
545 Isenkram into Debian Unstable with the patch included, and the default
546 for the background daemon is now to use PackageKit. To check it out,
547 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
548 and see if it is recognised.
</p
>
550 <p
>If you want to know what kind of packages isenkram would propose for
551 the machine it is running on, you can check out the isenkram-lookup
552 program. This is what it look like on a Thinkpad X230:
</p
>
554 <p
><blockquote
><pre
>
570 </pre
></blockquote
></p
>
572 <p
>The hardware mappings come from several places. The preferred way
573 is for packages to announce their hardware support using
574 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
575 cross distribution appstream system
</a
>.
577 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
578 blog posts about isenkram
</a
> to learn how to do that.
</p
>
583 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
584 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
585 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
586 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
587 <description><p
>Yesterday I updated the
588 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
589 package in Debian
</a
> with a few patches sent to me by skilled and
590 enterprising users. There were some nice user and visible changes.
591 First of all, both desktop menu entries now work. A design flaw in
592 one of the script made the history graph fail to show up (its PNG was
593 dumped in ~/.xsession-errors) if no controlling TTY was available.
594 The script worked when called from the command line, but not when
595 called from the desktop menu. I changed this to look for a DISPLAY
596 variable or a TTY before deciding where to draw the graph, and now the
597 graph window pop up as expected.
</p
>
599 <p
>The next new feature is a discharge rate estimator in one of the
600 graphs (the one showing the last few hours). New is also the user of
601 colours showing charging in blue and discharge in red. The percentages
602 of this graph is relative to last full charge, not battery design
605 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
607 <p
>The other graph show the entire history of the collected battery
608 statistics, comparing it to the design capacity of the battery to
609 visualise how the battery life time get shorter over time. The red
610 line in this graph is what the previous graph considers
100 percent:
612 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
614 <p
>In this graph you can see that I only charge the battery to
80
615 percent of last full capacity, and how the capacity of the battery is
616 shrinking. :(
</p
>
618 <p
>The last new feature is in the collector, which now will handle
619 more hardware models. On some hardware, Linux power supply
620 information is stored in /sys/class/power_supply/ACAD/, while the
621 collector previously only looked in /sys/class/power_supply/AC/. Now
622 both are checked to figure if there is power connected to the
625 <p
>If you are interested in how your laptop battery is doing, please
627 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
628 in Debian unstable, or rebuild it on Jessie to get it working on
629 Debian stable. :) The upstream source is available from
<a
630 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
631 Patches are very welcome.
</p
>
633 <p
>As usual, if you use Bitcoin and want to show your support of my
634 activities, please send Bitcoin donations to my address
635 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>