postmarketOS issueshttps://gitlab.com/groups/postmarketOS/-/issues2024-03-28T10:05:44Zhttps://gitlab.com/postmarketOS/pmbootstrap/-/issues/2317sideload: bad error message when --arch not given2024-03-28T10:05:44ZLuca Weisssideload: bad error message when --arch not givenWhen you try to sideload a package that is only e.g. on armv7 and you don't specify `pmbootstrap sideload --arch=armv7 $pkgname` then we write an error message that's not useful at all
```
sicelo@tpt440p:~/Git/pmos/pmbootstrap$ ./pmboot...When you try to sideload a package that is only e.g. on armv7 and you don't specify `pmbootstrap sideload --arch=armv7 $pkgname` then we write an error message that's not useful at all
```
sicelo@tpt440p:~/Git/pmos/pmbootstrap$ ./pmbootstrap.py sideload --host 192.168.0.28 linux-postmarketos-omap
[00:16:39] ERROR: Could not find package 'linux-postmarketos-omap'!
[00:16:39] See also: <https://postmarketos.org/troubleshooting>;
Run 'pmbootstrap log' for details.
Before you report this error, ensure that pmbootstrap is up to date.
Find the latest version here: https://git.sr.ht/~postmarketos/pmbootstrap/refs
Your version: 2.2.1
```
Make sure to at least tell the user they might need to use `--arch=` to specify the target architecture.https://gitlab.com/postmarketOS/pmaports/-/issues/2625xiaomi-mocha: mainlining2024-02-29T05:05:13ZChristine Ellenviaxiaomi-mocha: mainliningNow working on bringing [mocha](https://wiki.postmarketos.org/wiki/Xiaomi_Mi_Pad_(xiaomi-mocha)) to mainline.
Have a (maybe?) good start by [Insel](https://github.com/insei/linux), but on 5.4 and marked as WIP, been left.
This fork has ...Now working on bringing [mocha](https://wiki.postmarketos.org/wiki/Xiaomi_Mi_Pad_(xiaomi-mocha)) to mainline.
Have a (maybe?) good start by [Insel](https://github.com/insei/linux), but on 5.4 and marked as WIP, been left.
This fork has checked and confirmed work, but lost support on AtMel touchscreen and something else.
a Full list of I2C device can be found [here](https://github.com/Insei/SmokeR21.5-kernel).
Reviewed Code to here, have a look at document, replaced bq24192 to the mainline driver, moved MIPI initialize to the tegra124-mocha-mipi.dtsi file.
most of code is still from original git repo. some of them is from hammerhead(like mainlined bq2419x)
Dont know what to do next. Continue reviewing Insel's commit or rebase from jetson?
Not sure if the modified code work on the pad. have a problematic network connections and still tried to get Linux source downloaded.
[tegra124-mocha.dts](/uploads/b753ac599ac0aa00419f7032a4aada7b/tegra124-mocha.dts)
[tegra124-mocha-mipi.dtsi](/uploads/6f715c9631e0f0f56d371c919c9c026e/tegra124-mocha-mipi.dtsi)
[tegra124-mocha-pinmux.dtsi](/uploads/8f56c2d87b20c6e01be4ec34177bd43c/tegra124-mocha-pinmux.dtsi)
[tegra124-mocha-pmic.dtsi](/uploads/e577ea8df2b14454c71f9b1d27b8e03a/tegra124-mocha-pmic.dtsi)https://gitlab.com/postmarketOS/pmaports/-/issues/2624cutiepi: Could not get graphics environment to work2024-02-27T23:30:37ZPavel Machekcutiepi: Could not get graphics environment to workI'm using "edge" channel.
I tried "gnome" envinronment (wayland based) and screen just froze when GUI should have started.
With "mate" environment, Linux boots with console on external display. I'm able to start X manually (X & mate-se...I'm using "edge" channel.
I tried "gnome" envinronment (wayland based) and screen just froze when GUI should have started.
With "mate" environment, Linux boots with console on external display. I'm able to start X manually (X & mate-session) and Mate works fine on external display, but internal display is black and xrandr does not seem to see either connector, so I can't use it to tweak settings.https://gitlab.com/postmarketOS/pmaports/-/issues/2623cutiepi: Fails to mount root filesystem2024-02-27T23:50:39ZPavel Machekcutiepi: Fails to mount root filesystemI tried cutiepi on the tablet, and both console and gnome versions fail to boot. root filesystem can't be mounted. I tried switching off the quite option and adding root= on the command line, but could not get it to work. I'm using "edge...I tried cutiepi on the tablet, and both console and gnome versions fail to boot. root filesystem can't be mounted. I tried switching off the quite option and adding root= on the command line, but could not get it to work. I'm using "edge" and did patch firmware issue.https://gitlab.com/postmarketOS/pmaports/-/issues/2622Inverted input from USI Stylus (google-krane)2024-02-28T15:34:52ZDvaMishkiLapathesame.personal@gmail.comInverted input from USI Stylus (google-krane)
### Describe your issue
I installed the Edge build with Gnome, when using the USI Stylus I see the cursor on the opposite side of the screen to where I put the screen. Searching the internet hasn't been able to help me so far, I'm most...
### Describe your issue
I installed the Edge build with Gnome, when using the USI Stylus I see the cursor on the opposite side of the screen to where I put the screen. Searching the internet hasn't been able to help me so far, I'm mostly getting into setting up Wacom or other styluses in Xorg. I'd like to not break something that works well and continue to use Wayland.
Interestingly, there is no similar problem in KDE.
The stylus in question works completely correctly in ChromeOS.
#### What's the expected behavior?
USI Stylus works correctly.
#### What's the current behavior?
Stylus input seems to be inverted in all axes.
#### How to reproduce your issue?
### What device are you using?
[Lenovo IdeaPad Duet Chromebook (google-krane)](https://wiki.postmarketos.org/wiki/Lenovo_IdeaPad_Duet_Chromebook_(google-krane))
### On what postmarketOS version did you encounter the issue?
* [x] edge (`master` branch)
* [x] I confirm that the issue is still present after running `sudo apk upgrade -a`.
### On what environment did you encounter the issue?
#### Environments
* [x] GNOME Shell
* [ ] Plasma Desktop
### How did you get postmarketOS image?
* [x] I built it using pmbootstrap
### What's the build date of the image? (in yyyy-mm-dd format)
2024-02-27
### Additional information
`libinput list-devices` output:
```sh
Device: hid-over-i2c 27C6:0E30 Stylus
Kernel: /dev/input/event4
Group: 1
Seat: seat0, default
Size: 34x55mm
Capabilities: tablet
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock: n/a
Left-handed: disabled
Nat.scrolling: n/a
Middle emulation: n/a
Calibration: identity matrix
Scroll methods: none
Click methods: none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles: none
Rotation: n/a
```https://gitlab.com/postmarketOS/pmaports/-/issues/2620Hotspot not available for modern Android devices2024-03-25T19:47:55ZmagdesignHotspot not available for modern Android devices<!--
Thank you for using postmarketOS! In order to speed up process of resolving your issue,
we would like you to fill in the following :
-->
### Describe your issue
#### What's the expected behaviour?
Hotspot on a pmos device should b...<!--
Thank you for using postmarketOS! In order to speed up process of resolving your issue,
we would like you to fill in the following :
-->
### Describe your issue
#### What's the expected behaviour?
Hotspot on a pmos device should be accessable from all kind of devices.
#### What's the current behaviour?
Hotspot is only available for linux devices or older android phones.
#### How to reproduce your issue?
Create a hotspot on pmos device. Try to connect with new generation android13/14 device (e.g. samsung A33, A53).
It will complain that it can not connect. While another linux device connects without trouble, gets an ip and internet.
### What device are you using?
<!--
Leave name of your device in vendor-codename format.
If unsure, check name in the device package or leave full name of device
PinePhone: which revision exactly? See https://wiki.pine64.org/index.php/PinePhone#Hardware_revisions
-->
OnePlus 6
### On what postmarketOS version did you encounter the issue?
<!--
Replace space inside `[ ]` with `x` to fill the checkbox
-->
* [x] edge (`master` branch)
* [x] `v23.12`
* [ ] `v23.06` (supported until 2024-01-18)
* [x] I confirm that the issue still is present after running `sudo apk upgrade -a`
### On what environment did you encounter the issue?
#### Environments
* [ ] GNOME Shell on Mobile
* [ ] Phosh
* [ ] Plasma Mobile
* [x] Sxmo (Wayland/Sway) 1.15.1
### How did you get postmarketOS image?
* [x] I built it using pmbootstrap
* [ ] It was preinstalled on my device
### What's the build date of the image? (in 2024-02-24 format)
<!--
Notes:
can be left empty if unsure
If you downloaded image from images.postmarketos.org, date will be in yyyymmdd format
-->
### Additional information
<!-- logs, etc. -- make use <details> for long listings -->
Tried it with 2 samsung devices and 1 linux device.https://gitlab.com/postmarketOS/pmaports/-/issues/2619VPN not routing through GSM2024-03-03T07:30:05ZmagdesignVPN not routing through GSM### Describe your issue
#### What's the expected behaviour?
When enableing a VPN connection, all traffic should be routed through this tunnel.
#### What's the current behaviour?
Only wifi traffic goes through a VPN tunnel.
Traffic over...### Describe your issue
#### What's the expected behaviour?
When enableing a VPN connection, all traffic should be routed through this tunnel.
#### What's the current behaviour?
Only wifi traffic goes through a VPN tunnel.
Traffic over GSM/mobile date ignores the tunnel.
#### How to reproduce your issue?
enable a vpn connection as described [here](https://wiki.postmarketos.org/wiki/User:Magdesign#VPN)
### What device are you using?
<!--
Leave name of your device in vendor-codename format.
If unsure, check name in the device package or leave full name of device
PinePhone: which revision exactly? See https://wiki.pine64.org/index.php/PinePhone#Hardware_revisions
-->
Oneplus 6
### On what postmarketOS version did you encounter the issue?
<!--
Replace space inside `[ ]` with `x` to fill the checkbox
-->
* [x] edge (`master` branch)
* [x] `v23.12`
* [ ] `v23.06` (supported until 2024-01-18)
* [x] I confirm that the issue still is present after running `sudo apk upgrade -a`
### On what environment did you encounter the issue?
#### Environments
* [ ] GNOME Shell on Mobile
* [ ] Phosh
* [ ] Plasma Mobile
* [x] Sxmo (Wayland/Sway) v1.15.1
* [ ] Other: **Please fill out**
### How did you get postmarketOS image?
* [ ] from https://images.postmarketos.org
* [x] I built it using pmbootstrap
### Additional information
<!-- logs, etc. -- make use <details> for long listings -->
With manual setting `route` this issue can be solved. Due to the ip randomisation i am to stupid to to set the route after a reboot and so failing to provide a script as workaround.
To test you can use the vpnbook com/freevpn settings.
Here gitlab domain is totally blocked, so its pain in the a** to fill and track issues (without vpn over mobile data).https://gitlab.com/postmarketOS/pmaports/-/issues/2618clockworkpi-uconsole-cm4 - inaccurate reading of axp20x-battery2024-02-26T16:16:17Zmikeschnierclockworkpi-uconsole-cm4 - inaccurate reading of axp20x-battery<!--
Thank you for using postmarketOS! In order to speed up process of resolving your issue,
we would like you to fill in the following :
-->
### Describe your issue
#### What's the expected behaviour?
I am currently using 2 18650 cel...<!--
Thank you for using postmarketOS! In order to speed up process of resolving your issue,
we would like you to fill in the following :
-->
### Describe your issue
#### What's the expected behaviour?
I am currently using 2 18650 cels (LG MJ1s) in my uConsole. The cells should be reporting somewhere around 22Wh, but the uConsole sees them at 8 Wh. This is an issue present in Clockwork Pi's Debian-based images as well. It will report 8 Wh regardless of which cells you use.
Yatli on the ClockworkPi forum [wrote a patch](https://github.com/yatli/arch-linux-arm-clockworkpi-a06/commit/f171b5e543a216fd148a28051718efa1774a01bc) for the axp228 driver, which correctly reports energy and power readings for the axp20x-battery. While it was written for the A06 core, Yatli believes [it should work](https://forum.clockworkpi.com/t/axp228-properly-report-energy-power-readings/9318/6) with the CM4 core as well.
#### What's the current behaviour?
When I run `cat /sys/class/power_supply/axp20x-battery/uevent` it reports
`POWER_SUPPLY_ENERGY_FULL=0`
`POWER_SUPPLY_ENERGY_NOW=0`
`POWER_SUPPLY_ENERGY_FULL_DESIGN=8000000`
#### How to reproduce your issue?
run `cat /sys/class/power_supply/axp20x-battery/uevent`
### What device are you using?
<!--
clockworkpi-uconsole-cm4
-->
### On what postmarketOS version did you encounter the issue?
<!--
Replace space inside `[ ]` with `x` to fill the checkbox
-->
* [x] edge (`master` branch)
* [ ] `v23.12`
* [ ] `v23.06` (supported until 2024-01-18)
* [x] I confirm that the issue still is present after running `sudo apk upgrade -a`
### On what environment did you encounter the issue?
#### Environments
* [ ] GNOME Shell on Mobile
* [ ] Phosh
* [ ] Plasma Mobile
* [ ] Sxmo (Wayland/Sway) **Please post the output of `sxmo_version.sh`**
* [x] Other: **Wayland/Sway**
### How did you get postmarketOS image?
* [ ] from https://images.postmarketos.org
* [x] I built it using pmbootstrap
* [ ] It was preinstalled on my device
### What's the build date of the image? (in yyyy-mm-dd format)
<!--
Notes:
can be left empty if unsure
If you downloaded image from images.postmarketos.org, date will be in yyyymmdd format
-->
### Additional information
<!-- logs, etc. -- make use <details> for long listings -->https://gitlab.com/postmarketOS/pmaports/-/issues/2617Pinephone: Stuck message from2024-03-03T07:32:53ZKevin JOLYPinephone: Stuck message from### Describe your issue
I'm using my pinephone as a daily from about 2 months and I'm impressed on how it works! So, first and foremost, Congratulations!
I've noticed some quirks and I want to help resolve them so, here the first and t...### Describe your issue
I'm using my pinephone as a daily from about 2 months and I'm impressed on how it works! So, first and foremost, Congratulations!
I've noticed some quirks and I want to help resolve them so, here the first and the most annoying (from my point of view):
If someone send me an SMS while the network of my Pinephone is off (or phone powered off), I'm getting an SMS from +223344556677:
```
Stuck message from {PHONE_NUMBER}:
--------
```
{PHONE_NUMBER} being the phone number of the person who tried to text me. Unfortunately, I'm not getting the content of this SMS at all in chatty.
#### What's the expected behaviour?
Content of SMS finally downloaded and displayed in Chatty.
#### What's the current behaviour?
No way to get the content of the SMS.
#### How to reproduce your issue?
Turn off the Pinephone, send an SMS to it. Turn it on
### What device are you using?
PinePhone 1.2 Ubports Community Edition
### On what postmarketOS version did you encounter the issue?
* [ ] edge (`master` branch)
* [x] `v23.12`
* [ ] `v23.06` (supported until 2024-01-18)
* [x] I confirm that the issue still is present after running `sudo apk upgrade -a`
### On what environment did you encounter the issue?
#### Environments
* [ ] GNOME Shell on Mobile
* [x] Phosh
* [ ] Plasma Mobile
* [ ] Sxmo (Wayland/Sway) **Please post the output of `sxmo_version.sh`**
* [ ] Other: **Please fill out**
### How did you get postmarketOS image?
* [x] from https://images.postmarketos.org
* [ ] I built it using pmbootstrap
* [ ] It was preinstalled on my device
### What's the build date of the image? (in yyyy-mm-dd format)
### Additional information
Using modem firmware 0.7.2https://gitlab.com/postmarketOS/boot-deploy/-/issues/26Installation with heimdall-isorec method broken after https://gitlab.com/post...2024-03-16T06:38:05ZHenrik GrimlerInstallation with heimdall-isorec method broken after https://gitlab.com/postmarketOS/boot-deploy/-/merge_requests/50Hi, after https://gitlab.com/postmarketOS/boot-deploy/-/merge_requests/50 vmlinuz-dtb is no longer installed. This breaks the heimdall-isorec installation method, as [that method uses that file](https://gitlab.com/postmarketOS/pmbootstra...Hi, after https://gitlab.com/postmarketOS/boot-deploy/-/merge_requests/50 vmlinuz-dtb is no longer installed. This breaks the heimdall-isorec installation method, as [that method uses that file](https://gitlab.com/postmarketOS/pmbootstrap/-/blob/master/pmb/config/__init__.py?ref_type=heads#L1002). Only samsung-{i9100,i9100g,kiran} use this method at the moment.
I am not sure whether it would be best to fix this in boot-deploy or pmbootstrap, but I guess we can cat vmlinuz and the dtb somewhere in any case.https://gitlab.com/postmarketOS/pmaports/-/issues/2615samsung-manta: no output to display, hdmi works2024-03-01T11:51:42Zdasdgwsamsung-manta: no output to display, hdmi works<!--
Thank you for using postmarketOS! In order to speed up process of resolving your issue,
we would like you to fill in the following :
-->
### Describe your issue
#### What's the expected behaviour?
output on display after boot
##...<!--
Thank you for using postmarketOS! In order to speed up process of resolving your issue,
we would like you to fill in the following :
-->
### Describe your issue
#### What's the expected behaviour?
output on display after boot
#### What's the current behaviour?
display stays blank. ssh works. enabled hdmi via xrandr, looks ok.
#### How to reproduce your issue?
build current edge for samsung-manta, flash, boot
### What device are you using?
<!--
Leave name of your device in vendor-codename format.
If unsure, check name in the device package or leave full name of device
PinePhone: which revision exactly? See https://wiki.pine64.org/index.php/PinePhone#Hardware_revisions
-->
samsung-manta
### On what postmarketOS version did you encounter the issue?
<!--
Replace space inside `[ ]` with `x` to fill the checkbox
-->
* [x] edge (`master` branch)
* [ ] `v23.12`
* [ ] `v23.06` (supported until 2024-01-18)
* [x] I confirm that the issue still is present after running `sudo apk upgrade -a`
### On what environment did you encounter the issue?
#### Environments
* [ ] GNOME Shell on Mobile
* [ ] Phosh
* [ ] Plasma Mobile
* [ ] Sxmo (Wayland/Sway) **Please post the output of `sxmo_version.sh`**
* [x] Other: xfce4
### How did you get postmarketOS image?
* [ ] from https://images.postmarketos.org
* [x] I built it using pmbootstrap
* [ ] It was preinstalled on my device
### What's the build date of the image? (in yyyy-mm-dd format)
<!--
Notes:
can be left empty if unsure
If you downloaded image from images.postmarketos.org, date will be in yyyymmdd format
-->
2024-02-25
### Additional information
<!-- logs, etc. -- make use <details> for long listings -->
[dmesg.log](/uploads/b93ceb0786da0711a3d4a27f07767f23/dmesg.log)
[lineageos_17_dmesg.log](/uploads/3e1f45a5a300b064ff631d49229c11f0/lineageos_17_dmesg.log)
[twrp_dmesg.log](/uploads/57801a2c7615b3f60b74993c38160719/twrp_dmesg.log)
[twrp_dmesg3.log](/uploads/1fe1bb76d8db40ce4de15faef9770bbd/twrp_dmesg3.log)https://gitlab.com/postmarketOS/pmbootstrap/-/issues/2315documentation & other code improvements2024-02-23T06:17:50ZRobert Eckelmanndocumentation & other code improvementsWhile working on a documentation setup with sphinx and rtd-theme [WIP](https://gitlab.com/longnoserob/pmbootstrap/-/tree/docs?ref_type=heads), I noticed that many parts of the pmb code-base have no docstrings.
running flake8 with the [f...While working on a documentation setup with sphinx and rtd-theme [WIP](https://gitlab.com/longnoserob/pmbootstrap/-/tree/docs?ref_type=heads), I noticed that many parts of the pmb code-base have no docstrings.
running flake8 with the [flake8-docstrings](https://pypi.org/project/flake8-docstrings/) extension installed gave the folling report:
```
108 D100 Missing docstring in public module
2 D101 Missing docstring in public class
5 D102 Missing docstring in public method
371 D103 Missing docstring in public function
15 D104 Missing docstring in public package
1 D107 Missing docstring in __init__
41 D200 One-line docstring should fit on one line with quotes
34 D202 No blank lines allowed after function docstring
2 D204 1 blank line required after class docstring
215 D205 1 blank line required between summary line and description
62 D208 Docstring is over-indented
55 D209 Multi-line docstring closing quotes should be on a separate line
102 D210 No whitespaces allowed surrounding docstring text
3 D301 Use r""" if any backslashes in a docstring
234 D400 First line should end with a period
26 D401 First line should be in imperative mood; try rephrasing
2 D403 First word of the first line should be properly capitalized
1 E127 continuation line over-indented for visual indent
7 E128 continuation line under-indented for visual indent
1 E231 missing whitespace after ','
6 E261 at least two spaces before inline comment
2 E302 expected 2 blank lines, found 1
76 E501 line too long (83 > 79 characters)
2 E502 the backslash is redundant between brackets
2 E722 do not use bare 'except'
55 F401 '.config' imported but unused
3 W293 blank line contains whitespace
```
Full report with references to files needing improvement:
[pmb_master_flake8.txt](/uploads/697b26bb9b5f511554e2dfb517db1196/pmb_master_flake8.txt)https://gitlab.com/postmarketOS/artwork/-/issues/8sphinx-theme2024-02-22T10:50:09ZRobert Eckelmannsphinx-themehttps://gitlab.com/postmarketOS/artwork/-/issues/7Styleguide / templates / theming2024-03-08T09:17:54ZRobert EckelmannStyleguide / templates / themingIt would be good in terms of viasual communications and consitentcy to have a pmOS-styleguide.
Based on this styleguiode we could then develop:
- sphinx-theme for code documentation (esp. pmbootstrap) as HTML, PDF
- buffybox theming
- ...It would be good in terms of viasual communications and consitentcy to have a pmOS-styleguide.
Based on this styleguiode we could then develop:
- sphinx-theme for code documentation (esp. pmbootstrap) as HTML, PDF
- buffybox theming
- wiki-theme
- _others (please add)_
Questions:
1. Could the presentation/latax template be a base for this?
2. Colors/palette:
1. Keep the overall green tone of the presetnation template, maybe make it a bit lighter?
2. Or use the current design of the webpage (white & black with grey and green accents)?
3. Which font(s) to use?
@dikasetyaprayogi would that something, wehere you would be interested to give a hand?https://gitlab.com/postmarketOS/pmaports/-/issues/2613Support Wake-on-LAN and Push Notifications2024-03-17T23:28:01ZAlistair FrancisSupport Wake-on-LAN and Push Notifications### Describe your issue
#### What's the expected behaviour?
It would be great to support WoL and push notifications out of the box.
This isn't all up to us, as some server support is required. But we should at least ship it enabled on ...### Describe your issue
#### What's the expected behaviour?
It would be great to support WoL and push notifications out of the box.
This isn't all up to us, as some server support is required. But we should at least ship it enabled on the device and document how it can be setup.
We should also test it works on other major devices (like the Librem5)
There is a great write up at: https://uninsane.org/blog/mobile-linux-push-notifications/ about testing and setup
#### What's the current behaviour?
No WoL or push noties?
#### How to reproduce your issue?
### What device are you using?
<!--
Leave name of your device in vendor-codename format.
If unsure, check name in the device package or leave full name of device
PinePhone: which revision exactly? See https://wiki.pine64.org/index.php/PinePhone#Hardware_revisions
-->
### On what postmarketOS version did you encounter the issue?
<!--
Replace space inside `[ ]` with `x` to fill the checkbox
-->
* [X] edge (`master` branch)
* [ ] `v23.12`
* [ ] `v23.06` (supported until 2024-01-18)
* [ ] I confirm that the issue still is present after running `sudo apk upgrade -a`
### On what environment did you encounter the issue?
#### Environments
* [ ] GNOME Shell on Mobile
* [ ] Phosh
* [ ] Plasma Mobile
* [ ] Sxmo (Wayland/Sway) **Please post the output of `sxmo_version.sh`**
* [ ] Other: **Please fill out**
### How did you get postmarketOS image?
* [ ] from https://images.postmarketos.org
* [ ] I built it using pmbootstrap
* [ ] It was preinstalled on my device
### What's the build date of the image? (in yyyy-mm-dd format)
<!--
Notes:
can be left empty if unsure
If you downloaded image from images.postmarketos.org, date will be in yyyymmdd format
-->
### Additional information
<!-- logs, etc. -- make use <details> for long listings -->https://gitlab.com/postmarketOS/pmaports/-/issues/2610Consistent pkgver in device packages2024-03-11T18:54:55Zf_Consistent pkgver in device packagesCurrently a mess, it's not consistent. Some increment pkgver by one, others by 0.1.. There's no policy about that, would be nice to have one. Either increment pkgver by one, or by 0.1. IMO I don't really care, as long as it's consistent....Currently a mess, it's not consistent. Some increment pkgver by one, others by 0.1.. There's no policy about that, would be nice to have one. Either increment pkgver by one, or by 0.1. IMO I don't really care, as long as it's consistent.
Cc: @pabloyoyoistahttps://gitlab.com/postmarketOS/postmarketos.org/-/issues/160Proper design for HTTP 4xx/5xx pages2024-02-23T00:01:53ZLuca WeissProper design for HTTP 4xx/5xx pagesWe should have a html page that we can use in the web server config for e.g. HTTP 404 and 502 or 503 errors that looks in line with the other postmarketos.org pages.
![image](/uploads/efd73b418615f6334748497487335ded/image.png)
So I gu...We should have a html page that we can use in the web server config for e.g. HTTP 404 and 502 or 503 errors that looks in line with the other postmarketos.org pages.
![image](/uploads/efd73b418615f6334748497487335ded/image.png)
So I guess in the end there should be e.g. 404.html and 503.html in the web server root. Web server configuration will be done by the infra team in the end, not in scope of this issue.
The 5xx page(s) should link to status.postmarketos.org, something like "Please check status.postmarketos.org" with some more nice text.
I'd be thinking of something like this.
![image](/uploads/f6acdafcaab379088235341a910be380/image.png)https://gitlab.com/postmarketOS/openrc-settingsd/-/issues/5Make NTP work with Slackware2024-02-20T02:41:29ZNathaniel RussellMake NTP work with SlackwareI am trying to get ntpd to work on Slackware with openrc-settingsd but at the moment openrc-settingsd won't find the ntpd daemon that Slackware has. Is there any possible way to get this to work?I am trying to get ntpd to work on Slackware with openrc-settingsd but at the moment openrc-settingsd won't find the ntpd daemon that Slackware has. Is there any possible way to get this to work?https://gitlab.com/postmarketOS/pmaports/-/issues/2609Oneplus 6 sometimes does not receive phone calls2024-02-25T21:01:16ZSarah SpockOneplus 6 sometimes does not receive phone calls<!--
Thank you for using postmarketOS! In order to speed up process of resolving your issue,
we would like you to fill in the following :
-->
### Describe your issue
#### What's the expected behaviour?
Always receive phone calls and SM...<!--
Thank you for using postmarketOS! In order to speed up process of resolving your issue,
we would like you to fill in the following :
-->
### Describe your issue
#### What's the expected behaviour?
Always receive phone calls and SMS
#### What's the current behaviour?
After some time of having the phone on (and switching towers), it stops receiving calls and SMS. You must reboot the phone to receive calls and sms. This is a silent failure and there is no way to be aware that you are not accessible via phone or sms.
#### How to reproduce your issue?
Have phone on for at least 24 hours with most recent version of postmarked OS, then drive to a different location using a different phone tower. Then have someone call you.
### What device are you using?
<!--
Leave name of your device in vendor-codename format.
If unsure, check name in the device package or leave full name of device
PinePhone: which revision exactly? See https://wiki.pine64.org/index.php/PinePhone#Hardware_revisions
-->
Oneplus 6
### On what postmarketOS version did you encounter the issue?
<!--
Replace space inside `[ ]` with `x` to fill the checkbox
-->
* [x] edge (`master` branch)
* [x] `v23.12`
* [ ] `v23.06` (supported until 2024-01-18)
* [x] I confirm that the issue still is present after running `sudo apk upgrade -a`
### On what environment did you encounter the issue?
#### Environments
* [ ] GNOME Shell on Mobile
* [x] Phosh
* [ ] Plasma Mobile
* [ ] Sxmo (Wayland/Sway) **Please post the output of `sxmo_version.sh`**
* [ ] Other: **Please fill out**
### How did you get postmarketOS image?
* [x] from https://images.postmarketos.org
* [ ] I built it using pmbootstrap
* [ ] It was preinstalled on my device
### What's the build date of the image? (in yyyy-mm-dd format)
<!--
Notes:
can be left empty if unsure
If you downloaded image from images.postmarketos.org, date will be in yyyymmdd format
-->
### Additional information
<!-- logs, etc. -- make use <details> for long listings -->
This is a regression from the past 6 months . This was previously working.https://gitlab.com/postmarketOS/pmaports/-/issues/2607device packages should handle installing non-free firmware by default2024-02-22T20:34:06Zclayton craftdevice packages should handle installing non-free firmware by defaultdevice packages should install non-free firmware by default, because pmbootstrap might eventually no longer discover/install the `device-*-nonfree-firmware` packages. Device packages should explicitly list non-free firmware packages (whi...device packages should install non-free firmware by default, because pmbootstrap might eventually no longer discover/install the `device-*-nonfree-firmware` packages. Device packages should explicitly list non-free firmware packages (which can include "meta packages") in either `depends=` or `_pmb_recommends=`. If the firmware is required for basic functionality of the device, it should be listed in `depends=`. If it's optionally required on the device, then it can be listed in `_pmb_recommends` and users would be able to remove it later if they do not wish to have it installed. The goal is to be able to create device images that have all non-free firmware installed by default, and allow users the freedom to remove any that is not necessary. It's up to the device maintainers to figure out what "not necessary" means for their device.
This could probably be scripted out somehow, since it'll require changes to almost every device package in pmaports... The script should put every `device-*-nonfree-firmware` in the device package's `depends=`, effectively making all non-free fw required. This is the least flexible option, but it is probably the safest, since we don't know what fw is required for a device to boot, etc. This option lets device maintainers make that decision later on, and picks "safe" defaults for all device packages use non-free fw.
The benefit of this change is that we can drop some pmb code. Even though it's a lot of effort to do this change in pmaports, I still think it might be a "win" overall since I very much support making pmbootstrap simpler by doing stuff like removing unnecessary legacy code.
Relevant pmb change that sparked this: https://gitlab.com/postmarketOS/pmbootstrap/-/merge_requests/2255