npconfig crashed with SIGSEGV in g_str_equal()

Bug #1220180 reported by b_mfs
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nspluginwrapper (Ubuntu)
New
Undecided
Unassigned

Bug Description

After boot on Ubuntu 13.10

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nspluginwrapper 1.4.4-0ubuntu5
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Sun Sep 1 17:27:52 2013
ExecutablePath: /usr/lib/nspluginwrapper/x86_64/linux/npconfig
InstallationDate: Installed on 2013-05-08 (117 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: nspluginwrapper -a -v -u
SegvAnalysis:
 Segfault happened at: 0x7fbdc15e9026 <__strcmp_ssse3+22>: movlpd (%rdi),%xmm1
 PC (0x7fbdc15e9026) ok
 source "(%rdi)" (0x7fbdc06b310c) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nspluginwrapper
StacktraceTop:
 g_str_equal () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_quark_from_static_string () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 call_init (l=l@entry=0x25192b0, argc=argc@entry=4, argv=argv@entry=0x7fff1ef92798, env=env@entry=0x7fff1ef927c0) at dl-init.c:84
Title: npconfig crashed with SIGSEGV in g_str_equal()
UpgradeStatus: Upgraded to saucy on 2013-07-03 (62 days ago)
UserGroups:

Revision history for this message
b_mfs (b-mfs) 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 #1105417, 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.

information type: 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.