Librem5 issueshttps://source.puri.sm/groups/Librem5/-/issues2022-10-07T07:16:22Zhttps://source.puri.sm/Librem5/OS-issues/-/issues/209Auto-rotation icon unclear2022-10-07T07:16:22ZDorota CzaplejewiczAuto-rotation icon unclearThe button which controls automatic display orientation is a circular arrow. The meaning is hard to decode.
Usually this kind of icon is dedicated to verbs like restart, redo, reload, retry. Moreover, clicking it does not cause anything...The button which controls automatic display orientation is a circular arrow. The meaning is hard to decode.
Usually this kind of icon is dedicated to verbs like restart, redo, reload, retry. Moreover, clicking it does not cause anything to happen, making it not possible to understand the purpose without an external source of knowledge.
Here are some concepts that might be useful for creating a better icon:
- display
- that display orientation has only 4 cardinal directions
- that display has just 2 shapes: portrait and landscape
- lock
- gravity
The clearest icon I can immediately think of is something presenting the 2 possible display shapes, and an arrow connecting them.https://source.puri.sm/Librem5/debs/gnome-contacts/-/issues/41Contacts "Calls" button not working2022-10-07T07:16:48ZTodd WeaverContacts "Calls" button not workingReproduction:
1. Enter a contact
2. Click on the 'calls' icon
3. Witness nothing happens
![contacts-calls-not-sending-2020-06-18](/uploads/b0a5605d45842a8af34ab36be863d726/contacts-calls-not-sending-2020-06-18.webm)
(Also chat fails)
!...Reproduction:
1. Enter a contact
2. Click on the 'calls' icon
3. Witness nothing happens
![contacts-calls-not-sending-2020-06-18](/uploads/b0a5605d45842a8af34ab36be863d726/contacts-calls-not-sending-2020-06-18.webm)
(Also chat fails)
![chatty-fails-to-start-new-chat-from-number-2020-06-18](/uploads/994d6ef11be56691220fd6603b09628f/chatty-fails-to-start-new-chat-from-number-2020-06-18.webm)
```
purism@pureos:~$ dpkg -s gnome-contacts
Package: gnome-contacts
Status: install ok installed
Priority: optional
Section: gnome
Installed-Size: 1655
Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>
Architecture: arm64
Version: 3.32+3371+gitc22366f-1pureos0
Depends: libatk1.0-0 (>= 1.12.4), libc6 (>= 2.17), libcairo2 (>= 1.10.0), libcheese-gtk25 (>= 3.18.0), libcheese8 (>= 3.18.0), libedataserver-1.2-23 (>= 3.17), libedataserverui-1.2-2 (>= 3.16.2), libfolks-eds25 (>= 0.7.3), libfolks25 (>= 0.11.1), libgdk-pixbuf2.0-0 (>= 2.23.0), libgee-0.8-2 (>= 0.20.0), libglib2.0-0 (>= 2.51.2), libgnome-desktop-3-17 (>= 3.17.92), libgoa-1.0-0b (>= 3.5.90), libgtk-3-0 (>= 3.22.0), libhandy-0.0-0 (>= 0.0.12), libpango-1.0-0 (>= 1.37.5), libpangocairo-1.0-0 (>= 1.14.0), libwayland-server0 (>= 1.0.2), dconf-gsettings-backend | gsettings-backend
Description: Contacts manager for GNOME
GNOME Contacts is a standalone application to view and manage contacts
provided by all available contacts sources (Evolution, Empathy, etc).
Homepage: https://wiki.gnome.org/Apps/Contacts
purism@pureos:~$ dpkg -s calls
Package: calls
Status: install ok installed
Priority: optional
Section: comm
Installed-Size: 528
Maintainer: Julian Sparber <julian.sparber@puri.sm>
Architecture: arm64
Version: 0.1.6
Depends: libc6 (>= 2.17), libcairo2 (>= 1.14.0), libebook-contacts-1.2-2 (>= 3.16.2), libfeedback-0.0-0 (>= 0.0.0+git20200305), libfolks25 (>= 0.11.1), libgdk-pixbuf2.0-0 (>= 2.23.0), libgee-0.8-2 (>= 0.8.3), libglib2.0-0 (>= 2.57.2), libgom-1.0-0 (>= 0.3.2), libgtk-3-0 (>= 3.21.5), libhandy-0.0-0 (>= 0.0.12), libmm-glib0 (>= 1.5.993), libpango-1.0-0 (>= 1.14.0), libpeas-1.0-0 (>= 1.0.0), libwayland-client0 (>= 1.9.91), modemmanager
Conffiles:
/etc/xdg/autostart/sm.puri.Calls.desktop 656e549c2c3e7b931a8f37ac739cbc3c
Description: Make and receive PSTN phone calls
A GTK+ user interface for PSTN phone calls using oFono.
Homepage: https://gitlab.gnome.org/Community/Purism/calls
purism@pureos:~$
```https://source.puri.sm/Librem5/millipixels/-/issues/51fix comment and printf, add support for PinePhone.2022-10-07T08:11:22ZPavel Machekfix comment and printf, add support for PinePhone.I tried to create merge requests by email, but apparently that does not work. Can maintainers simply apply the patch? PinePhone support is useful because it allows me to work on Auto Exposure support without access to Librem 5. [delme](/...I tried to create merge requests by email, but apparently that does not work. Can maintainers simply apply the patch? PinePhone support is useful because it allows me to work on Auto Exposure support without access to Librem 5. [delme](/uploads/d6ad985d280359517e7a2691b4b9988a/delme)https://source.puri.sm/Librem5/Apps_Issues/-/issues/233include phosh-mobile-settings in default images2022-10-10T15:11:57ZPirate Praveeninclude phosh-mobile-settings in default imagesI think phosh-mobile-settings should be included by default in the images.I think phosh-mobile-settings should be included by default in the images.https://source.puri.sm/Librem5/librem5-base/-/issues/65Video output does not work with Fujitsu Siemens USB Port Replicator PR092022-10-16T21:58:08ZJan VlugVideo output does not work with Fujitsu Siemens USB Port Replicator PR09The Librem 5 connected to a [Fujitsu USB Port Replicator PR09](https://www.fujitsu.com/global/products/computing/peripheral/accessories/connectivity/usb-port-replicator-pr09.html) with two DisplayPort displays, does not detect the displa...The Librem 5 connected to a [Fujitsu USB Port Replicator PR09](https://www.fujitsu.com/global/products/computing/peripheral/accessories/connectivity/usb-port-replicator-pr09.html) with two DisplayPort displays, does not detect the displays.
When the Librem 5 is connected no output is shown on the displays. The displays are also not detected in GNOME settings. However, charging, mouse and keyboard do work.
For further details see this [forum thread](https://forums.puri.sm/t/should-video-output-work-with-fujitsu-siemens-usb-port-replicator-pr09/18140).https://source.puri.sm/Librem5/librem5-base/-/issues/49udev: usb-otg1 suspend doesn't always get enabled2022-10-21T20:57:23ZSebastian Krzyszkowiakudev: usb-otg1 suspend doesn't always get enabled[librem5-pm.udev](https://source.puri.sm/Librem5/librem5-base/-/blob/pureos/byzantium/debian/librem5-base-defaults.librem5-pm.udev#L7) sets:
```
DEVPATH=="/devices/platform/soc@0/38100000.usb", TEST=="power/control", ATTR{power/control}...[librem5-pm.udev](https://source.puri.sm/Librem5/librem5-base/-/blob/pureos/byzantium/debian/librem5-base-defaults.librem5-pm.udev#L7) sets:
```
DEVPATH=="/devices/platform/soc@0/38100000.usb", TEST=="power/control", ATTR{power/control}="auto"
```
...but for some reason, it does not always get actually applied:
```
$ cat /sys/devices/platform/soc@0/38100000.usb/power/control
on
```
Based on my testing, suspending 38100000.usb (usb-otg1 - the external USB-C port) when not in use can save around 80mW and I haven't noticed any undesirable side effects of doing so.
Last time I tried to debug it I ended up having no clue what's going on, so writing this down in hopes that someone else could take a look at it and offer a fresh perspective ;)https://source.puri.sm/Librem5/linux/-/issues/443Crash in GPU2022-10-29T15:12:27ZDorota CzaplejewiczCrash in GPUDiscovered when testing [libcamera with GPU processing](https://source.puri.sm/dorota.czaplejewicz/libcamera/-/commit/84e2dea3fb62f5d14b2d37d72594b94a770e3f23) on kernel 6.0.0-1-librem5:
```
DISPLAY=:0 WL_DISPLAY=:0 LIBCAMERA_LOG_LEVELS...Discovered when testing [libcamera with GPU processing](https://source.puri.sm/dorota.czaplejewicz/libcamera/-/commit/84e2dea3fb62f5d14b2d37d72594b94a770e3f23) on kernel 6.0.0-1-librem5:
```
DISPLAY=:0 WL_DISPLAY=:0 LIBCAMERA_LOG_LEVELS="*:0" GST_DEBUG="libcamera*:7" GST_PLUGIN_PATH=/home/purism/caminstall/lib/aarch64-linux-gnu/gstreamer-1.0/ LD_LIBRARY_PATH=/home/purism/caminstall/lib/aarch64-linux-gnu/ gst-launch-1.0 libcamerasrc camera-name="/base/soc\@0/bus\@30800000/i2c\@30a50000/camera\@2d" ! 'video/x-raw,format=BGRA,width=1052,height=780' ! glimagesink
```
Interrupting this process (which is not doing proper cleanup) yields:
```
[ 80.412658] ------------[ cut here ]------------
[ 80.412682] Memory manager not clean during takedown.
[ 80.412742] WARNING: CPU: 0 PID: 2052 at drivers/gpu/drm/drm_mm.c:999 drm_mm_takedown+0x30/0x40
[ 80.412773] Modules linked in: overlay usb_f_acm u_serial usb_f_ecm u_ether ofpart binfmt_misc spi_nor mtd caam_jr caamhash_desc hi846 caamalg_desc crypto_engine st_lsm6dsx_spi hantro_vpu(C) snd_soc_gtm601 imx7_media_csi(C) snd_soc_simple_card v4l2_vp9 v4l2_h264 snd_soc_simple_card_utils v4l2_mem2mem videobuf2_dma_contig dw9714 videobuf2_memops st_lsm6dsx_i2c imx8mq_mipi_csi2(C) s5k3l6xx leds_lm3560 v4l2_flash_led_class videobuf2_v4l2 v4l2_fwnode mousedev st_lsm6dsx vcnl4000 videobuf2_common v4l2_async industrialio_triggered_buffer kfifo_buf snd_soc_wm8962 videodev mc gnss_mtk gnss_serial gnss snd_soc_fsl_sai snd_soc_fsl_utils imx_pcm_dma snd_soc_core snd_pcm_dmaengine imx_sdma snd_pcm virt_dma snd_timer snd soundcore imx2_wdt caam error rfkill_hks watchdog rfkill libcomposite ledtrig_timer ledtrig_pattern fuse zram ip_tables x_tables ipv6 uas usb_storage xhci_plat_hcd xhci_hcd usbcore aes_ce_blk dwc3 crct10dif_ce ghash_ce cdns_mhdp_imx ulpi pwm_vibra cdns_mhdp_drmcore sha2_ce
[ 80.413094] drm_display_helper udc_core sha1_ce usb_common imx_dcss bq25890_charger phy_fsl_imx8mq_usb edt_ft5x06 tps6598x typec clk_bd718x7 roles snvs_pwrkey
[ 80.413149] CPU: 0 PID: 2052 Comm: task0 Tainted: G C 6.0.0-1-librem5 #1
[ 80.413159] Hardware name: Purism Librem 5r4 (DT)
[ 80.413166] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 80.413176] pc : drm_mm_takedown+0x30/0x40
[ 80.413184] lr : drm_mm_takedown+0x30/0x40
[ 80.413192] sp : ffff80000cd43950
[ 80.413196] x29: ffff80000cd43950 x28: 0000ffff9c944418 x27: fffffffffffffe00
[ 80.413212] x26: 0000000045585401 x25: ffff00002e905c80 x24: dead000000000100
[ 80.413228] x23: dead000000000122 x22: ffff0000bc317ba0 x21: ffff80000ae6f000
[ 80.413243] x20: ffff80000ae6f000 x19: ffff000031af3800 x18: 000000000000001c
[ 80.413258] x17: 000000000000001e x16: 0000000000000000 x15: 000000000016e360
[ 80.413273] x14: 0000000000000000 x13: 2e6e776f64656b61 x12: 7420676e69727564
[ 80.413288] x11: 00000000ffffdfff x10: 00000000ffffdfff x9 : ffff8000080b592c
[ 80.413303] x8 : 000000000002ffe8 x7 : c0000000ffffdfff x6 : 0000000000017ff4
[ 80.413318] x5 : ffff0000bf92c9d0 x4 : 0000000000000000 x3 : 0000000000000027
[ 80.413332] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff00002e905880
[ 80.413348] Call trace:
[ 80.413352] drm_mm_takedown+0x30/0x40
[ 80.413362] etnaviv_iommuv2_free+0x28/0xe0
[ 80.413374] etnaviv_iommu_unmap_gem+0xcc/0x130
[ 80.413384] etnaviv_gem_free_object+0x98/0x110
[ 80.413393] drm_gem_object_free+0x24/0x40
[ 80.413407] drm_gem_object_handle_put_unlocked+0xd0/0xf4
[ 80.413418] drm_gem_object_release_handle+0x60/0x7c
[ 80.413429] idr_for_each+0x68/0xfc
[ 80.413441] drm_gem_release+0x30/0x50
[ 80.413452] drm_file_free.part.0+0x1e0/0x230
[ 80.413462] drm_close_helper.isra.0+0x64/0x74
[ 80.413472] drm_release+0x70/0x150
[ 80.413482] __fput+0x78/0x230
[ 80.413493] ____fput+0x18/0x24
[ 80.413502] task_work_run+0x88/0x1a0
[ 80.413512] do_exit+0x2e4/0x970
[ 80.413525] do_group_exit+0x3c/0xb0
[ 80.413535] get_signal+0x8cc/0x940
[ 80.413543] do_notify_resume+0x17c/0xfcc
[ 80.413556] el0_svc+0x78/0x90
[ 80.413569] el0t_64_sync_handler+0xb8/0xc0
[ 80.413579] el0t_64_sync+0x18c/0x190
[ 80.413588] ---[ end trace 0000000000000000 ]---
[ 80.414927] Unable to handle kernel paging request at virtual address ffff80000b103ec8
[ 80.423466] Mem abort info:
[ 80.427270] ESR = 0x0000000096000047
[ 80.431246] EC = 0x25: DABT (current EL), IL = 32 bits
[ 80.436652] SET = 0, FnV = 0
[ 80.439884] EA = 0, S1PTW = 0
[ 80.443127] FSC = 0x07: level 3 translation fault
[ 80.448097] Data abort info:
[ 80.451052] ISV = 0, ISS = 0x00000047
[ 80.454967] CM = 0, WnR = 1
[ 80.457993] swapper pgtable: 4k pages, 48-bit VAs, pgdp=000000008191c000
[ 80.464721] [ffff80000b103ec8] pgd=10000000fffff003, p4d=10000000fffff003, pud=10000000ffffe003, pmd=10000000ff36e003, pte=0000000000000000
[ 80.477354] Internal error: Oops: 96000047 [#1] PREEMPT SMP
[ 80.482929] Modules linked in: overlay usb_f_acm u_serial usb_f_ecm u_ether ofpart binfmt_misc spi_nor mtd caam_jr caamhash_desc hi846 caamalg_desc crypto_engine st_lsm6dsx_spi hantro_vpu(C) snd_soc_gtm601 imx7_media_csi(C) snd_soc_simple_card v4l2_vp9 v4l2_h264 snd_soc_simple_card_utils v4l2_mem2mem videobuf2_dma_contig dw9714 videobuf2_memops st_lsm6dsx_i2c imx8mq_mipi_csi2(C) s5k3l6xx leds_lm3560 v4l2_flash_led_class videobuf2_v4l2 v4l2_fwnode mousedev st_lsm6dsx vcnl4000 videobuf2_common v4l2_async industrialio_triggered_buffer kfifo_buf snd_soc_wm8962 videodev mc gnss_mtk gnss_serial gnss snd_soc_fsl_sai snd_soc_fsl_utils imx_pcm_dma snd_soc_core snd_pcm_dmaengine imx_sdma snd_pcm virt_dma snd_timer snd soundcore imx2_wdt caam error rfkill_hks watchdog rfkill libcomposite ledtrig_timer ledtrig_pattern fuse zram ip_tables x_tables ipv6 uas usb_storage xhci_plat_hcd xhci_hcd usbcore aes_ce_blk dwc3 crct10dif_ce ghash_ce cdns_mhdp_imx ulpi pwm_vibra cdns_mhdp_drmcore sha2_ce
[ 80.483152] drm_display_helper udc_core sha1_ce usb_common imx_dcss bq25890_charger phy_fsl_imx8mq_usb edt_ft5x06 tps6598x typec clk_bd718x7 roles snvs_pwrkey
[ 80.583908] CPU: 0 PID: 2052 Comm: task0 Tainted: G WC 6.0.0-1-librem5 #1
[ 80.591999] Hardware name: Purism Librem 5r4 (DT)
[ 80.596702] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 80.603664] pc : etnaviv_iommuv2_unmap+0x34/0x50
[ 80.608292] lr : etnaviv_context_unmap+0x68/0x94
[ 80.612911] sp : ffff80000cd43910
[ 80.616223] x29: ffff80000cd43910 x28: 0000ffff9c944418 x27: fffffffffffffe00
[ 80.623362] x26: 0000000045585401 x25: ffff000031af3a00 x24: ffff00000d22b400
[ 80.630502] x23: ffff80000ae6f000 x22: 0000000000002000 x21: ffff80000ae6f000
[ 80.637641] x20: 0000000000000000 x19: 00000000fd3b2000 x18: 000000000000001c
[ 80.644779] x17: 000000000000001e x16: 0000000000000000 x15: 000000000016e360
[ 80.651918] x14: 0000000000000000 x13: 2e6e776f64656b61 x12: 7420676e69727564
[ 80.659057] x11: 00000000ffffdfff x10: 00000000ffffdfff x9 : ffff80000885ce68
[ 80.666196] x8 : ffff8000097b9640 x7 : ffff8000b6725000 x6 : 0000000000000000
[ 80.673334] x5 : 0000000000000002 x4 : 000000000000043c x3 : ffff80000ae6f000
[ 80.680473] x2 : ffff80000b103000 x1 : 00000000000003b2 x0 : 0000000000001000
[ 80.687613] Call trace:
[ 80.690057] etnaviv_iommuv2_unmap+0x34/0x50
[ 80.694329] etnaviv_iommu_remove_mapping+0x88/0xc4
[ 80.699208] etnaviv_iommu_unmap_gem+0xf8/0x130
[ 80.703739] etnaviv_gem_free_object+0x98/0x110
[ 80.708270] drm_gem_object_free+0x24/0x40
[ 80.712370] drm_gem_object_handle_put_unlocked+0xd0/0xf4
[ 80.717771] drm_gem_object_release_handle+0x60/0x7c
[ 80.722737] idr_for_each+0x68/0xfc
[ 80.726229] drm_gem_release+0x30/0x50
[ 80.729980] drm_file_free.part.0+0x1e0/0x230
[ 80.734338] drm_close_helper.isra.0+0x64/0x74
[ 80.738783] drm_release+0x70/0x150
[ 80.742272] __fput+0x78/0x230
[ 80.745330] ____fput+0x18/0x24
[ 80.748471] task_work_run+0x88/0x1a0
[ 80.752135] do_exit+0x2e4/0x970
[ 80.755367] do_group_exit+0x3c/0xb0
[ 80.758944] get_signal+0x8cc/0x940
[ 80.762433] do_notify_resume+0x17c/0xfcc
[ 80.766446] el0_svc+0x78/0x90
[ 80.769504] el0t_64_sync_handler+0xb8/0xc0
[ 80.773689] el0t_64_sync+0x18c/0x190
[ 80.777356] Code: d34c5421 52800045 d50323bf f8647862 (b8217845)
[ 80.783450] ---[ end trace 0000000000000000 ]---
[ 80.788197] Fixing recursive fault but reboot is needed!
```https://source.puri.sm/Librem5/linux/-/issues/25Needs to ship librem-evk.dtb as well2022-11-04T11:08:48ZGuido GuntherNeeds to ship librem-evk.dtb as wellSince the kernel sent upstream uses the same board name `Purism Librem 5 devkit` (and doesn't change to appending the board revision (as suggested)) but uses a different dtb name (`imx8mq-librem5-devkit.dtb`) we need to ship a dtb with t...Since the kernel sent upstream uses the same board name `Purism Librem 5 devkit` (and doesn't change to appending the board revision (as suggested)) but uses a different dtb name (`imx8mq-librem5-devkit.dtb`) we need to ship a dtb with the above name as well in order not break kernel installations.
I had a look at flash-kernel if there are ways around this but didn't spot anything. Other workarounds like dumping files in /etc/flash-kernel are even more cumbersome to maintain.https://source.puri.sm/Librem5/linux/-/issues/28Image should boot 5.X kernel2022-11-04T11:09:00ZHeather EllsworthImage should boot 5.X kernelEpic: https://source.puri.sm/Librem5/use-cases/issues/7
The phone will ultimately ship with a 5.X kernel, so we will need the image to be built and shipped with the latest linux-next kernel.
- [x] [Release linux-next kernel for testing]...Epic: https://source.puri.sm/Librem5/use-cases/issues/7
The phone will ultimately ship with a 5.X kernel, so we will need the image to be built and shipped with the latest linux-next kernel.
- [x] [Release linux-next kernel for testing](https://source.puri.sm/Librem5/linux-next/issues/27)
- [x] [Get all the branches together](https://source.puri.sm/Librem5/linux-next/issues/15)
- [x] [Trim defconfig](https://source.puri.sm/Librem5/linux-next/issues/29)
- [ ] [Phone Essentials List](https://source.puri.sm/Librem5/Apps_Issues/issues/64)
- [ ] [Screen won't turn on after 3hrs+ of blanked and idle charging while powered on](https://source.puri.sm/Librem5/linux-next/issues/148)Last: Poppy (W24-26)https://source.puri.sm/Librem5/debs/gnss-share/-/issues/4Won't let geoclue connect2022-11-07T09:50:00ZGuido GuntherWon't let geoclue connectgeoclue fails to connect issuing:
```
Dez 23 13:12:22 nn geoclue[5726]: Failed to connect to NMEA service: Could not connect: Connection refused
```
I haven't debuggged any further yet since the current status of what is expected to wo...geoclue fails to connect issuing:
```
Dez 23 13:12:22 nn geoclue[5726]: Failed to connect to NMEA service: Could not connect: Connection refused
```
I haven't debuggged any further yet since the current status of what is expected to work is unclear to me (given e.g. that we have newer gnss-share but no adjusted geoclue config)https://source.puri.sm/Librem5/debs/epiphany/-/issues/38No page is loading after upgrade to libwebkit2gtk-4.0-37 version 2.36.0-3~deb...2022-11-09T15:58:40ZMartin KepplingerNo page is loading after upgrade to libwebkit2gtk-4.0-37 version 2.36.0-3~deb11u1Since the system upgrade installed version 2.36.0-3~deb11u1 of libwebkit2gtk-4.0-37 Gnome Web doesn't load pages anymore and would use 100% of a cpu all the time.
That's today's byzantium.Since the system upgrade installed version 2.36.0-3~deb11u1 of libwebkit2gtk-4.0-37 Gnome Web doesn't load pages anymore and would use 100% of a cpu all the time.
That's today's byzantium.https://source.puri.sm/Librem5/feedbackd/-/issues/62Triggering event with no available feedbacks does not propagate "feedback-end...2022-11-10T12:52:09ZEvangelos Ribeiro TzarasTriggering event with no available feedbacks does not propagate "feedback-ended" signal from fbd to libfeedbackOn my desktop I don't have a vibration motor/LED.
When an event (e.g. `phone-incoming-call`) with `quiet` or `silent` profile level is triggered feedbackd will not find any available feedback (see https://source.puri.sm/Librem5/feedback...On my desktop I don't have a vibration motor/LED.
When an event (e.g. `phone-incoming-call`) with `quiet` or `silent` profile level is triggered feedbackd will not find any available feedback (see https://source.puri.sm/Librem5/feedbackd/-/blob/main/src/fbd-feedback-manager.c#L371-384) and will emit `feedback-ended` on DBus with reason `not-found` (see https://source.puri.sm/Librem5/feedbackd/-/blob/main/src/fbd-feedback-manager.c#L395-397)
```
$ gdbus monitor --session --dest org.sigxcpu.Feedback
Monitoring signals from all objects owned by org.sigxcpu.Feedback
[...]
/org/sigxcpu/Feedback: org.sigxcpu.Feedback.FeedbackEnded (uint32 2, uint32 4294967295)
```
However this signal will not be propagated to `LfbEvent` leaving applications in the dark that it has ended.
As applications might trigger events in a 'fire-and-forget' fashion they might later try to `lfb_event_end_feedback()` resulting in:
```
(feedbackd:112529): fbd-feedback-manager-DEBUG: 19:29:37.274: Ending feedback for event '2'
(feedbackd:112529): fbd-feedback-manager-WARNING **: 19:29:37.274: Tried to end non-existing event 2
```
My current hypothesis is that emitting `lfb_gdbus_feedback_emit_feedback_ended (LFB_GDBUS_FEEDBACK (self), event_id, FBD_EVENT_END_REASON_NOT_FOUND);`
only **after** we complete the handling of the DBus call `lfb_gdbus_feedback_complete_trigger_feedback (object, invocation, event_id);`
would teach `LfbEvent` of the event id before the `feedback-ended` DBus signal comes in making it realize the signal was meant for it instead of ignoring it because the IDs do not match and therefore fixing this issue.https://source.puri.sm/Librem5/linux/-/issues/444Qt's tlwRect.size() reports 16 GByte2022-11-11T12:07:21ZMatthias ApitzQt's tlwRect.size() reports 16 GByteWhile trying to run the app `Stellarium` on the L5, this fails with a message
```
qt.qpa.xcb: xcb_shm_create_segment() can't be called for size 17179344900
```
The maintainer of stellarium reports that this comes out of Qt from `tlwRect....While trying to run the app `Stellarium` on the L5, this fails with a message
```
qt.qpa.xcb: xcb_shm_create_segment() can't be called for size 17179344900
```
The maintainer of stellarium reports that this comes out of Qt from `tlwRect.size() ` in `qwidgetrepaintmanager.cpp` reporting this size of "top-level window". See also the thread https://github.com/Stellarium/stellarium/discussions/2831#https://source.puri.sm/Librem5/librem5-devkit-tools/-/issues/50Add more camera testing scripts or tests2022-11-11T12:10:41ZGuido GuntherAdd more camera testing scripts or tests@martin.kepplinger you have a nice summary at https://source.puri.sm/Librem5/linux/-/merge_requests/430 - can we get those into either the pytests or as interactive tests? We could either dump those into test_scripts or (preferred) make ...@martin.kepplinger you have a nice summary at https://source.puri.sm/Librem5/linux/-/merge_requests/430 - can we get those into either the pytests or as interactive tests? We could either dump those into test_scripts or (preferred) make them interactive and check some basic properties of the raw file?
I can look at that but wanted to check if you have more recent versions or even better tooling?
Having easier debugging tools at a "well known" location would be nice.https://source.puri.sm/Librem5/feedbackd/-/issues/43first release?2022-11-11T12:46:33ZTomasz Kloczkofirst release?Is it possible to make fioirst release which will be tagges just `<version>` string consisting only digits and dots?Is it possible to make fioirst release which will be tagges just `<version>` string consisting only digits and dots?https://source.puri.sm/Librem5/feedbackd/-/issues/59Should async methods notify first, before completing tasks?2022-11-11T12:59:10ZEvangelos Ribeiro TzarasShould async methods notify first, before completing tasks?According to https://gitlab.freedesktop.org/dbus/dbus/-/issues/179, message order is guaranteed.
I ran into this issue in the following pattern:
```
static void
update_ring_state (CallsRinger *self)
{
LfbEventState event_state;
ev...According to https://gitlab.freedesktop.org/dbus/dbus/-/issues/179, message order is guaranteed.
I ran into this issue in the following pattern:
```
static void
update_ring_state (CallsRinger *self)
{
LfbEventState event_state;
event_state = lfb_event_get_state (self->event);
switch (event_state) {
case LFB_EVENT_STATE_ENDED:
set_ring_state (self, CALLS_RING_STATE_INACTIVE);
break;
case LFB_EVENT_STATE_RUNNING:
set_ring_state (self, CALLS_RING_STATE_ACTIVE);
[...]
}
static void
on_event_triggered (LfbEvent *event,
GAsyncResult *res,
CallsRinger *self)
{
g_autoptr (GError) err = NULL;
gboolean ok;
g_return_if_fail (LFB_IS_EVENT (event));
ok = lfb_event_trigger_feedback_finish (event, res, &err);
[...]
update_ring_state (self);
}
```
which will not have updated `LfbEventState` because the state is updated after the `GTask` completes (see https://source.puri.sm/Librem5/feedbackd/-/blob/master/libfeedback/lfb-event.c#L163-172):
```
if (!success) {
g_task_return_error (task, g_steal_pointer (&err));
state = LFB_EVENT_STATE_ERRORED;
} else {
g_task_return_boolean (task, TRUE);
state = LFB_EVENT_STATE_RUNNING;
_lfb_active_add_id (self->id);
}
lfb_event_set_state (self, state);
```https://source.puri.sm/Librem5/libcmatrix/-/issues/10CRITICAL in logs: cm_room_set_status() called with CM_STATUS_UNKNOWN2022-11-14T09:12:18ZEvangelos Ribeiro TzarasCRITICAL in logs: cm_room_set_status() called with CM_STATUS_UNKNOWNI have a couple of rooms in my db which have `UNKNOWN` for the room status resulting in a couple of `cm-room[250190]:CRITICAL: cm_room_set_status: assertion 'status == CM_STATUS_INVITE || status == CM_STATUS_JOIN || status == CM_STATUS_L...I have a couple of rooms in my db which have `UNKNOWN` for the room status resulting in a couple of `cm-room[250190]:CRITICAL: cm_room_set_status: assertion 'status == CM_STATUS_INVITE || status == CM_STATUS_JOIN || status == CM_STATUS_LEAVE' failed`.
```
$ sqlite3 matrix.db "select id, room_name, prev_batch FROM rooms WHERE room_state == 0;" | wc -l
80
```
I've seen that the rest of the `rooms` table is populated correctly (didn't have a closer look at the json though).https://source.puri.sm/Librem5/debs/squeekboard/-/issues/5sm.puri.OSK0.desktop is provided by both squeekboard and librem5-base-defaults2022-11-14T09:56:11ZPirate Praveensm.puri.OSK0.desktop is provided by both squeekboard and librem5-base-defaultsWhen trying to do a dist-upgrade to mobian+bookworm from byzantium it fails with this error (this will be relevant for byzantium to crimson upgrades too). There should be Breaks/Conflicts relation to make the upgrade possible. If possibl...When trying to do a dist-upgrade to mobian+bookworm from byzantium it fails with this error (this will be relevant for byzantium to crimson upgrades too). There should be Breaks/Conflicts relation to make the upgrade possible. If possible having piuparts run the upgrades automatically like in debian (stable to unstable) would be nice for pureos too (when crimson is ready).
```
Preparing to unpack .../42-squeekboard_1.20.0-1_arm64.deb ...
Unpacking squeekboard (1.20.0-1) over (1.19.0-1pureos2) ...
dpkg: error processing archive /tmp/apt-dpkg-install-zcDx2U/42-squeekboard_1.20.0-1_
arm64.deb (--unpack):
trying to overwrite '/usr/share/applications/sm.puri.OSK0.desktop', which is also i
n package librem5-base-defaults 53pureos1
Errors were encountered while processing:
```https://source.puri.sm/Librem5/libcmatrix/-/issues/5cm_db_mark_user_device_change assertion failed2022-11-15T13:04:10ZEvangelos Ribeiro Tzarascm_db_mark_user_device_change assertion failedUsing current !18 (including !23) I just saw `cm-db[777037]:CRITICAL: cm_db_mark_user_device_change: assertion 'users && users->len' failed` in my logs (roughly at the time when element indicated there was another device
I suppose the f...Using current !18 (including !23) I just saw `cm-db[777037]:CRITICAL: cm_db_mark_user_device_change: assertion 'users && users->len' failed` in my logs (roughly at the time when element indicated there was another device
I suppose the fact that element did not show the IP under "from" might be related?
![image](/uploads/c5a6f0c15d87706f63872aa010b7642f/image.png)
Edit: And a couple minutes later the same CRITICAL appeared again.https://source.puri.sm/Librem5/libcmatrix/-/issues/6Attaching a file sometimes (?) does not work correctly2022-11-15T13:04:10ZEvangelos Ribeiro TzarasAttaching a file sometimes (?) does not work correctlyI tried attaching a random file.
Not sure if relevant, but I got
```
cm-room-member[16050]:CRITICAL: cm_room_member_set_json_data: assertion 'CM_IS_ROOM_MEMBER (self)' failed
cm-event[16050]: WARNING: unhandled event type: m.room_key_...I tried attaching a random file.
Not sure if relevant, but I got
```
cm-room-member[16050]:CRITICAL: cm_room_member_set_json_data: assertion 'CM_IS_ROOM_MEMBER (self)' failed
cm-event[16050]: WARNING: unhandled event type: m.room_key_request
```
half a minute before trying to attach a file (not sure if relevant, but wanted to include for completeness sake)
```
chatty-utils[16050]: DEBUG: Attachment Path: /home/purism/Downloads/Luggage-3015868561.pdf
cm-db[16050]:CRITICAL: cm_db_update_user_devices: assertion '(added && added->len) || (removed && removed->len)' failed
cm-olm[16050]:CRITICAL: cm_olm_encrypt: assertion 'CM_IS_OLM (self)' failed
cm-olm[16050]:CRITICAL: cm_olm_get_message_index: assertion 'CM_IS_OLM (self)' failed
cm-olm[16050]:CRITICAL: cm_olm_update_validity: assertion 'CM_IS_OLM (self)' failed
cm-olm[16050]:CRITICAL: cm_olm_save: assertion 'CM_IS_OLM (self)' failed
cm-olm[16050]:CRITICAL: cm_olm_get_session_id: assertion 'CM_IS_OLM (self)' failed
cm-db[16050]:CRITICAL: cm_db_mark_user_device_change: assertion 'users && users->len' failed
cm-db[16050]:CRITICAL: cm_db_mark_user_device_change: assertion 'users && users->len' failed
```
Logged into the same account in element I see:
![image](/uploads/d249a6a862beaba09e4285daa16095d0/image.png)