Bug 30464 - Using alt-tab to switch the game runescape to another aplication the system crash and send me to login window
Summary: Using alt-tab to switch the game runescape to another aplication the system c...
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-23 17:18 CEST by Victor Rivero
Modified: 2023-07-20 02:37 CEST (History)
2 users (show)

See Also:
Source RPM: kernel-desktop-5.15.41-1.mga8-1-1.mga8
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Victor Rivero 2022-05-23 17:18:54 CEST 
Description of problem: When i use alt-tab to switch the game runescape to another application the system crash and send me to login window, i'm using the kernel 5.10.78, newer kernels has this problem.
Graphic controler (pc 1): Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Grapihc controler (pc 2): Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
module: i915 (both pc's)
Desktop: KDE

Version-Release number of selected component (if applicable): kernels 5.15.16 and newer


How reproducible:


Steps to Reproduce:
1.Using the game Runescape
2.use alt-tab to switch application
3.The system crash and send me to login window.
Comment 1 sturmvogel 2022-05-23 17:33:56 CEST 
Runescape is a 3rd party program which is not shipped in any Mageia repository.

(Already tending at this point to close this bugreport as INVALID)

Please provide syslogs/crashreports/console outputs when your system crashes. 

Please indicate also clearly which Kernel was in use when it happened.

Also please clarify kernel versions. You have thrown 3 kernel versions into the ring: 5.10.78, 5.15.16, kernel-desktop-5.15.41

Additional you do mention "both pc's". Please also clarify this point!
Comment 2 sturmvogel 2022-05-23 17:46:39 CEST 
Seems a common problem with Runescape even under Windows with recent hardware and also Android.

https://www.reddit.com/r/runescape/comments/nnreox/client_crash_after_alt_tab_on_full_screen/

https://secure.runescape.com/m=forum/forums?443,444,93,66089728

https://www.drivereasy.com/knowledge/how-to-fix-runescape-keeps-crashing/


I tend to close this as INVALID. Awaiting some feedback from others...
Comment 3 Victor Rivero 2022-05-23 18:55:01 CEST 
(In reply to sturmvogel from comment #1)
> Runescape is a 3rd party program which is not shipped in any Mageia
> repository.
> 
> (Already tending at this point to close this bugreport as INVALID)
> 
> Please provide syslogs/crashreports/console outputs when your system
> crashes. 
> 
> Please indicate also clearly which Kernel was in use when it happened.
> 
> Also please clarify kernel versions. You have thrown 3 kernel versions into
> the ring: 5.10.78, 5.15.16, kernel-desktop-5.15.41
> 
> Additional you do mention "both pc's". Please also clarify this point!

Yes, Runescape is a 3rd party program, the problem is that the kernel is crashing with this program, maybe the problem is not only the program, could be opengl, i had some problems with opengl and this program some times and the problem was solved when opengl was fixed.

Last kernel i can use without the problem is: kernel-desktop-5.10.78-1

this problem occurs in the following kernels: kernel-desktop-5.15.16-1., 
kernel-desktop-5.15.18-2, kernel-desktop-5.15.23-1, kernel-desktop-5.15.25-1, kernel-desktop-5.15.28-1, kernel-desktop-5.15.32-1, kernel-desktop-5.15.35-2, kernel-desktop-5.15.41-1

I'm looking for some ways to find reports because the system crash and i'm kicked to login window, then i lose all console outputs or anothers.

I have 2 pc's, 1 laptop and another desktop pc, both pc's show the same problem.
Comment 4 Victor Rivero 2022-05-23 20:09:58 CEST 
this is the output from:
journalctl --since "2022-05-23 12:56:00" --until "2022-05-23 12:58:23"

when the crash ocurrs:

-- Logs begin at Mon 2020-01-20 18:00:08 CST, end at Mon 2022-05-23 13:07:21 CDT. --
may 23 12:56:00 localhost acpid[790]: client connected from 3264[0:0]
may 23 12:56:00 localhost acpid[790]: 1 client rule loaded
may 23 12:56:12 localhost acpid[790]: client 3264[0:0] has disconnected
may 23 12:56:14 localhost acpid[790]: client connected from 3264[0:0]
may 23 12:56:14 localhost acpid[790]: 1 client rule loaded
may 23 12:56:22 localhost acpid[790]: client 3264[0:0] has disconnected
may 23 12:56:23 localhost acpid[790]: client connected from 3264[0:0]
may 23 12:56:23 localhost acpid[790]: 1 client rule loaded
may 23 12:56:29 localhost acpid[790]: client 3264[0:0] has disconnected
may 23 12:56:33 localhost acpid[790]: client connected from 3264[0:0]
may 23 12:56:33 localhost acpid[790]: 1 client rule loaded
may 23 12:56:39 localhost acpid[790]: client 3264[0:0] has disconnected
may 23 12:56:40 localhost acpid[790]: client connected from 3264[0:0]
may 23 12:56:40 localhost acpid[790]: 1 client rule loaded
may 23 12:56:46 localhost acpid[790]: client 3264[0:0] has disconnected
may 23 12:56:47 localhost acpid[790]: client connected from 3264[0:0]
may 23 12:56:47 localhost acpid[790]: 1 client rule loaded
may 23 12:56:59 localhost acpid[790]: client 3264[0:0] has disconnected
may 23 12:57:02 localhost acpid[790]: client connected from 3264[0:0]
may 23 12:57:02 localhost acpid[790]: 1 client rule loaded
may 23 12:57:18 localhost acpid[790]: client 3264[0:0] has disconnected
may 23 12:57:19 localhost acpid[790]: client connected from 3264[0:0]
may 23 12:57:19 localhost acpid[790]: 1 client rule loaded
may 23 12:58:07 localhost acpid[790]: client 3264[0:0] has disconnected
may 23 12:58:09 localhost acpid[790]: client connected from 3264[0:0]
may 23 12:58:09 localhost acpid[790]: 1 client rule loaded
may 23 12:58:13 localhost at-spi-bus-launcher[11749]: X connection to :0 broken (explicit kill or server shutdown).
may 23 12:58:13 localhost systemd[7683]: plasma-kglobalaccel.service: Succeeded.
may 23 12:58:17 localhost pulseaudio[10783]: X connection to :0 broken (explicit kill or server shutdown).
may 23 12:58:13 localhost acpid[790]: client 3264[0:0] has disconnected
may 23 12:58:17 localhost sddm[10586]: kwalletd5: Checking for pam module
may 23 12:58:17 localhost sddm[10586]: kwalletd5: Got pam-login param
may 23 12:58:17 localhost sddm[10586]: kwalletd5: Waiting for hash on 6-
may 23 12:58:17 localhost sddm[10586]: kwalletd5: waitingForEnvironment on: 3
may 23 12:58:17 localhost sddm[10586]: kwalletd5: client connected
may 23 12:58:17 localhost sddm[10586]: kwalletd5: client disconnected
may 23 12:58:13 localhost systemd[7683]: plasma-kglobalaccel.service: Consumed 3.349s CPU time.
may 23 12:58:13 localhost acpid[790]: client 3264[0:0] has disconnected
may 23 12:58:14 localhost systemd[7683]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE
may 23 12:58:15 localhost polkitd[1098]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.62, object path /org/kde/PolicyKit1/AuthenticationAgent, locale es_MX.UTF-8) (disconnected from bus)
may 23 12:58:14 localhost systemd[7683]: pulseaudio.service: Failed with result 'exit-code'.
may 23 12:58:15 localhost sddm-helper[10576]: pam_unix(sddm:session): session closed for user victor
may 23 12:58:14 localhost systemd[7683]: pulseaudio.service: Consumed 6.352s CPU time.
may 23 12:58:15 localhost sddm-helper[10576]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_close_session
may 23 12:58:14 localhost systemd[7683]: pulseaudio.service: Scheduled restart job, restart counter is at 1.
may 23 12:58:16 localhost acpid[790]: client connected from 16705[0:0]
may 23 12:58:14 localhost systemd[7683]: Stopped Sound Service.
may 23 12:58:16 localhost acpid[790]: 1 client rule loaded
may 23 12:58:14 localhost systemd[7683]: pulseaudio.service: Consumed 6.352s CPU time.
may 23 12:58:16 localhost acpid[790]: client connected from 16705[0:0]
may 23 12:58:14 localhost systemd[7683]: Starting Sound Service...
may 23 12:58:16 localhost acpid[790]: 1 client rule loaded
may 23 12:58:14 localhost klauncher[16709]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
                                            
                                            Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
may 23 12:58:16 localhost rtkit-daemon[814]: Successfully made thread 16703 of process 16703 owned by '1750' high priority at nice level -11.
may 23 12:58:16 localhost pulseaudio[16703]: Stale PID file, overwriting.
may 23 12:58:16 localhost rtkit-daemon[814]: Supervising 2 threads of 2 processes of 1 users.
may 23 12:58:16 localhost systemd[7683]: app-\x2fusr\x2fbin\x2fkate-787291dd7b554f8d8e0799a268f7e0ee.scope: Succeeded.
may 23 12:58:17 localhost sddm-helper[10576]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
may 23 12:58:16 localhost systemd[7683]: app-\x2fusr\x2fbin\x2fkate-787291dd7b554f8d8e0799a268f7e0ee.scope: Consumed 1.444s CPU time.
may 23 12:58:18 localhost rtkit-daemon[814]: Supervising 2 threads of 2 processes of 1 users.
may 23 12:58:17 localhost systemd-logind[835]: Session c2 logged out. Waiting for processes to exit.
may 23 12:58:18 localhost rtkit-daemon[814]: Successfully made thread 16725 of process 16703 owned by '1750' RT at priority 5.
may 23 12:58:18 localhost rtkit-daemon[814]: Supervising 3 threads of 2 processes of 1 users.
may 23 12:58:19 localhost pulseaudio[16703]: module-rescue-stream is obsolete and should no longer be loaded. Please remove it from your configuration.
may 23 12:58:19 localhost systemd[7683]: Started Sound Service.
may 23 12:58:19 localhost sddm[3176]: QProcess: Destroyed while process ("/usr/libexec/sddm-helper") is still running.
may 23 12:58:19 localhost sddm-helper[16744]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
may 23 12:58:19 localhost systemd[1]: Created slice User Slice of UID 988.
may 23 12:58:19 localhost systemd[1]: Starting User Runtime Directory /run/user/988...
may 23 12:58:19 localhost systemd-logind[835]: New session c3 of user sddm.
may 23 12:58:19 localhost systemd[1]: Finished User Runtime Directory /run/user/988.
may 23 12:58:19 localhost systemd[1]: Starting User Manager for UID 988...
may 23 12:58:20 localhost plasmashell[16757]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
                                              
                                              Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
may 23 12:58:20 localhost systemd[1]: session-c2.scope: Succeeded.
may 23 12:58:20 localhost systemd[1]: session-c2.scope: Consumed 18.795s CPU time.
may 23 12:58:20 localhost systemd-logind[835]: Removed session c2.
may 23 12:58:21 localhost systemd[16749]: Queued start job for default target Main User Target.
may 23 12:58:21 localhost systemd[16749]: Reached target Paths.
may 23 12:58:21 localhost systemd[16749]: Reached target Timers.
may 23 12:58:21 localhost systemd[16749]: Starting D-Bus User Message Bus Socket.
may 23 12:58:21 localhost systemd[16749]: Listening on GnuPG cryptographic agent and passphrase cache.
may 23 12:58:21 localhost systemd[16749]: Listening on Sound System.
may 23 12:58:21 localhost systemd[16749]: Listening on D-Bus User Message Bus Socket.
may 23 12:58:21 localhost systemd[16749]: Reached target Sockets.
may 23 12:58:21 localhost systemd[16749]: Reached target Basic System.
may 23 12:58:21 localhost systemd[1]: Started User Manager for UID 988.
may 23 12:58:21 localhost systemd[16749]: Started GnuPG cryptographic agent and passphrase cache.
may 23 12:58:21 localhost systemd[16749]: Reached target Main User Target.
may 23 12:58:21 localhost systemd[1]: Started Session c3 of user sddm.
may 23 12:58:21 localhost systemd[16749]: Startup finished in 1.708s.
may 23 12:58:21 localhost gpg-agent[16765]: gpg-agent (GnuPG) 2.2.27 starting in supervised mode.
may 23 12:58:21 localhost gpg-agent[16765]: using fd 3 for std socket (/run/user/988/gnupg/S.gpg-agent)
may 23 12:58:21 localhost gpg-agent[16765]: listening on: std=3 extra=-1 browser=-1 ssh=-1
may 23 12:58:21 localhost systemd[16749]: Starting D-Bus User Message Bus...
may 23 12:58:22 localhost systemd[16749]: Started D-Bus User Message Bus.
may 23 12:58:22 localhost sddm-greeter[16767]: QFont::fromString: Invalid description '(empty)'
may 23 12:58:22 localhost sddm-greeter[16767]: Loading file:///usr/share/sddm/themes/flutter/Main.qml...
may 23 12:58:22 localhost sddm-greeter[16767]: QObject: Cannot create children for a parent that is in a different thread.
                                               (Parent is QGuiApplication(0x7ffe6d5768b0), parent's thread is QThread(0x15ed690), current thread is QThread(0x16689b0)
may 23 12:58:22 localhost sddm-greeter[16767]: QObject: Cannot create children for a parent that is in a different thread.
                                               (Parent is QGuiApplication(0x7ffe6d5768b0), parent's thread is QThread(0x15ed690), current thread is QThread(0x16689b0)
may 23 12:58:22 localhost sddm-greeter[16767]: QObject: Cannot create children for a parent that is in a different thread.
                                               (Parent is QGuiApplication(0x7ffe6d5768b0), parent's thread is QThread(0x15ed690), current thread is QThread(0x16689b0)
may 23 12:58:22 localhost sddm-greeter[16767]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Comment 5 Lewis Smith 2022-05-23 22:18:14 CEST 
> Last kernel i can use without the problem is: kernel-desktop-5.10.78-1
> this problem occurs in the following kernels: kernel-desktop-5.15...
Normally we would not accept problems with 3rd-party software, but if it used to work with Mageia, maybe we should look into it.
Did you keep kernel-desktop-5.10.78-1 to be able to boot with it?

Some of the journal reminds me of another recent bug, particularly "This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.". But which one?
Found candidates:
 https://bugs.mageia.org/show_bug.cgi?id=28620#c0
 https://bugs.mageia.org/show_bug.cgi?id=28250#c0

CC'ing tmb in the hope that he might be able to suggest something.
No promises though.

CC: (none) => lewyssmith, tmb

Comment 6 Victor Rivero 2022-05-24 05:37:17 CEST 
thanks for considering to find a solution to this problem.

Yes i'm using kernel kernel-desktop-5.10.78-1 and i don't have problem with that.

"No promises though", Okay, I know you're working extra on this. Thanks.
Comment 7 Lewis Smith 2023-06-01 21:31:37 CEST 
Sorry to have left you.
Is this still an issue? Have you been able to hang onto kernel-desktop-5.10.78-1 if the latest 5.15 still do not work with this program?
Comment 8 Victor Rivero 2023-07-19 20:47:43 CEST 
Sorry, I had not seen your message, i test the game (RuneScape) with Mageia 9 beta2 and is working using flatpak, for now, using Mageia 8 5.15.106 the problem haven't fixed yet for the game installed in the system, but is working it through flatpak. Thanks for your time.
Comment 9 Lewis Smith 2023-07-19 21:11:30 CEST 
Thank you for your own efforts and feedback. It seems that for Mageia 8, it works from Flatpak.
> i test the game (RuneScape) with Mageia
> 9 beta2 and is working using flatpak
Does this mean that for Mageia 9 also it only works as Flatpak? Otherwise, do you have the same problem as in Mageia 8?

Although I am closing this, you can still add comments, and they will be seen.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME

Comment 10 Victor Rivero 2023-07-20 02:37:31 CEST 
I couldn't install the game without flatpack, i got some problems with openssl version.
Note You need to log in before you can comment on or make changes to this bug.