Librem5 issueshttps://source.puri.sm/groups/Librem5/-/issues2022-01-12T09:59:16Zhttps://source.puri.sm/Librem5/linux/-/issues/374systemd-journald coredumps after resuming from s2idle2022-01-12T09:59:16ZMartin Kepplingersystemd-journald coredumps after resuming from s2idle```
[ 570.823229] systemd-coredump[1732]: Process 299 (systemd-journal) of user 0 dumped core.
[ 570.840744] systemd-coredump[1732]: Coredump diverted to /var/lib/systemd/coredump/core.systemd-journal.0.010f858170514833943a1cb3f976d6cc...```
[ 570.823229] systemd-coredump[1732]: Process 299 (systemd-journal) of user 0 dumped core.
[ 570.840744] systemd-coredump[1732]: Coredump diverted to /var/lib/systemd/coredump/core.systemd-journal.0.010f858170514833943a1cb3f976d6cc.299.1637926495000000.zst
[ 570.858423] systemd-coredump[1732]: Stack trace of thread 299:
[ 570.864666] systemd-coredump[1732]: #0 0x0000aaaad3356b10 n/a (systemd-journald + 0x6b10)
[ 570.875873] systemd-coredump[1732]: #1 0x0000aaaad33600c4 n/a (systemd-journald + 0x100c4)
[ 570.884546] systemd-coredump[1732]: #2 0x0000ffff8486de88 n/a (libsystemd-shared-247.so + 0x1bbe88)
[ 570.893849] systemd-coredump[1732]: #3 0x0000000000000011 n/a (n/a + 0x0)
[ 570.928113] systemd[1]: systemd-journald.service: Main process exited, code=dumped, status=6/ABRT
[ 570.928437] systemd[1]: systemd-journald.service: Failed with result 'watchdog'.
[ 570.929684] systemd[1]: systemd-journald.service: Consumed 1.408s CPU time.
[ 570.934035] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1.
[ 570.945383] systemd[1]: Stopping Flush Journal to Persistent Storage...
[ 570.966507] systemd[1]: systemd-journal-flush.service: Succeeded.
[ 570.967474] systemd[1]: Stopped Flush Journal to Persistent Storage.
[ 570.968915] systemd[1]: Stopped Journal Service.
[ 570.969114] systemd[1]: systemd-journald.service: Consumed 1.408s CPU time.
[ 570.976633] systemd[1]: Starting Journal Service...
[ 571.103759] systemd[1]: Started Journal Service.
[ 571.133979] systemd-journald[1762]: Received client request to flush runtime journal.
```
this could be
https://github.com/systemd/systemd/issues/9538 and the discussion linked there: https://bugzilla.kernel.org/show_bug.cgi?id=200595
so this should go away when switching to suspend to ram / deep sleep.https://source.puri.sm/Librem5/debs/gnome-calendar/-/issues/7Tag a first release?2021-10-25T17:02:22ZGuido GuntherTag a first release?There's no `pureos/<version>` tag yet so git based builders won't pick it up.There's no `pureos/<version>` tag yet so git based builders won't pick it up.https://source.puri.sm/Librem5/debs/gnss-share/-/issues/1Takes 15 sec to disable on shutdown/reboot2022-02-11T10:29:16ZJoao AzevedoTakes 15 sec to disable on shutdown/rebootWhen you reboot or shutdown the Librem 5, `gnss-share` service takes about 15 to 20 seconds to stop, which adds 15 to 20 seconds time to any reboot or shutdown process.When you reboot or shutdown the Librem 5, `gnss-share` service takes about 15 to 20 seconds to stop, which adds 15 to 20 seconds time to any reboot or shutdown process.https://source.puri.sm/Librem5/millipixels/-/issues/65Taking photos with the back camera on the Librem 5 does not work on postmarketOS2023-05-09T18:02:47ZNewbyteTaking photos with the back camera on the Librem 5 does not work on postmarketOSIn postmarketOS, taking photos with the back camera on the Librem 5 does not work. The viewfinder works and gives you a view of what the camera sees, but once you hit the button to take a photo the viewfinder hangs and the photo processi...In postmarketOS, taking photos with the back camera on the Librem 5 does not work. The viewfinder works and gives you a view of what the camera sees, but once you hit the button to take a photo the viewfinder hangs and the photo processing spinner spins indefinitely. This is with Millipixels 0.20.0 and Linux 6.1.10, but it can also be reproduced with our build of Linux 6.1.8. Notably, the front camera works fine. Unlike https://source.puri.sm/Librem5/linux/-/issues/458, this can be reproduced right away after a reboot.
Downstream issue: https://gitlab.com/postmarketOS/pmaports/-/issues/1947https://source.puri.sm/Librem5/linux/-/issues/309taking picture with selfie cam just hangs2021-05-14T11:02:19ZGuido Gunthertaking picture with selfie cam just hangsPreview works but hitting taking an image just shows the spinner endlessly.
This is on the byzantium version with `5.11.15pureos1`. I deliberately did no debugging since the question was if we want to ship it.Preview works but hitting taking an image just shows the spinner endlessly.
This is on the byzantium version with `5.11.15pureos1`. I deliberately did no debugging since the question was if we want to ship it.https://source.puri.sm/Librem5/millipixels/-/issues/1taking picture with selfie cam just hangs2021-04-26T13:30:10ZGuido Gunthertaking picture with selfie cam just hangsPreview works but hitting taking an image just shows the spinner and endlessy.
This is on the byzantium version with `5.11.15pureos1`. I deliberately did no debugging since the question was if we want to ship it.Preview works but hitting taking an image just shows the spinner and endlessy.
This is on the byzantium version with `5.11.15pureos1`. I deliberately did no debugging since the question was if we want to ship it.https://source.puri.sm/Librem5/OS-issues/-/issues/225TECHGEAR Active Strike Pro Bluetooth keyboard - wrong char mappings2021-10-15T12:17:57ZMatthias ApitzTECHGEAR Active Strike Pro Bluetooth keyboard - wrong char mappings
I use a `TECHGEAR Active Strike Pro` BT keyboard which paires fine with my L5 and my Ubuntu mobile phone BQ E4.5, but the key layout does not work on the L5, mostly for upper case chars. I have here what the both devices give when typin...
I use a `TECHGEAR Active Strike Pro` BT keyboard which paires fine with my L5 and my Ubuntu mobile phone BQ E4.5, but the key layout does not work on the L5, mostly for upper case chars. I have here what the both devices give when typing the upper row of physical keys with SHIFT:
```
BQ device: ! " £ $ % ^ & * ( ) _ +
L5 device: ! " # $ % & / ( ) = ? ¡
```
With the Ubuntu devices it gives as chars what is printed on the physical keys.
I investigated a bit:
I used the X11 tool `xev` to sniff what the keys are generating, here only for the physical key which is labeled with `=` (lowercase) and `+` (uppercase):
```
DISPLAY=:0 xev | tee -a xev.out
```
This gives for the key `=` / `+`:
```
KeyPress event, serial 35, synthetic NO, window 0x800001,
root 0x512, subw 0x800002, time 230474, (39,35), root:(39,67),
state 0x0, keycode 21 (keysym 0xbf, questiondown), same_screen YES,
XLookupString gives 2 bytes: (c2 bf) "¿"
XmbLookupString gives 2 bytes: (c2 bf) "¿"
XFilterEvent returns: False
```
and together with SHIFT:
```
KeyPress event, serial 35, synthetic NO, window 0x800001,
root 0x512, subw 0x800002, time 269343, (39,35), root:(39,67),
state 0x1, keycode 21 (keysym 0xa1, exclamdown), same_screen YES,
XLookupString gives 2 bytes: (c2 a1) "¡"
XmbLookupString gives 2 bytes: (c2 a1) "¡"
XFilterEvent returns: False
```
If I now run:
```
DISPLAY=:0 xmodmap -e "keycode 21 = equal plus"
```
it gives:
```
KeyPress event, serial 32, synthetic NO, window 0x800001,
root 0x512, subw 0x800002, time 348519, (39,35), root:(39,67),
state 0x0, keycode 21 (keysym 0x3d, equal), same_screen YES,
XLookupString gives 1 bytes: (3d) "="
XmbLookupString gives 1 bytes: (3d) "="
XFilterEvent returns: False
```
and togethet with SHIFT
```
KeyPress event, serial 35, synthetic NO, window 0x800001,
root 0x512, subw 0x800002, time 376107, (39,35), root:(39,67),
state 0x1, keycode 21 (keysym 0x2b, plus), same_screen YES,
XKeysymToKeycode returns keycode: 35
XLookupString gives 1 bytes: (2b) "+"
XmbLookupString gives 1 bytes: (2b) "+"
XFilterEvent returns: False
```
i.e. the physical key gives what it has as labels on it. Ofc, this works only in any X11 application, for example, I tested the (new installed) xterm, but not in the terminal app of the L5.
So, the question (or bug) is: where in Debian / PureOS is the mapping of such BT keyboard (wrong)defined?https://source.puri.sm/Librem5/linux/-/issues/363TECHGEAR Active Strike Pro Bluetooth keyboard - wrong char mappings2021-10-14T13:47:25ZMatthias ApitzTECHGEAR Active Strike Pro Bluetooth keyboard - wrong char mappings
I use a `TECHGEAR Active Strike Pro` BT keyboard which paires fine with my L5 and my Ubuntu mobile phone BQ E4.5, but the key layout does not work on the L5, mostly for upper case chars. I have here what the both devices give when typin...
I use a `TECHGEAR Active Strike Pro` BT keyboard which paires fine with my L5 and my Ubuntu mobile phone BQ E4.5, but the key layout does not work on the L5, mostly for upper case chars. I have here what the both devices give when typing the upper row of physical keys with SHIFT:
```
BQ device: ! " £ $ % ^ & * ( ) _ +
L5 device: ! " # $ % & / ( ) = ? ¡
```
With the Ubuntu devices it gives as chars what is printed on the physical keys.
I investigated a bit:
I used the X11 tool `xev` to sniff what the keys are generating, here only for the physical key which is labeled with `=` (lowercase) and `+` (uppercase):
```
DISPLAY=:0 xev | tee -a xev.out
```
This gives for the key `=` / `+`:
```
KeyPress event, serial 35, synthetic NO, window 0x800001,
root 0x512, subw 0x800002, time 230474, (39,35), root:(39,67),
state 0x0, keycode 21 (keysym 0xbf, questiondown), same_screen YES,
XLookupString gives 2 bytes: (c2 bf) "¿"
XmbLookupString gives 2 bytes: (c2 bf) "¿"
XFilterEvent returns: False
```
and together with SHIFT:
```
KeyPress event, serial 35, synthetic NO, window 0x800001,
root 0x512, subw 0x800002, time 269343, (39,35), root:(39,67),
state 0x1, keycode 21 (keysym 0xa1, exclamdown), same_screen YES,
XLookupString gives 2 bytes: (c2 a1) "¡"
XmbLookupString gives 2 bytes: (c2 a1) "¡"
XFilterEvent returns: False
```
If I now run:
```
DISPLAY=:0 xmodmap -e "keycode 21 = equal plus"
```
it gives:
```
KeyPress event, serial 32, synthetic NO, window 0x800001,
root 0x512, subw 0x800002, time 348519, (39,35), root:(39,67),
state 0x0, keycode 21 (keysym 0x3d, equal), same_screen YES,
XLookupString gives 1 bytes: (3d) "="
XmbLookupString gives 1 bytes: (3d) "="
XFilterEvent returns: False
```
and togethet with SHIFT
```
KeyPress event, serial 35, synthetic NO, window 0x800001,
root 0x512, subw 0x800002, time 376107, (39,35), root:(39,67),
state 0x1, keycode 21 (keysym 0x2b, plus), same_screen YES,
XKeysymToKeycode returns keycode: 35
XLookupString gives 1 bytes: (2b) "+"
XmbLookupString gives 1 bytes: (2b) "+"
XFilterEvent returns: False
```
i.e. the physical key gives what it has as labels on it. Ofc, this works only in any X11 application, for example, I tested the (new installed) xterm, but not in the terminal app of the L5.
So, the question (or bug) is: where in Debian / PureOS is the mapping of such BT keyboard (wrong)defined?https://source.puri.sm/Librem5/OS-issues/-/issues/243Telegram-deskop will not sign in due to old version (2.6)2021-12-29T22:18:42ZChris TalbotTelegram-deskop will not sign in due to old version (2.6)PureOS Byzantium has version Telegram-desktop 2.6, which Telegram considers "Old". Telegram will not allow it to sign in due to this.
Please update Telegram-Desktop to 3.1. Debian has it backported for Bullseye (which I think Byzantium ...PureOS Byzantium has version Telegram-desktop 2.6, which Telegram considers "Old". Telegram will not allow it to sign in due to this.
Please update Telegram-Desktop to 3.1. Debian has it backported for Bullseye (which I think Byzantium targets).https://source.puri.sm/Librem5/gnome-control-center/-/issues/43temporarily limit pin to 6 numers2019-10-23T15:24:35ZGuido Gunthertemporarily limit pin to 6 numersjust until we landed the @julian.sparber 's lockscreen changesjust until we landed the @julian.sparber 's lockscreen changeshttps://source.puri.sm/Librem5/Apps_Issues/-/issues/26Terminal2018-05-29T15:58:06ZAdrien PlazasTerminalWe need a terminal application for the phone.We need a terminal application for the phone.https://source.puri.sm/Librem5/Apps_Issues/-/issues/183Terminal 'search' button does nothing2020-01-13T09:13:37ZTodd WeaverTerminal 'search' button does nothing# What application is this relating to?
Terminal (King's Cross)
# What problem did you encounter
A Search button, that does nothing
## What is the actual behaviour?
Search button does nothing
## What is the expected behaviour?
No ...# What application is this relating to?
Terminal (King's Cross)
# What problem did you encounter
A Search button, that does nothing
## What is the actual behaviour?
Search button does nothing
## What is the expected behaviour?
No search button? or have it do something?
## How to reproduce
1. Open terminal
2. Click Search
3. Type something
4. It does nothing
![purism-librem-5-chestnut-terminal-search-2020-02-12](/uploads/600c88119dd7ab4b31547eea871be235/purism-librem-5-chestnut-terminal-search-2020-02-12.jpeg)
# Which version did you encounter the bug in?
```
purism@pureos:~$ uname -a
Linux pureos 5.3.0-librem5-h1 #1 SMP PREEMPT Tue Jan 7 10:16:00 CET 2020 aarch64 GNU/Linux
purism@pureos:~$ dpkg -s phosh | grep Version
Version: 0.1.6
purism@pureos:~$ dpkg -s kgx | grep Version
Version: 0.2.1pureos+librem5.1
purism@pureos:~$
```
# What hardware are you running on?
- Librem 5 Chestnuthttps://source.puri.sm/Librem5/Apps_Issues/-/issues/182Terminal Keyboard Shortcut overflow2020-01-13T09:12:32ZTodd WeaverTerminal Keyboard Shortcut overflowSee https://source.puri.sm/Librem5/OS-issues/issues/117See https://source.puri.sm/Librem5/OS-issues/issues/117https://source.puri.sm/Librem5/image-builder/-/issues/10Terminal will not start2018-07-26T11:12:57ZHeather EllsworthTerminal will not startThe issue is that the terminal icons do not start a terminal. I've verified that this issue exists on the most recent green build on jenkins (build 211), build 201, and a local build from commit 5ad1bea.
When I open the favorites menu, ...The issue is that the terminal icons do not start a terminal. I've verified that this issue exists on the most recent green build on jenkins (build 211), build 201, and a local build from commit 5ad1bea.
When I open the favorites menu, I see these logs in journalctl:
```
Jul 11 21:34:59 pureos rootston[386]: 2018-07-11 21:34:59 - [types/wlr_surface.c:614] New wlr_surface 0x55e61d19e140 (res 0x55e61d2ffbb0)
Jul 11 21:34:59 pureos rootston[386]: 2018-07-11 21:34:59 - [types/xdg_shell/wlr_xdg_surface.c:402] new xdg_surface 0x55e61c6830c0 (res 0x55e61d1a6980)
Jul 11 21:34:59 pureos rootston[386]: 2018-07-11 21:34:59 - [rootston/xdg_shell.c:401] new xdg popup
```
Then when I click either of the two terminal icons, I get these logs:
```
Jul 11 21:35:06 pureos rootston[386]: 2018-07-11 21:35:06 - [types/wlr_surface.c:614] New wlr_surface 0x55e61cd0c0f0 (res 0x55e61d1824f0)
Jul 11 21:35:06 pureos rootston[386]: 2018-07-11 21:35:06 - [types/wlr_surface.c:614] New wlr_surface 0x55e61d1bd2a0 (res 0x55e61c6951d0)
Jul 11 21:35:06 pureos dbus-daemon[437]: [session uid=1000 pid=437] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.3' (uid=1000 pid=499 comm="gnom
e-terminal ")
Jul 11 21:35:06 pureos systemd[400]: Starting GNOME Terminal Server...
Jul 11 21:35:06 pureos gnome-terminal-server[505]: Non UTF-8 locale (ANSI_X3.4-1968) is not supported!
Jul 11 21:35:06 pureos systemd[400]: gnome-terminal-server.service: Main process exited, code=exited, status=8/n/a
Jul 11 21:35:06 pureos systemd[400]: gnome-terminal-server.service: Failed with result 'exit-code'.
Jul 11 21:35:06 pureos systemd[400]: Failed to start GNOME Terminal Server.
Jul 11 21:35:08 pureos rootston[386]: 2018-07-11 21:35:08 - [types/wlr_output.c:763] Falling back to software cursor
```
Then some 25s later, I see this timeout:
```
Jul 11 21:35:30 pureos rootston[386]: 2018-07-11 21:35:30 - [types/wlr_output.c:763] Falling back to software cursor
Jul 11 21:35:30 pureos rootston[386]: 2018-07-11 21:35:30 - [types/wlr_surface.c:614] New wlr_surface 0x55e61d37b9d0 (res 0x55e61d1a4180)
Jul 11 21:35:30 pureos rootston[386]: 2018-07-11 21:35:30 - [types/xdg_shell/wlr_xdg_surface.c:402] new xdg_surface 0x55e61d38e0e0 (res 0x55e61d1a6bc0)
Jul 11 21:35:30 pureos rootston[386]: 2018-07-11 21:35:30 - [rootston/xdg_shell.c:401] new xdg popup
Jul 11 21:35:31 pureos rootston[386]: # Compositor prefers decoration mode 'client'
Jul 11 21:35:31 pureos rootston[386]: # Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
Jul 11 21:35:31 pureos rootston[386]: # Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached
Jul 11 21:35:37 pureos phosh[434]: Could not launch terminal
Jul 11 21:35:41 pureos rootston[386]: 2018-07-11 21:35:41 - [types/wlr_output.c:763] Falling back to software cursor
```https://source.puri.sm/Librem5/feedbackd/-/issues/69Test failure with GLib 2.76.02023-03-17T16:47:23ZJan TojnarTest failure with GLib 2.76.0After updating to GLib 2.76.0, lfb-integration test crashes:
```
6/6 lfb-integration FAIL 0.18s killed by signal 6 SIGABRT
>>> G_TEST_BUILDDIR=/build/source/build/tests XDG_CONFIG_DIRS=/build/source/tests MALLOC...After updating to GLib 2.76.0, lfb-integration test crashes:
```
6/6 lfb-integration FAIL 0.18s killed by signal 6 SIGABRT
>>> G_TEST_BUILDDIR=/build/source/build/tests XDG_CONFIG_DIRS=/build/source/tests MALLOC_CHECK_=2 G_DEBUG=gc-friendly,fatal-warnings G_TEST_SRCDIR=/build/source/tests XDG_CONFIG_HOME=/build/source/tests/data/user-config MALLOC_PERTURB_=87 PYTHONDONTWRITEBYTECODE=yes GSETTINGS_BACKEND=memory GSETTINGS_SCHEMA_DIR=/build/source/build/data LD_LIBRARY_PATH=/build/source/build/libfeedback /build/source/build/tests/test-lfb-integration
✀
stdout:
TAP version 13
# random seed: R02Sb7716a918269f3c28d16d71a57ea01de
1..6
# Start of feedbackd tests
# Start of lfb-integration tests
# GLib-GIO-DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
not ok /feedbackd/lfb-integration/event_sync - ERROR:../tests/test-lfb-integration.c:87:test_lfb_integration_event_sync: assertion failed (err == NULL): GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying (g-dbus-error-quark, 4)
Bail out!
stderr:
dbus-daemon[857]: [session uid=1000 pid=857] Activating service name='org.sigxcpu.Feedback' requested by ':1.0' (uid=1000 pid=850 comm="/build/source/build/tests/test-lfb-integration" label="kernel")
+ exec /build/source/build/src/feedbackd
dbus-daemon[857]: [session uid=1000 pid=857] Successfully activated service 'org.sigxcpu.Feedback'
0# (anonymous namespace)::segabort_handler(int) in /nix/store/ckgi9ql2xm627afl9fh529hg2vbgfn0r-libsegfault-unstable-2022-11-13/lib/libsegfault.so
1# 0x00007FFFF783DBF0 in /nix/store/76l4v99sk83ylfwkz8wmwrm4s8h73rhd-glibc-2.35-224/lib/libc.so.6
2# fbd_event_run_feedbacks at ../src/fbd-event.c:397
3# fbd_feedback_manager_handle_trigger_feedback at ../src/fbd-feedback-manager.c:402
4# ffi_call_unix64 in /nix/store/m0fsvgc5hrn3yjwsl9fvj5m6pyjk2il2-libffi-3.4.4/lib/libffi.so.8
5# ffi_call_int in /nix/store/m0fsvgc5hrn3yjwsl9fvj5m6pyjk2il2-libffi-3.4.4/lib/libffi.so.8
6# ffi_call in /nix/store/m0fsvgc5hrn3yjwsl9fvj5m6pyjk2il2-libffi-3.4.4/lib/libffi.so.8
7# g_cclosure_marshal_generic in /nix/store/bd9wr9186mk3wzxiww1rk7a3maaqgn8h-glib-2.74.5/lib/libgobject-2.0.so.0
8# g_closure_invoke in /nix/store/bd9wr9186mk3wzxiww1rk7a3maaqgn8h-glib-2.74.5/lib/libgobject-2.0.so.0
9# signal_emit_unlocked_R.isra.0 in /nix/store/bd9wr9186mk3wzxiww1rk7a3maaqgn8h-glib-2.74.5/lib/libgobject-2.0.so.0
10# _lfb_gdbus_feedback_skeleton_handle_method_call at data/lfb-gdbus.c:1328
11# g_dbus_interface_method_dispatch_helper in /nix/store/bd9wr9186mk3wzxiww1rk7a3maaqgn8h-glib-2.74.5/lib/libgio-2.0.so.0
12# call_in_idle_cb in /nix/store/bd9wr9186mk3wzxiww1rk7a3maaqgn8h-glib-2.74.5/lib/libgio-2.0.so.0
13# g_main_context_dispatch in /nix/store/bd9wr9186mk3wzxiww1rk7a3maaqgn8h-glib-2.74.5/lib/libglib-2.0.so.0
14# g_main_context_iterate.constprop.0 in /nix/store/bd9wr9186mk3wzxiww1rk7a3maaqgn8h-glib-2.74.5/lib/libglib-2.0.so.0
15# g_main_loop_run in /nix/store/bd9wr9186mk3wzxiww1rk7a3maaqgn8h-glib-2.74.5/lib/libglib-2.0.so.0
16# main at ../src/fbd.c:123
17# __libc_start_call_main in /nix/store/76l4v99sk83ylfwkz8wmwrm4s8h73rhd-glibc-2.35-224/lib/libc.so.6
18# __libc_start_main_impl in /nix/store/76l4v99sk83ylfwkz8wmwrm4s8h73rhd-glibc-2.35-224/lib/libc.so.6
19# _start in /build/source/build/src/feedbackd
**
ERROR:../tests/test-lfb-integration.c:87:test_lfb_integration_event_sync: assertion failed (err == NULL): GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying (g-dbus-error-quark, 4)
0# (anonymous namespace)::segabort_handler(int) in /nix/store/ckgi9ql2xm627afl9fh529hg2vbgfn0r-libsegfault-unstable-2022-11-13/lib/libsegfault.so
1# 0x00007FFFF7A3DBF0 in /nix/store/76l4v99sk83ylfwkz8wmwrm4s8h73rhd-glibc-2.35-224/lib/libc.so.6
2# __pthread_kill_implementation in /nix/store/76l4v99sk83ylfwkz8wmwrm4s8h73rhd-glibc-2.35-224/lib/libc.so.6
3# gsignal in /nix/store/76l4v99sk83ylfwkz8wmwrm4s8h73rhd-glibc-2.35-224/lib/libc.so.6
4# abort in /nix/store/76l4v99sk83ylfwkz8wmwrm4s8h73rhd-glibc-2.35-224/lib/libc.so.6
5# g_assertion_message_expr.cold in /nix/store/bd9wr9186mk3wzxiww1rk7a3maaqgn8h-glib-2.74.5/lib/libglib-2.0.so.0
6# g_assertion_message_error in /nix/store/bd9wr9186mk3wzxiww1rk7a3maaqgn8h-glib-2.74.5/lib/libglib-2.0.so.0
7# test_lfb_integration_event_sync at ../tests/test-lfb-integration.c:87
8# g_test_run_suite_internal in /nix/store/bd9wr9186mk3wzxiww1rk7a3maaqgn8h-glib-2.74.5/lib/libglib-2.0.so.0
9# g_test_run_suite_internal in /nix/store/bd9wr9186mk3wzxiww1rk7a3maaqgn8h-glib-2.74.5/lib/libglib-2.0.so.0
10# g_test_run_suite_internal in /nix/store/bd9wr9186mk3wzxiww1rk7a3maaqgn8h-glib-2.74.5/lib/libglib-2.0.so.0
11# g_test_run_suite in /nix/store/bd9wr9186mk3wzxiww1rk7a3maaqgn8h-glib-2.74.5/lib/libglib-2.0.so.0
12# g_test_run in /nix/store/bd9wr9186mk3wzxiww1rk7a3maaqgn8h-glib-2.74.5/lib/libglib-2.0.so.0
13# main at ../tests/test-lfb-integration.c:369
14# __libc_start_call_main in /nix/store/76l4v99sk83ylfwkz8wmwrm4s8h73rhd-glibc-2.35-224/lib/libc.so.6
15# __libc_start_main_impl in /nix/store/76l4v99sk83ylfwkz8wmwrm4s8h73rhd-glibc-2.35-224/lib/libc.so.6
16# _start in /build/source/build/tests/test-lfb-integration
cleaning up pid 857
```
I have bisected this to https://gitlab.gnome.org/GNOME/glib/commit/45b5a6c1e56d5b73cc5ed798ef59a5601e56c170, the removal of slice allocator.
Also opened an issue against GLib: https://gitlab.gnome.org/GNOME/glib/-/issues/2937https://source.puri.sm/Librem5/Apps_Issues/-/issues/103Test Fractal2019-06-11T16:00:38ZHeather EllsworthTest FractalEpic: https://source.puri.sm/Librem5/use-cases/issues/82
The state of Fractal on the devkit should be tested to identify areas still needing work to get a better understanding of the state of the app. To consider this feature done, a Fr...Epic: https://source.puri.sm/Librem5/use-cases/issues/82
The state of Fractal on the devkit should be tested to identify areas still needing work to get a better understanding of the state of the app. To consider this feature done, a Fractal flatpak should be built, installed, and tested for matching [the design](https://gitlab.gnome.org/Teams/Design/app-mockups/tree/master/fractal) as well as overall functionality.Past: Edelweiss (W22-24)https://source.puri.sm/Librem5/debs/gtk/-/issues/12Test suite failures2020-10-07T16:27:31ZGuido GuntherTest suite failuresWe currently fail to build on pureos proper (laneakia) because the tests fail right away:
https://master.pureos.net/raw/logs/0c/0c814eb7-bb8c-448b-9680-cc986a47f0bb.log
We did not notice earlier because tests are skipped on arm01. Two ...We currently fail to build on pureos proper (laneakia) because the tests fail right away:
https://master.pureos.net/raw/logs/0c/0c814eb7-bb8c-448b-9680-cc986a47f0bb.log
We did not notice earlier because tests are skipped on arm01. Two options:
- disabling all tests in `debian/rules`
- disabling the failing ref tests
```
$ grep 'expected contents' 0c814eb7-bb8c-448b-9680-cc986a47f0bb.log
/srv/build/gtk+3.0-3.24.8+1+gita67b143/testsuite/a11y/about.ui: Contents don't match expected contents:
/srv/build/gtk+3.0-3.24.8+1+gita67b143/testsuite/a11y/infobar.ui: Contents don't match expected contents:
/srv/build/gtk+3.0-3.24.8+1+gita67b143/testsuite/a11y/messagedialog.ui: Contents don't match expected contents:
```
- fixing the failing reftests
the 2. option looks like the best short term solution to me - @adrien.plazas could you have a look? There seems to already be a simple way to disable failing reftests: https://source.puri.sm/Librem5/gtk/blob/pureos/sloppy/debian%2Frules#L181
Merging will https://source.puri.sm/Librem5/deb-build-jobs/merge_requests/125 enable tests for gtk.
/cc @arno.bauernoppel since he looks into pureos migrations as well.https://source.puri.sm/Librem5/quickstart-guide/-/issues/23Text fixes2020-10-29T16:46:39ZDavid BoddieText fixesFrom Matrix chat:
```
s/apples/applies/
s/The Warranty Period for Physical Goods purchased from Purism, SPC is one year from the date of purchase./The Warranty Period for Physical Goods purchased from Purism, SPC is one year from the dat...From Matrix chat:
```
s/apples/applies/
s/The Warranty Period for Physical Goods purchased from Purism, SPC is one year from the date of purchase./The Warranty Period for Physical Goods purchased from Purism, SPC is one year from the date of shipment./
s/The nano-SIM card is supplied by your mobile network
provider./The nano-SIM card is supplied by your mobile network
provider or included as part of Librem AweSIM from Purism./
```David BoddieDavid Boddiehttps://source.puri.sm/Librem5/virtboard/-/issues/22Text prediction2019-07-15T16:39:56ZGuido GuntherText predictionOn such a small screen text prediction is an important feature so one has to type less.
(mostly we have a bug to track this, I'll leave details like self learning, editing dictionary, etc. as details for later).On such a small screen text prediction is an important feature so one has to type less.
(mostly we have a bug to track this, I'll leave details like self learning, editing dictionary, etc. as details for later).https://source.puri.sm/Librem5/debs/ModemManager/-/issues/26The Call object gets incorrectly terminated2020-02-06T08:51:53ZSebastian KrzyszkowiakThe Call object gets incorrectly terminatedWith BM818, libqmi 1.24.2 and MM 1.12.2:
```
ModemManager[3309]: <debug> [1579324133.242462] Added call at '/org/freedesktop/ModemManager1/Call/3'
ModemManager[3309]: <info> [1579324133.270003] user request to start call
ModemManager[3...With BM818, libqmi 1.24.2 and MM 1.12.2:
```
ModemManager[3309]: <debug> [1579324133.242462] Added call at '/org/freedesktop/ModemManager1/Call/3'
ModemManager[3309]: <info> [1579324133.270003] user request to start call
ModemManager[3309]: <debug> [1579324133.270156] voice call to 666666666 allowed
ModemManager[3309]: <info> [1579324133.270204] Call state changed: unknown -> dialing (outgoing-started)
ModemManager[3309]: <debug> [1579324133.270485] (ttyUSB1) device open count is 2 (open)
ModemManager[3309]: <debug> [1579324133.270835] Setting up in-call state...
ModemManager[3309]: <debug> [1579324133.270887] Setting up in-call ports context
ModemManager[3309]: <debug> [1579324133.270928] (ttyUSB1) device open count is 3 (open)
ModemManager[3309]: <debug> [1579324133.270995] (ttyUSB1) Setting voice in-call unsolicited events handlers
ModemManager[3309]: <debug> [1579324133.271047] (ttyUSB1): --> 'ATD666666666;<CR>'
ModemManager[3309]: <debug> [1579324133.271154] modem is now in-call state
ModemManager[3309]: <debug> [1579324133.773429] (ttyUSB1): <-- '<CR><LF>OK<CR><LF>'
ModemManager[3309]: <info> [1579324133.773739] call is started
ModemManager[3309]: <debug> [1579324133.773992] (ttyUSB1) device open count is 2 (close)
ModemManager[3309]: <debug> [1579324134.028806] (ttyUSB2): <-- '<CR><LF>^MODE: 5<CR><LF>'
ModemManager[3309]: <debug> [1579324135.053260] (ttyUSB0): <-- 60 42 00 46 26 a7 28 87 dc aa 51 eb 00 03 46 26 84 a6 b0 dc aa 51 eb 00 04 46 26 de 32 d7 dc aa 51 eb 00 07 46 26 6d 2c e7 dc aa 51 eb 00 01 46 26 01 9b f0 dc aa 51 eb 00 05 46 26 94 5b 92 dd aa 51 eb 00 00 21 48 7e
ModemManager[3309]: <debug> [1579324135.464032] 1 calls being established: call list polling required
ModemManager[3309]: <debug> [1579324135.464186] (ttyUSB1) device open count is 3 (open)
ModemManager[3309]: <debug> [1579324135.464323] (ttyUSB1): --> 'AT+CLCC<CR>'
ModemManager[3309]: <debug> [1579324135.467297] (ttyUSB2): <-- '<CR><LF>RING_BACK<CR><LF>'
ModemManager[3309]: <debug> [1579324135.820692] (ttyUSB1): <-- '<CR><LF>+CLCC: 1,1,0,1,0,"",128<CR><LF>+CLCC: 2,0,3,0,0,"666666666",129<CR><LF><CR><LF>OK<CR><LF>'
ModemManager[3309]: <debug> [1579324135.821149] Reported 2 ongoing calls
ModemManager[3309]: <debug> [1579324135.821227] call at index 1: direction incoming, state active, number n/a
ModemManager[3309]: <debug> [1579324135.821291] call at index 2: direction outgoing, state ringing-out, number 666666666
ModemManager[3309]: <info> [1579324135.821373] Call state changed: dialing -> terminated (unknown)
ModemManager[3309]: <warn> [1579324135.821752] unexpected incoming call to number 'n/a' reported in call list: state active
ModemManager[3309]: <warn> [1579324135.821822] unexpected outgoing call to number '666666666' reported in call list: state ringing-out
ModemManager[3309]: <debug> [1579324135.821900] (ttyUSB1) device open count is 2 (close)
ModemManager[3309]: <debug> [1579324135.822287] Cleaning up in-call state...
ModemManager[3309]: <debug> [1579324135.822359] Cleaning up in-call ports context
ModemManager[3309]: <debug> [1579324135.822447] (ttyUSB1) Removing voice in-call unsolicited events handlers
ModemManager[3309]: <debug> [1579324135.822511] (ttyUSB1) device open count is 1 (close)
ModemManager[3309]: <debug> [1579324135.822626] modem is no longer in-call state
ModemManager[3309]: <debug> [1579324135.841418] Deleted call at '/org/freedesktop/ModemManager1/Call/3'
ModemManager[3309]: <debug> [1579324138.467086] no calls being established: call list polling stopped
```
The connection is initiated anyway and the other party's phone starts to ring.
When the other party rejects the call, log shows:
```
ModemManager[3309]: <debug> [1579324149.133263] (ttyUSB2): <-- '<CR><LF>+DISC: 4,0,0,17,"666666666",129<CR><LF><CR><LF><CR><CR><LF>BUSY<CR><CR><LF><CR><LF>'
ModemManager[3309]: <debug> [1579324149.133627] Got failure code 1: No carrier
```
The difference with a working state appears to be this part:
**working**
```
ModemManager[3309]: <debug> [1579324072.845185] Reported 2 ongoing calls
ModemManager[3309]: <debug> [1579324072.845263] call at index 1: direction incoming, state active, number n/a
ModemManager[3309]: <debug> [1579324072.845326] call at index 2: direction outgoing, state dialing, number 666666666
ModemManager[3309]: <debug> [1579324072.845419] call info matched (matched direction/state yes, matched index no, matched terminated no) with call at '/org/freedesktop/ModemManager1/Call/2'
ModemManager[3309]: <debug> [1579324072.845482] index set: 2
```
**non-working** (skips the "dialing" state and goes directly to "ringing-out"):
```
ModemManager[3309]: <debug> [1579324135.821149] Reported 2 ongoing calls
ModemManager[3309]: <debug> [1579324135.821227] call at index 1: direction incoming, state active, number n/a
ModemManager[3309]: <debug> [1579324135.821291] call at index 2: direction outgoing, state ringing-out, number 666666666
ModemManager[3309]: <info> [1579324135.821373] Call state changed: dialing -> terminated (unknown)
ModemManager[3309]: <warn> [1579324135.821752] unexpected incoming call to number 'n/a' reported in call list: state active
ModemManager[3309]: <warn> [1579324135.821822] unexpected outgoing call to number '666666666' reported in call list: state ringing-out
```
It doesn't happen all the time, but doesn't seem hard to trigger either.