manjaro-arm issueshttps://gitlab.manjaro.org/groups/manjaro-arm/-/issues2023-01-31T22:23:17Zhttps://gitlab.manjaro.org/manjaro-arm/packages/community/yay/-/issues/2Upcoming dependency change for base-devel packages2023-01-31T22:23:17ZMark WagieUpcoming dependency change for base-devel packagesFYI, there is now new meta packages for the `base-devel` group:
* `base-devel` in [Arch x64 Testing](https://archlinux.org/packages/testing/any/base-devel) / [Arch ARM Extra](https://archlinuxarm.org/packages/any/base-devel)
* `multili...FYI, there is now new meta packages for the `base-devel` group:
* `base-devel` in [Arch x64 Testing](https://archlinux.org/packages/testing/any/base-devel) / [Arch ARM Extra](https://archlinuxarm.org/packages/any/base-devel)
* `multilib-devel` in the [Arch x64 Multilib-Testing](https://archlinux.org/packages/multilib-testing/x86_64/multilib-devel) repo
Disclaimer: I still disagree about adding `base-devel` packages to dependencies because that is completely improper.https://gitlab.manjaro.org/manjaro-arm/packages/core/linux/-/issues/381016-arm64-dts-meson-radxa-zero-add-support-for-the-usb-t.patch is out-of-date2023-02-14T18:54:12ZYuntian Zhang1016-arm64-dts-meson-radxa-zero-add-support-for-the-usb-t.patch is out-of-date[Upstream patch](https://github.com/chewitt/linux/commit/fc7e516e3e999d926c00f4d753696c60808be536#diff-aa7b02d9a8cf075bba27afeebec7799ba93f4c0e1b74f99ffad6d69425ddc40eR304) has been updated to fix incorrect IRQ number.
First fixed in [v...[Upstream patch](https://github.com/chewitt/linux/commit/fc7e516e3e999d926c00f4d753696c60808be536#diff-aa7b02d9a8cf075bba27afeebec7799ba93f4c0e1b74f99ffad6d69425ddc40eR304) has been updated to fix incorrect IRQ number.
First fixed in [vendor kernel](https://github.com/radxa-repo/bsp/commit/8b6879e20fdbe3d5b0108be3e3b1793d4b1b81ee).fkardamefkardamehttps://gitlab.manjaro.org/manjaro-arm/packages/core/linux/-/issues/371004-arm64-dts-rockchip-Add-Firefly-Station-p1-support.patch can't be applied...2023-01-30T07:47:48ZYuntian Zhang1004-arm64-dts-rockchip-Add-Firefly-Station-p1-support.patch can't be applied cleanly on 6.1.8[This part](https://gitlab.manjaro.org/manjaro-arm/packages/core/linux/-/blob/master/1004-arm64-dts-rockchip-Add-Firefly-Station-p1-support.patch#L22-24) of the patch does not match [upstream code](https://github.com/gregkh/linux/blob/v6...[This part](https://gitlab.manjaro.org/manjaro-arm/packages/core/linux/-/blob/master/1004-arm64-dts-rockchip-Add-Firefly-Station-p1-support.patch#L22-24) of the patch does not match [upstream code](https://github.com/gregkh/linux/blob/v6.1.8/arch/arm64/boot/dts/rockchip/Makefile#L63-L65). This causes issues when we are trying to develop our own custom kernel based on Manjaro kernel.https://gitlab.manjaro.org/manjaro-arm/packages/community/electron/-/issues/1Drop unused versions2023-01-27T06:06:13ZMark WagieDrop unused versionsNothing depends on `electron18`, `electron19` and `electron20` currently in arm-unstable.
Status of the other versions for reference:
```
dependency-checker electron17
community/keybase-gui depends on electron17 (built by Arch Linux AR...Nothing depends on `electron18`, `electron19` and `electron20` currently in arm-unstable.
Status of the other versions for reference:
```
dependency-checker electron17
community/keybase-gui depends on electron17 (built by Arch Linux ARM Build System <builder+seattle@archlinuxarm.org>)
```
```
dependency-checker electron21
community/bitwarden depends on electron21 (built by Manjaro Build Server <build@manjaro.org>)
community/mattermost-desktop depends on electron21 (built by Dan Johansen <strit@manjaro.org>)
community/wire-desktop depends on electron21 (built by Manjaro Build Server <build@manjaro.org>)
```
```
dependency-checker electron
community/element-desktop depends on electron (built by Manjaro Build Server <build@manjaro.org>)
community/element-web make depends on electron (built by Manjaro Build Server <build@manjaro.org>)
```https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-rpi4/-/issues/6[suggestion] Enable bcache2023-01-23T15:42:18ZGhost User[suggestion] Enable bcacheThe main kernels have CONFIG_BCACHE enabled as a module. We should do this in the RPI4 kernels too.The main kernels have CONFIG_BCACHE enabled as a module. We should do this in the RPI4 kernels too.https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/279Benefits of Ethical Hacking2023-01-19T14:57:25Zaarohi21Benefits of Ethical HackingEthical hacking has several advantages for both individuals and organizations.
1.Enhance your security posture. The ability to assist firms find and address security flaws in their systems is one of the most significant advantages of et...Ethical hacking has several advantages for both individuals and organizations.
1.Enhance your security posture. The ability to assist firms find and address security flaws in their systems is one of the most significant advantages of ethical hacking. By testing their system against prospective assaults, organisations can strengthen their defences and be more equipped to handle challenges in the real world.
2. Lessen the Chance of Data Breach Data leaks are growing more frequent and can have catastrophic effects on enterprises. Ethical hacking can help to lower the risk of data breaches by locating and correcting security flaws before they can be exploited.
3. Boost Emergency Response An efficient incident response plan must be in place in the case of a security occurrence. Organizations can test and improve their incident response procedures with the aid of ethical hacking to better handle actual incidents.
4.Improve Security Awareness Companies that use ethical hacking frequently discover that it aids in increasing staff understanding of security risks. By analysing their systems and finding vulnerabilities, employees can become more security-conscious and better prepared to handle possible threats.
Read more here: [Ethical Hacking Course in Pune](https://www.sevenmentor.com/ethical_hacking_training_institute_training_classes_in_pune_best_course_in_india.php)|
[Ethical Hacking Training in Pune](https://www.sevenmentor.com/ethical_hacking_training_institute_training_classes_in_pune_best_course_in_india.php) |
[Ethical Hacking Classes in Pune](https://www.sevenmentor.com/ethical_hacking_training_institute_training_classes_in_pune_best_course_in_india.php)https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-rc/-/issues/13Ethernet does not work on Rock 3A2023-01-17T18:40:15ZGhost UserEthernet does not work on Rock 3AFor some reason Ethernet does not work on kernel 6.2 rcs.
I've now tried multiple versions of https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-rc/-/blob/master/3009-board-rock3a-gmac1.patch. All of them results in the same thi...For some reason Ethernet does not work on kernel 6.2 rcs.
I've now tried multiple versions of https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-rc/-/blob/master/3009-board-rock3a-gmac1.patch. All of them results in the same thing as not having the patch at all.
Which is there's an `end0` device via `ip addr`, but it can't be set to up and there's no link in it.
So either, this is an upstream issue or we have a config option missing for the Ethernet in the Rock 3A.
There's no problem with our 6.1 patch, so I'm not sure what changed.https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/50no LUKS asked2022-12-29T06:14:50ZThijs van Uldenno LUKS askedI see in this issue that encryption should be enabled: https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/23
But when I run the script (sudo bash manjaro-arm-installer) there is no option to encrypt. I run...I see in this issue that encryption should be enabled: https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/23
But when I run the script (sudo bash manjaro-arm-installer) there is no option to encrypt. I run the script for the Devterm and choose EXT4.
My version: 1.4.11-1 and I read that encryption is added in 1.4.0 so what am I missing here?https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-clockworkpi-a06/-/issues/8Patch not applying for 6.1.12023-01-05T21:49:22ZGhost UserPatch not applying for 6.1.1Hi @maxfierke.
The current patch to add the ClockworkPi DTS does no longer apply in 6.1.1.
Can you create a new version and post it here, so we can get this kernel updated?
It's likely just changes to the /arch/arm64/boot/dts/Rockchi...Hi @maxfierke.
The current patch to add the ClockworkPi DTS does no longer apply in 6.1.1.
Can you create a new version and post it here, so we can get this kernel updated?
It's likely just changes to the /arch/arm64/boot/dts/Rockchip/Makefile in 6.1.
Thanks. :smile:https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-rpi4-mainline/-/issues/7File /sys/class/thermal/thermal_zone0/temp is missing it no longer exists wit...2022-12-23T20:56:14ZAbraham ClarkFile /sys/class/thermal/thermal_zone0/temp is missing it no longer exists with these 6.1 kernel versions.I have a simple program which I call pitemp which tells me the temperature of all my Raspberry Pi's.
#!/bin/sh
milcel=$(cat /sys/class/thermal/thermal_zone0/temp)
echo "CPU Temperature:"
echo
ctemp=$(echo "scale=3;$milcel/1000" | bc)
...I have a simple program which I call pitemp which tells me the temperature of all my Raspberry Pi's.
#!/bin/sh
milcel=$(cat /sys/class/thermal/thermal_zone0/temp)
echo "CPU Temperature:"
echo
ctemp=$(echo "scale=3;$milcel/1000" | bc)
echo $ctemp "°C"
echo
ftemp=$(echo "scale=3;(($milcel/1000)*(9/5))+32" | bc)
echo $ftemp "°F"
echo
It serves the same function as vcgencmd measure_temp. I've noticed that whenever I was testing the 6.1-rc series kernels, that whenever I'd run my script, that I would get this message:
/sys/class/thermal/thermal_zone0/temp: The file or directory does not exist I've been combing through the kernel config and I can't account for this. both configurations for kernel 6.0.14 and 6.1.1, essentially seem to be the same so I'm at a loss. Both kernels seem to work flawlessly, and curiously enough, whenever I run vcgencmd measure_temp I get the desired result on both kernels. The only difference that is observed, is what I have already stated, that /sys/class/thermal/ exists, however, thermalzone0/temp, does not.
I would appreciate any insights. I still have some more tests and experiments to make on different devices possibly some running different distributions to see if I have consistent results. Thank you for your time and I'll be paying attention to any replies.https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/277Chromium does not load on BETA 282022-12-22T20:02:39ZSkip DoodlesChromium does not load on BETA 28Chromium was working on BETA 24. I reloaded the BETA 28 release and Chromium now doesn't load.Chromium was working on BETA 24. I reloaded the BETA 28 release and Chromium now doesn't load.https://gitlab.manjaro.org/manjaro-arm/packages/community/wayfire/wayfire/-/issues/1Rebuild with wlroots 0.162023-01-04T13:21:34ZGhost UserRebuild with wlroots 0.16This is just a reminder to rebuild this package, once wlroots 0.16 gets in the repository.
0.7.5 requires it to build.This is just a reminder to rebuild this package, once wlroots 0.16 gets in the repository.
0.7.5 requires it to build.https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer/-/issues/49Dependency binfmt-qemu-static required for manjaro-arm-installer could not b...2022-12-06T23:13:18ZRiverDependency binfmt-qemu-static required for manjaro-arm-installer could not be foundmanjaro-arm-installer has a list of Dependencies
`binfmt-qemu-static`
is not available. tried but could not find this name package.
`sudo pacman -S binfmt-qemu-static`
This is the exact package listed as needed for use of the Manja...manjaro-arm-installer has a list of Dependencies
`binfmt-qemu-static`
is not available. tried but could not find this name package.
`sudo pacman -S binfmt-qemu-static`
This is the exact package listed as needed for use of the Manjaro-arm-installer
Also tried to search for any package with name qemu-static
sudo pacman -Ss qemu-static
and it could not be found.https://gitlab.manjaro.org/manjaro-arm/packages/core/uboot-rock3a/-/issues/1validate u-boot file fails2022-12-02T19:03:45Zelpataxvalidate u-boot file failsBuilding uboot for rock 3a in a rock 3a fails.
sudo buildarmpkg -p uboot-rock3a
fails when validating the downloaded package "https://gitlab.com/pgwipeout/u-boot-quartz64/-/archive/quartz64/u-boot-quartz64-quartz64.tar.gz".
Replacing th...Building uboot for rock 3a in a rock 3a fails.
sudo buildarmpkg -p uboot-rock3a
fails when validating the downloaded package "https://gitlab.com/pgwipeout/u-boot-quartz64/-/archive/quartz64/u-boot-quartz64-quartz64.tar.gz".
Replacing the corresponding sh256sum with the actual one from the downloaded package, lets the build complete, ~~but after installing "idbloader.img" and "u-boot.itb", the board gets stuck in a boot-loop.~~
[rock3a_custom_uboot_bootlog](https://pastebin.com/yPwn6E6i)
~~I haven't changed anything except the sha256sum in PKGBUILD.
After reinstalling the original u-boot with the same commands from uboot-rock3-a.install, the board boots again.~~
~~Is this the current u-boot that is being used for the rock 3a images? The built files don't have the same size.~~
Edit: Sorry, apparently it was in a bootloop, beacause the system didn't shutdown correctly. I suppose the sha256sum may be the only problem after all.https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/274Megapixels: Could not find camera entity matching 'ov5640'2023-01-02T14:07:31ZLadislav NesneraMegapixels: Could not find camera entity matching 'ov5640'When you try to start it, it will print:
```
$ megapixels
Found config file at /usr/share/megapixels/config/pine64,pinephone-1.2.ini
Adding camera rear from config
Adding camera front from config
Could not find camera entity matching 'ov...When you try to start it, it will print:
```
$ megapixels
Found config file at /usr/share/megapixels/config/pine64,pinephone-1.2.ini
Adding camera rear from config
Adding camera front from config
Could not find camera entity matching 'ov5640'
```
- HW: PinePhone v1.2b
- OS: Manjaro | Phosh Nightly updated 2022-11-29
- megapixels: 1.5.2-1
Probably the equivalent of [this issue](https://github.com/kgmt0/megapixels/issues/1).https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephone/-/issues/21nftables, netlink broken on linux-pinephone2023-03-15T02:12:24ZP Sevensnftables, netlink broken on linux-pinephoneI was trying to use `firewalld` (having a firewall on a mobile devices might be a good idea) but couldn't start it.
<details><summary>`systemctl status firewalld` output</summary>
```
Nov 24 18:37:31 plasma-mobile firewalld[8839]: ERRO...I was trying to use `firewalld` (having a firewall on a mobile devices might be a good idea) but couldn't start it.
<details><summary>`systemctl status firewalld` output</summary>
```
Nov 24 18:37:31 plasma-mobile firewalld[8839]: ERROR: Failed to load user configuration. Falling back to full stock configuration.
Nov 24 18:37:32 plasma-mobile firewalld[8839]: ERROR: 'python-nftables' failed: netlink: Error: cache initialization failed: Invalid argument
JSON blob:
{"nftables": [{"metainfo": {"json_schema_version": 1}}, {"delete": {"table": {"family": "inet", "name": "firewalld"}}}, {>
Nov 24 18:37:32 plasma-mobile firewalld[8839]: ERROR: COMMAND_FAILED: 'python-nftables' failed: netlink: Error: cache initialization failed: Invalid argument
JSON blob:
{"nftables": [{"metainfo": {"json_schema_version": 1}}, {"add": {"table": {"family": "inet", "name": "firewalld"}}}]}
Nov 24 18:37:32 plasma-mobile firewalld[8839]: Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/firewall/core/fw.py", line 629, in start
self._start()
File "/usr/lib/python3.10/site-packages/firewall/core/fw.py", line 593, in _start
self._start_apply_objects(reload=reload, complete_reload=complete_reload)
File "/usr/lib/python3.10/site-packages/firewall/core/fw.py", line 491, in _start_apply_objects
transaction.execute(True)
File "/usr/lib/python3.10/site-packages/firewall/core/fw_transaction.py", line 161, in execute
raise FirewallError(errors.COMMAND_FAILED, errorMsg)
firewall.errors.FirewallError: COMMAND_FAILED: 'python-nftables' failed: netlink: Error: cache initialization failed: Inv>
JSON blob:
{"nftables": [{"metainfo": {"json_schema_version": 1}}, {"add": {"table": {"family": "inet", "name": "firewalld"}}}]}
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/firewall/core/fw.py", line 634, in start
self._start_failsafe()
File "/usr/lib/python3.10/site-packages/firewall/core/fw.py", line 625, in _start_failsafe
self._start_apply_objects(reload=reload, complete_reload=complete_reload)
File "/usr/lib/python3.10/site-packages/firewall/core/fw.py", line 491, in _start_apply_objects
transaction.execute(True)
File "/usr/lib/python3.10/site-packages/firewall/core/fw_transaction.py", line 161, in execute
raise FirewallError(errors.COMMAND_FAILED, errorMsg)
firewall.errors.FirewallError: COMMAND_FAILED: 'python-nftables' failed: netlink: Error: cache initialization failed: Inv>
JSON blob:
{"nftables": [{"metainfo": {"json_schema_version": 1}}, {"delete": {"table": {"family": "inet", "name": "firewalld"}}}, {>
```
</details>
Testing nftables itself turns out this isn't working at all: a simple `nft list tables` or `nft list ruleset` both result in: "netlink: Error: cache initialization failed: Invalid argument". Searching for this exact message on DuckDuckGo (Google had same result) gave exactly [one result](https://bbs.archlinux.org/viewtopic.php?id=281026) with no useful info.
Both are clean firewalld/nftables installs, as far as I'm aware; also tried removing both packages, wiping all traces of them from `/etc` (checked `/var` as well but found nothing relevant) and reinstalling them again, to no avail.
On my pinebook pro, both `firewalld` and `nftables` are working fine, so it doesn't seem to be a generic issue with Manjaro Arm. Both pinephone and pinebook pro are running latest Manjaro Arm stable.
https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephone/-/issues/19 reports at least having `firewalld` with nftables running, 5 months ago. I did an earlier attempt to get this working, about 8-10 months ago, and as far as I remember I was hitting the exact same issues as I am now (at least the `systemctl firewalld status` one, didn't dig too deep into it back then).
The only other thing I could think of, combined with some other related searching, is that this may be related to the kernel config. Comparing the `linux-pinephone` to the regular `linux` config (running on pinebook pro), the former has quite a few `CONFIG_NF_*` options disabled whereas the latter only has `CONFIG_NF_FLOW_TABLE_PROCFS` disabled; and the former has some `*NETLINK*` options disabled, whereas the latter only has `CONFIG_NETFILTER_NETLINK_HOOK` disabled. Installing the regular `linux` kernel on my pinephone makes `nft list rulesets` work, `firewalld` start successfully. Switching back to `linux-pinephone` breaks both again.
Also `nft --debug all ...` gives no useful info at all:
<details><summary>nft --debug all list ruleset</summary>
```
Entering state 0
Stack now 0
Reducing stack by rule 1 (line 914):
-> $$ = nterm input (: )
Entering state 1
Stack now 0 1
Reading a token
--accepting rule at line 353 ("list")
Next token is token "list" (: )
Shifting token "list" (: )
Entering state 26
Stack now 0 1 26
Reading a token
--accepting rule at line 859 (" ")
--accepting rule at line 324 ("ruleset")
Next token is token "ruleset" (: )
Shifting token "ruleset" (: )
Entering state 115
Stack now 0 1 26 115
Reading a token
--accepting rule at line 853 ("
")
Next token is token "newline" (: )
Reducing stack by rule 424 (line 2777):
-> $$ = nterm ruleset_spec (: )
Entering state 455
Stack now 0 1 26 115 455
Reducing stack by rule 170 (line 1473):
$1 = token "ruleset" (: )
$2 = nterm ruleset_spec (: )
-> $$ = nterm list_cmd (: )
Entering state 130
Stack now 0 1 26 130
Reducing stack by rule 31 (line 956):
-> $$ = nterm close_scope_list (: )
Entering state 480
Stack now 0 1 26 130 480
Reducing stack by rule 73 (line 1064):
$1 = token "list" (: )
$2 = nterm list_cmd (: )
$3 = nterm close_scope_list (: )
-> $$ = nterm base_cmd (: )
Entering state 46
Stack now 0 1 46
Next token is token "newline" (: )
Shifting token "newline" (: )
Entering state 4
Stack now 0 1 46 4
Reducing stack by rule 3 (line 924):
$1 = token "newline" (: )
-> $$ = nterm stmt_separator (: )
Entering state 279
Stack now 0 1 46 279
Reducing stack by rule 64 (line 1036):
$1 = nterm base_cmd (: )
$2 = nterm stmt_separator (: )
-> $$ = nterm line (: )
Entering state 45
Stack now 0 1 45
Reducing stack by rule 2 (line 915):
$1 = nterm input (: )
$2 = nterm line (: )
-> $$ = nterm input (: )
Entering state 1
Stack now 0 1
Reading a token
--(end of buffer or a NUL)
--EOF (start condition 0)
Now at end of input.
Shifting token "end of file" (: )
Entering state 2
Stack now 0 1 2
Stack now 0 1 2
Cleanup: popping token "end of file" (: )
Cleanup: popping nterm input (: )
---------------- ------------------
| 0000000020 | | message length |
| 02576 | R--- | | type | flags |
| 0000000000 | | sequence number|
| 0000000000 | | port ID |
---------------- ------------------
| 00 00 00 00 | | extra header |
---------------- ------------------
---------------- ------------------
| 0000000020 | | message length |
| 02561 | R--- | | type | flags |
| 0000000000 | | sequence number|
| 0000000000 | | port ID |
---------------- ------------------
| 00 00 00 00 | | extra header |
---------------- ------------------
netlink: Error: cache initialization failed: Invalid argument
Segmentation fault (core dumped)
```
</details>
Version info:
* linux-pinephone: 6.0.3-1
* nftables: 1:1.0.5-1
* python: 3.10.8-2
* iptables: 1:1.8.8-2
* firewalld: 1.2.1-1https://gitlab.manjaro.org/manjaro-arm/packages/core/uboot-orangepi4-lts/-/issues/1HDMI audio does not work2022-11-20T17:59:05ZBald-79HDMI audio does not workHDMI audio does not work. Is there a way to solve the problem? Pre-release Dev 20221114HDMI audio does not work. Is there a way to solve the problem? Pre-release Dev 20221114https://gitlab.manjaro.org/manjaro-arm/packages/community/gnome-mobile/js102/-/issues/1Overlay needed anymore?2022-11-18T09:17:49ZGhost UserOverlay needed anymore?Arch Linux ARM Just added js102 to their packages, so we can get updated versions from them.
So is this overlay still needed, @philm ?Arch Linux ARM Just added js102 to their packages, so we can get updated versions from them.
So is this overlay still needed, @philm ?https://gitlab.manjaro.org/manjaro-arm/packages/community/phosh/megapixels/-/issues/1Does not launch on kernel 6 on Pinephone Pro2023-01-23T12:31:08ZGhost UserDoes not launch on kernel 6 on Pinephone ProAfter the update to kernel 6 on the PinePhone Pro, it seems that `megapixels-ppp` no longer launches.
I've read in a chat somewhere (can't remember which right now), that the PPP version of Megapixels needs a few fixes for kernel 6.0 su...After the update to kernel 6 on the PinePhone Pro, it seems that `megapixels-ppp` no longer launches.
I've read in a chat somewhere (can't remember which right now), that the PPP version of Megapixels needs a few fixes for kernel 6.0 support.
Here's the output of `megapixels` on the PPP:
```
Found config file at /usr/share/megapixels/config/pine64,pinephone-pro.ini
Adding camera rear from config
Adding camera front from config
Initializing postprocessor gsetting
Found postprocessor script at /usr/share/megapixels/postprocess.sh
Initialized postprocessor to /usr/share/megapixels/postprocess.sh
setup_camera()
compatible: pine64,pinephone-pro
media_dev: rkisp1
dev: imx258 1-001a
initializing new device
video path: /dev/video8
making sure camera starts out disabled
camera device path: /dev/v4l-subdev9
setup_camera()
compatible: pine64,pinephone-pro
media_dev: rkisp1
dev: m00_f_ov8858 1-0036
initializing new device
video path: /dev/video4
making sure camera starts out disabled
camera device path: /dev/v4l-subdev4
update_state()
initializing camera
Initialized OpenGL ES 3.1
Failed to get display configuration: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist
```https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/272patch request: gnome-clocks wake from suspend2023-01-18T21:53:30Zlectrodepatch request: gnome-clocks wake from suspend
# Current state of official wake-from-suspend support in `gnome-clocks`
The current state of `gnome-clocks` being able to wake the phone from suspend for an alarm is as follows:
Upstream [gnome-clocks bug report](https://gitlab.gnome.o...
# Current state of official wake-from-suspend support in `gnome-clocks`
The current state of `gnome-clocks` being able to wake the phone from suspend for an alarm is as follows:
Upstream [gnome-clocks bug report](https://gitlab.gnome.org/GNOME/gnome-clocks/-/issues/100) is currently waiting on [systemd bug report](https://github.com/systemd/systemd/issues/17564).
# Current stop-gap solution
`wake-mobile` is technically usable, but quite limited:
* Supports one, non-repeating alarm (requires manual intervention each time - potential to miss alarm)
* Must be left running in order to work (potential to miss alarm)
* Does not work after the phone first boots up (potential to miss alarm)
# Proposed solution
The devs over at PostmarketOS have expanded upon and polished up a [solution](https://gitlab.com/postmarketOS/pmaports/-/issues/1170) originally provided on the upstream [bug report](https://gitlab.gnome.org/GNOME/gnome-clocks/-/issues/100).
In short, their solution relies on [waked](https://aur.archlinux.org/packages/waked-git), which is a background service that runs with elevated permissions and forwards `rtcwake` requests on behalf of applications. I've been testing this solution for a few days now, and it hasn't missed an alarm yet.
The benefits of using this patch set:
* No need to leave the application running in the foreground
* No potential of forgetting to launch the application (starts in background automatically at boot)
* Supports **multiple**, **repeating** alarm schedules (set once and forget)
* Uses the alarm sound configured in gnome (can be configured with Tweaks - requires reboot to take effect)
# Build files
Build files can be found here:
* https://github.com/lectrode/gnome-clocks-waked
* https://aur.archlinux.org/packages/waked-git
* https://aur.archlinux.org/pkgbase/sdbus-cpp (dependency of waked)