alpine issueshttps://gitlab.alpinelinux.org/groups/alpine/-/issues2024-03-14T14:01:33Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15875backport pwritev2 to musl 1.2.42024-03-14T14:01:33ZJiri Kastnerbackport pwritev2 to musl 1.2.4bcachefs-tools needs pwritev2 in musl, which landed in 1.2.5. to update bcachefs-tools from 1.3.3 to something newer (1.6.4 as of 2024-03-14) would be good to have pwritev2 patches in 1.2.4 (v3.18/v3.19)bcachefs-tools needs pwritev2 in musl, which landed in 1.2.5. to update bcachefs-tools from 1.3.3 to something newer (1.6.4 as of 2024-03-14) would be good to have pwritev2 patches in 1.2.4 (v3.18/v3.19)https://gitlab.alpinelinux.org/alpine/aports/-/issues/15873community/lingot: segfault when opening preferences2024-03-14T11:31:33ZHugo Barreracommunity/lingot: segfault when opening preferencesThe main screen works fine, but `lingot` segfaults when I open preferences (Edit>Preferences):
```console
> lingot
cannot read UI settings filewarning: can't get info for subdevice hw:0,1,0: No such file or directory
warning: can't get ...The main screen works fine, but `lingot` segfaults when I open preferences (Edit>Preferences):
```console
> lingot
cannot read UI settings filewarning: can't get info for subdevice hw:0,1,0: No such file or directory
warning: can't get info for subdevice hw:1,3,0: No such file or directory
warning: can't get info for subdevice hw:1,7,0: No such file or directory
warning: can't get info for subdevice hw:1,8,0: No such file or directory
warning: can't get info for subdevice hw:1,9,0: No such file or directory
zsh: segmentation fault lingot
```
I installed `gtk+3.0-dbg` and `glib-dbg` and collected some information from `gdb`:
```
(gdb) run
Starting program: /usr/bin/lingot
[New LWP 12259]
[New LWP 12260]
[New LWP 12261]
[New LWP 12262]
[New LWP 12263]
cannot read UI settings file[New LWP 12264]
[LWP 12264 exited]
[New LWP 12265]
[New LWP 12266]
[LWP 12265 exited]
[LWP 12266 exited]
[New LWP 12267]
[New LWP 12268]
[New LWP 12269]
[New LWP 12288]
[New LWP 12289]
[New LWP 12338]
[New LWP 12340]
[LWP 12338 exited]
[LWP 12340 exited]
[New LWP 12341]
[New LWP 12342]
[LWP 12341 exited]
[LWP 12342 exited]
warning: can't get info for subdevice hw:0,1,0: No such file or directory
warning: can't get info for subdevice hw:1,3,0: No such file or directory
warning: can't get info for subdevice hw:1,7,0: No such file or directory
warning: can't get info for subdevice hw:1,8,0: No such file or directory
warning: can't get info for subdevice hw:1,9,0: No such file or directory
Thread 1 "lingot" received signal SIGSEGV, Segmentation fault.
get_nominal_size (end=0x7ffff3d5100c "\377\177", p=0x7ffff3d51000 "") at src/malloc/mallocng/meta.h:169
warning: 169 src/malloc/mallocng/meta.h: No such file or directory
(gdb) bt
#0 get_nominal_size (end=0x7ffff3d5100c "\377\177", p=0x7ffff3d51000 "") at src/malloc/mallocng/meta.h:169
#1 __libc_free (p=0x7ffff3d51000) at src/malloc/mallocng/free.c:110
#2 0x00007ffff7f493bc in lingot_audio_alsa_get_audio_system_properties () at /usr/lib/liblingot.so.0
#3 0x000055555555d10d in ??? ()
#7 0x00007ffff7e29e90 in <emit signal 'changed' on instance 0x7ffff400b880 [GtkComboBoxText]>
(instance=instance@entry=0x7ffff400b880, signal_id=<optimized out>, detail=detail@entry=0)
at ../gobject/gsignal.c:3675
#4 0x00007ffff7e29ce3 in _g_closure_invoke_va
(param_types=0x0, n_params=<optimized out>, args=0x7fffffffb830, instance=0x7ffff400b880, return_value=0x0, closure=0x7ffff3ca4060) at ../gobject/gclosure.c:895
#5 signal_emit_valist_unlocked
(instance=instance@entry=0x7ffff400b880, signal_id=signal_id@entry=223, detail=detail@entry=0, var_args=var_args@entry=0x7fffffffb830) at ../gobject/gsignal.c:3516
#6 0x00007ffff7e29dd3 in g_signal_emit_valist
(instance=0x7ffff400b880, signal_id=223, detail=0, var_args=var_args@entry=0x7fffffffb830)
at ../gobject/gsignal.c:3355
#8 0x00007ffff76e4bc3 in gtk_combo_box_set_active_internal
(combo_box=combo_box@entry=0x7ffff400b880 [GtkComboBoxText], path=path@entry=0x7ffff567a6f0)
at ../gtk/gtkcombobox.c:3855
#9 0x00007ffff76e52ec in gtk_combo_box_set_active_iter
(iter=<optimized out>, combo_box=0x7ffff400b880 [GtkComboBoxText]) at ../gtk/gtkcombobox.c:3917
#10 gtk_combo_box_set_active_iter (combo_box=0x7ffff400b880 [GtkComboBoxText], iter=<optimized out>)
at ../gtk/gtkcombobox.c:3907
#11 0x000055555555cf1e in ??? ()
#12 0x000055555555d6a3 in ??? ()
#13 0x000055555555e186 in ??? ()
#14 0x000055555555f4f1 in ??? ()
#15 0x00007ffff7e0b300 in g_closure_invoke
(closure=0x7ffff5672160, return_value=0x0, n_param_values=1, param_values=0x7fffffffbc60, invocation_hint=0x7fffffffbbb0) at ../gobject/gclosure.c:832
#16 0x00007ffff7e389f6 in signal_emit_unlocked_R.isra.0
(node=<optimized out>, detail=<optimized out>, instance=<optimized out>, emission_return=<optimized out>, instance_and_params=<optimized out>) at ../gobject/gsignal.c:3980
#17 0x00007ffff7e29bb2 in signal_emit_valist_unlocked
(instance=instance@entry=0x7ffff5a6cd40, signal_id=signal_id@entry=126, detail=detail@entry=0, var_args=var_args@entry=0x7fffffffbe90) at ../gobject/gsignal.c:3612
#18 0x00007ffff7e29dd3 in g_signal_emit_valist
(instance=0x7ffff5a6cd40, signal_id=126, detail=0, var_args=var_args@entry=0x7fffffffbe90)
--Type <RET> for more, q to quit, c to continue without paging--
at ../gobject/gsignal.c:3355
#19 0x00007ffff7e29e90 in g_signal_emit (instance=instance@entry=0x7ffff5a6cd40, signal_id=<optimized out>, detail=detail@entry=0) at ../gobject/gsignal.c:3675
#20 0x00007ffff792c1d5 in gtk_widget_activate (widget=0x7ffff5a6cd40 [GtkImageMenuItem]) at ../gtk/gtkwidget.c:7845
#21 0x00007ffff77f21b5 in gtk_menu_shell_activate_item (menu_shell=0x7ffff5acfc20 [GtkMenu], menu_item=0x7ffff5a6cd40 [GtkImageMenuItem], force_deactivate=<optimized out>) at ../gtk/gtkmenushell.c:1375
#22 0x00007ffff77f259a in gtk_menu_shell_button_release (widget=0x7ffff5acfc20 [GtkMenu], event=<optimized out>) at ../gtk/gtkmenushell.c:791
#27 0x00007ffff7e29e90 in <emit signal 'button-release-event' on instance 0x7ffff5acfc20 [GtkMenu]> (instance=instance@entry=0x7ffff5acfc20, signal_id=<optimized out>, detail=detail@entry=0) at ../gobject/gsignal.c:3675
#23 0x00007ffff766f825 in _gtk_marshal_BOOLEAN__BOXEDv
(closure=0x7ffff5ed8ba0, return_value=0x7fffffffc1b0, instance=<optimized out>, args=<optimized out>, marshal_data=<optimized out>, n_params=<optimized out>, param_types=0x7ffff5f10990) at gtk/gtkmarshalers.c:130
#24 0x00007ffff7e29ce3 in _g_closure_invoke_va (param_types=0x7ffff5f10990, n_params=<optimized out>, args=0x7fffffffc290, instance=0x7ffff5acfc20, return_value=0x7fffffffc1b0, closure=0x7ffff5ed8ba0)
at ../gobject/gclosure.c:895
#25 signal_emit_valist_unlocked (instance=instance@entry=0x7ffff5acfc20, signal_id=signal_id@entry=79, detail=detail@entry=0, var_args=var_args@entry=0x7fffffffc290) at ../gobject/gsignal.c:3516
#26 0x00007ffff7e29dd3 in g_signal_emit_valist (instance=0x7ffff5acfc20, signal_id=79, detail=0, var_args=var_args@entry=0x7fffffffc290) at ../gobject/gsignal.c:3355
#28 0x00007ffff793d415 in gtk_widget_event_internal.part.0.lto_priv.0 (widget=0x7ffff5acfc20 [GtkMenu], event=0x7ffff57cf860) at ../gtk/gtkwidget.c:7812
#29 0x00007ffff77daebb in propagate_event_up (topmost=<optimized out>, event=<optimized out>, widget=0x7ffff5acfc20 [GtkMenu]) at ../gtk/gtkmain.c:2588
#30 propagate_event (widget=widget@entry=0x7ffff5a6cd40 [GtkImageMenuItem], event=event@entry=0x7ffff57cf860, captured=captured@entry=0, topmost=topmost@entry=0x0) at ../gtk/gtkmain.c:2691
#31 0x00007ffff77dafee in gtk_propagate_event (event=0x7ffff57cf860, widget=0x7ffff5a6cd40 [GtkImageMenuItem]) at ../gtk/gtkmain.c:2725
#32 0x00007ffff77db9d7 in gtk_main_do_event (event=0x7ffff57cf860) at ../gtk/gtkmain.c:1921
#33 gtk_main_do_event (event=<optimized out>) at ../gtk/gtkmain.c:1691
#34 0x00007ffff7e7e837 in _gdk_event_emit (event=0x7ffff57cf860) at ../gdk/gdkevents.c:73
#35 _gdk_event_emit (event=0x7ffff57cf860) at ../gdk/gdkevents.c:67
#36 0x00007ffff7eb5e14 in gdk_event_source_dispatch (base=<optimized out>, callback=<optimized out>, data=<optimized out>) at ../gdk/wayland/gdkeventsource.c:124
#37 0x00007ffff7254295 in g_main_dispatch (context=0x7ffff6b7bf00) at ../glib/gmain.c:3476
#38 0x00007ffff72b5547 in g_main_context_dispatch_unlocked (context=0x7ffff6b7bf00) at ../glib/gmain.c:4284
#39 g_main_context_iterate_unlocked.isra.0 (context=0x7ffff6b7bf00, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4349
#40 0x00007ffff7254bd7 in g_main_loop_run (loop=0x7ffff568b430) at ../glib/gmain.c:4551
#41 0x00007ffff77d64af in gtk_main () at ../gtk/gtkmain.c:1329
#42 0x000055555555b3d5 in main ()
```
I'm not sure how to fill in the missing bits. There's no `lingot-dbg` package.
Does this look like an aports issue, or should I report upstream?Kay Thomaskaythomas@pm.meKay Thomaskaythomas@pm.mehttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15872qBittorrent-NOX (version 4.6.x+) -- Initial login Credentials <-> RC-SERVICE ...2024-03-13T18:51:52ZMartin von ReichenbergqBittorrent-NOX (version 4.6.x+) -- Initial login Credentials <-> RC-SERVICE Issues [ISSUE]The issue:
How to **run** & **configure** the **first** **_(launch/initial)_** **instance** of **qBittorrent-nox** using the (_**open-rc**_) service file?
There NO initial **admin** **password** printed anywhere in `stdout` output . ....The issue:
How to **run** & **configure** the **first** **_(launch/initial)_** **instance** of **qBittorrent-nox** using the (_**open-rc**_) service file?
There NO initial **admin** **password** printed anywhere in `stdout` output . . .
<details><summary>General output:</summary>
``root@dell-poweredge-t310--alpine-linux: qbittorrent-nox``
``< Legal Notice >``
``qBittorrent is a file sharing program. When you run a torrent, its data will be made available to others by means of upload. Any content you share is your sole responsibility.``
``No further notices will be issued.``
``Press 'y' key to accept and continue...``
``y``
``WebUI will be started shortly after internal preparations. Please wait...``
``< Information >``
``To control qBittorrent, access the WebUI at: http://localhost:8080``
``The WebUI administrator username is: admin``
``The WebUI administrator password was not set. A temporary password is provided for this session: LuRx4dt4V``
``You should set your own password in program preferences.``
</details>
. . . and using instance `qbittorrent-nox --profile=/var/lib/qbittorrent/` or: `qbittorrent-nox --configuration=/var/lib/qbittorrent/...` does not solve the issue after running `service qbittorrent-nox start`
<details><summary>The point:</summary>
The point is that it creates a randomly generated password for the first usage of the qBittorrent-nox instance. The default **login name** is always **admin** the **password** _(for example: **_LuRx4dt4V_**)_ for admin is each time randomly generated (it is encrypted and cannot be changed inside the configuration file) unless you login and then change the password in the qbittorrent-nox Web UI settings for anyone you want.
`systemctl start root@qbittorrent-nox` outputs the initially generated password in the `stdout` inside terminal, but there is no such output for **RC-SERVICES**.
`rc-service --verbose qbittorrent-nox start` will launch instance inside `/var/lib/qbittorrent/` and one needs an output from those files and not from `/var/lib/qbittorrent/qBittorrent/` caused by `qbittorrent-nox —profile=/var/lib/qbittorrent/`
Launching, on the other hand, `/usr/bin/qbittorrent-nox` creates instance in `/$USER/$HOME` directory so there we go . . .
</details>
<details><summary>Example of the know-how:</summary>
`qbittorrent-nox —profile=/var/lib/qbittorrent` = `\`
`/var/lib/qbittorrent/qBittorrent/cache/ \`
`/var/lib/qbittorrent/qBittorrent/conf/ \`
`/var/lib/qbittorrent/qBittorrent/local/`
V.S.:
`rc-service --verbose qbittorrent-nox start` = `\`
`/var/lib/qbittorrent/.cache/ \`
`/var/lib/qbittorrent/.conf/ \`
`/var/lib/qbittorrent/.local/`
Then go to: http://localhost:8080 and try it out . . .
</details>
<details><summary>Conclusion:</summary>
The qBittorrent program creates its own HOME directory structure by parsing the `--profile="*"` argument to `qbittorrent-nox`
</details>
<details><summary>Proposal:</summary>
Changing the `/etc/conf.d/qbittorrent-nox` file to:
`# qbittorrent configuration options`
`# extra arguments to pass to qbittorrent`
`command_args="--profile=/var/lib/"`
`# user:group`
`command_user="qbittorrent:qbittorrent"`
`# qbittorrent roots itself in this directory,`
`# creating its config files/logs under it`
`umask=0022`
`# comment to use traditional service management`
`supervisor=supervise-daemon`
+
`/etc/init.d/qbittorrent-nox` to:
`#!/sbin/openrc-run`
`name=qbittorrent-nox`
`description="qbittorrent torrent daemon"`
`command="/usr/bin/qbittorrent-nox"`
`command_background=true`
`: ${directory:=/var/lib/qBittorrent}`
`: ${command_user:=qbittorrent:qbittorrent}`
`: ${umask:=0022}`
`# raise file descriptor count (many open files..)`
`rc_ulimit="-n 50000"`
`depend() {`
`need net`
`after firewall`
`}`
`start_pre() {`
` checkpath -d -o $command_user "$directory"`
`}`
</details>
More details discussed at:
[Alpine Linux English](https://t.me/alpine_linux_english/74861)https://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/mkinitfs/-/issues/55Changing the console font in the initfs2024-03-19T16:25:39ZHugo BarreraChanging the console font in the initfsI'm trying to change the console font size on the initfs.
I mostly interact with the console _before_ the main partition is unlocked (providing a passphrase), so [changing the font via an openrc service](https://wiki.alpinelinux.org/wik...I'm trying to change the console font size on the initfs.
I mostly interact with the console _before_ the main partition is unlocked (providing a passphrase), so [changing the font via an openrc service](https://wiki.alpinelinux.org/wiki/Fonts#Changing_the_console_font) is a bit too late.
When cryptsetup tells me that I've provided the wrong password, I sometimes miss this due to the tiny fonts (it low-key bothers me that font size change halfway through boot, although that's not terrible).
I applied this small patch to `initramfs-init`:
```diff
--- initramfs-init.in
+++ /usr/share/mkinitfs/initramfs-init
@@ -574,6 +574,12 @@
$MOCK modprobe -a ata_piix mptspi sr-mod
fi
+if [ -f /usr/share/consolefonts/default.gz ] && [ -x /usr/sbin/setfont ]; then
+ /usr/sbin/setfont -C /dev/tty0 /usr/share/consolefonts/default.gz
+ echo font changed
+ sleep 2
+fi
+
if [ -n "$KOPT_cryptroot" ]; then
cryptopts="-c ${KOPT_cryptroot}"
if [ "$KOPT_cryptdiscards" = "yes" ]; then
```
And added the following to `/etc/mkinitfs/features.d/consolefont.files`:
/usr/share/consolefonts/default.gz
I finally symlinked `default.gz` to a font of my choice (ter-132n.psf.gz), added `consolefont` to `mkinitfs.conf`, and rebuilt my initfs (the default initfs already contains the busybox implementation of `setfont`).
This successfully changed the console font (to one nice and large and easy to read!)!
However, as soon as `nlplug-findfs` runs, the font resets back to the default tiny size. I suspect that this is a side effect of mdev, but haven't been able to pinpoint down the exact cause. I would appreciate any potential guidance at this point.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15867Differences between drbd utils and kernel module versions2024-03-14T10:30:46ZmikeisitDifferences between drbd utils and kernel module versionsI using v3.19.1
Differences between drbd utils and kernel module versions
The drbd kernel module version is 8.4.11, but drbd-utils is 9.26.0
These two versions are not compatible with each otherI using v3.19.1
Differences between drbd utils and kernel module versions
The drbd kernel module version is 8.4.11, but drbd-utils is 9.26.0
These two versions are not compatible with each otherNatanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15866tshark version greater than 4.0.112024-03-14T11:54:13ZMark Rousetshark version greater than 4.0.11Are there any plans to for any updated version, greater than 4.0.11, of tshark to be released or added to alpine? I'm using lts-alpine for a docker container, and tshark 4.0.11 is used, as expected, but I need a more recent version. On ...Are there any plans to for any updated version, greater than 4.0.11, of tshark to be released or added to alpine? I'm using lts-alpine for a docker container, and tshark 4.0.11 is used, as expected, but I need a more recent version. On my mac laptop, I have version 4.2.3.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15864dovecot icu normalization does not work2024-03-12T09:19:37ZFlorent Daignieredovecot icu normalization does not workHi,
I expect the '[normalizer-icu](https://doc.dovecot.org/settings/plugin/fts-plugin/#plugin_setting-fts-fts_tokenizers)' filter of dovecot to perform [Unicode_equivalence](https://en.wikipedia.org/wiki/Unicode_equivalence) and transpo...Hi,
I expect the '[normalizer-icu](https://doc.dovecot.org/settings/plugin/fts-plugin/#plugin_setting-fts-fts_tokenizers)' filter of dovecot to perform [Unicode_equivalence](https://en.wikipedia.org/wiki/Unicode_equivalence) and transpose non-ascii to ascii (things like 'é' to 'e' in french or 'ß' to 'ss' in german) in indexes to reduce their sizes and improve search results.
It currently doesn't and I am not sure why.
```
$ apk list|grep -E 'icu|dovecot'
dovecot-2.3.21-r17 aarch64 {dovecot} (MIT AND LGPL-2.1-or-later) [installed]
dovecot-fts-flatcurve-1.0.1-r0 aarch64 {dovecot-fts-flatcurve} (LGPL-2.1-or-later) [installed]
dovecot-lmtpd-2.3.21-r17 aarch64 {dovecot} (MIT AND LGPL-2.1-or-later) [installed]
dovecot-pigeonhole-plugin-2.3.21-r17 aarch64 {dovecot} (MIT AND LGPL-2.1-or-later) [installed]
dovecot-pop3d-2.3.21-r17 aarch64 {dovecot} (MIT AND LGPL-2.1-or-later) [installed]
dovecot-submissiond-2.3.21-r17 aarch64 {dovecot} (MIT AND LGPL-2.1-or-later) [installed]
icu-data-full-74.2-r0 aarch64 {icu} (ICU) [installed]
icu-libs-74.2-r0 aarch64 {icu} (ICU) [installed]
$ ldd /usr/lib/dovecot/libdovecot-fts.so|grep icu
libicui18n.so.74 => /usr/lib/libicui18n.so.74 (0xffffad3f5000)
libicuuc.so.74 => /usr/lib/libicuuc.so.74 (0xffffad202000)
libicudata.so.74 => /usr/lib/libicudata.so.74 (0xffffacd58000)
$ grep -iE 'filter|fts_(filter|tokenizers)' /etc/dovecot/dovecot.conf
fts_tokenizers = generic email-address
fts_filters = normalizer-icu snowball stopwords
fts_filters_en = lowercase normalizer-icu snowball english-possessive stopwords
fts_filters_fr = lowercase normalizer-icu snowball contractions stopwords
$ doveadm fts tokenize --lang fr "èéêçîàœôûù"
èéêçîàœôûù
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/15863GNOME 46 upgrade coordination2024-03-26T01:06:18ZNewbyteGNOME 46 upgrade coordinationI'm creating an issue about this just like last year (see https://gitlab.alpinelinux.org/alpine/aports/-/issues/15228) to coordinate the GNOME 46 upgrade. It's due 20 March 2024, so in nine days ([schedule](https://wiki.gnome.org/FortySi...I'm creating an issue about this just like last year (see https://gitlab.alpinelinux.org/alpine/aports/-/issues/15228) to coordinate the GNOME 46 upgrade. It's due 20 March 2024, so in nine days ([schedule](https://wiki.gnome.org/FortySix)). I'm not sure if there's anything we can do yet (haven't really investigated), but it would be nice if we could get the upgrade done smoothly and try to have it completed in Alpine not too long after the upstream release.
Tagging people who helped out last year @pabloyoyoista @chereskata @knuxify @jane4003.20.0https://gitlab.alpinelinux.org/alpine/aports/-/issues/15859KDE6 update aftermath2024-03-15T02:07:31ZPatrycja Rosaalpine@ptrcnull.meKDE6 update aftermatha bit more than a week after !61432 landed in master, countless fixes, at least 15 KF5 packages restored, and one somewhat critical fix still waiting for upstreaming (!61929), here's the current state of aports:
- [ ] 18 packages (x86_64...a bit more than a week after !61432 landed in master, countless fixes, at least 15 KF5 packages restored, and one somewhat critical fix still waiting for upstreaming (!61929), here's the current state of aports:
- [ ] 18 packages (x86_64, varies on others) dependent on KF5 stuff, unable to build due to missing build dependencies ( down from over 70 ) ([link][1])
- [ ] 20 packages (see above) still missing dependent libraries ([link][2])
- [ ] armv7 still choking on packages depending (transitively as well) on qt6-qtwebengine
[1]: https://tpaste.us/a1eM
[2]: https://dev.alpinelinux.org/~ptrc/errors20240311.svg
opening this mostly in hopes of getting more people to help in either upgrading apps to (KF|Qt)6 ( such as in !61851 ), or fixing those that still depend on KF5, so that they don't have missing dependencieshttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15857community/firefox: Speech Dispatcher library is missing2024-03-18T14:30:32ZPatrycja Rosaalpine@ptrcnull.mecommunity/firefox: Speech Dispatcher library is missing![image](/uploads/4d4685bf0ab2ef14d58b59fef32c6d62/image.png)
not sure yet *which* speech library it wants though![image](/uploads/4d4685bf0ab2ef14d58b59fef32c6d62/image.png)
not sure yet *which* speech library it wants thoughPatrycja Rosaalpine@ptrcnull.mePatrycja Rosaalpine@ptrcnull.mehttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15856community/gdm - Xorg sessions cant start on /dev/tty72024-03-10T21:06:16ZLassebqcommunity/gdm - Xorg sessions cant start on /dev/tty7Attempting to run an Xorg session from GDM will throw you right back to the login screen.
This happens because Xorg server started by user does not have permission to access /dev/tty7 as the logs mention:
[Xorg.1.log](/uploads/22d18b3e57...Attempting to run an Xorg session from GDM will throw you right back to the login screen.
This happens because Xorg server started by user does not have permission to access /dev/tty7 as the logs mention:
[Xorg.1.log](/uploads/22d18b3e57e6f56614292f108bae66c9/Xorg.1.log)
Workarounds:
- Switch to a VT2 and run `chown user /dev/tty7` as root
And another side note: This does not happen with lightdm since it starts session on the same tty as the DM, and (maybe) even reuses DM's Xorg server.
- Run a Wayland session and logout prior to logging in an Xorg session (/dev/tty7 remains owned by user after logout)https://gitlab.alpinelinux.org/alpine/aports/-/issues/15855community/gdm - ~/.profile doesn't get sourced by Xorg sessions and by Waylan...2024-03-10T21:04:21ZLassebqcommunity/gdm - ~/.profile doesn't get sourced by Xorg sessions and by Wayland sessions other than GNOMEWhile `~/.profile` does get sourced by GNOME Wayland session, other sessions don't use environment from login shells, but instead inherit environment variables from GDM.
To verify, I use GNOME's run menu (Alt + F2 by default) and run `k...While `~/.profile` does get sourced by GNOME Wayland session, other sessions don't use environment from login shells, but instead inherit environment variables from GDM.
To verify, I use GNOME's run menu (Alt + F2 by default) and run `kgx -- sh` and run `env` in the opened terminal window.
You can also notice MOZ_ENABLE_WAYLAND missing in firefox when running firefox through app launcher.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15854$PATH set in .zshenv gets overwritten by /etc/profile2024-03-13T20:57:57ZLassebq$PATH set in .zshenv gets overwritten by /etc/profileThanks to the mention of `/etc/profile` in !6563 I was able to identify cause of `.zshenv` not appending my paths by the login shell
Apparently Alpine's default /etc/profile sets PATH instead of appending to it.
I did not have such issue...Thanks to the mention of `/etc/profile` in !6563 I was able to identify cause of `.zshenv` not appending my paths by the login shell
Apparently Alpine's default /etc/profile sets PATH instead of appending to it.
I did not have such issue on Arch Linux since their /etc/profile looks like this:
```sh
# Append "$1" to $PATH when not already in.
# This function API is accessible to scripts in /etc/profile.d
append_path () {
case ":$PATH:" in
*:"$1":*)
;;
*)
PATH="${PATH:+$PATH:}$1"
esac
}
# Append our default paths
append_path '/usr/local/sbin'
append_path '/usr/local/bin'
append_path '/usr/bin'
# Force PATH to be environment
export PATH
# Load profiles from /etc/profile.d
if test -d /etc/profile.d/; then
for profile in /etc/profile.d/*.sh; do
test -r "$profile" && . "$profile"
done
unset profile
fi
# Unload our profile API functions
unset -f append_path
```
What makes Arch Linux's approach more convenient is that append_path function is exposed to all files in `/etc/profile.d/`. It also gets utilized by certain packages on Arch Linux (such as java's bin being appended to path)https://gitlab.alpinelinux.org/alpine/aports/-/issues/15852gdm keyboard layout cannot be changed2024-03-13T17:15:27Zviba1gdm keyboard layout cannot be changed**Issue Description**
After installing GNOME on Alpine Linux and setting up the display manager to use GDM3, it has been observed that the login screen is set to QWERTY keyboard layout by default. This makes it impossible for users who d...**Issue Description**
After installing GNOME on Alpine Linux and setting up the display manager to use GDM3, it has been observed that the login screen is set to QWERTY keyboard layout by default. This makes it impossible for users who do not have a QWERTY keyboard or prefer another layout (such as AZERTY) to log in at first attempt. The problem persists even when trying to change the layout from the login screen, which does not provide any option to switch to an alternative keyboard layout.
**Steps to reproduce:**
Install gnome on alpine : [https://wiki.alpinelinux.org/wiki/GNOME](https://wiki.alpinelinux.org/wiki/GNOME)
Attempt to log in with non-QWERTY keyboard layout.
**Expected result:**
The GDM3 interface should allow users to choose their preferred keyboard layout during initial login before entering their password, regardless of whether they are using a QWERTY, AZERTY, DVORAK, or other keyboard layout.
**Actual result:**
GDM3 defaults to QWERTY keyboard layout without providing options to change it at the login screen, making it difficult or impossible for some users to enter their credentials correctly and complete the login process successfully.
**Additional information:**
Once a user logs in and opens their desktop session, GDM3 considers the correct keyboard layout configured in GNOME. However, upon reboot or disconnection of the user, the error recurs where only the QWERTY keyboard layout is available at the GDM3 login screen. Investigation is needed to address why GDM3 fails to remember the last used keyboard layout across boots or disconnects.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15851testing/android-translation-layer: link against gcompat...?2024-03-09T22:51:21ZPatrycja Rosaalpine@ptrcnull.metesting/android-translation-layer: link against gcompat...?most android apps use bionic libc symbols, which seem to also exist in glibc, but not in musl, like `__openat_2` or `strtoull_l`
i feel like linking libandroid.so.0 against gcompat would be the easiest solution, but then, that doesn't q...most android apps use bionic libc symbols, which seem to also exist in glibc, but not in musl, like `__openat_2` or `strtoull_l`
i feel like linking libandroid.so.0 against gcompat would be the easiest solution, but then, that doesn't quite work correctly for mehttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15850py3-bind package missing in 3.17+2024-03-10T20:02:45ZRon Chinnpy3-bind package missing in 3.17+I recently upgraded a name server from Alpine Linux 3.16 to 3.18. The py3-bind subpackage was removed in 3.17 and there are no references to Python in the APKBUILD file now. This package provided support for communicating with rndc fr...I recently upgraded a name server from Alpine Linux 3.16 to 3.18. The py3-bind subpackage was removed in 3.17 and there are no references to Python in the APKBUILD file now. This package provided support for communicating with rndc from Python. Can this package be added again in a future release?https://gitlab.alpinelinux.org/alpine/aports/-/issues/15849bind package missing JSON support2024-03-09T21:05:57ZRon Chinnbind package missing JSON supportI recently upgraded a name server from Alpine Linux 3.16 to 3.18. Several changes were made to the bind package in 3.17 and up that remove functionality that was present in 3.16. One of these changes is the removal of JSON support for...I recently upgraded a name server from Alpine Linux 3.16 to 3.18. Several changes were made to the bind package in 3.17 and up that remove functionality that was present in 3.16. One of these changes is the removal of JSON support for the bind statistics channel. JSON support depends on the "--with-libjson" argument when building bind, but this is missing in 3.18. See https://kb.isc.org/docs/aa-01123 for details about this option.Mike Crutemike@crute.usMike Crutemike@crute.ushttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15846bemenu with wayland backend broken on phosh2024-03-24T07:57:45ZArnav Singhbemenu with wayland backend broken on phosh[bemenu v0.6.20 wants `zwlr_layer_shell_v1` v3](https://github.com/Cloudef/bemenu/commit/6bcffe408c1519834ed00abec4030b9d49f9a52c) but [phoc v0.36.0 only provides v2.](https://gitlab.gnome.org/World/Phosh/phoc/-/blob/v0.36.0/src/desktop....[bemenu v0.6.20 wants `zwlr_layer_shell_v1` v3](https://github.com/Cloudef/bemenu/commit/6bcffe408c1519834ed00abec4030b9d49f9a52c) but [phoc v0.36.0 only provides v2.](https://gitlab.gnome.org/World/Phosh/phoc/-/blob/v0.36.0/src/desktop.c?ref_type=tags#L57) (Newer phoc v0.37.0 or even its main branch also only provide v2.)
```sh
$ printf 'asd\nqwe\n' | WAYLAND_DEBUG=1 bemenu
[2920359.323] wl_registry@2.global(9, "zwlr_layer_shell_v1", 2)
[2920359.393] -> wl_registry@2.bind(9, "zwlr_layer_shell_v1", 3, new id [unknown]@6)
[2920362.814] wl_display@1.error(wl_registry@2, 0, "invalid version for global zwlr_layer_shell_v1 (9): have 2, wanted 3")
wl_registry@2: error 0: invalid version for global zwlr_layer_shell_v1 (9): have 2, wanted 3
```Sören TempelSören Tempelhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15843Pix - "org.kde.kquickimageeditor" is not installed2024-03-18T14:31:43ZJulian GroßPix - "org.kde.kquickimageeditor" is not installedUpgrading from Plasma Mobile 5 to 6, Pix doesn't start anymore.
Running it from command line has it complain about "org.kde.kquickimageeditor" not being installed. The kquickimageeditor package is installed, however. [pmOS-Edge-Pix_not_s...Upgrading from Plasma Mobile 5 to 6, Pix doesn't start anymore.
Running it from command line has it complain about "org.kde.kquickimageeditor" not being installed. The kquickimageeditor package is installed, however. [pmOS-Edge-Pix_not_starting-2024-03-08.log](/uploads/6fa243ae5bbc5e704ab89c94fceeef25/pmOS-Edge-Pix_not_starting-2024-03-08.log)
This is on postmarketOS Edge.