[Stable Update] 2018-12-02 - Kernels, Plasma, Mesa, Cinnamon, Gnome, Deepin, XFCE, Vulkan

update
stable

#23

After updates xfce-panel disappears and crashes


#24

Hi!!!
At the end of the update pamac gives this error notice

Thanks for Manjaro!


#25

I get this error:


conflicting files:
xautomation: /usr/bin/pat2ppm already exists in filesystem
xautomation: /usr/bin/patextract already exists in filesystem
xautomation: /usr/bin/png2pat already exists in filesystem
xautomation: /usr/bin/rgb2pat already exists in filesystem
xautomation: /usr/bin/visgrep already exists in filesystem
xautomation: /usr/bin/xmousepos already exists in filesystem
xautomation: /usr/bin/xte already exists in filesystem
xautomation: /usr/share/man/man1/pat2ppm.1.gz already exists in filesystem
xautomation: /usr/share/man/man1/patextract.1.gz already exists in filesystem
xautomation: /usr/share/man/man1/png2pat.1.gz already exists in filesystem
xautomation: /usr/share/man/man1/rgb2pat.1.gz already exists in filesystem
xautomation: /usr/share/man/man1/visgrep.1.gz already exists in filesystem
xautomation: /usr/share/man/man1/xmousepos.1.gz already exists in filesystem
xautomation: /usr/share/man/man1/xte.1.gz already exists in filesystem
xautomation: /usr/share/man/man7/xautomation.7.gz already exists in filesystem

EDIT:
Solved by following this Package installation says FILENAME exists in filesystem; "Failed to commit transaction (conflicting files)" - but it is strange because I never installed anything manually - everything I installed on Manjaro comes from pamac. But yeah, can be an AUR. Had to check all paths to see if they are used by any package (none was) then deleted them and I could upgrade.


#26

I know, I know … aur package … Shut up, I am not complaining! :slight_smile:
mergerfs 2.25.1-1 didn’t work anymore after this update.
Just in case somebody else runs into the same issue and doesn’t have a lot of time to dig around right now, here is a quick fix:
installing fuse3 alongside fuse2 does fix it
Gotta check out whats going on, when I have a little more time on my hands, cause fuse3 is actually not a dependency of mergerfs.

[edit]
fuse3 is a dependency of mergerfs now
PKGBUILD already changed
[/edit]


#27
more xfce panel info:

14:17:22 systemd-coredum: Process 1844 (xfce4-panel) of user 1000 dumped core.

Stack trace of thread 1844:
#0 0x00007fc36805702a n/a (libtasklist.so)
#1 0x00007fc36805ad24 n/a (libtasklist.so)
#2 0x00007fc36a4646d0 ffi_call_unix64 (libffi.so.6)
#3 0x00007fc36a4640a0 ffi_call (libffi.so.6)
#4 0x00007fc36c9c12dc g_cclosure_marshal_generic (libgobject-2.0.so.0)
#5 0x00007fc36c9b83d5 g_closure_invoke (libgobject-2.0.so.0)
#6 0x00007fc36c9a5195 n/a (libgobject-2.0.so.0)
#7 0x00007fc36c9a901e g_signal_emit_valist (libgobject-2.0.so.0)
#8 0x00007fc36c9a9a80 g_signal_emit (libgobject-2.0.so.0)
#9 0x00007fc36d59115d n/a (libwnck-3.so.0)
#10 0x00007fc36d590f09 n/a (libwnck-3.so.0)
#11 0x00007fc36d59101d n/a (libwnck-3.so.0)
#12 0x00007fc36c8d0271 g_main_context_dispatch (libglib-2.0.so.0)
#13 0x00007fc36c8d1f89 n/a (libglib-2.0.so.0)
#14 0x00007fc36c8d2f62 g_main_loop_run (libglib-2.0.so.0)
#15 0x00007fc36d0536cf gtk_main (libgtk-3.so.0)
#16 0x0000561a19bac375 main (xfce4-panel)
#17 0x00007fc36c51f223 __libc_start_main (libc.so.6)
#18 0x0000561a19bac93e _start (xfce4-panel)

Stack trace of thread 1864:
#0 0x00007fc36c6ccafc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fc36244b522 n/a (librsvg-2.so.2)
#2 0x00007fc362445554 n/a (librsvg-2.so.2)
#3 0x00007fc362446056 n/a (librsvg-2.so.2)
#4 0x00007fc36244703c n/a (librsvg-2.so.2)
#5 0x00007fc36253fcda n/a (librsvg-2.so.2)
#6 0x00007fc362446a8b n/a (librsvg-2.so.2)
#7 0x00007fc36253afdb n/a (librsvg-2.so.2)
#8 0x00007fc36c6c6a9d start_thread (libpthread.so.0)
#9 0x00007fc36c5f6b23 __clone (libc.so.6)

Stack trace of thread 1847:
#0 0x00007fc36c5ebc21 __poll (libc.so.6)
#1 0x00007fc36c8d1ee0 n/a (libglib-2.0.so.0)
#2 0x00007fc36c8d1fce g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007fc36c8d2022 n/a (libglib-2.0.so.0)
#4 0x00007fc36c89b3eb n/a (libglib-2.0.so.0)
#5 0x00007fc36c6c6a9d start_thread (libpthread.so.0)
#6 0x00007fc36c5f6b23 __clone (libc.so.6)

Stack trace of thread 1848:
#0 0x00007fc36c5ebc21 __poll (libc.so.6)
#1 0x00007fc36c8d1ee0 n/a (libglib-2.0.so.0)
#2 0x00007fc36c8d2f62 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007fc36ca38c28 n/a (libgio-2.0.so.0)
#4 0x00007fc36c89b3eb n/a (libglib-2.0.so.0)
#5 0x00007fc36c6c6a9d start_thread (libpthread.so.0)
#6 0x00007fc36c5f6b23 __clone (libc.so.6)

Stack trace of thread 1865:
#0 0x00007fc36c6ccafc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fc36244b522 n/a (librsvg-2.so.2)
#2 0x00007fc362445554 n/a (librsvg-2.so.2)
#3 0x00007fc362446056 n/a (librsvg-2.so.2)
#4 0x00007fc36244703c n/a (librsvg-2.so.2)
#5 0x00007fc36253fcda n/a (librsvg-2.so.2)
#6 0x00007fc362446a8b n/a (librsvg-2.so.2)
#7 0x00007fc36253afdb n/a (librsvg-2.so.2)
#8 0x00007fc36c6c6a9d start_thread (libpthread.so.0)
#9 0x00007fc36c5f6b23 __clone (libc.so.6)

Stack trace of thread 1867:
#0 0x00007fc36c6ccafc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fc36244b522 n/a (librsvg-2.so.2)
#2 0x00007fc362445554 n/a (librsvg-2.so.2)
#3 0x00007fc362446056 n/a (librsvg-2.so.2)
#4 0x00007fc36244703c n/a (librsvg-2.so.2)
#5 0x00007fc36253fcda n/a (librsvg-2.so.2)
#6 0x00007fc362446a8b n/a (librsvg-2.so.2)
#7 0x00007fc36253afdb n/a (librsvg-2.so.2)
#8 0x00007fc36c6c6a9d start_thread (libpthread.so.0)
#9 0x00007fc36c5f6b23 __clone (libc.so.6)

Stack trace of thread 1866:
#0 0x00007fc36c6ccafc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fc36244b522 n/a (librsvg-2.so.2)
#2 0x00007fc362445554 n/a (librsvg-2.so.2)
#3 0x00007fc362446056 n/a (librsvg-2.so.2)
#4 0x00007fc36244703c n/a (librsvg-2.so.2)
#5 0x00007fc36253fcda n/a (librsvg-2.so.2)
#6 0x00007fc362446a8b n/a (librsvg-2.so.2)
#7 0x00007fc36253afdb n/a (librsvg-2.so.2)
#8 0x00007fc36c6c6a9d start_thread (libpthread.so.0)
#9 0x00007fc36c5f6b23 __clone (libc.so.6)

14:17:22 kernel: audit: type=1130 audit(1543778242.604:112): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-coredump@10-1887-0 comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
14:17:22 kernel: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-coredump@10-1887-0 comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
14:17:22 systemd: Started Process Core Dump (PID 1887/UID 0).
14:17:22 kernel: audit: type=1701 audit(1543778242.594:111): auid=1000 uid=1000 gid=100 ses=5 pid=1844 comm=“xfce4-panel” exe="/usr/bin/xfce4-panel" sig=11 res=1
14:17:22 kernel: Code: 8d 35 0a c6 ff ff ff 15 ec 0b 01 00 48 89 df 48 89 43 40 5b ff 25 7e 0f 01 00 66 0f 1f 44 00 00 41 55 41 54 55 53 48 83 ec 08 <4c> 8b 66 08 4d 85 e4 0f 84 b9 01 00 00 48 89 f5 48 89 fb 67 e8 6d
14:17:22 kernel: xfce4-panel[1844]: segfault at 8 ip 00007fc36805702a sp 00007ffdc8e49720 error 4 in libtasklist.so[7fc368052000+b000]
14:17:22 xfce4-panel: ANOM_ABEND auid=1000 uid=1000 gid=100 ses=5 pid=1844 comm=“xfce4-panel” exe="/usr/bin/xfce4-panel" sig=11 res=1


#28

on KDE after running this update my computer would not let me shutdown, restart, or logout. I did a hard shutdown and powered it back up and then it brought me to a yellow and white terminal. I powered down again and when I powered up a 3rd time and everything was fine and I am able to do everything fine now.


#29

Huge updates I always recommend to use a terminal to update your system without having a graphical session running. We hope to avoid this on future updates. I also mentioned that now in the Update-Video.


#30

Deepin got bumped to 15.8 weeks ago. We didn’t had time to do a new ISO, though - however, you should get it thru regular updates.


#31

thanks I will start doing that from now on. I did my update in the terminal but still with the GUI.


#32

Another excellent update pack from the manjaro team! No issues! All my usbmuxd issues are fixed in this update!


#33

This upgrade somehow broke suspend-to-RAM.

I have done a fresh installation from the Manjaro GNOME 18.0 iso. After installation suspend-to-RAM was working as expected.

I then have made the upgrade via TTY using pamac upgrade, rebooted and suspend-to-RAM is not working anymore on my Clevo N130WU laptop. It’s not that it goes to suspend and wakes up again immediately, but it does not go into suspend at all (screen goes black, I can see some activity from the laptop status LEDs, then the lock-screen comes back).

dmesg shows the following unusual:

dpm_run_callback(): usb_dev_suspend+0x0/0x10 returns -16
PM: Device usb1 failed to suspend async: error -16
PM: Some devices failed to suspend, or early wake event detected

Please have a look if someone can confirm the issue and let me know if there is a fix for that problem. Unfortunately a non-working suspend is a show-stopper for me. :frowning:


#34

All OK on Cinnamon and Xfce 4.19 (update via terminal). Thanx for another stable update !!!


#35

Which is the recommended method for huge or critical updates, boot Manjaro into text mode or just logoff and switch to TTY?


#36

XFCE with 4.19 kernel. Halfway the update i got the message; failed to connect Dbus. Xfce panel was not provided by any service files.
Shut down the computer and after restart the update was successfully ended.


#37

What a strange update.

Still using yay in terminal as my updater, I got everything downloaded and installed up to:
[ALPM] upgraded iso-codes (3.79-1 -> 4.1-1)
and then suddenly…
[ALPM] transaction interrupted
and then xorg crashes.

Then met with:
[ ok ] started TLP system startup/shutdown and a blinking cursor.

Dropped to tty, finished sudo pacman -Syu (this probably saved a borked system), reinstalled “iso-codes”, rebooted, and everything seems fine? Anyway to know for sure other than querying various packages to make sure they’re the latest version?


Unstable update - pacman
#38

@philm

I can now confirm that it is kernel 4.19.6-1-MANJARO that breaks suspend-to-RAM.

I have installed 4.18.20-1-MANJARO using the Manjaro Kernel Manager and after booting that kernel, suspend-to-RAM is working.

After booting back into 4.19.6-1-MANJARO suspend-to-RAM is broken again.


#39

I always run pacman-mirrors -f 5 as well to be certain I don’t get a partial update. If going to update in a terminal, this doesn’t take but a few seconds.


#40

Boot your System and follow these instructions.


#41

Yes, and that’s much appreciated, just curious as to when it might show up.


#42

“Deepin got bumped to 15.8 weeks ago. We didn’t had time to do a new ISO, though - however, you should get it thru regular updates”

Splash page still shows as 15.7.