[Touch-packages] [Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131

2019-07-20 Thread Steve Langasek
** Changed in: base-files (Ubuntu)
   Status: Fix Released => Invalid

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

Title:
  9.4ubuntu4.9: Broken package because of missing "#" @
  /var/lib/dpkg/info/base-files.postinst +131

Status in base-files package in Ubuntu:
  Invalid
Status in base-files source package in Xenial:
  Fix Released

Bug description:
  Trying to install this on xenial results in:

  
  Setting up base-files (9.4ubuntu4.9) ...
  /var/lib/dpkg/info/base-files.postinst: 131: 
/var/lib/dpkg/info/base-files.postinst: Automatically: not found
  dpkg: error processing package base-files (--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   base-files
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  Because there is a missing comment "#" at the beginning of line 131 of 
/var/lib/dpkg/info/base-files.postinst, ie:

  Automatically added by dh_systemd_start
  ^-- # ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+subscriptions

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


[Touch-packages] [Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink

2019-07-20 Thread Launchpad Bug Tracker
[Expired for gdb (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  gdb doesn't search in debug-file-directory for .gnu_debugaltlink

Status in gdb package in Ubuntu:
  Expired

Bug description:
  As far as I can tell gdb version 8.2.90 isn't searching the debug-
  file-directory, which I set, for the '.gnu_debugaltlink' which is in
  the debug symbols. Here's the error I'm seeing:

  Type "apropos word" to search for commands related to "word".
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
  could not find '.gnu_debugaltlink' file for 
/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
  (No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)

  Here's part of an strace of what's going on behind the scenes:

  lstat("/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
 {st_mode=S_IFREG|0644, st_size=839744, ...}) = 0 
  openat(AT_FDCWD, 
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

  This is the only time "/usr/lib/debug" is searched, generally
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox/usr/lib/debug/" is used. I'll attach the full strace though.

  For completeness here's the gdb command I'm using:

  Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
  /report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
  --ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
  prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
  --ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
  -linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
  dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox//usr/bin/gnome-calculator"' --ex 'core-file
  /tmp/apport_core_1b6dn6np'

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

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


[Touch-packages] [Bug 1837173] Re: shall allow local save even it's neither ubuntu nor native.

2019-07-20 Thread Mathew Hodson
** Changed in: apport (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  shall allow local save even it's neither ubuntu nor native.

Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  Incomplete

Bug description:
  For command, apport-cli -p PKG -f --save=local-save.log, if the PKG is
  a local test one, it won't save the log.

  Let's skip package check if --save option is used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1837173/+subscriptions

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


[Touch-packages] [Bug 1828102] Re: Regression in ModemManager

2019-07-20 Thread Mathew Hodson
For Bionic, this bug was fixed in the package modemmanager -
1.10.0-1~ubuntu18.04.2

---
modemmanager (1.10.0-1~ubuntu18.04.2) bionic; urgency=medium

  * debian/patches/error-propagation-fix.patch: mm-broadband-modem: Fix error
propagation in CDMA service status (LP: #1819615, Upstream Issue #119).

** Tags added: regression-update

** Changed in: modemmanager (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: modemmanager (Ubuntu Cosmic)
   Importance: Undecided => High

** Changed in: modemmanager (Ubuntu Disco)
   Importance: Undecided => High

** Changed in: modemmanager (Ubuntu Eoan)
   Importance: Undecided => High

** Tags removed: regression-update
** Tags added: regression-release

** Tags added: regression-proposed

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

Title:
  Regression in ModemManager

Status in modemmanager package in Ubuntu:
  Fix Released
Status in modemmanager source package in Bionic:
  Fix Released
Status in modemmanager source package in Cosmic:
  Won't Fix
Status in modemmanager source package in Disco:
  Fix Committed
Status in modemmanager source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  ModemManager disconnects from CDMA modem after 30 sec failing to check
  signal status due to incorrect error handling

  [Test case]

  connect to a cdma device without an extra AT channel (Eg. Samsung
  brightside phone) and modemmanager will terminate the connection

  [Regression potential]

  The patch is tiny, fixing an obvious overlook, and it only affects
  CDMA broadband modems, so the risk of a regression is very low.

  [Original description]

  ModemManager disconnects after ~30 sec

  caused by a typo in 1.8

  see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615
  and
  https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119
  for details

  needs a SRU for cosmic and dingo

  patch attached

  yechiel

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

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


[Touch-packages] [Bug 1824111] Re: Backport packages for 18.04.3 HWE stack

2019-07-20 Thread Mathew Hodson
** Changed in: mesa (Ubuntu)
   Status: Invalid => Fix Released

** Changed in: llvm-toolchain-8 (Ubuntu)
   Status: Invalid => Fix Released

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

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

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

Title:
  Backport packages for 18.04.3 HWE stack

Status in OEM Priority Project:
  Confirmed
Status in libclc package in Ubuntu:
  Fix Released
Status in libdrm package in Ubuntu:
  Fix Released
Status in llvm-toolchain-8 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in libclc source package in Bionic:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-8 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.3 images.

  [Test case]

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

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

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

  libclc: more or less just adds support for new llvm

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

  xserver: a new minor release

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1824111/+subscriptions

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


[Touch-packages] [Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131

2019-07-20 Thread Mathew Hodson
** Changed in: base-files (Ubuntu)
   Status: Invalid => Fix Released

** Tags removed: verification-needed

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

Title:
  9.4ubuntu4.9: Broken package because of missing "#" @
  /var/lib/dpkg/info/base-files.postinst +131

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released

Bug description:
  Trying to install this on xenial results in:

  
  Setting up base-files (9.4ubuntu4.9) ...
  /var/lib/dpkg/info/base-files.postinst: 131: 
/var/lib/dpkg/info/base-files.postinst: Automatically: not found
  dpkg: error processing package base-files (--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   base-files
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  Because there is a missing comment "#" at the beginning of line 131 of 
/var/lib/dpkg/info/base-files.postinst, ie:

  Automatically added by dh_systemd_start
  ^-- # ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+subscriptions

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


[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2019-07-20 Thread Mathew Hodson
** Bug watch removed: Red Hat Bugzilla #1151544
   https://bugzilla.redhat.com/show_bug.cgi?id=1151544

** Bug watch removed: github.com/systemd/systemd/issues #3421
   https://github.com/systemd/systemd/issues/3421

** Bug watch removed: GNOME Bug Tracker #746422
   https://gitlab.gnome.org/746422

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Zesty:
  Won't Fix
Status in network-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1624317/+subscriptions

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


[Touch-packages] [Bug 1837300] Re: /usr/bin/locale-check is missing from bionic LTS versions

2019-07-20 Thread Steve Langasek
Downgrading is not supported.

Downgrading with the result that files / bugfixes present in the
-updates pocket are not installed because you only installed from the
release pocket is not a bug in Ubuntu.  Any changes we make to a stable
release after GA land only in the -updates pocket, never in the release
pocket.  So there is nothing we would change here to make this problem
go away.

The reason you saw the error is that /etc/profile.d/01-locale-fix.sh and
/usr/bin/locale-check were both introduced to bionic after release, so
are only in bionic-updates.  However, /usr/bin/locale-check is a regular
packaged file, and /etc/profile.d/01-locale-fix.sh is a conffile; which
means that on downgrade, /usr/bin/locale-check is removed because it's
not part of the older package, but /etc/profile.d/01-locale-fix.sh is
not removed because conffiles are only removed with additional handling
via the maintainer scripts, and there is no handling that would remove
this conffile as part of a downgrade.

Almost no conffiles are correctly removed on downgrade to a version of
the package earlier than the version which introduced the conffile.

This is why downgrades are not supported.

** Changed in: base-files (Ubuntu)
   Status: New => Invalid

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

Title:
  /usr/bin/locale-check is missing from bionic LTS versions

Status in base-files package in Ubuntu:
  Invalid

Bug description:
  After downgrading from 19.04 to 18.04 (which involved a bunch of `apt
  remove --purge` and manual dependency conflict resolution) I had the
  following error on logging into my machine:

  ```
  bash: /usr/bin/locale-check: No such file or directory
  ```

  On investigation, it seems that this file is supposed to be provided
  by `base-files`, but it is not present in the two current LTS versions
  (10.1ubuntu2 and 10.2ubuntu2.2).

  ```
  tl@hotbox:~$ apt download base-files=10.1ubuntu2
  Get:1 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 base-files amd64 
10.1ubuntu2 [58.2 kB]
  Fetched 58.2 kB in 0s (1,000 kB/s)
  tl@hotbox:~$ apt download base-files=10.1ubuntu2.2
  Get:1 http://security.ubuntu.com/ubuntu bionic-security/main amd64 base-files 
amd64 10.1ubuntu2.2 [58.2 kB]
  Fetched 58.2 kB in 0s (189 kB/s)
  tl@hotbox:~$ dpkg -c base-files_10.1ubuntu2_amd64.deb | rg "/usr/bin"
  drwxr-xr-x root/root 0 2018-04-24 04:34 ./usr/bin/
  tl@hotbox:~$ dpkg -c base-files_10.1ubuntu2.2_amd64.deb | rg "/usr/bin"
  drwxr-xr-x root/root 0 2018-08-20 09:44 ./usr/bin/
  ```

  It is present in `bionic-updates` which is currently `10.1ubuntu2.5`,
  however.

  The reason I think this happened to this system in particular is that
  as part of the dist-downgrade process I added the following to
  `/etc/apt/preferences`:

  ```
  Package: *
  Pin: release a=bionic
  Pin-Priority: 1001
  ```

  This appears to have prevented me from getting `bionic-updates`.
  Removing this file allows apt to install `base-files` from `bionic-
  updates` and resolved the issue for me.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1837300/+subscriptions

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


[Touch-packages] [Bug 1837300] [NEW] /usr/bin/locale-check is missing from bionic LTS versions

2019-07-20 Thread Tony Lykke
Public bug reported:

After downgrading from 19.04 to 18.04 (which involved a bunch of `apt
remove --purge` and manual dependency conflict resolution) I had the
following error on logging into my machine:

```
bash: /usr/bin/locale-check: No such file or directory
```

On investigation, it seems that this file is supposed to be provided by
`base-files`, but it is not present in the two current LTS versions
(10.1ubuntu2 and 10.2ubuntu2.2).

```
tl@hotbox:~$ apt download base-files=10.1ubuntu2
Get:1 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 base-files amd64 
10.1ubuntu2 [58.2 kB]
Fetched 58.2 kB in 0s (1,000 kB/s)
tl@hotbox:~$ apt download base-files=10.1ubuntu2.2
Get:1 http://security.ubuntu.com/ubuntu bionic-security/main amd64 base-files 
amd64 10.1ubuntu2.2 [58.2 kB]
Fetched 58.2 kB in 0s (189 kB/s)
tl@hotbox:~$ dpkg -c base-files_10.1ubuntu2_amd64.deb | rg "/usr/bin"
drwxr-xr-x root/root 0 2018-04-24 04:34 ./usr/bin/
tl@hotbox:~$ dpkg -c base-files_10.1ubuntu2.2_amd64.deb | rg "/usr/bin"
drwxr-xr-x root/root 0 2018-08-20 09:44 ./usr/bin/
```

It is present in `bionic-updates` which is currently `10.1ubuntu2.5`,
however.

The reason I think this happened to this system in particular is that as
part of the dist-downgrade process I added the following to
`/etc/apt/preferences`:

```
Package: *
Pin: release a=bionic
Pin-Priority: 1001
```

This appears to have prevented me from getting `bionic-updates`.
Removing this file allows apt to install `base-files` from `bionic-
updates` and resolved the issue for me.

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  /usr/bin/locale-check is missing from bionic LTS versions

Status in base-files package in Ubuntu:
  New

Bug description:
  After downgrading from 19.04 to 18.04 (which involved a bunch of `apt
  remove --purge` and manual dependency conflict resolution) I had the
  following error on logging into my machine:

  ```
  bash: /usr/bin/locale-check: No such file or directory
  ```

  On investigation, it seems that this file is supposed to be provided
  by `base-files`, but it is not present in the two current LTS versions
  (10.1ubuntu2 and 10.2ubuntu2.2).

  ```
  tl@hotbox:~$ apt download base-files=10.1ubuntu2
  Get:1 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 base-files amd64 
10.1ubuntu2 [58.2 kB]
  Fetched 58.2 kB in 0s (1,000 kB/s)
  tl@hotbox:~$ apt download base-files=10.1ubuntu2.2
  Get:1 http://security.ubuntu.com/ubuntu bionic-security/main amd64 base-files 
amd64 10.1ubuntu2.2 [58.2 kB]
  Fetched 58.2 kB in 0s (189 kB/s)
  tl@hotbox:~$ dpkg -c base-files_10.1ubuntu2_amd64.deb | rg "/usr/bin"
  drwxr-xr-x root/root 0 2018-04-24 04:34 ./usr/bin/
  tl@hotbox:~$ dpkg -c base-files_10.1ubuntu2.2_amd64.deb | rg "/usr/bin"
  drwxr-xr-x root/root 0 2018-08-20 09:44 ./usr/bin/
  ```

  It is present in `bionic-updates` which is currently `10.1ubuntu2.5`,
  however.

  The reason I think this happened to this system in particular is that
  as part of the dist-downgrade process I added the following to
  `/etc/apt/preferences`:

  ```
  Package: *
  Pin: release a=bionic
  Pin-Priority: 1001
  ```

  This appears to have prevented me from getting `bionic-updates`.
  Removing this file allows apt to install `base-files` from `bionic-
  updates` and resolved the issue for me.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1837300/+subscriptions

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


[Touch-packages] [Bug 1826730] Re: [ASUS X555YI] audio crackle when the sound a little loud.

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

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

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

Title:
  [ASUS X555YI] audio crackle when the sound a little loud.

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  both mpv and vlc have this problem, even when I use firefox see youtube 
video, if I turn the sound a little loud, the sound will with a lot of crackle 
sound.
  I ubuntu18.04 all the thing update to date.
  widon@widon-X555YI:~$ dpkg -l | grep pulseaudio
  ii  gstreamer1.0-pulseaudio:amd64 
1.14.1-1ubuntu1~ubuntu18.04.1amd64GStreamer plugin for 
PulseAudio
  ii  pulseaudio1:11.1-1ubuntu7.2   
 amd64PulseAudio sound server
  ii  pulseaudio-module-bluetooth   1:11.1-1ubuntu7.2   
 amd64Bluetooth module for PulseAudio sound server
  ii  pulseaudio-utils  1:11.1-1ubuntu7.2   
 amd64Command line tools for the PulseAudio sound server
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  widon  1517 F pulseaudio
   /dev/snd/controlC0:  widon  1517 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-24 (156 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: pulseaudio 1:11.1-1ubuntu7.2 [origin: unknown]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-46-generic x86_64
  UnreportableReason: 这不是官方的 Ubuntu 软件包。请删除所有第三方软件包,然后重试。
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555YI.510
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555YI
  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.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555YI
  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/linux/+bug/1826730/+subscriptions

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


[Touch-packages] [Bug 1837289] Re: yes

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

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

At a minimum, we need:

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

Thanks!

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

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

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

Title:
  yes

Status in Ubuntu:
  Incomplete

Bug description:
  no

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 20 22:26:07 2019
  InstallationDate: Installed on 2019-06-11 (39 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1837289] [NEW] yes

2019-07-20 Thread Raza Rizvi
Public bug reported:

no

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-25-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul 20 22:26:07 2019
InstallationDate: Installed on 2019-06-11 (39 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic wayland-session

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

Title:
  yes

Status in xorg package in Ubuntu:
  New

Bug description:
  no

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 20 22:26:07 2019
  InstallationDate: Installed on 2019-06-11 (39 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1837284] [NEW] Initial installation does not allow high graphics resolution. Requires disabling Wayland and using Nvidia proprietary driver.

2019-07-20 Thread Predrag Bokšić
Public bug reported:

1. Booting the system from USB 3.0 stick does not show any indication of
graphics problems.

2. Upon the installation to a hard drive, the graphics resolution is
below standard and cannot be changed in the system settings.

3. By installing the Nvidia driver and rebooting the system, I find that
there is no graphics desktop available; apparently, level 5 was not
fully reached. There is a workaround for this. I can try to press
CTRL+F2 and then CTRL+F1 and the high-resolution graphical desktop
becomes apparent. Switching terminals allows me to go to the graphical
session.

4. Disabling Wayland in the appropriate configuration file allows the
system to become fully functional.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
 GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul 20 16:34:26 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 418.56, 5.0.0-19-generic, x86_64: installed
 nvidia, 418.56, 5.0.0-20-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GM204 [GeForce GTX 970] 
[1462:3160]
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0dfd5d83-cd3e-4f06-bae7-d9db4e171814 verbose nomodeset
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/22/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2903
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97M-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2903:bd02/22/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco ubuntu

** Summary changed:

- Initial installation does not allow high resolution. Requires disabling 
Wayland and using Nvidia.
+ Initial installation does not allow high resolution. Requires disabling 
Wayland and using Nvidia proprietary driver.

** Summary changed:

- Initial installation does not allow high resolution. Requires disabling 
Wayland and using Nvidia proprietary driver.
+ Initial installation does not allow high graphics resolution. Requires 
disabling Wayland and using Nvidia proprietary driver.

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

Title:
  Initial installation does not allow high graphics resolution. Requires
  disabling Wayland and using Nvidia proprietary driver.

Status in xorg package in Ubuntu:
  New

Bug description:
  1. Booting the system from USB 3.0 stick does not show any indication
  of graphics problems.

  2. Upon the installation to a hard drive, the graphics resolution is
  below standard and cannot be changed in the system settings.

  3. By installing the Nvidia driver and rebooting the system, I find
  that there is no graphics desktop available; apparently, level 5 was
  not fully reached. There is a workaround for this. I can try to press
  CTRL+F2 and then CTRL+F1 and the high-resolution graphical desktop
  becomes apparent. Switching terminals allows me to go to the 

[Touch-packages] [Bug 1418885] Re: Gstreamer critical warning

2019-07-20 Thread Paul White
** Changed in: gstreamer1.0 (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Gstreamer critical warning

Status in gstreamer1.0 package in Ubuntu:
  Invalid

Bug description:
  Hi everybody,
  I have the following GStreamer-CRITICAL warning and I can't get rid of it:

  $ gst-launch-1.0 souphttpsrc location="http://IP/video.cgi?videocodec=h264;
  user-id=USER user-pw=PASSWORD do-timestamp=true ! multipartdemux ! fakesink
  Setting pipeline to PAUSED ...
  Pipeline is PREROLLING ...
  Pipeline is PREROLLED ...
  Setting pipeline to PLAYING ...
  New clock: GstSystemClock
  ^Chandling interrupt.
  Interrupt: Stopping pipeline ...
  Execution ended after 0:00:01.692054125
  Setting pipeline to PAUSED ...
  Setting pipeline to READY ...

  (gst-launch-1.0:12437): GStreamer-CRITICAL **: gst_mini_object_unref: 
assertion
  'mini_object->refcount > 0' failed
  Setting pipeline to NULL ...
  Freeing pipeline ...

  (For the warning to appear I pressed CTRL-C for stopping the stream.)
  It seems that it is from the multipartdemux element, if I execute the command
  without it the warning does not appear.

  I am using Gstreamer 1.4.5.

  I saw this link (which seems to describe the problem that I have) but I 
couldn't use it with Gstreamer 1.0 :
  https://wiki.archlinux.org/index.php/GStreamer

  It is very important to me to fix this warning. Can somebody help me
  with a fix?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1418885/+subscriptions

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


[Touch-packages] [Bug 1418885] Re: Gstreamer critical warning

2019-07-20 Thread Paul White
Bug did not expire due to bug watch
Upstream report was closed "RESOLVED INCOMPLETE" on 2016-02-22
Reporter last commented over 4 years ago
No reply to comment #2 after more than 60 days so closing

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

Title:
  Gstreamer critical warning

Status in gstreamer1.0 package in Ubuntu:
  Incomplete

Bug description:
  Hi everybody,
  I have the following GStreamer-CRITICAL warning and I can't get rid of it:

  $ gst-launch-1.0 souphttpsrc location="http://IP/video.cgi?videocodec=h264;
  user-id=USER user-pw=PASSWORD do-timestamp=true ! multipartdemux ! fakesink
  Setting pipeline to PAUSED ...
  Pipeline is PREROLLING ...
  Pipeline is PREROLLED ...
  Setting pipeline to PLAYING ...
  New clock: GstSystemClock
  ^Chandling interrupt.
  Interrupt: Stopping pipeline ...
  Execution ended after 0:00:01.692054125
  Setting pipeline to PAUSED ...
  Setting pipeline to READY ...

  (gst-launch-1.0:12437): GStreamer-CRITICAL **: gst_mini_object_unref: 
assertion
  'mini_object->refcount > 0' failed
  Setting pipeline to NULL ...
  Freeing pipeline ...

  (For the warning to appear I pressed CTRL-C for stopping the stream.)
  It seems that it is from the multipartdemux element, if I execute the command
  without it the warning does not appear.

  I am using Gstreamer 1.4.5.

  I saw this link (which seems to describe the problem that I have) but I 
couldn't use it with Gstreamer 1.0 :
  https://wiki.archlinux.org/index.php/GStreamer

  It is very important to me to fix this warning. Can somebody help me
  with a fix?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1418885/+subscriptions

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


[Touch-packages] [Bug 1835376] Re: package libvlc-bin:amd64 3.0.6-1 failed to install/upgrade: triggers looping, abandoned

2019-07-20 Thread Vlad Orlov
*** This bug is a duplicate of bug 1828639 ***
https://bugs.launchpad.net/bugs/1828639

** This bug has been marked a duplicate of bug 1828639
   Unlooping all the trigger loops!

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

Title:
  package libvlc-bin:amd64 3.0.6-1 failed to install/upgrade: triggers
  looping, abandoned

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  failed when i tried to do a partial upgrade because last upgrade
  already failed.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: libvlc-bin:amd64 3.0.6-1
  ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Thu Jul  4 10:16:45 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-04-06 (88 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: N/A
  SourcePackage: vlc
  Title: package libvlc-bin:amd64 3.0.6-1 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1835376/+subscriptions

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