[Touch-packages] [Bug 1801394] Re: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

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

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  設定 lvm2 (2.02.176-4.1ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Failed to restart lvm2-lvmetad.service: Unit lvm2-lvmetad.socket is masked.
  invoke-rc.d: initscript lvm2-lvmetad, action "restart" failed.
  ● lvm2-lvmetad.service - LVM2 metadata daemon
 Loaded: loaded (/lib/systemd/system/lvm2-lvmetad.service; static; vendor 
preset: enabled)
 Active: inactive (dead)
   Docs: man:lvmetad(8)

  11月 02 21:51:31 longman-UX510UX systemd[1]: Started LVM2 metadata daemon.
  11月 03 00:05:57 longman-UX510UX systemd[1]: Stopping LVM2 metadata daemon...
  11月 03 00:05:57 longman-UX510UX systemd[1]: Stopped LVM2 metadata daemon.
  dpkg: error processing package lvm2 (--configure):
   installed lvm2 package post-installation script subprocess returned error 
exit status 1
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for systemd (237-3ubuntu10.3) ...
  Processing triggers for initramfs-tools (0.130ubuntu3.5) ...
  update-initramfs: Generating /boot/initrd.img-4.15.0-38-generic
  處理時發生錯誤：
   lvm2
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: lvm2 2.02.176-4.1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Sat Nov  3 01:10:15 2018
  ErrorMessage: installed lvm2 package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2017-11-17 (350 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: lvm2
  Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed 
lvm2 package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-10-30 (2 days ago)

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

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

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[sojusnik]

@Ben

Thanks!

Patching and compiling the kernel is out of my league. I prefer the
user-friendly and "foolproof" way through the Kernel Update Utility for
Ubuntu (UKUU), mentioned above. Afaik, I can't edit the patch_realtek.c
file when doing so with UKUU.

Do you know if it's already planned to merge the UX391UA line too? If
not, can somebody mention this to the kernel developers.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  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/alsa-driver/+bug/1784485/+subscriptions

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

[Touch-packages] [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal

[Dariusz Gadomski]

According to my tests GDM works as expected - checking groups the user
belongs to on different terminal emulators (e.g. xterm) proves that the
/etc/security/group.conf groups are correctly applied.

The problem in this case affects gnome-terminal alone (and the problem
is present also if using e.g. LightDM instead of GDM).

This is related to the way gnome-terminal-server is started via DBus and
executed under systemd --user. It is started under the systemd-user PAM
service, so pam_group entry should be added to /etc/pam.d/systemd-user.
The problem is systemd will never apply pam_group settings because it
does not call pam_setcred.

The issue is reported to systemd along with a PR fixing it:
https://github.com/systemd/systemd/issues/11198

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

** Also affects: gnome-terminal via
   https://github.com/systemd/systemd/issues/11198
   Importance: Unknown
   Status: Unknown

** Project changed: gnome-terminal => systemd

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

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

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

Title:
  pam_group.so is not evaluated by gnome-terminal

Status in systemd:
  Unknown
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1808864] Re: Poor translation of zh_CN gpasswd(1) man page

[Sebastien Bacher]

** Also affects: language-pack-zh (Ubuntu)
   Importance: Undecided
   Status: New

** Package changed: language-pack-zh (Ubuntu) => language-pack-zh-hans
(Ubuntu)

** Also affects: ubuntu-translations
   Importance: Undecided
   Status: New

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

Title:
  Poor translation of zh_CN gpasswd(1) man page

Status in Ubuntu Translations:
  New
Status in language-pack-zh-hans package in Ubuntu:
  New
Status in shadow package in Ubuntu:
  New

Bug description:
  man -l /usr/share/man/zh_CN/man1/gpasswd.1.gz

  The zh_CN version of gpasswd(1) not only is partially done, but also
  contains an error in the first sentence. The translator confused the
  verb "administer" with the person "administrator." The section
  heading, originally "Notes (noun) about group passwords," was
  translated as "Please note (verb) the group passwords." Even Google
  translate does better!

  Translation errors
  ==
  gpasswd - administer /etc/group and /etc/gshadow
  gpasswd - 管理员 /etc/group 和 /etc/gshadow
^^ 管理员 -- administrator
   管理 -- administer

  Notes about group passwords
  请注意组密码
  ^^ 请注意…… -- please note (v.)
 关于……的说明 -- notes (n.) about

  Typos
  =
  -h, --help
  Display help message and exit.

  -h, --help
  现实帮助信息并退出。
   显示 Xiǎnshì -- display
   现实 Xiànshí -- reality

  Correct Google translate results (this but unironically)
  
  "gpasswd - administer /etc/group and /etc/gshadow"
  "gpasswd - 管理 /etc/group 和 /etc/gshadow"

  "Notes about group passwords"
  "关于组密码的说明"

  "Display help message and exit."
  "显示帮助消息并退出。"

  Notes about my system
  =
  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04
  $ apt-cache policy passwd
  passwd:
Installed: 1:4.5-1ubuntu1
Candidate: 1:4.5-1ubuntu1
Version table:
   *** 1:4.5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~osomon/network-manager/+git/network-manager/+merge/361051

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Confirmed

Bug description:
  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

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

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

[Touch-packages] [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => New

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

Title:
  pam_group.so is not evaluated by gnome-terminal

Status in systemd:
  New
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

[Kai-Heng Feng]

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Confirmed
Status in gnome-control-center source package in Bionic:
  New
Status in gnome-shell source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in upower source package in Bionic:
  New

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  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/gnome-control-center/+bug/1745032/+subscriptions

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

[Touch-packages] [Bug 1187981] Re: symbol conflicts in libtimezonemap1

[Sebastien Bacher]

that's not an issue in recent versions

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  symbol conflicts in libtimezonemap1

Status in gnome-control-center:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in libtimezonemap package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Incomplete
Status in unity-control-center package in Ubuntu:
  Incomplete

Bug description:
  In gnome-control-center 3.8 all built in panels are statically linked.
  When the indicator-datetime panel loads it is picking up the symbols
  from the gnome datetime panel rather than the ones in libtimezonemap1,
  causing g-c-c to segfault.

  All public symbols in libtimezonemap1 need to renamed to avoid
  conflict. Likewise this might apply to any other g-c-c plugins that
  have code cut+paste from the built in gnome panels.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 12.10.3daily13.05.06.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Thu Jun  6 12:35:40 2013
  InstallationDate: Installed on 2012-09-23 (256 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)
  MarkForUpload: True
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1187981/+subscriptions

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

[Touch-packages] [Bug 1806458] Re: Intel I219-V ethernet connection lost

[corrado venturini]

Last time I had the problem was dec 10 20:08 and I was using Ubuntu 19.04 with 
kernel 4.20rc5 and network-manager version 1.12.4. 
Since then I have not had the problem but I used kernel 4.20rc6 and 4.20rc7 
also network-manager has changed to 1.12.6-0ubuntu2 and firefox has been 
updated too.
If the problem reappears I will do more test.
thanks

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

Title:
  Intel I219-V ethernet connection lost

Status in systemd package in Ubuntu:
  New

Bug description:
  Ethernet connection id dropped randomly, sometimes works fine for the whole 
day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this 
bug being unable to add usable info to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar.
  I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with 
standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel.
  When the connection drops i can restart it just closing and restarting the 
net.
  Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm 
forced to do reconnect to send the doc.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: systemd 239-7ubuntu14
  Uname: Linux 4.20.0-042000rc4-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  3 18:33:12 2018
  InstallationDate: Installed on 2018-11-07 (26 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic 
root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-11-07 (26 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: systemd 239-7ubuntu14
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Tags:  wayland-session disco
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsIn

[Touch-packages] [Bug 1656100] Re: Unable to remove signing keys using gnome-software-properties

[Carlo Vanini]

** Branch linked: lp:~silhusk/software-properties/lp1656100-remove-
signing-keys

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

Title:
  Unable to remove signing keys using gnome-software-properties

Status in Ubuntu GNOME:
  Invalid
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  I have found that on Ubuntu GNOME 16.10 with GNOME 3.22 that I am
  unable to remove signing keys in the Authentication tab. If I select a
  key I wish to remove and click the Remove button, either nothing will
  happen, or it will ask me for authentication, upon giving it the
  correct password all that will happen is it will deselect the key I
  select, but at no point will it actually remove it, which is rather
  annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: software-properties-gtk 0.96.24.7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jan 12 21:35:55 2017
  InstallationDate: Installed on 2017-01-09 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore

[Colin Watson]

** Attachment removed: "printer.png"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721223/+attachment/5223123/+files/printer.png

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

Title:
  Networkd fail to set ip address between leases if ip address changes
  on UbuntuCore

Status in Snappy:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * networkd fails to renew a lease, specifically it fails to change IPv4 
address via DHCP renew/rebind.
   * networkd relies on a kernel feature to promote secondary IPv4 address to 
primary, upon primary address lease expiry.
   * this sysctl tunable was not enabled by default in systemd.

  [Test Case]

  Add a device, and assign two IPv4 addresses. First one, with a short
  lease time. Second one, with a different ip and a longer lease time.
  Second one should be treated as secondary ip address, and upon expiry
  of the first one, should be promoted and become primary ip address.
  The below scripted instructions simulate this:

  sudo ip link add name testleases type dummy

  sudo ip address add 192.0.2.10/27 dev testleases \
    valid_lft 5 preferred_lft 5

  sudo ip address add 192.0.2.11/27 dev testleases \
    valid_lft 11 preferred_lft 11

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \
  && echo ok || echo not ok

  sleep 6

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  sudo ip link del dev testleases

  [Regression Potential]

   * This changes the default kernel behaviour, previously upon expiry
  of the primary address, secondary addresses were removed as well.
  Which is imho silly.

  * comparing networkd renewal with isc-dhcp renewal the semantics are
  quite different. Upon acquiring new ip address, isc-dhcp would
  instantly flush existing ip address, and add a new one. Networkd add
  the new address as secondary, and waits for old one to expire first
  before promoting / switching to using the new ip address. IMHO kernel
  should have an API to promote secondary ip address to a primary one.

  * This update also applies other safe-looking options, which are
  currently also already applied via sysctls shipped in other packages

  # Source route verification
  net.ipv4.conf.default.rp_filter = 1
  net.ipv4.conf.all.rp_filter = 1

  # Do not accept source routing
  net.ipv4.conf.default.accept_source_route = 0
  net.ipv4.conf.all.accept_source_route = 0

  # Enable hard and soft link protection
  fs.protected_hardlinks = 1
  fs.protected_symlinks = 1

  * This update also applies the following upstream/bufferbloat.net
  recommended setting

  # Fair Queue CoDel packet scheduler to fight bufferbloat
  net.core.default_qdisc = fq_codel

  * [~racb] There are complex network setups out there, such as HA with
  corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this
  fix were SRU'd, will all of these things in the wild cope with this
  sysctl change?

  [Other Info]

   * Original bug report

  Hi there,
  we found a replicable issue that involves the Ubuntu Core networking and 
causes complete loss of connectivity.
  We run a custom board with ubuntu core: the architecure is amrhf.
  We replicated this issue with an official Ubuntu Core image on a Raspberry 
Pi: other platform was been tested.
  It shows that it is a snap core problem which interests networkd: we use the 
default network stack based on networkd + netplan.

  Below steps to replicate the issue.

  1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes).
  2)Boot the board and wait for get an ip from dhcp server
  3)Before the lease expires, set a reservation for a different ip address

  Depending on lease duration before the lease expires( for 10 minute we have 2 
minutes before ), networkd configure the new address in addition to the 
previous one.
  When the lease expire both ip address ( the prevoius and the new one ) 
disappear from the interested network interface.
  Depending on lease duration before the second lease expires ( for 10 minure 
we have 2 minutes before ) networkd configure only the new ip address on the 
network interface and the ping toward an outside host work properly.

  During the test the dhcp server records correctly leases and their
  duration.

  We check directly from console the network interface setting with the
  tool ip, checking continuously the value for ip address and vali

[Touch-packages] [Bug 1753776]

[Gitlab-migration]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/xserver/issues/33.

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

Title:
  Graphics corruption just before login animation to Xorg sessions
  (Intel gen9 GPUs only)

Status in Mesa:
  Unknown
Status in gdm3 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in wayland package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  Invalid
Status in mesa source package in Bionic:
  Fix Released
Status in wayland source package in Bionic:
  Invalid

Bug description:
  Immediately after login (I enter the password and hit enter) the screen 
"crumbles" for few seconds, then all becomes normal and the system works fine. 
I have done apt update+upgrade many times, also with proposed enabled, I have 
also installed a new ISO (now i'm using the Alpha dated 20180305) but the 
problem remains. The problem happens with the x11 session but not with wayland. 
  Also problem does not show with different hardware. 

  corrado@corrado-p7-bb-0305:~$ inxi -Fx
  System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 
gcc: 7.3.0
 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu 
Bionic Beaver (development branch)
  Machine:   Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: 
American Megatrends v: P1.10 date: 05/11/2017
  CPU:   Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 
3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 
3081 MHz
  Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 
1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes
  Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 
00:1f.3
 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic
  Network:   Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 
3.2.6-k bus-ID: 00:1f.6
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86
  Drives:HDD Total Size: 1000.2GB (1.3% used)
 ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB
  Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7
 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 38.5C mobo: N/A
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: 
systemd runlevel: 5 Gcc sys: N/A
 Client: Shell (bash 4.4.181) inxi: 2.3.56 
  corrado@corrado-p7-bb-0305:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  6 15:47:50 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2018-03-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.ver

[Touch-packages] [Bug 1753776] Re: Graphics corruption just before login animation to Xorg sessions (Intel gen9 GPUs only)

[Bug Watch Updater]

** Changed in: mesa
   Status: Confirmed => 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/1753776

Title:
  Graphics corruption just before login animation to Xorg sessions
  (Intel gen9 GPUs only)

Status in Mesa:
  Unknown
Status in gdm3 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in wayland package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  Invalid
Status in mesa source package in Bionic:
  Fix Released
Status in wayland source package in Bionic:
  Invalid

Bug description:
  Immediately after login (I enter the password and hit enter) the screen 
"crumbles" for few seconds, then all becomes normal and the system works fine. 
I have done apt update+upgrade many times, also with proposed enabled, I have 
also installed a new ISO (now i'm using the Alpha dated 20180305) but the 
problem remains. The problem happens with the x11 session but not with wayland. 
  Also problem does not show with different hardware. 

  corrado@corrado-p7-bb-0305:~$ inxi -Fx
  System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 
gcc: 7.3.0
 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu 
Bionic Beaver (development branch)
  Machine:   Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: 
American Megatrends v: P1.10 date: 05/11/2017
  CPU:   Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 
3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 
3081 MHz
  Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 
1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes
  Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 
00:1f.3
 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic
  Network:   Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 
3.2.6-k bus-ID: 00:1f.6
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86
  Drives:HDD Total Size: 1000.2GB (1.3% used)
 ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB
  Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7
 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 38.5C mobo: N/A
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: 
systemd runlevel: 5 Gcc sys: N/A
 Client: Shell (bash 4.4.181) inxi: 2.3.56 
  corrado@corrado-p7-bb-0305:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  6 15:47:50 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2018-03-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product

[Touch-packages] [Bug 1718254] Re: please drop url-dispatcher dependencies

[Will Cooke]

** Tags removed: rls-bb-incoming
** Tags added: rls-bb-notifixing

** Tags removed: rls-bb-notifixing
** Tags added: rls-bb-notfixing

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

Title:
  please drop url-dispatcher dependencies

Status in indicator-datetime package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  New
Status in unity-greeter-session-broadcast package in Ubuntu:
  New

Bug description:
  please drop url-dispatcher dependencies

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1718254/+subscriptions

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

[Touch-packages] [Bug 1808990] [NEW] Xorg freeze

[AlejandroHueto]

Public bug reported:

The screen appears to freeze, with possible SSH access from another machine 
during the first minutes. After that, the system totally freezes, with not even 
ethernet connection anymore.
Only hard reboot helps to solve the issue, with normal functionality afterwards.
It occurs in a random way.

Ubuntu version 18.04.1 LTS.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 18 15:32:13 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.18, 4.15.0-39-generic, x86_64: installed
 virtualbox, 5.2.18, 4.15.0-42-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GpuHangFrequency: Once a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 NVIDIA Corporation GK208 [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 730] [1043:850c]
InstallationDate: Installed on 2018-11-14 (34 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
 Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=7af5a6a3-c5c3-48e2-9477-704034a9e379 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/07/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1804
dmi.board.asset.tag: Default string
dmi.board.name: Z170-P
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1804:bd06/07/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
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 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic freeze ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  The screen appears to freeze, with possible SSH access from another machine 
during the first minutes. After that, the system totally freezes, with not even 
ethernet connection anymore.
  Only hard reboot helps to solve the issue, with normal functionality 
afterwards.
  It occurs in a random way.

  Ubuntu version 18.04.1 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 18 15:32:13 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-39-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GpuHangFrequency: Once a week
  GpuHangReproducibility: Seems to happen r

[Touch-packages] [Bug 1806076] Re: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii

[Julian Andres Klode]

** Changed in: apt (Ubuntu)
   Status: New => Fix Committed

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

Title:
  unattended-upgrade --help raises UnicodeEncodeError when stdout
  encoding is ascii

Status in apt package in Ubuntu:
  Fix Committed
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  [Test Case]

  rbalint@yogi:~$ lxc launch ubuntu:18.04 bb-lp-1806076
  Creating bb-lp-1806076
  Starting bb-lp-1806076
  rbalint@yogi:~$ lxc shell bb-lp-1806076
  mesg: ttyname failed: No such device
  root@bb-lp-1806076:~# apt install -yqq language-pack-ru-base
  The following package was automatically installed and is no longer required:
    libfreetype6
  Use 'apt autoremove' to remove it.
  The following additional packages will be installed:
    language-pack-ru
  The following NEW packages will be installed:
    language-pack-ru language-pack-ru-base
  0 upgraded, 2 newly installed, 0 to remove and 7 not upgraded.
  Need to get 2310 kB of archives.
  After this operation, 11.8 MB of additional disk space will be used.
  Selecting previously unselected package language-pack-ru-base.
  (Reading database ... 28536 files and directories currently installed.)
  Preparing to unpack .../language-pack-ru-base_1%3a18.04+20180712_all.deb ...
  Unpacking language-pack-ru-base (1:18.04+20180712) ...
  Selecting previously unselected package language-pack-ru.
  Preparing to unpack .../language-pack-ru_1%3a18.04+20180712_all.deb ...
  Unpacking language-pack-ru (1:18.04+20180712) ...
  Setting up language-pack-ru (1:18.04+20180712) ...
  Setting up language-pack-ru-base (1:18.04+20180712) ...
  Generating locales (this might take a while)...
    ru_RU.UTF-8... done
    ru_UA.UTF-8... done
  Generation complete.
  root@bb-lp-1806076:~# env LANG=ru_RU unattended-upgrade --help | cat
  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 1983, in 
  (options, args) = parser.parse_args()  # type: ignore
    File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args
  stop = self._process_args(largs, rargs, values)
    File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args
  self._process_long_opt(rargs, values)
    File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt
  option.process(opt, value, values, self)
    File "/usr/lib/python3.6/optparse.py", line 785, in process
  self.action, self.dest, opt, value, values, parser)
    File "/usr/lib/python3.6/optparse.py", line 807, in take_action
  parser.print_help()
    File "/usr/lib/python3.6/optparse.py", line 1647, in print_help
  file.write(self.format_help())
  UnicodeEncodeError: 'ascii' codec can't encode characters in position 
126-133: ordinal not in range(128)

  root@bb-lp-1806076:~# env LANG=ru_RU.UTF-8 unattended-upgrade --help | cat
  Usage: unattended-upgrade [options]

  Options:
    -h, --helpshow this help message and exit
    -d, --debug   print debug messages
    --apt-debug   make apt/libapt print verbose debug messages
    -v, --verbose print info messages
    --dry-run Simulation, download but do not install
    --download-only   Only download, do not even try to install.
    --minimal-upgrade-steps
  Upgrade in minimal steps (and allow interrupting with
  SIGTERM

  [Original Bug Text]

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1.18.04.6, the problem page at 
https://errors.ubuntu.com/problem/b3e3265e302351558260f54ae37c7b4c193dfc95 
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/.

  Also seen in:
   * https://errors.ubuntu.com/problem/936bb1c75c4efe018f968a5773b820bcf52c298a

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

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

[Touch-packages] [Bug 1808861] Re: chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated

[Brian Murray]

The log file /var/log/apport.log might be helpful in sorting out why an
incomplete core was written. Could you please add it as an attachment?

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

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

Title:
  chromium-browser crash Unreportable - Invalid core dump: BFD: warning:
  apport_core is truncated

Status in apport package in Ubuntu:
  Incomplete
Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Trying to report a crash in chromium-browser, get Unreportable reason
  Invalid core dump: BFD: warning apport_core is truncated (see
  screenshot, can't copy message from apport dialog - bug # 1273752).

  UnreportableReason:
   Invalid core dump: BFD: warning: /tmp/apport_core_6yb3cl_7 is truncated: 
expected core file size >= 1245646848, found: 760283136
   warning: core file may not match specified executable file.

  
  Expected: able to report ?

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.5
  ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportLog:
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, 
signal 5, core limit 0, dump mode 1
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: 
/usr/lib/chromium-browser/chromium-browser (command line 
"/usr/lib/chromium-browser/chromium-browser\ --enable-pinch")
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
   ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report 
/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 17 15:30:28 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (96 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago)

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

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

[Touch-packages] [Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided

[Gert van de Kraats]

Trace

** Attachment added: "trace at forced coredump"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1797882/+attachment/5223254/+files/wayland_stacktrace.txt

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

Title:
  At dual monitor intel_do_flush_locked failed: Resource deadlock
  avoided

Status in gnome-shell package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Using ubuntu wayland with dual monitors, configured above each other.
  Dock is configured at both displays, not hiding.
  Icons for "terminal" and "libreofffice Writer" are present at the dock.

  Start terminal on primary screen by mouseclick on dock.
  Start libreoffice Writer on primary screen by mouseclick on dock.
  Terminate libreoffice Witer by mouseclick on X.
  Repeat the starting and stopping of Writer.

  Login-screen will appear. Syslog shows:
  Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked 
failed: Resource deadlock avoided
  Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from 
display: Connection reset by peer
  Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main 
process exited, code=exited, status=1/FAILURE

  This problem doesnot occur in a dual monitor-session without wayland.
  It also doesnot occur, if only one monitor used with wayland
  It also doesnot occur, if the dock is only present at the primary screen.
  It also doesnot occur if second started application is present at the dock 
and doesnot add an icon to the dock (as libreoffice does).

  All other dual monitor/dock configurations seem to have this problem.

  No idea if this is helpful info, but the used graphics card does not support 
OpenGL version 2.1:
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 
2.1 or later.
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor, falling back to sw

  glxinfo:
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.1 Mesa 18.2.2
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic i686
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 15 13:25:10 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided

[Gert van de Kraats]

Without solving this problem, wayland cannot be used after logon, when
using dual monitor. The sesssion stops very easy and often. Work is
lost; you have to logon again. E.g. the simple switching between 2
overlapping windows causes the end of the session.

I changed src/mesa/drivers/dri/i915/intel_batchbuffer.c to force a coredump in 
this case. The stacktrace is added to this bug-report.
Linenumbers might deviate a little bit because of extra coding of tracing.
The deadlock always occurs at cogl_onscreen_swap_buffers calling cogl_flush(), 
at the first journal-batch-flush for the offscreen-framebuffer.

The deadlock disappeared as soon as cogl is compiled with disabled batching!
To minimize this disabling of batching, I made a very dirty but working patch, 
which is attached to this bug.
At program clutter_stage_cogl_redraw_view  routine paint_stage is called for 
the "Unclipped stage paint".
This call is manipulated to flush immedately the first journal-entry of the 
default onscreen framebuffer.
This is done by misusing and changing program cogl_framebuffer_set_viewport and 
by changing _cogl_journal_flush.
Apparenly this early flushing causes a lock to be set which avoids the deadlock.

I do not know how to see which locks are held and by which process, so I
cannot solve the root-cause of thhe problem, but I assume some extra
lock must be set in this case to avoid deadlock.

With this dirty patch combined with other suggested (simple) patches at 
#1790525, #1795774 and #1795760 wayland can be run without any problems on dual 
monitor and "old" intel graphic card.
It performs better than lightdm, specially if the monitors are positioned aside 
of each other.


** Attachment added: "dirty_patch.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1797882/+attachment/5223253/+files/dirty_patch.txt

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

Title:
  At dual monitor intel_do_flush_locked failed: Resource deadlock
  avoided

Status in gnome-shell package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Using ubuntu wayland with dual monitors, configured above each other.
  Dock is configured at both displays, not hiding.
  Icons for "terminal" and "libreofffice Writer" are present at the dock.

  Start terminal on primary screen by mouseclick on dock.
  Start libreoffice Writer on primary screen by mouseclick on dock.
  Terminate libreoffice Witer by mouseclick on X.
  Repeat the starting and stopping of Writer.

  Login-screen will appear. Syslog shows:
  Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked 
failed: Resource deadlock avoided
  Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from 
display: Connection reset by peer
  Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main 
process exited, code=exited, status=1/FAILURE

  This problem doesnot occur in a dual monitor-session without wayland.
  It also doesnot occur, if only one monitor used with wayland
  It also doesnot occur, if the dock is only present at the primary screen.
  It also doesnot occur if second started application is present at the dock 
and doesnot add an icon to the dock (as libreoffice does).

  All other dual monitor/dock configurations seem to have this problem.

  No idea if this is helpful info, but the used graphics card does not support 
OpenGL version 2.1:
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 
2.1 or later.
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor, falling back to sw

  glxinfo:
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.1 Mesa 18.2.2
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic i686
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 15 13:25:10 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by

[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

[Sebastien Bacher]

The issue looks like it could be what is fixed by
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/34ca1680
(the change is included in 1.10.8 which is currently not yet in bionic
but being SRUed)

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

Title:
  vlan created on bond fails auto activation on updating parent network
  bond

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Auto activation of Vlan created over network-bond fails if bond is 
deactivated and reactivated.
   
  Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar 
Deshpande(manda...@in.ibm.com) 
   
  ---uname output---
  Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Created a network bond with static IP address (and no IPv6 address); 
active backup mode; ARP polling; single slave.

  2. Created a VLAN using said network bond with static IPv4 address
  (and no IPv6 address).

  3. Can ping from the appliance to a target on both links (the parent
  bond and the VLAN).

  4. Switched to another slave for the created bond

  5. Can still ping from the appliance to a target via the parent bond;
  however, cannot ping to the target via the VLAN.

  =
  Detailed steps:

  1. Initial setup:
  
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --  

  2. Create Netwrok-bond with one slave:
  
  root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 
ipv4.method disabled ipv6.method ignore
  Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully 
added.

  root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1
  Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) 
successfully added.
  root@S36MANDAR:~# nmcli con up bond-slave-enc1d40
  Connection successfully activated (D-Bus active path: 
/org/freedesktop/NetworkManager/ActiveConnection/18)
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40 
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --  

  3. Create vlan over mybond1:
  ===
  root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname 
vlanbond.100 dev mybond1 id 100  ipv4.method disabled ipv6.method ignore
  Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully 
added.
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE
   
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40   
   
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80   
   
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00   
   
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1   
   
  vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e  vlan  
vlanbond.100 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --
   

  4. Reactivate bond : 
  =
  root@S36MANDAR:~# nmcli con up mybond1
  Connection successfully activated (master waiting for slaves) (D-Bus active 
path: /org/freedesktop/NetworkManager/ActiveConnection/30)

  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  enc1d40 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1 
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  --  
  encw18104ddeb38e-d5f7-3814-abb7-be50b8da874e  ethernet  --  
  vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e  vlan  --  

  As is seen, vlan(vlanbond.100) did not ge

[Touch-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

[Sebastien Bacher]

The issue looks like it could be what is fixed by
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/34ca1680
(the change is included in 1.10.8 which is currently not yet in bionic
but being SRUed)

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

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.
   
  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond 
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto

  From /var/log/syslog, we can see ip got assigned:

  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 
255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on 
test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 
10.2.3.1
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1

  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  28: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
  link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
  inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute 
test_bond
 valid_lft 353sec preferred_lft 353sec
  inet6 fe80::ff:feb3:b522/64 scope link 
 valid_lft forever preferred_lft forever

  
  
+++
  Bond interface, ipv4 automatic mode and ipv6 manual mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond 
  [connection]
  id=test_bond
  uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537943300

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  address1=fe81::32a5:bc5f:287f:8db8/64
  dns-search=
  method=manual

  No automatic ip assigned to ipv4 and no requests to dhcp server seen in 
/var/log/syslog
  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  29: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
  link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
  inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute 
 valid_lft forever preferred_lft forever

  
  ==> Correct LP-Package need to be assigned...!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+subscriptions

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

[Touch-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes

[Tom]

I still get this error in Cosmic on a Dell M6500.

The M6500 does not have a keyboard RFKILL shortcut - in only has a
physical switch. That switch correctly enables/disables WiFi.

Is this the same bug?

Dec 18 09:04:28 localhost kernel: [ 2706.037523] dell_wmi: Unknown key with 
type 0x0011 and code 0xffd0 pressed
Dec 18 09:04:28 localhost kernel: [ 2706.037526] dell_wmi: Unknown key with 
type 0x0011 and code 0xffd1 pressed
Dec 18 09:04:28 localhost kernel: [ 2706.037527] dell_wmi: Unknown key with 
type 0x0011 and code 0xffd0 pressed

Note that I never use the Fn-keys, so I have no idea which key(s) it
would be complaining about.

$ uname -a
Linux DellLaptop 4.18.0-12-generic #13-Ubuntu SMP Wed Nov 14 15:17:05 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

$ cat os-release 
NAME="Ubuntu"
VERSION="18.10 (Cosmic Cuttlefish)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.10"
VERSION_ID="18.10"
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
VERSION_CODENAME=cosmic
UBUNTU_CODENAME=cosmic

Here is the output from using the physical switch:

Dec 18 11:24:13 localhost kernel: [11090.779775] atkbd serio0: Unknown key 
pressed (translated set 2, code 0x88 on isa0060/serio0).
Dec 18 11:24:13 localhost kernel: [11090.779781] atkbd serio0: Use 'setkeycodes 
e008 ' to make it known.
Dec 18 11:24:13 localhost kernel: [11090.779888] iwlwifi :0c:00.0: RF_KILL 
bit toggled to disable radio.
Dec 18 11:24:13 localhost kernel: [11090.779899] iwlwifi :0c:00.0: 
reporting RF_KILL (radio disabled)
Dec 18 11:24:13 localhost kernel: [11090.780076] wlp12s0: deauthenticating from 
24:b6:57:f9:c6:9e by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 18 11:24:13 localhost kernel: [11090.780986] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.780991] wlp12s0: HW problem - can not 
stop rx aggregation for 24:b6:57:f9:c6:9e tid 0
Dec 18 11:24:13 localhost kernel: [11090.781003] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781011] wlp12s0: HW problem - can not 
stop rx aggregation for 24:b6:57:f9:c6:9e tid 1
Dec 18 11:24:13 localhost kernel: [11090.781019] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781023] wlp12s0: HW problem - can not 
stop rx aggregation for 24:b6:57:f9:c6:9e tid 2
Dec 18 11:24:13 localhost kernel: [11090.781028] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781031] wlp12s0: HW problem - can not 
stop rx aggregation for 24:b6:57:f9:c6:9e tid 3
Dec 18 11:24:13 localhost kernel: [11090.781197] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781202] wlp12s0: failed to remove key 
(0, 24:b6:57:f9:c6:9e) from hardware (-5)
Dec 18 11:24:13 localhost kernel: [11090.781359] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781366] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781378] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781387] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781419] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781433] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781874] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781882] wlp12s0: failed to remove key 
(1, ff:ff:ff:ff:ff:ff) from hardware (-5)
Dec 18 11:24:13 localhost kernel: [11090.782592] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.795404] iwlwifi :0c:00.0: RF_KILL 
bit toggled to disable radio.
Dec 18 11:24:13 localhost wpa_supplicant[1107]: rfkill: WLAN hard blocked
Dec 18 11:24:13 localhost NetworkManager[1109]:   [1545150253.0043] 
sup-iface[0x557818a4da10,wlp12s0]: connection disconnected (reason -3)
Dec 18 11:24:13 localhost wpa_supplicant[1107]: wlp12s0: 
CTRL-EVENT-DISCONNECTED bssid=24:b6:57:f9:c6:9e reason=3 locally_generated=1
Dec 18 11:24:13 localhost systemd[1]: Starting Load/Save RF Kill Switch 
Status...
Dec 18 11:24:13 localhost avahi-daemon[1078]: Interface wlp12s0.IPv6 no longer 
relevant for mDNS.
Dec 18 11:24:13 localhost NetworkManager[1109]:   [1545150253.0065] 
manager: rfkill: WiFi now disabled by radio killswitch
Dec 18 11:24:13 localhost avahi-daemon[1078]: Leaving mDNS multicast group on 
interface wlp12s0.IPv6 with address fe80::44c3:6970:aa31:f9a2.
Dec 18 11:24:13 localhost NetworkManager[1109]:   [1545150253.0069] 
device (wlp12s0): state change: activated -> unavailable (reason 'none', 
sys-iface-state: 'managed')
Dec 18 11:24:13 localho

[Touch-packages] [Bug 1370953] Re: layout switch is delayed

[Max]

I'm experiencing same bug on elementary OS 5.0. It really driving me nuts.
Added initial bounty on this.
https://www.bountysource.com/issues/63898369-slow-keyboard-layouts-switch

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

Title:
  layout switch is delayed

Status in console-setup package in Ubuntu:
  Confirmed
Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+subscriptions

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

[Touch-packages] [Bug 1688265] Re: Wifi disconnects when screen is locked

[Sebastien Bacher]

Thank you for your bug report. What desktop environment are you using?
Is it still an issue in newer Ubuntu series?

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  Wifi disconnects when screen is locked

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu: 17.04
  Wifi Chipset: Intel 7260 rev bb
  Driver: iwlwifi 4.10.0-19-generic

  If I lock my screen overnight, the following morning my Wifi will be
  disconnected and is slow to reconnect and often requires multiple
  connection attempts. Locking my screen for a short period of time
  (minutes or hours) doesn't trigger the behavior.

  Dmesg:

  
  ```
  [1256404.227085] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
  [1256404.229298] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
  [1256404.230281] wlp5s0: authenticated
  [1256404.843347] wlp5s0: Connection to AP 00:25:9c:xx:xx:xx lost
  [1256409.234035] wlp5s0: aborting authentication with 00:25:9c:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
  [1256413.045691] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
  [1256413.047962] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
  [1256413.048999] wlp5s0: authenticated
  [1256413.661996] wlp5s0: Connection to AP 00:25:9c:xx:xx:xx lost
  [1256418.051499] wlp5s0: aborting authentication with 00:25:9c:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
  [1256422.361848] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
  [1256422.364062] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
  [1256422.365122] wlp5s0: authenticated
  [1256422.978086] wlp5s0: Connection to AP 00:25:9c:xx:xx:xx lost
  [1256426.516541] wlp5s0: aborting authentication with 00:25:9c:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
  [1256426.518958] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
  [1256426.524074] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
  [1256426.544019] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
  [1256426.578930] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
  [1256426.581309] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
  [1256426.582424] wlp5s0: authenticated
  [1256426.582716] wlp5s0: associate with 00:25:9c:xx:xx:xx (try 1/3)
  [1256426.583584] wlp5s0: RX AssocResp from 00:25:9c:xx:xx:xx (capab=0x11 
status=0 aid=1)
  [1256426.584763] wlp5s0: associated
  [1256426.584867] IPv6: ADDRCONF(NETDEV_CHANGE): wlp5s0: link becomes ready
  [1256426.630815] bridge-wlp5s0: device is wireless, enabling SMAC
  [1256426.630817] bridge-wlp5s0: up
  [1256426.630823] bridge-wlp5s0: attached
  ```

  There are hundreds of lines like this. It looks like it gets into a
  loop where it disconnects every 5 seconds. Once I log in and reconnect
  using the applet in the menu bar, the connection is pretty reliable
  for hours -- I generally work a full day without wifi dropping.

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

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

[Touch-packages] [Bug 1317552] Re: usb modem doesn't recognized by system until wired network connected

[Sebastien Bacher]

Thank you for your bug report. There has been no activity nor new report
in a few years, could you try if that's still an issue using newer
ubuntu versions?

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  usb modem doesn't recognized by system until wired network connected

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I have an usb 3g modem huawei, configured as standalone network
  device. When I connect it, dmesg shows some error messages, but
  nothing happens. After connect and futher disconnect wired network
  (eth0), it succesful recognized by the system as eth1 device and all
  works fine. Problem is that sometimes I have no wired network to start
  usb-3g connection this way.

  Part of dmesg with connect/disconnect manipulations

  [   27.606224] init: libvirt-bin main process (979) terminated with status 127
  [   27.606239] init: libvirt-bin main process ended, respawning
  [   27.915799] r8169 :01:00.0 eth0: link down
  [   27.915869] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   27.916229] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   27.938186] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [   27.941688] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [   28.566084] usb 1-1.1: New USB device found, idVendor=0cf3, idProduct=0036
  [   28.566089] usb 1-1.1: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
  [   28.775155] init: plymouth-upstart-bridge main process ended, respawning
  [   34.989561] FAT-fs (sdb1): Volume was not properly unmounted. Some data 
may be corrupt. Please run fsck.
  [   55.380263] usb 3-3: new high-speed USB device number 3 using xhci_hcd
  [   55.397190] usb 3-3: New USB device found, idVendor=12d1, idProduct=1f01
  [   55.397202] usb 3-3: New USB device strings: Mfr=2, Product=1, 
SerialNumber=0
  [   55.397207] usb 3-3: Product: HUAWEI HiLink
  [   55.397212] usb 3-3: Manufacturer: HUAWEI
  [   55.465739] usb-storage 3-3:1.0: USB Mass Storage device detected
  [   55.465795] scsi7 : usb-storage 3-3:1.0
  [   55.465865] usbcore: registered new interface driver usb-storage
  [   56.464794] scsi 7:0:0:0: CD-ROMHUAWEI   Mass Storage 2.31 
PQ: 0 ANSI: 2
  [   56.472835] sr1: scsi-1 drive
  [   56.472989] sr 7:0:0:0: Attached scsi CD-ROM sr1
  [   56.473080] sr 7:0:0:0: Attached scsi generic sg3 type 5
  [   56.558838] audit_printk_skb: 156 callbacks suppressed
  [   56.558842] type=1400 audit(1399561168.962:64): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=2017 comm="apparmor_parser"
  [   56.558850] type=1400 audit(1399561168.962:65): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=2017 comm="apparmor_parser"
  [   56.559369] type=1400 audit(1399561168.962:66): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=2017 comm="apparmor_parser"
  [   56.638660] Buffer I/O error on device sr1, logical block 0
  [   56.638668] Buffer I/O error on device sr1, logical block 0
  [   56.638685] Buffer I/O error on device sr1, logical block 0
  [   56.638693] Buffer I/O error on device sr1, logical block 0
  [   56.638701] Buffer I/O error on device sr1, logical block 1
  [   56.638708] Buffer I/O error on device sr1, logical block 1
  [   56.638716] Buffer I/O error on device sr1, logical block 512
  [   56.640490] systemd-udevd[2001]: Failed to apply ACL on /dev/sr1: No such 
file or directory
  [   56.640501] systemd-udevd[2001]: Failed to apply ACL on /dev/sr1: No such 
file or directory
  [   56.651401] systemd-udevd[1987]: Failed to apply ACL on /dev/sr1: No such 
file or directory
  [   56.651427] systemd-udevd[1987]: Failed to apply ACL on /dev/sr1: No such 
file or directory
  [  107.810564] usb 3-3: USB disconnect, device number 3
  [  116.952712] usb 3-3: new high-speed USB device number 4 using xhci_hcd
  [  116.969698] usb 3-3: New USB device found, idVendor=12d1, idProduct=1f01
  [  116.969709] usb 3-3: New USB device strings: Mfr=2, Product=1, 
SerialNumber=0
  [  116.969715] usb 3-3: Product: HUAWEI HiLink
  [  116.969720] usb 3-3: Manufacturer: HUAWEI
  [  116.971391] usb-storage 3-3:1.0: USB Mass Storage device detected
  [  116.971653] scsi8 : usb-storage 3-3:1.0
  [  117.969336] scsi 8:0:0:0: CD-ROMHUAWEI   Mass Storage 2.31 
PQ: 0 ANSI: 2
  [  117.971006] sr1: scsi-1 drive
  [  117.971389] sr 8:0:0:0: Attached scsi CD-ROM sr1
  [  117.974632] sr 8:0:0:0: Attached scsi generic sg3 type 5
  [  118.063825] quiet_error: 1 callbacks suppressed
  [  118.063836] Buffer I/O error on device sr1, logical b

[Touch-packages] [Bug 942856] Re: NetworkManager does not support AES-encrypted private keys for WPA 802.1x authentication

[Sebastien Bacher]

Those keys are handled since 1.10.10 and Ubuntu 18.10
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/9b46af1a

That update is being SRUed to bionic

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  NetworkManager does not support AES-encrypted private keys for WPA
  802.1x authentication

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  NetworkManager does not appear to support private keys encrypted with
  AES.  At the very least, it will not validate such a key in nm-util
  when setting up a WPA 802.1x TLS wifi connection.

  To test:

  1. Start with a working (cleartext or DES-3) private key/cert for a network.  
Set up a connection and verify that everything works.
  2. Re-encrypt the key with AES-256 with this command: "openssl rsa -in 
working-key.pem -out aes-key.pem -aes256" (the output should have a line 
starting with "DEK-Info: AES-256-CBC,")
  3. Delete the settings for the test network and attempt to reconnect using 
the new key.  Even with the correct passphrase, the "Connect" button will 
remain disabled; debugging will determine that nm-util is failing to validate 
the private key.

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

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

[Touch-packages] [Bug 1795921] Re: Out-of-Bounds write in systemd-networkd dhcpv6 option handling

[Sebastien Bacher]

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

Title:
  Out-of-Bounds write in systemd-networkd dhcpv6 option handling

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  systemd-networkd contains a DHCPv6 client which is written from
  scratch and can be spawned automatically on managed interfaces when
  IPv6 router advertisement are received:

  "Note that DHCPv6 will by default be triggered by Router Advertisement, if 
that is enabled, regardless of this parameter. By enabling DHCPv6 support 
explicitly, the DHCPv6 client will be started regardless of the presence of 
routers on the link, or what flags the routers pass" 
  (https://www.freedesktop.org/software/systemd/man/systemd.network.html)

  
  The function dhcp6_option_append_ia function is used to encode Identity 
Associations received by the server into the options buffer of an outgoing 
DHCPv6 packet:

  // 
https://github.com/systemd/systemd/blob/master/src/libsystemd-network/dhcp6-option.c#L82
  int dhcp6_option_append_ia(uint8_t **buf, size_t *buflen, DHCP6IA *ia) {
  uint16_t len;
  uint8_t *ia_hdr;
  size_t iaid_offset, ia_buflen, ia_addrlen = 0;
  DHCP6Address *addr;
  int r;

  assert_return(buf && *buf && buflen && ia, -EINVAL);

  switch (ia->type) {
  case SD_DHCP6_OPTION_IA_NA:
  len = DHCP6_OPTION_IA_NA_LEN;
  iaid_offset = offsetof(DHCP6IA, ia_na);
  break;

  case SD_DHCP6_OPTION_IA_TA:
  len = DHCP6_OPTION_IA_TA_LEN;
  iaid_offset = offsetof(DHCP6IA, ia_ta);
  break;

  default:
  return -EINVAL;
  }

  A:  if (*buflen < len)
  return -ENOBUFS;

  ia_hdr = *buf;
  ia_buflen = *buflen;

  *buf += sizeof(DHCP6Option);
  B:  *buflen -= sizeof(DHCP6Option);

  C:   memcpy(*buf, (char*) ia + iaid_offset, len);

  *buf += len;
  D:  *buflen -= len;

  E:LIST_FOREACH(addresses, addr, ia->addresses) {
  r = option_append_hdr(buf, buflen, SD_DHCP6_OPTION_IAADDR,
sizeof(addr->iaaddr));
  if (r < 0)
  return r;

  memcpy(*buf, &addr->iaaddr, sizeof(addr->iaaddr));

  *buf += sizeof(addr->iaaddr);
  *buflen -= sizeof(addr->iaaddr);

  ia_addrlen += sizeof(DHCP6Option) + sizeof(addr->iaaddr);
  }

  r = option_append_hdr(&ia_hdr, &ia_buflen, ia->type, len + 
ia_addrlen);
  if (r < 0)
  return r;

  return 0;
  }

  
  The function receives a pointer to the option buffer buf, it's remaining size 
buflen and the IA to be added to the buffer. While the check at (A) tries to 
ensure that the buffer has enough space left to store the IA option, it does 
not take the additional 4 bytes from the DHCP6Option header into account (B). 
Due to this the memcpy at (C) can go out-of-bound and *buflen can underflow in 
(D) giving an attacker a very powerful and largely controlled OOB heap write 
starting at (E).

  The overflow can be triggered relatively easy by advertising a DHCPv6
  server with a server-id >= 493 characters long. This will trigger the
  following code once the client tries to create a REQUEST message:

  
//https://github.com/systemd/systemd/blob/7bcf8123c0305131ace02480763377af974924ef/src/libsystemd-network/sd-dhcp6-client.c#L493
  case DHCP6_STATE_REQUEST:
  case DHCP6_STATE_RENEW:

  if (client->state == DHCP6_STATE_REQUEST)
  message->type = DHCP6_REQUEST;
  else
  message->type = DHCP6_RENEW;

  A:  r = dhcp6_option_append(&opt, &optlen, 
SD_DHCP6_OPTION_SERVERID,
  client->lease->serverid_len,
  client->lease->serverid);
  if (r < 0)
  return r;

  if (FLAGS_SET(client->request, DHCP6_REQUEST_IA_NA)) {
  B:  r = dhcp6_option_append_ia(&opt, &optlen,
 &client->lease->ia);
  if (r < 0)
  return r;
  }

  optlen starts with the value 512 and gets decreased to 15 (512 - 493 -
  4) after the call in A. As 15 > DHCP6_OPTION_IA_NA_LEN but 15 <
  (DHCP6_OPTION_IA_NA_LEN + 4) this triggers the memory corruption:

  # journalctl -u systemd-networkd
  Oct 03 14:27:50 ubuntu18 systemd-networkd[45095]: malloc(): memory corruption
  Oct 03 14:27:50 ubuntu18 systemd[1]: 

[Touch-packages] [Bug 1809011] [NEW] package cups 2.2.7-1ubuntu2.1 failed to install/upgrade: read error in '/var/lib/dpkg/info/cups.triggers': Input/output error

[Alberto José Marrufo García]

Public bug reported:

Mientrasactualizaba el sistema recien instalado

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Dec 18 17:50:57 2018
DuplicateSignature:
 package:cups:2.2.7-1ubuntu2.1
 Preparing to unpack .../074-cups_2.2.7-1ubuntu2.2_amd64.deb ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-0IVoPc/074-cups_2.2.7-1ubuntu2.2_amd64.deb (--unpack):
  read error in '/var/lib/dpkg/info/cups.triggers': Input/output error
ErrorMessage: read error in '/var/lib/dpkg/info/cups.triggers': Input/output 
error
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Packard Bell EasyNote TS44HR
Papersize: a4
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=f9b48e7f-1e8e-46a2-b720-967fe70d5dde ro quiet splash vt.handoff=1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=f9b48e7f-1e8e-46a2-b720-967fe70d5dde ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: cups
Title: package cups 2.2.7-1ubuntu2.1 failed to install/upgrade: read error in 
'/var/lib/dpkg/info/cups.triggers': Input/output error
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/24/2011
dmi.bios.vendor: Packard Bell
dmi.bios.version: V1.11
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SJV50_HR
dmi.board.vendor: Packard Bell
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Packard Bell
dmi.chassis.version: V1.11
dmi.modalias: 
dmi:bvnPackardBell:bvrV1.11:bd05/24/2011:svnPackardBell:pnEasyNoteTS44HR:pvrV1.11:rvnPackardBell:rnSJV50_HR:rvrBaseBoardVersion:cvnPackardBell:ct10:cvrV1.11:
dmi.product.name: EasyNote TS44HR
dmi.product.version: V1.11
dmi.sys.vendor: Packard Bell

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


** Tags: amd64 apport-package bionic need-duplicate-check

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

Title:
  package cups 2.2.7-1ubuntu2.1 failed to install/upgrade: read error in
  '/var/lib/dpkg/info/cups.triggers': Input/output error

Status in cups package in Ubuntu:
  New

Bug description:
  Mientrasactualizaba el sistema recien instalado

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Dec 18 17:50:57 2018
  DuplicateSignature:
   package:cups:2.2.7-1ubuntu2.1
   Preparing to unpack .../074-cups_2.2.7-1ubuntu2.2_amd64.deb ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-0IVoPc/074-cups_2.2.7-1ubuntu2.2_amd64.deb (--unpack):
read error in '/var/lib/dpkg/info/cups.triggers': Input/output error
  ErrorMessage: read error in '/var/lib/dpkg/info/cups.triggers': Input/output 
error
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Packard Bell EasyNote TS44HR
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=f9b48e7f-1e8e-46a2-b720-967fe70d5dde ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=f9b48e7f-1e8e-46a2-b720-967fe70d5dde ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: cups
  Title: package cups 2.2.7-1ubuntu2.1 failed to install/upgrade: read error in 
'/var/lib/dpkg/info/cups.triggers': Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2011
  dmi.bios.vendor: Packard Bell
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SJV50_HR
  dmi.board.vendor: Packard Bell
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Packard Bell
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnPackardBell:bvrV1.11:bd05/24/2011:svnPackardBell:pnEasyNoteTS44HR:pvrV1.11:rvnPackardBell:rnSJV50_HR:rvrBaseBoardVersion:cvnPackardBell:ct10:cvrV1.11:
  dmi.product.name: EasyNote TS44HR
  dmi.product.version: V1.11
  dmi.sys.vendor: Packard Bell

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

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

[Touch-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work

[Brian Murray]

Hello Hui, or anyone else affected,

Accepted alsa-lib into cosmic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/alsa-
lib/1.1.6-1ubuntu1.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: alsa-lib (Ubuntu Cosmic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

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

Title:
  The line-out on the Dell Dock station can't work

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in alsa-lib source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback
  devices, one is headphone, the other is line-out, but there is no UCM for
  these docks yet, so the pluseaudio only can handle the 1st playback device,
  need us to add the UCM for them, before adding UCM, we need to set the
  longname of the sound card in the linux kernel.

  [Fix]
  For Linux kernel: Cherry-picked 3 upstream patches, these patches add the 
longname of the sound card for the dock station.

  For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will
  add ucm configuration files for Dell WD15&19, and change the SPDIF conf
  in the USB-AUDIO.conf.

  [Test Case]
  Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from
  UI, and play sound via these devices

  [Regression Potential]
  Very low, these patches come from upstream, and the change is only specific
  to WD15 and WD19 dock station.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806532/+subscriptions

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

[Touch-packages] [Bug 1807373] Please test proposed package

[Łukasz Zemczak]

Hello errors.ubuntu.com, or anyone else affected,

Accepted software-properties into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/software-properties/0.96.24.32.7 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Changed in: software-properties (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:on_driver_selection_changed

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Xenial:
  Fix Committed
Status in software-properties source package in Bionic:
  Fix Committed
Status in software-properties source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  software-properties-gtk is crashing regularly for users of Ubuntu stable 
releases.

  [Test Case]
  We aren't sure what exactly is causing the crash but we don't need to be 
given that there is a bucket in the Error Tracker with a large number of 
crashes. The fix for this bug can be verified by looking at the bucket in the 
description and confirming that the crash does not occur with the new version 
of the package.

  [Regression Potential]
  We are just adding in a except check for an AttributeError so there is little 
chance of a regression, just make sure the change is typo'ed.

  [Original Description]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
1.92.36bodhi1, the problem page at 
https://errors.ubuntu.com/problem/b13c9466e8741d31ba6c9934365589f383a60650 
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/software-properties/+bug/1807373/+subscriptions

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

[Touch-packages] [Bug 1807373] Please test proposed package

[Łukasz Zemczak]

Hello errors.ubuntu.com, or anyone else affected,

Accepted software-properties into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/software-properties/0.96.20.8 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:on_driver_selection_changed

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Xenial:
  Fix Committed
Status in software-properties source package in Bionic:
  Fix Committed
Status in software-properties source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  software-properties-gtk is crashing regularly for users of Ubuntu stable 
releases.

  [Test Case]
  We aren't sure what exactly is causing the crash but we don't need to be 
given that there is a bucket in the Error Tracker with a large number of 
crashes. The fix for this bug can be verified by looking at the bucket in the 
description and confirming that the crash does not occur with the new version 
of the package.

  [Regression Potential]
  We are just adding in a except check for an AttributeError so there is little 
chance of a regression, just make sure the change is typo'ed.

  [Original Description]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
1.92.36bodhi1, the problem page at 
https://errors.ubuntu.com/problem/b13c9466e8741d31ba6c9934365589f383a60650 
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/software-properties/+bug/1807373/+subscriptions

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

[Touch-packages] [Bug 1807373] Re: /usr/bin/software-properties-gtk:AttributeError:on_driver_selection_changed

[Łukasz Zemczak]

Hello errors.ubuntu.com, or anyone else affected,

Accepted software-properties into cosmic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/software-properties/0.96.27.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: software-properties (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

** Changed in: software-properties (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:on_driver_selection_changed

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Xenial:
  Fix Committed
Status in software-properties source package in Bionic:
  Fix Committed
Status in software-properties source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  software-properties-gtk is crashing regularly for users of Ubuntu stable 
releases.

  [Test Case]
  We aren't sure what exactly is causing the crash but we don't need to be 
given that there is a bucket in the Error Tracker with a large number of 
crashes. The fix for this bug can be verified by looking at the bucket in the 
description and confirming that the crash does not occur with the new version 
of the package.

  [Regression Potential]
  We are just adding in a except check for an AttributeError so there is little 
chance of a regression, just make sure the change is typo'ed.

  [Original Description]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
1.92.36bodhi1, the problem page at 
https://errors.ubuntu.com/problem/b13c9466e8741d31ba6c9934365589f383a60650 
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/software-properties/+bug/1807373/+subscriptions

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

[Touch-packages] [Bug 1809014] [NEW] mpeg-2 detected as tga (Targa image)

[Finn Kempers]

Public bug reported:

It appears that currently using either the file command or through the
File::LibMagic interface that 1:5.34-2 on Cosmic (18.10) makes a MPEG-2
file be detected as Targa at a higher priority, thus taking precedence
over being what it actually is. See the below lines as examples using
clips from http://hubblesource.stsci.edu/sources/video/clips/ as
examples:

$ file -k /home/piratefinn/Downloads/hst_2.mpg 
/home/piratefinn/Downloads/hst_2.mpg: Targa image data - Map 63635 x 65536 x 1 
+268 +60928 - 11-bit alpha - top - right - four way interleave MPEG sequence, 
v2, program multiplex (Lepton 3.x), scale 0-0, spot sensor temperature 
0.00, unit celsius, color scheme 0, calibration: offset 0.00, slope 
0.00\012- data

Note that this appears to only affect MPEG-2 (and possibly higher) as
MPEG-1 is detected corretly.

$ file -k /home/piratefinn/Downloads/hst_1.mpg 
/home/piratefinn/Downloads/hst_1.mpg: MPEG sequence, v1, progressive Y'CbCr 
4:2:0 video, 320x240, 4:3, 29.97 fps (Lepton 2.x), scale 1-2, spot sensor 
temperature 0.00, unit celsius, color scheme 0, show spot sensor, show 
scale bar, maximum point enabled, calibration: offset 586.228088, slope 
-411899156202779801569722368.00\012- data
file -k /home/piratefinn/Downloads/hst_1.mpg

This appears to not be an issue in 1:5.25 used in 16.04, however looking
through the github it appears since then in possible 5.26 (or above)
changes as seen in
https://github.com/file/file/commit/aee048a020badb5f36008f6d11e7d5b32834bcb2
affected this.

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

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

Title:
  mpeg-2 detected as tga (Targa image)

Status in file package in Ubuntu:
  New

Bug description:
  It appears that currently using either the file command or through the
  File::LibMagic interface that 1:5.34-2 on Cosmic (18.10) makes a
  MPEG-2 file be detected as Targa at a higher priority, thus taking
  precedence over being what it actually is. See the below lines as
  examples using clips from
  http://hubblesource.stsci.edu/sources/video/clips/ as examples:

  $ file -k /home/piratefinn/Downloads/hst_2.mpg 
  /home/piratefinn/Downloads/hst_2.mpg: Targa image data - Map 63635 x 65536 x 
1 +268 +60928 - 11-bit alpha - top - right - four way interleave MPEG sequence, 
v2, program multiplex (Lepton 3.x), scale 0-0, spot sensor temperature 
0.00, unit celsius, color scheme 0, calibration: offset 0.00, slope 
0.00\012- data

  Note that this appears to only affect MPEG-2 (and possibly higher) as
  MPEG-1 is detected corretly.

  $ file -k /home/piratefinn/Downloads/hst_1.mpg 
  /home/piratefinn/Downloads/hst_1.mpg: MPEG sequence, v1, progressive Y'CbCr 
4:2:0 video, 320x240, 4:3, 29.97 fps (Lepton 2.x), scale 1-2, spot sensor 
temperature 0.00, unit celsius, color scheme 0, show spot sensor, show 
scale bar, maximum point enabled, calibration: offset 586.228088, slope 
-411899156202779801569722368.00\012- data
  file -k /home/piratefinn/Downloads/hst_1.mpg

  This appears to not be an issue in 1:5.25 used in 16.04, however
  looking through the github it appears since then in possible 5.26 (or
  above) changes as seen in
  https://github.com/file/file/commit/aee048a020badb5f36008f6d11e7d5b32834bcb2
  affected this.

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

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

[Touch-packages] [Bug 1808075] Re: Backport Unicode/Emoji 11 updates

[Brian Murray]

Hello Jeremy, or anyone else affected,

Accepted pango1.0 into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pango1.0/1.42.4-3ubuntu1 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: pango1.0 (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

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

Title:
  Backport Unicode/Emoji 11 updates

Status in pango1.0 package in Ubuntu:
  Fix Released
Status in pango1.0 source package in Cosmic:
  Fix Committed

Bug description:
  Impact
  ==
  Once a year, there is a new Unicode and Emoji release. 2018's release is 
Unicode 11.

  Ubuntu 18.04 LTS and 18.10 already include Google's color emoji font
  for Unicode 11 (LP: #1788256) but neither Ubuntu 18.10 nor 18.04 LTS
  are able to display the new combinations introduced in Unicode 11 such
  as red-haired people.

  Test Case
  =
  Copy and paste the red-hair man 👨‍🦰 into gedit. It should show as a single 
character.

  Regression Potential
  
  Although the code was written several weeks ago, it was only released in 
pango 1.43 (a development release) today so it's not seen many users yet.

  On the other hand, pango does have a test suite run during the build
  and as autopkgtest and those tests still pass. I haven't seen any
  issues yet and we'll work to fix any issues that do develop.

  A significant portion of the change set comes from the Unicode data
  sets and from the Chromium Unicode/Emoji parser. Both of those parts
  have received wider testing and use over several months.

  Other Info
  ==
  This issue is easy to fix with Ubuntu 18.10 but it may not be practical to 
try to update Ubuntu 18.04 LTS for this feature.

  GTK's "Insert Emoji" feature will need to be updated to offer these
  new emoji.

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

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

Re: [Touch-packages] [Bug 1804910] Re: pip3 cannot install gmpy

[Kevin O'Gorman]

I wasn't aware of gmpy2.  Installing it has solved this issue for me.

On Sun, Nov 25, 2018 at 9:20 AM Hans Joachim Desserud <
1804...@bugs.launchpad.net> wrote:

> Thanks for reporting.
>
> I'm a bit confused to the issue. Though I am not familiar with gmpy, it
> looks like there are two versions of it available in Ubuntu, gmpy and
> gmpy2. While the former doesn't have a python3 package, the latter one
> does and this seems to be the maintained version too. That would be
> installable through `sudo apt install python3-gmpy2`
> (https://packages.ubuntu.com/bionic/python3-gmpy2).
>
> If for some reason the Ubuntu package doesn't fit or you really need to
> use the older gmpy version in combination with Python3 i suppose that might
> be why the script attempt to install via pip3 instead of apt. Based on the
> error message:
>   In file included from src/gmpy.c:251:0:
>   src/gmpy.h:30:10: fatal error: gmp.h: No such file or directory
>#include "gmp.h"
> ^~~
>   compilation terminated.
>   error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
>  it looks like it was fetched, but failed to compile while installing.
> Some python packages contain C/C++ code to speed up certain parts and looks
> like this is one of them. It might be missing some build dependencies,
> which perhaps `sudo apt build-dep python-gmpy` (for gmpy1) or `sudo apt
> build-dep python-gmpy2` (for gmpy2, though in that case it is probably
> easier to use the existing python3-gmpy2 package as described above)
>
>
> ** Changed in: python3-defaults (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1804910
>
> Title:
>   pip3 cannot install gmpy
>
> Status in python3-defaults package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I'm using python3 and want gmpy.  Attempts to install it fail.
>
>   I routinely capture the output of maintenance tasks, and am attaching
>   the results.  This output begins with the text of the shell script I
>   wrote to do this, which includes calls to the bash functions I wrote
>   to do this self-referential magic.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: python3 3.6.7-1~18.04
>   ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
>   Uname: Linux 4.15.0-39-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.5
>   Architecture: amd64
>   Date: Fri Nov 23 17:44:44 2018
>   InstallationDate: Installed on 2018-10-18 (36 days ago)
>   InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
>   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/python3-defaults/+bug/1804910/+subscriptions
>


-- 
Kevin O'Gorman
#define QUESTION ((bb) || (!bb))   /* Shakespeare */

Please consider the environment before printing this email.


** Attachment added: "unnamed"
   https://bugs.launchpad.net/bugs/1804910/+attachment/5223298/+files/unnamed

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

Title:
  pip3 cannot install gmpy

Status in python3-defaults package in Ubuntu:
  Incomplete

Bug description:
  I'm using python3 and want gmpy.  Attempts to install it fail.

  I routinely capture the output of maintenance tasks, and am attaching
  the results.  This output begins with the text of the shell script I
  wrote to do this, which includes calls to the bash functions I wrote
  to do this self-referential magic.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: python3 3.6.7-1~18.04
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 17:44:44 2018
  InstallationDate: Installed on 2018-10-18 (36 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  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/python3-defaults/+bug/1804910/+subscriptions

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

[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

[Dan Streetman]

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

** Also affects: systemd (Ubuntu Disco)
   Importance: Undecided
   Status: Confirmed

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

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

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

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  New
Status in systemd source package in Disco:
  Confirmed

Bug description:
  [Impact]

  Mounting manually a network share (NFS) and masking it breaks the state of 
other units (and their dependencies).
  Casper is masking a mounted NFS share, blocking the normal boot process as 
described in the original description, but the issue comes from systemd.

  [Test Case]

  - NFS mount point at /media
  root@iscsi-bionic:/home/ubuntu# mount | grep media
  10.230.56.72:/tmp/mnt on /media type nfs4 
(rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.127,local_lock=none,addr=10.230.56.72)

  - Test mount point (/test) defined in /etc/fstab:
  root@iscsi-bionic:/home/ubuntu# cat /etc/fstab |grep test
  tmpfs /test tmpfs nosuid,nodev 0 0

  1. If media.mount is not masked, everything works fine:

  root@iscsi-bionic:/home/ubuntu# mount | grep test
  root@iscsi-bionic:/home/ubuntu# systemctl status media.mount | grep Active
 Active: active (mounted) since Thu 2018-11-15 16:03:59 UTC; 3 weeks 6 days 
ago
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: inactive (dead) since Thu 2018-12-13 10:33:52 UTC; 4min 11s ago
  root@iscsi-bionic:/home/ubuntu# systemctl start test.mount
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: active (mounted) since Thu 2018-12-13 10:38:13 UTC; 3s ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: inactive (dead) since Thu 2018-12-13 10:38:32 UTC; 3s ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test

  2. If media.mount is masked, other mounts are failing:

  root@iscsi-bionic:/home/ubuntu# systemctl mask media.mount
  Created symlink /etc/systemd/system/media.mount → /dev/null.
  root@iscsi-bionic:/home/ubuntu# systemctl start test.mount
  Job for test.mount failed.
  See "systemctl status test.mount" and "journalctl -xe" for details.
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 10s 
ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 25s 
ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl start test.mount
  Job for test.mount failed.
  See "systemctl status test.mount" and "journalctl -xe" for details.
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)

  [Regression potential]

  Minimal. Originally, one failing mount point blocked the processing of
  the rest due to how the return codes were handled for every line in
  /proc/self/mountinfo. This patch removes this "dependency" and keeps
  the failure local to the affected mount point, allowing the rest to be
  processed normally.

  [Other Info]

  Upstream bug: https://github.com/systemd/systemd/issues/10874
  Fixed upstream with commit: 
https://github.com/systemd/systemd/commit/c165888426ef99440418592a8cdbaff4b7c319b3

  [Original Description]

  
  netbooting the bionic live CD[1] over NFS goes straight to maintenance mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" labe

[Touch-packages] [Bug 1807721] Re: Fix variant selection in emoji chooser

[Brian Murray]

Why is the cosmic task open here? I don't see an upload in the cosmic
queue and the description leads me to believe this may already be fixed
there.

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

Title:
  Fix variant selection in emoji chooser

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Bionic:
  In Progress
Status in gtk+3.0 source package in Cosmic:
  In Progress

Bug description:
  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
  Right-click (or long-click) on the emoji and select one of the skin tones 
instead of the default yellow.
  The emoji with the skin tone you selected should be added to the text area.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398

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

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

[Touch-packages] [Bug 1767314] Re: Ubuntu Bionic vi/vim not working correctly

[flashydave]

The "set nocompatible" fix doesn't work on 18.04.1 LTS server.  The
trigger condition appears to be a random operation and not repeatable.
Symptoms include loss of tab completion and syntax highlighting.   It is
persistent through a re-edit of the same file.  The fault can be cleared
by removing .viminfo until the next random occurence.

Given the use of vi on a server instance with no GUU is very high I
would request the importance of this bug is set to high as it
significantly damages productivity when used in a professional context.

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

Title:
  Ubuntu Bionic vi/vim not working correctly

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  The vim default configuration in Bionic does not match Ubuntu 17.10
  nor Centos 7 and is hard to use. It auto-inserts tabs or spaces, and
  the '/' search mode command works differently (pressing enter is
  required before you can use cursors left/right).

  For some discussion, please see
  https://askubuntu.com/questions/1026820/vi-vim-usage-in-ubuntu-bionic-
  not-normal/1028684#1028684

  Setting :set nocompatbile in ~/.vimrc fixes it, but this should not be
  required.

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

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

[Touch-packages] [Bug 1767314] Re: Ubuntu Bionic vi/vim not working correctly

[flashydave]

The mis-interpretation of PC cursor keys when accessed vi ssh (as
described in the discussion link above) is very remeniscent of trying to
use vim.tiny not vim.basic (which server install defaults to).  Maybe
this along with my above post will help characterise the bug.

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

Title:
  Ubuntu Bionic vi/vim not working correctly

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  The vim default configuration in Bionic does not match Ubuntu 17.10
  nor Centos 7 and is hard to use. It auto-inserts tabs or spaces, and
  the '/' search mode command works differently (pressing enter is
  required before you can use cursors left/right).

  For some discussion, please see
  https://askubuntu.com/questions/1026820/vi-vim-usage-in-ubuntu-bionic-
  not-normal/1028684#1028684

  Setting :set nocompatbile in ~/.vimrc fixes it, but this should not be
  required.

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

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

[Touch-packages] [Bug 1809027] [NEW] Make retired Ubuntu keyrings available from the archive

[Dan Watkins]

Public bug reported:

Currently, if an Ubuntu developer (or their code) is attempting to
interact with the precise archive (which is still supported in some form
via ESM) from a machine running bionic or later, they will run in to
issues verifying signatures, because the keys used to sign the precise
archive are no longer included in the default keyring as of bionic.

(Some form of this problem will present every time an archive key
rotation happens; eventually the old key will no longer be trusted, and
similar failures to the ones today will occur.)

Whilst the old keys should never be used by the system's apt (or other
installed software), it would be good if there were some way to install
those keys from the archives for projects which knowingly want to use
the older signatures.  (The old keys should be in a path that isn't
currently used by anything, so that they have to be explicitly used.)

(This bug came out of a discussion on
https://code.launchpad.net/~smoser/vmbuilder/mfdiff-apt-key-
transition/+merge/313797.)

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

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

Title:
  Make retired Ubuntu keyrings available from the archive

Status in ubuntu-keyring package in Ubuntu:
  New

Bug description:
  Currently, if an Ubuntu developer (or their code) is attempting to
  interact with the precise archive (which is still supported in some
  form via ESM) from a machine running bionic or later, they will run in
  to issues verifying signatures, because the keys used to sign the
  precise archive are no longer included in the default keyring as of
  bionic.

  (Some form of this problem will present every time an archive key
  rotation happens; eventually the old key will no longer be trusted,
  and similar failures to the ones today will occur.)

  Whilst the old keys should never be used by the system's apt (or other
  installed software), it would be good if there were some way to
  install those keys from the archives for projects which knowingly want
  to use the older signatures.  (The old keys should be in a path that
  isn't currently used by anything, so that they have to be explicitly
  used.)

  (This bug came out of a discussion on
  https://code.launchpad.net/~smoser/vmbuilder/mfdiff-apt-key-
  transition/+merge/313797.)

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

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

[Touch-packages] [Bug 1809025] [NEW] Files Failed to Be Moved to The Desktop

[Vanilla Summers]

Public bug reported:

I was trying to move a downloaded file from the "Downloads" folder to
the actual desktop background and the file(s) wouldn't move from any
folder to there. Please make a fix for this as its already a workaround.
[By the way, this happens when you change from the the default
wallpaper].

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
Uname: Linux 4.19.0-9-generic x86_64
ApportVersion: 2.20.10-0ubuntu14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 18 13:52:46 2018
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:179b]
InstallationDate: Installed on 2018-12-18 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181218)
MachineType: Hewlett-Packard HP EliteBook 8470p
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-9-generic 
root=UUID=6c7fa075-d8d0-47c2-b828-83d330564545 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/07/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68ICF Ver. F.45
dmi.board.name: 179B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 42.36
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.45:bd10/07/2013:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1019DD202:rvnHewlett-Packard:rn179B:rvrKBCVersion42.36:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP EliteBook 8470p
dmi.product.sku: D2E04UP#ABA
dmi.product.version: A1019DD202
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.6-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
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.15-3

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


** Tags: amd64 apport-bug disco has-workaround single-occurrence ubuntu 
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/1809025

Title:
  Files Failed to Be Moved to The Desktop

Status in xorg package in Ubuntu:
  New

Bug description:
  I was trying to move a downloaded file from the "Downloads" folder to
  the actual desktop background and the file(s) wouldn't move from any
  folder to there. Please make a fix for this as its already a
  workaround. [By the way, this happens when you change from the the
  default wallpaper].

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
  Uname: Linux 4.19.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 18 13:52:46 2018
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:179b]
  InstallationDate: Installed on 2018-12-18 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181218)
  MachineType: Hewlett-Packard HP EliteBook 8470p
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-9-generic 
root=UUID=6c7fa075-d8d0-47c2-b828-83d330564545 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ICF Ver. F.45
  dmi.board.name: 179B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 42.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.moda

[Touch-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected

[Chris]

I have the same issue. Running Linux Mint with latest kernel.
Kernel: Linux 4.19.9-041909-generic #201812130432 SMP Thu Dec 13 09:34:53 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

It takes me disabling bluetooth, deleting the profile, re-enabling
bluetooth, and putting the mouse back in pairing mode to fix.

Only began happening after updating from Linux Mint 19 from Linux Mint
18.3 (I assume due to the Bluez version)

dmesg:
[ 9094.174854] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 9113.487898] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 9129.243872] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 9145.487806] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 9155.351840] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 9171.601996] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 9187.474873] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 9193.843245] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 9193.843255] Bluetooth: HIDP socket layer initialized
[ 9194.686585] hid-generic 0005:046D:B016.0002: unknown main item tag 0x0
[ 9194.686700] input: Bluetooth Mouse M336/M337/M535 Mouse as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:046D:B016.0002/input/input27
[ 9194.687692] input: Bluetooth Mouse M336/M337/M535 Consumer Control as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:046D:B016.0002/input/input28
[ 9194.687919] input: Bluetooth Mouse M336/M337/M535 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:046D:B016.0002/input/input31
[ 9194.688328] hid-generic 0005:046D:B016.0002: input,hidraw1: BLUETOOTH HID 
v12.03 Mouse [Bluetooth Mouse M336/M337/M535] on a4:34:d9:e0:9c:d1

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

Title:
  [regression] Logitech M337 mice are automatically disconnected after
  connected

Status in Bluez Utilities:
  Confirmed
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

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

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

[Touch-packages] [Bug 1809027] Re: Make retired Ubuntu keyrings available from the archive

[Dan Watkins]

** Description changed:

  Currently, if an Ubuntu developer (or their code) is attempting to
  interact with the precise archive (which is still supported in some form
  via ESM) from a machine running bionic or later, they will run in to
  issues verifying signatures, because the keys used to sign the precise
  archive are no longer included in the default keyring as of bionic.
+ 
+ (Some form of this problem will present every time an archive key
+ rotation happens; eventually the old key will no longer be trusted, and
+ similar failures to the ones today will occur.)
  
  Whilst the old keys should never be used by the system's apt (or other
  installed software), it would be good if there were some way to install
  those keys from the archives for projects which knowingly want to use
  the older signatures.  (The old keys should be in a path that isn't
  currently used by anything, so that they have to be explicitly used.)
  
  (This bug came out of a discussion on
  https://code.launchpad.net/~smoser/vmbuilder/mfdiff-apt-key-
  transition/+merge/313797.)

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

Title:
  Make retired Ubuntu keyrings available from the archive

Status in ubuntu-keyring package in Ubuntu:
  New

Bug description:
  Currently, if an Ubuntu developer (or their code) is attempting to
  interact with the precise archive (which is still supported in some
  form via ESM) from a machine running bionic or later, they will run in
  to issues verifying signatures, because the keys used to sign the
  precise archive are no longer included in the default keyring as of
  bionic.

  (Some form of this problem will present every time an archive key
  rotation happens; eventually the old key will no longer be trusted,
  and similar failures to the ones today will occur.)

  Whilst the old keys should never be used by the system's apt (or other
  installed software), it would be good if there were some way to
  install those keys from the archives for projects which knowingly want
  to use the older signatures.  (The old keys should be in a path that
  isn't currently used by anything, so that they have to be explicitly
  used.)

  (This bug came out of a discussion on
  https://code.launchpad.net/~smoser/vmbuilder/mfdiff-apt-key-
  transition/+merge/313797.)

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

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

[Touch-packages] [Bug 1809027] Re: Make retired Ubuntu keyrings available from the archive

[Scott Moser]

The easiest thing to do would be to just ship a keyring that had the
obsolete public signing keys.  Then the consumer could hard code
that 'precise' was signed with keys A, B, C.  and work stuff out like
that.

Alternatively possibly we might want to deliver some distro-info like
data.

ubuntu-release|
fingerprint | status | used-releases
790BC7277767219C42C86F933B4FE6ACC0B21F32 | expired | precise quantal raring 
saucy trusty utopic ...
F6ECB3762474EDA9D21B7022871920D1991BC93C | current | trusty utopic vivid wily 
xenial yakkety ...

Then the consumer expecting to verify 'precise' data could determine
they should use the 790B key.

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

Title:
  Make retired Ubuntu keyrings available from the archive

Status in ubuntu-keyring package in Ubuntu:
  New

Bug description:
  Currently, if an Ubuntu developer (or their code) is attempting to
  interact with the precise archive (which is still supported in some
  form via ESM) from a machine running bionic or later, they will run in
  to issues verifying signatures, because the keys used to sign the
  precise archive are no longer included in the default keyring as of
  bionic.

  (Some form of this problem will present every time an archive key
  rotation happens; eventually the old key will no longer be trusted,
  and similar failures to the ones today will occur.)

  Whilst the old keys should never be used by the system's apt (or other
  installed software), it would be good if there were some way to
  install those keys from the archives for projects which knowingly want
  to use the older signatures.  (The old keys should be in a path that
  isn't currently used by anything, so that they have to be explicitly
  used.)

  (This bug came out of a discussion on
  https://code.launchpad.net/~smoser/vmbuilder/mfdiff-apt-key-
  transition/+merge/313797.)

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

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

[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

[Dan Streetman]

** Changed in: systemd (Ubuntu Disco)
 Assignee: (unassigned) => Victor Tapia (vtapia)

** Changed in: systemd (Ubuntu Cosmic)
 Assignee: (unassigned) => Victor Tapia (vtapia)

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Victor Tapia (vtapia)

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Victor Tapia (vtapia)

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

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

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

** Changed in: systemd (Ubuntu Disco)
   Status: Confirmed => In Progress

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

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

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

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

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

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress

Bug description:
  [Impact]

  Mounting manually a network share (NFS) and masking it breaks the state of 
other units (and their dependencies).
  Casper is masking a mounted NFS share, blocking the normal boot process as 
described in the original description, but the issue comes from systemd.

  [Test Case]

  - NFS mount point at /media
  root@iscsi-bionic:/home/ubuntu# mount | grep media
  10.230.56.72:/tmp/mnt on /media type nfs4 
(rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.127,local_lock=none,addr=10.230.56.72)

  - Test mount point (/test) defined in /etc/fstab:
  root@iscsi-bionic:/home/ubuntu# cat /etc/fstab |grep test
  tmpfs /test tmpfs nosuid,nodev 0 0

  1. If media.mount is not masked, everything works fine:

  root@iscsi-bionic:/home/ubuntu# mount | grep test
  root@iscsi-bionic:/home/ubuntu# systemctl status media.mount | grep Active
 Active: active (mounted) since Thu 2018-11-15 16:03:59 UTC; 3 weeks 6 days 
ago
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: inactive (dead) since Thu 2018-12-13 10:33:52 UTC; 4min 11s ago
  root@iscsi-bionic:/home/ubuntu# systemctl start test.mount
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: active (mounted) since Thu 2018-12-13 10:38:13 UTC; 3s ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: inactive (dead) since Thu 2018-12-13 10:38:32 UTC; 3s ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test

  2. If media.mount is masked, other mounts are failing:

  root@iscsi-bionic:/home/ubuntu# systemctl mask media.mount
  Created symlink /etc/systemd/system/media.mount → /dev/null.
  root@iscsi-bionic:/home/ubuntu# systemctl start test.mount
  Job for test.mount failed.
  See "systemctl status test.mount" and "journalctl -xe" for details.
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 10s 
ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 25s 
ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl start test.mount
  Job for test.mount failed.
  See "systemctl status test.mount" and "journalctl -xe" for details.
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)

  [Regression potential]

  Minimal. Originally, one failing mount point blocked the processing of
  the rest due to how the return codes were handled for every line in
  /proc/self/mountinfo. This patch removes this "dependency" and keeps

[Touch-packages] [Bug 1807721] Re: Fix variant selection in emoji chooser

[Jeremy Bicha]

Brian, I have now added a note to the bug description to explain that
the cosmic fix is being handled as part of the gtk 3.24.2 SRU. I did
upload this fix for cosmic but I got Steve to reject it for me since we
are doing to do the 3.24.2 SRU instead. I still haven't uploaded 3.24.2
to cosmic since I expect a 3.24.3 release "soon".

If you want to accept the bionic fix, I'll wait to verify the fix until
after this issue is also fixed is in cosmic-proopsed. Or we can just
wait a bit longer for bionic too.

** Description changed:

  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.
  
  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
  Right-click (or long-click) on the emoji and select one of the skin tones 
instead of the default yellow.
  The emoji with the skin tone you selected should be added to the text area.
  
  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.
  
  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.
  
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME
  
  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398
+ 
+ Other Info
+ ==
+ This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked in LP: 
#1808233

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: In Progress => Triaged

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

Title:
  Fix variant selection in emoji chooser

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Bionic:
  In Progress
Status in gtk+3.0 source package in Cosmic:
  Triaged

Bug description:
  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
  Right-click (or long-click) on the emoji and select one of the skin tones 
instead of the default yellow.
  The emoji with the skin tone you selected should be added to the text area.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398

  Other Info
  ==
  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked in LP: 
#1808233

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

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

[Touch-packages] [Bug 1807719] Re: Some emoji in emoji chooser are black & white

[Jeremy Bicha]

** Description changed:

  Impact
  ==
  Some emoji in the emoji chooser show as black & white.
  
  This is because these emoji default to "text presentation" instead of
  "emoji presentation".
  
  More information and a screenshot can be found in the pango issue linked
  below.
  
  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Browse through the emoji list. All should be in full color.
  
  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.
  
  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.
  
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME
  
  https://gitlab.gnome.org/GNOME/pango/issues/334
  https://gitlab.gnome.org/GNOME/gtk/commit/aac38198a3f5
  https://gitlab.gnome.org/GNOME/gtk/commit/b74e3209a5af0
  
  Other Info
  ==
  This adds an extra variation selector byte to each emoji added via the emoji 
chooser. (Many emoji are made up of multiple bytes.) This will not affect emoji 
added to GTK apps in other ways, such as copying and pasting from an app where 
the emoji doesn't have that variation selector added to it.
+ 
+ This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked in
+ LP: #1808233

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: In Progress => Triaged

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

Title:
  Some emoji in emoji chooser are black & white

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Bionic:
  In Progress
Status in gtk+3.0 source package in Cosmic:
  Triaged

Bug description:
  Impact
  ==
  Some emoji in the emoji chooser show as black & white.

  This is because these emoji default to "text presentation" instead of
  "emoji presentation".

  More information and a screenshot can be found in the pango issue
  linked below.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Browse through the emoji list. All should be in full color.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  https://gitlab.gnome.org/GNOME/pango/issues/334
  https://gitlab.gnome.org/GNOME/gtk/commit/aac38198a3f5
  https://gitlab.gnome.org/GNOME/gtk/commit/b74e3209a5af0

  Other Info
  ==
  This adds an extra variation selector byte to each emoji added via the emoji 
chooser. (Many emoji are made up of multiple bytes.) This will not affect emoji 
added to GTK apps in other ways, such as copying and pasting from an app where 
the emoji doesn't have that variation selector added to it.

  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked
  in LP: #1808233

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

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

[Touch-packages] [Bug 1807288] Re: mkfs.ext4 -d $directory_with_acls leads to EINVAL

[Launchpad Bug Tracker]

This bug was fixed in the package e2fsprogs - 1.44.4-2ubuntu0.1

---
e2fsprogs (1.44.4-2ubuntu0.1) cosmic; urgency=medium

  * debian/patches/0001-libext2fs-fix-regression-so-we-are-correctly-
transla.patch: cherry-pick upstream fix so we are correctly translating
acls in mkfs.ext4.  Closes LP: #1807288.

 -- Steve Langasek   Fri, 07 Dec 2018
12:12:52 +0200

** Changed in: e2fsprogs (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  mkfs.ext4 -d $directory_with_acls leads to EINVAL

Status in e2fsprogs package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Bionic:
  Fix Committed
Status in e2fsprogs source package in Cosmic:
  Fix Released
Status in e2fsprogs source package in Disco:
  Fix Released

Bug description:
  [Justification]
  `mkfs.ext4 -d` can produce broken filesystems when there are acls in the tree 
used as input.

  [Test case]
  1. dd if=/dev/zero count=0 bs=1M seek=100 of=./fake.img
  2. mkdir -p stuff/journal
  3. sudo apt install acl
  4. setfacl -m g:adm:rwx stuff/journal
  5. mkfs.ext4 -L lala -O -metadata_csum -T default -O uninit_bg fake.img -d 
./stuff/
  6. sudo mount ./fake.img /mnt
  7. Verify that `getfacl /mnt/journal/` returns an error.
  8. sudo umount /mnt
  9. install libext2fs2 from -proposed.
  10. mkfs.ext4 -L lala -O -metadata_csum -T default -O uninit_bg fake.img -d 
./stuff/
  11. sudo mount ./fake.img /mnt
  12. Verify that `getfacl /mnt/journal/` returns acl information, not an error.
  13. sudo umount /mnt

  [Original description]

  This looks an awful lot like bug 1645232 but that is claimed to be
  fixed:

  mwhudson@ringil:~/tmp$ mkfs.ext4 -V
  mke2fs 1.44.1 (24-Mar-2018)
   Using EXT2FS Library version 1.44.1
  mwhudson@ringil:~/tmp$ dd if=/dev/zero count=0 bs=1M seek=100 of=./fake.img
  0+0 records in
  0+0 records out
  0 bytes copied, 0.0015871 s, 0.0 kB/s
  mwhudson@ringil:~/tmp$ mkdir -p stuff/journal
  mwhudson@ringil:~/tmp$ setfacl -m g:adm:rwx stuff/journal
  mwhudson@ringil:~/tmp$ mkfs.ext4 -L lala -O -metadata_csum -T default -O 
uninit_bg fake.img -d ./stuff/
  mke2fs 1.44.1 (24-Mar-2018)
  Discarding device blocks: done
  Creating filesystem with 25600 4k blocks and 6400 inodes

  Allocating group tables: done
  Writing inode tables: done
  Creating journal (1024 blocks): done
  Copying files into the device: done
  Writing superblocks and filesystem accounting information: done

  mwhudson@ringil:~/tmp$ sudo mount ./fake.img /mnt
  mwhudson@ringil:~/tmp$ getfacl /mnt/journal/
  getfacl: /mnt/journal/: Invalid argument

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

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

[Touch-packages] [Bug 1807288] Update Released

[Brian Murray]

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

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

Title:
  mkfs.ext4 -d $directory_with_acls leads to EINVAL

Status in e2fsprogs package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Bionic:
  Fix Committed
Status in e2fsprogs source package in Cosmic:
  Fix Released
Status in e2fsprogs source package in Disco:
  Fix Released

Bug description:
  [Justification]
  `mkfs.ext4 -d` can produce broken filesystems when there are acls in the tree 
used as input.

  [Test case]
  1. dd if=/dev/zero count=0 bs=1M seek=100 of=./fake.img
  2. mkdir -p stuff/journal
  3. sudo apt install acl
  4. setfacl -m g:adm:rwx stuff/journal
  5. mkfs.ext4 -L lala -O -metadata_csum -T default -O uninit_bg fake.img -d 
./stuff/
  6. sudo mount ./fake.img /mnt
  7. Verify that `getfacl /mnt/journal/` returns an error.
  8. sudo umount /mnt
  9. install libext2fs2 from -proposed.
  10. mkfs.ext4 -L lala -O -metadata_csum -T default -O uninit_bg fake.img -d 
./stuff/
  11. sudo mount ./fake.img /mnt
  12. Verify that `getfacl /mnt/journal/` returns acl information, not an error.
  13. sudo umount /mnt

  [Original description]

  This looks an awful lot like bug 1645232 but that is claimed to be
  fixed:

  mwhudson@ringil:~/tmp$ mkfs.ext4 -V
  mke2fs 1.44.1 (24-Mar-2018)
   Using EXT2FS Library version 1.44.1
  mwhudson@ringil:~/tmp$ dd if=/dev/zero count=0 bs=1M seek=100 of=./fake.img
  0+0 records in
  0+0 records out
  0 bytes copied, 0.0015871 s, 0.0 kB/s
  mwhudson@ringil:~/tmp$ mkdir -p stuff/journal
  mwhudson@ringil:~/tmp$ setfacl -m g:adm:rwx stuff/journal
  mwhudson@ringil:~/tmp$ mkfs.ext4 -L lala -O -metadata_csum -T default -O 
uninit_bg fake.img -d ./stuff/
  mke2fs 1.44.1 (24-Mar-2018)
  Discarding device blocks: done
  Creating filesystem with 25600 4k blocks and 6400 inodes

  Allocating group tables: done
  Writing inode tables: done
  Creating journal (1024 blocks): done
  Copying files into the device: done
  Writing superblocks and filesystem accounting information: done

  mwhudson@ringil:~/tmp$ sudo mount ./fake.img /mnt
  mwhudson@ringil:~/tmp$ getfacl /mnt/journal/
  getfacl: /mnt/journal/: Invalid argument

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

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

[Touch-packages] [Bug 1809011] Re: package cups 2.2.7-1ubuntu2.1 failed to install/upgrade: read error in '/var/lib/dpkg/info/cups.triggers': Input/output error

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

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

** Tags added: hardware-error

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

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

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

Title:
  package cups 2.2.7-1ubuntu2.1 failed to install/upgrade: read error in
  '/var/lib/dpkg/info/cups.triggers': Input/output error

Status in cups package in Ubuntu:
  Invalid

Bug description:
  Mientrasactualizaba el sistema recien instalado

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Dec 18 17:50:57 2018
  DuplicateSignature:
   package:cups:2.2.7-1ubuntu2.1
   Preparing to unpack .../074-cups_2.2.7-1ubuntu2.2_amd64.deb ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-0IVoPc/074-cups_2.2.7-1ubuntu2.2_amd64.deb (--unpack):
read error in '/var/lib/dpkg/info/cups.triggers': Input/output error
  ErrorMessage: read error in '/var/lib/dpkg/info/cups.triggers': Input/output 
error
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Packard Bell EasyNote TS44HR
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=f9b48e7f-1e8e-46a2-b720-967fe70d5dde ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=f9b48e7f-1e8e-46a2-b720-967fe70d5dde ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: cups
  Title: package cups 2.2.7-1ubuntu2.1 failed to install/upgrade: read error in 
'/var/lib/dpkg/info/cups.triggers': Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2011
  dmi.bios.vendor: Packard Bell
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SJV50_HR
  dmi.board.vendor: Packard Bell
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Packard Bell
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnPackardBell:bvrV1.11:bd05/24/2011:svnPackardBell:pnEasyNoteTS44HR:pvrV1.11:rvnPackardBell:rnSJV50_HR:rvrBaseBoardVersion:cvnPackardBell:ct10:cvrV1.11:
  dmi.product.name: EasyNote TS44HR
  dmi.product.version: V1.11
  dmi.sys.vendor: Packard Bell

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

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

[Touch-packages] [Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided

[Ubuntu Foundations Team Bug Bot]

The attachment "dirty_patch.txt" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

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

** Tags added: patch

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

Title:
  At dual monitor intel_do_flush_locked failed: Resource deadlock
  avoided

Status in gnome-shell package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Using ubuntu wayland with dual monitors, configured above each other.
  Dock is configured at both displays, not hiding.
  Icons for "terminal" and "libreofffice Writer" are present at the dock.

  Start terminal on primary screen by mouseclick on dock.
  Start libreoffice Writer on primary screen by mouseclick on dock.
  Terminate libreoffice Witer by mouseclick on X.
  Repeat the starting and stopping of Writer.

  Login-screen will appear. Syslog shows:
  Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked 
failed: Resource deadlock avoided
  Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from 
display: Connection reset by peer
  Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main 
process exited, code=exited, status=1/FAILURE

  This problem doesnot occur in a dual monitor-session without wayland.
  It also doesnot occur, if only one monitor used with wayland
  It also doesnot occur, if the dock is only present at the primary screen.
  It also doesnot occur if second started application is present at the dock 
and doesnot add an icon to the dock (as libreoffice does).

  All other dual monitor/dock configurations seem to have this problem.

  No idea if this is helpful info, but the used graphics card does not support 
OpenGL version 2.1:
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 
2.1 or later.
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor, falling back to sw

  glxinfo:
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.1 Mesa 18.2.2
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic i686
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 15 13:25:10 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1809025] Re: Files Failed to Be Moved to The Desktop

[Juhani Numminen]

Reassigning to nautilus which I believe manages the desktop on GNOME.

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

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

Title:
  Files Failed to Be Moved to The Desktop

Status in nautilus package in Ubuntu:
  New

Bug description:
  I was trying to move a downloaded file from the "Downloads" folder to
  the actual desktop background and the file(s) wouldn't move from any
  folder to there. Please make a fix for this as its already a
  workaround. [By the way, this happens when you change from the the
  default wallpaper].

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
  Uname: Linux 4.19.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 18 13:52:46 2018
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:179b]
  InstallationDate: Installed on 2018-12-18 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181218)
  MachineType: Hewlett-Packard HP EliteBook 8470p
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-9-generic 
root=UUID=6c7fa075-d8d0-47c2-b828-83d330564545 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ICF Ver. F.45
  dmi.board.name: 179B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 42.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.45:bd10/07/2013:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1019DD202:rvnHewlett-Packard:rn179B:rvrKBCVersion42.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 8470p
  dmi.product.sku: D2E04UP#ABA
  dmi.product.version: A1019DD202
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  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.15-3

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

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

[Touch-packages] [Bug 1808710] [NEW] !xcb_xlib_threads_sequence_lost error

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Several applications randomly crash with same error. See attached files.

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

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

[Touch-packages] [Bug 1804910] Re: pip3 cannot install gmpy

[Hans Joachim Desserud]

Great to hear :)

I'm closing this report then.

** Changed in: python3-defaults (Ubuntu)
   Status: Incomplete => 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/1804910

Title:
  pip3 cannot install gmpy

Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  I'm using python3 and want gmpy.  Attempts to install it fail.

  I routinely capture the output of maintenance tasks, and am attaching
  the results.  This output begins with the text of the shell script I
  wrote to do this, which includes calls to the bash functions I wrote
  to do this self-referential magic.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: python3 3.6.7-1~18.04
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 17:44:44 2018
  InstallationDate: Installed on 2018-10-18 (36 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  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/python3-defaults/+bug/1804910/+subscriptions

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

[Touch-packages] [Bug 1808710] Re: !xcb_xlib_threads_sequence_lost error

[Ilya Kotov]

** Attachment added: "_usr_bin_gpicview.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1808710/+attachment/522/+files/_usr_bin_gpicview.1000.crash

** Package changed: freecad (Ubuntu) => gtk+2.0 (Ubuntu)

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

Title:
  !xcb_xlib_threads_sequence_lost error

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Some gkt2 applications randomly crash with same error. See attached
  files.

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

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

[Touch-packages] [Bug 1808710] Re: !xcb_xlib_threads_sequence_lost error

[Ilya Kotov]

** Description changed:

- Several applications randomly crash with same error. See attached files.
+ Some gkt2 applications randomly crash with same error. See attached
+ files.

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

Title:
  !xcb_xlib_threads_sequence_lost error

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Some gkt2 applications randomly crash with same error. See attached
  files.

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

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

[Touch-packages] [Bug 1809044] [NEW] DVD playback error: unable to play . . . DVD source is required . . .

[Chris Rainey]

Public bug reported:

Successful installation of libdvd-pkg and dpkg-reconfigure, afterwards,
to complete compilation.

Inserted known-good DVD and clicked on "Open in Videos" which launched
the Totem player.

Error msg:  "Unable to play the file, DVD source is required, but is not
installed."

DVD will play normally in VLC player after installation on same machine.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: libgstreamer1.0-0 1.14.4-1
ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
Uname: Linux 4.18.0-12-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 18 15:21:45 2018
InstallationDate: Installed on 2018-11-13 (34 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic

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

Title:
  DVD playback error:  unable to play . . . DVD source is required . . .

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Successful installation of libdvd-pkg and dpkg-reconfigure,
  afterwards, to complete compilation.

  Inserted known-good DVD and clicked on "Open in Videos" which launched
  the Totem player.

  Error msg:  "Unable to play the file, DVD source is required, but is
  not installed."

  DVD will play normally in VLC player after installation on same
  machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.4-1
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 18 15:21:45 2018
  InstallationDate: Installed on 2018-11-13 (34 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Touch-packages] [Bug 1809014] Re: mpeg-2 detected as tga (Targa image)

[Juhani Numminen]

** Tags added: cosmic

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

Title:
  mpeg-2 detected as tga (Targa image)

Status in file package in Ubuntu:
  New

Bug description:
  It appears that currently using either the file command or through the
  File::LibMagic interface that 1:5.34-2 on Cosmic (18.10) makes a
  MPEG-2 file be detected as Targa at a higher priority, thus taking
  precedence over being what it actually is. See the below lines as
  examples using clips from
  http://hubblesource.stsci.edu/sources/video/clips/ as examples:

  $ file -k /home/piratefinn/Downloads/hst_2.mpg 
  /home/piratefinn/Downloads/hst_2.mpg: Targa image data - Map 63635 x 65536 x 
1 +268 +60928 - 11-bit alpha - top - right - four way interleave MPEG sequence, 
v2, program multiplex (Lepton 3.x), scale 0-0, spot sensor temperature 
0.00, unit celsius, color scheme 0, calibration: offset 0.00, slope 
0.00\012- data

  Note that this appears to only affect MPEG-2 (and possibly higher) as
  MPEG-1 is detected corretly.

  $ file -k /home/piratefinn/Downloads/hst_1.mpg 
  /home/piratefinn/Downloads/hst_1.mpg: MPEG sequence, v1, progressive Y'CbCr 
4:2:0 video, 320x240, 4:3, 29.97 fps (Lepton 2.x), scale 1-2, spot sensor 
temperature 0.00, unit celsius, color scheme 0, show spot sensor, show 
scale bar, maximum point enabled, calibration: offset 586.228088, slope 
-411899156202779801569722368.00\012- data
  file -k /home/piratefinn/Downloads/hst_1.mpg

  This appears to not be an issue in 1:5.25 used in 16.04, however
  looking through the github it appears since then in possible 5.26 (or
  above) changes as seen in
  https://github.com/file/file/commit/aee048a020badb5f36008f6d11e7d5b32834bcb2
  affected this.

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

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

[Touch-packages] [Bug 1767314] Re: Ubuntu Bionic vi/vim not working correctly

[flashydave]

Further investigation with a recompiled version more recent than that
shipped with 18.04 yields that syntax highlighting failure is caused by
redrawtime being exceeded  - often triggered after using G to move to
the end of the file. It is not possible to set "syntax on" manually at
that point as it immediatetly gets disabled again unless you move to the
start of the file with g.

This explains the "persistence" due to the "jump to the previously
edited line in the file" setting being set - but forgetting it upon
deletion of .viminfo as this is where this Info is stored.  Without it
vi opens with the cursor at line 1.

In my case this problem has occurred following an upgrade and has never
happened before on the same hardware running the same applications for
many years with lots of files being edited multiple times every day -
day in day out.  Ie something in the timing dynamics when running vi has
changed wirh 18.04

See https://github.com/vim/vim/issues/2790 for further discussion and
possible workarounds.

** Bug watch added: github.com/vim/vim/issues #2790
   https://github.com/vim/vim/issues/2790

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

Title:
  Ubuntu Bionic vi/vim not working correctly

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  The vim default configuration in Bionic does not match Ubuntu 17.10
  nor Centos 7 and is hard to use. It auto-inserts tabs or spaces, and
  the '/' search mode command works differently (pressing enter is
  required before you can use cursors left/right).

  For some discussion, please see
  https://askubuntu.com/questions/1026820/vi-vim-usage-in-ubuntu-bionic-
  not-normal/1028684#1028684

  Setting :set nocompatbile in ~/.vimrc fixes it, but this should not be
  required.

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

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

[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

[Brian Murray]

Hello Daniel, or anyone else affected,

Accepted gnome-shell into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.30.1-2ubuntu1.18.10.2 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: gnome-shell (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-cosmic

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Fix Committed
Status in ibus source package in Cosmic:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/391

  ---

  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean
  users are simply unable to fill in password fields that previously
  were working fine. (see "ACTUAL RESULTS" below)

  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
    (click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).

  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun

[Touch-packages] [Bug 1767314] Re: Ubuntu Bionic vi/vim not working correctly

[flashydave]

Just by way of more info I was editing a gitolite conf file of 4096 lines with 
the following stats to render the syntax with the cursor at the end of the file
The total time taken was 5 seconds. By default redrawtime is set to 2 seconds 
so the 5 srconds taken represents a considetable drop off in performance.  It 
is true that 18.04 feels sluggish. Maybe Spectre malware fix slowdowns?


TOTAL  COUNT  MATCH   SLOWEST AVERAGE   NAME   PATTERN
  1.580522   4214   96  0.0028750.000375  gitoliteRefex  
\(^\s*\(-\|R\|RW+\?C\?D\?\)\s\+\)\@<=\S.\{-}\(\s*=
  1.542289   4068   27120.0060480.000379  gitoliteConfigKey  
\(\(config\|option\)\s\+\)\@<=[^ =]*
  0.986339   1426   0   0.0327780.000692  gitoliteCreateRule 
\(^\s*C\s.*=\s*\)\@<=\S[^#]*[^# ]
  0.777079   4068   40680.0008700.000191  gitoliteConfigVal  
\(=\s*\)\@<=\S.*
  0.652198   1502   95  0.040.000434  gitoliteDenyRule   
\(^\s*-\s.*=\s*\)\@<=\S[^#]*[^# ]
  0.059132   2852   14260.0001000.21  gitoliteRule   
\(^\s*\)\@<=\(-\|C\|R\|RW+\?C\?D\?\)\s\@=
  0.033258   4118   13560.490.08  gitoliteConfigLine 
^\s*\(config\|option\|include\|subconf\)\s[^#]*
  0.024610   4142   14260.350.06  gitoliteRuleLine   
^\s*\(-\|C\|R\|RW+\?C\?D\?\)\s[^#]*
  0.016784   6026   32580.130.03  gitoliteGroup  @\S\+
  0.014909   4142   13950.130.04  gitoliteRepoError  
^\s*\S\+\s*=
  0.014868   4118   657 0.450.04  gitoliteRepoLine   
^\s*repo\s\+[^=]*$
  0.013410   4118   0   0.440.03  gitoliteRepoError  ^\s*repo.*=
  0.010654   4400   574 0.450.02  gitoliteComment#.*
  0.004946   4118   1   0.140.01  gitoliteGroupLine  
^\s*@\S\+\s*=\s*\S.*$
  0.003386   4118   0   0.090.01  gitoliteTemplateLine ^=begin 
template-data$
  0.001547   4118   0   0.020.00  gitoliteSpecialRefex /USER/
  0.001208   4118   0   0.010.00  gitoliteSpecialRefex NAME/

  5.737139   65666

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

Title:
  Ubuntu Bionic vi/vim not working correctly

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  The vim default configuration in Bionic does not match Ubuntu 17.10
  nor Centos 7 and is hard to use. It auto-inserts tabs or spaces, and
  the '/' search mode command works differently (pressing enter is
  required before you can use cursors left/right).

  For some discussion, please see
  https://askubuntu.com/questions/1026820/vi-vim-usage-in-ubuntu-bionic-
  not-normal/1028684#1028684

  Setting :set nocompatbile in ~/.vimrc fixes it, but this should not be
  required.

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

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

[Touch-packages] [Bug 374079] Re: Internal microphone doesn't work at all

[David VANTYGHEM]

I have this problem with Ubuntu 18.04, 18.10 and Linux Mint 19, on 2 computers :
HP Pavilion dv6700 and Acer Extensa 5620Z, both with a Realtek ALC268 chipset.
Audio is working but not internal microphone (and on HP Pavilion, external 
microphone doesn't work too).

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

Title:
  Internal microphone doesn't work at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  My computer is Acer TravelMate 7520G. Ubuntu 9.04 Jaunty Jackalope.

  Sound card is working otherwise ok, but the internal microphone does't
  work at all. I've tired modifying the alsa-base.conf file's last row
  to read like: options snd-hda-intel model=acer-aspire, options snd-
  hda-intel model=acer and the third one for digital built-in acer mic.
  None of the above have worked.

  
  From the user's point of wiev it seems like the microphone cannot be 
activated at all. If I try to activate my microphone from sound menu (from top 
right corner on desk top) -> volume control -> record (tab), the microphone is 
allways showing a red cross (like it is muted). The red cross can be removed, 
but the red cross appears back after closing the control panel. 

  After test recording with mic activated the result is only static
  noise during play-back.

  ProblemType: Bug
  AplayDevices:
    Luettelo PLAYBACK laitteista 
   kortti 0: SB [HDA ATI SB], laite 0: ALC268 Analog [ALC268 Analog]
 Alalaitteet: 1/1
 Alalaite #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    Luettelo CAPTURE laitteista 
   kortti 0: SB [HDA ATI SB], laite 0: ALC268 Analog [ALC268 Analog]
 Alalaitteet: 1/1
 Alalaite #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kone   3631 F mixer_applet2
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xf060 irq 16'
 Mixer name : 'Realtek ALC268'
 Components : 'HDA:10ec0268,10250124,0013 
HDA:14f12c06,10250093,0010'
 Controls  : 11
 Simple ctrls  : 8
  CurrentDmesg:
   [   26.471439] sky2 eth0: enabling interface
   [   26.471669] ADDRCONF(NETDEV_UP): eth0: link is not ready
   [   31.097025] eth1: no IPv6 routers present
   [   84.500043] Clocksource tsc unstable (delta = -288762894 ns)
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: fglrx
  Package: alsa-base 1.0.18.dfsg-1ubuntu8
  PackageArchitecture: all
  ProcEnviron:
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Uname: Linux 2.6.28-11-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/374079/+subscriptions

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

[Touch-packages] [Bug 374079] Re: Internal microphone doesn't work at all

[David VANTYGHEM]

As explained in https://elubuntero.wordpress.com/tag/realtek-alc268/ , I
tried to add linux-backports-modules-*** but this package isn't anymore
in Ubuntu and Mint repositories.

I tried all options as explained in https://doc.ubuntu-
fr.org/audio_intel_hda , no result. Please heelp.

** Changed in: alsa-driver (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  Internal microphone doesn't work at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  My computer is Acer TravelMate 7520G. Ubuntu 9.04 Jaunty Jackalope.

  Sound card is working otherwise ok, but the internal microphone does't
  work at all. I've tired modifying the alsa-base.conf file's last row
  to read like: options snd-hda-intel model=acer-aspire, options snd-
  hda-intel model=acer and the third one for digital built-in acer mic.
  None of the above have worked.

  
  From the user's point of wiev it seems like the microphone cannot be 
activated at all. If I try to activate my microphone from sound menu (from top 
right corner on desk top) -> volume control -> record (tab), the microphone is 
allways showing a red cross (like it is muted). The red cross can be removed, 
but the red cross appears back after closing the control panel. 

  After test recording with mic activated the result is only static
  noise during play-back.

  ProblemType: Bug
  AplayDevices:
    Luettelo PLAYBACK laitteista 
   kortti 0: SB [HDA ATI SB], laite 0: ALC268 Analog [ALC268 Analog]
 Alalaitteet: 1/1
 Alalaite #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    Luettelo CAPTURE laitteista 
   kortti 0: SB [HDA ATI SB], laite 0: ALC268 Analog [ALC268 Analog]
 Alalaitteet: 1/1
 Alalaite #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kone   3631 F mixer_applet2
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xf060 irq 16'
 Mixer name : 'Realtek ALC268'
 Components : 'HDA:10ec0268,10250124,0013 
HDA:14f12c06,10250093,0010'
 Controls  : 11
 Simple ctrls  : 8
  CurrentDmesg:
   [   26.471439] sky2 eth0: enabling interface
   [   26.471669] ADDRCONF(NETDEV_UP): eth0: link is not ready
   [   31.097025] eth1: no IPv6 routers present
   [   84.500043] Clocksource tsc unstable (delta = -288762894 ns)
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: fglrx
  Package: alsa-base 1.0.18.dfsg-1ubuntu8
  PackageArchitecture: all
  ProcEnviron:
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Uname: Linux 2.6.28-11-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/374079/+subscriptions

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

[Touch-packages] [Bug 1809053] [NEW] package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess was killed by signal (Abo

[David Langolf]

Public bug reported:

doesn't seem to be a major issue.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: openssh-server 1:7.6p1-4ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic i686
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: i386
Date: Tue Dec 18 08:31:24 2018
ErrorMessage: installed openssh-server package post-installation script 
subprocess was killed by signal (Aborted)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: openssh
Title: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess was killed 
by signal (Aborted)
UpgradeStatus: Upgraded to bionic on 2018-12-18 (0 days ago)

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


** Tags: apport-package bionic i386

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

Title:
  package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  was killed by signal (Aborted)

Status in openssh package in Ubuntu:
  New

Bug description:
  doesn't seem to be a major issue.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: openssh-server 1:7.6p1-4ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  Date: Tue Dec 18 08:31:24 2018
  ErrorMessage: installed openssh-server package post-installation script 
subprocess was killed by signal (Aborted)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: openssh
  Title: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess was killed 
by signal (Aborted)
  UpgradeStatus: Upgraded to bionic on 2018-12-18 (0 days ago)

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

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

[Touch-packages] [Bug 1767314] Re: Ubuntu Bionic vi/vim not working correctly

[flashydave]

Setting regexpengine=1 drops this back down to 1.4 seconds. So either
this is the root cause of this particular slowdown (i.e. when syntax
highlighting gitolite format files) or at least compensates for whatever
is the root cause.  According to
https://stackoverflow.com/posts/38521226 the default regexp engine
changed with Vim 7.4. This was the version shipped with Trusty onwards
so in theory was already in use on 14.04 and 16.04 ubuntu so something
doesnt quite tie up

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

Title:
  Ubuntu Bionic vi/vim not working correctly

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  The vim default configuration in Bionic does not match Ubuntu 17.10
  nor Centos 7 and is hard to use. It auto-inserts tabs or spaces, and
  the '/' search mode command works differently (pressing enter is
  required before you can use cursors left/right).

  For some discussion, please see
  https://askubuntu.com/questions/1026820/vi-vim-usage-in-ubuntu-bionic-
  not-normal/1028684#1028684

  Setting :set nocompatbile in ~/.vimrc fixes it, but this should not be
  required.

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

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

[Touch-packages] [Bug 1808493] Re: Let's Encrypt CA Root Certificates missing

[Seth Arnold]

Thanks, I'll mark it "invalid" to take it off our radar again.

** Changed in: ca-certificates (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Let's Encrypt CA Root Certificates missing

Status in ca-certificates package in Ubuntu:
  Invalid

Bug description:
  Please add the Chain of trust for the Let's Encrypt CA to the ubuntu
  ca-certificates

  https://letsencrypt.org/certificates/


  we have to add them always manually and i think it's time to accept,
  that let's encrypt is now one of the bigger CA.

  
  Missing in releases 16.04  LTS / 18.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1808493/+subscriptions

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

[Touch-packages] [Bug 1809053] Re: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess was killed by signal (Abort

[Seth Arnold]

This is sure surprising:

(frontend:26097): Pango-WARNING **: 01:57:45.798: font_face 
status is: out of memory
...
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: 
assertion failed (error == NULL): Failed to load 
/usr/share/icons/Humanity/status/48/image-missing.svg: Error opening file 
/usr/share/icons/Humanity/status/48/image-missing.svg: Too many open files 
(g-io-error-quark, 31)
dpkg: error processing package openssh-server (--configure):
 installed openssh-server package post-installation script subprocess was 
killed by signal (Aborted)

Do you know how the system got "too many open files" as an error
message? that's normally pretty hard to hit.

Thanks

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

Title:
  package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  was killed by signal (Aborted)

Status in openssh package in Ubuntu:
  New

Bug description:
  doesn't seem to be a major issue.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: openssh-server 1:7.6p1-4ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  Date: Tue Dec 18 08:31:24 2018
  ErrorMessage: installed openssh-server package post-installation script 
subprocess was killed by signal (Aborted)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: openssh
  Title: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess was killed 
by signal (Aborted)
  UpgradeStatus: Upgraded to bionic on 2018-12-18 (0 days ago)

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

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

[Touch-packages] [Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided

[Daniel van Vugt]

Gert,

Please report the problem to the Mesa developers who will best be able
to help:

  https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa

and then let us know the new bug ID.

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

Title:
  At dual monitor intel_do_flush_locked failed: Resource deadlock
  avoided

Status in gnome-shell package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Using ubuntu wayland with dual monitors, configured above each other.
  Dock is configured at both displays, not hiding.
  Icons for "terminal" and "libreofffice Writer" are present at the dock.

  Start terminal on primary screen by mouseclick on dock.
  Start libreoffice Writer on primary screen by mouseclick on dock.
  Terminate libreoffice Witer by mouseclick on X.
  Repeat the starting and stopping of Writer.

  Login-screen will appear. Syslog shows:
  Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked 
failed: Resource deadlock avoided
  Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from 
display: Connection reset by peer
  Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main 
process exited, code=exited, status=1/FAILURE

  This problem doesnot occur in a dual monitor-session without wayland.
  It also doesnot occur, if only one monitor used with wayland
  It also doesnot occur, if the dock is only present at the primary screen.
  It also doesnot occur if second started application is present at the dock 
and doesnot add an icon to the dock (as libreoffice does).

  All other dual monitor/dock configurations seem to have this problem.

  No idea if this is helpful info, but the used graphics card does not support 
OpenGL version 2.1:
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 
2.1 or later.
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor, falling back to sw

  glxinfo:
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.1 Mesa 18.2.2
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic i686
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 15 13:25:10 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[VanVan]

** Changed in: alsa-driver (Ubuntu)
   Status: Confirmed => Fix Committed

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

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  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/alsa-driver/+bug/1784485/+subscriptions

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

[Touch-packages] [Bug 1808990] Re: Xorg freeze

[Daniel van Vugt]

If you can't log in remotely any more then that sounds like a kernel
issue. But regardless, please:

 1. Reproduce the freeze again.

 2. Reboot

 3. Run this command to collect the system log from the previous
(frozen) boot:

journalctl -b-1 > prevboot.txt

 4. Attach the file 'prevboot.txt' to the bug here.


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

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

** Tags added: nouveau

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

Title:
  Xorg freeze

Status in Ubuntu:
  Incomplete

Bug description:
  The screen appears to freeze, with possible SSH access from another machine 
during the first minutes. After that, the system totally freezes, with not even 
ethernet connection anymore.
  Only hard reboot helps to solve the issue, with normal functionality 
afterwards.
  It occurs in a random way.

  Ubuntu version 18.04.1 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 18 15:32:13 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-39-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GpuHangFrequency: Once a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GK208 [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 730] [1043:850c]
  InstallationDate: Installed on 2018-11-14 (34 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=7af5a6a3-c5c3-48e2-9477-704034a9e379 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1804
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1804:bd06/07/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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 
2:2.99.917+git20171229-1
  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/+bug/1808990/+subscriptions

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

[Touch-packages] [Bug 374079] Re: Internal microphone doesn't work at all

[Daniel van Vugt]

David,

Please log your own new bug from an affected machine by running:

  ubuntu-bug pulseaudio


** Changed in: alsa-driver (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Internal microphone doesn't work at all

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  My computer is Acer TravelMate 7520G. Ubuntu 9.04 Jaunty Jackalope.

  Sound card is working otherwise ok, but the internal microphone does't
  work at all. I've tired modifying the alsa-base.conf file's last row
  to read like: options snd-hda-intel model=acer-aspire, options snd-
  hda-intel model=acer and the third one for digital built-in acer mic.
  None of the above have worked.

  
  From the user's point of wiev it seems like the microphone cannot be 
activated at all. If I try to activate my microphone from sound menu (from top 
right corner on desk top) -> volume control -> record (tab), the microphone is 
allways showing a red cross (like it is muted). The red cross can be removed, 
but the red cross appears back after closing the control panel. 

  After test recording with mic activated the result is only static
  noise during play-back.

  ProblemType: Bug
  AplayDevices:
    Luettelo PLAYBACK laitteista 
   kortti 0: SB [HDA ATI SB], laite 0: ALC268 Analog [ALC268 Analog]
 Alalaitteet: 1/1
 Alalaite #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    Luettelo CAPTURE laitteista 
   kortti 0: SB [HDA ATI SB], laite 0: ALC268 Analog [ALC268 Analog]
 Alalaitteet: 1/1
 Alalaite #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kone   3631 F mixer_applet2
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xf060 irq 16'
 Mixer name : 'Realtek ALC268'
 Components : 'HDA:10ec0268,10250124,0013 
HDA:14f12c06,10250093,0010'
 Controls  : 11
 Simple ctrls  : 8
  CurrentDmesg:
   [   26.471439] sky2 eth0: enabling interface
   [   26.471669] ADDRCONF(NETDEV_UP): eth0: link is not ready
   [   31.097025] eth1: no IPv6 routers present
   [   84.500043] Clocksource tsc unstable (delta = -288762894 ns)
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: fglrx
  Package: alsa-base 1.0.18.dfsg-1ubuntu8
  PackageArchitecture: all
  ProcEnviron:
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Uname: Linux 2.6.28-11-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/374079/+subscriptions

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

[Touch-packages] [Bug 1809053] Re: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess was killed by signal (Abort

[David Langolf]

Unfortunately I don't. I let it run, came back a couple hours later and
it wasn't accepting my password. I just let it continue. Was able to
login in the morning and it finished installing while I was at work.
When I got home it worked except for the installation errors posted
here.

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

Title:
  package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  was killed by signal (Aborted)

Status in openssh package in Ubuntu:
  New

Bug description:
  doesn't seem to be a major issue.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: openssh-server 1:7.6p1-4ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  Date: Tue Dec 18 08:31:24 2018
  ErrorMessage: installed openssh-server package post-installation script 
subprocess was killed by signal (Aborted)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: openssh
  Title: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess was killed 
by signal (Aborted)
  UpgradeStatus: Upgraded to bionic on 2018-12-18 (0 days ago)

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

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

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[VanVan]

It's already commited, check here :
http://mailman.alsa-project.org/pipermail/alsa-devel/2018-December/143282.html

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  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/alsa-driver/+bug/1784485/+subscriptions

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

[Touch-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work

[Hui Wang]

The build failure for cosmic and bionic (after applying the debdiff of
#2 and #3) is because I forgot to add one more patch to add this ucm to
configure.ac.

here I fixed it, and generate an incremental debdiff for cosmic (since
the debdiff of #2 is already merged to cosmic-proposed branch). If need
me put this debdiff and the debdiff of #2 into one debdiff, let me know.

thanks.

This is the incremental debdiff based on #2 for Cosmic.


** Patch added: "alsa-lib_1.1.6-1ubuntu1.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806532/+attachment/5223433/+files/alsa-lib_1.1.6-1ubuntu1.2.debdiff

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

Title:
  The line-out on the Dell Dock station can't work

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in alsa-lib source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback
  devices, one is headphone, the other is line-out, but there is no UCM for
  these docks yet, so the pluseaudio only can handle the 1st playback device,
  need us to add the UCM for them, before adding UCM, we need to set the
  longname of the sound card in the linux kernel.

  [Fix]
  For Linux kernel: Cherry-picked 3 upstream patches, these patches add the 
longname of the sound card for the dock station.

  For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will
  add ucm configuration files for Dell WD15&19, and change the SPDIF conf
  in the USB-AUDIO.conf.

  [Test Case]
  Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from
  UI, and play sound via these devices

  [Regression Potential]
  Very low, these patches come from upstream, and the change is only specific
  to WD15 and WD19 dock station.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806532/+subscriptions

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

[Touch-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work

[Hui Wang]

This is the debdiff for bionic, it is not an incremental debdiff (since
the debdiff of #3 is not merged to bionic-proposed branch yet), this
debdiff will replace the one in the #3. It fixed the problem of
forgetting to add dir in the configure.ac.



** Patch added: "alsa-lib_1.1.3-5ubuntu0.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806532/+attachment/5223434/+files/alsa-lib_1.1.3-5ubuntu0.2.debdiff

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

Title:
  The line-out on the Dell Dock station can't work

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in alsa-lib source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback
  devices, one is headphone, the other is line-out, but there is no UCM for
  these docks yet, so the pluseaudio only can handle the 1st playback device,
  need us to add the UCM for them, before adding UCM, we need to set the
  longname of the sound card in the linux kernel.

  [Fix]
  For Linux kernel: Cherry-picked 3 upstream patches, these patches add the 
longname of the sound card for the dock station.

  For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will
  add ucm configuration files for Dell WD15&19, and change the SPDIF conf
  in the USB-AUDIO.conf.

  [Test Case]
  Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from
  UI, and play sound via these devices

  [Regression Potential]
  Very low, these patches come from upstream, and the change is only specific
  to WD15 and WD19 dock station.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806532/+subscriptions

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

[Touch-packages] [Bug 1731940] Re: [P7xxDM2(-G), Realtek ALC898, Headphone Jack, External] No sound at all

[Dennis Mungai Lin.Jr.]

A possible work-around: Update the jack's description to PulseAudio, as
shown:

Create the file `/usr/share/pulseaudio/alsa-mixer/paths/iec958-stereo-
output.conf` and populate it with:

```
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as
# published by the Free Software Foundation; either version 2.1 of the
# License, or (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .


[General]
description = Headphones + Digital Output (S/PDIF)

[Element IEC958]
switch = mute
```

Then set the model definition at `/etc/modprobe.d/sound.conf` with the
following entries:

`options snd-hda-intel model=no-primary-hp enable=1 index=0`

When done, issue a reboot.

For current HDA model lists, see http://git.alsa-project.org/?p=alsa-
kernel.git;a=blob;f=Documentation/sound/alsa/HD-Audio-
Models.txt;hb=HEAD.

Will test and report back.

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

Title:
  [P7xxDM2(-G), Realtek ALC898, Headphone Jack, External] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hello there,

  I have Ubuntu 16.04LTS installed on the Clevo P751DM2-G, also marketed
  as the Schenker XMG U507, the System76's Serval WS (2017 model), the
  Eurocom Sky X4E2, among others.

  The sound card is the Realtek ALC898 with the following output
  configuration:

  1. One SPDIF/headphone combo jack (to the right)
  2. One Line Out.
  3. One Line-In.
  4. One Mic-In.

  Background information:

  On Windows, one can use the Realtek HD Audio control panel pop-up menu
  on jack detection to set the output type when an audio device is
  plugged in to an appropriate jack, combined with Sound Blaster X-Fi
  MB5 software to enable post-processing effects such as Bass, noise
  cancellation, etc.

  What I have tried so far:

  1. Setting the model definition at /etc/modprobe.d/sound.conf with the
  following entries:

  options snd-hda-intel model=no-primary-hp enable=1 index=0

  Using such a line worked before on an MSI GS43VR 6RE Phantom Pro that
  also has the same (or a similar) ESS Sabre Audio DAC component.

  Expected behavior:

  When plugged into the microphone jack, the ESS Sabre DAC should be
  activated and sound should be routed to the headset.

  Observed anomaly:

  Sound comes out through the speakers instead.

  However, the line-out output works. In that case, when plugged into
  the line out, Audio works as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.14.0 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lin2199 F pulseaudio
   /dev/snd/controlC0:  lin2199 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Nov 13 17:34:53 2017
  InstallationDate: Installed on 2017-07-25 (111 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1812 F pulseaudio
lin2199 F pulseaudio
   /dev/snd/controlC0:  gdm1812 F pulseaudio
lin2199 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [P7xxDM2(-G), Realtek ALC898, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.06.04
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P7xxDM2(-G)
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.06.04:bd12/21/2016:svnNotebook:pnP7xxDM2(-G):pvrNotApplicable:rvnNotebook:rnP7xxDM2(-G):rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P7xxDM2(-G)
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

[Touch-packages] [Bug 1799693] Re: Stable libopus-1.3 released

[Bug Watch Updater]

** Changed in: opus (Debian)
   Status: New => Fix Released

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

Title:
  Stable libopus-1.3 released

Status in opus package in Ubuntu:
  Triaged
Status in opus package in Debian:
  Fix Released

Bug description:
  Cosmic is currently shipping libopus-1.3~beta+20180518-1 which is now 
outdated and technically marked as a beta. 
  http://opus-codec.org/release/stable/2018/10/18/libopus-1_3.html

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

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