LibreOffice Conference Schedule has been published on the conference website, at the following address:
Organizers are still finalizing the schedule of the business session on Friday morning, which will be held in Czech and English.
LibreOffice Conference Schedule has been published on the conference website, at the following address:
Organizers are still finalizing the schedule of the business session on Friday morning, which will be held in Czech and English.
It’s been over a month since our last contributor interview, as we’ve been busy with the release of LibreOffice 5.2, but now we’re back – and this time we’re talking to Franklin Weng, who is active within the marketing and migration teams.
What is your IRC nickname / nationality / location / family status?
Do you work for a LibreOffice-related company or just contribute in your spare time?
Two years ago I contributed in my spare time. Now I own a company providing consultancy, training and solutions with free and open source software (FOSS).
How did you get involved with LibreOffice?
Daily use of the software, and I had contributed some translations for the application and wiki as well. Then get I got more deeply involved when the government of Yi-Lan county and our National Development Council decided to migrate to the Open Document Format and LibreOffice starting in 2015.
What areas of the project do you normally work on?
Promotion, migration and training. I also cooperate with the localization (L10N) community in Taiwan.
What was your initial experience of contributing to LibreOffice like?
Well, I’ve been involved in free and open source software for more than 20 years, so it’s quite normal to me Still, I’m quite happy to see the migration to LibreOffice in Yi-Lan succeed, and some departments in our central government and several county or city governments starting to go with us too.
Which is your preferred text editor? And why?
I edit plain text and write code with Vim (no, I don’t use an IDE). The reason? It should be because I’ve been been in love with Vim for more than 20 years. For office text files, LibreOffice Writer is my first choice of course. Sometimes I use LyX or LaTeX too.
What do you do when you’re not working on LibreOffice? Any other hobbies you have?
I work on other open source projects. Okay, and I also spend quite some time with my family and my boys. And I like baseball too.
Thanks Franklin! Your efforts are very much appreciated. And to other potential contributors reading this: there are many ways to get involved with LibreOffice, from documentation and programming to translations and marketing. Join our community, gain valuable experience, and help to spread FOSS and open standards!
Google Summer of Code 2016 is coming to an end. It was an awesome experience and I got to learn something new every time I switched my linux on. I was assigned a project before the start of GSoC with my mentors, Samuel Mehrbrodt and Yousuf Philips, but I managed to complete two projects in the given time frame.Here is the link to my GSoC Introduction blog. This blog post provides an overview of the projects I’ve contributed to LibreOffice during GSoC and it’s significance in the professional working environment.
Total commits count: 61 patches in master and 31 backport commits to LibreOffice 5.2.
LibreOffice gave me commit access soon after the GSoC coding period started. I also committed few patches of other developers.
I will now continue with an overview of my projects.
The above link provides description of all the functionalities which are there in the new design. The dialog has gone through a major rework solving the defects which were surfacing in the previous template manager for ex: visible empty folders.
Initial Commit: https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-5-2&id=ca040d16d06fead95ad7ed8d10f5995fbade1219 New Template Manager
After the initial commit, I continued with my work and a series of major and minor commits were made to implement the functionalities. The commits can be found in the commit lists provided above. I’ll mention three of the important ones here.
After this project was completed, me and my mentors decided to take another project. It was Samuel’s idea to create an emoji toolbar control and we discussed the development process in detail.
The above blog contains all the information about the emoji control.
Initial Commit: https://cgit.freedesktop.org/libreoffice/core/commit/?id=72e6f08c692c0625db5ce377fb478a99660adb0d GSoC Emoji Control
Adding Noto Emoji font to LO installation: https://cgit.freedesktop.org/libreoffice/core/commit/?id=ecb096841a1d7b4d468ba111df4ebafc13134c8e
and so on..
There was so much to learn during GSoC and I would like to thank the LibreOffice community for continuously helping and supporting me to complete the projects.
Thank you Google for such an awesome summer program. 👌
During the FrOSCon I worked on an update for the Plone add-on that will drive the New LibreOffice templates website. This update contains some aditional validations. I released it weithin the ‚Cheeseshop‘ today. The new version will be available on the testsite for the new LibreOffice extensions and templates repository within the next run of buildout.
As Google Summer of Code 2016 draws to a close, I’d like to summarize my work for LibreOffice on the project - ‘Review of Sidebar and it’s functionality’. I had an awesome experience working with the LibreOffice community, under the mentorship of two amazing people - Katarina Behrens and Yousuf Philips.
This post aims at linking and listing out all the feature milestones developed during my project and the relevant commits, along with the goals missed and work to be done in the future.
Overall, a summer well spent. I’ll be contributing to LibreOffice even after the completion of GSoC, aiming to fix the rest of the Sidebar issues. Happy Hacking!
I worked in some more validators inside the TDF.extensionuploadcenter during the last days. I published a new release of this Plone add-on today. It will be used inside the test-website for the new LibreOffice extension Website during the next days.
Someone has rightly said, Emojis are the color of life 🎂. It’s use in text based softwares and editors are properly justified. LibreOffice was lacking this cool feature 😐. Me and my mentors, Samuel Mehrbrodt and Yousuf Philips, decided to work on Emoji integration in LibreOffice as part of my GSoC contributions.We planned to create a working control with proper emoji font support by the end of summer of code. This post provides an overview of the work done. The entire description of the idea can be found here Discussion on Emoji Integration.
After some pre-planned development and tricky debugging, I finally managed to get the toolbar control working. The beta version of toolbar control was merged and is ready to use, thanks to the help and guidance I got from my mentor and LO developers. Patch: GSoC Emoji Control: patch which makes all the above changes to LO.
Emojis gets inserted into the pad on clicking the respective emoji.
One should remember that unlike svg or png emoji, these emoji are glyphs of a particular unicode sequence. They hold all the properties of normal texts. Their colour and size can be changed just like any other character glyph.
The enhancement still needs some love to become bug free. The emoji control is hidden in the standard bar by default. It can be activated by right-clicking on the standard bar and going to Visible Buttons > Emoji Control. Another way to do so is by using the Customize dialog. Go to Tools > Customize and navigate as shown in the picture below.
The foundation for this enhancement has been built now. Further improvements have been proposed like:
Berlin, 17 August 2016 – The Free Software Foundation Europe (FSFE, https://fsfe.org) is joining the Advisory Board of The Document Foundation. At the same time, The Document Foundation is becoming an associated organisation of the FSFE (https://fsfe.org/associates/associates.en.html).
The Free Software Foundation Europe’s aim is to help people control technology instead of the other way around. However, this is a goal which no single organisation can achieve on its own. Associated organizations are entities that share the FSFE’s vision and support the foundation and Free Software in general by encouraging people to use and develop Free Software, by helping organisations understand how Free Software contributes to freedom, transparency and self-determination, and by removing barriers to Free Software adoption.
With this mutual expression of support, both organisations strengthen each other in their effort to keep the general public in the technological driver seat. While the FSFE embodies the principles of the community movement working in pro of the adoption of Free Software in companies, public administrations and for private citizens, The Document Foundation turns principles and ethics into actual products, putting a first class, full-featured, but completely free productivity suite in the hands of users.
“We are happy to welcome the Free Software Foundation Europe as a member of our Advisory Board. Together, we will be able to further develop the adoption of Free Software in Europe, amongst public administrations and enterprises”, said Eike Rathke, a Director of The Document Foundation and a long time Free Software advocate and hacker.
“We believe it is important to join forces with all the organisations active in Free Software around Europe,” said Matthias Kirschner, President of the Free Software Foundation Europe, “and work together to reach our common goals. With our associated organisations we want to show that we are a strong and cohesive movement, and we work to achieve common objectives. To do this, we exchange ideas, coordinate efforts, motivate each other, and find opportunities to work together on specific projects. This is the case with The Document Foundation, steward of one of the most successful Free Software projects: LibreOffice”.
Several members of The Document Foundation will join FSFE Summit 2016 in Berlin, from September 2 to September 4, to celebrate FSFE 15th anniversary (https://fsfe.org/community/events/2016/summit/frontpage.en.html).
Askbot unfortunately is having some database troubles. Infra is working on fixing the problem.
ask.libreoffice.org back in service
The new manual supports the large number of organizations and individuals deploying LibreOffice “Still” 5.1 to get superior quality and stability
Berlin, August 16, 2016 – Volunteers active in LibreOffice Documentation Project within The Document Foundation announce the availability of the Getting Started Guide for LibreOffice 5.1. The book updates the traditional introductory text with the new features provided by the “still” version of the software, targeted to enterprise deployments and to individual users looking for superior quality and stability.
Updated by members of the community, the book is an effort to fill the gap in official documentation for LibreOffice. The Document Foundation is working hard to reduce the delay between the release of the software and its companion documentation, for a better user experience and a stronger competitive offering.
“Many communities consider the Getting Started Guide as a source for translation into their native language, to create localized textbooks for teaching LibreOffice in all environments, from academia to the enterprise,” says Olivier Hallot, documentation coordinator at TDF. “A timely release of these books will send a strong message about the commitment of the community for professional collaterals.”
“In addition to the free downloads of the book in PDF and ODT (editable) forms, users can buy printed copies,” says Jean Hollis Weber, volunteer writer, editor, and publisher of the official LibreOffice guides. “I’ve been working with a great group of other documentation volunteers, but we always need more people.”
To download or buy copies (from Friends of OpenDocument Inc., an Australia-based volunteer organization with members around the world, which supports the LibreOffice project), visit https://www.libreoffice.org/get-help/documentation.
Gone are the days when users were limited to embedding local media and clip art bundled with an office suite, as we now live at a time where there is a plethora of online media at a user’s fingertips, so …
LibreOffice kann über Extensions mit weiteren Funktionen versehen werden. Die Extensions werden von freien Entwicklern beigesteuert, können über die LibreOffice-Extensions-Webseite heruntergeladen und in LibreOffice installiert werden. So findet sich dort auch eine Extension, mit der sich eine Writer-Textdatei in das Dateiformat epub exportieren lässt. So lassen sich auch elektronische Bücher (eBooks) aus LibreOffice heraus erstellen:
Infra is working on restoring the missing objects from replica
Seems a git gc was too aggressive...
bundle the latest xmlsec version, instead the one from 2009
upstream enough of the patches, so building & running against xmlsec as provided by a Linux distro also works
I’m happy to say that the first goal is now reached:
libreoffice-5-1 bundled xmlsec 1.2.14 from 2009
libreoffice-5-2 bundles xmlsec 1.2.20 from 2014
master bundles the latest xmlsec 1.2.22, released earlier this year :-)
This is good, as this way it’s easier to integrate xmlsec upstream improvements into LibreOffice in the future.
Regarding the other goal, shrinking the patch list is still to be done. ;-)
Today we release LibreOffice 5.2.0, the next step in our journey, and what will become the base of the increasingly stable 5.2.x series. There is a fine suite of new features for people to enjoy - you can read and enjoy all the great news about the user visible features from many great hackers, but there are, as always, many contributors whose work is primarily behind the scenes, and a lot of work that is more technical than user-facing.
Some moons ago, the ESC decided to add some under-the-hood wiki
pages so that people could add their own credits: I encourage you to read
those here: 5.1
There are lots of good things there, and it saves me reading and summarizing
~10k commits each release, but then again - that can be fun too. This is my
very quick attempt to make up for a year of inactivity on this front, and
pluck a few of the un-mentioned bits out of 17,734 commits (that is an average
of ~50 commits every day of the year) from
A great initiative of Norbert Thiebaud has been to collect together most of the infrastructure and entry points that we have at TDF, and build an attractive list of these to help those new to the project find and use our tools and services. Checkout http://devcentral.libreoffice.org/:
LibreOffice has been able to run in a headless mode, doing its own
pixel-bashing for a long time, and this is used intensively by both LibreOffice
Online and also the Linux / gtk3 port. It has been a neverending source of
amazement to myself and others that the (unreadable) template code using
Vigra produces rather poorly performing code for all manner of cases - and
needs special case optimization in the client code.
One of the great joys of LibreOffice 5.2 is the final replacement of vigra,
and the removal of the
basebmp directory which allows us to use
native (and assembler accelerated on eg. ARM) cairo for pixel bashing. While
basebmp has served well and accelerated rendering for years, cairo also gives
us accelerated anti-aliased line rendering and more. Thanks to Caolán
McNamara (RedHat) for that.
There were a large number of OpenGL and OpenCL improvements in this time period.
cache/opengl_device.logfiles with details of your drivers. After lots of work, it was discovered that Intel GL drivers on Windows 7 were flaky beyond belief, so these were black-listed.
vcldemotest paths, improved native widget rendering, faster clipping. There was a chunk of work put into lifecycle fixing, and shutdown cleanup, and many bug fixes.
sc/source/core/opencl/here: Tomaž Vajngerl (Collabora), Tor Lillqvist (Collabora), Noel Grandin (Peralex), Stephan Bergmann (RedHat), Caolán McNamara (RedHat), Markus Mohrhard, Marco Cecchetti (Collabora)
Performance improvements are hard to screenshot; but important nonetheless. We maintain performance regression tests (running under valgrind) at http://perf.libreoffice.org/ - which really helps to pin-point and repair issues as they arise.
One big-win in 5.2 was Armin Le Grand (CIB)'s work to improve our thread-pool, and use it to accelerate the 3D software renderer - which gives a particularly noticable speedup for 3D chart re-rendering.
Markus Mohrhard has done some simply excellent work on crash reporting - to help us find the most frequent crashes on Windows. While many Linux distributions have had similar tools deployed for years, covering Windows is important too. The implementation re-uses Google's Breakpad to create minidumps which are analyzed on the server side and charted prettily at http://crashreport.libreoffice.org/stats/
Markus would love some help from someone with web development skills
to help improve the front-end, and analytic / querying / data presentation
here. Please poke the developer list
This work has already lead to several vital fixes of the top crashers that have been seen in the wild, using good data to nail the worst quality issues. Thanks to Markus Mohrhard, Caolán McNamara (RedHat), and Miklos Vajna (Collabora) who have commits referencing crashreport URLs.
Work is ongoing around code quality in many areas, with 196 or so cppcheck fixes thanks to Caolán McNamara (RedHat), Julien Nabet, Jochen Nitschke, Noel Grandin (Peralex), Michael Weghorn, Takeshi Abe, Giuseppe Castagno and others.
Caolan and the RedHat guys manage to keep the Coverity scan count, and crash-testing (loading and saving ~91k documents to many formats) counts at or around zero at all times, as well as doing fuzzing and other cleanup.
Continuing the VclPtr re-work where we added strong referenced
lifecycle to all our widgets, Dipankar Niranjan in
has cleaned out all of the old & awful 'dog-tag' work that tried to get
lifecycle right in VCL, using much cleaner references.
In more recent times Yurtoglu, Melike Ayse and
Noel Grandin have worked to abstract the
and apply this to Menus, to ensure they are correctly lifecycle managed.
Thanks too to
Jocken Nitschke for internalizing the DeletionListener
which should be removed when we eventually reference count the sal/
Other great work to exorcise manual refcounting comes from
Thomas Arnhold, Daniel Robertson, Noel Grandin, Aleksas Pantechovskis
and especially Xisco Fauli for their work on
converting lots of manually reference counted or copy-on-write structures
to using the nice
cow_wrapper template; as well as converting
pImpl pointers to use std::unique_ptr. This reduces the scope for
programmer error, and missed corner cases and allows us to make
copy-on-write ref-counting thread-safe if necessary. There are 140 cases
fixed, and about 68 refcounting instances still needing love.
We continued to build and execute more critical unit tests this year - each one stopping some suite of regressions from ever returning. Grepping for the relevant TEST and ASSERT macros we continue to grow the number of unit tests:
The LibreOfficeKit API is the foundation of the Android App, GNOME Documents, and the ongoing LibreOffice Online work, and a lot changed in the last year. The two main building blocks of the LOK API are the methods of the exposed objects, and the callback types. Since 5.0, the following new methods has been added:
lok::Office::getFilterTypes()allows obtaining an up to date list of filter name - MIME type pairs, added for GNOME documents.
lok::Office::setDocumentPassword()allows opening password-protected documents.
lok::Office::freeError()allows releasing an error string allocated by the API.
lok::Document::getPartPageRectangles()allows obtaining the size and position of pages in a Writer document.
lok::Document::getTileMode()allows writing clients that work with both the new (Cairo) and the old (Vigra) headless backend (see above).
lok::Document::initializeForRendering()has been extended to allow key-value style options while initializing, like Writer's hide whitespace mode.
lok::Document::postMouseEvent()has been extended to handle click buttons and modifiers.
lok::Document::postUnoCommand()has been extended to get a callback when the result of an executed UNO command is ready.
lok::Document::paste()has been added to handle copy and paste.
lok::Document::getCommandValues()has been added to query possible values for UNO commands (font and style names, Calc row/column header details, Calc cell cursor).
lok::Document::setVisibleArea()has been added to be able to do correct page up / page down.
lok::Document::getViews()have been added as an initial support for collaborative editing.
lok::Document::renderFont()has been added to help providing font previews.
lok::Document::getPartHash()has been added to help clients tracking reordered slides.
lok::Document::paintPartTile()has been added to allow stateless rendering of different parts of a document.
LOK_CALLBACK_DOCUMENT_SIZE_CHANGED: Size of the document changed.
LOK_CALLBACK_SET_PART: The current part number is changed.
LOK_CALLBACK_SEARCH_RESULT_SELECTION: Selection rectangles of the search result when find all is performed.
LOK_CALLBACK_UNO_COMMAND_RESULT: Result of the UNO command execution.
LOK_CALLBACK_CELL_CURSOR: The size and/or the position of the cell cursor changed.
LOK_CALLBACK_MOUSE_POINTER: The current mouse pointer style.
LOK_CALLBACK_CELL_FORMULA: The text content of the formula bar in Calc.
LOK_CALLBACK_CONTEXT_MENU: Context menu structure (after a right-click).
An outcome of our Turkish Hackfest
in Ankarah was discovering that LibreOffice would not even build in the
toupper('i') != 'I' in this locale; fun cf.
Thanks to Krishna Keshav, Gökhan Gurbetoğlu and Apurva Priyadarshi
for the fixes.
A large number of UX / usability papercuts were fixed and improved such as keyboard shortcuts, consistent display issues, mis-sized and mis-placed controls, and some regressions from UI file conversion. Thanks to Caolán McNamara (RedHat), Akshay Deep, Regina Henschel, Maxim Monastirsky, Jürgen Funk (CIB), Bubli Behrens (CIB), Samuel Mehrbrodt (CIB) & Jay Philips.
One metric we watch in the ESC call is who is in the top ten in the freedesktop Weekly bug summary. Here is a list of the people who have appeared more than ten times in the weekly list of top bug closers in order of frequency of appearance: V Stuart Foote, Adolfo Jayme, Cor Nouws, Maxim Monastirsky, Eike Rathke (RedHat), raal, m.a.riosv, Julien Nabet, Caolán McNamara (RedHat), Miklos Vajna (Collabora), Beluga, Alex Thurgood, Michael Meeks (Collabora), Buovjaga, Yousuf (Jay) Philips, Joel Madero, Samuel Mehrbrodt (CIB), Markus Mohrhard, Timur, Jean-Baptiste Faure, Xisco Faulí, Aron Budea, tommy27, Michael Stahl (RedHat), Heiko Tietze, David Tardon, Laurent BP With many thanks to everyone else that helped to close and triage so many bugs for this release.
Thanks fundamentally to Norbert Thiebaud - we now have not only
great Jenkins / CI infrastructure, with gerrit integration - but we have a
much enlarged and more reliable hardware build farm that encourages people to
use Jenkins to check their work before pushing, in turn increasing the
quality and reliability of master. This year we've seen the benefits of
running our full suite of
make check unit tests on our debugging
builds under Linux.
The work Jenkins did for just master in the six month run up to the 5.2 branch point we have 34,124 tinderbox builds covering seven configuration across linux, mac and windows. With 27,737 builds covering three platforms tested on our gerrit infrastructure. This is for the CI managed hardware, there are a number of other volunteer run Tinderbox builders. This is extremely helpful for keeping master build-able and usable, making it easy for newbies to get stuck in. With 60,000 builds for 8k commits we are doing a lot of loop test and validation of the LibreOffice code at CI time.
Some of my favorite heroes are those who open up the code so
that others can work on it ! One of the key tasks there is translating
the remaining German
Comments (a list). The last four thousand lines seem to defy
translation - why this graph should flatten like this - I have simply
no idea. All patches from German speakers who love to finish things -
much appreciated. Many thanks to those who stuck with it, with more
than 2 commits; in order of commit count: Albert Thuswaldner, Phillip Sz,
Thomas Klausner, Chris Sherlock, Philipp Weissenbacher &
We are now down to seven modules left:
include, reportdesign, sc, sfx2, stoc, svx, sw
The 5.2.x releases run well on Windows XP, but we cannot be sure how long our tooling will continue to target that platform. As such - while the ESC has no concrete plans to drop Windows XP support, we are 'deprecating' it after the 5.2.x series - meaning that having a modern C++ compiler and a modern Windows build OS base-line have a higher priority. That means that in future it is possible that future major LibreOffice releases may not run on Windows XP; you have been warned. For now, there is no change here.
I hope you get the idea that more developers continue to find a home at LibreOffice and work together to complete some rather significant work both under the hood, and also on the surface. If you want to get involved there are plenty of great people to meet and work alongside. As you can see individuals ('Assigned') make a huge impact to the diversity of LibreOffice (the colour legends on the right should be read left to right, top to bottom, which maps to top down in the chart):
These charts, made so early in the month are still missing som individuals and commits queued up in gerrit for review - hence the July numbers. In terms of diversity of code commits, we love to see the unaffiliated volunteers contribution by volume, though clearly the volume and balance changes with the season, release cycle, and volunteers vacation / business plans:
Naturally we maintain a list of small, bite-sized tasks which you can use to get involved at our Easy Hacks page, with simple build / setup instructions. It is extremely easy to build LibreOffice, each easy-hack should have code pointers and be a nicely self contained task that is easy to solve. In addition some of them are really nice-to-have features or performance improvements. Please do consider getting stuck in with something.
Another thing that really helps is running pre-release builds and reporting bugs just grab and install a pre-release and you're ready to contribute alongside the rest of the development team.
LibreOffice 5.2 is great; it is made by a set of developers having fun, working together, and building an increasingly attractive and beautiful Free Software Office suite, I hope you enjoy using it. Thanks for reading, don't forget to checkout the user visible feature page and thank you for supporting LibreOffice.
If I have missed your good work out (and this is a very incomplete view based on a few hours of analysis) - please do add yourself to the relevant wiki page and potentially mail me a unified diff to this page; thanks !
I started to work further on a LibreOffice educational portal again these days. This portal (website) was discussed during a work weekend of the German speaking community. I created a first very alpha version during and short after that weekend and set up a development website. The site is driven by Plone and a specific add-on. I got some time to work on this add-on further and got the add-on more i18n-friendly. The add-on is hosted on Github in the account of the Document Foundation:
I added also a new repository for the configuration etc. of a new LibreOffice education website, which brings me to eight hundred commits to Github during the last year
The management of various objects is crucial for LibreOffice Draw, especially when a drawing or a diagram becomes complex with a lot of shapes and groups placed on different layers with an elaborated stack order.
Improvements for the handling of …
At LibreOffice and DocumentFoundation we work hard to make life easier for our many volunteers.
This week is dedicated to a meetup in Kaufbeuren (Germany), where we go through the infrastructure, spreading the knowledge as well as discussing future posibilities.
Our infrastructure is actually quite big, with a lot of services to help Developers/Documenters/Testers and other volunteers.
devcentral gives a nice (but not complete) overview of the developer resources.
Our tinderboxes runs continuously building/testing LibreOffice while our CI system builds every patch submitted, to control the quality before actually integrating the patch into master.
Infra is like the rest of the community, very lively, friendly to new people, so do not be afraid to join us. We have many small and big sysadmin tasks open, so it can be a way for you to get experience.
We all work toward a common goal:
Make sure it continues to be the opensource office suite of high quality and usability.
Tomorrow I go back to spain again for at (in my opinion a well deserved weekend).
Due to a massive disk failure on our hypervisor falco, the following services are offline at the moment:
Other services might be affected as well.
We will keep you up-to-date.
Gerrit, Jenkins, Bugzilla are back up.
Falco needs to be rebooted to rescue, as we ran into a Bug in Debian Jessie (http://unix.stackexchange.com/questions/235643/why-does-mdadm-believe-my-raid1-has-failed-so-using-add-cannot-work)
sanitizers (ASAN, UBSAN, etc.) is a collection of tools to detect memory corruption bugs, undefined behavior and more by instrumenting the code generated by the compiler. (That’s the main difference from valgrind.) From LibreOffice’s perspective one more important difference is that there is a Jenkins_Linux_Ubsan tinderbox that makes sure that the master branch is kept clean from errors detected by a given configuration.
So when the tinderbox failed after a commit of mine, I wanted to set up a similar environment locally, reproduce and fix the bug, and push the fix once I saw that the fix indeed solves the problem. You can set many options both at build and runtime, so while we have some documentation on the TDF wiki (and also Stephan was kind enough to share his config) on how to use these sanitizers, it wasn’t clear to me what to do step by step. So here is one possible setup that worked for me — in my case I wanted to reproduce a stack-use-after-return problem. If you haven’t ever built LibreOffice before, then go to the Development wiki page, first do a normal build, and if everything went fine, came back here.
autogen.input looks like this:
CC=clang -fsanitize=address CXX=clang++ -fsanitize=address --enable-dbgutil --disable-firebird-sdbc
Which is a normal clang debug build, except:
you need to add
CXX (not to
CXXFLAGS), as explained
on the wiki
you need to explicitly disable Firebird integration for now
My first attempt failed at build time, as even the tools used only during the build are instrumented, and some memory leak was detected there, which means the build aborted before reaching the problem I was interested in. To disable leak detection during build, and disable parallelism (I needed this, as I did the build in the background while using the machine for something else):
make build-nocheck ASAN_OPTIONS=detect_leaks=0 PARALLELISM=1
This also means that I explicitly disabled running any tests, as I knew which is the single unit test I want to run for the purposes of reproducing and fixing the problem.
Once the build completed, it turns out that the stack-use-after-return detection is disabled at runtime by default, which means I could not see any problem locally. Here is the commandline to run one specific CppunitTest with this detection on:
cd sw; make -sr CppunitTest_sw_tiledrendering ASAN_OPTIONS=detect_leaks=0:detect_stack_use_after_return=1
Again, this is just one possible setup, you can use other
options, other environment variables during build and during testing — but
hopefully it helps in the future to avoid pushing fixes for such problems
detected by sanitizers just blindly.
Midterms for GSoC 2016 have passed and my first project Redesigning the Template Manager is reaching completion. Therefore, I have decided to encapsulate all the modifications and enhancements that I (along with my mentors, Samuel Mehrbrodt and Yousuf Philips) have made to the Template Manager and some other UI components, namely Start Center, Presentation Wizard, etc. The idea behind the project can be seen here: Introduction: GSoC 2016 with Libreoffice
Overall, my first project went smoothly, thanks to the help and guidance provided by my mentors, Samuel Mehrbrodt and Yousuf Philips. I had a lot of time remaining in the GSoC and hence, I picked up another project, Emoji Toolbar Control. It’s a new idea mentioned here: Bug 100100: Emoji Toolbar Control. I will also follow it with a blog about the enhancements I made and the problems and issues associated with the new feature.
Yesterday I added Get around Brno page to the LibreOffice Conference website. There you can find comprehensive information about public transport in Brno, how to buy tickets, how to get to the hotel/venue if you arrive by train/bus/car/plane etc. All accompanied with maps and pictures of described places. So hopefully no one will get lost on their way to the hotel or venue, or struggle purchasing tickets.
If you’re coming to LibreOffice Conference 2016, definitely check it out. You may also want to download the page for offline usage in case you won’t mobile data.
‘Cause the players gonna play, play, play, play, play
And the haters gonna hate, hate, hate, hate, hate
— Taylor Swift, 1989, Shake It Off
The latest release candidate of the upcoming LibreOffice 5.2.0 feature release is available for installation from the snap store. This makes it very easy to install this prerelease of LibreOffice for testing out new features (an incomplete glimpse on what to look forward for can be found on the LibreOffice 5.2 release notes page, which is still under construction, go on #libreoffice-qa if you want to help with testing).
To install this build of LibreOffice on any snap supported platform just open a terminal and run:
sudo snap install --channel=beta libreoffice
To start this version of LibreOffice, you run:
The full path should only be needed, if you have another version of LibreOffice installed. If that is not the case a plain “libreoffice” should do.
Note that this version is still a prerelease and not for production use yet. That said, it is mostly a full-featured package including everything that would be packaged for end users of LibreOffice. While this package also includes a set of localizations to show that they work, their number has been restricted to English, French, German, Italian, Portuguese (Portugal/Brazil), Spanish for size considerations for now. This set is mostly the one Ubuntu provides on its installer images (removing those that might have issues as they need special fonts).
Another difference to prior downloads is that while LibreOffice still uses X11, now runs in confinement provided by snaps. Unlike previous releases on Ubuntu, this package defaults now to do so via the newer GTK3 backend: This has a lot of advantages, see details on Caolans Blog, but it is also a younger backend, that hasnt has that much time to be polished yet.
a missing-repaint problem in LibreOffice’s headless backend, but the root
cause wasn’t close to the symptom I saw first. Part of the debugging process
was to understand what’s the relation between
sdr::contact::ViewContact is part of the model, and
there is one
sdr::contact::ViewContact object per shape
sdr::contact::ViewObjectContact is part of a view, and there is one
sdr::contact::ViewObjectContact per shape, per view
sdr::contact::ObjectContact is part of a view, and there is one
sdr::contact::ObjectContact per view
So the answer to my original Is it normal that I have two object contacts and a single view contact for a shape and two views? question is: yes, that’s expected. ;-) Hopefully the updated documentation is now more clear, the incorrect 1:N relation in the original class diagram first confused me.
I had to work around an issue with user add form in the LibreOffice templates website and found a solution. I added the user within the Zope Management Interface (ZMI), edited the user, assigned him to a group and reset his password in administration interface later. That takes some extra effort, but in the end it works for now.
LibreOffice Conference 2016 is less than two months away and people are starting to look for information how to get to and around Brno. We’ve prepared a page with extensive information how to get to Brno.
If you go by plane, the best option is flying directly to Brno. You can get very cheap tickets from London-Stansted (Ryanair), London-Luton, Eindhoven (Wizz Air) and moderately cheap tickets from summer destinations (Spain, Greece, Italy,…) with SmartWings. There is also a daily Lufthansa flight to Munich which can connect you with dozens of destinations around the world (it’s particularly good for flights to the US, you can reach East Coast in 10 hours). But the line is rather oriented at business travelers, the plane is small and prices tend to be high.
The second best option is flying to Vienna which has flights to dozens of destinations in the world and prices are pretty good. RegioJet operates direct buses between the airport and Brno, so you can get conveniently to Brno in 2 hours. Another option is the airport in Prague, but it has fewer connected destinations and it takes longer to get from there to Brno.
If you happen to live in Germany, Austria, Poland, Slovakia, or Hungary. Train may be the best option for you. Brno has direct trains to those countries.
You can also come by car. You can be prepared for delays because of many road reconstructions. There is a long-term reconstruction of D1 highway (between Prague and Brno) and there are five sections under reconstruction this season. There are also several more motorways which are partly or completely closed for the same reason. Most of the road work happens during summer holidays, but some of it will be going on in Sept, too. It’s hard to estimate which now. Traffic jams occur, so give yourself enough time if you go to Brno by car.
If you’d like to go by bus, we can recommend RegioJet. They connect Brno with many destinations in Europe, they have very comfortable buses with free hot drinks, cheap snacks, wifi, entertainment systems and for reasonable prices. Other bus companies are e.g. Flixbus or Eurolines.
The LibreOffice community is truly global and attendees from further destinations may not know much about the Czech Republic. Maybe you wonder what’s the currency here, what’s the weather like in Sept etc. We’ve prepared a page with the basic information about the country. For more information we link CzechTurism website where you can learn much more information which is relevant to travelers to the Czech Republic.
Soon, we will also extend information about how to get around Brno (public transport system, how to buy tickets, where, how to get to the conference hotel, venue,…). Stay tuned
I’m only ever using a bleeding edge Clang trunk build myself. So when Fedora enabled use of the GCC abi_tag attribute in libstdc++ (i.e., switched the _GLIBCXX_USE_CXX11_ABI macro to 1 by default), it was only a matter of applying a set of (evolving) patches to Clang to keep things working.
However, others who wanted to use the Clang version included in Fedora were in for more of a problem. The typical symptom being that what you compiled with Clang fails to link against system libraries, most notably libstdc++.
For Fedora 23, we included a somewhat slapdash early version of the relevant Clang patches, but that didn’t survive the split-out of Clang from the overall LLVM package in Fedora 24. But now that the Clang upstream patches are deemed stable (and have been integrated into trunk towards Clang 3.9), I backported them to the Clang 3.8 in Fedora 24 (and rawhide).
And a lot of thanks to all of those who created these patches!
I am building a multiroom audio system (do not have money to buy a Sonos system). The system is based on 3 Raspberry PI 3 (2 Rooms + Television) and a NAS.
I have installed Raspbian (Debian Linux) and Kodi (former XBMC) and was testing on my Television. Raspian comes with a simple graphic desktop, so of course I took a look around and found to my surprise LibreOffice.
This had to be tested, LibreOffice, which everybody says is a mammut chunk of software, on a small Raspberry PI 3, sounded impossible. But as you can it actually worked pretty well. Admitted using the remote control to write was kind of interesting
This is the raspberry PI. It perform like a late PC from aroun 98, with a price of only 35 EUR.
So my multiroom audio is going to cost:
And of course a free version of LibreOffice.
The LibreOffice community consist of all kinds of people, distributed around the globe and have experience in different fields. Anybody can help, Users can help test our new features, Developers can help to solve bug or add new exciting features.
Hoping to see you in our community.
Just how much is our Clang plugin slowing down builds of LibreOffice? We are constantly adding more and more useful functionality to it, and some of it is well known to be written in a way that is likely performing not too well. But I never dared look at the performance implications too closely, for fear of being disappointed. The build always seemed to go along at more or less the same speed, so who cares for details?
Enter FlameGraph, generating beautiful and easy-to-digest graphs on top of the Linux perf tool’s (or others’) output. So I gathered data about half a minute of CPU activity during the LibreOffice build (randomly picked a time when all the cores were busy compiling .cxx files in the sw module, to keep noise contributed by other processes down to a minimum), and passed it through FlameGraph. And sobering set in:98.56% of all the time was spent in the clang-3.9 process (i.e., there was almost no noise from unrelated processes). And 19.22% of all time was spent in our plugin. That is, the plugin slows down compilation by about 25%. Quite a number.
Zooming in and breaking this down further per individual plugin, the distribution is
The recursive nature of RecursiveASTVisitor makes it a bit hard to easily spot each individual plugin’s hotspots, but one thing sticks out: CommaOperator is a rather simple piece of code (that shouldn’t need much heavy computation), but does use lopluign::Pluign::parentStmt, which rebuilds the AST to determine a node’s parent, and is really, really expensive.
Room for improvement. Time to clean up.
(At first, the generated graph looked way less interesting. One thing that was necessary was to build both LLVM/Clang and our plugin with -fno-omit-frame-pointer. The other thing was to teach FlameGraph to support “(anonymous namespace)” in C++ function names.)