** Changed in: debian-handbook (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2019939
Title:
Outdated documentation
** Changed in: debian-handbook (Ubuntu)
Assignee: (unassigned) => Heather Ellsworth (hellsworth)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2019939
Ti
Hi Alexandre, I just tried on a fresh 20.04.6 vm and the issue is no
longer present.
To test this, I had to `apt purge firefox && snap install firefox` which
installed 111.0-2. xdg-desktop-portals is at version 1.6.0-1ubuntu2.
--
You received this bug notification because you are a member of
Since upgrading to kinetic, I see this daily. My network connectivity
seems fine but yet the question mark appears in the wifi icon. Randomly
the question mark will go away, leaving a normal wifi indicator showing
connectivity, and then it will come back. There is no visible change in
the network
The issue exists in the Firefox snap as well:
https://bugzilla.mozilla.org/show_bug.cgi?id=1784977
** Bug watch added: Mozilla Bugzilla #1784977
https://bugzilla.mozilla.org/show_bug.cgi?id=1784977
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
If the solution is to remove libcanberra-gtk3-module and since it hasn't
been touched since 2012, do we need to provide it at all?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
I just tested this version on jammy and my headset now will reconnect
after a suspend without problems. Thanks so much for cherry-picking
those patches!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Regarding comment #17 and missing devices from rfkill, there was just a
miscommunication. I meant that the bluetooth line has not changed, and
only pasted that one. But in both cases (before/after suspend), I do see
all three lines as mentioned in #17. Sorry for the unnecessary
confusion.
I'm
There is no difference in 'rfkill' before/after suspend. In both cases,
the bluetooth line looks like this:
heather@fenrir:~$ rfkill
ID TYPE DEVICE SOFT HARD
0 bluetooth tpacpi_bluetooth_sw unblocked unblocked
And the PID of bluetoothd is the same before/after
apport information
** Attachment added: "syslog.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564360/+files/syslog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "getfacl.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564358/+files/getfacl.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "rfkill.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564359/+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.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564355/+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.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564354/+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.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564356/+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.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564357/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564351/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564350/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564348/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564352/+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.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564349/+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.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564353/+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.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564347/+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.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1962542/+attachment/5564346/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Description changed:
Bose quietcomfort 35 is a common headset that can no longer connect to a
jammy system after just one suspend. This started at the end of January
but just now really debugging the issue.
+
+ Side note that my bluetooth mouse works fine without
Public bug reported:
Bose quietcomfort 35 is a common headset that can no longer connect to a
jammy system after just one suspend. This started at the end of January
but just now really debugging the issue.
The headset is only trying to connect to the jammy system (no other
bluetooth devices
Here is a networkd-dispatcher fix:
https://launchpad.net/~hellsworth/+archive/ubuntu/networkd-dispatcher/+build/22316215
And here is a network-manager fix:
https://launchpad.net/~hellsworth/+archive/ubuntu/network-manager/+build/22316944
Both should work, so please test the networkd-dispatcher
I've got this setup between two vms, where the server vm is hosting
dnsmasq with ntp and the client synchronizes from the server (on a
private network). This issue of the timesync conf needing to be updated
exists in systemd-timesyncd too. But tackling the NetworkManager case as
this is the
I tried to reproduce this, to test the fix, but I am stuck trying to figure out
how to manually set the ntp server. I can't see any difference between when the
vm (with no network) has this
/etc/NetworkManager/dispatcher.d/10-update-timesyncd file in place or not. I
think that's good but maybe
The gstreamer commit that fixes the issue is on gstreamer master on
2021-06-23:
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/b16e96dd878e0c5e7baeb8fad62ca43de1f66982
So this should be picked up in the next tag, which might be in a month
or so. Then that gstreamer needs to be
Public bug reported:
indicator-power no longer builds.
make[3]: *** No rule to make target 'tests/gmock/libgmock_main.a',
needed by 'tests/test-notify'. Stop.
The build failure: https://launchpadlibrarian.net/532498126
/buildlog_ubuntu-hirsute-amd64.indicator-
Public bug reported:
I updated my focal system and rebooted. Shortly after logging in, I see
that PackageKit crashed. Here is the systemctl log from the time that
PackageKit started. Recording it here just in case it happens again.
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package:
Public bug reported:
On a freshly installed 20.04 system, going through the initial setup and
I'm presented with the Online Accounts panel where I selected Google,
entered my email and password. Then Google's 2-factor authentication
kicks in and instructs me to check my phone. I do and approve
Public bug reported:
When at the terminal, trying to file an issue with ubuntu-bug, I was
prompted for authentication. Only after the third try was the password
accepted.
1. I entered the password correctly and the authentication window closed and
reopened very quickly (no error message that I
In 19.10, with the error state, restarting upower fixes the issue. So if
you've booted without power connected, then connect power and don't see
the charging icon, execute `sudo systemctl restart upower` and see the
charging symbol.
--
You received this bug notification because you are a member
I tried this in a 19.04 live boot from a usb stick and the behavior was
correct: if the system was booted without power, the charging symbol was
not there. Then when I connected the power, the charging symbol
appeared.
Also, when booting 19.04 without power connected, there is only the one
The following is the output of `journalctl | grep -i power` that covers
the duration between the reboot command and login times.
** Attachment added: "journal-power-keyword_with-power-connected-on-boot.out"
The following is the output of `journalctl | grep -i power` that covers
the duration between the reboot command and login times.
** Attachment added: "journal-power-keyword_no-power-connected-on-boot.out"
The only difference in journalctl between when the system boots with
power and without is that when the system boots without power, I see two
journalctl messages:
Sep 26 10:53:27 fenrir dbus-daemon[793]: [system] Activating via systemd:
service name='org.freedesktop.UPower' unit='upower.service'
This issue is completely reproducible for me. Digging into the
journalctl logs around when the system is rebooting without power
plugged in, here are some lines that stand out and might be useful:
Note that the system was sent to reboot at 10:53:00
...
Sep 26 10:53:37 fenrir systemd[2088]:
Public bug reported:
Hardware: Lenovo T590
OS: 19.10
When the power is not connected when the laptop boots, and then
connected, the power icon in the top bar does not change to indicate
that the laptop is now charging.
$ upower -d
Device: /org/freedesktop/UPower/devices/line_power_AC
41 matches
Mail list logo
