[Bug 1640514] Re: /snap/bin is not added to the PATH when using zsh
bash from the tty receives the PATH with "/snap/bin" via sourcing "/etc/profile" (bash initialization file), and does not have it set before this. zsh from the tty does not receive the path, since it doesn't source "/etc/profile", and "/etc/zsh/zshenv", which it does source, does not update the PATH. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640514 Title: /snap/bin is not added to the PATH when using zsh To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1640514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640514] Re: /snap/bin is not added to the PATH when using zsh
I partially retract my comment. The dash is lexicographically earlier. However, the fix pushed by vogt does not help with making "/snap/bin" available in zsh. I'll make a comment later if it turns out that these settings ought to have been be propagated to the environment in zsh from their current location but fail to. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640514 Title: /snap/bin is not added to the PATH when using zsh To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1640514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640514] Re: /snap/bin is not added to the PATH when using zsh
This still affects 19.10 eoan. I hope a bug administrator can update the status to reflect that. The push by vogt https://github.com/snapcore/snapd/pull/5390/files unfortunately does not work since by environment.d folder looks like this: -rw-r--r-- 1 root root 106 Oct 30 20:17 990-snapd.conf lrwxrwxrwx 1 root root 16 Feb 6 22:45 99-environment.conf -> /etc/environment Notably, 99-envorinment.conf is executed after 990-snapd.conf since it is lexically later, and after 990-snapd.conf writes PATH=$PATH:/snap/bin we have 99-environment.conf overwriting PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games" it should be noted that 99-environment.conf is provided by the systemd package. I'll also raise a bug there about the naming of 99-environment.conf . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640514 Title: /snap/bin is not added to the PATH when using zsh To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1640514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747646] Re: Authentication error with google drive [$10]
I would like to retract my report: my backups appear to not have completed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747646 Title: Authentication error with google drive [$10] To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1747646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747646] Re: Authentication error with google drive [$10]
I noticed that I encounter this error when I am connecting via a VPN service, and do not encounter this error when I am not. If the reason is that Google rejects authenticating from suspicious IPs with the kind of authentication deja-dup and GNOME's online accounts use, I don't know if the team can do anything about it. If this is indeed the case, I think a workaround by connecting from a non-blacklisted IP may work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747646 Title: Authentication error with google drive [$10] To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1747646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742318] Re: USB-Storage Quirk for 174c:1356
Hi, I am facing a related bug. I am using an SSD enclosure utilizing the ASM1352R controller as well. This controller supports RAID-0, RAID-1 and other configurations with up to two SSDs, and I'm currently using it with only one SSD; the product advertises as ASM1352R-Safe in this configuration, which is also what it advertises as when in RAID-1. I am running Debian buster. The advertised product IDs and serial, etc. are all different for me. Nevertheless, the bug still remains, and the fix proposed by OP works. OP mentioned "With/without UAS the issue persisted". I suspect that OP might be confused and does not realize that the fix he proposes is responsible for the message "UAS is blacklisted for this device, using usb-storage instead"; the quirk he used disables UAS support from the kernel side. Nevertheless, fix OP proposes is not a universal fix. ASMedia, reputable hardware manufacturer that it is, manufactures multiple chips with different architectures and capabilities under the same vendorId:productId identifier. Blacklisting this identifier will blacklist all its controllers, which may not exactly be a bad thing as multiple other models have issues with UAS under Linux as well. Inspection of latest upstream source seems that it is not handled upstream, though I have not tried running it. I'd be happy to contribute however I can but I have my hands tied if you need more info: I'm running Debian buster, and I'm running the controller with only one SSD. Nevertheless, it seems to me that this is an upstream bug and not Ubuntu-kernel specific. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742318 Title: USB-Storage Quirk for 174c:1356 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
