nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id()

Bug #1018697 reported by Doug McMahon
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Probably not unexpected with gtk 3.5.6, if so sorry for report
(wanted to see if the new gtk fixed empty white DnD on files & folders which it did, otherwise this crash happens within a min or so...

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-1.1-generic 3.5.0-rc3
Uname: Linux 3.5.0-1-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.2.5-0ubuntu1
Architecture: amd64
Date: Thu Jun 28 00:09:43 2012
ExecutablePath: /usr/bin/nautilus
ExecutableTimestamp: 1340852081
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120623)
ProcCmdline: nautilus -n
ProcCwd: /home/doug
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f3183e3c580 <gtk_ui_manager_new_merge_id>: mov 0x18(%rdi),%rdx
 PC (0x7f3183e3c580) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 gtk_ui_manager_new_merge_id () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
 (gnome-settings-daemon:1791): color-plugin-WARNING **: failed to get edid: unable to get EDID for output
 (gnome-settings-daemon:1791): color-plugin-WARNING **: unable to get EDID for xrandr-default: unable to get EDID for output
 (gnome-settings-daemon:1791): color-plugin-WARNING **: failed to reset xrandr-default gamma tables: gamma size is zero
 (compiz:1807): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed

Revision history for this message
Doug McMahon (mc3man) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #925503, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-amd64-retrace
Revision history for this message
Doug McMahon (mc3man) wrote :

marking invalid, new nautilus build failed, hadn't noticed

Changed in nautilus (Ubuntu):
status: New → Invalid
Revision history for this message
Antec (info-janmob) wrote :

For me it crashes with 32-bit 12.10 and kernel 3.5.0-2-generic

Revision history for this message
Doug McMahon (mc3man) wrote :

@Antec (info-janmob) or anyone else affected & seeing this
if possible comment in this report which is the active one
Bug 925503

Changed in nautilus (Ubuntu):
status: Invalid → New
Revision history for this message
Doug McMahon (mc3man) wrote :

marking as new & duping as the crashs occur with both the 3.5.2 & 3.5.3 nautlilus versions

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

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

Changed in nautilus (Ubuntu):
status: New → Confirmed
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.