I'm also affected by this issue. Makes experimenting with settings very
tedious.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1746419
Title:
bond parameters are not chan
The nuget restore command works again on my Ubuntu 20.10 OS, thanks for
the fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1913951
Title:
ca-certificates: Sy
You can find every details about the Nuget incident here:
https://github.com/NuGet/Announcements/issues/49#issue-795386700
** Bug watch added: github.com/NuGet/Announcements/issues #49
https://github.com/NuGet/Announcements/issues/49
--
You received this bug notification because you are a mem
thanks, this seems to make it work
now the only strange thing seems to be that the volume control doesn't
work, but I guess that's a different issue / topic
so: why did this not work out of the box?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
on a second try pairing, this is what I get:
# pair 70:26:05:87:EC:01
Attempting to pair with 70:26:05:87:EC:01
[CHG] Device 70:26:05:87:EC:01 Connected: yes
[NEW] Primary Service
/org/bluez/hci0/dev_70_26_05_87_EC_01/service0001
1801--1000-8000-00805f9b34fb
Generi
doing the pairing from bluetoothctl gets the same result:
# pair 70:26:05:87:EC:01
Attempting to pair with 70:26:05:87:EC:01
[CHG] Device 70:26:05:87:EC:01 Connected: yes
[CHG] Device 70:26:05:87:EC:01 Name: WH-1000XM2
[CHG] Device 70:26:05:87:EC:01 Alias: WH-1000XM2
[CHG] Device 70:26:05:87:EC:01
interestingly, bluez was not yet installed. after installing, I see:
$ bluetoothctl
[NEW] Controller 9C:B6:D0:FE:37:CA dell-xps15 [default]
Agent registered
[bluetooth]# list
Controller 9C:B6:D0:FE:37:CA dell-xps15 [default]
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# scan on
Di
output after a clean boot:
$ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
$ rfkill unblock 1
$ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bl
$ rfkill unblock 3
$ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
but the result is the same. I open the settings panel, go to the Bluetooth tab,
try to turn it on, the switch shows 'ON',
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1782893/+attachment/5166573/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1782893/+attachment/5166585/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.laun
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1782893/+attachment/5166584/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1782893/+attachment/5166583/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1782893/+attachment/5166580/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://b
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1782893/+attachment/5166579/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.la
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1782893/+attachment/5166582/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1782893/+attachment/5166581/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.la
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1782893/+attachment/5166578/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
h
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1782893/+attachment/5166574/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1782893/+attachment/5166577/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.la
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1782893/+attachment/5166575/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1782893/+attachment/5166576/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1782893/+attachment/5166572/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Tags added: apport-collected bionic
** Description changed:
Bluetooth doesn't work on the Dell XPS 15 laptop, with Ubuntu 18.04.
expected behavior:
in Settings, one goes to the Bluetooth tab, slides the 'ON' button to
'ON', and then Bluetooth is enabled, and o
Public bug reported:
Bluetooth doesn't work on the Dell XPS 15 laptop, with Ubuntu 18.04.
expected behavior:
in Settings, one goes to the Bluetooth tab, slides the 'ON' button to
'ON', and then Bluetooth is enabled, and one can pair devices
what is happening:
in Settings, when clicking on the
Guys, it has been 5(!!!) years, since this bug has been reported. Any
chance for a fix?
Please raise severity to major, to reflect that this is a MAJOR issue
with a CORE component in ubuntu, that affects a lot of services that
would use pre-stop
Workaround-ish: service xxx restart works, because
Public bug reported:
?
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libldap-2.4-2 (not installed)
ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
Uname: Linux 3.13.0-53-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Mon Jul 13 20:52:57 2015
Public bug reported:
I got this automatic error when starting / logging in my 14.10 box
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: linux-image-extra-3.16.0-28-generic (not installed)
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
I wonder if there is a workaround to at least unload the module / re-
load after resuming from suspend
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/736788
Title:
13d3:3304
I'm encountering this not working after a suspend / resume cycle. on a
clean boot, it seems to work. this is on an Asus UX32LN
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/73
30 matches
Mail list logo