apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1233061/+attachment/3851838/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1233061/+attachment/3851837/+files/ProcEnviron.txt
--
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
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1233061/+attachment/3851843/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
I have executed the command as requested. Below is the output that was
displayed.
I have also changed the status of the bug to "confirmed" as instructed
in your email.
study@Eastford-Study:~$ apport-collect 1233061
The authorization page:
(https://launchpad.net/+authorize-token?oauth_token=SP
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1233061/+attachment/3851832/+files/BootDmesg.txt
--
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/
Carried out your request regarding the installation of the upstream
kernel and here are the results:-
study@Eastford-Study:~/Downloads/3.8.13$ ls
linux-headers-3.8.13-03081310_3.8.13-03081310.201309251435_all.deb
linux-headers-3.8.13-03081310-generic_3.8.13-03081310.201309251435_amd64.deb
linux-i
** 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.
https://bugs.launchpad.net/bugs/1233061
Title:
HDMI not working after update to linux image 3.8.0.31.46
Status in “linux” packag
Public bug reported:
System failed to resume; restarted system and this debug box came up
with this information.
ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-11-generic 3.11.0-11.17
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-
Public bug reported:
powering down an adapter times out, and powering it back up again
doesn't seem to work at all.
Demonstration with bluez-test-adapter after a cold boot:
---
charles@sita:~$ bluez-test-adapter powered
1
charles@sita:~$ bluez-test-adapter powered off
Traceback (most r
sorry, turns out the fresh install just shut off the screen when I
closed the lid, the suspend still doesn'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/bugs/1453299
Title:
Scree
4.2.0
Uname: Linux 4.2.0-10-generic i686
ApportVersion: 2.18.1-0ubuntu1
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: charles 948 F lxpanel
Date: Sat Sep 19 09:29:56 2015
DuplicateSignature: package:linux-image-4.2.0-10-generic:4.2.0-10.11:subpr
i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: charles 948 F lxpanel
Date: Sat Sep 19 09:29:56 2015
DuplicateSignature:
package:linux-image-4.2.0-10-generic:4.2.0-10.11:subprocess new
pre-installation script returned error exit status 1
ErrorMe
I have this issue on 14.04.3 as detailed here:
http://askubuntu.com/questions/685549/selecting-a2dp-changes-nothing-
whats-a-working-conf-file/685597
I have not tried updating to any version other than the current official
version for 14.04.3
--
You received this bug notification because you are
Public bug reported:
System: Dell XPS 13 9343
Action: Boot computer
Expected Behavior: Keyboard backlight would be off when computer is
booted
Actual Behavior: Keyboard backlight is on at boot
This did not happen with Ubuntu 15.04
There are new files in Ubuntu 15.10 -
/sys/class/leds/dell::kb
is system.
I'm running 15.04, also seen it in 14.10 and 14.04 on the same box.
I can actually hear the drive resetting from time to time so I know
there's something actually happening.
Charles
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-31-generic 3.19.0-3
** Changed in: linux (Ubuntu)
Status: Expired => Incomplete
--
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/1451246
Title:
Intel 7265 Wifi instability workaround
Status in linux p
We are also seeing this. We're now stuck on old kernels until this is
fixed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2050098
Title:
cgroup2 broken since 5.15.0-90-generic?
I'm concerned with the security implications of being frozen on a kernel
we can't update. I suspect we should start testing an HWE kernel. That
raises other issues, since there are lots of other features we also need
to work, so it's going to require a fair amount of testing. I'd
accelerate our mov
In src/plugins/cgroup/v2/ebpf.c, comment out logging. I.e. change
attr.log_level = 1;
attr.log_buf = (size_t) log;
attr.log_size = sizeof(log);
to
attr.log_level =
>From timing I suspect kernel.org
2dcb31e65d26a29a6842500e904907180e80a091, but I don't understand the
code so I can't tell whether there's actually a problem there.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
h
However the same patch is in 6.5. I give up. At least I have a
workaround.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2050098
Title:
cgroup2 broken since 5.15.0-90-generic?
S
Furthermore, slurm doesn't actually use the log data that the kernel
would pass back. So my code is better even with kernels that work. Why
pass a log buffer that you aren't going to use?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
For what it's worth, we've been running a file server for several weeks
with the 2.1.14 .ko files in 22.04 with no problem. I didn't try to
cherry pick the one fix as I'd prefer to have the whole 2.1.14.
--
You received this bug notification because you are a member of Kernel
Packages, which is s
Public bug reported:
1) Ubuntu 22.04.4 LTS
2) 470.256.02-0ubuntu0.22.04.1
3) After monitor sleeps and wakes, windows have same positions and sizes as
when monitor went to sleep
4) After monitor sleeps and wakes, windows have different positions and sizes
Since installing version 470.256.02-0ubun
This issue is different. It's another problem with block copy. But
that's known to still be an issue. It's why block copy is disabled in
2.2.1. This is only an issue for the Jammy HWE, which has 2.2.0. No one
should be shipping 2.2.0 with anything. It should be replaced with 2.2.1
at least.
--
Yo
Actually, it may not be an issue even for Jammy HWE. My copy shows block
cloning as an option that's off.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044657
Title:
Multiple data
it's likely to take a while. It's been committed but not released. They
chose to cherry pick the patch, so the version will still show as 2.1.5.
A lot of us would prefer going to 2.1.14, but there are enough other
changes that Ubuntu staff didn't want to do it. I'm considering building
my own zfs m
Since I was just referenced, note that I wouldn't favor putting 2.2 into
Jammy. I would, however, prefer to see the latest 2.1.x.
2.2 is still seeing a substantial number of bug fixes. It will probably
be ok by the release date of 24.04, but I still wouldn't change major
versions for Jammy.
--
Y
Jeff,
The patches are queued up to be submitted to 5.18
https://git.infradead.org/git/nvme.git/log/refs/tags/nvme-5.18-2022-03-03
--
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/1948626
Tit
Public bug reported:
I just upgraded an NFS server from 20.04 to 22.04. Because of problems
in my setup, it didn't come up cleanly. As part of recovery I did
"systemctl restart nfs-server." I did this after two reboots. In both
cases shortly thereafter I got one or more backtraces in syslog
Aug 1
uas.ko hangs, fails, spams dmesg on all 5 HP AMD A10 systems tested, on
all AMD USB3 ports if writing to any device that has UAS.
If booting a livecd on a UAS capable device, UAS cannot be unloaded.
UAS will stall any writes to the temp log partition ubuntu creates on the boot
device.
--
You r
I've also seen this. I wondered if the problem is that the libraries and
utilities haven't been updated. I doubt that it's intended for a version
0.8.3 ZFS send and receive to run on a ZFS 2.0.2. kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is s
I've got the same issue on a system76 gazelle - I just reinstalled 20.04
hoping that this would fix the issue, but the 5.8.0-38 kernel does not
complete the boot cycle by itself.
I have found that switching to tty2 and then back to tty1 causes the
boot to complete
--
You received this bug notifi
+f(num)
On 1/20/21 12:18 PM, Ben Hoyt wrote:
> Charles, very interesting. Though I wonder if yours is a different
> problem, partly because it's not in tty mode at all (for me it's in a
> graphical mode, sometimes with the Dell logo up). I can't seem to switch
> to tty2
dules-extra-5.4.0-58-generic 5.4.0-58.64
> ii linux-modules-extra-5.8.0-36-generic 5.8.0-36.40~20.04.1
> ii linux-modules-extra-5.8.0-38-generic 5.8.0-38.43~20.04.1
>
> I tried as Charles Green said: Switching to tty2 and then back to tty1 causes
> the boot to comple
Because it is not production ready,
We use the livecd uninstalled.
Please make an exception for the kernel packages,
Please just put the kinetic kernels on the lunar livecds,
(And for all new)
So we dont have to roll our own livecd just to smoke test a new version,
So we dont get the avalanche
Note that there are serious bugs with ZFS encryption. Most involve send
| receive, but not all. I strongly recommend against using it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/199
Public bug reported:
i have no idea really. new to linux.
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: nvidia-dkms-550 550.107.02-0ubuntu0.24.04.1
Uname: Linux 6.10.4-061004-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Thu Oct 2
Public bug reported:
Errors were encountered while processing:
zfs-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: zfs-dkms 2.2.2-0ubuntu9.1
ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12
Uname: Linux 6.8.0-47-generi
I'm also seeing this bug
--
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/1913350
Title:
Intel Wireless-AC 7260 (rev bb) wifi card crashes randomly
Status in Linux:
Confirmed
Status in
Public bug reported:
The payload in the xenial package kernel-signed-image-4.4.0-145-generic-
di_4.4.0-145.171_amd64.udeb doesn't have the proper suffix and
overwrites the unsigned version of the same kernel image:
(from data.tar.xz from the package):
./
./boot/
./boot/vmlinuz-4.4.0-145-generic
I see that this is a result of LP #1764794, I've adjusted my copy
debian-installer source package to compensate (using bionic version as a
template).
This however, should be fixed for xenial if there is going to be another
point release.
** Summary changed:
- xenial 4.4.0-145 image udeb overwrit
thanks for the feedback
On Thu, Sep 26, 2019, 09:55 daniel primo stuart <1609...@bugs.launchpad.net>
wrote:
> Kernel needs this patch for maxim98090 to work on cyan and some baytrail
> chromebooks:
>
> https://github.com/torvalds/linux/commit/d5e120422db8808e1c8b1507900ca393a877c58f
>
> As it did
Public bug reported:
Not sure what happened
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-80-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.1-0ubun
What should I do?
- Original Message -
From: "Joseph Salisbury"
To: coyl...@comcast.net
Sent: Monday, June 19, 2017 6:30:12 PM
Subject: [Bug 1698966] Status changed to Confirmed
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You receive
Still seeing this in 4.4.0 kernels on Ubuntu 16.04.
$ dmesg | grep -i blk
[5.660121] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS
+ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN)
[ 60.473635] b
linux-image-3.9.0-030900rc2-generic_3.9.0-030900rc2.201401071104_i386
has the bug.
--
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/1251816
Title:
Boot failure with saucy kernel 3.11 probi
This kernel boots.
$ uname -a
Linux kepler 3.9.0-030900rc2-generic #201401081132 SMP Wed Jan 8 16:47:32 UTC
2014 i686 i686 i686 GNU/Linux
--
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/12
linux-image-3.9.0-030900rc2-generic_3.9.0-030900rc2.201401091651_i386
has the bug.
--
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/1251816
Title:
Boot failure with saucy kernel 3.11 probi
This kernel boots.
Thank you!
$ uname -a
Linux kepler 3.13.0-3-generic #18~lp1251816v1 SMP Tue Jan 14 22:20:13 UTC 2014
i686 i686 i686 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
linux-
image-3.13.0-031300rc8-generic_3.13.0-031300rc8.201401120535_i386.deb
has the bug.
--
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/1251816
Title:
Boot failure with saucy kernel 3.1
This kernel boots and I didn't notice any other issues!
$ uname -a
Linux kepler 3.13.0-5-generic #20~lp1251816UpstreamRevert SMP Tue Jan 21
21:39:58 UTC 2014 i686 i686 i686 GNU/Linux
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
root@kepler:~# uname -a
Linux kepler 3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:13:28 UTC 2014 i686
i686 i686 GNU/Linux
The saucy-proposed kernel fixes the issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
Public bug reported:
I get error message that bcmwl-kernel-source is not installed properly
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-31.55-generic 3.13.11.4
Uname: Linux 3.13.0-31-generic x86_64
N
Just found this same abovementioned /.rpmdb directory on my install. It
wasn't there before and hasn't ever been there before this morning. I
did not do anything involving a kernel. Although vmware player uses
dkms when a new kernel is installed, no new kernel was installed today.
When will 4.11.
The 3.9 kernels work and the 3.10 kernels fail to boot.
In addition to the above kernels you listed, I tried the last 3.9 and
the first 3.10 based on the directory date listings at
http://kernel.ubuntu.com/~kernel-ppa/mainline/.
Boots OK:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9.11-sauc
The test kernel fails.
--
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/1251816
Title:
Boot failure with saucy kernel 3.11 probing eisa
Status in “linux” package in Ubuntu:
Confirmed
B
The kernel has the bug.
--
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/1251816
Title:
Boot failure with saucy kernel 3.11 probing eisa
Status in “linux” package in Ubuntu:
Confirmed
The kernel has the bug.
--
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/1251816
Title:
Boot failure with saucy kernel 3.11 probing eisa
Status in “linux” package in Ubuntu:
Confirmed
I hope you had a good holiday!
This kernel boots.
$ uname -a
Linux kepler 3.9.0-030900rc2-generic #201312201136 SMP Fri Dec 20 16:58:03 UTC
2013 i686 i686 i686 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
This kernel boots!
Thanks!
--
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/1251816
Title:
Boot failure with saucy kernel 3.11 probing eisa
Status in “linux” package in Ubuntu:
Confirm
This one has the bug.
--
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/1251816
Title:
Boot failure with saucy kernel 3.11 probing eisa
Status in “linux” package in Ubuntu:
Confirmed
Bu
This kernel has the bug.
--
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/1251816
Title:
Boot failure with saucy kernel 3.11 probing eisa
Status in “linux” package in Ubuntu:
Confirmed
cp@kepler:~$ uname -a
Linux kepler 3.9.0-030900-generic #201312121455 SMP Thu Dec 12 20:03:59 UTC
2013 i686 i686 i686 GNU/Linux
This one boots OK!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
3.9.0-030900rc2.201312131341_i386 has the bug.
--
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/1251816
Title:
Boot failure with saucy kernel 3.11 probing eisa
Status in “linux” package i
linux-image-3.9.0-030900rc2-generic_3.9.0-030900rc2.201312161520_i386
has the bug.
--
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/1251816
Title:
Boot failure with saucy kernel 3.11 probi
linux-image-3.9.0-030900rc2-generic_3.9.0-030900rc2.201312181333_i386
has the bug.
--
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/1251816
Title:
Boot failure with saucy kernel 3.11 probi
Public bug reported:
I have an old laptop that I upgraded to saucy and it will only boot the earlier
3.8 kernel. The 3.11, 3 versions tried including the proposed, hangs on
"Platform eisa.0: Probing EISA bus 0"
I also tried the 3.12.0-999 kernel at
http://kernel.ubuntu.com/~kernel-ppa/mainl
Public bug reported:
After a moment my system slow down, don't want to burn cpu or gpu :-(
Thanks
jc@jc-Portable:~$ sudo thermald --no-daemon --loglevel=debug
[1705190368][DEBUG]RAPL sysfs present
[1705190368][DEBUG]RAPL base path /sys/class/powercap/intel-rapl/
[1705190368][DEBUG]RAPL domain
Maybe this could be useful too, thanks a lot, by the way I did try to
reintall and purge the service, same problem:
jan 14 00:35:27 jc-Portable systemd[1]: Starting thermald.service - Thermal
Daemon Service...
jan 14 00:35:27 jc-Portable systemd[1]: Started thermald.service - Thermal
Daemon Serv
Maybe not accurate
** Attachment added: "Capture d’écran du 2024-01-14 01-13-39.png"
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2049285/+attachment/5739103/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202024-01-14%2001-13-39.png
--
You received this bug notification because you ar
** Bug watch added: Linux Kernel Bug Tracker #217165
https://bugzilla.kernel.org/show_bug.cgi?id=217165
--
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/2003053
Title:
NFS: client permi
solved the bug already i cleared some things and made an update
On Sun, Sep 26, 2021, 05:40 ian <1609...@bugs.launchpad.net> wrote:
> Any update on this? Having issues with sound working for some time,
> than suddenly stopping with a buzzing sound. Will attempt to modify
> patch for most recent
Public bug reported:
whiles installing nvidia dkms 535
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: nvidia-dkms-535 535.183.01-0ubuntu0.24.04.1
ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12
Uname: Linux 6.8.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
App
101 - 174 of 174 matches
Mail list logo
