Attached kern.log
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+attachment/4944721/+files/kern.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
We have found this issue on 4.4.0-92 too.
But only when the systems were put under stress.
Reverting back to 4.4.0-57 resolved it.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+attachment/4944720/+files/dmesg.txt
--
You received this bug
Public bug reported:
When putting pressure on a Linux Node in Azure we see OOM killers
(similar to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842 but not
this is a different kernel)
dmesg and kernel.log attached
** Affects: linux (Ubuntu)
Importance: Undecided
** Description changed:
- When putting pressure on a Linux Node in Azure we see OOM killers
- (similar to:
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842 but not
- this is a different kernel)
+ When putting pressure on a Linux Node in Azure we see OOM killers (similar
to:
** Attachment added: "kernel.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734744/+attachment/5015324/+files/kernel.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I cannot run apport-collect 1734744 right now, so manually changed to confirmed.
Hopefully the attached logs will help
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I tested with kernel:4.4.105-0404105-generic and could not reproduced
** Tags added: kernel-fixed-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/1734744
Title:
OOM killer with
To test with the mainline kernel will take some time. I hope I will have
the results within a week from now.
--
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/1734744
Title:
OOM killer
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1734744/+attachment/5021580/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1734744/+attachment/5021575/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1734744/+attachment/5021577/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1734744/+attachment/5021578/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected uec-images
** Description changed:
When putting pressure on a Linux Node in Azure we see OOM killers (similar
to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842 but not this
is a different kernel)
Reverting the kernel to
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1734744/+attachment/5021574/+files/Lspci.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/1734744
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1734744/+attachment/5021579/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1734744/+attachment/5021581/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1734744/+attachment/5021576/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1734744/+attachment/5021573/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks for your suggestion; happy to try any solution suggestions.
When entering the command I get:
Set Low Energy for hci0 failed with status 0x0a (Busy)
Tried finding more information about this message but couldn't find anything
which seemed relevant.
Any suggestions?
(BTW: just to be
Just to -perhaps- add to any confusion: when I submit the command "sudo btmgmt
le off" in terminal, I expected the command to simply do its thing (switch off
le) and then return cli to the "waiting for input" status. Well, it doesn't:
when I submit the command and enter my password and press
See question https://answers.launchpad.net/ubuntu-gnome/+question/424983
also.
I also see the message "Not enough free handles to register service".
Lenovo Ideapad 110.
Linux LPTP001 4.4.0-57-generic #78-Ubuntu SMP Fri Dec 9 23:50:32 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
Dec 31 16:02:49
thx for this temporary fix, it works great!
--
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/1722478
Title:
Two-finger scrolling no longer works after resuming from suspend
Status in
the modprobe trick works (thank god), this helps a lot! I will see if i
can install the kernel that does work and see how this works with all
the rest of my laptop!
thanks for the info guys! I sure hope this is getting fixed soon though
:)
--
You received this bug notification because you are a
having the same issue with my t440p thinkpad after updating from 17.04
to 17.10...
can somebody please explain how i install the working kernel (4.11.12)
were Thorsten was talking about? Because this bug is really annoying as
this is my working laptop...
--
You received this bug notification
I'm testing Xubuntu 18.04 and have the same message in kern.log:
Mar 15 17:26:21 Xubuntu-18-04 kernel: [ 543.782137]
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO
underrun
I have experienced some "weird" screens.Please have a look here:
http://i.imgur.com/x2vCDj3.png
Hi Christopher
Thanks for you email.
I am not using 10.04 any more, so I can't test as described below.
Thank you for the good work.
Happy to be using Ubuntu.
op 23-12-13 14:56, Christopher M. Penalver schreef:
WIllem Hobers, this bug was reported a while ago and there hasn't been
any
Public bug reported:
After switching from OTA8.5 to rc-proposed (to test if my BT keyboard would
work with that) BT cannot be turned on any more.
I can flip the switch, but after 30s it is switched off again (probably never
turned on).
I am unable to discover any BT devices.
Running
After a reboot it seems to work.
awe_ mentioned there might be a race condition which he will test.
Now bluetoothctl gives uuids for audio sink etc.
OS build details:
build number: r331
image part: 20160105
build decription: Ubuntu 15.04 - armhf (20160105-020304)
--
You received this bug
Luckily, I still had my terminal with the flash process open.
I flashed it and it rebooted at 14:38:13.
So 14:41:46 is indeed after rebooting, the first time, after the switch to
rc-proposed.
A later manual shutdown and start of the device resolved the issue. It might
have been one of those
oubleshoot this.
- ---
+ ---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: willem 3714 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: willem 3714 F pulseaudio
CurrentDesk
** Attachment added: "screenshot2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574428/+attachment/4646000/+files/Screenshot%20from%202016-04-24%2022-50-46.png
** Description changed:
In a fresh Ubuntu 16.04 install, my Macbook does not properly report any
of the following in
Public bug reported:
In a fresh Ubuntu 16.04 install, my Macbook does not properly report any
of the following in the top bar:
1. Charge. It always says 90-91%.
2. Charging or not: when the power adapter is plugged in, it claims its not
plugged in, and the LED is green on the charger; while if
** Attachment added: "screenshot"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574428/+attachment/4645999/+files/Screenshot%20from%202016-04-24%2022-50-31.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
even though its only charged ~88%
I don't know where to start to troubleshoot this.
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: willem 3714 F pulseaudio
CurrentDesktop: Unity
DistroR
ly charged ~88%
I don't know where to start to troubleshoot this.
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: willem 3714 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
even though its only charged ~88%
I don't know where to start to troubleshoot this.
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: willem 3714 F pulseaudio
CurrentDesktop: Unity
DistroR
ugh its only charged ~88%
I don't know where to start to troubleshoot this.
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: willem 3714 F pulseaudio
CurrentDesktop: Unity
DistroR
even though its only charged ~88%
I don't know where to start to troubleshoot this.
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: willem 3714 F pulseaudio
CurrentDesktop: Unity
DistroR
ly charged ~88%
I don't know where to start to troubleshoot this.
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: willem 3714 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
while of being plugged it registers as plugged in, fully
charged, even though its only charged ~88%
I don't know where to start to troubleshoot this.
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/contro
e to start to troubleshoot this.
+ ---
+ ApportVersion: 2.20.1-0ubuntu2
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: willem 3714 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=66fe1cc0
its only charged ~88%
I don't know where to start to troubleshoot this.
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: willem 3714 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
its only charged ~88%
I don't know where to start to troubleshoot this.
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: willem 3714 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
even though its only charged ~88%
I don't know where to start to troubleshoot this.
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: willem 3714 F pulseaudio
CurrentDesktop: Unity
DistroR
ged, even though its only charged ~88%
I don't know where to start to troubleshoot this.
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: willem 3714 F pulseaudio
CurrentDesktop: Unity
DistroR
ugh its only charged ~88%
I don't know where to start to troubleshoot this.
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: willem 3714 F pulseaudio
CurrentDesktop: Unity
DistroR
ly charged ~88%
I don't know where to start to troubleshoot this.
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: willem 3714 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
even though its only charged ~88%
I don't know where to start to troubleshoot this.
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: willem 3714 F pulseaudio
CurrentDesktop: Unity
DistroR
Seeing this on Linux LAPTOP 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu
Aug 1 13:51:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux, running xubuntu
18.04.3.
description: Notebook
product: Aspire A315-53 ()
vendor: Acer
*-pci
description: Host bridge
I am seeing this as well.
running Linux willem-Aspire-A315-53 5.3.0-29-generic #31-Ubuntu SMP Fri
Jan 17 17:27:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Operating System: Kubuntu 19.10
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.12.4
Kernel Version: 5.3.0-29-generic
I am seeing this in my log as well,
Kubuntu 19.10
Linux willem-Aspire-A315-53 5.3.0-29-generic #31-Ubuntu SMP Fri Jan 17
17:27:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Operating System: Kubuntu 19.10
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.12.4
Kernel Version
I am running the same packages as in comment #9 (however, under 13.10
alpha 2) but to no avail.
ii bluez 4.101-0ubuntu8b1 amd64
ii pulseaudio 1:4.0-0ubuntu2+b amd64
Apparently, downgrading to 12.10 versions fixes the problem, as has been
reported here:
a little digging and plymouth is supposed to work with drm modesetting
drivers which means i915 has to be loaded for it to work .. so not
seeing it means ..some hardware detection has failed .. is that part of
plymouth or something else?
since it works on the upgraded install on sda1 I suspect a
Kernel module will load if added to /etc/ modules .. I have my sda1
partition running kernel 5.0.0-8.9 as are the iso's tested recently .. my
sda1 partition loads i915 without using /etc/modules.. I notice that the
recent isos do not show Plymouth progress screen at startup..is that
relevant?
so why the peculiar behaviour that lightdm works when the partition
installed native grub boots the system
BUT not when a grub installed by another partition is used then lightdm
consistently crashes and the machine locks up..
BUT if i915 is added to /etc/modules in the offending partition it
** Summary changed:
- lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870 - failure to load i915 kernel module
+ lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870 (using "foreign grub")
--
You received this
here we have a normal journalctl boot log .. notice the size .. more
entries .. about 1 minute start to finish source the partition that
always works lightdm starts normally plymouth appears on screen etc.
this one was booted by grub installed by zlink4 - on sda6 ..
** Attachment added: "zlink1
here is the journalctl boot log for sda6 /zlink4 booted by it's own
install of grub (self grub)
(it was reinstalled for this purpose .. to show it works .. however
plymouth does not show on the screen at all on boot but does on shutdown
)
now one change is addition of a vt.handoff=1 to the end
I've been merrily switching between OS's without this kind of issue for more
than 10 years ..
the behaviour changed recently in the last 30 days ..
it was fine prior to that ..
This is a regression bug and will annoy anyone working with multiple instances
of disco xubuntu for testing..
yes
just some summary thoughts in addition to point to some anomalies ..
the "failures in lightdm appear to correspond with shorter journal logs ..
so certain processes are not running as expected ..
plymouth also does not appear on the screen ..
as it needs the proper graphics support ..
--
okay generated the default grub.cfg via sda6 grub-install boot instance
.. vt.handle=1 is set by default for self root boot about a minute to
boot
no change .. still no plymouth on boot but there is a flicker with
lightdm .. which restarts once video mode switch has happened ..
note all grub
whoops added the wrong attachment above it is the one including the
grub-update dialog .. instead of being the bot after the command
** Attachment added: "this one is after the grub-update .. accidental switch"
Yep, same issue here on Ubuntu 18.10, 4.18.0-16-lowlatency kernel.
If relevant:
CPU: AMD A10-5800K
GPU: AMD GeForce GTX 660
RAM: 8GB DDR3
DE/WM: GNOME 3.30.2 + GNOME Shell
Mouse: Logitech G502
System is close to unusable.
--
You received this bug notification because you are a member of Kernel
Public bug reported:
I am trying to remove the lowlatency kernel as this is causing issues,
but it is not clear how to do this.
There is no guide to be found and my system is unusable right now.
Related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787743
ProblemType: Package
For others running into this:
- Hold RIGHT shift during boot (left shift didn't work)
- In GRUB menu go to advanced > generic kernel (not lowlatency)
- Remove all -lowlatency packages
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
okay apr 8 and apr 9 iso's have same issues kept logs of various boots
into the fresh installs .. no change in grub-source during testing was
made .. all with fresh installs
typical first boot is normal .. no crash of xorg on first start ..
second boot shows lightdm briefly then xorg crashes
testing xubuntu-disco-daily.iso apr 06, 2019 First boot fine plymouth,
and xorg/lightdm started normally.. did a number of updates and
rebooted.
second boot plymouth not seen, xorg/lightdm appeared briefly .. then
vanished .. then reappears ..
checked xorg.0.log(s) ..
xorg.0.log .. seemed ok
third boot of same install ..
** Attachment added: "third reboot of fresh install xorg.0.log.old --
slighjtly different"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/5253548/+files/Xorg.0.log.old
--
You received this bug notification because you are a
An additional data point for reference .. did a netboot install of
xubuntu using "daily" amd64 netboot mini.iso .. base install followed
by taskselect install of xubuntu ..
boots normally plymouth and lightdm screens appear as expected .. also
switching to foreign grub .. it still boots
okay I stumbled across something .. the network install .. used netplan
to set-up my wifi connection to start on boot .. so as soon as systemd
networkd starts wifi is started NetworkManager thus has no access or
anyway to try for other networks.. so I tried to change this.. If I edit
the config
bug is still present in disco xubuntu iso "final" 04-13.1-2019
--
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/1821609
Title:
lightdm login screen briefly appears and then blanks out on
I will try to do videos for you tomorrow it is getting late in the day
here ..
a brief synopsis for now ..
history: this is standard grub arrangement as "installed by default"
used to work flawlessly with multiple partitions of various linux OS's
.. It is only since early march that I noticed an
video of sda9 boot using sda9 install of grub (native grub) .. note absence of
plymouth .. flash at top edge of screen was missed .. note brief appearance of
lightdm .. short gap then lightdm reappears .. xorg.0.log.old records the
crash .. similar to others above
xorg.0.log records
okay turned back the clock .. to a spinning metal disk previously
installed in this hardware .. ran a number of test installs all work
fine .. cosmic/bionic/disco early version disco final all work boot
normally .. always ..
thus conclusion is a SSD is very fast and can respond to requests sooner
video of sda8 non-native grub boot (a disco-xubuntu iso install) sda9
has installed grub (also a disco-xubuntu iso install ) will show in
next video uploaded
note the red flash .. plymouth attempt to start .. then cursor appears
and then lightdm briefly
** Attachment added: "video of failing
of course the sda1 partition (on the SSD) has never failed to work properly no
matter which grub source (installs on sda1,sda6,sda7,sda8,sda9) is used
plymouth always appears when sda1 boots..
this disco version was installed jan 10 with a bootstrap log date of oct 13,
2018 .. it has been
** Summary changed:
- lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870
+ lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870 (boot timing issues implicated)
--
You received this bug notification because you
okay I have another solution to the timing issue .. add two partition
mounts to fstab ..
my existing sda1 disco install has /home (sda2) and /home/store1 (sda5)
mounted via fstab .. this was the original install configuration .. thus
always a mount delay ..
to test .. added the same partions
Fine tuning: only one extra mount is necessary .. then plymouth
finishes very quickly .. and xorg/lightdm start normally!
--
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/1821609
Title:
okay a previous "fresh install that was crashing plymouth
screen/lightdm/xorg was fixed by copying a known working set of netplan
conf files into /etc/netplan ..
the 01-netcfg.yaml from the "network install" uses networkd as the
renderer .. with a working network device config.. plus the
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2038539/+attachment/5709949/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2038539/+attachment/5709948/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
oh I just saw that apport-collect is used for that.. sorry for the noise
--
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/2038539
Title:
bluetooth connections are unstable with
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2038539/+attachment/5709945/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2038539/+attachment/5709946/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2038539/+attachment/5709944/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/2038539/+attachment/5709947/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I wanted to make sure I had all the info needed pulled in .. it is the
same issue .. is there a way to use ubuntu-bug to add info to an
existing bug?
have I missed any logs you need for analysis?
--
You received this bug notification because you are a member of Kernel
Packages, which is
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2038539/+attachment/5709941/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2038539/+attachment/5709940/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2038539/+attachment/5709939/+files/Lsusb.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/2038539
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2038539/+attachment/5709950/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2038539/+attachment/5709937/+files/Lspci.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/2038539
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2038539/+attachment/5709938/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/2038539/+attachment/5709942/+files/PaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2038539/+attachment/5709943/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Okay the above represents apport-collection fron a linux-
image-6.5.0-9-generic kernel instance .. after bluetooth headphone
connection and at least two connection and disconnect insidents.. two
firefox browser start and stops at least
any thing else needed..?
--
You received this bug
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2038539/+attachment/5709936/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
Seems some random network activity regularly breaks bluetooth connections..
headphones connect and reconnect or suffer breaks in sound etc.
Started with this kernel version linux-image-6.5.0-7 .. previous kernel
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2038539/+attachment/5709935/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 126 matches
Mail list logo
