Librem5 issueshttps://source.puri.sm/groups/Librem5/-/issues2020-11-14T08:52:08Zhttps://source.puri.sm/Librem5/gnome-online-accounts/-/issues/4libreme.one dialogs not adaptive2020-11-14T08:52:08ZGuido Guntherlibreme.one dialogs not adaptiveThe account dialog is too wide (and basically copied from another provider) but the dialogs look out of place overall
@tobias.bernard is there design work already?
@mohammed.sadiq could you help with making it adaptive? It seems the g...The account dialog is too wide (and basically copied from another provider) but the dialogs look out of place overall
@tobias.bernard is there design work already?
@mohammed.sadiq could you help with making it adaptive? It seems the goaprovider base class could be improved already to use a full screen sized dialog instead of the tiny one?https://source.puri.sm/Librem5/gnome-software/-/issues/30Software Update details shows blank page on package details2020-01-29T22:44:06ZTodd WeaverSoftware Update details shows blank page on package detailsI am not sure what the design flow goals are, but this page is empty.
Reproduction:
1. OS Update
2. Click Details (See packages update list)
3. Click on a package
4. See a blank page.
Step 1:
![2020-01-29-5707](/uploads/8fe5d92ed26a21...I am not sure what the design flow goals are, but this page is empty.
Reproduction:
1. OS Update
2. Click Details (See packages update list)
3. Click on a package
4. See a blank page.
Step 1:
![2020-01-29-5707](/uploads/8fe5d92ed26a219b7cf7ea411b828157/2020-01-29-5707.png)
Step 2:
![2020-01-29-5721](/uploads/d26f6613f9373c3a377ef9406e6e7b01/2020-01-29-5721.png)
Step 3:
![2020-01-29-5737](/uploads/0dc8e79126bd5421da3d8623dc108bb4/2020-01-29-5737.png)![2020-01-29-5754](/uploads/fd4b57e7359cade1cd2733cb840c97ff/2020-01-29-5754.png)https://source.puri.sm/Librem5/linux/-/issues/156WWAN wakeup from BroadMobi BM818 not working2022-12-05T11:23:56ZBob HamWWAN wakeup from BroadMobi BM818 not workingWe need to check that the BroadMobi BM818 modem will wake up the CPU on an incoming call, etc.
Related issue: ModemManager#29
use-cases#75We need to check that the BroadMobi BM818 modem will wake up the CPU on an incoming call, etc.
Related issue: ModemManager#29
use-cases#75https://source.puri.sm/Librem5/debs/ModemManager/-/issues/29Configure BM818 wakeup2020-02-12T15:32:36ZBob HamConfigure BM818 wakeupConfigure the modem to wake up the CPU on whatever conditions are supported, for example:
* incoming call
* incoing SMS
* network change (change of base station or network type)
* loss of connectivity
* incoming data on the IP data conn...Configure the modem to wake up the CPU on whatever conditions are supported, for example:
* incoming call
* incoing SMS
* network change (change of base station or network type)
* loss of connectivity
* incoming data on the IP data connection, eventually with filtershttps://source.puri.sm/Librem5/debs/ModemManager/-/issues/28Regression: Incoming/Outgoing calls no longer work2020-02-13T15:53:13ZKyle RankinRegression: Incoming/Outgoing calls no longer workWhen I first got my Chestnut device I was able to making outgoing and receive incoming calls successfully. However recently (before calls 0.1.2 so it's not that) I have not been able to receive or send calls. Sometimes during my tests Ca...When I first got my Chestnut device I was able to making outgoing and receive incoming calls successfully. However recently (before calls 0.1.2 so it's not that) I have not been able to receive or send calls. Sometimes during my tests Calls acts as though the call connected (the timer starts) but the other phone (my home line) never rings.
I do not know whether this is a Calls or ModemManager issue so I'm filing it here, as our ModemManager project doesn't seem to have any issues filed yet.
The modem is in a connected state and was able to receive an IP from the tower:
```Jan 28 09:03:48 pureos NetworkManager[502]: <info> [1580231028.8672] modem-broadband[cdc-wdm0]: address 21.251.89.73/30
Jan 28 09:03:48 pureos NetworkManager[502]: <info> [1580231028.8673] modem-broadband[cdc-wdm0]: gateway 21.251.89.74
Jan 28 09:03:48 pureos NetworkManager[502]: <info> [1580231028.8674] modem-broadband[cdc-wdm0]: DNS 10.177.0.34
Jan 28 09:03:48 pureos NetworkManager[502]: <info> [1580231028.8674] modem-broadband[cdc-wdm0]: DNS 10.177.0.210
Jan 28 09:03:48 pureos NetworkManager[502]: <info> [1580231028.8753] modem-broadband[cdc-wdm0]: IPv6 base configuration:
Jan 28 09:03:48 pureos NetworkManager[502]: <info> [1580231028.8755] modem-broadband[cdc-wdm0]: address 2607:fb90:27dd:7931:1974:b23a:adcc:1d74/64
Jan 28 09:03:48 pureos NetworkManager[502]: <info> [1580231028.8756] modem-broadband[cdc-wdm0]: gateway 2607:fb90:27dd:7931:b01f:47d9:d92:c879
Jan 28 09:03:48 pureos NetworkManager[502]: <info> [1580231028.8757] modem-broadband[cdc-wdm0]: DNS fd00:976a::9
Jan 28 09:03:48 pureos NetworkManager[502]: <info> [1580231028.8757] modem-broadband[cdc-wdm0]: DNS fd00:976a::10
```
This was the state of the modem when trying to receive and send the call:
```purism@pureos:~$ mmcli -m 0
-----------------------------
General | dbus path: /org/freedesktop/ModemManager1/Modem/0
| device id: CENSORED
-----------------------------
Hardware | manufacturer: QUALCOMM INCORPORATED
| model: 0
| firmware revision: MPSS.JO.2.0.2.c1.1-00032-9607_GENNS_PACK-1 1 [Feb 25 2019 01:00:00]
| h/w revision: 10000
| supported: gsm-umts, lte
| current: gsm-umts, lte
| equipment id: CENSORED
-----------------------------
System | device: /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.3.auto/usb1/1-1/1-1.2
| drivers: qmi_wwan, option1
| plugin: Generic
| primary port: cdc-wdm0
| ports: ttyUSB0 (qcdm), ttyUSB1 (at), ttyUSB2 (at), ttyUSB3 (at),
| wwan0 (net), cdc-wdm0 (qmi)
-----------------------------
Numbers | own: CENSORED
-----------------------------
Status | lock: sim-pin2
| unlock retries: sim-pin (3), sim-pin2 (10), sim-puk (10), sim-puk2 (10)
| state: connected
| power state: on
| access tech: lte
| signal quality: 34% (cached)
-----------------------------
Modes | supported: allowed: 2g; preferred: none
| allowed: 3g; preferred: none
| allowed: 4g; preferred: none
| allowed: 2g, 3g; preferred: none
| allowed: 2g, 4g; preferred: none
| allowed: 3g, 4g; preferred: none
| allowed: 2g, 3g, 4g; preferred: none
| current: allowed: any; preferred: none
-----------------------------
Bands | supported: pcs, g850, utran-4, utran-5, utran-2, eutran-2, eutran-3,
| eutran-4, eutran-5, eutran-12, eutran-13, eutran-17, eutran-25,
| eutran-26, eutran-41, eutran-66
| current: pcs, g850, utran-4, utran-5, utran-2, eutran-2, eutran-3,
| eutran-4, eutran-5, eutran-12, eutran-13, eutran-17, eutran-25,
| eutran-26, eutran-41, eutran-66
-----------------------------
IP | supported: ipv4, ipv6, ipv4v6
-----------------------------
3GPP | imei: CENSORED
| operator id: CENSORED
| registration: home
-----------------------------
SIM | dbus path: /org/freedesktop/ModemManager1/SIM/0
-----------------------------
Bearer | dbus path: /org/freedesktop/ModemManager1/Bearer/0
```
Here is my latest attempt to make an outgoing call to my home landline:
```Jan 28 09:04:28 pureos ModemManager[516]: transaction 0x26 aborted, but message is not abortable
Jan 28 09:04:28 pureos ModemManager[516]: transaction 0x6 aborted, but message is not abortable
Jan 28 09:04:28 pureos ModemManager[516]: <warn> Reloading stats failed: QMI operation failed: Transaction timed out
Jan 28 09:04:58 pureos ModemManager[516]: transaction 0x7 aborted, but message is not abortable
Jan 28 09:04:58 pureos ModemManager[516]: <warn> Reloading stats failed: QMI operation failed: Transaction timed out
Jan 28 09:05:08 pureos ModemManager[516]: transaction 0x27 aborted, but message is not abortabl
e
Jan 28 09:05:28 pureos ModemManager[516]: transaction 0x8 aborted, but message is not abortable
Jan 28 09:05:28 pureos ModemManager[516]: <warn> Reloading stats failed: QMI operation failed: Transaction timed out
Jan 28 09:05:48 pureos ModemManager[516]: transaction 0x28 aborted, but message is not abortable
Jan 28 09:05:58 pureos ModemManager[516]: transaction 0x9 aborted, but message is not abortable
Jan 28 09:05:58 pureos ModemManager[516]: <warn> Reloading stats failed: QMI operation failed: Transaction timed out
Jan 28 09:06:04 pureos ModemManager[516]: <info> user request to start call
Jan 28 09:06:04 pureos ModemManager[516]: <info> Call state changed: unknown -> dialing (outgoing-started)
Jan 28 09:06:04 pureos ModemManager[516]: <info> call is started
...
Jan 28 09:06:34 pureos ModemManager[516]: <info> Call state changed: dialing -> terminated (unknown)
```
```https://source.puri.sm/Librem5/gnome-control-center/-/issues/110Coredump on control center device name text entry2021-03-18T07:39:40ZTodd WeaverCoredump on control center device name text entryReproduction
1. Go to Settings - Details - About
2. Try to change the Device name, or select all, or shift cursor location in the text area
3. Eventually it will coredump
![librem-5-birch-control-center-coredump-on-device-name-text-entr...Reproduction
1. Go to Settings - Details - About
2. Try to change the Device name, or select all, or shift cursor location in the text area
3. Eventually it will coredump
![librem-5-birch-control-center-coredump-on-device-name-text-entry-2020-01-28](/uploads/1f867fc2248de602c9ece6afafc517f8/librem-5-birch-control-center-coredump-on-device-name-text-entry-2020-01-28.webm)
```
purism@l5b:~$ uname -a
Linux l5b 5.3.0-librem5-h1 #1 SMP PREEMPT Sat Jan 25 09:55:23 CET 2020 aarch64 GNU/Linux
purism@l5b:~$ dpkg -s phosh | grep Version
Version: 0.1.7
purism@l5b:~$ dpkg -s phoc | grep Version
Version: 0.1.5pureos1
purism@l5b:~$ dpkg -s squeekboard | grep Version
Version: 1.8.0
purism@l5b:~$ dpkg -s gnome-control-center | grep Version
Version: 1:3.34.0.1+20020+git09f08da1a-1pureos0
purism@l5b:~$ uptime
07:54:26 up 42 min, 2 users, load average: 0.26, 0.16, 0.13
purism@l5b:~$ date
Tue 28 Jan 2020 07:54:27 AM PST
purism@l5b:~$
```
```
purism@l5b:~$ sudo coredumpctl gdb 1221
PID: 1221 (gnome-control-c)
UID: 1000 (purism)
GID: 1000 (purism)
Signal: 11 (SEGV)
Timestamp: Tue 2020-01-28 07:43:12 PST (7min ago)
Command Line: gnome-control-center
Executable: /usr/bin/gnome-control-center
Control Group: /user.slice/user-1000.slice/session-1.scope
Unit: session-1.scope
Slice: user-1000.slice
Session: 1
Owner UID: 1000 (purism)
Boot ID: dd4c32f00f2a4915a21ec0abf9685cb5
Machine ID: 3ffd86e60cc84d469124866fb33aecb3
Hostname: l5b
Storage: /var/lib/systemd/coredump/core.gnome-control-c.1000.dd4c32f00f2a4915a21ec0abf9685cb5.1221.1580226192000000.lz4
Message: Process 1221 (gnome-control-c) of user 1000 dumped core.
Stack trace of thread 1221:
#0 0x0000ffff9ba13118 wl_proxy_get_user_data (libwayland-client.so.0)
#1 0x0000ffff9cc76fdc n/a (libgdk-3.so.0)
#2 0x0000ffff9bbd6dcc ffi_call_SYSV (libffi.so.6)
#3 0x0000ffff9bbd76f4 ffi_call (libffi.so.6)
#4 0x0000ffff9ba14ffc n/a (libwayland-client.so.0)
#5 0x0000ffff9ba11b24 n/a (libwayland-client.so.0)
#6 0x0000ffff9ba12e90 wl_display_dispatch_queue_pending (libwayland-client.so.0)
#7 0x0000ffff9cc7d074 n/a (libgdk-3.so.0)
#8 0x0000ffff9cc1b248 gdk_display_get_event (libgdk-3.so.0)
#9 0x0000ffff9cc7cd54 n/a (libgdk-3.so.0)
#10 0x0000ffff9d476674 g_main_context_dispatch (libglib-2.0.so.0)
#11 0x0000ffff9d4768e8 n/a (libglib-2.0.so.0)
#12 0x0000ffff9d476984 g_main_context_iteration (libglib-2.0.so.0)
#13 0x0000ffff9d69ab84 g_application_run (libgio-2.0.so.0)
#14 0x0000aaaad2a4012c main (gnome-control-center)
#15 0x0000ffff9bd2bd24 __libc_start_main (libc.so.6)
#16 0x0000aaaad2a402a0 _start (gnome-control-center)
#17 0x0000aaaad2a402a0 _start (gnome-control-center)
GNU gdb (Debian 8.2.1-2) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "aarch64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/gnome-control-center...(no debugging symbols found)...done.
warning: core file may not match specified executable file.
[New LWP 1221]
[New LWP 1224]
[New LWP 1226]
[New LWP 1227]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
Core was generated by `gnome-control-center'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x0000ffff9ba13118 in wl_proxy_get_user_data ()
from /lib/aarch64-linux-gnu/libwayland-client.so.0
[Current thread is 1 (Thread 0xffff93268010 (LWP 1221))]
(gdb) bt
#0 0x0000ffff9ba13118 in wl_proxy_get_user_data ()
at /lib/aarch64-linux-gnu/libwayland-client.so.0
#1 0x0000ffff9cc76fdc in () at /lib/aarch64-linux-gnu/libgdk-3.so.0
#2 0x0000ffff9bbd6dcc in ffi_call_SYSV ()
at /lib/aarch64-linux-gnu/libffi.so.6
#3 0x0000ffff9bbd76f4 in ffi_call () at /lib/aarch64-linux-gnu/libffi.so.6
#4 0x0000ffff9ba14ffc in () at /lib/aarch64-linux-gnu/libwayland-client.so.0
#5 0x0000ffff9ba11b24 in () at /lib/aarch64-linux-gnu/libwayland-client.so.0
#6 0x0000ffff9ba12e90 in wl_display_dispatch_queue_pending ()
at /lib/aarch64-linux-gnu/libwayland-client.so.0
#7 0x0000ffff9cc7d074 in () at /lib/aarch64-linux-gnu/libgdk-3.so.0
#8 0x0000ffff9cc1b248 in gdk_display_get_event ()
at /lib/aarch64-linux-gnu/libgdk-3.so.0
#9 0x0000ffff9cc7cd54 in () at /lib/aarch64-linux-gnu/libgdk-3.so.0
#10 0x0000ffff9d476674 in g_main_context_dispatch ()
at /lib/aarch64-linux-gnu/libglib-2.0.so.0
#11 0x0000ffff9d4768e8 in () at /lib/aarch64-linux-gnu/libglib-2.0.so.0
#12 0x0000ffff9d476984 in g_main_context_iteration ()
at /lib/aarch64-linux-gnu/libglib-2.0.so.0
#13 0x0000ffff9d69ab84 in g_application_run ()
at /lib/aarch64-linux-gnu/libgio-2.0.so.0
#14 0x0000aaaad2a4012c in main ()
(gdb) quit
purism@l5b:~$
```https://source.puri.sm/Librem5/debs/plymouth/-/issues/1Shutdown fade doesn't go all the way to black2020-01-29T10:27:29ZTobias BernardShutdown fade doesn't go all the way to blackWhen shutting down the screen fades and becomes darker, but then freezes at some point and maintains that same brightness value for a few seconds, and then suddenly going black.
I'd be nicer if this fade went all the way to black withou...When shutting down the screen fades and becomes darker, but then freezes at some point and maintains that same brightness value for a few seconds, and then suddenly going black.
I'd be nicer if this fade went all the way to black without stopping inbetween.
![shutdown-fade](/uploads/d8075bce5f14f70ee01be587d333c6a7/shutdown-fade.mp4)https://source.puri.sm/Librem5/OS-issues/-/issues/126Headphone insertion events should change the PulseAudio port2020-07-05T11:21:32ZBob HamHeadphone insertion events should change the PulseAudio portAs Kyle [noted](https://source.puri.sm/Librem5/OS-issues/issues/50#note_80765):
> This is a script I ended up writing so I could ... as well as set it as the default audio sink, because inserting the headphones currently does not trigge...As Kyle [noted](https://source.puri.sm/Librem5/OS-issues/issues/50#note_80765):
> This is a script I ended up writing so I could ... as well as set it as the default audio sink, because inserting the headphones currently does not trigger thishttps://source.puri.sm/Librem5/OS-issues/-/issues/125Headphone volume cannot be controlled2020-09-21T11:45:47ZBob HamHeadphone volume cannot be controlledAs Kyle [noted](https://source.puri.sm/Librem5/OS-issues/issues/50#note_80765):
> one cannot control the volume of the headphones via any of the tools on the Librem 5. Instead currently you must use alsamixerAs Kyle [noted](https://source.puri.sm/Librem5/OS-issues/issues/50#note_80765):
> one cannot control the volume of the headphones via any of the tools on the Librem 5. Instead currently you must use alsamixerhttps://source.puri.sm/Librem5/OS-issues/-/issues/124Headphone output defaults to barely audible2020-07-05T11:22:09ZBob HamHeadphone output defaults to barely audibleAs Kyle [noted](https://source.puri.sm/Librem5/OS-issues/issues/50#note_80765):
> currently the audio output of the headphones defaults to be barely audibleAs Kyle [noted](https://source.puri.sm/Librem5/OS-issues/issues/50#note_80765):
> currently the audio output of the headphones defaults to be barely audiblehttps://source.puri.sm/Librem5/gnome-control-center/-/issues/109Mobile panel navigation: Use back buttons in more places2020-02-26T11:43:40ZTobias BernardMobile panel navigation: Use back buttons in more placesInside the Mobile panel we have 5 sub-views, some of which use cancel/apply, others a back button.
- **Network Mode** has cancel/apply, but should have a back button instead
- **Network** has cancel/apply, but should have a back button ...Inside the Mobile panel we have 5 sub-views, some of which use cancel/apply, others a back button.
- **Network Mode** has cancel/apply, but should have a back button instead
- **Network** has cancel/apply, but should have a back button instead
- **APNs** has a back button, which is appropriate
- **SIM Lock** has cancel/apply, but should probably back button (but needs a more general overhaul so I'd keep it as is for now)
- **Modem Details** has a back button, which is appropriate
These are immediately actionable:
- [ ] **Network Mode**: change to a back button
- [ ] **Network**: change to a back buttonhttps://source.puri.sm/Librem5/deb-build-jobs/-/issues/55blessed-builds: report success although no artifacts are produced2020-02-26T17:00:16ZGuido Guntherblessed-builds: report success although no artifacts are produced@arno.bauernoppel one more thing i noticed with your current pipeline logic:
if a job does not produce any debs the pipeline is marked as succesfull although it stops, see:
http://localhost:8080/job/Builds/job/debs/job/deb-folks-amber-...@arno.bauernoppel one more thing i noticed with your current pipeline logic:
if a job does not produce any debs the pipeline is marked as succesfull although it stops, see:
http://localhost:8080/job/Builds/job/debs/job/deb-folks-amber-phone-staging-aarch64/
(folks sets export-dir so the debs end up somehwere else but the pipeline must never report success then).Arno BauernoppelArno Bauernoppelhttps://source.puri.sm/Librem5/OS-issues/-/issues/123Feature (for consideration), a global setting for 'delete/purge' after n days2020-01-28T08:10:36ZTodd WeaverFeature (for consideration), a global setting for 'delete/purge' after n daysSeeing call recent https://source.puri.sm/Librem5/calls/issues/28 get closed and verified, and seeing delete recent https://source.puri.sm/Librem5/calls/issues/98 appear as a desire, while also seeing browser history delete options. It m...Seeing call recent https://source.puri.sm/Librem5/calls/issues/28 get closed and verified, and seeing delete recent https://source.puri.sm/Librem5/calls/issues/98 appear as a desire, while also seeing browser history delete options. It may be a feature to consider (I would use it) to purge all usage after n days (I would set it to a week).
Things I could see desiring to clear (for those that don't want an ever growing permanent record on their device):
1. Recent Calls
2. Recent Browsing (History and Cookies)
3. Recent Chats
4. Recent Map Addresses
5. Recent Files Accessed
I could see a "Purge Data" option of [Never, Monthly, Weekly, Daily, Hourly, Immediate]
This should not impact stored bookmarks, pictures, music, nor files (to name a few).
Another thing to consider would be a persona/profile switch to a fully temporary phosh instance for the user where this setting is 'Immediate' for everything.https://source.puri.sm/Librem5/OS-issues/-/issues/122Librem 5 system: locale(s) not generated automatically2020-12-26T10:41:19ZNils SiebelLibrem 5 system: locale(s) not generated automatically
# What problem did you encounter
## What is the actual behaviour?
Selected language in the user interface (gnome-settings-*): en_GB.UTF-8
THEN in Terminal:
```
# perl --version
perl: warning: Setting locale failed.
perl: warning: Pl...
# What problem did you encounter
## What is the actual behaviour?
Selected language in the user interface (gnome-settings-*): en_GB.UTF-8
THEN in Terminal:
```
# perl --version
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_MONETARY = "en_GB.UTF-8",
LC_PAPER = "en_GB.UTF-8",
LC_MEASUREMENT = "en_GB.UTF-8",
LC_TIME = "en_GB.UTF-8",
LC_NUMERIC = "en_GB.UTF-8",
LANG = "en_GB.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
This is perl 5, version 28, subversion 1 (v5.28.1) built for aarch64-linux-gnu-thread-multi
(with 61 registered patches, see perl -V for more detail)
(...)
```
This can actually cause trouble for some background processes as the output of perl scripts aren't parsable.
## What is the expected behaviour?
Locales will be generated as needed so that programs like `perl` run without issue.
## How to reproduce
Please provide steps to reproduce the issue. If it's a graphical issue please
attach screenshots.
# What hardware are you running on?
- [ ] amd64 qemu image
- [ ] Librem5 devkit
- [X] other (please elaborate)
Librem 5 Birch
# Relevant OS information
## Which kernel are you using?
Please paste the output of ``uname -a`` below.
`Linux pureos 5.3.0-librem5-h1 #1 SMP PREEMPT Tue Jan 7 10:16:00 CET 2020 aarch64 GNU/Linux`
## Which OS are you using?
Please paste the output of ``cat /etc/os-release`` below.
```
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/gnome-control-center/-/issues/108Date setting month flows off top of page2020-01-26T14:06:43ZTodd WeaverDate setting month flows off top of pageReproduction (yes, this user-flow did occur for me)
1. Settings
2. Details
3. Date & Time
4. Turn off Automatic Date & Time
5. edit Date & Time
6. Click Month, select 'December' (this flips the drop down to render to top on next click)
7...Reproduction (yes, this user-flow did occur for me)
1. Settings
2. Details
3. Date & Time
4. Turn off Automatic Date & Time
5. edit Date & Time
6. Click Month, select 'December' (this flips the drop down to render to top on next click)
7. Click Month
8. Witness overflow off the top
![2061-12-27-1840](/uploads/a1ccb061cc68c74f51d8bb2ec67ca5d7/2061-12-27-1840.png)
```
purism@librem-5-birch:~$ uname -a
Linux librem-5-birch 5.3.0-librem5-h1 #1 SMP PREEMPT Sat Jan 25 09:55:23 CET 2020 aarch64 GNU/Linux
purism@librem-5-birch:~$ dpkg -s phosh | grep Version
Version: 0.1.7
purism@librem-5-birch:~$ dpkg -s phoc | grep Version
Version: 0.1.5pureos1
purism@librem-5-birch:~$ dpkg -s gnome-control-center | grep Version
Version: 1:3.34.0.1+19975+gitf7dfd564f-1pureos0
purism@librem-5-birch:~$ uptime
06:06:15 up 13:17, 2 users, load average: 0.39, 0.47, 0.35
purism@librem-5-birch:~$ date
Sun 26 Jan 2020 06:06:20 AM PST
purism@librem-5-birch:~$
```https://source.puri.sm/Librem5/debs/gnome-clocks/-/issues/19Timer should repeat (like alarm) or be loud and longer2020-01-26T13:51:44ZTodd WeaverTimer should repeat (like alarm) or be loud and longerThe timer 'ding' is very quiet and very short
Reproduction
1. Clocks - Timer
2. Set to 1 second
3. Start
4. Hear tiny ding through earpiece
(now imagine your cookies burning from the other room because you missed this sound)
I could s...The timer 'ding' is very quiet and very short
Reproduction
1. Clocks - Timer
2. Set to 1 second
3. Start
4. Hear tiny ding through earpiece
(now imagine your cookies burning from the other room because you missed this sound)
I could see this either being like the alarm (continuous), or being much louder (through speaker) and much longer (at least 15 seconds). This probably needs @design to chime in :)
```
purism@librem-5-birch:~$ uname -a
Linux librem-5-birch 5.3.0-librem5-h1 #1 SMP PREEMPT Sat Jan 25 09:55:23 CET 2020 aarch64 GNU/Linux
purism@librem-5-birch:~$ dpkg -s phosh | grep Version
Version: 0.1.7
purism@librem-5-birch:~$ dpkg -s phoc | grep Version
Version: 0.1.5pureos1
purism@librem-5-birch:~$ dpkg -s gnome-clocks | grep Version
Version: 3.32.0+1911+git9afed36-1pureos0
purism@librem-5-birch:~$
```https://source.puri.sm/Librem5/debs/gnome-clocks/-/issues/18Alarm sound extremely quiet2020-02-19T17:29:00ZTodd WeaverAlarm sound extremely quietThe alarm plays quietly through the earpiece, and should be louder through the speaker.
Reproduction:
1. Clocks - Alarm
2. '+' create new alarm; for 1 minute from now
3. Wait
4. Hear alarm quietly playing through earpiece
```
purism@li...The alarm plays quietly through the earpiece, and should be louder through the speaker.
Reproduction:
1. Clocks - Alarm
2. '+' create new alarm; for 1 minute from now
3. Wait
4. Hear alarm quietly playing through earpiece
```
purism@librem-5-birch:~$ uname -a
Linux librem-5-birch 5.3.0-librem5-h1 #1 SMP PREEMPT Sat Jan 25 09:55:23 CET 2020 aarch64 GNU/Linux
purism@librem-5-birch:~$ dpkg -s phosh | grep Version
Version: 0.1.7
purism@librem-5-birch:~$ dpkg -s phoc | grep Version
Version: 0.1.5pureos1
purism@librem-5-birch:~$ dpkg -s gnome-clocks | grep Version
Version: 3.32.0+1911+git9afed36-1pureos0
purism@librem-5-birch:~$
```https://source.puri.sm/Librem5/debs/gtk/-/issues/19half-button press when moving finger off the button while pressing2021-01-11T09:26:20ZTodd Weaverhalf-button press when moving finger off the button while pressing# What problem did you encounter
Half button press
## What is the current behaviour?
Pressed the back button from Privacy settings that resulting in a half-button pressed state.
## What is the expected behaviour?
Button press and re...# What problem did you encounter
Half button press
## What is the current behaviour?
Pressed the back button from Privacy settings that resulting in a half-button pressed state.
## What is the expected behaviour?
Button press and release
## How to reproduce
Captured the state of half-press and subsequent press to release then tap event to have it proceed as expected.
![librem-5-chestnut-half-button-press-state-2020-01-12](/uploads/96344acc403b7c1d1cc7e888e6436f14/librem-5-chestnut-half-button-press-state-2020-01-12.webm)
![librem-5-chestnut-half-button-press-state-reproduced-2020-01-12](/uploads/e4a42c2843900a5b203a8f725eccf17a/librem-5-chestnut-half-button-press-state-reproduced-2020-01-12.webm)
# Which version did you encounter the bug in?
```
purism@pureos:~$ uname -a
Linux pureos 5.3.0-librem5-h1 #1 SMP PREEMPT Tue Jan 7 10:16:00 CET 2020 aarch64 GNU/Linux
purism@pureos:~$ dpkg -s phosh | grep Version
Version: 0.1.6
purism@pureos:~$ dpkg -s gnome-control-center | grep Version
Version: 1:3.34.0.1+19975+gitf7dfd564f-1pureos0
purism@pureos:~$
```
# What hardware are you running phosh on?
- Librem 5 Chestnuthttps://source.puri.sm/Librem5/debs/mesa/-/issues/4don't require ETNA_MESA_DEBUG=no_supertile for running phoc2021-08-05T09:17:30ZGuido Guntherdon't require ETNA_MESA_DEBUG=no_supertile for running phocneed to investigate why this is required and fix itneed to investigate why this is required and fix ithttps://source.puri.sm/Librem5/debs/gtk/-/issues/18Sending text input events without having received "enter" and without having ...2020-10-19T06:48:12ZGuido GuntherSending text input events without having received "enter" and without having requested enablePreviously (phoc): "We currently flood the log with `Text input commit received without focus`"
We have about 30 of these per second:
```
2019-04-15 11:46:37 - [subprojects/wlroots/types/wlr_text_input_v3.c:179] Text input commit receiv...Previously (phoc): "We currently flood the log with `Text input commit received without focus`"
We have about 30 of these per second:
```
2019-04-15 11:46:37 - [subprojects/wlroots/types/wlr_text_input_v3.c:179] Text input commit received without focus
2019-04-15 11:46:37 - [src/text_input.c:140] Inactive text input tried to commit an update
```
so s.th. is wrong in that area.
Feature: https://source.puri.sm/Librem5/phoc/issues/10 (-Dorota)
EDIT: The application is sending some events without having a good reason to do so:
```
$ WAYLAND_DEBUG=1 LD_LIBRARY_PATH=`pwd`/../../gestures/gtk-install/lib python3 ./tools/entry.py 2>&1 | grep text_input
[2567780.915] wl_registry@2.global(21, "zwp_text_input_manager_v3", 1)
[2567888.713] wl_registry@21.global(21, "zwp_text_input_manager_v3", 1)
[2567888.736] -> wl_registry@21.bind(21, "zwp_text_input_manager_v3", 1, new id [unknown]@32)
[2567888.751] -> zwp_text_input_manager_v3@32.get_text_input(new id zwp_text_input_v3@33, wl_seat@15)
-- should wait for "enter"
---- should send "enable", only then the following should happen
[2570904.081] -> zwp_text_input_v3@33.set_surrounding_text("", 0, 0)
[2570904.104] -> zwp_text_input_v3@33.set_text_change_cause(1)
[2570904.111] -> zwp_text_input_v3@33.commit()
```
No "enter" is an acceptable condition if there's no input method provider.Last: Romneya (W26-28)Dorota CzaplejewiczDorota Czaplejewicz