Ubuntu
signon-ui package

signon-ui crashed with SIGSEGV in QObject::connect()

Bug #1158969 reported by Marco
66
This bug affects 15 people
Affects Status Importance Assigned to Milestone
signon-ui (Ubuntu)
Fix Released
Medium
Unassigned
Raring
Won't Fix
Medium
Unassigned
Ubuntu raring-updates

Bug Description

crash when i don't grant access to google account

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: signon-ui 0.14-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
Uname: Linux 3.8.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu2
Architecture: amd64
Date: Fri Mar 22 21:17:22 2013
Disassembly: => 0x7f5900000001: Cannot access memory at address 0x7f5900000001
ExecutablePath: /usr/bin/signon-ui
InstallationDate: Installed on 2013-01-10 (70 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130110)
MarkForUpload: True
ProcCmdline: /usr/bin/signon-ui
SegvAnalysis:
 Segfault happened at: 0x7f5900000001: Cannot access memory at address 0x7f5900000001
 PC (0x7f5900000001) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: signon-ui
StacktraceTop:
 ?? ()
 QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 ?? ()
 ?? ()
 ?? ()
Title: signon-ui crashed with SIGSEGV in QObject::connect()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Additional information for the SRU request:

[Impact] Apparently random crashes of signon-ui when creting or re-authenticating accounts.

[Test Case] Open Online Accounts, click on "Add account", choose "Google", then press "Cancel", then "Add account" and "Google" again. This sequence of operations might lead to a crash.

[Regression Potential] The fix is entirely in the signon-ui process and consists of removing a widget pointer from a hash table when the widget itself is destroyed. Failing to do this was causing this bug, because signon-ui would try to use a destroyed widget.
The patch itself does not touch other code paths than this, and we've been using it in saucy without noticing any regressions.

The actual patch fixing this is http://bazaar.launchpad.net/~online-accounts/signon-ui/trunk/revision/86

See original description

Related branches

lp:signon-ui
Revision history for this message
Marco (0m3g4) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 QObject::connect (sender=0x2537960, signal=0x429ac0 "2error(QX11EmbedWidget::Error)", receiver=0x249b5a0, method=0x4299b2 "1onEmbedError()", type=Qt::UniqueConnection) at kernel/qobject.cpp:2550
 SignOnUi::RequestPrivate::setWidget (this=0x249b5a0, widget=0x25fb9d0) at request.cpp:141
 SignOnUi::BrowserRequestPrivate::start (this=0x2453ba0) at browser-request.cpp:540
 SignOnUi::ServicePrivate::runQueue (this=this@entry=0x246acc0, queue=...) at service.cpp:107

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in signon-ui (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in signon-ui (Ubuntu):
status: New → Confirmed
Ken VanDine (ken-vandine)
information type: Private → Public
Ken VanDine (ken-vandine)
Changed in signon-ui (Ubuntu Raring):
status: New → Confirmed
importance: Undecided → Medium
milestone: none → raring-updates
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package signon-ui - 0.14-0ubuntu2

---------------
signon-ui (0.14-0ubuntu2) saucy; urgency=low

  [ Alberto Mardegan ]
  * Fix a crash potentially happening when the XEmbed container reused the
    same X window ID from a previous one. (LP: #1158969)
  * Fixed Cannot log in to Google apps domain + Ubuntu SSO (LP: #1171853)
 -- Ken VanDine <email address hidden> Wed, 29 May 2013 10:37:43 -0400

Changed in signon-ui (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Missing SRU information

Thanks for uploading the fix for this bug report to -proposed. However, when reviewing the package in -proposed and the details of this bug report I noticed that the bug description is missing information required for the SRU process. You can find full details at http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially this bug is missing some of the following: a statement of impact, a test case and details regarding the regression potential. Thanks in advance!

Alberto Mardegan (mardy)
description: updated
Revision history for this message
Rolf Leggewie (r0lf) wrote :

raring has seen the end of its life and is no longer receiving any updates. Marking the raring task for this ticket as "Won't Fix".

Changed in signon-ui (Ubuntu Raring):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.