Bug 20245 - xauth:
Summary: xauth:
Alias: None
Product: xorg
Classification: Unclassified
Component: App/xauth (show other bugs)
Version: unspecified
Hardware: Other All
: medium trivial
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL: http://bugs.gentoo.org/show_bug.cgi?i...
Depends on:
Reported: 2009-02-21 11:50 UTC by Martin Mokrejs
Modified: 2011-10-15 16:45 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Martin Mokrejs 2009-02-21 11:50:29 UTC
Sometimes, xauth complains with:

$ xauth 
Using authority file /home/mmokrejs/.Xauthority
xauth> source /home/mmokrejs/.Xauthority
xauth: /home/mmokrejs/.Xauthority:2:  line too long

It does not show which lines is that, "xauth list" seems to work normally so one wonders what is really wrong. Please improve the error message to show at least the beginning of the problematic line ... whatever. See the bug at Gentoo for more details and the problematic .Xauthority file. At the very moment is seems the file is fine, so maybe it was an issue with xauth binary and not the file itself? Who knows. Googling around gives some hits to some similar cases. Would be nice if it would say what was too long on the line. The cookie? The hostname part?

Comment 1 Alan Coopersmith 2009-02-23 08:19:12 UTC
.Xauthority is a binary file - it doesn't really have lines to show, and
dumping them to your screen would just break your terminal.

The "source" command requires a text file containing xauth commands - an
.Xauthority file is not at all usable for source, and no amount of dumping
binary data to your terminal will help you fix that.
Comment 2 Martin Mokrejs 2009-02-23 08:31:48 UTC
So how can I import the old .Xauthority-old file?
Hmm, "xauth -f .Xauthority-old".

Could "xauth source" give an error message if the file is a binary? I know that you will probably disagree based on which chars should it detect the "binary" but it is up to you. ;-)

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.