Thanks for the bug report. The attached Xorg logs appear to be from
before the bug as they show a resolution of 1600x900. But I can also see
that your current resolution is 800x600 in Xrandr.txt. It seems Xorg now
can't even tell what kind of monitor connection it is.
Please try booting an older
Thanks for the bug report. Please try logging into 'Ubuntu on Wayland'
using the icon in the bottom right corner of the login screen before you
enter your password. That should make it behave the same as the login
screen.
** Tags added: nvidia
** Package changed: xorg (Ubuntu) => xorg-server
Please collect logs from the failed boots of the 470 driver by running:
journalctl -b-1 > prevboot-1.txt
journalctl -b-2 > prevboot-2.txt
journalctl -b-3 > prevboot-3.txt
journalctl -b-4 > prevboot-4.txt
journalctl -b-5 > prevboot-5.txt
and attach the resulting text files here.
**
** Tags added: rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1943189
Title:
"cannot refresh whilst network offline" bug
Status in packagekit package
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1943189
Title:
"cannot refresh whilst network offline" bug
Status in packagekit package in Ubuntu:
Public bug reported:
In Ubuntu Impish, an issue has been noted in regards to refreshing
packages in Plasma Discover for upgrade or installation. An error
appears upon initialization of the Discover interface:
"cannot refresh whilst network offline"
This will happen regardless of if a system is
This bug was fixed in the package grep - 3.7-0ubuntu1
---
grep (3.7-0ubuntu1) impish; urgency=medium
* New upstream version 3.7 to fix FTBFS (LP: #1940999)
* Use built-in regex instead of the one from glibc, to address failure of
test-regex with version 3.7.
-- Dan Bungert
** Description changed:
systemd.mount constantly unmounts an in use sshfs drive!
- mount has successfully entered the 'dead' state.
+ Sep 09 11:20:01 $HOSTNAME systemd[4613]: pathtomount.mount: Succeeded.
+ ░░ Subject: Unit succeeded
+ ░░ Defined-By: systemd
+ ░░ Support:
** Attachment removed: "WifiSyslog.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5361003/+files/WifiSyslog.txt
** Attachment removed: "CRDA.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360989/+files/CRDA.txt
**
** Attachment removed: "ping.txt"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313410/+files/ping.txt
** Attachment removed: "Screenshot of configuring screen and terminal"
** Attachment removed: "Dependencies.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310885/+files/Dependencies.txt
** Attachment removed: "NetDevice.enp4s0.txt"
** Description changed:
systemd.mount constantly unmounts an in use sshfs drive!
mount has successfully entered the 'dead' state.
+
+ Change my kernel and the issue *seems* to have subsided.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: systemd 247.3-3ubuntu3.4
** Attachment removed: "CRDA.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350596/+files/CRDA.txt
** Attachment removed: "CRDA.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310884/+files/CRDA.txt
**
** Attachment removed: "my initrd.img"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1870607/+attachment/5345796/+files/initrd.img
** Attachment removed: "ProcCpuinfoMinimal.txt"
** Description changed:
systemd.mount constantly unmounts an in use sshfs drive!
mount has successfully entered the 'dead' state. -What the hell I WAS
USING IT!
I had this drive originally in auto.sshfs but when the application I was
using accessing files on the drive just up and
** Attachment removed: "WifiSyslog.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310894/+files/WifiSyslog.txt
** Attachment removed: "IpAddr.txt"
After upgrading my systems to hirsute I was able to successfully validate on
hirsute, too.
Adjusting the tags accordingly ...
** Tags removed: verification-needed verification-needed-hirsute
** Tags added: verification-done verification-done-hirsute
--
You received this bug notification
I think Dan's summary above is very good. For clarification I would add
a couple of points.
The issue is not just remote logins. xdm behaves in the same way, and
the absence of a systemd-logind session may mean that sound is then
unavailable to the user logged in at the console. (Mentioned to
** Description changed:
systemd.mount constantly unmounts an in use sshfs drive!
mount has successfully entered the 'dead' state. -What the hell I WAS
USING IT!
I had this drive originally in auto.sshfs but when the application I was
using accessing files on the drive just up and
I totally get your concern. In the same time, other procps pkkg in
Ubuntu groovy, ... uses the same approach.
But I leave you to decide what is best for this particular bug.
Let us know.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Description changed:
systemd.mount constantly unmounts an in use sshfs drive!
mount has successfully entered the 'dead' state. -What the hell I WAS
USING IT!
I had this drive originally in auto.sshfs but when the application I was
using accessing files on the drive just up and
hm, I am a bit worried about this patch. Basically it's as the
regression potential field mentions: I don't like the idea that the
patch hard-codes the version number in the patch body. On the other
hand, it feels rather unlikely that we'll be bumping the upstream
version in focal... I think we'll
Public bug reported:
systemd.mount constantly unmounts an in use sshfs drive!
mount has successfully entered the 'dead' state. -What the hell I WAS
USING IT!
I had this drive originally in auto.sshfs but when the application I was
using accessing files on the drive just up and vanished I
** Tags removed: rls-ii-incoming
--
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/1940635
Title:
systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on
armhf
Hello Graham, or anyone else affected,
Accepted dpdk into hirsute-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dpdk/20.11.3-0ubuntu0.21.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: glibc (Ubuntu)
Status: Confirmed => 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/1940635
Title:
systemd-networkd failing to acquire a
Public bug reported:
My resolution has suddenly changed from a higher resolution from to low
resolution to 800x600 and it is now showing only one resolution option
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu
Retesting with snapd 2.52+git658.g005f554-dirty (13328), mksquashfs is
able to work as expected. I believe that when we are able to
autopkgtest against a snap with that fix, that this problem will be
resolved.
** Changed in: squashfs-tools (Ubuntu)
Status: New => Fix Committed
--
You
as systemd was respun (for focal) due to bug 1942899, and only the one
udev (hwdb) patch was reverted which shouldn't affect this at all, I'm
remarking this as verified still based on testing for the previous
version above.
** Tags removed: verification-needed verification-needed-focal
** Tags
as systemd was respun due to bug 1942899, and only the one udev (hwdb)
patch was reverted which shouldn't affect this at all, I'm remarking
this as verified still based on testing for the previous version above.
** Tags removed: verification-needed verification-needed-focal
** Tags added:
root@lp1853164-b:~# dpkg -l systemd|grep systemd
ii systemd237-3ubuntu10.51 amd64system and service manager
root@lp1853164-b:~# dpkg -l | grep -E 'ifupdown|resolvconf'
ii ifupdown 0.8.17ubuntu1.1 amd64
high level tools to
as systemd was respun due to bug 1942899, and only the one udev (hwdb)
patch was reverted which shouldn't affect this at all, I'm remarking
this as verified still based on testing for the previous version above.
--
You received this bug notification because you are a member of Ubuntu
Touch
heh, please ignore the above comment, the current focal systemd was
respun, but the fix for this was already released for focal, this only
needs bionic verified now :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
for the verifications above, i also updated the 'udev' package to the
same version as systemd
** Tags removed: verification-needed verification-needed-focal
verification-needed-hirsute
** Tags added: verification-done verification-done-focal
verification-done-hirsute
--
You received this bug
commit to focal that needed reverting:
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?h=ubuntu-focal=5c1be33900edee94da0dc9a4ade8edcd079b4c85
ubuntu@lp1942899-f:~$ dpkg -l systemd|grep systemd
ii systemd245.4-4ubuntu3.11 amd64system and service manager
commit to hirsute that needed reverting:
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a21edd743408b5603b0177e9c230c6d6b919e589
ubuntu@lp1942899-h:~$ dpkg -l systemd|grep systemd
ii systemd247.3-3ubuntu3.4 amd64system and service manager
** Tags removed: sts-sponsors-slashd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1917148
Title:
ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
Status in procps
** Description changed:
[impact]
initial patch for LP: #1938259 was incorrect.
[test case]
this bug is only to revert the previous patch
+
+ the upstream commit
+
is:https://github.com/systemd/systemd/pull/20314/commits/55b29d8f130684bf1fd9fdfaef3bcca64b66930e
+
+ checking for
Public bug reported:
I have two mice each with their own dongle. 1 is the microsoft sculpt
keyboard mouse combo and the other is a logitech master2 (using dongle
not bluetooth). Both of the mice work while in the login screen but
once you log in neither will control the cursor.
I know they are
ubuntu@lp1934981-f:~$ dpkg -l systemd|grep systemd
ii systemd245.4-4ubuntu3.11 amd64system and service manager
ubuntu@lp1934981-f:~$ grep -E '^Allow' /etc/systemd/sleep.conf
AllowSuspendThenHibernate=yes
AllowHybridSleep=no
ubuntu@lp1934981-f:~$ sudo systemctl
[sts-sponsors]
Sponsored in Focal upload queue, now waiting for SRU verification team
approval.
Thanks for your contribution, Kellen.
Test case validation (before upload):
root@procpsf:/tmp# pgrep --version
pgrep from procps-ng 3.3.16
root@procpsf:/tmp# ps --version
ps from procps-ng
ubuntu@lp1934981-h:~$ dpkg -l systemd|grep systemd
ii systemd247.3-3ubuntu3.4 amd64system and service manager
ubuntu@lp1934981-h:~$ grep -E '^Allow' /etc/systemd/sleep.conf
AllowSuspendThenHibernate=yes
AllowHybridSleep=no
ubuntu@lp1934981-h:~$ sudo systemctl
** Description changed:
basic.target waits for dbus.socket (via sockets.target) AND dbus.socket
waits for basic.target, too, delaying dbus-daemon startup. At some point
a timeout happens, dbus is started and all queued services try to start
registering to the bus at the same time.
** Description changed:
[Impact]
* Breakage of tools expecting the version number or the number to
substantially match the Debian package version.
* May confuse users expecting the version to substantially match the Debian
package version.
* Restores behavior to that provided in
ubuntu@lp1934147-f:~$ dpkg -l systemd|grep systemd
ii systemd245.4-4ubuntu3.11 amd64system and service manager
ubuntu@lp1934147-f:~$ loginctl list-sessions
SESSION UID USER SEAT TTY
1 1000 ubuntu ttyS0
1 sessions listed.
ubuntu@lp1934147-f:~$ for i in {1..100}; do
ubuntu@lp1934147-h:~$ dpkg -l systemd|grep systemd
ii systemd247.3-3ubuntu3.4 amd64system and service manager
ubuntu@lp1934147-h:~$ loginctl list-sessions
SESSION UID USER SEAT TTY
1 1000 ubuntu ttyS0
1 sessions listed.
ubuntu@lp1934147-h:~$ for i in {1..100}; do
[sts-sponsors]
Debian uses autopkgtest for 'version' w/ restriction superficial as
follows:
Tests: version
Restrictions: superficial
https://people.debian.org/~eriberto/README.package-tests.html
superficial
The test does not provide significant test coverage, so if it passes, that does
not
Public bug reported:
Please sync expat 2.4.1-1 (main) from Debian experimental (main)
Changelog entries since current impish version 2.3.0-1:
expat (2.4.1-1) experimental; urgency=high
* New upstream release:
- fix CVE-2013-0340: protect against billion laughs attacks
Sending this bug after, solved by change drivers, i can change it back
to 470, and perform debug commands if needed (gather logs etc.)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Public bug reported:
After turn on mu PC, it doesn't send signal to the second monitor. (with driver
"nvidia-driver-470(proprietary tested)"
After change it to: "nvidia-driver-460(proprietary)" problem solved.
Looks like new kernel update have conflict with nvidia - 470 driver.
(because
Just to summarize the specific flow of this bug:
1. an application is started for a user session, e.g. sshd handles a user
connecting.
2. the application uses pam for authentication, which by default includes
pam_systemd as an (optional) module.
3. pam invokes pam_systemd as part of session
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1943125
Title:
devscripts breaks apt
Status in apt
I was able to verify this on focal in a little z/VM env. that I've setup (it's
a little bit different to the setup that was used by the initial reporter, but
close enough).
So I'm updating the focal tag.
(will then upgrade to hirsute and redo - sorry this way it's less work for me)
** Tags
(In reply to Rob McCathie from comment #292)
> I should clarify: My broken use case is capturing from the global output
> monitor while also capturing the screen, and having the audio be
> synchronised like at capture time.
>
> In some of my early tests the audio was not only un-synchronised, but
Again a correction: the current default setup for Raven corresponds to
position_fix=6 option. It's not a simple LPIB read but contains some
awkward correction that takes the FIFO size into account.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I should clarify: My broken use case is capturing from the global output
monitor while also capturing the screen, and having the audio be
synchronised like at capture time.
In some of my early tests the audio was not only un-synchronised, but
had other issues too (jolting, etc.), so it's possible
... and looking back at the development history again, this seems too early to
be delighted. Actually the change to PRESET_AMD_SB was done as a fix for the
certain devices in the commit d2c63b7dfd06788a466d5ec8a850491f084c5fc2
ALSA: hda - Apply AMD controller workaround for Raven platform
@Takashi Iwai
> So moving it back would break something else, too. Hmm.
Indeed, it will break whatever solutions to the original issue of
microphone input crackling your changes may have fixed for this sound
device.
My use case - capturing from the global output monitor - has never had a
I hit this issue as well on my Gentoo box (see
https://bugs.gentoo.org/779157).
After applying the patch mentioned in comment #296, the audio is back to
normal with PulseAudio, no more distortions, the audio is clean. No
perceived audio lags. Everything is in working order again.
Tested only
1487 is with the same setup as Raven (15e3), and the same workaround is
applied.
Please note that the workaround isn't actually delaying the sound
transfer. Instead, it reports the PCM delay value up to 32bytes for
FIFO size for the applications. If the application (the sound backend)
doesn't
Update after the latest firmware update for the platform, called AMD
AGESA V2 PI 1.2.0.3 Patch A, released yesterday for my platform,
finally. This includes the USB patch for the drop in the USB
communication under load for too much recovery errors hitting the Pci-Ex
subsystem on the chipset,
Created attachment 295735
The partial revert patch
--
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/1801540
Title:
Microphone distorted sound on ALC892/1220 on AMD
Indeed.
My issue relates to usage with Pulse.
PipeWire looks like an interesting up-and-coming project, but right now
Pulse is what is rolled out in the vast majority of distros and, for
now, tales of outcomes with PipeWire aren't so useful.
--
You received this bug notification because you
After some gaming and streaming, I can confirm that I haven't heard
anymore pops or clicks, and a lot of performance issues completely
disappeared after applying this firmware, like microstutters in the
system under load and such. Kinda makes sense, since PciEx is basically
the main bus where
(In reply to Rob McCathie from comment #296)
> Just thought i'd update on my situation, i've now tested that it is only the
> Pulse changing to batch mode that causes my issue. So i'm no longer running
> the patch i posted earlier, rather now i do this:
>
>
>
> diff -Naur
Just thought i'd update on my situation, i've now tested that it is only
the Pulse changing to batch mode that causes my issue. So i'm no longer
running the patch i posted earlier, rather now i do this:
diff -Naur a/sound/pci/hda/hda_controller.c b/sound/pci/hda/hda_controller.c
---
OK, I'm going to submit this partial revert.
--
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/1801540
Title:
Microphone distorted sound on ALC892/1220 on AMD chipsets
Yes, that's merely an ugly workaround, and I'd happily get rid of it
once after confirming it's working fine without that!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
Any update on this? Perhaps I have a misunderstanding, however the issue
is still here unless I do a patch -R with what is in comment #296. Even
with the latest 5.11.13...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Launchpad has imported 5 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=211853.
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
Public bug reported:
This new upstream version consists only of a couple security fixes, and
should thus be merged into Impish.
Upstream changelog:
Changes between 1.1.1k and 1.1.1l [24 Aug 2021]
*) Fixed an SM2 Decryption Buffer Overflow.
In order to decrypt SM2 encrypted data an
That's a good discovery. This change makes sense, as the different of
PRESET_ATI_SB from PRESET_AMD_SB is about the position reporting. ATI_SB uses
the legacy LPIB register read while AMD_SB uses the position buffer table.
This could be verified by changing position_fix module option: 1 is
FYI, the 'solution' for this issue that is now in the kernel breaks
capturing screen+currrently playing audio with ffmpeg, for me at least,
on AMD Raven hardware.
I tried many things but could not achieve good audio capture that is
synchronised, not when capturing from Pulse anyway.
I'm guessing
Updates on this long endeavor as of today: I choose to give another try
for switching from PulseAudio to the PipeWire sound server.
The problems are completely gone. No audio clicking anywhere on the system.
I have tried one month ago, but on reboot I was not having any audio coming out
from
74 matches
Mail list logo
