okay installed kernel 6.8.0-7 from noble-proposed and bluetooth issue is gone
with this version.. no drops
so this appears fixed
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notif
All on the same hardware .. just different install paritions..
a manjaro install with kernel 6.6.7 has no bluetooth issues even though
the latest Ubuntu 6.6.0-14-generic kernel still has bluetooth dropouts
.. up to date nobel install .. same install parition running
6.5.0-5-generic kernel no blu
no change with kernel 6.6.0-14
--
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 linux-image-6.5.0-6-generic
and above (MANTIC)
Sta
upgrade to kernel 6.6.0-13 slightly lessens the problem but does not
eliminate the drop outs again starting browsing seems to trigger drop
out to begin.. scheduler issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
the apparmor lines above are also present using the 6.5.0-5 kernel which
does NOT have glitches .. so that's a red herring ..
--
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:
tried tail -f /var/log/syslog -f /var/log/kern.log ..
nothing syncronizes with the sound glitchers although a regular event is
==> /var/log/syslog <==
2023-11-15T13:17:48.973884-05:00 zlite1c kernel: [ 938.056939] audit:
type=1400 audit(1700072268.965:142): apparmor="DENIED" operation="open"
c
just did another fresh noble xubuntu daily install .. 11/14/2023
bluetooth sound is jittery .. even without a browser
started..vmlinux-6.5.0-9-generic .. is on the install media..
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
comment #41 was with the 6.5.0-12 kernel version .. switching to the
older 6.5.0-5 kernel there are no issues (same software/hardware/just a
reboot to a different kernel)
.. so a definite kernel internal interaction appears indicated between
regular network and bluetooth network .. regular networ
note: disconnecting from the network stops dropouts considerably to a
much more tolerable level.
I tried using flight mode but that kills bluetooth as well and turning
it on again resulted in a struggle to reconnect the headphones. ..
as a side note .. latest audio updates had just been installed
FYI a test install of fedora 39beta upgraded to latest
vmlinuz-6.5.9-300.fc39.x86_64 kernel has no bluetooth audio issues .. on
the same hardware .. different partions only..
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
intermittent behaviour still present in 6.5.0-10 .. just installed .. but
disconnects are less frequent.
audio drop-outs are frequent.. tracks play normally with linux-image-6.5.0-5 ..
manually marked .. to prevent removal..
--
You received this bug notification because you are a member of Ker
** Summary changed:
- bluetooth connections are unstable with linux-image-6.5.0-7-generic (MANTIC)
+ bluetooth connections are unstable with linux-image-6.5.0-6-generic and above
(MANTIC)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
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 notificati
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.
https://bugs.launchpad.net/bugs/20
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.
https://bugs.launchpad.net/bug
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.
https://bugs.launchpad.net/bugs/2038539
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.
https://bugs.launchpad.net/bugs/2038539
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.
https://bugs.launchpad.net/b
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.
https://bugs.launchpad
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.
https://bugs.l
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.
https://bugs.launchpad.net/b
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.
https://bugs.launchpad.net/bugs/2038539
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.
https://bugs.launchpad.net/bugs/2038
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.
https://bugs.launchpad.net/bugs/2038
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: "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.
https://bugs.launchpad.net/bugs/20
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.
https://bugs.launchpad.net/bugs/20
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.
https://bugs.launchpad.net
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
li
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 linux-image
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 subscrib
added bug report with ubuntu-bug with data from 6.5.0-9 kernel version
bug#2039358
--
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
okay .. it does not matter which snap or binary forefire browser or even
thunderbird network activity for all 6.5.0-6 and greater kernels cause dropouts
bluetooth audio noise and disconnect/reconnect behaviour..
kernels less than or equal to 6.5.0-5 do not exhibit this behaviour..
sometimes eve
I've been trying out new installs with bluetooth for the release
candidate of xubuntu 23.10 and the latest linux-image-generic-6.5.0-9
.. the initial clean install with no browser used .. gave good bluetooth
performance .. but while playing music through my bluetooth headphone I
started firefox(sn
boot.log.1
--
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 linux-image-6.5.0-7-generic
(MANTIC)
Status in linux package in Ubuntu
boot.log
--
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 linux-image-6.5.0-7-generic
(MANTIC)
Status in linux package in Ubuntu:
auth.log
** Attachment added: "auth.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038539/+attachment/5707345/+files/auth.log
--
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
kern.log.1 yesterday
** Attachment added: "kern.log.1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038539/+attachment/5707337/+files/kern.log.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
kern.log today
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038539/+attachment/5707336/+files/kern.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
next oldest
** Attachment added: "syslog.1-yesterday"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038539/+attachment/5707335/+files/syslog.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
logs from "bad kernel"
** Attachment added: "syslog-most recent"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038539/+attachment/5707334/+files/syslog
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
FYI the linux-image-6.5.0-6-genric version also has the bluetooth random
disconnect/reconnect issue..
(using kubuntu or xubuntu instances .. all on the same physical hardware .. all
Mantic
** Summary changed:
- bluetooth connections are unstable with linux-image-6.5.0-7-generic
+ bluetooth con
this is for the development version .. Mantic daily iso xubuntu
10-05-2023
--
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 linux-im
did a whole fresh install to verify this .. initial kernel installed was
6.5.0-5 everything worked as expected .. upon upgrade to 6.5.0-7 the
bluetooth connections became unstable ..
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
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
linux-image-6.5.0-5 works perfectly
Booting into the older ke
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:
** 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 ar
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 to
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 updat
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 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 successful
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 bo
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
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
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 01-netw
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 fi
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 normall
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 whil
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 memb
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 .
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 ..
--
You
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 it
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 in
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"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/525
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 o
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 /
** 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 bug
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 all
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 c
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?
On
71 matches
Mail list logo
