Bug 1265850 - Zenity crashes with coredump when doubleclicking quickly 2 (or more) items in a list
Zenity crashes with coredump when doubleclicking quickly 2 (or more) items in...
Status: NEW
Product: Fedora
Classification: Fedora
Component: zenity (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthias Clasen
Fedora Extras Quality Assurance
: Reopened
Depends On:
  Show dependency treegraph
Reported: 2015-09-23 18:46 EDT by maarten
Modified: 2018-05-03 04:47 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-19 14:00:11 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description maarten 2015-09-23 18:46:25 EDT
Description of problem:
Zenity crashes if you double click two times (or more)
on the same or another item in a list.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
find  /tmp  2>/dev/null |  zenity --list --title "Contents" --text "Files" --column "files"
Quickly double click on 2 items

Actual results: (I clicked on /tmp)

(zenity:10420): Gtk-CRITICAL **: gtk_list_store_get_value: assertion 'column < priv->n_columns' failed

(zenity:10420): GLib-GObject-CRITICAL **: g_value_dup_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed

(zenity:10420): GLib-GObject-CRITICAL **: g_value_unset: assertion 'G_IS_VALUE (value)' failed

Expected results:

Additional info:
This is probably a race condition since the  depends on the speed of double clicking the items and how much items you are able to double click.
The depth of the backtrace varies between 29 and 64 levels.
Comment 1 Fedora End Of Life 2016-07-19 14:00:11 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 2 maarten 2016-07-27 09:23:57 EDT
Still happens on Fedora 24


Steps to Reproduce:
find  /usr/bin  2>/dev/null |  zenity --list --title "Contents" --text "Files" --column "files"
Quickly double click on 2 items

Segmentation fault occurs with a high probability.
Comment 3 maarten 2017-07-12 07:49:10 EDT
Still happens on Fedora 26

zenity.x86_64                           3.24.0-1.fc26           @anaconda
Comment 4 Fedora End Of Life 2018-05-03 04:47:33 EDT
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Note You need to log in before you can comment on or make changes to this bug.