I'm getting this error message every 2nd time I launch geek menu. Geek menu then opens in the wrong location on the desktop and with no menu items or customisation. V1.2.5.2 under Windows XP SP3. I launch geek menu manually by clicking on "start geek.menu" in the root menu of my USB drive.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I used to get that, and then it disappeared as mysteriously as it started... It is possible that it was related to my moving to 1.3.4 (beta). I now have other problems, such as the "leaking categories" I wrote about, but not this one.
Good luck!
Salutations,
-Paul
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-07-22
I just recently started using geek.menu, and I'm having this same problem, exactly as 'debragail' described. It's occurring when it's connected to a computer running Windows XP. I use USBDLM to fix the assigned drive letter at P: and auto-launch geekmenu.exe. It seems that on these occasions when it does this it's somehow unable to read its own configuration file, but it makes no sense that this happens because the same file is there when it does work!
What might be different about my instance is that the exit button is FUBAR when it happens: trying to use it causes geek.menu's window to then become unresponsive, though the Tool Tray icon is still present and responsive to right-clicks. Well… mostly. Usually I wind up having to forcibly kill it with a process manager.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-07-22
Okay… I'm experimentally dancing around the problem by disabling the "Places Bar" modification, since that is what the error message specifically relates to in spite of the fact that the menu completely lacks customization. I simply edited geekmenu.ini and changed 'replacePlacesBar' to false. That seemed to get me past the immediate instance of the problem, so we'll see what happens in the next week.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This issue is gone in 1.3.6.0, but markacraig is right that it will only impact those using the places bar modification. This should default to false on a clean install.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm getting this error message every 2nd time I launch geek menu. Geek menu then opens in the wrong location on the desktop and with no menu items or customisation. V1.2.5.2 under Windows XP SP3. I launch geek menu manually by clicking on "start geek.menu" in the root menu of my USB drive.
Hi, Debra,
I used to get that, and then it disappeared as mysteriously as it started... It is possible that it was related to my moving to 1.3.4 (beta). I now have other problems, such as the "leaking categories" I wrote about, but not this one.
Good luck!
Salutations,
-Paul
I just recently started using geek.menu, and I'm having this same problem, exactly as 'debragail' described. It's occurring when it's connected to a computer running Windows XP. I use USBDLM to fix the assigned drive letter at P: and auto-launch geekmenu.exe. It seems that on these occasions when it does this it's somehow unable to read its own configuration file, but it makes no sense that this happens because the same file is there when it does work!
What might be different about my instance is that the exit button is FUBAR when it happens: trying to use it causes geek.menu's window to then become unresponsive, though the Tool Tray icon is still present and responsive to right-clicks. Well… mostly. Usually I wind up having to forcibly kill it with a process manager.
Okay… I'm experimentally dancing around the problem by disabling the "Places Bar" modification, since that is what the error message specifically relates to in spite of the fact that the menu completely lacks customization. I simply edited geekmenu.ini and changed 'replacePlacesBar' to false. That seemed to get me past the immediate instance of the problem, so we'll see what happens in the next week.
This issue is gone in 1.3.6.0, but markacraig is right that it will only impact those using the places bar modification. This should default to false on a clean install.