There is a fix upstream:
http://git.gnome.org/browse/zenity/commit/?id=4a30be17b3adfd7b8383f5c23fae71e31933326b

** Visibility changed to: Public

** Changed in: zenity (Ubuntu)
   Importance: Medium => High

** Changed in: zenity (Ubuntu)
       Status: Confirmed => Triaged

** Also affects: zenity (Ubuntu Precise)
   Importance: Undecided
       Status: New

** Changed in: zenity (Ubuntu Precise)
   Importance: Undecided => High

** Changed in: zenity (Ubuntu Precise)
       Status: New => Triaged

** Changed in: zenity (Ubuntu)
       Status: Triaged => Fix Committed

** Changed in: zenity (Ubuntu Precise)
       Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zenity in Ubuntu.
https://bugs.launchpad.net/bugs/968534

Title:
  zenity crashed with SIGSEGV in zenity_tree_dialog_response()

Status in “zenity” package in Ubuntu:
  Fix Committed
Status in “zenity” source package in Precise:
  In Progress

Bug description:
  I am using UCK and crashed...

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: zenity 3.4.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Mar 29 14:55:24 2012
  ExecutablePath: /usr/bin/zenity
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: zenity
  Title: zenity crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/968534/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to