LaunchBox moves out of the screen in 'persistent' geometry

[mtaki14]

Since the last couple of releases after a bit of usage something happens and I cannot bring up KP neither using the shortcut or by clicking on its system tray icon. The only way to do so is by closing and running KP again.

The log doesn't seem to be showing any useful info so a debug version might be needed to track this bug down.

2016-09-06 08:09:01.972 [i] Keypirinha 2.9.3 (697043d) for x64
2016-09-06 08:09:01.979 [i] Portable mode.
2016-09-06 08:09:01.985 [i] System: WinNT-x64 10.0.10586-ws-0x0100
2016-09-06 08:09:01.996 [i] Official packages: C:\Users\ma_t1\Keypirinha\default\Packages
2016-09-06 08:09:02.006 [i] Profile dir: C:\Users\ma_t1\Keypirinha\portable\Profile
2016-09-06 08:09:02.012 [i] Local dir: C:\Users\ma_t1\Keypirinha\portable\Local
2016-09-06 08:09:02.025 [i] Keyboard layout: 00000809
2016-09-06 08:09:02.049 [i] Monitor #1: Name[\\.\DISPLAY1] Rect[0, 0, 1366, 768] DpiScale[1.00] PRIMARY
2016-09-06 08:09:02.161 [i] Python 3.5.2 (default, Jul  1 2016, 10:33:08) [MSC v.1800 64 bit (AMD64)]
2016-09-06 08:09:03.181 [i] Loaded 439 items from history file.
2016-09-06 08:09:03.224 [i] Init done in 1.4033s, including 1.0288s (73%) for the Python interpreter.
2016-09-06 08:09:03.235 [i] Plugin loaded: Internal.About
2016-09-06 08:09:03.375 [i] Plugin loaded: Apps.Apps (instance #1)
2016-09-06 08:09:03.461 [i] Plugin loaded: Bookmarks.Bookmarks (instance #1)
2016-09-06 08:09:03.496 [i] Plugin loaded: Calc.Calc (instance #1)
2016-09-06 08:09:03.500 [i] Plugin loaded: ControlPanel.ControlPanel (instance #1)
2016-09-06 08:09:03.523 [i] Plugin loaded: Everything.Everything (instance #1)
2016-09-06 08:09:03.532 [i] Plugin loaded: FileBrowser.FileBrowser (instance #1)
2016-09-06 08:09:03.614 [i] Plugin loaded: FileZilla.FileZilla (instance #1)
2016-09-06 08:09:03.620 [i] Plugin loaded: PuTTY.PuTTY (instance #1)
2016-09-06 08:09:03.628 [i] Plugin loaded: TaskSwitcher.TaskSwitcher (instance #1)
2016-09-06 08:09:03.634 [i] Plugin loaded: URL.URL (instance #1)
2016-09-06 08:09:03.642 [i] Plugin loaded: WebSearch.WebSearch (instance #1)
2016-09-06 08:09:03.657 [i] Plugin loaded: Winamp.Winamp (instance #1)
2016-09-06 08:09:03.664 [i] Plugin loaded: WinSCP.WinSCP (instance #1)
2016-09-06 08:09:37.284 [i] Apps.Apps: Cataloged 1256 items in 33.3 seconds
2016-09-06 08:10:00.134 [i] Bookmarks.Bookmarks: Referenced 3 bookmarks

[polyvertex]

Could you share your Keypirinha.ini file so I can try to replicate the issue?
You may remove the [external] section before sharing if you wish (for privacy concern), as it is unlikely to be related.

[polyvertex]

Could you share your Keypirinha.ini file so I can try to replicate the issue?
You may remove the [external] section before sharing if you wish (for privacy concern), as it is unlikely to be related.

[mtaki14]

Keypirinha.zip

[mtaki14]

Keypirinha.zip

[polyvertex]

If your issue happens to come from a bug in KP, the only way for it to be solved is me being able to reproduce it, which is something I haven't managed to do so far using your configuration.

1. The log states that only one screen is detected by KP at startup. Is that correct? IIRC you were using several monitors.
2. Would you mind enabling the show_on_taskbar setting and check if, when the issue occurs, the taskbar button of the LaunchBox gets shown. At least that would indicate the LaunchBox gets fired up as expected but its position is outside your screen which is the reason why you don't see it. Another way to perform this test is to:
   • Right-click on the systray icon to display KP's main menu
   • Click on the Open LaunchBox item (this must be done that way since the hotkey toggles the LaunchBox as well as a single left-click on it)
   • Blindly type a known search (typically an associated word)
   • Press Enter and see if your item is executed as expected.

[polyvertex]

If your issue happens to come from a bug in KP, the only way for it to be solved is me being able to reproduce it, which is something I haven't managed to do so far using your configuration.

1. The log states that only one screen is detected by KP at startup. Is that correct? IIRC you were using several monitors.
2. Would you mind enabling the show_on_taskbar setting and check if, when the issue occurs, the taskbar button of the LaunchBox gets shown. At least that would indicate the LaunchBox gets fired up as expected but its position is outside your screen which is the reason why you don't see it. Another way to perform this test is to:
   • Right-click on the systray icon to display KP's main menu
   • Click on the Open LaunchBox item (this must be done that way since the hotkey toggles the LaunchBox as well as a single left-click on it)
   • Blindly type a known search (typically an associated word)
   • Press Enter and see if your item is executed as expected.

[mtaki14]

1. No, it's showing correctly at the moment. I have only 1 monitor.
2. I have tried and brought up KP successfully before. But as soon as I try to type something in the launchbox it immediately disappears.

I am currently using an older version but I will make separate a installation of the new one to test again further.

[mtaki14]

1. No, it's showing correctly at the moment. I have only 1 monitor.
2. I have tried and brought up KP successfully before. But as soon as I try to type something in the launchbox it immediately disappears.

I am currently using an older version but I will make separate a installation of the new one to test again further.

[polyvertex]

1. Hopefully you haven't deleted the old install with the 2.9.3 version because the Keypirinha.state file would be of interest as well if you still have it.
2. Can you confirm KP doesn't crash and that it's just that, when the LaunchBox gets shown and you start typing your search, it vanishes?

[polyvertex]

1. Hopefully you haven't deleted the old install with the 2.9.3 version because the Keypirinha.state file would be of interest as well if you still have it.
2. Can you confirm KP doesn't crash and that it's just that, when the LaunchBox gets shown and you start typing your search, it vanishes?

[mtaki14]

I overwrote the installation files with the older version so probably the file was overwritten when the executable ran. Not sure if that is the case.

In any case these are the contents of the file:

{
".header" : {
"creator" : "Keypirinha v2.9.3 (697043d)",
"creator_url" : "http://keypirinha.com/",
"format" : 101,
"modified" : "2016-09-06T09:49:16+0300",
"type" : "state"
},
"geometry" : {
"launchbox" : [
{
".monitors" : "monitors(0,0,1366,768,96dpi)",
"pos" : "410x-322",
"size" : 600
}
]
}
}

I am currently running a new installation of the latest version with a clean profile. So far so good.

[mtaki14]

I overwrote the installation files with the older version so probably the file was overwritten when the executable ran. Not sure if that is the case.

In any case these are the contents of the file:

{
".header" : {
"creator" : "Keypirinha v2.9.3 (697043d)",
"creator_url" : "http://keypirinha.com/",
"format" : 101,
"modified" : "2016-09-06T09:49:16+0300",
"type" : "state"
},
"geometry" : {
"launchbox" : [
{
".monitors" : "monitors(0,0,1366,768,96dpi)",
"pos" : "410x-322",
"size" : 600
}
]
}
}

I am currently running a new installation of the latest version with a clean profile. So far so good.

[polyvertex]

The line "pos" : "410x-322" indicates your LaunchBox gets displayed out of screen. That would explain the behavior you observe. I'll investigate further on the persistent geometry feature.

Meanwhile, may I ask for your whole profile directory? Since I'm blind here, I cannot really reduce the spectre of the potential sources to this issue.

[polyvertex]

The line "pos" : "410x-322" indicates your LaunchBox gets displayed out of screen. That would explain the behavior you observe. I'll investigate further on the persistent geometry feature.

Meanwhile, may I ask for your whole profile directory? Since I'm blind here, I cannot really reduce the spectre of the potential sources to this issue.

[polyvertex]

Should be corrected in 2.9.4

[polyvertex]

Should be corrected in 2.9.4