[Stable Update] 2017-12-31 - Kernels, Xorg-Server, Mesa, Compiz, Wine, Firefox

update
stable

#69

Hello philm

Updates went through smooth. No issues. Happy New year to you also. I have one request, Is it possible to setup one Manjaro Mirror in India, so that people in India can have faster updates? Keep up the good work!

Thanks
Harman


#70

hello

i have this error


#71

conan isn’t in the repos, so it’s probably an AUR package. Read its package page for more information: https://aur.archlinux.org/packages/conan


#72

i found this in the page of AUR but not in the update


#73

You need to update pacman and aur cache, $ yaourt -Syy
or maybe your mirror is out of date.

From the GUI, there is a switch to turn on AUR in preferences of pamac or Octopi.


#74

I would agree with what @anika200 has wrote. Seems your mirror is not up to date. Current version of conan is 0.30.3 on AUR, yours show 0.27. Also pkgbuild shows correct dependencies which should work with the version installed of python-distro and python-pylint.


#75

Smooth update on two XFCE installations(one on HDD partition and one on VirtualBox).

Thanks Manjaro Team! Happy New Year and all the best for all great things you do for Manjaro.:confetti_ball:


#77

First of all, thanks for great work MT and Happy New Year for all!

Notebook Lenovo ThinkPad E120, fresh installation of Manjaro-Gnome x86_84. Cheese starting, but not working. There is log output:

cheese-WARNING **: Device ‘/dev/video0’ cannot capture in the specified format: gstv4l2object.c(3640): gst_v4l2_object_set_format_full (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin1/GstV4l2Src:v4l2src1:
Tried to capture in BGR3, but device returned format YUYV

It seems to be the same bug as:
https://bugzilla.redhat.com/show_bug.cgi?id=1508706

Any ideas, how to fix it? V4L2 test utility works fine.


#78

I assume you try to do here some dkms build. For Manjaro we use our own extra modules. Simply install linux414-nvidia for the latest nvidia module. See also here.


split this topic #79

A post was merged into an existing topic: My best wishes for all. Happy New Year Manjarians


#80

Hi!

Update went good so far but now i have a issue with Bluetooth/bluez 5.48-1 after resume from sleep.

Power on:

● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor pr
   Active: active (running) since Thu 2018-01-04 14:08:17 CET; 5min ago

Jan 04 14:08:17 laptop bluetoothd[638]: Bluetooth daemon 5.48
Jan 04 14:08:17 laptop bluetoothd[638]: Starting SDP server
Jan 04 14:08:17 laptop bluetoothd[638]: Bluetooth management interface 1.14 ini
Jan 04 14:08:17 laptop systemd[1]: Starting Bluetooth service...
Jan 04 14:08:17 laptop systemd[1]: Started Bluetooth service.
Jan 04 14:09:13 laptop bluetoothd[638]: Endpoint registered: sender=:1.66 path=
Jan 04 14:09:13 laptop bluetoothd[638]: Endpoint registered: sender=:1.66 path=
Jan 04 14:09:15 laptop bluetoothd[638]: /org/bluez/hci0/dev_00_0D_44_E3_74_E4/fd0: fd(23) ready

Sleep…

After wakeup, the Bluetooth Service tries to reconnect to the Bluetooth Speaker but it fails with every try:

…Resume:

Jan 04 14:14:46 laptop bluetoothd[638]: Endpoint unregistered: sender=:1.66 path=/MediaEndpoint/A2DPSource
Jan 04 14:14:46 laptop bluetoothd[638]: Endpoint unregistered: sender=:1.66 path=/MediaEndpoint/A2DPSink
Jan 04 14:14:46 laptop bluetoothd[638]: Endpoint registered: sender=:1.66 path=/MediaEndpoint/A2DPSource
Jan 04 14:14:46 laptop bluetoothd[638]: Endpoint registered: sender=:1.66 path=/MediaEndpoint/A2DPSink
Jan 04 14:15:04 laptop bluetoothd[638]: Endpoint replied with an error: org.bluez.Error.InvalidArguments
Jan 04 14:15:21 laptop bluetoothd[638]: Endpoint replied with an error: org.bluez.Error.InvalidArguments
Jan 04 14:15:38 laptop bluetoothd[638]: Endpoint replied with an error: org.bluez.Error.InvalidArguments

in the journal appears:

Jan 04 14:15:38 laptop pulseaudio[1416]: E: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_0D_44_E3_74_E4 is invalid
Jan 04 14:15:22 laptop dbus-daemon[639]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.66" (uid=1000 pid=1416 comm="/usr/bin/pulseaudio --daemonize=no ") interface="(unset)" me
Jan 04 14:15:21 laptop bluetoothd[638]: Endpoint replied with an error: org.bluez.Error.InvalidArguments
Jan 04 14:15:21 laptop pulseaudio[1416]: E: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_0D_44_E3_74_E4 is invalid

Okay, now i have 2 Options…

After resume: Restart the Bluetooth Service (or reboot) and Bluetooth is working again

systemctl restart bluetooth

Thats not so nice…

my second try - downgrade bluez from 5.48-1 to 5.47-3 and everything works as usual. I have choose this.

any hints for a better solution?

thank you all

update:

a test with manjaro-gnome-17.1.0-stable-x86_64 iso live brings the same behavior

System Information
System:    Host: laptop Kernel: 4.14.10-2-MANJARO x86_64 bits: 64 gcc: 7.2.1
           Desktop: Gnome 3.26.2 (Gtk 3.22.26) Distro: Manjaro Linux
Machine:   Device: laptop System: TOSHIBA product: SATELLITE Z930 v: PT23LE-01400MS4 serial: N/A
           Mobo: TOSHIBA model: SATELLITE Z930 v: Version A0 serial: N/A
           UEFI: TOSHIBA v: Version 6.80 date: 06/25/2013
CPU:       Dual core Intel Core i5-3337U (-MT-MCP-) arch: Ivy Bridge rev.9 cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 7186
           clock speeds: max: 2700 MHz 1: 1795 MHz 2: 1795 MHz 3: 1795 MHz 4: 1795 MHz
Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller bus-ID: 00:02.0
           Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 1366x768@60.20hz, 1920x1080@60.00hz
           OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile version: 4.2 Mesa 17.3.1 Direct Render: Yes
Audio:     Card-1 Intel 7 Series/C216 Family High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 Texas Instruments PCM2902 Audio Codec driver: USB Audio usb-ID: 003-004
           Sound: Advanced Linux Sound Architecture v: k4.14.10-2-MANJARO
Network:   Card-1: Intel 82579V Gigabit Network Connection driver: e1000e v: 3.2.6-k port: 2080 bus-ID: 00:19.0
           IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: <filter>
           Card-2: Intel Centrino Advanced-N 6235 driver: iwlwifi bus-ID: 02:00.0
           IF: wlp2s0 state: down mac: <filter>

[Stable Update] 2018-01-07 - Browsers, Nvidia, PHP, Compiz, Adapta
#81

Hi, many thanks community! Everything went fine. Manjaro KDE on an Asus N54V series.


#82

Everything OK, two laptops
By the way: https://imgur.com/a/VW2OF <— Manjaro rank #2 in Distrowatch


#83

Hey, any chance the mesa update is the cause of this error?

$ glxinfo
name of display: :0
libGL error: unable to load driver: radeonsi_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: radeonsi
libGL error: unable to load driver: radeonsi_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: radeonsi
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request: GLXBadContext
Major opcode of failed request: 156 (GLX)
Minor opcode of failed request: 6 (X_GLXIsDirect)
Serial number of failed request: 58
Current serial number in output stream: 57

Which is weird, because radeon_dri.so is there but is not requested by libGL:

$ ldd /usr/lib/libGL.so.1
linux-vdso.so.1 (0x00007fffc7bb9000)
libGLX.so.0 => /usr/lib/libGLX.so.0 (0x00007f41c019e000)
libX11.so.6 => /usr/lib/libX11.so.6 (0x00007f41bfe5f000)
libXext.so.6 => /usr/lib/libXext.so.6 (0x00007f41bfc4d000)
libGLdispatch.so.0 => /usr/lib/libGLdispatch.so.0 (0x00007f41bf997000)
libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f41bf793000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f41bf575000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007f41bf1bd000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007f41bef94000)
/usr/lib64/ld-linux-x86-64.so.2 (0x00007f41c065a000)
libXau.so.6 => /usr/lib/libXau.so.6 (0x00007f41bed90000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007f41beb8a000)

Thanks, cheers and happy new year.


#84

All right. I fixed this problem for my setup. Don’t know if this is a common problem because I haven’t seen it anywhere else. Here’s the deal. libGL is looking for the mesa drivers in the wrong place.

$ LIBGL_DEBUG=verbose glxinfo
[…]
libGL: OpenDriver: trying /usr/lib/xorg/modules/dri/tls/radeonsi_dri.so
[…]

While the dri libraries installed by mesa|lib32-mesa are actually located at /usr/lib/dri and /usr/lib32/dri. To fix the issue I had to symlink this location with the one glxinfo is trying to get:

$ sudo ln -s /usr/lib/dri /usr/lib/xorg/modules/dri
$ sudo mkdir -p /usr/lib32/xorg/modules/
$ sudo ln -s /usr/lib32/dri /usr/lib32/xorg/modules/dri

I can’t tell who is at fault here, if xorg or mesa, but it’s an easy fix. Hope this helps somebody.

EDIT: sudo ln -s /usr/lib32/dri /usr/lib32/xorg/modules/dri


#85

What did I read recently about change around that…

@philm was this a MESA or Xorg change? Or have I remembered something else?


#86

After updating to the latest version (from Manjaro before Christmas) I’m not able to start kmail nor adkonadi anymore. Both crashes with following errors. Any idea what’s wrong?

kmail

QApplication: invalid style override passed, ignoring it.
kf5.kwidgetsaddons: Invalid framesize.
kf5.kwidgetsaddons: Invalid framesize.
Received signal 11 SEGV_MAPERR 000007400017
#0 0x7f0a66bfb086 <unknown>
#1 0x7f0a658271cc <unknown>
#2 0x7f0a66bfb3fc <unknown>
#3 0x7f0a7c6bd8e0 <unknown>
#4 0x7f0a7c6c06f2 __GI___cxa_atexit
#5 0x7f09c8002db0 <unknown>
  r8: 0000000000000000  r9: 0000000000000000 r10: 0000000000000000 r11: 00007f0a4c0e7600
 r12: 07b5427743dad500 r13: 00007f09e8ff8330 r14: 00007f0a4c208da0 r15: 00007f0a4c40d000
  di: 00007f09c8000020  si: 0000000000000000  bp: 0000000000000407  bx: 00007f09c8000020
  dx: 0000561101f7c7f0  ax: 0000000007400007  cx: 0000000000000000  sp: 00007f09e8ff8180
  ip: 00007f0a7c6c06f2 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000006
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000007400017
[end of stack trace]
Calling _exit(1). Core file will not be generated.

akonadi:

QApplication: invalid style override passed, ignoring it.
kf5.kwidgetsaddons: Invalid framesize.
kf5.kwidgetsaddons: Invalid framesize.
kf5.kwidgetsaddons: Invalid framesize.
Received signal 11 SEGV_MAPERR 000007400017
#0 0x7f9f29ba0086 <unknown>
#1 0x7f9f287cc1cc <unknown>
#2 0x7f9f29ba03fc <unknown>
#3 0x7f9f3a1178e0 <unknown>
#4 0x7f9f3a11a6f2 __GI___cxa_atexit
#5 0x7f9e88002db0 <unknown>
  r8: 0000000000000000  r9: 0000000000000000 r10: 0000000000000000 r11: 00007f9f036c7600
 r12: c266d24611423700 r13: 00007f9ec1ffa330 r14: 00007f9f0c6dcda0 r15: 00007f9f0c8e1000
  di: 00007f9e88000020  si: 0000000000000000  bp: 0000000000000407  bx: 00007f9e88000020
  dx: 000056120cd3de20  ax: 0000000007400007  cx: 0000000000000000  sp: 00007f9ec1ffa180
  ip: 00007f9f3a11a6f2 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000006
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000007400017
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Not sure if more applications are affected yet.


#89

Yes, mesa is looking now in a different folder than before. Therefore all Xorg-Server packages and Mesa itself got rebuilt.

https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/mesa&id=333fd67b95f9abb9ea96f4ba3e8f8d2445ec93bc


#90

I wonder if this explains why some people were having difficulties booting the installers with certain hardware/DE/free-non-free combinations…

Just tested on a 32-bit installer in a VM and this appears to be the cause of non-functional X. After creating a symlink (/usr/lib/xorg/modules/dri->/usr/lib/dri) X launches correctly.

I’m hoping this is fixed in later packages.


closed #91

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