Bug 1265850 - Zenity crashes with coredump when doubleclicking quickly 2 (or more) items in a list
Summary: Zenity crashes with coredump when doubleclicking quickly 2 (or more) items in...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: zenity
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-23 22:46 UTC by maarten
Modified: 2022-07-11 18:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-11 18:49:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description maarten 2015-09-23 22:46:25 UTC
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):
3.16.3-1.fc22

How reproducible:
99.9%

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

Actual results: (I clicked on /tmp)
/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
(null)

Expected results:
/tmp

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 18:00:11 UTC
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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 2 maarten 2016-07-27 13:23:57 UTC
Still happens on Fedora 24

zenity-3.20.0-1.fc24.x86_64

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

Segmentation fault occurs with a high probability.

Comment 3 maarten 2017-07-12 11:49:10 UTC
Still happens on Fedora 26

zenity.x86_64                           3.24.0-1.fc26           @anaconda

Comment 4 Fedora End Of Life 2018-05-03 08:47:33 UTC
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.

Comment 5 Fedora End Of Life 2018-05-29 11:57:49 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 6 maarten 2018-06-20 05:38:20 UTC
Still occurs on Fedora 28

(null)/usr/bin/vboxcnvt(null)/usr/bin/vboxcnvt(null)/usr/bin/vboxcnvt(null)/usr/bin/vboxcnvt(null)
malloc(): smallbin double linked list corrupted
Aborted (core dumped)

Comment 7 Ben Cotton 2018-11-26 15:52:51 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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.