- Arch-general - lists.archlinux.org

[arch-general] systemd-suspend hangs from time to time
by Bjoern Franke 02 Apr '18

02 Apr '18

Hi, from time to time, systemd-suspend hangs on my Thinkpad X140e. After starting a suspend (through e.g. closing the lid), the following happens: Mär 21 22:32:56 ostrea systemd[1]: Started Suspend. Mär 21 23:26:07 ostrea systemd[1]: Starting Suspend... Mär 21 23:26:07 ostrea systemd-sleep[11437]: Suspending system... dmesg shows: [40655.526324] PM: suspend entry (deep) [40655.526331] PM: Syncing filesystems ... done. But nothing further happens: JOB UNIT TYPE STATE 68633 systemd-suspend.service start running 68632 suspend.target start waiting After "sudo systemctl restart systemd-suspend" the laptop suspends, but I have no clue why it fails in the first place. I've searched around and found something regarding asynchronous pm, but that did not help. Kind regards Bjoern

1 1

[arch-general] mesa-18.0.0 (currently in [testing]) graphics corruption?
by Oon-Ee Ng 29 Mar '18

29 Mar '18

Any other [testing] users getting severe graphics corruption on mesa-18.0.0? I'm on Intel graphics. Bug report already made https://bugs.archlinux.org/task/58012 but I'm worried this is something unique to my system (unlikely maintainer of mesa would NOT have noticed the symptoms I'm getting...)

2 2

[arch-general] Wireless hardware inconsistent behaviour
by ashwin＠flatty.co 28 Mar '18

28 Mar '18

Hey everyone, I am running Manjaro Linux on a Dell Inspiron 5370. I always have low wifi signal strength and connecting to new networks is almost always a pain. The network manager applet is forever frozen and nmtui keeps dropping network connects. Is there a way I can debug this or look at solving the problem for good? I tried all options in the networking page on the archlinux wiki but none of them seem to properly solve the problem for me. Warm Regards, Ashwin.

4 4

[arch-general] Curious about arch repository policy
by Sudarshan Kakoty 27 Mar '18

27 Mar '18

Hello... I was reading "Arch Wiki" and felt curious about that difference between extra and community repo. Some packages, such as "meson" is in the "extra" repo, whereas "ninja" is in "community" repo. The interesting fact is that - is an implicit dependency to "meson". So why that is (ninja) in the community repo? Also, some critical GNOME specific packages are part of the community repo. Even, some compilers, like Haskell is also part of the community repo. What is the exact difference between extra and community repository? I wonder, Is it really important to have that split? -- Sudarshan Kakoty <skakoty1337(a)yahoo.com>

6 7

[arch-general] FS#57981 - [evolution] doesn't start
by Ralf Mardorf 27 Mar '18

27 Mar '18

Hi, does Evolution upgraded to 3.28.0+... still work for somebody? On my install it doesn't start anymore, see https://bugs.archlinux.org/task/57981 . Regards, Ralf

2 2

[arch-general] Dnscryp-proxy v2 support
by Ngô Huy 26 Mar '18

26 Mar '18

Dnscrypt-proxy v1 has been deleted and then no longer active, version 2 has been released 2.0.7 <https://github.com/jedisct1/dnscrypt-proxy/releases>. Can we rebuild and support new version ? Best regards, Severus

2 2

[arch-general] deluge post-install
by Jude DaShiell 24 Mar '18

24 Mar '18

A warning about a missing service_identity module comes up when deluge-console is used and I am probably not taking all correct steps to install that module to clear this warning. Is this something that can be left alone or has to be left alone? If I found the right module when it installs it doesn't also bring in any dependencies. Should the package build for deluge have this module and dependencies added to it? --

3 4

[arch-general] gtk-sharp-2 conflicts with gtk#
by Morgan Adamiec 22 Mar '18

22 Mar '18

I was doing some packing parsing and my parser failed to parse gtk-sharp-2 from extra. Turns out it's because gtk-sharp-2 conflicts with gtk# and my parser refuses to parse it because of man PKGBUILD stating: PKGNAME: Valid characters for members of this array are alphanumerics, and any of the following characters: “@ . _ + -”. Additionally, names are not allowed to start with hyphens or dots. Now that's for pgkname but I assume that would extend to conflicts and provides or am I mistaken? I'm guessing gtk# used to be a package before those rules were defined and has since been removed. If that's the case I realise that the conflict needs to be there for people who still have gtk# installed. But then again you now have a package in your repos have break your own standards. I don't know if its a good idea to remove that conflict, that's up to the devs. Would just like to know what you think before i go and patch the parser to allow '#'.

3 3

[arch-general] Re-install of Arch on a larger drive
by Trey Sizemore 19 Mar '18

19 Mar '18

Hi all- I currently have Arch running on a 250GB drive, and I'm going to be moving to a 500GB drive. I'm looking for 'best practices' when it comes to the migrating as much as possible during the re-install. It appears that I can migrate my installed packages (standard and AUR repos) via: pacman -Qqe > pkglist.txt and then on the new install, I can use the pkglist.txt generated previously to: pacman -S - < pkglist.txt In addition, by backing up and migrating much of my /home partition (to include 'hidden' config files, anything else I could do to make the process fast and as close to the current install as possible? Thanks!

15 24

[arch-general] Update to 4.15.8 on dual quad-core box locked on ( 3/16) Install DKMS modules, need help resurecting
by David C. Rankin 17 Mar '18

17 Mar '18

All, I experienced a hard lockup during kernel update to 4.15.8 on a Supermicro Dual Opteron Quad-core box. I've updated this box 50 times without issue, but something caused a hardlock. The filesystems are on mdadm linux-raid 1 partitions. The hardlock occurred after the packages were installed and it was in postprocessing at: ( 3/16) Install DKMS modules Now on boot I receive: Warning: /lib/modules/4.15.8-1-ARCH/modules.devname not found - ignoring starting version 237 ERROR: devide `UUID=c7492ac0-e805...` not found. Skipping fsck. mount: /new_root: can't find UUID UUID=c7492ac0-e805... You are being dropped into an emergency shell. sh: can't access tty; job control turned off [rootfs ]# (and the box hardlocks) So I downloaded the 201803 iso to try and fix the box. I have to boot from CD, since this box does not boot from USB. So I burn the .iso to CD (making sure the CD Label is `ARCH_201803`) and boot the box again in attempt to fix it: All goes well until... :: Mounting '/dev/disk/by-label/ARCH_201803' to '/run/archiso/bootmnt' Waiting 30 seconds for device /dev/disk/by-label/ARCH_201803 ... ERROR: '/dev/disk/by-label/ARCH_201803' device did not show up after 30 seconds ... Falling back to interactive prompt You can try to fix the problem manually, log out when you are finished sh: can't access tty; job control tuned off [rootfs ]# (thankfully this prompt is not hardlocked) This is bizarre, I've created the iso, sha1sums are correct, CD label is 'ARCH_201803', but the iso won't boot. I've researched, but these solutions don't solve the problem: https://bbs.archlinux.org/viewtopic.php?id=195671 https://superuser.com/questions/519784/error-installing-arch-linux https://bugs.launchpad.net/bugs/1318400 Check /dev/disk from the recovery prompt, there is no "by-label" directory under /dev/disk to begin with. Attempting to create 'by-label' and softlinking /dev/sr0 to /dev/disk/by-label/ARCH_201803 does create a series of additional errors I/O errors concluding with, mount: /run/archiso/bootmnt: wrong fs type, bad option, bad superblock on /dev/sr0, missing codepage or helper system .... So I'm snakebit and need help. I've never had the system lock during kernel update before and it has left part of the system thinking it has 4.15.7 and the rest thinking it is 4.15.8 (but the 4.15.8 update never finished) (1) How do I go about recovering? 4.15.7 was A-OK. I'm not sure what part of the install is still 4.15.7 and what's 4.15.8. 59 packages were updated, including the kernel and lts-kernel, but the initramfs was never regenerated due to the failure at the 'Install DKMS modules' phase. If I can get the ARCH_201803 install media to boot properly -- what next? (2) How do I get around the ERROR: '/dev/disk/by-label/ARCH_201803' device did not show up after 30 seconds problem? The disk label is correct, it's just not being seen and mounted by the installer to /run/archiso/bootmnt Any help greatly appreciated. -- David C. Rankin, J.D.,P.E.

7 17