On Sun, Feb 14, 2010 at 02:47:46PM +0000, Justin B Rye wrote: > Package: wdm > Version: 1.28-3.3 > > Now that a new version is available I'll send a followup - thanks > for maintaining wdm!
Unfortunately wdm is currently orphaned, I not the maintainer, and do not intend to adopt it. I am just reviewing some of its bug reports before the QA team receives it. > > On Fri, Sep 18, Justin B Rye wrote: > > Package: wdm > > Version: 1.28-3.1 > > Severity: important > > > > To be specific, /usr/bin/wdmLogin segfaults. > > That was on a machine which has since been decommissioned, trying > with either a Matrox Marvel graphics card or an antique S3ViRGE. > There, the segfaults happened frequently but not invariably (but > didn't start until the upgrade to Squeeze, and always stopped when I > switched to another display manager); elsewhere things have gone > differently. > > On a second i386 machine, I've seen the same versions of wdm working > flawlessly with the same Matrox card. > > On a third, I've seen wdm failing in a slightly different fashion. > This one is in fact a triple-boot Debian testbed PC with a Lenny > partition, a Squeeze/Sid partition, and a Squeeze kFreeBSD > partition; the graphics card is an onboard i8xx. In each case, > regardless of the kernel and X version involved, wdm fails. It > doesn't segfault, though - it just crashes over and over again when > it gets to the point of setting up the login screen. No such > problems occur with xdm, slim, nodm, or startx. I looked more at this problem and think this is the same problem as in http://bugs.debian.org/488715 [Fails to start] and in https://bugzilla.novell.com/show_bug.cgi?id=447331 where some corruptions appear when composite is enabled, and at a depth other than 24. I also noticed some strange segfault at my site, but only when exiting wdm with /etc/init.d/wdm stop. Patch from opensuse bugzilla seems to have fixed that problem here and I expect it to also fix #547251 and #488715. I am preparing a non maintainer upload for wdm including that fix. I will close #547251 and #488715 with it. Please reopen if problem was not fixed at your site. Thanks for your feedback, -- Agustin -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
