[Stable Update] 2017-08-10 - Kernels, LibreOffice, Systemd, VirtualBox

update
stable

#81

xps9550, KDE, OK


#82

Ok. If we look at the title of this thread we see that we received a new systemd update right in this update.
What sounds strange is that the manjaro forum anouncement that openrc will be discontinued points to this link.
http://systemd-free.org/news.php
The name of the site is systemd-free. It gives the impression that arch and manjaro are going to ban openrc and systemd also.
Will arch keep updating systemd? Or will manjaro team keep updating systemd by their own initiative?


#83

You are reading this all wrong.

Manjaro is discontinuing a particular community release that is systemd-free (ie, running open-rc instead). The systemd-free link relates to versions of Arch that are/were systemd-free. Did you even read the Manjaro thread about the discontinuance of Manjaro-openrc? A few Arch-family distros (including Manjaro-openrc) that were systemd-free are banding together and leaving the official Arch stable to form their own systemd-free distro because it was getting more difficult to stay systemd-free using just Arch’s (or Manjaro’s) official repos.

This present thread we are in relates to updates in the official releases of Manjaro, which use systemd as init manager. Since you use this version, the openrc discontinuance has nothing to do with you and you needn’t worry about it.

[ADDED: if you’re running any version of Manjaro - official or community - that uses systemd as init manager, it’s fine.]


#84

I have some problems on Gnome on Wayland after this update. Previously it was really stable, where as now it crashed every 2-3 hours. It is strange because I don’t see many gnome related updates here. Could someone please point me in right direction with debugging this?

Here is my journalctl since last wakeup. (it crashed once, or maybe even twice).


#85

See if this command below isolates the error and post it here with the code tag.
$ journalctl -b | grep dump


#86

@anika200 Is this what you mean? I don’t think there is something particularily interesting here.

sie 15 12:18:54 asus systemd[1]: Created slice system-systemd\x2dcoredump.slice.
sie 15 12:18:54 asus systemd-coredump[3233]: Process 3231 (dbus-send) of user 1000 dumped core.
sie 15 12:18:55 asus systemd-coredump[3242]: Process 3238 (dbus-send) of user 1000 dumped core.
sie 15 12:20:55 asus systemd-coredump[3408]: Process 3406 (dbus-send) of user 1000 dumped core.
sie 15 12:20:56 asus systemd-coredump[3417]: Process 3415 (dbus-send) of user 1000 dumped core.
sie 15 12:20:58 asus systemd-coredump[3438]: Process 3436 (dbus-send) of user 1000 dumped core.
sie 15 12:20:58 asus systemd-coredump[3447]: Process 3445 (dbus-send) of user 1000 dumped core.
sie 15 12:21:05 asus systemd-coredump[3468]: Process 3466 (dbus-send) of user 1000 dumped core.
sie 15 12:21:05 asus systemd-coredump[3477]: Process 3475 (dbus-send) of user 1000 dumped core.
sie 15 13:34:57 asus systemd-coredump[8919]: Process 8917 (dbus-send) of user 1000 dumped core.
sie 15 13:34:57 asus systemd-coredump[8931]: Process 8926 (dbus-send) of user 1000 dumped core.
sie 15 13:36:00 asus systemd-coredump[9068]: Process 9066 (dbus-send) of user 1000 dumped core.
sie 15 13:36:00 asus systemd-coredump[9080]: Process 9075 (dbus-send) of user 1000 dumped core.
sie 15 13:36:56 asus systemd-coredump[9227]: Process 9225 (dbus-send) of user 1000 dumped core.
sie 15 13:36:56 asus systemd-coredump[9239]: Process 9234 (dbus-send) of user 1000 dumped core.
sie 15 13:55:23 asus systemd-coredump[10729]: Process 10727 (dbus-send) of user 1000 dumped core.
sie 15 13:55:23 asus systemd-coredump[10738]: Process 10736 (dbus-send) of user 1000 dumped core.
sie 15 13:55:52 asus systemd-coredump[10781]: Process 10779 (dbus-send) of user 1000 dumped core.
sie 15 13:55:53 asus systemd-coredump[10795]: Process 10793 (dbus-send) of user 1000 dumped core.
sie 15 13:56:54 asus systemd-coredump[10875]: Process 10873 (dbus-send) of user 1000 dumped core.
sie 15 13:56:54 asus systemd-coredump[10884]: Process 10882 (dbus-send) of user 1000 dumped core.
sie 15 14:58:53 asus systemd-coredump[12275]: Process 1173 (gnome-shell) of user 1000 dumped core.
sie 15 15:34:05 asus org.gnome.Nautilus[12493]: ('Handling file: ', 'file:///home/dominik/.zcompdump')

#87

Well it helped me find your coredumps without searching your entire log. :wink:

Last time this was happening to me (gnome-shell dumps) it seemed to be extension related. Try turning off all you extensions and see if you get the coredump. You may need to open a thread specific to your errors to get more help.


#88

Do you mean to disable all extensions and check if former command returns anything more?
It does not. After enabling as well.
Did I understand you? :slight_smile:

Never mind, I just realised you meant to disable one axtension that breaks things. I realised that I recently installed an extension that makes my topbar gradiented.

Anyway, it just crashed again. From what I can see, there is one error that just keeps spamming whole log? Isn’t it the most possible cause?
New log here, crash was somewhere at 16:39


#89

Yes I did, see if you still get crashes. It seems unlikely this is related to this update to me. I encourage you to start a new google search for you specific problem and see what you get. You can also start a new topic with just the coredump related errors not your whole log in the new thread.


#90

Successful update (terminal) with xfce intel integrated graphics laptop - Thanks everyone


#91

Update was successful, but it borked my apple wireless trackpad. tried forgetting then rediscovering, but then it showed 2 of them. When I load bluetoothctl, it shows the trackpad as connecting and then immediately disconnecting repeatedly.

Have twice had fiddle around with it for twenty minutes or so after rebooting, remembering, forgetting, trusting, untrusting, pairing and unpairing. Heartbreaking, really. :grinning: anyway, working for the moment with only one entry. if there are logs I can grep, let me know and I’ll post them to a new thread if you want. definitely screwed up something that has been pretty stable for a while though/


#92