Re: xauth segfault
Well it seems I was wrong and this is a common-or-garden bug. Specifically,
from xauth/gethost.c, starting at line 199:
#ifdef HAVE_STRLCPY
strlcpy(path, fulldpyname, sizeof(path));
#else
strncpy(path, fulldpyname, sizeof(path));
path[sizeof(path) - 1] = '\0';
#endif
if (0 == stat(path, )) {
is_path_to_socket = 1;
} else {
char *dot = strrchr(path, '.');
if (dot) {
*dot = '\0';
/* screen = atoi(dot + 1); */
if (0 == stat(path, )) {
is_path_to_socket = 1;
}
}
}
fulldpyname is "drogo.datum:0" and there is a directory in $HOME named "drogo".
is_path_to_socket then gets set to 1 and the strlcpy(buf, strrchr(fulldpyname,
'/') + 1, sizeof(buf)) a few lines down passes 0x01 as the source pointer to
strlcpy.
I don't know if it is or should be required that $DISPLAY pointing to a unix
socket can be a relative path, but if they must be absolute then this patch
enforces that (and fixes my segfault, though by making the same assumption that
$DISPLAY will include a '/' in two places).
Matthew
Index: parsedpy.c
===
RCS file: /home/flask/src/openbsd/cvsync/xenocara/app/xauth/parsedpy.c,v
retrieving revision 1.5
diff -u -p -r1.5 parsedpy.c
--- parsedpy.c 19 Feb 2017 17:30:58 - 1.5
+++ parsedpy.c 18 Oct 2019 12:02:34 -
@@ -177,7 +177,7 @@ parse_displayname (const char *displayna
#endif
if (0 == stat(path, )) {
family = FamilyLocal;
-} else {
+} else if (strrchr(path, '/') == path) { /* I'm not sure this is the
best way to test for this */
char *dot = strrchr(path, '.');
if (dot) {
*dot = '\0';
Re: xauth segfault
Klemens Nanni writes: > On Thu, Oct 17, 2019 at 10:30:54PM +0100, cho...@jtan.com wrote: > > I don't even know where to begin with this one > Start with providing a backtrace from the core dump: build xauth with > debug symbols and reproduce, then inspect with gdb. > > Otherwise you're on your own with this very special setup. OK I should probably make it clear that I figured that much out. I was unable to gleen much from it 6 months ago but didn't look hard because as I said it wasn't important enough to deal with as that machine doesn't really need X. It didn't just go away so this time I'm willing to put more effort in to figuring it out but before I attack the problem in earnest I'd like to gather some thoughts on why otherwise-identical VMs could be acting differently. I don't think this is a common-or-garden bug. (Also I finished upgrading things very close to the end of the day last night - there wasn't any time to test anything yesterday and I haven't yet had coffee today) Matthew
Re: xauth segfault
On Thu, Oct 17, 2019 at 10:30:54PM +0100, cho...@jtan.com wrote: > I don't even know where to begin with this one Start with providing a backtrace from the core dump: build xauth with debug symbols and reproduce, then inspect with gdb. Otherwise you're on your own with this very special setup.
xauth segfault
This is sort of a weird one. Background is that I have a laptop with a bunch of VMs all running OpenBSD, now 6.6 (thanks!). The host runs X and one of the VMs runs the window manager which can then log into other VMs (or the host) to do whatever. My development environment, named void, is one those VMs. So far so strange. It's my setup and I like it. To run X apps, XAuthority credentials are banded about. All of the VMs have no problem with this except void, on which xauth segfaults. The login process when forwarding X credetials is essentially: var=$(xauth list $DISPLAY) ssh $remote xauth add $var ssh $remote DISPLAY=$DISPLAY $thing The strange thing is that with a few identical VMs running on this host, only on one of them does xauth segfault. All have today been upgraded to 6.6 and the fault was present on 6.5 too (I ignored it because I don't really need X there and hoped it would Just Go Away; it didn't). OpenBSD 6.6 (GENERIC) #353: Sat Oct 12 10:45:56 MDT 2019 [ksh]flask@chicken$ xauth list drogo.datum:0 MIT-MAGIC-COOKIE-1 86963dd9ee88bbfcc9eb66846b9cf4ce [ksh]flask@chicken$ ssh void OpenBSD 6.6 (GENERIC) #353: Sat Oct 12 10:45:56 MDT 2019 [ksh]flask@void$ xauth add drogo.datum:0 MIT-MAGIC-COOKIE-1 86963dd9ee88bbfcc9eb66846b9cf4ce /usr/X11R6/bin/xauth: file /home/flask/.Xauthority does not exist Segmentation fault (core dumped) [ksh]flask@void$ ^D [ksh]flask@chicken$ ssh shelob OpenBSD 6.6 (GENERIC) #353: Sat Oct 12 10:45:56 MDT 2019 [ksh]flask@shelob$ xauth add drogo.datum:0 MIT-MAGIC-COOKIE-1 86963dd9ee88bbfcc9eb66846b9cf4ce [ksh]flask@shelob$ I don't even know where to begin with this one (well I have some places to start looking but the fact that the otherwise-identical VMs react differently tells me this might be something deeper than the obvious so I'm waiting). I *think* this worked once but I can't be sure if I just didn't notice it failing. If nothing else I'll get around to figuring out how to build individual xenocara components and then step through the process to figure out what's broken in xauth but before I get to that I thought I'd see if anyone more familiar with these systems has any ideas. Matthew
Re: xauth: (argv):1: bad display name "BadSystemDetected.my.domain:0" in "remove" command
I tried to Xorg -configure today and I get this : (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d" (EE) Segmentation fault at address 0x28 Fatal server error: (EE) Caught Signal 11 (Segmentation Fault). Server aborting Still don't know what to do with it. 2016-01-30 18:34 GMT+01:00 Lô Baret <lo.ba...@gmail.com>: > Thanks for the answer, i've already looked for solutions in the > mailing list archive and on numerous forums. > Now I can successfully launch i3 or awesome with startx > /usr/local/bin/mywm but there is still the same xauth error: bad > display name. > $DISPLAY command returns nothing > > 2016-01-30 18:09 GMT+01:00 Peter N. M. Hansteen <pe...@bsdly.net>: >> On 01/30/16 17:48, Lô Baret wrote: >>> >>> Hello, I recently installed OpenBSD 5.8 amd64 for the first time >>> (default install options all the way) on my laptop (Thinkpad X200s) >>> and everything went well until I tried to startx another window >>> manager than the default fvwm. >>> >>> startx launches fvwm correctly but whenever I try with another window >>> manager with startx /usr/bin/mywm (i3 or awesome or cwm) I get this >>> error. I've looked for my wm packages in /usr/bin/ today and found >>> nothing (???) but it seems to be still present on the system (don't >>> know how to find package location) >> >> >> anything that comes out of packages (or ports) tends to land somewhere under >> /usr/local, so the binaries you're looking for will likely be in >> /usr/local/bin. >> >> Other than that, pasting the error message (minus the hostname) into a >> favorite search engine produces a number of potentially useful hints. >> >> >> -- >> Peter N. M. Hansteen, member of the first RFC 1149 implementation team >> http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ >> "Remember to set the evil bit on all malicious network traffic" >> delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: xauth: (argv):1: bad display name "BadSystemDetected.my.domain:0" in "remove" command
I always get that error. I have been ignoring it and so far no problems that I can tell. On 02/01/16 14:58, Lô Baret wrote: I tried to Xorg -configure today and I get this : (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d" (EE) Segmentation fault at address 0x28 Fatal server error: (EE) Caught Signal 11 (Segmentation Fault). Server aborting Still don't know what to do with it. 2016-01-30 18:34 GMT+01:00 Lô Baret <lo.ba...@gmail.com>: Thanks for the answer, i've already looked for solutions in the mailing list archive and on numerous forums. Now I can successfully launch i3 or awesome with startx /usr/local/bin/mywm but there is still the same xauth error: bad display name. $DISPLAY command returns nothing 2016-01-30 18:09 GMT+01:00 Peter N. M. Hansteen <pe...@bsdly.net>: On 01/30/16 17:48, Lô Baret wrote: Hello, I recently installed OpenBSD 5.8 amd64 for the first time (default install options all the way) on my laptop (Thinkpad X200s) and everything went well until I tried to startx another window manager than the default fvwm. startx launches fvwm correctly but whenever I try with another window manager with startx /usr/bin/mywm (i3 or awesome or cwm) I get this error. I've looked for my wm packages in /usr/bin/ today and found nothing (???) but it seems to be still present on the system (don't know how to find package location) anything that comes out of packages (or ports) tends to land somewhere under /usr/local, so the binaries you're looking for will likely be in /usr/local/bin. Other than that, pasting the error message (minus the hostname) into a favorite search engine produces a number of potentially useful hints. -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
xauth: (argv):1: bad display name "BadSystemDetected.my.domain:0" in "remove" command
Hello, I recently installed OpenBSD 5.8 amd64 for the first time (default install options all the way) on my laptop (Thinkpad X200s) and everything went well until I tried to startx another window manager than the default fvwm. startx launches fvwm correctly but whenever I try with another window manager with startx /usr/bin/mywm (i3 or awesome or cwm) I get this error. I've looked for my wm packages in /usr/bin/ today and found nothing (???) but it seems to be still present on the system (don't know how to find package location) I've tried to set my /etc/hosts host name but it doesn't work. I'm totally new to BSD's and fairly new to Unix systems configuration so I don't understand how everything works. My /etc/hosts looks like this: 127.0.0.1localhost localhost.localdomain BadSystemDetected.localdomain ::1 localhost localhost.localdomain BadSystemDetected.localdomain Thanks in advance.
Re: xauth: (argv):1: bad display name "BadSystemDetected.my.domain:0" in "remove" command
On 01/30/16 17:48, Lô Baret wrote: Hello, I recently installed OpenBSD 5.8 amd64 for the first time (default install options all the way) on my laptop (Thinkpad X200s) and everything went well until I tried to startx another window manager than the default fvwm. startx launches fvwm correctly but whenever I try with another window manager with startx /usr/bin/mywm (i3 or awesome or cwm) I get this error. I've looked for my wm packages in /usr/bin/ today and found nothing (???) but it seems to be still present on the system (don't know how to find package location) anything that comes out of packages (or ports) tends to land somewhere under /usr/local, so the binaries you're looking for will likely be in /usr/local/bin. Other than that, pasting the error message (minus the hostname) into a favorite search engine produces a number of potentially useful hints. -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: xauth: (argv):1: bad display name "BadSystemDetected.my.domain:0" in "remove" command
Thanks for the answer, i've already looked for solutions in the mailing list archive and on numerous forums. Now I can successfully launch i3 or awesome with startx /usr/local/bin/mywm but there is still the same xauth error: bad display name. $DISPLAY command returns nothing 2016-01-30 18:09 GMT+01:00 Peter N. M. Hansteen <pe...@bsdly.net>: > On 01/30/16 17:48, Lô Baret wrote: >> >> Hello, I recently installed OpenBSD 5.8 amd64 for the first time >> (default install options all the way) on my laptop (Thinkpad X200s) >> and everything went well until I tried to startx another window >> manager than the default fvwm. >> >> startx launches fvwm correctly but whenever I try with another window >> manager with startx /usr/bin/mywm (i3 or awesome or cwm) I get this >> error. I've looked for my wm packages in /usr/bin/ today and found >> nothing (???) but it seems to be still present on the system (don't >> know how to find package location) > > > anything that comes out of packages (or ports) tends to land somewhere under > /usr/local, so the binaries you're looking for will likely be in > /usr/local/bin. > > Other than that, pasting the error message (minus the hostname) into a > favorite search engine produces a number of potentially useful hints. > > > -- > Peter N. M. Hansteen, member of the first RFC 1149 implementation team > http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ > "Remember to set the evil bit on all malicious network traffic" > delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: Auto-configuring clients + Xauth for ipsec (isakmpd) road warrior VPN
On Friday, April 24, 2015 9:36 AM, Stuart Henderson s...@spacehopper.org wrote: On 2015-04-23, Yassen Damyanov yassen_...@yahoo.com wrote: Now I would like to auto-configure the clients (ike config pull) and allow for Mutual psk + xauth authentication. Having no any clue on how to do this OpenBSD isakmpd does not support xauth. There is user authentication available in IKEv2 (iked), but this is a different protocol, and you can't run it alongside isakmpd on the same machine. Stuart, thanks much for your help. How about running on different ports, maybe different enc interface, on the same machine?
Re: Auto-configuring clients + Xauth for ipsec (isakmpd) road warrior VPN
On Friday, April 24, 2015 10:17 AM, Stuart Henderson s...@spacehopper.org wrote: On 2015-04-24, Yassen Damyanov yassen_...@yahoo.com wrote: Stuart, thanks much for your help. How about running on different ports, maybe different enc interface, on the same machine? This came up before: http://thread.gmane.org/gmane.os.openbsd.tech/35967/focus=35967 Sadly this is not currently possible, firstly the port numbers are defined by the protocol and can't be changed (different IPs could theoretically work, but would need code changes as iked doesn't support binding to a specific address) but secondly, iked clears SAs from the kernel so any existing isakmpd sessions get broken Well, I see ... no way :) (Thanks again for saving me hours or days to discover that by trial and error.) Cheers,Y.
Re: Auto-configuring clients + Xauth for ipsec (isakmpd) road warrior VPN
On 2015-04-24, Yassen Damyanov yassen_...@yahoo.com wrote: On Friday, April 24, 2015 9:36 AM, Stuart Henderson s...@spacehopper.org wrote: On 2015-04-23, Yassen Damyanov yassen_...@yahoo.com wrote: Now I would like to auto-configure the clients (ike config pull) and allow for Mutual psk + xauth authentication. Having no any clue on how to do this OpenBSD isakmpd does not support xauth. There is user authentication available in IKEv2 (iked), but this is a different protocol, and you can't run it alongside isakmpd on the same machine. Stuart, thanks much for your help. How about running on different ports, maybe different enc interface, on the same machine? This came up before: http://thread.gmane.org/gmane.os.openbsd.tech/35967/focus=35967 Sadly this is not currently possible, firstly the port numbers are defined by the protocol and can't be changed (different IPs could theoretically work, but would need code changes as iked doesn't support binding to a specific address) but secondly, iked clears SAs from the kernel so any existing isakmpd sessions get broken.
Auto-configuring clients + Xauth for ipsec (isakmpd) road warrior VPN
I am trying to provide a road warrior ipsec vpn solution using isakmpd. (The router already runs three site-to-site ipsec channels via isakmpd already.) Now able to create the channel using a psk and a static ip on the client side (no authentication other than the psk). Now I would like to auto-configure the clients (ike config pull) and allow for Mutual psk + xauth authentication. Having no any clue on how to do this ... hours of googling does not yield much useful stuff for me. Would you guys help me sort this out? Any input greatly appreciated. Yassen
Re: Auto-configuring clients + Xauth for ipsec (isakmpd) road warrior VPN
On 2015-04-23, Yassen Damyanov yassen_...@yahoo.com wrote: I am trying to provide a road warrior ipsec vpn solution using isakmpd. (The router already runs three site-to-site ipsec channels via isakmpd already.) Now able to create the channel using a psk and a static ip on the client side (no authentication other than the psk). Now I would like to auto-configure the clients (ike config pull) and allow for Mutual psk + xauth authentication. Having no any clue on how to do this ... hours of googling does not yield much useful stuff for me. Would you guys help me sort this out? Any input greatly appreciated. Yassen OpenBSD isakmpd does not support xauth. There is user authentication available in IKEv2 (iked), but this is a different protocol, and you can't run it alongside isakmpd on the same machine.
Re: xauth
Instead of fixing Xenocara or other programs, the proper way to solve this issue is to elliminate the possibility to have multiple records of the same host in /etc/hosts file. I was stunned to see that after installing fresh OpenBSD and configuring and setting it up, I had several entries for 127.0.0.1 in my hosts file without modifying it by hand. It is clearly a flaw in OpenBSD or even standard Unix libraries. So the patch for Xenocara is a quickhack instead of a fix for the problem. If there are several entries of the same host in hosts file, then I would expect misbehaving programs all over the place but unfortunately only xauth was complaining here is a very recent install's hosts file: cat /etc/hosts # $OpenBSD: hosts,v 1.12 2009/03/10 00:42:13 deraadt Exp $ # # Host Database # # RFC 1918 specifies that these networks are internal. # 10.0.0.0 10.255.255.255 # 172.16.0.0172.31.255.255 # 192.168.0.0 192.168.255.255 # 127.0.0.1 localhost ::1 localhost 192.168.80.167 ner0.witworx.com ner0 end of file I see only one line for each address. It is totally autogenerated. Why do you have more than one line per address? We haven't seen your hosts file so we are only guessing. I cannot find any machines around here (including old stuff that isn't updated because it's only for being a PXE boot-server on the LAN etc.) that has it otherwise. Hello. I had the same problem. I've tested it to see when it happens. On a 4.5 install duplicate entries of 127.0.0.1 in hosts file do appear if you configure your net address through dhcp. Done it and seen it in a few installs today. If dhcp is a chosen option then you'll get the last line: 127.0.0.0 somehost.somewhere.local somehost with previous entries conforming to your example, creating multiple 127.0.0.1 entries. It does not happen if you enter a static address during install. Also does not happen if you use a current snaphot, address being specified in either of the ways. So, I guess its fixed in a new install.
Re: xauth
On Sun, Jul 19, 2009 at 10:49 AM, Matthias Kilian k...@outback.escape.de wrote: On Sun, Jul 19, 2009 at 02:38:08AM +, 4625 wrote: On first run and exit from X, I have 'Segmentation fault (core dumped)' (xauth.core). [...] How old is you X installation? Afaik this bug was fixed in march 09. My X come with OpenBSD 4.5 distributive. The fix had been merged to the stable branch (OPENBSD_4_5) of xenocara, so just rebuild xauth from this branch. Or look for duplicate entries in your /etc/hosts and remove them. Ciao, Kili Instead of fixing Xenocara or other programs, the proper way to solve this issue is to elliminate the possibility to have multiple records of the same host in /etc/hosts file. I was stunned to see that after installing fresh OpenBSD and configuring and setting it up, I had several entries for 127.0.0.1 in my hosts file without modifying it by hand. It is clearly a flaw in OpenBSD or even standard Unix libraries. So the patch for Xenocara is a quickhack instead of a fix for the problem. If there are several entries of the same host in hosts file, then I would expect misbehaving programs all over the place but unfortunately only xauth was complaining
Re: xauth
On Sun, 4 Oct 2009 13:03:02 +0300, Rein Kadastik wrote: On Sun, Jul 19, 2009 at 10:49 AM, Matthias Kilian k...@outback.escape.de wrote: On Sun, Jul 19, 2009 at 02:38:08AM +, 4625 wrote: On first run and exit from X, I have 'Segmentation fault (core dumped)' (xauth.core). [...] How old is you X installation? Afaik this bug was fixed in march 09. My X come with OpenBSD 4.5 distributive. The fix had been merged to the stable branch (OPENBSD_4_5) of xenocara, so just rebuild xauth from this branch. Or look for duplicate entries in your /etc/hosts and remove them. Ciao, Kili Instead of fixing Xenocara or other programs, the proper way to solve this issue is to elliminate the possibility to have multiple records of the same host in /etc/hosts file. I was stunned to see that after installing fresh OpenBSD and configuring and setting it up, I had several entries for 127.0.0.1 in my hosts file without modifying it by hand. It is clearly a flaw in OpenBSD or even standard Unix libraries. So the patch for Xenocara is a quickhack instead of a fix for the problem. If there are several entries of the same host in hosts file, then I would expect misbehaving programs all over the place but unfortunately only xauth was complaining here is a very recent install's hosts file: cat /etc/hosts # $OpenBSD: hosts,v 1.12 2009/03/10 00:42:13 deraadt Exp $ # # Host Database # # RFC 1918 specifies that these networks are internal. # 10.0.0.0 10.255.255.255 # 172.16.0.0172.31.255.255 # 192.168.0.0 192.168.255.255 # 127.0.0.1 localhost ::1 localhost 192.168.80.167 ner0.witworx.com ner0 end of file I see only one line for each address. It is totally autogenerated. Why do you have more than one line per address? We haven't seen your hosts file so we are only guessing. I cannot find any machines around here (including old stuff that isn't updated because it's only for being a PXE boot-server on the LAN etc.) that has it otherwise. *** NOTE *** Please DO NOT CC me. I am subscribed to the list. Mail to the sender address that does not originate at the list server is tarpitted. The reply-to: address is provided for those who feel compelled to reply off list. Thankyou. Rod/ --- This life is not the real thing. It is not even in Beta. If it was, then OpenBSD would already have a man page for it.
Re: xauth
On Sun, Oct 04, 2009 at 01:03:02PM +0300, Rein Kadastik wrote: The fix had been merged to the stable branch (OPENBSD_4_5) of xenocara, so just rebuild xauth from this branch. Or look for duplicate entries in your /etc/hosts and remove them. Instead of fixing Xenocara or other programs, the proper way to solve this issue is to elliminate the possibility to have multiple records of the same host in /etc/hosts file. Like, make it read-only and immutable or some shit? I was stunned to see that after installing fresh OpenBSD and configuring and setting it up, I had several entries for 127.0.0.1 in my hosts file without modifying it by hand. It is clearly a flaw in OpenBSD or even standard Unix libraries. This shouldn't happen, I didn't see this in recent installs. I don't have spare box for testing, but since Rod already wrote that he doesn't have seen duplicate entries in his installs, I doubt there's an error in the installer. So the patch for Xenocara is a quickhack instead of a fix for the problem. Fixing a NULL pointer deref is a quick hack? Did you even *look* at the bug and the bug fix? If there are several entries of the same host in hosts file, then I would expect misbehaving programs all over the place but unfortunately only xauth was complaining xauth didn't complain, it crashed. Because it had a bug. That bug has been fixed. So what? Ciao, Kili
Re: xauth
On Sun, Jul 19, 2009 at 02:38:08AM +, 4625 wrote: On first run and exit from X, I have 'Segmentation fault (core dumped)' (xauth.core). [...] How old is you X installation? Afaik this bug was fixed in march 09. My X come with OpenBSD 4.5 distributive. The fix had been merged to the stable branch (OPENBSD_4_5) of xenocara, so just rebuild xauth from this branch. Or look for duplicate entries in your /etc/hosts and remove them. Ciao, Kili
Re: xauth
On Sun 19.Jul'09 at 9:49:27 +0200, Matthias Kilian wrote: On Sun, Jul 19, 2009 at 02:38:08AM +, 4625 wrote: On first run and exit from X, I have 'Segmentation fault (core dumped)' (xauth.core). [...] How old is you X installation? Afaik this bug was fixed in march 09. The fix had been merged to the stable branch (OPENBSD_4_5) of xenocara, so just rebuild xauth from this branch. I installed OpenBSD4.5 yesterday and i'm having the exact same issue. Removing the ~/.Xauthority file does allow X to start again. -- Jamie . PGP Key ID: 0x842DD368 PGP Key Fingerprint: F850 A09C F877 FBC4 A63C FDDC 7484 4EEF 842D D368 [demime 1.01d removed an attachment of type application/pgp-signature]
Re: xauth
On Sun, Jul 19, 2009 at 10:27:41AM +0100, Jamie Griffin wrote: The fix had been merged to the stable branch (OPENBSD_4_5) of xenocara, so just rebuild xauth from this branch. I installed OpenBSD4.5 yesterday and i'm having the exact same issue. What's so difficult to understand in my mail? Rebuild xauth from the stable branch or remove duplicate entries in your /etc/hosts. Removing the ~/.Xauthority file does allow X to start again. Until the next segfault. Ciao, Kili
Re: xauth
I installed OpenBSD4.5 yesterday and i'm having the exact same issue. Removing the ~/.Xauthority file does allow X to start again. just to follow up on that, i did find a duplicate entry in /etc/hosts and removing it has fixed the problem. -- Jamie . PGP Key ID: 0x842DD368 PGP Key Fingerprint: F850 A09C F877 FBC4 A63C FDDC 7484 4EEF 842D D368 [demime 1.01d removed an attachment of type application/pgp-signature]
Re: xauth
On Sun, 19 Jul 2009, Jamie Griffin wrote: I installed OpenBSD4.5 yesterday and i'm having the exact same issue. Removing the ~/.Xauthority file does allow X to start again. just to follow up on that, i did find a duplicate entry in /etc/hosts and removing it has fixed the problem. Indeed, removing duplicate entry (in /etc/hotst) will fix this problem. -- 4625
Re: xauth
On Sat, Jul 18, 2009 at 4:55 AM, Philip Guentherguent...@gmail.com wrote: On 7/17/09, 4625 4625...@gmail.com wrote: On first run and exit from X, I have 'Segmentation fault (core dumped)' (xauth.core). On all following startx command - window manager unable connect to X server, while '.Xauthority' file are present in '~/' (home) dir. Can anyone help me to fix this problem? OpenBSD localhost 4.5 200907101811#0 i386 1) does removing your .Xauthority change the behavior? 2) does it happen with the stock 4.5 GENERIC or GENERIC.MP kernels? Philip How old is you X installation? Afaik this bug was fixed in march 09. -- Matthieu Herrb
Re: xauth
On Sat, 18 Jul 2009, Matthieu Herrb wrote: On first run and exit from X, I have 'Segmentation fault (core dumped)' (xauth.core). On all following startx command - window manager unable connect to X server, while '.Xauthority' file are present in '~/' (home) dir. Can anyone help me to fix this problem? OpenBSD localhost 4.5 200907101811#0 i386 1) does removing your .Xauthority change the behavior? 2) does it happen with the stock 4.5 GENERIC or GENERIC.MP kernels? How old is you X installation? Afaik this bug was fixed in march 09. My X come with OpenBSD 4.5 distributive. -- 4625
xauth
On first run and exit from X, I have 'Segmentation fault (core dumped)' (xauth.core). On all following startx command - window manager unable connect to X server, while '.Xauthority' file are present in '~/' (home) dir. Can anyone help me to fix this problem? OpenBSD localhost 4.5 200907101811#0 i386 -- 4625
Re: xauth
On 7/17/09, 4625 4625...@gmail.com wrote: On first run and exit from X, I have 'Segmentation fault (core dumped)' (xauth.core). On all following startx command - window manager unable connect to X server, while '.Xauthority' file are present in '~/' (home) dir. Can anyone help me to fix this problem? OpenBSD localhost 4.5 200907101811#0 i386 1) does removing your .Xauthority change the behavior? 2) does it happen with the stock 4.5 GENERIC or GENERIC.MP kernels? Philip
xauth segmentation fault when exiting x11
Hello, I've been running 4.5 beta current (update several times) for some times now, but I keep getting a segmentation fault from xauth when exiting X11, (and the $HOME/.Xauth* files are not removed) I'm not a programmer, so I'm not able to analyze it, may be someone can have a look into it. The xauth.core file can be downloaded here: http://www.wiroth.net/xauth.core.gz The dmesg is below. Thank you very much for helping, Dider OpenBSD 4.5-current (GENERIC.MP) #0: Fri Mar 6 08:17:59 CET 2009 r...@406334g.wiroth.net:/usr/obj/kernels/GENERIC.MP real mem = 3174764544 (3027MB) avail mem = 3066773504 (2924MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (74 entries) bios0: vendor LENOVO version 6FET56WW (2.02 ) date 01/09/2009 bios0: LENOVO 406334G acpi0 at bios0: rev 2 acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET SLIC BOOT ASF! SSDT TCPA SSDT S SDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) IGBE(S4) EXP0(S4) EXP1(S4) EXP2 (S4) EXP3(S4) EXP4(S4) PCI1(S4) USB0(S3) USB3(S3) USB5(S3) EHC0(S3) EHC1(S3) HDE F(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz, 2793.45 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,C X16,xTPR,NXE,LONG cpu0: 6MB 64b/line 16-way L2 cache cpu0: apic clock running at 265MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz, 2793.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,C X16,xTPR,NXE,LONG cpu1: 6MB 64b/line 16-way L2 cache ioapic0 at mainbus0 apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus 4 (EXP2) acpiprt5 at acpi0: bus 5 (EXP3) acpiprt6 at acpi0: bus 13 (EXP4) acpiprt7 at acpi0: bus 21 (PCI1) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2 acpicpu1 at acpi0: C3, C2 acpitz0 at acpi0: critical temperature 127 degC acpitz1 at acpi0: critical temperature 100 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model 42T4620 serial 3828 type LION oem Panasonic acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit offline acpithinkpad0 at acpi0 acpidock at acpi0 not configured acpivideo at acpi0 not configured acpivideo at acpi0 not configured cpu0: EST: strange msr value 0x06174a250600860f pci0 at mainbus0 bus 0: configuration mode 1 pchb0 at pci0 dev 0 function 0 Intel GM45 Host rev 0x07 vga1 at pci0 dev 2 function 0 Intel GM45 Video rev 0x07 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1: apic 1 int 16 (irq 11) drm0 at inteldrm0 Intel GM45 Video rev 0x07 at pci0 dev 2 function 1 not configured Intel GM45 HECI rev 0x07 at pci0 dev 3 function 0 not configured pciide0 at pci0 dev 3 function 2 Intel GM45 PT IDER rev 0x07: DMA (unsupported ), channel 0 wired to native-PCI, channel 1 wired to native-PCI pciide0: using apic 1 int 18 (irq 11) for native-PCI interrupt pciide0: channel 0 ignored (not responding; disabled or no drives?) pciide0: channel 1 ignored (not responding; disabled or no drives?) Intel GM45 AMT SOL rev 0x07 at pci0 dev 3 function 3 not configured em0 at pci0 dev 25 function 0 Intel ICH9 IGP M AMT rev 0x03: apic 1 int 20 (ir q 11), address 00:21:86:ff:1f:5c uhci0 at pci0 dev 26 function 0 Intel 82801I USB rev 0x03: apic 1 int 20 (irq 11) uhci1 at pci0 dev 26 function 1 Intel 82801I USB rev 0x03: apic 1 int 21 (irq 11) uhci2 at pci0 dev 26 function 2 Intel 82801I USB rev 0x03: apic 1 int 22 (irq 11) ehci0 at pci0 dev 26 function 7 Intel 82801I USB rev 0x03: apic 1 int 23 (irq 11) usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 Intel 82801I HD Audio rev 0x03: apic 1 int 1 7 (irq 11) azalia0: RIRB time out azalia0: codecs: Conexant CX20561, Conexant/0x2c06, using Conexant CX20561 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801I PCIE rev 0x03: apic 1 int 20 (irq 11) pci1 at ppb0 bus 2 ppb1 at pci0 dev 28 function 1 Intel 82801I PCIE rev 0x03: apic 1 int 21 (irq 11) pci2 at ppb1 bus 3 iwn0 at pci2 dev 0 function 0 Intel WiFi Link 5300AGN rev 0x00: apic 1 int 17 (irq 11), MIMO 3T3R, MoW, address 00:21:6a:0d:2f:0a ppb2 at pci0 dev 28 function 2 Intel 82801I PCIE rev 0x03: apic 1 int 22 (irq 11) pci3 at ppb2 bus 4 Intel Turbo Memory rev 0x11 at pci3 dev 0 function 0 not configured ppb3 at pci0 dev 28 function 3
Re: xauth segmentation fault when exiting x11
In case you would like to have a look a my xorg log file: http://www.wiroth.net/Xorg.0.log On Sunday 08 March 2009 10:41:02 Didier Wiroth wrote: Hello, I've been running 4.5 beta current (update several times) for some times now, but I keep getting a segmentation fault from xauth when exiting X11, (and the $HOME/.Xauth* files are not removed) I'm not a programmer, so I'm not able to analyze it, may be someone can have a look into it. The xauth.core file can be downloaded here: http://www.wiroth.net/xauth.core.gz The dmesg is below. Thank you very much for helping, Dider OpenBSD 4.5-current (GENERIC.MP) #0: Fri Mar 6 08:17:59 CET 2009 r...@406334g.wiroth.net:/usr/obj/kernels/GENERIC.MP real mem = 3174764544 (3027MB) avail mem = 3066773504 (2924MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (74 entries) bios0: vendor LENOVO version 6FET56WW (2.02 ) date 01/09/2009 bios0: LENOVO 406334G acpi0 at bios0: rev 2 acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET SLIC BOOT ASF! SSDT TCPA SSDT S SDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) IGBE(S4) EXP0(S4) EXP1(S4) EXP2 (S4) EXP3(S4) EXP4(S4) PCI1(S4) USB0(S3) USB3(S3) USB5(S3) EHC0(S3) EHC1(S3) HDE F(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz, 2793.45 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST, TM2,C X16,xTPR,NXE,LONG cpu0: 6MB 64b/line 16-way L2 cache cpu0: apic clock running at 265MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz, 2793.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST, TM2,C X16,xTPR,NXE,LONG cpu1: 6MB 64b/line 16-way L2 cache ioapic0 at mainbus0 apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus 4 (EXP2) acpiprt5 at acpi0: bus 5 (EXP3) acpiprt6 at acpi0: bus 13 (EXP4) acpiprt7 at acpi0: bus 21 (PCI1) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2 acpicpu1 at acpi0: C3, C2 acpitz0 at acpi0: critical temperature 127 degC acpitz1 at acpi0: critical temperature 100 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model 42T4620 serial 3828 type LION oem Panasonic acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit offline acpithinkpad0 at acpi0 acpidock at acpi0 not configured acpivideo at acpi0 not configured acpivideo at acpi0 not configured cpu0: EST: strange msr value 0x06174a250600860f pci0 at mainbus0 bus 0: configuration mode 1 pchb0 at pci0 dev 0 function 0 Intel GM45 Host rev 0x07 vga1 at pci0 dev 2 function 0 Intel GM45 Video rev 0x07 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1: apic 1 int 16 (irq 11) drm0 at inteldrm0 Intel GM45 Video rev 0x07 at pci0 dev 2 function 1 not configured Intel GM45 HECI rev 0x07 at pci0 dev 3 function 0 not configured pciide0 at pci0 dev 3 function 2 Intel GM45 PT IDER rev 0x07: DMA (unsupported ), channel 0 wired to native-PCI, channel 1 wired to native-PCI pciide0: using apic 1 int 18 (irq 11) for native-PCI interrupt pciide0: channel 0 ignored (not responding; disabled or no drives?) pciide0: channel 1 ignored (not responding; disabled or no drives?) Intel GM45 AMT SOL rev 0x07 at pci0 dev 3 function 3 not configured em0 at pci0 dev 25 function 0 Intel ICH9 IGP M AMT rev 0x03: apic 1 int 20 (ir q 11), address 00:21:86:ff:1f:5c uhci0 at pci0 dev 26 function 0 Intel 82801I USB rev 0x03: apic 1 int 20 (irq 11) uhci1 at pci0 dev 26 function 1 Intel 82801I USB rev 0x03: apic 1 int 21 (irq 11) uhci2 at pci0 dev 26 function 2 Intel 82801I USB rev 0x03: apic 1 int 22 (irq 11) ehci0 at pci0 dev 26 function 7 Intel 82801I USB rev 0x03: apic 1 int 23 (irq 11) usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 Intel 82801I HD Audio rev 0x03: apic 1 int 1 7 (irq 11) azalia0: RIRB time out azalia0: codecs: Conexant CX20561, Conexant/0x2c06, using Conexant CX20561 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801I PCIE rev 0x03: apic 1 int 20 (irq 11) pci1 at ppb0 bus 2 ppb1 at pci0 dev 28 function 1 Intel 82801I PCIE rev 0x03: apic 1 int 21 (irq 11) pci2 at ppb1 bus 3 iwn0 at pci2 dev 0 function 0 Intel WiFi Link 5300AGN rev 0x00: apic 1 int 17
Re: xauth segmentation fault when exiting x11
On Sun, Mar 8, 2009 at 4:41 AM, Didier Wiroth dwir...@gmail.com wrote: I've been running 4.5 beta current (update several times) for some times now, but I keep getting a segmentation fault from xauth when exiting X11, (and the $HOME/.Xauth* files are not removed) I'm not a programmer, so I'm not able to analyze it, may be someone can have a look into it. somebody already did... :) http://marc.info/?l=openbsd-bugsm=123650018716321w=2
Re: xauth segmentation fault when exiting x11
On Sunday 08 March 2009 11:55:58 Ted Unangst wrote: On Sun, Mar 8, 2009 at 4:41 AM, Didier Wiroth dwir...@gmail.com wrote: I've been running 4.5 beta current (update several times) for some times now, but I keep getting a segmentation fault from xauth when exiting X11, (and the $HOME/.Xauth* files are not removed) I'm not a programmer, so I'm not able to analyze it, may be someone can have a look into it. somebody already did... :) http://marc.info/?l=openbsd-bugsm=123650018716321w=2 Thanks, the patch solved the problem! Didier
xauth: (stdin):2: unknown command
Hello. When starting X server I'm getting following message: xauth: creating new authority file /home/raff/.serverauth.6489 xauth: (stdin):2: unknown command f7dc6384bd24019ab5620c73611c6135 xauth: (stdin):3: unknown command f7dc6384bd24019ab5620c73611c6135 xauth: (stdin):4: unknown command f7dc6384bd24019ab5620c73611c6135 Server starts and X are running fine, but what can cause those messages? dmesg: OpenBSD 4.4-beta (GENERIC) #977: Mon Jul 14 20:20:57 MDT 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: AMD Athlon(tm) XP 2000+ (AuthenticAMD 686-class, 256KB L2 cache) 1.71 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real mem = 804810752 (767MB) avail mem = 769478656 (733MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 08/10/04, BIOS32 rev. 0 @ 0xf9e80, SMBIOS rev. 2.3 @ 0xf0120 (37 entries) bios0: vendor Award Software International, Inc. version F4 date 08/10/2004 bios0: Gigabyte Technology Co., Ltd. GA-7VAX apm0 at bios0: Power Management spec V1.2 (slowidle) apm0: AC on, battery charge unknown acpi at bios0 function 0x0 not configured pcibios0 at bios0: rev 2.1 @ 0xf/0xc9c4 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfc910/176 (9 entries) pcibios0: PCI Exclusive IRQs: 5 7 10 11 pcibios0: PCI Interrupt Router at 000:17:0 (VIA VT82C596A ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0xd000 0xd/0x8000! cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 VIA VT8377 PCI rev 0x00 ppb0 at pci0 dev 1 function 0 VIA VT8235 AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 ATI Radeon 9200 rev 0x01 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) agp0 at vga1: v3, aperture at 0xd000, size 0x1000 ATI Radeon 9200 Sec rev 0x01 at pci1 dev 0 function 1 not configured ral0 at pci0 dev 11 function 0 Ralink RT2560 rev 0x01: irq 10, address 00:13:d3:73:7a:38 ral0: MAC/BBP RT2560 (rev 0x04), RF RT2525 uhci0 at pci0 dev 16 function 0 VIA VT83C572 USB rev 0x80: irq 5 uhci1 at pci0 dev 16 function 1 VIA VT83C572 USB rev 0x80: irq 7 uhci2 at pci0 dev 16 function 2 VIA VT83C572 USB rev 0x80: irq 11 ehci0 at pci0 dev 16 function 3 VIA VT6202 USB rev 0x82: irq 10 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 VIA EHCI root hub rev 2.00/1.00 addr 1 viapm0 at pci0 dev 17 function 0 VIA VT8235 ISA rev 0x00 iic0 at viapm0 maxtmp0 at iic0 addr 0x4c: lm90 spdmem0 at iic0 addr 0x50: 512MB DDR SDRAM non-parity PC2700CL2.5 spdmem1 at iic0 addr 0x51: 256MB DDR SDRAM non-parity PC2700CL2.5 pciide0 at pci0 dev 17 function 1 VIA VT82C571 IDE rev 0x06: ATA133, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: ST340014A wd0: 16-sector PIO, LBA48, 38166MB, 78165360 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets, initiator 7 cd0 at scsibus0 targ 0 lun 0: HL-DT-ST, CD-RW GCE-8520B, 1.04 ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 auvia0 at pci0 dev 17 function 5 VIA VT8233 AC97 rev 0x50: irq 11 ac97: codec id 0x414c4720 (Avance Logic ALC650) ac97: codec features 20 bit DAC, 18 bit ADC, Realtek 3D audio0 at auvia0 rl0 at pci0 dev 19 function 0 Realtek 8139 rev 0x10: irq 11, address 00:20:ed:52:04:db rlphy0 at rl0 phy 0: RTL internal PHY usb1 at uhci0: USB revision 1.0 uhub1 at usb1 VIA UHCI root hub rev 1.00/1.00 addr 1 usb2 at uhci1: USB revision 1.0 uhub2 at usb2 VIA UHCI root hub rev 1.00/1.00 addr 1 usb3 at uhci2: USB revision 1.0 uhub3 at usb3 VIA UHCI root hub rev 1.00/1.00 addr 1 isa0 at mainbus0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 it0 at isa0 port 0x2e/2: IT8705F rev 0x02, EC port 0x290 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 biomask ffed netmask ffed ttymask mtrr: Pentium Pro MTRR support uhidev0 at uhub1 port 1 configuration 1 interface 0 Logitech HID compliant keyboard rev 1.10/1.80 addr 2 uhidev0: iclass 3/1 ukbd0 at uhidev0: 8 modifier keys, 6 key codes wskbd1 at ukbd0 mux 1 wskbd1: connecting to wsdisplay0 uhidev1 at uhub1 port 1 configuration 1 interface 1 Logitech HID compliant keyboard rev 1.10/1.80 addr 2 uhidev1: iclass 3/0, 2 report ids uhid0 at uhidev1 reportid 1: input=2, output=0, feature=0 uhid1 at uhidev1 reportid 2: input=1, output=0, feature=0 softraid0 at root root on wd0a swap on wd0b dump on wd0b uhidev2 at uhub1 port 2 configuration 1 interface 0 Logitech USB RECEIVER rev 1.10/25.10 addr 3 uhidev2: iclass 3/1 ums0 at uhidev2: 16 buttons, Z dir wsmouse0 at ums0 mux 0 xorg.conf: Section Files
Re: Strange xauth entry
On Tue, Feb 07, 2006 at 08:56:10PM -0500, Dave Feustel wrote: I found the entry 10.0.3.15:0 in my .Xauthority file via the xauth list command. Assuming that I did not add that entry to the file, how might it have been added? Your box may have had that IP at some point? Joachim
