Yes, definitely.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749289
Title:
Installer stops after pressing Cancel on Select a language screen
during OEM install
To manage notifications about
Micheal: yes, that is expected after the patch has been applied. I just
filled the gaps the installer was expecting. Before the config just died
with AttributeError caused by calling a unimplemented method. Hence, my
understanding was that this is the original intention.
Simply hiding the cancel
** Attachment added: "SH_HL_08_Step1_F029.png"
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1793485/+attachment/5190922/+files/SH_HL_08_Step1_F029.png
** Description changed:
Regression between 8:6.8.9.9-7ubuntu5.9 and 8:6.8.9.9-7ubuntu5.12.
Test case:
1. Download the
Public bug reported:
Regression between 8:6.8.9.9-7ubuntu5.9 and 8:6.8.9.9-7ubuntu5.12.
Test case:
1. Download the attached pngs.
2. Run:
/usr/bin/convert -limit memory 512MiB -limit map 0MiB -limit file 10 -delay 16
-loop 0 -coalesce -deconstruct ./*.png ./output.gif
Expected result:
Process
I have just verified it and don't see any issues.
I tested all use cases listed in the description on metal and in a VM
(VirtualBox).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786933
Title:
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786933
Title:
New upstream
Michael, I've just tried again today. I have up waiting after 60
minutes. How long does it take in your case?
FWIW I used a vm (kvm) for testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789920
** Attachment added: "questions.dat"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1789920/+attachment/5187542/+files/questions.dat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789920
** Attachment added: "templates.dat"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1789920/+attachment/5187543/+files/templates.dat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789920
As advised by xnox I have retried the installation with adding apt-
setup/proposed=true.
The result was identical - after rebooting to perform the oem
configuration the boot process stucks.
Attaching installer logs.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "lsb-release"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1789920/+attachment/5187539/+files/lsb-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789920
** Attachment added: "initial-status.gz"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1789920/+attachment/5187540/+files/initial-status.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "status"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1789920/+attachment/5187536/+files/status
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789920
Title:
** Attachment added: "media-info"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1789920/+attachment/5187538/+files/media-info
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789920
** Attachment added: "hardware-summary"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1789920/+attachment/5187541/+files/hardware-summary
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1789920/+attachment/5187535/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789920
Title:
** Attachment added: "partman"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1789920/+attachment/5187537/+files/partman
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789920
Title:
Reported bug #1789920.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749289
Title:
Installer stops after pressing Cancel on Select a language screen
during OEM install
To manage notifications
Public bug reported:
I have downloaded the 18.04.1 iso with alternative (legacy) installer.
I took the following steps:
1. Booted from the ISO (using BIOS, haven't tested EFI).
2. F4 -> set the OEM mode.
3. Proceed through the initial setup.
4. Agree to reboot for the OEM setup.
5. Observe
Hello Łukasz, I was not able to verify this on bionic. The boot stucks
even before I had the chance to install the -proposed version of
ubiquity.
Steps I took:
1. Use the alternative iso with legacy installer.
2. F4 -> set OEM mode
3. Go through the initial setup.
4. Reboot to perform the OEM
** Description changed:
[Impact]
Pressing Cancel during Ubuntu 16.04.3 Server installation after OEM
install and after running oem-config-prepare aborts the installation.
The behaviour is different from a regular Ubuntu 16.04.3 Server
installation (without OEM) where the option at
Verified on xenial with 3.18.3-0ubuntu2.2.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Verified on bionic with 3.28.3-0ubuntu18.04.1.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782152
Title:
GDM
Dariusz Gadomski has proposed merging
~dgadomski/ubuntu/+source/gdm3/+git/lp1782152:unblock-sigusr1 into
~ubuntu-desktop/ubuntu/+source/gdm3:ubuntu/bionic.
Commit message:
[ Alberto Milone ]
* ubuntu_nvidia_prime.patch:
- Run scripts for Prime before and after Gdm sessions (LP: #1778011
Seb, Xenial is also affected (as long as the user switches to gdm) and
this patch fixes it, so it's worth having it.
I already talked to Eric (slashd) about it - he's going to drive it
forward.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Dariusz Gadomski has proposed merging
~dgadomski/ubuntu/+source/gdm3/+git/lp1782152:bionic into
~ubuntu-desktop/ubuntu/+source/gdm3:ubuntu/bionic.
Commit message:
[ Alberto Milone ]
* ubuntu_nvidia_prime.patch:
- Run scripts for Prime before and after Gdm sessions (LP: #1778011).
[ Dariusz
Although I originally shared Daniel's doubt, I reported it to Debian and
shared the patch (bug linked above).
** Bug watch added: Debian Bug tracker #905277
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905277
** Also affects: gdm3 (Debian) via
xnox: sadly there was a misunderstanding - I didn't take any actions about it
since the merge request was marked "on hold", but I hit some issues with the
installer after removing fcntl.ioctl(0, termios.TIOCSCTTY, 1)
The terminal debconf tools were failing without it.
I came up with 2 other
** No longer affects: nvidia-graphics-drivers-384 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721988
Title:
Ubuntu 17.10 full disk encryption + Nvidia drivers not booting
To manage
Thanks @goingwc, I have managed to reproduce it here so I can use my own
plymouth log. Turns out I couldn't get even 18.04 working correctly,
because I had integrated GPU enabled in my motherboard settings
(i7-6700K with HD 530) despite nvidia being set to "primary GPU". I had
to disable the
Hi,
Could anyone that has it working on 18.04 add plymouth:debug to their kernel
cmdline, reboot and share the /var/log/plymouth-debug.log?
I'm looking into this, but also experience the issue on 18.04. I'm
curious where the difference comes from.
Thanks!
--
You received this bug notification
SRU proposal for Xenial.
** Patch added: "xenial_gdm3_3.18.3-0ubuntu2.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782152/+attachment/5166679/+files/xenial_gdm3_3.18.3-0ubuntu2.2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
SRU proposal for Bionic.
** Patch added: "bionic_gdm3_3.28.2-0ubuntu1.4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782152/+attachment/518/+files/bionic_gdm3_3.28.2-0ubuntu1.4.debdiff
** Description changed:
https://gitlab.gnome.org/GNOME/gdm/issues/399
- ---
+
Patch for Cosmic.
** Patch added: "cosmic_gdm3_3.28.2-3ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782152/+attachment/517/+files/cosmic_gdm3_3.28.2-3ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I confirm - the issue is gone after testing a build with the upstream
patch applied.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782152
Title:
GDM blocks SIGUSR1 used in PAM scripts
To manage
** Attachment added: "session.py"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782152/+attachment/5164919/+files/session.py
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782152
Title:
Updated scripts for the reproducer.
** Attachment removed: "auth.py"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782152/+attachment/5164561/+files/auth.py
** Attachment removed: "session.py"
Upstream bug: https://gitlab.gnome.org/GNOME/gdm/issues/399
(not adding via "also affects projects" since LP does not parse gitlab
bugtracker yet).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport-collect 1782152 replies with "No additional information
collected" message.
But this issue is reproducible with any clean bionic desktop install
(since GDM needs to be the login managed).
It is NOT reproducible if I switch back to lightDM.
--
You received this bug notification because
** Attachment added: "session.py"
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1782152/+attachment/5164562/+files/session.py
** Summary changed:
- GDM block SIGUSR1 used in PAM scripts
+ GDM blocks SIGUSR1 used in PAM scripts
--
You received this bug notification because you are a
Adding scripts for reproducer.
** Description changed:
In case of the following scenario:
1. PAM configured to run auth and session with pam_exec scripts synchronizing
via SIGUSR1
2. Using GDM as the login manager causes SIGUSR1 never reaches the target
scripts.
Workaround:
a) Use
Public bug reported:
In case of the following scenario:
1. PAM configured to run auth and session with pam_exec scripts synchronizing
via SIGUSR1
2. Using GDM as the login manager causes SIGUSR1 never reaches the target
scripts.
Workaround:
a) Use SIGUSR2 in the scripts.
b) Comment out
** Changed in: unity-settings-daemon (Ubuntu)
Status: Invalid => In Progress
** Changed in: hwdata (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have repeated the tests for the second part of patch as well -
everything went as expected.
Although I haven't been able to hit the undefined guest scenario before.
I'll make a couple of attempts more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can confirm. With the patch applied all guests are being shutdown
correctly and the "Failed to determine state of guest" message is gone.
Tested for PARALLEL=2, 5, 10 for 40 guests.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've just finished verification for the following versions:
artful: 3.6.0-1ubuntu6.5
xenial: 1.3.1-1ubuntu10.21
No issues found in the scope of the test case (from the bug
description).
** Tags removed: verification-needed-artful verification-needed-xenial
** Tags added: verification-done-artful
Christian, works perfectly fine here as well (tested from the ppa).
I notice the "Failed to determine..." messages, but nonetheless the guests are
correctly shut down in a jiffie.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
After examining raw EDID data from 2 different LG TVs I can see that both of
them set bytes 21 and 22 of the EDID data in a wrong way.
They both state that the display size is 160x90 cm which in turn corresponds to
a approximately 72" diagonal.
So unity-settings-daemon does its job correctly
Seems that oem-config-firstboot ignores the question that should be presented
to the user on unfinished installation, because of the following line in
/usr/bin/ubiquity:
125: fcntl.ioctl(0, termios.TIOCSCTTY, 1)
It steals the terminal from the calling script, so the question is not
presented
log from verification on Xenial.
** Attachment added: "xenial_libvirt-guests.log.gz"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1688508/+attachment/5078252/+files/libvirt-guests.log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Goldstar seems to be a former name of LG (before the Lucky-Goldstar
merge).
I've made a pull request upstream to update it:
https://github.com/vcrhonek/hwdata/pull/1
** Also affects: unity-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Public bug reported:
After connecting a LG 49UB850T-DA TV the following information is
displayed in the unity-control-center: Goldstar Company Ltd 72"
It's misleading since neither the company name nor the diagonal matches.
** Affects: hwdata (Ubuntu)
Importance: Undecided
Status:
Another thing is the diagonal length calculation. From my quick look
this is done based on EDID data in unity-settings-daemon.
** Summary changed:
- Incorrect information displayed in unity-control-center
+ Incorrect information about display shown in unity-control-center
--
You received this
SRU proposal for Xenial.
** Patch added: "xenial_libvirt_1.3.1-1ubuntu10.20.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1688508/+attachment/5063490/+files/xenial_libvirt_1.3.1-1ubuntu10.20.debdiff
--
You received this bug notification because you are a member of Ubuntu
SRU proposal for Artful.
** Patch added: "artful_libvirt_3.6.0-1ubuntu6.4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1688508/+attachment/5063489/+files/artful_libvirt_3.6.0-1ubuntu6.4.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: libvirt (Ubuntu Zesty)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688508
Title:
libvirt-guests.sh fails to shutdown guests in parallel
To
The patch has been accepted upstream:
https://libvirt.org/git/?p=libvirt.git;a=commit;h=ff02d1af4041ea4cf6bea68aac66d93a970e92f1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688508
Title:
Verified
Trusty 2:9.4.0-1280544-5ubuntu6.4.
Works as expected.
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty
** Tags removed: verification-done
--
You received this bug notification because you are a member of Ubuntu
Turns out Trusty config requires a path to logfile explicitly stated in
tools.conf as there is no code for figuring out a default path in that
version.
Uploading new SRU proposal for Trusty.
** Changed in: open-vm-tools (Ubuntu Trusty)
Status: Fix Committed => In Progress
** Tags
Managed to successfully verify the following:
artful - 2:10.1.10-3ubuntu0.1 - OK
xenial - 2:10.0.7-3227872-5ubuntu1~16.04.2 - OK
** Tags removed: verification-needed-artful verification-needed-xenial
** Tags added: verification-done-artful verification-done-xenial
--
You received this bug
I have just verified this in my env earlier used to reproduce the issue.
Results:
artful - 3.22.3-1ubuntu2 - verified
xenial - 3.18.0-2ubuntu2 - verified
** Tags removed: verification-needed verification-needed-artful
verification-needed-xenial
** Tags added: verification-done
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
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
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
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
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
** 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
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
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:
** 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
** 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.
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"
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
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
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
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
The fix has been merged upstream, preparing new debdiffs reflecting
that.
** Patch removed: "xenial_gnome-themes-standard_3.18.0-2ubuntu2.debdiff"
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
** 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
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
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
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
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.
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"
** 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
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
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,
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
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
** 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.
+ *
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
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
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
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.
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
I've just verified that the segfault is fixed in the following releases:
bionic: 11.6.0-1ubuntu2
artful: 11.5.7-1ubuntu2
zesty: 11.4.3-1ubuntu1
xenial: 11.2.0-1ubuntu0.2
** Tags removed: verification-needed verification-needed-artful
verification-needed-xenial verification-needed-zesty
** Tags
Looks like I can't link another debian bug in a regular manner, so adding the
link here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883863
I also shared the Ubuntu bionic patch with Debian.
** Bug watch added: Debian Bug tracker #883863
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,
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
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
301 - 400 of 798 matches
Mail list logo
