Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#52199 - [pcsxr] Crash on starting game
Attached to Project:
Community Packages
Opened by Constantine (Hi-Angel) - Sunday, 18 December 2016, 13:11 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 27 August 2018, 17:31 GMT
Opened by Constantine (Hi-Angel) - Sunday, 18 December 2016, 13:11 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 27 August 2018, 17:31 GMT
|
DetailsDescription:
Running a game results in an immediate crash: $ pcsxr Gtk-Message: Failed to load module "canberra-gtk-module" Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. [1] 24371 segmentation fault (core dumped) pcsxr system log has more info on that: 18 14:57:23 constantine-N61Ja kernel: [27932.011833] traps: pcsxr[24371] general protection ip:808d099 sp:ffc5e89c error:0 in pcsxr[8048000+9d000] Additional info: * package version(s) pcsxr 1.9.93-5 The crash might be circumwented by setting in ~/.pcsxr/pcsxr.cfg the Cpu from "0" to "1". I believe it's somehow related to https://bugs.launchpad.net/ubuntu/+source/pcsxr/+bug/1504834 and they say the fix release, though I'm not sure where. Given that the latest pcsxr is 1.9.93 since 2013, whilst they have 1.9.94 version, I guess Ubuntu are using some patch of their own. Steps to reproduce: * Open a game, and see an immediate crash |
This task depends upon
Closed by Doug Newgard (Scimmia)
Monday, 27 August 2018, 17:31 GMT
Reason for closing: Won't fix
Additional comments about closing: Dropped to AUR
Monday, 27 August 2018, 17:31 GMT
Reason for closing: Won't fix
Additional comments about closing: Dropped to AUR
The packaged version didn't have that problem, it's a new bug.
I guess it has something to do with build options, like "-fno-stack-protector", but I'm not sure, neither I know what to report upstream given that address sanitizer was quiet.
In file included from /usr/lib/glib-2.0/include/glibconfig.h:9:0,
from /usr/include/glib-2.0/glib/gtypes.h:32,
from /usr/include/glib-2.0/glib/galloca.h:32,
from /usr/include/glib-2.0/glib.h:30,
from /usr/include/gtk-3.0/gdk/gdkconfig.h:13,
from /usr/include/gtk-3.0/gdk/gdk.h:30,
from /usr/include/gtk-3.0/gtk/gtk.h:30,
from LnxMain.c:30:
/usr/include/glib-2.0/glib/gtypes.h: In function '_GLIB_CHECKED_ADD_U64':
/usr/include/glib-2.0/glib/gmacros.h:232:53: error: size of array '_GStaticAssertCompileTimeAssertion_0' is negative
Thinking of orphaning this one.