[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#56487: xgselect race condition leading to abort when USE_GTK not def
|
From: |
Tom Gillespie |
|
Subject: |
bug#56487: xgselect race condition leading to abort when USE_GTK not defined |
|
Date: |
Mon, 11 Jul 2022 19:20:02 -0700 |
> No, because we don't want the different GLib event dispatch behavior
> outside of GTK with native input enabled.
Ok, got it. I'll see if I can figure out an alternate solution with that
constraint in mind.
Should I split out the release_select_lock change into a separate
patch so that we can get that merged independent of a fix for the
abort behavior?
- bug#56487: xgselect race condition leading to abort when USE_GTK not defined, Tom Gillespie, 2022/07/10
- bug#56487: xgselect race condition leading to abort when USE_GTK not defined, Po Lu, 2022/07/10
- bug#56487: xgselect race condition leading to abort when USE_GTK not defined, Tom Gillespie, 2022/07/10
- bug#56487: xgselect race condition leading to abort when USE_GTK not defined, Po Lu, 2022/07/10
- bug#56487: xgselect race condition leading to abort when USE_GTK not defined, Tom Gillespie, 2022/07/10
- bug#56487: xgselect race condition leading to abort when USE_GTK not defined, Po Lu, 2022/07/11
- bug#56487: xgselect race condition leading to abort when USE_GTK not defined, Tom Gillespie, 2022/07/11
- bug#56487: xgselect race condition leading to abort when USE_GTK not defined, Po Lu, 2022/07/11
- bug#56487: xgselect race condition leading to abort when USE_GTK not defined,
Tom Gillespie <=
- bug#56487: xgselect race condition leading to abort when USE_GTK not defined, Eli Zaretskii, 2022/07/12
- bug#56487: xgselect race condition leading to abort when USE_GTK not defined, Tom Gillespie, 2022/07/15