nautilus crashed with SIGSEGV in g_strdup()

Bug #1158735 reported by gogo
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

nautilus crashed

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: nautilus 1:3.6.3-0ubuntu11
ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
Uname: Linux 3.8.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu2
Architecture: amd64
Date: Fri Mar 22 13:06:15 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+285+106'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'170'
InstallationDate: Installed on 2013-03-21 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130321)
MarkForUpload: True
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=hr_HR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f82326b3c51: movdqu (%rdi),%xmm1
 PC (0x7f82326b3c51) ok
 source "(%rdi)" (0x3ff0000000000000) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 g_strdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in g_strdup()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
gogo (trebelnik-stefina) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_strdup (str=0x3ff0000000000000 <Address 0x3ff0000000000000 out of bounds>) at /build/buildd/glib2.0-2.35.8/./glib/gstrfuncs.c:363
 nautilus_icon_info_new_for_icon_info (icon_info=0x29ec650) at nautilus-icon-info.c:155
 nautilus_icon_info_lookup (icon=icon@entry=0x27db830, size=size@entry=24) at nautilus-icon-info.c:413
 nautilus_file_get_icon (file=file@entry=0x25eb960, size=size@entry=24, flags=(NAUTILUS_FILE_ICON_FLAGS_USE_THUMBNAILS | NAUTILUS_FILE_ICON_FLAGS_EMBEDDING_TEXT | NAUTILUS_FILE_ICON_FLAGS_USE_MOUNT_ICON_AS_EMBLEM)) at nautilus-file.c:4387
 nautilus_canvas_view_container_get_icon_images (container=0x7f822400c0d0, data=0x25eb960, size=24, embedded_text=0x7fffaf544068, for_drag_accept=0, need_large_embeddded_text=<optimized out>, embedded_text_needs_loading=0x7fffaf544048, has_window_open=0x7fffaf54404c) at nautilus-canvas-view-container.c:95

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 nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, could be an issue with the new GTK from the ppa, it doesn't seem we are getting reports from raring

Changed in nautilus (Ubuntu):
status: New → Confirmed
tags: added: saucy
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

SegvAnalysis:
 Segfault happened at: 0x7fb4c000c711 <__strlen_sse2_pminub+17>: movdqu (%rdi),%xmm1
 PC (0x7fb4c000c711) ok
 source "(%rdi)" (0x3fe0000000000000) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading unknown VMA
SourcePackage: nautilus

---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

pratically all dbgsym installed
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug didn't get activity/new duplicates for some years and the nautilus code saw quite some changes since which probably deprecated the issue so closing it. If it's still a problem in recent Ubuntu/nautilus version please submit a new report

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