Boo! I thought you'd found an interesting one! :-)
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/1784843
Title:
snap list: unexpected fault address 0xf1f0
To manage notifications
I wonder what happened to the traceback you clearly have in the
`systemctl status` you pasted in the description.
Anyway, is there anything special about this device?
Can you show us the output of `snap version`? what about `snap changes`?
--
You received this bug notification because you are a
Could you attach the output of 'journalctl -u snapd'? There's a
traceback in there, that's only partially visible in the 'status'
output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784843
Title:
*** This bug is a duplicate of bug 1662552 ***
https://bugs.launchpad.net/bugs/1662552
** This bug has been marked a duplicate of bug 1662552
snaps don't work with NFS home
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1782616 ***
https://bugs.launchpad.net/bugs/1782616
I think this is probably a dupe of lp:1782616; marking it as such.
** This bug has been marked a duplicate of bug 1782616
long delay (40 seconds) in boot due to snapd.seeded.service
--
You received
Could you attach the output of `journalctl -u snapd`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782602
Title:
On slow boots snapd falls into a initialization loop
To manage notifications
Em dashes cannot be part of a snap name.
They _could_ be part of an intentional 'snap set' command, something like
snap set mysnap foo=—o—
in which case, if the "snap set" fails, the user will get the above message,
followed by whatever error. Like so:
$ snap set bofh foo=—o—
Your command
For reference:
$ snap install ––help
Your command included some characters that look like dashes but are not:
"snap install \u2013\u2013help"
in some situations you might find that when copying from an online source such
as a blog you need to replace “typographic” dashes and quotes with their
I've added code to check for typographical dashes and warn the user:
https://github.com/snapcore/snapd/pull/5524
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782110
Title:
unhelpful error message
Yep! reproduced it:
$ snap install atom –classic
error: store.SnapNotFound with 2 snaps
that _is_ a terrible error.
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => John Lenton (chipaca)
** Changed in: snapd (
There's something very strange going on.
This is what I get:
$ snap install atom --classic
atom 1.28.2 from 'snapcrafters' installed
$ snap install atom --classic
snap "atom" is already installed, see 'snap help refresh'
$
the 'already installed' error is returned before even looking at the
Could you add the output of «journalctl -u snapd» to this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779948
Title:
Snapd gets stuck when starting Ubuntu.
To manage notifications about
Ok, so for this to be fixable I need go 1.7 which is not what we're
running (as it wasn't in 16.04).
Hmm.
** Bug watch added: github.com/golang/go/issues #13290
https://github.com/golang/go/issues/13290
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
For reference, the upstream bug and fix is
https://github.com/golang/go/issues/13290
Can you live with this for a while longer? (several months)
We'll be moving to 18.04's go at some point soon (in that timescale) and
then we can address this properly.
--
You received this bug notification
Hola!
it seems that user agent is only used for CONNECT. I'll dig into it.
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
** Changed in: snapd (Ubuntu)
Importance: Undecided => Medium
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => John Lenton (chipaca)
As a workaround, in seed.yaml, ensure content providers are before the
snaps that need them; the seeding step does not sort things.
It's unclear whether it should, but at least we should warn about it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Note that seed change is still ongoing (it's still got tasks in Doing
state). You can watch the progress with 'snap watch --last=seed'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772844
Title:
What are the contents of seed.yaml?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772844
Title:
snapd didn't initialize all the seeded snaps
To manage notifications about this bug go to:
OTOH what the client should be doing is looking at 'tracks' to get the
order of the channels, and then using that to look up each track in the
map; this would've avoided the issue (but not the info leak which is
still a bug)
--
You received this bug notification because you are a member of
FWIW there's a bug store-side, as it shouldn't be exposing branches at
all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768794
Title:
Snap branches all show with same name
To manage
The changes are garbage-collected after a certain time, or after a
certain number of changes, both of which are hard-coded.
If there's a bug it's in the hardcodedness of this :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Michal, have you done the things described in
https://forum.snapcraft.io/t/snaps-and-nfs-home/438 ?
On Mon, 14 May 2018 at 14:46, Michal Kukuča <1662...@bugs.launchpad.net>
wrote:
> With Ubuntu Bionic 18.04, snapd version 2.32, Snap still doesn’t work
> correctly with home folders mounted via
I am not a publisher for that snap, so I can't do that. I'll ask on
#snapd to see if anybody is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767896
Title:
Live 18.04 with broken seed causes
If you seed a snap, then you also need to seed that snap's base, and
snaps providing any plugs that snap requires, otherwise it'll fail to
seed.
A failure to seed it pretty bad, as snapd will be stuck in a loop trying
to do that. I don't think this is a bug in snapd, because if you have
network,
it looks like the seed is missing gtk-common-themes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767896
Title:
Live 18.04 with persistence snapd high CPU usage
To manage notifications about this
That's very interesting!
Could you paste the output of "snap tasks --last=seed" ?
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/1767896
Title:
Live 18.04 with persistence snapd high CPU
Marked as invalid for snapd (it's not a snapd bug)
** Changed in: snapd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746710
Title:
Snap creates
Yes, snapcraft.io tells you to use sudo, as not everywhere that can use
snaps has polkit. You're on Ubuntu, though, so polkit should just work.
In any case, sudo should also work :-)
Is there anything 'interesting' about your system, that would set it
apart from a standard default Ubuntu
igor, is this still the case? If so, can you give us the information
zyga asked for?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757284
Title:
Several snap apps fail to launch
To manage
> Does "no longer affects: snappy" mean that is has been fixed?
No, it means snappy is the wrong project for this bug
--
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
** No longer affects: snappy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746710
Title:
Snap creates redundant duplicate directories in home folder
To manage notifications about this bug go to:
** No longer affects: snappy
--
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
** Changed in: snapd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757284
Title:
Several snap apps fail to launch
To manage notifications about
Could you please give us the output of
snap version
snap info wavebox
also, could you please confirm that 'snap whoami' gives you the expected
email (and compare with 'sudo snap whoami').
thank you.
For the record, you should not need to log in to snapd to refresh the
wavebox snap (assuming
The 'every snap appears "broken"` is lp:1756793
The other one is really strange. How are you running the snaps?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757284
Title:
Several snap apps fail
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => John Lenton (chipaca)
** Package changed: snapd (Ubuntu) => snapd
** Changed in: snapd
Importance: Undecided => Medium
** Changed in: snapd
Status: New => In Progress
--
You received this bug notification
I removed the "snap" package bug task, as I doubt this bug affects the
gene finder.
** No longer affects: snap (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628289
Title:
snapd should
I expect that if /var or /var/lib are zfs datasets, and you created the
homologous .mount units, it would still work.
Is _that_ something you can test?
Either way, it would be good to have this documented over in the forum.
I'll see if I can't write something up this evening.
Thank you for all
ah! if that'd work, perfect.
If not, my question about the oneshot service was that, if that worked,
we could make all snap units have an After: on some agreed-upon name,
which would make this future-proof.
It might be a good idea independently; I'll discuss it with the team.
But please let me
How about: create a OneShot service that just polls to see if the zfs
mount is done, and have it be RequiredBy and Before the snap mount
units.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750059
Could you run «systemd-analyze plot > /tmp/startup.svg» and attach the
resulting /tmp/startup.svg?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750059
Title:
snaps are broken when /var/lib/snapd
Having snapd have an After= on the .mount unit that mounts
/var/lib/snapd should be enough? I think. I haven't tested this
(obviously).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750059
Title:
** Attachment added: "dmesg_4.12.0-13-generic.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342/+attachment/5058173/+files/dmesg_4.12.0-13-generic.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, I can confirm that with the 4.15.0-9 kernel with which the
touchscreen works, if I disconnect the keyboard dock I need to power
cycle (not just reboot) the machine to get it back.
Dmesg for disconnecting and reconnecting the dock for the 4.15.0-9 and
the old 4.12.0-13 (with which the
how is the mounting of /var/lib/snapd ordered in relation to starting of
snapd?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750059
Title:
snaps are broken when /var/lib/snapd is a mounted
Kai, I don't use the 7139 with a keyboard dock. I have a keyboard dock
on my 7140, and I can use it with my 7139 to test. I'll do that this
evening and report back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@redx dmesg from after re-plugging the keyboard a few times might help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745342
Title:
touchscreen that worked in artful with 4.12 no longer works with
The 7139 came back from suspend ~20 minutes later just fine.
** Attachment added: "/sys/firmware/acpi/tables/DSDT for 7139"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342/+attachment/5054510/+files/DSDT.7139.flimsy
--
You received this bug notification because you are a
** Attachment added: "/sys/firmware/acpi/tables/DSDT for 7140"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342/+attachment/5054509/+files/DSDT.7140.feuille
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[ +0.00] Linux version 4.15.0-9-generic (root@Ryzen) (gcc version
7.2.0 (Ubuntu 7.2.0-18ubuntu2)) #10~lp1745342+3 SMP Wed Feb 14 00:02:23
CST 2018
it worked!
I also suspended it, and it comes back fine from a short suspend; I'll
leave it for a while to see if it also comes back ok from a
I'll try that in a moment.
For what it's worth I've also got a 7140, running 16.04. That one's
running 4.13.0-32 just fine. If there's anything you want me to try on
it, just let me know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
https://people.canonical.com/~john/lp1745342/4.15.0-9.10~lp1745342+2/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745342
Title:
touchscreen that worked in artful with 4.12 no longer works with
With
Linux flimsy 4.15.0-9-generic #10~lp1745342+2 SMP Tue Feb 13 01:54:54
CST 2018 x86_64 x86_64 x86_64 GNU/Linux
the touchscreen didn't work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745342
I put the two configs on http://people.canonical.com/~john/lp1745342/
Including a diff at
http://people.canonical.com/~john/lp1745342/config-4.12.0-13_to_4.13.0-041300rc1.html
HTH,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342/+attachment/5053649/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745342
Title:
I just tried suspending with the 4.15 kernel, the touchscreen does not
work after resume either.
It does work after resume with the 4.12 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745342
** Attachment added: "udevadm_info"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342/+attachment/5053648/+files/udevadm_info
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745342
Nice hypothesis! Sadly, with
Linux flimsy 4.15.0-9-generic #10~lp1745342 SMP Mon Feb 12 16:02:41 CST 2018
x86_64 x86_64 x86_64 GNU/Linux
it didn't work, but there's chatter in dmesg about it: Attaching in case it's
useful.
** Attachment added: "dmesg"
Disappointing news I'm afraid: with the bottom half,
Linux flimsy 4.13.0-041300rc1-generic #201707151931LP1745342BottomHalfV1
SMP Fri Feb 9 21:01:09 UTC 20 x86_64 x86_64 x86_64 GNU/Linux
the touchscreen didn't work; with the top half,
Linux flimsy 4.13.0-041300rc1-generic
** Changed in: snapd (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748628
Title:
`snap`
** Changed in: snapd (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748630
Title:
`snap`
Note that, because snaps are self-contained, the answer to "list files
in installed snap" is simply to find /snap/ Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748627
Title:
`snap` should
** Changed in: snapd (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748627
Title:
`snap` should provide functionality to show files, which are included
flimsy:~$ uname -a
Linux flimsy 4.13.0-32-generic #35~lp1745342ConfigHAVEGENERICRCUGUP SMP Thu Feb
8 16:13:18 UTC x86_64 x86_64 x86_64 GNU/Linux
flimsy:~$
still nope.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello,
I tried with
$ uname -a
Linux flimsy 4.13.0-32-generic #35~lp1745342DESIGNWAREConfigsV2 SMP Wed Feb 7
20:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
and the bug is still there.
Sorry...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hello!
With
$ uname -a
Linux flimsy 4.13.0-32-generic #35~lp1745342ConfigDesignware SMP Tue Feb 6
20:11:39 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
still no luck.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello again! Sorry for the delay.
With
$ uname -a
Linux flimsy 4.14.0-16-generic #19-Ubuntu SMP Mon Jan 8 17:50:31 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
no dice.
Thank you,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
How do other polkit-using projects do the translation?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747272
Title:
Polkit dialogs of snapd are not translatable
To manage notifications about this
There seem to be two kernels there, so I tried them both: the
touchscreen didn't work with either of them.
$ uname -a
Linux flimsy 4.13.0-32-generic #35~lp1745342ConfigChange SMP Fri Feb 2 22:13:41
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
and
$ uname -a
Linux flimsy 4.13.0-32-generic
Here you go.
** Attachment added: "dmesg-working.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342/+attachment/5047589/+files/dmesg-working.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "lspci-working.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342/+attachment/5047588/+files/lspci-working.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Linux flimsy 4.12.0-13-generic #14-Ubuntu SMP Sat Sep 2 15:52:55 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
works;
Linux flimsy 4.13.0-10-generic #11-Ubuntu SMP Sun Sep 10 23:39:40 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
does not.
--
You received this bug notification because you are a member of
with the one from 4.12/zesty-remote,
~$ uname -a
Linux flimsy 4.12.0-041200-generic #201802011737 SMP Thu Feb 1 17:43:21 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
it works.
I get the impression this is not good news.
--
You received this bug notification because you are a member of Ubuntu
With the kernel in the 4.12 directory,
~$ uname -a
Linux flimsy 4.12.0-041200-generic #201802011529 SMP Thu Feb 1 15:34:08 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
the touchscreen did not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Happy February!
With
$ uname -a
Linux flimsy 4.12.0-041200rc2-generic #201802010156 SMP Thu Feb 1 01:58:04 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
it didn't work either.
Would it be possible to do a 4.12 final build in the same way you're
doing the bisect builds? I'm starting to worry it's
I just confirmed that
$ uname -a
Linux flimsy 4.12.0-041200-generic #201707022031 SMP Mon Jul 3 00:32:52 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
works, and that
$ uname -a
Linux flimsy 4.12.0-041200rc2-generic #201801312242 SMP Wed Jan 31 22:44:06 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
does
$ uname -a
Linux flimsy 4.12.0-041200rc2-generic #201801312121 SMP Wed Jan 31 21:23:03 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
did _not_ work...
also plymouthd crashed, but that might be unrelated :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
$ uname -a
Linux flimsy 4.12.0-041200rc5-generic #201801311949 SMP Wed Jan 31 19:50:53 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
did _not_ work.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
$ uname -a
Linux flimsy 4.12.0-041200rc5-generic #201801311805 SMP Wed Jan 31 18:06:52 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
did _not_ work.
What's the significance of the "rc5" in this last batch? I would've
thought these were prior to the known-good 4.12 final.
--
You received this bug
At some point somebody will figure out how to do newton-raphson instead
of bisect.
$ uname -a
Linux flimsy 4.12.0-041200rc5-generic #201801311623 SMP Wed Jan 31 16:25:11 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
did _not_ work.
Can't be much further now...
--
You received this bug notification
$ uname -a
Linux flimsy 4.12.0-041200rc5-generic #201801311413 SMP Wed Jan 31 14:14:46 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
did _not_ work.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
$ uname -a
Linux flimsy 4.12.0-041200-generic #201801302226 SMP Tue Jan 30 22:28:18 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
did _not_ work.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
$ uname -a
Linux flimsy 4.12.0-041200-generic #201801302050 SMP Tue Jan 30 21:06:17 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
did _not_ work.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
$ uname -a
Linux flimsy 4.12.0-041200-generic #201801261837 SMP Fri Jan 26 18:39:35 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
did _not_ work.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry for the delay :-) was at the doc's.
$ uname -a
Linux flimsy 4.12.0-041200-generic #201801261650 SMP Fri Jan 26 16:51:44 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
did _not_ work.
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
$ uname -a
Linux flimsy 4.12.0-041200-generic #201801261443 SMP Fri Jan 26 14:46:56 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
did _not_ work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745342
Linux flimsy 4.12.0-041200-generic #201707022031 SMP Mon Jul 3 00:32:52
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745342
Title:
touchscreen that
With
john@flimsy:~$ uname -a
Linux flimsy 4.13.0-041300rc1-generic #201707151931 SMP Sat Jul 15 23:32:39 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
the touchscreen does not work.
With
john@flimsy:~$ uname -a
Linux flimsy 4.12.14-041214-generic #201709200843 SMP Wed Sep 20 12:46:23 UTC
2017
$ uname -a
Linux flimsy 4.15.0-041500rc9-generic #201801212130 SMP Mon Jan 22 02:31:37 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I have a Dell Venue 11 Pro 7139, and when I installed artful on it
(before release) it worked fine. Recently (over the xmas break I think
but I'm not sure; this is not a machine I intended to pay too much
attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
Omiting architecture makes it default to amd64 afaik; you'd need to know
the list of architectures of the store you're querying, and loop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701232
Title:
I verified that 1:0.9.12.3+16.04.20171116-0ubuntu1 fixes the issue for
me in 16.04: before the upgrade, with the horizontal launcher and at a
high scaling factor the padding was wrong. After the upgrade, it was ok.
Thank you!
--
You received this bug notification because you are a member of
I can verify that after upgrading to 1:0.9.12.3+16.04.20171116-0ubuntu1,
that gsetting controls low graphics mode.
I had low graphics mode enabled before upgrading, using
~$ cat .config/upstart/lowgfx.conf
start on starting unity7
pre-start script
initctl set-env -g UNITY_LOW_GFX_MODE=1
end
Verified that 1:0.9.12.3+16.04.20171116-0ubuntu1 fixes the issue on
xenial: before upgrading, I confirmed xprop didn't disable the
decorations on an xterm window; after upgrading, it did.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I don't think systemd lets you express this, so it'd have to be logic
inside snapd itself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730159
Title:
Snapd should not start if there are no Snaps
Alfie,
thank you for the extra info. Could we also see
snap info stlouis-kernel
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724537
Title:
The revert features is not revert completed.
To
For what it's worth, "12to8" is a valid snap name, and a valid app name.
There was a bug in snapd (getting fixed right now).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636016
Title:
snapcraft
Oliver, the argument that ~/snap/ is “not just simply a
configuration dir” isn't particularly good, I think, as the same could
be said about the triple XDG directories for data, config and cache (all
of which default to be hidden).
It is the nature of the confinement that we build that these
*** This bug is a duplicate of bug 1581713 ***
https://bugs.launchpad.net/bugs/1581713
** This bug has been marked a duplicate of bug 1581713
Ubuntu Software always asks for an Ubuntu Single Sign-On account when
installing or removing a snap package
--
You received this bug notification
@Merlijn, I don't think there's a way for snapd to know the WMClass of
an app in a snap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718942
Title:
running favorited snap shows two icons in
201 - 300 of 976 matches
Mail list logo
