[Bug 1700645] Re: gpg-agent not running when needed by Déjà Dup
'morning,
I'm also affected, I'm not sure since when as I only occasionally receive
encrypted emails.
Ubuntu 16.04.5 LTS
gpgv 1.4.20-1ubuntu3.3
gnupg-agent 2.1.11-6ubuntu2.1
1) use-agent is active in ~/.gnupg/gpg.conf
2) gpg-agent fails to start due to a missing /run/usr/$UID/gnupg directory
(/run/usr/$UID exists)
3) After repair ("mkdir /run/usr/$UID/gnupg"), gpg-agent starts automagically
with these arguments: --homedir /home/josef/.gnupg --use-standard-socket
--daemon, but still the socket is create in /run/user/UID/gnupg!
4) /etc/X11/Xsession.d/90gpg-agent exists
5) I use KDE (kde-baseapps-bin 4:15.12.3-0ubuntu1, though other KDE packages
are 4:5.5.5-0ubuntu1).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700645
Title:
gpg-agent not running when needed by Déjà Dup
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1700645/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643750] Re: Buffer Overflow in ZipInfo
I just found, that a different solution is already present in http://antinode.info/ftp/info-zip/unzip60/zipinfo.c Please ignore my drool. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643750 Title: Buffer Overflow in ZipInfo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unzip/+bug/1643750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643750] Re: Buffer Overflow in ZipInfo
May I humbly offer the attached patch? As the methbuf is used for display only, I have made it large enough to hold 'u' + an unsigned short (5 digits) + the trailing NUL character. ** Patch added: "cve-2016-9844.patch" https://bugs.launchpad.net/ubuntu/+source/unzip/+bug/1643750/+attachment/4818916/+files/cve-2016-9844.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643750 Title: Buffer Overflow in ZipInfo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unzip/+bug/1643750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1014159] Re: update-grub error: physical volume pv0 not found.
With the modification mentioned above, a kernel upgrade does not produce the error message any mode. Maybe "vgextend" or "pvcreate" should make sure the device is in the "device.map"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1014159 Title: update-grub error: physical volume pv0 not found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1014159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1014159] Re: update-grub error: physical volume pv0 not found.
Reboot has succeeded, now I'm waiting for the next kernel update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1014159 Title: update-grub error: physical volume pv0 not found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1014159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1014159] Re: update-grub error: physical volume pv0 not found.
In my case the problem was that my "pv0" device was not in "/boot/grub/device.map". Once I added (hd3) /dev/sdd the error disappeared, but this error now appears: grub-probe: error: unknown filesystem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1014159 Title: update-grub error: physical volume pv0 not found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1014159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1014159] Re: update-grub error: physical volume pv0 not found.
Ahhh ... OK ... PEBKAC: "grub-probe /" returns "ext3". Let's see what happens once I reboot, can't do that now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1014159 Title: update-grub error: physical volume pv0 not found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1014159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1014159] Re: update-grub error: physical volume pv0 not found.
I'm also affected. I'll put some pressure on myself: I'll try to find some time to help on this one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1014159 Title: update-grub error: physical volume pv0 not found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1014159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1033954] [NEW] Ubuntu 12.04 server installer: cannot change BIOS drive order
Public bug reported: When installing onto LUN 1 of an iSCSI target, the BIOS boot order may need to be changed to (hd0) /dev/sdb (hd1) /dev/sda but this is not possible within the installer. One solution is to change to an alternate console (Alt-F2) and create the device.map file, but this is tedious and error-prone! Thus, an option must be provided to change the BIOS drive order to something else than the default. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033954 Title: Ubuntu 12.04 server installer: cannot change BIOS drive order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1033954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1033498] [NEW] Ubuntu 12.04 iSCSI boot fails
Public bug reported: I have installed Ubuntu 12.04 server onto a Fujitsu BX924 blade server with an iSCSI-based root FS. The system has iSCSI boot code which provides an iBFT (iSCSI Boot Firmware Table). The installation went smoothly, but the first (and any subsequent) boots failed. The messages were IP-Config: no response after n secs - giving up IP-Config: eth0 hardware address c8:0a:a9:03:c5:34 mtu 1500 DHCP RARP IP-Config: eth0 hardware address c8:0a:a9:03:c5:34 mtu 1500 DHCP RARP (these three lines repeating with increasing values of n) As can be seen, the system has 2 interfaces, one (eth0) connected to a storage-only LAN and the other (eth1) to our company intranet. At first I got around this by break-ing into the boot process, setting up eth0 manually ip addr add 192.168.1.198/24 brd + dev eth0 ip link set dev eth0 up touch /tmp/net-eth0.conf# Signal eth0 is configured touch /tmp/net-eth1.conf# Signal eth1 is configured Later, I added the iscsi-ibft kernel module to the initramfs and code to the iscsi scriptlet to get the required information from the iBFT (added as an attachment). Note that this code lacks starting the DHCP client in case /sys/firmware/ibft/ethernet0/dhcp does contain a valid IP address. This is required so any lease on the address does not expire and the address is given to another client. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: boot ibft iscsi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033498 Title: Ubuntu 12.04 iSCSI boot fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1033498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1033498] Re: Ubuntu 12.04 iSCSI boot fails
** Patch added: Patch to get IP configuration from iBFT. https://bugs.launchpad.net/bugs/1033498/+attachment/3250042/+files/Ubuntu-iscsi.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033498 Title: Ubuntu 12.04 iSCSI boot fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1033498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1033500] [NEW] Ubuntu 12.04 iSCSI installation impossible onto LUN other than 0
Public bug reported: I am trying to install Ubuntu 12.04 server onto a Fujitsu BX920 blade server. I have a small zoo of systems and my target configuration is structured such that all installations of a given distro/release comprise one iSCSI target and different instances running on different hardware use separate LUNs: BX924 blade servers use LUN 0 BX920 blade servers use LUN 1 While installation onto a BX924 went smoothly, installation onto a BX920 was impossible because LUN1 was not selectable. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033500 Title: Ubuntu 12.04 iSCSI installation impossible onto LUN other than 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1033500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1033500] Re: Ubuntu 12.04 iSCSI installation impossible onto LUN other than 0
Oops ... I just found out that I have to be bold and get past the offer to use the given target! I have been able to select sdb (LUN1) and that's OK. - Not a bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033500 Title: Ubuntu 12.04 iSCSI installation impossible onto LUN other than 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1033500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 623462] Re: install to iSCSI target does not pick up iSCSI parameters from iBFT
Apart from the suggested addition of iscsi_ibft, IMHO there is some code required to actually use that information. I humbly offer the attached patch to use the information provided by the ibft to set up the iSCSI interface. It is not perfect, though, because if /sys/firmware/ibft/ethernet0/dhcp is not 0.0.0.0, dhclient3 would need to be started as well so the lease would be refreshed. Adding iscsi_ibft and this patch caused my BX924 blade server to boot Ubuntu Server 12.04. ** Attachment added: patch.iscsi https://bugs.launchpad.net/ubuntu/+source/partman-iscsi/+bug/623462/+attachment/3245841/+files/patch.iscsi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/623462 Title: install to iSCSI target does not pick up iSCSI parameters from iBFT To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/623462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
