I think it's exactly getting the share list using NT1 that is failing. I
will look at this tomorrow, see what smbclient -L is doing wrt NT1
temporary downgrade.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
firefox (66.0+build2-0ubuntu1) disco; urgency=medium
* New upstream stable release (66.0build2)
[ Olivier Tilloy ]
* Re-enable and update debian/patches/unity-menubar.patch
* Disable unaligned FP accesses emulation on armhf:
- armhf-disable-unaligned-fp-access-emulation.patch
*
I think it's exactly getting the share list using NT1 that is failing. I
will look at this tomorrow, see what smbclient -L is doing wrt NT1
temporary downgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Error installing grub
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.9
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CasperVersion: 1.405
Date: Mon Apr 29
thunderbird (1:60.6.0+build2-0ubuntu1) disco; urgency=medium
* New upstream stable release (60.6.0build2)
[ Olivier Tilloy ]
* Bump build-dep to clang-7 and llvm-7-dev
- debian/config/mozconfig.in
- debian/control{,.in}
[ Rico Tzschichholz ]
* Add patches to fix build on
I marked debian-bug 918742 as being the upstream for this, but
technically that bug was against fakechroot and the only change was to
disable the hanging test; however jemalloc2 in debian did fix this, and
the changelog entry for the fix only mentions that debian bug.
** Summary changed:
-
This bug was fixed in the package gcc-defaults-ports - 1.176ubuntu1.2
---
gcc-defaults-ports (1.176ubuntu1.2) bionic-proposed; urgency=medium
* SRU: LP: #1814369.
* Bump GCC 7 version to 7.4.0.
* Bump GCC 8 version to 8.3.0.
* Build riscv64 packages on arm64 and ppc64el.
--
** Changed in: mariadb-5.5 (Ubuntu)
Assignee: (unassigned) => Otto Kekäläinen (otto)
** Changed in: mariadb-10.1 (Ubuntu)
Assignee: (unassigned) => Otto Kekäläinen (otto)
** Changed in: mariadb-10.0 (Ubuntu)
Assignee: (unassigned) => Otto Kekäläinen (otto)
--
You received this
This bug was fixed in the package gcc-8 - 8.3.0-6ubuntu1~18.04
---
gcc-8 (8.3.0-6ubuntu1~18.04) bionic-proposed; urgency=medium
* SRU: LP: #1814369.
* Update to the GCC 8.3.0 release.
* Don't build from the ARM/Linaro branch on armhf/arm64.
gcc-8 (8.3.0-6ubuntu1) disco;
This bug was fixed in the package gcc-7 - 7.4.0-1ubuntu1~18.10
---
gcc-7 (7.4.0-1ubuntu1~18.10) cosmic-proposed; urgency=medium
* SRU: LP: #1814369.
* Fix target/88856, taken from the gcc-7-branch. LP: #1815057.
* Fix PR tree-optimization/89505, taken from the gcc-8 branch.
This bug was fixed in the package gcc-7 - 7.4.0-1ubuntu1~18.04
---
gcc-7 (7.4.0-1ubuntu1~18.04) bionic-proposed; urgency=medium
* SRU: LP: #1814369.
* Fix target/88856, taken from the gcc-7-branch. LP: #1815057.
* Fix PR tree-optimization/89505, taken from the gcc-8 branch.
This bug was fixed in the package gcc-7 - 7.4.0-1ubuntu1~18.04
---
gcc-7 (7.4.0-1ubuntu1~18.04) bionic-proposed; urgency=medium
* SRU: LP: #1814369.
* Fix target/88856, taken from the gcc-7-branch. LP: #1815057.
* Fix PR tree-optimization/89505, taken from the gcc-8 branch.
This bug was fixed in the package gcc-7-cross - 21ubuntu0.2
---
gcc-7-cross (21ubuntu0.2) bionic-proposed; urgency=medium
* SRU: LP: #1814369.
* Build using 7.4.0-1ubuntu1.
* Build ppc64el packages on arm64.
* Build s390x packages on arm64 and ppc64el.
* Build riscv64
** Changed in: libreoffice (Ubuntu)
Status: Fix Committed => 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/1725320
Title:
libreoffice-nlpsolver should depend on
This bug was fixed in the package gcc-8 - 8.3.0-6ubuntu1~18.04
---
gcc-8 (8.3.0-6ubuntu1~18.04) bionic-proposed; urgency=medium
* SRU: LP: #1814369.
* Update to the GCC 8.3.0 release.
* Don't build from the ARM/Linaro branch on armhf/arm64.
gcc-8 (8.3.0-6ubuntu1) disco;
This bug was fixed in the package gcc-7 - 7.4.0-1ubuntu1~18.10
---
gcc-7 (7.4.0-1ubuntu1~18.10) cosmic-proposed; urgency=medium
* SRU: LP: #1814369.
* Fix target/88856, taken from the gcc-7-branch. LP: #1815057.
* Fix PR tree-optimization/89505, taken from the gcc-8 branch.
This bug was fixed in the package gcc-8-cross-ports - 12ubuntu1.1
---
gcc-8-cross-ports (12ubuntu1.1) cosmic-proposed; urgency=medium
* SRU: LP: #1814369.
* Build using gcc 8.3.0-6ubuntu1.
* Build riscv64 packages on arm64 and ppc64el.
-- Matthias Klose Mon, 08 Apr 2019
This bug was fixed in the package eclipse-titan - 6.3.1-1build4.1
---
eclipse-titan (6.3.1-1build4.1) cosmic-proposed; urgency=medium
* SRU: LP: #1814369.
* Rebuild to satisfy bogus GCC version check.
* Fix ftbfs on non x86 architectures.
-- Matthias Klose Wed, 10 Apr 2019
This bug was fixed in the package gcc-7 - 7.4.0-1ubuntu1~18.04
---
gcc-7 (7.4.0-1ubuntu1~18.04) bionic-proposed; urgency=medium
* SRU: LP: #1814369.
* Fix target/88856, taken from the gcc-7-branch. LP: #1815057.
* Fix PR tree-optimization/89505, taken from the gcc-8 branch.
This bug was fixed in the package gcc-8 - 8.3.0-6ubuntu1~18.04
---
gcc-8 (8.3.0-6ubuntu1~18.04) bionic-proposed; urgency=medium
* SRU: LP: #1814369.
* Update to the GCC 8.3.0 release.
* Don't build from the ARM/Linaro branch on armhf/arm64.
gcc-8 (8.3.0-6ubuntu1) disco;
Validated on linux 4.15.0-49.53 from bionic-proposed:
ubuntu@bionic-l2:~$ uname -r
4.15.0-49-generic
ubuntu@bionic-l2:~$ cat
/sys/devices/system/clocksource/clocksource0/available_clocksource
kvm-clock tsc hpet acpi_pm
ubuntu@bionic-l2:~$ dmesg | grep -i tsc
[0.04] tsc: Detected
Validated on linux 4.4.0-147.173 from xenial-proposed:
ubuntu@xenial-l2:~$ uname -r
4.4.0-147-generic
ubuntu@xenial-l2:~$ cat
/sys/devices/system/clocksource/clocksource0/available_clocksource
kvm-clock tsc hpet acpi_pm
ubuntu@xenial-l2:~$ dmesg | grep -i tsc
[0.00] tsc: Detected
This bug was fixed in the package gcc-7 - 7.4.0-1ubuntu1~18.10
---
gcc-7 (7.4.0-1ubuntu1~18.10) cosmic-proposed; urgency=medium
* SRU: LP: #1814369.
* Fix target/88856, taken from the gcc-7-branch. LP: #1815057.
* Fix PR tree-optimization/89505, taken from the gcc-8 branch.
Hi Mathieu, thank you for the explanation and pushing the fix!
Hi Brian, I'll test the new grub2 binary in a Ubuntu 16.04.6 VM on
Hyper-V.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826453
** Description changed:
[impact]
under some circumstances, libjemalloc2 hangs on arm64 architecture.
[test case]
- the mariadb-10.1 autopkgtests, specifically when apt installing mariadb-
- server-10.1, will hang. It's possible the apt install mariadb-
- server-10.1 hangs outside
This bug was fixed in the package gcc-8-cross - 18ubuntu0.3
---
gcc-8-cross (18ubuntu0.3) bionic-proposed; urgency=medium
* SRU: LP: #1814369.
* Build using gcc 8.3.0-6ubuntu1.
* Build ppc64el packages on arm64.
* Build s390x packages on arm64 and ppc64el.
* Build riscv64
Here's a different perspective. Accessing the Win10 machine again:
tester@vub1904:~$ smbclient -L vwin10 -U smbuser
Unable to initialize messaging context
Enter WORKGROUP\smbuser's password:
Sharename Type Comment
- ---
ADMIN$
This bug was fixed in the package eclipse-titan - 6.3.1-1build1.2
---
eclipse-titan (6.3.1-1build1.2) bionic-proposed; urgency=medium
* SRU: LP: #1814369.
* Rebuild to satisfy bogus GCC version check.
* Fix ftbfs on non x86 architectures.
-- Matthias Klose Mon, 29 Apr 2019
This bug was fixed in the package gcc-7-cross-ports - 17ubuntu0.2
---
gcc-7-cross-ports (17ubuntu0.2) bionic-proposed; urgency=medium
* SRU: LP: #1814369.
* Build using 7.4.0-1ubuntu1.
* Build riscv64 packages on arm64 and ppc64el.
-- Matthias Klose Fri, 05 Apr 2019
This bug was fixed in the package gcc-8-cross-ports - 9ubuntu0.3
---
gcc-8-cross-ports (9ubuntu0.3) bionic-proposed; urgency=medium
* SRU: LP: #1814369.
* Build using gcc 8.3.0-6ubuntu1.
* Build ppc64el packages on arm64.
* Build s390x packages on arm64 and ppc64el.
* Build
This bug was fixed in the package gcc-defaults - 1.176ubuntu2.2
---
gcc-defaults (1.176ubuntu2.2) bionic-proposed; urgency=medium
* SRU: LP: #1814369.
* Bump GCC 7 version to 7.4.0.
* Bump GCC 8 version to 8.3.0.
* Build ppc64el packages on arm64.
* Build s390x packages on
This bug was fixed in the package gcc-7-cross - 26ubuntu1.1
---
gcc-7-cross (26ubuntu1.1) cosmic-proposed; urgency=medium
* SRU: LP: #1814369.
* Build using 7.4.0-1ubuntu1.
* Build ppc64el packages on arm64.
* Build s390x packages on arm64 and ppc64el.
* Build riscv64
This bug was fixed in the package gcc-defaults-ports - 1.178ubuntu1.1
---
gcc-defaults-ports (1.178ubuntu1.1) cosmic-proposed; urgency=medium
* SRU: LP: #1814369.
* Bump GCC 7 version to 7.4.0.
* Bump GCC 8 version to 8.3.0.
* Build riscv64 packages on arm64 and ppc64el.
--
This bug was fixed in the package gcc-8-cross - 21ubuntu1.1
---
gcc-8-cross (21ubuntu1.1) cosmic-proposed; urgency=medium
* SRU: LP: #1814369.
* Build using gcc 8.3.0-6ubuntu1.
* Build ppc64el packages on arm64.
* Build s390x packages on arm64 and ppc64el.
* Build riscv64
This bug was fixed in the package gcc-defaults - 1.179ubuntu1.1
---
gcc-defaults (1.179ubuntu1.1) cosmic-proposed; urgency=medium
* SRU: LP: #1814369.
* Bump GCC 7 version to 7.4.0.
* Bump GCC 8 version to 8.3.0.
* Build ppc64el packages on arm64.
* Build s390x packages on
This bug was fixed in the package gcc-8 - 8.3.0-6ubuntu1~18.10
---
gcc-8 (8.3.0-6ubuntu1~18.10) cosmic-proposed; urgency=medium
* SRU: LP: #1814369.
* Update to the GCC 8.3.0 release.
* Don't build from the ARM/Linaro branch on armhf/arm64.
gcc-8 (8.3.0-6ubuntu1) disco;
This bug was fixed in the package ggcov - 0.9+20190314-0ubuntu1~18.04
---
ggcov (0.9+20190314-0ubuntu1~18.04) bionic-proposed; urgency=medium
* SRU: LP: #1817554.
* Build from the gcc8-support branch, support gcc 7.4, 8.2 and 8.3.
ggcov (0.9+20190314-0ubuntu1) disco;
This bug was fixed in the package ggcov - 0.9+20190314-0ubuntu1~18.10
---
ggcov (0.9+20190314-0ubuntu1~18.10) cosmic-proposed; urgency=medium
* SRU: LP: #1817554.
* Build from the gcc8-support branch, support gcc 7.4, 8.2 and 8.3.
ggcov (0.9+20190314-0ubuntu1) disco;
** Changed in: kernel-sru-workflow/promote-to-proposed
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/1826147
Title:
linux-hwe-edge: 5.0.0-14.15~18.04.1
** Changed in: kernel-sru-workflow/snap-release-to-candidate
Status: Confirmed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
** Changed in: kernel-sru-workflow/snap-release-to-beta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-candidate
Status: New => Confirmed
** Changed in: kernel-sru-workflow/snap-release-to-edge
Status: Confirmed => Fix Released
**
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Incomplete
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
The verification of the Stable Release Update for gcc-7-cross-ports 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
The problem here seems to be that the files are already downloaded, and
when asking sourceforge to continue the download, it does the redirect
rather than responding with a 416 error with the appropriate content-
range as it should.
jak@jak-t480s:$ /usr/lib/apt/apt-helper -q -o
With eclipse-titan rebuilt for both bionic and cosmic, this is now good
to go. Marking as verified and releasing.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done verification-done-bionic
verification-done-cosmic
--
This bug was fixed in the package gcc-7-cross-ports - 21ubuntu1.1
---
gcc-7-cross-ports (21ubuntu1.1) cosmic-proposed; urgency=medium
* SRU: LP: #1814369.
* Build using 7.4.0-1ubuntu1.
* Build riscv64 packages on arm64 and ppc64el.
-- Matthias Klose Fri, 05 Apr 2019
The verification of the Stable Release Update for ggcov 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 gcc-8 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 gcc-8 - 8.3.0-6ubuntu1~18.10
---
gcc-8 (8.3.0-6ubuntu1~18.10) cosmic-proposed; urgency=medium
* SRU: LP: #1814369.
* Update to the GCC 8.3.0 release.
* Don't build from the ARM/Linaro branch on armhf/arm64.
gcc-8 (8.3.0-6ubuntu1) disco;
This bug was fixed in the package binutils - 2.30-21ubuntu1~18.04.1
---
binutils (2.30-21ubuntu1~18.04.1) bionic-proposed; urgency=medium
* SRU: LP: #1822717.
* Build ppc64el packages on arm64.
* Build s390x packages on arm64 and ppc64el.
* Build riscv64 packages on arm64 and
This bug was fixed in the package binutils - 2.31.1-6ubuntu1.1
---
binutils (2.31.1-6ubuntu1.1) cosmic-proposed; urgency=medium
* SRU: LP: #1822717.
* Build ppc64el packages on arm64.
* Build s390x packages on arm64 and ppc64el.
* Build riscv64 packages on arm64 and ppc64el.
** Description changed:
+ [Impact]
+
+ * When applying a minimal upgrade set fails raising an exception
+ unattended-upgrades stops trying to install further sets and may remove
+ packages left marked to remove in the dirty set.
+
+ [Test Case]
+
+ * Set up unattended-upgrades to always
The verification of the Stable Release Update for binutils 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
So could g_spawn_command_line_sync be used in case of
SCREENSAVER_TYPE_OTHER in xfce_screensaver_lock?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1054299
Title:
Race condition in suspend scripts
This bug was fixed in the package msttcorefonts - 3.7ubuntu5
---
msttcorefonts (3.7ubuntu5) eoan; urgency=medium
* Download fonts from GitHub instead of SourceForge,
thanks Peter Bhat Harkins (LP: #1713615)
-- Graham Inggs Mon, 29 Apr 2019 18:11:32 +
** Changed in:
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1704419.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
--- Comment From mranw...@us.ibm.com 2019-04-29 14:42 EDT---
An initial test looks good, thank you!
mranweil@ltc-wspoon5:~$ dpkg --list |grep linux-image-4\.15\.0-49
ii linux-image-4.15.0-49-generic4.15.0-49.53
ppc64el Signed kernel
Hello Dexuan, or anyone else affected,
Accepted grub2 into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/grub2/2.02~beta2-36ubuntu3.22 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** 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:
Public bug reported:
When I close my notebook and open it subsequently the wallpaper appears
"bugged".
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules:
FWIW, I also get this one (022554), along with two others (10ac08 and
6013d4).
The machine is an ASUS UX501V with an Intel HD Graphics 530 + NVIDIA GTX
960M (more details below). I'm running an up to date Debian 9.9 with a
4.19.28-2~bpo9+1 kernel (from stretch-backports). It is usually plugged
to
** Changed in: deja-dup (Ubuntu)
Status: New => Triaged
** Changed in: deja-dup (Ubuntu)
Importance: Undecided => Wishlist
** Summary changed:
- File restore is completely abandoned due to a single invalid backup file
+ Have an option to continue with only partly restore in case of
Hi Chris,
Please provide more context on this. We specifically need logs on what
apt commands were executed, how, and the full process log of the
terminal (e.g. we wanna see what apt has done).
That said, we've never seen anything like this before.
TO recover, you should just be able to stop
Closing this to be very outdated, without getting any confirmation in
around 7 years. If you find this in an recent version of Déjà Dup.
Please file a new bug stating that Version.
Thanks
** Changed in: deja-dup (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification
smbclient -L, "gio mount smb://server/share ', even just specifying
smb://server/share in the location bar in Nautilus works just like you
would expect.
It's only the gvfsd-smb-browse process that's messed up.
As far as it being a related but different problem Well I reckon it
all depends
Hello Ads2000.
The "fix" for the previous duplicate was telling the users to include a
share, if I got this right. So could you please ensure, that your server
address is something like smb://gnome.org/deja-dup instead of just
smb://gnome.org/?
Thanks
--
You received this bug notification
Dexuan,
To be clear, while there is no further point-release to be published for
16.04, we can still fix the bug. The patch will be available to users
updating their systems normally while 16.04 is supported, so daily
images may receive the fix (if this is applicable to clouds) and after
an
*** This bug is a duplicate of bug 1813716 ***
https://bugs.launchpad.net/bugs/1813716
** This bug has been marked a duplicate of bug 1813716
gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay →
detach_pixmap → meta_surface_actor_x11_dispose → g_object_unref →
Public bug reported:
Having recently found my MAAS unresponsive I was surprised to find out
it's because it uninstalled itself. First, how on earth does this
happen, and second how do I go about recovering this I have several
critical juju services deployed on a nodes that this MAAS runs and juju
*** This bug is a duplicate of bug 1813716 ***
https://bugs.launchpad.net/bugs/1813716
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
3.32.0+git20190410-1ubuntu1, the
Public bug reported:
I am trying to create a new vm in vsphere 6.0 with Ubuntu Server 18.04.
I was successful the very first time I installed it, however I have
tried the same exact process again and I continue to get "An Error
Occurred During Installation" at the same spot "configuring apt
Public bug reported:
[Impact]
It is possible for a socket to use more memory than permitted on systems using
the hns network driver.
[Fix]
b1ccd4c0ab6ef net: hns: fix skb->truesize underestimation
[Test Case]
Regression tested only.
[Regression Risk]
Trivial fix local to a single driver only
** Changed in: deja-dup (Ubuntu)
Importance: Undecided => High
** Changed in: deja-dup (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778638
Title:
> bionic and cosmic autopkgtests all pass, with the exception of:
this is actually caused by bug 1826883 (i believe); i'll sru a fixed
jemalloc to correct these failures.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I indeed think interacting with a server that has disabled SMB1 entirely
is a related, but different problem. Can you get smbclient -L to work
with such a server, using the netbios hostname, or does it fail when
listing the shares?
--
You received this bug notification because you are a member
kernel.org bug ticket, showing similar crashes on 4.9 and 4.19 kernels:
https://bugzilla.kernel.org/show_bug.cgi?id=202669
** Bug watch added: Linux Kernel Bug Tracker #202669
https://bugzilla.kernel.org/show_bug.cgi?id=202669
--
You received this bug notification because you are a member of
I indeed think interacting with a server that has disabled SMB1 entirely
is a related, but different problem. Can you get smbclient -L to work
with such a server, using the netbios hostname, or does it fail when
listing the shares?
--
You received this bug notification because you are a member
** Attachment added: "5 kernel stack traces of crashes on 4.4.0-145 and -146,
on 4 different hardware nodes"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824687/+attachment/5260024/+files/hessu-ipv6_expire_frag_queue-crashes.txt
--
You received this bug notification because you are
** Changed in: kernel-sru-workflow/snap-release-to-beta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-edge
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/snap-certification-testing
Status: New => Confirmed
**
Public bug reported:
Ubuntu 16.04 includes postfix-3.1.0-3 which fails for us installing in
an OBS buildroot (so a very minimal system), with the issue apparently
fixed in 3.1.3 : https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=842948
FWIW, the exact error message we have is:
[ 148s]
Your reference to the Linux Samba Server command: smbstatus got me
thinking what would happen if I disabled NT1 on a Linux Samba server by
stipulating "server min protocol = SMB2" and using Windows Network > ...
to connect.
The exact same thing happens as when trying to connect to a Win10
machine
I have had this crash, with the ip6_expire_frag_queue stack trace, more
than 18 times since 2019-04-16 on more than 10 different servers in 8
different countries. There have been some more crashes, but from these
ones the panic dump managed to go out to a remote syslog server where
it's easy to
** Changed in: kernel-sru-workflow/snap-release-to-beta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-candidate
Status: New => Confirmed
** Changed in: kernel-sru-workflow/snap-release-to-edge
Status: Confirmed => Fix Released
**
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
derivatives: bug 1826356
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Thank You, yes libreoffice* was the reason for my mystery extension
install...
But now I cannot remove libreoffice cleanly any longer:
sudo apt autoremove --purge libreoffice*
Errors were encountered while processing:
libreoffice-lightproof-en
libreoffice-lightproof-hu
** Project changed: canonical-identity-provider => gimp (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826899
Title:
crash in GIMP on exporting file
To manage notifications about this bug
Public bug reported:
erro
ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: kaccounts-providers (not installed)
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
Date: Sun Apr 21 02:11:58 2019
You have been subscribed to a public bug:
```
GNU Image Manipulation Program version 2.10.6
git-describe: GIMP_2_10_4-278-g0a8173ffde
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
** Bug watch added: Red Hat Bugzilla #1704419
https://bugzilla.redhat.com/show_bug.cgi?id=1704419
** Also affects: inkscape (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1704419
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
Hello Matthias, or anyone else affected,
Accepted eclipse-titan into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/eclipse-
titan/6.3.1-1build1.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
So it seems we need to re-build eclipse-titan for bionic still, so for
now reverting the verification tag.
** Tags removed: verification-done-bionic
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1826354
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Please would you open a new bug L'Africain, this one has actually
subsequently been resolved.
** Changed in: libreoffice (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There is now also another feature available in newer netplan versions
(0.96 and above, in progress SRU for bionic and above, so it should be
available soon on all supported releases...).
With this, you'd be able to use "dhcp4-overrides" to specify what metric
to use for routes, and whether or not
All the bionic-proposed toolchain packages are green and marked as valid
candidates (after ignoring the false-positive linux failures).
Considering this aged and verified.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification
This bug was fixed in the package python-stdlib-extensions -
2.7.16-2~18.10
---
python-stdlib-extensions (2.7.16-2~18.10) cosmic-proposed; urgency=medium
* SRU: LP: #1822993.
python-stdlib-extensions (2.7.16-2) unstable; urgency=medium
* Re-pack the orig tarball without the VCS
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
usbmuxd. This problem was most recently seen with package version
1.1.0-2ubuntu0.1, the problem page at
https://errors.ubuntu.com/problem/0ab3146f9a13cc10682e6a4210ead867d649869f
contains more
201 - 300 of 829 matches
Mail list logo
