[Touch-packages] [Bug 1801540]
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 the system. Now everything worked on install right from the get go. Tried also the mic under Steam, which always had audio clicking issue while acquiring and audio stalling (don't remember under what condition); acquisition is now perfect. Tried to dual test recording from Steam Voice and Discord while playing audio, no delay, no crackling, no issue. All streams are working simultaneously. I still have not long tested this, by the way, but on a first impression, yes, it fixed a lot of issues for me. The only minor configuration issue was to switch the microphone detection method in the PipeWire configuration file, otherwise no microphone were detected. After that, everything work as it should, for now. The issue on my end was definitely PulseAudio. If you still have problems, try PipeWire if you can or if fits your needs. This definitely solved my problems, maybe it will help yours too. Marco. -- 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 Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
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 it's being in BATCH mode, and Pulse not operating with tsched, that is the problem, not the rest of the patchwork. Nonetheless I just wanted things to work as before without any doubt, so I now have my kernel patched with the following (restoring 1022:15e3 to use the parameter sets it used to before all this) and everything is working fine now: diff -Naur a/sound/pci/hda/hda_intel.c b/sound/pci/hda/hda_intel.c --- a/sound/pci/hda/hda_intel.c 2021-02-10 19:29:23.0 +1100 +++ b/sound/pci/hda/hda_intel.c 2021-02-14 02:42:38.714796278 +1100 @@ -2601,7 +2601,8 @@ AZX_DCAPS_PM_RUNTIME }, /* AMD Raven */ { PCI_DEVICE(0x1022, 0x15e3), - .driver_data = AZX_DRIVER_GENERIC | AZX_DCAPS_PRESET_AMD_SB }, + .driver_data = AZX_DRIVER_GENERIC | AZX_DCAPS_PRESET_ATI_SB | +AZX_DCAPS_PM_RUNTIME }, /* ATI HDMI */ { PCI_DEVICE(0x1002, 0x0002), .driver_data = AZX_DRIVER_ATIHDMI_NS | AZX_DCAPS_PRESET_ATI_HDMI_NS }, -- While I greatly appreciate the work on the microphone input crackling issue (which I have experienced and been annoyed by myself over the years), i'm concerned that the current solution should've been further tested and developed before being mainlined. -- 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 Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
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 LPIB and 2 is position buffer. If we can confirm that this change generally improves the behavior, I can merge the fix quickly to the upstream. Can anyone else check it? -- 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 Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943109] [NEW] Merge 1.1.1l-1 version from Debian
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 application is expected to call the API function EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the "out" parameter can be NULL and, on exit, the "outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the "out" parameter. A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a second time with a buffer that is too small. A malicious attacker who is able present SM2 content for decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of 62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour or causing the application to crash. The location of the buffer is application dependent but is typically heap allocated. (CVE-2021-3711) [Matt Caswell] *) Fixed various read buffer overruns processing ASN.1 strings ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). (CVE-2021-3712) [Matt Caswell] Debian changelog: openssl (1.1.1l-1) unstable; urgency=medium * New upstream version. - CVE-2021-3711 (SM2 Decryption Buffer Overflow). - CVE-2021-3712 (Read buffer overruns processing ASN.1 strings). -- Sebastian Andrzej Siewior Wed, 25 Aug 2021 00:19:05 +0200 ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: rls-ii-incoming -- 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/1943109 Title: Merge 1.1.1l-1 version from Debian Status in openssl package in Ubuntu: New Bug description: 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 application is ex
[Touch-packages] [Bug 1912052] Re: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 20.10 (not even wired, cable headset)
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 https://help.launchpad.net/InterBugTracking. On 2021-02-19T18:10:45+00:00 crysman wrote: Created attachment 295367 alsa-info-0.4.65_output Simply put, external microphone (classic cable jack input) does not work. I've already described thoroughly the whole issue on various places, choose your favorite: - https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1912052 - https://askubuntu.com/questions/1305942/external-headset-microphone-not-working-in-ubuntu-20-10-not-even-wired-cable-h Might be related?: - https://bugzilla.kernel.org/show_bug.cgi?id=195457#c29 I'm attaching the output of this ( https://git.alsa-project.org/?p=alsa- utils.git;a=blob_plain;f=alsa-info/alsa-info.sh;hb=HEAD ) Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1912052/comments/5 On 2021-02-22T10:11:54+00:00 tiwai wrote: First off, please try the latest kernel, at best 5.11. It makes further debugging easier. After confirming the latest kernel still doesn't work, let's try to switch to the legacy HD-audio snd-hda-intel driver; we're checking only about the external mic, and it makes easier to debug, too. Boot with snd_intel_dspcfg.dsp_driver=1 boot option, and it'll forcibly use the legacy driver. Note that, with this, the built-in mic won't work with this. Once after that, you can try to pass a different model option to snd- hda-intel module. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1912052/comments/7 On 2021-02-23T19:38:51+00:00 crysman wrote: OK, I wait until Ubuntu ships 5.11 natively and then let you know. 5.10 will be not enough in 21.04? Sad is that it used to work before - until some upgrade along the way... Meanwhile, just tested "snd_intel_dspcfg.dsp_driver=1" boot option and... nope, has not fixed the problem. There is a change it the name of the device - something like "...Analog input..." instead of something like "...SmartSound Technology..." but external cable mic is not working nevertheless. Regarding "passing different option to snd-..." I am not sure what you exacly mean? You mean try this "sudo hda-verb /dev/snd/hwC0D0 " kinda' hacking? Thank you! Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1912052/comments/8 On 2021-02-24T09:01:15+00:00 tiwai wrote: The debug will be based on 5.11.x, so it's better to move it at first. About the different option to snd-hda-intel: no, you can pass "model" option to snd-hda-intel module to apply some device-specific quirk. For example, snd_hda_intel.model=alc255-acer boot option will apply some Acer-specific workaround. Or try snd_hda_intel.model=headset-mic There are quite many model options for the Realtek codecs. A part of available values are found in Documentation/sound/hd-audio/models.rst, the section for ALC269. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1912052/comments/9 On 2021-03-01T17:48:05+00:00 pmenzel+bugzilla.kernel.org wrote: crysman, with Ubuntu you can easily test Linux kernel releases using their builds [1]. Download the package and install with `sudo dpkg -i …`. [1]: https://kernel.ubuntu.com/~kernel-ppa/mainline/ Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1912052/comments/11 -- 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/1912052 Title: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 20.10 (not even wired, cable headset) Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure Did not help. There are more information with screenshots here: https://askubuntu.com/questions/1305942/external-headset-microphone- not-working-on-ubuntu-20-10-not-even-wired-cable-h: Pro
[Touch-packages] [Bug 1801540]
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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
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. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
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 Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
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 everything is connected on a modern PC; I guess better late than never. I'll keep monitored the situation, but I think that at least for me after this firmware update the issue has been finally fixed. -- 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 Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
(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 a/sound/pci/hda/hda_controller.c b/sound/pci/hda/hda_controller.c > --- a/sound/pci/hda/hda_controller.c 2021-02-10 19:29:23.0 +1100 > +++ b/sound/pci/hda/hda_controller.c 2021-02-14 00:38:36.602466066 +1100 > @@ -609,13 +609,6 @@ >20, >17800); > > - /* by some reason, the playback stream stalls on PulseAudio with > - * tsched=1 when a capture stream triggers. Until we figure out the > - * real cause, disable tsched mode by telling the PCM info flag. > - */ > - if (chip->driver_caps & AZX_DCAPS_AMD_WORKAROUND) > - runtime->hw.info |= SNDRV_PCM_INFO_BATCH; > - > if (chip->align_buffer_size) > /* constrain buffer sizes to be multiple of 128 > bytes. This is more efficient in terms of memory > > > > -- > > It's my opinion that the above reversion should be done in mainline. A > bugfix that fixes a problem over here but creates a new one over there isn't > a bugfix at all. FWIW, on my system this improves the recording start, removing completely audio clicks at the start of recording (no audio stalls in reproduction, even with multiple streams on acquisition while playing audio), so for my use case it's fine, but someone with PulseAudio should test this and see if it causes regressions. -- 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 Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
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 --- a/sound/pci/hda/hda_controller.c2021-02-10 19:29:23.0 +1100 +++ b/sound/pci/hda/hda_controller.c2021-02-14 00:38:36.602466066 +1100 @@ -609,13 +609,6 @@ 20, 17800); - /* by some reason, the playback stream stalls on PulseAudio with -* tsched=1 when a capture stream triggers. Until we figure out the -* real cause, disable tsched mode by telling the PCM info flag. -*/ - if (chip->driver_caps & AZX_DCAPS_AMD_WORKAROUND) - runtime->hw.info |= SNDRV_PCM_INFO_BATCH; - if (chip->align_buffer_size) /* constrain buffer sizes to be multiple of 128 bytes. This is more efficient in terms of memory -- It's my opinion that the above reversion should be done in mainline. A bugfix that fixes a problem over here but creates a new one over there isn't a bugfix at all. -- 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 Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
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 chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
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 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 Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
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 take the delay attribute into account, it's of course unaffected. I don't know whether PipeWire behaves properly for the delay evaluation, though. -- 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 Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
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, apparently, that was only present when using Pci-Ex 4 (B5xx and X5xx, not on b4xx, in theory). However, the USB issues was still present even on older platform, apparently. Just not as grave as the 500 series. The audio clicking is completely gone and the machine is finally much more responsive; I've yet have to test the system under high loads, but even on the desktop the audio clicking was audible sometimes, when event from application fires; after the firmware update, this is completely disappeared. The audio now is perfect, at least in output. I'll update here as soon as I can test the recording now. I didn't think it would change much. But, for me at least, it did. -- 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 Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
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 with 5.10.24 and 5.10.26 here, will test with a 5.11.x kernel later. -- 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 Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
@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 crackling issue, but is completely broken by the changes. It's a difficult situation. -- 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 Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
... 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 So moving it back would break something else, too. Hmm. That said, the behavior might depend on the PCM parameters, or the chip revision, BIOS, or whatever subtle things... -- 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 Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
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 even just capturing from the audio monitor alone has issues, but i haven't confirmed that. -- 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 Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
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, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
(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 had > other issues too (jolting, etc.), so it's possible even just capturing from > the audio monitor alone has issues, but i haven't confirmed that. I have tested this (if i have done it correctly, taken from https://trac.ffmpeg.org/wiki/Capture/Desktop for pulse acquisition, using PipeWire), and besides a small audio missing at the start of the recording of about one second and at the end of it (but that was maybe caused to the ctrl-c to ffmpeg, I'm not sure about that), it looks pretty much synchronized to me, using a microphone next to my mouse and selecting text on the screen I can't really see any delay on it (on the current implemented workaround, Kernel 5.11) Mind you, I'm on a 0x1487 and not on a 0x15e3 host side controller (not an "AMD Raven"), so maybe the behavior of the two controllers are different from each other (or PipeWire is not causing the issue here). Marco. -- 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 Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
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 removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode Status in Ubuntu on IBM z Systems: Fix Committed Status in isc-dhcp package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Committed Status in netplan.io source package in Focal: New Status in systemd source package in Focal: Fix Committed Status in netplan.io source package in Hirsute: New Status in systemd source package in Hirsute: Fix Committed Status in netplan.io source package in Impish: Confirmed Status in systemd source package in Impish: Fix Committed Bug description: ---Problem Description--- IPs are not getting assigned for Hipersockets in DHCP mode Contact Information = Asha Shekharappa(ashsh...@in.ibm.com) Sankar(sankar...@in.ibm.com) ---uname output--- 52-Ubuntu SMP Thu Sep 10 10:59:04 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Ubuntu 20.04 Netplan with systemd-networkd as renderer Creating ethernet connection on Hipersockets device in DHCP mode fails to assign IPs 1. Configure a Hipersockets device chzdev -e 0.0.8f00 2. Create a .yaml file with the below details network: version: 2 ethernets: enc8f00: dhcp4: yes 3. netplan apply 4. The IP is not assigned as seen below root@M96SANKAR:/etc/netplan# ip a s enc8f00: mtu 32768 qdisc mq state UP group default qlen 1000 link/ether fe:da:af:44:08:02 brd ff:ff:ff:ff:ff:ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943125] Re: devscripts breaks apt
** 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 package in Ubuntu: New Status in devscripts package in Ubuntu: New Bug description: Hello, devscripts package seem to break apt installs. using following Dockerfile: FROM ubuntu:impish ENV DEBIAN_FRONTEND noninteractive RUN apt-get update -qq && apt-get install -y nano RUN apt-get update -qq && apt-get install -y devscripts RUN apt-get update -qq && apt-get install -y htop docker build -t test . Will break installing "htop" with random post apt install errors: E: Problem executing scripts APT::Update::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true' E: Sub-process returned an error code Excluding devscripts package will solve the issue. Any idears why devscripts is breaking apt? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1943125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934393] Re: systemd-logind network access is blocked, and breaks remote authentication configurations
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 creation. 4. pam_systemd calls into systemd-logind, over dbus with CreateSession. 5. the running systemd-logind process receives the dbus request and begins setting up the session. 6. systemd-logind attempts to get the full user info via NSS, e.g. getpwuid_r() or similar call 7. glibc attempts the user lookup, doesn't find the UID or username in /etc/passwd using the normal "files" based lookup 8. since nsswitch.conf is configured with network-based authentication (an essential part of this bug), glibc attempts (either through its "compat" mechanism, or separate nss module like libnss_ldap) to open a network connection to the remote authentication server to get the user info 9. since the glibc code, as well as any libnss module loaded by glibc, is running under the systemd-logind process, the network connection fails due to systemd-logind RestrictAddressFamilies= setting 10. nss returns a result of "no user found" to systemd-logind 11. systemd-logind determines it was unable to find the user data for the requested session, so it returns failure over dbus to the pam_systemd module 12. the pam_systemd module returns failure, but since it's marked "optional" (by default) in the pam common-session config file, the application isn't stopped from finishing successful auth 13. the application finishes pam authentication and opens a shell, but without a successful systemd-logind session note that if there is a local caching component to whatever network authentication is configured - e.g. nscd - glibc might attempt to check that locally first, and if the user is located and no remote connection is needed, the lookup will succeed. also note that this bug only applies for nss modules that actually perform network connections directly from the nss module; if the nss module calls a local unix socket into a separate locally running process, that won't be blocked, since systemd-logind is allowed to do AF_UNIX. As has been pointed out and discussed, it really doesn't seem like there are any options to address this other than 1) open up systemd-logind to AF_INET and/or AF_INET6, or 2) provide systemd-logind with a way to perform nss lookups outside of direct nss calls, e.g. userdb. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1934393 Title: systemd-logind network access is blocked, and breaks remote authentication configurations Status in systemd: Fix Released Status in nis package in Ubuntu: Confirmed Status in openldap package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Status in nis package in Debian: Fix Released Bug description: [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 debian bug report, see other info section below [test case] many possible ways to reproduce this; there are reproducers in some of the bugs reported before that are caused by this, e.g. bug 1915502 or bug 1916235 [regression potential] failure to authenticate when using remote user data, incorrect authentication, security issues due to un-sandboxing of systemd-logind [scope] this is needed in f and later before focal, systemd-logind was not sandboxed so this did not apply [other info] this isn't actually a bug in systemd, this is a by-design security feature, and the intended upstream design is for systemd-logind to talk to systemd-userdb, so that systemd-logind can remain network- sandboxed while systemd-userdb performs any needed network access for user/auth data. However, Debian and Ubuntu don't enable/provide systemd-userdb, so that design does not work for Debian/Ubuntu. this also can cause systemd-udevd failures in some cases as well, apparently (based on upstream and debian discussion comments) For reference, upstream discussion around the systemd-logind sandboxing specifically: https://github.com/systemd/systemd/issues/7074 upstream updated doc PR explaining the upstream position: https://github.com/systemd/systemd/pull/7343 Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878625 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1934393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://
[Touch-packages] [Bug 1943130] [NEW] Nvidia drivers info
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 yesterday it was fine but today is broken, and made me to change the driver) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..2b.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.91.03 Fri Jul 2 06:04:10 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Відмовлено у доступі: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 9 15:15:39 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.91.03, 5.11.0-34-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:2208] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8803] InstallationDate: Installed on 2021-08-31 (8 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Micro-Star International Co., Ltd. MS-7C91 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=1bb75479-3578-4389-a29e-40823860bbbc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 05/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG B550 TOMAHAWK (MS-7C91) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.60:bd05/12/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C91:pvr2.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMAGB550TOMAHAWK(MS-7C91):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C91 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal 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/1943130 Title: Nvidia drivers info Status in xorg package in Ubuntu: New Bug description: 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 yesterday it was fine but today is broken, and made me to change the driver) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.
[Touch-packages] [Bug 1943130] Re: Nvidia drivers info
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. https://bugs.launchpad.net/bugs/1943130 Title: Nvidia drivers info Status in xorg package in Ubuntu: New Bug description: 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 yesterday it was fine but today is broken, and made me to change the driver) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..2b.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.91.03 Fri Jul 2 06:04:10 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Відмовлено у доступі: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 9 15:15:39 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.91.03, 5.11.0-34-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:2208] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8803] InstallationDate: Installed on 2021-08-31 (8 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Micro-Star International Co., Ltd. MS-7C91 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=1bb75479-3578-4389-a29e-40823860bbbc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 05/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG B550 TOMAHAWK (MS-7C91) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.60:bd05/12/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C91:pvr2.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMAGB550TOMAHAWK(MS-7C91):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C91 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1943130/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943133] [NEW] Sync expat 2.4.1-1 (main) from Debian experimental (main)
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 (denial-of-service; flavors targeting CPU time or RAM or both, leveraging general entities or parameter entities or both). * Update libexpat1 symbols. -- Laszlo Boszormenyi (GCS) Mon, 24 May 2021 10:14:11 +0200 ** Affects: expat (Ubuntu) Importance: Wishlist Status: New ** Changed in: expat (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1943133 Title: Sync expat 2.4.1-1 (main) from Debian experimental (main) Status in expat package in Ubuntu: New Bug description: 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 (denial-of-service; flavors targeting CPU time or RAM or both, leveraging general entities or parameter entities or both). * Update libexpat1 symbols. -- Laszlo Boszormenyi (GCS) Mon, 24 May 2021 10:14:11 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1943133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1917148] Re: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
[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 necessarily mean that the package under test is actually functional. If a superficial test fails, it will be treated like any other failing test, but if it succeeds, this is only a weak indication of success. Continuous integration systems should treat a package where all non-superficial tests are skipped as equivalent to a package where all tests are skipped. Additionally, since that ".tarball-version" only focus on upstream version "3.3.16". The version won't change unless ones bump the version (which won't happen in stable release) unless under serious exception. So this value is unlikely to be removed or changes any time soon in Focal. Usually, adding autopkgtest inside an SRU is not a desired change. For the above reasons, I think it is safe to skip the autopkgtest and only focus on the version fix. -- 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 package in Ubuntu: Fix Released Status in procps source package in Bionic: Fix Released Status in procps source package in Focal: In Progress Status in procps source package in Hirsute: Fix Released Status in procps source package in Impish: Fix Released Bug description: [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 Groovy/Hirsute+ and Bionic and prior releases. - Focal is the only release affected. * Backported Debian fix to restore ".tarball-version" file to provide version information during build. - Also included the autopkgtests for versioning from the same Debian fix. [Test Plan] 1) Create a Focal (or derived from Focal) system. 2) Execute "ps --version" or any of the binaries provided by the package with their respective version flags. 3) Instead of desired output of the version, the output is: the invoked binary name followed by "from procps-ng UNKNOWN" Example: "ps from procps-ng UNKNOWN" [Where problems could occur] * This fix could cause issues if applications have come to depend on the incorrect behavior. IE, an application that uses a version string of "UNKNOWN" as part of a heuristic for identifying a Focal system. * If the version of procps-ng is incremented, this patch would need to be updated or removed if it is no longer relevant. Otherwise, an incorrect version would be reported by the binaries. * The addition of the autopkgtests could cause testing failures. [Other Info] * This change is in Groovy+ and Debian packaging with the same version of procps-ng. - Introduced in procps (2:3.3.16-5) unstable in Debian. [Original Description] From Linux Lint 20.1, so Focal Fossa 20.04.1 Package procps 2:3.3.16-1ubuntu2 $ LANG=C ps --version ps from procps-ng UNKNOWN I don't know if it comes from Ubuntu or upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1917148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934147] Re: systemd leaks abandoned session scopes
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 sudo -b -i -u ubuntu ssh localhost -- sleep 1; done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl daemon-reload; done Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... ubuntu@lp1934147-h:~$ loginctl list-sessions SESSION UID USER SEAT TTY 1 1000 ubuntu ttyS0 54 1000 ubuntu 67 1000 ubuntu 71 1000 ubuntu 77 1000 ubuntu 5 sessions listed. ubuntu@lp1934147-h:~$ ubuntu@lp1934147-h:~$ dpkg -l systemd|grep systemd ii systemd247.3-3ubuntu3.6 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 sudo -b -i -u ubuntu ssh localhost -- sleep 1; done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl daemon-reload; done Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... ubuntu@lp1934147-h:~$ loginctl list-sessions SESSION UID USER SEAT TTY 1 1000 ubuntu ttyS0 1 sessions listed. -- 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/1934147 Title: systemd leaks abandoned session scopes Status in snapd: New Status in systemd: New Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Won't Fix Status in systemd source package in Hirsute: Fix Committed Status in systemd source package in Impish: Fix Committed Bug description: [impact] systemd may leak sessions, leaving empty cgroups around as well as abandoned session scopes. [test case] on a system where the user has a ssh key that allows noninteractive login to localhost, and also has noninteractive sudo, run: $ for i in {1..100}; do sudo -b -i -u ubuntu ssh localhost -- sleep 1; done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl daemon- reload; done check the sessions to see there have been leaked sessions: $ loginctl list-sessions SESSION UID USER SEAT TTY 1 1000 ubuntu ttyS0 350 1000 ubuntu 351 1000 ubuntu 360 1000 ubuntu ... to verify the sessions were leaked, clear them out with: $ echo '' | sudo tee /sys/fs/cgroup/unified/user.slice/user-1000.slice/session-*.scope/cgroup.events that should result in all the leaked sessions being cleaned up. [regression potential] issues during systemd pid1 reexec/reload, or issues while cleaning up sessions, including leaking sessions/cgroups [scope] this is needed for all releases upstream bug linked above, and upstream PR: https://github.com/systemd/systemd/pull/20199 [original description] On a system that is monitored via telegraf I found many abandoned systemd session which I believe are created by a potential race where systemd is reloading unit files and at the same time a user is connecting to the system via ssh or is executing the su command. The simple reproducer $ for i in {1..100}; do sleep 0.2; ssh localhost sudo systemctl daemon-reload & ssh localhost sleep 1 & done Wait > 1 second $ jobs -p | xargs --verbose --no-run-if-empty kill -KILL To clean out STOPPED jobs and $ systemctl status --all 2> /dev/null | grep --before-context 3 abandoned will produce something similar to │ ├─ 175 su - ubuntu │ ├─ 178 -su │ ├─62375 systemctl status --all │ └─62376 grep --color=auto --before-context 3 abandoned -- ● session-273.scope - Session 273 of user ubuntu Loaded: loaded (/run/systemd/transient/session-273.scope; transient) Transient: yes Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago -- ● session-274.scope - Session 274 of user ubuntu Loaded: loaded (/run/systemd/transient/session-274.scope; transient) Transient: yes Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago -- ● session-30.scope - Session 30 of user ubuntu Loaded: loaded (/run/systemd/transient/session-30.scope; tr
[Touch-packages] [Bug 1934147] Re: systemd leaks abandoned session scopes
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 sudo -b -i -u ubuntu ssh localhost -- sleep 1; done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl daemon-reload; done Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... ubuntu@lp1934147-f:~$ loginctl list-sessions SESSION UID USER SEAT TTY 1 1000 ubuntu ttyS0 64 1000 ubuntu 69 1000 ubuntu 74 1000 ubuntu 76 1000 ubuntu 82 1000 ubuntu 88 1000 ubuntu 94 1000 ubuntu 95 1000 ubuntu 9 sessions listed. ubuntu@lp1934147-f:~$ dpkg -l systemd|grep systemd ii systemd245.4-4ubuntu3.13 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 sudo -b -i -u ubuntu ssh localhost -- sleep 1; done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl daemon-reload; done Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... Reloading... ubuntu@lp1934147-f:~$ loginctl list-sessions SESSION UID USER SEAT TTY 1 1000 ubuntu ttyS0 1 sessions listed. ** Tags removed: verification-needed verification-needed-focal verification-needed-hirsute ** Tags added: verification-done verification-done-focal verification-done-hirsute -- 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/1934147 Title: systemd leaks abandoned session scopes Status in snapd: New Status in systemd: New Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Won't Fix Status in systemd source package in Hirsute: Fix Committed Status in systemd source package in Impish: Fix Committed Bug description: [impact] systemd may leak sessions, leaving empty cgroups around as well as abandoned session scopes. [test case] on a system where the user has a ssh key that allows noninteractive login to localhost, and also has noninteractive sudo, run: $ for i in {1..100}; do sudo -b -i -u ubuntu ssh localhost -- sleep 1; done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl daemon- reload; done check the sessions to see there have been leaked sessions: $ loginctl list-sessions SESSION UID USER SEAT TTY 1 1000 ubuntu ttyS0 350 1000 ubuntu 351 1000 ubuntu 360 1000 ubuntu ... to verify the sessions were leaked, clear them out with: $ echo '' | sudo tee /sys/fs/cgroup/unified/user.slice/user-1000.slice/session-*.scope/cgroup.events that should result in all the leaked sessions being cleaned up. [regression potential] issues during systemd pid1 reexec/reload, or issues while cleaning up sessions, including leaking sessions/cgroups [scope] this is needed for all releases upstream bug linked above, and upstream PR: https://github.com/systemd/systemd/pull/20199 [original description] On a system that is monitored via telegraf I found many abandoned systemd session which I believe are created by a potential race where systemd is reloading unit files and at the same time a user is connecting to the system via ssh or is executing the su command. The simple reproducer $ for i in {1..100}; do sleep 0.2; ssh localhost sudo systemctl daemon-reload & ssh localhost sleep 1 & done Wait > 1 second $ jobs -p | xargs --verbose --no-run-if-empty kill -KILL To clean out STOPPED jobs and $ systemctl status --all 2> /dev/null | grep --before-context 3 abandoned will produce something similar to │ ├─ 175 su - ubuntu │ ├─ 178 -su │ ├─62375 systemctl status --all │ └─62376 grep --color=auto --before-context 3 abandoned -- ● session-273.scope - Session 273 of user ubuntu Loaded: loaded (/run/systemd/transient/session-273.scope; transient) Transient: yes Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago -- ● session-274.scope - Session
[Touch-packages] [Bug 1917148] Re: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
** 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 Groovy/Hirsute+ and Bionic and prior releases. - Focal is the only release affected. * Backported Debian fix to restore ".tarball-version" file to provide version information during build. - Also included the autopkgtests for versioning from the same Debian fix. [Test Plan] 1) Create a Focal (or derived from Focal) system. 2) Execute "ps --version" or any of the binaries provided by the package with their respective version flags. 3) Instead of desired output of the version, the output is: the invoked binary name followed by "from procps-ng UNKNOWN" Example: "ps from procps-ng UNKNOWN" [Where problems could occur] * This fix could cause issues if applications have come to depend on the incorrect behavior. IE, an application that uses a version string of "UNKNOWN" as part of a heuristic for identifying a Focal system. * If the version of procps-ng is incremented, this patch would need to be updated or removed if it is no longer relevant. Otherwise, an incorrect version would be reported by the binaries. - * The addition of the autopkgtests could cause testing failures. [Other Info] * This change is in Groovy+ and Debian packaging with the same version of procps-ng. - Introduced in procps (2:3.3.16-5) unstable in Debian. [Original Description] From Linux Lint 20.1, so Focal Fossa 20.04.1 Package procps 2:3.3.16-1ubuntu2 $ LANG=C ps --version ps from procps-ng UNKNOWN I don't know if it comes from Ubuntu or upstream. -- 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 package in Ubuntu: Fix Released Status in procps source package in Bionic: Fix Released Status in procps source package in Focal: In Progress Status in procps source package in Hirsute: Fix Released Status in procps source package in Impish: Fix Released Bug description: [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 Groovy/Hirsute+ and Bionic and prior releases. - Focal is the only release affected. * Backported Debian fix to restore ".tarball-version" file to provide version information during build. - Also included the autopkgtests for versioning from the same Debian fix. [Test Plan] 1) Create a Focal (or derived from Focal) system. 2) Execute "ps --version" or any of the binaries provided by the package with their respective version flags. 3) Instead of desired output of the version, the output is: the invoked binary name followed by "from procps-ng UNKNOWN" Example: "ps from procps-ng UNKNOWN" [Where problems could occur] * This fix could cause issues if applications have come to depend on the incorrect behavior. IE, an application that uses a version string of "UNKNOWN" as part of a heuristic for identifying a Focal system. * If the version of procps-ng is incremented, this patch would need to be updated or removed if it is no longer relevant. Otherwise, an incorrect version would be reported by the binaries. [Other Info] * This change is in Groovy+ and Debian packaging with the same version of procps-ng. - Introduced in procps (2:3.3.16-5) unstable in Debian. [Original Description] From Linux Lint 20.1, so Focal Fossa 20.04.1 Package procps 2:3.3.16-1ubuntu2 $ LANG=C ps --version ps from procps-ng UNKNOWN I don't know if it comes from Ubuntu or upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1917148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1936948] Re: Dependency loop via sockets.target
** 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. All services registering at the same time, seems to be triggering bugs like this more often: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1871538/ This happens since Hirsute (dbus 1.12.20-1ubuntu3), where the following delta was added: Index: dbus-1.12.20/bus/dbus.socket.in === --- dbus-1.12.20.orig/bus/dbus.socket.in +++ dbus-1.12.20/bus/dbus.socket.in @@ -1,5 +1,9 @@ - [Unit] - Description=D-Bus System Message Bus Socket + [Unit] + Description=D-Bus System Message Bus Socket +# Do not stop on shutdown +DefaultDependencies=no +Wants=sysinit.target +After=sysinit.target basic.target - [Socket] - ListenStream=@DBUS_SYSTEM_SOCKET@ + [Socket] + ListenStream=@DBUS_SYSTEM_SOCKET@ + + It leads to deadlock situations like this: + 09:23:59.276245 systemd[1]: basic.target: starting held back, waiting for: sockets.target + 09:23:59.276438 systemd[1]: dbus.socket: starting held back, waiting for: basic.target + 09:23:59.304393 systemd[1]: dbus.service: starting held back, waiting for: dbus.socket -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1936948 Title: Dependency loop via sockets.target Status in dbus package in Ubuntu: Confirmed Status in dbus source package in Impish: Confirmed Bug description: 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. All services registering at the same time, seems to be triggering bugs like this more often: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1871538/ This happens since Hirsute (dbus 1.12.20-1ubuntu3), where the following delta was added: Index: dbus-1.12.20/bus/dbus.socket.in === --- dbus-1.12.20.orig/bus/dbus.socket.in +++ dbus-1.12.20/bus/dbus.socket.in @@ -1,5 +1,9 @@ [Unit] Description=D-Bus System Message Bus Socket +# Do not stop on shutdown +DefaultDependencies=no +Wants=sysinit.target +After=sysinit.target basic.target [Socket] ListenStream=@DBUS_SYSTEM_SOCKET@ It leads to deadlock situations like this: 09:23:59.276245 systemd[1]: basic.target: starting held back, waiting for: sockets.target 09:23:59.276438 systemd[1]: dbus.socket: starting held back, waiting for: basic.target 09:23:59.304393 systemd[1]: dbus.service: starting held back, waiting for: dbus.socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1936948/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934981] Re: systemctl suspend-then-hibernate attempts hybrid-sleep instead
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 suspend-then-hibernate Failed to suspend system, hibernate later via logind: Sleep verb "hybrid-sleep" not supported ubuntu@lp1934981-h:~$ ubuntu@lp1934981-h:~$ dpkg -l systemd|grep systemd ii systemd247.3-3ubuntu3.6 amd64system and service manager ubuntu@lp1934981-h:~$ grep -E '^Allow' /etc/systemd/sleep.conf AllowSuspendThenHibernate=yes AllowHybridSleep=no ubuntu@lp1934981-h:~$ sudo systemctl suspend-then-hibernate ubuntu@lp1934981-h:~$ -- 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/1934981 Title: systemctl suspend-then-hibernate attempts hybrid-sleep instead Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Won't Fix Status in systemd source package in Hirsute: Fix Committed Status in systemd source package in Impish: Fix Committed Bug description: [impact] suspend-then-hibernate not possible using systemctl [test case] configure a system (that has enough swap to be able to hibernate) to allow suspend-then-hibernate but not hybrid-sleep, e.g. by editing /etc/systemd/sleep.conf to set AllowSuspendThenHibernate=yes and AllowHybridSleep=no, then try it: $ sudo systemctl suspend-then-hibernate Failed to suspend system, hibernate later via logind: Sleep verb "hybrid-sleep" not supported note that on bionic, the Allow...= params do not exist, instead we can reproduce the error by setting one of the hybrid parameters to an invalid value, e.g. HybridSleepState=bugverification [regression potential] failure to correctly enter hybrid-sleep and/or suspend-then-hibernate, or other issues around suspending/hibernating [scope] This is needed in b and later. The bug appears to have been introduced by a typo in the original suspend-then-hibernate commit c58493c00af, and then fixed with larger changes in commit c8cd8ca3986. this is also present in b, by a backport of the functionality [other info] note that if hybrid-sleep is allowed/possible, then calling 'systemctl suspend-then-hibernate' does actually perform suspend-then-hibernate; this typo only controls what suspend action logind checks for support of, not what suspend action it actually performs. [original description] ``` systemctl suspend-then-hibernate Failed to suspend system, hibernate later via logind: Sleep verb "hybrid-sleep" not supported ``` Note the verb change! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 8 08:54:01 2021 InstallationDate: Installed on 2021-07-06 (1 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=/dev/mapper/username-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/03/2021 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0PP9G2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd02/03/2021:br1.5:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0PP9G2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. mtime.conffile..etc.systemd.sleep.conf: 2021-07-08T08:51:57.213321 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934981/+
[Touch-packages] [Bug 1917148] Re: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
[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 3.3.16 root@procpsf:/tmp# free --version free from procps-ng 3.3.16 - Eric -- 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 package in Ubuntu: Fix Released Status in procps source package in Bionic: Fix Released Status in procps source package in Focal: In Progress Status in procps source package in Hirsute: Fix Released Status in procps source package in Impish: Fix Released Bug description: [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 Groovy/Hirsute+ and Bionic and prior releases. - Focal is the only release affected. * Backported Debian fix to restore ".tarball-version" file to provide version information during build. - Also included the autopkgtests for versioning from the same Debian fix. [Test Plan] 1) Create a Focal (or derived from Focal) system. 2) Execute "ps --version" or any of the binaries provided by the package with their respective version flags. 3) Instead of desired output of the version, the output is: the invoked binary name followed by "from procps-ng UNKNOWN" Example: "ps from procps-ng UNKNOWN" [Where problems could occur] * This fix could cause issues if applications have come to depend on the incorrect behavior. IE, an application that uses a version string of "UNKNOWN" as part of a heuristic for identifying a Focal system. * If the version of procps-ng is incremented, this patch would need to be updated or removed if it is no longer relevant. Otherwise, an incorrect version would be reported by the binaries. [Other Info] * This change is in Groovy+ and Debian packaging with the same version of procps-ng. - Introduced in procps (2:3.3.16-5) unstable in Debian. [Original Description] From Linux Lint 20.1, so Focal Fossa 20.04.1 Package procps 2:3.3.16-1ubuntu2 $ LANG=C ps --version ps from procps-ng UNKNOWN I don't know if it comes from Ubuntu or upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1917148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934981] Re: systemctl suspend-then-hibernate attempts hybrid-sleep instead
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 suspend-then-hibernate Failed to suspend system, hibernate later via logind: Sleep verb "hybrid-sleep" not supported ubuntu@lp1934981-f:~$ ubuntu@lp1934981-f:~$ dpkg -l systemd|grep systemd ii systemd245.4-4ubuntu3.13 amd64system and service manager ubuntu@lp1934981-f:~$ grep -E '^Allow' /etc/systemd/sleep.conf AllowSuspendThenHibernate=yes AllowHybridSleep=no ubuntu@lp1934981-f:~$ sudo systemctl suspend-then-hibernate ubuntu@lp1934981-f:~$ ** Tags removed: verification-needed verification-needed-focal verification-needed-hirsute ** Tags added: verification-done verification-done-focal verification-done-hirsute -- 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/1934981 Title: systemctl suspend-then-hibernate attempts hybrid-sleep instead Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Won't Fix Status in systemd source package in Hirsute: Fix Committed Status in systemd source package in Impish: Fix Committed Bug description: [impact] suspend-then-hibernate not possible using systemctl [test case] configure a system (that has enough swap to be able to hibernate) to allow suspend-then-hibernate but not hybrid-sleep, e.g. by editing /etc/systemd/sleep.conf to set AllowSuspendThenHibernate=yes and AllowHybridSleep=no, then try it: $ sudo systemctl suspend-then-hibernate Failed to suspend system, hibernate later via logind: Sleep verb "hybrid-sleep" not supported note that on bionic, the Allow...= params do not exist, instead we can reproduce the error by setting one of the hybrid parameters to an invalid value, e.g. HybridSleepState=bugverification [regression potential] failure to correctly enter hybrid-sleep and/or suspend-then-hibernate, or other issues around suspending/hibernating [scope] This is needed in b and later. The bug appears to have been introduced by a typo in the original suspend-then-hibernate commit c58493c00af, and then fixed with larger changes in commit c8cd8ca3986. this is also present in b, by a backport of the functionality [other info] note that if hybrid-sleep is allowed/possible, then calling 'systemctl suspend-then-hibernate' does actually perform suspend-then-hibernate; this typo only controls what suspend action logind checks for support of, not what suspend action it actually performs. [original description] ``` systemctl suspend-then-hibernate Failed to suspend system, hibernate later via logind: Sleep verb "hybrid-sleep" not supported ``` Note the verb change! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 8 08:54:01 2021 InstallationDate: Installed on 2021-07-06 (1 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=/dev/mapper/username-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/03/2021 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0PP9G2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd02/03/2021:br1.5:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0PP9G2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc.
[Touch-packages] [Bug 1943137] [NEW] Mouse is connected however input does not move cursor
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 connected because: - keyboard works for the microsoft sculpt - the logitech mouse is detected by the solar app i use to configure it. - they both work during login ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 9 09:19:31 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-27-generic, x86_64: installed nvidia, 470.57.02, 5.11.0-34-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:098f] NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f12] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:098f] InstallationDate: Installed on 2021-03-25 (167 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=1cef9c97-5ee0-47f7-aa9e-da9d48059d31 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0CXCCY dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd05/21/2021:br1.8:svnDellInc.:pnXPS179700:pvr:sku098F:rvnDellInc.:rn0CXCCY:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages 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/1943137 Title: Mouse is connected however input does not move cursor Status in xorg package in Ubuntu: New Bug description: 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 connected because: - keyboard works for the microsoft sculpt - the logitech mouse is detected by the solar app i use to configure it. - they both work during login ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.d
[Touch-packages] [Bug 1942899] Re: Revert Add ACCEL_LOCATION=base property for Dell clamshell models
** 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 lack of the new 'sku' lines, and presence of the old lines, + should be enough to verify this revert is correct [regression potential] any regression would likely be restricted to dell clamshell models matching the modified config settings [scope] the incorrect patch was added in f/h/i so only those need the patch removed/reverted [other info] this only reverts the patch that was added for bug 1938259, as the bug reporter indicated in that bug in comment 15 that the patch did not actually work correctly. a correct patch will need to go upstream first, so this bug is just to revert the last patch and respin systemd for all releases -- 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/1942899 Title: Revert Add ACCEL_LOCATION=base property for Dell clamshell models Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: Fix Committed Status in systemd source package in Impish: Fix Committed Bug description: [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 lack of the new 'sku' lines, and presence of the old lines, should be enough to verify this revert is correct [regression potential] any regression would likely be restricted to dell clamshell models matching the modified config settings [scope] the incorrect patch was added in f/h/i so only those need the patch removed/reverted [other info] this only reverts the patch that was added for bug 1938259, as the bug reporter indicated in that bug in comment 15 that the patch did not actually work correctly. a correct patch will need to go upstream first, so this bug is just to revert the last patch and respin systemd for all releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1942899/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1917148] Re: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
** 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 package in Ubuntu: Fix Released Status in procps source package in Bionic: Fix Released Status in procps source package in Focal: In Progress Status in procps source package in Hirsute: Fix Released Status in procps source package in Impish: Fix Released Bug description: [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 Groovy/Hirsute+ and Bionic and prior releases. - Focal is the only release affected. * Backported Debian fix to restore ".tarball-version" file to provide version information during build. - Also included the autopkgtests for versioning from the same Debian fix. [Test Plan] 1) Create a Focal (or derived from Focal) system. 2) Execute "ps --version" or any of the binaries provided by the package with their respective version flags. 3) Instead of desired output of the version, the output is: the invoked binary name followed by "from procps-ng UNKNOWN" Example: "ps from procps-ng UNKNOWN" [Where problems could occur] * This fix could cause issues if applications have come to depend on the incorrect behavior. IE, an application that uses a version string of "UNKNOWN" as part of a heuristic for identifying a Focal system. * If the version of procps-ng is incremented, this patch would need to be updated or removed if it is no longer relevant. Otherwise, an incorrect version would be reported by the binaries. [Other Info] * This change is in Groovy+ and Debian packaging with the same version of procps-ng. - Introduced in procps (2:3.3.16-5) unstable in Debian. [Original Description] From Linux Lint 20.1, so Focal Fossa 20.04.1 Package procps 2:3.3.16-1ubuntu2 $ LANG=C ps --version ps from procps-ng UNKNOWN I don't know if it comes from Ubuntu or upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1917148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942899] Re: Revert Add ACCEL_LOCATION=base property for Dell clamshell models
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 ubuntu@lp1942899-h:~$ grep -E 'pnLatitude7420|pnLatitude9520|sku0B0B|sku0A3E' /lib/udev/hwdb.d/60-sensor.hwdb sensor:modalias:platform:HID-SENSOR-200073:dmi:*svnDell*:pnLatitude9520:*:ct10:* sensor:modalias:platform:HID-SENSOR-200073:dmi:*svnDell*:pnLatitude7420:* ubuntu@lp1942899-h:~$ ubuntu@lp1942899-h:~$ dpkg -l systemd|grep systemd ii systemd247.3-3ubuntu3.6 amd64system and service manager ubuntu@lp1942899-h:~$ grep -E 'pnLatitude7420|pnLatitude9520|sku0B0B|sku0A3E' /lib/udev/hwdb.d/60-sensor.hwdb sensor:modalias:platform:HID-SENSOR-200073:dmi:*svnDell*:pnLatitude9520:*:ct10:* sensor:modalias:platform:HID-SENSOR-200073:dmi:*svnDell*:pnLatitude7420:* ubuntu@lp1942899-h:~$ -- 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/1942899 Title: Revert Add ACCEL_LOCATION=base property for Dell clamshell models Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: Fix Committed Status in systemd source package in Impish: Fix Committed Bug description: [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 lack of the new 'sku' lines, and presence of the old lines, should be enough to verify this revert is correct [regression potential] any regression would likely be restricted to dell clamshell models matching the modified config settings [scope] the incorrect patch was added in f/h/i so only those need the patch removed/reverted [other info] this only reverts the patch that was added for bug 1938259, as the bug reporter indicated in that bug in comment 15 that the patch did not actually work correctly. a correct patch will need to go upstream first, so this bug is just to revert the last patch and respin systemd for all releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1942899/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942899] Re: Revert Add ACCEL_LOCATION=base property for Dell clamshell models
commit to focal that needed reverting: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?h=ubuntu-focal&id=5c1be33900edee94da0dc9a4ade8edcd079b4c85 ubuntu@lp1942899-f:~$ dpkg -l systemd|grep systemd ii systemd245.4-4ubuntu3.11 amd64system and service manager ubuntu@lp1942899-f:~$ grep -E 'sku0A3E|sku0B0B' /lib/udev/hwdb.d/60-sensor.hwdb ubuntu@lp1942899-f:~$ ubuntu@lp1942899-f:~$ dpkg -l systemd|grep systemd ii systemd245.4-4ubuntu3.13 amd64system and service manager ubuntu@lp1942899-f:~$ grep -E 'sku0A3E|sku0B0B' /lib/udev/hwdb.d/60-sensor.hwdb ubuntu@lp1942899-f:~$ -- 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/1942899 Title: Revert Add ACCEL_LOCATION=base property for Dell clamshell models Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: Fix Committed Status in systemd source package in Impish: Fix Committed Bug description: [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 lack of the new 'sku' lines, and presence of the old lines, should be enough to verify this revert is correct [regression potential] any regression would likely be restricted to dell clamshell models matching the modified config settings [scope] the incorrect patch was added in f/h/i so only those need the patch removed/reverted [other info] this only reverts the patch that was added for bug 1938259, as the bug reporter indicated in that bug in comment 15 that the patch did not actually work correctly. a correct patch will need to go upstream first, so this bug is just to revert the last patch and respin systemd for all releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1942899/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942899] Re: Revert Add ACCEL_LOCATION=base property for Dell clamshell models
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 notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1942899 Title: Revert Add ACCEL_LOCATION=base property for Dell clamshell models Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: Fix Committed Status in systemd source package in Impish: Fix Committed Bug description: [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 lack of the new 'sku' lines, and presence of the old lines, should be enough to verify this revert is correct [regression potential] any regression would likely be restricted to dell clamshell models matching the modified config settings [scope] the incorrect patch was added in f/h/i so only those need the patch removed/reverted [other info] this only reverts the patch that was added for bug 1938259, as the bug reporter indicated in that bug in comment 15 that the patch did not actually work correctly. a correct patch will need to go upstream first, so this bug is just to revert the last patch and respin systemd for all releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1942899/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853164] Re: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
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 in Ubuntu. https://bugs.launchpad.net/bugs/1853164 Title: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [impact] with systemd-resolved disabled, dhclient doesn't correctly notify resolvconf about dns server(s) [test case] install resolvconf and ifupdown and disable systemd-resolved and systemd-networkd, use ifupdown to get a dhcp address where the lease includes a dns nameserver, verify resolvconf is using that dhcp- provided nameserver [regression potential] failure to correctly notify systemd-resolved about new dhclient- provided nameserver(s) [scope] this is needed for f and earlier in g and later the hook script is moved to the isc-dhcp package, and edited to correctly check is-enabled systemd-resolved instead of only checking for the existence of the binary [original description] The functionality exists to allow users to revert to the traditional ifupdown package for network configuration. Alongside this, systemd's often-buggy resolver can be disabled. However, there's a logic error in the systemd- supplied /etc/dhcp/dhclient-enter-hooks.d/resolved that prevents the system from populating /etc/resolv.conf properly when systemd-resolved is disabled. The issue is here: if [ -x /lib/systemd/systemd-resolved ] ; then Instead of checking to see if the systemd-resolved service is enabled or active, which would be the correct behaviour, this checks for the existence of a binary, assuming that if it exists it's supposed to be used. I've not tested this in the absence of resolvconf, but if systemd-resolved isn't enabled, it's difficult to imagine this code wanting to run. I've tested this with resolvconf and ifupdown driving dhclient, and it corrects the behaviour that was broken with the introduction of systemd-resolved. I'm attaching a patch, and am also including it here for easy access: *** resolved.broken 2019-11-19 15:01:28.785588838 + --- resolved2019-11-19 15:08:06.519430073 + *** *** 14,20 # (D) = master script downs interface # (-) = master script does nothing with this ! if [ -x /lib/systemd/systemd-resolved ] ; then # For safety, first undefine the nasty default make_resolv_conf() make_resolv_conf() { : ; } case "$reason" in --- 14,21 # (D) = master script downs interface # (-) = master script does nothing with this ! systemctl is-active systemd-resolved > /dev/null 2>&1 ! if [ $? -eq 0 ]; then # For safety, first undefine the nasty default make_resolv_conf() make_resolv_conf() { : ; } case "$reason" in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853164/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853164] Re: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
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 seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1853164 Title: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [impact] with systemd-resolved disabled, dhclient doesn't correctly notify resolvconf about dns server(s) [test case] install resolvconf and ifupdown and disable systemd-resolved and systemd-networkd, use ifupdown to get a dhcp address where the lease includes a dns nameserver, verify resolvconf is using that dhcp- provided nameserver [regression potential] failure to correctly notify systemd-resolved about new dhclient- provided nameserver(s) [scope] this is needed for f and earlier in g and later the hook script is moved to the isc-dhcp package, and edited to correctly check is-enabled systemd-resolved instead of only checking for the existence of the binary [original description] The functionality exists to allow users to revert to the traditional ifupdown package for network configuration. Alongside this, systemd's often-buggy resolver can be disabled. However, there's a logic error in the systemd- supplied /etc/dhcp/dhclient-enter-hooks.d/resolved that prevents the system from populating /etc/resolv.conf properly when systemd-resolved is disabled. The issue is here: if [ -x /lib/systemd/systemd-resolved ] ; then Instead of checking to see if the systemd-resolved service is enabled or active, which would be the correct behaviour, this checks for the existence of a binary, assuming that if it exists it's supposed to be used. I've not tested this in the absence of resolvconf, but if systemd-resolved isn't enabled, it's difficult to imagine this code wanting to run. I've tested this with resolvconf and ifupdown driving dhclient, and it corrects the behaviour that was broken with the introduction of systemd-resolved. I'm attaching a patch, and am also including it here for easy access: *** resolved.broken 2019-11-19 15:01:28.785588838 + --- resolved2019-11-19 15:08:06.519430073 + *** *** 14,20 # (D) = master script downs interface # (-) = master script does nothing with this ! if [ -x /lib/systemd/systemd-resolved ] ; then # For safety, first undefine the nasty default make_resolv_conf() make_resolv_conf() { : ; } case "$reason" in --- 14,21 # (D) = master script downs interface # (-) = master script does nothing with this ! systemctl is-active systemd-resolved > /dev/null 2>&1 ! if [ $? -eq 0 ]; then # For safety, first undefine the nasty default make_resolv_conf() make_resolv_conf() { : ; } case "$reason" in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853164/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853164] Re: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
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 configure network interfaces ii resolvconf 1.79ubuntu10.18.04.3all name server information handler root@lp1853164-b:~# grep eth0 /etc/network/interfaces auto eth0 iface eth0 inet dhcp root@lp1853164-b:~# ip a show dev eth0 222: eth0@if223: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:16:3e:16:1c:78 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 10.202.51.62/24 brd 10.202.51.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::216:3eff:fe16:1c78/64 scope link valid_lft forever preferred_lft forever root@lp1853164-b:~# systemctl is-enabled systemd-resolved disabled root@lp1853164-b:~# systemctl is-enabled systemd-networkd disabled root@lp1853164-b:~# cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. root@lp1853164-b:~# root@lp1853164-b:~# dpkg -l systemd|grep systemd ii systemd237-3ubuntu10.52 amd64system and service manager root@lp1853164-b:~# dpkg -l | grep -E 'ifupdown|resolvconf' ii ifupdown 0.8.17ubuntu1.1 amd64 high level tools to configure network interfaces ii resolvconf 1.79ubuntu10.18.04.3all name server information handler root@lp1853164-b:~# grep eth0 /etc/network/interfaces auto eth0 iface eth0 inet dhcp root@lp1853164-b:~# ip a show dev eth0 224: eth0@if225: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:16:3e:16:1c:78 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 10.202.51.62/24 brd 10.202.51.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::216:3eff:fe16:1c78/64 scope link valid_lft forever preferred_lft forever root@lp1853164-b:~# systemctl is-enabled systemd-resolved disabled root@lp1853164-b:~# systemctl is-enabled systemd-networkd disabled root@lp1853164-b:~# cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 10.202.51.1 search lxd root@lp1853164-b:~# ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1853164 Title: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [impact] with systemd-resolved disabled, dhclient doesn't correctly notify resolvconf about dns server(s) [test case] install resolvconf and ifupdown and disable systemd-resolved and systemd-networkd, use ifupdown to get a dhcp address where the lease includes a dns nameserver, verify resolvconf is using that dhcp- provided nameserver [regression potential] failure to correctly notify systemd-resolved about new dhclient- provided nameserver(s) [scope] this is needed for f and earlier in g and later the hook script is moved to the isc-dhcp package, and edited to correctly check is-enabled systemd-resolved instead of only checking for the existence of the binary [original description] The functionality exists to allow users to revert to the traditional ifupdown package for network configuration. Alongside this, systemd's often-buggy resolver can be disabled. However, there's a logic error in the systemd- supplied /etc/dhcp/dhclient-enter-hooks.d/resolved that prevents the system from populating /etc/resolv.conf properly when systemd-resolved is disabled. The issue is here: if [ -x /lib/systemd/systemd-resolved ] ; then Instead of checking to see if the systemd-resolved service is enabled or active, which would be the correct behaviour, this checks for the existence of a binary, assuming that if it exists it's supposed to be used. I've not tested this in the absence of resolvconf, but if systemd-resolved isn't enabled, it's difficult to imagine this code wanting to run. I've tested this with resolvconf and ifupdown dri
[Touch-packages] [Bug 1937238] Re: systemd-time-wait-sync.service stuck in "activating" state after boot, blocks timers from starting
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: verification-done verification-done-focal -- 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/1937238 Title: systemd-time-wait-sync.service stuck in "activating" state after boot, blocks timers from starting Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [impact] systemd-time-wait-sync service sometimes misses sync completed event and remains in 'activating' state [test case] this isn't consistently reproducable, see original description for test case [regression potential] possible problems with the systemd-time-wait-sync service completing too early or not completing on time [scope] this is needed only for f this is fixed upstream with commit f6f4f5fe5395a57f10dd446c7266c53f0673eaac which is in v246, so this is fixed in h and later already the service does not exist in b so this does not apply there [original description] When I start my server running Ubuntu 20.04 the systemd-time-wait- sync.service is stuck in "activating" state. I noticed this because none of the systemd timer units triggered, because all the timers depend on systemd-time-wait-sync.service. Running "systemctl restart systemd-time-wait-sync.service" manually works around the problem. Some logs and command outputs: raek@mizar:~$ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 raek@mizar:~$ systemctl | grep systemd-time-wait-sync.service systemd-time-wait-sync.service loaded activating start start Wait Until Kernel Time Synchronized raek@mizar:~$ systemctl status systemd-time-wait-sync.service ● systemd-time-wait-sync.service - Wait Until Kernel Time Synchronized Loaded: loaded (/lib/systemd/system/systemd-time-wait-sync.service; enabled; vendor preset: enabled) Active: activating (start) since Thu 2021-07-22 11:06:52 CEST; 27min ago Docs: man:systemd-time-wait-sync.service(8) Main PID: 514 (systemd-time-wa) Tasks: 1 (limit: 9415) Memory: 972.0K CGroup: /system.slice/systemd-time-wait-sync.service └─514 /lib/systemd/systemd-time-wait-sync Jul 22 11:06:52 mizar systemd-time-wait-sync[514]: adjtime state 5 status 40 time Thu 2021-07-22 09:06:52.216338 UTC Warning: journal has been rotated since unit was started, output may be incomplete. raek@mizar:~$ journalctl -b -u systemd-time-wait-sync.service -- Logs begin at Wed 2020-07-08 16:34:13 CEST, end at Thu 2021-07-22 11:36:44 CEST. -- Jul 22 11:06:52 mizar systemd-time-wait-sync[514]: adjtime state 5 status 40 time Thu 2021-07-22 09:06:52.216338 UTC raek@mizar:~$ dpkg -S /lib/systemd/system/systemd-time-wait-sync.service systemd: /lib/systemd/system/systemd-time-wait-sync.service raek@mizar:~$ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3.11 Candidate: 245.4-4ubuntu3.11 Version table: *** 245.4-4ubuntu3.11 500 500 http://se.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 245.4-4ubuntu3.10 500 500 http://se.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 245.4-4ubuntu3.8 400 400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 245.4-4ubuntu3 500 500 http://se.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939255] Re: dhclient triggers systemd-resolved start limit when processing more than 5 interfaces at once
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 added: verification-done verification-done-focal -- 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/1939255 Title: dhclient triggers systemd-resolved start limit when processing more than 5 interfaces at once Status in systemd package in Ubuntu: Invalid Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Bug description: [impact] on a system where systemd-resolved is running, if dhclient is used on more than 5 interfaces, it calls the '/etc/dhcp/dhclient-enter- hooks.d/resolved' script multiple times, which then restarts systemd- resolved multiple times, triggering the unit's start-limit throttle which results in the unit entering failed state [test case] on a system with more than 5 available interfaces to run dhclient on (where all the interfaces will get a dhcp response), run dhclient with the interfaces: $ dhclient ens8 ens9 ens10 ens11 ens12 ens13 ens14 ens15 check if systemd-resolved failed: $ journalctl -b -1 -u systemd-resolved ... Aug 09 00:38:08 sf316232-b systemd[1]: systemd-resolved.service: Start request repeated too quickly. Aug 09 00:38:08 sf316232-b systemd[1]: systemd-resolved.service: Failed with result 'start-limit-hit'. Aug 09 00:38:08 sf316232-b systemd[1]: Failed to start Network Name Resolution. [regression potential] failure to start/stop/restart systemd-resolved, or problems adding dhclient-provided DNS nameservers to systemd-resolved [scope] this is needed only for b/f the dhclient 'hook' script is provided by the systemd package in focal and earlier, and needs fixing in those releases in h and later, the 'hook' script is included in the isc-dhcp-client package and notifies systemd-resolved in a more direct way without requiring restarting, and so doesn't trigger the restart limiting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1939255/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943077] Re: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s
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 received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1943077 Title: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s Status in snapd: New Status in openssh package in Ubuntu: New Status in squashfs-tools package in Ubuntu: Fix Committed Bug description: During current snapd autopkgtest, a failure can be observed: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/amd64/s/snapd/20210907_175258_5451b@/log.gz error: cannot pack "/home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox": mksquashfs call failed: - libgcc_s.so.1 must be installed for pthread_cancel to work Parallel mksquashfs: Using 1 processor Creating 4.0 filesystem on /home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox/test-snapd-sandbox_1.0_all.snap, block size 131072. - error: cannot read snap file: "/var/lib/snapd/snaps/.local-install-136125945" is not a snap or snapdir I traced the underlying call to the following: "/snap/snapd/current/lib/x86_64-linux-gnu/ld-2.23.so" "--library-path" "/snap/snapd/current/usr/local/lib:/snap/snapd/current/lib/x86_64-linux-gnu:/snap/snapd/current/usr/lib/x86_64-linux-gnu" "/snap/snapd/current/usr/bin/mksquashfs" asdf asdf.squashfs (the real call has more arguments, this is a simplified version that produces the failure) To observe this, one can create a VM based a cloud image from https://cloud-images.ubuntu.com/impish/current, then run the above command in the resulting environment. Doing so will test against snapd v2.51.4 (12883). Retesting with edge 2.52+git635.gada2d87 (13323) produces an equivalent result. Running a more bland `/snap/snapd/current/usr/bin/mksquashfs asdf asdf.squashfs` without messing with library paths has mksquashfs behaving as expected. Also, getting a v2.51.3 snapd seems to behave itself. Updating from 2.51.3 -> 2.51.4 also works. One can see a passing mksquashfs by taking libgcc_s.so.1 from hirsute and placing it in the library path for the above call. In the working scenario, it appears that libgcc_s is being obtained from outside of /snap (and also libz). In the failing scenario, this external copy of libgcc_s is not being loaded (per gdb info sharedlibrary), but libz still is. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1943077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943154] [NEW] My resolution has changed to 800x600 , it was in higher than 1000 I dont know the exact no
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 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 9 20:32:10 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2042] ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=78d7ef17-370f-42ec-839a-ad90938c65fb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: HOH6110H.86A.0010.2012.0424.1632 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61HO dmi.board.vendor: Intel Corporation dmi.board.version: AAG62445-102 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrHOH6110H.86A.0010.2012.0424.1632:bd04/24/2012:svn:pn:pvr:sku:rvnIntelCorporation:rnDH61HO:rvrAAG62445-102:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal 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/1943154 Title: My resolution has changed to 800x600 , it was in higher than 1000 I dont know the exact no Status in xorg package in Ubuntu: New Bug description: 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 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 9 20:32:10 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2042] ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=78d7ef17-370f-42ec-839a-ad90938c65fb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: HOH6110H.86A.0010.2012.0424.1632 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61HO dmi.board.vendor: Intel Corporation dmi.board.version: AAG62445-102 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrHOH6110H.86A.0010.2012.0424.1632:bd04/24/2012:svn:pn:pvr:sku:rvnIntelCorporation:rnDH61HO:rvrAAG62445-102:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau:
[Touch-packages] [Bug 1940635] Re: systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on armhf
** 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 DHCP6 lease from dnsmasq on armhf Status in glibc package in Ubuntu: Invalid Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Bug description: systemd-networkd is failing to acquire a DCHP6 lease from dnsmasq on armhf since glibc 2.34-0ubuntu1, failing systemd (tests-name=networkd- test.py) and netplan.io (test-name=ethernets) tests on armhf. Reproducer: * Setup an armhf container, e.g. via: autopkgtest systemd --test-name=networkd-test.py --shell -U --apt-pocket=proposed=src:systemd,src:glibc -s -- lxd autopkgtest/ubuntu/impish/armhf * It will fail and drop you into the shell * cd test/ && apt install python3-nose * nosetests3 -v -s -m "test_.*_dhcp_ip6" networkd-test.py This is unrelated to the recent dnsmasq changes (LP: #1894619), as that would fail on all architectures, not just armhf. It still passes inside an amd64 LXD container, so it is also not related to armhf being tested inside a container. But it shows the difference between armhf vs amd64 container, that on armhf we're missing the DHCPSOLICIT (and therefore DHCPREPLY) messages, as can be seen from the dnsmasq log: dnsmasq-dhcp[]: DHCPSOLICIT(router_eth42) 00:02:00:00:ab:11:57:1e:20:2f:9e:56:5f:34 dnsmasq-dhcp[]: DHCPREPLY(router_eth42) 2600::1f 00:02:00:00:ab:11:57:1e:20:2f:9e:56:5f:34 autopkgtest-lxd-rtypaf The issue is most probably the same that causes the currently failing netplan.io/ethernets autopkgtest on armhf, if tested against glibc 2.34-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1940635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939861] Re: dpdk: ppc64el autopkgtest regressed in release
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 https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: dpdk (Ubuntu Hirsute) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1939861 Title: dpdk: ppc64el autopkgtest regressed in release Status in dpdk package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Invalid Status in pexpect package in Ubuntu: Invalid Status in util-linux package in Ubuntu: Invalid Status in zlib package in Ubuntu: Invalid Status in dpdk source package in Hirsute: Fix Committed Bug description: [Impact] * Some tests (just a small portion of a vast list of tests) is not really breaking due to real issues but just happen to be notorious timeouts or flaky in the Ubuntu build&test environment. * We have fixed that in Debian and Impish already, but the same behavior now also affects the MRE of 20.11.3 therefore backport the same test improvements to Hirsute. [Test Plan] * Build time and autopkgtests are supposed to work (they are anyway for an SRU, but for this fix this is exactly the test that we want/need to do) [Where problems could occur] * If the patches would be wrong they could have broken the tests, but that would then just not build and thereby not migrate. OTOH there is theoretical chance that the few disabled tests would have catched something down the road which they now no more do - but that isn't that much of a regression, more a trade-off that we want to make. [Other Info] * This initially only affected impish, but later it was found that Hirsute is affected as well. Therefore on this MRE we want to improve it here as well. * To be clear this really is flaky, we could have just hit retry a few times and get through without - but I think we agree that flaky tests are not really helpful and can cause a lot of pain. --- dpkg's autopkgtest on ppc64el has regressed in release [1]. This currently blocks pexpect/8.0-2ubuntu1 from migrating to -release. [1] https://autopkgtest.ubuntu.com/packages/dpdk/impish/ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1939861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940635] Re: systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on armhf
** 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 Status in glibc package in Ubuntu: Invalid Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Bug description: systemd-networkd is failing to acquire a DCHP6 lease from dnsmasq on armhf since glibc 2.34-0ubuntu1, failing systemd (tests-name=networkd- test.py) and netplan.io (test-name=ethernets) tests on armhf. Reproducer: * Setup an armhf container, e.g. via: autopkgtest systemd --test-name=networkd-test.py --shell -U --apt-pocket=proposed=src:systemd,src:glibc -s -- lxd autopkgtest/ubuntu/impish/armhf * It will fail and drop you into the shell * cd test/ && apt install python3-nose * nosetests3 -v -s -m "test_.*_dhcp_ip6" networkd-test.py This is unrelated to the recent dnsmasq changes (LP: #1894619), as that would fail on all architectures, not just armhf. It still passes inside an amd64 LXD container, so it is also not related to armhf being tested inside a container. But it shows the difference between armhf vs amd64 container, that on armhf we're missing the DHCPSOLICIT (and therefore DHCPREPLY) messages, as can be seen from the dnsmasq log: dnsmasq-dhcp[]: DHCPSOLICIT(router_eth42) 00:02:00:00:ab:11:57:1e:20:2f:9e:56:5f:34 dnsmasq-dhcp[]: DHCPREPLY(router_eth42) 2600::1f 00:02:00:00:ab:11:57:1e:20:2f:9e:56:5f:34 autopkgtest-lxd-rtypaf The issue is most probably the same that causes the currently failing netplan.io/ethernets autopkgtest on armhf, if tested against glibc 2.34-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1940635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943163] [NEW] systemd.mount constantly unmounts an in use drive!
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 thought it crashed. Relaunch...finish doing what I was doing, get up, do something...come back it's GONE! Much more of this and I get fed up. I disabled it in autofs and moved to a "permanent" fstab entry...nope still vanishes mid use! More digging and it's systemd.mount. I know I'm ranty but my lord. 18.04 was comfy, nice, everything worked...now nothing works! Lost a GPU due to multi GPU being completely broken in everything newer than 19.10...now I can't even work on a d* remote drive!? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3.4 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Sep 9 10:05:11 2021 EcryptfsInUse: Yes MachineType: Micro-Star International Co., Ltd MS-7C02 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=8e862394-d94b-4c1a-81be-8cef6143bedd ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.H5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.H5:bd04/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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/1943163 Title: systemd.mount constantly unmounts an in use drive! Status in systemd package in Ubuntu: New Bug description: 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 thought it crashed. Relaunch...finish doing what I was doing, get up, do something...come back it's GONE! Much more of this and I get fed up. I disabled it in autofs and moved to a "permanent" fstab entry...nope still vanishes mid use! More digging and it's systemd.mount. I know I'm ranty but my lord. 18.04 was comfy, nice, everything worked...now nothing works! Lost a GPU due to multi GPU being completely broken in everything newer than 19.10...now I can't even work on a d* remote drive!? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3.4 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Sep 9 10:05:11 2021 EcryptfsInUse: Yes MachineType: Micro-Star International Co., Ltd MS-7C02 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=8e862394-d94b-4c1a-81be-8cef6143bedd ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files foun
[Touch-packages] [Bug 1917148] Re: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
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 likely just stay on 3.3.16. Still, need to think about this a bit. -- 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 package in Ubuntu: Fix Released Status in procps source package in Bionic: Fix Released Status in procps source package in Focal: In Progress Status in procps source package in Hirsute: Fix Released Status in procps source package in Impish: Fix Released Bug description: [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 Groovy/Hirsute+ and Bionic and prior releases. - Focal is the only release affected. * Backported Debian fix to restore ".tarball-version" file to provide version information during build. - Also included the autopkgtests for versioning from the same Debian fix. [Test Plan] 1) Create a Focal (or derived from Focal) system. 2) Execute "ps --version" or any of the binaries provided by the package with their respective version flags. 3) Instead of desired output of the version, the output is: the invoked binary name followed by "from procps-ng UNKNOWN" Example: "ps from procps-ng UNKNOWN" [Where problems could occur] * This fix could cause issues if applications have come to depend on the incorrect behavior. IE, an application that uses a version string of "UNKNOWN" as part of a heuristic for identifying a Focal system. * If the version of procps-ng is incremented, this patch would need to be updated or removed if it is no longer relevant. Otherwise, an incorrect version would be reported by the binaries. [Other Info] * This change is in Groovy+ and Debian packaging with the same version of procps-ng. - Introduced in procps (2:3.3.16-5) unstable in Debian. [Original Description] From Linux Lint 20.1, so Focal Fossa 20.04.1 Package procps 2:3.3.16-1ubuntu2 $ LANG=C ps --version ps from procps-ng UNKNOWN I don't know if it comes from Ubuntu or upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1917148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943163] Re: systemd.mount constantly unmounts an in use drive!
** 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 vanished I thought it crashed. Relaunch...finish doing what I was doing, get up, do something...come back it's GONE! Much more of this and I get fed up. I disabled it in autofs and moved to a "permanent" fstab entry...nope still vanishes mid use! More digging and it's systemd.mount. I know I'm ranty but my lord. 18.04 was comfy, nice, everything worked...now nothing works! Lost a GPU due to multi GPU being completely broken in everything newer than 19.10...now I can't even work on a - d* remote drive!? + d* remote drive!? By what does this idiotic system deem the mount + idle or dead? I mean if an application or user has a file open on that + system it's NOT DEAD! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3.4 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Sep 9 10:05:11 2021 EcryptfsInUse: Yes MachineType: Micro-Star International Co., Ltd MS-7C02 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=8e862394-d94b-4c1a-81be-8cef6143bedd ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: - [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf - [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf - [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf - - 3 overridden configuration files found. + [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf + [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf + [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf + + 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.H5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.H5:bd04/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd ** 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 vanished I thought it crashed. Relaunch...finish doing what I was doing, get up, do something...come back it's GONE! Much more of this and I get fed up. I disabled it in autofs and moved to a "permanent" fstab entry...nope - still vanishes mid use! More digging and it's systemd.mount. + still vanishes mid use! Right in the middle of working on a file and get + the "File not found on disk" message. More digging and it's + systemd.mount. I know I'm ranty but my lord. 18.04 was comfy, nice, everything worked...now nothing works! Lost a GPU due to multi GPU being completely broken in everything newer than 19.10...now I can't even work on a d* remote drive!? By what does this idiotic system deem the mount idle or dead? I mean if an application or user has a file open on that system it's NOT DEAD! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3.4 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Sep 9 10:05:11 2021 EcryptfsInUse: Yes MachineType: Micro-Star Internati
[Touch-packages] [Bug 1917148] Re: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
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, 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 package in Ubuntu: Fix Released Status in procps source package in Bionic: Fix Released Status in procps source package in Focal: In Progress Status in procps source package in Hirsute: Fix Released Status in procps source package in Impish: Fix Released Bug description: [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 Groovy/Hirsute+ and Bionic and prior releases. - Focal is the only release affected. * Backported Debian fix to restore ".tarball-version" file to provide version information during build. - Also included the autopkgtests for versioning from the same Debian fix. [Test Plan] 1) Create a Focal (or derived from Focal) system. 2) Execute "ps --version" or any of the binaries provided by the package with their respective version flags. 3) Instead of desired output of the version, the output is: the invoked binary name followed by "from procps-ng UNKNOWN" Example: "ps from procps-ng UNKNOWN" [Where problems could occur] * This fix could cause issues if applications have come to depend on the incorrect behavior. IE, an application that uses a version string of "UNKNOWN" as part of a heuristic for identifying a Focal system. * If the version of procps-ng is incremented, this patch would need to be updated or removed if it is no longer relevant. Otherwise, an incorrect version would be reported by the binaries. [Other Info] * This change is in Groovy+ and Debian packaging with the same version of procps-ng. - Introduced in procps (2:3.3.16-5) unstable in Debian. [Original Description] From Linux Lint 20.1, so Focal Fossa 20.04.1 Package procps 2:3.3.16-1ubuntu2 $ LANG=C ps --version ps from procps-ng UNKNOWN I don't know if it comes from Ubuntu or upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1917148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943163] Re: systemd.mount constantly unmounts an in use drive!
** 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 vanished I thought it crashed. Relaunch...finish doing what I was doing, get up, do something...come back it's GONE! Much more of this and I get fed up. I disabled it in autofs and moved to a "permanent" fstab entry...nope still vanishes mid use! Right in the middle of working on a file and get the "File not found on disk" message. More digging and it's systemd.mount. I know I'm ranty but my lord. 18.04 was comfy, nice, everything worked...now nothing works! Lost a GPU due to multi GPU being completely broken in everything newer than 19.10...now I can't even work on a d* remote drive!? By what does this idiotic system deem the mount idle or dead? I mean if an application or user has a file open on that - system it's NOT DEAD! I'm going to have to start calling Linux + system it's NOT DEAD! I'm going to have to start calling Ubuntu Lucy...because that B always yanks the football away just as you're about to punt and that's about what things are becoming. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3.4 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Sep 9 10:05:11 2021 EcryptfsInUse: Yes MachineType: Micro-Star International Co., Ltd MS-7C02 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=8e862394-d94b-4c1a-81be-8cef6143bedd ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.H5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.H5:bd04/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd -- 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/1943163 Title: systemd.mount constantly unmounts an in use drive! Status in systemd package in Ubuntu: New Bug description: 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 thought it crashed. Relaunch...finish doing what I was doing, get up, do something...come back it's GONE! Much more of this and I get fed up. I disabled it in autofs and moved to a "permanent" fstab entry...nope still vanishes mid use! Right in the middle of working on a file and get the "File not found on disk" message. More digging and it's systemd.mount. I know I'm ranty but my lord. 18.04 was comfy, nice, everything worked...now nothing works! Lost a GPU due to multi GPU being completely broken in everything newer than 19.10...now I can't even work on a d* remote drive!? By what does this idiotic system deem the mount idle or dead? I mean if an application or user has a file open on that system it's NOT DEAD! I'm going to have to start calling Ubuntu Lucy...because that B always yanks the football away just as you're about to punt and that's about what things are becoming. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3.4 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Un
[Touch-packages] [Bug 1934393] Re: systemd-logind network access is blocked, and breaks remote authentication configurations
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 help people searching for local sound issues.) Comments 12 and 16 of bug #1915502 also mention ProtectHostname=no which I don't understand. My understanding of nscd is that, even on cache misses, it will perform the lookup itself, and, being a separate process outside the systemd- logind sandbox, it will succeed. I am not convinced that mandating the use of nscd would be a good idea though, especially as some distributions are moving away from it, e.g. https://fedoraproject.org/wiki/Changes/RemoveNSCD I suspect a lot of NIS/LDAP users do use some version of nscd, which is why there are not more people caught by this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1934393 Title: systemd-logind network access is blocked, and breaks remote authentication configurations Status in systemd: Fix Released Status in nis package in Ubuntu: Confirmed Status in openldap package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Status in nis package in Debian: Fix Released Bug description: [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 debian bug report, see other info section below [test case] many possible ways to reproduce this; there are reproducers in some of the bugs reported before that are caused by this, e.g. bug 1915502 or bug 1916235 [regression potential] failure to authenticate when using remote user data, incorrect authentication, security issues due to un-sandboxing of systemd-logind [scope] this is needed in f and later before focal, systemd-logind was not sandboxed so this did not apply [other info] this isn't actually a bug in systemd, this is a by-design security feature, and the intended upstream design is for systemd-logind to talk to systemd-userdb, so that systemd-logind can remain network- sandboxed while systemd-userdb performs any needed network access for user/auth data. However, Debian and Ubuntu don't enable/provide systemd-userdb, so that design does not work for Debian/Ubuntu. this also can cause systemd-udevd failures in some cases as well, apparently (based on upstream and debian discussion comments) For reference, upstream discussion around the systemd-logind sandboxing specifically: https://github.com/systemd/systemd/issues/7074 upstream updated doc PR explaining the upstream position: https://github.com/systemd/systemd/pull/7343 Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878625 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1934393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
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 because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode Status in Ubuntu on IBM z Systems: Fix Committed Status in isc-dhcp package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Committed Status in netplan.io source package in Focal: New Status in systemd source package in Focal: Fix Committed Status in netplan.io source package in Hirsute: New Status in systemd source package in Hirsute: Fix Committed Status in netplan.io source package in Impish: Confirmed Status in systemd source package in Impish: Fix Committed Bug description: ---Problem Description--- IPs are not getting assigned for Hipersockets in DHCP mode Contact Information = Asha Shekharappa(ashsh...@in.ibm.com) Sankar(sankar...@in.ibm.com) ---uname output--- 52-Ubuntu SMP Thu Sep 10 10:59:04 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Ubuntu 20.04 Netplan with systemd-networkd as renderer Creating ethernet connection on Hipersockets device in DHCP mode fails to assign IPs 1. Configure a Hipersockets device chzdev -e 0.0.8f00 2. Create a .yaml file with the below details network: version: 2 ethernets: enc8f00: dhcp4: yes 3. netplan apply 4. The IP is not assigned as seen below root@M96SANKAR:/etc/netplan# ip a s enc8f00: mtu 32768 qdisc mq state UP group default qlen 1000 link/ether fe:da:af:44:08:02 brd ff:ff:ff:ff:ff:ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855628] Re: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep
** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310894/+files/WifiSyslog.txt ** Attachment removed: "IpAddr.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310886/+files/IpAddr.txt ** Attachment removed: "PciNetwork.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310892/+files/PciNetwork.txt ** Attachment removed: "NetworkManager.conf.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310891/+files/NetworkManager.conf.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310887/+files/IwConfig.txt ** Attachment removed: "NetworkManager.conf.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350605/+files/NetworkManager.conf.txt ** Attachment removed: "IpAddr.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350599/+files/IpAddr.txt ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350613/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855628 Title: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: Whenever I wake the computer up from sleep, the computer no longer connects to the Internet without my having to go into Settings and turn Wi-Fi off and then back on again. Please address this issue. Thank you! network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 19:51:31 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b wifi 1575852612 Sun 08 Dec 2019 07:50:12 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 28634e82-4c1c-3a61-b152-3bd92aaa6992 ethernet 1575852610 Sun 08 Dec 2019 07:50:10 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b /org/freedesktop/NetworkManager/ActiveConnection/1 enp4s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedeskt
[Touch-packages] [Bug 1943163] Re: systemd.mount constantly unmounts an in use drive!
** 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 vanished I thought it crashed. Relaunch...finish doing what I was doing, get up, do something...come back it's GONE! Much more of this and I get fed up. I disabled it in autofs and moved to a "permanent" fstab entry...nope still vanishes mid use! Right in the middle of working on a file and get the "File not found on disk" message. More digging and it's systemd.mount. - I know I'm ranty but my lord. 18.04 was comfy, nice, everything - worked...now nothing works! Lost a GPU due to multi GPU being completely - broken in everything newer than 19.10...now I can't even work on a - d* remote drive!? By what does this idiotic system deem the mount - idle or dead? I mean if an application or user has a file open on that - system it's NOT DEAD! I'm going to have to start calling Ubuntu - Lucy...because that B always yanks the football away just as you're - about to punt and that's about what things are becoming. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3.4 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Sep 9 10:05:11 2021 EcryptfsInUse: Yes MachineType: Micro-Star International Co., Ltd MS-7C02 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=8e862394-d94b-4c1a-81be-8cef6143bedd ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.H5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.H5:bd04/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd ** 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 vanished I thought it crashed. Relaunch...finish doing what I was doing, get up, do - something...come back it's GONE! Much more of this and I get fed up. I + something...come back it's GONE! Much more of this and I got fed up so I disabled it in autofs and moved to a "permanent" fstab entry...nope still vanishes mid use! Right in the middle of working on a file and get the "File not found on disk" message. More digging and it's systemd.mount. - ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3.4 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Sep 9 10:05:11 2021 EcryptfsInUse: Yes MachineType: Micro-Star International Co., Ltd MS-7C02 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=8e862394-d94b-4c1a-81be-8cef6143bedd ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/syst
[Touch-packages] [Bug 1870607] Re: After installing Ubuntu 20.04 alongside 19.10, initramfs no longer is able to extract from either OSes when I boot them.
** Attachment removed: "my initrd.img" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1870607/+attachment/5345796/+files/initrd.img ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1870607/+attachment/5345795/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1870607/+attachment/5345794/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1870607 Title: After installing Ubuntu 20.04 alongside 19.10, initramfs no longer is able to extract from either OSes when I boot them. Status in initramfs-tools package in Ubuntu: New Bug description: After installing Ubuntu 20.04, initramfs no longer can extract from either 20.04 OR 19.10. However, the initramfs should work AT LEAST on 20.04. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: initramfs-tools-core 0.133ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Fri Apr 3 15:33:36 2020 InstallationDate: Installed on 2020-04-03 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1870607/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855628] Re: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep
** 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: "PciNetwork.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350606/+files/PciNetwork.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855628 Title: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: Whenever I wake the computer up from sleep, the computer no longer connects to the Internet without my having to go into Settings and turn Wi-Fi off and then back on again. Please address this issue. Thank you! network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 19:51:31 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b wifi 1575852612 Sun 08 Dec 2019 07:50:12 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 28634e82-4c1c-3a61-b152-3bd92aaa6992 ethernet 1575852610 Sun 08 Dec 2019 07:50:10 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b /org/freedesktop/NetworkManager/ActiveConnection/1 enp4s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: seija 1560 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-04-04 (5 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: defau
[Touch-packages] [Bug 1943163] Re: systemd.mount constantly unmounts an in use drive!
** 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 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Sep 9 10:05:11 2021 EcryptfsInUse: Yes MachineType: Micro-Star International Co., Ltd MS-7C02 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=8e862394-d94b-4c1a-81be-8cef6143bedd ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.H5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.H5:bd04/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd -- 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/1943163 Title: systemd.mount constantly unmounts an in use drive! Status in systemd package in Ubuntu: New Bug description: 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 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Sep 9 10:05:11 2021 EcryptfsInUse: Yes MachineType: Micro-Star International Co., Ltd MS-7C02 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=8e862394-d94b-4c1a-81be-8cef6143bedd ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.H5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.H5:bd04/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1943163/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchp
[Touch-packages] [Bug 1855628] Re: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep
** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310885/+files/Dependencies.txt ** Attachment removed: "NetDevice.enp4s0.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310888/+files/NetDevice.enp4s0.txt ** Attachment removed: "NetDevice.lo.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310889/+files/NetDevice.lo.txt ** Attachment removed: "NetDevice.wlp3s0.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310890/+files/NetDevice.wlp3s0.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310893/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350595/+files/AlsaInfo.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350597/+files/CurrentDmesg.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350598/+files/Dependencies.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350600/+files/IwConfig.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350601/+files/Lspci.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350612/+files/UdevDb.txt ** Attachment removed: "RfKill.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350611/+files/RfKill.txt ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350610/+files/PulseList.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350609/+files/ProcModules.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350608/+files/ProcInterrupts.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350607/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "NetDevice.wlp2s0.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350604/+files/NetDevice.wlp2s0.txt ** Attachment removed: "NetDevice.lo.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350603/+files/NetDevice.lo.txt ** Attachment removed: "NetDevice.enp1s0.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350602/+files/NetDevice.enp1s0.txt ** Description changed: - Whenever I wake the computer up from sleep, the computer no longer - connects to the Internet without my having to go into Settings and turn - Wi-Fi off and then back on again. - - Please address this issue. - - Thank you! - - network-manager: - Installed: 1.10.6-2ubuntu1.2 - Candidate: 1.10.6-2ubuntu1.2 - Version table: - *** 1.10.6-2ubuntu1.2 500 - 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 1.10.6-2ubuntu1.1 500 - 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages - 1.10.6-2ubuntu1 500 - 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages - - Description: Ubuntu 18.04.3 LTS - Release: 18.04 - - ProblemType: Bug - DistroRelease: Ubuntu 18.04 - Package: network-manager 1.10.6-2ubuntu1.2 - ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 - Uname: Linux 5.0.0-37-generic x86_64 - ApportVersion: 2.20.9-0ubuntu7.9 - Architecture: amd64 - CurrentDesktop: ubuntu:GNOME - Date: Sun Dec 8 19:51:31 2019 - IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback - IpRoute: - default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 - 169.254.0.0/16 dev wlp3s0 scope link metric 1000 - 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 - NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true - ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash - RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no - SourcePackage: network-manager - UpgradeStatus: No upgrade log present (probably fresh install) - nmcli-con: - NAMEUUID TYPE TIM
[Touch-packages] [Bug 1856718] Re: CUPS server has an internal error whenever I attempt to add my HP OfficeJet8600 printer to configured devices via networking
** 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" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313383/+files/Screenshot%20from%202019-12-17%2009-43-12.png ** Attachment removed: "CupsErrorLog.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313384/+files/CupsErrorLog.txt ** Information type changed from Public to Private ** Attachment removed: "dnssd.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313412/+files/dnssd.txt ** Attachment removed: "nmap.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313411/+files/nmap.txt ** Attachment removed: "route.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313416/+files/route.txt ** Attachment removed: "access_log.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313417/+files/access_log.txt ** Attachment removed: "Locale.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313388/+files/Locale.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313394/+files/ProcModules.txt ** Attachment removed: "KernLog.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313387/+files/KernLog.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313385/+files/CurrentDmesg.txt ** Attachment removed: "PrintingPackages.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313390/+files/PrintingPackages.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313393/+files/ProcInterrupts.txt ** Attachment removed: "ifconfig.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313414/+files/ifconfig.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313386/+files/Dependencies.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313392/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313389/+files/Lspci.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313391/+files/ProcCpuinfo.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313395/+files/UdevDb.txt ** Attachment removed: "modified.conffile..etc.apport.crashdb.conf.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313396/+files/modified.conffile..etc.apport.crashdb.conf.txt ** Attachment removed: "lpinfo.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313413/+files/lpinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1856718 Title: CUPS server has an internal error whenever I attempt to add my HP OfficeJet8600 printer to configured devices via networking Status in cups package in Ubuntu: New Bug description: Whenever I attempt to add my HP OfficeJet8600 printer and configure it for printing on my Ubuntu PC, CUPS has an internal error and it is unable to configure the device or install drivers. This happened when I ran "system-config-printer" and selected the printer from the list of network printers and clicked "Forward" Instead of configuring the printer and installing drivers, CUPS had an error. Description: Ubuntu 19.10 Release: 19.10 cups: Installed: 2.2.12-2ubuntu1 Candidate: 2.2.12-2ubuntu1 Version table: *** 2.2.12-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Tue Dec 17 09:37:45 2019 InstallationDate: Installed on 2019-11-20 (26 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Co
[Touch-packages] [Bug 1870975] Re: [Dell Inspiron 5570] No audio devices appear except "Dummy Output" after I close my laptop lid while audio is playing and then open it back up.
** 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 ** Information type changed from Public to Private ** Attachment removed: "Image of Audio Settings Menu" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5347299/+files/Screenshot%20from%202020-04-05%2014-51-31.png ** Attachment removed: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5349980/+files/journalctl.log ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: alsa-driver (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Invalid => Confirmed ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5347300/+files/Dependencies.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5347301/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360990/+files/CurrentDmesg.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360999/+files/ProcModules.txt ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5361000/+files/PulseList.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360992/+files/IwConfig.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5361002/+files/UdevDb.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360991/+files/Dependencies.txt ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360988/+files/AlsaInfo.txt ** Attachment removed: "RfKill.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5361001/+files/RfKill.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360998/+files/ProcInterrupts.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360993/+files/Lspci.txt ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Attachment removed: "Lspci-vt.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360994/+files/Lspci-vt.txt ** Attachment removed: "Lsusb-v.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360996/+files/Lsusb-v.txt ** Attachment removed: "Lsusb-t.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360995/+files/Lsusb-t.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360997/+files/ProcCpuinfoMinimal.txt -- 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/1870975 Title: [Dell Inspiron 5570] No audio devices appear except "Dummy Output" after I close my laptop lid while audio is playing and then open it back up. Status in alsa-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: When I closed my laptop lid while sound was playing in Audacity and then opened the lid back up, the device woke up from sleep. However, my headphones were plugged in at the time, and Ubuntu acted as if the audio resumed. However, I was not hearing audio. So I went to the Audio section of Settings and found there was only one sound device: Dummy Device, instead of seeing the speakers built into the laptop and the headphones. Description: Ubuntu 18.04.4 LTS Release: 18.04 I am forced to reboot my machine as a workaround. gnome-control-center: Installed: 1:3.28.2-0ubuntu0.18.04.6 Candidate: 1:3.28.2-0ubuntu0.18.04.6 Version table: *** 1:3.28.2-0ubuntu0.18.04.6 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.28.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-contr
[Touch-packages] [Bug 1943163] Re: systemd.mount constantly unmounts an in use drive!
** 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: http://www.ubuntu.com/support + ░░ + ░░ The unit UNIT has successfully entered the 'dead' state. + Sep 09 11:20:01 $HOSTNAME systemd[1]: pathtomount.mount: Succeeded. + ░░ Subject: Unit succeeded + ░░ Defined-By: systemd + ░░ Support: http://www.ubuntu.com/support + ░░ + ░░ The unit pathtomount.mount has successfully entered the 'dead' state. - Change my kernel and the issue *seems* to have subsided. + Change my kernel and the issue *seems* to have subsided. Coincidence or + swapping kernels reconfigured whatever was causing the issue. Did not + change kernel expecting to fix this, just so happened after I did this + stopped happening. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3.4 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Sep 9 10:05:11 2021 EcryptfsInUse: Yes MachineType: Micro-Star International Co., Ltd MS-7C02 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=8e862394-d94b-4c1a-81be-8cef6143bedd ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.H5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.H5:bd04/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd ** Description changed: systemd.mount constantly unmounts an in use sshfs drive! Sep 09 11:20:01 $HOSTNAME systemd[4613]: pathtomount.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support - ░░ + ░░ ░░ The unit UNIT has successfully entered the 'dead' state. Sep 09 11:20:01 $HOSTNAME systemd[1]: pathtomount.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support - ░░ + ░░ ░░ The unit pathtomount.mount has successfully entered the 'dead' state. Change my kernel and the issue *seems* to have subsided. Coincidence or swapping kernels reconfigured whatever was causing the issue. Did not change kernel expecting to fix this, just so happened after I did this - stopped happening. + stopped happening. Judging by the time stamps (that 01 seconds) + something was misbehaving with cron. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3.4 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Sep 9 10:05:11 2021 EcryptfsInUse: Yes MachineType: Micro-Star International Co., Ltd MS-7C02 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=8e862394-d94b-4c1a-81be-8cef6143bedd ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh in
[Touch-packages] [Bug 1940999] Re: FTBFS against glibc 2.34
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 Mon, 30 Aug 2021 16:41:22 -0600 ** Changed in: grep (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1940999 Title: FTBFS against glibc 2.34 Status in grep package in Ubuntu: Fix Released Bug description: The package grep failed to build in a recent archive rebuild, see https://people.canonical.com/~doko/ftbfs-report/test- rebuild-20210805-impish-impish.html#foundations-bugs . The failure is in automated test, as follows: stack-overflow: failed test: grep never printed "stack overflow" FAIL: stack-overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943189] [NEW] "cannot refresh whilst network offline" bug
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 online or not. I identified a race condition in which this is occurring on systems where packagekitd is initialized before the network service is online. This was a relatively easy fix and required adding one line to the packagekit.service file: Wants=network-online.target This ensures that packagekitd is not initialized prior to being online. If the 90 second deadline isn't met, then packagekitd will simply not start as a background process until the user connects to the network and initializes it via a graphical utility, such as with GNOME Software or Plasma Discover, both of which initialize packagekitd on a user level. The attached patch will easily apply the fix via normal Debian packaging methods. Unfortunately, the upstream PackageKit maintainers seem to be unwilling to apply this fix themselves, seeing it as not an issue per https://github.com/PackageKit/PackageKit/issues/336 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: packagekit 1.2.2-2ubuntu1 [modified: lib/systemd/system/packagekit.service] ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1 Uname: Linux 5.13.0-14-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 9 16:34:12 2021 InstallationDate: Installed on 2021-03-20 (172 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to impish on 2021-06-13 (88 days ago) ** Affects: packagekit (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-bug impish ** Patch added: "Patch to fix packagekitd systemd service race condition" https://bugs.launchpad.net/bugs/1943189/+attachment/5524211/+files/10-wait-network-online.patch ** Changed in: packagekit (Ubuntu) Importance: Undecided => Medium -- 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: New Bug description: 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 online or not. I identified a race condition in which this is occurring on systems where packagekitd is initialized before the network service is online. This was a relatively easy fix and required adding one line to the packagekit.service file: Wants=network-online.target This ensures that packagekitd is not initialized prior to being online. If the 90 second deadline isn't met, then packagekitd will simply not start as a background process until the user connects to the network and initializes it via a graphical utility, such as with GNOME Software or Plasma Discover, both of which initialize packagekitd on a user level. The attached patch will easily apply the fix via normal Debian packaging methods. Unfortunately, the upstream PackageKit maintainers seem to be unwilling to apply this fix themselves, seeing it as not an issue per https://github.com/PackageKit/PackageKit/issues/336 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: packagekit 1.2.2-2ubuntu1 [modified: lib/systemd/system/packagekit.service] ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1 Uname: Linux 5.13.0-14-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 9 16:34:12 2021 InstallationDate: Installed on 2021-03-20 (172 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to impish on 2021-06-13 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1943189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943189] Re: "cannot refresh whilst network offline" bug
** 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: New Bug description: 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 online or not. I identified a race condition in which this is occurring on systems where packagekitd is initialized before the network service is online. This was a relatively easy fix and required adding one line to the packagekit.service file: Wants=network-online.target This ensures that packagekitd is not initialized prior to being online. If the 90 second deadline isn't met, then packagekitd will simply not start as a background process until the user connects to the network and initializes it via a graphical utility, such as with GNOME Software or Plasma Discover, both of which initialize packagekitd on a user level. The attached patch will easily apply the fix via normal Debian packaging methods. Unfortunately, the upstream PackageKit maintainers seem to be unwilling to apply this fix themselves, seeing it as not an issue per https://github.com/PackageKit/PackageKit/issues/336 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: packagekit 1.2.2-2ubuntu1 [modified: lib/systemd/system/packagekit.service] ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1 Uname: Linux 5.13.0-14-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 9 16:34:12 2021 InstallationDate: Installed on 2021-03-20 (172 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to impish on 2021-06-13 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1943189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943189] Re: "cannot refresh whilst network offline" bug
** 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 in Ubuntu: New Bug description: 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 online or not. I identified a race condition in which this is occurring on systems where packagekitd is initialized before the network service is online. This was a relatively easy fix and required adding one line to the packagekit.service file: Wants=network-online.target This ensures that packagekitd is not initialized prior to being online. If the 90 second deadline isn't met, then packagekitd will simply not start as a background process until the user connects to the network and initializes it via a graphical utility, such as with GNOME Software or Plasma Discover, both of which initialize packagekitd on a user level. The attached patch will easily apply the fix via normal Debian packaging methods. Unfortunately, the upstream PackageKit maintainers seem to be unwilling to apply this fix themselves, seeing it as not an issue per https://github.com/PackageKit/PackageKit/issues/336 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: packagekit 1.2.2-2ubuntu1 [modified: lib/systemd/system/packagekit.service] ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1 Uname: Linux 5.13.0-14-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 9 16:34:12 2021 InstallationDate: Installed on 2021-03-20 (172 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to impish on 2021-06-13 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1943189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943130] Re: Nvidia drivers info
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. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-470 (Ubuntu) ** Also affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Nvidia drivers info + PC doesn't send signal to the second monitor ** Summary changed: - PC doesn't send signal to the second monitor + [nvidia] PC doesn't send signal to the second monitor ** Tags added: nvidia ** Summary changed: - [nvidia] PC doesn't send signal to the second monitor + [nvidia] PC doesn't send signal to the second monitor using nvidia-470 (but nvidia-460 works) ** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Incomplete ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Incomplete -- 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/1943130 Title: [nvidia] PC doesn't send signal to the second monitor using nvidia-470 (but nvidia-460 works) Status in linux-hwe-5.11 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: 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 yesterday it was fine but today is broken, and made me to change the driver) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..2b.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.91.03 Fri Jul 2 06:04:10 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Відмовлено у доступі: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 9 15:15:39 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.91.03, 5.11.0-34-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:2208] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8803] InstallationDate: Installed on 2021-08-31 (8 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Micro-Star International Co., Ltd. MS-7C91 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=1bb75479-3578-4389-a29e-40823860bbbc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 05/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG B550 TOMAHAWK (MS-7C91) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.60:bd05/12/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C91:pvr2.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMAGB550TOMAHAWK(MS-7C91):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C91 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-m
[Touch-packages] [Bug 1943137] Re: Mouse is connected however input does not move cursor
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 (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1943137 Title: Mouse is connected however input does not move cursor Status in xorg-server package in Ubuntu: Incomplete Bug description: 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 connected because: - keyboard works for the microsoft sculpt - the logitech mouse is detected by the solar app i use to configure it. - they both work during login ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 9 09:19:31 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-27-generic, x86_64: installed nvidia, 470.57.02, 5.11.0-34-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:098f] NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f12] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:098f] InstallationDate: Installed on 2021-03-25 (167 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=1cef9c97-5ee0-47f7-aa9e-da9d48059d31 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0CXCCY dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd05/21/2021:br1.8:svnDellInc.:pnXPS179700:pvr:sku098F:rvnDellInc.:rn0CXCCY:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1943137/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943154] Re: My resolution has changed to 800x600 , it was in higher than 1000 I dont know the exact no
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 kernel by accessing the grub menu (press Esc at startup). Do you find older kernel versions avoid the problem? Please also try unplugging and reconnecting the monitor. ** Package changed: xorg (Ubuntu) => linux-hwe-5.11 (Ubuntu) ** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Incomplete ** Summary changed: - My resolution has changed to 800x600 , it was in higher than 1000 I dont know the exact no + [i915] My resolution has changed to 800x600, it was 1600x900 before -- 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/1943154 Title: [i915] My resolution has changed to 800x600, it was 1600x900 before Status in linux-hwe-5.11 package in Ubuntu: Incomplete Bug description: 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 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 9 20:32:10 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2042] ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=78d7ef17-370f-42ec-839a-ad90938c65fb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: HOH6110H.86A.0010.2012.0424.1632 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61HO dmi.board.vendor: Intel Corporation dmi.board.version: AAG62445-102 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrHOH6110H.86A.0010.2012.0424.1632:bd04/24/2012:svn:pn:pvr:sku:rvnIntelCorporation:rnDH61HO:rvrAAG62445-102:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1943154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943163] Re: systemd.mount constantly unmounts an in use drive!
** Description changed: systemd.mount constantly unmounts an in use sshfs drive! Sep 09 11:20:01 $HOSTNAME systemd[4613]: pathtomount.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit UNIT has successfully entered the 'dead' state. Sep 09 11:20:01 $HOSTNAME systemd[1]: pathtomount.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit pathtomount.mount has successfully entered the 'dead' state. Change my kernel and the issue *seems* to have subsided. Coincidence or swapping kernels reconfigured whatever was causing the issue. Did not change kernel expecting to fix this, just so happened after I did this stopped happening. Judging by the time stamps (that 01 seconds) something was misbehaving with cron. This only seemed to affect the fuse mounts which correlates with other reports elsewhere I found but no real fixes and me changing kernels and rebuilding some things were just happenstance. i.e. magically fixed yields no answers. I installed a snap app around the time it started misbehaving but again could be pointless coincidence. I just noticed in the logs snap was playing with mounts for sandboxing. + + Just occurred to me that I think I've seen this before. When 20.04 came + out I updated my roommates laptop with it. It's old, just plays movies + off the network and the hard drive died so I just did an install to a + little flash drive. She'd be watching something and it would do that + little buffer stutter like you just yanked the drive out mid audio/video + playback and crash. Eventually I just moved the machine back to 18.04 + because there was no rhyme or reason to why it was doing that. I spent a + month hunting thermal trip issues, power saving, you name it but not + systemd. I never found anything in the logs but I was looking for + power/thermal/shutdown stuff not something idiotic unmounting the + rootfs! + + While I fear my angry bits are seen as trolling there is a distinct fall + off from 18.04. Every release past 19 has been riddled with massive + problems across several machines. Another friend I upgraded to 20.04, + couldn't print. Worked fine in 18.04. Found a solution after months of + printing from an 18.04 vm. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3.4 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Sep 9 10:05:11 2021 EcryptfsInUse: Yes MachineType: Micro-Star International Co., Ltd MS-7C02 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=8e862394-d94b-4c1a-81be-8cef6143bedd ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.H5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.H5:bd04/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd -- 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/1943163 Title: systemd.mount constantly unmounts an in use drive! Status in systemd package in Ubuntu: New Bug description: systemd.mount constantly unmounts an in use sshfs drive! Sep 09 11:20:01 $HOSTNAME systemd[4613]: pathtomount.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit UNIT has successfully entered the 'de
[Touch-packages] [Bug 1939409] Re: e2fsprogs 1.46.3-1 on architecture s390x fails in test f_baddotdir
** No longer affects: e2fsprogs (Ubuntu Impish) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1939409 Title: e2fsprogs 1.46.3-1 on architecture s390x fails in test f_baddotdir Status in e2fsprogs package in Ubuntu: Fix Released Bug description: e2fsprogs 1.46.3-1ubuntu1 is in proposed. Architecture s390x fail in test f_baddotdir. The test image was changed with the new release. Next step should be analyzing the error on a s390x virtual machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1939409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp