gnome-screenshot crashed with SIGSEGV if I write a full path on filename

Bug #984524 reported by Daniel Cordeiro on 2012-04-18
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gnome-screenshot (Ubuntu)

Bug Description

I can reproduce this bug everytime:

1. open gnome-screenshot
2. choose a filename like '/tmp/screen.png' and don't change the default target folder
3. click on the save button.

Gnome screenshot dies with SIGSEGV.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-screenshot 3.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu4
Architecture: amd64
Date: Wed Apr 18 00:00:37 2012
Disassembly: => 0x0: Não é possível acessar a memória no endereço 0x0
ExecutablePath: /usr/bin/gnome-screenshot
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcCmdline: gnome-screenshot
 Segfault happened at: 0x0: Não é possível acessar a memória no endereço 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
 source "0x0" (0x00000000) not located in a known VMA region (needed readable region)!
 Stack memory exhausted (SP below stack segment)
 executing NULL VMA
 reading NULL VMA
Signal: 11
SourcePackage: gnome-screenshot
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
 ?? () from /lib/x86_64-linux-gnu/
Title: gnome-screenshot crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Daniel Cordeiro (dcordeiro) wrote :
visibility: private → public

 ?? ()
 create_async_thread (res=0x145a750, object=0x150ef00, cancellable=0x0) at /build/buildd/glib2.0-2.32.1/./gio/gfile.c:5169
 run_in_thread (job=<optimized out>, c=0x0, _data=0x14b2c90) at /build/buildd/glib2.0-2.32.1/./gio/gsimpleasyncresult.c:861
 io_job_thread (data=0x15095b0, user_data=<optimized out>) at /build/buildd/glib2.0-2.32.1/./gio/gioscheduler.c:177
 g_thread_pool_thread_proxy (data=<optimized out>) at /build/buildd/glib2.0-2.32.1/./glib/gthreadpool.c:309

Changed in gnome-screenshot (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-screenshot (Ubuntu):
status: New → Confirmed
Rolf Leggewie (r0lf) wrote :

upstream made some changes to detect this and AFAICS trusty is no longer affected. Can you confirm?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers