- First, there is a clear difference between the raw glibc functions (all in the glibc module) and anything else. You can use them directly just as you would have from C. There's no magic going on and it's all there.
- Second, we now have a growing collection of python wrappers (in the new pyglibc package), that give low-level primitives nice, high-level, pythonic API. Some of those are straight out of Python 3.4 (but are not a code copy), those include selectors.EpollSelector and select.epoll, some are custom (there's nothing to based this on) like signalfd and pthread_sigmask. More are on the way.
- Third, and this is pretty interesting. I've decided to build a PEP3156 compatible event loop API. This is paramount for how this code can be consumed. It should roughly work out of the box as a drop-in replacement for the Python 3.4 only asyncio module. Did I mention that it works on Python 2.7? A lot is still missing but I am making progress. This ultimately means that once my contraption makes it into plainbox it won't have to be supported forever (aka job security) and can be discarded once we can depend on Python 3.4. It also means there's a clear, well defined API, a reference implementation (and some others if you look hard enough.
My ultimate goal is to scratch my itch. I want to build a reliable test launcher that does monitoring and cleanup. My only constraint is support for Python 3.2 on Ubuntu 12.04 that I have to support. I'm doing a little bit more by supporting Python 2.7 (since it's not costing me anything) on anything that is running the recent enough glibc.
If you're interested in discussing this, using it, adding patches or the like, ping me please.
Ubuntu is 10 today! That's reason to celebrate.
I encourage everyone who's ever enjoyed or contributed to Ubuntu to find the most fun, outrageous, and outlandish birthday photo you can and show it to three people you know who have never heard of (or tried) Ubuntu. Then post it to Planet Ubuntu (or to your favourite place if you can't post here). (If you're not a Planet Ubuntu author, please link to your post in the comments so others can find it here.)
Here's my favourite birthday photo:
Put Orange Candles on Your Head and Celebrate Ubuntu!
10 years may seem like an eternity in the tech world, but I like to remind people that we're only part way along the journey to create technology that respects humans, doesn't treat them as "users", and gives them a voice in the decision-making process. Look around you. Is your technology serving you, or are you part of a predatory business model? Are your friends and family enjoying Ubuntu yet?
I once heard that the path to widespread Ubuntu adoption would be a 20-year journey. I can't remember who to attribute this to, but if you're reading, please chime in, and please accept my thanks for setting realistic expectations. This is a struggle that won't be over soon, but we're well on our way.
I am honoured to be part of the Ubuntu family, and I'm looking forward to the next 10 years. When we have our 20th, the world will be a *much* better place, thanks in part to the wonderful people who make Ubuntu.
And, finally, no Happy Birthday message for Ubuntu would be complete without thanking Mark "sabdl" Shuttleworth. Thank you Mark for being the change you want to see in the world and for inspiring so many (myself included) to work on something meaningful.
image by Bart
The Ubuntu GNOME Team is proud and happy to announce the release of Ubuntu GNOME 14.10 (Utopic Unicorn).
Ubuntu GNOME is an official flavour of Ubuntu, featuring the GNOME desktop environment. Ubuntu GNOME is a mostly pure GNOME desktop experience built from the Ubuntu repositories. Two years ago, Ubuntu GNOME has started as unofficial flavour to Ubuntu – see the release notes of 12.10 – and 6 months after that, Ubuntu GNOME has become an official flavour. So, 13.04, 13.10, 14.04 LTS and today, this is our 5th version and the 4th official one. Let’s find out more about Ubuntu GNOME 14.10Release Notes
Please read the Release Notes before Downloading Ubuntu GNOME 14.10:
There are important steps you need to be aware of before installing Ubuntu GNOME 14.10 so please read carefully: Download Ubuntu GNOME 14.10Support
Ubuntu GNOME 14.10 (Utopic Unicorn) is supported for 9 months only. This is our Non-LTS Release. If you seek stability and long support, please consider Ubuntu GNOME 14.04 (Trusty Tahr) LTS Release. If you seek the latest software/packages that we can offer, then go ahead and use Ubuntu GNOME 14.10 (Utopic Unicorn).Contact Us
Please, see the full list of our communications channelsThank you everyone
To each and everyone who participated, helped, supported and contributed to Ubuntu GNOME this cycle; big thanks to all of you. Special thanks to our testers who did a unique great job to make Ubuntu GNOME better.
Thank you for choosing and using Ubuntu GNOME.
Non-Technical Leader of Ubuntu GNOME
The Xubuntu team is pleased to announce the immediate release of Xubuntu 14.10!
The release is available for download by torrents and direct downloads from http://xubuntu.org/getxubuntu/
As the main server will be very busy in the first days after the release, we recommend using the Torrents wherever possible.
For support with the release, navigate to Help & Support for a complete list of methods to get help.Highlights and Known Issues
To celebrate the 14.10 codename “Utopic Unicorn” and to demonstrate the easy customisability of Xubuntu, highlight colors have been turned pink for this release. You can easily revert this change by using the theme configuration application (gtk-theme-config) under the Settings Manager; simply turn Custom Highlight Colors “Off” and click “Apply”. Of course, if you wish, you can change the highlight color to something you like better than the default blue!
Starting with Xubuntu 14.10, you should use pkexec instead of gksudo for running graphical applications with root access from the terminal for improved security. The Xubuntu team has prepared and shipped the necessary pkexec policy files for all default applications in the Xubuntu installation that we deemed necessary.
Please note that changes in the default configuration affect all users who haven’t changed the default configuration. Read more about the default configuration changes in the release notes.Highlights
- New Xfce Power Manager plugin is added to the panel
Note: Upgraders from Trusty will not see the new xfce4-power-manager panel plugin by default, but instead stick to indicator-power. This can easily be resolved by uninstalling indicator-power and adding the “Power Manager Plugin” to the panel.
- Items in the newly themed alt-tab dialog can now be clicked with the mouse
- com32r error on boot with usb (1325801)
- Virtualbox can start with a black screen (1378423)
- Black background to Try/Install dialogue (1365815)
- Move to TTY1 (with VirtualBox, RightCtrl+F1), then back to TTY7 (with VirtualBox, RightCtrl+F7) and proceed
For a more complete changelog between Xubuntu 14.04 and 14.10, please refer to the release notes.
To kick off the day, I led a session on something that has been wreaking havoc for application test writers within the core apps -- environment setup. In theory, setting up the environment to run your test should be easy. In practice, I've found it increasingly difficult. The music, calendar, clock, reminders, file manager and other teams have all been quite affected by this and the canonical QA team and myself have all pitched in to help, but struggled as well. In short, a test should be easy to launch, be well behaved and not delete any user data, and be easy to setup and feed test data into for the test process. I'm happy to report that the idea of a permanent solution has been reached. Now we must implement it of course, but the result should be drastically easier and more reliable test setup for you the test author.
I also had the chance to list some grievances for application developers with the QA team. We spoke about wanting to expand the documentation on testing and specifically targeted the need to create better templates in the ubuntu sdk for new projects. When you start a new project you should have well functioning tests, and we should teach you about how to run them too!
Just before lunch the community core app developers were able to discuss post-RTM plans and features. A review of the apps was undertaken and some desire for new designs or features were discussed. Terminal is being rebuilt to be more aligned with upstream. Music is currently undergoing a re-design which is coming along great. Calculator is anxious to get some design love. Reminders potential for offline notetaking as well as potential name changes were all discussed. Overall, an amazing accomplishment by all the developers!
After lunch, I spent time confirming the fix for a longstanding bug within autopilot. The merge proposal for fixing this bug has been simmering all summer and it's time to get it fixed. The current test suites for calendar and clock have been impacted by this and have already had regressions occur that could have been caught had tests been able to be written for this area. Having myself, the autopilot team, and the calendar developers in one place made fixing this possible.
To end the day, I spent some time attending sessions for changes to CI and learning more about the coming changes to CI within ubuntu. In summary the news is wonderful. CI will test using autopkgtest, and all of ubuntu will come under this umbrella -- phone, desktop, everything. If it's a package and it has tests, we will do all of the autopkgtest goodness currently being done for the distro.
The evening closed with a bit of fun provided by a game making hackathon using bacon2d and the hilariously horrible "Turkish Star Wars". We could always use more games in the ubuntu app store, and I hear there might even still be a pioneers t-shirt or two left if you get it in early!
This brief announcement was released yesterday to the debian-devel-announce mailing list.
The Debian Multimedia Maintainers have been quite active since the Wheezy release, and have some interesting news to share for the Jessie release. Here we give you a brief update on what work has been done and work that is still ongoing.
Let’s see what’s cooking for Jessie then.
Frameworks and libraries Support for many new media formats and codecs.
The codec library libavcodec, which is used by popular media playback applications including vlc, mpv, totem (using gstreamer1.0-libav), xine, and many more, has been updated to the latest upstream release version 11 provided by Libav. This provides Debian users with HEVC playback, a native Opus decoder, Matroska 3D support, Apple ProRes, and much more. Please see libav’s changelog for a full list of functionality additions and updates.libebur128
libebur128 is a free implementation of the European Broadcasting Union Loudness Recommendation (EBU R128), which is essentially an alternative to ReplayGain. The library can be used to analyze audio perceived loudness and subsequentially normalize the volume during playback.libltc
libltc provides functionalities to encode and decode Linear (or Longitudinal) Timecode (LTC) from/to SMPTE data timecode.libva
libva and the driver for Intel GPUs has been updated to the 1.4.0 release. Support for new GPUs has been added. libva now also supports Wayland.Pure Data
A number of new additional libraries (externals) will appear in Jessie, including (among others) Eric Lyon’s fftease and lyonpotpourrie, Thomas Musil’s iemlib, the pdstring library for string manipulation and pd-lua that allows to write Pd-objects in the popular lua scripting language.
JACK and LADI
LASH Audio Session Handler was abandoned upstream a long time ago in favor of the new session management system, called ladish (LADI Session Handler). ladish allows users to run many JACK applications at once and save/restore their configuration with few mouse clicks.
The current status of the integration between the session handler and JACK may be summarized as follows:
- ladish provides the backend;
- laditools contains a number of useful graphical tools to tune the session management system’s whole configuration (including JACK);
- gladish provides a easy-to-use graphical interface for the session handler.
Note that ladish uses the D-Bus interface to the jack daemon, therefore only Jessie’s jackd2 provides support for and also cooperates fine with it.
Plugins: LV2 and LADSPA
Debian Jessie will bring the newest 1.10.0 version of the LV2 technology. Most changes affect the packaging of new plugins and extensions, a brief list of packaging guidelines is now available.
A number of new plugins and development tools too have been made available during the Jessie development cycle:
LVTK provides libraries that wrap the LV2 C API and extensions into easy to use C++ classes. The original work for this was mostly done by Lars Luthman in lv2-c++-tools.Vee One Suite
The whole suite by Rui Nuno Capela is now available in Jessie, and consists of three components:
- drumkv1: old-school drum-kit sampler synthesizer
- samplv1: polyphonic sampler
- synthv1: analog-style 4-oscillator substractive synthesizer
All three are provided in both forms of LV2 plugins and stand-alone JACK client. JACK session, JACK MIDI, and ALSA MIDI are supported too.x42-plugins and zam-plugins
LV2 bundles containing many audio plugins for high quality processing.Fomp
Fomp is an LV2 port of the MCP, VCO, FIL, and WAH plugins by Fons Adriaensen.
Some other components have been upgraded to more recent upstream versions:
- ab2gate: 1.1.7
- calf: 0.0.19+git20140915+5de5da28
- eq10q: 2.0~beta5.1
- NASPRO: 0.5.1
We’ve packaged ste-plugins, Fons Adriaensen’s new stereo LADSPA plugins bundle.
A major upgrade of frei0r, namely the standard collection for the minimalistic plugin API for video effects, will be available in Jessie.
New multimedia applications Advene
Advene (Annotate Digital Video, Exchange on the NEt) is a flexible video
The new generation of the popular digital audio workstation will make its very first appearance in Debian Jessie.Cantata
Qt4 front-end for the MPD daemon.Csound
Csound for jessie will feature the new major series 6, with the improved IDE CsoundQT. This new csound supports improved array data type handling, multi-core rendering and debugging features.din
DIN Is Noise is a musical instrument and audio synthesizer that supports JACK audio output, MIDI, OSC, and IRC bot as input sources. It could be extended and customized with Tcl scripts too.dvd-slideshow
dvd-slideshow consists of a suite of command line tools which come in handy to make slideshows from collections of pictures. Documentation is provided and available in `/usr/share/doc/dvd-slideshow/’.dvdwizard
DVDwizard can fully automate the creation of DVD-Video filesystem. It supports graphical menus, chapters, multiple titlesets and multi-language streams. It supports both PAL and NTSC video modes too.flowblade
Flowblade is a video editor – like the popular KDenlive based on the MLT engine, but more lightweight and with some difference in editing concepts.forked-daapd
Forked-daapd switched to a new, active upstream again dropping Grand Central Dispatch in favor of libevent. The switch fixed several bugs and made forked-daapd available on all release architectures instead of shipping only on amd64 and i386. Now nothing prevents you from setting up a music streaming (DAAP/DACP) server on your favorite home server no matter if it is based on mips, arm or x86!harvid
HTTP Ardour Video Daemon decodes still images from movie files and serves them via HTTP. It provides frame-accurate decoding and is main use-case is to act as backend and second level cache for rendering the
videotimeline in Ardour.
Groove Basin is a music player server with a web-based user interface inspired by Amarok 1.4. It runs on a server optionally connected to speakers. Guests can control the music player by connecting with a laptop, tablet, or smart phone. Further, users can stream their music libraries remotely.
It comes with a fast, responsive web interface that supports keyboard shortcuts and drag drop. It also provides the ability to upload songs, download songs, and import songs by URL, including YouTube URLs. Groove Basin supports Dynamic Mode which automatically queues random songs, favoring songs that have not been queued recently.
It automatically performs ReplayGain scanning on every song using the EBU R128 loudness standard, and automatically switches between track and album mode. Groove Basin supports the MPD protocol, which means it is compatible with MPD clients. There is also a more powerful Groove Basin protocol which you can use if the MPD protocol does not meet your needs.
HandBrake, a versatile video transcoder, is now available for Jessie. It could convert video from nearly any format to a wide range of commonly supported codecs.jack-midi-clock
New jackd midiclock utility made by Robin Gareus.laborejo
Laborejo, Esperanto for “Workshop”, is used to craft music through notation. It is a LilyPond GUI frontend, a MIDI creator and a tool collection to inspire and help music composers.mpv
mpv is a movie player based on MPlayer and mplayer2. It supports a wide variety of video file formats, audio and video codecs, and subtitle types. The project focuses mainly on modern systems and encourages developer activity. As such, large portions of outdated code originating from MPlayer have been removed, and many new features and improvements have been added. Note that, although there are still some similarities to its predecessors, mpv should be considered a completely different program (e.g. lacking compatibility with both mplayer and mplayer2 in terms of command-line arguments and configuration).smtube
SMTube is a stand-alone graphical video browser and player, which makes YouTube’s videos browsing, playing, and download such a piece of cake.
It has so many features that, we are sure, will make YouTube lovers very, very happy.
Sonic Visualiser Application for viewing and analysing the contents of music audio files.SoundScapeRenderer
SoundScapeRenderer (aka SSR) is a (rather) easy to use render engine for spatial audio, that provides a number of different rendering algorithms, ranging from binaural (headphone) playback via wave field synthesis to higher-order ambisonics.Videotrans
videotrans is a set of scripts that allow its user to reformat existing movies into the VOB format that is used on DVDs.XBMC
XBMC has been partially rebranded as XBMC from Debian to make it clear that it is changed to conform to Debian’s Policy. The latest stable release, 13.2 Gotham will be part of Jessie making Debian a good choice for HTPC-s.zita-bls1
Binaural stereo signals converter made by Fons Adriaensenzita-mu1
Stereo monitoring organiser for jackd made by Fons Adriaensenzita-njbridge
Jack clients to transmit multichannel audio over a local IP network made by Fons Adriaensenradium-compressor
Radium Compressor is the system compressor of the Radium suite. It is provided in the form of stand-alone JACK application.
With Jessie we are shipping a set of multimedia related tasks.
They include package lists for doing several multimedia related tasks. If you are interested in defining new tasks, or tweaking the current, existing ones, we are very much interested in hearing from you.
Upgraded applications and libraries
- Aeolus: 0.9.0
- Aliki: 0.3.0
- Ams: 2.1.1
- amsynth: 1.4.2
- Audacious: 3.5.2
- Audacity: 2.0.5
- Audio File Library: 0.3.6
- Blender: 2.72b
- Bristol: 0.60.11f
- C* Audio Plugin Suite: 0.9.23
- Cecilia: 5.0.9
- cmus: 2.5.0
- DeVeDe: 3.23.0-13-gbfd73f3
- DRC: 3.2.1
- EasyTag: 2.2.2
- ebumeter: 0.2.0
- faustworks: 0.5
- ffDiaporama: 1.5
- ffms: 2.20
- gmusicbrowser: 1.1.13
- Hydrogen: 0.9.6.1
- IDJC: 0.8.14
- jack-tools: 20131226
- LiVES: 2.2.6
- mhWaveEdit: 1.4.23
- Mixxx: 1.11.0
- mp3fs: 0.91
- MusE: 2.1.2
- Petri-Foo: 0.1.87
- PHASEX: 0.14.97
- QjackCtl: 0.3.12
- Qtractor: 0.6.3
- rtaudio: 4.1.1
- Rosegarden: 14.02
- rtmidi: 2.1.0
- SoundTouch: 1.8.0
- stk: 4.4.4
- streamtuner2: 2.1.3
- SuperCollider: 3.6.6
- Synfig Studio: 0.64.1
- TerminatorX: 3.90
- tsdecrypt: 10.0
- Vamp Plugins SDK: 2.5
- VLC: Jessie will release with the 2.2.x series of VLC
- XCFA: 4.3.8
- xwax: 1.5
- xjadeo: 0.8.0
- x264: 0.142.2431+gita5831aa
- zynaddsubfx: 2.4.3
What’s not going to be in Jessie
With the aim to improve the overall quality of the multimedia software available in Debian, we have dropped a number of packages which were abandoned upstream:
- lv2fil (suggested replacement for users is eq10q or calf eq)
- specimen (suggested replacement for users is petri-foo – fork of specimen)
- zynjacku (suggested replacement for users is jalv)
We’ve also dropped mplayer, presently nobody seems interested in maintaining it.
The suggested replacements for users are mplayer2 or mpv. Whilst the former is mostly compatible with mplayer in terms of command-line arguments and configuration (and adds a few new features too), the latter adds a lot of new features and improvements, and it is actively maintained upstream.
Please note that although the mencoder package is no longer available anymore, avconv and mpv do provide encoding functionality. For more information see avconv’s manual page and documentation, and mpv’s encoding documentation.
rtkit under systemd is broken at the moment.
More information about team’s activity are available.
Where to reach us
The Debian Multimedia Maintainers can be reached at pkg-multimedia-maintainers AT lists.alioth.debian.org for packaging related topics, or at debian-multimedia AT lists.debian.org for user and more general discussion.
We would like to invite everyone interested in multimedia to join us there. Some of the team members are also in the #debian-multimedia channel on OFTC.
on behalf of the Debian Multimedia Maintainers
On Tuesday I was finally able to sit down with the team and plan our week. In addition I was able to plan some of the work I had in mind with the community folks working on the core apps. Being obsessed with testing, my primary goals this week are centered around quality. Namely I want to make it easier for developers to write tests. Asking them to write tests is much easier when it's easy to do so. Fortunately, I think (hope?) all of the community core apps developers recognize the benefits to tests and thus are motivated to drive maturity into the testing story.
I'm also keen to work on the manual testing story. The community is imperative in helping test images for not only ubuntu, but also all of it's flavors. Seriously, you should say thank you to those folks helping make sure your install of ubuntu works well. They are busy this week helping make sure utopic is as good as it can be. Rock on image testers! But the tools and process used weigh on my mind, and I'm keen to chat later in the week with the canonical QA team and get there feedback.
During the day I attended sessions regarding changes and tweaks to the CI process. For core apps developers, errors in jenkins should be easier to replicate after these changes. CI will be moving to utilizing adt-run (autopkgtest) for there test execution (and you should too!). They will also provide the exact commands used to run the test. That means you can easily duplicate the results on the dashboard locally and fix the issues found. No more works on my box excuses!
I also met the team responsible for the application store and gave them feedback on the application submission process. Submitting apps is already so simple, but even more cool things are happening on this front.
The end of the evening found us shuffling into cab's for a team dinner. We had a long table of folks eating Italian food and getting to know each other better.
After dinner, I pressured a few folks into having some dessert and ordered a sorbet for myself. After receiving no less than 4 fruit sorbets due to a misunderstanding, I began carving the fruits and sending plates of sorbet down the table. My testcase failed however when the plates all came back :-(
I thought it might be useful to give writeups each day of what's going on, at least from my perspective during the sprint. I won't yammer on too much about quality and instead bring you pictures of what you really want. And some of this too. Whoops, here's one.
Pictures of people taking pictures . . .Monday was the first day of the sprint, and also the day of my arrival! Personally I'm busy at home during this week, so it's tough to get away. That said, I can't imagine being anywhere else for the week. The sprints are a wonderful source of respite for everyone.
Monday itself consisted of making sure everything is ready for the week, planning events, and icebreakers. In typical fashion, an opening plenary set the bar for the week with notes about the progress being made on the phone as well as the future of the desktop. Lots of meetings and a few blurry jet lagged hours later, everyone was ready to sit for a bit and have some non-technical conversation!
Fortunately for us there was an event planned to meet both our social and hunger needs. After being split randomly into teams of bugs (love the play on quality), we played a bit of trivia. After each round teams were scored not only on the correct response, but also how quickly they responded. The questions varied from the obscure to fun bits about ubuntu. The final round centered around Canonical itself which was fun trip down memory lane to remember.
As I crawled into bed I still had the wonderfully cheesy announcer playing trivia questions in my head.
Kubuntu 14.10 is available for upgrade or install. It comes in two flavours, the stable Plasma 4 running the desktop we know from previous releases, and a tech preview of the next generation Plasma 5 for early adopters.
Doing this is surprisingly difficult and I was certainly caught in a few mistakes the first time I tried to do this. I recently posted a lengthy comment on the corresponding bug. It took me a few moments to carefully analyze and re-think the situation and how a reliable approach should work. Non the less I am only human and I certainly have made my set of mistakes.
Below is the reproduction for my current approach. The implementation is still in progress but it seems to work (I need to implement the termination phase of non-kill-able processes and switch to fully non-blocking I/O). So far I've used epoll(7) and signalfd(7). I'm still planning to use timerfd_create(2) for the timer, perhaps with CLOCK_RTC for hard wall-clock-time limit enforcement. I'll post the full, complete examples once I'm done with this but you can look at how it mostly looks like today in the python-glibc git tree's demos/ directory.
I'd like to ask everyone that has experience with this part of systems engineering to poke holes in my reasoning and show how this might fail and misbehave. Thanks.
The current approach, that so far works good on all the pathological cases is to do this.The general idea is that we're in a I/O loop, using non-blocking I/O and a select-like mechanism to wait for wait for:
- timeout (optional, new feature)
- read side of the stdout pipe data
- read side of the stdout pipe being closed
- read side of the stderr pipe data
- read side of the stderr pipe being closed
- SIGCHLD being delivered with the intent to say that the process is deadIn general we keep looping and terminate only when the set of waited things (stdout depleted, stderr depleted, process terminated) is empty. This is not always true so see below. The action that we do on each is event is obviously different:If the timeout has elapsed we proceed to send SIGTERM, reset the timer for shutdown period, followed by SIGQUIT and another timer reset. After that we send SIGKILL. This can fail as the process may have elevated itself beyond our capabilities. This is still undecided but perhaps, at this time, we should use an elevated process manager (see below). If we fail to terminate the process special provisions apply (see below).If we have data to read we just do and process that (send to log files, process, send to .record.gz). This is a point where we can optimize the process and improve reliability in event of sudden system crash. Using more modern facilities we can implement tee in kernel space which lowers processing burden on python and, in general, makes it more likely that the log files will see actual output the process made just prior to its death.We can also use pipes in O_DIRECT (aka packet mode) here to ensure that all writes() end up as individual records, which is the indented design of the I/O log record concept. This won't address the inherent buffering that is enabled in all programs that detect when they are redirected and no longer attached to a tty.Whenever one of the pipes is depleted (which may *never* happen, lesson learned) we just close our side.When the child dies, and this is the most important part and the actual bugfix, we do the following sequence of events:
- if we still have stdout pipe open, read at most one PIPE_BUF. We cannot read more as the pipe may live on forever and we can just hang as we currently do. Reading one PIPE_BUF ensures that we catch the last moments of what the originally started process intended to tell us. Then we close the pipe. This will likely result in SIGPIPE in any processes that are still attached to it though we have no guarantee that it will rally kill them as that signal can be blocked.
- if we still have stderr pipe open we follow the same logic as for stdout above.
- we restore some signal handling that was blocked during the execution of the loop and terminate.There's one more trick up our sleeve and that is PR_SET_CHILD_SUBREAPER but I'll describe that in a separate bug report that deals with runaway processes. Think dbus-launch or anything that double-forks and demonizes
If you have any comments or ideas please post them here (wherever you are reading this), on the launchpad bug report page or via email. Thanks a lot!
#ubuntu-meeting: Regular LoCo Council Meeting for October 2014, 21 Oct at 20:00 — 21:33 UTC
Full logs at http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-10-21-20.00.log.html
The discussion about “Opening Business” started at 20:00.
Listing of Sitting Members of LoCo Council (20:00)
For the avoidance of uncertainty and doubt, it is necessary to list the members of the council who are presently serving active terms.
Marcos Costales, term expiring 2015-04-16
Jose Antonio Rey, term expiring 2015-10-04
Pablo Rubianes, term expiring 2015-04-16
Sergio Meneses, term expiring 2015-10-04
Stephen Michael Kellat, term expiring 2015-10-04
There is currently one vacant seat on LoCo Council
Roll Call (20:00)
Vote: LoCo Council Roll Call (All Members Present To Vote In Favor To Register Attendance) (Carried)
The discussion about “Re-Verification: France” started at 20:03.
Vote: That the re-verification application of France be approved and that the period of verification be extended for a period of two years from this date. (Carried)
Update on open cases before the LoCo Council
The discussion about “Update on open cases before the LoCo Council” started at 20:19.
LoCo Council presently has before it pending verification and re-verification proceedings for the following LoCo Teams: Mauritius, Finland, Netherlands, Peru, Russia, Serbia.
The loco-contacts thread “Our teams reject the new LoCo Council policy”
The discussion about “The loco-contacts thread ‘Our teams reject the new LoCo Council policy’” started at 20:20.
Requests from the Galician and Asturian teams
The discussion about “Requests from the Galician and Asturian teams” started at 20:59.
Vote: That the Galician Team, pursuant to their request this day, be considered an independent LoCo team notwithstanding representing less than a country. (Carried)
Vote: That the Asturian Team, pursuant to their request this day, be considered an independent LoCo Team notwithstanding representing less than a country. (Carried)
Marcos Costales, in his capacity as leader of Ubuntu Spain and as a member of LoCo Council, stood aside from both votes.
Any Other Business
The discussion about “Any Other Business” started at 21:13.
Those who have requests of the LoCo Council are advised to write to it at email@example.com for assistance.
LoCo Council Roll Call (All Members Present To Vote In Favor To Register Attendance)
Motion carried (For/Against/Abstained 4/0/0)
Voters PabloRubianes, skellat, costales, SergioMeneses
That the re-verification application of France be approved and that the period of verification be extended for a period of two years from this date.
Motion carried (For/Against/Abstained 4/0/0)
Voters PabloRubianes, skellat, costales, SergioMeneses
That the Galician Team, pursuant to their request this day, be considered an independent LoCo team notwithstanding representing less than a country.
Motion carried (For/Against/Abstained 2/0/1)
Voters PabloRubianes, skellat, SergioMeneses
That the Asturian Team, pursuant to their request this day, be considered an independent LoCo Team notwithstanding representing less than a country.
Motion carried (For/Against/Abstained 2/0/1)
Voters PabloRubianes, skellat, SergioMeneses
This morning I came to work a hour earlier than usual. I started my work PC and waited for it to boot into Debian Jessie. And waited… waited… waited…
This sounds strange, doesn’t it? It generally boots rather quickly. In fact Debian hangs during boot with this message:A start job is running for Create Volatile Files and Directories
Followed by a timer and no limit. You can leave it there, but it does not finish and just hangs there. So, let’s try understand the problem.
The problem here is quite obvious: in the previous session you updated systemd to version 215-5+b1. If you have a look at your system’s /tmp directory (you can’t do it now, but we’ll do it later for sake of knowledge), you find out that it’s bloated. Here’s the bug report.
Thankfully, the solution is pretty straightforward. Reboot your computer with Ctrl+Alt+Del and wait for Grub to load, then press e to edit Debian’s entry. After the line with /boot/vmlinuz... add the following:--add rw init=/bin/bash
And press F10 to boot. Debian will load as a shell with root permissions, so you can do whatever you want (but be careful, because you can cause big issues too!
Now it’s time to check your /tmp directory:ls -l /tmp
You should wait some minutes until it finishes, and the output may scare you. It’s bloated, as I told you before. What can you do now? Just remove and recreate it.rm -rf /tmp mkdir /tmp chmod 1777 /tmp
Now restart your PC and check it out: Debian will boot correctly!
Is systemd ready to go towards a Debian stable release? I don’t think so. The team has to work hard to accomplish this step. So, good luck guys, and please test it a little more next time!
Source: Debian User Forums
Created and supported by community: http://www.kubuntu.org/supportProfessional support for users: http://kubuntu.emerge-open.com/buySupport by Blue Systems to some developers & projects:http://www.blue-systems.com/ http://www.blue-systems.com/projects/Infrastructure support by Ubuntu, KDE, Blue Systems and DebianGovernance: Kubuntu Council https://launchpad.net/~kubuntu-council
How to contact us: kubuntu.org, freenode irc: #kubuntu (-devel), kubuntu-user list, kubuntu-devel list, kubuntuforum - http://kubuntu.org - http://webchat.freenode.net/ - https://lists.ubuntu.com/mailman/listinfo/kubuntu-users - https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel - https://www.kubuntuforums.net - Documentation on KDE userbase: http://userbase.kde.org/Kubuntu - Kubuntu in the news: http://wire.kubuntu.org/
* our "upstream" KDE is also making big changes, starting by splitting kdelibs into the Frameworks, and basing them on Qt5 - that work is largely done, although of course each library is being improved as time goes along. Releases monthly. - We're writing a KDE Frameworks book; more about that at books.kde.org - Developers: apidox at api.kde.org
* KDE has now released Plasma 5, based on those new frameworks - that is nearly done, and 5.1 was released 15 Oct.https://www.kde.org/announcements/plasma-5.1/ - lots of excitement around that, because it looks and works really elegant, smooth and modern - Riddell: 14.12 release of KDE Applications will be in December with a mix of Qt 4 and Qt 5 apps, they should both work equally well on your Plasma 4 or 5 desktop and look the same with the classic Oxygen or lovely new Breeze themes
* so our upstream is up to lots of new wonderful stuff, including using CI too (CI: continuous integration with automated testing)
* meanwhile, bugfixes continue on KDE4:https://www.kde.org/announcements/announce-4.14.2.php
* Our base for 14.10 (codename Utopic Unicorn) is that stable KDE platform.* At the same time, we are releasing weekly ISOs of Plasma 5, to makeit easy for people to test - http://apachelog.wordpress.com/2014/10/17/plasma-5-weekly-iso-revisited/ - Riddell: We're releasing a tech preview of Kubuntu Plasma 5 as part of 14.10 for people to test. I'm using it daily and it's working great but expect testers to be competent enough to check for and report beasties
* we're following along to KDE's CI effort, and doing that with our packages - see #kubuntu-ci IRC channel for the reports as they are generated - Riddell: gory details at http://kci.pangea.pub/ - packages built constantly to check for any updates that need changed
* Our new packaging is now in Debian git, so we can share packaging work - as time goes on, all our packaging files will be there - tooling such as packaging scripts are being updated - Debian and Kubuntu packagers will both save time which they can use to improve quality
* moving from LightDM to SDDM (Simple Desktop Display Manager), KDE/Qt defaultgraphical login program
* moving to systemd replacing upstart along with Debian and Ubuntu at some point in the future
* moving to Wayland when it is ready along with KDE (Kwin); now on xorg windowing system. We do not plan to use Ubuntu's Mir
* Testing until release (please!) on the 23rd: - http://iso.qa.ubuntu.com/qatracker/milestones/325/builds/82050/testcases - http://iso.qa.ubuntu.com/qatracker/milestones/325/builds/82052/testcases
* Testing Plasma 5:http://apachelog.wordpress.com/2014/10/17/plasma-5-weekly-iso-revisited/(fresh install) - https://community.kde.org/Plasma/Packages#Kubuntu (upgrading)
* Another way we stay close to KDE is that since Ubuntu stopped inviting community members to participate in face-to-face meetings, we have a Kubuntu Day with Akademy, KDE's annual meeting. Thanks to the Ubuntu Contributors who paid the travel costs for some of us to attend
Qt Free: http://qt-project.org/wiki/The_Qt_Governance_Model
--Thanks to Jonathan Riddell for his clarifications and corrections
plugged = True
plugin = 2
mouse = False
AnalogDeadzone = 100,100
AnalogPeak = 20000,20000
DPad R = button(13)
DPad L = button(15)
DPad D = button(14)
DPad U = button(15)
Start = button(9)
Z Trig = button(7)
B Button = button(2)
A Button = button(1)
C Button R = axis(3+)
C Button L =
C Button D = axis(4-)
C Button U =
R Trig = button(3)
L Trig = button(0)
Mempak switch = key(109)
Rumblepak switch = key(114)
X Axis = axis(0-,0+)
Y Axis = axis(1-,1+)
I almost have every button/axis working but not the c-pad as an axis. Based on what the joystick test program is giving me, the d-pad is also an axis, but I can’t that axis to work. Can someone help me with that.
OS: Ubuntu 14.04 32-bit
Ronnie Tucker: Systemd Creator Says Linux Community Is Rotten, Points at Linus Torvalds as the Source
The creator of systemd, Lennart Poettering, had some very harsh words to say about the Linux community and about one of its role models, Linus Torvalds.
It might seem that the Linux community in its entirety is all about rainbows and bunnies, but the truth is that it’s made up of regular people and the likes. Most of the other communities are formed in this way and Linux is no exception. The problem is that Linus is pegged as one of the people responsible by Lennart Poettering.
There has been some small friction between the two projects, Linux and systemd, but nothing that would indicate that something was amiss. In fact, when asked what he thought about systemd, just a couple of weeks ago, Linus Torvalds was actually very tactful about it.
Submitted by: Silviu Stahie
I’m considering a proposal to have 16.04 LTS be the last release of Ubuntu with 32 bit images to run on 32 bit only machines (on x86 aka Intel/AMD only – this has no bearing on ARM). You would still be able to run 32 bit applications on 64 bit Ubuntu.
Please answer my survey on how this would affect you or your organization.
If you can’t see the form below click here.
Welcome to the Ubuntu Weekly Newsletter. This is issue #388 for the week October 13 – 19, 2014, and the full version is available here.
In this issue we cover:
- Final Freeze for Ubuntu 14.10 (utopic) in effect
- Ubuntu Stats
- Ubuntu Cloud News
- Randall Ross: Why Smart Phones Aren’t – Reason #2 & Reason #3
- Joe Liau: Documenting the Death of the Dumb Telephone – Part 1: Unnecessary & Part 2: Balderdash
- Michael Hall: Unity 8 Desktop
- Kubuntu: KDE Applications and Development Platform 4.14.2
- Jonathan Riddell: Ubuntu’s Linux Scheduler or Why Baloo Might be Slowing Your System in 14.04
- Randall Ross: Writing About Ubuntu? Own Your Own Content
- Mythbuntu: Actions required by Nov 1st due to Schedules Direct change
- Nicholas Skaggs: Final testing for Utopic
- Ronnie Tucker: Canonical Details Plans for Unity 8 Integration in Ubuntu Desktop
- Jussi Kekkonen: Notes about Dell XPS 13 developer edition and Kubuntu
- Randall Ross: Ubuntu Contributors’ Guide
- BootStack FAQs
- Designing machine view
- How to customize and brand your scope
- In The Blogosphere
- Other Articles of Interest
- Featured Audio and Video
- Monthly Team Reports: September 2014
- Upcoming Meetings and Events
- Updates and Security for 10.04, 12.04 and 14.04
- And much more!
The issue of The Ubuntu Weekly Newsletter is brought to you by:
- Paul White
- Elizabeth K. Joseph
- John Mahoney
- And many others
Except where otherwise noted, content in this issue is licensed under a Creative Commons Attribution 3.0 License BY SA Creative Commons License
10 years ago today, Mark Shuttleworth made the 4th post ever to the ubuntu-announce mailing list when he wrote: Announcing Ubuntu 4.10 “The Warty Warthog Release”
In this announcement, Mark wrote:
Ubuntu is a new Linux distribution that brings together the extraordinary breadth of Debian with a fast and easy install, regular releases (every six months), a tight selection of excellent packages installed by default and a commitment to security updates with 18 months of security and technical support for every release.
So it’s with much excitement, the Ubuntu News team wishes Ubuntu a happy 10th Birthday!
Over the years, we’ve had several cakes celebrating releases, here are a sampling we found on Flickr, first from the 8.04 release party in London:
And an amazing trio from Kitchener-Waterloo, Ontario, Canada for 9.10, 10.10 and 11.04:
And dozens of strictly Ubuntu logo cakes over the years (this one from 2006):
With the release of 14.10 just days away, enjoy your release parties and perhaps take some time to reflect upon how far we’ve come in these 10 years!
Posted by Elizabeth K. Joseph, on behalf of the Ubuntu News Team
Today is Ubuntu’s ten year anniversary. Scott did a wonderful job summarizing many of those early years and his own experience, and while I won’t be as articulate as him, I wanted to share a few thoughts on my experience too.
I heard of this super secret Debian startup from Scott James Remnant. When I worked at OpenAdvantage we would often grab lunch in Birmingham, and he filled me in on what he was working on, but leaving a bunch of the blanks out due to confidentiality.
I was excited about this new mystery distribution. For many years I had been advocating at conferences about a consumer-facing desktop, and felt that Debian and GNOME, complete with the exciting Project Utopia work from Robert Love and David Zeuthen made sense. This was precisely what this new distro would be shipping.
When Warty was released I installed it and immediately became an Ubuntu user. Sure, it was simple, but the level of integration was a great step forward. More importantly though, what really struck me was how community-focused Ubuntu was. There was open governance, a Code Of Conduct, fully transparent mailing lists and IRC channels, and they had the Oceans 11 of rock-star developers involved from Debian, GNOME, and elsewhere.
I knew I wanted to be part of this.
While at GUADEC in Stuttgart I met Mark Shuttleworth and had a short meeting with him. He seemed a pretty cool guy, and I invited him to speak at our very first LugRadio Live in Wolverhampton.
Mark at LugRadio Live.
I am not sure how many multi-millionaires would consider speaking to 250 sweaty geeks in a football stadium sports bar in Wolverhampton, but Mark did it, not once, but twice. In fact, one time he took a helicopter to Wolverhampton and landed at the dog racing stadium. We had to have a debate in the LugRadio team for who had the nicest car to pick him up in. It was not me.
This second LugRadio Live appearance was memorable because two weeks previous I had emailed Mark to see if he had a spot for me at Canonical. OpenAdvantage was a three-year funded project and was wrapping up, and I was looking at other options.
Mark’s response was:
“Well, we are opening up an Ubuntu Community Manager position, but I am not sure it is for you.”
I asked him if he could send over the job description. When I read it I knew I wanted to do it.
Fast forward four interviews, the last of which being in his kitchen (which didn’t feel awkward, at all), and I got the job.
The day I got that job was one of the greatest days of my life. I felt like I had won the lottery; working on a project with mission, meaning, and something that could grow my career and skill-set.
Canonical team in 2007
The day I got the job was not without worry though.
I was going to be working with people like Colin Watson, Scott James Remnant, Martin Pitt, Matt Zimmerman, Robert Collins, and Ben Collins. How on earth was I going to measure up?
A few months later I flew out to my first Ubuntu Developer Summit in Mountain View, California. Knowing little about California in November, I packed nothing but shorts and t-shirts. Idiot.
I will always remember the day I arrived, going to a bar with Scott and some others, meeting the team, and knowing absolutely nothing about what they were saying. It sounded like gibberish, and I felt like I was a fairly technical guy at this point. Obviously not.
What struck me though was how kind, patient, and friendly everyone was. The delta in technical knowledge was narrowed with kindness and mentoring. I met some of my heroes, and they were just normal people wanting to make an awesome Linux distro, and wanting to help others get in on the ride too.
What followed was an incredible seven and a half years. I travelled to Ubuntu Developer Summits, sprints, and conferences in more than 30 countries, helped create a global community enthused by a passion for openness and collaboration, experimented with different methods of getting people to work together, and met some of the smartest and kindest people walking on this planet.
The awesome Ubuntu community
Ubuntu helped to define my career, but more importantly, it helped to define my perspective and outlook on life. My experience in Ubuntu helped me learn how to think, to manage, and to process and execute ideas. It helped me to be a better version of me, and to fill my world with good people doing great things, all of which inspired my own efforts.
This is the reason why Ubuntu has always been much more than just software to me. It is a philosophy, an ethos, and most importantly, a family. While some of us have moved on from Canonical, and some others have moved on from Ubuntu, one thing we will always share is this remarkable experience and a special connection that makes us Ubuntu people.
TL;DR: I apparently typed mkfs.vfat /dev/sda1 at some point. Oops.
So I rarely reboot my machines, and last night, when I rebooted my laptop (for graphics card weirdness) Grub just came up with:Error: unknown filesystem. grub rescue>
WTF, I wonder how I borked my grub config? Let's see what happens when we ls my /boot partition.grub rescue>ls (hd0,msdos1) unknown filesystem
Hrrm, that's no good. An ls on my other partition isn't going to be very useful, it's a LUKS-encrypted LVM PV. Alright, time for a live system. I grab a Kali live USB (not because Kali is necessarily the best option here, it's just what I happen to have handy) and put it in the system and boot from that. file tells me its an x86 boot sector, which is not at all what I'm expecting from an ext4 boot partition. It slowly dawns on me that at some point, intending to format a flash drive or SD card, I must've run mkfs.vfat /dev/sda1 instead of mkfs.vfat /dev/sdb1. That one letter makes all the difference. Of course, it turns out it's not even a valid FAT filesystem... since the device was mounted, the OS had kept writing to it like an ext4 filesystem, so it was basically a mangled mess. fsck wasn't able to restore it, even pointing to backup superblocks: it seems as though, among other things, the root inode was destroyed.
So, at this point, I basically have a completely useless /boot partition. I have approximately two options: reinstall and reconfigure the entire OS, or try to fix it manually. Since it didn't seem I had much to lose and it would probably be faster to fix manually (if I could), I decided to give door #2 a try.
First step: recreate a valid filesystem. mkfs.ext4 -L boot /dev/sda1 takes care of that, but you better believe I checked the device name about a dozen times. Now I need to get all the partitions and filesystems mounted for a chroot and then get into it:% mkdir /target % cryptsetup luksOpen /dev/sda5 sda5_crypt % vgchange -a y % mount /dev/mapper/ubuntu-root /target % mount /dev/sda1 /target/boot % mount -o bind /proc /target/proc % mount -o bind /sys /target/sys % mount -o bind /dev /target/dev % chroot /target /bin/bash
Now I'm in my system and it's time to replace my missing files, but how to figure out what goes there? I know there are at least files for grub, kernels, initrds. I wonder if dpkg-query can be useful here?# dpkg-query -S /boot linux-image-3.13.0-36-generic, linux-image-3.13.0-37-generic, memtest86+, base-files: /boot
Well, there's a handful of packages. Let's reinstall them:# apt-get install --reinstall linux-image-3.13.0-36-generic linux-image-3.13.0-37-generic memtest86+ base-files
That's gotten our kernel and initrd replace, but no grub files. Those can be copied by grub-install /dev/sda. Just to be on the safe side, let's also make sure our grub config and initrd images are up to date.# grub-install /dev/sda # update-grub2 # update-initramfs -k all -u
At this point, I've run out of things to double check, so I decide it's time to find out if this was actually good for anything. Exit the chroot and unmount all the filesystems, then reboot from the hard drive.
It worked! Fortunately for me, /boot is such a predictable skeleton that it's relatively easy to rebuild when destroyed. Here's hoping you never find yourself in this situation, but if you do, maybe this will help you get back to normal without a full reinstall.