Re: G3 iBook LCD brightness in X under kernel 2.4.25 and 2.6.8

2004-12-01 Thread murphyf+xfree86

OK, works for me here as well. I think I'm seeing some weird color
artifacts, but I'll bring it up with the guy who's doing all the Mach64
work. There seems to be a lot in 2.6.10.

Frank

On Tue, 30 Nov 2004 10:05:00 +0100, Frank Murphy
[EMAIL PROTECTED] said:
 
 On Tue, 30 Nov 2004 09:02:52 +0100, Christof Petig
 [EMAIL PROTECTED] said:
  I can confirm that everything works well with Linus' 2.6.10-rc2-bk6. So 
  consider the problem as solved (writing from said version).
  
  snooze and the brightness keys work well.
 
 Well *that's* good news. I'll retry here as well and confirm.
 
 Frank



Bug#279252: #279252 uxterm should not override my locale

2004-12-01 Thread Steinar H. Gunderson
On Tue, Nov 30, 2004 at 08:47:52PM -0500, Thomas Dickey wrote:
 xterm patch #197 addresses this by using the error status from the 'locale'
 program to check if a given locale is installed.

That does not really solve the problem if I should happen to have the UTF-8
locales installed; the default x-terminal-emulator still uses a locale I
never asked for (and do not want), which is distinctly different from all
other applications (say, Mozilla, or gvim) and the Linux console.

/* Steinar */
-- 
Homepage: http://www.sesse.net/




Bug#279252: #279252 uxterm should not override my locale

2004-12-01 Thread Thomas Dickey

On Wed, 1 Dec 2004, Steinar H. Gunderson wrote:


On Tue, Nov 30, 2004 at 08:47:52PM -0500, Thomas Dickey wrote:

xterm patch #197 addresses this by using the error status from the 'locale'
program to check if a given locale is installed.


That does not really solve the problem if I should happen to have the UTF-8
locales installed; the default x-terminal-emulator still uses a locale I
never asked for (and do not want), which is distinctly different from all
other applications (say, Mozilla, or gvim) and the Linux console.


uxterm sets a UTF-8 locale.
If you don't want a UTF-8 locale, you should not run uxterm.

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




Processed: Re: Bug#279252: #279252 uxterm should not override my locale

2004-12-01 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 retitle 279252 default x-terminal-emulator should not override my locale
Bug#279252: [uxterm] uxterm should not override my locale
Changed Bug title.

 thanks
Stopping processing here.

Please contact me if you need assistance.

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



Bug#279252: #279252 uxterm should not override my locale

2004-12-01 Thread Steinar H. Gunderson
retitle 279252 default x-terminal-emulator should not override my locale
thanks

On Wed, Dec 01, 2004 at 05:54:00AM -0500, Thomas Dickey wrote:
 That does not really solve the problem if I should happen to have the UTF-8
 locales installed; the default x-terminal-emulator still uses a locale I
 never asked for (and do not want), which is distinctly different from all
 other applications (say, Mozilla, or gvim) and the Linux console.
 uxterm sets a UTF-8 locale.
 If you don't want a UTF-8 locale, you should not run uxterm.

I do not run uxterm. I run x-terminal-emulator, which is supposed to give me
a sane terminal emulator by default, but in current sarge, uxterm is the
default for x-terminal-emulator. This is what my bug is all about; uxterm
should not be the default for x-terminal-emulator. (I've retitled the bug to
make it clearer.)

/* Steinar */
-- 
Homepage: http://www.sesse.net/




Bug#279252: #279252 uxterm should not override my locale

2004-12-01 Thread Steinar H. Gunderson
On Wed, Dec 01, 2004 at 06:04:20AM -0500, Thomas Dickey wrote:
 I do not run uxterm. I run x-terminal-emulator, which is supposed to give
 me a sane terminal emulator by default, but in current sarge, uxterm is
 the default for x-terminal-emulator. This is what my bug is all about;
 uxterm should not be the default for x-terminal-emulator. (I've retitled
 the bug to make it clearer.)
 In that case, it's not a bug against xterm, but against whatever 
 meta-package owns x-terminal-emulator.

From xterms postinst:

update-alternatives --install /usr/bin/x-terminal-emulator x-terminal-emulator 
/usr/X11R6/bin/xterm 20 (...)
update-alternatives --install /usr/bin/x-terminal-emulator x-terminal-emulator 
/usr/X11R6/bin/uxterm 30 (...)

I don't see how anything but xterm is supposed to change this situation.
AFAIK no package owns an alternative per se, but I might be wrong here; my
understanding of this was that by default, whatever alternative has the
highest priority is selected as the alternative in use.

/* Steinar */
-- 
Homepage: http://www.sesse.net/




Bug#279252: #279252 uxterm should not override my locale

2004-12-01 Thread Thomas Dickey

On Wed, 1 Dec 2004, Steinar H. Gunderson wrote:


I do not run uxterm. I run x-terminal-emulator, which is supposed to give me
a sane terminal emulator by default, but in current sarge, uxterm is the
default for x-terminal-emulator. This is what my bug is all about; uxterm
should not be the default for x-terminal-emulator. (I've retitled the bug to
make it clearer.)


In that case, it's not a bug against xterm, but against whatever 
meta-package owns x-terminal-emulator.


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




Bug#279252: #279252 uxterm should not override my locale

2004-12-01 Thread Tollef Fog Heen

* Thomas E. Dickey

| In that case, it's not a bug against xterm, but against whatever
| meta-package owns «x-terminal-emulator».

x-terminal-emulator is not provided by any package per se and
certainly not a meta-package.  x-termnial-emulator is handled by the
alternatives system.  The problem here is uxterm is provided with a
higher priority than plain xterm, which means it gets selected as the
default x-terminal-emulator unless it is overridden by the user:

: [EMAIL PROTECTED] ~  update-alternatives --display x-terminal-emulator
x-terminal-emulator - status is auto.
 link currently points to /usr/bin/gnome-terminal.wrapper
/usr/X11R6/bin/xterm - priority 20
 slave x-terminal-emulator.1.gz: /usr/X11R6/man/man1/xterm.1x.gz
/usr/X11R6/bin/uxterm - priority 30
 slave x-terminal-emulator.1.gz: /usr/X11R6/man/man1/uxterm.1x.gz
/usr/bin/gnome-terminal.wrapper - priority 40
 slave x-terminal-emulator.1.gz: /usr/share/man/man1/gnome-terminal.1.gz
Current `best' version is /usr/bin/gnome-terminal.wrapper.
: [EMAIL PROTECTED] ~ 

As you can see, uxterm has priority 30, plain xterm has priority 20.
If those were reversed, x-terminal-emulator would be behaving just as
it should be -- xterm would be the default (with just x-window-system
installed).

-- 
Tollef Fog Heen,''`.
UNIX is user friendly, it's just picky about who its friends are  : :' :
  `. `' 
`-  



Bug#279252: #279252 uxterm should not override my locale

2004-12-01 Thread Steinar H. Gunderson
On Wed, Dec 01, 2004 at 07:09:42AM -0500, Thomas Dickey wrote:
 I don't see how anything but xterm is supposed to change this situation.
 AFAIK no package owns an alternative per se, but I might be wrong here;
 my understanding of this was that by default, whatever alternative has the
 highest priority is selected as the alternative in use.
 I would regard that as a defect in the alternatives scheme, since package 
 maintainers can otherwise choose to set arbitrary priorities for their 
 favorite packages (and doing so late in the release cycle leads to 
 competitive issues).

You could of course view that as a problem, but it's completely irrelevant
here, as xterm's postinst sets the priority for both xterm and uxterm, and
it's the relative priorities of those two I want to swap.

/* Steinar */
-- 
Homepage: http://www.sesse.net/



Bug#279252: #279252 uxterm should not override my locale

2004-12-01 Thread Thomas Dickey

On Wed, 1 Dec 2004, Steinar H. Gunderson wrote:


On Wed, Dec 01, 2004 at 06:04:20AM -0500, Thomas Dickey wrote:

In that case, it's not a bug against xterm, but against whatever
meta-package owns x-terminal-emulator.



From xterms postinst:


update-alternatives --install /usr/bin/x-terminal-emulator x-terminal-emulator 
/usr/X11R6/bin/xterm 20 (...)
update-alternatives --install /usr/bin/x-terminal-emulator x-terminal-emulator 
/usr/X11R6/bin/uxterm 30 (...)

I don't see how anything but xterm is supposed to change this situation.
AFAIK no package owns an alternative per se, but I might be wrong here; my
understanding of this was that by default, whatever alternative has the
highest priority is selected as the alternative in use.


I would regard that as a defect in the alternatives scheme, since package 
maintainers can otherwise choose to set arbitrary priorities for their 
favorite packages (and doing so late in the release cycle leads to 
competitive issues).


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




Bug#279252: #279252 uxterm should not override my locale

2004-12-01 Thread Thomas Dickey

On Wed, 1 Dec 2004, Steinar H. Gunderson wrote:


You could of course view that as a problem, but it's completely irrelevant
here, as xterm's postinst sets the priority for both xterm and uxterm, and
it's the relative priorities of those two I want to swap.


true (it's the package maintainer who is able to fix this - I'm not).
My fix ensures that the locale is valid.

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



Bug#11147: Turn your little one into the master of the bedroom using the Patch! txn

2004-12-01 Thread Jana Browne
Tired of thinking about risky surgery?
Still wishing there was still an easy,
safe and affective way to enlarge your member?
Start thinking bout...
..the safest,
..most effective
..and most afforadable Patch to enlarge it!
Ease of Use:
This doctor developed patch is very easy to use;
Simply peel off the backing (just like a band-aid)
Place it on your arm.

Watch it Grow!
http://wheatstone.argonon.net/app/index.php?id=27
Most have the Seeds of Judgment in their Mind;
But as the slightest Sketch, if justly trac'd,

Jana

4240949541747422352--



Bug#280384: XFree crashing on kernel 2.4.28

2004-12-01 Thread Admar Schoonen
On Wed, Dec 01, 2004 at 09:52:48AM -0800, [EMAIL PROTECTED] wrote:
 A couple of issues come to mind looking at the transcript of our bug
 #280384:
 
 1) Why couldn't Peter De Schrijver experience this problem for himself
 on the Debian 2.6.8.1 kernel?
 
 2) Why does Admar Schoonen's work-around (using the debug server)
 function properly? I think it's supremely ironic that the debug build
 doesn't have the bug. LOL.

Well, I have to admit that this bug does occur on my Sun Blade 100 (with 2
almost identical ati mach 64 cards), but not on my Sun Ultra 5 (with only 1 ati
mach 64 card that is slightly different than the one in the blade 100). 

The bug also doesn't occur on a Sun Ultra 5 at my friend's place, but iirc, it
does occur on an Ultra 5 or Ultra 10 from someone else, so I'm a bit sceptical
to say that U5's are not affected.

The fact that the debug server doesn't show the bug could indicate that it's a
timing issue, but to be honest, I am a terrible programmer and I wouldn't know
how to start debugging this issue.

I hope this could be useful for someone, and if he/she needs more
information/testing, I'd happy volunteer.

Admar



Processed: severity of 280384 is important

2004-12-01 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.8.5
  # If it doesn't affect all hardware configurations, it's not grave.
 severity 280384 important
Bug#280384: xserver-xfree86: X crashes on load, UltraSPARC with 2.6.xx kernel 
and udev
Severity set to `important'.


End of message, stopping processing here.

Please contact me if you need assistance.

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



File was infected with a virus

2004-12-01 Thread KDDI-INFO

Note: JP stands for Japanese.

ALERT!!
This e-mail contained one or more virus-infected files and have been rejected.
(JP:コンピュータウィルスを発見しましたので、メールの送信を中止しました。)

The following attachments were infected:
(JP:感染ファイルは以下のとおり。) 
file=msg6185.zip,status=deleted,virus-id=37711,[EMAIL PROTECTED]

Thank you,

KDDI Corporation [EMAIL PROTECTED]

-- Original message text follows ---
Subject:  Delivery Failure ([EMAIL PROTECTED])
Message-ID:  [EMAIL PROTECTED]
Date: 2004/12/02
From: debian-x@lists.debian.org
To: [EMAIL PROTECTED]



Bug#280384: XFree crashing on kernel 2.4.28

2004-12-01 Thread Jurij Smakov

Hello,

Branden Robinson of the Debian's X Strike Force (XFS) mentioned the bug 
#225526, which might be the same problem, according to him. Presumably, 
this bug should be fixed by the following commit to the XFS' SVN 
repository:


 * Apply patch from David Mosberger that replaces
   the fix for #225526 with one that works on systems
   that do not have a PCI bus numbered 0.  Thanks,
   David!  (Closes: #279436)

The ultimate test would be to build the packages from the SVN source and 
test it on the machines, which are affected. I'll try to arrange the 
build, but it can take a while, since I do not have access to any decent 
Ultra hardware.


Best regards,

Jurij Smakov[EMAIL PROTECTED]
Key: http://www.wooyd.org/pgpkey/   KeyID: C99E03CC




Bug#280384: XFree crashing on kernel 2.4.28

2004-12-01 Thread Ron Murray

Jurij Smakov wrote:

Hello,

Branden Robinson of the Debian's X Strike Force (XFS) mentioned the bug 
#225526, which might be the same problem, according to him. Presumably, 
this bug should be fixed by the following commit to the XFS' SVN 
repository:


 * Apply patch from David Mosberger that replaces
   the fix for #225526 with one that works on systems
   that do not have a PCI bus numbered 0.  Thanks,
   David!  (Closes: #279436)

The ultimate test would be to build the packages from the SVN source and 
test it on the machines, which are affected. I'll try to arrange the 
build, but it can take a while, since I do not have access to any decent 
Ultra hardware.


   Colour me doubtful about this as a fix. Its bug report has an 
XFree86.log that actually appears to scan the PCI bus, then does lots of 
other things before reporting no screens found. In contrast, both the 
logs from the originator of this thread and the XFree86.log in bug 
#280384 show the crash occurring immediately after loading the pcidata 
module, with no attempt to scan the PCI bus. That is also my experience, 
as evidenced by the log in my own post to bug #280384. They don't look 
like the same problem to me at all.


   That said, if somebody can tell me how to extract sources with this 
patch, I'm willing to try compiling it. Only takes the machine six hours 
these days :-)


 .Ron

--
Ron Murray   ([EMAIL PROTECTED])
http://www.rjmx.net/~ron
GPG Public Key Fingerprint: F2C1 FC47 5EF7 0317 133C  D66B 8ADA A3C4 
D86C 74DE




Bug#116507: Expiration Date (29-Dec-2004)

2004-12-01 Thread Greens Solutions

Client Update:

Several Companies have been competing for your mortgage
refinance application over the past 2 weeks.  

The company that offered the lowest rate, and largest
loan quantity has requested your information be verified.

http://qtbouncytpj.rosearbusto.net/prime/ElsaElder


Thanks,
Christoper Hatcher
Greens Solutions
Account Creations

 
WR0NG PERS0N?
Visit our Site to 0pt-0ut



Bug#283764: X clients will not start. Fix found.

2004-12-01 Thread David Lawyer
Package: xfree86-common
Version: 4.3.0.dfsg.1.-1

When I type startx at the console, x starts and quits.  But if I type
startx at a dumb terminal on a serial port, x starts OK and goes to
the icewm (ice window manager which I have installed).  So why can I
start X from a dumb terminal but not from the console? 

It took me some time to determine why.  The error is in the file
/etc/X11/Xsession.  The run_parts() function has
for F in $(ls $1); do
it should be:
for F in $(command ls $1); do

This is because I have in my /etc/profile:

if [ $TERM = linux -o $TERM = xterm ]; then
if [ $TERM = linux ]; then
   eval `dircolors`;
   ls () { command ls --color $* ; }
fi
else 
ls () { command ls -F $* ; }
.

So when I use a dumb terminal and $TERM = my-dumb-terminal (or whatever)
then ls() is defined differently.  But at the console, ls() is made
to support colors and the run_parts() can't seem to cope with the
control codes which are embedded in the file names to create colors.
One word command fixes it.

What was frustrating was that there were no error messages.

David Lawyer