Computer suddenly crashes and change the way of working when restart

Support
1

Hello,
I had android studio, google chrome and others applications opened and suddenly thes apps crashed/turned off. Now when I turn on the computer it behaves weird. I don’t have access to this bottom menu easily.
I use GNOME.



mar 21 18:21:37 chris-15 kernel: Linux version 6.1.19-1-MANJARO (builduser@fv-a>
mar 21 18:21:37 chris-15 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.1-x86>
mar 21 18:21:37 chris-15 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 >
mar 21 18:21:37 chris-15 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE >
mar 21 18:21:37 chris-15 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX >
mar 21 18:21:37 chris-15 kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[>
mar 21 18:21:37 chris-15 kernel: x86/fpu: Enabled xstate features 0x7, context >
mar 21 18:21:37 chris-15 kernel: signal: max sigframe size: 1776
mar 21 18:21:37 chris-15 kernel: BIOS-provided physical RAM map:
mar 21 18:21:37 chris-15 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000>
mar 21 18:21:37 chris-15 kernel: BIOS-e820: [mem 0x00000000000a0000-0x000000000>
mar 21 18:21:37 chris-15 kernel: BIOS-e820: [mem 0x0000000000100000-0x000000000>
mar 21 18:21:37 chris-15 kernel: BIOS-e820: [mem 0x0000000009ef0000-0x000000000>
mar 21 18:21:37 chris-15 kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000>
mar 21 18:21:37 chris-15 kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000>
mar 21 18:21:37 chris-15 kernel: BIOS-e820: [mem 0x000000000a20f000-0x00000000b>
mar 21 18:21:37 chris-15 kernel: BIOS-e820: [mem 0x00000000b5842000-0x00000000b>
mar 21 18:21:37 chris-15 kernel: BIOS-e820: [mem 0x00000000b59c1000-0x00000000b>
mar 21 18:21:37 chris-15 kernel: BIOS-e820: [mem 0x00000000b5a3c000-0x00000000b>
mar 21 18:21:37 chris-15 kernel: BIOS-e820: [mem 0x00000000b7136000-0x00000000b>
mar 21 18:21:37 chris-15 kernel: BIOS-e820: [mem 0x00000000bcb79000-0x00000000b>
mar 21 18:21:37 chris-15 kernel: BIOS-e820: [mem 0x00000000bcbfe000-0x00000000b>
mar 21 18:21:37 chris-15 kernel: BIOS-e820: [mem 0x00000000be000000-0x00
2

:question:

filmst Du quer, siehst Du mehr.

(use a translator like translate.google.com - from german to … whatever)

I can’t see anything - don’t record video in portrait mode when you want to show 90° of it.

I did not see a crash …

… you might mean that some program did not start - or did not what you thought it should do …

1 Like
3

It should allow me to open bottom menu when I let my mouse there. It shouldn’t behave like that in the start I mean the screen goes back at start. It starts after crash.

4

Google Translate says,

if you film sideways, you see more

I understand what you mean, so I’ll convey it:

If you turn on Auto-Rotate before taking the video, it won’t be sideways when you rotate your phone.

@chrisWW Nudge, nudge, wink, wink

5

kk sorry for that normally i could rotate wideo in program, so I do not take care of it so much, but it you can’t or just don’t want to see anything on the video I comment it what exactly happens. Is it possible to somehow reinstall only system files? Thanks for any advice even the recording course for 3 posts long which is nothing to the topic.
I will rotate the video and edit post anyway

6

This is a support forum, not an instant messenger or social network. There is no character limit and no need for abbreviations.

Please see the following and make appropriate edits to your first post. That way, our helpful volunteers will be more inclined to help you:

7

Ok, you can check it now.

10
13

The 'crash' was basically restarting graphics and closing all applications with reset settings to default, which happened because of one external monitor plugged and changing graphic option to launch two monitors from the external which was in usage. So basically I could use kscreen-doctor, wdisplays or just turn off primary monitor and launch only external one. That was the solution for this crash behaviour.

14
15

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.