On 2011-03-08 14:48:12 -0500, John D. Hendrickson and Sara Darnell wrote:
> hi I wrote www.sourceforge.net/projects/xdm-options/
>
> one reason I've used xdm for so long is that having my environment in xterm
> was more important to me than how X got started
>
> I think the C-coded display manage
hi I wrote www.sourceforge.net/projects/xdm-options/
one reason I've used xdm for so long is that having my environment in
xterm was more important to me than how X got started
I think the C-coded display managers out there don't bother with
/etc/profile or ~/.profile like a login should - bu
if you don't mind my butting in
I notice when I start gdm xdm has *no* environment.
I have no comment on whether this or that app uses that particular env.
var. though.
Vincent Lefevre wrote:
On 2011-03-08 11:31:00 +0100, Vincent Lefevre wrote:
[adding Thomas to Cc, as this concerns xterm]
Vincent Lefevre (08/03/2011):
> Note that the command in question is in my $HOME/bin, thus not in
> the default $PATH.
Oh, OK.
> […] and rebuilt libxt6 again, and the problem was solved. So, I
> confirm that the problem was due to this memory corruption.
Thanks for checking.
KiBi.
signature.
On 2011-03-08 16:16:24 +0100, Cyril Brulebois wrote:
> Hi,
>
> Vincent Lefevre (08/03/2011):
> > On 2011-03-08 11:31:00 +0100, Vincent Lefevre wrote:
> > > [adding Thomas to Cc, as this concerns xterm]
>
> only remotely.
Yes, just in case Thomas got bug reports because of this.
> Probably that
Hi,
Vincent Lefevre (08/03/2011):
> On 2011-03-08 11:31:00 +0100, Vincent Lefevre wrote:
> > [adding Thomas to Cc, as this concerns xterm]
only remotely. Probably that stupid libxt memory corruption:
http://article.gmane.org/gmane.comp.freedesktop.xorg.devel/19675
> Actually, not just XAUTHOR
Hi there,
This issue was originally reported against version 1:1.1.10-3. It was
reported fixed two days ago in version 1:1.1.0-2 which makes no sense to
me considering that oldstable is 1.1.8-5 and stable/unstable is
1.1.10-3. I'm still seeing this issue this morning. Thanks!
Tony
--
To UNSUB
On 2011-03-08 11:31:00 +0100, Vincent Lefevre wrote:
> [adding Thomas to Cc, as this concerns xterm]
>
> FYI, libxt/1:1.1.0-1 also breaks xterm: XAUTHORITY is removed from the
> environment, meaning that I can no longer start X applications from
> xterm when gdm3 is used. As libxt/1:1.1.0-2 fixes
[adding Thomas to Cc, as this concerns xterm]
FYI, libxt/1:1.1.0-1 also breaks xterm: XAUTHORITY is removed from the
environment, meaning that I can no longer start X applications from
xterm when gdm3 is used. As libxt/1:1.1.0-2 fixes the problem (which
appeared with the upgrade to libxt/1:1.1.0-1
On Mon, Mar 7, 2011 at 11:52:01 +0100, Sven Joachim wrote:
> On 2011-03-07 09:21 +0100, Sven Joachim wrote:
>
> > This morning I found myself at the console rather than at the XDM login
> > prompt, with the following messages in /var/log/xdm.log:
> >
> > ,
> > | Mon Mar 7 07:50:32 2011 xdm
reassign 617208 libxt6
found 617208 1:1.1.0-1
forcemerge 617208 617223
thanks
On 2011-03-07 09:21 +0100, Sven Joachim wrote:
> This morning I found myself at the console rather than at the XDM login
> prompt, with the following messages in /var/log/xdm.log:
>
> ,
> | Mon Mar 7 07:50:32 2011
Package: xdm
Version: 1:1.1.10-3
Severity: important
This morning I found myself at the console rather than at the XDM login
prompt, with the following messages in /var/log/xdm.log:
,
| Mon Mar 7 07:50:32 2011 xdm error (pid 1285): Unknown session exit code 2816
from process 1463
| Mon Mar
12 matches
Mail list logo
