Miro froze up while watching it.

Bug #1134841 reported by Roy H Huddleston
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
miro (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

The screen froze up while Miro was adding more to watch. Using Miro 4.0.4-1 on Raring Ringtail Lubuntu 13.04 Cadence Week 7 / Ubuntu Global Jam version.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: miro 4.0.4-1
ProcVersionSignature: Ubuntu 3.8.0-7.16-generic 3.8.0
Uname: Linux 3.8.0-7-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.8-0ubuntu4
Architecture: i386
Date: Wed Feb 27 15:34:07 2013
ExecutablePath: /usr/bin/miro.real
InstallationDate: Installed on 2013-02-17 (9 days ago)
InstallationMedia: Lubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130128)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
ProcCmdline: /usr/bin/python /usr/bin/miro.real
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: miro
UpgradeStatus: Upgraded to raring on 2013-02-25 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Roy H Huddleston (archspader) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0xb1e6b2b9 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbf96e3c0
StacktraceSource: #0 0xb1e6b2b9 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 19 (LWP 15578):
 #0 0xb7757424 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xa93d56c4

Changed in miro (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libgcc1 version 1:4.7.2-22ubuntu2 required, but 1:4.7.2-22ubuntu1 is available
outdated debug symbol package for libfftw3-3: package version 3.3.3-2ubuntu1 dbgsym version 3.3.2-3.1ubuntu1
libstdc++6 version 4.7.2-22ubuntu2 required, but 4.7.2-22ubuntu1 is available
libgomp1 version 4.7.2-22ubuntu2 required, but 4.7.2-22ubuntu1 is available
gcc-4.7-base version 4.7.2-22ubuntu2 required, but 4.7.2-22ubuntu1 is available

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

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.