ubiquity crashed with SIGSEGV in dbus_message_unref()

Bug #1227006 reported by Mr-Liang on 2013-09-18

This bug report will be marked for expiration in 9 days if no further activity occurs. (find out why)

10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Undecided
Unassigned

Bug Description

I DON'T KNOW

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: ubiquity 2.15.16
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
CasperVersion: 1.336
Date: Wed Sep 18 16:57:24 2013
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- locale=zh_CN keyboard-configuration/layoutcode?=cn maybe-ubiquity
InterpreterPath: /usr/bin/python3.3
LiveMediaBuild: UbuntuKylin 13.10 "Saucy Salamander" - Alpha amd64 (20130903)
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --greeter --only
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=zh_CN.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f3b4235bc10: mov 0x8(%rdi),%rax
 PC (0x7f3b4235bc10) ok
 source "0x8(%rdi)" (0x00000009) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: ubiquity
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_message_unref () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
Title: ubiquity crashed with SIGSEGV in dbus_message_unref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Mr-Liang (liangzhijie611) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
information type: Private Security → Public
Simon Quigley (tsimonq2) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1227006

and any other logs that are relevant for this particular issue.

Changed in ubiquity (Ubuntu):
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers