nautilus crash when creating symlink

[Christian Rauch]

nautilus crashes when I try to create a symbolic link via drag and drop:

1. open an arbitrary folder in nautlus
2. hold 'Alt' and drag and drop a file
3. a context dialog will open with options to move, copy or link the file
4. chose any option

Choosing any option (even abort) or just changing to another window will crash nautilus with:

gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed

Since the "nautilus-dbgsym" package hasn't been updated, it cannot be installed and I cannot collect a meaningful backtrace.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 10 16:01:41 2021
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

[Sebastien Bacher (seb128)]

Thank you for your bug report. What do you mean by 'Since the "nautilus-dbgsym" package hasn't been updated, it cannot be installed and I cannot collect a meaningful backtrace.' ? Do you have the ddebs source enabled for focal-updates?

[Christian Rauch (christianrauch)]

I have the ddebs sources added:
deb http://ddebs.ubuntu.com focal main restricted universe multiverse
deb http://ddebs.ubuntu.com focal-updates main restricted universe multiverse
deb http://ddebs.ubuntu.com focal-proposed main restricted universe multiverse

But the dbgsym version does not match the package version:

$ apt list nautilus -a
nautilus/focal-updates,now 1:3.36.3-0ubuntu1 amd64 [installiert]
nautilus/focal 1:3.36.1.1-1ubuntu2 amd64

$ apt list nautilus-dbgsym -a
nautilus-dbgsym/focal 1:3.36.1.1-1ubuntu2 amd64

After nautilus has been updated to version "1:3.36.3-0ubuntu1" the -dbgsym package stayed at version "1:3.36.1.1-1ubuntu2". So I cannot install "nautilus-dbgsym" and run gdb with the debug symbols to check where it crashes.

Anyway, this issue is pretty easy reproducible on my side and occurs every time.

[Sebastien Bacher (seb128)]

Weird, well you can get the dbgsym packages from launchpad on https://launchpad.net/ubuntu/+source/nautilus/1:3.36.3-0ubuntu1/+build/19437394 and dpkg -i install those. Could you do that and get a stacktrace? (or submit the report generated in /var/crash)

[Christian Rauch (christianrauch)]

After installing that dbgsym package, I still do not get a backtrace. It just exits with "[Inferior 1 (process 116937) exited with code 01]" so maybe it does not crash but the failed assertion makes it just quit? Also, there is nothing in "/var/crash" which is another indicator that the process just exits, but does not crash.

I found the upstream issue at https://gitlab.gnome.org/GNOME/nautilus/-/issues/1303. There it is reported that this is a Wayland-only issue and I can indeed verify that this does not happen on X11.

[Sebastien Bacher (seb128)]

Thanks

[Christian Rauch (christianrauch)]

A bit unrelated, but the reason that there is no "nautilus-dbgsym" for the updated nautilus package (version 1:3.36.3-0ubuntu from "focal-updates") is that the dbgsym index for the released version ("focal") at:

http://ddebs.ubuntu.com/dists/focal/main/binary-amd64/Packages

shows the "nautilus-dbgsym" at version "1:3.36.1.1-1ubuntu2", but the updated index ("focal-updates") at:

http://ddebs.ubuntu.com/dists/focal-updates/main/binary-amd64/Packages

does not contain any "nautilus-dbgsym".

I am mentioning this because I have a couple of other packages that have been updated but now do not have a corresponding "-dbgsym" package.

@seb128 Do you have an idea where I can report this issue?

[Sebastien Bacher (seb128)]

sorry I forgot to reply to the previous comment, indeed that was an issue with the service, it has been resolved now, see bug #1921940 for details

[Sebastien Bacher (seb128)]

The upstream bug was closed with that comment

> Checked in Ubuntu 22.04, it seems that it was fixed in v 42.2.

doing the same here now