** Summary changed:
- Update to mesa and xorg-server causes Cinnamon desktop to not render properly
+ [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render
properly
** Tags added: vmware vmwgfx
--
You received this bug notification because you are a member of Ubuntu
You have been subscribed to a public bug:
Steps to reproduce:
---
1. Open a document signed with DocuSign
Expected behaviour:
---
Document opens fine
Actual behaviour:
---
Evince refuses to display the document, with the error message "The
document contains no pages".
If document is opened
It's not going to be simple I'm afraid, at least for the original
problem! "scmp_sys_resolver close_range" will quickly test whether
current seccomp has support for close_range (prints "-1" if not
supported, "436" otherwise - at least on x86_64.) Ubuntu seccomp
maintainers have been pretty happy
Still working out kinks in the above, but here's a simpler one. Needs
running in an nspawn container again (steps 1-2 above); should either
succeed (no output) or print "function not implemented", but without
seccomp support nspawn will block it and it will print "not permitted"
#include
Thanks for the bug report. Can you explain what is slow? Is it just
screen updates?
Also please open a Terminal window and run:
top
Do you see any high CPU users?
** Summary changed:
- very slow
+ [Lenovo IdeaPad 5 15IIL05] very slow
** Package changed: xorg (Ubuntu) => ubuntu
** Changed
It's due to the new glibc, confirmed using vscode
download and install using
https://code.visualstudio.com/sha/download?build=stable=linux-deb-x64
$ code
on an hirsute machine it works correctly, add an impish source and
upgrade libc6 and it fails to start with the error reported
** Package
Public bug reported:
my system is very slow
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
BootLog: Error:
** Changed in: libdrm (Ubuntu)
Status: New => Fix Committed
** Changed in: libdrm (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
Thanks, trying using the example from
https://sec.report/lux/doc/102081415.pdf the issue is fixed in hirsute
** Package changed: evince (Ubuntu) => poppler (Ubuntu)
** Changed in: poppler (Ubuntu)
Importance: Undecided => High
** Changed in: poppler (Ubuntu)
Status: New => Fix
I suspect these may be related:
https://github.com/electron/electron/pull/30893 "fix: crash when
launching app with systemd v249"
https://github.com/microsoft/vscode/issues/132609 "Electron 14+
required? Potential systemd 249 / nVidia issue"
Electron patch backported from Chromium:
I think the long test case in #5 now works. Note that later versions of
crun have worked around the problem:
https://github.com/containers/crun/pull/672
Still worth fixing, though, I think, as it is likely to cause further
problems as more code starts to use close_range.
--
You received this
** Description changed:
[impact]
starting in focal, systemd-logind runs sandboxed without any network
access, which breaks any configuration that uses remote servers for user
data, e.g. ldap, nis, etc
A more full discussion is available in the upstream bug report as well
as the
** Changed in: runc (Ubuntu Xenial)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1916485
Title:
test -x fails inside shell scripts in
** Changed in: docker.io (Ubuntu Xenial)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1916485
Title:
test -x fails inside shell scripts
** Changed in: binutils (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1940505
Title:
monero FTBFS on riscv64
Status in binutils:
> @Dan: have you actually confirmed, that building and running userdbd
solves those issues with NIS and LDAP?
sorry for the delay in getting back to this.
So, you're correct, userdb doesn't actually help this, it only moves the
problem.
While systemd-userdbd.service does (currently, at least)
** Changed in: docker.io (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: docker.io (Ubuntu Focal)
Status: New => Fix Released
** Changed in: docker.io (Ubuntu Hirsute)
Status: New => Fix Released
** Changed in: docker.io (Ubuntu Bionic)
Status: Fix
ubuntu-meta (1.472) impish; urgency=medium
* Refreshed dependencies
* Added dmidecode to standard [riscv64]
* Added gnome-initial-setup to desktop-minimal-recommends [riscv64],
desktop-recommends [riscv64]
* Added language-selector-common to desktop, desktop-minimal, desktop-
This bug was fixed in the package ubuntu-settings - 21.10.4
---
ubuntu-settings (21.10.4) impish; urgency=medium
[ Olivier Tilloy ]
* ubuntu-settings.gsettings-override:
- Update the dock's gsetting override to pin the launcher for the
firefox snap (LP: #1943840).
--
** Changed in: audacity
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/687689
Title:
Audacity ruins bluetooth
Status in Audacity:
You have been subscribed to a public bug:
When I click anywhere on the screen, I can see a text cursor in ṕoints
where I shouldn't be able to write, such as youtube video titles.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu
Closing this bug as it works for me (Xubuntu 20.04) and we've not seen
any reports of this problem for many years.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/687689
Hi,
I've created the package if someone would like to review it.
https://launchpad.net/~sagiben/+archive/ubuntu/network-manager-libreswan
Thanks,
Sagi.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1944595
Title:
text cursor
Status in xorg package in Ubuntu:
New
Bug
I took the liberty to clean up this bug and mark things as Invalid/Fix
Released as needed. Hopefully I got everything right, but feel free to
reopen/re-classify a task if there's something wrong.
Thanks.
** Changed in: libseccomp (Ubuntu Hirsute)
Status: Fix Committed => Fix Released
**
Public bug reported:
Device doesn't appear in the input options inside gnome sound controls.
It appears in pavucontrol, but there is no port associated to it, and no
sound is captured.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature:
Public bug reported:
A regression to sshd running in a chroot exists under the following
conditions:
1) sshd was built with glibc 2.34
2) sshd is running with a kernel that does not define the close_range syscall
(kernel <= 5.8)
3) /proc/self/fd does not exist in the chroot
The glibc 2.34
One good point in favor of including systemd-userdbd in Debian/Ubuntu
would be that we only need to adjust the restrictions for that service;
all other systemd-provided services would use (or at least, *should*
use...) systemd-userdbd to get user records. I'm not sure if that is
actually worth
I initially preferred your option two, a drop-in file in whichever nis
and ldap binary packages, on principle of trying to keep the mitigations
in place if we can.
But your case for a difficult debugging session is persuasive. Reading
the various bug reports around this, option three seems pretty
*** Bug 89138 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1308261
Title:
ICE provoked by a lambda using the sizeof a
I created upstream bugs to track this:
https://bugzilla.mindrot.org/show_bug.cgi?id=3349
https://sourceware.org/bugzilla/show_bug.cgi?id=28377
** Bug watch added: OpenSSH Portable Bugzilla #3349
https://bugzilla.mindrot.org/show_bug.cgi?id=3349
** Bug watch added: Sourceware.org Bugzilla
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
** Patch added: "Configure without closefrom"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1944621/+attachment/5527126/+files/lp1944621.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
Thanks for the bug report. Please attach a photo or video of the problem
so we can better understand what you are seeing.
** Tags added: amdgpu
** Summary changed:
- text cursor
+ [amdgpu] text cursor
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server
** Tags added: fossa-squirtle
** Also affects: oem-priority
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1944409
Title:
According to the PulseList.txt in the #1, the default input device should be
"Digital Microphone - sof-hda-dsp":
Default source name:
alsa_input.pci-_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_6__source
I have no idea why "Device doesn't appear in the input options inside
This is still a bug in 20.04.3 LTS. It's a fresh install with
proprietary drivers enabled from the installer. Could it be routing
analog audio to the wrong place? I can get it to work fine with
bluetooth headphones, usb headphones on the dock and the laptop. I can't
get any audio from the analog
*** This bug is a duplicate of bug 1911055 ***
https://bugs.launchpad.net/bugs/1911055
This bug was discovered as duplicate - the issue persisted while the P50
was suspended & resumed while in a docking station (probably prime-
select using 'ondemand'). This is GPU driver related.
** This
38 matches
Mail list logo
