public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Cc: Carlo.DiCocco@dfs.ny.gov
Subject: Re: Fatal Error (Segmentation Fault) only while viewing the LVM GUI
Date: Thu, 26 Apr 2012 13:18:00 -0000 [thread overview]
Message-ID: <4F994B13.7020101@dronecode.org.uk> (raw)
In-Reply-To: <OF35234193.566F8742-ON852579EB.00632D87-852579EB.006511D1@dfs.ny.gov>
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/
next prev parent reply other threads:[~2012-04-26 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 18:22 Carlo.DiCocco
2012-04-26 13:18 ` Jon TURNEY [this message]
2012-04-26 13:23 ` Jon TURNEY
2012-04-26 18:21 ` Jon TURNEY
2012-04-27 12:38 Carlo.DiCocco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F994B13.7020101@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=Carlo.DiCocco@dfs.ny.gov \
--cc=cygwin-xfree@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).