[Touch-packages] [Bug 1929647] Re: debian helper tools for python never updates
still present ** Attachment added: "still cannot upgrade" https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1929647/+attachment/5502052/+files/still%20not%20able%20to%20select%20Peek%202021-06-03%2008-36.gif -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-debian in Ubuntu. https://bugs.launchpad.net/bugs/1929647 Title: debian helper tools for python never updates Status in python-debian package in Ubuntu: New Bug description: software updater prompts new updates debian helper tools for python is always one of them but I cannot select the checkbox so debian helper tools for python never updates Here's the screen shot https://i.imgur.com/AjDd5yo.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1929647/+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 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions)
It's only as a test. Does a Wayland session avoid this bug? I know other people have said it does in the past but they are no longer experiencing problems and it would be most useful to have an answer from the original reporter. > I've tried this before commenting last time and it had way worse > performance with the desktop itself. For example the dash would > take a minute or so to load all the icons. Please open a new bug about that or it's unlikely to be investigated and fixed. Although check to see if it is bug 1874578 first. > Also applications like OBS, Discord and Teams have issues with > recording and/or streaming, so I have to stay on X. That's due to missing support for PipeWire in those apps, required for screen capturing in Wayland sessions. OBS has a fix coming in version 27 for example (bug 1838967). Please remember to report back on your findings from comment #33. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions) Status in gnome-shell package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+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 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions)
> * Logging into 'Ubuntu on Wayland' (select it on the login screen). I've tried this before commenting last time and it had way worse performance with the desktop itself. For example the dash would take a minute or so to load all the icons. Also applications like OBS, Discord and Teams have issues with recording and/or streaming, so I have to stay on X. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions) Status in gnome-shell package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+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 1922380] Re: remove shim-signed very difficult
[Expired for apt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: apt (Ubuntu)
Status: Incomplete => Expired
--
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/1922380
Title:
remove shim-signed very difficult
Status in apt package in Ubuntu:
Expired
Bug description:
Hello
I don't want the shim-signed anymore, but I need an additional password to
remove it.
This error is for all version of ubuntu.
I am sure I am entering the correct one because I entered it using a
copy paste technique.
Have pity on those who do not know English well !!
apt purge shim-signed
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Les paquets suivants ont été installés automatiquement et ne sont plus
nécessaires :
mokutil shim
Veuillez utiliser « apt autoremove » pour les supprimer.
Les paquets suivants seront ENLEVÉS :
shim-signed*
ATTENTION : Les paquets essentiels suivants vont être enlevés.
Vous NE devez PAS faire ceci, à moins de savoir exactement ce
que vous êtes en train de faire.
shim-signed
0 mis à jour, 0 nouvellement installés, 1 à enlever et 0 non mis à jour.
Après cette opération, 2 734 ko d'espace disque seront libérés.
Vous êtes sur le point de faire quelque chose de potentiellement dangereux
Pour continuer, tapez la phrase « Oui, faites ce que je vous dis ! »
?]Oui, faites ce que je vous dis !
Annulation.
root@a:~# export LANG=us
root@a:~# apt purge shim-signed
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer
required:
mokutil shim
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
shim-signed*
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
shim-signed
0 upgraded, 0 newly installed, 1 to remove and 171 not upgraded.
After this operation, 2734 kB disk space will be freed.
You are about to do something potentially harmful.
To continue type in the phrase 'Yes, do as I say!'
?] Yes, do as I say!
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "fr_FR:fr_CA",
LC_ALL = (unset),
LC_TIME = "fr_FR.UTF-8",
LC_MONETARY = "fr_FR.UTF-8",
LC_ADDRESS = "fr_FR.UTF-8",
LC_TELEPHONE = "fr_FR.UTF-8",
LC_NAME = "fr_FR.UTF-8",
LC_MEASUREMENT = "fr_FR.UTF-8",
LC_IDENTIFICATION = "fr_FR.UTF-8",
LC_NUMERIC = "fr_FR.UTF-8",
LC_PAPER = "fr_FR.UTF-8",
LANG = "us"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: this is a protected package; it should not be removed
(Reading database ... 211327 files and directories currently installed.)
Removing shim-signed (1.45+15+1552672080.a4a1fbe-0ubuntu2) ...
(Reading database ... 211314 files and directories currently installed.)
Purging configuration files for shim-signed
(1.45+15+1552672080.a4a1fbe-0ubuntu2) ...
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
root@a:~#
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: evince 3.38.0-1
ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
Uname: Linux 5.8.0-34-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 2 15:07:48 2021
InstallationDate: Installed on 2020-10-25 (159 days ago)
InstallationMedia: Ubuntu-Server 20.10 "Groovy Gorilla" - Release amd64
(20201022)
KernLog:
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1922380/+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 1930286] Re: Defensics' synopsys fuzzer testing tool cause openssh to segfault
Hello Seth, So far no production impact has been reported, for now it is only reproducible using that particular fuzzer on xenial's openssh version. Thanks -- 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/1930286 Title: Defensics' synopsys fuzzer testing tool cause openssh to segfault Status in openssh package in Ubuntu: New Status in openssh source package in Xenial: New Bug description: Here's what has been brought to my attention by a UA customer: * Release: Xenial/16.04LTS * Openssh version: 7.2p2-4ubuntu2.10 * Fuzzer tool used: https://www.synopsys.com/software-integrity/security-testing/fuzz-testing.html (proprietary software) As of today, I have no access to a reproducer. Still working on getting access to one (if possible) in order to better understand what the failing test scenario is doing. * coredump: $ gdb $(which sshd) core.cic-1.domain.tld.1612566260.sshd.20731 ... Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `sshd: [net] '. Program terminated with signal SIGSEGV, Segmentation fault. #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 136 ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S: No such file or directory. (gdb) bt #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 #1 0x7fec25b241db in memcpy (__len=, __src=0x0, __dest=) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #2 aes_gcm_ctrl (c=0x558a7ae19758, type=, arg=, ptr=0x0) at e_aes.c:1189 #3 0x7fec25b20897 in EVP_CIPHER_CTX_ctrl (ctx=ctx@entry=0x558a7ae19758, type=type@entry=18, arg=arg@entry=-1, ptr=ptr@entry=0x0) at evp_enc.c:619 #4 0x558a7953f54c in cipher_init (cc=cc@entry=0x558a7ae19750, cipher=0x558a797b3ef0 , key=0x0, keylen=32, iv=0x0, ivlen=, do_encrypt=0) at ../cipher.c:336 #5 0x558a7954521a in ssh_set_newkeys (ssh=ssh@entry=0x558a7ae18ef0, mode=mode@entry=0)at ../packet.c:919 #6 0x558a7955ae92 in kex_input_newkeys (type=, seq=, ctxt=0x558a7ae18ef0)at ../kex.c:434 #7 0x558a7954d269 in ssh_dispatch_run (ssh=ssh@entry=0x558a7ae18ef0, mode=0, done=0x558a7ae18278, ctxt=0x558a7ae18ef0) at ../dispatch.c:119 #8 0x558a7954d2b9 in ssh_dispatch_run_fatal (ssh=0x558a7ae18ef0, mode=, done=, ctxt=) at ../dispatch.c:140 #9 0x558a79502770 in do_ssh2_kex () at ../sshd.c:2744 #10 main (ac=, av=) at ../sshd.c:2301 (gdb) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1930286/+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 1930567] Re: Popup menu handling broken with multiple monitors in Wayland sessions
The first issue with Terminal is being tracked upstream in https://gitlab.gnome.org/GNOME/mutter/-/issues/1768 The second issue with Firefox (which the new design does not exhibit but other apps do still) is being tracked upstream in https://gitlab.gnome.org/GNOME/mutter/-/issues/1783 ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low ** Changed in: mutter (Ubuntu) Importance: Undecided => Low ** Summary changed: - Popup menu handling broken with multiple monitors in Wayland sessions + Popup menus don't appear at all if opened close to inter-monitor boundaries in Wayland sessions ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1768 https://gitlab.gnome.org/GNOME/mutter/-/issues/1768 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1768 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1783 https://gitlab.gnome.org/GNOME/mutter/-/issues/1783 ** Changed in: mutter (Ubuntu) Status: Confirmed => Triaged ** No longer affects: gnome-shell (Ubuntu) ** No longer affects: gtk+3.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1930567 Title: Popup menus don't appear at all if opened close to inter-monitor boundaries in Wayland sessions Status in Mutter: Unknown Status in mutter package in Ubuntu: Triaged Bug description: I have two (hopefully related) problems with popup-menus for applications on an external monitor. For background I have two displays, the first a builtin LCD panel, the second and HDMI connected LCD monitor. The external monitor is stacked "above" the internal LCD panel, the internal LCD panel is the "primary" display from a where the dash et al are placed. The first issue occurs with gnome-terminal. When using right-click on an element in the window such as a link, a menu is shown to allow OpenURL et al. This menu will not appear when the link it too close to the bottom of the upper display (the external one); the cursor changes to the arrow menu item selector cursor but not menu is rendered. This occurs regardless of whether the window is maximised and it related to proximity to the boundary of the display. It behaves correctly at the bottom boundary of the lower display. Two screenshots attached showing it working/not-working. The second issue occurs in firefox. When it is rendered on the upper displays its internal menus are displayed at the top of the lower display rather than on the upper display rooted at the menu item itself. This also does not occur on the lower display. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1930567/+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 1930286] Re: Defensics' synopsys fuzzer testing tool cause openssh to segfault
Hello Eric, thanks for doing the research on this issue. Does the coredump look like this may be exploitable in some fashion? Is the crash something that affects anything beyond the specific process serving the client in question? Thanks -- 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/1930286 Title: Defensics' synopsys fuzzer testing tool cause openssh to segfault Status in openssh package in Ubuntu: New Status in openssh source package in Xenial: New Bug description: Here's what has been brought to my attention by a UA customer: * Release: Xenial/16.04LTS * Openssh version: 7.2p2-4ubuntu2.10 * Fuzzer tool used: https://www.synopsys.com/software-integrity/security-testing/fuzz-testing.html (proprietary software) As of today, I have no access to a reproducer. Still working on getting access to one (if possible) in order to better understand what the failing test scenario is doing. * coredump: $ gdb $(which sshd) core.cic-1.domain.tld.1612566260.sshd.20731 ... Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `sshd: [net] '. Program terminated with signal SIGSEGV, Segmentation fault. #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 136 ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S: No such file or directory. (gdb) bt #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 #1 0x7fec25b241db in memcpy (__len=, __src=0x0, __dest=) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #2 aes_gcm_ctrl (c=0x558a7ae19758, type=, arg=, ptr=0x0) at e_aes.c:1189 #3 0x7fec25b20897 in EVP_CIPHER_CTX_ctrl (ctx=ctx@entry=0x558a7ae19758, type=type@entry=18, arg=arg@entry=-1, ptr=ptr@entry=0x0) at evp_enc.c:619 #4 0x558a7953f54c in cipher_init (cc=cc@entry=0x558a7ae19750, cipher=0x558a797b3ef0 , key=0x0, keylen=32, iv=0x0, ivlen=, do_encrypt=0) at ../cipher.c:336 #5 0x558a7954521a in ssh_set_newkeys (ssh=ssh@entry=0x558a7ae18ef0, mode=mode@entry=0)at ../packet.c:919 #6 0x558a7955ae92 in kex_input_newkeys (type=, seq=, ctxt=0x558a7ae18ef0)at ../kex.c:434 #7 0x558a7954d269 in ssh_dispatch_run (ssh=ssh@entry=0x558a7ae18ef0, mode=0, done=0x558a7ae18278, ctxt=0x558a7ae18ef0) at ../dispatch.c:119 #8 0x558a7954d2b9 in ssh_dispatch_run_fatal (ssh=0x558a7ae18ef0, mode=, done=, ctxt=) at ../dispatch.c:140 #9 0x558a79502770 in do_ssh2_kex () at ../sshd.c:2744 #10 main (ac=, av=) at ../sshd.c:2301 (gdb) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1930286/+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 1930567] Re: Popup menu handling broken with multiple monitors in Wayland sessions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1930567 Title: Popup menus don't appear at all if opened close to inter-monitor boundaries in Wayland sessions Status in Mutter: Unknown Status in mutter package in Ubuntu: Triaged Bug description: I have two (hopefully related) problems with popup-menus for applications on an external monitor. For background I have two displays, the first a builtin LCD panel, the second and HDMI connected LCD monitor. The external monitor is stacked "above" the internal LCD panel, the internal LCD panel is the "primary" display from a where the dash et al are placed. The first issue occurs with gnome-terminal. When using right-click on an element in the window such as a link, a menu is shown to allow OpenURL et al. This menu will not appear when the link it too close to the bottom of the upper display (the external one); the cursor changes to the arrow menu item selector cursor but not menu is rendered. This occurs regardless of whether the window is maximised and it related to proximity to the boundary of the display. It behaves correctly at the bottom boundary of the lower display. Two screenshots attached showing it working/not-working. The second issue occurs in firefox. When it is rendered on the upper displays its internal menus are displayed at the top of the lower display rather than on the upper display rooted at the menu item itself. This also does not occur on the lower display. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1930567/+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 1930567] Re: Popup menu handling broken with multiple monitors in Wayland sessions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1930567 Title: Popup menus don't appear at all if opened close to inter-monitor boundaries in Wayland sessions Status in Mutter: Unknown Status in mutter package in Ubuntu: Triaged Bug description: I have two (hopefully related) problems with popup-menus for applications on an external monitor. For background I have two displays, the first a builtin LCD panel, the second and HDMI connected LCD monitor. The external monitor is stacked "above" the internal LCD panel, the internal LCD panel is the "primary" display from a where the dash et al are placed. The first issue occurs with gnome-terminal. When using right-click on an element in the window such as a link, a menu is shown to allow OpenURL et al. This menu will not appear when the link it too close to the bottom of the upper display (the external one); the cursor changes to the arrow menu item selector cursor but not menu is rendered. This occurs regardless of whether the window is maximised and it related to proximity to the boundary of the display. It behaves correctly at the bottom boundary of the lower display. Two screenshots attached showing it working/not-working. The second issue occurs in firefox. When it is rendered on the upper displays its internal menus are displayed at the top of the lower display rather than on the upper display rooted at the menu item itself. This also does not occur on the lower display. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1930567/+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 1930567] Re: Popup menu handling broken with multiple monitors in Wayland sessions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1930567 Title: Popup menus don't appear at all if opened close to inter-monitor boundaries in Wayland sessions Status in Mutter: Unknown Status in mutter package in Ubuntu: Triaged Bug description: I have two (hopefully related) problems with popup-menus for applications on an external monitor. For background I have two displays, the first a builtin LCD panel, the second and HDMI connected LCD monitor. The external monitor is stacked "above" the internal LCD panel, the internal LCD panel is the "primary" display from a where the dash et al are placed. The first issue occurs with gnome-terminal. When using right-click on an element in the window such as a link, a menu is shown to allow OpenURL et al. This menu will not appear when the link it too close to the bottom of the upper display (the external one); the cursor changes to the arrow menu item selector cursor but not menu is rendered. This occurs regardless of whether the window is maximised and it related to proximity to the boundary of the display. It behaves correctly at the bottom boundary of the lower display. Two screenshots attached showing it working/not-working. The second issue occurs in firefox. When it is rendered on the upper displays its internal menus are displayed at the top of the lower display rather than on the upper display rooted at the menu item itself. This also does not occur on the lower display. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1930567/+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 1802331] Re: Drop down menus appear in wrong position when using multiple monitors arranged vertically
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1802331 Title: Drop down menus appear in wrong position when using multiple monitors arranged vertically Status in gnome-terminal package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Bug description: I am using multiple monitors arranged as shown below: ++++ |__3_||__2_| |||| ++++ +-+ |1| |_| +-+ Monitors 1 and 3 have different resolutions (1920x1080 and 1600x900) and are arranged so that their right edges align. When opening a drop down menu (such as the 'File' menu in terminal) that appears to the top left of a full-screen application on monitor 3, the drop down menu position is offset horizontally. It is as if menus that appear at the left of monitor 3 are 'pushed' to the right so that they are in line with monitor 1. The attached screen capture shows roughly where the File menu drop down appears. Menus on monitors 1 and 2 appear in the expected location. I imagine this is a problem with GNOME 3, as I never had this problem with Unity on Ubuntu 16, and it seems to affect all applications. Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 8 15:26:34 2018 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2018-11-02 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1802331/+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 1930567] Re: Popup menu handling broken with multiple monitors in Wayland sessions
Might be related to bug 1802331. ** Summary changed: - popup menu handling broken with multiple monitors + Popup menu handling broken with multiple monitors in Wayland sessions ** Tags added: impish ** Tags added: wayland-session ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1930567 Title: Popup menus don't appear at all if opened close to inter-monitor boundaries in Wayland sessions Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have two (hopefully related) problems with popup-menus for applications on an external monitor. For background I have two displays, the first a builtin LCD panel, the second and HDMI connected LCD monitor. The external monitor is stacked "above" the internal LCD panel, the internal LCD panel is the "primary" display from a where the dash et al are placed. The first issue occurs with gnome-terminal. When using right-click on an element in the window such as a link, a menu is shown to allow OpenURL et al. This menu will not appear when the link it too close to the bottom of the upper display (the external one); the cursor changes to the arrow menu item selector cursor but not menu is rendered. This occurs regardless of whether the window is maximised and it related to proximity to the boundary of the display. It behaves correctly at the bottom boundary of the lower display. Two screenshots attached showing it working/not-working. The second issue occurs in firefox. When it is rendered on the upper displays its internal menus are displayed at the top of the lower display rather than on the upper display rooted at the menu item itself. This also does not occur on the lower display. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1930567/+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 1930591] Re: Not able to attach secondary display through HDMI
Thanks for the bug report. Indeed the HDMI port is showing nothing is connected. Maybe you need to try a different HDMI cable or a different monitor. ** 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/1930591 Title: Not able to attach secondary display through HDMI Status in xorg-server package in Ubuntu: Incomplete Bug description: Not able to attach secondary display through HDMI ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 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: Wed Jun 2 19:09:31 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:1854] InstallationDate: Installed on 2021-05-01 (32 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard HP 2000 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=4b855eaf-8204-49cb-8e54-11983d2916a7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2013 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1854 dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.2A dmi.chassis.asset.tag: 5CG3244HK1 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 100.42 dmi.modalias: dmi:bvnInsyde:bvrF.45:bd12/19/2013:br15.69:efr100.42:svnHewlett-Packard:pnHP2000NotebookPC:pvr098E130059160:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PRE X=MIN dmi.product.name: HP 2000 Notebook PC dmi.product.sku: E4X59PA#ACJ dmi.product.version: 098E130059160 dmi.sys.vendor: Hewlett-Packard 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 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/1930591/+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 1930550] Re: usb sound devices crackling
It might also be a good idea to ensure your USB sound device is never sharing the same USB bus/hub as other devices. You can check that using: lsusb -t -- 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/1930550 Title: usb sound devices crackling Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrade from 20.04 to 21.04 all 3 my usb sound devices start crackling, i have xduoo05plus, audeze mobius, audient id4. I also tried to modify default-fragments = 5 default-fragment-size-msec = 2 to different sugested on stackoverflow articles setting Also this is in my config: high-priority = yes nice-level = -11 realtime-scheduling = yes realtime-priority = 5 I even tried to switch to pipewire, but it still the same. Possible issue in alsa kernel drivers for usb interface, submitting bug to pulse as it default in ubuntu. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jun 2 11:11:55 2021 InstallationDate: Installed on 2019-08-13 (658 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to hirsute on 2021-05-16 (16 days ago) dmi.bios.date: 08/12/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd08/12/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnB85-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85-HD3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2021-05-18T13:33:15.787174 mtime.conffile..etc.pulse.system.pa: 2021-05-18T11:20:40.860787 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1930550/+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 1930641] Re: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2
Thanks for the bug report. Memory leaks in the Xorg process are usually the fault of an application. Because in X11 the server owns the resources created by applications, and any leaks will appear in the server process 'Xorg'. To help track down any offending applications, please run this command while the leak is happening: xrestop and it will show the applications causing the most memory usage in Xorg. ** 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/1930641 Title: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2 Status in xorg-server package in Ubuntu: Incomplete Bug description: Progressive memory leak in Xorg. With 16Gb RAM, memory use increases by about 1% each day according to top. Started at about 1%, now 24% after nearly 3 weeks. Video driver is i915, uname -m shows x86_64. Ubuntu 20.04, up to date as at 29 May 2021. HDMI connector. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Jun 3 11:06:35 2021 DistUpgraded: 2021-04-26 20:35:01,095 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox-guest, 6.1.16, 5.4.0-73-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 5500 [1458:1000] InstallationDate: Installed on 2017-05-31 (1463 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: GIGABYTE GB-BXi7-5500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=6999d6bd-6356-4df2-b056-032c25b2dd60 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-04-26 (37 days ago) dmi.bios.date: 12/05/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MQLP7AP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/05/2014:svnGIGABYTE:pnGB-BXi7-5500:pvr1.x:rvnGIGABYTE:rnMQLP7AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BXi7-5500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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.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/1930641/+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 1930641] [NEW] memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2
Public bug reported: Progressive memory leak in Xorg. With 16Gb RAM, memory use increases by about 1% each day according to top. Started at about 1%, now 24% after nearly 3 weeks. Video driver is i915, uname -m shows x86_64. Ubuntu 20.04, up to date as at 29 May 2021. HDMI connector. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Jun 3 11:06:35 2021 DistUpgraded: 2021-04-26 20:35:01,095 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox-guest, 6.1.16, 5.4.0-73-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 5500 [1458:1000] InstallationDate: Installed on 2017-05-31 (1463 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: GIGABYTE GB-BXi7-5500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=6999d6bd-6356-4df2-b056-032c25b2dd60 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-04-26 (37 days ago) dmi.bios.date: 12/05/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MQLP7AP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/05/2014:svnGIGABYTE:pnGB-BXi7-5500:pvr1.x:rvnGIGABYTE:rnMQLP7AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BXi7-5500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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.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 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/1930641 Title: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2 Status in xorg package in Ubuntu: New Bug description: Progressive memory leak in Xorg. With 16Gb RAM, memory use increases by about 1% each day according to top. Started at about 1%, now 24% after nearly 3 weeks. Video driver is i915, uname -m shows x86_64. Ubuntu 20.04, up to date as at 29 May 2021. HDMI connector. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Jun 3 11:06:35 2021 DistUpgraded: 2021-04-26 20:35:01,095 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox-guest, 6.1.16, 5.4.0-73-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 5500 [1458:1000] InstallationDate: Installed on 2017-05-31 (1463 days ago) InstallationMedia: Ubuntu 17.04 "Zesty
[Touch-packages] [Bug 1925730] Re: Dell XPS 17 (Ubuntu 21.04) - No sound AT ALL upon fresh installation
*** This bug is a duplicate of bug 1921632 *** https://bugs.launchpad.net/bugs/1921632 Hi, the proposed kernel is ready, you could install the kernel of 5.11.0-19 to verify, this kernel merged the fix of this bug. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632/comments/28 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1925730 Title: Dell XPS 17 (Ubuntu 21.04) - No sound AT ALL upon fresh installation Status in alsa-driver package in Ubuntu: New Bug description: New laptop - Dell XPS 17, bought in 2020. Upon installation of Ubuntu 21.04 sound does not work at all. System settings only show one audio output - "Dummy output". Audio input does not have even that, just an empty drop-down list. Issue can be fixed if we load a custom sound driver as described here: https://blog.fts.scot/2020/07/04/dell-xps-2020-how-to-get-audio- working-on-linux/ That poses a security risk however and according to the author of the article is not necessary since mainline Kernel release 5.11 now has required device headers included. ... lspci output: user@MYPC:~$ lspci -v | grep -i -A 10 audio 00:1f.3 Multimedia audio controller: Intel Corporation Comet Lake PCH cAVS Subsystem: Dell Comet Lake PCH cAVS Flags: bus master, fast devsel, latency 64, IRQ 229, IOMMU group 16 Memory at 609b218000 (64-bit, non-prefetchable) [size=16K] Memory at 609b10 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: sof-audio-pci Kernel modules: snd_hda_intel, snd_sof_pci -- 01:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio Controller (rev a1) Subsystem: Dell TU106 High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 17, IOMMU group 1 Memory at 7300 (32-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel Looked around for soundwire drivers, found this: user@MYPC:~$ lsmod | grep soundwire soundwire_intel40960 2 snd_sof_intel_hda_common,snd_intel_dspcfg soundwire_generic_allocation16384 1 soundwire_intel soundwire_cadence 32768 1 soundwire_intel soundwire_bus 77824 7 regmap_sdw,soundwire_intel,snd_soc_rt715,soundwire_generic_allocation,soundwire_cadence,snd_soc_rt711,snd_soc_rt1308_sdw snd_soc_core 294912 8 soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_rt715,snd_soc_hdac_hda,snd_soc_rt711,snd_soc_dmic,snd_soc_rt1308_sdw snd_pcm 118784 14 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_sof_intel_ipc,snd_soc_rt715,snd_compress,snd_soc_core,snd_soc_rt711,snd_soc_rt1308_sdw,snd_hda_core,snd_pcm_dmaengine Maybe using the soundwire_intel driver would fix the problem? Need to keep digging. Will post an update if I have any progress. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iamarkadyt 1593 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 00:18:15 2021 InstallationDate: Installed on 2021-04-23 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: TU106 High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iamarkadyt 1593 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA NVidia, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2020 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0YK6XT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd09/03/2020:br1.4:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0YK6XT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925730/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list
This bug was fixed in the package ubuntu-release-upgrader - 1:20.10.16
---
ubuntu-release-upgrader (1:20.10.16) groovy; urgency=medium
* DistUpgrade/DistUpgradeController.py: restore sources.list where possible
if a KeyboardInterrupt event is received and redirect the output of
gnome-session-inhibit to devnull so a message regarding Ctrl-C is not
displayed. (LP: #1898026)
* Update mirrors, demotions, and translations.
-- Brian Murray Fri, 14 May 2021 10:27:44 -0700
** Changed in: ubuntu-release-upgrader (Ubuntu Groovy)
Status: Fix Committed => Fix Released
--
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/1898026
Title:
interruption of dist-upgrade can leave you next release in
sources.list
Status in apt package in Ubuntu:
Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
Fix Released
Status in apt source package in Bionic:
New
Status in ubuntu-release-upgrader source package in Bionic:
New
Status in apt source package in Focal:
New
Status in ubuntu-release-upgrader source package in Focal:
Fix Released
Status in apt source package in Groovy:
Fix Released
Status in ubuntu-release-upgrader source package in Groovy:
Fix Released
Status in apt source package in Hirsute:
Fix Released
Status in ubuntu-release-upgrader source package in Hirsute:
Fix Released
Bug description:
[Impact]
Calling update() or installing packages from apt clients resets their SIGINT
and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they might have
set for them.
In case of ubuntu-release-upgrader, this results in the release
upgrader being unable to handle interrupts after it did the initial
update - the default libc handler will run and the program exits.
[Test plan]
[[apt]]
As a standalone test for apt, we can test the following script:
import apt
import time
apt.Cache().update()
print("WAITING")
try:
time.sleep(1)
except BaseException as e:
print("Seen", repr(e))
print("END")
Pressing Ctrl+C while WAITING is printed should print Seen
KeyboardInterrupt, and importantly, also the END line.
[[ubuntu-release-upgrader]]
1) On an Ubuntu 18.04 system run do-release-upgrade in a terminal.
2) At the "Do you want to start the upgrade?" question say Y.
3) When you see the "Lock screen disabled" message you will also see
"Inhibiting until Ctrl+C is pressed".
4) Press "Ctrl+C"
Your /etc/apt/sources.list file will now have focal in it instead of
bionic although the upgrade has quit. With the version of ubuntu-
release-upgrader in -proposed you will not see the "Ctrl+C" message.
For your sources.list file to be restored you'll need the version of
apt from bionic-proposed installed before starting the upgrade.
[Where problems could occur]
apt: This specific change removes the two lines that SIG_DFL the signal
handlers after running scripts. AFAWCT those lines are unnecessary - the code
that calls it temporarily sets the handlers to SIG_IGN but restores previous
handlers at the end; it was wrongly refactored decades ago. A regression could
occur in that those signals will now continue to be ignored if we missed a spot.
ubuntu-release-upgrader: The change is wrapping a bunch of code in a
try: except: block so if the indentation was off the pyflakes /
pycodestyle tests would fail but autopkgtest will catch that.
[Original bug report]
As a long-time-user of ?ubuntu, with apt-get as tool of choice for
updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'.
In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu
version; just all packages including new ones. Version updates had to be
initiated manually, and I was always asked if I really wanted the new ?ubuntu
version. Sounds appropriate.
Last night when it (dist-upgrade), it just gave me 20.04. No questions asked.
I for one consider this kind of intrusive, though.
It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a
number of times earlier; just to *check* if the upgrade was on offer; but this
is only a guess.
In *any* case, a pop-up asking "Are you sure? Are you connected
through an adequate pipe? Are you sitting with full batteries; better
a power supply?" would be convenient; since I am using my PC for
urgent duties, and didn't want to fiddle with unexpected upgrade bugs.
ProblemType: BugDistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.25
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Thu Oct 1 11:48:39 2020
InstallationDate: Installed on 2019-03-14 (566 days ago)
InstallationMedia: Kubuntu
[Touch-packages] [Bug 1796712] Re: libcurl3-gnutls in trusty fails to verify certificates when certificate chain is out-of-order
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: curl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1796712 Title: libcurl3-gnutls in trusty fails to verify certificates when certificate chain is out-of-order Status in curl package in Ubuntu: Confirmed Bug description: libcurl3-gnutls 7.35.0-1ubuntu2.17 fails to verify remote certificate if the certificate chain provided is out-of-order. This is caused by libgnutls-dev package dependency, since libgnutls26 package is apparently long known to have this issue: https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1373422 This bug can be observed with git, which depends on libcurl3-gnutls: git clone https://gnunet.org/git/libmicrohttpd.git/ Cloning into 'libmicrohttpd'... fatal: unable to access 'https://gnunet.org/git/libmicrohttpd.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none libgnutls28 package fixes this issue, since out-of-order certificate chains are allowed in that package. I am not very familiar with debian packaging process, so I was wondering if it is possible at all to bump dependency of libcurl3-gnutls from libgnutls-dev -> libgnutls28-dev for trusty. libgnutls28-dev conflicts with libgnutls-dev. At first sight, one of dependencies of libcurl3-gnutls-dev, lbrtmp-dev, also depends on libgnutls-dev. So, again I am not sure if this change is applicable or it causes nontrivial reverse-dependency issues. Given above bug filed against gnutls26 is still open after 4 years, I thought it might be easier to solve it on libcurl dependencies. (Is it?) Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1796712/+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 1930550] Re: usb sound devices crackling
Checked 5.9.16 - the same 5.8.5 - much rare and smaller (but 'cracks' still exists). Also there are cracks in 90% cases when i click on kmix tray app (opens kmix window), when i change volume or tab in kmix (between apps and hw), or when another app open stream. Its on all kernels and was on 20.04 too. 5.12 cant check, i have home profile on zfs, zfs dkms not builds on it. Also it much bigger in time and more noticeable now. There is no cracks when playing one stream on ae-5 and xonar d1, only usb affected. But there is sometimes when new app open stream or volume is changed, its not the case of that bug report, seems it some kind of general architecture problem >:-( >:-[ -- 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/1930550 Title: usb sound devices crackling Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrade from 20.04 to 21.04 all 3 my usb sound devices start crackling, i have xduoo05plus, audeze mobius, audient id4. I also tried to modify default-fragments = 5 default-fragment-size-msec = 2 to different sugested on stackoverflow articles setting Also this is in my config: high-priority = yes nice-level = -11 realtime-scheduling = yes realtime-priority = 5 I even tried to switch to pipewire, but it still the same. Possible issue in alsa kernel drivers for usb interface, submitting bug to pulse as it default in ubuntu. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jun 2 11:11:55 2021 InstallationDate: Installed on 2019-08-13 (658 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to hirsute on 2021-05-16 (16 days ago) dmi.bios.date: 08/12/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd08/12/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnB85-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85-HD3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2021-05-18T13:33:15.787174 mtime.conffile..etc.pulse.system.pa: 2021-05-18T11:20:40.860787 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1930550/+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 1854588] Re: gdebi-gtk calls pkexec inappropriately
I'm seeing the same buggy behavior on freshly installed Ubuntu MATE 20.04.2 LTS running inside VirtualBox. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1854588 Title: gdebi-gtk calls pkexec inappropriately Status in gdebi: Confirmed Status in gdebi package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu with gdebi-gtk installed 2. Open Firefox 3. Visit some site with deb-package download link or use direct link like https://github.com/jgm/pandoc/releases/download/2.9.2.1/pandoc-2.9.2.1-1-amd64.deb 4. Proceed with file downloading 5. In Firefox select Library → Downloads, click on downloaded deb-file Expected results: * gdebi-gtk is opened, the package installs normally after users clicks Install button Actual results: * gdebi-gtk is opened, the package is not installed because of vanishing of gdebi-gtk window just after clicking Install button Before anyone says this bug already exists... it doesn't (at least as far as I can see). It's just that a lot of similar bugs do/did exist where people have also experienced the same symptoms (of gdebi-gtk vanishing upon clicking 'Install'). So yes this is the same symptoms, but it must be a different cause as the circumstances are different and doesn't have the same resolution. The meat of it... Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or with Chrome if you installed that) go to any site that offers a .deb package and either... a) choose to open it directly from the browser (rather than saving it to 'Downloads' folder) b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that file from within the browser itself. You should find that gdebi-gtk appears but vanishes the moment you click 'Install' without a prompt for a password, an explanation or the package actually getting installed. This bug has existed since the beginning of Ubuntu 18.04 however it's been largely confused with other similar bugs. I've had it on half a dozen machines and confirmed it exists with IRC users on #ubuntu-mate of freenode. However with *this* bug (compared to others) gdebi-gtk works perfectly fine if you run it from the terminal or just double click the .deb package from your file manager. It's the kind of bug which if you're a hardened desktop Linux user, you'd just work around it... But if you're a novice and you can't get a simple thing like Teamviewer installed (which is a .deb, and a thing I might ask someone to do over the phone to try to help them) you likely get fed up and re-install Windows :S Any input on this would be brilliant as I can't seem to get any logs/output. ~lantizia To manage notifications about this bug go to: https://bugs.launchpad.net/gdebi/+bug/1854588/+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 1903351] Re: ignore_eacces and ignore_erofs patches don't work properly
I've reconciled the concern raised in comment #7 now. -- 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/1903351 Title: ignore_eacces and ignore_erofs patches don't work properly Status in procps package in Ubuntu: Fix Released Status in procps source package in Focal: In Progress Status in procps source package in Groovy: In Progress Status in procps source package in Hirsute: In Progress Bug description: The patches used to ignore errors in containers no longer work as of 3.3.16 due to upstream commit https://gitlab.com/procps- ng/procps/-/commit/7af88da373bb4d515a98ec2f0f5d56c63904f932 The ignore_eacces patch was fuzzed and gets applied to ReadSetting, not WriteSetting Both patches ignore the change that rc is no longer propagated up and instead everything is trapped by: if (!ignore_failure && errno != ENOENT) rc = -1; Versions affected: focal+ root@bfee89058713:/tmp# cat /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy root@bfee89058713:/# dpkg -l procps Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--= ii procps 2:3.3.16-5ubuntu2 amd64/proc file system utilities root@bfee89058713:/# echo "kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 255 root@bfee89058713:/# echo "-kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1903351/+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 1929371] Please test proposed package
Hello jeremyszu, or anyone else affected,
Accepted alsa-ucm-conf into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.2-1ubuntu0.8 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-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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.
--
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/1929371
Title:
[SRU] there is always a "Rear Microphone - Built-in Audio" option on
the input device list even if the microphone is unplugged
Status in OEM Priority Project:
Triaged
Status in alsa-ucm-conf package in Ubuntu:
Fix Released
Status in pulseaudio package in Ubuntu:
Fix Released
Status in alsa-ucm-conf source package in Focal:
Fix Committed
Status in pulseaudio source package in Focal:
Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
Fix Released
Status in pulseaudio source package in Hirsute:
Fix Committed
Bug description:
[Impact]
In Lenovo P520, which using a codec for front panel, the other codec for rear
panel and both are on a same card.
In this case, the rear Mic will present on input devices of "Sound
Settings" even if attaching nothing to rear mic jack.
[Fix]
For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl
because of
```
control.18 {
iface CARD
name 'Rear Mic Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
```
After applying "Rear Mic Jack", the rear Mic will not always there anymore
but it's not there as well if hot-plugging audio device on rear mic. Thus, it
needs to change pulseaudio to handle if all devices are off cases.
For pulseaudio, if there is no any audio devices attached, then
attaching an input device on rear mic jack. The port will not be
selected automatically because the profiles is off. It needs patch
pulseaudio to check off profiles (for dual codec case).
[Test]
After applying these patches, the rear mic jack works good in all cases (boot
without mic and then attach mic, boot with mic and then hotplug it) and other
functions (line-in / line-out) work pretty well.
[Where problems could occur]
This change only apply the bonus on below cases:
```
if ((has_input_port && found_available_input_port && !has_output_port) ||
(has_output_port && found_available_output_port && !has_input_port) ||
(has_input_port && found_available_input_port && has_output_port &&
found_available_output_port))
```
and these cases have been tested.
If there are some complex codec design then it might cause problem but so far
we didn't see that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1930286] Re: Defensics fuzzer testing tool cause openssh to segfault
I have produced a test pkg including the potential fix candidate above for the impacted UA customer to test in their lab. Unfortunately, I have no access to a reproducer since this fuzzer is proprietary and need to be purchased. Meaning, the testing will rely on UA customer end. - Eric ** Description changed: - I'm reporting this bug to keep track of it, as of today I'm still - collecting informations. + Here's what has been brought to my attention by a UA customer: - Here's what I have gathered so far: + * Release: + Xenial/16.04LTS - Release: Xenial/16.04LTS - Openssh version :7.2p2-4ubuntu2.10 - Fuzzer tool used: https://www.synopsys.com/software-integrity/security-testing/fuzz-testing.html (proprietary software) + * Openssh version: + 7.2p2-4ubuntu2.10 + + * Fuzzer tool used: + https://www.synopsys.com/software-integrity/security-testing/fuzz testing.html (proprietary software) As of today, I have no access to a reproducer. Still working on getting - access to one and better understand what the failing test scenario is - doing. + access to one (if possible) in order to better understand what the + failing test scenario is doing. - gdb backtrace: + * coredump: + $ gdb $(which sshd) core.cic-1.domain.tld.1612566260.sshd.20731 ... Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `sshd: [net] '. Program terminated with signal SIGSEGV, Segmentation fault. #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 136 ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S: No such file or directory. (gdb) bt #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 #1 0x7fec25b241db in memcpy (__len=, __src=0x0, __dest=) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #2 aes_gcm_ctrl (c=0x558a7ae19758, type=, arg=, ptr=0x0) at e_aes.c:1189 #3 0x7fec25b20897 in EVP_CIPHER_CTX_ctrl (ctx=ctx@entry=0x558a7ae19758, type=type@entry=18, arg=arg@entry=-1, ptr=ptr@entry=0x0) at evp_enc.c:619 #4 0x558a7953f54c in cipher_init (cc=cc@entry=0x558a7ae19750, cipher=0x558a797b3ef0 , key=0x0, keylen=32, iv=0x0, ivlen=, do_encrypt=0) at ../cipher.c:336 #5 0x558a7954521a in ssh_set_newkeys (ssh=ssh@entry=0x558a7ae18ef0, mode=mode@entry=0)at ../packet.c:919 #6 0x558a7955ae92 in kex_input_newkeys (type=, seq=, ctxt=0x558a7ae18ef0)at ../kex.c:434 #7 0x558a7954d269 in ssh_dispatch_run (ssh=ssh@entry=0x558a7ae18ef0, mode=0, done=0x558a7ae18278, ctxt=0x558a7ae18ef0) at ../dispatch.c:119 #8 0x558a7954d2b9 in ssh_dispatch_run_fatal (ssh=0x558a7ae18ef0, mode=, done=, ctxt=) at ../dispatch.c:140 #9 0x558a79502770 in do_ssh2_kex () at ../sshd.c:2744 #10 main (ac=, av=) at ../sshd.c:2301 (gdb) ** Summary changed: - Defensics fuzzer testing tool cause openssh to segfault + Defensics' synopsys fuzzer testing tool cause openssh to segfault ** Description changed: Here's what has been brought to my attention by a UA customer: * Release: Xenial/16.04LTS * Openssh version: 7.2p2-4ubuntu2.10 - * Fuzzer tool used: - https://www.synopsys.com/software-integrity/security-testing/fuzz testing.html (proprietary software) + * Fuzzer tool used: + https://www.synopsys.com/software-integrity/security-testing/fuzz-testing.html(proprietary software) As of today, I have no access to a reproducer. Still working on getting access to one (if possible) in order to better understand what the failing test scenario is doing. * coredump: $ gdb $(which sshd) core.cic-1.domain.tld.1612566260.sshd.20731 ... Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `sshd: [net] '. Program terminated with signal SIGSEGV, Segmentation fault. #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 136 ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S: No such file or directory. (gdb) bt #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 #1 0x7fec25b241db in memcpy (__len=, __src=0x0, __dest=) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #2 aes_gcm_ctrl (c=0x558a7ae19758, type=, arg=, ptr=0x0) at e_aes.c:1189 #3 0x7fec25b20897 in EVP_CIPHER_CTX_ctrl (ctx=ctx@entry=0x558a7ae19758, type=type@entry=18, arg=arg@entry=-1, ptr=ptr@entry=0x0) at evp_enc.c:619 #4 0x558a7953f54c in cipher_init (cc=cc@entry=0x558a7ae19750, cipher=0x558a797b3ef0 , key=0x0, keylen=32, iv=0x0, ivlen=, do_encrypt=0) at ../cipher.c:336 #5 0x558a7954521a in ssh_set_newkeys (ssh=ssh@entry=0x558a7ae18ef0, mode=mode@entry=0)at ../packet.c:919 #6 0x558a7955ae92 in kex_input_newkeys (type=, seq=, ctxt=0x558a7ae18ef0)at ../kex.c:434 #7 0x558a7954d269 in ssh_dispatch_run (ssh=ssh@entry=0x558a7ae18ef0, mode=0, done=0x558a7ae18278, ctxt=0x558a7ae18ef0) at ../dispatch.c:119 #8
[Touch-packages] [Bug 1929854] Re: Vital and critical configuration files get overridden by system updates without warning
Making changes to /usr/share/X11/locale/en_US.UTF-8/Compose was, at least for some time, the only way to make keyboard composition work in Ubuntu, as ~/.XCompose didn't work anymore, and creating a custom keyboard layout from scratch was not an option (my XCompose contains key compositions for almost the entire non-JCK UniCode character set in XCompose-coding). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1929854 Title: Vital and critical configuration files get overridden by system updates without warning Status in grub2 package in Ubuntu: New Status in libx11 package in Ubuntu: Invalid Status in openssh package in Ubuntu: Incomplete Bug description: • In my /usr/share/X11/locale/en_US.UTF-8/Compose I have about 10'000 lines of special compose keys defined. • In my /boot/grub/grub.cfg I have a very complicated special setup for my various boot configurations, and a 5-sec timout for my EFI-config. • My /etc/ssh/sshd_config contains a well-balanced configuration All these files are regularly overridden WITHOUT EVEN A SINGLE WARNING or ASKING BACK by ubuntu system setups (discover). I set all of them to read-only by root and no-access for group and other users, but they still get overridden by every other system update. I even have a shutdown process in place which should actually make sure that changes to these files are reverted by writing a backup copy over any newly installed override — unfortunately, everything I did to run either a custom shutdown process or a startup process with systemd turned out to not work and be a nightmare to make work. How somebody could be as bold as to override vital configuration files like this without even asking for consent is one of the strange miracles in this world which I'll probably never understand. However, if "ubuntu" is really what it translates to, it should take a little bit more care about pre-existing configurations on systems on which it is set up and running well — until one system update suddenly jeopardizes the functioning of the entire system. I'm pretty sure these are not the only configuration files which are carelessly just overridden. They're just the ones every other update breaks my system and inflinges on my the costs of hours of research until I find out that — of course — it was an overridden critical system configuration again. The really mean thing is that you don't notice anything when you run the update … only next time you start your system and of course are not aware anymore that you did a system update, the new (absolutely wrong and/or insufficent) settings are in place and shoot you in the leg. Take an example from gentoo's etc-update feature which lets you merge new configuration files with pre-existing ones using a diff3-update. I went away from gentoo for other reasons, but I always praised that feature. Please make sure immediately that critical configuration files do not get overridden if they are non-writable by root, and then gradually introduce a system that merges changes to configuration files with the current situation on the target system. Or at least present the configs that would be changed in a particular directory, so that anybody who is interested in preserving local settings could merge them in a suitable way. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 27 18:48:15 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297] InstallationDate: Installed on 2021-01-15 (132 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20QQS0KL13 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-53-generic root=UUID=35cef147-e021-4bdd-b8db-31a3192c8a6a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET38W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QQS0KL13 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: ZF211710 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO
[Touch-packages] [Bug 1930286] Re: Defensics fuzzer testing tool cause openssh to segfault
Potential fix candidate: https://github.com/openssh/openssh-portable/commit/2adbe1e63bc313d03e8e84e652cc623af8ebb163 ** Tags added: seg sts -- 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/1930286 Title: Defensics fuzzer testing tool cause openssh to segfault Status in openssh package in Ubuntu: New Status in openssh source package in Xenial: New Bug description: I'm reporting this bug to keep track of it, as of today I'm still collecting informations. Here's what I have gathered so far: Release: Xenial/16.04LTS Openssh version :7.2p2-4ubuntu2.10 Fuzzer tool used: https://www.synopsys.com/software-integrity/security-testing/fuzz-testing.html (proprietary software) As of today, I have no access to a reproducer. Still working on getting access to one and better understand what the failing test scenario is doing. gdb backtrace: $ gdb $(which sshd) core.cic-1.domain.tld.1612566260.sshd.20731 ... Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `sshd: [net] '. Program terminated with signal SIGSEGV, Segmentation fault. #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 136 ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S: No such file or directory. (gdb) bt #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 #1 0x7fec25b241db in memcpy (__len=, __src=0x0, __dest=) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #2 aes_gcm_ctrl (c=0x558a7ae19758, type=, arg=, ptr=0x0) at e_aes.c:1189 #3 0x7fec25b20897 in EVP_CIPHER_CTX_ctrl (ctx=ctx@entry=0x558a7ae19758, type=type@entry=18, arg=arg@entry=-1, ptr=ptr@entry=0x0) at evp_enc.c:619 #4 0x558a7953f54c in cipher_init (cc=cc@entry=0x558a7ae19750, cipher=0x558a797b3ef0 , key=0x0, keylen=32, iv=0x0, ivlen=, do_encrypt=0) at ../cipher.c:336 #5 0x558a7954521a in ssh_set_newkeys (ssh=ssh@entry=0x558a7ae18ef0, mode=mode@entry=0)at ../packet.c:919 #6 0x558a7955ae92 in kex_input_newkeys (type=, seq=, ctxt=0x558a7ae18ef0)at ../kex.c:434 #7 0x558a7954d269 in ssh_dispatch_run (ssh=ssh@entry=0x558a7ae18ef0, mode=0, done=0x558a7ae18278, ctxt=0x558a7ae18ef0) at ../dispatch.c:119 #8 0x558a7954d2b9 in ssh_dispatch_run_fatal (ssh=0x558a7ae18ef0, mode=, done=, ctxt=) at ../dispatch.c:140 #9 0x558a79502770 in do_ssh2_kex () at ../sshd.c:2744 #10 main (ac=, av=) at ../sshd.c:2301 (gdb) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1930286/+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 1929854] Re: Vital and critical configuration files get overridden by system updates without warning
libx11 owns it's files in /usr, users are not supposed to touch them ** Changed in: libx11 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1929854 Title: Vital and critical configuration files get overridden by system updates without warning Status in grub2 package in Ubuntu: New Status in libx11 package in Ubuntu: Invalid Status in openssh package in Ubuntu: Incomplete Bug description: • In my /usr/share/X11/locale/en_US.UTF-8/Compose I have about 10'000 lines of special compose keys defined. • In my /boot/grub/grub.cfg I have a very complicated special setup for my various boot configurations, and a 5-sec timout for my EFI-config. • My /etc/ssh/sshd_config contains a well-balanced configuration All these files are regularly overridden WITHOUT EVEN A SINGLE WARNING or ASKING BACK by ubuntu system setups (discover). I set all of them to read-only by root and no-access for group and other users, but they still get overridden by every other system update. I even have a shutdown process in place which should actually make sure that changes to these files are reverted by writing a backup copy over any newly installed override — unfortunately, everything I did to run either a custom shutdown process or a startup process with systemd turned out to not work and be a nightmare to make work. How somebody could be as bold as to override vital configuration files like this without even asking for consent is one of the strange miracles in this world which I'll probably never understand. However, if "ubuntu" is really what it translates to, it should take a little bit more care about pre-existing configurations on systems on which it is set up and running well — until one system update suddenly jeopardizes the functioning of the entire system. I'm pretty sure these are not the only configuration files which are carelessly just overridden. They're just the ones every other update breaks my system and inflinges on my the costs of hours of research until I find out that — of course — it was an overridden critical system configuration again. The really mean thing is that you don't notice anything when you run the update … only next time you start your system and of course are not aware anymore that you did a system update, the new (absolutely wrong and/or insufficent) settings are in place and shoot you in the leg. Take an example from gentoo's etc-update feature which lets you merge new configuration files with pre-existing ones using a diff3-update. I went away from gentoo for other reasons, but I always praised that feature. Please make sure immediately that critical configuration files do not get overridden if they are non-writable by root, and then gradually introduce a system that merges changes to configuration files with the current situation on the target system. Or at least present the configs that would be changed in a particular directory, so that anybody who is interested in preserving local settings could merge them in a suitable way. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 27 18:48:15 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297] InstallationDate: Installed on 2021-01-15 (132 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20QQS0KL13 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-53-generic root=UUID=35cef147-e021-4bdd-b8db-31a3192c8a6a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET38W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QQS0KL13 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: ZF211710 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN2NET38W(1.23):bd06/04/2020:br1.23:efr1.14:svnLENOVO:pn20QQS0KL13:pvrThinkPadP53:rvnLENOVO:rn20QQS0KL13:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
[Touch-packages] [Bug 1925775] Update Released
The verification of the Stable Release Update for gnome-online-accounts has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1925775 Title: SRU the current 3.36.1 stable update Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Focal: Fix Released Bug description: * Impact That's the current GNOME stable update, including some API documentation fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Try adding online account in a GNOME session, ensure the service is correctly enabled in application, for example that a google accounts are picked up in gnome-calendar and evolution. * Regression potential The changes are in API documentation so nothing specific to check, if there is an issue it would be from a toolchain regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1925775/+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 1926843] Re: online accounts integration with fb isn't working
This bug was fixed in the package gnome-online-accounts - 3.36.1-0ubuntu1 --- gnome-online-accounts (3.36.1-0ubuntu1) focal; urgency=medium * New stable version (lp: #1925775) * debian/rules: disable the facebook provider since it's current not working (lp: #1926843) -- Sebastien Bacher Mon, 10 May 2021 17:03:46 +0200 ** Changed in: gnome-online-accounts (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1926843 Title: online accounts integration with fb isn't working Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Focal: Fix Released Status in gnome-online-accounts source package in Hirsute: Fix Released Bug description: * Impact The online accounts setting are proposing a facebook item which isn't working * Test case Go to settings -> online account, browse the accounts option proposed, facebook shouldn't be in the list since it doesn't work. * Regression potential The change is to disable the facebook provider using the upstream provided build option. Check that facebook isn't listed anymore but that the other providers still are. Since it's a build option change it could fail to build so check for that as well on launchpad. Since the facebook service currently doesn't consider gnome-online- accounts as a valid client there should be no user with that provider configured. Even if there were since the service isn't working they would see a functional regression. --- Hi i tryed to use gnome-control-center online-accounts to make easy like windows 10 to login to email or add other login so its more easy with ID to use pincode or other ID fingerprint and other. But its look its much issue compared with windows 10 with thunderbird, firefox, and other program. Worst is facebook only little windows with issue with login? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-online-accounts 3.38.1-1ubuntu1 Uname: Linux 5.12.0-051200-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:38:03 2021 InstallationDate: Installed on 2019-05-07 (725 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+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 1925775] Re: SRU the current 3.36.1 stable update
This bug was fixed in the package gnome-online-accounts - 3.36.1-0ubuntu1 --- gnome-online-accounts (3.36.1-0ubuntu1) focal; urgency=medium * New stable version (lp: #1925775) * debian/rules: disable the facebook provider since it's current not working (lp: #1926843) -- Sebastien Bacher Mon, 10 May 2021 17:03:46 +0200 ** Changed in: gnome-online-accounts (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1925775 Title: SRU the current 3.36.1 stable update Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Focal: Fix Released Bug description: * Impact That's the current GNOME stable update, including some API documentation fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Try adding online account in a GNOME session, ensure the service is correctly enabled in application, for example that a google accounts are picked up in gnome-calendar and evolution. * Regression potential The changes are in API documentation so nothing specific to check, if there is an issue it would be from a toolchain regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1925775/+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 1926437] Re: [SRU] Backport zstd support, fix bug in python-apt
This bug was fixed in the package python-apt - 2.0.0ubuntu0.20.04.5
---
python-apt (2.0.0ubuntu0.20.04.5) focal; urgency=medium
* debfile: Pass `Name` instead of `Binary` to ExtractTar.
Passing the binary causes it to fail trying to find the `false`
compressor when a binary for a given compressor is not installed.
(LP: #1926437)
* Update mirror lists
-- Julian Andres Klode Thu, 29 Apr 2021 16:12:21
+0200
** Changed in: python-apt (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
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/1926437
Title:
[SRU] Backport zstd support, fix bug in python-apt
Status in apt package in Ubuntu:
Fix Released
Status in python-apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Fix Released
Status in python-apt source package in Xenial:
Fix Released
Status in python-apt source package in Bionic:
Fix Released
Status in python-apt source package in Focal:
Fix Released
Status in python-apt source package in Groovy:
Fix Committed
Status in python-apt source package in Hirsute:
Fix Released
Status in python-apt source package in Impish:
Fix Released
Bug description:
[Impact]
APT in xenial needs to learn about zstd support to enable Launchpad to work
with zstd packages.
python-apt in all releases needs to be adjusted to pass the compressor
names instead of programs to ExtractTar, as otherwise, if
/usr/bin/zstd does not exist, it will pass "false" as the compressor,
and then ExtractTar fails (same for other compressors).
On hirsute, the python-apt upload also includes some new
annotations for build-dependencies, as it's a straight upload of the 2.2
stable series.
[Test plan]
The apt regression tests cover the compression methods extensively, including
even stored compressed lists in /var/lib/apt and fetching Packages files
compressed with such methods, for all compression methods.
The final test is to make apt_inst.DebFile("glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
1923845 work in python3-apt.
For hirsute, the build dependency changes will verify themselves
during the build ;)
[Where problems could occur]
APT:
The changes to APT are adding the zstd compression backend to FileFd
and then linking it into the configuration. The former is adding new
code, triggered only on zstd files, and should not be able to cause
regressions.
The latter is a bunch of small lines here and there, and it caused
issues during backporting in the test suite because it expected
compressors in a specific order. However, chances are that nothing
else has as stringent requirements as the test suite, so I don't
believe that is a problem for existing users.
Bugs can of course be in the code dealing with zstd, and that might
open you up to security vulnerabilities in the zstd code if you pass
APT zstd compressed files.
A regression can be if clients used apt-helper cat-file to cat a zstd-
compressed file ending in .zst - they'll now get uncompressed content,
rather than compressed.
python-apt:
The change just replaces Binary with Name, aligning the code with APT
itself, so it's so trivial, we don't expect regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926437/+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 1930584] Re: InstallProgress is not being used as a context manager
Ok, thanks Julian. For future reference, which was the proper place to report this bug? Here or over at bugs.debian? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1930584 Title: InstallProgress is not being used as a context manager Status in python-apt package in Ubuntu: Won't Fix Bug description: Package: python3-apt Version: 2.2.0 As can be seen in the constructor, InstallProgress is designed to be used in a 'with' in order to properly close write_stream and status_stream: https://git.launchpad.net/python-apt/tree/apt/progress/base.py#n163 This commit added support for using InstallProgress as a context manager: https://git.launchpad.net/python- apt/commit/?id=462c05b39eae5a0fa2270d329b03d4711742f20d It also modified a test, but didn't change the way InstallProgress is used by cache.py. This causes Python 3 to complain that InstallProgress's constructor leaves unclosed files: > /usr/lib/python3.9/glob.py:123: ResourceWarning: unclosed file <_io.TextIOWrapper name=4 mode='r' encoding='UTF-8'> > with os.scandir(dirname) as it: > Object allocated at (most recent call last): > File "/opt/thinlinc/modules/thinlinc/packageinstaller/__init__.py", lineno 33 > OOO0o000 = globals ( ) [ IIi1i111IiII ] . Backend ( ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", lineno 88 > self . _aptcallback = i1Ii1i ( self ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", lineno 31 > super ( ) . __init__ ( ) > File "/usr/lib/python3/dist-packages/apt/progress/base.py", lineno 164 > self.status_stream = os.fdopen(self.statusfd, "r") # type: io.TextIOBase # noqa > File "/usr/lib/python3.9/os.py", lineno 1023 > return io.open(fd, *args, **kwargs) > /usr/lib/python3.9/glob.py:123: ResourceWarning: unclosed file <_io.TextIOWrapper name=5 mode='w' encoding='UTF-8'> > with os.scandir(dirname) as it: > Object allocated at (most recent call last): > File "/opt/thinlinc/modules/thinlinc/packageinstaller/__init__.py", lineno 33 > OOO0o000 = globals ( ) [ IIi1i111IiII ] . Backend ( ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", lineno 88 > self . _aptcallback = i1Ii1i ( self ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", lineno 31 > super ( ) . __init__ ( ) > File "/usr/lib/python3/dist-packages/apt/progress/base.py", lineno 163 > self.write_stream = os.fdopen(self.writefd, "w") # type: io.TextIOBase > File "/usr/lib/python3.9/os.py", lineno 1023 > return io.open(fd, *args, **kwargs) The issue was identified on Ubuntu 21.04: > Linux ubuntu2104 5.11.0-17-generic #18-Ubuntu SMP Thu May 6 20:10:11 > UTC 2021 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1930584/+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 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default
** Changed in: dnsmasq (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1894619 Title: [2.82 regression] router announcements have 'forever' lifetime by default Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq package in Debian: New Bug description: The default lifetime was changed to 1 day in 2.82 in the change corresponding to this changelog entry: Change default lease time for DHCPv6 to one day. Fine, but the same commit also did this: Alter calculation of preferred and valid times in router advertisements, so that these do not have a floor applied of the lease time in the dhcp-range if this is not explicitly specified and is merely the default. And that change is buggy and causes advertisements to have infinite lifetime, when you are using the default. See this thread http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2020q3/014341.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+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 1906741] Re: Firefox sometimes causes garbled audio
I have the same issue on Xubuntu 20.04. I find that just exiting Firefox completely and relaunching it resolves the audio problem on other applications and stays fixed, even after relaunching Firefox, unless I go to a website that causes the issue to start again. So, it seems to be very website specific for triggering it. One website that always triggered it was, strangely enough, www.subway.com. I was in a live meeting with MS Teams at the same time, but not 100% sure that MS Teams factored into it except that the audio of the meeting got scrambled up until I exited Firefox. If I went back to that website again, it would happen again. Unlike the other commenters, I don't even have a webcam on this PC at the moment, so I don't think it's webcam related. But, I do have some other hardware in common with the previous poster -- specifically Radeon and Starship/Matisse Audio. At the time of the incident, the audio (of both MS Teams and Firefox) was playing on the Starship/Matisse Audio port. But based on all of the comments here, it doesn't seem to be sound/video card specific, as I'm seeing both Nvidia vs Radeon and Intel vs AMD throughout this thread. $ lspci | grep Audio 2d:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] 2f:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller $ uname -a Linux sylvester 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:39:42 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -l | grep firefox ii firefox 88.0.1+build1-0ubuntu0.20.04.2 amd64Safe and easy web browser from Mozilla ii firefox-locale-en 88.0.1+build1-0ubuntu0.20.04.2 amd64English language pack for Firefox $ sudo lshw -C sound *-multimedia description: Audio device product: Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0.1 bus info: pci@:2d:00.1 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:116 memory:fce6-fce63fff *-usb:2 description: Audio device product: Plantronics .Audio 478 USB vendor: Plantronics physical id: 3 bus info: usb@5:2.1.3 version: 2.43 capabilities: usb-2.00 audio-control configuration: driver=usbhid maxpower=120mA speed=12Mbit/s *-multimedia description: Audio device product: Starship/Matisse HD Audio Controller vendor: Advanced Micro Devices, Inc. [AMD] physical id: 0.4 bus info: pci@:2f:00.4 version: 00 width: 32 bits clock: 33MHz capabilities: pm pciexpress msi bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:118 memory:fcd0-fcd07fff -- 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/1906741 Title: Firefox sometimes causes garbled audio Status in firefox package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Opening certain applications/websites at the same time as Firefox causes the audio to become garbled. The audio sounds distorted with an echo. Certain actions are guaranteed to cause this, but it can also happening when only running instances of Firefox. I've been able to consistently cause this by launching Zoom from a link within Firefox. This does not occur when using Chrome. The only way to fix the issue is to shut down all audio-related programs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 83.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rdevans 55475 F pulseaudio /dev/snd/controlC0: rdevans 55475 F pulseaudio /dev/snd/controlC3: rdevans 55475 F pulseaudio /dev/snd/controlC1: rdevans 55475 F pulseaudio BuildID: 20201112153044 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 16:55:36 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on
[Touch-packages] [Bug 1930584] Re: InstallProgress is not being used as a context manager
I kind of don't need the bug in both places. I'd suggest to go fix your backend to pass an install progress and use a with statement, that we don't use one inside apt.cache was intentional. This means it produces warnings if you don't pass one, but frankly, that's bad practice. ** Changed in: python-apt (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1930584 Title: InstallProgress is not being used as a context manager Status in python-apt package in Ubuntu: Won't Fix Bug description: Package: python3-apt Version: 2.2.0 As can be seen in the constructor, InstallProgress is designed to be used in a 'with' in order to properly close write_stream and status_stream: https://git.launchpad.net/python-apt/tree/apt/progress/base.py#n163 This commit added support for using InstallProgress as a context manager: https://git.launchpad.net/python- apt/commit/?id=462c05b39eae5a0fa2270d329b03d4711742f20d It also modified a test, but didn't change the way InstallProgress is used by cache.py. This causes Python 3 to complain that InstallProgress's constructor leaves unclosed files: > /usr/lib/python3.9/glob.py:123: ResourceWarning: unclosed file <_io.TextIOWrapper name=4 mode='r' encoding='UTF-8'> > with os.scandir(dirname) as it: > Object allocated at (most recent call last): > File "/opt/thinlinc/modules/thinlinc/packageinstaller/__init__.py", lineno 33 > OOO0o000 = globals ( ) [ IIi1i111IiII ] . Backend ( ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", lineno 88 > self . _aptcallback = i1Ii1i ( self ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", lineno 31 > super ( ) . __init__ ( ) > File "/usr/lib/python3/dist-packages/apt/progress/base.py", lineno 164 > self.status_stream = os.fdopen(self.statusfd, "r") # type: io.TextIOBase # noqa > File "/usr/lib/python3.9/os.py", lineno 1023 > return io.open(fd, *args, **kwargs) > /usr/lib/python3.9/glob.py:123: ResourceWarning: unclosed file <_io.TextIOWrapper name=5 mode='w' encoding='UTF-8'> > with os.scandir(dirname) as it: > Object allocated at (most recent call last): > File "/opt/thinlinc/modules/thinlinc/packageinstaller/__init__.py", lineno 33 > OOO0o000 = globals ( ) [ IIi1i111IiII ] . Backend ( ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", lineno 88 > self . _aptcallback = i1Ii1i ( self ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", lineno 31 > super ( ) . __init__ ( ) > File "/usr/lib/python3/dist-packages/apt/progress/base.py", lineno 163 > self.write_stream = os.fdopen(self.writefd, "w") # type: io.TextIOBase > File "/usr/lib/python3.9/os.py", lineno 1023 > return io.open(fd, *args, **kwargs) The issue was identified on Ubuntu 21.04: > Linux ubuntu2104 5.11.0-17-generic #18-Ubuntu SMP Thu May 6 20:10:11 > UTC 2021 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1930584/+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 1930591] [NEW] Not able to attach secondary display through HDMI
Public bug reported: Not able to attach secondary display through HDMI ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 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: Wed Jun 2 19:09:31 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:1854] InstallationDate: Installed on 2021-05-01 (32 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard HP 2000 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=4b855eaf-8204-49cb-8e54-11983d2916a7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2013 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1854 dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.2A dmi.chassis.asset.tag: 5CG3244HK1 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 100.42 dmi.modalias: dmi:bvnInsyde:bvrF.45:bd12/19/2013:br15.69:efr100.42:svnHewlett-Packard:pnHP2000NotebookPC:pvr098E130059160:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PRE X=MIN dmi.product.name: HP 2000 Notebook PC dmi.product.sku: E4X59PA#ACJ dmi.product.version: 098E130059160 dmi.sys.vendor: Hewlett-Packard 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 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 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/1930591 Title: Not able to attach secondary display through HDMI Status in xorg package in Ubuntu: New Bug description: Not able to attach secondary display through HDMI ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 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: Wed Jun 2 19:09:31 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:1854] InstallationDate: Installed on 2021-05-01 (32 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard HP 2000 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=4b855eaf-8204-49cb-8e54-11983d2916a7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2013 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1854 dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.2A dmi.chassis.asset.tag: 5CG3244HK1 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 100.42 dmi.modalias:
[Touch-packages] [Bug 1930584] Re: InstallProgress is not being used as a context manager
Also reported to debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989389 ** Bug watch added: Debian Bug tracker #989389 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989389 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1930584 Title: InstallProgress is not being used as a context manager Status in python-apt package in Ubuntu: New Bug description: Package: python3-apt Version: 2.2.0 As can be seen in the constructor, InstallProgress is designed to be used in a 'with' in order to properly close write_stream and status_stream: https://git.launchpad.net/python-apt/tree/apt/progress/base.py#n163 This commit added support for using InstallProgress as a context manager: https://git.launchpad.net/python- apt/commit/?id=462c05b39eae5a0fa2270d329b03d4711742f20d It also modified a test, but didn't change the way InstallProgress is used by cache.py. This causes Python 3 to complain that InstallProgress's constructor leaves unclosed files: > /usr/lib/python3.9/glob.py:123: ResourceWarning: unclosed file <_io.TextIOWrapper name=4 mode='r' encoding='UTF-8'> > with os.scandir(dirname) as it: > Object allocated at (most recent call last): > File "/opt/thinlinc/modules/thinlinc/packageinstaller/__init__.py", lineno 33 > OOO0o000 = globals ( ) [ IIi1i111IiII ] . Backend ( ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", lineno 88 > self . _aptcallback = i1Ii1i ( self ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", lineno 31 > super ( ) . __init__ ( ) > File "/usr/lib/python3/dist-packages/apt/progress/base.py", lineno 164 > self.status_stream = os.fdopen(self.statusfd, "r") # type: io.TextIOBase # noqa > File "/usr/lib/python3.9/os.py", lineno 1023 > return io.open(fd, *args, **kwargs) > /usr/lib/python3.9/glob.py:123: ResourceWarning: unclosed file <_io.TextIOWrapper name=5 mode='w' encoding='UTF-8'> > with os.scandir(dirname) as it: > Object allocated at (most recent call last): > File "/opt/thinlinc/modules/thinlinc/packageinstaller/__init__.py", lineno 33 > OOO0o000 = globals ( ) [ IIi1i111IiII ] . Backend ( ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", lineno 88 > self . _aptcallback = i1Ii1i ( self ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", lineno 31 > super ( ) . __init__ ( ) > File "/usr/lib/python3/dist-packages/apt/progress/base.py", lineno 163 > self.write_stream = os.fdopen(self.writefd, "w") # type: io.TextIOBase > File "/usr/lib/python3.9/os.py", lineno 1023 > return io.open(fd, *args, **kwargs) The issue was identified on Ubuntu 21.04: > Linux ubuntu2104 5.11.0-17-generic #18-Ubuntu SMP Thu May 6 20:10:11 > UTC 2021 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1930584/+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 1930584] [NEW] InstallProgress is not being used as a context manager
Public bug reported: Package: python3-apt Version: 2.2.0 As can be seen in the constructor, InstallProgress is designed to be used in a 'with' in order to properly close write_stream and status_stream: https://git.launchpad.net/python-apt/tree/apt/progress/base.py#n163 This commit added support for using InstallProgress as a context manager: https://git.launchpad.net/python- apt/commit/?id=462c05b39eae5a0fa2270d329b03d4711742f20d It also modified a test, but didn't change the way InstallProgress is used by cache.py. This causes Python 3 to complain that InstallProgress's constructor leaves unclosed files: > /usr/lib/python3.9/glob.py:123: ResourceWarning: unclosed file > <_io.TextIOWrapper name=4 mode='r' encoding='UTF-8'> > with os.scandir(dirname) as it: > Object allocated at (most recent call last): > File "/opt/thinlinc/modules/thinlinc/packageinstaller/__init__.py", lineno > 33 > OOO0o000 = globals ( ) [ IIi1i111IiII ] . Backend ( ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", > lineno 88 > self . _aptcallback = i1Ii1i ( self ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", > lineno 31 > super ( ) . __init__ ( ) > File "/usr/lib/python3/dist-packages/apt/progress/base.py", lineno 164 > self.status_stream = os.fdopen(self.statusfd, "r") # type: io.TextIOBase > # noqa > File "/usr/lib/python3.9/os.py", lineno 1023 > return io.open(fd, *args, **kwargs) > /usr/lib/python3.9/glob.py:123: ResourceWarning: unclosed file > <_io.TextIOWrapper name=5 mode='w' encoding='UTF-8'> > with os.scandir(dirname) as it: > Object allocated at (most recent call last): > File "/opt/thinlinc/modules/thinlinc/packageinstaller/__init__.py", lineno > 33 > OOO0o000 = globals ( ) [ IIi1i111IiII ] . Backend ( ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", > lineno 88 > self . _aptcallback = i1Ii1i ( self ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", > lineno 31 > super ( ) . __init__ ( ) > File "/usr/lib/python3/dist-packages/apt/progress/base.py", lineno 163 > self.write_stream = os.fdopen(self.writefd, "w") # type: io.TextIOBase > File "/usr/lib/python3.9/os.py", lineno 1023 > return io.open(fd, *args, **kwargs) The issue was identified on Ubuntu 21.04: > Linux ubuntu2104 5.11.0-17-generic #18-Ubuntu SMP Thu May 6 20:10:11 > UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ** Affects: python-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 python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1930584 Title: InstallProgress is not being used as a context manager Status in python-apt package in Ubuntu: New Bug description: Package: python3-apt Version: 2.2.0 As can be seen in the constructor, InstallProgress is designed to be used in a 'with' in order to properly close write_stream and status_stream: https://git.launchpad.net/python-apt/tree/apt/progress/base.py#n163 This commit added support for using InstallProgress as a context manager: https://git.launchpad.net/python- apt/commit/?id=462c05b39eae5a0fa2270d329b03d4711742f20d It also modified a test, but didn't change the way InstallProgress is used by cache.py. This causes Python 3 to complain that InstallProgress's constructor leaves unclosed files: > /usr/lib/python3.9/glob.py:123: ResourceWarning: unclosed file <_io.TextIOWrapper name=4 mode='r' encoding='UTF-8'> > with os.scandir(dirname) as it: > Object allocated at (most recent call last): > File "/opt/thinlinc/modules/thinlinc/packageinstaller/__init__.py", lineno 33 > OOO0o000 = globals ( ) [ IIi1i111IiII ] . Backend ( ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", lineno 88 > self . _aptcallback = i1Ii1i ( self ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", lineno 31 > super ( ) . __init__ ( ) > File "/usr/lib/python3/dist-packages/apt/progress/base.py", lineno 164 > self.status_stream = os.fdopen(self.statusfd, "r") # type: io.TextIOBase # noqa > File "/usr/lib/python3.9/os.py", lineno 1023 > return io.open(fd, *args, **kwargs) > /usr/lib/python3.9/glob.py:123: ResourceWarning: unclosed file <_io.TextIOWrapper name=5 mode='w' encoding='UTF-8'> > with os.scandir(dirname) as it: > Object allocated at (most recent call last): > File "/opt/thinlinc/modules/thinlinc/packageinstaller/__init__.py", lineno 33 > OOO0o000 = globals ( ) [ IIi1i111IiII ] . Backend ( ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", lineno 88 > self . _aptcallback = i1Ii1i ( self ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", lineno 31 > super ( ) . __init__ ( ) > File
[Touch-packages] [Bug 1930582] [NEW] Fix ICL PCH no picture after S3
Public bug reported: [Impact] Blank DP display after S3 on Intel GFX in ICL PCH desktop. [Fix] Use proper IRQ setup so the system in question can detect HPD after S3. [Test] Suspend and resume the system. No picture on DP display. With the patch applied, DP display works as expected. [Where problems could occur] It changes how the Intel GFX setup its HPD IRQ, so hotplug detection will be affected. This change is limited to ICL PCH. This is the second patch of "drm/i915/gen9bc: Handle TGP PCH during suspend/resume", but somehow it was omitted. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Hirsute) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1930202 sutton ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided => Medium ** Tags added: oem-priority originate-from-1930202 sutton -- 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/1930582 Title: Fix ICL PCH no picture after S3 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] Blank DP display after S3 on Intel GFX in ICL PCH desktop. [Fix] Use proper IRQ setup so the system in question can detect HPD after S3. [Test] Suspend and resume the system. No picture on DP display. With the patch applied, DP display works as expected. [Where problems could occur] It changes how the Intel GFX setup its HPD IRQ, so hotplug detection will be affected. This change is limited to ICL PCH. This is the second patch of "drm/i915/gen9bc: Handle TGP PCH during suspend/resume", but somehow it was omitted. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930582/+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 1929817] Re: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only)
Installed the pulseaudio-1:13.99.1-1ubuntu3.11 on two different machines, one of them have 4 digital mic and after installed the proposed pulseaudio, we could adjust 4 channel input volume through gnome or pulseaudio, the other machine has 2 digital mics, and the proposed pulseaudio worked as well as before. verified done on focal. ** 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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1929817 Title: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only) Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Bug description: [Impact] Many Lenovo laptops have up to 4 microphones (microphone array), before the linux kernel 5.11, the alsa mixer for digital microphone is 2 channels, and the PA in the focal also supports up to 2 chanels for a single alsa mixer, so the PA in the focal works well with linux kernel 5.10 and lower on those Lenovo laptops. But we are going to install hirsute kernel (5.11) to the focal, the PA in the focal can't handle 4 channels of the digital mic, it will use pure software volume for digital mic, user can't adjust hardware volume of the digital mic anymore. [Fix] Backport 2 patches from PA-14.2, the PA in the hirsute (21.04) already have these 2 patches, so this SRU is for focal only. After applying these 2 patches, the PA could handle up to 8 channels for a single alsa mixer. [Test] Install patched PA on Lenovo laptops with 4 digital microphone, I could change the hardware input volume of digital mic through pulseaudio. I also installed patched PA to some old lenovo and Dell machines, all output and input devices worked as well as before, there is no regression observed. [Where problems could occur] This could introduce a regression on the output/input volume control, for example, the output or input volume only supports software volume in the PA, users can't adjust the hardware volume through pulseaudio anymore. But this regression possibility is very low, first the hirsute already has these 2 patches, second I already tested these 2 patches on different machines, all worked as well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1929817/+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 1152187] Re: [MIR] systemd
** Changed in: systemd (Ubuntu Bionic) Status: Incomplete => Fix Committed -- 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/1152187 Title: [MIR] systemd Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: * The package is in universe and built on all archs: https://launchpad.net/ubuntu/+source/systemd/44-10ubuntu1 * Rationale: - in a first step we want systemd-services promoted to replace ubuntu- system-services - We will also want to move from consolekit to logind soon (https://blueprints.launchpad.net/ubuntu/+spec/foundations-1303 -consolekit-logind-migration) - udev has been merged in the systemd source upstream so we will want to build it from there at some point as well we don't plan to use the systemd init system at this point * Security: there has been some security issues in the past http://secunia.com/advisories/search/?search=systemd http://secunia.com/advisories/48220/ http://secunia.com/advisories/48208/ http://secunia.com/advisories/48331/ Those are mostly logind issue and have been fixed upstream. Our current package is outdated but we do plan to update it before starting using logind. There should be no issue with the services * Quality: - there is no RC bug in debian: http://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=systemd - there is no bug open in launchpad: https://launchpad.net/ubuntu/+source/systemd/+bugs - upstream is active and responsive to issues The desktop bugs team is subscribed to the package in launchpad, foundations/desktop will maintain the package and look to the bug reports regularly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1152187/+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 1926547] Re: Add Dell Privacy Mic Mute Key mapping
Test with machine which supports Dell privacy. Mic mute key works well in groovy and focal. [kernel version] linux-oem-20.04b (1029) ** Tags removed: verification-needed-focal verification-needed-groovy ** Tags added: verification-done-focal verification-done-groovy -- 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/1926547 Title: Add Dell Privacy Mic Mute Key mapping Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Status in systemd source package in Hirsute: Fix Committed Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * The change can only work with kernel commit on some specific hardware, ex. Latitude 9520. The commit series is "hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree. https://patchwork.kernel.org/project/alsa-devel/list/?series=465445 * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1926547/+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 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default
** Bug watch added: Debian Bug tracker #989378 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989378 ** Also affects: dnsmasq (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989378 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1894619 Title: [2.82 regression] router announcements have 'forever' lifetime by default Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq package in Debian: Unknown Bug description: The default lifetime was changed to 1 day in 2.82 in the change corresponding to this changelog entry: Change default lease time for DHCPv6 to one day. Fine, but the same commit also did this: Alter calculation of preferred and valid times in router advertisements, so that these do not have a floor applied of the lease time in the dhcp-range if this is not explicitly specified and is merely the default. And that change is buggy and causes advertisements to have infinite lifetime, when you are using the default. See this thread http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2020q3/014341.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+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 1930550] Re: usb sound devices crackling
Thanks for the bug report. Please try some older and newer kernel versions and tell us if they have the same problem: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1930550 Title: usb sound devices crackling Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrade from 20.04 to 21.04 all 3 my usb sound devices start crackling, i have xduoo05plus, audeze mobius, audient id4. I also tried to modify default-fragments = 5 default-fragment-size-msec = 2 to different sugested on stackoverflow articles setting Also this is in my config: high-priority = yes nice-level = -11 realtime-scheduling = yes realtime-priority = 5 I even tried to switch to pipewire, but it still the same. Possible issue in alsa kernel drivers for usb interface, submitting bug to pulse as it default in ubuntu. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jun 2 11:11:55 2021 InstallationDate: Installed on 2019-08-13 (658 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to hirsute on 2021-05-16 (16 days ago) dmi.bios.date: 08/12/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd08/12/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnB85-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85-HD3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2021-05-18T13:33:15.787174 mtime.conffile..etc.pulse.system.pa: 2021-05-18T11:20:40.860787 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1930550/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts
IMO the change should be reverted later in Impish as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Committed Status in gdb source package in Focal: New Status in glibc source package in Focal: Opinion Status in gdb source package in Groovy: New Status in glibc source package in Groovy: Opinion Status in gdb source package in Hirsute: New Status in glibc source package in Hirsute: Opinion Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Committed Bug description: [Impact] * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not installed. [Test Plan] * Check that ld.so is not stripped on armhf: $ /lib/*/ld-2.31.so libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not stripped * Check that ld.so is stripped on amd64: $ file /lib/x86_64-linux-gnu/ld-2.31.so /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped [Where problems could occur] * The fix is not stripping ld.so on armhf. Not stripping it comes with a notable increase in file size and it may be performance critical 109K stripped vs 1.3M unstripped. Accidentally ld.so could be left unstripped on other architectures, but the test plan covers checking that, at least on amd64. Other than those not stripping ld.so should not cause any issue. [Original Bug Text] see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+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 1930550] [NEW] usb sound devices crackling
Public bug reported: After upgrade from 20.04 to 21.04 all 3 my usb sound devices start crackling, i have xduoo05plus, audeze mobius, audient id4. I also tried to modify default-fragments = 5 default-fragment-size-msec = 2 to different sugested on stackoverflow articles setting Also this is in my config: high-priority = yes nice-level = -11 realtime-scheduling = yes realtime-priority = 5 I even tried to switch to pipewire, but it still the same. Possible issue in alsa kernel drivers for usb interface, submitting bug to pulse as it default in ubuntu. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jun 2 11:11:55 2021 InstallationDate: Installed on 2019-08-13 (658 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to hirsute on 2021-05-16 (16 days ago) dmi.bios.date: 08/12/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd08/12/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnB85-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85-HD3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2021-05-18T13:33:15.787174 mtime.conffile..etc.pulse.system.pa: 2021-05-18T11:20:40.860787 ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1930550 Title: usb sound devices crackling Status in pulseaudio package in Ubuntu: New Bug description: After upgrade from 20.04 to 21.04 all 3 my usb sound devices start crackling, i have xduoo05plus, audeze mobius, audient id4. I also tried to modify default-fragments = 5 default-fragment-size-msec = 2 to different sugested on stackoverflow articles setting Also this is in my config: high-priority = yes nice-level = -11 realtime-scheduling = yes realtime-priority = 5 I even tried to switch to pipewire, but it still the same. Possible issue in alsa kernel drivers for usb interface, submitting bug to pulse as it default in ubuntu. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jun 2 11:11:55 2021 InstallationDate: Installed on 2019-08-13 (658 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to hirsute on 2021-05-16 (16 days ago) dmi.bios.date: 08/12/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd08/12/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnB85-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85-HD3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85-HD3 dmi.product.sku: To be
[Touch-packages] [Bug 1927192] Re: gdb ftbfs on armhf, testsuite timeouts
@doko Not stripping ld.so on Focal came with an increase of ld.so from 110K to 1.3M. I don't think this is an acceptable increase when pulling in libc6-dbg also fixes the problem. See the test package here: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4570 ** Description changed: [Impact] * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not installed. [Test Plan] * Check that ld.so is not stripped on armhf: + $ /lib/*/ld-2.31.so + libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not stripped * Check that ld.so is stripped on amd64: $ file /lib/x86_64-linux-gnu/ld-2.31.so /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped [Where problems could occur] * The fix is not stripping ld.so on armhf. Not stripping it comes with a - slight increase in file size but this should not be performance - critical. Accidentally ld.so could be left unstripped on other - architectures, but the test plan covers checking that, at least on - amd64. Other than those not stripping ld.so should not cause any issue. - + notable increase in file size and it may be performance critical 109K + stripped vs 1.3M unstripped. Accidentally ld.so could be left unstripped + on other architectures, but the test plan covers checking that, at least + on amd64. Other than those not stripping ld.so should not cause any + issue. [Original Bug Text] see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 ** Changed in: glibc (Ubuntu Hirsute) Status: New => Opinion ** Changed in: glibc (Ubuntu Groovy) Status: New => Opinion ** Changed in: glibc (Ubuntu Focal) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Committed Status in gdb source package in Focal: New Status in glibc source package in Focal: Opinion Status in gdb source package in Groovy: New Status in glibc source package in Groovy: Opinion Status in gdb source package in Hirsute: New Status in glibc source package in Hirsute: Opinion Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Committed Bug description: [Impact] * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not installed. [Test Plan] * Check that ld.so is not stripped on armhf: $ /lib/*/ld-2.31.so libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not stripped * Check that ld.so is stripped on amd64: $ file /lib/x86_64-linux-gnu/ld-2.31.so /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped [Where problems could occur] * The fix is not stripping ld.so on armhf. Not stripping it comes with a notable increase in file size and it may be performance critical 109K stripped vs 1.3M unstripped. Accidentally ld.so could be left unstripped on other architectures, but the test plan covers checking that, at least on amd64. Other than those not stripping ld.so should not cause any issue. [Original Bug Text] see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+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 1925742] Update Released
The verification of the Stable Release Update for evolution-data-server has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Released Bug description: * Impact The Icloud service introduced changes that are confusing evolution- data-server which means evolution is now failing to connect to the email server * Test case Set up an iCloud account and try to use it for emails in evolution * Regression potential The change is in the imapx connection code, it could create problems with other type of servers so we should try to test on different providers. - The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1922951] Re: SRU the current 3.36.5 stable update
This bug was fixed in the package evolution-data-server - 3.36.5-0ubuntu1 --- evolution-data-server (3.36.5-0ubuntu1) focal; urgency=medium * New stable version (lp: #1922951) * debian/patches/git_imapx_compat.patch: cherry pick a fix needed for compatibility with the new iCloud behaviour (lp: #1925742) -- Sebastien Bacher Wed, 07 Apr 2021 20:27:39 +0200 ** Changed in: evolution-data-server (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1922951 Title: SRU the current 3.36.5 stable update Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Released Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the calendar integration in GNOME and gnome-calendar is working, also test evolution with an email account. * Regression potential There is no specific change or feature to test in the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1922951/+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 1922951] Update Released
The verification of the Stable Release Update for evolution-data-server has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1922951 Title: SRU the current 3.36.5 stable update Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Released Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the calendar integration in GNOME and gnome-calendar is working, also test evolution with an email account. * Regression potential There is no specific change or feature to test in the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1922951/+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 1922951] Re: SRU the current 3.36.5 stable update
The 3.36.5-0ubuntu1 update is working as expected, evolution is able to access calendar emails and contact, gnome-calendar integration is working ** 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 evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1922951 Title: SRU the current 3.36.5 stable update Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Released Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the calendar integration in GNOME and gnome-calendar is working, also test evolution with an email account. * Regression potential There is no specific change or feature to test in the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1922951/+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 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
This bug was fixed in the package evolution-data-server - 3.36.5-0ubuntu1 --- evolution-data-server (3.36.5-0ubuntu1) focal; urgency=medium * New stable version (lp: #1922951) * debian/patches/git_imapx_compat.patch: cherry pick a fix needed for compatibility with the new iCloud behaviour (lp: #1925742) -- Sebastien Bacher Wed, 07 Apr 2021 20:27:39 +0200 ** Changed in: evolution-data-server (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Released Bug description: * Impact The Icloud service introduced changes that are confusing evolution- data-server which means evolution is now failing to connect to the email server * Test case Set up an iCloud account and try to use it for emails in evolution * Regression potential The change is in the imapx connection code, it could create problems with other type of servers so we should try to test on different providers. - The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts
** Description changed: + [Impact] + + * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not + installed. + + [Test Plan] + + * Check that ld.so is not stripped on armhf: + + * Check that ld.so is stripped on amd64: + + $ file /lib/x86_64-linux-gnu/ld-2.31.so + /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped + + [Where problems could occur] + + * The fix is not stripping ld.so on armhf. Not stripping it comes with a + slight increase in file size but this should not be performance + critical. Accidentally ld.so could be left unstripped on other + architectures, but the test plan covers checking that, at least on + amd64. Other than those not stripping ld.so should not cause any issue. + + + [Original Bug Text] + see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Committed Status in gdb source package in Focal: New Status in glibc source package in Focal: New Status in gdb source package in Groovy: New Status in glibc source package in Groovy: New Status in gdb source package in Hirsute: New Status in glibc source package in Hirsute: New Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Committed Bug description: [Impact] * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not installed. [Test Plan] * Check that ld.so is not stripped on armhf: $ /lib/*/ld-2.31.so libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not stripped * Check that ld.so is stripped on amd64: $ file /lib/x86_64-linux-gnu/ld-2.31.so /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped [Where problems could occur] * The fix is not stripping ld.so on armhf. Not stripping it comes with a notable increase in file size and it may be performance critical 109K stripped vs 1.3M unstripped. Accidentally ld.so could be left unstripped on other architectures, but the test plan covers checking that, at least on amd64. Other than those not stripping ld.so should not cause any issue. [Original Bug Text] see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+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 1930103] Re: isc-dhcp-server overwrites /etc/default/isc-dhcp-server during update
I had a working setup and it was broken by update. The config file was modified/recreated/whatever. I don't know what was exactly written in this file before update and no backup was created. In any case, update must not break working config, especially on LTS version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1930103 Title: isc-dhcp-server overwrites /etc/default/isc-dhcp-server during update Status in isc-dhcp package in Ubuntu: New Bug description: Today unattended upgrade of ISC DHCPD overwrite config file /etc/default/isc-dhcp-server and set wrong interface where daemon have to listen (eno2 instead of br0 as was set before update). I see no backup file of original config file so I had to investigate where the problem was. Update have to never overwrite config file and throw away previous version. /var/log/apt/history.log: Start-Date: 2021-05-28 06:17:41 Commandline: /usr/bin/unattended-upgrade Upgrade: isc-dhcp-server:amd64 (4.4.1-2.1ubuntu5, 4.4.1-2.1ubuntu5.20.04.2) End-Date: 2021-05-28 06:17:47 root@linux:~# ls -l /etc/default/isc-dhcp-server -rw-r--r-- 1 root root 629 May 28 06:17 /etc/default/isc-dhcp-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1930103/+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 1919177] Re: Azure: issues with accelerated networking on Hirsute
It's been there for almost 3 months, I think it can wait a few more
days. It's affecting Azure's users who use Hirsute instances with
accelerated networking enabled, I don't know how many users that is.
--
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/1919177
Title:
Azure: issues with accelerated networking on Hirsute
Status in cloud-init:
Incomplete
Status in cloud-init package in Ubuntu:
Incomplete
Status in linux-azure package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Fix Released
Status in cloud-init source package in Hirsute:
Incomplete
Status in linux-azure source package in Hirsute:
Invalid
Status in systemd source package in Hirsute:
New
Bug description:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
enabled, sometimes part of the cloud-init configuration is not
applied.
Especially, in those cases, the public SSH key is not setup properly.
[how to reproduce]
Start a VM with AN enabled:
```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"
--image
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY"
--accelerated-networking
```
After a moment, try to SSH: if you succeed, delete and recreate a new
VM.
[troubleshooting]
To be able to connect into the VM, run:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
```
In "/run/cloud-init/instance-data.json", I can see:
```
"publicKeys": [
{
"keyData": "",
"path": "/home/ubuntu/.ssh/authorized_keys"
}
],
```
as expected.
[workaround]
As mentioned, Azure allows the user to run command into the VM without
SSH connection. To do so, one can use the Azure CLI:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
This example uses "ssh-import-id" but it's also possible to just echo
a given public key into /home/ubuntu/.ssh/authorized_keys
NOTE: this will only solves the SSH issue, I do not know if this bug
affects other things. If so the user would have to apply those things
manually.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1919177/+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
Re: [Touch-packages] [Bug 1921696] Re: Failed to start Load/Save RF Kill Switch Status
Installed Ubuntu 20.04. Enabled "Developer Options". Updated and systemd 245.4-4ubuntu3.7 was installed. Rebooted and the system booted and worked OK. However the installed version of Ubuntu 20.04 use Kernel: 5.8.0-54-generic x86_64. Bluetooth works fine. Den ons 2 juni 2021 kl 01:15 skrev Brian Murray <1921...@bugs.launchpad.net >: > Hello Per-Inge, or anyone else affected, > > Accepted systemd into focal-proposed. The package will build now and be > available at > https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.7 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- > focal to verification-done-focal. If it does not fix the bug for you, > please add a comment stating that, and change the tag to verification- > failed-focal. 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: systemd (Ubuntu Focal) >Status: In Progress => Fix Committed > > ** Tags added: verification-needed-focal > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1921696 > > Title: > Failed to start Load/Save RF Kill Switch Status > > Status in systemd: > Fix Released > Status in systemd package in Ubuntu: > Fix Released > Status in systemd source package in Focal: > Fix Committed > Status in systemd source package in Groovy: > Fix Committed > > Bug description: > [impact] > > systemd-rfkill fails when running under kernel 5.10 or later due to > change in the kernel/userspace api > > [test case] > > on a system with kernel 5.10 or later, check systemd-rfkill status or > journal output, see comment 3 for specific failure text > > [regression] > > any regression would almost certainly cause problems with the systemd- > rfkill service and/or systemd-rfkill binary > > [scope] > > this is needed for focal > > this was fixed upstream in commit > a71c09685021cbcecb7566a00342421f635cc002 which was backported to h in > version 247.3-3ubuntu3. > > since this only occurs with kernel 5.10 or later, no releases earlier > than f are affected because they will never receive kernel 5.10. > > since the HWE kernel in f will be updated to 5.10 once 21.04 is > released, this is needed for f. Since a user could upgrade to the 5.10 > HWE kernel in f, and then do-release-upgrade to g before it EOL, this > is also needed in g. > > [original description] > > > When I boot the system I get these lög messages > - Failed to start Load/Save RF Kill Switch Statu > - A start job for unit systemd-rfkill.service has failed > and with sender systemd-rfkil > Read event structure of invalid size > > Also happens on an Ubuntu system on the same computer. > > System details > > p-i@pi-tuf-b550m-wifi:~$ inxi -Fz > System:Kernel: 5.11.0-11-generic x86_64 bits: 64 Desktop: Cinnamon > 4.8.6 Distro: Ubuntu 21.04 (Hirsute Hippo) > Machine: Type: Desktop System: ASUS product: N/A v: N/A serial: > > Mobo: ASUSTeK model: TUF GAMING B550M-PLUS (WI-FI) v: Rev > X.0x serial: UEFI: American Megatrends v: 1804 > date: 02/02/2021 > CPU: Info: 6-Core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP > L2 cache: 3 MiB > Speed: 2509 MHz min/max: 2200/4791 MHz Core speeds (MHz): 1: > 2509 2: 2237 3: 2858 4: 2236 5: 2235 6: 2238 7: 2798 > 8: 2239 9: 2238 10: 2233 11: 2236 12: 2234 > Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX > 5600 OEM/5600 XT / 5700/5700 XT] driver: amdgpu > v: kernel > Display: x11 server: X.Org 1.20.10 driver: loaded: amdgpu,ati > unloaded: fbdev,modesetting,radeon,vesa > resolution: 2560x1440~60Hz > OpenGL: renderer: AMD Radeon RX 5700 (NAVI10 DRM 3.40.0 > 5.11.0-11-generic LLVM 11.0.1) v: 4.6 Mesa 21.0.1 > Audio: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio > driver: snd_hda_intel > Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD > Audio driver: snd_hda_intel > Device-3: Logitech Webcam C250 type: USB driver: > snd-usb-audio,uvcvideo > Sound
[Touch-packages] [Bug 1854588] Re: gdebi-gtk calls pkexec inappropriately
Can somebody please re-check and confirm on focal? On UM focal I'm not seeing this issue but do so on hirsute and impish. When we click on a .deb file firefox asks 'What should Firefox do with this file?, with `open with` and `save` being two options. I tried the following one by one. a) Chose open with. Install with gdebi was OK. b) Chose save. But opened downloaded file from within firefox (from download icon on navigation bar). OK. c) Chose save but then opened downloaded file from Caja. OK. On hirsute and impish only c) works. a) and b) fail. Gdebi version on focal: 0.9.5.7+nmu3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1854588 Title: gdebi-gtk calls pkexec inappropriately Status in gdebi: Confirmed Status in gdebi package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu with gdebi-gtk installed 2. Open Firefox 3. Visit some site with deb-package download link or use direct link like https://github.com/jgm/pandoc/releases/download/2.9.2.1/pandoc-2.9.2.1-1-amd64.deb 4. Proceed with file downloading 5. In Firefox select Library → Downloads, click on downloaded deb-file Expected results: * gdebi-gtk is opened, the package installs normally after users clicks Install button Actual results: * gdebi-gtk is opened, the package is not installed because of vanishing of gdebi-gtk window just after clicking Install button Before anyone says this bug already exists... it doesn't (at least as far as I can see). It's just that a lot of similar bugs do/did exist where people have also experienced the same symptoms (of gdebi-gtk vanishing upon clicking 'Install'). So yes this is the same symptoms, but it must be a different cause as the circumstances are different and doesn't have the same resolution. The meat of it... Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or with Chrome if you installed that) go to any site that offers a .deb package and either... a) choose to open it directly from the browser (rather than saving it to 'Downloads' folder) b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that file from within the browser itself. You should find that gdebi-gtk appears but vanishes the moment you click 'Install' without a prompt for a password, an explanation or the package actually getting installed. This bug has existed since the beginning of Ubuntu 18.04 however it's been largely confused with other similar bugs. I've had it on half a dozen machines and confirmed it exists with IRC users on #ubuntu-mate of freenode. However with *this* bug (compared to others) gdebi-gtk works perfectly fine if you run it from the terminal or just double click the .deb package from your file manager. It's the kind of bug which if you're a hardened desktop Linux user, you'd just work around it... But if you're a novice and you can't get a simple thing like Teamviewer installed (which is a .deb, and a thing I might ask someone to do over the phone to try to help them) you likely get fed up and re-install Windows :S Any input on this would be brilliant as I can't seem to get any logs/output. ~lantizia To manage notifications about this bug go to: https://bugs.launchpad.net/gdebi/+bug/1854588/+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
