[Touch-packages] [Bug 1908473] Re: rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak

2021-01-25 Thread Matthew Ruffell
Performing verification for Focal. I installed rsyslog-relp 8.2001.0-1ubuntu1.1 and librelp0 1.5.0-1ubuntu2 from -updates. >From there I set up the configuration file, launched a new rsyslog instance, and used netcat to set 100 packets to the relp port. https://paste.ubuntu.com/p/HfSDvNJzpX/

[Touch-packages] [Bug 1908473] Re: rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak

2021-01-24 Thread Matthew Ruffell
Hi Mauricio, I filed bug 1912969 to fix the FTBFS for librelp on focal. Adjusting the packets down from 50,000 to 10,000 makes the build succeed on riscv64. I attached two debdiffs, one an incremental patch from 1.5.0-1ubuntu2.20.04.1, and the other a full patch from 1.5.0-1ubuntu2. Please

[Touch-packages] [Bug 1908473] Re: rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak

2021-01-21 Thread Matthew Ruffell
Hi Mauricio, It seems riscv64 passes on Groovy due to tests being skipped on the riscv64 architecture. >From Groovy's build log: https://paste.ubuntu.com/p/NCJPDVSbSW/ If you look at the man page for dh_auto_test it mentions: If the DEB_BUILD_OPTIONS environment variable contains nocheck, no

[Touch-packages] [Bug 1908473] Re: rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak

2021-01-20 Thread Matthew Ruffell
Performing verification for Focal I installed rsyslog-relp 8.2001.0-1ubuntu1.1 and librelp0 1.5.0-1ubuntu2 from -updates. >From there I set up the configuration file, launched a new rsyslog instance, >and used netcat to set 100 packets to the relp port. https://paste.ubuntu.com/p/jCs9Dy6FYF/

[Touch-packages] [Bug 1908473] Re: rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak

2021-01-20 Thread Matthew Ruffell
Performing verification for librelp in Groovy. I installed rsyslog-relp 8.2006.0-2ubuntu1 and librelp 1.5.0-1ubuntu2 from -updates to reproduce: https://paste.ubuntu.com/p/gtn4rcXc72/ >From there I set up the configuration script, ran a new instance of rsyslog, and used netcat to open 100

[Touch-packages] [Bug 1908473] Re: rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak

2021-01-20 Thread Matthew Ruffell
Same one failure on today's rebuild. Strange, since this is the exact same code as Groovy. ** Attachment added: "buildlog_ubuntu-focal-riscv64.librelp_1.5.0-1ubuntu2.20.04.1_BUILDING.txt.gz.5"

[Touch-packages] [Bug 1912122] Re: /var/log/dmesg is 0644, should be 0640 to match new DMESG_RESTRICT restrictions

2021-01-20 Thread Matthew Ruffell
Hi Robie, I agree this probably isn't worth a SRU to Groovy, I just made the packages available in the odd chance that they might be considered. I will mark Groovy as won't fix. Hirsute is what really matters in the end. ** Changed in: rsyslog (Ubuntu Groovy) Status: In Progress => Won't

[Touch-packages] [Bug 1912122] Re: /var/log/dmesg is 0644, should be 0640 to match new DMESG_RESTRICT restrictions

2021-01-18 Thread Matthew Ruffell
Attached is a patch which changes /var/log/dmesg to 0640 on groovy. It also contains Steve's recommendation to set the logrotate files to 0640. ** Patch added: "Debdiff for syslog on groovy"

[Touch-packages] [Bug 1912122] Re: /var/log/dmesg is 0644, should be 0640 to match new DMESG_RESTRICT restrictions

2021-01-18 Thread Matthew Ruffell
Attached is a patch which changes /var/log/dmesg to 0640 on hirsute. It also contains Steve's recommendation to set the logrotate files to 0640. ** Patch removed: "Debdiff for rsyslog on hirsute"

[Touch-packages] [Bug 1912122] Re: /var/log/dmesg is 0644, should be 0640 to match new DMESG_RESTRICT restrictions

2021-01-17 Thread Matthew Ruffell
** Tags added: sts-sponsor -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1912122 Title: /var/log/dmesg is 0644, should be 0640 to match new DMESG_RESTRICT restrictions

[Touch-packages] [Bug 1912122] Re: /var/log/dmesg is 0644, should be 0640 to match new DMESG_RESTRICT restrictions

2021-01-17 Thread Matthew Ruffell
Attached is a debdiff for Groovy to change /var/log/dmesg to 0640. ** Patch added: "Debdiff for syslog on groovy" https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1912122/+attachment/5454005/+files/lp1912122_groovy.debdiff -- You received this bug notification because you are a member

[Touch-packages] [Bug 1912122] Re: /var/log/dmesg is 0644, should be 0640 to match new DMESG_RESTRICT restrictions

2021-01-17 Thread Matthew Ruffell
Attached is a debdiff for hirsute to set /var/log/dmesg to 0640. ** Patch added: "Debdiff for rsyslog on hirsute" https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1912122/+attachment/5454004/+files/lp1912122_hirsute.debdiff -- You received this bug notification because you are a

[Touch-packages] [Bug 1912122] Re: /var/log/dmesg is 0644, should be 0640 to match new DMESG_RESTRICT restrictions

2021-01-17 Thread Matthew Ruffell
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1912122 Title: /var/log/dmesg is 0644, should be 0640 to match new DMESG_RESTRICT restrictions Status

[Touch-packages] [Bug 1912122] Re: /var/log/dmesg is 0644, should be 0640 to match new DMESG_RESTRICT restrictions

2021-01-17 Thread Matthew Ruffell
** Changed in: rsyslog (Ubuntu Hirsute) Status: New => In Progress ** Changed in: rsyslog (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: rsyslog (Ubuntu Hirsute) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Description changed: [Impact]

[Touch-packages] [Bug 1912122] [NEW] /var/log/dmesg is 0644, should be 0640 to match new DMESG_RESTRICT restrictions

2021-01-17 Thread Matthew Ruffell
) Importance: Medium Assignee: Matthew Ruffell (mruffell) Status: In Progress ** Affects: rsyslog (Ubuntu Groovy) Importance: Undecided Status: New ** Affects: rsyslog (Ubuntu Hirsute) Importance: Medium Assignee: Matthew Ruffell (mruffell) Status

[Touch-packages] [Bug 1908473] Re: rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak

2021-01-05 Thread Matthew Ruffell
** Tags added: sts-sponsor -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1908473 Title: rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to

[Touch-packages] [Bug 1908473] Re: rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak

2021-01-05 Thread Matthew Ruffell
Attached is the debdiff for librelp for Focal ** Patch added: "Debdiff for librelp on Focal" https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1908473/+attachment/5449602/+files/librelp_focal.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1908473] Re: rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak

2021-01-05 Thread Matthew Ruffell
Attached is the debdiff for librelp for Groovy ** Patch added: "Debdiff for librelp on Groovy" https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1908473/+attachment/5449601/+files/librelp_groovy.debdiff -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1908473] Re: rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak

2021-01-05 Thread Matthew Ruffell
** Description changed: [Impact] In recent versions of rsyslog and librelp, the imrelp module leaks file descriptors due to a bug where it does not correctly close sockets, and instead, leaves them in the CLOSE_WAIT state. This causes rsyslogd on busy servers to eventually hit the

[Touch-packages] [Bug 1908473] Re: rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak

2021-01-02 Thread Matthew Ruffell
Since we only need to change librelp to fix the problem, we won't SRU the testcase to Focal's rsyslog, since there is no need to risk a regression for a testcase, which would effectively be a no-change rebuild. The testcase is already present in rsyslog on Groovy and Hirsute, marking as released.

[Touch-packages] [Bug 1908473] [NEW] rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak

2020-12-16 Thread Matthew Ruffell
: fix double free of sendbuf in some cases. Link: https://github.com/rsyslog/librelp/commit/4a6ad8637c244fd3a1caeb9a93950826f58e956a ** Affects: librelp (Ubuntu) Importance: Medium Assignee: Matthew Ruffell (mruffell) Status: In Progress ** Affects: rsyslog (Ubuntu) Imp

[Touch-packages] [Bug 1906627] Re: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression

2020-12-15 Thread Matthew Ruffell
To anyone following this bug: As we get ready to re-release the new adcli package which implements the --use-ldaps flag, if you are happy to spend a few moments testing the new package, I would really appreciate it. I really don't want to cause another regression again. You can install the new

[Touch-packages] [Bug 1906627] Re: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression

2020-12-15 Thread Matthew Ruffell
Performing verification for Bionic Firstly, I installed adcli and libsasl2-modules-gssapi-mit from -updates: adcli 0.8.2-1 libsasl2-modules-gssapi-mit 2.1.27~101-g0780600+dfsg-3ubuntu2.1 >From there, I joined a Active Directory realm: https://paste.ubuntu.com/p/zJhvpRzktk/ Next, I enabled

[Touch-packages] [Bug 1906627] Re: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression

2020-12-07 Thread Matthew Ruffell
Attached is option two: a debdiff for adcli, which builds on 0.8.2-1ubuntu2, which re-introduces all of the --use-ldaps patches, and also adds a depends to the fixed libsasl2-modules-gssapi-mit at greater or equal to relationship. Use this if option 1 is a no go. ** Patch added: "debdiff for

[Touch-packages] [Bug 1906627] Re: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression

2020-12-07 Thread Matthew Ruffell
Attached is option one: a debdiff for adcli, which builds on 0.8.2-1ubuntu1 and simply adds a depends to the fixed libsasl2-modules- gssapi-mit at greater or equal to relationship. This will require the 0.8.2-1ubuntu2 package in -unapproved queue to be deleted. ** Patch added: "debdiff for adcli

[Touch-packages] [Bug 1906627] Re: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression

2020-12-06 Thread Matthew Ruffell
** Tags added: sts-sponsor -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1906627 Title: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active

[Touch-packages] [Bug 1906627] Re: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression

2020-12-06 Thread Matthew Ruffell
Attached is a debdiff for cyrus-sasl2 on Bionic, which resolves the incompatibilities of the GSS-SPNEGO implementation with the one in Active Directory. ** Patch added: "cyrus-sasl2 debdiff for Bionic"

[Touch-packages] [Bug 1906627] Re: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression

2020-12-06 Thread Matthew Ruffell
** Summary changed: - adcli fails, can't contact LDAP server + GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression ** Description changed: - Package: adcli - Version: 0.8.2-1ubuntu1 - Release: Ubuntu 18.04 LTS + [Impact] - When

[Touch-packages] [Bug 1906627] Re: adcli fails, can't contact LDAP server

2020-12-04 Thread Matthew Ruffell
** Changed in: cyrus-sasl2 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1906627 Title: adcli fails, can't contact

[Touch-packages] [Bug 1906627] Re: adcli fails, can't contact LDAP server

2020-12-04 Thread Matthew Ruffell
** Changed in: cyrus-sasl2 (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: cyrus-sasl2 (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: cyrus-sasl2 (Ubuntu Bionic) Assignee: (unassigned) => Matthew Ruffell (mruffell) -- You received

[Touch-packages] [Bug 1906627] Re: adcli fails, can't contact LDAP server

2020-12-04 Thread Matthew Ruffell
Attached is a debdiff to revert the changes we made to adcli to restore functionality to GSS-API. ** Patch added: "Debdiff for adcli on Bionic" https://bugs.launchpad.net/ubuntu/+source/adcli/+bug/1906627/+attachment/5441133/+files/lp1906627_adcli_bionic.debdiff -- You received this bug

[Touch-packages] [Bug 1906627] Re: adcli fails, can't contact LDAP server

2020-12-03 Thread Matthew Ruffell
Yes, when --use-ldaps is specified, adcli will make a TLS connection to the domain controller, and speak LDAPS. This works, and is the reason why this bug slipped through our regression testing. I should have tested without the --use-ldaps flag as well. Regardless, this bug seems to be caused by

[Touch-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward

2020-08-30 Thread Matthew Ruffell
As per my most recent email to ubuntu-devel, I am marking the changes to util-linux as Won't Fix. Relevant mailing list discussion (for future reference): Ansgar responded on debian-devel mentioning that adding cap_syslog to dmesg enables the user to clear the kernel log buffer:

[Touch-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward

2020-08-30 Thread Matthew Ruffell
As 5.8.0-16-generic has now been released to the -release pocket, CONFIG_SECURITY_DMESG_RESTRICT is now enabled in Groovy. Marking the changes to the kernel as Fix Released. ** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification

[Touch-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward

2020-08-16 Thread Matthew Ruffell
Wrote to debian-devel to see if upstream is interested in carrying the debian postinstall changes for util-linux: https://lists.debian.org /debian-devel/2020/08/msg00107.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward

2020-08-10 Thread Matthew Ruffell
Attached is a rebased debdiff for util-linux, which implements the permission changes to the dmesg binary. ** Patch removed: "util-linux debdiff for Groovy" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886112/+attachment/5395389/+files/lp1886112_util-linux_groovy.debdiff ** Patch

[Touch-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward

2020-07-23 Thread Matthew Ruffell
Attached is a debdiff for util-linux which implements the permission and capability changes to the dmesg binary. ** Patch added: "util-linux debdiff for Groovy" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886112/+attachment/5395389/+files/lp1886112_util-linux_groovy.debdiff -- You

[Touch-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward

2020-07-23 Thread Matthew Ruffell
I emailed Seth Forshee asking about what happens when Groovy's kernel becomes Focal's HWE kernel, and he mentioned that the kernel team has processes in place to handle config changes, and that it isn't a problem. So we will go with the more secure by default way, and enable

[Touch-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward

2020-07-23 Thread Matthew Ruffell
Attached is a procps debdiff for groovy, which adds documentation to /etc/sysctl.d/10-kernel-hardening.conf and a commented out way to disable DMESG_RESTRICT. ** Patch added: "procps debdiff for Groovy"

[Touch-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward

2020-07-05 Thread Matthew Ruffell
I have created patches for both the procps package and the util-linux package which implements the proposed changes. You can find test packages in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1886112-test Debdiff for procps: https://paste.ubuntu.com/p/qvmHgMhXSj/ Debdiff

[Touch-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward

2020-07-05 Thread Matthew Ruffell
I was thinking about this over the weekend, and I think we overlooked the impact of setting CONFIG_SECURITY_DMESG_RESTRICT in the kernel config has on downstream users of Groovy's kernel, namely when it becomes Focal's HWE kernel. Focal won't be receiving any patches for /usr/bin/dmesg, so I

[Touch-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward

2020-07-05 Thread Matthew Ruffell
** Description changed: [Impact] This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT feature by default for Groovy onward, proposed to ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html The kernel log buffer contains a wealth of

[Touch-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward

2020-07-03 Thread Matthew Ruffell
** Patch removed: "procps debdiff for Groovy" https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1886112/+attachment/5389194/+files/lp1886112_procps_groovy.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward

2020-07-02 Thread Matthew Ruffell
Attached is a debdiff for procps on Groovy. It adds a commented out entry to 10-kernel-hardening.conf which users can use to disable the setting if they wish. ** Patch added: "procps debdiff for Groovy"

[Touch-packages] [Bug 1886112] [NEW] Enabling DMESG_RESTRICT in Groovy Onward

2020-07-02 Thread Matthew Ruffell
: Undecided Status: Fix Committed ** Affects: procps (Ubuntu) Importance: Undecided Assignee: Matthew Ruffell (mruffell) Status: In Progress ** Affects: util-linux (Ubuntu) Importance: Undecided Assignee: Matthew Ruffell (mruffell) Status: In Progress

[Touch-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward

2020-07-02 Thread Matthew Ruffell
Kernel is fix-committed as per: Mailing list: https://lists.ubuntu.com/archives/ubuntu-devel/2020-July/041079.html Commit: https://kernel.ubuntu.com/git/ubuntu/unstable.git/commit/?id=25e6c851704a47c81e78e1a82530ac4b328098a6 -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1876230] Re: liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address performance problems with MEMBARRIER_CMD_SHARED

2020-05-11 Thread Matthew Ruffell
> - apart from feedback given by @mruffell, to also check if any of librcu consumers are depending on a full membarrier - driven by kernel - for ** shared pages among different processes ** I agree with @ddstreet, I don't think liburcu gives that sort of guarantee when it comes to cross process

[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-05-10 Thread Matthew Ruffell
I went and looked at the autopkgtest regressions, and they aren't actual regressions, just transient network problems and slow build timeouts. chrony autopkgtest regression on armhf: Need to get 263 kB of archives. After this operation, 2,048 B of additional disk space will be used. Err:1

[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-05-10 Thread Matthew Ruffell
I repeated the same SRU verification as before, this time using kmod from -proposed. I installed a fresh Bionic KVM, with EFI enabled. I upgraded the system to use the latest -updates packages. Linux 4.15.0-99-generic and Kmod 24-1ubuntu3.3 were installed. I shut the machine down, set the VGA

[Touch-packages] [Bug 1876230] Re: liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address performance problems with MEMBARRIER_CMD_SHARED

2020-05-05 Thread Matthew Ruffell
Answering question 2. I have done a comprehensive performance analysis based on the benchmark application. Note: The SRU changes how the sys_membarrier syscall is used. The implementation that we want to change to in this SRU never blocks, while the previous implementation does. This makes

[Touch-packages] [Bug 1876230] Re: liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address performance problems with MEMBARRIER_CMD_SHARED

2020-05-05 Thread Matthew Ruffell
To answer question 1, I went and checked every rdepends package: gdnsd: dynamically links to -lurcu-qsbr $ ldd /usr/sbin/gdnsd liburcu-qsbr.so.6 => /usr/lib/x86_64-linux-gnu/liburcu-qsbr.so.6 (0x7f33bfde5000) glusterfs: The only package I am not entirely sure about. Only glusterd uses

[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-05-02 Thread Matthew Ruffell
For both tests I used the kmod package from my test ppa, since it is still in the unapproved upload queue. Firstly, I installed 4.15.0-99-generic from -updates, and booted my EFI based KVM machine with VGA=std. The screen was garbled, as the framebuffer used was efifb. I then installed

[Touch-packages] [Bug 1876230] Re: liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address performance problems with MEMBARRIER_CMD_SHARED

2020-04-30 Thread Matthew Ruffell
Attached is a debdiff for Bionic ** Patch added: "liburcu debdiff for Bionic" https://bugs.launchpad.net/ubuntu/+source/liburcu/+bug/1876230/+attachment/5364290/+files/lp1876230_bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages,

[Touch-packages] [Bug 1876230] [NEW] liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address performance problems with MEMBARRIER_CMD_SHARED

2020-04-30 Thread Matthew Ruffell
Status: Fix Released ** Affects: liburcu (Ubuntu Bionic) Importance: Medium Assignee: Matthew Ruffell (mruffell) Status: In Progress ** Tags: sts ** Also affects: liburcu (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: liburcu (Ubuntu) Sta

[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-04-22 Thread Matthew Ruffell
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1872863 [Impact] A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the kernel EFI stub whenever EFI is enabled. This causes problems for QEMU/KVM virtual machines which use the VGA=std video device,

[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-04-22 Thread Matthew Ruffell
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1872863 [Impact] A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the kernel EFI stub whenever EFI is enabled. This causes problems for QEMU/KVM virtual machines which use the VGA=std video device,

[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-04-21 Thread Matthew Ruffell
I have verified that enabling the bochs-drm kernel module on bionic does not cause any regressions for PowerKVM machines when the video device is VGA=std. TLDR: See Screenshot: https://launchpadlibrarian.net/475658598/Screenshot%20from%202020-04-22%2015-14-13.png This is in response to the main

[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-04-21 Thread Matthew Ruffell
Attached is proof the VM is using VGA=std for the ppc64el test. ** Attachment added: "Proof VM is running VGA=std on ppc64el" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872863/+attachment/5357796/+files/Screenshot%20from%202020-04-22%2015-14-04.png -- You received this bug

[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-04-21 Thread Matthew Ruffell
Attached is screenshot proof that bochs-drm functions correctly on 4.15.0-96-generic ppc64el, and does not cause any regressions when bochs-drm is enabled on ppc64el. ** Attachment added: "bochs-drm functions correctly on ppc64el"

[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-04-15 Thread Matthew Ruffell
I rebuilt the kmod and Linux packages to include the ppc64le and powerpc architectures, so we can test against POWER to ensure that LP #1378648 is no more, and we don't cause any regressions. I don't have access to any POWER machines though, so I need help testing. -- You received this bug

[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-04-14 Thread Matthew Ruffell
Attached is the debdiff for kmod, which removes bochs-drm from the framebuffer blacklist. ** Patch added: "kmod debdiff for bionic" https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1872863/+attachment/5354280/+files/lp1872863_bionic.debdiff -- You received this bug notification because

[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-04-14 Thread Matthew Ruffell
Submitted Kernel patches to mailing list: https://lists.ubuntu.com/archives/kernel-team/2020-April/109027.html https://lists.ubuntu.com/archives/kernel-team/2020-April/109028.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed

[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-04-14 Thread Matthew Ruffell
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1872863 [Impact] A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the kernel EFI stub whenever EFI is enabled. This causes problems for QEMU/KVM virtual machines which use the VGA=std video device,

[Touch-packages] [Bug 1872863] [NEW] QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-04-14 Thread Matthew Ruffell
Affects: kmod (Ubuntu Bionic) Importance: Medium Assignee: Matthew Ruffell (mruffell) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Medium Assignee: Matthew Ruffell (mruffell) Status: In Progress ** Tags: sts ** Description changed: -

[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-04-14 Thread Matthew Ruffell
Attached is a picture of the garbled screen when VGA=std under booting via kernel EFI stub. ** Attachment added: "Garbled screen" https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1872863/+attachment/5354248/+files/Screenshot%20from%202020-04-15%2012-19-48.png -- You received this bug

[Touch-packages] [Bug 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.

2020-04-13 Thread Matthew Ruffell
This bug is triggered when I went to upgrade the avahi packages as part of a daily upgrade in focal: $ sudo apt list --upgradable Listing... Done avahi-autoipd/focal 0.7-4ubuntu7 amd64 [upgradable from: 0.7-4ubuntu6] avahi-daemon/focal 0.7-4ubuntu7 amd64 [upgradable from: 0.7-4ubuntu6]

[Touch-packages] [Bug 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.

2020-04-13 Thread Matthew Ruffell
Still happening under Focal to this day. ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1820584 Title: seahorse assert failure: seahorse:

[Touch-packages] [Bug 1869831] [NEW] lvm2: VG swaps to most recent disk if underlying PV has duplicate UUID and VG name

2020-03-30 Thread Matthew Ruffell
untu 16.10 and later, meaning xenial is the only impacted supported release. ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: lvm2 (Ubuntu Xenial) Importance: Medium Assignee: Matthew Ruffell (mruffell) Status: Won't Fix ** Affects: lv

[Touch-packages] [Bug 1827172] Re: update-rc.d: enabling or disabling S runlevel services incorrectly modifies runlevel

2019-11-26 Thread Matthew Ruffell
The fix was released in sysv-rc 2.88dsf-41ubuntu6.3+esm1 for Trusty ESM. ** Changed in: sysvinit (Ubuntu Trusty) Status: In Progress => Fix Released ** Changed in: sysvinit (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu

[Touch-packages] [Bug 1847176] Re: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card

2019-10-08 Thread Matthew Ruffell
@gunnarl, did your audio work correctly in kernel 5.0.0-29, and broke when you updated to 5.0.0-31? If you boot 5.0.0-29 by selecting it in grub when you turn your computer on, does your audio work? Might this be related to Bug 1846991? -- You received this bug notification because you are a

[Touch-packages] [Bug 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox

2019-08-08 Thread Matthew Ruffell
I enabled bionic-proposed and installed ibus, ibus-gtk, ibus-gtk3 versions 1.5.17-3ubuntu5. I ran the test in a bionic VM which had VMware Horizon Agent for Linux installed, version 7.9.0-13916467. Running firefox with no environment variables caused long input delays and small lockups with the

[Touch-packages] [Bug 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox

2019-08-05 Thread Matthew Ruffell
Hi Lukasz, We are in luck, after some very helpful debugging done by the customer, I have been able to reliably reproduce this issue myself. Firstly, this issue only affects users of Ubuntu inside a VMware Horizon VDI, and only occurs after you install the VMware Horizon Agent for Linux. The

[Touch-packages] [Bug 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox

2019-07-31 Thread Matthew Ruffell
Revised debdiff for bionic which enables the environment variables IBUS_DISCARD_PASSWORD and IBUS_DISCARD_PASSWORD_APPS ** Patch added: "revised debdiff for bionic" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1838358/+attachment/5280261/+files/lp1838358_bionic_revised.debdiff -- You

[Touch-packages] [Bug 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox

2019-07-31 Thread Matthew Ruffell
Hi Oliver, Full details from the environment which has the problem: Affected machines are all running Bionic and are fully patched. firefox: 68.0.1+build1-0ubuntu0.18.04.1 gnome-shell: 3.28.4-0ubuntu18.04.1 ibus: 1.5.17-3ubuntu4 Machines are accessed as a VDI through VMware Horizon 7.9.0, and

[Touch-packages] [Bug 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox

2019-07-31 Thread Matthew Ruffell
** Description changed: [Impact] The following has been seen in a VMware Horizon VDI. I cannot reproduce this issue myself. When a user interacts with any password field in Firefox, gnome-shell and Firefox both freeze and the system becomes unusable. If you ssh into the system

[Touch-packages] [Bug 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox

2019-07-29 Thread Matthew Ruffell
Attached is the debdiff for bionic which restores ibus- xx-f19-password.patch ** Patch added: "ibus debdiff for bionic" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1838358/+attachment/5279953/+files/lp1838358_bionic.debdiff ** Tags added: sts-sponsor -- You received this bug

[Touch-packages] [Bug 1838358] [NEW] Ibus causes gnome-shell to freeze when password fields are selected in Firefox

2019-07-29 Thread Matthew Ruffell
D_PASSWORD=1 firefox or export IBUS_DISCARD_PASSWORD_APPS='firefox,.*chrome.*' ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Affects: ibus (Ubuntu Bionic) Importance: Medium Assignee: Matthew Ruffell (mruffell) Status: In Progress ** Tags: sts

[Touch-packages] [Bug 1827172] Re: update-rc.d: enabling or disabling S runlevel services incorrectly modifies runlevel

2019-06-06 Thread Matthew Ruffell
Attached is the final debdiff for release, mostly for having a record of it. I have built it in a personal ppa, tested it and verified it works. ** Patch added: "sysvinit debdiff for trusty esm"

[Touch-packages] [Bug 1827172] Re: update-rc.d: enabling or disabling S runlevel services incorrectly modifies runlevel

2019-05-02 Thread Matthew Ruffell
** Tags added: sts-sponsor -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1827172 Title: update-rc.d: enabling or disabling S runlevel services incorrectly modifies

[Touch-packages] [Bug 1827172] Re: update-rc.d: enabling or disabling S runlevel services incorrectly modifies runlevel

2019-05-01 Thread Matthew Ruffell
This debdiff contains the patch for trusty. I have tested it, built it in a ppa and run autopkgtest, and things look fine to me. ** Patch added: "sysvinit debdiff for trusty" https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1827172/+attachment/5260712/+files/lp1827172_trusty.debdiff

[Touch-packages] [Bug 1827172] Re: update-rc.d: enabling or disabling S runlevel services incorrectly modifies runlevel

2019-05-01 Thread Matthew Ruffell
I have developed a patch which I believe fixes the problem. https://paste.ubuntu.com/p/QRw4XTkXkV/ ** Description changed: [Impact]  * update-rc.d, in sysv-rc-2.88dsf-41ubuntu6.3 is broken in trusty. -  * update-rc.d incorrectly modifies symlinks when enabling or disabling -

[Touch-packages] [Bug 1827172] Re: update-rc.d: enabling or disabling S runlevel services incorrectly modifies runlevel

2019-04-30 Thread Matthew Ruffell
** Description changed: [Impact] - * update-rc.d, in sysv-rc-2.88dsf-41ubuntu6.3 is broken in trusty. +  * update-rc.d, in sysv-rc-2.88dsf-41ubuntu6.3 is broken in trusty. - * update-rc.d incorrectly modifies symlinks when enabling or disabling services -which are started on the

[Touch-packages] [Bug 1827172] [NEW] update-rc.d: enabling or disabling S runlevel services incorrectly modifies runlevel

2019-04-30 Thread Matthew Ruffell
the code in question is removed from update-rc.d.  * The bug exists in debian squeeze, which is now unsupported, and the code in question is not in any newer versions.  * The bug was introduced in 2009-06-29 and somehow evaded anyone noticing it. ** Affects: sysvinit (Ubuntu) Importanc