Public bug reported:
Using the relatively new Raspberry Pi 5B/16GB model, my SD card doesn't
work without a quirk passed kernel command line. Without the quirk the
logs are full of:
Jan 24 14:32:30 pi5-2 kernel: mmc_cqe_recovery: 3 callbacks suppressed
Jan 24 14:32:30 pi5-2 kernel: mmc0: running
Public bug reported:
Running Ubuntu 24.10 (Oracular) with Nvidia 560 driver, manually
switched to X11 mode on login, shows errors in some applications using
the opengl API. Notably this is visible in:
desktop-security-center snap:
zyga@novigrad:~/Canonical/snapd$ desktop-security-center
Gtk-Mes
** Also affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/18
I'm marking the snapd task as invalid as it's really not something that
snapd interacts with. Most likely kernel configuration OR core20 snap.
If it happens that this is related to kernel modules and their layout in
the system please reopen the snapd task.
** Changed in: snapd
Status: New =
The bug is in progress but it is unclear who is working on it. Can the
party responsible please self-assign and update the status of the issue.
Is there something to be done in the snappy project for this issue to be fixed?
Is this just waiting on a kernel snaps? Are those in stable channel now?
This has been fixed and is available in snapd for multiple releases now.
I'm marking it as fix released.
** Changed in: snappy
Status: In Progress => Fix Released
** Project changed: snappy => snapd
--
You received this bug notification because you are a member of Kernel
Packages, which
** Changed in: snappy
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1627643
Title:
oops on pi3 (seemingly wlan related)
Status in Snappy:
Invalid
This has been fixed now. Marking it as such.
** Project changed: snappy => snapd
** Changed in: snapd
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
I'm marking this as invalid in snappy as it doesn't seem related to
snapd proper.
** Changed in: snappy
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/b
This issue happened to me on a new machine that I never used with Ubuntu
before. I don't know if tis is a regression.
--
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/1755270
Title:
Linux
I've been testing the patch from jj and I cannot see the issue after 24
hours of intense apparmor activity. +1 from me.
--
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/1755563
Title:
dang
** Description changed:
On my artful system running 4.13.0-36-generic I noticed that there are
dangling symlinks for "raw_data", "raw_sha1" and "raw_abi" files in the
sysfs path containing loaded apparmor profiles.
Sample of profiles that had dangling symlinks:
/sys/kernel/securit
** Description changed:
On my artful system running 4.13.0-36-generic I noticed that there are
dangling symlinks for "raw_data", "raw_sha1" and "raw_abi" files in the
sysfs path containing loaded apparmor profiles.
Sample of profiles that had dangling symlinks:
/sys/kernel/securit
Public bug reported:
On my artful system running 4.13.0-36-generic I noticed that there are
dangling symlinks for "raw_data", "raw_sha1" and "raw_abi" files in the
sysfs path containing loaded apparmor profiles.
Sample of profiles that had dangling symlinks:
/sys/kernel/security/apparmor/policy/
Public bug reported:
I was using my iPhone network sharing over USB-C cable to my ThinkPad
T470 while on the road. Using 4.15.0-10-generic available in Bionic I am
experiencing regular crashes that bring my machine down.
After hard power cycle I can find things like this in my last log:
mar 12 1
Hey Tyler, thank you for the update, this looks very promising indeed.
I'd like to ask about two aspects:
- detection, how can we detect that this feature is available? Shall
we just compile a program and see if it loads on snapd startup?
- golang, we use golang bindings to libseccomp and we will
This also happens on Fedora 25 running 4.10.8-200.fc25.x64_64
--
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 fai
> Wiadomość napisana przez Ying-Chun Liu w dniu
> 13.03.2017, o godz. 11:02:
>
> I think I'm making wrong assumption? It seems to me that refresh gadget snaps
> won't upgrade the files in the system.
That is correct. This is not yet supported by snapd.
> Upgrading kernel snap does change the
Hey Seth.
To reply to your earlier question:
@zyga: I'm honestly very surprised that the config change had that
drastic an impact on the single-CPU system. Can you tell me what 'cat
/sys/devices/system/cpu/possible' says on that system?
This was in a virtual machine with one CPU and the file lis
After using the CONFING_SQUASHFS_DECOMP_SINGLE=y option in an
experimental kernel the memory usage dropped significantly. The traces
below are for -45 and the experimental -46 kernel. The 1 and 4 are the
number of CPUs on the system.
A single CPU system used to consumer 131MB per mounted snap, thi
Public bug reported:
This is a tracking bug for what might be kernel bugs or kernel
configuration changes.
As described [1], memory used by simply mounting a squashfs file (even
an empty one) is ranging from almost nothing (on certain distributions)
to 131MB on Ubuntu 16.04 and 16.10 on a single-
Per agreement with jdstrand it is sufficient to verify that the new
policy is a superset (that is, it allows to do more, not less) of the
old policy. This prevents the possibility of regressions. Given that the
original bug was reported on a non-common hardware/kernel combination
this serves as a s
Yann could you please verify that this bug is fixed by the package in
xenial-proposed?
You can find more information about the process at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
** Description changed:
+ [Impact]
- - Finding issues running snaps (hello-world).
+ snap-confine would refuse to work on an older kernel running on an
+ Nvidia Tegra X1 board. This was traced to a bug in older version of
+ apparmor there that required directory-like syntax for /dev/pts/ptmx
+
** Changed in: snap-confine
Status: Fix Committed => Fix Released
--
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/1584456
Title:
apparmor denial using ptmx char device
Status in S
** Changed in: snap-confine
Milestone: None => 1.0.40
** Changed in: snap-confine
Status: In Progress => Fix Committed
--
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/1584456
Ti
Public bug reported:
My Thinkpad x200t has rebooted instead of resumed from hibernation. I'm
using Ubuntu Wily daily.
ProblemType: KernelOops
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-10-generic 4.2.0-10.12 [modified:
boot/vmlinuz-4.2.0-10-generic]
ProcVersionSignature: Ubuntu 4.2.0
Hey, a small update. Lantern test v2 tests exactly what happens when
brightness is set to 0. I have 10 samples so far and I will be able to
analyze them today. My gut feeling is that acpi aka firmware control
never tuns the backlight off entirely (so setting zero in userspace is
safe) while raw con
Hey.
I'm researching the behaviour of backlight in the wild and my current
theory is that brightness of zero can equally well mean "dim" or
"totally off". I don't have a test for that yet so the sample range is
very small (the hardware I have at home + several contributions from the
community) but
** Changed in: kernel-sru-workflow/certification-testing
Status: In Progress => Fix Released
** Tags added: certification-testing-passed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Changed in: kernel-sru-workflow/certification-testing
Status: In Progress => Fix Released
** Tags added: certification-testing-passed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Changed in: kernel-sru-workflow/certification-testing
Status: In Progress => Fix Released
** Tags added: certification-testing-passed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/certification-testing
Assignee: Canonical Hardware Certification (canonical-hw-cert) => Zygmunt
Krynicki (zkrynicki)
--
You received this bug notifi
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
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/1176953
Title:
linux: 3.8.0-20.31 -proposed tr
Looks good based on http://people.canonical.com/~hwcert/sru-
testing/precise/3.2.0-69.103/precise-proposed.html
** Changed in: kernel-sru-workflow/certification-testing
Status: In Progress => Fix Released
** Tags added: certification-testing-passed
--
You received this bug notification
** Changed in: kernel-sru-workflow/certification-testing
Status: In Progress => Fix Released
--
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/1364092
Title:
linux: 2.6.32-66.132 -pr
** Changed in: kernel-sru-workflow/certification-testing
Assignee: Canonical Hardware Certification (canonical-hw-cert) => Zygmunt
Krynicki (zkrynicki)
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
--
You received this bug notifi
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/certification-testing
Assignee: Canonical Hardware Certification (canonical-hw-cert) => Zygmunt
Krynicki (zkrynicki)
--
You received this bug notifi
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/certification-testing
Assignee: Canonical Hardware Certification (canonical-hw-cert) => Zygmunt
Krynicki (zkrynicki)
--
You received this bug notifi
Thanks for the tip! I'll update my bios and re-test according to
instructions.
On Sat, Aug 30, 2014 at 10:54 AM, Christopher M. Penalver
wrote:
> Zygmunt Krynicki, as per
> https://downloadcenter.intel.com/SearchResult.aspx?lang=&ProductID=3444&ProdId=3444
> an update to
I'm sorry for the lag. We had some issues with fwts that were traced
back to using the wrong version. +1 from the cert team
** Changed in: kernel-sru-workflow/certification-testing
Status: In Progress => Fix Released
** Tags added: certification-testing-passed
--
You received this bug no
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Fix Released
** Tags added: certification-testing-passed
--
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
** Changed in: kernel-sru-workflow/certification-testing
Status: In Progress => Fix Released
** Tags added: certification-testing-passed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Changed in: kernel-sru-workflow/certification-testing
Status: Invalid => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Assignee: Canonical Hardware Certification (canonical-hw-cert) => Zygmunt
Krynicki (zkrynicki)
--
You received this bug notifi
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
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/1357394
Title:
linux: 2.6.32-65.131 -proposed
** Changed in: kernel-sru-workflow/certification-testing
Assignee: (unassigned) => Zygmunt Krynicki (zkrynicki)
--
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/1357148
Title:
li
I've tested 3.17.0-031700rc1-generic #201408161335 -- the particular
xhci endpoint message goes away but 'adb shell' dies instantly when
using 3.0 ports. When I unplug my device I see this error message in
syslog:
Aug 20 00:24:06 silverblade kernel: [ 129.264680] usb 3-3.3: usbfs:
USBDEVFS_CONTRO
** Changed in: kernel-sru-workflow/certification-testing
Assignee: Canonical Hardware Certification (canonical-hw-cert) => Zygmunt
Krynicki (zkrynicki)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
Public bug reported:
On Utopic 3.16.0-9-generic x86_64 kernel:
I'm using the Intel DQ77KB desktop board [1]. Apart from the board and
some disks and memory the computer has no other hardware. The board has
four usb 3.0 ports on the back. Using any of those ports, with my USB
3.0 hub, with my phon
** Changed in: kernel-sru-workflow/certification-testing
Assignee: Canonical Hardware Certification (canonical-hw-cert) => Zygmunt
Krynicki (zkrynicki)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
Public bug reported:
not sure what's going on.
on resume my wired bonded networking was busted (I had to reboot to get
it back)
ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-8-generic 3.13.0-8.27
ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
Uname: Lin
Hey. I seem to experience this bug as well. It definitely feels like a
race condition somewhere. I have to reboot my machine 2-5 times each
morning to finally get it to boot. I don't have any issues mounting
stuff after bootup is done, it certainly feels like a bug around
upstart/mountall to me. Th
52 matches
Mail list logo
