On Fri, 24 Oct 2025 at 07:19:52 +0100, [email protected] wrote:
I think we need to raise the priority of this bug to Grave to prevent it
migrating to Testing.
The version of nautilus in testing and unstable is the same, so whatever
might have regressed to cause this, either it isn't nautilus (but
instead some dependency) or it's too late to prevent it from migrating.
And, in your previous message to this bug, you reported that
"downgrading to libnautilus-extension4_49.0-1_amd64.deb
nautilus-data_49.0-1_all.deb nautilus_49.0-1_amd64.deb didn't help",
which would suggest that this is not a nautilus change.
We've had no maintainer response
I can't speak for the whole GNOME team, but here is a response: it's
working for me, I don't know why it's behaving differently for you, and
I don't have a solution for you. I know that this is an unsatisfying
response, which is why I didn't say anything previously, and instead
left it to others who might have had a more useful contribution to
respond.
What does it say in the systemd Journal? (Specific messages, not just
paraphrasing)
Is there anything unusual about your system configuration, like perhaps
a networked filesystem like NFS, or an unusual on-disk filesystem used
for $HOME?
You mentioned it crashing. What does the backtrace from those crashes
look like? The easiest way to get a backtrace is usually by installing
systemd-coredump: please see
<https://wiki.debian.org/HowToGetABacktrace> for more details.
It's truly unusable as it is and seems to crash the whole gdm3 session
eventually
If another component is crashing, please collect the log messages and
backtrace from that crash as well. nautilus is just an application, and
in an ideal world it shouldn't be able to crash your session even if it
wanted to.
smcv
