This may have something to do with another user already being logged in
another Gnome Session.
--
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/1853762
Title:
Headphones stop
*** This bug is a duplicate of bug 1847524 ***
https://bugs.launchpad.net/bugs/1847524
SOLVED: I found the fix for the gnome-tweak tool. In my case, it turns
out the rapid flickering occurs when Animations is disabled in the
GENERAL page of GNOME-tweak. Re-enabling Animations stopped the
*** This bug is a duplicate of bug 1847524 ***
https://bugs.launchpad.net/bugs/1847524
Additional information: The above rapid flickering on cursor hover in
GNOME-tweak occurs even after:
1) Removing un...@hardpixel.eu (a window decoration multi-function extension)
-- no effect
2) Disabling
** Summary changed:
- Blurred texts, icons and character typed on login screen after logout
+ Blurred texts, icons and character typed on login screen after logout or
switching user
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
add_hooks_info works, however, there seems certain limitation and
something out of current design scope.
For example, check source_xorg.py, there is code flow like:
if is_xorg_input_package(pkg):
code a
else:
code b
If I want to get log from code a and b, I need to use code like:
** Changed in: fedora
Status: Fix Released => Confirmed
** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/issues
#328
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/328
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2105
I don't think it's helpful to reopen bugs that were closed for years.
The original issue was identified and confirmed to be fixed.
It's unlikely that the new symptoms have the same cause as the original
one. But even so, it would require information to understand the new
symptoms better.
Let's
Now https://gitlab.gnome.org/GNOME/gnome-shell/issues/2105
--
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/1609700
Title:
username is not saved in openconnect
That build seems not to fix it. I tried to build locally to bisect, but
can't seem to get the local build to work at all. May have to leave this
to the NM maintainers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Just wanted to mention that this 'bug/issue' is also present in the
current Fedora 31 beta with the following packages:
NetworkManager-openconnect-gnome-1.2.6-2.fc31.x86_64
NetworkManager-openconnect-1.2.6-2.fc31.x86_64
NetworkManager-1.20.4-1.fc31.x86_64
--
You received this bug notification
This is happening to me with F30 with the latest updates as of date.
NetworkManager-openconnect-1.2.6-2.fc30.x86_64
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
This is happening to me with F31 and some Anyconnect VPNs
NetworkManager-openconnect-gnome-1.2.6-2.fc31.x86_64
NetworkManager-openconnect-1.2.6-2.fc31.x86_64
NetworkManager-1.20.6-1.fc31.x86_64
My workaround:
nmcli con mod VPNNAME vpn.secrets
Please test the Fedora 30 build with that commit reverted, at
https://koji.fedoraproject.org/koji/taskinfo?taskID=36857342
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
I wonder if this regression is caused by
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=009f7560867e939
?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
According to https://bugs.launchpad.net/bugs/1609700 this bug has
reoccurred in f30.
--
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/1609700
Title:
username is not
*** Bug 1705711 has been marked as a duplicate of this bug. ***
--
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/1609700
Title:
username is not saved in openconnect
*** This bug is a duplicate of bug 1688018 ***
https://bugs.launchpad.net/bugs/1688018
This is scary thread for a relatively easy fix, for some reason dnsmasq
and OpenVPN don't play well together, it's as simple as commenting out
the "dns=dnsmasq" line in
** Package changed: network-manager-openconnect (Ubuntu) => gnome-shell
(Ubuntu)
--
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/1838838
Title:
username is not
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Public bug reported:
busybox 1.27.2, shipped with at least Ubuntu 18.04, has a bug where the
udhcpd daemon does not react properly to SIGTERM.
That bug if fixed in upstream busybox as of 1.29.0, commit
3293bc146985c56790033409facc0ad64a471084 . That patch should be back-
ported to the busybox
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
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/1853935
Title:
systemd-mount doesn't support lazyunmount
Public bug reported:
lsb_release -rd
Description:Ubuntu 19.10
Release:19.10
apt-cache policy xorg
xorg:
Installed: 1:7.7+19ubuntu12
Candidate: 1:7.7+19ubuntu12
Version table:
*** 1:7.7+19ubuntu12 500
500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
Hey Timo! How is this update looking? Is it looking good for the
upcoming point release? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1848522
Title:
Backport
not proper link
wrote(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1847570
Title:
PulseAudio
** Changed in: librsvg (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to librsvg in Ubuntu.
https://bugs.launchpad.net/bugs/1853657
Title:
librsvg 2.44.15 FTBFS in focal
i take off earphones from the socket, my acoustics sounds correct(switch signal
from earphones to acoustics)
but when i take on my earphones to socket, acoustics sounds , but earphones
don't.
settings->sound, it chooses proper device(earphones), but it doesn't
work proper(not switch signal from
also hedgewars, ghc, and others are having the very same SIGILL
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1859404
Title:
binutils regressed llvm-toolchain-9 and
Having journald in place, rsyslog is no longer strictly necessary, so I
would suggest to stop assuming that rsyslog will be in installed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
golang-1.13 has a really similar issue
# ../misc/cgo/testshared
shared_test.go:72: executing go install -installsuffix=5577006791947779410
-buildmode=shared runtime sync/atomic failed exit status 2:
# /tmp/go-build097387848/b009/libruntime,sync-atomic.so
/<>/pkg/tool/linux_arm64/link:
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
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/1769075
Title:
[regression][bionic] Bluetooth keyboard
Excellent news! The bluetooth dock battery status started working
properly a couple of weeks ago. I can't be sure which update fixed the
bug, but here is the latest system status:-
ubuntu 19.10 eoan Desktop
5.3.0-26-generic x86_64 kernel
Bluez-* 5.50-0ubuntu4
gnome-bluetooth 3.34.0-1
udev
The autopkgtest issue got resolved on a retry
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1847570
Title:
PulseAudio automatically switches to HDMI sound output on
Public bug reported:
Retrying builds on bileto with the release only pocket enabled worked
correctly.
Still trying to figure out what can have regressed it (Debian doesn't show the
issue, but probably it is affected on the same way, just his CPUs can
understand the new instructions?
**
33 matches
Mail list logo
