Ubuntu
synaptic package

synaptic crashed with SIGSEGV in GI___strtol_l_internal()

Bug #1298774 reported by kuprin2015 on 2014-03-28

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	synaptic (Ubuntu)	New	Medium	Unassigned

Bug Description

synaptic crashed with SIGSEGV in __GI_____strtol_l_internal()

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: synaptic 0.80.4
ProcVersionSignature: Ubuntu 3.13.0-19.40-lowlatency 3.13.6
Uname: Linux 3.13.0-19-lowlatency x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Mar 28 08:10:13 2014
ExecutablePath: /usr/sbin/synaptic
InstallationDate: Installed on 2014-03-27 (0 days ago)
InstallationMedia: Ubuntu-Studio 14.04 "Trusty Tahr" - Alpha amd64 (20140304)
ProcCmdline: synaptic
SegvAnalysis:
Segfault happened at: 0x7fdf8951b7c7 <__GI_____strtol_l_internal+55>: movzbl 0x0(%r13),%r14d
PC (0x7fdf8951b7c7) ok
source "0x0(%r13)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%r14d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: synaptic
StacktraceTop:
__GI_____strtol_l_internal (nptr=0x0, endptr=0x0, base=10, group=<optimized out>, loc=0x7fdf8989e060 <_nl_global_locale>) at ../stdlib/strtol_l.c:298
?? ()
?? ()
?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: synaptic crashed with SIGSEGV in __GI_____strtol_l_internal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

kuprin2015 (kuprin2015) wrote on 2014-03-28:

#1

CurrentDmesg.txt.txt Edit (1.0 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (7.6 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.2 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt.txt Edit (156.9 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt.txt Edit (162.1 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (302 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (53.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (836 bytes, text/plain; charset="utf-8")
Registers.txt Edit (782 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (4.5 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (7.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2014-03-28:

#2

StacktraceTop:
__GI_____strtol_l_internal (nptr=0x0, endptr=0x0, base=10, group=<optimized out>, loc=0x7fdf8989e060 <_nl_global_locale>) at ../stdlib/strtol_l.c:298
atoi (__nptr=<optimized out>) at /usr/include/stdlib.h:280
RunAsSudoUserCommand (cmd=...) at rgutils.cc:147
RGPkgDetailsWindow::cbOpenHomepage (button=<optimized out>, data=<optimized out>) at rgpkgdetails.cc:206
_gtk_marshal_BOOLEAN__VOID (closure=0xd28b80, return_value=0x7fff26ff9970, n_param_values=<optimized out>, param_values=<optimized out>, invocation_hint=<optimized out>, marshal_data=0x0) at /build/buildd/gtk+3.0-3.10.7/./gtk/gtkmarshalers.c:1992

Revision history for this message

Apport retracing service (apport) wrote on 2014-03-28: Stacktrace.txt

#3

Stacktrace.txt Edit (16.2 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2014-03-28: StacktraceSource.txt

#4

StacktraceSource.txt Edit (9.8 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2014-03-28: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (19.9 KiB, text/plain)

Changed in synaptic (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Seth Arnold (seth-arnold) wrote on 2014-03-28: Bug is not a security issue

#6

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type:

Private Security → Public

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.