Le Wed, 16 Feb 2011 18:19:19 +0000, Thomas Adam <tho...@xteddy.org> a écrit :
> On Wed, Feb 16, 2011 at 06:28:10PM +0100, Dominique Michel wrote: > > Le Wed, 9 Feb 2011 18:10:30 +0000, > > Thomas Adam <tho...@xteddy.org> a ??crit : > > > > > On Wed, Feb 09, 2011 at 05:22:32PM +0100, Dominique Michel wrote: > > > > Later yesterday, I begin to modify the Corner recipe with the > > > > same fixes I made in Clean and Clean Vertical. But it is not > > > > working into the Corner recipe, FvwmPager is still crashing at > > > > restart once on 2 or 3 times (it show up and disappear, and I > > > > cannot find it with the debug window). It was late and I will > > > > investigate this further today. > > > > > > Then ensure you compile FVWM with "-g" and "-ggdb", because if it > > > really is a crash, there should be a corefile left behind. You'll > > > have also ensure, before starting FVWM in this case, that your > > > ulimit values are set to allow corefile creation, typically: > > > > > > ulimit -c unlimited > > > > > > will suffice. > > > > > > > But I already have a question: In order to be sure than > > > > FvwmPager will work fine, do I need to swallow it into some > > > > button, or will such a swallowing, if it work, just be a > > > > workaround instead of a real fix? > > > > > > No, there is no requirement to swallow it at all. > > > > I found something. Some recipes do have a swallowed FvwmPager, some > > other do have a non swallowed pager. The configuration for the > > pager is the same in fvwm-crystal-3.0.6 and into the svn. I try > > 3.0.6 with my current fvwm-2.5.31. The pager is working fine with > > all the recipe. > > > > That imply than this must be no problem with the pager > > configuration. I > > No, the implication is that it's still broken. There's still a > problem with ParentalRelativity here. > > > SetEnv Desk_Pages_X "8" > > SetEnv Desk_Pages_Y "1" > > PipeRead 'echo DesktopSize $[Desk_Pages_X]x$[Desk_Pages_Y]' > > Why? > > DesktopSize $[foo]x$[bar] > > sufficees, without the PipeRead > > > All (FvwmPager) Close > > No. "KillModule FvwmPager", please. Same goes for all the other > instances where I've seen this in fvwm-crystal. > > > DestroyModuleConfig FvwmPager: * > > PipeRead "echo *FvwmPager: Geometry $[FvwmPager_Width]x24--1+-1" > > Again. Why PipeRead? It's not necessary. > > > DestroyFunc Wallpaper-Pref-Write > > AddToFunc Wallpaper-Pref-Write > > + I Test (x habak) *FvwmBacker: Command (Desk *, Page $0 $1) Exec > > habak -ms $2 > > Of course it will fail with this from time-to-time. You should be > setting the background by testing the page via a function in the > above. > > So you will need to be much more specific now about where the failure > is -- if it is with the Wallpaper-Pref-Write function, that doesn't > surprise me, it's just broken. The reason why it will work sometimes > and not others is all to do with how functions are parsed and acted > on. Something I've already documented on the wiki. > > -- Thomas Adam > I get some time to look at it and I am just more confused. I modified the way FvwmBacker config is loaded: file preferences/LastChoosenWallpaper: AddToFunc StartFunction I Module FvwmBacker DestroyModuleConfig FvwmBacker* *FvwmBacker: Command (Desk 0, Page 0 0) Exec Esetroot -scale /home/dom/.fvwm-crystal/wallpapers/Stars/orion_gendler_big.jpg *FvwmBacker: Command (Desk 0, Page 1 0) Exec Esetroot -scale /home/dom/.fvwm-crystal/wallpapers/Stars/orion_gendler_big.jpg *FvwmBacker: Command (Desk 0, Page 2 0) Exec Esetroot -scale /home/dom/.fvwm-crystal/wallpapers/Art/Boulet_01.jpg *FvwmBacker: Command (Desk 0, Page 3 0) Exec Esetroot -scale /home/dom/.fvwm-crystal/wallpapers/Stars/orion_gendler_big.jpg *FvwmBacker: Command (Desk 0, Page 4 0) Exec Esetroot -scale /home/dom/.fvwm-crystal/wallpapers/Cuba/08_Playa/raw_DSC_0256.jpg *FvwmBacker: Command (Desk 0, Page 5 0) Exec Esetroot -scale /home/dom/.fvwm-crystal/wallpapers/Cuba/05_Trinidad/raw_DSC_0202.jpg *FvwmBacker: Command (Desk 0, Page 6 0) Exec Esetroot -scale /home/dom/.fvwm-crystal/wallpapers/Stars/orion_gendler_big.jpg *FvwmBacker: Command (Desk 0, Page 7 0) Exec Esetroot -scale /home/dom/.fvwm-crystal/wallpapers/Art/jose_correa_w3csg002_lever_de_lune.jpg This file is read with Include preferences/LastChoosenWallpaper where Include is DestroyFunc Include AddToFunc Include + I Test (f $[FVWM_USERDIR]/$*) Read $[FVWM_USERDIR]/$* ... I also try to put the content of preferences/LastChoosenWallpaper directly into a recipe. The problem remain the same in both cases. I wrote a plain fvwm config file with all the styles, all the element of the desktop, this wallpaper stuff, and a little menu with quit and restart. This work just fine when I run fvwm with Xephyr. But it is a difference. When I restart fvwm running the plain fvwm config file in Xephyr, the screen is always completely erased and become black during a little amount of time during the restart. When I restart the equivalent fvwm-crystal recipe in Xephyr, sometime the screen is completely erased, sometime the wallpaper is still here. The issue occur only when the wallpaper is visible during the restart, but not each time. So, I am lost here. It look like something interfere with the action's order during the restart. I also try to modify the recipe by starting all the modules into the StartFunction, but that doesn't helped. Dominique -- "We have the heroes we deserve." _______________________________________________ fvwm-crystal-users mailing list fvwm-crystal-users@gna.org https://mail.gna.org/listinfo/fvwm-crystal-users
