Bug#238407: XFree86 crashes on PPC in 0x1072260c in AccessXCancelRepeatKey (xkbi=0x0, key=64 '@') at xkbAccessX.c:387

2004-03-24 Thread Don Armstrong
tags 238407 patch
thanks

I'm currently testing[1] the attached patch, which seems to be clear of
the licensing issues affecting X, but regardless, it's extreemly
trivial.

I will update with results shortly.


Don Armstrong

1: Which seems to amount to running X until it crashes, since I
haven't been able to reliably trigger the core...
-- 
Ban cryptography! Yes. Let's also ban pencils, pens and paper, since
criminals can use them to draw plans of the joint they are casing or
even, god forbid, create one time pads to pass uncrackable codes to
each other. Ban open spaces since criminals could use them to converse
with each other out of earshot of the police. Let's ban flags since
they could be used to pass secret messages in semaphore. In fact let's
just ban all forms of verbal and non-verbal communication -- let's see
those criminals make plans now!

http://www.donarmstrong.com
http://www.anylevel.com
http://rzlab.ucr.edu
$Id$

Patch stolen from 
http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/dix/events.c.diff?r2=3.52r1=3.51diff_format=u

--- xc/programs/Xserver/dix/events.c2004/01/12 17:04:52 3.51
+++ xc/programs/Xserver/dix/events.c2004/01/23 07:23:34 3.52
@@ -991,7 +991,8 @@
 
 #ifdef XKB
 /* Fix for key repeating bug. */
-if (xE-u.u.type == KeyRelease)
+if (device-key != NULL  device-key-xkbInfo != NULL  
+   xE-u.u.type == KeyRelease)
AccessXCancelRepeatKey(device-key-xkbInfo, xE-u.u.detail);
 #endif
 


Bug#239719: xserver-xfree86: v4.3.0-7 post-installation script returned error exit status 139

2004-03-24 Thread Andreas Metzler
On 2004-03-24 Greg Folkert [EMAIL PROTECTED] wrote:
 Package: xserver-xfree86
 Version: 4.3.0-7
 Severity: grave
 Tags: sid
 Justification: renders package unusable
[...]
 Performed a dist-upgrade. So I am working. But I did do a base
 install, then an dpkg --set-selections apt-get dselect-upgrade
 to test this out and did cause the same error.

 Reporting from my regular machine. I am currently working, currently
 dpkg-reconfigure won't work should I change something

 Here is the output of dpkg --configure --debug=3773 etc
[...]
 D02: fork/exec /var/lib/dpkg/info/xserver-xfree86.postinst ( )
 dpkg: error processing xserver-xfree86 (--configure):
  subprocess post-installation script returned error exit status 139
 Errors were encountered while processing:
  xserver-xfree86
[...]


This bug matches the criteria for important exactly:
| important
|a bug which has a major effect on the usability of a package,
|without rendering it completely unusable to everyone.

Clearly it is not unusable to everyone otherwise it would have been
reported a week ago.

I am not downgrading it, as I am no part of the xfree86
maintainer-team.

DEBCONF_DEBUG=developer dpkg --configure xserver-xfree86
or temporarily adding set -x as 2nd line to
/var/lib/dpkg/info/xserver-xfree86.postinst and running
dpkg --configure xserver-xfree86 might show useful information.
   cu andreas



Bug#239510: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=239510

2004-03-24 Thread dickey
   Debian Bug report logs - #239510
   xterm: Reverse video specification broken
In linux.debian.maint.x John Goerzen [EMAIL PROTECTED] wrote:
 Package: xterm
 Version: 4.3.0-7
 Severity: normal

 Hello,

 xterm, on startup, always displays black text on a white background.
 That is, the following three commands do the exact same thing:

 xterm
 xterm -rv
 xterm +rv

Perhaps there is a more-specific resource setting that is overriding
the command-line.  I seem to recall another report to this effect.
The -rv, +rv options use the pattern *reverseVideo, which could be
overridden by an .Xdefaults setting, e.g., XTerm.VT100.reverseVideo

appres XTerm

might show the conflicting resource.

 Also, specifying XTerm*reverseVideo: true does not alter the startup
 colors.

 However, selecting reverse video from the middle-mouse-button menu will
 toggle the colors.

That bypasses the resource-settings.



Bug#236006: xlibs: less/greater/bar key doesn't work with display :0 on xfree86/pc105/de

2004-03-24 Thread Julien Langer
I purged xlibs, removed the remaining files in /usr/lib/X11/xkb/ and
then reinstalled xlibs und xbase-clients, and now it works.




Bug#239798: X4.3.0 missing shape extension

2004-03-24 Thread Flexy
Package: libxext6
Version: 4.3.0-7

OK, since the X upgraded to 4.3.x, I've been unable to start X sessions, 
Enlightenment bitches about missing shape 
extension... From the log files prior 4.3.x I can found the shape extensions, 
but after the first 4.3.x upgrade, 
this has been missing. I will add both logfiles and my configuration file. I'm 
happy to provide extra information, 
just name what you need. This same behaviour has stayed thru multiple updates 
of X related packages.

My kernel version is 2.4.25, build from www.kernel.org sources.
My libc6 version is 2.3.2.ds1-11.
I'm running Debian Sid.

Flexy

# 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 InputDevice
Identifier  Generic Keyboard
Driver  keyboard
Option  CoreKeyboard
Option  XkbRules  xfree86
Option  XkbModel  pc102
Option  XkbLayout fi
Option  XkbVariantnodeadkeys
EndSection

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

Section Device
Identifier  rage
Driver  ati
EndSection

Section Monitor
Identifier  tft
HorizSync   30-60
VertRefresh 50-75
Option  DPMS
EndSection

Section Screen
Identifier  Default Screen
Device  rage
Monitor tft
DefaultDepth24
SubSection Display
Depth   1
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   4
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   8
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   15
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   16
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   24
Modes   1024x768 800x600 640x480
EndSubSection
EndSection

Section ServerLayout
Identifier  Default Layout
Screen  Default Screen
InputDevice Generic Keyboard
InputDevice Configured Mouse
EndSection

Section DRI
Mode0666
EndSection


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-7 20040318043201 [EMAIL PROTECTED])
Release Date: 15 August 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.6.4 i686 [ELF] 
Build Date: 18 March 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.4.25 ([EMAIL PROTECTED]) (gcc version 3.3.3 
(Debian)) #1 Thu Feb 26 16:35:55 EET 2004 
Markers: (--) probed, (**) from config file, (==) 

Processed: Re: Bug#239719: xserver-xfree86: v4.3.0-7 post-installation script returned error exit status 139

2004-03-24 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 severity 239719 important
Bug#239719: xserver-xfree86: v4.3.0-7 post-installation script returned error 
exit status 139
Severity set to `important'.

 thanks
Stopping processing here.

Please contact me if you need assistance.

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



Bug#239719: xserver-xfree86: v4.3.0-7 post-installation script returned error exit status 139

2004-03-24 Thread Daniel Stone
severity 239719 important
thanks

On Wed, Mar 24, 2004 at 11:27:04AM +0100, Andreas Metzler wrote:
 On 2004-03-24 Greg Folkert [EMAIL PROTECTED] wrote:
  Package: xserver-xfree86
  Version: 4.3.0-7
  Severity: grave
  Tags: sid
  Justification: renders package unusable
 [...]
  Here is the output of dpkg --configure --debug=3773 etc
 [...]
  D02: fork/exec /var/lib/dpkg/info/xserver-xfree86.postinst ( )
  dpkg: error processing xserver-xfree86 (--configure):
   subprocess post-installation script returned error exit status 139
  Errors were encountered while processing:
   xserver-xfree86
 [...]
 
 This bug matches the criteria for important exactly:
 | important
 |a bug which has a major effect on the usability of a package,
 |without rendering it completely unusable to everyone.
 
 Clearly it is not unusable to everyone otherwise it would have been
 reported a week ago.
 
 I am not downgrading it, as I am no part of the xfree86
 maintainer-team.

Neither am I, but don't let that stop you.

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


signature.asc
Description: Digital signature


Bug#239341: xdm: extraneous TCP port introduced in upstream

2004-03-24 Thread Jeff King
Package: xdm
Version: 4.3.0-7
Severity: normal
Followup-For: Bug #239341

Hmm. The TCP port opening was introduced in xc/programs/xdm/socket.c,
revision 3.11, when they removed the lines:

if (request_port == 0)   
return;

which also got backported to 4_3_0_2.
See here:
http://cvsweb.xfree86.org/cvsweb/xc/programs/xdm/socket.c#rev3.10.4.1

The xdmcp listening socket code was ripped out of
CreateWellKnownSockets(), and my guess is that the check for
request_port == 0 went accidentally. I don't see why you would want a
randomly-selected chooser socket if you're not going to listen for the
well-known UDP requests. 

I'm not familiar enough with this code to actually submit a patch. Can
somebody with more clue check this out? Or maybe this should just be
forwarded upstream.



Bug#239448: Problem solved. Reassign?

2004-03-24 Thread Scott Robinson
The problem is not with libxft2. It is with GNOME. Specifically, capplets
and capplets-data. This bug should be re-assigned, though I'm not certain
how the maintainer would fix it? (The depends has already been added to
capplets-data.)

Quick answer:

apt-get install --reinstall capplets-data

Long answer:

My GNOME schemas were messed up because of an out of order install of the
capplets packages.

There was a period of time where gnome-control-center did not require
capplets and capplets-data. During that period of time, I was sent an IM
from a friend noting that gnome-control-center would be giving me problems
unless I apt-get'ed capplets-data. (this was passed on from #debian)

I proceeded to do this, but was confused by the requisite of the -data
package without the base package. I installed the base package afterwards.
gnome-control-center, as installed on my system, did not require either of
these!

It was only in this latest update cycle, with gnome-control-center updated,
that the issue finally reared its head. I have tested this by rolling back
to versions in my archives.

The upgrade path was as thus:

[gnome-control-center (1:2.4.0-5)] (Initial State)
capplets-data (2.4.0-7) - capplets (2.4.0-7) (BROKEN!)
gnome-control-center (2.4.0-9), capplets (2.4.0-9), capplets-data (2.4.0-9) 
(FIXED!)

Scott.

-- 
http://quadhome.com/- Personal webpage
http://tranzoa.net/ - Corporate webpage


signature.asc
Description: Digital signature


Bug#239278: xserver-xfree86: Missing dependency on cursor package?

2004-03-24 Thread David Liontooth

Branden Robinson wrote:


tag 239278 + moreinfo
thanks

On Sun, Mar 21, 2004 at 04:29:24PM -0800, David Liontooth wrote:
 


Package: xserver-xfree86
Version: 4.3.0-5
Severity: normal
Tags: sid

After upgrading XFree86 from 4.2 to 4.3.0-5, I was unable to start X11; it 
exited
with the following error: could not open default font 'cursor'. A quick google
and I found someone who had solved this problem by reinstalling artwiz-cursor. I
didn't have that installed already, but installing it fixed my problem (and I 
got
a cool cursor). I imagine I could have used a different cursor package. Is this
a missing dependency?

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

X server symlink status:
lrwxrwxrwx1 root root   20 Feb 18 02:44 /etc/X11/X - 
/usr/bin/X11/XFree86
-rwxr-xr-x1 root root  1743308 Mar  4 21:35 /usr/bin/X11/XFree86
/etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum.

Contents of /var/lib/xfree86/XF86Config-4.roster:
xserver-xfree86
   



Did you remove a lot of information from this report?
 

I plead guilty on this count. I removed it in the belief that reams of 
configuration information about stuff that was working fine wasn't needed.



Also, when the X server failed, you should have seen a message that
looked like this:

#ifdef DEBIAN
FatalError(could not open default cursor font '%s';\n
the X server's font paths might be misconfigured, remote font server(s)\n
may be unreachable, and/or local fonts may not be installed or are not\n
configured correctly.\n
\n
People inexperienced with the X Window System should have either the\n
\x-window-system\ or \x-window-system-core\ packages installed.\n
# apt-get install x-window-system-core\n
# apt-get install x-window-system\n
\n
Useful commands to run include:\n
$ dpkg --status xserver-common\n
$ dpkg --status xfonts-base\n
$ zmore /usr/share/doc/xfree86-common/FAQ.gz, defaultCursorFont);

(Please mentally translate the above C string into proper English.)

Did you not see the above?

 

Indeed I did! Now, please consider that installing artwiz-cursor solved 
my problem, so it's slightly disconcerting to be referred to an error 
message that tells me in very general terms about the x-windows system, 
which you will be the first to admit is an awe-inspiring pile of code, 
right up there with St. Paul's Cathedral.


If there is not a missing dependency, I retract the report and will 
amuse myself in figuring out what went wrong. But couldn't we say 
something more helpful to someone who runs into this problem? Error 
messages that say Something went wrong with this program; why don't you 
figure it all out and then fix it? don't meet that immediate need for a 
well-defined way forward.


Cheers,
David











Bug#239830: xbase-clients: [xcalc] wrong button symbols

2004-03-24 Thread Uwe Storbeck
Package: xbase-clients
Version: 4.2.1-12.1
Severity: normal

Hi,

xcalc has wrong or no symbols on some of it's buttons. The sqrt button
has a wrong symbol (somewhat like a greek delta plus an equal sign with
a tilde) and the division button has no symbol on it.
I can send you a snapshot if you want.

Maybe it's a font problem, so the sqrt symbol is wrong (could be
avoided by using SQRT as button label). But this would not explain
why the slash is missing on the division button.

Uwe


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (900, 'testing'), (200, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.25
Locale: LANG=C, LC_CTYPE=de_CH

Versions of packages xbase-clients depends on:
ii  cpp-3.2   1:3.2.3-9  The 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  libfreetype6  2.1.7-2FreeType 2 font engine, shared lib
ii  libncurses5   5.3.20030719-5 Shared 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

-- no debconf information




Bug#239668: Bug #239668: xserver-xfree86: Elf_RelocateEntry() Unsupported relocation type 0 on i386

2004-03-24 Thread Branden Robinson
 Package: xserver-xfree86
 Version: 4.3.0-7
 Severity: serious
 
 I've made the severity serious, since it appeared initially that X was
 completely unable to start.  It turns out that the error is
 encountered upon loading /usr/X11R6/lib/modules/libxaa.a.  After
 enabling NoAccel in my XF86Config-4, I got the server to start again.
 
 I would appreciate if someone (with similar hardware, if necessary)
 could attempt to reproduce this bug.  There has been no change in my
 hardware or configuration (other than upgrading to the latest
 unstable) since X last functioned with hardware acceleration enabled.

Just FYI, you made a couple of poor decisions when filing this bug
report:

1) You set the severity to serious.  That's a decision for the package
maintainers to make.

As the bug tracking system documentation spells out:

serious
is a severe violation of Debian policy (that is, it violates a must or
required directive), or, in the package maintainer's opinion, makes the
package unsuitable for release.

You were not reporting a violation of Debian policy, nor are you one of
the package maintainers, so your usage of the serious severity was
inapposite.

This is not mere nitpicking, as xfree86 4.3.0-7 is scheduled to enter
testing today, and your report would have prevented that.

2) You included approximately 2 megabytes' worth of strace logs in your
bug report.  Since the Debian packages of xfree86 are team-maintained,
a mailing list is used as the package maintainer address, and our
mailing list software rejected this ridiculously large message.
Consequently, few if any people saw your bug report as soon as it was
submitted.

Once your bug report begins to include large quantities (over 100kB or
so) of attachments, it's time to start thinking about putting the
information on a web page and simply providing URLs to it.  Even a
gzipped attachment is preferable; this would have rendered your bug
report about 189kB in length, which is a big improvement on 2.2 MB.

Finally, it is worth noting that if this problem were widespread among
x86 users, it very likely would have been seen by many others long
before now (4.3.0-7 entered unstable for i386 about a week ago).  I
suspect some subtle problem with your installation.

We'll be happy to work with you to resolve this problem, but if you have
expressed your frustration by filing an oversized bug report with an
inflated severity, I would suggest there are more productive ways to
request assistance.

Thanks for your report; we'll see what we can do.  In the meantime, have
you tried using the debugging server instead?

# apt-get install xserver-xfree86-dbg

(You can use aptitude or your favorite package manager rather than
apt-get, if you like.)

[1] http://www.debian.org/Bugs/Developer#severities

-- 
G. Branden Robinson|  The National Security Agency is
Debian GNU/Linux   |  working on the Fourth Amendment
[EMAIL PROTECTED] |  thing.
http://people.debian.org/~branden/ |  -- Phil Lago, Deputy XD, CIA


signature.asc
Description: Digital signature


Processed: severity of 239668 is important, tagging 239668

2004-03-24 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.7.95.1
 severity 239668 important
Bug#239668: xserver-xfree86: Elf_RelocateEntry() Unsupported relocation type 0 
on i386
Severity set to `important'.

  # no one else has yet seen this -- it's not RC until it's reproducible
 tags 239668 + unreproducible
Bug#239668: xserver-xfree86: Elf_RelocateEntry() Unsupported relocation type 0 
on i386
There were no tags set.
Tags added: unreproducible


End of message, stopping processing here.

Please contact me if you need assistance.

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



Bug#239719: xserver-xfree86: v4.3.0-7 post-installation script returned error exit status 139

2004-03-24 Thread Greg Folkert
Okay Gents. Have done the editing of

/var/lib/dpkg/info/xserver-xfree86.[pre|post]inst

To have set -x as the second line

As they Both now are faulty since I downgraded to -5 and the re-updated to
-7

I even did a set -x before I ran the command, as you will see.

-- Begin xf86-install-set-x-debug-out

Before this output of script, I edited both
/var/lib/dpkg/info/xserver-xfree86.preinst
/var/lib/dpkg/info/xserver-xfree86.postinst
to have set -x as the second line.

Script started on Wed 24 Mar 2004 06:24:59 PM EST
duke:/win1# set -x
duke:/win1# DEBCONF_DEBUG=developer dpkg --debug=3773 --install
/var/cache/apt/archives/xserver-xfree86_4.3.0-7_i386.deb
+ DEBCONF_DEBUG=developer
+ dpkg --debug=3773 --install
/var/cache/apt/archives/xserver-xfree86_4.3.0-7_i386.deb
D10: ensure_pathname_nonexisting `/var/lib/dpkg/tmp.ci'
(Reading database ... 212053 files and directories currently installed.)
Unpacking xserver-xfree86 (from .../xserver-xfree86_4.3.0-7_i386.deb) ...
D01: process_archive oldversionstatus=not installed
D02: fork/exec /var/lib/dpkg/tmp.ci/preinst ( )
debconf (developer): frontend started
debconf (developer): frontend running, package name is xserver-xfree86
debconf (developer): starting /var/lib/dpkg/tmp.ci/config configure
debconf (developer): -- GET
xserver-xfree86/config/inputdevice/mouse/emulate3buttons
debconf (developer): -- 0 false
debconf (developer): -- GET
xserver-xfree86/config/inputdevice/mouse/zaxismapping
debconf (developer): -- 0 true
debconf (developer): -- GET
xserver-xfree86/config/monitor/selection-method
debconf (developer): -- 0 Medium
debconf (developer): -- GET xserver-xfree86/config/modules
debconf (developer): -- 0 bitmap, dbe, ddc, dri, extmod, freetype, glx,
int10, record, speedo, type1, vbe
debconf (developer): -- GET xserver-xfree86/config/device/driver
debconf (developer): -- 0 nvidia
debconf (developer): -- METAGET shared/default-x-server owners
debconf (developer): -- 0 xserver-xfree86
debconf (developer): -- METAGET shared/default-x-server choices
debconf (developer): -- 0 xserver-xfree86
dpkg: error processing
/var/cache/apt/archives/xserver-xfree86_4.3.0-7_i386.deb (--install):
 subprocess pre-installation script returned error exit status 139
D02: fork/exec /var/lib/dpkg/tmp.ci/postrm ( )
D10: ensure_pathname_nonexisting `/var/lib/dpkg/tmp.ci'
D10: ensure_pathname_nonexisting running rm -rf
D10: ensure_pathname_nonexisting `/var/lib/dpkg/reassemble.deb'
Errors were encountered while processing:
 /var/cache/apt/archives/xserver-xfree86_4.3.0-7_i386.deb
duke:/win1# exit

Script done on Wed 24 Mar 2004 06:26:47 PM EST

-- End xf86-install-set-x-debug-out

Looks like the errors of significance are in
/var/lib/dpkg/tmp.ci/

Well that doesn't exist now. Because it gets removed by post error
cleanup.

One last thing I also cleaned out all the 4.3.0-7 package from
/var/cache/apt/archives and re-D/Ld the 4.3.0-7 packages from Master to be
sure.

Have fun. You know how to get ahold of me.

-- 
Greg Folkert, [EMAIL PROTECTED]



none

2004-03-24 Thread Shawn Stern
Get the  low.est  pri.ce  for  gen.eric  medica.tions!

Xa.n.ax  - only $100
Vi.cod.in  - only $99
Ci.al.is  - only $2 per  do.se
Le.vit.ra  - only $73
Li.pit.or  - only $99
Pr.opec.ia  - only $79
Vi.ag.ra  - only $4 per  do.se
Z.oco.r  - only $99

Your  Sav.ings 40% compared Average Internet Pr.ice!

No  Consult.ation  Fe.es!  No  Pr.ior  Prescrip.tions   Required!  No  
Appoi.ntments!
No  Wait.ing  Room!  No  Embarra.ssment!  Private and  Confid.ential!  
Disc.reet  Packa.ging!

http://www.race2bbest.com/r3/?d=pra=2






abstention flatworm dick opec card semi sense resurrect pauper sharpe 
extraneous custodial anybody'd

earthmover alex custodial doctrinal eben gauguin beggar import rhine normalcy 
wordy caption alvin

religiosity collier scotia cremate stag inharmonious lamp adventitious metzler 
predict tunnel acumen welfare

apportion reciprocal azerbaijan elastomer dividend burly grammarian 
ineradicable maze butch gilbertson humpback phyla

referent tyrosine meander silverman gaucherie combustible buckley workforce 
leila bordeaux crocodilian bore confucianism

hilltop arterial cruddy mispronunciation goren attestation libelous seethe 
jericho alison johnny monochromatic detergent

meek ridiculous admire trivial primitivism analytic intellect receptacle 
sinister cleanse epa accomplish diagnoses



Bug#239278: xserver-xfree86: Missing dependency on cursor package?

2004-03-24 Thread Branden Robinson
On Wed, Mar 24, 2004 at 09:53:31AM -0800, David Liontooth wrote:
 Did you remove a lot of information from this report?
 
 I plead guilty on this count. I removed it in the belief that reams of 
 configuration information about stuff that was working fine wasn't needed.

Trust me: 19 times out of 20, it helps.

 Also, when the X server failed, you should have seen a message that
 looked like this:
 
 #ifdef DEBIAN
  FatalError(could not open default cursor font '%s';\n
 the X server's font paths might be misconfigured, remote font server(s)\n
 may be unreachable, and/or local fonts may not be installed or are not\n
 configured correctly.\n
 \n
 People inexperienced with the X Window System should have either the\n
 \x-window-system\ or \x-window-system-core\ packages installed.\n
 # apt-get install x-window-system-core\n
 # apt-get install x-window-system\n
 \n
 Useful commands to run include:\n
 $ dpkg --status xserver-common\n
 $ dpkg --status xfonts-base\n
 $ zmore /usr/share/doc/xfree86-common/FAQ.gz, defaultCursorFont);
 
 (Please mentally translate the above C string into proper English.)
 
 Did you not see the above?
  
 
 Indeed I did! Now, please consider that installing artwiz-cursor solved 
 my problem, so it's slightly disconcerting to be referred to an error 
 message that tells me in very general terms about the x-windows system, 
 which you will be the first to admit is an awe-inspiring pile of code, 
 right up there with St. Paul's Cathedral.
 
 If there is not a missing dependency, I retract the report and will 
 amuse myself in figuring out what went wrong. But couldn't we say 
 something more helpful to someone who runs into this problem? Error 
 messages that say Something went wrong with this program; why don't you 
 figure it all out and then fix it? don't meet that immediate need for a 
 well-defined way forward.

It *did* say:

 People inexperienced with the X Window System should have either the\n
 \x-window-system\ or \x-window-system-core\ packages installed.\n
 # apt-get install x-window-system-core\n
 # apt-get install x-window-system\n

Try removing artwiz-cursor, executing either of the above commands,
and starting the X server again.

-- 
G. Branden Robinson| Q: How does a Unix guru have sex?
Debian GNU/Linux   | A: unzip;strip;touch;finger;mount;
[EMAIL PROTECTED] |fsck;more;yes;fsck;fsck;fsck;
http://people.debian.org/~branden/ |umount;sleep


signature.asc
Description: Digital signature


Bug#239668: Bug #239668: xserver-xfree86: Elf_RelocateEntry() Unsupported relocation type 0 on i386

2004-03-24 Thread Anthony W. Juckel
Sorry about the mistake.  I'm just now heading down the road to becoming 
a Debian developer, so my knowledge of policy is not quite up to par 
yet, I'll admit.  I wasn't attempting to file an inflated bug report in 
order to be obnoxious, I was simply trying to be thorough.  I was in a 
bit of a rush though, and I didn't realize that strace log was that large.


I apologize for stepping on anyone's toes.  I can understand your 
frustration with the report.  I really appreciate you taking time to 
spell out the policy issue for me.  I should have been aware of it, but 
thank you for reminding me.  As for the strace logs, that was just poor 
judgement on my part.  I'll be more careful in the future.


Thank you for all the work that you and your team have put into the 
XFree packages.


Anthony W. Juckel

Branden Robinson wrote:

Package: xserver-xfree86
Version: 4.3.0-7
Severity: serious

[..snip..]


Just FYI, you made a couple of poor decisions when filing this bug
report:

1) You set the severity to serious.  That's a decision for the package
maintainers to make.

As the bug tracking system documentation spells out:

serious
is a severe violation of Debian policy (that is, it violates a must or
required directive), or, in the package maintainer's opinion, makes the
package unsuitable for release.

You were not reporting a violation of Debian policy, nor are you one of
the package maintainers, so your usage of the serious severity was
inapposite.

This is not mere nitpicking, as xfree86 4.3.0-7 is scheduled to enter
testing today, and your report would have prevented that.

2) You included approximately 2 megabytes' worth of strace logs in your
bug report.  Since the Debian packages of xfree86 are team-maintained,
a mailing list is used as the package maintainer address, and our
mailing list software rejected this ridiculously large message.
Consequently, few if any people saw your bug report as soon as it was
submitted.

Once your bug report begins to include large quantities (over 100kB or
so) of attachments, it's time to start thinking about putting the
information on a web page and simply providing URLs to it.  Even a
gzipped attachment is preferable; this would have rendered your bug
report about 189kB in length, which is a big improvement on 2.2 MB.

Finally, it is worth noting that if this problem were widespread among
x86 users, it very likely would have been seen by many others long
before now (4.3.0-7 entered unstable for i386 about a week ago).  I
suspect some subtle problem with your installation.

We'll be happy to work with you to resolve this problem, but if you have
expressed your frustration by filing an oversized bug report with an
inflated severity, I would suggest there are more productive ways to
request assistance.

Thanks for your report; we'll see what we can do.  In the meantime, have
you tried using the debugging server instead?

# apt-get install xserver-xfree86-dbg

(You can use aptitude or your favorite package manager rather than
apt-get, if you like.)

[1] http://www.debian.org/Bugs/Developer#severities







Bug#126519: Urgent, Refill Your Prescription Now

2004-03-24 Thread Jasmine Woodruff
31096559567912015534


 Absolutely the cheapest Gen.eric Dr.ugs from Canada -
Vic.odin, Xan.ax, Cia.lis and more:

http://www.raeli03.com/r3/?d=pra=5




inextinguishable veracity yeager alan temple paulus floe light revisionary 
disneyland begrudge legato horatio

cohn conclusive archery maneuver thereupon chaplain careworn beman commandeer 
toledo dinosaur analgesic collegiate

catabolic bluebill sea melinda bladder video immodest hug grizzly prevail 
adolphus corpsmen accident

directrix afghanistan chen commemorate usa violin torus repetitive larson 
furtive stupor cafe deprivation

lindstrom condensible edmund al holdout rooky brahmaputra disquietude motive 
wrongdoer otto tangy staple

tag redstone showpiece curriculum congratulatory draco hoyden salisbury grail 
bobby buckhorn loudspeaking cruddy

upholstery nyc borneo antique trustworthy durable hurwitz clothesbrush dim 
vanilla presbytery mullen appointee


31096559567912015534--





Bug#166515: Pain Relief drugs prescribed online for free and to your door.

2004-03-24 Thread German Wiggins

 Absolutely the cheapest Gen.eric Dr.ugs from Canada -
Vic.odin, Xan.ax, Cia.lis and more:

http://www.ragya.com/r3/?d=pra=5




cranberry bouquet cannister scholastic liturgy metcalf fear adenine northland 
ohio premier bellamy tycoon

formal instalment negotiate snafu knapsack eighth coffin titian brand ruinous 
onondaga nightmare vengeful

traverse airstrip award gsa carlton marjorie billfold tsunami crag shako 
disjunct sentient grass

laureate alga colorimeter anastomosis sarcastic civil burgess ellipsoidal 
playground f's animadversion adopt consternate

depositary epiphysis falsehood derail idle feign drugstore wa umlaut getty 
damnation concede pyre

irradiate prurient amman charm thirteenth lawman malden along switchman fence 
essay autistic levine

carrel polopony negotiate barfly boyfriend bruce beryllium terramycin 
hereinbelow organic uniroyal stagestruck augustus



Bug#233867: xlibs: WORKAROUND for xlib6g conflict for source-less packages

2004-03-24 Thread Leonardo Rochael Almeida
Package: xlibs
Version: 4.3.0-7
Severity: normal
Followup-For: Bug #233867

As I mentioned before, I had some binary packages hanging around that
depended on xlib6g. I didn't have access to the source packages for
these so I used dpkg-repack + alien to convert them:

cd to some temp dir
# dpkg-repack oldpackage1 oldpackage2 oldpackage3
use apt to install new xlibs
# alien -g oldpackage1_some.version-debversion_i386.deb
# cd oldpackage1-some.version
# debian/rules binary
# cd ..
# dpkg -i oldpackage1_some.version-newdebversion_i386.deb

This worked for me because alien created a
oldpackage_some.version/debian/control file where the Depends: line was
just ${shlibs:Depends} and so it was calculated from current packages
after the installation of xlibs. I think it does this with every
package, but you might want to review the debian/control file before the
debian/rules binary step above.





Processed: Re: Problem solved. Reassign?

2004-03-24 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 reassign 239448 capplets-data
Bug#239448: libxft2: Fails to render fonts, making GTK+ 2 and related system 
unusable.
Bug reassigned from package `libxft2' to `capplets-data'.

 thanks
Stopping processing here.

Please contact me if you need assistance.

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



Bug#239668: Bug #239668: xserver-xfree86: Elf_RelocateEntry() Unsupported relocation type 0 on i386

2004-03-24 Thread Anthony W. Juckel
Just to follow up, it appears that I was indeed rather premature with 
this report (but you all knew that anyway).  I acted too hastily.  I had 
just upgraded the xfree86 packages, and went to restart my x session and 
X crashed.  After a little bit of debugging, and seeing a similar report 
on Alpha, I added another bug.  I assumed that since the package simply 
did not start, that it qualified as a serious bug (I believe that a 
package that does not start in its default configuration is a serious 
violation of policy, but I can't find the reference now).


In hindsight, I should have been more thoughtful.  The package was, 
first of all, not in its default configuration, obviously, since I have 
spent time customizing my XF86Config-4 file.  Secondly, I didn't check 
to see how long the package had been out before filing the report.


Anyway, I downloaded xserver-xfree86-dbg in the hopes of finding out 
more information, and it started just fine.  I redownloaded the standard 
4.3.0-7 package, and it too worked just fine.  I'm not sure exactly what 
the problem was on my system that day, but the very same package is 
working fine now.


So, now that I'm sufficiently embarrassed, I'm going to recommend that 
this bug be closed, and start a thorough reading of the Debian Policy 
Manual, as well as promise to behave more sensibly in the future.


Anthony W. Juckel

ps.  Perhaps I should have just sat back and got a nice warm cup of shut 
the f**k up :-)  At least until I had verified it with a couple other 
users...


Branden Robinson wrote:

Package: xserver-xfree86
Version: 4.3.0-7
Severity: serious

I've made the severity serious, since it appeared initially that X was
completely unable to start.  It turns out that the error is
encountered upon loading /usr/X11R6/lib/modules/libxaa.a.  After
enabling NoAccel in my XF86Config-4, I got the server to start again.

I would appreciate if someone (with similar hardware, if necessary)
could attempt to reproduce this bug.  There has been no change in my
hardware or configuration (other than upgrading to the latest
unstable) since X last functioned with hardware acceleration enabled.