[Testing Update] 2018-07-09 - Kernels, Firefox, Octopi, Adapta, Haskell, Python

update
testing

#1

Hi community,

Welcome to another testing 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)

Overlay Packages

  • testing core x86_64: 6 new and 6 removed package(s)
  • testing extra x86_64: 38 new and 134 removed package(s)
  • testing community x86_64: 33 new and 33 removed package(s)

Sync Packages

  • testing core x86_64: 7 new and 6 removed package(s)
  • testing multilib x86_64: 2 new and 2 removed package(s)
  • testing extra x86_64: 144 new and 145 removed package(s)
  • testing community x86_64: 539 new and 534 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:


Ready for Stable ?!?

  • We are ready to move this to our stable branch
  • I still see some issues (post about them)

0 voters


#2

Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Testing 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.


#3

@oberon, @Ste74, @jonathon: since I’ll be in Rumania this week, I won’t add additional packages to our repos the coming days. My current clean-script can be found here. Simply sync as needed in testing and then copy the overlay packages locally to testing. Run the cleanup and push it with a second step. That is why we currently have the testing updates with commits, rather then snaps. stable however should be snapped as always :wink:

Based on my internal testing, this update may go as is to stable soon.


#4
Maybe of topic

Firefox (61.0.1) dos not remember last session, Deepin.
In testing Xfce Firefox (61.0.1) work nomal.


#5

downgrade boinc

new boinc isn’t connecting in my case.
Thus I switched from 7.10.3 to 7.8.6 back.


#6

Not sure if this update was responsible - can’t see any package that seems relevant - but today my customised dns resolution stopped being honoured. Removing systemd-resolvconf and reverting to openresolv fixed the problem.

(Only other thing that might have caused the issue was switching kernels for a quick test and then back again, but I don’t understand how that would do it either.)

:ear:


#7

systemd custom DNS still works here. Maybe the DNS went down.

Since you mentioned a reboot. Is systemd-resolved.service enabled? Maybe you only started it and forgot to enable it on reboot.


#8

boinc does not work, whether new or earlier version.


#9

Pretty sure that the DNS did not go down. Systemd-resolved.service was enabled and had persisted through several boots since the change. When switching back the change was instantaneous, no login/reboot needed, and the existing (correct) resolv.conf did not need changing. IF this was the problem I suspect the resolvconf binary, which I could not inspect.

Since others aren’t experiencing it must be something (else?) on my end. :woman_shrugging:


#10

Have you tried setting up systemd-resolved the recommended way and not using /etc/resolv.conf?


#11

Yep, and couldn’t get it to work with custom DNS. My failing. :smile:

But that is not the point here; systemd-resolvconf using resolv.conf was working for several days (and should still?) but it ceased to for some reason. I thought maybe(/probably) this update was involved.

(I am happy using openresolv - well, while it works for me. :wink: Just don’t mind trying new things and reporting problems that occur.)


#12

I am curious to see if I can recreate the problem going the other way. I will report back in a few hours (in the middle of something I should not be on the forum right now :sweat_smile:).

If you want to set up systemd-resolvconf again without resolv.conf, here’s how I did it.


#13

@grinner I created a new /etc/resolv.conf and tried a few different nameservers confirming with both resolvectl status and www.dnsleaktest.com , and everything seems to be working fine.

using linux 4.17.5-1 and systemd-resolvconf 239.0-2

I wonder what could be wrong.


#14

update, I have returned from work fired up boinc and it works. Seems that this update just coincided with their servers temporarily not working…


#15
Packages (23) avahi-0.7+16+g1cc2b8e-1  brotli-1.0.5-1  dialog-1:1.3_20180621-1  gdbm-1.16-1  imagemagick-7.0.8.5-1  libinput-1.11.2-1  libmagick-7.0.8.5-1
              libsasl-2.1.26-13  linux-ck-silvermont-4.17.5-1  linux-ck-silvermont-headers-4.17.5-1  linux417-4.17.5-1  man-db-2.8.3-2
              manjaro-browser-settings-20180707-1  manjaro-openbox-basic-config-1.18.10-1  nodejs-10.6.0-1  perl-5.26.2-2  python-3.6.6-1  python2-2.7.15-2  ruby-2.5.1-2
              youtube-dl-2018.07.04-1  zeromq-4.2.3-1  zsh-5.5.1-2  zstd-1.3.5-1

Total Installed Size:  614.36 MiB
Net Upgrade Size:       -0.27 MiB

:: Proceed with installation? [Y/n]
(23/23) checking keys in keyring                                                                       [############################################################] 100%
(23/23) checking package integrity                                                                     [############################################################] 100%
(23/23) loading package files                                                                          [############################################################] 100%
(23/23) checking for file conflicts                                                                    [############################################################] 100%
error: failed to commit transaction (conflicting files)
manjaro-openbox-basic-config: /etc/default/useradd exists in filesystem (owned by shadow)
Errors occurred, no packages were upgraded.
  Updates from system repositories have failed probably because of file conflicts.
  Do you want to forcefully overwrite all conflicting files? [y|N]

@fhdk, FYI.

Tried to remove:

4

checking dependencies...

Packages (1) manjaro-openbox-basic-config-1.18.9-1

Total Removed Size:  0.46 MiB

:: Do you want to remove these packages? [Y/n]
:: Processing package changes...
(1/1) removing manjaro-openbox-basic-config                                                            [############################################################] 100%
sed: can't read /etc/lightdm/slick-greeter.conf: No such file or directory
error: command failed to execute correctly

  Package(s) including all unneeded dependencies removed. To return to PacUI press ENTER

But it is removed now.


#16

I was aware of the conflict.

Thank you for reminding me.


#18

I was trying to move as much customization as possible to the config package.

I then discovered when building the iso that the useradd file was indeed present in the root file system - owned by shadow.

So that specific file needs to in the desktop-overlay - which I totally forgot until you reminded me.

I have just pushed 1.18.11 to unstable and testing. Some mirrors catch up very quickly.


#19

Thanks for trying. The strange thing (for me) is that it worked for some time then stopped. A bit busy at the moment but when I find some time I’ll switch back and see if it reappears. Looking back at the updates it seems avahi updated (along with gdbm), could of that triggered it? I’ll make a test if you don’t get there first. :grin:


#20

can team manjaro check this point ?
https://www.phoronix.com/scan.php?page=news_item&px=GCC-8-march-native-Skylake


#21

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.