Manjaro Linux Forum

Announcements => Announcements, Package & Security Advisories => Stable Updates => Topic started by: Kirek on 31. March 2016, 05:26:40

Title: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: Kirek on 31. March 2016, 05:26:40
We are happy to announce our fourteenth update of Manjaro 15.12 (Capella)!

Many kernels updated, Budgie, Calamares 2.2 and a bluez bugfix.
Plasma 5.6.1 and Qt 5.6, Octopi 0.8.1, a fix for Menda gtk3 theme.

Archlinux upstream fixes are now from: Wed Mar 30 20:28:59 CEST 2016.

It is always good to check for updated packages, even we don't notify you
about them. As usual people using our testing branch will help us to get snaps
over to our stable branch almost smoothly. For notifications on daily bases
please take a look at our mailing list:

https://lists.manjaro.org/pipermail/manjaro-packages/

Kind regards,
The Manjaro Development Team

-------------------------------------------------------------------------------

:: Current supported kernels

 - Linux310 3.10.101
 - Linux312 3.12.57
 - Linux313 3.13.11.35
 - Linux314 3.14.65
 - Linux316 3.16.7.25
 - Linux318 3.18.28
 - Linux319 3.19.8.17
 - Linux41  4.1.20
 - Linux42  4.2.8.6
 - Linux43  4.3.6 EOL
 - Linux44  4.4.6
 - Linux45  4.5

-------------------------------------------------------------------------------

:: Package changes

 - stable community i686:  371 new and 344 removed package(s)
 - stable community x86_64:  371 new and 344 removed package(s)
 - stable core i686:  17 new and 17 removed package(s)
 - stable core x86_64:  17 new and 17 removed package(s)
 - stable extra i686:  395 new and 397 removed package(s)
 - stable extra x86_64:  395 new and 397 removed package(s)
 - stable multilib x86_64:  4 new and 5 removed package(s)

https://lists.manjaro.org/pipermail/manjaro-packages/Week-of-Mon-20160328/006561.html
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: grzadr on 31. March 2016, 08:06:29
Everything went smoothly.

I have one question. When nvidia driver will be updated?
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: jesusrop on 31. March 2016, 08:07:05
Hi,

my owncloud sync client is broken now. It can't connect to the server. I think the bug comes from Arch: https://bugs.archlinux.org/task/48764

This is happening in both my laptop and desktop computer. The proposed downgrade  in the above bug report works.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: webstar on 31. March 2016, 08:34:03
Owncloud sync is broken as reported above.

Also dual monitor setup is broken (KDE). The dual monitor configuration is not stored after reboot. So it has to be configured every time. The panel is not on the main monitor as well. Did not find a solution for this so far.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: KabirGandhiok on 31. March 2016, 08:52:04
Smooth update, thanks to the developers. Just one question - since the last few updates I've been getting this message in pamac: "tput: No value for $term and no -T specified", what does this message mean and can anyone help me fix it?

Thanks for helping a newbie!

Code: [Select]
[2016-03-31 11:58] [ALPM] transaction completed
[2016-03-31 11:58] [ALPM] running 'pacli-description.hook'...
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: ruziel on 31. March 2016, 09:38:04
Perfect update on my machine.

Big thanks all round!

Ruziel  ;)
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: robbi3 on 31. March 2016, 10:06:45
Smooth update. plasma is getting better with each update.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: Kirek on 31. March 2016, 10:30:41
Smooth update, thanks to the developers. Just one question - since the last few updates I've been getting this message in pamac: "tput: No value for $term and no -T specified", what does this message mean and can anyone help me fix it?

Thanks for helping a newbie!

Code: [Select]
[2016-03-31 11:58] [ALPM] transaction completed
[2016-03-31 11:58] [ALPM] running 'pacli-description.hook'...
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified
[2016-03-31 11:58] [ALPM-SCRIPTLET] tput: No value for $TERM and no -T specified

It was reported that it was caused by the package "pacli", removing should fix it.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: Fatboy on 31. March 2016, 10:39:46
Epic update, as usual :D

One thing did change though. My conky's text changed from Cantarell to something else (mono/typewriter type font), unbolded and everthing?
Weird.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: perpf on 31. March 2016, 10:40:25
Plasma update to 5.6.1 went remarkably well. Very impressive.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: KabirGandhiok on 31. March 2016, 10:46:01
It was reported that it was caused by the package "pacli", removing should fix it.

@Kirek, thanks for responding! I tried removing pacli, but the transaction did not go through. If removing pacli breaks dependency then is it safe to remove it?

Code: [Select]
[kabir@manjaro ~]$ sudo pacman -Ss pacli
[sudo] password for kabir:
community/pacli 0.8-1 [installed]
    An interactive pacman interface using fzf
community/pacli-jwm 0.1-1
    an interactive pacman interface using pmenu
[kabir@manjaro ~]$ sudo pacman -Rsn pacli
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: bmenu: removing pacli breaks dependency 'pacli'
[kabir@manjaro ~]$ sudo pacman -R pacli
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: bmenu: removing pacli breaks dependency 'pacli'
[kabir@manjaro ~]$

Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: emmedi on 31. March 2016, 10:59:29
plasmashell not work

My desktop: http://s14.postimg.org/58q8m36i9/plasmanotwork.png

Code: [Select]
[emmedi@pc ~]$ plasmashell
kscreen: starting external backend launcher for ""
org.kde.plasma: unversioned plugin detected, may result in instability
org.kde.plasma: unversioned plugin detected, may result in instability
org.kde.plasma: unversioned plugin detected, may result in instability
org.kde.plasma: unversioned plugin detected, may result in instability
org.kde.plasma: unversioned plugin detected, may result in instability
org.kde.plasma: unversioned plugin detected, may result in instability
org.kde.plasma: unversioned plugin detected, may result in instability
org.kde.plasma: unversioned plugin detected, may result in instability
org.kde.plasma: unversioned plugin detected, may result in instability
No metadata file in the package, expected it at: "/usr/share/wallpapers/EveningGlow/contents/images//metadata.desktop"
No metadata file in the package, expected it at: "/usr/share/wallpapers/EveningGlow/contents/images//metadata.desktop"
No metadata file in the package, expected it at: "/usr/share/wallpapers/EveningGlow/contents/images//metadata.desktop"
file:///usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/main.qml:38: TypeError: Cannot read property 'Layout' of null
file:///usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/main.qml:39: TypeError: Cannot read property 'Layout' of null
KActivities: Database connection:  "kactivities_db_resources_140146990680064_readonly"
    query_only:          QVariant(qlonglong, 1)
    journal_mode:        QVariant(QString, "wal")
    wal_autocheckpoint:  QVariant(qlonglong, 100)
    synchronous:         QVariant(qlonglong, 0)
Could not resolve property : radialGradient4857
Could not resolve property : radialGradient4857
Could not resolve property : radialGradient4857
Could not resolve property : radialGradient4857
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
file:///usr/lib/qt/qml/org/kde/plasma/extras/ScrollArea.qml:48: Error: Cannot assign to non-existent property "interactive"
file:///usr/lib/qt/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null
file:///usr/lib/qt/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null
file:///usr/lib/qt/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:220: TypeError: Cannot read property '0' of undefined
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:209: TypeError: Cannot read property '0' of undefined
file:///usr/lib/qt/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null
KCrash: Attempting to start /usr/bin/plasmashell from kdeinit
sock_file=/run/user/1000/kdeinit5__0
KCrash: Application 'plasmashell' crashing...
KCrash: Attempting to start /usr/lib/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 21 and type 'Read', disabling...

[1]+  Fermato                 plasmashell
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: lightbeam on 31. March 2016, 11:00:54
Rebooting after updating caused a kernel panic - with current kernel Linux45 - so I shut down the computer and restarted.  For the moment, things seem to be *OK*, but I've been experiencing some issues recently that might be due to past updates -- don't know for sure if *everything* is working as it should.

However, I did get this message in dmesg, after restarting the computer, after the kernel panic. This was the first time that this message has ever appeared:

Code: [Select]
[   12.052487] systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:00:14.1\x2data\x2d2.device: Dev dev-disk-by\x2dpath-pci\x2d0000:00:14.1\x2data\x2d2.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.1/ata2/host1/target1:0:0/1:0:0:0/block/sr0 and /sys/devices/pci0000:00/0000:00:14.1/ata2/host1/target1:0:1/1:0:1:0/block/sr1
Can any of the Head Honchos tell me what that means?

Update #1: OK, as far as I know, /dev/sr0 and /dev/sr1 are the respective locations of the DVD and CD optical drives.  But I have no idea about the rest of that message. "x2d2.device"?  What is that?!   ???

Update #2:   In response to the dmesg message listed above, I decided to test all of kernels installed on my machine to see if that message repeated across those kernels, and I also installed Linux44 to see if it, too, produced the same message:


So, Core Team Czars, what might this latest dmesg doohickey be about?
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: papajoke on 31. March 2016, 11:01:57
@KabirGandhiok (https://forum.manjaro.org/index.php?action=profile;u=14145)


dont remove pacli , just this command for fix :
Code: [Select]
sudo rm /etc/pacman.d/hooks/pacli-description.hookor update pacli from AUR
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: Esclapion on 31. March 2016, 11:10:14
No problem, thanks.  :)

Thursday, now ?  ;D
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: KabirGandhiok on 31. March 2016, 11:39:00
@KabirGandhiok (https://forum.manjaro.org/index.php?action=profile;u=14145)


dont remove pacli , just this command for fix :
Code: [Select]
sudo rm /etc/pacman.d/hooks/pacli-description.hookor update pacli from AUR

@papajoke

Thanks! :D I used that command.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: fdc1b on 31. March 2016, 12:20:48
No problem. Good work!  ;D
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: viking60 on 31. March 2016, 12:26:53
I get this:
Code: [Select]
error: failed to commit transaction (conflicting files)
ki18n: /usr/share/locale/nb/LC_SCRIPTS/ki18n5/ki18n5.js exists in filesystem
qt5-tools: /usr/lib/qt/bin/qdoc exists in filesystem
Errors occurred, no packages were upgraded.

Do we have a recipe for it?
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: miku on 31. March 2016, 12:28:31
Good update, no issues.
Anyone has tried to use the nem breeze-grub package? I have not tried it yet, but found info how to do it.

http://kde-look.org/content/show.php/Breeze+GRUB2+theme?content=171217
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: Esmaeil Elqenawy on 31. March 2016, 12:31:59
Smooth Update
Thanks All
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: oberon on 31. March 2016, 12:35:09
Do we have a recipe for it?
No/Yes ;)
pacman -Qo <path/to/the/conflicting/file> will tell you which package has installed that file. If no package owns the file you might have created it somehow differently...
After that you have to decide if you want to keep the file for whatever reason or move it somewhere in case you need it later.
Then pacman -S --force <the complaining package> should update the package and overwrite the conflicting file.
If that fails you can still remove the conflicting file manually, or uninstall the package owning the conflicting file.
This should only be the case if we missed to specify a conflict in our package, so please let us know - or the conflict is a package from the AUR... that can happen ;)
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: boletus on 31. March 2016, 12:51:06
Epic update, as usual :D

One thing did change though. My conky's text changed from Cantarell to something else (mono/typewriter type font), unbolded and everthing?
Weird.

Good update for me, except for this conky behaviour, exactly the same.
I'm using the new "conky-lua-nv" since it reached the stable repos, and it worked perfectly even with the old conky sintax until the current upgrade.

Anybody else with that?
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: Fatboy on 31. March 2016, 12:52:31
Same conky here. Also, when I execute conky from a terminal I get an error message: can't load xft font
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: oberon on 31. March 2016, 12:54:26
I'm using the new "conky-lua-nv" since it reached the stable repos, and it worked perfectly even with the old conky sintax until the current upgrade.
What does that mean? What happened with today's update? conky-lua-nv was not changed!
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: scachemaille on 31. March 2016, 12:59:09
Good update, no issues.
Anyone has tried to use the nem breeze-grub package? I have not tried it yet, but found info how to do it.

http://kde-look.org/content/show.php/Breeze+GRUB2+theme?content=171217
Just tried on my VM, it would maybe just need to change the manjaro logo with a green one.. ;)
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: miku on 31. March 2016, 13:00:32
Just tried on my VM
Looks OK :)
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: viking60 on 31. March 2016, 13:03:22
No/Yes ;)
pacman -Qo <path/to/the/conflicting/file> will tell you which package has installed that file. If no package owns the file you might have created it somehow differently...
After that you have to decide if you want to keep the file for whatever reason or move it somewhere in case you need it later.
Then pacman -S --force <the complaining package> should update the package and overwrite the conflicting file.
If that fails you can still remove the conflicting file manually, or uninstall the package owning the conflicting file.
This should only be the case if we missed to specify a conflict in our package, so please let us know - or the conflict is a package from the AUR... that can happen ;)

Letting you know:  ^-^

/usr/lib/qt/bin/qdoc was owned by qt5-base-dev-git 5.5.1.r134.gb5ea7a5-1 - I deleted the file - Berserk style.

/usr/share/locale/nb/LC_SCRIPTS/ki18n5/ki18n5.js was owned by kde-l10n-nb - I deleted it.

I don't have KDE on this box but I have tested it so it might be a leftover.

This is probably mostly because of my fiddling around but it could be that the global nb locale has been discriminated by the KDE guys too.

After that the update went through - thanks!

 

Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: boletus on 31. March 2016, 13:08:32
What does that mean? What happened with today's update? conky-lua-nv was not changed!

I know it, but when I rebooted the system after the today's update, the conky text is changed. Your package has been working perfectly until today
There must be one upgraded package that cause this strange issue.

I was thinking this:   lib32-fontconfig 2.11.1-1 > 2.11.94-1
I downgraded the package, but nothing is changed  :'(
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: oberon on 31. March 2016, 13:20:00
the conky text is changed.
I was thinking this:   lib32-fontconfig 2.11.1-1 > 2.11.94-1
I downgraded the package, but nothing is changed  :'(
Yes. fontconfig is a good idea! But you should downgrade fontconfig AND the lib32 !! Try that, please!
Also afterwards do a
Code: [Select]
fc-cache -f
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: oberon on 31. March 2016, 13:36:02
I must say that I don't have any problems with the latest conky and fontconfig packages.
In my config (in the updated syntax) I am using
Code: [Select]
font = 'Bitstream Vera Sans:size=8',
use_xft = true,
Have a closer look at the way you define your fonts there, maybe?
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: boletus on 31. March 2016, 13:40:33
Yes Oberon, and thanks a lot, I was completely missed to downgrade fontconfig, I had just downgrade lib32-fontconfig.

In short:
downgraded fontconfig (2.11.94-1 -> 2.11.1-2)
downgraded lib32-fontconfig (2.11.94-1 -> 2.11.1-1)

This solved my conky issue
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: boletus on 31. March 2016, 13:54:51
@Oberon
I used old and new conky sintax to solve, but nothing changed, the fonts were wrong in both configurations, only the downgrade of these 2 packages solved the problem.



Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: g33zr on 31. March 2016, 14:58:30
Perfect!  :)
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: emmedi on 31. March 2016, 15:07:44
plasmashell not work
Solution: remove or rename ~/.config/plasma-org.kde.plasma.desktop-appletsrc.*
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: oberon on 31. March 2016, 15:11:16
@boletus, @Fatboy are you both trying to use Cantarell? Or other fonts not working either?
As you can see in my example, I have defined " font = " , not " xftfont = " and for me it works normally.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: AHatLikeThat on 31. March 2016, 15:42:07
Since applying the update I am unable to restart or shut down.
I have tried changing the themes to fix this. Upon doing so, I noticed my splash screen had been changed from Breeze to "empty", however changing it back, or using any of the other themes makes no difference.

This is the error I get upon attempted power off.
Quote
3/31/16 7:32 AM   ksmserver   Shutdown called with confirm  -1  type  2  and mode  -1
3/31/16 7:32 AM   kwin_x11   QXcbConnection: XCB error: 9 (BadDrawable), sequence: 42300, resource id: 0, major code: 14 (GetGeometry), minor code: 0
3/31/16 7:32 AM   kwin_x11   QXcbConnection: XCB error: 9 (BadDrawable), sequence: 42301, resource id: 0, major code: 14 (GetGeometry), minor code: 0
3/31/16 7:32 AM   kwin_x11   QXcbConnection: XCB error: 9 (BadDrawable), sequence: 42310, resource id: 0, major code: 14 (GetGeometry), minor code: 0
3/31/16 7:32 AM   kwin_x11   QXcbConnection: XCB error: 9 (BadDrawable), sequence: 42311, resource id: 0, major code: 14 (GetGeometry), minor code: 0
3/31/16 7:32 AM   kwin_x11   QXcbConnection: XCB error: 9 (BadDrawable), sequence: 42312, resource id: 0, major code: 14 (GetGeometry), minor code: 0
3/31/16 7:32 AM   kwin_x11   QXcbConnection: XCB error: 9 (BadDrawable), sequence: 42321, resource id: 0, major code: 14 (GetGeometry), minor code: 0
3/31/16 7:32 AM   kwin_x11   QXcbConnection: XCB error: 9 (BadDrawable), sequence: 42322, resource id: 0, major code: 14 (GetGeometry), minor code: 0
3/31/16 7:32 AM   kwin_x11   QXcbConnection: XCB error: 9 (BadDrawable), sequence: 42323, resource id: 0, major code: 14 (GetGeometry), minor code: 0
3/31/16 7:32 AM   kwin_x11   QXcbConnection: XCB error: 9 (BadDrawable), sequence: 42324, resource id: 0, major code: 14 (GetGeometry), minor code: 0
3/31/16 7:32 AM   kwin_x11   QXcbConnection: XCB error: 9 (BadDrawable), sequence: 42331, resource id: 0, major code: 14 (GetGeometry), minor code: 0
3/31/16 7:32 AM   kwin_x11   QXcbConnection: XCB error: 9 (BadDrawable), sequence: 42342, resource id: 0, major code: 14 (GetGeometry), minor code: 0

I am afraid to shut down with a hard reset, for fear that the lack of a spash screen will prevent me from getting back in. What can I do?
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: kouros17 on 31. March 2016, 15:51:54
Did you try to restart or shutdown from terminal?
Run "reboot" for restart or "poweroff" for shutdown.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: alissonsuassuna on 31. March 2016, 16:22:08
Hello community this morning , called PC as I always do and I noticed it had new updates of the system , well I open my terminal and type the following command
sudo pacman -Syyuu , the updated system good all ok , more and when I opened my browser saw all stand, the letters all crazy , I tried various forms fix sources of my most did not succeed browser either firefox like Google Chrome - and also the chromim letters are all bugged , ask for help and tBM warn developers about this bug

sorry my inglês, not speak good, I'm from Brazil !!!
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: AHatLikeThat on 31. March 2016, 16:34:30
Thank you, kouros17. "reboot" from terminal did the trick. I am now able to use the reboot/power off keys on the screen.
Everything seems to be working correctly, though ksystemlog shows a lot of errors for plasma shell and kwin_X11. I am new to linux and only started looking at the system log because of the problems today after the update. Is it normal to have errors like that, should I ignore them?
Examples:
Code: [Select]
3/31/16 8:32 AM plasmashell QXcbConnection: XCB error: 2 (BadValue), sequence: 4992, resource id: 100663427, major code: 142 (Unknown), minor code: 3
3/31/16 8:27 AM kwin_x11 QXcbConnection: XCB error: 3 (BadWindow), sequence: 36298, resource id: 98566145, major code: 18 (ChangeProperty), minor code: 0

Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: beardedragon on 31. March 2016, 16:34:38
Good Stable update, no problems, thanks Team.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: CyberWolf2k14 on 31. March 2016, 17:08:00
Semi-large update, but went VERY smoothly. No issues at all.
So, once again, major kudos to the devs.  8)
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: nilssn on 31. March 2016, 17:08:45
Big Plasma 5/Qt update. No problem so far :)
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: Nergal on 31. March 2016, 17:40:28
Yet again smooth update on two systems.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: miku on 31. March 2016, 17:43:48
Just tried on my VM, it would maybe just need to change the manjaro logo with a green one.. ;)
Could you post the grub.cfg and what else do you did? I could not find the wallpaper.
Thanks in advance!
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: scachemaille on 31. March 2016, 17:54:02
Could you post the grub.cfg and what else do you did? I could not find the wallpaper.
Thanks in advance!
I extracted/copied the breeze foler in (as root)
Code: [Select]
/boot/grub/themes/and I modified grub config (near the end of file)
Code: [Select]
sudo nano /etc/default/grub I commented
Code: [Select]
#GRUB_BACKGROUND="/usr/share/grub/background.png"and removed comment and change the path to the breeze theme for
Code: [Select]
GRUB_THEME="/boot/grub/themes/breeze"and when all is done.
Code: [Select]
sudo update-grub
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: AHatLikeThat on 31. March 2016, 17:59:07
Well, crap, this is a problem.
UPDATED: Grub no longer sees my Windows disk. The grub bootloader is on /sda (where it was always installed). Linux is on a separate disk, /sdb. Grub is accessing the bootloader on the Windows disk, but then lists only the second disk as an option at boot. Can someone please help with this? I have BIOS. If the update is not the cause of this (though the problem just appeared after the update) pleasemove this to a more appropriate location.

UPDATED 2: Fixed using the grub restore instructions in the wiki. Not sure why my update has been so problematic when so many are having smooth experiences. Newbie curse?

Ignore the below:
 After the update and also updating the kernal, it appears that grub has moved itself to my second disk(the one with Manjaro), and now does not see my first disk (the one with Windows).

When I installed Majaro originally, grub properly installed itself on the windows disk, but now I have no way of booting to windows.

I tried selecting the older kernal from the advanced start options, but this had no effect. Honestly I do not recall if the windows boot option was there before I updated the kernal (after the system update) because I was too concerned with not being able to reboot Linux.
Help!
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: notargets on 31. March 2016, 18:24:37
Everything went smoothly except for one thing: whenever mpv is playing a video, even in windowed mode, the KWin compositor is temporarily disabled in Plasma 5.6.1. According to this (https://github.com/mpv-player/mpv/issues/2997), this is due to a new feature in Plasma rather than a bug, but I would be happier if the compositor was disabled only when I want to do it manually.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: minMax3 on 31. March 2016, 18:55:19
All went well for me,
Plasma keeps getting better.
KDE - linux45 & 16.06 Pre1

To the devs, thanks.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: AJSlye on 31. March 2016, 19:14:35
Everything went smoothly except for one thing: whenever mpv is playing a video, even in windowed mode, the KWin compositor is temporarily disabled in Plasma 5.6.1. According to this (https://github.com/mpv-player/mpv/issues/2997), this is due to a new feature in Plasma rather than a bug, but I would be happier if the compositor was disabled only when I want to do it manually.


This was added so that when an application like 3d games and movies are running the compositor doesn't slow them down by taking up resources these applications need (aka hardware acceleration). Plasma also disables screen blanking and power management when playing movies even in firefox, media players, etc., It's not the application doing this but KF5 itself (solid, etc).
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: notargets on 31. March 2016, 20:35:23

This was added so that when an application like 3d games and movies are running the compositor doesn't slow them down by taking up resources these applications need (aka hardware acceleration). Plasma also disables screen blanking and power management when playing movies even in firefox, media players, etc., It's not the application doing this but KF5 itself (solid, etc).

I've made comparisons of performance while playing games with and without the compositor in the past, and, to be honest, I never noticed any difference. (It may be because the AMD drivers have a bottleneck somewhere with my HD6670, I don't know.) The only difference I noticed was when XRender was used instead of OpenGL, which gave a considerable performance boost. I also remember that Commandos BEL and BTCOD actually always ran much worse in Wine when the compositor was disabled.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: salome on 31. March 2016, 20:50:21
Another update went smooth! Thank you guys!
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: deemde on 31. March 2016, 20:51:33
I am experiencing owncloud breakage, too. Was able to resolve it by deleting my login and adding it back again.
Other than that, a very smooth update. Thank you Manjaro!
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: Zenny422 on 31. March 2016, 21:14:51
Hello Manjaroneers , I have a problem with Knotes , I have no access to old knotes. New ones work fine is there s solution for this ?

Dropbox still missing form taskbar

WINE programs from startup still slow

Otherwise everything oK
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: jonathon on 31. March 2016, 21:21:59
I have one question. When nvidia driver will be updated?

When it's ready.
Title: font issues with conky and youtube
Post by: theMuspilli on 31. March 2016, 21:23:16
Also I encountered the problem that one of my 5 conky configs did not start up properly because of font problems, and moreover youtube pages would not show in proper design, but like in a textmode browser without table support. Switching through some stylish themes for yt, I found one that works (galaxy) and therefore concluded that it really had to be some issue with the fonts.

After following the advice of @oberon and @boletus yt shows up normal again - also in vanilla mode and with all stylish themes that I have installed. The conky I cannot test at the moment, because it relies on a monitor configuration that is not available to me atm. But I would expect that there the issue is solved, too.

greets
Title: KDE broken?
Post by: Twenex on 31. March 2016, 21:41:49
Hi,

This latest update has broken KDE for me; startkde appears to be empty:

Code: (html5) [Select]
zsh: exec format error: startkde
and the default DM for Manjaro KDE (sddm?) no longer boots.

Also, although Kernel 4.5 works. 4.4 boots to single user only.

Please let me know what other info, if any, you require.

Thanks,

Jeff.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: kalin on 31. March 2016, 22:10:26
Any idea ?
Code: [Select]
error: failed to commit transaction (conflicting files)
virt-install: /usr/share/virt-manager/virtcli/__init__.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtcli/cliconfig.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/__init__.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/capabilities.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/cli.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/clock.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/cloner.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/connection.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/cpu.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/device.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/deviceaudio.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicechar.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicecontroller.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicedisk.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicefilesystem.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicegraphics.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicehostdev.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/deviceinput.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/deviceinterface.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicememballoon.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicepanic.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/deviceredirdev.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicerng.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicesmartcard.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicetpm.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicevideo.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicewatchdog.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/diskbackend.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/distroinstaller.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/domainblkiotune.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/domainfeatures.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/domainmemorybacking.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/domainmemorytune.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/domainnumatune.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/domainresource.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/domcapabilities.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/guest.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/hostkeymap.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/idmap.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/installer.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/interface.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/network.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/nodedev.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/osdict.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/osxml.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/pm.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/pollhelpers.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/progress.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/seclabel.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/snapshot.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/storage.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/support.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/uri.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/urlfetcher.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/util.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/xmlbuilder.pyc exists in filesystem
Errors occurred, no packages were upgraded.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: eugen-b on 31. March 2016, 22:19:17
@kalin, install the problematic package with sudo pacman -S --force <package>
This will overwrite the existing files.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: kalin on 31. March 2016, 22:25:42
How to understand which package is the problematic ?
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: jonathon on 31. March 2016, 22:28:09
Any idea ?

http://www.google.com/?q=pacman+conflicting+files

How to understand which package is the problematic ?

pacman -Qo /usr/share/virt-manager/virtcli/__init__.pyc

Or, take a wild (wild) guess that it's 'virt-manager'
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: eugen-b on 31. March 2016, 22:30:42
Take a look at /var/log/pacman.log at the end of the log file. You should see during the upgrade of which package the errors occured. Or do as jonathon suggested. ;) But the package name should be 'virt-install', I took a look at Octopi.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: BS86 on 31. March 2016, 22:42:21
Solution: remove or rename ~/.config/plasma-org.kde.plasma.desktop-appletsrc.*

thanks, that also solved my broken KDE desktop that was only showing the mouse pointer after an enormous time that it hang on the loadscreen
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: jonathon on 31. March 2016, 22:42:50
But the package name should be 'virt-install', I took a look at Octopi.

Hmm - I'm not so sure.

Code: [Select]
1 community/virt-manager 1.3.2-4
    Desktop user interface for managing virtual machines

1 community/virt-install 1.3.2-4
    Desktop user interface for managing virtual machines

File path being "/usr/share/virt-manager" would point to virt-manager; However, I have no issue when I installed them both just now (`pacman -S virt-manager virt-install`).
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: fredhoud on 31. March 2016, 23:06:12
No problem with any of my computers with the update itself, but the occasional annoying 1:45 min delay still there after you turn off the computer. It doesn't happen all the time, but hangs occasionally. I was hoping the Plasma 5.6 would have fixed this issue, but not so far.

Thank you.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: flipper on 31. March 2016, 23:30:18
No problem with any of my computers with the update itself, but the occasional annoying 1:45 min delay still there after you turn off the computer. It doesn't happen all the time, but hangs occasionally. I was hoping the Plasma 5.6 would have fixed this issue, but not so far.

Thank you.

Now I am curious if you have any networkshares mounted with fstab. If so, maybe the system hangs not being able to unmount them properly.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: fredhoud on 31. March 2016, 23:42:23
Now I am curious if you have any networkshares mounted with fstab. If so, maybe the system hangs not being able to unmount them properly.

No, I have no networkshares, except I a few shared-folders via Dropbox.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: AJSlye on 31. March 2016, 23:44:52
No, I have no networkshares, except I a few shared-folders via Dropbox.

Dropbox is a network share, it's a Wan rather than a Lan share, but still.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: fredhoud on 01. April 2016, 00:18:50
Dropbox is a network share, it's a Wan rather than a Lan share, but still.

Is there any trick/s to shutdown properly, or to disconnect from network?
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: Ars Technis on 01. April 2016, 00:22:03
Nice update ! Everything's fine excepted a little visual glitch on firefox-kde/thunderbird-kde title bar sometimes.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: eugen-b on 01. April 2016, 00:37:07
Is there any trick/s to shutdown properly, or to disconnect from network?
/etc/systemd/system.conf -> DefaultTimeoutStopSec=10s
But I don't know how it will play with your network.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: Zenny422 on 01. April 2016, 00:38:35
Update This is how i fixed old Knote that showed up black. Copy and paste text to new Knote. Everything is back normal.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: linuxbf13 on 01. April 2016, 01:06:27
Hello,

I have just updated and after reboot I have not been able to boot system. I have enclosed picture. Can anyone help?

Thank you.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: Foxwater on 01. April 2016, 01:53:34
Smooth update both KDE & Xfce. Thank you
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: fredhoud on 01. April 2016, 03:11:40
/etc/systemd/system.conf -> DefaultTimeoutStopSec=10s
But I don't know how it will play with your network.

I get an error when I try to save it. It says "the document could not be saved, as it was not possible to write to etc/systemd/system.conf. Check that you have write access to this file or that enough disk space is available", and I have plenty of disk space.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: AJSlye on 01. April 2016, 03:20:02
I get an error when I try to save it. It says "the document could not be saved, as it was not possible to write to etc/systemd/system.conf. Check that you have write access to this file or that enough disk space is available", and I have plenty of disk space.

Seriously fredhound, it's a system file. LOL. ;)
Code: [Select]
sudo /etc/systemd/system.conf -> DefaultTimeoutStopSec=10s
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: fredhoud on 01. April 2016, 03:28:36
Seriously fredhound, it's a system file. LOL. ;)
Code: [Select]
sudo /etc/systemd/system.conf -> DefaultTimeoutStopSec=10s

I get this:
sudo: /etc/systemd/system.conf: command not found
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: AJSlye on 01. April 2016, 03:35:45
I get this:
sudo: /etc/systemd/system.conf: command not found

OK then do this:
Code: [Select]
sudo nano /etc/systemd/system.confadd:
Code: [Select]
DefaultTimeoutStopSec=10sand save. ;)
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: fredhoud on 01. April 2016, 03:46:35
OK then do this:
Code: [Select]
sudo nano /etc/systemd/system.confadd:
Code: [Select]
DefaultTimeoutStopSec=10sand save. ;)

I changed it, but I don't see how you save and exit.  ???
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: c00ter on 01. April 2016, 03:49:41
No problem with any of my computers with the update itself, but the occasional annoying 1:45 min delay still there after you turn off the computer. It doesn't happen all the time, but hangs occasionally. I was hoping the Plasma 5.6 would have fixed this issue, but not so far.

Thank you.

Yep, it's still there as you found out. The way around it remains the same. Edit /etc/systemd/system.conf as root. Change these two lines...

Quote
#DefaultTimeoutStartSec=90s
#DefaultTimeoutStopSec=90s
to this

Quote
DefaultTimeoutStartSec=10s
DefaultTimeoutStopSec=10s

Save, and reboot. The first time rebooting after changing those lines, you'll probably still get the 1:30 timeout, but never again.

Regards
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: AJSlye on 01. April 2016, 03:51:59
I changed it, but I don't see how you save and exit.  ???

The commands are along the bottom:
ctrl o (write out or save)
ctrl x (exit)
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: c00ter on 01. April 2016, 03:55:45
The commands are along the bottom:
ctrl o (write out or save)
ctrl x (exit)

Nano, nanoo! :D
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: jack_howels on 01. April 2016, 04:02:48
I updated at the university today (UCR) and after several issues where manjaro stopped downloading the packages due to them being labeled as corrupted (probably due to a bad internet connection) I finally managed to update, discarding and re-downloading, the problem was that Manjaro didn't manage to shutdown after the update. It did suspend, lock session and permited to surf the internet but when the shutdown or the restard botton where clicked it just froze for some seconds and then when I tried again the 30 seconds shutdown window or restart were not displayed.

I checked if the download went well and pacman reported everything as up to date.

When I checked Dolphin file manager froze too and didn't let me search for my files by the gui interface, by console everything worked, after using the console to shutdown the system and then restarted, Manjaro hasn't presented any further issue.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: kb41 on 01. April 2016, 04:13:26
So far so good I updated my desktop and my test lab at work with no problems. What happened to the Monday updates? Is Thursday th enew update day now?
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: fredhoud on 01. April 2016, 04:24:19
The commands are along the bottom:
ctrl o (write out or save)
ctrl x (exit)

I changed it to 10 seconds, and restarted several times, but the delay still exits. This is not as bad on my desktop with NVIDIA graphics, but it's worse on my laptop with Intel graphics. It may has something to do with the encryption, because I get the following message when it's hanging:

Starting version 229
A password is required to access the encrytManjaro volume:
ManjaroRoot: clean 332249/15114240 file, 13851048/60426496 blocks

Then it shuts down after a minute or two.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: iKreate on 01. April 2016, 06:30:54
everything seems fine....
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: Nergal on 01. April 2016, 08:24:19
No problem with any of my computers with the update itself, but the occasional annoying 1:45 min delay still there after you turn off the computer. It doesn't happen all the time, but hangs occasionally. I was hoping the Plasma 5.6 would have fixed this issue, but not so far.

Thank you.

I remember seeing a bug report for systemd about this. If I remember correctly it is related to polkit and some delay between systemd and plasma not communicating shutdown sequences properly.

I have this same annoying delay on desktop (nvidia) and laptop (intel/nvidia). Both are using plasma 5.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: fsimerey on 01. April 2016, 08:37:07
Hi, i have conflicts for upgrading some python2 packages:
Code: [Select]
(132/132) checking for file conflicts                                             [##############################################] 100%
error: failed to commit transaction (conflicting files)
python2-idna: /usr/lib/python2.7/site-packages/idna/intranges.py exists in filesystem
python2-idna: /usr/lib/python2.7/site-packages/idna/intranges.pyc exists in filesystem
python2-cryptography: /usr/lib/python2.7/site-packages/cryptography-1.3.1-py2.7.egg-info/PKG-INFO exists in filesystem
python2-cryptography: /usr/lib/python2.7/site-packages/cryptography-1.3.1-py2.7.egg-info/SOURCES.txt exists in filesystem
python2-cryptography: /usr/lib/python2.7/site-packages/cryptography-1.3.1-py2.7.egg-info/dependency_links.txt exists in filesystem
python2-cryptography: /usr/lib/python2.7/site-packages/cryptography-1.3.1-py2.7.egg-info/entry_points.txt exists in filesystem
python2-cryptography: /usr/lib/python2.7/site-packages/cryptography-1.3.1-py2.7.egg-info/not-zip-safe exists in filesystem
python2-cryptography: /usr/lib/python2.7/site-packages/cryptography-1.3.1-py2.7.egg-info/requires.txt exists in filesystem
python2-cryptography: /usr/lib/python2.7/site-packages/cryptography-1.3.1-py2.7.egg-info/top_level.txt exists in filesystem
python2-pyopencl: /usr/lib/python2.7/site-packages/pyopencl-2015.2.4-py2.7.egg-info/PKG-INFO exists in filesystem
python2-pyopencl: /usr/lib/python2.7/site-packages/pyopencl-2015.2.4-py2.7.egg-info/SOURCES.txt exists in filesystem
python2-pyopencl: /usr/lib/python2.7/site-packages/pyopencl-2015.2.4-py2.7.egg-info/dependency_links.txt exists in filesystem
python2-pyopencl: /usr/lib/python2.7/site-packages/pyopencl-2015.2.4-py2.7.egg-info/not-zip-safe exists in filesystem
python2-pyopencl: /usr/lib/python2.7/site-packages/pyopencl-2015.2.4-py2.7.egg-info/requires.txt exists in filesystem
python2-pyopencl: /usr/lib/python2.7/site-packages/pyopencl-2015.2.4-py2.7.egg-info/top_level.txt exists in filesystem
python2-pytz: /usr/lib/python2.7/site-packages/pytz/zoneinfo/Asia/Barnaul exists in filesystem
python2-pytz: /usr/lib/python2.7/site-packages/pytz/zoneinfo/Europe/Astrakhan exists in filesystem
python2-pytz: /usr/lib/python2.7/site-packages/pytz/zoneinfo/Europe/Ulyanovsk exists in filesystem
Errors occurred, no packages were upgraded.

Any idea how to fix this ?
Thanks
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: fsimerey on 01. April 2016, 09:14:54
I have found the problem, those packages were installed with pip. Uninstall via pip solved the problem.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: varikonniemi on 01. April 2016, 09:20:06
no problems on xfce.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: mauve002 on 01. April 2016, 10:15:37
The update process and reboot went smoothly on 3 different computers, but kernel 4.5 has a new outstanding bug when it comes to sleeping or hibernating. On the 3 machines (all different : an older legacy bios HP core 2 duo, a newer HP UEFI core i3 13x360 convertible and a dell i3 optiplex 980), sleeping or hibernating the computers leads to irrecoverable coma, screen blank but still lit, fans still spinning, brain dead. Rebooting shows fsck recovering the fs journal. Switching back to kernel 4.4LTS seems to fix the issue.

M.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: joshuadunamis on 01. April 2016, 10:34:18
No issues. Everything OK!!!
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: CyBeRmIdGeT on 01. April 2016, 11:13:22
The update went fine except Airvpn (Portable version) will not run, how do I rollback the update?

It worked fine before the update

Thanks
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: ottomops on 01. April 2016, 12:08:20
I am experiencing owncloud breakage, too. Was able to resolve it by deleting my login and adding it back again.
Other than that, a very smooth update. Thank you Manjaro!

I am having persistent problems with Owncloud client here.

I tried downgrading to 2.1.1-1 as reported here

https://bugs.archlinux.org/task/48764

but can't find qtkeychain-qt5 0.5-2 anywhere. So oc-client 2.1.1.-1 is not even starting in KDE with the current qtkeychain. So I reinstalled the current oc-client version and disconnected/reconnected from my owncloud account. That worked momentarily, but after a reboot same problem again...

Anybody got it fixed?

Thanks.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: Strit on 01. April 2016, 12:22:53
I did also have the ownCloud issue, but it seems that my owncloud daemon is still running and syncing in the background. I also get a "another Client is already running" when trying to launch owncloud from terminal, so it just seems that the tray icon is missing on my system.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: ottomops on 01. April 2016, 12:32:14
Sucessfully downgraded to owncloud client 2.1.1-1 now...

First I downloaded qtkeychain-qt5 0.5-2 here

https://archive.archlinux.org/packages/q/qtkeychain-qt5/

Then I downgraded owncloud client to 2.1.1-1

Code: [Select]
sudo downgrade owncloud-client
Then I installed the downloaded qtkeychain version using

Code: [Select]
sudo pacman -U qtkeychain-qt5-0.5-2-x86_64.pkg.tar.xz
Owncloud client is working now as before  :P
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: kb41 on 01. April 2016, 12:43:46
Tried to update my main laptop but the root partition was full so I deleted some stuff so I could  run the update. That worked but my root partition was still full so I did a search on the forum and found out cache was huge it was about 22GB was that was cleared out evreything is back to normal. Anyway greta update as usual
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: mikronimo on 01. April 2016, 13:13:51
Huston... we have not any problem... thanks!
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: boletus on 01. April 2016, 14:03:41
@boletus, @Fatboy are you both trying to use Cantarell? Or other fonts not working either?
As you can see in my example, I have defined " font = " , not " xftfont = " and for me it works normally.

I don't use Cantarell font, I'm using a mix of Bitstream Vera Sans and Ubuntu fonts.
Anyway I have updated my second machine and same story, I needed to make a downgrade again, this time only the fontconfig package, and not lib32-fontconfig.

The 3 of us who reported this issue (fatboy, theMuspilli and me), accordingly with the forum profile layout seems to use xfce desktop. This might be another point...

Are there more xfce users with this problem?
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: Fatboy on 01. April 2016, 15:16:55
Yo @boletus. Good point!
I also have a Manjaro Deepin machine and there I use the exact same conky with the exact same issue (on top of other ones), so I don't know?
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: fredhoud on 01. April 2016, 16:50:13
I updated 5 computers with no problem. I went to work, this morning, and updated my work computer, which is exactly like my desktop profile, except the graphic card is NVIDIA GeForce GTX 645. The Grub won't load after I restarted the computer. I tried kernel 4.4, 4.2, as well as 4.1, but the grub won't load at all. It goes through a cycle. What can I do at this point?  :(
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: boletus on 01. April 2016, 16:52:37
Yo @boletus. Good point!
I also have a Manjaro Deepin machine and there I use the exact same conky with the exact same issue (on top of other ones), so I don't know?

So it has nothing to see with xfce... Ok
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: ninsa on 01. April 2016, 16:59:03
Another update, and again no issues. Perfect! Thanks a lot Manjaro team! :D
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: pawelx on 01. April 2016, 19:52:57
I'm not getting any notification and my update manager says the system is up to date.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: Fatboy on 01. April 2016, 22:34:07
@pawelx try "sudo pacman -Syy" before "sudo pacman -Syu"
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: jonathon on 01. April 2016, 23:48:11
I'm not getting any notification and my update manager says the system is up to date.

Adding to @Fatboy's suggestion, also check your mirror list is up-to-date: `sudo pacman-mirrors -g`
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: philm on 02. April 2016, 00:32:21
However, I did get this message in dmesg, after restarting the computer, after the kernel panic. This was the first time that this message has ever appeared:

Code: [Select]
[   12.052487] systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:00:14.1\x2data\x2d2.device: Dev dev-disk-by\x2dpath-pci\x2d0000:00:14.1\x2data\x2d2.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.1/ata2/host1/target1:0:0/1:0:0:0/block/sr0 and /sys/devices/pci0000:00/0000:00:14.1/ata2/host1/target1:0:1/1:0:1:0/block/sr1

Please check this:

http://ubuntuforums.org/showthread.php?t=2275068
https://bugs.freedesktop.org/show_bug.cgi?id=90386
https://bugzilla.redhat.com/show_bug.cgi?id=1245860
https://bbs.archlinux.org/viewtopic.php?id=196640

Can you boot your system still with this message?
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: wolfyrion on 02. April 2016, 06:57:29
my system monitoring issues not solved yet :(

I have submitted this bug to

https://bugs.kde.org/show_bug.cgi?id=360815

and it seems they cant reproduce the bug

So is either something with Manjaro/Systemd or something with my system

When the System Load Viewer Widget is Enabled the resources I monitor display 0 values or goes offline every 3 sec !?!?
http://i.imgur.com/Qk63U1t.png

And then it goes back to normal
http://i.imgur.com/LbRvcjW.png

so in short every 3 sec resources display 0 values ><

Can anyone else reproduce this bug? or is just me :o??
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: pawelx on 02. April 2016, 10:21:19
@pawelx try "sudo pacman -Syy" before "sudo pacman -Syu"

Thanks, this has helped. I wonder what blocked the automatic checking, it has always worked so far.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: BS86 on 02. April 2016, 13:02:56

Solution: remove or rename ~/.config/plasma-org.kde.plasma.desktop-appletsrc.*

thanks, that also solved my broken KDE desktop that was only showing the mouse pointer after an enormous time that it hang on the loadscreen

I have to take the "solution" back. I have to do that step everytime the machine reboots, always resulting in the desktop settings being wiped .... Any other hints on how to solve that?
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: nyanloutre on 02. April 2016, 13:06:31
Since this update I have a little bug with lvmcache
In fact, every times I reboot it seem to check the whole cache (in the lvs output Cpy%Sync and CacheDirtyBlocks are not at 0)
My cache is configured in writethrough, I use linux 4.4 and before this update I didn't have this issue
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: hakayova on 02. April 2016, 16:55:54
Since this update, Plasma does not remember my double display settings, which consist of two monitors, one in portrait one and the other in landscape orientation. The one that uses the portrait mode also uses a submaximal resolution. Plasma does not remember any of these settings when logged in and when I correct them by KDE system settings and/or nvidia settings (several combinations tried) the outcome is suboptimal, with some of the desktop wallpaper from one monitor extending to the other. Log out and log in again, everything changed is reset, you have to do all again. I am not even mentioning X-server crashing when the monitors were turned off. It is a known bug for monitors with display port that is yet to be addressed.

After years of KDE use, I am now forced to use XFCE :(.

I don't think this is necessarily a Manjaro update problem, my humble guess is it is related to qt5 and KDE-plasma.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: varikonniemi on 02. April 2016, 18:09:01
Yes, this was the version that was supposed to end multimonitor issues.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: akhilesh on 02. April 2016, 19:35:18
Solution: remove or rename ~/.config/plasma-org.kde.plasma.desktop-appletsrc.*

This actually fixed a lot for me. Thanks.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: fredhoud on 02. April 2016, 21:09:43
Sadly, this last update totally created a grub nightmare on my work desktop. The grub wouldn't load with any of the 4 installed kernels. I didn't hear any solution, so I ended up installing Netrunner 17 on a new hard drive, and kept the other hard drive with the corrupted grub, just in case someone comes up with a solution. I guess having a bleeding edge OS has its own nightmares, and I experienced enough.  :-\
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: hakayova on 02. April 2016, 22:06:09
I have to take the "solution" back. I have to do that step everytime the machine reboots, always resulting in the desktop settings being wiped .... Any other hints on how to solve that?
I am on the same boat. Renaming that file did not help solve the problem. I either don't have a KDE desktop (black screen with a mouse cursor) or, occasionally a KDE desktop which did not remember any settings from before. In addition, Doplhin doesn't launch and crashes consistently, as well as drkonqi crashing. It is a mess.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: philm on 03. April 2016, 00:40:05
@fredhoud: please post the pacman.log or pamac.log so we see which packages got exactly updated on your end. I don't see any grub updates (https://lists.manjaro.org/pipermail/manjaro-packages/Week-of-Mon-20160328/006561.html) in this update at all, except the breeze theme for it. If needed you can try the latest stable build of Manjaro KDE (https://sourceforge.net/projects/manjarolinux/files/release/16.06-pre2/kde/).
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: AJSlye on 03. April 2016, 01:56:01
Philip, almost all of the kernels had updates, would this not rebuild the  initramfs and trigger a grub update?
Installed grub, not the package.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: philm on 03. April 2016, 01:59:16
Yep, a kernel update triggers a grub-update call. However this shouldn't change anything. We already removed grub-customizer from our repos weeks ago to avoid unwanted issues.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: AJSlye on 03. April 2016, 02:20:44
Yep, a kernel update triggers a grub-update call. However this shouldn't change anything. We already removed grub-customizer from our repos weeks ago to avoid unwanted issues.

Yes, but all versions of Netrunner are required to ships grub-customizer and is included in all the netrunner repositories.

Fredhoud,
Did you use grub-customizer on your systems?
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: philm on 03. April 2016, 02:22:36
It is known that grub-customizer create issues. Therefore it shouldn't be used at all.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: AJSlye on 03. April 2016, 02:33:54
It is known that grub-customizer create issues. Therefore it shouldn't be used at all.

Again not my decision to make.
However, if a user has more than one distribution installed they are likely to have grub-customizer installed.
Not having this in the Manjaro repositories also doesn't stop someone from installing it and using it from the AUR.
The only issues I've seen with grub-customizer on arch based systems has to do with the way they load the intel ucode.
We don't ship the Intel ucode by default with Netrunner Rolling.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: philm on 03. April 2016, 03:03:59
Yep, most likely it is the odd ucode distribution for the Intel CPU.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: CyberWolf2k14 on 03. April 2016, 05:42:42
It is known that grub-customizer create issues. Therefore it shouldn't be used at all.
I use it to keep my grub menu organized, especially after the rare update causes like 2 or 3 copies of something. It is the only easy way to maintain it.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: DK3 on 03. April 2016, 08:36:23
Update on 12 Machines without Problems.

Thx


DK3
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: lallulli on 03. April 2016, 16:03:15
Is anybody experiencing performance issues with the Plasma Desktop? After updating to Plasma 5.6.1, my plasmashell process became extremely slow when user interacts with the desktop. Clicking on a desktop file/folder, or simply hovering a dekstop item, freezes the process for 1-2 seconds while consuming 100% CPU, before the item changes its visual status (e.g., the file looks selected).

Please notice that:

I noticed that the visual look of desktop items has improved. For example, text is shadowed. May it be an issue related to the GPU?

I also tried to rename the file plasma-org.kde.plasma.desktop-appletsrc with no success. At the end, I had to donwgrade the package plasma-desktop to version plasma-desktop-5.5.5-1.1-x86_64.

Best regards and, as always, thank you for your hard work!
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: Rebelyouth on 04. April 2016, 01:20:45
Hi all,

I updated and now yoaurt showing :

error: file owned by 'lsb-release' and 'manjaro-release': 'etc/lsb-release'

How i can fix it?
Other than that all ok.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: Ham Radio on 04. April 2016, 04:40:03
Is anybody experiencing performance issues with the Plasma Desktop? After updating to Plasma 5.6.1, my plasmashell process became extremely slow when user interacts with the desktop. Clicking on a desktop file/folder, or simply hovering a dekstop item, freezes the process for 1-2 seconds while consuming 100% CPU, before the item changes its visual status (e.g., the file looks selected).

Please notice that:
  • dolphin works correctly (quick interaction with files, without performance issues)
  • plasmashell works correctly for its other parts, e.g. the taskbar and the kicker menu are fast, provided that there is not some "pending" interaction with a desktop file

So far it's been really fast and stable for me. Have you tried deleting your config files?

I noticed that the visual look of desktop items has improved. For example, text is shadowed. May it be an issue related to the GPU?

I also tried to rename the file plasma-org.kde.plasma.desktop-appletsrc with no success. At the end, I had to donwgrade the package plasma-desktop to version plasma-desktop-5.5.5-1.1-x86_64.

Best regards and, as always, thank you for your hard work!
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: webstar on 04. April 2016, 11:31:28
Since this update, Plasma does not remember my double display settings, which consist of two monitors, one in portrait one and the other in landscape orientation. The one that uses the portrait mode also uses a submaximal resolution. Plasma does not remember any of these settings when logged in and when I correct them by KDE system settings and/or nvidia settings (several combinations tried) the outcome is suboptimal, with some of the desktop wallpaper from one monitor extending to the other. Log out and log in again, everything changed is reset, you have to do all again. I am not even mentioning X-server crashing when the monitors were turned off. It is a known bug for monitors with display port that is yet to be addressed.

After years of KDE use, I am now forced to use XFCE :(.

I don't think this is necessarily a Manjaro update problem, my humble guess is it is related to qt5 and KDE-plasma.

I found a workaround this fixes it. You have to disable kscreen service as well.
https://forums.opensuse.org/showthread.php/493985-SOLUTION-FOR-KSCREEN-NOT-SAVING-DUAL-MONITOR-CONFIGURATION-IN-OPENSUSE-13-1?s=988796fa1c4d61a3d61b15385ee72d51&p=2612606#post2612606

After the workaround I also had to fix the panel position in config/plasma-org.kde.plasma.desktop-appletsrc to fully get what I wanted.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: oberon on 04. April 2016, 11:48:29
error: file owned by 'lsb-release' and 'manjaro-release': 'etc/lsb-release'
@Rebelyouth, looks like your package lsb-release is maybe not originally a manjaro one... ??? Possible? Arch maybe? ;)

Try reinstalling:
Code: [Select]
sudo pacman -S lsb-release manjaro-release
You don't have any arch-repos active, do you? C:-)
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: viking60 on 04. April 2016, 13:52:54
After having had conflicting files - deleted them and then updated here (https://forum.manjaro.org/index.php?topic=32586.msg266275#msg266275); I noticed that Octopi needs the deleted file:

/usr/lib/libQt5Network.so.5 in qt5-base-dev-git. So Octopi does not work anymore.

Reinstalling Octopi does not fix it.
 
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: Kirek on 04. April 2016, 14:16:51
After having had conflicting files - deleted them and then updated here (https://forum.manjaro.org/index.php?topic=32586.msg266275#msg266275); I noticed that Octopi needs the deleted file:

/usr/lib/libQt5Network.so.5 in qt5-base-dev-git. So Octopi does not work anymore.

Reinstalling Octopi does not fix it.
 

The stable qt5 packages are 5.6, and you are using 5.5 dev versions of it...
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: viking60 on 04. April 2016, 14:30:18
Thanks!
You are right! I dunno how that came about (probably something I have fiddled around with) , but that was the reason. Removing the 5.5 git package and reinstalling Octopi worked just fine and pulled the right packages.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: danielson on 04. April 2016, 22:51:39
Can not update:

(354/354) checking keys in keyring                     [############################] 100%
downloading required keys...
error: key "8DB9F8C18DF53602" could not be looked up remotely
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: eugen-b on 04. April 2016, 23:02:59
It is a good idea to use the search function of the forum with the error message as search item. (Helps me usually more than asking a question...)
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: danielson on 05. April 2016, 01:38:58
@eugen-b

True! I did search now and came up with this suggestion:

sudo pacman -S archlinux-keyring manjaro-keyring
sudo pacman-key --populate archlinux manjaro
sudo pacman-key --refresh
sudo pacman -Syyu

Did have this error when doing sudo pacma-key --refresh:

sudo pacman-key --refresh
gpg: connecting dirmngr at '/root/.gnupg/S.dirmngr' failed: IPC connect call failed
gpg: keyserver refresh failed: No dirmngr
==> ERROR: A specified local key could not be updated from a keyserver.

At present time 352 of 352 have been downloaded/installed instead of initial 354/354
Hopefully reboot will be okay...


Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: tropper on 05. April 2016, 02:05:57
I had a problem with rendering fonts after upgrading font-config

see image
(https://lut.im/W5OSFS5IRm/xZW0v0zpbopor3Ck.png)
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: Rebelyouth on 05. April 2016, 02:52:49
@oberon thank you for your answer,

I have package from yaourt, but I don't have any arch repo, just the one from manjaro.

pacman -S lsb-release manjaro-release
warning: lsb-release-1.4-14 is up to date -- reinstalling
error: target not found: manjaro-release

and got again
error: file owned by 'lsb-release' and 'manjaro-release': 'etc/lsb-release'

Plus, I tried :

pacman -R lsb-release
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: manjaro-release: removing lsb-release breaks dependency 'lsb-release'
pacman -R manjaro-release:
error: target not found: manjaro-release:

So this is the issue? The system installed the new pacman-mirrorlist-20160404-1-any and I just de-comment earth as repo.
Everything working ok, just as manjaro user  ;) , want to know : why?

Thank you
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: scachemaille on 05. April 2016, 03:09:21
@oberon thank you for your answer,

I have package from yaourt, but I don't have any arch repo, just the one from manjaro.

pacman -S lsb-release manjaro-release
warning: lsb-release-1.4-14 is up to date -- reinstalling
error: target not found: manjaro-release

and got again
error: file owned by 'lsb-release' and 'manjaro-release': 'etc/lsb-release'

Plus, I tried :

pacman -R lsb-release
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: manjaro-release: removing lsb-release breaks dependency 'lsb-release'
pacman -R manjaro-release:
error: target not found: manjaro-release:

So this is the issue? The system installed the new pacman-mirrorlist-20160404-1-any and I just de-comment earth as repo.
Everything working ok, just as manjaro user  ;) , want to know : why?

Thank you
It's seems you're in unstable branch..  I don't know where pacman found lsb-release-1.4-14 as on repos it's the version 1.4-12. And normally this package don't own /etc/lsb-release.  Maybe a dev could find out why this.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: Rebelyouth on 05. April 2016, 03:25:56
I checked the system and look like reflector was installed in my system (I don't remember installing it).
I erased all the repo and install manually the Manjaro repo.

There are a lot of packages from Arch , so my solution are 1) live with it until new update 2) reinstall everything  3) use downgrade ...but look like it will chose arch repo. 4) or... any good suggestion.... ;)

Moral of this story is : don't install packages after 4 am  ;D

Thank you @oberon  and @scachemaille for the help.
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: hakayova on 05. April 2016, 04:06:05
I found a workaround this fixes it. You have to disable kscreen service as well.
https://forums.opensuse.org/showthread.php/493985-SOLUTION-FOR-KSCREEN-NOT-SAVING-DUAL-MONITOR-CONFIGURATION-IN-OPENSUSE-13-1?s=988796fa1c4d61a3d61b15385ee72d51&p=2612606#post2612606

After the workaround I also had to fix the panel position in config/plasma-org.kde.plasma.desktop-appletsrc to fully get what I wanted.

Thanks webstar. This is a good enough workaround until plasma pulls itself together, hopefully in the near future. This problem made me think that perhaps it was time to try DEs other than KDE, lol. Too much attachment to anything is risky  ;).
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: eugen-b on 05. April 2016, 09:25:22
Did have this error when doing sudo pacma-key --refresh:

sudo pacman-key --refresh
gpg: connecting dirmngr at '/root/.gnupg/S.dirmngr' failed: IPC connect call failed
gpg: keyserver refresh failed: No dirmngr
==> ERROR: A specified local key could not be updated from a keyserver.
You could guess my answer here, too. Search the error message. ;)
Title: Re: [Update] 2016-03-31 - Kernels, Plasma 5, Qt, Octopi, Calamares, Bluez, Budgie
Post by: lightbeam on 05. April 2016, 19:56:54
Please check this:

http://ubuntuforums.org/showthread.php?t=2275068
https://bugs.freedesktop.org/show_bug.cgi?id=90386
https://bugzilla.redhat.com/show_bug.cgi?id=1245860
https://bbs.archlinux.org/viewtopic.php?id=196640

Can you boot your system still with this message?

Yes, I'm able to booth the system despite the message.  Thanks for the leads.