Librem5 issueshttps://source.puri.sm/groups/Librem5/-/issues2019-09-24T13:28:00Zhttps://source.puri.sm/Librem5/OS-issues/-/issues/3Add identification of mobile device.2019-09-24T13:28:00ZClipseyAdd identification of mobile device.As an app developer, i'd like an easy way to idenfify if the device is a phone/mobile device.
Maybe adding an entry in /dev/ or an environment variable would be the easiest way to go.As an app developer, i'd like an easy way to idenfify if the device is a phone/mobile device.
Maybe adding an entry in /dev/ or an environment variable would be the easiest way to go.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/41Please provide guidance on how to style widgets2020-02-04T14:52:10ZGuido GuntherPlease provide guidance on how to style widgetsThere's several ways to style widgets:
* ui file
* within the C source code
* CSS
* (for labels etc) via Pango
The different ways to do so have different advantages/disadvantages but we should try to be consistent among our apps to pro...There's several ways to style widgets:
* ui file
* within the C source code
* CSS
* (for labels etc) via Pango
The different ways to do so have different advantages/disadvantages but we should try to be consistent among our apps to provide good examples for other phone apps. Please describe where to style what
cc: @adrien.plazas @tobias.bernardhttps://source.puri.sm/Librem5/Apps_Issues/-/issues/57Provide default CSS2018-08-30T08:41:53ZGuido GuntherProvide default CSSTo make chatty, calls, OSK, phosh consistent please provide a CSS file that sets default padding, fonts, button styles, etc. that can be added to the different projects otherwise this will be very inconsistent.
cc: @tobias.bernardTo make chatty, calls, OSK, phosh consistent please provide a CSS file that sets default padding, fonts, button styles, etc. that can be added to the different projects otherwise this will be very inconsistent.
cc: @tobias.bernardhttps://source.puri.sm/Librem5/Apps_Issues/-/issues/55g-s-d: Provide kill switch state2020-09-21T10:24:35ZGuido Guntherg-s-d: Provide kill switch stateEpic: https://source.puri.sm/Librem5/use-cases/issues/90
gnome-settings-daemon should provide the state of the hardware kill switches via org.gnome.SettingsDaemon rfkill (or similar). Applications like calls and phosh can then just quer...Epic: https://source.puri.sm/Librem5/use-cases/issues/90
gnome-settings-daemon should provide the state of the hardware kill switches via org.gnome.SettingsDaemon rfkill (or similar). Applications like calls and phosh can then just query it.
This should abstract away the case where the device is actually "unplugged" and not visible to the OS anymore. The short hack is to hardcode the devices. In the long run we might be able to get them from DT and compare to the devices we see to determine which ones are currently off (which would allow upstream merging).https://source.puri.sm/Librem5/developer.puri.sm/-/issues/40Standardize Translation Process w/ Documentation and Translation Tool2019-09-02T16:56:29ZScott AnecitoStandardize Translation Process w/ Documentation and Translation ToolEpic: https://source.puri.sm/Librem5/use-cases/issues/62
**Issue:**
With only three language translations, there is already a decent amount of variety within the copyright header comments:
German:
```
# German translations for phosh pa...Epic: https://source.puri.sm/Librem5/use-cases/issues/62
**Issue:**
With only three language translations, there is already a decent amount of variety within the copyright header comments:
German:
```
# German translations for phosh package.
# Copyright (C) 2018 THE phosh'S COPYRIGHT HOLDER
# This file is distributed under the same license as the phosh package.
# Automatically generated, 2018.
#
```
Spanish:
```
# Spanish translation for phosh package.
# Copyright (C) 2018 THE phosh'S COPYRIGHT HOLDER
# This file is distributed under the same license as the phosh package.
# Alberto Fanjul <albfan@gnome.org>, 2018.
#
```
Italian:
```
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the phosh package.
# FIRST AUTHOR <ant.pandolfo@gmail.com>, 2018.
#
```
For example, the Italian header is missing the "[...] translations for phosh package" and has a 'FIRST AUTHOR' line whereas the Spanish .po doesn't have this text and the German .po has 'Automatically generated'. There should be a standardized header across translations files.
**Proposed Solutions:**
Create a documented/standardized process for contributing translations:
Short Term: @guido.gunther should probably write a guide on how to contribute a translation in either the README or Wiki so that the same process is more likely to be followed resulting in similar copyright headers and making it easier for people not familiar with translating .po files resulting in more contributions
Long Term: Purism should setup a translation web service instance of Weblate, Pootle, or something similar which in turn provides numerous benefits. Not all privacy lovers are necessarily familiar with cloning, committing, and PR'ing and using such an instance eliminates most of the hurdles and allows them to focus on just translating strings. It also provides easier management of translations; Purism can easily see how many x of y strings are translated, and adding a new string in the 'master' copy is automatically reflected in the .po files. There are also other features that help make sure terminology is similar across strings, etc. While the benefits may not be immediate now given how few strings there are, it's easier to set this up now while there are only three languages with a few strings than later on with many languages with many strings.https://source.puri.sm/Librem5/Apps_Issues/-/issues/53Align mobile and desktop UX (user experience)2019-03-26T13:20:55ZPeter BittnerAlign mobile and desktop UX (user experience)(Maybe this is already covered by some of your UI guidelines, not sure. Sorry, if that's the case!)
I'd love to see that the user experience on Librem desktop-grade devices (notebooks) is just the same as on Librem mobile devices. Deskt...(Maybe this is already covered by some of your UI guidelines, not sure. Sorry, if that's the case!)
I'd love to see that the user experience on Librem desktop-grade devices (notebooks) is just the same as on Librem mobile devices. Desktop devices should be regarded as "[GTD](https://gettingthingsdone.com/five-steps/) devices" (productivity tools) first, hence Mail, Calendar, Todo lists should all appear integrated in a notification system.
By default, there should be no need to fire up a mail or calendar application after starting or opening your computer.
Current State
-------------
This UX is partly already implemented in the GNOME desktop (as for calendar and defining related data sources in the System Setting "Online Accounts", for example).
See Also
--------
- ["Nicely integrated"](https://forums.puri.sm/t/will-the-librem-5-support-my-must-have-apps/3374/6) (forum comment)https://source.puri.sm/Librem5/infra/ansible-librem/-/issues/3Set up pbuilder so it runs "apt update" before starting the build2018-08-07T14:48:08ZGuido GuntherSet up pbuilder so it runs "apt update" before starting the buildThis makes sure we pull in fresh build-deps (instead of relying on the chroot to be upgraded).
See https://source.puri.sm/Librem5/deb-build-jobs/merge_requests/23#note_3452
Filing it here since these ansible scripts set up the pbuilder...This makes sure we pull in fresh build-deps (instead of relying on the chroot to be upgraded).
See https://source.puri.sm/Librem5/deb-build-jobs/merge_requests/23#note_3452
Filing it here since these ansible scripts set up the pbuilder chroots.https://source.puri.sm/Librem5/Apps_Issues/-/issues/47Time tracking application2019-03-25T19:51:14ZGuido GuntherTime tracking applicationA time trackig application like [hamster](https://github.com/projecthamster/) would be nice. There's a GTK+3 version in the works. On a phone it could start tracking time when at a certain location (e.g. a customer's site).A time trackig application like [hamster](https://github.com/projecthamster/) would be nice. There's a GTK+3 version in the works. On a phone it could start tracking time when at a certain location (e.g. a customer's site).https://source.puri.sm/Librem5/librem-buildbot/-/issues/4Please allow to query other board types too2018-07-29T16:20:22ZGuido GuntherPlease allow to query other board types tooI'd be great if the build bot could spit out links for the imx6 and imx8 boards too.I'd be great if the build bot could spit out links for the imx6 and imx8 boards too.https://source.puri.sm/Librem5/librem-buildbot/-/issues/3Please fix name2018-07-30T06:52:06ZGuido GuntherPlease fix nameThis is not a build bot but rather a bot to query build information so what about ``librem5-matrix-bot``? With a generic name it could then in the future also answer questions like ``!faq screensize`` and then go lookup FAQ entries with ...This is not a build bot but rather a bot to query build information so what about ``librem5-matrix-bot``? With a generic name it could then in the future also answer questions like ``!faq screensize`` and then go lookup FAQ entries with matching screensize in the FAQ, etc. etc.
A build bot is s.th. like this: https://en.wikipedia.org/wiki/Buildbot.https://source.puri.sm/Librem5/librem-buildbot/-/issues/2Please point to qcow2 image for amd642018-07-29T16:18:39ZGuido GuntherPlease point to qcow2 image for amd64it's more flexible than the raw image.it's more flexible than the raw image.https://source.puri.sm/Librem5/virtboard/-/issues/8Add an option of full "slim keyboard"2018-07-28T18:31:01ZOtto BolyosAdd an option of full "slim keyboard"I would like to suggest to add an option of a slim keyboard. On Android, I currently use [Hacker’s Keyboard](https://github.com/klausw/hackerskeyboard/tree/master/java) (some images [here](http://google.com/images?q=hackers+keyboard). HK...I would like to suggest to add an option of a slim keyboard. On Android, I currently use [Hacker’s Keyboard](https://github.com/klausw/hackerskeyboard/tree/master/java) (some images [here](http://google.com/images?q=hackers+keyboard). HK is quite good, but still is not perfect, if you use nearly all the keys.
What I would like the `virtboard` to look like is something like this:
![Slim keyboard (UK layout)](https://www.uk-edeals.co.uk/discount-checkout/KBS.TO-L800.UK.W.F.jpg)
Some notes:
(1) F1 to F12 could be hidden (we could have some kind of toggle to access these keys).
(2) Above Left and Right keys and below Right Shift, there definately should be some space. :)
(3) Left Ctrl should be the leftmost key.
(4) There could be an Fn key, which could be used to access the NumPad (like in HK).
(5) [Low Priority] Use might configure the image of Win/Meta key.
(6) There should a bit more space under the ESC and F1 to F12 keys, and left from Home, PgUp, PgDn and End keys.
(7) Context menu key is sometimes also important. :)https://source.puri.sm/Librem5/Apps_Issues/-/issues/46Put deviced on the dev board2019-10-01T10:51:20ZGuido GuntherPut deviced on the dev boardTo interact with build we likely want that.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904632To interact with build we likely want that.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904632https://source.puri.sm/Librem5/Apps_Issues/-/issues/45Make glade useable for everyone2018-07-27T10:25:44ZGuido GuntherMake glade useable for everyone@adrien.plazas brings up points *against* glade usage in https://source.puri.sm/Librem5/calls/merge_requests/7#note_3139.
- [ ] writes defaults for properties in UI files
- [ ] adds useless placeholers
- [ ] it doesn't support all the f...@adrien.plazas brings up points *against* glade usage in https://source.puri.sm/Librem5/calls/merge_requests/7#note_3139.
- [ ] writes defaults for properties in UI files
- [ ] adds useless placeholers
- [ ] it doesn't support all the features of GtkBuilder, like properties bindings
@adrien.plazas could you please follow up with links to upstream bugs here? We need to get these fixed so that working on ui files with and without glade is possible. Otherwise the whole development story will suck.
(I'm a happy glade user though).https://source.puri.sm/Librem5/developer.puri.sm/-/issues/35Describe how to work with UI files2020-02-12T15:11:24ZGuido GuntherDescribe how to work with UI filesEpic: https://source.puri.sm/Librem5/use-cases/issues/62
@adrien.plazas brings up points against glade usage. We should have a very clear guideline in the documentation how to handle UI files that works both for newcomers as well as fo...Epic: https://source.puri.sm/Librem5/use-cases/issues/62
@adrien.plazas brings up points against glade usage. We should have a very clear guideline in the documentation how to handle UI files that works both for newcomers as well as for people very familiar with GTK+. @adrien.plazas can you expand on this?
See https://source.puri.sm/Librem5/calls/merge_requests/7#note_3133David BoddieDavid Boddiehttps://source.puri.sm/Librem5/librem-buildbot/-/issues/1dub exception causing librem-buildbot to enter failed state2018-07-25T17:02:38ZHeather Ellsworthdub exception causing librem-buildbot to enter failed stateLooks like there is some dub exception happening. Not sure what is causing it though.
Full journalctl crash log:
```
Jul 25 02:47:31 heimdall systemd[1]: Started Run matrix/jenkins bot to inform room when new qemu image available.
Jul 2...Looks like there is some dub exception happening. Not sure what is causing it though.
Full journalctl crash log:
```
Jul 25 02:47:31 heimdall systemd[1]: Started Run matrix/jenkins bot to inform room when new qemu image available.
Jul 25 02:55:18 heimdall librem-buildbot[22693]: object.Exception@../../../.dub/packages/vibe-d-master/vibe-d/http/vibe/http/client.d(542): Second attempt to send HTTP request failed.
Jul 25 02:55:18 heimdall librem-buildbot[22693]: ----------------
Jul 25 02:55:18 heimdall librem-buildbot[22693]: /usr/include/dmd/phobos/std/exception.d:515 pure @safe void std.exception.bailOut!(Exception).bailOut(immutable(char)[], ulong, scope const(char)[]) [0x59257c7e]
Jul 25 02:55:18 heimdall librem-buildbot[22693]: /usr/include/dmd/phobos/std/exception.d:436 pure @safe bool std.exception.enforce!().enforce!(bool).enforce(bool, lazy const(char)[], immutable(char)[], ulong) [0
Jul 25 02:55:18 heimdall librem-buildbot[22693]: ../../../.dub/packages/vibe-d-master/vibe-d/http/vibe/http/client.d:542 @safe bool vibe.http.client.HTTPClient.doRequestWithRetry(scope void delegate(vibe.http.cl
Jul 25 02:55:18 heimdall librem-buildbot[22693]: ../../../.dub/packages/vibe-d-master/vibe-d/http/vibe/http/client.d:471 @trusted void vibe.http.client.HTTPClient.request(scope void delegate(scope vibe.http.clie
Jul 25 02:55:18 heimdall librem-buildbot[22693]: ../../../.dub/packages/vibe-d-master/vibe-d/http/vibe/http/client.d:182 @safe void vibe.http.client.requestHTTP(vibe.inet.url.URL, void delegate(scope vibe.http.c
Jul 25 02:55:18 heimdall librem-buildbot[22693]: ../../../.dub/packages/vibe-d-master/vibe-d/web/vibe/web/rest.d:1871 @safe vibe.data.json.Json vibe.web.rest.request(vibe.inet.url.URL, void delegate(vibe.http.cl
Jul 25 02:55:18 heimdall librem-buildbot[22693]: ../../../.dub/packages/vibe-d-master/vibe-d/web/vibe/web/rest.d:1762 @safe irest.JenkinsRestBuildList.Root vibe.web.rest.executeClientMethod!(irest.JenkinsRestBui
Jul 25 02:55:18 heimdall librem-buildbot[22693]: ../../../.dub/packages/vibe-d-master/vibe-d/utils/vibe/internal/meta/codegen.d-mixin-301:304 irest.JenkinsRestBuildList.Root vibe.web.rest.RestInterfaceClient!(ir
Jul 25 02:55:18 heimdall librem-buildbot[22693]: source/rest.d:14 irest.JenkinsRestBuildList.Root rest.GetBuildList() [0x5928d7e8]
Jul 25 02:55:18 heimdall librem-buildbot[22693]: source/bot.d:175 bot.JobDescrBox bot.MatrixBOT.GetJenkinsInfo() [0x5924fd4e]
Jul 25 02:55:18 heimdall librem-buildbot[22693]: source/bot.d:78 void bot.MatrixBOT.Update() [0x5924f636]
Jul 25 02:55:18 heimdall librem-buildbot[22693]: source/app.d:22 _Dmain [0x5924cf30]
Jul 25 02:55:18 heimdall librem-buildbot[22693]: API::JenkinsRestBuildList https://arm01.puri.sm/job/Images/job/Image%20Build//api/json
Jul 25 02:55:18 heimdall librem-buildbot[22693]: API::JenkinsRestJobDescription https://arm01.puri.sm/job/Images/job/Image%20Build/266/api/json
Jul 25 02:55:18 heimdall librem-buildbot[22693]: imx8 image
Jul 25 02:55:18 heimdall librem-buildbot[22693]: API::JenkinsRestJobDescription https://arm01.puri.sm/job/Images/job/Image%20Build/265/api/json
Jul 25 02:55:18 heimdall librem-buildbot[22693]: imx6 image
Jul 25 02:55:18 heimdall librem-buildbot[22693]: API::JenkinsRestJobDescription https://arm01.puri.sm/job/Images/job/Image%20Build/264/api/json
Jul 25 02:55:18 heimdall librem-buildbot[22693]: qemu-x86_64 image
Jul 25 02:55:18 heimdall librem-buildbot[22693]: API::JenkinsRestBuildList https://arm01.puri.sm/job/Images/job/Image%20Build//api/json
Jul 25 02:55:18 heimdall systemd[1]: librem-buildbot.service: Main process exited, code=exited, status=1/FAILURE
Jul 25 02:55:18 heimdall systemd[1]: librem-buildbot.service: Unit entered failed state.
Jul 25 02:55:18 heimdall systemd[1]: librem-buildbot.service: Failed with result 'exit-code'.
```https://source.puri.sm/Librem5/Apps_Issues/-/issues/42Make gnome-settings-daemon run without XWayland2020-09-21T10:24:35ZGuido GuntherMake gnome-settings-daemon run without XWaylandIt be great if we could run without XWayland but at least
- [ ] gsd-color
- [ ] gsd-power
- [ ] gsd-keyboard
require it. TODO:
- [ ] check with upstream
- [ ] check if we can build these without X11 support
See https://source.puri.sm...It be great if we could run without XWayland but at least
- [ ] gsd-color
- [ ] gsd-power
- [ ] gsd-keyboard
require it. TODO:
- [ ] check with upstream
- [ ] check if we can build these without X11 support
See https://source.puri.sm/Librem5/phosh/merge_requests/83https://source.puri.sm/Librem5/Apps_Issues/-/issues/41Automatic dark theme switching2019-06-07T09:21:29ZGuido GuntherAutomatic dark theme switchingNot sure if this is a phosh issue (ie is it something handled by the compositor/display manager, or is that automagically handled by the services in GNOME) but I expect the phone to shift its screen towards the reds to reduce blue light ...Not sure if this is a phosh issue (ie is it something handled by the compositor/display manager, or is that automagically handled by the services in GNOME) but I expect the phone to shift its screen towards the reds to reduce blue light at night, AND to switch to a dark GTK+Qt theme, so that it's 10x easier on the eyes.
Assuming there is an ambient light sensor, it should also switch to dark theme variants whenever the user is in the dark.
- [x] Automatic red shift (by time)
- [ ] Automatic theme switching (needs to go into g-s-d)
- [ ] Redshift/Theme-switching by environment brightness (needs to go into g-s-d)https://source.puri.sm/Librem5/Apps_Issues/-/issues/40Get kgdb working with the imx8mq2018-07-17T17:12:52ZAngus Ainslieangus.ainslie@puri.smGet kgdb working with the imx8mqgdb can connect over the serial port to the imx8m but cannot set break points. I think it might be due to RO kernel sections.
Here is a patch to allow disabling CONFIG_STRICT_KERNEL_RWX but it still can't write breakpoints
https://sour...gdb can connect over the serial port to the imx8m but cannot set break points. I think it might be due to RO kernel sections.
Here is a patch to allow disabling CONFIG_STRICT_KERNEL_RWX but it still can't write breakpoints
https://source.puri.sm/Librem5/linux-emcraft/commit/0f246ee3344a2c435003dad90743fe4b7c968b62https://source.puri.sm/Librem5/image-builder/-/issues/11uboot/kernel: Only send mail on failed builds2019-03-26T11:59:14ZGuido Guntheruboot/kernel: Only send mail on failed buildsAs I learned today mails from Jenkins were so far held by list moderation. Now that they flow in it'd be nice to only have them when a build fails. E.g. like:
https://stackoverflow.com/questions/39720225/send-email-on-jenkins-pipeline...As I learned today mails from Jenkins were so far held by list moderation. Now that they flow in it'd be nice to only have them when a build fails. E.g. like:
https://stackoverflow.com/questions/39720225/send-email-on-jenkins-pipeline-failure
@angus.ainslie since this affects kernel and uboot could you have a look (since I'm on my way back from GUADEC)