Describe the bug
I’m getting inconsistent results when converting AVIF images to other formats, using Firefox (in Ubuntu). I’m self-hosting Mazanoke 1.1.5, but the results are the same with mazanoke.com.

To Reproduce
Steps to reproduce the behavior:

1. Download this example AVIF file (as raw)
2. In Mazanoke, select Convert to: PNG
3. Drag and drop the AVIF file into the browser
4. Click the Download button of the converted file

Expected behavior
to receive a PNG file, fox.profile0.10bpc.yuv420.png

Screenshots
I receive a JPEG file, named fox.profile0.10bpc.yuv420.jpeg

Desktop (please complete the following information):

• OS: Ubuntu 24.04
• Browser Firefox 142.0.1

Additional context
The same thing (i.e. receiving a JPEG file) happens if I choose WebP as output, but not if I choose ICO: downloading the latter does produce a fox.profile0.10bpc.yuv420.ico, as expected.

Choosing JPG output also works as expected (although it would be pretty funny if it didn’t). Notably, this produces the filename fox.profile0.10bpc.yuv420.jpg: the file extension differs from the one produced by Firefox for the unexpected cases (.jpeg).

I can also work around the issue by selecting ”Download all”, which produces a zip archive, and all the files therein are in my chosen output formats as listed.

In Vivaldi (which is based on Chrome) the Download link also does produce the file in the chosen output format. So this looks like Firefox-specific issue.

Converting from (and to) other formats seems to work as expected in Firefox (at least the ones I’ve tested so far).

No problem; like I said, using node 20 works fine. I only noticed this issue recently, when I rebuilt my build environment, and tried doing so by the book (i.e. according to the docs).

If there’s something I can do to try to further narrow this down, let me know. I’m doing the build in an Ubuntu 24.04 VM, which I can restore to a working snapshot if testing causes it to break.

I was able to work around this (in a test VM, after upgrading it from 20.04 to 24.04) with adapted instructions from a blogpost [1], by temporarily installing postgresql-14 from the PGDG repository for doing the 14 -> 16 upgrade:

# apt install postgresql-common
# /usr/share/postgresql-common/pgdg/apt.postgresql.org.sh
# apt install postgresql-14
# pg_dropcluster 16 main –stop
# pg_upgradecluster 14 main
# pg_dropcluster 14 main
# apt purge postgresql-14 postgresql-client-14
# rm /etc/apt/sources.list.d/pgdg.sources
# apt update

I have yet to try this on my actual server with actual data. Please be careful if you attempt this with a production database.

*[1] https://www.directedignorance.com/blog/upgrading-postgresql-14-to-16-on-ubuntu

== Summary ==
On my computer with an ancient Nvidia chipset (Geforce 7025/nForce 630a), running `sysctl suspend` (or suspending from the Gnome menu) causes the system to start suspending, but it freezes halfway, leaving fans and hard drives spinning. There’s no way to resume from this frozen state apart from forcing a reboot (with a hardware reset button/poweroff).

== Steps to reproduce ==
* boot with modeset enabled
* run `sysctl suspend`

== What I expect to happen ==
For the system to suspend, shutting down all fans and hard drives.

== What happens ==
The system begins to suspend, but freezes halfway, leaving the display on and fans and hard drives spinning, but the keyboard unresponsive.

== Workaround ==
Disable kernel modesetting by adding ”nomodeset” to the kernel commandline.

== Affected kernels ==
Prior to upgrades the system was running HWE kernel 5.15.0, so I tried the 5.15 series, and found that I could now suspend and wake the machine again just as before. I worked my way up the versions:

* 5.15.50: unaffected
* 5.15.165: unaffected
* 5.19.17: unaffected
* 6.4.0: unaffected
* 6.6.0: unaffected
* 6.6.48: unaffected
* 6.7.0: first to fail

I also tried the current newest mainline kernel 6.10.7, and the issue is still present there.

== Background ==
I have an old desktop machine now functioning as a NAS, and yesterday I upgraded it from Ubuntu 20.04 first to 22.04, and then all the way up to 24.04. The upgrade went smoothly, and this is the only issue I’ve come across since.

In the BIOS settings of the affected machine there are three ”suspend mode” alternatives to choose from: ”S1 (POS) only”, ”S3 only” and ”Auto”. I’ve always had it on ”Auto”, but with this issue I also tested both ”S1 only” and ”S3 only”, with no effect.

The issue is also present when booting from the installation media (USB) into a live environment.

I’ve previously upgraded my laptop to 24.04, and there suspending still works as it did before the ugprade, so this is probably hardware-specific; the laptop is a modern one with all-Intel hardware.

Googling around, I could smelled hints of this being once again related to the troublesome Nvidia chipset, so I tried nomodeset with the stock 6.8.0 kernel (6.8.0-41 currently) and voilà! Suspend and wake were working again.

Well, except for the display, which stayed black. But I couldn’t say if this was the way it was before, because the NAS is normally running headless.

Yeah, still not working for me either. Restarting HA snap just results in the same traceback getting logged as before.

Settings > Devices & services > HACS shows it’s up to date (or at least at that same version, 1.34.0). I can’t find a ”Configuration” or ”HACS update” view under the HACS service, only the one with related Service info, Automations and so on (possibly because HACS is ”Not loaded”, which is the issue).

I don’t know if the host system has any bearing on this, but mine is running Ubuntu 20.04, and I’ll happily provide any other info if needed.

== System information ==
Ubuntu 23.10, up to date before today’s updates.

== Steps to reproduce (WIP) ==
0. have a group of packages that are kept back from updating, plus some that aren’t (screenshot demonstration attached) below
1. open update-manager
2. (try to) open the kept group, click on their (unchecked) checkboxes
3. do the same for some of the other, non-kept packages
4. repeat 2.-3. for a while

== What happens ==
Update-manager becomes unresponsive, then eventually segfaults:

update-manager[3292]: segfault at 30 ip 00007fc0718b4c41 sp 00007ffc2cca6a68 error 4 in libgobject-2.0.so.0.7800.0[7fc071889000+34000] likely on CPU 4 (core 0, socket 0)

== Other info ==
I’ve marked the steps above WIP because these are the conditions under which I found this today, but I haven’t yet tried narrowing them down, because of course I have little control over which updates are available. (For instance, the kept packages might just be a red herring.)

I initially tried to report the crash file with ubuntu-bug, but despite asking preliminary questions, in the end it never opened a browser to complete the report. I’ll try apport-collect next, but if that fails too, I’ll just attach the crash file here manually.

For Ubuntu 23.10, open a terminal and run `gnome-extensions disable ding@rastersoft.com`

There’s a bug report about this on Launchpad.

I have the same issue. I’m doing this in a Linux container (Ubuntu 20.04 inside Ubuntu 20.04), but like matthaios-easy-bi, I’m using npm run build:android to build (as per documentation). This has worked up until 2.0, but with 2.1 it always fails due to non-existent org.webrtc. Manually running npm install prior to npm run build:android makes no difference, nor does node node_modules/react-native-webrtc/tools/downloadWebRTC.js (although it does seemingly download the package successfully).

Here’s excerpts from the build output.

@Julian: I’d argue that if a simple accidental click somewhere can cause this, that’s a loaded gun pointed at the user’s toe, and hence a bug in the installer.

@Brian: I’ll try the 22.04 images. I’ve kept trying with 20.04.5, but have yet to find another instance of this occurring, so it’s obviously not easy to trigger.

I’m not particularly troubled by this issue (and the original reporter doesn’t seem to be either), so feel free to adjust ’Importance’ accordingly.