Librem5 issueshttps://source.puri.sm/groups/Librem5/-/issues2019-03-22T12:15:36Zhttps://source.puri.sm/Librem5/wlroots/-/issues/20Plugging a screen confines the cursor2019-03-22T12:15:36ZDorota CzaplejewiczPlugging a screen confines the cursorPreparation:
x86_64 Debian Testing with Purism CI repo, librem5-gnome installed, `purism` user, AMD GPU, DVI display attached
Execution:
1. Attach a HDMI screen (dev board adapter)
2. Start phosh
Result:
Mouse pointer is restricted ...Preparation:
x86_64 Debian Testing with Purism CI repo, librem5-gnome installed, `purism` user, AMD GPU, DVI display attached
Execution:
1. Attach a HDMI screen (dev board adapter)
2. Start phosh
Result:
Mouse pointer is restricted to the HDMI screen
Expected result:
Both screens are positioned side-by-side from the POV of the mouse pointer, allowing it to move from one to another seamlessly
Workaround:
If the HDMI screen was attached later, the UI will stay on the unreachable one. Disconnect the newly attached screen to go back to the first one.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/61Documentation should not discuss flashing (proprietary) firmware for modem2018-12-14T11:43:46ZBob HamDocumentation should not discuss flashing (proprietary) firmware for modemCurrently the "Mini-Tutorials" have a section on flashing modem firmware:
https://source.puri.sm/Librem5/developer.puri.sm/blob/f358d3afea8115411030947074c126909f5e619a/Boards/mini-tutorials.rst#L19
Firstly, we no longer use that Sierr...Currently the "Mini-Tutorials" have a section on flashing modem firmware:
https://source.puri.sm/Librem5/developer.puri.sm/blob/f358d3afea8115411030947074c126909f5e619a/Boards/mini-tutorials.rst#L19
Firstly, we no longer use that Sierra Wireless modem. Second, providing instructions on how to flash proprietary firmware is a problem from the perspective of the FSF, both for the Librem 5's potential RYF certification and PureOS's listing as a GNU-FSDG satisfying distribution:
https://www.gnu.org/distros/free-system-distribution-guidelines.html#documentation
We should remove this section on the firmware flashing and remove mention of the MC7455 as this will just confuse people.https://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 Czaplejewiczhttps://source.puri.sm/Librem5/image-builder/-/issues/19imx6 image stuck in u-boot2018-12-18T15:36:36ZDorota Czaplejewiczimx6 image stuck in u-boothttps://arm01.puri.sm/job/Images/job/Image%20Build/732/ gets stuck while looking for a device:
```
U-Boot 2017.07-28563-g04d7ed8078 (Dec 24 2017 - 20:46:50 +0100)
CPU: Freescale i.MX6QP rev1.0 at 792 MHz
Reset cause: POR
Board: nitro...https://arm01.puri.sm/job/Images/job/Image%20Build/732/ gets stuck while looking for a device:
```
U-Boot 2017.07-28563-g04d7ed8078 (Dec 24 2017 - 20:46:50 +0100)
CPU: Freescale i.MX6QP rev1.0 at 792 MHz
Reset cause: POR
Board: nitrogen6_max
I2C: ready
DRAM: 3.8 GiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
SF: Detected sst25vf016b with page size 256 Bytes, erase size 4 KiB, total 2 MiB
auto-detected panel 1280x720M@60
Display: hdmi:1280x720M@60 (1280x720)
In: serial
Out: serial
Err: serial
Net: Micrel ksz9021 at 6
FEC [PRIME], usb_ether
Hit any key to stop autoboot: 0
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part
No port device detected!
** Bad device size - sata 0 **
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part
No port device detected!
** Bad device sata 1 **
switch to partitions #0, OK
mmc0 is current device
** File not found /6x_bootscript **
timeout irqstat=10000
timeout irqstat=10000
switch to partitions #0, OK
mmc1(part 0) is current device
** No partition table - mmc 1 **
starting USB...
USB0: Port not available.
USB1: USB EHCI 1.00
scanning bus 1 for devices... EHCI timed out on TD - token=0x80008c80
unable to get device descriptor (error=-1)
2 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
scanning usb for ethernet devices... 0 Ethernet Device(s) found
USB device 0: unknown device
** Bad device usb 0 **
USB device 1: unknown device
** Bad device usb 1 **
6x_bootscript not found
serial console at 115200, 8N1
details at http://boundarydevices.com/6q_bootscript
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part
No port device detected!
timeout irqstat=10000
timeout irqstat=10000
switch to partitions #0, OK
mmc1(part 0) is current device
expose MMC 1 over USB
UMS: LUN 0, dev 1, hwpart 0, sector 0x0, count 0x710000
/
```
I checksummed my SD card contents against the image, so it's unlikely to be the issue. It would be nice if someone could check if this happens with their board too before I dive into bisecting things.
A suggestion for a temporary image to use would be nice too.https://source.puri.sm/Librem5/virtboard/-/issues/18Crash on clicking tab2018-12-18T14:27:02ZDorota CzaplejewiczCrash on clicking tabNot sure if this is a virtboard crash, but it's ~~very likely~~ confirmed.
Steps to reproduce:
1. Use wlroots from https://source.puri.sm/Librem5/wlroots/merge_requests/40
2. Start the calendar
3. Start `yad --entry` (keyboard pops up)...Not sure if this is a virtboard crash, but it's ~~very likely~~ confirmed.
Steps to reproduce:
1. Use wlroots from https://source.puri.sm/Librem5/wlroots/merge_requests/40
2. Start the calendar
3. Start `yad --entry` (keyboard pops up)
4. Type "tab" in virtboard (Observation 1)
5. Kill yad
6. Start `yad --entry` (Observation 2)
Expected result:
1. Focus moves to "OK", keyboard hides
2. Keyboard appears
Actual result:
1. Key gets stuck
2. Keyboard crashesDorota CzaplejewiczDorota Czaplejewiczhttps://source.puri.sm/Librem5/haegtesse/-/issues/3Fails to build on PureOS2018-12-10T11:34:34ZGuido GuntherFails to build on PureOSSee http://software.pureos.net/builds/job/67bfe23f-2de1-45d0-aa1c-63b07a593900 . This currently holds up our PureOS image build.See http://software.pureos.net/builds/job/67bfe23f-2de1-45d0-aa1c-63b07a593900 . This currently holds up our PureOS image build.https://source.puri.sm/Librem5/wlroots/-/issues/19Lets consider switching packaging to Debian + diff2019-03-22T13:10:55ZGuido GuntherLets consider switching packaging to Debian + diffNow that wlroots starts tagging releases we could base our packaging entirely to what's in Debian plus a diff between that and our Librem5 branch. We would basically build that diff and ship it as debian/patches/librem-5.patch. This woul...Now that wlroots starts tagging releases we could base our packaging entirely to what's in Debian plus a diff between that and our Librem5 branch. We would basically build that diff and ship it as debian/patches/librem-5.patch. This would ease automation too.https://source.puri.sm/Librem5/image-builder/-/issues/18Build a "proper" kernel package2019-12-10T18:07:44ZGuido GuntherBuild a "proper" kernel packageDebian's kernel package does more things then "make deb-pkg" can provide. See
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s-common-official
for how this would work. This package could be uploaded to the Pu...Debian's kernel package does more things then "make deb-pkg" can provide. See
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s-common-official
for how this would work. This package could be uploaded to the PureOS repos.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/59Note that "master" branches come from nightly repositories2018-11-29T17:11:52ZBob HamNote that "master" branches come from nightly repositoriesAs discussed in calls!27, building the Calls flatpak requires access to the "master" branch of the GNOME Sdk and Platform, only available from the nightly repositories. Merge request !73 adds a note about the nightly repositories but ma...As discussed in calls!27, building the Calls flatpak requires access to the "master" branch of the GNOME Sdk and Platform, only available from the nightly repositories. Merge request !73 adds a note about the nightly repositories but makes no mention of "master" branches and the GNOME wiki page does not explain "master" branches either. If someone followed the instructions on our flatpak page and went on to try and build a Calls flatpak, they would still come across an error and still have no information about why.
The instructions need to note not only that the nightly repositories might be required but more importantly, *why*: because the nightly repositories *contain the "master" branches that some packages, such as Calls, depend on*.https://source.puri.sm/Librem5/virtboard/-/issues/16fatal error: systemd/sd-bus.h2018-11-28T08:55:10ZMarkus Wenzelfatal error: systemd/sd-bus.hHi
Just trying to compile on gentoo linux... getting error:
```
../clients/keyboard.c:44:10: fatal error: systemd/sd-bus.h: No such file or directory
#include <systemd/sd-bus.h>
^~~~~~~~~~~~~~~~~~
compilation terminated.
ninja...Hi
Just trying to compile on gentoo linux... getting error:
```
../clients/keyboard.c:44:10: fatal error: systemd/sd-bus.h: No such file or directory
#include <systemd/sd-bus.h>
^~~~~~~~~~~~~~~~~~
compilation terminated.
ninja: build stopped: subcommand failed.
```
On gentoo we use OpenRC, not systemd... is this the problem?https://source.puri.sm/Librem5/developer.puri.sm/-/issues/58Explain translation handling2018-11-28T16:21:55ZGuido GuntherExplain translation handlingThe "recommended way of handling translations" should be documented for both transators as well as project maintainers / app developers. See e.g.
https://source.puri.sm/Librem5/phosh/snippets/9
and the thread at:
https://lists.communi...The "recommended way of handling translations" should be documented for both transators as well as project maintainers / app developers. See e.g.
https://source.puri.sm/Librem5/phosh/snippets/9
and the thread at:
https://lists.community.puri.sm/pipermail/librem-5-dev/2018-November/000078.htmlhttps://source.puri.sm/Librem5/developer.puri.sm/-/issues/57Explain how translation are being handled2018-11-28T14:44:22ZGuido GuntherExplain how translation are being handledHow translations are being updated / handled causes confusion. See the thread at:
https://lists.community.puri.sm/pipermail/librem-5-dev/2018-November/000078.html
The workflow should be documented and maybe the commands used by maintai...How translations are being updated / handled causes confusion. See the thread at:
https://lists.community.puri.sm/pipermail/librem-5-dev/2018-November/000078.html
The workflow should be documented and maybe the commands used by maintainers moved out of the gitlab snippet:
https://source.puri.sm/Librem5/phosh/snippets/9https://source.puri.sm/Librem5/Apps_Issues/-/issues/74Make Web's history windows fit the phone2020-09-21T10:24:34ZAdrien PlazasMake Web's history windows fit the phoneFeature: https://source.puri.sm/Librem5/use-cases/issues/51
The history window of Web should fit the phone's screen, preferably by making it adaptive upstream.Feature: https://source.puri.sm/Librem5/use-cases/issues/51
The history window of Web should fit the phone's screen, preferably by making it adaptive upstream.Adrien PlazasAdrien Plazashttps://source.puri.sm/Librem5/Apps_Issues/-/issues/73Make Web's preferences windows fit the phone2020-09-21T10:24:34ZAdrien PlazasMake Web's preferences windows fit the phoneFeature: https://source.puri.sm/Librem5/use-cases/issues/52
The preferences window of Web should fit the phone's screen, preferably by making it adaptive upstream.Feature: https://source.puri.sm/Librem5/use-cases/issues/52
The preferences window of Web should fit the phone's screen, preferably by making it adaptive upstream.Adrien PlazasAdrien Plazashttps://source.puri.sm/Librem5/Apps_Issues/-/issues/72Make Web's secondary windows adaptive2020-09-21T10:24:35ZHeather EllsworthMake Web's secondary windows adaptiveFeature: https://source.puri.sm/Librem5/use-cases/issues/51
Secondary windows of Web should fit the phone's screen, preferably by making them adaptive upstream.
Secondary windows refer to Import bookmarks, Export bookmarks, Override te...Feature: https://source.puri.sm/Librem5/use-cases/issues/51
Secondary windows of Web should fit the phone's screen, preferably by making them adaptive upstream.
Secondary windows refer to Import bookmarks, Export bookmarks, Override text encoding and maybe more.Adrien PlazasAdrien Plazashttps://source.puri.sm/Librem5/librem5-base/-/issues/3Add theme with default ringtone2019-09-26T13:50:15ZHeather EllsworthAdd theme with default ringtoneAs mentioned in https://source.puri.sm/Librem5/calls/issues/37, the default ringtone should be shipped in a package and the Calls application can use the default that is configured.As mentioned in https://source.puri.sm/Librem5/calls/issues/37, the default ringtone should be shipped in a package and the Calls application can use the default that is configured.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/55Provide Non-C examples for creating app from scratch2019-05-31T20:41:36ZHeather EllsworthProvide Non-C examples for creating app from scratchIn order to be friendly to newcomers, document at least one example of how to write an app from scratch in Python. Then add in some adaptive widgets that make sense for this app to further show how a user can implement libhandy for their...In order to be friendly to newcomers, document at least one example of how to write an app from scratch in Python. Then add in some adaptive widgets that make sense for this app to further show how a user can implement libhandy for their own apps.David BoddieDavid Boddiehttps://source.puri.sm/Librem5/developer.puri.sm/-/issues/53Document how disk encryption works2020-12-11T16:18:05ZHeather EllsworthDocument how disk encryption worksFeature: https://source.puri.sm/Librem5/Apps_Issues/issues/104
Document how disk encryption work will work (needs a plan how we want to do e.g. PIN entry, ...)Feature: https://source.puri.sm/Librem5/Apps_Issues/issues/104
Document how disk encryption work will work (needs a plan how we want to do e.g. PIN entry, ...)https://source.puri.sm/Librem5/developer.puri.sm/-/issues/52Phone setup instructions2019-11-25T15:24:43ZHeather EllsworthPhone setup instructionsAs soon as a user receives their Librem 5, they will want to follow some guide to set it up. This product *should* come with a user manual in the box (makes a nice impression) but in case the user looses their manual:
- [ ] we should pro...As soon as a user receives their Librem 5, they will want to follow some guide to set it up. This product *should* come with a user manual in the box (makes a nice impression) but in case the user looses their manual:
- [ ] we should provide a link to download the user manual (do we want this on developer.puri.sm or some place from the main puri.sm website?)
- [ ] add a picture of the phone identifying each port, similar to https://developer.puri.sm/Librem5/_images/dev-board-sockets-buttons-switches.png
- [ ] detailed setup instructions with screenshots of each of the initial setup panels and very brief explanation of each field
- [ ] add instructions on reinstalling to phone
- [ ] list where to contact us for help: support@puri.sm (or librem-5-users@lists.community.puri.sm?)
- [ ] add instructions on how to put Plasma Mobile on the phone (if it works)
- [ ] add instructions on how to put UBports on the phone (if it works)
See the related [Devkit unboxing experience](https://source.puri.sm/Librem5/use-cases/issues/23)
- [ ] [Phone Essentials List](https://source.puri.sm/Librem5/Apps_Issues/issues/64)
- [x] [Write a quickstart guide for the Librem 5](https://source.puri.sm/Librem5/quickstart-guide/issues/1)