Arch Linux

shako

Member

Registered: 2021-11-16

Posts: 50

xinit: unexpected signal 15

I just noticed this line:

xinit: unexpected signal 15

popping up whenever I shut down an X session. Everything else is clean, and the server gets terminated successfully. Xorg.0.log:

[   733.289] (**) Option "fd" "25"
[   733.289] (II) event2  - Power Button: device removed
[   733.289] (**) Option "fd" "28"
[   733.289] (II) event12 - Video Bus: device removed
[   733.290] (**) Option "fd" "29"
[   733.290] (II) event1  - Sleep Button: device removed
[   733.290] (**) Option "fd" "30"
[   733.290] (II) event5  - PS2toUSB PS2toUSB Adapter: device removed
[   733.290] (**) Option "fd" "31"
[   733.290] (II) event6  - PS2toUSB PS2toUSB Adapter Mouse: device removed
[   733.290] (**) Option "fd" "32"
[   733.290] (II) event7  - PS2toUSB PS2toUSB Adapter System Control: device removed
[   733.290] (**) Option "fd" "33"
[   733.290] (**) Option "fd" "34"
[   733.290] (II) event3  - PixArt Lenovo USB Optical Mouse: device removed
[   733.290] (**) Option "fd" "35"
[   733.290] (II) event11 - Integrated Camera: Integrated C: device removed
[   733.290] (**) Option "fd" "36"
[   733.290] (II) event4  - AT Translated Set 2 keyboard: device removed
[   733.290] (**) Option "fd" "37"
[   733.290] (II) event13 - SynPS/2 Synaptics TouchPad: device removed
[   733.290] (**) Option "fd" "38"
[   733.290] (II) event21 - TPPS/2 IBM TrackPoint: device removed
[   733.291] (**) Option "fd" "39"
[   733.291] (II) event10 - ThinkPad Extra Buttons: device removed
[   733.291] (**) Option "fd" "33"
[   733.291] (II) event8  - PS2toUSB PS2toUSB Adapter Consumer Control: device removed
[   733.292] (II) UnloadModule: "libinput"
[   733.292] (II) systemd-logind: not releasing fd for 13:72, still in use
[   733.292] (II) UnloadModule: "libinput"
[   733.292] (II) systemd-logind: releasing fd for 13:74
[   733.308] (II) UnloadModule: "libinput"
[   733.308] (II) systemd-logind: releasing fd for 13:85
[   733.351] (II) UnloadModule: "libinput"
[   733.351] (II) systemd-logind: releasing fd for 13:77
[   733.388] (II) UnloadModule: "libinput"
[   733.388] (II) systemd-logind: releasing fd for 13:68
[   733.404] (II) UnloadModule: "libinput"
[   733.405] (II) systemd-logind: releasing fd for 13:75
[   733.438] (II) UnloadModule: "libinput"
[   733.438] (II) systemd-logind: releasing fd for 13:67
[   733.474] (II) UnloadModule: "libinput"
[   733.475] (II) systemd-logind: releasing fd for 13:72
[   733.491] (II) UnloadModule: "libinput"
[   733.491] (II) systemd-logind: releasing fd for 13:71
[   733.508] (II) UnloadModule: "libinput"
[   733.508] (II) systemd-logind: releasing fd for 13:70
[   733.541] (II) UnloadModule: "libinput"
[   733.541] (II) systemd-logind: releasing fd for 13:69
[   733.558] (II) UnloadModule: "libinput"
[   733.558] (II) systemd-logind: releasing fd for 13:65
[   733.574] (II) UnloadModule: "libinput"
[   733.575] (II) systemd-logind: releasing fd for 13:76
[   733.602] (II) UnloadModule: "libinput"
[   733.602] (II) systemd-logind: releasing fd for 13:66
[   733.658] (II) Server terminated successfully (0). Closing log file.

Is it all normal? Or is there something I might want to investigate more?

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,345

Website

Re: xinit: unexpected signal 15

Signal 15 is SIGTERM which is not surprising.  How are you shutting down the session?

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

shako

Member

Registered: 2021-11-16

Posts: 50

Re: xinit: unexpected signal 15

Signal 15 is SIGTERM which is not surprising.  How are you shutting down the session?

Plain poweroff from the command line. Now turned into a signal 1...

EDIT: actually, it is signal 1 if I shut the machine down from a terminal, and signal 15 if I, for example, shut it down by pressing the power button. signal 15 is sigterm, which makes sense to me. signal 1 is hangup, which means the terminal which launched the process has been terminated abruptly (which also makes sense to me, since I launched shutdown from a terminal). So, I suppose it is nothing to worry about...? Maybe I am just paranoid.

Last edited by shako (2022-11-10 14:14:12)

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,345

Website

Re: xinit: unexpected signal 15

Yup, it all sounds fine to me - though `poweroff` should do the same thing as pressing the power button.  I'm mildly curious why they end up shutting down differently, but it's certainly not any cause for concern.

However, if this is all while powering down, how / where are you seeing that message from xinit?  (also just a curiousity - there is no issue here)

Also, why xinit would call two common signals used for shutting it down "unexpected" is a bit silly.  But then so is all of xinit (but not nearly as silly as startx).

Last edited by Trilby (2022-11-10 14:40:17)

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

shako

Member

Registered: 2021-11-16

Posts: 50

Re: xinit: unexpected signal 15

However, if this is all while powering down, how / where are you seeing that message from xinit?  (also just a curiousity - there is no issue here)

In tty, right after launching the shutdown command subsequently exiting the X server. Glad it is nothing to worry about (I also got that feeling, since there is nothing suspicious in the xorg log). Thank you for your time @Trilby

Last edited by shako (2022-11-10 15:08:39)

shako

Member

Registered: 2021-11-16

Posts: 50

Re: xinit: unexpected signal 15

Yup, it all sounds fine to me - though `poweroff` should do the same thing as pressing the power button.  I'm mildly curious why they end
Also, why xinit would call two common signals used for shutting it down "unexpected" is a bit silly.  But then so is all of xinit (but not nearly as silly as startx).

It is, indeed. I investigated more on the issue and ended up on this (not yet accepted) merge request:

https://gitlab.freedesktop.org/xorg/app … /issues/19

So, xinit exits with a failure upon receiving SIGTERM, if I got that correctly. That's quite annoying... Guess I'll just have to ignore it, or re-compile it. Thanks again!

Last edited by shako (2022-11-14 17:07:58)