Librem5 issueshttps://source.puri.sm/groups/Librem5/-/issues2021-01-22T12:25:08Zhttps://source.puri.sm/Librem5/librem5-devkit-tools/-/issues/37Split out pytests2021-01-22T12:25:08ZGuido GuntherSplit out pytestsThey're useful on their own nowadays and have a scope that warants an extra package.They're useful on their own nowadays and have a scope that warants an extra package.https://source.puri.sm/Librem5/deb-build-jobs/-/issues/67Keep upstream/latest & pristine-tar in sync with Debian automatically2021-01-22T12:50:40ZGuido GuntherKeep upstream/latest & pristine-tar in sync with Debian automaticallyNot really a `deb-build-jobs` issues but this repo fits somewhat better than the others:
Now that we thankfully backport way more packaging from Debian it would be nice if we could keep `pristine-tar`, `upstream/latest` and tags in sync...Not really a `deb-build-jobs` issues but this repo fits somewhat better than the others:
Now that we thankfully backport way more packaging from Debian it would be nice if we could keep `pristine-tar`, `upstream/latest` and tags in sync from salsa automatically. This could also be used for changes notification.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/178Reference board schematic instead of adding them2021-01-23T17:14:08ZGuido GuntherReference board schematic instead of adding themthe git repo contains the schematics. It would be better to link to the corresponding repo (https://source.puri.sm/Librem5/l5-schematic) instead since double maintenance outdates quickly.the git repo contains the schematics. It would be better to link to the corresponding repo (https://source.puri.sm/Librem5/l5-schematic) instead since double maintenance outdates quickly.https://source.puri.sm/Librem5/feedbackd/-/issues/34New release2021-01-25T10:34:54ZDylan Van Asscheme@dylanvanassche.beNew releaseAfter merging !44, a new release would be helpful for integrating these changes in other distributions :)After merging !44, a new release would be helpful for integrating these changes in other distributions :)https://source.puri.sm/Librem5/feedbackd/-/issues/32End feedback when the client vanished2021-01-25T10:35:49ZGuido GuntherEnd feedback when the client vanishedWe should watch DBus names of clients and cancel their feedbacks when they go away (via https://developer.gnome.org/gio/stable/gio-Watching-Bus-Names.html#g-bus-watch-name)We should watch DBus names of clients and cancel their feedbacks when they go away (via https://developer.gnome.org/gio/stable/gio-Watching-Bus-Names.html#g-bus-watch-name)https://source.puri.sm/Librem5/gnome-control-center/-/issues/48Cellular: Odd spacing at the top2021-01-25T15:02:42ZTobias BernardCellular: Odd spacing at the topThere's a bit too much margin before the start of the content on the main view:
![image](/uploads/a54dfe95c50d0291cdbcfbf5ffcfb3ff/image.png)
I'd reduce it to about half, or whatever the standard value on other panels is.There's a bit too much margin before the start of the content on the main view:
![image](/uploads/a54dfe95c50d0291cdbcfbf5ffcfb3ff/image.png)
I'd reduce it to about half, or whatever the standard value on other panels is.https://source.puri.sm/Librem5/linux/-/issues/259CONFIG_COMMON_CLK_BD718XX=y hangs at boot2021-01-26T05:50:33ZSebastian KrzyszkowiakCONFIG_COMMON_CLK_BD718XX=y hangs at bootWhen `CONFIG_COMMON_CLK_BD718XX` is set to be built-in, the kernel hangs before handing the control over to the init process. Tested on 5.9/imx8-current-librem5.When `CONFIG_COMMON_CLK_BD718XX` is set to be built-in, the kernel hangs before handing the control over to the init process. Tested on 5.9/imx8-current-librem5.https://source.puri.sm/Librem5/feedbackd-device-themes/-/issues/1Create release2021-01-26T13:09:25ZDylan Van Asscheme@dylanvanassche.beCreate releaseNo release is available yet for this package, a release would be helpful for integrating it in other distributions :)No release is available yet for this package, a release would be helpful for integrating it in other distributions :)https://source.puri.sm/Librem5/Apps_Issues/-/issues/195Build for byzantium by deault too2021-01-26T14:14:06ZGuido GuntherBuild for byzantium by deault tooAlready discussed but let's have a bug so we can track byzantium progressAlready discussed but let's have a bug so we can track byzantium progresshttps://source.puri.sm/Librem5/OS-issues/-/issues/53User instance of systemd for session management2021-01-26T14:23:07ZGuido GuntherUser instance of systemd for session managementsee https://wiki.gnome.org/Initiatives/SystemdUser
Systemd units have more fine grained control and don't require us to register via gnome sessions's dbus api.
related:
- https://www.freedesktop.org/software/systemd/man/systemd.specia...see https://wiki.gnome.org/Initiatives/SystemdUser
Systemd units have more fine grained control and don't require us to register via gnome sessions's dbus api.
related:
- https://www.freedesktop.org/software/systemd/man/systemd.special.html#id-1.7.3
- https://github.com/swaywm/sway/wiki/Systemd-integrationhttps://source.puri.sm/Librem5/geary/-/issues/2Needs an adaptive and unsloppy build for byzantium2021-01-26T15:12:14ZGuido GuntherNeeds an adaptive and unsloppy build for byzantiumIf this package can't use the version in byzantium (currently 3.36.2-1) please provide an adpaptive (working on laptop and phones) and unsloppy build. See https://source.puri.sm/Librem5/pureos-store/-/issues/4.If this package can't use the version in byzantium (currently 3.36.2-1) please provide an adpaptive (working on laptop and phones) and unsloppy build. See https://source.puri.sm/Librem5/pureos-store/-/issues/4.https://source.puri.sm/Librem5/debs/gnome-clocks/-/issues/27Needs an adaptive and unsloppy build for byzantium2021-01-26T15:57:15ZGuido GuntherNeeds an adaptive and unsloppy build for byzantiumIf this package can't use the version in byzantium (currently 3.38.0-2) please provide an adaptive (working on laptop and phones) and unsloppy build. See pureos-store#4.If this package can't use the version in byzantium (currently 3.38.0-2) please provide an adaptive (working on laptop and phones) and unsloppy build. See pureos-store#4.https://source.puri.sm/Librem5/linux/-/issues/234DP does not recover from display blank2021-01-26T17:20:36ZGuido GuntherDP does not recover from display blankAt least with my 2-lane hub on the unblank after a power save screen blank i only (most of the time) get a cyan colored screen.At least with my 2-lane hub on the unblank after a power save screen blank i only (most of the time) get a cyan colored screen.EvgGuido GuntherGuido Guntherhttps://source.puri.sm/Librem5/debs/gnome-bluetooth/-/issues/2Needs an adaptive and unsloppy build for byzantium2021-01-27T10:01:01ZGuido GuntherNeeds an adaptive and unsloppy build for byzantiumIf this package can't use the version in byzantium (currently 3.34.3-2) please provide an adpaptive (working on laptop and phones) and unsloppy build. See https://source.puri.sm/Librem5/pureos-store/-/issues/4.If this package can't use the version in byzantium (currently 3.34.3-2) please provide an adpaptive (working on laptop and phones) and unsloppy build. See https://source.puri.sm/Librem5/pureos-store/-/issues/4.https://source.puri.sm/Librem5/debs/gnome-clocks/-/issues/7Clocks landscape adaptive design2021-01-27T11:30:06ZTodd WeaverClocks landscape adaptive designThis issue may be highlighting a larger design decision, which is portrait 'apps' and landscape 'apps', combined with apps that can do both.
Web could be both portrait and landscape, while videos could be landscape only, while clocks ma...This issue may be highlighting a larger design decision, which is portrait 'apps' and landscape 'apps', combined with apps that can do both.
Web could be both portrait and landscape, while videos could be landscape only, while clocks maybe could be portrait only (I don't know and will leave that to the designers).
Clocks works well in portrait, but then switching to landscape it does not work very well.
![clocks-landscape](/uploads/03447062226f3fe6dbe203196210019d/clocks-landscape.webm)Heather EllsworthHeather Ellsworthhttps://source.puri.sm/Librem5/debs/gnome-clocks/-/issues/6Monospaced font2021-01-27T11:32:01ZbalpingMonospaced fontI've seen your [demo video](https://www.youtube.com/watch?v=GbLHlS0-q9k) that was posted recently. I think for the timer (and for the clock), the font should be replaced by a monospaced one to avoid the text "wobbling".I've seen your [demo video](https://www.youtube.com/watch?v=GbLHlS0-q9k) that was posted recently. I think for the timer (and for the clock), the font should be replaced by a monospaced one to avoid the text "wobbling".https://source.puri.sm/Librem5/developer.puri.sm/-/issues/174Update flashing instructions2021-01-27T12:08:49ZGuido GuntherUpdate flashing instructionsdogwood and later are considerably easier to flash (and give more optical feedback) than the steps in https://developer.puri.sm/Librem5/Development_Environment/Phone/Troubleshooting/Reflashing_the_Phone.html#prepare-the-phone
- turn all...dogwood and later are considerably easier to flash (and give more optical feedback) than the steps in https://developer.puri.sm/Librem5/Development_Environment/Phone/Troubleshooting/Reflashing_the_Phone.html#prepare-the-phone
- turn all hks off
- remove battery
- hold vol+
- insert usb-c cable -> red led blinks (no green led)
- insert battery -> red led is constantly on
- lsusb shows device
- start flashing
(no timing requirements, etc)
You can use the same steps to recover from a dead battery by just skipping the last step.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/180reflashing the phone: Add udev rule details2021-01-27T12:11:59ZGuido Guntherreflashing the phone: Add udev rule detailsA new mfgtool is released so once that enters PureOS we should add running that for setting up the udev rules.A new mfgtool is released so once that enters PureOS we should add running that for setting up the udev rules.https://source.puri.sm/Librem5/debs/gnome-clocks/-/issues/9Shouldn't geolocate automatically2021-01-27T13:12:57ZAdrien PlazasShouldn't geolocate automaticallyGeolocalization should be opt-in, for privacy reasons.Geolocalization should be opt-in, for privacy reasons.https://source.puri.sm/Librem5/arm-trusted-firmware/-/issues/2Needs a version in byzatium2021-01-27T14:46:07ZGuido GuntherNeeds a version in byzatiumOtherwise we're not self hosting - debian ships a newer ATF that conflicts with our 2.0 version.Otherwise we're not self hosting - debian ships a newer ATF that conflicts with our 2.0 version.