gksu crashed with SIGSEGV in fputs()

Bug #901109 reported by piotrekw1
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gksu (Ubuntu)
New
Undecided
Unassigned

Bug Description

I do not know what is causing

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gksu 2.0.2-6ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-3.8-generic 3.2.0-rc4
Uname: Linux 3.2.0-3-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Wed Dec 7 09:02:44 2011
ExecutablePath: /usr/bin/gksu
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/bin/gksu --message <span\ weight="bold"\ size="larger">Proszę\ wprowadzić\ hasło,\ aby\ uzyskać\ dostęp\ do\ raportów\ o\ problemach\ w\ systemie</span> /usr/share/apport/apport-gtk
ProcEnviron:
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f52228966a1: movdqu (%rdi),%xmm1
 PC (0x7f52228966a1) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gksu
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 fputs () from /lib/x86_64-linux-gnu/libc.so.6
 gksu_sudo_fuller () from /usr/lib/libgksu2.so.0
 ?? ()
 __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
Title: gksu crashed with SIGSEGV in fputs()
UpgradeStatus: Upgraded to precise on 2011-12-06 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
piotrekw1 (piotrekw1) 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 #901531, 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
visibility: private → public
tags: removed: need-amd64-retrace
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.