On dimanche, 8 octobre 2017 19.38:10 h CEST Jan Engelhardt wrote:
On Sunday 2017-10-08 14:05, Andrei Dziahel wrote:
Which poses the question: how can I have automated g-s core dumps back? And, for sake of curiosity, how and why were they even disabled at all?
Does gnome-shell do suid games? Then sysctl fs.suid_dumpable Can gnome-shell write to the right directory? sysctl kernel.core_pattern Is gnome-shell not exceeding its core limits? ulimit -c and /proc/$$/limits
I'm also interested by make coredump great again. I've now since months none of the backtrace recorded in var/lib/systemd/ coredump (or some truncated). For example Sat 2017-10-07 10:53:45 CEST 1901 1502 1500 11 none /usr/bin/ baloo_file 1502 being me I've setup (as I can on my laptop) generous vars in /etc/systemd/coredump.conf [Coredump] Storage=external Compress=yes ProcessSizeMax=32G ExternalSizeMax=32G JournalSizeMax=16G MaxUse=32G KeepFree=2G So I can't understand why I don't get backtrace. I've now created a systemd-coredump@1502.service link as @0 exist but didn't find the right documentation for it. journalctl give some info Oct 08 12:29:46 qt-kt.labaroche.ioda.net systemd[1]: Requested transaction contradicts existing jobs: Transaction is destructive. Oct 08 12:29:46 qt-kt.labaroche.ioda.net systemd[1]: systemd-coredump.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Transaction is de Oct 08 12:29:46 qt-kt.labaroche.ioda.net systemd[1]: systemd-coredump.socket: Unit entered failed state. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org