System information:
* Release: Ubuntu 14.04 LTS
* Package version: Mupen64plus 2.0+1 0
Crash information
1. problem occured just 2 days ago, recently
2. Any video plugin set to 'Fullscreen=True` crashes mupen64plus regardless of
width/height specification in config file
3. This occurs with any game I try
4. command used was 'mupen64plus /home/test/my_game.v64`
Please requesty any information not in the apport crash collection and I will
report it here.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: mupen64plus-ui-console 2.0-1
Uname: Linux 3.14.0-031400-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Aug 12 06:50:18 2014
ExecutablePath: /usr/games/mupen64plus
ExecutableTimestamp: 1373087866
InstallationDate: Installed on 2014-08-09 (2 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: mupen64plus /home/test/RetroRig/ROMs/N64/Mario\ Kart\ 64.v64
ProcCwd: /var/crash
SegvAnalysis:
Segfault happened at: 0x7f18d3d6d216 <ViStatusChanged+38>: mov (%rdi),%rax
PC (0x7f18d3d6d216) ok
source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mupen64plus-ui-console
StacktraceTop:
ViStatusChanged () from /usr/lib/x86_64-linux-gnu/mupen64plus/mupen64plus-video-rice.so
?? ()
?? ()
CoreDoCommand () from /usr/lib/x86_64-linux-gnu/libmupen64plus.so.2
__bss_start ()
Title: mupen64plus crashed with SIGSEGV in ViStatusChanged()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
StacktraceTop:
ViStatusChanged () at ../../src/Video.cpp:785
?? ()
?? ()
add_breakpoint_struct (newbp=0x140) at ../../src/debugger/dbg_breakpoints.c:54
DebugBreakpointCommand (command=<optimized out>, index=3781498672, ptr=0x140) at ../../src/api/debugger.c:363
Original issue reported on code.google.com by conc...@web.de on 12 Aug 2014 at 4:26
Original issue reported on code.google.com by
conc...@web.deon 12 Aug 2014 at 4:26Attachments: