Kevin's musings

Greetings everyone. I thought I would just write up a quick post on some current status and tips and information around running Fedora on pine64 pinephones.

First, let me talk about scaling. One of the problems putting a desktop OS into a small screen on a phone is scaling. Phosh (a librem started gnome-shell replacement for small screens) and Phoc (a mutter/window manager replacement that works with Phosh do there best with this issue. There’s a setting to try and resize all windows from all applications, and a way to do it on a case by case basis, however many applications are just not friendly to small screens. They refuse to shrink below a point, or they cut off valuable parts. I guess this might be something thats best solved upstream at the toolkit level, but it’s a hard problem. By default Phosh sets 200% scaling on the pinephone as well. It all depends on how small a screen/type you can handle, but lowering that gets more applications usable. You can do so via: ‘wlr-randr –output DSI-1 –scale 1.25’ for 125% for example. This also makes it harder to press buttons, so beware. 🙂

Next some great news. The latest round of uboot updates in Fedora Rawhide get my 3GB pinephone booting from a stock rawhide workstation image. Things boot, the display comes up, gnome comes up (and is really difficult to use, see above scaling issue). There’s no net, no modem, no camera, etc, but the display and the base boot chain all works great. Many thanks to Peter Robinson for getting those patches in!

A short note about flatpaks: I installed some flatpaks from flathub, and they work just dandy. The Fedora flatpak registry should soon also be advertising all it’s flatpaks for aarch64 as well. This is a great step for us down the road when we start working on a ostree version.

On the remix front, more things are getting reviewed and added to Fedora repos. chatty (sms/mms/matrix/jabber) client just finished review. There’s only a few more things on the list, but then the big one: The kernel patches. Hopefully we can find some folks to help us upstream things so we can get a vanilla fedora kernel usable. Even just getting in the patches for wifi or modem would be a great help (allowing you to ssh in and apply updates).

I’m still not using mine as a daily driver yet, there’s stil some important things not there that I need:

• MMS handling (in progress via a mmsd and chatty, but not there yet). For those in EU, in the US all group chats and anything with media uses MMS (at least on my carrier)
• The camera now works, but it’s still really not good at all. I’m hoping for improvements.
• There’s so far no good otp app packaged up. Will have to look at them and package up the best one.
• Lots of small stuff thats nice, but not urgent: the torch mode, auto rotation, docking detection

But a number of things are looking better:

• Sound works fine along with bluetooth and gpodder, so podcasts are good. (Side note: if you set the dip switch for serial console, it messes up the audio, you need to reset it back to get working audio. 😉
• epiphany works pretty well here as a web browser. Resizes nicely and is pretty fast.
• neochat seems the best of the matrix clients here (but chatty is adding matrix support, so will be interesting to see that)
• newsflash works pretty great for rss reading (although you have to actually read each article to mark it as read. The android tt-rss reader I am using on my android phone lets you just scroll by things to mark them read.
• gnome-maps seems to work fine, except no GPS. There’s some AGPS upload song and dance I haven’t looked into yet. Hopefully that can get automated so it works out of the box.
• tootle works fine for mastodon.
• cawbird works ok if I don’t give up twitter entirely.

Finally a few hardware related notes:

• In case you missed out on any of the community edition pinephones, the “Beta edition” should be open for preorders on March 24th: https://www.pine64.org/2021/03/19/beta-edition-pre-orders/ This is the same hardware as the later community editions (1.2) at the same price. 🙂
• There should be in a few months a keyboard for the pinephone. It will be a big honking battery case, so in addition to a hardware keyboard you will get a large battery too. Even though battery life has been pretty good having that extra battery will be very nice. I definitely plan to get one.
• Finally, and I can’t stress how much I still find this cool and amusing: The modem on the phonephone is a armv7 SOC. You can even run linux on it (The postmarketos folks are making a distribution for it). So wild to see a armv7 processor to just run the modem. How far we have come.

If you’re interested in the pinephone (or any other linux mobility projects), come join us on #fedora-phone on freenode or matrix or telegram.

Recently the Fedora Council has been floating the idea of modernizing the Fedora community real-time chat platform (currently IRC hosted at freenode.net). The front runner is matrix. I last looked at matrix 4 or so years ago, so I thought it would be a good time to revisit it and see how it looks today.

TLDR: I suspect we will have IRC and Matrix bridged together for a long time to come, if you are new user, use Matrix, if not keep using IRC.

First a few words about IRC (Internet Relay Chat). IRC is a 30+ year old chat protocol. There’s tons of clients. There’s tons of bots and add-ons. There’s tons of gateways and aggregators. So, whats not to like? Well, everything is a add-on mish mash that can be very confusing and frustrating for new users. For example, IRC has no persistance, you only see messages while your client is connected. So, folks invented irc “bouncers” to connect for you to the IRC networks you care about and when you reconnect play back all the messages you missed. Authentication is via messaging various services bots. Encryption is via plugins or other add ons (and often not setup). So, most old timers have a client they have carefully tuned, a bouncer and a bunch of custom bots, which is fine, but new users (not surprisingly) find this all a hassle and frustrating. IRC also has it’s own culture and rituals, some of which still make sense to me, but others that don’t.

Matrix on the other hand is pretty new (6 years). You can interact with it as a guest or have an account on a particular homeserver. If you have an account all your history is saved, and can be synced to your client on login. You can send pictures and moves and fancy gifs. You can (somewhat) have end to end encryption (see clients below) with encrypted rooms where the server can’t know what was said in the room. You can have ‘reactions’ to things people say. You can redact something you said in the past. You can have a nice avatar and a Real Name (if you like). You can join rooms/conversations with other matrix servers (for example the kde, mozilla and others are running servers). You can get read receipts to see who read your message and notifications when someone is typing (also client dependent see below).

Finally there’s matrix <–> IRC bridges. These allow conversations to be relayed from one side to another. Of course some things don’t translate over at all (reactions, receipts, typing notification, avatars) and some look different (if someone in matrix posts a picture, the people on IRC accross the bridge will see a link to the picture). The main text of the conversation is properly relayed to both sides.

I managed to re-setup my matrix homeserver (matrix.scrye.com) from 4 years ago. Ran into a little problem with the version of matrix-synapse in Fedora (It’s too old to federate right, so I built the new one and the other update thats blocking it. Hopefully that blockage will be fixed soon). It’s still a memory hog, but it runs well enough. They are working on the next generation server written in go (dentrite), but it still lacks a lot of features.

After that it was on to testing clients. There’s a bunch more available than there used to be, which is great. The documentation on them is pretty much missing for most of the clients (exception: element has docs).

The premier client is element (used to be riot). It’s available as a web app, an android app and a native linux app (which isn’t available except direct from them that I could find). The web app and android app are likely the most full featured of the clients. They support setting up client encryption and cross signing your connections so all of them can read the same encrypted rooms. For chat clients, I really prefer stand alone, as web apps have a lot of issues (not restarting on browser restart, notifications not working right, poor integration into the desktop, etc).

Fractal is the gnome native client, available as a flatpak. My impression: full screen is horrible as the chat text is centered in a small col in the middle. No way to adjust the text size or font, making it really small and non readable by me. On the plus side, it does have a ‘take me to next room with unread messages’ key, which is really nice.

nheko is a QT client with a mix of features implemented, it’s available as a rpm packaged in Fedora. My impression: Looks pretty nice, nice to be able to tag rooms into groups. Looks good full screen. There’s only really a “this room has unread messages in it”, not any indicator of _how many_ and no easy way to go to the next room with unread in it (that I could figure out). No docs at all anywhere that I could find. 🙁

Quaternion is another QT client with a mix of features implemented. No end to end encryption, but lots of the other features. It’s also available in Fedora as a rpm. My impression: looks pretty nice, lets you tag rooms and seperates them easily. Doesn’t seem to have a ‘go to next unread room’ function. ;( No docs.

spectral is a c++ client. Its packaged in Fedora, but it seems to crash on launch for me, so I didn’t get much chance to look it over. ;(

FluffyChat is a port of a native android matrix client. It’s pretty full featured and available as a flatpak. Does the chat sort of ‘sms’ style, which is cute and all, and fine for small rooms, but bad for larger discussions and such. Otherwise looks outstanding and is really fast!

Neochat is another QT client available as a rpm in Fedora. I had to tinker with my server setup and get /.well-known/matrix/client and server working before I could get neochat connecting. After that it connected fine, it was really fast, but

All of the clients seemed to handle basic chatting and history fine. Other features are all over the map. Element was the only one I saw with a search feature (to search the history). None of them had logging, which I guess could be mooted at least partly by a good search of the history/backlog. Element was the only one that seemed to have the url previews working (where the server fetches them for you and shows a preview in the client). I am not sure why so many of the clients are using QT, perhaps because kde is running their own matrix server?

So, as far as clients, I’m really missing easy ways to go to the next room with unread messages in most of them (I use this ALLLLLLLLLLLLL the time in hexchat). Logging/searching is really important to me too. I often have to look up what happened back on day X or see the exact command I used to solve something a year ago.

If you’re a new user/contributor these days I think it completely makes sense to just use a matrix client. You get history without having to deal with a bouncer and some nice other features and you can bridge to all the old fogeys on IRC. If Fedora gets it’s own home server this will be even easier (as I assume you will just be able to use your fedora account to login and create an account for you).

The real question is how long should we keep the current situation with Matrix and IRC bridged? What advantages would be dropping the irc bridges bring? Right now, not too much. End to end encryption isn’t that interesting for an open source project. Reactions are interesting (think about using them to vote up or down proposals in meetings?), but we have done without them so far. I think migration from IRC is going to be a long process, nor is there great advantage to pushing things to go faster. I hope that over coming years matrix clients continue to get better and implement more features. Someday (probably years down the road) more Fedora users will be on Matrix than IRC, then sometime after that things will have shifted enough that the community will start assuming you are on Matrix.

I have also a few other things I use my existing IRC client with: a bitlbee server to pull in other IM/twitter/etc, and a few old IRC servers that I still hang out in, so it probably doesn’t make sense for me to move over to matrix full time yet.

One additional thought: we have several IRC bots that do various things on IRC. Matrix has a handful of bots, but nothing like IRC. It’s practically a programming rite of passage to make a IRC bot. 🙂 I think we could safely look at starting design on bots for our needs for matrix and switch to them when ready (but again, no hurry at all here).

The first part of 2020 (in addition to all the horrible things happening in the world) was pretty heads down in our datacenter move. Now that that is over, and Fedora 33 is out the door (hurray!), I’m slowly trying to catch up on other things I normally do that are now a bit backlogged. This weekend, I decided to try and catch up (at least some) on my package maintaining and bugzilla bugs.

In the distant past (before 2020) I basically tried to work on this stuff mostly as it came in. Update packages when release monitoring let me know there was a release, ask questions of bug reporters as they reported and try and get something actionable. Of course now I’m behind, so lets try a different process to catch up.

First, some of you may be aware that there is a python module for bugzilla (python-bugzilla), but did you know that it also includes a handy command line interface?

Lets try some initial queries and see if we can triage things to work on things in (hopefully) some semblance of their priority.

% bugzilla query -a kevin@scrye.com -s NEW,ASSIGNED  | wc -l      
102

So, 102 bugs. Not bad at all! Oh, but wait, those are only the ones I am directly assigned to, I am in a number of groups that get assignment and I am just CCed. How bad are those:

% bugzilla query --cc kevin@scrye.com -s NEW,ASSIGNED  | wc -l
412

Well, thats not great. But some of these might be bugs that are since solved or someone else is busy working on them or they have been made moot somehow. So, I will dump that query into a text file (The default output is to give you bugnumber, state (NEW,ASSIGNED), and the summary of the bug. Amusingly, I see the oldest bug I am assigned to was filed in 2011. 🙂 So, I have those to look through and do something with, but perhaps we can make some smaller lists:

bugzilla query -a kevin@scrye.com -s NEW,ASSIGNED  | grep CVE | wc -l
3

Cool, Only 3 CVE’s are assigned to me directly. 2 of those are tracking (fedora,epel) for a ansible bug thats not fixed yet and one is for a libntlm bug. Hurray, a CVE I can check on.

So, what I usually do is read the CVE bug, looking in particular for versions (this one affects versions through 1.5). I then look on https://src.fedoraproject.org/rpms/libntlm to see what versions are in what releases. All 1.5 here. Next, I look at other libntlm bugs by going to the handy: https://bugz.fedoraproject.org/libntlm In addition to the 2 CVE tracking bugs (fedora,epel), I see there’s a release monitoring bug about 1.6 being available. Great. Time to do some packaging work.

So, this is a library, so we need to be carefull about changes and what might depend on it. Looking at the NEWS file for 1.6 however, we see: “** API and ABI modifications. No changes since last version.” Great. Thats an update and 3 less bugs. 🙂

ok, on to messing with a few packages/components that more ‘system wide’. epel-release, distribution, etc.

Then, lets look at packages that are needing updates:

bugzilla query --cc kevin@scrye.com -s NEW,ASSIGNED --outputformat '%{id}: %{component}: %{summary}'  |sed -e 's|^\#||' | sort -n | grep 'is available'
1271027: python-stevedore: python-stevedore-3.2.2 is available
1757650: python-feedparser: python-feedparser-6.0.2 is available
1771091: python-mechanize: python-mechanize-0.4.5 is available
1801531: awscli: awscli-2.0.61 is available
1813734: hiredis: hiredis-1.0.0 is available
1815307: bodhi: bodhi-5.5.0 is available
1829595: python-redis: python-redis-3.5.3 is available
1839836: blueberry: blueberry-1.3.9 is available
1846161: iperf3: iperf3-3.9 is available
1848739: ansible: ansible-2.10.1 is available
1862178: python-eventlet: python-eventlet-0.29.1 is available
1862531: python-vcrpy: python-vcrpy-4.1.1 is available
1880754: calibre: calibre-5.4.2 is available
1881455: python-greenlet: python-greenlet-0.4.17 is available
1886993: mxml: mxml-3.2 is available
1888249: python-pygal: python-pygal-3.0.0.dev1 is available
1890435: koji: koji-1.23.0 is available
1890954: GitPython: GitPython-3.1.11 is available
1891597: libnftnl: libnftnl-1.1.8 is available
1891769: nftables: nftables-0.9.7 is available
1893366: wordpress: wordpress-5.5.3 is available
1893453: iptables: iptables-1.8.6 is available

Some of those are blocked (calibre needs sip5 packaged, ansible needs 2.10.x packaged (which I have done, but need to clean up and submit)), but some of the others should be pretty easy. 🙂 Lets see how far I can get today!

A few hours later…

% bugzilla query --cc kevin@scrye.com -s NEW,ASSIGNED  | wc -l
380

Dealt with 32 bugs. Not a bad afternoon I guess. 🙂 I hope the command line bugzilla use and triage helps others deal with bugs as well.