nautilus crashed with SIGSEGV in theme_changed_cb()

Bug #954269 reported by yohgaz
44
This bug affects 9 people
Affects Status Importance Assigned to Milestone
DBus Menu
Confirmed
High
Unassigned
libdbusmenu (Ubuntu)
Triaged
High
Unassigned
nautilus (Ubuntu)
Invalid
High
Unassigned

Bug Description

This bug appears sometimes when I Empty the trash

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.91-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Tue Mar 13 18:42:54 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: org.gnome.nautilus.window-state geometry '800x550+65+24'
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcCmdline: nautilus -n
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f5d7ea93e9c <g_type_check_instance_cast+28>: mov (%rax),%rbp
 PC (0x7f5d7ea93e9c) ok
 source "(%rax)" (0x5000000d8) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libdbusmenu-gtk3.so.4
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
yohgaz (yohanngazziero) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_cast (type_instance=0x1fd7c20, iface_type=24335904) at /build/buildd/glib2.0-2.31.20/./gobject/gtype.c:3999
 theme_changed_cb (theme=0x1608c80, data=0x1fd7c20) at /build/buildd/libdbusmenu-0.5.94/./libdbusmenu-gtk/parser.c:1295
 g_closure_invoke (closure=0x2144000, return_value=0x0, n_param_values=1, param_values=0x24ac460, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.31.20/./gobject/gclosure.c:777
 signal_emit_unlocked_R (node=<optimized out>, detail=0, instance=<optimized out>, emission_return=0x0, instance_and_params=0x24ac460) at /build/buildd/glib2.0-2.31.20/./gobject/gsignal.c:3547
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=0, var_args=<optimized out>) at /build/buildd/glib2.0-2.31.20/./gobject/gsignal.c:3295

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

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

Changed in nautilus (Ubuntu):
status: New → Confirmed
tags: added: bugpattern-needed
visibility: private → public
Changed in nautilus (Ubuntu):
importance: Medium → High
affects: nautilus (Ubuntu) → libdbusmenu (Ubuntu)
affects: libdbusmenu (Ubuntu) → dbusmenu
Changed in nautilus (Ubuntu):
importance: Undecided → High
status: New → Invalid
summary: - nautilus crashed with SIGSEGV in g_type_check_instance_cast()
+ nautilus crashed with SIGSEGV in theme_changed_cb()
Changed in libdbusmenu (Ubuntu):
importance: Undecided → High
status: New → Triaged
Revision history for this message
Christopher Kyle Horton (christhehorton) wrote :

I just got a duplicate of this bug shortly after login.

Revision history for this message
niklas (skudwig) wrote :

Happened to me while deleting a folder.

Revision history for this message
AndresClari (andresclari) wrote :

To me this happened while dragging a file from the desktop to a ssh connected server.

Revision history for this message
Charles Kerr (charlesk) wrote :

I should have noticed this before, but this has an identical backtrace to #953509, so I'm closing this bug as a dupe.

There are a lot of people cc'ed on this ticket -- please note that any further discussion regarding the bug should occur in the other report. Thanks!

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.