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.
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.
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
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.
tests ran: 7, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-83.106-generic/onza__4.4.0-83.106__2017-06-27_14-35-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700541
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63-generic/rumford__4.8.0-58.63__2017-06-27_14-23-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700533
tests ran: 5, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63-generic/secchi__4.8.0-58.63__2017-06-27_15-11-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700533
Temporary fix forked for me by adding those two lines before each job
however I need something that will work permanently.
lpadmin -p -R usb-unidir-default
lpadmin -p -o usb-no-reattach-default=true
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700544
Title:
linux-raspi2: 4.4.0-1061.69 -proposed
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-123.172-generic/gonzo__3.13.0-123.172__2017-06-27_14-58-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Temporary fix for me worked with adding those two lines before printing
each time:
lpadmin -p -R usb-unidir-default
lpadmin -p -o usb-no-reattach-default=true
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700763
Title:
I'm a noob, and
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
** Changed in: libreoffice (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: libreoffice (Ubuntu)
Importance: Undecided => High
** Changed in: libreoffice (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
Public bug reported:
Testing the 5.3.3 candidate update the menus are corrupted (a part of
the labels are not showing or only on mouseover)
** Affects: libreoffice (Ubuntu)
Importance: High
Assignee: Olivier Tilloy (osomon)
Status: Confirmed
** Tags: snap
--
You received
This bug was fixed in the package transmission - 2.92-2ubuntu2
---
transmission (2.92-2ubuntu2) artful; urgency=low
[ Leszek Lesner ]
* debian/rules, debian/transmission-qt.install:
- Fix translation loading for transmission-qt (LP: #1007744).
-- Gunnar Hjalmarsson
Also occured on fresh install of kubuntu 16.04.2.
So I am turning it off, and would suggest to disable it by default and
eventually suggest user to turn it on to "optimize" his system.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to Kubuntu
Can you get the journal (journalctl -b > file) to help determine what
prevented it from starting?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/270899
Title:
/etc/init.d/apache2 restart fails on
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1548051
Title:
baloo takes
** Also affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1548051
Title:
baloo takes up most of my CPU
To manage notifications about this
How is ghemical affected?
** Changed in: ghemical (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583550
Title:
sudo sh ./molmol-2K.2.sh MolMol v2K.2 -
How does this affect ghemical and avogadro?
** Changed in: avogadro (Ubuntu)
Status: New => Incomplete
** Changed in: ghemical (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I don't know anything about the bug. This report was automatically
generated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698186
Title:
package libmagickcore-6.q16-2:amd64 8:6.8.9.9-7ubuntu5.7
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: imagemagick (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698186
Title:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699360
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699360
Title:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699360
Title:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699360
Title:
** Also affects: elinks (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866015
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
** Also affects: elinks (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866015
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700283
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63-generic/hainzel__4.8.0-58.63__2017-06-27_14-01-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700533
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-58.63-generic/ms10-35-mcdivittB0-kernel__4.8.0-58.63__2017-06-27_14-06-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63-generic/fozzie__4.8.0-58.63__2017-06-27_15-15-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700533
tests ran: 6, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63-generic/pepe__4.8.0-58.63__2017-06-27_14-23-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700533
tests ran: 4, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-123.172-generic/archytas__3.13.0-123.172__2017-06-27_15-17-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
tests ran: 4, failed: 1;
http://kernel.ubuntu.com/testing/3.13.0-123.172-generic/ms10-34-mcdivittB0-kernel__3.13.0-123.172__2017-06-27_15-09-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
tests ran: 5, failed: 1;
http://kernel.ubuntu.com/testing/3.13.0-123.172-generic/archytas__3.13.0-123.172__2017-06-27_14-36-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
tests ran: 19, failed: 2;
http://kernel.ubuntu.com/testing/3.13.0-123.172-generic/fozzie__3.13.0-123.172__2017-06-27_14-06-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
tests ran: 3, failed: 1;
http://kernel.ubuntu.com/testing/3.13.0-123.172-generic/ms10-34-mcdivittB0-kernel__3.13.0-123.172__2017-06-27_14-24-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Project changed: intel => linux-firmware (Ubuntu)
** Changed in: linux-firmware (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700772
Title:
Opened bug #1700772 for reverting to version 0.47.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519668
Title:
[Feature]Add Intel Omni-Path Architecture (OPA) Firmware
To manage notifications
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;
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;
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;
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;
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
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
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
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
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
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
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;
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;
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;
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;
http://lists.gnu.org/archive/html/freeipmi-devel/2017-06/msg0.html
Patch on upstream mailing list
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699933
Title:
ipmi-locate crash on arm64
To
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
Bugs, which is subscribed
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"
*** This bug is a duplicate of bug 1646739 ***
https://bugs.launchpad.net/bugs/1646739
** This bug has been marked a duplicate of bug 1646739
"Use of uninitialized value" in debconf via update-manager
--
You received this bug notification because you are a member of Ubuntu
Server Team,
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;
> Why would you want to run Math separately?
I personally wouldn't, but it might be a valid use case for some users.
It feels a bit harsh to be hiding the application from them.
> You could move the .desktop and appstream metadata for LibreOffice Math
> into a separate binary package
*** This bug is a duplicate of bug 1646739 ***
https://bugs.launchpad.net/bugs/1646739
** This bug has been marked a duplicate of bug 1646739
"Use of uninitialized value" in debconf via update-manager
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1695216
Title:
Can't disable USB port from BIOS
To manage
Thank you for reporting this bug to Ubuntu.
You have "security = share" in your /etc/samba/smb.conf:
$ testparm ./smb.conf
Load smb config files from ./smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
WARNING: The "syslog" option is deprecated
WARNING: Ignoring
Is the primary point of contention for a trusty backport the early
initramfs microcode loading referenced in comment #12? Can we continue
using the same mechanism previous trusty microcode updates used?
Also, it sounds like 14.04 trusty has the early microcode loading
feature?
Thank you for reporting this bug to Ubuntu.
You have "security = share" in your /etc/samba/smb.conf:
$ testparm ./smb.conf
Load smb config files from ./smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
WARNING: The "syslog" option is deprecated
WARNING: Ignoring
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63-generic/secchi__4.8.0-58.63__2017-06-27_13-44-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700533
tests ran: 15, failed: 3;
http://kernel.ubuntu.com/testing/4.8.0-58.63-generic/s2lp6g002__4.8.0-58.63__2017-06-27_14-31-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700533
tests ran: 15, failed: 3;
http://kernel.ubuntu.com/testing/4.8.0-58.63-generic/s2lp4__4.8.0-58.63__2017-06-27_14-29-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700533
tests ran: 20, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-83.106-generic/michael__4.4.0-83.106__2017-06-27_13-34-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700541
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700534
Title:
linux-hwe: 4.8.0-58.63~16.04.1 -proposed
tests ran: 15, failed: 3;
http://kernel.ubuntu.com/testing/4.4.0-83.106-generic/s2lp3__4.4.0-83.106__2017-06-27_14-22-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700541
tests ran: 15, failed: 3;
http://kernel.ubuntu.com/testing/4.4.0-83.106-generic/kernel01__4.4.0-83.106__2017-06-27_14-22-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700541
tests ran: 15, failed: 3;
http://kernel.ubuntu.com/testing/4.4.0-83.106-generic/s2lp6g001__4.4.0-83.106__2017-06-27_14-22-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
701 - 800 of 1096 matches
Mail list logo
