On Fri, Feb 01, 2008 at 01:10:43PM +0600, Roman S Dubtsov wrote: > Hi, > > Thanks a lot for the replies! > > First, I have forgot to mention that I run FVWM under gnome-session manager. > I > think that this may be important, because sometimes gnome-settings-daemon > resets the wallpaper to the one from gnome settings (I wish I could turn this > off, very annoying). After FVWM crash I still have X up and running and I am > able to restart FVWM from console. > > Next, I have two separate screens: DFP and TV set up using nvidia proprietary > driver. I have also reproduced the issue using open-source nv dirver, so > screen setup probably is not an issue. > > Also, I have attached: > * crash.log.bz2 --- log file obtained after source modifications described in > Viktor's e-mail, > * gdb.log.bz2 --- gdb log, > * fvwm.tar.bz2 --- my config (stripped down a bit).
I could take just a quick look at the output. We have average_pixmap = something != 0 cs->width = 720 cs->height = 360 image = 0 k = 0 > The config consists of multiple files that are sourced from .fvwm/config. All > colorset definitions and some uses are in data/decorations/current/script > (Translucent is a left-over from the times I used that patch, now I don't). > Other files where colorsets are used are: > * data/panels/combopanel-horz > * data/scripts/FvwmScript-NetworkPanel > * data/scripts/FvwmScript-ClockCalendar > > PS. I have added a check for NULL after XGetImage with a goto to the cleanup > portion of the function and was not able to reproduce the crash. > > PPS. Just in case, periodically (several minutes after startup, and a day or > two later) I also observe screen lock-ups after dragging a window: window is > not moved, I cannot click on anything, but if there's video output, it goes > on normally. After ~10-15 seconds everything is back to normal. Ciao Dominik ^_^ ^_^ -- Dominik Vogt
