{"action":"created","issue":{"url":"https://api.github.com/repos/zdia/gorilla/issues/141","labels_url":"https://api.github.com/repos/zdia/gorilla/issues/141/labels{/name}","comments_url":"https://api.github.com/repos/zdia/gorilla/issues/141/comments","events_url":"https://api.github.com/repos/zdia/gorilla/issues/141/events","html_url":"https://github.com/zdia/gorilla/issues/141","id":81434197,"number":141,"title":"Database window not mapped after reopen","user":{"login":"pniemann","id":12626681,"avatar_url":"https://avatars.githubusercontent.com/u/12626681?v=3","gravatar_id":"","url":"https://api.github.com/users/pniemann","html_url":"https://github.com/pniemann","followers_url":"https://api.github.com/users/pniemann/followers","following_url":"https://api.github.com/users/pniemann/following{/other_user}","gists_url":"https://api.github.com/users/pniemann/gists{/gist_id}","starred_url":"https://api.github.com/users/pniemann/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pniemann/subscriptions","organizations_url":"https://api.github.com/users/pniemann/orgs","repos_url":"https://api.github.com/users/pniemann/repos","events_url":"https://api.github.com/users/pniemann/events{/privacy}","received_events_url":"https://api.github.com/users/pniemann/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-05-27T12:56:49Z","updated_at":"2015-05-29T11:55:38Z","closed_at":null,"body":"When reopening the database (that is, from the lockedDialog Dialog) the database window is not mapped at all on my desktop.\r\n\r\nI have Debian GNU/Linux with X11 and fvwm2 and two monitors using xinerama.\r\n\r\nPassword Gorilla is at version 1.5.3.7-1 as packaged with debian jessie.\r\n\r\nWhen I open a new instance of password gorilla from the command line and enter the database password, I get the database window mapped as expected (I currently use manual placement style in fvwm). After staying idle for some time the database gets auto-locked and the lockedDialog window gets mapped as expected (again manual placement).\r\n\r\nBut the next time I enter the password the database window is not mapped at all. It doesn't appear in the window list of fvwm, it is not visible anywhere on my desktop, just seems to crash. But the process is not crashed and after some time the database gets auto-locked. At that time the lockedDialog is mapped again as expected.\r\n\r\nI have tried some tweaking with fvwm styles but to no success yet.\r\n\r\nI didn't have this kind of problem with debian wheezy. Downgrading to that version (1.5.3.4-1 with bwidget instead of tklib) resolves the issue.\r\n\r\nKind regards,\r\nPhilipp"},"comment":{"url":"https://api.github.com/repos/zdia/gorilla/issues/comments/106782470","html_url":"https://github.com/zdia/gorilla/issues/141#issuecomment-106782470","issue_url":"https://api.github.com/repos/zdia/gorilla/issues/141","id":106782470,"user":{"login":"rich123","id":305956,"avatar_url":"https://avatars.githubusercontent.com/u/305956?v=3","gravatar_id":"","url":"https://api.github.com/users/rich123","html_url":"https://github.com/rich123","followers_url":"https://api.github.com/users/rich123/followers","following_url":"https://api.github.com/users/rich123/following{/other_user}","gists_url":"https://api.github.com/users/rich123/gists{/gist_id}","starred_url":"https://api.github.com/users/rich123/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rich123/subscriptions","organizations_url":"https://api.github.com/users/rich123/orgs","repos_url":"https://api.github.com/users/rich123/repos","events_url":"https://api.github.com/users/rich123/events{/privacy}","received_events_url":"https://api.github.com/users/rich123/received_events","type":"User","site_admin":false},"created_at":"2015-05-29T11:55:38Z","updated_at":"2015-05-29T11:55:38Z","body":"Two additional items to try.\r\n\r\n1) What would be the set of FVWM stylings your .fvwm2rc applies to Gorilla by default.  I can try applying those locally myself to see if one or the combination triggers the bug locally for me (which if they do will help tremendously in fixing the issue);\r\n\r\n2) Since you are running Debian, the .deb install package should have installed the Gorilla source code.  Would you be willing to try making a quick edit to your gorilla.tcl file to output some debugging information, which might at the very least indicate what is happening when it appears to disappear from the screen?\r\n\r\nIf yes, then find the location where your gorilla.tcl is installed and do the following (the edit steps you'll need to do as a user with write permissions, this will usually be 'root'):\r\n\r\n1) Make a backup copy of gorilla.tcl;\r\n\r\n2) Open gorilla.tcl in a text editor, and search for a line that begins: \"proc gorilla::LockDirtyMessage\";\r\n\r\n3) About 30 lines up lower line numbers) you should find another line that reads: \"# restore all closed window statuses and positions\"\r\n\r\n4) The next line after #3 above should begin \"foreach tl\", and the next line after that should begin \"wm state\".  Insert a new blank line between the \"foreach\" and \"wm state\" lines and add this text to the new blank line:\r\n\r\n    puts stderr \"$tl $withdrawn($tl)\"\r\n\r\n5) Now, open a terminal (xterm/rxvt/etc.) and from the terminal window, launch gorilla.tcl (you should be able to type just \"gorilla.tcl\" (without quotes) to launch it, if not you might have to type the full path to the executable, i.e. /usr/bin/gorilla.tcl)\r\n\r\n6) Cause the issue to happen, after which you should see some extra text output to the terminal window by gorilla.tcl.  Copy and pasted that extra output here into another reply.\r\n\r\n7) Undo your changes (if you wish to undo them at this point) by replacing the edited gorilla.tcl with the backup you made in step #1 above.\r\n"}}