tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-83.106-lowlatency/fozzie__4.4.0-83.106__2017-06-27_21-25-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: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri
(mhcerri)
** Changed in: kernel-sru-workflow/prepare-package-meta
** Changed in: ubuntu-terminal-app (Ubuntu)
Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625074
Title:
[MIR]
tests ran: 20, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63~16.04.1-generic/ms10-35-mcdivittB0-kernel__4.8.0-58.63~16.04.1__2017-06-27_20-33-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
With latest proposed kernel (4.4.0-83.106) Scilab does not crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699772
Title:
linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.10.0-26.30~16.04.1-generic/rizzo__4.10.0-26.30~16.04.1__2017-06-27_21-20-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@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
Bugs, which is subscribed to Ubuntu.
tests ran: 20, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63~16.04.1-generic/hainzel__4.8.0-58.63~16.04.1__2017-06-27_20-34-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tested this kernel with Scilab (see bug 1699772). Scilab does not
crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700541
Title:
linux: 4.4.0-83.106 -proposed tracker
To manage
*** This bug is a duplicate of bug 1700373 ***
https://bugs.launchpad.net/bugs/1700373
Please see https://bugs.launchpad.net/ubuntu/+source/intel-
microcode/+bug/1700373/comments/12
Unfortunately it looks like 14.04 will not receive any new intel-
microcode updates.
For 14.04 users instead
tests ran: 34, failed: 3;
http://kernel.ubuntu.com/testing/4.4.0-83.106-lowlatency/amaura__4.4.0-83.106__2017-06-27_20-52-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
"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
Closing this as it appears to have been fixed in newer versions of the
4.8 kernel.
** Changed in: intel-microcode (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
tests ran: 19, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-58.63-generic/pepe__4.8.0-58.63__2017-06-27_20-19-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: 19, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-83.106-generic/fozzie__4.4.0-83.106__2017-06-27_20-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/1700541
tests ran: 9, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-83.106-generic/ms10-34-mcdivittB0-kernel__4.4.0-83.106__2017-06-27_20-34-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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 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 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
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.10.0-26.30~16.04.1-generic/rizzo__4.10.0-26.30~16.04.1__2017-06-27_20-49-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700834
Title:
Intel i40e PF reset under load
To manage notifications about this
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-83.106-generic/archytas__4.4.0-83.106__2017-06-27_19-53-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: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-83.106-lowlatency/amaura__4.4.0-83.106__2017-06-27_20-38-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I also can't see the error after installing systemd (ubuntu-core-
launcher and all its deps, actually).
Original version shipped with trusty:
http://pastebin.ubuntu.com/24965690/
Now with upgrades enabled, trying an upgrade:
http://pastebin.ubuntu.com/24965703/
I note, however, that systemd
I also can't see the error after installing systemd (ubuntu-core-
launcher and all its deps, actually).
Original version shipped with trusty:
http://pastebin.ubuntu.com/24965690/
Now with upgrades enabled, trying an upgrade:
http://pastebin.ubuntu.com/24965703/
I note, however, that systemd
tests ran: 16, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-83.106-generic/onza__4.4.0-83.106__2017-06-27_20-27-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
** Description changed:
- When attempting to run doomsday 1.15.8-3 on Ubuntu 17.04 it immediately
- segfaults.
+ [SRU]
+ When attempting to run doomsday 1.15.8-3 on Ubuntu 17.04 it immediately
segfaults.
This (and a separate segfault which happens when attempting to start a
- new game [1])
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1700834
and then change the status of the bug to 'Confirmed'.
If, due to the
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Invalid
** Changed in:
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-83.106-generic/amaura__4.4.0-83.106__2017-06-27_20-13-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
** Tags added: gnome-17.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696395
Title:
gnome-control-center crashed with SIGSEGV in um_carousel_select_item()
To manage notifications about this
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.10.0-26.30~16.04.1-generic/rizzo__4.10.0-26.30~16.04.1__2017-06-27_20-19-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
tests ran: 20, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63~16.04.1-generic/secchi__4.8.0-58.63~16.04.1__2017-06-27_19-35-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The review tools are being migrated to snaps. The deb format is always
out of date and the store uses a VCS checkout.
** Affects: click-reviewers-tools (Ubuntu)
Importance: Undecided
Status: Fix Released
--
You received this bug notification because you are a
Debdiff bringing in the patches resolving the segfaults to the zesty
package.
** Patch added: "zesty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/doomsday/+bug/1700822/+attachment/4904267/+files/zesty.debdiff
--
You received this bug notification because you are a member of Ubuntu
tests ran: 6, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63-generic/gonzo__4.8.0-58.63__2017-06-27_19-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/1700533
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63~16.04.1-generic/hainzel__4.8.0-58.63~16.04.1__2017-06-27_20-11-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63~16.04.1-generic/ms10-35-mcdivittB0-kernel__4.8.0-58.63~16.04.1__2017-06-27_20-08-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The attachment "zesty.debdiff" seems to be a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you
Removing packages from artful:
click-reviewers-tools 0.46 in artful
click-reviewers-tools 0.46 in artful amd64
click-reviewers-tools 0.46 in artful arm64
click-reviewers-tools 0.46 in artful armhf
click-reviewers-tools 0.46 in
Public bug reported:
ubiquity fails to install grub-efi
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.3
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
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
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-83.106-generic/ms10-34-mcdivittB0-kernel__4.4.0-83.106__2017-06-27_19-16-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
SRU Justification:
Impact:
Using an Intel i40e network device, under heavy traffic load with
TSO enabled, the device will spontaneously reset itself and issue errors
similar to the following:
Jun 14 14:09:51 hostname kernel: [4253913.851053] i40e :05:00.1: TX
test the patch from https://bugs.freedesktop.org/show_bug.cgi?id=99410
** Bug watch added: freedesktop.org Bugzilla #99410
https://bugs.freedesktop.org/show_bug.cgi?id=99410
** Changed in: libinput (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-83.106-generic/amaura__4.4.0-83.106__2017-06-27_19-56-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: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in:
Other discussions
# systemd or sysv ??
Dariusz:
Do we need to port it to systemd or are sysv script is fine?
Christian:
In general sysv is fine, but there are a few issues due using the "old" calls
e.g. if you have PCP running in a container it will collide on the Host (no
service start,
tests ran: 16, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-83.106-generic/onza__4.4.0-83.106__2017-06-27_19-54-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
TJ: ping? this is still unverified..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655752
Title:
Xorg crashed with SIGABRT in
libinput_device_config_tap_get_finger_count()
To manage
Public bug reported:
This bug is for tracking the 4.11.0-1003.3 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Affects:
tests ran: 19, failed: 2;
http://kernel.ubuntu.com/testing/4.4.0-83.106-generic/fozzie__4.4.0-83.106__2017-06-27_19-09-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
Public bug reported:
duno
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: docker.io 1.12.6-0ubuntu4
ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
Uname: Linux 4.10.0-24-generic i686
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: i386
Date: Tue Jun 27 21:56:29 2017
tests ran: 16, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63-generic/pepe__4.8.0-58.63__2017-06-27_19-52-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
Hello everyone,
Kuba,
Could you please show more details on what is happening in your case ?
Could you follow what I did in my previous comments, to show more logs
from the nfs service(s) failure(s) ? Could you reproduce the issue - the
startup problem - and show me a "systemctl status" on every
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.10.0-26.30~16.04.1-generic/rizzo__4.10.0-26.30~16.04.1__2017-06-27_19-48-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
tests ran: 64, failed: 2;
http://kernel.ubuntu.com/testing/4.8.0-58.63-generic/ms10-35-mcdivittB0-kernel__4.8.0-58.63__2017-06-27_19-22-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hunh. How odd... I can't imagine that there would be something
particular to this system that is causing the crash. As you requested:
skunk@darkstar:/tmp/krb5-auth-dialog-3.20.0/_build/src$ G_MESSAGES_DEBUG=all
./krb5-auth-dialog -a
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG:
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63-generic/hainzel__4.8.0-58.63__2017-06-27_19-28-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
The following, must first be addressed before this package would be accepted
into main :
- tracking down upstream maintenance
- fix segfaulting binaries
- evaluating all dependencies
- base dep8 tests included
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Matthew - Do you have an idea on how we might word what '-d' will now
do? Without any outside input I might use something like "Upgrade to the
development release of Ubuntu if running the release preceding it".
Thanks!
** Changed in: update-manager (Ubuntu)
Status: New => Triaged
**
Public bug reported:
The -d switch for update-manager is documented as 'Check if upgrading to
the latest devel release is possible'. This implies that no matter what
release you are running the -d switch check if you can upgrade to the
devel release (Artful right now) however, this isn't
*** 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
Checking this out now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699065
Title:
package sssd-common 1.11.8-0ubuntu0.6 failed to install/upgrade:
subprocess new pre-removal script returned
tests ran: 34, failed: 3;
http://kernel.ubuntu.com/testing/4.4.0-83.106-generic/amaura__4.4.0-83.106__2017-06-27_19-19-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
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700659
*** 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
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"
Checking this out now.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to sssd in Ubuntu.
https://bugs.launchpad.net/bugs/1699065
Title:
package sssd-common 1.11.8-0ubuntu0.6 failed to install/upgrade:
subprocess new pre-removal
*** 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:
** Description changed:
[Availability]
Available:
pcp | 3.11.10 | artful/universe | source, amd64, arm64, armhf, i386,
ppc64el, s390x
[Rationale]
This is a valuable source of metrics for large deployments. There are
numerous users with large installations interested in
*** This bug is a duplicate of bug 1605259 ***
https://bugs.launchpad.net/bugs/1605259
** This bug has been marked a duplicate of bug 1605259
do-release-upgrade --sandbox fails
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We want to provide users the safest upgrade path from one release to
another as such we going to keep it so that the '-d' switch will only
take you to the development release of Ubuntu if you are running the
release immediately before the development one. If testers want to test
the upgrade path
I verified that there are no reports for this issue on
https://errors.ubuntu.com/problem/c7ba5238c01adbb8a245dfc02bac9633a362ea44
for 17.04 after the 3.22.7-0ubuntu3.17.04.2 update. On 17.10, we haven't
gotten any new reports of this bug since early May.
This issue is also a bit odd because it's
tests ran: 16, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63-generic/pepe__4.8.0-58.63__2017-06-27_19-26-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
** Description changed:
[Availability]
Available:
pcp | 3.11.10 | artful/universe | source, amd64, arm64, armhf, i386,
ppc64el, s390x
+
[Rationale]
This is a valuable source of metrics for large deployments. There are
numerous users with large installations interested in
Um, I wasn't able to verify the original bug because both moon-buggy and
hello-snaps did show up in Installed with the current zesty version
(3.22.7-0ubuntu3.17.04.2)
But there were two improvements in the new SRU (3.22.7-0ubuntu3.17.04.5) so I'm
going to mark this as verified.
- moon-buggy now
** Changed in: doomsday (Debian)
Status: Unknown => 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/1700822
Title:
Doomsday segfaults when attempting to start on Ubuntu 17.04
To
tests ran: 20, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-83.106-generic/archytas__4.4.0-83.106__2017-06-27_18-51-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
Running update-manager -d now first displays a dialog saying "However,
Ubuntu 17.10 is now available (you have 17.04)." After you click the
"Upgrade..." button another dialog is displayed which talks about Artful
Aardvark being in development and not to install it on production
systems. Do you
Check some debug options that can be enabled on-the-fly, taken from bug
https://bugs.launchpad.net/ubuntu/karmic/+source/linux/+bug/406466/comments/8.
In particular:
echo 1 > /proc/fs/cifs/traceSMB
showed that the missing files/directories are sent to the client when
"ls -l /mountpoint" is
smbclient sees all files without issues, so I'm changing the affected
package
** Package changed: samba (Ubuntu) => cifs-utils (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572132
Title:
smbclient sees all files without issues, so I'm changing the affected
package
** Package changed: samba (Ubuntu) => cifs-utils (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Check some debug options that can be enabled on-the-fly, taken from bug
https://bugs.launchpad.net/ubuntu/karmic/+source/linux/+bug/406466/comments/8.
In particular:
echo 1 > /proc/fs/cifs/traceSMB
showed that the missing files/directories are sent to the client when
"ls -l /mountpoint" is
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:
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63~16.04.1-generic/secchi__4.8.0-58.63~16.04.1__2017-06-27_19-15-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.10.0-26.30-generic/rizzo__4.10.0-26.30__2017-06-27_19-18-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/1700528
We have tested and confirm it works as expected. Partial MAAS CI logs
for xenial can be seen here [1]. Zesty and Yakkety were tested manually.
[1]: http://pastebin.ubuntu.com/24964664/
** Tags added: verification-done-xenial verification-done-yakkety
verification-done-zesty
--
You received
Public bug reported:
[Availability]
Available:
pcp | 3.11.10 | artful/universe | source, amd64, arm64, armhf, i386,
ppc64el, s390x
[Rationale]
This is a valuable source of metrics for large deployments. There are numerous
users with large installations interested in having it in fully
Action items :
- tracking down upstream maintenance
- fix segfaulting binaries
- evaluating all dependencies
- base dep8 tests included
** Tags added: sts
** Changed in: pcp (Ubuntu)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
You received this bug notification because you
*** This bug is a duplicate of bug 1605259 ***
https://bugs.launchpad.net/bugs/1605259
** This bug is no longer a duplicate of bug 564053
do-release-upgrade --sandbox fails ("submount of systemdir")
** This bug has been marked a duplicate of bug 1605259
do-release-upgrade --sandbox
*** This bug is a duplicate of bug 1605259 ***
https://bugs.launchpad.net/bugs/1605259
** This bug has been marked a duplicate of bug 1605259
do-release-upgrade --sandbox fails
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
And the moment I created another entry on C:\, one of the missing
directories showed up on the linux side :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1572132
Title:
SMB driver
Amr, thanks. If this is accepted as an update, please test it on GNOME
Shell too.
I don't intend to enable the appindicator because that feature was
removed in gpaste 3.24.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1605259 ***
https://bugs.launchpad.net/bugs/1605259
** This bug is no longer a duplicate of bug 564053
do-release-upgrade --sandbox fails ("submount of systemdir")
** This bug has been marked a duplicate of bug 1605259
do-release-upgrade --sandbox
Curious indeed. I can reproduce this on xenial mounting a share from a
windows 7 enterprise VM:
With vers 2.1 (same with 2.0):
root@nsn7:~# l /c
total 3,0G
drwxr-xr-x 2 andreas andreas 4,0K Jun 12 16:58 .
drwxr-xr-x 33 rootroot4,0K Jun 27 15:56 ..
-rwxr-xr-x 1 andreas andreas 24 Jun
Curious indeed. I can reproduce this on xenial mounting a share from a
windows 7 enterprise VM:
With vers 2.1 (same with 2.0):
root@nsn7:~# l /c
total 3,0G
drwxr-xr-x 2 andreas andreas 4,0K Jun 12 16:58 .
drwxr-xr-x 33 rootroot4,0K Jun 27 15:56 ..
-rwxr-xr-x 1 andreas andreas 24 Jun
And the moment I created another entry on C:\, one of the missing
directories showed up on the linux side :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572132
Title:
SMB driver (SMBv2) does not
201 - 300 of 1096 matches
Mail list logo