Public bug reported:
i dont know, but i can't install some programs
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: util-linux 2.27.1-6ubuntu3.2
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
** Changed in: ubuntu-themes
Importance: Undecided => High
** Changed in: ubuntu-themes (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
Is it feasible to put NM 1.4 into -backports pocket?
--
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/1585863
Title:
WiFi malfunction after suspend & resume stress
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
** Changed in: oem-priority/xenial
Importance: High => Critical
--
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/1690980
Title:
No pop-up window to warn
Public bug reported:
failure to download repository information
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic i686
ApportVersion: 2.14.1-0ubuntu3.7
Architecture:
https://packages.debian.org/stretch/network-manager has contained those
fixes.
Could someone help to test
https://launchpad.net/~happyaron/+archive/ubuntu/nm-oem/+packages if it
can fix this bug?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
This bug was fixed in the package util-linux - 2.27.1-6ubuntu3.3
---
util-linux (2.27.1-6ubuntu3.3) xenial; urgency=medium
* Cherrypick upstream fix to prevent lscpu crash on arm64 by
accessing DMI in sysfs instead of /dev/mem. LP: #1674258
-- Ike Panhc
The verification of the Stable Release Update for util-linux has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package util-linux - 2.29-1ubuntu2.1
---
util-linux (2.29-1ubuntu2.1) zesty; urgency=medium
* Cherrypick upstream fix to prevent lscpu crash on arm64 by
accessing DMI in sysfs instead of /dev/mem. LP: #1674258
-- Ike Panhc
This bug was fixed in the package util-linux - 2.28.2-1ubuntu1.2
---
util-linux (2.28.2-1ubuntu1.2) yakkety; urgency=medium
* Cherrypick upstream fix to prevent lscpu crash on arm64 by
accessing DMI in sysfs instead of /dev/mem. LP: #1674258
-- Ike Panhc
This very common crash has not been reported to errors.ubuntu.com in
several weeks on artful. I verified that I could not reproduce the crash
at LP: #1695567 any more after updating libgweather to 3.24.1-0ubuntu0.1
on Ubuntu GNOME 17.04.
** Tags removed: verification-needed
** Tags added:
Before applying this update, I was able to easily crash GNOME Shell in a
default clean updated Ubuntu GNOME 17.04. All I had to do with click the
system status menu in the top right and enable Location.
After updating to libgweather 3.24.1-0ubuntu0.1, I can't reproduce the
crash.
** Tags
In Xenial the translation template has 33 items, and in Zesty it only
has 13. I suspect that this bug was caused by this commit:
http://bazaar.launchpad.net/~indicator-applet-developers/indicator-
datetime/trunk.16.10/revision/476
The missing translation, which Olivier mentioned in the bug
Hello Darko,
This is a server misconfiguration. Servers need to supply the full
certificate chain to a trusted root certificate, not just their end
certificate. Qualys's excellent ssltest tool caps the grade for this
server at B as a result of this misconfiguration:
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
evolution-data-server. This problem was most recently seen with package
version 3.22.7-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/5fbe24c6d9fbde80c0c8a6c0436da49809ae6515
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1700854
Title:
package software-properties-gtk 0.96.20.5 failed to
Public bug reported:
The software app froze while updating, and now whenever I try to install
or update anything I get a message saying I need to run dpkg --configure
-a first, but terminal freezes when I try to run it.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package:
Here's a request asking for gnome-control-center to warn somehow when
the Synaptics driver is in use:
https://bugzilla.gnome.org/show_bug.cgi?id=784266
** Bug watch added: GNOME Bug Tracker #784266
https://bugzilla.gnome.org/show_bug.cgi?id=784266
--
You received this bug notification
This bug was fixed in the package cloud-init - 0.7.9-197-gebc9ecbc-
0ubuntu1
---
cloud-init (0.7.9-197-gebc9ecbc-0ubuntu1) artful; urgency=medium
* debian/control: add build dependency python3-jsonschema (LP: #1695318)
* New upstream snapshot.
- Azure: Add network-config,
same here
Reading package lists... Done
Building dependency tree... Done
Calculating upgrade... Done
The following packages have been kept back:
libmirclient9 libmirclient9:i386
The following packages will be upgraded:
libqt5test5
1 to upgrade, 0 to newly install, 0 to remove and 2 not to
Public bug reported:
Since Ubuntu 16.10, mesa-utils has been installed by default (I think this is
because libqt5gui5 Recommends: mesa-utils). mesa-utils provides these binaries:
glxdemo
glxgears
glxheads
glxinfo
For 17.10, Ubuntu plans to switch to GNOME on Wayland as default (or at least
Thank you for taking the time to verify this stable release fix. We
have noticed that you have used the verification-done tag for marking
the bug as verified and would like to point out that due to a recent
change in SRU bug verification policy fixes now have to be marked with
per-release tags
@mattofak - thanks for filing the bug. I've linked it to the manpage
project. It'll get fixed.
** Also affects: ubuntu-manpage-repository
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
"So if this is a bug, it is a bug against manpages.ubuntu.com."
Yes, I misspoke. To clarify I'm used to seeing the "provided by" link on
manpages.ubuntu.com to link to the package I need to install to get the thing
the man page references. That may just be a false association though.
--
You
Hello Brian, or anyone else affected,
Accepted apport into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.3-0ubuntu8.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Brian, or anyone else affected,
Accepted apport into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.4-0ubuntu4.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Brian, or anyone else affected,
Accepted apport into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.1-0ubuntu2.8 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Of course, this would be adding complexity instead of removing it, but
it might be worth doing an "ntpdate -q" first, parsing the output, and
if the offset is "large enough" (whatever that might be), do the
stop/ntpdate/start dance, else exit.
--
You received this bug notification because you
So, the one regression I see possible here is on machines with
lousy/broken clocks at boot time. If you start ntpd with a clock too
far in the past/future, it'll either give up and exit (if VERY far off)
or start a drift that could take hours/days to correct. If you remove
the restarting around
*** This bug is a duplicate of bug 1699108 ***
https://bugs.launchpad.net/bugs/1699108
Due to a bug in apport's method for creating a duplicate signature, the
DuplicateSignature in this report was incorrect. We are fixing that now,
sorry for the noise!
** Attachment added:
Due to a bug in apport's method for creating a duplicate signature, the
DuplicateSignature in this report was incorrect. We are fixing that now,
sorry for the noise!
** Attachment added: "DuplicateSignature.txt"
*** This bug is a duplicate of bug 1699108 ***
https://bugs.launchpad.net/bugs/1699108
** Attachment removed: "DuplicateSignature.txt"
https://bugs.launchpad.net/bugs/1700575/+attachment/4903626/+files/DuplicateSignature.txt
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1700282 ***
https://bugs.launchpad.net/bugs/1700282
DuplicateSignature:
Unpacking systemd (229-4ubuntu17) over (229-4ubuntu4) ...
Unpacking systemd (229-4ubuntu17) over (229-4ubuntu4) ...
dpkg: error processing archive
** Attachment removed: "DuplicateSignature.txt"
https://bugs.launchpad.net/bugs/1700659/+attachment/4903799/+files/DuplicateSignature.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
Public bug reported:
I've submitted an MIR for the numactl binary package at: LP: #1700824.
Assuming that is approved, please also include this on the server seed, which I
believe is necessary for it to appear on the ubuntu-server ISOs.
** Affects: ubuntu-meta (Ubuntu)
Importance:
*** This bug is a duplicate of bug 1693226 ***
https://bugs.launchpad.net/bugs/1693226
** This bug has been marked a duplicate of bug 1693226
Break the conflicts with click the optparser
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
E: /usr/share/initramfs-tools/hooks/casper-memdisk failed with return 1.
This seems to be related to an initramfs hook for casper, so marking
this bug as also affecting casper.
** Also affects: casper (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-base1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1700820
Title:
package gstreamer1.0-plugins-base:i386 (not installed)
Public bug reported:
it happened after 14.04 to 16.04 upgrade.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gstreamer1.0-plugins-base:i386 (not installed)
ProcVersionSignature: Ubuntu 4.4.0-81.104~14.04.1-generic 4.4.67
Uname: Linux 4.4.0-81-generic x86_64
NonfreeKernelModules:
Actually it was solved on 17.04 :)
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624317/comments/82
Enjoy!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Could you please explain why Canonical is tracking user hardware per
default without user consent?
See /etc/update-motd.d/50-motd-news
e.g.
platformn : GNU/Linux/4.4.0-81-generic/x86_64
lsb : Ubuntu/16.04.2/LTS
arch : x86_64
cpu : Intel(R)/Xeon(R)/CPU/E5-2650/0/@/2.00GHz
uptime
*** This bug is a duplicate of bug 1693226 ***
https://bugs.launchpad.net/bugs/1693226
** This bug has been marked a duplicate of bug 1693226
Break the conflicts with click the optparser
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
It looks like you've installed click via pip or another python package
system.
Preparing to unpack .../click_0.4.43+16.04.20170613-0ubuntu1_amd64.deb ...
Cannot start click due to a conflict with a different locally-installed Python
'click' package. Remove it using Python packaging tools and
Note, the actual manpage makes no mention of the package. Which is
how it should be, as the manpage comes from upstream and not from
Ubuntu.
So if this is a bug, it is a bug against manpages.ubuntu.com.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
wow, this was opened in 2013...linux users are really patient! I will
restart my Ubuntu Mate and boot into Win10...where I can use openvpn
config files...pushed dns server...log verbosity...
Pls don't get me wrong...I love linux...but bugs like this one gets me
nuts...2013...wow...even I know to
Public bug reported:
If I grant a user (via pam_cap) cap_setfcap+i, I would then expect them
to be able to use setcap without sudo. setcap is not provided with any
default file capabilities however, so either the user has to sudo, or I
have to grant the setfcap capability to setcap with setcap.
Public bug reported:
The man page for pam_cap
(http://manpages.ubuntu.com/manpages/xenial/man8/pam_cap.8.html) claims
that it is provided by the libcap2-bin package. This is incorrect, it is
actually provided by the libpam-cap package (which is recommended by
libcap2-bin.)
** Affects: libcap2
For reference... https://github.com/karma-runner/karma-chrome-
launcher/issues/76
** Bug watch added: github.com/karma-runner/karma-chrome-launcher/issues #76
https://github.com/karma-runner/karma-chrome-launcher/issues/76
--
You received this bug notification because you are a member of
** Also affects: base-files (Ubuntu Artful)
Importance: High
Assignee: Dustin Kirkland (kirkland)
Status: In Progress
** Also affects: base-files (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: base-files (Ubuntu Zesty)
Assignee: (unassigned) =>
** Changed in: base-files (Ubuntu)
Assignee: (unassigned) => Dustin Kirkland (kirkland)
** Changed in: base-files (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Hi there. By design, it does not fetch motd.ubuntu.com with every ssh
session.
Rather, there's a systemd timer that runs, asynchronously once about a
minute after boot, and then every 12 hours (plus/minus a random interval
up to an hour). That systemd timer updates a cache file,
Public bug reported:
Testing failed on:
ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/systemd/20170627_083238_11cda@/log.gz
** Affects: systemd (Ubuntu)
Importance:
Using ath9k driver: no issues
My netbook running iwlwifi driver still has this bug. It's in Ubuntu,
because I'm running Debian Stretch just fine there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
You can also edit /etc/default/motd-news and:
a) set ENABLED=0
b) changed the URL to a custom one that does resolve or work for you
c) change the time to wait
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files
By design, the cache file, /var/cache/motd-news, should be populated in
the background by a systemd timer that runs roughly once a day.
If that file is populated, then there should be zero impact on login.
Perhaps the background cache population should create an empty file, if
it can't reach the
suggested fix is
http://paste.ubuntu.com/24964373/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1691901
Title:
50-motd-news costs 5 seconds every login on
** Changed in: base-files (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1691901
Title:
50-motd-news costs 5 seconds every
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1692543
Title:
Regression tests cannot write to apparmor path_max module parameter in
artful/4.11
Public bug reported:
I have desktop background set on tile mode but on lightdm login screen
the image is stretched and pixelated.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
Uname: Linux 4.4.0-81-generic
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1700791
Title:
package libkmod2 22-1.1ubuntu1 [modified:
Public bug reported:
crashes on startup
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libkmod2 22-1.1ubuntu1 [modified:
usr/share/doc/libkmod2/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
Uname: Linux 4.10.0-24-generic x86_64
NonfreeKernelModules:
One final note: it seems that problem may be overcame by removing
contents of /run/network just before reboot/shutdown.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
** Summary changed:
- [Latitude 3340, Realtek ALC3234, Headphone] Static in Headphones While on
Battery Power
+ [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery Power
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
For future reference, this is the list of upstream commits corresponding
to Aaron's patches, in the order they are being applied:
312cea870dfbc363da44074bd6f56ccd283c5420
shared: add nm_auto_close and nm_auto_fclose
ed299cc8605a8291a61b3a514f8dc20390b18c77
device/wwan: use nm_auto_close
Actually, I'm not convinced that update-manager is the front end in use
here. If we look at the JournalErrors.txt file attached to this bug we
can see the following:
dic 02 09:33:40 hostname org.debian.apt[871]: 09:33:40 AptDaemon [INFO]:
Initializing daemon
dic 02 09:33:40 hostname
This bug was fixed in the package klibc - 2.0.3-0ubuntu1.14.04.3
---
klibc (2.0.3-0ubuntu1.14.04.3) trusty; urgency=medium
* debian/patches/dhcp-one-socket-per-interface.patch: Use separate
sockets for DHCP from multiple interfaces. Thanks to Jay Vosburgh
This bug was fixed in the package nplan - 0.23~16.10.1
---
nplan (0.23~16.10.1) yakkety; urgency=medium
* Backport netplan 0.23 to 16.10. (LP: #1688632)
nplan (0.23) artful; urgency=medium
* Do not unbind brcmfmac, interface will be gone. (LP: #1696162)
nplan (0.22) artful;
I see now that this issue is true for Swedish as well, so the issue is
not specific to French. Can it be that the translation template for
indicator-datetime needs to be updated?
** Changed in: ubuntu-translations
Assignee: Ubuntu French Translators (ubuntu-l10n-fr) => (unassigned)
--
You
These lines should work permanently, as the option setting changes are
permanently recorded in /etc/cups/printers.conf.
For making them getting applied automatically for everyone having this
printer a quirk rule has to be added to /usr/share/cups/usb/org.cups
.usb-quirks.
You can edit the file
I can also confirm that the issue exists.
I'm the administrator of 2 DNS nameservers (bind9) running Ubuntu
14.04.5 LTS with upgraded kernel (linux-image-generic-lts-xenial which
depends on linux-image-4.4.0-81-generic at this time).
root@ns2:~# lsb_release -a
No LSB modules are available.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
You have been subscribed to a public bug:
When I print a PDF from my raspberry pi (raspbian jessie) through CUPS (
CUPS 1.7.5) service the first job prints fine but after that any other job
prints random set of characters at the top of the page. I run `CUPS error_log`
but it has nearly 26,000
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
Khurshi, thanks for your comment.
Shotwell was stuck on an old git snapshot for over a year (LP: #1581180)
because the UOA support was unmaintained and no one had the time or
ability to forward-port that support. That support has now been removed
and we'll finally get a supportable version of
** Information type changed from Public to Public Security
** Information type changed from Public Security to Private
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1700763
Public bug reported:
After a new install of Ubuntu 16.04.2 LTS, i have some bugs.
I'm new in the Ubuntu world, but i would like to know more.
I have install the OS with a pen and after i installed some apps from the
"Ubuntu software" and i run the "software update". After this i restart the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-software (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pam (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
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 pam in Ubuntu.
The verification of the Stable Release Update for nplan has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package nplan - 0.23~16.04.1
---
nplan (0.23~16.04.1) xenial; urgency=medium
* Backport netplan 0.23 to 16.04. (LP: #1688632)
nplan (0.23) artful; urgency=medium
* Do not unbind brcmfmac, interface will be gone. (LP: #1696162)
nplan (0.22) artful;
Will these be available on universe? Because many little applications
still depends on them? Shotwell works with UOA and flickr. Same for
empathy. Removal of UOA basically means removal of Unity7.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
This patch fixes the tests for me. Turns out that we can't simply skip
writing to path_max as that seems to break the test case completely, so
I changed it to print an XFAIL message and abort the test.
** Patch added: "fix-longpath-test.patch"
** Tags removed: verification-done
** Tags added: verification-done-xenial
--
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/1283003
Title:
Bluetooth headset/speakers listed
** Tags removed: verification-done
** Tags added: verification-done-xenial
--
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/1438510
Title:
[regression] Bluetooth audio no
1 - 100 of 136 matches
Mail list logo