aports issueshttps://gitlab.alpinelinux.org/alpine/aports/-/issues2020-09-01T13:34:45Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/11907weston: system freeze on launch2020-09-01T13:34:45Zshumweston: system freeze on launch`Alpine Edge, x86_64`
Weston freezes the system upon launch with `weston-launch`.
Steps to reproduce:
1. `apk add weston weston-backend-drm weston-shell-desktop weston-xwayland weston-clients`
2. `addgroup $(whoami) weston-launch`
3. D...`Alpine Edge, x86_64`
Weston freezes the system upon launch with `weston-launch`.
Steps to reproduce:
1. `apk add weston weston-backend-drm weston-shell-desktop weston-xwayland weston-clients`
2. `addgroup $(whoami) weston-launch`
3. Do not forget to [set XDG_RUNTIME_DIR](https://wiki.alpinelinux.org/wiki/Wayland).
4. Logout from your session and log back in.
5. Run `weston-launch 2> 1.log` from TTY.
After this, system just hangs. To unfreeze the system, one can switch to another TTY and kill the weston process.
The thing is – `sway` starts perfectly fine.
Here is a log file from fifth step: [1.log](/uploads/d89952d72c7d8bc6217787e1731082f2/1.log)https://gitlab.alpinelinux.org/alpine/aports/-/issues/11904Xorg server segfaults2020-11-29T17:41:48Zalex14frXorg server segfaultsX.org worked until I apk upgraded yesterday. When launching startx I get segmentation fault from the X server. Attached are the X server log and the gdb stacktrace, the segfault appears [here](https://cgit.freedesktop.org/xorg/xserver/tr...X.org worked until I apk upgraded yesterday. When launching startx I get segmentation fault from the X server. Attached are the X server log and the gdb stacktrace, the segfault appears [here](https://cgit.freedesktop.org/xorg/xserver/tree/hw/xfree86/common/xf86platformBus.c#n367).[typescript2](/uploads/66f00d11cd2ee3b28cd1b57636f723b5/typescript2)[Xorg.3.log](/uploads/6dc91b82a51a136718a5716bf05e2231/Xorg.3.log)https://gitlab.alpinelinux.org/alpine/aports/-/issues/11701Ensure valid AppStream metadata2023-05-09T14:22:44ZRasmus Thomsenoss@cogitri.devEnsure valid AppStream metadataCurrently we're having many faulty (e.g. missing description, missing icons etc.) AppStream files in our packages. This isn't necessarily because of packaging error but because upstream didn't follow the AppStream policies while writing ...Currently we're having many faulty (e.g. missing description, missing icons etc.) AppStream files in our packages. This isn't necessarily because of packaging error but because upstream didn't follow the AppStream policies while writing the file for their project. As such we should probably poke upstreams about these issues when we discover them.
See https://appstream.alpinelinux.org/20200628/html/edge/community/issues/index.html for a list of issues. Note that the data is regenerated daily, so you might have to change the date. Also see the main and testing repos.3.19.0Rasmus Thomsenoss@cogitri.devRasmus Thomsenoss@cogitri.devhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/14563[GNOME] [pipewire] noise-cancellation with xiph rnnoise - pipewire fails2023-01-18T06:43:07ZBigB[GNOME] [pipewire] noise-cancellation with xiph rnnoise - pipewire failsHi!
I encouraged a bug on desktop (graphical setup) while trying to enroll xiph rnnoise noise-cancellation for video-conferencing with pipewire (and pipewire-pulse)
- Alpine: `3.17`
- Kernel: `5.15.88-0-lts`
- Gnome: `43.2`
- pipewire,...Hi!
I encouraged a bug on desktop (graphical setup) while trying to enroll xiph rnnoise noise-cancellation for video-conferencing with pipewire (and pipewire-pulse)
- Alpine: `3.17`
- Kernel: `5.15.88-0-lts`
- Gnome: `43.2`
- pipewire, pipewire-pulse: `libpipewire 0.3.60`
- Apparmor enabled: `yes`
According to https://github.com/werman/noise-suppression-for-voice I installed `rnnoise` package using apk. Then I copied and corrected my working OpenSUSE configs.
When I run pipewire as current user it fails with:
```bash
[W][01060.900867] mod.rt | [ module-rt.c: 297 translate_error()] RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
[W][01060.900885] mod.rt | [ module-rt.c: 622 set_nice()] could not set nice-level to -11: No such file or directory
[E][01060.904616] pw.module | [ impl-module.c: 279 pw_context_load_module()] No module "libpipewire-module-x11-bell" was found
[W][01060.905451] default | [ ladspa_plugin.c: 214 ladspa_handle_load_by_path()] cannot find descriptor function in '/usr/lib/librnnoise.so.0': Symbol not found: ladspa_descriptor
[E][01060.905466] default | [ ladspa_plugin.c: 272 load_ladspa_plugin()] failed to load plugin '/usr/lib/librnnoise.so.0': Function not implemented
[E][01060.905475] mod.filter-chain | [module-filter-ch: 2293 pipewire__module_init()] can't load graph: Function not implemented
[E][01060.905495] pw.conf | [ conf.c: 594 load_module()] 0x7fe7dc26e040: could not load mandatory module "libpipewire-module-filter-chain": Function not implemented
[E][01060.905797] default | [ pipewire.c: 125 main()] failed to create context: Function not implemented
```
If I remember correctly, I had similar bug on Void Linux.
Could you help me?
Here is my: `~/.config/pipewire/pipewire.conf.d/99-input-denoising.conf`
```conf
context.modules = [
{ name = libpipewire-module-filter-chain
args = {
node.description = "Noise Canceling source"
media.name = "Noise Canceling source"
filter.graph = {
nodes = [
{
type = ladspa
name = rnnoise
plugin = /usr/lib/librnnoise.so.0
label = noise_suppressor_mono
control = {
"VAD Threshold (%)" = 50.0
"VAD Grace Period (ms)" = 200
"Retroactive VAD Grace (ms)" = 0
}
}
]
}
capture.props = {
node.name = "capture.rnnoise_source"
node.passive = true
audio.rate = 48000
}
playback.props = {
node.name = "rnnoise_source"
media.class = Audio/Source
audio.rate = 48000
}
}
}
]
```
Here is my: `/etc/pipewire/pipewire-pulse.conf`
```conf
# PulseAudio config file for PipeWire version "0.3.49" #
#
# Copy and edit this file in /etc/pipewire for system-wide changes
# or in ~/.config/pipewire for local changes.
#
# It is also possible to place a file with an updated section in
# /etc/pipewire/pipewire-pulse.conf.d/ for system-wide changes or in
# ~/.config/pipewire/pipewire-pulse.conf.d/ for local changes.
#
context.properties = {
## Configure properties in the system.
#mem.warn-mlock = false
#mem.allow-mlock = true
#mem.mlock-all = false
#log.level = 2
#default.clock.quantum-limit = 8192
}
context.spa-libs = {
audio.convert.* = audioconvert/libspa-audioconvert
support.* = support/libspa-support
}
context.modules = [
{ name = libpipewire-module-rt
args = {
nice.level = -11
#rt.prio = 88
#rt.time.soft = -1
#rt.time.hard = -1
}
flags = [ ifexists nofail ]
}
{ name = libpipewire-module-protocol-native }
{ name = libpipewire-module-client-node }
{ name = libpipewire-module-adapter }
{ name = libpipewire-module-metadata }
{ name = libpipewire-module-protocol-pulse
args = {
# contents of pulse.properties can also be placed here
# to have config per server.
}
}
]
# Extra modules can be loaded here. Setup in default.pa can be moved here
context.exec = [
{ path = "pactl" args = "load-module module-always-sink" }
#{ path = "pactl" args = "load-module module-switch-on-connect" }
#{ path = "/usr/bin/sh" args = "~/.config/pipewire/default.pw" }
]
stream.properties = {
#node.latency = 1024/48000
#node.autoconnect = true
resample.quality = 15
#channelmix.normalize = false
#channelmix.mix-lfe = false
#channelmix.upmix = true
#channelmix.upmix-method = simple # none, psd
#channelmix.lfe-cutoff = 120
#channelmix.fc-cutoff = 6000
#channelmix.rear-delay = 12.0
#channelmix.stereo-widen = 0.1
#channelmix.hilbert-taps = 0
}
pulse.properties = {
# the addresses this server listens on
server.address = [
"unix:native"
#"unix:/tmp/something" # absolute paths may be used
#"tcp:4713" # IPv4 and IPv6 on all addresses
#"tcp:[::]:9999" # IPv6 on all addresses
#"tcp:127.0.0.1:8888" # IPv4 on a single address
#
#{ address = "tcp:4713" # address
# max-clients = 64 # maximum number of clients
# listen-backlog = 32 # backlog in the server listen queue
# client.access = "restricted" # permissions for clients
#}
]
#pulse.min.req = 256/48000 # 5ms
#pulse.default.req = 960/48000 # 20 milliseconds
#pulse.min.frag = 256/48000 # 5ms
#pulse.default.frag = 96000/48000 # 2 seconds
#pulse.default.tlength = 96000/48000 # 2 seconds
#pulse.min.quantum = 256/48000 # 5ms
#pulse.default.format = F32
#pulse.default.position = [ FL FR ]
default.clock.rate = 48000
default.clock.allowed-rates = [ 44100 48000 88200 96000 192000 ]
# These overrides are only applied when running in a vm.
vm.overrides = {
pulse.min.quantum = 1024/48000 # 22ms
}
}
# client/stream specific properties
pulse.rules = [
{
matches = [
{
# all keys must match the value. ~ starts regex.
#client.name = "Firefox"
#application.process.binary = "teams"
#application.name = "~speech-dispatcher.*"
}
]
actions = {
update-props = {
#node.latency = 512/48000
}
# Possible quirks:"
# force-s16-info forces sink and source info as S16 format
# remove-capture-dont-move removes the capture DONT_MOVE flag
#quirks = [ ]
}
}
{
# skype does not want to use devices that don't have an S16 sample format.
matches = [
{ application.process.binary = "teams" }
{ application.process.binary = "skypeforlinux" }
]
actions = { quirks = [ force-s16-info ] }
}
{
# firefox marks the capture streams as don't move and then they
# can't be moved with pavucontrol or other tools.
matches = [ { application.process.binary = "firefox" } ]
actions = { quirks = [ remove-capture-dont-move ] }
}
{
# speech dispatcher asks for too small latency and then underruns.
matches = [ { application.name = "~speech-dispatcher*" } ]
actions = {
update-props = {
pulse.min.req = 1024/48000 # 21ms
pulse.min.quantum = 1024/48000 # 21ms
}
}
}
]
```
Thanks for creating Alpine Linux, I love it on desktop, mobile (postmarketOS) and server :heart: !https://gitlab.alpinelinux.org/alpine/aports/-/issues/13781Possible Bug: PyGObject misbehaving surfaced by GNOME Builder2022-05-06T13:15:13ZSaijin-NaibPossible Bug: PyGObject misbehaving surfaced by GNOME BuilderIn testing the latest build of GNOME Builder, it was revealed that one of the built-in Extensions (rstcheck) was not functioning properly, despite working properly in the flatpak builds.
It was suggested by the maintainer of Builder tha...In testing the latest build of GNOME Builder, it was revealed that one of the built-in Extensions (rstcheck) was not functioning properly, despite working properly in the flatpak builds.
It was suggested by the maintainer of Builder that this might be an issue happening in PyGObject for some reason.
https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1669Rasmus Thomsenoss@cogitri.devRasmus Thomsenoss@cogitri.devhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/13706GNOME on Xorg either crashing or working very very slowly2024-03-09T18:49:33ZlinuxuserGNOME on Xorg either crashing or working very very slowlyGNOME, when started via startx, behaves like a powerpoint slide. It renders frame by frame _ONLY_ when I'm switching between TTY's (e.g. CTRL + ALT + F2). <br><br>
**This is the content of my .xinitrc: <br>**
`export XDG_SESSION_TYPE=x1...GNOME, when started via startx, behaves like a powerpoint slide. It renders frame by frame _ONLY_ when I'm switching between TTY's (e.g. CTRL + ALT + F2). <br><br>
**This is the content of my .xinitrc: <br>**
`export XDG_SESSION_TYPE=x11` <br>
`export GDK_BACKEND=x11` <br>
`exec gnome-session` <br><br>
Whereas when I try to start it via GDM, it just kicks me back to the login-screen. <br>
I am using an AMD RX 6800 XT and a Ryzen 5 3600, with kernel version 5.15 LTS, so there shouldn't be any hardware problems. <br><br>
This is my latest Xorg.log file: [Xorg.0.log](/uploads/91f834de3f469870c1f0c368e5c0862f/Xorg.0.log)Rasmus Thomsenoss@cogitri.devRasmus Thomsenoss@cogitri.devhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/13397community/koko: shows folder icons instead of image thumbnails, and UI is broken2022-01-07T21:12:58ZMike Banoncommunity/koko: shows folder icons instead of image thumbnails, and UI is brokenExperienced on Pinephone *(so - a smaller screen than Desktop)* . May be related to packaging, but just in case also reporting here: https://invent.kde.org/graphics/koko/-/issues/61Experienced on Pinephone *(so - a smaller screen than Desktop)* . May be related to packaging, but just in case also reporting here: https://invent.kde.org/graphics/koko/-/issues/61Bart RibbersBart Ribbershttps://gitlab.alpinelinux.org/alpine/aports/-/issues/13283Wrong widgets in Breeze Dark icon theme2021-12-09T16:45:58ZAntonio PiniWrong widgets in Breeze Dark icon themebreeze-icons-5.88.0-r0 dark theme does now display the right (white) widgets in Spacefm file browser, but the common (black) ones instead.breeze-icons-5.88.0-r0 dark theme does now display the right (white) widgets in Spacefm file browser, but the common (black) ones instead.Bart RibbersBart Ribbershttps://gitlab.alpinelinux.org/alpine/aports/-/issues/13230Incomplete drawing in Qt apps and Firefox context menus after upgrading to Al...2021-11-29T07:08:12Z/dev/urandomIncomplete drawing in Qt apps and Firefox context menus after upgrading to Alpine 3.15After I upgraded my machine to Alpine Linux version 3.15, a strange graphical glitch has started occurring whenever I use certain applications.
It seems like some graphical elements, in particular the menus (both the hamburger menu and ...After I upgraded my machine to Alpine Linux version 3.15, a strange graphical glitch has started occurring whenever I use certain applications.
It seems like some graphical elements, in particular the menus (both the hamburger menu and the context menus) in Mozilla Firefox and everything in Qt-based applications, is being drawn partially, with some random 16x1 stripes missing. It's a temporary effect that disappears upon later redraws (sometimes even unrelated ones, like the tint2 taskbar or the window titlebar buttons in Openbox).
Kernel version (uname -a):
`Linux flash-alpine 5.15.4-0-lts #1-Alpine SMP Mon, 22 Nov 2021 09:25:02 +0000 x86_64 Linux`
lspci output:
```
00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 0d)
00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] (rev 02)
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10)
00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #21 (rev f0)
00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #5 (rev f0)
00:1c.7 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #8 (rev f0)
00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device a308 (rev 10)
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
```
lsmod output:
```
Module Size Used by
nls_cp437 20480 1
tcp_bbr 20480 2
cfg80211 1028096 0
8021q 40960 0
mrp 20480 1 8021q
ext4 921600 1
crc16 16384 1 ext4
mbcache 16384 1 ext4
jbd2 163840 1 ext4
nls_utf8 16384 2
nls_cp866 20480 1
vfat 24576 2
fat 86016 1 vfat
snd_sof_pci_intel_cnl 16384 0
snd_sof_intel_hda_common 86016 1 snd_sof_pci_intel_cnl
soundwire_intel 40960 1 snd_sof_intel_hda_common
soundwire_generic_allocation 16384 1 soundwire_intel
soundwire_cadence 32768 1 soundwire_intel
snd_sof_intel_hda 16384 1 snd_sof_intel_hda_common
snd_sof_pci 16384 2 snd_sof_intel_hda_common,snd_sof_pci_intel_cnl
snd_sof_xtensa_dsp 16384 1 snd_sof_intel_hda_common
snd_sof 122880 2 snd_sof_pci,snd_sof_intel_hda_common
snd_hda_codec_hdmi 69632 1
snd_soc_skl 147456 0
snd_soc_hdac_hda 20480 2 snd_sof_intel_hda_common,snd_soc_skl
snd_hda_ext_core 32768 4 snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_soc_skl,snd_sof_intel_hda
snd_soc_sst_ipc 16384 1 snd_soc_skl
snd_soc_sst_dsp 36864 1 snd_soc_skl
snd_hda_codec_realtek 155648 1
snd_soc_acpi_intel_match 57344 3 snd_sof_intel_hda_common,snd_soc_skl,snd_sof_pci_intel_cnl
coretemp 16384 0
snd_soc_acpi 16384 3 snd_soc_acpi_intel_match,snd_sof_intel_hda_common,snd_soc_skl
intel_rapl_msr 16384 0
snd_hda_codec_generic 90112 1 snd_hda_codec_realtek
intel_rapl_common 24576 1 intel_rapl_msr
snd_soc_core 307200 5 soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_soc_skl
ledtrig_audio 16384 2 snd_hda_codec_generic,snd_sof
snd_compress 20480 1 snd_soc_core
intel_tcc_cooling 16384 0
x86_pkg_temp_thermal 16384 0
intel_powerclamp 16384 0
snd_hda_intel 49152 3
snd_intel_dspcfg 24576 3 snd_hda_intel,snd_sof_intel_hda_common,snd_soc_skl
eeepc_wmi 16384 0
snd_intel_sdw_acpi 16384 2 snd_sof_intel_hda_common,snd_intel_dspcfg
iTCO_wdt 16384 0
asus_wmi 45056 1 eeepc_wmi
kvm_intel 323584 0
intel_pmc_bxt 16384 1 iTCO_wdt
snd_hda_codec 163840 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek,snd_soc_hdac_hda
battery 24576 1 asus_wmi
iTCO_vendor_support 16384 1 iTCO_wdt
platform_profile 16384 1 asus_wmi
kvm 1040384 1 kvm_intel
mfd_core 16384 1 intel_pmc_bxt
ee1004 16384 0
sparse_keymap 16384 1 asus_wmi
snd_hda_core 110592 10 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_soc_skl,snd_sof_intel_hda
irqbypass 16384 1 kvm
rfkill 28672 2 asus_wmi,cfg80211
mei_hdcp 20480 0
crct10dif_pclmul 16384 1
hwmon 32768 2 coretemp,asus_wmi
snd_hwdep 16384 1 snd_hda_codec
ghash_clmulni_intel 16384 0
ppdev 20480 0
snd_pcm 135168 11 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_compress,snd_soc_core,snd_soc_skl,snd_hda_core
wmi_bmof 16384 0
aesni_intel 380928 0
snd_timer 45056 1 snd_pcm
r8169 98304 0
i915 3031040 26
crypto_simd 16384 1 aesni_intel
cryptd 24576 2 crypto_simd,ghash_clmulni_intel
snd 106496 15 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_compress,snd_soc_core,snd_pcm
realtek 28672 1
rapl 16384 0
intel_cstate 20480 0
pcspkr 16384 0
soundcore 16384 1 snd
i2c_i801 32768 0
mdio_devres 16384 1 r8169
libphy 159744 3 r8169,mdio_devres,realtek
i2c_smbus 16384 1 i2c_i801
mei_me 40960 1
i2c_algo_bit 16384 1 i915
mei 118784 3 mei_hdcp,mei_me
mousedev 24576 0
ttm 77824 1 i915
evdev 28672 36
input_leds 16384 0
joydev 24576 0
intel_gtt 24576 1 i915
fan 16384 0
thermal 20480 0
wmi 32768 2 asus_wmi,wmi_bmof
parport_pc 28672 0
parport 40960 2 parport_pc,ppdev
video 49152 2 asus_wmi,i915
tun 61440 2
acpi_tad 20480 0
button 20480 0
ipv6 622592 250
af_packet 53248 2
hid_generic 16384 0
usbhid 45056 0
hid 143360 2 usbhid,hid_generic
uas 28672 0
sr_mod 28672 0
cdrom 45056 1 sr_mod
crc32_pclmul 16384 0
xhci_pci 20480 0
xhci_pci_renesas 16384 1 xhci_pci
xhci_hcd 270336 1 xhci_pci
ahci 45056 2
libahci 45056 1 ahci
libata 294912 2 libahci,ahci
simpledrm 16384 0
drm_kms_helper 311296 2 i915,simpledrm
cfbfillrect 16384 1 drm_kms_helper
syscopyarea 16384 1 drm_kms_helper
cfbimgblt 16384 1 drm_kms_helper
sysfillrect 16384 1 drm_kms_helper
sysimgblt 16384 1 drm_kms_helper
fb_sys_fops 16384 1 drm_kms_helper
cfbcopyarea 16384 1 drm_kms_helper
cec 49152 2 drm_kms_helper,i915
drm 626688 16 drm_kms_helper,i915,simpledrm,ttm
i2c_core 102400 7 drm_kms_helper,i2c_algo_bit,ee1004,i2c_smbus,i2c_i801,i915,drm
drm_panel_orientation_quirks 24576 1 drm
agpgart 49152 3 intel_gtt,ttm,drm
loop 40960 0
btrfs 1581056 1
libcrc32c 16384 1 btrfs
crc32c_generic 16384 0
crc32c_intel 24576 4
xor 24576 1 btrfs
raid6_pq 122880 1 btrfs
usb_storage 77824 4 uas
usbcore 294912 5 xhci_hcd,usbhid,usb_storage,xhci_pci,uas
usb_common 16384 2 xhci_hcd,usbcore
sd_mod 53248 6
t10_pi 16384 1 sd_mod
scsi_mod 217088 5 sd_mod,usb_storage,uas,libata,sr_mod
```
I was unable to screenshoot the effect, so this smartphone camera pic will have to do.
![IMG_20211125_114111](/uploads/181d0fa2ffdc34ef3f3c99967e9a26f9/IMG_20211125_114111.jpg)https://gitlab.alpinelinux.org/alpine/aports/-/issues/12605gdm: fails to wake up after locking2023-01-29T15:58:55ZDylan Van Asschegdm: fails to wake up after locking# Description
I upgraded to edge to have GNOME 40 and when my desktop is now locked (manually or automatically after X minutes), I cannot wake it up anymore. The screen stays blank. If I switch to another tty using CTRL + F-key, the scr...# Description
I upgraded to edge to have GNOME 40 and when my desktop is now locked (manually or automatically after X minutes), I cannot wake it up anymore. The screen stays blank. If I switch to another tty using CTRL + F-key, the screen turns on and shows me a prompt. If I switch back to the original tty, the GDM greeter is shown.
# What's happening
Pressing a key or moving the mouse doesn't do anything when the desktop is locked.
# What's supposed to happen
Pressing a key or moving the mouse wakes up the desktop and shows the GDM greeter.
# Steps to reproduce
1. Lock the screen
2. Wait until the screen enter low power mode
3. Try to wake it up by moving the mouse or pressing a key on the keyboard.
# Environment
- Alpine Linux edge
- Intel integrated GPU (Mesa Intel® UHD Graphics 630 (CML GT2))
- GNOME 40.0 on Wayland
- GDM 40.0
# Logs
[greeter.log](/uploads/1b0a415a8a2978b4011bb906bed51295/greeter.log)Rasmus Thomsenoss@cogitri.devRasmus Thomsenoss@cogitri.devhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/11809telegram-desktop hard crashes looking at certain sticker previews2020-11-10T15:59:08ZEllietelegram-desktop hard crashes looking at certain sticker previewstelegram-desktop hard crashes for me when I look at certain sticker combinations in the preview panel when writing a single emoji which will show a live-mix of "fitting" stickers based on recent usage to go with that emoji. This seems to...telegram-desktop hard crashes for me when I look at certain sticker combinations in the preview panel when writing a single emoji which will show a live-mix of "fitting" stickers based on recent usage to go with that emoji. This seems to happen 100% depending on the exact sticker set shown, which makes me wonder if this is a musl-libc issue? (E.g. stack blown when rendering certain more complex animated ones in combination?)
Edit: this is on the PinePhone using postmarketOS stable based on Alpine 3.12 with telegram-desktop 2.1.11-r1https://gitlab.alpinelinux.org/alpine/aports/-/issues/11643telegram-desktop minimum window height is too big on PinePhone+phosh (in post...2022-05-16T20:38:13ZEllietelegram-desktop minimum window height is too big on PinePhone+phosh (in postmarketOS)The telegram-desktop minimum window height is too big on PinePhone using the phosh desktop (with alpine-based postmarketOS), which leads to the input bar not being visible in a chat window:
![](https://user-images.githubusercontent.com/...The telegram-desktop minimum window height is too big on PinePhone using the phosh desktop (with alpine-based postmarketOS), which leads to the input bar not being visible in a chat window:
![](https://user-images.githubusercontent.com/64124388/84539028-3e896700-ace2-11ea-933b-e8481780f046.png)
There has apparently been an upstream change for this that was reverted due to other windows (like theme preview) glitching out, and it was suggested that maybe Alpine would want to re-apply this patch downstream:
https://github.com/telegramdesktop/tdesktop/issues/8058#issuecomment-643461605
I think it would make a lot more sense if original Telegram was just fixed itself, but since apparently that might not happen any time soon I thought I might as well forward the suggestion to temporarily address it in the aports.https://gitlab.alpinelinux.org/alpine/aports/-/issues/11642Move /usr/share/appdata to /usr/share/metainfo2023-05-10T02:33:10ZRasmus Thomsenoss@cogitri.devMove /usr/share/appdata to /usr/share/metainfoSee https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#spec-component-location:
> # Important: Legacy Path
>
> AppStream tools scan the /usr/share/appdata/ path for legacy compatibility as well. It should not be use...See https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#spec-component-location:
> # Important: Legacy Path
>
> AppStream tools scan the /usr/share/appdata/ path for legacy compatibility as well. It should not be used anymore by new software though, even on older Linux distributions (like RHEL 7 and Ubuntu 16.04 LTS) the metainfo path is well supported. Support for the legacy path will likely be dropped completely with a future AppStream 1.0 release.Rasmus Thomsenoss@cogitri.devRasmus Thomsenoss@cogitri.dev