manjaro-arm issueshttps://gitlab.manjaro.org/groups/manjaro-arm/-/issues2023-03-15T02:12:24Zhttps://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/linux-rpi4-mainline/-/issues/4Please export /proc/config.gz to align with mainline kernel2023-03-07T21:14:03ZadamPlease export /proc/config.gz to align with mainline kernelJust surprised to see no /proc/config.gz to check if the DWC2 driver is included.Just surprised to see no /proc/config.gz to check if the DWC2 driver is included.https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-lts/-/issues/2Linux 515 seems to be missing some files.2023-03-03T12:21:30ZdaiajiLinux 515 seems to be missing some files.```
env LANG=en_US.UTF-8 LANGUAGE=en_US.UTF-8 ls -alh
total 55M
drwxr-xr-x 3 daiaji daiaji 16K Jan 1 1970 .
drwxr-x---+ 4 root root 80 Feb 13 18:43 ..
drwxr-xr-x 2 daiaji daiaji 8.0K Feb 13 18:24 extlinux
-rw-r--r-- 1 daiaji ...```
env LANG=en_US.UTF-8 LANGUAGE=en_US.UTF-8 ls -alh
total 55M
drwxr-xr-x 3 daiaji daiaji 16K Jan 1 1970 .
drwxr-x---+ 4 root root 80 Feb 13 18:43 ..
drwxr-xr-x 2 daiaji daiaji 8.0K Feb 13 18:24 extlinux
-rw-r--r-- 1 daiaji daiaji 140K Dec 28 22:54 idbloader.img
-rw-r--r-- 1 daiaji daiaji 17M Feb 13 18:31 initramfs-5.15.85-1-MANJARO-ARM-fallback.img
-rw-r--r-- 1 daiaji daiaji 8.0M Feb 13 18:30 initramfs-5.15.85-1-MANJARO-ARM.img
-rw-r--r-- 1 daiaji daiaji 30 Dec 22 02:16 linux515-aarch64.kver
-rw-r--r-- 1 daiaji daiaji 1.1M Dec 28 22:54 u-boot.itb
-rw-r--r-- 1 daiaji daiaji 30M Feb 13 18:30 vmlinuz-5.15.85-1-MANJARO-ARM
```
For example, dtbshttps://gitlab.manjaro.org/manjaro-arm/packages/core/linux/-/issues/39Wifi, battery, and other NIC devices missing since kernel 6.1.82023-02-25T19:51:51ZrmsynWifi, battery, and other NIC devices missing since kernel 6.1.8Device: Pinebook Pro, late 2022 - early 2023
The last kernel that successfully detects the `brcmfmac43455` wi-fi NIC is 6.1.7.
I've tried updating to the releases since the from 6.1.8 - 6.2, and the same issue happens. The device boots...Device: Pinebook Pro, late 2022 - early 2023
The last kernel that successfully detects the `brcmfmac43455` wi-fi NIC is 6.1.7.
I've tried updating to the releases since the from 6.1.8 - 6.2, and the same issue happens. The device boots fine, but the wi-fi device is missing. Even plugging in external USB dongles for wi-fi and ethernet are not detected. Strangely, the battery device is also missing.
I'm not familiar enough with Linux subsystems to know where to look for the common factor that would cause these devices to go missing.
Also tried removing patches added since the 6.1.7 release, and the problem still exists.
Happy to help debug, and test fixes.https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-odroid/-/issues/1Any known issue for mainline kernel not working on VIM boards?2023-02-19T20:42:17ZadamAny known issue for mainline kernel not working on VIM boards?Hi,
Just recently got upstream U-boot flashed into SPI of my VIM3 board, and can finally play around the board.
Ironically, it looks linux-vim kernel is a little less capable compared to mainline kernel:
- PCIE/USB switch
Upstream ...Hi,
Just recently got upstream U-boot flashed into SPI of my VIM3 board, and can finally play around the board.
Ironically, it looks linux-vim kernel is a little less capable compared to mainline kernel:
- PCIE/USB switch
Upstream Uboot supports MCU programming to detect PCIE/USB3 mode, and adds PCIE node into device tree.
It looks like the linux-vim device tree is not quite the same as current upstream (v5.11.1)
Thus it doesn't work on linux-vim, but works like a charm in linux mainline kernel.
- MCU/fan control
The khadas MCU and fan control support is merged into mainline kernel already.
Although it uses thermal interface, not directly using i2c interface thus the old khadas tool won't work.
In theory the MCU/fan control should work out-of-box for upstream kernel now.
- GPU/VPU
GPU is supported by panfrost, and VPU is in upstream staging drivers.
I haven't yet tested GPU output as the main usage of the board is 64K page size testing, thus GPU is not
an important part.
But I guess it would be more or less fine?
Any idea on the known issues where mainline kernel is less capable here?
Finally, you guys are really awesome!
Thanks.https://gitlab.manjaro.org/manjaro-arm/packages/community/waydroid/-/issues/11.4.0 needs dbus2023-02-16T16:35:58ZCharles Johnson1.4.0 needs dbus`dbus-python` needs to be added as a dependency and also the permissions from https://github.com/waydroid/waydroid/tree/main/dbus are not added so the container fails with `ERROR: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.3...`dbus-python` needs to be added as a dependency and also the permissions from https://github.com/waydroid/waydroid/tree/main/dbus are not added so the container fails with `ERROR: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.30" is not allowed to own the service "id.waydro.Container" due to security policies in the configuration ":1.30" is not allowed to own the service "id.waydro.Container" due to security policies in the configuration file`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/issues/pinephone/phosh/-/issues/179[Lollypop] Can't change the default music categories2023-02-12T14:33:42Zcirno-999[Lollypop] Can't change the default music categoriesHello all. I noticed I can't tap the three dots icon (marked below) which on PC opens the menu that changes the categories (like Web, Artists, Genres, Playlists). Opening it would be very useful to me as the "Albums" category is missing ...Hello all. I noticed I can't tap the three dots icon (marked below) which on PC opens the menu that changes the categories (like Web, Artists, Genres, Playlists). Opening it would be very useful to me as the "Albums" category is missing by default (which I would use).
Some additional notes I would add that on Mobian currently it's the same issue.
Perhaps this is an upstream Lollypop issue, but I don't know, I'd like to hear your thoughts on this.
![image](/uploads/688016f7fbe8c3645189ff0bebdb0630/image.png)https://gitlab.manjaro.org/manjaro-arm/packages/community/vvmd/-/issues/2What happened to 0.8-1?2023-02-11T16:55:30ZMark WagieWhat happened to 0.8-1?The package was [updated](d185ac46) here, however it seems 0.8 was never pushed to the repos: https://manjaro.org/branch-compare/?query=vvmdThe package was [updated](d185ac46) here, however it seems 0.8 was never pushed to the repos: https://manjaro.org/branch-compare/?query=vvmdPhilip MüllerPhilip Müllerhttps://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/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/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/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/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)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/issues/pinephone/plasma-mobile/-/issues/168KDE spashl (or black screen) + pointer2023-01-17T02:33:36ZLadislav NesneraKDE spashl (or black screen) + pointerOn PinePone with Manjaro & PlaMo I have an identical [problem as here](https://unix.stackexchange.com/questions/613773/black-screen-and-cursor-in-sddm) - KDE spashl (or black screen) + pointer (sddm with "Couldn't get user info (passwd) ...On PinePone with Manjaro & PlaMo I have an identical [problem as here](https://unix.stackexchange.com/questions/613773/black-screen-and-cursor-in-sddm) - KDE spashl (or black screen) + pointer (sddm with "Couldn't get user info (passwd) info" error). Do you have any idea how to solve it?
_History: PP stopped booting after update. I flashed only the boot partition with the image. Then I updated from the CLI (serial cable, WiFi connection) and it seems that the phone also works - in journald I see incoming calls and SMS, systemctl list-units --failed is empty. The aim is to preserve user data (calls, SMS, etc.)_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/issues/pinephone/plasma-mobile/-/issues/202Manjaro Plasma-Mobile - Megapixels viewfinder view does not turn to landscape2023-01-05T21:00:04ZrehejuhanManjaro Plasma-Mobile - Megapixels viewfinder view does not turn to landscapeUp-to date Manjaro Plasma-Mobile beta 9.
1. Launch Megapixels
2. Start to turn phone to landscape mode
3. Megapixels viewfinder view starts to turn also, but at little bit more than 45 degrees the view turns back to portrait mode as a na...Up-to date Manjaro Plasma-Mobile beta 9.
1. Launch Megapixels
2. Start to turn phone to landscape mode
3. Megapixels viewfinder view starts to turn also, but at little bit more than 45 degrees the view turns back to portrait mode as a narrow vertical bar in the center of viewfinder screen.
4. Expected behavior - view turns to landscape filling the whole viewfinder window.
This seems to work OK in Manjaro Plasma-Mobile Developer Edition even that the Megapixels version is the same: megapixels 1.4.2-1