gnome-control-center.real crashed with SIGSEGV in gtk_lock_button_set_permission()

[Fran Diéguez]

[Impact]
When starting deja-dup through the gnome-control-center it crashes. This is caused by an ABI break in libgnome-control-center. Which is an Ubuntu-ism, upstream dropped quite a while back.

[Test case]
Click Backups in gnome-control-center

[Regression potential]
Low, this is just a simple rebuild to pick up the new ABI in libgnome-control-center. It will cause the libunity-control-center plugin to also be rebuilt but there were no changes there, so that should be fine.

=== Original Report ====

g-c-c 3.14 crashes when loading the Backup panel
(This also affects 3.12 in utopic)

ProblemType: CrashDistroRelease: Ubuntu 14.10
Package: gnome-control-center 1:3.14.0-1ubuntu1~utopic1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
Uname: Linux 3.16.0-21-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Thu Oct 9 19:30:35 2014
ExecutablePath: /usr/bin/gnome-control-center.real
InstallationDate: Installed on 2014-09-19 (20 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140917)
ProcCmdline: /usr/bin/gnome-control-center.real --overview
SegvAnalysis:
 Segfault happened at: 0x7faac2be3743 <gtk_lock_button_set_permission+99>: cmp %rax,(%rdx)
 PC (0x7faac2be3743) ok
 source "%rax" ok
 destination "(%rdx)" (0x6a65643a706c6568) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMASignal: 11SourcePackage: gnome-control-center
StacktraceTop:
 gtk_lock_button_set_permission () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? ()
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center.real crashed with SIGSEGV in gtk_lock_button_set_permission()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
usr_lib_gnome-control-center: deja-dup 32.0-0ubuntu1

[Ubuntu GNOME (ug-bot)]

StacktraceTop:
 gtk_level_bar_add_offset_value (self=0x27302a0, name=0x7faa9719a85c "\004\003", value=1.3852388523421298e-309) at /build/buildd/gtk+3.0-3.14.1~git20140927.89c0522c/./gtk/gtklevelbar.c:1394
 ?? ()

[Tim Lunn (darkxst)]

This also affects g-c-c 3.12 in utopic

[Fran Diéguez (frandieguez)]

Fixed with latest updates in gnome3-staging

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Iain Lane (laney)]

Is this an ABI break?

[Tim Lunn (darkxst)]

Laney, yes an extra symbol got added in libgnome-control-center.

I suppose it should of had a soname but, however I might actually just drop the external panel patches this cycle, deja-dup is the only thing left using them. g-c-c-datetime seems to be still building the panel, but it won't actually be used.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[vaiopro (vaiopro-deactivatedaccount)]

when can we expect the patch to hit the gnome3 ppa and the stable release?

[Sebastien Bacher (seb128)]

Unsubscribing sponsor, the issue is fixed in vidid and there is no SRU information, please add those if you want a SRU to utopic

[Brian Murray (brian-murray)]

Hello Fran, or anyone else affected,

Accepted deja-dup into utopic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/deja-dup/32.0-0ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Tim Brooks (morphit2k)]

Works for me. I couldn't seem to get apt to fetch the new package from utopic-proposed, but I downloaded the new deb from https://launchpad.net/ubuntu/utopic/amd64/deja-dup/32.0-0ubuntu1.1 and used dpkg -i to install.

I can now open deja-dup from the settings panel. Thanks for the fix!

[Tim Lunn (darkxst)]

marking verification-done based on Tim's comment in #17

[Bruce Pieterse (octoquad)]

Works for me as well.

deja-dup:
  Installed: 32.0-0ubuntu2~utopic1
  Candidate: 32.0-0ubuntu2~utopic1
  Version table:
 *** 32.0-0ubuntu2~utopic1 0
        500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu/ utopic/main amd64 Packages
        100 /var/lib/dpkg/status
     32.0-0ubuntu1 0
        500 http://za.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages

[Launchpad Janitor (janitor)]

This bug was fixed in the package deja-dup - 32.0-0ubuntu1.1

---------------
deja-dup (32.0-0ubuntu1.1) utopic; urgency=medium

  * No change rebuild for ABI break in libgnome-control-center (LP: #1379446)
 -- Tim Lunn <email address hidden> Sat, 31 Jan 2015 09:00:30 +1100

[Adam Conrad (adconrad)]

The verification of the Stable Release Update for deja-dup has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.