http://bugzilla.opensuse.org/show_bug.cgi?id=1045700 http://bugzilla.opensuse.org/show_bug.cgi?id=1045700#c3 --- Comment #3 from Tomas Kuchta --- Created attachment 730208 --> http://bugzilla.opensuse.org/attachment.cgi?id=730208&action=edit journalctl -xb -0 output output of: journalctl -xb -0 | gzip > journalctl_xb_0.log.gz -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1045700 http://bugzilla.opensuse.org/show_bug.cgi?id=1045700#c5 --- Comment #5 from Franck Bui ---

From the logs, it seems that the system boot up fine and you could log in.

But after, that there were a bunch of processes that you started (?) and that crashed:

$ grep "^Jun.*dumped core" journalctl_xb_0.log Jun 26 06:02:23 artichoke.home systemd-coredump[21484]: Process 21483 (single) of user 1000 dumped core. Jun 26 06:02:29 artichoke.home systemd-coredump[21542]: Process 21541 (single) of user 1000 dumped core. Jun 26 06:02:29 artichoke.home systemd-coredump[21543]: Process 21523 (tracker-extract) of user 1000 dumped core. Jun 26 06:02:35 artichoke.home systemd-coredump[21490]: Process 21366 (tracker-extract) of user 1000 dumped core. Jun 26 06:02:35 artichoke.home systemd-coredump[21579]: Process 21546 (tracker-extract) of user 1000 dumped core.

$ grep "^Jun.*dumped core" journalctl_xb_0.log | wc -l 101

So what did you do exactly ? what's "tracked-extract" ? did you start them manually ? After reading your initial description, it sounds that did happen during the first boot process, right after installing 42.3. Also next time, please drop the '-x' option from journalctl, it makes the logs harder to read IMHO. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1045700 http://bugzilla.opensuse.org/show_bug.cgi?id=1045700#c7 --- Comment #7 from Tomas Kuchta --- Created attachment 730303 --> http://bugzilla.opensuse.org/attachment.cgi?id=730303&action=edit new jornalctl -b -0 log for readability -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1045700 http://bugzilla.opensuse.org/show_bug.cgi?id=1045700#c9 --- Comment #9 from Tomas Kuchta --- I am not sure what is your problem with the media file and how is that related to the system behavior. As I have said, I am trying to help with testing and media is important part of openSuSE. It should be clear, if you look at my bug reports that I am trying to help this project. There was a call for more testing on real HW from Douglas DeMayo - that is how I am able to help. I am not sure what your circumstances are and how you got assigned this report - If you do not want to help and work on this - please do not. There is no need to discourage other people from trying to contribute. --------------------------------------------------------------- In order to be able to use this laptop with those systemd-tracker processes, I stop them by sending SIGSTOP signal to them. Killing is pointless as systemd will spawn new ones. Here is how I do that: sudo kill -s SIGSTOP $(ps -ef | grep dump | grep -v grep | awk '{print $2}') Then I try to use the system as much as I can to see if I stumble on additional problems. I guarantee you that the reported behavior has started at the first login to the system post-install and it is behaving consistently for over week now - despite system updates and reboots. I do not know anything about this tracker process beyond that I can learn from man and google. It is causing me unnecessary troble on other non leap 42.3 systems because it keeps scanning large mounted NFS volumes. I have issue with that from performance, network and filer load point of view as well as from data security point of view because it is storing confidential remote data on the local disks of every machine, and there is no stopping it. --------------------------------------------------------------- As I said, if you are annoyed with this report, do not want to work on it or you do not believe me that it is real please stop. Given the rate at which users are abandoning openSuse, there is no need for negative, not constructive response to bug reports. See Ludwig Nussel openSuSE Conference talk: https://www.youtube.com/watch?v=s1v-icm2uuc&feature=youtu.be for pretty dramatic dropping user base charts. Best regards, Tomas -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1045700 http://bugzilla.opensuse.org/show_bug.cgi?id=1045700#c12 Tomas Kuchta changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #12 from Tomas Kuchta --- This issue is no longer present after reinstalling build300 (my original install was build277). It is strange that updates were not able to fix this ..... I am changing the status as resolved. -- You are receiving this mail because: You are on the CC list for the bug.