Your message dated Mon, 23 Nov 2020 11:48:26 +0000 with message-id <[email protected]> and subject line Bug#933865: fixed in android-platform-external-boringssl 10.0.0+r36-1 has caused the Debian Bug report #933865, regarding adb crashes on startup with SIGBUS (armhf) to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 933865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933865 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: adb Version: 1:8.1.0+r23-5 Severity: grave Justification: renders package unusable Dear Maintainer, the problem appears to be a regression between 9 (Stretch) and 10 (Buster) as adb worked fine under Stretch and doesn't work anymore under Buster. When I try to start 'adb' using 'adb devices -l' I get --- snip --- user@box:~> adb devices -l List of devices attached * daemon not running; starting now at tcp:5037 ADB server didn't ACK Full server startup log: /tmp/adb.1000.log Server had pid: 16703 --- adb starting (pid 16703) --- adb I 08-04 11:37:16 16703 16703 main.cpp:57] Android Debug Bridge version 1.0.39 adb I 08-04 11:37:16 16703 16703 main.cpp:57] Version 1:8.1.0+r23-5 adb I 08-04 11:37:16 16703 16703 main.cpp:57] Installed as /usr/lib/android-sdk/platform-tools/adb adb I 08-04 11:37:16 16703 16703 main.cpp:57] adb I 08-04 11:37:16 16703 16703 adb_auth_host.cpp:416] adb_auth_init... adb I 08-04 11:37:16 16703 16703 adb_auth_host.cpp:174] read_key_file '/home/till/.android/adbkey'... adb I 08-04 11:37:16 16703 16703 adb_auth_host.cpp:391] adb_auth_inotify_init... adb I 08-04 11:37:16 16703 16703 adb_auth_host.cpp:467] Calling send_auth_response * failed to start daemon error: cannot connect to daemon --- snap --- Note: /tmp/adb.1000.log shows exactly what's on stdout/stderr (seen above). The problem appears to be that adb gets killed by SIGBUS: --- snip --- user@box:~> strace -ffff -o adb adb devices -l [...] * failed to start daemon error: cannot connect to daemon user@box:~> grep killed adb.167* adb.16702:--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_KILLED, si_pid=16703, si_uid=1000, si_status=SIGBUS, si_utime=2, si_stime=8} --- adb.16703:+++ killed by SIGBUS +++ adb.16705:+++ killed by SIGBUS +++ adb.16706:+++ killed by SIGBUS +++ adb.16713:+++ killed by SIGBUS +++ adb.16715:+++ killed by SIGBUS +++ adb.16716:+++ killed by SIGBUS +++ user@box:~> cat adb.16703 set_robust_list(0xb6b25540, 12) = 0 close(3) = 0 execve("/usr/lib/android-sdk/platform-tools/adb", ["adb", "-L", "tcp:5037", "fork-server", "server", "--reply-fd", "4"], 0xbecde0d4 /* 30 vars */) = 0 brk(NULL) = 0xde9000 [...] bind(6, {sa_family=AF_INET, sin_port=htons(5037), sin_addr=inet_addr("127.0.0.1")}, 16) = 0 listen(6, 4) = 0 [...] futex(0xb6bd9860, FUTEX_WAKE_PRIVATE, 2147483647) = 0 getrandom("\xd6\x33\x59\xbc\xf7\x11\x33\x14\x38\x2d\x14\x48\x24\x14\xfb\xe0\x17\x40\xfd\x73\x07\x9a\xec\x6e\x89\x28\x25\xb6\x3e\x41\x04\x94", 32, 0) = 32 futex(0xb6bd9bec, FUTEX_WAKE_PRIVATE, 2147483647) = 0 getrandom("\xd2\x6f\x66\x87\x1c\x98\x22\x65\xd0\x70\x74\x8d\x8e\xd6\xe6\xa8\x83\xce\xc5\x63\x09\x25\x63\xe4\xbf\x97\x95\xfe\x6c\x3a\x9b\x89"..., 48, 0) = 48 --- SIGBUS {si_signo=SIGBUS, si_code=BUS_ADRALN, si_addr=0xb6b9dba1} --- +++ killed by SIGBUS +++ --- snap --- Forcibly installing these packages gives me a working adb: adb_7.0.0+r33-1_armhf.deb android-libadb_7.0.0+r33-1_armhf.deb android-libbase_7.0.0+r33-1_armhf.deb android-libcutils_7.0.0+r33-1_armhf.deb -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.19.0-5-armmp-lpae (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages adb depends on: ii android-libadb 1:8.1.0+r23-5 ii android-libbase 1:8.1.0+r23-5 ii libc6 2.28-10 ii libgcc1 1:8.3.0-6 ii libstdc++6 8.3.0-6 Versions of packages adb recommends: ii android-sdk-platform-tools-common 27.0.0+10 adb suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Source: android-platform-external-boringssl Source-Version: 10.0.0+r36-1 Done: Dhyey Patel <[email protected]> We believe that the bug you reported is fixed in the latest version of android-platform-external-boringssl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dhyey Patel <[email protected]> (supplier of updated android-platform-external-boringssl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Mon, 23 Nov 2020 12:14:17 +0100 Source: android-platform-external-boringssl Architecture: source Version: 10.0.0+r36-1 Distribution: unstable Urgency: medium Maintainer: Android Tools Maintainers <[email protected]> Changed-By: Dhyey Patel <[email protected]> Closes: 933865 Changes: android-platform-external-boringssl (10.0.0+r36-1) unstable; urgency=medium . * Team upload * New upstream version * Upstream (10.0.0+r36) (Closes: #933865) Checksums-Sha1: 3bd9ddc46f2ee410e2f7ab6446de5e2b72bcd12d 2110 android-platform-external-boringssl_10.0.0+r36-1.dsc 5f3cc773e5a264ddeb14a25702a0c5f4cbdc61cc 25852051 android-platform-external-boringssl_10.0.0+r36.orig.tar.gz c63e0d5b04dc7602a94683c1aa2e985f00b44a15 7876 android-platform-external-boringssl_10.0.0+r36-1.debian.tar.xz bbc6d6a99c94522d7552b4abb838a3ff4ab36409 5260 android-platform-external-boringssl_10.0.0+r36-1_source.buildinfo Checksums-Sha256: 36ec425a992384711c63a62db4f398e173a3560b796e4d6ad3e4812399816d1e 2110 android-platform-external-boringssl_10.0.0+r36-1.dsc 919a64a2794e7a5b0aca8cf9d41216655d9d6a9b2737e2e46a5a135195c1ec30 25852051 android-platform-external-boringssl_10.0.0+r36.orig.tar.gz 0e90b260e4bfe97879d7e5bd54e6f35ce38a27bbff27bf7afd1ba15d3011e089 7876 android-platform-external-boringssl_10.0.0+r36-1.debian.tar.xz eba396e7229b4f83e37470e27c73db377ac02c7165cbc571a097c99d0d622cb4 5260 android-platform-external-boringssl_10.0.0+r36-1_source.buildinfo Files: 6ab286eb6f95b939dc4b55862ad1f215 2110 libs optional android-platform-external-boringssl_10.0.0+r36-1.dsc 0d019d2951ee75de52ed3326a5824205 25852051 libs optional android-platform-external-boringssl_10.0.0+r36.orig.tar.gz bcf52dfdcde7c79246a9539dc9963b66 7876 libs optional android-platform-external-boringssl_10.0.0+r36-1.debian.tar.xz 3e78086b7da96f2d28e1383a9576c489 5260 libs optional android-platform-external-boringssl_10.0.0+r36-1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEElyI52+aGmfUmwGoFPhd4F7obm/oFAl+7nP0ACgkQPhd4F7ob m/qKOAf+KXXweuoovFbj63GyShjfiWurUnuuMWTANgyZIjVHopL0xDqUxNnw1Bdi nXxRAtRjx+qflmVzE6I5vqyLwYax8C4dSsZUKL6rbsfB9bLSHvWBNzJjSMQjwb3z HR4CZjzbpCOZYL7CdHqjCE9JGzZGFOJV48vwb4ptVCHkk87yYTstNc5j81j7QKL+ aKQUvyqqVyNGCiN2jwDxI6Ke0hoNwChN0wFEL/b78+1JWSyPnMI+WF6H8M3s+rs/ w5QahvEOQgIk4DiQw7jHL2q8iNyZLuIvWecFWxQedt2nhyad7An2Sx+Gul5xnTrI 8Opk/s3F68q76zXA0m9SLqume4smJw== =5t75 -----END PGP SIGNATURE-----
--- End Message ---
