Public bug reported:
On a system running a 5.2 kernel, doing a large number of mounts of
squashfs filesystems in parallel results in the mounts getting out of
sync with their backing devices.
To reproduce,
https://paste.ubuntu.com/p/VCpzGxvy6h/
this breaks people with ~40 snaps (easily achievab
I haven't yet tried to reproduce this with an upstream kernel, but given
that it's affecting arch users with 5.2 as well, it's fairly likely to
be there.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
The mainline builds for i386 and amd64 are failing right now so not sure
I can do more.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1836914
Title:
Doing multiple squashfs (and other l
** Patch added:
"0001-loop-Fix-mount-2-failure-due-to-race-with-LOOP_SET_F.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836914/+attachment/5280018/+files/0001-loop-Fix-mount-2-failure-due-to-race-with-LOOP_SET_F.patch
--
You received this bug notification because you are a me
Can somebody build and test a kernel with Jan's patch, from
https://lore.kernel.org/linux-block/20190730133607.gd28...@quack2.suse.cz/
?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/18369
the tests now check for the existence of the package before installing
it.
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
** Changed in: snapd (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: snapd
Status: Incomplete => Fix Released
** Changed in: linux-o
With the kernel from #16 I am no longer able to reproduce the issue, not
with the simplified reproducers described in this bug, nor with the
original (slower and more convoluted) snapd reproducer.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1672819
Title:
exec'ing a setuid binary from a threaded progr
$ 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
$ 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
$ 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
$ 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
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 #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 not
$ 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
$ 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 Kernel
Packages, which is 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
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 some
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 Kernel
Packages, which is subscribe
The linux-headers deb seems to be truncated in that one.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745342
Title:
touchscreen that worked in artful with 4.12 no longer works with 4.
Ah, ok then, I'll give it a try.
(there haven't been linux-image-extra debs in all this)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745342
Title:
touchscreen that worked in artful
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 Kernel
Packa
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
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
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 #35~lp17453
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 Kernel
Packages, which is subscribed to linux in Ub
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
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 Kernel
Packages, which is subsc
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
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 #201707151931LP1745342T
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"
https://bugs.launchpad.net/ubuntu/+sour
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745342
Title:
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 Kernel
Packages, which is subscribed to linux in
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
https://people.canonical.com/~john/lp1745342/4.15.0-9.10~lp1745342+2/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745342
Title:
touchscreen that worked in artful with 4.12 no longer
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 Kernel
Packages, which is subscribed to li
[ +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 lon
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
h
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 member
@redx dmesg from after re-plugging the keyboard a few times might help?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745342
Title:
touchscreen that worked in artful with 4.12 no longe
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
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 touchscr
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
ha
$ 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
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 x86_6
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745342
Title:
touc
$ 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
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 Kernel
Packages, which is subscribed
Public bug reported:
This can be reproduced with
https://gist.github.com/chipaca/806c90d96c437444f27f45a83d00a813
With that, and go 1.8, if you run “make” and then
for i in `seq 99`; do ./a_go; done
you'll see a variable number of ”GOT 1000” (or whatever your user id
is). If you don't, add one
I also tried this in 4.10.0-11-generic, same results.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1672819
Title:
exec'ing a setuid binary from a threaded program sometimes fails to
Might this be related to https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=857909 ?
** Bug watch added: Debian Bug tracker #857909
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857909
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
55 matches
Mail list logo
