I have a 18.04 Ubuntu (not Lubuntu) system with LXDE installed. It's been pretty trouble-free for years (since I installed it in April 2018).
About a month ago lxpanel started crashing on the first login after a powerup. It first happened on the next reboot after an NVIDIA driver update, so at first I suspected that, but I don't think that was it any more.
Because if I then open a terminal via keyboard shortcuts, log out using the command line, and log in again, it does not crash.
I can also, on that first login, open a terminal via keyboard shortcuts and issue a lxpanel --profile LXDE & and that works. In fact, that's the workaround I've been using.
I found a lxsession log that shows the crash, but there's not much information there, at least for me:
** Message: 08:30:55.205: app.vala:130: lxpanel exit with this type of exit: 139
** Message: 08:30:55.205: app.vala:148: Exit not normal, try to reload
** Message: 08:30:55.206: app.vala:76: Launching lxpanel
** Message: 08:30:55.417: app.vala:130: lxpanel exit with this type of exit: 139
** Message: 08:30:55.418: app.vala:148: Exit not normal, try to reload
** Message: 08:30:55.418: app.vala:76: Launching lxpanel
** Message: 08:30:55.636: app.vala:130: lxpanel exit with this type of exit: 139
** Message: 08:30:55.636: app.vala:148: Exit not normal, try to reload
** Message: 08:30:55.637: app.vala:76: Launching lxpanel
** Message: 08:30:55.837: app.vala:130: lxpanel exit with this type of exit: 139
** Message: 08:30:55.838: app.vala:148: Exit not normal, try to reload
** Message: 08:30:55.839: app.vala:76: Launching lxpanel
** Message: 08:30:56.038: app.vala:130: lxpanel exit with this type of exit: 139
** Message: 08:30:56.038: app.vala:148: Exit not normal, try to reload
** Message: 08:30:56.039: app.vala:76: Launching lxpanel
** Message: 08:30:56.243: app.vala:130: lxpanel exit with this type of exit: 139
** Message: 08:30:56.243: app.vala:148: Exit not normal, try to reload
** Message: 08:30:56.243: app.vala:156: Application crashed too much, stop reloading
There's probably info in whatever exit type 139 is, but I haven't been able to google up what that means.
What additional information can I collect to diagnose this problem?
