[Stable Update] 2018-07-13 - Kernels, Firefox, Octopi, Adapta, Haskell, Python

update
stable

#1

Hi community,

Welcome to another stable update. So what do we have with this one?

  • latest kernels
  • Firefox updated in Standard and Development edition
  • Octopi got another revert in regard of the network check issue
  • Stefano managed to update our Adapta themes once more
  • python and haskell updates/rebuilds.

We hope with all these changes Manjaro to be more efficient for you all.


If you are curious about the latest state of development for the upcoming Manjaro-Illyria 18.0 release, you now have the opportunity to download a beta-build of Manjaro-Xfce 18.0 including the latest xfce-gtk3 packages aswell as our most recent styling efforts:

Our KDE fans may try our beta-build with the latest KDE v5.13 instead.


Latest information about the intel-cpu-bug risk and our efforts can be found here.


Current supported Kernels

  • linux316 3.16.57
  • linux318 3.18.114 [EOL]
  • linux41 4.1.52 [EOL]
  • linux44 4.4.139
  • linux49 4.9.111
  • linux414 4.14.54
  • linux415 4.15.18 [EOL]
  • linux416 4.16.18 [EOL]
  • linux417 4.17.5
  • linux418 4.18-rc3
  • linux414-rt 4.14.52_rt34
  • linux416-rt 4.16.18_rt9

Package Updates (Mon Jul 9 06:59:43 CEST 2018)

  • stable community x86_64: 576 new and 571 removed package(s)
  • stable core x86_64: 12 new and 12 removed package(s)
  • stable extra x86_64: 186 new and 283 removed package(s)
  • stable multilib x86_64: 2 new and 2 removed package(s)

A detailed list of all package changes may be reviewed here.

  • No issue, everything went smoothly
  • Yes there was an issue. I was able to resolve it myself.(Please post your solution)
  • Yes i am currently experiencing an issue due to the update. (Please post about it)

0 voters

Check if your mirror has already synced:


#2

Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Stable Updates Announcements RSS feed


Items from previous update sets

Issues with folder view widget in KDE v5.13

KDE introduced a new setting for icon sizes. Now you’re able to define also the size for your panel. If you have a high-DPI display, you may want to increase the value. This will fix the display issue with given widget.

icon-kde-513

Pulseaudio changes

With this update we have a /etc/pulse/default.pa.pacnew. It may be necessary to merge (some lines related to “GSettings” in /etc/pulse/default.pa ) if ‘default.pa’ has been customised.

File conflict engrampa.tap

thunar-archive-plugin: /usr/lib/xfce4/thunar-archive-plugin/engrampa.tap exists in filesystem (owned by engrampa-thunar-plugin)

thunar-archive-plugin has added native support for the Engrampa archive manager. engrampa-thunar-plugin is no longer needed. Remove engrampa-thunar-plugin to continue with the update.


Kernel 4.9 issues

Seems on rare conditions you may face a faulty boot with linux49. It results in messages similar like this: <module> likely not compiled with -mcmodel=kernel. Also you will land in the emergency console.

We recommend to install at least another kernel as backup. You may follow this post to recover. v4.9.107-2 is known to be working.


:: alpm-octopi-utils: installing “pacman” (5.1.0-2) breaks the dependency with «pacman <5.1»

Make sure your mirrors are up-to-date. All package management tools should be compatible with pacman 5.1


:: ffmpeg2.8: installing x265 (2.8-1) breaks dependency ‘libx265.so=151-64’

ffmpeg2.8 is no longer in the repos. Remove it, and if you need it, rebuild/reinstall it from the AUR.


gcc54 and gcc5 are in conflict

For those using CUDA, if this error comes up, run the update from terminal
sudo pacman -Syyu
and type YES to replace gcc5 with gcc54


Extension “Workspace to Dock” is bugged

Be careful like there is a bug if you use the Extension “Workspace to Dock”. You need to update/install this version in ~/.local/share/gnome-shell/extensions/ for not have desktop freeze after reboot : https://github.com/passingthru67/workspaces-to-dock/archive/master.zip

Thanks for nabd who have solved this issue : [Testing Update] 2018-05-11 - Kernels, GCC8, Gnome 3.28.2, Cinnamon, KDE Apps 18.04.1, LibreOffice


I see a lot of pacnew files

Well, there is no manual intervention needed for pacnew files coming from filesystem package. The best thing you can do is, do nothing.

Never, ever, ever, ever, ever merge the pacnew file for /etc/{passwd,shadow,gshadow,group}, unless you want to make the new comments match aesthetically with your in-use user accounts database. The only practical difference that merging can ever cause is to accidentally delete users or mangle the whole file’s syntax and render your computer maybe unbootable.

More advice in this regard you may find here.


Nvidia drivers and Fermi support

With the current Nvidia driver release v396.24, support for the old Fermi cards got dropped. Please switch either over to Nouveau driver or downgrade to v390xx driver series.

Bumblebee users follow:

sudo mhwd -r pci video-hybrid-intel-nvidia-bumblebee
sudo mhwd -i pci video-hybrid-intel-nvidia-390xx-bumblebee

Normal users follow:

sudo mhwd -r pci video-nvidia
sudo mhwd -i pci video-nvidia-390xx

To switch to opensource drivers do:

sudo mhwd -r pci video-nvidia
sudo mhwd -i pci video-linux


Changes made to Glibc

The new version of glibc removes support for NIS and NIS+. The default /etc/nsswitch.conf file provided by filesystem package already reflects this change. Please make sure to merge pacnew file if it exists prior to upgrade.

NIS functionality can still be enabled by installing libnss_nis package. There is no replacement for NIS+ in the official repositories.


Changes made to PAM

pam 1.3.0-2 no longer ships pam_unix2 module and pam_unix_*.so compatibility symlinks. Before upgrading, review PAM configuration files in the /etc/pam.d directory and replace removed modules with pam_unix.so. Users of pam_unix2 should also reset their passwords after such change. Defaults provided by pambase package do not need any modifications.

Check grep -rn 'pam_unix[2_]' /etc/pam.d, if no output, you need to do nothing.


Samba units renamed

Note: In samba 4.8.0-1, the units were renamed from smbd.service and nmbd.service to smb.service and nmb.service.

To provide basic file sharing through SMB start/enable smb.service and/or nmb.service services. See the smbd(8) and nmbd(8) man pages for details, as the nmb.service service may not always be required.


Directory permissions differ

Directory permissions differ on /var/lib/samba/private/
filesystem: 755 package: 700

sudo chmod 700 /var/lib/samba/private/


Samba - Error 255: net usershare add: cannot convert name “Everyone” to a SID.

Currently there seems to be an issue when using group = sambashare with Samba 4.8.1-1, which is used by default in thesmb.conf provided by Manjaro. Changing it to group = +sambashare or force group = +sambashare resolves this. However, we might fill out a bug report, to see why that is currently needed.

Commenting/removing group = sambashare is also a viable solution.


Long delay for starting Desktop Environment

There’s a bug which is exhausting the entropy pool. This is refilled over time through e.g. disk activity and mouse movement. You can increase the fill rate with a software solution:

sudo pacman -S haveged
sudo systemctl enable haveged
sudo systemctl start haveged

An alternative method if activating the haveged service is not something you want to do is to press the shift key 8-10 times in succession.


Failed to commit transaction: conflicting file
Known Issues from Stable Updates Announcements
#3

error - deepin
gone after a second reboot…
:+1::+1::+1:


#4

HTPC, OK
Workstation, OK
2x Notebook, OK
1 x Fujitsu Siemens miniTower, Revived :hugs:

Everything clean update without error. Many thanks to the Manjaro Team & Community


#5

Looks as if I got two orphans on KDE.

$ sudo pacman -Rs $(pacman -Qqdt)
[sudo] password for mparillo: 
checking dependencies...

Packages (2) pangox-compat-0.0.2+2+gedb9e09-2  gtkglext-1.2.0-11

#6

PC and laptop: Update OK. Manjaro Gnome

Thanks Manjaro Team!!!


#7

Updates were successful. Manjaro Gnome :slight_smile:


#8

Update for kernel 4.17 breaks boot sequence if plymouth is not installed. Since I don´t want plymouth I uninstalled it. Manjaro kernel builds with plymouth-encrypt. At boot it won´t find /dev/mapper/manjaro-root-encrypt because of plymouth hook. It should check for plymouth instead of blind building mkinit.


#9

no problems here :grinning:

regards
caho


#10

Is this a recommended command to run? For me it says:

Packages (4) boost-1.67.0-4 lash-0.6.0~rc2-14 maven-3.5.2-1 wxgtk2-3.0.4-1

Update went perfectly on KDE.


#11

i was about to make sure i have plymouth installed and noticed something odd:
i can find plymouth-themes, they have plymouth as a dep, but i can’t find plymouth itself?
Am i missing something??


#12

Uneventful smooth updates on Lappy KDE, Tower VMs [Cinnamon, KDE+Cinnamon, Xfce]. Tower’s real KDE also ok, albeit this msg appeared at the end:

directory permissions differ on /usr/Brother/inf/
filesystem: 775  package: 755

I’ve not yet bothered trying to use the MFC to see if anything’s now wrong with it.


#13

This was the only issue I had with the update. Everything else is neat. Thanks! (and also thanks to @bogdancovaciu that replied in another post to a user that missed this info)


#14

Plymouth was removed form the repository long ago. It is in the AUR, however do not install it. Unless you really want it and you can configure your system properly for the use of plymouth.

@mioc has either used an old iso or has a older system. Plymouth is not part of any recent Manjaro versions. Plymouth is not required for Kernel 4.17. However, if you installed a version with Plymouth and removed it, make sure you also update your /etc/mkinitcpio.conf .

See the Manajro wiki for a proper way to remove Plymouth
https://wiki.manjaro.org/index.php?title=Plymouth#Removal


#15

Thanks for the explanation - now that i read it i remember that it was removed…and i think i just wasn’t awake enough yet to simply check my hooks :smile:

But if plymouth was removed, the fact that the plymouth-themes are still in the repos is a bit odd, isn’t it?


#16

Yes it is a little bit odd. There was a discussion recently. Unfortunately no real solution was found.


#17

Thanks! Didn´t change mkinitcpio.conf :slight_smile:


#18

I have never had a problem running
$ sudo pacman -Rs $(pacman -Qqdt)
I assume if it were terribly dangerous, it would not be in the wiki, but I did see someone posted a warning against it once in these forums.

Of course, my important user data is backed up.


#19

For me it looks like this

ls -lar /opt/brother/Printers/mfc9332cdw/inf
insgesamt 32
-rwxr-xr-x 1 root root 1771  9. Mai 22:52 setupPrintcapij
-rw-r--r-- 1 root root  489  9. Mai 22:52 paperinfij2
drwxr-xr-x 2 root root 4096  9. Mai 22:52 lut
-rw-r--r-- 1 root root  642  9. Mai 22:52 ImagingArea
-rw-r--r-- 1 root root  337  9. Mai 22:52 brmfc9332cdwrc
-rw-r--r-- 1 root root 1187  9. Mai 22:52 brmfc9332cdwfunc
drwxr-xr-x 5 root root 4096  9. Mai 22:52 ..
drwxr-xr-x 3 root root 4096  9. Mai 22:52 .

#20

Thanks. For me, using the path of the error/warning message:

$ ls -lar /usr/Brother/inf
total 204
-rwxr-xr-x 1 root lp   1638 Sep 28  2012 setupPrintcap
-rw-r--r-- 1 root lp    215 Sep 28  2012 paperinf
-rwxr-xr-x 1 root lp    595 Sep 28  2012 brPrintList
-rw-r--r-- 1 root root  168 Jul 14 17:54 brMFC8870DWrc
-rw-r--r-- 1 root root  668 Jul 14 17:54 brMFC8870DWfunc
-rw-r--r-- 1 root root  168 Jul 14 17:54 brMFC8860DNrc
-rw-r--r-- 1 root root  668 Jul 14 17:54 brMFC8860DNfunc
-rw-r--r-- 1 root root  168 Jul 14 17:54 brMFC8660DNrc
-rw-r--r-- 1 root root  668 Jul 14 17:54 brMFC8660DNfunc
-rw-r--r-- 1 root root  167 Jul 14 17:54 brMFC8460Nrc
-rw-r--r-- 1 root root  667 Jul 14 17:54 brMFC8460Nfunc
-rw-r--r-- 1 root root  167 Jul 14 17:54 brMFC7820Nrc
-rw-r--r-- 1 root root  701 Jul 14 17:54 brMFC7820Nfunc
-rw-r--r-- 1 root root  166 Jul 14 17:54 brMFC7420rc
-rw-r--r-- 1 root root  652 Jul 14 17:54 brMFC7420func
-rw-r--r-- 1 root root  167 Jul 14 17:54 brMFC7225Nrc
-rw-r--r-- 1 root root  653 Jul 14 17:54 brMFC7225Nfunc
-rw-r--r-- 1 root root  166 Jul 14 17:54 brMFC7220rc
-rw-r--r-- 1 root root  652 Jul 14 17:54 brMFC7220func
-rw-r--r-- 1 root root  167 Jul 14 17:54 brHL5280DWrc
-rw-r--r-- 1 root root  667 Jul 14 17:54 brHL5280DWfunc
-rw-r--r-- 1 root root  167 Jul 14 17:54 brHL5270DNrc
-rw-r--r-- 1 root root  667 Jul 14 17:54 brHL5270DNfunc
-rw-r--r-- 1 root root  167 Jul 14 17:54 brHL5250DNrc
-rw-r--r-- 1 root root  667 Jul 14 17:54 brHL5250DNfunc
-rw-r--r-- 1 root root  165 Jul 14 17:54 brHL5240rc
-rw-r--r-- 1 root root  665 Jul 14 17:54 brHL5240func
-rw-r--r-- 1 root root  166 Jul 14 17:54 brHL2070Nrc
-rw-r--r-- 1 root root  652 Jul 14 17:54 brHL2070Nfunc
-rw-r--r-- 1 root root  165 Jul 14 17:54 brHL2040rc
-rw-r--r-- 1 root root  651 Jul 14 17:54 brHL2040func
-rw-r--r-- 1 root root  165 Jul 14 17:54 brHL2030rc
-rw-r--r-- 1 root root  651 Jul 14 17:54 brHL2030func
-rw-r--r-- 1 root root  166 Jul 14 17:54 brFAX2920rc
-rw-r--r-- 1 root root  652 Jul 14 17:54 brFAX2920func
-rw-r--r-- 1 root root  166 Jul 14 17:54 brFAX2820rc
-rw-r--r-- 1 root root  652 Jul 14 17:54 brFAX2820func
-rw-r--r-- 1 root root  168 Jul 14 17:54 brDCP8065DNrc
-rw-r--r-- 1 root root  668 Jul 14 17:54 brDCP8065DNfunc
-rw-r--r-- 1 root root  166 Jul 14 17:54 brDCP8060rc
-rw-r--r-- 1 root root  666 Jul 14 17:54 brDCP8060func
-rw-r--r-- 1 root root  166 Jul 14 17:54 brDCP7025rc
-rw-r--r-- 1 root root  652 Jul 14 17:54 brDCP7025func
-rw-r--r-- 1 root root  166 Jul 14 17:54 brDCP7020rc
-rw-r--r-- 1 root root  652 Jul 14 17:54 brDCP7020func
-rw-r--r-- 1 root root  166 Jul 14 17:54 brDCP7010rc
-rw-r--r-- 1 root root  652 Jul 14 17:54 brDCP7010func
-rwxr-xr-x 1 root root 5600 Jul 14 17:54 braddprinter
drwxr-xr-x 6 root lp   4096 Dec 17  2017 ..
drwxrwxr-x 2 root lp   4096 Jul 14 17:54 .