[Stable Update] 2019-04-03 - Mate, KDE-Dev, Cinnamon, Deepin, Browsers

Ta, yeah, maybe tomorrow. The Australian ones are notoriously slow to update, so i usually avoid them. It's late here now; i'll retry tomorrow & cross my fingers.

1 Like

Yeah, I manually edit my mirrorlist file with a good quick mirror or three and just stick with it (ie moson), don't use pacman-mirrors.

Are you doing this in peak evening timeframe? Could be ISP congestion also if all mirror downloads are crawling, or as was mentioned the mirrors are getting clobbered by lots of users updating.

Imagine it would be annoying anyway ... move this box to testing too ... :grin:

Good update, System after reboot works fine.
LXQT and XFCE with Kernel 5.0.
Thanks!

1 Like

Can someone please explain deepin-file-manager-nomodule? Thanks

The update went smoothly but some new errors have popped up in my logs

Apr 04 13:37:07 nicomo-pc kernel: rtl8192c_common: Polling FW ready fail! REG_MCUFWDL:0x00030006.
Apr 04 13:37:07 nicomo-pc kernel: rtl8192c_common: Firmware is not ready to run!
Apr 04 13:37:07 nicomo-pc kernel: rtl8192cu: 8051 reset failed!.........................

will do another reboot and see if they reappear.

Update : disappeared on the second reboot - no idea why.

Before doing the update via TTY (I am usually following these instructions) and wanting to have the newest version of mesa, I would like to know if I should:

  1. either run sudo pacman -Syyuw and then sudo pacman -Syuu, pamac upgrade --enable-downgrade
  2. or run sudo pacman -Syyuuw and then sudo pacman -Syuu, pamac upgrade --enable-downgrade

Or is there another way to do that?
Thanks in advance.

This is where configuring pamac-manager to automatically download updates comes into its own. By the time you come to do the update, the packages should all be sitting in cache ready for you.

This bug: [Stable Update] 2019-04-03 - Mate, KDE-Dev, Cinnamon, Deepin, Browsers (plasmashell use 100% CPU for each animated indicator)
can be fixed by setting environment variable QSG_RENDER_LOOP=basic
just create /etc/profile.d/fix_qt_bug.sh file with content: export QSG_RENDER_LOOP=basic

but I do not know what else it will affect and why everything was fine without this "fix" with QT 5.12.1 .

@suzannex you would be better working with Play on Linux for Wine... that way you can control different versions of wine and avoid that kind of problems.

2 Likes

Compton-6.2-2 broken after this upgrade...

/usr/bin/manjaro-compositor --start
[ 2019-04-04 07:45:26.388 parse_config_libconfig FATAL ERROR ] Error when reading configuration file "/home/obxdan/.config/compton.conf", line 29: syntax error
[ 2019-04-04 07:45:26.388 main FATAL ERROR ] Failed to create new compton session.

FYI: /home/obxdan/.config/compton.conf", line 29

    27  
    28  # Backend
    29  backend = "xrender";
    30  vsync = "opengl";
    31  mark-wmwin-focused = true;
    32  mark-ovredir-focused = true;
...

<<<Workaround>>>
downgraded to compton-4.0-1 :smile:
compton-5.1-1 also broken

inxi -Sxx
System:    Host: obxdan-pc Kernel: 5.0.5-1-MANJARO x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: Openbox 3.6.1 
           dm: LightDM Distro: 5.0.5-1-MANJARO

There used to be two that were slow, but they've been removed.
Now there's only the good one: http://manjaro.melbourneitmirror.net/
It's easy to see at https://repo.manjaro.org/ that it updates very frequently.

I did the same as sueridgepipe and edited my mirrorlist.
Have had only melbourneit in it for a long time.

Note: Still have syntax error but compton is running (go figure)

/usr/bin/manjaro-compositor --start
Error when reading configuration file "/home/obxdan/.config/compton.conf", line 29: syntax error
ps -ef |grep compton
obxdan   22614     1  1 08:18 ?        00:00:02 compton -b

Actually, independent of that post, on one of my earlier-updated VMs, i did get those errors & i did fix them by doing that method [i noted it in my CherryTree notes for reference many months ago when i saw @jonathon describe it elsewhere as the "nuclear option"].

Ha, well, take your pick. It's now my 23:23, but i began this process [on VM1] maybe ~15:00... i did say earlier that i've been fighting these dreadful speeds for hours [& hours, &...].

You cheeky thing! Teehee. But seriously, i now have 3 x Testing VMs, 1 x Unstable VM, 3 x Stable VMs, 1 x Testing Tower, & 1 x Stable Lappy. I don't wish to move them all onto any one branch, given my strategy is to be able to test all the branches & provide my own data-points back to the project.

Ta cobber [heehee]. Yes i know this, but [given i'm silly] i edited my .conf file yonks ago to only use https mirrors. That Melb one is only http.
20190404_010

1 Like

What is the recommended way? To keep the current mesa or to "downgrade"?

Probably worth working backwards through the release notes to see relatively recently changed and updated settings. :slightly_smiling_face: For example the default location of compton.conf has changed to ~/.config/compton - although the old location will still work... for now. :smile:

2 Likes

Look in the wiki post of this thread - it's all there :slight_smile:

MATE 1.22 here, overall the update went well but i have some errors i can't manage to resolve.

-- Logs begin at Fri 2019-01-18 09:55:10 CET, end at Thu 2019-04-04 15:48:47 CEST. --
avril 04 15:48:26 xps13 lightdm[898]: gkr-pam: unable to locate daemon control file
avril 04 15:48:29 xps13 systemd-coredump[1118]: Process 1068 (mate-maximus) of user 1000 dumped core.
                                                
                                                Stack trace of thread 1068:
                                                #0  0x00007f8daa8f32ed n/a (libgdk-3.so.0)
                                                #1  0x00007f8daa8f337e gdk_x11_display_error_trap_push (libgdk-3.so.0)
                                                #2  0x00005612aa4dd134 n/a (mate-maximus)
                                                #3  0x00007f8daa04e223 __libc_start_main (libc.so.6)
                                                #4  0x00005612aa4dd1be n/a (mate-maximus)
                                                
                                                Stack trace of thread 1096:
                                                #0  0x00007f8daa11ac21 __poll (libc.so.6)
                                                #1  0x00007f8daa5c0690 n/a (libglib-2.0.so.0)
                                                #2  0x00007f8daa5c077e g_main_context_iteration (libglib-2.0.so.0)
                                                #3  0x00007f8daa5c07d2 n/a (libglib-2.0.so.0)
                                                #4  0x00007f8daa59bc21 n/a (libglib-2.0.so.0)
                                                #5  0x00007f8daa1f5a9d start_thread (libpthread.so.0)
                                                #6  0x00007f8daa125b23 __clone (libc.so.6)
                                                
                                                Stack trace of thread 1099:
                                                #0  0x00007f8daa11ac21 __poll (libc.so.6)
                                                #1  0x00007f8daa5c0690 n/a (libglib-2.0.so.0)

Update went seemingly fine but after a reboot I'm having plasmashell crash upon login. When attempting to start manually via kstart5 plasmashell it crashes shortly after launching. Below is the stdout from a manual launch, and a gdb backtrace of the coredump from the crash:

kstart5 plasmashell stdout:

Fontconfig warning: "/etc/fonts/local.conf", line 10: saw bool, expected number
Fontconfig warning: FcPattern object hintstyle does not accept value True
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:62:5: Unable to assign [undefined] to int
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:53:5: Unable to assign [undefined] to int
kf5.kpackage: No metadata file in the package, expected it at: "/home/ryan/Wallpapers/"
kf5.kpackage: No metadata file in the package, expected it at: "/home/ryan/Wallpapers/"
kf5.kpackage: No metadata file in the package, expected it at: "/home/ryan/Wallpapers/"
trying to show an empty dialog
Added 38 filters
Added 1 files from "file:///home/ryan/Pictures/DSC_0079_v1.jpg"
Nothing in watch list
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:62:5: Unable to assign [undefined] to int
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:53:5: Unable to assign [undefined] to int
kf5.kpackage: No metadata file in the package, expected it at: "/home/ryan/Wallpapers/"
kf5.kpackage: No metadata file in the package, expected it at: "/home/ryan/Wallpapers/"
kf5.kpackage: No metadata file in the package, expected it at: "/home/ryan/Wallpapers/"
trying to show an empty dialog
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:62:5: Unable to assign [undefined] to int
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:53:5: Unable to assign [undefined] to int
kf5.kpackage: No metadata file in the package, expected it at: "/home/ryan/Wallpapers/"
kf5.kpackage: No metadata file in the package, expected it at: "/home/ryan/Wallpapers/"
kf5.kpackage: No metadata file in the package, expected it at: "/home/ryan/Wallpapers/"
trying to show an empty dialog
Fontconfig warning: FcPattern object hintstyle does not accept value True
Fontconfig warning: FcPattern object hintstyle does not accept value True
Fontconfig warning: FcPattern object hintstyle does not accept value True
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
KCrash: Attempting to start /usr/bin/plasmashell from kdeinit
sock_file=/run/user/1000/kdeinit5__0
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 9 and type 'Read', disabling...
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = plasmashell path = /usr/bin pid = 5705
KCrash: Arguments: /usr/bin/plasmashell

plasmashell coredump backtrace:

Reading symbols from /usr/bin/plasmashell...(no debugging symbols found)...done.
[New LWP 5618]
[New LWP 5615]
[New LWP 5625]
[New LWP 5623]
[New LWP 5614]
[New LWP 5616]
[New LWP 5622]
[New LWP 5619]
[New LWP 5624]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000010a90 in ?? ()
[Current thread is 1 (Thread 0x7f103e3a3700 (LWP 5618))]
(gdb) bt
#0  0x0000000000010a90 in  ()
#1  0x00007f10484b254a in call_init.part () at /lib64/ld-linux-x86-64.so.2
#2  0x00007f10484b264a in _dl_init () at /lib64/ld-linux-x86-64.so.2
#3  0x00007f10484b6533 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2
#4  0x00007f1045c38f57 in _dl_catch_exception () at /usr/lib/libc.so.6
#5  0x00007f10484b5dff in _dl_open () at /lib64/ld-linux-x86-64.so.2
#6  0x00007f104581115a in  () at /usr/lib/libdl.so.2
#7  0x00007f1045c38f57 in _dl_catch_exception () at /usr/lib/libc.so.6
#8  0x00007f1045c38ff3 in _dl_catch_error () at /usr/lib/libc.so.6
#9  0x00007f10458118bf in  () at /usr/lib/libdl.so.2
#10 0x00007f10458111fa in dlopen () at /usr/lib/libdl.so.2
#11 0x00007f10460cb40e in  () at /usr/lib/libQt5Core.so.5
#12 0x00007f10460c4f36 in  () at /usr/lib/libQt5Core.so.5
#13 0x00007f10460c5501 in  () at /usr/lib/libQt5Core.so.5
#14 0x00007f10478dc179 in  () at /usr/lib/libQt5Qml.so.5
#15 0x00007f10478dd649 in  () at /usr/lib/libQt5Qml.so.5
#16 0x00007f10478de4f0 in  () at /usr/lib/libQt5Qml.so.5
#17 0x00007f10478de66f in QQmlImports::addLibraryImport(QQmlImportDatabase*, QString const&, QString const&, int, int, QString const&, QString const&, bool, QList<QQmlError>*) () at /usr/lib/libQt5Qml.so.5
#18 0x00007f10478a9992 in QQmlTypeLoader::Blob::addImport(QV4::CompiledData::Import const*, QList<QQmlError>*) () at /usr/lib/libQt5Qml.so.5
#19 0x00007f10478aaa6d in  () at /usr/lib/libQt5Qml.so.5
#20 0x00007f10478ac9c1 in  () at /usr/lib/libQt5Qml.so.5
#21 0x00007f10478a5d9f in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) () at /usr/lib/libQt5Qml.so.5
#22 0x00007f10478a66c0 in QQmlTypeLoader::setData(QQmlDataBlob*, QString const&) () at /usr/lib/libQt5Qml.so.5
#23 0x00007f10478a67fe in QQmlTypeLoader::loadThread(QQmlDataBlob*) () at /usr/lib/libQt5Qml.so.5
#24 0x00007f10478a6a1e in  () at /usr/lib/libQt5Qml.so.5
#25 0x00007f1047919466 in  () at /usr/lib/libQt5Qml.so.5
#26 0x00007f1047919b6a in  () at /usr/lib/libQt5Qml.so.5
#27 0x00007f1046c0fe24 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#28 0x00007f1046c175f1 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#29 0x00007f10460cedf9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#30 0x00007f10460d1ee8 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#31 0x00007f10461256c4 in  () at /usr/lib/libQt5Core.so.5
#32 0x00007f10442b97bf in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#33 0x00007f10442bb739 in  () at /usr/lib/libglib-2.0.so.0
#34 0x00007f10442bb77e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#35 0x00007f1046124c99 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#36 0x00007f10460cda8c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#37 0x00007f1045f11569 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#38 0x00007f1047919109 in  () at /usr/lib/libQt5Qml.so.5
#39 0x00007f1045f1296c in  () at /usr/lib/libQt5Core.so.5
#40 0x00007f1045210a9d in start_thread () at /usr/lib/libpthread.so.0
#41 0x00007f1045bfcb23 in clone () at /usr/lib/libc.so.6

Update went smoothly, no errors during or after on qtile and i3. Thank you!

You either use startx or startkde
The command you used is ok when you are already in the desktop as your user and you want to restart plasma without logging out, and you want to use it as service ...
Also if you did not updated in long time (as i see this is your first post) making the update from TTY is much better. To make sure you didn't end up with a partial update or some corrupted package, run this command from TTY:
sudo pacman-mirrors -f5 && sudo pacman -Syyu
then do a
systemctl reboot
and let the system boot normally and log in.

Forum kindly sponsored by