Librem5 issueshttps://source.puri.sm/groups/Librem5/-/issues2018-07-03T08:44:31Zhttps://source.puri.sm/Librem5/virtboard/-/issues/1Add CI file2018-07-03T08:44:31ZDorota CzaplejewiczAdd CI fileA minimal file should contain building instructions only.A minimal file should contain building instructions only.Dorota CzaplejewiczDorota Czaplejewiczhttps://source.puri.sm/Librem5/developer.puri.sm/-/issues/32Document widget size request, homgeneous etc2020-02-04T14:45:37ZGuido GuntherDocument widget size request, homgeneous etcMany apps look ugly when run on a small screen. We should document the best way to prevent e.g. buttons getting huge, alignment getting messed up etc. when running in larger displays. @adrien.plazas that might overlap with purism-gtk-exa...Many apps look ugly when run on a small screen. We should document the best way to prevent e.g. buttons getting huge, alignment getting messed up etc. when running in larger displays. @adrien.plazas that might overlap with purism-gtk-examples. Should we track these things there?https://source.puri.sm/Librem5/Apps_Issues/-/issues/36QEMU VM should use phone like video mode2018-07-04T10:23:35ZGuido GuntherQEMU VM should use phone like video mode(Although this is likely not the perfect place for this but since this spans several projects I'll put it here):
We want the QEMU VM have a phone like resolution by default. Therefore we need to
- [x] Support this in wlroots: https://...(Although this is likely not the perfect place for this but since this spans several projects I'll put it here):
We want the QEMU VM have a phone like resolution by default. Therefore we need to
- [x] Support this in wlroots: https://github.com/swaywm/wlroots/pull/1095
- [x] Update our wlroots/rootston (either with a new upstream version or the patches from above)
- [x] Add the right configuration to rootston.ini, luckily QXL uses a specific output name (Virtual-1):
```
[output:Virtual-1]
modeline = 87.25 720 776 848 976 1440 1443 1453 1493 -hsync +vsync
mode = 720x1440
scale = 2
```Dorota CzaplejewiczDorota Czaplejewiczhttps://source.puri.sm/Librem5/virtboard/-/issues/2Does not fit on 720x1440 && scale = 22018-08-28T13:15:26ZGuido GuntherDoes not fit on 720x1440 && scale = 2Starting virtboad on a phone like geometry (see above) only shows the right half of the keyboard. It should scale so all characters are visible.Starting virtboad on a phone like geometry (see above) only shows the right half of the keyboard. It should scale so all characters are visible.Dorota CzaplejewiczDorota Czaplejewiczhttps://source.puri.sm/Librem5/virtboard/-/issues/3Does not hide when there's no text input2019-10-11T12:54:12ZGuido GuntherDoes not hide when there's no text inputEpic: https://source.puri.sm/Librem5/use-cases/issues/22
Even on a completely empty screen the keyboad is shown. It should only show when a widget wants to receive text input (or explicitly instructed by the user)
Blocked by https://so...Epic: https://source.puri.sm/Librem5/use-cases/issues/22
Even on a completely empty screen the keyboad is shown. It should only show when a widget wants to receive text input (or explicitly instructed by the user)
Blocked by https://source.puri.sm/Librem5/wlroots/merge_requests/35 and !21Dorota CzaplejewiczDorota Czaplejewiczhttps://source.puri.sm/Librem5/wlroots/-/issues/8Add support for input method related protocols2023-07-24T09:06:32ZDorota CzaplejewiczAdd support for input method related protocolsUpstream issue: https://github.com/swaywm/wlroots/pull/892
Needed work:
* [ ] `input-method-v2`
* [ ] `text-input-v3`
* [ ] popping up when focusing a text edit field
* [ ] handling the passing of events
* handling the surface posi...Upstream issue: https://github.com/swaywm/wlroots/pull/892
Needed work:
* [ ] `input-method-v2`
* [ ] `text-input-v3`
* [ ] popping up when focusing a text edit field
* [ ] handling the passing of events
* handling the surface positioning in case of floating input method window (optional)A1: Support fully featured on screen keyboardDorota CzaplejewiczDorota Czaplejewiczhttps://source.puri.sm/Librem5/virtboard/-/issues/5Drop unused clients2018-07-03T11:01:10ZGuido GuntherDrop unused clientsclients/ contains lots of unused clients like desktop-shell and ivi-shell-user-interface which makes grepping harder than necessary.clients/ contains lots of unused clients like desktop-shell and ivi-shell-user-interface which makes grepping harder than necessary.Dorota CzaplejewiczDorota Czaplejewiczhttps://source.puri.sm/Librem5/wlroots/-/issues/9Crash when second virtual-keyboard is used2023-07-24T09:06:32ZDorota CzaplejewiczCrash when second virtual-keyboard is usedwlroots gets some sort of memory corruption when the second virtual-keyboard client tries to interact with the interface after the first one is gone.
To reproduce:
1. Start wlroots
2. Start virtboard
3. Press a button to trigger bindin...wlroots gets some sort of memory corruption when the second virtual-keyboard client tries to interact with the interface after the first one is gone.
To reproduce:
1. Start wlroots
2. Start virtboard
3. Press a button to trigger binding
4. Close virtboard
5. Start virtboard
6. Press a button
The crash is probably related to not destroying `wlr_input_device` associated to the virtual `wlr_keyboard` before freeing both.Dorota CzaplejewiczDorota Czaplejewiczhttps://source.puri.sm/Librem5/developer.puri.sm/-/issues/33Add qemu-x86_64 image to storage.puri.sm2018-07-04T17:07:49ZHeather EllsworthAdd qemu-x86_64 image to storage.puri.smBy storing the qemu-x86_64 image to some place on storage.puri.sm, we could direct users to a cleaner link that is not some jenkins build link.
I would like to see a latest tested image in https://storage.puri.sm/librem5/binaries/unstab...By storing the qemu-x86_64 image to some place on storage.puri.sm, we could direct users to a cleaner link that is not some jenkins build link.
I would like to see a latest tested image in https://storage.puri.sm/librem5/binaries/unstable/latest/ and I would be happy to periodically manually update this image to a new tested one.
I prefer the latest folder to https://storage.puri.sm/librem5/binaries/ci/ because it is a pain to have to frequently go and clean out old images. There are already plenty of old images for uboot and the kernel. If we add the qemu-x86_64 images to this, then the folder will fill up even quicker and it will become obvious that someone needs to go remove old images only when there is no space left.https://source.puri.sm/Librem5/image-builder/-/issues/8Need to enlarge the filesystem/partition on first boot2019-03-26T10:48:16ZGuido GuntherNeed to enlarge the filesystem/partition on first bootOn SD-Cards we should enlarge the filesystem / partition to take up all the space on first boot, scripts could be take from the raspberry pi. This would also help users using the qemu image sine they'd only need to resize the qcow2.
- [...On SD-Cards we should enlarge the filesystem / partition to take up all the space on first boot, scripts could be take from the raspberry pi. This would also help users using the qemu image sine they'd only need to resize the qcow2.
- [X] enlarge partition
- [ ] grow filesystem
- [X] [use initramfs on the ~~armhf/~~arm8 boards](https://source.puri.sm/Librem5/image-builder/issues/24)Dorota CzaplejewiczDorota Czaplejewiczhttps://source.puri.sm/Librem5/image-builder/-/issues/9Make qemu image larger2018-07-17T18:11:27ZGuido GuntherMake qemu image largerThere's no reason why we wouldn' make the qemu image 10GB or similar. It would be even better to convert the raw image to a qcow2 in the qemu case at the end of the build, we could then make it 100GB and it would grow as needed.
The fi...There's no reason why we wouldn' make the qemu image 10GB or similar. It would be even better to convert the raw image to a qcow2 in the qemu case at the end of the build, we could then make it 100GB and it would grow as needed.
The first part isn't hard: make what's passed to --size a variable, default it in conf/board to the current value and use a bigger value for qemu.
The second half is one qemu-img invoction.https://source.puri.sm/Librem5/Apps_Issues/-/issues/37Modernize Seahorse2021-10-19T12:28:57ZGuido GuntherModernize SeahorseIt still has a menu bar and needs HdyLeaflet to fit on screen, etc.It still has a menu bar and needs HdyLeaflet to fit on screen, etc.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
```https://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/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/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/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/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/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/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.