Re: mouse for x

2004-09-26 Thread Branden Robinson
On Wed, Sep 22, 2004 at 01:13:25PM +0200, Geert Uytterhoeven wrote:
  1) If the available and default choices for Amiga, Atari, and Mac are sane;
 
 I think they are.
 
 Except that Mac uses the new input layer in 2.4 and later.

Even for bus mice?

 This is also valid for other subarchs in 2.6.

You can review the full code in question at:

svn://necrotic.deadbeast.net/xfree86/branches/debconf-overhaul/debian/xserver-xfree86.config.in

  2) If anyone has anything to regarding VME or Q40/Q60 machines.
 
 Q40/Q60 has PS/2 keyboard, so I guess it has a PS/2 mouse as well. Richard?

I could still use an answer on this point.

-- 
G. Branden Robinson|Computer security is like an onion:
Debian GNU/Linux   |the more you dig in, the more you
[EMAIL PROTECTED] |want to cry.
http://people.debian.org/~branden/ |-- Cory Altheide


signature.asc
Description: Digital signature


Bug#272493: libxpm4 security problem

2004-09-26 Thread Daniel Stone
On Mon, Sep 20, 2004 at 03:14:18PM -0500, Branden Robinson wrote:
 Daniel Stone's understanding about who is handling 4.3 is wrong -- I'm
 not sure where he got it, as I've discussed this issue with Martin Schulze
 from the Debian Security Team and Fabio Massimo Di Nitto, the XFree86
 package release manager.

Apologies for the misunderstanding.

 [...]
 
 (In the future, please don't file bugs against unsupported or unreleased
 versions of Debian packages.  I have no idea what libxpm4
 4.3.0-0pre1v5.49.200406160839 is.  Whoever shipped that package is the
 proper recipient of your bug report.)

Ehm, while it's a decent general rule, the bug here clearly applies to
all versions of XFree86, so there's no reason to tell them to go file
a bug report somewhere else.  Both you and I know that the version
header is irrelevant in this case.

-- 
Daniel Stone[EMAIL PROTECTED]
Debian: the universal operating system http://www.debian.org


signature.asc
Description: Digital signature


Bug#229850: DEFAULT_HORIZ_SYNC and DEFAULT_VERT_REFRESH still ignored (updated patch)

2004-09-26 Thread Jay Berkenbilt

Thanks for the update, and for mentioning trying to get -8 into
Sarge.  I noticed that the bug wasn't fixed for -7 and that it had
been pushed to -8 in the to do list along with several other debconf
changes.  If you're interested in help with testing, please let me
know and I'll see what I can do.  Thanks for all you do and for
finding the time to keep me informed through all of it.

   Please let me know what you think of the following logic.  It includes your
   patch, along with some other enhancements as well as better instrumentation
   and internal documentation.

   I have committed this to the XSF SVN XFree86 repo's debconf-overhaul branch
   as revision 1858.

Reading through the code, I have a couple of quick comments.  I'll
also test on a few machines and post additional comments even if they
are limited to saying that it works well.

 * My guess is that several people out there have monitors whose
   refresh rates are suboptimal but whose rates will not get fixed
   during the upgrade because there are already answers in debconf to
   some questions.  If my understanding is correct, this could be
   partially mitigated by changing the names of the some of the
   variables.  I haven't actually looked to see whether this is the
   case, but it may be worth considering if it isn't.  Stated
   differently, it may be worth seeing whether there is something that
   could make it possible to automatically fix suboptimal data left
   over from older versions of the package.  (I'm going to dpkg -P
   --force-depends xserver-xfree86 and reinstall just to be sure.)

 * In the Medium monitor selection code, there are 60Hz and 85Hz
   choices for 1280x960 but only a 60Hz choice for 1280x1024.
   Personally, my eyes hurt looking at any screen whose refresh rate
   is less than about 75Hz (which is what motivated me to post this
   bug in the first place).  I think it would be best if there were a
   75Hz rate at all common resolutions.  1280x1024 is the native
   resolution on almost all 17 and 19 flat panels, so it is a pretty
   important one to have in there.  There is also no option to have
   1024x768 at anything higher than 75Hz.  I guess, ideally, there
   should be a 60Hz, 75Hz, and 85Hz for all resolutions.  If my
   understanding is correct, in principle, to convert the sync and
   refresh rates from one refresh rate to another at the same
   resolution, you should be able to multiply the top number in each
   range by the square root of the ratios of the sync/refresh rates.
   In other words, the ratio of the product of the sync and refresh
   rates should be the same as the ratio of the refresh rates.
   Someone else probably understands better.  The obsolete XFree86
   Video Timings HOWTO actually explains this better.  Anyway, people
   with older hardware that need to use this menu probably won't be
   pushing those resolutions anyway.  (I notice this rule I've stated
   doesn't actually match with all the menu items that are already
   there.)

I should have time in the next day or two to test this on a few
different machines.  If I have access to check out from subversion,
I'll try checking out the maintainer scripts and testing with all of
them.  Otherwise, I'll just drop this config_monitor into the version
in the current package.  (I'm trying to check svn now but alioth is
too slow.)

I'll try to get back to you after testing on three machines: a laptop
with a Radeon Mobility M6, my desktop machine with a Radeon 9600, and
my work machine with a built-in Intel video.  I am no longer using the
Rage Pro card I was using when I posted the original report.

-- 
Jay Berkenbilt [EMAIL PROTECTED]
http://www.ql.org/q/




Bug#267062: xlibs: [xkb] wrong Compose file for pl_PL.UTF-8?

2004-09-26 Thread Branden Robinson
Sorry for the delay in replying; I was on vacation last week.

On Mon, Aug 30, 2004 at 12:42:18AM +0200, Shot wrote:
 Branden Robinson:
  Yes, this works for me on a Debian testing system (xfree86 4.3.0.dfsg.1-4).
 
 I'm running -6 here, but it doesn't seem to matter, because...
 
   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.
  
  This is screwed up.  In uxterm running bash with LC_CTYPE=en_US.UTF-8,
  I *can* get per mille, but not aogonek, using the compose sequences
  you indicated.
 
 ...uxterm, you say. This gets interesting - uxterm works for
 me according to the compose maps, that is it seems to be using
 en_US.UTF-8/Compose; I *can* get per mille, I *can't* get aogonek.
 Does this mean there's something broken in GTK/GNOME? Mozilla, Galeon,
 gnome-terminal: all broken. xterm, uxterm, OpenOffice.org Writer:
 all working.

Jeff Licquia told me this actually has something to do with a wrong or
suboptimal input manager being used by GNOME.

Jeff, can you reply to [EMAIL PROTECTED] with a more
coherent explanation?

-- 
G. Branden Robinson| Eternal vigilance is the price of
Debian GNU/Linux   | liberty.
[EMAIL PROTECTED] | -- Wendell Phillips
http://people.debian.org/~branden/ |


signature.asc
Description: Digital signature


Re: mouse for x

2004-09-26 Thread Brad Boyer
On Sat, Sep 25, 2004 at 11:14:16PM -0500, Branden Robinson wrote:
 On Wed, Sep 22, 2004 at 01:13:25PM +0200, Geert Uytterhoeven wrote:
  Except that Mac uses the new input layer in 2.4 and later.
 
 Even for bus mice?

The only type of mouse on a 68k mac is ADB, and the entire ADB layer
got converted over to use the generic input system for 2.4. The old
adbmouse driver doesn't even exist in the tree in 2.6, but it was
still possible to compile it in during 2.4, i think.

Because of this, if a 68k mac is running anything 2.4 or 2.6, the
mice should show up in /dev/input/mice. If it is running a 2.2
kernel, they should show up in /dev/adbmouse (busmouse protocol).

The ppc macs made the same transition a few years ago. It's actually
an integrated code base for ADB support now.

Brad Boyer
[EMAIL PROTECTED]



Bug#253607: #253607: xserver-xfree86: (debconf) X 4.3.0 is perfectly capable of detecting monitor resolutions, debconf should ask only if needed

2004-09-26 Thread Daniel Stone
On Mon, Sep 13, 2004 at 12:50:52PM -0500, Branden Robinson wrote:
 On Tue, Aug 31, 2004 at 08:12:07PM -0700, Daniel Stone wrote:
  On Tue, Aug 31, 2004 at 02:32:49PM -0500, Branden Robinson wrote:
   Yes, somehow.  You don't provide any code, or anything beyond the barest
   sketch of a design really, so this is going to have to wait until after
   sarge.
  
  http://www.google.com/search?q=ddcprobe+source
 
 This comment is too terse to be useful for me.  The top link is a set of
 compiled RPMs for Caldera machines.  In reviewing a Red Hat Bugzilla entry
 farther down the list, I see that ddcprobe may have as many problems as
 read-edid.  Perhaps just different ones.  :-P

read-edid only detects detailed timings (the ones you get back with
horizonal active, horizontal blanking, et al), not any of the standard
timings the monitor outputs.  I'm using ddcprobe to detect standard
timings, detailed timings (my hack), and monitor information.

-- 
Daniel Stone[EMAIL PROTECTED]
Debian: the universal operating system http://www.debian.org


signature.asc
Description: Digital signature


Bug#271235: Starting xine and mplayer makes mplayer work

2004-09-26 Thread Fabio Massimo Di Nitto

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Eric Valette wrote:
| I discovered this when using xine to display the temporary file before
| mplayer tries to play it makes mplayer work. So it looks like once
| XVideo is alraedy used, mplayer can access it...
|
|
| -- eric
|
|
|

I have been discussing this issue with other people. We believe, at this
point in time, that the bug is in mplayer since all the others players
work fine at the first shot. But there are no doubts that the changes to
the driver (that now supports much more hardware) have introduced this
change.

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.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBVtsmhCzbekR3nhgRArKRAKCIHLRClIkUeHh5/OBmuJe22fMqzQCghRft
h81fqREO/elVnmEcJPByC4s=
=4rCY
-END PGP SIGNATURE-



Bug#271235: Starting xine and mplayer makes mplayer work

2004-09-26 Thread Andrei Badea

Fabio Massimo Di Nitto wrote:


Eric Valette wrote:
| I discovered this when using xine to display the temporary file before
| mplayer tries to play it makes mplayer work. So it looks like once
| XVideo is alraedy used, mplayer can access it...
|
|
| -- eric
|
|
|

I have been discussing this issue with other people. We believe, at this
point in time, that the bug is in mplayer since all the others players
work fine at the first shot. But there are no doubts that the changes to
the driver (that now supports much more hardware) have introduced this
change.


Not quite all the other players. I'm also experiencing problems with tvtime (a 
program to watch tv which uses the xvideo extension) which I'm describing in an 
older post to this bug. Maybe this is too a bug in tvtime triggered by the 
changes in nv_drv.o.


Best regards,
Andrei

--
[EMAIL PROTECTED] # http://movzx.net # ICQ: 52641547


signature.asc
Description: OpenPGP digital signature


Re: Bug#271235: Starting xine and mplayer makes mplayer work

2004-09-26 Thread Xavier Bestel
Le dim 26/09/2004 à 17:07, Fabio Massimo Di Nitto a écrit :

 I have been discussing this issue with other people. We believe, at this
 point in time, that the bug is in mplayer since all the others players
 work fine at the first shot. But there are no doubts that the changes to
 the driver (that now supports much more hardware) have introduced this
 change.

One thing that may help: mplayer uses AUTOPAINT (the Xv window is
painted with the transparent color automatically) whereas xine paints
the window itself. Maybe just the AUTOPAINT method is broken in the
driver, i.e. the drivers paints the window with the wrong color.

HTH,

Xav



Bug#267062: xlibs: [xkb] wrong Compose file for pl_PL.UTF-8?

2004-09-26 Thread Jeff Licquia
On Mon, 2004-09-20 at 14:55, Branden Robinson wrote:
 On Mon, Aug 30, 2004 at 12:42:18AM +0200, Shot wrote:
  ...uxterm, you say. This gets interesting - uxterm works for
  me according to the compose maps, that is it seems to be using
  en_US.UTF-8/Compose; I *can* get per mille, I *can't* get aogonek.
  Does this mean there's something broken in GTK/GNOME? Mozilla, Galeon,
  gnome-terminal: all broken. xterm, uxterm, OpenOffice.org Writer:
  all working.
 
 Jeff Licquia told me this has to do with the GNOME input method you have
 configured.
 
 Jeff, can you mail [EMAIL PROTECTED]  with a little more
 elaboration?

Sorry for the late reply; it appears that Debian's mail system held onto
these messages for a while, so I just now got them.

GTK+ has its own input method framework that is separate from the X
input methods.  This is necessary because GTK+ is supposed to be
independent of X.

The default input method is, of course, Latin.  When implementing this
method, the GTK+ people focused on ISO-8859-1, and did not implement
many of the other Latin character sets.  This is why GTK-based programs
seem not to be able to type characters that other pure X programs can.

There are several things you can do about the problem.  All of them
involve using a different GTK+ input method.  You can test these by
opening some GTK+ app that takes input, such as gedit.  Right-click on
the edit box, and there should be a submenu for Input Methods.  The
new input method should show up in that submenu.

 - Get a better GTK+ input method.  The gtk-im-extra Sourceforge project
(http://gtk-im-extra.sourceforge.net/) contains a Latin Plus input
method, for example.  While you're at it, you might also lobby the GTK+
people to include gtk-im-extra, and make Latin Plus the default.

 - There are alternative input method projects out there that provide
GTK+ IM shims; look for the packages iiimgcf, scim-gtk2-immodule, and
uim-gtk2.0 in testing/unstable.  Most of these, though, are aimed at
non-Latin issues, so I can't tell you if any of them would be
appropriate.

 - Additionally, GTK+ ships with a XIM shim module.  This is the
solution I've implemented.

If you want to make some other input method the default, edit
/etc/environment, and set the environment variable GTK_IM_MODULE there
to the input method module you want (xim for the XIM shim).  Of
course, you can do the same thing for just yourself by setting that
environment variable in .profile, .bashrc, or whatever.





Bug#273516: [l10n] Updated Czech translation of XFree86 debconf messages

2004-09-26 Thread Miroslav Kure
Package: xfree86
Severity: wishlist
Tags: patch, l10n

Hi, in attachement there is updated Czech translation (cs.po) of
XFree86 debconf messages. Please include it, thanks.

-- 
Miroslav Kure


xfree86-cs.po.gz
Description: Binary data


Bug#271235: Starting xine and mplayer makes mplayer work

2004-09-26 Thread Eric Valette

Fabio Massimo Di Nitto wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Eric Valette wrote:
| I discovered this when using xine to display the temporary file before
| mplayer tries to play it makes mplayer work. So it looks like once
| XVideo is alraedy used, mplayer can access it...
|
|
| -- eric
|
|
|

I have been discussing this issue with other people. We believe, at this
point in time, that the bug is in mplayer since all the others players
work fine at the first shot. But there are no doubts that the changes to
the driver (that now supports much more hardware) have introduced this
change.

Fabio


Then I will bug mplayer people :-)

A big thanks for your work and time.

-- eric







a process designed To close your card accounts

2004-09-26 Thread serina payne
Calls concerning overdue payments will cease.
We have pioneered an advanced system of proven strategies 
that will get the creditors and debt collectors off your back for good

Our debt termination program has legally stopped millions of dollars worth
of debt from being collected.


check out our Elimination Program here
http://www.turboproductuse.com/e2/



po box in link above and you can say no thank you for future




In feature he was most majestic, and his eyes held the soft but penetrating
brilliance of electric lights. It was hard to meet the gaze of those
searching eyes, but Rob did it, and at once the splendid apparition bowed
and said in a low, clear voice: I am here
I know that, answered the boy, trembling, but WHY are you here? Because you
have touched the Master Key of Electricity, and I must obey the laws of
nature that compel me to respond to your summons



pianoladys.com

2004-09-26 Thread ShrlH


Please subscribe ne to Pianoladys.com Thank you
 [EMAIL PROTECTED]


Bug#229850: DEFAULT_HORIZ_SYNC and DEFAULT_VERT_REFRESH still ignored (updated patch)

2004-09-26 Thread Jay Berkenbilt

There's at least one bug in configure_monitor that I found during my
testing.  The place where configure_monitor decides to pre-answer the
selection method with Advanced may be wrong.  If I leave it as it
appears in the original file:

db_subst xserver-xfree86/config/monitor/selection-method default Advanced

then the horiz-sync and vert-refresh debconf items never get set.  If
I change it to this instead:

db_set xserver-xfree86/config/monitor/selection-method Advanced

then everything works -- well, at least I get answers to those
questions in the debconf database.  Here's the relevant background.

I should point out that preinst and config do not appear to be in sync
at the moment, or at least I don't have correct versions.  I used
viewCVS from necrotic.deadbeast.net to grab the latest
xserver-xfree86.config.in and xserver-xfree86.preinst.in along with
shell-lib.sh.  I reconstructed config and preinst manually by
inserting shell-lib.sh at the right place.  Upon doing this, I
observed that there were no meaningful changes in either preinst or
shell-lib.sh, which was not surprising since they still had an older
svn revision.  Since the overall structure of config changed quite a
bit, I couldn't just drop configure_monitor in and instead had to use
the entire new config file.

For whatever reason, discover decides that the vesa device, rather
than the ATI device, is the right one for my card.  Even with correct
settings, my monitor refresh rate is at 60Hz with the vesa driver and
at 75Hz with the ati driver (which works fine as long as I don't load
radeonfb).  I have a Radeon 9600 card.

Regardless of my DEBIAN_PRIORITY, I end up with a zero-length
XF86Config file, and I get asked three times (once in config and twice
in preinst) whether I wish to try hardware autodetection.  In the end,
apt-get install aborts saying that
xserver-xfree86/config/monitor/horiz-sync is not set and tells me to
run dpkg-reconfigure xserver-xfree86.  Looking at
/var/log/xserver-xfree86.config.log, I see this:

2004-09-26 04:36:36 PM-0400 configure_monitor(): using  selection method

which is what made me decide to try the change I described above.

After I make the change, I get:

2004-09-26 04:42:11 PM-0400 configure_monitor(): using Advanced selection 
method

I'll admit to not having a deep knowledge of debconf, so I'm not sure
why the original code is wrong.  There is a db_get on
xserver-xfree86/config/monitor/selection-method before the above
message, but I never see the question.  In any case, the comment
doesn't say that it wants to change the default: it says it wants to
pre-answer the question, so I think the db_set is probably correct.

I also can't see what in preinst is causing the autodetect_video_card
question to be asked twice even though we've been through it already
in config.

The good news is that, if I make the one-line change I made, at least
I do eventually get an XF86Config-4 that has the correct refresh
rates.

So obviously, there's some more work to do and I don't know how
much of my testing problems were the result of my trying to cobble
together configuration files from subversion.  Again, please let me
know if you need additional testing.  I'll also try on some hardware
that discover recognizes better to see whether some of the problems go
away.

-- 
Jay Berkenbilt [EMAIL PROTECTED]
http://www.ql.org/q/




Bug#229850: DEFAULT_HORIZ_SYNC and DEFAULT_VERT_REFRESH still ignored (updated patch)

2004-09-26 Thread Jay Berkenbilt

I should amend slightly what I said before:

   at the moment, or at least I don't have correct versions.  I used
   viewCVS from necrotic.deadbeast.net to grab the latest
   xserver-xfree86.config.in and xserver-xfree86.preinst.in along with
   shell-lib.sh.  I reconstructed config and preinst manually by

I forgot to say that I was on the debconf-overhaul branch.

I also forgot to say that I had updated these variables as follows:

SOURCE_VERSION=4.3.0.dfsg.1-7
OFFICIAL_BUILD=yes

to make them match the config file that was already there.

Also, I sent a separate bug report against discover-data about the
fact that my video card seems not to be mapped properly to an X server
or driver.

-- 
Jay Berkenbilt [EMAIL PROTECTED]
http://www.ql.org/q/




Bug#203509: marked as done (xfree86-common: [Xsession] want 'x-no-session-manager' command)

2004-09-26 Thread Debian Bug Tracking System
Your message dated Sun, 26 Sep 2004 23:15:18 +0200
with message-id [EMAIL PROTECTED]
and subject line I do not get annoyed by alternative any more :-)
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; 30 Jul 2003 14:57:06 +
From [EMAIL PROTECTED] Wed Jul 30 09:56:54 2003
Return-path: [EMAIL PROTECTED]
Received: from ns.uni-sofia.bg (su.uni-sofia.bg) [62.44.96.1] 
by master.debian.org with smtp (Exim 3.35 1 (Debian))
id 19hsNp-0002H1-00; Wed, 30 Jul 2003 09:56:54 -0500
Received: (qmail 3101 invoked by uid 503); 30 Jul 2003 14:53:32 -
Received: from [EMAIL PROTECTED] by su.uni-sofia.bg by uid 500 with 
qmail-scanner-1.12 (F-PROT: 3.11. Clear:. Processed in 0.372157 secs); 30 Jul 
2003 14:53:32 -
Received: from magid.fmi.uni-sofia.bg (HELO fmi.uni-sofia.bg) (62.44.101.57)
  by ns.uni-sofia.bg with SMTP; 30 Jul 2003 14:53:31 -
Message-ID: [EMAIL PROTECTED]
Date: Wed, 30 Jul 2003 17:58:09 +0300
From: Ognyan Kulev [EMAIL PROTECTED]
Organization: Faculty of Mathematics and Informatics
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030714 
Debian/1.4-2
X-Accept-Language: bg, en-us
MIME-Version: 1.0
To: [EMAIL PROTECTED]
Subject: x-no-session-manager
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-7.0 required=4.0
tests=BAYES_10,HAS_PACKAGE,USER_AGENT_MOZILLA_UA
version=2.53-bugs.debian.org_2003_07_20
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_07_20 
(1.174.2.15-2003-03-30-exp)

Package: xfree86-common
Version: 4.2.1-9
Severity: wishlist

Hi,

As you know, when you have GNOME installed, you will always get 
x-session-manager started before any x-window-manager (by default). 
Sometimes you don't want that behaviour.

I propose creating x-no-session-manager that is symbolic link to 
x-window-manager.  This way user has choice for pure window manager when 
something like GNOME is installed.

Regards
-- 
Ognyan Kulev [EMAIL PROTECTED],fsa-bg.org}
7D9F 66E6 68B7 A62B 0FCF  EB04 80BF 3A8C A252 9782


---
Received: (at 168347-done) by bugs.debian.org; 26 Sep 2004 21:10:15 +
From [EMAIL PROTECTED] Sun Sep 26 14:10:15 2004
Return-path: [EMAIL PROTECTED]
Received: from outmx005.isp.belgacom.be [195.238.2.102] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CBgHf-0005Cv-00; Sun, 26 Sep 2004 14:10:15 -0700
Received: from outmx005.isp.belgacom.be (localhost [127.0.0.1])
by outmx005.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with 
ESMTP id i8QLA7U4006350
for [EMAIL PROTECTED]; Sun, 26 Sep 2004 23:10:07 +0200
(envelope-from [EMAIL PROTECTED])
Received: from dambo.lan.aokiconsulting.com (11.201-200-80.adsl.skynet.be 
[80.200.201.11])
by outmx005.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with 
ESMTP id i8QLA0pa006306
for [EMAIL PROTECTED]; Sun, 26 Sep 2004 23:10:00 +0200
(envelope-from [EMAIL PROTECTED])
Received: from osamu by dambo.lan.aokiconsulting.com with local (Exim 4.34)
id 1CBgMY-00031u-Er
for [EMAIL PROTECTED]; Sun, 26 Sep 2004 23:15:18 +0200
Date: Sun, 26 Sep 2004 23:15:18 +0200
From: Osamu Aoki [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: I do not get annoyed by alternative any more :-)
Message-ID: [EMAIL PROTECTED]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-GPG-Fingerprint: 253A 4076 6A3B CCE2 A426  DEF5 E80F C4C1 A806 1F32
User-Agent: Mutt/1.5.6+20040818i
Sender: Osamu Aoki [EMAIL PROTECTED]
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=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Hi,

Let me close this since alternative is not main way to select SM/WM
thesedays.  (GDM, KDM, WDM)

For XDM, we can use ~/.xsession anyway.

Now all DM use /etc/X11/Xsession.d/* files so inconsistent boot up
issues are gone.

Cheers,

Osamu
-- 
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +
Osamu Aoki [EMAIL PROTECTED]  Brussels Belgium, GPG-key: A8061F32
 .''`.  Debian Reference: post-installation user's guide for non-developers
 : :' : http://qref.sf.net and 

Bug#168347: marked as done (xfree86-common: [Xsession] want another way to prefer x-window-manager over x-session-manager)

2004-09-26 Thread Debian Bug Tracking System
Your message dated Sun, 26 Sep 2004 23:15:18 +0200
with message-id [EMAIL PROTECTED]
and subject line I do not get annoyed by alternative any more :-)
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; 8 Nov 2002 19:43:40 +
From [EMAIL PROTECTED] Fri Nov 08 13:43:40 2002
Return-path: [EMAIL PROTECTED]
Received: from sccrmhc03.attbi.com [204.127.202.63] 
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 18AF2a-0001xF-00; Fri, 08 Nov 2002 13:43:40 -0600
Received: from gateway.lan.aokiconsulting.com ([12.234.106.18])
  by sccrmhc03.attbi.com
  (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
  id [EMAIL PROTECTED]
  for [EMAIL PROTECTED]; Fri, 8 Nov 2002 19:43:09 +
Received: from goofy.lan.aokiconsulting.com ([192.168.1.3])
by gateway.lan.aokiconsulting.com with esmtp (Exim 3.35 #1 (Debian))
id 18AF22-0007CX-00
for [EMAIL PROTECTED]; Fri, 08 Nov 2002 11:43:06 -0800
Received: from nospam by goofy.lan.aokiconsulting.com with local (Exim 3.36 #1 
(Debian))
id 18AF1z-0004rH-00
for [EMAIL PROTECTED]; Fri, 08 Nov 2002 11:43:03 -0800
Date: Fri, 8 Nov 2002 11:43:03 -0800
From: Osamu Aoki [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: system default x-session-manager/xwindow-manager (patch)
Message-ID: [EMAIL PROTECTED]
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary=x+6KMIRAuhnl3hBn
Content-Disposition: inline
User-Agent: Mutt/1.4i
X-GPG-Fingerprint: 253A 4076 6A3B CCE2 A426  DEF5 E80F C4C1 A806 1F32
Sender: Osamu Aoki [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-4.6 required=5.0
tests=SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_MUTT
version=2.41
X-Spam-Level: 


--x+6KMIRAuhnl3hBn
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Package: xfree86-common
Version: 4.2.1-3
Severity: wishlist
Tags: patch

File:  /etc/X11/Xsession.d/50xfree86-common_determine-startup

Issues:
 1) Full path was not given for REALSTARTUP (Just to be safe side)
 2) If x-session-manager is installed on the system, it gets quite
intrusive to make one of the x-window-manager as the system default
(I like blackbox but want to have some accounts with KDE or GNOME.)
 3) If alternative system is broken (as I did recently), fall-back
scenario is weak.  (Let's fall-back to twm or xterm to make people
aware there is life beyond GNOME and KDE. Both xterm and twm are in
your associated packages).
 4) Hello, Branden.  I am brave enough to write a section for quick 
start-up guide for X in my Debian Reference.  Windows manager
set-up was one of the challenging one and I want my life to be easy
:-)  (I still have to add/correct few things in there.  This is
solicitation of constructive flame.) Latest CVS build are:

  http://qref.sf.net/Debian/reference/ch-tune.en.html#s-x

Please consider replacing 50xfree86-common_determine-startup with
something like attached file and update /etc/X11/Xsession.options
accordingly as attached file.  (Oops, I do not have manual page)

-- 
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +
Osamu Aoki [EMAIL PROTECTED]   Cupertino CA USA, GPG-key: A8061F32
 .''`.  Debian Reference: post-installation user's guide for non-developers
 : :' : http://qref.sf.net and http://people.debian.org/~osamu
 `. `'  Our Priorities are Our Users and Free Software --- Social Contract


--x+6KMIRAuhnl3hBn
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=50xfree86-common_determine-startup


if grep -qs ^allow-user-xsession $OPTIONFILE; then
  for STARTUPFILE in $STARTUP $ALTSTARTUP; do
if [ -e $STARTUPFILE ]; then
  if [ -x $STARTUPFILE ]; then
REALSTARTUP=$STARTUPFILE
  else
REALSTARTUP=sh $STARTUPFILE
  fi
  break
fi
  done
fi

# Works even if alternative system is broken. :-)
# also now you can install X session manager and you can choose to
# use X window manager as default for everyone.
if [ -z $REALSTARTUP ]; then
  if [ -x /usr/bin/x-session-manager ]; then
if ! grep -qs ^do-not-use-x-session-manager $OPTIONFILE; then
  REALSTARTUP=/usr/bin/x-session-manager
fi
  elif [ -x /usr/bin/x-window-manager ]; then
if ! grep -qs ^do-not-use-x-window-manager $OPTIONFILE; then
  REALSTARTUP=/usr/bin/x-window-manager
fi
  elif [ -x /usr/bin/X11/twm ]; then

Bug#273571: xserver-xfree86: lacks modelines for 16:10 modes

2004-09-26 Thread Jonathan
Package: xserver-xfree86
Version: 4.3.0.dfsg.1-7
Severity: important

I recently purchased a 20 16:10 aspect ratio lcd monitor from apple.  I
discovered, however, that X did not seem to have modelines for it by
default.  I used http://koala.ilog.fr/cgi-bin/nph-colas-modelines to
generate some, which I have tested to work on my monitor (apple 20
cinema display).

I added the following to my XF86Config-4:
Section Modes
Identifier 16:10
#   Computed by http://koala.ilog.fr/cgi-bin/nph-colas-modelines
#   parameters given: (some came from the site's defaults)
#   bandwidth: 20 - 200 MHz
#   vert sync: = 85 Hz
#   horiz sync: 30 - 100 kHz
#   DDC did not detect vsync and hsync on my monitor, set manually

ModeLine 640x400 33.51 640 672 832 896 400 402 414 440 #85Hz
ModeLine 800x500 51.40 800 840 1040 1120 500 502 514 540 #85Hz
ModeLine 1024x640 81.38 1024 1072 1312 1408 640 642 654 680 #85Hz
ModeLine 1280x800 123.37 1280 1336 1616 1728 800 802 814 840 #85Hz
ModeLine 1680x1050 199.18 1680 1752 2112 2256 1050 1052 1064 1090 #81Hz
EndSection

And in my Monitor section:
UseModes16:10

Other users may want these modes to be in the standard database.

Thank you.

-- 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 2004-07-11 16:07 /etc/X11/X - /usr/bin/X11/XFree86
-rwxr-xr-x  1 root root 1745484 2004-09-06 07:16 /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: nVidia Corporation NV34 [GeForce FX 
5200] (rev a1)

/etc/X11/XF86Config-4 does not match checksum in 
/var/lib/xfree86/XF86Config-4.md5sum.

XFree86 X server configuration file status:
-rw---  1 root root 4208 2004-09-26 20:08 /etc/X11/XF86Config-4

Contents of /etc/X11/XF86Config-4:


XFree86 X server log files on system:
-rw-r--r--  1 root root 28983 2004-09-26 20:11 /var/log/XFree86.0.log

Contents of most recent XFree86 X server log file
/var/log/XFree86.0.log:

This is a pre-release version of XFree86, and is not supported in any
way.  Bugs may be reported to XFree86@XFree86.Org and patches submitted
to [EMAIL PROTECTED]  Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository
(http://www.XFree86.Org/cvs).

XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-7 20040906103015 [EMAIL PROTECTED])
Release Date: 15 August 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.26 i686 [ELF] 
Build Date: 06 September 2004
Before reporting problems, check http://www.XFree86.Org/
to make sure that you have the latest version.
Module Loader present
OS Kernel: Linux version 2.6.7 ([EMAIL PROTECTED]) (gcc version 3.3.4 (Debian 
1:3.3.4-3)) #2 Tue Jul 13 22:48:38 EDT 2004 T
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/XFree86.0.log, Time: Sun Sep 26 20:08:16 2004
(==) Using config file: /etc/X11/XF86Config-4
(==) ServerLayout Default Layout
(**) |--Screen Default Screen (0)
(**) |   |--Monitor Generic Monitor
(**) |   |--Device nVidia Corporation NV34 [GeForce FX 5200]
(**) |--Input Device Generic Keyboard
(**) Option XkbRules xfree86
(**) XKB: rules: xfree86
(**) Option XkbModel pc101
(**) XKB: model: pc101
(**) Option XkbLayout us
(**) XKB: layout: us
(==) Keyboard: CustomKeycode disabled
(**) |--Input Device Configured Mouse
(WW) The directory /usr/lib/X11/fonts/cyrillic does not exist.
Entry deleted from font path.
(WW) The directory /usr/lib/X11/fonts/75dpi/ does not exist.
Entry deleted from font path.
(WW) The directory /usr/lib/X11/fonts/CID does not exist.
Entry deleted from font path.
(WW) The directory /usr/lib/X11/fonts/75dpi does not exist.
Entry deleted from font path.
(**) FontPath set to 
unix/:7100,/usr/lib/X11/fonts/misc,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi
(==) RgbPath set to /usr/X11R6/lib/X11/rgb
(==) ModulePath set to /usr/X11R6/lib/modules
(++) using VT number 7

(II) Open APM successful
(II) Module ABI versions:
XFree86 ANSI C Emulation: 0.2
XFree86 Video Driver: 0.6
XFree86 XInput driver : 0.4
XFree86 Server Extension : 0.2
XFree86 Font Renderer : 0.4
(II) Loader running on linux
(II) LoadModule: bitmap
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor=The XFree86 Project
compiled for 4.3.0.1, module version = 1.0.0
Module class: XFree86 Font Renderer
ABI class: XFree86 Font Renderer, version 0.4
(II) Loading