Hello Paul,
is the issue reproducible on a system you have on where you can get a
stacktrace?
I just tested on my Linux i386 laptop running Devuan with GCC runtime
(all source being GIT and compiled by myself, no packages) and I have no
issues with GWorkspace. So no immediate i386 32bit issue (which would be
also strange).
Thus we must understand what is happening at your place.
First thing I see is that the screenshot shows a different exception
than the one you describe. NSConstantString vs NSImage. Why? is it
random? or a different compilation run? This is probably a memory issue
somewhere.
We need a stacktrace.
We need to know how gnustep core and gworkspace is compiled. Do you have
PDFKit installed and is it enabled? did you enable GWMetadata?
Please open an issue on github for gworkspace for it if you want to
collaborate on this, so we can exhange discussion. It might be a core
bug or GWorkspace bug or a configuration problem.
Riccardo
Paul Seelig wrote:
Package: gworkspace.app
Version: 1.0.0-4
Severity: important
Tags: upstream
X-Debbugs-Cc: discuss-gnus...@gnu.org, wml...@sf.net, wml...@rumbero.org
Hello all,
the current gworkspace.app application for trixie/i386 shows following error
message when started:
"Uncaught exception NSInvalidArgumentException, reason: NSImage(instance) does
not recognize subviews"
and only leaves the option to "Abort" the application.
A screenshot is available at
http://wmlive.rumbero.org/NSInvalidArgumentException.png for a visual depiction
of the error message.
Running the same application version in both amd64 and arm64 doesn't show any
errors and works normally. So this issue appears to be limited to the i386
variant only.
Checking out and recompiling the current upstream sources from
https://github.com/gnustep/apps-gworkspace produces the same issue under i386.
Please let me know if need me to provide more information.
Thanks for maintaining this package!
Regards,
Paul
