FWIW for me it appears to be fixed with 4.1.2, thanks!

Here are some more logs from my end, since I'm experiencing the same problem. I think it's a regression with 4.0.0 and it only seems to happen when I zoom the content size:

19:28:49 - DEBUG - navigation action uri: about:blank  (news_flash_gtk::article_view::webview::imp:270)
19:28:49 - DEBUG - navigation action uri: about:blank  (news_flash_gtk::article_view::webview::imp:270)
19:28:50 - DEBUG - set show article view: false        (news_flash_gtk::content_page::article_view_column:398)
19:28:50 - DEBUG - navigation action uri: https://flathub.org/ (news_flash_gtk::article_view::webview::imp:270)
19:28:51 - DEBUG - widget height: 0                    (news_flash_gtk::article_view::scrollable::imp:246)
19:28:51 - DEBUG - header height: 148                  (news_flash_gtk::article_view::scrollable::imp:247)
19:28:51 - DEBUG - webview height: 908                 (news_flash_gtk::article_view::scrollable::imp:248)
19:28:51 - DEBUG - upper: 1056                         (news_flash_gtk::article_view::scrollable::imp:249)
19:28:51 - DEBUG - page_size: 0                        (news_flash_gtk::article_view::scrollable::imp:250)
19:28:51 - DEBUG - widget height: 1362                 (news_flash_gtk::article_view::scrollable::imp:246)
19:28:51 - DEBUG - header height: 148                  (news_flash_gtk::article_view::scrollable::imp:247)
19:28:51 - DEBUG - webview height: 433                 (news_flash_gtk::article_view::scrollable::imp:248)
19:28:51 - DEBUG - upper: 581                          (news_flash_gtk::article_view::scrollable::imp:249)
19:28:51 - DEBUG - page_size: 581                      (news_flash_gtk::article_view::scrollable::imp:250)
19:28:51 - DEBUG - widget height: 1362                 (news_flash_gtk::article_view::scrollable::imp:246)
19:28:51 - DEBUG - header height: 148                  (news_flash_gtk::article_view::scrollable::imp:247)
19:28:51 - DEBUG - webview height: 549                 (news_flash_gtk::article_view::scrollable::imp:248)
19:28:51 - DEBUG - upper: 697                          (news_flash_gtk::article_view::scrollable::imp:249)
19:28:51 - DEBUG - page_size: 697                      (news_flash_gtk::article_view::scrollable::imp:250)
19:28:51 - DEBUG - widget height: 1362                 (news_flash_gtk::article_view::scrollable::imp:246)
19:28:51 - DEBUG - header height: 148                  (news_flash_gtk::article_view::scrollable::imp:247)
19:28:51 - DEBUG - webview height: 907                 (news_flash_gtk::article_view::scrollable::imp:248)
19:28:51 - DEBUG - upper: 1055                         (news_flash_gtk::article_view::scrollable::imp:249)
19:28:51 - DEBUG - page_size: 1055                     (news_flash_gtk::article_view::scrollable::imp:250)
19:28:51 - DEBUG - Easylist adblock filter loaded      (news_flash_gtk::article_view::webview::imp:486)

My resolution is 3440x1440 with 100% zoom factor (so no actual additional scaling/zooming on the monitor level) in GNOME.

I can confirm that if I make the window smaller vertically instead of fullscreen I can do some scrolling on the article, but not much, whilst when it's fullscreen I can do no scrolling. This happens for me with article 'GCAP 2024' from the Flatpak new application feed.

Sorry for the late reply, I didn't get any notifications from these posts for some reason. And no problem, I understand that time for FOSS isn't always easy to allocate.

I changed the title of the ticket to indicate that the project is looking for new maintainers. As alluded to on the Atom plugin ticket and visible from my involvement lately before I don't intend to maintain Serenata myself since I don't work with PHP professionally any more and have since moved on to other language pastures.

It would be unfortunate to see Serenata die if no one steps up, but I see that at least PHPActor and Phan offer LSP support and are maintained - especially the former appears to offer most of the features Serenata does, so in the spirit of FOSS without new maintainers Serenata will or already has been superseded by maintained (and possibly superior, I wouldn't know since I haven't tested it) alternatives 😉 .

If anyone does believe Serenata to have more potential than the alternatives, feel free to fork, or request contributor rights - if I see that contribution with those rights goes well for a while and there is some trust in the future under a new flag from my part, I'm also willing to hand over organisation and repository ownership 🙂.

I am curious, since I don't have a Linux phone of any kind, what's the experience like? How usable is it?

Well... I think the best way to describe it is: it is the same as using desktop Linux every day for work or home use; expect rough edges with stuff that works on other platforms without issues but somehow doesn't on yours, but also awesomeness on other fronts that you won't easily find on other platforms. 😅

To avoid making this post too long because there is a lot to say, I'll try to do a quick breakdown of pain points and good things personal to me.

The good:

• Privacy is dear to me, so carrying an Android/iOS device around all the time wasn't an option for me and my employer wanted me to have a smartphone of some type, so the Librem Phone happened and it delivers on that regard with control over the hardware switches for the modem, Wi-Fi, and microphone.
• You have the full power of Debian-based ARM64 Linux at your disposal. Flatpak works fine as well. You can do pretty much whatever you can also do on other Linux systems, including scripting SMS, updating your phone over SSH, and so on. You can even turn it into a server with touch screen if you wanted to.
• Purism tries to upstream patches as much as possible and are on the almost latest Linux kernel (I believe 6.6 or 6.7 now), so that if they end up going out of business, someone else can still pick up software support relatively easily.
• Full convergence is pretty neat; plug into a dock with screen, mouse and keyboard and you can use it like a desktop. I don't use this much, though.
• Battery life used to be around 10 to 12 hours, but they now have experimental suspend support where the phone can wake itself up when a call or SMS comes in, so now it's up to approximately 20 hours, which is pretty good.
• Several parts of the hardware are replaceable, including the battery.
• It seems to really be aimed at longevity hardware and software wise. I've had the phone for about three years now, the battery is still fine, I still get updates and support so far, and there has been no announcement of a new phone to try and get everyone to buy a new one.
• You rarely encounter applications that don't work at all because Linux/Debian has been supporting ARM64 for quite some time now. You might encounter ones that can't deal with the small screen or adaptive form factor, but 'GNOME' applications as in GTK4 and Adwaita ones (such as Mission Center) work pretty much as expected on the mobile screen with toggleable sidebars and such.

The iffy:

• Of course you can't use Android or iOS apps outside something like Anbox or perhaps even installing actual Android on the phone, but that kind of misses the point, so don't buy it if you need specialty mobile apps that don't provide alternatives such as a web application that works in a browser.
• To get good call quality nowadays, you need VoLTE with 4G. Depending on your cellular provider though, it's hit or miss if you can get this on the Librem Phone because apparently it's hard to get this right for every provider for Purism (because technical reasons) - if it doesn't work for you, you can get in touch with Purism support to try and update the modem to more recent firmware to have more luck. If it ends up not working regardless, it's becoming a problem now because providers are starting to retire 3G entirely, which you'll be falling back to if it doesn't work. Not sure how Purism intends to 'handle' this. In my case it worked out of the box with my Belgian provider, though, and incoming/outgoing call quality is as good as it is with other phones for me.
• Bluetooth works fine, and I can play audio in my car even, but the Bluetooth stuff for calling hands-free isn't supported yet. Apparently Pipewire now supposedly supports this, but the Librem Phone has yet to catch up to this development (it still uses PulseAudio). The Librem Phone uses PureOS, which is basically Debian with some custom software and patches by Purism specifically fro the Librem Phone and there other devices, meaning they prefer stable over cutting edge - a good thing for a phone, but they then need to 'backport' stuff over if they need cutting edge stuff like Pipewire or more upstream versions of things.
• Default software is mostly GNOME apps, but they are old versions, because of the Debian base thing. As a result, the stock version of GNOME Maps is horrible to use on touch devices, which can easily be alleviated by installing it through Flatpak, in which case you not only get the latest version, but they actually support touch properly with all the mobile and adaptive GTK/GNOME developments in the last few years.
• Other software tends to have rough edges too, such as:
  • The occasional Wi-Fi not coming online when you activate one of the hardware switches.
  • The latest Epiphany Flatpak or WebKit not showing the on-screen keyboard when you tap an input field on a page; the stock Epiphany does this fine, though, but it's subjectively much slower, and Firefox takes 10 seconds or so to start.
  • Some apps not using the latest libadwaita stuff and having a dialog box that extends beyond the screen.
  • The screen sometimes not coming on because of a more recent issue that requires rebooting a few times.
  • The camera application handles determining exposure and other settings automatically, but the algorithm (which they had to develop manually because of it being mostly proprietary everywhere else, to be fair) is not on point yet and sometimes chooses poor settings (which you then need to override).
• Performance is not on point yet: whilst daily use of the shell is good, don't expect convergence with a 4k or ultra-wide monitor on 144 Hz to be a buttery smooth experience 😅.

When installing the AARCH64 build of Mission Center through Flatpak, starting it on a Librem Phone results in a crash when starting up. The following logs are printed:

Apr 05 15:00:16 librem sm.puri.Phosh.desktop[8623]: thread 'main' panicked at /run/build/missioncenter/cargo/vendor/pathfinder_gl/src/lib.rs:434:17:
Apr 05 15:00:16 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:16 librem missioncenter[8623]: Failed to get property "Addresses": GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Interface ‘org.freedesktop.DBus.Properties’ on object with path / does not exist
Apr 05 15:00:16 librem missioncenter[8623]: Failed to get property "Addresses": GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Interface ‘org.freedesktop.DBus.Properties’ on object with path / does not exist
Apr 05 15:00:16 librem missioncenter[8623]: Failed to get property "Addresses": GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Interface ‘org.freedesktop.DBus.Properties’ on object with path / does not exist
Apr 05 15:00:16 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:16 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:16 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:15 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:15 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:15 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:15 librem missioncenter[8623]: Failed to read memory device information, host command execution failed: Unknown device "/sys/devices/virtual/dmi/id": No such device
Apr 05 15:00:14 librem missioncenter[8623]: Failed to get property "Addresses": GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Interface ‘org.freedesktop.DBus.Properties’ on object with path / does not exist
Apr 05 15:00:14 librem missioncenter[8623]: Failed to get property "Addresses": GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Interface ‘org.freedesktop.DBus.Properties’ on object with path / does not exist
Apr 05 15:00:14 librem missioncenter[8623]: Failed to create udev device from "/sys/devices/platform/soc@0/38100000.usb/gadget.0/net/usb0". No such file or directory
Apr 05 15:00:13 librem missioncenter[8623]: Failed to get property "Addresses": GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Interface ‘org.freedesktop.DBus.Properties’ on object with path / does not exist
Apr 05 15:00:13 librem missioncenter[8623]: Failed to create udev device from "/org/freedesktop/ModemManager1/Modem/0". Invalid argument
Apr 05 15:00:13 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:13 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:13 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:13 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:13 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:13 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS

The Librem Phone runs PureOS Byzantium (based on Debian) as latest stable, so if Mission Center depends on host tools (lsblk?), they may be older than expected.

Can verify this fixed it on the Librem Phone 🎉 , thanks!

Okay, no problem. By all means, if it is easier or more opportune to replace Pathfinder for the entire application then that is also the way I would go.

Happy to try out a test build without Pathfinder on the Librem Phone 🙂 .

Thanks for the reply.

If I can create a build of the main branch, where Pathfinder was removed, for AARCH64, would you be willing to test it out?

Sure!

I'm not familiar with Pathfinder, but if it's a bug there, I'd be happy to upvote or report there instead. The Librem Phone has a Vivante GPU and should support hardware acceleration, but as mentioned some of the dependencies and drivers may be older as Purism adds additional conservatism on the already conservative Debian, so there may also be driver bugs, in which case I'm willing to report it to Purism instead.

EDIT: Not sure if Mission Center is compiling custom shaders, but the line in question appears to be this one, linked to an OpenGL shader not being able to be compiled.

When installing the AARCH64 build of Mission Center through Flatpak, starting it on a Librem Phone results in a crash when starting up. The following logs are printed:

Apr 05 15:00:16 librem sm.puri.Phosh.desktop[8623]: thread 'main' panicked at /run/build/missioncenter/cargo/vendor/pathfinder_gl/src/lib.rs:434:17:
Apr 05 15:00:16 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:16 librem missioncenter[8623]: Failed to get property "Addresses": GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Interface ‘org.freedesktop.DBus.Properties’ on object with path / does not exist
Apr 05 15:00:16 librem missioncenter[8623]: Failed to get property "Addresses": GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Interface ‘org.freedesktop.DBus.Properties’ on object with path / does not exist
Apr 05 15:00:16 librem missioncenter[8623]: Failed to get property "Addresses": GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Interface ‘org.freedesktop.DBus.Properties’ on object with path / does not exist
Apr 05 15:00:16 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:16 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:16 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:15 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:15 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:15 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:15 librem missioncenter[8623]: Failed to read memory device information, host command execution failed: Unknown device "/sys/devices/virtual/dmi/id": No such device
Apr 05 15:00:14 librem missioncenter[8623]: Failed to get property "Addresses": GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Interface ‘org.freedesktop.DBus.Properties’ on object with path / does not exist
Apr 05 15:00:14 librem missioncenter[8623]: Failed to get property "Addresses": GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Interface ‘org.freedesktop.DBus.Properties’ on object with path / does not exist
Apr 05 15:00:14 librem missioncenter[8623]: Failed to create udev device from "/sys/devices/platform/soc@0/38100000.usb/gadget.0/net/usb0". No such file or directory
Apr 05 15:00:13 librem missioncenter[8623]: Failed to get property "Addresses": GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Interface ‘org.freedesktop.DBus.Properties’ on object with path / does not exist
Apr 05 15:00:13 librem missioncenter[8623]: Failed to create udev device from "/org/freedesktop/ModemManager1/Modem/0". Invalid argument
Apr 05 15:00:13 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:13 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:13 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:13 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:13 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS
Apr 05 15:00:13 librem missioncenter[8623]: Failed to refresh block device information, host command execution failed: lsblk: unknown column: MOUNTPOINTS

The Librem Phone runs PureOS Byzantium (based on Debian) as latest stable, so if Mission Center depends on host tools (lsblk?), they may be older than expected.

I'm a Dutch translation contributor, but arguably 'Ouderdom' ('age' translated literally) is used sometimes in Dutch software translations to indicate 'what is the age of the process', or 'how old is the process', or 'how long has it been running'.

I do agree though that specifically how it's displayed in Mission Center doesn't make sense with the current translation:

'In bedrijf' makes some sense, but as-is just means 'Running'. I pushed an update to the translations that changes it to 'Tijd in bedrijf' ('running time' roughly directly translated) instead, is that acceptable?

EDIT: It's now present in this Weblate merge request.

For what it's worth, /sys/class/drm/card*/device/power_state (where the asterisk is a number depending on which GPU it is) returns D3cold in my case on an Optimus laptop if the NVIDIA dGPU is fully powered down - there are also some other states like D3hot IIRC just before it hits D3cold or just D0 if it is powered up.

Reading this value doesn't spin up the GPU like using nvidia-smi or other tools does, so perhaps it could be used as an early check to just display 'GPU currently powered down' or similar (assuming this file can be read from a Flatpak).

EDIT: Note that there is an open issue with Optimus setups where starting some GTK4 applications will power up the dGPU anyway, but if the application ends up running on the iGPU it will power down again after a few seconds - just mentioning this since it might make testing confusing if Mission Center also suffers from this.

I can confirm this build fixes it for me. I tried the following, which all seem to work:

• Reuse my old database from 2.x.
• Start fresh and import my full OPML, which includes the nested categories from the example feed as well.

Thanks! Now I can enjoy the sidebar improvements from 3.0 🙂 .

How did you manage to create that inside of NewsFlash? Because I think the only option would be to have & import an OPML that contains one or to sync with a service that supports subcategories.

Yes, the former. I originally migrated from an OPML exported from Liferea with the nested subfolders in them already. They always seemed to be handled correctly for me in NewsFlash 2.x, so I didn't pay any further attention to them.

Because I had problems in 3.0, I downgraded to export a new OPML from NewsFlash 2.x, and then tried to reimport in 3.0, hoping that this might fix the database being corrupted or something, which is when I hit this problem. To finally create the example OPML from my post, I just stripped down that exported OPML further to remove feeds that didn't seem to be part of the problem.

(I restored a back-up of the database to do the OPML export as well, since once the database is opened with 3.x and the feeds disappear, 2.x doesn't seem to be able to open the database any more either.)

I've created an OPML with just a few folders and a single feed that reproduces the issue:

FeedsTest.opml

Steps to reproduce:

1. Clear database.sqlite from NewsFlash to start clean.
2. Import the OPML above.
3. Try to move the imported feed somewhere.
4. See error.
5. Try to refresh feeds.
6. See error after spinner spins a while.
7. Restart NewsFlash.
8. All feeds are gone.

General Information:

• Distribution: Arch Linux x86-64
• Desktop Environment: GNOME 45
• NewsFlash Package Type: Flatpak
• NewsFlash Version: 3.0.0
• NewsFlash Back-end: Local RSS / inoreader / etc. Local

Observed behavior and how to reproduce:

1. Have some local feeds, some in categories.
2. Upgrade to 3.0.0.
3. Start the application.
4. Feeds show up correctly; in the database I see migrations happened.
5. Try to move a feed in the sidebar a row higher.
6. Get error pop-up related to not being able to 'add category to feed'.
7. Try to refresh feeds - spinner spins for a while, but no new feeds are pulled (also seems to finish way too quickly compared to 2.3.0 for an unknown reason, but those may be performance improvements, I guess). Get error about not being able to add feed.
8. Restart the application.
9. All feeds are gone, the sidebar is empty. The error about not being able to add feeds shows again.

Expected behavior:

I guess it's obvious 😉, but all feeds display and refresh like in 2.3.x.

Other info:

I'm assuming that this isn't happening for everyone as it would have been spotted early, so it may be related to my exact set of feeds. If need be, I can supply them, but I need to try and prepare a smaller set to reproduce with in that case since there are a few URLs in there that point to the local network and might make testing less reproducible for others.

Gert (2ed32d41) at 26 Aug 07:40

This one wasn't present on Weblate yet, so I added it and immediately translated the existing POT file using Poedit. Enjoy 🙂 !

Gert (2ed32d41) at 25 Aug 18:20

Gert (5cba1210) at 11 Jul 01:18