aports issueshttps://gitlab.alpinelinux.org/alpine/aports/-/issues2021-10-16T08:02:01Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/2535sysctl.conf changes2021-10-16T08:02:01ZChris Spillanesysctl.conf changesIt seems by default many security features are already enabled, a few
not enabled (checked on alpine 2.7.0) that would be a good idea to turn
on are:
\- TOCTOU prevention
\- rfc1337
\- magic-sysreq
I’ve already documented these on th...It seems by default many security features are already enabled, a few
not enabled (checked on alpine 2.7.0) that would be a good idea to turn
on are:
\- TOCTOU prevention
\- rfc1337
\- magic-sysreq
I’ve already documented these on the wiki page
(http://wiki.alpinelinux.org/wiki/Sysctl.conf)
Maybe we could enable these by default in new installs?
Also, it would potentially be a good idea to enable the IPv6 privacy
extensions via sysctl.conf, for those that do use IPv6.
*(from redmine: issue id 2535, created on 2013-12-31, closed on 2015-12-09)*
* Changesets:
* Revision 26212b3bdd85d0b4ed7835b789519507f3d54a56 by Natanael Copa on 2014-06-10T14:05:19Z:
```
main/libvirt: security upgrade to 1.0.5.9 fixes various CVEs
CVE-2013-6458
CVE-2014-1447
CVE-2013-6456
CVE-2014-0179
fixes #2535
fixes #2953
```Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/8769Packet-Request: RTPEngine2021-10-02T21:37:21ZJan-Hendrik DörnerPacket-Request: RTPEngineRTPEngine seems to be a modern / less resource consuming replacement for
RTPProxy to be used with kamailio.
https://github.com/sipwise/rtpengine
*(from redmine: issue id 8769, created on 2018-04-05)*RTPEngine seems to be a modern / less resource consuming replacement for
RTPProxy to be used with kamailio.
https://github.com/sipwise/rtpengine
*(from redmine: issue id 8769, created on 2018-04-05)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/9391[Feature Request]: Please integrate cockroachDB into Alpine Linux mainstream2021-10-02T21:30:16ZGiovanni Minniti[Feature Request]: Please integrate cockroachDB into Alpine Linux mainstreamHi Jakub,
looking around I see you are the postgres maintainer for Alpine Linux.
CockroachDB is a distributed, high available Database using the postgres
driver.
I would like to see cockroachDB for aarch64 under Alpine Linux.
Is the...Hi Jakub,
looking around I see you are the postgres maintainer for Alpine Linux.
CockroachDB is a distributed, high available Database using the postgres
driver.
I would like to see cockroachDB for aarch64 under Alpine Linux.
Is there a chance to integrate it.
Web: https://www.cockroachlabs.com/
Doc: https://www.cockroachlabs.com/docs/stable/
GitHub: https://github.com/cockroachdb/cockroach
Thanks for all the hard work on Alpine Linux
*(from redmine: issue id 9391, created on 2018-09-05)*Jakub JirutkaJakub Jirutkahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/8609mkintifs: nlplug-findfs mount zfs filesystems on import2021-09-28T13:23:19ZAlexander Zubkovmkintifs: nlplug-findfs mount zfs filesystems on importHello. As I see nlplug-findgs calls zpool import without any additional
parameters during its work:
https://github.com/alpinelinux/mkinitfs/blob/master/nlplug-findfs.c\#L508
In that case imported pool’s filesystems are mounted by defa...Hello. As I see nlplug-findgs calls zpool import without any additional
parameters during its work:
https://github.com/alpinelinux/mkinitfs/blob/master/nlplug-findfs.c\#L508
In that case imported pool’s filesystems are mounted by default if they
have mounpoint properties.
When later initramfs pivots into new root, they are left there mounted
and can not be used because zfs thinks they are already mounted and
cannot unmount them at the same time.
I think it would be better to do zpool import with “-N” option to not
mount filesystems by default and then mount specified root filesystem
somehow.
Also, I think providing some means to specify “-f” option would be nice
too in cases when pool that was imported to other system needs to be
imported.
*(from redmine: issue id 8609, created on 2018-03-05)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/10199Illegal instruction (SIGILL) in libaprutil-1.so.02021-09-27T16:13:16ZthealikIllegal instruction (SIGILL) in libaprutil-1.so.0When running Apache with SSL enabled, httpd processes frequently crash
with the following message:
[Mon Apr 01 13:21:49.170358 2019] [core:notice] [pid 1:tid 140156675435368] AH00051: child pid 332 exit signal Illegal instruction (4...When running Apache with SSL enabled, httpd processes frequently crash
with the following message:
[Mon Apr 01 13:21:49.170358 2019] [core:notice] [pid 1:tid 140156675435368] AH00051: child pid 332 exit signal Illegal instruction (4), possible coredump in /usr/local/apache2
No issues when the exact same image ran in the same configuration on a
VM without AES-NI.
Coredump:
warning: .dynamic section for "/usr/lib/libssl.so.1.1" is not at the expected address (wrong library or version mismatch?)
Core was generated by `httpd -DFOREGROUND'.
Program terminated with signal SIGILL, Illegal instruction.
#0 0x00007f93c3da265b in apr_brigade_flatten () from /usr/lib/libaprutil-1.so.0
[Current thread is 1 (LWP 210)]
(gdb) bt
#0 0x00007f93c3da265b in apr_brigade_flatten () from /usr/lib/libaprutil-1.so.0
#1 0x00007f93c38ef8f3 in get_line () from /usr/local/apache2/modules/mod_http2.so
#2 0x00007f93c38f0690 in h2_from_h1_parse_response () from /usr/local/apache2/modules/mod_http2.so
#3 0x00007f93c391cffb in h2_filter_parse_h1 () from /usr/local/apache2/modules/mod_http2.so
#4 0x000055a3e961729c in ap_pass_brigade ()
#5 0x000055a3e96607bc in ap_process_request_after_handler ()
#6 0x000055a3e9661047 in ap_process_async_request ()
#7 0x000055a3e9661080 in ap_process_request ()
#8 0x00007f93c391e794 in h2_task_process_request () from /usr/local/apache2/modules/mod_http2.so
#9 0x00007f93c391f0ea in h2_task_process_conn () from /usr/local/apache2/modules/mod_http2.so
#10 0x000055a3e964ebef in ap_run_process_connection ()
#11 0x00007f93c391df63 in h2_task_do () from /usr/local/apache2/modules/mod_http2.so
#12 0x00007f93c39248eb in slot_run () from /usr/local/apache2/modules/mod_http2.so
#13 0x00007f93c3e714d8 in ?? () from /lib/ld-musl-x86_64.so.1
#14 0x0000000000000000 in ?? ()
CPU: Intel® Celeron® CPU J3455 @ 1.50GHz
CPU Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
pdpe1gb rdtscp lm constant\_tsc art arch\_perfmon pebs bts rep\_good
nopl xtopology tsc\_reliable nonstop\_tsc cpuid aperfmperf
tsc\_known\_freq pni pclmulqdq dtes64 ds\_cpl vmx est tm2 ssse3 sdbg
cx16 xtpr pdcm sse4\_1 sse4\_2 x2apic movbe popcnt tsc\_deadline\_timer
aes xsave rdrand lahf\_lm 3dnowprefetch cpuid\_fault cat\_l2 ibrs ibpb
stibp tpr\_shadow vnmi flexpriority ept vpid fsgsbase tsc\_adjust smep
erms mpx rdt\_a rdseed smap clflushopt intel\_pt sha\_ni xsaveopt xsavec
xgetbv1 xsaves dtherm ida arat pln pts arch\_capabilities
I first opened this issue against Alpine Docker image, please see it
here for more details:
https://github.com/docker-library/httpd/issues/128
*(from redmine: issue id 10199, created on 2019-04-04)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/9609mount not recognizing exFAT partitions2021-09-27T16:10:41ZWayne DePrincemount not recognizing exFAT partitionsroot is not able to mount exFAT partitions with `/bin/mount`
# lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sdc
...root is not able to mount exFAT partitions with `/bin/mount`
# lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sdc
├─sdc1 vfat ESP 3451-84E1
├─sdc2
└─sdc3 exfat Gialla 4C78-12E3@
#mount /dev/sdc3 /media/usb/
mount: /media/usb: unknown filesystem type 'exfat'.
# mount -t exfat /dev/sdc3 /media/usb/
mount: /media/usb: unknown filesystem type 'exfat'.
even though exFAT utils are installed
# apk list --installed | grep -i exfat
fuse-exfat-1.3.0-r0 x86_64 {fuse-exfat} (GPL-2.0-or-later) [installed]
fuse-exfat-utils-1.3.0-r0 x86_64 {fuse-exfat} (GPL-2.0-or-later) [installed]
however mounting will work on exFAT partitions if
`/usr/sbin/mount.exfat` or `/usr/sbin/mount.exfat-fuse` is run directly
# mount.exfat /dev/sdc3 /media/usb/
FUSE exfat 1.3.0
thus with plain `/bin/mount` not working for exFAT, non-root users
cannot mount exFAT partitions via udiskctl, udevil, etc. that use that
command.
thanks.
PS: running Alpine edge:
# uname -a
Linux 4.14.78-0-vanilla #1-Alpine SMP Tue Oct 23 11:20:00 UTC 2018 x86_64 Linux
# apk update
fetch http://mirror.clarkson.edu/alpine/edge/main/x86_64/APKINDEX.tar.gz
fetch http://mirror.clarkson.edu/alpine/edge/community/x86_64/APKINDEX.tar.gz
fetch http://mirror.clarkson.edu/alpine/edge/testing/x86_64/APKINDEX.tar.gz
v3.8.0-2746-g74834905da [http://mirror.clarkson.edu/alpine/edge/main]
v3.8.0-2749-g179e6e1221 [http://mirror.clarkson.edu/alpine/edge/community]
v3.8.0-2747-g2acae47fcc [http://mirror.clarkson.edu/alpine/edge/testing]
OK: 13128 distinct packages available
*(from redmine: issue id 9609, created on 2018-11-01)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/9624ghostscript-fonts package is not a dependency of imagemagick package2021-09-27T16:08:22ZSamuel BOHNghostscript-fonts package is not a dependency of imagemagick packageI had to install manually ghostscript-fonts to make imagemagick work.
I suggest to add ghostscript-fonts as a dependency of imagemagick
*(from redmine: issue id 9624, created on 2018-11-06)*I had to install manually ghostscript-fonts to make imagemagick work.
I suggest to add ghostscript-fonts as a dependency of imagemagick
*(from redmine: issue id 9624, created on 2018-11-06)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/8873intel ipw2200 firmare packaged2021-09-26T16:56:40Zalgitbotintel ipw2200 firmare packagedplease package firmware for intel ipw2200 wireless card
non-free could be a good place
Debian puts it under /lib/firmware/ipw2200-\[bss/ibss\].fw
http://http.debian.net/debian/pool/non-free/f/firmware-nonfree/firmware-nonfree\_2016113...please package firmware for intel ipw2200 wireless card
non-free could be a good place
Debian puts it under /lib/firmware/ipw2200-\[bss/ibss\].fw
http://http.debian.net/debian/pool/non-free/f/firmware-nonfree/firmware-nonfree\_20161130-3.debian.tar.xz
*(from redmine: issue id 8873, created on 2018-05-10)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/10063DNS intermittent delays of 5s2021-09-25T19:31:35ZJuan Carlos AminDNS intermittent delays of 5sThis bug described a few different types of slow DNS queries,
in my use case the slow DNS requests occurred on alpine:3.7/3.8, due to
the timed out for additional AAAA query along with A query by default.
currently no need to query A...This bug described a few different types of slow DNS queries,
in my use case the slow DNS requests occurred on alpine:3.7/3.8, due to
the timed out for additional AAAA query along with A query by default.
currently no need to query AAAA records by default, so the solution is
removing AAAA resolution from the implements
(musl/src/network/lookup\_name.c, function ‘name\_from\_dns’), and the
code fix worked for me:
//musl/src/network/lookup\_name.c, function ‘name\_from\_dns’
static const struct { int af; int rr; } afrr\[2\] = {
{ .af = AF\_INET6, .rr = RR\_A },
{ .af = AF\_INET, .rr = RR\_AAAA },
};
for (i=0; i<2; i<span class="underline"></span>) {
if (family != afrr\[i\].af) {
qlens\[nq\] = \_\_res\_mkquery(0, name, 1, afrr\[i\].rr,
0, 0, 0, qbuf\[nq\], sizeof \*qbuf);
if (qlens\[nq\] == –1)
return EAI\_NONAME;
nq<span class="underline"></span>;
}
//hack: if set the AF\_UNSPEC family, just return ipv4 result
if (family == AF\_UNSPEC) break;
}
*(from redmine: issue id 10063, created on 2019-03-05)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/9046Mariadb 10.2.15-r02021-09-25T19:25:53ZalgitbotMariadb 10.2.15-r0Mariadb now is using native Linux fallocate for creating the ibdata
file. It fails in alpine edge and alpine 3.8 running as containers.
2018-06-29 19:11:12 140013615233928 \[ERROR\] InnoDB: preallocating
12582912 bytes for file ./ibdata...Mariadb now is using native Linux fallocate for creating the ibdata
file. It fails in alpine edge and alpine 3.8 running as containers.
2018-06-29 19:11:12 140013615233928 \[ERROR\] InnoDB: preallocating
12582912 bytes for file ./ibdata1 failed with error 95
2018-06-29 19:11:12 140013615233928 \[ERROR\] InnoDB: Could not set the
file size of ‘./ibdata1’. Probably out of disk space
2018-06-29 19:11:12 140013615233928 \[ERROR\] InnoDB: Database creation
was aborted with error Generic error. You may need to delete the ibdata1
file before trying to start up again.
2018-06-29 19:11:13 140013615233928 \[ERROR\] Plugin ‘InnoDB’ init
function returned error.
2018-06-29 19:11:13 140013615233928 \[ERROR\] Plugin ‘InnoDB’
registration as a STORAGE ENGINE failed.
2018-06-29 19:11:13 140013615233928 \[ERROR\] Unknown/unsupported
storage engine: InnoDB
2018-06-29 19:11:13 140013615233928 \[ERROR\] Aborting
*(from redmine: issue id 9046, created on 2018-06-29)*3.8.5Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/9744hostname variable configuration in /etc/conf.d/hostname made moot by /etc/hos...2021-09-09T05:52:43ZGeorgi Sminhostname variable configuration in /etc/conf.d/hostname made moot by /etc/hostname being created by alpine-baselayout at bootExpected behavior of /etc/init.d/hostname script is to check if
/etc/hostname exists, else set hostname to the variable configured in
/etc/conf.d/hostname
However, /etc/hostname will always exist prior to this check since it is
installe...Expected behavior of /etc/init.d/hostname script is to check if
/etc/hostname exists, else set hostname to the variable configured in
/etc/conf.d/hostname
However, /etc/hostname will always exist prior to this check since it is
installed by alpine-baselayout at boot (set to ‘localhost’). The init.d
script will always return True when checking for the file, which results
in the conf.d variable never being used.
Related to: https://bugs.alpinelinux.org/issues/9737
*(from redmine: issue id 9744, created on 2018-12-10)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/10159shorewall : error messages at startup2021-09-05T00:37:47ZPaul Gauretshorewall : error messages at startupStarting shorewall4 or shorewall6 gives the following error message.
# /etc/init.d/shorewall start
* Starting shorewall ...
sh: recursive: unknown operand
find: invalid number '-type'
sh: recursive: unknown operand
...Starting shorewall4 or shorewall6 gives the following error message.
# /etc/init.d/shorewall start
* Starting shorewall ...
sh: recursive: unknown operand
find: invalid number '-type'
sh: recursive: unknown operand
find: invalid number '-type'
The issue seems to be with the comparisons done in
/usr/share/shorewall/lib.cli-std at lines 408 and 415.
*(from redmine: issue id 10159, created on 2019-03-26)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/11242apk refuses to install seamonkey along with firefox-esr2021-09-02T13:50:44Zalgitbotapk refuses to install seamonkey along with firefox-esrIt seems that apk refuses to install packages that have libraries with
same name even if they are going to install different paths.
```
ERROR: unsatisfiable constraints:
firefox-esr-52.6.0-r1:
conflicts: seamonkey-2.48-r1[so:liblg...It seems that apk refuses to install packages that have libraries with
same name even if they are going to install different paths.
```
ERROR: unsatisfiable constraints:
firefox-esr-52.6.0-r1:
conflicts: seamonkey-2.48-r1[so:liblgpllibs.so=0] seamonkey-2.48-r1[so:libxul.so=0]
satisfies: world[firefox-esr]
seamonkey-2.48-r1:
conflicts: firefox-esr-52.6.0-r1[so:liblgpllibs.so=0] firefox-esr-52.6.0-r1[so:libxul.so=0]
satisfies: world[seamonkey]
```
*(from redmine: issue id 8648, created on 2018-03-15)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/10543scripts/mkimage.sh doesn't build uboot profile2021-08-19T18:31:31ZMilan P. Stanićscripts/mkimage.sh doesn't build uboot profileruning
./mkimage.sh —arch armv7 —hostkeys —profile uboot —outdir out —workdir
workdir —repository http://dl-cdn.alpinelinux.org/alpine/edge/main
gives next:
fetch
http://dl-cdn.alpinelinux.org/alpine/edge/main/armv7/APKINDEX.tar.gz ...runing
./mkimage.sh —arch armv7 —hostkeys —profile uboot —outdir out —workdir
workdir —repository http://dl-cdn.alpinelinux.org/alpine/edge/main
gives next:
fetch
http://dl-cdn.alpinelinux.org/alpine/edge/main/armv7/APKINDEX.tar.gz
v3.10.0\_rc1-574-ged8584b7cb
\[http://dl-cdn.alpinelinux.org/alpine/edge/main\]
OK: 5632 distinct packages available
>>>mkimage-armv7: Building uboot
>>>mkimage-armv7: —>kernel armv7 vanilla
70780944a96e84dd29767d38f44330605b4b98ec linux-vanilla linux-firmware
ERROR: unsatisfiable constraints:
alpine-base (missing):
required by: world\[alpine-base\]
linux-firmware (missing):
required by: world\[linux-firmware\]
linux-vanilla (missing):
required by: world\[linux-vanilla\]
it doesn’t make tarball
*(from redmine: issue id 10543, created on 2019-06-07)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/10237Add support for IPv6 only installations2021-08-09T20:44:01ZNico SchotteliusAdd support for IPv6 only installationsHello,
there are more and more IPv6 only environments that don’t facilitate
DHCP (v6) anymore. Clients configure themselves after receiving “Router
Advertisements”, including DNS information. (Alpine) Linux correctly
handles the IP addr...Hello,
there are more and more IPv6 only environments that don’t facilitate
DHCP (v6) anymore. Clients configure themselves after receiving “Router
Advertisements”, including DNS information. (Alpine) Linux correctly
handles the IP address assignment (i.e. doing nothing, the kernel takes
care of it), however there is no support for DNS information on the
current installation medium and thus packages cannot be downloaded.
The main problem that needs to be solved is to add DNS information from
router advertisements into /etc/resolv.conf.
There are multiple ways to solve this:
- install rdnssd
- use a dhpcv6 client that allows failing dhcpv6 request, but still
reads router advertisement information
As more and more networks become IPv6 only (and I in particular deal
with many of these on a daily basis), I would appreciate having IPv6 DNS
support in the installation medium.
Please let me know if you need further information or access to a test
network.
*(from redmine: issue id 10237, created on 2019-04-14)*3.14.1Kevin DaudtKevin Daudthttps://gitlab.alpinelinux.org/alpine/aports/-/issues/9976wpa_supplicant: enable support for IBSS RSN (WPA2 in Ad-Hoc mode)2021-08-08T21:14:19ZMarnix Rijnartwpa_supplicant: enable support for IBSS RSN (WPA2 in Ad-Hoc mode)Please add support for IBSS RSN aka WPA2 in Ad-Hoc mode.
Should be as easy as adding CONFIG\_IBSS\_RSN=y to
wpa\_supplicant/config
Sidenote: it does seem that this file is out of date compared to
upstream https://w1.fi/cgit/hostap/plai...Please add support for IBSS RSN aka WPA2 in Ad-Hoc mode.
Should be as easy as adding CONFIG\_IBSS\_RSN=y to
wpa\_supplicant/config
Sidenote: it does seem that this file is out of date compared to
upstream https://w1.fi/cgit/hostap/plain/wpa\_supplicant/defconfig,
which has some more options with comments at the end, including the
requested option.
*(from redmine: issue id 9976, created on 2019-02-10)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/9048libgomp segfault - example usage java z32021-08-08T12:45:13Zalgitbotlibgomp segfault - example usage java z3Hi All,
I encountered a segfault when running the java interface for z3 and
figured out the alpine libgomp.so is to blame. I was able to get it
working by disabling openMP and GMP usage in my build and wanted to know
what y’all think.
...Hi All,
I encountered a segfault when running the java interface for z3 and
figured out the alpine libgomp.so is to blame. I was able to get it
working by disabling openMP and GMP usage in my build and wanted to know
what y’all think.
The original ticket I put to z3 is here:
https://github.com/Z3Prover/z3/issues/1702
Steps to reproduce:
Use the following dockerfile to make a container:
<code>
FROM alpine:latest
MAINTAINER Matthew Ahrens
ENV ES_JAVA_OPTS="-Xms512m -Xmx512m"
RUN apk update
RUN apk add musl
RUN apk add gcc
RUN apk add g++
RUN apk add git
RUN apk add libstdc++
RUN apk add openjdk8 && apk add openjdk8-jre
RUN apk add tar
RUN apk add wget
RUN apk add build-base
RUN apk add cmake
RUN apk add python3
RUN ln -s /usr/bin/python3 /usr/bin/python
RUN apk add paxctl
RUN paxctl -c /usr/lib/jvm/default-jvm/jre/bin/java && paxctl -m /usr/lib/jvm/default-jvm/jre/bin/java && paxctl -c /usr/lib/jvm/default-jvm/bin/java && paxctl -m /usr/lib/jvm/default-jvm/bin/java
RUN apk upgrade
RUN wget https://github.com/Z3Prover/z3/releases/download/z3-4.7.1/z3-4.7.1.tar.gz
RUN tar -xzf z3-4.7.1.tar.gz
RUN export JAVA_HOME=/usr/lib/jvm/default-jvm && export PATH=$JAVA_HOME/bin:$JAVA_HOME/jre/bin:$PATH && cd z3rel && mkdir build && cd build && cmake -DUSE_OPENMP=TRUE -DUSE_LIB_GMP=TRUE -DBUILD_JAVA_BINDINGS=TRUE ../ && make && make install && cp com.microsoft.z3.jar /usr/lib
</code>
Then in the image you can build the following java program:
<code class="java">
import com.microsoft.z3.Context;
public class Test{
public static void main(String[] args){
Context c = new Context();
}
}
</code>
build and run with:
`javac -cp "/usr/lib:com.microsoft.z3.jar:." Test.java`
`java -cp "/usr/lib:com.microsoft.z3.jar:." Test`
And you should get the same error I get:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x000066614dc1d14d, pid=13471, tid=0x00006661d0049ae8
#
# JRE version: OpenJDK Runtime Environment (8.0_171-b11) (build 1.8.0_171-b11)
# Java VM: OpenJDK 64-Bit Server VM (25.171-b11 mixed mode linux-amd64 compressed oops)
# Derivative: IcedTea 3.8.0
# Distribution: Custom build (Wed Jun 13 18:00:32 UTC 2018)
# Problematic frame:
# C [libgomp.so.1+0x814d] omp_set_nested+0xf
#
# Core dump written. Default location: /root/z3-z3-4.6.0/build/core or core.13471
#
# An error report file with more information is saved as:
# /root/z3-z3-4.6.0/build/hs_err_pid13471.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# http://icedtea.classpath.org/bugzilla
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Segmentation fault (core dumped)
*(from redmine: issue id 9048, created on 2018-06-29)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/8025WLAN does not connect after reboot2021-08-08T12:21:04ZalgitbotWLAN does not connect after rebootI’m dual-booting Alpine 3.6.2 (standard) and Ubuntu 16.04. I set up the
system by following the instructions at
https://wiki.alpinelinux.org/wiki/Installing\_Alpine\_on\_HDD\_dualbooting
(which seem to be wrong since vmlinuz and initramf...I’m dual-booting Alpine 3.6.2 (standard) and Ubuntu 16.04. I set up the
system by following the instructions at
https://wiki.alpinelinux.org/wiki/Installing\_Alpine\_on\_HDD\_dualbooting
(which seem to be wrong since vmlinuz and initramfs both have the
‘-hardened’ suffix rather than ‘grsec’).
What I’m seeing is that after rebooting I always have to re-configure
wlan0 through setup-interfaces. I didn’t do any sort of manual
networking configurations during the install process.
I’m assigning this an Immediate priority since it’s an obvious usability
bug that users shouldn’t have to deal with, much less in their very
first install of the system.
*(from redmine: issue id 8025, created on 2017-10-21)*
* Relations:
* relates #7986https://gitlab.alpinelinux.org/alpine/aports/-/issues/8861cloud-init doesn't load cloud-config from attached wirtual CDROM2021-08-03T08:31:29Zalgitbotcloud-init doesn't load cloud-config from attached wirtual CDROMI have a virtual CDROM to load my cloud-init config to an Alpine 3.7.0
where I installed the cloud-init apk previously, but it doesn’t seem to
get detected or mounted correctly
*(from redmine: issue id 8861, created on 2018-05-04)*
* ...I have a virtual CDROM to load my cloud-init config to an Alpine 3.7.0
where I installed the cloud-init apk previously, but it doesn’t seem to
get detected or mounted correctly
*(from redmine: issue id 8861, created on 2018-05-04)*
* Uploads:
* [alpine.log](/uploads/586dbe3ff417c90a03cd9a4c91b575e5/alpine.log) Full log descriing the problem3.7.4Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/10440vagrant halt on the Official Vagrant box alpine/alpine64 dont work: bash: lin...2021-08-01T00:06:15ZMax Pealvagrant halt on the Official Vagrant box alpine/alpine64 dont work: bash: line 4: shutdown: command not foundThe official Vagrant box alpine/alpine64 /
https://app.vagrantup.com/alpine
vagrant halt gives an error:
————————————————————————-
$ vagrant halt
==>default: Attempting graceful shutdown of VM…
The following SSH command responde...The official Vagrant box alpine/alpine64 /
https://app.vagrantup.com/alpine
vagrant halt gives an error:
————————————————————————-
$ vagrant halt
==>default: Attempting graceful shutdown of VM…
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
shutdown -h now
Stdout from the command:
Stderr from the command:
bash: line 4: shutdown: command not found
------------------------------------------------------------------------
also with no link and no user information (see also
https://bugs.alpinelinux.org/issues/8902 )
its no way to conact the maintainer.
*(from redmine: issue id 10440, created on 2019-05-09)*