signon-ui crashed with SIGSEGV in QObject::event()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
signon-ui (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Attempting to add a Flickr account. I don't actually know my Flickr password, if I have one, as I always sign in using my Google account. However, the steps I took were:
1. Open Online Accounts
2. Select Add account...
3. Select Flickr
4. In the login page that opens, click Login using SSL
5. In the new login page that opens, click in the Yahoo! ID field
This isn't reproducible every time, but I've seen it happen three times today.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: signon-ui 0.15daily13.
ProcVersionSign
Uname: Linux 3.11.0-1-generic x86_64
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
CheckboxSubmission: dd3689fa6394f60
CheckboxSystem: b633b4f40868d49
Date: Thu Aug 15 14:25:02 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/signon-ui
InstallationDate: Installed on 2010-08-23 (1087 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
MarkForUpload: True
ProcCmdline: /usr/bin/signon-ui
SegvAnalysis:
Segfault happened at: 0x7f5f3519c8cb: mov 0x28(%rdi),%r12d
PC (0x7f5f3519c8cb) ok
source "0x28(%rdi)" (0x00000028) not located in a known VMA region (needed readable region)!
destination "%r12d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: signon-ui
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
QObject:
Title: signon-ui crashed with SIGSEGV in QObject::event()
UpgradeStatus: Upgraded to saucy on 2013-08-11 (3 days ago)
UserGroups: adm admin audio cdrom dialout disk floppy fuse libvirtd lpadmin netdev plugdev powerdev sambashare sudo vde2-net video
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1200957, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.