Performing verification for Focal
Generating the ssl certificates, and reproducing the problem with version
1.1.1f-1ubuntu2.3 from -updates.
ubuntu@select-lobster:~$ sudo apt-cache policy openssl | grep Installed
Installed: 1.1.1f-1ubuntu2.3
ubuntu@select-lobster:~$ mkdir reproducer
and grub.cfg in correct directories
since grub 2.04 seems to enforce pedantic locations. (LP: #1928040)
Date: Tue, 11 May 2021 19:38:29 +1200
Changed-By: Matthew Ruffell
Maintainer: Colin Watson
Signed-By: Łukasz Zemczak
https://launchpad.net/ubuntu/+source/grub2-signed/1.167~16.04.2
Format: 1.8
Attached is a debdiff for grub2-signed which issues a sed to remove the
GRUB_DISTRIBUTOR=Debian line from /etc/default/grub.d/50-cloudimg-
settings.cfg
** Patch added: "Debdiff for grub2-signed on Xenial"
** Description changed:
[Impact]
GCE cloud instances started with images released prior to 2020-11-11
will fail to reboot when the newest grub2 2.02~beta2-36ubuntu3.32
packages are installed from -updates.
Upon reboot, the instance drops down to a grub prompt, and ceases to
boot
Public bug reported:
[Impact]
GCE cloud instances started with images released prior to 2020-11-11
will fail to reboot when the newest grub2 2.02~beta2-36ubuntu3.32
packages are installed from -updates.
Upon reboot, the instance drops down to a grub prompt, and ceases to
boot any further.
The
Public bug reported:
[Impact]
GCE cloud instances started with images released prior to 2020-11-11
will fail to reboot when the newest grub2 2.02~beta2-36ubuntu3.32
packages are installed from -updates.
Upon reboot, the instance drops down to a grub prompt, and ceases to
boot any further.
The
I have completed most of my regression testing, and things are still looking
good. The performance of the block discard is there, and I haven't seen any
data corruption.
In particular, I have been testing against the testcase for the regression that
occurred with the previous revision of the
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1896578
[Impact]
Block discard is very slow on Raid10, which causes common use cases
which invoke block discard, such as mkfs and fstrim operations, to take
a very long time.
For example, on a i3.8xlarge
If anyone is interested in testing, there are new re-spins of the test kernels
available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/lp1896578-test
The patches used are the ones I will be submitting for SRU, and are more
or less identical to the patches in the previous
Hi Thimo,
I have been doing quite a bit of regression testing, and so far everything is
looking good. The performance of the block discard is there, and I haven't
come across any data corruption.
I have also spent some time running through the testcase you created for this
bug, and I have the
Hi Thimo,
I have been doing quite a bit of regression testing, and so far everything is
looking good. The performance of the block discard is there, and I haven't
come across any data corruption.
I have also spent some time running through the testcase you created for this
bug, and I have the
I have completed most of my regression testing, and things are still looking
good. The performance of the block discard is there, and I haven't seen any
data corruption.
In particular, I have been testing against the testcase for the regression that
occurred with the previous revision of the
If anyone is interested in testing, there are new re-spins of the test kernels
available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/lp1896578-test
The patches used are the ones I will be submitting for SRU, and are more
or less identical to the patches in the previous
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1896578
[Impact]
Block discard is very slow on Raid10, which causes common use cases
which invoke block discard, such as mkfs and fstrim operations, to take
a very long time.
For example, on a i3.8xlarge
Hi Thimo,
As promised yesterday, the new re-spins of the test kernels have
finished building and are now available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/lp1896578-test
The patches used are the ones I will be submitting for SRU, and are more
or less identical to
Hi Thimo,
As promised yesterday, the new re-spins of the test kernels have
finished building and are now available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/lp1896578-test
The patches used are the ones I will be submitting for SRU, and are more
or less identical to
** Description changed:
[impact]
openssl doesn't build source properly because of a badly-constructed
patch
[test case]
$ pull-lp-source openssl groovy
...
$ cd openssl-1.1.1f/
$ quilt pop -a
...
$ dpkg-buildpackage -d -S
dpkg-buildpackage: info: source package
** Description changed:
[impact]
openssl doesn't build source properly because of a badly-constructed
patch
[test case]
$ pull-lp-source openssl groovy
...
$ cd openssl-1.1.1f/
$ quilt pop -a
...
$ dpkg-buildpackage -d -S
dpkg-buildpackage: info: source package
Attached is a V2 for hirsute which correctly has d/p/ in the
debian/changelog.
** Patch added: "debdiff for openssl on hirsute"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494814/+files/lp1927161_hirsute_v2.debdiff
--
You received this bug notification
Attached is a V2 for hirsute which correctly has d/p/ in the
debian/changelog.
** Patch added: "debdiff for openssl on hirsute"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494814/+files/lp1927161_hirsute_v2.debdiff
--
You received this bug notification
Attached is a V2 for impish which correctly has d/p/ in the
debian/changelog.
** Patch added: "debdiff for openssl on impish"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494813/+files/lp1927161_impish_v2.debdiff
** Patch removed: "debdiff for openssl on
Attached is a V2 for impish which correctly has d/p/ in the
debian/changelog.
** Patch added: "debdiff for openssl on impish"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494813/+files/lp1927161_impish_v2.debdiff
** Patch removed: "debdiff for openssl on
Attached is a debdiff for openssl on groovy, which fixes this issue, and
also bug 1926254
** Patch added: "debdiff for openssl on groovy"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494812/+files/lp1926254_lp1927161_groovy.debdiff
** Patch removed: "debdiff
Attached is a debdiff for openssl on hirsute which fixes this problem.
** Patch added: "debdiff for openssl on hirsute"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494811/+files/lp1927161_hirsute.debdiff
--
You received this bug notification because you are a
Attached is a debdiff for openssl on groovy, which fixes this issue, and
also bug 1926254
** Patch added: "debdiff for openssl on groovy"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494812/+files/lp1926254_lp1927161_groovy.debdiff
** Patch removed: "debdiff
Attached is a debdiff for openssl on hirsute which fixes this problem.
** Patch added: "debdiff for openssl on hirsute"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494811/+files/lp1927161_hirsute.debdiff
--
You received this bug notification because you are a
Attached is a debdiff for impish which fixes this problem.
** Patch added: "debdiff for openssl on impish"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494810/+files/lp1927161_impish.debdiff
--
You received this bug notification because you are a member of
Attached is a debdiff for impish which fixes this problem.
** Patch added: "debdiff for openssl on impish"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494810/+files/lp1927161_impish.debdiff
--
You received this bug notification because you are a member of
I split 'pr12272.patch' into one file per commit, and I did a diff to
ensure that there is no changes to the code:
https://paste.ubuntu.com/p/zDqqXmsM8c/
When using these split up patches "dpkg-buildpackage -d -S" completes
successfully.
--
You received this bug notification because you are a
I split 'pr12272.patch' into one file per commit, and I did a diff to
ensure that there is no changes to the code:
https://paste.ubuntu.com/p/zDqqXmsM8c/
When using these split up patches "dpkg-buildpackage -d -S" completes
successfully.
--
You received this bug notification because you are a
nassigned) => Matthew Ruffell (mruffell)
** Changed in: openssl (Ubuntu Hirsute)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: openssl (Ubuntu Impish)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a mem
nassigned) => Matthew Ruffell (mruffell)
** Changed in: openssl (Ubuntu Hirsute)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: openssl (Ubuntu Impish)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a memb
Hi Thimo,
Thanks for writing back, great timing!
So, the new revision of the patches that we have been testing since
February have just been merged into mainline. The md/raid10 patches got
merged on Friday, and the dm/raid patches got merged on Saturday, and
will be tagged into 5.13-rc1. There's
Hi Thimo,
Thanks for writing back, great timing!
So, the new revision of the patches that we have been testing since
February have just been merged into mainline. The md/raid10 patches got
merged on Friday, and the dm/raid patches got merged on Saturday, and
will be tagged into 5.13-rc1. There's
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1896578
[Impact]
Block discard is very slow on Raid10, which causes common use cases
which invoke block discard, such as mkfs and fstrim operations, to take
a very long time.
For example, on a i3.8xlarge
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1896578
[Impact]
Block discard is very slow on Raid10, which causes common use cases
which invoke block discard, such as mkfs and fstrim operations, to take
a very long time.
For example, on a i3.8xlarge
signed) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896578
Title:
raid10: Block discard is very slow, causing severe delays for mkfs and
fstrim operations
signed) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896578
Title:
raid10: Block discard is very slow, causing severe delays for mkfs and
fstrim o
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1896578
[Impact]
Block discard is very slow on Raid10, which causes common use cases
which invoke block discard, such as mkfs and fstrim operations, to take
a very long time.
For example, on a i3.8xlarge
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1896578
[Impact]
Block discard is very slow on Raid10, which causes common use cases
which invoke block discard, such as mkfs and fstrim operations, to take
a very long time.
For example, on a i3.8xlarge
Hi Seth,
Thanks for the review.
I read the commit you found:
commit 1e41dadfa7b9f792ed0f4714a3d3d36f070cf30e
Author: Dr. David von Oheimb
Date: Sat Jun 27 16:16:12 2020 +0200
Subject: Extend X509 cert checks and error reporting in v3_{purp,crld}.c and
x509_{set,vfy}.c
Link:
Hi Seth,
Thanks for the review.
I read the commit you found:
commit 1e41dadfa7b9f792ed0f4714a3d3d36f070cf30e
Author: Dr. David von Oheimb
Date: Sat Jun 27 16:16:12 2020 +0200
Subject: Extend X509 cert checks and error reporting in v3_{purp,crld}.c and
x509_{set,vfy}.c
Link:
Hi Dan,
I responded to Seth's question about the re-factor commit in openssl
3.0alpha, and it does not need to be backported.
I think we are good to go for sponsorship now, thanks!
Matthew
On Sat, May 1, 2021 at 7:52 AM Dan Streetman wrote:
>
> On Thu, Apr 29, 2021 at 8:13 PM Matthew R
Hi Mike,
The Raid10 block discard performance patchset from Xiao Ni has reached mainline
this morning in the following commits:
254c271da071 md/raid10: improve discard request for far layout
d30588b2731f md/raid10: improve raid10 discard request
f2e7e269a752 md/raid10: pull the code that wait
** Tags added: 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/1926254
Title:
x509 Certificate verification fails when
basicConstraints=CA:FALSE,pathlen:0 on self-signed leaf certs
To
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1926254
Title:
x509 Certificate verification fails when
basicConstraints=CA:FALSE,pathlen:0 on
Hi Security Team,
VISA opened a case, SF308725 - "openssl unable to process the certificate on
Ubuntu 20.0" [1], about a minor regression in openssl 1.1.1f that affects
both Focal and Groovy.
[1]
https://canonical.lightning.force.com/lightning/r/Case/5004K05pGePQAU/view
A commit was merged
Attached is a debdiff for openssl on Groovy which fixes this bug.
** Patch added: "Debdiff for openssl on Groovy"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1926254/+attachment/5493443/+files/lp1926254_groovy.debdiff
--
You received this bug notification because you are a member
Attached is a debdiff for openssl on Groovy which fixes this bug.
** Patch added: "Debdiff for openssl on Groovy"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1926254/+attachment/5493443/+files/lp1926254_groovy.debdiff
--
You received this bug notification because you are a member
Attached is a debdiff for openssl on Focal which fixes this bug.
** Patch added: "Debdiff for openssl on focal"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1926254/+attachment/5493442/+files/lp1926254_focal.debdiff
--
You received this bug notification because you are a member of
Attached is a debdiff for openssl on Focal which fixes this bug.
** Patch added: "Debdiff for openssl on focal"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1926254/+attachment/5493442/+files/lp1926254_focal.debdiff
--
You received this bug notification because you are a member of
** Changed in: linux (Ubuntu Groovy)
Assignee: Sinclair Willis (yousure1222) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1907262
Title:
raid10: discard
** Changed in: linux (Ubuntu Groovy)
Assignee: Sinclair Willis (yousure1222) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907262
Title:
raid10: discard leads to
** Description changed:
[Impact]
In openssl 1.1.1f, the below commit was merged:
commit ba4356ae4002a04e28642da60c551877eea804f7
Author: Bernd Edlinger
Date: Sat Jan 4 15:54:53 2020 +0100
Subject: Fix error handling in x509v3_cache_extensions and related functions
Link:
** Description changed:
[Impact]
In openssl 1.1.1f, the below commit was merged:
commit ba4356ae4002a04e28642da60c551877eea804f7
Author: Bernd Edlinger
Date: Sat Jan 4 15:54:53 2020 +0100
Subject: Fix error handling in x509v3_cache_extensions and related functions
Link:
** Affects: openssl (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: openssl (Ubuntu Focal)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: openssl (Ubuntu Groovy)
Importance: Medium
Assignee:
** Affects: openssl (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: openssl (Ubuntu Focal)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: openssl (Ubuntu Groovy)
Importance: Medium
Assignee:
@dannf: Yes, this bug sure is a tricky one.
Most of these reports will be due to failing / faulty / non-spec
complaint USB devices or cables, like the original reason for this bug
being opened. Although, there have been some reports where user's
systems do go back to working when they install my
@dannf: Yes, this bug sure is a tricky one.
Most of these reports will be due to failing / faulty / non-spec
complaint USB devices or cables, like the original reason for this bug
being opened. Although, there have been some reports where user's
systems do go back to working when they install my
*** This bug is a duplicate of bug 1923670 ***
https://bugs.launchpad.net/bugs/1923670
Hi Kjell,
Thanks for reporting the issue! We have been tracking it in bug 1923670.
We found the root cause, and we have commit a fix to the source code
tree. This will be fixed in the next kernel update
*** This bug is a duplicate of bug 1923670 ***
https://bugs.launchpad.net/bugs/1923670
Hi Kjell,
Thanks for reporting the issue! We have been tracking it in bug 1923670.
We found the root cause, and we have commit a fix to the source code
tree. This will be fixed in the next kernel update
Thanks Tim for building the test kernel, and Hmpf, thanks for testing it
and confirming it fixes the problem.
Okay, so the problem is:
commit a738c93fb1c17e386a09304b517b1c6b2a6a5a8b
Author: Shyam Prasad N
Date: Thu Feb 11 03:26:54 2021 -0800
Subject: cifs: Set CIFS_MOUNT_USE_PREFIX_PATH flag
Thanks Tim for building the test kernel, and Hmpf, thanks for testing it
and confirming it fixes the problem.
Okay, so the problem is:
commit a738c93fb1c17e386a09304b517b1c6b2a6a5a8b
Author: Shyam Prasad N
Date: Thu Feb 11 03:26:54 2021 -0800
Subject: cifs: Set CIFS_MOUNT_USE_PREFIX_PATH flag
Hi @Hmpf,
Thanks for filing a bug report.
I had a look at the changes between 5.4.0-70-generic and
5.4.0-71-generic, and I found three patches for CIFS:
$ git log --grep "cifs" Ubuntu-5.4.0-70.78..Ubuntu-5.4.0-71.79
https://paste.ubuntu.com/p/YgrZcN8B6j/
I had a read of the patches, and I
Hi @Hmpf,
Thanks for filing a bug report.
I had a look at the changes between 5.4.0-70-generic and
5.4.0-71-generic, and I found three patches for CIFS:
$ git log --grep "cifs" Ubuntu-5.4.0-70.78..Ubuntu-5.4.0-71.79
https://paste.ubuntu.com/p/YgrZcN8B6j/
I had a read of the patches, and I
Attached is a debdiff for Hirsute which re-applies "screen: Use clean
env when creating new tab" and is the same patch in the PPA.
** Description changed:
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus,
selecting "Open in Terminal", you get a fully
Attached is a debdiff for Hirsute which re-applies "screen: Use clean
env when creating new tab" and is the same patch in the PPA.
** Description changed:
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus,
selecting "Open in Terminal", you get a fully
Attached is a debdiff for Hirsute which re-applies "screen: Use clean
env when creating new tab" and is the same patch in the PPA.
** Description changed:
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus,
selecting "Open in Terminal", you get a fully
** Description changed:
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus,
selecting "Open in Terminal", you get a fully functional terminal
window.
If you then press the new tab button, or ctrl-shift-t to open a new
terminal tab, you will find that
** Description changed:
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus,
selecting "Open in Terminal", you get a fully functional terminal
window.
If you then press the new tab button, or ctrl-shift-t to open a new
terminal tab, you will find that
** Description changed:
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus,
selecting "Open in Terminal", you get a fully functional terminal
window.
If you then press the new tab button, or ctrl-shift-t to open a new
terminal tab, you will find that
It seems the revert for "screen: Use clean env when creating new tab" is
already in 3.38.1, and I checked the Ubuntu source package, and the
revert is in place.
https://gitlab.gnome.org/GNOME/gnome-
terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
Interesting.
I might try a test build
It seems the revert for "screen: Use clean env when creating new tab" is
already in 3.38.1, and I checked the Ubuntu source package, and the
revert is in place.
https://gitlab.gnome.org/GNOME/gnome-
terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
Interesting.
I might try a test build
It seems the revert for "screen: Use clean env when creating new tab" is
already in 3.38.1, and I checked the Ubuntu source package, and the
revert is in place.
https://gitlab.gnome.org/GNOME/gnome-
terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
Interesting.
I might try a test build
** 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/1921104
Title:
net/mlx5e: Add missing capability check for uplink follow
To manage notifications about this bug go to:
** Tags added: sts
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1921104
Title:
net/mlx5e: Add missing capability check for uplink follow
Status in Ubuntu on IBM z Systems:
In
Performing verification for Bionic.
I want to say straight up, I haven't been able to reproduce the problem,
I have tried many mechanisms, but I can not reproduce the 20 second
shell hang and crash, as documented in https://github.com/GSConnect
Performing verification for Bionic.
I want to say straight up, I haven't been able to reproduce the problem,
I have tried many mechanisms, but I can not reproduce the 20 second
shell hang and crash, as documented in https://github.com/GSConnect
Performing verification for Bionic.
I want to say straight up, I haven't been able to reproduce the problem,
I have tried many mechanisms, but I can not reproduce the 20 second
shell hang and crash, as documented in https://github.com/GSConnect
Performing verification for Focal.
I installed qemu 4.2-3ubuntu6.14 from -updates with the usual KVM stack
command:
$ sudo apt-get install qemu-kvm libvirt-daemon-system libvirt-clients
bridge-utils
$ sudo reboot
>From there I installed and configured a NFS server:
$ sudo -s
$ sudo apt
Performing verification for Groovy.
I installed qemu 5.0-5ubuntu9.6 from -updates with the usual KVM stack
command:
$ sudo apt-get install qemu-kvm libvirt-daemon-system libvirt-clients
bridge-utils
$ sudo reboot
>From there I installed and configured a NFS server:
$ sudo -s
$ sudo apt
Might also be related:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/303
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1922839
Title:
Opening new tab in
Might also be related:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/303
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922839
Title:
Opening new tab in gnome-terminal launched from
Might also be related:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/303
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1922839
Title:
Opening new tab in
Seems this is a long running issue.
Upstream bug:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253
** Bug watch added: gitlab.gnome.org/GNOME/gnome-terminal/-/issues #253
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253
** Bug watch added:
Seems this is a long running issue.
Upstream bug:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253
** Bug watch added: gitlab.gnome.org/GNOME/gnome-terminal/-/issues #253
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253
** Bug watch added:
Seems this is a long running issue.
Upstream bug:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253
** Bug watch added: gitlab.gnome.org/GNOME/gnome-terminal/-/issues #253
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253
** Bug watch added:
Version tested in hirsute is 3.38.1-1ubuntu1.
I checked Groovy, with 3.38.0-1ubuntu1.1, and the problem does not happen.
Both systems using Wayland session.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
Version tested in hirsute is 3.38.1-1ubuntu1.
I checked Groovy, with 3.38.0-1ubuntu1.1, and the problem does not happen.
Both systems using Wayland session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus,
selecting "Open in Terminal", you get a fully functional terminal
window.
If you then press the new tab button, or ctrl-shift-t to open a new
terminal tab, you will find that most environment
Version tested in hirsute is 3.38.1-1ubuntu1.
I checked Groovy, with 3.38.0-1ubuntu1.1, and the problem does not happen.
Both systems using Wayland session.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
Public bug reported:
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus,
selecting "Open in Terminal", you get a fully functional terminal
window.
If you then press the new tab button, or ctrl-shift-t to open a new
terminal tab, you will find that most environment
Public bug reported:
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus,
selecting "Open in Terminal", you get a fully functional terminal
window.
If you then press the new tab button, or ctrl-shift-t to open a new
terminal tab, you will find that most environment
Thanks for the quick work Christian!
I'll keep an eye out and be ready to test once builds enter -proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921665
Title:
QEMU hits assertion when
Attached is a debdiff for Groovy which fixes this bug.
** Patch added: "QEMU debdiff for Groovy"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921665/+attachment/5481777/+files/lp1921665_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Attached is a debdiff for Focal which fixes this bug.
** Patch added: "QEMU debdiff for focal"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921665/+attachment/5481776/+files/lp1921665_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
O_DIRECT with NFS
Link:
https://git.qemu.org/?p=qemu.git;a=commit;h=5edc85571e7b7269dce408735eba7507f18ac666
Mailing list discussion:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg721982.html
** Affects: qemu (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affe
Performing verification for gnome-shell in Bionic.
During this verification I will explain how VMware Horizon SSO works,
and will prove that the gnome-shell in -proposed is equivalent to the
custom gnome-shell package distributed by VMware.
I will begin by walking through the SSO workflow, based
Performing verification for gnome-shell in Bionic.
During this verification I will explain how VMware Horizon SSO works,
and will prove that the gnome-shell in -proposed is equivalent to the
custom gnome-shell package distributed by VMware.
I will begin by walking through the SSO workflow, based
Performing verification for gnome-shell in Bionic.
During this verification I will explain how VMware Horizon SSO works,
and will prove that the gnome-shell in -proposed is equivalent to the
custom gnome-shell package distributed by VMware.
I will begin by walking through the SSO workflow, based
701 - 800 of 1624 matches
Mail list logo
