Post output of these 2 commands [Nothing harmful]

General system Newbie
1

The first command lets you know how old is your endeavour os install
awk -F "[[ ]" 'NR==1 {print $2;}' /var/log/pacman.log

The second command is about core dumps.
I am just intrigued as how many you are getting core dumps lately or is it just me.

coredumpctl -r

Better if you can post the output of a physical hardware, not a virtual machine running EOS.

1 Like
2

Maybe post yours first so that other users can start identifying what’s wrong with your system right away?

1 Like
3
Output from commands requested: 
$ awk -F "[[ ]" 'NR==1 {print $2;}' /var/log/pacman.log
2023-04-05T16:24:13-0300]
$ coredumpctl -r
No coredumps found.
4

I reinstalled eos just today so I don’t have any coredumps yet but here’s the output anyway.
2023-08-10T15:07:42+0500]
No coredumps found.

5

:rofl:
Obviously, I was referring to the problematic coredumps before your reinstall.

6

Yeah, I’m intrigued as how many other people are getting core dumps. I remember calamares crashed on me with a core dump as well while installing eos.

7

actually, it only displays the first time pacman was used after you rotated/cleaned your log files, which can be the install date but does not have to be :wink:

1 Like
8

Yup. It makes more sense to check the timestamps when the file systems were created. Or the earliest journal entry, if the journal has never been vacuumed.

9

yeah, that’s correct. But many people I guess don’t clean them :wink:

10

And here, we go got another core dump.
I suspect it just happens on EOS, I’m gonna try plain arch or another arch distribution to see if it happens there too. As core dumps are never normal.

11 
PID: 1136 (picom)
           UID: 1000 (v3n0m)
           GID: 1001 (v3n0m)
        Signal: 6 (ABRT)
     Timestamp: Thu 2023-08-10 19:58:46 PKT (25min ago)
  Command Line: picom
    Executable: /usr/bin/picom
 Control Group: /user.slice/user-1000.slice/session-1.scope
          Unit: session-1.scope
         Slice: user-1000.slice
       Session: 1
     Owner UID: 1000 (v3n0m)
       Boot ID: ed30f482309f41beb47bcc345a72e797
    Machine ID: acd4ce7187d74bcfbf1b1be882e4d655
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.picom.1000.ed30f482309f41beb47bcc345a72e797.1136.1691679526000000.zst (present)
  Size on Disk: 190.2K
       Message: Process 1136 (picom) of user 1000 dumped core.

                Stack trace of thread 1136:
                #0  0x00007f5ccf88e83c n/a (libc.so.6 + 0x8e83c)
                #1  0x00007f5ccf83e668 raise (libc.so.6 + 0x3e668)
                #2  0x00007f5ccf8264b8 abort (libc.so.6 + 0x264b8)
                #3  0x000055e599171035 n/a (picom + 0xb035)
                #4  0x000055e59917e691 n/a (picom + 0x18691)
                #5  0x000055e59919ce5c n/a (picom + 0x36e5c)
                #6  0x000055e599177faa n/a (picom + 0x11faa)
                #7  0x000055e5991ab71f n/a (picom + 0x4571f)
                #8  0x000055e599173b6c n/a (picom + 0xdb6c)
                #9  0x00007f5ccff410cb ev_invoke_pending (libev.so.4 + 0x50cb)
                #10 0x00007f5ccff44d10 ev_run (libev.so.4 + 0x8d10)
                #11 0x000055e59917146e n/a (picom + 0xb46e)
                #12 0x00007f5ccf827cd0 n/a (libc.so.6 + 0x27cd0)
                #13 0x00007f5ccf827d8a __libc_start_main (libc.so.6 + 0x27d8a)
                #14 0x000055e599172845 n/a (picom + 0xc845)
                ELF object binary architecture: AMD x86-64
~

This is the output of the latest core dump

12 
2022-10-02T16:27:48+0200]

I can’t believe it is almost a year on only one installation!
(It could have been more than that if it was my previous laptop, but this is a new laptop I bought - I can say I bought it that day because I remember once I went home I directly installed EndeavourOS and wiped the Windoze).

13

$ stat / | grep Birth
Birth: 2023-06-03 17:45:49.000000000 +0200

Still in its infancy.

$ coredumpctl -r
No coredumps found.