Librem5 issueshttps://source.puri.sm/groups/Librem5/-/issues2022-06-23T19:22:43Zhttps://source.puri.sm/Librem5/debs/libhandy-1/-/issues/3New upstrream version 1.6.22022-06-23T19:22:43ZGuido GuntherNew upstrream version 1.6.2Byzantium currently only carries 1.5Byzantium currently only carries 1.5https://source.puri.sm/Librem5/developer.puri.sm/-/issues/184Modernize tutorials for recent lilbhandy2021-04-03T11:00:55ZGuido GuntherModernize tutorials for recent lilbhandyThe python tutorials at https://source.puri.sm/Librem5/example-apps are outdated since they still use Libhandy-0 instead of libhandy-1,see e.g. https://source.puri.sm/Librem5/example-apps/adaptive-ui-title-bar/-/blob/master/src/main.py#L...The python tutorials at https://source.puri.sm/Librem5/example-apps are outdated since they still use Libhandy-0 instead of libhandy-1,see e.g. https://source.puri.sm/Librem5/example-apps/adaptive-ui-title-bar/-/blob/master/src/main.py#L12 - several patterns changed so it would be great to have them updated.
The `handy-1-demo` app can be used as a reference for common patterns.
(it might also make sense to move the demos to gnome.org at some point later on since they could help there as well)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/29Use a `feedbackd` group for file permissions2020-11-14T14:54:02ZGuido GuntherUse a `feedbackd` group for file permissionsWe shouldn't abuse the video group but rather use a daemon specific `feedbackd` group.We shouldn't abuse the video group but rather use a daemon specific `feedbackd` group.https://source.puri.sm/Librem5/feedbackd/-/issues/27Allow for per device profiles2021-01-11T09:26:30ZGuido GuntherAllow for per device profilesWe currently just have a per default profile, we could make feedbackd automatically pick a theme based on the DT model if that exists. this would help #26
We could e.g. look at `/u/s/feedbackd/<model>/default.json` before looking at `/u...We currently just have a per default profile, we could make feedbackd automatically pick a theme based on the DT model if that exists. this would help #26
We could e.g. look at `/u/s/feedbackd/<model>/default.json` before looking at `/u/s/feedbackd/default.json`.https://source.puri.sm/Librem5/Apps_Issues/-/issues/187Package wlr-randr2021-03-18T07:53:45ZSebastian KrzyszkowiakPackage wlr-randrJust noticed that I have wlr-randr (https://github.com/emersion/wlr-randr) installed manually in /usr/local on my phone. It's an insanely useful little utility that would be great to have in the repositories.Just noticed that I have wlr-randr (https://github.com/emersion/wlr-randr) installed manually in /usr/local on my phone. It's an insanely useful little utility that would be great to have in the repositories.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/debs/ModemManager/-/issues/34Submitting udev rule upstream?2020-06-29T20:07:34ZClayton CraftSubmitting udev rule upstream?I am using upstream ModemManager (the latest release, which includes the series submitted by @bob.ham) on postmarketOS with Phosh/Calls, and placing/receiving phone calls was really unreliable for me. I needed to include the udev rule in...I am using upstream ModemManager (the latest release, which includes the series submitted by @bob.ham) on postmarketOS with Phosh/Calls, and placing/receiving phone calls was really unreliable for me. I needed to include the udev rule in this patch for things to start working: 27113daef1af7c2767d0a48d2ae6c5176d1c8f3e
Is there any reason why this wasn't submitted upstream?https://source.puri.sm/Librem5/feedbackd/-/issues/12feedbackd manpage2020-07-04T11:39:30ZGuido Guntherfeedbackd manpagethe doc/ folder could use a feebackd manapage using the given docbook structure, examples could be taken from gio or modemmanagerthe doc/ folder could use a feebackd manapage using the given docbook structure, examples could be taken from gio or modemmanagerhttps://source.puri.sm/Librem5/feedbackd/-/issues/3Use yaml for feedback profiles2020-04-17T16:57:08ZGuido GuntherUse yaml for feedback profilesit's easier to parse and write than json.it's easier to parse and write than json.