Re: X -configure segmentation fault
On Tue, Sep 10, 2013 at 10:18:43PM +, 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
Re: X -configure segmentation fault
On 9/10/13, Martin Brandenburg mar...@martinbrandenburg.com wrote: On Tue, Sep 10, 2013 at 10:18:43PM +, 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.ga12...@nebraska.herrb.net - 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).
Re: X -configure segmentation fault
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
Re: X -configure segmentation fault
On Wed, Sep 11, 2013 at 10:37 AM, Heptas Torres hepta...@gmail.com wrote: On 9/10/13, Martin Brandenburg mar...@martinbrandenburg.com wrote: On Tue, Sep 10, 2013 at 10:18:43PM +, 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/
Re: X -configure segmentation fault
On 9/11/13, David Coppa dco...@gmail.com wrote: On Wed, Sep 11, 2013 at 10:37 AM, Heptas Torres hepta...@gmail.com wrote: On 9/10/13, Martin Brandenburg mar...@martinbrandenburg.com wrote: On Tue, Sep 10, 2013 at 10:18:43PM +, 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
Re: X -configure segmentation fault
On Wed, Sep 11, 2013 at 11:15 AM, Heptas Torres hepta...@gmail.com 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.
Re: X -configure segmentation fault
On Wed, Sep 11, 2013 at 09:15:57AM +, Heptas Torres wrote: On 9/11/13, David Coppa dco...@gmail.com wrote: On Wed, Sep 11, 2013 at 10:37 AM, Heptas Torres hepta...@gmail.com wrote: On 9/10/13, Martin Brandenburg mar...@martinbrandenburg.com wrote: On Tue, Sep 10, 2013 at 10:18:43PM +, 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
Re: X -configure segmentation fault
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
Re: X -configure segmentation fault
Heptas Torres hepta...@gmail.com 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.)
Re: X -configure segmentation fault
On Tue, Sep 10, 2013 at 10:18:43PM +, 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.ga12...@nebraska.herrb.net - 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).
Re: X -configure -- Segmentation fault at address 0x28
On May 10, 2013, at 9:56 AM, Stefan Olsson stefan.karl.ols...@gmail.com wrote: Hello, When I use startx things works quite well with X-windows, but since I want a multihead config I tried to run X -configure. That configuration doesn't get very far though, it lists the available graphics drivers and then chokes and gives Segmentation fault at address 0x28. -The config that is created is very basic but I note that it has entries for both intel and vesa. -What can I do to get a more useful xorg.conf? Prevent the segmentation fault? Since you have an intel gpu, and if all you need is simple multihead (i.e. multiple monitors on one gpu), I'd advise you to forget xorg.conf and take a look at xrandr. Search the archives, there was a thread on this, recently.
Re: X -configure -- Segmentation fault at address 0x28
2013/5/10 Stefan Olsson stefan.karl.ols...@gmail.com When I use startx things works quite well with X-windows, but since I want Long time since I saw one of these knee-jerk reactions: The X.Org Foundation requests that the following names be used when referring to this software: X X Window System X Version 11 X Window System, Version 11 X11 =)
