[Touch-packages] [Bug 852276] Re: package libdbusmenu-qt2 0.8.2-0ubuntu2 failed to install/upgrade: archive du système de fichiers corrompue - archive du paquet corrompue

2019-12-18 Thread Rik Mills
** Changed in: libdbusmenu-qt (Ubuntu)
   Status: New => Won't Fix

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

Title:
  package libdbusmenu-qt2 0.8.2-0ubuntu2 failed to install/upgrade:
  archive du système de fichiers corrompue - archive du paquet corrompue

Status in libdbusmenu-qt package in Ubuntu:
  Won't Fix

Bug description:
  apres telechargement du drivers nvidia 280.13 pas moyen de l'ouvrir
  pour l'intaller .!!!

  ProblemType: Package
  DistroRelease: Ubuntu 11.04
  Package: libdbusmenu-qt2 0.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sat Sep 17 01:10:25 2011
  ErrorMessage: archive du système de fichiers corrompue - archive du paquet 
corrompue
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  SourcePackage: libdbusmenu-qt
  Title: package libdbusmenu-qt2 0.8.2-0ubuntu2 failed to install/upgrade: 
archive du système de fichiers corrompue - archive du paquet corrompue
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/852276/+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 1682297] Re: package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: poging tot overschrijven van '/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', wat ook in pa

2019-12-18 Thread Rik Mills
** Changed in: libdbusmenu-qt (Ubuntu)
   Status: New => Won't Fix

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

Title:
  package libdbusmenu-qt5-2 (not installed) failed to install/upgrade:
  poging tot overschrijven van '/usr/lib/x86_64-linux-gnu/libdbusmenu-
  qt5.so.2.6.0', wat ook in pakket libdbusmenu-qt5:amd64
  0.9.3+16.04.20160218-0ubuntu1 zit

Status in libdbusmenu-qt package in Ubuntu:
  Won't Fix

Bug description:
  i clicked to install a lot of software at once

  ProblemType: Package
  DistroRelease: Kali 2017.1
  Package: libdbusmenu-qt5-2 (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-lowlatency 4.8.17
  Uname: Linux 4.8.0-46-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Apr 12 23:45:47 2017
  ErrorMessage: poging tot overschrijven van 
'/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', wat ook in pakket 
libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1 zit
  InstallationDate: Installed on 2017-04-11 (1 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.23kali1
   apt  1.2.19
  SourcePackage: libdbusmenu-qt
  Title: package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: 
poging tot overschrijven van 
'/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', wat ook in pakket 
libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1 zit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1682297/+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 1856953] Re: Misconfigured Debian control file makes dist-upgrading with package libdbusmenu-qt5 crash

2019-12-18 Thread Rik Mills
A direct xenial to eoan upgrade path is NOT supported.

The correct breaks/replaces are in place for any supported upgrade
paths, and have quite correctly been dropped after Bionic, where keeping
that delta to debian is no longer required.

** Changed in: libdbusmenu-qt (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Misconfigured Debian control file makes dist-upgrading with package
  libdbusmenu-qt5 crash

Status in libdbusmenu-qt package in Ubuntu:
  Won't Fix

Bug description:
  Dear maintainers,

  Lacking of `Breaks` and `Replaces` parts in the Debian control file of
  libdbusmenu-qt5-2 package (version 0.9.3+16.04.20160218-2) would make
  dist-upgrading from Xenial (with libdbusmenu-qt5 installed) to Eoan or
  Focal crash.

  Expected behavior of dist-upgrading:
  - should deconfigure `libdbusmenu-qt5` first
  - only then can `libdbusmenu-qt5-2` be installed

  What happened instead:
  - dpkg unpacks `libdbusmenu-qt5-2` over files of `libdbusmenu-qt5`, thus 
causing a crash

  Steps to reproduce:
  1. install a fresh Ubuntu 16.04.6 and upgrade packages
  2. change the release in apt source list from `xenial` to `eoan` or `focal` 
and include universe section
  3. perform `apt dist-upgrade`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1856953/+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 1757730] Re: Please port your package away from Qt 4

2019-12-18 Thread Rik Mills
** Changed in: libdbusmenu-qt (Ubuntu)
   Status: New => Fix Released

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

Title:
  Please port your package away from Qt 4

Status in libdbusmenu-qt package in Ubuntu:
  Fix Released
Status in libdbusmenu-qt package in Debian:
  Fix Released

Bug description:
  Currently Qt 4 has been dead upstream and we are starting to have
  problems maintaining it, like for example in the OpenSSL 1.1 support
  case.

  Following in the footsteps of Debian[1], all packages directly or
  indirectly depending on qt4-x11 (like this one) must either get ported
  to Qt 5 and uploaded to the development release or get removed (by
  means of demotion to -proposed or removal of the package) before the
  19.04 release. If it is possible to port your package by the 18.10
  release, please do so.

  If you have any questions about porting or this transition, please ask
  in #ubuntu-qt (preferred) or directly ping me

  [1] https://wiki.debian.org/Qt4Removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1757730/+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 1856884] Re: not proper sound device

2019-12-18 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1847570 ***
https://bugs.launchpad.net/bugs/1847570

Thanks! This makes me think you are experiencing bug 1847570:
Default sink name: alsa_output.pci-_26_00.1.hdmi-stereo-extra1

Please wait till a fix for that is available, which will be soon.


** This bug has been marked a duplicate of bug 1847570
   PulseAudio automatically switches to HDMI sound output on login

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

Title:
  not proper sound device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  when i insert or take out my headphones , the system doesn't send signal on 
my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1929 F pulseaudio
   /dev/snd/controlC1:  rob1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (326 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884/+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 1856946] Re: system freezes after prolonged usage

2019-12-18 Thread Daniel van Vugt
When the system freezes,

1. Can you still move the mouse?

2. If you have these commands running in Terminal windows already:
dmesg
journalctl -f
   then do they show anything new after the freeze?

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  system freezes after prolonged usage

Status in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:27:43 2019
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-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.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: systemd 242-7ubuntu3.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

To manage notifications about this bug go to:

[Touch-packages] [Bug 1856947] Re: system freezes after prolonged usage

2019-12-18 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1856946 ***
https://bugs.launchpad.net/bugs/1856946

** This bug has been marked a duplicate of bug 1856946
   system freezes after prolonged usage

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

Title:
  system freezes after prolonged usage

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:32:08 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: xorg 1:7.7+19ubuntu12
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
 

[Touch-packages] [Bug 1856953] [NEW] Misconfigured Debian control file makes dist-upgrading with package libdbusmenu-qt5 crash

2019-12-18 Thread Tianyun Zhang
Public bug reported:

Dear maintainers,

Lacking of `Breaks` and `Replaces` parts in the Debian control file of
libdbusmenu-qt5-2 package (version 0.9.3+16.04.20160218-2) would make
dist-upgrading from Xenial (with libdbusmenu-qt5 installed) to Eoan or
Focal crash.

Expected behavior of dist-upgrading:
- should deconfigure `libdbusmenu-qt5` first
- only then can `libdbusmenu-qt5-2` be installed

What happened instead:
- dpkg unpacks `libdbusmenu-qt5-2` over files of `libdbusmenu-qt5`, thus 
causing a crash

Steps to reproduce:
1. install a fresh Ubuntu 16.04.6 and upgrade packages
2. change the release in apt source list from `xenial` to `eoan` or `focal` and 
include universe section
3. perform `apt dist-upgrade`

** Affects: libdbusmenu-qt (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Misconfigured Debian control file makes dist-upgrading with package
  libdbusmenu-qt5 crash

Status in libdbusmenu-qt package in Ubuntu:
  New

Bug description:
  Dear maintainers,

  Lacking of `Breaks` and `Replaces` parts in the Debian control file of
  libdbusmenu-qt5-2 package (version 0.9.3+16.04.20160218-2) would make
  dist-upgrading from Xenial (with libdbusmenu-qt5 installed) to Eoan or
  Focal crash.

  Expected behavior of dist-upgrading:
  - should deconfigure `libdbusmenu-qt5` first
  - only then can `libdbusmenu-qt5-2` be installed

  What happened instead:
  - dpkg unpacks `libdbusmenu-qt5-2` over files of `libdbusmenu-qt5`, thus 
causing a crash

  Steps to reproduce:
  1. install a fresh Ubuntu 16.04.6 and upgrade packages
  2. change the release in apt source list from `xenial` to `eoan` or `focal` 
and include universe section
  3. perform `apt dist-upgrade`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1856953/+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 1856884] CurrentDmesg.txt

2019-12-18 Thread Robert
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1856884/+attachment/5313883/+files/CurrentDmesg.txt

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

Title:
  not proper sound device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  when i insert or take out my headphones , the system doesn't send signal on 
my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1929 F pulseaudio
   /dev/snd/controlC1:  rob1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (326 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884/+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 1856884] Dependencies.txt

2019-12-18 Thread Robert
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1856884/+attachment/5313884/+files/Dependencies.txt

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

Title:
  not proper sound device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  when i insert or take out my headphones , the system doesn't send signal on 
my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1929 F pulseaudio
   /dev/snd/controlC1:  rob1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (326 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884/+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 1856884] ProcCpuinfoMinimal.txt

2019-12-18 Thread Robert
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1856884/+attachment/5313885/+files/ProcCpuinfoMinimal.txt

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

Title:
  not proper sound device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  when i insert or take out my headphones , the system doesn't send signal on 
my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1929 F pulseaudio
   /dev/snd/controlC1:  rob1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (326 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884/+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 1856884] ProcEnviron.txt

2019-12-18 Thread Robert
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1856884/+attachment/5313886/+files/ProcEnviron.txt

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

Title:
  not proper sound device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  when i insert or take out my headphones , the system doesn't send signal on 
my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1929 F pulseaudio
   /dev/snd/controlC1:  rob1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (326 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884/+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 1856884] PulseList.txt

2019-12-18 Thread Robert
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1856884/+attachment/5313887/+files/PulseList.txt

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

Title:
  not proper sound device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  when i insert or take out my headphones , the system doesn't send signal on 
my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1929 F pulseaudio
   /dev/snd/controlC1:  rob1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (326 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884/+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 1856884] Re: not proper sound device

2019-12-18 Thread Robert
apport information

** Tags added: apport-collected

** Description changed:

- when i insert or take out my headphones , the system doesn't send signal
- on my headphones, i need to switch by hand. it worked in ubuntu 18.10
- correct.
+ when i insert or take out my headphones , the system doesn't send signal on 
my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  rob1929 F pulseaudio
+  /dev/snd/controlC1:  rob1929 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2019-01-26 (326 days ago)
+ InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: pulseaudio 1:13.0-1ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
+ Tags:  eoan
+ Uname: Linux 5.3.0-24-generic x86_64
+ UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/19/2018
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: P5.40
+ dmi.board.name: AB350 Pro4
+ 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1856884/+attachment/5313882/+files/AlsaInfo.txt

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

Title:
  not proper sound device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  when i insert or take out my headphones , the system doesn't send signal on 
my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1929 F pulseaudio
   /dev/snd/controlC1:  rob1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (326 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884/+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 1856946] modified.conffile..etc.apport.crashdb.conf.txt

2019-12-18 Thread Seija Kijin
apport information

** Attachment added: "modified.conffile..etc.apport.crashdb.conf.txt"
   
https://bugs.launchpad.net/bugs/1856946/+attachment/5313854/+files/modified.conffile..etc.apport.crashdb.conf.txt

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

Title:
  system freezes after prolonged usage

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:27:43 2019
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-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.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: systemd 242-7ubuntu3.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

-- 
Mailing list: 

[Touch-packages] [Bug 1856947] ProcModules.txt

2019-12-18 Thread Seija Kijin
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1856947/+attachment/5313863/+files/ProcModules.txt

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

Title:
  system freezes after prolonged usage

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:32:08 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: xorg 1:7.7+19ubuntu12
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  

[Touch-packages] [Bug 1856946] UdevDb.txt

2019-12-18 Thread Seija Kijin
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1856946/+attachment/5313853/+files/UdevDb.txt

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

Title:
  system freezes after prolonged usage

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:27:43 2019
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-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.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: systemd 242-7ubuntu3.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1856947] modified.conffile..etc.apport.crashdb.conf.txt

2019-12-18 Thread Seija Kijin
apport information

** Attachment added: "modified.conffile..etc.apport.crashdb.conf.txt"
   
https://bugs.launchpad.net/bugs/1856947/+attachment/5313866/+files/modified.conffile..etc.apport.crashdb.conf.txt

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

Title:
  system freezes after prolonged usage

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:32:08 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: xorg 1:7.7+19ubuntu12
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  

[Touch-packages] [Bug 1856947] xdpyinfo.txt

2019-12-18 Thread Seija Kijin
apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1856947/+attachment/5313867/+files/xdpyinfo.txt

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

Title:
  system freezes after prolonged usage

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:32:08 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: xorg 1:7.7+19ubuntu12
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  

[Touch-packages] [Bug 1856946] ProcInterrupts.txt

2019-12-18 Thread Seija Kijin
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1856946/+attachment/5313851/+files/ProcInterrupts.txt

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

Title:
  system freezes after prolonged usage

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:27:43 2019
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-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.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: systemd 242-7ubuntu3.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1856946] Dependencies.txt

2019-12-18 Thread Seija Kijin
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1856946/+attachment/5313847/+files/Dependencies.txt

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

Title:
  system freezes after prolonged usage

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:27:43 2019
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-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.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: systemd 242-7ubuntu3.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1856947] UdevDb.txt

2019-12-18 Thread Seija Kijin
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1856947/+attachment/5313864/+files/UdevDb.txt

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

Title:
  system freezes after prolonged usage

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:32:08 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: xorg 1:7.7+19ubuntu12
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 

[Touch-packages] [Bug 1856946] ProcModules.txt

2019-12-18 Thread Seija Kijin
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1856946/+attachment/5313852/+files/ProcModules.txt

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

Title:
  system freezes after prolonged usage

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:27:43 2019
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-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.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: systemd 242-7ubuntu3.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1856946] Re: system freezes after prolonged usage

2019-12-18 Thread Seija Kijin
apport information

** Tags added: apport-collected

** Description changed:

  Ubuntu 19.10
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:27:43 2019
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-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.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.2
+ Architecture: amd64
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2019-11-20 (28 days ago)
+ InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
+  Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
+  Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Dell Inc. Inspiron 5570
+ Package: systemd 242-7ubuntu3.2
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
+ 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.
+ Tags:  eoan
+ Uname: Linux 5.3.0-24-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 05/15/2019
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.2.3
+ dmi.board.name: 09YTN7
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
+ dmi.product.family: Inspiron
+ dmi.product.name: Inspiron 5570
+ dmi.product.sku: 0810
+ dmi.sys.vendor: Dell Inc.
+ mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1856946/+attachment/5313846/+files/CurrentDmesg.txt

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

Title:
  system freezes after prolonged usage

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.2
  ProcVersionSignature: Ubuntu 

[Touch-packages] [Bug 1856947] DpkgLog.txt

2019-12-18 Thread Seija Kijin
apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1856947/+attachment/5313858/+files/DpkgLog.txt

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

Title:
  system freezes after prolonged usage

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:32:08 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: xorg 1:7.7+19ubuntu12
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  

[Touch-packages] [Bug 1856947] Lspci.txt

2019-12-18 Thread Seija Kijin
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1856947/+attachment/5313859/+files/Lspci.txt

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

Title:
  system freezes after prolonged usage

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:32:08 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: xorg 1:7.7+19ubuntu12
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 

[Touch-packages] [Bug 1856946] ProcCpuinfo.txt

2019-12-18 Thread Seija Kijin
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1856946/+attachment/5313849/+files/ProcCpuinfo.txt

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

Title:
  system freezes after prolonged usage

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:27:43 2019
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-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.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: systemd 242-7ubuntu3.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1856947] [NEW] system freezes after prolonged usage

2019-12-18 Thread Seija Kijin
Public bug reported:

Ubuntu 19.10

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec 19 01:32:08 2019
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 620 [1028:0810]
InstallationDate: Installed on 2019-11-20 (28 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 5570
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.3
dmi.board.name: 09YTN7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5570
dmi.product.sku: 0810
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CompositorRunning: None
DistUpgraded: Fresh install
DistroCodename: eoan
DistroRelease: Ubuntu 19.10
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 620 [1028:0810]
InstallationDate: Installed on 2019-11-20 (28 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 5570
Package: xorg 1:7.7+19ubuntu12
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Tags:  eoan ubuntu
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
_MarkForUpload: True
dmi.bios.date: 05/15/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.3
dmi.board.name: 09YTN7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5570
dmi.product.sku: 0810
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: 

[Touch-packages] [Bug 1856946] Lspci.txt

2019-12-18 Thread Seija Kijin
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1856946/+attachment/5313848/+files/Lspci.txt

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

Title:
  system freezes after prolonged usage

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:27:43 2019
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-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.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: systemd 242-7ubuntu3.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1856947] Xrandr.txt

2019-12-18 Thread Seija Kijin
apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1856947/+attachment/5313865/+files/Xrandr.txt

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

Title:
  system freezes after prolonged usage

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:32:08 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: xorg 1:7.7+19ubuntu12
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 

[Touch-packages] [Bug 1856946] ProcCpuinfoMinimal.txt

2019-12-18 Thread Seija Kijin
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1856946/+attachment/5313850/+files/ProcCpuinfoMinimal.txt

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

Title:
  system freezes after prolonged usage

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:27:43 2019
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-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.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: systemd 242-7ubuntu3.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  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.
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to 

[Touch-packages] [Bug 1856947] BootLog.txt

2019-12-18 Thread Seija Kijin
apport information

** Attachment added: "BootLog.txt"
   
https://bugs.launchpad.net/bugs/1856947/+attachment/5313855/+files/BootLog.txt

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

Title:
  system freezes after prolonged usage

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:32:08 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: xorg 1:7.7+19ubuntu12
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  

[Touch-packages] [Bug 1856947] CurrentDmesg.txt

2019-12-18 Thread Seija Kijin
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1856947/+attachment/5313856/+files/CurrentDmesg.txt

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

Title:
  system freezes after prolonged usage

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:32:08 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: xorg 1:7.7+19ubuntu12
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  

[Touch-packages] [Bug 1856947] ProcCpuinfo.txt

2019-12-18 Thread Seija Kijin
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1856947/+attachment/5313860/+files/ProcCpuinfo.txt

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

Title:
  system freezes after prolonged usage

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:32:08 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: xorg 1:7.7+19ubuntu12
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  

[Touch-packages] [Bug 1856947] Dependencies.txt

2019-12-18 Thread Seija Kijin
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1856947/+attachment/5313857/+files/Dependencies.txt

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

Title:
  system freezes after prolonged usage

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:32:08 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: xorg 1:7.7+19ubuntu12
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  

[Touch-packages] [Bug 1856947] ProcInterrupts.txt

2019-12-18 Thread Seija Kijin
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1856947/+attachment/5313862/+files/ProcInterrupts.txt

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

Title:
  system freezes after prolonged usage

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:32:08 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: xorg 1:7.7+19ubuntu12
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  

[Touch-packages] [Bug 1856947] ProcCpuinfoMinimal.txt

2019-12-18 Thread Seija Kijin
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1856947/+attachment/5313861/+files/ProcCpuinfoMinimal.txt

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

Title:
  system freezes after prolonged usage

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:32:08 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: xorg 1:7.7+19ubuntu12
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: 

[Touch-packages] [Bug 1856946] [NEW] system freezes after prolonged usage

2019-12-18 Thread Seija Kijin
Public bug reported:

Ubuntu 19.10

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: systemd 242-7ubuntu3.2
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec 19 01:27:43 2019
InstallationDate: Installed on 2019-11-20 (28 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 5570
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /usr/lib/systemd/system/systemd-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.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.3
dmi.board.name: 09YTN7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5570
dmi.product.sku: 0810
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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


** Tags: amd64 apport-bug eoan

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

Title:
  system freezes after prolonged usage

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 01:27:43 2019
  InstallationDate: Installed on 2019-11-20 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-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.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

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

[Touch-packages] [Bug 1685754] Re: gnome-terminal unduly forces umask=0022

2019-12-18 Thread Bug Watch Updater
Launchpad has imported 57 comments from the remote bug at
https://bugzilla.gnome.org/show_bug.cgi?id=780622.

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 2017-03-27T21:38:07+00:00 Reuben Thomas wrote:

I set my umask in my .profile to 0027.

When I run most applications in my GNOME session, e.g. Emacs, or another
terminal, such as xterm, the umask within is 0027.

When I run gnome-terminal (3.18.3, Ubuntu 16.04), my umask is 0002.

As far as I can tell, I am starting gnome-terminal and xterm (also tried
uxterm) in the same way. Both are configured not to start a login shell.

If I run "umask" at the top of my .bashrc, in gnome-terminal it prints
0002, and in xterm, 0027.

If I run xterm from within gnome-terminal, the umask remains 0002.

Running gnome-terminal.real directly has the same effect.

I tried killing gnome-terminal-server and running gnome-terminal: same
result.

If I set the umask in my .bashrc, then the setting is respected.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
terminal/+bug/1685754/comments/0


On 2017-03-27T21:50:36+00:00 Chpe wrote:

(In reply to Reuben Thomas from comment #0)
> I set my umask in my .profile to 0027.
[...]
> Both are configured not to start a login shell.

There's the solution: .profile is only sourced for login shells (at
least on debian derived distributions).

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
terminal/+bug/1685754/comments/1


On 2017-03-28T00:59:08+00:00 Reuben Thomas wrote:

Thanks for your reply. I am sorry, I tried very hard to be clear, but
obviously failed.

.profile is run at login, and sets various environment variables. These
are all correctly set in gnome-terminal and xterm.

As I said previously, neither gnome-terminal nor xterm is configured to
start a login shell. Yet in xterm both the environment variables (which
are only set in .profile) and umask are correctly set, whereas in gnome-
terminal only the environment variables are set correctly, and the umask
has been changed to a different value.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
terminal/+bug/1685754/comments/2


On 2017-03-28T01:08:04+00:00 Reuben Thomas wrote:

Just to confirm: /etc/gdm/Xsession on my Ubuntu system contains the
lines:

# First read /etc/profile and .profile
for file in /etc/profile "$HOME/.profile"; do
  if [ -f "$file" ]; then
source_with_error_check "$file"
  fi
done

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
terminal/+bug/1685754/comments/3


On 2017-03-28T08:54:37+00:00 Reuben Thomas wrote:

Some additional information, for the sake of clarity: umask(2) says:

A child process created via fork(2) inherits its parent's umask.  The
umask is left unchanged by execve(2).

I am assuming therefore that my umask having been set, by my .profile,
by /etc/gdm/Xsession, that the same process will (eventually) start
gnome-terminal-server (via gnome-terminal), and that therefore the umask
I set should be inherited (as occurs with xterm).

This is why I believe that something has changed the umask.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
terminal/+bug/1685754/comments/4


On 2017-03-28T09:01:19+00:00 Egmont Koblinger wrote:

Neither vte's nor gnome-terminal's code has any umask() calls.

If I start gnome-terminal (no previous instance running) from my xterm
with a weird one-off umask manually set in that xterm, my umask gets
reset to my preferred value in g-t. If I start the server manually and
then a client(*) then that weird umask is preserved.

(*)The two commands shown at
https://wiki.gnome.org/Apps/Terminal/Debugging, without the gdb bits.

So it must have something to do with the dbus activation, it's probably
dbus (or a closely related component) that decides on the umask.

(Remotely reminds me of
https://bugs.launchpad.net/terminator/+bug/1646034.)

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
terminal/+bug/1685754/comments/5


On 2017-03-28T09:09:07+00:00 Egmont Koblinger wrote:

Just for the record: Could you please check the umask of your gnome-
terminal-server process?

grep Umask /proc/$(pidof gnome-terminal-server)/status

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
terminal/+bug/1685754/comments/6


[Touch-packages] [Bug 1746128] Re: package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', which is also in packa

2019-12-18 Thread Rik Mills
libdbusmenu-qt (0.9.3+16.04.20160218-1ubuntu1) bionic; urgency=medium

  * Breaks/Replaces on libdbusmenu-qt5 for libdbusmenu-qt5-2.
libdbusmenu-qt5 exists in Ubuntu archive, but not debian history.
Can be dropped after 18.04.

** Changed in: libdbusmenu-qt (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  package libdbusmenu-qt5-2 (not installed) failed to install/upgrade:
  trying to overwrite '/usr/lib/x86_64-linux-gnu/libdbusmenu-
  qt5.so.2.6.0', which is also in package libdbusmenu-qt5:amd64
  0.9.3+16.04.20160218-0ubuntu1

Status in libdbusmenu-qt package in Ubuntu:
  Fix Released

Bug description:
  i don't know to be specific

  ProblemType: Package
  DistroRelease: Kali 2018.1
  Package: libdbusmenu-qt5-2 (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Jan 29 21:00:43 2018
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', which is also in package 
libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1
  InstallationDate: Installed on 2018-01-26 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.19.0.5kali1
   apt  1.6~alpha7
  SourcePackage: libdbusmenu-qt
  Title: package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', which 
is also in package libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1746128/+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 1855782] Re: Typo in the documentation: "systen" -> "system"

2019-12-18 Thread Bug Watch Updater
Launchpad has imported 2 comments from the remote bug at
https://bugzilla.gnome.org/show_bug.cgi?id=786829.

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 2017-08-26T09:33:18+00:00 Laurent Bigonville wrote:

Hello,

There is apparently a typo in the dconf.7 manpage, the whatis entry
shows "A configuration systen"

should be "system"

The typo is in:
https://git.gnome.org/browse/dconf/tree/docs/dconf-overview.xml#n29

Original bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868233

Reply at:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1855782/comments/0


On 2017-08-29T01:19:51+00:00 Piotr Drąg wrote:

Thank you!

https://git.gnome.org/browse/dconf/commit/?id=9ac8f161962c8e2eeab2847caa036064d21e807f

Reply at:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1855782/comments/1


** Changed in: dconf
   Status: Unknown => Fix Released

** Changed in: dconf
   Importance: Unknown => Medium

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

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

Title:
  Typo in the documentation: "systen" -> "system"

Status in dconf:
  Fix Released
Status in d-conf package in Ubuntu:
  Confirmed

Bug description:
  Found on 14.04, 16.04, and 18.04. 19.04 and later distributions have
  it fixed.

  The "NAME" section of dconf7
  manpage(http://manpages.ubuntu.com/manpages/bionic/man7/dconf.7.html)
  says "dconf - A configuration systen".

  "systen" should be a typo for "system".

To manage notifications about this bug go to:
https://bugs.launchpad.net/dconf/+bug/1855782/+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 1746128] Re: package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', which is also in packa

2019-12-18 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: libdbusmenu-qt (Ubuntu)
   Status: New => Confirmed

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

Title:
  package libdbusmenu-qt5-2 (not installed) failed to install/upgrade:
  trying to overwrite '/usr/lib/x86_64-linux-gnu/libdbusmenu-
  qt5.so.2.6.0', which is also in package libdbusmenu-qt5:amd64
  0.9.3+16.04.20160218-0ubuntu1

Status in libdbusmenu-qt package in Ubuntu:
  Confirmed

Bug description:
  i don't know to be specific

  ProblemType: Package
  DistroRelease: Kali 2018.1
  Package: libdbusmenu-qt5-2 (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Jan 29 21:00:43 2018
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', which is also in package 
libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1
  InstallationDate: Installed on 2018-01-26 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.19.0.5kali1
   apt  1.6~alpha7
  SourcePackage: libdbusmenu-qt
  Title: package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', which 
is also in package libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1746128/+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 1669931] Re: apport not opening browser

2019-12-18 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/1669931

Title:
  apport not opening browser

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.04.5 LTS with apport 2.14.1-0ubuntu3.23.

  After a system crash, apport launches and presents me with the "Send
  problem report?" window
  
(https://help.ubuntu.com/community/ReportingBugs?action=AttachFile=get
  =apport-problem-report.png).  I click to send the report but nothing
  happens after that... not even the next dialog
  
(https://help.ubuntu.com/community/ReportingBugs?action=AttachFile=get
  =information-upload.png) opens up, and launchpad isn't opened so i can
  report the bug.

  Expected: New browser tab is opened to login to launchpad and report
  the bug.

  Perhaps related to Bug #1486639 and Bug #1630720

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1669931/+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 1080978] Re: apport forcefully overrides sysctl kernel.core_pattern from values set in /etc/sysctl.*

2019-12-18 Thread Zertrin
Same surprise here, after adding a custom
'/etc/sysctl.d/60-core_pattern.conf' to set it to my desired value, I
could not understand why it seemed not applied after a reboot. Finally
discovered the echoing inside '/etc/init/apport.conf' and died a little
internally.

The proper course of action for apport would probably be to create its
own '/etc/sysctl.d/30-core_pattern.conf' ("30" being documented as to be
used by packages), instead of hijacking '/proc/sys/kernel/core_pattern'
...

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

Title:
  apport forcefully overrides sysctl kernel.core_pattern from values set
  in /etc/sysctl.*

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I think that the way apport registers itself as a core dump handler
  with the system is badly behaved with respect to other configuration
  processes one would expect to follow on a Debian or Ubuntu based
  system. It forcibly overrides settings specified by a user in
  /etc/sysctl.conf, and does not employ /etc/sysctl.d. Thus it is
  overriding settings that have been configured elsewhere upon start and
  upon shutdown.

  I think perhaps it should be checking for non-default values in these
  settings and not dynamically playing with them while it starts and
  stops.

  Thanks,
  Matthew.

  mhall@mhsm:src$ sudo fgrep kernel.core /etc/sysctl.conf
  kernel.core_pattern = /var/crash/core.%e.%u.%t
  kernel.core_uses_pid = 1
  mhall@mhsm:src$ 

  $ sudo sysctl -a | fgrep -i kernel.core
  kernel.core_uses_pid = 1
  kernel.core_pattern = |/usr/share/apport/apport %p %s %c
  kernel.core_pipe_limit = 0

  $ cat /etc/init/apport.conf 
  ... SNIP ...
  pre-start script
  ... SNIP ...
  echo "|/usr/share/apport/apport %p %s %c" > /proc/sys/kernel/core_pattern
  ... SNIP ...
  post-stop script
  ... SNIP ...
  if [ "`dd if=/proc/sys/kernel/core_pattern count=1 bs=1 2>/dev/null`" != 
"|" ]
  then
exit 1
  else
echo "core" > /proc/sys/kernel/core_pattern
  fi
  end script

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1080978/+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 1856884] Re: not proper sound device

2019-12-18 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1856884

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

** Tags added: eoan

** 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/1856884

Title:
  not proper sound device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  when i insert or take out my headphones , the system doesn't send
  signal on my headphones, i need to switch by hand. it worked in ubuntu
  18.10 correct.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884/+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 1856908] Re: [80SY, Realtek ALC236, Speaker, Internal] Playback problem

2019-12-18 Thread Daniel van Vugt
Looks like the Intel graphics kernel driver crashing.

** Summary changed:

- [80SY, Realtek ALC236, Speaker, Internal] Playback problem
+ Sometimes my Lenovo v310 freezes completely while playing music

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

Title:
  Sometimes my Lenovo v310 freezes completely while playing music

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $lsb_release -rd
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04

  $uname -a
  Linux fvg 4.15.0-73-generic #82~16.04.1-Ubuntu SMP Tue Dec 3 17:36:08 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  audacious: 3.6.2-2

  What happened:
  Sometimes my Lenovo v310 freezes completely while playing music (Audacious).
  This is something i found in syslog.

  
  Dec 19 03:01:53 localhost kernel: [12615.593931] [ cut here 
]
  Dec 19 03:01:53 localhost kernel: [12615.593947] WARN_ON(fbc->active)
  Dec 19 03:01:53 localhost kernel: [12615.594285] WARNING: CPU: 0 PID: 14771 
at 
/build/linux-hwe-BQMZOc/linux-hwe-4.15.0/drivers/gpu/drm/i915/intel_fbc.c:1136 
intel_fbc_enable+0x3ed/0x570 [i915]
  Dec 19 03:01:53 localhost kernel: [12615.594289] Modules linked in: ccm 
rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep rtsx_usb_ms memstick 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi 
kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
snd_hda_codec_realtek snd_hda_codec_generic arc4 aesni_intel aes_x86_64 
crypto_simd glue_helper cryptd snd_soc_skl intel_cstate intel_rapl_perf 
snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi 
snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep iwlmvm mac80211 snd_pcm uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_seq_midi 
snd_seq_midi_event videobuf2_core joydev snd_rawmidi input_leds videodev 
serio_raw snd_seq media wmi_bmof snd_seq_device
  Dec 19 03:01:53 localhost kernel: [12615.594456]  intel_wmi_thunderbolt 
snd_timer iwlwifi snd soundcore cfg80211 shpchp intel_pch_thermal mei_me mei 
btusb btrtl btbcm btintel bluetooth ecdh_generic mac_hid ideapad_laptop 
sparse_keymap acpi_pad parport_pc ppdev lp parport autofs4 hid_generic 
rtsx_usb_sdmmc usbhid hid rtsx_usb i915 i2c_algo_bit drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops psmouse r8169 drm mii ahci libahci wmi video
  Dec 19 03:01:53 localhost kernel: [12615.594572] CPU: 0 PID: 14771 Comm: 
kworker/u8:0 Tainted: G   OE4.15.0-73-generic #82~16.04.1-Ubuntu
  Dec 19 03:01:53 localhost kernel: [12615.594576] Hardware name: LENOVO 80SY/, 
BIOS 0ZCN30WW 12/08/2016
  Dec 19 03:01:53 localhost kernel: [12615.594768] Workqueue: events_unbound 
intel_atomic_commit_work [i915]
  Dec 19 03:01:53 localhost kernel: [12615.594953] RIP: 
0010:intel_fbc_enable+0x3ed/0x570 [i915]
  Dec 19 03:01:53 localhost kernel: [12615.594960] RSP: 0018:c23fc1367cb0 
EFLAGS: 00010286
  Dec 19 03:01:53 localhost kernel: [12615.594969] RAX:  RBX: 
a06e2a00 RCX: 97e63a28
  Dec 19 03:01:53 localhost kernel: [12615.594974] RDX: 0001 RSI: 
0082 RDI: 0202
  Dec 19 03:01:53 localhost kernel: [12615.594979] RBP: c23fc1367d00 R08: 
fffa734938d0 R09: 
  Dec 19 03:01:53 localhost kernel: [12615.594984] R10: c23fc30e38e8 R11: 
0367 R12: a06c56299000
  Dec 19 03:01:53 localhost kernel: [12615.594989] R13: a06d4cbd6b00 R14: 
a06c5629f000 R15: a06e2a00
  Dec 19 03:01:53 localhost kernel: [12615.594997] FS:  () 
GS:a06e3ec0() knlGS:
  Dec 19 03:01:53 localhost kernel: [12615.595003] CS:  0010 DS:  ES:  
CR0: 80050033
  Dec 19 03:01:53 localhost kernel: [12615.595008] CR2: e1ad9000 CR3: 
000210a0a001 CR4: 003626f0
  Dec 19 03:01:53 localhost kernel: [12615.595012] Call Trace:
  Dec 19 03:01:53 localhost kernel: [12615.595197]  ? 
intel_pre_plane_update+0x12f/0x190 [i915]
  Dec 19 03:01:53 localhost kernel: [12615.595371]  intel_update_crtc+0x75/0xa0 
[i915]
  Dec 19 03:01:53 localhost kernel: [12615.595526]  
skl_update_crtcs+0x1a9/0x1f0 [i915]
  Dec 19 03:01:53 localhost kernel: [12615.595663]  
intel_atomic_commit_tail+0x3c8/0xe00 [i915]
  Dec 19 03:01:53 localhost kernel: [12615.595676]  ? __switch_to+0x9b/0x4e0
  Dec 19 03:01:53 localhost kernel: [12615.595687]  ? __switch_to_asm+0x35/0x70
  Dec 19 03:01:53 localhost kernel: [12615.595819]  
intel_atomic_commit_work+0x12/0x20 [i915]
  Dec 19 03:01:53 localhost kernel: [12615.595830]  process_one_work+0x14d/0x410
  Dec 19 03:01:53 localhost kernel: [12615.595839]  worker_thread+0x4b/0x460
  Dec 19 03:01:53 

[Touch-packages] [Bug 1856880] Re: Unable to install intel from partner repositories

2019-12-18 Thread Daniel van Vugt
That's the wrong driver which is why it can't install.

xserver-xorg-video-intel is for Ubuntu 18.04 running Xorg 1.19.6. You
need xserver-xorg-video-intel-hwe-18.04 to match your Ubuntu 18.04.2
running Xorg 1.20.4.

That said, we recommend neither because the built-in modesetting driver
that comes with all versions of Xorg (and that you are already using)
will provide higher performance and greater compatibility for Intel
GPUs.

If you want better graphics performance then please try Ubuntu 19.10
instead where the most dramatic performance improvements are included in
the latest Mutter and Gnome Shell release.

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

** Changed in: ubuntu
   Status: New => Invalid

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

Title:
  Unable to install intel from partner repositories

Status in Ubuntu:
  Invalid

Bug description:
  The following packages have unmet dependencies:
   xserver-xorg-video-intel : Depends: xorg-video-abi-23
  Depends: xserver-xorg-core (>= 2:1.18.99.901)
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 18 23:14:32 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:1094]
 Subsystem: Acer Incorporated [ALI] GM108M [GeForce 940MX] [1025:1094]
  InstallationDate: Installed on 2019-12-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b571 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic 
root=UUID=b7dfb4a2-5789-441a-9384-11e4d4c2b6c4 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.51
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ironman_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.51
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.51:bd05/31/2019:svnAcer:pn:pvrV1.51:rvnAcer:rnIronman_SK:rvrV1.51:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: KBL
  dmi.product.sku: _115F_1.51
  dmi.product.version: V1.51
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  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/1856880/+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 1856884] [NEW] not proper sound device

2019-12-18 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

when i insert or take out my headphones , the system doesn't send signal
on my headphones, i need to switch by hand. it worked in ubuntu 18.10
correct.

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

-- 
not proper sound device
https://bugs.launchpad.net/bugs/1856884
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 1856872] Re: bluez regression: Bluetooth fails after resume

2019-12-18 Thread Daniel van Vugt
** Tags added: eoan

** Summary changed:

- bluez regression: Bluetooth fails after resume
+ Realtek btusb dongle vanishes after resume from suspend

** Package changed: bluez (Ubuntu) => linux (Ubuntu)

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

Title:
  Realtek btusb dongle vanishes after resume from suspend

Status in linux package in Ubuntu:
  New

Bug description:
  New laptop that is running Ubuntu Mate 19.10, most everything works
  out of the box even bluetooth but bluetooth does not resume after
  suspend.  In fact I am unable to restart it and get it to work after a
  suspend. Wireless resumes and continues to work, just bluetooth fails.
  After suspend the controller and adapter are not found, restarting
  bluetooth.service nor restarting network manger solve the issue.
  After a resume the adapter is not found at all, I have tried to remove
  the module before a suspend and add it back to no avail, the only way
  to get it working is to reboot which is a pain.

  Please let me know what additional data you may need, posting
  information below:

  Chipset is Realtek RTL8822CE, combined wireless and Bluetooth module
  Running Bluez 5.50 package...

  Working on intial Boot:

  lsusb -tv
  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
  ID 1d6b:0003 Linux Foundation 3.0 root hub
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
  ID 1d6b:0002 Linux Foundation 2.0 root hub
  |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  ID 0408:5365 Quanta Computer, Inc.
  |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
  ID 0408:5365 Quanta Computer, Inc.
  |__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
  ID 0bda:b00c Realtek Semiconductor Corp.
  |__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
  ID 0bda:b00c Realtek Semiconductor Corp.

  rfkill list
  0: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no
  1: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no

  usb-devices
  T:  Bus=01 Lev=01 Prnt=01 Port=09 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
  D:  Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=0bda ProdID=b00c Rev=00.00
  S:  Manufacturer=Realtek
  S:  Product=Bluetooth Radio
  S:  SerialNumber=00e04c01
  C:  #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA
  I:  If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  I:  If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

  lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera
  Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  dmesg | grep Blue
  [1.192743] usb 1-10: Product: Bluetooth Radio
  [   11.706607] Bluetooth: Core ver 2.22
  [   11.706620] Bluetooth: HCI device and connection manager initialized
  [   11.706624] Bluetooth: HCI socket layer initialized
  [   11.706626] Bluetooth: L2CAP socket layer initialized
  [   11.706628] Bluetooth: SCO socket layer initialized
  [   11.720229] Bluetooth: hci0: RTL: rtl: examining hci_ver=0a hci_rev=000c 
lmp_ver=0a lmp_subver=8822
  [   11.721252] Bluetooth: hci0: RTL: rom_version status=0 version=3
  [   11.721254] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_fw.bin
  [   11.722558] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_config.bin
  [   11.722879] Bluetooth: hci0: RTL: cfg_sz 6, total sz 24866
  [   15.466810] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.466812] Bluetooth: BNEP filters: protocol multicast
  [   15.466816] Bluetooth: BNEP socket layer initialized
  [   18.070246] Bluetooth: RFCOMM TTY layer initialized
  [   18.070250] Bluetooth: RFCOMM socket layer initialized
  [   18.070253] Bluetooth: RFCOMM ver 1.11

  After resume:

  lsusb -tv
  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
  ID 1d6b:0003 Linux Foundation 3.0 root hub
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
  ID 1d6b:0002 Linux Foundation 2.0 root hub
  |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  ID 0408:5365 Quanta Computer, Inc.
  |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
  ID 0408:5365 Quanta Computer, Inc.

  rfkill list
  1: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no

  usb-devices

  T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh=12
  D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0002 Rev=05.03
  S:  Manufacturer=Linux 5.3.0-24-generic xhci-hcd
  S:  Product=xHCI Host Controller
  S:  SerialNumber=:00:14.0
  C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
  I:  If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub  

[Touch-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

2019-12-18 Thread Daniel van Vugt
Tracking in:
https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f

** Description changed:

- .
+ https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
-  LANG=nb_NO.UTF-8
-  LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
+  LANG=nb_NO.UTF-8
+  LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
-  g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
-  g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
+  g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1843982/+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 1856908] [NEW] [80SY, Realtek ALC236, Speaker, Internal] Playback problem

2019-12-18 Thread Valery Frolov
Public bug reported:

$lsb_release -rd
Description:Ubuntu 16.04.6 LTS
Release:16.04

$uname -a
Linux fvg 4.15.0-73-generic #82~16.04.1-Ubuntu SMP Tue Dec 3 17:36:08 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

audacious: 3.6.2-2

What happened:
Sometimes my Lenovo v310 freezes completely while playing music (Audacious).
This is something i found in syslog.


Dec 19 03:01:53 localhost kernel: [12615.593931] [ cut here 
]
Dec 19 03:01:53 localhost kernel: [12615.593947] WARN_ON(fbc->active)
Dec 19 03:01:53 localhost kernel: [12615.594285] WARNING: CPU: 0 PID: 14771 at 
/build/linux-hwe-BQMZOc/linux-hwe-4.15.0/drivers/gpu/drm/i915/intel_fbc.c:1136 
intel_fbc_enable+0x3ed/0x570 [i915]
Dec 19 03:01:53 localhost kernel: [12615.594289] Modules linked in: ccm rfcomm 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep rtsx_usb_ms memstick intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel kvm 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
snd_hda_codec_realtek snd_hda_codec_generic arc4 aesni_intel aes_x86_64 
crypto_simd glue_helper cryptd snd_soc_skl intel_cstate intel_rapl_perf 
snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi 
snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep iwlmvm mac80211 snd_pcm uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_seq_midi 
snd_seq_midi_event videobuf2_core joydev snd_rawmidi input_leds videodev 
serio_raw snd_seq media wmi_bmof snd_seq_device
Dec 19 03:01:53 localhost kernel: [12615.594456]  intel_wmi_thunderbolt 
snd_timer iwlwifi snd soundcore cfg80211 shpchp intel_pch_thermal mei_me mei 
btusb btrtl btbcm btintel bluetooth ecdh_generic mac_hid ideapad_laptop 
sparse_keymap acpi_pad parport_pc ppdev lp parport autofs4 hid_generic 
rtsx_usb_sdmmc usbhid hid rtsx_usb i915 i2c_algo_bit drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops psmouse r8169 drm mii ahci libahci wmi video
Dec 19 03:01:53 localhost kernel: [12615.594572] CPU: 0 PID: 14771 Comm: 
kworker/u8:0 Tainted: G   OE4.15.0-73-generic #82~16.04.1-Ubuntu
Dec 19 03:01:53 localhost kernel: [12615.594576] Hardware name: LENOVO 80SY/, 
BIOS 0ZCN30WW 12/08/2016
Dec 19 03:01:53 localhost kernel: [12615.594768] Workqueue: events_unbound 
intel_atomic_commit_work [i915]
Dec 19 03:01:53 localhost kernel: [12615.594953] RIP: 
0010:intel_fbc_enable+0x3ed/0x570 [i915]
Dec 19 03:01:53 localhost kernel: [12615.594960] RSP: 0018:c23fc1367cb0 
EFLAGS: 00010286
Dec 19 03:01:53 localhost kernel: [12615.594969] RAX:  RBX: 
a06e2a00 RCX: 97e63a28
Dec 19 03:01:53 localhost kernel: [12615.594974] RDX: 0001 RSI: 
0082 RDI: 0202
Dec 19 03:01:53 localhost kernel: [12615.594979] RBP: c23fc1367d00 R08: 
fffa734938d0 R09: 
Dec 19 03:01:53 localhost kernel: [12615.594984] R10: c23fc30e38e8 R11: 
0367 R12: a06c56299000
Dec 19 03:01:53 localhost kernel: [12615.594989] R13: a06d4cbd6b00 R14: 
a06c5629f000 R15: a06e2a00
Dec 19 03:01:53 localhost kernel: [12615.594997] FS:  () 
GS:a06e3ec0() knlGS:
Dec 19 03:01:53 localhost kernel: [12615.595003] CS:  0010 DS:  ES:  
CR0: 80050033
Dec 19 03:01:53 localhost kernel: [12615.595008] CR2: e1ad9000 CR3: 
000210a0a001 CR4: 003626f0
Dec 19 03:01:53 localhost kernel: [12615.595012] Call Trace:
Dec 19 03:01:53 localhost kernel: [12615.595197]  ? 
intel_pre_plane_update+0x12f/0x190 [i915]
Dec 19 03:01:53 localhost kernel: [12615.595371]  intel_update_crtc+0x75/0xa0 
[i915]
Dec 19 03:01:53 localhost kernel: [12615.595526]  skl_update_crtcs+0x1a9/0x1f0 
[i915]
Dec 19 03:01:53 localhost kernel: [12615.595663]  
intel_atomic_commit_tail+0x3c8/0xe00 [i915]
Dec 19 03:01:53 localhost kernel: [12615.595676]  ? __switch_to+0x9b/0x4e0
Dec 19 03:01:53 localhost kernel: [12615.595687]  ? __switch_to_asm+0x35/0x70
Dec 19 03:01:53 localhost kernel: [12615.595819]  
intel_atomic_commit_work+0x12/0x20 [i915]
Dec 19 03:01:53 localhost kernel: [12615.595830]  process_one_work+0x14d/0x410
Dec 19 03:01:53 localhost kernel: [12615.595839]  worker_thread+0x4b/0x460
Dec 19 03:01:53 localhost kernel: [12615.595853]  kthread+0x105/0x140
Dec 19 03:01:53 localhost kernel: [12615.595861]  ? process_one_work+0x410/0x410
Dec 19 03:01:53 localhost kernel: [12615.595867]  ? kthread_bind+0x40/0x40
Dec 19 03:01:53 localhost kernel: [12615.595878]  ret_from_fork+0x35/0x40
Dec 19 03:01:53 localhost kernel: [12615.595885] Code: 4a 03 00 00 00 0f 84 55 
01 00 00 80 bb ca 2c 00 00 00 0f 84 1c ff ff ff 48 c7 c6 5e 54 5e c0 48 c7 c7 
44 54 5e c0 e8 a3 f0 52 d6 <0f> 0b e9 02 ff ff ff 3d 00 08 00 00 ba 00 08 00 00 
0f 4f c2 e9 
Dec 19 03:01:53 localhost kernel: [12615.596031] ---[ end trace 
4627cd6bd9d494bf ]---

ProblemType: Bug

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2019-12-18 Thread James Smith
Adding the needed domain to the /etc/NetworkManager/system-connections
as an argument to :

dns-search= see

Works for me.

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

Title:
  dnsmasq sometimes fails to resolve private names in networks with non-
  equivalent nameservers

Status in dnsmasq package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Precise:
  Triaged
Status in network-manager source package in Precise:
  Invalid
Status in dnsmasq package in Debian:
  New

Bug description:
  A number of reports already filed against network-manager seem to
  reflect this problem, but to make things very clear I am opening a new
  report.  Where appropriate I will mark other reports as duplicates of
  this one.

  Consider a pre-Precise system with the following /etc/resolv.conf:

  nameserver 192.168.0.1
  nameserver 8.8.8.8

  The first address is the address of a nameserver on the LAN that can
  resolve both private and public domain names.  The second address is
  the address of a nameserver on the Internet that can resolve only
  public names.

  This setup works fine because the GNU resolver always tries the first-
  listed address first.

  Now the administrator upgrades to Precise and instead of writing the
  above to resolv.conf, NetworkManager writes

  server=192.168.0.1
  server=8.8.8.8

  to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to
  resolv.conf.  Resolution of private domain names is now broken because
  dnsmasq treats the two upstream nameservers as equals and uses the
  faster one, which could be 8.8.8.8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+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 1856871] Re: i/o error if next unused loop device is queried

2019-12-18 Thread Eric Desrochers
# parted code (3.3-1) from focal

-
libparted/arch/linux.c:
.
=>  if (fsync (fd) < 0 || close (fd) < 0)
if (ped_exception_throw (
PED_EXCEPTION_WARNING,
PED_EXCEPTION_RETRY +
PED_EXCEPTION_IGNORE,
=>  _("Error fsyncing/closing %s: 
%s"),
name, strerror (errno))
== PED_EXCEPTION_RETRY)
goto retry;
}
}
free (name);


# FSYNC(2)
RETURN VALUE
   On success, these system calls return zero.  On error, -1 is returned, 
and errno is set appropriately.
-

so definitely fsync() fails returning "-1" on the next unused loop
device as oppose to any other unused loop device.

The question is why unused loop device fails on fsync() ONLY when it is
the next unused loop device after a system boot (losetup -f) ?

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

Title:
  i/o error if next unused loop device is queried

Status in snapd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New

Bug description:
  This is reproducible in Bionic and late.

  Here's an example running 'focal':

  $ lsb_release -cs
  focal

  $ uname -r
  5.3.0-24-generic

  The error is:
  blk_update_request: I/O error, dev loop2, sector 0

  and on more recent kernel:

  kernel: [18135.185709] blk_update_request: I/O error, dev loop18,
  sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0

  
  How to trigger it:
  $ sosreport -o block

  or more precisely the cmd causing the situation inside the block plugin:
  $ parted -s $(losetup -f) unit s print

  https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52

  but if I run it on the next next unused loop device, in this case
  /dev/loop3 (which is also unused), no errors.

  While I agree that sosreport shouldn't query unused loop devices,
  there is definitely something going on with the next unused loop
  device.

  What is differentiate loop2 and loop3 and any other unused ones ?

  3 things so far I have noticed:
  * loop2 is the next unused loop device (losetup -f)
  * A reboot is needed (if some loop modification (snap install, mount loop, 
...) has been made at runtime
  * I have also noticed that loop2 (or whatever the next unused one is) have 
some stat as oppose to other unused loop devices. The stat exist already right 
after the system boot for the next unused loop device.

  /sys/block/loop2/stat
  ::
  2 0 10 0 1 0 0 0 0 0 0

  2  = number of read I/Os processed
  10 = number of sectors read
  1  = number of write I/Os processed

  Explanation of each column:
  https://www.kernel.org/doc/html/latest/block/stat.html

  while /dev/loop3 doesn't

  /sys/block/loop3/stat
  ::
  0 0 0 0 0 0 0 0 0 0 0

  Which tells me that something during the boot process most likely
  acquired (on purpose or not) the next unused loop and possibly didn't
  released it well enough.

  If loop2 is generating errors, and I install a snap, the snap squashfs
  will take loop2, making loop3 the next unused loop device.

  If I query loop3 with 'parted' right after, no errors.

  If I reboot, and query loop3 again, then no I'll have an error.

  To triggers the errors it need to be after a reboot and it only impact
  the first unused loop device available (losetup -f).

  This was tested with focal/systemd whic his very close to latest
  upstream code.

  This has been test with latest v5.5 mainline kernel as well.

  For now, I don't think it's a kernel problem, I'm more thinking of a
  userspace misbehaviour dealing with loop device (or block device) at
  boot.

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

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


[Touch-packages] [Bug 1845529] Re: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/`

2019-12-18 Thread Brian Murray
Hello Norbert, or anyone else affected,

Accepted util-linux into eoan-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/util-
linux/2.34-0.1ubuntu2.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: util-linux (Ubuntu Eoan)
   Status: New => Fix Committed

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

Title:
  bash completion shows `awk: line 18: function gensub never defined` on
  `umount /dev/`

Status in bash-completion package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in util-linux package in Ubuntu:
  Fix Released
Status in bash-completion source package in Eoan:
  Invalid
Status in gawk source package in Eoan:
  New
Status in mawk source package in Eoan:
  New
Status in ubuntu-meta source package in Eoan:
  New
Status in util-linux source package in Eoan:
  Fix Committed
Status in bash-completion source package in Focal:
  Invalid
Status in gawk source package in Focal:
  Invalid
Status in mawk source package in Focal:
  Invalid
Status in ubuntu-meta source package in Focal:
  Invalid
Status in util-linux source package in Focal:
  Fix Released
Status in Debian:
  Confirmed

Bug description:
  [Impact]
  Any user attempting to tab-complete from "umount /dev/" when running the bash 
shell.

  [Test cases]
  Steps to reproduce:
  1. Install Ubuntu MATE 19.10 using minimal desktop option
  2. Open terminal and enter `umount /dev/s` and then hit 

  Expected result:
  * bash completion works as expected

  Actual results:
  * bash completion does not work :

  $ umount /dev/awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined

  $ umount /meawk: line 18: function gensub never defined
  awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined

  
  [Regression potential]
  Since it is limited to a single file 
(/usr/share/bash-completion/completions/umount) and affects only it, as well as 
given that it currently does not work, I estimate this as a low risk change. 
Things to look out for as a regression would be if another previously-working 
completion would fail to work (ie. what if mount stops completing correctly, 
and works again if the fix is backed out?).

  ---

  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bash-completion 1:2.9-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Sep 26 18:46:59 2019
  Dependencies:

  InstallationDate: Installed on 2019-09-26 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  PackageArchitecture: all
  SourcePackage: bash-completion
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1845529/+subscriptions

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


[Touch-packages] [Bug 1856871] Re: i/o error if next unused loop device is queried

2019-12-18 Thread Eric Desrochers
losetup -l
NAME   SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE 
DIO LOG-SEC
/dev/loop1 0  0 1  1 /var/lib/snapd/snaps/core_7270.snap
 0 512
/dev/loop2 0  0 1  1 /var/lib/snapd/snaps/core_8268.snap
 0 512
/dev/loop0 0  0 1  1 /var/lib/snapd/snaps/firefox_287.snap  
 0 512


# losetup -f
/dev/loop3

# strace parted -s $(losetup -f) unit s print
ioctl(3, BLKSSZGET, [512])  = 0
fadvise64(3, 0, 0, POSIX_FADV_RANDOM)   = 0
fstat(3, {st_mode=S_IFBLK|0660, st_rdev=makedev(7, 3), ...}) = 0
ioctl(3, BLKGETSIZE64, [0]) = 0
openat(AT_FDCWD, "/sys/dev/block/7:3", O_RDONLY|O_CLOEXEC) = 4
openat(4, "dm/uuid", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
close(4)= 0
ioctl(3, BLKALIGNOFF, [0])  = 0
ioctl(3, BLKIOMIN, [512])   = 0
ioctl(3, BLKIOOPT, [0]) = 0
ioctl(3, BLKPBSZGET, [512]) = 0
ioctl(3, BLKSSZGET, [512])  = 0
ioctl(3, BLKGETSIZE64, [0]) = 0
ioctl(3, BLKGETSIZE64, [0]) = 0
fsync(3)= -1 EIO (Input/output error)
openat(AT_FDCWD, "/usr/share/locale/en_US.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) 
= -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en_US.utf8/LC_MESSAGES/libc.mo", O_RDONLY) 
= -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 
ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = 
-1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = 
-1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 
ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en_US.UTF-8/LC_MESSAGES/libc.mo", 
O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en_US.utf8/LC_MESSAGES/libc.mo", 
O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en_US/LC_MESSAGES/libc.mo", 
O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en.UTF-8/LC_MESSAGES/libc.mo", 
O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en.utf8/LC_MESSAGES/libc.mo", 
O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en/LC_MESSAGES/libc.mo", O_RDONLY) 
= -1 ENOENT (No such file or directory)
write(2, "Warning", 7Warning)  = 7
write(2, ": ", 2: )   = 2
write(2, "Error fsyncing/closing /dev/loop"..., 53Error fsyncing/closing 
/dev/loop3: Input/output error) = 53
write(2, "\n", 1
)   = 1
close(1)= 0
close(2)= 0
exit_group(1)   = ?
+++ exited with 1 +++


# strace parted -s /dev/loop5 unit s print

ioctl(3, BLKSSZGET, [512])  = 0
fadvise64(3, 0, 0, POSIX_FADV_RANDOM)   = 0
fstat(3, {st_mode=S_IFBLK|0660, st_rdev=makedev(7, 5), ...}) = 0
ioctl(3, BLKGETSIZE64, [0]) = 0
openat(AT_FDCWD, "/sys/dev/block/7:5", O_RDONLY|O_CLOEXEC) = 4
openat(4, "dm/uuid", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
close(4)= 0
ioctl(3, BLKALIGNOFF, [0])  = 0
ioctl(3, BLKIOMIN, [512])   = 0
ioctl(3, BLKIOOPT, [0]) = 0
ioctl(3, BLKPBSZGET, [512]) = 0
ioctl(3, BLKSSZGET, [512])  = 0
ioctl(3, BLKGETSIZE64, [0]) = 0
ioctl(3, BLKGETSIZE64, [0]) = 0
fsync(3)= 0
close(3)= 0
close(1)= 0
close(2)= 0
exit_group(1)   = ?
+++ exited with 1 +++

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

Title:
  i/o error if next unused loop device is queried

Status in snapd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New

Bug description:
  This is reproducible in Bionic and late.

  Here's an example running 'focal':

  $ lsb_release -cs
  focal

  $ uname -r
  5.3.0-24-generic

  The error is:
  blk_update_request: I/O error, dev loop2, sector 0

  and on more recent kernel:

  kernel: [18135.185709] blk_update_request: I/O error, dev loop18,
  sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0

  
  How to trigger it:
  $ sosreport -o block

  or more precisely the cmd causing the situation inside the block plugin:
  $ parted -s $(losetup -f) unit s print

  

[Touch-packages] [Bug 1856871] Re: i/o error if next unused loop device is queried

2019-12-18 Thread Eric Desrochers
Talking with mvo (snap team) on the subject trying to eliminate some
components:

[09:48:27]  so snapd does not do anything "special" with block devices 
beside using them
[09:48:39]  it uses the standard system mount units to do that
[09:49:01]  so if you see strange things with extra block devices, I'm 
inclined to point my finger at systemd :/

** Also affects: snapd (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/1856871

Title:
  i/o error if next unused loop device is queried

Status in snapd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New

Bug description:
  This is reproducible in Bionic and late.

  Here's an example running 'focal':

  $ lsb_release -cs
  focal

  $ uname -r
  5.3.0-24-generic

  The error is:
  blk_update_request: I/O error, dev loop2, sector 0

  and on more recent kernel:

  kernel: [18135.185709] blk_update_request: I/O error, dev loop18,
  sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0

  
  How to trigger it:
  $ sosreport -o block

  or more precisely the cmd causing the situation inside the block plugin:
  $ parted -s $(losetup -f) unit s print

  https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52

  but if I run it on the next next unused loop device, in this case
  /dev/loop3 (which is also unused), no errors.

  While I agree that sosreport shouldn't query unused loop devices,
  there is definitely something going on with the next unused loop
  device.

  What is differentiate loop2 and loop3 and any other unused ones ?

  3 things so far I have noticed:
  * loop2 is the next unused loop device (losetup -f)
  * A reboot is needed (if some loop modification (snap install, mount loop, 
...) has been made at runtime
  * I have also noticed that loop2 (or whatever the next unused one is) have 
some stat as oppose to other unused loop devices. The stat exist already right 
after the system boot for the next unused loop device.

  /sys/block/loop2/stat
  ::
  2 0 10 0 1 0 0 0 0 0 0

  2  = number of read I/Os processed
  10 = number of sectors read
  1  = number of write I/Os processed

  Explanation of each column:
  https://www.kernel.org/doc/html/latest/block/stat.html

  while /dev/loop3 doesn't

  /sys/block/loop3/stat
  ::
  0 0 0 0 0 0 0 0 0 0 0

  Which tells me that something during the boot process most likely
  acquired (on purpose or not) the next unused loop and possibly didn't
  released it well enough.

  If loop2 is generating errors, and I install a snap, the snap squashfs
  will take loop2, making loop3 the next unused loop device.

  If I query loop3 with 'parted' right after, no errors.

  If I reboot, and query loop3 again, then no I'll have an error.

  To triggers the errors it need to be after a reboot and it only impact
  the first unused loop device available (losetup -f).

  This was tested with focal/systemd whic his very close to latest
  upstream code.

  This has been test with latest v5.5 mainline kernel as well.

  For now, I don't think it's a kernel problem, I'm more thinking of a
  userspace misbehaviour dealing with loop device (or block device) at
  boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1856871/+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 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset

2019-12-18 Thread Johnny Ooi
More details that might help debugging.  Found this in the syslog:

Dec 18 18:58:21 johnny-W35xSS-370SS systemd[1]: systemd-rfkill.service: 
Succeeded.
Dec 18 18:58:24 johnny-W35xSS-370SS kernel: [  336.791201] input: 
00:20:5B:12:1F:B6 as /devices/virtual/input/input34
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) 
config/udev: Adding input device 00:20:5B:12:1F:B6 (/dev/input/event20)
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) 
00:20:5B:12:1F:B6: Applying InputClass "libinput keyboard catchall"
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) 
Using input driver 'libinput' for '00:20:5B:12:1F:B6'
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) 
systemd-logind: got fd for /dev/input/event20 13:84 fd 70 paused 0
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) 
00:20:5B:12:1F:B6: always reports core events
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) 
Option "Device" "/dev/input/event20"
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) 
Option "_source" "server/udev"
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) 
event20 - 00:20:5B:12:1F:B6: is tagged by udev as: Keyboard
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) 
event20 - 00:20:5B:12:1F:B6: device is a keyboard
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) 
event20 - 00:20:5B:12:1F:B6: device removed
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) 
Option "config_info" "udev:/sys/devices/virtual/input/input34/event20"
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) 
XINPUT: Adding extended input device "00:20:5B:12:1F:B6" (type: KEYBOARD, id 18)
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) 
Option "xkb_model" "pc105"
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) 
Option "xkb_layout" "gb"
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) 
Option "xkb_variant" "extd"
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (WW) 
Option "xkb_options" requires a string value
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) 
event20 - 00:20:5B:12:1F:B6: is tagged by udev as: Keyboard
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) 
event20 - 00:20:5B:12:1F:B6: device is a keyboard
Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window 
manager warning: Overwriting existing binding of keysym 35 with keysym 35 
(keycode e).
Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window 
manager warning: Overwriting existing binding of keysym 36 with keysym 36 
(keycode f).
Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window 
manager warning: Overwriting existing binding of keysym 39 with keysym 39 
(keycode 12).
Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window 
manager warning: Overwriting existing binding of keysym 34 with keysym 34 
(keycode d).
Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window 
manager warning: Overwriting existing binding of keysym 37 with keysym 37 
(keycode 10).
Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window 
manager warning: Overwriting existing binding of keysym 33 with keysym 33 
(keycode c).
Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window 
manager warning: Overwriting existing binding of keysym 31 with keysym 31 
(keycode a).
Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window 
manager warning: Overwriting existing binding of keysym 38 with keysym 38 
(keycode 11).
Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window 
manager warning: Overwriting existing binding of keysym 32 with keysym 32 
(keycode b).
Dec 18 18:58:29 johnny-W35xSS-370SS bluetoothd[1134]: 
/org/bluez/hci0/dev_00_20_5B_12_1F_B6/fd7: fd(37) ready
Dec 18 18:58:29 johnny-W35xSS-370SS rtkit-daemon[1517]: Supervising 3 threads 
of 1 processes of 1 users.
Dec 18 18:58:29 johnny-W35xSS-370SS rtkit-daemon[1517]: Successfully made 
thread 6460 of process 2154 owned by '1000' RT at priority 5.
Dec 18 18:58:29 johnny-W35xSS-370SS rtkit-daemon[1517]: Supervising 4 threads 
of 1 processes of 1 users.

-- At this point the headset is connected. After a few seconds,
bluetooth then restarts:

Dec 18 18:58:40 johnny-W35xSS-370SS kernel: [  353.504506] usb 3-7: Failed to 
suspend device, error -71
Dec 18 18:58:40 johnny-W35xSS-370SS kernel: [  353.504570] usb 3-7: USB 
disconnect, device number 12
Dec 18 18:58:40 johnny-W35xSS-370SS acpid: input device has been disconnected, 
fd 24
Dec 18 18:58:40 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) 
config/udev: removing device 

[Touch-packages] [Bug 1856871] Re: i/o error if next unused loop device is queried

2019-12-18 Thread Eric Desrochers
Interesting fact,

If I modified "snapd.service" to prevent snapd to run and reboot. I
don't get the problem with the first unused loop device which is
/dev/loop0 since nothing is using a loop device.

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

Title:
  i/o error if next unused loop device is queried

Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New

Bug description:
  This is reproducible in Bionic and late.

  Here's an example running 'focal':

  $ lsb_release -cs
  focal

  $ uname -r
  5.3.0-24-generic

  The error is:
  blk_update_request: I/O error, dev loop2, sector 0

  and on more recent kernel:

  kernel: [18135.185709] blk_update_request: I/O error, dev loop18,
  sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0

  
  How to trigger it:
  $ sosreport -o block

  or more precisely the cmd causing the situation inside the block plugin:
  $ parted -s $(losetup -f) unit s print

  https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52

  but if I run it on the next next unused loop device, in this case
  /dev/loop3 (which is also unused), no errors.

  While I agree that sosreport shouldn't query unused loop devices,
  there is definitely something going on with the next unused loop
  device.

  What is differentiate loop2 and loop3 and any other unused ones ?

  3 things so far I have noticed:
  * loop2 is the next unused loop device (losetup -f)
  * A reboot is needed (if some loop modification (snap install, mount loop, 
...) has been made at runtime
  * I have also noticed that loop2 (or whatever the next unused one is) have 
some stat as oppose to other unused loop devices. The stat exist already right 
after the system boot for the next unused loop device.

  /sys/block/loop2/stat
  ::
  2 0 10 0 1 0 0 0 0 0 0

  2  = number of read I/Os processed
  10 = number of sectors read
  1  = number of write I/Os processed

  Explanation of each column:
  https://www.kernel.org/doc/html/latest/block/stat.html

  while /dev/loop3 doesn't

  /sys/block/loop3/stat
  ::
  0 0 0 0 0 0 0 0 0 0 0

  Which tells me that something during the boot process most likely
  acquired (on purpose or not) the next unused loop and possibly didn't
  released it well enough.

  If loop2 is generating errors, and I install a snap, the snap squashfs
  will take loop2, making loop3 the next unused loop device.

  If I query loop3 with 'parted' right after, no errors.

  If I reboot, and query loop3 again, then no I'll have an error.

  To triggers the errors it need to be after a reboot and it only impact
  the first unused loop device available (losetup -f).

  This was tested with focal/systemd whic his very close to latest
  upstream code.

  This has been test with latest v5.5 mainline kernel as well.

  For now, I don't think it's a kernel problem, I'm more thinking of a
  userspace misbehaviour dealing with loop device (or block device) at
  boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1856871/+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 1856871] Re: i/o error if next unused loop device is queried

2019-12-18 Thread Eric Desrochers
** Description changed:

  This is reproducible in Bionic and late.
  
  Here's an example running 'focal':
  
  $ lsb_release -cs
  focal
  
  $ uname -r
  5.3.0-24-generic
  
  The error is:
  blk_update_request: I/O error, dev loop2, sector 0
+ 
+ and on more recent kernel:
+ 
+ kernel: [18135.185709] blk_update_request: I/O error, dev loop18, sector
+ 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
+ 
  
  How to trigger it:
  $ sosreport -o block
  
  or more precisely the cmd causing the situation inside the block plugin:
  $ parted -s $(losetup -f) unit s print
  
  https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52
  
  but if I run it on the next next unused loop device, in this case
  /dev/loop3 (which is also unused), no errors.
  
  While I agree that sosreport shouldn't query unused loop devices, there
  is definitely something going on with the next unused loop device.
  
  What is differentiate loop2 and loop3 and any other unused ones ?
  
  3 things so far I have noticed:
  * loop2 is the next unused loop device (losetup -f)
  * A reboot is needed (if some loop modification (snap install, mount loop, 
...) has been made at runtime
  * I have also noticed that loop2 (or whatever the next unused one is) have 
some stat as oppose to other unused loop devices. The stat exist already right 
after the system boot for the next unused loop device.
  
  /sys/block/loop2/stat
  ::
  2 0 10 0 1 0 0 0 0 0 0
  
  2  = number of read I/Os processed
  10 = number of sectors read
  1  = number of write I/Os processed
  
  Explanation of each column:
  https://www.kernel.org/doc/html/latest/block/stat.html
  
  while /dev/loop3 doesn't
  
  /sys/block/loop3/stat
  ::
  0 0 0 0 0 0 0 0 0 0 0
  
  Which tells me that something during the boot process most likely
  acquired (on purpose or not) the next unused loop and possibly didn't
  released it well enough.
  
  If loop2 is generating errors, and I install a snap, the snap squashfs
  will take loop2, making loop3 the next unused loop device.
  
  If I query loop3 with 'parted' right after, no errors.
  
  If I reboot, and query loop3 again, then no I'll have an error.
  
  To triggers the errors it need to be after a reboot and it only impact
  the first unused loop device available (losetup -f).
  
  This was tested with focal/systemd whic his very close to latest
  upstream code.
  
  This has been test with latest v5.5 mainline kernel as well.
  
  For now, I don't think it's a kernel problem, I'm more thinking of a
  userspace misbehaviour dealing with loop device (or block device) at
  boot.

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

Title:
  i/o error if next unused loop device is queried

Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New

Bug description:
  This is reproducible in Bionic and late.

  Here's an example running 'focal':

  $ lsb_release -cs
  focal

  $ uname -r
  5.3.0-24-generic

  The error is:
  blk_update_request: I/O error, dev loop2, sector 0

  and on more recent kernel:

  kernel: [18135.185709] blk_update_request: I/O error, dev loop18,
  sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0

  
  How to trigger it:
  $ sosreport -o block

  or more precisely the cmd causing the situation inside the block plugin:
  $ parted -s $(losetup -f) unit s print

  https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52

  but if I run it on the next next unused loop device, in this case
  /dev/loop3 (which is also unused), no errors.

  While I agree that sosreport shouldn't query unused loop devices,
  there is definitely something going on with the next unused loop
  device.

  What is differentiate loop2 and loop3 and any other unused ones ?

  3 things so far I have noticed:
  * loop2 is the next unused loop device (losetup -f)
  * A reboot is needed (if some loop modification (snap install, mount loop, 
...) has been made at runtime
  * I have also noticed that loop2 (or whatever the next unused one is) have 
some stat as oppose to other unused loop devices. The stat exist already right 
after the system boot for the next unused loop device.

  /sys/block/loop2/stat
  ::
  2 0 10 0 1 0 0 0 0 0 0

  2  = number of read I/Os processed
  10 = number of sectors read
  1  = number of write I/Os processed

  Explanation of each column:
  https://www.kernel.org/doc/html/latest/block/stat.html

  while /dev/loop3 doesn't

  /sys/block/loop3/stat
  ::
  0 0 0 0 0 0 0 0 0 0 0

  Which tells me that something during the boot process most likely
  acquired (on purpose or not) the next unused loop and possibly didn't
  released it well enough.

  If loop2 is generating errors, and I install a snap, the snap squashfs
  will take loop2, making loop3 the next unused loop device.

  If 

[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

2019-12-18 Thread naisanza
Same problem with Ubuntu 19.04 on Dell XPS 13 2-in-1 (2019)

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in pm-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1574120/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

2019-12-18 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in pm-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1574120/+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 1745984] Re: package update-notifier 3.168.7 failed to install/upgrade: problemas de dependencias - se deja sin configurar

2019-12-18 Thread Balint Reczey
Unattended-upgrades is expected to detect changed conffiles which did
not happen here for some reason.

The version of u-u this bug was observed with was 0.90ubuntu0.9 and
there were major changes since this version. The current version of
unattended-upgrades in xenial-updates is 1.1ubuntu1.18.04.7~16.04.5 and
we don't observe similar errors for some time thus I assume the issue
has been fixed.

Has anyone observed similar issue with recent unattended-upgrades
versions?

** Changed in: unattended-upgrades (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  package update-notifier 3.168.7 failed to install/upgrade: problemas
  de dependencias - se deja sin configurar

Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: update-notifier 3.168.7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Jan 29 09:32:30 2018
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2016-11-13 (442 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: update-notifier
  Title: package update-notifier 3.168.7 failed to install/upgrade: problemas 
de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.update-notifier.desktop: 2016-06-29T18:23:45

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1745984/+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 1856871] Re: i/o error if next unused loop device is queried

2019-12-18 Thread Eric Desrochers
I also filed a sosreport upstream issue, because I believe sosreport
shouldn't try to query "unused" block device such as loop device.

https://github.com/sosreport/sos/issues/1897

but situation remain that there is something going wrong with loop
device and systemd/systemd-udevd at boot as explained above.

** Bug watch added: github.com/sosreport/sos/issues #1897
   https://github.com/sosreport/sos/issues/1897

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

Title:
  i/o error if next unused loop device is queried

Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New

Bug description:
  This is reproducible in Bionic and late.

  Here's an example running 'focal':

  $ lsb_release -cs
  focal

  $ uname -r
  5.3.0-24-generic

  The error is:
  blk_update_request: I/O error, dev loop2, sector 0

  and on more recent kernel:

  kernel: [18135.185709] blk_update_request: I/O error, dev loop18,
  sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0

  
  How to trigger it:
  $ sosreport -o block

  or more precisely the cmd causing the situation inside the block plugin:
  $ parted -s $(losetup -f) unit s print

  https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52

  but if I run it on the next next unused loop device, in this case
  /dev/loop3 (which is also unused), no errors.

  While I agree that sosreport shouldn't query unused loop devices,
  there is definitely something going on with the next unused loop
  device.

  What is differentiate loop2 and loop3 and any other unused ones ?

  3 things so far I have noticed:
  * loop2 is the next unused loop device (losetup -f)
  * A reboot is needed (if some loop modification (snap install, mount loop, 
...) has been made at runtime
  * I have also noticed that loop2 (or whatever the next unused one is) have 
some stat as oppose to other unused loop devices. The stat exist already right 
after the system boot for the next unused loop device.

  /sys/block/loop2/stat
  ::
  2 0 10 0 1 0 0 0 0 0 0

  2  = number of read I/Os processed
  10 = number of sectors read
  1  = number of write I/Os processed

  Explanation of each column:
  https://www.kernel.org/doc/html/latest/block/stat.html

  while /dev/loop3 doesn't

  /sys/block/loop3/stat
  ::
  0 0 0 0 0 0 0 0 0 0 0

  Which tells me that something during the boot process most likely
  acquired (on purpose or not) the next unused loop and possibly didn't
  released it well enough.

  If loop2 is generating errors, and I install a snap, the snap squashfs
  will take loop2, making loop3 the next unused loop device.

  If I query loop3 with 'parted' right after, no errors.

  If I reboot, and query loop3 again, then no I'll have an error.

  To triggers the errors it need to be after a reboot and it only impact
  the first unused loop device available (losetup -f).

  This was tested with focal/systemd whic his very close to latest
  upstream code.

  This has been test with latest v5.5 mainline kernel as well.

  For now, I don't think it's a kernel problem, I'm more thinking of a
  userspace misbehaviour dealing with loop device (or block device) at
  boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1856871/+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 1856880] [NEW] Unable to install intel from partner repositories

2019-12-18 Thread anonymous abcd
Public bug reported:

The following packages have unmet dependencies:
 xserver-xorg-video-intel : Depends: xorg-video-abi-23
Depends: xserver-xorg-core (>= 2:1.18.99.901)
E: Unable to correct problems, you have held broken packages.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 18 23:14:32 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:1094]
   Subsystem: Acer Incorporated [ALI] GM108M [GeForce 940MX] [1025:1094]
InstallationDate: Installed on 2019-12-18 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b571 Chicony Electronics Co., Ltd 
 Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic 
root=UUID=b7dfb4a2-5789-441a-9384-11e4d4c2b6c4 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2019
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.51
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ironman_SK
dmi.board.vendor: Acer
dmi.board.version: V1.51
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.51:bd05/31/2019:svnAcer:pn:pvrV1.51:rvnAcer:rnIronman_SK:rvrV1.51:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: KBL
dmi.product.sku: _115F_1.51
dmi.product.version: V1.51
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Unable to install intel from partner repositories

Status in xorg package in Ubuntu:
  New

Bug description:
  The following packages have unmet dependencies:
   xserver-xorg-video-intel : Depends: xorg-video-abi-23
  Depends: xserver-xorg-core (>= 2:1.18.99.901)
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 18 23:14:32 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:1094]
 Subsystem: Acer Incorporated [ALI] GM108M [GeForce 940MX] [1025:1094]
  InstallationDate: Installed on 2019-12-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b571 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic 
root=UUID=b7dfb4a2-5789-441a-9384-11e4d4c2b6c4 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.51
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ironman_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.51
 

[Touch-packages] [Bug 1856871] Re: i/o error if next unused loop device is queried

2019-12-18 Thread Eric Desrochers
Booting with "systemd.log_level=debug" revealed:

Dec 18 17:26:22 ubuntu systemd-udevd[1326]: value '[dmi/id]sys_vendor' is 'QEMU'
Dec 18 17:26:22 ubuntu systemd-udevd[1326]: created db file 
'/run/udev/data/b7:2' for '/devices/virtual/block/loop2'
Dec 18 17:26:22 ubuntu systemd[1]: dev-loop2.device: Changed dead -> tentative
Dec 18 17:26:22 ubuntu systemd-udevd[1326]: created db file 
'/run/udev/data/b7:2' for '/devices/virtual/block/loop2'
Dec 18 17:26:22 ubuntu systemd-udevd[1326]: passed 293 byte device to netlink 
monitor 0x557a8c0f8680
Dec 18 17:26:22 ubuntu systemd[1120]: dev-loop2.device: Changed dead -> 
tentative
...
Dec 18 17:26:22 ubuntu systemd[1120]: sys-devices-virtual-block-loop2.device: 
Changed dead -> plugged
Dec 18 17:26:22 ubuntu systemd[1120]: dev-loop2.device: Changed tentative -> 
plugged
Dec 18 17:26:22 ubuntu systemd-udevd[529]: passed 179 byte device to netlink 
monitor 0x557a8c0c7bc0
Dec 18 17:26:22 ubuntu systemd[1]: sys-devices-virtual-block-loop2.device: 
Changed dead -> plugged
Dec 18 17:26:22 ubuntu systemd[1]: dev-loop2.device: Changed tentative -> 
plugged
...
Dec 18 17:26:22 ubuntu systemd[1]: Sent message type=signal sender=n/a 
destination=n/a path=/org/freedesktop/systemd1/unit/dev_2dloop2_2edevice 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=1009 
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Dec 18 17:26:22 ubuntu systemd[1]: Sent message type=signal sender=n/a 
destination=n/a path=/org/freedesktop/systemd1/unit/dev_2dloop2_2edevice 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=1010 
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
...
Dec 18 17:26:22 ubuntu systemd-udevd[1328]: created db file 
'/run/udev/data/b7:2' for '/devices/virtual/block/loop2'
Dec 18 17:26:22 ubuntu systemd-udevd[1328]: created db file 
'/run/udev/data/b7:2' for '/devices/virtual/block/loop2'
Dec 18 17:26:22 ubuntu systemd-udevd[1328]: passed 252 byte device to netlink 
monitor 0x557a8c0f8680
Dec 18 17:26:22 ubuntu systemd[1]: sys-devices-virtual-block-loop2.device: 
Installed new job sys-devices-virtual-block-loop2.device/nop as 412
Dec 18 17:26:22 ubuntu systemd[1]: dev-loop2.device: Installed new job 
dev-loop2.device/nop as 413
Dec 18 17:26:22 ubuntu systemd[1]: sys-devices-virtual-block-loop2.device: 
Changed plugged -> dead
Dec 18 17:26:22 ubuntu systemd[1120]: sys-devices-virtual-block-loop2.device: 
Installed new job sys-devices-virtual-block-loop2.device/nop as 14
Dec 18 17:26:22 ubuntu systemd[1]: dev-loop2.device: Changed plugged -> dead
Dec 18 17:26:22 ubuntu systemd[1120]: dev-loop2.device: Installed new job 
dev-loop2.device/nop as 15
Dec 18 17:26:22 ubuntu systemd[1120]: sys-devices-virtual-block-loop2.device: 
Changed plugged -> dead
Dec 18 17:26:22 ubuntu systemd[1]: Sent message type=signal sender=n/a 
destination=n/a path=/org/freedesktop/systemd1/unit/dev_2dloop2_2edevice 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=1028 
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Dec 18 17:26:22 ubuntu systemd[1120]: dev-loop2.device: Changed plugged -> dead
Dec 18 17:26:22 ubuntu systemd[1]: Sent message type=signal sender=n/a 
destination=n/a path=/org/freedesktop/systemd1/unit/dev_2dloop2_2edevice 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=1029 
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Dec 18 17:26:22 ubuntu systemd[1120]: dev-loop2.device: Job 
dev-loop2.device/nop finished, result=done
Dec 18 17:26:22 ubuntu systemd[1120]: sys-devices-virtual-block-loop2.device: 
Job sys-devices-virtual-block-loop2.device/nop finished, result=done
Dec 18 17:26:22 ubuntu systemd[1]: Sent message type=signal sender=n/a 
destination=n/a 
path=/org/freedesktop/systemd1/unit/sys_2ddevices_2dvirtual_2dblock_2dloop2_2edevice
 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=1030 
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Dec 18 17:26:22 ubuntu systemd[1120]: sys-devices-virtual-block-loop2.device: 
Collecting.
Dec 18 17:26:22 ubuntu systemd[1]: Sent message type=signal sender=n/a 
destination=n/a 
path=/org/freedesktop/systemd1/unit/sys_2ddevices_2dvirtual_2dblock_2dloop2_2edevice
 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=1031 
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Dec 18 17:26:22 ubuntu systemd[1120]: dev-loop2.device: Collecting.
Dec 18 17:26:22 ubuntu systemd[1]: Sent message type=signal sender=n/a 
destination=n/a path=/org/freedesktop/systemd1 
interface=org.freedesktop.systemd1.Manager member=JobNew cookie=1032 
reply_cookie=0 signature=uos error-name=n/a error-message=n/a
Dec 18 17:26:22 ubuntu systemd[1]: Sent message type=signal sender=n/a 
destination=n/a path=/org/freedesktop/systemd1 
interface=org.freedesktop.systemd1.Manager member=JobNew cookie=1033 
reply_cookie=0 

[Touch-packages] [Bug 1856871] Re: i/o error if next unused loop device is queried

2019-12-18 Thread Eric Desrochers
** Description changed:

  This is reproducible in Bionic and late.
  
  Here's an example running 'focal':
  
  $ lsb_release -cs
  focal
  
  $ uname -r
  5.3.0-24-generic
  
+ The error is:
+ blk_update_request: I/O error, dev loop2, sector 0
+ 
  How to trigger it:
- 
  $ sosreport -o block
  
- or more precisely the command causing the situation inside the block plugin:
+ or more precisely the cmd causing the situation inside the block plugin:
  $ parted -s /dev/$(losetup -f) unit s print
  
  https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52
  
  but if I run it on the next next unused loop device, in this case
  /dev/loop3 (which is also unused), no errors.
  
  While I agree that sosreport shouldn't query unused loop devices, there
  is definitely something going on with the next unused loop device.
  
- What is the difference between loop2 and loop3 and other unused one ?
+ What is differentiate loop2 and loop3 and any other unused ones ?
  
  3 things so far I have noticed:
- * The loop device need to be the next unused loop device (losetup -f)
+ * loop2 is the next unused loop device (losetup -f)
  * A reboot is needed (if some loop modification (snap install, mount loop, 
...) has been made at runtime
  * I have also noticed that loop2 (or whatever the next unused one is) have 
some stat as oppose to other unused loop devices. The stat exist already right 
after the system boot for the next unused loop device.
  
  /sys/block/loop2/stat
  ::
  2 0 10 0 1 0 0 0 0 0 0
  
  2  = number of read I/Os processed
- 10 = number of sectors read 
+ 10 = number of sectors read
  1  = number of write I/Os processed
  
  Explanation of each column:
  https://www.kernel.org/doc/html/latest/block/stat.html
  
  while /dev/loop3 doesn't
  
  /sys/block/loop3/stat
  ::
  0 0 0 0 0 0 0 0 0 0 0
  
- 
- Which tells me that something during the boot process most likely acquired 
(on purpose or not) the next unused loop and possibly didn't released it well.
+ Which tells me that something during the boot process most likely
+ acquired (on purpose or not) the next unused loop and possibly didn't
+ released it well enough.
  
  If loop2 is generating errors, and I install a snap, the snap squashfs
  will take loop2, making loop3 the next unused loop device.
  
  If I query loop3 with 'parted' right after, no errors.
  
  If I reboot, and query loop3 again, then no I'll have an error.
  
  To triggers the errors it need to be after a reboot and it only impact
  the first unused loop device available (losetup -f).
  
- This was tested with focal/systemd whic his very close to latest upstream 
code.
- This has been test with latest v5.5 kernel as well. For now, I don't think 
it's a kernel problem, I'm more thinking of a userspace misbehaviour dealing 
with loop device at boot.
+ This was tested with focal/systemd whic his very close to latest
+ upstream code.
+ 
+ This has been test with latest v5.5 mainline kernel as well.
+ 
+ For now, I don't think it's a kernel problem, I'm more thinking of a
+ userspace misbehaviour dealing with loop device (or block device) at
+ boot.

** Description changed:

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

Title:
  i/o error if next unused loop device is queried

Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New

Bug description:
  This is reproducible in Bionic and late.

  Here's an example running 'focal':

  $ lsb_release -cs
  focal

  $ uname -r
  5.3.0-24-generic

  The error is:
  blk_update_request: I/O error, dev loop2, sector 0

  How to trigger it:
  $ sosreport -o block

  or more precisely the cmd causing the situation inside the block plugin:
  $ parted -s /dev/$(losetup -f) unit s print

  https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52

  but if I run it on the next next unused loop device, in this case
  /dev/loop3 (which is also unused), no errors.

  While I agree that sosreport shouldn't query unused loop devices,
  there is definitely something going on with the next unused loop
  device.

  What is differentiate loop2 and loop3 and any other unused ones ?

  3 things so far I have noticed:
  * loop2 is the next unused loop device (losetup -f)
  * A reboot is needed (if some loop modification (snap install, mount loop, 
...) has been made at runtime
  * I have also noticed that loop2 (or whatever the next unused one is) have 
some stat as oppose to other unused loop devices. The stat exist already right 
after the system boot for the next unused loop device.

  /sys/block/loop2/stat
  ::
  2 0 10 0 1 0 0 0 0 0 0

  2  = number of read I/Os processed
  10 = number of sectors read
  1  = number of write I/Os processed

  Explanation of each column:
  https://www.kernel.org/doc/html/latest/block/stat.html

  while 

[Touch-packages] [Bug 1856872] [NEW] bluez regression: Bluetooth fails after resume

2019-12-18 Thread bishoptf
Public bug reported:

New laptop that is running Ubuntu Mate 19.10, most everything works out
of the box even bluetooth but bluetooth does not resume after suspend.
In fact I am unable to restart it and get it to work after a suspend.
Wireless resumes and continues to work, just bluetooth fails. After
suspend the controller and adapter are not found, restarting
bluetooth.service nor restarting network manger solve the issue.  After
a resume the adapter is not found at all, I have tried to remove the
module before a suspend and add it back to no avail, the only way to get
it working is to reboot which is a pain.

Please let me know what additional data you may need, posting
information below:

Chipset is Realtek RTL8822CE, combined wireless and Bluetooth module
Running Bluez 5.50 package...

Working on intial Boot:

lsusb -tv
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
ID 0408:5365 Quanta Computer, Inc.
|__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
ID 0408:5365 Quanta Computer, Inc.
|__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
ID 0bda:b00c Realtek Semiconductor Corp.
|__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
ID 0bda:b00c Realtek Semiconductor Corp.

rfkill list
0: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
1: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

usb-devices
T:  Bus=01 Lev=01 Prnt=01 Port=09 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
D:  Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0bda ProdID=b00c Rev=00.00
S:  Manufacturer=Realtek
S:  Product=Bluetooth Radio
S:  SerialNumber=00e04c01
C:  #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA
I:  If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
I:  If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera
Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

dmesg | grep Blue
[1.192743] usb 1-10: Product: Bluetooth Radio
[   11.706607] Bluetooth: Core ver 2.22
[   11.706620] Bluetooth: HCI device and connection manager initialized
[   11.706624] Bluetooth: HCI socket layer initialized
[   11.706626] Bluetooth: L2CAP socket layer initialized
[   11.706628] Bluetooth: SCO socket layer initialized
[   11.720229] Bluetooth: hci0: RTL: rtl: examining hci_ver=0a hci_rev=000c 
lmp_ver=0a lmp_subver=8822
[   11.721252] Bluetooth: hci0: RTL: rom_version status=0 version=3
[   11.721254] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_fw.bin
[   11.722558] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_config.bin
[   11.722879] Bluetooth: hci0: RTL: cfg_sz 6, total sz 24866
[   15.466810] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   15.466812] Bluetooth: BNEP filters: protocol multicast
[   15.466816] Bluetooth: BNEP socket layer initialized
[   18.070246] Bluetooth: RFCOMM TTY layer initialized
[   18.070250] Bluetooth: RFCOMM socket layer initialized
[   18.070253] Bluetooth: RFCOMM ver 1.11

After resume:

lsusb -tv
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
ID 0408:5365 Quanta Computer, Inc.
|__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
ID 0408:5365 Quanta Computer, Inc.

rfkill list
1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no

usb-devices

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh=12
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev=05.03
S:  Manufacturer=Linux 5.3.0-24-generic xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=:00:14.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#=  2 Spd=480 MxCh= 0
D:  Ver= 2.01 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0408 ProdID=5365 Rev=00.02
S:  Manufacturer=SunplusIT Inc
S:  Product=HP TrueVision HD Camera
C:  #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA
I:  If#=0x0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo
I:  If#=0x1 Alt= 0 #EPs= 0 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=1 MxCh= 6
D:  Ver= 3.10 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=1d6b ProdID=0003 Rev=05.03
S:  Manufacturer=Linux 5.3.0-24-generic xhci-hcd
S:  

[Touch-packages] [Bug 1856871] [NEW] i/o error if next unused loop device is queried

2019-12-18 Thread Eric Desrochers
Public bug reported:

This is reproducible in Bionic and late.

Here's an example running 'focal':

$ lsb_release -cs
focal

$ uname -r
5.3.0-24-generic

How to trigger it:

$ sosreport -o block

or more precisely the command causing the situation inside the block plugin:
$ parted -s /dev/$(losetup -f) unit s print

https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52

but if I run it on the next next unused loop device, in this case
/dev/loop3 (which is also unused), no errors.

While I agree that sosreport shouldn't query unused loop devices, there
is definitely something going on with the next unused loop device.

What is the difference between loop2 and loop3 and other unused one ?

3 things so far I have noticed:
* The loop device need to be the next unused loop device (losetup -f)
* A reboot is needed (if some loop modification (snap install, mount loop, ...) 
has been made at runtime
* I have also noticed that loop2 (or whatever the next unused one is) have some 
stat as oppose to other unused loop devices. The stat exist already right after 
the system boot for the next unused loop device.

/sys/block/loop2/stat
::
2 0 10 0 1 0 0 0 0 0 0

2  = number of read I/Os processed
10 = number of sectors read 
1  = number of write I/Os processed

Explanation of each column:
https://www.kernel.org/doc/html/latest/block/stat.html

while /dev/loop3 doesn't

/sys/block/loop3/stat
::
0 0 0 0 0 0 0 0 0 0 0


Which tells me that something during the boot process most likely acquired (on 
purpose or not) the next unused loop and possibly didn't released it well.

If loop2 is generating errors, and I install a snap, the snap squashfs
will take loop2, making loop3 the next unused loop device.

If I query loop3 with 'parted' right after, no errors.

If I reboot, and query loop3 again, then no I'll have an error.

To triggers the errors it need to be after a reboot and it only impact
the first unused loop device available (losetup -f).

This was tested with focal/systemd whic his very close to latest upstream code.
This has been test with latest v5.5 kernel as well. For now, I don't think it's 
a kernel problem, I'm more thinking of a userspace misbehaviour dealing with 
loop device at boot.

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

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


** Tags: sts

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

** Description changed:

  This is reproducible in Bionic and late.
  
  Here's an example running 'focal':
  
  $ lsb_release -cs
  focal
  
  $ uname -r
  5.3.0-24-generic
  
  How to trigger it:
  
  $ sosreport -o block
  
  or more precisely the command causing the situation inside the block plugin:
  $ parted -s /dev/$(losetup -f) unit s print
  
  https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52
  
- 
- but if I run it on the next next unused loop device, in this case /dev/loop3 
(which is also unused), no errors.
+ but if I run it on the next next unused loop device, in this case
+ /dev/loop3 (which is also unused), no errors.
  
  While I agree that sosreport shouldn't query unused loop devices, there
  is definitely something going on with the next unused loop device.
  
  What is the difference between loop2 and loop3 and other unused one ?
  
  3 things so far I have noticed:
  * The loop device need to be the next unused loop device (losetup -f)
  * A reboot is needed (if some loop modification (snap install, mount loop, 
...) has been made at runtime
- * I have also noticed that loop2 (or whatever the next unused one is) have 
some stat as oppose to other unused loop devices
+ * I have also noticed that loop2 (or whatever the next unused one is) have 
some stat as oppose to other unused loop devices. The stat exist already right 
after the system boot for the next unused loop device.
  
  /sys/block/loop2/stat
  ::
  2 0 10 0 1 0 0 0 0 0 0
  
  while /dev/loop3 doesn't
  
- /sys/block/loop2/stat
+ /sys/block/loop3/stat
  ::
  0 0 0 0 0 0 0 0 0 0 0
  
  Explanation of each column:
  
https://meet.google.com/linkredirect?authuser=0=https%3A%2F%2Fwww.kernel.org%2Fdoc%2Fhtml%2Flatest%2Fblock%2Fstat.html
  
  Which tells me that something during the boot process most likely
  acquired (on purpose or not) the next unused loop and possibly didn't
  released it well.
  
  If loop2 is generating errors, and I install a snap, the snap squashfs
  will take loop2, making loop3 the next unused loop device.
  
  If I query loop3 with 'parted' right after, no errors.
  
  If I reboot, and query loop3 again, then no I'll have an error.
  
  To triggers the errors it need to be after a reboot and it only impact
  the first unused loop device available (losetup -f).
  
  This was tested with focal/systemd whic his very close to latest upstream 
code.
  This has been test with latest v5.5 kernel as well. For 

[Touch-packages] [Bug 1856574] Re: removal of various autopilot packages

2019-12-18 Thread Jean-Baptiste Lallement
** Changed in: autopilot-gtk (Ubuntu)
 Assignee: Jean-Baptiste Lallement (jibel) => (unassigned)

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

Title:
  removal of various autopilot packages

Status in autopilot-gtk package in Ubuntu:
  Fix Released
Status in autopilot-legacy package in Ubuntu:
  New
Status in python-fixtures package in Ubuntu:
  New
Status in python-testtools package in Ubuntu:
  New

Bug description:
  python-fixtures and python-testtools are not built anymore in focal,
  but still referenced by some Ubuntu-only packages.  We need to at
  least remove autopilot-legacy if we don't want to re-introduce those
  package, and modify autopilot-gtk to build witout the autopilot-legacy
  b-d.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopilot-gtk/+bug/1856574/+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 1733142] Re: unattended-upgrades 0.90ubuntu0.8 spit ERROR: os.close(4): [Errno 9] Bad file descriptor

2019-12-18 Thread Balint Reczey
I believe this is fixed since then. Please reopen if you still observe
the issue.

** Changed in: unattended-upgrades (Ubuntu)
   Status: Confirmed => 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/1733142

Title:
  unattended-upgrades 0.90ubuntu0.8 spit ERROR: os.close(4): [Errno 9]
  Bad file descriptor

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Description:
  unattended-upgrades could execute its task successfully, but gives the error 
message during the task.

  $ lsb_release -a
  Description:  Ubuntu 16.04.3 LTS
  Codename: xenial

  $ uname -a
  Linux  4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux

  dpkg -l unattended-upgrades
  Version: 0.90ubuntu0.8

  Reduplication procedure:
  * Available packages for unattended-upgrades to upgrade
  * sudo unattended-upgrades
  * Wait for unattended-upgrades to finish its task
  * check the console message:

  ... ...
  marking libmircommon5 for remove
  Packages that are auto removed: 'libmircommon5'
  ERROR: os.close(4): [Errno 9] Bad file descriptor
  ERROR: os.close(5): [Errno 9] Bad file descriptor
  ERROR: os.close(6): [Errno 9] Bad file descriptor
  ERROR: os.close(150): [Errno 9] Bad file descriptor

  Sometimes the os.close error is:
  Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
  ERROR: os.close(4): [Errno 9] Bad file descriptor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1733142/+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 1827328] Re: ModemManager does not honor blacklisted ttys (ID_MM_DEVICE_IGNORE)

2019-12-18 Thread Lionel Penaud
Also observed on Ubuntu 18.04.3, with kernel 5.0.0-37-generic

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

Title:
  ModemManager does not honor blacklisted ttys (ID_MM_DEVICE_IGNORE)

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 19.04 (and likely earlier) Modem Manager is installed with
  filter policy 'strict' as opposed to 'default', which actually makes
  Modem Manager _less_ strict regarding explicitly blacklisted ttys (see
  man modemmanager).

  This means that ttys, that are explicitly blacklisted from Modem
  Manager by using ENV{ID_MM_DEVICE_IGNORE}="1" in its udev rule is
  still opened and probed by Modem Manager although it should not.

  This is a common cause of problems and frustrations for people working
  with actual serial devices, e.g. within embedded development (e.g.
  Arduino and the like). See https://nick.zoic.org/art/failed-to-set-
  dtr-rts-systemd-modemmanager/ for an example.

  A proposed solution is to change the following line in: 
/lib/systemd/system/ModemManager.service
  from:
  ExecStart=/usr/sbin/ModemManager --filter-policy=strict
  to:
  ExecStart=/usr/sbin/ModemManager --filter-policy=paranoid

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: modemmanager 1.10.0-1 [modified: 
lib/systemd/system/ModemManager.service]
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 15:35:58 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-26 (340 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: modemmanager
  UpgradeStatus: Upgraded to disco on 2019-04-18 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1827328/+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 1856811] Re: Systemd warning re moving remaining userspace processes

2019-12-18 Thread Brian Murray
** Summary changed:

- Systemd warning
+ Systemd warning re moving remaining userspace processes

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

Title:
  Systemd warning re moving remaining userspace processes

Status in systemd package in Ubuntu:
  New

Bug description:
  :~$ dmesg|grep error
  [   49.262644] systemd[1]: Couldn't move remaining userspace processes, 
ignoring: Input/output error
  systemd/focal-proposed,now 244-3ubuntu1 amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1856811/+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 1856731] Re: Cannot add a Google accounts with GOA

2019-12-18 Thread Sebastien Bacher
likely an upstream issue, could be useful to report it also on gitlab
(including journal log)

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

Title:
  Cannot add a Google accounts with GOA

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

Bug description:
  On a freshly installed 20.04 system, going through the initial setup
  and I'm presented with the Online Accounts panel where I selected
  Google, entered my email and password. Then Google's 2-factor
  authentication kicks in and instructs me to check my phone. I do and
  approve the connection, but the online accounts page on the laptop
  never updates until it eventually asks if I want the authentication to
  be resent.

  There are two older bugs that looks like this - both are fix committed:
  - https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1687019
  - https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1175122

  Opening a new bug since the issue definitely exists and the other bugs
  have been fix committed for years.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-online-accounts 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 17 09:17:06 2019
  InstallationDate: Installed on 2019-12-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217)
  ProcEnviron:
   TERM=xterm-256color
   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/ubuntu/+source/gnome-online-accounts/+bug/1856731/+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 1666432] Re: Internet drops every few minutes on wired and wireless connection

2019-12-18 Thread Kent Lion
Perhaps this can help: The symptoms I experience started sometime during
the past year after an update (sudo apt update && sudo apt upgrade &&
sudo apt autoremove) are that some indefinite time (usually less than ½
hour) after I log on, the network disconnects without warning or error.
Clicking on the up/down arrows of the indicator plugin and selecting the
interface reconnects; however, I recently discovered that if, as soon as
I log on, I select "Disconnect" and then select the adapter to
reconnect, my session will be fine until I log out and back in again. So
perhaps the bug is not with network-manager, samba or ifupdown, but with
the logon process(es). My version is 18.04 and I'm using LiteDM GTK+. I
haven't the faintest idea where to look for a cause that might be
related to the logon process(s), but none of the very many "solutions"
offered on various web pages I found on the problem have fixed it for
me.

One other unexpected thing I've noticed is that in editing Ethernet
connections (I don't used wireless enough to have noticed a problem), I
can't edit (or delete) the one the system creates without first adding
another (even if it's the same, e.g., enp2s0, with the same settings)
and switching to it; however, after I did that the first time, and
deleted the system's entry ("Wired connection 1", I think it was
called), at some point the system added another entry, identical in
every way to the one I had added, but called "Ifupdown (enp2s0)" and
connects to that when I log on, not to the one I created (which I have
since deleted, but the original problem still occurs, and disconnecting
and reconnecting still prevents the random disconnect).

All of this applies to 2 other machines, also running up-to-date xubuntu
18.04, although on one of the other machines, the adapter is enp4s25. It
also occurs with xubuntu and xfce sessions. I suspect the difficutly in
finding the cause(s) is in part due to the confusing way samba/network
settings are stored, with the same setting sometimes stored in different
locations, entered via GUI or command line or both, possibly leading to
conflicts.

I have spent many hours on this problem, and have only the above work-
around, not a fix. Even though this problem has been around longer than
18.04, since 18.04, samba has clearly been broken, and until networking
is as reliable and as easy to set up as in Windows, (x/l/k)ubuntu will
not be suitable for typical home users.

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

Title:
  Internet drops every few minutes on wired and wireless connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Internet drops every 1-30 minutes when connected via wired or wireless
  (i.e., this is a problem on both wired and wireless) even though
  connection icon indicates the computer is still connected.

  Disconnecting and reconnecting via the connection icon resets internet
  temporarily until the next time.

  Dropped internet is discovered with "The site can't be reached"
  screens in Chromium, or error messages when downloading/updating in
  Terminal, or missing connection in Ubuntu Software app, or stalled
  syncing in Insync application (occurred even without Insync).

  Internet drops more frequently on wireless than on wired.

  It seems to disconnect more frequently with heavier internet use
  (e.g., downloading multiple files, opening several webpages in quick
  succession).

  This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron
  15 5567 (dual boot). It occurs when running Live CD as well though.

  Ethernet and wifi both work without randomly disconnecting in Windows
  10 on the same machine, and ethernet and wifi work on other machines
  running Ubuntu and Windows with the same router, so it is not a
  hardware or router issue.

  Output from sudo lshw -class network

  *-network
     description: Wireless interface
     product: Wireless 3165
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:02:00.0
     logical name: wlp2s0
     version: 79
     serial: 58:fb:84:55:21:52
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
     resources: irq:283 memory:df10-df101fff
    *-network
     description: Ethernet interface
     product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:03:00.0
     logical name: enp3s0
     version: 07
     serial: 18:db:f2:3c:d5:37
     size: 10Mbit/s
    

[Touch-packages] [Bug 1856604] Re: First char appears twice when searching in "Save as..." dialog in every application

2019-12-18 Thread Sebastien Bacher
** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  First char appears twice when searching in "Save as..." dialog in
  every application

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  - Open a document or web page in an application with a "Save as..." function. 
Possible examples I tried are LibreOffice Calc and Brave browser.
  - Hit "Save as.."
  - In the file list below, navigate to to a directory that is not empty.
  - Select one of the files or directories to make sure the list has focus.
  - Type some letters, e.g. "test".

  Expected behavior:
  - Search field appears to filter the list of files and directories.
  - Search string is "test".

  Actual behavior:
  - Search field appears to filter the list of files and directories.
  - Search string is "ttest", with the first letter appearing twice.

  Note:
  This only happens if you follow the instructions above.


  Ubuntu 18.04.3 LTS
  MATE desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-core 1:6.0.7-0ubuntu0.18.04.10
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Dec 16 18:42:16 2019
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2019-01-12 (337 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1856604/+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 970814] Re: Combobox badly initialized (semi-sensitive?) since gtk3

2019-12-18 Thread Sebastien Bacher
Is that still an issue in newer Ubuntu versions?

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Incomplete

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

Title:
  Combobox badly initialized (semi-sensitive?) since gtk3

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  My app uses a GTK3 ui created by Glade3.10.
  In the Glade file, there are some combobox with default "sensitive" settings 
(sensitive=yes), other with "non-sensitive" settings (sensitive=no)

  OBSERVED BEHAVIOR:
  When running my app (either in Ubuntu 11.10 or 12.04), all comboboxes 
(sensitive=yes or no) appear in what i will call "semi-sensitive" state: they 
behave like sensitive but their label is greyed (not the arrow, which is 
normally black, see attached screenshot).
  When the user moves the cursor above the combobox, the grey label becomes 
black (like a normal sensitive combobox).

  EXPECTED BEHAVIOR:
  the comboboxes should directly appear in the state chosen in the Glade file.

  
  WORKAROUND: 
  in the code of my app, i send a signal to set the state of the combobox as 
"sensitive" to make it sensitive at start. If i want the combobox to appear 
"non-sensitive" at start, i need to send a signal to set the state of the 
combobox as "sensitive" then another one to set it "non-sensitive".

  
  Remarks: 
  - don't hesitate to ask more informations, or link me to the right place.
  - with gtk2 my app does not have this bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/970814/+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 1856439] Re: Add "Set Application as Default" to the "Open with Other Application" popup.

2019-12-18 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1413283 ***
https://bugs.launchpad.net/bugs/1413283

was already reported as bug #1413283

** This bug has been marked a duplicate of bug 1413283
   "Set as default" is absent from "Open with.." context menu

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

Title:
  Add "Set Application as Default" to the "Open with Other Application"
  popup.

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  1) Ubuntu 19.10
  2) 1:3.34.1-1ubuntu2
  3) Ability to set selected application as default.
  4) No "Set Application as Default" on "Select Application" popup.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1856439/+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 1856439] Re: Add "Set Application as Default" to the "Open with Other Application" popup.

2019-12-18 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1413283 ***
https://bugs.launchpad.net/bugs/1413283

The 'open with' dialog is a gkt component, reassigning

** Package changed: gnome-control-center (Ubuntu) => gtk+3.0 (Ubuntu)

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Add "Set Application as Default" to the "Open with Other Application"
  popup.

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  1) Ubuntu 19.10
  2) 1:3.34.1-1ubuntu2
  3) Ability to set selected application as default.
  4) No "Set Application as Default" on "Select Application" popup.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1856439/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

2019-12-18 Thread Sebastien Bacher
Uploaded to the SRU queue nowb

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  Low. The fix proposed just reverts to the same code used in PulseAudio
  12 and earlier. It has also been released and verified on focal
  already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1856439] [NEW] Add "Set Application as Default" to the "Open with Other Application" popup.

2019-12-18 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

1) Ubuntu 19.10
2) 1:3.34.1-1ubuntu2
3) Ability to set selected application as default.
4) No "Set Application as Default" on "Select Application" popup.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Wishlist
 Status: New

-- 
Add "Set Application as Default" to the "Open with Other Application" popup.
https://bugs.launchpad.net/bugs/1856439
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 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 1856592] Re: Nautilus button icons are missing

2019-12-18 Thread Sebastien Bacher
You didn't attach the journal log, one way to do it would be
$ journalctl -b 0 > log
and add the log file to the bug

What's the outut of
$ dpkg -l ubuntu-mono

does it make a difference if you use
$ gsettings reset org.gnome.desktop.interface icon-theme

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

Title:
  Nautilus button icons are missing

Status in gtk+3.0 package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  in some programs th little  icons that allow to undo or redo or the
  icons that allow to go up or down appear like some little squares! I
  don't know how can I solve this problem!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.21
  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
  Date: Mon Dec 16 17:40:38 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3905]
  InstallationDate: Installed on 2019-12-07 (8 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: LENOVO 80G0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=42ddfb90-969c-4976-998c-893d136068bb ro splash quiet pci=nomsi 
RESUME=UUID=92781adb-f2a6-4f15-88fc-e1ce801291dd vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/22/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN45WW:bd01/22/2015:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Dec 16 17:31:25 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1856592/+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 1856574] Re: removal of various autopilot packages

2019-12-18 Thread Launchpad Bug Tracker
This bug was fixed in the package autopilot-gtk - 1.6.0

---
autopilot-gtk (1.6.0) focal; urgency=medium

  * Remove the dependency on python2 version of autopilot (LP: #1856574)
  * Update the dependencies to python3 version of autopilot.
  * Fixed the testsuite.
  * Bump version number and align it with autopilot
  * Update Standards-Version to 4.4.1

 -- Jean-Baptiste Lallement   Tue,
17 Dec 2019 07:55:05 +0100

** Changed in: autopilot-gtk (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 python-testtools in
Ubuntu.
https://bugs.launchpad.net/bugs/1856574

Title:
  removal of various autopilot packages

Status in autopilot-gtk package in Ubuntu:
  Fix Released
Status in autopilot-legacy package in Ubuntu:
  New
Status in python-fixtures package in Ubuntu:
  New
Status in python-testtools package in Ubuntu:
  New

Bug description:
  python-fixtures and python-testtools are not built anymore in focal,
  but still referenced by some Ubuntu-only packages.  We need to at
  least remove autopilot-legacy if we don't want to re-introduce those
  package, and modify autopilot-gtk to build witout the autopilot-legacy
  b-d.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopilot-gtk/+bug/1856574/+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 1853852] Re: hard to reproduce issues in systemd autopkgtest against new libseccomp 2.4.2

2019-12-18 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 244-3ubuntu1

---
systemd (244-3ubuntu1) focal; urgency=medium

  [ Balint Reczey ]
  * Merge to Ubuntu from Debian unstable
  * Refresh patches:
- Dropped changes:
  * d/t/control: mark udev test skippable.
File: debian/tests/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c3419bd2a30a78d05cca9c38e50c9726de7e7632
  * test-execute: Filter /dev/.lxc in exec-dynamicuser-statedir.service.
File: 
debian/patches/test-execute-Filter-dev-.lxc-in-exec-dynamicuser-statedir.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=75af888d5552f706b86182a56f12ccc8e83ca04e
  * Pass personality test even when i386 userland runs on amd64 kernel
File: 
debian/patches/debian/UBUNTU-test-Pass-personality-test-even-when-i386-userland-runs-o.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=42e0bfc426f19430f6768ef4922a9531a345765f
  * Fix resolved fallback to TCP (LP: #1849658)
Author: Dan Streetman
File: 
debian/patches/resolved-set-stream-type-during-DnsStream-creation.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f1ee30b13c9d2d34968b09ce620f3bc24a1a78c7
- Remaining changes:
  * Recommend networkd-dispatcher
File: debian/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1e3b2c7e4757119da0d550b0b3c0a6626a176dc
  * Enable EFI/bootctl on armhf.
File: debian/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=043122f7d8a1487bfd357e815a6ece1ceea6e7d1
  * debian/control: strengthen dependencies.
File: debian/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1ecf0c372f5212129c85ae60fddf26b2271a1fe
  * Add conflicts with upstart and systemd-shim
File: debian/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=83ed7496afc7c27be026014d109855f7d0ad1176
  * Specify Ubuntu's Vcs-Git
File: debian/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=fd832930ef280c9a4a9dda2440d5a46a6fdb6232
  * Ubuntu/extra: ship dhclient-enter hook.
Files:
- debian/extra/dhclient-enter-resolved-hook
- debian/rules

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f3398a213f80b02bf3db0c1ce9e22d69f6d56764

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=258893bae8cbb12670e4807636fe8f7e9fb5407a

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0725c1169ddde4f41cacba7af3e546704e2206be
  * udev-udeb: ship modprobe.d snippet to force scsi_mod.scan=sync in d-i.
Files:
- debian/extra/modprobe.d-udeb/scsi-mod-scan-sync.conf
- debian/udev-udeb.install

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=eb6d8a2b9504917abb7aa2c4035fdbb7b98227f7
  * debian/extra/start-udev: Set scsi_mod scan=sync even if it's builtin to 
the kernel (we previously only set it in modprobe.d)
Files:
- debian/extra/start-udev

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6b72628f8de991e2c67ac4289fc74daf3abe7d14
  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf:
drop resolvconf.conf drop-in, resolved integration moved to resolvconf 
package.
  * debian/extra/wrap_cl.py: add changelog formatter
Files:
- debian/extra/wrap_cl.py
- debian/gbp.conf

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=26e69bceab9cec8df64cdca18cd71e7c0874f8b3
  * debian/gbp.conf: Set tag format to ubuntu/*
  * debian/gbp.conf: Change debian-branch to ubuntu-eoan
  * libnss-resolve: do not disable and stop systemd-resolved
File: debian/libnss-resolve.postrm

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=95577d14e84e19b614b83b2e24985d89e8c2dac0
  * core: Revert strict mount namespacing/sandboxing, until LXD allows the 
needed mounts.
File: 
debian/patches/Revert-namespace-be-more-careful-when-handling-namespacin.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=030919ba5e4931d6ee576d0259fae67fe4ed9770
  * Add "AssumedApparmorLabel=unconfined" to timedate1 dbus service file
File: 
debian/patches/debian/UBUNTU-Add-AssumedApparmorLabel-unconfined-to-timedate1-dbus.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=5ad0879e10bbe3d641f940260b93c7eb2cf4624c
  * Re-add support for /etc/writable for core18
File: 

[Touch-packages] [Bug 1015819] Re: sb_sasl_generic_pkt_length: received illegal packet length when using Active Directory and ldapsearch and sasl with ssl or tls

2019-12-18 Thread Michael Osipov
I need to add an important note here:
Even this bug is marked as fixed, the change in Cyrus SASL now breaks RFC 4752. 
See my comment: 
https://github.com/cyrusimap/cyrus-sasl/issues/419#issuecomment-566981689

Technically, one would now need to create an issue in Launchpad that
Cyrus SASL GSSAPI mech is broken.

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

Title:
  sb_sasl_generic_pkt_length: received illegal packet length when using
  Active Directory and ldapsearch and sasl with ssl or tls

Status in Cyrus-sasl2:
  Fix Released
Status in cyrus-sasl2 package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 source package in Bionic:
  Triaged
Status in cyrus-sasl2 source package in Cosmic:
  Triaged

Bug description:
  [Status]

  Awaiting upstream fix.

  [Workaround]

  Unknown.

  [Description]

  Not sure if this is a problem with openldap or cyrus-sasl2 at this
  point.

  Using sasl binding only works with ldapsearch when not using ssl or
  tls.  If either ssl or tls is used I see this ouput from -d 1 from
  ldapsearch:

  sb_sasl_generic_pkt_length: received illegal packet length of 813957120 bytes
  sasl_generic_read: want=16, got=16
    :  00 7e 02 01 00 78 84 00  00 00 5d 0a 01 02 04 00   .~...x].
  sb_sasl_cyrus_decode: failed to decode packet: generic failure
  sb_sasl_generic_read: failed to decode packet
  ldap_read: want=8 error=Input/output error

  # numResponses: 0
  ldap_result: Can't contact LDAP server (-1)
  tls_write: want=165 error=Connection reset by peer
  tls_write: want=165 error=Bad file descriptor

To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-sasl2/+bug/1015819/+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 1726068] Re: debconf socket closes if aptdaemon/PK client exits

2019-12-18 Thread Julian Andres Klode
I'm still happy with the test case. It shows that the debconf socket is
independent of whatever frontend is running, and hence closing the
frontend can't close the debconf socket. Which means you can just use
pkcon / aptdcon to test that bit.

I don't really know of any PackageKit frontend that's heavily affected
by this. gnome-software is running as a background service, so I guess
you could install via it and then kill it and check that the prompts
still work. And the KDE stuff is still broken, as they use their own
mess.

For aptdaemon, you could probably write a small script.

** No longer affects: packagekit (Ubuntu Disco)

** No longer affects: aptdaemon (Ubuntu Disco)

** No longer affects: apper (Ubuntu Disco)

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

Title:
  debconf socket closes if aptdaemon/PK client exits

Status in apper package in Ubuntu:
  New
Status in aptdaemon package in Ubuntu:
  Fix Released
Status in packagekit package in Ubuntu:
  Fix Released
Status in software-properties package in Ubuntu:
  Invalid
Status in apper source package in Bionic:
  New
Status in aptdaemon source package in Bionic:
  New
Status in packagekit source package in Bionic:
  New

Bug description:
  [Impact]
  Closing an application using PackageKit or aptdaemon to install packages 
kills the debconf endpoint (because it's a subprocess that's cleaned up), 
causing debconf to use defaults which might lead to wrong results, or even 
cause installations to fail.

  [Solution]
  The solution is to move the end point into a socket-activated systemd unit, 
so that it is independent of the graphical frontend that started the 
transaction. The other advantage is that this offers us restart if the end 
point crashes.

  [Test case]
  1. Install opera deb using packagekit, ensure service is activated
  2. Install opera deb using aptdaemon, ensure service is activated

  Alternatively, you might use another deb that has debconf prompts.

  [Regression potential]
  Systems that do not yet use systemd will fall back to the old method, so 
should not regress.

  Otherwise, if there are bugs, they'd affect the ability to show
  debconf prompts, and behavior would revert to using the defaults.

  There might be some uncertainty if you restart your desktop while the
  helper is running and it does not pick up the new X/Wayland display
  until it restarts (it should fail to connect and restart). Given that
  the helper times out, this should not be an issue in practice, as
  you'd have to logout, login, and start a new install within 60
  seconds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apper/+bug/1726068/+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 1854985] Re: pm-utils overrides runtime power management mode for audio devices

2019-12-18 Thread Alberto Milone
** Changed in: pm-utils (Ubuntu)
   Status: New => Triaged

** Changed in: pm-utils (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: pm-utils (Ubuntu)
   Importance: Undecided => High

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

Title:
  pm-utils overrides runtime power management mode for audio devices

Status in pm-utils package in Ubuntu:
  Triaged

Bug description:
  In newer Ubuntu 18.04 HWE kernels, it is possible for GPU HDA
  controllers to be dynamically runtime-suspended if the HDA's
  power/control mode is set to "auto". However, pm-utils explicitly sets
  this to "on" when resuming, which prevents runtime power management of
  these devices from working as intended.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1854985/+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 1732962] Re: apport uses sys.argv instead of named arguments

2019-12-18 Thread Julian Andres Klode
** Changed in: apport (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  apport uses sys.argv instead of named arguments

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  New
Status in apport source package in Xenial:
  New
Status in apport source package in Bionic:
  New
Status in apport source package in Cosmic:
  Won't Fix
Status in apport source package in Disco:
  Fix Released

Bug description:
  data/apport which processes core files expects a certain quantity of
  arguments in a specific order. This ended up causing an issue with
  some security updates where we were trying to support a new version of
  apport on a host system and one inside a container.  Here's something
  of an example:

  347 # Normal startup
  348 if len(sys.argv) not in (5, 6):
  349 try:
  350 print('Usage: %s [global pid]' % sys.argv[0])
  351 print('The core dump is read from stdin.')

  We could not maintain backwards compatibility because "global pid" is
  an optional argument and "dump mode" was a new argument. So if there
  were five arguments its possible the last one was "dump mode" (no
  global pid) or "global pid" (no support for dump mode).

  Its possible to use strings in /proc/sys/kernel/core_pattern so we
  could use those and have apport accept named arguments e.g:

  $ cat /proc/sys/kernel/core_pattern
  |/usr/share/apport/apport --pid=%p --signal=%s --core-size=%c --dump-mode=%d 
--global-pid=%P

  ['/home/bdmurray/source-trees/apport/artful/data/apport', '--
  pid=5870', '--signal=11', '--core-size=0', '--dump-mode=1', '--global-
  pid=5870']

  Tyler said "that's probably a nice cleanup to make no matter what
  because the magic arg ordering is dangerous".

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1732962/+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 1856691] Re: libpulse-mainloop-glib0:i386 cannot be installed

2019-12-18 Thread Julian
I installed libpulse-mainloop-glib0_11.1-1ubuntu7.5_i386.deb from the link you 
provided.
It worked an I can now install what was depending on that package.

Thank you very much.

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

Title:
  libpulse-mainloop-glib0:i386 cannot be installed

Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  libpulse-mainloop-glib0:i386 cannot be installed because it needs
  libpulse0:i386 (= 1:11.1-1ubuntu7.4), but 1:11.1-1ubuntu7.5 is
  installed. I am running Linux Mint 19.2 which is using the Ubuntu
  bionic packages.

  user@computer:$ sudo apt policy libpulse-mainloop-glib0:i386
  libpulse-mainloop-glib0:i386:
Installiert:   (keine)
Installationskandidat: 1:11.1-1ubuntu7.4
Versionstabelle:
   1:11.1-1ubuntu7.4 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic-updates/main i386 
Packages
   1:11.1-1ubuntu7 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic/main i386 Packages
  user@computer:$ sudo apt policy libpulse0:i386
  libpulse0:i386:
Installiert:   1:11.1-1ubuntu7.5
Installationskandidat: 1:11.1-1ubuntu7.5
Versionstabelle:
   *** 1:11.1-1ubuntu7.5 100
  100 /var/lib/dpkg/status
   1:11.1-1ubuntu7.4 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic-updates/main i386 
Packages
   1:11.1-1ubuntu7 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic/main i386 Packages
  user@computer:$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856691/+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 1813339] Re: Apparmor is denying evince from running vivaldi

2019-12-18 Thread luagwoandersch
Thank you for the reply! The evince (3.28.4-0ubuntu1.2) update done the trick.
So your suggested fix isn't needed anymore in this constellation.

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

Title:
  Apparmor is denying evince from running vivaldi

Status in apparmor package in Ubuntu:
  Won't Fix

Bug description:
  It's similar to this bug https://bugs.launchpad.net/bugs/1432126 or
  discussed here; https://forum.vivaldi.net/topic/33591/vivaldi-opening-
  from-a-link-in-a-pdf-file/7

  Apparmor is denying evince from running vivaldi by clicking on a http
  link

  kernel: [ 3271.799807] audit: type=1400 audit(1548434352.941:114):
  apparmor="DENIED" operation="exec" profile="/usr/bin/evince"
  name="/opt/vivaldi/vivaldi" pid=6795 comm="exo-helper-1"
  requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  vivaldi-stable: 2.2.1388.37-1
  apparmor: 2.12-4ubuntu5.1
  evince: 3.28.4-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1813339/+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 1856811] Re: Systemd warning

2019-12-18 Thread Paul White
** Package changed: ubuntu => systemd (Ubuntu)

** Tags added: focal

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

Title:
  Systemd warning

Status in systemd package in Ubuntu:
  New

Bug description:
  :~$ dmesg|grep error
  [   49.262644] systemd[1]: Couldn't move remaining userspace processes, 
ignoring: Input/output error
  systemd/focal-proposed,now 244-3ubuntu1 amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1856811/+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 1849859] Re: smb printing fails

2019-12-18 Thread Xu Xiaopeng
problem reproduced on my Ubuntu 19.10

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

Title:
  smb printing fails

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1856811] [NEW] Systemd warning

2019-12-18 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

:~$ dmesg|grep error
[   49.262644] systemd[1]: Couldn't move remaining userspace processes, 
ignoring: Input/output error
systemd/focal-proposed,now 244-3ubuntu1 amd64

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


** Tags: bot-comment
-- 
Systemd warning
https://bugs.launchpad.net/bugs/1856811
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd 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 1856604] Re: First char appears twice when searching in "Save as..." dialog in every application

2019-12-18 Thread Marcus Tomlinson
** Package changed: libreoffice (Ubuntu) => gtk+3.0 (Ubuntu)

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

Title:
  First char appears twice when searching in "Save as..." dialog in
  every application

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  - Open a document or web page in an application with a "Save as..." function. 
Possible examples I tried are LibreOffice Calc and Brave browser.
  - Hit "Save as.."
  - In the file list below, navigate to to a directory that is not empty.
  - Select one of the files or directories to make sure the list has focus.
  - Type some letters, e.g. "test".

  Expected behavior:
  - Search field appears to filter the list of files and directories.
  - Search string is "test".

  Actual behavior:
  - Search field appears to filter the list of files and directories.
  - Search string is "ttest", with the first letter appearing twice.

  Note:
  This only happens if you follow the instructions above.


  Ubuntu 18.04.3 LTS
  MATE desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-core 1:6.0.7-0ubuntu0.18.04.10
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Dec 16 18:42:16 2019
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2019-01-12 (337 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1856604/+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 1856604] [NEW] First char appears twice when searching in "Save as..." dialog in every application

2019-12-18 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Steps to reproduce:
- Open a document or web page in an application with a "Save as..." function. 
Possible examples I tried are LibreOffice Calc and Brave browser.
- Hit "Save as.."
- In the file list below, navigate to to a directory that is not empty.
- Select one of the files or directories to make sure the list has focus.
- Type some letters, e.g. "test".

Expected behavior:
- Search field appears to filter the list of files and directories.
- Search string is "test".

Actual behavior:
- Search field appears to filter the list of files and directories.
- Search string is "ttest", with the first letter appearing twice.

Note:
This only happens if you follow the instructions above.


Ubuntu 18.04.3 LTS
MATE desktop

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice-core 1:6.0.7-0ubuntu0.18.04.10
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Dec 16 18:42:16 2019
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2019-01-12 (337 days ago)
InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic third-party-packages
-- 
First char appears twice when searching in "Save as..." dialog in every 
application
https://bugs.launchpad.net/bugs/1856604
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 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