[Touch-packages] [Bug 2017898] Re: MESA 22.2 Regression Causes Kwin Crashes (Fix Available)

2023-05-06 Thread Kai Kasurinen
*** This bug is a duplicate of bug 2003339 ***
https://bugs.launchpad.net/bugs/2003339

** This bug has been marked a duplicate of bug 2003339
   kwin_x11: The X11 connection broke: I/O error (code 1)

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

Title:
  MESA 22.2 Regression Causes Kwin Crashes (Fix Available)

Status in mesa package in Ubuntu:
  New

Bug description:
  MESA 22.2 contains a malfunction which causes kwin to exit regularly /
  frequently, leaving the system without window management.

  This is a regression compared to MESA 22.1 and fixed again in MESA
  22.3.

  See following MESA bug:

  * https://gitlab.freedesktop.org/mesa/mesa/-/issues/7674
  * just for reference, corresponding KDE Bugtracker entry: 
https://bugs.kde.org/show_bug.cgi?id=461316

  Maybe the fix could be backported?

  It currently is something between inconvenient (for very technically
  savy users) and rendering the system unusable (for less technically
  savy users - suddenly, Window Management will be gone and switching
  windows, accessing panels, and controlling most applications even if
  they are in foreground at the time of a crash become impossible).

  ProblemType: Bug
  DistroRelease: KDE neon 22.04
  Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: kwin
  CurrentDesktop: KDE
  Date: Thu Apr 27 14:26:47 2023
  DistUpgraded: 2020-10-11 12:05:38,766 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.38, 5.19.0-40-generic, x86_64: installed
   virtualbox/6.1.38, 5.19.0-41-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:07bf]
 Subsystem: Dell GM107GLM [Quadro M1200 Mobile] [1028:07bf]
  MachineType: Dell Inc. Precision 5520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic 
root=/dev/mapper/ubuntu--vg--970-root ro resume=/dev/ubuntu-vg-970/swap 
fsck.mode=force rd.driver.blacklist=nouveau pcie_aspm=off
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: mesa
  UpgradeStatus: Upgraded to jammy on 2020-10-11 (928 days ago)
  dmi.bios.date: 11/10/2022
  dmi.bios.release: 1.31
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.31.0
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.31.0:bd11/10/2022:br1.31:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-0xneon+22.04+jammy+release+build8
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2017898/+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 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)

2023-03-06 Thread Kai Kasurinen
** Changed in: mesa (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  kwin_x11: The X11 connection broke: I/O error (code 1)

Status in KDE Base Workspace:
  Fix Released
Status in Mesa:
  Fix Released
Status in kwin package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in kwin package in Debian:
  New

Bug description:
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)

2023-02-28 Thread Kai Kasurinen
** Tags added: fixed-in-mesa-22.3.0

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

Title:
  kwin_x11: The X11 connection broke: I/O error (code 1)

Status in KDE Base Workspace:
  Fix Released
Status in Mesa:
  Fix Released
Status in kwin package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Committed
Status in kwin package in Debian:
  New

Bug description:
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)

2023-02-28 Thread Kai Kasurinen
** Changed in: kwin (Ubuntu)
   Status: Confirmed => Invalid

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

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

Title:
  kwin_x11: The X11 connection broke: I/O error (code 1)

Status in KDE Base Workspace:
  Fix Released
Status in Mesa:
  Fix Released
Status in kwin package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Committed
Status in kwin package in Debian:
  New

Bug description:
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 2005124] Re: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubunt

2023-02-04 Thread Kai Kasurinen
** Bug watch added: Debian Bug tracker #103
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=103

** Also affects: fontconfig (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=103
   Importance: Unknown
   Status: Unknown

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

Title:
  package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade:
  trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which
  is also in package kubuntu-settings-desktop 1:23.04.2

Status in fontconfig package in Ubuntu:
  Confirmed
Status in kubuntu-settings package in Ubuntu:
  Confirmed
Status in fontconfig package in Debian:
  Unknown

Bug description:
   I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: fontconfig-config 2.13.1-4.4ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.24.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Feb  4 05:59:53 2023
  DuplicateSignature:
   package:fontconfig-config:2.13.1-4.4ubuntu1
   Unpacking fontconfig-config (2.14.1-3ubuntu1) over (2.13.1-4.4ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-xn7IM4/015-fontconfig-config_2.14.1-3ubuntu1_amd64.deb 
(--unpack):
trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is 
also in package kubuntu-settings-desktop 1:23.04.2
  ErrorMessage: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', 
which is also in package kubuntu-settings-desktop 1:23.04.2
  InstallationDate: Installed on 2023-01-31 (3 days ago)
  InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230130)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 
3.11.1-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.19ubuntu3
   apt  2.5.5
  SourcePackage: fontconfig
  Title: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: 
trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in 
package kubuntu-settings-desktop 1:23.04.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124/+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 2005124] Re: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubunt

2023-02-04 Thread Kai Kasurinen
** Also affects: kubuntu-settings (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade:
  trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which
  is also in package kubuntu-settings-desktop 1:23.04.2

Status in fontconfig package in Ubuntu:
  Confirmed
Status in kubuntu-settings package in Ubuntu:
  Confirmed
Status in fontconfig package in Debian:
  Unknown

Bug description:
   I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: fontconfig-config 2.13.1-4.4ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.24.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Feb  4 05:59:53 2023
  DuplicateSignature:
   package:fontconfig-config:2.13.1-4.4ubuntu1
   Unpacking fontconfig-config (2.14.1-3ubuntu1) over (2.13.1-4.4ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-xn7IM4/015-fontconfig-config_2.14.1-3ubuntu1_amd64.deb 
(--unpack):
trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is 
also in package kubuntu-settings-desktop 1:23.04.2
  ErrorMessage: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', 
which is also in package kubuntu-settings-desktop 1:23.04.2
  InstallationDate: Installed on 2023-01-31 (3 days ago)
  InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230130)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 
3.11.1-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.19ubuntu3
   apt  2.5.5
  SourcePackage: fontconfig
  Title: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: 
trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in 
package kubuntu-settings-desktop 1:23.04.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124/+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 2003339] [NEW] kwin_x11: The X11 connection broke: I/O error (code 1)

2023-01-19 Thread Kai Kasurinen
Public bug reported:

...

** Affects: kdebase-workspace
 Importance: Unknown
 Status: Unknown

** Affects: mesa
 Importance: Unknown
 Status: Unknown

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

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

** Affects: kwin (Debian)
 Importance: Unknown
 Status: Unknown

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

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

** Also affects: kwin (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026404
   Importance: Unknown
   Status: Unknown

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #7674
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/7674

** Also affects: mesa via
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/7674
   Importance: Unknown
   Status: Unknown

** Bug watch added: KDE Bug Tracking System #461316
   https://bugs.kde.org/show_bug.cgi?id=461316

** Also affects: kdebase-workspace via
   https://bugs.kde.org/show_bug.cgi?id=461316
   Importance: Unknown
   Status: Unknown

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

Title:
  kwin_x11: The X11 connection broke: I/O error (code 1)

Status in KDE Base Workspace:
  Unknown
Status in Mesa:
  Unknown
Status in kwin package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in kwin package in Debian:
  Unknown

Bug description:
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 1943189] Re: "cannot refresh whilst network offline" bug

2021-09-21 Thread Kai Kasurinen
/lib/systemd/system/packagekit.service:13: Unknown key name 'Wants' in
section 'Service', ignoring.

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

Title:
  "cannot refresh whilst network offline" bug

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Focal:
  New
Status in packagekit source package in Hirsute:
  New
Status in packagekit source package in Impish:
  Fix Released

Bug description:
  Impact]

  In Ubuntu Impish, an issue has been noted in regards to refreshing
  packages in Plasma Discover for upgrade or installation. An error
  appears upon initialization of the Discover interface:

  "cannot refresh whilst network offline"

  This will happen regardless of if a system is online or not.

  I identified a race condition in which this is occurring on systems
  where packagekitd is initialized before the network service is online.
  This was a relatively easy fix and required adding one line to the
  packagekit.service file:

  Wants=network-online.target

  This ensures that packagekitd is not initialized prior to being
  online. If the 90 second deadline isn't met, then packagekitd will
  simply not start as a background process until the user connects to
  the network and initializes it via a graphical utility, such as with
  GNOME Software or Plasma Discover, both of which initialize
  packagekitd on a user level.

  The attached patch will easily apply the fix via normal Debian
  packaging methods.

  [Test Plan]

   * Install Kubuntu or Ubuntu Studio

   * While connected to network, Run Discover

   * Discover will complain about "cannot refresh whilst offline", which
  is being communicated from PackageKit. All functionality in Discover
  is hindered from this point forward. This is due to a hung packagekitd
  process which sees the network offline, even though this is false.

  [Where problems could occur]

   * packagekitd's systemd service will time-out after 90 seconds if
  systemd finds no network, which means any update notifications will
  not automatically start until packagekitd is manually started.
  Luckily, Discover and GNOME Software both attempt to start packagekitd
  for the user when run. I'd consider this to be expected behavior for
  an offline system. The fix is mostly to prevent the false-negative of
  the system being offline when it's really not.

  [Other Info]
   
   * This fix has been accepted upstream by the PackageKit maintainers as a 
sane workaround for when gio misbehaves or otherwise. It's a decent safety net. 
https://github.com/PackageKit/PackageKit/pull/506

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: packagekit 1.2.2-2ubuntu1 [modified: 
lib/systemd/system/packagekit.service]
  ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1
  Uname: Linux 5.13.0-14-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Sep  9 16:34:12 2021
  InstallationDate: Installed on 2021-03-20 (172 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  SourcePackage: packagekit
  UpgradeStatus: Upgraded to impish on 2021-06-13 (88 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1943189/+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 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings

2021-05-18 Thread Kai Kasurinen
Confirmed that patched [1][2] Qt fixes this bug.

[1] https://codereview.qt-project.org/c/qt/qtbase/+/328240
[2] 
https://launchpadlibrarian.net/539330399/qtbase-opensource-src_5.15.2+dfsg-5+0.drop.0_5.15.2+dfsg-5+0.drop.1.diff.gz

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

Title:
  kmimetypefinder5 misidentifies mimetype of python files containing
  certain strings

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Expected behavior:

  $ kmimetypefinder5 example.py 
  text/x-python3

  or

  $ kmimetypefinder5 example.py 
  text/x-python

  or

  $ kmimetypefinder5 example.py 
  text/plain

  Actual behavior:

  $ kmimetypefinder5 example.py 
  application/xhtml+xml

  Summary: Python scripts with a string containing HTML can be
  misidentified as HTML files by kmimetypefinder5.

  For example, this python script is identified as
  "application/xhtml+xml":

  #! /usr/bin/env python3
  example_string = \
  """\
  http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
  http://www.w3.org/1999/xhtml;>

  Example title


  Example body

  
  """
  print('Hello, world!')

  This difficulty is not shared by other mimetype identification tools.

  $ kmimetypefinder5 example.py 
  application/xhtml+xml
  $ cat example2.py #! /usr/bin/env python3
  print('Hello, world!')
  $ kmimetypefinder5 example2.py 
  text/x-python3
  $ mimetype 'example.py'
  example.py: text/x-python
  $ mimetype 'example2.py'
  example2.py: text/x-python
  $ file --mime-type 'example.py'
  example.py: text/plain
  $ file --mime-type 'example2.py'
  example2.py: text/plain

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  $ apt-cache policy kde-cli-tools
  kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
   *** 4:5.12.8-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   4:5.12.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
  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: KDE
  Date: Sun Dec 29 13:28:37 2019
  InstallationDate: Installed on 2018-12-12 (381 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: kde-cli-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1857824/+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 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"

2021-05-18 Thread Kai Kasurinen
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-
src/+bug/1857824/comments/12

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Invalid

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

Title:
  misidentifies .html file as Perl script when it contains JavaScript
  "use strict"

Status in shared-mime-info:
  Unknown
Status in qtbase-opensource-src package in Ubuntu:
  Invalid
Status in shared-mime-info package in Ubuntu:
  Fix Released
Status in shared-mime-info package in Debian:
  Confirmed

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+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 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"

2021-05-18 Thread Kai Kasurinen
shared-mime-info 2.0-1  Published in groovy-release on 2020-10-14

** Changed in: shared-mime-info (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  misidentifies .html file as Perl script when it contains JavaScript
  "use strict"

Status in shared-mime-info:
  Unknown
Status in qtbase-opensource-src package in Ubuntu:
  Invalid
Status in shared-mime-info package in Ubuntu:
  Fix Released
Status in shared-mime-info package in Debian:
  Confirmed

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+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 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings

2021-05-18 Thread Kai Kasurinen
specially:
"The spec hasn't changed, but I made the same mistake in xdgmime
(the reference implementation) and in Qt: when multiple globs match,
and the result from magic sniffing is unrelated to any of those globs,
then I used the magic result, but that's wrong, globs have priority
and one of them should be picked up."

and there is multiple glob matches:





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

Title:
  kmimetypefinder5 misidentifies mimetype of python files containing
  certain strings

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Expected behavior:

  $ kmimetypefinder5 example.py 
  text/x-python3

  or

  $ kmimetypefinder5 example.py 
  text/x-python

  or

  $ kmimetypefinder5 example.py 
  text/plain

  Actual behavior:

  $ kmimetypefinder5 example.py 
  application/xhtml+xml

  Summary: Python scripts with a string containing HTML can be
  misidentified as HTML files by kmimetypefinder5.

  For example, this python script is identified as
  "application/xhtml+xml":

  #! /usr/bin/env python3
  example_string = \
  """\
  http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
  http://www.w3.org/1999/xhtml;>

  Example title


  Example body

  
  """
  print('Hello, world!')

  This difficulty is not shared by other mimetype identification tools.

  $ kmimetypefinder5 example.py 
  application/xhtml+xml
  $ cat example2.py #! /usr/bin/env python3
  print('Hello, world!')
  $ kmimetypefinder5 example2.py 
  text/x-python3
  $ mimetype 'example.py'
  example.py: text/x-python
  $ mimetype 'example2.py'
  example2.py: text/x-python
  $ file --mime-type 'example.py'
  example.py: text/plain
  $ file --mime-type 'example2.py'
  example2.py: text/plain

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  $ apt-cache policy kde-cli-tools
  kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
   *** 4:5.12.8-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   4:5.12.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
  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: KDE
  Date: Sun Dec 29 13:28:37 2019
  InstallationDate: Installed on 2018-12-12 (381 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: kde-cli-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1857824/+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 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings

2021-05-18 Thread Kai Kasurinen
maybe fixed: https://codereview.qt-project.org/c/qt/qtbase/+/328240

** Package changed: kde-cli-tools (Ubuntu) => qtbase-opensource-src
(Ubuntu)

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

Title:
  kmimetypefinder5 misidentifies mimetype of python files containing
  certain strings

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Expected behavior:

  $ kmimetypefinder5 example.py 
  text/x-python3

  or

  $ kmimetypefinder5 example.py 
  text/x-python

  or

  $ kmimetypefinder5 example.py 
  text/plain

  Actual behavior:

  $ kmimetypefinder5 example.py 
  application/xhtml+xml

  Summary: Python scripts with a string containing HTML can be
  misidentified as HTML files by kmimetypefinder5.

  For example, this python script is identified as
  "application/xhtml+xml":

  #! /usr/bin/env python3
  example_string = \
  """\
  http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
  http://www.w3.org/1999/xhtml;>

  Example title


  Example body

  
  """
  print('Hello, world!')

  This difficulty is not shared by other mimetype identification tools.

  $ kmimetypefinder5 example.py 
  application/xhtml+xml
  $ cat example2.py #! /usr/bin/env python3
  print('Hello, world!')
  $ kmimetypefinder5 example2.py 
  text/x-python3
  $ mimetype 'example.py'
  example.py: text/x-python
  $ mimetype 'example2.py'
  example2.py: text/x-python
  $ file --mime-type 'example.py'
  example.py: text/plain
  $ file --mime-type 'example2.py'
  example2.py: text/plain

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  $ apt-cache policy kde-cli-tools
  kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
   *** 4:5.12.8-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   4:5.12.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
  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: KDE
  Date: Sun Dec 29 13:28:37 2019
  InstallationDate: Installed on 2018-12-12 (381 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: kde-cli-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1857824/+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 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"

2021-05-18 Thread Kai Kasurinen
** Package changed: kde-cli-tools (Ubuntu) => qtbase-opensource-src
(Ubuntu)

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

Title:
  misidentifies .html file as Perl script when it contains JavaScript
  "use strict"

Status in shared-mime-info:
  Unknown
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in shared-mime-info package in Ubuntu:
  Fix Committed
Status in shared-mime-info package in Debian:
  Confirmed

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+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 1902987] Re: package gstreamer1.0-plugins-bad 1.16.2-2.1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstcamerabin.so', which

2020-11-07 Thread Kai Kasurinen
gstreamer1.0-plugins-bad:amd64 (1.18.0-2+b1)

Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug. Please
report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Status: New => Invalid

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

Title:
  package gstreamer1.0-plugins-bad 1.16.2-2.1ubuntu1 failed to
  install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-
  gnu/gstreamer-1.0/libgstcamerabin.so', which is also in package
  gstreamer1.0-plugins-good:amd64 1.16.2-1ubuntu2

Status in gst-plugins-bad1.0 package in Ubuntu:
  Invalid

Bug description:
  package broken

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: gstreamer1.0-plugins-bad 1.16.2-2.1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Nov  3 17:03:38 2020
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstcamerabin.so', which is also in 
package gstreamer1.0-plugins-good:amd64 1.16.2-1ubuntu2
  InstallationDate: Installed on 2020-11-03 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: gst-plugins-bad1.0
  Title: package gstreamer1.0-plugins-bad 1.16.2-2.1ubuntu1 failed to 
install/upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstcamerabin.so', which is also in 
package gstreamer1.0-plugins-good:amd64 1.16.2-1ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1902987/+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 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings

2020-09-23 Thread Kai Kasurinen
testing with xdgmime [1] (reference implementation of the spec [2] and
also used tests on shared-mine-type):

> ../xdgmime/src/print-mime-data .
test.py:
name: text/x-python
data: application/xhtml+xml
file: application/xhtml+xml

> ../xdgmime/src/test-mime test.py
File "test.py" has a mime-type of application/xhtml+xml


[1] https://gitlab.freedesktop.org/xdg/xdgmime
[2] https://freedesktop.org/wiki/Specifications/shared-mime-info-spec/

--

kmimetypefinder5 is just a tiny wrapper over QMimeDatabase [3][4]. So
bug is likely on shared-mime-info or Qt implementation.

[3] 
https://github.com/KDE/kde-cli-tools/blob/master/kmimetypefinder/kmimetypefinder.cpp
[4] https://bugs.freedesktop.org/show_bug.cgi?id=99672

** Bug watch added: freedesktop.org Bugzilla #99672
   https://bugs.freedesktop.org/show_bug.cgi?id=99672

** Package changed: kde-cli-tools (Ubuntu) => shared-mime-info (Ubuntu)

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

Title:
  kmimetypefinder5 misidentifies mimetype of python files containing
  certain strings

Status in kde-cli-tools package in Ubuntu:
  New

Bug description:
  Expected behavior:

  $ kmimetypefinder5 example.py 
  text/x-python3

  or

  $ kmimetypefinder5 example.py 
  text/x-python

  or

  $ kmimetypefinder5 example.py 
  text/plain

  Actual behavior:

  $ kmimetypefinder5 example.py 
  application/xhtml+xml

  Summary: Python scripts with a string containing HTML can be
  misidentified as HTML files by kmimetypefinder5.

  For example, this python script is identified as
  "application/xhtml+xml":

  #! /usr/bin/env python3
  example_string = \
  """\
  http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
  http://www.w3.org/1999/xhtml;>

  Example title


  Example body

  
  """
  print('Hello, world!')

  This difficulty is not shared by other mimetype identification tools.

  $ kmimetypefinder5 example.py 
  application/xhtml+xml
  $ cat example2.py #! /usr/bin/env python3
  print('Hello, world!')
  $ kmimetypefinder5 example2.py 
  text/x-python3
  $ mimetype 'example.py'
  example.py: text/x-python
  $ mimetype 'example2.py'
  example2.py: text/x-python
  $ file --mime-type 'example.py'
  example.py: text/plain
  $ file --mime-type 'example2.py'
  example2.py: text/plain

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  $ apt-cache policy kde-cli-tools
  kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
   *** 4:5.12.8-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   4:5.12.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
  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: KDE
  Date: Sun Dec 29 13:28:37 2019
  InstallationDate: Installed on 2018-12-12 (381 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: kde-cli-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1857824/+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 1654839] Re: shared-mime-info detects all binary files as shared libraries

2020-09-23 Thread Kai Kasurinen
** Bug watch added: gitlab.freedesktop.org/xdg/shared-mime-info/-/issues #11
   https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/11

** Also affects: shared-mime-info via
   https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/11
   Importance: Unknown
   Status: Unknown

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

Title:
  shared-mime-info detects all binary files as shared libraries

Status in shared-mime-info:
  Unknown
Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  Initially I reported bug to KDE but it's a shared-mime-info issue.
  https://bugs.kde.org/show_bug.cgi?id=373220

  All binary files are detected as application/x-sharedlib but should be
  application/x-executable.

  This started to happen in Kubuntu 16.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1654839/+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 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"

2020-09-23 Thread Kai Kasurinen
probably fixed on shared-mime-info 2.0:
https://gitlab.freedesktop.org/xdg/shared-mime-info/-/commit/18bb7cfc6c43d710ecf60339b5dd9bd19c297cdf

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

Title:
  misidentifies .html file as Perl script when it contains JavaScript
  "use strict"

Status in shared-mime-info:
  Unknown
Status in kde-cli-tools package in Ubuntu:
  New
Status in shared-mime-info package in Ubuntu:
  New
Status in shared-mime-info package in Debian:
  Unknown

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+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 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings

2020-09-23 Thread Kai Kasurinen
> dpkg -S /usr/bin/mimetype
libfile-mimeinfo-perl: /usr/bin/mimetype
> /usr/bin/mimetype --magic-only foo.py
foo.py: application/xhtml+xml

** Package changed: kde-cli-tools (Ubuntu) => shared-mime-info (Ubuntu)

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

Title:
  kmimetypefinder5 misidentifies mimetype of python files containing
  certain strings

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  Expected behavior:

  $ kmimetypefinder5 example.py 
  text/x-python3

  or

  $ kmimetypefinder5 example.py 
  text/x-python

  or

  $ kmimetypefinder5 example.py 
  text/plain

  Actual behavior:

  $ kmimetypefinder5 example.py 
  application/xhtml+xml

  Summary: Python scripts with a string containing HTML can be
  misidentified as HTML files by kmimetypefinder5.

  For example, this python script is identified as
  "application/xhtml+xml":

  #! /usr/bin/env python3
  example_string = \
  """\
  http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
  http://www.w3.org/1999/xhtml;>

  Example title


  Example body

  
  """
  print('Hello, world!')

  This difficulty is not shared by other mimetype identification tools.

  $ kmimetypefinder5 example.py 
  application/xhtml+xml
  $ cat example2.py #! /usr/bin/env python3
  print('Hello, world!')
  $ kmimetypefinder5 example2.py 
  text/x-python3
  $ mimetype 'example.py'
  example.py: text/x-python
  $ mimetype 'example2.py'
  example2.py: text/x-python
  $ file --mime-type 'example.py'
  example.py: text/plain
  $ file --mime-type 'example2.py'
  example2.py: text/plain

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  $ apt-cache policy kde-cli-tools
  kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
   *** 4:5.12.8-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   4:5.12.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
  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: KDE
  Date: Sun Dec 29 13:28:37 2019
  InstallationDate: Installed on 2018-12-12 (381 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: kde-cli-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1857824/+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 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"

2020-09-23 Thread Kai Kasurinen
> dpkg -S /usr/bin/mimetype
libfile-mimeinfo-perl: /usr/bin/mimetype
> /usr/bin/mimetype --magic-only foo.html
foo.html: application/x-perl

** Changed in: shared-mime-info (Ubuntu)
   Status: Invalid => New

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

Title:
  misidentifies .html file as Perl script when it contains JavaScript
  "use strict"

Status in shared-mime-info:
  Unknown
Status in kde-cli-tools package in Ubuntu:
  New
Status in shared-mime-info package in Ubuntu:
  New
Status in shared-mime-info package in Debian:
  Unknown

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+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 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings

2020-09-22 Thread Kai Kasurinen
** Package changed: kde-cli-tools (Ubuntu) => shared-mime-info (Ubuntu)

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

Title:
  kmimetypefinder5 misidentifies mimetype of python files containing
  certain strings

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  Expected behavior:

  $ kmimetypefinder5 example.py 
  text/x-python3

  or

  $ kmimetypefinder5 example.py 
  text/x-python

  or

  $ kmimetypefinder5 example.py 
  text/plain

  Actual behavior:

  $ kmimetypefinder5 example.py 
  application/xhtml+xml

  Summary: Python scripts with a string containing HTML can be
  misidentified as HTML files by kmimetypefinder5.

  For example, this python script is identified as
  "application/xhtml+xml":

  #! /usr/bin/env python3
  example_string = \
  """\
  http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
  http://www.w3.org/1999/xhtml;>

  Example title


  Example body

  
  """
  print('Hello, world!')

  This difficulty is not shared by other mimetype identification tools.

  $ kmimetypefinder5 example.py 
  application/xhtml+xml
  $ cat example2.py #! /usr/bin/env python3
  print('Hello, world!')
  $ kmimetypefinder5 example2.py 
  text/x-python3
  $ mimetype 'example.py'
  example.py: text/x-python
  $ mimetype 'example2.py'
  example2.py: text/x-python
  $ file --mime-type 'example.py'
  example.py: text/plain
  $ file --mime-type 'example2.py'
  example2.py: text/plain

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  $ apt-cache policy kde-cli-tools
  kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
   *** 4:5.12.8-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   4:5.12.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
  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: KDE
  Date: Sun Dec 29 13:28:37 2019
  InstallationDate: Installed on 2018-12-12 (381 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: kde-cli-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1857824/+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 1890716] Re: kmimetypefinder5 *.html reports wrong type

2020-09-22 Thread Kai Kasurinen
** Changed in: shared-mime-info (Ubuntu)
   Status: Invalid => New

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

** Also affects: shared-mime-info (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887709
   Importance: Unknown
   Status: Unknown

** Summary changed:

- kmimetypefinder5 *.html reports wrong type
+ misidentifies .html file as Perl script when it contains JavaScript "use 
strict"

** Bug watch added: gitlab.freedesktop.org/xdg/shared-mime-info/-/issues #80
   https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/80

** Also affects: shared-mime-info via
   https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/80
   Importance: Unknown
   Status: Unknown

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

Title:
  misidentifies .html file as Perl script when it contains JavaScript
  "use strict"

Status in shared-mime-info:
  Unknown
Status in shared-mime-info package in Ubuntu:
  New
Status in shared-mime-info package in Debian:
  Unknown

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+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 1775457] Re: /usr/bin/pip3:ImportError:/usr/bin/pip3@9

2020-08-31 Thread Kai Kasurinen
** Bug watch added: github.com/pypa/pip/issues #5599
   https://github.com/pypa/pip/issues/5599

** Also affects: pip via
   https://github.com/pypa/pip/issues/5599
   Importance: Unknown
   Status: Unknown

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

Title:
  /usr/bin/pip3:ImportError:/usr/bin/pip3@9

Status in pip:
  Unknown
Status in apport package in Ubuntu:
  New
Status in python-pip package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
python-pip.  This problem was most recently seen with package version 
9.0.1-2.3~ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/4e26eab10247fe3383fb8c84ca8a0d8eb21abc83 
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/pip/+bug/1775457/+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 1593749] Re: puppet apply with pip provider gives 403 error

2020-08-30 Thread Kai Kasurinen
** Package changed: dbus (Ubuntu) => puppet (Ubuntu)

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

Title:
  puppet apply with pip provider gives 403 error

Status in puppet package in Ubuntu:
  New

Bug description:
  Since some time on 16/06/2016 Puppet manifests that use the "pip"
  provider to manage Python packages are failing with a 403 error, on
  (at least) Ubuntu 14.04.4 LTS, when processed using "puppet apply...".

  puppet version is 3.4.3-1ubuntu1.1
  python-pip version is 1.5.4-1ubuntu3
  python version is 2.7.5-5ubuntu3

  On the command line:

  pip install --upgrade rarfile

  returns:

  Requirement already up-to-date: rarfile in 
/usr/local/lib/python2.7/dist-packages
  Cleaning up...

  However, creating init.pp containing:

  package { 'rarfile':
ensure   => 'latest',
provider => 'pip',
  }

  and running:

  puppet apply ./init.pp

  returns:

  Notice: Compiled catalog for narsaq.isys.bris.ac.uk in environment production 
in 0.01 seconds
  Error: Could not get latest version: HTTP-Error: 403 Must access using HTTPS 
instead of HTTP
  Error: /Stage[main]/Main/Package[rarfile]/ensure: change from 2.8 to latest 
failed: Could not get latest version: HTTP-Error: 403 Must access using HTTPS 
instead of HTTP
  Notice: Finished catalog run in 1.05 seconds

  This was previously working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1593749/+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 1800723] Re: Missing package python3.7-pip

2020-08-30 Thread Kai Kasurinen
$ python3.7 -m pip --version
pip 9.0.1 from /usr/lib/python3/dist-packages (python 3.7)

also python3.7 -m pip install ... works fine


** Changed in: python-pip (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Missing package python3.7-pip

Status in python-pip package in Ubuntu:
  Invalid
Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  There appears to be no way to get "pip" or "python3.7 -m pip" to work
  after installing python3.7 using "apt install python3.7". I expected
  to be able to install a "python3.7-pip" package similar to the other
  "python3.7-*" packages but I couldn't find one.

  This problem appears in a clean install of 18.04 as well as 18.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1800723/+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 1800723] Re: Missing package python3.7-pip

2020-08-30 Thread Kai Kasurinen
** Changed in: python3-defaults (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Missing package python3.7-pip

Status in python-pip package in Ubuntu:
  Invalid
Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  There appears to be no way to get "pip" or "python3.7 -m pip" to work
  after installing python3.7 using "apt install python3.7". I expected
  to be able to install a "python3.7-pip" package similar to the other
  "python3.7-*" packages but I couldn't find one.

  This problem appears in a clean install of 18.04 as well as 18.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1800723/+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 1775457] Re: /usr/bin/pip3:ImportError:/usr/bin/pip3@9

2020-08-29 Thread Kai Kasurinen
** Changed in: python-pip (Ubuntu)
   Status: New => Invalid

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

Title:
  /usr/bin/pip3:ImportError:/usr/bin/pip3@9

Status in apport package in Ubuntu:
  New
Status in python-pip package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
python-pip.  This problem was most recently seen with package version 
9.0.1-2.3~ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/4e26eab10247fe3383fb8c84ca8a0d8eb21abc83 
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/apport/+bug/1775457/+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 1892798] Re: systemd package missing resolvconf(8) compatibility symlink, and a Provides: resolvconf

2020-08-29 Thread Kai Kasurinen
** Bug watch added: Debian Bug tracker #939904
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939904

** Also affects: systemd (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939904
   Importance: Unknown
   Status: Unknown

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

Title:
  systemd package missing resolvconf(8) compatibility symlink, and a
  Provides: resolvconf

Status in systemd package in Ubuntu:
  Won't Fix
Status in wireguard package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Unknown

Bug description:
  By default Ubuntu now uses systemd to manage the nameservers in
  resolv.conf, so resolvconf and openresolv seem to be redundant.
  However, it appears that systemd's resolvectl is compatable with
  resolvconf style commands if symlinked as resolvconf.

  I'm not really sure how deb packaging works, but if it possible to
  check for the resolvconf command, and if not found just symlink
  /usr/bin/resolvectl to /usr/sbin/resolvconf then wg-quick will work
  without additional packages.

  See
  
https://manpages.ubuntu.com/manpages/focal/man1/resolvectl.1#compatibility%20with%20resolvconf(8)
  for more info.

  Apologies if there is a better place to direct this info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+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 1891260] Re: iptables doesn't work with kernel 5.8

2020-08-12 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1891020 ***
https://bugs.launchpad.net/bugs/1891020

** This bug has been marked a duplicate of bug 1891020
   No IPv4 iptable kernel module can be loaded

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

Title:
  iptables doesn't work with kernel 5.8

Status in iptables package in Ubuntu:
  New
Status in ufw package in Ubuntu:
  New

Bug description:
  Hi dear maintainers,
  iptables doesn't work since kernel 5.8 updated. Maybe you could update this 
package to 1.8.5 to fix this issue?

  iptables v1.8.4 (legacy): can't initialize iptables table `filter': Bad 
address
  Perhaps iptables or your kernel needs to be upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: iptables 1.8.4-3ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-12.13-generic 5.8.0-rc7
  Uname: Linux 5.8.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 12 10:54:29 2020
  InstallationDate: Installed on 2020-04-13 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: iptables
  UpgradeStatus: Upgraded to groovy on 2020-06-02 (70 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1891260/+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 1432211] Re: package libc6-dev-i386 (not installed) failed to install/upgrade: trying to overwrite '/usr/include/bits', which is also in package libc6-dev-amd64 2.19-0ubuntu6.6

2020-08-11 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1408173 ***
https://bugs.launchpad.net/bugs/1408173

** This bug has been marked a duplicate of bug 1408173
   package libc6-dev-i386 (not installed) failed to install/upgrade: trying to 
overwrite '/usr/include/bits', which is also in package libc6-dev-amd64 
2.19-0ubuntu6.4

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

Title:
  package libc6-dev-i386 (not installed) failed to install/upgrade:
  trying to overwrite '/usr/include/bits', which is also in package
  libc6-dev-amd64 2.19-0ubuntu6.6

Status in eglibc package in Ubuntu:
  Confirmed

Bug description:
  I don't know what I'm doing. I'm just trying to get steam-launcher
  working!

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libc6-dev-i386 (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Sat Mar 14 14:00:19 2015
  DuplicateSignature: package:libc6-dev-i386:(not installed):trying to 
overwrite '/usr/include/bits', which is also in package libc6-dev-amd64 
2.19-0ubuntu6.6
  ErrorMessage: trying to overwrite '/usr/include/bits', which is also in 
package libc6-dev-amd64 2.19-0ubuntu6.6
  InstallationDate: Installed on 2015-03-14 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: eglibc
  Title: package libc6-dev-i386 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/include/bits', which is also in package 
libc6-dev-amd64 2.19-0ubuntu6.6
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1432211/+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 1588596] Re: package libc6-dev-i386 (not installed) failed to install/upgrade: trying to overwrite '/usr/include/bits', which is also in package libc6-dev-amd64 2.19-0ubuntu6.9

2020-08-11 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1408173 ***
https://bugs.launchpad.net/bugs/1408173

** This bug has been marked a duplicate of bug 1408173
   package libc6-dev-i386 (not installed) failed to install/upgrade: trying to 
overwrite '/usr/include/bits', which is also in package libc6-dev-amd64 
2.19-0ubuntu6.4

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

Title:
  package libc6-dev-i386 (not installed) failed to install/upgrade:
  trying to overwrite '/usr/include/bits', which is also in package
  libc6-dev-amd64 2.19-0ubuntu6.9

Status in eglibc package in Ubuntu:
  New

Bug description:
  $ lsb_release -a
  LSB Version:  
core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04
  Codename: trusty
  

  $ sudo apt-cache policy
  Package files:
   100 /var/lib/dpkg/status
   release a=now
   500 https://deb.opera.com/opera-stable/ stable/non-free i386 Packages
   release o=Opera Software ASA,a=stable,n=stable,l=The Opera web 
browser,c=non-free
   origin deb.opera.com
   500 https://deb.opera.com/opera-stable/ stable/non-free amd64 Packages
   release o=Opera Software ASA,a=stable,n=stable,l=The Opera web 
browser,c=non-free
   origin deb.opera.com
   500 http://dl.google.com/linux/chrome/deb/ stable/main amd64 Packages
   release v=1.0,o=Google, Inc.,a=stable,n=stable,l=Google,c=main
   origin dl.google.com
   500 https://apt.dockerproject.org/repo/ ubuntu-trusty/main i386 Packages
   release o=Docker,a=ubuntu-trusty,n=ubuntu-trusty,l=Docker APT 
Repository,c=main
   origin apt.dockerproject.org
   500 https://apt.dockerproject.org/repo/ ubuntu-trusty/main amd64 Packages
   release o=Docker,a=ubuntu-trusty,n=ubuntu-trusty,l=Docker APT 
Repository,c=main
   origin apt.dockerproject.org
   500 http://archive.ubuntu.com/ubuntu/ trusty-updates/universe Translation-en
   500 http://archive.ubuntu.com/ubuntu/ trusty-updates/restricted 
Translation-en
   500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main Translation-en
   500 http://archive.ubuntu.com/ubuntu/ trusty-updates/universe i386 Packages
   release v=14.04,o=Ubuntu,a=trusty-updates,n=trusty,l=Ubuntu,c=universe
   origin archive.ubuntu.com
   500 http://archive.ubuntu.com/ubuntu/ trusty-updates/restricted i386 Packages
   release v=14.04,o=Ubuntu,a=trusty-updates,n=trusty,l=Ubuntu,c=restricted
   origin archive.ubuntu.com
   500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages
   release v=14.04,o=Ubuntu,a=trusty-updates,n=trusty,l=Ubuntu,c=main
   origin archive.ubuntu.com
   500 http://archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages
   release v=14.04,o=Ubuntu,a=trusty-updates,n=trusty,l=Ubuntu,c=universe
   origin archive.ubuntu.com
   500 http://archive.ubuntu.com/ubuntu/ trusty-updates/restricted amd64 
Packages
   release v=14.04,o=Ubuntu,a=trusty-updates,n=trusty,l=Ubuntu,c=restricted
   origin archive.ubuntu.com
   500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
   release v=14.04,o=Ubuntu,a=trusty-updates,n=trusty,l=Ubuntu,c=main
   origin archive.ubuntu.com
   500 http://security.ubuntu.com/ubuntu/ trusty-security/universe 
Translation-en
   500 http://security.ubuntu.com/ubuntu/ trusty-security/restricted 
Translation-en
   500 http://security.ubuntu.com/ubuntu/ trusty-security/main Translation-en
   500 http://security.ubuntu.com/ubuntu/ trusty-security/universe i386 Packages
   release v=14.04,o=Ubuntu,a=trusty-security,n=trusty,l=Ubuntu,c=universe
   origin security.ubuntu.com
   500 http://security.ubuntu.com/ubuntu/ trusty-security/restricted i386 
Packages
   release v=14.04,o=Ubuntu,a=trusty-security,n=trusty,l=Ubuntu,c=restricted
   origin security.ubuntu.com
   500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 Packages
   release v=14.04,o=Ubuntu,a=trusty-security,n=trusty,l=Ubuntu,c=main
   origin security.ubuntu.com
   500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 
Packages
   release v=14.04,o=Ubuntu,a=trusty-security,n=trusty,l=Ubuntu,c=universe
   origin security.ubuntu.com
   500 http://security.ubuntu.com/ubuntu/ trusty-security/restricted amd64 
Packages
   release v=14.04,o=Ubuntu,a=trusty-security,n=trusty,l=Ubuntu,c=restricted
   origin security.ubuntu.com
   500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
   release 

[Touch-packages] [Bug 1620459] Re: package bash-completion 1:2.1-4ubuntu0.2 failed to install/upgrade: trying to overwrite '/usr/share/bash-completion/completions/apt', which is also in package apt 1.

2020-08-11 Thread Kai Kasurinen
** Also affects: apt (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  package bash-completion 1:2.1-4ubuntu0.2 failed to install/upgrade:
  trying to overwrite '/usr/share/bash-completion/completions/apt',
  which is also in package apt 1.0.1ubuntu2.14

Status in apt package in Ubuntu:
  Confirmed
Status in bash-completion package in Ubuntu:
  Confirmed

Bug description:
  I updated my system from 14.XX LTS to 16.04 LTS and now my updates
  will not finish

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bash-completion 1:2.1-4ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Mon Sep  5 23:17:46 2016
  DuplicateSignature:
   package:bash-completion:1:2.1-4ubuntu0.2
   Unpacking bash-completion (1:2.1-4.2ubuntu1.1) over (1:2.1-4ubuntu0.2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/bash-completion_1%3a2.1-4.2ubuntu1.1_all.deb (--unpack):
trying to overwrite '/usr/share/bash-completion/completions/apt', which is 
also in package apt 1.0.1ubuntu2.14
  ErrorMessage: trying to overwrite 
'/usr/share/bash-completion/completions/apt', which is also in package apt 
1.0.1ubuntu2.14
  InstallationDate: Installed on 2015-04-23 (501 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: bash-completion
  Title: package bash-completion 1:2.1-4ubuntu0.2 failed to install/upgrade: 
trying to overwrite '/usr/share/bash-completion/completions/apt', which is also 
in package apt 1.0.1ubuntu2.14
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1620459/+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 1675246] Re: package apt 1.0.10.2ubuntu3 failed to install/upgrade: trying to overwrite '/usr/share/bash-completion/completions/apt', which is also in package bash-completion 1:2

2020-08-11 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1620459 ***
https://bugs.launchpad.net/bugs/1620459

** This bug has been marked a duplicate of bug 1620459
   package bash-completion 1:2.1-4ubuntu0.2 failed to install/upgrade: trying 
to overwrite '/usr/share/bash-completion/completions/apt', which is also in 
package apt 1.0.1ubuntu2.14

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

Title:
  package apt 1.0.10.2ubuntu3 failed to install/upgrade: trying to
  overwrite '/usr/share/bash-completion/completions/apt', which is also
  in package bash-completion 1:2.1-4.1ubuntu2

Status in apt package in Ubuntu:
  New

Bug description:
  sandy@hostsandy:~$ sudo apt-get -f install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following extra packages will be installed:
apt
  Suggested packages:
apt-doc aptitude synaptic wajig
  The following packages will be upgraded:
apt
  1 upgraded, 0 newly installed, 0 to remove and 2140 not upgraded.
  1 not fully installed or removed.
  Need to get 0 B/1.045 kB of archives.
  After this operation, 108 kB of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  apt-extracttemplates: /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0: no 
version information available (required by apt-extracttemplates)
  apt-extracttemplates: relocation error: apt-extracttemplates: symbol 
_Z19DispatchCommandLineR11CommandLineRKSt6vectorINS_8DispatchESaIS2_EE, version 
APTPRIVATE_0.0 not defined in file libapt-private.so.0.0 with link time 
reference
  debconf: apt-extracttemplates failed: No such file or directory
  (Reading database ... 1445526 files and directories currently installed.)
  Preparing to unpack .../archives/apt_1.3.1_amd64.deb ...
  Unpacking apt (1.3.1) over (1.0.10.2ubuntu3) ...
  dpkg: error processing archive /var/cache/apt/archives/apt_1.3.1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/share/bash-completion/completions/apt', which is 
also in package bash-completion 1:2.1-4.1ubuntu2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Reinstalling /etc/apt/apt.conf.d/20changelog that was moved away
  Reinstalling /etc/cron.daily/apt that was moved away
  Processing triggers for libc-bin (2.21-0ubuntu4.3) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/apt_1.3.1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: apt 1.0.10.2ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  AptOrdering:
   apt: Install
   apt: Configure
   apt-utils: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Mar 23 10:10:31 2017
  DpkgTerminalLog:
   Preparing to unpack .../archives/apt_1.3.1_amd64.deb ...
   Unpacking apt (1.3.1) over (1.0.10.2ubuntu3) ...
   dpkg: error processing archive /var/cache/apt/archives/apt_1.3.1_amd64.deb 
(--unpack):
trying to overwrite '/usr/share/bash-completion/completions/apt', which is 
also in package bash-completion 1:2.1-4.1ubuntu2
  DuplicateSignature: package:apt:1.0.10.2ubuntu3:trying to overwrite 
'/usr/share/bash-completion/completions/apt', which is also in package 
bash-completion 1:2.1-4.1ubuntu2
  ErrorMessage: trying to overwrite 
'/usr/share/bash-completion/completions/apt', which is also in package 
bash-completion 1:2.1-4.1ubuntu2
  InstallationDate: Installed on 2014-04-02 (1085 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu3
  SourcePackage: apt
  Title: package apt 1.0.10.2ubuntu3 failed to install/upgrade: trying to 
overwrite '/usr/share/bash-completion/completions/apt', which is also in 
package bash-completion 1:2.1-4.1ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1675246/+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 1750955] Re: package libopencv-dev 2.4.9.1+dfsg-1.5ubuntu1 failed to install/upgrade: trying to overwrite '/usr/include/opencv/cvaux.hpp', which is also in package libcvaux-dev:a

2020-08-09 Thread Kai Kasurinen
libopencv-dev (3.3.1)

Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug. Please
report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

** Changed in: opencv (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package libopencv-dev 2.4.9.1+dfsg-1.5ubuntu1 failed to
  install/upgrade: trying to overwrite '/usr/include/opencv/cvaux.hpp',
  which is also in package libcvaux-dev:amd64 2.4.9.1+dfsg-1.5ubuntu1

Status in opencv package in Ubuntu:
  Invalid

Bug description:
  Unable to update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libopencv-dev 2.4.9.1+dfsg-1.5ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Feb 21 21:30:46 2018
  DpkgTerminalLog:
   Preparing to unpack .../libopencv-dev_3.3.1_amd64.deb ...
   Unpacking libopencv-dev (3.3.1) over (2.4.9.1+dfsg-1.5ubuntu1) ...
   dpkg: error processing archive 
/home/bruno/Downloads/jetpack/jetpack_download/libopencv-dev_3.3.1_amd64.deb 
(--unpack):
trying to overwrite '/usr/include/opencv/cvaux.hpp', which is also in 
package libcvaux-dev:amd64 2.4.9.1+dfsg-1.5ubuntu1
  DuplicateSignature:
   package:libopencv-dev:2.4.9.1+dfsg-1.5ubuntu1
   Unpacking libopencv-dev (3.3.1) over (2.4.9.1+dfsg-1.5ubuntu1) ...
   dpkg: error processing archive 
/home/bruno/Downloads/jetpack/jetpack_download/libopencv-dev_3.3.1_amd64.deb 
(--unpack):
trying to overwrite '/usr/include/opencv/cvaux.hpp', which is also in 
package libcvaux-dev:amd64 2.4.9.1+dfsg-1.5ubuntu1
  ErrorMessage: trying to overwrite '/usr/include/opencv/cvaux.hpp', which is 
also in package libcvaux-dev:amd64 2.4.9.1+dfsg-1.5ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: opencv
  Title: package libopencv-dev 2.4.9.1+dfsg-1.5ubuntu1 failed to 
install/upgrade: trying to overwrite '/usr/include/opencv/cvaux.hpp', which is 
also in package libcvaux-dev:amd64 2.4.9.1+dfsg-1.5ubuntu1
  UpgradeStatus: Upgraded to xenial on 2018-02-14 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1750955/+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 1710613] Re: package systemd-services (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in package systemd 232-

2020-08-09 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1803691 ***
https://bugs.launchpad.net/bugs/1803691

** This bug has been marked a duplicate of bug 1803691
   package systemd-services (not installed) failed to install/upgrade: trying 
to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in package 
systemd 237-3ubuntu10.6

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

Title:
  package systemd-services (not installed) failed to install/upgrade:
  trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is
  also in package systemd 232-21ubuntu5

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  None

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: systemd-services (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Mon Aug 14 14:03:19 2017
  ErrorMessage: trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', 
which is also in package systemd 232-21ubuntu5
  InstallationDate: Installed on 2017-08-11 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: systemd
  Title: package systemd-services (not installed) failed to install/upgrade: 
trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in 
package systemd 232-21ubuntu5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710613/+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 1881715] Re: package libopencv-dnn-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/include/opencv4/opencv2/dnn/all_layers.hpp', which is also in package

2020-08-08 Thread Kai Kasurinen
libopencv-dev 4.1.1-2-gd5a58aa75

Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug. Please
report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

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

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

Title:
  package libopencv-dnn-dev (not installed) failed to install/upgrade:
  trying to overwrite '/usr/include/opencv4/opencv2/dnn/all_layers.hpp',
  which is also in package libopencv-dev 4.1.1-2-gd5a58aa75

Status in opencv package in Ubuntu:
  Invalid

Bug description:
  Didn't know what exactly happened. I'm using the system mostly for ML
  purposes with Nvidia drivers and ML frameworks. Upgraded from 18.04 to
  20.04 today and ran into some errors with libopencv.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libopencv-dnn-dev (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jun  2 08:58:20 2020
  ErrorMessage: trying to overwrite 
'/usr/include/opencv4/opencv2/dnn/all_layers.hpp', which is also in package 
libopencv-dev 4.1.1-2-gd5a58aa75
  InstallationDate: Installed on 2018-07-07 (695 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  2.0.2ubuntu0.1
  SourcePackage: opencv
  Title: package libopencv-dnn-dev (not installed) failed to install/upgrade: 
trying to overwrite '/usr/include/opencv4/opencv2/dnn/all_layers.hpp', which is 
also in package libopencv-dev 4.1.1-2-gd5a58aa75
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1881715/+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 1877238] Re: package libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: попытка перезаписать общий «/usr/share/

2020-08-08 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1881502 ***
https://bugs.launchpad.net/bugs/1881502

** This bug has been marked a duplicate of bug 1881502
   package libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: 
usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: trying to 
overwrite shared '/usr/share/glvnd/egl_vendor.d/50_mesa.json', which is 
different from other instances of package libegl-mesa0:armhf

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

Title:
  package libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified:
  usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade:
  попытка перезаписать общий
  «/usr/share/glvnd/egl_vendor.d/50_mesa.json», который отличается от
  других экземпляров пакета libegl-mesa0:armhf

Status in mesa package in Ubuntu:
  New

Bug description:
  -

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: 
usr/share/glvnd/egl_vendor.d/50_mesa.json]
  Uname: Linux 4.9.140-tegra aarch64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: arm64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu May  7 09:53:41 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ErrorMessage: попытка перезаписать общий 
«/usr/share/glvnd/egl_vendor.d/50_mesa.json», который отличается от других 
экземпляров пакета libegl-mesa0:armhf
  GraphicsCard:
   
  ProcKernelCmdLine: tegraid=21.1.2.0.0 ddr_die=4096M@2048M section=512M 
memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 
touch_id=0@63 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 
debug_uartport=lsport,2 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 
usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff78 core_edp_mv=1075 
core_edp_ma=4000  root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 
console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0
root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 
console=tty0 fbcon=map:0 net.ifnames=0 quiet
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12
  SourcePackage: mesa
  Title: package libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: 
usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: попытка 
перезаписать общий «/usr/share/glvnd/egl_vendor.d/50_mesa.json», который 
отличается от других экземпляров пакета libegl-mesa0:armhf
  UpgradeStatus: No upgrade log present (probably fresh install)
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1877238/+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 1890854] Re: Conflict with python2

2020-08-07 Thread Kai Kasurinen
** Bug watch added: Debian Bug tracker #968046
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968046

** Also affects: dh-python (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968046
   Importance: Unknown
   Status: Unknown

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

Title:
  Conflict with python2

Status in dh-python package in Ubuntu:
  New
Status in dh-python package in Debian:
  Unknown

Bug description:
  During a package update in groovy I got this error message:

  Unpacking dh-python (4.20200804ubuntu1) over (4.20200315ubuntu1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-JUlowz/00-dh-python_4.20200804ubuntu1_all.deb (--unpack):
   trying to overwrite '/usr/share/debhelper/autoscripts/postinst-pycompile', 
which is also in package python2 2.7.17-2ubuntu4
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

  +++

  Errors were encountered while processing:
   /tmp/apt-dpkg-install-JUlowz/00-dh-python_4.20200804ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1890854/+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 1340177] Re: Python3-dbus attribute error, usb creator pendrive formatting.

2020-08-06 Thread Kai Kasurinen
** Package changed: dbus-python (Ubuntu) => usb-creator (Ubuntu)

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

Title:
  Python3-dbus attribute error, usb creator pendrive formatting.

Status in usb-creator package in Ubuntu:
  New

Bug description:
  Python3-dbus attribute error, usb creator pendrive formatting. 14.04
  Trusty Tahr.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1340177/+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 1760801] Re: package python3-dbus 1.2.0-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

2020-08-06 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1768379 ***
https://bugs.launchpad.net/bugs/1768379

** This bug has been marked a duplicate of bug 1768379
   python3-minimal should predepend on versioned version of python3-minimal

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

Title:
  package python3-dbus 1.2.0-3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 127

Status in dbus-python package in Ubuntu:
  Confirmed

Bug description:
  this error appeared during Ubuntu startup

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3-dbus 1.2.0-3
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Mar 26 14:45:49 2018
  DuplicateSignature:
   package:python3-dbus:1.2.0-3
   Setting up python3-apt (1.1.0~beta1ubuntu0.16.04.1) ...
   /var/lib/dpkg/info/python3-apt.postinst: 6: 
/var/lib/dpkg/info/python3-apt.postinst: py3compile: not found
   dpkg: error processing package python3-apt (--configure):
subprocess installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2018-03-07 (26 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: dbus-python
  Title: package python3-dbus 1.2.0-3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-python/+bug/1760801/+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 1669932] Re: package python-dbus 1.2.0-3 failed to install/upgrade: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました

2020-08-06 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package python-dbus 1.2.0-3 failed to install/upgrade: サブプロセス
  インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました

Status in dbus-python package in Ubuntu:
  New

Bug description:
  I don't know what exactly the problem is, but problem report is always
  displayed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-dbus 1.2.0-3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Sat Mar  4 00:08:10 2017
  ErrorMessage: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました
  InstallationDate: Installed on 2017-01-22 (40 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: dbus-python
  Title: package python-dbus 1.2.0-3 failed to install/upgrade: サブプロセス 
インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-python/+bug/1669932/+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 1405199] Re: Using open() on an optical drive with its tray open will close the tray

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  Using open() on an optical drive with its tray open will close the
  tray

Status in systemd package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 15.04 dev with udev 218-2ubuntu3 and if the tray of
  an optical drive is open and open() will then be used on the device
  file the tray will be closed. Here is an example code (compiled with
  "gcc -Wall -pedantic -o test test.c"):

  #include 

  int main()
  {
open("/dev/sr0", O_EXCL);
return 0;
  }

  
  Normally I would expect that the tray doesn't get closed so I'm assuming an 
udev rule causes this behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1405199/+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 1456338] Re: USB floppy drive is running without floppy

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  USB floppy drive is running without floppy

Status in systemd package in Ubuntu:
  New

Bug description:
  When I connect USB floppy drive (Gembird) without floppy under Ubuntu, the 
drive engine seems to be running (the floppy drive LED is on and the drive is 
sounding). The same behaviour takes place if I connect the drive with a floppy 
and then remove the floppy. It seems that the system accesses the drive 
permanently when there is no floppy. Under Windows XP it works normally - when 
there is no floppy, the LED and engine are switched off. I have tried Ubuntu 
14.10 (amd64) with upstart, LXQt and KDE 5; Ubuntu 15.04 with systemd, LXQt - 
the same behaviour.
  If I boot using bash as init (init=/bin/bash) and connect the floppy drive 
after boot, the engine is off (the normal behaviour).
  lsof /dev/sdb during engine running outputs nothing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456338/+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 1495723] Re: Connecting USB devices failing

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  Connecting USB devices failing

Status in systemd package in Ubuntu:
  New

Bug description:
  rob@DesktopUbuntu:~$ lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  Ubuntu Software Center 13.10  (XUbuntu)

  I have had a problem with connecting my phone as a memory/disk device
  on Ubuntu 14.04 and found the same with a live install of 15.04. I
  recently bought an expensive 3-D Robox-CEL printer and was also
  experiencing no joy at all with extremely flaky connections.
  Fortunately one of the engineers at Robox-CEL published a patch to the
  udev .rules files and this cured the 3-D Printer connections and when
  I applied the same to the mobile phone .rules file it has been
  reliable as well.  His assertion was the later Linux's (I am not sure
  how wide he sees this problem here) have some sort of 'improvement'
  that interrogates the USB devices and in my case these two devices
  don't work with this new 'feature' and are extremely flaky.

  Here are the two new .rules I have added, that work for me

  # Samsung
  ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="685b", 
ENV{ID_MM_DEVICE_IGNORE}="1"
  SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="685b", 
GROUP="plugdev", NAME="GalaxySII", MODE="0666", OWNER=""

  #Robox Rules to stop the Linux sending disruptive commands to the 3D-Printer
  ATTRS{idVendor}=="16d0", ATTRS{idProduct}=="081b", 
ENV{ID_MM_DEVICE_IGNORE}="1"
  #Establish a standard name for the Robox tty interface
  SUBSYSTEM=="tty", ATTRS{idVendor}=="16d0", ATTRS{idProduct}=="081b", 
SYMLINK="robox%n", MODE="0666"

  The first line in the .rules is the really critical one.

  This has been a huge problem for me, and I registering it as a 'bug'
  as I believe the OS should be a bit more clever with these devices and
  should not require this sort of user work-around.  Over the last two
  years my phone went from super reliable to unusable, wasting huge
  amounts of my time, and recently made my 14 day old 3-D Printer from a
  quality manufacturer useless.

  Thank you for your time and patience. I can send you a log of the
  transactions of the Robox machine's interactions with the USB port if
  you need them.  However the above two files should give a good lead on
  where I feel the problems lie.

  Cheers, Rob Ward

  PS The Robox people also altered the shell script in their software to
  look for the newly named 'robox0' connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1495723/+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 1526111] Re: RAID1 + LVM in 14.04.3 causes intermittent boot failure

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  RAID1 + LVM in 14.04.3 causes intermittent boot failure

Status in systemd package in Ubuntu:
  New

Bug description:
  This problem seems to be related to a timing bug within `udev`, and has been 
experienced by other users as seen here;
  
http://serverfault.com/questions/567579/boot-failure-with-root-on-md-raid1-lvm-udev-event-timing

  Changing `/dev/md/0` to `/dev/md0` inside `/etc/mdadm/mdadm.conf`
  seems to resolve the problem. However unless you apply this patch, the
  system will intermittently fail to boot correctly, getting stuck here;

  kernel: [3.003506] md: bind
  kernel: [3.007705] md/raid1:md0: active with 1 out of 1 mirrors
  kernel: [3.007768] md0: detected capacity change from 0 to 499972440064
  kernel: [3.047284]  md0: unknown partition table
  kernel: [3.124709] device-mapper: table: 252:0: linear: dm-linear: Device 
lookup failed
  kernel: [3.124759] device-mapper: ioctl: error adding target to table
  kernel: [3.125156] device-mapper: table: 252:1: linear: dm-linear: Device 
lookup failed
  kernel: [3.125196] device-mapper: ioctl: error adding target to table

  There is also an example `/lib/udev/rules.d/` patch inside the thread
  I posted above, which proposes to add a `sleep` statement into LVM
  udev rules.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1526111/+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 1618471] Re: udev: init script unconditionally writes to /sys/kernel/uevent_helper

2020-08-06 Thread Kai Kasurinen
Fixed in version systemd/208-8

** Package changed: udev (Debian) => systemd (Debian)

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

** Changed in: systemd (Ubuntu)
   Status: New => 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/1618471

Title:
  udev: init script unconditionally writes to /sys/kernel/uevent_helper

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  The udev initramfs-tools script from trusty lts:

  /usr/share/initramfs-tools/scripts/init-top/udev

  does not check if uevent_helper does exist and fails to boot if it is
  missing - which it is in recent kernels (e.g. 4.7.2 from the mainline
  ppa or modern self build kernels where it is disabled per default
  afaik).

  See e.g.: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756312

  Its fixed in xenials version (latest LTS) but fails in current supported LTS 
trusty to boot.
  Please backport those simple fix:

  if [ -w /sys/kernel/uevent_helper ]; then
echo > /sys/kernel/uevent_helper
  fi

  and maybe add

  udevadm settle || true

  at the end to support kernels without uevent_helper enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618471/+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 1559643] Re: kswapd0 high cpu

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  kswapd0 high cpu

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  kswapd0 high cpu load.
  System doesn't have swap partition / swap file.

  Using AWS t2.nano

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-34-generic 4.2.0-34.39
  ProcVersionSignature: User Name 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 07:35 seq
   crw-rw 1 root audio 116, 33 Mar 20 07:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Sun Mar 20 07:57:52 2016
  Ec2AMI: ami-b7443fc0
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 cirrusdrmfb
   1 xen
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic 
root=UUID=b079c5f1-8fc8-4bb0-aa26-31610f9c5615 ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-34-generic N/A
   linux-backports-modules-4.2.0-34-generic  N/A
   linux-firmware1.149.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-11-13 (127 days ago)
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/07/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559643/+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 1564159] Re: vbox guest rules should be included by default

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  vbox guest rules should be included by default

Status in systemd package in Ubuntu:
  New

Bug description:
  Since vivid, Ubuntu ships the VirtualBox drivers as part of the main
  kernel package, by incorporating the virtualbox-guest-dkms package
  directly. See
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1418743 .
  However, the udev rules (/lib/udev/rules.d/60-virtualbox-guest-
  dkms.rules) from the same DKMS package are not beind shipped with the
  main udev installation. This leads to incorrect permissions of the
  /dev/vboxuser device. Since Ubuntu ships the kernel modules "by
  default" it should do the same for the udev rules. This is broken in
  vivid, wily and xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1564159/+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 1583372] Re: 73-special-net-names.rules is renaming manually created wifi interface

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  73-special-net-names.rules is renaming manually created wifi interface

Status in systemd package in Ubuntu:
  New

Bug description:
  The 73-special-net-names.rules file from 229-4ubuntu5 is renaming USB
  wifi network interfaces that I create manually with "iw phy phy0
  interface add wifi0 type managed":

  # Use MAC based names for network interfaces which are directly or indirectly
  # on USB and have an universally administered (stable) MAC address (second bit
  # is 0).
  ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="usb", NAME=="", 
ATTR{address}=="?[014589cd]:*", IMPORT{builtin}="net_id", 
NAME="$env{ID_NET_NAME_MAC}"

  
  The device is being renamed by udev as soon as it is created:
  KERNEL[3299.499637] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0 (net)
  KERNEL[3299.500180] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/rx-0 (queues)
  KERNEL[3299.500388] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-0 (queues)
  KERNEL[3299.500548] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-1 (queues)
  KERNEL[3299.500680] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-2 (queues)
  KERNEL[3299.500811] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-3 (queues)
  KERNEL[3299.502911] move 
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wlxc83a35c1 (net)
  UDEV  [3299.546165] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wlxc83a35c1 (net)
  UDEV  [3299.547977] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/rx-0 (queues)
  UDEV  [3299.549123] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-0 (queues)
  UDEV  [3299.550082] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-1 (queues)
  UDEV  [3299.550353] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-2 (queues)
  UDEV  [3299.550495] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-3 (queues)
  UDEV  [3299.552404] move 
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wlxc83a35c1 (net)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1583372/+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 1562589] Re: USB DVDRW's No Longer Function Correctly in 15.10 or 16.04

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  USB DVDRW's No Longer Function Correctly in 15.10 or 16.04

Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading several systems from 15.04 to 15.10, none of the
  systems were able to recognize the DVDRW in userland. This was tested
  with two different USB DVDRW's

  *-cdrom
 description: DVD-RAM writer
 product: SuperMultiPA3761
 vendor: Toshiba
 physical id: 0.0.0
 bus info: scsi@4:0.0.0
 logical name: /dev/cdrom
 logical name: /dev/cdrw
 logical name: /dev/dvd
 logical name: /dev/dvdrw
 logical name: /dev/sr0
 version: TO01
 capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
 configuration: status=ready
   *-medium
physical id: 0
logical name: /dev/cdrom

  
  And

*-cdrom
 description: DVD-RAM writer
 product: DVD RW DRU-830A
 vendor: SONY
 physical id: 0.0.0
 bus info: scsi@5:0.0.0
 logical name: /dev/cdrom
 logical name: /dev/cdrw
 logical name: /dev/dvd
 logical name: /dev/dvdrw
 logical name: /dev/sr0
 version: SS15
 capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
 configuration: status=ready
   *-medium
physical id: 0
logical name: /dev/cdrom

  This was also tested on 4 different systems. Three with Ubuntu and one
  with Kubuntu. I upgraded Kubuntu to 16.04. The difference in 16.04 is
  peculiar. The DVD player does not appear in any file manager. However,
  I could access the DVD via VLC. Attempting to play the DVD failed
  however. There was no sound and any option  chosen on the DVD menu
  resulted in a blank/black screen.

  This bug seems to afflict other users:

  http://askubuntu.com/questions/692934/after-upgrade-to-ubuntu-15-10
  -can-no-longer-access-video-files-on-cd-dvd

  I've also included this report here:

  https://bugs.launchpad.net/ubuntu/+source/udev/+bug/646293?comments=all

  But am filing a new bug since the other seems to be dead and/or
  outdated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1562589/+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 1635729] Re: bcache won't start on boot due to exotic block devices filtered in udev rules

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  bcache won't start on boot due to exotic block devices filtered in
  udev rules

Status in systemd package in Ubuntu:
  New

Bug description:
  If a bcache is created with a Curtis-Wright NVRAM card as caching
  device, the bcache device will not show up on boot without manual
  intervention.

  Tracking this down show this being due to the fact, that line 9 of
  /lib/udev/rules.d/60-persistent-storage.rules filters on a whitelist
  of devices
  
(loop*|mmcblk*[0-9]|msblk*[0-9]|mspblk*[0-9]|nvme*|sd*|sr*|vd*|xvd*|bcache*|cciss*|dasd*|ubd*),
  that doesn't include the NVRAM devices (umem*). A few steps later,
  this results in bcache_register() not being called.

  Trivially patching

  
-KERNEL!="loop*|mmcblk*[0-9]|msblk*[0-9]|mspblk*[0-9]|nvme*|sd*|sr*|vd*|xvd*|bcache*|cciss*|dasd*|ubd*",
 GOTO="persistent_storage_end"
  
+KERNEL!="loop*|mmcblk*[0-9]|msblk*[0-9]|mspblk*[0-9]|nvme*|sd*|sr*|vd*|xvd*|bcache*|cciss*|dasd*|ubd*|umem*",
 GOTO="persistent_storage_end"

  resolves the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635729/+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 1638518] Re: USB port gets rarely disabled until the next reboot

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  USB port gets rarely disabled until the next reboot

Status in systemd package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 17.04 dev with udev 231-10 and rarely (happened now
  the second time within 1-2 months) I'm noticing that the USB port of
  my mouse disables. This happens randomly on the current boot instance
  and replugging the mouse into the same USB port does not solve the
  issue. But plugging the mouse into another port causes it to work
  again but trying to plugging it back to the old port causes it to not
  work anymore. The only way to get the USB port working again is to
  reboot the system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1638518/+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 1634714] Re: ASUS T300 CHI Keyboard Fn Mappings

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  ASUS T300 CHI Keyboard Fn Mappings

Status in systemd package in Ubuntu:
  New

Bug description:
  I believe that this is in the incorrect queue, but Launchpad would not
  allow me to move it to udev.

  I am submitting this bug report following the directions at
  https://wiki.ubuntu.com/Hotkeys/Troubleshooting

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 16.10

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
    Installed: 231-9git1

  The Fn+F5,F6,F7, and F9 combinations do not produce the desired
  behavior of changing screen brightness or toggling the touchpad on the
  ASUS T300 Chi bluetooth keyboard. They do not produce any response
  whatsoever.

  They key events (as according to evtest) and their functions are
  listed below.

  type 2 (EV_REL), code 9 (REL_MISC), value 16 : Brightness Down (Fn + F5)
  type 2 (EV_REL), code 9 (REL_MISC), value 32 : Brightness Up (Fn + F6)
  type 2 (EV_REL), code 9 (REL_MISC), value 53 : Disable LCD Backlight (Fn + F7)
  type 2 (EV_REL), code 9 (REL_MISC), value 107 : Disable Touchpad (Fn + F9)

  Please let me know if I missed anything, this is my first bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: udev 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 18 20:04:07 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-18 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc.
   Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp.
   Bus 001 Device 012: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. T300CHI
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic.efi.signed 
root=UUID=33082bfc-d5e7-4dd9-869c-01e06d67bb28 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T300CHI.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T300CHI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.207:bd08/06/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: T300CHI
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1634714/+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 1646557] Re: /bin/udevadm should be exit 0 instead of exit 1

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  /bin/udevadm should be exit 0 instead of exit 1

Status in systemd package in Ubuntu:
  New

Bug description:
  if [ "$1" = "trigger" ]; then
  echo "some text halt was sinnvolle oder unsinniges zum Abruch
exit 1
  fi

  apt-get install rfkill 
  for example fails to configure 

  why not in /bin/udevadm end with exit 0 in case of trigger
  or settle? 

  then apt-get install rfkill and 28 other packages can configure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1646557/+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 1647067] Re: Dangling UDEV links after removing FC LUNs

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  Dangling UDEV links after removing FC LUNs

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  We're using Q-Logic QLE2562 Fibre Channel adapters (qla2xxx driver)
  against a HPE 3PAR 7400c storage array in an OpenStack environment.
  The OpenStack 3PAR driver manages volume attachments from the array to
  the servers. There is 4 path multipath to every volume.

  As the LUNs are removed, sometimes udev does not remove all links,
  particularly in /run/udev/links and /dev/disk/by-path. The symptoms
  are multiple records in one by-path directory under /run/udev/links,
  broken links to no longer attached luns in dev/disk/by-path and links
  between wrong LUNs and scsi devices there.

  OpenStack relies on these links. When another volume is attached using
  a LUN that has these leftover links and it happens that it is the
  first of the 4 paths, OpenStack incorrectly identifies the volume and
  attaches the same volume to multiple instances, leading to data loss.

  What could be causing this behavior?

  Ubuntu version 14.04 
  Linux version Ubuntu 4.4.0-47.68~14.04.1-generic 4.4.24
  udev 204-5ubuntu20.19
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CustomUdevRuleFiles: 20-3par-unmap.rulez
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2015-10-01 (429 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: HP ProLiant DL380 Gen9
  Package: udev 204-5ubuntu20.19
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic 
root=/dev/mapper/hostname--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-47.68~14.04.1-generic 4.4.24
  Tags:  trusty
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.4.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/03/2014
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd11/03/2014:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL380 Gen9
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647067/+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 1647078] Re: udevadm trigger (falsely?) reports udev is not configured

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  udevadm trigger (falsely?) reports udev is not configured

Status in systemd package in Ubuntu:
  New

Bug description:
  Eigentlich wollte ich nur ubuntu oder gnome als Desktop verwenden, da
  beide nicht starteten nahm ich dann Meta das läuft wenigstens und
  bekam die Fehlermeldung präsentiert. udisk2 ist wohl ein
  Abhängigkeitspaket für ubuntu-Desktop oder gnome-desktop beide wollen
  nicht laufen, warum auch immer.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udisks2 2.1.7-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  CustomUdevRuleFiles: 51-android.rules 69-usbmoto.rules 69-libmtp.rules 
60-raw1394.rules z60_hdaps-games.rules README.dpkg-new 51-hdaps.rules 
69-phicomm.rules
  Date: Thu Dec  1 12:10:32 2016
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  MachineType: LENOVO 3093BU3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic 
root=UUID=7aead086-5ba6-492c-921a-17a5656dba11 ro locale=de_DE bootkbd=de 
console-setup/layoutcode=de quiet splash selinux=0 enforcing=0 acpi_osi=Linux 
loglevel=0 vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: udisks2
  Title: package udisks2 2.1.7-1ubuntu1 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3093BU3
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:svnLENOVO:pn3093BU3:pvrThinkPadX201Tablet:rvnLENOVO:rn3093BU3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3093BU3
  dmi.product.version: ThinkPad X201 Tablet
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647078/+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 1652019] Re: udev does not read LINK files dynamically

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  udev does not read LINK files dynamically

Status in systemd package in Ubuntu:
  New

Bug description:
  Hello all,

  To comply to SystemD's way of thinking, NIC names can be changed
  assuming my MAC addresses.

  I have then changed /etc/systemd/10-net.link assuming the nomenclature
  in https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  Expected behavior: When restart, changes can be taken into account and
  NIC names changed, just like udev udev raw rules in /etc/udev/rules.d.

  Got: NIC names not changed. However: whane re-updating initramfs ( #
  update-initramfs -u ), it works.

  Question: why is udev not reading SystemD link files directly in the
  root FS, but is able to read udev rules.d files ?

  Distro : Ubuntu 16.04.4

  Thanks,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1652019/+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 1702320] Re: CUPS serial backend don't initialize correctly USB to serial converters

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  CUPS serial backend don't initialize correctly USB to serial
  converters

Status in systemd package in Ubuntu:
  New

Bug description:
  CUPS serial backend don't initialize correctly USB to serial
  converters

  See here for more details:

  https://bugs.linuxfoundation.org/show_bug.cgi?id=1397

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: cups-filters 1.13.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue Jul  4 16:57:25 2017
  InstallationDate: Installed on 2010-02-19 (2691 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  Lpstat: device for PRN-ttyS0: 
serial:/dev/ttyUSB0?baud=38400+bits=8+parity=none+flow=dtrdsr
  MachineType: System manufacturer System Product Name
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=UUID=6c704848-ff2d-4ef5-ba14-bbbe8a620cd0 ro quiet splash vt.handoff=7
  SourcePackage: cups-filters
  UpgradeStatus: Upgraded to zesty on 2017-07-03 (0 days ago)
  dmi.bios.date: 08/23/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1003
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5KPL-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1003:bd08/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-VM:rvrx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1702320/+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 1712575] Re: Upgrade from Ubuntu 12.04 LTS to 14.04 LTS Server. Can't bring up eth0. RTNETLINK answers: no such process [61709.025401] bnx2: can't load firmware file bnx2/bnx2-mi

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  Upgrade from Ubuntu 12.04 LTS to 14.04 LTS Server. Can't bring up
  eth0. RTNETLINK answers: no such process [61709.025401] bnx2: can't
  load firmware file bnx2/bnx2-mips-06-6.2.3.fw

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi. I just did a do-release-upgrade from Ubuntu Server 12.04 to 14.04
  LTS. After the upgrade eth0 does not exist. Networking fails on boot.
  Its on a Dell PowerEdge 2950 with one network connection and one
  static address on eth0 only (dual nics, 2nd is not being used).

  Here is the error I'm getting when trying to ifup eth0.

  RTNETLINK answers: no such process
  [61709.025401] bnx2: Can't load firmware file "bnx2/bnx2-mips-06-6.2.3.fw"
  RTNETLINK answers: No such file or directory
  Failed to bring up eth0.

  If I check dmesg, I can see the same error that it can't load the
  firmware file. I checked in /lib/firmware and the file is indeed
  there.

  
  This could be a dupe of this bug. However, I was told to file a new one as it 
is still an issue.
  https://bugs.launchpad.net/ubuntu/+source/udev/+bug/842560

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1712575/+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 1669420] Re: udevadm unconfigured script leaks into initrd causing boot failure

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  udevadm unconfigured script leaks into initrd causing boot failure

Status in systemd package in Ubuntu:
  New

Bug description:
  If update-initramfs is run while udevadm is "unconfigured", then the
  system is rendered unbootable.  Instead of containing a working
  version of udevadm, the "initrd" is built with the wrapper script that
  reports an error, and proceeds no further (as per code below).

  Please incorporate the check for 'unconfigured' into the code for
  udevadm, so that the udevadm binary can work correctly whether it is
  on an unconfigured system, or an initrd.

  This was a sticky problem, because no amount of 'dpkg-reconfigure
  udev' did the required 'mv udevadm.upgrade udevadm'

  #!/bin/sh

  if [ "$1" = "trigger" ]; then
  echo "udevadm trigger is not permitted while udev is unconfigured." 1>&2
  exit 1
  fi
  # ... snip ...
  exec /bin/bash -c "exec -a \"\$0\" /bin/udevadm.upgrade \"\$@\"" "$0" "$@"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1669420/+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 1720621] Re: Systemd does not start UDEV after remounting root

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  Systemd does not start UDEV after remounting root

Status in systemd package in Ubuntu:
  New

Bug description:
  Systemd under zesty starts udev before the root file system has been
  made writeable.

  This means that every insertion script (from /lib/udev/rules.d) that
  is subsequently run, even long after system boot, is unable to change
  anything in the world (for example can't create locks in /run/lock,
  device files in /dev etc etc) can't even write to /tmp;

  In my case scripts run at device insertion (including an attempt to
  log data to /tmp) fail:

  Oct  1 21:45:02 rata systemd-udevd[21055]: '/sbin/onerng.sh ttyACM0'(err) 
'/sbin/onerng.sh: 2: /sbin/onerng.sh: cannot create /tmp/yy: Read-only file 
system'
  Oct  1 21:45:02 rata systemd-udevd[21055]: '/sbin/onerng.sh ttyACM0'(err) 
'warning: commands will be executed using /bin/sh'
  Oct  1 21:45:02 rata systemd-udevd[21055]: '/sbin/onerng.sh ttyACM0'(err) 
'Cannot open lockfile /var/spool/cron/atjobs/.SEQ: Read-only file system'

  This breaks add-on products already in the field that worked with
  previous versions of Ubuntu

  One can use "/etc/init.d/udev restart" to restart udev  and everything
  works great after that - but devices that were discovered since udev
  was originally started will already have had their startup scripts run
  and fail - works great for devices that are only inserted after system
  boot, fails for devices that were already present at boot time

  The solution is to make sure that udev is started after the system
  directories are remoutned RW

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1720621/+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 1665143] Re: Commission scripts select the wrong nvme device link, then fails to report any storage

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  Commission scripts select the wrong nvme device link, then fails to
  report any storage

Status in MAAS:
  Fix Released
Status in MAAS 2.1 series:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The udev package provides /lib/udev/rules.d/60-persistent-
  storage.rules which creates two symlinks for nvme devices, under
  /dev/disk/by-id/. The first link name includes the device wwid and the
  second includes the device model/serial. The commission script selects
  the first link discovered and subsequently attempts to store it in a
  FilePath field, which allows for 100 characters. Since the wwid link
  is greater than 100 characters an exception is thrown, causing not
  only the nvme device not to be registered but all other storage
  devices as well. Although commissioning completes there is no storage
  assigned, which makes deployment of the node impossible.

  This issue has blocked all test runs performed by the CDO-QA test
  infrastructure, since every run installs MAAS on a fresh machine and
  commissions new nodes. The failure is seen when installing from either
  ppa:maas/next (2.2.0~beta2) or ppa:maas/stable (2.1.3+bzr5573).

  ubuntu@meowth:~$ dpkg -l '*maas*'|cat
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ NameVersion  
Architecture Description
  
+++-===---=
  ii  maas2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all  
"Metal as a Service" is a physical cloud and IPAM
  ii  maas-cli2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all  
MAAS client and command-line interface
  un  maas-cluster-controller
   (no description available)
  ii  maas-common 2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all  
MAAS server common files
  ii  maas-dhcp   2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all  
MAAS DHCP server
  ii  maas-dns2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all  
MAAS DNS server
  ii  maas-proxy  2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all  
MAAS Caching Proxy
  ii  maas-rack-controller2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all  
Rack Controller for MAAS
  ii  maas-region-api 2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all  
Region controller API service for MAAS
  ii  maas-region-controller  2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all  
Region Controller for MAAS
  un  maas-region-controller-min 
   (no description available)
  un  python-django-maas 
   (no description available)
  un  python-maas-client 
   (no description available)
  un  python-maas-provisioningserver 
   (no description available)
  ii  python3-django-maas 2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all  
MAAS server Django web framework (Python 3)
  ii  python3-maas-client 2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all  
MAAS python API client (Python 3)
  ii  python3-maas-provisioningserver 2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all  
MAAS server provisioning libraries (Python 3)

  After re-commissioning one of the servers with ssh enabled the
  attached log files were collected. Please note that from the shell it
  can be seen that block devices are discovered and even the
  commissioning output found in /tmp/user_data.sh.IK9yVp/out/00-maas-07
  -block-devices lists devices (see attached), where-as this file is
  shown as a 0 byte file from the GUI (see screen shot).

  There are 'HTTP Error 500: INTERNAL SERVER ERROR' errors in cloud-
  init-output.log

  ubuntu@azurill:~$ uname -a
  Linux azurill 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:55:08 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@azurill:~$ sudo lsblk  --exclude 1,2,7 -d -P -o NAME,RO,RM,MODEL,ROTA
  NAME="sdb" RO="0" RM="0" MODEL="LOGICAL VOLUME  " ROTA="1"
  NAME="sdc" RO="1" RM="0" MODEL="VIRTUAL-DISK" ROTA="1"
  NAME="sda" RO="0" RM="0" MODEL="LOGICAL VOLUME  " ROTA="1"
  NAME="nvme0n1" RO="0" RM="0" MODEL="INTEL SSDPEDME400G4

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

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

[Touch-packages] [Bug 1744928] Re: udev doesn't include a rule for security keys (including Yubico)

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  udev doesn't include a rule for security keys (including Yubico)

Status in systemd package in Ubuntu:
  New

Bug description:
  https://bugs.chromium.org/p/chromium/issues/detail?id=427966#c19

  I can confirm that the following solves the problem on bionic:

  sudo bash -c 'cat > /lib/udev/rules.d/50-securitykey.rules << EOF
  SUBSYSTEMS=="usb", ATTRS{idVendor}=="1050", MODE="0644", GROUP="plugdev"
  EOF'
  service udev restart

  We might wish to flesh this out with a list of vendor IDs, but even
  just Yubico (1050) will likely cover the vast majority of use cases
  due to their market share.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1744928/+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 1748698] Re: udevadm trigger kills X server

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  udevadm trigger kills X server

Status in systemd package in Ubuntu:
  New

Bug description:
  Running Xubuntu 16.04.3, with udev version 229-4ubuntu21.1.

  Every time I install the plexmediaserver package, no matter with what
  mechanism, my X server crashes out completely, taking all my running
  applications with it.

  I traced it to a postinst script call to `udevadm trigger`.  Running
  that one command manually will instantly kill the X server every time.

  In looking at the logs, there's a segfault in radeon_drv.o that's
  clearly the end of the X server.  syslog contains a set of messages
  about Ethernet interfaces "changed", then a cluster of messages about
  how various disk devices (/dev/sdX) appear twice with different sysfs
  paths, and then suddenly xfce4 is logging about how the X server just
  vanished.

  A mess of UPower[d] messages show up in the log as well, but shutting
  down upowerd before running another test yields no change, so it's not
  responsible for this.

  Whatever udev is doing to the X server is giving it a very bad day.
  This makes it impractical for me to upgrade plex very frequently at
  all, since my machine runs 24/7.  However, I'm having so many problems
  with Plex right now that I'll be investigating other solutions
  anyway...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748698/+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 1778900] Re: udev mounts MTP devices in read-only mode.

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  udev mounts MTP devices in read-only mode.

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 18.04 udev mounts MTP devices (mine is Google Pixel C
  tablet) in read-only mode by default, so that files cannot be copied
  over to the device.

  One has to manually create a udev rule to mount the device in read-
  write mode. This is rather user-unfriendly.

  Make udev mount MTP devices in read-write mode by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778900/+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 1778833] Re: tty symlink incorrect after disconnect/reconnect, fixed by manual udevadm trigger

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  tty symlink incorrect after disconnect/reconnect, fixed by manual
  udevadm trigger

Status in systemd package in Ubuntu:
  New

Bug description:
  I recently upgraded from Ubuntu 17.10 to 18.04 and encountered what appears 
to be a regression in udev. On 17.10 (and previous), the following udev rule to 
rename a USB serial device worked perfectly:
  SUBSYSTEMS=="usb", ATTRS{product}=="IOTool", 
ATTRS{manufacturer}=="zplab.wustl.edu", ATTRS{serial}=="0x", 
SYMLINK+="ttyIOTool"

  This would yield symlinks as expected:
  > ls -l /dev/ttyIOTool
  lrwxrwxrwx 1 root root 7 Jun 26 21:34 /dev/ttyIOTool -> ttyACM1

  On 18.04, the same symlinks are made correctly at boot time. However,
  if the device is unplugged and then re-plugged, the symlink instead
  goes to /dev/bus/usb:

  > ls -l /dev/ttyIOTool 
  lrwxrwxrwx 1 root root 15 Jun 26 21:33 /dev/ttyIOTool -> bus/usb/003/013

  This is a problem, because /dev/bus/usb devices can't be opened as
  serial ports in the way that /dev/tty devices can.

  However, manually triggering udev via `udevadm trigger` returns the
  symlinks to the expected state. I am fairly certain that this behavior
  represents a bug, because there shouldn't be any difference in
  behavior between an auto-triggered event with a disconnect /
  reconnect, and one manually triggered via udevadm trigger, right?

  Version information: udevadm --version gives 237 on the 18.04 system
  (with this broken behavior) and 234 on an identical 17.10 system with
  the correct behavior. On a similar 16.10 system with udevadm version
  231, such symlinks also work fine.

  Note also that there are several reports of similar udev behavior around the 
web, which have left the users fairly perplexed; e.g.:
  https://github.com/psi46/elComandante/issues/14
  https://github.com/oskarpearson/mmeowlink/issues/52

  Please let me know if there's anything further I can do to help debug
  this problem. I can probably work around this by using /dev/serial/by-
  id, but if anyone has other workarounds to try (different udev rules,
  perhaps?), I would be grateful as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778833/+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 1822451] Re: high cpu load

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  high cpu load

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing  Kubuntu 19.04 Disco Dingo
  Same bug #1767968 on Dell Latitude E6400

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1822451/+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 1767968] Re: systemd-udev cause high cpu load after upgrade to bionic

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

** Project changed: udev => linux

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

Title:
  systemd-udev cause high cpu load after upgrade to bionic

Status in Linux:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in bluez package in Debian:
  New

Bug description:
  After upgraded from xenial to bionic (kernel 4.15.0-20) systemd-udevd
  runs with high cpu load in 2 instances (50%, 15%) on Dell Precision
  M6500 when wlan switch will be enabled.

  With xenial this problem did't happen and Dell bluetooth & wifi (b43)
  are working.

  After some research I found that /var/log/syslog gets filled with a
  lot of messages (see log sample below).

  If I modify /lib/udev/rules.d/97-hid2hci.rules (disable rule for
  413c:8154, 413c:8158, 413c:8162), restart udev, turn wifi off/on by
  hardware switch, the messages go away but the bluetooth adapter will
  be not enabled anymore. It seems that udev is running in a loop.

  My modification for the rule just was (just as proof):

  --- before ---
  ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01", 
ATTR{bInterfaceProtocol}=="02", \
ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c", 
ATTRS{bmAttributes}=="e0", \
RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"
  --- end before ---

  --- after ---
  ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01", 
ATTR{bInterfaceProtocol}=="02", \
ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c", 
ATTRS{bmAttributes}=="e0", \
RUN+="/bin/sh", ENV{HID2HCI_SWITCH}="1"
  --- end after ---

  If you need some experiment or testing I can do (compiling software is
  not a problem, I'm a developer).

  lsusb:
  Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 058: ID 413c:8162 Dell Computer Corp. Integrated Touchpad 
[Synaptics]
  Bus 001 Device 057: ID 413c:8161 Dell Computer Corp. Integrated Keyboard
  Bus 001 Device 056: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
  Bus 001 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor
  Bus 001 Device 003: ID 05ca:1815 Ricoh Co., Ltd 
  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  lspci:
  Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 058: ID 413c:8162 Dell Computer Corp. Integrated Touchpad 
[Synaptics]
  Bus 001 Device 057: ID 413c:8161 Dell Computer Corp. Integrated Keyboard
  Bus 001 Device 056: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
  Bus 001 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor
  Bus 001 Device 003: ID 05ca:1815 Ricoh Co., Ltd 
  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  root@precision:~# lspci
  00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
  00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 
(rev 11)
  00:08.0 System peripheral: Intel Corporation Core Processor System Management 
Registers (rev 11)
  00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and 
Scratchpad Registers (rev 11)
  00:08.2 System peripheral: Intel Corporation Core Processor System Control 
and Status Registers (rev 11)
  00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous 
Registers (rev 11)
  00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11)
  00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and 
Protocol Registers (rev 11)
  00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 
Enhanced Host Controller (rev 05)
  00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 1 (rev 05)
  00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 2 (rev 05)
  00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 3 (rev 05)
  00:1c.3 PCI bridge: Intel Corporation 5 

[Touch-packages] [Bug 1838992] Re: udev doesn't pick up volumes properly

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  udev doesn't pick up volumes properly

Status in systemd package in Ubuntu:
  New

Bug description:
  [Only happens on Ubuntu, not other OS's, like Debian]

  When we are attaching a volume to a running Ubuntu server (using
  kvm/libvirt), most of the time the udev rules are not properly
  triggered. In the end the volume will most of the time not be
  available in `/dev/disk/by-id/virtio-`. Sometimes it works
  though (10%/20%?).

  The reason for this is that udev somehow doesn't pick it up when the
  volume is attached. It looks like a timing issue. Just looking at
  `/sys/devices/pci:00/:00:05.0/virtio2/block/vdb/serial` makes
  it clear that it's there. However `udevadm info /dev/vdb` returns
  without the `ID_SERIAL` key. Only a `udevadm trigger` leads to a
  correct entry of `ID_SERIAL` and also fixes `/dev/disk/by-id`.

  We are a small cloud provider (cloudscale.ch). We have tested this on
  Ubuntu (16.04/18.04), Debian 9, CentOS, CoreOS. We haven't tested this
  extensively, but it sure looks like it's only happening on Ubuntu. .
  We never had any issues reported on other OS's about this.

  I tried looking at the differences of Debian and Ubuntu udev packages,
  but couldn't figure out what might be responsible for this behavior.

  If someone needs an account for our control panel to reproduce this,
  please contact me, I'm happy to give you the resources to debug this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1838992/+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 1846367] Re: udev /dev/null incorrect permissions after package auto upgrades

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  udev /dev/null incorrect permissions after package auto upgrades

Status in systemd package in Ubuntu:
  New

Bug description:
  I've been attempting to determine root cause of this problem for
  months.

  Symptom is group/other permissions being dropped from all /dev/*
  files.

  This only occurs on some machines, so some machine udev updates work,
  some machines quietly fail.

  Looks like the problem relates to...

  1) APT /etc/apt/apt.conf.d/10periodic APT::Periodic::Update-Package-
  Lists == 1, which triggers auto upgrades for critical packages.

  2) This triggers the udev package run as an unattended/automatic
  upgrade.

  3) When udev package updates, /var/log/dpkg.log shows no errors.

  4) /dev/* files have group/other permissions stripped.

  5) LXD containers become unstable, as containers /dev points to
  machine /dev.

  Temp fix is change /etc/apt/apt.conf.d/10periodic - APT::Periodic
  ::Update-Package-Lists == 0 to disable all unattended upgrades.

  Someone let me know where I can find APT/DPKG logs detailing exactly
  what post install hook scripts run for udev, so I can look for errors.

  Or if log verbosity has to be increased for this level of logging, let
  me know how to increase verbosity, so next time udev updates, I can
  provide logging detail sufficient to generate a fix for this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1846367/+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 1840772] Re: Script cannot access network when triggered by udev rule

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  Script cannot access network when triggered by udev rule

Status in systemd package in Ubuntu:
  New

Bug description:
  I have a script that is triggered by a udev rule, and that needs to
  connect to a remote host.

  The example below works fine in 16.04, but fails in 18.04. It seems
  that the process executing the script is somehow limited wrt. network
  access. The script works fine when started from a shell prompt.

  To reproduce:

  
  - create /tmp/myscript:

  #/bin/sh
  wget -o /tmp/wget.log -O /tmp/index.html http://www.google.com

  
  - create /etc/udev/rules.d/52-netaccess.rules

  ACTION=="add", ATTRS{idVendor}=="cafe", MODE="0660", GROUP="root",
  SUBSYSTEM=="usbmisc", RUN+="/tmp/myscript"

  
  - Plugin a USB device with vendor ID 0xcafe, and check the wget output in 
/tmp/wget.log. 

  On ubuntu 18.04 wget fails with this output:

  --2019-08-19 14:49:43--  http://www.google.com/
  Resolving www.google.com (www.google.com)... failed: Name or service not 
known.
  wget: unable to resolve host address 'www.google.com'

  
  If I use an IP address in the URL there is no resolve error, but then wget 
blocks in the socket connect() syscall (according to strace). At some point the 
script is killed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840772/+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 1833443] Re: Calculator button does nothing (Calculator not launched)

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  Calculator button does nothing (Calculator not launched)

Status in systemd package in Ubuntu:
  New

Bug description:
  Troubleshoot steps followed:
  https://wiki.ubuntu.com/Hotkeys/Troubleshooting.

  Step-by-step Troubleshooting
  1. Is latest I think
  2. gnome-settings-daemon not running
  3. No keypress event
  4. Skip (see 3)
  5. a. 

  evtest output:
  Event: time 1560959333.892425, -- SYN_REPORT 
  Event: time 1560959337.916913, type 4 (EV_MSC), code 4 (MSC_SCAN), value a1
  Event: time 1560959337.916913, type 1 (EV_KEY), code 140 (KEY_CALC), value 1
  Event: time 1560959337.916913, -- SYN_REPORT 
  Event: time 1560959338.121844, type 4 (EV_MSC), code 4 (MSC_SCAN), value a1
  Event: time 1560959338.121844, type 1 (EV_KEY), code 140 (KEY_CALC), value 0
  Event: time 1560959338.121844, -- SYN_REPORT 

 b. 140 (0x08c) not found in /usr/include/linux/input.h
  7. N/A (see 4)

  I can try provide info from
  https://wiki.ubuntu.com/DebuggingProcedures if wanted.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10.22
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_51_55_generic_52
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.warzone2100.rules 70-snap.core.rules 
70-snap.opendungeons.rules 56-hpmud.rules S99-2000S1.rules 
70-snap.minetest.rules 40-libsane.rules 70-snap.canonical-livepatch.rules 
70-snap.chromium.rules
  Date: Wed Jun 19 17:58:19 2019
  InstallationDate: Installed on 2019-05-14 (36 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=9b9d08ae-0424-4d09-87e0-5db4115b3a2b ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SVD Ver. F.60
  dmi.board.name: 1631
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 01.3F
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SVDVer.F.60:bd03/12/2015:svnHewlett-Packard:pn:pvrA0001C02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3F:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.version: A0001C02
  dmi.sys.vendor: Hewlett-Packard

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

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


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

2020-08-06 Thread Kai Kasurinen
** Changed in: udev (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/1856871

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

Status in linux package in Ubuntu:
  Incomplete
Status in parted package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in udev package in Ubuntu:
  Invalid

Bug description:
  This is reproducible in Bionic and late.

  Here's an example running 'focal':

  $ lsb_release -cs
  focal

  $ uname -r
  5.3.0-24-generic

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

  and on more recent kernel:

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

  
  How to trigger it:
  $ sosreport -o block

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

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

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

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

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

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

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

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

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

  while /dev/loop3 doesn't

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

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

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

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 1873648] Re: After suspend, ttyusb0 is moved to ttyusb1

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  After suspend, ttyusb0 is moved to ttyusb1

Status in systemd package in Ubuntu:
  New

Bug description:
  I have an old Core2 Duo running Ubuntu 20.04.
  As it was sluggish with gnome, I installed the xfce environment (only xfce, 
not xubuntu)

  Yesterday, I was using minicom then I suspended my laptop.
  When I restarted minicom reported it could not open ttyusb0

  After a few checks, I noticed that my usb to serial adapter was now
  ttyusb1. I did not try to replicate.

  This is quite annoying if you intend to rely a lot on suspend.

  This behavior used to be in Windows in the past, but I believe they
  use the UUID to always assign the same port to a USB device, as under
  Windows, wherever I plug my US?B device, it always identifies as the
  same "COM" port (used not to be the case before).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1873648/+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 1839156] Re: TCP/IP connection stuck when called from UDEV rule

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  TCP/IP connection stuck when called from UDEV rule

Status in systemd package in Ubuntu:
  New

Bug description:
  It seems that in Eoan there is a lock/any other issue preventing
  particular system calls to be executed by the triggered action
  handler. I have an action executing wget when USB-serial adapter is
  plugged:

  SUBSYSTEM=="tty", ACTION=="add", ATTRS{idVendor}=="1a86", 
ATTRS{idProduct}=="7523", MODE="0666", RUN+="/usr/bin/wget -v --method=POST 
http://127.0.0.1:4000/udev_trigger/add;
  This action works perfectly in a prior versions - but in Eoan Ermine it hangs 
for ~30s and fails on a timeout. Analysis with strace shows that execution is 
stuck on connect() syscall - until it returns with ETIMEDOUT.

  Same Wget command, being run from a command line, works perfectly.

  The issue doesn't seem to be related to a particular IP
  (localhost/remote) and/or the status of a listener process - execution
  hangs also when listener is not running and port is free.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1839156/+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 1874424] Re: USB external disks are not torn down correctly when they are unplugged

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  USB external disks are not torn down correctly when they are unplugged

Status in systemd package in Ubuntu:
  New

Bug description:
  System information:

  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10
  $ apt-cache policy udev
  udev:
Installed: 242-7ubuntu3.7
Candidate: 242-7ubuntu3.7
Version table:
   *** 242-7ubuntu3.7 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   242-7ubuntu3.6 500
  500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 
Packages
   242-7ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  I have a USB3 external SSD (VID/PID is /).  The whole device
  is encrypted (ie /dev/sdc is an encrypted LUKS volume) and the
  encrypted volume contains an LVM2 physical volume, a volume group
  called "vms" and two logical volumes.

  If I plug it into a booted system, everything works as expected.  I'm
  prompted for the volume password, the volume is unlocked and LVM then
  maps the logical volumes:

  $ ls -l /dev/mapper
  total 0
  crw--- 1 root root 10, 236 Apr 23 11:49 control
  lrwxrwxrwx 1 root root   7 Apr 23 11:51 
luks-5e586d40-5f49-4c33-8f73-22da39d2728a -> ../dm-3
  lrwxrwxrwx 1 root root   7 Apr 23 11:49 nvme0n1p3_crypt -> ../dm-0
  lrwxrwxrwx 1 root root   7 Apr 23 11:49 vgubuntu-root -> ../dm-1
  lrwxrwxrwx 1 root root   7 Apr 23 11:49 vgubuntu-swap_1 -> ../dm-2
  lrwxrwxrwx 1 root root   7 Apr 23 11:51 vms-veeabuild -> ../dm-4
  lrwxrwxrwx 1 root root   7 Apr 23 11:51 vms-veea--mirror -> ../dm-5

  (The volumes "vms-*" are the ones on the external disk).  I can mount
  the volumes and use them.

  If I'm careful to unmount the LVM volumes correctly and lock the
  disks, everything works as expected:

  $ vgchange -a n vms
0 logical volume(s) in volume group "vms" now active
  $ sudo udisksctl lock -b /dev/sdc
  Locked /dev/sdc.

  I then unplug the disk and repeat the process - everything works.  If,
  for whatever reason, the device gets unplugged without the proper
  cleanup, things get messy:

  $ ls -l /dev/mapper
  total 0
  crw--- 1 root root 10, 236 Apr 23 11:49 control
  lrwxrwxrwx 1 root root   7 Apr 23 12:04 
luks-5e586d40-5f49-4c33-8f73-22da39d2728a -> ../dm-3
  lrwxrwxrwx 1 root root   7 Apr 23 11:49 nvme0n1p3_crypt -> ../dm-0
  lrwxrwxrwx 1 root root   7 Apr 23 11:49 vgubuntu-root -> ../dm-1
  lrwxrwxrwx 1 root root   7 Apr 23 11:49 vgubuntu-swap_1 -> ../dm-2
  lrwxrwxrwx 1 root root   7 Apr 23 12:04 vms-veeabuild -> ../dm-4
  lrwxrwxrwx 1 root root   7 Apr 23 12:04 vms-veea--mirror -> ../dm-5

  Note that the "vms-*" volumes are still there.

  $ ls -l /dev/dm-*
  brw-rw 1 root disk 253, 0 Apr 23 11:49 /dev/dm-0
  brw-rw 1 root disk 253, 1 Apr 23 11:49 /dev/dm-1
  brw-rw 1 root disk 253, 2 Apr 23 11:49 /dev/dm-2
  brw-rw 1 root disk 253, 3 Apr 23 12:04 /dev/dm-3
  brw-rw 1 root disk 253, 4 Apr 23 12:04 /dev/dm-4
  brw-rw 1 root disk 253, 5 Apr 23 12:04 /dev/dm-5

  /dev/dm-* still exists.

  However, sdc has been removed:

  $ ls -l /dev/sdc
  ls: cannot access '/dev/sdc': No such file or directory

  If I then plug the disk in again, I'm again prompted for the
  passphrase and the disk is mapped to /dev/sdd (not /dev/sdc like
  previous times).  If I try to mount one of the volumes:

  $ sudo mount /dev/mapper/vms-veeabuild mnt2
  mount: /home/tkcook/mnt2: can't read superblock on /dev/mapper/vms-veeabuild.

  Something is not getting cleaned up when the disk is forcibly removed.
  There doesn't seem to be any way to clean up from here; vgchange can't
  deactivate the volume group and udisksctl can't lock the LUKS volume.
  The only way I've found of using the disk again is to reboot (!)

  I'm raising this on the udev package but that is a bit of a guess; I'm
  assuming this is udev not processing the disconnection event correctly
  (though since I can't find a way of cleaning this up, it's not clear
  what it could do).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1874424/+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 1890654] Re: udev service does not log

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  udev service does not log

Status in systemd package in Ubuntu:
  New

Bug description:
  By default udev is supposed to log to /var/log.  In Ubuntu 20 it is
  not logging.  Logging was then explicitly enabled by uncommenting this
  line in /etc/udev/udev.conf:

  "udev_log=info"

  After running "systemctl restart udev" and plugging in a USB drive,
  there is still no udev log in /var/log.  Yet /var/log/system shows
  that a device was in fact attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890654/+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 1890520] Re: catastrophic bug with deluser command -- destroys large number of system files

2020-08-06 Thread Kai Kasurinen
** Package changed: ubuntu => adduser (Ubuntu)

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

Title:
  catastrophic bug with deluser command -- destroys large number of
  system files

Status in adduser package in Ubuntu:
  New

Bug description:
  I installed rygel and created a specific rygel user to run it with (as
  directed by the docs). I then realized a specific user was not needed.
  To reverse my steps, I ran deluser which proceeded to delete lots of
  files that have nothing to do with the rygel user:

  root@host:~# adduser --home /home/rygel --disabled-password --disabled-login 
--gecos 'Rygel media server' rygel
  root@host:~# sudo su - rygel
  rygel@host:$ systemctl start rygel
  rygel@host:$ exit
  root@host:~# deluser --remove-home --remove-all-files rygel
  Looking for files to backup/remove ...
  /usr/sbin/deluser: Cannot handle special file /etc/systemd/system/mdm.service
  /usr/sbin/deluser: Cannot handle special file 
/etc/systemd/system/samba-ad-dc.service
  /usr/sbin/deluser: Cannot handle special file 
/etc/systemd/system/cgmanager.service
  /usr/sbin/deluser: Cannot handle special file 
/etc/systemd/system/cgproxy.service
  /usr/sbin/deluser: Cannot handle special file /dev/vcsa7
  /usr/sbin/deluser: Cannot handle special file /dev/vcsu7
  /usr/sbin/deluser: Cannot handle special file /dev/vcs7
  /usr/sbin/deluser: Cannot handle special file /dev/gpiochip0
  /usr/sbin/deluser: Cannot handle special file /dev/dvdrw
  /usr/sbin/deluser: Cannot handle special file /dev/dvd
  /usr/sbin/deluser: Cannot handle special file /dev/cdrw
  /usr/sbin/deluser: Cannot handle special file /dev/zfs
  /usr/sbin/deluser: Cannot handle special file /dev/vhost-vsock
  /usr/sbin/deluser: Cannot handle special file /dev/vhost-net
  /usr/sbin/deluser: Cannot handle special file /dev/uhid
  /usr/sbin/deluser: Cannot handle special file /dev/vhci
  /usr/sbin/deluser: Cannot handle special file /dev/userio
  /usr/sbin/deluser: Cannot handle special file /dev/nvram
  /usr/sbin/deluser: Cannot handle special file /dev/btrfs-control
  /usr/sbin/deluser: Cannot handle special file /dev/cuse
  /usr/sbin/deluser: Cannot handle special file /dev/autofs
  /usr/sbin/deluser: Cannot handle special file /dev/sde
  /usr/sbin/deluser: Cannot handle special file /dev/sdd
  /usr/sbin/deluser: Cannot handle special file /dev/sdc
  /usr/sbin/deluser: Cannot handle special file /dev/sdb
  /usr/sbin/deluser: Cannot handle special file /dev/sg5
  /usr/sbin/deluser: Cannot handle special file /dev/sg4
  /usr/sbin/deluser: Cannot handle special file /dev/sg3
  /usr/sbin/deluser: Cannot handle special file /dev/sg2
  /usr/sbin/deluser: Cannot handle special file /dev/vcsa6
  /usr/sbin/deluser: Cannot handle special file /dev/vcsu6
  /usr/sbin/deluser: Cannot handle special file /dev/vcs6
  /usr/sbin/deluser: Cannot handle special file /dev/vcsa5
  /usr/sbin/deluser: Cannot handle special file /dev/vcsu5
  /usr/sbin/deluser: Cannot handle special file /dev/vcs5
  /usr/sbin/deluser: Cannot handle special file /dev/vcsa4
  /usr/sbin/deluser: Cannot handle special file /dev/vcsu4
  /usr/sbin/deluser: Cannot handle special file /dev/vcs4
  /usr/sbin/deluser: Cannot handle special file /dev/vcsa3
  /usr/sbin/deluser: Cannot handle special file /dev/vcsu3
  /usr/sbin/deluser: Cannot handle special file /dev/vcs3
  /usr/sbin/deluser: Cannot handle special file /dev/vcsa2
  /usr/sbin/deluser: Cannot handle special file /dev/vcsu2
  /usr/sbin/deluser: Cannot handle special file /dev/vcs2
  /usr/sbin/deluser: Cannot handle special file /dev/hidraw2
  /usr/sbin/deluser: Cannot handle special file /dev/hidraw1
  /usr/sbin/deluser: Cannot handle special file /dev/cdrom
  /usr/sbin/deluser: Cannot handle special file /dev/hidraw0
  /usr/sbin/deluser: Cannot handle special file /dev/fb0
  /usr/sbin/deluser: Cannot handle special file /dev/i2c-5
  /usr/sbin/deluser: Cannot handle special file /dev/i2c-4
  /usr/sbin/deluser: Cannot handle special file /dev/i2c-3
  /usr/sbin/deluser: Cannot handle special file /dev/i2c-2
  /usr/sbin/deluser: Cannot handle special file /dev/i2c-1
  /usr/sbin/deluser: Cannot handle special file /dev/i2c-0
  /usr/sbin/deluser: Cannot handle special file /dev/rtc
  /usr/sbin/deluser: Cannot handle special file /dev/stderr
  /usr/sbin/deluser: Cannot handle special file /dev/stdout
  /usr/sbin/deluser: Cannot handle special file /dev/stdin
  /usr/sbin/deluser: Cannot handle special file /dev/sda6
  /usr/sbin/deluser: Cannot handle special file /dev/sda5
  /usr/sbin/deluser: Cannot handle special file /dev/sda3
  /usr/sbin/deluser: Cannot handle special file /dev/sda2
  /usr/sbin/deluser: Cannot handle special file /dev/sda1
  /usr/sbin/deluser: Cannot handle special file /dev/sg1
  /usr/sbin/deluser: Cannot handle special file /dev/sr0
  /usr/sbin/deluser: Cannot handle special file 

[Touch-packages] [Bug 1890170] Re: ImportError libstdc++.so.6 cannot allocate memory after importing PyQt5.Qt PyQt5.QtCore and cv2

2020-08-03 Thread Kai Kasurinen
downgrading libmysqlclient21:amd64 from 8.0.21-0ubuntu0.20.04.3 to
8.0.19-0ubuntu5 fixes issue

** Also affects: mysql-8.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  ImportError libstdc++.so.6 cannot allocate memory after importing
  PyQt5.Qt PyQt5.QtCore and cv2

Status in mysql-8.0 package in Ubuntu:
  New
Status in opencv package in Ubuntu:
  New
Status in pyqt5 package in Ubuntu:
  New

Bug description:
  I'm using an updated Lubuntu focal. Starting maybe last week (monday July 
27th), if in python3 I do
  from PyQt5 import Qt, QtCore
  import cv2

  I get
  ImportError: /lib/x86_64-linux-gnu/libstdc++.so.6: cannot allocate memory in 
static TLS block

  I noticed only now that the reverse (first import cv2, then Qt,
  QtCore) seems to work correctly and displays no errors. I'm afraid I
  might not be able to do the reverse in my real software...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Mon Aug  3 17:49:20 2020
  InstallationDate: Installed on 2020-07-15 (19 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890170/+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 1890170] Re: ImportError libstdc++.so.6 cannot allocate memory after importing PyQt5.Qt PyQt5.QtCore and cv2

2020-08-03 Thread Kai Kasurinen
** Package changed: python3-defaults (Ubuntu) => opencv (Ubuntu)

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

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

Title:
  ImportError libstdc++.so.6 cannot allocate memory after importing
  PyQt5.Qt PyQt5.QtCore and cv2

Status in opencv package in Ubuntu:
  New
Status in pyqt5 package in Ubuntu:
  New

Bug description:
  I'm using an updated Lubuntu focal. Starting maybe last week (monday July 
27th), if in python3 I do
  from PyQt5 import Qt, QtCore
  import cv2

  I get
  ImportError: /lib/x86_64-linux-gnu/libstdc++.so.6: cannot allocate memory in 
static TLS block

  I noticed only now that the reverse (first import cv2, then Qt,
  QtCore) seems to work correctly and displays no errors. I'm afraid I
  might not be able to do the reverse in my real software...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Mon Aug  3 17:49:20 2020
  InstallationDate: Installed on 2020-07-15 (19 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1890170/+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 1621686] Re: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package python-gobject-2 2.28.6-12build1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in pygobject-2 package in Ubuntu:
  Confirmed

Bug description:
  When I install sudo apt-get install im-switch and sudo apt-get install
  ibus ibus-clutter ibus-gtk ibus-gtk3 ibus-qt4.

  I've received these errors below:

  Errors were encountered while processing:
   python-gi
   python-cairo
   python-gobject-2
   python-gtk2
   python-notify
   ibus
   python-configparser
   python-django
   python-pkg-resources
   python-setuptools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-gobject-2 2.28.6-12build1
  ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Sep  9 09:24:21 2016
  DuplicateSignature: package:python-gobject-2:2.28.6-12build1:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-08-18 (21 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: pygobject-2
  Title: package python-gobject-2 2.28.6-12build1 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/pygobject-2/+bug/1621686/+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 1621687] Re: package python-gi 3.12.0-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package python-gi 3.12.0-1ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in pygobject package in Ubuntu:
  New

Bug description:
  When I install sudo apt-get install im-switch and sudo apt-get install
  ibus ibus-clutter ibus-gtk ibus-gtk3 ibus-qt4.

  I've received these errors below:

  Errors were encountered while processing:
   python-gi
   python-cairo
   python-gobject-2
   python-gtk2
   python-notify
   ibus
   python-configparser
   python-django
   python-pkg-resources
   python-setuptools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-gi 3.12.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Sep  9 09:24:21 2016
  DuplicateSignature: package:python-gi:3.12.0-1ubuntu1:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-08-18 (21 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: pygobject
  Title: package python-gi 3.12.0-1ubuntu1 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/pygobject/+bug/1621687/+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 1632835] Re: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug is no longer a duplicate of bug 1621686
   package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade:
  sub-processo script post-installation instalado retornou estado de
  saída de erro 1

Status in pygobject-2 package in Ubuntu:
  New

Bug description:
  Referente ao python

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-gobject-2 2.28.6-12ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 10 11:46:09 2016
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  InstallationDate: Installed on 2016-09-26 (15 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.14
  SourcePackage: pygobject-2
  Title: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject-2/+bug/1632835/+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 1743727] Re: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug is no longer a duplicate of bug 1621686
   package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade:
  子进程 已安装 post-installation 脚本 返回错误状态 1

Status in pygobject-2 package in Ubuntu:
  New

Bug description:
  when pc powered up, the mistake appeared

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-gobject-2 2.28.6-12ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Jan 12 15:09:31 2018
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
  InstallationDate: Installed on 2018-01-10 (7 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: pygobject-2
  Title: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: 
子进程 已安装 post-installation 脚本 返回错误状态 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject-2/+bug/1743727/+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 1637355] Re: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug is no longer a duplicate of bug 1621686
   package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package python-gobject-2 2.28.6-12build1 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in pygobject-2 package in Ubuntu:
  New

Bug description:
  I was uninstall python2 and reinstalled

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-gobject-2 2.28.6-12build1
  ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-87-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Thu Oct 27 18:37:32 2016
  DuplicateSignature: package:python-gobject-2:2.28.6-12build1:el subproceso 
instalado el script post-installation devolvió el código de salida de error 1
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2015-12-23 (309 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: pygobject-2
  Title: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: Upgraded to trusty on 2016-10-19 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject-2/+bug/1637355/+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 1360883] Re: package apport 2.14.1-0ubuntu3.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package apport 2.14.1-0ubuntu3.2 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 1

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Reported automatically.  I did not initiate this bug report.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu3.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportLog:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Sun Aug 24 13:53:20 2014
  DuplicateSignature: package:apport:2.14.1-0ubuntu3.2:subprocess new 
pre-removal script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2014-04-23 (123 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: apport
  Title: package apport 2.14.1-0ubuntu3.2 failed to install/upgrade: subprocess 
new pre-removal 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/apport/+bug/1360883/+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 1666657] Re: package apport 2.20.1-0ubuntu2 failed to install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package apport 2.20.1-0ubuntu2 failed to install/upgrade: подпроцесс
  новый сценарий pre-removal возвратил код ошибки 1

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  The error appears after the system has started.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Feb 18 12:02:43 2017
  ErrorMessage: подпроцесс новый сценарий pre-removal возвратил код ошибки 1
  InstallationDate: Installed on 2016-11-22 (90 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2 failed to install/upgrade: подпроцесс 
новый сценарий pre-removal возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/157/+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 1667930] Re: package apport 2.20.1-0ubuntu2 failed to install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug is no longer a duplicate of bug 157
   package apport 2.20.1-0ubuntu2 failed to install/upgrade: подпроцесс новый 
сценарий pre-removal возвратил код ошибки 1
** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package apport 2.20.1-0ubuntu2 failed to install/upgrade: подпроцесс
  новый сценарий pre-removal возвратил код ошибки 1

Status in apport package in Ubuntu:
  New

Bug description:
  the error occurred when running apt dist-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Feb 25 17:33:29 2017
  ErrorMessage: подпроцесс новый сценарий pre-removal возвратил код ошибки 1
  InstallationDate: Installed on 2016-11-22 (94 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2 failed to install/upgrade: подпроцесс 
новый сценарий pre-removal возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1667930/+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 1692338] Re: package apport 2.20.1-0ubuntu2.1 failed to install/upgrade: 子进程 新的 pre-removal 脚本 返回错误状态 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package apport 2.20.1-0ubuntu2.1 failed to install/upgrade: 子进程 新的
  pre-removal 脚本 返回错误状态 1

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  sudo apt-get  -f install 
  正在读取软件包列表... 完成
  正在分析软件包的依赖关系树   
  正在读取状态信息... 完成   
  将会同时安装下列软件:
apport
  下列软件包将被升级:
apport
  升级了 1 个软件包,新安装了 0 个软件包,要卸载 0 个软件包,有 118 个软件包未被升级。
  有 74 个软件包没有被完全安装或卸载。
  需要下载 0 B/120 kB 的归档。
  解压缩后会消耗 0 B 的额外空间。
  您希望继续执行吗? [Y/n] y
  (正在读取数据库 ... 系统当前共安装有 335730 个文件和目录。)
  正准备解包 .../apport_2.20.1-0ubuntu2.4_all.deb  ...
File "/usr/bin/pyclean", line 63
  except (IOError, OSError), e:
   ^
  SyntaxError: invalid syntax
  dpkg:警告:子进程 旧的 pre-removal 脚本 返回错误状态 1
  dpkg: 现在尝试使用新软件包所带的脚本...
File "/usr/bin/pyclean", line 63
  except (IOError, OSError), e:
   ^
  SyntaxError: invalid syntax
  dpkg: 处理归档 /var/cache/apt/archives/apport_2.20.1-0ubuntu2.4_all.deb 
(--unpack)时出错:
   子进程 新的 pre-removal 脚本 返回错误状态 1
  Traceback (most recent call last):
File "/usr/bin/pycompile", line 35, in 
  from debpython.version import SUPPORTED, debsorted, vrepr, \
File "/usr/share/python/debpython/version.py", line 24, in 
  from ConfigParser import SafeConfigParser
  ImportError: No module named 'ConfigParser'
  dpkg:清理时出错:
   子进程 已安装 post-installation 脚本 返回错误状态 1
  在处理时有错误发生:
   /var/cache/apt/archives/apport_2.20.1-0ubuntu2.4_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashReports:
   600:0:116:85235:2017-05-22 09:00:58.731974601 +0800:2017-05-22 
09:00:59.731974601 +0800:/var/crash/apport.0.crash
   640:0:116:14080:2017-05-22 09:00:59.055974600 +0800:2017-05-22 
09:00:59.055974600 +0800:/var/crash/_usr_bin_pyclean.0.crash
  Date: Mon May 22 09:00:59 2017
  DpkgHistoryLog:
   Start-Date: 2017-05-22  09:00:56
   Commandline: apt-get -f install
   Requested-By: nirvana (1000)
   Upgrade: apport:amd64 (2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.4)
  ErrorMessage: 子进程 新的 pre-removal 脚本 返回错误状态 1
  InstallationDate: Installed on 2016-10-13 (220 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.1 failed to install/upgrade: 子进程 新的 
pre-removal 脚本 返回错误状态 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1692338/+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 1702734] Re: package apport 2.20.1-0ubuntu2.5 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package apport 2.20.1-0ubuntu2.5 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 1

Status in apport package in Ubuntu:
  New

Bug description:
  My system will no longer start up the default ubuntu 16.04 terminal. I
  cannot open the "software and Updates" in System settings. This
  installed Ubuntu 16.04 is falling apart

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.5
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CrashReports: 600:0:116:134735:2017-07-06 10:42:53.091179370 -0700:2017-07-06 
10:42:54.091179370 -0700:/var/crash/apport.0.crash
  Date: Thu Jul  6 10:42:53 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.5 failed to install/upgrade: subprocess 
new pre-removal 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/apport/+bug/1702734/+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 1732548] Re: package apport 2.20.1-0ubuntu2.10 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package apport 2.20.1-0ubuntu2.10 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I am not familiar with Linux, so I don't know how to describe the
  issue.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Nov 16 09:06:19 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-11-08 (7 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.10 failed to install/upgrade: 
subprocess new pre-removal 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/apport/+bug/1732548/+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 1740555] Re: package apport 2.20.1-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package apport 2.20.1-0ubuntu2 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  any

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Fri Dec 29 18:53:07 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-12-23 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1740555/+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 1740410] Re: package apport 2.20.1-0ubuntu2 failed to install/upgrade: le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package apport 2.20.1-0ubuntu2 failed to install/upgrade: le sous-
  processus nouveau script pre-removal a retourné une erreur de sortie
  d'état 1

Status in apport package in Ubuntu:
  New

Bug description:
  any

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Wed Dec 27 12:55:51 2017
  ErrorMessage: le sous-processus nouveau script pre-removal a retourné une 
erreur de sortie d'état 1
  InstallationDate: Installed on 2017-12-23 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2 failed to install/upgrade: le 
sous-processus nouveau script pre-removal a retourné une erreur de sortie 
d'état 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1740410/+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 1741146] Re: package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: sub-processo novo script pre-removal retornou estado de saída de erro 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: sub-
  processo novo script pre-removal retornou estado de saída de erro 1

Status in apport package in Ubuntu:
  New

Bug description:
  dpkg: aviso: sub-processo antigo script pre-removal retornou estado de saída 
de erro 1
  dpkg: em vez disso a tentar script do novo pacote ...
File "/usr/bin/pyclean", line 63
  except (IOError, OSError), e:
   ^
  SyntaxError: invalid syntax
  dpkg: erro ao processar o arquivo 
/var/cache/apt/archives/apport_2.20.1-0ubuntu2.15_all.deb (--unpack):
   sub-processo novo script pre-removal retornou estado de saída de erro 1
  Traceback (most recent call last):
File "/usr/bin/pycompile", line 35, in 
  from debpython.version import SUPPORTED, debsorted, vrepr, \
File "/usr/share/python/debpython/version.py", line 24, in 
  from ConfigParser import SafeConfigParser
  ImportError: No module named 'ConfigParser'
  dpkg: erro enquanto efetuava a limpeza:
   sub-processo script post-installation instalado retornou estado de saída de 
erro 1
  Erros foram encontrados durante o processamento de:
   /var/cache/apt/archives/apport_2.20.1-0ubuntu2.15_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.13
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CrashReports:
   644:0:117:0:2018-01-03 22:39:39.965581426 -0200:2018-01-03 
22:39:39.965581426 -0200:/var/crash/_usr_bin_pyclean.0.upload
   640:0:117:28098:2018-01-03 22:39:35.449562072 -0200:2018-01-03 
22:39:36.449562072 -0200:/var/crash/_usr_bin_pyclean.0.crash
   600:0:117:64346:2018-01-03 22:38:42.201278209 -0200:2018-01-03 
22:38:43.201278209 -0200:/var/crash/apport.0.crash
   640:0:117:16629:2018-01-02 22:20:43.849161573 -0200:2018-01-02 
22:20:43.845161880 -0200:/var/crash/_usr_bin_pycompile.0.crash
   600:109:117:0:2018-01-03 22:39:42.377594821 -0200:2018-01-03 
22:39:42.377594821 -0200:/var/crash/_usr_bin_pyclean.0.uploaded
  Date: Wed Jan  3 22:38:43 2018
  ErrorMessage: sub-processo novo script pre-removal retornou estado de saída 
de erro 1
  InstallationDate: Installed on 2017-11-27 (37 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: 
sub-processo novo script pre-removal retornou estado de saída de erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1741146/+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 1491565] Re: package apport 2.17.2-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package apport 2.17.2-0ubuntu1 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 1

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  It's occurs while system auto update

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: apport 2.17.2-0ubuntu1.3
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Wed Sep  2 16:05:44 2015
  DuplicateSignature: package:apport:2.17.2-0ubuntu1:subprocess new pre-removal 
script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2015-08-22 (10 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.1
  SourcePackage: apport
  Title: package apport 2.17.2-0ubuntu1 failed to install/upgrade: subprocess 
new pre-removal 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/apport/+bug/1491565/+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 1741164] Re: package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package apport 2.20.1-0ubuntu2.13 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Happened on startup, after password, loading desktop.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.13
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CrashReports:
   640:0:117:28321:2018-01-03 20:05:51.323303222 -0700:2018-01-03 
20:05:53.767416549 -0700:/var/crash/_usr_bin_pyclean.0.crash
   644:0:117:0:2018-01-03 20:05:53.767416549 -0700:2018-01-03 
20:05:53.767416549 -0700:/var/crash/_usr_bin_pyclean.0.upload
   640:0:117:94462:2018-01-03 20:05:53.363460302 -0700:2018-01-03 
20:05:54.363460302 -0700:/var/crash/apport.0.crash
   600:109:117:0:2018-01-03 20:05:55.019506896 -0700:2018-01-03 
20:05:55.019506896 -0700:/var/crash/_usr_bin_pyclean.0.uploaded
   640:0:117:16569:2018-01-03 20:05:25.257935448 -0700:2018-01-03 
20:05:25.257935448 -0700:/var/crash/_usr_bin_pycompile.0.crash
  Date: Wed Jan  3 20:05:25 2018
  DpkgHistoryLog:
   Start-Date: 2018-01-03  20:05:24
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: apport:amd64 (2.20.1-0ubuntu2.13, 2.20.1-0ubuntu2.15), 
python3-apport:amd64 (2.20.1-0ubuntu2.13, 2.20.1-0ubuntu2.15), 
libwebkit2gtk-4.0-37:amd64 (2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1), 
apport-gtk:amd64 (2.20.1-0ubuntu2.13, 2.20.1-0ubuntu2.15), 
gir1.2-webkit2-4.0:amd64 (2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1), 
libjavascriptcoregtk-4.0-18:amd64 (2.18.3-0ubuntu0.16.04.1, 
2.18.4-0ubuntu0.16.04.1), python3-problem-report:amd64 (2.20.1-0ubuntu2.13, 
2.20.1-0ubuntu2.15), libwebkit2gtk-4.0-37-gtk2:amd64 (2.18.3-0ubuntu0.16.04.1, 
2.18.4-0ubuntu0.16.04.1), gir1.2-javascriptcoregtk-4.0:amd64 
(2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1)
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-08-11 (145 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: 
subprocess new pre-removal 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/apport/+bug/1741164/+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 1781231] Re: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package apport 2.20.1-0ubuntu2.15 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in apport package in Ubuntu:
  New

Bug description:
  Get it when trying to start terminal.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.15
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Jul 11 08:32:16 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-08-11 (333 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: 
subprocess new pre-removal 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/apport/+bug/1781231/+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 1537883] Re: package lsb-release 4.1+Debian11ubuntu6 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package lsb-release 4.1+Debian11ubuntu6 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in lsb package in Ubuntu:
  Confirmed

Bug description:
  dontwork

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: lsb-release 4.1+Debian11ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-47-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Fri Jan 22 11:33:03 2016
  DuplicateSignature: package:lsb-release:4.1+Debian11ubuntu6:subprocess new 
pre-removal script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-01-14 (11 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.11
  SourcePackage: lsb
  Title: package lsb-release 4.1+Debian11ubuntu6 failed to install/upgrade: 
subprocess new pre-removal 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/lsb/+bug/1537883/+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 1888974] Re: python 2.7.17 buggy cannot run calculator python program with native python compiler 2.17.17 and geany 1.32-2 on ubuntu-mate 18.04.2 with raspberry pi 3

2020-07-26 Thread Kai Kasurinen
https://stackoverflow.com/questions/5868506/backwards-compatible-input-
calls-in-python

Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it. We understand the
difficulties you are facing, but it is better to raise problems you are
having in the support tracker at https://answers.launchpad.net/ubuntu if
you are uncertain if they are bugs. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org. For help on reporting bugs, see
https://help.ubuntu.com/community/ReportingBugs.

** Changed in: python2.7 (Ubuntu)
   Status: New => Invalid

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

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

Title:
  python 2.7.17 buggy cannot run calculator python program with native
  python compiler 2.17.17 and geany 1.32-2 on ubuntu-mate 18.04.2 with
  raspberry pi 3

Status in Ubuntu MATE:
  Invalid
Status in python2.7 package in Ubuntu:
  Invalid

Bug description:
  Hi

  I am using Raspberry pi 3 with Ubuntu-mate 18.04.2.
  I try this url link, 
https://www.programiz.com/python-programming/examples/calculator
  and copy and paste the code via nano text editor program. 
  And run using python 2.7.17. Come to find out that I unable to run the code.
  I even try Geany. It too did not work. 

  However when i run the python code from the link above with Python3.
  It work!

  I think there is a bug with Python 2.7.17 that need to be fixed.

  That goes the same to Geany.

  I wonder how am i going to run Python3 with Geany??? Any ideaas.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1888974/+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 1888985] Re: fs-uae-launcher did produce an error with python

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1887732 ***
https://bugs.launchpad.net/bugs/1887732

** This bug is no longer a duplicate of bug 1803045
package fs-uae-launcher 2.8.4+dfsg-1 failed to install/upgrade: installed 
fs-uae-launcher package post-installation script subprocess returned error exit 
status 1
** This bug has been marked a duplicate of bug 1887732
   py3compile: NameError: name 'quiet' is not defined

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

Title:
  fs-uae-launcher did produce an error with python

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  this error happened while "do-release-upgrade -d" from 18.04 to 20.04.

  i rolled back the failed do-release-upgrade (thank you btrfs!).

  after uninstalling the package "fs-uae-launcher",
  the release upgrade runs smooth.

  thank you for your attention!

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-41.45~18.04.1-lowlatency 5.4.44
  Uname: Linux 5.4.0-41-lowlatency x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  Date: Sun Jul 26 07:36:16 2020
  ErrorMessage: »installiertes python3-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 4 zurück
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: python3-defaults
  Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: 
»installiertes python3-Skript des Paketes post-installation«-Unterprozess gab 
den Fehlerwert 4 zurück
  UpgradeStatus: Upgraded to focal on 2020-07-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1888985/+subscriptions

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


  1   2   3   >