Patch proposal for Artful.
** Patch added: "cups_2.2.3-1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1695884/+attachment/4889375/+files/cups_2.2.3-1ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I have just tested the package (1.11.8-0ubuntu0.7) on Trusty and I
confirm that it fixes the issue: sssd starts correctly without autofs
installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1695870
Till,
The printer in question is was used completely *outside* CUPS - via the
/dev/usb/lp* nodes only. Although there was also an attempt with using it with
a raw queue - with the same result: whenever CUPS was enabled or the printer
was not blacklisted the output from the printer was malformed.
** Tags removed: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665018
Title:
client tools ignore -h option without port number
To manage notifications about this bug go to:
https://bug
Public bug reported:
Upgrading to the latest openvpn breakes already configured VPN
connections.
Steps to reproduce:
1. Import an OpenVPN connection via NetworkManager with the tls-remote option
used.
2. Try to connect to VPN.
Expected result:
VPN connection is established.
Actual result:
(fro
** Description changed:
Steps to reproduce:
- 1. Import an OpenVPN connection via NetworkManager with the tls-remote option
use.
+ 1. Import an OpenVPN connection via NetworkManager with the tls-remote option
used.
2. Try to connect to VPN.
Expected result:
VPN connection is establish
A backport of an upstream-merged workaround for this issue.
The real fix is to manually modify the VPN configurations, but this
reduces the impact after upgrading to Zesty.
** Attachment added: "zesty_network-manager-openvpn_1.2.6-2ubuntu2.dsc"
https://bugs.launchpad.net/ubuntu/+source/networ
I have just verified it for Trusty and Yakkety on the same images that
were used earlier to reproduce it.
The issue is gone.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Thanks Till & Brian.
In the same environment that served as a reproducer the new version
fixes the issue.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Of course I meant Xenial and Yakkety. Thanks for noticing that Robie.
The versions I tested:
* Xenial
libgtk-3-0:
Installed: 3.18.9-1ubuntu3.2
* Yakkety:
libgtk-3-0:
Installed: 3.20.9-1ubuntu2.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Public bug reported:
Affected release: Ubuntu 14.04.5
Version of package: 14.12-0ubuntu5.14.04
Steps to reproduce:
1. Run do-release-upgrade to upgrade to 16.04.2.
2. Trigger the package-reporter to kick in while do-release-upgrade is working
but not having the package database locked.
3. Packag
SRU proposal for artful.
Previous releases are not affected, as this was introduced with some
refactoring done to cupsGetNamedDest (cups/dest.c).
** Patch added: "artful_cups_2.2.4-7ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1729910/+attachment/5005833/+files/artful_
/etc/cups/printers.conf
2) Execute lpstat -d
3) Above will output default defined in prints.conf instead of
~/cups/lpoptions
** Changed in: cups (Ubuntu Artful)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a member
SRU proposal for Artful.
** Patch removed: "artful_cups_2.2.4-7ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1729910/+attachment/5005833/+files/artful_cups_2.2.4-7ubuntu3.debdiff
** Patch added: "artful_cups_2.2.4-7ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/
** Description changed:
[Impact]
- * During some refactoring done to cupsGetNamedDest function used in
+ * During some refactoring done to cupsGetNamedDest function used in
many different parts of the code a regression has been introduced
causing the per-user default printer setting (in
** Changed in: papi (Ubuntu)
Assignee: Dariusz Gadomski (dgadomski) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704130
Title:
[MIR] papi
To manage notificati
I believe it's really useful to also include papi [1] in main as dependency of
pcp and offers support for the performance counter hardware in many processor
types providing a low-level source of metrics.
This ofc seems like an important feature in a performance monitoring suite.
[1] http://icl.u
I believe it's really useful to also include papi [1] in main as it is a
dependency of pcp and offers support for the performance counter hardware in
many processor types providing a low-level source of metrics.
This ofc seems like an important feature in a performance monitoring suite.
[1] http
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729910
Title:
lp ignores ~/.cups/lpoptions in 17.10
To manage notifications about this bug go to:
https://bugs.la
Hello Matthias. Is there any progress with applying those features to
Xenial? Please let me know if you need any testing to be done.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638695
Title:
Pyth
I have reported a Debian bug with request to include the autopkgtests.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871254
** Bug watch added: Debian Bug tracker #871254
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871254
** Also affects: pcp via
https://bugs.debian.org/cgi-bin/b
Artful patch proposal.
** Patch added: "artful_bluez_5.45-0ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+attachment/4928336/+files/artful_bluez_5.45-0ubuntu3.debdiff
** Patch removed: "zesty_bluez_5.43-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+s
Patch proposal for Artful.
** Patch added: "artful_bluez_5.45-0ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+attachment/4928420/+files/artful_bluez_5.45-0ubuntu3.debdiff
** Patch removed: "artful_bluez_5.45-0ubuntu3.debdiff"
https://bugs.launchpad.net/ubun
ged in: samba (Ubuntu)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
** Changed in: samba (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Looks like this has been fixed as a side effect of
https://git.samba.org/?p=samba.git;a=commit;h=b886a9443d49f6e27fa3863d87c9e24d12e62874
So I'll abandon my patch and use the one from upstream.
Artful is not affected - 4.6.7 has the patch already.
Tested it successfully for Trusty, Xenial and Zes
** Description changed:
+ [Impact]
+
+ * In case of accessing directories chdir to it directly instead of its
+ parent directory. This changes how dir symlinks are handled in root
+ shares and leads to avoiding the ACCESS_DENIED ISSUE.
+
+ [Test Case]
+
+ 1. Prepare smb server with a share:
+
SRU proposal for Xenial.
** Patch added: "xenial_samba_4.3.11+dfsg-0ubuntu0.16.04.10.debdiff"
https://bugs.launchpad.net/samba/+bug/1702529/+attachment/4937415/+files/xenial_samba_4.3.11+dfsg-0ubuntu0.16.04.10.debdiff
--
You received this bug notification because you are a member of Ubuntu
B
SRU proposal for Zesty.
** Patch added: "zesty_samba_4.5.8+dfsg-0ubuntu0.17.04.6.debdiff"
https://bugs.launchpad.net/samba/+bug/1702529/+attachment/4937416/+files/zesty_samba_4.5.8+dfsg-0ubuntu0.17.04.6.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
SRU proposal for Trusty.
** Patch added: "trusty_samba_4.3.11+dfsg-0ubuntu0.14.04.11.debdiff"
https://bugs.launchpad.net/samba/+bug/1702529/+attachment/4937414/+files/trusty_samba_4.3.11+dfsg-0ubuntu0.14.04.11.debdiff
--
You received this bug notification because you are a member of Ubuntu
B
** Tags added: sts sts-sru-needed
** Description changed:
[Impact]
- * In case of accessing directories chdir to it directly instead of its
+ * In case of accessing directories chdir to it directly instead of its
parent directory. This changes how dir symlinks are handled in root
share
** Changed in: samba (Ubuntu)
Status: In Progress => 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/1702529
Title:
ACCESS_DENIED with symlinks within a root ("/") share
To manag
** Description changed:
[Impact]
* In case of accessing directories chdir to it directly instead of its
parent directory. This changes how dir symlinks are handled in root
shares and leads to avoiding the ACCESS_DENIED ISSUE.
[Test Case]
1. Prepare smb server with a share:
I have just retried the gvfs autopkgtests locally and all tests pass
there (log attached).
What I run was:
autopkgtest -l autopkgtests.log --apt-pocket=proposed -U
gvfs_1.28.2-1ubuntu1~16.04.2.dsc -- qemu adt-xenial-amd64-cloud.img
It may be something related to the autopkgtest infrastructure.
I have verified the following version of samba this morning:
- Trusty: 4.3.11+dfsg-0ubuntu0.14.04.11
- Xenial: 4.3.11+dfsg-0ubuntu0.16.04.10
- Zesty: 4.5.8+dfsg-0ubuntu0.17.04.6
I run it in a testing environment that was originally used to reproduce
this issue. On all 3 the issue is gone.
** Tags
Matthias, I have made a series of pyperformance benchmarks [1] to
compare the influence of the factors listed by Elvis on Xenial and
Artful. All runs were done on the same machine (metal) with a fresh
Ubuntu cloud image.
My observations confirm that both: changing fpectl and fPIC for _math.c
modul
** Changed in: landscape-client (Ubuntu)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699179
Title:
PackageReporter kicks in during
Public bug reported:
There is a setting available on selected Cisco hardware named "Wi-Fi
Direct Client Policy". One of the allowed option there is 'not-allow'.
It's intention is to block WiFi P2P capable devices from connecting to
it. If a device trying to associate with an AP with this setting e
Thanks for the explanation Matthias. I have added the Xenial variant you
asked for to the spreadsheet.
The artful will follow once I'm after a couple of days out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Bisecting between v4.10 and v4.11 resulted in finding that this was caused by
the following commit:
[ef65aaede23f75977af56a8c330bb9be8c6e125c] smb2: Enforce sec= mount option
Reverting it on top of v4.11 makes it go away.
Looking more into it.
--
You received this bug notification because you
** Summary changed:
- mount.cifs stopped working with protocol version != 1.0
+ mount.cifs stopped working with protocol version>1 and sec=ntlm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746482
T
After the preliminary analysis my understanding is as follows:
since the change found thanks to the bisection the behaviour change in a way
that if an unsupported security mode is requested it results in an error
(invalid argument in this case).
Looks like NTLM was not supported even before the
The fix has been merged upstream, preparing new debdiffs reflecting
that.
** Patch removed: "xenial_gnome-themes-standard_3.18.0-2ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1644662/+attachment/5045075/+files/xenial_gnome-themes-standard_3.18.0-2ubuntu2
Patch for bionic.
** Patch added: "bionic_gnome-themes-standard_3.22.3-3ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1644662/+attachment/5051152/+files/bionic_gnome-themes-standard_3.22.3-3ubuntu2.debdiff
--
You received this bug notification because y
SRU proposal for xenial.
** Patch added: "xenial_gnome-themes-standard_3.18.0-2ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1644662/+attachment/5051154/+files/xenial_gnome-themes-standard_3.18.0-2ubuntu2.debdiff
--
You received this bug notification be
SRU proposal for artful.
** Patch added: "artful_gnome-themes-standard_3.22.3-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1644662/+attachment/5051153/+files/artful_gnome-themes-standard_3.22.3-1ubuntu2.debdiff
--
You received this bug notification be
Public bug reported:
The tools.conf template shipped with Ubuntu (debian/local/tools.conf) is
incorrect.
It's current contents:
bindir = "/usr/bin"
do not mean anything to open-vm-tools - it's not interpreted in any way by
vmtoolsd.
Moreover, on the first launch this content is cleared by a pie
A more useful example based on the comment in open-vm-
tools/lib/include/vmware/tools/log.h.
** Patch added: "bionic_gnome-themes-standard_3.22.3-3ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1748122/+attachment/5051185/+files/bionic_gnome-themes-standard_3.22.
** Also affects: gnome-themes-standard (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity-control-center (Ubuntu Xenial)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
** Bug watch added: Debian Bug tracker #889884
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889884
** Also affects: open-vm-tools via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889884
Importance: Unknown
Status: Unknown
--
You received this bug notification because yo
This time the correct patch attached.
** Patch removed: "bionic_gnome-themes-standard_3.22.3-3ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1748122/+attachment/5051185/+files/bionic_gnome-themes-standard_3.22.3-3ubuntu2.debdiff
** Patch added: "bionic_open-vm-t
Thanks for noticing that, wrong debdiff attached. Sorry about that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748122
Title:
incorrect tools.conf template is shipped with Ubuntu
To manage notif
** No longer affects: unity-control-center (Ubuntu)
** No longer affects: unity-control-center (Ubuntu Xenial)
** No longer affects: unity-control-center (Ubuntu Artful)
** No longer affects: unity-control-center (Ubuntu Bionic)
--
You received this bug notification because you are a member of
Of course. I will do that.
Thanks Christian!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748122
Title:
incorrect tools.conf template is shipped with Ubuntu
To manage notifications about this bu
Christian, debian has merged the proposal [1].
I believe we're good to merge it to Ubuntu.
Thanks!
[1] https://github.com/bzed/pkg-open-vm-
tools/commit/34538a58a8ed705e09f0dcf8c1627319efba49fd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
SRU proposal for Artful.
** Patch added: "artful_open-vm-tools_10.0.7-3227872-5ubuntu1~17.10.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1748122/+attachment/5055676/+files/artful_open-vm-tools_10.0.7-3227872-5ubuntu1~17.10.1.debdiff
--
You received this bug notifi
SRU proposal for Xenial.
** Patch added: "xenial_open-vm-tools_10.0.7-3227872-5ubuntu1~16.04.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1748122/+attachment/5055674/+files/xenial_open-vm-tools_10.0.7-3227872-5ubuntu1~16.04.2.debdiff
--
You received this bug notifi
SRU proposal for Trusty.
** Patch added: "trusty_open-vm-tools_9.4.0-1280544-5ubuntu6.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1748122/+attachment/5055673/+files/trusty_open-vm-tools_9.4.0-1280544-5ubuntu6.3.debdiff
--
You received this bug notification because
Seth: those values were somehow calculated from a number of runs. A
single pyperformance benchmark run took ~20 minutes and I repeated each
of them 3 times.
I still have the 'raw' outputs of pyperformance if needed. From those I
see that there are at least 3 values for each test and also there is
Xenial pyperformance results with -fstack-protector-strong changed to
-fstack-protector.
** Attachment added: "xenial-fsp-01.json"
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+attachment/5015696/+files/xenial-fsp-01.json
--
You received this bug notification because you
SRU proposal for Xenial.
** Patch added: "xenial_sysstat_11.2.0-1ubuntu0.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/1720627/+attachment/5019330/+files/xenial_sysstat_11.2.0-1ubuntu0.2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs
SRU proposal for Artful.
** Patch added: "artful_sysstat_11.5.7-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/1720627/+attachment/5019321/+files/artful_sysstat_11.5.7-1ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
SRU proposal for Zesty.
** Patch added: "zesty_sysstat_11.4.3-1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/1720627/+attachment/5019322/+files/zesty_sysstat_11.4.3-1ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Description changed:
+ [Impact]
+
+ * With long entries in mtab tools utilizing the get_filesystem_nr and
read_filesystem functions cause a segfault due to a fact that they don't
+ check strchr result for being null.
+
+ [Test Case]
+
+ *
+
+ [Regression Potential]
+
+ * The fix is pre
debdiff proposal for Bionic.
** Patch added: "bionic_sysstat_11.6.0-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/1720627/+attachment/5019336/+files/bionic_sysstat_11.6.0-1ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs
SRU proposal for Xenial.
** Patch added: "xenial_sysstat_11.2.0-1ubuntu0.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/1720627/+attachment/5019351/+files/xenial_sysstat_11.2.0-1ubuntu0.2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs
SRU proposal for Artful.
** Description changed:
[Impact]
- * With long entries in mtab tools utilizing the get_filesystem_nr and
read_filesystem functions cause a segfault due to a fact that they don't
+ * With long entries in mtab tools utilizing the get_filesystem_nr and
read_filesyst
SRU proposal for Zesty.
** Patch added: "zesty_sysstat_11.4.3-1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/1720627/+attachment/5019350/+files/zesty_sysstat_11.4.3-1ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I've just finished testing version 0.9.7-2ubuntu1.
With that version update finishes cleanly.
Thanks!
** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done verification-done-artful
--
You received this bug notification because you are a member of Ubunt
I was also able to reproduce it on 17.10 _on metal_.
For some reason the launcher hides for good and I was not able to
display it again on VM (Virtualbox).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
The /usr/share/themes/HighContrast/index.theme sets Adwaita as the
default icon theme for the HighContrast team.
Unfortunately some of the needed icons are missing in that team. I
wonder why the HighContrast icon theme is not used here by default?
Another observation: as visible in David's screen
The /usr/share/themes/HighContrast/index.theme sets Adwaita as the
default icon theme for the HighContrast theme.
Unfortunately some of the needed icons are missing. I wonder why the
HighContrast icon theme is not used here by default?
Another observation: as visible in David's screenshot there a
SRU proposal for Xenial.
** Description changed:
+ [Impact]
+
+ * Switching to HighContrast theme in System Settings/Appearance results in
missing icons for some of the panels in System Settings.
+ * Only Xenial is affected of the currently supported releases.
+ * Current development release
** Description changed:
[Impact]
- * Switching to HighContrast theme in System Settings/Appearance results in
missing icons for some of the panels in System Settings.
- * Only Xenial is affected of the currently supported releases.
- * Current development release is not affected.
+ * Swi
Public bug reported:
On a Xenial installation after upgrading to the HWE 4.13.0-32-generic
kernel it is not possible to use mount.cifs with -o vers=x.y different
than 1.0.
Steps to reproduce:
1. Setup a local Samba share.
2. Run:
mount.cifs -o user=,vers=2.0 //localhost/theshare/ /mnt/theshare
(p
As discussed with cascardo I tested the mainline builds from [1].
After some tests the results were:
v4.12.14 - good
v4.13 - bad
So the regression seems to be introduced in v4.13.
[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/
--
You received this bug notification because you are a member
dmesg output after reproducing the issue with
echo 7 > /proc/fs/cifs/cifsFYI
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+attachment/5046387/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Surprisingly it works perfectly fine for 4.15.0-041500-generic.
I have tested vers= parameter from 1.0 to 3.0 - no issues at all.
I went forward and tested v4.14 - it is not affected by the issue as
well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Description changed:
On a Xenial installation after upgrading to the HWE 4.13.0-32-generic
kernel it is not possible to use mount.cifs with -o vers=x.y different
than 1.0.
Steps to reproduce:
1. Setup a local Samba share.
2. Run:
- mount.cifs -o user=,vers=2.0 //localhost/theshar
Conclusion after correcting the parameters in my test procedure:
v4.10 - good
v4.11 - bad
v4.15 - bad
I'm performing a bisect between v4.10 and v4.11.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/174
Added updated dmesg (with verbose error message).
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+attachment/5047511/+files/dmesg_latest.log
** Attachment removed: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+atta
Looks like I've been mislead by the man page of mount.cifs and
linux/fs/cifs/connect.c which state:
man mount.cifs:
vers=
SMB protocol version. Allowed values are:
· 1.0 - The classic CIFS/SMBv1 protocol. This is the
default.
4.13 kernel code:
pr_warn("No dialect specifi
Added updated dmesg (with verbose error message).
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+attachment/5047510/+files/dmesg_latest.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Public bug reported:
Samba version used:
4.3.9+dfsg-0ubuntu0.16.04.2
Steps to reproduce:
1. Configure a samba share with inherited permissions:
[share1]
path = /srv/share1
browseable = yes
read only = no
guest ok = no
inherit permissions = yes
2. Create a directory under that share:
cd
Public bug reported:
Samba version used:
4.3.9+dfsg-0ubuntu0.16.04.2
Steps to reproduce:
1. Configure a samba share with inherited permissions:
[share1]
path = /srv/share1
browseable = yes
read only = no
guest ok = no
create mask = 0770
force create mode = 0660
directory mask = 2770
** Description changed:
- [Impact]
+ [Impact]
There are some unlinked calls to libGL.so.1 undetected in the build process
because of using libepoxy. Running an application that does not depend on
libgl1 (directly or indirectly) may lead to aborting the process with an
undefined reference to
Yakkety SRU proposal with fixed version number.
** Patch removed: "yakkety_gtk+3.0_3.20.9-1ubuntu3.debdiff"
https://bugs.launchpad.net/hundredpapercuts/+bug/1550983/+attachment/4808140/+files/gtk+3.0_3.20.9-1ubuntu3.debdiff
** Patch added: "yakkety_gtk+3.0_3.20.9-1ubuntu2.1.debdiff"
https
f the one given by -h option).
If a port number is given (e.g. server2:631) the commands work as
expected.
** Affects: cups (Ubuntu)
Importance: Medium
Assignee: Dariusz Gadomski (dgadomski)
Status: New
** Tags: sts
** Changed in: cups (Ubuntu)
Importance: Undecided =>
SRU proposal for Trusty.
** Patch added: "trusty_cups_1.7.2-0ubuntu1.8.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1665018/+attachment/4819939/+files/trusty_cups_1.7.2-0ubuntu1.8.debdiff
** Tags added: sts-sponsor
--
You received this bug notification because you are a memb
Public bug reported:
Support for config files has been dropped upstream in 2012 (however
version shipped with Trusty still supports it), but the latest versions
(including Xenial and Zesty) still mention it in the docs and in the
legacy /etc/init/bluetooth.conf file.
** Affects: bluez (Ubuntu)
** Summary changed:
- Dropped rfcomm.conf still mentioned
+ Deprecated rfcomm.conf still mentioned
** Description changed:
Support for config files has been dropped upstream in 2012 (however
version shipped with Trusty still supports it), but the latest versions
(including Xenial and Zest
Patch proposal for Zesty.
** Tags added: sts sts-sponsor
** Patch added: "zesty_bluez_5.43-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+attachment/4841667/+files/zesty_bluez_5.43-0ubuntu2.debdiff
--
You received this bug notification because you are a memb
** Description changed:
+ [Impact]
+
+ * The package contains misleading documentation mentioning the use of
+ /etc/bluetooth/rfcomm.conf for rfcomm setup while the support for config
+ file has been dropped after 14.04 release. I have directly received a
+ question about it from a user mislead
** Changed in: gtk+3.0 (Ubuntu)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550983
Title:
Fails to start with "Couldn't
This bug is fixed in Zesty by latest sync with Debian (gtk+3.0
(3.22.7-2)).
** Changed in: gtk+3.0 (Ubuntu)
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/15509
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550983
Title:
Fails to start with "Couldn't open libGL.so.1" (missing dependency?)
To manage notifications about this bug go to:
ht
** Description changed:
+ [Impact]
+ There are some unlinked calls to libGL.so.1 undetected in the build process
because of using libepoxy. Running an application that does not depend on
libgl1 (directly or indirectly) may lead to aborting the process with an
undefined reference to libGL.so.1.
SRU proposal for Yakkety - backport from Zesty.
** Patch added: "gtk+3.0_3.20.9-1ubuntu3.debdiff"
https://bugs.launchpad.net/hundredpapercuts/+bug/1550983/+attachment/4808140/+files/gtk+3.0_3.20.9-1ubuntu3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs,
SRU proposal for Xenial - backport from Zesty.
** Patch added: "xenial_gtk+3.0_3.18.9-1ubuntu3.2.debdiff"
https://bugs.launchpad.net/hundredpapercuts/+bug/1550983/+attachment/4808141/+files/xenial_gtk+3.0_3.18.9-1ubuntu3.2.debdiff
** Tags added: sts-sru
--
You received this bug notification
I have tested this several times with different network settings and can
see that ubiquity plays quite nicely with resolvconf. That includes
static (e.g. dns-nameservers entries in /e/n/interfaces) and dhcp cases.
The only problem is the issue identified by Newton Liu above - the
resolv.conf gets
Fix proposal for zesty.
** Tags added: sts sts-sponsor
** Patch added: "zesty_ubiquity_17.04.8.debdiff"
https://bugs.launchpad.net/nvidia/+bug/1646585/+attachment/4835373/+files/zesty_ubiquity_17.04.8.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
301 - 400 of 821 matches
Mail list logo
