Just another reason to avoid snaps. For me... why is LXD a snap??? If
you're using LXD then the machine is likely an important hypervisor host
and why wouldn't you want LXD fully integrated into the host's
filesystem. Isolating the program that isolates others? No sane person
would install
Would be great to have possibility to have hidden snap folder out of
experimental field in snap settings. If you need any help, code-wise,
money or whatever, just tell us. We will help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The only really sensible use case for Snaps, if any, is packaging
software that will never make it into an official repository, like some
3rd party software, e.g. MS-Office suite, or Photoshop. Servers use
docker or podman to deploy services. But what ever you do, please sort
out the mess with
Adding my voice to this. I will continue to run `sudo apt autoremove
--purge snapd` as the first command on every fresh installation of
Ubuntu until they no longer live in ~/snap. ~/.snap is a perfectly
acceptable alternative, ~/.local/snap is even better.
I will not use snaps - and if that
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/snap" directory to a less obtrusive location
To manage notifications about this bug go to:
echo snap >> ~/.hidden
Might be a default configuration for all new users if included in
/etc/skel ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/snap"
Just add an UI option to hide this folder from the system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/snap" directory to a less obtrusive location
To
For someone who is still struggling with this,
https://forum.snapcraft.io/t/experimental-flag-for-hiding-snap/28509 may help.
It seems that
sudo snap set system experimental.hidden-snap-folder=true
works and puts data in ~/.snap/data, but snap still creates an empty ~/snap on
app startups.
--
I just upgraded to 22.04, and was unpleasantly surprised to see ~/snap
as a new directory in HOME. If there is no solution for this issue I
will be switching back to Fedora.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can only echo acabal, foresto and a lot of the above comments. The
technical merit of snap is not the point. But cluttering the homedir as
a default _and_ offering no way around is not acceptable from any
application. Hidden folders do exist for a reason, /var exists for a
reason.
In the end,
The effectively forced use of Snap is what finally drove me to abandon
Ubuntu. This issue played a part in that.
To be clear, I am in favor of app isolation on desktop linux, and I find
container-based packaging useful in certain situations. However, the
Snap project has demonstrated over and
Before 22.04 I was able to just uninstall snapd to remove ~/snap, and
that was fine.
But now that Firefox is being delivered as only a Snap in 22.04, I'm
essentially being strong-armed into using snaps, because Firefox is
probably the most critical piece of software on my system and I cannot
work
Thank you, Ivan. I have add my "affects me" status and a comment there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/snap" directory to a less obtrusive
Given that this is affecting so many people: I've opened a request
against Ubuntu-meta so that Snap stops being recommended by default and
we make sure no packages provide snap-based installation only:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535
Feel free to comment there.
I would not care anymore were it not for the fact that snap is becoming
the default. We will have a less and less usable system if we just
remove snap.
Can we not just request to the Ubuntu team that snap be removed from the
default installation, and that no package should be made available only
I was so excited to see the link with more info on what the migration
will look like: https://forum.snapcraft.io/t/experimental-flag-for-
hiding-snap/28509/21
...only to find out that the end goal is to introduce a new ~/Snap
directory (that - if I understand correctly - again cannot be changed
@Maciej Borzecki I'll believe that when I see it.
This thread is a five-year history of users requesting a fix and the dev
team responding that the users are stupid and it's not really a big
problem.
Why should we believe you that this will ever be fixed, let alone
documented?
--
You received
@lukeweller you probably guessed this is not part of any release yet.
Documentation will be there in due time. In the meantime you're welcome
to contribute to the discussion in the forum or grab snapd from edge and
try it out yourself.
--
You received this bug notification because you are a
@Maciej Borzecki So that's it? There's an experimental setting I can
use to manually move my ~snap folder. No documentation to go with it?
No plans to actually implement this feature for anyone who isn't
extremely tech literate?
That solution is less helpful than the ~/.hidden workaround that
@lukeweller 3 commens up there's:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1575053/comments/308
there's also a forum topic with more details:
https://forum.snapcraft.io/t/experimental-flag-for-hiding-snap/28509
--
You received this bug notification because you are a member of Ubuntu
Is anyone from Canonical actually working on this bug? And why tf is
this still considered a "Wishlist" item after 1200 user reports and
hundreds of comments?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@dimitri-papadopoulos
If there's a high likelihood that ceph will be used on a desktop
distribution then its choice of snapshot directory has been incorrect in
two ways. The way forward would be to not ignore conventions designed to
avoid such issues :)
--
You received this bug notification
Note that .snap is also the default location of snapshots of the Ceph file
system (https://github.com/ceph/ceph). It's a hidden (not visible during a
directory listing) directory available in each directory of a mounted Ceph file
system. See:
This is actively being worked on - for those interested you can follow
the progress in https://github.com/snapcore/snapd/pull/10836
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
After 5 years there's still no fix. This is so annoying. I'm now getting
rid of all snap packages and installing deb variants instead. Finally
I'll purge snap and if these weird decisions keep on going I'll also
move to another distro. Common Canonical. Seriously?
--
You received this bug
To Snap and Ubuntu developers, here is a concrete example of why this is
important and so many people are annoyed.
Imagine a user likes to back up their home directory. (Imagine that!
Crazy stuff!)
The user will likely exclude hidden files from the backup, so as to
avoid filling their storage
Seeing how this has been treated for 4.5 years makes this seem like a
pretty dysfunctional project. Please have mercy on your poor users and
fix this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I finally resorted to the uninstall snap workaround. Annoying users and
being intrusive is a solid way to ensure the success of a package you're
responsible for.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I would not have that big a problem if Ubuntu had not made it the
preferred way of installing and packaging apps now.
It highlights more fundamental issues with the design of snap, with the
management, and with the way that it was included and promoted. And this
is just one issue that is
I humbly want to express my disbelief in that such a seemingly simple
problem: hiding Snap's own directory from the $HOME, which seems as easy
as renaming $HOME/snapd to $HOME/.snapd, has been going on for 5 years,
with a number of proposals and promises arising (as early as in
** Also affects: snapd (Debian)
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/1575053
Title:
Please move the "$HOME/snap" directory to a less obtrusive
@Gustavo and dev team
In #259 it was said that an approach has been discussed and agreement
uppon. I understand that on 2021-03-29 a fix was confirmed, although I
could not find anything on the matter (including the design document).
I am running snap/snapd 2-50 (full system, fresh install) and
** Also affects: snapd (Arch Linux)
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/1575053
Title:
Please move the "$HOME/snap" directory to a less
Hey guys what about the fix?
Placing a directory that was meant to be hidden to user's home dir is uncool.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/snap"
Ah my apologies was it fixed? Am I still running an old version? Thank
you thank you thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/snap" directory
Hello kind pple, pretty please move this dir from the central home
location, it does not belong there! Thank you kindly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the
** Changed in: snapd (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/snap" directory to a less obtrusive
** Changed in: snapd
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/snap" directory to a less obtrusive location
To
** Changed in: snapd
Status: Confirmed => Fix Released
** Changed in: snapd (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Was wondering if this is still scheduled for 21.04 as suggested in the
below comment by @niemeyer...
> From recent conversations with the team, the approach has been discussed and
> we have
> an agreement on it, we should now see a design document made public in the
> next few
> weeks
@Wolfgang: No worries. And as an early and vocal critic of the
"$HOME/snap" directory (see post #14, for example), I share your
frustration. But I've come to realize that devs truly want to, and are
working to, resolve the issue. We (the users of this FREE software)
just need to be patient.
GizmoChicken, I apologize for my post. Wanted to delete it but cannot
figure out how.
Was just so frustrated in the moment about the non-communication about
progress and that Canonical decided to push snap in the current state,
even though they participated from the beginning in this thread and
Wolfgang (wolfgang-v) wrote:
>@jean-miguel and anyone else affected: Please report your feedback to
Ubuntu customer support too, so that they can draw their own conclusion
on how their product decisions affect their user base.
Wolfgang, you forgot to suggest that all dissatisfied users should
@jean-miguel and anyone else affected: Please report your feedback to
Ubuntu customer support too, so that they can draw their own conclusion
on how their product decisions affect their user base.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This is my first time using snap, and i realized there's a 'snap' folder
in my $HOME. Google redirected me here. It's really a surprise that this
is still not fixed in 4.5 years.
We don't care those internal stuff. Please just get rid of this folder,
no more excuses. There are millions of linux
We just updated all of our Ubuntu installations to 20.04 and first
everything seems very smooth. But after installing chromium-browser the
annoyances began. After slow program starts we realized it's no real deb
package anymore and it silently installs a snap! Then users realized the
intrusive
>From a high level view it seems like the project is far from being
usable in mission critical systems if there are so many other problems
that are prioritized over this community outrage. But maybe i am wrong
and user feedback is just not valued here.
--
You received this bug notification
there is a workaround - apt purge snapd - this works for me
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/snap" directory to a less obtrusive location
To
:thumbs_down:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/snap" directory to a less obtrusive location
To manage notifications about this bug go to:
My hopes are still up - see comment #259 for some more information about
the process:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1575053/comments/259
I really hope 21.04 still is reachable. Not sure where to find the
public design document though (or if it even exists yet).
--
You
20.10
/home/user/snap still there...
I have a bad impression that he will never leave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/snap" directory to a less
Reproducing this critical problem in 20.04.1 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/snap" directory to a less obtrusive location
To manage
I found this page helpful,
https://www.kevin-custer.com/blog/disabling-snaps-in-ubuntu-20-04/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/snap" directory to
I would suggest you read through the past comments on this issue, and
the design document you mention. For example, "put things in the XDG
directories (~/.local, ~/.cache, ~/.config)" has been suggested many
times; it's explained earlier in the comments here (e.g. comment #30)
why that wouldn't
I really appreciate the effort put into snapd. However, as a fellow
software developer, I honestly fail to understand how an issue that's
been going on for 4 years and has the most heat of all issues
(https://bugs.launchpad.net/ubuntu/+source/snapd/+bugs?orderby=-heat=0),
that depends on **being
I came up with a convenient solution. I added the following to my
crontab:
* * * * * rm -rf /home/amichaux/snap
Works like a charm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
It is insane... it affects me too!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/snap" directory to a less obtrusive location
To manage notifications about
@polirecyliente,
Please allow me to reiterate what I wrote in post #265 of this thread:
>I was an early and vocal critic of the "$HOME/snap" directory who:
>
>(a) complained about this issue in numerous comments, including comment #14
>(posted 2017-04-16), >comment #15 (posted 2017-05-20),
I was doing a cleanup of my $HOME directory, and sadly I found this
"snap" dir, this made me follow through and find this open issue... open
for MORE than FOUR years already... is this fixable? Because if it's
fixable and this much time has happened I can't help but to feel
contempt for the snap
For whom does not care about multi users and backward compatibility,
this is actually quite straightforward to change the snap directory from
'$HOME/snap' to '$HOME/.snap'. Change the hard-coded path and the
apparmor rule is fairly enough for release 2.46:
diff --git
For whom does not care about multi users and backward compatibility,
this is actually quite straightforward to change the snap directory from
'$HOME/snap' to '$HOME/.snap'. Changing the hard-coded path and the
AppArmor rule is fairly enough for release 2.46:
diff --git a/dirs/dirs.go
For whom does not care about multi users and backward compatibility,
this is actually quite straightforward to change the snap directory from
'$HOME/snap' to '$HOME/.snap'. Change the hard-coded path and the
apparmor rule is fairly enough for release 2.46:
diff --git
This needs to go
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/snap" directory to a less obtrusive location
To manage notifications about this bug go to:
> How do you have "many more" voices to pay attention to? 1018 people
have marked
We have millions of users, Avamander.
> "I'm sorry you chose to feel insulted
Your words.
Now I'll stop here and hope that we can go back to being productive on
this issue. Failing that, we'll lock this thread up
> Not in your preferred timeline, unfortunately, but we have many more
issues and voices to pay attention to.
How do you have "many more" voices to pay attention to? 1018 people have
marked this issue as it affects them, if anything, you have *many fewer*
voices to listen to elsewhere.
> waiting
The way we select priorities for the project every single cycle for
years is having several stakeholders (that's more than a dozen people,
covering community, customers, development groups, etc) with several
different perspectives in a room after having followed a process of
funneling requirements
I already had an account, it's totally fine (see comments #184 and
#192).
I'm not individuality insulting anyone and I'm also not trying to be
rude. But come on, 4 years? If the developers are going to drag their
feet that long - an outright eternity in software development terms - on
such a high
This is a place for respectful collaboration about the project and the
issue at hand. People in the community are most welcome to participate
and help, and many have done exactly that.
Insults and blaming are not welcome here or anywhere else in this
community, though, no matter how much you care
So are we now shaming people because that they are personally affected
by a bug for years, that decided to participate in the community?
I suspect the reaction would be a lot milder without all this thinly-
veiled condescension constantly thrown at people here. I'm personally
appalled.
--
You
> a ridiculously mismanaged and misprioritized project
So you create an account just to come here say that? Indeed we have
different a notion of priorities and time allocation, David.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You say "as soon as practicable" but this bug is over 4 YEARS old now. I
think the frustration from the users is completely understandable and
justified. It's by far the hottest issue on the list but the developers
continue to waffle. Not that I think one more post is going to change
anything,
I was an early and vocal critic of the "$HOME/snap" directory who:
(a) complained about this issue in numerous comments, including comment #14
(posted 2017-04-16), comment #15 (posted 2017-05-20), comment #19 (posted
2017-07-12), and comment #32 (posted 2017-10-22);
(b) reverted the status
> In addition the ~/snap directory is very explicitly, and non-trivially
baked into apparmor profiles that are currently global to the system.
This setting can vary per user.
We have mechanisms in AppArmor to help with alternate locations for
things (there is the home tunable and we could add new
Zygmunt, let's stick to the design and the spec only. Speculation or
subjective remarks do not help the conversation.
Avamander, your personal notion of fault attribution won't help you or anyone
else.
There's a lot of people here. Let's please preserve this thread relevant and
respectful.
> In addition the ~/snap directory is very explicitly, and non-trivially
baked into apparmor profiles that are currently global to the system.
And whose fault is that? Should've thought about it sooner.
> Lastly .config and .local and .cache are just top-level directories
with absolutely no
Those are not fixed locations. You'd have to cope with responding to the
settings (that may differ per process) that govern their location. In
addition the ~/snap directory is very explicitly, and non-trivially
baked into apparmor profiles that are currently global to the system.
This setting can
I add my voice to the choir. We have two directories that can be used
for all configuration and locally needed files, .config and .local.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Hi Seth,
>From recent conversations with the team, the approach has been discussed
and we have an agreement on it, we should now see a design document made
public in the next few weeks (september still, hopefully), which means
an implementation available in the next few months. So we'll see it as
@Gustavo, happy to hear that progress is being made after nearly three
years of reports.
Do you have any estimate as to when the change will make it into the
next Ubuntu LTS release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Right, I spent my time explaining the design and trationale that got us
here, and in which direction we'll improve it. It seemed much more
interesting for everyone.
> WE are whining about it annoyingly.
You are the one saying that. It is a hot topic for several reasons, but
most people in this
>At this point you are the one ignoring what others are saying.
Come on @niemeyer, no point throwing fuel on the fire.
YOU guys screwed up bad with this. You have never really admitted that,
just promised to fix it.
WE are whining about it annoyingly. We have made our point and should
stop.
Folks, we said multiple times above that this is in the roadmap and
there's on going work to get it addressed. We'll be posting more details
about the actual change soon, and it's not just a rename.
> The community and it's voice matters - ignoring it will just cause
people to not support Ubuntu.
The real priority is on the upstream project. The Ubuntu package
priority is irrelevant and I cannot change it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the
> this now seems to be a priority bug which will be fixed fairly soon
Indicated by the status "Wishlist"?
> Nobody "wants to piss off" anyone, that is silly.
Oh it absolutely is. But two years, people have their limits when
assuming good faith.
> Most of us here are not paying customers,
@avamander If you read carefully the discussion above you will see that
the "resistance" has crumbled, this now seems to be a priority bug which
will be fixed fairly soon. The Snap team made a bad design mistake which
is harder to fix than it looks, see posts by @zyga for detail. Nobody
"wants to
The very least make it hidden. It's simply horrible in my neat home
folder, there's really no arguing against that.
The resistance to fix it baffles me the most. Add a dot to the damn path
and make the snapd package install script `mv` the folder if it exists
before the upgrade. It's not that
@niemeyer Your tone suggests that you do not understand why this
seemingly small issue is so important to many people. It is NOT just
esthetics, or rigid ideology. Others have mentioned issues with mounts
and disk space. Or imagine having a script which follows the XDG spec,
for backing up or
@niemeyer,
As someone commented on the potential urgency of this issue back in 2017
(see comments #14, #15, #19, etc.), I fully appreciate that this issue
is complex and that your team is diligently working toward a solution.
Also, I support snaps. Your work is appreciated! Ganbatte kudasai!!
If not having a ~/snap in your home is more important than what the
entire snap ecosystem provides, then removing it indeed sounds like the
right choice.
With that said, we've been working on this issue and Zygmunt says so
above quite clearly, because we care, and always did. But we can only
care
Egregious violation of the XDG specification, almost a thousand users
actively complaining, years of stalling, and still Snap managers are
explicitly saying that this bug is not a priority. You have to ask what
they think IS important, or whether they care about their users at all.
@zyga seems
It's been years. This is still annoying. May as well download my
applications from websites like a Windows user if package management is
going to be this dirty on Linux.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@zyga
Thank you! That's awesome!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/snap" directory to a less obtrusive location
To manage notifications about this
@Oliver
thx that worked. Its required that your user is owner of the snap folder. A bit
complicated to realise on an ntfs partition but possible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
to move the content of the dir you might be able to:
stop all snap apps ...
mv ~/snap /whereever/your/bigger/disk/is/mounted
mkdir ~/snap
sudo mount --bind /whereever/your/bigger/disk/is/mounted/snap ~/snap
you might need to adjust permissions on the target disk, the snap dir
must be fully
I didn't read all posts and i used snap yesterday for the first time.
I installed League of Legends which worked after a few tries, so great work.
But my system has 2 hard drives, a fast (and small) SSD for system data and a
classic one for large data. Now League of legends is about 10 Gb in my
@zyga Wonderful! Thanks in advance for working on this!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/snap" directory to a less obtrusive location
To manage
@zyga
GREAT NEWS! THANK YOU!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/snap" directory to a less obtrusive location
To manage notifications about this
To be clear, we've agreed to work on this in our cycle that runs for the
next 6 months.
It's happening! :)
** Changed in: snapd
Importance: Wishlist => High
** Changed in: snapd
Assignee: (unassigned) => Zygmunt Krynicki (zyga)
--
You received this bug notification because you are a
I understand the sentiment with ~/snap being a fixed location, shared by
both yourself and other people who have commented here.
The cost of making ~/snap arbitrary is very high but we have some ideas
that we are actively exploring as a part of the 20.10 cycle planning and
I suspect there will be
My main issue is that the snap folder is visible in the file manager and
on the command line by default. With .snap that would no longer be the
case. Workarounds for all file managers / file dialogs / file listing
commands are not always easy.
Is there any specific context in which it is
1 - 100 of 300 matches
Mail list logo
