Federico Mena Quintero | 27 Feb 17:44 2015
Picon

Librsvg 2.40.8 is released

Dear lovers of fast vectors,

Here is a new release of librsvg, everyone's favorite SVG rendering
library.  There is a fuzz-testing bugfix in this release, and a few
minor optimizations.

I removed a libart-ism which I then had to revert, because it caused
incorrect rendering (see bug #745177).  If anyone has any clue of why we
need a "moveto" after "closepath", I'm all ears :)

Anyway, you can get librsvg-2.40.8 here:

  https://download.gnome.org/sources/librsvg/2.40/

Checksums:

9c355bf863011675403cf432254661da32a5be90fe640310f192c7b72bcc869d  librsvg-2.40.8.news
724ae4a17fe70729a6b44fefbd4f68b7f8d63902e361cf40c7105b2a35ed2ede  librsvg-2.40.8.changes
0af42ec79ebfc70f980a9adf63f1b63d8150457dc7140dd041484e8c60d5387a  librsvg-2.40.8.tar.xz

Changes in this release:

- Bugs fixed from fuzz testing: #744688 - possible double g_free()
  when processing stroke-dasharray
- Optimize rendering of polylines, lines, rectangles, circles, and
  ellipses.  These should be marginally faster, marginally more
  precise, and should put less pressure on the memory allocator.

Enjoy,

(Continue reading)

Release Team | 27 Feb 01:00 2015
Picon

GNOME 3.15.91 beta tarballs due (and more)

Hello all,

We would like to inform you about the following:
* GNOME 3.15.91 beta tarballs due
* String Freeze

Tarballs are due on 2015-03-02 before 23:59 UTC for the GNOME 3.15.91
beta release, which will be delivered on Wednesday. Modules which were
proposed for inclusion should try to follow the unstable schedule so
everyone can test them.  Please make sure that your tarballs will be
uploaded before Monday 23:59 UTC: tarballs uploaded later than that
will probably be too late to get in 3.15.91. If you are not able to
make a tarball before this deadline or if you think you'll be late,
please send a mail to the release team and we'll find someone to roll
the tarball for you!

No string changes may be made without confirmation from the i18n team
and notification to release team, translation team, and documentation
team. From this point, developers can concentrate on stability and
bug-fixing. Translators can work without worrying that the original
English strings will change, and documentation writers can take
accurate screenshots. For the string freezes explained, and to see
which kind of changes are not covered by freeze rules, check
https://wiki.gnome.org/TranslationProject/HandlingStringFreezes.

For more information about 3.15, the full schedule, the official
module lists and the proposed module lists, please see our colorful 3.15
page:
   http://www.gnome.org/start/unstable

(Continue reading)

Daniel Svensson | 22 Feb 14:46 2015
Picon

Using GNOME Continous images

Hi,
I'm developing some GTK applications and I usually try to stay ahead of the curve wrt new features. Traditionally I've been using jhbuild to get newer library versions than Debian Sid has to offer, but I've recently read up a bit on OSTree thanks to Alex's blog post on sandboxed applications and then from there I read about the build.g.o images. I've done some basic experimentation but I'm kind of stuck, so question time:

What images to use?

Here are two fairly recent directories both named "current":

One has z in its directory and is compressed, but is also 20 days older than the former, and both images are from january when we're now in late febuary, which takes us to the next question..

What conditions must be met for a new qcow2 image to be created?

Is it correct that the latest of these ones, 27:th jan, is the one to use, and then execute "ostree admin upgrade" once it has booted, rather than new images being produced every commit or day or something?

When starting in qemu I didn't really know what to expect. Turns out it leaves me without a graphical environment, and without a login-prompt. To try to figure out what's going on I had to mount the qcow2 image and edit the boot parameters to include console=.. which together with "-serial stdio" to qemu gives you a loginprompt in the terminal that launches qemu.

By now I was able to login, and see that wayland seems to be started, and after some googling I found that to get gdm up I needed to start qemu with "-vga std" instead of relying on the default.

Now gdm started, and I was greeted by a list of no users, after adding a user via the serial access and restarting gdm I could now finally login, except that nothing happens, just the grey gdm background all over the screen, for what seems likely to be, forever... so that leaves me stuck.

So what's the suggested way of doing all of this? It feels like I'm bruteforcing something that ought to have a clear path.

Is using the GNOME Continous images a good way to have access to the latest GNOME build environment, or is it meant to be used only for the automated testing the C-I infrastructure applies?

Is the kernel kdbus-patched?

Another question that popped up is if this is possible to run all of this via systemd-nspawn, as a more lightweight solution. I found some hacky suggestions about changing the host kernel parameters, but I'm hoping those suggestions are somewhat dated by now.

--
Daniel Svensson
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Matthias Clasen | 21 Feb 22:31 2015
Picon

GNOME 3.15.90

Hi all,

a few days late, but here it is: GNOME 3.15.90 is now available.

This is the first beta release of the 3.15 development, and it is a big release.
All of the big features that we have been working on have made it into this
release, in more or less complete form:
 * A new GNOME shell theme
 * Redesigned notifications in GNOME shell
 * Codec installation integrated in gnome-software
 * Login screen on Wayland
 * New UI in eog
 * UI improvements in nautilus
and many more.

To compile GNOME 3.15.90, you can use the jhbuild [1] modulesets [2]
(which use the exact tarball versions from the official release).

We are working on fixing the creation of vm images by our continous integration
infrastructure, build.gnome.org [3], so that you can again use these as another
way of testing the latest code.

[1] http://library.gnome.org/devel/jhbuild/
[2] http://download.gnome.org/teams/releng/3.15.90/
[3] https://wiki.gnome.org/Projects/GnomeContinuous#Installation

The release notes that describe the changes between 3.15.4 and 3.15.90
are available. Go read them to learn what's new in this release:

core - http://download.gnome.org/core/3.15/3.15.90/NEWS
apps - http://download.gnome.org/apps/3.15/3.15.90/NEWS

The GNOME 3.15.90 release itself is available here:

core sources - http://download.gnome.org/core/3.15/3.15.90
apps sources - http://download.gnome.org/apps/3.15/3.15.90

WARNING! WARNING! WARNING!
--------------------------

This release is a snapshot of early development code. Although it is
buildable and usable, it is primarily intended for testing and hacking
purposes. GNOME uses odd minor version numbers to indicate development
status.

For more information about 3.15, the full schedule, the official
module lists and the proposed module lists, please see our 3.15
planning page:
http://www.gnome.org/start/unstable

For a quick overview of the GNOME schedule, please see:
http://live.gnome.org/Schedule

Regards,
--
Matthias Clasen
GNOME Release Team
--

-- 
devel-announce-list mailing list
devel-announce-list <at> gnome.org
https://mail.gnome.org/mailman/listinfo/devel-announce-list

Matthias Clasen | 21 Feb 02:21 2015
Picon

3.15.90 status update

Hey,

sorry we are a bit delayed with 3.15.90. We were waiting for
gnome-shell features to land. Thankfully that has now happened, and
all the 'must have' tarballs for 3.15.90 are in, which means we'll
have the release out soon.

While starting the release preparations, I noticed a few modules that
could do with a tarball release. If you own one of these, maybe you
want to do a release now to make sure we'll pick it up for .91:

epiphany
gnome-calculator
seahorse
glade
polari

Thanks, Matthias
Federico Mena Quintero | 16 Feb 16:41 2015
Picon

Librsvg 2.40.7 is released

Dear lovers of smooth vectors,

As I announced in [1], I've taken over the maintainership of librsvg.
There is cool stuff going on in this release!

Atte Kettunen, of the Oulu University Secure Programming Group, has been
doing fuzz testing of librsvg, and some very interesting bugs are
appearing.  I've been fixing them, and this release contains the first
batch of fixes.

Librsvg 2.40.7 is available at

  https://download.gnome.org/sources/librsvg/2.40/

sha256sum:
62fdd5feb49a3fef923e0c847d1d186a99f180927ff91b0fe89c5d1b27c53240
librsvg-2.40.7.tar.bz2

65e4ca71f1cc13bda9f22bd49c62032458fd9f5df5595b3bf2a078947ec0cb89  librsvg-2.40.7.news
935ffb7a04bcb85b0bca149272dc33fe4d460464bb8fff0e2b16fe308ad6ff35  librsvg-2.40.7.changes
6ecb7ae2f75408f0c046166f327e50cefc57eb874e3c7ba43cd4daa10d5a0501  librsvg-2.40.7.tar.xz

Changes in this release:

- Bugs fixed from fuzz testing: #703102, #738050, #738169, #744270,
#744299
- Fixed unfiled bug from fuzz testing, where the convolution filter
  had an integer multiplication overflow.
- Fix build of rsvg-convert on Windows.
- Fix a bunch of compiler warnings.

[1] https://people.gnome.org/~federico/news-2015-02.html#10

Enjoy!

  Federico

_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Olav Vitters | 13 Feb 16:51 2015
Picon

Killing off UNCONFIRMED in Bugzilla

With Bugzilla 4.4 we can disable UNCONFIRMED on a per-product basis.
With that option available, I suggest to kill off the UNCONFIRMED status
for all products except whomever wants it. I think we had this
discussion before, but couldn't easily find that.

Reasoning to kill unconfirmed:
Unconfirmed at various times gives the impression the bug will not be
looked at. Not having this state would solve that.

Action required:
  IF YOU WANT TO KEEP UNCONFIRMED FOR YOUR PRODUCT PLEASE SPEAK UP!!

Steps (for all products except the ones opting out):
- Change "use unconfirmed" to false (product specific setting)
- Mass change all unconfirmed bugs to new for all

Timeline:
I want to do this Friday 27 February 2015.

--

-- 
Regards,
Olav
Colin Walters | 13 Feb 00:59 2015

Planning to deprecate libgsystem, introduce libgsystem2 as git submodule

I've updated this page:

https://wiki.gnome.org/Projects/LibGSystem

libgsystem has already become Linux specific (reading symlink xattrs from /proc), and I'd like to make it
even more so (some container APIs).  

gnome-desktop used to depend on it, but with this bug:
https://bugzilla.gnome.org/show_bug.cgi?id=708453
doesn't any more.

Further, GLib now has the cleanup macros:
https://bugzilla.gnome.org/show_bug.cgi?id=743640
As well as GSubprocess.

Another major chunk of libgsystem is the file utilities.  However, I've
been backing away from using GFile * in my code, which operates
quite a lot on files.  The two primary reasons are:
 - Doing atomic operations and malloc() just to interact with the
   filesystem sucks
 - Inability to make use of openat() and friends, which provide speed
   and security benefits

So my high level plan is to make a "libgsystem2" which is
explicitly Linux specific and drops most of the GFile* stuff,
and it will return to being a git submodule - shared among consumers
like ostree/rpm-ostree, NetworkManager, xdg-app, libhif/PackageKit,
and anything else that uses glib and is Linux specific.

There are a few other things like GSConsole in libgsystem that I
never really pushed forward into GLib, but that API didn't really
work out anyways.

Speak now if you have any thoughts, objections, or just want to see your name in the mailing list archives.
Release Team | 13 Feb 01:00 2015
Picon

GNOME 3.15.90 beta tarballs due (and more)

Hello all,

We would like to inform you about the following:
* GNOME 3.15.90 beta tarballs due
* API/ABI, UI and Feature Addition Freeze; String Change Announcement Period
* New APIs must be fully documented
* Writing of release notes begins

Tarballs are due on 2015-02-16 before 23:59 UTC for the GNOME 3.15.90
beta release, which will be delivered on Wednesday. Modules which were
proposed for inclusion should try to follow the unstable schedule so
everyone can test them.  Please make sure that your tarballs will be
uploaded before Monday 23:59 UTC: tarballs uploaded later than that
will probably be too late to get in 3.15.90. If you are not able to
make a tarball before this deadline or if you think you'll be late,
please send a mail to the release team and we'll find someone to roll
the tarball for you!

New APIs must be fully documented

Writing of release notes begins

For more information about 3.15, the full schedule, the official
module lists and the proposed module lists, please see our colorful 3.15
page:
   http://www.gnome.org/start/unstable

For a quick overview of the GNOME schedule, please see:
   https://wiki.gnome.org/Schedule

Thanks,
-- 
Automatically generated email. Source at:
https://git.gnome.org/browse/releng/tree/tools/schedule/automail.py
--

-- 
devel-announce-list mailing list
devel-announce-list <at> gnome.org
https://mail.gnome.org/mailman/listinfo/devel-announce-list

Marina Zhurakhinskaya | 12 Feb 06:25 2015
Picon

GSoC 2015 call for ideas

Dear GNOME hackers,

It's that time of the year again: Google Summer of Code is approaching. We've updated our program pages [1]
to have the latest information and we need your help in creating a list of great project ideas. It's
essential that we have a well-prepared ideas page when GNOME applies as a mentoring organization by next
Friday, February 20.

So what should you do? Please visit the ideas page [2] and enter your project ideas under the "Untriaged
Ideas" section.

 * Discuss your ideas with designers in #gnome-design to get their input and plan collaboration,
especially if your ideas are related to one of the core GNOME modules. If you are not sure who to speak to,
start with Allan Day (aday).
 * Consider manageable ideas consisting of multiple smaller features that share a common theme, in
addition to single large feature ideas. See the information for mentors page [3] for more on preferred
project formats and other mentoring resources.

If you are interested in being a mentor this year or at any point find yourself drafted to be one, please join
soc-mentors-list [4] to receive future communications about GNOME's participation in GSoC, including
the information about important deadlines.

The GNOME administrators for GSoC participation this year are Alexandre Franke, Christophe Fergeau,
Ekaterina Gerasimova, Lasse Schuirmann, and Marina Zhurakhinskaya. Big thank you to Fabiano Fidencio,
who was an administrator for the last two years! Welcome to Lasse Schuirmann, who was a GSoC participant
last year!

Cheers,
The GNOME Google Summer of Code Administrators

[1] https://wiki.gnome.org/Outreach/SummerOfCode/2015
[2] https://wiki.gnome.org/Outreach/SummerOfCode/2015/Ideas
[3] https://live.gnome.org/Outreach/SummerOfCode/Mentors
[4] https://mail.gnome.org/mailman/listinfo/soc-mentors-list
Aydin K. | 12 Feb 01:53 2015
Picon

switching applications

Hello. 

1. I switch to another workspace and this workspace has more then one application. Then when i switch applications with shortcut "switch applications" (quick pressing, without opening switcher meny) it switches to applications that is in another workspace. Would it not make more sense to make it switch between applications on the same workspace? 

2. There is no option to assign shortcut directly to typing language. And i have to cycle throw all the languages installed (i have four).

Thank you.

ayd
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Gmane