Works with Munbyn ITPP941 203 dpi. Prints from Firefox but not from evince - still better than no support for my label printer.
kernel-tests passes. Kernel logs look good. No regressions in hardware support.
@tiberias I don't see any difference from the previous version. It's still compiled against Qt 5. I still have to enter my password in KWallet on every log in. The autostart is still under the same name app-Nextcloud@autostart.service (different from GNOME). There are no icons in the context menu on the tray icon. The main dialog has no menu items below my name, which is different from GNOME, which has Settings there. There is an area in the top right corner or the main dialog that has no icon. It shows a menu when clicked: Dashboard, Files, ..., Tasks (but no Settings).
The current git version of mfakto doesn't fail with unaligned access anymore, great! However, 5 out of 30 self-tests fail. gpuowl fails with "use of type 'double' requires cl_khr_fp64 support" as before.
Functional. No regressions. Tested on x86_64 with GNOME and arm64 with KDE (Asahi). nextcloud --version
reports 3.13.0git
but it's probably a cosmetic upstream issue.
The install script hangs both on update and new install. Killing nvim allows the installation to complete successfully.
I was wrong in my previous comment. The kernel is not to blame for the hang with wrong swap UUID. It's the systemd update baked into initrd. Specifically, systemd-hibernate-resume.service is started by systems 255.6-1.fc40 but not by 255.4-1.fc40. The kernel is OK, I've been using it for days.
When booting this kernel, I saw systemd waiting for a partition UUID for a long time. I tried several times - kernel-6.8.9-300.fc40.x86_64 would boot, kernel-6.8.10-300.fc40.x86_64 won't. It turns out the UUID was an old swap UUID used in the "resume" argument to the kernel. At some point that UUID changed, but it had no affect until I updated to this kernel. I restored the old UUID and adjusted /etc/fstab, which fixed booting this kernel. It's still unexpected to see that change in a minor kernel update.
$ nvim nvim: error while loading shared libraries: /usr/lib64/lua/5.1/lpeg.so: cannot open shared object file: No such file or directory
The nextcloud-client binary package requires Qt and KDE libraries. Shouldn't they be split into a separate package for KDE users? In any case, I don't see any regressions compared to the previous version.
Tried my favorite sites, downloads, PDF opening. All is good. Typing this in Chromium.
Works on Dell Inc. Inspiron 7348/0G14T4, all is good, no new errors in the kernel log, no noticeable performance changes.
The issue with Intel video on Dell Precision 7510 is resolved.
I confirm that Linux 5.9.13 fixes my issue with Dell Precision 7510. I compiled that kernel from source. It's not just GNOME X11 that is affected. GNOME on Wayland works when I login, but I get a kernel panic on reboot.
Regression on Dell Precision 7510, with Intel and nVidia video, using an internal monitor (Intel) and external monitor (nVidia). Getting flicker on internal monitor, messages in journalctl:
(WW) modeset(0): hotplug event: connector 95's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails...
kernel-5.19.11-200.fc36.x86_64 is OK. GNOME on X11. Fedora 36 updated to the current updates-testing.
The update is functional. The font is selectable in GNOME Terminal and looks good. Only variable fonts are included, which is good. The font files are identical to the ones in the GitHub repository https://github.com/googlefonts/RobotoMono
Cannot reproduce the appointment timezone issue seen in older Evolution with libical-3.0.14-1.fc35.x86_64. Tested with Office 365, everything is good.
When creating a new appointment in Evolution, the timezone resets to Atlantic/Reykjavik. If changed manually, it's reset to Atlantic/Reykjavik again when saved. I'm using evolution-3.42.3-1.fc35.x86_64 with corporate calendar in Office 365 through evolution-ews. The whole company is in America/Los_Angeles, and that's my local timezone setting. Restoring libical and libical-glib to version 3.0.13-1.fc35 fixes the problem. The timezone has the correct default and can be edited and saved.
The Ctrl-C (copy password) have been fixed. Ctrl-B (copy username) is still broken. I assume it's an upstream problem. In any case, this package is better than the previous version 2.5.2.
WiFi is working again on Apple MacBook Pro (14-inch, M2 Max, 2023) with brcmfmac