I'm seeing RPM scriptlet failures on upgrade to this version (can't copy them here because they're truncated to cut off all useful information by dnf5), and I'm also seeing crashes every few minutes.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
Indeed you are correct @decathorpe. Processes dying here too:
Dec 14 08:21:39 tracker-miner-fs-3[4537]: (tracker-extract-3:4537): Tracker-WARNING **: 08:21:39.862: File 'file:///home/_homedir/Documents/software/lenovo/t450s_hmm_en_sp40g54937.pdf' took too long to process. Shutting down everything
Dec 14 08:21:39 tracker-miner-f[4344]: Extractor subprocess died unexpectedly: Child process exited with code 1
Dec 14 08:21:40 tracker-miner-fs-3[4858]: (tracker-extract-3:4858): GLib-WARNING **: 08:21:40.928: getpwuid_r(): failed due to unknown user id (5000)
Dec 14 08:21:58 tracker-miner-fs-3[4858]: libpng warning: iCCP: known incorrect sRGB profile
Dec 14 08:25:19 tracker-miner-fs-3[5542]: (tracker-extract-3:5542): GLib-WARNING **: 08:25:19.208: getpwuid_r(): failed due to unknown user id (5000)
The RPM scriptlet failures you are seeing are most likely from the old package being updated and therefore nothing we can do about, but the crashes sound serious.
Could one of you file the miner crashes upstream at https://gitlab.gnome.org/GNOME/localsearch/-/issues please? I have no idea what's going on here but upstream would probably be able to quickly figure it out.
@decathorpe, the error from my journal is apparently a normal thing. If you have a backtrace for what you're seeing, upstream would like to hear from you.
I have reset my tracker database and can see the same SIGSEGV crashes for the "bad" files with the previous stable tracker-miners version, so this is not a new issue. Disregard my -1 karma (though I won't give +1).
This update has been submitted for testing by kalev.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
Works.
Works great! LGTM! =)
This update can be pushed to stable now if the maintainer wishes
I'm seeing RPM scriptlet failures on upgrade to this version (can't copy them here because they're truncated to cut off all useful information by dnf5), and I'm also seeing crashes every few minutes.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
Running
tracker3 statusshows multiple paths withCrash/hang handling filemessages.Indeed you are correct @decathorpe. Processes dying here too:
The RPM scriptlet failures you are seeing are most likely from the old package being updated and therefore nothing we can do about, but the crashes sound serious.
Could one of you file the miner crashes upstream at https://gitlab.gnome.org/GNOME/localsearch/-/issues please? I have no idea what's going on here but upstream would probably be able to quickly figure it out.
https://gitlab.gnome.org/GNOME/localsearch/-/issues/377
no regressions noted, but 0 due others users comments
Thanks! I appreciate the help.
@decathorpe, the error from my journal is apparently a normal thing. If you have a backtrace for what you're seeing, upstream would like to hear from you.
I have reset my tracker database and can see the same SIGSEGV crashes for the "bad" files with the previous stable tracker-miners version, so this is not a new issue. Disregard my -1 karma (though I won't give +1).
Ah, if it's not a regression that sounds like good news and we don't need to hold back the update any more.
It might be good to file an upstream ticket regardless though and see if these can get fixed.
Ok update ran fine. Running tracker3 status seems fine. No errors noted.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been submitted for stable by kalev.
This update has been pushed to stable.