nautilus crashed with SIGSEGV in _IO_vfprintf_internal()

Bug #1082901 reported by Sasa Paporovic on 2012-11-25
54
This bug affects 7 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Medium
Unassigned

Bug Description

Using gksu nautilus fo modifiy the properties of a .zip archive in

/var/www/...

causes the crasher.

Steps to reproduce(stortened:
1.Copy a .zip file in /var/www/...subfolders
2.call a terminal
3.Give the command gksu nautilus
4.See nautilus starting
5.Navigate to the .zip folder
6.right mouse click
7.Choose properties
8.Modify the owner(by accident to sane-)
9.See the crasher

Additional:

The .zip file will be attached. It is a VirtuaMart module for the CMS Joomla.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: nautilus 1:3.6.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.7.0-3.9-generic 3.7.0-rc6
Uname: Linux 3.7.0-3-generic x86_64
ApportVersion: 2.6.2-0ubuntu5
Architecture: amd64
Date: Sun Nov 25 15:52:02 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'795x550+464+105'"
InstallationDate: Installed on 2012-07-22 (125 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120722)
MarkForUpload: True
ProcCmdline: nautilus
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f146f7c8178 <vfprintf+18072>: repnz scas %es:(%rdi),%al
 PC (0x7f146f7c8178) ok
 source "%es:(%rdi)" (0x2078756d00202d00) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 vfprintf () from /lib/x86_64-linux-gnu/libc.so.6
 __vasprintf_chk () from /lib/x86_64-linux-gnu/libc.so.6
 g_vasprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_strdup_vprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_strdup_printf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in vfprintf()
UpgradeStatus: Upgraded to raring on 2012-11-15 (9 days ago)
UserGroups:

Sasa Paporovic (melchiaros) wrote :
information type: Private → Public
Sasa Paporovic (melchiaros) wrote :

StacktraceTop:
 _IO_vfprintf_internal (s=s@entry=0x7fff5b4642c0, format=<optimized out>, format@entry=0x4fc209 "%s\n%s", ap=ap@entry=0x7fff5b464428) at vfprintf.c:1635
 __GI___vasprintf_chk (result_ptr=result_ptr@entry=0x7fff5b464408, flags=flags@entry=1, format=0x4fc209 "%s\n%s", args=0x7fff5b464428) at vasprintf_chk.c:66
 vasprintf (__ap=<optimized out>, __fmt=<optimized out>, __ptr=0x7fff5b464408) at /usr/include/x86_64-linux-gnu/bits/stdio2.h:210
 g_vasprintf (string=string@entry=0x7fff5b464408, format=<optimized out>, args=args@entry=0x7fff5b464428) at /build/buildd/glib2.0-2.34.2/./glib/gprintf.c:314
 g_strdup_vprintf (format=<optimized out>, args=args@entry=0x7fff5b464428) at /build/buildd/glib2.0-2.34.2/./glib/gstrfuncs.c:517

Changed in nautilus (Ubuntu):
importance: Undecided → Medium
summary: - nautilus crashed with SIGSEGV in vfprintf()
+ nautilus crashed with SIGSEGV in _IO_vfprintf_internal()
tags: removed: need-amd64-retrace
Sasa Paporovic (melchiaros) wrote :

Following the headline this here might be a dub of

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/945378

, but the procedure to archive the crsher is different(they only access the trash folder) and the stacktrace looks only simliar in it's steps. I could not say if it is the same. They have also not used gksu as far as I have seen.

Launchpad Janitor (janitor) wrote :

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

Changed in nautilus (Ubuntu):
status: New → Confirmed
vlotho (gdalmas) wrote :

same bug on Ubuntu 13.10 using sudo nautilus for changing owner of a repertorie into www repertorie

Jeff (jdorenbush) wrote :

I get this error on Ubuntu 14.04, right after I log in to my desktop.

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  Edit
Everyone can see this information.

Other bug subscribers