[Desktop-packages] [Bug 1391775] [NEW] SSH_AUTH_SOCK and GPG_AGENT_INFO unset
Public bug reported: I use Distributor ID: Ubuntu Description:Ubuntu 14.04.1 LTS Release:14.04 Codename: trusty After some of the recent updates when using from terminal ssh or gpg started to ask key passphrase. I noticed that SSH_AUTH_SOCK and GPG_AGENT_INFO are unset. After playing around I found out that they are only unset when launching terminal using Alt-F2. If using Dash (Super), then it is fine.. env dump attached for both cases. you can see that env-alt-f2.txt has no SSH_AUTH_SOCK or GPG_AGENT_INFO set. Bad one has JOB=xsession-init. Good one has JOB=dbus. I am not sure if the problem of gnome-keyring.. - Dmitry ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: keyring upstrart ** Attachment added: Bad environment https://bugs.launchpad.net/bugs/1391775/+attachment/4258931/+files/env-alt-f2-terminal.txt -- 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/1391775 Title: SSH_AUTH_SOCK and GPG_AGENT_INFO unset Status in “gnome-keyring” package in Ubuntu: New Bug description: I use Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty After some of the recent updates when using from terminal ssh or gpg started to ask key passphrase. I noticed that SSH_AUTH_SOCK and GPG_AGENT_INFO are unset. After playing around I found out that they are only unset when launching terminal using Alt-F2. If using Dash (Super), then it is fine.. env dump attached for both cases. you can see that env-alt-f2.txt has no SSH_AUTH_SOCK or GPG_AGENT_INFO set. Bad one has JOB=xsession-init. Good one has JOB=dbus. I am not sure if the problem of gnome-keyring.. - Dmitry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1391775/+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 1391775] Re: SSH_AUTH_SOCK and GPG_AGENT_INFO unset
good envrionment ** Attachment added: Good environment https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1391775/+attachment/4258932/+files/env-super-terminal.txt -- 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/1391775 Title: SSH_AUTH_SOCK and GPG_AGENT_INFO unset Status in “gnome-keyring” package in Ubuntu: New Bug description: I use Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty After some of the recent updates when using from terminal ssh or gpg started to ask key passphrase. I noticed that SSH_AUTH_SOCK and GPG_AGENT_INFO are unset. After playing around I found out that they are only unset when launching terminal using Alt-F2. If using Dash (Super), then it is fine.. env dump attached for both cases. you can see that env-alt-f2.txt has no SSH_AUTH_SOCK or GPG_AGENT_INFO set. Bad one has JOB=xsession-init. Good one has JOB=dbus. I am not sure if the problem of gnome-keyring.. - Dmitry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1391775/+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 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
I have the same problem on 13.04, which is solved by 2 steps (as mentioned above): 1) uninstalling ureadahead or adding console none to /etc/init/ureadahead-other.conf 2) killing dhclient in umountfs. Indeed, why it has not been fixed for years -- 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/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 Status in Upstart: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “network-manager” package in Ubuntu: Triaged Status in “upstart” package in Ubuntu: Confirmed Bug description: 1. Format and label a target Ext4 partion using Ubuntu 12.04 2. Install 64bit 12.10 OS using that target without reformatting it 3. Shut down 4. Boot an alternate copy of Ubuntu 5. Restart selecting the newly installed OS 6. Login then shutdown 6. Boot an alternate copy of Ubuntu 7.Fsck the newly installed OS allowing corrections to be made Each time the the newly installed OS is executed and then shutdown, even if execution only consists of logging on, a subsequent fsck will FAIL. I used Acronis True Image Home 2013 to create an image of the newly installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4 filesystem corruption 100% of the time by restoring from the image, booting, logging on and shutting down. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aguru 1871 F pulseaudio /dev/snd/controlC0: aguru 1871 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Oct 30 22:24:54 2012 HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5Q-E ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5Q-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+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
