April 2018 - Arch-general - lists.archlinux.org

[arch-general] valgrind 3.13.0-6 exclusions broken again
by David C. Rankin 08 Apr '18

08 Apr '18

Devs, valgrind is reporting more memory allocated than actual. This occurred a couple of months back as well, was resolved, and is now apparently back again? I don't know if this is a regression, but for each allocation, an additional allocation is reported and up to 2^10 additional bytes are reported. Here is a short example where 1 allocation of 10-bytes is made: #include <stdio.h> #include <stdlib.h> #define NVAL 10 int main (void) { char *a = calloc (NVAL, sizeof *a); if (!a) { perror ("calloc - a"); return 1; } /* fill with [a-i] and output */ for (int i = 0; i < NVAL - 1; i++) a[i] = 'a' + i; printf ("a: '%s' (1 alloc - %lu bytes)\n", a, sizeof *a * NVAL); free (a); } However, valgrind reports 2 allocations and 1034-bytes (10 + 2^10), e.g. $ valgrind ./bin/valgrindchk ==1134== Memcheck, a memory error detector ==1134== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==1134== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==1134== Command: ./bin/valgrindchk ==1134== a: 'abcdefghi' (1 alloc - 10 bytes) ==1134== ==1134== HEAP SUMMARY: ==1134== in use at exit: 0 bytes in 0 blocks ==1134== total heap usage: 2 allocs, 2 frees, 1,034 bytes allocated ==1134== ==1134== All heap blocks were freed -- no leaks are possible ==1134== ==1134== For counts of detected and suppressed errors, rerun with: -v ==1134== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) I'm not even using the --atavistic option... If someone can confirm, and let me know if a bug is warranted and I'll happily file one. If I recall correctly, this would be an upstream issue, I don't think Arch messes with the exclusions in any way. Let me know what you think. -- David C. Rankin, J.D.,P.E.

3 5

[arch-general] kernel panic, failed to execute /init error 2
by Aren Jared 06 Apr '18

06 Apr '18

Hi everyone, My system won't boot. The forum thread is: https://bbs.archlinux.org/viewtopic.php?id=236017 What I tried so far: - Reinstall boot partition - Reinstall mkinitcpio, systemd, kernels pacman log: https://paste.ubuntu.com/p/ypzDhhnc8P/ initramfs file is accessible: https://paste.ubuntu.com/p/grC4Qq2xxN/ Ideas?

1 0

[arch-general] libsecret dependency error
by Trey Sizemore 06 Apr '18

06 Apr '18

I've recently been getting the following errors for the libsecret package, and I'm not sure how to best resolve: Making package: lib32-libsecret 0.18.6-1 (Fri Apr 6 13:15:40 EDT 2018) ==> Checking runtime dependencies... ==> Missing dependencies: -> libsecret=0.18.6 Or this variation with pacman: error: failed to prepare transaction (could not satisfy dependencies) :: lib32-libsecret: installing libsecret (0.18.6-1) breaks dependency 'libsecret=0.18.5+14+g9980655' Any help is greatly appreciated! -- Cheers, Trey ---- In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time. --Edward P. Tryon Linux antergos 4.15.14-1-ARCH x86_64 14:10:50 up 22:17, 1 user, load average: 0.24, 0.34, 0.29

4 7

[arch-general] Why do we have scapy and scapy3k and which do we keep?
by David C. Rankin 06 Apr '18

06 Apr '18

Archdevs, Attempting a system update tonight, I was hit with: # pacman -Syu ... looking for conflicting packages... error: unresolvable package conflicts detected error: failed to prepare transaction (conflicting dependencies) :: scapy3k and scapy are in conflict They both seem to be similar, but which one do we keep? There was never a conflict before. I removed scapy3k, then curiously on one machine, it then proceeded to reinstall, along with scapy. I don't know how either were originally installed, I'd never heard of the package before the conflict popped up. Which should be keep? Or was this a packaging hiccup? -- David C. Rankin, J.D.,P.E.

2 1

[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