[Stable Update] 2016-12-07 - Systemd, Kernels, Firefox, Thunderbird, Mesa, Python

codelite stopped working with the kernel 4.4.30-1 update.

Was working with kernel 4.4.27-1.

Tried restricting updates to codelite in pacman.conf. But has no effect. The problem has to do with the update to clang.

Now get the folowing message when try to load codelite:

codelite: error while loading shared libraries: libclang.so.3.8: cannot open shared object file: no such file or directory

If try to restrict update to clang in pacman.conf, then get the following error when try > pacman -Syu:

:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
warning: clang: ignoring package upgrade (3.8.1-1 => 3.9.0-3)
warning: menulibre: local (1:2.1.0-1) is newer than community (2.1.3-1)
warning: minitube: ignoring package upgrade (2.4-2 => 2.5.2-2)
warning: palemoon-bin: ignoring package upgrade (25.8.1-2 => 27.0.2-1)
:: Replace prebootloader with extra/efitools? [Y/n] n
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: clang: installing llvm-libs (3.9.0-3) breaks dependency 'llvm-libs=3.8.1-1'

Nice that waterfox-bin now displays in aur.

Codelite is an AUR package, and is therefore not supported by Manjaro directly.
According to the AUR page it has not been updated since August, so Codelite needs an update, to get it to work with the new clang.

1 Like

Worked fine on my KDE system using: yaourt -Syua
Had an issue with the session during update, but it was easily resolved with loginctl unlock-sessions.

Updated with Octopi without a problem, even though my router dropped the internet mid-update o.o . Some info:

Software:

KDE Plasma Version: 5.8.4
KDE Frameworks Version: 5.28.0
QT Version: 5.7.0
Kernel Version: 4.8.12-1-MANJARO
Release: 16.10.2
OS Type: 64-bit

Hardware:

CPU: 4 x Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz
GPU: Intel 3rd Gen Core processor Graphics Controller
RAM: 4GiB
Network: wlp2s0    Broadcom BCM4313 802.11bgn Wireless Network Adapter

Work fine on my laptop kernel 4.4 (GNOME system).

Thanks!

Yeah, I remember that bug. Unfortunately gtk3-theming means literally thousands of lines of code and it seems a bit hopeless to solve this. At some point in the conversion vertex to vertex-maia one of the color replacements must be not ideal. I seem to remember that a while ago I simply decided that the issue is maybe not serious enough to spend hours on trying to fix it :wink: So I thought we can maybe just live with bold file names for renaming in Cinnamon :laughing: Sorry for that... :expressionless:

1 Like

Haha that's okay. As a non technical person I'm really in awe of people like you and countless others who spend hours and days to make something this great of a distro. This bug is something that I find annoying but also I understand that priorities matter. Since I know now that it has got your attention, I'll rest assured that you'll think of it at your convenience.

Thank you for such an amazing work on Manjaro Cinnamon.:slightly_smiling_face:

4 Likes

I thought I am the master by now...

I followed the usual procedure as suggested - ranked mirrors etc ran the commands as pinpointed in the manual above.

Now I can see a screen in black.

I am not screaming nor panicking - what now?

I hard rebooted and can enter GNU GRUB.

I am on KDE.

what is this for a theme?

the update went smoothly, but whenever i open up the terminal now, it states:

cat: /sys/class/hwmon/hwmon0/temp1_input: invalid argument
(standard_in) 1: syntax error

as a sidenote: as of kernel 4.8.9, the notebooks cpu fan starts to kick in quite aggressively even on usual tasks like watching youtube videos (never did before). but when i checked sensors in the terminal, the temp was not that immense high at all for both cores (37-39 running idle).

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +48.0°C (high = +87.0°C, crit = +105.0°C)
Core 0: +48.0°C (high = +87.0°C, crit = +105.0°C)
Core 1: +49.0°C (high = +87.0°C, crit = +105.0°C)

need to find out if 4.8.12-1 makes a difference in this matter.

Get out of you ass and open a terminal to run #pacman -S archlinux-keyring
then #pacman -Sy and finally # pacman -Su to run the friggin' update...

1 Like

@Zehph: please stay polite.

2 Likes

Another great update - thanks to Phil, core team & everyone else who contributed upstream to this.

More power to you all.

Ruziel :slight_smile:

Smooth update, thank you all! :slight_smile:

P.S. : palemoon-bin 27.0.2-1 will not work with the version 26.4-1 of the language packs.

I suggest to update on our repos some of the beta versions of the languages packs, that you can find here:

Dear All,

I would like to ask for help with a problem that I am having with this update.

I couldn't update the system because a conflict related to Eclipse IDE (eclipse-java). After removing it I could proceed with the update, however when I tried to install Eclipse again, I received the following messages:

error: failed to commit transaction (conflicting files)
eclipse-common: /usr/lib/eclipse/features/org.eclipse.epp.mpc_1.5.2.v20161005-1414/META-INF/ECLIPSE_.RSA exists in filesystem
eclipse-common: /usr/lib/eclipse/features/org.eclipse.epp.mpc_1.5.2.v20161005-1414/META-INF/ECLIPSE_.SF exists in filesystem
eclipse-common: /usr/lib/eclipse/features/org.eclipse.epp.mpc_1.5.2.v20161005-1414/META-INF/MANIFEST.MF exists in filesystem
eclipse-common: /usr/lib/eclipse/features/org.eclipse.epp.mpc_1.5.2.v20161005-1414/about.html exists in filesystem
eclipse-common: /usr/lib/eclipse/features/org.eclipse.epp.mpc_1.5.2.v20161005-1414/epl-v10.html exists in filesystem
eclipse-common: /usr/lib/eclipse/features/org.eclipse.epp.mpc_1.5.2.v20161005-1414/feature.properties exists in filesystem
eclipse-common: /usr/lib/eclipse/features/org.eclipse.epp.mpc_1.5.2.v20161005-1414/feature.xml exists in filesystem
eclipse-common: /usr/lib/eclipse/features/org.eclipse.epp.mpc_1.5.2.v20161005-1414/license.html exists in filesystem
eclipse-common: /usr/lib/eclipse/features/org.eclipse.epp.package.common.feature_4.6.1.20161007-1200/META-INF/ECLIPSE_.RSA exists in filesystem
eclipse-common: /usr/lib/eclipse/features/org.eclipse.epp.package.common.feature_4.6.1.20161007-1200/META-INF/ECLIPSE_.SF exists in filesystem
eclipse-common: /usr/lib/eclipse/features/org.eclipse.epp.package.common.feature_4.6.1.20161007-1200/META-INF/MANIFEST.MF exists in filesystem
eclipse-common: /usr/lib/eclipse/features/org.eclipse.epp.package.common.feature_4.6.1.20161007-1200/epl-v10.html exists in filesystem
eclipse-common: /usr/lib/eclipse/features/org.eclipse.epp.package.common.feature_4.6.1.20161007-1200/feature.properties exists in filesystem
eclipse-common: /usr/lib/eclipse/features/org.eclipse.epp.package.common.feature_4.6.1.20161007-1200/feature.xml exists in filesystem
eclipse-common: /usr/lib/eclipse/features/org.eclipse.epp.package.common.feature_4.6.1.20161007-1200/license.html exists in filesystem
eclipse-common: /usr/lib/eclipse/features/org.eclipse.epp.package.common.feature_4.6.1.20161007-1200/p2.inf exists in filesystem
eclipse-common: /usr/lib/eclipse/plugins/org.eclipse.epp.mpc.core_1.5.2.v20161004-1655.jar exists in filesystem
eclipse-common: /usr/lib/eclipse/plugins/org.eclipse.epp.mpc.help.ui_1.5.2.v20161004-1655.jar exists in filesystem
eclipse-common: /usr/lib/eclipse/plugins/org.eclipse.epp.mpc.ui_1.5.2.v20161005-1414.jar exists in filesystem
eclipse-java: /usr/lib/eclipse/features/org.eclipse.epp.package.java.feature_4.6.1.20161007-1200/META-INF/ECLIPSE_.RSA exists in filesystem
eclipse-java: /usr/lib/eclipse/features/org.eclipse.epp.package.java.feature_4.6.1.20161007-1200/META-INF/ECLIPSE_.SF exists in filesystem
eclipse-java: /usr/lib/eclipse/features/org.eclipse.epp.package.java.feature_4.6.1.20161007-1200/META-INF/MANIFEST.MF exists in filesystem
eclipse-java: /usr/lib/eclipse/features/org.eclipse.epp.package.java.feature_4.6.1.20161007-1200/epl-v10.html exists in filesystem
eclipse-java: /usr/lib/eclipse/features/org.eclipse.epp.package.java.feature_4.6.1.20161007-1200/feature.properties exists in filesystem
eclipse-java: /usr/lib/eclipse/features/org.eclipse.epp.package.java.feature_4.6.1.20161007-1200/feature.xml exists in filesystem
eclipse-java: /usr/lib/eclipse/features/org.eclipse.epp.package.java.feature_4.6.1.20161007-1200/license.html exists in filesystem
eclipse-java: /usr/lib/eclipse/features/org.eclipse.epp.package.java.feature_4.6.1.20161007-1200/p2.inf exists in filesystem
eclipse-java: /usr/lib/eclipse/p2/org.eclipse.equinox.p2.core/cache/binary/epp.package.java.executable.gtk.linux.x86_64_4.6.1.20161007-1200 exists in filesystem
eclipse-java: /usr/lib/eclipse/plugins/org.eclipse.epp.package.java_4.6.1.20161007-1200/META-INF/ECLIPSE_.RSA exists in filesystem
eclipse-java: /usr/lib/eclipse/plugins/org.eclipse.epp.package.java_4.6.1.20161007-1200/META-INF/ECLIPSE_.SF exists in filesystem
eclipse-java: /usr/lib/eclipse/plugins/org.eclipse.epp.package.java_4.6.1.20161007-1200/META-INF/MANIFEST.MF exists in filesystem
eclipse-java: /usr/lib/eclipse/plugins/org.eclipse.epp.package.java_4.6.1.20161007-1200/META-INF/maven/org.eclipse.epp/org.eclipse.epp.package.java/pom.properties exists in filesystem
eclipse-java: /usr/lib/eclipse/plugins/org.eclipse.epp.package.java_4.6.1.20161007-1200/META-INF/maven/org.eclipse.epp/org.eclipse.epp.package.java/pom.xml exists in filesystem
eclipse-java: /usr/lib/eclipse/plugins/org.eclipse.epp.package.java_4.6.1.20161007-1200/about.html exists in filesystem
eclipse-java: /usr/lib/eclipse/plugins/org.eclipse.epp.package.java_4.6.1.20161007-1200/about.ini exists in filesystem
eclipse-java: /usr/lib/eclipse/plugins/org.eclipse.epp.package.java_4.6.1.20161007-1200/about.mappings exists in filesystem
eclipse-java: /usr/lib/eclipse/plugins/org.eclipse.epp.package.java_4.6.1.20161007-1200/about.properties exists in filesystem
eclipse-java: /usr/lib/eclipse/plugins/org.eclipse.epp.package.java_4.6.1.20161007-1200/eclipse16.png exists in filesystem
eclipse-java: /usr/lib/eclipse/plugins/org.eclipse.epp.package.java_4.6.1.20161007-1200/eclipse256.png exists in filesystem
eclipse-java: /usr/lib/eclipse/plugins/org.eclipse.epp.package.java_4.6.1.20161007-1200/eclipse32.png exists in filesystem
eclipse-java: /usr/lib/eclipse/plugins/org.eclipse.epp.package.java_4.6.1.20161007-1200/eclipse48.png exists in filesystem
eclipse-java: /usr/lib/eclipse/plugins/org.eclipse.epp.package.java_4.6.1.20161007-1200/epp-java-about.png exists in filesystem
eclipse-java: /usr/lib/eclipse/plugins/org.eclipse.epp.package.java_4.6.1.20161007-1200/intro-eclipse.png exists in filesystem
eclipse-java: /usr/lib/eclipse/plugins/org.eclipse.epp.package.java_4.6.1.20161007-1200/org.eclipse.ui.intro.universal.solstice/intro-eclipse.png exists in filesystem
eclipse-java: /usr/lib/eclipse/plugins/org.eclipse.epp.package.java_4.6.1.20161007-1200/plugin.properties exists in filesystem
eclipse-java: /usr/lib/eclipse/plugins/org.eclipse.epp.package.java_4.6.1.20161007-1200/plugin.xml exists in filesystem
eclipse-java: /usr/lib/eclipse/plugins/org.eclipse.epp.package.java_4.6.1.20161007-1200/plugin_customization.ini exists in filesystem
Errors occurred, no packages were upgraded.

When I tried to discover who owns the files with pacman -Qo /path/to/file I always received the same output for each one of them: error: No package owns /path/to/file

So I decided to force (pacman --force) the installation of Eclipse. Now when I try to run it, all steps before the initialization of the GUI are executed (it is informed by the splash screen) but nothing happen and it stops.

My system:

* Hardware:
System:    Host: orion-manjaro Kernel: 4.8.12-1-MANJARO x86_64 (64 bit gcc: 6.2.1)
           Desktop: Xfce 4.12.3 (Gtk 2.24.31) Distro: Manjaro Linux
Machine:   Device: laptop System: Dell product: Inspiron 7348 v: A09
           Mobo: Dell model: 0RTGX8 v: A00 UEFI: Dell v: A09 date: 05/13/2016
Battery    BAT0: charge: 36.3 Wh 100.0% condition: 36.3/37.6 Wh (97%)
           model: SANYO DELL 4K8YH55P status: Full
CPU:       Dual core Intel Core i7-5500U (-HT-MCP-) cache: 4096 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9580
           clock speeds: max: 3000 MHz 1: 499 MHz 2: 499 MHz 3: 499 MHz 4: 499 MHz
Graphics:  Card: Intel HD Graphics 5500 bus-ID: 00:02.0
           Display Server: X.Org 1.18.4 driver: intel Resolution: 1920x1080@60.00hz
           GLX Renderer: Mesa DRI Intel HD Graphics 5500 (Broadwell GT2)
           GLX Version: 3.0 Mesa 13.0.2 Direct Rendering: Yes
Audio:     Card-1 Intel Wildcat Point-LP High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 Intel Broadwell-U Audio Controller driver: snd_hda_intel bus-ID: 00:03.0
           Sound: Advanced Linux Sound Architecture v: k4.8.12-1-MANJARO
Network:   Card: Intel Wireless 7265 driver: iwlwifi bus-ID: 01:00.0
           IF: wlp1s0 state: up mac: <filter>
Drives:    HDD Total Size: 500.1GB (75.4% used)
           ID-1: /dev/sda model: ST500LM000 size: 500.1GB
Partition: ID-1: / size: 228G used: 120G (56%) fs: ext4 dev: /dev/sda5
Sensors:   System Temperatures: cpu: 46.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 242 Uptime: 1:11 Memory: 2852.9/7903.3MB Init: systemd Gcc sys: 6.2.1
           Client: Shell (bash 4.4.51) inxi: 2.3.4
  • Software:
    Linux orion-manjaro 4.8.12-1-MANJARO #1 SMP PREEMPT Fri Dec 2 20:03:35 UTC 2016 x86_64 GNU/Linux

    DISTRIB_ID=ManjaroLinux
    DISTRIB_RELEASE=16.10
    DISTRIB_CODENAME=Fringilla
    DISTRIB_DESCRIPTION="Manjaro Linux"

Thank you in advance.
Rick

Did you backup your system before applying this update? Hopefully you did, worst case you can restorre.

Have you tried other kernels?

How far through the boot process does it get? Does it die before the SDDM login screen? Are there any error messages?

Does it boot far enough to enable tty2 access (ie CTRL + ALT F2)? If so check the kernel logs using dmesg.

Can you boot into a live USB environment and manjaro-chroot into your system?

Once you have a CLI...

What graphics driver are you using? mhwd -li

Check for errors in the journal logs using journalctl -xn

Check for xorg errors in /var/log/xorg.*.log

1 Like

Update ran smoothly and flawless as ever. Always a pleasure to enjoy this distribution.

Keep on rocking and rolling!!!

Manjaro KDE linux 4.8.12 AMD non-free driver.

Hello

on my eepc 1201n laptop the update is installed all went fine.
on my desktop machine update is installed and all went fine too.
on my packard bell lm 98 laptop the update is installed and all went fine here too.

wow...nice work to all from the team. special thanks to philip.

1 Like

No problems on Plasma. All good.
Thank to the Team!

Quad core Intel Core i5-4570
Kernel: 4.8.12-1-MANJARO x86_64
Cedar [Radeon HD 7350/8350 / R5 220]
Display Server: X.Org 1.18.4 driver: radeon
Desktop: KDE Plasma 5.8.4 (Qt 5.7.0)

Just one issue that's currently ongoing. Minor and cosmetic, but primarily affects those with disabilities / visual impairment. I've posted my findings here

Forum kindly sponsored by