[ANNOUNCE] xorg-server 1.7.5.901

2010-03-04 Thread Peter Hutterer
The first and likely only RC for 1.7.6 with a bunch of fixes all over the
place. This release finally brings the RECORD extension back, promised for
more-or-less every point release since 1.7.0. There's one more
record-related patch on the list that I want to get into 1.7.6 but other
than that I think we're shaping up quite nicely.

Note that the minimum requirements have changed to libselinux 2.0.86
(released before 1.7.0 came out, so that shouldn't be an issue for most of
you).

Alan Coopersmith (1):
  Solaris xf86OSRingBell() off-by-one error in filling iov[] array

Chris Dekter (1):
  Re-enable RECORD extension.

Eamon Walsh (5):
  libselinux now has a pkgconfig file.  Use it.
  xselinux: Remove reference counting calls for SID objects.
  xselinux: Allow GetWindowContext to be used for pixmaps as well.
  xselinux: Rename window-related requests that now support pixmaps.
  xselinux: Bump extension minor version.

Jeremy Huddleston (2):
  XQuartz: clang static analysis fixes
  XQuartz: Fix a possible buffer overrun in quartzAudio

Keith Packard (1):
  Allow for missing or disabled compat_output

Peter Hutterer (8):
  dix: don't update the slave coordinates from the VCK.
  Xi: assume BadMode for non-BadMatch errors returned from SetDeviceMode.
  dix: try to ring the bell even if the current device doesn't have one. 
(#24503)
  dix: remove now-erroneous comment about frozen slave devices.
  dix: Use DeliverGrabbedEvent for implicit passive grabs (#25400)
  configure: move libselinux requirement up to the common section.
  configure: move SELINUX_LIBS to XSERVER_SYS_LIBS
  xserver 1.7.5.901

Tiago Vignatti (1):
  xfree86: vgaarb: remove useless debug

git tag: xorg-server-1.7.5.901

http://xorg.freedesktop.org/archive/individual/xserver/xorg-server-1.7.5.901.tar.bz2
MD5:  d436ce2f2239c196ee163c7c047c1dd2  xorg-server-1.7.5.901.tar.bz2
SHA1: 0ac7b037f511938cc4da32fc71de7e81617790cd  xorg-server-1.7.5.901.tar.bz2

http://xorg.freedesktop.org/archive/individual/xserver/xorg-server-1.7.5.901.tar.gz
MD5:  d116b85ad1c49dea7a8f73ddf9f6c601  xorg-server-1.7.5.901.tar.gz
SHA1: 53431e10e052d4b977fb86a1273d0f7b3fccb633  xorg-server-1.7.5.901.tar.gz



pgpCTuBGymhUn.pgp
Description: PGP signature
___
xorg-announce mailing list
xorg-announce@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg-announce


Problems with pure X11 program's Fonts

2010-03-04 Thread Aaron Lewis

Hi,
 I'm trying CrossOver for Linux , it's a pure X11 Program , and i got 
an ugly UI.

 It's problem with my fonts. I know i should modify ~/.Xdefaults .

Google ain't giving much information , do anyone knows howto change X11 
defaults fonts ?


Any ideas will appreciate.

--
Best Regards,
Aaron Lewis - PGP: 0xA476D2E9
irc: A4r0n on freenode

___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


Re: Problems with pure X11 program's Fonts

2010-03-04 Thread Harald Braumann
On Thu, Mar 04, 2010 at 09:13:18PM +0800, Aaron Lewis wrote:
 Hi,
  I'm trying CrossOver for Linux , it's a pure X11 Program , and i
 got an ugly UI.
  It's problem with my fonts. I know i should modify ~/.Xdefaults .
 
 Google ain't giving much information , do anyone knows howto change
 X11 defaults fonts ?
I guess you don't mean CrossOver-Wine and you're talking about core 
fonts?

Start xfontsel and select the font, you'd like to
use. Copy the font specification and add it to your ~/.Xdefaults, like
this:
*font: -*-helvetica-*-r-*-*-12-*-*-*-*-*-*-*

Then call `xrdb -merge ~/.Xdefaults' or restart X.

This will change the default font for all good old X programmes. If you
only want to change the font for CrossOver, you'd have to do:
app*font: ...

Of course you first have to find out what app is for CrossOver. Usually
programmes that can be configured through xresources document that
somewhere.

If xfontsel doesn't show you nice fonts, you have to add more FontPath
entries to your xorg.org.

harry
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


Re: vesa driver reports many modes, but only allows a few

2010-03-04 Thread Pat Kane
  Ross Boylan r...@biostat.ucsf.edu wrote:
Program received signal SIGSEGV, Segmentation fault.
0x in ?? ()
(gdb) where
#0  0x in ?? ()
#1  0x0051a72a in DoConfigure ()
at ../../../../hw/xfree86/common/xf86Configure.c:832

The traceback says that someone branched to zero at
line 832 of hw/xfree86/common/xf86Configure.c, that
section of code (from git master) looks like this:

ConfiguredMonitor = NULL;

xf86EnableAccess(xf86Screens[dev2screen[j]]);
if ((*xf86Screens[dev2screen[j]]-PreInit)(xf86Screens[dev2screen[j]],
832: PROBE_DETECT) 
ConfiguredMonitor) {
MonitorPtr = configureDDCMonitorSection(j);
} else {
MonitorPtr = configureMonitorSection(j);
}

So it appears that the expression:
(*xf86Screens[dev2screen[j]]-PreInit)
is NULL;  it would be a good idea for that code to check
if PreInit has been filled in before jumping through it.

Can you recompile the X server with a test for NULL?

Pat
---


On Wed, Mar 3, 2010 at 6:12 PM, Ross Boylan r...@biostat.ucsf.edu wrote:
 On Wed, 2010-03-03 at 15:41 -0600, Pat Kane wrote:
 Could you run the configure under gdb to see if you get a better trace back?

     $gdb  Xorg
       :r -configure

 could be some xemu hw emulated hw weirdness...

 I also loaded some debug symbols.

 [tcsetpgrp failed in terminal_inferior: Operation not permitted]
 (++) Using config file: /root/xorg.conf.new
 (EE) open /dev/fb0: No such file or directory

 Program received signal SIGSEGV, Segmentation fault.
 0x in ?? ()
 (gdb) where
 #0  0x in ?? ()
 #1  0x0051a72a in DoConfigure ()
 at ../../../../hw/xfree86/common/xf86Configure.c:832
 #2  0x00471c17 in InitOutput (pScreenInfo=0x7d5a80, argc=value
 optimized out, argv=value optimized out)
 at ../../../../hw/xfree86/common/xf86Init.c:610
 #3  0x00425a25 in main (argc=2, argv=0x7fffe258, envp=value
 optimized out) at ../../dix/main.c:203

 Ross


 On Tue, Mar 2, 2010 at 1:04 PM, Ross Boylan r...@biostat.ucsf.edu wrote:
  On Tue, 2010-03-02 at 05:34 -0600, Pat Kane wrote:
  On Mon, Mar 1, 2010 at 2:35 PM, Ross Boylan r...@biostat.ucsf.edu wrote:
   Do I need to create a complete xorg.conf?
 
 
  The command Xorg -configure  will create one for you.
  Hooray!  With some hacking I got it working.  However, I want to report
  that Xorg -configure generated a segfault, and I'd like to improve my
  understanding of how configuration works.


___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


Re: vesa driver reports many modes, but only allows a few

2010-03-04 Thread Pat Kane
Here is an untest, not even compiled, patch to try:

diff --git a/hw/xfree86/common/xf86Configure.c
b/hw/xfree86/common/xf86Configure.c
index bce5aae..a8d8ef9 100644
--- a/hw/xfree86/common/xf86Configure.c
+++ b/hw/xfree86/common/xf86Configure.c
@@ -828,7 +828,9 @@ DoConfigure(void)
ConfiguredMonitor = NULL;

xf86EnableAccess(xf86Screens[dev2screen[j]]);
-   if ((*xf86Screens[dev2screen[j]]-PreInit)(xf86Screens[dev2screen[j]],
+
+   if ((*xf86Screens[dev2screen[j]]-PreInit) 
+   (*xf86Screens[dev2screen[j]]-PreInit)(xf86Screens[dev2screen[j]],
   PROBE_DETECT) 
ConfiguredMonitor) {
MonitorPtr = configureDDCMonitorSection(j);


Pat
---


On Thu, Mar 4, 2010 at 7:52 AM, Pat Kane pekan...@gmail.com wrote:
  Ross Boylan r...@biostat.ucsf.edu wrote:
    Program received signal SIGSEGV, Segmentation fault.
    0x in ?? ()
    (gdb) where
    #0  0x in ?? ()
    #1  0x0051a72a in DoConfigure ()
    at ../../../../hw/xfree86/common/xf86Configure.c:832

 The traceback says that someone branched to zero at
 line 832 of hw/xfree86/common/xf86Configure.c, that
 section of code (from git master) looks like this:

        ConfiguredMonitor = NULL;

        xf86EnableAccess(xf86Screens[dev2screen[j]]);
        if ((*xf86Screens[dev2screen[j]]-PreInit)(xf86Screens[dev2screen[j]],
 832:                                             PROBE_DETECT) 
            ConfiguredMonitor) {
            MonitorPtr = configureDDCMonitorSection(j);
        } else {
            MonitorPtr = configureMonitorSection(j);
        }

 So it appears that the expression:
    (*xf86Screens[dev2screen[j]]-PreInit)
 is NULL;  it would be a good idea for that code to check
 if PreInit has been filled in before jumping through it.

 Can you recompile the X server with a test for NULL?

 Pat
 ---


 On Wed, Mar 3, 2010 at 6:12 PM, Ross Boylan r...@biostat.ucsf.edu wrote:
 On Wed, 2010-03-03 at 15:41 -0600, Pat Kane wrote:
 Could you run the configure under gdb to see if you get a better trace back?

     $gdb  Xorg
       :r -configure

 could be some xemu hw emulated hw weirdness...

 I also loaded some debug symbols.

 [tcsetpgrp failed in terminal_inferior: Operation not permitted]
 (++) Using config file: /root/xorg.conf.new
 (EE) open /dev/fb0: No such file or directory

 Program received signal SIGSEGV, Segmentation fault.
 0x in ?? ()
 (gdb) where
 #0  0x in ?? ()
 #1  0x0051a72a in DoConfigure ()
 at ../../../../hw/xfree86/common/xf86Configure.c:832
 #2  0x00471c17 in InitOutput (pScreenInfo=0x7d5a80, argc=value
 optimized out, argv=value optimized out)
 at ../../../../hw/xfree86/common/xf86Init.c:610
 #3  0x00425a25 in main (argc=2, argv=0x7fffe258, envp=value
 optimized out) at ../../dix/main.c:203

 Ross


 On Tue, Mar 2, 2010 at 1:04 PM, Ross Boylan r...@biostat.ucsf.edu wrote:
  On Tue, 2010-03-02 at 05:34 -0600, Pat Kane wrote:
  On Mon, Mar 1, 2010 at 2:35 PM, Ross Boylan r...@biostat.ucsf.edu 
  wrote:
   Do I need to create a complete xorg.conf?
 
 
  The command Xorg -configure  will create one for you.
  Hooray!  With some hacking I got it working.  However, I want to report
  that Xorg -configure generated a segfault, and I'd like to improve my
  understanding of how configuration works.



___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


Re: vesa driver reports many modes, but only allows a few

2010-03-04 Thread Daniel Stone
On Thu, Mar 04, 2010 at 07:52:02AM -0600, Pat Kane wrote:
   Ross Boylan r...@biostat.ucsf.edu wrote:
 Program received signal SIGSEGV, Segmentation fault.
 0x in ?? ()
 (gdb) where
 #0  0x in ?? ()
 #1  0x0051a72a in DoConfigure ()
 at ../../../../hw/xfree86/common/xf86Configure.c:832
 
 The traceback says that someone branched to zero at
 line 832 of hw/xfree86/common/xf86Configure.c, that
 section of code (from git master) looks like this:
 
   ConfiguredMonitor = NULL;
 
   xf86EnableAccess(xf86Screens[dev2screen[j]]);
   if ((*xf86Screens[dev2screen[j]]-PreInit)(xf86Screens[dev2screen[j]],
 832:   PROBE_DETECT) 
   ConfiguredMonitor) {
   MonitorPtr = configureDDCMonitorSection(j);
   } else {
   MonitorPtr = configureMonitorSection(j);
   }
 
 So it appears that the expression:
 (*xf86Screens[dev2screen[j]]-PreInit)
 is NULL;  it would be a good idea for that code to check
 if PreInit has been filled in before jumping through it.
 
 Can you recompile the X server with a test for NULL?

Er, if pScrn-PreInit is NULL, then something's gone quite seriously
wrong and we're screwed anyway.

Cheers,
Daniel


pgpVW1K0hDoUZ.pgp
Description: PGP signature
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: Problems with pure X11 program's Fonts

2010-03-04 Thread Aaron Lewis

Dear Harry ,

Harald Braumann wrote:

On Thu, Mar 04, 2010 at 09:13:18PM +0800, Aaron Lewis wrote:
  

Hi,
 I'm trying CrossOver for Linux , it's a pure X11 Program , and i
got an ugly UI.
 It's problem with my fonts. I know i should modify ~/.Xdefaults .

Google ain't giving much information , do anyone knows howto change
X11 defaults fonts ?

I guess you don't mean CrossOver-Wine and you're talking about core 
fonts?


Start xfontsel and select the font, you'd like to
use. Copy the font specification and add it to your ~/.Xdefaults, like
this:
*font: -*-helvetica-*-r-*-*-12-*-*-*-*-*-*-*

Then call `xrdb -merge ~/.Xdefaults' or restart X.

This will change the default font for all good old X programmes. If you
only want to change the font for CrossOver, you'd have to do:
app*font: ...

Of course you first have to find out what app is for CrossOver. Usually
programmes that can be configured through xresources document that
somewhere.

If xfontsel doesn't show you nice fonts, you have to add more FontPath
entries to your xorg.org.

harry
  

I did like this :
   open xfontsel , and choose a good font , then use select to copy , 
use xrdb to reload configuration.


Still got an ugly fonts .. This time , i tried with putty , i checked 
and thought it's pure X11 program. (checked the library it linked)


My ~/.Xdefaults is in attachment .

Now , i was wondering if i made some mistakes ..
ldd of CrossOver Main UI:
   linux-gate.so.1 =  (0xe000)
   libm.so.6 = /lib/tls/i686/cmov/libm.so.6 (0x008cb000)
   libdl.so.2 = /lib/tls/i686/cmov/libdl.so.2 (0x0099e000)
   libSM.so.6 = /usr/lib/libSM.so.6 (0x004e1000)
   libICE.so.6 = /usr/lib/libICE.so.6 (0x00e63000)
   libXext.so.6 = /usr/lib/libXext.so.6 (0x0070c000)
   libX11.so.6 = /usr/lib/libX11.so.6 (0x0030a000)
   libc.so.6 = /lib/tls/i686/cmov/libc.so.6 (0x00c78000)
   /lib/ld-linux.so.2 (0x0043d000)
   libXau.so.6 = /usr/lib/libXau.so.6 (0x0011)
   libxcb-xlib.so.0 = /usr/lib/libxcb-xlib.so.0 (0x00113000)
   libxcb.so.1 = /usr/lib/libxcb.so.1 (0x00116000)
   libXdmcp.so.6 = /usr/lib/libXdmcp.so.6 (0x00e5d000)

ldd of putty:
% ldd `which putty`
   linux-gate.so.1 =  (0xe000)
   libgtk-1.2.so.0 = /usr/lib/libgtk-1.2.so.0 (0x00232000)
   libgdk-1.2.so.0 = /usr/lib/libgdk-1.2.so.0 (0x00575000)
   libgmodule-1.2.so.0 = /usr/lib/libgmodule-1.2.so.0 (0x00c6)
   libglib-1.2.so.0 = /usr/lib/libglib-1.2.so.0 (0x0064c000)
   libdl.so.2 = /lib/tls/i686/cmov/libdl.so.2 (0x00a7d000)
   libXi.so.6 = /usr/lib/libXi.so.6 (0x005c4000)
   libXext.so.6 = /usr/lib/libXext.so.6 (0x00941000)
   libX11.so.6 = /usr/lib/libX11.so.6 (0x00de9000)
   libm.so.6 = /lib/tls/i686/cmov/libm.so.6 (0x00728000)
   libc.so.6 = /lib/tls/i686/cmov/libc.so.6 (0x00c85000)
   /lib/ld-linux.so.2 (0x00412000)
   libXau.so.6 = /usr/lib/libXau.so.6 (0x0054)
   libxcb-xlib.so.0 = /usr/lib/libxcb-xlib.so.0 (0x005d7000)
   libxcb.so.1 = /usr/lib/libxcb.so.1 (0x0011)
   libXdmcp.so.6 = /usr/lib/libXdmcp.so.6 (0x008e7000)

My Gtk (2.0+) Program has a good UI , everything fine .
If it's problem with gtk1's rc file , i would make mistakes.

--
Best Regards,
Aaron Lewis - PGP: 0xA476D2E9
irc: A4r0n on freenode

*font: -misc-vera sans yuanti mono-*-r-*-10-*-*-*-*-*-*-*-*

! Xcursor 

 Xcursor.theme: LSD
 Xcursor.size:  22

! Xft settings ---

Xft.dpi:96
Xft.antialias:  true
Xft.rgba:   rgb
Xft.hinting:true
Xft.hintstyle:  hintslight

xft.antialias:true


___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: Problems with pure X11 program's Fonts

2010-03-04 Thread Aaron Lewis

Well Harry , here's more information:

I tried to use strace to detect what the hell it reads from my disk.

CrossOver Main UI doesn't seems to read .Xdefaults , but like what Putty 
does.


Putty tends to read ~/.Xdefaults-HOSTNAME , so i linked it , still ugly 
fonts.  ;-(


___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


Re: Problems with pure X11 program's Fonts

2010-03-04 Thread Harald Braumann
On Thu, Mar 04, 2010 at 10:11:04PM +0800, Aaron Lewis wrote:
 harry
 I did like this :
open xfontsel , and choose a good font , then use select to
 copy , use xrdb to reload configuration.
 
 Still got an ugly fonts .. This time , i tried with putty , i
 checked and thought it's pure X11 program. (checked the library it
 linked)

Probably the font doesn't get anti-aliased. While some prefer the
`crisp' look of this, others find it ugly.

Did the setting change anything at all? Try with a font that looks
very different, so you see if the setting has any effect. Maybe that
programme doesn't use xresources for configuration.

 My Gtk (2.0+) Program has a good UI , everything fine .
 If it's problem with gtk1's rc file , i would make mistakes.

GTK2 uses a completely different system (fontconfig + freetype). 
GTK1 still uses core fonts, if I'm not mistaken (haven't got it around
anymore). And AFAIK it also doesn't do anti-aliasing. I think that
this might be your main problem.

I, too, spent a lot of time trying to get nice fonts in the old
system. But this is a Don Quichottesque task. Unlike Don Quichotte,
however, I gave up at some point and just accepted my defeat.
Nowadays everything supports nice fonts, including xterm and TK, 
and I don't have any gtk1 apps. So for me the problem disappeared.

harry
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


Re: xrandr and external touchscreen on notebook

2010-03-04 Thread Wolfgang Rohdewald
am I asking for something impossible or was my question
too trivial to answer? Either way, please tell me!

On Saturday 13 February 2010, Wolfgang Rohdewald wrote:
 Hi,
 
 I can make the external touchscreen work with this:
 
 xrandr --output LVDS1 --right-of DVI1
 which gives me 1920x1080 on DVI1 and 1920x1200 on the
 notebook.
 
 Now the touchscreen moves the mouse relative to the entire
 virtual screen (3840x1200). How can I restrict the touchscreen
 inputdevice to the external monitor?
 
 I believe it should work with xorg.conf (see below) entry but
 it seems that xrandr ignores this.
 
 I am running kubuntu 9.10 with backported KDE 4.4
 X.Org X Server 1.6.4
 
 r...@notebook:/etc/X11# cat xorg.conf
 
 Section ServerFlags
 Option  DontZap   True
 EndSection
 
 Section InputDevice
 Identifier Acer T230H
 Driver evdev
 Option Device
 /dev/input/by-id/usb-Acer_T230H-event-if00 Option
 Calibration 0 1920 0 1080
 EndSection
 
 Section ServerLayout
 Identifier Touchscreen
 InputDevice Acer T230H SendCoreEvents
 EndSection
 
 notebook:~$ xrandr -q
 Screen 0: minimum 320 x 200, current 3840 x 1200, maximum 4096
 x 4096 VGA1 disconnected (normal left inverted right x axis y
 axis) LVDS1 connected 1920x1200+1920+0 (normal left inverted
 right x axis y axis) 367mm x 230mm
1920x1200  60.0*+
1600x1200  60.0
1680x1050  60.0
1600x1024  60.2
1400x1050  60.0
1280x1024  60.0
1440x900   59.9
1280x960   60.0
1360x768   59.8
1152x864   60.0
1024x768   60.0
800x60060.3
640x48059.9
 DVI1 connected 1920x1080+0+0 (normal left inverted right x
 axis y axis) 443mm x 249mm
1920x1080  60.0*+
1024x768   70.1 60.0
800x60060.3 56.2
640x48066.7 60.0
720x40070.1
 TV1 disconnected (normal left inverted right x axis y axis)


-- 
Wolfgang
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


Re: X doesn't start in minilinux

2010-03-04 Thread GreenFlash
Isn't there somebody who wants to help me??

GreenFlash schrieb:
 Hi guys,

 I'm building a minilinux for our library at my
 university. It has to
 have also a browser with flash, so I need a Xserver.
 The whole system is build of an ubuntu distro. I
 only copied the files I
 need from my distro to the sourcefolder of the
 miniimage, then make it
 to an image and boot the virtual maschine by pxe.
 So it is possible,
 that I missed a file or forgot a option in the
 kernel or something like
 that for the xserver.
 The server shall use vesa for the first time, but
 I'm not able to get it
 to work. Any ideas why it isn't able to find a
 screen? The latest
 XFree86 server did work on this maschine.

 Here's the log from /var/log/Xorg.0.log:



 _XSERVTransSocketOpenCOTSServer: Unable to open
 socket for inet6
 _XSERVTransOpen: transport open failed for
 inet6/(none):0
 _XSERVTransMakeAllCOTSServerListeners: failed to
 open listener for inet6

 X.Org X Server 1.6.4
 Release Date: 2009-9-27
 X Protocol Version 11, Revision 0
 Build Operating System: Linux 2.6.24-23-server
 i686 Ubuntu
 Current Operating System: Linux (none) 2.6.31.1 #9
 Wed Mar 3 21:15:10
 CET 2010 i686
 Kernel command line:
 BOOT_IMAGE=bibotestkernel.image root=/dev/ram
 initrd=bibotestinitrd.gz
 Build Date: 14 November 2009  05:48:26PM
 xorg-server 2:1.6.4-2ubuntu4.1 (buildd@)
 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: Wed
 Mar  3 22:32:55 2010
 (==) Using config file: /etc/X11/xorg.conf
 (==) ServerLayout Default Layout
 (**) |--Screen Default Screen (0)
 (**) |   |--Monitor TFT
 (**) |   |--Device VIA
 (**) |--Input Device PS2 Mouse
 (**) |--Input Device PS2 Keyboard 
 (**) Option BlankTime 0
 (**) Option StandbyTime 0
 (**) Option SuspendTime 0
 (**) Option OffTime 0
 (==) Automatically adding devices
 (==) Automatically enabling devices
 (WW) The directory /usr/lib/X11/fonts/misc does
 not exist.
 Entry deleted from font path.
 (WW) The directory /usr/share/fonts/X11/misc
 does not exist.
 Entry deleted from font path.
 (WW) The directory /usr/share/fonts/X11/cyrillic
 does not exist.
 Entry deleted from font path.
 (WW) The directory /usr/share/fonts/X11/100dpi/
 does not exist.
 Entry deleted from font path.
 (WW) The directory /usr/share/fonts/X11/75dpi/
 does not exist.
 Entry deleted from font path.
 (WW) The directory /usr/share/fonts/X11/Type1
 does not exist.
 Entry deleted from font path.
 (WW) The directory /usr/share/fonts/X11/100dpi
 does not exist.
 Entry deleted from font path.
 (WW) The directory /usr/share/fonts/X11/75dpi
 does not exist.
 Entry deleted from font path.
 (WW) The directory
 /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType
 does not exist.
 Entry deleted from font path.
 (**) FontPath set to:
 built-ins
 (==) ModulePath set to /usr/lib/xorg/modules
 (WW) AllowEmptyInput is on, devices using drivers
 'kbd', 'mouse' or
 'vmmouse' will be disabled.
 (WW) Disabling PS2 Mouse
 (II) Loader magic: 0x3bc0
 (II) Module ABI versions:
 X.Org ANSI C Emulation: 0.4
 X.Org Video Driver: 5.0
 X.Org XInput driver : 4.0
 X.Org Server Extension : 2.0
 (II) Loader running on linux
 (--) using VT number 2

 (WW) Open ACPI failed (/var/run/acpid.socket) (No
 such file or directory)
 (II) No APM support in BIOS or kernel
 (II) System resource ranges:
 (II) extmod will be loaded by default.
 (II) dbe will be loaded. This was enabled by
 default and also
 specified in the config file.
 (II) glx will be loaded. This was enabled by
 default and also
 specified in the config file.
 (II) record will be loaded by default.
 (II) dri will be loaded by default.
 (II) dri2 will be loaded by default.
 (II) LoadModule: dbe
 (II) Loading
 /usr/lib/xorg/modules/extensions//libdbe.so
 (II) Module dbe: vendor=X.Org Foundation
 compiled for 1.6.4, module version = 1.0.0
 Module class: X.Org Server Extension
 ABI class: X.Org Server Extension, version 2.0
 (II) Loading extension DOUBLE-BUFFER
 (II) LoadModule: glx
 (II) Loading
 /usr/lib/xorg/modules/extensions//libglx.so
 (II) Module glx: vendor=X.Org Foundation
 compiled for 1.6.4, module version = 1.0.0
 ABI class: X.Org Server Extension, version 2.0
 (==) AIGLX enabled
 (II) Loading extension GLX
 (II) LoadModule: extmod
 (II) Loading
 /usr/lib/xorg/modules/extensions//libextmod.so
 (II) Module extmod: vendor=X.Org Foundation
 compiled for 1.6.4, module version = 1.0.0
 Module class: X.Org Server Extension
 ABI class: X.Org Server Extension, version 2.0
 (II) Loading extension MIT-SCREEN-SAVER
 (II) Loading extension XFree86-VidModeExtension
 (II) Loading extension XFree86-DGA
 (II) Loading extension DPMS
 

Re: X doesn't start in minilinux

2010-03-04 Thread Jay Cotton

On 03/04/10 10:25, GreenFlash wrote:

alling back to old probe method for vesa
   
Well, according to the log the vesa driver did not find a graphics 
device. So, PCI bus code
could be missing, all the connecting logic for that must be present.  
There may also be a
driver like xsvc or its equivalent that is needed.  Not sure about linux 
in that way.


I notice that all the fonts are missing, that may be o.k. on newest 
versions of X, your

version is rather stale.

You may want to start the server with an option to ignore networking.  
see if that clears the

warnings.


The root cause seems to be that the server can't find a video chip.  The 
probe code is a good place

to start looking.

jc

___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


Re: X doesn't start in minilinux

2010-03-04 Thread GreenFlash
thx, that somebody helps me. Here's the device-Section from my xorg.conf:

Section Device
Identifier  VIA
Driver  vesa
BusID   PCI:0:2:0
EndSection

And the corresponding line from lspci:

00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH
VirtualBox Graphics Adapter

I also just realised, that there are some version differences in the
xserver and the vesa module. The module is compiled for version 1.6.3,
but the server has version 1.6.4.
Might this cause the problem?
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


Re: to neomagic users and devels

2010-03-04 Thread Risto Suominen
I've installed Debian Lenny on a Fujitsu B110 mini notebook, probably
quite similar to yours internally, and it is quite slow, indeed.

I also have Neomagic on a Dell Latitude CPi 300 MHz P2 with
VectorLinux 5.0. I don't remember any unusual slowness with that one.
Older X? Just a thought...

Risto
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


[ANNOUNCE] xf86-input-penmount 1.4.1

2010-03-04 Thread Julien Cristau
This release brings compatibility with xserver 1.7.x, and adds a new
InvertX option.

Alan Coopersmith (1):
  Fill in COPYING file, add SubmittingPatches URL to README

Julien Cristau (3):
  Janitorial configure.ac/Makefile.am updates
  Don't use obsolete loader functions
  Bump to 1.4.1

Peter Hutterer (1):
  Cope with XINPUT ABI 7.

Steve Bian (1):
  Added InvertX option

git tag: xf86-input-penmount-1.4.1

http://xorg.freedesktop.org/archive/individual/driver/xf86-input-penmount-1.4.1.tar.bz2
MD5:  e5984e43ce31d45659eb6ee91c02aba5  xf86-input-penmount-1.4.1.tar.bz2
SHA1: a6923fe92ffbc698813063a5426b4ba2edfe465f  
xf86-input-penmount-1.4.1.tar.bz2

http://xorg.freedesktop.org/archive/individual/driver/xf86-input-penmount-1.4.1.tar.gz
MD5:  30ba29fac73d0879d6a01dacf9acd946  xf86-input-penmount-1.4.1.tar.gz
SHA1: b06c8583999c370bca304571c940025ea5cf29bb  xf86-input-penmount-1.4.1.tar.gz



signature.asc
Description: Digital signature
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: How to configure a serial mouse

2010-03-04 Thread Risto Suominen
I'm not sure about this, I have only done this on Debian Lenny, but I
have not heard that xorg.conf had disappeared.

So I think that you can run X -configure (as root) and xorg.conf will
be created. Then you can edit the mouse protocol, as before.

Risto
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


Re: Problems with pure X11 program's Fonts

2010-03-04 Thread Glynn Clements

Aaron Lewis wrote:

 open xfontsel , and choose a good font , then use select to copy , 
 use xrdb to reload configuration.
 
 Still got an ugly fonts .. This time , i tried with putty , i checked 
 and thought it's pure X11 program. (checked the library it linked)
 
 My ~/.Xdefaults is in attachment .
 
 Now , i was wondering if i made some mistakes ..
 ldd of CrossOver Main UI:
 linux-gate.so.1 =  (0xe000)
 libm.so.6 = /lib/tls/i686/cmov/libm.so.6 (0x008cb000)
 libdl.so.2 = /lib/tls/i686/cmov/libdl.so.2 (0x0099e000)
 libSM.so.6 = /usr/lib/libSM.so.6 (0x004e1000)
 libICE.so.6 = /usr/lib/libICE.so.6 (0x00e63000)
 libXext.so.6 = /usr/lib/libXext.so.6 (0x0070c000)
 libX11.so.6 = /usr/lib/libX11.so.6 (0x0030a000)
 libc.so.6 = /lib/tls/i686/cmov/libc.so.6 (0x00c78000)
 /lib/ld-linux.so.2 (0x0043d000)
 libXau.so.6 = /usr/lib/libXau.so.6 (0x0011)
 libxcb-xlib.so.0 = /usr/lib/libxcb-xlib.so.0 (0x00113000)
 libxcb.so.1 = /usr/lib/libxcb.so.1 (0x00116000)
 libXdmcp.so.6 = /usr/lib/libXdmcp.so.6 (0x00e5d000)

Xt-based toolkits use X resources for configuration, but CrossOver
doesn't appear to be using such a toolkit. Other toolkits *might* use
X resources, or they might not.

Assuming that CrossOver is the Windows emulation software based upon
Wine and formerly known as CrossOver Office, I wouldn't expect it to
support configuration via X resources. I suggest that you refer to the
CrossOver documentation for guidance.

-- 
Glynn Clements gl...@gclements.plus.com
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


Re: X doesn't start in minilinux

2010-03-04 Thread Jay Cotton

On 03/04/10 11:28, GreenFlash wrote:

thx, that somebody helps me. Here's the device-Section from my xorg.conf:

Section Device
 Identifier  VIA
 Driver  vesa
 BusID   PCI:0:2:0
EndSection

And the corresponding line from lspci:

00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH
VirtualBox Graphics Adapter

I also just realised, that there are some version differences in the
xserver and the vesa module. The module is compiled for version 1.6.3,
but the server has version 1.6.4.
Might this cause the problem?
   


YES.   ABI is important to Xorg now.

jc

___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
   


___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


Re: X doesn't start in minilinux

2010-03-04 Thread GreenFlash

 I also just realised, that there are some version differences in the
 xserver and the vesa module. The module is compiled for version 1.6.3,
 but the server has version 1.6.4.
 Might this cause the problem?


 YES.   ABI is important to Xorg now.
Compiled the vesa driver again for the 1.6.4 server, but it still tells
me, that it is compiled for server 1.6.3. So I would like to say, that
this isn't the problem, why the Xserver can't find the graphic card.
What about HAL? Is this important for the graphic card? What do I need
for hal to work?
Are there any other things I can do, to detect the error, except
debugging the vesa module? Because I don't have a debugger in the minilinux.

Sam
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


Re: X doesn't start in minilinux

2010-03-04 Thread Alan Coopersmith


GreenFlash wrote:
 What about HAL? Is this important for the graphic card? 

No.  HAL is used by Xorg only for input devices (mouse, keyboard, tablet, etc.),
not output devices (video cards  monitors).

-- 
-Alan Coopersmith-   alan.coopersm...@sun.com
 Oracle Solaris Platform Engineering: X Window System

___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


Re: X doesn't start in minilinux

2010-03-04 Thread Jay Cotton

On 03/04/10 15:20, GreenFlash wrote:
   

I also just realised, that there are some version differences in the
xserver and the vesa module. The module is compiled for version 1.6.3,
but the server has version 1.6.4.
Might this cause the problem?

   

YES.   ABI is important to Xorg now.
 

Compiled the vesa driver again for the 1.6.4 server, but it still tells
me, that it is compiled for server 1.6.3. So I would like to say, that
this isn't the problem, why the Xserver can't find the graphic card.
What about HAL? Is this important for the graphic card? What do I need
for hal to work?
Are there any other things I can do, to detect the error, except
debugging the vesa module? Because I don't have a debugger in the minilinux.

Sam
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
   

in the vesa.c file:

#ifdef XSERVER_LIBPCIACCESS
^  this implies there may be a lib you need.  check 
for that

static Bool
VESAPciProbe(DriverPtr drv, int entity_num, struct pci_device *dev,
 intptr_t match_data)
{
ScrnInfoPtr pScrn;

pScrn = xf86ConfigPciEntity(NULL, 0, entity_num, NULL,
NULL, NULL, NULL, NULL, NULL);
if (pScrn != NULL) {
VESAPtr pVesa = VESAGetRec(pScrn);

VESAInitScrn(pScrn);
pVesa-pciInfo = dev;
}

return (pScrn != NULL);
}
#endif

static Bool
VESAProbe(DriverPtr drv, int flags)

___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


Re: X doesn't start in minilinux

2010-03-04 Thread Dan Nicholson
On Thu, Mar 4, 2010 at 12:52 PM, Jay Cotton jay.cot...@sun.com wrote:
 On 03/04/10 11:28, GreenFlash wrote:

 thx, that somebody helps me. Here's the device-Section from my xorg.conf:

 Section Device
         Identifier      VIA
         Driver          vesa
         BusID           PCI:0:2:0
 EndSection

 And the corresponding line from lspci:

 00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH
 VirtualBox Graphics Adapter

 I also just realised, that there are some version differences in the
 xserver and the vesa module. The module is compiled for version 1.6.3,
 but the server has version 1.6.4.
 Might this cause the problem?


 YES.   ABI is important to Xorg now.

Xorg does usually maintain ABI through a minor release series. So, a
1.6.x driver should work with a 1.6.y server without recompiling.

--
Dan
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: How to configure a serial mouse

2010-03-04 Thread steffen

 I'm not sure about this, I have only done this on Debian Lenny, but I
 have not heard that xorg.conf had disappeared.
 
 So I think that you can run X -configure (as root) and xorg.conf will
 be created. Then you can edit the mouse protocol, as before.
 
 Risto

I think what Risto said is correct, but even easier - as far as I
understand X, which admittedly is not that much - it should be possible to
simply create /etc/X11/xorg.conf with only the sections relevant to your
mouse. That way you can use the goodness of X automagical configuration
for
everything, except the mouse where it's obviously not working.

Cheers, Steffen
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


Re: How to configure a serial mouse

2010-03-04 Thread Peter Hutterer
On Fri, Mar 05, 2010 at 02:32:38AM +0200, stef...@schaumburger.info wrote:
 
  I'm not sure about this, I have only done this on Debian Lenny, but I
  have not heard that xorg.conf had disappeared.
  
  So I think that you can run X -configure (as root) and xorg.conf will
  be created. Then you can edit the mouse protocol, as before.
  
  Risto
 
 I think what Risto said is correct, but even easier - as far as I
 understand X, which admittedly is not that much - it should be possible to
 simply create /etc/X11/xorg.conf with only the sections relevant to your
 mouse. That way you can use the goodness of X automagical configuration
 for
 everything, except the mouse where it's obviously not working.

the hotplugging code takes over and ignores any mouse driver settings in the
configuration. You'd need to disable hotplugging as well to make the mouse
section actually take effect.

Section ServerFlags
Option AutoAddDevices off
EndSection

Cheers,
  Peter
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


X (from CentOS 5) crashes on Lenovo T61 laptop when I try to change screen resolution or set up external monitor

2010-03-04 Thread Aleksey Tsalolikhin
Hi.  Xorg 7.1.1 (from CentOS 5.4)  crashes when I bring up the Display or
Screen Resolution control panels -- this is on a Lenovo ThinkPad T61.

I am trying to configure an extended desktop using the laptop screen and
an external monitor connected through the docking station - right now I get
a duplicate image and the external monitor is at a very low resolution.

I am including my Xorg.log, could somebody help me sort
this out, please, or point me in the right direction?

I do see this:

(WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found

(--) PCI:*(0:2:0) Intel Corporation unknown chipset (0x2a02) rev 12,
Mem @ 0xf810/20, 0xe000/28, I/O @ 0x1800/3
(--) PCI: (0:2:1) Intel Corporation unknown chipset (0x2a03) rev 12,
Mem @ 0xf820/20

So I thought I might need a special video driver.

http://www.linlap.com/wiki/ibm-lenovo+thinkpad+t61  says
the T61 laptop graphics should work OK with recent Linux distros.

I tried the xorg.conf mod in
http://www.thinkwiki.org/wiki/Installing_Fedora_8_on_a_T61#Graphics
but X crashes when I run xrandr.  (Fedora 8 is the closest thing
I could find to CentOS 5 when googling this issue.)

I went on the vendor website but there was no driver available except for
an NVIDIA driver for SUSE, but  (a) my laptop does not have an NVIDIA device,
and (b) I am running CentOS.

Help?

Thanks,
-at

P.S. xorg.conf included as well:

Section ServerLayout
Identifier Default Layout
Screen  0  Screen0 0 0
InputDeviceKeyboard0 CoreKeyboard
InputDeviceSynaptics CorePointer
EndSection

Section InputDevice
Identifier  Keyboard0
Driver  kbd
Option  XkbModel pc105
Option  XkbLayout us
EndSection

Section InputDevice
Identifier  Synaptics
Driver  synaptics
Option  Device /dev/input/mice
Option  Protocol auto-dev
Option  Emulate3Buttons yes
EndSection

Section Device
Identifier  Videocard0
Driver  intel
EndSection

Section Screen
Identifier Screen0
Device Videocard0
DefaultDepth 24
SubSection Display
Viewport   0 0
Depth 24
EndSubSection
EndSection
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


Re: Problems with pure X11 program's Fonts

2010-03-04 Thread Aaron Lewis
Glynn Clements wrote:
 Aaron Lewis wrote:

 open xfontsel , and choose a good font , then use select to copy ,
 use xrdb to reload configuration.

 Still got an ugly fonts .. This time , i tried with putty , i checked
 and thought it's pure X11 program. (checked the library it linked)

 My ~/.Xdefaults is in attachment .

 Now , i was wondering if i made some mistakes ..
 ldd of CrossOver Main UI:
 linux-gate.so.1 =  (0xe000)
 libm.so.6 = /lib/tls/i686/cmov/libm.so.6 (0x008cb000)
 libdl.so.2 = /lib/tls/i686/cmov/libdl.so.2 (0x0099e000)
 libSM.so.6 = /usr/lib/libSM.so.6 (0x004e1000)
 libICE.so.6 = /usr/lib/libICE.so.6 (0x00e63000)
 libXext.so.6 = /usr/lib/libXext.so.6 (0x0070c000)
 libX11.so.6 = /usr/lib/libX11.so.6 (0x0030a000)
 libc.so.6 = /lib/tls/i686/cmov/libc.so.6 (0x00c78000)
 /lib/ld-linux.so.2 (0x0043d000)
 libXau.so.6 = /usr/lib/libXau.so.6 (0x0011)
 libxcb-xlib.so.0 = /usr/lib/libxcb-xlib.so.0 (0x00113000)
 libxcb.so.1 = /usr/lib/libxcb.so.1 (0x00116000)
 libXdmcp.so.6 = /usr/lib/libXdmcp.so.6 (0x00e5d000)

 Xt-based toolkits use X resources for configuration, but CrossOver
 doesn't appear to be using such a toolkit. Other toolkits *might* use
 X resources, or they might not.

 Assuming that CrossOver is the Windows emulation software based upon
 Wine and formerly known as CrossOver Office, I wouldn't expect it to
 support configuration via X resources. I suggest that you refer to the
 CrossOver documentation for guidance.

Thanks , Glynn . strace told me it reads ~/.Xdefaults-HOSTNAME
And i already sent Codeweavers a mail talking about this , but there's
no response yet.

I tried CentOS on VMware , it has a normal font view , not so bad as
my OS ,

I'm using KDE3 ,  maybe there's some misconfigurations , i'll create a
new user to test it.

-- 
Best Regards,
Aaron Lewis - PGP: 0xA476D2E9
irc: A4r0n on freenode

___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


Re: Problems with pure X11 program's Fonts

2010-03-04 Thread Glynn Clements

Aaron Lewis wrote:

  Assuming that CrossOver is the Windows emulation software based upon
  Wine and formerly known as CrossOver Office, I wouldn't expect it to
  support configuration via X resources. I suggest that you refer to the
  CrossOver documentation for guidance.
 
 Thanks , Glynn . strace told me it reads ~/.Xdefaults-HOSTNAME

In which case, it may be reading *some* configuration information via
X resources, or it may just be a particular library which does so
(it's linked against libdl, so I don't know which other libraries it
may be loading dynamically).

Conventionally, X resources are read from the file specified by
$XENVIRONMENT, or ~/.Xdefaults-hostname if that variable is not set,
and also read from the RESOURCE_MANAGER property on the root window,
or from ~/.Xdefaults if the property doesn't exist.

xrdb sets the RESOURCE_MANAGER property, so if you've used xrdb, the
~/.Xdefaults file won't be read. You can use xprop -root will list
any properties on the root window.

Conventionally, fonts are specified by font, fontSet and/or fontList
resources. Athena uses fontSet if the international resource is True
and font otherwise, while Motif uses fontList. Xt-based programs which
have had Xft support added (e.g. xterm) tend to use faceName and
faceSize.

Having said all that, there's no guarantee that CrossOver's font
configuration is influenced by X resources in any way.

-- 
Glynn Clements gl...@gclements.plus.com
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


Re: to neomagic users and devels

2010-03-04 Thread Piotr Gluszenia Slawinski

i've had a peek into source, and it seems that there is
problem with ImageWrite and colour expansion...

runnin x11perf is quite interesting, it seems this chipset is
not so dead slow, and many modes are quite quick...
except the ones which are not ;)


ad. older X - as there is no accel of i.e. ImageWrite ,
it is done by software, and i think such 'software' functions
got somehow broken recently.
afterall painting just 16x16 pix cursor in gimp should not
be so slow, even without acceleration at all on pentium...
such things could be performed on zx-spectrum lightning fast...



--

On Thu, 4 Mar 2010, Risto Suominen wrote:


I've installed Debian Lenny on a Fujitsu B110 mini notebook, probably
quite similar to yours internally, and it is quite slow, indeed.

I also have Neomagic on a Dell Latitude CPi 300 MHz P2 with
VectorLinux 5.0. I don't remember any unusual slowness with that one.
Older X? Just a thought...

Risto
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg


___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg