[Stable Update i686] 2019-09-20 - Another very large set of updates

Hello i686ers!

This has been a while coming due to the number of rebuilds required. It updates pretty much everything, so strap in.

I strongly recommend applying this update in a TTY or screen session:


Available kernels

Series Version PAE
linux316 3.16.73 No
linux44 4.4.193 No
linux49 4.9.193 No
linux414 4.14.145 No
linux419 4.19.74 Yes

Full list of changes

Full list of changes available here (around 6350 updated packages).


Anyone who would like to help out testing the upstream packages, please read the archlinux32 thread for details about how they automate their testing process and how to get involved:

https://bbs.archlinux32.org/viewtopic.php?id=171

(running this in an archlinux32 VM would be fine, there will hopefully be a way of doing this directly from within manjaro32 in the future)


archlinux32

If you find manjaro32 useful please consider donating to, or helping out with, archlinux32. It's a small team taking on a huge project and any help will no doubt be very much appreciated.

Why aren't the available packages/package versions the same as x86_64?

archlinux32 packages are based on Arch packages but may need editing to build correctly. Builds of less-popular packages are lower priority.

Manjaro-specific packages may lag behind x86_64 because there aren't as many packagers. If you notice an important package is lagging please report it; at the moment it's only me packaging for i686:

I'm only packaging current LTS kernels. Any marked as EOL are dropped. I'll not be building the mainline kernel.

What about security updates?

I cannot guarantee timely security updates on x32-stable. If this is critical for you I recommend you switch to x32-testing or cherry-pick those packages from x32-testing or x32-unstable as they become available.

Something broke. Isn't this meant to be stable?

"Stable" means "infrequently changing", not "everything will work perfectly all the time". If you want it to mean everything works, you need to help test the things you're interested in.

What about installer images?

Yes, this is old and doesn't work particularly well. Because time.

What about x32-testing and x32-unstable?

These are already available, and I recommend you use x32-testing if you can to make sure testing is done.

x32-unstable should be used by the adventurous who want to try and find any issues before they impact other people. If you have multiple/many machines you really should run one of those on x32-unstable. However: expect breakage.


Any problems?

  • No issues, 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


6 Likes

Known Issues and Solutions


Incompatible libdevmapper 1.02.164 (2019-08-27) and kernel driver (unknown version).

This happens every so often when there's a kernel ABI change. As far as I know it's harmless and can be ignored.


xfwm4 crashes when zooming

Not sure why it does this; there's no obvious reason.


Pacui fails to display package list

Options "3 Install packages" and "4 Remove packages and deps" don't work in pacui.

  • Workaround: Install fzf-git from AUR. Until resolved in this topic.

upower 0.99.11 fails to start

  • workaround: downgrade to upower 0.99.10-1.1

Xfce4-panel diappeared

Log out and relogin. The panel will be there, but without all widgets.

1 Like

Weekend kernels:

:: Different overlay package(s) in repository core i686

-------------------------------------------------------------------------------
                             PACKAGE           x32-stable          x32-testing
-------------------------------------------------------------------------------
                            linux414           4.14.145-1           4.14.146-1
                    linux414-headers           4.14.145-1           4.14.146-1
                            linux419            4.19.74-1            4.19.75-1
                    linux419-headers            4.19.74-1            4.19.75-1
                             linux44            4.4.193-1            4.4.194-1
                     linux44-headers            4.4.193-1            4.4.194-1
                             linux49            4.9.193-1            4.9.194-1
                     linux49-headers            4.9.193-1            4.9.194-1


:: Different overlay package(s) in repository extra i686

-------------------------------------------------------------------------------
                             PACKAGE           x32-stable          x32-testing
-------------------------------------------------------------------------------
                         kinfocenter             5.15.5-1             5.16.5-1
                  linux414-acpi_call            1.1.0-145            1.1.0-146
                   linux414-bbswitch              0.8-145              0.8-146
                linux414-broadcom-wl     6.30.223.271-145     6.30.223.271-146
                linux414-ndiswrapper             1.62-145             1.62-146
               linux414-nvidia-340xx          340.107-145          340.107-146
                      linux414-r8168         8.047.02-145         8.047.02-146
                  linux414-rt3562sta       2.4.1.1_r4-145       2.4.1.1_r4-146
                linux414-vhba-module         20190831-145         20190831-146
   linux414-virtualbox-guest-modules            6.0.8-145            6.0.8-146
    linux414-virtualbox-host-modules            6.0.8-145            6.0.8-146
                        linux414-zfs            0.8.1-145            0.8.1-146
                  linux419-acpi_call             1.1.0-74             1.1.0-75
                   linux419-bbswitch               0.8-74               0.8-75
                linux419-broadcom-wl      6.30.223.271-74      6.30.223.271-75
                linux419-ndiswrapper              1.62-74              1.62-75
               linux419-nvidia-340xx           340.107-74           340.107-75
                   linux419-nvidiabl              0.88-74              0.88-75
                      linux419-r8168          8.047.02-74          8.047.02-75
                linux419-vhba-module          20190831-74          20190831-75
   linux419-virtualbox-guest-modules             6.0.8-74             6.0.8-75
    linux419-virtualbox-host-modules             6.0.8-74             6.0.8-75
                        linux419-zfs             0.8.1-74             0.8.1-75
                   linux44-acpi_call            1.1.0-193            1.1.0-194
                 linux44-broadcom-wl     6.30.223.271-193     6.30.223.271-194
                    linux44-catalyst    1:15.201.1151-193    1:15.201.1151-194
                 linux44-ndiswrapper             1.62-193             1.62-194
                       linux44-r8168         8.047.02-193         8.047.02-194
                   linux44-rt3562sta       2.4.1.1_r4-193       2.4.1.1_r4-194
                 linux44-vhba-module         20190831-193         20190831-194
    linux44-virtualbox-guest-modules            6.0.8-193            6.0.8-194
     linux44-virtualbox-host-modules            6.0.8-193            6.0.8-194
                         linux44-zfs            0.8.1-193            0.8.1-194
                   linux49-acpi_call            1.1.0-193            1.1.0-194
                    linux49-bbswitch              0.8-193              0.8-194
                 linux49-broadcom-wl     6.30.223.271-193     6.30.223.271-194
                    linux49-catalyst    1:15.201.1151-193    1:15.201.1151-194
                 linux49-ndiswrapper             1.62-193             1.62-194
                linux49-nvidia-340xx          340.107-193          340.107-194
                       linux49-r8168         8.047.02-193         8.047.02-194
                 linux49-vhba-module         20190831-193         20190831-194
    linux49-virtualbox-guest-modules            6.0.8-193            6.0.8-194
     linux49-virtualbox-host-modules            6.0.8-193            6.0.8-194
                         linux49-zfs            0.8.1-193            0.8.1-194

upower not working after latest update with linux316, linux318 and linux49

Hello, and again many thanks to your hard work

I prefer running linux kernel series 3 on my aged laptop. I was not happy with stopping the maintainence of linux318 because this kernel was compatible with libQt5Core.so.5. Linux has to be >=3.17. Just found a workaround to work with maintained linux316! Its the .note.ABI-tag in libQt5Core.so.5. Did 'strip --remove-section=.note.ABI-tag /usr/lib/libQt5Core.so.5.x.y' as root and voila Qt5 dependent manjaro-settings-manager is working with linux316. So I had been happy for a short time.
After the latest marathon update upowerd.service is not loading with linux316, linux318 and linux49. Its working fine with linux419. After stopping upowerd.service, starting upowerd manually (sudo /usr/lib/upowerd &) the deamon was working fine. Please need some help weather its a systemd or a upower related problem. I would like to stay with linux316 or linux318.

Thank you in advance

got two warning

warning: directory permissions differ on /etc/NetworkManager/system-connections/
filesystem: 755  package: 700
warning: directory permissions differ on /var/lib/AccountsService/icons/
filesystem: 775  package: 755

fixed

than the intel video was giving some problems
have to modify intel.conf
now everything seem fine :smiley:

Update on 1 System and 1 VB without Problems.

DK3

Systemctl start upowerd failure in manjaro32 after sysupdate 2019/09/21

Fails with linux316, linux318 and linux49, not linux419
Here some data and messages from my system.

# inxi -CM
Machine: Type: Portable System: Acer product: TravelMate 290 v: 290 serial:
Mobo: Intel model: 855GM v: FAB-2 serial: BIOS: ACER v: 2.00 date: 07/29/2004
CPU: Topology: Single Core model: Intel Pentium M bits: 32 type: MCP L2 cache: 2048 KiB
Speed: 1800 MHz min/max: 600/1800 MHz Core speed (MHz): 1: 1800

# mhwd-kernel -li
Currently running: 3.16.73-1-MANJARO (linux316)
The following kernels are installed in your system:

  • linux316
  • linux318
  • linux419
  • linux49

# uname -a
Linux loki 3.16.73-1-MANJARO #1 SMP PREEMPT Sat Aug 24 11:26:11

# systemctl status upower
● upower.service - Daemon for power management
Loaded: loaded (/usr/lib/systemd/system/upower.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2019-09-22 17:46:27 CEST; 9min ago
Docs: man:upowerd(8)
Process: 1070 ExecStart=/usr/lib/upowerd (code=exited, status=217/USER)
Main PID: 1070 (code=exited, status=217/USER)

Sep 22 17:46:27 loki systemd[1]: upower.service: Service RestartSec=100ms expired, scheduling restart.
Sep 22 17:46:27 loki systemd[1]: upower.service: Scheduled restart job, restart counter is at 5.
Sep 22 17:46:27 loki systemd[1]: Stopped Daemon for power management.
Sep 22 17:46:27 loki systemd[1]: upower.service: Start request repeated too quickly.
Sep 22 17:46:27 loki systemd[1]: upower.service: Failed with result 'exit-code'.
Sep 22 17:46:27 loki systemd[1]: Failed to start Daemon for power management.

# systemctl restart upower
Job for upower.service failed because the control process exited with error code.
See "systemctl status upower.service" and "journalctl -xe" for details.

# journalctl -xe
Sep 22 17:57:33 loki systemd[1]: Stopped Daemon for power management.
-- Subject: A stop job for unit upower.service has finished
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
--
-- A stop job for unit upower.service has finished.
--
-- The job identifier is 4357 and the job result is done.
Sep 22 17:57:33 loki systemd[1]: upower.service: Start request repeated too quickly.
Sep 22 17:57:33 loki systemd[1]: upower.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
--
-- The unit upower.service has entered the 'failed' state with result 'exit-code'.
Sep 22 17:57:33 loki systemd[1]: Failed to start Daemon for power management.
-- Subject: A start job for unit upower.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
--
-- A start job for unit upower.service has finished with a failure.
--
-- The job identifier is 4357 and the job result is failed.
lines 3417-3439/3439 (END)

# upower -v
(upower:1180): UPower-WARNING **: 18:02:27.242: Cannot connect to upowerd: Fehler ↵
beim Aufruf von StartServiceByName für org.freedesktop.UPower: Failed to activate ↵
service 'org.freedesktop.UPower': timed out (service_start_timeout=25000ms)

# sudo systemctl stop upower
# sudo /usr/lib/upowerd --immediate-exit -v

TI:18:09:43 Acquired inhibitor lock (10)
TI:18:09:43 Starting upowerd version 0.99.11

(upowerd:1290): GLib-CRITICAL **: 18:09:43.994: g_source_set_name_by_id: assertion 'tag > 0' failed
TI:18:09:43 cannot find a keyboard backlight
TI:18:09:43 daemon now coldplug
...

# sudo /usr/lib/upowerd &
# upower -v
UPower client version 0.99.11
UPower daemon version 0.99.11

WORKAROUND
##########
Downgrade to upower 0.99.10-1.1

(EOF)

@jonathon
Please have a look at newest upower package

1 Like

Loss of terminal, success by installing termite
Gimp not working (still)
Loss of panels and icons, success by logout/login/new setup

Like in testing I have the xfwm4 zooming problem mentioned in known issues.


I also have an issue in both staple and testing when power management blanks the screen. When I unlock the screen I get a black screen and a cursor, I then have to reboot the system from tty2 (or restart lightdm).

Workround:
Removed light-locker, xfce4-power-manager
Installed xscreensaver

!! Workaround !!
sudo ln -s /usr/lib/libmypaint-1.4.so.0.0.0 /usr/lib/libmypaint-1.3.so.0

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

Forum kindly sponsored by Bytemark