On Don, 2011-03-17 at 10:30 +0100, Michal Suchanek wrote: > 2011/3/17 Michel Dänzer <daen...@debian.org>: > > On Don, 2011-03-17 at 09:31 +0100, Michal Suchanek wrote: > >> 2011/3/17 Michel Dänzer <daen...@debian.org>: > >> > On Don, 2011-03-17 at 00:46 +0100, Michal Suchanek wrote: > >> >> > >> >> Running a fullscreen d3d application that changes screen mode (such as > >> >> Vazteroids, in Wine) causes one screen to go blank and the other to > >> >> switch to the resolution the application requested. > >> >> > >> >> When I run my script that sets the main screen to native resolution and > >> >> reenables the other screen and exit the d3d application X crashes. > >> > > >> > Please try to provide more information about the crash. Preferably a > >> > full gdb backtrace, but at least an X log file with a backtrace. > >> > >> It's a double free (abort) so there is no backtrace in the log. There > >> is a gdb backtrace attached to the original report. > > > > Oh, I didn't notice the attachment, and you didn't mention it. > > > > Probably the fastest way to track down the problem would be to run the X > > server in valgrind. > > A valgrind log showing some (probably unrelated) issues. > > As I need to run the X server as root to run in valgrind the > environment is different and there is probably some piece missing. > > I can't reproduce the crash as root with valgrind or without.
The X server always runs as root. You can run the clients from the same user accounts as before. -- Earthling Michel Dänzer | http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1300354347.9075.31.camel@thor.local
