Librem5 issueshttps://source.puri.sm/groups/Librem5/-/issues2021-11-11T10:42:34Zhttps://source.puri.sm/Librem5/debs/kgx/-/issues/3Selecting and copying text via touch doesn't seem to work2021-11-11T10:42:34ZDorota CzaplejewiczSelecting and copying text via touch doesn't seem to workSomeone complained about this in the forums:
https://forums.puri.sm/t/terminal-to-clipboard/8293/7Someone complained about this in the forums:
https://forums.puri.sm/t/terminal-to-clipboard/8293/7https://source.puri.sm/Librem5/OS-issues/-/issues/97No video signal when connecting to a USB-C monitor2020-10-08T17:09:14ZDanNo video signal when connecting to a USB-C monitor# What problem did you encounter
No video on USB-C
## What is the actual behaviour?
No video signal on USB-C
## What is the expected behaviour?
Video signal on USB-C with "gnome" desktop
## How to reproduce
Connect a USB-C compati...# What problem did you encounter
No video on USB-C
## What is the actual behaviour?
No video signal on USB-C
## What is the expected behaviour?
Video signal on USB-C with "gnome" desktop
## How to reproduce
Connect a USB-C compatible monitor to Librem5 Chestnut USB-C port.
See no signal on monitor.
# What hardware are you running on?
- [ ] amd64 qemu image
- [ ] Librem5 devkit
- [x] Librem5 Chestnut Phone
# Relevant OS information
## Which kernel are you using?
`Linux pietro 5.3.0-librem5-h1 #1 SMP PREEMPT Tue Dec 24 15:42:56 CET 2019 aarch64 GNU/Linux`
## Which OS are you using?
```
ID=pureos
NAME=PureOS
PRETTY_NAME=PureOS
VERSION_ID=9.0
VERSION_CODENAME=amber
HOME_URL="https://pureos.net/"
SUPPORT_URL="https://puri.sm/faq/#faq-WherecanIfindoutmoreaboutPureOS"
BUG_REPORT_URL="https://tracker.pureos.net/"
LOGO=pureos-logo-icon
```
## Any other information that may be helpful?
* Monitor is a Samsung LS24H850QFNXZAhttps://source.puri.sm/Librem5/linux/-/issues/141dcss: forward hdmi to 5.x2020-03-17T13:59:20ZGuido Guntherdcss: forward hdmi to 5.xwe left that behind in 4.18 and only moved the dsi part forward. gettings this to work on the devkit (while using mxsfb for dsi) would be a first step towards dual screen mode and future phone usage via usb-c.we left that behind in 4.18 and only moved the dsi part forward. gettings this to work on the devkit (while using mxsfb for dsi) would be a first step towards dual screen mode and future phone usage via usb-c.https://source.puri.sm/Librem5/linux/-/issues/142dcss: display port support2023-10-03T16:17:47ZGuido Guntherdcss: display port supportneeded since the phone does dp over usb-cneeded since the phone does dp over usb-chttps://source.puri.sm/Librem5/OS-issues/-/issues/98DHCP fails after battery goes flat2020-11-18T01:49:49ZDorota CzaplejewiczDHCP fails after battery goes flat# What problem did you encounter
dhclient (and NetworkManager too) fails when starting the phone after the battery is dead enough for the RTC to reset.
## How to reproduce
1. Connect to a host runnig DHCP (can be usb0)
2. Set system d...# What problem did you encounter
dhclient (and NetworkManager too) fails when starting the phone after the battery is dead enough for the RTC to reset.
## How to reproduce
1. Connect to a host runnig DHCP (can be usb0)
2. Set system date to Wed Dec 31 12:03:03 UTC 2155
3. dhclient -v usb0
## What is the actual behaviour?
No IPv4 address on WiFi or usb0 (no way to get system updates from Purism IPv4 servers)
dhclient output:
```
purism@pureos:~$ sudo dhclient -4 -v usb0
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/usb0/1e:4f:b8:42:6c:f3
Sending on LPF/usb0/1e:4f:b8:42:6c:f3
Sending on Socket/fallback
DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 6
Unable to set up timer: out of range
If you think you have received this message due to a bug rather
than a configuration issue please read the section on submitting
bugs on either our web page at www.isc.org or in the README file
before submitting a bug. These pages explain the proper
process and the information we find helpful for debugging.
exiting.
```
## What is the expected behaviour?
DHCP is independent of system date.
# What hardware are you running on?
Birch
# Relevant OS information
## Which kernel are you using?
Linux pureos 5.3.0-librem5-h1 #1 SMP PREEMPT Mon Dec 23 13:31:19 UTC 2019 aarch64 GNU/Linux
## Which OS are you using?
Amber
## Any other information that may be helpful?
```
root@pureos:/home/purism# dhclient --version
isc-dhclient-4.4.1
```https://source.puri.sm/Librem5/linux/-/issues/143Redpine module needs power cycle after boot on Chestnut2023-10-03T16:17:47ZAngus Ainslieangus.ainslie@puri.smRedpine module needs power cycle after boot on ChestnutThe Wifi card is not automatically detected on chestnut flipping the HKS for Wifi gets the modules to probe correctly.The Wifi card is not automatically detected on chestnut flipping the HKS for Wifi gets the modules to probe correctly.Angus Ainslieangus.ainslie@puri.smAngus Ainslieangus.ainslie@puri.smhttps://source.puri.sm/Librem5/OS-issues/-/issues/99Shorten the systemd stop timeout2020-01-15T03:52:49ZSebastian KrzyszkowiakShorten the systemd stop timeoutThe default systemd stop timeout for jobs is 90 seconds, which seems quite excessive for a mobile phone, possibly making the shutdown sequence very long.
On my device I've changed that by editing /etc/systemd/system.conf:
```
DefaultTim...The default systemd stop timeout for jobs is 90 seconds, which seems quite excessive for a mobile phone, possibly making the shutdown sequence very long.
On my device I've changed that by editing /etc/systemd/system.conf:
```
DefaultTimeoutStopSec=15s
```https://source.puri.sm/Librem5/gnome-initial-setup/-/issues/17CI doesn't produce .deb files2020-01-16T11:07:01ZDorota CzaplejewiczCI doesn't produce .deb filesThat would make testing easier.That would make testing easier.https://source.puri.sm/Librem5/uboot-imx/-/issues/17i2c dev 2 not properly probing devices in u-boot2022-04-26T14:53:42ZAngus Ainslieangus.ainslie@puri.smi2c dev 2 not properly probing devices in u-boot```
u-boot=> gpio set GPIO1_4
gpio: pin GPIO1_4 (gpio 4) value is 1
u-boot=> i2c dev 2
Setting bus to 2
u-boot=> i2c probe 0x1a
Valid chip addresses:wait_for_sr_state: Arbitration lost sr=93 cr=80 state=2020
i2c_init_transfer: failed for...```
u-boot=> gpio set GPIO1_4
gpio: pin GPIO1_4 (gpio 4) value is 1
u-boot=> i2c dev 2
Setting bus to 2
u-boot=> i2c probe 0x1a
Valid chip addresses:wait_for_sr_state: Arbitration lost sr=93 cr=80 state=2020
i2c_init_transfer: failed for chip 0x1a retry=0
wait_for_sr_state: Arbitration lost sr=93 cr=80 state=2020
i2c_init_transfer: failed for chip 0x1a retry=1
wait_for_sr_state: Arbitration lost sr=93 cr=80 state=2020
i2c_init_transfer: failed for chip 0x1a retry=2
i2c_init_transfer: give up i2c_regs=0x30a40000
```
The bus probes fine in the kernelhttps://source.puri.sm/Librem5/librem5-user-docs-common/-/issues/14Add Chestnut known issues2020-01-28T00:29:24ZDavid BoddieAdd Chestnut known issuesAdd a Chestnut section to the [Known Issues](https://docs.puri.sm/Librem_5/Known_Issues.html) page.Add a Chestnut section to the [Known Issues](https://docs.puri.sm/Librem_5/Known_Issues.html) page.David BoddieDavid Boddiehttps://source.puri.sm/Librem5/quickstart-guide/-/issues/18Update the guide with new post-Chestnut screenshots2020-07-11T19:20:18ZDavid BoddieUpdate the guide with new post-Chestnut screenshotsSome features and workflow may have changed since Chestnut was shipped.Some features and workflow may have changed since Chestnut was shipped.David BoddieDavid Boddiehttps://source.puri.sm/Librem5/gnome-control-center/-/issues/89Sound Output Settings Persist Reboots, but Aren't Reapplied2020-03-02T19:58:07ZKyle RankinSound Output Settings Persist Reboots, but Aren't Reapplied# Problem
When changing the audio output device in Control Center, the output device does change (such as in the case of changing to the speakerphone speaker so you can hear music output from Lollypop), and upon reboot, if you go to the ...# Problem
When changing the audio output device in Control Center, the output device does change (such as in the case of changing to the speakerphone speaker so you can hear music output from Lollypop), and upon reboot, if you go to the Control Center, the output device is still what you set it to, however if you play music through Lollypop, it now outputs from the headset speaker instead of the (louder) speakerphone speaker. Changing the audio device to something else and then back to the speakerphone speaker causes it to output through the louder speaker.
# Expected Behavior
The audio output settings in Settings should reflect the actual settings on the device. If these settings persist reboot, they should be reapplied, or else the settings should reflect the actual state.
# Steps to Reproduce
* Play audio on default audio output device
* Change the default audio output to a different output device (such as from headset to speakerphone)
* Play audio and confirm audio outputs from the new device
* Reboot
* Open Settings and confirm the new audio output device is still set
* Play audio and notice that audio outputs from the old device
* Switch to old device and back to new device
* Notice audio now outputs on new devicehttps://source.puri.sm/Librem5/OS-issues/-/issues/100Flicker-free booting2020-03-31T23:37:16ZSebastian KrzyszkowiakFlicker-free bootingOpening an issue just to write it down somewhere.
With plymouth, the boot experience is pretty nice already, although some adjustments can be still made:
- a `vt.global_cursor_default=0` param in kernel cmdline disables the blinking c...Opening an issue just to write it down somewhere.
With plymouth, the boot experience is pretty nice already, although some adjustments can be still made:
- a `vt.global_cursor_default=0` param in kernel cmdline disables the blinking cursor
- `systemctl disable getty@tty1.service` disables the console login prompt that blinks shortly before phoc starts
- we'll need to find a way to prevent fsck message from appearing in plymouth, since it usually blinks just for a split second, creating unnecessary flicker
- a fade-in (or even cross-fade, depending on plymouth theme design) when starting phoc would be nice toohttps://source.puri.sm/Librem5/OS-issues/-/issues/101ETNA_MESA_DEBUG=no_supertile breaks OpenGL apps2020-03-02T18:59:59ZSebastian KrzyszkowiakETNA_MESA_DEBUG=no_supertile breaks OpenGL appsWith current Mesa version, most of the games I tried appear broken with `ETNA_MESA_DEBUG=no_supertile`, which on the other hand is necessary for phoc to function correctly. Ideally this variable would apply only to phoc and not any other...With current Mesa version, most of the games I tried appear broken with `ETNA_MESA_DEBUG=no_supertile`, which on the other hand is necessary for phoc to function correctly. Ideally this variable would apply only to phoc and not any other application.
An example of artefacts appearing with `no_supertile` option (it works fine with `ETNA_MESA_DEBUG` unset):
![etna](/uploads/d95f25376bf538faee9581437b0c9b30/etna.png)https://source.puri.sm/Librem5/debs/epiphany/-/issues/13Webapp mode uses two bars even though it would fit on one2020-12-02T10:32:26ZSebastian KrzyszkowiakWebapp mode uses two bars even though it would fit on oneWebapps waste quite a lot of vertical space on blank UI with both the top and bottom bars visible, even though all the controls would actually fit on the top bar:
![ddg](/uploads/db42269c6d7cbf1c43027baa3818fe5a/ddg.png)Webapps waste quite a lot of vertical space on blank UI with both the top and bottom bars visible, even though all the controls would actually fit on the top bar:
![ddg](/uploads/db42269c6d7cbf1c43027baa3818fe5a/ddg.png)https://source.puri.sm/Librem5/debs/gtk/-/issues/17Touchscreen scrolling needs adjustments2020-10-21T20:05:16ZSebastian KrzyszkowiakTouchscreen scrolling needs adjustmentsGTK's touchscreen scrolling isn't exactly pleasurable to use. The most annoying issue with it is velocity calculation when the finger is released.
When the finger isn't moving, releasing it shouldn't trigger further scrolling. However, ...GTK's touchscreen scrolling isn't exactly pleasurable to use. The most annoying issue with it is velocity calculation when the finger is released.
When the finger isn't moving, releasing it shouldn't trigger further scrolling. However, with GTK it's extremely easy to trigger either on devkit or the phone, and even on my laptop - which is something that doesn't happen in other apps (like Firefox, Chromium or Qt-based ones).https://source.puri.sm/Librem5/OS-issues/-/issues/102Disabling suspend after 1 minutes of idle remove the option to re-enable for ...2020-01-09T16:06:02ZDanDisabling suspend after 1 minutes of idle remove the option to re-enable for 1minute# What problem did you encounter
After disabling auto suspend after 1 minute, you loose the option to re-enable auto suspend after 1 minute.
## What is the actual behaviour?
The minimum suspend delay is now 15minutes you can't see 1 m...# What problem did you encounter
After disabling auto suspend after 1 minute, you loose the option to re-enable auto suspend after 1 minute.
## What is the actual behaviour?
The minimum suspend delay is now 15minutes you can't see 1 minute delay before suspend.
## What is the expected behaviour?
See 1 minute delay before suspend
## How to reproduce
`settings -> Power -> Suspend & Power Button -> Automatic Suspend`
`Turn off On Battery Power`
# What hardware are you running on?
- [ ] amd64 qemu image
- [ ] Librem5 devkit
- [x] Librem5 Chestnut
# Relevant OS information
## Which kernel are you using?
`Linux pietro 5.3.0-librem5-h1 #1 SMP PREEMPT Tue Jan 7 11:48:44 UTC 2020 aarch64 GNU/Linux`
## Which OS are you using?
```
ID=pureos
NAME=PureOS
PRETTY_NAME=PureOS
VERSION_ID=9.0
VERSION_CODENAME=amber
HOME_URL="https://pureos.net/"
SUPPORT_URL="https://puri.sm/faq/#faq-WherecanIfindoutmoreaboutPureOS"
BUG_REPORT_URL="https://tracker.pureos.net/"
LOGO=pureos-logo-icon
```https://source.puri.sm/Librem5/developer.puri.sm/-/issues/150Add Chestnut hardware information2020-01-28T00:32:16ZDavid BoddieAdd Chestnut hardware informationIncluding [schematics](https://source.puri.sm/Librem5/l5-schematic) and quick start guide.Including [schematics](https://source.puri.sm/Librem5/l5-schematic) and quick start guide.David BoddieDavid Boddiehttps://source.puri.sm/Librem5/gnome-initial-setup/-/issues/18please drop 6 digit pin restriction2020-01-27T03:08:43ZGuido Guntherplease drop 6 digit pin restrictionphosh supports arbitrary length now. Please add a
`Breaks: phosh (<< 0.1.7)`
to `debian/control{,.in}` to make sure we don't end up on a system with that phosh.phosh supports arbitrary length now. Please add a
`Breaks: phosh (<< 0.1.7)`
to `debian/control{,.in}` to make sure we don't end up on a system with that phosh.https://source.puri.sm/Librem5/gnome-control-center/-/issues/90please drop 6 digit pin restriction2021-01-15T15:39:54ZGuido Guntherplease drop 6 digit pin restrictionphosh supports arbitrary length now. Please add a
`Breaks: phosh (<< 0.1.7)`
to `debian/control{,.in}` to make sure we don't end up on a system with that phosh.phosh supports arbitrary length now. Please add a
`Breaks: phosh (<< 0.1.7)`
to `debian/control{,.in}` to make sure we don't end up on a system with that phosh.