Page 2 of 2 FirstFirst 12
Results 11 to 15 of 15

Thread: 19.10, chromium snap and keepassxc

  1. #11
    Join Date
    Feb 2010
    Location
    South of the Maple Trees
    Beans
    9,268
    Distro
    Xubuntu 18.04 Bionic Beaver

    Re: 19.10, chromium snap and keepassxc

    Quote Originally Posted by nickmcg View Post
    I've just checked, keepassxc-browser also doesn't work with the snap firefox

    As a long time user of ubuntu, I have to say that I'm not impressed.
    I don't see a bug report for this, so it may be something that needs to be created. Snaps are frustrating. They have their place, but I don't think softwares that were already being regularly updated without library issues should be packaged this way.

  2. #12
    Join Date
    Dec 2014
    Beans
    1,606

    Re: 19.10, chromium snap and keepassxc

    Quote Originally Posted by uRock View Post
    Snaps are frustrating. They have their place, but I don't think softwares that were already being regularly updated without library issues should be packaged this way.
    Actually, programs that are updated often are exactly the target for using snaps. If you do it the traditional way, you have to compile and package a different version for each distribution you're supporting, might even have to compile and package a separate version for each release because the versions of libraries you use might be different across releases. With snap you just tell the user to get 'snapd' running on their system and publish one package for every distro because it brings along everything inside the package. This is a serious reduction of the workload for developers and packagers.

    Holger

  3. #13
    Join Date
    Feb 2010
    Location
    South of the Maple Trees
    Beans
    9,268
    Distro
    Xubuntu 18.04 Bionic Beaver

    Re: 19.10, chromium snap and keepassxc

    Quote Originally Posted by Holger_Gehrke View Post
    Actually, programs that are updated often are exactly the target for using snaps. If you do it the traditional way, you have to compile and package a different version for each distribution you're supporting, might even have to compile and package a separate version for each release because the versions of libraries you use might be different across releases. With snap you just tell the user to get 'snapd' running on their system and publish one package for every distro because it brings along everything inside the package. This is a serious reduction of the workload for developers and packagers.

    Holger
    Saving them a bit of time is not worth the forfeiture of system performance and program interoperability. People like the OP shouldn't have to change their security posture just because developers want to take shortcuts.

    Some say hard drives and RAM are cheap, I say more people have lost the value of money.

  4. #14
    Join Date
    Dec 2005
    Location
    U.K.
    Beans
    168
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: 19.10, chromium snap and keepassxc

    Quote Originally Posted by uRock View Post
    I don't see a bug report for this, so it may be something that needs to be created. Snaps are frustrating. They have their place, but I don't think softwares that were already being regularly updated without library issues should be packaged this way.
    The thing is, it's not a bug as such, it's a security feature of snaps.

  5. #15
    Join Date
    Feb 2010
    Location
    South of the Maple Trees
    Beans
    9,268
    Distro
    Xubuntu 18.04 Bionic Beaver

    Re: 19.10, chromium snap and keepassxc

    Quote Originally Posted by nickmcg View Post
    The thing is, it's not a bug as such, it's a security feature of snaps.
    A security feature that prevents integration with security software is a bug.

Page 2 of 2 FirstFirst 12

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •