Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#19800 - [geany] 0.19-1 doesn't show certain windows/dialogs
Attached to Project:
Community Packages
Opened by Olivier (litemotiv) - Tuesday, 15 June 2010, 10:03 GMT
Last edited by Angel Velasquez (angvp) - Monday, 05 July 2010, 21:49 GMT
Opened by Olivier (litemotiv) - Tuesday, 15 June 2010, 10:03 GMT
Last edited by Angel Velasquez (angvp) - Monday, 05 July 2010, 21:49 GMT
|
DetailsDescription:
The latest Geany version doesn't show certain popups, for instance the search dialog. Opening it seems to show a brief flash on screen, but doesn't open the dialog itself. I'm not sure if this is a Geany or GTK bug, but downgrading to an older Geany version solves this. Additional info: Not working: 0.19-1 Working: 0.18.1-1 Tested with gtk2 2.20.1-2 on the i3 window manager. Steps to reproduce: Upgrade to 0.19-1, start Geany, open search dialog (ctrl-f) |
This task depends upon
Closed by Angel Velasquez (angvp)
Monday, 05 July 2010, 21:49 GMT
Reason for closing: Not a bug
Additional comments about closing: Re-open if it's necessary and you figured out how to reproduce the bug correctly
Monday, 05 July 2010, 21:49 GMT
Reason for closing: Not a bug
Additional comments about closing: Re-open if it's necessary and you figured out how to reproduce the bug correctly
I also switched to i3 to test it out and the find dialog worked.
I had old configuration of geany on .config folder, and it worked fine :-/ weird, is there any other person with this problem?
It's most likely a config, template or colorscheme problem, but thrashing the old config and starting from scratch isn't really problematic.
I will let the bug open for a couple of days to see if there is another person with the same issue, else I will close it.
i'm on 64bit btw, running the lastest stable packages.