Poll

Did you experience any issue with this update?

No issues, everything went smoothly.
138 (73%)
Yes there was an issue. I was able to resolve it myself. (Please post your solution)
11 (5.8%)
Yes I am currently experiencing an issue due to the update. (Please post about it)
40 (21.2%)

Total Members Voted: 189

Author Topic: [Update] 2016-02-21 - Kernels, KDE, Pamac, Firefox, Thunderbird, Lumina, Intel  (Read 22448 times)

0 Members and 1 Guest are viewing this topic.

Offline mmtm

  • Neuling
  • *
  • Posts: 6
  • I'm new. Be nice!
  • Branch: stable
  • Desktop: i3
  • GPU Card: Intel
  • GPU driver: free
  • Kernel: linux44-x64
  • Skill: Novice
Hi, I'm still stuck at boot with my encrypted disk. The cli command from heyne001 did not help me much. Here is what I've got.
I booted a live usb stick with manjaro KDE 15.12. I opened konsole and typed su and unlocked my hard drive.
I am not that good with chroot. I never did that before.

Code: [Select]
[manjaro manjaro]# lsblk -f
NAME                        FSTYPE      LABEL       UUID                                   MOUNTPOINT
sda                                                                                       
├─sda1                      ext2        ManjaroBoot 403bcce7-a3d3-4103-a6cf-5acf3ded9cb6   /run/media/manjaro/ManjaroBoot
└─sda2                      crypto_LUKS             37f05b17-edfc-4d5d-a9c8-3f729d5d9043   
  └─root                    LVM2_member             DFLKL1-KC4r-qZU2-JYnX-gZrp-6K8o-FtHCF2
    ├─ManjaroVG-ManjaroRoot ext4        ManjaroRoot bc61870e-ec40-4ecc-80a4-1e52832881e0   /run/media/manjaro/ManjaroRoot
    ├─ManjaroVG-ManjaroSwap ext4                    599cb3d7-de91-4995-8acd-2573f4a5b4e0   
    └─ManjaroVG-ManjaroHome ext4        ManjaroHome 384f1407-a332-4545-803d-c71d1eb19598   /run/media/manjaro/ManjaroHome
sdb                         iso9660     MJRO1512    2015-12-22-16-57-08-00                 
├─sdb1                      iso9660     MJRO1512    2015-12-22-16-57-08-00                 /bootmnt
└─sdb2                      vfat        MISO_EFI    B499-C7EC                             
loop0                       squashfs                                                       
loop1                       squashfs                                                       
loop2                       squashfs                                                       
loop3                       squashfs                                                       
[manjaro manjaro]# ls -ll /dev/mapper/
total 0
crw------- 1 root root 10, 236 Feb 24 13:33 control
lrwxrwxrwx 1 root root       7 Feb 24 13:34 ManjaroVG-ManjaroHome -> ../dm-3
lrwxrwxrwx 1 root root       7 Feb 24 13:34 ManjaroVG-ManjaroRoot -> ../dm-1
lrwxrwxrwx 1 root root       7 Feb 24 13:34 ManjaroVG-ManjaroSwap -> ../dm-2
lrwxrwxrwx 1 root root       7 Feb 24 13:34 root -> ../dm-0
[manjaro manjaro]# mount -t ext4 /dev/mapper/root /mnt
mount: /dev/mapper/root is already mounted or /mnt busy
[manjaro manjaro]# mount /dev/sda1 /mnt/boot
mount: mount point /mnt/boot does not exist
[manjaro manjaro]# cd /mnt
[manjaro mnt]# ls -lart
total 0
drwxr-xr-x 2 root root   3 Sep 30 20:43 .
drwxr-xr-x 1 root root 160 Feb 24 13:13 ..

So how could I mount root and boot properly to chroot and install the new kernet?
Any help is greatly appreciated.

Try this:

Code: [Select]
# su

# cryptsetup open --type luks /dev/sda2 root

# mount -t ext4 /dev/mapper/ManjaroVG-ManjaroRoot /mnt

# mount /dev/sda1 /mnt/boot
# mount --bind /dev /mnt/dev
# mount --bind /dev/pts /mnt/dev/pts
# mount --bind /proc /mnt/proc
# mount --bind /sys /mnt/sys
# mount --bind /run /mnt/run

make a backup of /mnt/etc/resolv.conf; dont't know if this is necessary, but better safe than sorry?  ;)
and then:
Code: [Select]
# cp /etc/resolv.conf /mnt/etc/resolv.conf


# chroot /mnt /bin/bash

That worked in my case.  O:-)

Have you gotten so far you then can run pacman -Syu and/or install another kernel.  :)

Offline jonathon

  • Core Team
  • *****
  • Posts: 2104
  • Technologist - Teacher - Tea drinker
  • Branch: Unstable
  • Desktop: MATE 1.14
  • GPU Card: Nvidia GTX680M
  • GPU driver: Bumblebee nvidia+intel
  • Kernel: 4.6.0-*-MANJARO x86_64
  • Skill: Advanced
So... does anyone have any idea what to do about the mouse jack? Logitech site is a joke and I've found nothing on LKML

Reading that article:

Quote
More than half of the mice are not able to be updated and will not be patched.

which is just great.

You might try Windows in a virtual machine - that has worked for me in the past with other Windows-only device updates. No need to buy anything, use the MS browser testing images: https://dev.windows.com/en-us/microsoft-edge/tools/vms/ (worth remembering: http://modern.ie/)
--
MSI GT70: Core i7-3630QM, 16GB, Nvidia GTX680M, Intel 2230, Manjaro-MATE-amd64-EFI
Lenovo X230: Core i5-3320M, 4GB, Intel HD4000, Intel 6205, Manjaro-MATE-amd64
Dell Studio 1749: Core i5 540, 8GB, ATi HD5650, Intel WLAN, Manjaro-Xfce-amd64
Let's go in the garden; you'll find something waiting.

Offline jinformatique

  • Neuling
  • *
  • Posts: 10
  • I'm new. Be nice!
  • Branch: stable
  • Desktop: KDE
  • Kernel: x64
  • Skill: Intermediate
@LA-MJ
I checked the arch wiki. I tried yesterday during 2 hours. I was able to mount my root volume but I did not get the part where to mount the boot and chroot is new to me. I'm a Kubuntu user since 2006 and switched to Manjaro a year ago. I choosed it because there is a GUI to install it, it's rolling release, latest software all the time and KDE. I have a 2 yo kid and don't have so much time anymore to play with debugging stuff. I am happy to use it for what I have to do that's all.

@mmtm
THANKS man, that worked like a charm!! I am back in my desktop. Yeayy.
At the end I did:
Code: [Select]
sudo mhwd-kernel -i linux44
reboot
And all was back to normal.

@fredhoud
Ok for the `Grub-Customizer` tip, I'll never touch it.

Thanks to the manjaro team for this great distro with so much effort put in there.

Offline quatrolibro

  • Neuling
  • *
  • Posts: 1
  • I'm new. Be nice!
  • Desktop: KDE 5
  • GPU Card: Intel & nVidia
  • GPU driver: free
  • Skill: Novice
My first issue from about 6 months with Manjaro. After last upgrade
Code: [Select]
libsystemd (229-2 -> 229-3)
systemd (229-2 -> 229-3)
lib32-systemd (228-1 -> 229-0.1)
system hangs on shutdown with no message.
Code: [Select]
dev/sda5: clean, (numbers) files (numbers) blocks
_
 
Sometines hangs on black screan with Manjaro logo.
Linux 4.4.2-1 and 4.3.6-1





« Last Edit: 25. February 2016, 15:45:24 by quatrolibro »

Offline cb474

  • Vollwertiges Mitglied
  • ***
  • Posts: 169
Yes, I said in my original post, to which you responded, that I have 1.7.0-1.1 installed.

Actually, you said:

I did the upgrade today, so the latest version of cryptsetup that fixes the encryption bug was already in the stable repo. So I have cryptsetup 1.7.0-1.1 on my system.

You didn't specifically say you had checked the package version, and I interpreted what you said as that you assumed the package version was current. You might think verifying these things is trite, but after you do any sort of support for any length of time you learn that making assumptions about what users mean is a dangerous thing. Making sure you get unambiguous verification avoids hella problems.

Heard the anecdote about tech support asking whether the non-functioning device is actually plugged in and turned on? Experienced users will say "hang on, I'll double check". Inexperienced users will say "of course it is! That would be stupid!" And how many times is the thing not plugged in and turned on? More than you'd think.

Honsetly, I don't know how "I have cryptsetup 1.7.0-1.1 on my system" could mean anything other than I have cryptsetup 1.7.0-1.1.

I also explained that I did the upgrade a couple days after the updated version of cryptsetup went into the repo, so I indicated that I knew what was in the repo when. In other words, I explained not once but twice that I had 1.7.0-1.1 on my system. You really have to bend over backwards to almost deliberately misread my post to see it the way you claim you did.

Also, all you said in your reply to my initial post was, "Is that the package you have installed? You could also try updating (again) to see if 1.7.0-2 is available." You didn't say, "Did you check the package version or are you just assuming you have it because you did the upgrade?" It really seems like you didn't read my post closely, assumed I didn't know what I was doing, didn't actually have an answer to my question, and weren't being careful with taking time with the wording of your own post.

This is a forum, not tech support. My experience with countless years in Linux forums is that lots of people respond to posts without really reading them and ask questions that are answered in the post; they do this more because they like to see themselves as helpful, than because they have any relevant input. That happens constantly. I don't know how often I have to repeat exactly what I already said, I can't keep track anymore. So rather than lecturing me and making assumptions about how experienced I am with Linux, you might just say, "sorry, I misunderstood your post" or "I should have been more clear what I was asking."
« Last Edit: 25. February 2016, 06:58:21 by cb474 »

Offline notageek

  • Jr. Mitglied
  • **
  • Posts: 84
  • I'm new. Be nice!
  • Branch: Stable
  • Skill: Novice
I'm experiencing most of the time a delay in shutdown and reboot, more then one minute after systemd update
my old friend 'Failed to finalize file system, ignoring' is still there from systemd 226

rest is ok, no drive encryption
Plasma 5 Kernel 319-318 on Dell Precision M4800 i7 4800MQ NVidia Optimus K1100M + Intel HD 4600 16 GB RAM SSD Samsung 840 Pro
Plasma 5 Kernel 44-41 on Lenovo X1 Carbon Gen3 i5 5200 Intel HD 5500 8 GB RAM SSD Samsung SM951

Offline Strit

  • Maintainer
  • ***
  • Posts: 746
  • Manjaro Torrent Maintainer
    • Strits.dk
  • Branch: Stable
  • Desktop: XFCE
  • GPU Card: GTX 760 OC
  • GPU driver: Non-free nvidia 361
  • Kernel: 4.4.8-1-MANJARO
  • Skill: Intermediate
Small problem with Cantarell font and harfbuzz (I think). Some language specific characters does not get displayed correctly.
This is already fixed in unstable branch, so I'll just wait for the next Cantarell/Harfbuzz update in Stable. :)
Desktop PC: Manjaro XFCE 15.12 (stable, kernel 4.4)
Private Laptop: Manjaro Strit 16.03 (unstable, kernel 4.6)
Work Laptop: Manjaro Strit 16.03 (stable, kernel 4.4)
Netbook: Arch Linux XFCE/LXqt (i686, kernel 4.0)

Offline enrico_zh

  • Neuling
  • *
  • Posts: 6
  • I'm new. Be nice!
  • Branch: stable
  • Desktop: Xfce
  • GPU Card: Intel 3rd Gen
  • GPU driver: driver: intel
  • Kernel: 4.4.8-1-MANJARO x86_64
  • Skill: Novice
'Failed to finalize file system, ignoring' is still there from systemd 226
The same with my not so old friend  :D
Grüsse, Enrico

Offline ansich

  • Jr. Mitglied
  • **
  • Posts: 96
  • Desktop: Xfce
  • GPU Card: Intel Mobile 4 Series
  • Kernel: linux 41
  • Skill: Intermediate
When I updated libreoffice-fresh to 5.1 the font rendering was different and not in a good way. Times New Roman fonts for example were rendering like they did on my windows machine (at certain magnification they letters would get quite bold while the italics stayed thin). In general the rendering for all the fonts was less pleasant and also scrolling through the document was slower (seemed like the mouse had a smaller scroll interval and I did not find the setting to change it).

So I downgraded it back to 5.0.4.2.
« Last Edit: 26. February 2016, 11:33:08 by ansich »

Offline omnimoon

  • Neuling
  • *
  • Posts: 18
  • Former distrohopper
  • Branch: stable
  • Desktop: KDE / Xfce
  • GPU Card: Nvidia GeForce 940M / ATI Radeon HD 6310
  • GPU driver: non-free
  • Kernel: linux44-x64 / linux43-x64
  • Skill: Novice
Okay, VICTORY (at least so far)

Managed to install the latest kernel (45 rc) and it's working. Also tried 44, but couldn't log in - first there was a black screen and then a white screen saying that something went wrong (rly).

For all still struggling, maybe the following helps. This is what I did once in the live system and open terminal:

Code: [Select]
# su
Code: [Select]
# cryptsetup open --type luks /dev/sda2 root
Code: [Select]
# mount -t ext4 /dev/mapper/root /mnt
These are optional - if you want to install a new kernel:
Code: [Select]
# mount /dev/sda1 /mnt/boot
# mount --bind /dev /mnt/dev
# mount --bind /dev/pts /mnt/dev/pts
# mount --bind /proc /mnt/proc
# mount --bind /sys /mnt/sys

Code: [Select]
# chroot /mnt /bin/bash
Install the updated cryptsetup package and/or linux45
Code: [Select]
pacman -U /var/cache/pacman/pkg/cryptsetup-1.7.0-1.1-$(uname -m).pkg.tar.xz
Code: [Select]
pacman -S linux45

I had never used chroot before, so at the beggining it was difficult for me to follow the instructions from the Arch wiki. But this made it really easy and I could finally install a new kernel, everything is working back again! No system reinstalling, no starting all over again... Thank you so much!! And thaks to the team and everyone for making such a wonderful community.

Offline theMuspilli

  • Neuling
  • *
  • Posts: 21
  • I'm new. Be nice!
    • me on dA
  • Branch: stable
  • Desktop: xfce
  • Skill: Intermediate
@heyne001: also I want to thank you! Your posting made dealing with the kernel / cryptset issue a lot easier.  ;D I used to copy a lot from it when trying to find the right kernel.

Clean install issue:

And an information for all who care: new users doing a clean install from the latest live cd [1][2] will still run into the problem with the first innocent system update (only if they have chosen to encrypt their system, off course), With the update they get  kernel 4.1.18, cryptsetup 1.7.0-1.1 and a system that cannot decrypt their freshly set up root partition and therefore will not boot. I do not think that many of them will continue with manjaro.

I mean.. how does it look like to a new user? You install from CD, you thankfully use the option to encrypt your system, you make the first recommendable update (because there are newer versions of lotsa stuff than were on the cd) and voila' your system will not boot anymore. If you know nothing else about manjaro then this won't  give you the right impression of a distribution you can trust.

I don't have the knowledge to tell you what would be the right way of handling this. I don't know what bells and whistles exist that could prevent the problem.  Perhaps make the live-cds step over to linux44. With the combination

- Kernel: x86_64 Linux 4.4.2-1-MANJARO
- cryptsetup-1.7.0-2-x86_64 (obtained via downgrade)

I experience no problems so far. But iirc also linux41 is LTS and therefore it would be nice if also for 41 this issue could be solved.

And a short suggestion for the managment of this issue...

If you want to know what helped the most, it was the posting of heyne001. Concrete advices, the right amount of explanation and easy to follow instructions. In a crisis situation where one has to repair his system from outside the comfort zone (like from a live cd which does not reflect your normal customized working environment at all) this has been exactly what was needed. With copy & paste I just needed to change the drive and could focus on the problem.
This posting, maybe with the resolv.conf addition,  should have been put sticky  somewhere even easier to find (search engines - startpage.com, duckduckgo, google - still do not find it for me, even when I am very precisely stating what I am looking for)..

What I am still missing is a list of kernel-cryptsetup combinations that are *tested* to be working ok now.  I might have had just bad luck, but I had to test some combinations until my old system was able to boot again and then it did feel unstable (also a reason for the clean install).

Moreover I wondered which other options there might have been. I myself was most unsuccessful when downgrading kernel and cryptsetup, but I think this also might have been a possibility. Then I wondered if one could not have simply removed the encryption of the root drive? I did not consider that, but it might have been possible.
 
the footnotes:
[1] I tried xfce flavor and the kernel was 4.1.15
[2] I decided for a clean new install yesterday. My now old manjaro install was xfce installed as a second de on top of a manjaro kde installation. It had become a bit bloated and often kept me wondering which kde components could be safely removed and which I would need for the kde programs that I run... It had some minor issues as well... After having played a lot to find a working kernel cryptsetup combination I did not feel comfortable with the result and therefore went for a new start.

Offline RacerBG

  • Jr. Mitglied
  • **
  • Posts: 71
  • Lost in translation!
  • Branch: Stable
  • Desktop: XFCE
  • Kernel: linux41-x86
  • Skill: Intermediate
Around 1-2 times per month I'm updating my Manjaro install and guys this OS and updates are rock solid! :) No issues at all, everytime the update is smooth as possible.
Manjaro Linux Bulgarian Translator

Offline jonathon

  • Core Team
  • *****
  • Posts: 2104
  • Technologist - Teacher - Tea drinker
  • Branch: Unstable
  • Desktop: MATE 1.14
  • GPU Card: Nvidia GTX680M
  • GPU driver: Bumblebee nvidia+intel
  • Kernel: 4.6.0-*-MANJARO x86_64
  • Skill: Advanced
@muncharo

I've moved your issues off to their own thread to make keeping track of process easier: https://forum.manjaro.org/index.php?topic=31600.0
--
MSI GT70: Core i7-3630QM, 16GB, Nvidia GTX680M, Intel 2230, Manjaro-MATE-amd64-EFI
Lenovo X230: Core i5-3320M, 4GB, Intel HD4000, Intel 6205, Manjaro-MATE-amd64
Dell Studio 1749: Core i5 540, 8GB, ATi HD5650, Intel WLAN, Manjaro-Xfce-amd64
Let's go in the garden; you'll find something waiting.

Offline thor_20

  • Sr. Mitglied
  • ****
  • Posts: 362
  • I became...
  • Branch: stable - hopefully... :)
  • Desktop: XFCE
  • GPU Card: nVidia FX 1800 quadro
  • GPU driver: The proprietry ones...
  • Kernel: 3.18.30-1-MANJARO
  • Skill: Intermediate
Hi all,
Pretty late in the update, as usual. No issues...on a vanilla system :)
Thanks team
Melissa
I hate contants in source code...they do not reflect real life...
Change...the one constant in the universe...
=^.^=

Offline art

  • Neuling
  • *
  • Posts: 7
  • I'm new. Be nice!
  • Branch: stable
  • Desktop: Xfce
  • Skill: Novice
Hi,

I'm running Manjaro since July last year on my main notebook - everything was fine.
Before I had ~2-3 years Linux Mint Debian on the former notebook, as I do love the idea of rolling releases; but the frequency of update was very low.

Now I do have an mayor issue and I have no clue, how to solve that.
I'm running the stable branch of Manjaro x64 Xfce and did an update on Saturday with Manjaro Update 2016-02-21 (stable) which now results in kernel 4.1.18-1-Manjaro x64.
I did not read the "Talk about this update" carefully, as I wrongly thought that I did do that update already the weekend before  :(
Next time I do need to be more careful on that.
On Sunday I did reboot and surprise --> no success. :o
I do have encrypted the whole disk and now run into the trouble during boot-up:
   Failed to setup dm_crypt ...
   Check that the kernel supports aes_xts_plain64 cipher.
I tried the fix_tutorial several times - but unfortunately without success.
Booting from Live-CD, opening a terminal (no further program is started) ...
Code: [Select]
[manjaro@manjaro ~]$ su
[manjaro manjaro]# mkdir /mnt/root
[manjaro manjaro]# cryptsetup open /dev/sda2 root
Geben Sie die Passphrase für »/dev/sda2« ein:
[manjaro manjaro]# mount /dev/mapper/ManjaroVG-ManjaroRoot /mnt/root
[manjaro manjaro]# chroot /mnt/root /bin/bash
[root@manjaro /]# pacman -U http://repo.manjaro.org.uk/pool/overlay/cryptsetup-1.7.0-1.1-$(uname -m).pkg.tar.xz
Lade Pakete...
Fehler: '/var/cache/pacman/pkg/cryptsetup-1.7.0-1.1-x86_64.pkg.tar.xz': Erforderliche Signatur für Paket fehlt
[root@manjaro /]# pacman -U /var/cache/pacman/pkg/cryptsetup-1.7.0-1.1-$(uname -m).pkg.tar.xz
Lade Pakete...
Warnung: cryptsetup-1.7.0-1.1 ist aktuell -- Reinstalliere
Löse Abhängigkeiten auf...
Suche nach in Konflikt stehenden Paketen...

Pakete (1) cryptsetup-1.7.0-1.1

Gesamtgröße der installierten Pakete:  1,14 MiB
Größendifferenz der Aktualisierung:  0,00 MiB

:: Installation fortsetzen? [J/n] J
(1/1) Prüfe Schlüssel im Schlüsselring             [######################] 100%
(1/1) Überprüfe Paket-Integrität                   [######################] 100%
(1/1) Lade Paket-Dateien                           [######################] 100%
(1/1) Prüfe auf Dateikonflikte                     [######################] 100%
:: Verarbeite Paketänderungen...
(1/1) Installiere cryptsetup                       [######################] 100%
[root@manjaro /]# exit
exit
[manjaro manjaro]# umount /mnt/root
[manjaro manjaro]# cryptsetup close root
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
device-mapper: remove ioctl on root failed: Das Gerät oder die Ressource ist belegt
Gerät »root« wird gerade benutzt.
[manjaro manjaro]# pwd
/home/manjaro
I also tried, what was suggested in the forum (from heyne001)...

For all still struggling, maybe the following helps. This is what I did once in the live system and open terminal:
Code: [Select]
# su
# cryptsetup open --type luks /dev/sda2 root
# mount -t ext4 /dev/mapper/root /mnt
# mount /dev/sda1 /mnt/boot
# mount --bind /dev /mnt/dev
# mount --bind /dev/pts /mnt/dev/pts
# mount --bind /proc /mnt/proc
# mount --bind /sys /mnt/sys
# chroot /mnt /bin/bash
pacman -U /var/cache/pacman/pkg/cryptsetup-1.7.0-1.1-$(uname -m).pkg.tar.xz
pacman -S linux45

but with the last command I got a hell of error messages (I did not log that) - I do have the impression this "linux45" is not on the servers.

Any tip?
I do not have experience with this deep stuff of kernel, cryptsetup and pacman topics - as I'm much much more a user of Manjaro.
And up to now was pretty happy.
But now I have no clue to come out of that. ???