On Mon, Apr 20, 2009 at 8:39 AM, Paul Harris <[email protected]> wrote: > 2009/4/20 Samir SAADA <[email protected]>: >> On Mon, Apr 20, 2009 at 1:59 AM, Paul Harris <[email protected]> wrote: >>>>> $ tar xf /tmp/pauls_test.tar.gz >>>> >>>> Is this your configuration files from your user that already >>>> reproduces the strange behavior? >>>> >>> >>> its the config files, slimmed down to just the bare bones. with this, >>> I am able to see the problem. >> >> You don't need that. just start you wmaker after doing an adduser(8), >> as your new user of course. > > you DO need those configuration files if you want to see the problem! > > I didn't want to give my full configuration files as its got all sort > of shit in there. > > If you just run wmaker, you MAY NOT see the problem. > > Maybe this is why you were not able to see the problem, did you follow > my instructions to the letter? Did you extract the config files I > included? > > >>> >>>>> can anyone duplicate this? >>>> >>>> The test case is clear thank you, however it doesn't reproduced the >>>> described follower icon. >>>> >>> >>> What version of wmaker are you using? >>> >>> I just tried it and successfully duplicated the test on a second machine. >>> >>> I'm using Debian's testing wmaker (freshly installed), and on the >>> second machine I also had to edit .vnc/xstartup so that it didn't run >>> x-window-manager at the end, instead I added "wmaker &" >> >> John gave you the link to it, anyway browser the front page of >> http://windowmaker.info and you'll have the dev verison from hg site >> and the latest stable version too. >> >> Can you explain the reasons of working with vnc? > > So that you don't need to log out, of course! I have all sorts of > windows and editors open, I don't want to close them all down just to > test this bug. > >> You don't need vnc. Just login as your new user, add -- exec wmaker >> -- in your .xinitrc, >> and type startx at terminal prompt, here you go! >> > > of course, again that would require logging out. This way you could > test for the bug, code a patch, compile, test again, all without > logging out or disturbing your environment. >
Paul, I didn't suggest you to log out ? anyway it's your way to do. I have nothing to say about it. But obviously you didn't reproduce the bug with a fresh configuration file. It is possible that you corrupted your configuration file, and this is not the bug you mentioned in this thread. This bug report is invalid for me until new elements are brought, and this is my last word on this thread. -- To unsubscribe, send mail to [email protected].
