ri-li crashed with SIGSEGV in __libc_start_main()

Bug #557226 reported by Tibor Papp
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ri-li (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: ri-li

1. Ubuntu-Netbook-Edition 10.04 LTS Beta verzio + installed the edubuntu-desktop + (KDE, Lubuntu, Xfce - desktop was above already )
2. ri - li data 2.0.1-2 // ri - li 2.0.1-2
3. I would have liked stepping out after a launch ( on a beginner screen ) with a closing button ( left, above x )
4. x freezing until short time, the program collapsed, it x in additional ones problem free

5. Sorry, that I sent it again, "chance" I deleted the previous announcement

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: ri-li 2.0.1-2
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
CheckboxSubmission: 0944bf3adb49a904b88af610e0c79ba7
CheckboxSystem: 5db121db1e4cce88e7e18a823a405fdd
CrashCounter: 1
Date: Wed Apr 7 13:11:27 2010
ExecutablePath: /usr/games/ri-li
ProcCmdline: ri-li
ProcEnviron:
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x8053513: mov 0x8(%eax),%ecx
 PC (0x08053513) ok
 source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: ri-li
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
Title: ri-li crashed with SIGSEGV in __libc_start_main()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Tibor Papp (papp13tibor) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #557151, 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.

visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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