crash due to assertion in caja_bookmark_connect_file

Bug #1570363 reported by Marc
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
caja (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I'm just tinkering with an external SMB server. This report is generated automatically, I'm just a user.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: caja 1.12.7-1
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Apr 14 13:34:02 2016
ExecutablePath: /usr/bin/caja
InstallationDate: Installed on 2016-04-13 (0 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323.1)
ProcCmdline: caja
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: caja
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
Title: caja crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo

Revision history for this message
Marc (myrc) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_assertion_message () from /tmp/apport_sandbox_dbrz8_/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /tmp/apport_sandbox_dbrz8_/lib/x86_64-linux-gnu/libglib-2.0.so.0
 caja_bookmark_connect_file ()
 caja_bookmark_get_icon ()
 caja_bookmark_get_pixbuf ()

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
summary: - caja crashed with SIGABRT in raise()
+ caja crashed with SIGABRT in g_assertion_message()
tags: removed: need-amd64-retrace
Revision history for this message
Marc (myrc) wrote : Re: caja crashed with SIGABRT in g_assertion_message()

I think I traced the source of the crash to me pulling the rug from under Caja.

As I'm still learning Samba 4, I changed the name of a connected share while the server was still connected and I think that's what caused the drop out.

Incidentally and FWIW, Ubuntu 16.04 Mate is blowing me away with it's beauty and brilliance. Well done all - I can put this on any pretty much machine, anywhere and be happy that I won't be getting screams of anguish!

information type: Private → Public
Vlad Orlov (monsta)
summary: - caja crashed with SIGABRT in g_assertion_message()
+ crash due to assertion in caja_bookmark_connect_file
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
Norbert (nrbrtx)
Changed in caja (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Norbert (nrbrtx) wrote :

Can you reproduce this bug with newer version of Ubuntu MATE?

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

[Expired for caja (Ubuntu) because there has been no activity for 60 days.]

Changed in caja (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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