[Touch-packages] [Bug 1861177] Autopkgtest regression report (libseccomp/2.4.3-1ubuntu3.18.04.3)

2020-07-13 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted libseccomp (2.4.3-1ubuntu3.18.04.3) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

lxc/3.0.3-0ubuntu1~18.04.1 (arm64)
systemd/unknown (armhf)
systemd/237-3ubuntu10.41 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#libseccomp

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1861177

Title:
  seccomp_rule_add is very slow

Status in snapd:
  Invalid
Status in libseccomp package in Ubuntu:
  In Progress
Status in libseccomp source package in Xenial:
  Fix Committed
Status in libseccomp source package in Bionic:
  Fix Committed
Status in libseccomp source package in Eoan:
  Fix Committed
Status in libseccomp source package in Focal:
  Fix Committed
Status in libseccomp source package in Groovy:
  In Progress

Bug description:
  [IMPACT]
  There is a known and patched issue with version 2.4 of libseccomp where 
certain operations have a large performance regression. This is causing some 
packages that use libseccomp such as container orchestration systems to 
occasionally time out or otherwise fail under certain workloads.

  Please consider porting the patch into the various Ubuntu versions
  that have version 2.4 of libseccomp and into the backports. The
  performance patch from version 2.5 (yet to be released) applies
  cleanly on top of the 2.4 branch of libseccomp.

  For more information, and for a copy of the patch (which can also be
  cherry picked from the upstream libseccomp repos) see the similar
  Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913

  Upstream issue : https://github.com/seccomp/libseccomp/issues/153
  Upstream fix : https://github.com/seccomp/libseccomp/pull/180/

  [Test Case]

  For this test case we use Docker on Ubuntu Groovy (20.10) :

  --> Current libseccomp version
  #dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu3 
 amd64high level interface to Linux seccomp filter

  ## pull ubuntu image
  # docker pull ubuntu
  ## create a container
  # docker run --name test_seccomp -it 74435f89ab78 /bin/bash

  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m10,319s
  user  0m0,018s
  sys   0m0,033s

  
  --> Patched libseccomp version

  # dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu4 
 amd64high level interface to Linux seccomp filter

  # docker start test_seccomp
  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m3,650s
  user  0m0,025s
  sys   0m0,028s

  [Regression Potential]

  The first of the 2 patches cleans up the code that adds rules to a
  single filter without changing the logic of the code. The second patch
  introduces the idea of shadow transactions. On a successful
  transaction commit the old transaction checkpoint is preserved and is
  brought up to date with the current filter. The next time a new
  transaction starts, it checks is the a shadow transaction exist and if
  so the shadow is used instead of creating a new checkpoint from
  scratch [1]. This is the patch that mitigates the performance
  regression. Any potential regression will involve the parts of the
  code that add rules to filters and/or the code that creates and checks
  the shadow transactions.

  
  [Other]

  Affected releases : Groovy, Focal, Eoan, Bionic, Xenial.

  [1]
  
https://github.com/seccomp/libseccomp/pull/180/commits/bc3a6c0453b0350ee43e4925482f705a2fbf5a4d

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1861177/+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 1878482] Re: EPSON WF 3520 driver problem - PpdFiles: Error

2020-07-13 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1878482

Title:
  EPSON WF 3520 driver problem - PpdFiles: Error

Status in cups package in Ubuntu:
  Expired

Bug description:
  doesn't work

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 13 23:17:35 2020
  InstallationDate: Installed on 2020-05-06 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for Generic-ESC-P-Dot-Matrix: lpd://192.168.1.133:515/PASSTHRU
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b413 Chicony Electronics Co., Ltd FJ Camera
   Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless 
Keyboard/Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK A555
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Generic-ESC-P-Dot-Matrix.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Generic-ESC-P-Dot-Matrix.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=85a6cbd6-a8d0-4ee5-ac82-9f54acbb0106 ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2016
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: 1.21
  dmi.board.name: FJNBB3E
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.21:bd05/31/2016:svnFUJITSU:pnLIFEBOOKA555:pvr:rvnFUJITSU:rnFJNBB3E:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK A555
  dmi.sys.vendor: FUJITSU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1878482/+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 1887016] Re: Openssh default config has two PasswordAuthentication params

2020-07-13 Thread Rulon Oboev
What image are you using?

I've got the same problem with 20.04-live-server-amd64.iso
(https://releases.ubuntu.com/20.04/ubuntu-20.04-live-server-amd64.iso)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1887016

Title:
  Openssh default config has two PasswordAuthentication params

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu server 20.04 the /etc/ssh/sshd_config file has an additional
  `PasswordAuthentication yes` string in the end.

  It can lead to security problems, because there's already one string
  `# PasswordAuthentication yes` in the beginning of the file. It is
  supposed to be uncommented if it's needed to change the default value.

  But if the user uncomments this string and set in to "no", it will be
  overriden by the last line of config.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1887016/+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 1877023] Re: Unhandled exception in check_ignored()

2020-07-13 Thread Seth Arnold
Hello, please use CVE-2020-15701 for this issue. Thanks

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-15701

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1877023

Title:
  Unhandled exception in check_ignored()

Status in Apport:
  New
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have found a security issue on apport 2.20.11 and earlier.

  ## Vulnerability 
  apport 2.20.11 and earlier have an unhandled exception vulnerability during 
parsing apport-ignore.xml.
  An attacker can cause a denial of service (i.e., application crash) via a 
crafted apport-ignore.xml file.

  ## Description
  Reports can be suppressed by blacklisting in apport-ignore.xml.

  This is an example of apport-ignore.xml

  
  
    
    
    
  

  Unfortunately, it may cause an unhandled exception when 'mtime'
  attribute is specified as a string value, not a number like this.

  
  
    
  

  It may disrupt apport service and allow an attacker to potentially
  enable a denial of service via local access.

  The flaw lies in improper exception handling of 'mtime' attribute in
  apport-ignore.xml (see
  
https://git.launchpad.net/ubuntu/+source/apport/tree/apport/report.py?h=applied/ubuntu/devel#n1104).

  ## Log
  Here is /var/log/apport.log when the above exception occurs.

  ERROR: apport (pid 25904) Tue May  5 18:38:21 2020: Unhandled exception:
  Traceback (most recent call last):
    File "/usr/share/apport/apport", line 629, in 
  if info.check_ignored():
    File "/usr/lib/python3/dist-packages/apport/report.py", line 1082, in 
check_ignored
  if float(ignore.getAttribute('mtime')) >= cur_mtime:
  ValueError: could not convert string to float: 'string'

  Sincerely,

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1877023/+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 1887404] Re: the information was send by the system

2020-07-13 Thread Daniel van Vugt
Please explain what kind of problem you are having.

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: 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/1887404

Title:
  the information was send by the system

Status in Ubuntu:
  Incomplete

Bug description:
  the information was send by the system

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18
  Uname: Linux 4.15.0-109-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Jul 13 12:42:26 2020
  DistUpgraded: 2019-01-28 11:28:31,005 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:0782]
 Subsystem: Dell GM108M [GeForce 940MX] [1028:0782]
  InstallationDate: Installed on 2018-05-07 (798 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 7560
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-109-generic 
root=UUID=21d7010c-b6c8-41b7-a8fc-3e0dfe929d16 ro nopat vesafb.invalid=1 
drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-01-28 (532 days ago)
  dmi.bios.date: 07/19/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.6
  dmi.board.name: 09WC1G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.6:bd07/19/2017:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn09WC1G:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7560
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Jan 28 09:06:38 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1716 
   vendor BOE
  xserver.version: 2:1.18.4-0ubuntu0.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1887404/+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 1887356] Re: System crashes while loading an application in cisco webex meeting

2020-07-13 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: 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/1887356

Title:
  System crashes while loading an application in cisco webex meeting

Status in Ubuntu:
  Incomplete

Bug description:
  The above error was also encountered in Linux Mint Tessa. The Xubuntu
  is doing better as the whole system doesn't freeze and only the
  fozilla freezes.No other slow down or crashes was observed unless
  opening games on steam and this error in cisco webex.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Jul 13 13:50:14 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] 
[1025:1085]
  InstallationDate: Installed on 2020-07-11 (2 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Acer Aspire ES1-572
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=84c7b499-378e-469f-8216-9024afe9b1fc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: T-Rex_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd04/12/2016:svnAcer:pnAspireES1-572:pvrV1.09:rvnAcer:rnT-Rex_SK:rvrV1.09:cvnAcer:ct10:cvrV1.09:
  dmi.product.family: SKL
  dmi.product.name: Aspire ES1-572
  dmi.product.sku: Aspire ES1-572_1085_V1.09
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1887356/+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 1868520] Re: Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 808665665

2020-07-13 Thread Daniel van Vugt
Note that bionic was never affected by this bug. Although it did lack
the code change that fixed it :)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1868520

Title:
  Wayland apps fail to run with zwp_linux_dmabuf error (failed to import
  supplied dmabufs: Unsupported buffer format 808669784
  [DRM_FORMAT_XRGB2101010]) (or 808665665 [DRM_FORMAT_ABGR2101010])

Status in Mesa:
  Fix Released
Status in MPV:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in mesa source package in Focal:
  Fix Released

Bug description:
  [Impact]

  Wayland apps fail to start in focal with:

  error 7: failed to import supplied dmabufs: Unsupported buffer format
  808669784

  [Test Case]

  Just run: es2gears_wayland

  [Regression Potential]

  Medium/unknown. The fix is quite new.

  [Other Info]

  When attempting to run es2gears_wayland against GNOME Shell, it fails
  with:

  EGL_VERSION = 1.5
  vertex shader info:
  fragment shader info:
  info:
  [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported 
buffer format 808669784

  The full wayland protocol trace is:

  [3104432.914]  -> wl_display@1.get_registry(new id wl_registry@2)
  [3104432.972]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3104433.139] wl_display@1.delete_id(3)
  [3104433.175] wl_registry@2.global(1, "wl_drm", 2)
  [3104433.207] wl_registry@2.global(2, "wl_compositor", 4)
  [3104433.240]  -> wl_regis...@2.bind(2, "wl_compositor", 1, new id 
[unknown]@4)
  [3104433.285] wl_registry@2.global(3, "wl_shm", 1)
  [3104433.316] wl_registry@2.global(4, "wl_output", 2)
  [3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3)
  [3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3)
  [3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1)
  [3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2)
  [3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1)
  [3104433.513] wl_registry@2.global(11, "wl_shell", 1)
  [3104433.542]  -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5)
  [3104433.582] wl_registry@2.global(12, "gtk_shell1", 3)
  [3104433.611] wl_registry@2.global(13, "wp_viewporter", 1)
  [3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1)
  [3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1)
  [3104433.699] wl_registry@2.global(16, "wl_seat", 5)
  [3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1)
  [3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1)
  [3104433.816] wl_registry@2.global(20, "zxdg_importer_v1", 1)
  [3104433.846] wl_registry@2.global(21, "zwp_linux_dmabuf_v1", 3)
  [3104433.875] wl_registry@2.global(22, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
  [3104433.904] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1)
  [3104433.933] wl_registry@2.global(24, "gtk_text_input_manager", 1)
  [3104433.960] wl_registry@2.global(26, "wl_eglstream_controller", 1)
  [3104433.991] wl_callb...@3.done(3421)
  [3104436.266]  -> wl_display@1.get_registry(new id wl_registry@3)
  [3104436.279]  -> wl_disp...@1.sync(new id wl_callback@6)
  [3104436.647] wl_display@1.delete_id(6)
  [3104436.672] wl_registry@3.global(1, "wl_drm", 2)
  [3104436.726]  -> wl_regis...@3.bind(1, "wl_drm", 2, new id [unknown]@7)
  [3104436.744] wl_registry@3.global(2, "wl_compositor", 4)
  [3104436.780] wl_registry@3.global(3, "wl_shm", 1)
  [3104436.790] wl_registry@3.global(4, "wl_output", 2)
  [3104436.803] wl_registry@3.global(5, "zxdg_output_manager_v1", 3)
  [3104436.833] wl_registry@3.global(6, "wl_data_device_manager", 3)
  [3104436.868] wl_registry@3.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104436.882] wl_registry@3.global(8, "wl_subcompositor", 1)
  [3104436.898] wl_registry@3.global(9, "xdg_wm_base", 2)
  [3104436.913] wl_registry@3.global(10, "zxdg_shell_v6", 1)
  [3104436.925] wl_registry@3.global(11, "wl_shell", 1)
  [3104436.937] wl_registry@3.global(12, "gtk_shell1", 3)
  [3104436.950] wl_registry@3.global(13, "wp_viewporter", 1)
  [3104436.963] wl_registry@3.global(14, "zwp_pointer_gestures_v1", 1)
  [3104436.976] wl_registry@3.global(15, "zwp_tablet_manager_v2", 1)
  [3104436.990] wl_registry@3.global(16, "wl_seat", 5)
  [3104437.001] wl_registry@3.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104437.013] wl_registry@3.global(18, "zwp_pointer_constraints_v1", 1)
  [3104437.026] wl_registry@3.global(19, "zxdg_exporter_v1", 1)
  [3104437.038] wl_registry@3.global(20, "zxdg_importer_v1", 1)
  [3104437.051] wl_registry@3.global(21, "zwp_linux_dmabuf_v1", 3)
  [3104437.066]  -> wl_regis...@3.bind(21, "zwp_linux_dmabuf_v1", 3, new id 
[unknown]@8)
  

[Touch-packages] [Bug 1887446] Re: Area of desktop behind the Launcher is filled with random noise

2020-07-13 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1855757 ***
https://bugs.launchpad.net/bugs/1855757

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1855757, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1855757
   [nvidia] Background image corrupted after standby or resume from suspend

-- 
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/1887446

Title:
  Area of desktop behind the Launcher is filled with random noise

Status in xorg package in Ubuntu:
  New

Bug description:
  The screenshot speaks for itself.

  Stuff like this used to happen occasionally up to 16.04, sually after
  resuming from suspend, but normally the areas would get redrawn
  properly sooner or later.

  But since I upgraded to 20.04 I've seen display garbage like this a
  lot more often, and this particular instance has been like this for
  hours now.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 13 18:51:51 2020
  DistUpgraded: 2020-07-12 20:55:12,554 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.108, 5.3.0-62-generic, x86_64: installed
   nvidia-340, 340.108, 5.4.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
   NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
  InstallationDate: Installed on 2013-10-11 (2466 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.family: Type1Family
  dmi.product.name: Aspire V3-571G
  dmi.product.sku: Aspire V3-_0648_V2.07
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sun Jul 12 20:59:51 2020
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.8-2ubuntu2.1

To manage notifications about this bug go to:

[Touch-packages] [Bug 1887446] Re: Area of desktop behind the Launcher is filled with random noise

2020-07-13 Thread teo1978
Actually, now that I've been able to restore the shortcut for showing
desktop (yeah, I could have minimized all the windows manually one by
one), I realize that MY ENTIRE FUCKING DESKTOP is filled with noise.


I attach a screenshot of the whole desktop (I blurred out the icons)

** Attachment added: "Screenshot from 2020-07-14 01-37-20.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1887446/+attachment/5392430/+files/Screenshot%20from%202020-07-14%2001-37-20.png

-- 
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/1887446

Title:
  Area of desktop behind the Launcher is filled with random noise

Status in xorg package in Ubuntu:
  New

Bug description:
  The screenshot speaks for itself.

  Stuff like this used to happen occasionally up to 16.04, sually after
  resuming from suspend, but normally the areas would get redrawn
  properly sooner or later.

  But since I upgraded to 20.04 I've seen display garbage like this a
  lot more often, and this particular instance has been like this for
  hours now.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 13 18:51:51 2020
  DistUpgraded: 2020-07-12 20:55:12,554 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.108, 5.3.0-62-generic, x86_64: installed
   nvidia-340, 340.108, 5.4.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
   NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
  InstallationDate: Installed on 2013-10-11 (2466 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.family: Type1Family
  dmi.product.name: Aspire V3-571G
  dmi.product.sku: Aspire V3-_0648_V2.07
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sun Jul 12 20:59:51 2020
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.8-2ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1887446/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : 

[Touch-packages] [Bug 1887446] [NEW] Area of desktop behind the Launcher is filled with random noise

2020-07-13 Thread teo1978
Public bug reported:

The screenshot speaks for itself.

Stuff like this used to happen occasionally up to 16.04, sually after
resuming from suspend, but normally the areas would get redrawn properly
sooner or later.

But since I upgraded to 20.04 I've seen display garbage like this a lot
more often, and this particular instance has been like this for hours
now.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 13 18:51:51 2020
DistUpgraded: 2020-07-12 20:55:12,554 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia-340, 340.108, 5.3.0-62-generic, x86_64: installed
 nvidia-340, 340.108, 5.4.0-40-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
 NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
InstallationDate: Installed on 2013-10-11 (2466 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Acer Aspire V3-571G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago)
dmi.bios.date: 10/15/2012
dmi.bios.vendor: Acer
dmi.bios.version: V2.07
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: VA50_HC_CR
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.07
dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
dmi.product.family: Type1Family
dmi.product.name: Aspire V3-571G
dmi.product.sku: Aspire V3-_0648_V2.07
dmi.product.version: V2.07
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Sun Jul 12 20:59:51 2020
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.8-2ubuntu2.1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages ubuntu

** Attachment added: "Screenshot from 2020-07-13 18-51-36.png"
   
https://bugs.launchpad.net/bugs/1887446/+attachment/5392401/+files/Screenshot%20from%202020-07-13%2018-51-36.png

-- 
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/1887446

Title:
  Area of desktop behind the Launcher is filled with random noise

Status in xorg package in Ubuntu:
  New

Bug description:
  The screenshot speaks for itself.

  Stuff like this used to happen occasionally up to 16.04, sually after
  resuming from suspend, but normally the areas would get redrawn
  properly sooner or later.

  But since I upgraded to 20.04 I've seen display garbage like this a
  lot more often, and this particular instance has been like this for
  hours now.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  

[Touch-packages] [Bug 1887404]

2020-07-13 Thread darkakrog76
1AdvuJTbqaAJdNc2ur2vAddg66WzX19q1N

-- 
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/1887404

Title:
  the information was send by the system

Status in xorg package in Ubuntu:
  New

Bug description:
  the information was send by the system

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18
  Uname: Linux 4.15.0-109-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Jul 13 12:42:26 2020
  DistUpgraded: 2019-01-28 11:28:31,005 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:0782]
 Subsystem: Dell GM108M [GeForce 940MX] [1028:0782]
  InstallationDate: Installed on 2018-05-07 (798 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 7560
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-109-generic 
root=UUID=21d7010c-b6c8-41b7-a8fc-3e0dfe929d16 ro nopat vesafb.invalid=1 
drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-01-28 (532 days ago)
  dmi.bios.date: 07/19/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.6
  dmi.board.name: 09WC1G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.6:bd07/19/2017:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn09WC1G:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7560
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Jan 28 09:06:38 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1716 
   vendor BOE
  xserver.version: 2:1.18.4-0ubuntu0.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1887404/+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 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf

2020-07-13 Thread Sultan Alsawaf
The script responsible for updating the /boot/initrd.img symlink is
called `linux-update-symlinks`. If a kernel is installed without that
script being run, the symlink will not be updated.

The only place where `linux-update-symlinks` is run is inside each of
our kernels, in `debian/templates/image.postinst.in`. This means that
when our kernels are built as .deb packages, the appropriate machinery
will be placed inside the .deb to thus update the /boot/initrd.img
symlink.

I checked the change history to `installkernel` and could not find any
point in time in which it ran `linux-update-symlinks`. Furthermore, the
help info inside `linux-update-symlinks` contains the following note:
"This command is intended to be called from the postinst and postrm
maintainer scripts of Linux kernel packages." It looks like `linux-
update-symlinks` was only ever intended to be used in postinst/postrm
hooks for .deb packages (and not called by `installkernel`).

There are a few remedies to this problem I can see, but I'm not sure which is 
the correct solution:
1. Add a call to `linux-update-symlinks` into `installkernel`
or
2. Add a script into /etc/kernel/postinst.d to run `linux-update-symlinks`
or
3. Run `linux-update-symlinks` manually after installing a kernel directly via 
`installkernel`

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debianutils in Ubuntu.
https://bugs.launchpad.net/bugs/1877088

Title:
  [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img
  which is required with the default zipl.conf

Status in Ubuntu on IBM z Systems:
  Triaged
Status in debianutils package in Ubuntu:
  New
Status in linux-base package in Ubuntu:
  New

Bug description:
  When testing development kernels I usually rely on the installkernel
  script either through the "make install" target of the Kernel source
  or manually. This used to work great on Ubuntu on Z.

  On Ubuntu 20.04 (freshly installed up to date) this fails however because
  /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the
  wrong kernel/initrd combination rendering the system unbootable.

  (with the correct modules already copied to 
/usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/)
  # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasda (3844).
  Done.
  run-parts: executing /etc/kernel/postinst.d/zz-zipl 
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasda (3844).
  Done.
  # ls -l /boot
  total 178364
  -rw--- 1 root root135168 May  6 11:52 bootmap
  -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic
  lrwxrwxrwx 1 root root27 May  6 11:40 initrd.img -> 
initrd.img-5.4.0-29-generic   <== should point to new version
  -rw-r--r-- 1 root root  19663996 May  6 11:42 initrd.img-5.4.0-29-generic
  -rw-r--r-- 1 root root 125339494 May  6 11:52 
initrd.img-5.7.0-rc4-06500-gb67ea026badd
  lrwxrwxrwx 1 root root27 May  6 11:40 initrd.img.old -> 
initrd.img-5.4.0-29-generic
  -rw--- 1 root root   3087920 Apr 29 15:34 System.map-5.4.0-29-generic
  -rw-r--r-- 1 root root   4031691 May  6 11:52 
System.map-5.7.0-rc4-06500-gb67ea026badd
  -rw-r--r-- 1 root root   4031691 May  6 11:49 
System.map-5.7.0-rc4-06500-gb67ea026badd.old
  lrwxrwxrwx 1 root root37 May  6 11:52 vmlinuz -> 
vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  -rw--- 1 root root   8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic
  -rw-r--r-- 1 root root   9080832 May  6 11:52 
vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  -rw-r--r-- 1 root root   9080832 May  6 11:49 
vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old
  lrwxrwxrwx 1 root root41 May  6 11:52 vmlinuz.old -> 
vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+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 1887016] Re: Openssh default config has two PasswordAuthentication params

2020-07-13 Thread Lucas Kanashiro
I launched a VM locally and I also was not able to find what you
mentioned. Not sure what might have happened to make you get to this
state.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1887016

Title:
  Openssh default config has two PasswordAuthentication params

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu server 20.04 the /etc/ssh/sshd_config file has an additional
  `PasswordAuthentication yes` string in the end.

  It can lead to security problems, because there's already one string
  `# PasswordAuthentication yes` in the beginning of the file. It is
  supposed to be uncommented if it's needed to change the default value.

  But if the user uncomments this string and set in to "no", it will be
  overriden by the last line of config.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1887016/+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 1863080] Re: Unable to use dead keys in Java apps

2020-07-13 Thread Gunnar Hjalmarsson
** Also affects: ibus via
   https://github.com/ibus/ibus/issues/2237
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1863080

Title:
  Unable to use dead keys in Java apps

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  This is same bug as #540751, as it happens again in Ubuntu 19.10 with
  Java 11. Way of reproduce it:

  - Fresh Ubuntu 19.10 install.
  - Install default-jre.
  - Download (for example) lastest NetBeans version.
  - Edit a file in NetBeans, you can't insert characters like 'á'.

  The workaround is the same, define XMODIFIERS='' before launching the
  app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1863080/+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 1884265] Re: [fips] Not fully initialized digest segfaulting some client applications

2020-07-13 Thread Joy Latten
** Changed in: openssl (Ubuntu)
 Assignee: (unassigned) => Joy Latten (j-latten)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1884265

Title:
  [fips] Not fully initialized digest segfaulting some client
  applications

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Bionic:
  New

Bug description:
  [Impact]
  In FIPS mode on Bionic MD5 is semi-disabled causing some applications to 
segfault.

  ntpq uses crypto hashes to authenticate its requests. By default it
  uses md5. However, when compiled with openssl it creates a lists of
  acceptable hashes from openssl that can be used.

  [Test Steps]
  Test case:
  sudo apt install ntp
  ntpq -p
  Segmentation fault (core dumped)

  What happens there is ntpq wants to iterate all available digests
  (list_digest_names in ntpq.c). It uses EVP_MD_do_all_sorted for this
  task.

  EVP_MD_do_all_sorted eventually runs openssl_add_all_digests_int in c_alld.c.
  For FIPS mode it adds:
  EVP_add_digest(EVP_md5());

  What happens later in ntpq is (list_md_fn function inside ntpq.c):
  ctx = EVP_MD_CTX_new();
  EVP_DigestInit(ctx, EVP_get_digestbyname(name));
  EVP_DigestFinal(ctx, digest, _len);

  First digest it gets is MD5, but while running EVP_DigestInit for it, it gets 
to this point (openssl/crypto/evp/digest.c EVP_DigestInit_ex):
  #ifdef OPENSSL_FIPS
  if (FIPS_mode()) {
  if (!(type->flags & EVP_MD_FLAG_FIPS)
  && !(ctx->flags & EVP_MD_CTX_FLAG_NON_FIPS_ALLOW)) {
  EVPerr(EVP_F_EVP_DIGESTINIT_EX, EVP_R_DISABLED_FOR_FIPS);
  return 0;
  }
  }
  #endif

  Due to type->flags for MD5 being 0 there's an error set 
(EVP_R_DISABLED_FOR_FIPS).
  After getting back to ntpq.c:
  ctx->engine and ctx->digest are not set (due to the mentioned error), hence

  inside EVP_DigestFinal_ex (openssl/crypto/evp/digest.c)
  OPENSSL_assert(ctx->digest->md_size <= EVP_MAX_MD_SIZE);
  causes a segfault (ctx->digest is NULL).

  So either MD5 shouldn't be added in FIPS mode or it should have the
  EVP_MD_FLAG_FIPS to be properly initialized.

  [Regression Potential]

  I don't think this should regress ntpq + openssl from the Ubuntu
  archive.

  Current archive ntpq + openssl behaviour:
  openssl includes all message digests and hands ntpq a sorted digest-list. 
  ntpq doesn't check return from EVP_Digest(Init|Final) and assumes all is well 
and sticks all digests into its list regardless if it is working or not.

  i.e.  
  ntpq> help keytype
  function: set key type to use for authenticated requests, one of:
  MD4, MD5, RIPEMD160, SHA1, SHAKE128

  If somehow openssl library is corrupted and sends back erroneous
  results, its possible the authentication will just not ever work.

  Newly fixed archive ntpq + oenssl beahviour:
  openssl includes all message digests and hands ntpq a sorted digest-list.
  ntpq checks each one and includes each working digest. With a non-corrupted 
openssl, everything works fine and ntpq includes each into its list. Ends up 
with a list identical to the one above.
   
  If somehow opensll library is corrupted and sends back erroneous results, 
ntpq will hopefully catch it by checking return code and include only those 
algos that appear to be working. Its possible authentication will work for ntpq.

  The difference will be seen in ntpq + fips-openssl. ntpq will check
  return, and for fips-not-approved algos, return will indicate an
  error. So these algos will be skipped and ntpq will not include into
  its digest list. Resulting in a much shorter list of only fips-
  approved algos.

  i.e.
  ntpq> help keytype
  function: set key type to use for authenticated requests, one of:
  SHA1, SHAKE128

  Since md5 is ntpq's default auth algo, this will need to be changed to one of 
the above algos in the config files. 
  But I think it is somewhat understood that MD5 is bad in a FIPS environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1884265/+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 1884265] Re: [fips] Not fully initialized digest segfaulting some client applications

2020-07-13 Thread Joy Latten
Additional testing for ntpq authentication to ensure MD5 still works for
ntpq in archive

NOTE: The shown testing is ntpq(with patch) + openssl from archive. To ensure 
all still works.
Testing with ntpq + fips-openssl was also done successfully.
 
VM-A (ntp server) 

1. Edit /etc/ntp.keys to include,

1 SHA1 austintexas
2 MD5 cedarpark

2. Edit /etc/ntp.conf to include.

keys /etc/ntp.keys   
trustedkey 2 
controlkey 2
requestkey 2

3. restart ntp
sudo service ntp restart

VM-B (ntp client)

$ dpkg -l | grep ntp
ii  ntp1:4.2.8p10+dfsg-5ubuntu7.1+ppa1  
   amd64Network Time Protocol daemon and utility programs

1. Edit /etc/ntp.keys to include,

1 SHA1 austintexas
2 MD5 cedarpark

2. Edit /etc/ntp.conf to include,
keys /etc/ntp.keys
server  key 2
trustedkey 2
controlkey 2
requestkey 2

3. I commented out all the "pool" entries in /etc/ntp.conf

4. restart ntp
sudo service ntp restart


On the client,

$ ntpq -c as

ind assid status  conf reach auth condition  last_event cnt
===
  1 46728  f014   yes   yes   ok reject   reachable  1

Notice that "auth" is ok.

$ ntpq
ntpq> keytype
keytype is MD5 with 16 octet digests
ntpq> keyid 2
ntpq> ifstats
MD5 Password: 
interface namesend
 #  address/broadcast drop flag ttl mc received sent failed peers   uptime
==
  0 v6wildcard   D   81   0  0  0  0  0 0   96
[::]:123
  1 v4wildcard   D   89   0  0  0  0  0 0   96
0.0.0.0:123
  2 lo   .5   0  0  2  1  0 0   96
127.0.0.1:123
  3 ens3 .   19   0  0  2  2  0 1   96
192.168.122.105:123
  4 lo   .5   0  0  0  0  0 0   96
[::1]:123
  5 ens3 .   11   0  0  0  0  0 0   96
[fe80::5054:ff:fefe:b092%2]:123
ntpq> 


Note: issuing "ifstats" requires authentication.

I also tested with SHA1 and it worked as well.


And last test on client, 
ntpq -p 

remote   refid  st t when poll reach   delay   offset  jitter
==
 192.168.122.106 204.11.201.123 u   56   6471.5412.723   0.826

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1884265

Title:
  [fips] Not fully initialized digest segfaulting some client
  applications

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Bionic:
  New

Bug description:
  [Impact]
  In FIPS mode on Bionic MD5 is semi-disabled causing some applications to 
segfault.

  ntpq uses crypto hashes to authenticate its requests. By default it
  uses md5. However, when compiled with openssl it creates a lists of
  acceptable hashes from openssl that can be used.

  [Test Steps]
  Test case:
  sudo apt install ntp
  ntpq -p
  Segmentation fault (core dumped)

  What happens there is ntpq wants to iterate all available digests
  (list_digest_names in ntpq.c). It uses EVP_MD_do_all_sorted for this
  task.

  EVP_MD_do_all_sorted eventually runs openssl_add_all_digests_int in c_alld.c.
  For FIPS mode it adds:
  EVP_add_digest(EVP_md5());

  What happens later in ntpq is (list_md_fn function inside ntpq.c):
  ctx = EVP_MD_CTX_new();
  EVP_DigestInit(ctx, EVP_get_digestbyname(name));
  EVP_DigestFinal(ctx, digest, _len);

  First digest it gets is MD5, but while running EVP_DigestInit for it, it gets 
to this point (openssl/crypto/evp/digest.c EVP_DigestInit_ex):
  #ifdef OPENSSL_FIPS
  if (FIPS_mode()) {
  if (!(type->flags & EVP_MD_FLAG_FIPS)
  && !(ctx->flags & EVP_MD_CTX_FLAG_NON_FIPS_ALLOW)) {
  EVPerr(EVP_F_EVP_DIGESTINIT_EX, EVP_R_DISABLED_FOR_FIPS);
  return 0;
  }
  }
  #endif

  Due to type->flags for MD5 being 0 there's an error set 
(EVP_R_DISABLED_FOR_FIPS).
  After getting back to ntpq.c:
  ctx->engine and ctx->digest are not set (due to the mentioned error), hence

  inside EVP_DigestFinal_ex (openssl/crypto/evp/digest.c)
  OPENSSL_assert(ctx->digest->md_size <= EVP_MAX_MD_SIZE);
  causes a segfault (ctx->digest is NULL).

  So either MD5 shouldn't be added in FIPS mode or it should have the
  EVP_MD_FLAG_FIPS to be properly initialized.

  [Regression Potential]

  I don't think this should regress ntpq + openssl from the Ubuntu
  archive.

  Current archive ntpq + openssl behaviour:
  openssl includes all message digests and hands ntpq a sorted digest-list. 
  ntpq doesn't check return from EVP_Digest(Init|Final) and assumes all is well 
and sticks all 

[Touch-packages] [Bug 1884265] Re: [fips] Not fully initialized digest segfaulting some client applications

2020-07-13 Thread Joy Latten
Testing:

There are no autopkgtests for ntp pkg and we do not run "make check" in
the tests dir as part of the build. So, just in case it is applicable, I
ran make check on my local build to ensure everything passes.

** Attachment added: "Results of running make check in ../tests directory"
   
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1884265/+attachment/5392383/+files/ntp-test-results

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1884265

Title:
  [fips] Not fully initialized digest segfaulting some client
  applications

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Bionic:
  New

Bug description:
  [Impact]
  In FIPS mode on Bionic MD5 is semi-disabled causing some applications to 
segfault.

  ntpq uses crypto hashes to authenticate its requests. By default it
  uses md5. However, when compiled with openssl it creates a lists of
  acceptable hashes from openssl that can be used.

  [Test Steps]
  Test case:
  sudo apt install ntp
  ntpq -p
  Segmentation fault (core dumped)

  What happens there is ntpq wants to iterate all available digests
  (list_digest_names in ntpq.c). It uses EVP_MD_do_all_sorted for this
  task.

  EVP_MD_do_all_sorted eventually runs openssl_add_all_digests_int in c_alld.c.
  For FIPS mode it adds:
  EVP_add_digest(EVP_md5());

  What happens later in ntpq is (list_md_fn function inside ntpq.c):
  ctx = EVP_MD_CTX_new();
  EVP_DigestInit(ctx, EVP_get_digestbyname(name));
  EVP_DigestFinal(ctx, digest, _len);

  First digest it gets is MD5, but while running EVP_DigestInit for it, it gets 
to this point (openssl/crypto/evp/digest.c EVP_DigestInit_ex):
  #ifdef OPENSSL_FIPS
  if (FIPS_mode()) {
  if (!(type->flags & EVP_MD_FLAG_FIPS)
  && !(ctx->flags & EVP_MD_CTX_FLAG_NON_FIPS_ALLOW)) {
  EVPerr(EVP_F_EVP_DIGESTINIT_EX, EVP_R_DISABLED_FOR_FIPS);
  return 0;
  }
  }
  #endif

  Due to type->flags for MD5 being 0 there's an error set 
(EVP_R_DISABLED_FOR_FIPS).
  After getting back to ntpq.c:
  ctx->engine and ctx->digest are not set (due to the mentioned error), hence

  inside EVP_DigestFinal_ex (openssl/crypto/evp/digest.c)
  OPENSSL_assert(ctx->digest->md_size <= EVP_MAX_MD_SIZE);
  causes a segfault (ctx->digest is NULL).

  So either MD5 shouldn't be added in FIPS mode or it should have the
  EVP_MD_FLAG_FIPS to be properly initialized.

  [Regression Potential]

  I don't think this should regress ntpq + openssl from the Ubuntu
  archive.

  Current archive ntpq + openssl behaviour:
  openssl includes all message digests and hands ntpq a sorted digest-list. 
  ntpq doesn't check return from EVP_Digest(Init|Final) and assumes all is well 
and sticks all digests into its list regardless if it is working or not.

  i.e.  
  ntpq> help keytype
  function: set key type to use for authenticated requests, one of:
  MD4, MD5, RIPEMD160, SHA1, SHAKE128

  If somehow openssl library is corrupted and sends back erroneous
  results, its possible the authentication will just not ever work.

  Newly fixed archive ntpq + oenssl beahviour:
  openssl includes all message digests and hands ntpq a sorted digest-list.
  ntpq checks each one and includes each working digest. With a non-corrupted 
openssl, everything works fine and ntpq includes each into its list. Ends up 
with a list identical to the one above.
   
  If somehow opensll library is corrupted and sends back erroneous results, 
ntpq will hopefully catch it by checking return code and include only those 
algos that appear to be working. Its possible authentication will work for ntpq.

  The difference will be seen in ntpq + fips-openssl. ntpq will check
  return, and for fips-not-approved algos, return will indicate an
  error. So these algos will be skipped and ntpq will not include into
  its digest list. Resulting in a much shorter list of only fips-
  approved algos.

  i.e.
  ntpq> help keytype
  function: set key type to use for authenticated requests, one of:
  SHA1, SHAKE128

  Since md5 is ntpq's default auth algo, this will need to be changed to one of 
the above algos in the config files. 
  But I think it is somewhat understood that MD5 is bad in a FIPS environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1884265/+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 1884265] Re: [fips] Not fully initialized digest segfaulting some client applications

2020-07-13 Thread Joy Latten
** Description changed:

  [Impact]
  In FIPS mode on Bionic MD5 is semi-disabled causing some applications to 
segfault.
  
- ntpq uses crypto hashes to authenticate its requests. By default it appears 
to use an internal md5 implementation. However, when compiled with openssl it 
creates a lists of acceptable hashes from openssl that can be used. 
-  
+ ntpq uses crypto hashes to authenticate its requests. By default it uses
+ md5. However, when compiled with openssl it creates a lists of
+ acceptable hashes from openssl that can be used.
+ 
  [Test Steps]
  Test case:
  sudo apt install ntp
  ntpq -p
  Segmentation fault (core dumped)
  
  What happens there is ntpq wants to iterate all available digests
  (list_digest_names in ntpq.c). It uses EVP_MD_do_all_sorted for this
  task.
  
  EVP_MD_do_all_sorted eventually runs openssl_add_all_digests_int in c_alld.c.
  For FIPS mode it adds:
  EVP_add_digest(EVP_md5());
  
  What happens later in ntpq is (list_md_fn function inside ntpq.c):
  ctx = EVP_MD_CTX_new();
  EVP_DigestInit(ctx, EVP_get_digestbyname(name));
  EVP_DigestFinal(ctx, digest, _len);
  
  First digest it gets is MD5, but while running EVP_DigestInit for it, it gets 
to this point (openssl/crypto/evp/digest.c EVP_DigestInit_ex):
  #ifdef OPENSSL_FIPS
  if (FIPS_mode()) {
  if (!(type->flags & EVP_MD_FLAG_FIPS)
  && !(ctx->flags & EVP_MD_CTX_FLAG_NON_FIPS_ALLOW)) {
  EVPerr(EVP_F_EVP_DIGESTINIT_EX, EVP_R_DISABLED_FOR_FIPS);
  return 0;
  }
  }
  #endif
  
  Due to type->flags for MD5 being 0 there's an error set 
(EVP_R_DISABLED_FOR_FIPS).
  After getting back to ntpq.c:
  ctx->engine and ctx->digest are not set (due to the mentioned error), hence
  
  inside EVP_DigestFinal_ex (openssl/crypto/evp/digest.c)
  OPENSSL_assert(ctx->digest->md_size <= EVP_MAX_MD_SIZE);
  causes a segfault (ctx->digest is NULL).
  
  So either MD5 shouldn't be added in FIPS mode or it should have the
  EVP_MD_FLAG_FIPS to be properly initialized.
  
  [Regression Potential]
  
- I believe the resolution to check the return code and if unsuccessful, do not 
include the hash algorithm in the internal ntpq digest list, should not 
introduce any regression.
- It will simply not add md5 and md5_sha1 to its lists of digests when compiled 
with openssl. Instead it will add the others like sha1, sha2, and sha3.
+ I don't think this should regress ntpq + openssl from the Ubuntu
+ archive.
+ 
+ Current archive ntpq + openssl behaviour:
+ openssl includes all message digests and hands ntpq a sorted digest-list. 
+ ntpq doesn't check return from EVP_Digest(Init|Final) and assumes all is well 
and sticks all digests into its list regardless if it is working or not.
+ 
+ i.e.  
+ ntpq> help keytype
+ function: set key type to use for authenticated requests, one of:
+ MD4, MD5, RIPEMD160, SHA1, SHAKE128
+ 
+ If somehow openssl library is corrupted and sends back erroneous
+ results, its possible the authentication will just not ever work.
+ 
+ Newly fixed archive ntpq + oenssl beahviour:
+ openssl includes all message digests and hands ntpq a sorted digest-list.
+ ntpq checks each one and includes each working digest. With a non-corrupted 
openssl, everything works fine and ntpq includes each into its list. Ends up 
with a list identical to the one above.
+  
+ If somehow opensll library is corrupted and sends back erroneous results, 
ntpq will hopefully catch it by checking return code and include only those 
algos that appear to be working. Its possible authentication will work for ntpq.
+ 
+ The difference will be seen in ntpq + fips-openssl. ntpq will check
+ return, and for fips-not-approved algos, return will indicate an error.
+ So these algos will be skipped and ntpq will not include into its digest
+ list. Resulting in a much shorter list of only fips-approved algos.
+ 
+ i.e.
+ ntpq> help keytype
+ function: set key type to use for authenticated requests, one of:
+ SHA1, SHAKE128
+ 
+ Since md5 is ntpq's default auth algo, this will need to be changed to one of 
the above algos in the config files. 
+ But I think it is somewhat understood that MD5 is bad in a FIPS environment.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1884265

Title:
  [fips] Not fully initialized digest segfaulting some client
  applications

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Bionic:
  New

Bug description:
  [Impact]
  In FIPS mode on Bionic MD5 is semi-disabled causing some applications to 
segfault.

  ntpq uses crypto hashes to authenticate its requests. By default it
  uses md5. However, when compiled with openssl it creates a lists of
  acceptable hashes from openssl that can be used.

  [Test Steps]
  Test case:
  sudo apt install ntp
  ntpq -p
  Segmentation fault (core 

[Touch-packages] [Bug 1863080] Re: Unable to use dead keys in Java apps

2020-07-13 Thread indigocat
Opened issue in iBus repo: https://github.com/ibus/ibus/issues/2237

** Bug watch added: github.com/ibus/ibus/issues #2237
   https://github.com/ibus/ibus/issues/2237

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1863080

Title:
  Unable to use dead keys in Java apps

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  This is same bug as #540751, as it happens again in Ubuntu 19.10 with
  Java 11. Way of reproduce it:

  - Fresh Ubuntu 19.10 install.
  - Install default-jre.
  - Download (for example) lastest NetBeans version.
  - Edit a file in NetBeans, you can't insert characters like 'á'.

  The workaround is the same, define XMODIFIERS='' before launching the
  app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1863080/+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 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)

2020-07-13 Thread Noctis Bennington
On W10 it's setted as 1920x1080 - 59Hz. It works perfectly.

I tried with this resolution on Ubuntu 20.04. Still doesn't works.

** Attachment added: "Resolution and refresh second monitor on W10.PNG"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1871721/+attachment/5392357/+files/Resolution%20and%20refresh%20second%20monitor%20on%20W10.PNG

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 

[Touch-packages] [Bug 1886128] Re: walinuxagent blocks DNS fallback to TCP

2020-07-13 Thread Dan Streetman
** Changed in: systemd (Ubuntu)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: systemd (Ubuntu)
   Importance: Medium => Undecided

-- 
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/1886128

Title:
  walinuxagent blocks DNS fallback to TCP

Status in systemd package in Ubuntu:
  Invalid
Status in walinuxagent package in Ubuntu:
  New

Bug description:
  [impact]

  on azure instances, walinuxagent blocks all (new) TCP connections to
  the azure nameserver, which prevents fallback to TCP DNS for truncated
  dns queries

  [test case]

  on an azure instance:

  ddstreet@lp1886128:~$ systemd-resolve --status | grep Servers
   DNS Servers: 168.63.129.16
  ddstreet@lp1886128:~$ dig +retries=0 +timeout=1 +short +tcp @168.63.129.16 
toomany100.ddstreet.org
  ;; connection timed out; no servers could be reached
  ;; Connection to 168.63.129.16#53(168.63.129.16) for toomany100.ddstreet.org 
failed: timed out.

  
  change the actual nameserver ip in the 'dig' command to match what resolved 
is configured with (which comes from dhcp)

  [regression potential]

  TBD

  [scope]

  TBD

  [original description]

  
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  systemd-resolve --version

  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
  +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN
  -PCRE2 default-hierarchy=hybrid

  We met an error: on an attempt to resolve address, the following issue
  appears:

  ; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> 
mharder-formrec.cognitiveservices.azure.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44096
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;mharder-formrec.cognitiveservices.azure.com. IN  A

  ;; Query time: 231 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Tue Apr 28 20:47:14 UTC 2020
  ;; MSG SIZE  rcvd: 72

  Let me provide you important notes about the issue:
  1) It's not reproducing on Ubuntu 16;
  2) Bypassing systemd-resolve - everything works fine;
  3) Only the difference between systemd-resolve and END is UDP_PAYLOAD_SIZE

  Successful query:

  113516:27:25.964386 10.1.0.4168.63.129.16   DNS 128
  Standard query 0xc2d4 A mharder-formrec.cognitiveservices.azure.com
  OPT

  Domain Name System (query)
  Transaction ID: 0xc2d4
  Flags: 0x0120 Standard query
  0...    = Response: Message is a query
  .000 0...   = Opcode: Standard query (0)
   ..0.   = Truncated: Message is not truncated
   ...1   = Recursion desired: Do query recursively
    .0..  = Z: reserved (0)
    ..1.  = AD bit: Set
    ...0  = Non-authenticated data: Unacceptable
  Questions: 1
  Answer RRs: 0
  Authority RRs: 0
  Additional RRs: 1
  Queries
  mharder-formrec.cognitiveservices.azure.com: type A, class IN
  Additional records
  : type OPT
  Name: 
  Type: OPT (41)
  UDP payload size: 4096
  Higher bits in extended RCODE: 0x00
  EDNS0 version: 0
  Z: 0x
  0...    = DO bit: Cannot handle DNSSEC security 
RRs
  .000    = Reserved: 0x
  Data length: 12
  Option: COOKIE
  Unsuccessful query:

  112816:27:25.713886 10.1.0.4168.63.129.16   DNS 116
  Standard query 0x198d A mharder-formrec.cognitiveservices.azure.com
  OPT

  Domain Name System (query)
  Transaction ID: 0x198d
  Flags: 0x0100 Standard query
  0...    = Response: Message is a query
  .000 0...   = Opcode: Standard query (0)
   ..0.   = Truncated: Message is not truncated
   ...1   = Recursion desired: Do query recursively
    .0..  = Z: reserved (0)
    ...0  = Non-authenticated data: Unacceptable
  Questions: 1
  Answer RRs: 0
  Authority RRs: 0
  Additional RRs: 1
  Queries
  mharder-formrec.cognitiveservices.azure.com: type A, class IN
  Additional records
  : type OPT
  Name: 
  Type: OPT (41)
  UDP payload size: 512
  Higher bits in extended RCODE: 0x00
  EDNS0 version: 0
  Z: 0x
  0...    = DO bit: Cannot handle DNSSEC security 
RRs
  .000    = Reserved: 0x
  Data length: 0
  Notable difference:

  Success:
  UDP payload size: 4096


[Touch-packages] [Bug 1886128] Re: walinuxagent blocks DNS fallback to TCP

2020-07-13 Thread Dan Streetman
also note that the iptable rules that walinuxagent adds does allow TCP
traffic to the nameserver if the process is running as root, e.g.:

ddstreet@lp1886128:~$ dig +retries=0 +timeout=1 +short +tcp @168.63.129.16 
toomany100.ddstreet.org
;; connection timed out; no servers could be reached
;; Connection to 168.63.129.16#53(168.63.129.16) for toomany100.ddstreet.org 
failed: timed out.
ddstreet@lp1886128:~$ sudo dig +retries=0 +timeout=1 +short +tcp @168.63.129.16 
toomany100.ddstreet.org | head -5
10.254.201.0
10.254.201.1
10.254.201.18
10.254.201.19
10.254.201.2


however systemd-resolved doesn't run as root, it runs as the 'systemd-resolve' 
user.

-- 
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/1886128

Title:
  walinuxagent blocks DNS fallback to TCP

Status in systemd package in Ubuntu:
  Invalid
Status in walinuxagent package in Ubuntu:
  New

Bug description:
  [impact]

  on azure instances, walinuxagent blocks all (new) TCP connections to
  the azure nameserver, which prevents fallback to TCP DNS for truncated
  dns queries

  [test case]

  on an azure instance:

  ddstreet@lp1886128:~$ systemd-resolve --status | grep Servers
   DNS Servers: 168.63.129.16
  ddstreet@lp1886128:~$ dig +retries=0 +timeout=1 +short +tcp @168.63.129.16 
toomany100.ddstreet.org
  ;; connection timed out; no servers could be reached
  ;; Connection to 168.63.129.16#53(168.63.129.16) for toomany100.ddstreet.org 
failed: timed out.

  
  change the actual nameserver ip in the 'dig' command to match what resolved 
is configured with (which comes from dhcp)

  [regression potential]

  TBD

  [scope]

  TBD

  [original description]

  
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  systemd-resolve --version

  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
  +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN
  -PCRE2 default-hierarchy=hybrid

  We met an error: on an attempt to resolve address, the following issue
  appears:

  ; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> 
mharder-formrec.cognitiveservices.azure.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44096
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;mharder-formrec.cognitiveservices.azure.com. IN  A

  ;; Query time: 231 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Tue Apr 28 20:47:14 UTC 2020
  ;; MSG SIZE  rcvd: 72

  Let me provide you important notes about the issue:
  1) It's not reproducing on Ubuntu 16;
  2) Bypassing systemd-resolve - everything works fine;
  3) Only the difference between systemd-resolve and END is UDP_PAYLOAD_SIZE

  Successful query:

  113516:27:25.964386 10.1.0.4168.63.129.16   DNS 128
  Standard query 0xc2d4 A mharder-formrec.cognitiveservices.azure.com
  OPT

  Domain Name System (query)
  Transaction ID: 0xc2d4
  Flags: 0x0120 Standard query
  0...    = Response: Message is a query
  .000 0...   = Opcode: Standard query (0)
   ..0.   = Truncated: Message is not truncated
   ...1   = Recursion desired: Do query recursively
    .0..  = Z: reserved (0)
    ..1.  = AD bit: Set
    ...0  = Non-authenticated data: Unacceptable
  Questions: 1
  Answer RRs: 0
  Authority RRs: 0
  Additional RRs: 1
  Queries
  mharder-formrec.cognitiveservices.azure.com: type A, class IN
  Additional records
  : type OPT
  Name: 
  Type: OPT (41)
  UDP payload size: 4096
  Higher bits in extended RCODE: 0x00
  EDNS0 version: 0
  Z: 0x
  0...    = DO bit: Cannot handle DNSSEC security 
RRs
  .000    = Reserved: 0x
  Data length: 12
  Option: COOKIE
  Unsuccessful query:

  112816:27:25.713886 10.1.0.4168.63.129.16   DNS 116
  Standard query 0x198d A mharder-formrec.cognitiveservices.azure.com
  OPT

  Domain Name System (query)
  Transaction ID: 0x198d
  Flags: 0x0100 Standard query
  0...    = Response: Message is a query
  .000 0...   = Opcode: Standard query (0)
   ..0.   = Truncated: Message is not truncated
   ...1   = Recursion desired: Do query recursively
    .0..  = Z: reserved (0)
    ...0  = Non-authenticated data: Unacceptable
  Questions: 1
  Answer RRs: 0
  Authority RRs: 0
  Additional RRs: 1
  Queries
  

[Touch-packages] [Bug 1886128] Re: walinuxagent blocks DNS fallback to TCP

2020-07-13 Thread Chris Newcomer
Issue filed against walinuxagent on GitHub:
https://github.com/Azure/WALinuxAgent/issues/1673

** Bug watch added: github.com/Azure/WALinuxAgent/issues #1673
   https://github.com/Azure/WALinuxAgent/issues/1673

-- 
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/1886128

Title:
  walinuxagent blocks DNS fallback to TCP

Status in systemd package in Ubuntu:
  Invalid
Status in walinuxagent package in Ubuntu:
  New

Bug description:
  [impact]

  on azure instances, walinuxagent blocks all (new) TCP connections to
  the azure nameserver, which prevents fallback to TCP DNS for truncated
  dns queries

  [test case]

  on an azure instance:

  ddstreet@lp1886128:~$ systemd-resolve --status | grep Servers
   DNS Servers: 168.63.129.16
  ddstreet@lp1886128:~$ dig +retries=0 +timeout=1 +short +tcp @168.63.129.16 
toomany100.ddstreet.org
  ;; connection timed out; no servers could be reached
  ;; Connection to 168.63.129.16#53(168.63.129.16) for toomany100.ddstreet.org 
failed: timed out.

  
  change the actual nameserver ip in the 'dig' command to match what resolved 
is configured with (which comes from dhcp)

  [regression potential]

  TBD

  [scope]

  TBD

  [original description]

  
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  systemd-resolve --version

  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
  +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN
  -PCRE2 default-hierarchy=hybrid

  We met an error: on an attempt to resolve address, the following issue
  appears:

  ; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> 
mharder-formrec.cognitiveservices.azure.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44096
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;mharder-formrec.cognitiveservices.azure.com. IN  A

  ;; Query time: 231 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Tue Apr 28 20:47:14 UTC 2020
  ;; MSG SIZE  rcvd: 72

  Let me provide you important notes about the issue:
  1) It's not reproducing on Ubuntu 16;
  2) Bypassing systemd-resolve - everything works fine;
  3) Only the difference between systemd-resolve and END is UDP_PAYLOAD_SIZE

  Successful query:

  113516:27:25.964386 10.1.0.4168.63.129.16   DNS 128
  Standard query 0xc2d4 A mharder-formrec.cognitiveservices.azure.com
  OPT

  Domain Name System (query)
  Transaction ID: 0xc2d4
  Flags: 0x0120 Standard query
  0...    = Response: Message is a query
  .000 0...   = Opcode: Standard query (0)
   ..0.   = Truncated: Message is not truncated
   ...1   = Recursion desired: Do query recursively
    .0..  = Z: reserved (0)
    ..1.  = AD bit: Set
    ...0  = Non-authenticated data: Unacceptable
  Questions: 1
  Answer RRs: 0
  Authority RRs: 0
  Additional RRs: 1
  Queries
  mharder-formrec.cognitiveservices.azure.com: type A, class IN
  Additional records
  : type OPT
  Name: 
  Type: OPT (41)
  UDP payload size: 4096
  Higher bits in extended RCODE: 0x00
  EDNS0 version: 0
  Z: 0x
  0...    = DO bit: Cannot handle DNSSEC security 
RRs
  .000    = Reserved: 0x
  Data length: 12
  Option: COOKIE
  Unsuccessful query:

  112816:27:25.713886 10.1.0.4168.63.129.16   DNS 116
  Standard query 0x198d A mharder-formrec.cognitiveservices.azure.com
  OPT

  Domain Name System (query)
  Transaction ID: 0x198d
  Flags: 0x0100 Standard query
  0...    = Response: Message is a query
  .000 0...   = Opcode: Standard query (0)
   ..0.   = Truncated: Message is not truncated
   ...1   = Recursion desired: Do query recursively
    .0..  = Z: reserved (0)
    ...0  = Non-authenticated data: Unacceptable
  Questions: 1
  Answer RRs: 0
  Authority RRs: 0
  Additional RRs: 1
  Queries
  mharder-formrec.cognitiveservices.azure.com: type A, class IN
  Additional records
  : type OPT
  Name: 
  Type: OPT (41)
  UDP payload size: 512
  Higher bits in extended RCODE: 0x00
  EDNS0 version: 0
  Z: 0x
  0...    = DO bit: Cannot handle DNSSEC security 
RRs
  .000    = Reserved: 0x
  Data length: 0
  Notable 

[Touch-packages] [Bug 1886128] Re: walinuxagent blocks DNS fallback to TCP

2020-07-13 Thread Dan Streetman
@darii-nurgaleev I marked this invalid for systemd as the specific
problem in this case is blocking fallback to TCP DNS by walinuxagent,
but if you want to open a separate bug to track updating systemd to use
large edns0 packets even without DNSSEC, please feel free to.

** Description changed:

+ [impact]
+ 
+ on azure instances, walinuxagent blocks all (new) TCP connections to the
+ azure nameserver, which prevents fallback to TCP DNS for truncated dns
+ queries
+ 
+ [test case]
+ 
+ on an azure instance:
+ 
+ ddstreet@lp1886128:~$ systemd-resolve --status | grep Servers
+  DNS Servers: 168.63.129.16
+ ddstreet@lp1886128:~$ dig +retries=0 +timeout=1 +short +tcp @168.63.129.16 
toomany100.ddstreet.org
+ ;; connection timed out; no servers could be reached
+ ;; Connection to 168.63.129.16#53(168.63.129.16) for toomany100.ddstreet.org 
failed: timed out.
+ 
+ 
+ change the actual nameserver ip in the 'dig' command to match what resolved 
is configured with (which comes from dhcp)
+ 
+ [regression potential]
+ 
+ TBD
+ 
+ [scope]
+ 
+ TBD
+ 
+ [original description]
+ 
+ 
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  
  systemd-resolve --version
  
  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
  +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN
  -PCRE2 default-hierarchy=hybrid
  
  We met an error: on an attempt to resolve address, the following issue
  appears:
  
  ; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> 
mharder-formrec.cognitiveservices.azure.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44096
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;mharder-formrec.cognitiveservices.azure.com. IN  A
  
  ;; Query time: 231 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Tue Apr 28 20:47:14 UTC 2020
  ;; MSG SIZE  rcvd: 72
  
  Let me provide you important notes about the issue:
  1) It's not reproducing on Ubuntu 16;
  2) Bypassing systemd-resolve - everything works fine;
  3) Only the difference between systemd-resolve and END is UDP_PAYLOAD_SIZE
  
  Successful query:
  
  113516:27:25.964386 10.1.0.4168.63.129.16   DNS 128
  Standard query 0xc2d4 A mharder-formrec.cognitiveservices.azure.com OPT
  
  Domain Name System (query)
- Transaction ID: 0xc2d4
- Flags: 0x0120 Standard query
- 0...    = Response: Message is a query
- .000 0...   = Opcode: Standard query (0)
-  ..0.   = Truncated: Message is not truncated
-  ...1   = Recursion desired: Do query recursively
-   .0..  = Z: reserved (0)
-   ..1.  = AD bit: Set
-   ...0  = Non-authenticated data: Unacceptable
- Questions: 1
- Answer RRs: 0
- Authority RRs: 0
- Additional RRs: 1
- Queries
- mharder-formrec.cognitiveservices.azure.com: type A, class IN
- Additional records
- : type OPT
- Name: 
- Type: OPT (41)
- UDP payload size: 4096
- Higher bits in extended RCODE: 0x00
- EDNS0 version: 0
- Z: 0x
- 0...    = DO bit: Cannot handle DNSSEC security 
RRs
- .000    = Reserved: 0x
- Data length: 12
- Option: COOKIE
+ Transaction ID: 0xc2d4
+ Flags: 0x0120 Standard query
+ 0...    = Response: Message is a query
+ .000 0...   = Opcode: Standard query (0)
+  ..0.   = Truncated: Message is not truncated
+  ...1   = Recursion desired: Do query recursively
+   .0..  = Z: reserved (0)
+   ..1.  = AD bit: Set
+   ...0  = Non-authenticated data: Unacceptable
+ Questions: 1
+ Answer RRs: 0
+ Authority RRs: 0
+ Additional RRs: 1
+ Queries
+ mharder-formrec.cognitiveservices.azure.com: type A, class IN
+ Additional records
+ : type OPT
+ Name: 
+ Type: OPT (41)
+ UDP payload size: 4096
+ Higher bits in extended RCODE: 0x00
+ EDNS0 version: 0
+ Z: 0x
+ 0...    = DO bit: Cannot handle DNSSEC security 
RRs
+ .000    = Reserved: 0x
+ Data length: 12
+ Option: COOKIE
  Unsuccessful query:
  
  112816:27:25.713886 10.1.0.4168.63.129.16   DNS 116
  Standard query 0x198d A mharder-formrec.cognitiveservices.azure.com OPT
  
  Domain Name System (query)
- Transaction ID: 0x198d
- Flags: 0x0100 Standard query
- 0...    = Response: Message is a query
- .000 0...   = 

[Touch-packages] [Bug 1886128] Re: systemd-resolved does not resolve address due to udp payload size.

2020-07-13 Thread Dan Streetman
aha:

ddstreet@lp1886128:~$ sudo iptables -n -t security -L OUTPUT
Chain OUTPUT (policy ACCEPT)
target prot opt source   destination 
ACCEPT tcp  --  0.0.0.0/0168.63.129.16owner UID match 0
DROP   tcp  --  0.0.0.0/0168.63.129.16ctstate 
INVALID,NEW


it seems like this is being added by walinuxagent:

Jul 13 16:21:15 lp1886128 python3[1298]: 2020/07/13 16:21:15.672132 INFO 
ExtHandler Successfully added Azure fabric firewall rules
Jul 13 16:21:15 lp1886128 python3[1298]: 2020/07/13 16:21:15.683188 INFO 
ExtHandler Firewall rules:
Jul 13 16:21:15 lp1886128 python3[1298]: Chain INPUT (policy ACCEPT 0 packets, 
0 bytes)
Jul 13 16:21:15 lp1886128 python3[1298]: pkts  bytes target prot 
opt in out source   destination
Jul 13 16:21:15 lp1886128 python3[1298]: Chain FORWARD (policy ACCEPT 0 
packets, 0 bytes)
Jul 13 16:21:15 lp1886128 python3[1298]: pkts  bytes target prot 
opt in out source   destination
Jul 13 16:21:15 lp1886128 python3[1298]: Chain OUTPUT (policy ACCEPT 0 packets, 
0 bytes)
Jul 13 16:21:15 lp1886128 python3[1298]: pkts  bytes target prot 
opt in out source   destination
Jul 13 16:21:15 lp1886128 python3[1298]:00 ACCEPT tcp  --  
*  *   0.0.0.0/0168.63.129.16owner UID match 0
Jul 13 16:21:15 lp1886128 python3[1298]:00 DROP   tcp  --  
*  *   0.0.0.0/0168.63.129.16ctstate INVALID,NEW


** Also affects: walinuxagent (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- systemd-resolved does not resolve address due to udp payload size.
+ walinuxagent blocks DNS fallback to TCP

** Changed in: systemd (Ubuntu)
   Status: In Progress => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1886128

Title:
  walinuxagent blocks DNS fallback to TCP

Status in systemd package in Ubuntu:
  Invalid
Status in walinuxagent package in Ubuntu:
  New

Bug description:
  [impact]

  on azure instances, walinuxagent blocks all (new) TCP connections to
  the azure nameserver, which prevents fallback to TCP DNS for truncated
  dns queries

  [test case]

  on an azure instance:

  ddstreet@lp1886128:~$ systemd-resolve --status | grep Servers
   DNS Servers: 168.63.129.16
  ddstreet@lp1886128:~$ dig +retries=0 +timeout=1 +short +tcp @168.63.129.16 
toomany100.ddstreet.org
  ;; connection timed out; no servers could be reached
  ;; Connection to 168.63.129.16#53(168.63.129.16) for toomany100.ddstreet.org 
failed: timed out.

  
  change the actual nameserver ip in the 'dig' command to match what resolved 
is configured with (which comes from dhcp)

  [regression potential]

  TBD

  [scope]

  TBD

  [original description]

  
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  systemd-resolve --version

  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
  +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN
  -PCRE2 default-hierarchy=hybrid

  We met an error: on an attempt to resolve address, the following issue
  appears:

  ; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> 
mharder-formrec.cognitiveservices.azure.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44096
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;mharder-formrec.cognitiveservices.azure.com. IN  A

  ;; Query time: 231 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Tue Apr 28 20:47:14 UTC 2020
  ;; MSG SIZE  rcvd: 72

  Let me provide you important notes about the issue:
  1) It's not reproducing on Ubuntu 16;
  2) Bypassing systemd-resolve - everything works fine;
  3) Only the difference between systemd-resolve and END is UDP_PAYLOAD_SIZE

  Successful query:

  113516:27:25.964386 10.1.0.4168.63.129.16   DNS 128
  Standard query 0xc2d4 A mharder-formrec.cognitiveservices.azure.com
  OPT

  Domain Name System (query)
  Transaction ID: 0xc2d4
  Flags: 0x0120 Standard query
  0...    = Response: Message is a query
  .000 0...   = Opcode: Standard query (0)
   ..0.   = Truncated: Message is not truncated
   ...1   = Recursion desired: Do query recursively
    .0..  = Z: reserved (0)
    ..1.  = AD bit: Set
    ...0  = Non-authenticated data: Unacceptable
  Questions: 1
  Answer RRs: 0
  Authority RRs: 0
  Additional RRs: 1
  Queries
  mharder-formrec.cognitiveservices.azure.com: type A, class IN
  

[Touch-packages] [Bug 1887407] Re: Distribution upgrade uninstalled TortoiseHG without asking me

2020-07-13 Thread Daniel Letzeisen
First off, some background about why TortoiseHG was removed and why the PPA 
disappeared:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939258
https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/5562

Second, the upgrade gives you a chance to see the details you want. You
were prompted with these screens, including the obsolete software
screen, correct?

 Screen 1 
Do you want to start the upgrade? 

36 installed packages are no longer supported by Canonical. You can 
still get support from the community. 

13 packages are going to be removed. 246 new packages are going to be 
installed. 1256 packages are going to be upgraded. 

You have to download a total of 810 M. This download will take about 
11 minutes with your connection. 

Installing the upgrade can take several hours. Once the download has 
finished, the process cannot be canceled. 

 Continue [yN]  Details [d]

- Screen 2 --
Searching for obsolete software
Reading state information... Done

Remove obsolete packages?

86 packages are going to be removed.

 Continue [yN]  Details [d]


Please be more specific about the exact changes you would like to see.

** Bug watch added: Debian Bug tracker #939258
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939258

** Bug watch added: foss.heptapod.net/mercurial/tortoisehg/thg/-/issues #5562
   https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/5562

** Changed in: apt (Ubuntu)
   Status: New => Incomplete

-- 
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/1887407

Title:
  Distribution upgrade uninstalled TortoiseHG without asking me

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  I had TortoiseHG installed on my computer
  https://tortoisehg.bitbucket.io/download/linux.html

  After upgrading from Ubuntu 16.04 to 18.04, then 19.10 and then 20.04
  (I can't tell at what stage), it's GONE.

  Never was I asked if I was fine with that.

  I don't care if there's a conflict of packages or whatever, you don't
  just uninstall software like that without asking me for confirmation.

  And yes, at some point I guess I clicked Yes to something like "2387
  packages will be installed, 8793 will be removed" or whatever. But if
  you are going to uninstall an application that I installed manually
  (as opposed to some library that I never chose to install), you have
  to give a very specific warning and prompt, one that I can't easily
  miss.

  This is OUTRAGEOUS. Now I wonder how many other programs, that I don't
  use that often (unlike THG with which I work on a daily basis) may be
  gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.2ubuntu0.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 13 17:55:51 2020
  InstallationDate: Installed on 2013-10-11 (2466 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1887407/+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 1886128] Re: systemd-resolved does not resolve address due to udp payload size.

2020-07-13 Thread Dan Streetman
To repro on azure instance:

ddstreet@lp1886128:~$ systemd-resolve --status | grep Servers
 DNS Servers: 168.63.129.16
ddstreet@lp1886128:~$ dig +retries=0 +timeout=1 +short +tcp @168.63.129.16 
toomany100.ddstreet.org
;; connection timed out; no servers could be reached
;; Connection to 168.63.129.16#53(168.63.129.16) for toomany100.ddstreet.org 
failed: timed out.


tcp does work with external dns servers, e.g.:

ddstreet@lp1886128:~$ dig +retries=0 +timeout=1 +short +tcp @8.8.8.8 
toomany100.ddstreet.org | head -5
10.254.201.0
10.254.201.1
10.254.201.18
10.254.201.19
10.254.201.2


note that the TCP packets to 168.63.129.16 do not make it out of the instance; 
they don't show up in the tcpdump at all, although TCP packets to 168.63.129.15 
or 168.63.129.17 *do* show up.  So there is something specific to that ip 
address that's causing TCP packets to get lost inside the instance.

-- 
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/1886128

Title:
  systemd-resolved does not resolve address due to udp payload size.

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  systemd-resolve --version

  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
  +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN
  -PCRE2 default-hierarchy=hybrid

  We met an error: on an attempt to resolve address, the following issue
  appears:

  ; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> 
mharder-formrec.cognitiveservices.azure.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44096
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;mharder-formrec.cognitiveservices.azure.com. IN  A

  ;; Query time: 231 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Tue Apr 28 20:47:14 UTC 2020
  ;; MSG SIZE  rcvd: 72

  Let me provide you important notes about the issue:
  1) It's not reproducing on Ubuntu 16;
  2) Bypassing systemd-resolve - everything works fine;
  3) Only the difference between systemd-resolve and END is UDP_PAYLOAD_SIZE

  Successful query:

  113516:27:25.964386 10.1.0.4168.63.129.16   DNS 128
  Standard query 0xc2d4 A mharder-formrec.cognitiveservices.azure.com
  OPT

  Domain Name System (query)
  Transaction ID: 0xc2d4
  Flags: 0x0120 Standard query
  0...    = Response: Message is a query
  .000 0...   = Opcode: Standard query (0)
   ..0.   = Truncated: Message is not truncated
   ...1   = Recursion desired: Do query recursively
    .0..  = Z: reserved (0)
    ..1.  = AD bit: Set
    ...0  = Non-authenticated data: Unacceptable
  Questions: 1
  Answer RRs: 0
  Authority RRs: 0
  Additional RRs: 1
  Queries
  mharder-formrec.cognitiveservices.azure.com: type A, class IN
  Additional records
  : type OPT
  Name: 
  Type: OPT (41)
  UDP payload size: 4096
  Higher bits in extended RCODE: 0x00
  EDNS0 version: 0
  Z: 0x
  0...    = DO bit: Cannot handle DNSSEC security 
RRs
  .000    = Reserved: 0x
  Data length: 12
  Option: COOKIE
  Unsuccessful query:

  112816:27:25.713886 10.1.0.4168.63.129.16   DNS 116
  Standard query 0x198d A mharder-formrec.cognitiveservices.azure.com
  OPT

  Domain Name System (query)
  Transaction ID: 0x198d
  Flags: 0x0100 Standard query
  0...    = Response: Message is a query
  .000 0...   = Opcode: Standard query (0)
   ..0.   = Truncated: Message is not truncated
   ...1   = Recursion desired: Do query recursively
    .0..  = Z: reserved (0)
    ...0  = Non-authenticated data: Unacceptable
  Questions: 1
  Answer RRs: 0
  Authority RRs: 0
  Additional RRs: 1
  Queries
  mharder-formrec.cognitiveservices.azure.com: type A, class IN
  Additional records
  : type OPT
  Name: 
  Type: OPT (41)
  UDP payload size: 512
  Higher bits in extended RCODE: 0x00
  EDNS0 version: 0
  Z: 0x
  0...    = DO bit: Cannot handle DNSSEC security 
RRs
  .000    = Reserved: 0x
  Data length: 0
  Notable difference:

  Success:
  UDP payload size: 4096

  Failure:
  UDP payload size: 

[Touch-packages] [Bug 1886128] Re: systemd-resolved does not resolve address due to udp payload size.

2020-07-13 Thread Dan Streetman
I spun up an azure instance and tested, and indeed tcp port 53 appears
completely missing from any tcpdump, but only for packets sent to the
upstream nameserver.  TCP sent to port 53 on *any* other ip address does
make it out, but tcp port 53 to the nameserver does not. There are no
routing rules or ip routes or iptables I could find that might be
blocking the packets, so I'm not sure why the packets aren't being sent
out, but that's the cause of the failure here to fallback to TCP DNS.

So 1) we do need to fix upstream systemd to use >512 byte edns0 udp with
upstream nameservers, and also 2) something is wrong with the azure
instances that is blocking TCP DNS to the upstream nameserver.

-- 
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/1886128

Title:
  systemd-resolved does not resolve address due to udp payload size.

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  systemd-resolve --version

  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
  +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN
  -PCRE2 default-hierarchy=hybrid

  We met an error: on an attempt to resolve address, the following issue
  appears:

  ; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> 
mharder-formrec.cognitiveservices.azure.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44096
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;mharder-formrec.cognitiveservices.azure.com. IN  A

  ;; Query time: 231 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Tue Apr 28 20:47:14 UTC 2020
  ;; MSG SIZE  rcvd: 72

  Let me provide you important notes about the issue:
  1) It's not reproducing on Ubuntu 16;
  2) Bypassing systemd-resolve - everything works fine;
  3) Only the difference between systemd-resolve and END is UDP_PAYLOAD_SIZE

  Successful query:

  113516:27:25.964386 10.1.0.4168.63.129.16   DNS 128
  Standard query 0xc2d4 A mharder-formrec.cognitiveservices.azure.com
  OPT

  Domain Name System (query)
  Transaction ID: 0xc2d4
  Flags: 0x0120 Standard query
  0...    = Response: Message is a query
  .000 0...   = Opcode: Standard query (0)
   ..0.   = Truncated: Message is not truncated
   ...1   = Recursion desired: Do query recursively
    .0..  = Z: reserved (0)
    ..1.  = AD bit: Set
    ...0  = Non-authenticated data: Unacceptable
  Questions: 1
  Answer RRs: 0
  Authority RRs: 0
  Additional RRs: 1
  Queries
  mharder-formrec.cognitiveservices.azure.com: type A, class IN
  Additional records
  : type OPT
  Name: 
  Type: OPT (41)
  UDP payload size: 4096
  Higher bits in extended RCODE: 0x00
  EDNS0 version: 0
  Z: 0x
  0...    = DO bit: Cannot handle DNSSEC security 
RRs
  .000    = Reserved: 0x
  Data length: 12
  Option: COOKIE
  Unsuccessful query:

  112816:27:25.713886 10.1.0.4168.63.129.16   DNS 116
  Standard query 0x198d A mharder-formrec.cognitiveservices.azure.com
  OPT

  Domain Name System (query)
  Transaction ID: 0x198d
  Flags: 0x0100 Standard query
  0...    = Response: Message is a query
  .000 0...   = Opcode: Standard query (0)
   ..0.   = Truncated: Message is not truncated
   ...1   = Recursion desired: Do query recursively
    .0..  = Z: reserved (0)
    ...0  = Non-authenticated data: Unacceptable
  Questions: 1
  Answer RRs: 0
  Authority RRs: 0
  Additional RRs: 1
  Queries
  mharder-formrec.cognitiveservices.azure.com: type A, class IN
  Additional records
  : type OPT
  Name: 
  Type: OPT (41)
  UDP payload size: 512
  Higher bits in extended RCODE: 0x00
  EDNS0 version: 0
  Z: 0x
  0...    = DO bit: Cannot handle DNSSEC security 
RRs
  .000    = Reserved: 0x
  Data length: 0
  Notable difference:

  Success:
  UDP payload size: 4096

  Failure:
  UDP payload size: 512
  And notable differences in the responses:

  Success:
  Flags: 0x8180 Standard query response, No error
   ..0.   = Truncated: Message is not truncated

  Failure:
  Flags: 

[Touch-packages] [Bug 1799580] Re: Settings made by qasmixer are lost on next reboot

2020-07-13 Thread Erich Eickmeyer
I don't believe this is a bug with qastools since it simply tells alsa
what to do. Also, the issue can be duplicated on alsamixer. qasmixer
itself doesn't save anything, neither does alsamixer. Something
somewhere isn't remembering between reboots, but it's definitely not
qastools related.

** Also affects: alsa-utils (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: alsa-utils (Ubuntu)
   Status: New => Confirmed

** No longer affects: qastools (Ubuntu)

** Changed in: alsa-utils (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1799580

Title:
  Settings made by qasmixer are lost on next reboot

Status in alsa-utils package in Ubuntu:
  Confirmed

Bug description:
  I use qasmixer to set the "Synth" volume to full, on my SoundBlaster
  Live sound-card.

  On prior levels of Ubuntu (through 18.04), any settings I make are
  preserved over reboots.

  On the latest level of Ubuntu (18.10) the settings are effective only
  as long as the system is running.  The next time I reboot, the
  settings are gone, and I have to use qasmixer to set them all over
  again.

  I expected the settings made by qasmixer to be preserved on the next
  reboot, as with past levels of Ubuntu.

  The settings made by qasmixer are not preserved over a reboot on
  Ubuntu 18.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: qasmixer 0.21.0-1.1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic i686
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: i386
  CurrentDesktop: LXQt
  Date: Tue Oct 23 14:59:06 2018
  InstallationDate: Installed on 2018-10-23 (0 days ago)
  InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release i386 
(20181017.2)
  SourcePackage: qastools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1799580/+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 1671951] Re: networkd should allow configuring IPV6 MTU

2020-07-13 Thread Dan Watkins
I'm trying to understand if there is any work still required on this bug
for cloud-init.  I've tested two network configurations (in lxd
containers).  The first:

  version: 2
  ethernets:
eth0:
  dhcp4: true
  dhcp6: true
  ipv6-mtu: 1337

As this is just a passthrough to netplan, this works as expected:
/proc/sys/net/ipv6/conf/eth0/mtu is 1337, /sys/class/net/eth0/mtu is
1500.

The second:

  version: 1
  config:
  - type: physical
name: eth0
mtu: 1337
subnets:
- type: dhcp
- type: dhcp6

Given that we don't have a separate setting for the IPv6-specific MTU,
this seems to work as I expect: both /proc/sys/net/ipv6/conf/eth0/mtu
and /sys/class/net/eth0/mtu are set to 1337.  I'm not sure, however,
that this is a sufficient test, or if my expectations are correct.

Thoughts, anyone?

-- 
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/1671951

Title:
  networkd should allow configuring IPV6 MTU

Status in systemd:
  Unknown
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in cloud-init source package in Disco:
  Won't Fix
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Won't Fix
Status in cloud-init source package in Eoan:
  New
Status in netplan.io source package in Eoan:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released
Status in cloud-init source package in Focal:
  Confirmed
Status in netplan.io source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  = netplan.io =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]
   * Apply a netplan configuration that specifices ipv6-mtu:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 6000

   * Check that MTU bytes, is at least IPv6MTUBytes on the interface:

  $ sysctl net.ipv6.conf.eth0.mtu
  net.ipv6.conf.eth0.mtu = 6000

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of netplan.io =

  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of systemd =

  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  Some context from those discussions

  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel 

[Touch-packages] [Bug 1861177] Autopkgtest regression report (libseccomp/2.4.3-1ubuntu3.19.10.3)

2020-07-13 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted libseccomp (2.4.3-1ubuntu3.19.10.3) for 
eoan have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/242-7ubuntu3.11 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#libseccomp

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1861177

Title:
  seccomp_rule_add is very slow

Status in snapd:
  Invalid
Status in libseccomp package in Ubuntu:
  In Progress
Status in libseccomp source package in Xenial:
  Fix Committed
Status in libseccomp source package in Bionic:
  Fix Committed
Status in libseccomp source package in Eoan:
  Fix Committed
Status in libseccomp source package in Focal:
  Fix Committed
Status in libseccomp source package in Groovy:
  In Progress

Bug description:
  [IMPACT]
  There is a known and patched issue with version 2.4 of libseccomp where 
certain operations have a large performance regression. This is causing some 
packages that use libseccomp such as container orchestration systems to 
occasionally time out or otherwise fail under certain workloads.

  Please consider porting the patch into the various Ubuntu versions
  that have version 2.4 of libseccomp and into the backports. The
  performance patch from version 2.5 (yet to be released) applies
  cleanly on top of the 2.4 branch of libseccomp.

  For more information, and for a copy of the patch (which can also be
  cherry picked from the upstream libseccomp repos) see the similar
  Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913

  Upstream issue : https://github.com/seccomp/libseccomp/issues/153
  Upstream fix : https://github.com/seccomp/libseccomp/pull/180/

  [Test Case]

  For this test case we use Docker on Ubuntu Groovy (20.10) :

  --> Current libseccomp version
  #dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu3 
 amd64high level interface to Linux seccomp filter

  ## pull ubuntu image
  # docker pull ubuntu
  ## create a container
  # docker run --name test_seccomp -it 74435f89ab78 /bin/bash

  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m10,319s
  user  0m0,018s
  sys   0m0,033s

  
  --> Patched libseccomp version

  # dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu4 
 amd64high level interface to Linux seccomp filter

  # docker start test_seccomp
  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m3,650s
  user  0m0,025s
  sys   0m0,028s

  [Regression Potential]

  The first of the 2 patches cleans up the code that adds rules to a
  single filter without changing the logic of the code. The second patch
  introduces the idea of shadow transactions. On a successful
  transaction commit the old transaction checkpoint is preserved and is
  brought up to date with the current filter. The next time a new
  transaction starts, it checks is the a shadow transaction exist and if
  so the shadow is used instead of creating a new checkpoint from
  scratch [1]. This is the patch that mitigates the performance
  regression. Any potential regression will involve the parts of the
  code that add rules to filters and/or the code that creates and checks
  the shadow transactions.

  
  [Other]

  Affected releases : Groovy, Focal, Eoan, Bionic, Xenial.

  [1]
  
https://github.com/seccomp/libseccomp/pull/180/commits/bc3a6c0453b0350ee43e4925482f705a2fbf5a4d

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1861177/+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 1887407] [NEW] Distribution upgrade uninstalled TortoiseHG without asking me

2020-07-13 Thread teo1978
Public bug reported:

I had TortoiseHG installed on my computer
https://tortoisehg.bitbucket.io/download/linux.html

After upgrading from Ubuntu 16.04 to 18.04, then 19.10 and then 20.04 (I
can't tell at what stage), it's GONE.

Never was I asked if I was fine with that.

I don't care if there's a conflict of packages or whatever, you don't
just uninstall software like that without asking me for confirmation.

And yes, at some point I guess I clicked Yes to something like "2387
packages will be installed, 8793 will be removed" or whatever. But if
you are going to uninstall an application that I installed manually (as
opposed to some library that I never chose to install), you have to give
a very specific warning and prompt, one that I can't easily miss.

This is OUTRAGEOUS. Now I wonder how many other programs, that I don't
use that often (unlike THG with which I work on a daily basis) may be
gone.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: apt 2.0.2ubuntu0.1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 13 17:55:51 2020
InstallationDate: Installed on 2013-10-11 (2466 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: apt
UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago)

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages

-- 
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/1887407

Title:
  Distribution upgrade uninstalled TortoiseHG without asking me

Status in apt package in Ubuntu:
  New

Bug description:
  I had TortoiseHG installed on my computer
  https://tortoisehg.bitbucket.io/download/linux.html

  After upgrading from Ubuntu 16.04 to 18.04, then 19.10 and then 20.04
  (I can't tell at what stage), it's GONE.

  Never was I asked if I was fine with that.

  I don't care if there's a conflict of packages or whatever, you don't
  just uninstall software like that without asking me for confirmation.

  And yes, at some point I guess I clicked Yes to something like "2387
  packages will be installed, 8793 will be removed" or whatever. But if
  you are going to uninstall an application that I installed manually
  (as opposed to some library that I never chose to install), you have
  to give a very specific warning and prompt, one that I can't easily
  miss.

  This is OUTRAGEOUS. Now I wonder how many other programs, that I don't
  use that often (unlike THG with which I work on a daily basis) may be
  gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.2ubuntu0.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 13 17:55:51 2020
  InstallationDate: Installed on 2013-10-11 (2466 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1887407/+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 1887404] [NEW] the information was send by the system

2020-07-13 Thread Manoel
Public bug reported:

the information was send by the system

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18
Uname: Linux 4.15.0-109-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CompositorRunning: None
Date: Mon Jul 13 12:42:26 2020
DistUpgraded: 2019-01-28 11:28:31,005 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 620 [1028:0782]
   Subsystem: Dell GM108M [GeForce 940MX] [1028:0782]
InstallationDate: Installed on 2018-05-07 (798 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. Inspiron 7560
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-109-generic 
root=UUID=21d7010c-b6c8-41b7-a8fc-3e0dfe929d16 ro nopat vesafb.invalid=1 
drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2019-01-28 (532 days ago)
dmi.bios.date: 07/19/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.6
dmi.board.name: 09WC1G
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.6:bd07/19/2017:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn09WC1G:rvrA01:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7560
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Jan 28 09:06:38 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1716 
 vendor BOE
xserver.version: 2:1.18.4-0ubuntu0.8

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic 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/1887404

Title:
  the information was send by the system

Status in xorg package in Ubuntu:
  New

Bug description:
  the information was send by the system

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18
  Uname: Linux 4.15.0-109-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Jul 13 12:42:26 2020
  DistUpgraded: 2019-01-28 11:28:31,005 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:0782]
 Subsystem: Dell GM108M [GeForce 940MX] [1028:0782]
  InstallationDate: Installed on 2018-05-07 (798 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 7560
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-109-generic 
root=UUID=21d7010c-b6c8-41b7-a8fc-3e0dfe929d16 ro nopat vesafb.invalid=1 
drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-01-28 (532 days ago)
  dmi.bios.date: 07/19/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.6
  dmi.board.name: 09WC1G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.6:bd07/19/2017:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn09WC1G:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7560
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 

[Touch-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)

2020-07-13 Thread Kai-Heng Feng
What's the resolution and refresh rate picked under Windows?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri 

[Touch-packages] [Bug 1887397] Re: perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1

2020-07-13 Thread Andrea Righi
** Attachment added: "perf object files / build tree"
   
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1887397/+attachment/5392329/+files/perf-build-fail.tar.gz

-- 
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/1887397

Title:
  perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1

Status in binutils package in Ubuntu:
  New
Status in binutils source package in Groovy:
  New

Bug description:
  After updating to binutils 2.34.90.20200706-1ubuntu1 Linux' perf build
  is failing with the following error:

  
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 ignoring invalid character `@' in script
  
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 ignoring invalid character `@' in script
  
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 syntax error in dynamic list
  collect2: error: ld returned 1 exit status

  The file mentioned in the error (libtraceevent-dynamic-list) contains
  some '@' that ld doesn't seem to like:

  $ cat lib/traceevent/plugins/libtraceevent-dynamic-list
  {
  __stack_chk_fail@@GLIBC_2.4;
  free@@GLIBC_2.2.5;
  memset@@GLIBC_2.2.5;
  realloc@@GLIBC_2.2.5;
  sprintf@@GLIBC_2.2.5;
  strcmp@@GLIBC_2.2.5;
  strdup@@GLIBC_2.2.5;
  strncmp@@GLIBC_2.2.5;
  tep_find_any_field;
  tep_find_field;
  tep_find_function;
  tep_find_function_address;
  tep_get_field_raw;
  tep_get_field_val;
  tep_is_file_bigendian;
  tep_is_local_bigendian;
  tep_plugin_add_options;
  tep_plugin_remove_options;
  tep_print_func_field;
  tep_print_num_field;
  tep_read_number_field;
  tep_register_comm;
  tep_register_event_handler;
  tep_register_print_function;
  tep_unregister_event_handler;
  tep_unregister_print_function;
  trace_seq_printf;
  trace_seq_putc;
  trace_seq_puts;
  trace_seq_terminate;
  warning;
  };

  The same file generated in a Focal environment (w/ binutils
  2.34-6ubuntu1) looks as following:

  $ cat lib/traceevent/plugins/libtraceevent-dynamic-list
  {
  __stack_chk_fail;
  free;
  memset;
  realloc;
  sprintf;
  strcmp;
  strdup;
  strncmp;
  tep_find_any_field;
  tep_find_field;
  tep_find_function;
  tep_find_function_address;
  tep_get_field_raw;
  tep_get_field_val;
  tep_is_file_bigendian;
  tep_is_local_bigendian;
  tep_plugin_add_options;
  tep_plugin_remove_options;
  tep_print_func_field;
  tep_print_num_field;
  tep_read_number_field;
  tep_register_comm;
  tep_register_event_handler;
  tep_register_print_function;
  tep_unregister_event_handler;
  tep_unregister_print_function;
  trace_seq_printf;
  trace_seq_putc;
  trace_seq_puts;
  trace_seq_terminate;
  warning;
  };

  And here is the chunk of Makefile that is generating this file:

  define do_generate_dynamic_list_file
  symbol_type=`$(NM) -u -D $1 | awk 'NF>1 {print $$1}' | \
  xargs echo "U w W" | tr 'w ' 'W\n' | sort -u | xargs echo`;\
  if [ "$$symbol_type" = "U W" ];then \
  (echo '{';  \
  $(NM) -u -D $1 | awk 'NF>1 {print "\t"$$2";"}' | sort -u;\
  echo '};';  \
  ) > $2; \
  else\
  (echo Either missing one of [$1] or bad version of $(NM)) 
1>&2;\
  fi

  My guess is that something changed in the output of `nm` to show the @
  charaters that ld does not like.

  This problem is currently breaking all kernel builds in Groovy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1887397/+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 1887397] Re: perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1

2020-07-13 Thread Andrea Righi
Adding the specific command that is reporting error:

gcc  -Wbad-function-cast -Wdeclaration-after-statement -Wformat-security 
-Wformat-y2k -Winit-self -Wmissing-declarations -Wmissing-prototypes 
-Wnested-externs -Wno-system-headers -Wold-style-definition -Wpacked 
-Wredundant-decls -Wstrict-prototypes -Wswitch-default -Wswitch-enum -Wundef 
-Wwrite-strings -Wformat -Wstrict-aliasing=3 -Wshadow 
-DHAVE_ARCH_X86_64_SUPPORT -Iarch/x86/include/generated 
-DHAVE_SYSCALL_TABLE_SUPPORT -DHAVE_PERF_REGS_SUPPORT 
-DHAVE_ARCH_REGS_QUERY_REGISTER_OFFSET -Werror -O6 -fno-omit-frame-pointer 
-ggdb3 -funwind-tables -Wall -Wextra -std=gnu99 -fstack-protector-all 
-D_FORTIFY_SOURCE=2 
-I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/perf/lib/include 
-I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/perf/util/include 
-I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/perf/arch/x86/include
 -I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/include/ 
-I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/arch/x86/include/uapi
 -I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/include/uapi 
-I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/arch/x86/include/ 
-I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/arch/x86/ 
-I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/perf/util 
-I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/perf 
-I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/lib/ 
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE 
-DHAVE_SYNC_COMPARE_AND_SWAP_SUPPORT -DHAVE_PTHREAD_ATTR_SETAFFINITY_NP 
-DHAVE_PTHREAD_BARRIER -DHAVE_EVENTFD -DHAVE_GET_CURRENT_DIR_NAME -DHAVE_GETTID 
-DHAVE_DWARF_GETLOCATIONS_SUPPORT -DHAVE_GLIBC_SUPPORT -DHAVE_AIO_SUPPORT 
-DHAVE_SCHED_GETCPU_SUPPORT -DHAVE_SETNS_SUPPORT -DHAVE_LIBELF_SUPPORT 
-DHAVE_LIBELF_MMAP_SUPPORT -DHAVE_ELF_GETPHDRNUM_SUPPORT 
-DHAVE_GELF_GETNOTE_SUPPORT -DHAVE_ELF_GETSHDRSTRNDX_SUPPORT 
-DHAVE_DWARF_SUPPORT  -DHAVE_LIBBPF_SUPPORT -DHAVE_BPF_PROLOGUE -DHAVE_JITDUMP 
-DHAVE_DWARF_UNWIND_SUPPORT -DNO_LIBUNWIND_DEBUG_FRAME -DHAVE_LIBUNWIND_SUPPORT 
-DHAVE_LIBCRYPTO_SUPPORT -DHAVE_SLANG_SUPPORT -DNO_LIBPERL 
-DHAVE_TIMERFD_SUPPORT -DNO_LIBPYTHON -DHAVE_CPLUS_DEMANGLE_SUPPORT 
-DHAVE_ZLIB_SUPPORT -DHAVE_LZMA_SUPPORT -DHAVE_LIBCAP_SUPPORT 
-DHAVE_BACKTRACE_SUPPORT -DHAVE_LIBNUMA_SUPPORT -DHAVE_KVM_STAT_SUPPORT 
-DHAVE_AUXTRACE_SUPPORT -DHAVE_JVMTI_CMLR -Wl,-z,noexecstack  -lunwind-x86_64 
-lunwind -llzma  -Xlinker 
--dynamic-list=/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/lib/traceevent/plugins/libtraceevent-dynamic-list
 \
perf-in.o pmu-events/pmu-events-in.o -Wl,--whole-archive 
/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/lib/api/libapi.a 
/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/lib/traceevent/libtraceevent.a
 
/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/lib/subcmd/libsubcmd.a
 /home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/perf/lib/libperf.a 
/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/lib/bpf/libbpf.a  
-Wl,--no-whole-archive -Wl,--start-group -lpthread -lrt -lm -ldl -lelf -ldw 
-lunwind-x86_64 -lunwind -llzma -lcrypto -lslang -liberty -lz -llzma -lcap 
-lnuma -Wl,--end-group -o perf

-- 
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/1887397

Title:
  perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1

Status in binutils package in Ubuntu:
  New
Status in binutils source package in Groovy:
  New

Bug description:
  After updating to binutils 2.34.90.20200706-1ubuntu1 Linux' perf build
  is failing with the following error:

  
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 ignoring invalid character `@' in script
  
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 ignoring invalid character `@' in script
  
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 syntax error in dynamic list
  collect2: error: ld returned 1 exit status

  The file mentioned in the error (libtraceevent-dynamic-list) contains
  some '@' that ld doesn't seem to like:

  $ cat lib/traceevent/plugins/libtraceevent-dynamic-list
  {
  __stack_chk_fail@@GLIBC_2.4;
  free@@GLIBC_2.2.5;
  memset@@GLIBC_2.2.5;
  realloc@@GLIBC_2.2.5;
  sprintf@@GLIBC_2.2.5;
  strcmp@@GLIBC_2.2.5;
  strdup@@GLIBC_2.2.5;
  strncmp@@GLIBC_2.2.5;
  tep_find_any_field;
  tep_find_field;
  tep_find_function;
  tep_find_function_address;
  tep_get_field_raw;
  tep_get_field_val;
  tep_is_file_bigendian;
 

[Touch-packages] [Bug 1886128] Re: systemd-resolved does not resolve address due to udp payload size.

2020-07-13 Thread Chad Kimes
Azure DNS does support DNS over TCP. Looking through a separate packet
capture I had taken during investigating this issue, I don't see any
attempts by resolved to open a TCP connection to port 53 of the DNS
server (in fact, I don't see any use of TCP port 53 at all).

Wireshark filters used:

udp.port == 53 or tcp.port == 53 (shows all DNS traffic)
tcp.port == 53 (shows nothing)

-- 
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/1886128

Title:
  systemd-resolved does not resolve address due to udp payload size.

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  systemd-resolve --version

  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
  +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN
  -PCRE2 default-hierarchy=hybrid

  We met an error: on an attempt to resolve address, the following issue
  appears:

  ; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> 
mharder-formrec.cognitiveservices.azure.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44096
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;mharder-formrec.cognitiveservices.azure.com. IN  A

  ;; Query time: 231 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Tue Apr 28 20:47:14 UTC 2020
  ;; MSG SIZE  rcvd: 72

  Let me provide you important notes about the issue:
  1) It's not reproducing on Ubuntu 16;
  2) Bypassing systemd-resolve - everything works fine;
  3) Only the difference between systemd-resolve and END is UDP_PAYLOAD_SIZE

  Successful query:

  113516:27:25.964386 10.1.0.4168.63.129.16   DNS 128
  Standard query 0xc2d4 A mharder-formrec.cognitiveservices.azure.com
  OPT

  Domain Name System (query)
  Transaction ID: 0xc2d4
  Flags: 0x0120 Standard query
  0...    = Response: Message is a query
  .000 0...   = Opcode: Standard query (0)
   ..0.   = Truncated: Message is not truncated
   ...1   = Recursion desired: Do query recursively
    .0..  = Z: reserved (0)
    ..1.  = AD bit: Set
    ...0  = Non-authenticated data: Unacceptable
  Questions: 1
  Answer RRs: 0
  Authority RRs: 0
  Additional RRs: 1
  Queries
  mharder-formrec.cognitiveservices.azure.com: type A, class IN
  Additional records
  : type OPT
  Name: 
  Type: OPT (41)
  UDP payload size: 4096
  Higher bits in extended RCODE: 0x00
  EDNS0 version: 0
  Z: 0x
  0...    = DO bit: Cannot handle DNSSEC security 
RRs
  .000    = Reserved: 0x
  Data length: 12
  Option: COOKIE
  Unsuccessful query:

  112816:27:25.713886 10.1.0.4168.63.129.16   DNS 116
  Standard query 0x198d A mharder-formrec.cognitiveservices.azure.com
  OPT

  Domain Name System (query)
  Transaction ID: 0x198d
  Flags: 0x0100 Standard query
  0...    = Response: Message is a query
  .000 0...   = Opcode: Standard query (0)
   ..0.   = Truncated: Message is not truncated
   ...1   = Recursion desired: Do query recursively
    .0..  = Z: reserved (0)
    ...0  = Non-authenticated data: Unacceptable
  Questions: 1
  Answer RRs: 0
  Authority RRs: 0
  Additional RRs: 1
  Queries
  mharder-formrec.cognitiveservices.azure.com: type A, class IN
  Additional records
  : type OPT
  Name: 
  Type: OPT (41)
  UDP payload size: 512
  Higher bits in extended RCODE: 0x00
  EDNS0 version: 0
  Z: 0x
  0...    = DO bit: Cannot handle DNSSEC security 
RRs
  .000    = Reserved: 0x
  Data length: 0
  Notable difference:

  Success:
  UDP payload size: 4096

  Failure:
  UDP payload size: 512
  And notable differences in the responses:

  Success:
  Flags: 0x8180 Standard query response, No error
   ..0.   = Truncated: Message is not truncated

  Failure:
  Flags: 0x8380 Standard query response, No error
   ..1.   = Truncated: Message is truncated

  Interestingly, systemd-resolved is setting the maximum payload size to 512 
regardless of whether EDNS0 is configured and regardless of what is sent to it 
for the payload size.
  I tried to found a way to 

[Touch-packages] [Bug 1887397] [NEW] perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1

2020-07-13 Thread Andrea Righi
Public bug reported:

After updating to binutils 2.34.90.20200706-1ubuntu1 Linux' perf build
is failing with the following error:

/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 ignoring invalid character `@' in script
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 ignoring invalid character `@' in script
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 syntax error in dynamic list
collect2: error: ld returned 1 exit status

The file mentioned in the error (libtraceevent-dynamic-list) contains
some '@' that ld doesn't seem to like:

$ cat lib/traceevent/plugins/libtraceevent-dynamic-list
{
__stack_chk_fail@@GLIBC_2.4;
free@@GLIBC_2.2.5;
memset@@GLIBC_2.2.5;
realloc@@GLIBC_2.2.5;
sprintf@@GLIBC_2.2.5;
strcmp@@GLIBC_2.2.5;
strdup@@GLIBC_2.2.5;
strncmp@@GLIBC_2.2.5;
tep_find_any_field;
tep_find_field;
tep_find_function;
tep_find_function_address;
tep_get_field_raw;
tep_get_field_val;
tep_is_file_bigendian;
tep_is_local_bigendian;
tep_plugin_add_options;
tep_plugin_remove_options;
tep_print_func_field;
tep_print_num_field;
tep_read_number_field;
tep_register_comm;
tep_register_event_handler;
tep_register_print_function;
tep_unregister_event_handler;
tep_unregister_print_function;
trace_seq_printf;
trace_seq_putc;
trace_seq_puts;
trace_seq_terminate;
warning;
};

The same file generated in a Focal environment (w/ binutils
2.34-6ubuntu1) looks as following:

$ cat lib/traceevent/plugins/libtraceevent-dynamic-list
{
__stack_chk_fail;
free;
memset;
realloc;
sprintf;
strcmp;
strdup;
strncmp;
tep_find_any_field;
tep_find_field;
tep_find_function;
tep_find_function_address;
tep_get_field_raw;
tep_get_field_val;
tep_is_file_bigendian;
tep_is_local_bigendian;
tep_plugin_add_options;
tep_plugin_remove_options;
tep_print_func_field;
tep_print_num_field;
tep_read_number_field;
tep_register_comm;
tep_register_event_handler;
tep_register_print_function;
tep_unregister_event_handler;
tep_unregister_print_function;
trace_seq_printf;
trace_seq_putc;
trace_seq_puts;
trace_seq_terminate;
warning;
};

And here is the chunk of Makefile that is generating this file:

define do_generate_dynamic_list_file
symbol_type=`$(NM) -u -D $1 | awk 'NF>1 {print $$1}' | \
xargs echo "U w W" | tr 'w ' 'W\n' | sort -u | xargs echo`;\
if [ "$$symbol_type" = "U W" ];then \
(echo '{';  \
$(NM) -u -D $1 | awk 'NF>1 {print "\t"$$2";"}' | sort -u;\
echo '};';  \
) > $2; \
else\
(echo Either missing one of [$1] or bad version of $(NM)) 1>&2;\
fi

My guess is that something changed in the output of `nm` to show the @
charaters that ld does not like.

This problem is currently breaking all kernel builds in Groovy.

** Affects: binutils (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: binutils (Ubuntu Groovy)
 Importance: Undecided
 Status: New

** Also affects: binutils (Ubuntu Groovy)
   Importance: Undecided
   Status: New

-- 
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/1887397

Title:
  perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1

Status in binutils package in Ubuntu:
  New
Status in binutils source package in Groovy:
  New

Bug description:
  After updating to binutils 2.34.90.20200706-1ubuntu1 Linux' perf build
  is failing with the following error:

  
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 ignoring invalid character `@' in script
  
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 ignoring invalid character `@' in script
  
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 syntax error in dynamic 

[Touch-packages] [Bug 1861177] Re: seccomp_rule_add is very slow

2020-07-13 Thread Łukasz Zemczak
Hello Sam, or anyone else affected,

Accepted libseccomp into eoan-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libseccomp/2.4.3-1ubuntu3.19.10.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
eoan to verification-done-eoan. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-eoan. In either case, without details of your testing we will not
be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: libseccomp (Ubuntu Eoan)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-eoan

** Changed in: libseccomp (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1861177

Title:
  seccomp_rule_add is very slow

Status in snapd:
  Invalid
Status in libseccomp package in Ubuntu:
  In Progress
Status in libseccomp source package in Xenial:
  Fix Committed
Status in libseccomp source package in Bionic:
  Fix Committed
Status in libseccomp source package in Eoan:
  Fix Committed
Status in libseccomp source package in Focal:
  Fix Committed
Status in libseccomp source package in Groovy:
  In Progress

Bug description:
  [IMPACT]
  There is a known and patched issue with version 2.4 of libseccomp where 
certain operations have a large performance regression. This is causing some 
packages that use libseccomp such as container orchestration systems to 
occasionally time out or otherwise fail under certain workloads.

  Please consider porting the patch into the various Ubuntu versions
  that have version 2.4 of libseccomp and into the backports. The
  performance patch from version 2.5 (yet to be released) applies
  cleanly on top of the 2.4 branch of libseccomp.

  For more information, and for a copy of the patch (which can also be
  cherry picked from the upstream libseccomp repos) see the similar
  Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913

  Upstream issue : https://github.com/seccomp/libseccomp/issues/153
  Upstream fix : https://github.com/seccomp/libseccomp/pull/180/

  [Test Case]

  For this test case we use Docker on Ubuntu Groovy (20.10) :

  --> Current libseccomp version
  #dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu3 
 amd64high level interface to Linux seccomp filter

  ## pull ubuntu image
  # docker pull ubuntu
  ## create a container
  # docker run --name test_seccomp -it 74435f89ab78 /bin/bash

  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m10,319s
  user  0m0,018s
  sys   0m0,033s

  
  --> Patched libseccomp version

  # dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu4 
 amd64high level interface to Linux seccomp filter

  # docker start test_seccomp
  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m3,650s
  user  0m0,025s
  sys   0m0,028s

  [Regression Potential]

  The first of the 2 patches cleans up the code that adds rules to a
  single filter without changing the logic of the code. The second patch
  introduces the idea of shadow transactions. On a successful
  transaction commit the old transaction checkpoint is preserved and is
  brought up to date with the current filter. The next time a new
  transaction starts, it checks is the a shadow transaction exist and if
  so the shadow is used instead of creating a new checkpoint from
  scratch [1]. This is the patch that mitigates the performance
  regression. Any potential regression will involve the parts of the
  code that add rules to filters and/or the code that creates and checks
  the shadow transactions.

  
  [Other]

  Affected releases : Groovy, Focal, Eoan, Bionic, Xenial.

  [1]
  
https://github.com/seccomp/libseccomp/pull/180/commits/bc3a6c0453b0350ee43e4925482f705a2fbf5a4d

To manage notifications 

[Touch-packages] [Bug 1861177] Please test proposed package

2020-07-13 Thread Łukasz Zemczak
Hello Sam, or anyone else affected,

Accepted libseccomp into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libseccomp/2.4.3-1ubuntu3.16.04.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
xenial to verification-done-xenial. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-xenial. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1861177

Title:
  seccomp_rule_add is very slow

Status in snapd:
  Invalid
Status in libseccomp package in Ubuntu:
  In Progress
Status in libseccomp source package in Xenial:
  Fix Committed
Status in libseccomp source package in Bionic:
  Fix Committed
Status in libseccomp source package in Eoan:
  Fix Committed
Status in libseccomp source package in Focal:
  Fix Committed
Status in libseccomp source package in Groovy:
  In Progress

Bug description:
  [IMPACT]
  There is a known and patched issue with version 2.4 of libseccomp where 
certain operations have a large performance regression. This is causing some 
packages that use libseccomp such as container orchestration systems to 
occasionally time out or otherwise fail under certain workloads.

  Please consider porting the patch into the various Ubuntu versions
  that have version 2.4 of libseccomp and into the backports. The
  performance patch from version 2.5 (yet to be released) applies
  cleanly on top of the 2.4 branch of libseccomp.

  For more information, and for a copy of the patch (which can also be
  cherry picked from the upstream libseccomp repos) see the similar
  Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913

  Upstream issue : https://github.com/seccomp/libseccomp/issues/153
  Upstream fix : https://github.com/seccomp/libseccomp/pull/180/

  [Test Case]

  For this test case we use Docker on Ubuntu Groovy (20.10) :

  --> Current libseccomp version
  #dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu3 
 amd64high level interface to Linux seccomp filter

  ## pull ubuntu image
  # docker pull ubuntu
  ## create a container
  # docker run --name test_seccomp -it 74435f89ab78 /bin/bash

  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m10,319s
  user  0m0,018s
  sys   0m0,033s

  
  --> Patched libseccomp version

  # dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu4 
 amd64high level interface to Linux seccomp filter

  # docker start test_seccomp
  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m3,650s
  user  0m0,025s
  sys   0m0,028s

  [Regression Potential]

  The first of the 2 patches cleans up the code that adds rules to a
  single filter without changing the logic of the code. The second patch
  introduces the idea of shadow transactions. On a successful
  transaction commit the old transaction checkpoint is preserved and is
  brought up to date with the current filter. The next time a new
  transaction starts, it checks is the a shadow transaction exist and if
  so the shadow is used instead of creating a new checkpoint from
  scratch [1]. This is the patch that mitigates the performance
  regression. Any potential regression will involve the parts of the
  code that add rules to filters and/or the code that creates and checks
  the shadow transactions.

  
  [Other]

  Affected releases : Groovy, Focal, Eoan, Bionic, Xenial.

  [1]
  
https://github.com/seccomp/libseccomp/pull/180/commits/bc3a6c0453b0350ee43e4925482f705a2fbf5a4d

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1861177/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More 

[Touch-packages] [Bug 1861177] Please test proposed package

2020-07-13 Thread Łukasz Zemczak
Hello Sam, or anyone else affected,

Accepted libseccomp into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libseccomp/2.4.3-1ubuntu3.18.04.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: libseccomp (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1861177

Title:
  seccomp_rule_add is very slow

Status in snapd:
  Invalid
Status in libseccomp package in Ubuntu:
  In Progress
Status in libseccomp source package in Xenial:
  Fix Committed
Status in libseccomp source package in Bionic:
  Fix Committed
Status in libseccomp source package in Eoan:
  Fix Committed
Status in libseccomp source package in Focal:
  Fix Committed
Status in libseccomp source package in Groovy:
  In Progress

Bug description:
  [IMPACT]
  There is a known and patched issue with version 2.4 of libseccomp where 
certain operations have a large performance regression. This is causing some 
packages that use libseccomp such as container orchestration systems to 
occasionally time out or otherwise fail under certain workloads.

  Please consider porting the patch into the various Ubuntu versions
  that have version 2.4 of libseccomp and into the backports. The
  performance patch from version 2.5 (yet to be released) applies
  cleanly on top of the 2.4 branch of libseccomp.

  For more information, and for a copy of the patch (which can also be
  cherry picked from the upstream libseccomp repos) see the similar
  Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913

  Upstream issue : https://github.com/seccomp/libseccomp/issues/153
  Upstream fix : https://github.com/seccomp/libseccomp/pull/180/

  [Test Case]

  For this test case we use Docker on Ubuntu Groovy (20.10) :

  --> Current libseccomp version
  #dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu3 
 amd64high level interface to Linux seccomp filter

  ## pull ubuntu image
  # docker pull ubuntu
  ## create a container
  # docker run --name test_seccomp -it 74435f89ab78 /bin/bash

  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m10,319s
  user  0m0,018s
  sys   0m0,033s

  
  --> Patched libseccomp version

  # dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu4 
 amd64high level interface to Linux seccomp filter

  # docker start test_seccomp
  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m3,650s
  user  0m0,025s
  sys   0m0,028s

  [Regression Potential]

  The first of the 2 patches cleans up the code that adds rules to a
  single filter without changing the logic of the code. The second patch
  introduces the idea of shadow transactions. On a successful
  transaction commit the old transaction checkpoint is preserved and is
  brought up to date with the current filter. The next time a new
  transaction starts, it checks is the a shadow transaction exist and if
  so the shadow is used instead of creating a new checkpoint from
  scratch [1]. This is the patch that mitigates the performance
  regression. Any potential regression will involve the parts of the
  code that add rules to filters and/or the code that creates and checks
  the shadow transactions.

  
  [Other]

  Affected releases : Groovy, Focal, Eoan, Bionic, Xenial.

  [1]
  
https://github.com/seccomp/libseccomp/pull/180/commits/bc3a6c0453b0350ee43e4925482f705a2fbf5a4d

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1861177/+subscriptions

-- 
Mailing list: 

[Touch-packages] [Bug 1861177] Re: seccomp_rule_add is very slow

2020-07-13 Thread Łukasz Zemczak
Hello Sam, or anyone else affected,

Accepted libseccomp into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libseccomp/2.4.3-1ubuntu3.20.04.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: libseccomp (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1861177

Title:
  seccomp_rule_add is very slow

Status in snapd:
  Invalid
Status in libseccomp package in Ubuntu:
  In Progress
Status in libseccomp source package in Xenial:
  In Progress
Status in libseccomp source package in Bionic:
  Fix Committed
Status in libseccomp source package in Eoan:
  Fix Committed
Status in libseccomp source package in Focal:
  Fix Committed
Status in libseccomp source package in Groovy:
  In Progress

Bug description:
  [IMPACT]
  There is a known and patched issue with version 2.4 of libseccomp where 
certain operations have a large performance regression. This is causing some 
packages that use libseccomp such as container orchestration systems to 
occasionally time out or otherwise fail under certain workloads.

  Please consider porting the patch into the various Ubuntu versions
  that have version 2.4 of libseccomp and into the backports. The
  performance patch from version 2.5 (yet to be released) applies
  cleanly on top of the 2.4 branch of libseccomp.

  For more information, and for a copy of the patch (which can also be
  cherry picked from the upstream libseccomp repos) see the similar
  Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913

  Upstream issue : https://github.com/seccomp/libseccomp/issues/153
  Upstream fix : https://github.com/seccomp/libseccomp/pull/180/

  [Test Case]

  For this test case we use Docker on Ubuntu Groovy (20.10) :

  --> Current libseccomp version
  #dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu3 
 amd64high level interface to Linux seccomp filter

  ## pull ubuntu image
  # docker pull ubuntu
  ## create a container
  # docker run --name test_seccomp -it 74435f89ab78 /bin/bash

  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m10,319s
  user  0m0,018s
  sys   0m0,033s

  
  --> Patched libseccomp version

  # dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu4 
 amd64high level interface to Linux seccomp filter

  # docker start test_seccomp
  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m3,650s
  user  0m0,025s
  sys   0m0,028s

  [Regression Potential]

  The first of the 2 patches cleans up the code that adds rules to a
  single filter without changing the logic of the code. The second patch
  introduces the idea of shadow transactions. On a successful
  transaction commit the old transaction checkpoint is preserved and is
  brought up to date with the current filter. The next time a new
  transaction starts, it checks is the a shadow transaction exist and if
  so the shadow is used instead of creating a new checkpoint from
  scratch [1]. This is the patch that mitigates the performance
  regression. Any potential regression will involve the parts of the
  code that add rules to filters and/or the code that creates and checks
  the shadow transactions.

  
  [Other]

  Affected releases : Groovy, Focal, Eoan, Bionic, Xenial.

  [1]
  
https://github.com/seccomp/libseccomp/pull/180/commits/bc3a6c0453b0350ee43e4925482f705a2fbf5a4d

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1861177/+subscriptions

-- 
Mailing list: 

[Touch-packages] [Bug 1887370] Re: libgbm-dev installation fails because of wrong dependency

2020-07-13 Thread Timo Aaltonen
you should first install all updates

** Changed in: mesa (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1887370

Title:
  libgbm-dev installation fails because of wrong dependency

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  /u/s/linux# apt install libgbm-dev
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgbm-dev : Depends: libgbm1 (= 19.2.8-0ubuntu0~18.04.3) but 
20.0.8-0ubuntu1~18.04.1 is to be installed
  E: Unable to correct problems, you have held broken packages.

  System info:
   Distributor ID: Ubuntu
   Description:Ubuntu 18.04.4 LTS
   Release:18.04
   Codename:   bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1887370/+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 1868520] Re: Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 808665665

2020-07-13 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 20.0.8-0ubuntu1~18.04.1

---
mesa (20.0.8-0ubuntu1~18.04.1) bionic; urgency=medium

  * Backport to bionic.
  * control: Relax libclc-dev build-dep for bionic.
  * Revert-meson-Use-dependency.partial_dependency.patch: Don't use a special
meson feature not in bionic.

mesa (20.0.8-0ubuntu1~20.04.1) focal; urgency=medium

  * Backport to focal.
- migrate to LLVM 10 (LP: #1882901)
- fix zwp_linux_dmabuf_v1 on wayland (LP: #1868520)
  * control: Relax libclc-dev build-dep for the backport.

mesa (20.0.8-0ubuntu1) groovy; urgency=medium

  * New upstream release.
  * fix-build-with-llvm-10.diff: Dropped, upstream.

mesa (20.0.7-1ubuntu1) groovy; urgency=medium

  * Merge from Debian.

mesa (20.0.7-1) unstable; urgency=medium

  * New upstream release.
  * src_glx_dri_common.h.diff: A new attempt to fix hurd ftbfs. (Closes:
#960197)

mesa (20.0.6-3ubuntu1) groovy; urgency=medium

  * Merge from Debian.
  * control: Build with llvm-10.

mesa (20.0.6-3) unstable; urgency=medium

  * src_glx_dri_common.h.diff: Dropped, breaks the build.

mesa (20.0.6-2) unstable; urgency=medium

  [ Timo Aaltonen ]
  * control: Bump libdrm-dev build-dep.

  [ Svante Signell ]
  * src_glx_dri_common.h.diff: Fix build on Hurd. (Closes: #959975)

  [ Frédéric Bonnard ]
  * Fix ppc64el FTBFS. (Closes: #959943)

mesa (20.0.6-1) unstable; urgency=medium

  * New upstream release.
  * patches: Drop upstreamed patches, refresh llvm-10 build-fix.

mesa (20.0.4-2ubuntu1~18.04.2) bionic; urgency=medium

  * rules: Disable zink, it adds libvulkan1 dependency to libgl1-mesa-
dri, and it's in universe.

mesa (20.0.4-2ubuntu1~18.04.1) bionic; urgency=medium

  * Backport for 18.04.5 HWE stack update. (LP: #1876882).
  * Install EGL/GL/GLES header files again, migration to libglvnd doesn't
concern bionic.
  * control: Relax debhelper requirement.
  * patches: Refreshed.
  * patches: Revert more things for old libglvnd/meson.
  * control: Bump libdrm-dev build-dep.
  * rules: Don't prefer iris over i965 on Intel to avoid needing a newer
libepoxy.

 -- Timo Aaltonen   Fri, 12 Jun 2020 14:51:05 +0300

** Changed in: mesa (Ubuntu Bionic)
   Status: Invalid => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1868520

Title:
  Wayland apps fail to run with zwp_linux_dmabuf error (failed to import
  supplied dmabufs: Unsupported buffer format 808669784
  [DRM_FORMAT_XRGB2101010]) (or 808665665 [DRM_FORMAT_ABGR2101010])

Status in Mesa:
  Fix Released
Status in MPV:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in mesa source package in Focal:
  Fix Released

Bug description:
  [Impact]

  Wayland apps fail to start in focal with:

  error 7: failed to import supplied dmabufs: Unsupported buffer format
  808669784

  [Test Case]

  Just run: es2gears_wayland

  [Regression Potential]

  Medium/unknown. The fix is quite new.

  [Other Info]

  When attempting to run es2gears_wayland against GNOME Shell, it fails
  with:

  EGL_VERSION = 1.5
  vertex shader info:
  fragment shader info:
  info:
  [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported 
buffer format 808669784

  The full wayland protocol trace is:

  [3104432.914]  -> wl_display@1.get_registry(new id wl_registry@2)
  [3104432.972]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3104433.139] wl_display@1.delete_id(3)
  [3104433.175] wl_registry@2.global(1, "wl_drm", 2)
  [3104433.207] wl_registry@2.global(2, "wl_compositor", 4)
  [3104433.240]  -> wl_regis...@2.bind(2, "wl_compositor", 1, new id 
[unknown]@4)
  [3104433.285] wl_registry@2.global(3, "wl_shm", 1)
  [3104433.316] wl_registry@2.global(4, "wl_output", 2)
  [3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3)
  [3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3)
  [3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1)
  [3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2)
  [3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1)
  [3104433.513] wl_registry@2.global(11, "wl_shell", 1)
  [3104433.542]  -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5)
  [3104433.582] wl_registry@2.global(12, "gtk_shell1", 3)
  [3104433.611] wl_registry@2.global(13, "wp_viewporter", 1)
  [3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1)
  [3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1)
  [3104433.699] wl_registry@2.global(16, "wl_seat", 5)
  [3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1)
  [3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1)
  [3104433.816] 

[Touch-packages] [Bug 1882901] Re: Migrate mesa to llvm 10

2020-07-13 Thread Launchpad Bug Tracker
This bug was fixed in the package libclc -
0.2.0+git20190827-1ubuntu0.18.04.3

---
libclc (0.2.0+git20190827-1ubuntu0.18.04.3) bionic; urgency=medium

  * clang: Bump to 10. (LP: #1882901)

 -- Timo Aaltonen   Wed, 10 Jun 2020 11:29:07 +0300

** Changed in: libclc (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** Changed in: mesa (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1882901

Title:
  Migrate mesa to llvm 10

Status in libclc package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in libclc source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in libclc source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Released

Bug description:
  [Impact]

  Mesa should migrate to llvm 10. Focal didn't migrate to it before
  release, because there was a build issue on ppc64el, which has since
  been fixed.

  [Test case]

  Test AMD graphics and/or qemu desktop after installing migrated
  packages.

  [Regression potential]

  This has been in Debian for a month now without issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1882901/+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 1882901] Re: Migrate mesa to llvm 10

2020-07-13 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 20.0.8-0ubuntu1~18.04.1

---
mesa (20.0.8-0ubuntu1~18.04.1) bionic; urgency=medium

  * Backport to bionic.
  * control: Relax libclc-dev build-dep for bionic.
  * Revert-meson-Use-dependency.partial_dependency.patch: Don't use a special
meson feature not in bionic.

mesa (20.0.8-0ubuntu1~20.04.1) focal; urgency=medium

  * Backport to focal.
- migrate to LLVM 10 (LP: #1882901)
- fix zwp_linux_dmabuf_v1 on wayland (LP: #1868520)
  * control: Relax libclc-dev build-dep for the backport.

mesa (20.0.8-0ubuntu1) groovy; urgency=medium

  * New upstream release.
  * fix-build-with-llvm-10.diff: Dropped, upstream.

mesa (20.0.7-1ubuntu1) groovy; urgency=medium

  * Merge from Debian.

mesa (20.0.7-1) unstable; urgency=medium

  * New upstream release.
  * src_glx_dri_common.h.diff: A new attempt to fix hurd ftbfs. (Closes:
#960197)

mesa (20.0.6-3ubuntu1) groovy; urgency=medium

  * Merge from Debian.
  * control: Build with llvm-10.

mesa (20.0.6-3) unstable; urgency=medium

  * src_glx_dri_common.h.diff: Dropped, breaks the build.

mesa (20.0.6-2) unstable; urgency=medium

  [ Timo Aaltonen ]
  * control: Bump libdrm-dev build-dep.

  [ Svante Signell ]
  * src_glx_dri_common.h.diff: Fix build on Hurd. (Closes: #959975)

  [ Frédéric Bonnard ]
  * Fix ppc64el FTBFS. (Closes: #959943)

mesa (20.0.6-1) unstable; urgency=medium

  * New upstream release.
  * patches: Drop upstreamed patches, refresh llvm-10 build-fix.

mesa (20.0.4-2ubuntu1~18.04.2) bionic; urgency=medium

  * rules: Disable zink, it adds libvulkan1 dependency to libgl1-mesa-
dri, and it's in universe.

mesa (20.0.4-2ubuntu1~18.04.1) bionic; urgency=medium

  * Backport for 18.04.5 HWE stack update. (LP: #1876882).
  * Install EGL/GL/GLES header files again, migration to libglvnd doesn't
concern bionic.
  * control: Relax debhelper requirement.
  * patches: Refreshed.
  * patches: Revert more things for old libglvnd/meson.
  * control: Bump libdrm-dev build-dep.
  * rules: Don't prefer iris over i965 on Intel to avoid needing a newer
libepoxy.

 -- Timo Aaltonen   Fri, 12 Jun 2020 14:51:05 +0300

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1882901

Title:
  Migrate mesa to llvm 10

Status in libclc package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in libclc source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in libclc source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Released

Bug description:
  [Impact]

  Mesa should migrate to llvm 10. Focal didn't migrate to it before
  release, because there was a build issue on ppc64el, which has since
  been fixed.

  [Test case]

  Test AMD graphics and/or qemu desktop after installing migrated
  packages.

  [Regression potential]

  This has been in Debian for a month now without issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1882901/+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 1876882] Re: Backport packages for 18.04.5 HWE stack

2020-07-13 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 20.0.8-0ubuntu1~18.04.1

---
mesa (20.0.8-0ubuntu1~18.04.1) bionic; urgency=medium

  * Backport to bionic.
  * control: Relax libclc-dev build-dep for bionic.
  * Revert-meson-Use-dependency.partial_dependency.patch: Don't use a special
meson feature not in bionic.

mesa (20.0.8-0ubuntu1~20.04.1) focal; urgency=medium

  * Backport to focal.
- migrate to LLVM 10 (LP: #1882901)
- fix zwp_linux_dmabuf_v1 on wayland (LP: #1868520)
  * control: Relax libclc-dev build-dep for the backport.

mesa (20.0.8-0ubuntu1) groovy; urgency=medium

  * New upstream release.
  * fix-build-with-llvm-10.diff: Dropped, upstream.

mesa (20.0.7-1ubuntu1) groovy; urgency=medium

  * Merge from Debian.

mesa (20.0.7-1) unstable; urgency=medium

  * New upstream release.
  * src_glx_dri_common.h.diff: A new attempt to fix hurd ftbfs. (Closes:
#960197)

mesa (20.0.6-3ubuntu1) groovy; urgency=medium

  * Merge from Debian.
  * control: Build with llvm-10.

mesa (20.0.6-3) unstable; urgency=medium

  * src_glx_dri_common.h.diff: Dropped, breaks the build.

mesa (20.0.6-2) unstable; urgency=medium

  [ Timo Aaltonen ]
  * control: Bump libdrm-dev build-dep.

  [ Svante Signell ]
  * src_glx_dri_common.h.diff: Fix build on Hurd. (Closes: #959975)

  [ Frédéric Bonnard ]
  * Fix ppc64el FTBFS. (Closes: #959943)

mesa (20.0.6-1) unstable; urgency=medium

  * New upstream release.
  * patches: Drop upstreamed patches, refresh llvm-10 build-fix.

mesa (20.0.4-2ubuntu1~18.04.2) bionic; urgency=medium

  * rules: Disable zink, it adds libvulkan1 dependency to libgl1-mesa-
dri, and it's in universe.

mesa (20.0.4-2ubuntu1~18.04.1) bionic; urgency=medium

  * Backport for 18.04.5 HWE stack update. (LP: #1876882).
  * Install EGL/GL/GLES header files again, migration to libglvnd doesn't
concern bionic.
  * control: Relax debhelper requirement.
  * patches: Refreshed.
  * patches: Revert more things for old libglvnd/meson.
  * control: Bump libdrm-dev build-dep.
  * rules: Don't prefer iris over i965 on Intel to avoid needing a newer
libepoxy.

 -- Timo Aaltonen   Fri, 12 Jun 2020 14:51:05 +0300

** Changed in: mesa (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1876882

Title:
  Backport packages for 18.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-10 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Invalid
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-10 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.5 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-10: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

  [Other info]

  mesa and libclc will migrate to llvm-10 in a separate upload

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1876882/+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 1887356] Re: System crashes while loading an application in cisco webex meeting

2020-07-13 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (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/1887356

Title:
  System crashes while loading an application in cisco webex meeting

Status in xorg package in Ubuntu:
  New

Bug description:
  The above error was also encountered in Linux Mint Tessa. The Xubuntu
  is doing better as the whole system doesn't freeze and only the
  fozilla freezes.No other slow down or crashes was observed unless
  opening games on steam and this error in cisco webex.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Jul 13 13:50:14 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] 
[1025:1085]
  InstallationDate: Installed on 2020-07-11 (2 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Acer Aspire ES1-572
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=84c7b499-378e-469f-8216-9024afe9b1fc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: T-Rex_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd04/12/2016:svnAcer:pnAspireES1-572:pvrV1.09:rvnAcer:rnT-Rex_SK:rvrV1.09:cvnAcer:ct10:cvrV1.09:
  dmi.product.family: SKL
  dmi.product.name: Aspire ES1-572
  dmi.product.sku: Aspire ES1-572_1085_V1.09
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1887356/+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 1887356] [NEW] System crashes while loading an application in cisco webex meeting

2020-07-13 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The above error was also encountered in Linux Mint Tessa. The Xubuntu is
doing better as the whole system doesn't freeze and only the fozilla
freezes.No other slow down or crashes was observed unless opening games
on steam and this error in cisco webex.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Jul 13 13:50:14 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] [1025:1085]
InstallationDate: Installed on 2020-07-11 (2 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Acer Aspire ES1-572
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=84c7b499-378e-469f-8216-9024afe9b1fc ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/12/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.09
dmi.board.asset.tag: Type2 - Board Serial Number
dmi.board.name: T-Rex_SK
dmi.board.vendor: Acer
dmi.board.version: V1.09
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.09
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd04/12/2016:svnAcer:pnAspireES1-572:pvrV1.09:rvnAcer:rnT-Rex_SK:rvrV1.09:cvnAcer:ct10:cvrV1.09:
dmi.product.family: SKL
dmi.product.name: Aspire ES1-572
dmi.product.sku: Aspire ES1-572_1085_V1.09
dmi.product.version: V1.09
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubuntu
-- 
System crashes while loading an application in cisco webex meeting
https://bugs.launchpad.net/bugs/1887356
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 1721398] Re: Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils package

2020-07-13 Thread Bug Watch Updater
** Changed in: libimobiledevice (Debian)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
https://bugs.launchpad.net/bugs/1721398

Title:
  Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils
  package

Status in libimobiledevice package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Debian:
  Fix Released

Bug description:
  Currently all of the other important utilities are included for
  installation on Ubuntu. However currently though a Ubuntu Linux user,
  is unable to perform an iOS device restore. In order to do so
  currently the user needs to have some way of running an up to date
  iTunes software with a usb connection to the iPhone, iPad or iPod
  Touch.

  Which is quite a hassle to go through in order to completely reload
  the device's iOS software. It would be much better if a binary
  compiled version of the software (idevicerestore and libirecovery)
  could be included in the utilities package.

  It would allow the Ubuntu user to be able to quickly and easily
  perform software update or device restore functions. Without the need
  for a virtual machine running a compatible version of Windows and
  iTunes etc. While also saving them from having to run Wine, its
  dependencies, iTunes and its own software requirements.

  All the would need is what is required to install idevicerestore and
  run its actions (the appropriate iOS release download image file).

  The code for idevice restore is available here
  (https://cgit.sukimashita.com/idevicerestore.git/) and the library
  from here (https://cgit.sukimashita.com/libirecovery.git/).

  Running Ubuntu 16.04.3
  libimobiledevice-utils 1.2.0+dfsg-3~ubuntu0.2 installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1721398/+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 1887372] [NEW] Cannot create lvm opon IMSM raid array

2020-07-13 Thread Mariusz Tkaczyk
Public bug reported:

The issue has been observed on 2.3.7 (Ubuntu 20.04).
Reported to lvm team:
https://bugzilla.redhat.com/show_bug.cgi?id=1855251

Steps to Reproduce:
1. Create IMSM raid array:
#mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1
#mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G

2. Create lvm volume on raid:
# pvcreate -ff -y /dev/md/vol
# vgcreate group0 /dev/md/vol
# lvcreate -Z y -y -l +100%FREE group0 -n lvm0

Actual results:
Vg creation fails.

Expected results:
LVM should be able to determine the best drive and ignore duplicates.

Additional info:
IMSM metadata is written at the end of the drive. The first drive sector 
belongs to the raid volume and other metadata saved there (like lvm) can be 
recognized directly on raid members.

The following patches should fix the issue (not verified yet):
https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca
https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81

** Affects: lvm2 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1887372

Title:
  Cannot create lvm opon IMSM raid array

Status in lvm2 package in Ubuntu:
  New

Bug description:
  The issue has been observed on 2.3.7 (Ubuntu 20.04).
  Reported to lvm team:
  https://bugzilla.redhat.com/show_bug.cgi?id=1855251

  Steps to Reproduce:
  1. Create IMSM raid array:
  #mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1
  #mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G

  2. Create lvm volume on raid:
  # pvcreate -ff -y /dev/md/vol
  # vgcreate group0 /dev/md/vol
  # lvcreate -Z y -y -l +100%FREE group0 -n lvm0

  Actual results:
  Vg creation fails.

  Expected results:
  LVM should be able to determine the best drive and ignore duplicates.

  Additional info:
  IMSM metadata is written at the end of the drive. The first drive sector 
belongs to the raid volume and other metadata saved there (like lvm) can be 
recognized directly on raid members.

  The following patches should fix the issue (not verified yet):
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887372/+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 1887370] [NEW] libgbm-dev installation fails because of wrong dependency

2020-07-13 Thread Helio Loureiro
Public bug reported:

/u/s/linux# apt install libgbm-dev
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libgbm-dev : Depends: libgbm1 (= 19.2.8-0ubuntu0~18.04.3) but 
20.0.8-0ubuntu1~18.04.1 is to be installed
E: Unable to correct problems, you have held broken packages.

System info:
 Distributor ID: Ubuntu
 Description:Ubuntu 18.04.4 LTS
 Release:18.04
 Codename:   bionic

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1887370

Title:
  libgbm-dev installation fails because of wrong dependency

Status in mesa package in Ubuntu:
  New

Bug description:
  /u/s/linux# apt install libgbm-dev
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgbm-dev : Depends: libgbm1 (= 19.2.8-0ubuntu0~18.04.3) but 
20.0.8-0ubuntu1~18.04.1 is to be installed
  E: Unable to correct problems, you have held broken packages.

  System info:
   Distributor ID: Ubuntu
   Description:Ubuntu 18.04.4 LTS
   Release:18.04
   Codename:   bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1887370/+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 1883846] Re: hwdb: Mask rfkill event from intel-hid on HP platforms

2020-07-13 Thread Chih-Hsyuan Ho
@Dan, got it. Will ping the team for help. Thanks again.

-- 
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/1883846

Title:
  hwdb: Mask rfkill event from intel-hid on HP platforms

Status in HWE Next:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  Press wireless hotkey on HP's latest generation laptops generate two rfkill 
events, prevent airplane mode from turning off.

  One event is from intel-hid and the other one is from hp-wireless.

  [Fix]
  Commit "hwdb: Mask rfkill event from intel-hid on HP platforms", to only use 
rfkill from hp-wireless.

  [Test]
  With the one-liner fix, press wireless hotkey only generate one rfkill event, 
hence airplane mode works as expected.

  [Regression Potential]
  Low, use hp-wireless over intel-hid is anticipated.

  any regression would likely result in missed rfkill events.

  [scope]

  this is fixed upstream by commit
  d8a9dd0dc17df77229d079afe29c05ae4a9e2ae9 which is not included in any
  version yet, so this is needed for f and g.

  @kaihengfeng is this needed on b and/or x as well?

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1883846/+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 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background

2020-07-13 Thread Guy Baconniere
I added https://ubuntu.com/legal/motd to Archive.org's Internet Wayback
Machine

https://web.archive.org/web/20200713070037/https://ubuntu.com/legal/motd

** Attachment added: "canonical-legal-motd.pdf"
   
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5392271/+files/canonical-legal-motd.pdf

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1867424

Title:
  motd-news transmitting private hardware data without consent or
  knowledge in background

Status in base-files package in Ubuntu:
  Won't Fix

Bug description:
  In package base-files there is a script /etc/update-motd.d/50-motd-
  news that harvests private hardware data from the machine and
  transmits it in the background every day.  There is no notice, no
  consent, no nothing.  This should be by default disabled until there
  is informed consent.

  This solution is simple:

  1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 
  2. Place a comment in the file disclosing the fact that the 50-motd-news 
script will harvest private hardware data and upload it to motd.ubuntu.com 
daily if the end-user enables it.

  Creating databases that maps ip address to specify hardware is a
  threat to both privacy and security.  If an adversary knows the
  specific hardware and the ip address for that hardware their ability
  to successfully attack it is greatly increased.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+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 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with 5.4 kernels in Bionic

2020-07-13 Thread Kleber Sacilotto de Souza
This is a testcase issue, so I'm lowering the importance to 'Medium'.

** Changed in: lxc (Ubuntu Bionic)
   Importance: High => Medium

-- 
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/1886790

Title:
  lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with 5.4 kernels in Bionic

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Bionic:
  Confirmed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz

  The failing test seems to be:

  FAIL: lxc-tests: lxc-test-device-add-remove (0s)
  ---
  Adding /dev/network_latency to the container (device_add_remove_test) 
failed...
  ---

  This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note
  that this testcase is successful on Focal with the same kernel
  version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1886790/+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 1855350] Re: Will not logout or shutdown from guest-session

2020-07-13 Thread Jarno Suni
Mika, I can confirm, oddly it helped renaming 
/usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf to 
/usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf.bak.
I am using 20.04 now.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1855350

Title:
  Will not logout or shutdown from guest-session

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce4-session package in Ubuntu:
  Confirmed

Bug description:
  This is in Xubuntu 19.10, a regression from 18.04. xfce4-session
  4.14.0-0ubuntu1. I enabled guest-session and logged in that. But there
  I can not log out or even shut down using the graphical way at least
  unless put Action Buttons on the panel and choose Switch User. If I
  run "xfce4-session-logout -l" I get error dialog saying:

  Received error while trying to log out

  GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs:Type of message,
  "(yb)", does not match expected type"(b)"

  And in standard output there is: "Received error while trying to log
  out, error was GDBus.Error:org.xfce.SessionManager.Error.Failed:
  Session manager must be in idle state when requesting a shutdown"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1855350/+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 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background

2020-07-13 Thread Guy Baconniere
https://ico.org.uk/make-a-complaint/your-personal-information-concerns/

To: ICO

Dear Information Commissioner’s Office,

I confirm that I want to proceed with the creation of the case about
Canonical's motd-news as Canonical don't want to remediate the privacy 
issue of sending by default hardware details and public IP of all 
Ubuntu Desktop and Ubuntu Server twice a day, every day of the year.

Next to this message, you will find the final answer from Canonical.

https://ubuntu.com/legal/motd

The following are my comments on their legal information.

"The purpose of sending the system information is so that Canonical can
tailor the message returned by https://motd.canonical.com.;

This is wrong motd.canonical.com does not exist and is part of motd-news.
The server used by Ubuntu is https://motd.ubuntu.com

lynx -mime_header https://motd.canonical.com

Looking up motd.canonical.com
Unable to locate remote host motd.canonical.com.
Alert!: Unable to connect to remote host.

The evidence is part of the Ticket
https://launchpadlibrarian.net/487032881/ubuntu-desktop-2004-motd-news.png

"None of this data can be used to identify a machine or user."

"Along with this data, the IP address and other network information is
transmitted to facilitate communication on the internet from the Ubuntu
machine to Canonical. This information is not stored by Canonical."

This is wrong as Canonical is using Apache and the default is to store
IP address in the access log

https://httpd.apache.org/docs/current/logs.html

Common Log Format

(%h)
 This is the IP address of the client (remote host) which
made the request to the server. If HostnameLookups is set to On, then the 
server will try to determine the hostname and log it in place of the IP 
address. However, this configuration is not recommended since it can 
significantly slow the server. Instead, it is best to use a log post-processor 
such as logresolve to determine the hostnames. The IP address reported here is 
not necessarily the address of the machine at which the user is sitting. If a 
proxy server exists between the user and the server, this address will be the 
address of the proxy, rather than the originating machine.

lynx -mime_header https://motd.ubuntu.com

HTTP/1.1 200 OK
Date: Mon, 13 Jul 2020 06:05:38 GMT
Server: Apache/2.4.18 (Ubuntu)
Last-Modified: Mon, 13 Jul 2020 06:00:50 GMT
Accept-Ranges: bytes
Content-Length: 215
Vary: Accept-Encoding
Connection: close
Content-Type: text/plain

 * "If you've been waiting for the perfect Kubernetes dev solution for
   macOS, the wait is over. Learn how to install Microk8s on macOS."

   https://www.techrepublic.com/article/how-to-install-microk8s-on-
macos/

"You can disable this service as follows:"
"/etc/default/motd-news has an ENABLED=1 setting that if set to 0 will turn off 
this functionality."

I assume 80% of Ubuntu Desktop users will not know how to disable motd-news
because they need a Terminal and sudo access. A regular editor running
a default user will not allow to edit this file as super user. So this doc
is useless. 

On top of that Canonical send motd-news information before
the user can even opt out during the installation of Ubuntu Desktop
and during the first boot of the Ubuntu Desktop operating system
so setting it is only useful to stop it but the harm is already done
and data already sent to Canonical.

Evidence https://launchpadlibrarian.net/487031151/ubuntu-
desktop-2004.png

For more information read
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424

Please also note that https://ubuntu.com/legal/motd title is not searchable
in their search engine and is not part of the legal notice during the 
installation of Ubuntu

Evidence (picture in attachment) and
https://launchpadlibrarian.net/487031391/ubuntu-desktop-2004-legal.png

"No, don't send system info" is not respected
https://launchpadlibrarian.net/487031210/ubuntu-desktop-2004-optout.png
https://launchpadlibrarian.net/487032881/ubuntu-desktop-2004-motd-news.png

Privacy does not have an option to opt out from motd-news
https://launchpadlibrarian.net/487031529/ubuntu-desktop-2004-privacy.png

 Forwarded Message 
Subject: Re: Unremovable motd-news used as Telemetry and Advertising tool 
without explicit consent
Date: Fri, 10 Jul 2020 12:00:29 +0100

Dear Guy

Thank you for your patience.

Please now see the legal notice for MOTD on Canonical's website:
https://ubuntu.com/legal/motd

I can assure you that no access to or storage of IP address data is
made.

Canonical takes data protection compliance very seriously and we
continue to review how we can improve this and other services.

Many thanks

Director of Legal & Company Secretary
Canonical
Blue Fin Building, 5th Floor
110 Southwark Street, SE1 0SU
Ubuntu - Linux for Human Beings
www.canonical.com

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.

[Touch-packages] [Bug 1887304] Re: Display configuration gets applied only after I log in

2020-07-13 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1760849 ***
https://bugs.launchpad.net/bugs/1760849

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1760849, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** This bug has been marked a duplicate of bug 1760849
   Login screen appears on only one monitor and it's not the one I want

-- 
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/1887304

Title:
  Display configuration gets applied only after I log in

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This isn't new, this idiocy has annoyed me ever since I've been using
  Ubuntu; however, after upgrading to 20.04 I'm disappointed to see that
  it still hasn't been fixed.

  I use a laptop and I have an external monitor that I keep connected
  most of the time.

  So, I have it set up to use the external screen as the only display.

  However, when I boot and the login screen shows up, a different
  configuration, which I guess is the default, is applied, with the
  laptop's built-in display as the main display and the external screen
  as the secondary one in extended desktop configuration. Therefore the
  login screen shows up on the builtin display.

  Only after I log in, my configuration gets applied and the builtin
  displey turns off and the external one becomes the only one.

  It's not a huge deal since the laptop screen is kind of in front of me
  anyway so I can see it, but it's not ideal and it's stupid. Also, it
  implies that when I do log in, I have that few seconds of all-black
  screens while the displays adjust, which is irritating considered they
  would have had plenty of time to do that before I logged in.

  I guess the display configuration is somehow stored as associated to
  the user, and I understand that theoretically different users may have
  different configurations.

  However, that's no excuse. As an administrator, I should be able to
  choose a configuration that gets applied from the beginning before
  anybody logs in. Also, given that I am the ONLY user (which is a
  pretty common scenario on Desktop), it should be the default that my
  configuration be the global configuration (with the possibility to
  choose differently).

  Probably a good solution would be to have, in the Displays settings,
  an option such as "apply this configuration globally" (or whatever
  better phrasing), meaning it would be applied before login.

  Obviously that doesn't mean that, if the saved configuration is not
  applicable to the current situation at startup (e.g. I have set it up
  to use only the external monitor but there is no external monitor
  connected right now), it shouldn't automatically switch to a different
  workable setting. I think it already does that if that happens after
  login, so that would be no different before login.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 21:04:20 2020
  DistUpgraded: 2020-07-12 20:55:12,554 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.108, 5.3.0-62-generic, x86_64: installed
   nvidia-340, 340.108, 5.4.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
   NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] 

[Touch-packages] [Bug 1887296] Re: Moving popup windows drags the application's main window behind it

2020-07-13 Thread Daniel van Vugt
This is a feature we inherited from GNOME. It is not a design choice by
Ubuntu.

To disable it just set:

  Gnome Tweaks > Windows > Attach Modal Dialogs = OFF


** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1887296

Title:
  Moving popup windows drags the application's main window behind it

Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  Sometimes programs open a "popup" or a "secondary", "child" window, I
  don't know what the word is.

  For example, in Chrome, if I right-click on an image in a web page and
  choose "Save As", this will open a new file browser window that allows
  me to browse for a directory to save the image to.

  Until Ubuntu 16.04, I could move that child window around by dragging
  it by its title bar, and that would not move around the parent window
  behind it.

  Now, it does. That is, the "parent" window greyes out, and moving the
  "child" window (i.e. the popup) on the foreground causes the parent
  window in the background to move as if they were glued together.

  In the above example, if I drag around the "Save As" window, the
  Chrome window behind it moves too. Even worse, if the parent window is
  maximized, it will "oppose resistance" to the dragging of the popup
  window, and if I drag far enough, the parent window will unmaximize
  and unblock the movement of both windows.

  It's pure madness.

  
  I can't imagine a scenario where this is the unavoidable consequence of some 
improvement. It looks like it is by design.

  Why?

  What were you thinking? Why do you ACTIVELY work to degrade usability
  and make the users' life miserable??

  
  Here's a very real-life example:

  As mentioned above, I right-click on something in the browser (like an
  image or a video) and do Save As. When the file browser window opens,
  it covers the content of the web page from which I was saving the
  content. Maybe I want to move the child window in order to reveal the
  web page that I was visiting in the first place, because the context
  (which I haven't memorized in full in my brain just yet) helps me
  choose a file name for the very file I'm saving.

  
  Another example: I am browsing some folder in Nautilus. I right-click on a 
file or folder inside it, and open Properties. That opens in a popup. Now I 
want to have another look at the name of the file I selected (of which I'm now 
seeing the properties), and those around it, because I'm wondering if I chose 
the wrong file, or for whatever other reason. I can't do taht without closing 
the Properties window.

  The everyday examples are countless.

  
  This is idiotic. Seriously, what are you doing?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18
  Uname: Linux 5.3.0-62-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 18:11:28 2020
  DistUpgraded: 2020-07-12 15:56:23,368 INFO cache.commit()
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia-340, 340.108: added
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
   NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
  InstallationDate: Installed on 2013-10-11 (2465 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - 

[Touch-packages] [Bug 1887294] Re: Display freeze

2020-07-13 Thread Daniel van Vugt
It appears you have a kernel crash in the Nvidia driver:

[412515.698236] Call Trace:
[412515.698244]  ? _nv002628kms+0x3aa/0x1f70 [nvidia_modeset]
[412515.698246]  ? __alloc_pages_nodemask+0x173/0x320
[412515.698248]  ? alloc_pages_current+0x87/0xe0
...


** Tags added: nvidia

** Summary changed:

- Display freeze
+ [nvidia] Display freeze

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-440
(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/1887294

Title:
  [nvidia] Display freeze

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New

Bug description:
  The display is completely frozen, and no signal is output to the
  monitors. There is also no signal when switching to a console (Ctr-
  Alt-F1). I have normal access via SSH.

  It happens about once in 14 days. Only happens when turning the
  display off or on (about once in 15 screen power cycles).

  nvidia-smi still works (via SSH; without any options)

  DISPLAY=:1 xset dpms force on

  hangs indefinitely.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Jul 12 17:47:58 2020
  DistUpgraded: 2020-05-17 13:48:43,365 DEBUG entry '# deb [arch=amd64] 
https://repo.skype.com/deb stable main # disabled on upgrade to focal' was 
disabled (unknown mirror)
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.100, 5.4.0-39-generic, x86_64: installed
   nvidia, 440.100, 5.4.0-40-generic, x86_64: installed (WARNING! Diff between 
built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!)
   v4l2loopback, 0.12.3, 5.4.0-39-generic, x86_64: installed
   v4l2loopback, 0.12.3, 5.4.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106 [GeForce GTX 1060 6GB] [1043:85ae]
  InstallationDate: Installed on 2016-07-27 (1445 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-05-17 (56 days ago)
  dmi.bios.date: 04/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8C WS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd04/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8CWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  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
  xserver.bootTime: Tue Jul  7 22:02:38 2020
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.8-2ubuntu2.1

To manage notifications about this bug go to:

[Touch-packages] [Bug 1887287] Re: No show-desktop shortcut out of the box since 18.04

2020-07-13 Thread Daniel van Vugt
Super-D does work correctly in Ubuntu 20.04 at least. I just tested it.

As for Ubuntu 19.10, that is about to reach end of life:

  https://wiki.ubuntu.com/Releases

so any bugs in 19.10 won't get fixed. Please install Ubuntu 20.04
instead.

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1887287

Title:
  No show-desktop shortcut out of the box since 18.04

Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  On Ubuntu 16.04 I was used to the keyboard shortcut ctrl+Super+D to
  reveal the Desktop by minimizing all windows (it was not exactly the
  same as minimizing all windows but whatever).

  That shortcut was changed at almost every major release, which was
  already irritating enough, but at least there always was one.

  Now, however, there doesn't seem to be any half-discoverable keyboard 
shortcut to show the desktop.
  I have tried Super+D, Ctrl+Alt+D (both mentioned in a bullshit article I 
found out by googling), and every other similar combination I can think of 
involving a D. Nothing works.

  
  I shouldn't have to install a tool and create a shortcut to it just to reveal 
the desktop. It's something basic. Especially considering that it used to be 
available out of the box.

  So sick of Ubuntu going backwards.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18
  Uname: Linux 5.3.0-62-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8.9
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 15:30:58 2020
  DistUpgraded: 2020-07-12 15:02:52,488 DEBUG running apport_crash()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.108, 4.15.0-109-generic, x86_64: installed
   nvidia-340, 340.108, 4.4.0-185-generic, x86_64: installed
   nvidia-340, 340.108, 5.3.0-62-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
   NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
  InstallationDate: Installed on 2013-10-11 (2465 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to eoan on 2020-07-12 (0 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.family: Type1Family
  dmi.product.name: Aspire V3-571G
  dmi.product.sku: Aspire V3-_0648_V2.07
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  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
  xserver.bootTime: Sun Jul 12 15:12:31 2020
  xserver.configfile: default
  xserver.errors:
   modeset(G0): eglGetDisplay() failed
   modeset(G0): glamor initialization failed
  

[Touch-packages] [Bug 1887254] Re: The new design makes maximized windows unusable

2020-07-13 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1710353 ***
https://bugs.launchpad.net/bugs/1710353

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1710353, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1710353
   Window controls and menus aren't in top bar when app is maximized

-- 
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/1887254

Title:
  The new design makes maximized windows unusable

Status in xorg package in Ubuntu:
  New

Bug description:
  I have just upgraded from ubuntu 16.04 to 18.04 (and I would have
  upgraded to 20.04 already if the stupid package manager weren't unable
  to resolve some conflicts which are "holding back" packages).

  An unbelievavly stupid mistake was made in the new design of windows.

  When you maximize a window, the title bar used to be at the very top
  of the screen, and the close/minimize/restore buttons used to be at
  the top-left corner of the screen.

  That means they had a property that in interface design has even a
  name, "infinite width" or "infinite something", that is: you can move
  the mouse all the way to the top and all the way to the left without
  having to "stop at the right time" in order to "land" within the area
  of the button, because the screen edges limit the mouse cursor.

  Now, the title bar of the window is no longer at the very top of the
  screen. At the top of the screen is a system bar. I mean that was
  already there, but the window buttons used to be in it on the left, as
  if the system bar at the top of the screen *was* the window title bar.
  Now the window title bar is just below it, and the buttons have been
  moved to the right (the fact that they have been moved from the left
  to the right after decades being on the left is irritating AF, but
  it's irrelevant here).

  So now the buttons, while still at the horizintal edge of the screen,
  are no longer at the corner of the screen, so when you "shoot" the
  mouse pointer to go to their area, you cannot simply go as far as you
  can and then click, you have to move a little bit down from the top in
  order to click the buttons.

  It's not just an aesthetic thing, it's a huge usablility thing. And
  it's not just a matter of habits and getting used to, it's objectively
  a step backwards (actually, it's a step in a completely new dimension,
  one of stupidity).

  It violates a very well known UI design principle that has been
  established for decades - and for a good reason, not just for
  historical reasons.

  
  Please revert this madness.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18
  Uname: Linux 4.15.0-109-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 11 22:32:12 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.108, 4.15.0-109-generic, x86_64: installed
   nvidia-340, 340.108, 4.4.0-185-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
   NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
  InstallationDate: Installed on 2013-10-11 (2465 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Touch-packages] [Bug 1887271] Re: Square rectangles instead of system fonts after upgrade

2020-07-13 Thread Daniel van Vugt
Please open:

  Gnome Tweaks > Fonts

and check that you are using 'Ubuntu' fonts.


** Package changed: xorg (Ubuntu) => pango1.0 (Ubuntu)

** Summary changed:

- Square rectangles instead of system fonts after upgrade
+ Square rectangles instead of system fonts after upgrade (LANG=de_AT.UTF-8)

** Changed in: pango1.0 (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1887271

Title:
  Square rectangles instead of system fonts after upgrade
  (LANG=de_AT.UTF-8)

Status in pango1.0 package in Ubuntu:
  Incomplete

Bug description:
  After upgrading my room mate's Fujitsu Esprimo Desktop PC  to 20.04
  Focal Fossa (from Bionic 18.04):

  Any system font line is being displayed distorted / erroneous / in
  sort of placeholder blocks or SQUARE RECTANGLES, as if the fonts set
  wouldn't be installed at all... Tthe 'gsettings'-procedure from some
  link mentioned on askubuntu-com wouldn't help either (with copy
  into unreadable terminal display font output) Gnome-tweak didn't help,
  BUT I can copy text from terminal into libreoffice document and thus
  make it readable afterwards. I cannot find any information about
  "system font output/printing" on the whole internet leaving me with a
  mysrltery about how that stuff works from xserver to gnome, Wayland-
  session login IMPOSSIBLE in order to print the correct display font
  ... I will attach some screenshots later on if possible.

  P.S.: firefox/libreoffice fonts are being displayed correctly inside
  any homepage

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 10:55:08 2020
  DistUpgraded: 2020-06-29 10:31:32,274 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.108, 5.3.0-51-generic, x86_64: installed
   nvidia-340, 340.108, 5.4.0-39-generic, x86_64: installed
   nvidia-340, 340.108, 5.4.0-40-generic, x86_64: installed
   rtlwifi-new, 0.10: added
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: CardExpert Technology G84 [GeForce 8600 GT] [10b0:0801]
  InstallationDate: Installed on 2017-08-28 (1048 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  LightdmLog:
   [+6033.49s] DEBUG: Seat seat0 changes active session to 
   [+6033.53s] DEBUG: Seat seat0 changes active session to c5
   [+6033.53s] DEBUG: Session c5 is already active
  MachineType: FUJITSU SIEMENS ESPRIMO P
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sdb4
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-06-29 (13 days ago)
  dmi.bios.date: 10/11/2007
  dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
  dmi.bios.version: 6.00 R1.12.2312.A3
  dmi.board.name: D2312-A3
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: S26361-D2312-A3
  dmi.chassis.type: 2
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.chassis.version: ESPP
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.12.2312.A3:bd10/11/2007:svnFUJITSUSIEMENS:pnESPRIMOP:pvr:rvnFUJITSUSIEMENS:rnD2312-A3:rvrS26361-D2312-A3:cvnFUJITSUSIEMENS:ct2:cvrESPP:
  dmi.product.name: ESPRIMO P
  dmi.sys.vendor: FUJITSU SIEMENS
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Jul 11 20:24:02 2020
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
 

[Touch-packages] [Bug 1887208] Re: May be xorg

2020-07-13 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: 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/1887208

Title:
  May be xorg

Status in Ubuntu:
  Incomplete

Bug description:
  My system reports something problem.
  Saying xorg crash

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18
  Uname: Linux 4.15.0-109-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Jul 11 10:45:09 2020
  DistUpgraded: 2020-07-05 12:47:35,837 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: ./xorg_fix_proprietary.py 
を子プロセスとして起動できませんでした: No such file or directory (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2015-09-24 (1751 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Build amd64 LIVE Binary 
20140422-09:40
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic 
root=UUID=1f04dac6-7535-44a7-8ea2-e3d566af9feb ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2020-07-05 (5 days ago)
  dmi.bios.date: 04/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3602
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3602:bd04/08/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sun Jul  5 11:17:27 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1887208/+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 1887247] Re: Annoying drum sound that I turned off ages ago has turned on again after upgrade

2020-07-13 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Low

-- 
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/1887247

Title:
  Annoying drum sound that I turned off ages ago has turned on again
  after upgrade

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have just upgraded from 16.04 to 18.04

  Now, every time I hit the TAB key in a terminal to autocomplete a file
  name, when there is no option or more than one, an annoying and
  ungodly loud drum sound plays.

  I'm pretty sure I disabled that sound years ago, probably even before
  I even upgraded to 16.04.

  I don't want to be forced to re-configure everything. If I turned off
  a certain kind of system sounds, I expect this configuration to be
  kept after I upgrade to a newer release. Otherwise I might as well
  wipe out my hard disk and do a clean install, if you are going to
  reset my settings anyway.

  And by the way, if the sound had been chosen with a minimum of taste
  and was not disproportionately loud (my global volume is pretty low) I
  probably wouldn't need to turn it off in the first place, as in
  principle it can be useful.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18
  Uname: Linux 4.15.0-109-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 11 20:48:14 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.108, 4.15.0-109-generic, x86_64: installed
   nvidia-340, 340.108, 4.4.0-185-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
   NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
  InstallationDate: Installed on 2013-10-11 (2465 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.family: Type1Family
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Jul 11 20:18:24 2020
  xserver.configfile: default
  xserver.errors:
   modeset(G0): eglGetDisplay() failed
   modeset(G0): glamor initialization failed
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1887247/+subscriptions

-- 
Mailing list: 

[Touch-packages] [Bug 1887150] Re: Fractional Scaling turns screen sideways

2020-07-13 Thread Daniel van Vugt
** Tags added: xrandr-scaling

** Package changed: xorg (Ubuntu) => mutter (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/1887150

Title:
  Fractional Scaling turns screen sideways

Status in mutter package in Ubuntu:
  New

Bug description:
  I right-click on desktop, click Display Settings, and find the Fractional 
Scaling option.
  When I enable the option my screen rotates 90 degrees. It's as if the display 
thought I had rotated my device 90 degrees (but I hadn't I'm using a laptop).
  Can attach screenshots if possible.

  I just freshly installed Ubuntu 20.04 from a USB and ran sudo apt-get
  update and sudo apt-get upgrade for the first time literally minutes
  ago. Nothing else was installed except for Grub Customizer and

  EDIT: Turns out I can't attach three screenshots. I can only attach
  one. I attached the final screenshot. I took screenshots of the
  original rotation, then before I selected the Fractional Scaling
  option, then what happened after. But I can only attach one of them.
  Please allow us to attach more than one screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 06:34:56 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) 
[1043:19d1]
  InstallationDate: Installed on 2020-07-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b568 Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP412FA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=d20ac799-f93e-4aea-9632-495aa9132b04 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP412FA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP412FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP412FA.302:bd05/06/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP412FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP412FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: VivoBook Flip
  dmi.product.name: VivoBook_ASUSLaptop TP412FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887150/+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 1887198] Re: [Raspberry Pi 4] Screen Freeze

2020-07-13 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Summary changed:

- Screen Freeze
+ [Raspberry Pi 4] Screen Freeze

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: 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/1887198

Title:
  [Raspberry Pi 4] Screen Freeze

Status in Ubuntu:
  Incomplete

Bug description:
  When changing user or logging off of ubuntu-desktop got a screen
  freeze that I can't get out of. No response from keyboard or mouse.
  After some time screen goes black with cursor flicking at the bottom.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-1013.13-raspi 5.4.44
  Uname: Linux 5.4.0-1013-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  Date: Fri Jul 10 20:05:57 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   
  ImageMediaBuild: 20200423.1
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 17ef:600e Lenovo 
   Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=1920 
bcm2708_fb.fbheight=1080 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:7C:B3:EE 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  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/+bug/1887198/+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