caja crashed with SIGSEGV in eel_ref_str_ref()

Bug #1569132 reported by Seal20
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
caja (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Crash when trying to acces smb server

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: caja 1.12.7-1
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Apr 12 04:17:53 2016
ExecutablePath: /usr/bin/caja
InstallationDate: Installed on 2016-04-11 (0 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323.1)
ProcCmdline: caja
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x55cbee124723 <eel_ref_str_ref+3>: lock addl $0x1,-0x4(%rdi)
 PC (0x55cbee124723) ok
 source "$0x1" ok
 destination "-0x4(%rdi)" (0xfffffffffffffffc) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: caja
StacktraceTop:
 eel_ref_str_ref ()
 ?? ()
 caja_file_new_from_info ()
 ?? ()
 ?? ()
Title: caja crashed with SIGSEGV in eel_ref_str_ref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Seal20 (swiller) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 eel_ref_str_ref ()
 update_info_internal ()
 caja_file_new_from_info ()
 dequeue_pending_idle_callback ()
 directory_load_done ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in caja (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in caja (Ubuntu):
status: New → Confirmed
information type: Private → Public
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.