Librem5 issueshttps://source.puri.sm/groups/Librem5/-/issues2022-11-29T15:14:54Zhttps://source.puri.sm/Librem5/libcmatrix/-/issues/13events may appear more than once2022-11-29T15:14:54ZMohammed Sadiqevents may appear more than onceIt's seems some people are having issues that every event are being shown twice. I was not able to reproduce the issue at all. Filing the issue anyway so as to not forgetIt's seems some people are having issues that every event are being shown twice. I was not able to reproduce the issue at all. Filing the issue anyway so as to not forgethttps://source.puri.sm/Librem5/libcmatrix/-/issues/11libcmatrix may fail to load/save sessions2023-01-04T11:16:37ZMohammed Sadiqlibcmatrix may fail to load/save sessionsVery occasionally libcmatrix fails to save/load session secret. It did happen to me only once, and I'm not able to reproduce the bug. But in such a case, libcmatrix creates a new login leaving encrypted messages no longer available, whic...Very occasionally libcmatrix fails to save/load session secret. It did happen to me only once, and I'm not able to reproduce the bug. But in such a case, libcmatrix creates a new login leaving encrypted messages no longer available, which is not good.
If anyone can reproduce the bug, please let me know the steps to do so.https://source.puri.sm/Librem5/Apps_Issues/-/issues/205gnome-maps: Navigation side bar not adaptive2021-07-10T10:39:57ZGuido Gunthergnome-maps: Navigation side bar not adaptivethis is the byzantium verison, need to check upstream so filing it here for the moment.this is the byzantium verison, need to check upstream so filing it here for the moment.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/177Outdated documentation for plasma mobile on librem 52021-01-13T14:07:30ZGeorge AndreouOutdated documentation for plasma mobile on librem 5I was trying to install Plasma Mobile on Librem 5 (Dogwood) using documentation in https://developer.puri.sm/Librem5/Development_Environment/Boards/HowTo/Install_Plasma_Mobile.html#devkit-howto-install-plasma-mobile.
However when running...I was trying to install Plasma Mobile on Librem 5 (Dogwood) using documentation in https://developer.puri.sm/Librem5/Development_Environment/Boards/HowTo/Install_Plasma_Mobile.html#devkit-howto-install-plasma-mobile.
However when running `sudo apt update` I get a 404 error for https://repo.kaidan.im/debpm.
I asked in the forum (https://forums.puri.sm/t/problem-installing-plasma-mobile-on-librem-5-dogwood/11682) and it seems that the documentation is outdated.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/176Expand on debugging / backtraces via coredumpctl2021-01-18T16:09:09ZGuido GuntherExpand on debugging / backtraces via coredumpctlhttps://developer.puri.sm/Librem5/Development_Environment/Boards/Troubleshooting/Debugging.html?highlight=coredumpctl helps to get started but just coredumpctl is not enough. You want matching debug packages (which requires adding a debu...https://developer.puri.sm/Librem5/Development_Environment/Boards/Troubleshooting/Debugging.html?highlight=coredumpctl helps to get started but just coredumpctl is not enough. You want matching debug packages (which requires adding a debug repository too) e.g. for phosh/phoc/squeekboard debugging see
https://source.puri.sm/snippets/88
An update to https://source.puri.sm/Librem5/developer.puri.sm/-/blob/master/Development_Environment/Boards/Troubleshooting/Debugging.rst would be nice.https://source.puri.sm/Librem5/feedbackd/-/issues/19create a libfeedback-rs2020-06-04T12:14:49ZGuido Gunthercreate a libfeedback-rsFor squeekboard and others having rust bindings would be useful. I'm open to whether that would better be done using gir or building a native library using the `dbus` crate.For squeekboard and others having rust bindings would be useful. I'm open to whether that would better be done using gir or building a native library using the `dbus` crate.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/158Explain <package>-dbgsym Debian packages2021-02-01T11:43:55ZGuido GuntherExplain <package>-dbgsym Debian packagesthese are a necessary tools for getting meaningful backtraces and are built by default nowadays but we should explain that
- they exist
- they do end up in the pureos archive
- one needs to enable a separate /etc/apt/sources.list entry
...these are a necessary tools for getting meaningful backtraces and are built by default nowadays but we should explain that
- they exist
- they do end up in the pureos archive
- one needs to enable a separate /etc/apt/sources.list entry
- the caveat that for `amber-phone` the entry is currently:
## amber-phone
```sh
cat <<EOF > /etc/apt/sources.list.d/debug.list
deb https://repo.pureos.net/pureos-debug/ amber-debug main
deb https://repo.pureos.net/pureos-debug/ amber-proposed-updates-debug main
deb https://repo.pureos.net/pureos-debug amber-phone-staging-debug main
EOF
apt update
apt install systemd-coredump gdb calls-dbgsym chatty-dbgsym libglib2.0-0-dbgsym libgtk-3-0-dbgsym phoc-dbgsym phosh-dbgsym squeekboard-dbgsym
```
(note the staging there).
## byzantium
```sh
cat <<EOF > /etc/apt/sources.list.d/debug.list
deb https://repo.pureos.net/pureos-debug/ byzantium-debug main
deb https://repo.pureos.net/pureos-debug/ landing-debug main
deb http://debug.mirrors.debian.org/debian-debug/ testing-debug main
EOF
apt update
apt install systemd-coredump gdb calls-dbgsym libglib2.0-0-dbgsym libgtk-3-0-dbgsym phoc-dbgsym phosh-dbgsym```
```
(dropped chatty and squeeboard since they're outdated in byzantium)
##
## Usage
- how they're used with coredumpctl/gdb
This could go to a `Creating meaningful coredump` section at https://developer.puri.sm/Librem5/Development_Environment/Boards/Troubleshooting/Debugging.html?highlight=coredumpctl#finding-core-dumpshttps://source.puri.sm/Librem5/Apps_Issues/-/issues/186Adaptive mumble app2023-06-14T08:26:13ZGuido GuntherAdaptive mumble appAn adaptive app (e.g. using libhandy) for mumble (https://www.mumble.info/) would be great since it's low overhead voice communication solution.An adaptive app (e.g. using libhandy) for mumble (https://www.mumble.info/) would be great since it's low overhead voice communication solution.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/151VM mouse support broken2020-02-08T12:45:56ZDavid BoddieVM mouse support brokenAccording to phoc#106 mouse events were not getting processed in qemu. This has been closed with the resolution that the "Virtio Tablet" device type should be used.
This isn't needed when I run a recent image (3445) but maybe something ...According to phoc#106 mouse events were not getting processed in qemu. This has been closed with the resolution that the "Virtio Tablet" device type should be used.
This isn't needed when I run a recent image (3445) but maybe something can be added to the documentation in case others experience this problem.Dorota CzaplejewiczDorota Czaplejewiczhttps://source.puri.sm/Librem5/Apps_Issues/-/issues/167Have an IVR system2019-11-22T11:12:56ZBob HamHave an IVR systemFrom David Hamner's [comment on a Calls issue](https://source.puri.sm/Librem5/calls/issues/26#note_68404):
"Auto answer the phone and ask for input:
* Press one (or enter pre-setup pin) to ring phone
* Press two to leave a message
* PI...From David Hamner's [comment on a Calls issue](https://source.puri.sm/Librem5/calls/issues/26#note_68404):
"Auto answer the phone and ask for input:
* Press one (or enter pre-setup pin) to ring phone
* Press two to leave a message
* PIN Code to start phone alarm and or IM GPS (lost phones)
* Custom greeting (Custom menu options/audio)
Give known callers a PIN that lets them ring straight through to your phone. They can then input your number into their contacts as \[number\]\[pause pause pause\]\[PIN\] to make it seamless."
This is a full [IVR](https://en.wikipedia.org/wiki/Interactive_voice_response) system, beyond the scope of just Calls really. Probably [Asterisk](https://www.asterisk.org) would be needed.https://source.puri.sm/Librem5/image-builder/-/issues/41Switch away from vmdebootstrap2023-08-11T09:57:14ZGuido GuntherSwitch away from vmdebootstrapFeature: https://source.puri.sm/Librem5/use-cases/issues/19
No urgency here, just since this came up a couple of time. vmdeboostrap is unmaintained upstream which isn't a big issue since we could pick it up but since there are alternati...Feature: https://source.puri.sm/Librem5/use-cases/issues/19
No urgency here, just since this came up a couple of time. vmdeboostrap is unmaintained upstream which isn't a big issue since we could pick it up but since there are alternatives we might also pick something more featureful. Candidates are
- [fai](https://fai-project.org/) (used for e.g. debian's cloud images, robust, has classes for different image types)
- [vmdb2](https://liw.fi/vmdb2/) (same upstream as vmdeboostrap so it might get dropped again)
- [debos](https://github.com/go-debos/debos) - looks well maintained
- [debspawn](https://github.com/lkorigin/debspawn) PureOS uses Debspawn to build images which are then used in reproducible testing.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/130Needs 'Librem 5 for iOS developers'2021-04-28T12:58:14ZGuido GuntherNeeds 'Librem 5 for iOS developers'Epic: https://source.puri.sm/Librem5/developer.puri.sm/issues/132
This should explain how to get started with our toolset (Gtk+ libhandy, builder, flatpak, ...) based on tools known from iOS.
This allows iOS developers to get started q...Epic: https://source.puri.sm/Librem5/developer.puri.sm/issues/132
This should explain how to get started with our toolset (Gtk+ libhandy, builder, flatpak, ...) based on tools known from iOS.
This allows iOS developers to get started quickly.https://source.puri.sm/Librem5/OS-issues/-/issues/32Provide /etc/fw_env.config to allow getting/setting u-boot environment from OS2019-04-29T09:22:57ZBob HamProvide /etc/fw_env.config to allow getting/setting u-boot environment from OSThe `fw_printenv(8)` and `fw_setenv(8)` programs in the `u-boot-tools` package require a configuration file, `/etc/fw_env.config`, to work. Various examples are under `/usr/share/doc/u-boot-tools/examples` and here:
https://salsa.debia...The `fw_printenv(8)` and `fw_setenv(8)` programs in the `u-boot-tools` package require a configuration file, `/etc/fw_env.config`, to work. Various examples are under `/usr/share/doc/u-boot-tools/examples` and here:
https://salsa.debian.org/debian/u-boot/tree/master/debian/env-configs
https://salsa.debian.org/debian/u-boot/blob/master/tools/env/fw_env.confighttps://source.puri.sm/Librem5/librem5-devkit-tools/-/issues/10Place u-boot in the boot MMC area2023-11-27T10:04:04ZDorota CzaplejewiczPlace u-boot in the boot MMC areaFeature: https://source.puri.sm/Librem5/use-cases/issues/60
u-boot is a device-specific piece of code, and OS should be generic across different devices. To allow the OS to get flashed seamlessly without taking care of what happens on t...Feature: https://source.puri.sm/Librem5/use-cases/issues/60
u-boot is a device-specific piece of code, and OS should be generic across different devices. To allow the OS to get flashed seamlessly without taking care of what happens on the boot loader side, they should occupy separate areas. Unfortunately, the OS likes to control the partition table of the whole device it resides on, so it conflicts with the boot loader if that boot loader lives in the general usage space. This can be solved by moving the non-OS pieces to the boot area of the eMMC device, and u-boot is the most important of them.
The pieces affected should be:
- u-boot, to be able to run from the boot area ([done](https://source.puri.sm/Librem5/uboot-imx/merge_requests/4))
- either u-boot builder, or image builder, to create a flashable boot area image
- image builder, to create a flashable OS image (without things in boot area)
- update arm01 Jenkins pipelines to expose the two images
- update flashing scripts to download two images and flash them separately
When u-boot is moved away from the main area, it will be possible to use [GPT](https://source.puri.sm/Librem5/librem5-devkit-tools/issues/7#note_14635), as the SoC's load address otherwise conflicts with the partition table.
Additional consequences:
- when updating u-boot using the OS, some way to get the boot area read-write needs to be found
- boot data must be kept closely updated with the kernel, or very stable, in order to avoid non-booting kernels
* * *https://source.puri.sm/Librem5/librem5-devkit-tools/-/issues/9instructions for downloading devkit image files with standard tools like curl...2019-03-26T12:04:57Zjezrainstructions for downloading devkit image files with standard tools like curl or wgetThis is a more of a feature request.
It would be excellent if devkit image files could be downloaded with curl or wget in a similar fashion to how a user downloads every other GNU Linux or Android image. Ideally, the instructions would ...This is a more of a feature request.
It would be excellent if devkit image files could be downloaded with curl or wget in a similar fashion to how a user downloads every other GNU Linux or Android image. Ideally, the instructions would also include the steps for flashing the images onto the dev kit.https://source.puri.sm/Librem5/linux/-/issues/1SDMA firmware2024-03-07T05:40:29ZAngus Ainslieangus.ainslie@puri.smSDMA firmwareEpic: https://source.puri.sm/Librem5/use-cases/issues/110
The imx sdma engine can load updated firmware for dma transfers but it also has a ROM fallback
imx-sdma 302c0000.sdma: external firmware not found,
using ROM firmware
There is ...Epic: https://source.puri.sm/Librem5/use-cases/issues/110
The imx sdma engine can load updated firmware for dma transfers but it also has a ROM fallback
imx-sdma 302c0000.sdma: external firmware not found,
using ROM firmware
There is also the possibility of writing custom sdma "scripts" so we could use open source firmware in the future.
http://billauer.co.il/blog/2011/10/imx-sdma-howto-assembler-linux/https://source.puri.sm/Librem5/image-builder/-/issues/29Use upstream vmdebootstrap2019-03-26T13:04:34ZZoltan GyarmatiUse upstream vmdebootstrapWhen i try to build an image for the devkit on my Ubuntu 18.04 host, it fails with the following error:
`ERROR: Only UEFI is supported on arm64`
A quick Google loo.kup shows that the reason is that vmdebootstrap doesn't support buildin...When i try to build an image for the devkit on my Ubuntu 18.04 host, it fails with the following error:
`ERROR: Only UEFI is supported on arm64`
A quick Google loo.kup shows that the reason is that vmdebootstrap doesn't support building arm64 image without uefi, which is a known issue[1] Turned out that the vmdebootstrap version used in the docker image is patched[2] to bypass this, so after I patched my host's vmdebootstrap version as well, the image builder works, although it's a rather hackish workaround.
I think this should be at least documented (gonna send a PR soon to cover this in the ReadMe), or migrating away from vmdebootstrap to vmdb2, as vmdebootstrap is abandonware anyway. Is there any plan to do this migration?
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845439
[2] https://source.puri.sm/Librem5/image-builder/commit/e28ecaf55ef3f13890193b7c22b069cc97e58627
EDIT: The proper solution is to use an upstream version of vmdebootstrap, like described above.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/66Describe cross-compilation2020-02-05T11:38:07ZDorota CzaplejewiczDescribe cross-compilationFeel free to close if this is not a valid issue.
One of the first questions on the evkit community channel was how to set up a cross-compiler. There are docs for building applications, but I'm not sure if any of those describe cross-bui...Feel free to close if this is not a valid issue.
One of the first questions on the evkit community channel was how to set up a cross-compiler. There are docs for building applications, but I'm not sure if any of those describe cross-building.David BoddieDavid Boddiehttps://source.puri.sm/Librem5/image-builder/-/issues/20USB C serial console2018-12-30T16:03:56ZAngus Ainslieangus.ainslie@puri.smUSB C serial consoleSetup a USB serial gadget on the USB C port so that me can have a console for the devkit.
Having ethernet and mass_storage would b enice too.Setup a USB serial gadget on the USB C port so that me can have a console for the devkit.
Having ethernet and mass_storage would b enice too.https://source.puri.sm/Librem5/virtboard/-/issues/19crashing on startup with g_dbus_interface_skeleton_export: assertion 'error =...2018-12-13T16:34:34ZBenedikt Wildenhaincrashing on startup with g_dbus_interface_skeleton_export: assertion 'error == NULL || *error == NULL' failed## What problem did you encounter
virtboard did crash while trying to start phosh
### What is the current behaviour?
Outputs "g_dbus_interface_skeleton_export: assertion 'error == NULL || *error == NULL' failed" and exits.
### How to...## What problem did you encounter
virtboard did crash while trying to start phosh
### What is the current behaviour?
Outputs "g_dbus_interface_skeleton_export: assertion 'error == NULL || *error == NULL' failed" and exits.
### How to reproduce
Install pureos on Emcrafts IMX8 development board and try to run phosh from a local root shell.
## Which version did you encounter the bug in?
- [ ] I Compiled it myself. If you compiled virtboard from source please provide the
git revision via e.g. by running ``git log -1 --pretty=oneline`` and pasting
the output below.
- [X] I used the precompiled Debian package (e.g. by running a prebuilt
image). Please paste the output oof ``dpkg -s virtboard`` below.
Package: virtboard
Status: install ok installed
Priority: optional
Section: x11
Installed-Size: 334
Maintainer: Dorota Czaplejewicz <dorota.czaplejewicz@puri.sm>
Architecture: arm64
Version: 0.0.6~6287.gbpcca2a8
Depends: libc6 (>= 2.17), libcairo2 (>= 1.10.0), libglib2.0-0 (>= 2.37.3), libpixman-1-0 (>= 0.15.12), libpng16-16 (>= 1.6.2-1), libwayland-client0 (>= 1.16), libwayland-cursor0 (>= 1.16), libxkbcommon0 (>= 0.5.0)
Suggests: libwlroots-examples
Description: On-screen keyboard for Wayland
A modified version of weston-keyboard. Changes include
.
* use of virtual-keyboard protocol to submit raw keycodes
* use of layer-shell protocol to display the keyboard
.
These protocols are supported by wlroots.
Homepage: https://source.puri.sm/Librem5/virtboard
## What hardware are you running virtboard on?
- [ ] amd64 qemu image
- [ ] Librem5 devkit
- [X] other (please elaborte)
Emcraft IMX8 devboard
## Releveant logfiles
Please provide relevant logs. You can e.g. the logs since last boot read
with ``journalctl -b 0``.
[virtkeyboardcrash.log](/uploads/557aeaa826f56331fb9de071c7b41737/virtkeyboardcrash.log)Dorota CzaplejewiczDorota Czaplejewicz