** Description changed: 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)! + 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 - ?? () - ?? () - ?? () + ?? () + 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
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1158969 Title: signon-ui crashed with SIGSEGV in QObject::connect() Status in “signon-ui” package in Ubuntu: Fix Released Status in “signon-ui” source package in Raring: Confirmed 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1158969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
