Caja repeatedly crashes and restarts after booting Mate Wily
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
One Hundred Papercuts |
Fix Released
|
Critical
|
Unassigned | ||
Ubuntu MATE |
Fix Released
|
Undecided
|
Unassigned | ||
caja (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
Bug Description
After installing Ubuntu Mate Wily 20150825.1 amd64 and booting into the new install Caja tries to open repeatedly filling the window list applet with Caja attempting to open. And Caja will not open in order to view logs or such.
I believe this is reported upstream here:
https:/
In my case though it does not occur only on the first login but also each time you try to boot that install. Oddly this only affects one of two installs on the same identical hardware - the one being affected being an entire disc install and the one not affected being a manual partitioning install.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: caja 1.10.3-1
ProcVersionSign
Uname: Linux 4.1.0-3-generic x86_64
NonfreeKernelMo
ApportVersion: 2.18-0ubuntu7
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Aug 25 22:33:13 2015
InstallationDate: Installed on 2015-08-25 (0 days ago)
InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Alpha amd64 (20150825.1)
SourcePackage: caja
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in caja (Ubuntu): | |
importance: | Undecided → High |
importance: | High → Critical |
Changed in hundredpapercuts: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
Changed in caja (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in hundredpapercuts: | |
status: | Confirmed → Triaged |
summary: |
- Caja repeatedly attempts to automount after booting Mate Wily + Caja repeatedly crashes and restarts after booting Mate Wily |
Changed in caja (Ubuntu): | |
status: | Triaged → Fix Released |
Changed in ubuntu-mate: | |
status: | New → Fix Released |
Changed in hundredpapercuts: | |
status: | Triaged → Fix Released |
Apport had appeared to be filing an automated report but that never actually occurred. You can see that there are files in /var/crash:
lance@lance- AMD-desktop: ~$ ls /var/crash caja.1000. crash _usr_bin_ caja.1000. uploaded caja.1000. upload
_usr_bin_
_usr_bin_
I have no idea what will happen when I try to attach those but here we go.