[Touch-packages] [Bug 1854557] Re: Sync opencv 4.1.2+dfsg-5 (universe) from Debian unstable (main)
Published on 2019-11-30 Copied from debian sid in Primary Archive for Debian GNU/Linux by Gianfranco Costamagna ** Changed in: opencv (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1854557 Title: Sync opencv 4.1.2+dfsg-5 (universe) from Debian unstable (main) Status in opencv package in Ubuntu: Fix Released Bug description: Please sync opencv 4.1.2+dfsg-5 (universe) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Move from libgdcm2-dev to libgdcm-dev. * No-change rebuild against libgdcm3.0 * Rebuild against new libproj15. The Debian package has changed to libgdcm-dev too. Changelog entries since current focal version 4.1.2+dfsg-4ubuntu3: opencv (4.1.2+dfsg-5) unstable; urgency=medium [ Bas Couwenberg ] * Replace libgdbm2-dev with libgdbm-dev, and libvtkgdcm2-dev with libvtkgdcm-dev. (closes: #944341) [ Mo Zhou ] * Add AVX512_COMMON to amd64 dispatch list, and VFPV3,NEON to arm64 list. * Exclude gdcm development packages from B-D on non-release architectures. [ Gianfranco Costamagna ] * Remove builddir-static to save some space (Closes: #943706) -- Mo Zhou Sun, 24 Nov 2019 16:08:26 +0800 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1854557/+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 1854891] [NEW] Editing crontab by script doesn't work
Public bug reported:
I wrote a script to automatically edit a crontab across a fleet of machines.
The script works something like this:
ex $crontab << EOT
wq!
EOT
I set EDITOR to point at that script, and then run "crontab -e", only to
find that the program says "No modification made". I carefully debugged
my script to ensure that it was actually making a change. In spite of
the change, crontab(1) claims "No modification made" and rejects the
changes.
After other attempts at troubleshooting failed, I delved into the source
code. The "No modification made" error is reported after "crontab"
checks the file modification time, which it does both before and after
calling $EDITOR.
The check is done like this:
if (statbuf.st_mtime == fsbuf->st_mtime) {
return 1; /* No change to file */
}
According to the stat(2) Linux man page, "st_mtime" is actually a macro
defined as:
#define st_mtime st_mtim.tv_sec
So it seems that the problem is that editing a file by script takes less
than a second, and this method of checking a file's modification time
only provides 1-second resolution.
It seems that attempting to move away from using the st_mtime field
would introduce some portability problems, since Linux and MacOS X
provide incompatible ways to get subsecond precision on a file's
modification time.
In the meantime, I will call sleep(1) from my script to ensure that
enough time passes that crontab can see that there was a change.
** Affects: cron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1854891
Title:
Editing crontab by script doesn't work
Status in cron package in Ubuntu:
New
Bug description:
I wrote a script to automatically edit a crontab across a fleet of machines.
The script works something like this:
ex $crontab << EOT
wq!
EOT
I set EDITOR to point at that script, and then run "crontab -e", only
to find that the program says "No modification made". I carefully
debugged my script to ensure that it was actually making a change. In
spite of the change, crontab(1) claims "No modification made" and
rejects the changes.
After other attempts at troubleshooting failed, I delved into the
source code. The "No modification made" error is reported after
"crontab" checks the file modification time, which it does both before
and after calling $EDITOR.
The check is done like this:
if (statbuf.st_mtime == fsbuf->st_mtime) {
return 1; /* No change to file */
}
According to the stat(2) Linux man page, "st_mtime" is actually a
macro defined as:
#define st_mtime st_mtim.tv_sec
So it seems that the problem is that editing a file by script takes
less than a second, and this method of checking a file's modification
time only provides 1-second resolution.
It seems that attempting to move away from using the st_mtime field
would introduce some portability problems, since Linux and MacOS X
provide incompatible ways to get subsecond precision on a file's
modification time.
In the meantime, I will call sleep(1) from my script to ensure that
enough time passes that crontab can see that there was a change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1854891/+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 1854890] Re: apt has package conflicts whenever I attempt to install gcc and gcc-guile in one line using apt install
** Attachment added: "Screenshot from 2019-12-02 23-04-45.png" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1854890/+attachment/5309460/+files/Screenshot%20from%202019-12-02%2023-04-45.png -- 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/1854890 Title: apt has package conflicts whenever I attempt to install gcc and gcc- guile in one line using apt install Status in apt package in Ubuntu: New Bug description: Description: Ubuntu 18.04.3 LTS Release: 18.04 apt: Installed: 1.6.12 Candidate: 1.6.12 Version table: *** 1.6.12 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.6.6ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.6.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Expected Results: apt should have installed gcc first and then gcc-guile, instead of reporting package inconsistency because installing gcc via apt and then guile had no issues for me. Actual Results: apt reports a package error and that packages may be broken. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.12 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 2 22:42:04 2019 InstallationDate: Installed on 2019-12-01 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1854890/+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 1854890] [NEW] apt has package conflicts whenever I attempt to install gcc and gcc-guile in one line using apt install
Public bug reported: Description:Ubuntu 18.04.3 LTS Release:18.04 apt: Installed: 1.6.12 Candidate: 1.6.12 Version table: *** 1.6.12 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.6.6ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.6.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Expected Results: apt should have installed gcc first and then gcc-guile, instead of reporting package inconsistency because installing gcc via apt and then guile had no issues for me. Actual Results: apt reports a package error and that packages may be broken. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.12 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 2 22:42:04 2019 InstallationDate: Installed on 2019-12-01 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1854890 Title: apt has package conflicts whenever I attempt to install gcc and gcc- guile in one line using apt install Status in apt package in Ubuntu: New Bug description: Description: Ubuntu 18.04.3 LTS Release: 18.04 apt: Installed: 1.6.12 Candidate: 1.6.12 Version table: *** 1.6.12 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.6.6ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.6.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Expected Results: apt should have installed gcc first and then gcc-guile, instead of reporting package inconsistency because installing gcc via apt and then guile had no issues for me. Actual Results: apt reports a package error and that packages may be broken. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.12 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 2 22:42:04 2019 InstallationDate: Installed on 2019-12-01 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1854890/+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 1843479]
Well, yes, but patches can be posted to binut...@sourceware.org without a bugzilla open. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in binutils: Confirmed Status in binutils package in Ubuntu: In Progress Status in gzip package in Ubuntu: In Progress Bug description: Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1843479/+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 1843479]
(In reply to Alan Modra from comment #3) > (In reply to Balint Reczey from comment #2) > > Did I miss something? > > You did. By subtracting off_adjust from the value written to p_offset you > potentially have p_offset mod page_size != p_vaddr mod page_size. > > This will fail the glibc test in elf/dl-load.c resulting in "ELF load > command address/offset not properly aligned" Thanks. Could you please consider accepting a fixed patch rather than closing the bug as won't fix? While this is not an issue with traditional loaders, users of WSL would certainly appreciate strip not generating binaries crashing there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in binutils: Confirmed Status in binutils package in Ubuntu: In Progress Status in gzip package in Ubuntu: In Progress Bug description: Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1843479/+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 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
** Changed in: binutils Status: Won't Fix => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in binutils: Confirmed Status in binutils package in Ubuntu: In Progress Status in gzip package in Ubuntu: In Progress Bug description: Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1843479/+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 1854864] Re: In the Settings app, the word "Dock" is used instead of "Dash"
** Also affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1854864 Title: In the Settings app, the word "Dock" is used instead of "Dash" Status in gnome-shell package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Bug description: Ubuntu 19.10 1) Open Settings app. The word "Dock" is displayed as an option. 2) The word "Dash" should have been displayed instead of "Dock". The "Visual overview of Gnome" in the "Ubuntu Desktop Guide" refers to the icon bar as the "Dash". 3) The word "Dock" was displayed instead of "Dash". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1854864/+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 1099788] Re: I can't uninstall completely whoopsie
Please open a new bug report about this issue.
On Thu, Nov 28, 2019 at 01:06:22PM -, Andreas Nadobnik wrote:
> I have a similar issue while removing whoopsie within a preseed
> installation, so whoopsie will be removed before it is started the first
> time.
>
> $ sudo apt purge whoopsie
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages will be REMOVED:
> whoopsie*
> 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
> After this operation, 0 B of additional disk space will be used.
> Do you want to continue? [Y/n] y
> (Reading database ... 227602 files and directories currently installed.)
> Purging configuration files for whoopsie (0.2.69) ...
> rm: cannot remove '/var/lib/whoopsie/whoopsie-id': No such file or directory
> dpkg: error processing package whoopsie (--purge):
> installed whoopsie package post-removal script subprocess returned error
> exit status 1
> Errors were encountered while processing:
> whoopsie
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>
> As you can see, the post-removal script is missing the whoopsie-id file.
> After creating the dir and file, the post-removal script runs fine.
>
> Tested under Ubuntu focal.
>
> --
> You received this bug notification because you are subscribed to
> whoopsie in Ubuntu.
> https://bugs.launchpad.net/bugs/1099788
>
> Title:
> I can't uninstall completely whoopsie
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1099788/+subscriptions
>
--
Brian Murray
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1099788
Title:
I can't uninstall completely whoopsie
Status in whoopsie package in Ubuntu:
Invalid
Bug description:
$ sudo aptitude -y purge whoopsie
The following packages will be REMOVED:
whoopsie{p}
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
(Reading database ... 331880 files and directories currently installed.)
Removing whoopsie ...
Purging configuration files for whoopsie ...
dpkg: error processing whoopsie (--purge):
subprocess installed post-removal script returned error exit status 1
No apport report written because MaxReports is reached already
Errors were
encountered while processing:
whoopsie
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: whoopsie (not installed)
Uname: Linux 3.7.2-999-i7 x86_64
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
Date: Tue Jan 15 12:29:07 2013
InstallationDate: Installed on 2013-01-10 (4 days ago)
InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Release
amd64(20121023)
MarkForUpload: True
ProcEnviron:
LANGUAGE=es_ES:en
TERM=xterm
PATH=(custom, no user)
LANG=es_ES.UTF-8
SHELL=/bin/bash
SourcePackage: whoopsie
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1099788/+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 1846787] Re: systemd-logind leaves leftover sessions and scope files
The autopkgtests regression on docker.io are unrelated to this change.
The failure is on debian/tests/basic-smoke; it happens because
'debootstrap stable ' fails the gpg verification of the Release
file -- the keys used for the Buster stable release are not found in
Xenial's debian-archive-keyring.
This only happens on Xenial; on Bionic and later the debian-archive-
keyring is sufficiently updated.
The workaround is to just patch docker.io/xenial to use 'debootstrap
--no-gpg-check' (the debian debootstrap image is only used to run 'true'
in a container).
The proper solution is a bit more involved on debian-archive-keyring;
discussing this w/ cjwatson.
I'm not sure the proper solution is actually required on this case -- or
even in the general case, as we haven't had bug reports yet about this
since the Buster release in early July.
So we can probably just go with the workaround, but it's a non-runtime
affecting change (build/test-time only), so would have to piggyback on
another SRU to docker.io anyway, i.e., it won't make it to the archive
just to fix this autopkgtest regression.
Thus, we should probably just ignore the docker.io regressions -- I'll
test those w/ PPA build w/ the workaround above.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1846787
Title:
systemd-logind leaves leftover sessions and scope files
Status in dbus package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in dbus source package in Xenial:
Fix Committed
Status in systemd source package in Xenial:
Fix Committed
Bug description:
[Impact]
Scope file leakage can cause SSH delays and reduce performance in systemd
[Description]
The current systemd-logind version present in Xenial can leave abandoned SSH
sessions and scope files in cases where the host sees a lot of concurrent SSH
connections. These leftover sessions can slow down systemd performance
greatly, and can have an impact on sshd handling a great number of concurrent
connections.
To fix this issue, patches are needed in both dbus and systemd. These improve
the
performance of the communication between dbus and systemd, so that they can
handle a better volume of events (e.g. SSH logins). All of those patches are
already present from Bionic onwards, so we only need those fixes for Xenial.
== Systemd ==
Upstream patches:
- core: use an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification
(d8fdc62037b5)
$ git describe --contains d8fdc62037b5
v230~71^2~2
$ rmadison systemd
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.22 | xenial-updates | source, ... <
systemd | 237-3ubuntu10| bionic | source, ...
systemd | 237-3ubuntu10.29 | bionic-security | source, ...
systemd | 237-3ubuntu10.29 | bionic-updates | source, ...
systemd | 237-3ubuntu10.31 | bionic-proposed | source, ...
== DBus ==
Upstream patches:
- Only read one message at a time if there are fds pending (892f084eeda0)
- bus: Fix timeout restarts (529600397bca)
- DBusMainLoop: ensure all required timeouts are restarted (446b0d9ac75a)
$ git describe --contains 892f084eeda0 529600397bca 446b0d9ac75a
dbus-1.11.10~44
dbus-1.11.10~45
dbus-1.11.16~2
$ rmadison dbus
dbus | 1.10.6-1ubuntu3| xenial | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-security | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-updates | source, ... <
dbus | 1.12.2-1ubuntu1| bionic | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-security | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-updates | source, ...
[Test Case]
1) Simulate a lot of concurrent SSH connections with e.g. a for loop:
multipass@xenial-logind:~$ for i in {1..1000}; do sleep 0.1; ssh localhost
sleep 1 & done
2) Check for leaked sessions in /run/systemd/system/:
multipass@xenial-logind:~$ ls -ld /run/systemd/system/session-*.scope*
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-103.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-104.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-105.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-106.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-110.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-111.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-112.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-113.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-114.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-115.scope.d
drwxr-xr-x 2
[Touch-packages] [Bug 21837] Re: debdelta integration / zsync support
Windows and android have delta updates. https://en.wikipedia.org/wiki/Delta_update -- 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/21837 Title: debdelta integration / zsync support Status in apt package in Ubuntu: Triaged Status in apt package in Baltix: Confirmed Bug description: Ubuntu should, like Mandrake 10.2, Firefox 1.5 and Windows, update packages using binary patches instead of by re-downloading entire packages. This would be especially helpful when running beta versions of software which change daily. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/21837/+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 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional
To answer the question posed on IRC. I do not know at this time if any fix to this will be SRUed to Xenial. A proper generic fix will require a new userspace api. The owner conditional can not be properly generically answered without subject context. This api can be fixed for the inquiring tasks subject querying against the the object, but the the generic case of querying where an external helper task H needs to query whether task A with profile P can access file F can not be fixed with the current api. Fixing the query using the subjects task is possible to SRU Xenial. The generic fix of a new API will not be SRUed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1620635 Title: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional Status in AppArmor: Triaged Status in Snappy: Won't Fix Status in apparmor package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Download and compile the following sample C app that calls aa_query_label wget https://launchpadlibrarian.net/207629699/query_file.c gcc -o query_file query_file.c -l apparmor 2. Install a snap that uses the home interface, for example demo-wget: snap install demo-wget 3. Create a file in your home: touch /home/USERNAME/testfile 4. Ask apparmor if demo-wget can read that file with query_file: ./query_file snap.demo-wget.wget /home/USERNAME/testfile Expected result: output of ./query_file command is read '/home/kaleo/toto' allowed Current result: output of ./query_file command is read '/home/kaleo/toto' denied To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1620635/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
The same. HP Omen as per this https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852636. Eoan with 5.3.0-24-generic -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+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 1707831] Re: [enhancement] Replace the "Activities" label with the Ubuntu icon/logo/glyph
In Windows XP, Microsoft placed the Windows logo next to "start". In MacOS, Apple placed there logo in the top left corner. Why not place the Ubuntu logo to the left of "Activities"? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1707831 Title: [enhancement] Replace the "Activities" label with the Ubuntu icon/logo/glyph Status in gnome-shell package in Ubuntu: Won't Fix Status in ubuntu-themes package in Ubuntu: Won't Fix Bug description: I suggest replacing the "Activities" label with the Ubuntu icon/logo. "Activities" sounds awkward and misleading. It would be more suitably vague, and more consistent with the existing Unity7 experience if the Gnome Shell "Activities" label was replaced by just the Ubuntu logo. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Tue Aug 1 11:28:08 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-03 (89 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) 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/1707831/+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 1854682] Re: Add option to "Privacy" in Ubuntu Settings that would enable/disable software installation outside trusted app stores.
I will add it to the "ubuntu-devel-discuss" mailing list. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1854682 Title: Add option to "Privacy" in Ubuntu Settings that would enable/disable software installation outside trusted app stores. Status in ubuntu-settings package in Ubuntu: Opinion Bug description: 1) Ubuntu 19.10 2) Gnome Settings 1:3.34.1-1ubuntu2 3) Ability to block installation of untrusted software not in trusted app stores(Ubuntu Software Center, Steam, etc). 4) Unable to block installation of untrusted software not in trusted app stores. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1854682/+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 1845529] Re: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/`
** Also affects: gawk (Ubuntu Focal) Importance: Undecided Status: Invalid ** Also affects: mawk (Ubuntu Focal) Importance: Undecided Status: Invalid ** Also affects: ubuntu-meta (Ubuntu Focal) Importance: Undecided Status: Invalid ** Also affects: bash-completion (Ubuntu Focal) Importance: High Status: Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mawk in Ubuntu. https://bugs.launchpad.net/bugs/1845529 Title: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/` Status in bash-completion package in Ubuntu: Triaged Status in gawk package in Ubuntu: Invalid Status in mawk package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Invalid Status in bash-completion source package in Focal: Triaged Status in gawk source package in Focal: Invalid Status in mawk source package in Focal: Invalid Status in ubuntu-meta source package in Focal: Invalid Status in Debian: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 19.10 using minimal desktop option 2. Open terminal and enter `umount /dev/s` and then hit Expected result: * bash completion works as expected Actual results: * bash completion does not work : $ umount /dev/awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined $ umount /meawk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bash-completion 1:2.9-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Thu Sep 26 18:46:59 2019 Dependencies: InstallationDate: Installed on 2019-09-26 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1845529/+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 1850267] Re: autopkgtest 'nm' fails because it can't find dnsmasq
** Description changed: [impact] test 'nm' fails [test case] see test results http://autopkgtest.ubuntu.com/packages/network-manager/bionic/amd64 [regression potential] low, test fix only [other info] - disco and later already include dnsmasq-base in test dep packages, this - is needed only for bionic + disco and later already include dnsmasq-base in test dep packages, and + in xenial network-manager directly depends on dnsmasq-base. So this is + needed only for bionic. ** Description changed: [impact] - test 'nm' fails + test 'nm' fails because dnsmasq-base isn't installed [test case] see test results http://autopkgtest.ubuntu.com/packages/network-manager/bionic/amd64 [regression potential] low, test fix only [other info] + The d/t/control file 'nm' test section, for bionic, needs to include + dnsmasq-base in its dep list. + disco and later already include dnsmasq-base in test dep packages, and in xenial network-manager directly depends on dnsmasq-base. So this is needed only for bionic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1850267 Title: autopkgtest 'nm' fails because it can't find dnsmasq Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: In Progress Bug description: [impact] test 'nm' fails because dnsmasq-base isn't installed [test case] see test results http://autopkgtest.ubuntu.com/packages/network-manager/bionic/amd64 [regression potential] low, test fix only [other info] The d/t/control file 'nm' test section, for bionic, needs to include dnsmasq-base in its dep list. disco and later already include dnsmasq-base in test dep packages, and in xenial network-manager directly depends on dnsmasq-base. So this is needed only for bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850267/+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 1850267] Re: autopkgtest 'nm' fails because it can't find dnsmasq
** Description changed: [impact] test 'nm' fails [test case] see test results http://autopkgtest.ubuntu.com/packages/network-manager/bionic/amd64 [regression potential] low, test fix only + + [other info] + + disco and later already include dnsmasq-base in test dep packages, this + is needed only for bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1850267 Title: autopkgtest 'nm' fails because it can't find dnsmasq Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: In Progress Bug description: [impact] test 'nm' fails [test case] see test results http://autopkgtest.ubuntu.com/packages/network-manager/bionic/amd64 [regression potential] low, test fix only [other info] disco and later already include dnsmasq-base in test dep packages, this is needed only for bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850267/+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 1825946] Re: 'nm' autopkgtest fails due to GI stderr output
> nm test no longer fails due to stderr output as listed in description. nm
> test does now fail due to the test thinking dnsmasq is not available, but
> that's a separate bug.
For this I opened bug 1850267
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1825946
Title:
'nm' autopkgtest fails due to GI stderr output
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Xenial:
New
Status in network-manager source package in Bionic:
Fix Released
Bug description:
[impact]
'nm' testcase contains:
from gi.repository import NetworkManager, NMClient, GLib
which generates output to stderr:
/tmp/autopkgtest.naU0ts/build.riU/src/debian/tests/nm:23: PyGIWarning:
NetworkManager was imported without specifying a version first. Use
gi.require_version('NetworkManager', '1.0') before import to ensure that the
right version gets loaded.
the gi.require_version call has already been added to cosmic and
disco.
[test case]
see http://autopkgtest.ubuntu.com/packages/network-manager bionic test
results.
[other info]
this only fails intermittently, but the failure is clearly not an
actual problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1825946/+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 1838154] Re: Something hinders XFCE performance. >:]
** Package changed: xorg (Ubuntu) => null-and-void ** Changed in: null-and-void Status: New => Incomplete ** Changed in: xorg-server Status: New => Incomplete ** Changed in: xfdesktop Status: New => Incomplete ** Changed in: xfwm4 Status: New => Incomplete ** Changed in: wayland Status: New => Incomplete ** Changed in: xfwm4 (Fedora) Importance: Unknown => Undecided ** Changed in: xfwm4 (Fedora) Status: Unknown => New ** Changed in: xfwm4 (Fedora) Remote watch: Red Hat Bugzilla #1674486 => None ** Changed in: xfwm4 (Fedora) Status: New => Incomplete ** Changed in: null-and-void Status: Incomplete => Invalid ** Changed in: xorg-server Status: Incomplete => Invalid ** Changed in: xfdesktop Status: Incomplete => Invalid ** Changed in: xfwm4 (Fedora) Status: Incomplete => Invalid ** Changed in: xfwm4 Status: Incomplete => Invalid ** Changed in: wayland Status: Incomplete => Invalid -- 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/1838154 Title: Something hinders XFCE performance. >:] Status in NULL Project: Invalid Status in wayland: Invalid Status in Xfce4 Desktop: Invalid Status in Xfwm4: Invalid Status in X.Org X server: Invalid Status in xfwm4 package in Fedora: Invalid Bug description: The following settings get rid of some kind of flickering or slow-down during typing and so on. 1. Snapping settings: 1 (top) 1 (bottom) 0 (left) 2 (right) 2. Send message trick lowers temperature. :-) 3. Avoid alt-tabbing. >:] 4. Rename Templates to "# Templates". __ Additional info: two spaces bug - https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716 https://bugzilla.redhat.com/show_bug.cgi?id=1754300#c2 Templates bug - https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462 https://bugzilla.redhat.com/show_bug.cgi?id=1729666 :-) To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1838154/+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 1854682] Re: Add option to "Privacy" in Ubuntu Settings that would enable/disable software installation outside trusted app stores.
Thank you for your suggestion. However, the changes you are requesting aren't really a bug and require more discussion, which should be done on an appropriate mailing list or forum. http://www.ubuntu.com/support/community/mailinglists might be a good start for determining which mailing list to use. ** Changed in: ubuntu-settings (Ubuntu) Importance: Undecided => Wishlist ** Changed in: ubuntu-settings (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1854682 Title: Add option to "Privacy" in Ubuntu Settings that would enable/disable software installation outside trusted app stores. Status in ubuntu-settings package in Ubuntu: Opinion Bug description: 1) Ubuntu 19.10 2) Gnome Settings 1:3.34.1-1ubuntu2 3) Ability to block installation of untrusted software not in trusted app stores(Ubuntu Software Center, Steam, etc). 4) Unable to block installation of untrusted software not in trusted app stores. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1854682/+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 1854733] Re: Canon LPB 6030
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => cups (Ubuntu) ** Changed in: cups (Ubuntu) Importance: Undecided => Low ** Changed in: cups (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1854733 Title: Canon LPB 6030 Status in cups package in Ubuntu: Incomplete Bug description: printter driwer das not work. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-70.79~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Dec 2 14:09:33 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: 2019-12-02 10:56:18 startup archives install 2019-12-02 10:57:25 startup archives install ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:172a] InstallationDate: Installed on 2019-01-21 (315 days ago) InstallationMedia: Ubuntu-GNOME 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, no user) LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=d23c244f-cbd5-450e-a02a-2772583abebf ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.11 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.31 dmi.chassis.asset.tag: CZC10542JV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.11:bd11/25/2010:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.31:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1854733/+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 1852773] Re: test failures on focal due to missing build-depends on gpg and gpg-agent
** Changed in: software-properties (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1852773
Title:
test failures on focal due to missing build-depends on gpg and gpg-
agent
Status in software-properties package in Ubuntu:
Fix Committed
Bug description:
==
ERROR: test_add_ppa_signing_key_multiple_fingerprints
(tests.test_lp.AddPPASigningKeyTestCase)
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
return func(*args, **keywargs)
File "/build/software-properties-0.98.6/tests/test_lp.py", line 148, in
test_add_ppa_signing_key_multiple_fingerprints
res = self.t.add_ppa_signing_key("~mvo/ubuntu/ppa")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
317, in add_ppa_signing_key
minimal_key = self._minimize_key(armored_key)
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
259, in _minimize_key
p = self.gpg_cmd("import-minimal,import-export")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
242, in gpg_cmd
return subprocess.Popen(cmd.split(), stdin=subprocess.PIPE,
stdout=subprocess.PIPE)
File "/usr/lib/python3.8/subprocess.py", line 854, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'gpg'
==
ERROR: test_add_ppa_signing_key_ok (tests.test_lp.AddPPASigningKeyTestCase)
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
return func(*args, **keywargs)
File "/build/software-properties-0.98.6/tests/test_lp.py", line 158, in
test_add_ppa_signing_key_ok
res = self.t.add_ppa_signing_key("~mvo/ubuntu/ppa")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
317, in add_ppa_signing_key
minimal_key = self._minimize_key(armored_key)
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
259, in _minimize_key
p = self.gpg_cmd("import-minimal,import-export")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
242, in gpg_cmd
return subprocess.Popen(cmd.split(), stdin=subprocess.PIPE,
stdout=subprocess.PIPE)
File "/usr/lib/python3.8/subprocess.py", line 854, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'gpg'
==
ERROR: test_add_ppa_signing_key_wrong_fingerprint
(tests.test_lp.AddPPASigningKeyTestCase)
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
return func(*args, **keywargs)
File "/build/software-properties-0.98.6/tests/test_lp.py", line 140, in
test_add_ppa_signing_key_wrong_fingerprint
res = self.t.add_ppa_signing_key("~mvo/ubuntu/ppa")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
317, in add_ppa_signing_key
minimal_key = self._minimize_key(armored_key)
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
259, in _minimize_key
p = self.gpg_cmd("import-minimal,import-export")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
242, in gpg_cmd
return subprocess.Popen(cmd.split(), stdin=subprocess.PIPE,
stdout=subprocess.PIPE)
File "/usr/lib/python3.8/subprocess.py", line 854, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'gpg'
==
FAIL: test_add_gpg_key (tests.test_dbus.TestDBus)
--
Traceback (most recent call last):
File "/build/software-properties-0.98.6/tests/test_dbus.py", line 372, in
test_add_gpg_key
[Touch-packages] [Bug 1854737] Re: games dont start
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (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/1854737 Title: games dont start Status in xorg package in Ubuntu: Incomplete Bug description: games dont start on my intel graphics ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 2 14:45:32 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Core Processor Integrated Graphics Controller [10cf:150a] InstallationDate: Installed on 2019-12-02 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: FUJITSU LIFEBOOK AH530 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=81837462-24c5-4880-b5bc-ed8f2196cdfe ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/03/2019 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.22 dmi.board.name: FJNBB06 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.22:bd04/03/2019:svnFUJITSU:pnLIFEBOOKAH530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK AH530 dmi.sys.vendor: FUJITSU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1854737/+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 1852489] Re: [SRU] Enable support for Ussuri Cloud Archive
Fixed in focal via https://launchpad.net/ubuntu/+source/software- properties/0.98.6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1852489 Title: [SRU] Enable support for Ussuri Cloud Archive Status in software-properties package in Ubuntu: Triaged Status in software-properties source package in Bionic: Triaged Status in software-properties source package in Focal: Triaged Bug description: Please add support for: cloud-archive:ussuri cloud-archive:ussuri-proposed This will also need to be SRU'd back to bionic. [Impact] End users have to manually enable the ussuri cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:ussuri sudo add-apt-repository cloud-archive:ussuri-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1852489/+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 1852773] Re: test failures on focal due to missing build-depends on gpg and gpg-agent
Fixed in focal via https://launchpad.net/ubuntu/+source/software-
properties/0.98.6
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1852773
Title:
test failures on focal due to missing build-depends on gpg and gpg-
agent
Status in software-properties package in Ubuntu:
Fix Committed
Bug description:
==
ERROR: test_add_ppa_signing_key_multiple_fingerprints
(tests.test_lp.AddPPASigningKeyTestCase)
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
return func(*args, **keywargs)
File "/build/software-properties-0.98.6/tests/test_lp.py", line 148, in
test_add_ppa_signing_key_multiple_fingerprints
res = self.t.add_ppa_signing_key("~mvo/ubuntu/ppa")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
317, in add_ppa_signing_key
minimal_key = self._minimize_key(armored_key)
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
259, in _minimize_key
p = self.gpg_cmd("import-minimal,import-export")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
242, in gpg_cmd
return subprocess.Popen(cmd.split(), stdin=subprocess.PIPE,
stdout=subprocess.PIPE)
File "/usr/lib/python3.8/subprocess.py", line 854, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'gpg'
==
ERROR: test_add_ppa_signing_key_ok (tests.test_lp.AddPPASigningKeyTestCase)
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
return func(*args, **keywargs)
File "/build/software-properties-0.98.6/tests/test_lp.py", line 158, in
test_add_ppa_signing_key_ok
res = self.t.add_ppa_signing_key("~mvo/ubuntu/ppa")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
317, in add_ppa_signing_key
minimal_key = self._minimize_key(armored_key)
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
259, in _minimize_key
p = self.gpg_cmd("import-minimal,import-export")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
242, in gpg_cmd
return subprocess.Popen(cmd.split(), stdin=subprocess.PIPE,
stdout=subprocess.PIPE)
File "/usr/lib/python3.8/subprocess.py", line 854, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'gpg'
==
ERROR: test_add_ppa_signing_key_wrong_fingerprint
(tests.test_lp.AddPPASigningKeyTestCase)
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
return func(*args, **keywargs)
File "/build/software-properties-0.98.6/tests/test_lp.py", line 140, in
test_add_ppa_signing_key_wrong_fingerprint
res = self.t.add_ppa_signing_key("~mvo/ubuntu/ppa")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
317, in add_ppa_signing_key
minimal_key = self._minimize_key(armored_key)
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
259, in _minimize_key
p = self.gpg_cmd("import-minimal,import-export")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
242, in gpg_cmd
return subprocess.Popen(cmd.split(), stdin=subprocess.PIPE,
stdout=subprocess.PIPE)
File "/usr/lib/python3.8/subprocess.py", line 854, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'gpg'
==
FAIL: test_add_gpg_key (tests.test_dbus.TestDBus)
--
Traceback (most recent call last):
File "/build/software-properties-0.98.6/tests/test_dbus.py", line 372, in
test_add_gpg_key
[Touch-packages] [Bug 1852772] Re: test_updates_interval fails on focal
Thanks Mathieu. Fixed in focal via https://launchpad.net/ubuntu/+source
/software-properties/0.98.6
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1852772
Title:
test_updates_interval fails on focal
Status in software-properties package in Ubuntu:
Triaged
Bug description:
==
FAIL: test_updates_interval (tests.test_dbus.TestDBus)
--
Traceback (most recent call last):
File "/build/software-properties-0.98.6/tests/test_dbus.py", line 332, in
test_updates_interval
self.assertTrue('APT::Periodic::Update-Package-Lists "1";' in config)
AssertionError: False is not true
Looking closer, while in the SetUpdateInterval() method in
softwareproperties/dbus/SoftwarePropertiesDBus.py, days is of
dbus.Int32 type. A simple print output shows:
days=dbus.Int32(1)
D-Bus is statically typed, unlike python. More details at:
https://dbus.freedesktop.org/doc/dbus-python/tutorial.html#data-types
I think once we're in the dbus method (SetUpdateInterval() method in
softwareproperties/dbus/SoftwarePropertiesDBus.py) we can convert the
dbus.Int32 to an int.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1852772/+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 1854772] Re: /var/lib/dpkg/status has faulty entries
** Attachment added: "faulty /var/lib/dpkg/status"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1854772/+attachment/5309330/+files/status
--
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/1854772
Title:
/var/lib/dpkg/status has faulty entries
Status in apt package in Ubuntu:
New
Bug description:
Es wurden 1.109 kB in 0 s geholt (3.865 kB/s).
Traceback (most recent call last):
File "/usr/share/apt-listchanges/DebianFiles.py", line 117, in readfile
self.stanzas += [ControlStanza(x) for x in f.read().split('\n\n') if x]
File "/usr/share/apt-listchanges/DebianFiles.py", line 117, in
self.stanzas += [ControlStanza(x) for x in f.read().split('\n\n') if x]
File "/usr/share/apt-listchanges/DebianFiles.py", line 70, in __init__
field, value = line.split(':', 1)
ValueError: not enough values to unpack (expected 2, got 1)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/bin/apt-listchanges", line 280, in
main(config)
File "/usr/bin/apt-listchanges", line 83, in main
status.readfile('/var/lib/dpkg/status')
File "/usr/share/apt-listchanges/DebianFiles.py", line 120, in readfile
{'what': file, 'errmsg': str(ex)}) from ex
RuntimeError: Fehler beim Verarbeiten von »/var/lib/dpkg/status«: not enough
values to unpack (expected 2, got 1)
(Lese Datenbank ... 376829 Dateien und Verzeichnisse sind derzeit
installiert.)
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: apt 1.9.4
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Dec 2 16:00:56 2019
InstallationDate: Installed on 2019-09-09 (83 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1854772/+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 1854772] [NEW] /var/lib/dpkg/status has faulty entries
Public bug reported:
Es wurden 1.109 kB in 0 s geholt (3.865 kB/s).
Traceback (most recent call last):
File "/usr/share/apt-listchanges/DebianFiles.py", line 117, in readfile
self.stanzas += [ControlStanza(x) for x in f.read().split('\n\n') if x]
File "/usr/share/apt-listchanges/DebianFiles.py", line 117, in
self.stanzas += [ControlStanza(x) for x in f.read().split('\n\n') if x]
File "/usr/share/apt-listchanges/DebianFiles.py", line 70, in __init__
field, value = line.split(':', 1)
ValueError: not enough values to unpack (expected 2, got 1)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/bin/apt-listchanges", line 280, in
main(config)
File "/usr/bin/apt-listchanges", line 83, in main
status.readfile('/var/lib/dpkg/status')
File "/usr/share/apt-listchanges/DebianFiles.py", line 120, in readfile
{'what': file, 'errmsg': str(ex)}) from ex
RuntimeError: Fehler beim Verarbeiten von »/var/lib/dpkg/status«: not enough
values to unpack (expected 2, got 1)
(Lese Datenbank ... 376829 Dateien und Verzeichnisse sind derzeit installiert.)
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: apt 1.9.4
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Dec 2 16:00:56 2019
InstallationDate: Installed on 2019-09-09 (83 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug eoan
--
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/1854772
Title:
/var/lib/dpkg/status has faulty entries
Status in apt package in Ubuntu:
New
Bug description:
Es wurden 1.109 kB in 0 s geholt (3.865 kB/s).
Traceback (most recent call last):
File "/usr/share/apt-listchanges/DebianFiles.py", line 117, in readfile
self.stanzas += [ControlStanza(x) for x in f.read().split('\n\n') if x]
File "/usr/share/apt-listchanges/DebianFiles.py", line 117, in
self.stanzas += [ControlStanza(x) for x in f.read().split('\n\n') if x]
File "/usr/share/apt-listchanges/DebianFiles.py", line 70, in __init__
field, value = line.split(':', 1)
ValueError: not enough values to unpack (expected 2, got 1)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/bin/apt-listchanges", line 280, in
main(config)
File "/usr/bin/apt-listchanges", line 83, in main
status.readfile('/var/lib/dpkg/status')
File "/usr/share/apt-listchanges/DebianFiles.py", line 120, in readfile
{'what': file, 'errmsg': str(ex)}) from ex
RuntimeError: Fehler beim Verarbeiten von »/var/lib/dpkg/status«: not enough
values to unpack (expected 2, got 1)
(Lese Datenbank ... 376829 Dateien und Verzeichnisse sind derzeit
installiert.)
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: apt 1.9.4
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Dec 2 16:00:56 2019
InstallationDate: Installed on 2019-09-09 (83 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1854772/+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 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
What this triggers in the logs: gnome-shell: > polkitAuthenticationAgent: Received 2 identities that can be used for > authentication. Only considering one. > pushModal: invocation of begin_modal failed > polkitAuthenticationAgent: Failed to show modal dialog. Dismissing > authentication request for action-id > com.ubuntu.softwareproperties.applychanges cookie > 7-b2a6e60b05bc38c7fd20137335c2abcb-34-cd8e89ea6620c9969383c39013bf86c1 polkitd: > Operator of unix-session:2 FAILED to authenticate to gain authorization for > action com.ubuntu.softwareproperties.applychanges for > system-bus-name::1.26625 [/usr/bin/python3 /usr/bin/software-properties-gtk] > (owned by unix-user:fabio) gnome-shell: > ERROR:root:Authentication canceled, changes have not been saved -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: Confirmed Status in software-properties source package in Bionic: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties 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/1727908/+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 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Video of the bug ** Attachment added: "Screencast from 02-12-19 16:00:10.webm" https://bugs.launchpad.net/ubuntu/bionic/+source/gnome-shell/+bug/1727908/+attachment/5309266/+files/Screencast%20from%2002-12-19%2016%3A00%3A10.webm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: Confirmed Status in software-properties source package in Bionic: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties 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/1727908/+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 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Just tested on focal. I didn't have the repo, so I added it: ``` deb http://archive.canonical.com/ubuntu focal partner ``` It correctly asked me the password and after that it was added. I deselected it to verify this bug. Then I closed the software-properties-gtk window. To then verify the bug, I opened again software-properties-gtk (from Dash), moved to Other Software and clicked on the Canonical Partners repo. On click nothing appeared (we would be expecting a password prompt) but the window got unselected, like if I had moved to some other window. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: Confirmed Status in software-properties source package in Bionic: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties 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/1727908/+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 1854737] [NEW] games dont start
Public bug reported: games dont start on my intel graphics ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 2 14:45:32 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Core Processor Integrated Graphics Controller [10cf:150a] InstallationDate: Installed on 2019-12-02 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: FUJITSU LIFEBOOK AH530 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=81837462-24c5-4880-b5bc-ed8f2196cdfe ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/03/2019 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.22 dmi.board.name: FJNBB06 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.22:bd04/03/2019:svnFUJITSU:pnLIFEBOOKAH530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK AH530 dmi.sys.vendor: FUJITSU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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 eoan 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/1854737 Title: games dont start Status in xorg package in Ubuntu: New Bug description: games dont start on my intel graphics ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 2 14:45:32 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Core Processor Integrated Graphics Controller [10cf:150a] InstallationDate: Installed on 2019-12-02 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: FUJITSU LIFEBOOK AH530 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=81837462-24c5-4880-b5bc-ed8f2196cdfe ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/03/2019 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.22 dmi.board.name: FJNBB06 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.22:bd04/03/2019:svnFUJITSU:pnLIFEBOOKAH530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK AH530 dmi.sys.vendor: FUJITSU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Touch-packages] [Bug 1846787] Re: systemd-logind leaves leftover sessions and scope files
Summary of autopkg regressions
systemd:
- most tests passed on retest (thanks ddstreet)
- still failing: gvfs/s390x, docker.io/all archs but armhf, nplan/amd64
dbus:
- no new failures.
Looking at the pending failures/regressions.
systemd
--
umockdev/0.8.11-2 (i386)
passed on retest.
apt/1.2.32 (ppc64el)
passed on retest.
unity8/8.12+16.04.20160401-0ubuntu1 (i386)
passed on retest.
udisks2/2.1.7-1ubuntu1 (amd64)
passed on retest.
gvfs/1.28.2-1ubuntu1~16.04.3 (s390x)
still failing.
systemd/229-4ubuntu21.23 (i386)
passed on retest.
docker.io/18.09.7-0ubuntu1~16.04.5 (i386, arm64, s390x, ppc64el, amd64)
still failing.
nplan/0.32~16.04.7 (amd64)
still failing.
dbus
--
libnih/blacklisted (armhf)
package not relevant?
libreoffice/1:5.1.6~rc2-0ubuntu1~xenial10 (i386)
fails since 2017-07-06.
--
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/1846787
Title:
systemd-logind leaves leftover sessions and scope files
Status in dbus package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in dbus source package in Xenial:
Fix Committed
Status in systemd source package in Xenial:
Fix Committed
Bug description:
[Impact]
Scope file leakage can cause SSH delays and reduce performance in systemd
[Description]
The current systemd-logind version present in Xenial can leave abandoned SSH
sessions and scope files in cases where the host sees a lot of concurrent SSH
connections. These leftover sessions can slow down systemd performance
greatly, and can have an impact on sshd handling a great number of concurrent
connections.
To fix this issue, patches are needed in both dbus and systemd. These improve
the
performance of the communication between dbus and systemd, so that they can
handle a better volume of events (e.g. SSH logins). All of those patches are
already present from Bionic onwards, so we only need those fixes for Xenial.
== Systemd ==
Upstream patches:
- core: use an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification
(d8fdc62037b5)
$ git describe --contains d8fdc62037b5
v230~71^2~2
$ rmadison systemd
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.22 | xenial-updates | source, ... <
systemd | 237-3ubuntu10| bionic | source, ...
systemd | 237-3ubuntu10.29 | bionic-security | source, ...
systemd | 237-3ubuntu10.29 | bionic-updates | source, ...
systemd | 237-3ubuntu10.31 | bionic-proposed | source, ...
== DBus ==
Upstream patches:
- Only read one message at a time if there are fds pending (892f084eeda0)
- bus: Fix timeout restarts (529600397bca)
- DBusMainLoop: ensure all required timeouts are restarted (446b0d9ac75a)
$ git describe --contains 892f084eeda0 529600397bca 446b0d9ac75a
dbus-1.11.10~44
dbus-1.11.10~45
dbus-1.11.16~2
$ rmadison dbus
dbus | 1.10.6-1ubuntu3| xenial | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-security | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-updates | source, ... <
dbus | 1.12.2-1ubuntu1| bionic | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-security | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-updates | source, ...
[Test Case]
1) Simulate a lot of concurrent SSH connections with e.g. a for loop:
multipass@xenial-logind:~$ for i in {1..1000}; do sleep 0.1; ssh localhost
sleep 1 & done
2) Check for leaked sessions in /run/systemd/system/:
multipass@xenial-logind:~$ ls -ld /run/systemd/system/session-*.scope*
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-103.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-104.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-105.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-106.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-110.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-111.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-112.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-113.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-114.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-115.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-116.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-117.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-118.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-119.scope.d
drwxr-xr-x 2 root root 160 Oct 4
[Touch-packages] [Bug 1854733] [NEW] Canon LPB 6030
Public bug reported: printter driwer das not work. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-70.79~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Dec 2 14:09:33 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: 2019-12-02 10:56:18 startup archives install 2019-12-02 10:57:25 startup archives install ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:172a] InstallationDate: Installed on 2019-01-21 (315 days ago) InstallationMedia: Ubuntu-GNOME 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, no user) LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=d23c244f-cbd5-450e-a02a-2772583abebf ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.11 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.31 dmi.chassis.asset.tag: CZC10542JV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.11:bd11/25/2010:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.31:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- 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/1854733 Title: Canon LPB 6030 Status in xorg package in Ubuntu: New Bug description: printter driwer das not work. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-70.79~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Dec 2 14:09:33 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: 2019-12-02 10:56:18 startup archives install 2019-12-02 10:57:25 startup archives install ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:172a] InstallationDate: Installed on 2019-01-21 (315 days ago) InstallationMedia: Ubuntu-GNOME 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, no user) LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=d23c244f-cbd5-450e-a02a-2772583abebf ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.11 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.31 dmi.chassis.asset.tag: CZC10542JV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.11:bd11/25/2010:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.31:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN
[Touch-packages] [Bug 21837] Re: debdelta integration / zsync support
Blocking points raised are: - We need to be able to validate that the delta is correct before using it. We could + provide delta indices like we have packages - this does require pdiff support so we don't have to download the entire index everytime, as that would make deltas pointless for small updates + sign the deltas directly - but that's too slow, signatures are slow + provide one delta index per source package - might be useful compromise - we need to uniquely identify package. I proposed we introduce a package id, based on the hash of the mtree (+ control fields maybe), but this does need mtrees first (or hashing the md5sum file) - space usage on mirrors, how to keep this in check -- 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/21837 Title: debdelta integration / zsync support Status in apt package in Ubuntu: Triaged Status in apt package in Baltix: Confirmed Bug description: Ubuntu should, like Mandrake 10.2, Firefox 1.5 and Windows, update packages using binary patches instead of by re-downloading entire packages. This would be especially helpful when running beta versions of software which change daily. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/21837/+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 21837] Re: debdelta integration / zsync support
Work on delta debs was being done in https://wiki.debian.org/Teams/Dpkg/Spec/DeltaDebs amongst other places, but it kind of stopped a bit. Deltas are getting harder and harder to justify with increasing speeds and less and less data caps, but it's certainly something I'm interested in developing. I believe my format is fairly solid. The problem with debdelta was that it was incredibly slow, to the point where using it outside of dialup (well, I did not measure it, it might be a hyperbole) would basically be pointless. ** Changed in: apt (Ubuntu) Status: Confirmed => Triaged ** No longer affects: apt -- 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/21837 Title: debdelta integration / zsync support Status in apt package in Ubuntu: Triaged Status in apt package in Baltix: Confirmed Bug description: Ubuntu should, like Mandrake 10.2, Firefox 1.5 and Windows, update packages using binary patches instead of by re-downloading entire packages. This would be especially helpful when running beta versions of software which change daily. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/21837/+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 21837] Re: debdelta integration / zsync support
Oh, also building the deltas (which is fairly expensive), and which deltas to build are important points to consider. -- 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/21837 Title: debdelta integration / zsync support Status in apt package in Ubuntu: Triaged Status in apt package in Baltix: Confirmed Bug description: Ubuntu should, like Mandrake 10.2, Firefox 1.5 and Windows, update packages using binary patches instead of by re-downloading entire packages. This would be especially helpful when running beta versions of software which change daily. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/21837/+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 1850667] Re: cgroup v2 is not fully supported yet, proceeding with partial confinement
When Ubuntu Eoan is started with systemd.unified_cgroup_hierarchy, lxc- start (version 3.0.4 packaged by Eoan) cannot be used in its default setting. It is a combination of unsuitable default configuration and an upstream bug in LXC 3.0.4. For detail, please refer to https://github.com/lxc/lxc/issues/3183 ** Project changed: lxc => lxc (Ubuntu) ** Changed in: lxc (Ubuntu) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: cgroup v2 is not fully supported yet, proceeding with partial confinement Status in docker.io package in Ubuntu: New Status in lxc package in Ubuntu: New Status in lxd package in Ubuntu: New Status in snapd package in Ubuntu: In Progress Bug description: Systemd upstream switched the default cgroup hierarchy to unified with v243. This change is reverted by the Ubuntu systemd packages, but as unified is the way to go per upstream support should be added to all relevant Ubuntu packges (and snaps): https://github.com/systemd/systemd/blob/v243/NEWS#L56 * systemd now defaults to the "unified" cgroup hierarchy setup during build-time, i.e. -Ddefault-hierarchy=unified is now the build-time default. Previously, -Ddefault-hierarchy=hybrid was the default. This change reflects the fact that cgroupsv2 support has matured substantially in both systemd and in the kernel, and is clearly the way forward. Downstream production distributions might want to continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for their builds as unfortunately the popular container managers have not caught up with the kernel API changes. Systemd is rebuilt using the new default and is available from the following PPA for testing: https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh The autopkgtest results against other packges are available here: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified-cgh/?format=plain https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal-rbalint-systemd-unified-cgh/?format=plain lxc autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz snapd autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz docker.io autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1850667/+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 1850667] [NEW] cgroup v2 is not fully supported yet, proceeding with partial confinement
You have been subscribed to a public bug: Systemd upstream switched the default cgroup hierarchy to unified with v243. This change is reverted by the Ubuntu systemd packages, but as unified is the way to go per upstream support should be added to all relevant Ubuntu packges (and snaps): https://github.com/systemd/systemd/blob/v243/NEWS#L56 * systemd now defaults to the "unified" cgroup hierarchy setup during build-time, i.e. -Ddefault-hierarchy=unified is now the build-time default. Previously, -Ddefault-hierarchy=hybrid was the default. This change reflects the fact that cgroupsv2 support has matured substantially in both systemd and in the kernel, and is clearly the way forward. Downstream production distributions might want to continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for their builds as unfortunately the popular container managers have not caught up with the kernel API changes. Systemd is rebuilt using the new default and is available from the following PPA for testing: https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh The autopkgtest results against other packges are available here: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified-cgh/?format=plain https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal-rbalint-systemd-unified-cgh/?format=plain lxc autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz snapd autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz docker.io autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz ** Affects: lxc (Ubuntu) Importance: Unknown Status: Unknown ** Affects: docker.io (Ubuntu) Importance: Undecided Status: New ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Affects: snapd (Ubuntu) Importance: Undecided Assignee: Maciej Borzecki (maciek-borzecki) Status: In Progress -- cgroup v2 is not fully supported yet, proceeding with partial confinement https://bugs.launchpad.net/bugs/1850667 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. -- 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 1785383] Re: missing EDNS0 record confuses systemd-resolved
Any news on this? Recent upgrade has removed my patches to dnsmasq, and
I'm hitting this again. Still convinced the Ubuntu-specific patch to
systemd-resolved is flawed as well.
I will try to get brain back into gear to have at look at this all
again. If nothing else, would be good to SRU the dnsmasq upstream fix?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1785383
Title:
missing EDNS0 record confuses systemd-resolved
Status in dnsmasq package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
Confirmed
Bug description:
dnsmasq 2.79 and below omits EDNS0 OPT records when returning an empty
answer for a domain it is authoritative for. systemd-resolved seems to
get confused by this in certain circumstances; when using the stub
resolver and requesting an address for which there are no
records, there can sometimes be a five second hang in resolution.
This is fixed by upstream commit
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78
Not sure if it is worth cherry picking? I imagine the most likely
trigger will be dnsmasq on routers which are not likely to be running
Ubuntu, but maybe just in case.
I also think there are some logic issues in systemd-resolved, upstream
bug filed:
https://github.com/systemd/systemd/issues/9785
Simple-ish test case:
---
IFACE=dummy0
SUBNET=10.0.0
ip link add $IFACE type dummy
ifconfig $IFACE ${SUBNET}.1/24
dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo
--host-record=test.test,${SUBNET}.1 &
dig -t a test.test @10.0.0.1 | grep EDNS
# should return "; EDNS ..."
dig -t test.test @10.0.0.1 | grep EDNS
# again, should return "; EDNS ..." but doesn't
---
To reproduce the systemd-resolved side of the problem
---
# as above, but
# now configure systemd-resolved to look at only 10.0.0.1, then
systemd-resolve --reset-server-features
# should exhibit five second delay then connect, assuming sshd is running :)
ssh test.test
---
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dnsmasq-base 2.79-1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sat Aug 4 11:33:56 2018
InstallationDate: Installed on 2018-05-31 (64 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: dnsmasq
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1785383/+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 1853120] Re: Xorg crashes with a bus error in OsLookupColor when using a second display
** Changed in: xorg (Ubuntu)
Status: Incomplete => New
--
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/1853120
Title:
Xorg crashes with a bus error in OsLookupColor when using a second
display
Status in xorg package in Ubuntu:
New
Bug description:
I'm using a Dell XPS 9380 ("developer edition") connected to an
external monitor via USB C.
I've been running Ubuntu 19.04 for months with an external monitor
with no issues. On upgrading to 19.10 xorg crashes with a bus error
within a few seconds or minutes of using the external monitor.
The xorg package installed is 1:7.7+19ubuntu12
The system is stable without the external monitor.
The crash is consistently repeatable and the stack trace looks very
similar each time.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Nov 19 09:50:40 2019
DistUpgraded: 2019-11-17 14:04:28,024 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: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00
[VGA controller])
Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
InstallationDate: Installed on 2019-07-09 (132 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
MachineType: Dell Inc. XPS 13 9380
ProcEnviron:
LANGUAGE=en_IE:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_IE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic
root=UUID=6b08154b-c421-45b7-bc75-c4feccc18654 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to eoan on 2019-11-17 (1 days ago)
dmi.bios.date: 10/01/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.0
dmi.board.name: 088MRW
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.8.0:bd10/01/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn088MRW:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9380
dmi.product.sku: 08AF
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1853120/+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 1832414] Re: Removing document files spam from cups
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1832414 Title: Removing document files spam from cups Status in cups package in Ubuntu: Confirmed Bug description: Since my server (running xenial) updated to cups 2.1.3-4ubuntu0.9 last night the CUPS logs have had a considerable number of messages from cupsd stating "Removing document files" - about 3 or 4 a second constantly. Stopping the cups service stops the log-spam, and starting it again immediately resumes it (after a few hundred "Loading from cache..." messages). I've tried removing document files from the cache (there were a couple of ancient ones lying around - it's not a heavily used printer), but this made little difference to the symptoms. I'm pretty confident this is due to the upgrade as: 1. the spam in the logs starts immediately after CUPS reloads (after the upgrade) 2. looking at the diff for 2.1.3-4ubuntu0.9 it does seem to be fiddling with things related to job clean-up (e.g. cupsdUpdateJobs and cupsdCleanJobs in scheduler/job.c) If I can provide any further information, do let me know! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1832414/+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 1845046] Re: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected
This is likely a bluez bug, not a pulseaudio one, since it only affects some headsets. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1845046 Title: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected Status in bluez package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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
