Public bug reported:
La óptima para el monitor Lenovo L151 es 1024x678, en su lugar se activa
siempre la pantalla a 640x480 lo que impide el uso normal de los
programas, he tratado de corregirlo desde Terminal con xrandr, he
seguido las instrucciones pero no se soluciona, y cuando visualizo el
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1872504
and then change the status of the bug to 'Confirmed'.
If, due to the
This bug was fixed in the package whoopsie - 0.2.74
---
whoopsie (0.2.74) hirsute; urgency=medium
* adding force flag to rm command in postrm script in case whoopsie-id
does not yet exist when the package is removed (LP: #1907956)
-- William 'jawn-smith' Wilson Fri, 22
Jan
I upgraded my video card to a newer NVIDIA 1660 Ti. An expensive way to
fix a bug :).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1911369
Title:
[radeon] Horizontal
I added the linux source package to this bug because I've heard this
commit addresses the issue:
https://github.com/gregkh/linux/commit/099340d3e758cca06a82bf5dcff8b9a8acbdcb0a
Thanks
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
[Expired for lightdm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: lightdm (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
Hi @kaihengfeng thank you very much for commenting, much appreciated.
Yes, linux-modules-extra is installed:
$ uname -r
5.8.0-36-generic
$ sudo apt install linux-modules-extra-5.8.0-36-generic
[sudo] password for hazrpg:
Reading package lists... Done
Building dependency tree
Reading
** Changed in: mesa (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: mesa (Ubuntu)
Assignee: Timo Aaltonen (tjaalton) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
[Expired for gdebi (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gdebi (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdebi in Ubuntu.
[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
Something fishy with proprietary drivers. I don't know how to manually
update them. I am new to Linux. Also, I tried running all kind of
updates from Ubuntu Software Update.
I can't copy bug report because ubuntu doesn't allow so here's text from
OCR.
gdrive link to ss:
Incidentally, why are apport-gtk and whoopsie being removed? I'd think
crash reporting would be useful.
https://git.launchpad.net/~xubuntu-dev/ubuntu-
seeds/+git/xubuntu/commit/?id=c6d4cd2e0a24a5114dfe1cb8554d99ca91630a91
--
You received this bug notification because you are a member of Ubuntu
** Changed in: systemd
Status: Unknown => Fix Released
--
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/1911059
Title:
gce: 247.1-4ubuntu1 causes loss of networking
** Branch linked: lp:whoopsie
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1907956
Title:
ubiquity crash on whoopsie removal, Xubuntu 21.04 minimal install
Status in
I just upgraded two machines to Ubuntu 20.04 LTS and /var/log/syslog is
full of:
systemd-resolved[...]: Server returned error NXDOMAIN, mitigating
potential DNS violation DVE-2018-0001, retrying transaction with reduced
feature level UDP.
with the only thing reported by tcpdump(8) as:
[...]
I've done more digging and I think the regressing happened sooner, but I
only rebooted it on the day I noticed it wasn't working. I decided to
see when the system was actually last rebooted by using:
$ last reboot | less
reboot system boot 5.8.0-40-generic Fri Jan 22 11:44 still running
[Expired for shadow (Ubuntu) because there has been no activity for 60
days.]
** Changed in: shadow (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
Is linux-modules-extra installed?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1912773
Title:
[MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all, second
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1912773
Title:
[MS-7C52, ATI R6xx HDMI, Digital Out, HDMI]
libx11 (2:1.7.0-1) unstable; urgency=medium
* New upstream release.
* patches: Refreshed.
* signing-key: Added key from Keith Packard.
* symbols: Updated.
-- Timo Aaltonen Wed, 06 Jan 2021 20:47:58 +0200
** Also affects: libx11 (Ubuntu Bionic)
Importance: Undecided
Status:
All autopkgtests for the newly accepted glib2.0 (2.64.6-1~ubuntu20.04.1) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
libxmlb/0.1.15-2 (amd64)
libreoffice/1:6.4.6-0ubuntu0.20.04.1 (armhf)
netplan.io/0.101-0ubuntu3~20.04.2
** Tags removed: verification-done-bionic
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to audit in Ubuntu.
https://bugs.launchpad.net/bugs/1848330
Title:
Installing auditd
Forgot to mention in the original post, but trying to revert all updates
that caused the problem (as per the versions listed above) but that
didn't work because they no longer exist in the repo (and the system had
already cleared the cache). So I always get the error that the
package(s) were not
--- Comment From heinz-werner_se...@de.ibm.com 2021-01-22 05:51 EDT---
IBM Bugzilla status->closed, Fix Released for all requested distros
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to elfutils in Ubuntu.
Dr. Harbott, would you be able to test the new audit packages in bionic-
proposed? The SRU team is reluctant to approve this update without some
sort of confirmation that it fixes the bug, and I haven't been able to
reproduce it myself.
--
You received this bug notification because you are a
Public bug reported:
After a recent update, I now have a system that can no longer play audio
(via HDMI), my second monitor (DVI) is no longer being picked up, and
CPU/AGPU usage has lost a lot of performance (OBS is basically unusable
at this point).
Whatever has happened with the recent
This bug is finally fixed in mawk 1.3.4.20200120-2 which is available in
Ubuntu 20.04 LTS "Focal Fossa" and later releases. ✔️
** Changed in: mawk (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Also affects: systemd (Ubuntu)
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/1908065
Title:
Invalid SYSLOG_PID for
Hi Valters,
This really seems to be a systemd issue: sssd never sets SYSLOG_PID when
calling sd_journal_send(), yet journalctl shows e.g. SYSLOG_PID=sudo
instead of an empty string. Looks like systemd is mixing the variables
or leaking one into the others. The sssd upstream patch you pointed to
Hi, all.
I obtained feedback from one Canonical customer (with a Support Case
opened just for that), that hit the very same bug and, when testing the
package sitting in -proposed, didn't reproduce the issue anymore.
>From his own words:
"I wasn't able to recreate the auditd problem with the
** Changed in: gettext (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gettext in Ubuntu.
https://bugs.launchpad.net/bugs/1910792
Title:
gettext 0.21-3 FTBFS on armhf
I'm sending links to reports of affected apps - I can find only one there.
https://errors.ubuntu.com/oops/135f3daa-4578-11eb-8a73-fa163e6cac46
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
sssd is setting SYSLOG_IDENTIFIER to the debug_prg_name internal var, which is
set via calls to server_setup(), and in focal (and probably earlier) that's set
to a name like "sssd[sudo]". However the syslog MSG section TAG field format
requires only alphanumeric characters:
It does not appear that systemd-journald is automatically parsing
SYSLOG_IDENTIFIER. The following sample program:
#include
int main(int argc, char *argv[]) {
sd_journal_send("MESSAGE=%s", "Hello world!",
"SYSLOG_IDENTIFIER=%s", "sssd[sudo]",
NULL);
}
Hi Matthew,
Thanks for the analysis.
We'll need such changes on top of what's in -proposed (ie, in an
incremental version), re-uploaded.
Please see `dpkg-buildpackage -v` to generate a package build including
the version in -proposed plus the new version with the workaround for
the test-case.
Thanks for correcting the SRU version number.
I had to run update-maintainer to update maintainer fields.
Sponsored.
$ dput ubuntu binutils_2.34-6ubuntu1.1_source.changes
Checking signature on .changes
gpg: /tmp/binutils_2.34-6ubuntu1.1_source.changes: Valid signature from
9B8EC849D5EF70ED
** Bug watch added: github.com/systemd/systemd/issues #17803
https://github.com/systemd/systemd/issues/17803
** Also affects: systemd via
https://github.com/systemd/systemd/issues/17803
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Public bug reported:
On modern Ubuntu systems, /sys/kernel/debug is mounted by default due to
sys-kernel-debug.mount being enabled by default.
AFAIK, this FS doesn't need to be mounted for normal operations and back
in the day, there were concerns about the security implications of
having it
I'm inclined to say an admin should ask to mount this explicitly,
however stgraber pointed out on irc that lxd premounts /sys/kernel/debug
in part to placate upstart in guests. This may have implications for
disabling /lib/systemd/system/sys-kernel-debug.mount by default.
Thanks
--
You received
However, lxd seems to deal with /sys/kernel/debug itself by mounting it
unconditionally, irrespective of what systemd would do.
This was tested by running `systemctl mask sys-kernel-debug.mount` in a
container and seeing /sys/kernel/debug being mounted nevertheless.
--
You received this bug
40 matches
Mail list logo