Librem5 issueshttps://source.puri.sm/groups/Librem5/-/issues2019-10-08T08:54:23Zhttps://source.puri.sm/Librem5/gnome-control-center/-/issues/69Add support for more wifi security methods2019-10-08T08:54:23ZMohammed SadiqAdd support for more wifi security methodsThe following security methods are required:
- [ ] LEAP
- [ ] WPA/WPA2 Enterprise
- [ ] Dyanamic WEPThe following security methods are required:
- [ ] LEAP
- [ ] WPA/WPA2 Enterprise
- [ ] Dyanamic WEPhttps://source.puri.sm/Librem5/librem5-base/-/issues/8librem5-base-defaults contains devkit-specific parts2019-10-08T12:17:15ZBob Hamlibrem5-base-defaults contains devkit-specific partsThe `librem5-base-defaults` package contains devkit-specific parts, for example `/usr/share/pulseaudio/alsa-mixer/profile-sets/librem5-devkit.conf` and `/etc/pulse/daemon.conf.d/85-librem5-devkit-sgtl5000.conf`. These should be moved to...The `librem5-base-defaults` package contains devkit-specific parts, for example `/usr/share/pulseaudio/alsa-mixer/profile-sets/librem5-devkit.conf` and `/etc/pulse/daemon.conf.d/85-librem5-devkit-sgtl5000.conf`. These should be moved to the `librem5-devkit-base` package in Librem5/librem5-devkit-tools>.https://source.puri.sm/Librem5/gnome-control-center/-/issues/35SIM Lock error message2019-10-08T14:16:56ZFrancois TecheneSIM Lock error messageThe current error message when entering the wrong PIN code to unlock the SIM card is not useful and says :
"Error: Mobile Equipment Error"
Instead it should say something like :
"You entered an incorrect PIN code"The current error message when entering the wrong PIN code to unlock the SIM card is not useful and says :
"Error: Mobile Equipment Error"
Instead it should say something like :
"You entered an incorrect PIN code"https://source.puri.sm/Librem5/Apps_Issues/-/issues/161Remove "Help" from the default applications2019-10-08T22:15:13ZFrancois TecheneRemove "Help" from the default applications"Help" doesn't show any documentation about the phone UIs nor gestures and only focuses on the desktop platform.
It makes no sense keeping it visible within the default apps in the apps drawer.
/cc @guido.gunther"Help" doesn't show any documentation about the phone UIs nor gestures and only focuses on the desktop platform.
It makes no sense keeping it visible within the default apps in the apps drawer.
/cc @guido.guntherhttps://source.puri.sm/Librem5/meson/-/issues/1fix version number in debian/changelog2019-10-10T15:22:24ZGuido Guntherfix version number in debian/changelogcurrently there's `0.51.1-pureos+librem5.1` which should have been `0.51.1-1pureos+librem5.1` (https://source.puri.sm/snippets/20). there's no need to do anything atm but please fix it for the next upload.currently there's `0.51.1-pureos+librem5.1` which should have been `0.51.1-1pureos+librem5.1` (https://source.puri.sm/snippets/20). there's no need to do anything atm but please fix it for the next upload.https://source.puri.sm/Librem5/image-builder/-/issues/21vmdebootstrap leaves loop0p1 around2019-10-11T12:51:50ZGuido Gunthervmdebootstrap leaves loop0p1 aroundOn arm01 *loop0p1* is left around after an image build so that other builds afterwards fail like
```
device-mapper: reload ioctl on loop0p2p1 failed: Device or resource busy
create/reload failed on loop0p2p1
```
A `dmsetup remove loop0...On arm01 *loop0p1* is left around after an image build so that other builds afterwards fail like
```
device-mapper: reload ioctl on loop0p2p1 failed: Device or resource busy
create/reload failed on loop0p2p1
```
A `dmsetup remove loop0p1` works around this (which we currently do in */etc/cron.hourly/work-around-vmdebootstrap*).https://source.puri.sm/Librem5/virtboard/-/issues/11Keyboard too large at scale == 12019-10-11T12:53:08ZGuido GuntherKeyboard too large at scale == 1At scale == 1 the keyboards panel is at least 5 times as high as the shell's home button. It should rather be about the same height IMHO.At scale == 1 the keyboards panel is at least 5 times as high as the shell's home button. It should rather be about the same height IMHO.A1: Support fully featured on screen keyboardhttps://source.puri.sm/Librem5/virtboard/-/issues/4Keyboard does not scale when display->allocation.width/height == 02019-10-11T12:54:53ZGuido GuntherKeyboard does not scale when display->allocation.width/height == 0This breaks scaling the on screen keyboard in our QEMU VM:
See
display_set_output_configure_handler:
```
if (output->allocation.width == 0 &&
output->allocation.height == 0)
continue;
```
...This breaks scaling the on screen keyboard in our QEMU VM:
See
display_set_output_configure_handler:
```
if (output->allocation.width == 0 &&
output->allocation.height == 0)
continue;
```
however e.g. custom modes in QXL have no approprite size information (which can also happen with broken edid):
```
$ weston-info
…
interface: 'wl_output', version: 3, name: 20
x: 0, y: 0, scale: 2,
physical_width: 0 mm, physical_height: 0 mm,
make: '<Unknown>', model: '<Unknown>',
```
so this should be handled properly.https://source.puri.sm/Librem5/virtboard/-/issues/17Labels change when keyboard is clicked2019-10-11T12:55:15ZDorota CzaplejewiczLabels change when keyboard is clickedSteps to reproduce:
0. Use Polish layout in gsettings
1. Fire up rootston
2. Fire up a *non-text-input* application (`yad --entry` works with GTK<3.24)
3. Fire up virtboard
4. Type a number
Expected result:
- letter is entered
Actual...Steps to reproduce:
0. Use Polish layout in gsettings
1. Fire up rootston
2. Fire up a *non-text-input* application (`yad --entry` works with GTK<3.24)
3. Fire up virtboard
4. Type a number
Expected result:
- letter is entered
Actual result:
- letter is entered
- labels on keys momentarily changehttps://source.puri.sm/Librem5/deb-build-jobs/-/issues/24evaluate git-debpush2019-10-17T15:32:58ZGuido Guntherevaluate git-debpush(as mentioned previously but to have note) this does similar things than we do so we should reuse that where possible.(as mentioned previously but to have note) this does similar things than we do so we should reuse that where possible.https://source.puri.sm/Librem5/gnome-initial-setup/-/issues/14Remove the Problem Reporting section from the Privacy panel2019-10-18T11:33:54ZFrancois TecheneRemove the Problem Reporting section from the Privacy panel![Screenshot_from_2019-09-24_09-31-36](/uploads/a22c950080e2d0b500fa02b907dadafb/Screenshot_from_2019-09-24_09-31-36.png)
This section is confusing for the non technical user who doesn't know what Debian buster is and the feature itself...![Screenshot_from_2019-09-24_09-31-36](/uploads/a22c950080e2d0b500fa02b907dadafb/Screenshot_from_2019-09-24_09-31-36.png)
This section is confusing for the non technical user who doesn't know what Debian buster is and the feature itself is not related to PureOS. It should be removed.
The panel should look like this :
![setup-privacy](/uploads/eb46995e4863414517cbb154e30de770/setup-privacy.png)https://source.puri.sm/Librem5/gnome-calculator/-/issues/1Disable pulling currency values by default2019-10-18T16:40:55ZAdrien PlazasDisable pulling currency values by defaultCurrently, currency values are downloaded regularly, it's not clear for the user and it should be both user controllable and fllow some system-wide privacy settings.Currently, currency values are downloaded regularly, it's not clear for the user and it should be both user controllable and fllow some system-wide privacy settings.https://source.puri.sm/Librem5/OS-issues/-/issues/67Support '/org/gnome/SessionManager` Logout2019-10-20T12:17:55ZGuido GuntherSupport '/org/gnome/SessionManager` LogoutWhen changing language there's a button that sends
method call time=1571573627.403695 sender=:1.167 -> destination=:1.12 serial=50 path=/org/gnome/SessionManager; interface=org.gnome.SessionManager; member=Logout
which does nothing - l...When changing language there's a button that sends
method call time=1571573627.403695 sender=:1.167 -> destination=:1.12 serial=50 path=/org/gnome/SessionManager; interface=org.gnome.SessionManager; member=Logout
which does nothing - likely we're missing something in the shell so gnome-session fails to do anything useful.
see #66https://source.puri.sm/Librem5/gnome-control-center/-/issues/71Cellular: change panel icon to full bars2019-10-21T14:51:05ZTobias BernardCellular: change panel icon to full barsI don't remember why we use the icon we currently have, but seeing as the Wifi icon has full bars, we should probably do the same for cellular. The icon string for the one with 4 full bars is `network-cellular-signal-excellent-symbolic`.I don't remember why we use the icon we currently have, but seeing as the Wifi icon has full bars, we should probably do the same for cellular. The icon string for the one with 4 full bars is `network-cellular-signal-excellent-symbolic`.https://source.puri.sm/Librem5/Apps_Issues/-/issues/162consider using abrt for problem reports2019-10-21T17:02:11ZGuido Guntherconsider using abrt for problem reportsthis could give us better problem reports if the user opts in in g-i-s.this could give us better problem reports if the user opts in in g-i-s.https://source.puri.sm/Librem5/OS-issues/-/issues/68Feature request: Ability to ignore notifications per app, for X minutes,2019-10-22T12:09:13Zkl@vsen.dkFeature request: Ability to ignore notifications per app, for X minutes,In Android 7/Lineage OS 14 - its possible to set a notification "ignore rule" - to always ignore notifications from an app for X minutes, after last notification.
That works great, when I am f.ex. talking with a colleague on irc (and us...In Android 7/Lineage OS 14 - its possible to set a notification "ignore rule" - to always ignore notifications from an app for X minutes, after last notification.
That works great, when I am f.ex. talking with a colleague on irc (and use weechat with android client) - as every highlight on irc to me - gives me a notification on Android.. the auto-ignore - meant I could have a dialogue with someone on irc - and not be ping'ed constantly on the phone whilst doing it - and still not missing the first notification. I usually set it to a 5 minute ignore time.
If you could point me to what code is being used for notifications - I'd happily look at doing an MR myself.
I opted to get my librem 5 in december first.. so happily waiting :)https://source.puri.sm/Librem5/dvk-mx8m-bsb/-/issues/4USB-C 2.0 Interface Only Works In One Orientation For Some Units2019-10-23T07:54:48ZGuido GuntherUSB-C 2.0 Interface Only Works In One Orientation For Some UnitsI tried to flash a devkit (devkit A) with uuu as of mfgtools@c81a5dab6f590dc95aed26f0663bf7d89e75defb but the uuu script
```
uuu_version 1.0.1
SDP: boot -f u-boot-devkit-recovery.imx
SDPU: delay 1000
SDPU: write -f u-boot-devkit-recov...I tried to flash a devkit (devkit A) with uuu as of mfgtools@c81a5dab6f590dc95aed26f0663bf7d89e75defb but the uuu script
```
uuu_version 1.0.1
SDP: boot -f u-boot-devkit-recovery.imx
SDPU: delay 1000
SDPU: write -f u-boot-devkit-recovery.imx -offset 0x57c00
SDPU: jump
SDPS: boot -f u-boot-devkit-recovery.imx
SDPU: delay 1000
FB: ucmd setenv fastboot_dev mmc
FB: ucmd setenv mmcdev 0
FB: flash -raw2sparse all devkit.img
FB: Done
```
would stop at
```
1:1 1/ 1 [============100%============] SDP: boot -f u-boot-devkit-recovery.imx`
```
The serial console output showed
```
SDP: initialize...
```
I then tried another board (devkit B) and flashing worked right away. I then retried devkit A again and it seem that it matters which way of the USB-C plug is up. One way works, the other doesn't. That's 100% reproducible here atm.https://source.puri.sm/Librem5/debs/gnome-settings-daemon/-/issues/7Cellular : The SIM unlock dialog should diplay a numerical keyboard2019-10-23T11:46:31ZFrancois TecheneCellular : The SIM unlock dialog should diplay a numerical keyboardThe dialog to unlock the SIM card currently displays a normal keyboard. Instead, it should display a keyboard with numbers only.The dialog to unlock the SIM card currently displays a normal keyboard. Instead, it should display a keyboard with numbers only.https://source.puri.sm/Librem5/gnome-control-center/-/issues/74Wifi connection editor: IPv6 address is not fully visible2019-10-24T19:41:24ZTobias BernardWifi connection editor: IPv6 address is not fully visibleThe last part of the IPv6 address is not visible on the details screen because it's truncated:
![image](/uploads/d929d8d9d422a1ab6aab888d276ae03c/image.png)
Could we move the address to a second line below the label?The last part of the IPv6 address is not visible on the details screen because it's truncated:
![image](/uploads/d929d8d9d422a1ab6aab888d276ae03c/image.png)
Could we move the address to a second line below the label?https://source.puri.sm/Librem5/OS-issues/-/issues/70Need to restrict the allowed USB devices on the modem bus2019-10-28T17:40:30ZDorota CzaplejewiczNeed to restrict the allowed USB devices on the modem busThe modem as the untrusted part of the system, must be resticted to a whitelisted set of necessary functionality, e.g. serial USB device, a certain PID/VID.
Since the modem may be malicious, that would restrict the attack surface area ...The modem as the untrusted part of the system, must be resticted to a whitelisted set of necessary functionality, e.g. serial USB device, a certain PID/VID.
Since the modem may be malicious, that would restrict the attack surface area available to it. Even if it's found to pretend to be something it isn't (input device, booby-trapped filesystem), it wouldn't be able to do much damage.
Some of the same precautions apply here as with untrusted external USB devices, although the device has more information in this case, and the way of letting the user know about irregularities should be different here.
Credit to a random internet stranger's post reminding me of this.