Next time is crashes:
-
Provide the output of:
journalctl --system --boot=-1 --priority=3 | tail --lines=35
--priority=3
1 Like
ill try that
but fyi , when i freezes , even the keyboard is not responsive , the caps lock lamp even can’t work
and sometimes it blinks
i think it’s not freeze , more like a crash , can i see the log of that crash in journalctl , or all the log data is gone ?
EDIT :
it just crashed and “journalctl -b -1” can’t get to crash time
it crashed at 17:15 , and the last record in journal was 17:06
here it is anyway
>un 25 16:59:22 mohamed-pc kernel: audit: type=1334 audit(1624633162.635:205): prog-id=20 op=LOAD
Jun 25 16:59:22 mohamed-pc kernel: audit: type=1334 audit(1624633162.635:206): prog-id=21 op=LOAD
Jun 25 16:59:22 mohamed-pc kernel: audit: type=1334 audit(1624633162.635:207): prog-id=22 op=LOAD
Jun 25 16:59:22 mohamed-pc audit: BPF prog-id=21 op=LOAD
Jun 25 16:59:22 mohamed-pc audit: BPF prog-id=22 op=LOAD
Jun 25 16:59:22 mohamed-pc systemd[1]: Starting Time & Date Service...
Jun 25 16:59:22 mohamed-pc dbus-daemon[591]: [system] Successfully activated service 'org.freedesktop.timedate1'
Jun 25 16:59:22 mohamed-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostna>
Jun 25 16:59:22 mohamed-pc kernel: audit: type=1130 audit(1624633162.888:208): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-timedated comm="systemd" exe="/usr>
Jun 25 16:59:22 mohamed-pc systemd[1]: Started Time & Date Service.
Jun 25 16:59:52 mohamed-pc systemd[1]: systemd-timedated.service: Deactivated successfully.
Jun 25 16:59:53 mohamed-pc kernel: audit: type=1131 audit(1624633192.935:209): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-timedated comm="systemd" exe="/usr>
Jun 25 16:59:53 mohamed-pc kernel: audit: type=1334 audit(1624633192.955:210): prog-id=22 op=UNLOAD
Jun 25 16:59:53 mohamed-pc kernel: audit: type=1334 audit(1624633192.955:211): prog-id=21 op=UNLOAD
Jun 25 16:59:53 mohamed-pc kernel: audit: type=1334 audit(1624633192.955:212): prog-id=20 op=UNLOAD
Jun 25 16:59:52 mohamed-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostnam>
Jun 25 16:59:52 mohamed-pc audit: BPF prog-id=22 op=UNLOAD
Jun 25 16:59:52 mohamed-pc audit: BPF prog-id=21 op=UNLOAD
Jun 25 16:59:52 mohamed-pc audit: BPF prog-id=20 op=UNLOAD
Jun 25 17:01:01 mohamed-pc CROND[13400]: (root) CMD (run-parts /etc/cron.hourly)
Jun 25 17:01:01 mohamed-pc CROND[13399]: (root) CMDEND (run-parts /etc/cron.hourly)
Jun 25 17:06:05 mohamed-pc audit[13681]: USER_ACCT pid=13681 uid=1000 auid=1000 ses=1 subj==unconfined msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_time acct="mohamed" exe="/usr/bi>
Jun 25 17:06:05 mohamed-pc kernel: audit: type=1101 audit(1624633565.761:213): pid=13681 uid=1000 auid=1000 ses=1 subj==unconfined msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_time>
Jun 25 17:06:05 mohamed-pc kernel: audit: type=1103 audit(1624633565.765:214): pid=13681 uid=1000 auid=1000 ses=1 subj==unconfined msg='op=PAM:setcred grantors=pam_unix,pam_env acct="mohamed">
Jun 25 17:06:05 mohamed-pc audit[13681]: CRED_ACQ pid=13681 uid=1000 auid=1000 ses=1 subj==unconfined msg='op=PAM:setcred grantors=pam_unix,pam_env acct="mohamed" exe="/usr/bin/crontab" hostn>
Jun 25 17:06:05 mohamed-pc crontab[13681]: (mohamed) LIST (mohamed)
You need someone smarter than me then…
Sorry!
Today it crashed but i could enter tty before it totally crash
here is the output of journalctl
Jun 29 19:14:50 mohamed-pc bamfdaemon[902]: Got an X error: BadWindow (invalid Window parameter)
Jun 29 19:14:50 mohamed-pc bamfdaemon[902]: Got an X error: BadWindow (invalid Window parameter)
Jun 29 19:14:50 mohamed-pc bamfdaemon[902]: Got an X error: BadWindow (invalid Window parameter)
Jun 29 19:20:25 mohamed-pc kernel: i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=1089281 end=1089282) time 1768 us, min 763, max 767, scanline start 744, end 26
Jun 29 19:24:05 mohamed-pc bamfdaemon[902]: Got an X error: BadWindow (invalid Window parameter)
Jun 29 19:24:05 mohamed-pc bamfdaemon[902]: Got an X error: BadWindow (invalid Window parameter)
Jun 29 19:24:05 mohamed-pc bamfdaemon[902]: Got an X error: BadWindow (invalid Window parameter)
Jun 29 19:24:09 mohamed-pc vlc[43526]: QObject::~QObject: Timers cannot be stopped from another thread
Jun 29 19:24:20 mohamed-pc audit[43462]: ANOM_ABEND auid=1000 uid=1000 gid=1001 ses=1 subj==unconfined pid=43462 comm=53575420546872656164 exe="/usr/lib/jvm/java-11-openjdk/bin/java" sig=6 res=1
Jun 29 19:24:20 mohamed-pc kernel: audit: type=1701 audit(1624987460.109:198): auid=1000 uid=1000 gid=1001 ses=1 subj==unconfined pid=43462 comm=53575420546872656164 exe="/usr/lib/jvm/java-11-openjdk/bin/java" sig=6 res=1
Jun 29 19:24:20 mohamed-pc audit: BPF prog-id=42 op=LOAD
Jun 29 19:24:20 mohamed-pc audit: BPF prog-id=43 op=LOAD
Jun 29 19:24:20 mohamed-pc audit: BPF prog-id=44 op=LOAD
Jun 29 19:24:20 mohamed-pc kernel: audit: type=1334 audit(1624987460.203:199): prog-id=42 op=LOAD
Jun 29 19:24:20 mohamed-pc kernel: audit: type=1334 audit(1624987460.203:200): prog-id=43 op=LOAD
Jun 29 19:24:20 mohamed-pc kernel: audit: type=1334 audit(1624987460.203:201): prog-id=44 op=LOAD
Jun 29 19:24:20 mohamed-pc systemd[1]: Started Process Core Dump (PID 45278/UID 0).
Jun 29 19:24:20 mohamed-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-coredump@3-45278-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 29 19:24:20 mohamed-pc kernel: audit: type=1130 audit(1624987460.206:202): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-coredump@3-45278-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 29 19:25:12 mohamed-pc systemd-coredump[45279]: Process 43462 (java) of user 1000 dumped core.
Stack trace of thread 43480:
#0 0x00007f24a0ca0d22 raise (libc.so.6 + 0x3cd22)
#1 0x00007f24a0c8a862 abort (libc.so.6 + 0x26862)
#2 0x00007f24a0c8a747 __assert_fail_base.cold (libc.so.6 + 0x26747)
#3 0x00007f24a0c99616 __assert_fail (libc.so.6 + 0x35616)
#4 0x00007f2403b1ad2d n/a (libX11.so.6 + 0x40d2d)
#5 0x00007f2403b1adc8 n/a (libX11.so.6 + 0x40dc8)
#6 0x00007f2403b1b182 _XEventsQueued (libX11.so.6 + 0x41182)
#7 0x00007f2403b0c8f2 XPending (libX11.so.6 + 0x328f2)
#8 0x00007f2468567272 n/a (libgdk-3.so.0 + 0x8d272)
#9 0x00007f24682d9bc0 g_main_context_prepare (libglib-2.0.so.0 + 0x53bc0)
#10 0x00007f246832da06 n/a (libglib-2.0.so.0 + 0xa7a06)
#11 0x00007f24682d7781 g_main_context_iteration (libglib-2.0.so.0 + 0x51781)
#12 0x00007f2468dd1aca Java_org_eclipse_swt_internal_gtk_OS_g_1main_1context_1iteration (/home/mohamed/.swt/lib/linux/x86_64/libswt-pi3-gtk-4942r22.so + 0x51aca)
#13 0x00007f24883f38f9 n/a (n/a + 0x0)
#14 0x00007f2488c396f0 n/a (n/a + 0x0)
>Jun 29 19:25:12 mohamed-pc systemd[1]: systemd-coredump@3-45278-0.service: Deactivated successfully.
Jun 29 19:25:12 mohamed-pc kernel: audit: type=1131 audit(1624987512.379:203): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-coredump@3-45278-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 29 19:25:12 mohamed-pc kernel: audit: type=1334 audit(1624987512.466:204): prog-id=44 op=UNLOAD
Jun 29 19:25:12 mohamed-pc kernel: audit: type=1334 audit(1624987512.466:205): prog-id=43 op=UNLOAD
Jun 29 19:25:12 mohamed-pc kernel: audit: type=1334 audit(1624987512.466:206): prog-id=42 op=UNLOAD
Jun 29 19:25:12 mohamed-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-coredump@3-45278-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 29 19:25:12 mohamed-pc audit: BPF prog-id=44 op=UNLOAD
Jun 29 19:25:12 mohamed-pc audit: BPF prog-id=43 op=UNLOAD
Jun 29 19:25:12 mohamed-pc audit: BPF prog-id=42 op=UNLOAD
Jun 29 19:25:12 mohamed-pc systemd[1]: systemd-coredump@3-45278-0.service: Consumed 11.442s CPU time.
Jun 29 19:25:54 mohamed-pc wpa_supplicant[579]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-23 noise=9999 txrate=54000
Jun 29 19:30:44 mohamed-pc bamfdaemon[902]: Got an X error: BadWindow (invalid Window parameter)
Jun 29 19:30:44 mohamed-pc bamfdaemon[902]: Got an X error: BadWindow (invalid Window parameter)
Jun 29 19:30:44 mohamed-pc bamfdaemon[902]: Got an X error: BadWindow (invalid Window parameter)
Jun 29 19:30:44 mohamed-pc bamfdaemon[902]: Got an X error: BadWindow (invalid Window parameter)
Jun 29 19:30:44 mohamed-pc bamfdaemon[902]: Got an X error: BadWindow (invalid Window parameter)
Jun 29 19:30:44 mohamed-pc bamfdaemon[902]: Got an X error: BadWindow (invalid Window parameter)
it crashed at exactly 19:30:44
I’m not as smart as fabby, and not sure if this will help you but there is a error in the log that is referenced in this thread on the arch forum with the same symptoms as you descibe, I refer to this error: kernel: i915 0000:00:02.0: [drm] ERROR Atomic update failure on pipe A. There are more people with this error.
There are some possible solutions, the user in the arch thread added a option in their grub config as described in post 5 in that thread. You could try it, it is not a difficult procedure. Make sure you take precautions
Summary
$ sudo nano /etc/default/grub
Find the line
GRUB_CMDLINE_LINUX_DEFAULT="quiet apparmor=1 security=apparmor udev.log_priority=3 sysrq_always_enabled=1 loglevel=3"
Add the variable:
GRUB_CMDLINE_LINUX_DEFAULT="quiet apparmor=1 security=apparmor udev.log_priority=3 sysrq_always_enabled=1 loglevel=3 intel_idle.max_cstate=1"
save (ctrl+X Y enter)
$ sudo update-grub
Reboot
If this does not stop the crashes there are more options to pursue, post your results, maybe there is a user who can help you further 
1 Like
i’ll try that , btw , the post you mention says that it has something to do with thermal monitoring widget he had
did the last update has something like that updated / installed ? because it started happening since the last update , i’ve installed manjaro for the past three years , nothing happened , not a single freeze
Checking out the #announcements:stable-updates posts for clues might help, there are detailed package lists that are updated. I’m not familiar with your DE so a more experienced user might chime in here to help out.
1 Like
Feedback, please?
If still happening: Does this also happen if you log into another user? (E.G. k3rnelpanic2)
i found out a workaround , i created a new user and the problem is solved , so im 100% sure that it was the power settings that i edited , but i don’t know exactly what happened to cause all these crashes , it was just changing the lid switch , could this lead to crashes , or is it a bug in the last update ?
1 Like
So you have an issue in your user profile and finding out which exact setting you changed is going to take weeks if not months, therefore, we’re going to do the following:
-
Verify that the new user has access to the same groups as your old one by executing groups and comparing the output of both users.
groups k3rnelpanic groups k3rnelpanic2(Where obviously,
k3rnelpanicis your old user andk3rnelpanic2is your new one.)
E.G. ifk3rnelpanicis a member ofoperatorandk3rnelpanic2isn’t, execute:usermod --append --groups operator k3rnelpanic2 -
Copy all data files from your old profile into your new one
cp --verbose --recursive --preserve=time-stamps /home/k3rnelpanic/Documents/* /home/k3rnelpanic2/Documents/If that worked and you had no errors, remove the documents from your old user:
rm --recursive /home/k3rnelpanic/Documents/*repeat for:
PicturesVideosMusic.thunderbird.mozilla/firefox/- Templates, and everything else that is important to you.
- Linux games like Battle of Wesnoth have their game data stored under
~/.local/share/E.G.~/.local/share/wesnoth/
After everything has been copied over, disable the old user so you cannot accidentally log on:
usermod --lock k3rnelpanicIf you would have theming going on, don’t do everything in one day but do this at the rate of 1 application / theme / whatever per day and if the same issue crops up again, roll back your last change and thus you’ve now pinpointed the exact setting that made your old user misbehave.
-
in 1 month delete the entire home directory of your old user, but don’t delete the user itself so that in 6 months time files still owned by that user will still show up under its username.
-
If you ever migrate to a new machine, just don’t migrate the old user: only the new one.
-
From now on, start making backups so you can roll back and never have to do this again:
Probably not, or it would have been mentioned in the issues underneath the last release notes
2 Likes
I’ve marked this answer as the solution to your question as it is by far the best answer you’ll get.
However, if you disagree with my choice, please feel free to take any other answer as the solution to your question or even remove the solution altogether: You are in control! (If you disagree with my choice, just send me a personal message and explain why I shouldn’t have done this or 
or 
if you agree)
P.S. In the future, please don’t forget to come back and click the 3 dots below the answer to mark a solution like this below the answer that helped you most:
so that the next person that has the exact same problem you just had will benefit from your post as well as your question will now be in the “solved” status.
thanks for this post man , this what i like about manjaro , the great community
3 Likes
EDIT :
i thought the problem was gone by making a new user , but it reappeared again
and i can’t find any logs , same info from journalctl
could this be a faulty hardware ? and if so , is there any logs i can view to see which part is faulty
What did you do?
- Install a theme?
- fiddled with power settings
- ran some obscure “optimization” program
- Something else entirely?
i didn’t do anything , even used the vanilla theme
is there any log that can view the exact error ?
Yeah, journalctl with a higher priority than 3. But it gets to be too much information really quickly, so you’ll have to do the grunt work for me…
i used journalctl -b -1
and journalctl -b -1 -p 7
nothing shows up at the crash time
It’s a hardware issue , i tried other live distros even live usb old manjaro
the same problem persist
but i can’t find any logs like a crash report or something , if someone help me find which part is faulty that would be great
i ran bios diagnostics , and memory tests , all are ok
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.