Crash on "Eject" with two tabs open

Bug #1804978 reported by Scott Cowles Jacobs
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nemo (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I can fairly reliably cause Nemo to crash.

I have to say "fairly", as after multiple crashes, nemo now does something different.
(More on that later)

To induce the crash, I would mount a USB stick with files on it, and open it in a second tab.
I then clicked on "Eject", and Nemo would be gone (I did receive the "You can now remove xxx safely" message).

I will attempt to attach a SimpleScreenRecorder file showing one such cycle.

Looking at the terminal output, when launched, there are 2/3 warnings, but no problem.
When mounted, no more messages are displayed, but after Nemo's window disappeared,
there are 7 identical gtk-CRITICAL messages (then after about 1/2 a minute, the terminal prompt comes back):

" (nemo: 3854): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed"

My original attempt to reproduce merely had me click on the "Eject" button without attempting to see the contents by clicking on the drive.
When this did not elicit the crash, I then replaced the drive and then clicked on the drive,
and then "Eject". Also, no crash.
When, however, I bring up the contents in a second tab, and THEN "Eject", then it crashes.

Except that now, it doesn't crash, but there are a couple of OTHER gtk-CRITICAL messages:
(nemo:4199): Gtk-CRITICAL **: gtk_tree_model_filter_convert_iter_to_child_iter: assertion 'filter_iter->stamp == filter->priv->stamp' failed

(nemo:4199): Gtk-CRITICAL **: gtk_tree_store_set_valist: assertion 'VALID_ITER (iter, tree_store)' failed

[Yes, I KNOW that this is not the latest Lubuntu (and possibly Nemo)
I am forced to use 17.10, as that is the latest version that can successfully
install the nvidia-304 driver, which has been abandoned by nvidia, and which I need,
as nouveau video-crashes (diagonal garbage) and I must hard-reboot, way more often than
is convenient.
I am probably going to get a new computer soon (old one is 7+ years old)
If at some point I get to test this out with updated OS/app, I'll update you as well...]

------------------------------------------------
scott@scott-Asus-M2N68-AM-PLUS:~$ uname -a
Linux scott-Asus-M2N68-AM-PLUS 4.13.0-46-generic #51-Ubuntu SMP Tue Jun 12 12:36:29 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
scott@scott-Asus-M2N68-AM-PLUS:~$ lsb_release -dsc
Ubuntu 17.10
artful
scott@scott-Asus-M2N68-AM-PLUS:~$ echo $DESKTOP_SESSION
QLubuntu
scott@scott-Asus-M2N68-AM-PLUS:~$ apt-cache policy nemo
nemo:
  Installed: 3.4.7-1ubuntu1
  Candidate: 3.4.7-1ubuntu1
  Version table:
 *** 3.4.7-1ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
        100 /var/lib/dpkg/status

------------------------------------------------

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nemo 3.4.7-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16
Uname: Linux 4.13.0-46-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.7-0ubuntu3.9
Architecture: amd64
CurrentDesktop: LXQt
Date: Sat Nov 24 20:29:31 2018
InstallationDate: Installed on 2017-11-06 (384 days ago)
InstallationMedia: Lubuntu-Next 17.10 "Artful Aardvark" - Beta amd64 (20171014)
SourcePackage: nemo
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Scott Cowles Jacobs (scott092707) wrote :
Revision history for this message
Scott Cowles Jacobs (scott092707) wrote :

As of Nemo 3.8.5, bug still present.

scott@ASUS-PRIME-B350M-A-CSM:~$ uname -a
Linux ASUS-PRIME-B350M-A-CSM 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17) x86_64 GNU/Linux
scott@ASUS-PRIME-B350M-A-CSM:~$ lsb_release -dsc
Debian GNU/Linux buster/sid
buster
scott@ASUS-PRIME-B350M-A-CSM:~$ echo $DESKTOP_SESSION
/usr/share/xsessions/lxqt

scott@ASUS-PRIME-B350M-A-CSM:~$ apt-cache policy nemo
nemo:
  Installed: 3.8.5-1+b1
  Candidate: 3.8.5-1+b1
  Version table:
 *** 3.8.5-1+b1 500
        500 https://deb.debian.org/debian testing/main amd64 Packages
        100 /var/lib/dpkg/status

Revision history for this message
José Luis Vitzcouz (cell32) wrote :

Nemo was Fixed in version 4.0.2

https://github.com/linuxmint/nemo/issues/1899

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nemo (Ubuntu):
status: New → Confirmed
Revision history for this message
Scott Cowles Jacobs (scott092707) wrote :

As of version 4.0.6-1 from https://deb.debian.org/debian testing/main amd64 Packages
bug is still present.
(bring` up external drive in second tab, eject: nemo window disappears)

scott@ASUS-PRIME-B350M-A-CSM:~$ uname -a
Linux ASUS-PRIME-B350M-A-CSM 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17) x86_64 GNU/Linux
scott@ASUS-PRIME-B350M-A-CSM: $ lsb_release -dsc
Debian GNU/Linux bullseye/sid
bullseye
scott@ASUS-PRIME-B350M-A-CSM: $ echo $DESKTOP_SESSION
/usr/share/xsessions/lxqt

Revision history for this message
Scott Cowles Jacobs (scott092707) wrote :
Download full text (14.9 KiB)

As of version 4.2.3-2 from https://deb.debian.org/debian testing/main amd64 Packages
bug is still present.
(bring` up external drive in second tab, eject: nemo window disappears)

scott@ASUS-PRIME-B350M-A-CSM:~$ uname -a
Linux ASUS-PRIME-B350M-A-CSM 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17) x86_64 GNU/Linux
scott@ASUS-PRIME-B350M-A-CSM:~$ lsb_release -dsc
Debian GNU/Linux bullseye/sid
bullseye
scott@ASUS-PRIME-B350M-A-CSM:~$ echo $DESKTOP_SESSION
/usr/share/xsessions/lxqt

---------------------------------------------------------------------------------------
gdb run follows (no package nemo-dbgsym seems to exist for debian (at least))
---------------------------------------------------------------------------------------
scott@ASUS-PRIME-B350M-A-CSM:~$ gdb nemo
GNU gdb (Debian 8.3.1-1) 8.3.1
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from nemo...
(No debugging symbols found in nemo)
(gdb) run
Starting program: /usr/bin/nemo
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff2b2d700 (LWP 2008)]
[New Thread 0x7ffff232c700 (LWP 2009)]
[New Thread 0x7ffff1a51700 (LWP 2010)]
[New Thread 0x7ffff1250700 (LWP 2011)]

** (nemo:2004): WARNING **: 20:42:13.320: Current gtk theme is not known to have nemo support (Adwaita) - checking...

** (nemo:2004): WARNING **: 20:42:13.392: The theme appears to have no nemo support. Adding some...
[New Thread 0x7fffe3fff700 (LWP 2013)]
[New Thread 0x7fffe37fe700 (LWP 2015)]
[New Thread 0x7fffe2ffd700 (LWP 2016)]
[New Thread 0x7fffe27fc700 (LWP 2017)]
[New Thread 0x7fffe1ffb700 (LWP 2018)]
[New Thread 0x7fffe17fa700 (LWP 2019)]
[Thread 0x7fffe37fe700 (LWP 2015) exited]
[Thread 0x7fffe1ffb700 (LWP 2018) exited]
[Thread 0x7fffe27fc700 (LWP 2017) exited]
[Thread 0x7fffe3fff700 (LWP 2013) exited]
[Thread 0x7fffe2ffd700 (LWP 2016) exited]
[Thread 0x7ffff1250700 (LWP 2011) exited] ...

Revision history for this message
Scott Cowles Jacobs (scott092707) wrote :
Download full text (11.3 KiB)

Debian apparently has a separate repository for debug packages. I found and installed nemo-dbgsym and nemo-fileroller-dbgsym, and re-ran gdb.
(terminal output for gdb without dbgsym is shown in comment #6, above)

No crash.

Ran without gdb.

Crash.

I will attach the no-crash terminal output for gdb nemo.

I find it significant that both times it crashed, whether with gdb without dbgsym, or without gdb, the same seven lines were printed:

with gdb (no dbgsym):
(nemo:2004): Gtk-CRITICAL **: 20:42:29.116: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed

(nemo:2004): Gtk-CRITICAL **: 20:42:29.117: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed

(nemo:2004): Gtk-CRITICAL **: 20:42:29.117: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed

(nemo:2004): Gtk-CRITICAL **: 20:42:29.118: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed ...

Revision history for this message
Scott Cowles Jacobs (scott092707) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.