miro.real crashed with SIGSEGV in __kernel_vsyscall()

Bug #178486 reported by aguy
34
Affects Status Importance Assigned to Milestone
miro (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: miro

Just start up miro using ubuntu heron 8.04 and the following error appears.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Dec 24 16:59:38 2007
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/miro.real
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: nvidia
Package: miro 1.0-1ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/bin/python /usr/bin/miro.real
ProcCwd: /home/asty
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: miro
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libpthread.so.0
 ?? () from /usr/lib/xulrunner-1.9b1/libxul.so
 ?? ()
 ?? ()
Title: miro.real crashed with SIGSEGV in __kernel_vsyscall()
Uname: Linux asty-desktop 2.6.24-2-generic #1 SMP Thu Dec 20 17:36:12 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
aguy (astyguy-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:__kernel_vsyscall ()
raise () from /lib/tls/i686/cmov/libpthread.so.0
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Shawn vega (svega85-gmail) wrote :

I have the same problem

Revision history for this message
aguy (astyguy-deactivatedaccount) wrote :

latest version now does

/usr/lib/firefox
before 3
INFO Starting up Miro
INFO Version: 1.0
INFO Revision: unknown
INFO Builder: buildd@vernadsky
INFO Build Time: 1197365180.86
INFO Loading preferences...
INFO Showing startup dialog...
INFO Starting event loop thread
INFO Restoring database...
INFO Connecting to /root/.miro/sqlitedb
TIMING Database load slow: 0.264
TIMING idle (Initializing database) too slow (0.580 secs)
INFO Spawning global feed dtv:manualFeed
INFO Spawning global feed dtv:singleFeed
INFO Spawning global feed dtv:search
INFO Spawning global feed dtv:searchDownloads
INFO Creating channel tab order
INFO Creating playlist tab order
INFO *** Launching Downloader Daemon ****
INFO Spawning Miro Guide...
INFO Adding default feeds
u'http://www.getmiro.com/screencasts/windows/win.feed.rss'
(u'Starter Channels', [u'http://richie-b.blip.tv/posts/?skin=rss', u'http://feeds.pbs.org/pbs/kcet/wiredscience-video', u'http://www.jpl.nasa.gov/multimedia/rss/podfeed-hd.xml', u'http://www.linktv.org/rss/hq/mosaic.xml'])
INFO Spawning global feed dtv:directoryfeed
INFO Spawning auto downloader...
INFO Displaying main frame...
WARNING Menu item action "RenameVideo" not implemented
WARNING Menu item action "FastForward" not implemented
WARNING Menu item action "Rewind" not implemented
WARNING Menu item action "UpVolume" not implemented
WARNING Menu item action "DownVolume" not implemented
INFO Creating video display...
INFO loaded renderer 'xinerenderer'
TIMING gtkAsyncMethod: <function initRenderers at 0x89fb56c> took too long: 14.235
TIMING gtkSyncMethod: <function getDisplay at 0x8a2387c> took too long: 15.079
INFO First URL is https://www.miroguide.com/firsttime
TIMING Icon clear: 0.006
INFO Starting movie data updates
WARNING Error setting up HTTP observer
Segmentation fault

Revision history for this message
Shawn vega (svega85-gmail) wrote :

ok i think this is fixed now just tried it with a fresh install of alpha 3

Revision history for this message
Adam Niedling (krychek) wrote :

This bug just happened for me using Hardy Beta.

Revision history for this message
Markus Golser (golserma) wrote :

Fixed on the final version

Changed in miro:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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