Re: DRAFT [was: Re: Fabio, please summarize the future thread :)]
On Sat, 21 Aug 2004, Branden Robinson wrote: On Sun, Aug 15, 2004 at 12:27:05PM +0200, Fabio Massimo Di Nitto wrote: Here is a draft. I kept it simple for global understanding, but guys feel free to destroy it if you think it is not good enough. Looks great. I'll do the usual en_IT to en_US translation that I usually do. ;-) I'll queue it up for committing. Thanks :-) I only received a comment in private regarding a sentence not completly clear but i am sure the itaglish - english translation will do :-) Fabio -- user fajita: step one fajita Whatever the problem, step one is always to look in the error log. user fajita: step two fajita When in danger or in doubt, step two is to scream and shout.
Bug#267062: xlibs: [xkb] wrong Compose file for pl_PL.UTF-8?
Hello. Branden Robinson: Hmm, according to compose.dir, pl_PL.UTF-8 *should* be using the en_US.UTF-8 compose map. Yes, it should. The catch is it doesn't. The interesting thing is, when I overwrite /usr/X11R6/lib/X11/locale/iso8859-2/Compose with /usr/X11R6/lib/X11/locale/en_US.UTF-8/Compose nothing changes. I'm a bit confused. I'm using LC_CTYPE=en_US.UTF-8 myself, and getting the en_US.UTF-8 compose map. Can you compose UTF-8-only characters (as opposed to ISO-8859-1-compatible) as well? Can you use Multi_key percent o : ‰ U2030 # PER MILLE SIGN I tried running X (GNOME) with Option XkbLayout en and locale en_US.UTF-8, but I still can input ą (aogonek) with Multi_key a comma and can't, for example, get the above-mentioned per mille sign. Except that it doesn't seem to work at all in bash. However, I can compose characters into the Mozilla location bar just fine. Weird. Mozilla location bar is a different beast altogether - when typing Multi_key minus minus nothing happens, then when I press the third minus a minus appears, and in the drop-down I can see the option to Search for --, with two minuses. Multi_key minus minus period produces a period. Also, I can't get the UTF-8-specific per mille sign, while easily getting the Multi_key a comma (which is not present in the en_US.UTF-8/Compose map). I don't think Mozilla's location bar is a good testing-area (Galeon's location bar acts the same as bash inside gnome-terminal, i.e. seems to use iso8859-2/Compose). Cheers, -- Shot (Piotr Szotkowski) -- SCO is the thief who puts a gun to his own head and says give me your money or I'll shoot. ~~~ Bruce Perens, /. ~~~ http://shot.pl/hovercraft/
Processed: Re: Bug#266336: xterm changes meta-X to meta-8 in en_US.UTF-8 locale
Processing commands for [EMAIL PROTECTED]: reassign 266336 emacs21 Bug#266336: xterm changes meta-X to meta-8 in en_US.UTF-8 locale Bug reassigned from package `xterm' to `emacs21'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: Bug#265084: Not critical
On Sat, Aug 21, 2004 at 03:54:42PM +0200, Thomas Hood wrote: According to my understanding of the severity levels, the fact that X doesn't work on one system doesn't count as a critical bug. That's correct. Thanks for helping with the triage. -- G. Branden Robinson|For every credibility gap, there is Debian GNU/Linux |a gullibility fill. [EMAIL PROTECTED] |-- Richard Clopton http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Bug#267085: marked as done (xbase-clients: preinst script accessing xinitrc causes syntax error)
Your message dated Mon, 23 Aug 2004 04:03:52 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#267085: xbase-clients: preinst script accessing xinitrc causes syntax error has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 20 Aug 2004 16:09:11 + From [EMAIL PROTECTED] Fri Aug 20 09:09:11 2004 Return-path: [EMAIL PROTECTED] Received: from pop.gmx.net (mail.gmx.net) [213.165.64.20] by spohr.debian.org with smtp (Exim 3.35 1 (Debian)) id 1ByBx1-0001b9-00; Fri, 20 Aug 2004 09:09:11 -0700 Received: (qmail 12165 invoked by uid 65534); 20 Aug 2004 16:08:39 - Received: from p548003AC.dip.t-dialin.net (EHLO dione.myth.net) (84.128.3.172) by mail.gmx.net (mp010) with SMTP; 20 Aug 2004 18:08:39 +0200 X-Authenticated: #13979910 Received: from dione.myth.net ([EMAIL PROTECTED] [127.0.0.1]) by dione.myth.net (8.12.11.Beta0/8.12.11.Beta0/Debian-1) with ESMTP id i7KG8WvD014383; Fri, 20 Aug 2004 18:08:32 +0200 Received: (from [EMAIL PROTECTED]) by dione.myth.net (8.12.11.Beta0/8.12.11.Beta0/Debian-1) id i7KG8Wxt014381; Fri, 20 Aug 2004 18:08:32 +0200 Message-Id: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Alexis Huxley [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: xbase-clients: preinst script accessing xinitrc causes syntax error X-Mailer: reportbug 2.48 Date: Fri, 20 Aug 2004 18:08:32 +0200 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: xbase-clients Version: 4.2.1-12.1 Severity: normal At line 469 in the preinst script is the following: if [ -L /etc/X11/xinit/xinitrc -a $(readlink /etc/X11/xinitrc)= This is causing a syntax error at install time: /var/lib/dpkg/tmp.ci/preinst: line 469: [: too many arguments I believe the line should read: if [ -L /etc/X11/xinit/xinitrc -a $(readlink /etc/X11/xinit/xinitrc)= Alexis -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.16 Locale: LANG=C, LC_CTYPE=C Versions of packages xbase-clients depends on: ii cpp-3.2 1:3.2.3-9The GNU C preprocessor ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii libdps1 4.2.1-12.1 Display PostScript (DPS) client li ii libfreetype62.1.7-2 FreeType 2 font engine, shared lib ii libncurses5 5.4-2Shared libraries for terminal hand ii libxaw7 4.2.1-12.1 X Athena widget set library ii xlibmesa3-gl [libgl1] 4.2.1-12.1 Mesa 3D graphics library [XFree86] ii xlibmesa3-glu [libglu1] 4.2.1-12.1 Mesa OpenGL utility library [XFree ii xlibs 4.2.1-12.1 X Window System client libraries -- debconf information excluded --- Received: (at 267085-done) by bugs.debian.org; 23 Aug 2004 09:03:53 + From [EMAIL PROTECTED] Mon Aug 23 02:03:53 2004 Return-path: [EMAIL PROTECTED] Received: from dhcp065-026-182-085.indy.rr.com (sisyphus.deadbeast.net) [65.26.182.85] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1BzAk4-00013d-00; Mon, 23 Aug 2004 02:03:53 -0700 Received: by sisyphus.deadbeast.net (Postfix, from userid 1000) id 0CE1368C015; Mon, 23 Aug 2004 04:03:52 -0500 (EST) Date: Mon, 23 Aug 2004 04:03:52 -0500 From: Branden Robinson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Bug#267085: xbase-clients: preinst script accessing xinitrc causes syntax error Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=l3ej7W/Jb2pB3qL2 Content-Disposition: inline In-Reply-To: [EMAIL PROTECTED] Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. User-Agent: Mutt/1.5.6+20040803i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0
Re: Please pass judgement on X-Oz licence: free or nay?
On Sun, Aug 08, 2004 at 11:35:10PM -0500, Joe Wreschnig wrote: Now, I can infer one of three things: 1. You had off-list contact with the X-Oz people before the license was analyzed here on -legal, and did not communicate their non-standard interpretation of that clause back to us for the summary. 2. You can travel through time, and went back to prepare the summary with the knowledge that X-Oz had weird license interpretations. 3. You are confusing the order in which events happened (I suppose this is not really in conflict with the above). I suppose 1) is possible, but I find 3) most likely. David Dawes, who is the founder of X-Oz Technologies, was asked many questions about the meaning of the XFree86 1.1 license (which appears to be semantically identical to the X-Oz License) on the XFree86 Forum list[1] and other lists in January and February. I'm not subscribed to -forum, but I read a lot of its traffic back then because, as a member of the X Strike Force package maintenance team for Debian, I needed to know what the heck was going on with the upstream licensing of XFree86. I don't see why you consider this determination to be an egregious mistake. I don't know what business we have declaring licenses whose terms we don't understand as DFSG-free. Clause 4 -- which you declared non-free in that thread *before* public conversations with X-Oz, and Brian declared non-free at the start of this thread -- is identical to that used in the existing X license. There is a world beyond Debian, you know. :) I agree that non-standard interpretations of common clauses can result in a license being non-free (c.f. pine), but I don't find any evidence that that was the case when the X-Oz license summary was published. Well, the problem was more a refusal on the part of the license author to *state* an interpretation, rather than adopt a non-standard one. I suspect that summary is where Brian drew his conclusion that the license that started this thread was non-free. I stand by my statement that the X-Oz license summary as currently published is an egregious mistake. The XFree86 Forum list archives stand available to anyone who cares to slog through the gigantic threads the announced the license change generated. In my view, there are many more questions than answers to be found on that list -- particularly when it comes to on-topic threads, sadly. [1] http://www.xfree86.org/pipermail/forum/ -- G. Branden Robinson|Beware of and eschew pompous Debian GNU/Linux |prolixity. [EMAIL PROTECTED] |-- Charles A. Beardsley http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Bug#267566: libxft2: abiword (compiled from CVS HEAD) crash
Package: libxft2 Version: 2.1.2-6 Severity: important If I download abiword sources from CVS HEAD (cvs -z 9 -q checkout popt libpng ots abi expat abidistfiles wv psiconv abiword-plugins abispell) and then I compile it (./configure --enable-debug, make) I obtain I crash running /usr/local/bin/ abiword. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1078950848 (LWP 7110)] 0x4171a87a in XftFontOpenXlfd () from /usr/lib/libXft.so.2 (gdb) backtrace #0 0x4171a87a in XftFontOpenXlfd () from /usr/lib/libXft.so.2 #1 0x4171acfb in XftLockFace () from /usr/lib/libXft.so.2 #2 0x40157d37 in pango_xft_picture_render () from /usr/lib/libpangoxft-1.0.so.0 #3 0x404d7445 in pango_fc_font_lock_face () from /usr/lib/libpangoft2-1.0.so.0 #4 0x40652f2c in ?? () from /usr/lib/pango/1.4.0/modules/pango-basic-fc.so #5 0x08a2e5c0 in ?? () #6 0x000b in ?? () #7 0x4016a735 in ?? () from /usr/lib/libpango-1.0.so.0 #8 0x051f6c85 in ?? () #9 0x40168274 in ?? () from /usr/lib/libpango-1.0.so.0 #10 0x in ?? () #11 0x01ec9275 in ?? () #12 0x40154518 in ?? () #13 0x40169f69 in ?? () from /usr/lib/libpango-1.0.so.0 #14 0x in ?? () #15 0x0001 in ?? () #16 0x4000b9b3 in _dl_map_object_deps () from /lib/ld-linux.so.2 #17 0x401798ed in _pango_engine_shape_shape () from /usr/lib/libpango-1.0.so.0 #18 0x401871fe in pango_shape () from /usr/lib/libpango-1.0.so.0 #19 0x4017f75d in pango_layout_get_pixel_size () from /usr/lib/libpango-1.0.so.0 #20 0x4017f8d3 in pango_layout_get_pixel_size () from /usr/lib/libpango-1.0.so.0 #21 0x4017ffdc in pango_layout_get_pixel_size () from /usr/lib/libpango-1.0.so.0 #22 0x4017e396 in pango_layout_get_cursor_pos () from /usr/lib/libpango-1.0.so.0 #23 0x4017e6e7 in pango_layout_get_extents () from /usr/lib/libpango-1.0.so.0 #24 0x412869d6 in gtk_label_get () from /usr/lib/libgtk-x11-2.0.so.0 #25 0x401b9c7e in g_cclosure_marshal_VOID__BOXED () from /usr/lib/libgobject-2.0.so.0 #26 0x401a4fb7 in g_cclosure_new_swap () from /usr/lib/libgobject-2.0.so.0 #27 0x401a4c20 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #28 0x401b844e in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0 #29 0x401b7be7 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #30 0x401b7fd4 in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0 #31 0x412e5d01 in gtk_size_group_remove_widget () from /usr/lib/libgtk-x11-2.0.so.0 #32 0x412e6088 in _gtk_size_group_compute_requisition () from /usr/lib/libgtk-x11-2.0.so.0 #33 0x4139897c in gtk_widget_size_request () from /usr/lib/libgtk-x11-2.0.so.0 #34 0x08466678 in abi_table_resize (table=0x8a26f20) at xap_UnixTableWidget.cpp:134 #35 0x08467b35 in abi_table_init (table=0x8a26f20) at xap_UnixTableWidget.cpp:687 #36 0x401bde6a in g_type_create_instance () from /usr/lib/libgobject-2.0.so.0 #37 0x401a873f in g_object_new_valist () from /usr/lib/libgobject-2.0.so.0 #38 0x411de654 in gtk_button_get_type () from /usr/lib/libgtk-x11-2.0.so.0 #39 0x401a7ece in g_object_newv () from /usr/lib/libgobject-2.0.so.0 #40 0x401a870e in g_object_new_valist () from /usr/lib/libgobject-2.0.so.0 #41 0x401a7b96 in g_object_new () from /usr/lib/libgobject-2.0.so.0 #42 0x08468015 in abi_table_new () at xap_UnixTableWidget.cpp:768 #43 0x082d684e in EV_UnixToolbar::synthesize (this=0x8a21b90) at ev_UnixToolbar.cpp:737 #44 0x082770d2 in XAP_FrameImpl::_createToolbars (this=0x89395d8) at xap_Frame.cpp:663 #45 0x0828e2ec in XAP_UnixFrameImpl::createTopLevelWindow (this=0x89395d8) at xap_UnixFrameImpl.cpp:1176 #46 0x0814bb4f in AP_UnixFrameImpl::_createWindow (this=0x89395d8) at ap_UnixFrameImpl.cpp:298 #47 0x081497ff in AP_UnixFrame::initialize (this=0x8939558, frameMode=XAP_NormalFrame) at ap_UnixFrame.cpp:207 #48 0x08144a9e in AP_UnixApp::newFrame (this=0x878d130) at ap_UnixApp.cpp:366 #49 0x0814ee5c in AP_App::openCmdLineFiles (this=0x878d130, args=0xb860) at ap_App.cpp:90 #50 0x081476a8 in AP_UnixApp::main (szAppName=0x849bcaa AbiWord, argc=1, argv=0xb944) at ap_UnixApp.cpp:1483 #51 0x08143d0e in main (argc=1, argv=0xb944) at UnixMain.cpp:26 -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.7-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] Versions of packages libxft2 depends on: ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an ii libfontconfig12.2.3-1generic font configuration library ii libfreetype6 2.1.7-2.2 FreeType 2 font engine, shared lib ii libx11-6 4.3.0.dfsg.1-6 X Window System protocol client li ii libxrender1 0.8.3-7X Rendering Extension client libra ii xlibs 4.3.0.dfsg.1-6 X Window System client libraries m ii zlib1g1:1.2.1.1-5compression library - runtime -- no debconf information
Bug#89887: Bug#19538: marked as done (xterm: resize not handled by both primary and alternate screens)
Thomas Dickey writes (Bug#89887: Bug#19538: marked as done (xterm: resize not handled by both primary and alternate screens)): On Sat, Aug 21, 2004 at 01:18:49AM -0500, Branden Robinson wrote: What reason is there for not changing it ? Thomas, meet Ian Jackson. ;-) I've already had the experience. I can mark this bug wontfix, if you like. ok. I take this to mean that you don't have the effort. I will go away and prepare a patch (trivial, no doubt). When I have done that I would appreciate it if you would apply it. Ian.
X Strike Force XFree86 SVN commit: r1746 - in trunk/debian: . local
Author: branden
Date: 2004-08-23 09:50:25 -0500 (Mon, 23 Aug 2004)
New Revision: 1746
Modified:
trunk/debian/CHANGESETS
trunk/debian/changelog
trunk/debian/local/dexconf
trunk/debian/local/dexconf.1
trunk/debian/xserver-xfree86.postinst.in
Log:
Overhaul dexconf.
+ Drop support for XFree86 3.x X server format.
+ Drop support for -f, --format and -s, --stdout options.
+ Use exec and open file descriptor 4 for output, instead of repetitiously
redirecting standard output to a file explicitly all the time. We can't
use fd 3 since debconf uses it.
+ Use here documents a little more, and printf a little less.
+ Put blank lines between XF86Config-4 sections so that the file is easier
to read.
+ Overwrite the destination file instead of mving or cping it; this
way it is never unlinked. (The maintainer scripts implement enough
paranoia already.)
+ Tidy up shell style.
+ Modernize dexconf(1) manual page to undocument obsolete options, replace
the FUTURE DIRECTIONS section with HISTORY, correct and update
DIAGNOSTICS section, provide more cross-references, and put a newline
at the end of every sentence in the document source (per the GNU Roff
texinfo documentation).
+ Use -o instead of -s and redirection when invoking dexconf from
xserver-xfree86's postinst script, since the -s option is no longer
supported.
+ WARNING: xserver-xfree86{,-dbg} 4.3.0.dfsg.1-[56] are not compatible with
this version of xserver-common, or planned future versions, due to the
above-mentioned removal of dexconf's -s option. At the same time,
saying xserver-common 4.3.0.dfsg.1-7 conflicts: xserver-xfree86
( 4.3.0.dfsg.1-7) and xserver-xfree86-dbg ( 4.3.0.dfsg.1-7) is
excessive because 4.3.0.dfsg.1-4 and earlier will work. I have heard
that stating such a conflict can make things difficult for apt's
problem resolver (or even impossible, if in conjunction with enough
other versioned dependency or conflicts), so the risk seems greater than
the reward. It's too bad we don't have a way to conflict on ranges that
aren't bounded on either zero or infinity. Given that 4.3.0.dfsg.1-[56]
have never appeared even in sarge, I'm making this judgement call. Any
bugs about this will be closed with this changelog entry included,
unless you can rebut my premises; i.e., I am Jason Gunthorpe and I
declare that apt can eat a stack of versioned conflicts like this for
breakfast and still see the One True Upgrade Path!, or You silly
person, of *course* dpkg and apt accept 'Conflicts: (4.3.0.dfsg.1-4 )
xserver-xfree86 ( 4.3.0.dfsg.1-7)'!
Modified: trunk/debian/CHANGESETS
===
--- trunk/debian/CHANGESETS 2004-08-22 04:46:19 UTC (rev 1745)
+++ trunk/debian/CHANGESETS 2004-08-23 14:50:25 UTC (rev 1746)
@@ -394,4 +394,45 @@
xrestop package and utility.
1745
+Overhaul dexconf.
++ Drop support for XFree86 3.x X server format.
++ Drop support for -f, --format and -s, --stdout options.
++ Use exec and open file descriptor 4 for output, instead of repetitiously
+ redirecting standard output to a file explicitly all the time. We can't
+ use fd 3 since debconf uses it.
++ Use here documents a little more, and printf a little less.
++ Put blank lines between XF86Config-4 sections so that the file is easier
+ to read.
++ Overwrite the destination file instead of mving or cping it; this
+ way it is never unlinked. (The maintainer scripts implement enough
+ paranoia already.)
++ Tidy up shell style.
++ Modernize dexconf(1) manual page to undocument obsolete options, replace
+ the FUTURE DIRECTIONS section with HISTORY, correct and update
+ DIAGNOSTICS section, provide more cross-references, and put a newline
+ at the end of every sentence in the document source (per the GNU Roff
+ texinfo documentation).
++ Use -o instead of -s and redirection when invoking dexconf from
+ xserver-xfree86's postinst script, since the -s option is no longer
+ supported.
++ WARNING: xserver-xfree86{,-dbg} 4.3.0.dfsg.1-[56] are not compatible with
+ this version of xserver-common, or planned future versions, due to the
+ above-mentioned removal of dexconf's -s option. At the same time,
+ saying xserver-common 4.3.0.dfsg.1-7 conflicts: xserver-xfree86
+ ( 4.3.0.dfsg.1-7) and xserver-xfree86-dbg ( 4.3.0.dfsg.1-7) is
+ excessive because 4.3.0.dfsg.1-4 and earlier will work. I have heard
+ that stating such a conflict can make things difficult for apt's
+ problem resolver (or even impossible, if in conjunction with enough
+ other versioned dependency or conflicts), so the risk seems greater than
+ the reward. It's too bad we don't have a way to conflict on ranges that
+ aren't bounded on either zero or infinity. Given that 4.3.0.dfsg.1-[56]
+ have never appeared even in sarge, I'm making this judgement call. Any
+ bugs about this will be closed with this changelog entry included,
+ unless you can rebut my premises;
Re: Bug#267503: upgrading from potato -- /etc/X11/Xwrapper.config not created
I upgraded xserver-common from 3.3.6-11potato32 to 4.3.0.dfsg.1-4 /etc/X11/Xwrapper.config was not created. Upgrading over more than one release at once (in your case, from potato to sarge) isn't necessarily supported. Did you try first upgrading to the woody package (4.1.0-16woody3) and then to the package in sarge? If upgrading that way works fine, this bug ought to be downgraded to wishlist. (n.b. I have nothing to do with the X packages, so consider this an advisory opinion only :-) regards, -- Kevin B. McCarty [EMAIL PROTECTED] Physics Department WWW: http://www.princeton.edu/~kmccarty/Princeton University GPG public key ID: 4F83C751 Princeton, NJ 08544
Bug#267713: xserver-xfree86: Turns off video card when changing tty
Package: xserver-xfree86 Version: 4.3.0.dfsg.1-4 Severity: important I was running xdm and attempted to switch to a console, but in doing so the monitor turned off. All connections were correct, and the console had previously worked. Upon switching back to tty7 (X), the monitor came back on. I suspect that X turns off the video card when switching, rather than releasing it. -- Package-specific info: Contents of /var/lib/xfree86/X.roster: xserver-xfree86 /etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 20 Aug 23 11:39 /etc/X11/X - /usr/bin/X11/XFree86 -rwxr-xr-x 1 root root 1745132 May 29 08:33 /usr/bin/X11/XFree86 Contents of /var/lib/xfree86/XF86Config-4.roster: xserver-xfree86 VGA-compatible devices on PCI bus: :01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1 /etc/X11/XF86Config-4 unchanged from checksum in /var/lib/xfree86/XF86Config-4.md5sum. XFree86 X server configuration file status: -rw-r--r-- 1 root root 3363 Aug 23 11:39 /etc/X11/XF86Config-4 Contents of /etc/X11/XF86Config-4: # XF86Config-4 (XFree86 X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type man XF86Config-4 at the shell prompt.) # # This file is automatically updated on xserver-xfree86 package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xfree86 # package. # # If you have edited this file but would like it to be automatically updated # again, run the following commands as root: # # cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom # md5sum /etc/X11/XF86Config-4 /var/lib/xfree86/XF86Config-4.md5sum # dpkg-reconfigure xserver-xfree86 Section Files FontPathunix/:7100# local font server # if the local font server has problems, we can fall back on these FontPath/usr/lib/X11/fonts/misc FontPath/usr/lib/X11/fonts/cyrillic FontPath/usr/lib/X11/fonts/100dpi/:unscaled FontPath/usr/lib/X11/fonts/75dpi/:unscaled FontPath/usr/lib/X11/fonts/Type1 FontPath/usr/lib/X11/fonts/CID FontPath/usr/lib/X11/fonts/Speedo FontPath/usr/lib/X11/fonts/100dpi FontPath/usr/lib/X11/fonts/75dpi EndSection Section Module LoadGLcore Loadbitmap Loaddbe Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadrecord Loadspeedo Loadtype1 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc104 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/psaux Option Protocol ImPS/2 Option Emulate3Buttons true Option ZAxisMapping 4 5 EndSection Section Device Identifier Trident Microsystems CyberBlade/i1 Driver trident EndSection Section Monitor Identifier MAG:0203 HorizSync 50-90 VertRefresh 43-75 Option DPMS EndSection Section Screen Identifier Default Screen Device Trident Microsystems CyberBlade/i1 Monitor MAG:0203 DefaultDepth24 SubSection Display Depth 1 Modes 1280x1024 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 1280x1024 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 1280x1024 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 15 Modes 1280x1024 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 16 Modes 1280x1024 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 24 Modes 1280x1024 1152x864 1024x768 800x600 640x480 EndSubSection EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard
