[Desktop-packages] [Bug 1586835] Re: ssh-agent fighting gnome-keyring on Ubuntu Gnome 16.04
I have located a way to disable ssh-agent by commenting out the use-ssh- agent line from file "/etc/X11/Xsession.options". But even after doing this it is not guaranteed that the $SSH_AUTH_SOCK variable will be set when I open a new terminal, even while doing so several minutes after I have logged into my GNOME session, presumably when all session programs are running. Sometimes I open a terminal and see that $SSH_AUTH_SOCK is set, then close it and open a new one a few minutes later, and there is no $SSH_AUTH_SOCK anymore. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1586835 Title: ssh-agent fighting gnome-keyring on Ubuntu Gnome 16.04 Status in gnome-keyring package in Ubuntu: New Bug description: Sometimes I open a terminal and try to login to a remote server, just to be greeted by a command-line-based prompt asking for my password. Whenever that happens, it is ssh-agent instead of gnome-keyring that is providing the SSH agent capabilities: $ echo $SSH_AUTH_SOCK /tmp/ssh-qeG7CTbx4w7D/agent.4592 $ ps -p 4592 -f UIDPID PPID C STIME TTY TIME CMD xeno 4592 4576 0 20:53 tty3 00:00:00 /usr/lib/gnome-session/gnome-session-binary --session=gnome $ ps -p $SSH_AGENT_PID -f UIDPID PPID C STIME TTY TIME CMD xeno 4652 4592 0 20:53 ?00:00:00 /usr/bin/ssh-agent /usr/bin/im-launch gnome-session --session=gnome I usually close the GNOME Terminal and open a new one (sometimes I must do this more than once), and I eventually get the expected output: $ echo $SSH_AUTH_SOCK /run/user/1000/keyring/ssh $ ps -p $SSH_AGENT_PID -f UIDPID PPID C STIME TTY TIME CMD xeno 4652 4592 0 20:53 ?00:00:00 /usr/bin/ssh-agent /usr/bin/im-launch gnome-session --session=gnome Interestingly, the $SSH_AGENT_PID variable seems to continue pointing to the process where ssh-agent is running. Generally once I get the keyring socket in the $SSH_AUTH_SOCK environment variable, it will stay that way even when I close the terminal and launch a new one. This seems to be a weird conflict between two programs offering the ssh-agent service. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1586835/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1586835] [NEW] ssh-agent fighting gnome-keyring on Ubuntu Gnome 16.04
Public bug reported: Sometimes I open a terminal and try to login to a remote server, just to be greeted by a command-line-based prompt asking for my password. Whenever that happens, it is ssh-agent instead of gnome-keyring that is providing the SSH agent capabilities: $ echo $SSH_AUTH_SOCK /tmp/ssh-qeG7CTbx4w7D/agent.4592 $ ps -p 4592 -f UIDPID PPID C STIME TTY TIME CMD xeno 4592 4576 0 20:53 tty3 00:00:00 /usr/lib/gnome-session/gnome-session-binary --session=gnome $ ps -p $SSH_AGENT_PID -f UIDPID PPID C STIME TTY TIME CMD xeno 4652 4592 0 20:53 ?00:00:00 /usr/bin/ssh-agent /usr/bin/im-launch gnome-session --session=gnome I usually close the GNOME Terminal and open a new one (sometimes I must do this more than once), and I eventually get the expected output: $ echo $SSH_AUTH_SOCK /run/user/1000/keyring/ssh $ ps -p $SSH_AGENT_PID -f UIDPID PPID C STIME TTY TIME CMD xeno 4652 4592 0 20:53 ?00:00:00 /usr/bin/ssh-agent /usr/bin/im-launch gnome-session --session=gnome Interestingly, the $SSH_AGENT_PID variable seems to continue pointing to the process where ssh-agent is running. Generally once I get the keyring socket in the $SSH_AUTH_SOCK environment variable, it will stay that way even when I close the terminal and launch a new one. This seems to be a weird conflict between two programs offering the ssh- agent service. ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1586835 Title: ssh-agent fighting gnome-keyring on Ubuntu Gnome 16.04 Status in gnome-keyring package in Ubuntu: New Bug description: Sometimes I open a terminal and try to login to a remote server, just to be greeted by a command-line-based prompt asking for my password. Whenever that happens, it is ssh-agent instead of gnome-keyring that is providing the SSH agent capabilities: $ echo $SSH_AUTH_SOCK /tmp/ssh-qeG7CTbx4w7D/agent.4592 $ ps -p 4592 -f UIDPID PPID C STIME TTY TIME CMD xeno 4592 4576 0 20:53 tty3 00:00:00 /usr/lib/gnome-session/gnome-session-binary --session=gnome $ ps -p $SSH_AGENT_PID -f UIDPID PPID C STIME TTY TIME CMD xeno 4652 4592 0 20:53 ?00:00:00 /usr/bin/ssh-agent /usr/bin/im-launch gnome-session --session=gnome I usually close the GNOME Terminal and open a new one (sometimes I must do this more than once), and I eventually get the expected output: $ echo $SSH_AUTH_SOCK /run/user/1000/keyring/ssh $ ps -p $SSH_AGENT_PID -f UIDPID PPID C STIME TTY TIME CMD xeno 4652 4592 0 20:53 ?00:00:00 /usr/bin/ssh-agent /usr/bin/im-launch gnome-session --session=gnome Interestingly, the $SSH_AGENT_PID variable seems to continue pointing to the process where ssh-agent is running. Generally once I get the keyring socket in the $SSH_AUTH_SOCK environment variable, it will stay that way even when I close the terminal and launch a new one. This seems to be a weird conflict between two programs offering the ssh-agent service. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1586835/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292113] Re: CTRL+ALT+T - shortcut to open Terminal is does not work
I get this problem sometimes in Ubuntu 15.04. Logging out and then logging back in usually fixes it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1292113 Title: CTRL+ALT+T - shortcut to open Terminal is does not work Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Fix Released Bug description: The global shortcut CTRL+ALT+T to open a new terminal windows is missing in Ubuntu since 14.04 Please reenable it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-terminal 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 13 18:01:32 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-10 (92 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to trusty on 2014-03-07 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1292113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245287] Re: upower showing keyboard at 0% charge
I have added information to the upstream package, and modified the patch slightly in my system to ignore Logitech K810 keyboard, which displays the same behaviour. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1245287 Title: upower showing keyboard at 0% charge Status in “upower” package in Ubuntu: Confirmed Bug description: This bug is new upon upgrading to 13.10; bug did not exist on 13.04, 12.10 or 12.04. I'm using an apple wireless keyboard. I have replaced the batteries and confirmed they are fully charged with voltmeter. Keyboard is working fine but indicator says it's 0% and is red indicating some problem. Also upower says "keyboard not present"; bluetooth shows keyboards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1245287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1009879] [NEW] NetworkManager high CPU usage while nm-applet and Transmission run
Public bug reported: If I leave my computer downloading overnight using BitTorrent client Transmission, I notice the next day that the NetworkManager process is eating up lots of CPU power. It gets immediately fixed if I kill nm- applet, although when I relaunch nm-applet CPU usage skyrockets again. Killing Transmission doesn't affect anything. I'm not sure there is a relation between Transmission and this issue, I just mention it because I only leave my computer on overnight when I download torrents. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1009879 Title: NetworkManager high CPU usage while nm-applet and Transmission run Status in “network-manager” package in Ubuntu: New Bug description: If I leave my computer downloading overnight using BitTorrent client Transmission, I notice the next day that the NetworkManager process is eating up lots of CPU power. It gets immediately fixed if I kill nm- applet, although when I relaunch nm-applet CPU usage skyrockets again. Killing Transmission doesn't affect anything. I'm not sure there is a relation between Transmission and this issue, I just mention it because I only leave my computer on overnight when I download torrents. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1009879/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1009879] Re: NetworkManager high CPU usage while nm-applet and Transmission run
Description:Ubuntu 12.04 LTS Release:12.04 Linux m1530 3.2.0-25-generic #40-Ubuntu SMP Wed May 23 20:30:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Package: network-manager Priority: optional Section: net Installed-Size: 1688 Maintainer: Ubuntu Core Dev Team Architecture: amd64 Version: 0.9.4.0-0ubuntu4.1 Package: transmission Priority: optional Section: net Installed-Size: 20 Maintainer: Ubuntu Developers Architecture: all Version: 2.33-0ubuntu2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1009879 Title: NetworkManager high CPU usage while nm-applet and Transmission run Status in “network-manager” package in Ubuntu: New Bug description: If I leave my computer downloading overnight using BitTorrent client Transmission, I notice the next day that the NetworkManager process is eating up lots of CPU power. It gets immediately fixed if I kill nm- applet, although when I relaunch nm-applet CPU usage skyrockets again. Killing Transmission doesn't affect anything. I'm not sure there is a relation between Transmission and this issue, I just mention it because I only leave my computer on overnight when I download torrents. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1009879/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
