I've had this problem twice in the last year, I'm testing something related to touch in my laptop and I'm stuck trying to figure out if it's my code that is wrong or if my screen is misconfigured and it's only sending mouse events.
Thanks to Shawn of Qt fame for having helped me the two times and explained me how to test if my screen is sending touch events, I'm writing this blog so i don't forget and ask him a third time :D
First step is figuring out the xinput id of the touch screen of my laptop
tsdgeos@yoga:~:$ xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Wacom Co.,Ltd. Pen and multitouch sensor Finger id=9 [slave pointer (2)]
⎜ ↳ ETPS/2 Elantech TrackPoint id=13 [slave pointer (2)]
⎜ ↳ ETPS/2 Elantech Touchpad id=14 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Sleep Button id=8 [slave keyboard (3)]
↳ Wacom Co.,Ltd. Pen and multitouch sensor Pen id=10 [slave keyboard (3)]
↳ Integrated Camera id=11 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]
↳ ThinkPad Extra Buttons id=15 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
In this case would be id=9
Then you can do
tsdgeos@yoga:~:$ xinput test-xi2 9
and if the output contains RawTouchBegin and RawTouchEnd events, it means that the screen is correctly sending touch events :)
Next you probably want to check if Qt actually is seeing those events, for that there's a few ready to use demos in the qtdeclarative source code, so I would do
tsdgeos@yoga:~:$ qml qt5/qtdeclarative_58/examples/quick/touchinteraction/multipointtouch/multiflame.qml
And after putting my five fingers on the screen I would see
So all is good, the bug is my code and not in Qt or the configuration of my touch screen :D
A blog about random things and sometimes about my work translating and developing KDE and anything
Thursday, August 24, 2017
How to check if your touch screen is really sending touch events
Etiquetes de comentaris:
multitouch,
qt,
touch screen,
xinput
Tuesday, August 01, 2017
Big day in poppler-land
Today in Poppler:
* Poppler 0.57 got released
* We agreed to stop supporting openjpeg 1.x at the end of the year
* We agreed to stop supporting Qt 4.x at the end of the year
* We merged the better_object branch
The last one is the one that is really big, since it introduces a big rework of the Object class, a central component to Poppler. Object is much used like a QVariant, i.e. it can hold various kind of data inside and you can pass it around.
Unfortunately the Object implementation we inherited from xpdf was kind of hard to use, having to basically do the memory management by hand. i.e. destroying the object was not enough to free the memory, you had to call free() on it.
Thanks to C++11 now we have an implementation with move semantics that greatly simplifies the use of Object and will hopefully make for less memory management mistakes.
Let's hope we didn't break anything in the process though :D
* Poppler 0.57 got released
* We agreed to stop supporting openjpeg 1.x at the end of the year
* We agreed to stop supporting Qt 4.x at the end of the year
* We merged the better_object branch
The last one is the one that is really big, since it introduces a big rework of the Object class, a central component to Poppler. Object is much used like a QVariant, i.e. it can hold various kind of data inside and you can pass it around.
Unfortunately the Object implementation we inherited from xpdf was kind of hard to use, having to basically do the memory management by hand. i.e. destroying the object was not enough to free the memory, you had to call free() on it.
Thanks to C++11 now we have an implementation with move semantics that greatly simplifies the use of Object and will hopefully make for less memory management mistakes.
Let's hope we didn't break anything in the process though :D
Etiquetes de comentaris:
C++11,
move semantics,
poppler
Thursday, June 15, 2017
KDE Applications 17.08 Schedule finalized
It is available at the usual place https://community.kde.org/Schedules/Applications/17.08_Release_Schedule
Dependency freeze is in 4 weeks and Feature Freeze in 5 weeks, so hurry up!
Dependency freeze is in 4 weeks and Feature Freeze in 5 weeks, so hurry up!
Thursday, April 20, 2017
Okular 1.1 released!
Today KDE Applications 17.04 was released.
It includes Okular 1.1, it contains a nice set of features:
* Add annotation resize functionality
* Add support for auto-calculation of form contents via JavaScript
* Allow to rotate the page view using two-finger pinches on a touchscreen
* Change pages in presentation mode by swiping on touch screen
* Added support for Links that change the Optional Content visibility status
* Allow to disable automatic search while typing
* Allow to create bookmarks from the Table Of Contents
This release was brought to you by Albert Astals Cid, Oliver Sander, Luigi Toscano, Martin T. H. Sandsmark, Tobias Deiminger, Antonio Rojas, Burkhard Lück, Christoph Feck, Elvis Angelaccio, Gilbert Assaf, Heiko Becker, Hrvoje Senjan, Marco Scarpetta, Miklós Máté, Pino Toscano, Yuri Chornoivan.
It includes Okular 1.1, it contains a nice set of features:
* Add annotation resize functionality
* Add support for auto-calculation of form contents via JavaScript
* Allow to rotate the page view using two-finger pinches on a touchscreen
* Change pages in presentation mode by swiping on touch screen
* Added support for Links that change the Optional Content visibility status
* Allow to disable automatic search while typing
* Allow to create bookmarks from the Table Of Contents
This release was brought to you by Albert Astals Cid, Oliver Sander, Luigi Toscano, Martin T. H. Sandsmark, Tobias Deiminger, Antonio Rojas, Burkhard Lück, Christoph Feck, Elvis Angelaccio, Gilbert Assaf, Heiko Becker, Hrvoje Senjan, Marco Scarpetta, Miklós Máté, Pino Toscano, Yuri Chornoivan.
Tuesday, April 04, 2017
Akademy 2017 Call for Papers deadline is in a week!
The Akademy 2017 Call for Papers ends April 10th at 23:59:59 CEST.
Surely you have interesting stuff to share with the community, so go to https://akademy.kde.org/2017/cfp and submit a proposal!
Surely you have interesting stuff to share with the community, so go to https://akademy.kde.org/2017/cfp and submit a proposal!
Tuesday, March 07, 2017
Okular table selection mode is amazing
I case you didn't know ;)
Okular has a amazing table select mode where you select an area and Okular will auto detect rows and columns on it (you can fine-tune it afterwards) and then you can directly copy&paste to a spreadsheet :)
It's mostly tested on PDF files, but should work the same on any of the formats we support text extraction.
Update: This feature is not new, just i got to use it today ;) Video at https://www.youtube.com/watch?v=E8XWI06tltY
Okular has a amazing table select mode where you select an area and Okular will auto detect rows and columns on it (you can fine-tune it afterwards) and then you can directly copy&paste to a spreadsheet :)
It's mostly tested on PDF files, but should work the same on any of the formats we support text extraction.
Update: This feature is not new, just i got to use it today ;) Video at https://www.youtube.com/watch?v=E8XWI06tltY
Wednesday, March 01, 2017
Okular Form Field auto-updating (Work In Progress)
You can see it in https://www.youtube.com/watch?v=fCLFkpaW3Ug
As the description of the YouTube video says:
Form 14 updates from Form 13 values as defined by the PDF file.
There's a few bugs left:
* To make the page contents update i need to edit another form in the page of the form that is being auto updated
* The contents of the "editable" Form are not updated. (The form is actually not editable since it's readonly)
And also a pile of uncommited and unreviewed patches, and probably only works for very simple files like this one, but it's a start :)
Update: It works fine now and everything has been commited :) https://www.youtube.com/watch?v=S-zmHc3WUhs
As the description of the YouTube video says:
Form 14 updates from Form 13 values as defined by the PDF file.
There's a few bugs left:
* To make the page contents update i need to edit another form in the page of the form that is being auto updated
* The contents of the "editable" Form are not updated. (The form is actually not editable since it's readonly)
And also a pile of uncommited and unreviewed patches, and probably only works for very simple files like this one, but it's a start :)
Update: It works fine now and everything has been commited :) https://www.youtube.com/watch?v=S-zmHc3WUhs
Thursday, February 16, 2017
KDE Applications 17.04 Schedule finalized
It is available at the usual place https://community.kde.org/Schedules/Applications/17.04_Release_Schedule
Dependency freeze is in 4 weeks and Feature Freeze in 5 weeks, so hurry up!
Dependency freeze is in 4 weeks and Feature Freeze in 5 weeks, so hurry up!
Thursday, December 15, 2016
KDE Applications 16.12.0 just out!
See https://www.kde.org/announcements/announce-applications-16.12.0.php for the announcement and https://www.kde.org/announcements/fulllog_applications.php?version=16.12.0 for the reaaaaaaaaally long changelog.
Well done everyone :)
Well done everyone :)
Wednesday, December 07, 2016
The dangers of stable/LTS/supported versions
Ubuntu 14.04 LTS is supported until April 2019 and ships poppler 0.24.5 http://packages.ubuntu.com/search?suite=trusty&searchon=names&keywords=libpoppler-dev
RHEL 7.3 ships poppler 0.26.5 (I may be wrong, https://git.centos.org/summary/?r=rpms/poppler is the best info i could find, Red Hat does not make easy to know what you're buying)
Debian stable (Jessie) ships poppler 0.26.5 https://packages.debian.org/search?suite=jessie&searchon=names&keywords=libpoppler-dev
Current release is poppler 0.49 https://poppler.freedesktop.org/releases.html
This means that people are running stable versions and thinking they are secure, but if we trust security specialists, [almost] every crash can be exploited, and I'm almost sure neither Ubuntu nor RedHat nor Debian have backported all of the crash fixes of the more than 20 releases and 2 years of development behind those *very old* versions they are shipping.
I don't know how/if this can be fixed, but i honestly think we're giving users a false sense of security by letting them run those versions.
RHEL 7.3 ships poppler 0.26.5 (I may be wrong, https://git.centos.org/summary/?r=rpms/poppler is the best info i could find, Red Hat does not make easy to know what you're buying)
Debian stable (Jessie) ships poppler 0.26.5 https://packages.debian.org/search?suite=jessie&searchon=names&keywords=libpoppler-dev
Current release is poppler 0.49 https://poppler.freedesktop.org/releases.html
This means that people are running stable versions and thinking they are secure, but if we trust security specialists, [almost] every crash can be exploited, and I'm almost sure neither Ubuntu nor RedHat nor Debian have backported all of the crash fixes of the more than 20 releases and 2 years of development behind those *very old* versions they are shipping.
I don't know how/if this can be fixed, but i honestly think we're giving users a false sense of security by letting them run those versions.
No one "works" on Poppler
I thought that was obvious, but today someone thought that i was "working" as "paid working" on it.
No, I don't get paid for the work i do on Poppler.
It's my computing hobby, and on top of that it's not even my "primary" computing hobby, lots of KDE stuff take precedence over it, and i guess Gnome stuff may also take precedence for Carlos (second top commiter according to the git shortlog)
Aside a few paid contributions and some patches that may have come from people that use the software on their business (and we could file them under "paid" since they did the fix as part of their job) no one has a paid job that is mainly "work on poppler".
I guess we've done a good enough job as hobbyist :)
Obviously we could do better, so if you have lots of money and are interested in making free software PDF rendering beter please hire someone to help us (no, this is not me asking for money, I've a good enough job already).
And if you don't have money but you have some free time and like to help, join us :)
And if you really really have some free time or lots of money you could port Okular, Evince et al to pdfium and see if it's actually better/worse than poppler.
No, I don't get paid for the work i do on Poppler.
It's my computing hobby, and on top of that it's not even my "primary" computing hobby, lots of KDE stuff take precedence over it, and i guess Gnome stuff may also take precedence for Carlos (second top commiter according to the git shortlog)
Aside a few paid contributions and some patches that may have come from people that use the software on their business (and we could file them under "paid" since they did the fix as part of their job) no one has a paid job that is mainly "work on poppler".
I guess we've done a good enough job as hobbyist :)
Obviously we could do better, so if you have lots of money and are interested in making free software PDF rendering beter please hire someone to help us (no, this is not me asking for money, I've a good enough job already).
And if you don't have money but you have some free time and like to help, join us :)
And if you really really have some free time or lots of money you could port Okular, Evince et al to pdfium and see if it's actually better/worse than poppler.
Etiquetes de comentaris:
free software,
pdf,
poppler
Tuesday, November 15, 2016
Finding a valid build order for KDE repositories
KDE has been lately been growing quite a bit in repositories, and it's not always easy to tell what needs to be build before, do i build first kdepim-apps-libs or pimcommon?
A few days ago i was puzzled by the same question and realized we have the answer in the dependency-data-* files from the kde-build-metadata repository.
They define what depends on what so what we need to do is just build a graph with those dependencies and get a valid build order from it.
Thankfully python already has a module for graphs and stuff so build-order.py was not that hard to write.
So say you want to know a valid build order for the stable repositories based on kf5-qt5
Here it is
Note i've been saying *a* valid build order, not *the* valid build order, since there are various orders that are valid since not every repo depends other repos.
Now i wonder, does anyone else find this useful? And if so to which repository do you think i should commit such script?
A few days ago i was puzzled by the same question and realized we have the answer in the dependency-data-* files from the kde-build-metadata repository.
They define what depends on what so what we need to do is just build a graph with those dependencies and get a valid build order from it.
Thankfully python already has a module for graphs and stuff so build-order.py was not that hard to write.
So say you want to know a valid build order for the stable repositories based on kf5-qt5
Here it is
Note i've been saying *a* valid build order, not *the* valid build order, since there are various orders that are valid since not every repo depends other repos.
Now i wonder, does anyone else find this useful? And if so to which repository do you think i should commit such script?
KDE Applications 16.12 branches created
The dependency freeze for KDE Applications 16.12 is on since November 10
For all repositories part of the KDE Applications 16.12 release the Applications/16.12 branch has been created.
The list of modules+branches that will be part of the release is at https://cgit.kde.org/sysadmin/release-tools.git/tree/modules.git?h=Applications/16.12
Please make sure the list is correct. If it's not please email release-team at kde.org *NOW*
From now on master is open for feature changes, but remember that all your fixes also should get to the Applications/16.12 branch (my suggestion, commit fixes to Applications/16.12 and then merge that branch to master)
KDE Applications 16.12 Beta (version number 16.11.80) will be tagged November 17 at 23:59 UTC
Once the Beta is tagged no more features can be added.
For all repositories part of the KDE Applications 16.12 release the Applications/16.12 branch has been created.
The list of modules+branches that will be part of the release is at https://cgit.kde.org/sysadmin/release-tools.git/tree/modules.git?h=Applications/16.12
Please make sure the list is correct. If it's not please email release-team at kde.org *NOW*
From now on master is open for feature changes, but remember that all your fixes also should get to the Applications/16.12 branch (my suggestion, commit fixes to Applications/16.12 and then merge that branch to master)
KDE Applications 16.12 Beta (version number 16.11.80) will be tagged November 17 at 23:59 UTC
Once the Beta is tagged no more features can be added.
Sunday, October 23, 2016
KDE Applications 16.12 Schedule finalized
It is available at the usual place https://community.kde.org/Schedules/Applications/16.12_Release_Schedule
Dependency freeze is in 2.5 weeks and Feature Freeze in 3.5 weeks, so hurry up!
Dependency freeze is in 2.5 weeks and Feature Freeze in 3.5 weeks, so hurry up!
Etiquetes de comentaris:
kde applications,
release schedule
Tuesday, August 30, 2016
I'm going to Akademy :)
Saturday, July 02, 2016
KDE Applications 16.08 Schedule finalized
It is available at the usual place https://community.kde.org/Schedules/Applications/16.08_Release_Schedule
Dependency freeze is in 2 weeks and Feature Freeze in 3 weeks, so hurry up!
Dependency freeze is in 2 weeks and Feature Freeze in 3 weeks, so hurry up!
Etiquetes de comentaris:
16.08,
kde applications,
release schedule
Tuesday, May 03, 2016
Akademy 2016 travel support
If you want to attend Akademy 2016 but are a bit short on money, that is no excuse :)
Read https://mail.kde.org/pipermail/kde-community/2016q2/002758.html for more info on how the KDE e.V. can help you!
Read https://mail.kde.org/pipermail/kde-community/2016q2/002758.html for more info on how the KDE e.V. can help you!
Friday, March 11, 2016
Workaround for trouble with updating akonadi tables
I was just updating the Kubuntu packages that move from akonadi 15.08 to 15.12.1 and sadly akonadi failed to migrate with this error
Adding new foreign key constraints
"ALTER TABLE PimItemFlagRelation ADD FOREIGN KEY (PimItem_id) REFERENCES PimItemTable(id) ON UPDATE CASCADE ON DELETE CASCADE"
Updating index failed:
Sql error: Cannot add or update a child row: a foreign key constraint fails (`akonadi`.`#sql-6ea8_3`, CONSTRAINT `#sql-6ea8_3_ibfk_1` FOREIGN KEY (`PimItem_id`) REFERENCES `pimitemtable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE) QMYSQL: Unable to execute query
Query: ALTER TABLE PimItemFlagRelation ADD FOREIGN KEY (PimItem_id) REFERENCES PimItemTable(id) ON UPDATE CASCADE ON DELETE CASCADE
""
Unable to initialize database.
Bug 354536 will be fixed with the akonadi 15.12.3 release next week.
Lucky meanwhile amazing Dan was ready to help me workaround the issue.
You need to start mysql (if that's what you're using as akonadi backend)
mysqld --defaults-file=$HOME/.local/share/akonadi/mysql.conf --datadir=$HOME/.local/share/akonadi/db_data --socket=/tmp/akonadi-mysql.socket
then connect to it
mysql -S /tmp/akonadi-mysql.socket
And run a series of sql commands
http://paste.ubuntu.com/15344766/
After that shut down mysql
mysqladmin -S /tmp/akonadi-mysql.socket shutdown
And start akonadi and you should be golden again
akonadictrl start
Adding new foreign key constraints
"ALTER TABLE PimItemFlagRelation ADD FOREIGN KEY (PimItem_id) REFERENCES PimItemTable(id) ON UPDATE CASCADE ON DELETE CASCADE"
Updating index failed:
Sql error: Cannot add or update a child row: a foreign key constraint fails (`akonadi`.`#sql-6ea8_3`, CONSTRAINT `#sql-6ea8_3_ibfk_1` FOREIGN KEY (`PimItem_id`) REFERENCES `pimitemtable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE) QMYSQL: Unable to execute query
Query: ALTER TABLE PimItemFlagRelation ADD FOREIGN KEY (PimItem_id) REFERENCES PimItemTable(id) ON UPDATE CASCADE ON DELETE CASCADE
""
Unable to initialize database.
Bug 354536 will be fixed with the akonadi 15.12.3 release next week.
Lucky meanwhile amazing Dan was ready to help me workaround the issue.
You need to start mysql (if that's what you're using as akonadi backend)
mysqld --defaults-file=$HOME/.local/share/akonadi/mysql.conf --datadir=$HOME/.local/share/akonadi/db_data --socket=/tmp/akonadi-mysql.socket
then connect to it
mysql -S /tmp/akonadi-mysql.socket
And run a series of sql commands
http://paste.ubuntu.com/15344766/
After that shut down mysql
mysqladmin -S /tmp/akonadi-mysql.socket shutdown
And start akonadi and you should be golden again
akonadictrl start
Wednesday, February 10, 2016
KDE Applications 16.04 Schedule finalized
It is available at the usual place https://techbase.kde.org/Schedules/Applications/16.04_Release_Schedule.
Dependency freeze is in 4 weeks and Feature Freeze in 6 weeks, so hurry up!
Dependency freeze is in 4 weeks and Feature Freeze in 6 weeks, so hurry up!
Etiquetes de comentaris:
kde applications,
release schedule
Sunday, September 27, 2015
KDE dinner in Berlin - October 3
This weekend the KDE e.V. board is going to have an in-person board meeting in Berlin.
We would like you to join us for dinner on Saturday 3 around 19:00 (location still undecided, suggestions accepted).
If you are interested in talking about KDE, KDE e.V., Free Software, Open Source, today's elections in Catalonia or any other random talk and want to have a good time let me know that you're coming (latest by Wednesday night).
We would like you to join us for dinner on Saturday 3 around 19:00 (location still undecided, suggestions accepted).
If you are interested in talking about KDE, KDE e.V., Free Software, Open Source, today's elections in Catalonia or any other random talk and want to have a good time let me know that you're coming (latest by Wednesday night).
Saturday, September 26, 2015
September 26: SystemSettings and KCMs bug triaging day!
Today/Tomorrow September 26 is SystemSettings and KCMs bug triaging day.
As described by Jeremy in this post in the KDE Gardening mailing list the purpose is:
1. Triage all bugs in the systemsettings product (and maybe the kcm product too).
2. If a bug is reproducible still, comment on it and find someone that knows how to fix it and convince them to do so.
3. Find maintainers for as many of the kcms as we can.
This is something anyone with a relatively new Plasma installed can help with so join us on September 26 at the #kde-devel IRC channel!
Personally I'll be on from 10am Spanish time until around 4pm with some lunch time in between.
More info at the gardening wiki for SystemSettings
As described by Jeremy in this post in the KDE Gardening mailing list the purpose is:
1. Triage all bugs in the systemsettings product (and maybe the kcm product too).
2. If a bug is reproducible still, comment on it and find someone that knows how to fix it and convince them to do so.
3. Find maintainers for as many of the kcms as we can.
This is something anyone with a relatively new Plasma installed can help with so join us on September 26 at the #kde-devel IRC channel!
Personally I'll be on from 10am Spanish time until around 4pm with some lunch time in between.
More info at the gardening wiki for SystemSettings
Etiquetes de comentaris:
gardening,
kde,
system settings
Tuesday, August 18, 2015
Using git the proper way for correct release changelogs
If you look at kdenlive's changelog for KDE Applications 15.08 and for KDE Applications 15.04.3 you'll see that "Fix autosave not working when opening project file from command line or click in file browser" shows up in both.
On the other hand if you have a look at gwenview, in 15.04.3 it shows "Make saving thumbnails work again" while it's not part of 15.08.
Does that mean that this bug got lost?
No, gwenview is actually the correct thing, we should not mention a bug again for 15.08 if it was released in 15.04.3, since well it's been released already :D
So why does kdenlive, marble and others show commits in the two places?
Because their developers are not doing the proper git-thing of commiting to the oldest supported branch and then merging up to master, so for git it's two different commits instead of the same (in case of the kdenlive commit in question it'd be https://quickgit.kde.org/?p=kdenlive.git&a=commit&h=cc55a9cea5c2f029744f8aba79a362fd302ec0bb and https://quickgit.kde.org/?p=kdenlive.git&a=commit&h=28b3cc7b5141fcc2fed84433b9fe9851c35b7e08).
Commiting the fix to the oldest supported branch and then merging up has lots of other benefits (like making sure you never forget a fix in master), but maybe this is the one that finally convinces more devs to switch to it, nicer changelogs ;)
On the other hand if you have a look at gwenview, in 15.04.3 it shows "Make saving thumbnails work again" while it's not part of 15.08.
Does that mean that this bug got lost?
No, gwenview is actually the correct thing, we should not mention a bug again for 15.08 if it was released in 15.04.3, since well it's been released already :D
So why does kdenlive, marble and others show commits in the two places?
Because their developers are not doing the proper git-thing of commiting to the oldest supported branch and then merging up to master, so for git it's two different commits instead of the same (in case of the kdenlive commit in question it'd be https://quickgit.kde.org/?p=kdenlive.git&a=commit&h=cc55a9cea5c2f029744f8aba79a362fd302ec0bb and https://quickgit.kde.org/?p=kdenlive.git&a=commit&h=28b3cc7b5141fcc2fed84433b9fe9851c35b7e08).
Commiting the fix to the oldest supported branch and then merging up has lots of other benefits (like making sure you never forget a fix in master), but maybe this is the one that finally convinces more devs to switch to it, nicer changelogs ;)
Etiquetes de comentaris:
changelogs,
git,
release
Sunday, August 09, 2015
KDE Workspaces 4.11 End of Life this August
Back in August 2013 we promised to do Long Term Support for kde-workspace for 2 years.
This means this August is the last release for kde-workspace (coming with KDE Applications 15.08.0).
Of course, we can extend the releases if anyone has a strong reason.
If you do, head to the release-team mailing list!
This means this August is the last release for kde-workspace (coming with KDE Applications 15.08.0).
Of course, we can extend the releases if anyone has a strong reason.
If you do, head to the release-team mailing list!
Sunday, August 02, 2015
rsibreak port to KF5 started!
I just started the port of rsibreak to KF5.
Contributions at http://quickgit.kde.org/?p=rsibreak.git
Contributions at http://quickgit.kde.org/?p=rsibreak.git
Saturday, August 01, 2015
Akademy 2015 and Akademy-es 2015 recap
I'm back home after more than a week of talks and hacking in the beautiful city of A Coruña.
There I attended Akademy, the international conference of the KDE Community, and Akademy-es, it's Spanish counterpart.
First off I'd like to thank the local organization, GPUL, that as always has done an amazing job in hosting us, repeating the success of Guademy, Akademy-es 2008, KDE-EDu sprint, etc.
Also kudos to the Scottish-Kenny duo, top notch organizing work as always.
Finally thanks to the both Akademy and Akademy-es sponsors. Specially Qindel, that sponsored us for the first time, hope we can continue the relationship in the future.
The talks this year were specially interesting, I attended some good BoFs on releasing and translation infrastructure, hopefully some improvements coming your way soon :)
Of course not everything is perfect and my biggest pain point this year was that we did not have as much people in Akademy-es as we expected. Akademy-es happened the 2 days before Akademy and this meant that lots of local people from the organization team were helping set up the place instead of attending the talks; also on Friday some of us (I count at least 8) were attending the KDE e.V. General Assembly so couldn't attend Akademy-es either. Definitely something to think about and improve next time Akademy and Akademy-es happen at the same place.
But all in all pretty positive experience as always, nice to meet so many KDE people :)
There I attended Akademy, the international conference of the KDE Community, and Akademy-es, it's Spanish counterpart.
First off I'd like to thank the local organization, GPUL, that as always has done an amazing job in hosting us, repeating the success of Guademy, Akademy-es 2008, KDE-EDu sprint, etc.
Also kudos to the Scottish-Kenny duo, top notch organizing work as always.
Finally thanks to the both Akademy and Akademy-es sponsors. Specially Qindel, that sponsored us for the first time, hope we can continue the relationship in the future.
The talks this year were specially interesting, I attended some good BoFs on releasing and translation infrastructure, hopefully some improvements coming your way soon :)
Of course not everything is perfect and my biggest pain point this year was that we did not have as much people in Akademy-es as we expected. Akademy-es happened the 2 days before Akademy and this meant that lots of local people from the organization team were helping set up the place instead of attending the talks; also on Friday some of us (I count at least 8) were attending the KDE e.V. General Assembly so couldn't attend Akademy-es either. Definitely something to think about and improve next time Akademy and Akademy-es happen at the same place.
But all in all pretty positive experience as always, nice to meet so many KDE people :)
Etiquetes de comentaris:
akademy,
akademy-es,
coruña
Friday, May 15, 2015
KDE Applications 15.08 release schedule
We have just made official the release schedule for KDE Applications 15.08.
It's a bit simpler than in previous times, let's see if it works out.
Freeze is in 2 months
Full schedule at https://techbase.kde.org/Schedules/Applications/15.08_Release_Schedule
It's a bit simpler than in previous times, let's see if it works out.
Freeze is in 2 months
Full schedule at https://techbase.kde.org/Schedules/Applications/15.08_Release_Schedule
Etiquetes de comentaris:
15.08,
kde,
release schedule
Wednesday, May 13, 2015
Help the KDE eV write a privacy policy for Piwik
We want to enable piwik to get meaningful statistics of kde.org visits, to be nice with privacy for that we have enabled the ip anonymizer plugin but we still need to provide a way for people to opt out.
More info at the todo.kde.org task (Use this link if you don't have a KDE identity account)
More info at the todo.kde.org task (Use this link if you don't have a KDE identity account)
Wednesday, March 25, 2015
Dear Lazyweb: What to visit in Alaska?
I'm holidaying in Alaska for a few weeks around June, anyone has been there and can share the stuff we should totally not miss/do when visiting?
Tuesday, March 24, 2015
Akademy-es 2015 registration open
We have just opened the registration for Akademy-es 2015.
This year we are piggy-backing on the Akademy 2015 registration system since Akademy-es 2015 happens in the same place just 2 days before so we thought it made sense have a common registration for both.
More info at https://www.kde-espana.org/akademy-es2015/registro.php
See you at A Coruña!
This year we are piggy-backing on the Akademy 2015 registration system since Akademy-es 2015 happens in the same place just 2 days before so we thought it made sense have a common registration for both.
More info at https://www.kde-espana.org/akademy-es2015/registro.php
See you at A Coruña!
Sunday, March 22, 2015
Submit your talk to Akademy 2015!
The Call for Papers deadline for Akademy 2015 is just 10 days away. So you should submit a talk now, you know you have cool stuff to share, so do a small write up and tell the world that awesome new stuff you're working on.
And of course don't forget to register as always it's free but let's us know how many of you nice people are going to come over ;)
Ah and we also have the badges available, thanks to Alba Carro for the nice pictures :)
And of course don't forget to register as always it's free but let's us know how many of you nice people are going to come over ;)
Ah and we also have the badges available, thanks to Alba Carro for the nice pictures :)
Etiquetes de comentaris:
akademy,
call for papers,
kde,
talk
Friday, March 20, 2015
KDE dinner in Berlin - April 11
In a few weeks (April 11-12) the KDE e.V. board is going to have an in-person board meeting in Berlin.
We board people have to eat from time to time and since we like talking to other people besides ourselves we’re organizing a dinner on Saturday 11 around 19:00 (location still undecided, suggestions accepted).
So if you are interested in talking about KDE, KDE e.V., Free Software, Open Source, or any other random talk and want to have a good time let me know that you're coming as soon as possible, space is limited.
We board people have to eat from time to time and since we like talking to other people besides ourselves we’re organizing a dinner on Saturday 11 around 19:00 (location still undecided, suggestions accepted).
So if you are interested in talking about KDE, KDE e.V., Free Software, Open Source, or any other random talk and want to have a good time let me know that you're coming as soon as possible, space is limited.
Tuesday, February 17, 2015
KRecipes Gardening Day: Saturday 21 February
It's clear the current KRecipes gardening effort is not having much traction, but before moving on to different applications, let's try a different format, the Gardening Day.
This Saturday 21 February we will meet at #kde-devel on freenode IRC from 9 UTC onwards (It'll probably go well into the UTC late-afternoon) to work on KRecipes.
There's three main topics:
* Triage and fix bugs
* Make tests pass in jenkins
* Port code away from Qt3Support/KDE3Support (without breaking stuff :D)
If we have some extra time we can try to work on some feature like using
KUnitConversion to convert between units.
You don't need to be an expert on KRecipes to help, so join us :)
This Saturday 21 February we will meet at #kde-devel on freenode IRC from 9 UTC onwards (It'll probably go well into the UTC late-afternoon) to work on KRecipes.
There's three main topics:
* Triage and fix bugs
* Make tests pass in jenkins
* Port code away from Qt3Support/KDE3Support (without breaking stuff :D)
If we have some extra time we can try to work on some feature like using
KUnitConversion to convert between units.
You don't need to be an expert on KRecipes to help, so join us :)
Wednesday, February 11, 2015
KDE Applications 15.04 Feature Freeze is in 2 weeks
As per our Release Schedule, the freeze for KDE Applications 15.04 is in two weeks (25 February).
Get yourselves ready!
Get yourselves ready!
Etiquetes de comentaris:
freeze,
kde,
kde applications
Friday, February 06, 2015
Qt 5.4 QML -> C++ QVariant issues
I usually don't blog about what I do in my day-time job in my personal blog but since this may affect some of the KDE/Qt developers I will do this time.
Qt 5.4 was released three months ago; at Canonical we're starting to move the Ubuntu Pĥone codebase to it now and it has an important behavior change as noted in it's changes file (that is quite hard to find by the way, it took me like 5 minutes to find, and that's knowing it existed, searching for "qt 5.4 changelog" does not return http://qt-project.org/wiki/Change-files-in-Qt-5.4.0 that is the important page) that has affected us in many places
The important behavior change is that now some QVariants will be passed to C++ as QJSValue-QVariants instead of QStringList-QVariants, QMap-QVariants, etc so if your code did things like checking the variant type now it will fail, so basically for any C++ function that receives QVariants from QML you need to add extra code to unbox the QVariant, i.e.
Qt 5.4 was released three months ago; at Canonical we're starting to move the Ubuntu Pĥone codebase to it now and it has an important behavior change as noted in it's changes file (that is quite hard to find by the way, it took me like 5 minutes to find, and that's knowing it existed, searching for "qt 5.4 changelog" does not return http://qt-project.org/wiki/Change-files-in-Qt-5.4.0 that is the important page) that has affected us in many places
The important behavior change is that now some QVariants will be passed to C++ as QJSValue-QVariants instead of QStringList-QVariants, QMap-QVariants, etc so if your code did things like checking the variant type now it will fail, so basically for any C++ function that receives QVariants from QML you need to add extra code to unbox the QVariant, i.e.
void MyClass::myFunction(QVariant v)
{
// unbox the QVariant-QJSValue
if (v.userType() == qMetaTypeId<QJSValue>()) {
v = v.value<QJSValue>().toVariant();
}
// This is your old code that checks the type
// of the QVariant is a valid one
if (v.type() != QVariant::Map &&
v.type() != QVariant::List &&
v.type() != QVariant::StringList) {
qWarning() << "Bad param" << v;
return;
}
// From here your old code that does things
}
Wednesday, January 28, 2015
Disabling downloadable fonts
We have a nice new style for planet.kde.org. I think it is generally an improvement over what we had, but sadly it decides to force the oxygen font over my browser selected font.
If you're like me and can stand the oxygen font being forced over the font you chose on your configuration have a look at this article to see how to disable downloadable fonts.
Update: Unfortunately if you do that you'll lose the K-logo on the left because instead of an icon we're using a font to render it. So now I have to decide between unreadable (for me) oxygen font a having the broken K-logo on the top.
If you're like me and can stand the oxygen font being forced over the font you chose on your configuration have a look at this article to see how to disable downloadable fonts.
Update: Unfortunately if you do that you'll lose the K-logo on the left because instead of an icon we're using a font to render it. So now I have to decide between unreadable (for me) oxygen font a having the broken K-logo on the top.
Sunday, January 25, 2015
Help test KDE Bomber game
As Laurent mentioned we are moving some KDE games from kdelibs4-based to kf5-based for the next KDE Applications 15.04 relase.
Today we just switched libkdegames, libkmahjongg and bovo. Next target is bomber, so if you have some time grab the master branch of libkdegames and the frameworks one of bomber, give it a try and make sure we're not regressing somewhere we didn't realize.
Today we just switched libkdegames, libkmahjongg and bovo. Next target is bomber, so if you have some time grab the master branch of libkdegames and the frameworks one of bomber, give it a try and make sure we're not regressing somewhere we didn't realize.
Thursday, January 22, 2015
GSoC student digikam sprint experience
Very refreshing to read about one of our GSoC students experience traveling for the first time to Europe for a KDE Sprint :)
And thanks to Tobias and The Qt Company for hosting the sprint in their Berlin offices :)
And thanks to Tobias and The Qt Company for hosting the sprint in their Berlin offices :)
Saturday, January 17, 2015
KDE End of Year 2014 Fundraiser is over
Yesterday was the last day of the KDE End of Year 2014 Fundraiser.
I want to thank publicly the 788 donors that helped us raise over 22000 euro.
You all rock and rule!
Thanks to this money we'll be able to keep sponsoring developers to attend conferences and sprints to improve the software we all love and use.
Of course there's never enough money so we still greatly appreciate your donations at http://kde.org/donate or even better you can become a KDE Supporting Member.
I want to thank publicly the 788 donors that helped us raise over 22000 euro.
You all rock and rule!
Thanks to this money we'll be able to keep sponsoring developers to attend conferences and sprints to improve the software we all love and use.
Of course there's never enough money so we still greatly appreciate your donations at http://kde.org/donate or even better you can become a KDE Supporting Member.
Etiquetes de comentaris:
donate,
donations,
fundraising,
kde,
supporting member
Wednesday, January 14, 2015
KDE Applications 15.04 Release Schedule
The schedule for KDE Applications 15.04 release is ready. As always it's available in techbase at https://techbase.kde.org/Schedules/Applications/15.04_Release_Schedule.
The Freeze is only six weeks away!
The Freeze is only six weeks away!
Saturday, December 20, 2014
New full changelogs for KDE Applications releases
With 14.12.0 we've introduced full changelogs for KDE Applications releases; you can see it at https://www.kde.org/announcements/fulllog_applications-14.12.0.php.
To generate this changelog we diff from previous release to the released one and use the commit message with a few annotations for stuff like REVIEW: BUG: etc.
This means the world is now going to see your commits more so spend 3 seconds when writing them instead of 0.5 ;)
If someone wants to improve the page (I'd like to have a checkbox that shows only commits that fix bugs) please contact me :)
The code lives in the release-tools repo (this is probably my longest python script, so be gentle ;))
To generate this changelog we diff from previous release to the released one and use the commit message with a few annotations for stuff like REVIEW: BUG: etc.
This means the world is now going to see your commits more so spend 3 seconds when writing them instead of 0.5 ;)
If someone wants to improve the page (I'd like to have a checkbox that shows only commits that fix bugs) please contact me :)
The code lives in the release-tools repo (this is probably my longest python script, so be gentle ;))
Wednesday, December 03, 2014
KDE End of Year Fundraising cards are being sent out!
We ordered some samples to make sure they looked good, and here they are here!
If you want some, we will send them to you as gift if you donate to the KDE End of Year 2014 Fundraising
P.S: If you made a donation that qualifies for a postcard gift before this monday and have not received an email from me asking which design and to which address you want the postcards sent please contact me at aacid@kde.org
If you want some, we will send them to you as gift if you donate to the KDE End of Year 2014 Fundraising
P.S: If you made a donation that qualifies for a postcard gift before this monday and have not received an email from me asking which design and to which address you want the postcards sent please contact me at aacid@kde.org
Etiquetes de comentaris:
fundraising,
kde,
postcards
Friday, November 14, 2014
Keywords vs X-KDE-Keywords on .desktop files
Seem similar, do they? But they have a *radical* difference, one is "old" (X-KDE-Keywords) and the other is "new" (Keywords). The "new" one is also an xdg standard and as such the separator is ';'. The old one is just a KConfig string list and thus the separator is ','.
Great isn't it?
TL;DR
X-KDE-Keywords uses , for separation
Keywords uses ; for separation
Great isn't it?
TL;DR
X-KDE-Keywords uses , for separation
Keywords uses ; for separation
Wednesday, November 12, 2014
Third design added for the KDE End of Year 2014 Fundraising Campaign!
I hope you know we're running a Fundraiser Campaign in KDE land. As a way to say thank you donors over 30€ get a postcard.
Today we've announced the last of the three designs you can choose as a gift when donating.
Donate and get a physical copy of it ;)
Today we've announced the last of the three designs you can choose as a gift when donating.
Donate and get a physical copy of it ;)
Friday, November 07, 2014
KDE Gardening Love Project: KRecipes
KRecipes has been in 2.0beta since 2010 so we decided it will be our next Love Project.
Objectives:
* We want to release 2.0 "quickly" and then 2.1 in one/two months.
* Migrate https://lists.sourceforge.net/lists/listinfo/krecipes-devel over to kde.org
* Migrate http://krecipes.sourceforge.net/ contents over to https://userbase.kde.org/KRecipes
* Add krecipes group to reviewboard that mails the KDE mailing list
* Add krecipes to jenkins that mails the kde.org mailing list
* Make sure bugs/reviewboards are defaulted to kde.org and go thorugh
* Port some of the Qt3Support code (make sure don't break stuff) :D
We will be updating this list at https://community.kde.org/Gardening/KRecipes
If you want to join the initiative please join the KDE Gardening mailing list and announce yourself :)
Objectives:
* We want to release 2.0 "quickly" and then 2.1 in one/two months.
* Migrate https://lists.sourceforge.net/lists/listinfo/krecipes-devel over to kde.org
* Migrate http://krecipes.sourceforge.net/ contents over to https://userbase.kde.org/KRecipes
* Add krecipes group to reviewboard that mails the KDE mailing list
* Add krecipes to jenkins that mails the kde.org mailing list
* Make sure bugs/reviewboards are defaulted to kde.org and go thorugh
* Port some of the Qt3Support code (make sure don't break stuff) :D
We will be updating this list at https://community.kde.org/Gardening/KRecipes
If you want to join the initiative please join the KDE Gardening mailing list and announce yourself :)
Tuesday, November 04, 2014
K3b 2.0.3 released
K3b 2.0.3 can be downloaded from http://download.kde.org/stable/k3b/k3b-2.0.3a.tar.xz
I don't have access to k3b.org so can't update the news there, shows why the Manifesto is such an important thing.
Changelog since 2.0.2:
* Fixed crash in MetaItemModel on submodel item removal
* Fixed Solid predicates for AudioCd and VideoDvd media. BUG: 265819
* Set error status when CDDB query fails.
* Prefer growisofs to wodim for DVD/BluRay burning.
* Fixed improper track number in CDDB track edit window title. BUG: 276681
* Fixed crash on detecting writing speeds. BUG: 272427
* Fix problem with HL-DT-ST BH10LS30. BUG: 268307
* Fixed compilation with new FFMPEG. BUG: 274817 BUG: 300731
* Allow using CD-R90 and CD-R99 media to full capacity. BUG: 276002
* Refactor the FreeBSD SCSI/CAM interface.
* Fix crash on dvd ripping
* fix sox detection with sox >= 14.4.0. BUG: 301544
* Support more media types. BUG: 261652
* Fix file system detection. BUG: 325616 BUG: 262607
* Surround output filename for transcode with double quotes. BUG: 326097
* Fix FILE name and type detection for cue sheet images. BUG: 337201
* Rip audio tracks in ascending numerical order. BUG: 319678
* Upstream patches from NetBSD.
* Make paranoia lib detection better.
* Don't preview if called process failed. BUG: 268680
* Fix Crash while remove songs in "Mixed mode CD proyect". BUG: 323117
* Use QElapsedTimer to calculate remaining time. BUG: 330239 BUG:315463
* Fix crash in lsof wrapper. BUGS: 340515
This marks the end of the "Gardening Love Project", I'll still be subscribed
to the k3b list but won't do any more than some lurking
I think someone should stand up and start thinking for a 2.1 release.
I don't have access to k3b.org so can't update the news there, shows why the Manifesto is such an important thing.
Changelog since 2.0.2:
* Fixed crash in MetaItemModel on submodel item removal
* Fixed Solid predicates for AudioCd and VideoDvd media. BUG: 265819
* Set error status when CDDB query fails.
* Prefer growisofs to wodim for DVD/BluRay burning.
* Fixed improper track number in CDDB track edit window title. BUG: 276681
* Fixed crash on detecting writing speeds. BUG: 272427
* Fix problem with HL-DT-ST BH10LS30. BUG: 268307
* Fixed compilation with new FFMPEG. BUG: 274817 BUG: 300731
* Allow using CD-R90 and CD-R99 media to full capacity. BUG: 276002
* Refactor the FreeBSD SCSI/CAM interface.
* Fix crash on dvd ripping
* fix sox detection with sox >= 14.4.0. BUG: 301544
* Support more media types. BUG: 261652
* Fix file system detection. BUG: 325616 BUG: 262607
* Surround output filename for transcode with double quotes. BUG: 326097
* Fix FILE name and type detection for cue sheet images. BUG: 337201
* Rip audio tracks in ascending numerical order. BUG: 319678
* Upstream patches from NetBSD.
* Make paranoia lib detection better.
* Don't preview if called process failed. BUG: 268680
* Fix Crash while remove songs in "Mixed mode CD proyect". BUG: 323117
* Use QElapsedTimer to calculate remaining time. BUG: 330239 BUG:315463
* Fix crash in lsof wrapper. BUGS: 340515
This marks the end of the "Gardening Love Project", I'll still be subscribed
to the k3b list but won't do any more than some lurking
I think someone should stand up and start thinking for a 2.1 release.
Monday, November 03, 2014
New postcard design added for the KDE End of Year 2014 Fundraising Campaign!
You probably know we're running a Fundraiser Campaign in KDE land. As a way to say thank you donors over 30€ get a postcard.
Today we've announced the second of three designs we are planning.
Donate and get a physical copy of it ;)
Today we've announced the second of three designs we are planning.
Donate and get a physical copy of it ;)
Thursday, October 16, 2014
KDE Gardening Team: K3b
As mentioned on other KDE Gardening Team bugs we are focusing on getting K3b 2.0.3 release out.
The release will be on 4th November if all goes to plan.
Also we are going through the bugs doing two things:
You can visit https://community.kde.org/Gardening/K3b for the relevant bugzilla links.
[1] This should be a mostly empty list since we already have 2.0.2 out and doesn't make sense to delay 2.0.3 until a bug is fixed given 2.0.3 will be already better than 2.0.2
The release will be on 4th November if all goes to plan.
Also we are going through the bugs doing two things:
- Checking if it still happens and asking people to give more info if needed
- Classifying it regarding it's gardening potential
You can visit https://community.kde.org/Gardening/K3b for the relevant bugzilla links.
[1] This should be a mostly empty list since we already have 2.0.2 out and doesn't make sense to delay 2.0.3 until a bug is fixed given 2.0.3 will be already better than 2.0.2
Make the World a Better Place! - KDE End of Year 2014 Fundraising

At KDE sometimes we focus in the technical parts of Free Software. This is understandable since most of us are technical people doing a technical job.
But KDE also has a huge social impact, thanks to KDE there's schools that can teach touch typing , there's people out there that can do their accounting, there's business that can fill their taxes. KDE does provide quality software for all the world to use, making it a better place for all of us.
Donating to KDE is not for you, it is for the entire world.
As a way to say thank you, starting with € 30 KDE e.V. will send a KDE themed postcard to any given address. You will get an extra card for every additional € 10 donation.
More at https://www.kde.org/fundraisers/yearend2014/
Saturday, September 27, 2014
Plasma 5.1 release parties!
Plasma 5.1 is coming up in less than a month, we have already two release parties in the planning, but i'm sure you have some fellow KDE users around you want to meet and have a beer with, so hop onto your local LUG, meetup, or something, organize a party and add it to https://community.kde.org/Promo/Events/Release_Parties/Plasma5.1
Etiquetes de comentaris:
plasma,
release party
Thursday, September 25, 2014
The KDE Gardening Team
At Akademy I did a short talk (8 min) + herded a BoF with a title called "Quality is in the eye of the beholder".
One of the topics was that we should try to get a team of people to care about the global state of KDE software, we've decided to call this "The Gardening Team".
The mandate of the team is to:
# Find *really* important bugs and ping people to fix them
# Find stale reviewboards and ping people to fix them
# Bugzilla gardening, close old products etc
# Find projects that need love and give them some
For that we have various ideas:
Try to find monthly a bug to get people to fix it, by highlighting it as "The Bug of The Month" or something. Of course this bug can't be stuff like "Make Okular support javascript", it has to be something that is really a pain point of the whole user base and we think we can find people to fix it, it makes no sense setting impossible goals ;)
Do routine passes over reviewboard trying to identify stale requests and finding people to help moving those.
Run something called "Love Project". The idea is to pick up a project that is somewhat stale, and for a short amount of time (let's say 2/3 months) try to get a new release out, fix the most important crashers/bugs, get the review boards released, etc. This goal of the team is *not* becoming the maintainers of the project, but maybe by virtue of the "Love Project" we can attract new contributors that decide to.
Since we're only a few maybe we can't do this all, so we're focusing on a particular "Love Project" by now, but you should join and help us do more!
Our current Love Project is K3b, that had 2.0.2 released a long time ago and has a 2.0 branch with a few more bugfixes that have been never released.
We are coordinating through https://todo.kde.org/?controller=board&action=show&project_id=26 at the moment but plan to get a mailing list soon (or invade an unused existing one).
If you're interested, comment and i'll give you a shout when the list is created, no mega skills are needed (though people with mega skills are also welcome ;))
One of the topics was that we should try to get a team of people to care about the global state of KDE software, we've decided to call this "The Gardening Team".
The mandate of the team is to:
# Find *really* important bugs and ping people to fix them
# Find stale reviewboards and ping people to fix them
# Bugzilla gardening, close old products etc
# Find projects that need love and give them some
For that we have various ideas:
Try to find monthly a bug to get people to fix it, by highlighting it as "The Bug of The Month" or something. Of course this bug can't be stuff like "Make Okular support javascript", it has to be something that is really a pain point of the whole user base and we think we can find people to fix it, it makes no sense setting impossible goals ;)
Do routine passes over reviewboard trying to identify stale requests and finding people to help moving those.
Run something called "Love Project". The idea is to pick up a project that is somewhat stale, and for a short amount of time (let's say 2/3 months) try to get a new release out, fix the most important crashers/bugs, get the review boards released, etc. This goal of the team is *not* becoming the maintainers of the project, but maybe by virtue of the "Love Project" we can attract new contributors that decide to.
Since we're only a few maybe we can't do this all, so we're focusing on a particular "Love Project" by now, but you should join and help us do more!
Our current Love Project is K3b, that had 2.0.2 released a long time ago and has a 2.0 branch with a few more bugfixes that have been never released.
We are coordinating through https://todo.kde.org/?controller=board&action=show&project_id=26 at the moment but plan to get a mailing list soon (or invade an unused existing one).
If you're interested, comment and i'll give you a shout when the list is created, no mega skills are needed (though people with mega skills are also welcome ;))
Wednesday, September 24, 2014
KDE Applications 14.12 Release Schedule
The schedule for KDE Applications 14.12 release is ready. As always it's available in techbase at https://techbase.kde.org/Schedules/Applications/14.12_Release_Schedule.
The Freeze is only one month away!
The Freeze is only one month away!
Sunday, September 07, 2014
Okular wants to "Save"
TLDR - Short version:
We are reworking part of the "Save As" code, and we are adding the long-requested "Save" button! The old "internal implicit save" behavior is being dropped and we need your input about what to do with data saved internally by previous Okular versions.
Please visit https://forum.kde.org/viewtopic.php?f=251&t=122750 and share your opinion on the poll/comments.
We are reworking part of the "Save As" code, and we are adding the long-requested "Save" button! The old "internal implicit save" behavior is being dropped and we need your input about what to do with data saved internally by previous Okular versions.
Please visit https://forum.kde.org/viewtopic.php?f=251&t=122750 and share your opinion on the poll/comments.
Saturday, August 23, 2014
KDE Community plans for Releases in the Future
Long post about releases ahead, brace yourselves!
Last week we released KDE Applications and KDE Platform 4.14.
KDE Applications, KDE Platform and KDE Workspaces were sometimes collectively referred as the "KDE Software Compilation" or "KDE SC" in short form, which is arguably a bad name, but it is what it is.
The "Software Compilation" started dying a while ago and 4.14 marks its end.
KDE Platform was 'virtually frozen' a long time ago, but we kept increasing the version number for some reasons that are now not important, so KDE Platform 4.14.x will be the last version, of course we will go to very high 'x' if there is bugfixes to be done.
KDE Frameworks 5 is the successor of KDE Platform based on Qt5, it's already on 5.1 and the team plans to release a new 5.x version with both features and bugfixes every month.
KDE Workspaces was frozen at 4.11.x, in fact if you check your distro, you are probably using 4.11.somehighnumber, the plan is to keep doing releases for at least a year if there are bugfixes available.
Plasma 5 is the successor of KDE Workspaces based on KF5, it's currently at 5.0.1. The team plans releasing a stable 5.x.y version every month with bugfixes and a 5.x+1 feature release every three months.
That leaves us with the third component of the old releases, "KDE Applications", comprised of more than 100 applications. We want those to move to Qt5 and KF5 since it's simply a better world, but we're not going to do it all at once as we did in 4.0. We will give the maintainers the choice to move as they feel the quality of their KF5 port is good enough.
KDE Applications has been having feature releases every four months, with bugfix releases in the three months in between.
We don't plan changing that, but to highlight that applications can be used independently of the libraries used to build the desktop you are using, we're just going to use a time approach for version numbers, that is, next release will be "KDE Applications 14.12"
And that marks the end of the SC era since libraries, desktop and applications are now in a separate release schedule.
Also, if you are at akademy we're having a short session Sunday at 10:40, and I guess i'll schedule a BoF later in the week.
Last week we released KDE Applications and KDE Platform 4.14.
KDE Applications, KDE Platform and KDE Workspaces were sometimes collectively referred as the "KDE Software Compilation" or "KDE SC" in short form, which is arguably a bad name, but it is what it is.
The "Software Compilation" started dying a while ago and 4.14 marks its end.
KDE Platform was 'virtually frozen' a long time ago, but we kept increasing the version number for some reasons that are now not important, so KDE Platform 4.14.x will be the last version, of course we will go to very high 'x' if there is bugfixes to be done.
KDE Frameworks 5 is the successor of KDE Platform based on Qt5, it's already on 5.1 and the team plans to release a new 5.x version with both features and bugfixes every month.
KDE Workspaces was frozen at 4.11.x, in fact if you check your distro, you are probably using 4.11.somehighnumber, the plan is to keep doing releases for at least a year if there are bugfixes available.
Plasma 5 is the successor of KDE Workspaces based on KF5, it's currently at 5.0.1. The team plans releasing a stable 5.x.y version every month with bugfixes and a 5.x+1 feature release every three months.
That leaves us with the third component of the old releases, "KDE Applications", comprised of more than 100 applications. We want those to move to Qt5 and KF5 since it's simply a better world, but we're not going to do it all at once as we did in 4.0. We will give the maintainers the choice to move as they feel the quality of their KF5 port is good enough.
KDE Applications has been having feature releases every four months, with bugfix releases in the three months in between.
We don't plan changing that, but to highlight that applications can be used independently of the libraries used to build the desktop you are using, we're just going to use a time approach for version numbers, that is, next release will be "KDE Applications 14.12"
And that marks the end of the SC era since libraries, desktop and applications are now in a separate release schedule.
Also, if you are at akademy we're having a short session Sunday at 10:40, and I guess i'll schedule a BoF later in the week.
Etiquetes de comentaris:
kde,
kde applications,
kde frameworks,
kde sc,
kf5,
plasma
Saturday, August 16, 2014
Akademy 2014 needs *you*
Akademy 2014 is just 3 weeks away.
If you haven't registered, you should register now, but since probably you are registered already, the next step is thinking if you want to be a volunteer.
Every big event needs volunteers: infodesk people, session chairs, video operators, etc.
If you want to make Akademy 2014 a success please go over to https://community.kde.org/Akademy/2014/Volunteers and sign yourself up!
If you haven't registered, you should register now, but since probably you are registered already, the next step is thinking if you want to be a volunteer.
Every big event needs volunteers: infodesk people, session chairs, video operators, etc.
If you want to make Akademy 2014 a success please go over to https://community.kde.org/Akademy/2014/Volunteers and sign yourself up!
Thursday, August 14, 2014
KDE Randa Meetings 2014 - The End
Everything, good or bad, reaches to an end. So will do the KDE Randa Meetings 2014 in a few hours.
I can't say all the great stuff that has happened here the last few days, but i'll try to summarize:
* The book is looking great and something that would help us grow
* api.kde.org got some love and more to come in the future.
* Planning on making life easier for newbies trying to compile and contribute patches
* KF5 ports of lots of programs in progress
* Lots of planning on automating tasks
* GCompris being more KDE
* Bugfixing everywhere
* Awesome people all around
Thanks to everyone that donated in the Randa 2014 fund-raiser.
Thanks Mario for such a beautiful event.
And of course, do not forget about the next big KDE event you should to attend: AKADEMY 2014 in 3 weeks!
I can't say all the great stuff that has happened here the last few days, but i'll try to summarize:
* The book is looking great and something that would help us grow
* api.kde.org got some love and more to come in the future.
* Planning on making life easier for newbies trying to compile and contribute patches
* KF5 ports of lots of programs in progress
* Lots of planning on automating tasks
* GCompris being more KDE
* Bugfixing everywhere
* Awesome people all around
Thanks to everyone that donated in the Randa 2014 fund-raiser.
Thanks Mario for such a beautiful event.
And of course, do not forget about the next big KDE event you should to attend: AKADEMY 2014 in 3 weeks!
Tuesday, August 12, 2014
KDE Randa Meetings 2014 Day 4
Time flies when you're in good company, i planned to blog every day and now i realize we're on day 4 already.
Well, here comes some of the things i've been doing
* Participated in a few discussions about "the KDE SDK" Aleix seems very promising to recruit new developers :) Let's see if I can convince Aleix to blog about it
* KGeography port to KF5 started by David Gil is now complete.
* Started and finished Blinken port to KF5
* Made some patches for some frameworks while porting KGeography
Some of the cool things I've seen:
* kdenlive cleaning up their code to ease maintaince
* GCompris, a nice educational tool for children
* The KF5 Book is shaping up nicely
* Lots of KF5 porting and refining everywhere
Let's keep rolling!
Well, here comes some of the things i've been doing
* Participated in a few discussions about "the KDE SDK" Aleix seems very promising to recruit new developers :) Let's see if I can convince Aleix to blog about it
* KGeography port to KF5 started by David Gil is now complete.
* Started and finished Blinken port to KF5
* Made some patches for some frameworks while porting KGeography
Some of the cool things I've seen:
* kdenlive cleaning up their code to ease maintaince
* GCompris, a nice educational tool for children
* The KF5 Book is shaping up nicely
* Lots of KF5 porting and refining everywhere
Let's keep rolling!
Saturday, August 09, 2014
KDE Randa Meetings 2014 Day 1
I wasn't planning on attending KDE Randa Meetings 2014 but last Wednesday I decided to, so bought some not so cheap plane and train tickets (don't worry, I payed from my own pocket) and here I am surrounded by awesome KDE hackers in the middle of the Swiss Alps.
I want to thank the more than 400 people that helped us fund KDE Randa Meetings 2014, you are awesome and directly responsible of improvements that are to come to millions of users in the world.
And remember we still need money to fund more sprints and stuff, so head over to our donations page and help us improve the world!
I want to thank the more than 400 people that helped us fund KDE Randa Meetings 2014, you are awesome and directly responsible of improvements that are to come to millions of users in the world.
And remember we still need money to fund more sprints and stuff, so head over to our donations page and help us improve the world!
Etiquetes de comentaris:
donations,
fundraising,
kde,
randa
Friday, August 08, 2014
Help the KDE promo team do their work
We KDE developers have been working on the KDE Applications 4.14 release for the past four months, we've implemented features and important bugfixes. Now the release is near, and we have to write release notes so that our users get the message.
The thing about writing release notes is that you can't write about stuff you don't know, and KDE Applications is biiiiiiiiig so it's impossible for a small group of promo people to know all that happened to it in the last 4 months.
This means *you* developers have to help the promo team write the promo highlighting the most important changes you did to your app and writing them at https://notes.kde.org/p/release_4.14_kde-devel_notes so they can write a more distilled and promo-like text.
Please help them help you.
The thing about writing release notes is that you can't write about stuff you don't know, and KDE Applications is biiiiiiiiig so it's impossible for a small group of promo people to know all that happened to it in the last 4 months.
This means *you* developers have to help the promo team write the promo highlighting the most important changes you did to your app and writing them at https://notes.kde.org/p/release_4.14_kde-devel_notes so they can write a more distilled and promo-like text.
Please help them help you.
Tuesday, July 29, 2014
Logging in into Picasa 3.9 under Linux
A few years ago I showed my father Picasa under Linux, he liked it and started to use it to upload his photos, and has been using it for almost 6 years, even Google discontinued Picasa for Linux at version 3.0 (Picasa is at 3.9 now).
Unfortunately a few weeks ago seems Google decided to kill support for old APIs in the server side and Picasa 3.0 for Linux was giving back an error when trying to upload an image ("Could not find POST url" or similar). I suggested to wait to see if they would come back, but it seems they haven't and so i've had to fix it for him.
Since he's heavily invested in Picasa I've had to install Picasa for windows under wine to make it work. It has not been trivial to get to work so I'll share it here for others that committed the error of trusting privative software and services.
The story is this: Installing picasa 3.9 for windows under wine is pretty easy (next, next, next). The problem is once you are running it, being able to log in. First problem is that the webview using for login doesn't even show. Most of the interwebs suggest installing ie8 using winetricks to solve that and it indeed solves the problem of the webview not showing, but still i can't log in (interestingly the webview will tell you if you wrote the password wrong).
At this point i was stuck for a few hours, even found some dude that claimed he had installed Google Chrome Frame for Internet Explorer and that had fixed for him. But not for me.
After a few hours, I stopped trusting the internet and started to think. I have a windows installation laying around, and i can log in from there, and once logged in Picasa does not ask for the password again, so it must be storing something no?
So I made a copy of the Program Files folder and compared it after loggin in, folders where exactly the same. So it was not stored there, which makes sense since log in is per user not per machine. Next i tried in that weird Personal Folder (Windows $HOME) but could not find any change either. Last chance was the registry, i used http://www.nirsoft.net/utils/reg_file_from_application.html and saw that when logging in, Picasa writes a few entries in HKEY_CURRENT_USER\Software\Google\Picasa\Picasa2\Preferences namely GoogleOAuth, GoogleOAuthEmail, GoogleOAuthServices and GoogleOAuthVersion, so I copied these over to the wine installation (with "wine regedit") and now my father can run Picasa just fine again.
Lessons learned:
* Non Free Software will eventually come back and hit you, if possible don't use it for stuff that is critical to you
* Think about your problem, sometimes is easier than just googling random instructions from the internet.
Unfortunately a few weeks ago seems Google decided to kill support for old APIs in the server side and Picasa 3.0 for Linux was giving back an error when trying to upload an image ("Could not find POST url" or similar). I suggested to wait to see if they would come back, but it seems they haven't and so i've had to fix it for him.
Since he's heavily invested in Picasa I've had to install Picasa for windows under wine to make it work. It has not been trivial to get to work so I'll share it here for others that committed the error of trusting privative software and services.
The story is this: Installing picasa 3.9 for windows under wine is pretty easy (next, next, next). The problem is once you are running it, being able to log in. First problem is that the webview using for login doesn't even show. Most of the interwebs suggest installing ie8 using winetricks to solve that and it indeed solves the problem of the webview not showing, but still i can't log in (interestingly the webview will tell you if you wrote the password wrong).
At this point i was stuck for a few hours, even found some dude that claimed he had installed Google Chrome Frame for Internet Explorer and that had fixed for him. But not for me.
After a few hours, I stopped trusting the internet and started to think. I have a windows installation laying around, and i can log in from there, and once logged in Picasa does not ask for the password again, so it must be storing something no?
So I made a copy of the Program Files folder and compared it after loggin in, folders where exactly the same. So it was not stored there, which makes sense since log in is per user not per machine. Next i tried in that weird Personal Folder (Windows $HOME) but could not find any change either. Last chance was the registry, i used http://www.nirsoft.net/utils/reg_file_from_application.html and saw that when logging in, Picasa writes a few entries in HKEY_CURRENT_USER\Software\Google\Picasa\Picasa2\Preferences namely GoogleOAuth, GoogleOAuthEmail, GoogleOAuthServices and GoogleOAuthVersion, so I copied these over to the wine installation (with "wine regedit") and now my father can run Picasa just fine again.
Lessons learned:
* Non Free Software will eventually come back and hit you, if possible don't use it for stuff that is critical to you
* Think about your problem, sometimes is easier than just googling random instructions from the internet.
Etiquetes de comentaris:
free software,
picasa
Sunday, July 20, 2014
My way to develop with git in KDE repos
From time to time there is the discussion of which workflow is better to develop with git, etc.
I'm not going to try to convince anyone on which workflow to use, i'm just going to explain what i do and explain why i think it's useful (and even more in the multi-developer KDE environment).
Let's picture the scenario we had a few days ago where there were lots of projects with three "live" branches, i.e. KDE/4.13, KDE/4.14 and master.
What is my way to develop?
* Bugfixes go to oldest "live" stable branch
* Features go to oldest "live" non frozen branch
* Branches are merged up
So let's say that I develop a new feature to support a whole new document format to Okular. Since that is a new feature it would go to the "oldest live non frozen branch", that in this case was master since KDE/4.13 and KDE/4.14 where already feature frozen. So I commit it to master and then "Branches are merged up" which in this case means nothing since there's no branch "up" from master.
Now let's say there's a crash bug when opening a file with three monitors. Since that is a bugfix, it'd go to the "oldest live stable branch", that in this case would be KDE/4.13. And then "Branches are merged up", so i would mean 4.13 into 4.14 and after that 4.14 into master. Ensuring that 4.14 and master also have the bugfix.
I think that this is a very useful way of developing using git branches for a lot of reasons, but the biggest of them is that for a random person it is easy to know if a "branch high in the hiearchy" has all the bugfixes or not, he just have to go to KDE/4.14 and to "git merge origin/KDE/4.13", if no change is brought over, it means that for sure all the bugfixes and code that was in the 4.13 release will be in the 4.14 release, otherwise it is hard to know.
So now that 4.13 is not going to be released anymore and 4.14 is a very young fork of master, i suggest that for every push you do to KDE/4.14 you go to the master branch and merge origin/KDE/4.14. This way you will have a master that is always fully merged with 4.14 and a third party person looking at your code (like the release manager) won't have to worry if it contains all the code or not.
Happy hacking!
And of course if you disagree with me, that's fine, not that i'm happy if my reasons did not convince you :)
I'm not going to try to convince anyone on which workflow to use, i'm just going to explain what i do and explain why i think it's useful (and even more in the multi-developer KDE environment).
Let's picture the scenario we had a few days ago where there were lots of projects with three "live" branches, i.e. KDE/4.13, KDE/4.14 and master.
What is my way to develop?
* Bugfixes go to oldest "live" stable branch
* Features go to oldest "live" non frozen branch
* Branches are merged up
So let's say that I develop a new feature to support a whole new document format to Okular. Since that is a new feature it would go to the "oldest live non frozen branch", that in this case was master since KDE/4.13 and KDE/4.14 where already feature frozen. So I commit it to master and then "Branches are merged up" which in this case means nothing since there's no branch "up" from master.
Now let's say there's a crash bug when opening a file with three monitors. Since that is a bugfix, it'd go to the "oldest live stable branch", that in this case would be KDE/4.13. And then "Branches are merged up", so i would mean 4.13 into 4.14 and after that 4.14 into master. Ensuring that 4.14 and master also have the bugfix.
I think that this is a very useful way of developing using git branches for a lot of reasons, but the biggest of them is that for a random person it is easy to know if a "branch high in the hiearchy" has all the bugfixes or not, he just have to go to KDE/4.14 and to "git merge origin/KDE/4.13", if no change is brought over, it means that for sure all the bugfixes and code that was in the 4.13 release will be in the 4.14 release, otherwise it is hard to know.
So now that 4.13 is not going to be released anymore and 4.14 is a very young fork of master, i suggest that for every push you do to KDE/4.14 you go to the master branch and merge origin/KDE/4.14. This way you will have a master that is always fully merged with 4.14 and a third party person looking at your code (like the release manager) won't have to worry if it contains all the code or not.
Happy hacking!
And of course if you disagree with me, that's fine, not that i'm happy if my reasons did not convince you :)
Wednesday, July 09, 2014
KDE/4.14 branch forked
KDE/4.14 branch forked, master is now open. Next applications release will be a kdelibs4 and KF5 mix!
http://mail.kde.org/pipermail/kde-cvs-announce/2014/000147.html
http://mail.kde.org/pipermail/kde-cvs-announce/2014/000147.html
Tuesday, May 20, 2014
KDE is a nice community, but we can do better!
Since a long time KDE.org has been referring to KDE as a team of people, a community, and not the software products we make.
I agree with this but sadly sometimes we struggle in being a nice community to live in.
There's a few things I think we can improve:
This doesn't happen all the time, but it happens more than I would like, so I'm just raising it up so that people think about it and try to improve :)
Of course I'm not saying I'm not guilty of the things I mentioned, but as the wise-man said: "Don't do what i do, do what i say"
I agree with this but sadly sometimes we struggle in being a nice community to live in.
There's a few things I think we can improve:
- Being better 'winners': We are a big community, at some point we have to take community-wide decisions, and it's impossible we will all agree on something. If you are part of the 'winning' group, be gentle with the people that 'lost', sure you think you are right, but they think the same and think the rest is doing a terrible mistake, so when you talk with them be polite and point out that the majority is going in the other direction, but that you still appreciate all the other stuff they do, etc. They already 'lost' so there's no need to put their head under your foot and do an evil laugh.
- Being better 'losers': We are a big community, at some point we have to take community-wide decisions, and it's impossible we will all agree on something. If you are part of the 'losing' group, be accepting that you 'lost' and try to carry on with the amazing work you do in other areas. Sure you are allowed to some venting, but it should be all within the limits of not trying to drag the discussion forever and not trying to destroy the project just because you disagree in one decision, so yes, you're allowed to some small complaining but understand that the majority decided different than what you think it's better, accept it and carry on, you'll be happier :)
- Assuming good by default: If a sentence can be read in two ways, do not assume it was said in the worse way, assume it was said in the good. Will help keeping the discussion sane and constructive.
- Not workarounding by default: If you find a bug or shortcoming in kdelibs, KF5, Qt or any other library, don't workaround it by default, please report it to the library people and try to work with them to fix it. Library code is not that hard and if you fix it in the source, everyone will benefit from the fix, not just the users of your software because you workarounded it and kept quiet about it to upper layers.
- Not caring enough for the global: We produce zillions of different projects of software. It's almost impossible to have a global overview of "what the bad bugs are", so if you know there is a bug that is bad, and it's affecting quite a bit of people, don't say "someone else will fix it" and ignore it, share it with the wider community and if the current maintainers are missing or overworked I'm pretty sure we can find someone to have a look and fix that bug that is making people sad.
This doesn't happen all the time, but it happens more than I would like, so I'm just raising it up so that people think about it and try to improve :)
Of course I'm not saying I'm not guilty of the things I mentioned, but as the wise-man said: "Don't do what i do, do what i say"
Wednesday, May 14, 2014
Web developer: Help KDE with a few hours of work
At KDE we're trying to get people to donate more (I hope I don't have to explain to this audience why), one of the ideas floating around is adding a small "impulse donate" button to kde.org similar to the one at http://www.videolan.org/ (only with euros and without a "why?" link for now)
I'm not a web devel by far (though have done my fair share of copy&pasting php, html and css for KDE and other personal projects) but I understand it should not be "that hard"™, it would be basically doing some modifications of the kde.org sources, the capacity framework and doing some reuse of the existing paypal donation page code.
Anyone up for the work? If so, please contact me!
I'm not a web devel by far (though have done my fair share of copy&pasting php, html and css for KDE and other personal projects) but I understand it should not be "that hard"™, it would be basically doing some modifications of the kde.org sources, the capacity framework and doing some reuse of the existing paypal donation page code.
Anyone up for the work? If so, please contact me!
Tuesday, May 06, 2014
Commit your approved Review Requests!
By looking at KDE git Review Board I realize we have over 4 pages of "ship it"-ed review requests that are still marked as not commited.
This is nuts!
I know some of them are still work in progress (yes, it sucks that reviewboard does not let you "unship it" when you find something wrong or when some newbie mistakenly gives himself a +1) but I am pretty sure at least 3 of those 4 pages are stuff that was coded, reviewed, approved and then no one committed it :/
So please go through your reviewboard changes and commit them, or ping the maintainer of the app if you don't have commit rights (and if the maintainer is unresponsive for some reason and it's obvious you had his "Ship it" just come to me and I'll commit it for you).
This is nuts!
I know some of them are still work in progress (yes, it sucks that reviewboard does not let you "unship it" when you find something wrong or when some newbie mistakenly gives himself a +1) but I am pretty sure at least 3 of those 4 pages are stuff that was coded, reviewed, approved and then no one committed it :/
So please go through your reviewboard changes and commit them, or ping the maintainer of the app if you don't have commit rights (and if the maintainer is unresponsive for some reason and it's obvious you had his "Ship it" just come to me and I'll commit it for you).
Wednesday, April 16, 2014
KDE Applications 4.13 released
Today we've released 4.13 which is probably the best KDE Applications release ever :)
It also marks the second release we do with a four months schedule instead of a six month one. I think we've ended up with a pretty nice cadence in which we are faster delivering features and bugfixes to users, which at the end is what is important, since the earlier people get the features the earlier they'll find the bugs (let's accept it, all software has bugs) and the earlier the bugs are found the earlier they can be fixed. So basically it's faster progress :)
We have also made good our promise to keep our tests passing, as you can see everything from this release is green (kde-workspace is not green but is not part of the 4.13 release). So kudos to all developers for being awesome in that regard too.
Let's all celebrate on this release but not forget we need to keep working full steam ahead on the releases of KDE Frameworks 5, Plasma 2014.06 and KDE Applications 4.14.
Finally I'd like to remind you that most of the people doing KDE development are volunteers and they invest their time in making this awesome software for you to use for free.
Lots of them even spend time to travel abroad to meet each other in Sprints were they do concentrated hacking for a few days, so if you appreciate the work they do in those Sprints please donate some money so we can actually help them travel and we can make more Sprints happen :-) http://www.kde.org/community/donations/
As anecdote, I had the pleasure of meeting the guys from the KTP Sprint this Friday and after dinner they went back to hacking instead of joining some of us for some beers. That is dedication!
It also marks the second release we do with a four months schedule instead of a six month one. I think we've ended up with a pretty nice cadence in which we are faster delivering features and bugfixes to users, which at the end is what is important, since the earlier people get the features the earlier they'll find the bugs (let's accept it, all software has bugs) and the earlier the bugs are found the earlier they can be fixed. So basically it's faster progress :)
We have also made good our promise to keep our tests passing, as you can see everything from this release is green (kde-workspace is not green but is not part of the 4.13 release). So kudos to all developers for being awesome in that regard too.
Let's all celebrate on this release but not forget we need to keep working full steam ahead on the releases of KDE Frameworks 5, Plasma 2014.06 and KDE Applications 4.14.
Finally I'd like to remind you that most of the people doing KDE development are volunteers and they invest their time in making this awesome software for you to use for free.
Lots of them even spend time to travel abroad to meet each other in Sprints were they do concentrated hacking for a few days, so if you appreciate the work they do in those Sprints please donate some money so we can actually help them travel and we can make more Sprints happen :-) http://www.kde.org/community/donations/
As anecdote, I had the pleasure of meeting the guys from the KTP Sprint this Friday and after dinner they went back to hacking instead of joining some of us for some beers. That is dedication!
Tuesday, March 25, 2014
ASAN and libraries (2nd part)
In ASAN and libraries I claimed you didn't need to compile a library with -fsanitize=address to get ASAN to work over it. Well it turns out that is only true in some cases and in some others like the one in this example you actually need it. So here comes a different example and the differences of using -fsanitize=address and not in the library code.
shared.cpp
#include "shared.h"
Foo::Foo()
{
int a[1];
a[2] = 3;
}
shared.h
class Foo
{
public:
Foo();
};
main.cpp
#include "shared.h"
int main(int, char **)
{
Foo f;
return 0;
}
Let's see what happens if we do
Nothing, no error detected.
But if we change to
Boom! We get the error :-) So my conclusion that ASAN wasn't needed on libraries was bad. You need it. Thanks Zecke for pointing me to my wrongness :-)
shared.cpp
#include "shared.h"
Foo::Foo()
{
int a[1];
a[2] = 3;
}
shared.h
class Foo
{
public:
Foo();
};
main.cpp
#include "shared.h"
int main(int, char **)
{
Foo f;
return 0;
}
Let's see what happens if we do
export ASAN_SYMBOLIZER_PATH=/usr/bin/llvm-symbolizer-3.4 export ASAN_OPTIONS=symbolize=1 g++ -Wl,--no-undefined -shared -o libshared.so shared.cpp -g3 g++ -fno-omit-frame-pointer -fsanitize=address main.cpp -lshared -L . -g3 LD_LIBRARY_PATH=. ./a.outAs the suggested in the previous blog entry.
Nothing, no error detected.
But if we change to
export ASAN_SYMBOLIZER_PATH=/usr/bin/llvm-symbolizer-3.4
export ASAN_OPTIONS=symbolize=1
g++ -fno-omit-frame-pointer -fsanitize=address -Wl,--no-undefined \
-shared -o libshared.so shared.cpp -g3 -lasan -fPIC
g++ -fno-omit-frame-pointer -fsanitize=address main.cpp -lshared -L . -g3
LD_LIBRARY_PATH=. ./a.out
==13069== ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7fffe74fafa8
at pc 0x7fb0ef71f792 bp 0x7fffe74faf60 sp 0x7fffe74faf58
WRITE of size 4 at 0x7fffe74fafa8 thread T0
#0 0x7fb0ef71f791 in Foo::Foo() /home/tsdgeos/test/shared.cpp:6
#1 0x40074a in main /home/tsdgeos/test/main.cpp:5
#2 0x7fb0ef37aec4 (/lib/x86_64-linux-gnu/libc.so.6+0x21ec4)
#3 0x400638 in _start (/home/tsdgeos/test/a.out+0x400638)
Address 0x7fffe74fafa8 is located at offset 40 in frame <__base_ctor> of T0's stack:
Boom! We get the error :-) So my conclusion that ASAN wasn't needed on libraries was bad. You need it. Thanks Zecke for pointing me to my wrongness :-)
Saturday, March 22, 2014
ASAN and plugins
In ASAN and libraries Milian asked if the reasoning for libraries also applied for plugins. Since I had no idea, I had to try it.
Here comes the output
main.cpp
So it seems that "plugins are just libraries" applies here :)
Here comes the output
main.cpp
#include <QDebug>
#include <QLibrary>
int main(int, char **)
{
QLibrary l("libshared");
qDebug() << l.load();
return 0;
}
shared.cpp
#include "shared.h"
static Foo f;
Foo::Foo()
{
int *a = 0;
*a = 33;
}
shared.h
class Foo
{
public:
Foo();
};
export ASAN_SYMBOLIZER_PATH=/usr/bin/llvm-symbolizer-3.4
export ASAN_OPTIONS=symbolize=1
g++ -shared -o libshared.so shared.cpp -g3 -fPIC
g++ -fsanitize=address main.cpp -g3 -I /usr/include/qt4/QtCore/ \
-I /usr/include/qt4/ -lQtCore
And then we run it!
$ LD_LIBRARY_PATH=. ./a.out
ASAN:SIGSEGV
=================================================================
==7048== ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000
(pc 0x7f199c1326aa sp 0x7fff37e557c0 bp 0x7fff37e557c0 T0)
AddressSanitizer can not provide additional info.
#0 0x7f199c1326a9 in Foo::Foo() /home/tsdgeos/test/shared.cpp:8
#1 0x7f199c1326da in __static_initialization_and_destruction_0(int, int)
/home/tsdgeos/test/shared.cpp:3
#2 0x7f199c1326ef in _GLOBAL__sub_I_shared.cpp /home/tsdgeos/test/shared.cpp:9
#3 0x7f19a132b139 (/lib64/ld-linux-x86-64.so.2+0x10139)
#4 0x7f19a132b222 (/lib64/ld-linux-x86-64.so.2+0x10222)
#5 0x7f19a132fc6f (/lib64/ld-linux-x86-64.so.2+0x14c6f)
#6 0x7f19a132aff3 (/lib64/ld-linux-x86-64.so.2+0xfff3)
#7 0x7f19a132f3ba (/lib64/ld-linux-x86-64.so.2+0x143ba)
#8 0x7f199d1a602a (/lib/x86_64-linux-gnu/libdl.so.2+0x102a)
#9 0x7f19a132aff3 (/lib64/ld-linux-x86-64.so.2+0xfff3)
#10 0x7f199d1a662c (/lib/x86_64-linux-gnu/libdl.so.2+0x162c)
#11 0x7f199d1a60c0 (/lib/x86_64-linux-gnu/libdl.so.2+0x10c0)
#12 0x7f199e0156b7 (/usr/lib/x86_64-linux-gnu/libQtCore.so.4+0x16e6b7)
#13 0x7f199e010599 (/usr/lib/x86_64-linux-gnu/libQtCore.so.4+0x169599)
#14 0x4011c0 in main /home/tsdgeos/test/main.cpp:8
#15 0x7f199d5e8ec4 (/lib/x86_64-linux-gnu/libc.so.6+0x21ec4)
#16 0x401078 in _start (/home/tsdgeos/test/a.out+0x401078)
SUMMARY: AddressSanitizer: SEGV /home/tsdgeos/test/shared.cpp:8 Foo::Foo()
==7048== ABORTING
So it seems that "plugins are just libraries" applies here :)
Thursday, March 20, 2014
ASAN and libraries
Yesterday we saw how to get line numbers in the stacktrace when using ASAN and gcc, today we're going to see how to deal with ASAN and libraries. For that we're going to use these three very simple files
shared.cpp
shared.h
main.cpp
We do the initial compilation:
Now we want to use ASAN to find out what's wrong, where do we add the -fsanitize=address -fno-omit-frame-pointer? Logic would say that we add it to both places, but actually it's only necessary to add it to the final binary, i.e
There you go, no need to add the -fsanitize=address flag to the library compilation :)
Now, until a few minutes ago I did not know this, I actually was adding -fsanitize=address to the library itself; that comes with a few problems that i'll explain how i solved (just for completeness, since the above example shows you don't need it)
My logic was that by looking at main.cpp i knew nothing could be wrong there so i decided i wanted sanitize the library, my first attempt was:
OK, so we are told to recompile with -fPIC, easy peasy
OK, so if ASAN symbols are missing, let's just compile libasan in
Next since I know nothing is wrong in main.cpp I don't need ASAN in there
But when run it segfaults :-/ And if you debug it you'll see a stack trace like
So something weird in ASAN thing is going on, let's compile -lasan in also
Same crash :-/
Ok, so then you think, well, let's just add the fsanitize in. And then it works, but as demonstrated a few lines ago, the whole thing of adding -fsanitize=address and -lasan to the library was unneeded since all that was required was just adding -fsanitize=address to the binary when it's compiled and that's it :)
shared.cpp
#include "shared.h"
Foo::Foo()
{
int *a = 0;
*a = 33;
}
shared.h
class Foo
{
public:
Foo();
};
main.cpp
#include "shared.h"
int main(int, char **)
{
Foo f;
return 0;
}
We do the initial compilation:
g++ -Wl,--no-undefined -shared -o libshared.so shared.cpp -g3 g++ main.cpp -lshared -L . -g3 LD_LIBRARY_PATH=. ./a.outand it segfaults :)
Now we want to use ASAN to find out what's wrong, where do we add the -fsanitize=address -fno-omit-frame-pointer? Logic would say that we add it to both places, but actually it's only necessary to add it to the final binary, i.e
g++ -Wl,--no-undefined -shared -o libshared.so shared.cpp -g3 g++ -fno-omit-frame-pointer -fsanitize=address main.cpp -lshared -L . -g3 LD_LIBRARY_PATH=. ./a.outand we get
==10226== ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000
(pc 0x7f497563f66a sp 0x7fff77cc4310 bp 0x7fff77cc4310 T0)
AddressSanitizer can not provide additional info.
#0 0x7f497563f669 in Foo::Foo() /home/tsdgeos/test/shared.cpp:6
#1 0x40074a in main /home/tsdgeos/test/main.cpp:5
#2 0x7f497529aec4 (/lib/x86_64-linux-gnu/libc.so.6+0x21ec4)
#3 0x400638 in _start (/home/tsdgeos/test/a.out+0x400638)
SUMMARY: AddressSanitizer: SEGV /home/tsdgeos/test/shared.cpp:6 Foo::Foo()
There you go, no need to add the -fsanitize=address flag to the library compilation :)
Now, until a few minutes ago I did not know this, I actually was adding -fsanitize=address to the library itself; that comes with a few problems that i'll explain how i solved (just for completeness, since the above example shows you don't need it)
My logic was that by looking at main.cpp i knew nothing could be wrong there so i decided i wanted sanitize the library, my first attempt was:
g++ -Wl,--no-undefined -shared -o libshared.so shared.cpp -g3 \ -fno-omit-frame-pointer -fsanitize=addresswhich gives a linking error
/tmp/cc18Wen3.o: In function `Foo::Foo()': /home/tsdgeos/test/shared.cpp:6: undefined reference to `__asan_report_store4' /usr/bin/ld: /tmp/cc18Wen3.o: relocation R_X86_64_PC32 against undefined symbol `__asan_report_store4' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Bad value
OK, so we are told to recompile with -fPIC, easy peasy
g++ -Wl,--no-undefined -shared -o libshared.so shared.cpp -g3 \ -fno-omit-frame-pointer -fsanitize=address -fPICWhich still fails to link!
/tmp/ccNkpRZo.o: In function `Foo::Foo()': /home/tsdgeos/test/shared.cpp:6: undefined reference to `__asan_report_store4' /tmp/ccNkpRZo.o: In function `_GLOBAL__sub_I_00099_0_shared.cpp': /home/tsdgeos/test/shared.cpp:7: undefined reference to `__asan_init_v1' collect2: error: ld returned 1 exit status
OK, so if ASAN symbols are missing, let's just compile libasan in
g++ -Wl,--no-undefined -shared -o libshared.so shared.cpp -g3 \ -fno-omit-frame-pointer -fsanitize=address -fPIC -lasanLinks!
Next since I know nothing is wrong in main.cpp I don't need ASAN in there
g++ main.cpp -lshared -L . -g3Compiles!
But when run it segfaults :-/ And if you debug it you'll see a stack trace like
#0 0x0000000000000000 in ?? () #1 0x00007ffff4894bf1 in ?? () from /usr/lib/x86_64-linux-gnu/libasan.so.0 #2 0x00007ffff4894e32 in ?? () from /usr/lib/x86_64-linux-gnu/libasan.so.0 #3 0x00007ffff4895d9b in __asan_init_v1 () from /usr/lib/x86_64-linux-gnu/libasan.so.0 #4 0x00007ffff7bd8776 in _GLOBAL__sub_I_00099_0_shared.cpp(void) () at shared.cpp:7 #5 0x00007ffff7dea13a in call_init (l=, argc=argc@entry=1, argv=argv@entry=0x7fffffffde18, env=env@entry=0x7fffffffde28) at dl-init.c:78 #6 0x00007ffff7dea223 in call_init (env= , argv= , argc= , l= ) at dl-init.c:36 #7 _dl_init (main_map=0x7ffff7ffe1c8, argc=1, argv=0x7fffffffde18, env=0x7fffffffde28) at dl-init.c:126 #8 0x00007ffff7ddb30a in _dl_start_user () from /lib64/ld-linux-x86-64.so.2 #9 0x0000000000000001 in ?? () #10 0x00007fffffffe1ca in ?? () #11 0x0000000000000000 in ?? ()
So something weird in ASAN thing is going on, let's compile -lasan in also
g++ main.cpp -lshared -L . -g3 -lasan
Same crash :-/
Ok, so then you think, well, let's just add the fsanitize in. And then it works, but as demonstrated a few lines ago, the whole thing of adding -fsanitize=address and -lasan to the library was unneeded since all that was required was just adding -fsanitize=address to the binary when it's compiled and that's it :)
Wednesday, March 19, 2014
ASAN and gcc: How to get line numbers in the stacktrace
ASAN or Address Sanitizer is a nice project by Google that is a memory error detector for C/C++. According to their web it finds:
Also it's much faster than valgrind :-) Unfortunately it's not as easy to use as valgrind since it requires a rebuild of your code.
The basic instructions to use ASAN are:
As a simple example let's see what happens when we run
The result:
In this case it's pretty obvious what's wrong with just looking at the code and ASAN is even telling us it is a bad write just after the 'a' object, but note that we are not getting the line number of where the error happens. You'll say, that's why you didn't use the -g switch! So let's see what do we get after compiling with
The result:
Same thing :-/
Here is where people may give up or think to switch to clang and try there, but since clang is sometimes more picky with the code (not bad per se) it may be a lot of work to get your code to compile under clang, if you keep digging you'll read some news about GCC not having a ASAN symbolizer [yet], but clang has one and you can still use it with GCC, so if you
The result:
And now we have line numbers :-)
- Use after free (dangling pointer dereference)
- buffer overflow
- Stack buffer overflow
- Global buffer overflow
- Use after return
- Initialization order bugs
Also it's much faster than valgrind :-) Unfortunately it's not as easy to use as valgrind since it requires a rebuild of your code.
The basic instructions to use ASAN are:
Use the -fsanitize=address switchtogether with the suggestion of
To get nicer stack traces in error messages add -fno-omit-frame-pointer.
As a simple example let's see what happens when we run
int main(int, char **)
{
int a[3];
a[3] = 4;
return 0;
}
compiled withg++ -fno-omit-frame-pointer -fsanitize=address main.cpp
The result:
==8403== ERROR: AddressSanitizer: stack-buffer-overflow
on address 0x7fffbe7c7d8c at pc 0x400779
bp 0x7fffbe7c7d40 sp 0x7fffbe7c7d38
WRITE of size 4 at 0x7fffbe7c7d8c thread T0
#0 0x400778 (/home/tsdgeos_work/test/a.out+0x400778)
#1 0x7f2f5cfa6ec4 (/lib/x86_64-linux-gnu/libc-2.19.so+0x21ec4)
#2 0x400638 (/home/tsdgeos_work/test/a.out+0x400638)
Address 0x7fffbe7c7d8c is located at offset 44 in frame of T0's stack:
This frame has 1 object(s):
[32, 44) 'a'
In this case it's pretty obvious what's wrong with just looking at the code and ASAN is even telling us it is a bad write just after the 'a' object, but note that we are not getting the line number of where the error happens. You'll say, that's why you didn't use the -g switch! So let's see what do we get after compiling with
g++ -g3 -fno-omit-frame-pointer -fsanitize=address main.cpp
The result:
==8467== ERROR: AddressSanitizer: stack-buffer-overflow
on address 0x7fff59ccaa2c at pc 0x400779
bp 0x7fff59cca9e0 sp 0x7fff59cca9d8
WRITE of size 4 at 0x7fff59ccaa2c thread T0
#0 0x400778 (/home/tsdgeos_work/test/a.out+0x400778)
#1 0x7f6f75601ec4 (/lib/x86_64-linux-gnu/libc-2.19.so+0x21ec4)
#2 0x400638 (/home/tsdgeos_work/test/a.out+0x400638)
Address 0x7fff59ccaa2c is located at offset 44 in frame of T0's stack:
This frame has 1 object(s):
[32, 44) 'a'
Same thing :-/
Here is where people may give up or think to switch to clang and try there, but since clang is sometimes more picky with the code (not bad per se) it may be a lot of work to get your code to compile under clang, if you keep digging you'll read some news about GCC not having a ASAN symbolizer [yet], but clang has one and you can still use it with GCC, so if you
export ASAN_SYMBOLIZER_PATH=/usr/bin/llvm-symbolizer-3.4 export ASAN_OPTIONS=symbolize=1and then run the binary again (the one we just compiled with -g3)
The result:
WRITE of size 4 at 0x7fff4f5f0ebc thread T0
#0 0x400778 in main /home/tsdgeos_work/test/main.cpp:5
#1 0x7f3d4dce2ec4 (/lib/x86_64-linux-gnu/libc.so.6+0x21ec4)
#2 0x400638 in _start (/home/tsdgeos_work/test/a.out+0x400638)
Address 0x7fff4f5f0ebc is located at offset 44 in frame of T0's stack:
This frame has 1 object(s):
[32, 44) 'a'
And now we have line numbers :-)
Akademy-es 2014 in Málaga
This year, the 9th Akademy-es will take place in Málaga from 16 to 18 May.
Málaga is the city that hosted Akademy 2005 and were a few few crazy people met and thought about doing Akademy-es 2006 next year in Barcelona, and after that, 9 years in a row. Not bad :-)
I'm definitely going and you should if you're interested in KDE too. And of course you should think about submitting a talk :-)
Finally if you have a company you may want to join and sponsor the event, have a look at the sponsor page.
Registration is still not open but will be in a few days/weeks.
Hope to see you there :-)
Málaga is the city that hosted Akademy 2005 and were a few few crazy people met and thought about doing Akademy-es 2006 next year in Barcelona, and after that, 9 years in a row. Not bad :-)
I'm definitely going and you should if you're interested in KDE too. And of course you should think about submitting a talk :-)
Finally if you have a company you may want to join and sponsor the event, have a look at the sponsor page.
Registration is still not open but will be in a few days/weeks.
Hope to see you there :-)
Saturday, January 25, 2014
How to strike out text in Okular
We just had a user report a wish item in bugs.kde.org asking for Okular to come with a text strike-out annotation by default. I just closed the bug saying that he can create his own annotations by Settings -> Configure Okular -> Annotations -> Add ->
Text Markup -> Strike Out -> Set Color -> OK

Of course we could still ship it, but if you have a look at that "Add Annotations" dialogs there's lots of lots of possibilities so people should just create the ones they see the need for instead of us shipping lots that may not be that useful.
Text Markup -> Strike Out -> Set Color -> OK

Of course we could still ship it, but if you have a look at that "Add Annotations" dialogs there's lots of lots of possibilities so people should just create the ones they see the need for instead of us shipping lots that may not be that useful.
Etiquetes de comentaris:
annotations,
okular,
strikeout
Thursday, January 09, 2014
KDE Applications and Platform 4.13 Schedule
You can find the release schedule for KDE Applications and Platform 4.13 at http://techbase.kde.org/Schedules/KDE4/4.13_Release_Schedule
This schedule consolidates the changes made for 4.12 since it seems to have worked well.
Also remember that 4.13 will be applications and kdelibs only; KDE Workspace (aka Plasma) will be getting 4.11.x LTS releases until August 2015
This schedule consolidates the changes made for 4.12 since it seems to have worked well.
Also remember that 4.13 will be applications and kdelibs only; KDE Workspace (aka Plasma) will be getting 4.11.x LTS releases until August 2015
Etiquetes de comentaris:
4.13,
kde,
release schedule
Tuesday, October 29, 2013
Changes in Okular printing for 4.12
Since today, Okular master (i.e. 4.12) respects the margins specified in the printer setup dialog (which default to the hard-margins of the printer). This means that I'll be able to print in my printer without getting cropped stuff; yes, my printer has a default hard-dead margin of 1.5 cm at the bottom and usually files contain stuff in that area.
If your document does already contains the margins, you can get the old behaviour by simply setting the margins to 0. Also hopefully you don't have a printer that is as bad as mine and your default margins are just 0,0,0,0
If your document does already contains the margins, you can get the old behaviour by simply setting the margins to 0. Also hopefully you don't have a printer that is as bad as mine and your default margins are just 0,0,0,0
Sunday, October 27, 2013
KDEEdu sprint is over for me
I'm sitting at the Coruña airport waiting for my plane for Barcelona to leave. This means my three days at the KDEEdu Sprint 2013 are gone. It's been good to meet new people like Punit, get to know better people I had already met like Samikshan and meet old co-sprints like Sebastian and Andreas, and of course re-meeting my fellow KDE España friends Jose, Aleix and Santa. Sadly Oindrila could not make it due to visa problems :-(
In these three days we'd had time to talk about KDE Edu apps future on mobile, KF5 ports, libkdeedu splitting and lots of other stuff.
I tried to port Blinken over the BB10. Got stuck trying to compile stuff using cmake until I found KDE's own Laszlo Papp guide. Unfortunately other stuff got in the middle and I could not finish the port, but now I'm closer and if I can find a couple of free afternoons will probably have something in the BB10 store.
Unrelated to KDEEdu i finally got time to create a review request for a patch i worked a few weeks ago that will hopefully workaround one of the most hated crashes people are having in the KDE Plasma Desktop, let's see if that helps.
Finally, I'd like to thank GPUL and KDE e.V. for organizing and sponsoring the event. And specially thanks to Jose for his mad organizing skills, you're awesome :-)
In these three days we'd had time to talk about KDE Edu apps future on mobile, KF5 ports, libkdeedu splitting and lots of other stuff.
I tried to port Blinken over the BB10. Got stuck trying to compile stuff using cmake until I found KDE's own Laszlo Papp guide. Unfortunately other stuff got in the middle and I could not finish the port, but now I'm closer and if I can find a couple of free afternoons will probably have something in the BB10 store.
Unrelated to KDEEdu i finally got time to create a review request for a patch i worked a few weeks ago that will hopefully workaround one of the most hated crashes people are having in the KDE Plasma Desktop, let's see if that helps.
Finally, I'd like to thank GPUL and KDE e.V. for organizing and sponsoring the event. And specially thanks to Jose for his mad organizing skills, you're awesome :-)
KReversi master is now Qt Quick based!
Denis Kuplyakov worked on porting KReversi to QtQuick during this Google Summer of Code and his code has now been merged to master for the upcoming 4.12 release. The kdegames team has given the new code as much testing as we can, but it is a big re-work so it'd be great if you can give it a try and report any regression you may find compared to the old version.
Wednesday, October 02, 2013
4 weeks until KDE SC 4.12 Feature Freeze
Just a quick heads up that the KDE SC 4.12 Feature Freeze is now 4 weeks away.
Full schedule at http://techbase.kde.org/Schedules/KDE4/4.12_Release_Schedule.
Full schedule at http://techbase.kde.org/Schedules/KDE4/4.12_Release_Schedule.
Saturday, September 21, 2013
Dine with the KDE e.V. board
Next weekend (September 28-29) the KDE e.V. board is going to have an in-person board meeting in Berlin.
As part of the board meeting we'll have food (geeks need to eat too) and since we like talking to other people besides ourselves we’d like to invite KDE people to come to the board dinner on Saturday at 19:00 (location still undecided).
We can talk about all things KDE, KDE e.V., Free Software and maybe even have a good time ;-). Please let me know as soon as possible if you’re coming as space is limited.
As part of the board meeting we'll have food (geeks need to eat too) and since we like talking to other people besides ourselves we’d like to invite KDE people to come to the board dinner on Saturday at 19:00 (location still undecided).
We can talk about all things KDE, KDE e.V., Free Software and maybe even have a good time ;-). Please let me know as soon as possible if you’re coming as space is limited.
Thursday, August 29, 2013
KNetwalk ported to QtQuick
Ashwin Rajeev has just commited his port of KNetwalk to use QtQuick to the master branch of the knetwalk git repository.
Ideally you should not notice any difference, but it would be awesome if you guys could give it a try and report to either Ashwin or to the kde-games-devel mailing list (if you do it here I'll try to pass the info, but I'm going to be off the web for a while so it may get lost when I come back and there's a ton of emails to read :D)
Ideally you should not notice any difference, but it would be awesome if you guys could give it a try and report to either Ashwin or to the kde-games-devel mailing list (if you do it here I'll try to pass the info, but I'm going to be off the web for a while so it may get lost when I come back and there's a ton of emails to read :D)
Tuesday, August 20, 2013
KDE SC 4.12 Release Schedule
After discussions at kde-core-devel, Akademy and release-team you can find the release schedule for KDE SC 4.12 at http://techbase.kde.org/Schedules/KDE4/4.12_Release_Schedule
The main change agreed by Release Team is that we have more simplified freezes (basically just one) and our betas/RC happen a bit more often (every week) so we have testers trying more up to date code. This also lead to a somewhat shorter cycle with a release mid December 2013.
The main change agreed by Release Team is that we have more simplified freezes (basically just one) and our betas/RC happen a bit more often (every week) so we have testers trying more up to date code. This also lead to a somewhat shorter cycle with a release mid December 2013.
Etiquetes de comentaris:
4.12,
kde,
release schedule
Sunday, August 04, 2013
Fixed: My Z10 automagically shutsdown at a random battery number (mine was around 33%)
Last week I hard a weird issue in which my Z10 was shutting down when the battery was around 33%, I thought the battery had gone wrong, but it seems the problem lies somewhere in the OS that gets confused, in my case i think it was because i pulled/put different batteries in a very short time span.
After some digging I found http://forums.crackberry.com/blackberry-z10-f254/blackberry-z10-shuts-down-30-battery-807279/index6.html#post8755531 that helped me make the OS "reset" according to battery handling.
Basically it boilds down to "make sure you really really run out of battery and it'll fix itself"
Adding here in case someone has the same issue.
After some digging I found http://forums.crackberry.com/blackberry-z10-f254/blackberry-z10-shuts-down-30-battery-807279/index6.html#post8755531 that helped me make the OS "reset" according to battery handling.
Basically it boilds down to "make sure you really really run out of battery and it'll fix itself"
Adding here in case someone has the same issue.
Tuesday, July 30, 2013
KDE 4.11 releases are around the corner. Let's cellebrate!
At KDE España we have started the ball rolling to cellebrate the release for 4.11 by starting the organization of the Barcelona event. Right now it feels pretty lonely at http://community.kde.org/Promo/Events/Release_Parties/4.11.
If you are interested in attending the Barcelona event don't hesitate voting at the doodle to decide the day!
If you are interested in attending the Barcelona event don't hesitate voting at the doodle to decide the day!
Etiquetes de comentaris:
barcelona,
kde,
release party
Saturday, July 06, 2013
Okular: "fit best" zoom. Yes? No? How?
The Okular team is looking for your input regarding a potential "Fit Best" feature for zoom. Please visit http://forum.kde.org/viewtopic.php?f=251&t=111777&sid=343334fa86e550d294793cf6a56e6ce5 and give us your opinion!
Sunday, June 30, 2013
I'm going to Bilbao!
I will be in Bilbao from July 11th to 19th. I am going to be attending lots of different events

The first of the events is the Akademy-es, Akademy little sister that we've been celebrating since 2006, this year we have modified of usual schedule of making it happen in a weekend to accommodate for Akademy schedule, so it will run from Thursday to Friday. In Akademy-es I'll be talking of how Qt5 and KDE projects fit together and also about QML, QtQuick and the other declarative-y things you can find in Qt world.

Obviously I'll also be at Akademy, I've been attending each year since 2005 so I couldn't miss it :-) I'm looking forward to lots of the talks there, but specially the keynote by Kevin Ottens :-) I will be running for a position in the KDE e.V. board as announced in the kde-community mailing list a few weeks ago, wish me luck!
Qt Contributor Summit
On Monday and Tuesday we will have the Qt Contributor Summit running in parallel with Akademy. I will be there with my Canonical-hat making sure everything QML-y we need for the Ubuntu software we are writing in Qt is fine and dandy :-)

And incidentally from Thursday to Saturday there's Green Day, Depenche Mode, Kings of Leon, Biffy Clyro and a lot more of bands playing in Bilbao, so I could not miss them!
Rock on Bilbao!
The first of the events is the Akademy-es, Akademy little sister that we've been celebrating since 2006, this year we have modified of usual schedule of making it happen in a weekend to accommodate for Akademy schedule, so it will run from Thursday to Friday. In Akademy-es I'll be talking of how Qt5 and KDE projects fit together and also about QML, QtQuick and the other declarative-y things you can find in Qt world.
Obviously I'll also be at Akademy, I've been attending each year since 2005 so I couldn't miss it :-) I'm looking forward to lots of the talks there, but specially the keynote by Kevin Ottens :-) I will be running for a position in the KDE e.V. board as announced in the kde-community mailing list a few weeks ago, wish me luck!
Qt Contributor Summit
On Monday and Tuesday we will have the Qt Contributor Summit running in parallel with Akademy. I will be there with my Canonical-hat making sure everything QML-y we need for the Ubuntu software we are writing in Qt is fine and dandy :-)
And incidentally from Thursday to Saturday there's Green Day, Depenche Mode, Kings of Leon, Biffy Clyro and a lot more of bands playing in Bilbao, so I could not miss them!
Rock on Bilbao!
Etiquetes de comentaris:
akademy,
akademy-es,
bilbao,
qtcs
Tuesday, June 11, 2013
builds.kde.org tests report for 4.11 release - 11 June 2013
We are 2 days away from Beta 1 tag:
* kate has 1 test that fails
* kcalc has 1 test that fails
* kde-baseapps has 1 test that fails
* kde-runtime has 1 test that fails
* kdepim has 5 tests that fail
* kdepim-runtime has 1 test that fail
* kdepimlibs has 7 tests that fail
* knetwalk has 1 test that fails
* kopete has 2 tests that fail
* ksystemlog has 1 test that fails
* marble has 1 test that fails
* okteta has 1 test that fails
Everything else that belongs into the 4.11 release is green
Please fix your tests.
* kate has 1 test that fails
* kcalc has 1 test that fails
* kde-baseapps has 1 test that fails
* kde-runtime has 1 test that fails
* kdepim has 5 tests that fail
* kdepim-runtime has 1 test that fail
* kdepimlibs has 7 tests that fail
* knetwalk has 1 test that fails
* kopete has 2 tests that fail
* ksystemlog has 1 test that fails
* marble has 1 test that fails
* okteta has 1 test that fails
Everything else that belongs into the 4.11 release is green
Please fix your tests.
Tuesday, May 28, 2013
Akademy-es 2013 schedule ready!
As you probably know we are having Akademy-es 2013 just a few days earlier than Akademy in Bilbao, from 11th to 12th of July.
We have just made the schedule available. If you understand Spanish you may want to come to Bilbao a few days earlier to enjoy our talks :-)
We have just made the schedule available. If you understand Spanish you may want to come to Bilbao a few days earlier to enjoy our talks :-)
Tuesday, May 21, 2013
Okular welcomes configurable review tools
I have just merged to master a branch by Fabio D'Urso that lets you configure the review tools that appear in the review bar.

This way you can decide that by default you want your highlighter to be green instead of yellow. Or even have two highlighters in the review bar.
Please test and enjoy it :-)

This way you can decide that by default you want your highlighter to be green instead of yellow. Or even have two highlighters in the review bar.
Please test and enjoy it :-)
Wednesday, May 15, 2013
4.11 Soft Feature Freeze in 7 days!
Remember the 4.11 Soft Feature Freeze is in 7 days so try to get your features ready for merging as soon as possible. If you add your features to the Feature Plan you get two weeks more until Hard Feature Freeze. Even if you don't need those two weeks you should add them anyway since it really helps other teams like promo, Q/A, etc. to have the features listed in one place.
Tuesday, May 07, 2013
gs 9.07 can't render ps files on comma-locales [fixed]
Okular and other libspectre based PostScript viewers can't render some ps files when using a locale that uses , instead of . for decimals.
This happens because of a bug in ghostscript 9.07 that has now been fixed.
I'm not a huge fan of distro-patches myself, but in this case it may make sense to have one, so feel free to ping your distribution if you are a PostScript user.
This happens because of a bug in ghostscript 9.07 that has now been fixed.
I'm not a huge fan of distro-patches myself, but in this case it may make sense to have one, so feel free to ping your distribution if you are a PostScript user.
Etiquetes de comentaris:
ghostscript,
libspectre,
okular,
postscript
Saturday, April 20, 2013
Specifications: Correct when writing, Gentle when reading
I got a BlackBerry Z10 a few days ago.
I had not tried to use it as my main phone until yesterday since it needed a MicroSIM and i had a regular one.
Yesterday I got myself a MicroSIM and put it on the device to find out I could not access the 3G data network.
No problem, my operator has a website where you put the make and model of the phone and they send a SMS to the phone that autoconfigures it.
I went there and was surprised to see there was no BlackBerry listed at all.
OK, time to write the APN settings by hand, so I went to the Settings and started to look where to write the APN details, found them and realized they were disabled(greyed out) so I could not write the correct values.
After lots of searching I have come to understand that the phone obeys a indicator of the SIM that can say "I know how to connect to 3G data, no need to letting the user edit it" and when that happens, the BlackBerry Z10 happily complies and locks you out from editing them.
Problem is, my operator SIMs are wrong, they say "I know how to connect to 3G data, no need to letting the user edit it" and then provide wrong data.
And BOOM! I have a nice paperweight worth 600€
BlackBerry fan forums are full of people that say "BlackBerry is just doing what the spec says, blame your operator".
I say to them "I've used that SIM in Apple devices, Samsung devices and Nokia devices and had never any problem connecting to the Internet". Because the manufacturers were smart enough to let me edit the APN settings and write there the correct values if I wanted.
And this brings us to one of the mantras of engineering, be Correct when writing stuff but be Gentle when reading. It's good the BlackBerry browser is following that mantra, otherwise you'd hardly be able to render any webpage.
So people at BlackBerry, please come of your senses and let people edit stuff. This way maybe I'll get to use your device and people around me will see it and will want to buy one.
Otherwise I'll just wait until the Ubuntu Phone is a bit more usable and start using it. It may not be as polished (at the moment) but at least it's open source and I can fix crazy stuff like this.
Update: With BB 10.1.0.1627 I've been able to edit the field and now my 3G data works again
I had not tried to use it as my main phone until yesterday since it needed a MicroSIM and i had a regular one.
Yesterday I got myself a MicroSIM and put it on the device to find out I could not access the 3G data network.
No problem, my operator has a website where you put the make and model of the phone and they send a SMS to the phone that autoconfigures it.
I went there and was surprised to see there was no BlackBerry listed at all.
OK, time to write the APN settings by hand, so I went to the Settings and started to look where to write the APN details, found them and realized they were disabled(greyed out) so I could not write the correct values.
After lots of searching I have come to understand that the phone obeys a indicator of the SIM that can say "I know how to connect to 3G data, no need to letting the user edit it" and when that happens, the BlackBerry Z10 happily complies and locks you out from editing them.
Problem is, my operator SIMs are wrong, they say "I know how to connect to 3G data, no need to letting the user edit it" and then provide wrong data.
And BOOM! I have a nice paperweight worth 600€
BlackBerry fan forums are full of people that say "BlackBerry is just doing what the spec says, blame your operator".
I say to them "I've used that SIM in Apple devices, Samsung devices and Nokia devices and had never any problem connecting to the Internet". Because the manufacturers were smart enough to let me edit the APN settings and write there the correct values if I wanted.
And this brings us to one of the mantras of engineering, be Correct when writing stuff but be Gentle when reading. It's good the BlackBerry browser is following that mantra, otherwise you'd hardly be able to render any webpage.
So people at BlackBerry, please come of your senses and let people edit stuff. This way maybe I'll get to use your device and people around me will see it and will want to buy one.
Otherwise I'll just wait until the Ubuntu Phone is a bit more usable and start using it. It may not be as polished (at the moment) but at least it's open source and I can fix crazy stuff like this.
Update: With BB 10.1.0.1627 I've been able to edit the field and now my 3G data works again
Tuesday, April 16, 2013
builds.kde.org tests report for 4.11 release - 15 April 2013
We are 59 days away from Beta 1:
* kate has 1 tests that fails
* kde-runtime has 1 test that fail
* kdelibs has 1 test that fails
* kdepim has 8 tests that fail
* kdepim-runtime has 21 tests that fails
* kdepimlibs has 14 tests that fails
* nepomuk-widgets has 1 test that fails
* okteta has 1 test that fails
Everything else that belongs into the 4.11 release is green
You can find the up-to-date info at jenkins http://build.kde.org/view/KDE%20SC%20master/
* kate has 1 tests that fails
* kde-runtime has 1 test that fail
* kdelibs has 1 test that fails
* kdepim has 8 tests that fail
* kdepim-runtime has 21 tests that fails
* kdepimlibs has 14 tests that fails
* nepomuk-widgets has 1 test that fails
* okteta has 1 test that fails
Everything else that belongs into the 4.11 release is green
You can find the up-to-date info at jenkins http://build.kde.org/view/KDE%20SC%20master/
Saturday, April 06, 2013
Okular welcomes undo/redo for annotations
Thanks to the amazing work of Jon Mease Okular now has undo/redo for annotation editing in master. Give it a go, it's quite cool :)
Now let's see if we can get Jon to do the same for Form editing, everyone give him some love!
Now let's see if we can get Jon to do the same for Form editing, everyone give him some love!
Monday, April 01, 2013
builds.kde.org tests report for 4.11 release - 1 April 2013
We are 73 days away from Beta 1:
* kate has 2 tests that fail (down 2-3 from 2 weeks ago)
* kde-runtime has 1-2 tests that fail (no change)
* kdelibs has 1 test that fails (up 1 from 2 weeks ago)
* kdepim has 7-8 tests that fail (stable from 2 weeks ago)
* kdepim-runtime has 19-22 tests that fail (up 0-3 from 2 weeks ago)
* kdepimlibs has 12-16 tests that fail (stable from 2 weeks ago)
* nepomuk-core has 1 test that fails (down 2 from 2 weeks ago)
* nepomuk-widgets has 1 test that fails (stable from 2 weeks ago)
* okteta has 1 test that fails (stable from 2 weeks ago)
Everything else that belongs into the 4.11 release is green
* kate has 2 tests that fail (down 2-3 from 2 weeks ago)
* kde-runtime has 1-2 tests that fail (no change)
* kdelibs has 1 test that fails (up 1 from 2 weeks ago)
* kdepim has 7-8 tests that fail (stable from 2 weeks ago)
* kdepim-runtime has 19-22 tests that fail (up 0-3 from 2 weeks ago)
* kdepimlibs has 12-16 tests that fail (stable from 2 weeks ago)
* nepomuk-core has 1 test that fails (down 2 from 2 weeks ago)
* nepomuk-widgets has 1 test that fails (stable from 2 weeks ago)
* okteta has 1 test that fails (stable from 2 weeks ago)
Everything else that belongs into the 4.11 release is green
Monday, March 18, 2013
KDE Frameworks 5 day at Barcelona
This last Saturday, Alex Fiestas, Martin Klapetek, Miquel Canes, Aleix Pol and me spent the whole day acquainting ourselves with the KDE Frameworks 5 codebase and starting to work on some of the tasks described in the Qt 5.1 and kdelibs cleanup epics.
It was a great day but i still have to say I find myself a bit lost in Frameworks land, we'll have to repeat it soon to get more in the loop :-)

I'd like to thank Blue Systems for hosting us in their office in Barcelona.
It was a great day but i still have to say I find myself a bit lost in Frameworks land, we'll have to repeat it soon to get more in the loop :-)

I'd like to thank Blue Systems for hosting us in their office in Barcelona.
Etiquetes de comentaris:
barcelona,
kde frameworks
builds.kde.org tests report for 4.11 release - 18 March 2013
We are 87 days away from Beta 1:
* kate has 4-5 tests that fail
* kde-runtime has 0-2 tests that fail
* kdepim has 7-8 tests that fail
* kdepim-runtime has 19 tests that fail
* kdepimlibs has 12-16 tests that fail
* nepomuk-core has 3 tests that fail
* nepomuk-widgets has 1 test that fails
* okteta has 1 test that fails
Everything else that belongs into the 4.11 release is green
* kate has 4-5 tests that fail
* kde-runtime has 0-2 tests that fail
* kdepim has 7-8 tests that fail
* kdepim-runtime has 19 tests that fail
* kdepimlibs has 12-16 tests that fail
* nepomuk-core has 3 tests that fail
* nepomuk-widgets has 1 test that fails
* okteta has 1 test that fails
Everything else that belongs into the 4.11 release is green
Wednesday, March 13, 2013
KDE SC 4.11 Release Schedule
You can find it at http://techbase.kde.org/Schedules/KDE4/4.11_Release_Schedule
There are two main changes agreed by Release Team against the previous releases:
* No specified time between Beta and RC tag and release. We will try to release them ASAP after the tag to make them as useful as possible
* No release with broken tests. We won't release if there are tests that do not pass in build.kde.org. So please start caring about tests that do not pass
There are two main changes agreed by Release Team against the previous releases:
* No specified time between Beta and RC tag and release. We will try to release them ASAP after the tag to make them as useful as possible
* No release with broken tests. We won't release if there are tests that do not pass in build.kde.org. So please start caring about tests that do not pass
Etiquetes de comentaris:
4.11,
kde,
release schedule
Monday, February 18, 2013
KDE 4.10 Release Party in Barcelona
This Friday 22nd of February we are having the KDE 4.10 Release Party in Barcelona. Fill in the wiki or tell me if you want to come!
Etiquetes de comentaris:
4.10,
kde,
release party
Subscribe to:
Posts (Atom)




