Hi Carlos
If the same wmvolman worked before your git pull, then it's
wmaker-crm fault. In this case, doing a git bisect would
be helpful.
Ran 'n bisect last night, and I ended up with this commit:
c201e1612c1798106ccc2f806669a90b0bbb7a19 (Make wmaker XRandR aware)
Specifically the problem is in event.c:
@@ -562,6 +571,10 @@ static void handleExtensions(XEvent * event)
handleXkbIndicatorStateNotify(event);
}
#endif /*KEEP_XKB_LOCK_STATUS */
+#ifdef HAVE_XRANDR
+ if (has_randr && event->type == (randr_event_base +
RRScreenChangeNotify))
+ Restart(NULL,True);
+#endif
}
For some reason my X sends a RRScreenChangeNotify (binary NVIDIA drivers
maybe?) when X starts, so wmaker restarts immediately on startup. Now
that I know to look for it I can actually see wmaker do a double-take
when it starts (the desktop name flashes twice).
What I suspect is happening (but don't have proof yet) is that wmaker
starts up, it then starts wmvolman, and then restarts because of the
RRScreenChangeNotify. By that time wmvolman has not yet started so it
tries to start it again, resulting in two copies.
I think wmaker needs a "started" flag for each dockapp, so it won't
start them again if they have already been started. Maybe you have
better ideas on how to approach this.
Regards,
Johann
--
To unsubscribe, send mail to [email protected].
