Segfault (core dumped) in gdk-pixbuf on upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdk-pixbuf |
Fix Released
|
Medium
|
|||
gdk-pixbuf (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[ Description ]
In the Raring cycle, libgobject gained a global constructor.
If a dynamically loaded module (by gdk-pixbuf-
This can easily happen in dist-upgrades if you get unlucky with the ordering.
[ Proposed fix ]
Build with -Wl,--no-as-needed to ensure we get linked against libgobject even though we use none of its symbols.
In later glib & gdk-pixbuf releases, there's a function g_type_ensure() which is used for this purpose, but we don't have that in 12.04.
[ Development Fix ]
Described above: g_type_ensure() is used.
[ Regression potential ]
Not sure. The library will now be linked against more things so it could be a bit slower to initialise.
[ QA ]
1. Be in a precise chroot without precise-proposed
2. apt-get install libgdk-pixbuf2.0-0
3. sed -i 's/precise/trusty/' /etc/apt/
4. apt-get update
5. apt-get install libglib2.0-0
6. /usr/lib/
# that should have segfaulted
7. echo 'deb http://
8. apt-get update
9. apt-get install libgdk-
10. /usr/lib/
# that should have worked
[ Original description ]
In two machines I had errors in the upgrade from Precise to Raring.
Preparing to replace librsvg2-2:i386 2.36.3-0ubuntu1 (using .../librsvg2-
Unpacking replacement librsvg2-2:i386 ...
Processing triggers for libgdk-
Segmentation fault (core dumped)
Processing triggers for libgdk-
Segmentation fault (core dumped)
Setting up librsvg2-2:i386 (2.36.4-1) ...
Setting up librsvg2-2:amd64 (2.36.4-1) ...
Setting up librsvg2-
Setting up librsvg2-
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Processing triggers for libgdk-
Segmentation fault (core dumped)
Processing triggers for libgdk-
Segmentation fault (core dumped)
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
I guess that due to that error, the gdk-pixbuf-
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: libgdk-pixbuf2.0-0 2.28.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.5.0-27-generic x86_64
NonfreeKernelMo
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Mon Apr 29 12:17:40 2013
InstallationDate: Installed on 2009-11-25 (1251 days ago)
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MarkForUpload: True
SourcePackage: gdk-pixbuf
UpgradeStatus: Upgraded to raring on 2013-04-29 (0 days ago)
Related branches
summary: |
- Segfault (core dumped) during upgrade 12.10 to 13.04 + Segfault (core dumped) in gdk-pixbuf on upgrade |
information type: | Public → Public Security |
information type: | Public Security → Public |
Changed in gdk-pixbuf (Ubuntu): | |
importance: | Undecided → High |
description: | updated |
Changed in gdk-pixbuf (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in gdk-pixbuf (Ubuntu Precise): | |
status: | New → In Progress |
Changed in gdk-pixbuf: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.