[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

[Adam Katz]

Peter:  Yes, that's all true (it's a workaround after all), though you
could add the ssh-agent command to your startup scripts.  I've updated
my Stack Exchange answer 
to reflect that.

BTW, you don't actually need the `mv` line since the .broken socket
isn't terribly useful.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/201786

Title:
  ssh Agent admitted failure to sign using the key on big endian
  machines

To manage notifications about this bug go to:
https://bugs.launchpad.net/seahorse/+bug/201786/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

[Adam Katz]

Peter:  Yes, that's all true (it's a workaround after all), though you
could add the ssh-agent command to your startup scripts.  I've updated
my Stack Exchange answer 
to reflect that.

BTW, you don't actually need the `mv` line since the .broken socket
isn't terribly useful.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/201786

Title:
  ssh Agent admitted failure to sign using the key on big endian
  machines

To manage notifications about this bug go to:
https://bugs.launchpad.net/seahorse/+bug/201786/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

[Adam Katz]

While this is not a big endian problem, it is a problem and it is NOT
solved yet.  I doubt it will be solved until Ubuntu bug 1420522
 is
solved.

This is GNOME bug 754028 
(Among others, see 
https://bugzilla.gnome.org/buglist.cgi?no_redirect=0=ed25519#)

** Bug watch added: GNOME Bug Tracker #754028
   https://bugzilla.gnome.org/show_bug.cgi?id=754028

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/201786

Title:
  ssh Agent admitted failure to sign using the key on big endian
  machines

To manage notifications about this bug go to:
https://bugs.launchpad.net/seahorse/+bug/201786/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

[Adam Katz]

While this is not a big endian problem, it is a problem and it is NOT
solved yet.  I doubt it will be solved until Ubuntu bug 1420522
 is
solved.

This is GNOME bug 754028 
(Among others, see 
https://bugzilla.gnome.org/buglist.cgi?no_redirect=0=ed25519#)

** Bug watch added: GNOME Bug Tracker #754028
   https://bugzilla.gnome.org/show_bug.cgi?id=754028

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/201786

Title:
  ssh Agent admitted failure to sign using the key on big endian
  machines

To manage notifications about this bug go to:
https://bugs.launchpad.net/seahorse/+bug/201786/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1420522] Re: It's not possible to create ED25519 SSH keys

[Adam Katz]

There is information on using (but not creating) ed25519 keys in
seahorse at bug 201786 and a workaround posted at
https://unix.stackexchange.com/a/189646/87770

Here is the seahorse bug: https://bugzilla.gnome.org/show_bug.cgi?id=754028
Related GNOME bugs: https://bugzilla.gnome.org/buglist.cgi?quicksearch=ed25519

** Bug watch added: GNOME Bug Tracker #754028
   https://bugzilla.gnome.org/show_bug.cgi?id=754028

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1420522

Title:
  It's not possible to create ED25519 SSH keys

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1420522/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

[Adam Katz]

Summary of problem (for me):

* ssh host fails with ssh Agent admitted failure
* SSH_AUTH_SOCK= ssh host works just fine
* Conclusion:  gnome-keyring can't deal with complex keys

WORKAROUND:

mv $SSH_AUTH_SOCK $SSH_AUTH_SOCK.broken
ssh-agent -a $SSH_AUTH_SOCK

This is a new instance of ssh-agent, so it won't have any keys in it
(despite what seahorse says, since that's tied to the .broken agent).
You'll have to add them via ssh-add.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/201786

Title:
  ssh Agent admitted failure to sign using the key on big endian
  machines

To manage notifications about this bug go to:
https://bugs.launchpad.net/seahorse/+bug/201786/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

[Adam Katz]

Summary of problem (for me):

* ssh host fails with ssh Agent admitted failure
* SSH_AUTH_SOCK= ssh host works just fine
* Conclusion:  gnome-keyring can't deal with complex keys

WORKAROUND:

mv $SSH_AUTH_SOCK $SSH_AUTH_SOCK.broken
ssh-agent -a $SSH_AUTH_SOCK

This is a new instance of ssh-agent, so it won't have any keys in it
(despite what seahorse says, since that's tied to the .broken agent).
You'll have to add them via ssh-add.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/201786

Title:
  ssh Agent admitted failure to sign using the key on big endian
  machines

To manage notifications about this bug go to:
https://bugs.launchpad.net/seahorse/+bug/201786/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 40189] Re: autofs needs to be restarted to pick up Windows XP shares

[Adam Katz]

Reproduced on Ibex (8.10), none of the above proposed workarounds solved
the issue.

The reason the above workarounds did not solve my issue was that my home
directory was mounted via autofs, so something like a script run by
NetworkManager, which requires a login, will not do the trick.  I'm not
sure why the /etc/network/*.d/ scripts didn't do it.  I had to create an
init script (attached).

Since the autofs-bump init script is a hack, I didn't know how to enter
it with update-rc.d ... here's how to do it manually:

sudo -s
cp etc_init.d_autofs-bump /etc/init.d/autofs-bump
chmod 755 /etc/init.d/autofs-bump
cd /etc
for L in 2 3 4 5; do
  cd rc$L.d
  ln -s ../init.d/autofs-bump S99autofs-bump
  cd -
done

** Attachment added: init script for workaround
   http://launchpadlibrarian.net/22563709/etc_init.d_autofs-bump

-- 
autofs needs to be restarted to pick up Windows XP shares
https://bugs.launchpad.net/bugs/40189
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 245017] Re: pidgin crashes with _XGetXCBBuffer: Assertion `((int) ((xcb_req) - (dpy-request)) = 0)' failed

[Adam Katz]

I hope I'm not stepping beyond my rights in changing the status and
taking the bug...

I'm respecting the original Confirmed status while marking it Fix
Released rather than Invalid the way Pidgin and others have marked
similar bugs.  (This bug should have been flagged Invalid because it
was a bug with the 'skype4pidgin' package/plugin rather than for Pidgin
itself, and there is no such package within the Debian or Ubuntu
repositories.  A better status would be a bugzilla-styled Worksforme)

Of course, that makes it odd for this bug to have a resolution of Fix
Released since the release part of that has nothing to do with
Ubuntu, but presumably anybody who had this bug found the plugin before
and can find it again (hint:  look at the comments above).

I use Skype via pidgin every day, and I haven't had skype4pidgin cause
this XCB crash since before my last comment.  There have been no other
posts noting that this is still a problem, and the skype4pidgin site has
confirmed the fix (including on Ubuntu itself) and closed the
corresponding bug.  Time to close this one, too.

** Changed in: pidgin (Ubuntu)
 Assignee: (unassigned) = Adam Katz (khopesh)
   Status: Confirmed = Fix Released

-- 
pidgin crashes with _XGetXCBBuffer: Assertion `((int) ((xcb_req) - 
(dpy-request)) = 0)' failed
https://bugs.launchpad.net/bugs/245017
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 40189] Re: autofs needs to be restarted to pick up Windows XP shares

[Adam Katz]

** Changed in: autofs (Ubuntu)
   Status: Fix Released = Incomplete

-- 
autofs needs to be restarted to pick up some shares
https://bugs.launchpad.net/bugs/40189
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 40189] Re: autofs needs to be restarted to pick up some shares

[Adam Katz]

** Summary changed:

- autofs needs to be restarted to pick up Windows XP shares
+ autofs needs to be restarted to pick up some shares

** Description changed:

  I am using autofs to access shares on a Windows XP machine from a
  Kubuntu AMD64 machine.  The problems applies in both Breezy and Dapper.
+ 
+ EDIT:  confirmed with similar configuration on Intrepid with a NetApp
+ filer hosting NFS.  Server OS removed from summary.
  
  When I first try to access the mount point via cd or in Konqueror it
  does not exist.  However,  if I then restart autofs (/etc/init.d/autofs
  restart) everythin then works OK.  My config files are:
  
  auto.master
  
  #
  # $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $
  #
  # Sample auto.master file
  # This is an automounter map and it has the following format
  # key [ -mount-options-separated-by-comma ] location
  # For details of the format look at autofs(5).
  #/misc/etc/auto.misc --timeout=60
  #/misc/etc/auto.misc
  #/net /etc/auto.net
  
  /petunia /etc/petunia.misc --timeout=60
  
  
  petunia.misc
  
  #
  # $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $
  #
  # This is an automounter map and it has the following format
  # key [ -mount-options-separated-by-comma ] location
  # Details may be found in the autofs(5) manpage
  
  cd  -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom
  
  tony  -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/tony
  chris -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/chris
  shared-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/SharedDocs
  linuxbackups  -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/linuxbackups

-- 
autofs needs to be restarted to pick up some shares
https://bugs.launchpad.net/bugs/40189
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 203385] Re: Recovery menu cannot be controlled with keyboard

[Adam Katz]

Still an issue on Ubuntu Intrepid 8.10 (with a Dell Latitude D530) when
altering the non-recovery mode boot option to suffix the word single
on the end of the loading.  This works fine when I go to recovery mode
directly, but I really expected appending single to the end of that
string to simply dump me in a root shell as if I had entered root from
the Recovery Menu (but without anywhere near so much stuff loading
beforehand).

-- 
Recovery menu cannot be controlled with keyboard
https://bugs.launchpad.net/bugs/203385
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 245017] Re: pidgin crashes with _XGetXCBBuffer: Assertion `((int) ((xcb_req) - (dpy-request)) = 0)' failed

[Adam Katz]

As of 2008-11-19, a new version of skype4pidgin was released with that
fix.  You should be able to upgrade to the latest version and this
problem should go away.  http://eion.robbmob.com/

I've been using it for a few hours without any issues, but it only
crashed about once a week for me beforehand.

The .deb looks pretty usable now.  Maybe it will find its way into
Debian Sid?

-- 
pidgin crashes with _XGetXCBBuffer: Assertion `((int) ((xcb_req) - 
(dpy-request)) = 0)' failed
https://bugs.launchpad.net/bugs/245017
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 245017] Re: pidgin crashes with _XGetXCBBuffer: Assertion `((int) ((xcb_req) - (dpy-request)) = 0)' failed

[Adam Katz]

Debian Lenny, pidgin 2.4.3-2, skype (via apt) 2.0.0.72-1, libxcb-render-
util0 0.2.1+git1-1, libxcb1 1.1-1.1, dev versions of xcb packages are
installed (total of 11 related libxcb* packages installed at above
versions).  As of September, this is still a bug.

However, this is NOT a bug with pidigin, as noted at
http://developer.pidgin.im/ticket/6367

The relevant bug is registered at
http://code.google.com/p/skype4pidgin/issues/detail?id=18

A search for the error message revealed this tip:
http://www.linuxquestions.org/linux/blog/Vermind/2008-08-01/Skype_Pidgin_Plugin
... but setting LIBXCB_ALLOW_SLOPPY_LOCK=1 does not solve this for me
(or at least, it doesn't fully solve the issue; either it reduced my
crash frequency or I've been less popular since trying it), and I'm less
interested in a custom xcb-lacking build of libX11 (which would
certainly solve the issue).

-- 
pidgin crashes with _XGetXCBBuffer: Assertion `((int) ((xcb_req) - 
(dpy-request)) = 0)' failed
https://bugs.launchpad.net/bugs/245017
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs