Public bug reported:

This is a update of the bug https://bugs.launchpad.net/ubuntu-
mate/+bug/1630515

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: caja 1.15.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CrashCounter: 1
CurrentDesktop: MATE
Date: Wed Oct  5 13:15:26 2016
ExecutablePath: /usr/bin/caja
InstallationDate: Installed on 2016-10-05 (0 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20161003)
ProcCmdline: caja
SegvAnalysis:
 Segfault happened at: 0x7ffa5bbc5870:  movzbl 0x60(%rdi),%eax
 PC (0x7ffa5bbc5870) ok
 source "0x60(%rdi)" (0x00000060) not located in a known VMA region (needed 
readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: caja
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: caja crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: ubuntu-mate
     Importance: Undecided
         Status: New


** Tags: amd64 apport-crash need-amd64-retrace yakkety

** Information type changed from Private to Public

** Package changed: caja (Ubuntu) => ubuntu-mate

** Summary changed:

- The Mate Panel 1.15.1 unusable
+ The Mate Panel 1.15.1 unusable (caja error)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630517

Title:
  The Mate Panel 1.15.1 unusable (caja error)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1630517/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to