[Bug 841672] Re: ssh-add does not always unlock ssh keys
Scratch my last workaround (#13). It didn't work. This one does though Stop gnome-keyring ssh-agent from starting. Then ssh-agent and ssh works as expected. To stop gnome-keyring ssh-agent from starting do: sudo mv /etc/xdg/autostart/gnome-keyring-ssh /etc/xdg/autostart /gnome-keyring-ssh.desktop.disabled I first posted this, plus a load of stuff about trying to work through the problem at http://askubuntu.com/questions/122824/how-to-manually- trigger-ssh-add-dialog-box/ -- 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/841672 Title: ssh-add does not always unlock ssh keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/841672/+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 841672] Re: ssh-add does not always unlock ssh keys
I found a way to trigger the gnome dialog box directly, so I only have to enter the ssh password once. I created ~/bin/gssh-add and put the following in it: SSH_ASK_PASS=/usr/bin/ssh-askpass ssh-add I then make it executable: chmod +x ~/bin/gssh-add And then I launch it using Alt+F2. That triggers the gnome dialog box. Note that if you run gssh-add from the terminal it will not trigger the gnome dialog box. See the ENVIRONMENT section of the ssh-add man page for details as to why. -- 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/841672 Title: ssh-add does not always unlock ssh keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/841672/+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 841672] Re: ssh-add does not always unlock ssh keys
My use case is that I have a script (using tmuxinator) that opens several shells inside tmux and executes ssh in them, all at once. I run ssh-add before starting the script, so that I only have to enter the passphrase once. However with this behaviour I have to enter the passphrase into the gui dialog box multiple times. After that ssh and the agent work as expected. But I can't seem to unlock the ssh key properly before starting an actual ssh session. -- 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/841672 Title: ssh-add does not always unlock ssh keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/841672/+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 50385] Re: samba does not support private dir option (qemu related)
Hi, work-around for user accounts you trust as administrators, if you don't want to run everything as root, but are not so insane as to use `chmod a+rw`: essentially just give the user permission to the files in the /var/lib/samba dir as noted by others earlier. (as root) # disable samba startup at boot: (so only qemu's one will be running) update-rc.d -f samba remove adduser $YOU adm chgrp adm /var/lib/samba/*.tdb chmod g+rw /var/lib/samba/*.tdb I also applied that to /var/lib/samba/perfmon and the parent dir but I don't know if that is really necessary. note that cd /tmp/qemu-smb.1234-0 /usr/sbin/smbd -i -s smb.conf ends with: """ ... Failed to open group mapping ldb '/var/lib/samba/group_mapping.ldb' - '(null)' ... Abnormal server exit: open_sockets_smbd() failed BACKTRACE: ... ... """ but C:\> net use e: \\10.0.2.4\qemu in the WinXP guest works. shrug. tested in Debian/squeeze + samba 2:3.5.6~dfsg-3squeeze2 :-/ Hamish -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/50385 Title: samba does not support private dir option (qemu related) -- 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 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
Hi Thierry There are lots of reasons why we don't use gvfs mounts. I am using a NAS and want the mounts to be there automatically on login. With gvfs mounts I have to go in an "activate" them each time. I use an rsync script for backing up from my NAS to an external hard disk drive and want to have defined mount points for that to work. There's no easy way to mount the smb shares from my NAS to a point that I want on my filesystem, without using fstab entries. Hamish -- Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
Hi Tom I installed Karmic Beta the other day and no longer get this error (with the entries in the /etc/fstab as I originally described). Hamish -- Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 211631] Re: CIFS/SMBFS issue (was not resolved on #207441)
I am commenting here to keep this thread alive, and wondering if any of the wpasupplicant team are looking at it? More than happy to keep experimenting and chatting about it! Thanks. Hamish -- CIFS/SMBFS issue (was not resolved on #207441) https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 211631] Re: CIFS/SMBFS issue (was not resolved on #207441)
Hi Steve I have changed wpa-ifupdown to S41 for both rc0.d and rc6.d, but I still get the problem. [EMAIL PROTECTED]:/etc/rc0.d$ ls K01gdm K30squidS30urandom K01usplash K39ufw S31umountnfs.sh K16dhcdbdK50alsa-utils S40umountfs K20apportK59mountoverflowtmp S41wpa-ifupdown K20atieventsdK99laptop-mode S60umountroot K20avahi-daemon README S90halt K20hddtemp S01linux-restricted-modules-common K25hwclock.shS20sendsigs [EMAIL PROTECTED]:/etc/rc6.d$ ls K01gdm K30squidS30urandom K01usplash K39ufw S31umountnfs.sh K16dhcdbdK50alsa-utils S40umountfs K20apportK59mountoverflowtmp S41wpa-ifupdown K20atieventsdK99laptop-mode S60umountroot K20avahi-daemon README S90reboot K20hddtemp S01linux-restricted-modules-common K25hwclock.shS20sendsigs Is there something else that needs to be changed? Can this be escalated? Hamish -- CIFS/SMBFS issue (was not resolved on #207441) https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 211631] Re: CIFS/SMBFS issue (was not resolved on #207441)
Hi Chuck I can umount and re- mount the shares using the command line (sudo umount -a and sudo mount -a) and it works successfully. I get nautilus sessions opening for each mounted drive every time I do this, which is very annoying! I can do the following: [EMAIL PROTECTED]:~$ sudo mount -t cifs //192.168.73.10/ /home/hamish/nas_ Password: And it works successfully :-) I *really* think that the problem is to do with the system attempting to read the /etc/fstab file and mount the drives *before* the network is up, and the reverse on the dismounts at shutdown/restart. [EMAIL PROTECTED]:/etc/rc2.d$ ls README S12dbus S20powernowd S89cron S01policykitS18avahi-daemon S20rsync S98usplash S05vbesaveS20apmd S24dhcdbd S99acpi-support S10acpid S20apport S24hal S99laptop-mode S10powernowd.early S20atieventsd S25pulseaudio S99rc.local S10sysklogd S20cupsys S30gdm S99rmnologin S10xserver-xorg-input-wacom S20hotkey-setupS89anacron S99stop-readahead S11klogd S20nvidia-kernel S89atd This works OK, as I get the drives mounted and then a separate nautilus session opens for each connected drive (which as I said previously is very annoying!), but we have the errors in the logs to prove that not all is good with this system of mounting drives. [EMAIL PROTECTED]:/etc/rc0.d$ ls K01gdm K39ufw S20sendsigs K01usplash K50alsa-utils S30urandom K16dhcdbd K59mountoverflowtmp S31umountnfs.sh K20apport K99laptop-mode S40umountfs K20atieventsd README S60umountroot K20avahi-daemonS01linux-restricted-modules-common S90halt K25hwclock.sh S15wpa-ifupdown [EMAIL PROTECTED]:/etc/rc6.d$ ls K01gdm K39ufw S20sendsigs K01usplashK50alsa-utils S30urandom K16dhcdbdK59mountoverflowtmp S31umountnfs.sh K20apport K99laptop-mode S40umountfs K20atieventsd README S60umountroot K20avahi-daemonS01linux-restricted-modules-common S90reboot K25hwclock.sh S15wpa-ifupdown As you can see, S40umountfs is *after* S15wpa-ifupdown in both the above rc0.d and rc6.d. I *strongly* believe this is the problem. Hope this helps Hamish -- CIFS/SMBFS issue (was not resolved on #207441) https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 211631] Re: CIFS/SMBFS issue (was not resolved on #207441)
lspci -vvnn ** Attachment added: "lspci -vvnn" http://launchpadlibrarian.net/13194770/lspci.txt -- CIFS/SMBFS issue (was not resolved on #207441) https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 211631] Re: CIFS/SMBFS issue (was not resolved on #207441)
...although I have included the error message in the original description above: CIFS VFS: server not responding CIFS VFS: no response for cmd 50 mid eventually after 2-3 minutes this times out and the computer restarts, but it isn't really good enough Hamish -- CIFS/SMBFS issue (was not resolved on #207441) https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 211631] Re: CIFS/SMBFS issue (was not resolved on #207441)
dmesg look for" [ 62.697883] CIFS VFS: Error connecting to IPv4 socket. Aborting operation [ 62.697948] CIFS VFS: cifs_mount failed w/return code = -101 then after that wlan0 is configured i think the timing of these operations is the problem how do i get the shutting down logs so I can show you the errors there? Hamish ** Attachment added: "dmesg log" http://launchpadlibrarian.net/13194695/dmesg.txt -- CIFS/SMBFS issue (was not resolved on #207441) https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 211631] Re: CIFS/SMBFS issue (was not resolved on #207441)
/var/log/messages from last startup [EMAIL PROTECTED]:~$ uname -r 2.6.24-15-generic ** Attachment added: "/var/log/messages" http://launchpadlibrarian.net/13194682/messages%20log.txt -- CIFS/SMBFS issue (was not resolved on #207441) https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 211631] Re: CIFS/SMBFS issue (was not resolved on #207441)
** Description changed: I installed smbfs, and then put some entries into /etc/fstab, so they automount on startup. An example of this is here: /// /home/hamish/ cifs credentials=/home/hamish/.smbcredentials,file_mode=0777,dir_mode=0777,uid=1000,gid=1000 0 0 ** note the use of "cifs" in the lines above ** (The username and password are in the .smbcredentials file) On startup, for each entry in the /etc/fstab file, I get the following in dmesg: [ 70.495504] CIFS VFS: Error connecting to IPv4 socket. Aborting operation [ 70.495569] CIFS VFS: cifs_mount failed w/return code = -101 But the shares are mounted, and a nautilus session opens up (which is also annoying...) Also logging off with CIFS shares mounted in /etc/fstab, it sits with an error message: CIFS VFS: server not responding CIFS VFS: no response for cmd 50 mid And takes about 2 minutes to timeout. This also happened with Gutsy Should the timing of the mounting and dismounting be changed so that it works? It is related to the starting of network-manager and CIFS shares trying to connect on startup *before* the network is up, and dismounting the shares *after* network-manager is stopped. Hamish - - PS: note to Chuck Short. I am using cifs. -- CIFS/SMBFS issue (was not resolved on #207441) https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 211631] [NEW] CIFS/SMBFS issue (was not resolved on #207441)
Public bug reported: I installed smbfs, and then put some entries into /etc/fstab, so they automount on startup. An example of this is here: /// /home/hamish/ cifs credentials=/home/hamish/.smbcredentials,file_mode=0777,dir_mode=0777,uid=1000,gid=1000 0 0 ** note the use of "cifs" in the lines above ** (The username and password are in the .smbcredentials file) On startup, for each entry in the /etc/fstab file, I get the following in dmesg: [ 70.495504] CIFS VFS: Error connecting to IPv4 socket. Aborting operation [ 70.495569] CIFS VFS: cifs_mount failed w/return code = -101 But the shares are mounted, and a nautilus session opens up (which is also annoying...) Also logging off with CIFS shares mounted in /etc/fstab, it sits with an error message: CIFS VFS: server not responding CIFS VFS: no response for cmd 50 mid And takes about 2 minutes to timeout. This also happened with Gutsy Should the timing of the mounting and dismounting be changed so that it works? It is related to the starting of network-manager and CIFS shares trying to connect on startup *before* the network is up, and dismounting the shares *after* network-manager is stopped. Hamish PS: note to Chuck Short. I am using cifs. ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- CIFS/SMBFS issue (was not resolved on #207441) https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 207441] Re: Hardy Beta - smbfs/cifs issues
I *am* using CIFS, as you can see in the /etc/fstab lines: /// /home/hamish/ cifs credentials=/home/hamish/.smbcredentials,file_mode=0777,dir_mode=0777,uid=1000,gid=1000 0 0 There is no CIFS in the repositories, so I installed SMBFS What I want to know is: * I have used the nautilus way of connecting to a share and created a "bookmark", but I cannot use VLC to play files from the bookmarked shares (smb:// is not supported) - this is a problem * when using CIFS, I get errors starting up and shutting down. I have detailed these in the bug report - this is still a problem I do NOT think that my bug report was correctly handled and would like some feedback on these issues that I have raised Thanks Hamish -- Hardy Beta - smbfs/cifs issues https://bugs.launchpad.net/bugs/207441 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 207441] Re: Hardy Beta - smbfs/cifs issues
** Description changed: "smbfs" is not installed by default, which it probably should be if this is to be used in the enterprise. Or is there an alternative, as I have been using "smbfs" for a few releases now and am not sure if how to mount SMB shares has changed for Hardy. - I installed smbfs, and then put some entries into /etc/fstab, so they automount on startup. On startup, for each entry in the /etc/fstab file, I get the following in dmesg: + I installed smbfs, and then put some entries into /etc/fstab, so they automount on startup. An example of this is here: + /// /home/hamish/ cifs credentials=/home/hamish/.smbcredentials,file_mode=0777,dir_mode=0777,uid=1000,gid=1000 0 0 + + (The username and password are in the .smbcredentials file) + + On startup, for each entry in the /etc/fstab file, I get the following in dmesg: [ 70.495504] CIFS VFS: Error connecting to IPv4 socket. Aborting operation [ 70.495569] CIFS VFS: cifs_mount failed w/return code = -101 But the shares are mounted, and a nautilus session opens up (which is also annoying...) - Also logging off with CIFS shares mounted in /etc/fstab, it sits with an - error message, and does not shutdown or restart. This also happened with - Gutsy, and was fixed using a script I found on the Ubuntu Forums. + Also logging off with CIFS shares mounted in /etc/fstab, it sits with an error message: + CIFS VFS: server not responding + CIFS VFS: no response for cmd 50 mid 775 + And takes about 2 minutes to timeout. This also happened with Gutsy, and was fixed using a script I found on the Ubuntu Forums. Is there an alternative way to mount the shares so that this doesn't happen, or should the timing of the mounting and dismounting be changed so that it works? I think it is related to the starting of network- manager and CIFS shares trying to connect on startup *before* the network is up, and dismounting the shares *after* network-manager is stopped. Hamish -- Hardy Beta - smbfs/cifs issues https://bugs.launchpad.net/bugs/207441 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 207441] [NEW] Hardy Beta - smbfs/cifs issues
Public bug reported: "smbfs" is not installed by default, which it probably should be if this is to be used in the enterprise. Or is there an alternative, as I have been using "smbfs" for a few releases now and am not sure if how to mount SMB shares has changed for Hardy. I installed smbfs, and then put some entries into /etc/fstab, so they automount on startup. On startup, for each entry in the /etc/fstab file, I get the following in dmesg: [ 70.495504] CIFS VFS: Error connecting to IPv4 socket. Aborting operation [ 70.495569] CIFS VFS: cifs_mount failed w/return code = -101 But the shares are mounted, and a nautilus session opens up (which is also annoying...) Also logging off with CIFS shares mounted in /etc/fstab, it sits with an error message, and does not shutdown or restart. This also happened with Gutsy, and was fixed using a script I found on the Ubuntu Forums. Is there an alternative way to mount the shares so that this doesn't happen, or should the timing of the mounting and dismounting be changed so that it works? I think it is related to the starting of network- manager and CIFS shares trying to connect on startup *before* the network is up, and dismounting the shares *after* network-manager is stopped. Hamish ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- Hardy Beta - smbfs/cifs issues https://bugs.launchpad.net/bugs/207441 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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
