aports issueshttps://gitlab.alpinelinux.org/alpine/aports/-/issues2024-03-29T08:10:29Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15921community/pdal: 112 - pdal_info_test (Failed)2024-03-29T08:10:29ZNatanael Copacommunity/pdal: 112 - pdal_info_test (Failed)<!--
This is the issue template for reporting an issue with a specific package. You
can select a different issue template from the dropdown above. Also, feel free
to use the "No template" option in case no template applies to your issue....<!--
This is the issue template for reporting an issue with a specific package. You
can select a different issue template from the dropdown above. Also, feel free
to use the "No template" option in case no template applies to your issue.
Also note that this repository is intended for reporting issues with packages.
For other components, separate issue trackers exist:
* Installer issues: https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues
* Infrastructure issues: https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues
* Initramfs issues: https://gitlab.alpinelinux.org/alpine/mkinitfs/-/issues
-->
## Package Information
* Package name: comunity/pdal
* Package version: 2.7.0
* Alpine version: 3.20.0_alpha20240315
* Alpine architecture: x86_64
*
## Summary
build fails during check:
```
[ RUN ] Info.stac
/home/ncopa/aports/community/pdal/src/PDAL-2.7.0-src/test/unit/apps/InfoTest.cpp:62: Failure
Expected: (output.find(validation)) != (std::string::npos), actual: 18446744073709551615 vs 18446744073709551615
Found: '{
"file_size": 3742038,
"filename": "/home/ncopa/aports/community/pdal/src/PDAL-2.7.0-src/test/data/las/autzen_trim.las",
"now": "2024-03-27T12:01:59+0100",
"pdal_version": "2.7.0 (git-version: 4f8157)",
"reader": "readers.las",
"stac":
{
"assets":
{
"data":
{
"href": "/home/ncopa/aports/community/pdal/src/PDAL-2.7.0-src/test/data/las/autzen_trim.las",
"title": "Pointcloud data"
}
},
"bbox":
[
-123.0734622,
44.04990616,
406.26,
-123.068918,
44.05155049,
520.51
],
...
{
"name": "Latitude of 2nd standard parallel",
"value": 45.5,
"unit": "degree",
"id": {
"authority": "EPSG",
"code": 8824
}
},
{
"name": "Easting at false origin",
"value": 1312335.95800525,
"unit": {
"type": "LinearUnit",
"name": "foot",
"conversion_factor": 0.3048
},
"id": {
"authority": "EPSG",
"code": 8826
}
},
{
"name": "Northing at false origin",
"value": 0,
"unit": {
"type": "LinearUnit",
"name": "foot",
"conversion_factor": 0.3048
},
"id": {
"authority": "EPSG",
"code": 8827
}
}
]
},
"coordinate_system": {
"subtype": "Cartesian",
"axis": [
{
"name": "Easting",
"abbreviation": "",
"direction": "east",
"unit": {
"type": "LinearUnit",
"name": "foot",
"conversion_factor": 0.3048,
"id": {
"authority": "EPSG",
"code": 9002
}
}
},
{
"name": "Northing",
"abbreviation": "",
"direction": "north",
"unit": {
"type": "LinearUnit",
"name": "foot",
"conversion_factor": 0.3048,
"id": {
"authority": "EPSG",
"code": 9002
}
}
}
]
}
},
"proj:wkt2": "PROJCS[\"NAD_1983_HARN_Lambert_Conformal_Conic\",GEOGCS[\"NAD83(HARN)\",DATUM[\"NAD83_High_Accuracy_Reference_Network\",SPHEROID[\"GRS 1980\",6378137,29
8.257222101004,AUTHORITY[\"EPSG\",\"7019\"]],AUTHORITY[\"EPSG\",\"6152\"]],PRIMEM[\"Greenwich\",0],UNIT[\"degree\",0.0174532925199433,AUTHORITY[\"EPSG\",\"9122\"]]],PROJECT
ION[\"Lambert_Conformal_Conic_2SP\"],PARAMETER[\"latitude_of_origin\",41.75],PARAMETER[\"central_meridian\",-120.5],PARAMETER[\"standard_parallel_1\",43],PARAMETER[\"standa
rd_parallel_2\",45.5],PARAMETER[\"false_easting\",1312335.95800525],PARAMETER[\"false_northing\",0],UNIT[\"foot\",0.3048,AUTHORITY[\"EPSG\",\"9002\"]],AXIS[\"Easting\",EAST
],AXIS[\"Northing\",NORTH]]"
},
"stac_extensions":
[
"https://stac-extensions.github.io/pointcloud/v1.0.0/schema.json",
"https://stac-extensions.github.io/projection/v1.1.0/schema.json"
],
"stac_version": "1.0.0",
"type": "Feature"
}
}
'
expected: '
"properties":
{
"datetime": "2015-09-10T00:00:00Z",
"pc:count": 110000,
"pc:encoding": ".las",
'
[ FAILED ] Info.stac (426 ms)
[----------] 6 tests from Info (2735 ms total)
[----------] Global test environment tear-down
[==========] 6 tests from 1 test suite ran. (2739 ms total)
[ PASSED ] 5 tests.
[ FAILED ] 1 test, listed below:
[ FAILED ] Info.stac
1 FAILED TEST
118/122 Test #37: pdal_io_ept_addon_writer_test ................ Passed 6.03 sec
119/122 Test #92: pdal_filters_pmf_test ........................ Passed 5.58 sec
120/122 Test #38: pdal_io_copc_reader_test ..................... Passed 7.63 sec
121/122 Test #65: pdal_filters_colorization_test ............... Passed 7.15 sec
122/122 Test #118: translate_test ............................... Passed 5.93 sec
99% tests passed, 1 tests failed out of 122
Total Test time (real) = 8.31 sec
The following tests FAILED:
112 - pdal_info_test (Failed)
Errors while running CTest
>>> ERROR: pdal: check failed
```
## Steps to reproduce
`abuild -r`3.20.0Bart RibbersBart Ribbershttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15929community/pavucontrol: desktop entry refers to missing icon2024-03-28T23:34:55ZHugo Barreracommunity/pavucontrol: desktop entry refers to missing icon## Package Information
* Package name: pavucontrol-5.0-r4
* Alpine version: 3.20.0_alpha20240315
* Alpine architecture: x86_64
## Summary
This package installs a desktop entry which refers to an icon:
```console
> grep Icon /usr/shar...## Package Information
* Package name: pavucontrol-5.0-r4
* Alpine version: 3.20.0_alpha20240315
* Alpine architecture: x86_64
## Summary
This package installs a desktop entry which refers to an icon:
```console
> grep Icon /usr/share/applications/pavucontrol.desktop
Icon=multimedia-volume-control
````
But the icon is not installed as part of this package, so launchers (e.g.: fuzzel) will show an empty icon.
pavucontrol's icon should be installed into /app/share/icons/hicolor/scalable/apps/multimedia-volume-control.svg
## Steps to reproduce
Use any launcher (e.g.: `fuzzel`) and find `pavucontrol`'s desktop entry.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15917community/gnome-extensions-app: GNOME 46 extensions app won't launch2024-03-28T22:48:21ZAngelo Verlain Shemacommunity/gnome-extensions-app: GNOME 46 extensions app won't launch<!--
This is the issue template for reporting an issue with a specific package. You
can select a different issue template from the dropdown above. Also, feel free
to use the "No template" option in case no template applies to your issue....<!--
This is the issue template for reporting an issue with a specific package. You
can select a different issue template from the dropdown above. Also, feel free
to use the "No template" option in case no template applies to your issue.
Also note that this repository is intended for reporting issues with packages.
For other components, separate issue trackers exist:
* Installer issues: https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues
* Infrastructure issues: https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues
* Initramfs issues: https://gitlab.alpinelinux.org/alpine/mkinitfs/-/issues
-->
## Package Information
* Package name: *gnome-extensions-app*
* Package version: *46.0-r0*
* Alpine version: *3.20.0_alpha20240315*
* Alpine architecture: *x86_64*
## Summary
The app won't launch.
Trace:
```
~$ gnome-extensions-app
(gnome-extensions-app:9555): Gjs-CRITICAL **: 20:59:56.442: JS ERROR: Error: No property version on Gjs_Application
_init@resource:///org/gnome/Extensions/js/main.js:17:15
Application@resource:///org/gnome/Extensions/js/main.js:14:1
main@resource:///org/gnome/Extensions/js/main.js:61:11
@file:///usr/share/gnome-shell/org.gnome.Extensions:10:7
(gnome-extensions-app:9555): Gjs-CRITICAL **: 20:59:56.442: Module file:///usr/share/gnome-shell/org.gnome.Extensions threw an exception
```
## Steps to reproduce
*If applicable, please provide instructions to reproduce the issue.*Pablo Correa GomezPablo Correa Gomezhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15924virt-manager support for pytest 82024-03-28T07:48:06ZLeonardo Arenavirt-manager support for pytest 8virt-manager does not pass tests with pytest 8.x
This has been reported upstream: https://github.com/virt-manager/virt-manager/issues/648virt-manager does not pass tests with pytest 8.x
This has been reported upstream: https://github.com/virt-manager/virt-manager/issues/6483.20.0Leonardo ArenaLeonardo Arenahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15897Edge kde5 -» 6 sddm breeze segv2024-03-26T16:14:50ZBjörn StrömbergEdge kde5 -» 6 sddm breeze segvUpdated a older edge kde rootfs and it unfortunately does not want to start sddm after.
It segv sddm-helper according to /var/log/sddm.log err code 11
And /var/lib/sddm/.local/sddm.log
Says it can't create child in another thread
@Pur...Updated a older edge kde rootfs and it unfortunately does not want to start sddm after.
It segv sddm-helper according to /var/log/sddm.log err code 11
And /var/lib/sddm/.local/sddm.log
Says it can't create child in another thread
@PureTryOut anything you have encountered?Bart RibbersBart Ribbershttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15915community/flatpak: `[7] Couldn't connect to server`2024-03-26T12:55:10ZVehementHamcommunity/flatpak: `[7] Couldn't connect to server`<!--
This is the issue template for reporting an issue with a specific package. You
can select a different issue template from the dropdown above. Also, feel free
to use the "No template" option in case no template applies to your issue....<!--
This is the issue template for reporting an issue with a specific package. You
can select a different issue template from the dropdown above. Also, feel free
to use the "No template" option in case no template applies to your issue.
Also note that this repository is intended for reporting issues with packages.
For other components, separate issue trackers exist:
* Installer issues: https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues
* Infrastructure issues: https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues
* Initramfs issues: https://gitlab.alpinelinux.org/alpine/mkinitfs/-/issues
-->
## Package Information
* Package name: `flatpak`
* Package version: `flatpak-1.14.5-r2 `
* Alpine version: `3.20.0_alpha20240315`
* Alpine architecture: `x86_64`
## Summary
Flatpak fails to connect to flathub.
### Installing a package
```
localhost:~$ doas flatpak install com.play0ad.zeroad
Looking for matches…
Remotes found with refs similar to ‘com.play0ad.zeroad’:
1) ‘flathub’ (system)
2) ‘fluthub’ (system)
Which do you want to use (0 to abort)? [0-2]: 2
Required runtime for com.play0ad.zeroad/x86_64/stable (runtime/org.freedesktop.Platform/x86_64/22.08) found in remotes:
1) fluthub
2) flathub
Which do you want to install (0 to abort)? [0-2]: 2
com.play0ad.zeroad permissions:
ipc network pulseaudio x11 dri shm
ID Branch Op Remote Download
1. [✗] com.play0ad.zeroad.Locale stable i fluthub 1.0 kB / 1.0 kB
2. [✗] org.freedesktop.Platform.GL.default 22.08 i flathub 1.0 kB / 148.3 MB
3. [✗] org.freedesktop.Platform.GL.default 22.08-extra i flathub 1.0 kB / 148.3 MB
4. [✗] org.freedesktop.Platform.Locale 22.08 i flathub 1.0 kB / 333.7 MB
5. [✗] org.freedesktop.Platform.openh264 2.2.0 i flathub 1.0 kB / 944.3 kB
6. [✗] org.freedesktop.Platform 22.08 i flathub 1.0 kB / 214.5 MB
7. [ ] com.play0ad.zeroad stable i fluthub < 1.8 GB
Warning: While pulling runtime/com.play0ad.zeroad.Locale/x86_64/stable from remote fluthub: While fetching https://dl.flathub.org/repo/config: [7] Couldn't connect to server
Warning: While pulling runtime/org.freedesktop.Platform.GL.default/x86_64/22.08 from remote flathub: While fetching https://dl.flathub.org/repo/config: [7] Couldn't connect to server
Warning: While pulling runtime/org.freedesktop.Platform.GL.default/x86_64/22.08-extra from remote flathub: While fetching https://dl.flathub.org/repo/config: [7] Couldn't connect to server
Warning: While pulling runtime/org.freedesktop.Platform.Locale/x86_64/22.08 from remote flathub: While fetching https://dl.flathub.org/repo/config: [7] Couldn't connect to server
Warning: While pulling runtime/org.freedesktop.Platform.openh264/x86_64/2.2.0 from remote flathub: While fetching https://dl.flathub.org/repo/config: [7] Couldn't connect to server
Error: While pulling runtime/org.freedesktop.Platform/x86_64/22.08 from remote flathub: While fetching https://dl.flathub.org/repo/config: [7] Couldn't connect to server
error: Failed to install org.freedesktop.Platform: While pulling runtime/org.freedesktop.Platform/x86_64/22.08 from remote flathub: While fetching https://dl.flathub.org/repo/config: [7] Couldn't connect to server
```
# Searching
```
localhost:~$ flatpak search 0ad
No matches found
localhost:~$
```
### Updating the appstream
```
localhost:~$ flatpak update --appstream
Updating appstream data for remote flathub
Error updating: While pulling appstream2/x86_64 from remote flathub: While fetching https://dl.flathub.org/repo/config: [7] Couldn't connect to server
Updating appstream data for remote fluthub
Error updating: While pulling appstream2/x86_64 from remote fluthub: While fetching https://dl.flathub.org/repo/config: [7] Couldn't connect to server
```
### Aditional information
Network is functional. This issue does not occur on non-Alpine Linux machines at my location. `curl` is able to download the files that flatpak is not.
## Steps to reproduce
Install and attempt it use flatpak on Alpine Linux. Maybe.A. KlitzingA. Klitzinghttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15914Kdenlive Fails to Start2024-03-26T12:54:34ZVehementHamKdenlive Fails to Start<!--
This is the issue template for reporting an issue with a specific package. You
can select a different issue template from the dropdown above. Also, feel free
to use the "No template" option in case no template applies to your issue....<!--
This is the issue template for reporting an issue with a specific package. You
can select a different issue template from the dropdown above. Also, feel free
to use the "No template" option in case no template applies to your issue.
Also note that this repository is intended for reporting issues with packages.
For other components, separate issue trackers exist:
* Installer issues: https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues
* Infrastructure issues: https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues
* Initramfs issues: https://gitlab.alpinelinux.org/alpine/mkinitfs/-/issues
-->
## Package Information
* Package name: `kdenlive`
* Package version: `kdenlive-24.02.1-r0`
* Alpine version: `3.20.0_alpha20240315`
* Alpine architecture: `x86_64`
## Summary
Upon start, kdenlive returns this error:
```
Could not detect package type, probably default? App dir is "/usr/bin"
= = = =
GOT Deleted file: "/home/<user>/.config/kdenliverc"
QPaintDevice: Cannot destroy paint device that is being painted
```
## Steps to reproduce
Install and attempt to run Kdenlive.Bart RibbersBart Ribbershttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15918main/powertop: v2.15-r4 does not report power estimates2024-03-26T12:53:30Zedepamain/powertop: v2.15-r4 does not report power estimates## Package Information
* Package name: powertop
* Package version: powertop-2.15-r4
* Alpine version: 3.19.1
* Alpine architecture: x86_64
## Summary
Power estimates are not shown in "powertop --calibrate" output, nor in "powertop" o...## Package Information
* Package name: powertop
* Package version: powertop-2.15-r4
* Alpine version: 3.19.1
* Alpine architecture: x86_64
## Summary
Power estimates are not shown in "powertop --calibrate" output, nor in "powertop" output. "/var/cache/powertop/saved_parameters.powertop" is not created.
## Steps to reproduce
On a fresh installation of Alpine Standard 3.19.1, install powertop using "apk update", followed by "apk add powertop".
Run the command "powertop --calibrate".
No power estimates column shown in output.
No "/var/cache/powertop/saved_parameters.powertop" produced.
Downgrading to 2.11-rc1 resolves the issue, and "/var/cache/powertop/saved_parameters.powertop" is produced too.Steven GuikalSteven Guikalhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15869community/helix Grammars/syntax hightlighting not working (23.10-r2)2024-03-25T19:10:53ZRdbocommunity/helix Grammars/syntax hightlighting not working (23.10-r2)Similarly to #14303, syntax hightlighting doesn't seem to be working on `helix-23.10-r2`.
To reproduce:
- Install helix on edge `sudo apk add helix`
- Fetch grammars `hx -g fetch`
- Build grammars `hx -g build`
- Run `hx --health`
The la...Similarly to #14303, syntax hightlighting doesn't seem to be working on `helix-23.10-r2`.
To reproduce:
- Install helix on edge `sudo apk add helix`
- Fetch grammars `hx -g fetch`
- Build grammars `hx -g build`
- Run `hx --health`
The last command will show you that none of the grammars are getting picked up.
Also, using the `tree-sitter-*` packages works, but is not ideal, since there are many missing languages from there.
I manage to fix this problem by downgrading helix to `23.10-r0`, so something must have happened between these two versions that caused this.
My downgrade process that fixed the issue:
```
echo 'http://dl-cdn.alpinelinux.org/alpine/v3.19/community' > /tmp/REPOS
sudo apk del helix
sudo apk add --no-cache --repositories-file=/tmp/REPOS helix
hx -g fetch
hx -g build
```Jakub JirutkaJakub Jirutkahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15878Freezing on "Loading hardware drivers"2024-03-25T14:18:05ZGianmichele TrottaFreezing on "Loading hardware drivers"Hi everyone. I have a big problem installing the latest version of Linux Alpine.
When I start the installation it freeze almost immediately while loading hardware drivers.
I'm trying to install it on an Asus Eee PC 1101HA.
I hope someon...Hi everyone. I have a big problem installing the latest version of Linux Alpine.
When I start the installation it freeze almost immediately while loading hardware drivers.
I'm trying to install it on an Asus Eee PC 1101HA.
I hope someone can help me. Thanks everyone in advance.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15881font-dejavu not properly installed2024-03-24T23:55:28Zcristian_cifont-dejavu not properly installed## Package Information
* Package name: *font-dejavu*
* Package version: *2.37-r5*
* Alpine version: *3.20.0_alpha20231219*
* Alpine architecture: *x86*
## Summary
I was suggested to issue a report against font-dejavu because it's not ...## Package Information
* Package name: *font-dejavu*
* Package version: *2.37-r5*
* Alpine version: *3.20.0_alpha20231219*
* Alpine architecture: *x86*
## Summary
I was suggested to issue a report against font-dejavu because it's not properly installed on Xorg. If I run `xlsfonts` (built from [sources](https://gitlab.freedesktop.org/xorg/app/xlsfonts)) command, it doesn't list dejavu font. As a result, applications that rely on it do not find the font in the right path, for some reason. I've tried to compare package() functions in archilinux's [PKGBUILD](https://gitlab.archlinux.org/archlinux/packaging/packages/ttf-dejavu/-/blob/main/PKGBUILD) and alpine's [APKBUILD](https://git.alpinelinux.org/aports/tree/main/font-dejavu/APKBUILD).
When I remove and reinstall the package, I get:
```
alpine-test:~$ doas apk del font-dejavu
(1/1) Purging font-dejavu (2.37-r5)
Executing fontconfig-2.15.0-r0.trigger
Executing mkfontscale-1.2.2-r5.trigger
OK: 314 MiB in 958 packages
alpine-test:~$
```
```
alpine-test:~$ doas apk add font-dejavu
(1/1) Installing font-dejavu (2.37-r5)
Executing fontconfig-2.15.0-r0.trigger
Executing mkfontscale-1.2.2-r5.trigger
OK: 324 MiB in 959 packages
alpine-test:~$
```
So, I've compared also [fontconfig](https://git.alpinelinux.org/aports/tree/main/fontconfig/fontconfig.trigger) and [mkfontscale](https://git.alpinelinux.org/aports/tree/main/mkfontscale/mkfontscale.trigger) triggers with the respective archlinux's hooks.
Still, I can't figure out why the path is wrong and is not listed by xlsfonts, after font-dejavu installation.
While at it, I noticed that font-dejavu's APKBUILD doesn'install the [LICENSE](https://github.com/dejavu-fonts/dejavu-fonts/blob/master/LICENSE) file into `/usr/share/licenses`, unlike archlinux's PKGBUILD (likely that's not required by alpine)Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15892busybox: not possible to permanently remove klogd user2024-03-19T21:47:08ZNatanael Copabusybox: not possible to permanently remove klogd userCommit b870258c717220a2ea3f8803e54578ee80820979 (main/busybox: run klogd as klogd user and not root) introduced a user named `klogd` that is created from busybox install script. A consequence of this is that users who don't want this use...Commit b870258c717220a2ea3f8803e54578ee80820979 (main/busybox: run klogd as klogd user and not root) introduced a user named `klogd` that is created from busybox install script. A consequence of this is that users who don't want this user on their system can not remove it without it gets recreated on next busybox upgrade. And since it is not really possible to uninstall busybox, it means that it is not really possible to permanently remove the `klogd` user.
Possible solutions:
1. Move the `klogd` user to default `/etc/passwd` provided by `alpine-baselayout`. Users can simply `deluser klogd`, and it will not automatically come back on upgrades. This is the solution I prefer. It is very simple, and the drawback is insignificant (`klogd` user is there by default even if you never install `busybox-openrc`).
2. Move the user creation to `busybox-openrc.pre-install`. Users can avoid creating the `klogd` user with `apk add !busybox-openrc` and not use any of the busybox provided services. There should be alternatives to those, but in this case you cannot use any of the busybox provided services.
3. Split `busybox-openrc`, and ship every service in a separate package. The `klogd` user would be created with `busybox-klogd-openrc` package. I really don't want to do this, because it adds a lot complexity with high risk of unexpected breakages and it has very low benefit.
4. let the install script parse some config where you can disable creation. For example, source `/etc/conf.d/klogd` and see if `command_user=klogd`https://gitlab.alpinelinux.org/alpine/aports/-/issues/15891testing/ddcci-driver-linux-src fails to build with linux-edge-dev-6.8.1-r02024-03-19T16:40:22ZHugo Barreratesting/ddcci-driver-linux-src fails to build with linux-edge-dev-6.8.1-r0## Package Information
* Package name*: **ddcci-driver-linux-src-0.4.4-r2** and **linux-edge-dev-6.8.1-r0**
* Alpine version*: edge / 3.20.0_alpha20240315
* Alpine architecture*: x86_64
## Summary
```
> doas apk fix ddcci-driver-linux...## Package Information
* Package name*: **ddcci-driver-linux-src-0.4.4-r2** and **linux-edge-dev-6.8.1-r0**
* Alpine version*: edge / 3.20.0_alpha20240315
* Alpine architecture*: x86_64
## Summary
```
> doas apk fix ddcci-driver-linux-src
WARNING: opening /home/hugo/packages/main: No such file or directory
(1/1) Reinstalling ddcci-driver-linux-src (0.4.4-r2)
Executing akms-0.2.1-r0.trigger
akms: Building module ddcci-driver-linux/0.4.4-r2 for kernel 6.8.1-0-edge
WARNING: opening /home/hugo/packages/main: No such file or directory
WARNING: opening /home/hugo/packages/main: No such file or directory
(1/8) Installing libasm (0.191-r0)
(2/8) Installing elfutils-dev (0.191-r0)
(3/8) Installing flex (2.6.4-r6)
(4/8) Installing bison (3.8.2-r1)
(5/8) Installing linux-edge-dev (6.8.1-r0)
(6/8) Installing .akms-build (20240319.154618)
(7/8) Installing bison-doc (3.8.2-r1)
(8/8) Installing flex-doc (2.6.4-r6)
OK: 13718 MiB in 3090 packages
make: Entering directory '/usr/src/linux-headers-6.8.1-0-edge'
CC [M] /var/lib/akms/6.8.1-0-edge/ddcci-driver-linux/0.4.4-r2/build/ddcci/ddcci.o
/usr/src/ddcci-driver-linux-0.4.4/ddcci/ddcci.c: In function 'ddcci_detect':
/usr/src/ddcci-driver-linux-0.4.4/ddcci/ddcci.c:1669:9: error: implicit declaration of function 'strlcpy'; did you mean 'strscpy'? [-Werror=implicit-function-declaration]
1669 | strlcpy(info->type, (outer_addr == DDCCI_DEFAULT_DEVICE_ADDR) ? "ddcci" : "ddcci-dependent", I2C_NAME_SIZE);
| ^~~~~~~
| strscpy
/usr/src/ddcci-driver-linux-0.4.4/ddcci/ddcci.c: At top level:
/usr/src/ddcci-driver-linux-0.4.4/ddcci/ddcci.c:1827:27: error: 'I2C_CLASS_DDC' undeclared here (not in a function); did you mean 'I2C_CLASS_SPD'?
1827 | .class = I2C_CLASS_DDC,
| ^~~~~~~~~~~~~
| I2C_CLASS_SPD
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:243: /var/lib/akms/6.8.1-0-edge/ddcci-driver-linux/0.4.4-r2/build/ddcci/ddcci.o] Error 1
make[1]: *** [/usr/src/linux-headers-6.8.1-0-edge/Makefile:1921: /var/lib/akms/6.8.1-0-edge/ddcci-driver-linux/0.4.4-r2/build/ddcci] Error 2
make: *** [Makefile:240: __sub-make] Error 2
make: Leaving directory '/usr/src/linux-headers-6.8.1-0-edge'
akms: ERROR: Failed to build module ddcci-driver-linux/0.4.4-r2 for 6.8.1-0-edge
akms: ERROR: examine /var/lib/akms/6.8.1-0-edge/ddcci-driver-linux/0.4.4-r2/build
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/10267nmtui can not configure wlan02024-03-19T16:16:23Zxrsnmtui can not configure wlan0I’m using the NetworkManager. I installed the package networkmanager and
started the service. The service is working perfectly since a few
months. Wifi works and connection are established automatically.
But since the beginning it was n...I’m using the NetworkManager. I installed the package networkmanager and
started the service. The service is working perfectly since a few
months. Wifi works and connection are established automatically.
But since the beginning it was not possible to use nmtui to configure my
wlan0 interface, only eth0 and lo. I also added my user to the groups
plugdev and netdev and restarted.
nmcli -d:
DEVICE TYPE STATE CONNECTION
eth0 ethernet unavailable —
wlan0 wifi unavailable —
lo loopback unmanaged —
Currently I use wpa\_supplicant to configure my wifi.
*(from redmine: issue id 10267, created on 2019-04-16)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15884erlang: `erl` returned `erl_child_setup closed`2024-03-19T04:27:53ZKomoerlang: `erl` returned `erl_child_setup closed`<!--
This is the issue template for reporting an issue with a specific package. You
can select a different issue template from the dropdown above. Also, feel free
to use the "No template" option in case no template applies to your issue....<!--
This is the issue template for reporting an issue with a specific package. You
can select a different issue template from the dropdown above. Also, feel free
to use the "No template" option in case no template applies to your issue.
Also note that this repository is intended for reporting issues with packages.
For other components, separate issue trackers exist:
* Installer issues: https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues
* Infrastructure issues: https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues
* Initramfs issues: https://gitlab.alpinelinux.org/alpine/mkinitfs/-/issues
-->
## Package Information
* Package name: erlang
* Package version: 26.2.3-r1
* Alpine version: 3.18.4
* Alpine architecture: armv7
## Summary
The `erl` returned `erl_child_setup closed` error.
```
erl_child_setup closed
Crash dump is being written to: erl_crash.dump...done
```
## Steps to reproduce
1. Open up Terminal.
2. Type `erl` with/without arguments and press enter.
3. Error show up.CelesteCelestehttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15885Chromium Segfault inside Docker or other containerization.2024-03-18T20:31:00ZRyan KubaChromium Segfault inside Docker or other containerization.## Package Information
* Package name: chromium
* Package version: chromium-122.0.6261.128-r0
* Alpine version: 3.19.1
* Alpine architecture: all, but x86_64 specifically for this issue
## Summary
Chromium segfaults when run inside do...## Package Information
* Package name: chromium
* Package version: chromium-122.0.6261.128-r0
* Alpine version: 3.19.1
* Alpine architecture: all, but x86_64 specifically for this issue
## Summary
Chromium segfaults when run inside docker/bwrap/proot specifically only the Alpine version. I have maintained webtop and a chromium Docker image for a while and a couple months ago had to swap off chromium to default firefox in these images while rebasing chromium to Debian.
https://github.com/linuxserver/docker-webtop/issues/192
The Glibc versions of chromium on Arch/Debian/Fedora do not exhibit this behavior despite being the same version.
## Steps to reproduce
This is difficult to debug. I am hoping for a magic bullet, but not expecting one. I understand running these desktop applications in a jail like this is a corner case and a bare metal install of Alpine does not suffer from this issue.
The easiest way to reproduce would be on a system with Docker:
```
docker run --rm -it --shm-size=1gb -p 3000:3000 linuxserver/webtop bash
```
Access http://localhost:3000, open a terminal `sudo apk add chromium` `chromium --no-sandbox` (you can avoid no sandbox with `--security-opt seccomp=unconfined`)
Today I discovered something odd when giving another shot at trying to get it to run, it seems like there is some kind of race in the init as chromium can potentially be launched by spamming the command repeatedly as seen here:
![chromium](/uploads/1876da293f379ea4cf989908cdbfd59f/chromium.mp4)
When expanding the CLI options you can get it to launch more reliably, had the best luck with a clean session and `chromium --no-sandbox --disable-gpu --disable-dev-shm-usage --single-process --no-zygote` but it still suffers from the same segfault.
The youtube issue in the attached example happened to me when playing with namespacing and running apps in userspace with bubblewrap and proot even the Glibc versions that work reliably in Docker, it has me thinking all of this is connected somehow and revolves around the sandboxing that chromium is doing.
That is all the information I really have and have been unable to find any kind of reliable fix on my side.lauren n. liberdalauren n. liberdahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15759valgrind on armv7 doesn't work2024-03-01T20:57:33Zqaqlandvalgrind on armv7 doesn't workProblem first found when package mustach !59786 , armv7 get check failed.
Setup qemu-arm following [wiki](https://wiki.alpinelinux.org/wiki/How_to_make_a_cross_architecture_chroot) and run `valgrind uname` also get errors:
<details><su...Problem first found when package mustach !59786 , armv7 get check failed.
Setup qemu-arm following [wiki](https://wiki.alpinelinux.org/wiki/How_to_make_a_cross_architecture_chroot) and run `valgrind uname` also get errors:
<details><summary>Click to expand logs</summary>
```
lab:~/test-c# valgrind uname
==19523== Memcheck, a memory error detector
==19523== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==19523== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info
==19523== Command: uname
==19523==
==19523== error calling PR_SET_PTRACER, vgdb might block
disInstr(thumb): unhandled instruction: 0xDEFF 0x6803
disInstr(thumb): unhandled instruction: 0xDEFF 0xF8D6
disInstr(thumb): unhandled instruction: 0xDEFF 0x2502
disInstr(thumb): unhandled instruction: 0xDEFF 0x4584
disInstr(thumb): unhandled instruction: 0xDEFF 0x682B
disInstr(thumb): unhandled instruction: 0xDEFF 0x4A83
disInstr(thumb): unhandled instruction: 0xDEFF 0xF850
==19523== Invalid write of size 4
==19523== at 0x48956F4: strcpy (in /usr/libexec/valgrind/vgpreload_memcheck-arm-linux.so)
==19523== Address 0x3f8007ac is on thread 1's stack
==19523== 56 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x4884466: ??? (in /usr/libexec/valgrind/vgpreload_core-arm-linux.so)
==19523== Address 0x3f800c80 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x488B4C2: ??? (in /usr/libexec/valgrind/vgpreload_memcheck-arm-linux.so)
==19523== Address 0x3f800c80 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x115AFE: ??? (in /bin/busybox)
==19523== Address 0x3f800c80 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
disInstr(thumb): unhandled instruction: 0xDEFF 0xF850
disInstr(thumb): unhandled instruction: 0xDEFF 0x1B1F
disInstr(thumb): unhandled instruction: 0xDEFF 0x5D73
disInstr(thumb): unhandled instruction: 0xDEFF 0x2602
==19523== Invalid write of size 4
==19523== at 0x1160E2: ??? (in /bin/busybox)
==19523== Address 0x3f800d40 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x115CA2: ??? (in /bin/busybox)
==19523== Address 0x3f800d38 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x18D644: ??? (in /bin/busybox)
==19523== Address 0x3f800d38 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x115E0C: ??? (in /bin/busybox)
==19523== Address 0x3f800d18 is on thread 1's stack
==19523== 24 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x115B3C: ??? (in /bin/busybox)
==19523== Address 0x3f800d00 is on thread 1's stack
==19523== 24 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x115D5E: ??? (in /bin/busybox)
==19523== Address 0x3f800d20 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x115D12: ??? (in /bin/busybox)
==19523== Address 0x3f800d18 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x173A56: ??? (in /bin/busybox)
==19523== Address 0x3f800ae4 is on thread 1's stack
==19523== 560 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x182E78: ??? (in /bin/busybox)
==19523== Address 0x3f800ac0 is on thread 1's stack
==19523== 24 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x182984: ??? (in /bin/busybox)
==19523== Address 0x3f80063c is on thread 1's stack
==19523== 1144 bytes below stack pointer
==19523==
Linux
==19523== Invalid write of size 4
==19523== at 0x1931FE: ??? (in /bin/busybox)
==19523== Address 0x3f800ae8 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x1822C6: ??? (in /bin/busybox)
==19523== Address 0x3f800ae0 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x1165B2: ??? (in /bin/busybox)
==19523== Address 0x3f800ad8 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x115A9A: ??? (in /bin/busybox)
==19523== Address 0x3f800a10 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x488B45E: ??? (in /usr/libexec/valgrind/vgpreload_memcheck-arm-linux.so)
==19523== Address 0x3f800a10 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x4884402: ??? (in /usr/libexec/valgrind/vgpreload_core-arm-linux.so)
==19523== Address 0x3f800a10 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x48844A8: _vgnU_freeres (in /usr/libexec/valgrind/vgpreload_core-arm-linux.so)
==19523== Address 0x3f800a9c is on thread 1's stack
==19523== 48 bytes below stack pointer
==19523==
==19523==
==19523== HEAP SUMMARY:
==19523== in use at exit: 0 bytes in 0 blocks
==19523== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==19523==
==19523== All heap blocks were freed -- no leaks are possible
==19523==
==19523== For lists of detected and suppressed errors, rerun with: -s
==19523== ERROR SUMMARY: 25 errors from 21 contexts (suppressed: 0 from 0)
```
</details>Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/13386testing/nix: channel update broken?2024-02-16T09:53:12ZAlan Diwixtesting/nix: channel update broken?Trying to use nix, got it installed and daemon running, but the first steps of any howto
```
# nix-channel --add https://nixos.org/channels/nixpkgs-unstable nixpkgs
# nix-channel --update
```
fail with
```
unpacking channels...
while set...Trying to use nix, got it installed and daemon running, but the first steps of any howto
```
# nix-channel --add https://nixos.org/channels/nixpkgs-unstable nixpkgs
# nix-channel --update
```
fail with
```
unpacking channels...
while setting up the build environment: executing '/bin/bash': No such file or directory
builder for '/nix/store/j9jgggyvbh6y9cg0ld6ygpspqmcaj2vj-nixpkgs-22.05pre343831.77fda7f6727.drv' failed with exit code 1
error: build of '/nix/store/j9jgggyvbh6y9cg0ld6ygpspqmcaj2vj-nixpkgs-22.05pre343831.77fda7f6727.drv' failed
error: program '/usr/bin/nix-env' failed with exit code 100
```
Am I just using it wrong or is it just broken?
I'm wondering why does it set up build environment during simple channel updateJakub JirutkaJakub Jirutkahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/11645php misuses fpu control, causing improper math behavior in musl2023-09-22T13:54:32ZAndy Postnikovphp misuses fpu control, causing improper math behavior in muslThere's second report about php is wrong with float/double types
- https://gitlab.alpinelinux.org/alpine/aports/-/issues/11446#note_83824
- https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/9188#note_96140 (x86-64 x86 s390x ...There's second report about php is wrong with float/double types
- https://gitlab.alpinelinux.org/alpine/aports/-/issues/11446#note_83824
- https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/9188#note_96140 (x86-64 x86 s390x archs)
Both places using `atof()` or `strtod()`, also I recall https://github.com/php/pecl-file_formats-yaml/pull/29
Same time working on upgrade of PHP I found `sin()` and `cos()` also getting overflow with floats (to investigate)https://gitlab.alpinelinux.org/alpine/aports/-/issues/12275openjdk-jre crashes on s390x arch2023-09-21T06:24:36ZCarole Corleyopenjdk-jre crashes on s390x archLinuxForHealth kafdrop alpine image crashes on s390x but works on arm64 and amd64.
Image on Docker Hub: https://hub.docker.com/repository/docker/linuxforhealth/kafdrop-alpine
The kafdrop image is built on an openjdk image, which is i...LinuxForHealth kafdrop alpine image crashes on s390x but works on arm64 and amd64.
Image on Docker Hub: https://hub.docker.com/repository/docker/linuxforhealth/kafdrop-alpine
The kafdrop image is built on an openjdk image, which is in turn built on a base alpine:3.12.1 image.
The same crash occurs with openjdk11-jre-headless and openjdk11-jre.
Ultimately the shell snippet that invokes the jre is
```
ARGS="--add-opens=java.base/sun.nio.ch=ALL-UNNAMED -Xss256K \
$JMX_ARGS \
$HEAP_ARGS \
$JVM_OPTS"
exec java ${ARGS} -jar /opt/lfh/kafdrop/kafdrop*jar ${CMD_ARGS}
```
Snippet of error, full error file attached.
```
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGFPE (0x8) at pc=0x000003ff9965b3fe (sent by kill), pid=8, tid=18
#
# JRE version: OpenJDK Runtime Environment (11.0.9+11) (build 11.0.9+11-alpine-r0)
# Java VM: OpenJDK 64-Bit Server VM (11.0.9+11-alpine-r0, mixed mode, tiered, compressed oops, g1 gc, linux-s390x)
# Problematic frame:
# V [libjvm.so+0x45b402]
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to /opt/lfh/kafdrop/core.8)
#
# If you would like to submit a bug report, please visit:
# https://gitlab.alpinelinux.org/alpine/aports/issues
#
--------------- S U M M A R Y ------------
Command Line: --add-opens=java.base/sun.nio.ch=ALL-UNNAMED -Xss256K /opt/lfh/kafdrop/kafdrop-3.27.0.jar
Host: 8561, 2 cores, 15G, Alpine Linux v3.12
Time: Mon Jan 4 21:46:25 2021 UTC elapsed time: 0.516111 seconds (0d 0h 0m 0s)
--------------- T H R E A D ---------------
Current thread (0x000002aa39fef000): JavaThread "main" [_thread_in_vm, id=18, stack(0x000003ff9a23d000,0x000003ff9a27dae8)]
Stack: [0x000003ff9a23d000,0x000003ff9a27dae8], sp=0x000003ff9a27ad80, free space=247k
Native frames: (J=compiled Java code, A=aot compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.so+0x45b402]
V [libjvm.so+0x6a7728] JVM_ArrayCopy+0xe0
J 73 java.lang.System.arraycopy(Ljava/lang/Object;ILjava/lang/Object;II)V java.base@11.0.9 (0 bytes) @ 0x000003ff8a5cc322 [0x000003ff8a5cc280+0x00000000000000a2]
j java.lang.AbstractStringBuilder.shift(II)V+33 java.base@11.0.9
```
[hs_err_pid8.log](/uploads/80a7fbe5aedfa8281fed8bd6ba1311a9/hs_err_pid8.log)Simon Fsimon-alpine@fraho.euSimon Fsimon-alpine@fraho.eu