nautilus-scripts-manager crashed with SIGSEGV in IA__gdk_window_enable_synchronized_configure()

[NeilGreenwood]

I started the program from a SSH session where DISPLAY wasn't set, so it's user error. However, it shouldn't dump core in that situation.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus-scripts-manager 1.6-1
ProcVersionSignature: Ubuntu 3.2.0-21.34-generic-pae 3.2.13
Uname: Linux 3.2.0-21-generic-pae i686
ApportVersion: 2.0-0ubuntu4
Architecture: i386
Date: Wed Apr 4 12:47:42 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus-scripts-manager
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/nautilus-scripts-manager list-available
ProcEnviron:
 TERM=screen-bce
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus-scripts-manager
Title: nautilus-scripts-manager crashed with SIGSEGV in gdk_window_enable_synchronized_configure()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip fuse libvirtd lpadmin netdev plugdev sambashare sudo video wireshark

[Pietro Battiston (toobaz)]

This is solved in bugfix version 1.7, which is currently in Debian unstable as 1.7-1, which should reach Debian testing in 9 days.

[Jeremy Bícha (jbicha)]

Please don't set as Fix Released in Ubuntu if the fix isn't actually in Ubuntu yet.

[Jeremy Bícha (jbicha)]

This bug was fixed in the package nautilus-scripts-manager - 1.7-1

---------------
nautilus-scripts-manager (1.7-1) unstable; urgency=low

  * New upstream release
    - Stop crashing when scripts dir contains subdirs (LP: #494704)
    - Check if a display is available before starting the GUI (LP: #973239)
  * Updated Standards-Version

 -- Pietro Battiston <email address hidden> Wed, 04 Jul 2012 20:31:17 +0200