debian-japanese@lists.debian.org , your requested information

[Cyril Pearce]

Hello,
We sent you an email a while ago, because you now qualify for a new mortgage.
You could get $300,000 for as little as $600 a month!
Bad credit is no problem, you can pull cash out or refinance.

Please click on this link for free consultation by a mortgage broker:
Start Saving Here 

Best Regards,
Diann CrainFuture pref here

Direct from Canada Phamracy

[Juan Ochoa]

 

 

 

 

 

Sa;ve 7_0% ord.ering onl/ine To`day!
Vi!sit our Site and Sa!ve Big


removemeplease



 

 

 

 

 

 

 

 

 

 

 

Bug#282713: xlibs: Error loading keymap /usr/X11R6/lib/X11/xkb/compiled/server-0.xkm

[Branden Robinson]

tag 282713 + moreinfo
thanks

On Tue, Nov 23, 2004 at 11:01:56PM +0100, Frans Pop wrote:
> Package: xlibs
> Version: 4.3.0.dfsg.1-8
> Severity: normal
> 
> Very recently I noticed this message in my /var/log/XFree86.0.log. Not
> sure if it is since the very latest update in Sarge, but it's not much
> older.
> 
> My keyboard configuration in /etc/X11/XF86Config-4 is:
> Section "InputDevice"
> Identifier  "Generic Keyboard"
> Driver  "keyboard"
> Option  "CoreKeyboard"
> Option  "XkbRules"  "xfree86"
> Option  "XkbModel"  "pc104"
> Option  "XkbLayout" "us"
> EndSection
> 
> If I look in /usr/X11R6/lib/X11/xkb/compiled/, the directory is empty.
> 
> If I manually create the missing file, using 'sudo xkbcomp :0 -xkm', the
> file is created. But if I log out and restart kdm, the file will be deleted
> and the same message appears in the log again.
> 
> I've attached the full log.

In the future, please don't compress the logfiles -- that makes them harder
to view on the debian-x mailing list and in the BTS web interface.

I'm attaching your log file in uncompressed form to this message.

On the subject of your bug report:

I suspect an X client that runs after your session starts is responsible
for the message.  If a keymap could not be compiled for xfree86/pc104/us,
the debian-x mailing list would be drowning in bugs.

Please provide us with the following additional information:

1) The output of "xprop -root | grep XKB" during a normal X session after
   the message "Error loading keymap
   /usr/X11R6/lib/X11/xkb/compiled/server-0.xkm" has appeared in the
   XFree86 log file; and
2) Let us know if you can reproduce this problem in a "minimal" X sesstion
   such as that provided by:
   $ startx $(which x-terminal-emulator) -- :1

-- 
G. Branden Robinson|
Debian GNU/Linux   |Yeah, that's what Jesus would do.
[EMAIL PROTECTED] |Jesus would bomb Afghanistan. Yeah.
http://people.debian.org/~branden/ |

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-8 20040928112350 [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: 28 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.8.20041121-1 ([EMAIL PROTECTED]) (gcc version 
3.3.4 (Debian 1:3.3.4-13)) #2 Sun Nov 21 16:08:34 CET 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: Tue Nov 23 22:49:30 2004
(==) Using config file: "/etc/X11/XF86Config-4"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) |   |-->Monitor "Generic Monitor"
(**) |   |-->Device "Generic Video Card"
(**) |-->Input Device "Generic Keyboard"
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "pc104"
(**) XKB: model: "pc104"
(**) Option "XkbLayout" "us"
(**) XKB: layout: "us"
(==) Keyboard: CustomKeycode disabled
(**) |-->Input Device "Touchpad"
(**) |-->Input Device "Logitech"
(WW) The directory "/usr/lib/X11/fonts/cyrillic" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/lib/X11/fonts/100dpi/" 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/100dpi" does not exist.
Entry deleted from font path.
(WW) `fonts.dir' not found (or not valid) in 
"/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID".
Entry deleted from font path.
(Run 'mkfontdir' on "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID").
(**) FontPath set to 
"/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
(==) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(==) ModulePath set to "/usr/X11R6/lib/modules"
(++) using VT number 7

(WW) Open APM failed (/dev/apm_bios) (No such device)
(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/libbitm

Processed: Re: Bug#282713: xlibs: Error loading keymap /usr/X11R6/lib/X11/xkb/compiled/server-0.xkm

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tag 282713 + moreinfo
Bug#282713: xlibs: Error loading keymap 
/usr/X11R6/lib/X11/xkb/compiled/server-0.xkm
There were no tags set.
Tags added: moreinfo

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Processed: your mail

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> retitle 286164 XPM security fix breaks writing XPM files with absolute path 
> names
Bug#286164: Gimp does not save to .xpm image format
Changed Bug title.

> reassign 286164 libxpm4
Bug#286164: XPM security fix breaks writing XPM files with absolute path names
Bug reassigned from package `gimp' to `libxpm4'.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Bug#277832: #277832 xterm: copy/paste of non-ISO-8859-1 characters between uxterm windows

[Vincent Lefevre]

On 2004-12-17 19:22:15 -0500, Thomas Dickey wrote:
> On Sat, 18 Dec 2004, Vincent Lefevre wrote:
> >When I tried with the latest Debian version, neither of these
> >conditions were satisfied (a click shouldn't be regarded as
> >starting a selection). So, the bug is still there.
> 
> It's been documented that way for (hmm) 15 years (man xterm):
> 
>The default bindings in the VT102 window are:
> 
>~Meta :select-start() \n\
>  ~Meta :select-extend() \n\
> Meta :clear-saved-lines() \n\
>~Ctrl ~Meta :insert-selection(PRIMARY, CUT_BUFFER0) 
>\n\
> 
> Likewise, it's always possible to change those settings in your resource 
> file.  They're _default_ values.

How should I change them? Does select-extend() work without a
select-start() first?

> >Also, if the screen is redrawn (e.g. in Mutt, when entering or
> >quitting the pager, or in screen, when switching windows), the
> >primary selection shouldn't be lost (for instance, xterm should
> >put it in a safe place).
> 
> I cannot imagine where it might, since there's always the possiblity
> of making a new primary selection. Which (old or new) would be the
> correct one?

The primary selection should be kept as long as a new selection isn't
started (from xterm or another application).

-- 
Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / SPACES project at LORIA

Bug#277832: #277832 xterm: copy/paste of non-ISO-8859-1 characters between uxterm windows

[Thomas Dickey]

On Sat, 18 Dec 2004, Vincent Lefevre wrote:


On 2004-12-17 13:27:40 -0500, Thomas Dickey wrote:



When I tried with the latest Debian version, neither of these
conditions were satisfied (a click shouldn't be regarded as
starting a selection). So, the bug is still there.


It's been documented that way for (hmm) 15 years (man xterm):

   The default bindings in the VT102 window are:

   ~Meta :select-start() \n\
 ~Meta :select-extend() \n\
Meta :clear-saved-lines() \n\
   ~Ctrl ~Meta :insert-selection(PRIMARY, CUT_BUFFER0) \n\

Likewise, it's always possible to change those settings in your resource 
file.  They're _default_ values.



Also, if the screen is redrawn (e.g. in Mutt, when entering or
quitting the pager, or in screen, when switching windows), the
primary selection shouldn't be lost (for instance, xterm should
put it in a safe place).


I cannot imagine where it might, since there's always the possiblity of
making a new primary selection.  Which (old or new) would be the correct
one?

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

Bug#277832: #277832 xterm: copy/paste of non-ISO-8859-1 characters between uxterm windows

[Vincent Lefevre]

On 2004-12-17 13:27:40 -0500, Thomas Dickey wrote:
> There aren't that many choices - the primary selection is only owned by 
> one application at a time.  I reduced(*) xterm's tendency to give it up, 
> but
> 
>   if another application asserts it, or
> 
>   you start a new selection, or

The first point is a particular case of the second point.

>   something updates the xterm window where it's highlighted for
>   the selection
> 
> then the primary selection is lost - there's no standard mechanism to get 
> it back again.

When I tried with the latest Debian version, neither of these
conditions were satisfied (a click shouldn't be regarded as
starting a selection). So, the bug is still there.

Also, if the screen is redrawn (e.g. in Mutt, when entering or
quitting the pager, or in screen, when switching windows), the
primary selection shouldn't be lost (for instance, xterm should
put it in a safe place).

-- 
Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / SPACES project at LORIA

Bug#284965: X11/Mouse Problems Solved

[Otavio Salvador]

|| On Fri, 17 Dec 2004 15:34:41 -0500
|| Alan McConnell <[EMAIL PROTECTED]> wrote: 

am> I don't have to recapitulate what needs to be fixed -- the inadequacies
am> are apparent from the numbers 1, 2, and 3 above.  I hope that attention
am> will be paid and efforts will be made to make a standard tool
am> for making -- at least on a vanilla system, which mine is -- a
am> workable XF86Config file.

$: apt-cache show xdebconfigurator
Package: xdebconfigurator
Priority: optional
Section: x11
Installed-Size: 83
Maintainer: Debian Edu Developers 
Architecture: all
Version: 1.14
Depends: debconf (>= 0.5) | debconf-2.0, perl-modules, discover1 | discover, 
kudzu
Recommends: read-edid
Suggests: hwinfo (>= 4.27-0), kudzu-vesa, detect
Filename: pool/main/x/xdebconfigurator/xdebconfigurator_1.14_all.deb
Size: 22784
MD5sum: 586d96d7bb052bdb7f5f19537732db2f
Description: A script used with debconf to autoconfigure xserver-xfree86
 A script-package used in conjunction with debconf to autoconfigure
 xserver-xfree86.  This script is supposed to help setup X correctly
 even with DEBIAN_FRONTEND set to noninteractive.

We already have one. It works in most of cases.

Another issue is use the suggested packages to configure X server so
it does some detection too.

You are free to help us to improve both tools ;-)

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
-
"Microsoft gives you Windows ... Linux gives
 you the whole house."


pgpMm9vPjiKmH.pgp
Description: PGP signature

Bug#284965: X11/Mouse Problems Solved

[Alan McConnell]

The Subject says it; you can delete the 284965 ticket.

However, I wish to relate my experiences with this problem, as it
may help the Debian team help others avoid similar problems in the
future.

[ It is probably useful to mention that I have been running Linux
exclusively at home and at work since 1993, and I have had my problems
with the X11 systems of that time:  I have had to adjust the huge
mode lines of those days and edit e.g. the clock speeds till fuzzy
lines of ill-sychronized horizontal refreshes gradually settled
down into a semblance of order(this on all manner of monitors, including
at first ancient Hercules displays) ]

Here is the sequence of difficulties I experienced, all, as events
showed, with the /etc/X11/XF86Config-4 file:
1.  The Woody installer didn't put any "Modes" in any of the Display
SubSections of the Screen section.  Fortunately I had saved my
Red Hat XF86Config file, and since my errors had to do with no
screens found, I decided it wouldn't hurt to put Modes in.  But
that didn't help. 
2.  As I reported in my immediately previous message, I was able
to find out, through googling with lynx,  that the option 
"UseFBDev" was causing, for whatever reason, the X11 to fail
completely.  After that Option, in the Video Card section, was
commented out, I got at least some part of the X display.(Tnank
goodness I left the Mode lines in!).
3.  The mouse was, however, still flakey.  At the suggestion of
a friend, who has been doing Debian for several years, I got
rid of the Generic Mouse stanza, with its /dev/input/mice and
its ImPS/2 Protocol.

Only after this grappling and groping, which involved many many
reruns of dpkg-reconfigure, plus several tries with the various
tools for making XF86Config files that exist, was I -- with
afore-mentioned help -- able finally to achieve a rock-solid
X11 display.

I don't have to recapitulate what needs to be fixed -- the inadequacies
are apparent from the numbers 1, 2, and 3 above.  I hope that attention
will be paid and efforts will be made to make a standard tool
for making -- at least on a vanilla system, which mine is -- a
workable XF86Config file.

Best wishes,

Alan McConnell

-- 
Alan McConnell :  http://patriot.net/users/alan
   We live in a world that is full of mistaken policies, but they
   are not mistaken for their supporters.(George Stigler)

Bug#286068: xterm "iconFont" and faceName

[Thomas Dickey]

On Fri, Dec 17, 2004 at 11:30:18AM +0100, [EMAIL PROTECTED] wrote:
> Package: xterm
> Version: 4.3.0.dfsg.1-8
> 
> xterm does/can not use any "iconFont" (at least it is not visible) if you
> set XTerm.VT100.faceName to a FreeType font. It also does not use (a
> minimized version of) the faceName font.

This is still an issue in #197 (I considered doing that, but put it on my
list for #198, worked on porting/testing).

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgphuVmP2FOlo.pgp
Description: PGP signature

Bug#282708: xserver-xfree86: repeatable server crash related to xscreensaver, full-screen sdl, and kde

[Branden Robinson]

retitle 282708 xserver-xfree86: [ati/radeon] SEGV related to xscreensaver, 
full-screen SDL apps, KDE, and attempted keyboard grabs while X VT inactive on 
Radeon R200 BB [Radeon All in Wonder 8500DV] rev 0
tag 282708 + upstream moreinfo
thanks

On Tue, Nov 23, 2004 at 10:49:57PM +0100, Yann Dirson wrote:
> Package: xserver-xfree86
> Version: 4.3.0.dfsg.1-8
> Severity: important
> 
> The crash is 100% reproducible on my box, but I feel the context is still a
> bit too wide, given the large software to reproduce.

I'm sorry it has taken a while to get back to you about this.

> How to get it:
> 
> - run an X server with KDE (fvwm won't do), either from gdm or from startx
> with a simple "startkde" in the .xsession
> 
> - run xscreensaver in the background
> 
> - arrange to have xscreensaver activated while an SDL app (eg. wesnoth or
> pachi) is running full-screen (the same apps in windowed mode won't do), and
> you have switched to another console (either X or text).  I usually do that
> by running the app in windowed mode, running "sleep 10; xscreensaver-command
> -lock" in an xterm, and switching the app to fullscreen, then to another VT
> during the sleep time.
> 
> 
> If I do not switch VT, I see xscreensaver complaining that it cannot grab
> the keyboard (I presume this is where the full-screen SDL part thing comes
> into action), but X still survives.
> 
> If I switch to the text console from which I launched startx, I can see the
> "SetGrabKeysState - disabled" message appearing quite shortly before the
> crash.
> 
> I cannot see how KDE interacts with all this.  I could even reproduce from a
> freshly-created user account, running kde rom startx, and skipping the
> configuration wizard, to make sure there is no special config item involved.

Can anyone else reproduce this?

(In the future, please include your XF86Config-4 in bug reports against
xserver-xfree86{,-dbg}.)

[The following is a form letter.]

Can you reproduce the problem with xserver-xfree86-dbg?  Install the
package and tell debconf you want to use that X server.  Then restart the X
server and try to reproduce the bug (hopefully, this is easy).  If it
doesn't crash, let us know.  If a bug is in the XFree86 X server's ELF
module loader, you likely won't see it when you use the debugging server.
We still want to know that information.  If it does crash, become root,
enable core dumps ("ulimit -c unlimited" in bash), start the X server as
root and reproduce the crash again:

# startx $(which x-terminal-emulator) -- :1

(If no X server is running at DISPLAY=:0, you can leave off the "-- :1"
part).

This will launch the X server running a lone terminal client with no window
manager.  Run the client that provokes the crash from the terminal prompt.
If you can only reproduce the crash with a more elaborate environment, then
go ahead and produce that environment.  Be sure to tell us what you did to
get it (e.g., launching GNOME or KDE, setting up a particular screensaver,
running an SDL game -- whatever it takes).  It is not wise to run X clients
as root except when absolutely necessary, so if the session doesn't crash,
don't leave it running.  Shut it down as soon as you can.  It might also be
a good idea to scrub out root's home directory (/root) of hidden files and
directories created by desktop environments and whatever X clients you
attempted to reproduce the crash with.  Look for /root/.gnome /root/.kde,
and so forth.

If the X server crashes, it should leave a core dump in /etc/X11.

We then run the GNU Debugger, GDB, on the core file and executable.  We're
interested in a backtrace of execution.  The X server has a signal handler
in it so it can do things like exit gracefully (restoring the text console,
and so forth), so we're not actually interested in all the stack frames --
just those "above" the signal handler.

Here's an example GDB session I logged after provoking an artificial server
crash (with "kill -SEGV").

  % gdb $(which XFree86-debug) core
  GNU gdb 6.1-debian
  Copyright 2004 Free Software Foundation, Inc.
  GDB is free software, covered by the GNU General Public License, and you are
  welcome to change it and/or distribute copies of it under certain conditions.
  Type "show copying" to see the conditions.
  There is absolutely no warranty for GDB.  Type "show warranty" for details.
  This GDB was configured as "i386-linux"...Using host libthread_db library 
"/lib/libthread_db.so.1".

  Core was generated by `/usr/X11R6/bin/X :1'.
  Program terminated with signal 6, Aborted.
  Reading symbols from /usr/lib/libfreetype.so.6...done.
  Loaded symbols for /usr/lib/libfreetype.so.6
  Reading symbols from /usr/lib/libz.so.1...done.
  Loaded symbols for /usr/lib/libz.so.1
  Reading symbols from /lib/libm.so.6...done.
  Loaded symbols for /lib/libm.so.6
  Reading symbols from /lib/libc.so.6...done.
  Loaded symbols for /lib/libc.so.6
  Reading symbols from /lib/ld-linux.so.2...done.
  Loaded symbols for /lib/ld-linux.so.2
  #0

Processed: Re: Bug#282708: xserver-xfree86: repeatable server crash related to xscreensaver, full-screen sdl, and kde

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> retitle 282708 xserver-xfree86: [ati/radeon] SEGV related to xscreensaver, 
> full-screen SDL apps, KDE, and attempted keyboard grabs while X VT inactive 
> on Radeon R200 BB [Radeon All in Wonder 8500DV] rev 0
Bug#282708: xserver-xfree86: repeatable server crash related to xscreensaver, 
full-screen sdl, and kde
Changed Bug title.

> tag 282708 + upstream moreinfo
Bug#282708: xserver-xfree86: [ati/radeon] SEGV related to xscreensaver, 
full-screen SDL apps, KDE, and attempted keyboard grabs while X VT inactive on 
Radeon R200 BB [Radeon All in Wonder 8500DV] rev 0
There were no tags set.
Tags added: upstream, moreinfo

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Bug#285782: closing duplicate fixed bug

[Branden Robinson]

close 285782
# An easy workaround in a conffile existed.  That ain't "grave".
severity 285782 important
retitle 285150 xdm: typo in /etc/X11/xdm/Xstartup prevents login
merge 285150 285782
thanks

This bug was fixed in xdm 4.3.0.dfsg.1-10.

[The following is a form letter.]

Hello,

You recently filed a duplicate bug report against a Debian package; that
is, the problem had already been reported.

While there is often nothing inherently wrong with doing so, the filing of
duplicate reports can cause Debian package maintainers to spend time
performing triage and maintenance operations on bug reports (e.g.,
instructing the Debian Bug Tracking System to merge the duplicates) that
could otherwise be spent resolving problems and doing other work on the
package.

One very good way to file bugs with the Debian Bug Tracking System is to
use the "reportbug" package and command of the same name.  A very nice
feature of reportbug is that, if the machine where you run it has network
access to the World Wide Web, it can query the Debian Bug Tracking System
and show you existing reports.  This reduces the chance that you'll file a
duplicate report, and offers you the option of adding follow-up information
to an existing bug report.  This is especially valuable if you have unique
information to add to an existing report, because this way information
relevant to the problem is gathered together in one place as opposed to
being scattered among multiple, duplicate bug reports where some facts may
be overlooked by the package maintainers.  The reportbug program also does
a lot of automatic information-gathering that helps package maintainers to
understand your system configuration, and also ensures that your message to
the Debian Bug Tracking System is well-formed so that it is processed
correctly by the automated tools that manage the reports.  (If you've ever
gotten a "bounce" message from the Debian Bug Tracking System that tells
you your message couldn't be processed, you might appreciate this latter
feature.)

Therefore, I strongly urge you to give "reportbug" a try as your primary
bug reporting tool for the Debian System.  (If you already do use
"reportbug", please see below.)

One way to install reportbug is with "apt-get"; for
example:

  # apt-get install reportbug

The "reportbug" command has a few different modes that cater to different
levels of user expertise.  If this message has contained a lot of jargon
that is unfamiliar to you, you likely want to use reportbug's "novice"
mode; here's one way to do that.

  $ reportbug --mode=novice
  Please enter the name of the package in which you have found a problem,
  or type 'other' to report a more general problem.
  >

If you're more sophisticated, or if you are not using the released version
of Debian ("stable"), but instead Debian "testing" or "unstable", you
should use reportbug's standard mode.

  $ reportbug
  Please enter the name of the package in which you have found a problem,
  or type 'other' to report a more general problem.
  >

The reportbug command is extensively documented in its usage message and
manual page.  Commands to view these pieces of documentation are:

  $ reportbug --help | more
  $ man reportbug

(The output of the above commands has been omitted from this message.)

If you do use reportbug, but are so daunted by the large number of bugs
already filed against a package that you feel you cannot search for a
duplicate, please note that reportbug has a (f)ilter feature that enables
you to use a keyword search to limit the number of bugs reported.  (If
you're feeling ambitious, the filter feature also accepts a regular
expression.)  For example, if you'd like to report a SEGV (segfault), you
might filter based on the term "SEGV".  If you're having trouble upgrading
a package, you might filter based on "upgrad" (to catch both "upgrade" and
"upgrading").  Some package maintainers retitle bugs to contain keywords so
as to facilitate better filtering and convey more useful information, since
a bug report with a title of "broken" or the like is not very useful to
anyone.

We appreciate you taking the time to help package maintainers serve you
better by reducing the amount of time they need to spend coping with
duplicate bug reports.

Thanks for using the Debian system!

-- 
G. Branden Robinson| If the jury can count higher than
Debian GNU/Linux   | two, the case will fail.
[EMAIL PROTECTED] | -- Tom Lane, on Forgent's claim of
http://people.debian.org/~branden/ |a patent on JPEG


signature.asc
Description: Digital signature

Bug#280118: xterm: alt-. gives wrong signal to zsh

[Branden Robinson]

On Fri, Dec 10, 2004 at 06:10:23AM -0500, Thomas Dickey wrote:
> On Fri, Dec 10, 2004 at 03:27:11AM -0500, Branden Robinson wrote:
> > > > Upgrading to xterm 4.3.0 caused the (often used) alt-. to send the 
> > > > wrong signal
> > > > to zsh (4.0.4 and later) in viins mode.  Alt-. is used in zsh to insert 
> > > > the
> > > > last argument of the previous cmd line. 
> > > > 
> > > > The behaviour is as expected in emacs-mode. More importantly it is as 
> > > > expected
> > > > in viins mode in any other shell or the console. Downgrading to 4.0.4 
> > > > `fixed'
> > > > the problem.
> > > 
> > > That's one bug report (but it's actually against the X libraries).
> > 
> > Any idea which one?  Xlib, I guess?  Can you elaborate a bit on what you
> > think is wrong?
> 
> ugh - I should write this one down.  Lacking more specific information, it
> sounds as if he's running into the one that was confusing meta and alt. 
> googling for "Debian" and "metaSendsEscape", I see for instance #260232,
> #215034.

Well, #260232 was closed a few months ago, and it looks like #215034 should
be:

  Meta-keystrokes are ignored by xterm from debian unstable. They work
  with current xterm patch (179).

Debian unstable has had a version of XTerm more recent than #179 since
4.3.0.dfsg.1-5 (16 Jun 2004) at the latest, and possibly as far back as
4.3.0.dfsg.1-2 (25 May 2004).

I am therefore closing #215034.  If the problem persists, it's likely
caused by something else.

> (I don't know how far along your resolution of it is - thought the number
> of new reports had gone down).

I'm not sure I quite understand you here, but I do not that I am very
confused by the current report if two similar reports were already fixed.

-- 
G. Branden Robinson|Imagination was given man to
Debian GNU/Linux   |compensate for what he is not, and
[EMAIL PROTECTED] |a sense of humor to console him for
http://people.debian.org/~branden/ |what he is.


signature.asc
Description: Digital signature

Bug#215034: marked as done (xterm: resource setting 'XTerm*metaSendsEscape: true' has no effect)

[Debian Bug Tracking System]

Your message dated Fri, 17 Dec 2004 13:58:16 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#280118: xterm: alt-. gives wrong signal to zsh
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; 9 Oct 2003 22:41:57 +
>From [EMAIL PROTECTED] Thu Oct 09 17:41:56 2003
Return-path: <[EMAIL PROTECTED]>
Received: from mailout08.sul.t-online.com [194.25.134.20] 
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1A7jTn-0002G5-00; Thu, 09 Oct 2003 17:41:56 -0500
Received: from fwd01.aul.t-online.de 
by mailout08.sul.t-online.com with smtp 
id 1A7f2G-0003Cm-06; Thu, 09 Oct 2003 19:57:12 +0200
Received: from abrasax.taupan.ath.cx ([EMAIL PROTECTED]) by 
fmrl01.sul.t-online.com
with esmtp id 1A7f1u-13IZ3w0; Thu, 9 Oct 2003 19:56:50 +0200
Received: from friedel by abrasax.taupan.ath.cx with local (Exim 3.36 #1 
(Debian))
id 1A7f1s-0003Jp-00; Thu, 09 Oct 2003 19:56:48 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Friedrich Delgado Friedrichs <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: XTerm*metaSendsEscape: true has no effect
Reply-To: [EMAIL PROTECTED]
X-Mailer: reportbug 2.34
Date: Thu, 09 Oct 2003 19:56:48 +0200
Message-Id: <[EMAIL PROTECTED]>
Sender: Friedrich Delgado Friedrichs <[EMAIL PROTECTED]>
X-Seen: false
X-ID: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-5.0 required=4.0
tests=HAS_PACKAGE
version=2.53-bugs.debian.org_2003_10_09
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_10_09 
(1.174.2.15-2003-03-30-exp)

Package: xterm
Version: 4.2.1-12.1
Severity: normal

Meta-keystrokes are ignored by xterm from debian unstable. They work
with current xterm patch (179). Try with xemacs -nw, or whatever
pleases you.

That's all I can say. If you have questions, please ask.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux abrasax 2.4.20 #5 Fri May 2 19:26:52 CEST 2003 i686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8

Versions of packages xterm depends on:
ii  libc6 2.3.2-8GNU C Library: Shared libraries an
ii  libfreetype6  2.1.5-2FreeType 2 font engine, shared lib
ii  libncurses5   5.3.20030719-2 Shared libraries for terminal hand
ii  libxaw7   4.2.1-12.1 X Athena widget set library
ii  xlibs 4.2.1-12.1 X Window System client libraries

-- no debconf information


---
Received: (at 215034-done) by bugs.debian.org; 17 Dec 2004 18:58:18 +
>From [EMAIL PROTECTED] Fri Dec 17 10:58:18 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 1CfNIv-J2-00; Fri, 17 Dec 2004 10:58:17 -0800
Received: by sisyphus.deadbeast.net (Postfix, from userid 1000)
id D2E2B68C413; Fri, 17 Dec 2004 13:58:16 -0500 (EST)
Date: Fri, 17 Dec 2004 13:58:16 -0500
From: Branden Robinson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Bug#280118: xterm: alt-. gives wrong signal to zsh
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL 
PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="jho1yZJdad60DJr+"
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+20040907i
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 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 


--jho1yZJdad60DJr+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Dec 10, 2004 at 06:10:23AM -0500, Thomas Dickey wrote:
> On Fri, Dec 10, 2004 at 03:27:11AM -0500, Branden Robinson wrote:
> > > > Upgrading to xterm 4.3.0 caused the (often used) alt-. to send the =
wrong signal
> > > > to zsh (4.0.4 and later) in viins mode.  Alt-.

Processed: closing duplicate fixed bug

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> close 285782
Bug#285782: xdm fails to login due to error in Xstartup
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to Martin Stolle <[EMAIL PROTECTED]>

> # An easy workaround in a conffile existed.  That ain't "grave".
> severity 285782 important
Bug#285782: xdm fails to login due to error in Xstartup
Severity set to `important'.

> retitle 285150 xdm: typo in /etc/X11/xdm/Xstartup prevents login
Bug#285150: Typo in /etc/X11/xdm/Xstartup prevents login
Changed Bug title.
(By the way, that Bug is currently marked as done.)

> merge 285150 285782
Bug#285150: xdm: typo in /etc/X11/xdm/Xstartup prevents login
Bug#285782: xdm fails to login due to error in Xstartup
Mismatch - only Bugs in same state can be merged:
Values for `severity' don't match:
 #285150 has `serious';
 #285782 has `important'

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Bug#277832: #277832 xterm: copy/paste of non-ISO-8859-1 characters between uxterm windows

[Thomas Dickey]

On Fri, 17 Dec 2004, Vincent Lefevre wrote:


But I don't want to use the clipboard for that, as it doesn't work
with the middle-click with other applications (and it doesn't seem
to always work).


There aren't that many choices - the primary selection is only owned by 
one application at a time.  I reduced(*) xterm's tendency to give it up, 
but


if another application asserts it, or

you start a new selection, or

something updates the xterm window where it's highlighted for
the selection

then the primary selection is lost - there's no standard mechanism to get 
it back again.


(*) some minor improvements are possible, but I don't believe we're
talking about those.

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

Bug#277832: #277832 xterm: copy/paste of non-ISO-8859-1 characters between uxterm windows

[Vincent Lefevre]

On 2004-12-16 17:55:47 -0500, Thomas Dickey wrote:
> Actually I did fix the hard part. The remainder is user-preferences
> which can be easily set with resources.

How? I didn't see anything new in the man page.

> In #197, I also added a section to the manpage describing the use of
> the clipboard - you should try that (sounds as if your click in the
> other window is asserting the primary selection, e.g,. by moving the
> mouse a little as you do the click). Once the source has lost the
> primary selection, it can't be fixed. The clipboard selection is
> less volatile.

But I don't want to use the clipboard for that, as it doesn't work
with the middle-click with other applications (and it doesn't seem
to always work).

-- 
Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / SPACES project at LORIA

Bug#286104: /usr/X11R6/bin/XFree86: Seemingly random server crash

[Lonnie Sutton]

Package: xserver-xfree86
Version: 4.3.0.dfsg.1-9
Severity: normal
File: /usr/X11R6/bin/XFree86

This system is on 24/7. When last used around 11 PM last evening, all
was fine. When I sat down at system at 7:45 AM, the server had crashed
and I was asked to file a bug report, which this is. The only change is
that I have suffered the XDM bug, which I get around by logging in from
a console and using startx. The only other recent change is the
replacing of my old Logitech trackman mouse with a new Logitech trackman
wheel mouse, which required an update of XFree86Config-4. I also
installed gpm to use the mouse on the console, and those changes seem to
be working just fine. This is the first time this server has crashed,
though several times recently, the server has randomly cycled when not
in active use by me, leaving me at the xdm login screen, which, as
reported above, is currently not working as it should, i.e., each login
attempt results in a quick cycling back to the xdm login screen, which I
then work around by using "control-alt-backspace" to get to a console,
where I log in and then use startx to start the xserver, and use the
system as I normally do. The random recycles and this crash happened
while I was not actively using the system, and therefore the screensaver
was activated, if that helps.

Not sure how useful the above info is, or what the logs reveal, but hope
that it is useful to the great folks at Debian.


-- Package-specific info:
Contents of /var/lib/xfree86/X.roster:
xserver-xfree86

/etc/X11/X target does not match checksum in /var/lib/xfree86/X.md5sum.

X server symlink status:
lrwxrwxrwx  1 root root 20 2003-04-30 14:29 /etc/X11/X -> /usr/bin/X11/XFree86
-rwxr-xr-x  1 root root 1745740 2004-12-09 09:03 /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 NV25 [GeForce4 Ti 
4200] (rev a3)

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

XFree86 X server configuration file status:
-rw-r--r--  1 root root 3344 2004-12-08 19:37 /etc/X11/XF86Config-4

Contents of /etc/X11/XF86Config-4:
# XF86Config-4 (XFree86 X server configuration file) 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"
FontPath"unix/:7100"# local font server
# if the local font server has problems, we can fall back on these
FontPath"/usr/lib/X11/fonts/Type1"
FontPath"/usr/lib/X11/fonts/CID"
FontPath"/usr/lib/X11/fonts/Speedo"
FontPath"/usr/lib/X11/fonts/misc"
FontPath"/usr/lib/X11/fonts/cyrillic"
FontPath"/usr/lib/X11/fonts/100dpi"
FontPath"/usr/lib/X11/fonts/75dpi"
FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"


EndSection

Section "Module"

Load"bitmap"
Load"dbe"
Load"ddc"

Load"extmod"
Load"freetype"
Load"glx"
Load"int10"
Load"record"
Load"speedo"
Load"type1"
Load"vbe"
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/gpmdata"
Option  "Protocol"  "IMPS/2"
Option  "Emulate3Buttons"   "true"
Option  "ZAxisMapping"  "4 5"
EndSection

Section "InputDevice"
Identifier  "Generic Mouse"
Driver  "mouse"
Option  "SendCoreEvents""true"
Option  "Device""/dev/input/mice"
Option  "Protocol"  "ImPS/2"
Option  "Emulate3Buttons"   "true"
Option  "ZAxisMapping"  "4 5"
EndSection

Section "Device"

Re: Xabre SiS 330 (xserver-xfree86 4.2.1-15)

[Michelle Konzack]

Good evening Thomas, 

Am 2004-12-17 10:43:44, schrieb Thomas Winischhofer:

> SiS330 support was never "dropped"/"restored". I have no idea what man 
> pages Michelle read. Perhaps one of the versions she tried contained a 
> "backported" newer version of the driver.

Wired, because the manpage "sis" was from http://www.XFree86.org/>
and was from Version 4.1.0.

This was what me iritating because there is no SIS330 Support in
Version 4.1.0 from WOODY.

Now I have selled this Crappy SIS746 Mainboard on eBay.

(Requires the PCI module SIS5513 to activate the NIC SIS900 which is
crap and WOODY can not be installed on it because the missing SIS5513
in bf24)

> Thomas

Greetings
Michelle

-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/ 
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSM LinuxMichi
0033/3/8845235667100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature

Bug#261993: mga pixel clock increase works for G400 also

[Jeff King]

On Thu, 9 Dec 2004, Branden Robinson wrote:


I reckon that guess was wrong, at least for MGA G550 users.  If other
Matrox cards can tolerate modes with lower pixel clocks, we'll have to add
case-dependent logic for setting the pixel clock.  This won't be too hard,
but until I have data from such users, I'm going to just raise the floor
for the pixel clock across the board.


Just to chime in as one "such user": I have a Matrox G400. I tried
running all-demo with 4.3.0.dfsg.1-9 and got the same crash. Moving to
-10 (with the pixel clock increase) fixed the problem.

-Peff

Bug#286067: xterm iconFont and utf8 support

[Thomas Dickey]

On Fri, Dec 17, 2004 at 11:30:19AM +0100, [EMAIL PROTECTED] wrote:
> Package: xterm
> Version: 4.3.0.dfsg.1-8
> 
> XTerm.VT100.iconFont does not correctly support UTF8: the font is not used
> if xterm is started with UTF8 on but you can switch to UTF8 by tek menu
> _after_ you started the xterm. Therfore the font usage is also
> inconsistent.

This was fixed in patch #197 (package is on the to-do list).

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgpJ6Xe4YJqDc.pgp
Description: PGP signature

Bug#284448: xserver-xfree86: xserver (ATI or Radeon something 7500) crashes on variouslaunches of programcs from within X.

[Thomas Winischhofer]

This looks like an Xlibs bug.

---

#10 0x0892a025 in fs_read_list_info (fpe=0x8bcf350, blockrec=0x8d65198)

   at fserve.c:2376

binfo = 0x8d651b4
rep = (fsListFontsWithXInfoReply *) 0x8bcf808
buf = 0x10c3a3fc  <---
conn = 0x8bcf378
pi = (fsPropInfo *) 0x8bcf83c
po = (fsPropOffset *) 0x8bcf844
pd = 0x8bcf894  <--
ret = 1
err = 146600824

---

The source of Xfont/fc/fserve.c at this point (in fs_read_list_info) 
looks like this:


if (conn->fsMajorVersion <= 1)
{
memcpy (binfo->name, buf, rep->nameLength);
buf += _fs_pad_length (rep->nameLength);
}
pi = (fsPropInfo *) buf;
buf += SIZEOF (fsPropInfo);
po = (fsPropOffset *) buf;
buf += pi->num_offsets * SIZEOF (fsPropOffset);
pd = (pointer) buf; <--
buf += pi->data_len; <--
if (conn->fsMajorVersion > 1)
{
memcpy (binfo->name, buf, rep->nameLength);
buf += _fs_pad_length (rep->nameLength);
}

---

From the fact that "pd" is set to a legal value in the debugging 
output, while "buf" (after adding "pi->data_len") is "out of bounds" I 
would very much assume that "pi->data_len" contains garbage.


As regards why it does this, I have no idea.

Are these patches in the Debian SVN:

http://freedesktop.org/cgi-bin/viewcvs.cgi/xlibs/Xfont/fc/fserve.c?r1=3.22&r2=3.22.2.1
http://freedesktop.org/cgi-bin/viewcvs.cgi/xlibs/Xfont/fc/fserve.c?r1=3.23&r2=3.24
http://cvsweb.xfree86.org/cvsweb/xc/lib/font/fc/fserve.c.diff?r1=3.26&r2=3.27

Thomas

--
Thomas Winischhofer
Vienna/Austria
thomas AT winischhofer DOT net *** http://www.winischhofer.net
twini AT xfree86 DOT org

Re: xdm sessreg failure

[Adam D. Barratt]

On Friday, December 17, 2004 10:14 AM, Sven Bachmann <[EMAIL PROTECTED]>
wrote:

> I just upgraded to xdm 4.3.0.dfsg.1-9 and after a restart my window
> manager won't come up.
> So I read the xdm log and found out, that sessreg wasn't called
> correctly.
>
> In /etc/X11/xdm/Xstartup at line 24 there is missing an "\" at the
> end of the line. So not all parameters where passed to sessreg.

This is indeed a known problem with -9 - see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=285151 and
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=285150.

The bug was corrected in -10, which was uploaded yesterday, but
unfortunately hasn't hit the mirrors yet.

Regards,

Adam

xdm sessreg failure

[Sven Bachmann]

Hello,

I just upgraded to xdm 4.3.0.dfsg.1-9 and after a restart my window
manager won't come up.
So I read the xdm log and found out, that sessreg wasn't called
correctly.

In /etc/X11/xdm/Xstartup at line 24 there is missing an "\" at the
end of the line. So not all parameters where passed to sessreg.

The correct line must be:
exec sessreg -a -l "$DISPLAY" -u /var/run/utmp \
 -x /etc/X11/xdm/Xservers "$USER"

Could you please verify that?

Thank you.
  Sven

Bug#286067: xterm iconFont and utf8 support

[bernhard . sammer]

Package: xterm
Version: 4.3.0.dfsg.1-8

XTerm.VT100.iconFont does not correctly support UTF8:
the font is not used if xterm is started with UTF8 on but you can switch
to UTF8 by tek menu _after_ you started the xterm. Therfore the font usage
is also inconsistent.

i.e. export LANG=en_US.UTF8. Start xterm and it does/can
not use the default font "nil2" if the XTerm.VT100.locale uses
UTF8 (or XTerm.VT100.utf8 is set).

(to prove this use a window manager that supports
icons i.e. fvwm and set the X resource "XTerm.VT100.activeIcon: true".)



Disclaimer:
Diese Nachricht dient ausschließlich zu Informationszwecken und ist nur
für den Gebrauch des Empfängers bestimmt.

This message is only for informational purposes and is intended solely
for the use of the addressee.
 

Bug#286068: xterm "iconFont" and faceName

[bernhard . sammer]

Package: xterm
Version: 4.3.0.dfsg.1-8

xterm does/can not use any "iconFont" (at
least it is not visible) if you set XTerm.VT100.faceName to a FreeType
font. It also does not use (a minimized version of) the faceName font.

(to prove this use a window manager that supports
icons i.e. fvwm and set the X resource "XTerm.VT100.activeIcon: true".)



Disclaimer:
Diese Nachricht dient ausschließlich zu Informationszwecken und ist nur
für den Gebrauch des Empfängers bestimmt.

This message is only for informational purposes and is intended solely
for the use of the addressee.
 

Processed: Fix severities and merge

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> package xfs
Ignoring bugs not assigned to: xfs

> severity 286043 serious
Bug#286043: xfs: init.d scrip has bad "test[]" paramiters.
Severity set to `serious'.

> merge 286043 285133
Bug#285133: Typo in XFS startup script
Bug#286043: xfs: init.d scrip has bad "test[]" paramiters.
Bug#285154: typo in /etc/init.d/xfs prevents it from setting up X font server 
socket directory
Merged 285133 285154 286043.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Re: Xabre SiS 330 (xserver-xfree86 4.2.1-15)

[Thomas Winischhofer]

Branden said:
> I'm afraid we probably can't help you with the whys and wherefores of
> driver support of specific models of display adapter, but the author
> of the driver in question might be able to: his name is Thomas
> Winischhofer, and his webpage about his SiS driver for XFree86/XOrg is
> at the following site:
>
> http://www.winischhofer.at/linuxsisvga.shtml
>
> Note that according to this site, the SiS 330 *is* supported.  Perhaps
> support for it was dropped for a while but later restored.  The
> version of the SiS driver in Debian's XFree86 4.3.0 packages is quite
> a bit newer than the stock XFree86 4.3.0 version.

The website offers each a version of the most current driver for ALL 
versions of XFree86/X.org since 4.1.0.


See the "Debian" paragraph in the download section.

SiS330 support was never "dropped"/"restored". I have no idea what man 
pages Michelle read. Perhaps one of the versions she tried contained a 
"backported" newer version of the driver.


Thomas

--
Thomas Winischhofer
Vienna/Austria
thomas AT winischhofer DOT net *** http://www.winischhofer.net
twini AT xfree86 DOT org

Bug#286043: xfs: init.d scrip has bad "test[]" paramiters.

[Adam D. Barratt]

package xfs
close 286043
merge 286043 285133
thanks

On Friday, December 17, 2004 3:33 AM, Mike Mestnik) (the Archmage forever
<[EMAIL PROTECTED]> wrote:

> Package: xfs
> Version: 4.3.0.dfsg.1-9
> Severity: normal
>
> Line 24 of /etc/init.d/xfs should read...
> if [ -e $SOCKET_DIR -a ! -d $SOCKET_DIR ]; then
> and not...
> if [ -e $SOCKET_DIR && [ ! -d $SOCKET_DIR ]; then
> The latter is clearly missing an ']'.

Indeed, but the proper way to correct it would be to add the ']', not to
make the test non-POSIX-compliant. :-)

if [ -e $SOCKET_DIR ] && [ ! -d $SOCKET_DIR ]; then

(possibly quoting $SOCKET_DIR if there's any chance of it being empty).

In fact, that's exactly what was done in 4.3.0.dfsg.1-10, to close the
previous report of this bug (#285133). Closing this report as the fixed
packages are already in the archive (and will be on mirrors once the daily
pulse is fixed).

Regards,

Adam

Processed: Re: Bug#286043: xfs: init.d scrip has bad "test[]" paramiters.

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> package xfs
Ignoring bugs not assigned to: xfs

> close 286043
Bug#286043: xfs: init.d scrip has bad "test[]" paramiters.
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to [EMAIL PROTECTED]

> merge 286043 285133
Bug#285133: Typo in XFS startup script
Bug#286043: xfs: init.d scrip has bad "test[]" paramiters.
Mismatch - only Bugs in same state can be merged:
Values for `severity' don't match:
 #285133 has `serious';
 #286043 has `normal'

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

X Strike Force XFree86 SVN property change: propchange - r2079 svn:log

[X Strike Force SVN Repository Admin]

Author: branden
Revision: 2079
Property Name: svn:log

New Property Value:
The loading of srvr_ctrl(xfree86) symbol definitions for Sun keyboards
was broken and made such keyboards unusable.  Thanks to Henry Margies
for reporting this bug.  (Closes: #236086)