Ughh, I totally forgot about this one...
I didn't get a chance to test this on a newer Ubuntu version. Unfortunately I
don't have a Ubuntu box in vicinity to try this either. Please close this and
I'm hoping that bluetoothd is working just fine in the newer version.
Thanks.
--
You received
My output with precise-updates:
$ sudo unattended-upgrades --debug --dry-run
Initial blacklisted packages:
Starting unattended upgrades script
Allowed origins are: ['o=Ubuntu,a=precise-security']
Checking: unattended-upgrades ([""])
pkgs that look like they should be upgraded:
Fetched 0 B in 0s
** Attachment added: "foo.log: /var/log/sysylog and dumpe2fs on system chris
saw this on."
https://bugs.launchpad.net/maas/+bug/1643838/+attachment/4871572/+files/foo.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
that said, maybe those could be moved to xorg itself..
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1616742
Title:
xdiagnose does nothing in Wayland
Status in
xdiagnose provides hooks for apport, so that folks filing bugs against
xorg etc actually provide something useful to debug with
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
Nevermind. Found a config issue. Network Manager fails silently
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Here is a run with the updated unattended-upgrades package against the
staging version of the ESM service which is using the requested changes
to the Release file. It recognises the sample landscape-common update
that is there:
root@precise-esm:~# unattended-upgrades --dry-run -d 2>&1
Initial
OdyX, did you have any idea here what is wrong with the multiarch
packaging? Or is it normal that one cannot install both 32-bit and
64-bit -dev packages?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
** Description changed:
Firstly, you should know that the bug reporting software did not work on
the target machine. I have therefore been forced to make this bug report
from a completely different machine, which means that the nicely
automatically packaged information will all be utterly
Adding additional DNS servers via NetworkManager config - also has 0
effect on `systemd-resolve --status`
DNS Domains are changed, though.
Here is systemd-resolve --status:
Global
DNS Servers: 8.8.8.8
8.8.4.4
2001:4860:4860::
Public bug reported:
ubuntu 16.04, enrolled with freeipa-client to FreeIPA 4.4.0 (under
CentOS 7)
With sudo 1.8.16-0ubuntu1, everything is fine:
brian.candler@api-dev:~$ sudo -s
[sudo] password for brian.candler:
root@api-dev:~#
After update to 1.8.16-0ubuntu1.3, it no longer works:
** Description changed:
- [SRU Justification]
- When the dust has settled on the ESM archive Release file format[1],
unattended-upgrades needs to be tweaked to match.
+ [Impact]
+ ESM users relying on unattended upgrades.
+
+ [Test cases]
+ This requires a system installed with Ubuntu 12.04 and
Public bug reported:
When I connect to Corporate WiFi(Enterprise PEAP with certificate,
MSCHAPv2) and acquire a DHCP lease, the DNS servers are never changed by
systemd-resolved from Google's servers.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received
I think unattended-upgrade with -v and --dry-run will be helpful for
testing this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1687129
Title:
Needs to
Public bug reported:
Firstly, you should know that the bug reporting software did not work on
the target machine. I have therefore been forced to make this bug report
from a completely different machine, which means that the nicely
automatically packaged information will all be utterly useless to
Public bug reported:
You newer know when your document or template created using ubuntu family fonts
will crash.
You can save a flawless document and after reopening it within minutes it's
crashed. The text is scattered around and you can make it useful again only by
changing the size of the
** Description changed:
- When the dust has settled on the ESM archive Release file format[1],
- unattended-upgrades needs to be tweaked to match.
+ [SRU Justification]
+ When the dust has settled on the ESM archive Release file format[1],
unattended-upgrades needs to be tweaked to match.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Here is bug report for DNS VPN problems -> #1688018 ... as requested.
--
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
Public bug reported:
This was initially opened as #1671606 then later duped to #1639776.
Discussion in #1639776 indicate that we need new bug for this so I am
opening one ... Please don't mark this as duplicate to #1639776 or other
similar bug report. We already lost several months and we are
** Changed in: ubuntu-z-systems
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1679691
Title:
libseccomp fix - s390: handle
** Description changed:
+ [ Impact ]
+
+ * Unable to ssh into Ubuntu, using default sshd configuration, when hw
+ acceleration is enabled in openssl.
+
+ [ Proposed solution ]
+
+ * Cherrypick upstream fixes for:
+ - sandboxing code on big endian
+ - allowing hw accel iocls in the sandbox
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.
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]
** 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)
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
** 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
** 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
** 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,
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
** 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.
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.
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.
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
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
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.
** 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
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:
** 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
** 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
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
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-
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
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.
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
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:
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
** 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
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
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/1362694
Title:
Can't pair with car kit (reverse mode)
Status in bluez package in Ubuntu:
** 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
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:
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:
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:
** 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
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
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
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-
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-
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-
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:
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:
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:
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:
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:
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:
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)
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)
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:
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:
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:
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
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:
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:
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:
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
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:
** 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
** 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
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
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:
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)
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:
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,
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,
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:
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
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)
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
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:
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)
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:
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)
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
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
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)
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:
101 - 200 of 224 matches
Mail list logo
