Public bug reported:
My W540 can not detect my external screen when I arrive at work after my
laptop have been used at home with no external screen and suspended on
the way to work. Sometimes it does detect it. Sometimes I can un-dock
and dock again and it works. Sometimes it never works when I am
I am running Ubuntu Zesty 17.04 and have this flickering issue. The
above fix of changing the theme does nothing to correct the issue. I was
using 16.10 prior and did not have this problem. Only after the upgrade
did this start to happen. Is there any update on a possible fix for
this?
--
You rec
My current situation is matching Johns comment, since the Host is Xenial
in my case all "would" run just fine - and it does seem to work, except
of the fact that while loading fine due to the postinst loading them on
reboot they are skipped.
On a not representative scan on my system in /var/lib/dp
I have a fully updated Ubuntu 17.04 and when I connect to VPN
/var/run/NetworkManager/resolv.conf does not get updated with DNS. Any
fix soon?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.lau
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: debconf (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.n
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openssl (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.n
I did some testing, it affects PPTP, but does not seem to affect
OpenVPN.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1639776
Title:
name resolution (dnsmasq) fails to
@exander77 this bug is specifically about a failure after
suspend/resume. If your issue does not relate to suspend/resume it is a
different bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.l
@colin-law That's bullshit, #1671606 was closed as duplicated of this:
DNS server from vpn connection is not being used after network-manager upgrade
to 1.2.6-0ubuntu0.16.04.1
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606
--
You received this bug notification because you
G'day Brian! Yes, the theme workaround began not working for me with
17.04. Yes, the problem can come and go with any changes to the
hardware, kernel, X server, or libraries. There is a fix that makes the
situation a lot better, see my post last week on the upstream bug
https://bugzilla.abisourc
@mbrennwa that seems likely (display issue) There was a similar bug a
while ago that was a rendering issue:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-
accounts/+bug/1309247
Also, there have been recent updates to Gnome's Javascript engine iirc
--
You received this bug notification b
Philip, the 'not working' one or the 'way too fast' one?
--
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/1657553
Title:
Laptop stick and touchpad problems after linux 4.4 u
Karl,
Please retest with a newer (supported) version of Ubuntu:
https://wiki.ubuntu.com/Releases
** Changed in: bluez (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in U
@exander77 there is no need for personal abuse here. In that case the
description of this bug should have been updated to include that.
However I see there is debate on that bug about whether it is fixed by
the version of dnsmasq which fixes this bug. If not then it is
definitely a different bug. I
Thank you for reporting this bug to Ubuntu. Ubuntu 9.10 (karmic) reached EOL on
April 30, 2011.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Confirmed =
Thank you for reporting this bug to Ubuntu. Ubuntu 9.10 (karmic) reached EOL on
April 30, 2011.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Confirmed =
Jeff,
Thank you for reporting this bug to Ubuntu. Ubuntu 10.04 (lucid) reached
EOL on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Confirme
vava,
Thank you for reporting this bug to Ubuntu. Ubuntu 10.10 (maverick)
reached EOL on April 10, 2012.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Co
co0lingFir3,
Thank you for reporting this bug to Ubuntu. Ubuntu 10.04 (lucid) reached
EOL on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: gnome-bluetooth (Ubuntu)
Thank you for reporting this bug to Ubuntu. Ubuntu 10.04 (lucid) reached EOL on
May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Confirmed => I
Perttu,
Thank you for reporting this bug to Ubuntu. Ubuntu 10.04 (lucid) reached
EOL on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Confir
Yotam,
Thank you for reporting this bug to Ubuntu. Ubuntu 10.04 (lucid) reached
EOL on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Confirm
Vojtěch,
Thank you for reporting this bug to Ubuntu. Ubuntu 11.04 (natty) reached
end-of-life on October 28, 2012.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
The fix mentioned in vorlon's branch does not appear in the current
bluez source yet. Do we need it or was another solution found?
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
I realized we carry this as Delta and there was no Debian report yet, I
opened one and linked it up here.
** Bug watch added: Debian Bug tracker #861727
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861727
** Also affects: ntp (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug
Ivan,
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Sta
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Co
Lunarts,
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Co
Varga,
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
St
Thank you for reporting this bug to Ubuntu. Ubuntu 12.10 (quantal)
reached end-of-life on May 16, 2014. And Ubuntu 11.04 (natty) reached
end-of-life on October 28, 2012.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest versi
Damian,
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
S
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1686081
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Ne
James,
Thank you for reporting this bug to Ubuntu. Ubuntu 12.10 (quantal)
reached end-of-life on May 16, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
Others: If you have ongoing issues, pleas
The aforementioned fixes should be in Ubuntu now, for at least the past
year.
Please confirm and if so we can mark it Fix Released.
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whic
Rykel,
Thank you for reporting this bug to Ubuntu. Ubuntu 13.04 (raring)
reached end-of-life on January 27, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
S
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Co
Thank you for reporting this bug to Ubuntu. Ubuntu 12.10 (quantal)
reached end-of-life on May 16, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Conf
Public bug reported:
blok browser
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CompizPlugin
** Changed in: bluez (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/1241805
Title:
After Upgrade to Kubuntu 13.10 Bluetooth
Please retest on a current supported Ubuntu release and let us know if
the problem persists...
https://wiki.ubuntu.com/Releases
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wik
** Changed in: ntp (Debian)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1576698
Title:
ntpdate-debian not working
Status in ntp package
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached
end-of-life on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Conf
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: C
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Ne
Steve,
Thank you for reporting this bug to Ubuntu. Ubuntu 13.04 (raring)
reached end-of-life on January 27, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
David and others: Please log a new bug
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Ne
Ubuntu Touch is no longer being developed.
** Changed in: bluez (Ubuntu)
Status: New => Won't Fix
--
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/1177421
Title:
pulse
Teo,
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached
end-of-life on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status:
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: C
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Ne
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Ne
Leonid,
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached
end-of-life on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Sta
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Co
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Co
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached
end-of-life on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Conf
Thank you for reporting this bug to Ubuntu. Ubuntu 14.10 (utopic)
reached end-of-life on July 23, 2015.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Conf
Thank you for reporting this bug to Ubuntu. Ubuntu 14.10 (utopic)
reached end-of-life on July 23, 2015.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Con
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1362180
When reporting bugs in the future please use apport by using 'ubuntu-
bu
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1295339
When reporting bugs in the future please use apport by using 'ubuntu-
bu
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1342568
When reporting bugs in the future please use apport by using 'ubuntu-
bu
Do we need to keep this open?
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
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/1362694
Title:
Can't pair with c
Thank you for reporting this bug to Ubuntu. Ubuntu 14.10 (utopic)
reached end-of-life on July 23, 2015.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: New
** Tags added: ubuntu-touch
--
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/1411437
Title:
[mako] crash right after the boot (segfault in plugins/hciops.c:2910)
Status in bl
** Tags added: ubuntu-touch
--
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/1414142
Title:
Continuous skipping of audio track after reconnecting bluetooth to Car
Status in b
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached
end-of-life on February 4, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Ne
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached
end-of-life on February 4, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: C
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached
end-of-life on February 4, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Ne
** Tags added: ubuntu-touch
--
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/1362694
Title:
Can't pair with car kit (reverse mode)
Status in bluez package in Ubuntu:
Incomp
Thank you for reporting this bug to Ubuntu. Ubuntu 14.10 (utopic)
reached end-of-life on July 23, 2015.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: New
** Tags added: ubuntu-touch
--
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/1409047
Title:
Bluetooth audio not working with Volvo multimedia
Status in bluez package in Ubunt
Thank you for reporting this bug to Ubuntu. Ubuntu 14.10 (utopic)
reached end-of-life on July 23, 2015.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: New
Thanks for investigating. At minimum, I think sss_ssh_knownhostsproxy
is going to need to provide a -4 flag for it to be possible to make that
work correctly. After that, it might be necessary to either mangle the
configured ProxyCommand by hand or to somehow extend the ProxyCommand
mechanism to
Public bug reported:
Hi ,
It seems this OS is not good for me where i want to create c drive but it does
not allowing to create drive C which is not good please fix problem as soon as
possbile and let me install windows, system crashing many times ,
and always need updataion
** Affects: debconf
You have been subscribed to a public bug:
Binary package hint: bluez-utils
After connecting to a server once, bnep0 is created and brought up,
however after disconnecting, bnep0 disappears and after reconnecting is
not brought back up, which makes the connection unusable
** Affects: bluez (Ubun
Installed Ubuntu GNOME 16.04 yesterday. Same problem. I get blank window
after password. Not sure if if matters, but I'm using 2-step
verification on my Google account.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-onl
ah... never mind. I was using the systemd netdev, link and network
documentation for Ubuntu 17.04, when my system is on 16.10. My
apologies.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 224389
When reporting bugs in the future please use apport by using 'ubuntu-
bug
I got Ubuntu 16.04 and same problem, but I do not use 2 step
verification, still got same problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1687019
Title
** Changed in: ntp (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1582767
Title:
apparmor permissions missing for winbind
Status in ntp
** Changed in: systemd (Ubuntu)
Status: New => In Progress
--
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/1685484
Title:
DHCP exit hook for setting NTP servers does
Public bug reported:
it happens when I tried to update Libreoffice
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-72-generic 4.4.0-72.93
ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39
Uname: Linux 3.13.0-116-generic x86_64
ApportVersion: 2.20.1-0ubu
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1687950
Title:
package linux-image-4.4.0-72-generic 4.4.0-72.93 failed to
in
I tried reproducing the issue, but without NM it worked.
Seems to be LP: #293139, but I dig further and test in a VM with NM.
--
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/1
This is the format we have now (in the staging esm service, soon to be
deployed to production)
500 https://extended.security.staging.ubuntu.com/ubuntu/ precise/main i386
Packages
release v=12.04,o=UbuntuESM,a=precise,n=precise,l=UbuntuESM,c=main
origin extended.security.staging.ubuntu.c
Hello Adam, or anyone else affected,
Accepted unattended-upgrades into precise-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/0.76ubuntu1.3 in a few hours, and then in the
-proposed repository.
Please help us by testing this new
So there is indeed no technical reason why apparmor wouldn't work in
trusty containers as long as the host supports it (trusty with hwe
kernel or xenial).
The reason why this wasn't enabled is due to concerns about apparmor
profiles in trusty possibly needing updates to work inside containers.
We'
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
** Also affects: debconf
Importance: Undecided
Status: New
** Changed in: debconf (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpa
Thanks Stéphane,
I can agree to the decision and forward that statement to reports I get for
individual packages.
In the case the need/severity of those issues ever passes a threshold this can
be reconsidered but that will be on you and the security Team again then.
Marking this bug as opinion f
** Also affects: libdrm (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
[Impact]
- Mesa stable release for zesty & backport to xenial.
+ Mesa stable release for zesty & backport to xenial. Xenial needs newer
+ libdrm from zesty.
[Test case]
Install, run
** Changed in: krb5 (Ubuntu Zesty)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: krb5 (Ubuntu Zesty)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in U
** Package changed: debconf (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/1687898
Title:
unable to create drive c
Status in Ubuntu:
New
Bug descri
Public bug reported:
Hi,
since upgrading to 17.04 I can't connect to bluetooth headsets anymore.
Headsets are found and listed as devices, but when trying to connect,
there's an error
blueman.bluez.errors.DBusFailedError: Protocol not available...
syslog says:
May 3 16:43:12 pcdanisch blueto
** Changed in: libseccomp (Ubuntu Artful)
Status: New => Invalid
** No longer affects: libseccomp (Ubuntu Zesty)
** No longer affects: libseccomp (Ubuntu Yakkety)
** Changed in: libseccomp (Ubuntu Xenial)
Status: New => Triaged
** Changed in: libseccomp (Ubuntu Xenial)
Importan
https://launchpad.net/ubuntu/+source/pcsc-lite/1.8.20-1ubuntu1
** Changed in: pcsc-lite (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launc
I have the same issue:
Dell XPS 15 9560
Ubuntu 17.04
4.10.0-20-generic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1575078
Title:
[XPS 15 9550, Realtek ALC3266] He
1 - 100 of 224 matches
Mail list logo