[Touch-packages] [Bug 1722478] Re: Two-finger scrolling and click-and-drag no longer works after resuming from suspend

2020-04-14 Thread Kai-Heng Feng
** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Two-finger scrolling and click-and-drag no longer works after resuming
  from suspend

Status in Linux:
  Confirmed
Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1722478/+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 1868246] Re: No network after subiquity LPAR installation on s390x with VLAN

2020-04-14 Thread Michael Hudson-Doyle
** Changed in: initramfs-tools (Ubuntu)
   Status: New => Fix Released

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

Title:
  No network after subiquity LPAR installation on s390x with VLAN

Status in cloud-init:
  Invalid
Status in subiquity:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  I tried today an subiquity LPAR installation using the latest ISO (March 19) 
that includes the latest 20.03 subiquity.
  The installation itself completed fine, but after the post-install reboot the 
system didn't had a network active - please note that the LPAR is connected to 
a VLAN.

  $ ip a   
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
defaul
  t qlen 1000   
  
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 
  
  inet 127.0.0.1/8 scope host lo
  
 valid_lft forever preferred_lft forever
  
  inet6 ::1/128 scope host  
  
 valid_lft forever preferred_lft forever
  
  2: encc000:  mtu 1500 qdisc noop state DOWN group 
default q
  len 1000  
  
  link/ether a2:8d:91:85:12:e3 brd ff:ff:ff:ff:ff:ff
  
  3: enP1p0s0:  mtu 1500 qdisc noop state DOWN group 
default 
  qlen 1000 
  
  link/ether 82:0c:2d:0c:b8:70 brd ff:ff:ff:ff:ff:ff
  
  4: enP1p0s0d1:  mtu 1500 qdisc noop state DOWN group 
defaul
  t qlen 1000   
  
  link/ether 82:0c:2d:0c:b8:71 brd ff:ff:ff:ff:ff:ff
  
  5: enP2p0s0:  mtu 1500 qdisc noop state DOWN group 
default 
  qlen 1000 
  
  link/ether 82:0c:2d:0c:b7:00 brd ff:ff:ff:ff:ff:ff
  
  6: enP2p0s0d1:  mtu 1500 qdisc noop state DOWN group 
defaul
  t qlen 1000   
  
  link/ether 82:0c:2d:0c:b7:01 brd ff:ff:ff:ff:ff:ff   

  Wanting to have a look at the netplan config it turned out that there is no 
yaml file:
  $ ls -l /etc/netplan/
  total 0  

  Adding one manually and applying it worked fine.

  So looks like the installer does not properly generate or copy a
  01-netcfg.yaml to /etc/netplan.

  Please see below the entire steps as well as a compressed file with
  the entire content of /var/log

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1868246/+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 1872286] Re: gio - cifs mount smb not possible "Location is not mountable"

2020-04-14 Thread Dirk Heumann
Remark: In Ubuntu 19.04, if the user/domain/password is not piped, `gio mount` 
requests
the `user/domain/password`:

`$ gio mount smb://192.168.178.1/Fritz7490`
`Password required for share fritz7490 on 192.168.178.1
`User [SessionUserName]: NewUserIfDifferent
`Domain [WORKGROUP]: NewDomainIfDifferent
`Password: PassWord

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

Title:
  gio - cifs mount smb not possible "Location is not mountable"

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  1) Release
  $ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2) Package
  $ apt-cache policy libglib2.0-bin
  libglib2.0-bin:
Installed: 2.64.1-1
Candidate: 2.64.1-1
Version table:
   *** 2.64.1-1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) Expected to happen
  The path should be mounted at
  /run/user/1000/gvfs/smb-share:server=192.168.178.1,share=PathName/

  4) What happened instead:
  Error Message:
  gio: smb://192.168.178.1/PathName/: Location is not mountable

  5) Long description / explanation
  Since some years, I mount a Windows drive with

  gio mount smb://192.168.178.1/PathName

  After upgrading from 19.04 to 20.04 beta, this does not work any more,
  I get the error message

  gio: smb://192.168.178.1/PathName/: Location is not mountable

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-bin 2.64.1-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 12 12:43:53 2020
  InstallationDate: Installed on 2019-02-17 (420 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: glib2.0
  UpgradeStatus: Upgraded to focal on 2020-04-05 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1872286/+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 1872162] Re: crash report fail to submit

2020-04-14 Thread Daniel van Vugt
** Package changed: firefox (Ubuntu) => apport (Ubuntu)

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

Title:
  crash report fail to submit

Status in apport package in Ubuntu:
  New

Bug description:
  Since 2020-03-19, firefox crashed about 17 times (it did not crash 1,5
  years before). Though, all crash reports failed to submit. My firefox
  crash report submit.log reads:

  [Mo 17 Dez 2018 00:14:42 CET] Crash report submitted successfully
  [Do 19 Mär 2020 00:06:24 CET] Crash report submission failed: Couldn't 
connect to server
  [Sa 21 Mär 2020 15:14:19 CET] Crash report submission failed: Couldn't 
connect to server
  [Di 24 Mär 2020 23:22:51 CET] Crash report submission failed: Couldn't 
connect to server
  [Mi 25 Mär 2020 14:22:41 CET] Crash report submission failed: Couldn't 
connect to server
  [Do 26 Mär 2020 17:40:46 CET] Crash report submission failed: Couldn't 
connect to server
  [Sa 28 Mär 2020 10:59:32 CET] Crash report submission failed: Couldn't 
connect to server
  [Mo 30 Mär 2020 01:03:56 CEST] Crash report submission failed: Couldn't 
connect to server
  [Mi 01 Apr 2020 16:01:11 CEST] Crash report submission failed: Couldn't 
connect to server
  [Do 02 Apr 2020 20:39:29 CEST] Crash report submission failed: Couldn't 
connect to server
  [Fr 03 Apr 2020 21:07:53 CEST] Crash report submission failed: Couldn't 
connect to server
  [So 05 Apr 2020 22:38:08 CEST] Crash report submission failed: Couldn't 
connect to server
  [Di 07 Apr 2020 21:40:43 CEST] Crash report submission failed: Couldn't 
connect to server
  [Mi 08 Apr 2020 13:05:39 CEST] Crash report submission failed: Couldn't 
connect to server
  [Mi 08 Apr 2020 20:16:28 CEST] Crash report submission failed: Couldn't 
connect to server
  [Mi 08 Apr 2020 22:27:58 CEST] Crash report submission failed: Couldn't 
connect to server
  [Do 09 Apr 2020 23:36:31 CEST] Crash report submission failed: Couldn't 
connect to server
  [Fr 10 Apr 2020 20:07:48 CEST] Crash report submission failed: Couldn't 
connect to server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1872162/+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 1872162] [NEW] crash report fail to submit

2020-04-14 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Since 2020-03-19, firefox crashed about 17 times (it did not crash 1,5
years before). Though, all crash reports failed to submit. My firefox
crash report submit.log reads:

[Mo 17 Dez 2018 00:14:42 CET] Crash report submitted successfully
[Do 19 Mär 2020 00:06:24 CET] Crash report submission failed: Couldn't connect 
to server
[Sa 21 Mär 2020 15:14:19 CET] Crash report submission failed: Couldn't connect 
to server
[Di 24 Mär 2020 23:22:51 CET] Crash report submission failed: Couldn't connect 
to server
[Mi 25 Mär 2020 14:22:41 CET] Crash report submission failed: Couldn't connect 
to server
[Do 26 Mär 2020 17:40:46 CET] Crash report submission failed: Couldn't connect 
to server
[Sa 28 Mär 2020 10:59:32 CET] Crash report submission failed: Couldn't connect 
to server
[Mo 30 Mär 2020 01:03:56 CEST] Crash report submission failed: Couldn't connect 
to server
[Mi 01 Apr 2020 16:01:11 CEST] Crash report submission failed: Couldn't connect 
to server
[Do 02 Apr 2020 20:39:29 CEST] Crash report submission failed: Couldn't connect 
to server
[Fr 03 Apr 2020 21:07:53 CEST] Crash report submission failed: Couldn't connect 
to server
[So 05 Apr 2020 22:38:08 CEST] Crash report submission failed: Couldn't connect 
to server
[Di 07 Apr 2020 21:40:43 CEST] Crash report submission failed: Couldn't connect 
to server
[Mi 08 Apr 2020 13:05:39 CEST] Crash report submission failed: Couldn't connect 
to server
[Mi 08 Apr 2020 20:16:28 CEST] Crash report submission failed: Couldn't connect 
to server
[Mi 08 Apr 2020 22:27:58 CEST] Crash report submission failed: Couldn't connect 
to server
[Do 09 Apr 2020 23:36:31 CEST] Crash report submission failed: Couldn't connect 
to server
[Fr 10 Apr 2020 20:07:48 CEST] Crash report submission failed: Couldn't connect 
to server

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

-- 
crash report fail to submit
https://bugs.launchpad.net/bugs/1872162
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apport 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 1751269] Re: Compiz related colour-swapping bug (Endianness bug somewhere)

2020-04-14 Thread Daniel van Vugt
** Summary changed:

- Compiz related bug (Endianness bug somewhere)
+ Compiz related colour-swapping bug (Endianness bug somewhere)

** Package changed: xorg (Ubuntu) => compiz (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/1751269

Title:
  Compiz related colour-swapping bug (Endianness bug somewhere)

Status in compiz package in Ubuntu:
  New

Bug description:
  Hello,
  I suspect a endianness problem in this BigEndian Machine (Apple PowerBook G4 
with ATI Radeon Mobility 9700). The same architecture (bigEndian) shows no this 
specific issue on PowerMac G5 Quad with PCI-Express ATI Radeon HD4670 with VGA 
BIOS (not powerpc flashed card).

  The problem seems to be a screen changing resolution or similar having
  Compiz activated. If I switch the screen resolution on this laptop,
  the garbage on the screen is more visible than using NO COMPOSITE
  Marco Mate Display Manager.

  The problem is enhanced using a second monitor attached to a DVI
  connector on this laptop.

  Can be easly reproduced.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-116.140-powerpc-smp 4.4.98
  Uname: Linux 4.4.0-116-powerpc-smp ppc
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: powerpc
  CurrentDesktop: MATE
  Date: Fri Feb 23 14:01:47 2018
  InstallationDate: Installed on 2018-02-21 (2 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release powerpc 
(20160719)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1751269/+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 1752728] Re: My pc is going in blank after sleep and nothing works

2020-04-14 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => 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/1752728

Title:
  My pc is going in blank after sleep and nothing works

Status in Ubuntu:
  New

Bug description:
  My pc is going in blank after sleep and nothing works

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Mar  1 17:12:11 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  GraphicsCard:
   Subsystem: Dell Device [1028:0774]
   NVIDIA Corporation Device [10de:1c60] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07c0]
  InstallationDate: Installed on 2017-09-27 (155 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Alienware Alienware 15 R3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=55e321af-6860-4c50-a132-9e8fe6024cd7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2017
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.2.0
  dmi.board.name: Alienware 15 R3
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.2.0:bd09/14/2017:svnAlienware:pnAlienware15R3:pvr1.2.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware 15 R3
  dmi.product.version: 1.2.0
  dmi.sys.vendor: Alienware
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1752728/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() from dri2_make_current()

2020-04-14 Thread Daniel van Vugt
Tracking in:

https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a


** Description changed:

+ https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
+ https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
+ 
+ ---
+ 
  nothing particular done to trigger this, just opening the lid apparently
  crashed the x server (ubuntu 20.04); then after reboot apport prompted
  me to report a crash
  
  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
-  # This is the distribution channel descriptor for the OEM CDs
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
-Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
+  Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
+    Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
-  Bus 001 Device 003: ID 8087:0029 Intel Corp. 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
+  Bus 001 Device 003: ID 8087:0029 Intel Corp.
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
-  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
-  __GI_abort () at abort.c:79
-  ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
-  ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
-  ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
+  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
+  __GI_abort () at abort.c:79
+  ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
+  ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
+  ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:
-  
+ 
  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:
-  
+ 
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  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+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush.cold() from
  

[Touch-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() from dri2_make_current()

2020-04-14 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xorg-server (Ubuntu)
   Status: New => Confirmed

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush.cold() from
  iris_fence_flush() from st_glFlush() from dri2_make_current()

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  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+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1871959/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() from dri2_make_current()

2020-04-14 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush.cold() from
  iris_fence_flush() from st_glFlush() from dri2_make_current()

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  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+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1871959/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() from dri2_make_current() from

2020-04-14 Thread Daniel van Vugt
** Summary changed:

- Xorg crashed with SIGABRT in __GI_raise()
+ Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() 
from st_glFlush() from dri2_make_current() from

** Summary changed:

- Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() 
from st_glFlush() from dri2_make_current() from
+ Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() 
from st_glFlush() from dri2_make_current()

** Information type changed from Private to Public

** Also 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/1871959

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush.cold() from
  iris_fence_flush() from st_glFlush() from dri2_make_current()

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  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+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1871959/+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 1872869] Re: package gnome-icon-theme-full (not installed) failed to install/upgrade: cannot copy extracted data for './usr/share/icons/gnome/48x48/actions/insert-object.png' to

2020-04-14 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: corrupted-package

** Changed in: gnome-icon-theme (Ubuntu)
   Status: New => Invalid

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

Title:
  package gnome-icon-theme-full (not installed) failed to
  install/upgrade: cannot copy extracted data for
  './usr/share/icons/gnome/48x48/actions/insert-object.png' to
  '/usr/share/icons/gnome/48x48/actions/insert-object.png.dpkg-new':
  unexpected end of file or stream

Status in gnome-icon-theme package in Ubuntu:
  Invalid

Bug description:
  This error occurred while installing xubuntu-desktop.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gnome-icon-theme-full (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Tue Apr 14 21:25:50 2020
  DuplicateSignature: package:gnome-icon-theme-full:(not installed):cannot copy 
extracted data for './usr/share/icons/gnome/48x48/actions/insert-object.png' to 
'/usr/share/icons/gnome/48x48/actions/insert-object.png.dpkg-new': unexpected 
end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/share/icons/gnome/48x48/actions/insert-object.png' to 
'/usr/share/icons/gnome/48x48/actions/insert-object.png.dpkg-new': unexpected 
end of file or stream
  InstallationDate: Installed on 2020-04-13 (1 days ago)
  InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release amd64 
(20190304.5)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.20
  SourcePackage: gnome-icon-theme
  Title: package gnome-icon-theme-full (not installed) failed to 
install/upgrade: cannot copy extracted data for 
'./usr/share/icons/gnome/48x48/actions/insert-object.png' to 
'/usr/share/icons/gnome/48x48/actions/insert-object.png.dpkg-new': unexpected 
end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/1872869/+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 1872875] [NEW] [Focal] Intel libva va_openDriver() returns -1 (VA-API broken)

2020-04-14 Thread Raymond Kimathi
Public bug reported:

Ubuntu 20.04
System selects wrong intel driver (iris_drv_video.so). Therefore cannot use 
vaapi hardware decoding

vainfo:

libva info: VA-API version 1.7.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iris_drv_video.so
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

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

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

Title:
  [Focal] Intel libva va_openDriver() returns -1 (VA-API broken)

Status in libva package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04
  System selects wrong intel driver (iris_drv_video.so). Therefore cannot use 
vaapi hardware decoding

  vainfo:

  libva info: VA-API version 1.7.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iris_drv_video.so
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1872875/+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 1717796] Re: Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle

2020-04-14 Thread Bug Watch Updater
Launchpad has imported 15 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=204275.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-07-22T13:36:29+00:00 steve wrote:

Many bluetooth HID keyboard profile devices disconnect on idle to save
power, I have two such devices:

Logitech Y-X5A77 keyboard

Sony PS3 bluetooth remote control

When the device disconnects on idle the g_io_channels get disconnected

bluetoothd[3167]: profiles/input/device.c:ctrl_watch_cb() Device 
00:07:61:F6:C9:7D disconnected
bluetoothd[3167]: profiles/input/device.c:intr_watch_cb() Device 
00:07:61:F6:C9:7D disconnected

But, something isn't closed properly (possibly g_io_add_watch) since
bluetoothd then spins at 100% CPU in g_main_loop_run() until the device
reconnects, at which point every works normally again until the device
next idles.

This bug has been present for at least 2 years, I'm certain it's much
longer:

https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1717796

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1717796/comments/11


On 2019-07-22T14:22:28+00:00 steve wrote:

I've tried adding g_source_remove()s for ctrl_watch and intr_watch
before shutting down the io channels but it doesn't make any difference.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1717796/comments/12


On 2019-07-22T19:36:06+00:00 steve wrote:

strace results in continuous repeating:

poll([{fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=7,
events=POLLIN}, {fd=8, events=POLLIN}, {fd=10, events=POLLIN}, {fd=11,
events=POLLIN}, {fd=12, events=POLLIN}, {fd=16, events=POLLIN}, {fd=17,
events=POLLIN}, {fd=18, events=POLLIN}, {fd=19, events=POLLIN}, {fd=20,
events=POLLIN}, {fd=21, events=POLLIN}, {fd=22, events=POLLIN}, {fd=23,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}, {fd=44,
events=POLLIN}, {fd=45, events=POLLIN}, {fd=46, events=POLLIN}, {fd=47,
events=POLLIN}, {fd=48, events=POLLIN}, {fd=49, events=POLLIN}, {fd=50,
events=POLLIN}, {fd=51, events=POLLIN}, {fd=52, events=POLLIN}, {fd=53,
events=POLLIN}, {fd=55, events=POLLOUT}], 28, -1) = 1 ([{fd=55,
revents=POLLNVAL}])

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1717796/comments/13


On 2019-07-22T20:54:45+00:00 steve wrote:

Ahhh...

I was already aware that on first connect the HID input device wasn't
created, but I hadn't realised it's part of the same bug.

What's happening is that on initial connect:

 dev->sec_watch = g_io_add_watch(idev->intr_io, G_IO_OUT,
encrypt_notify, idev);

creates the notify callback.  But it never triggers.  On second
connection the callback gets triggered, but the connect code gets run
again so another refcount is added.  This means the intr channel never
gets closed which means it's stuck on the last event.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1717796/comments/14


On 2019-07-22T21:00:23+00:00 steve wrote:

I flipped the G_IO_OUT to G_IO_IN and it started working on first
connect.  I don't know why it was G_IO_OUT?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1717796/comments/15


On 2019-07-22T23:56:16+00:00 steve wrote:

Created attachment 283925
Patch to fix high CPU usage with HID keyboard and other devices

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1717796/comments/16


On 2019-07-24T11:14:41+00:00 luiz.dentz wrote:

Ive sent a fix upstream:

https://lore.kernel.org/linux-
bluetooth/20190724110151.4258-1-luiz.de...@gmail.com/T/#u

Let me know if that works.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1717796/comments/17


On 2019-07-24T15:31:20+00:00 steve wrote:

(In reply to Luiz Von Dentz from comment #6)
> Ive sent a fix upstream:
> 
> https://lore.kernel.org/linux-bluetooth/20190724110151.4258-1-luiz.
> de...@gmail.com/T/#u
> 
> Let me know if that works.

That will prevent the channel getting left dangling, but it doesn't
address the issue of the callback not happening on initial connect,
which is AFAICT what results in that part of the bug for me.

Is it really supposed to be waiting for G_IO_OUT?  It seems it only gets
triggered for me when a second connection 

[Touch-packages] [Bug 1872802] Re: Resizing any window will randomly result in glitchy appearance for a fraction of a second

2020-04-14 Thread Daniel van Vugt
Interesting two of two reports so far are both on Kaby Lake.

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

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

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

** Changed in: mutter (Ubuntu)
   Status: New => Confirmed

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

Title:
  Resizing any window will randomly result in glitchy appearance for a
  fraction of a second

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
  This glitchy appearance is restored immediately.
  The issue seems to be seen less often when the CPU is utilized more heavily, 
as when I recorded the screen with OBS to grab the screenshot.
  The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.

  No such issues were experienced with previously installed Ubuntu Mate
  or Windows 10.

  Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
  i5-7200U CPU @ 2.50GHz × 4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:45:47 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions

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


[Touch-packages] [Bug 1872791] Re: PulseAudio doesn't see analog output on Dell Inspiron 6400 with STAC9200

2020-04-14 Thread Daniel van Vugt
** Also affects: pulseaudio via
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/852
   Importance: Unknown
   Status: Unknown

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

Title:
  PulseAudio doesn't see analog output on Dell Inspiron 6400 with
  STAC9200

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio currently doesn't see the analog audio output in my Dell
  Inspiron 6400 laptop with Intel HDA STAC9200 audio. It only sees the
  SPDIF output. This is the situation in both "pactl list sinks" and
  pavucontrol. I hear no sound from applications, probably because it's
  going to SPDIF. I don't have a way to listen to SPDIF to see if that
  is indeed the case.

  ALSA sees the analog output and "speaker-test -D plughw:0" plays sound
  through the laptop's speakers.

  This problem never happened in Ubuntu 19.10 and earlier. It might have
  worked earlier in 20.04 also, but I'm not sure of that. Rebooting
  didn't help. Purging and reinstalling pulseaudio and its automatically
  installed dependencies didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-21-generic.
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bgjenero   1414 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 27'
 Mixer name : 'SigmaTel STAC9200'
 Components : 'HDA:83847690,102801bd,00102201 
HDA:14f12bfa,14f100c3,0009'
 Controls  : 22
 Simple ctrls  : 9
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Apr 14 13:37:43 2020
  InstallationDate: Installed on 2012-01-19 (3008 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-04-05 (9 days ago)
  dmi.bios.date: 06/13/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0XD720
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1872791/+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 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-04-14 Thread Matthew Ruffell
Attached is the debdiff for kmod, which removes bochs-drm from the
framebuffer blacklist.

** Patch added: "kmod debdiff for bionic"
   
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1872863/+attachment/5354280/+files/lp1872863_bionic.debdiff

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

Title:
  QEMU/KVM display is garbled when booting from kernel EFI stub due to
  missing bochs-drm module

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in kmod source package in Bionic:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1872863

  [Impact]

  A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the
  kernel EFI stub whenever EFI is enabled. This causes problems for
  QEMU/KVM virtual machines which use the VGA=std video device, as the
  efifb driver yields an unreadable garbled screen. See the attached
  image.

  The correct framebuffer driver to use in this situation is bochs-drm,
  and modprobing it from a HWE kernel fixes the issues.

  bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled
  in LP #1378648 due to bochs-drm causing problems in a PowerKVM
  machine. This problem appears to be fixed now, and bochs-drm has been
  re-enabled for Disco and up, in LP #1795857 and has been proven safe.

  This has also come up again in LP #1823152, as well as chatter on LP
  #1795857 to get this enabled on Bionic.

  The customer which is experiencing this issue cannot switch to VGA=qxl
  as a workaround, and must use VGA=std, hence I suggest we re-enable
  bochs-drm for Bionic.

  [Fix]

  I noticed on Focal, if you boot, the framebuffer is initially efifb:

  [ 0.603716] efifb: probing for efifb
  [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k
  [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1
  [ 0.603736] efifb: scrolling: redraw
  [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
  [ 0.604462] Console: switching to colour frame buffer device 100x37
  [ 0.605829] fb0: EFI VGA frame buffer device

  This soon changes to bochs-drm about a second later:

  [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
0: 0xc000 -> 0xc0ff
  [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
2: 0xc1c8c000 -> 0xc1c8cfff
  [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100)
  [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA
  [ 0.939085] Console: switching to colour dummy device 80x25
  [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console
  [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5.
  [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000.
  [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized
  [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB
  [ 0.942081] [TTM] Initializing pool allocator
  [ 0.942089] [TTM] Initializing DMA pool allocator
  [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 
GB/10.0 GiB)
  [ 0.944019] [drm] Found EDID data blob.
  [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on 
minor 0
  [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device
  [ 0.947712] Console: switching to colour frame buffer device 128x48

  On bionic, the framebuffer never changes from efifb, since the bochs-
  drm kernel module is not built, and it is also present on the module
  banlist in /etc/modprobe.d/blacklist-framebuffer.conf

  bochs-drm needs to be enabled to be built in the kernel config, and
  removed from the module blacklist in kmod.

  [Testcase]

  Create a new QEMU/KVM virtual machine, I used virt-manager. Before you
  install the OS, check the box to modify settings before install. In
  the "Overview" tab, enable EFI by setting the firmware to "UEFI
  x86_64: /usr/share/OVMF/OVMF_CODE.secboot.fd".

  Set the video device to qxl while you install Bionic. Once the install
  is done, reboot, do a "apt update" and "apt upgrade", to ensure you
  have grub2 2.02-2ubuntu8.15 installed.

  Shut the VM down, and set the video device to VGA. Or VGA=std if you
  use the QEMU command line.

  Start the VM up, and the screen will be garbled. See attached picture.

  If you install my test packages, which are available here:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test

  Instructions to install (on a bionic system):

  1) sudo add-apt-repository ppa:mruffell/sf272653-test
  2) sudo apt-get update
  3) sudo apt install linux-image-unsigned-4.15.0-96-generic 
linux-modules-4.15.0-96-generic linux-modules-extra-4.15.0-96-generic 
linux-headers-4.15.0-96-generic linux-headers-4.15.0-96 libkmod2 kmod
  4) sudo reboot
  5) uname -rv
  

[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-04-14 Thread Matthew Ruffell
Submitted Kernel patches to mailing list:

https://lists.ubuntu.com/archives/kernel-team/2020-April/109027.html
https://lists.ubuntu.com/archives/kernel-team/2020-April/109028.html

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

Title:
  QEMU/KVM display is garbled when booting from kernel EFI stub due to
  missing bochs-drm module

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in kmod source package in Bionic:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1872863

  [Impact]

  A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the
  kernel EFI stub whenever EFI is enabled. This causes problems for
  QEMU/KVM virtual machines which use the VGA=std video device, as the
  efifb driver yields an unreadable garbled screen. See the attached
  image.

  The correct framebuffer driver to use in this situation is bochs-drm,
  and modprobing it from a HWE kernel fixes the issues.

  bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled
  in LP #1378648 due to bochs-drm causing problems in a PowerKVM
  machine. This problem appears to be fixed now, and bochs-drm has been
  re-enabled for Disco and up, in LP #1795857 and has been proven safe.

  This has also come up again in LP #1823152, as well as chatter on LP
  #1795857 to get this enabled on Bionic.

  The customer which is experiencing this issue cannot switch to VGA=qxl
  as a workaround, and must use VGA=std, hence I suggest we re-enable
  bochs-drm for Bionic.

  [Fix]

  I noticed on Focal, if you boot, the framebuffer is initially efifb:

  [ 0.603716] efifb: probing for efifb
  [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k
  [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1
  [ 0.603736] efifb: scrolling: redraw
  [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
  [ 0.604462] Console: switching to colour frame buffer device 100x37
  [ 0.605829] fb0: EFI VGA frame buffer device

  This soon changes to bochs-drm about a second later:

  [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
0: 0xc000 -> 0xc0ff
  [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
2: 0xc1c8c000 -> 0xc1c8cfff
  [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100)
  [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA
  [ 0.939085] Console: switching to colour dummy device 80x25
  [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console
  [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5.
  [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000.
  [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized
  [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB
  [ 0.942081] [TTM] Initializing pool allocator
  [ 0.942089] [TTM] Initializing DMA pool allocator
  [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 
GB/10.0 GiB)
  [ 0.944019] [drm] Found EDID data blob.
  [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on 
minor 0
  [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device
  [ 0.947712] Console: switching to colour frame buffer device 128x48

  On bionic, the framebuffer never changes from efifb, since the bochs-
  drm kernel module is not built, and it is also present on the module
  banlist in /etc/modprobe.d/blacklist-framebuffer.conf

  bochs-drm needs to be enabled to be built in the kernel config, and
  removed from the module blacklist in kmod.

  [Testcase]

  Create a new QEMU/KVM virtual machine, I used virt-manager. Before you
  install the OS, check the box to modify settings before install. In
  the "Overview" tab, enable EFI by setting the firmware to "UEFI
  x86_64: /usr/share/OVMF/OVMF_CODE.secboot.fd".

  Set the video device to qxl while you install Bionic. Once the install
  is done, reboot, do a "apt update" and "apt upgrade", to ensure you
  have grub2 2.02-2ubuntu8.15 installed.

  Shut the VM down, and set the video device to VGA. Or VGA=std if you
  use the QEMU command line.

  Start the VM up, and the screen will be garbled. See attached picture.

  If you install my test packages, which are available here:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test

  Instructions to install (on a bionic system):

  1) sudo add-apt-repository ppa:mruffell/sf272653-test
  2) sudo apt-get update
  3) sudo apt install linux-image-unsigned-4.15.0-96-generic 
linux-modules-4.15.0-96-generic linux-modules-extra-4.15.0-96-generic 
linux-headers-4.15.0-96-generic linux-headers-4.15.0-96 libkmod2 kmod
  4) sudo reboot
  5) uname -rv
  4.15.0-96-generic #97+TEST272653v20200409b1-Ubuntu SMP Thu Apr 9 04:09:18 UTC 
2020


[Touch-packages] [Bug 1872788] Re: super key searching show incomplete icon

2020-04-14 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1869571 ***
https://bugs.launchpad.net/bugs/1869571

Yeah the attached Xrandr.txt shows this is another variation on bug
1869571.

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** This bug has been marked a duplicate of bug 1869571
   Vertical dual monitor setup with main monitor on bottom causes overview to 
only use one eigth of screen

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

Title:
  super key searching show incomplete icon

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  compare to bionic, bionic will show complete icon when I press super
  key and type prefix of application.

  But in Focal, the icon is incomplete as attache screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.6.0-1007.7-oem 5.6.2
  Uname: Linux 5.6.0-1007-oem x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 01:37:30 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
  InstallationDate: Installed on 2020-04-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411)
  MachineType: Dell Inc. XPS 13 9380
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1007-oem 
root=UUID=0b23d7d3-fb6c-4ee1-9681-71d148d364d1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872788/+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 1872864] Re: appstream metadata not created

2020-04-14 Thread Ken VanDine
** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

** Changed in: ubuntu-meta (Ubuntu)
   Importance: Undecided => Critical

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Triaged

** Changed in: ubuntu-meta (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  appstream metadata not created

Status in snap-store:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  The gnome-software packaged depends on appstream, which was bringing
  in that binary package in previous releases.  With the switch to
  seeding the snap this is causing a problem with the appstream cache
  never getting populated.  The appstream package includes an apt config
  that triggered the appstream cache refresh after update.  We need to
  explicitly seed the appstream package in ubuntu-desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-store/+bug/1872864/+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 1872146] Re: Audio on Headphones stopped working

2020-04-14 Thread Daniel van Vugt
Please try moving or deleting your:  ~/.config/pulse
and then log out and in again.

Does audio device selection now work?

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

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

Title:
  Audio on Headphones stopped working

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Audio via my headphones worked yesterday, Today no such luck.

  When I plug in my headphone, Plasma picks it up but no sound.

  Bluetooth headset still works.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Fri Apr 10 23:03:09 2020
  InstallationDate: Installed on 2020-04-05 (5 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200404)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872146/+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 1872561] Re: apport-bug crashes when launched

2020-04-14 Thread Panos Asproulis
** Changed in: apport (Ubuntu)
   Status: New => Fix Released

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

Title:
  apport-bug crashes when launched

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  When trying to run apport-bug on Focal the application crashes:

  $ apport-bug python
  Gdk-Message: 01:49:45.090: Window 0x20f7270 is a temporary window without 
parent, application will not be able to position it on screen.
  Gdk-Message: 01:49:45.090: Window 0x20f7270 is a temporary window without 
parent, application will not be able to position it on screen.
  Gdk-Message: 01:49:45.090: Window 0x20f7270 is a temporary window without 
parent, application will not be able to position it on screen.
  Gdk-Message: 01:49:45.090: Window 0x20f7270 is a temporary window without 
parent, application will not be able to position it on screen.
  ERROR: AttributeError("'NoneType' object has no attribute 'origins'")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1872561/+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 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acc

2020-04-14 Thread Panos Asproulis
This worked for me! Thank you.

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

Title:
  libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client
  with error "Error performing TLS handshake: The Diffie-Hellman prime
  sent by the server is not acceptable (not long enough)."

Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  Confirmed
Status in gnutls28 package in Ubuntu:
  Incomplete

Bug description:
  After upgrade to 20.04 package libgnutls30 broke pulseUI VPN client
  with the following error:

  "Error performing TLS handshake: The Diffie-Hellman prime sent by the
  server is not acceptable (not long enough)."

  I had to revert the package to the 19.10 version (3.6.9-5ubuntu1) and
  to install 19.10 dependency libhogweed4 3.4.1-1 to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgnutls30 3.6.9-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Tue Jan 21 17:48:39 2020
  InstallationDate: Installed on 2017-06-21 (943 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnutls28
  UpgradeStatus: Upgraded to focal on 2020-01-10 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+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 1717796] Re: Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle

2020-04-14 Thread Daniel van Vugt
** Tags added: eoan

** Changed in: bluez (Ubuntu)
   Status: Expired => Confirmed

** Changed in: ubuntu-power-consumption
   Status: Expired => Confirmed

** Bug watch added: Linux Kernel Bug Tracker #204275
   https://bugzilla.kernel.org/show_bug.cgi?id=204275

** Also affects: bluez via
   https://bugzilla.kernel.org/show_bug.cgi?id=204275
   Importance: Unknown
   Status: Unknown

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

Title:
  Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle

Status in Bluez Utilities:
  Unknown
Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  When bluetooth keyboard goes in idle bluetoothd fills 100% CPU. At
  this point you have to press any key to reconnect the device and let
  bluetoothd to return to work normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sun Sep 17 19:02:40 2017
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2016-08-06 (406 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: GIGABYTE GB-BXBT-2807
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic.efi.signed 
root=UUID=8931ead4-8d43-4aef-8946-c7845c63c7d3 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F8
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MZBAYAP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF8:bd10/22/2015:svnGIGABYTE:pnGB-BXBT-2807:pvr1.x:rvnGIGABYTE:rnMZBAYAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GB-BXBT-2807
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: DC:85:DE:FD:2F:BC  ACL MTU: 820:8  SCO MTU: 255:16
UP RUNNING PSCAN ISCAN 
RX bytes:528225 acl:32183 sco:0 events:1134 errors:0
TX bytes:33849 acl:338 sco:0 commands:388 errors:1

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1717796/+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 1871695] Re: Bluetoothd uses 100% of a CPU thread

2020-04-14 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1717796 ***
https://bugs.launchpad.net/bugs/1717796

Thanks. This sounds kind of like bug 1717796 so that is now reopened.
It's also active with the upstream developers.

** This bug has been marked a duplicate of bug 1717796
   Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle

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

Title:
  Bluetoothd uses 100% of a CPU thread

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I have a bluetooth keyboard that I use for my laptop, which runs
  Kubuntu 19.04. I noticed though, that a short while after connecting
  the keyboard, the CPU fan goes on and one of the threads is at 100%.
  If I open a terminal and type "top", it shows that a process called
  bluetoothd is taking 12% of the CPU power which is a full thread
  (100/8=12.5). I'm not sure what it's doing, but it doesn't require
  that much CPU power to work. If I end the process and restart it, the
  keyboard works fine and the CPU is calm until it happens again (about
  20 minutes later). I reinstalled bluez and even tried recompiling from
  source, but the problem persists.

  My specs:

  Version of bluetoothd: 5.50
  Linux Kernel: 5.3.0-46-generic
  KDE Plasma Version 5.16.5


  Thank you,
  Isaac Cohen
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-12-15 (115 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:5301 HTMicroelectronics Goodix Fingerprint 
Device 
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3583
  Package: bluez 5.50-0ubuntu5.1 [modified: 
lib/systemd/system/bluetooth.service lib/udev/hid2hci 
lib/udev/rules.d/97-hid2hci.rules]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=dad855bd-aa2f-4675-a8a6-6fa960525f41 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Tags:  eoan
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0WHCP7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd05/30/2019:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0WHCP7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3583
  dmi.product.sku: 08CA
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: AC:D5:64:CC:54:D6  ACL MTU: 1024:8  SCO MTU: 50:8
UP RUNNING PSCAN ISCAN 
RX bytes:47194 acl:2390 sco:0 events:266 errors:0
TX bytes:3046 acl:50 sco:0 commands:163 errors:0
  mtime.conffile..etc.dbus-1.system.d.bluetooth.conf: 2020-04-07T16:35:14.446062

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871695/+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 1872869] [NEW] package gnome-icon-theme-full (not installed) failed to install/upgrade: cannot copy extracted data for './usr/share/icons/gnome/48x48/actions/insert-object.png' t

2020-04-14 Thread Lukasz Masiukiewicz
Public bug reported:

This error occurred while installing xubuntu-desktop.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: gnome-icon-theme-full (not installed)
ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167
Uname: Linux 4.4.0-142-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
Date: Tue Apr 14 21:25:50 2020
DuplicateSignature: package:gnome-icon-theme-full:(not installed):cannot copy 
extracted data for './usr/share/icons/gnome/48x48/actions/insert-object.png' to 
'/usr/share/icons/gnome/48x48/actions/insert-object.png.dpkg-new': unexpected 
end of file or stream
ErrorMessage: cannot copy extracted data for 
'./usr/share/icons/gnome/48x48/actions/insert-object.png' to 
'/usr/share/icons/gnome/48x48/actions/insert-object.png.dpkg-new': unexpected 
end of file or stream
InstallationDate: Installed on 2020-04-13 (1 days ago)
InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release amd64 (20190304.5)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.8
 apt  1.0.1ubuntu2.20
SourcePackage: gnome-icon-theme
Title: package gnome-icon-theme-full (not installed) failed to install/upgrade: 
cannot copy extracted data for 
'./usr/share/icons/gnome/48x48/actions/insert-object.png' to 
'/usr/share/icons/gnome/48x48/actions/insert-object.png.dpkg-new': unexpected 
end of file or stream
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-icon-theme (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package gnome-icon-theme-full (not installed) failed to
  install/upgrade: cannot copy extracted data for
  './usr/share/icons/gnome/48x48/actions/insert-object.png' to
  '/usr/share/icons/gnome/48x48/actions/insert-object.png.dpkg-new':
  unexpected end of file or stream

Status in gnome-icon-theme package in Ubuntu:
  New

Bug description:
  This error occurred while installing xubuntu-desktop.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gnome-icon-theme-full (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Tue Apr 14 21:25:50 2020
  DuplicateSignature: package:gnome-icon-theme-full:(not installed):cannot copy 
extracted data for './usr/share/icons/gnome/48x48/actions/insert-object.png' to 
'/usr/share/icons/gnome/48x48/actions/insert-object.png.dpkg-new': unexpected 
end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/share/icons/gnome/48x48/actions/insert-object.png' to 
'/usr/share/icons/gnome/48x48/actions/insert-object.png.dpkg-new': unexpected 
end of file or stream
  InstallationDate: Installed on 2020-04-13 (1 days ago)
  InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release amd64 
(20190304.5)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.20
  SourcePackage: gnome-icon-theme
  Title: package gnome-icon-theme-full (not installed) failed to 
install/upgrade: cannot copy extracted data for 
'./usr/share/icons/gnome/48x48/actions/insert-object.png' to 
'/usr/share/icons/gnome/48x48/actions/insert-object.png.dpkg-new': unexpected 
end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/1872869/+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 1872869] Re: package gnome-icon-theme-full (not installed) failed to install/upgrade: cannot copy extracted data for './usr/share/icons/gnome/48x48/actions/insert-object.png' to

2020-04-14 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package gnome-icon-theme-full (not installed) failed to
  install/upgrade: cannot copy extracted data for
  './usr/share/icons/gnome/48x48/actions/insert-object.png' to
  '/usr/share/icons/gnome/48x48/actions/insert-object.png.dpkg-new':
  unexpected end of file or stream

Status in gnome-icon-theme package in Ubuntu:
  New

Bug description:
  This error occurred while installing xubuntu-desktop.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gnome-icon-theme-full (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Tue Apr 14 21:25:50 2020
  DuplicateSignature: package:gnome-icon-theme-full:(not installed):cannot copy 
extracted data for './usr/share/icons/gnome/48x48/actions/insert-object.png' to 
'/usr/share/icons/gnome/48x48/actions/insert-object.png.dpkg-new': unexpected 
end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/share/icons/gnome/48x48/actions/insert-object.png' to 
'/usr/share/icons/gnome/48x48/actions/insert-object.png.dpkg-new': unexpected 
end of file or stream
  InstallationDate: Installed on 2020-04-13 (1 days ago)
  InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release amd64 
(20190304.5)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.20
  SourcePackage: gnome-icon-theme
  Title: package gnome-icon-theme-full (not installed) failed to 
install/upgrade: cannot copy extracted data for 
'./usr/share/icons/gnome/48x48/actions/insert-object.png' to 
'/usr/share/icons/gnome/48x48/actions/insert-object.png.dpkg-new': unexpected 
end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/1872869/+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 1872791] Re: PulseAudio doesn't see analog output on Dell Inspiron 6400 with STAC9200

2020-04-14 Thread Boris Gjenero
I did some more investigation and found that without the workaround the
analog output only appears while headphones are plugged in. The SPDIF
output disappears while headphones are plugged in.

The bug has been submitted with this new information at
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/852

** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #852
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/852

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

Title:
  PulseAudio doesn't see analog output on Dell Inspiron 6400 with
  STAC9200

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio currently doesn't see the analog audio output in my Dell
  Inspiron 6400 laptop with Intel HDA STAC9200 audio. It only sees the
  SPDIF output. This is the situation in both "pactl list sinks" and
  pavucontrol. I hear no sound from applications, probably because it's
  going to SPDIF. I don't have a way to listen to SPDIF to see if that
  is indeed the case.

  ALSA sees the analog output and "speaker-test -D plughw:0" plays sound
  through the laptop's speakers.

  This problem never happened in Ubuntu 19.10 and earlier. It might have
  worked earlier in 20.04 also, but I'm not sure of that. Rebooting
  didn't help. Purging and reinstalling pulseaudio and its automatically
  installed dependencies didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-21-generic.
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bgjenero   1414 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 27'
 Mixer name : 'SigmaTel STAC9200'
 Components : 'HDA:83847690,102801bd,00102201 
HDA:14f12bfa,14f100c3,0009'
 Controls  : 22
 Simple ctrls  : 9
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Apr 14 13:37:43 2020
  InstallationDate: Installed on 2012-01-19 (3008 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-04-05 (9 days ago)
  dmi.bios.date: 06/13/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0XD720
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872791/+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 1872842] Re: PCI/internal sound card not detected

2020-04-14 Thread Hui Wang
Is there an audio enable option in the BIOS? Maybe it is disabled?

Or the codec is damaged physically? You could install the newer kernel
to verify if the codec is good or not, if it is good and newer kernel
could work, then we will bisect the kernel to find the fix for this
issue.

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Upsstream says try a newer kernel, but I am on the LTS HWE kernels for
  Xenial, and want to solve this on this version.  This is a Think
  Centre M710e Model/Type 10UR, and the snd_hba_intel correctly loads,
  but finds no codecs.  This is the onboard audio card, and don't think
  they have chnaged it much in years, so I expect that at least SOME
  codecs should be detected.  Played with various alsa conf settings, no
  joy..

  options snd-hda-intel single_cmd=1
  options snd-hda-intel probe_mask=1
  options snd-hda-intel model=thinkpad
  options snd-hda-intel position_fix=3

  Tried model(s) generic, and auto.. always the same in bootup..

  [   12.684107] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [   12.827419] snd_hda_intel :00:1f.3: CORB reset timeout#1, CORBRP = 0
  [   12.830129] snd_hda_intel :00:1f.3: no codecs found!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-96.97~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: X-Cinnamon
  Date: Tue Apr 14 15:00:59 2020
  InstallationDate: Installed on 2019-11-03 (163 days ago)
  InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190226)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M1ZKT23A
  dmi.board.name: 313C
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN 3305181519567
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM1ZKT23A:bd06/05/2018:svnLENOVO:pn10UR001JUS:pvrThinkCentreM710e:rvnLENOVO:rn313C:rvrSDK0J40697WIN3305181519567:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710e
  dmi.product.name: 10UR001JUS
  dmi.product.version: ThinkCentre M710e
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-13T16:09:19.881423

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1872842/+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 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-04-14 Thread Matthew Ruffell
** Description changed:

  BugLink: https://bugs.launchpad.net/bugs/1872863
  
  [Impact]
  
  A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the
  kernel EFI stub whenever EFI is enabled. This causes problems for
  QEMU/KVM virtual machines which use the VGA=std video device, as the
  efifb driver yields an unreadable garbled screen. See the attached
  image.
  
  The correct framebuffer driver to use in this situation is bochs-drm,
  and modprobing it from a HWE kernel fixes the issues.
  
  bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled in
  LP #1378648 due to bochs-drm causing problems in a PowerKVM machine.
  This problem appears to be fixed now, and bochs-drm has been re-enabled
  for Disco and up, in LP #1795857 and has been proven safe.
  
  This has also come up again in LP #1823152, as well as chatter on LP
  #1795857 to get this enabled on Bionic.
  
  The customer which is experiencing this issue cannot switch to VGA=qxl
  as a workaround, and must use VGA=std, hence I suggest we re-enable
  bochs-drm for Bionic.
  
  [Fix]
  
  I noticed on Focal, if you boot, the framebuffer is initially efifb:
  
  [ 0.603716] efifb: probing for efifb
  [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k
  [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1
  [ 0.603736] efifb: scrolling: redraw
  [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
  [ 0.604462] Console: switching to colour frame buffer device 100x37
  [ 0.605829] fb0: EFI VGA frame buffer device
  
  This soon changes to bochs-drm about a second later:
  
  [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
0: 0xc000 -> 0xc0ff
  [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
2: 0xc1c8c000 -> 0xc1c8cfff
  [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100)
  [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA
  [ 0.939085] Console: switching to colour dummy device 80x25
  [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console
  [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5.
  [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000.
  [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized
  [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB
  [ 0.942081] [TTM] Initializing pool allocator
  [ 0.942089] [TTM] Initializing DMA pool allocator
  [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 
GB/10.0 GiB)
  [ 0.944019] [drm] Found EDID data blob.
  [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on 
minor 0
  [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device
  [ 0.947712] Console: switching to colour frame buffer device 128x48
  
  On bionic, the framebuffer never changes from efifb, since the bochs-drm
  kernel module is not built, and it is also present on the module banlist
  in /etc/modprobe.d/blacklist-framebuffer.conf
  
  bochs-drm needs to be enabled to be built in the kernel config, and
  removed from the module blacklist in kmod.
  
  [Testcase]
  
  Create a new QEMU/KVM virtual machine, I used virt-manager. Before you
  install the OS, check the box to modify settings before install. In the
  "Overview" tab, enable EFI by setting the firmware to "UEFI x86_64:
  /usr/share/OVMF/OVMF_CODE.secboot.fd".
  
  Set the video device to qxl while you install Bionic. Once the install
  is done, reboot, do a "apt update" and "apt upgrade", to ensure you have
  grub2 2.02-2ubuntu8.15 installed.
  
  Shut the VM down, and set the video device to VGA. Or VGA=std if you use
  the QEMU command line.
  
  Start the VM up, and the screen will be garbled. See attached picture.
  
  If you install my test packages, which are available here:
  
  https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test
  
  Instructions to install (on a bionic system):
  
  1) sudo add-apt-repository ppa:mruffell/sf272653-test
  2) sudo apt-get update
  3) sudo apt install linux-image-unsigned-4.15.0-96-generic 
linux-modules-4.15.0-96-generic linux-modules-extra-4.15.0-96-generic 
linux-headers-4.15.0-96-generic linux-headers-4.15.0-96 libkmod2 kmod
  4) sudo reboot
  5) uname -rv
  4.15.0-96-generic #97+TEST272653v20200409b1-Ubuntu SMP Thu Apr 9 04:09:18 UTC 
2020
  
  If you reboot, the screen will be perfectly readable, since the bochs-
  drm driver will be in use.
  
  [Regression Potential]
  
  We are enabling a display driver on Bionic which was previously
  disabled, so there will be some virtual machines making the jump to
  using bochs-drm since it would now be available.
  
  I don't think that this is a bad thing, and in many ways will probably
  end up improving some user's experience. Although there are two
  scenarios where a regression could happen:
  
- 1 - frequently gamers use GPU passthrough to their Windows based virtual
+ 1 - frequently gamers use GPU 

[Touch-packages] [Bug 1872586] Re: firefox won't display WEBGL web page in 20.04 ok in 19.10

2020-04-14 Thread Launchpad Bug Tracker
This bug was fixed in the package libdrm - 2.4.101-2

---
libdrm (2.4.101-2) unstable; urgency=medium

  * fix-realpath-vs-firefox.diff: Fix webgl on intel with firefox.
(Closes: #956665) (LP: #1872586)

 -- Timo Aaltonen   Tue, 14 Apr 2020 16:32:57 +0300

** Changed in: libdrm (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  firefox won't display WEBGL web page in 20.04 ok in 19.10

Status in libdrm package in Ubuntu:
  Fix Released

Bug description:
  When I open a website using WEBGL, firefox displays a message that the 
browser does not
  support GL. The GL support is enabled in firefox. The command line displays:

  libGL error: MESA-LOADER: failed to retrieve device information
  libGL error: Version 4 or later of flush extension not found
  libGL error: failed to load driver: i915
  libGL error: MESA-LOADER: failed to retrieve device information

  This happens in Ubuntu 20.04 beta. In Ubuntu 19.10 with the same browser and
  browser settings, the website is displayed correctly. Chromium displays the
  same page correctly both on 19.10 and 20.04.

  Sample website: www.geocaching.com/play/map

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 75.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dick   1252 F pulseaudio
  BuildID: 20200403170909
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 13 23:20:24 2020
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-03-04 (40 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.1.1 dev enp2s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.243 metric 
100
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profile2Extensions: extensions.sqlite corrupt or missing
  Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile2Locales: extensions.sqlite corrupt or missing
  Profile2PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile2PrefSources: prefs.js
  Profile2Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=75.0/20200403170909 (In use)
   Profile2 - LastVersion=75.0/20200403170909
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to focal on 2020-04-13 (0 days ago)
  dmi.bios.date: 05/10/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.10.0
  dmi.board.name: 0C0JMC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.10.0:bd05/10/2019:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0C0JMC:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1872586/+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 1872863] [NEW] QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-04-14 Thread Matthew Ruffell
Public bug reported:

BugLink: https://bugs.launchpad.net/bugs/1872863

[Impact]

A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the
kernel EFI stub whenever EFI is enabled. This causes problems for
QEMU/KVM virtual machines which use the VGA=std video device, as the
efifb driver yields an unreadable garbled screen. See the attached
image.

The correct framebuffer driver to use in this situation is bochs-drm,
and modprobing it from a HWE kernel fixes the issues.

bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled in
LP #1378648 due to bochs-drm causing problems in a PowerKVM machine.
This problem appears to be fixed now, and bochs-drm has been re-enabled
for Disco and up, in LP #1795857 and has been proven safe.

This has also come up again in LP #1823152, as well as chatter on LP
#1795857 to get this enabled on Bionic.

The customer which is experiencing this issue cannot switch to VGA=qxl
as a workaround, and must use VGA=std, hence I suggest we re-enable
bochs-drm for Bionic.

[Fix]

I noticed on Focal, if you boot, the framebuffer is initially efifb:

[ 0.603716] efifb: probing for efifb
[ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k
[ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1
[ 0.603736] efifb: scrolling: redraw
[ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 0.604462] Console: switching to colour frame buffer device 100x37
[ 0.605829] fb0: EFI VGA frame buffer device

This soon changes to bochs-drm about a second later:

[ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 0: 
0xc000 -> 0xc0ff
[ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 2: 
0xc1c8c000 -> 0xc1c8cfff
[ 0.937776] checking generic (c000 1d5000) vs hw (c000 100)
[ 0.937776] fb0: switching to bochsdrmfb from EFI VGA
[ 0.939085] Console: switching to colour dummy device 80x25
[ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console
[ 0.939210] [drm] Found bochs VGA, ID 0xb0c5.
[ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000.
[ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized
[ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB
[ 0.942081] [TTM] Initializing pool allocator
[ 0.942089] [TTM] Initializing DMA pool allocator
[ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 
GB/10.0 GiB)
[ 0.944019] [drm] Found EDID data blob.
[ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on 
minor 0
[ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device
[ 0.947712] Console: switching to colour frame buffer device 128x48

On bionic, the framebuffer never changes from efifb, since the bochs-drm
kernel module is not built, and it is also present on the module banlist
in /etc/modprobe.d/blacklist-framebuffer.conf

bochs-drm needs to be enabled to be built in the kernel config, and
removed from the module blacklist in kmod.

[Testcase]

Create a new QEMU/KVM virtual machine, I used virt-manager. Before you
install the OS, check the box to modify settings before install. In the
"Overview" tab, enable EFI by setting the firmware to "UEFI x86_64:
/usr/share/OVMF/OVMF_CODE.secboot.fd".

Set the video device to qxl while you install Bionic. Once the install
is done, reboot, do a "apt update" and "apt upgrade", to ensure you have
grub2 2.02-2ubuntu8.15 installed.

Shut the VM down, and set the video device to VGA. Or VGA=std if you use
the QEMU command line.

Start the VM up, and the screen will be garbled. See attached picture.

If you install my test packages, which are available here:

https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test

Instructions to install (on a bionic system):

1) sudo add-apt-repository ppa:mruffell/sf272653-test
2) sudo apt-get update
3) sudo apt install linux-image-unsigned-4.15.0-96-generic 
linux-modules-4.15.0-96-generic linux-modules-extra-4.15.0-96-generic 
linux-headers-4.15.0-96-generic linux-headers-4.15.0-96 libkmod2 kmod
4) sudo reboot
5) uname -rv
4.15.0-96-generic #97+TEST272653v20200409b1-Ubuntu SMP Thu Apr 9 04:09:18 UTC 
2020

If you reboot, the screen will be perfectly readable, since the bochs-
drm driver will be in use.

[Regression Potential]

We are enabling a display driver on Bionic which was previously
disabled, so there will be some virtual machines making the jump to
using bochs-drm since it would now be available.

I don't think that this is a bad thing, and in many ways will probably
end up improving some user's experience. Although there are two
scenarios where a regression could happen:

1 - frequently gamers use GPU passthrough to their Windows based virtual
machines, and I have seen them expect, or hardcode their kernel command
lines to use the efifb driver. I actually find this strange, as if you
read the kernel documentation, the efifb driver is meant for Apple
Macintosh computers only:

[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-04-14 Thread Matthew Ruffell
Attached is a picture of the garbled screen when VGA=std under booting
via kernel EFI stub.

** Attachment added: "Garbled screen"
   
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1872863/+attachment/5354248/+files/Screenshot%20from%202020-04-15%2012-19-48.png

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

Title:
  QEMU/KVM display is garbled when booting from kernel EFI stub due to
  missing bochs-drm module

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in kmod source package in Bionic:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1872863

  [Impact]

  A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the
  kernel EFI stub whenever EFI is enabled. This causes problems for
  QEMU/KVM virtual machines which use the VGA=std video device, as the
  efifb driver yields an unreadable garbled screen. See the attached
  image.

  The correct framebuffer driver to use in this situation is bochs-drm,
  and modprobing it from a HWE kernel fixes the issues.

  bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled
  in LP #1378648 due to bochs-drm causing problems in a PowerKVM
  machine. This problem appears to be fixed now, and bochs-drm has been
  re-enabled for Disco and up, in LP #1795857 and has been proven safe.

  This has also come up again in LP #1823152, as well as chatter on LP
  #1795857 to get this enabled on Bionic.

  The customer which is experiencing this issue cannot switch to VGA=qxl
  as a workaround, and must use VGA=std, hence I suggest we re-enable
  bochs-drm for Bionic.

  [Fix]

  I noticed on Focal, if you boot, the framebuffer is initially efifb:

  [ 0.603716] efifb: probing for efifb
  [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k
  [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1
  [ 0.603736] efifb: scrolling: redraw
  [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
  [ 0.604462] Console: switching to colour frame buffer device 100x37
  [ 0.605829] fb0: EFI VGA frame buffer device

  This soon changes to bochs-drm about a second later:

  [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
0: 0xc000 -> 0xc0ff
  [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
2: 0xc1c8c000 -> 0xc1c8cfff
  [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100)
  [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA
  [ 0.939085] Console: switching to colour dummy device 80x25
  [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console
  [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5.
  [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000.
  [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized
  [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB
  [ 0.942081] [TTM] Initializing pool allocator
  [ 0.942089] [TTM] Initializing DMA pool allocator
  [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 
GB/10.0 GiB)
  [ 0.944019] [drm] Found EDID data blob.
  [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on 
minor 0
  [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device
  [ 0.947712] Console: switching to colour frame buffer device 128x48

  On bionic, the framebuffer never changes from efifb, since the bochs-
  drm kernel module is not built, and it is also present on the module
  banlist in /etc/modprobe.d/blacklist-framebuffer.conf

  bochs-drm needs to be enabled to be built in the kernel config, and
  removed from the module blacklist in kmod.

  [Testcase]

  Create a new QEMU/KVM virtual machine, I used virt-manager. Before you
  install the OS, check the box to modify settings before install. In
  the "Overview" tab, enable EFI by setting the firmware to "UEFI
  x86_64: /usr/share/OVMF/OVMF_CODE.secboot.fd".

  Set the video device to qxl while you install Bionic. Once the install
  is done, reboot, do a "apt update" and "apt upgrade", to ensure you
  have grub2 2.02-2ubuntu8.15 installed.

  Shut the VM down, and set the video device to VGA. Or VGA=std if you
  use the QEMU command line.

  Start the VM up, and the screen will be garbled. See attached picture.

  If you install my test packages, which are available here:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test

  Instructions to install (on a bionic system):

  1) sudo add-apt-repository ppa:mruffell/sf272653-test
  2) sudo apt-get update
  3) sudo apt install linux-image-unsigned-4.15.0-96-generic 
linux-modules-4.15.0-96-generic linux-modules-extra-4.15.0-96-generic 
linux-headers-4.15.0-96-generic linux-headers-4.15.0-96 libkmod2 kmod
  4) sudo reboot
  5) uname -rv

[Touch-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

2020-04-14 Thread Brian Murray
** Tags added: rls-ff-incoming

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.

  
  It seems like some internal service broke and everything that followed was a 
secondary issue to that:
  Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ...
  Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting.
  Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel ModemManager[1308]:   Caught signal, 
shutting down...
  Apr 08 06:09:19 Keschdeichel systemd[1]: switcheroo-control.service: 
Unexpected error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Leaving mDNS multicast group 
on interface vnet0.IPv6 with address fe80::fc54:ff:fe78:26c2.
  

[Touch-packages] [Bug 1870729] Re: DHCP Server regularly killed code=killed, status=6/ABRT

2020-04-14 Thread Brian Murray
** Also affects: isc-dhcp (Ubuntu Focal)
   Importance: High
 Assignee: Jamie Strandboge (jdstrand)
   Status: In Progress

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

Title:
  DHCP Server regularly killed code=killed, status=6/ABRT

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Focal:
  In Progress

Bug description:
  On Ubuntu 20.04 The idc-dhcp- server version is
  isc-dhcp-server:
Installed: (none)
Candidate: 4.4.1-2.1ubuntu3
Version table:
   4.4.1-2.1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  The DHCP server is being regularly killed, when searching google the  bug 
looks very similar to an older bug regarding accessing a lease file, that was 
fixed year ago. As a temporary fix in systemd I have enabled a restart every 
time the main process fails. The error got worse when i start to run a pair of 
dhcp servers syncing state between each other

  
  I regularly see the following in the syslog

  Apr  4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr  4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ??
  Apr  4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ??
  Apr  4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ??
  Apr  4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ??
  Apr  4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ??
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.
  Apr  4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart 
job, restart counter is at 3.
  Apr  4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400 
audit(1585958700.678:46): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium.
  Apr  4 00:05:00 gw sh[2049]: All rights reserved.
  Apr  4 00:05:00 gw sh[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems 
Consortium.
  Apr  4 00:05:00 gw dhcpd[2049]: All rights reserved.
  Apr  4 00:05:00 gw dhcpd[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400 
audit(1585958700.678:47): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw kernel: [ 3508.161563] audit: type=1400 
audit(1585958700.682:48): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2070/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw sh[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw dhcpd[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Wrote 0 deleted host decls to leases file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1870729/+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 1838329] Re: Cryptswap periodically fails to mount at boot due to missing a udev notification

2020-04-14 Thread Brian Murray
** Tags added: rls-ff-incoming

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

Title:
  Cryptswap periodically fails to mount at boot due to missing a udev
  notification

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  On some systems, cryptsetup-based encrypted swap partitions cause
  systemd to get stuck at boot. This is a timing-sensitive Heisenbug, so
  the rate of occurrence varies from one system to another. Some
  hardware will not experience the issue at all, others will only
  occasionally experience the issue, and then there are the unlucky who
  are unable to boot at all, no matter how many times they restart.

  The workaround is for the cryptsetup-generator to generate cryptswap
  service entries that call `udevadm trigger` after `mkswap`. This will
  ensure that the udev event is triggered, so that systemd is notified
  that the encrypt swap partition is ready to activate. This patch has
  already been submitted upstream to systemd, but it was not accepted
  because it is a workaround for the side effect of systemd not seeing
  the udev event upon creating the swap partition.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1838329/+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 1871695] Re: Bluetoothd uses 100% of a CPU thread

2020-04-14 Thread Isaac Cohen
Now I get this:

isaac@isaac-Inspiron-3583:~$ sudo gdb
[sudo] password for isaac: 
GNU gdb (Ubuntu 8.3-0ubuntu1) 8.3
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) attach 794
Attaching to process 794
Reading symbols from target:/usr/local/libexec/bluetooth/bluetoothd...
Reading symbols from target:/lib/x86_64-linux-gnu/libglib-2.0.so.0...
(No debugging symbols found in target:/lib/x86_64-linux-gnu/libglib-2.0.so.0)
Reading symbols from target:/lib/x86_64-linux-gnu/libdbus-1.so.3...
(No debugging symbols found in target:/lib/x86_64-linux-gnu/libdbus-1.so.3)
Reading symbols from target:/lib/x86_64-linux-gnu/libdl.so.2...
Reading symbols from 
target:/usr/lib/debug//lib/x86_64-linux-gnu/libdl-2.30.so...
Reading symbols from target:/lib/x86_64-linux-gnu/libc.so.6...
Reading symbols from target:/usr/lib/debug//lib/x86_64-linux-gnu/libc-2.30.so...
Reading symbols from target:/lib/x86_64-linux-gnu/libpcre.so.3...
(No debugging symbols found in target:/lib/x86_64-linux-gnu/libpcre.so.3)
Reading symbols from target:/lib/x86_64-linux-gnu/libpthread.so.0...
Reading symbols from 
/usr/lib/debug/.build-id/7f/4107df84da625f1b445ade877e1e0ab6ba823d.debug...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Reading symbols from target:/lib/x86_64-linux-gnu/libsystemd.so.0...
(No debugging symbols found in target:/lib/x86_64-linux-gnu/libsystemd.so.0)
Reading symbols from target:/lib64/ld-linux-x86-64.so.2...
(No debugging symbols found in target:/lib64/ld-linux-x86-64.so.2)
Reading symbols from target:/lib/x86_64-linux-gnu/librt.so.1...
Reading symbols from 
target:/usr/lib/debug//lib/x86_64-linux-gnu/librt-2.30.so...
Reading symbols from target:/lib/x86_64-linux-gnu/liblzma.so.5...
(No debugging symbols found in target:/lib/x86_64-linux-gnu/liblzma.so.5)
Reading symbols from target:/lib/x86_64-linux-gnu/liblz4.so.1...
(No debugging symbols found in target:/lib/x86_64-linux-gnu/liblz4.so.1)
Reading symbols from target:/lib/x86_64-linux-gnu/libgcrypt.so.20...
(No debugging symbols found in target:/lib/x86_64-linux-gnu/libgcrypt.so.20)
Reading symbols from target:/lib/x86_64-linux-gnu/libgpg-error.so.0...
(No debugging symbols found in target:/lib/x86_64-linux-gnu/libgpg-error.so.0)
--Type  for more, q to quit, c to continue without paging--
0x7f888e505f66 in g_main_context_prepare () from 
target:/lib/x86_64-linux-gnu/libglib-2.0.so.0
(gdb) thread apply all bt

Thread 1 (Thread 0x7f888df97c00 (LWP 794)):
#0  0x7f888e505f66 in g_main_context_prepare () from 
target:/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f888e5069db in ?? () from 
target:/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f888e506e33 in g_main_loop_run () from 
target:/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x55b91a835959 in mainloop_run () at src/shared/mainloop-glib.c:79
#4  0x55b91a835dc0 in mainloop_run_with_signal (func=, 
user_data=0x0) at src/shared/mainloop-notify.c:201
#5  0x55b91a79f5fe in main (argc=, argv=) at 
src/main.c:770
(gdb) 


I actually noticed that when I attached the process (or maybe when I
backtracked it), it slowed down or even stopped and the CPU fan went
off. When I closed gdb and detached it, the process resumed once again
taking up lots of CPU power and making the fan go on.

I also noticed that this only happens if I don't use the keyboard for a
while. If the process is busy and I start typing on the keyboard, it
immediately slows down and goes back to normal. I wonder if the keyboard
has a feature that it "goes to sleep". Maybe then the bluetooth program
is  polling for the keyboard and not finding it.


Isaac Cohen

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

Title:
  Bluetoothd uses 100% of a CPU thread

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I have a bluetooth keyboard that I use for my laptop, which runs
  Kubuntu 19.04. I noticed though, that a short while after connecting
  the keyboard, the CPU fan goes on and one of the threads is at 100%.
  If I open a terminal and type "top", it shows that a process called
  bluetoothd is taking 12% of the CPU power which is a full thread
  (100/8=12.5). I'm not sure what it's 

[Touch-packages] [Bug 1604617] Re: dhclient does not send fqdn.fqdn for DHCPv6

2020-04-14 Thread Coops
This issue occurs in Ubuntu 18.04.04 (dhclient 4.3.5), but at some point
by Ubuntu 20.04 beta (dhclient 4.4.1) it seems to now be resolved.

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

Title:
  dhclient does not send fqdn.fqdn for DHCPv6

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  ISC DHCP's dynamic DNS updates rely on the fqdn.fqdn option being sent
  in order to work for DHCPv6.  This used to be done in Ubuntu, as shown
  in bugs #991360 and #108862, and all my Windows hosts send it.
  However this was removed in Ubuntu due to a regression in IPv4
  functionality.

  As IPv6 is more widely deployed these days, this regression in IPv6 should be 
fixed.  This bug is
  current as of Ubuntu 16.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1604617/+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 1780985] Re: apport-unpack crashed with ValueError in extract_keys(): ['ProcEnviron'] has no binary content

2020-04-14 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: apport (Ubuntu)
   Status: New => Confirmed

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

Title:
  apport-unpack crashed with ValueError in extract_keys():
  ['ProcEnviron'] has no binary content

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Sometimes apport creates a crash file with an empty field for
  'ProcEnviron'. In that situation, I want to be able to continue
  extracting fields from the crash file rather than aborting.

  Workaround is to add some made up values for ProcEnviron in the crash file, 
such as " LANG=en_US.UTF-8
  ".

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Jul 10 08:02:35 2018
  ExecutablePath: /usr/bin/apport-unpack
  InstallationDate: Installed on 2018-04-27 (73 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/apport-unpack 
/var/crash/_usr_bin_kdeinit5.1000.crash crash_files/
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonArgs: ['/usr/bin/apport-unpack', 
'/var/crash/_usr_bin_kdeinit5.1000.crash', 'crash_files/']
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  SourcePackage: apport
  Title: apport-unpack crashed with ValueError in extract_keys(): 
['ProcEnviron'] has no binary content
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio bluetooth cdrom dialout dip floppy lpadmin netdev 
plugdev sambashare scanner sudo systemd-journal tty vboxusers video wireshark
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-05-18T07:41:41.681859

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1780985/+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 1872842] [NEW] PCI/internal sound card not detected

2020-04-14 Thread Michael
Public bug reported:

Upsstream says try a newer kernel, but I am on the LTS HWE kernels for
Xenial, and want to solve this on this version.  This is a Think Centre
M710e Model/Type 10UR, and the snd_hba_intel correctly loads, but finds
no codecs.  This is the onboard audio card, and don't think they have
chnaged it much in years, so I expect that at least SOME codecs should
be detected.  Played with various alsa conf settings, no joy..

options snd-hda-intel single_cmd=1
options snd-hda-intel probe_mask=1
options snd-hda-intel model=thinkpad
options snd-hda-intel position_fix=3

Tried model(s) generic, and auto.. always the same in bootup..

[   12.684107] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[   12.827419] snd_hda_intel :00:1f.3: CORB reset timeout#1, CORBRP = 0
[   12.830129] snd_hda_intel :00:1f.3: no codecs found!

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-96.97~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-96-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.23
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: X-Cinnamon
Date: Tue Apr 14 15:00:59 2020
InstallationDate: Installed on 2019-11-03 (163 days ago)
InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190226)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/05/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: M1ZKT23A
dmi.board.name: 313C
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305181519567
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrM1ZKT23A:bd06/05/2018:svnLENOVO:pn10UR001JUS:pvrThinkCentreM710e:rvnLENOVO:rn313C:rvrSDK0J40697WIN3305181519567:cvnLENOVO:ct3:cvrNone:
dmi.product.family: ThinkCentre M710e
dmi.product.name: 10UR001JUS
dmi.product.version: ThinkCentre M710e
dmi.sys.vendor: LENOVO
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-13T16:09:19.881423

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Upsstream says try a newer kernel, but I am on the LTS HWE kernels for
  Xenial, and want to solve this on this version.  This is a Think
  Centre M710e Model/Type 10UR, and the snd_hba_intel correctly loads,
  but finds no codecs.  This is the onboard audio card, and don't think
  they have chnaged it much in years, so I expect that at least SOME
  codecs should be detected.  Played with various alsa conf settings, no
  joy..

  options snd-hda-intel single_cmd=1
  options snd-hda-intel probe_mask=1
  options snd-hda-intel model=thinkpad
  options snd-hda-intel position_fix=3

  Tried model(s) generic, and auto.. always the same in bootup..

  [   12.684107] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [   12.827419] snd_hda_intel :00:1f.3: CORB reset timeout#1, CORBRP = 0
  [   12.830129] snd_hda_intel :00:1f.3: no codecs found!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-96.97~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: X-Cinnamon
  Date: Tue Apr 14 15:00:59 2020
  InstallationDate: Installed on 2019-11-03 (163 days ago)
  InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190226)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M1ZKT23A
  dmi.board.name: 313C
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN 3305181519567
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM1ZKT23A:bd06/05/2018:svnLENOVO:pn10UR001JUS:pvrThinkCentreM710e:rvnLENOVO:rn313C:rvrSDK0J40697WIN3305181519567:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710e
  dmi.product.name: 10UR001JUS
  dmi.product.version: ThinkCentre M710e
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-13T16:09:19.881423

To manage notifications about this 

[Touch-packages] [Bug 1866974] Re: The Diffie-Hellman prime sent by the server is not acceptable

2020-04-14 Thread Steven Jay Cohen
*** This bug is a duplicate of bug 1872778 ***
https://bugs.launchpad.net/bugs/1872778

Thank you Simon Déziel! That worked. I couldn't quite figure that out on
my own.

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

Title:
  The Diffie-Hellman prime sent by the server is not acceptable

Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  I can no longer connect to my ISP mail server.
  Works in previous version 19.10

  "The reported error was “Failed to get capabilities: Error performing
  TLS handshake: The Diffie-Hellman prime sent by the server is not
  acceptable (not long enough).”."

  I've tried finding a workaround but so far no luck.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: evolution 3.35.92-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 11:07:01 2020
  InstallationDate: Installed on 2020-03-03 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974/+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 1872227] Re: Ubuntu bugs cannot be reported because of obsolete package versions, but everything is up-to-date

2020-04-14 Thread Lyubomir Parvanov
Why would this be an invalid bug? There is an other program crashing and
the crash report cannot be submitted because of gnome-shell? What if
there are 4 months left till next Ubuntu release which will actually
update the gnome-shell?

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

Title:
  Ubuntu bugs cannot be reported because of obsolete package versions,
  but everything is up-to-date

Status in apport package in Ubuntu:
  Invalid

Bug description:
  I had at least two or three crashes, and they cannot be submitted
  because some "obsolete package versions" have been found. However,
  under my update settings every update source is activated, and there
  are no updates (i checked ASAP after the crash report). I reported it
  here because there was no section for "updates" in "Find right
  package" on Ubuntu wiki. This bug might be very dangerous if it is
  experiences on many machines - other bugs will be missing bug reports.

  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15.4
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 11 21:35:19 2020
  InstallationDate: Installed on 2020-02-08 (63 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1872227/+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 1872825] Re: nm-online crashed with SIGSEGV in g_source_set_ready_time()

2020-04-14 Thread Apport retracing service
*** This bug is a duplicate of bug 1866783 ***
https://bugs.launchpad.net/bugs/1866783

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1866783, so 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.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1872825/+attachment/5354154/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1872825/+attachment/5354156/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1872825/+attachment/5354166/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1872825/+attachment/5354167/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1872825/+attachment/5354168/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1872825/+attachment/5354170/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1872825/+attachment/5354171/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1866783

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nm-online crashed with SIGSEGV in g_source_set_ready_time()

Status in network-manager package in Ubuntu:
  New

Bug description:
  can't find kernel on boot

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr 14 15:36:00 2020
  ExecutablePath: /usr/bin/nm-online
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411)
  IpRoute:
   default via 192.168.43.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.43.0/24 dev wlp2s0 proto kernel scope link src 192.168.43.91 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcCmdline: /usr/bin/nm-online -s -q --timeout=30
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f8526942bf3 :   cmp
0x10(%rax),%rbp
   PC (0x7f8526942bf3) ok
   source "0x10(%rax)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   g_source_set_ready_time () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nm-online crashed with SIGSEGV in g_source_set_ready_time()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1872825/+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 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version

2020-04-14 Thread Launchpad Bug Tracker
This bug was fixed in the package alsa-lib - 1.1.3-5ubuntu0.5

---
alsa-lib (1.1.3-5ubuntu0.5) bionic; urgency=medium

  * d/p/0020-add-bios-version-for-looking-for-ucm.patch
Add a new way to looking for the ucm by DMI bios_version.
Without this patch, the alsa-lib looks for the ucm by cardlongname
first, if it fails, then by the cardname. This has a problem at least
on LENOVO machines, since a LENOVO model has the same audio design but
it has hundreds of cardlongname, we need to create hundreds of folders
for one model, that is unacceptable. LENOVO told us a LENOVO model has
the unique biso_version, we could use it to find the ucm. After applying
this patch, the alsa-lib looks for the ucm by cardlongname first, if it
fails, it will use bios_version, if it also fails, it will fallback to
cardname.
(LP: #1868210)

 -- Hui Wang   Fri, 27 Mar 2020 10:26:30 +0800

** Changed in: alsa-lib (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 alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1868210

Title:
  [SRU] Load ucm on Lenovo notebooks based on bios version

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Fix Released
Status in alsa-lib source package in Eoan:
  Fix Released
Status in alsa-lib source package in Focal:
  Invalid

Bug description:
  This SRU is not backported from upstream of alsa-lib and this SRU is
  not going to be submitted to upstream. That is because the latest
  alsa-lib already supports ucm2, and with ucm2 all machines could share
  one ucm, so latest alsa-lib does not have this problem. This problem
  is only specific to the alsa-lib in Bionic and Eoan.

  [Impact]
  On some Lenovo notebooks, UCM files are not loaded and mic can't be used.

  [Fix]
  UCM was loaded based on cardlongname, but that can't cover all configs of the 
same model. Lenovo suggested to load  ucm by the first 3 letters of 
/sys/devices/virtual/dmi/id/bios_version, so that all configs could use just 
one ucm.

  [Test Case]
  After applying this patch, install the testing alsa-lib on Lenovo X1C7 and 
Dell vostro 5390, which are all machines with the DMIC connected to PCH. After 
system bootup, check the /usr/share/alsa/ucm/ for the presence of 
LENOVO-BIOSID-xxx directories.

  Lenovo X1C7 should load the N2H/*.conf and verify the audio
  functionalities. The Dell machine should still load the ucm by
  cardname, and it should work as good as before.

  [Regression Potential]
  low, just add some new UCMs and let Lenovo machine find the UCM by 
bios_version if it fails by cardlongname. I've already tested the change on 
Lenovo and Dell machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1868210/+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 1872824] [NEW] Can't upgrade console-setup-linux (1.194ubuntu3) over (1.108ubuntu15.5), trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package

2020-04-14 Thread Hayden Barnes
Public bug reported:

Upgrade path from 16.04 to 20.04 fails.

console-setup-linux_1.194ubuntu3_all.deb tries to overwrite
'/lib/systemd/system/console-setup.service', which is also in package
keyboard-configuration 1.108ubuntu15.5.

I have reproduced this bug on bare metal and WSL.

Log:

Unpacking console-setup-linux (1.194ubuntu3) over (1.108ubuntu15.5) ...
dpkg: error processing archive 
/var/cache/apt/archives/console-setup-linux_1.194ubuntu3_all.deb (--unpack):
 trying to overwrite '/lib/systemd/system/console-setup.service', which is also 
in package keyboard-configuration 1.108ubuntu15.5
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Preparing to unpack .../keyboard-configuration_1.194ubuntu3_all.deb ...
Unpacking keyboard-configuration (1.194ubuntu3) over (1.108ubuntu15.5) ...
Preparing to unpack .../busybox-initramfs_1%3a1.30.1-4ubuntu6_amd64.deb ...
Unpacking busybox-initramfs (1:1.30.1-4ubuntu6) over (1:1.22.0-15ubuntu1.4) ...
Preparing to unpack .../initramfs-tools-bin_0.136ubuntu6_amd64.deb ...
Unpacking initramfs-tools-bin (0.136ubuntu6) over (0.122ubuntu8.16) ...
Preparing to unpack .../cpio_2.13+dfsg-2_amd64.deb ...
Unpacking cpio (2.13+dfsg-2) over (2.11+dfsg-5ubuntu1.1) ...
Preparing to unpack .../liblz4-1_1.9.2-2_amd64.deb ...
Unpacking liblz4-1:amd64 (1.9.2-2) over (0.0~r131-2ubuntu2) ...
Processing triggers for libc-bin (2.31-0ubuntu7) ...
Processing triggers for ureadahead (0.100.0-19.1) ...
Processing triggers for systemd (229-4ubuntu21.27) ...
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/console-setup-linux_1.194ubuntu3_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Can't upgrade console-setup-linux (1.194ubuntu3) over
  (1.108ubuntu15.5), trying to overwrite '/lib/systemd/system/console-
  setup.service', which is also in package keyboard-configuration
  1.108ubuntu15.5

Status in console-setup package in Ubuntu:
  New

Bug description:
  Upgrade path from 16.04 to 20.04 fails.

  console-setup-linux_1.194ubuntu3_all.deb tries to overwrite
  '/lib/systemd/system/console-setup.service', which is also in package
  keyboard-configuration 1.108ubuntu15.5.

  I have reproduced this bug on bare metal and WSL.

  Log:

  Unpacking console-setup-linux (1.194ubuntu3) over (1.108ubuntu15.5) ...
  dpkg: error processing archive 
/var/cache/apt/archives/console-setup-linux_1.194ubuntu3_all.deb (--unpack):
   trying to overwrite '/lib/systemd/system/console-setup.service', which is 
also in package keyboard-configuration 1.108ubuntu15.5
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Preparing to unpack .../keyboard-configuration_1.194ubuntu3_all.deb ...
  Unpacking keyboard-configuration (1.194ubuntu3) over (1.108ubuntu15.5) ...
  Preparing to unpack .../busybox-initramfs_1%3a1.30.1-4ubuntu6_amd64.deb ...
  Unpacking busybox-initramfs (1:1.30.1-4ubuntu6) over (1:1.22.0-15ubuntu1.4) 
...
  Preparing to unpack .../initramfs-tools-bin_0.136ubuntu6_amd64.deb ...
  Unpacking initramfs-tools-bin (0.136ubuntu6) over (0.122ubuntu8.16) ...
  Preparing to unpack .../cpio_2.13+dfsg-2_amd64.deb ...
  Unpacking cpio (2.13+dfsg-2) over (2.11+dfsg-5ubuntu1.1) ...
  Preparing to unpack .../liblz4-1_1.9.2-2_amd64.deb ...
  Unpacking liblz4-1:amd64 (1.9.2-2) over (0.0~r131-2ubuntu2) ...
  Processing triggers for libc-bin (2.31-0ubuntu7) ...
  Processing triggers for ureadahead (0.100.0-19.1) ...
  Processing triggers for systemd (229-4ubuntu21.27) ...
  Processing triggers for man-db (2.7.5-1) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/console-setup-linux_1.194ubuntu3_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1872824/+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 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version

2020-04-14 Thread Launchpad Bug Tracker
This bug was fixed in the package alsa-lib - 1.1.9-0ubuntu1.3

---
alsa-lib (1.1.9-0ubuntu1.3) eoan; urgency=medium

  * d/p/0010-add-bios-version-for-looking-for-ucm.patch
Add a new way to looking for the ucm by DMI bios_version.
Without this patch, the alsa-lib looks for the ucm by cardlongname
first, if it fails, then by the cardname. This has a problem at least
on LENOVO machines, since a LENOVO model has the same audio design but
it has hundreds of cardlongname, we need to create hundreds of folders
for one model, that is unacceptable. LENOVO told us a LENOVO model has
the unique biso_version, we could use it to find the ucm. After applying
this patch, the alsa-lib looks for the ucm by cardlongname first, if it
fails, it will use bios_version, if it also fails, it will fallback to
cardname.
(LP: #1868210)

 -- Hui Wang   Fri, 27 Mar 2020 11:40:37 +0800

** Changed in: alsa-lib (Ubuntu Eoan)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Load ucm on Lenovo notebooks based on bios version

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Released
Status in alsa-lib source package in Focal:
  Invalid

Bug description:
  This SRU is not backported from upstream of alsa-lib and this SRU is
  not going to be submitted to upstream. That is because the latest
  alsa-lib already supports ucm2, and with ucm2 all machines could share
  one ucm, so latest alsa-lib does not have this problem. This problem
  is only specific to the alsa-lib in Bionic and Eoan.

  [Impact]
  On some Lenovo notebooks, UCM files are not loaded and mic can't be used.

  [Fix]
  UCM was loaded based on cardlongname, but that can't cover all configs of the 
same model. Lenovo suggested to load  ucm by the first 3 letters of 
/sys/devices/virtual/dmi/id/bios_version, so that all configs could use just 
one ucm.

  [Test Case]
  After applying this patch, install the testing alsa-lib on Lenovo X1C7 and 
Dell vostro 5390, which are all machines with the DMIC connected to PCH. After 
system bootup, check the /usr/share/alsa/ucm/ for the presence of 
LENOVO-BIOSID-xxx directories.

  Lenovo X1C7 should load the N2H/*.conf and verify the audio
  functionalities. The Dell machine should still load the ucm by
  cardname, and it should work as good as before.

  [Regression Potential]
  low, just add some new UCMs and let Lenovo machine find the UCM by 
bios_version if it fails by cardlongname. I've already tested the change on 
Lenovo and Dell machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1868210/+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 1868210] Update Released

2020-04-14 Thread Timo Aaltonen
The verification of the Stable Release Update for alsa-lib has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] Load ucm on Lenovo notebooks based on bios version

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Released
Status in alsa-lib source package in Focal:
  Invalid

Bug description:
  This SRU is not backported from upstream of alsa-lib and this SRU is
  not going to be submitted to upstream. That is because the latest
  alsa-lib already supports ucm2, and with ucm2 all machines could share
  one ucm, so latest alsa-lib does not have this problem. This problem
  is only specific to the alsa-lib in Bionic and Eoan.

  [Impact]
  On some Lenovo notebooks, UCM files are not loaded and mic can't be used.

  [Fix]
  UCM was loaded based on cardlongname, but that can't cover all configs of the 
same model. Lenovo suggested to load  ucm by the first 3 letters of 
/sys/devices/virtual/dmi/id/bios_version, so that all configs could use just 
one ucm.

  [Test Case]
  After applying this patch, install the testing alsa-lib on Lenovo X1C7 and 
Dell vostro 5390, which are all machines with the DMIC connected to PCH. After 
system bootup, check the /usr/share/alsa/ucm/ for the presence of 
LENOVO-BIOSID-xxx directories.

  Lenovo X1C7 should load the N2H/*.conf and verify the audio
  functionalities. The Dell machine should still load the ucm by
  cardname, and it should work as good as before.

  [Regression Potential]
  low, just add some new UCMs and let Lenovo machine find the UCM by 
bios_version if it fails by cardlongname. I've already tested the change on 
Lenovo and Dell machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1868210/+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 1869961] Re: systemd-networkd ignores RA preference and creates multipath routes anyway

2020-04-14 Thread Dan Streetman
For reference https://tools.ietf.org/html/rfc4191

** Tags added: ddstreet

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

Title:
  systemd-networkd ignores RA preference and creates multipath routes
  anyway

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

Bug description:
  When IPv6 ND RAs are sent from two different routers, one with Medium
  and one with High preferences, systemd-networkd will ignore the fact
  they have different preferences and create two multipath routes with
  the same weight.

  I ran a tcpdump of the RAs and confirmed that both have different
  preferences sent.

  i.e.

  nms-mon1:~$ ip -6 route
  2a0d:1a40:7551:6010::/64 dev ens18 proto ra metric 100 pref medium
  fe80::/64 dev ens18 proto kernel metric 256 pref medium
  default proto ra metric 100 
nexthop via fe80::c030:9cff:fe10:3492 dev ens18 weight 1 
nexthop via fe80::215:5dff:fe83:c81c dev ens18 weight 1

  Ubuntu version: Ubuntu 18.04.4 LTS
  systemd version: 237-3ubuntu10.39

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1869961/+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 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acc

2020-04-14 Thread Simon Déziel
Oops, it should have been LOW, not LEGACY. Here it is again to avoid any
confusion:

As a workaround, can you try lowering the profile from MEDIUM [1] to LOW
[2]:

sudo mkdir /etc/gnutls
cat << EOF | sudo tee -a /etc/gnutls/config
[overrides]
default-priority-string = 
NORMAL:-VERS-ALL:+VERS-TLS1.3:+VERS-TLS1.2:+VERS-DTLS1.2:%PROFILE_LOW
EOF


1: https://git.launchpad.net/ubuntu/+source/gnutls28/tree/debian/rules#n38
2: 
https://gnutls.org/manual/html_node/Selecting-cryptographic-key-sizes.html#Selecting-cryptographic-key-sizes

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

Title:
  libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client
  with error "Error performing TLS handshake: The Diffie-Hellman prime
  sent by the server is not acceptable (not long enough)."

Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  Confirmed
Status in gnutls28 package in Ubuntu:
  Incomplete

Bug description:
  After upgrade to 20.04 package libgnutls30 broke pulseUI VPN client
  with the following error:

  "Error performing TLS handshake: The Diffie-Hellman prime sent by the
  server is not acceptable (not long enough)."

  I had to revert the package to the 19.10 version (3.6.9-5ubuntu1) and
  to install 19.10 dependency libhogweed4 3.4.1-1 to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgnutls30 3.6.9-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Tue Jan 21 17:48:39 2020
  InstallationDate: Installed on 2017-06-21 (943 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnutls28
  UpgradeStatus: Upgraded to focal on 2020-01-10 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+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 1866974] Re: The Diffie-Hellman prime sent by the server is not acceptable

2020-04-14 Thread Simon Déziel
*** This bug is a duplicate of bug 1872778 ***
https://bugs.launchpad.net/bugs/1872778

As a workaround, can you try lowering the profile from MEDIUM [1] to LOW
[2]:

sudo mkdir /etc/gnutls
cat << EOF | sudo tee -a /etc/gnutls/config
[overrides]
default-priority-string = 
NORMAL:-VERS-ALL:+VERS-TLS1.3:+VERS-TLS1.2:+VERS-DTLS1.2:%PROFILE_LOW
EOF


1: https://git.launchpad.net/ubuntu/+source/gnutls28/tree/debian/rules#n38
2: 
https://gnutls.org/manual/html_node/Selecting-cryptographic-key-sizes.html#Selecting-cryptographic-key-sizes

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

Title:
  The Diffie-Hellman prime sent by the server is not acceptable

Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  I can no longer connect to my ISP mail server.
  Works in previous version 19.10

  "The reported error was “Failed to get capabilities: Error performing
  TLS handshake: The Diffie-Hellman prime sent by the server is not
  acceptable (not long enough).”."

  I've tried finding a workaround but so far no luck.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: evolution 3.35.92-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 11:07:01 2020
  InstallationDate: Installed on 2020-03-03 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974/+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 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acc

2020-04-14 Thread Simon Déziel
As a workaround, can you try lowering the profile from MEDIUM [1] to
LEGACY:

sudo mkdir /etc/gnutls
cat << EOF | sudo tee -a /etc/gnutls/config
[overrides]
default-priority-string = 
NORMAL:-VERS-ALL:+VERS-TLS1.3:+VERS-TLS1.2:+VERS-DTLS1.2:%PROFILE_LEGACY
EOF


1:
https://git.launchpad.net/ubuntu/+source/gnutls28/tree/debian/rules#n38

** Changed in: gnutls28 (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client
  with error "Error performing TLS handshake: The Diffie-Hellman prime
  sent by the server is not acceptable (not long enough)."

Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  Confirmed
Status in gnutls28 package in Ubuntu:
  Incomplete

Bug description:
  After upgrade to 20.04 package libgnutls30 broke pulseUI VPN client
  with the following error:

  "Error performing TLS handshake: The Diffie-Hellman prime sent by the
  server is not acceptable (not long enough)."

  I had to revert the package to the 19.10 version (3.6.9-5ubuntu1) and
  to install 19.10 dependency libhogweed4 3.4.1-1 to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgnutls30 3.6.9-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Tue Jan 21 17:48:39 2020
  InstallationDate: Installed on 2017-06-21 (943 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnutls28
  UpgradeStatus: Upgraded to focal on 2020-01-10 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+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 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acc

2020-04-14 Thread Simon Déziel
** This bug is no longer a duplicate of bug 1872778
   update-crypto-policies not affecting Gnome Online Accounts

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

Title:
  libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client
  with error "Error performing TLS handshake: The Diffie-Hellman prime
  sent by the server is not acceptable (not long enough)."

Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  Confirmed
Status in gnutls28 package in Ubuntu:
  Incomplete

Bug description:
  After upgrade to 20.04 package libgnutls30 broke pulseUI VPN client
  with the following error:

  "Error performing TLS handshake: The Diffie-Hellman prime sent by the
  server is not acceptable (not long enough)."

  I had to revert the package to the 19.10 version (3.6.9-5ubuntu1) and
  to install 19.10 dependency libhogweed4 3.4.1-1 to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgnutls30 3.6.9-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Tue Jan 21 17:48:39 2020
  InstallationDate: Installed on 2017-06-21 (943 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnutls28
  UpgradeStatus: Upgraded to focal on 2020-01-10 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+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 1872227] Re: Ubuntu bugs cannot be reported because of obsolete package versions, but everything is up-to-date

2020-04-14 Thread Brian Murray
This is actually because gnome-shell is a not fully phased update and as
such appears as an available update to apt but not to update-manager
which respects phasing of packages.

** Package changed: ubuntu-release-upgrader (Ubuntu) => apport (Ubuntu)

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

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

Title:
  Ubuntu bugs cannot be reported because of obsolete package versions,
  but everything is up-to-date

Status in apport package in Ubuntu:
  Invalid

Bug description:
  I had at least two or three crashes, and they cannot be submitted
  because some "obsolete package versions" have been found. However,
  under my update settings every update source is activated, and there
  are no updates (i checked ASAP after the crash report). I reported it
  here because there was no section for "updates" in "Find right
  package" on Ubuntu wiki. This bug might be very dangerous if it is
  experiences on many machines - other bugs will be missing bug reports.

  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15.4
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 11 21:35:19 2020
  InstallationDate: Installed on 2020-02-08 (63 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1872227/+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 1872146] Re: Audio on Headphones stopped working

2020-04-14 Thread Brian Murray
** Package changed: ubuntu-release-upgrader (Ubuntu) => pulseaudio
(Ubuntu)

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

Title:
  Audio on Headphones stopped working

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Audio via my headphones worked yesterday, Today no such luck.

  When I plug in my headphone, Plasma picks it up but no sound.

  Bluetooth headset still works.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Fri Apr 10 23:03:09 2020
  InstallationDate: Installed on 2020-04-05 (5 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200404)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872146/+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 1872146] [NEW] Audio on Headphones stopped working

2020-04-14 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Audio via my headphones worked yesterday, Today no such luck.

When I plug in my headphone, Plasma picks it up but no sound.

Bluetooth headset still works.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.18
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Fri Apr 10 23:03:09 2020
InstallationDate: Installed on 2020-04-05 (5 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200404)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_ZA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug dist-upgrade focal
-- 
Audio on Headphones stopped working
https://bugs.launchpad.net/bugs/1872146
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio 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 1872778] Re: update-crypto-policies not affecting Gnome Online Accounts

2020-04-14 Thread Steven Jay Cohen
1. The specific steps or actions you took that caused you to encounter
the problem.

a. Go to Gnome Online Accounts and add a Google Apps Account (in my case 
nyu.edu)
b. After entering the email address see the following error:
Error performing TLS handshake: The Diffie-Hellman prime sent by the server is 
not acceptable (not long enough).
c. Use update-crypto-policies to change setting to LEGACY and EMPTY then 
repeating step A
d. Attempted the connection again.

2. The behavior you expected.

I would have expected to be able to connect under LEGACY or EMPTY. Or,
alternatively, I would have expected a different error message (since by
definition LEGACY would have accepted the shorter prime and EMPTY
wouldn't have needed it).

3. The behavior you actually encountered (in as much detail as
possible).

See that the error message still talks about "not long enough" in all 3
cases.

If you check the duplicate cases you will see that as of 20.04
connections are failing because of weak crypto. The only workaround is
to tell the local system to lower its standards (LEGACY or NONE) until
the people running the server get their act together.

But, since the error message remains constant, even when the setting has
been changed, it looks like the mechanism running Online Accounts might
not be referencing the setting like it should.

Now, it could just as likely be a poorly worded error message.

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

Title:
  update-crypto-policies not affecting Gnome Online Accounts

Status in gnome-online-accounts package in Ubuntu:
  Incomplete
Status in gnutls28 package in Ubuntu:
  Confirmed

Bug description:
  -crypto-policies 20190816git-1
  -gnome-online-accounts 3.36.0-1ubuntu1

  Changing between DEFAULT, LEGACY, and EMPTY has no affect on attempts
  to connect to accounts through Online Accounts.

  Changing to LEGACY or EMPTY should at least change the following
  error:

  Error performing TLS handshake: The Diffie-Hellman prime sent by the
  server is not acceptable (not long enough).

  Under either LEGACY or EMPTY the (not long enough) error is
  nonsensical. The persistence of the incorrect error message could
  imply that gnome-online-accounts is not respecting settings made by
  crypto-policies.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1872778/+subscriptions

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


[Touch-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

2020-04-14 Thread Sebastien Bacher
** Changed in: software-properties (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

Status in gnome-shell package in Ubuntu:
  Invalid
Status in software-properties package in Ubuntu:
  In Progress
Status in gnome-shell source package in Bionic:
  Invalid
Status in software-properties source package in Bionic:
  Confirmed

Bug description:
  
  On the "Other Software" tab, I am unable to select "Canonical Partners".
  Similarly, the other checkboxes on the "Other Software" can not be clicked.
  Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.

  However, activating or deactivating checkboxes on other tabs causes an
  authorization dialog to be presented to the user.

  I experience this bug in an an Xorg session.

  sources.list and sources.list.d have the following permissions:
  -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
  drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d

  All files in sources.list.d have the following permissions as this example:
  -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy software-properties-gtk
  software-properties-gtk:
Installed: 0.96.24.17
Candidate: 0.96.24.17
Version table:
   *** 0.96.24.17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 26 22:45:09 2017
  InstallationDate: Installed on 2017-10-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions

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


[Touch-packages] [Bug 1872227] [NEW] Ubuntu bugs cannot be reported because of obsolete package versions, but everything is up-to-date

2020-04-14 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I had at least two or three crashes, and they cannot be submitted
because some "obsolete package versions" have been found. However, under
my update settings every update source is activated, and there are no
updates (i checked ASAP after the crash report). I reported it here
because there was no section for "updates" in "Find right package" on
Ubuntu wiki. This bug might be very dangerous if it is experiences on
many machines - other bugs will be missing bug reports.

Ubuntu 19.10

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubuntu-release-upgrader-core 1:19.10.15.4
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 11 21:35:19 2020
InstallationDate: Installed on 2020-02-08 (63 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: apport (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: amd64 apport-bug dist-upgrade eoan
-- 
Ubuntu bugs cannot be reported because of obsolete package versions, but 
everything is up-to-date
https://bugs.launchpad.net/bugs/1872227
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apport 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 1872286] Re: gio - cifs mount smb not possible "Location is not mountable"

2020-04-14 Thread Dirk Heumann
I updated my Ubuntu 19.10 laptop with "sudo update-manager -d" to 20.04
beta.  I always mount a small local drive in my network, because I have
there my private git repo, which is then easily available to my laptops
and to may raspberries.

I did not delete the package on my own, but there were some hickups
during installation.

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

Title:
  gio - cifs mount smb not possible "Location is not mountable"

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  1) Release
  $ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2) Package
  $ apt-cache policy libglib2.0-bin
  libglib2.0-bin:
Installed: 2.64.1-1
Candidate: 2.64.1-1
Version table:
   *** 2.64.1-1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) Expected to happen
  The path should be mounted at
  /run/user/1000/gvfs/smb-share:server=192.168.178.1,share=PathName/

  4) What happened instead:
  Error Message:
  gio: smb://192.168.178.1/PathName/: Location is not mountable

  5) Long description / explanation
  Since some years, I mount a Windows drive with

  gio mount smb://192.168.178.1/PathName

  After upgrading from 19.04 to 20.04 beta, this does not work any more,
  I get the error message

  gio: smb://192.168.178.1/PathName/: Location is not mountable

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-bin 2.64.1-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 12 12:43:53 2020
  InstallationDate: Installed on 2019-02-17 (420 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: glib2.0
  UpgradeStatus: Upgraded to focal on 2020-04-05 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1872286/+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 1872504] Re: date modified is wrong for files on an exfat formatted drive

2020-04-14 Thread Brian Murray
** Package changed: ubuntu-release-upgrader (Ubuntu) => ubuntu-meta
(Ubuntu)

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

Title:
  date modified is wrong for files on an exfat formatted drive

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  When using exfat formatted drives (e.g. my camera card) with focal
  fossa any access causes the date modified to be set, even when it
  would not normally be set, and it is set a month into the future.

  Installing exfat-fuse and exfat-utils results in the correct
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 13 17:27:30 2020
  InstallationDate: Installed on 2020-04-12 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1872504/+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 1872504] [NEW] date modified is wrong for files on an exfat formatted drive

2020-04-14 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When using exfat formatted drives (e.g. my camera card) with focal fossa
any access causes the date modified to be set, even when it would not
normally be set, and it is set a month into the future.

Installing exfat-fuse and exfat-utils results in the correct behaviour.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.18
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 13 17:27:30 2020
InstallationDate: Installed on 2020-04-12 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade focal
-- 
date modified is wrong for files on an exfat formatted drive
https://bugs.launchpad.net/bugs/1872504
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-meta 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 1872778] Re: update-crypto-policies not affecting Gnome Online Accounts

2020-04-14 Thread Sebastien Bacher
Thank you for taking the time to report this bug and help make Ubuntu
better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read 'How to report bugs effectively'
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Thanks!

** Changed in: gnome-online-accounts (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Incomplete

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

Title:
  update-crypto-policies not affecting Gnome Online Accounts

Status in gnome-online-accounts package in Ubuntu:
  Incomplete
Status in gnutls28 package in Ubuntu:
  Confirmed

Bug description:
  -crypto-policies 20190816git-1
  -gnome-online-accounts 3.36.0-1ubuntu1

  Changing between DEFAULT, LEGACY, and EMPTY has no affect on attempts
  to connect to accounts through Online Accounts.

  Changing to LEGACY or EMPTY should at least change the following
  error:

  Error performing TLS handshake: The Diffie-Hellman prime sent by the
  server is not acceptable (not long enough).

  Under either LEGACY or EMPTY the (not long enough) error is
  nonsensical. The persistence of the incorrect error message could
  imply that gnome-online-accounts is not respecting settings made by
  crypto-policies.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1872778/+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 1872788] Re: super key searching show incomplete icon

2020-04-14 Thread Sebastien Bacher
Thank you for your bug report. What screens configuration and resolution
do you use?

It sounds similar to bug #1869571

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

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

Title:
  super key searching show incomplete icon

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  compare to bionic, bionic will show complete icon when I press super
  key and type prefix of application.

  But in Focal, the icon is incomplete as attache screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.6.0-1007.7-oem 5.6.2
  Uname: Linux 5.6.0-1007-oem x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 01:37:30 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
  InstallationDate: Installed on 2020-04-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411)
  MachineType: Dell Inc. XPS 13 9380
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1007-oem 
root=UUID=0b23d7d3-fb6c-4ee1-9681-71d148d364d1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872788/+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 1872791] Re: PulseAudio doesn't see analog output on Dell Inspiron 6400 with STAC9200

2020-04-14 Thread Sebastien Bacher
Thank you for your bug report, could you report it upstream on
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/ ?

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Low

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

Title:
  PulseAudio doesn't see analog output on Dell Inspiron 6400 with
  STAC9200

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio currently doesn't see the analog audio output in my Dell
  Inspiron 6400 laptop with Intel HDA STAC9200 audio. It only sees the
  SPDIF output. This is the situation in both "pactl list sinks" and
  pavucontrol. I hear no sound from applications, probably because it's
  going to SPDIF. I don't have a way to listen to SPDIF to see if that
  is indeed the case.

  ALSA sees the analog output and "speaker-test -D plughw:0" plays sound
  through the laptop's speakers.

  This problem never happened in Ubuntu 19.10 and earlier. It might have
  worked earlier in 20.04 also, but I'm not sure of that. Rebooting
  didn't help. Purging and reinstalling pulseaudio and its automatically
  installed dependencies didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-21-generic.
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bgjenero   1414 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 27'
 Mixer name : 'SigmaTel STAC9200'
 Components : 'HDA:83847690,102801bd,00102201 
HDA:14f12bfa,14f100c3,0009'
 Controls  : 22
 Simple ctrls  : 9
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Apr 14 13:37:43 2020
  InstallationDate: Installed on 2012-01-19 (3008 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-04-05 (9 days ago)
  dmi.bios.date: 06/13/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0XD720
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872791/+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 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

2020-04-14 Thread Dan Streetman
** Description changed:

  [impact]
  
  A bridged interface with static ipv4 address and gateway configuration
  will fail to properly add the route via the gateway, leaving the system
  without a globally working network.
  
  [test case]
  
- On a Focal system, remove all configuration and create this netplan:
+ On a Focal system, remove all network configuration and create this
+ netplan:
  
  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]
  
  Replace the interface name 'enp4s0' with the actual interface name on
  the test system.
  
  Reboot the system, and check the route to the gateway, which will be
  missing:
  
  root@lp1860926-f:~# ip r
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4
  
  The route is expected to be present, e.g.:
  
  ubuntu@lp1860926-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4
  
  [regression potential]
  
  Not SRU - N/A
  
  [scope]
  
  This is not reproducable on Eoan or Bionic; this is needed only for
  Focal.
  
  [original description]
  
  Freshly installed Ubuntu 20.04 fully patched to days date with static IP
  address works fine and survives a reboot
  
  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]
  
  however when converted to a bridged network for kvm
  
  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]
  
  will not survive a reboot and required systemd-network to be restarted or
  @reboot /usr/sbin/netplan apply
  added to the crontab
  
  after a reboot the network can not b eaccseed and a
  systemctl status systemd-networkd produces
  
  systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 979 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 57662)
   Memory: 4.1M
   CGroup: /system.slice/systemd-networkd.service
   └─979 /lib/systemd/systemd-networkd
  
  Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for 
link '5' we don't know about, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an 
address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring.
  
  systemctl restart systemd-networkd resolved the issue and a
  
  systemctl status systemd-network producessystemd-networkd.service - Network 
Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:39:28 UTC; 41s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 1650 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 57662)
   Memory: 1.6M
   CGroup: /system.slice/systemd-networkd.service
   └─1650 /lib/systemd/systemd-networkd
  
  Jan 26 16:39:28 firebolt systemd[1]: Starting Network Service...
  Jan 26 16:39:28 firebolt systemd-networkd[1650]: br0: netdev ready
  Jan 26 16:39:28 firebolt systemd-networkd[1650]: br0: Gained IPv6LL
  Jan 26 16:39:28 firebolt systemd-networkd[1650]: Enumeration completed
  Jan 26 16:39:28 firebolt systemd[1]: Started Network Service.
  

[Touch-packages] [Bug 1870585] Re: Not cleaning /var/tmp by default

2020-04-14 Thread Dan Streetman
** Tags added: ddstreet

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

Title:
  Not cleaning /var/tmp by default

Status in systemd package in Ubuntu:
  New

Bug description:
  1) 20.04
  2) 245.2-1ubuntu2
  3) I expect /var/tmp to be cleaned up in some way.
  4) It's commented out per 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773313

  In sosreport was comparing the difference between /tmp (Ubuntu/Debian)
  and /var/tmp (RH) and determined that as long as /var/tmp gets cleaned
  on a regular basis we would prefer /var/tmp.

  The  bug that appears to have prompted the disabling was fixed a long
  time ago, can we have this 30d delete re-enabled by default?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870585/+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 1872797] [NEW] [GP63 Leopard 8RE, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all

2020-04-14 Thread Awet Haileslassie Gebrehiwot
Public bug reported:

while doing Deeplearning training my computer battery finished and my laptop 
turned off suddenly.
when i turn it on back the audio failed.
i have tried may option to fix the issue but noting worked

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
Uname: Linux 4.15.0-96-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  msi_awet   1909 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 14 20:30:13 2020
InstallationDate: Installed on 2019-11-14 (152 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: GP106 High Definition Audio Controller - HDA NVidia
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gdm1502 F pulseaudio
  msi_awet   1909 F pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [GP63 Leopard 8RE, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at 
all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/20/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16P5IMS.110
dmi.board.asset.tag: Default string
dmi.board.name: MS-16P5
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16P5IMS.110:bd05/20/2019:svnMicro-StarInternationalCo.,Ltd.:pnGP63Leopard8RE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16P5:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
dmi.product.family: GP
dmi.product.name: GP63 Leopard 8RE
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-11T21:38:46.914721

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  [GP63 Leopard 8RE, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound
  at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  while doing Deeplearning training my computer battery finished and my laptop 
turned off suddenly.
  when i turn it on back the audio failed.
  i have tried may option to fix the issue but noting worked

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  msi_awet   1909 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:30:13 2020
  InstallationDate: Installed on 2019-11-14 (152 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: GP106 High Definition Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1502 F pulseaudio
msi_awet   1909 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [GP63 Leopard 8RE, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16P5IMS.110
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16P5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16P5IMS.110:bd05/20/2019:svnMicro-StarInternationalCo.,Ltd.:pnGP63Leopard8RE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16P5:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: GP
  dmi.product.name: GP63 Leopard 8RE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-11T21:38:46.914721

To manage notifications about this bug 

[Touch-packages] [Bug 1774843] Re: apport python exception for python versions which python-apt is not built on

2020-04-14 Thread Brian Murray
** Changed in: python3.8 (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: python-apt (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: python-apt (Ubuntu Eoan)
   Status: New => Invalid

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

Title:
  apport python exception for python versions which python-apt is not
  built on

Status in Apport:
  New
Status in python-apt package in Ubuntu:
  Invalid
Status in python3.7 package in Ubuntu:
  Invalid
Status in python3.8 package in Ubuntu:
  Invalid
Status in python-apt source package in Bionic:
  Invalid
Status in python3.7 source package in Bionic:
  Triaged
Status in python3.8 source package in Bionic:
  Triaged
Status in python-apt source package in Eoan:
  Invalid
Status in python3.7 source package in Eoan:
  Triaged
Status in python3.8 source package in Eoan:
  Triaged
Status in python-apt source package in Focal:
  Invalid
Status in python3.7 source package in Focal:
  Invalid
Status in python3.8 source package in Focal:
  Invalid

Bug description:
  it seems apport installs an exception hook whenever running python3.
  This hook is apparently installed for python3.7 too.
  This exception handler has a dependency on apt_pkg, which is a binary that is 
not compatible with python3.7 it seems (you can't import it, see below)

  As a result, whenever I run a python3.7 script and run into an exception 
(which happens often when writing code), I get an additional exception in the 
exception handler + a copy of the original exception, so three stacktraces in 
total.
  A solution would be to only install the exception hook for the system python  
i.e. python3.6

  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  apport: 2.20.9-0ubuntu7
  python-apt: 1.6.0
  python3.7: 3.7.0~b3-1

  Demo with a trivial error:
  $ python3 -c 'print hello'
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?

  
  $ python3.7 -c 'print hello'
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in 
apport_excepthook
  from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in 

  from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in 
  import apport.fileutils
File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in 

  from apport.packaging_impl import impl as packaging
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in 

  import apt
File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in 
  import apt_pkg
  ModuleNotFoundError: No module named 'apt_pkg'

  Original exception was:
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?


  Python 3.6.5 (default, Apr  1 2018, 05:46:30) 
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  >>> import apt_pkg
  >>> apt_pkg.__file__
  '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so'
  >>> 

  Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) 
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  >> import apt_pkg
  Traceback (most recent call last):
File "", line 1, in 
  ModuleNotFoundError: No module named 'apt_pkg'

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1774843/+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 1872791] Re: PulseAudio doesn't see analog output on Dell Inspiron 6400 with STAC9200

2020-04-14 Thread Boris Gjenero
It was easy to fix this by adding the following line to /etc/pulse/default.pa
load-module module-alsa-sink device=hw:0,0

After doing that and rebooting, I had to set the analog device as the
fallback device in pavucontrol. (Before the default.pa change, the SPDIF
device had been the only playback device there.)

So, sound works now. But, why did I have to do that? Why was the SPDIF
device automatically detected but not the audio device?

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

Title:
  PulseAudio doesn't see analog output on Dell Inspiron 6400 with
  STAC9200

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio currently doesn't see the analog audio output in my Dell
  Inspiron 6400 laptop with Intel HDA STAC9200 audio. It only sees the
  SPDIF output. This is the situation in both "pactl list sinks" and
  pavucontrol. I hear no sound from applications, probably because it's
  going to SPDIF. I don't have a way to listen to SPDIF to see if that
  is indeed the case.

  ALSA sees the analog output and "speaker-test -D plughw:0" plays sound
  through the laptop's speakers.

  This problem never happened in Ubuntu 19.10 and earlier. It might have
  worked earlier in 20.04 also, but I'm not sure of that. Rebooting
  didn't help. Purging and reinstalling pulseaudio and its automatically
  installed dependencies didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-21-generic.
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bgjenero   1414 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 27'
 Mixer name : 'SigmaTel STAC9200'
 Components : 'HDA:83847690,102801bd,00102201 
HDA:14f12bfa,14f100c3,0009'
 Controls  : 22
 Simple ctrls  : 9
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Apr 14 13:37:43 2020
  InstallationDate: Installed on 2012-01-19 (3008 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-04-05 (9 days ago)
  dmi.bios.date: 06/13/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0XD720
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872791/+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 1872286] Re: gio - cifs mount smb not possible "Location is not mountable"

2020-04-14 Thread Sebastien Bacher
Weird that you didn't have gvfs-backends installed, it should be there
on a default installation. How did you install your system?

The new issue seems worth debugging, it's fine to repurpose the bug
here, maybe ask upstream what they prefer on gitlab though?

The error is similar to
https://gitlab.gnome.org/GNOME/glib/-/issues/2090 so maybe reusing that
one makes sense

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

Title:
  gio - cifs mount smb not possible "Location is not mountable"

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  1) Release
  $ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2) Package
  $ apt-cache policy libglib2.0-bin
  libglib2.0-bin:
Installed: 2.64.1-1
Candidate: 2.64.1-1
Version table:
   *** 2.64.1-1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) Expected to happen
  The path should be mounted at
  /run/user/1000/gvfs/smb-share:server=192.168.178.1,share=PathName/

  4) What happened instead:
  Error Message:
  gio: smb://192.168.178.1/PathName/: Location is not mountable

  5) Long description / explanation
  Since some years, I mount a Windows drive with

  gio mount smb://192.168.178.1/PathName

  After upgrading from 19.04 to 20.04 beta, this does not work any more,
  I get the error message

  gio: smb://192.168.178.1/PathName/: Location is not mountable

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-bin 2.64.1-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 12 12:43:53 2020
  InstallationDate: Installed on 2019-02-17 (420 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: glib2.0
  UpgradeStatus: Upgraded to focal on 2020-04-05 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1872286/+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 1774843] Re: apport python exception handler messes up python3.7

2020-04-14 Thread Brian Murray
** Package changed: apport (Ubuntu Focal) => python3.7 (Ubuntu Focal)

** Changed in: python3.7 (Ubuntu Focal)
   Status: Triaged => Invalid

** Also affects: python3.8 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: python3.8 (Ubuntu Focal)
   Status: New => Invalid

** Summary changed:

- apport python exception handler messes up python3.7
+ apport python exception for python versions which python-apt is not built on

** Also affects: python-apt (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: python3.7 (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: python3.8 (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: python-apt (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: python3.7 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: python3.8 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: python3.7 (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: python3.7 (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: python3.7 (Ubuntu Eoan)
   Importance: Undecided => Medium

** Changed in: python3.7 (Ubuntu Eoan)
   Status: New => Triaged

** Changed in: python3.8 (Ubuntu Eoan)
   Importance: Undecided => Medium

** Changed in: python3.8 (Ubuntu Eoan)
   Status: New => Triaged

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

Title:
  apport python exception for python versions which python-apt is not
  built on

Status in Apport:
  New
Status in python-apt package in Ubuntu:
  Invalid
Status in python3.7 package in Ubuntu:
  Invalid
Status in python3.8 package in Ubuntu:
  Invalid
Status in python-apt source package in Bionic:
  New
Status in python3.7 source package in Bionic:
  Triaged
Status in python3.8 source package in Bionic:
  New
Status in python-apt source package in Eoan:
  New
Status in python3.7 source package in Eoan:
  Triaged
Status in python3.8 source package in Eoan:
  Triaged
Status in python-apt source package in Focal:
  Invalid
Status in python3.7 source package in Focal:
  Invalid
Status in python3.8 source package in Focal:
  Invalid

Bug description:
  it seems apport installs an exception hook whenever running python3.
  This hook is apparently installed for python3.7 too.
  This exception handler has a dependency on apt_pkg, which is a binary that is 
not compatible with python3.7 it seems (you can't import it, see below)

  As a result, whenever I run a python3.7 script and run into an exception 
(which happens often when writing code), I get an additional exception in the 
exception handler + a copy of the original exception, so three stacktraces in 
total.
  A solution would be to only install the exception hook for the system python  
i.e. python3.6

  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  apport: 2.20.9-0ubuntu7
  python-apt: 1.6.0
  python3.7: 3.7.0~b3-1

  Demo with a trivial error:
  $ python3 -c 'print hello'
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?

  
  $ python3.7 -c 'print hello'
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in 
apport_excepthook
  from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in 

  from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in 
  import apport.fileutils
File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in 

  from apport.packaging_impl import impl as packaging
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in 

  import apt
File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in 
  import apt_pkg
  ModuleNotFoundError: No module named 'apt_pkg'

  Original exception was:
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?


  Python 3.6.5 (default, Apr  1 2018, 05:46:30) 
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  >>> import apt_pkg
  >>> apt_pkg.__file__
  '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so'
  >>> 

  Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) 
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  

[Touch-packages] [Bug 1868892] Re: initramfs-tools/hooks/udev for network *.link really sucks

2020-04-14 Thread Dan Streetman
** Description changed:

+ [impact]
+ 
+ If the /{etc,lib}/systemd/network directory itself is a symlink, the find
+ command will not actually find any of the files in the dir it links to.
+ 
+ [test case]
+ 
+ $ sudo touch /etc/systemd/network/lp1868892.link
+ $ sudo update-initramfs -u
+ update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic
+ ...
+ $ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
+ usr/lib/systemd/network/lp1868892.link
+ $ sudo mv /etc/systemd/network /etc/systemd/network.abc
+ $ sudo ln -s network.abc /etc/systemd/network
+ $ sudo update-initramfs -u
+ $ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
+ $ 
+ 
+ [regression potential]
+ 
+ this adjusts how link files are included in the initramfs, so
+ regressions would likely occur when creating new initramfs, such as
+ failure to create initramfs at all, or failure to properly copy link
+ files into the initramfs, causing network setup failure.
+ 
+ [scope]
+ 
+ this is a Debian/Ubuntu specific file, and the Debian MR was just
+ opened, so this is needed for Debian and all releases of Ubuntu.
+ 
+ [other info]
+ 
+ This bug likely has a very limited impact, as it is uncommon to symlink
+ either the /lib/systemd/network or /etc/systemd/network dirs.
+ 
+ [original description]
+ 
  If one creates e.g. /etc/systemd/network.cu and /etc/systemd/network.fc
  and symlinks  /etc/systemd/network to one of them, network setup will
  fail on reboot, because /usr/share/initramfs-tools/hooks/udev does a
  very poor job: it simply checks for a directory instead of the link
  files and therefore skips copying required files to the ram image.
  Another poor job is done when copying the files to the ram image:
  instead of following symlinks it copies them as which in turn makes them
  useless, because it does not copy the related dirs and thus the symlinks
  point to nothing. So keeping the system in an consistent state which
  such poor scripts is very hard, asking for trouble.
  
  Suggested fix is attached.

** Tags added: ddstreet

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

Title:
  initramfs-tools/hooks/udev for network *.link really sucks

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  [impact]

  If the /{etc,lib}/systemd/network directory itself is a symlink, the find
  command will not actually find any of the files in the dir it links to.

  [test case]

  $ sudo touch /etc/systemd/network/lp1868892.link
  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic
  ...
  $ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
  usr/lib/systemd/network/lp1868892.link
  $ sudo mv /etc/systemd/network /etc/systemd/network.abc
  $ sudo ln -s network.abc /etc/systemd/network
  $ sudo update-initramfs -u
  $ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
  $ 

  [regression potential]

  this adjusts how link files are included in the initramfs, so
  regressions would likely occur when creating new initramfs, such as
  failure to create initramfs at all, or failure to properly copy link
  files into the initramfs, causing network setup failure.

  [scope]

  this is a Debian/Ubuntu specific file, and the Debian MR was just
  opened, so this is needed for Debian and all releases of Ubuntu.

  [other info]

  This bug likely has a very limited impact, as it is uncommon to
  symlink either the /lib/systemd/network or /etc/systemd/network dirs.

  [original description]

  If one creates e.g. /etc/systemd/network.cu and
  /etc/systemd/network.fc and symlinks  /etc/systemd/network to one of
  them, network setup will fail on reboot, because /usr/share/initramfs-
  tools/hooks/udev does a very poor job: it simply checks for a
  directory instead of the link files and therefore skips copying
  required files to the ram image. Another poor job is done when copying
  the files to the ram image: instead of following symlinks it copies
  them as which in turn makes them useless, because it does not copy the
  related dirs and thus the symlinks point to nothing. So keeping the
  system in an consistent state which such poor scripts is very hard,
  asking for trouble.

  Suggested fix is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1868892/+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 1872286] Re: gio - cifs mount smb not possible "Location is not mountable"

2020-04-14 Thread Dirk Heumann
After installing package `gvfs-backends` and reboot, I got the follow
error:

`$ gio mount smb://192.168.178.1/PathName`  
`gio: smb://192.168.178.1/PathName/: Failed to mount Windows share: Software 
caused connection abort`  
`gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)`

The debug logs look like the following:

`smb: g_vfs_backend_smb_init: default workgroup = 'NULL'`  
`smb: Added new job source 0x55e4166bc080 (GVfsBackendSmb)`  
`smb: Queued new job 0x55e4166bd940 (GVfsJobMount)`  
`smb: do_mount - URI = smb://192.168.178.1/PathName`  
`smb: do_mount - try #0 `  
`smb: auth_callback - kerberos pass`  
`smb: auth_callback - out: last_user = 'UserName', last_domain = 'WORKGROUP'`  
`smb: do_mount - [smb://192.168.178.1/fritz7490; 0] res = -1, cancelled = 0, 
errno = [103] 'Software caused connection abort' `  
`smb: do_mount - (errno != EPERM && errno != EACCES), cancelled = 0, breaking`  
`smb: send_reply(0x55e4166bd940), failed=1 (Failed to mount Windows share: 
Software caused connection abort)`

The question is now, if a new bug should be opened, because of the
reason is different and the description should be changed.

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

Title:
  gio - cifs mount smb not possible "Location is not mountable"

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  1) Release
  $ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2) Package
  $ apt-cache policy libglib2.0-bin
  libglib2.0-bin:
Installed: 2.64.1-1
Candidate: 2.64.1-1
Version table:
   *** 2.64.1-1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) Expected to happen
  The path should be mounted at
  /run/user/1000/gvfs/smb-share:server=192.168.178.1,share=PathName/

  4) What happened instead:
  Error Message:
  gio: smb://192.168.178.1/PathName/: Location is not mountable

  5) Long description / explanation
  Since some years, I mount a Windows drive with

  gio mount smb://192.168.178.1/PathName

  After upgrading from 19.04 to 20.04 beta, this does not work any more,
  I get the error message

  gio: smb://192.168.178.1/PathName/: Location is not mountable

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-bin 2.64.1-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 12 12:43:53 2020
  InstallationDate: Installed on 2019-02-17 (420 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: glib2.0
  UpgradeStatus: Upgraded to focal on 2020-04-05 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1872286/+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 1722478] Re: Two-finger scrolling and click-and-drag no longer works after resuming from suspend

2020-04-14 Thread Aethralis
I started to experience this bug now after kernel update,
4.15.0-96-generic, 18.04.4, Thinkpad-T470s.

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

Title:
  Two-finger scrolling and click-and-drag no longer works after resuming
  from suspend

Status in Linux:
  Confirmed
Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1722478/+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 1868892] Re: initramfs-tools/hooks/udev for network *.link really sucks

2020-04-14 Thread Dan Streetman
opened Debian MR
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/85

** Also affects: systemd (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Eoan)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Focal)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

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

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

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

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

Title:
  initramfs-tools/hooks/udev for network *.link really sucks

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  [impact]

  If the /{etc,lib}/systemd/network directory itself is a symlink, the find
  command will not actually find any of the files in the dir it links to.

  [test case]

  $ sudo touch /etc/systemd/network/lp1868892.link
  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic
  ...
  $ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
  usr/lib/systemd/network/lp1868892.link
  $ sudo mv /etc/systemd/network /etc/systemd/network.abc
  $ sudo ln -s network.abc /etc/systemd/network
  $ sudo update-initramfs -u
  $ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
  $ 

  [regression potential]

  this adjusts how link files are included in the initramfs, so
  regressions would likely occur when creating new initramfs, such as
  failure to create initramfs at all, or failure to properly copy link
  files into the initramfs, causing network setup failure.

  [scope]

  this is a Debian/Ubuntu specific file, and the Debian MR was just
  opened, so this is needed for Debian and all releases of Ubuntu.

  [other info]

  This bug likely has a very limited impact, as it is uncommon to
  symlink either the /lib/systemd/network or /etc/systemd/network dirs.

  [original description]

  If one creates e.g. /etc/systemd/network.cu and
  /etc/systemd/network.fc and symlinks  /etc/systemd/network to one of
  them, network setup will fail on reboot, because /usr/share/initramfs-
  tools/hooks/udev does a very poor job: it simply checks for a
  directory instead of the link files and therefore skips copying
  required files to the ram image. Another poor job is done when copying
  the files to the ram image: instead of following symlinks it copies
  them as which in turn makes them useless, because it does not copy the
  related dirs and thus the symlinks point to nothing. So keeping the
  system in an consistent state which such poor scripts is very hard,
  asking for trouble.

  Suggested fix is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1868892/+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 1872791] [NEW] PulseAudio doesn't see analog output on Dell Inspiron 6400 with STAC9200

2020-04-14 Thread Boris Gjenero
Public bug reported:

PulseAudio currently doesn't see the analog audio output in my Dell
Inspiron 6400 laptop with Intel HDA STAC9200 audio. It only sees the
SPDIF output. This is the situation in both "pactl list sinks" and
pavucontrol. I hear no sound from applications, probably because it's
going to SPDIF. I don't have a way to listen to SPDIF to see if that is
indeed the case.

ALSA sees the analog output and "speaker-test -D plughw:0" plays sound
through the laptop's speakers.

This problem never happened in Ubuntu 19.10 and earlier. It might have
worked earlier in 20.04 also, but I'm not sure of that. Rebooting didn't
help. Purging and reinstalling pulseaudio and its automatically
installed dependencies didn't help.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-21-generic.
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
ArecordDevices:
  List of CAPTURE Hardware Devices 
 card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bgjenero   1414 F pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 27'
   Mixer name   : 'SigmaTel STAC9200'
   Components   : 'HDA:83847690,102801bd,00102201 
HDA:14f12bfa,14f100c3,0009'
   Controls  : 22
   Simple ctrls  : 9
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Tue Apr 14 13:37:43 2020
InstallationDate: Installed on 2012-01-19 (3008 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to focal on 2020-04-05 (9 days ago)
dmi.bios.date: 06/13/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0XD720
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: MM061
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal

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

Title:
  PulseAudio doesn't see analog output on Dell Inspiron 6400 with
  STAC9200

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio currently doesn't see the analog audio output in my Dell
  Inspiron 6400 laptop with Intel HDA STAC9200 audio. It only sees the
  SPDIF output. This is the situation in both "pactl list sinks" and
  pavucontrol. I hear no sound from applications, probably because it's
  going to SPDIF. I don't have a way to listen to SPDIF to see if that
  is indeed the case.

  ALSA sees the analog output and "speaker-test -D plughw:0" plays sound
  through the laptop's speakers.

  This problem never happened in Ubuntu 19.10 and earlier. It might have
  worked earlier in 20.04 also, but I'm not sure of that. Rebooting
  didn't help. Purging and reinstalling pulseaudio and its automatically
  installed dependencies didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-21-generic.
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bgjenero   1414 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 27'
 Mixer name : 'SigmaTel STAC9200'
 Components : 'HDA:83847690,102801bd,00102201 
HDA:14f12bfa,14f100c3,0009'
 Controls  : 22
 Simple ctrls  : 9
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Apr 14 13:37:43 2020
  InstallationDate: Installed on 2012-01-19 (3008 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-04-05 (9 days ago)
  dmi.bios.date: 06/13/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0XD720
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go 

[Touch-packages] [Bug 1872788] Re: super key searching show incomplete icon

2020-04-14 Thread Alex Tu
** Attachment added: "2020-04-15_01-41.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872788/+attachment/5354040/+files/2020-04-15_01-41.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/1872788

Title:
  super key searching show incomplete icon

Status in xorg package in Ubuntu:
  New

Bug description:
  compare to bionic, bionic will show complete icon when I press super
  key and type prefix of application.

  But in Focal, the icon is incomplete as attache screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.6.0-1007.7-oem 5.6.2
  Uname: Linux 5.6.0-1007-oem x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 01:37:30 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
  InstallationDate: Installed on 2020-04-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411)
  MachineType: Dell Inc. XPS 13 9380
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1007-oem 
root=UUID=0b23d7d3-fb6c-4ee1-9681-71d148d364d1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872788/+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 1872788] [NEW] super key searching show incomplete icon

2020-04-14 Thread Alex Tu
Public bug reported:

compare to bionic, bionic will show complete icon when I press super key
and type prefix of application.

But in Focal, the icon is incomplete as attache screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.6.0-1007.7-oem 5.6.2
Uname: Linux 5.6.0-1007-oem x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 15 01:37:30 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
InstallationDate: Installed on 2020-04-12 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411)
MachineType: Dell Inc. XPS 13 9380
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1007-oem 
root=UUID=0b23d7d3-fb6c-4ee1-9681-71d148d364d1 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.0
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9380
dmi.product.sku: 08AF
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
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+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption focal ubuntu

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

Title:
  super key searching show incomplete icon

Status in xorg package in Ubuntu:
  New

Bug description:
  compare to bionic, bionic will show complete icon when I press super
  key and type prefix of application.

  But in Focal, the icon is incomplete as attache screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.6.0-1007.7-oem 5.6.2
  Uname: Linux 5.6.0-1007-oem x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 01:37:30 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
  InstallationDate: Installed on 2020-04-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411)
  MachineType: Dell Inc. XPS 13 9380
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1007-oem 
root=UUID=0b23d7d3-fb6c-4ee1-9681-71d148d364d1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1763611] Re: Lubuntu bionic boots slower than the other Ubuntu flavours with some SSDs

2020-04-14 Thread Ginés Utrera Pavón
*** This bug is a duplicate of bug 1768230 ***
https://bugs.launchpad.net/bugs/1768230

For the versions of Ubuntu in which the file does not exist, we simply
create it with the name 'resume', containing within the parameter
'RESUME = none'.

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

Title:
  Lubuntu bionic boots slower than the other Ubuntu flavours with some
  SSDs

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Fix Released

Bug description:
  See this thread at the Ubuntu Forums:

  https://ubuntuforums.org/showthread.php?t=2388799

  How come the ultra light Lubuntu Bionic needs 40 seconds from the grub
  menu to the log in screen, while the corresponding Kubuntu and Xubuntu
  Bionic can do it in 10 seconds in my Toshiba laptop?

  All the operating systems were installed from the Bionic Beta-2
  desktop 64-bit iso files and made up to date today (and reside in a
  new SSD connected via the internal SATA bay).

  -o-

  and to summarize the conclusion

  
https://ubuntuforums.org/showthread.php?t=2388799=2=13756324#post13756324

  This supports the assumption, that there are problems for Lubuntu to
  manage SSDs with 4096 byte size physical sectors. But the other
  flavours of Ubuntu can manage it.

  Let us hope that this can help the Lubuntu developer to find and
  squash the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lubuntu-desktop 0.93
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Apr 13 09:59:42 2018
  InstallationDate: Installed on 2018-04-06 (7 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180405)
  SourcePackage: lubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1763611/+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 1866974] Re: The Diffie-Hellman prime sent by the server is not acceptable

2020-04-14 Thread Steven Jay Cohen
*** This bug is a duplicate of bug 1872778 ***
https://bugs.launchpad.net/bugs/1872778

** This bug is no longer a duplicate of bug 1860461
   libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with 
error "Error performing TLS handshake: The Diffie-Hellman prime sent by the 
server is not acceptable (not long enough)."
** This bug has been marked a duplicate of bug 1872778
   update-crypto-policies not affecting Gnome Online Accounts

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

Title:
  The Diffie-Hellman prime sent by the server is not acceptable

Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  I can no longer connect to my ISP mail server.
  Works in previous version 19.10

  "The reported error was “Failed to get capabilities: Error performing
  TLS handshake: The Diffie-Hellman prime sent by the server is not
  acceptable (not long enough).”."

  I've tried finding a workaround but so far no luck.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: evolution 3.35.92-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 11:07:01 2020
  InstallationDate: Installed on 2020-03-03 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974/+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 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acc

2020-04-14 Thread Steven Jay Cohen
*** This bug is a duplicate of bug 1872778 ***
https://bugs.launchpad.net/bugs/1872778

** This bug has been marked a duplicate of bug 1872778
   update-crypto-policies not affecting Gnome Online Accounts

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

Title:
  libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client
  with error "Error performing TLS handshake: The Diffie-Hellman prime
  sent by the server is not acceptable (not long enough)."

Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  Confirmed
Status in gnutls28 package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to 20.04 package libgnutls30 broke pulseUI VPN client
  with the following error:

  "Error performing TLS handshake: The Diffie-Hellman prime sent by the
  server is not acceptable (not long enough)."

  I had to revert the package to the 19.10 version (3.6.9-5ubuntu1) and
  to install 19.10 dependency libhogweed4 3.4.1-1 to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgnutls30 3.6.9-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Tue Jan 21 17:48:39 2020
  InstallationDate: Installed on 2017-06-21 (943 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnutls28
  UpgradeStatus: Upgraded to focal on 2020-01-10 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+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 1872778] Re: update-crypto-policies not affecting Gnome Online Accounts

2020-04-14 Thread Steven Jay Cohen
** Also affects: gnome-online-accounts (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update-crypto-policies not affecting Gnome Online Accounts

Status in gnome-online-accounts package in Ubuntu:
  New
Status in gnutls28 package in Ubuntu:
  Confirmed

Bug description:
  -crypto-policies 20190816git-1
  -gnome-online-accounts 3.36.0-1ubuntu1

  Changing between DEFAULT, LEGACY, and EMPTY has no affect on attempts
  to connect to accounts through Online Accounts.

  Changing to LEGACY or EMPTY should at least change the following
  error:

  Error performing TLS handshake: The Diffie-Hellman prime sent by the
  server is not acceptable (not long enough).

  Under either LEGACY or EMPTY the (not long enough) error is
  nonsensical. The persistence of the incorrect error message could
  imply that gnome-online-accounts is not respecting settings made by
  crypto-policies.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1872778/+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 1872286] Re: gio - cifs mount smb not possible "Location is not mountable"

2020-04-14 Thread Dirk Heumann
I found out, that I had to install the package `gvfs-backends` to get
`gvfsd-smb`:

`$ find /usr -name 'gvfsd-smb' -exec ls -l '{}' \; 2>/dev/null`
`-rwxr-xr-x 1 root root 59704 Mär 11 17:23 /usr/libexec/gvfsd-smb`
`lrwxrwxrwx 1 root root 23 Mär 11 17:23 /usr/lib/gvfs/gvfsd-smb -> 
../../libexec/gvfsd-smb`

After installing it, I got:

`$ gio mount smb://192.168.178.1/PathName`
`gio: smb://192.168.178.1/PathName/: Failed to mount Windows share: Software 
caused connection abort`
`gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse` 
`(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)`

I will reboot the machine to look if there is another result afterwards.

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

Title:
  gio - cifs mount smb not possible "Location is not mountable"

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  1) Release
  $ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2) Package
  $ apt-cache policy libglib2.0-bin
  libglib2.0-bin:
Installed: 2.64.1-1
Candidate: 2.64.1-1
Version table:
   *** 2.64.1-1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) Expected to happen
  The path should be mounted at
  /run/user/1000/gvfs/smb-share:server=192.168.178.1,share=PathName/

  4) What happened instead:
  Error Message:
  gio: smb://192.168.178.1/PathName/: Location is not mountable

  5) Long description / explanation
  Since some years, I mount a Windows drive with

  gio mount smb://192.168.178.1/PathName

  After upgrading from 19.04 to 20.04 beta, this does not work any more,
  I get the error message

  gio: smb://192.168.178.1/PathName/: Location is not mountable

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-bin 2.64.1-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 12 12:43:53 2020
  InstallationDate: Installed on 2019-02-17 (420 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: glib2.0
  UpgradeStatus: Upgraded to focal on 2020-04-05 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1872286/+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 1871615] Re: package apparmor 2.13.3-7ubuntu4 failed to install/upgrade: end of file on stdin at conffile prompt

2020-04-14 Thread Launchpad Bug Tracker
This bug was fixed in the package unattended-upgrades - 2.3

---
unattended-upgrades (2.3) unstable; urgency=medium

  * Fix checking if Python regexp is also a POSIX regexp
  * Prepend implied '^' when converting Python regex to a POSIX one
  * Blacklist not trusted packages and ones with conffile prompts
instead of just pinning them once with NEVER_PIN which is can be cleared
later. (LP: #1871615) (Closes: #956339)

 -- Balint Reczey   Tue, 14 Apr 2020 00:37:21 +0200

** Changed in: unattended-upgrades (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  package apparmor 2.13.3-7ubuntu4 failed to install/upgrade: end of
  file on stdin at conffile prompt

Status in apparmor package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Debian:
  Fix Released

Bug description:
  I have no definite idea what happened, it just popped up randomly.

  I can only assume it was trying to show the usual update notification

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: apparmor 2.13.3-7ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  AptOrdering:
   apparmor:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Apr  8 13:57:33 2020
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2020-03-25 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=66ca0e88-1f73-48ce-a0ae-cfa14442ffe1 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.1ubuntu1
  SourcePackage: apparmor
  Syslog:
   Apr  8 13:04:35 sebipc dbus-daemon[1090]: [system] AppArmor D-Bus mediation 
is enabled
   Apr  8 13:04:44 sebipc dbus-daemon[1479]: [session uid=125 pid=1479] 
AppArmor D-Bus mediation is enabled
   Apr  8 13:05:16 sebipc dbus-daemon[2072]: [session uid=1000 pid=2072] 
AppArmor D-Bus mediation is enabled
   Apr  8 13:55:52 sebipc dbus-daemon[2072]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" path="/" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="com.canonical.Unity" pid=11890 
label="snap.telegram-desktop.telegram-desktop" peer_pid=2359 
peer_label="unconfined"
   Apr  8 13:55:53 sebipc dbus-daemon[2072]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" path="/org/freedesktop/ScreenSaver" 
interface="org.freedesktop.ScreenSaver" member="GetSessionIdleTime" mask="send" 
name="org.freedesktop.ScreenSaver" pid=11890 
label="snap.telegram-desktop.telegram-desktop" peer_pid=2462 
peer_label="unconfined"
  Title: package apparmor 2.13.3-7ubuntu4 failed to install/upgrade: end of 
file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apparmor.d.abstractions.base: 2020-03-26T13:00:28.401582

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1871615/+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 1872286] Re: gio - cifs mount smb not possible "Location is not mountable"

2020-04-14 Thread Dirk Heumann
Comments on  
https://gitlab.gnome.org/GNOME/glib/-/issues/2090  
showed, that there is this file `/usr/share/gvfs/mounts/smb.mount`  
in Ubuntu 19.10, which is not there in Ubuntu 20.04 beta.

Inside of this file, there was a reference to the file  
`/usr/lib/gvfs/gvfsd-smb`. Also a file `/usr/libexec/gvfsd-smb`  
cannot be found.

I did not get any debug logs, I think because the prerequisites
are missing.

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

Title:
  gio - cifs mount smb not possible "Location is not mountable"

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  1) Release
  $ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2) Package
  $ apt-cache policy libglib2.0-bin
  libglib2.0-bin:
Installed: 2.64.1-1
Candidate: 2.64.1-1
Version table:
   *** 2.64.1-1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) Expected to happen
  The path should be mounted at
  /run/user/1000/gvfs/smb-share:server=192.168.178.1,share=PathName/

  4) What happened instead:
  Error Message:
  gio: smb://192.168.178.1/PathName/: Location is not mountable

  5) Long description / explanation
  Since some years, I mount a Windows drive with

  gio mount smb://192.168.178.1/PathName

  After upgrading from 19.04 to 20.04 beta, this does not work any more,
  I get the error message

  gio: smb://192.168.178.1/PathName/: Location is not mountable

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-bin 2.64.1-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 12 12:43:53 2020
  InstallationDate: Installed on 2019-02-17 (420 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: glib2.0
  UpgradeStatus: Upgraded to focal on 2020-04-05 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1872286/+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 1872765] Re: nm-online crashed with SIGSEGV in g_source_set_ready_time()

2020-04-14 Thread Apport retracing service
*** This bug is a duplicate of bug 1866783 ***
https://bugs.launchpad.net/bugs/1866783

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1866783, so 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.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1872765/+attachment/5353909/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1872765/+attachment/5353911/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1872765/+attachment/5353921/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1872765/+attachment/5353922/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1872765/+attachment/5353923/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1872765/+attachment/5353925/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1872765/+attachment/5353926/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1866783

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nm-online crashed with SIGSEGV in g_source_set_ready_time()

Status in network-manager package in Ubuntu:
  New

Bug description:
  Not sure what this is exactly; I received a crash notification upon
  bootup, but network-manager's functionality didn't appear to be
  impacted.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr  7 06:12:06 2020
  ExecutablePath: /usr/bin/nm-online
  InstallationDate: Installed on 2020-01-25 (79 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 10.9.8.1 dev wlp3s0 proto dhcp metric 600 
   10.9.8.0/21 dev wlp3s0 proto kernel scope link src 10.9.14.138 metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcCmdline: nm-online -q --timeout 30
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f351720fbf3 :   cmp
0x10(%rax),%rbp
   PC (0x7f351720fbf3) ok
   source "0x10(%rax)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   g_source_set_ready_time () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nm-online crashed with SIGSEGV in g_source_set_ready_time()
  UpgradeStatus: Upgraded to focal on 2020-04-03 (10 days ago)
  UserGroups:
   
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1872765/+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 1870930] Re: systemctl crashed with SIGSEGV

2020-04-14 Thread Gunnar Hjalmarsson
Thanks for letting me know, Balint. Then it was no confusion on my side,
after all. :)

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

Title:
  systemctl crashed with SIGSEGV

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Logged in to an updated focal, entered a few unrelated commands in
  gnome-terminal, and then the crash message showed up.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Apr  5 16:26:11 2020
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/systemctl
  InstallationDate: Installed on 2019-11-10 (147 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Notebook P64_HJ,HK1
  ProcCmdline: systemctl --user start --wait unity-session.target
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=a8fd6652-86e7-4e1a-8259-809e0a4abd2b ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-timesyncd.service → 
/usr/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: systemctl crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.08
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P64_HJ,HK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.08:bd07/06/2017:svnNotebook:pnP64_HJ,HK1:pvrNotApplicable:rvnNotebook:rnP64_HJ,HK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P64_HJ,HK1
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870930/+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 1870930] Re: systemctl crashed with SIGSEGV

2020-04-14 Thread Balint Reczey
@gunnarhj The crashes happen when exiting Unity the collection happended in the 
standard Ubuntu session AFAICT.
All similar crashes I saw crashed waiting for the unity-session.target.

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

Title:
  systemctl crashed with SIGSEGV

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Logged in to an updated focal, entered a few unrelated commands in
  gnome-terminal, and then the crash message showed up.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Apr  5 16:26:11 2020
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/systemctl
  InstallationDate: Installed on 2019-11-10 (147 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Notebook P64_HJ,HK1
  ProcCmdline: systemctl --user start --wait unity-session.target
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=a8fd6652-86e7-4e1a-8259-809e0a4abd2b ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-timesyncd.service → 
/usr/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: systemctl crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.08
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P64_HJ,HK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.08:bd07/06/2017:svnNotebook:pnP64_HJ,HK1:pvrNotApplicable:rvnNotebook:rnP64_HJ,HK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P64_HJ,HK1
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870930/+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 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

2020-04-14 Thread Sebastien Bacher
** Changed in: gnome-control-center (Ubuntu Focal)
   Status: Incomplete => Invalid

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

Title:
  External audio device shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker, or none at
  all.

Status in gnome-control-center:
  Unknown
Status in PulseAudio:
  New
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  In Progress
Status in gnome-control-center source package in Focal:
  Invalid
Status in pulseaudio source package in Focal:
  In Progress

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

  1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
  2. Make sure it's the one selected as "Output device"
  3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  5. Try to switch back to the BT device and click Test
  -> same result as in step 3

  Tested with 2 different BT devices (one headset and one speaker) as
  well as a USB audio interface (Zoom H2N microphone).

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+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 1791405] Re: bluetooth always in discoverable mode (security issue)

2020-04-14 Thread Sebastien Bacher
(removing the focal targetting, there is no assigne nor sign it deserve
particular handling)

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

Title:
  bluetooth always in discoverable mode (security issue)

Status in bluez package in Ubuntu:
  Triaged
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in gnome-bluetooth source package in Bionic:
  Fix Released
Status in gnome-bluetooth source package in Cosmic:
  Fix Released
Status in gnome-bluetooth source package in Disco:
  Fix Released
Status in gnome-bluetooth source package in Focal:
  Fix Released
Status in gnome-bluetooth package in Fedora:
  Won't Fix

Bug description:
  Excerpt from a similar report
  (https://bugzilla.redhat.com/show_bug.cgi?id=1602985) :

  Opening the Bluetooth settings will make the device discoverable
  again, but does not make the device undiscoverable after the settings
  are closed (this is not intended behavior; devices should only be
  discoverable when the bluetooth settings UI is open).

  There seem to be a merge request :

  https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/1

  Could you please merge it asap, it should be treated as a security
  issue IMHO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1791405/+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 1872282] Re: Failed to get user record: Invalid argument

2020-04-14 Thread Josef Hopfgartner
Hey Balint,

thanks for the fix!
Works like a charm right now.

I've also noticed an improvement with version 245:
after reboot gdm login screen displays the last logins from AD/winbind accounts 
the same like from UNIX accounts.

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

Title:
  Failed to get user record: Invalid argument

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  system is ubuntu focal with pam_winbind and nss_winbind enabled.

  unix users are not affected.
  this bug won't happen with systemd version 2.44.3

  beginning with version 245 (including 245.4-2) no user session will be 
created after login.
  login itself works e.g. on tty2.
  but loginctl does not show a corresponding user session.
  gdm login needs a user session, so it fails.

  this bug already seems to be handled here:
  https://github.com/systemd/systemd/issues/15149

  this bug only affects user sessions directly on a samba domain controller.
  users can log in with pam_systemd version 245 on winbind client workstations 
in the same domain.

  journalctl reports:
  Apr 10 14:11:23 joebook.netzagentur.localdomain login[21975]: 
pam_systemd(login:session): Failed to get user record: Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-systemd:amd64 244.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Apr 12 11:44:41 2020
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1872282/+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 1872551] Re: software-properties-qt: nvidia driver version switch fails

2020-04-14 Thread Horst Schirmeier
The patch in comment #9 solves the issue for me.

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

Title:
  software-properties-qt: nvidia driver version switch fails

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Switching the Nvidia driver version with kubuntu-driver-manager
  doesn't work anymore: Selecting a different driver version (nvidia-
  driver-440 instead of the currently selected / installed -390) and
  clicking "Apply Changes" has no effect and produces this error message
  in the terminal:

Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 895, in on_driver_changes_apply
  for dep in get_dependencies(self.apt_cache, pkg.shortname, 'nvidia'):
  NameError: name 'get_dependencies' is not defined

  Steps to reproduce:
  - sudo kubuntu-driver-manager
  - Under "Additional Drivers", select a different Nvidia driver version
(in my case: 440 instead of 390)
  - Click "Apply Changes"
  - (observe error message in the terminal)

  Expected result:
  - No error message
  - Nvidia driver version 440 gets installed

  Actual result:
  - Error message
  - No change in the installed Nvidia driver version

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: kubuntu-driver-manager (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 13 23:41:56 2020
  InstallationDate: Installed on 2016-11-26 (1234 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  SourcePackage: kubuntu-driver-manager
  UpgradeStatus: Upgraded to focal on 2020-03-06 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1872551/+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 1685754] Re: gnome-terminal unduly forces umask=0022

2020-04-14 Thread Balint Reczey
** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  gnome-terminal unduly forces umask=0022

Status in gedit:
  Invalid
Status in gnome-session:
  New
Status in GNOME Terminal:
  Confirmed
Status in Nautilus:
  Confirmed
Status in dbus package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  In order to set the default umask of my users to 027 or 007, I
  followed the instructions provided in 'man pam_umask' :

  In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
  'umask=007' (for myself).

  Then, MOST graphical applications systematically run with the correct
  umask.

  In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
  it systematically displays 0007.

  But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
  it systematically displays 0022.

  That is BAD, and is a security issue.

  
  Workaround :  Inside the newly created '/etc/profile.d/umask.sh', and in each 
'~/.bashrc', add following content :
  UMASK="$(grep  -o  "^$USER:.*,umask=0[0-7]*"  /etc/passwd)"
  if  [ "$UMASK" ];  then
umask  "${UMASK#$USER:*,umask=}"
  fi

  
  In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.

  Thank you in advance for a quick correction.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 24 08:36:58 2017
  InstallationDate: Installed on 2017-03-28 (26 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+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 1791405] Re: bluetooth always in discoverable mode (security issue)

2020-04-14 Thread Sebastien Bacher
** No longer affects: bluez (Ubuntu Focal)

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

Title:
  bluetooth always in discoverable mode (security issue)

Status in bluez package in Ubuntu:
  Triaged
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in gnome-bluetooth source package in Bionic:
  Fix Released
Status in gnome-bluetooth source package in Cosmic:
  Fix Released
Status in gnome-bluetooth source package in Disco:
  Fix Released
Status in gnome-bluetooth source package in Focal:
  Fix Released
Status in gnome-bluetooth package in Fedora:
  Won't Fix

Bug description:
  Excerpt from a similar report
  (https://bugzilla.redhat.com/show_bug.cgi?id=1602985) :

  Opening the Bluetooth settings will make the device discoverable
  again, but does not make the device undiscoverable after the settings
  are closed (this is not intended behavior; devices should only be
  discoverable when the bluetooth settings UI is open).

  There seem to be a merge request :

  https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/1

  Could you please merge it asap, it should be treated as a security
  issue IMHO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1791405/+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 1870135] Re: Focal Fossa : Systemd show warning when username or groupname contain a dot

2020-04-14 Thread Balint Reczey
** Changed in: systemd (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Focal Fossa : Systemd show warning when username or groupname contain
  a dot

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  I am currently working on ubuntu 20.04 server
  when username contain a dot, systemd show warning.

  how to test :

  useradd u.user
  su - u.user

  Output : 
  Creating directory '/home/u.user'.
  Bad user or group name "u.user", accepting for compatibility.

  In my real life, i have this problem with Active Directory groups that
  contains a dot.

  More information about this from my search : 
  https://github.com/systemd/systemd/pull/13244
  https://bugzilla.redhat.com/show_bug.cgi?id=1717603

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870135/+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 1872715] [NEW] 5.1 audio does not work properly [To Be Filled By O.E.M., Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] Playback problem

2020-04-14 Thread Lando
Public bug reported:

Hello,

I am using Ubuntu 19.10 with 5.1 surround speakers.
I tried to configure 5.1 surround, but it still doesn't work.
I also installed Pulse audio.
Here is the info about my soundcard:
# aplay -l
 Lista PLAYBACK de dispozitive 
placa 0: PCH [HDA Intel PCH], dispozitiv 0: ALC892 Analog [ALC892 Analog]
  subdispozitive: 0/1
  Subdispozitiv #0: subdevice #0
placa 1: NVidia [HDA NVidia], dispozitiv 3: HDMI 0 [HDMI 0]
  subdispozitive: 1/1
  Subdispozitiv #0: subdevice #0
placa 1: NVidia [HDA NVidia], dispozitiv 7: HDMI 1 [HDMI 1]
  subdispozitive: 1/1
  Subdispozitiv #0: subdevice #0
placa 1: NVidia [HDA NVidia], dispozitiv 8: HDMI 2 [HDMI 2]
  subdispozitive: 1/1
  Subdispozitiv #0: subdevice #0
placa 1: NVidia [HDA NVidia], dispozitiv 9: HDMI 3 [HDMI 3]
  subdispozitive: 1/1
  Subdispozitiv #0: subdevice #0

See 'lscpi -v' output attached.


$ speaker-test -c6 -l1 -twav

speaker-test 1.1.9

Playback device is default
Stream parameters are 48000Hz, S16_LE, 6 channels
WAV file(s)
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 32 to 349525
Period size range from 10 to 116509
Using max buffer size 349524
Periods = 4
was set period_size = 87381
was set buffer_size = 349524
 0 - Față stânga
 4 - Centru
 1 - Față dreapta
 3 - Spate dreapta
 2 - Spate stânga
 5 - LFE
Timp per Perioada = 8,733519


I tried the test below and instead of center speaker, right speaker plays two 
times and the subwoofer do not work at all.

Please let me know what other details you need.

Thank you!

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  lucian 1257 F pulseaudio
 /dev/snd/controlC0:  lucian 1257 F pulseaudio
 /dev/snd/pcmC0D0p:   lucian 1257 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 14 16:46:45 2020
InstallationDate: Installed on 2019-03-30 (380 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ro_RO.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: GP106 High Definition Audio Controller - HDA NVidia
Symptom_Jack: Digital Out, HDMI
Symptom_Type: Only some of outputs are working
Title: [To Be Filled By O.E.M., Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] 
Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/21/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P7.30
dmi.board.name: B150 Pro4/3.1
dmi.board.vendor: ASRock
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.:bvrP7.30:bd11/21/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150Pro4/3.1:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-17T14:42:34.178435

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

** Attachment added: "lspci"
   
https://bugs.launchpad.net/bugs/1872715/+attachment/5353855/+files/lspci-v.out

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

Title:
  5.1 audio does not work properly [To Be Filled By O.E.M., Nvidia GPU
  84 HDMI/DP, Digital Out, HDMI] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,

  I am using Ubuntu 19.10 with 5.1 surround speakers.
  I tried to configure 5.1 surround, but it still doesn't work.
  I also installed Pulse audio.
  Here is the info about my soundcard:
  # aplay -l
   Lista PLAYBACK de dispozitive 
  placa 0: PCH [HDA Intel PCH], dispozitiv 0: ALC892 Analog [ALC892 Analog]
subdispozitive: 0/1
Subdispozitiv #0: subdevice #0
  placa 1: NVidia [HDA NVidia], dispozitiv 3: HDMI 0 [HDMI 0]
subdispozitive: 1/1
Subdispozitiv #0: subdevice #0
  placa 1: NVidia [HDA NVidia], dispozitiv 7: HDMI 1 [HDMI 1]
subdispozitive: 1/1
Subdispozitiv #0: subdevice #0
  placa 1: NVidia [HDA NVidia], dispozitiv 8: HDMI 2 [HDMI 2]
subdispozitive: 1/1
Subdispozitiv #0: subdevice #0
  placa 1: NVidia [HDA NVidia], dispozitiv 9: HDMI 3 [HDMI 3]
   

[Touch-packages] [Bug 1872282] Re: Failed to get user record: Invalid argument

2020-04-14 Thread Balint Reczey
If you can, please check systemd in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3801 . It has the upstream fix for the user name
handling regression and the package is planned to land later today in
20.04.


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

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

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Balint Reczey (rbalint)

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

Title:
  Failed to get user record: Invalid argument

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  system is ubuntu focal with pam_winbind and nss_winbind enabled.

  unix users are not affected.
  this bug won't happen with systemd version 2.44.3

  beginning with version 245 (including 245.4-2) no user session will be 
created after login.
  login itself works e.g. on tty2.
  but loginctl does not show a corresponding user session.
  gdm login needs a user session, so it fails.

  this bug already seems to be handled here:
  https://github.com/systemd/systemd/issues/15149

  this bug only affects user sessions directly on a samba domain controller.
  users can log in with pam_systemd version 245 on winbind client workstations 
in the same domain.

  journalctl reports:
  Apr 10 14:11:23 joebook.netzagentur.localdomain login[21975]: 
pam_systemd(login:session): Failed to get user record: Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-systemd:amd64 244.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Apr 12 11:44:41 2020
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1872282/+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 1868246] Re: No network after subiquity LPAR installation on s390x with VLAN

2020-04-14 Thread Frank Heimes
Yes, I can confirm that this is fixed now (using image from Apr 14th) -
many thx!

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

Title:
  No network after subiquity LPAR installation on s390x with VLAN

Status in cloud-init:
  Invalid
Status in subiquity:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I tried today an subiquity LPAR installation using the latest ISO (March 19) 
that includes the latest 20.03 subiquity.
  The installation itself completed fine, but after the post-install reboot the 
system didn't had a network active - please note that the LPAR is connected to 
a VLAN.

  $ ip a   
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
defaul
  t qlen 1000   
  
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 
  
  inet 127.0.0.1/8 scope host lo
  
 valid_lft forever preferred_lft forever
  
  inet6 ::1/128 scope host  
  
 valid_lft forever preferred_lft forever
  
  2: encc000:  mtu 1500 qdisc noop state DOWN group 
default q
  len 1000  
  
  link/ether a2:8d:91:85:12:e3 brd ff:ff:ff:ff:ff:ff
  
  3: enP1p0s0:  mtu 1500 qdisc noop state DOWN group 
default 
  qlen 1000 
  
  link/ether 82:0c:2d:0c:b8:70 brd ff:ff:ff:ff:ff:ff
  
  4: enP1p0s0d1:  mtu 1500 qdisc noop state DOWN group 
defaul
  t qlen 1000   
  
  link/ether 82:0c:2d:0c:b8:71 brd ff:ff:ff:ff:ff:ff
  
  5: enP2p0s0:  mtu 1500 qdisc noop state DOWN group 
default 
  qlen 1000 
  
  link/ether 82:0c:2d:0c:b7:00 brd ff:ff:ff:ff:ff:ff
  
  6: enP2p0s0d1:  mtu 1500 qdisc noop state DOWN group 
defaul
  t qlen 1000   
  
  link/ether 82:0c:2d:0c:b7:01 brd ff:ff:ff:ff:ff:ff   

  Wanting to have a look at the netplan config it turned out that there is no 
yaml file:
  $ ls -l /etc/netplan/
  total 0  

  Adding one manually and applying it worked fine.

  So looks like the installer does not properly generate or copy a
  01-netcfg.yaml to /etc/netplan.

  Please see below the entire steps as well as a compressed file with
  the entire content of /var/log

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1868246/+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 1872502] Re: There is no installable python package on Focal

2020-04-14 Thread Matthias Klose
we have removed any reference to the python package in the archive.
Packages have to explicitly depend on python2 or python3.

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

Title:
  There is no installable python package on Focal

Status in python-defaults package in Ubuntu:
  New

Bug description:
  There is no installable "python" package on Focal. An attempt to
  install it produces the following error:

  $ sudo apt install python
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Package python is not available, but is referred to by another package.
  This may mean that the package is missing, has been obsoleted, or
  is only available from another source
  However the following packages replace it:
python2-minimal:i386 python2:i386 python2-minimal python2 python-is-python2 
2to3 python-is-python3

  E: Package 'python' has no installation candidate

  This breaks the installation of many other software packages which
  have the "python" package as a dependency.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1872502/+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 1871019] Re: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work)

2020-04-14 Thread Christopher Leggett
Ok sounds good. Should I expect these to come through as an update
through the Software Updater eventually?

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

Title:
  Nextcloud account added to Online Accounts does not populate Calendar
  apps (WebDAV file sharing does work)

Status in gnome-online-accounts:
  Unknown
Status in gnome-online-accounts package in Ubuntu:
  In Progress

Bug description:
  My Nextcloud server was working fine with previous versions of Ubuntu,
  but on the 20.04 daily when I add my Nextcloud account it does not
  populate my Calendars or todo lists. It does give me file access via
  WebDAV. Server is working fine as far as I'm aware. Going to Settings
  -> Administration - Overview shows me any configuration issues it can
  detect, currently the only error there is related to background job
  execution (which is only relevant to the News app if I'm not
  mistaken).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-online-accounts 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  5 23:59:55 2020
  InstallationDate: Installed on 2020-04-03 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1871019/+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


  1   2   >