npconfig crashed with SIGSEGV in g_str_equal()

[Jiremek]

Crach occure when reconfig screen from dual-sreen to one screen

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nspluginwrapper 1.4.4-0ubuntu5
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
Uname: Linux 3.11.0-8-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
Date: Mon Sep 23 01:36:08 2013
ExecutablePath: /usr/lib/nspluginwrapper/x86_64/linux/npconfig
InstallationDate: Installed on 2013-09-14 (8 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130914)
MarkForUpload: True
ProcCmdline: nspluginwrapper -a -v -u
ProcEnviron:
 LANGUAGE=fr_FR
 TERM=xterm
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f24e1baf0a6 <__strcmp_sse2+22>: movlpd (%rdi),%xmm1
 PC (0x7f24e1baf0a6) ok
 source "(%rdi)" (0x7f24e0d3419c) 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=0x1a71290, argc=argc@entry=4, argv=argv@entry=0x7fff00178e78, env=env@entry=0x7fff00178ea0) at dl-init.c:84
Title: npconfig crashed with SIGSEGV in g_str_equal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

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.