Bug#617223: marked as done (libxt6: xdm segfaults)
Debian Bug Tracking System
with message-id <E1Pwhn4-...@franck.debian.org>
and subject line Bug#617208: fixed in libxt 1:1.1.0-2
has caused the Debian Bug report #617208,
regarding libxt6: xdm segfaults
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
617208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Debian Bug Tracking System
with message-id <E1Pwhn4-...@franck.debian.org>
and subject line Bug#617208: fixed in libxt 1:1.1.0-2
has caused the Debian Bug report #617208,
Vincent Lefevre
> [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) and other terminals
> didn't have any problem, I assume this is the same bug.
Actually, not just XAUTHORITY, as $PATH was affected too
("xterm -e some_command" started by fvwm output an error
message saying that some_command couldn't be found), and
I suspect that the whole environment was removed or something
similar.
--
Vincent Lefèvre <vin...@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)
--
To UNSUBSCRIBE, email to debian-bugs...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Cyril Brulebois
> 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.
John D. Hendrickson and Sara Darnell
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 - but I don't know.
by the way XAUTHORITY may not be an export when you think it is - and
maybe it shouldn't be (reasons omitted)
you can use xauth it is simple to use
Vincent Lefevre wrote:
> 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 the problem (which
>> appeared with the upgrade to libxt/1:1.1.0-1) and other terminals
>> didn't have any problem, I assume this is the same bug.
>
> Actually, not just XAUTHORITY, as $PATH was affected too
> ("xterm -e some_command" started by fvwm output an error
> message saying that some_command couldn't be found), and
> I suspect that the whole environment was removed or something
> similar.
>
--
John D. Hendrickson and Sara Darnell
I didn't see your doing this from a gdm desktop. NEVER MIND.
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 the problem (which
> appeared with the upgrade to libxt/1:1.1.0-1) and other terminals
> didn't have any problem, I assume this is the same bug.
>
Vincent Lefevre
> 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 - but I don't know.
>
> by the way XAUTHORITY may not be an export when you think it is - and maybe
> it shouldn't be (reasons omitted)
FYI, gdm3 is different from gdm or xdm. It defines its own $XAUTHORITY,
so that if the value is lost (like it is with xterm + the buggy libxt),
then one can no longer start X applications. One cannot even guess what
the $XAUTHORITY value was, since the directory is not readable.
> you can use xauth it is simple to use
It is not possible to use it, as xauth needs to know the location of
the X authority file, which is precisely the information that has been
lost.
--
Vincent Lefèvre <vin...@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)
--
Vincent Lefevre
> OH DANG it!
>
> I didn't see your doing this from a gdm desktop. NEVER MIND.
Note: gdm3, not gdm (the difference is important).
--
Vincent Lefèvre <vin...@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)
--