Librem5 issueshttps://source.puri.sm/groups/Librem5/-/issues2019-10-01T10:51:20Zhttps://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/wlroots/-/issues/12Consider implementing gtk_shell1 protocoll2023-07-24T09:06:32ZGuido GuntherConsider implementing gtk_shell1 protocollIt's provided by gnome-shell and allows for modal dialogs as well as identifiying apps by their app_id.It's provided by gnome-shell and allows for modal dialogs as well as identifiying apps by their app_id.https://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/image-builder/-/issues/12Liniakea integration / Making official devkit images2020-09-21T10:24:34ZGuido GuntherLiniakea integration / Making official devkit imagesTracking bug for integration into PureOS builds:
- [x] switch to PureOS (!26)
- [x] allow to disable inclusion of CI packages
- [ ] sort out how to communicate with Laniakea which artifacts to build
- [ ] What about external dependencie...Tracking bug for integration into PureOS builds:
- [x] switch to PureOS (!26)
- [x] allow to disable inclusion of CI packages
- [ ] sort out how to communicate with Laniakea which artifacts to build
- [ ] What about external dependencies (e.g. our imx6/imx8 kernels and u-boot are not in PureOS proper atm (#4, #3)
- [ ] depend on pureos-minimalhttps://source.puri.sm/Librem5/Apps_Issues/-/issues/44Basic flatpak config2018-07-28T07:21:42ZAlberto Fanjul AlonsoBasic flatpak configBy now steps to use flatpak are:
use steps in #34 to make room for flatpak runtime and apps. At some point it will be done automatically with cloud-initramfs-growroot. See https://source.puri.sm/Librem5/image-builder/merge_requests/39
...By now steps to use flatpak are:
use steps in #34 to make room for flatpak runtime and apps. At some point it will be done automatically with cloud-initramfs-growroot. See https://source.puri.sm/Librem5/image-builder/merge_requests/39
```
sudo flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
```
As an example install and configure Fractal:
```
sudo flatpak install flathub org.gnome.Fractal
```
Although there's a `XDG_DATA_DIRS` for purism user, it is not accesible for phosh, so it cannot read the desktop application installed by flatpak. You can check environment for phosh with:
xargs -n 1 -0 < /proc/$(ps -ef | grep phos[h] | grep -v rootston | awk '{print $2}')/environ
So we override that with:
sudo systemctl edit phosh.service
with this contents:
```
[Service]
Environment=XDG_DATA_DIRS=/home/purism/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
```
Then add Fractal to favorites with:
gsettings set sm.puri.phosh favorites "['org.gnome.Contacts.desktop', 'org.gnome.Epiphany.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.Fractal.desktop']"
![Captura_de_pantalla_de_2018-07-25_19-28-12](/uploads/6d630de863c3f53f844ff50c13e524ff/Captura_de_pantalla_de_2018-07-25_19-28-12.png)
![Captura_de_pantalla_de_2018-07-25_19-28-36](/uploads/4ee3cab132ffe5da180c9879cff0e6ef/Captura_de_pantalla_de_2018-07-25_19-28-36.png)https://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/wlroots/-/issues/11Crashes when phosh is killed and then reconnected2023-07-24T09:06:32ZGuido GuntherCrashes when phosh is killed and then reconnectedResource handling problem. See !14.Resource handling problem. See !14.https://source.puri.sm/Librem5/wlroots/-/issues/10qemu/nitrogen: Phosh's right menu is missing and the favorites menu is cut off2023-07-24T09:06:32ZGuido Guntherqemu/nitrogen: Phosh's right menu is missing and the favorites menu is cut offrootston is not applying the right scaling to popups: https://github.com/swaywm/wlroots/issues/1163 that's why they're of the screen with the scaling of two.rootston is not applying the right scaling to popups: https://github.com/swaywm/wlroots/issues/1163 that's why they're of the screen with the scaling of two.https://source.puri.sm/Librem5/Apps_Issues/-/issues/43gnome-settings users panel needs to be adjusted to PIN entry2019-12-13T18:37:28ZGuido Gunthergnome-settings users panel needs to be adjusted to PIN entryFeature: https://source.puri.sm/Librem5/use-cases/issues/46, https://source.puri.sm/Librem5/use-cases/issues/45
First it's likely far to hidden (under Details and it should also be adjusted for mobile (PIN entry))
This is about the PIN...Feature: https://source.puri.sm/Librem5/use-cases/issues/46, https://source.puri.sm/Librem5/use-cases/issues/45
First it's likely far to hidden (under Details and it should also be adjusted for mobile (PIN entry))
This is about the PIN to unlock the lockscreen.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/34Add 'strategy' section in the FAQ2019-04-16T21:27:02ZThibaultAdd 'strategy' section in the FAQPurism news often raise a loft of questions, some of which are recurrent. Among the questions I answer the most frequently are the following:
* Why didn't they chose Plasma Mobile? It's much more advanced
* Why won't they help Plasma Mo...Purism news often raise a loft of questions, some of which are recurrent. Among the questions I answer the most frequently are the following:
* Why didn't they chose Plasma Mobile? It's much more advanced
* Why won't they help Plasma Mobile as they promised?
* Do they support GNOME/push code upstream? (though, this questions happens less and less frequently as time passes)
* Porting GNOME to a mobile device is an ugly hack
* Their phone shell doesn't use GNOME technology
* Why hacking GTK+ 3 which is already obsolete?
* Their compositor is a fork of wlroots's example compositor rootston, which the founder told them in strong words not to do (actually he supports the project)
* Their code is not likely to make it to GTK+ 4 and GNOME Shell 4
The FAQ could benefit from a 'strategy' section answering some of those questions.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/virtboard/-/issues/7Use different keyboard layouts2018-12-03T19:13:13ZGuido GuntherUse different keyboard layoutsThese need to queried from gsettings ``org.gnome.desktop.input-sources``. Layout can be determined via ``gnome_xkb_info_get_layout_info()``. ``cc-region-panel.c`` in gnome-settings has stuff to look at.These need to queried from gsettings ``org.gnome.desktop.input-sources``. Layout can be determined via ``gnome_xkb_info_get_layout_info()``. ``cc-region-panel.c`` in gnome-settings has stuff to look at.https://source.puri.sm/Librem5/virtboard/-/issues/6Need "pin input" keyboard layout2020-02-12T12:32:05ZGuido GuntherNeed "pin input" keyboard layoutWe (will) have several dialogs (e.g. initial PIN entry) that require only numbers. For these cases it would be nice to have a keyboard layout that only displays a keypad (e.g. by using the HdyDialer widget). This could be used when the i...We (will) have several dialogs (e.g. initial PIN entry) that require only numbers. For these cases it would be nice to have a keyboard layout that only displays a keypad (e.g. by using the HdyDialer widget). This could be used when the input hint is "pin entry"https://source.puri.sm/Librem5/Apps_Issues/-/issues/39Need wwan gnome-settings-daemon plugin2020-02-12T12:32:37ZGuido GuntherNeed wwan gnome-settings-daemon pluginFeature: https://source.puri.sm/Librem5/use-cases/issues/4
As discussed with @bob.ham and @andrea.schaefer at GUADED 2018 we want something in the user session that:
* brings up the modem (e.g. pops up the sim card dialog via gcr)
* al...Feature: https://source.puri.sm/Librem5/use-cases/issues/4
As discussed with @bob.ham and @andrea.schaefer at GUADED 2018 we want something in the user session that:
* brings up the modem (e.g. pops up the sim card dialog via gcr)
* allows applications via a simple API to find out if the modem is ready (and if not initiate that)
Similar code used to live in nm-applet but that's (AFAIK) not used anymore in GMOME3. This will have interactions with #38 so parts might life in g-s-d.
See [mobile-applet.pdf](/uploads/74d46dbaae3cc3cfe005721d7a27db7c/mobile-applet.pdf)Guido GuntherGuido Guntherhttps://source.puri.sm/Librem5/Apps_Issues/-/issues/38Add mobile / wwan panel to GNOME settings2020-09-21T10:24:34ZGuido GuntherAdd mobile / wwan panel to GNOME settingsEpic: https://source.puri.sm/Librem5/use-cases/issues/2
As discussed at the settings [BoF at GUADEC](https://wiki.gnome.org/GUADEC/2018/Hacking%20days/SettingsBoF) we want a mobile specific panel for WWAN / mobile. According to Georges ...Epic: https://source.puri.sm/Librem5/use-cases/issues/2
As discussed at the settings [BoF at GUADEC](https://wiki.gnome.org/GUADEC/2018/Hacking%20days/SettingsBoF) we want a mobile specific panel for WWAN / mobile. According to Georges Stavracas there already was a WWAN panel redesign but I couldn't find it. @tobias.bernard any idea where that could be?
Somewhat related to
https://source.puri.sm/Librem5/Apps_Issues/issues/19
The minimum functionality is:
- [ ] select provider
- [ ] select network
- [ ] change PINGuido GuntherGuido Guntherhttps://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)https://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
```