Bugzilla – Bug 131619
Regular crashes of YaST modules in 800x600 resolution
Last modified: 2009-11-30 21:08:26 UTC
In 800x600 interlace screen resolution with default GNOME session, YaST modules crashes on exit, if window is maximized during operation. k6-3:~ # YaST2 -i xscreensaver Segmentation fault at /usr/share/YaST2/clients/sw_single.ycp:289 /sbin/YaST2: line 207: 9823 Neoprávněný přístup do paměti (SIGSEGV) $ybindir/y2base $module "$@" qt -geometry "$Y2_GEOMETRY" $Y2QT_ARGS k6-3:~ # YaST2 online_update Segmentation fault at /usr/share/YaST2/clients/online_update.ycp:195 /sbin/YaST2: line 207: 10985 Neoprávněný přístup do paměti (SIGSEGV) $ybindir/y2base $module "$@" qt -geometry "$Y2_GEOMETRY" $Y2QT_ARGS Additional info: Default GNOME contains two protected panels and maximized window has 800x527 pixels.
Please attach the yast2-logfiles here. Are you certain that this has something todo with the screen-resoltion? Have you tried another screen with another resolution with this box?
Well, maybe not with resolution, but with one of screen properties. Tested with YaST2 sw_single: - Make local window fullscreen (800x527). Do not install anything and Accept. -> crashes - Make local window as is (80x550, only move it, to be able to press Accept - see bug 74131). Do not install anything and Accept. -> crashes - Log in to the same machine remotelly (from X screen 1024x768) -> does not crash
Is there some indication of what's going wrong in the logfiles? You might also create a backtrace with gdb and ltrace/strace to narrow the problem.
Strace output, core file and y2log placed to ~sbrabec/y2test131619 There is no evidence, why it crashes. Trying the same windows size on different machine does not crash.
Can you attach these files here, please? Not everyone will have access to your machine. Thanks.
It's 16MB of bzipped data. Moved to ftp://ftp.suse.com/pub/people/sbrabec/testing/131619
I'm reassigning this to Stanislav (Visnovsky)... Stanislav: Please take a look at this.
I can't reproduce it. I need access to the machine.
It is not possible. The machine is not connected to the network and is physically located 100km away. I can try to reproduce on different machine.
Please, reopen if you can reproduce the problem.