Crash on "Eject" with two tabs open
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 SimpleScreenRec
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_
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_
(nemo:4199): Gtk-CRITICAL **: gtk_tree_
[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-
Linux scott-Asus-
scott@scott-
Ubuntu 17.10
artful
scott@scott-
QLubuntu
scott@scott-
nemo:
Installed: 3.4.7-1ubuntu1
Candidate: 3.4.7-1ubuntu1
Version table:
*** 3.4.7-1ubuntu1 500
500 http://
100 /var/lib/
-------
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nemo 3.4.7-1ubuntu1
ProcVersionSign
Uname: Linux 4.13.0-46-generic x86_64
NonfreeKernelMo
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)
As of Nemo 3.8.5, bug still present.
scott@ASUS- PRIME-B350M- A-CSM:~ $ uname -a B350M-A- CSM 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17) x86_64 GNU/Linux PRIME-B350M- A-CSM:~ $ lsb_release -dsc PRIME-B350M- A-CSM:~ $ echo $DESKTOP_SESSION xsessions/ lxqt
Linux ASUS-PRIME-
scott@ASUS-
Debian GNU/Linux buster/sid
buster
scott@ASUS-
/usr/share/
scott@ASUS- PRIME-B350M- A-CSM:~ $ apt-cache policy nemo /deb.debian. org/debian testing/main amd64 Packages dpkg/status
nemo:
Installed: 3.8.5-1+b1
Candidate: 3.8.5-1+b1
Version table:
*** 3.8.5-1+b1 500
500 https:/
100 /var/lib/