+1! Thanks!
** Tags removed: review
--
landscape-sysinfo - full squashfs filesystems considered events
https://bugs.launchpad.net/bugs/303284
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
Same problem here. Fresh Jaunty images built with ubuntu-vm-builder
moments ago are hanging over after "Starting up ...". Hardy images work
fine.
--
Certain VMs do not run under KVM using 2.6.30-rc5 kernel
https://bugs.launchpad.net/bugs/379991
You received this bug notification because you are
Hello Martin,
> in http://bugs.debian.org/416204 and
> https://bugs.launchpad.net/bugs/271680 we requested that the
> python-dateutil package in Debian and Ubuntu should use the system
> tzdata files instead of the shipped obsolete copy. This will keep a
> single reference of the pretty volatile t
Thanks for the review Thomas!
[1] is fixed with a test, even though it's assertion is disabled because
the issue is not yet totally fixed. The branch deb-ordering-fix (which
is pretty much ready too) will uncomment the assertion and fix the issue
completely.
[2] Fixed!
[3] I won't address these
That's been committed in Smart's trunk.
--
Small smart fixes need to go in the Intrepid package
https://bugs.launchpad.net/bugs/279343
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
Public bug reported:
The dbus infrastructure is useful even in server environments, with command line
applications. Right now there's a chain of dependencies which cascade into
x11-common:
dbus -> consolekit -> libx11-6 -> x11-common
This means that to get dbus installed, x11-common must be
Martin pointed out that in Intrepid the dependency between libx11 and
x11-common doesn't exist anymore, so this will probably solve the issue for
future releases.
I'm not yet sure if there is interest in solving that problem for past
releases as well.
--
dbus shouldn't depend on x11-common
https
FWIW, a friend just told me he's being affected by this same bug.
--
MemStick problem with card_reader (tifm)
https://bugs.launchpad.net/bugs/222557
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
** Description changed:
Binary package hint: landscape-client
Following the format at
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
STATEMENT EXPLAINING THE IMPACT: The new Landscape feature Custom Graphs
doesn't work on the client yet. Existing customers using landscape-
This is the only purpose of the SRU exception, as far as Landscape is
concerned. Not upgrading it means that
users of released distributions will never get any new features, for the whole
life time of the given distribution. The problem is aggravated when
considering that the users *will* see
** Changed in: landscape-client
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: landscape
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
logrotate script needs to redirect stderr too
https://bugs.launchpad.net/bugs/271767
You received this bug notificat
Why has this been marked as Invalid? We've just upgraded a Jaunty
machine to Karmic and had exactly the same problem. If this is a file
which has to be removed, the upgrade should do something about it.
** Changed in: ifupdown (Ubuntu)
Status: Invalid => New
--
ifdown: failed to open st
We don't have this file by the way, and the problem still happens.
The directory /var/run/network doesn't exist, and that's the reason why
the networking init.d script is failing. Something is removing the
directory during reboot, since even if the directory is created by hand,
it's gone on the n
One more case with hermes/orinoco_cs.
--
WEP Connection cannot be made
https://launchpad.net/bugs/48473
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I'm getting the same problem.
I've checked out matplotlib, and in setup.py it tests for existence of
pytz and dateutil in the system, and won't install them unless the user
doesn't have them already. So I suspect that using python-tz as a build
dependency and runtime dependency might fix the issue
Same problem. IBM/Lenovo T60, Fan doesn't go up and CPU burns up to
shutdown.
--
CPU overheats during high usage "throttling "
https://bugs.launchpad.net/bugs/22336
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing
Same problem. IBM/Lenovo T60. Fan doesn't increase its speed and CPU burns
until shutdown.
--
[feisty] cpu heats a lot and laptop turn off
https://bugs.launchpad.net/bugs/104069
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Public bug reported:
Binary package hint: libcurl3-gnutls
The curl version currently present in Dapper (0.15.1) has a bug which
corrupts POSTs when sent to SSL servers.
The bug and the respective fix is described at:
http://sourceforge.net/tracker/index.php?func=detail&aid=1480821&group_id=976&
** Attachment added: "Source package with fix included."
http://launchpadlibrarian.net/9236186/fixed-package.tar.bz2
--
Curl corrupts large POSTs to SSL servers
https://bugs.launchpad.net/bugs/137849
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Attachment added: "Reproducer script."
http://launchpadlibrarian.net/9236190/curl-send-bug.py
--
Curl corrupts large POSTs to SSL servers
https://bugs.launchpad.net/bugs/137849
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Ok, I see the problem. The installed "curl" binary is linked against
OpenSSL instead of GnuTLS.
I'm attaching another script, which uses pycurl to perform the same
logic.
Can you please try it out?
** Attachment added: "PyCurl-based reproducer."
http://launchpadlibrarian.net/9248585/curl-send
Also notice that due to the bug nature, it may not *always* fail.
--
Curl corrupts large POSTs to SSL servers
https://bugs.launchpad.net/bugs/137849
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubunt
Yes, we've run the test script in our own environment with the
proposed package and confirmed that it works.
--
Curl corrupts large POSTs to SSL servers
https://bugs.launchpad.net/bugs/137849
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Public bug reported:
Binary package hint: python-mysqldb
Ubuntu has inherited a patch from Debian in Python's MySQLdb package which
is quite harmful to any application which needs transactional behavior.
Here is a comment in Storm which explains the problem:
# Here is another sad story
Please don't apply this patch.
First, the description is incorrect. It doesn't offer a "reconnect" parameter.
It
turns on reconnection by default.
Second, the patch should actually be *removed* from any versions that currently
have it applied. Check bug #163184 for more information.
--
Requ
Public bug reported:
A Karmic server image in EC2 just got stuck in the following message
during boot:
* Waiting for EC2 meta-data service
Rebooting it didn't help. The machine successfully rebooted, but then
was holding in the same position again.
Some details:
AMI: ami-1515f67c
Zone: us
** Attachment added: "ec2-console-output.txt"
http://launchpadlibrarian.net/36824066/ec2-console-output.txt
--
Karmic image stuck in "Waiting for EC2"
https://bugs.launchpad.net/bugs/497036
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Public bug reported:
Binary package hint: ec2-init
Amazon's EC2 and Eucalyptus do not offer a way for the user to know if
the image he's using is out of date or not. With a simple mechanism
which queries an API server at Canonical, and a hook inside the image
itself, we'd be able to tell users a
work.
The estimated availability time for the proxy code is on September 14th.
** Affects: eucalyptus (Ubuntu)
Importance: Undecided
Assignee: Gustavo Niemeyer (niemeyer)
Status: In Progress
** Changed in: eucalyptus (Ubuntu)
Status: New => In Progress
** Changed
Can you suggest a different mechanism that would work both in Eucalyptus
and in Amazon, and that would allow people running customized images to
be notified as well? Or are you saying that notifying people about new
images being available isn't valuable?
Note that this isn't much different from t
Right, agreed.
What I find particularly interesting in this case is the concern that
Canonical might be having some benefit in accessing *anonymous* data
about upgrade inquires in a public API. This really puzzles me, because
EC2 is a proprietary system from Amazon, and Amazon is able to tell
*ex
> Gustavo: Note that the current enhancement proposal goes beyond just
> EC2, but appears to also apply to Ubuntu images users run with
> Eucalyptus on their own hardware at their own company.
Eric, your point about the "Ubuntu philosophy" was specific to EC2.
About working on Eucalytpus, yes, we
Public bug reported:
Eucalyptus is hanging during an euca-upload-bundle and the command euca-
upload-bundle doesn't return.
The ps output:
112 8313 0.0 0.3 51496 12340 pts/0S<+ 15:16 0:00 python
/usr/bin/euca-upload-bundle --manifest
/tmp/tmpmObI_X/fe0859214e955a11d57d20665543bac
Public bug reported:
Eucalyptus was returning a 403 error during an image registration even when
everything was apparently correct.
The commands executed were:
euca-bundle-image --user 000100729354 --image
/tmp/image-store-proxy/download/http%3A%2F%2Flocalhost%3A52781%2Fimages%2Fkernel
--des
It does. It should just display a message saying that the proxy is not
available.
That said, considering it has so few dependencies by itself, it'd be
good to have the Eucalyptus package depending on the Image Store Proxy
package, so that people will benefit from the service without having to
fig
Public bug reported:
The Image Store Proxy which landed last week through the Feature Freeze
Exception in bug #423865 needs to be updated to version 1.0 so that it
fully works. The 0.9.1 version which landed in alpha 5 still missed
some features like signature checking.
** Affects: eucalyptus (U
FWIW, I have the same issue with a Radeon Mobility X1400.
--
fglrx module not loaded, Cannot allocate memory
https://bugs.launchpad.net/bugs/480668
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
I had the same issue as well with Ubuntu 10.04. None of the renaming
tricks worked.
I finally worked around the problem by changing the access point from
WEP to WPA TKIP.
--
Wireless network card stopped working with ubuntu 9.10
https://bugs.launchpad.net/bugs/498336
You received this bug notif
And that too:
$ sudo lxc-execute -n foo /bin/echo hello
hello
--
Linux containers not working on EC2
https://bugs.launchpad.net/bugs/471615
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
Public bug reported:
Binary package hint: euca2ools
The euca2ools command line tools should generate a non-zero status code
when receiving bad arguments in the command line:
nieme...@cumulus:~$ euca-register --non-existent
option --non-existent not recognized
Registers a manifest for use with t
Public bug reported:
I had to reinstall Eucalyptus from the ground up several times already.
After some time with little to no activity (besides running euca-
describe-images and logging in the admin interface), it refuses new
actions through the interface with:
$ euca-describe-images
Warning: f
Oops.. sorry for missing the package.
Btw, this was with 1.6~bzr645-0ubuntu2.
--
Eucalyptus cloud controller stops working suddenly
https://bugs.launchpad.net/bugs/428010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
Potentially some times, but signals seems to be working fine now, and it
happened to me today again.
--
Eucalyptus cloud controller stops working suddenly
https://bugs.launchpad.net/bugs/428010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I'm attaching my cloud-ouput.log file. grep -i "corrupt" there doesn't
find anything, but there are several other errors.
** Attachment added: "cloud-output.log"
http://launchpadlibrarian.net/31664702/cloud-output.log
--
Eucalyptus cloud controller stops working suddenly
https://bugs.launchp
Public bug reported:
Eucalyptus is returning a 500 error when trying to register a ramdisk
image:
Command 'euca-register' returned status code 1:
Warning: failed to parse error message from AWS: :1:0: syntax error
BotoServerError: 500 Internal Server Error
Failure: 500 Internal Server Error
Take
The source code for 1.0.2 is available at:
http://launchpad.net/image-store-proxy/1.0/1.0.2/+download/image-store-
proxy-1.0.2.tar.gz
--
[FFE] Image Store Proxy must handle compressed images
https://bugs.launchpad.net/bugs/445714
You received this bug notification because you are a member of Ubu
Public bug reported:
Up to version 1.0.1, the image store proxy cannot handle compressed
images, which means Canonical would have to provide 10GB files
uncompressed somewhere, rather than the much smaller 700MB versions.
Version 1.0.2 is able to handle gzip compressed images.
It's important to in
The relevant code change between 1.0.1 and 1.0.2 is attached. The rest
of the diff is documentation and tests.
** Changed in: ubuntu
Assignee: (unassigned) => Mathias Gug (mathiaz)
** Attachment added: "1.0.1-1.0.2.diff"
http://launchpadlibrarian.net/33246004/1.0.1-1.0.2.diff
--
[FFE]
No, this is not a security issue. localPath is based on the sha256,
which is checked right above for validity.
--
[FFE] Image Store Proxy must handle compressed images
https://bugs.launchpad.net/bugs/445714
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Oh, again, this was all unittested, and manually tested using the fake
store api.
--
[FFE] Image Store Proxy must handle compressed images
https://bugs.launchpad.net/bugs/445714
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
Scott Moser pointed out that he wants to use .tar.gz on the published
images, because using the --sparse option of tar greatly reduces the
size of the resulting file in comparison to plain gzip, so I went ahead
and added support for .tar.gz on the image store proxy too, in addition
to .gz.
This is
Martin,
Please rest assured I understand very well all of the consequences of
using one approach or the other, and opt to use one or the other
depending on specific needs. In fact, if you look through the code
you'll see that in some cases subprocess was used.
In the case at hand I could very we
> Just because I trust my data to Amazon does not mean that I'm comfortable
> sharing my data with the rest of the world. That's the "trust" part.
This is a pretty misleading statement.
The mechanism does not send *your data* anywhere, and the query is a
read-only query made against an API in Can
> Something like this:
>
> http://people.canonical.com/~soren/ec2-version-query/current/
That's really not much different in terms of privacy than what is being
suggested in this bug. The image will have to look at a URI like this
for knowing if it's out of date or not:
http://people.canoni
*** This bug is a duplicate of bug 436885 ***
https://bugs.launchpad.net/bugs/436885
>From the description of bug #436885, this doesn't feel like a duplicate
at least, since the deadlock condition wasn't following any significant
usage. But then, the other bug is quite short on details, so i
Public bug reported:
Registering a walrus on localhost fails with an internal error message:
$ sudo euca_conf --register-walrus localhost
Adding WALRUS host localhost
Internal Error.
ERROR: failed to register Walrus, please log in to the admin interface and
check cloud status.
This was done wit
** Attachment added: "eucalyptus-logs.tar.bz2"
http://launchpadlibrarian.net/32747582/eucalyptus-logs.tar.bz2
--
Internal error registering local walrus
https://bugs.launchpad.net/bugs/439364
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I'm attaching an Eucalyptus patch which implements the following
changes:
- New services tab, with links to Canonical services
- New Landscape registration option in the services tab
- Moved Rightscale registration option to right after the Landscape one (was
under Credentials).
- Fixed the size
Woonjas, if you're having an issue, it's probably not this one as the
problem was found and fixed.
Can you please open a separate bug, and include the same details
requested above for your machine, so we can investigate in more detail?
Thank you.
--
You received this bug notification because yo
Hi Eric,
Thanks for the call yesterday.
Similar to other cases we covered yesterday, and unlike stated above,
the translation of the alias in "snap get system" to "snap get core" is
actually made inside the daemon, so there shouldn't be any difference in
results, whether via the command line or v
Snapshots, which is mostly finished by now, will allow keeping data past
the removal of the snap itself. That said, it will only hold the data
saved for some time. The design applied there is a trade off between
leaving data behind forever, and risking removing data unintendedly as
you reported.
S
The picture might not be completely clear if you haven't been watching,
so let me help:
- We have snaps by default in Ubuntu for years now
- There are thousands of snaps published
- There are more than 100 thousand snap installs per day
- There are more than 3 million new snap installs a month
- T
> This is by design so not easy to fix if at all possible at this stage
It is by design, but as I said the solution not only is possible, but is
elegant, and is almost done.
The foundations of snapshots is done and is landing
(https://github.com/snapcore/snapd/pull/5955). In the coming weeks,
we'
The issue is most probably that your headset implements the HFP profile,
but not the HSP profile, and pulseaudio does not yet support the HFP
profile despite what that line says (HSP/HFP). To confirm, run
bluetoothctl, and type something like:
> devices
(...)
> info 11:22:33:44:55:66
Where the ad
We listen, even to harsh comments like that one.
I'm sorry that we cannot implement the exact changes you want on the
exact time frames you want. Rest assured we are working hard on this
project, though, and for years now we've been landing major improments
like clock work. There are actually some
That's not the only concern, Zygmunt. We also need to design what we'll
move towards when it actually happens. As was detailed much earlier in
this thread, there are considerations about both the kind of content
that is inside those directories (which isn't something that typically
goes hidden), an
> I believe this is a very incorrect line of argumentation. Your
position is "others have done it too". This is not an excuse. Also they
have done it differently.
This whole thread is about consistency and common practices, Ivàn.
Consistency and common practices for the placement of a single
direc
> having a directory not hidden with a fixed name in the home directory
is not a common practice.
The vast majority of Ubuntu users in the desktop have directories named
similar to "Video", "Pictures", "Documents", "Downloads", "Music", etc
there, which means that in fact this is a common practice
> The dev team made it clear that for them it has no priority and from
their point of view it is no bug and does not belong here.
I actually stated something else way back above. We care, and we'll fix
it. It's not as straightforward as it sounds, though, and indeed there
were higher priorities. I
The fix for one snap or ten thousand is exactly the same, as we're
addressing this inside snapd proper. No snaps will need to change.
--
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:
Ple
Public bug reported:
This morning I experienced an interaction which left me a bit concerned.
I took a sleeping laptop to the office, opened it, and the usual login
dialog came up. I then plugged in an external monitor, and it unlocked.
Anybody experienced something similar recently?
Looking th
There's no time in most lines in that file unfortunately, but this might
be it:
WARN 2016-06-28 20:36:08 nux.inputmethod.ibus InputMethodIBus.cpp:67
Impossible to connect to connect to ibus
[2378:2411:0629/100015:ERROR:connection_factory_impl.cc(367)] Failed to connect
to MCS endpoint with erro
Here it goes:
ii unity 7.4.0+16.04.20160526.1-0 amd64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597390
Title:
Screen unlocked on external monitor plugged?
To manage notifications about this
It's way too late for that behavior right now. Many features expect
snapd to be live to work. Seeding happens the first time snapd runs,
which means a new system will by default start without any snaps
installed. The data for command-not-found is acquired by snapd while
running as well. We also can
This is the second hottest bug because it's very easy to have an opinion
about it without any strings attached.
As I believe was explained multiple times above the real reason this is
not "hidden" is that snap/ is not just a configuration directory. This
is where the writable space for all snaps l
No worries, Joel Teixeira, we'll still be here if you need us, working
on developing modern package management for Linux, and hopefully making
it good enough that people will be excited to use despite the name of a
directory not being their preferred one.
In fact, we can definitely work allowing a
There are two recent issues in 18.04 that we're aware about. For one of
them, the most trivial fix is to reboot the system. It's a problem in
systemd ignoring a Condition on the snap.mount being inside a container
and stopping the snap.mount unit, which chains into unmounting all snaps
during the p
Hi Colin,
We discussed in the sprint two weeks ago how we could prevent this from
happening again. Part of the problem here is that this only shows up in
a multi-stage upgrade, because it's a misbehavior of systemd that was
triggered on the prerm script.
So normal upgrade tests do not catch it. W
*** This bug is a duplicate of bug 1756793 ***
https://bugs.launchpad.net/bugs/1756793
Sorry for the trouble, James. A reboot is the most trivial workaround,
and the fix is being released.
We got bitten by a misbehavior in systemd, which got hidden due to lack
of testing for double updates (u
The snap infrastructure is used in production by us and many of our
customers, and we also regularly hear about success stories from the
community. So in that sense, yes it's production quality, today.
That said, Ubuntu will not replace all debs by snaps. These are
complementary technologies, and
Hi Carl,
This is likely what we will do indeed, as it's a nice partner to the
other standard options already there, is language-agnostic, and thus
easier to handle on the confinement sense. We'll also clean it up a bit
on the way, by stashing the non-current revisions in a better place.
--
You r
Viktoria,
We have been working non-stop on snapd over those three years, including
features that will improve the situation for this folder. The fact it is
marked as Wishlist reflects more on the fact nothing is in fact broken,
other than you and me would both like to have a nicer folder structure
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
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.
--
> 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.
h
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
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
> 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
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
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.
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 th
Chris, I've just read your blog post at:
https://shenaniganslabs.io/2019/02/13/Dirty-Sock.html
There you install a snap in devmode, which does a bunch of things to
demonstrate that the snap can access system resources via the
vulnerability in <2.37. Just for the record, it's slightly undue to
cla
Thanks for the clarification, Chris. We're in complete agreement.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813365
Title:
Local privilege escalation via snapd socket
To manage notifications ab
There's some further discussion about the topic of this PR here:
https://forum.snapcraft.io/t/access-to-specific-hidden-file-path-in-
users-home/6948/8
Josh, we're are researching about a way to solve problems similar to the
ones you describe. It's still not ready for prime time, but I believe we
For the record, the epoch feature is being actively worked on and it's
not that far hopefully.
You can track progress in the forum:
https://forum.snapcraft.io/t/epochs-stepped-upgrades/1757/57
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is supposed to work indeed, even outside of Ubuntu Core.
It's also documented:
https://snapdocs.labix.org/configuration-options/87
(this will go into snapcraft.io/docs soon)
I'm going to close this issue for now. Please reopen if I'm missing
something.
** Changed in: snapd (Ubuntu)
Sergio, see comment from Seb above. It's the launcher, and rebuilding
apparently solves the problem. We won't pack the launcher in snapd.
If you have some more information about why that's still a bug in snapd,
then please talk to us or provide good details about why the affected
applications abov
It's not even just that. Part of the confusion here is that people think
this is content that should be hidden, but it's really not. This is
closer to "~/Documents" than it is to "~/.config". The directories under
~/snap hold the $HOME for snaps. They are the place strict snaps can
write to, unless
Hi Tony,
Stepping up on a culture pedestal and looking down on others is pretty
unhealthy, even more if you do that blindly.
As was repeated many times in this thread, the files inside ~/snap must
*not* be hidden. Those are going to be music files, documents, pictures,
which strict snaps want to
Hi Krisztian,
There's no test here. Those are just user
data files which need to be exposed, whether you're young or not. That
said, your general sense is right: we want those exposed, and nicely so.
You're also hitting the right points when you raise symlink and
confinement issues. That's part o
1 - 100 of 220 matches
Mail list logo
