Running Appimage logs me out and back to login screen on KDE

[Blad3forc3]

Describe the bug

When i run the appimage it automatically logs me out and back to the login screen

Expected behavior

PCSX-Redux just runs

Steps to reproduce the bug

1..Download appimage 2..Run appimage

Operating System

KDE Neon

CPU model

Intel Core I5

GPU model

Nvidia 1080Ti

BIOS version

Doesnt get this far

CPU emulation mode

Recompiler

Additional information

N/A

[wheremyfoodat]

Could you run Redux from a terminal with the flags -stdout -safe?

[Blad3forc3]

Running the appimage from the terminal with the flags produces the same

[nicolasnoble]

Well if it logs you out, it means your window manager and/or GPU driver crashed. While it's interesting that Redux causes this, a proper environment shouldn't just crash like this.

I would suggest cross filing a bug with your distribution vendor as its behavior isn't proper here. At best the application should exit, not crash your whole environment.

[nicolasnoble]

Also, could you maybe try and build it from source to see if it's the AppImage specifically that's doing this or Redux in general?

[Blad3forc3]

I have never had another app cause this problem. When i compile the source with the makefile it just errors straight away and when i compile with the docker it compiles but then wont run complaining about dependencies

On Mon, 30 May 2022, 17:32 Nicolas Noble, @.***> wrote:

Also, could you maybe try and build it from source to see if it's the AppImage specifically that's doing this or Redux in general?

— Reply to this email directly, view it on GitHub https://github.com/grumpycoders/pcsx-redux/issues/856#issuecomment-1141333100, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJOLIO5XEKGIXNEG3QU5UILVMTURFANCNFSM5XK4G2DQ . You are receiving this because you authored the thread.Message ID: @.***>

[wheremyfoodat]

What sort of errors do make/docker spit out?

[lorn10]

@Blad3forc3 Which Linux distro is used here? Kubuntu 22.04 LTS?

I have tested current PCSX-Redux build 91e3c8a6 under Kubuntu 20.04 LTS and everything is running fine. So I am unable to reproduce the problem described here.

Update: I have seen it now, KDE Neon, most likely current version 5.24.

[Blad3forc3]

KDE Neon and docker spits out no errors and i get a binary at the end but i get dependency errors when trying to run the binary Running make with gcc9 after cloning the repository gives me this error

g++: error: unrecognized command line option ‘-fcoroutines’ g++: error: unrecognized command line option ‘-fcoroutines’ g++: error: unrecognized command line option ‘-fcoroutines’ g++: error: unrecognized command line option ‘-fcoroutines’ make: *** No rule to make target 'src/spu/adsr.dep', needed by 'dep'. Stop.

Running make with gcc10 gives me this error compiling:

src/support/uvfile.h: In member function ‘virtual bool PCSX::UvFifo::failed()’: src/support/uvfile.h:217:60: error: ‘struct std::atomic_flag’ has no member named ‘test’ 217 | virtual bool failed() final override { return m_failed.test(); } | ^~~~ src/support/uvfile.h: In member function ‘bool PCSX::UvFifo::isConnecting()’: src/support/uvfile.h:218:47: error: ‘struct std::atomic_flag’ has no member named ‘test’ 218 | bool isConnecting() { return m_connecting.test(); } | ^~~~ In file included from src/support/version.h:31, from src/core/system.h:38, from src/support/settings.h:34, from src/core/psxemulator.h:43, from src/core/decode_xa.h:22, from src/spu/externals.h:32, from src/spu/adsr.h:29, from src/spu/spu.cc:99: src/support/uvfile.h: In member function ‘virtual bool PCSX::UvFifo::failed()’: src/support/uvfile.h:217:60: error: ‘struct std::atomic_flag’ has no member named ‘test’ 217 | virtual bool failed() final override { return m_failed.test(); } | ^~~~ src/support/uvfile.h: In member function ‘bool PCSX::UvFifo::isConnecting()’: src/support/uvfile.h:218:47: error: ‘struct std::atomic_flag’ has no member named ‘test’ 218 | bool isConnecting() { return m_connecting.test(); } | ^~~~ In file included from src/support/version.h:30, from src/core/system.h:38, from src/support/settings.h:34, from src/core/psxemulator.h:43, from src/core/decode_xa.h:22, from src/spu/externals.h:32, from src/spu/xa.cc:32: src/support/file.h: In destructor ‘virtual PCSX::File::~File()’: src/support/file.h:76:13: warning: ‘throw’ will always call ‘terminate’ [-Wterminate] 76 | throw std::runtime_error("File object used without IO<> wrapper despite being in one"); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ src/support/file.h:76:13: note: in C++11 destructors default to ‘noexcept’ In file included from src/support/version.h:30, from src/core/system.h:38, from src/support/settings.h:34, from src/core/psxemulator.h:43, from src/core/decode_xa.h:22, from src/spu/externals.h:32, from src/spu/registers.cc:46: src/support/file.h: In destructor ‘virtual PCSX::File::~File()’: src/support/file.h:76:13: warning: ‘throw’ will always call ‘terminate’ [-Wterminate] 76 | throw std::runtime_error("File object used without IO<> wrapper despite being in one"); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ src/support/file.h:76:13: note: in C++11 destructors default to ‘noexcept’ In file included from src/support/version.h:31, from src/core/system.h:38, from src/support/settings.h:34, from src/core/psxemulator.h:43, from src/core/decode_xa.h:22, from src/spu/externals.h:32, from src/spu/xa.cc:32: src/support/uvfile.h: In member function ‘virtual bool PCSX::UvFifo::failed()’: src/support/uvfile.h:217:60: error: ‘struct std::atomic_flag’ has no member named ‘test’ 217 | virtual bool failed() final override { return m_failed.test(); } | ^~~~ src/support/uvfile.h: In member function ‘bool PCSX::UvFifo::isConnecting()’: src/support/uvfile.h:218:47: error: ‘struct std::atomic_flag’ has no member named ‘test’ 218 | bool isConnecting() { return m_connecting.test(); } | ^~~~ In file included from src/support/version.h:31, from src/core/system.h:38, from src/support/settings.h:34, from src/core/psxemulator.h:43, from src/core/decode_xa.h:22, from src/spu/externals.h:32, from src/spu/registers.cc:46: src/support/uvfile.h: In member function ‘virtual bool PCSX::UvFifo::failed()’: src/support/uvfile.h:217:60: error: ‘struct std::atomic_flag’ has no member named ‘test’ 217 | virtual bool failed() final override { return m_failed.test(); } | ^~~~ src/support/uvfile.h: In member function ‘bool PCSX::UvFifo::isConnecting()’: src/support/uvfile.h:218:47: error: ‘struct std::atomic_flag’ has no member named ‘test’ 218 | bool isConnecting() { return m_connecting.test(); } | ^~~~ make: *** [Makefile:230: src/spu/adsr.o] Error 1 make: *** Waiting for unfinished jobs.... make: *** [Makefile:230: src/spu/spu.o] Error 1 make: *** [Makefile:230: src/spu/xa.o] Error 1 make: *** [Makefile:230: src/spu/registers.o] Error 1

[lorn10]

For the record, this here is definitely KDE Neon 5.24 specific. I am also unable to reproduce a problem under Kubuntu 22.04 LTS.

[nicolasnoble]

FWIW, it looks like KDE Neon is based on Ubuntu 20.04. In terms of Ubuntu LTS, this code requires at least 22.04 to compile properly. Using the AppImage is a great way to avoid dependency issues like those compilation errors, which unfortunately doesn't seem to be working for you at the moment.

You should definitely check your system logs to see why the window manager decided to crash.