Ubuntu
ubiquity package

ubiquity crashed with SIGSEGV

Bug #289651 reported by Yoshi_Matrix
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: ubiquity

this was he beta install four days before release

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InterpreterPath: /usr/bin/python2.5
Package: ubiquity 1.10.7
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity --only
ProcEnviron:
 LANGUAGE=
 PATH=/sbin:/bin:/usr/sbin:/usr/bin
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: ubiquity
StacktraceTop:
 ?? () from /usr/lib/libcairo.so.2
 ?? () from /usr/lib/libcairo.so.2
 ?? () from /usr/lib/libcairo.so.2
 ?? () from /usr/lib/libcairo.so.2
 ?? () from /usr/lib/libcairo.so.2
Title: ubiquity crashed with SIGSEGV
Uname: Linux 2.6.27-7-generic i686
UserGroups:

Tags: apport-crash
Revision history for this message
Yoshi_Matrix (yoshi-matrix) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:_cairo_box_round_to_rectangle (box=0xbff100a0, rectangle=0xbff1001c)
_clip_and_composite_trapezoids (src=0x901faf8, op=CAIRO_OPERATOR_OVER, dst=0x876ab38,
_cairo_surface_fallback_fill (surface=0x876ab38, op=CAIRO_OPERATOR_OVER, source=0x901faf8,
_cairo_surface_fill (surface=0x876ab38, op=CAIRO_OPERATOR_OVER, source=0xbff102a4, path=0x901f76c,
_cairo_gstate_fill (gstate=0x901f000, path=0x901f76c)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in ubiquity:
importance: Undecided → Medium
Andreas Olsson (andol)
visibility: private → public
Revision history for this message
Monkey (monkey-libre) 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 a current, supported, Ubuntu version. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 289651, and any other logs that are relevant for this particular issue.

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Monkey (monkey-libre) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

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

Other bug subscribers

Remote bug watches

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