aports issueshttps://gitlab.alpinelinux.org/alpine/aports/-/issues2021-11-24T23:41:07Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/5093apk doesn't deactivate packages from OpenRC when delEting2021-11-24T23:41:07ZSteffen Nurpmesoapk doesn't deactivate packages from OpenRC when delEtingI’ve had to manually remove a stale entry in runlevels/default.
I think it would be pretty cool if at least a warning would be shown.
P.S.: hey, apk is pretty nice.
*(from redmine: issue id 5093, created on 2016-02-09)*I’ve had to manually remove a stale entry in runlevels/default.
I think it would be pretty cool if at least a warning would be shown.
P.S.: hey, apk is pretty nice.
*(from redmine: issue id 5093, created on 2016-02-09)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/9964Add community/omxplayer aarch64 support2021-11-25T00:08:07ZMarnix RijnartAdd community/omxplayer aarch64 supportNow that Alpine supports aarch64 on Raspberry Pi, it would be nice to
have community/aarch64/omxplayer if that is possible.
*(from redmine: issue id 9964, created on 2019-02-07)*Now that Alpine supports aarch64 on Raspberry Pi, it would be nice to
have community/aarch64/omxplayer if that is possible.
*(from redmine: issue id 9964, created on 2019-02-07)*Timo TeräsTimo Teräshttps://gitlab.alpinelinux.org/alpine/aports/-/issues/7411ecryptfs-utils 111-r4 problem2021-11-25T06:11:02ZFelix Mecryptfs-utils 111-r4 problemHi,
I cannot migrate home directory with ecryptfs-migrate-home. I’m logged
as root and no one is logged with any other user name.
ecryptfs-migrate-home -u felix
INFO: Checking disk space, this may take a few moments. Please be
patient...Hi,
I cannot migrate home directory with ecryptfs-migrate-home. I’m logged
as root and no one is logged with any other user name.
ecryptfs-migrate-home -u felix
INFO: Checking disk space, this may take a few moments. Please be
patient.
INFO: Checking for open files in /home/felix
INFO: The following files are in use:
1 /bin/busybox /dev/console (deleted)
1 /bin/busybox /dev/console (deleted)
1 /bin/busybox /dev/console (deleted)
2428 /bin/busybox /dev/null
2428 /bin/busybox /dev/null
2428 /bin/busybox /dev/null
2428 /bin/busybox socket:\[2807\]
2453 /bin/busybox socket:\[1315\]
2453 /bin/busybox /dev/null
2453 /bin/busybox /dev/null
2453 /bin/busybox /var/log/messages
2505 /bin/busybox /dev/null
2505 /bin/busybox /var/log/acpid.log
2505 /bin/busybox /var/log/acpid.log
2505 /bin/busybox /dev/input/event0
2505 /bin/busybox /dev/input/event1
2505 /bin/busybox /dev/input/event2
2505 /bin/busybox /dev/input/event3
2505 /bin/busybox /dev/input/event4
2505 /bin/busybox /dev/input/event5
2505 /bin/busybox /dev/input/event6
2505 /bin/busybox /dev/input/event7
2505 /bin/busybox /dev/input/event8
2505 /bin/busybox /dev/input/event9
2554 /usr/sbin/chronyd socket:\[2840\]
2554 /usr/sbin/chronyd socket:\[2843\]
2554 /usr/sbin/chronyd socket:\[2844\]
2554 /usr/sbin/chronyd /dev/urandom
2554 /usr/sbin/chronyd socket:\[624\]
2581 /bin/busybox /dev/null
2581 /bin/busybox /dev/null
2581 /bin/busybox /dev/null
2581 /bin/busybox socket:\[2846\]
2609 /usr/sbin/sshd /dev/null
2609 /usr/sbin/sshd /dev/null
2609 /usr/sbin/sshd /dev/null
2609 /usr/sbin/sshd socket:\[3334\]
2609 /usr/sbin/sshd socket:\[3336\]
2613 /bin/busybox /dev/tty1
2613 /bin/busybox /dev/tty1
2613 /bin/busybox /dev/tty1
2614 /bin/busybox /dev/tty2
2614 /bin/busybox /dev/tty2
2614 /bin/busybox /dev/tty2
2617 /bin/busybox /dev/tty3
2617 /bin/busybox /dev/tty3
2617 /bin/busybox /dev/tty3
2620 /bin/busybox /dev/tty4
2620 /bin/busybox /dev/tty4
2620 /bin/busybox /dev/tty4
2623 /bin/busybox /dev/tty5
2623 /bin/busybox /dev/tty5
2623 /bin/busybox /dev/tty5
2626 /bin/busybox /dev/tty6
2626 /bin/busybox /dev/tty6
2626 /bin/busybox /dev/tty6
2629 /usr/sbin/sshd /dev/null
2629 /usr/sbin/sshd /dev/null
2629 /usr/sbin/sshd /dev/null
2629 /usr/sbin/sshd socket:\[2868\]
2629 /usr/sbin/sshd pipe:\[1397\]
2629 /usr/sbin/sshd pipe:\[1397\]
2629 /usr/sbin/sshd /dev/ptmx
2629 /usr/sbin/sshd /dev/ptmx
2629 /usr/sbin/sshd /dev/ptmx
2631 /bin/busybox /dev/pts/0
2631 /bin/busybox /dev/pts/0
2631 /bin/busybox /dev/pts/0
2631 /bin/busybox /dev/tty
2746 /bin/busybox /dev/pts/0
2746 /bin/busybox /dev/pts/0
2746 /bin/busybox /dev/pts/0
2746 /bin/busybox /usr/bin/ecryptfs-migrate-home
2768 /bin/busybox pipe:\[4111\]
2768 /bin/busybox /dev/pts/0
2768 /bin/busybox /dev/pts/0
ERROR: Cannot proceed.
*(from redmine: issue id 7411, created on 2017-06-10)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/10446busybox wget doesn't support HTTP CONNECT2021-11-25T06:23:29ZAndre tjebusybox wget doesn't support HTTP CONNECTWhen using the wget from busybox in combination with an Proxy (squid) it
won’t work.
Manual downloading the “full” wget solves the problem
*(from redmine: issue id 10446, created on 2019-05-13)*When using the wget from busybox in combination with an Proxy (squid) it
won’t work.
Manual downloading the “full” wget solves the problem
*(from redmine: issue id 10446, created on 2019-05-13)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/2085Apache2 mod_ldap crashes2021-11-29T02:02:41ZJeff Bilykjbilyk@gmail.comApache2 mod_ldap crashesDuring a build on current edge to try to resolve a crash in mod\_ldap, I
received the following output. I’m not sure how to track down TEXTRELs
though.
>>>ERROR: apache2\*: Found textrels:
TEXTREL
/home/jbilyk/aports/main/apache...During a build on current edge to try to resolve a crash in mod\_ldap, I
received the following output. I’m not sure how to track down TEXTRELs
though.
>>>ERROR: apache2\*: Found textrels:
TEXTREL
/home/jbilyk/aports/main/apache2/pkg/apache2-ldap/usr/lib/apache2/mod\_ldap.so
TEXTREL
/home/jbilyk/aports/main/apache2/pkg/apache2-ldap/usr/lib/apache2/mod\_authnz\_ldap.so
>>>ERROR: apache2\*: prepare\_subpackages failed
>>>ERROR: apache2: all failed
However, the root issue I’m trying to fix is an apache
server(apache2-2.4.4-r0) with mod\_ldap(apache2-ldap-2.4.4-r0) enabled
crashes as soon as it tries to authenticate with mod\_ldap with the
following error (domain name has been replaced in the following logs and
config with example.com):
\[Thu Jun 13 18:39:15.411076 2013\] \[authnz\_ldap:debug\] \[pid 21921\]
mod\_authnz\_ldap.c(501): \[client 10.14.59.106:48231\] AH01691:
auth\_ldap authenticate: using URL
ldaps://example.com/dc=example,dc=com?sAMAccountName?sub?(objectClass=\*)
\[Thu Jun 13 18:39:15.411244 2013\] \[authnz\_ldap:info\] \[pid 21921\]
\[client 10.14.59.106:48231\] AH01695: auth\_ldap authenticate: user
jbilyk@example.com authentication failed; URI /racktables/ \[LDAP: ldap
initialization failed\]\[Unknown (private extension) error\]
Apache auth config on the virtual directory is:
AuthType Basic
AuthName “AD Authentication”
AuthBasicProvider ldap
AuthLDAPAuthoritative Off
AuthLDAPURL
“ldap://example.com:389/OU=testOU,DC=example,DC=com?sAMAccountName?sub?(objectClass=\*)”
AuthLDAPBindDN “CN=user,OU=Users,OU=testOU,DC=example,DC=com”
AuthLDAPBindPassword passforuser
Require valid-user
*(from redmine: issue id 2085, created on 2013-06-13, closed on 2013-06-26)*
* Changesets:
* Revision 23b112fa0b4c683178bf2038c2719d4889575ee1 by Natanael Copa on 2013-06-18T15:50:26Z:
```
main/apache2: fix deps for apache2-ldap
it needs apr-util-ldap
ref #2085
```
* Revision a628280d18a5ecf904c8498961e973fb82946389 by Natanael Copa on 2013-06-19T08:38:20Z:
```
main/apache2: fix deps for apache2-ldap
it needs apr-util-ldap
ref #2085
(cherry picked from commit 23b112fa0b4c683178bf2038c2719d4889575ee1)
```
* Revision 9974c43a8e517a749c44bf06b17e5f5fd5665f0f by Natanael Copa on 2013-06-19T12:56:17Z:
```
main/apache2: fix deps for apache2-ldap
it needs apr-util-ldap
fixes #2085
(cherry picked from commit 23b112fa0b4c683178bf2038c2719d4889575ee1)
```
* Uploads:
* [httpd.conf](/uploads/711100acd93b3a158bfaa972f49665a2/httpd.conf)
* [ssl.conf](/uploads/d6ac2a79674c9d430c99e10d57e71cd8/ssl.conf)
* [php5-module.conf](/uploads/3c2e937138fe4903920a5d4110aa4479/php5-module.conf)
* [mod-auth-radius.conf](/uploads/bda0ee735244ae80728e7754a1bb0719/mod-auth-radius.conf)Alpine 2.5.5Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/2086Bacula-FD needs a link to libxz2021-11-29T02:02:41ZFlorian HeiglBacula-FD needs a link to libxzBacula has support for two compression algorithms since version 5.2.
The choice of algorithm is done server-side with a setting like this:
Include {
Options {
\#compression = GZIP1
compression = LZO }
… stuff …
}
So the age...Bacula has support for two compression algorithms since version 5.2.
The choice of algorithm is done server-side with a setting like this:
Include {
Options {
\#compression = GZIP1
compression = LZO }
… stuff …
}
So the agent (if of 5.2+ version) is just told “how” and “if” to
compress and if it doesn’t the link to the specifc compression algorythm
it’ll just turn off compression.
As a result, you get bigger and possibly slower backups.
The bacula-fd package would need to depend on some of these:
:~\# apk search xz
xz-dev-5.0.4-r1
xz-doc-5.0.4-r1
xz-libs-5.0.4-r1
xz-5.0.4-r1
I suspect dev and libs are enough.
ldd
checking sub-depends for ‘/usr/lib/libbacfind-5.2.12.so’
checking sub-depends for ‘/usr/lib/libbacpy-5.2.12.so’
checking sub-depends for ‘/usr/lib/libbaccfg-5.2.12.so’
checking sub-depends for ‘/usr/lib/libbac-5.2.12.so’
checking sub-depends for ‘/lib/libz.so.1’
checking sub-depends for ‘/lib/libpthread.so.0.9.32’
checking sub-depends for ‘/lib/libc.so.0.9.32’
checking sub-depends for ‘/lib/libdl.so.0.9.32’
checking sub-depends for ‘/lib/libssl.so.1.0.0’
checking sub-depends for ‘/lib/libcrypto.so.1.0.0’
checking sub-depends for ‘/usr/lib/libstdc<span
class="underline"></span>.so.6’
checking sub-depends for ‘/lib/libm.so.0.9.32’
checking sub-depends for ‘/usr/lib/libgcc\_s.so.1’
checking sub-depends for ‘/lib/libubacktrace.so.0.9.32’
libbacfind-5.2.12.so =>/usr/lib/libbacfind-5.2.12.so (0x00000000)
libbacpy-5.2.12.so =>/usr/lib/libbacpy-5.2.12.so (0x00000000)
libbaccfg-5.2.12.so =>/usr/lib/libbaccfg-5.2.12.so (0x00000000)
libbac-5.2.12.so =>/usr/lib/libbac-5.2.12.so (0x00000000)
libz.so.1 =>/lib/libz.so.1 (0x00000000)
libpthread.so.0.9.32 =>/lib/libpthread.so.0.9.32 (0x00000000)
libc.so.0.9.32 =>/lib/libc.so.0.9.32 (0x00000000)
libdl.so.0.9.32 =>/lib/libdl.so.0.9.32 (0x00000000)
libssl.so.1.0.0 =>/lib/libssl.so.1.0.0 (0x00000000)
libcrypto.so.1.0.0 =>/lib/libcrypto.so.1.0.0 (0x00000000)
libstdc<span class="underline"></span>.so.6 =>/usr/lib/libstdc<span
class="underline"></span>.so.6 (0x00000000)
libm.so.0.9.32 =>/lib/libm.so.0.9.32 (0x00000000)
libgcc\_s.so.1 =>/usr/lib/libgcc\_s.so.1 (0x00000000)
libubacktrace.so.0.9.32 =>/lib/libubacktrace.so.0.9.32
(0x00000000)
ld64-uClibc.so.0.9.32 =>ld64-uClibc.so.0.9.32 (0x00000000)
ld64-uClibc.so.0.9.32 =>ld64-uClibc.so.0.9.32 (0x00000000)
*(from redmine: issue id 2086, created on 2013-06-13, closed on 2013-07-03)*
* Changesets:
* Revision 8ffcd2e1271f9baf1831f8568df75d977e173073 by Carlo Landmeter on 2013-06-17T13:42:26Z:
```
main/bacula: add lzo support
fixes #2086
```
* Revision af657d90a1ff1118c8be76209ad3baeb078971b0 by Carlo Landmeter on 2013-07-03T08:26:03Z:
```
main/bacula: add lzo support
fixes #2086
(cherry picked from commit 8ffcd2e1271f9baf1831f8568df75d977e173073)
```Alpine 2.6.3Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12277Gogs wiki cannot be created/update2021-12-02T00:29:00Zsybix sybixGogs wiki cannot be created/updateHi,
When creating a wiki in a projet, with gogs installed from repository,
it fail with an error 500
There is this message in log :
2017/01/13 07:25:18 \[…routers/repo/wiki.go:253 EditWikiPost()\] \[E\]
EditWikiPage: UpdateLocalWiki: ...Hi,
When creating a wiki in a projet, with gogs installed from repository,
it fail with an error 500
There is this message in log :
2017/01/13 07:25:18 \[…routers/repo/wiki.go:253 EditWikiPost()\] \[E\]
EditWikiPage: UpdateLocalWiki: git clone : mkdir data: permission denied
Gogs try to create data directory for tmp data (at least) in it’s
running directory.
gogs binary should be launch in it’s home directory.
I attach the modification i made in the openrc script for gogs.
*(from redmine: issue id 6682, created on 2017-01-13)*
* Uploads:
* [gogs.initd-wiki.patch](/uploads/1f88790e75c0009bc01c87065c843e37/gogs.initd-wiki.patch)https://gitlab.alpinelinux.org/alpine/aports/-/issues/8131qemu user executables do not work for fedora/debian images2021-12-02T00:59:54Zalgitbotqemu user executables do not work for fedora/debian imagesProblem can be demonstrated best by using docker
Get qemu:
docker -v $(pwd):/ws debian:9 bash -c “apt-get update && apt-get -y
install qemu-user-static && cp /usr/bin/qemu-ppc64le-static
/ws/qemu-debian
docker -v $(pwd):/ws alpine sh...Problem can be demonstrated best by using docker
Get qemu:
docker -v $(pwd):/ws debian:9 bash -c “apt-get update && apt-get -y
install qemu-user-static && cp /usr/bin/qemu-ppc64le-static
/ws/qemu-debian
docker -v $(pwd):/ws alpine sh -c ”apk update && apk add qemu-ppc64le
&&/usr/bin/qemu-ppc64le /ws/qemu-alpine
docker run —rm -v $(pwd)/qemu-alpine:/qemu -it ppc64le/fedora:26 /qemu
/usr/libexec/system-python /usr/bin/yum update
Error: Failed to synchronize cache for repo ‘updates’
However debians qemu works:
docker run —rm -v $(pwd)/qemu-debian:/qemu -it ppc64le/fedora:26 /qemu
/usr/libexec/system-python /usr/bin/yum update
Either a patch from debian is missing , or maybe some compile time
dependency triggers an issue
Thanks!
See https://github.com/linuxkit/linuxkit/issues/2710 for downstream
usage
*(from redmine: issue id 8131, created on 2017-11-11)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/1864mktemp incorrectly handles template-parameter2021-12-02T04:58:57ZAlexander Hirschmktemp incorrectly handles template-parameterWhat happens:
$ mktemp -u blah.tmp_XXXXXX
blah.T97AeK
$ mktemp -u /home/me/blah.tmp_XXXXXX
/home512h4b
Expected:
$ mktemp -u blah.tmp_XXXXXX
blah.tmp_T97AeK
$ mktemp -u /home/me/blah.tmp_XXXXXX
/home...What happens:
$ mktemp -u blah.tmp_XXXXXX
blah.T97AeK
$ mktemp -u /home/me/blah.tmp_XXXXXX
/home512h4b
Expected:
$ mktemp -u blah.tmp_XXXXXX
blah.tmp_T97AeK
$ mktemp -u /home/me/blah.tmp_XXXXXX
/home/me/blah.tmp_512h4b
*(from redmine: issue id 1864, created on 2013-05-15, closed on 2013-12-09)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/10402litespeed: Move to community?2021-12-26T20:24:07ZChun-Shemg Lilitespeed: Move to community?Hi all, I use the Alpine Linux inside Docker container, but it seems
that I cannot install the litespeed package.
Instruction
===========
- Using the following Dockerfile
<!-- -->
<code class="text">
FROM alpine:3.7
R...Hi all, I use the Alpine Linux inside Docker container, but it seems
that I cannot install the litespeed package.
Instruction
===========
- Using the following Dockerfile
<!-- -->
<code class="text">
FROM alpine:3.7
RUN apk update
RUN apk add --no-cache litespeed
</code>
- Finally. I got this message:
<!-- -->
<code class="text">
Step 3/3 : RUN apk add --no-cache litespeed
---> Running in d49c2a1063fe
fetch http://dl-cdn.alpinelinux.org/alpine/v3.7/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.7/community/x86_64/APKINDEX.tar.gz
ERROR: unsatisfiable constraints:
litespeed (missing):
required by: world[litespeed]
The command '/bin/sh -c apk add --no-cache litespeed' returned a non-zero code: 1
</code>
I also check the all available mirror lists in Alpine Linux and it seems
that they don’t include the litespeed package.
Please include this package in mirror lists.
Thanks.
*(from redmine: issue id 10402, created on 2019-05-03)*Valery KartelValery Kartelhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/1868CVE-2013-2053 Openswan: remote buffer overflow in atodn()2022-01-06T22:26:22ZPeter KotcauerCVE-2013-2053 Openswan: remote buffer overflow in atodn()A buffer overflow flaw was found in Openswan. If Opportunistic
Encryption
were enabled (“oe=yes” in “/etc/ipsec.conf”) and an RSA key configured,
an
attacker able to cause a system to perform a DNS lookup for an
attacker-
controlle...A buffer overflow flaw was found in Openswan. If Opportunistic
Encryption
were enabled (“oe=yes” in “/etc/ipsec.conf”) and an RSA key configured,
an
attacker able to cause a system to perform a DNS lookup for an
attacker-
controlled domain containing malicious records (such as by sending an
email that triggers a DKIM or SPF DNS record lookup) could cause
Openswan’s pluto IKE daemon to crash or, potentially, execute
arbitrary
code with root privileges. With “oe=yes” but no RSA key configured,
the
issue can only be triggered by attackers on the local network who can
control the reverse DNS entry of the target system. Opportunistic
Encryption is disabled by default. (CVE-2013-2053)
*(from redmine: issue id 1868, created on 2013-05-15, closed on 2013-05-20)*
* Relations:
* child #1895https://gitlab.alpinelinux.org/alpine/aports/-/issues/6989lttng-ust-dev package contains lttng-ust-dev.so with bad symbol references2022-01-07T17:29:32ZJan Vorliceklttng-ust-dev package contains lttng-ust-dev.so with bad symbol referencesThe lttng-ust-dev.so in the package (tested for x86\_64 on Alpine 3.4.6)
contains references to symbols that don’t exist on Alpine:
bash-4.3\# ldd
/usr/bin/../lib/gcc/x86\_64-alpine-linux-musl/5.3.0/../../../liblttng-ust.so
ldd (0x7fa...The lttng-ust-dev.so in the package (tested for x86\_64 on Alpine 3.4.6)
contains references to symbols that don’t exist on Alpine:
bash-4.3\# ldd
/usr/bin/../lib/gcc/x86\_64-alpine-linux-musl/5.3.0/../../../liblttng-ust.so
ldd (0x7fad89147000)
liblttng-ust-tracepoint.so.0 =>/usr/lib/liblttng-ust-tracepoint.so.0
(0x7fad88cc6000)
liburcu-bp.so.4 =>/usr/lib/liburcu-bp.so.4 (0x7fad88abf000)
liburcu-cds.so.4 =>/usr/lib/liburcu-cds.so.4 (0x7fad888b8000)
libc.musl-x86\_64.so.1 =>ldd (0x7fad89147000)
liburcu-common.so.4 =>/usr/lib/liburcu-common.so.4
(0x7fad886b4000)
Error relocating
/usr/bin/../lib/gcc/x86\_64-alpine-linux-musl/5.3.0/../../../liblttng-ust.so:
pthread\_setname\_np: symbol not found
Error relocating
/usr/bin/../lib/gcc/x86\_64-alpine-linux-musl/5.3.0/../../../liblttng-ust.so:
sched\_getcpu: symbol not found
*(from redmine: issue id 6989, created on 2017-03-08)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/5615accumulated atop crontab process2022-01-08T18:22:59ZV Krishnaccumulated atop crontab processNoticing accumulated atop crontab process,
Don’t know if its busybox issue or atop.
Pls find attached image
Tested on AlpineLinux 3.3.x
Thanks
*(from redmine: issue id 5615, created on 2016-05-21)*
* Uploads:
* ![atop-crontab-...Noticing accumulated atop crontab process,
Don’t know if its busybox issue or atop.
Pls find attached image
Tested on AlpineLinux 3.3.x
Thanks
*(from redmine: issue id 5615, created on 2016-05-21)*
* Uploads:
* ![atop-crontab-process1](/uploads/6002b2e83ed590e1fceae6961cabed3b/atop-crontab-process1.png)https://gitlab.alpinelinux.org/alpine/aports/-/issues/10257chromium-browser: seccomp-bpf failure in syscall 03242022-01-13T05:39:25ZTomas Pollakchromium-browser: seccomp-bpf failure in syscall 0324Running chromium-browser results in a fatal crash. Running Alpine
3.10\_alpha20190408.
$ chromium-browser
[3298:3333:0415/093257.685805:ERROR:bus.cc(396)] Failed to connect to the bus: Could not parse server address: Unknown ad...Running chromium-browser results in a fatal crash. Running Alpine
3.10\_alpha20190408.
$ chromium-browser
[3298:3333:0415/093257.685805:ERROR:bus.cc(396)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[3328:3328:0415/093257.731855:ERROR:sandbox_linux.cc(364)] InitializeSandbox() called with multiple threads in process gpu-process.
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0324
Received signal 11 SEGV_MAPERR 000000010144
r8: 00007ffd33fc5395 r9: ffffffffffffffff r10: 00007ffd33fc5382 r11: 00007ffd33fc536f
r12: 00007ffd33fc53f4 r13: 0000000000000001 r14: 00007f93f0c37889 r15: 000055a075299a80
di: 0000000000000001 si: 00007ffd33fc5270 bp: 00007ffd33fc5440 bx: 0000000000000144
dx: 0000000000000000 ax: 0000000000010144 cx: 000000000000006d sp: 00007ffd33fc53f0
ip: 000055a06f2f97e1 efl: 0000000000010206 cgf: 002b000000000033 erf: 0000000000000006
trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000010144
[end of stack trace]
Calling _exit(1). Core file will not be generated.
The problem disappears when launching with the
**—disable-seccomp-filter-sandbox** flag:
$ chromium-browser --disable-seccomp-filter-sandbox
*(from redmine: issue id 10257, created on 2019-04-15, closed on 2019-06-19)*Sören TempelSören Tempelhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/108acf-openvpn(v0.4.1) displays all files as they would be config-files in the c...2022-01-19T01:35:34ZMika Havelaacf-openvpn(v0.4.1) displays all files as they would be config-files in the config-tabWhen looking at the config-tab for acf-openvpn, you will notice that all
files (“.keep\_net-misc\_openvpn-0”, certificate-files, etc) will get
presented in the list of config-files. This causes some confusion.
One suggestion is to filt...When looking at the config-tab for acf-openvpn, you will notice that all
files (“.keep\_net-misc\_openvpn-0”, certificate-files, etc) will get
presented in the list of config-files. This causes some confusion.
One suggestion is to filter out \*.conf files.
*(from redmine: issue id 108, created on 2009-07-30, closed on 2009-08-19)*Mika HavelaMika Havelahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/591setup-vs-guest progressbar looks strange2022-01-30T04:00:35ZNatanael Copasetup-vs-guest progressbar looks strangeIt looks something like:
...
Enter template file (or empty for generate a new):
Generating template...-[
]- 0% -[ ...It looks something like:
...
Enter template file (or empty for generate a new):
Generating template...-[
]- 0% -[
]- 1% -[#
]- 3% -[##
]- 4% -[###
]- 5% -[#######
]- 12% -[#######
]- 12% -[########
]- 13% -[###################
]- 30% -[###################
]- 30% -[####################
]- 31% -[####################
]- 32% -[#####################
...etc
This comes from the apk-tools progressbar improvement. We need simply
add a newline in setup-vs-guest.
*(from redmine: issue id 591, created on 2011-04-27, closed on 2011-04-30)*Alpine 2.2.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/534Please compile extra FreeTDM modules2022-01-30T04:00:35ZNatanael CopaPlease compile extra FreeTDM modulesI deleted bug \#532 by mistake so I create a new one.
We would like to use freeswitch with our digium Wildcard T407P. We need
the PRI and ISDN modules. Would it be possible to compile the following
modules:
ftmod\_zt
ftmod\_libpri ...I deleted bug \#532 by mistake so I create a new one.
We would like to use freeswitch with our digium Wildcard T407P. We need
the PRI and ISDN modules. Would it be possible to compile the following
modules:
ftmod\_zt
ftmod\_libpri
ftmod\_isdn
Comment from Timo:
Looks like this is not really supported in freeswitch-1.0.6. I’m not
sure if it’s just not being built, or if it’s intentionally disabled due
to missing stuff. There’s been a lot of activity on FS git tree for tdm
stuff since 1.0.6 release. They say 1.0.7 is imminent (since Dec 2010).
So I’m wondering if we wait for 1.0.7, check the git snapshots or try to
make 1.0.6 build the tdm modules.
*(from redmine: issue id 534, created on 2011-02-22, closed on 2011-03-24)*
* Changesets:
* Revision c5416cf20701bb5896f80aafdc0f1f9a0d607bf2 on 2011-02-22T14:36:36Z:
```
main/freeswitch: upgrade to 1.0.7
ref #532
ref #534
```
* Revision 280383464cc4c4ab689fe341d6339452d1cba95b on 2011-03-04T15:22:02Z:
```
main/freeswitch: upgrade to 1.0.7
ref #532
ref #534
(cherry picked from commit c5416cf20701bb5896f80aafdc0f1f9a0d607bf2)
```Alpine 2.2.0Timo TeräsTimo Teräshttps://gitlab.alpinelinux.org/alpine/aports/-/issues/5278Enable CONFIG_USB_GADGET in kernel config2022-02-13T17:11:42ZScrumpy JackEnable CONFIG_USB_GADGET in kernel confighttps://www.kernel.org/doc/htmldocs/gadget/
It’s handy for connecting embedded devices or microbaord to your USB
port, thethering, TCP/IP over USB etc.
*(from redmine: issue id 5278, created on 2016-03-15)*https://www.kernel.org/doc/htmldocs/gadget/
It’s handy for connecting embedded devices or microbaord to your USB
port, thethering, TCP/IP over USB etc.
*(from redmine: issue id 5278, created on 2016-03-15)*3.12.0https://gitlab.alpinelinux.org/alpine/aports/-/issues/8726openrc docker init does not use system proxy2022-02-20T22:04:28ZSimon Alpineopenrc docker init does not use system proxydockerd started by /etc/init.d/docker does not honor the proxy
configured by setup-proxy.
1. repro:
1. setup-proxy http://192.0.2.1:8080
2. rc-service docker restart
<!-- -->
1. docker pull alpine:latest
Error response from ...dockerd started by /etc/init.d/docker does not honor the proxy
configured by setup-proxy.
1. repro:
1. setup-proxy http://192.0.2.1:8080
2. rc-service docker restart
<!-- -->
1. docker pull alpine:latest
Error response from daemon: Get https://registry-1.docker.io/v2/:
dial tcp 34.200.90.16:443: connect: network is unreachable
2. fix:
load proxy environment variables in /etc/init.d/docker
—- /etc/init.d/docker.orig
<span class="underline"></span>+ /etc/init.d/docker
@@ –32,5 +32,9 @@
\# in the kernel. We recommend using cgroups to do container-local
accounting.
ulimit -p unlimited
\+ if [-e /etc/profile.d/proxy.sh](-e_/etc/profile.d/proxy.sh); then
+ source /etc/profile.d/proxy.sh
+ fi
+
return 0
}
*(from redmine: issue id 8726, created on 2018-03-25)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/9001lxc-attach works different as expected2022-02-21T22:09:07Zalgitbotlxc-attach works different as expectedWhen using LXC on an Alpine Linux host, `lxc-attach` works different
than in other distributions.
So when you attach to a container with `lxc-attach`, it seems that you
only get a chrooted shell, so you can’t see any other processes run...When using LXC on an Alpine Linux host, `lxc-attach` works different
than in other distributions.
So when you attach to a container with `lxc-attach`, it seems that you
only get a chrooted shell, so you can’t see any other processes running
in the container.
On other distributions like Debian or Ubuntu, you can see running
processes when connecting with `lxc-attach` and e.g. run `top`. I’m not
quite sure, but I think these distros cause `lxc-attach` to attach to
the container namespaces by default.
*(from redmine: issue id 9001, created on 2018-06-14)*Natanael CopaNatanael Copa