<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[PINE64 - PineNote Software]]></title>
		<link>https://forum.pine64.org/</link>
		<description><![CDATA[PINE64 - https://forum.pine64.org]]></description>
		<pubDate>Thu, 16 Apr 2026 06:38:34 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[http://pinenote.mweigand.net/repo_pn_stable Public Key is not available]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=20154</link>
			<pubDate>Sun, 04 Jan 2026 16:47:40 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=29806">nailliK</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=20154</guid>
			<description><![CDATA[Hello, I just ran`sudo apt update`via ssh on my V2 PineNote and I'm receiving the following warning<br />
<br />
Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: <a href="http://pinenote.mweigand.net/repo_pn_stable" target="_blank" rel="noopener" class="mycode_url">http://pinenote.mweigand.net/repo_pn_stable</a> trixie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E0B6906147A709C6]]></description>
			<content:encoded><![CDATA[Hello, I just ran`sudo apt update`via ssh on my V2 PineNote and I'm receiving the following warning<br />
<br />
Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: <a href="http://pinenote.mweigand.net/repo_pn_stable" target="_blank" rel="noopener" class="mycode_url">http://pinenote.mweigand.net/repo_pn_stable</a> trixie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E0B6906147A709C6]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Problems With Extensions After Upgrading]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=20147</link>
			<pubDate>Thu, 01 Jan 2026 06:03:43 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=29800">Notebook823</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=20147</guid>
			<description><![CDATA[So, I bought myself a PineNote like a month ago (my device is a batch 2, I think), and I'm having some issues with the Pinenote Helper extension and Maximized by default extension. <br />
<br />
I recently used a script <a href="https://git.sr.ht/~diederik/pinenote-batch2-factory-install-fixes/" target="_blank" rel="noopener" class="mycode_url">https://git.sr.ht/~diederik/pinenote-bat...all-fixes/</a> to upgrade my system (heads up to people, using sudo apt upgrade seems to put the device in a boot loop. I had to re-flash the OS). I don't know if its the script or the upgrades themselves that did this, but the PineNote Helper extension and the Maximized by default extension appear to be completely broken after upgrading. They each give separate warnings inside of the Extension Manager. I tried re-installing the Pinenote Helper extension, but it only added back the display refresh button and nothing else. <br />
<br />
Pinenote Helper error:<br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>An error has occurred in this extension. This could cause issues elsewhere in the system. It is recommended to turn the extension off until the error is resolved. <br />
<br />
<br />
Error details: Gio.DBusError:<br />
GDBus.Error:org.freedesktop.DBus.Error.UknownMethod:<br />
Unknown method SetNoOffScreen</blockquote>
<br />
<br />
Maximized by default extension:<br />
<br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>The installed version of this extension (1.3.1+pn) is incompatible with the current version of GNOME (48.4). The extension has been disabled.</blockquote>
<br />
<br />
For the Maximized by default extension error, I'm guessing I have to wait until it supports GNOME 48.4 and then upgrade my system again since I probably want the latest system updates possible at the moment. But maybe there's some other solution? <br />
<br />
Anyways, for the Pinenote Helper extension error, I'm at a bit of a dead end. I did find this <a href="https://github.com/PNDeb/pinenote-gnome-extension/issues/24" target="_blank" rel="noopener" class="mycode_url">https://github.com/PNDeb/pinenote-gnome-.../issues/24</a>, in which someone fixes the same issue I'm having by recompiling the PineNote DBUS Service. Apparently a change was made in the Pinenote Helper extension, creating a problem of some kind with the DBUS Service, which is fixed in the latest version of the DBUS Service. Only problem is, I barley know what a DBus is, much less how to recompile one. I've checked some other forum posts, but I can't find any other solutions or other posts talking about this issue. I tend to overlook things, so please let me know if some other post has already fixed this problem.<br />
<br />
I'm new to Pine64 and relatively new to Linux as a whole, so excessive amounts of detail would be appreciated so I can research and learn more!]]></description>
			<content:encoded><![CDATA[So, I bought myself a PineNote like a month ago (my device is a batch 2, I think), and I'm having some issues with the Pinenote Helper extension and Maximized by default extension. <br />
<br />
I recently used a script <a href="https://git.sr.ht/~diederik/pinenote-batch2-factory-install-fixes/" target="_blank" rel="noopener" class="mycode_url">https://git.sr.ht/~diederik/pinenote-bat...all-fixes/</a> to upgrade my system (heads up to people, using sudo apt upgrade seems to put the device in a boot loop. I had to re-flash the OS). I don't know if its the script or the upgrades themselves that did this, but the PineNote Helper extension and the Maximized by default extension appear to be completely broken after upgrading. They each give separate warnings inside of the Extension Manager. I tried re-installing the Pinenote Helper extension, but it only added back the display refresh button and nothing else. <br />
<br />
Pinenote Helper error:<br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>An error has occurred in this extension. This could cause issues elsewhere in the system. It is recommended to turn the extension off until the error is resolved. <br />
<br />
<br />
Error details: Gio.DBusError:<br />
GDBus.Error:org.freedesktop.DBus.Error.UknownMethod:<br />
Unknown method SetNoOffScreen</blockquote>
<br />
<br />
Maximized by default extension:<br />
<br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>The installed version of this extension (1.3.1+pn) is incompatible with the current version of GNOME (48.4). The extension has been disabled.</blockquote>
<br />
<br />
For the Maximized by default extension error, I'm guessing I have to wait until it supports GNOME 48.4 and then upgrade my system again since I probably want the latest system updates possible at the moment. But maybe there's some other solution? <br />
<br />
Anyways, for the Pinenote Helper extension error, I'm at a bit of a dead end. I did find this <a href="https://github.com/PNDeb/pinenote-gnome-extension/issues/24" target="_blank" rel="noopener" class="mycode_url">https://github.com/PNDeb/pinenote-gnome-.../issues/24</a>, in which someone fixes the same issue I'm having by recompiling the PineNote DBUS Service. Apparently a change was made in the Pinenote Helper extension, creating a problem of some kind with the DBUS Service, which is fixed in the latest version of the DBUS Service. Only problem is, I barley know what a DBus is, much less how to recompile one. I've checked some other forum posts, but I can't find any other solutions or other posts talking about this issue. I tend to overlook things, so please let me know if some other post has already fixed this problem.<br />
<br />
I'm new to Pine64 and relatively new to Linux as a whole, so excessive amounts of detail would be appreciated so I can research and learn more!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Quill OS for the PineNote]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=20090</link>
			<pubDate>Tue, 25 Nov 2025 21:55:06 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=29115">Szybet</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=20090</guid>
			<description><![CDATA[Quill OS is now available for the PineNote in a "working" state<br />
<br />
I don't think it's worth repeating myself with what I have written on github, so here are some links:<br />
- An a bit outdated demo: <a href="https://github.com/PorQ-Pine/docs/blob/main/public/demo.md" target="_blank" rel="noopener" class="mycode_url">https://github.com/PorQ-Pine/docs/blob/m...ic/demo.md</a><br />
- Explanation of what I'm even talking about: <a href="https://github.com/PorQ-Pine/docs/tree/main/public" target="_blank" rel="noopener" class="mycode_url">https://github.com/PorQ-Pine/docs/tree/main/public</a><br />
- Entry repo: <a href="https://github.com/PorQ-Pine/quillstrap?tab=readme-ov-file" target="_blank" rel="noopener" class="mycode_url">https://github.com/PorQ-Pine/quillstrap?...me-ov-file</a><br />
- Technical explanation of Quill OS (A cool graph <img src="https://forum.pine64.org/images/smilies/biggrin.png" alt="Big Grin" title="Big Grin" class="smilie smilie_4" />): <a href="https://github.com/PorQ-Pine/docs/tree/main/public/technical" target="_blank" rel="noopener" class="mycode_url">https://github.com/PorQ-Pine/docs/tree/m.../technical</a><br />
<br />
We are looking for people to guide them to install it and write the installation steps along the way, so if you are interested, contact us in our discord server or in the official #pinenote<br />
<br />
Also of course some more disclaimers:<br />
1. Quill on pinenote is in its early days, there are many issues and minor problems like no rotation, no sleep (sleep drains the battery a lot anyway, so i did not care to add it)<br />
2. The installation, while we used it, could have problems along the way, cant promise it would be painless, so maybe a few days without a working pinenote is possible<br />
<br />
If you have questions, feel free to ask them here<br />
<img src="https://forum.pine64.org/images/smilies/biggrin.png" alt="Big Grin" title="Big Grin" class="smilie smilie_4" />]]></description>
			<content:encoded><![CDATA[Quill OS is now available for the PineNote in a "working" state<br />
<br />
I don't think it's worth repeating myself with what I have written on github, so here are some links:<br />
- An a bit outdated demo: <a href="https://github.com/PorQ-Pine/docs/blob/main/public/demo.md" target="_blank" rel="noopener" class="mycode_url">https://github.com/PorQ-Pine/docs/blob/m...ic/demo.md</a><br />
- Explanation of what I'm even talking about: <a href="https://github.com/PorQ-Pine/docs/tree/main/public" target="_blank" rel="noopener" class="mycode_url">https://github.com/PorQ-Pine/docs/tree/main/public</a><br />
- Entry repo: <a href="https://github.com/PorQ-Pine/quillstrap?tab=readme-ov-file" target="_blank" rel="noopener" class="mycode_url">https://github.com/PorQ-Pine/quillstrap?...me-ov-file</a><br />
- Technical explanation of Quill OS (A cool graph <img src="https://forum.pine64.org/images/smilies/biggrin.png" alt="Big Grin" title="Big Grin" class="smilie smilie_4" />): <a href="https://github.com/PorQ-Pine/docs/tree/main/public/technical" target="_blank" rel="noopener" class="mycode_url">https://github.com/PorQ-Pine/docs/tree/m.../technical</a><br />
<br />
We are looking for people to guide them to install it and write the installation steps along the way, so if you are interested, contact us in our discord server or in the official #pinenote<br />
<br />
Also of course some more disclaimers:<br />
1. Quill on pinenote is in its early days, there are many issues and minor problems like no rotation, no sleep (sleep drains the battery a lot anyway, so i did not care to add it)<br />
2. The installation, while we used it, could have problems along the way, cant promise it would be painless, so maybe a few days without a working pinenote is possible<br />
<br />
If you have questions, feel free to ask them here<br />
<img src="https://forum.pine64.org/images/smilies/biggrin.png" alt="Big Grin" title="Big Grin" class="smilie smilie_4" />]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Simulating a touch through the command line]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=20026</link>
			<pubDate>Fri, 03 Oct 2025 16:50:42 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=29616">babygnu</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=20026</guid>
			<description><![CDATA[Hi all,<br />
<br />
First time poster! Excited to be here!<br />
<br />
I'm working on a project where my pine note is networked to my computer. I want to control software on my pinenote that does *not* have command line access, from my computer. <br />
<br />
Seems the best way to do this is to simulate a touch on the pinenote.<br />
<br />
Anyone know how to do this?<br />
<br />
Thanks for reading my query!<br />
<br />
- BabyGNU]]></description>
			<content:encoded><![CDATA[Hi all,<br />
<br />
First time poster! Excited to be here!<br />
<br />
I'm working on a project where my pine note is networked to my computer. I want to control software on my pinenote that does *not* have command line access, from my computer. <br />
<br />
Seems the best way to do this is to simulate a touch on the pinenote.<br />
<br />
Anyone know how to do this?<br />
<br />
Thanks for reading my query!<br />
<br />
- BabyGNU]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Wifi 5Ghz Issue]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=20003</link>
			<pubDate>Thu, 18 Sep 2025 00:36:33 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=29572">nicolaos</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=20003</guid>
			<description><![CDATA[New Pinenote user here, running on Debian Trixie. I've read the recent blog post explaining the issues with Wifi using 5Ghz, and indeed I can't connect my Pinenote to my home network on that frequency.<br />
<br />
The blog post explains 2 workarounds, the first of which involves changing your network to only use specific bands. I'm not particularly interested in that option as it won't work on any other networks when I'm away from home and I don't want to jeopardize performance to my other devices.<br />
<br />
What's not clear to me is if there's any action I can take to try out the second workaround listed there. It sounds like a more robust way to solve the issue, but the blog post doesn't seem to contain any instructions or links to instructions for how to actually do it.]]></description>
			<content:encoded><![CDATA[New Pinenote user here, running on Debian Trixie. I've read the recent blog post explaining the issues with Wifi using 5Ghz, and indeed I can't connect my Pinenote to my home network on that frequency.<br />
<br />
The blog post explains 2 workarounds, the first of which involves changing your network to only use specific bands. I'm not particularly interested in that option as it won't work on any other networks when I'm away from home and I don't want to jeopardize performance to my other devices.<br />
<br />
What's not clear to me is if there's any action I can take to try out the second workaround listed there. It sounds like a more robust way to solve the issue, but the blog post doesn't seem to contain any instructions or links to instructions for how to actually do it.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[booting is looping]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19929</link>
			<pubDate>Sun, 27 Jul 2025 04:54:08 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=29382">jabi27</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19929</guid>
			<description><![CDATA[Hi<br />
<br />
After <br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>- deleting symlink /lib64 <br />
- apt update ; apt upgrade<br />
- reboot</blockquote>
<br />
<br />
the pinenote is "booting..." and flashing the screen every 3-4 seconds and nothing else is happening.<br />
<br />
Any ideas ?<br />
<br />
Best and thanks<br />
<br />
/Jan]]></description>
			<content:encoded><![CDATA[Hi<br />
<br />
After <br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>- deleting symlink /lib64 <br />
- apt update ; apt upgrade<br />
- reboot</blockquote>
<br />
<br />
the pinenote is "booting..." and flashing the screen every 3-4 seconds and nothing else is happening.<br />
<br />
Any ideas ?<br />
<br />
Best and thanks<br />
<br />
/Jan]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[* /lib64 is a symbolic link and not pointing at usr/lib64 exactly.]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19928</link>
			<pubDate>Sat, 26 Jul 2025 15:45:32 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=29382">jabi27</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19928</guid>
			<description><![CDATA[Hi<br />
<br />
I see that others have had this issue, but it is not clear to me if there is any solution or bypass ?<br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>apt upgrade<br />
<br />
Preparing to unpack .../base-files_13.8_arm64.deb ...<br />
******************************************************************************<br />
*<br />
* The base-files package cannot be installed because<br />
* /lib64 is a symbolic link and not pointing at usr/lib64 exactly.<br />
..<br />
Error: Sub-process /usr/bin/dpkg returned an error code (1)</blockquote>
<br />
Best and thanks<br />
<br />
<br />
/Jan]]></description>
			<content:encoded><![CDATA[Hi<br />
<br />
I see that others have had this issue, but it is not clear to me if there is any solution or bypass ?<br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>apt upgrade<br />
<br />
Preparing to unpack .../base-files_13.8_arm64.deb ...<br />
******************************************************************************<br />
*<br />
* The base-files package cannot be installed because<br />
* /lib64 is a symbolic link and not pointing at usr/lib64 exactly.<br />
..<br />
Error: Sub-process /usr/bin/dpkg returned an error code (1)</blockquote>
<br />
Best and thanks<br />
<br />
<br />
/Jan]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Invalid Signature by m-weigand]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19922</link>
			<pubDate>Fri, 25 Jul 2025 11:26:48 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=29357">Francus</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19922</guid>
			<description><![CDATA[<span style="color: #666666;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font">Hello, first time user,  so I already made an error, posted first in the wrong place. But kindly <dvz_me_placeholder id="0" />  put me on the right path.</span></span><br />
<br />
<span style="color: #666666;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font">The UI in settings does not seem to work, because the packages to be updated are always the same.</span></span><br />
<br />
<span style="color: #666666;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font">Particularly firmware is brcm80211    20240709 and it seems it expects to be updated to 20250410 even if it does not work</span></span><br />
<br />
<span style="color: #666666;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font">So I tried to update using the terminal</span></span><br />
<span style="color: #666666;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font"> sudo apt update</span></span><br />
<br />
<span style="color: #666666;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font">, but I get an error regarding invalid signature: EXPKEYSIG 447D9EBF6B6F552D Maximilian Weigang</span></span><br />
<br />
<span style="color: #666666;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font">kindly <dvz_me_placeholder id="0" />  wrote the following;</span></span><br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite><span style="color: #666666;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font">If you do a web search on apt EXPKEYSIG you can find advice on fixing it, e.g.</span></span><br />
<a href="https://tecadmin.net/expired-key-expkeysig-with-apt/" target="_blank" rel="noopener" class="mycode_url"><span style="color: #3c699c;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font">https://tecadmin.net/expired-key-expkeysig-with-apt/</span></span></a><br />
<br />
<span style="color: #666666;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font">Basically, your particular install has an old key and you need to get the new one.</span></span></blockquote>
<br />
But the relevant key is not available on the server to which that page points.<br />
<br />
I also tried Ubuntu keyserver, but the key is not there.<br />
<br />
So perhaps that key does not exists and the only way to get updates is to waive GPG security and modify the repository line as follows<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>deb [trusted=yes] http://deb.debian.org/debian trixie main contrib non-free non-free-firmware</code></div></div><br />
But before doing that I would like to know if others had the same issue.<br />
<br />
<span style="color: #666666;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font">Best</span></span>]]></description>
			<content:encoded><![CDATA[<span style="color: #666666;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font">Hello, first time user,  so I already made an error, posted first in the wrong place. But kindly <dvz_me_placeholder id="0" />  put me on the right path.</span></span><br />
<br />
<span style="color: #666666;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font">The UI in settings does not seem to work, because the packages to be updated are always the same.</span></span><br />
<br />
<span style="color: #666666;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font">Particularly firmware is brcm80211    20240709 and it seems it expects to be updated to 20250410 even if it does not work</span></span><br />
<br />
<span style="color: #666666;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font">So I tried to update using the terminal</span></span><br />
<span style="color: #666666;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font"> sudo apt update</span></span><br />
<br />
<span style="color: #666666;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font">, but I get an error regarding invalid signature: EXPKEYSIG 447D9EBF6B6F552D Maximilian Weigang</span></span><br />
<br />
<span style="color: #666666;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font">kindly <dvz_me_placeholder id="0" />  wrote the following;</span></span><br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite><span style="color: #666666;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font">If you do a web search on apt EXPKEYSIG you can find advice on fixing it, e.g.</span></span><br />
<a href="https://tecadmin.net/expired-key-expkeysig-with-apt/" target="_blank" rel="noopener" class="mycode_url"><span style="color: #3c699c;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font">https://tecadmin.net/expired-key-expkeysig-with-apt/</span></span></a><br />
<br />
<span style="color: #666666;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font">Basically, your particular install has an old key and you need to get the new one.</span></span></blockquote>
<br />
But the relevant key is not available on the server to which that page points.<br />
<br />
I also tried Ubuntu keyserver, but the key is not there.<br />
<br />
So perhaps that key does not exists and the only way to get updates is to waive GPG security and modify the repository line as follows<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>deb [trusted=yes] http://deb.debian.org/debian trixie main contrib non-free non-free-firmware</code></div></div><br />
But before doing that I would like to know if others had the same issue.<br />
<br />
<span style="color: #666666;" class="mycode_color"><span style="font-family: 'Open Sans', Arial, Tahoma, sans-serif;" class="mycode_font">Best</span></span>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Page turner for PineNote (Airturn, Joyo JSP-01) - for sheet music (using KOReader)]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19831</link>
			<pubDate>Fri, 09 May 2025 15:10:04 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=29056">macmartin</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19831</guid>
			<description><![CDATA[Hi musicians (or speakers, or...)<br />
<br />
<br />
<br />
this is mostly a quick note for those who may think about getting such a gadget for playing sheet music.<br />
<br />
<br />
<br />
<br />
Although the PineNote may be a little to small it works for lyrics and chord sheets (I tweak the pages to get more on one screen).<br />
<br />
<br />
<br />
And it's good to have the backlight, e.g. for a dark stage. Unfortunately I find the flickering of the backlight distracting. But in the lower positions (not at 100% backlight) it works.<br />
<br />
<br />
<br />
<br />
The PineNote (Debian) with KOReader works perfectly fine with following page turners:<br />
<br />
- Airturn PED 500 <a href="https://www.thomann.co.uk/airturn_ped_500.htm" target="_blank" rel="noopener" class="mycode_url">https://www.thomann.co.uk/airturn_ped_500.htm</a><br />
<br />
<br />
- Airturn BT500S-2 <a href="https://www.thomann.co.uk/airturn_bt500s_2.htm" target="_blank" rel="noopener" class="mycode_url">https://www.thomann.co.uk/airturn_bt500s_2.htm</a><br />
<br />
<br />
- Joyo JSP-01 <a href="https://www.thomann.co.uk/joyo_jsp_01_page_turner_pedal.htm" target="_blank" rel="noopener" class="mycode_url">https://www.thomann.co.uk/joyo_jsp_01_pa..._pedal.htm</a><br />
<br />
<br />
<br />
<br />
<br />
<br />
I had them all and they are connecting fine and instantly via bluetooth with the PN.<br />
<br />
<br />
Page turning works out of the box with all of them in KOReader (Attention: it starts in "scrolling" mode, but you most likely want the "page flipping" mode).<br />
<br />
<br />
<br />
<br />
<br />
I didn't like the PED500 - it's very compact, usb-c, but the haptic feedback wasn't good for me.<br />
<br />
<br />
<br />
<br />
<br />
The Airturn BT500S and JSP-01 both are nice, but have their pros/cons:<br />
<br />
<br />
<br />
<br />
Airturn BT500S:<br />
<br />
<br />
- Made in USA (might be a pro argument?!)<br />
<br />
<br />
- expensive (~80Euro)<br />
<br />
<br />
- no USB-C (that was the main reason I decided against it. It has a round power jack, like you would find in a E-Guitar pedal case)<br />
<br />
- has a plastic shell, but still looks/feels nice and sturdy<br />
<br />
<br />
- the switches have a good feedback - like those of a normal effect pedal<br />
<br />
<br />
- switching of page turner mode works by holding a button. Not obvious at first, but it works.<br />
<br />
<br />
<br />
<br />
JSP-01:<br />
<br />
<br />
<br />
- I decided for this one because of the price (&lt;30Euro), the surprisingly good quality and USB-C power<br />
<br />
- Made in China (might be a con?!)<br />
<br />
- although it's all plastic it feels well manufactured<br />
<br />
- the feedback of the plastic flaps is good enough<br />
<br />
- changing the mode is easy and clear<br />
<br />
<br />
<br />
<br />
<br />
<br />
But as I said they both work well with KOReader: <br />
<br />
<br />
<br />
- in a multi-page document (and if you are in page-flipping mode) the right switch flips to the next and the left switch flips to the previous page.<br />
<br />
<br />
<br />
- If you configure KOReader to go to the next file at the end of the document, you can click through a whole set of songs/documents if the filenames are numbered in a specific order (I tried with collections, but I wasn't able to find "go to next file in collection" or something like it.)<br />
<br />
<br />
<br />
- the only things that doesn't work (or at least I didn't find out how) is to go back to the previous documents. (I put the "go back" function in one edge of the screen and configured it to go to the last position. Thats a workaround to at least go back to the previous song in case it's needed. But it doesn't work with the left pedal and you can only "go back" to the "last used" document - it will not cycle back to the first document in your set list)<br />
<br />
<br />
<br />
App-wise: Making notes is not completely straightforward. Okular can be used as a workaround, to make an edit fast. But Okular annotations may be cropped/cut off by KOReader.<br />
<br />
A solid workflow was: <br />
<br />
- I put the original PDF-files in one folder (together with the original odt files from which I exported the PDFs with libreoffice)<br />
<br />
- Editing them with Xournalpp and:<br />
<br />
    - saving the Xournalpp files in a separate xopp folder<br />
<br />
    - I export the annotated PDF files in a separate folder where I number the filenames like they occur on the setlist<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
If anyone has a more convenient approach/idea on how to setup documents, or other apps to use - I'd be glad to read about it.<br />
<br />
<br />
<br />
<br />
<br />
adios]]></description>
			<content:encoded><![CDATA[Hi musicians (or speakers, or...)<br />
<br />
<br />
<br />
this is mostly a quick note for those who may think about getting such a gadget for playing sheet music.<br />
<br />
<br />
<br />
<br />
Although the PineNote may be a little to small it works for lyrics and chord sheets (I tweak the pages to get more on one screen).<br />
<br />
<br />
<br />
And it's good to have the backlight, e.g. for a dark stage. Unfortunately I find the flickering of the backlight distracting. But in the lower positions (not at 100% backlight) it works.<br />
<br />
<br />
<br />
<br />
The PineNote (Debian) with KOReader works perfectly fine with following page turners:<br />
<br />
- Airturn PED 500 <a href="https://www.thomann.co.uk/airturn_ped_500.htm" target="_blank" rel="noopener" class="mycode_url">https://www.thomann.co.uk/airturn_ped_500.htm</a><br />
<br />
<br />
- Airturn BT500S-2 <a href="https://www.thomann.co.uk/airturn_bt500s_2.htm" target="_blank" rel="noopener" class="mycode_url">https://www.thomann.co.uk/airturn_bt500s_2.htm</a><br />
<br />
<br />
- Joyo JSP-01 <a href="https://www.thomann.co.uk/joyo_jsp_01_page_turner_pedal.htm" target="_blank" rel="noopener" class="mycode_url">https://www.thomann.co.uk/joyo_jsp_01_pa..._pedal.htm</a><br />
<br />
<br />
<br />
<br />
<br />
<br />
I had them all and they are connecting fine and instantly via bluetooth with the PN.<br />
<br />
<br />
Page turning works out of the box with all of them in KOReader (Attention: it starts in "scrolling" mode, but you most likely want the "page flipping" mode).<br />
<br />
<br />
<br />
<br />
<br />
I didn't like the PED500 - it's very compact, usb-c, but the haptic feedback wasn't good for me.<br />
<br />
<br />
<br />
<br />
<br />
The Airturn BT500S and JSP-01 both are nice, but have their pros/cons:<br />
<br />
<br />
<br />
<br />
Airturn BT500S:<br />
<br />
<br />
- Made in USA (might be a pro argument?!)<br />
<br />
<br />
- expensive (~80Euro)<br />
<br />
<br />
- no USB-C (that was the main reason I decided against it. It has a round power jack, like you would find in a E-Guitar pedal case)<br />
<br />
- has a plastic shell, but still looks/feels nice and sturdy<br />
<br />
<br />
- the switches have a good feedback - like those of a normal effect pedal<br />
<br />
<br />
- switching of page turner mode works by holding a button. Not obvious at first, but it works.<br />
<br />
<br />
<br />
<br />
JSP-01:<br />
<br />
<br />
<br />
- I decided for this one because of the price (&lt;30Euro), the surprisingly good quality and USB-C power<br />
<br />
- Made in China (might be a con?!)<br />
<br />
- although it's all plastic it feels well manufactured<br />
<br />
- the feedback of the plastic flaps is good enough<br />
<br />
- changing the mode is easy and clear<br />
<br />
<br />
<br />
<br />
<br />
<br />
But as I said they both work well with KOReader: <br />
<br />
<br />
<br />
- in a multi-page document (and if you are in page-flipping mode) the right switch flips to the next and the left switch flips to the previous page.<br />
<br />
<br />
<br />
- If you configure KOReader to go to the next file at the end of the document, you can click through a whole set of songs/documents if the filenames are numbered in a specific order (I tried with collections, but I wasn't able to find "go to next file in collection" or something like it.)<br />
<br />
<br />
<br />
- the only things that doesn't work (or at least I didn't find out how) is to go back to the previous documents. (I put the "go back" function in one edge of the screen and configured it to go to the last position. Thats a workaround to at least go back to the previous song in case it's needed. But it doesn't work with the left pedal and you can only "go back" to the "last used" document - it will not cycle back to the first document in your set list)<br />
<br />
<br />
<br />
App-wise: Making notes is not completely straightforward. Okular can be used as a workaround, to make an edit fast. But Okular annotations may be cropped/cut off by KOReader.<br />
<br />
A solid workflow was: <br />
<br />
- I put the original PDF-files in one folder (together with the original odt files from which I exported the PDFs with libreoffice)<br />
<br />
- Editing them with Xournalpp and:<br />
<br />
    - saving the Xournalpp files in a separate xopp folder<br />
<br />
    - I export the annotated PDF files in a separate folder where I number the filenames like they occur on the setlist<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
If anyone has a more convenient approach/idea on how to setup documents, or other apps to use - I'd be glad to read about it.<br />
<br />
<br />
<br />
<br />
<br />
adios]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Password reset via u-boot (init=/bin/sh) possible?]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19746</link>
			<pubDate>Wed, 19 Mar 2025 07:32:47 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=29056">macmartin</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19746</guid>
			<description><![CDATA[Hello everyone,<br />
<br />
<span style="font-weight: bold;" class="mycode_b">first I want to phrase the question:</span><br />
Is it possible to somehow reset the userpassword via setting a boot parameter in uboot to drop into a root shell (without disk encryption this should (?!) be possible in linux via the init=/bin/sh "trick"). I connected via UART and to my pinenote and tried some combinations, setting the bootcmd and others (see <a href="https://isc.sans.edu/forums/diary/Resetting+Linux+Passwords+with+UBoot+Bootloaders/28564/" target="_blank" rel="noopener" class="mycode_url">https://isc.sans.edu/forums/diary/Resett...ers/28564/</a>).<br />
<br />
<span style="font-weight: bold;" class="mycode_b">now the why</span>:<br />
<br />
What was bugging me, since I have the pinenote for 2-3 weeks now, is that it crash-reboots at least once in a using session (no heavy actions done (?!): a bit browsing and configuring koreader, xournaling some pdfs, and stuff). I thought, this is because the system is not meant to be stable by now (as far as I understood what I read)  and wasn't yet able to investigate further<br />
<br />
Now 2 days ago I apt-upgraded via terminal and the update seemed relatively big (but it was NOT my first time running the os update). The screen froze at 55% - no reaction. I was already fearful because it happened after the downloading/unpacking part and still I powercycled it after 1-2 hours. It didn't boot anymore (it showed a dark version of the image with the squares and it said "booting ...").<br />
<br />
I connected UART (thanks so much for delivering the dongle with it!!) and was presented a login.<br />
Ok, what was my root password again? I've set it up a week ago and used it some times. But although I'm 98% sure that I got it right, I was not able to log in.<br />
Ok, I created another user with sudo permissions and because of the many reboots of the pinenote I had to put it in very frequently, so I'm 99,999% sure that I have it right (still there was a slight uncertainty, because the password is somehow bound to the layout of the on-screen-keyboard) - NO, not able to login.<br />
Ok, what was the password of ther originals "user" ... yeah, I'm able to log in ... BUT ... as I created another user I removed sudo group from "user" -.-<br />
Now I'm confused even more - I can see that the user I created really exists in /etc/passwd ... so once again my reality is questioned - why wasn't I able to login?<br />
Did I tried to much and some new PAM restriction is active by default in Trixie? Seems not so. But I remembered the workaround of dropping to a root shell in grub, maybe/hopefully this also works here? But I'm not very proficient with uboot and UART yet. <br />
Alternatively: can I copy the bootmenu file from the pine, change it and put it back? <br />
Maybe there is an even easier option I didn't think of yet, before I have to flash it(?!)]]></description>
			<content:encoded><![CDATA[Hello everyone,<br />
<br />
<span style="font-weight: bold;" class="mycode_b">first I want to phrase the question:</span><br />
Is it possible to somehow reset the userpassword via setting a boot parameter in uboot to drop into a root shell (without disk encryption this should (?!) be possible in linux via the init=/bin/sh "trick"). I connected via UART and to my pinenote and tried some combinations, setting the bootcmd and others (see <a href="https://isc.sans.edu/forums/diary/Resetting+Linux+Passwords+with+UBoot+Bootloaders/28564/" target="_blank" rel="noopener" class="mycode_url">https://isc.sans.edu/forums/diary/Resett...ers/28564/</a>).<br />
<br />
<span style="font-weight: bold;" class="mycode_b">now the why</span>:<br />
<br />
What was bugging me, since I have the pinenote for 2-3 weeks now, is that it crash-reboots at least once in a using session (no heavy actions done (?!): a bit browsing and configuring koreader, xournaling some pdfs, and stuff). I thought, this is because the system is not meant to be stable by now (as far as I understood what I read)  and wasn't yet able to investigate further<br />
<br />
Now 2 days ago I apt-upgraded via terminal and the update seemed relatively big (but it was NOT my first time running the os update). The screen froze at 55% - no reaction. I was already fearful because it happened after the downloading/unpacking part and still I powercycled it after 1-2 hours. It didn't boot anymore (it showed a dark version of the image with the squares and it said "booting ...").<br />
<br />
I connected UART (thanks so much for delivering the dongle with it!!) and was presented a login.<br />
Ok, what was my root password again? I've set it up a week ago and used it some times. But although I'm 98% sure that I got it right, I was not able to log in.<br />
Ok, I created another user with sudo permissions and because of the many reboots of the pinenote I had to put it in very frequently, so I'm 99,999% sure that I have it right (still there was a slight uncertainty, because the password is somehow bound to the layout of the on-screen-keyboard) - NO, not able to login.<br />
Ok, what was the password of ther originals "user" ... yeah, I'm able to log in ... BUT ... as I created another user I removed sudo group from "user" -.-<br />
Now I'm confused even more - I can see that the user I created really exists in /etc/passwd ... so once again my reality is questioned - why wasn't I able to login?<br />
Did I tried to much and some new PAM restriction is active by default in Trixie? Seems not so. But I remembered the workaround of dropping to a root shell in grub, maybe/hopefully this also works here? But I'm not very proficient with uboot and UART yet. <br />
Alternatively: can I copy the bootmenu file from the pine, change it and put it back? <br />
Maybe there is an even easier option I didn't think of yet, before I have to flash it(?!)]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[postmarketOS / sxmo]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19743</link>
			<pubDate>Sun, 16 Mar 2025 22:40:37 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=21981">magdesign</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19743</guid>
			<description><![CDATA[is anyone successfully running <a href="https://wiki.postmarketos.org/wiki/PINE64_PineNote_(pine64-pinenote)" target="_blank" rel="noopener" class="mycode_url">postmarketOS</a> on a Pine Note?<br />
if yes, do you think i could run sxmo on it (sway, wayland?)]]></description>
			<content:encoded><![CDATA[is anyone successfully running <a href="https://wiki.postmarketos.org/wiki/PINE64_PineNote_(pine64-pinenote)" target="_blank" rel="noopener" class="mycode_url">postmarketOS</a> on a Pine Note?<br />
if yes, do you think i could run sxmo on it (sway, wayland?)]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[SSH over USB]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19703</link>
			<pubDate>Thu, 20 Feb 2025 15:42:26 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=28979">alexg11100</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19703</guid>
			<description><![CDATA[Is it possible to ssh over USB? I found this very useful with the remarkable 2 since it avoids having to deal with dynamic IP addresses etc. and you can use tools like rsync which don't seem to play nicely with a USB storage mounting.]]></description>
			<content:encoded><![CDATA[Is it possible to ssh over USB? I found this very useful with the remarkable 2 since it avoids having to deal with dynamic IP addresses etc. and you can use tools like rsync which don't seem to play nicely with a USB storage mounting.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Install SIgnal messenger?]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19683</link>
			<pubDate>Sat, 15 Feb 2025 19:31:13 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=28958">bloopedybloop</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19683</guid>
			<description><![CDATA[Any ideas about how one might install the Signal messenger app on the Pine Note?]]></description>
			<content:encoded><![CDATA[Any ideas about how one might install the Signal messenger app on the Pine Note?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Unable to find a working keepass app]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19660</link>
			<pubDate>Sat, 01 Feb 2025 20:53:20 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=28918">ntnsndr</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19660</guid>
			<description><![CDATA[I'm about a week in with my PineNote and mostly really enjoying it, figuring out one little issue at a time. But one thing has remained confounding: I can't get the on-screen keyboard to work with KeePass XC.<br />
<br />
My usual go-to is KeePassXC. However, when I open it on the PineNote, I can't get the keyboard to come up to enter my password. I can use it with a Bluetooth keyboard, but not without that. I imagine this is because it isn't GNOME-native enough (whatever the terminology is). But is there a trick to get XC working? This would be great as it would integrate with the browser.<br />
<br />
Thanks in advance for any help!]]></description>
			<content:encoded><![CDATA[I'm about a week in with my PineNote and mostly really enjoying it, figuring out one little issue at a time. But one thing has remained confounding: I can't get the on-screen keyboard to work with KeePass XC.<br />
<br />
My usual go-to is KeePassXC. However, when I open it on the PineNote, I can't get the keyboard to come up to enter my password. I can use it with a Bluetooth keyboard, but not without that. I imagine this is because it isn't GNOME-native enough (whatever the terminology is). But is there a trick to get XC working? This would be great as it would integrate with the browser.<br />
<br />
Thanks in advance for any help!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[does the Joplin note taking app work on the PineNote?]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19641</link>
			<pubDate>Thu, 23 Jan 2025 18:59:45 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=28883">derdon</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19641</guid>
			<description><![CDATA[Hello dear PineNote users,<br />
<br />
has anyone tried using Joplin on the PineNote yet? Joplin has a built in drawing function and I am curious on how that works with the stylus and the overall experience of Joplin on the PineNote.<br />
<br />
Best regards,<br />
<br />
Don]]></description>
			<content:encoded><![CDATA[Hello dear PineNote users,<br />
<br />
has anyone tried using Joplin on the PineNote yet? Joplin has a built in drawing function and I am curious on how that works with the stylus and the overall experience of Joplin on the PineNote.<br />
<br />
Best regards,<br />
<br />
Don]]></content:encoded>
		</item>
	</channel>
</rss>