"X -configure" segmentation fault

classic Classic list List threaded Threaded
21 messages Options
12
Reply | Threaded
Open this post in threaded view
|

"X -configure" segmentation fault

hepta tor
I am trying to generate a starting xorg.conf file by running "X
-configure" but get a segmentation fault error (output below). Any
ideas what could go wrong? Have tried this both in a VMware guest and
on real hardware but I get the same problems. dmesg is at the end.
thanks
-h


************************************************************
# X -configure

X.Org X Server 1.14.2
Release Date: 2013-06-25
X Protocol Version 11, Revision 0
Build Operating System: OpenBSD 5.4 amd64
Current Operating System: OpenBSD daq.lan 5.4 GENERIC.MP#53 amd64
Build Date: 06 September 2013  02:03:22PM

Current version of pixman: 0.30.2
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Sep 10 23:58:12 2013
List of video drivers:
        apm
        ark
        ati
        chips
        cirrus
        dummy
        glint
        i128
        intel
        mach64
        mga
        neomagic
        nv
        openchrome
        r128
        radeon
        rendition
        s3
        s3virge
        savage
        siliconmotion
        sis
        tdfx
        trident
        tseng
        wsudl
        wsudl
        vmware
        vesa
(==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d"
(EE) Segmentation fault at address 0x28
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
(EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for
additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
Abort trap

************************************************************



dmesg:

OpenBSD 5.4-current (GENERIC.MP) #53: Sun Sep  8 15:28:55 MDT 2013
    [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 520028160 (495MB)
avail mem = 498135040 (475MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (364 entries)
bios0: vendor Phoenix Technologies LTD version "6.00" date 07/31/2013
bios0: VMware, Inc. VMware Virtual Platform
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP BOOT APIC MCFG SRAT HPET WAET
acpi0: wakeup devices PCI0(S3) USB_(S1) P2P0(S3) S1F0(S3) S2F0(S3)
S3F0(S3) S4F0(S3) S5F0(S3) S6F0(S3) S7F0(S3) S8F0(S3) S9F0(S3)
S10F(S3) S11F(S3) S12F(S3) S13F(S3) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz, 2394.59 MHz
cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,SSSE3,CX16,SSE4.1,x2APIC,NXE,LONG,LAHF,PERF,ITSC
cpu0: 3MB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
cpu0: apic clock running at 66MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz, 2418.56 MHz
cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,SSSE3,CX16,SSE4.1,x2APIC,NXE,LONG,LAHF,PERF,ITSC
cpu1: 3MB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec00000, version 11, 24 pins
acpimcfg0 at acpi0 addr 0xf0000000, bus 0-127
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0
acpicpu1 at acpi0
acpibat0 at acpi0: BAT1 not present
acpibat1 at acpi0: BAT2 not present
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: SLPB
acpibtn1 at acpi0: LID_
vmt0 at mainbus0
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x01
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x01
pci1 at ppb0 bus 1
pcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x08
pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA,
channel 0 configured to compatibility, channel 1 configured to
compatibility
pciide0: channel 0 disabled (no drives)
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <NECVMWar, VMware IDE CDR10, 1.00> ATAPI
5/cdrom removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
piixpm0 at pci0 dev 7 function 3 "Intel 82371AB Power" rev 0x08: SMBus disabled
"VMware Virtual Machine Interface" rev 0x10 at pci0 dev 7 function 7
not configured
vga1 at pci0 dev 15 function 0 "VMware Virtual SVGA II" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
mpi0 at pci0 dev 16 function 0 "Symbios Logic 53c1030" rev 0x01: apic 2 int 17
scsibus1 at mpi0: 16 targets, initiator 7
sd0 at scsibus1 targ 0 lun 0: <VMware,, VMware Virtual S, 1.0> SCSI2
0/direct fixed
sd0: 20480MB, 512 bytes/sector, 41943040 sectors
mpi0: target 0 Sync at 160MHz width 16bit offset 127 QAS 1 DT 1 IU 1
ppb1 at pci0 dev 17 function 0 "VMware Virtual" rev 0x02
pci2 at ppb1 bus 2
uhci0 at pci2 dev 0 function 0 "VMware Virtual UHCI" rev 0x00: apic 2 int 18
em0 at pci2 dev 1 function 0 "Intel 82545EM" rev 0x01: apic 2 int 19,
address 00:0c:29:eb:94:f6
eap0 at pci2 dev 2 function 0 "Ensoniq AudioPCI97" rev 0x02: apic 2 int 16
ac97: codec id 0x43525913 (Cirrus Logic CS4297A rev 3)
audio0 at eap0
midi0 at eap0: <AudioPCI MIDI UART>
ehci0 at pci2 dev 3 function 0 "VMware Virtual EHCI" rev 0x00: apic 2 int 17
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "VMware EHCI root hub" rev 2.00/1.00 addr 1
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 "VMware UHCI root hub" rev 1.00/1.00 addr 1
ppb2 at pci0 dev 21 function 0 "VMware Virtual PCIE-PCIE" rev 0x01
pci3 at ppb2 bus 3
ppb3 at pci0 dev 21 function 1 "VMware Virtual PCIE-PCIE" rev 0x01
pci4 at ppb3 bus 4
ppb4 at pci0 dev 21 function 2 "VMware Virtual PCIE-PCIE" rev 0x01
pci5 at ppb4 bus 5
ppb5 at pci0 dev 21 function 3 "VMware Virtual PCIE-PCIE" rev 0x01
pci6 at ppb5 bus 6
ppb6 at pci0 dev 21 function 4 "VMware Virtual PCIE-PCIE" rev 0x01
pci7 at ppb6 bus 7
ppb7 at pci0 dev 21 function 5 "VMware Virtual PCIE-PCIE" rev 0x01
pci8 at ppb7 bus 8
ppb8 at pci0 dev 21 function 6 "VMware Virtual PCIE-PCIE" rev 0x01
pci9 at ppb8 bus 9
ppb9 at pci0 dev 21 function 7 "VMware Virtual PCIE-PCIE" rev 0x01
pci10 at ppb9 bus 10
ppb10 at pci0 dev 22 function 0 "VMware Virtual PCIE-PCIE" rev 0x01
pci11 at ppb10 bus 11
ppb11 at pci0 dev 22 function 1 "VMware Virtual PCIE-PCIE" rev 0x01
pci12 at ppb11 bus 12
ppb12 at pci0 dev 22 function 2 "VMware Virtual PCIE-PCIE" rev 0x01
pci13 at ppb12 bus 13
ppb13 at pci0 dev 22 function 3 "VMware Virtual PCIE-PCIE" rev 0x01
pci14 at ppb13 bus 14
ppb14 at pci0 dev 22 function 4 "VMware Virtual PCIE-PCIE" rev 0x01
pci15 at ppb14 bus 15
ppb15 at pci0 dev 22 function 5 "VMware Virtual PCIE-PCIE" rev 0x01
pci16 at ppb15 bus 16
ppb16 at pci0 dev 22 function 6 "VMware Virtual PCIE-PCIE" rev 0x01
pci17 at ppb16 bus 17
ppb17 at pci0 dev 22 function 7 "VMware Virtual PCIE-PCIE" rev 0x01
pci18 at ppb17 bus 18
ppb18 at pci0 dev 23 function 0 "VMware Virtual PCIE-PCIE" rev 0x01
pci19 at ppb18 bus 19
ppb19 at pci0 dev 23 function 1 "VMware Virtual PCIE-PCIE" rev 0x01
pci20 at ppb19 bus 20
ppb20 at pci0 dev 23 function 2 "VMware Virtual PCIE-PCIE" rev 0x01
pci21 at ppb20 bus 21
ppb21 at pci0 dev 23 function 3 "VMware Virtual PCIE-PCIE" rev 0x01
pci22 at ppb21 bus 22
ppb22 at pci0 dev 23 function 4 "VMware Virtual PCIE-PCIE" rev 0x01
pci23 at ppb22 bus 23
ppb23 at pci0 dev 23 function 5 "VMware Virtual PCIE-PCIE" rev 0x01
pci24 at ppb23 bus 24
ppb24 at pci0 dev 23 function 6 "VMware Virtual PCIE-PCIE" rev 0x01
pci25 at ppb24 bus 25
ppb25 at pci0 dev 23 function 7 "VMware Virtual PCIE-PCIE" rev 0x01
pci26 at ppb25 bus 26
ppb26 at pci0 dev 24 function 0 "VMware Virtual PCIE-PCIE" rev 0x01
pci27 at ppb26 bus 27
ppb27 at pci0 dev 24 function 1 "VMware Virtual PCIE-PCIE" rev 0x01
pci28 at ppb27 bus 28
ppb28 at pci0 dev 24 function 2 "VMware Virtual PCIE-PCIE" rev 0x01
pci29 at ppb28 bus 29
ppb29 at pci0 dev 24 function 3 "VMware Virtual PCIE-PCIE" rev 0x01
pci30 at ppb29 bus 30
ppb30 at pci0 dev 24 function 4 "VMware Virtual PCIE-PCIE" rev 0x01
pci31 at ppb30 bus 31
ppb31 at pci0 dev 24 function 5 "VMware Virtual PCIE-PCIE" rev 0x01
pci32 at ppb31 bus 32
ppb32 at pci0 dev 24 function 6 "VMware Virtual PCIE-PCIE" rev 0x01
pci33 at ppb32 bus 33
ppb33 at pci0 dev 24 function 7 "VMware Virtual PCIE-PCIE" rev 0x01
pci34 at ppb33 bus 34
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
uhidev0 at uhub1 port 1 configuration 1 interface 0 "VMware VMware
Virtual USB Mouse" rev 1.10/1.02 addr 2
uhidev0: iclass 3/0
ums0 at uhidev0: 16 buttons, Z dir
wsmouse1 at ums0 mux 0
uhidev1 at uhub1 port 1 configuration 1 interface 1 "VMware VMware
Virtual USB Mouse" rev 1.10/1.02 addr 2
uhidev1: iclass 3/0
ums1 at uhidev1: 16 buttons, Z dir
wsmouse2 at ums1 mux 0
uhub2 at uhub1 port 2 "vendor 0x0e0f VMware Virtual USB Hub" rev
1.10/1.00 addr 3
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on sd0a (4cb38eaa9074f9f9.a) swap on sd0b dump on sd0b

Reply | Threaded
Open this post in threaded view
|

Re: "X -configure" segmentation fault

Martin Brandenburg
On Tue, Sep 10, 2013 at 10:18:43PM +0000, Heptas Torres wrote:
> I am trying to generate a starting xorg.conf file by running "X
> -configure" but get a segmentation fault error (output below). Any
> ideas what could go wrong? Have tried this both in a VMware guest and
> on real hardware but I get the same problems. dmesg is at the end.
> thanks
> -h

A similar problem was discussed about a month ago here[1]. The code of X
-configure is not maintained. See Matthieu Herrb's suggestions in the
archive or enclosed below.

[1] http://mid.gmane.org/20130819055603.GA12883@...

- Martin

On Mon, 19 Aug 2013 07:56:04 +0200, Matthieu Herrb wrote:
> I've written to a number of mailing lists of a long time that the code
> behind X -configure is not maintained (and there are a number of knwon
> issues) and that I strongly recommend not using it. Running X without
> a config file is much more likely to produce a working result.
>
> And for the few cases where an xorg.conf file is needed, just read the
> xorg.conf(5) man page and use a text editor to create one containing
> only the needed section(s).

Reply | Threaded
Open this post in threaded view
|

Re: "X -configure" segmentation fault

hepta tor
On 9/10/13, Martin Brandenburg <[hidden email]> wrote:

> On Tue, Sep 10, 2013 at 10:18:43PM +0000, Heptas Torres wrote:
>> I am trying to generate a starting xorg.conf file by running "X
>> -configure" but get a segmentation fault error (output below). Any
>> ideas what could go wrong? Have tried this both in a VMware guest and
>> on real hardware but I get the same problems. dmesg is at the end.
>> thanks
>> -h
>
> A similar problem was discussed about a month ago here[1]. The code of X
> -configure is not maintained. See Matthieu Herrb's suggestions in the
> archive or enclosed below.

Thanks for the pointer. Wanted to run cwm but could not make it work -
I guess it's related to the problem you mention.

Does this mean that obsd as a desktop is not really supported on the long run?

Maybe the page at http://www.openbsd.org/faq/faq11.html#amd64i386
should be updated so that it gives an indication that the info is not
updated? Thought quality of the documentation was a core goal of obsd
:)

-H


> [1] http://mid.gmane.org/20130819055603.GA12883@...
>
> - Martin
>
> On Mon, 19 Aug 2013 07:56:04 +0200, Matthieu Herrb wrote:
>> I've written to a number of mailing lists of a long time that the code
>> behind X -configure is not maintained (and there are a number of knwon
>> issues) and that I strongly recommend not using it. Running X without
>> a config file is much more likely to produce a working result.
>>
>> And for the few cases where an xorg.conf file is needed, just read the
>> xorg.conf(5) man page and use a text editor to create one containing
>> only the needed section(s).

Reply | Threaded
Open this post in threaded view
|

Re: "X -configure" segmentation fault

Antoine Jacoutot-7
> Thanks for the pointer. Wanted to run cwm but could not make it work -
> I guess it's related to the problem you mention.
>
> Does this mean that obsd as a desktop is not really supported on the long run?

Considering that several OpenBSD developers also have commit access (and/or a high position in) to GNOME, KDE, LibreOffice, Mozilla, X.org ... and use these softwares everyday on OpenBSD -- then I would say yes, obviously OpenBSD as a Desktop is doomed for eternity.
Oh and we have the best KMS support of all BSDs, but it's only needed on the VAX obviously -- no Desktop would ever need that.

--
Antoine

Reply | Threaded
Open this post in threaded view
|

Re: "X -configure" segmentation fault

David Coppa
In reply to this post by hepta tor
On Wed, Sep 11, 2013 at 10:37 AM, Heptas Torres <[hidden email]> wrote:

> On 9/10/13, Martin Brandenburg <[hidden email]> wrote:
>> On Tue, Sep 10, 2013 at 10:18:43PM +0000, Heptas Torres wrote:
>>> I am trying to generate a starting xorg.conf file by running "X
>>> -configure" but get a segmentation fault error (output below). Any
>>> ideas what could go wrong? Have tried this both in a VMware guest and
>>> on real hardware but I get the same problems. dmesg is at the end.
>>> thanks
>>> -h
>>
>> A similar problem was discussed about a month ago here[1]. The code of X
>> -configure is not maintained. See Matthieu Herrb's suggestions in the
>> archive or enclosed below.
>
> Thanks for the pointer. Wanted to run cwm but could not make it work -
> I guess it's related to the problem you mention.
>
> Does this mean that obsd as a desktop is not really supported on the long run?

Don't make me laugh.

I use OpenBSD for my desktop on a daily-basis since years:
http://dcoppa.deviantart.com/gallery/

Reply | Threaded
Open this post in threaded view
|

Re: "X -configure" segmentation fault

hepta tor
On 9/11/13, David Coppa <[hidden email]> wrote:

> On Wed, Sep 11, 2013 at 10:37 AM, Heptas Torres <[hidden email]> wrote:
>> On 9/10/13, Martin Brandenburg <[hidden email]> wrote:
>>> On Tue, Sep 10, 2013 at 10:18:43PM +0000, Heptas Torres wrote:
>>>> I am trying to generate a starting xorg.conf file by running "X
>>>> -configure" but get a segmentation fault error (output below). Any
>>>> ideas what could go wrong? Have tried this both in a VMware guest and
>>>> on real hardware but I get the same problems. dmesg is at the end.
>>>> thanks
>>>> -h
>>>
>>> A similar problem was discussed about a month ago here[1]. The code of X
>>> -configure is not maintained. See Matthieu Herrb's suggestions in the
>>> archive or enclosed below.
>>
>> Thanks for the pointer. Wanted to run cwm but could not make it work -
>> I guess it's related to the problem you mention.
>>
>> Does this mean that obsd as a desktop is not really supported on the long
>> run?
>
> Don't make me laugh.
>
> I use OpenBSD for my desktop on a daily-basis since years:
> http://dcoppa.deviantart.com/gallery/

I was referring to what's in the base system. I am looking for a
minimal window manager in the base system, so no external packages. I
wanted to try out cwm but when I run it I get " cwm: unable to open
display "" ". Is some special configuration needed to run it properly?
-h

Reply | Threaded
Open this post in threaded view
|

Re: "X -configure" segmentation fault

David Coppa
On Wed, Sep 11, 2013 at 11:15 AM, Heptas Torres <[hidden email]> wrote:

> I was referring to what's in the base system. I am looking for a
> minimal window manager in the base system, so no external packages. I
> wanted to try out cwm but when I run it I get " cwm: unable to open
> display "" ". Is some special configuration needed to run it properly?
> -h

I'm sorry to say but this is Unix 101.

Reply | Threaded
Open this post in threaded view
|

Re: "X -configure" segmentation fault

Zé Loff-2
In reply to this post by hepta tor
On Wed, Sep 11, 2013 at 09:15:57AM +0000, Heptas Torres wrote:

> On 9/11/13, David Coppa <[hidden email]> wrote:
> > On Wed, Sep 11, 2013 at 10:37 AM, Heptas Torres <[hidden email]> wrote:
> >> On 9/10/13, Martin Brandenburg <[hidden email]> wrote:
> >>> On Tue, Sep 10, 2013 at 10:18:43PM +0000, Heptas Torres wrote:
> >>>> I am trying to generate a starting xorg.conf file by running "X
> >>>> -configure" but get a segmentation fault error (output below). Any
> >>>> ideas what could go wrong? Have tried this both in a VMware guest and
> >>>> on real hardware but I get the same problems. dmesg is at the end.
> >>>> thanks
> >>>> -h
> >>>
> >>> A similar problem was discussed about a month ago here[1]. The code of X
> >>> -configure is not maintained. See Matthieu Herrb's suggestions in the
> >>> archive or enclosed below.
> >>
> >> Thanks for the pointer. Wanted to run cwm but could not make it work -
> >> I guess it's related to the problem you mention.
> >>
> >> Does this mean that obsd as a desktop is not really supported on the long
> >> run?
> >
> > Don't make me laugh.
> >
> > I use OpenBSD for my desktop on a daily-basis since years:
> > http://dcoppa.deviantart.com/gallery/
>
> I was referring to what's in the base system. I am looking for a
> minimal window manager in the base system, so no external packages. I
> wanted to try out cwm but when I run it I get " cwm: unable to open
> display "" ". Is some special configuration needed to run it properly?
> -h
>

man xinitrc

Reply | Threaded
Open this post in threaded view
|

Re: "X -configure" segmentation fault

Zoran Kolic-4
In reply to this post by hepta tor
> I was referring to what's in the base system. I am looking for a
> minimal window manager in the base system, so no external packages. I
> wanted to try out cwm but when I run it I get " cwm: unable to open
> display "" ". Is some special configuration needed to run it properly?

In fact, fvwm is in base part. It is highly customable and
able to follow the way I use "the desktop".
Reading manual pages is necessary to get the best of almost
every application in the world.
Best regards

                                   Zoran

Reply | Threaded
Open this post in threaded view
|

Re: "X -configure" segmentation fault

Carson Chittom-3
In reply to this post by hepta tor
Heptas Torres <[hidden email]> writes:

> Does this mean that obsd as a desktop is not really supported on the long run?

I run OpenBSD as a desktop every day.  Depends on how you mean
"supported."  (Read: The fact that upstream code isn't maintained isn't
OpenBSD's fault.  If X's autoconfigure system doesn't work for you,
then that's a bug that should be filed--presumably upstream, with X.)

Reply | Threaded
Open this post in threaded view
|

Re: fvwm in base [was: "X -configure" segmentation fault]

Carson Chittom-3
In reply to this post by Zoran Kolic-4
Zoran Kolic <[hidden email]> writes:

> In fact, fvwm is in base part.

A while ago, there was a message to misc from the fvwm developer about
relicensing fvwm to allow a more recent version into base.  I wonder if
there is any status update?

Reply | Threaded
Open this post in threaded view
|

Re: fvwm in base [was: "X -configure" segmentation fault]

James Griffin-2
On Thu, Sep 12, 2013 at 12:10:36AM -0500, Carson Chittom wrote:

> Zoran Kolic <[hidden email]> writes:
>
> > In fact, fvwm is in base part.
>
> A while ago, there was a message to misc from the fvwm developer about
> relicensing fvwm to allow a more recent version into base.  I wonder if
> there is any status update?
>

I do know he is stepping down from the development, forums and wiki of
fvwm2 - announced earlier this week.

Reply | Threaded
Open this post in threaded view
|

Re: fvwm in base [was: "X -configure" segmentation fault]

Thomas Adam-5
In reply to this post by Carson Chittom-3
On 12 September 2013 06:10, Carson Chittom <[hidden email]> wrote:
> Zoran Kolic <[hidden email]> writes:
>
>> In fact, fvwm is in base part.
>
> A while ago, there was a message to misc from the fvwm developer about
> relicensing fvwm to allow a more recent version into base.  I wonder if
> there is any status update?

That is I.  Unfortunately, FVWM cannot be relicensed.

-- Thomas Adam

Reply | Threaded
Open this post in threaded view
|

Re: "X -configure" segmentation fault

howard eisenberger
In reply to this post by hepta tor
On Tue, Sep 10, 2013 at 10:18:43PM +0000, Heptas Torres wrote:

> I am trying to generate a starting xorg.conf file by running "X
> -configure" but get a segmentation fault error (output below). Any
> ideas what could go wrong? Have tried this both in a VMware guest and
> on real hardware but I get the same problems. dmesg is at the end.

Hello,

I got the same thing this evening on a Debian (jessie) box, but
xorg.conf.new was created and seemed to work fine. X worked without
it, but I was able to get a higher resolution by editing xorg.conf.

Regards,

Howard E.
Ottawa

Reply | Threaded
Open this post in threaded view
|

Re: fvwm in base [was: "X -configure" segmentation fault]

James Griffin-2
In reply to this post by Thomas Adam-5
* Thomas Adam <[hidden email]> [2013-09-12 10:17:56 +0100]:

> On 12 September 2013 06:10, Carson Chittom <[hidden email]> wrote:
> > Zoran Kolic <[hidden email]> writes:
> >
> >> In fact, fvwm is in base part.
> >
> > A while ago, there was a message to misc from the fvwm developer about
> > relicensing fvwm to allow a more recent version into base.  I wonder if
> > there is any status update?
>
> That is I.  Unfortunately, FVWM cannot be relicensed.
>
> -- Thomas Adam

If it can't be relicensed so an up-to-date version can be included in the base distribution then is there much point in it being there at all? People can simply use the package/port to install a supported version and the base distribution can simply have cwm as its main wm.

Reply | Threaded
Open this post in threaded view
|

Re: fvwm in base [was: "X -configure" segmentation fault]

Jeremie Courreges-Anglas-2
James Griffin <[hidden email]> writes:

> * Thomas Adam <[hidden email]> [2013-09-12 10:17:56 +0100]:
>
>> On 12 September 2013 06:10, Carson Chittom <[hidden email]> wrote:
>> > Zoran Kolic <[hidden email]> writes:
>> >
>> >> In fact, fvwm is in base part.
>> >
>> > A while ago, there was a message to misc from the fvwm developer about
>> > relicensing fvwm to allow a more recent version into base.  I wonder if
>> > there is any status update?
>>
>> That is I.  Unfortunately, FVWM cannot be relicensed.
>>
>> -- Thomas Adam
>
> If it can't be relicensed so an up-to-date version can be included in
> the base distribution then is there much point in it being there at all?
> People can simply use the package/port to install a supported version
> and the base distribution can simply have cwm as its main wm.

Lots of people use the base fvwm.  Which works fine for them, even if
older.  Also fvwm is easier to work than cwm when you don't know either.

--
jca | PGP: 0x06A11494 / 61DB D9A0 00A4 67CF 2A90  8961 6191 8FBF 06A1 1494

Reply | Threaded
Open this post in threaded view
|

Re: fvwm in base [was: "X -configure" segmentation fault]

Thomas Adam-5
Hi,

On 15 September 2013 11:48, Jérémie Courrèges-Anglas <[hidden email]> wrote:

> James Griffin <[hidden email]> writes:
>
>> * Thomas Adam <[hidden email]> [2013-09-12 10:17:56 +0100]:
>>
>>> On 12 September 2013 06:10, Carson Chittom <[hidden email]> wrote:
>>> > Zoran Kolic <[hidden email]> writes:
>>> >
>>> >> In fact, fvwm is in base part.
>>> >
>>> > A while ago, there was a message to misc from the fvwm developer about
>>> > relicensing fvwm to allow a more recent version into base.  I wonder if
>>> > there is any status update?
>>>
>>> That is I.  Unfortunately, FVWM cannot be relicensed.
>>>
>>> -- Thomas Adam
>>
>> If it can't be relicensed so an up-to-date version can be included in
>> the base distribution then is there much point in it being there at all?
>> People can simply use the package/port to install a supported version
>> and the base distribution can simply have cwm as its main wm.
>
> Lots of people use the base fvwm.  Which works fine for them, even if
> older.  Also fvwm is easier to work than cwm when you don't know either.

I agree.  The fact that there's a newer version of FVWM in ports is
fine; FVWM in base, despite being older might be a minor nuisance, but
not insurmountable.

-- Thomas Adam

Reply | Threaded
Open this post in threaded view
|

Re: fvwm in base [was: "X -configure" segmentation fault]

Marc Espie-2
On Sun, Sep 15, 2013 at 08:12:53PM +0100, Thomas Adam wrote:

> Hi,
>
> On 15 September 2013 11:48, Jérémie Courrèges-Anglas <[hidden email]> wrote:
> > James Griffin <[hidden email]> writes:
> >
> >> * Thomas Adam <[hidden email]> [2013-09-12 10:17:56 +0100]:
> >>
> >>> On 12 September 2013 06:10, Carson Chittom <[hidden email]> wrote:
> >>> > Zoran Kolic <[hidden email]> writes:
> >>> >
> >>> >> In fact, fvwm is in base part.
> >>> >
> >>> > A while ago, there was a message to misc from the fvwm developer about
> >>> > relicensing fvwm to allow a more recent version into base.  I wonder if
> >>> > there is any status update?
> >>>
> >>> That is I.  Unfortunately, FVWM cannot be relicensed.
> >>>
> >>> -- Thomas Adam
> >>
> >> If it can't be relicensed so an up-to-date version can be included in
> >> the base distribution then is there much point in it being there at all?
> >> People can simply use the package/port to install a supported version
> >> and the base distribution can simply have cwm as its main wm.
> >
> > Lots of people use the base fvwm.  Which works fine for them, even if
> > older.  Also fvwm is easier to work than cwm when you don't know either.
>
> I agree.  The fact that there's a newer version of FVWM in ports is
> fine; FVWM in base, despite being older might be a minor nuisance, but
> not insurmountable.

One thing we can do is re-do some of the useful code.

I've been playing a bit with the newer one. One thing I really would like
is for chromium (video) and fvwm to play nice with each other, namely an
implementation of the stuff that makes it possible to go fullscreen and back.

Point me in the right direction, and I will look at rewriting this under
a reasonable licence...

Reply | Threaded
Open this post in threaded view
|

Re: fvwm in base [was: "X -configure" segmentation fault]

Okan Demirmen
On Sun, Sep 15, 2013 at 4:34 PM, Marc Espie <[hidden email]> wrote:

> On Sun, Sep 15, 2013 at 08:12:53PM +0100, Thomas Adam wrote:
>> Hi,
>>
>> On 15 September 2013 11:48, Jérémie Courrèges-Anglas <[hidden email]> wrote:
>> > James Griffin <[hidden email]> writes:
>> >
>> >> * Thomas Adam <[hidden email]> [2013-09-12 10:17:56 +0100]:
>> >>
>> >>> On 12 September 2013 06:10, Carson Chittom <[hidden email]> wrote:
>> >>> > Zoran Kolic <[hidden email]> writes:
>> >>> >
>> >>> >> In fact, fvwm is in base part.
>> >>> >
>> >>> > A while ago, there was a message to misc from the fvwm developer about
>> >>> > relicensing fvwm to allow a more recent version into base.  I wonder if
>> >>> > there is any status update?
>> >>>
>> >>> That is I.  Unfortunately, FVWM cannot be relicensed.
>> >>>
>> >>> -- Thomas Adam
>> >>
>> >> If it can't be relicensed so an up-to-date version can be included in
>> >> the base distribution then is there much point in it being there at all?
>> >> People can simply use the package/port to install a supported version
>> >> and the base distribution can simply have cwm as its main wm.
>> >
>> > Lots of people use the base fvwm.  Which works fine for them, even if
>> > older.  Also fvwm is easier to work than cwm when you don't know either.
>>
>> I agree.  The fact that there's a newer version of FVWM in ports is
>> fine; FVWM in base, despite being older might be a minor nuisance, but
>> not insurmountable.
>
> One thing we can do is re-do some of the useful code.
>
> I've been playing a bit with the newer one. One thing I really would like
> is for chromium (video) and fvwm to play nice with each other, namely an
> implementation of the stuff that makes it possible to go fullscreen and back.
>
> Point me in the right direction, and I will look at rewriting this under
> a reasonable licence...

Enhanced Window Manager Hints.

Reply | Threaded
Open this post in threaded view
|

Re: fvwm in base [was: "X -configure" segmentation fault]

Thomas Adam-5
In reply to this post by Marc Espie-2
Marc,

On 15 September 2013 21:34, Marc Espie <[hidden email]> wrote:

> On Sun, Sep 15, 2013 at 08:12:53PM +0100, Thomas Adam wrote:
>> Hi,
>>
>> On 15 September 2013 11:48, Jérémie Courrèges-Anglas <[hidden email]> wrote:
>> > James Griffin <[hidden email]> writes:
>> >
>> >> * Thomas Adam <[hidden email]> [2013-09-12 10:17:56 +0100]:
>> >>
>> >>> On 12 September 2013 06:10, Carson Chittom <[hidden email]> wrote:
>> >>> > Zoran Kolic <[hidden email]> writes:
>> >>> >
>> >>> >> In fact, fvwm is in base part.
>> >>> >
>> >>> > A while ago, there was a message to misc from the fvwm developer about
>> >>> > relicensing fvwm to allow a more recent version into base.  I wonder if
>> >>> > there is any status update?
>> >>>
>> >>> That is I.  Unfortunately, FVWM cannot be relicensed.
>> >>>
>> >>> -- Thomas Adam
>> >>
>> >> If it can't be relicensed so an up-to-date version can be included in
>> >> the base distribution then is there much point in it being there at all?
>> >> People can simply use the package/port to install a supported version
>> >> and the base distribution can simply have cwm as its main wm.
>> >
>> > Lots of people use the base fvwm.  Which works fine for them, even if
>> > older.  Also fvwm is easier to work than cwm when you don't know either.
>>
>> I agree.  The fact that there's a newer version of FVWM in ports is
>> fine; FVWM in base, despite being older might be a minor nuisance, but
>> not insurmountable.
>
> One thing we can do is re-do some of the useful code.

Unfortunately, whilst this might work for very simple things, you're
on to something of a lost cause in the grander scheme of things (read:
 you might as well just write your own window manager.)

I'd dearly love to be able to relicence FVWM, but that requires
something I cannot do for a twenty year project.  It's a real shame,
but there's code added there from all sorts of proprietary companies
over the years, and contacting them in nigh impossible.

> I've been playing a bit with the newer one. One thing I really would like
> is for chromium (video) and fvwm to play nice with each other, namely an
> implementation of the stuff that makes it possible to go fullscreen and back.
>
> Point me in the right direction, and I will look at rewriting this under
> a reasonable licence...

This is where it'll go south.  You need EWMH support for this, and you
can't just pick-and-choose the best bits and shoe-horn it in to that
FVWM version at all easily.  The undertaking would be quite big.

-- Thomas Adam

12