** No longer affects: whoopsie-daisy (Ubuntu)
** No longer affects: whoopsie-daisy (Ubuntu Precise)
** No longer affects: whoopsie-daisy (Ubuntu Quantal)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs
the fix is in the current glib, and was not a whoopsie issue
** Changed in: glib2.0 (Ubuntu Quantal)
Status: Fix Committed => Fix Released
** Changed in: whoopsie-daisy (Ubuntu Precise)
Status: Confirmed => Invalid
** Changed in: whoopsie-daisy (Ubuntu Quantal)
Status: Confi
** Changed in: glib2.0 (Ubuntu Quantal)
Milestone: quantal-alpha-2 => quantal-alpha-3
** Changed in: whoopsie-daisy (Ubuntu Quantal)
Milestone: quantal-alpha-2 => quantal-alpha-3
** Changed in: whoopsie-daisy (Ubuntu Precise)
Milestone: None => ubuntu-12.04.1
--
You received this bu
This bug was fixed in the package glib2.0 - 2.32.3-0ubuntu1
---
glib2.0 (2.32.3-0ubuntu1) precise-proposed; urgency=low
* New upstream version
* debian/patches/git_powerpc_gresources.patch:
- dropped, the fix in the new version
[ Evan Dandrea ]
* gnetworkmonitor_dont_leak
Left the same system running with the new glib package running overnight
- whoopsie is at 3Mb RES after 11 hours (earlier it would go to 100Mb
and beyond).
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubun
** Changed in: whoopsie-daisy (Ubuntu)
Milestone: quantal-alpha-1 => quantal-alpha-2
** Changed in: glib2.0 (Ubuntu)
Milestone: quantal-alpha-1 => quantal-alpha-2
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubun
Hello Roman, or anyone else affected,
Accepted glib2.0 into precise-proposed. The package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
The previous summary is basically the diff between the versions (add the
patch Evan backported), what strategy the SRU team suggest to get that
update in?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.
summary of the changes
small bug fixes, including (which we would probably backport):
* "GSocketControlMessage: Don't warn about unknown messages"
http://git.gnome.org/browse/glib/commit/?h=glib-2-32&id=9b1a9ed4ce326d4ebfca68b2a98ddb4d8110e5e7
* "gmain: block child sources when blocking the paren
** Changed in: glib2.0 (Ubuntu Precise)
Milestone: None => ubuntu-12.04.1
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/998521
Title:
whoopsie process is leaking memory
To ma
Excerpts from Sebastien Bacher's message of 2012-05-31 08:54:24 UTC:
> Clint, on the diff when filtering out "noise":
>
> $ debdiff --exclude *win32* --exclude tests* --exclude Makefile.in --exclude
> po --exclude docs --exclude ChangeLog --exclude configure --exclude
> *generated* glib2.0_2.32.
Clint, on the diff when filtering out "noise":
$ debdiff --exclude *win32* --exclude tests* --exclude Makefile.in --exclude po
--exclude docs --exclude ChangeLog --exclude configure --exclude *generated*
glib2.0_2.32.1-0ubuntu2.dsc glib2.0_2.32.3-0ubuntu1.dsc | diffstat
...
INSTALL
Clint:
you can see the details of the commits on
http://git.gnome.org/browse/glib/log/?h=glib-2-32
summary of the .news:
* GApplication: can now have a NULL application ID
* g_clear_object: fix warnings when using it on C++ (due to lack of
ability to implicitly cast void*)
* GDBus:
- add ou
This is a huge diff, not just "a few minor changes" IMO. Its sort of
shocking that glib adds so much in a a few "patch" releases. I know some
of these things are for non-Linux platforms, but its really quite hard
to separate them out.
If this is just a one line fix, why aren't we just cherry picki
** Changed in: glib2.0 (Ubuntu Precise)
Status: Confirmed => Fix Committed
** Changed in: glib2.0 (Ubuntu Precise)
Importance: Undecided => High
** Changed in: whoopsie-daisy (Ubuntu Precise)
Importance: Undecided => High
** Description changed:
+ Impact: stable update from the ups
** Attachment removed: "var-crash.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/whoopsie-daisy/+bug/998521/+attachment/3150516/+files/var-crash.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://b
I've rejected the current glib2.0 in the queue so that the full upstream
stable SRU can go through more easily.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/998521
Title:
whoopsi
Indeed. And apologies, I hadn't seen your reply to this bug and went
ahead and uploaded it to -proposed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/998521
Title:
whoopsie proce
** Changed in: whoopsie-daisy
Status: Unknown => Fix Released
** Changed in: whoopsie-daisy
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/998
The bug has been fixed upstream:
http://git.gnome.org/browse/glib/commit/?id=17e95c59c9f7b1cd023aabb3645c70b9f1f37577
Setting "fix commited" for quantal since that's going to be included in
the next version, we will also include the fix in the glib SRU that
should be uploaded next week to precise
** Branch linked: lp:~ubuntu-desktop/glib/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/998521
Title:
whoopsie process is leaking memory
To manage notifications about this
The main leak there seems to be:
==12580== 10,059,776 bytes in 9,557 blocks are definitely lost in loss record
1,071 of 1,074
==12580==at 0x4C2B7B2: realloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==12580==by 0x541DAF6: g_realloc (gmem.c:224)
==12580==by 0x53ECC67: g
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: whoopsie-daisy (Ubuntu)
Status: Confirmed => Invalid
** Changed in: glib2.0 (Ubuntu)
Importance: Undecided => High
** Changed in: glib2.0 (Ubuntu)
Status: New => Confirmed
** Changed in
23 matches
Mail list logo