gufw.py crashed with SIGSEGV in _dl_close_worker()

Bug #1559510 reported by lucas serafin avalos
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gui-ufw (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

it wont even start, all system updated untill 19th

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gufw 16.04.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
Uname: Linux 4.4.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Sat Mar 19 14:17:23 2016
ExecutablePath: /usr/share/gufw/gufw/gufw.py
InstallationDate: Installed on 2016-03-09 (10 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: python /usr/share/gufw/gufw/gufw.py lucas
SegvAnalysis:
 Segfault happened at: 0x7fc73d11028d: mov 0x8(%rbx),%rdi
 PC (0x7fc73d11028d) ok
 source "0x8(%rbx)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gui-ufw
StacktraceTop:
 ?? () from /usr/lib/nvidia-358/libGL.so.1
 ?? () from /usr/lib/nvidia-358/libGL.so.1
 ?? () from /usr/lib/nvidia-358/libGL.so.1
 _dl_close_worker (map=map@entry=0x1e32940) at dl-close.c:744
 _dl_close_worker (map=0x1e32940) at dl-close.c:125
Title: gufw.py crashed with SIGSEGV in _dl_close_worker()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
lucas serafin avalos (avalos-lucas-gmail) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00007fc73d11028d in ?? ()
 No symbol table info available.
 #1 0x0000000000000000 in ?? ()
 No symbol table info available.
StacktraceSource:
 #0 0x00007fc73d11028d in ?? ()
 #1 0x0000000000000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
Marc Deslauriers (mdeslaur) wrote : Bug is not a security issue

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
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gui-ufw (Ubuntu):
status: New → Confirmed
Changed in gui-ufw (Ubuntu):
importance: Undecided → Medium
Revision history for this message
costales (costales) wrote :

16.04 is so tested. I think is a bug in one install. I'm sorry.

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