Re: Fatal Error (Segmentation Fault) only while viewing the LVM GUI
On 25/04/2012 19:25, Carlo.DiCocco wrote: I think I may have found a bug. I am connecting to a remote Linux server from my Windows desktop and attempting to use some of the GUI tools on the remote server. The xclock GUI displays fine. The Oracle dbca GUI displays fine. The LVM system-config-lvm GUI displays and works fine, but cygwin generates a fatal error window due to a segmentation fault. The following command displays the GUI, but reports a fatal error: [root@aorahdev ~]# system-config-lvm [ 64144.546] Segmentation fault at address 0x44 [ 64144.546] Fatal server error: [ 64144.546] Caught signal 11 (Segmentation fault). Server aborting [ 64144.546] Server terminated with error (1). Closing log file. Thanks for reporting this problem. I was not able to reproduce this crash using system-config-lvm 1.1.16, on Fedora 15. Perhaps you can provide details on the remote server and system-config-lvm version you are using? It would be very helpful if you could follow the instructions at [1] to use gdb to get a backtrace for the X server when it crashes. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Fatal Error (Segmentation Fault) only while viewing the LVM GUI
On 26/04/2012 14:18, Jon TURNEY wrote: On 25/04/2012 19:25, Carlo.DiCocco wrote: I think I may have found a bug. I am connecting to a remote Linux server from my Windows desktop and attempting to use some of the GUI tools on the remote server. The xclock GUI displays fine. The Oracle dbca GUI displays fine. The LVM system-config-lvm GUI displays and works fine, but cygwin generates a fatal error window due to a segmentation fault. The following command displays the GUI, but reports a fatal error: [root@aorahdev ~]# system-config-lvm [ 64144.546] Segmentation fault at address 0x44 [ 64144.546] Fatal server error: [ 64144.546] Caught signal 11 (Segmentation fault). Server aborting [ 64144.546] Server terminated with error (1). Closing log file. Thanks for reporting this problem. I was not able to reproduce this crash using system-config-lvm 1.1.16, on Fedora 15. Perhaps you can provide details on the remote server and system-config-lvm version you are using? It would be very helpful if you could follow the instructions at [1] to use gdb to get a backtrace for the X server when it crashes. Oops [1] http://x.cygwin.com/devel/backtrace.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Fatal Error (Segmentation Fault) only while viewing the LVM GUI
On 26/04/2012 14:23, Jon TURNEY wrote: On 26/04/2012 14:18, Jon TURNEY wrote: On 25/04/2012 19:25, Carlo.DiCocco wrote: I think I may have found a bug. I am connecting to a remote Linux server from my Windows desktop and attempting to use some of the GUI tools on the remote server. The xclock GUI displays fine. The Oracle dbca GUI displays fine. The LVM system-config-lvm GUI displays and works fine, but cygwin generates a fatal error window due to a segmentation fault. The following command displays the GUI, but reports a fatal error: [root@aorahdev ~]# system-config-lvm [ 64144.546] Segmentation fault at address 0x44 [ 64144.546] Fatal server error: [ 64144.546] Caught signal 11 (Segmentation fault). Server aborting [ 64144.546] Server terminated with error (1). Closing log file. Thanks for reporting this problem. I was not able to reproduce this crash using system-config-lvm 1.1.16, on Fedora 15. Perhaps you can provide details on the remote server and system-config-lvm version you are using? It would be very helpful if you could follow the instructions at [1] to use gdb to get a backtrace for the X server when it crashes. Oops [1] http://x.cygwin.com/devel/backtrace.html It seems quite likely this is the same crash as reported at [1], so it's probably worth testing X server 1.12.0-5 to see if it's fixed there, first. [1] http://cygwin.com/ml/cygwin-xfree/2012-04/msg00097.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
