[Touch-packages] [Bug 1763584] Re: ureadahead service fails with error Error while tracing: No such file or directory

[Max Gaukler]

The ureadahead package is no longer available on Ubuntu 20 or 22.
Just uninstall it:
sudo apt-get -qy remove ureadahead

On a standard release upgrade, it should be removed automatically;
however I have experienced one case where it was not removed for
whatever reason.

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

Title:
  ureadahead service fails with error Error while tracing: No such file
  or directory

Status in ureadahead package in Ubuntu:
  Confirmed

Bug description:
  I'm reporting this as duplicate of #1176536 to provide more info.

  dmig@dmig-Inspiron-5379:~$ systemctl status ureadahead.service 
  ● ureadahead.service - Read required files in advance
 Loaded: loaded (/lib/systemd/system/ureadahead.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Fri 2018-04-13 13:09:41 +07; 
10min ago
   Main PID: 379 (code=exited, status=5)

  Apr 13 13:09:41 dmig-Inspiron-5379 ureadahead[379]: ureadahead: Error while 
tracing: No such file or directory
  Apr 13 13:09:41 dmig-Inspiron-5379 ureadahead[379]: Counted 8 CPUs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ureadahead 0.100.0-20
  Uname: Linux 4.16.2-041602-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 13 13:13:26 2018
  InstallationDate: Installed on 2018-03-27 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  SourcePackage: ureadahead
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1973359] Re: on_ac_power says false, but real answer is true

[Max Gaukler]

*** This bug is a duplicate of bug 1980991 ***
https://bugs.launchpad.net/bugs/1980991

Closing as duplicate of
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1980991
which is slightly newer but contains further discussion and even a
suggested fix.

** This bug has been marked a duplicate of bug 1980991
   /usr/sbin/on_ac_power incorrectly reporting ac power status

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

Title:
  on_ac_power says false, but real answer is true

Status in powermgmt-base package in Ubuntu:
  Confirmed

Bug description:
  On a Dell 7000 Micro (Intel 12700T), plugged into mains power,
  on_ac_power reports false.

  As the micro computer is plugged into mains power, I had expected it
  instead to report true.

  /sys/class/power_supply$ ls
  ucsi-source-psy-USBC000:001

  /sys/class/power_supply/ucsi-source-psy-USBC000:001$ cat type
  USB

  /sys/class/power_supply/ucsi-source-psy-USBC000:001$ cat online
  0

  The initial logic in /usr/bin/on_ac_power goes:
  if [ -d /sys/class/power_supply/ ]; then
  for FN in /sys/class/power_supply/*; do
  if test -d "${FN}" && test -r "${FN}/type"; then
  type="$(cat "${FN}/type")"
  case "${type}" in
  Mains|USB*|BrickID|Wireless)
  if [ -r "${FN}/online" ]; then
  online="$(cat "${FN}/online")"
  [ "$online" = 1 ] && exit 0
  [ "$online" = 0 ] && OFF_LINE_P=yes
  fi;;
  esac
  fi
  done
  [ "${OFF_LINE_P}" = "yes" ] && exit 1
  fi

  Due the adapter being of type USB and the online status being 0,
  OFF_LINE_P is set to "yes" and the script exits with status code 1.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: powermgmt-base 1.36
  Uname: Linux 5.17.0-051700-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  Date: Fri May 13 11:50:59 2022
  Dependencies:
   
  InstallationDate: Installed on 2022-04-22 (21 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: powermgmt-base
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1976233] Re: "File has unexpected size" error on Focal ddebs repository

[Max]

** Tags added: focal

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

Title:
  "File has unexpected size" error on Focal ddebs repository

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Similar to https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865
  but affecting Ubuntu 20.04 "Focal"

  
  Steps to reproduce:

  1. Configure the debug repositories, like how it is explained in
  https://wiki.ubuntu.com/Debug%20Symbol%20Packages

  I ran these commands on a newly created Docker container (docker run
  --pull always --rm -ti ubuntu:20.04), but a typical bare metal
  installation should present the same issue:

  apt-get update ; apt-get install --yes gnupg

  apt-key adv \
  --keyserver keyserver.ubuntu.com \
  --recv-keys F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622

  source /etc/lsb-release

  tee /etc/apt/sources.list.d/ddebs.list >/dev/null 

[Touch-packages] [Bug 1976233] Re: "File has unexpected size" error on Focal ddebs repository

[Max]

Release file for focal-updates debug symbols is out of date again

curl -I 
http://ddebs.ubuntu.com/dists/focal-updates/main/binary-amd64/Packages.xz
date: Thu, 04 Aug 2022 07:46:41 GMT
last-modified: Tue, 02 Aug 2022 13:44:48 GMT

curl -I http://ddebs.ubuntu.com/dists/focal-updates/Release
last-modified: Wed, 27 Jul 2022 20:48:02 GMT

Please, update server content to consistent state.

I do not know if it is intentional, but TLS (SSL) certificate is not
suitable for the ddebs.ubuntu.com host:

curl -I https://ddebs.ubuntu.com/
curl: (60) SSL: no alternative certificate subject name matches target host 
name 'ddebs.ubuntu.com'

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

Title:
  "File has unexpected size" error on Focal ddebs repository

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Similar to https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865
  but affecting Ubuntu 20.04 "Focal"

  
  Steps to reproduce:

  1. Configure the debug repositories, like how it is explained in
  https://wiki.ubuntu.com/Debug%20Symbol%20Packages

  I ran these commands on a newly created Docker container (docker run
  --pull always --rm -ti ubuntu:20.04), but a typical bare metal
  installation should present the same issue:

  apt-get update ; apt-get install --yes gnupg

  apt-key adv \
  --keyserver keyserver.ubuntu.com \
  --recv-keys F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622

  source /etc/lsb-release

  tee /etc/apt/sources.list.d/ddebs.list >/dev/null 

[Touch-packages] [Bug 1966091] Re: Random noises with 5.13.0-37-generic and later but not with 5.13.0-35-generic

[Max]

I can confirm that. Fixed with 5.13.0-41-generic.

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

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

Title:
  Random noises with 5.13.0-37-generic and later but not with
  5.13.0-35-generic

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  After a recent update to linux-image-5.13.0-37-generic, I started
  experiencing random noises about every five seconds.  After rebooting
  into linux-image-5.13.0-35-generic, the noises were gone.

  Some details that I've noticed:

  1.  When launching pulseaudio manually, not as a daemon, the problem
  disappears.

  2.  If I set the log-level in /etc/pulse/daemon.conf to debug and
  reload it, the log has a lot of:

  Mar 23 17:22:44 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
  Mar 23 17:22:43 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
  Mar 23 17:22:39 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
  Mar 23 17:22:38 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!

  Which roughly correspond with the noises.

  3.  The usual "rm -f -r ~/.config/pulse && pulseaudio -k && sudo alsa
  force-reload" doesn't seem to help.  Only a kernel downgrade does.

  4.  This happens both in Firefox (where I first noticed it) as well as
  in Totem and in system sounds.

  5.  I tried to report the bug using "ubuntu-bug audio", but it showed
  me six inputs of which three looked the same, and for each of them it
  told me that it pulseaudio wasn't configured to use it.  I'm ready to
  collect logs and other info within the next days.


  Additional Info

$ lsb_release -a
  LSB Version:  
core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  Codename: focal

$ apt-cache policy linux-image-generic-hwe-20.04
  linux-image-generic-hwe-20.04:
Installed: 5.13.0.37.42~20.04.22
Candidate: 5.13.0.37.42~20.04.22
Version table:
   *** 5.13.0.37.42~20.04.22 500
  500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages
  500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages
  100 /var/lib/dpkg/status
   5.4.0.26.32 500
  500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages

$ apt-cache policy pulseaudio
  pulseaudio:
Installed: 1:13.99.1-1ubuntu3.13
Candidate: 1:13.99.1-1ubuntu3.13
Version table:
   *** 1:13.99.1-1ubuntu3.13 500
  500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.8 500
  500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages
   1:13.99.1-1ubuntu3 500
  500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages

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


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

[Touch-packages] [Bug 1967995] Re: [USB-Audio - Logitech G930 Headset, playback] Underruns, dropouts or crackling sound

[Max]

This got fixed for me with 5.13.0-41-generic.

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

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

Title:
  [USB-Audio - Logitech G930 Headset, playback] Underruns, dropouts or
  crackling sound

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  In the last 24 hours, my system has started having skipping/stuttering
  audio when gaming, or watching videos on youtube in chrome, and no
  audio at all when using VLC to play music files or watching youtube in
  Firefox.

  I believe I did a system update in the last week or so but I don't
  know if that is the cause.

  Description: Ubuntu 20.04.4 LTS
  Release: 20.04

  alsa-base:
Installed: 1.0.25+dfsg-0ubuntu5
Candidate: 1.0.25+dfsg-0ubuntu5
Version table:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 00:05:34 2022
  InstallationDate: Installed on 2020-08-31 (582 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Headset successful
  Symptom_Card: G930 - Logitech G930 Headset
  Symptom_PulseAudioLog:
   Apr 05 23:40:42 nzxt dbus-daemon[1169]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.40' (uid=125 pid=1765 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
   Apr 05 23:41:59 nzxt systemd[1655]: pulseaudio.service: Succeeded.
   Apr 05 23:42:09 nzxt systemd[1655]: pulseaudio.socket: Succeeded.
   Apr 05 23:49:33 nzxt sudo[8926]: root : TTY=unknown ; PWD=/home/raj ; 
USER=raj ; ENV=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus ; 
COMMAND=/usr/bin/xdg-open 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+filebug/b77c80a0-b575-11ec-b9ed-40a8f0305cb4?
   Apr 05 23:54:56 nzxt sudo[11680]: root : TTY=unknown ; PWD=/home/raj ; 
USER=raj ; ENV=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus ; 
COMMAND=/usr/bin/xdg-open 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+filebug/77aee818-b576-11ec-b78d-40a8f0308420?
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [USB-Audio - Logitech G930 Headset, playback] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 I AORUS PRO WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnB450IAORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450IAORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450 I AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Touch-packages] [Bug 1966091] Re: Random noises with 5.13.0-37-generic and later but not with 5.13.0-35-generic

[Max]

Also with new 5.13.0-40-generic the issue is still available for me.

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

Title:
  Random noises with 5.13.0-37-generic and later but not with
  5.13.0-35-generic

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After a recent update to linux-image-5.13.0-37-generic, I started
  experiencing random noises about every five seconds.  After rebooting
  into linux-image-5.13.0-35-generic, the noises were gone.

  Some details that I've noticed:

  1.  When launching pulseaudio manually, not as a daemon, the problem
  disappears.

  2.  If I set the log-level in /etc/pulse/daemon.conf to debug and
  reload it, the log has a lot of:

  Mar 23 17:22:44 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
  Mar 23 17:22:43 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
  Mar 23 17:22:39 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
  Mar 23 17:22:38 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!

  Which roughly correspond with the noises.

  3.  The usual "rm -f -r ~/.config/pulse && pulseaudio -k && sudo alsa
  force-reload" doesn't seem to help.  Only a kernel downgrade does.

  4.  This happens both in Firefox (where I first noticed it) as well as
  in Totem and in system sounds.

  5.  I tried to report the bug using "ubuntu-bug audio", but it showed
  me six inputs of which three looked the same, and for each of them it
  told me that it pulseaudio wasn't configured to use it.  I'm ready to
  collect logs and other info within the next days.


  Additional Info

$ lsb_release -a
  LSB Version:  
core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  Codename: focal

$ apt-cache policy linux-image-generic-hwe-20.04
  linux-image-generic-hwe-20.04:
Installed: 5.13.0.37.42~20.04.22
Candidate: 5.13.0.37.42~20.04.22
Version table:
   *** 5.13.0.37.42~20.04.22 500
  500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages
  500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages
  100 /var/lib/dpkg/status
   5.4.0.26.32 500
  500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages

$ apt-cache policy pulseaudio
  pulseaudio:
Installed: 1:13.99.1-1ubuntu3.13
Candidate: 1:13.99.1-1ubuntu3.13
Version table:
   *** 1:13.99.1-1ubuntu3.13 500
  500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.8 500
  500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages
   1:13.99.1-1ubuntu3 500
  500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages

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


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

[Touch-packages] [Bug 1967995] Re: [USB-Audio - Logitech G930 Headset, playback] Underruns, dropouts or crackling sound

[Max]

Similar issue for me with a Jabra Evolve 75 headset. As soon as
microphone is used, e.g. for a call, the driver seems to get into a
corrupted state where sound from speakers have crackling sound as long
as microphone is active. The issue doesn't appear when starting with
kernel 5.13.0-35. Looks like there have been some changes to usb-audio
drivers with kernel version 5.13.0-37.

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

Title:
  [USB-Audio - Logitech G930 Headset, playback] Underruns, dropouts or
  crackling sound

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  In the last 24 hours, my system has started having skipping/stuttering
  audio when gaming, or watching videos on youtube in chrome, and no
  audio at all when using VLC to play music files or watching youtube in
  Firefox.

  I believe I did a system update in the last week or so but I don't
  know if that is the cause.

  Description: Ubuntu 20.04.4 LTS
  Release: 20.04

  alsa-base:
Installed: 1.0.25+dfsg-0ubuntu5
Candidate: 1.0.25+dfsg-0ubuntu5
Version table:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 00:05:34 2022
  InstallationDate: Installed on 2020-08-31 (582 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Headset successful
  Symptom_Card: G930 - Logitech G930 Headset
  Symptom_PulseAudioLog:
   Apr 05 23:40:42 nzxt dbus-daemon[1169]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.40' (uid=125 pid=1765 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
   Apr 05 23:41:59 nzxt systemd[1655]: pulseaudio.service: Succeeded.
   Apr 05 23:42:09 nzxt systemd[1655]: pulseaudio.socket: Succeeded.
   Apr 05 23:49:33 nzxt sudo[8926]: root : TTY=unknown ; PWD=/home/raj ; 
USER=raj ; ENV=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus ; 
COMMAND=/usr/bin/xdg-open 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+filebug/b77c80a0-b575-11ec-b9ed-40a8f0305cb4?
   Apr 05 23:54:56 nzxt sudo[11680]: root : TTY=unknown ; PWD=/home/raj ; 
USER=raj ; ENV=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus ; 
COMMAND=/usr/bin/xdg-open 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+filebug/77aee818-b576-11ec-b78d-40a8f0308420?
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [USB-Audio - Logitech G930 Headset, playback] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 I AORUS PRO WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnB450IAORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450IAORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450 I AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Touch-packages] [Bug 1965008] Re: 'Software & Updates' crashes on tab 'Additional drivers'

[Max Overmeyer]

** Information type changed from Private to Public

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

Title:
  'Software & Updates' crashes on tab 'Additional drivers'

Status in software-properties package in Ubuntu:
  New

Bug description:
  Crash did not occur a couple of days ago.

  'sudo ubuntu-drivers list' has no problems listing the drivers.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: software-properties-gtk 0.99.19
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 21:04:29 2022
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2022-02-26 (16 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
  InterpreterPath: /usr/bin/python3.10
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab=4
  Python3Details: /usr/bin/python3.10, Python 3.10.2+, python3-minimal, 
3.10.1-0ubuntu2
  PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab=4']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with AttributeError in 
packages_for_modalias(): 'Cache' object has no attribute 'packages'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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


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

[Touch-packages] [Bug 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore

[Max Harmathy]

This issue is spamming the log with messages


Failed to get Yr.no forecast data: 404 Not Found

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

Title:
  (Update libgweather to 3.36.2) Weather forecast and info is not
  available anymore

Status in libgweather:
  Unknown
Status in gnome-weather package in Ubuntu:
  Fix Released
Status in libgweather package in Ubuntu:
  Fix Released
Status in gnome-weather source package in Focal:
  Confirmed
Status in libgweather source package in Focal:
  Confirmed
Status in gnome-weather package in Fedora:
  New

Bug description:
  [Impact]

  The weather forecast is not available since one week now. Also, the
  weather info is gone from gnome-shell.

  The weather service provider retired their old API.
  
https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/

  https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS

  ==
  Version 3.36.2
  ==

  This version switches the yr.no backend to use met.no instead. Please note
  that this backport is only meant as a compatibility layer. Where at all
  possible, the newer libgweather 40 should be used as applications cannot
  fully comply with the met.no ToS otherwise.

  
  [Test case]

  - gnome-weather shows the weather forecast
  - gnome-shell shows the weather forecast in the calendar menu

  
  [Regression potential]

  - Weather forecast is totally broken now and can't be more broken.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  7 09:54:52 2021
  InstallationDate: Installed on 2020-04-26 (314 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: libgweather
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1926305] Re: 20.04 Online Accounts - Google Shared Drives

[max]

Thank you for looking into it.

I appreciate it may not be an easy process.  However corporate
environments will not be upgraded until the next LTS.  This is quite an
important feature for end users and administrators alike.  As a
workaround we use rclone, but to have it all ready to go in the Desktop
environment would really make a big difference.

Just a thought for Canonical to consider.

But thanks again for your help.

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

Title:
  20.04 Online Accounts - Google Shared Drives

Status in gnome-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  Just tested out 21.04 and Google Shared Drives works just fine.

  Any chance the 20.04 LTS gnome-online-accounts could be updated to
  support it?

  If that is not possible, any way to build the package from source?

  Patch available here:
  
https://gitlab.gnome.org/GNOME/gvfs/-/commit/5fa777ddc6dafc71e72f499fd699f508a711924c#11a2f3edde24e314d0420b86f0caf06e5de195a1

  Problem is that building requires dependencies newer than package.
  Tried this with 3-36 as gnome on 20.04 is 3.36
  https://gitlab.gnome.org/GNOME/gvfs/-/tree/gnome-3-36

  Example error:
  meson.build:305:2: ERROR: Invalid version of dependency, need 
'polkit-gobject-1' ['>= 0.114'] found '0.105'

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

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

[Touch-packages] [Bug 1926305] Re: 20.04 Online Accounts - Google Shared Drives

[max]

** Tags removed: bot-comment

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

Title:
  20.04 Online Accounts - Google Shared Drives

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

Bug description:
  Just tested out 21.04 and Google Shared Drives works just fine.

  Any chance the 20.04 LTS gnome-online-accounts could be updated to
  support it?

  If that is not possible, any way to build the package from source?

  Patch available here:
  
https://gitlab.gnome.org/GNOME/gvfs/-/commit/5fa777ddc6dafc71e72f499fd699f508a711924c#11a2f3edde24e314d0420b86f0caf06e5de195a1

  Problem is that building requires dependencies newer than package.
  Tried this with 3-36 as gnome on 20.04 is 3.36
  https://gitlab.gnome.org/GNOME/gvfs/-/tree/gnome-3-36

  Example error:
  meson.build:305:2: ERROR: Invalid version of dependency, need 
'polkit-gobject-1' ['>= 0.114'] found '0.105'

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

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

[Touch-packages] [Bug 1926305] Re: 20.04 Online Accounts - Google Shared Drives

[max]

** Package changed: ubuntu => gnome-online-accounts (Ubuntu)

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

Title:
  20.04 Online Accounts - Google Shared Drives

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

Bug description:
  Just tested out 21.04 and Google Shared Drives works just fine.

  Any chance the 20.04 LTS gnome-online-accounts could be updated to
  support it?

  If that is not possible, any way to build the package from source?

  Patch available here:
  
https://gitlab.gnome.org/GNOME/gvfs/-/commit/5fa777ddc6dafc71e72f499fd699f508a711924c#11a2f3edde24e314d0420b86f0caf06e5de195a1

  Problem is that building requires dependencies newer than package.
  Tried this with 3-36 as gnome on 20.04 is 3.36
  https://gitlab.gnome.org/GNOME/gvfs/-/tree/gnome-3-36

  Example error:
  meson.build:305:2: ERROR: Invalid version of dependency, need 
'polkit-gobject-1' ['>= 0.114'] found '0.105'

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

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

[Touch-packages] [Bug 1896137] Re: syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7"

[Max]

I see those messages as well although in my case all the sleep.target
suspend.target hibernate.target hybrid-sleep.target targets are
unmasked. Note: I'm not trying to suspend or hybernate, the laptop is
running on external power. Is there a way to figure out what's causing
those messages?

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

Title:
  syslog flooded with "Lockdown: systemd-logind: hibernation is
  restricted; see man kernel_lockdown.7"

Status in systemd package in Ubuntu:
  New

Bug description:
  When I close the lid on my laptop, syslog goes crazy with the message

  systemd-logind: hibernation is restricted; see man kernel_lockdown.7

  repeated ad infinitum, using up all the CPU and GBs of disk space.  I
  am not even trying to hibernate; everything in /etc/systemd/login.conf
  is commented out.  So nothing much should happen when I close the lid,
  but systemd is trying to kill me with these messages.  I am running
  Ubuntu 20.04.

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

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

[Touch-packages] [Bug 1916469] [NEW] Ubuntu universe Wayland problem

[Max Vincent Goldgamer]

Public bug reported:

The Ubuntu universe has a big Wayland problem!

What does that mean?

So a lot of packages in the Universe repository are not compiled with
Wayland support which is really bad and would lead to bad performance
after 21.04 comes out.

Here are the following packages that I detected with wrong compilation:

telegram-desktop (Wayland support work with snap version)
qdirstat
vlc
kiwix
firefox (everything works fine with this env variable 
set:"MOZ_ENABLE_WAYLAND=1")

** Affects: ubuntu
 Importance: Undecided
 Status: New

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

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

** Affects: telegram-desktop (Ubuntu)
 Importance: Undecided
 Status: New

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

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


** Tags: hirsute wayland

** Tags added: wayland

** Tags added: hirsute

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

** Also affects: telegram-desktop (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

** Description changed:

  The Ubuntu universe has a big Wayland problem!
  
  What does that mean?
  
  So a lot of packages in the Universe repository are not compiled with
  Wayland support which is really bad and would lead to bad performance
  after 21.04 comes out.
  
  Here are the following packages that I detected with wrong compilation:
  
- telegram (Wayland support work with snap version)
+ telegram-desktop (Wayland support work with snap version)
  qdirstat
  vlc
  kiwix
  firefox (everything works fine with this env variable 
set:"MOZ_ENABLE_WAYLAND=1")

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

Title:
  Ubuntu universe Wayland problem

Status in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in qdirstat package in Ubuntu:
  New
Status in telegram-desktop package in Ubuntu:
  New
Status in vlc package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  The Ubuntu universe has a big Wayland problem!

  What does that mean?

  So a lot of packages in the Universe repository are not compiled with
  Wayland support which is really bad and would lead to bad performance
  after 21.04 comes out.

  Here are the following packages that I detected with wrong
  compilation:

  telegram-desktop (Wayland support work with snap version)
  qdirstat
  vlc
  kiwix
  firefox (everything works fine with this env variable 
set:"MOZ_ENABLE_WAYLAND=1")

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

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

[Touch-packages] [Bug 1896772] Re: systemd-resolved configures no Current Scopes on start

[Max]

I've hit exactly the same problem:

tree -p -u -d -L 3 /run/systemd/
...
├── [drwxr-xr-x systemd-resolve]  resolve
│   └── [drwxr-xr-x root]  netif
...

The issue happens with wi-fi interface. Could it be somehow related to
iwd?

I can add workaround to force proper permissions on the folder but I'd
rather digg into the root cause.

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  systemd-resolved configures no Current Scopes on start

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Running groovy on the desktop, with the systemd packages that migrated
  today(/overnight EDT).

  # Steps to reproduce:

  1) `systemctl restart systemd-resolved.service`

  (This is a minimal reproducer, but I first saw this after an apt
  upgrade of systemd.)

  # Expected behaviour:

  DNS continues to work, status looks like this:

  Link 2 (enp5s0)
Current Scopes: DNS
  DefaultRoute setting: yes
 LLMNR setting: yes
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no
Current DNS Server: 192.168.1.1
   DNS Servers: 192.168.1.1
DNS Domain: ~.
lan

  # Actual behaviour:

  DNS is unconfigured:

  Link 2 (enp5s0)
Current Scopes: none
  DefaultRoute setting: no
 LLMNR setting: yes
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no

  # Workaround

  Disconnecting and reconnecting my network connection restored DNS
  functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.5-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: i3
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Wed Sep 23 09:05:42 2020
  InstallationDate: Installed on 2019-05-07 (504 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7
  RebootRequiredPkgs: gnome-shell
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
   --
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: Upgraded to groovy on 2020-06-22 (92 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1901428] Re: PCI/internal sound card not detected

[Max]

After I added lines below to subl /etc/modprobe.d/alsa-base.conf

options snd-hda-intel model=clevo-p950
options snd-hda-intel model=generic
options snd-hda-intel dmic_detect=0
options snd-hda-intel model=laptop-dmic
options snd-hda-intel probe_mask=1

"Speakers - Built-in Audio" - appeared (Output Device)
"Microphone - Built-in Audio" - appeared (Input Device)

I can hear sounds now, but the microphone doesn't work.

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello there!
  Sounds and the microphone don't work. There is only Dummy Output in the 
output list. Input list is empty.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.9.1-050901-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  max1679 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Sun Oct 25 19:28:34 2020
  InstallationDate: Installed on 2020-10-22 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/10/2020
  dmi.bios.release: 15.24
  dmi.bios.vendor: AMI
  dmi.bios.version: F.24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8600
  dmi.board.vendor: HP
  dmi.board.version: 44.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 44.41
  dmi.modalias: 
dmi:bvnAMI:bvrF.24:bd03/10/2020:br15.24:efr44.41:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dh0xxx
  dmi.product.sku: 6ZL48EA#ACB
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-25T19:23:12.181325

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

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

[Touch-packages] [Bug 1901428] [NEW] PCI/internal sound card not detected

[Max]

Public bug reported:

Hello there!
Sounds and the microphone don't work. There is only Dummy Output in the output 
list. Input list is empty.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 5.9.1-050901-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  max1679 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Sun Oct 25 19:28:34 2020
InstallationDate: Installed on 2020-10-22 (2 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/10/2020
dmi.bios.release: 15.24
dmi.bios.vendor: AMI
dmi.bios.version: F.24
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8600
dmi.board.vendor: HP
dmi.board.version: 44.41
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 44.41
dmi.modalias: 
dmi:bvnAMI:bvrF.24:bd03/10/2020:br15.24:efr44.41:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP OMEN
dmi.product.name: OMEN by HP Laptop 15-dh0xxx
dmi.product.sku: 6ZL48EA#ACB
dmi.sys.vendor: HP
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-25T19:23:12.181325

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello there!
  Sounds and the microphone don't work. There is only Dummy Output in the 
output list. Input list is empty.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.9.1-050901-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  max1679 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Sun Oct 25 19:28:34 2020
  InstallationDate: Installed on 2020-10-22 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/10/2020
  dmi.bios.release: 15.24
  dmi.bios.vendor: AMI
  dmi.bios.version: F.24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8600
  dmi.board.vendor: HP
  dmi.board.version: 44.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 44.41
  dmi.modalias: 
dmi:bvnAMI:bvrF.24:bd03/10/2020:br15.24:efr44.41:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dh0xxx
  dmi.product.sku: 6ZL48EA#ACB
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-25T19:23:12.181325

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

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

[Touch-packages] [Bug 1857335] Re: System volume slider only works between ~90% and 100% with a USB 2.0 speaker

[Max Waterman]

I can't change the status to confirmed. What's the point in instructions
that people are prevented from following? Very frustrating.

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

Title:
  System volume slider only works between ~90% and 100% with a USB 2.0
  speaker

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  This is only with my USB 2.0 speaker[1] - with other devices, it works
  fine and the slider's 0% corresponds to silent and 100% full. With my
  USB 2.0 speaker, with the 'output' set to 'Analogue Output - USB2.0
  Device', it only has an effect between about 90% and 100%.

  I took a video of the problem and uploaded it here:

  http://davidmaxwaterman.fastmail.co.uk/xfer/ubuntu_volume_problem.mp4

  [1]
  
https://www.amazon.co.uk/gp/product/B07W1KN1XD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 23 10:00:17 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-07-19 (156 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2019-10-28 (56 days ago)

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

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

[Touch-packages] [Bug 1857335] Re: System volume slider only works between ~90% and 100% with a USB 2.0 speaker

[Max Waterman]

Still a problem: Ubuntu 20.04.1 LTS

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

Title:
  System volume slider only works between ~90% and 100% with a USB 2.0
  speaker

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  This is only with my USB 2.0 speaker[1] - with other devices, it works
  fine and the slider's 0% corresponds to silent and 100% full. With my
  USB 2.0 speaker, with the 'output' set to 'Analogue Output - USB2.0
  Device', it only has an effect between about 90% and 100%.

  I took a video of the problem and uploaded it here:

  http://davidmaxwaterman.fastmail.co.uk/xfer/ubuntu_volume_problem.mp4

  [1]
  
https://www.amazon.co.uk/gp/product/B07W1KN1XD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 23 10:00:17 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-07-19 (156 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2019-10-28 (56 days ago)

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

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

[Touch-packages] [Bug 264313] Re: ls --color hangs for directories linked from network

[Max Schillinger]

The workaround mentioned works for me. For fish users: Put

eval (dircolors -c | sed 's/or=[^:]*://')

in your `~/.config/fish/config.fish`.

And you have to modify the builtin `ls` function:

cp /usr/share/fish/functions/ls.fish ~/.config/fish/functions/

Then open `~/.config/fish/functions/ls.fish` and comment out this line:

set -a param --indicator-style=classify

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

Title:
  ls --color hangs for directories linked from network

Status in coreutils package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: coreutils

  ls --color hangs for directories linked from network resources if those 
resources are not available
  I guess it hangs in trying to validate the link ( have not tried to wait and 
see if it times out or not )

  easily reproducible.

  annoying since --color is default

  Running Ubuntu 8.0.4
  2.6.24-21-generic #1 SMP Mon Aug 25 16:57:51 UTC 2008 x86_64 GNU/Linux
  ls (GNU coreutils) 6.10

  ISSUE:

  since ls --color will try to determine if a symlink is broken or not
  (so that it will be correctly coloured), it *will* timeout on vanished
  resources.

  WORKAROUND:

  Inhibit 'ls' from following symlinks (at least in the context of --color):
  eval `dircolors -b | sed s/or=[^:]*://`

  Add the above to your profile.

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

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

[Touch-packages] [Bug 264313] Re: ls --color hangs for directories linked from network

[Max Schillinger]

Same issue in Ubuntu 18.04.

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

Title:
  ls --color hangs for directories linked from network

Status in coreutils package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: coreutils

  ls --color hangs for directories linked from network resources if those 
resources are not available
  I guess it hangs in trying to validate the link ( have not tried to wait and 
see if it times out or not )

  easily reproducible.

  annoying since --color is default

  Running Ubuntu 8.0.4
  2.6.24-21-generic #1 SMP Mon Aug 25 16:57:51 UTC 2008 x86_64 GNU/Linux
  ls (GNU coreutils) 6.10

  ISSUE:

  since ls --color will try to determine if a symlink is broken or not
  (so that it will be correctly coloured), it *will* timeout on vanished
  resources.

  WORKAROUND:

  Inhibit 'ls' from following symlinks (at least in the context of --color):
  eval `dircolors -b | sed s/or=[^:]*://`

  Add the above to your profile.

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

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

[Touch-packages] [Bug 1883428] [NEW] Use sysusers.d format

[Max]

Public bug reported:

Similar to 
https://fedoraproject.org/wiki/Changes/Adopting_sysusers.d_format Ubuntu should 
adopt modern sysusers.d format so the users added and removed by various 
packages could be properly cleared without polluting end-user system once the 
corresponding package is removed. This would also simplify the packages which 
needs to install system users.

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

Title:
  Use sysusers.d format

Status in systemd package in Ubuntu:
  New

Bug description:
  Similar to 
  https://fedoraproject.org/wiki/Changes/Adopting_sysusers.d_format Ubuntu 
should adopt modern sysusers.d format so the users added and removed by various 
packages could be properly cleared without polluting end-user system once the 
corresponding package is removed. This would also simplify the packages which 
needs to install system users.

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

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

[Touch-packages] [Bug 1883429] [NEW] Use sysusers.d format

[Max]

Public bug reported:

Similar to 
https://fedoraproject.org/wiki/Changes/Adopting_sysusers.d_format Ubuntu should 
adopt modern sysusers.d format so the users added and removed by various 
packages could be properly cleared without polluting end-user system once the 
corresponding package is removed. This would also simplify the packages which 
needs to install system users.

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

Title:
  Use sysusers.d format

Status in systemd package in Ubuntu:
  New

Bug description:
  Similar to 
  https://fedoraproject.org/wiki/Changes/Adopting_sysusers.d_format Ubuntu 
should adopt modern sysusers.d format so the users added and removed by various 
packages could be properly cleared without polluting end-user system once the 
corresponding package is removed. This would also simplify the packages which 
needs to install system users.

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

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

[Touch-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

[Max Waterman]

I have a similar problem on my Dell XPS 13 - if I boot the laptop with the 
headphones (3.5mm) plugged in, then it essentially disabled the 3.5mm headphone 
jack - nothing I've tried re-enabled it again (eg unplugging/replugging the 
headphone, all the settings, etc). Only a reboot without the headphones plugged 
in and plugging them in after logging in, fixes the problem.
I don't have this problem on my Lenovo T480s.
Perhaps this is a different problem?

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

Title:
  External audio device shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker, or none at
  all.

Status in gnome-control-center:
  Unknown
Status in PulseAudio:
  New
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  In Progress
Status in gnome-control-center source package in Focal:
  Invalid
Status in pulseaudio source package in Focal:
  In Progress

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

  1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
  2. Make sure it's the one selected as "Output device"
  3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  5. Try to switch back to the BT device and click Test
  -> same result as in step 3

  Tested with 2 different BT devices (one headset and one speaker) as
  well as a USB audio interface (Zoom H2N microphone).

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1832106] [NEW] Some packages could not be installed

[Max Emerling]

Public bug reported:

sudo apt-get install xserver-xorg-video-intel

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-21-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun  8 12:10:54 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06dc]
InstallationDate: Installed on 2019-06-06 (1 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
 Bus 001 Device 002: ID 0bda:5686 Realtek Semiconductor Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude E7470
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=4c3f6446-77d8-4152-8446-dbda7f591ea6 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/20/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.21.6
dmi.board.name: 0T6HHJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.21.6:bd05/20/2019:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude E7470
dmi.product.sku: 06DC
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Some packages could not be installed

Status in xorg package in Ubuntu:
  New

Bug description:
  sudo apt-get install xserver-xorg-video-intel

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  8 12:10:54 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06dc]
  InstallationDate: Installed on 2019-06-06 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
   Bus 001 Device 002: ID 0bda:5686 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E7470
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=4c3f6446-77d8-4152-8446-dbda7f591ea6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.21.6
  dmi.board.name: 0T6HHJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.21.6:bd05/20/2019:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude E7470
  dmi.product.sku: 06DC
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2

[Touch-packages] [Bug 1547024] Re: [N501VW, Realtek ALC668, Black Headphone Out, Right] Static Noise Problem

[Max Samukha]

Same problem on ux501vw, Ubuntu 18.10

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

Title:
  [N501VW, Realtek ALC668, Black Headphone Out, Right] Static Noise
  Problem

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure what's happening, my sound works great, there's just a
  static noise in the background that can get very annoying.

  Let me know if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.5.0-040500rc4-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zkanda 1519 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Feb 18 21:34:15 2016
  InstallationDate: Installed on 2016-02-16 (2 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160216)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [N501VW, Realtek ALC668, Black Headphone Out, Right] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.204:bd11/12/2015:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  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/1547024/+subscriptions

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

[Touch-packages] [Bug 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic

[Max Ehrlich]

*** This bug is a duplicate of bug 1576559 ***
https://bugs.launchpad.net/bugs/1576559

Also having this issue, the "headset" profile is not missing

Name: OrigAudio_HP
Alias: OrigAudio_HP
Class: 0x00260404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
RSSI: -60

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

Title:
  Bluetooth headset HSP/HFP mode not working in Bionic

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  There is a previous bug with almost the same title, but for Xenial
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I
  have had this issue in Artful, and when commented on the old bug, I
  was asked to raise a new one instead. I waited to see if Bionic fixed
  it for me, but it does not seem to work still. So!

  Steps to reproduce:
  1. enable bluetooth on computer and switch on the headset.
  2. pair and connect the headset
  3. go to settings to switch headset to HSP/HFP mode to enable mic
  4. save and close window.

  Expected behaviour:
  1. mic should be enabled and headset should be usable to attend calls on 
laptop.

  Behaviour in error:
  1. Headset profile switches back to A2DP and mic is not enabled.

  I am using a generic bluetooth headset on a fresh updated Kubuntu
  18.04 bionic with plasma DE.

  Software versions:
  Kernel: 4.15.0-20-generic
  Bluez version: 5.48-0ubuntu3
  pulseaudio: 1:11.1-1ubuntu7
  pulseaudio-module-bluetooth: 1:11.1-1ubuntu7

  
  Additional information:
  Running "pacmd list-cards" says that HSF/HFP is 'not available' on the 
headset:

  Output from Headset section:
  profiles:
  a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, 
available: unknown)
  headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, 
available: no)
  off: Off (priority 0, available: yes)
  active profile: 

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

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

[Touch-packages] [Bug 1814025] [NEW] Screen flickering on many programm

[max]

Public bug reported:

While using VSCode, Firefox Developer Edition, Google Chrome. Watching
youtube videos or coding the screen flickering really bad

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: i3
Date: Thu Jan 31 10:55:30 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1c20]
InstallationDate: Installed on 2019-01-11 (19 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: ASUSTeK COMPUTER INC. UX430UAR
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=b2e09cf1-c874-41a4-86ee-c64c58e32f29 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
XorgConf:
 Section "Device"
 Identifier  "Card0"
 Driver  "intel"
 Option  "Backlight"  "intel_backlight"
 EndSection
dmi.bios.date: 10/06/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX430UAR.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX430UAR
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.:bvrUX430UAR.300:bd10/06/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX430UAR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901260730.8e9ad5~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0~git1901260730.8e9ad5~oibaf~b
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.1.99+git1901101932.b1c016~oibaf~b
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1901211932.33ee0c~oibaf~b
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1901240732.ca1391~oibaf~b

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


** Tags: amd64 apport-bug bionic third-party-packages 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/1814025

Title:
  Screen flickering on many programm

Status in xorg package in Ubuntu:
  New

Bug description:
  While using VSCode, Firefox Developer Edition, Google Chrome. Watching
  youtube videos or coding the screen flickering really bad

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: i3
  Date: Thu Jan 31 10:55:30 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1c20]
  InstallationDate: Installed on 2019-01-11 (19 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUSTeK COMPUTER INC. UX430UAR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=b2e09cf1-c874-41a4-86ee-c64c58e32f29 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
   Identifier  "Card0"
   Driver  "intel"
   Option  "Backlight"  "intel_backlight"
   EndSection
  dmi.bios.date: 10/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UAR.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UAR
  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.:bvrUX430UAR.300:bd10/06/

[Touch-packages] [Bug 1685796] Re: systemctl -H user@host hangs after execution

[Max]

This bug is affecting me in 2019, it looks like it was fixed in 2016:

https://github.com/systemd/systemd/issues/3543#ref-commit-6590ca9

Is there a chance of getting this fix in 16.04?
Is there anything I can do to help?

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

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

Title:
  systemctl -H user@host hangs after execution

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04.2 (x86_64)

  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g  1 Mar 2016

  If I execute:

  systemctl -H root@127.0.0.1 restart networking

  The command is executed correctly but it hangs forever. If I run it
  localy:

  systemctl restart networking

  It is also executed correctly, but it does not hang at the end if the
  command.

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

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

[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 1799232] Re: my displays jump to the right occasionally

[Max Waterman]

IINM, this is the thunderbolt-3 display adaptor I am using:

https://www.startech.com/uk/AV/thunderbolt-3-video-
adapters/thunderbolt-3-to-dual-hdmi~TB32HD24K60

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

Title:
  my displays jump to the right occasionally

Status in xorg package in Ubuntu:
  New

Bug description:
  I have two monitors connected to my Dell XPS 13 via the USB-C output.

  For the majority of the time, it works fine. Occasionally, one or both
  of the images on the displays jump to the right, so that the right few
  inches appear on the left.

  To rectify the problem, I run the 'displays' app, move one of the
  displays a little, click 'apply', and then, instead of 'keep
  settings', I 'revert' them to their original, and then everything is
  fine for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 15:17:27 2018
  DistUpgraded: 2018-05-23 09:09:55,083 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:075b]
  InstallationDate: Installed on 2017-10-11 (376 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=15ace73f-6b30--a755-85264a11ae1e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-23 (152 days ago)
  dmi.bios.date: 05/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.7.1
  dmi.board.name: 05JK94
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.7.1:bd05/21/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  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
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Oct 31 11:01:05 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193 
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1.3

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

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

[Touch-packages] [Bug 1799232] Re: my displays jump to the right occasionally

[Max Waterman]

It just occurred again. dmesg output hasn't changed from what is in
CurrentDmesg.txt. Attempting to find details, I found:

$ boltctl list
 ● StarTech.com TB32HD24K60
   ├─ type:  peripheral
   ├─ name:  TB32HD24K60
   ├─ vendor:StarTech.com
   ├─ uuid:  cf03-0080-7718-2378-36488f03111d
   ├─ status:authorized
   │  ├─ authflags:  boot
   │  ├─ authorized: Mon 22 Oct 2018 14:13:05 UTC
   │  └─ connected:  Mon 22 Oct 2018 14:13:05 UTC
   └─ stored:yes
  ├─ when:   Wed 23 May 2018 08:12:24 UTC
  ├─ policy: auto
  └─ key:no

$ boltctl info cf03-0080-7718-2378-36488f03111d
 ● StarTech.com TB32HD24K60
   ├─ type:  peripheral
   ├─ name:  TB32HD24K60
   ├─ vendor:StarTech.com
   ├─ uuid:  cf03-0080-7718-2378-36488f03111d
   ├─ dbus path: 
/org/freedesktop/bolt/devices/cf03_0080_7718_2378_36488f03111d
   ├─ status:authorized
   │  ├─ authflags:  boot
   │  ├─ parent: c503-00b2-9d18-222d-f4d412c1b818
   │  ├─ syspath:
/sys/devices/pci:00/:00:1c.0/:01:00.0/:02:00.0/:03:00.0/domain0/0-0/0-1
   │  ├─ authorized: Mon 22 Oct 2018 14:13:05 UTC
   │  └─ connected:  Mon 22 Oct 2018 14:13:05 UTC
   └─ stored:yes
  ├─ when:   Wed 23 May 2018 08:12:24 UTC
  ├─ policy: auto
  └─ key:no

I don't see much else of interest. Let me know what else is needed.

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

Title:
  my displays jump to the right occasionally

Status in xorg package in Ubuntu:
  New

Bug description:
  I have two monitors connected to my Dell XPS 13 via the USB-C output.

  For the majority of the time, it works fine. Occasionally, one or both
  of the images on the displays jump to the right, so that the right few
  inches appear on the left.

  To rectify the problem, I run the 'displays' app, move one of the
  displays a little, click 'apply', and then, instead of 'keep
  settings', I 'revert' them to their original, and then everything is
  fine for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 15:17:27 2018
  DistUpgraded: 2018-05-23 09:09:55,083 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:075b]
  InstallationDate: Installed on 2017-10-11 (376 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=15ace73f-6b30--a755-85264a11ae1e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-23 (152 days ago)
  dmi.bios.date: 05/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.7.1
  dmi.board.name: 05JK94
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.7.1:bd05/21/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  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
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Oct 31 11:01:05 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193 
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1.3

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

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

[Touch-packages] [Bug 1799232] [NEW] my displays jump to the right occasionally

[Max Waterman]

Public bug reported:

I have two monitors connected to my Dell XPS 13 via the USB-C output.

For the majority of the time, it works fine. Occasionally, one or both
of the images on the displays jump to the right, so that the right few
inches appear on the left.

To rectify the problem, I run the 'displays' app, move one of the
displays a little, click 'apply', and then, instead of 'keep settings',
I 'revert' them to their original, and then everything is fine for a
while.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 22 15:17:27 2018
DistUpgraded: 2018-05-23 09:09:55,083 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 620 [1028:075b]
InstallationDate: Installed on 2017-10-11 (376 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Dell Inc. XPS 13 9360
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=15ace73f-6b30--a755-85264a11ae1e ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-05-23 (152 days ago)
dmi.bios.date: 05/21/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.7.1
dmi.board.name: 05JK94
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.7.1:bd05/21/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
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
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Oct 31 11:01:05 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5193 
 vendor SHP
xserver.version: 2:1.19.3-1ubuntu1.3

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  my displays jump to the right occasionally

Status in xorg package in Ubuntu:
  New

Bug description:
  I have two monitors connected to my Dell XPS 13 via the USB-C output.

  For the majority of the time, it works fine. Occasionally, one or both
  of the images on the displays jump to the right, so that the right few
  inches appear on the left.

  To rectify the problem, I run the 'displays' app, move one of the
  displays a little, click 'apply', and then, instead of 'keep
  settings', I 'revert' them to their original, and then everything is
  fine for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 15:17:27 2018
  DistUpgraded: 2018-05-23 09:09:55,083 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:075b]
  InstallationDate: Installed on 2017-10-11 (376 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=15ace73f-6b30--a755-85264a11ae1e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-23 (152 days ago)
  dmi.bios.date: 05/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.7.1
  dmi.board.name: 05JK94
  dmi.board.vendor: D

[Touch-packages] [Bug 1761834] Re: Right-click doesn't work

[Jean-Max Reymond]

Same issue with a new Dell Inspiron 5000 and Ubuntu 18.04 Xorg

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

Title:
  Right-click doesn't work

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I decided to try out the beta for 18.04 from 17.10.  Upon upgrading, I
  discovered that right-clicking no longer works on my trackpad, and
  right-clicks are handled as left-clicks would be.  Two-finger right
  click does not work either.  If I plug in a mouse with a physical
  right button, right clicking does work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr  6 11:26:00 2018
  DistUpgraded: 2018-04-06 11:14:08,949 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.14.15-041415-generic, x86_64: installed
   bbswitch, 0.8, 4.15.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2017-05-04 (337 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic 
root=UUID=62d6bfc3-82e2-4ca2-9255-8dae5ad9b117 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-04-06 (0 days ago)
  dmi.bios.date: 08/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd08/21/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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/+source/xorg/+bug/1761834/+subscriptions

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

[Touch-packages] [Bug 1765911] Re: Major performance regression from Ubuntu 17.10 with i915

[Max Bowsher]

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

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

Title:
  Major performance regression from Ubuntu 17.10 with i915

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Desktop performance on my laptop (Intel HD 520, driver: i915) used to
  be generally good on previous Ubuntu releases but on 18.04, there is a
  VERY noticeable regression. Moving windows around in GNOME is choppy
  and tearing. It gets dramatic after the laptop resumes from suspend,
  GNOME drops to literally ~1-2 FPS. Logging out and restarting the
  session usually fixes the problem in that it restores the barely
  acceptable performance level prior to suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 21 16:04:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:8079]
   Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] 
(rev 81) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f]
  InstallationDate: Installed on 2018-04-03 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  MachineType: HP HP EliteBook 850 G3
  ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-15-lowlatency.efi.signed 
root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro 
rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash 
module.sig_enforce=1 intel_pstate=skylake_hwp vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.10
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.6F
  dmi.chassis.asset.tag: 5CG6351LQL
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 850 G3
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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/+source/linux/+bug/1765911/+subscriptions

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

[Touch-packages] [Bug 1765911] Re: Major performance regression from Ubuntu 17.10 with i915

[Max Bowsher]

Similar/same issue observed on HP Spectre 13 (2017 model) which has
exactly the same Intel HD 520 graphics. Bad enough that I had to
reinstall 17.10.

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

Title:
  Major performance regression from Ubuntu 17.10 with i915

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Desktop performance on my laptop (Intel HD 520, driver: i915) used to
  be generally good on previous Ubuntu releases but on 18.04, there is a
  VERY noticeable regression. Moving windows around in GNOME is choppy
  and tearing. It gets dramatic after the laptop resumes from suspend,
  GNOME drops to literally ~1-2 FPS. Logging out and restarting the
  session usually fixes the problem in that it restores the barely
  acceptable performance level prior to suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 21 16:04:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:8079]
   Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] 
(rev 81) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f]
  InstallationDate: Installed on 2018-04-03 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  MachineType: HP HP EliteBook 850 G3
  ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-15-lowlatency.efi.signed 
root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro 
rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash 
module.sig_enforce=1 intel_pstate=skylake_hwp vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.10
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.6F
  dmi.chassis.asset.tag: 5CG6351LQL
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 850 G3
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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/+source/xorg/+bug/1765911/+subscriptions

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

[Touch-packages] [Bug 1765199] [NEW] [ICH - Intel 82801AA-ICH, playback] Underruns, dropouts or crackling sound

[Max]

Public bug reported:

when listening to music occasional random static, happened on youtube,
doesent seem to be particular cause

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   saki   1313 F...m pulseaudio
 /dev/snd/controlC0:  saki   1313 F pulseaudio
 /dev/snd/timer:  saki   1313 f pulseaudio
CurrentDesktop: XFCE
Date: Wed Apr 18 15:46:12 2018
InstallationDate: Installed on 2018-04-18 (0 days ago)
InstallationMedia: Xubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH failed
Symptom_Card: Built-in Audio - Intel 82801AA-ICH
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [ICH - Intel 82801AA-ICH, playback] Underruns, dropouts or crackling 
sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  [ICH - Intel 82801AA-ICH, playback] Underruns, dropouts or crackling
  sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  when listening to music occasional random static, happened on youtube,
  doesent seem to be particular cause

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   saki   1313 F...m pulseaudio
   /dev/snd/controlC0:  saki   1313 F pulseaudio
   /dev/snd/timer:  saki   1313 f pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Apr 18 15:46:12 2018
  InstallationDate: Installed on 2018-04-18 (0 days ago)
  InstallationMedia: Xubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH failed
  Symptom_Card: Built-in Audio - Intel 82801AA-ICH
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [ICH - Intel 82801AA-ICH, playback] Underruns, dropouts or crackling 
sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Touch-packages] [Bug 1723809] Re: NetworkManager-wait-online.service slows down boot

[Max]

Karsten Tausche, I have a clean install and the service is blocking for
8 secs.

That's still pretty slow, considering my system didn't take too long too
boot up in other releases of Ubuntu (~15 secs before, it's now 25 secs).

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

Title:
  NetworkManager-wait-online.service slows down boot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to artful, boot is considerable slower. By using 
systemd-analyze blame I've managed to narrow it to 
NetworkManager-wait-online.service.
   30.591s NetworkManager-wait-online.service
   10.240s nmbd.service
9.273s postfix@-.service
9.110s apt-daily.service
6.485s dev-sdb1.device
5.488s ModemManager.service
5.318s udisks2.service
4.968s accounts-daemon.service
3.807s fwupd.service
3.049s grub-common.service
2.837s apport.service
2.764s NetworkManager.service
2.413s speech-dispatcher.service
2.362s snapd.service
2.160s networking.service
2.083s pppd-dns.service
2.078s lm-sensors.service
2.073s gpu-manager.service
2.066s alsa-restore.service
1.570s smbd.service
1.380s rsyslog.service
1.310s polkit.service
1.117s apparmor.service

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Mon Oct 16 00:18:09 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev enp2s0 proto static metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.3 metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   enp2s0 ethernet  connected 
/org/freedesktop/NetworkManager/Devices/4  Wired connection 1  
066da907-ea49-35a2-8b54-b829cc834081  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   enp0s18f2u2ethernet  disconnected  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   enp0s18f2u2i2  ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/3  --  --   
 -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1747270] [NEW] package libssl1.0.0:i386 1.0.2g-1ubuntu4.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29

[Max]

Public bug reported:

My Computer Just Started FREAKING OUT! Error messages were everywhere! I
closed firefox and it finally stopped. P.S. I have ubuntu 14.4

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.10
ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
Uname: Linux 4.2.0-42-generic i686
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: i386
Date: Sun Feb  4 10:22:32 2018
DuplicateSignature: package:libssl1.0.0:i386:1.0.2g-1ubuntu4.10:subprocess 
installed post-installation script returned error exit status 29
ErrorMessage: subprocess installed post-installation script returned error exit 
status 29
InstallationDate: Installed on 2018-02-03 (1 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: openssl
Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.10 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 29
UpgradeStatus: Upgraded to trusty on 2018-02-03 (1 days ago)

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


** Tags: apport-package i386 trusty

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.10 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 29

Status in openssl package in Ubuntu:
  New

Bug description:
  My Computer Just Started FREAKING OUT! Error messages were everywhere!
  I closed firefox and it finally stopped. P.S. I have ubuntu 14.4

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.10
  ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic i686
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: i386
  Date: Sun Feb  4 10:22:32 2018
  DuplicateSignature: package:libssl1.0.0:i386:1.0.2g-1ubuntu4.10:subprocess 
installed post-installation script returned error exit status 29
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 29
  InstallationDate: Installed on 2018-02-03 (1 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: openssl
  Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.10 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 29
  UpgradeStatus: Upgraded to trusty on 2018-02-03 (1 days ago)

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

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

[Touch-packages] [Bug 1746527] [NEW] Systemd User Service Cannot Start with ECryptFS Due to PAM Misconfiguration

[Max Ehrlich]

Public bug reported:

If a user encrypts their home directory using the standard Ubuntu
installer GUI, which uses ecryptfs, then the users home directory is
encrypted while systemd is trying to start their user services so they
cant be read. After consulting with the systemd developers, the problem
is remarkably simple to fix

Ubuntu releases /etc/pam.d/common-session with the follow entries:

session optionalpam_systemd.so
session optionalpam_ecryptfs.so unwrap

they need to be swapped to

session optionalpam_ecryptfs.so unwrap
session optionalpam_systemd.so

so that decryption happens before systemd user services are started.

Check the thread on the systemd developers mailing list at
https://lists.freedesktop.org/archives/systemd-
devel/2018-January/040301.html for further information

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12.1
Uname: Linux 4.14.4-acso x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 31 09:25:10 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-11-04 (87 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Dell Inc. XPS 15 9560
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.14.4-acso 
root=/dev/mapper/ubuntu--vg-root ro quiet splash intel_iommu=on pci=noaer 
pcie_acs_override=downstream vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/30/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.0
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug artful

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

Title:
  Systemd User Service Cannot Start with ECryptFS Due to PAM
  Misconfiguration

Status in systemd package in Ubuntu:
  New

Bug description:
  If a user encrypts their home directory using the standard Ubuntu
  installer GUI, which uses ecryptfs, then the users home directory is
  encrypted while systemd is trying to start their user services so they
  cant be read. After consulting with the systemd developers, the
  problem is remarkably simple to fix

  Ubuntu releases /etc/pam.d/common-session with the follow entries:

  session optionalpam_systemd.so
  session optionalpam_ecryptfs.so unwrap

  they need to be swapped to

  session optionalpam_ecryptfs.so unwrap
  session optionalpam_systemd.so

  so that decryption happens before systemd user services are started.

  Check the thread on the systemd developers mailing list at
  https://lists.freedesktop.org/archives/systemd-
  devel/2018-January/040301.html for further information

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  Uname: Linux 4.14.4-acso x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 31 09:25:10 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (87 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.14.4-acso 
root=/dev/mapper/ubuntu--vg-root ro quiet splash intel_iommu=on pci=noaer 
pcie_acs_override=downstream vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1570921] Re: suspend not working

[Jean-Max Reymond]

Now, It works for me with 17.10 (HP Pavilion dv6)

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

Title:
  suspend not working

Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  My computer cannot go to suspend state.  The monitor switch off but the 
cpu/cpu fan keeps running and the hard drive is active.
  It doesn't respond, I need to switch off manually to reboot the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pm-utils 1.4.1-16
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 15 18:42:49 2016
  InstallationDate: Installed on 2016-04-15 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160414)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=hu
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c

[Max]

Ubuntu:: 16.04.3
gnome-screensaver :: 3.6.1-7ubuntu4
libglib2.0-0:i386 :: 2.48.2-0ubuntu1

Another example:
org.gnome.ScreenSaver[1963]: (gnome-screensaver:2131): GLib-CRITICAL **: Source 
ID 4988 was not found when attempting to remove it

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

Title:
  GLib-CRITICAL **: Source ID was not found when attempting to remove it
  - warning when leaving Network menu of g-c-c

Status in AndroidSDK:
  New
Status in Banshee:
  New
Status in gnome-control-center:
  Incomplete
Status in GParted:
  Unknown
Status in notification-daemon:
  New
Status in anjuta package in Ubuntu:
  Confirmed
Status in consolekit package in Ubuntu:
  Confirmed
Status in f-spot package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-mplayer package in Ubuntu:
  Confirmed
Status in putty package in Ubuntu:
  Confirmed

Bug description:
  Steps to recreate:
  1. Open gnome-control-center in terminal.
  2. Go to Network.
  3. Go back to All preferences.
  4. Notice that in terminal there is a warning:

  $ gnome-control-center

  (gnome-control-center:13519): GLib-CRITICAL **: Source ID 166 was not
  found when attempting to remove it

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu49
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Dec 26 21:03:52 2013
  InstallationDate: Installed on 2013-10-15 (71 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131015)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to trusty on 2013-11-05 (51 days ago)

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

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

[Touch-packages] [Bug 1742536] [NEW] ubuntu-bug does not permit filing bug reports against Ubuntu-managed kernels

[Max Burke]

Public bug reported:

I am trying to report bugs with kernel 3.2.0-132, part of the ESM
updates for 12.04, but when I use ubuntu-bug I see the following error:

$ ubuntu-bug linux-image-3.2.0-132-virtual

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
tail: cannot open `/var/log/syslog' for 
reading: Permission denied
...

*** Problem in linux-image-3.2.0-132-virtual

The problem cannot be reported:

This is not an official Ubuntu package. Please remove any third party
package and try again.

Press any key to continue...

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

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

Title:
  ubuntu-bug does not permit filing bug reports against Ubuntu-managed
  kernels

Status in apport package in Ubuntu:
  New

Bug description:
  I am trying to report bugs with kernel 3.2.0-132, part of the ESM
  updates for 12.04, but when I use ubuntu-bug I see the following
  error:

  $ ubuntu-bug linux-image-3.2.0-132-virtual

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  tail: cannot open `/var/log/syslog' for 
reading: Permission denied
  ...

  *** Problem in linux-image-3.2.0-132-virtual

  The problem cannot be reported:

  This is not an official Ubuntu package. Please remove any third party
  package and try again.

  Press any key to continue...

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

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

[Touch-packages] [Bug 1719959] [NEW] eglibc 2.19 leaks memory on getaddrinfo

[Max Dymond]

Public bug reported:

eglibc 2.19-0ubuntu6.13 is leaking memory when getaddrinfo is called
with a bad address.

Ubuntu version: 14.04.5 LTS

We're using Travis CI to do our CI. https://travis-ci.org/curl/curl-
fuzzer/builds/279417251 exhibits a memory leak when attempting to do a
lookup on the fqdn "t.."

I've done a bit of investigation - the memory is allocated here:

Direct leak of 65536 byte(s) in 1 object(s) allocated from:
#0 0x4be69c in __interceptor_malloc 
/home/development/llvm/3.9.0/final/llvm.src/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:64:3
#1 0x7513bd05 in send_dg 
/build/eglibc-SvCtMH/eglibc-2.19/resolv/res_send.c:1369
#2 0x7513bd05 in __libc_res_nsend 
/build/eglibc-SvCtMH/eglibc-2.19/resolv/res_send.c:576


Backtrace at point of allocation is:

(gdb) bt
#0  __libc_res_nsend (statp=statp@entry=0x702ffdb8, 
buf=buf@entry=0x702fc360 "\t:\001", buflen=19, 
buf2=buf2@entry=0x702fc374 "\371%\001", buflen2=buflen2@entry=19,
ans=ans@entry=0x702fcf70 "\t:\201\203", anssiz=anssiz@entry=2048, 
ansp=ansp@entry=0x702fd7e0, ansp2=ansp2@entry=0x702fd7f0, 
nansp2=nansp2@entry=0x702fd7a0,
resplen2=resplen2@entry=0x702fd7b0, 
ansp2_malloced=ansp2_malloced@entry=0x702fd7c0) at res_send.c:580
#1  0x75138e2c in __GI___libc_res_nquery 
(statp=statp@entry=0x702ffdb8, name=0x702fcaf0 "t.", 
class=class@entry=1, type=type@entry=62321, answer=answer@entry=0x702fcf70 
"\t:\201\203",
anslen=anslen@entry=2048, answerp=answerp@entry=0x702fd7e0, 
answerp2=answerp2@entry=0x702fd7f0, 
nanswerp2=nanswerp2@entry=0x702fd7a0, 
resplen2=resplen2@entry=0x702fd7b0,
answerp2_malloced=answerp2_malloced@entry=0x702fd7c0) at res_query.c:227
#2  0x75139863 in __libc_res_nquerydomain (domain=0x0, 
answerp2_malloced=0x702fd7c0, resplen2=0x702fd7b0, 
nanswerp2=0x702fd7a0, answerp2=0x702fd7f0, answerp=0x702fd7e0, 
anslen=2048,
answer=0x702fcf70 "\t:\201\203", type=62321, class=1, 
name=0x60323f28 "t..", statp=0x702ffdb8) at res_query.c:591
#3  __GI___libc_res_nsearch (statp=0x702ffdb8, 
name=name@entry=0x60323f28 "t..", class=class@entry=1, 
type=type@entry=62321, answer=answer@entry=0x702fcf70 "\t:\201\203", 
anslen=anslen@entry=2048,
answerp=answerp@entry=0x702fd7e0, 
answerp2=answerp2@entry=0x702fd7f0, 
nanswerp2=nanswerp2@entry=0x702fd7a0, 
resplen2=resplen2@entry=0x702fd7b0,
answerp2_malloced=answerp2_malloced@entry=0x702fd7c0) at res_query.c:381
#4  0x7fffef6f0c73 in _nss_dns_gethostbyname4_r 
(name=name@entry=0x60323f28 "t..", pat=pat@entry=0x702fde00, 
buffer=buffer@entry=0x702fd890 "\177", buflen=buflen@entry=1064,
errnop=errnop@entry=0x702fddd0, herrnop=herrnop@entry=0x702fde30, 
ttlp=ttlp@entry=0x0) at nss_dns/dns-host.c:315
#5  0x7595a636 in gaih_inet (name=, 
name@entry=0x60323f28 "t..", service=, 
req=req@entry=0x60d0cfb8, pai=pai@entry=0x702fdf40, 
naddrs=naddrs@entry=0x702fdf30)
at ../sysdeps/posix/getaddrinfo.c:858
#6  0x7595d93d in __GI_getaddrinfo (name=0x60323f28 "t..", 
service=0x702fec60 "80", hints=0x60d0cfb8, pai=0x702fe9a0) at 
../sysdeps/posix/getaddrinfo.c:2414
#7  0x00449825 in __interceptor_getaddrinfo () at 
/home/development/llvm/3.9.0/final/llvm.src/projects/compiler-rt/lib/asan/../sanitizer_common/sanitizer_common_interceptors.inc:2169
#8  0x0051dbe5 in curl_dogetaddrinfo (hostname=0x60323f28 "t..", 
service=0x702fec60 "80", hints=0x60d0cfb8, result=0x702fe9a0, 
line=124, source=0x6c3f60 <.str> "curl_addrinfo.c")
at curl_addrinfo.c:575
#9  0x0051cf81 in Curl_getaddrinfo_ex (nodename=0x60323f28 "t..", 
servname=0x702fec60 "80", hints=0x60d0cfb8, result=0x60d0cfb0) at 
curl_addrinfo.c:124
#10 0x005275f7 in getaddrinfo_thread (arg=0x60d0cf90) at 
asyn-thread.c:279
#11 0x0062e71a in curl_thread_create_thunk (arg=0x60323e98) at 
curl_threads.c:57
#12 0x76897184 in start_thread (arg=0x702ff700) at 
pthread_create.c:312
#13 0x75987ffd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Let me know if any further diagnostics would be helpful. It's 100%
reproducible on Travis.

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

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

Title:
  eglibc 2.19 leaks memory on getaddrinfo

Status in eglibc package in Ubuntu:
  New

Bug description:
  eglibc 2.19-0ubuntu6.13 is leaking memory when getaddrinfo is called
  with a bad address.

  Ubuntu version: 14.04.5 LTS

  We're using Travis CI to do our CI. https://travis-ci.org/curl/curl-
  fuzzer/builds/279417251 exhibits a memory leak when attempting to do a
  lookup on the fqdn

[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

[max moro]

as I don't want to rebuild now again, did anyone try
eg.

chmod +x ~/myshutdown.sh
sudo ~/myshutdown.sh

# with

echo r > /proc/sysrq-trigger
echo e > /proc/sysrq-trigger
echo s > /proc/sysrq-trigger
echo i > /proc/sysrq-trigger

echo u > /proc/sysrq-trigger
echo o > /proc/sysrq-trigger

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

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm booting a fully patched 16.04 from an Intel Rapid Storage
  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).

  If the RAID volume is recovering or resyncing for whatever reason, then `sudo 
systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo 
systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to 
consistently get that). However, once the recovery/resync is complete and 
clean, the reboot and poweroff commands above hang forever after "Reached 
target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in 
the bug #1464917) does not help.
  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
But I've never seen it succeed once the resync is complete.[/EDIT]

  Then, if the server has been forcibly restarted with the power button,
  the Intel Matrix Storage Manager indicates a "Normal" status for the
  RAID1 volume, but Ubuntu then resyncs the volume anyway:

  [1.223649] md: bind
  [1.228426] md: bind
  [1.230030] md: bind
  [1.230738] md: bind
  [1.232985] usbcore: registered new interface driver usbhid
  [1.233494] usbhid: USB HID core driver
  [1.234022] md: raid1 personality registered for level 1
  [1.234876] md/raid1:md126: not clean -- starting background reconstruction
  [1.234956] input: CHESEN USB Keyboard as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
  [1.236797] md126: detected capacity change from 0 to 1000202043392
  [1.246271] md: md126 switched to read-write mode.
  [1.246834] md: resync of RAID array md126
  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
  [1.247503]  md126: p1 p2 p3 p4
  [1.248269] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
  [1.248774] md: using 128k window, over a total of 976759940k.

  Note that the pain of "resync upon every (re)boot" cannot even be a
  bit relieved thanks to bitmaps because mdadm does not support them for
  IMSM containers:

  $ sudo mdadm --grow --bitmap=internal /dev/md126
  mdadm: Cannot add bitmaps to sub-arrays yet

  I also get this in syslog during boot when the individual drives are
  detected, but this seems to be harmless:

  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental 
/dev/sdb --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental 
/dev/sda --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  During a resync, `sudo sh -c 'echo idle >
  /sys/block/md126/md/sync_action'` actually stops it as expected, but
  it restarts immediately though nothing seems to have triggered it:

  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
md126.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for resync.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
total of 976759940k.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 
from checkpoint.
  May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device 
/dev/md/Volume0

  I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 
> /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has 
deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is 
unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without 
any keyboard.
  [EDIT]But I can still switch back to tty1.[/EDIT]

  I have also tried with much lower values for vm.dirty_background_ratio
  and vm.dirty_ratio, but to no

[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

[max moro]

a BIOS reconfig. from "RAID" to "AHCI" did not change anything.
m.

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

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm booting a fully patched 16.04 from an Intel Rapid Storage
  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).

  If the RAID volume is recovering or resyncing for whatever reason, then `sudo 
systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo 
systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to 
consistently get that). However, once the recovery/resync is complete and 
clean, the reboot and poweroff commands above hang forever after "Reached 
target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in 
the bug #1464917) does not help.
  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
But I've never seen it succeed once the resync is complete.[/EDIT]

  Then, if the server has been forcibly restarted with the power button,
  the Intel Matrix Storage Manager indicates a "Normal" status for the
  RAID1 volume, but Ubuntu then resyncs the volume anyway:

  [1.223649] md: bind
  [1.228426] md: bind
  [1.230030] md: bind
  [1.230738] md: bind
  [1.232985] usbcore: registered new interface driver usbhid
  [1.233494] usbhid: USB HID core driver
  [1.234022] md: raid1 personality registered for level 1
  [1.234876] md/raid1:md126: not clean -- starting background reconstruction
  [1.234956] input: CHESEN USB Keyboard as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
  [1.236797] md126: detected capacity change from 0 to 1000202043392
  [1.246271] md: md126 switched to read-write mode.
  [1.246834] md: resync of RAID array md126
  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
  [1.247503]  md126: p1 p2 p3 p4
  [1.248269] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
  [1.248774] md: using 128k window, over a total of 976759940k.

  Note that the pain of "resync upon every (re)boot" cannot even be a
  bit relieved thanks to bitmaps because mdadm does not support them for
  IMSM containers:

  $ sudo mdadm --grow --bitmap=internal /dev/md126
  mdadm: Cannot add bitmaps to sub-arrays yet

  I also get this in syslog during boot when the individual drives are
  detected, but this seems to be harmless:

  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental 
/dev/sdb --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental 
/dev/sda --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  During a resync, `sudo sh -c 'echo idle >
  /sys/block/md126/md/sync_action'` actually stops it as expected, but
  it restarts immediately though nothing seems to have triggered it:

  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
md126.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for resync.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
total of 976759940k.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 
from checkpoint.
  May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device 
/dev/md/Volume0

  I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 
> /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has 
deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is 
unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without 
any keyboard.
  [EDIT]But I can still switch back to tty1.[/EDIT]

  I have also tried with much lower values for vm.dirty_background_ratio
  and vm.dirty_ratio, but to no avail.

  Linux 4.6.0-040600-generic_4.6.0-040600.201605151930_amd64 from
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ did not
  help either.

  More information below:

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

  $ u

[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

[max moro]

Shutting down with a "R E S U I O" Workaround
was ok. The Raid was not rebuilt.
m.

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

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm booting a fully patched 16.04 from an Intel Rapid Storage
  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).

  If the RAID volume is recovering or resyncing for whatever reason, then `sudo 
systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo 
systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to 
consistently get that). However, once the recovery/resync is complete and 
clean, the reboot and poweroff commands above hang forever after "Reached 
target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in 
the bug #1464917) does not help.
  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
But I've never seen it succeed once the resync is complete.[/EDIT]

  Then, if the server has been forcibly restarted with the power button,
  the Intel Matrix Storage Manager indicates a "Normal" status for the
  RAID1 volume, but Ubuntu then resyncs the volume anyway:

  [1.223649] md: bind
  [1.228426] md: bind
  [1.230030] md: bind
  [1.230738] md: bind
  [1.232985] usbcore: registered new interface driver usbhid
  [1.233494] usbhid: USB HID core driver
  [1.234022] md: raid1 personality registered for level 1
  [1.234876] md/raid1:md126: not clean -- starting background reconstruction
  [1.234956] input: CHESEN USB Keyboard as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
  [1.236797] md126: detected capacity change from 0 to 1000202043392
  [1.246271] md: md126 switched to read-write mode.
  [1.246834] md: resync of RAID array md126
  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
  [1.247503]  md126: p1 p2 p3 p4
  [1.248269] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
  [1.248774] md: using 128k window, over a total of 976759940k.

  Note that the pain of "resync upon every (re)boot" cannot even be a
  bit relieved thanks to bitmaps because mdadm does not support them for
  IMSM containers:

  $ sudo mdadm --grow --bitmap=internal /dev/md126
  mdadm: Cannot add bitmaps to sub-arrays yet

  I also get this in syslog during boot when the individual drives are
  detected, but this seems to be harmless:

  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental 
/dev/sdb --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental 
/dev/sda --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  During a resync, `sudo sh -c 'echo idle >
  /sys/block/md126/md/sync_action'` actually stops it as expected, but
  it restarts immediately though nothing seems to have triggered it:

  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
md126.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for resync.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
total of 976759940k.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 
from checkpoint.
  May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device 
/dev/md/Volume0

  I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 
> /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has 
deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is 
unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without 
any keyboard.
  [EDIT]But I can still switch back to tty1.[/EDIT]

  I have also tried with much lower values for vm.dirty_background_ratio
  and vm.dirty_ratio, but to no avail.

  Linux 4.6.0-040600-generic_4.6.0-040600.201605151930_amd64 from
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ did not
  help either.

  More information below:

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  

[Touch-packages] [Bug 1714301] Re: systemd-networkd hangs my boot (wireless)

[Max Bowsher]

Still a problem in artful upgraded from zesty right now.

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

Title:
  systemd-networkd hangs my boot (wireless)

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Artful:
  Confirmed

Bug description:
  Since that systemd-networkd is enabled, my laptop doesn't boot (hangs)
  until I plug in an ethernet cable.

  Here is the journal from this boot, note the hang up until I connect my cable 
at 17:51:35:
  août 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo
  août 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo
  août 31 17:50:08 tidus systemd[1]: emergency-tmp.service: Cannot add 
dependency job, ignoring: Unit emergency-tmp.service is not loaded properly: 
Inva
  août 31 17:50:08 tidus ntpdate[3836]: Can't find host 0.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3836]: Can't find host 1.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3836]: Can't find host 2.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3836]: Can't find host 3.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3836]: Can't find host ntp.ubuntu.com: Name 
or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3836]: no servers can be used, exiting
  août 31 17:50:08 tidus systemd[1]: 
systemd-resolved-update-resolvconf.service: Start request repeated too quickly.
  août 31 17:50:08 tidus systemd[1]: Failed to start 
systemd-resolved-update-resolvconf.service.
  août 31 17:50:08 tidus systemd[1]: 
systemd-resolved-update-resolvconf.service: Failed with result 
'start-limit-hit'.
  août 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server.
  août 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting.
  août 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  août 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  août 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
  août 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  août 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  août 31 17:50:08 tidus nm-dispatcher[2511]: req:3 'up' [virbr0], 
"/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script 
'/etc/Ne
  août 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0]: start 
running ordered scripts...
  août 31 17:50:08 tidus NetworkManager[2340]:   [1504194608.6148] 
dispatcher: (6) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat
  août 31 17:50:08 tidus ntpdate[3908]: Can't find host 0.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3908]: Can't find host 1.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3908]: Can't find host 2.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3908]: Can't find host 3.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3908]: Can't find host ntp.ubuntu.com: Name 
or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3908]: no servers can be used, exiting
  août 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server.
  août 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting.
  août 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  août 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  août 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  août 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  août 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
  août 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0], 
"/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script 
'/etc/N
  août 31 17:50:08 tidus NetworkManager[2340]:   [1504194608.6612] 
dispatcher: (7) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat
  août 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  août 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  août 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  août 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  août 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
  août 31 17:50:08 tidus nm-dispatcher[25

[Touch-packages] [Bug 1716801] [NEW] Spurious creation of /stub-resolv.conf symlink

[Max Bowsher]

Public bug reported:

Code in /lib/systemd/system/systemd-resolved.service seeks to populate
/etc/resolv.conf if it is empty:

ExecStartPre=-+/bin/sh -c '[ ! -s /etc/resolv.conf ] && ln -snf
../run/systemd/resolve/stub-resolv.conf'


However the code is just wrong, and writes a symlink to /stub-resolv.conf 
rather than /etc/resolv.conf

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu9
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 13 00:55:32 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-08-16 (392 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: HP HP Spectre Notebook
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic 
root=UUID=4989886a-f95e-4802-ab51-dcbf53167aeb ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to artful on 2017-08-31 (12 days ago)
dmi.bios.date: 02/21/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.31
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81A0
dmi.board.vendor: HP
dmi.board.version: 48.54
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.31:bd02/21/2017:svnHP:pnHPSpectreNotebook:pvrType1ProductConfigId:rvnHP:rn81A0:rvr48.54:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
dmi.product.name: HP Spectre Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
modified.conffile..etc.systemd.resolved.conf: [modified]
mtime.conffile..etc.systemd.resolved.conf: 2017-09-02T14:44:21.354384

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


** Tags: amd64 apport-bug artful

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

Title:
  Spurious creation of /stub-resolv.conf symlink

Status in systemd package in Ubuntu:
  New

Bug description:
  Code in /lib/systemd/system/systemd-resolved.service seeks to populate
  /etc/resolv.conf if it is empty:

  ExecStartPre=-+/bin/sh -c '[ ! -s /etc/resolv.conf ] && ln -snf
  ../run/systemd/resolve/stub-resolv.conf'

  
  However the code is just wrong, and writes a symlink to /stub-resolv.conf 
rather than /etc/resolv.conf

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 13 00:55:32 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-16 (392 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Spectre Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic 
root=UUID=4989886a-f95e-4802-ab51-dcbf53167aeb ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-08-31 (12 days ago)
  dmi.bios.date: 02/21/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.31
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81A0
  dmi.board.vendor: HP
  dmi.board.version: 48.54
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.31:bd02/21/2017:svnHP:pnHPSpectreNotebook:pvrType1ProductConfigId:rvnHP:rn81A0:rvr48.54:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  modified.conffile..etc.systemd.resolved.conf: [modified]
  mtime.conffile..etc.systemd.resolved.conf: 2017-09-02T14:44:21.354384

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

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

[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

[max moro]

... interesting, but the pain is the new resync ... (writing 4(8) TB on each 
"hanging" reboot, ehm ...)

I used SysReq to sync before power-off

echo 1 > /proc/sys/kernel/sysrq

ALT + "DRUCK" ( or "Print Screen") + R E I S U O

as a workaround. as I have to wait for the sync, I can't report now.
of course that's no fun @ for remote machines.

ps. the servers were on centos before, I did not have any probs there ?!

m.

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

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm booting a fully patched 16.04 from an Intel Rapid Storage
  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).

  If the RAID volume is recovering or resyncing for whatever reason, then `sudo 
systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo 
systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to 
consistently get that). However, once the recovery/resync is complete and 
clean, the reboot and poweroff commands above hang forever after "Reached 
target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in 
the bug #1464917) does not help.
  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
But I've never seen it succeed once the resync is complete.[/EDIT]

  Then, if the server has been forcibly restarted with the power button,
  the Intel Matrix Storage Manager indicates a "Normal" status for the
  RAID1 volume, but Ubuntu then resyncs the volume anyway:

  [1.223649] md: bind
  [1.228426] md: bind
  [1.230030] md: bind
  [1.230738] md: bind
  [1.232985] usbcore: registered new interface driver usbhid
  [1.233494] usbhid: USB HID core driver
  [1.234022] md: raid1 personality registered for level 1
  [1.234876] md/raid1:md126: not clean -- starting background reconstruction
  [1.234956] input: CHESEN USB Keyboard as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
  [1.236797] md126: detected capacity change from 0 to 1000202043392
  [1.246271] md: md126 switched to read-write mode.
  [1.246834] md: resync of RAID array md126
  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
  [1.247503]  md126: p1 p2 p3 p4
  [1.248269] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
  [1.248774] md: using 128k window, over a total of 976759940k.

  Note that the pain of "resync upon every (re)boot" cannot even be a
  bit relieved thanks to bitmaps because mdadm does not support them for
  IMSM containers:

  $ sudo mdadm --grow --bitmap=internal /dev/md126
  mdadm: Cannot add bitmaps to sub-arrays yet

  I also get this in syslog during boot when the individual drives are
  detected, but this seems to be harmless:

  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental 
/dev/sdb --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental 
/dev/sda --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  During a resync, `sudo sh -c 'echo idle >
  /sys/block/md126/md/sync_action'` actually stops it as expected, but
  it restarts immediately though nothing seems to have triggered it:

  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
md126.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for resync.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
total of 976759940k.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 
from checkpoint.
  May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device 
/dev/md/Volume0

  I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 
> /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has 
deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is 
unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without 
any keyboard.
  [EDIT]But I can still switch back to tty1.[/EDIT]

  I have also tri

[Touch-packages] [Bug 1164016] Re: restore type-ahead find

[Max D]

This is up to date again in 17.10

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

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

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

[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

[max moro]

** Attachment added: "screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1587142/+attachment/4945763/+files/reached_target.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/1587142

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm booting a fully patched 16.04 from an Intel Rapid Storage
  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).

  If the RAID volume is recovering or resyncing for whatever reason, then `sudo 
systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo 
systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to 
consistently get that). However, once the recovery/resync is complete and 
clean, the reboot and poweroff commands above hang forever after "Reached 
target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in 
the bug #1464917) does not help.
  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
But I've never seen it succeed once the resync is complete.[/EDIT]

  Then, if the server has been forcibly restarted with the power button,
  the Intel Matrix Storage Manager indicates a "Normal" status for the
  RAID1 volume, but Ubuntu then resyncs the volume anyway:

  [1.223649] md: bind
  [1.228426] md: bind
  [1.230030] md: bind
  [1.230738] md: bind
  [1.232985] usbcore: registered new interface driver usbhid
  [1.233494] usbhid: USB HID core driver
  [1.234022] md: raid1 personality registered for level 1
  [1.234876] md/raid1:md126: not clean -- starting background reconstruction
  [1.234956] input: CHESEN USB Keyboard as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
  [1.236797] md126: detected capacity change from 0 to 1000202043392
  [1.246271] md: md126 switched to read-write mode.
  [1.246834] md: resync of RAID array md126
  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
  [1.247503]  md126: p1 p2 p3 p4
  [1.248269] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
  [1.248774] md: using 128k window, over a total of 976759940k.

  Note that the pain of "resync upon every (re)boot" cannot even be a
  bit relieved thanks to bitmaps because mdadm does not support them for
  IMSM containers:

  $ sudo mdadm --grow --bitmap=internal /dev/md126
  mdadm: Cannot add bitmaps to sub-arrays yet

  I also get this in syslog during boot when the individual drives are
  detected, but this seems to be harmless:

  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental 
/dev/sdb --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental 
/dev/sda --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  During a resync, `sudo sh -c 'echo idle >
  /sys/block/md126/md/sync_action'` actually stops it as expected, but
  it restarts immediately though nothing seems to have triggered it:

  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
md126.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for resync.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
total of 976759940k.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 
from checkpoint.
  May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device 
/dev/md/Volume0

  I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 
> /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has 
deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is 
unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without 
any keyboard.
  [EDIT]But I can still switch back to tty1.[/EDIT]

  I have also tried with much lower values for vm.dirty_background_ratio
  and vm.dirty_ratio, but to no avail.

  Linux 4.6.0-040600-generic_4.6.0-040600.201605151930_amd64 from
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ did not
  help either.

  More information below:

 

[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

[max moro]

confirmed on 
HP ProLiant ML10 Gen9, Xeon E3-1225 v5
Intel Raid Bios set to RAID1 (4 drives, 2xraid1)

Shutdowen/reboot hangs (kworkers) and Raid is rebuilt on every "reset"


Linux w11 4.4.0-93-generic #116-Ubuntu SMP Fri Aug 11 21:17:51 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
Description:Ubuntu 16.04.3 LTS
Release:16.04

Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] 
[raid10]
md124 : active raid1 sdc[1] sdd[0]
  2930264064 blocks super external:/md125/0 [2/2] [UU]
  [=>...]  resync = 27.1% (795895744/2930264196) 
finish=190.3min speed=186838K/sec

md125 : inactive sdd[1](S) sdc[0](S)
  4776 blocks super external:imsm

md126 : active raid1 sda[1] sdb[0]
  976759808 blocks super external:/md127/0 [2/2] [UU]
  [===>.]  resync = 75.0% (733104704/976759940) 
finish=28.2min speed=143955K/sec

md127 : inactive sda[1](S) sdb[0](S)
  5288 blocks super external:imsm

unused devices: 

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

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm booting a fully patched 16.04 from an Intel Rapid Storage
  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).

  If the RAID volume is recovering or resyncing for whatever reason, then `sudo 
systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo 
systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to 
consistently get that). However, once the recovery/resync is complete and 
clean, the reboot and poweroff commands above hang forever after "Reached 
target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in 
the bug #1464917) does not help.
  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
But I've never seen it succeed once the resync is complete.[/EDIT]

  Then, if the server has been forcibly restarted with the power button,
  the Intel Matrix Storage Manager indicates a "Normal" status for the
  RAID1 volume, but Ubuntu then resyncs the volume anyway:

  [1.223649] md: bind
  [1.228426] md: bind
  [1.230030] md: bind
  [1.230738] md: bind
  [1.232985] usbcore: registered new interface driver usbhid
  [1.233494] usbhid: USB HID core driver
  [1.234022] md: raid1 personality registered for level 1
  [1.234876] md/raid1:md126: not clean -- starting background reconstruction
  [1.234956] input: CHESEN USB Keyboard as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
  [1.236797] md126: detected capacity change from 0 to 1000202043392
  [1.246271] md: md126 switched to read-write mode.
  [1.246834] md: resync of RAID array md126
  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
  [1.247503]  md126: p1 p2 p3 p4
  [1.248269] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
  [1.248774] md: using 128k window, over a total of 976759940k.

  Note that the pain of "resync upon every (re)boot" cannot even be a
  bit relieved thanks to bitmaps because mdadm does not support them for
  IMSM containers:

  $ sudo mdadm --grow --bitmap=internal /dev/md126
  mdadm: Cannot add bitmaps to sub-arrays yet

  I also get this in syslog during boot when the individual drives are
  detected, but this seems to be harmless:

  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental 
/dev/sdb --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental 
/dev/sda --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  During a resync, `sudo sh -c 'echo idle >
  /sys/block/md126/md/sync_action'` actually stops it as expected, but
  it restarts immediately though nothing seems to have triggered it:

  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
md126.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for resync.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
total of 976759940k.
  May 30 18:17:02 wssrv1 kerne

[Touch-packages] [Bug 1577168] Re: Browser hangs Ubuntu 16.04

[Max Rumpf]

Still happens for me on Ubuntu 17.04 on my Dell XPS13:

max@xps13:~$ webbrowser-app

(webbrowser-app:4031): Gtk-WARNING **: Failed to parse 
/etc/gtk-3.0/settings.ini: Keine Berechtigung
libGL error: MESA-LOADER: failed to retrieve device information
libGL error: Version 4 or later of flush extension not found
libGL error: failed to load driver: i915
libGL error: MESA-LOADER: failed to retrieve device information
inotify_add_watch("/home/max/.config/ubuntu-ui-toolkit/theme.ini") failed: "No 
such file or directory"
UCUriHandler: Empty "APP_ID" environment variable, ignoring.
qml: webbrowser-app using oxide 1.21.5 (chromium 57.0.2987.110)
unity::action::ActionManager::ActionManager(QObject*):
Could not determine application identifier. HUD will not work properly.
Provide your application identifier in $APP_ID environment variable.
libGL error: MESA-LOADER: failed to retrieve device information
libGL error: Version 4 or later of flush extension not found
libGL error: failed to load driver: i915
libGL error: MESA-LOADER: failed to retrieve device information

(webbrowser-app:4031): dconf-CRITICAL **: unable to create file
'/run/user/1001/dconf/user': Keine Berechtigung.  dconf will not work
properly.

(webbrowser-app:4031): dconf-CRITICAL **: unable to create file
'/run/user/1001/dconf/user': Keine Berechtigung.  dconf will not work
properly.

(webbrowser-app:4031): dconf-CRITICAL **: unable to create file
'/run/user/1001/dconf/user': Keine Berechtigung.  dconf will not work
properly.

(webbrowser-app:4031): dconf-CRITICAL **: unable to create file
'/run/user/1001/dconf/user': Keine Berechtigung.  dconf will not work
properly.

(webbrowser-app:4031): dconf-CRITICAL **: unable to create file
'/run/user/1001/dconf/user': Keine Berechtigung.  dconf will not work
properly.

(webbrowser-app:4031): dconf-CRITICAL **: unable to create file
'/run/user/1001/dconf/user': Keine Berechtigung.  dconf will not work
properly.

(webbrowser-app:4031): dconf-CRITICAL **: unable to create file
'/run/user/1001/dconf/user': Keine Berechtigung.  dconf will not work
properly.

(webbrowser-app:4031): dconf-CRITICAL **: unable to create file
'/run/user/1001/dconf/user': Keine Berechtigung.  dconf will not work
properly.

(webbrowser-app:4031): dconf-CRITICAL **: unable to create file
'/run/user/1001/dconf/user': Keine Berechtigung.  dconf will not work
properly.

(webbrowser-app:4031): dconf-CRITICAL **: unable to create file
'/run/user/1001/dconf/user': Keine Berechtigung.  dconf will not work
properly.

(webbrowser-app:4031): dconf-CRITICAL **: unable to create file
'/run/user/1001/dconf/user': Keine Berechtigung.  dconf will not work
properly.

(webbrowser-app:4031): dconf-CRITICAL **: unable to create file
'/run/user/1001/dconf/user': Keine Berechtigung.  dconf will not work
properly.

(webbrowser-app:4031): dconf-CRITICAL **: unable to create file 
'/run/user/1001/dconf/user': Keine Berechtigung.  dconf will not work properly.
[0803/014332.722002:ERROR:child_thread_impl.cc(762)] Request for unknown 
Channel-associated interface: ui::mojom::GpuMain
error calling result "An AppArmor policy prevents this sender from sending this 
message to this recipient; type=\"method_call\", sender=\":1.129\" (uid=1001 
pid=4031 comm=\"webbrowser-app \") 
interface=\"com.canonical.libertine.Service.Operations\" member=\"list\" error 
name=\"(unset)\" requested_reply=\"0\" 
destination=\"com.canonical.libertine.Service\" (uid=1001 pid=2059 
comm=\"/usr/bin/python3 /usr/bin/libertined --cache-outpu\")"
error calling result "An AppArmor policy prevents this sender from sending this 
message to this recipient; type=\"method_call\", sender=\":1.129\" (uid=1001 
pid=4031 comm=\"webbrowser-app \") 
interface=\"com.canonical.libertine.Service.OperationsMonitor\" 
member=\"running\" error name=\"(unset)\" requested_reply=\"0\" 
destination=\"com.canonical.libertine.Service\" (uid=1001 pid=2059 
comm=\"/usr/bin/python3 /usr/bin/libertined --cache-outpu\")"
lastError - no arguments?
error calling result "An AppArmor policy prevents this sender from sending this 
message to this recipient; type=\"method_call\", sender=\":1.129\" (uid=1001 
pid=4031 comm=\"webbrowser-app \") 
interface=\"com.canonical.libertine.Service.OperationsMonitor\" 
member=\"last_error\" error name=\"(unset)\" requested_reply=\"0\" 
destination=\"com.canonical.libertine.Service\" (uid=1001 pid=2059 
comm=\"/usr/bin/python3 /usr/bin/libertined --cache-outpu\")"
lastError - no arguments?
error calling result "

[Touch-packages] [Bug 1472792] Re: evince does not open with broadway backend

[Max Chao]

It was fixed in evince 3.18.2. Tested with xenial.

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

Title:
  evince does not open with broadway backend

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  On Lubuntu 15.04, when trying to open Evince with GTK+ Broadway
  backend, Evince reports incomplete errors and then ends.

  In first terminal:

  $ broadwayd -a 127.0.0.1 -p 8889 :2
  Listening on /run/user/1000/broadway3.socket

  In second terminal:

  $ GDK_BACKEND=broadway BROADWAY_DISPLAY=:2 evince
  Unable to init server: Could not connect: Permission denied
  Cannot parse arguments: Cannot open display: 

  (There is nothing more in the output, program ends.)

  gtk3-demo or gitg have GUI in a browser as expected.

  Not sure if related or if it is perhaps expected, but I cannot see the
  socket file (with sudo or without):

  $ ls /run/user/1000/broadway3.socket
  ls: cannot access /run/user/1000/broadway3.socket: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: libgtk-3-0 3.14.13-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Jul  8 17:13:25 2015
  InstallationDate: Installed on 2015-02-09 (149 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to vivid on 2015-05-30 (38 days ago)

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

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

[Touch-packages] [Bug 1551351] Re: dhclient does not renew leases

[Jean-Max Reymond]

I have compiled dhclient v4.3.5 from the isc site, installed and it does not 
work. 
I have to create a new directory /var/db and dhclient 4.3.5 put 
dhclient6.leases in this directory
No trace in syslog, ifconfig eno1 seems OK but ping6 fails

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

Title:
  dhclient does not renew leases

Status in bind9 package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in bind9 source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Fix Released

Bug description:
  Release: Xenial

  I think this only recently started after some bind9 updates triggered a 
rebuild. When booting dhclient gets started and acquires an IP address, but it 
does seem to lock up somewhere as it does not renew the lease.
  In my environment I set the lease time to 5 minutes, so I notice such things 
rather soon. I looked on the dhcp server side but saw any further dhcp messages 
come in from the client side.

  Related bugs:
   * bug 1551415:  systemctl stop networking hang / timeout 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Mon Feb 29 12:32:52 2016
  DhclientLeases:

  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1541100] Re: package cups-daemon 2.1.2-2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Max Graves]

** Information type changed from Public to Public Security

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

Title:
  package cups-daemon 2.1.2-2 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  i install the unity mir.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.2-2
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sun Jan 31 21:03:30 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2015-11-24 (69 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151124)
  Lpstat: device for HP-Deskjet-3510-series: 
hp:/net/Deskjet_3510_series?zc=HP6C3BE5E55B12
  MachineType: ASUSTeK COMPUTER INC. S400CA
  Papersize: a4
  PpdFiles: HP-Deskjet-3510-series: HP Deskjet 3510 Series, hpcups 3.15.11
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-2-generic 
root=UUID=d9cc6d74-3876-4d0c-a45c-386bc46b03c4 ro locale=pt_BR quiet splash 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-2-generic 
root=UUID=d9cc6d74-3876-4d0c-a45c-386bc46b03c4 ro locale=pt_BR quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.1.10
  SourcePackage: cups
  Title: package cups-daemon 2.1.2-2 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: S400CA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: S400CA
  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.:bvrS400CA.206:bd11/28/2012:svnASUSTeKCOMPUTERINC.:pnS400CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS400CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: S400CA
  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/cups/+bug/1541100/+subscriptions

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

[Touch-packages] [Bug 861642] Re: upowerd uses 100% cpu till killed

[Max Barry]

Same as #8 with iPhone 6 and Ubuntu 16.10. CPU usage vanishes upon
tapping "Trust" on phone.

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

Title:
  upowerd uses 100% cpu till killed

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  top - 12:57:54 up  2:56,  3 users,  load average: 1.06, 1.12, 1.35
  Tasks: 219 total,   2 running, 216 sleeping,   0 stopped,   1 zombie
  Cpu0  : 70.2%us, 29.8%sy,  0.0%ni,  0.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu1  :  2.3%us,  1.3%sy,  0.0%ni, 96.4%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu2  :  1.0%us,  0.3%sy,  0.0%ni, 98.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu3  :  0.7%us,  1.6%sy,  0.0%ni, 97.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu4  :  0.0%us,  0.3%sy,  0.0%ni, 99.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu5  :  0.0%us,  0.3%sy,  0.0%ni, 98.3%id,  1.4%wa,  0.0%hi,  0.0%si,  0.0%st
  Mem:   5994176k total,  4198260k used,  1795916k free,63308k buffers
  Swap:  8193144k total,   355188k used,  7837956k free,   334316k cached

PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND  
  
   2268 root  20   0  148m 1572  680 R  100  0.0 111:08.37 upowerd

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: upower 0.9.9-4
  ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Wed Sep 28 12:53:23 2011
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  ProcEnviron:
   
  SourcePackage: upower
  UpgradeStatus: Upgraded to natty on 2011-04-06 (175 days ago)

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

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

[Touch-packages] [Bug 1640734] [NEW] package libperl5.22 5.22.2-3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other

[Max]

Public bug reported:

Wanted to install scanner

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libperl5.22 5.22.2-3
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Thu Nov 10 10:56:59 2016
DuplicateSignature:
 package:libperl5.22:5.22.2-3
 Unpacking libperl5.22:i386 (5.22.2-3) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-Il1Esk/23-libperl5.22_5.22.2-3_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', 
which is different from other instances of package libperl5.22:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
InstallationDate: Installed on 2016-07-29 (103 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: perl
Title: package libperl5.22 5.22.2-3 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is 
different from other instances of package libperl5.22:i386
UpgradeStatus: Upgraded to yakkety on 2016-10-15 (25 days ago)

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


** Tags: amd64 apport-package need-duplicate-check package-conflict yakkety

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

Title:
  package libperl5.22 5.22.2-3 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz',
  which is different from other instances of package libperl5.22:i386

Status in perl package in Ubuntu:
  New

Bug description:
  Wanted to install scanner

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libperl5.22 5.22.2-3
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Thu Nov 10 10:56:59 2016
  DuplicateSignature:
   package:libperl5.22:5.22.2-3
   Unpacking libperl5.22:i386 (5.22.2-3) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-Il1Esk/23-libperl5.22_5.22.2-3_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  InstallationDate: Installed on 2016-07-29 (103 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: perl
  Title: package libperl5.22 5.22.2-3 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is 
different from other instances of package libperl5.22:i386
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (25 days ago)

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

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

[Touch-packages] [Bug 1622089] Re: timezone parser in qt-5.5 breaks KDE clock

[Max]

With libqt5core5a 5.5.1+dfsg-16ubuntu7.2 I have no problem for the
Asia/Novosibirsk timezone.

Sorry for delay. I faced another bug that I did not noticed just after upgrade 
to 16.04.
Now I see that missing cities such as Europe/Astrakhan or Asia/Barnaul in 
digital clock
settings are unrelated to Qt version. The behavior is the same for 
5.5.1+dfsg-16ubuntu7.1 and
for 5.5.1+dfsg-16ubuntu7.2.

Thank you for backporting of the fix.

$ LANG=C apt-cache policy libqt5core5a 
libqt5core5a:
  Installed: 5.5.1+dfsg-16ubuntu7.2
  Candidate: 5.5.1+dfsg-16ubuntu7.2
  Version table:
 *** 5.5.1+dfsg-16ubuntu7.2 500
500 http://ru.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 5.5.1+dfsg-16ubuntu7.1 500
500 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
 5.5.1+dfsg-16ubuntu7 500
500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages


** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  timezone parser in qt-5.5 breaks KDE clock

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Xenial:
  Fix Committed

Bug description:
  [ Impact ]

  People in certain timezones have buggy time conversions in all Qt
  apps.

  [ Test Case ]

  See bug report.

  [ Regression Potential ]

  Should be low, in upstream LTS release and includes unit tests during
  build time.

  --- original bug report ---

  For a set of timezones in tzdata-2016*
  Qt parser produces wrong result in
  Qt versions earlier than 5.6.

  In kubuntu-16.04 xenial xerus the most annoying
  issue is broken digital clock plasmoid on the default KDE panel
  if system timezone is set to e.g. Asia/Novosibirsk.
  All Qt programs that attempts to convert time to non-default
  timezone are affected as well in xenial and earlier ubuntu released
  including ubuntu-14.04 LTS trusty.

  I consider the bug is nasty enough for updating Qt in LTS ubuntu
  releases.

  The upstream bug is https://bugreports.qt.io/browse/QTBUG-53071
  "QTimeZone mishandles tzdata 2016b and later in Russia, Kazakhstan".
  The direct link to the patch that fixes the problem is
  
https://codereview.qt-project.org/gitweb?p=qt/qtbase.git;a=patch;h=e9041c7fc1052167f1ec2df0ea9623059e55d00f

  I have rebuilt qtbase-opensource-src-5.5.1+dfsg (-16ubuntu7.1)
  from sources with the patch applied and the bug has gone away.

  A bit more details.

  I faced the problem with Kubuntu 16.04.1, x86_64.
  Asia/Novosibirsk has UTC+07:00 offset last a couple of months
  but KDE clock shows a time that has offset of 14 hours from the actual wall 
time,
  so it is rather unusable.
  Command line tool "date" reports correct local time.
  KDE digital clock works correctly in e.g. Asia/Krasnoyarsk timezone.
  It as a workaround if time transition history does not matter.

  Some other timezones affected by the bug (tzdata-2106f)
  file europe:
  Europe/Astrakhan
  Europe/Kirov
  Europe/Ulyanovsk
  Asia/Barnaul
  Asia/Novosibirsk
  Asia/Tomsk
  Asia/Novokuznetsk
  file asia:
  Asia/Almaty
  Asia/Qyzylorda
  Asia/Aqtobe
  Asia/Aqtau
  Asia/Oral

  A simple program to demonstrate the problem:

  #include 
  #include 
  #include 

  int main() {
  QTimeZone tz = QTimeZone(QTimeZone::systemTimeZoneId());
  QDateTime current = QDateTime::currentDateTime();
  qDebug() << "current offset" << tz.offsetFromUtc(current);
  return 0;
  }

  It reports 0 for incorrectly parsed timezones.

  The only thing that bothers me is that I had to disable tests
  when was rebuilding libqt5core5a_5.5.1+dfsg-16ubuntu7.1_amd64.deb
  using dpg-buildpackage. Otherwise I got error with cmake
  in tests/auto/cmake/. Cmake was unable to find qt libraries
  in the build tree.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1622089/+subscriptions

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

[Touch-packages] [Bug 1624480] [NEW] ir-keytable extra key presses repeating

[Max]

Public bug reported:

Greetings, I searched the forum and multiple others for a solution to
this, but I can't seem to find one that addresses this issue directly
for ir-keytable. Most seem to refer to lirc installations.

I do NOT have lirc installed, but it exists natively in Ubuntu 16.04
kernel. I’m using Ubuntu LTS 16.04. ir-keytable is configured using the
NEC driver for the MCE/Xbox remote I configured mappings for. What is
happening, is that when I press a key, it emulates the keyboard properly
without any issues and it works as designed. However, if I press the
same key more than once in succession within about 250 ms, it will
repeat the key about 20 times incredibly fast. I have dumps of the ir-
keytable -t as well as the status and configuration I’m using. I also
have confirmed that the remote sending the keypresses is NOT sending any
sustain or repeats (RTI environment). I have also confirmed lirc is NOT
installed by searching the config directories don't exist and irw
doesn't exist. I have also tried to change the default Repeat delay and
repeat period, but it takes and changes them, they just aren’t
persistent after a reboot. It doesn’t seem to help anyway, I’ve changed
them to 1000 and 50 respectively and tested but it doesn’t change the
behavior. This is happening in Plex Home Theater as well as the OS. Any
ideas? Thank you in advance.

Hardware: Intel NUC6i5SYH with latest BIOS.
IR onboard and configured in BIOS. Confirmed working reliably.

root@nuc:~# ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event7) with:
Driver ite-cir, table rc-rc6-mce
Supported protocols: unknown other lirc rc-5 jvc sony nec sanyo mce-kbd rc-6 
sharp xmp
Enabled protocols: lirc nec rc-6
Name: ITE8713 CIR transceiver
bus: 25, vendor/product: 1283:, version: 0x
Repeat delay = 500 ms, repeat period = 125 ms
root@nuc:~#

~~First three lines of /etc/rc_maps.cfg~~
#driver table file
* * xbox_remote
* rc-adstech-dvb-t-pci adstech_dvb_t_pci
* rc-alink-dtu-m alink_dtu_m

root@nuc:~# ir-keytable -c -p RC-6,NEC -w /etc/rc_keymaps/xbox_remote


root@nuc:~# ir-keytable -s rc0 -r
scancode 0x80d801 = KEY_1 (0x02)
scancode 0x80d802 = KEY_2 (0x03)
scancode 0x80d803 = KEY_3 (0x04)
scancode 0x80d804 = KEY_4 (0x05)
scancode 0x80d805 = KEY_5 (0x06)
scancode 0x80d806 = KEY_6 (0x07)
scancode 0x80d807 = KEY_7 (0x08)
scancode 0x80d808 = KEY_8 (0x09)
scancode 0x80d809 = KEY_9 (0x0a)
scancode 0x80d80e = KEY_0 (0x0b)
scancode 0x80d813 = KEY_Q (0x10)
scancode 0x80d814 = KEY_F (0x21)
scancode 0x80d815 = KEY_R (0x13)
scancode 0x80d819 = KEY_X (0x2d)
scancode 0x80d81e = KEY_UP (0x67)
scancode 0x80d81f = KEY_DOWN (0x6c)
scancode 0x80d820 = KEY_LEFT (0x69)
scancode 0x80d821 = KEY_RIGHT (0x6a)
scancode 0x80d822 = KEY_ENTER (0x1c)
scancode 0x80d823 = KEY_ESC (0x01)
scancode 0x80d865 = KEY_C (0x2e)
scancode 0x80d866 = KEY_P (0x19)
scancode 0x80d867 = KEY_H (0x23)
scancode 0x80d868 = KEY_O (0x18)
scancode 0x80d86e = KEY_I (0x17)
scancode 0x80d86f = KEY_M (0x32)
scancode 0x80d870 = KEY_SPACE (0x39)
Enabled protocols: lirc nec rc-6
root@nuc:~#


root@nuc:~# ir-keytable -t
Testing events. Please, press CTRL-C to abort.
1473634552.241175: event type EV_MSC(0x04): scancode = 0x80d821
1473634552.241175: event type EV_KEY(0x01) key_down: KEY_RIGHT(0x006a)
1473634552.241175: event type EV_SYN(0x00).
1473634552.251813: event type EV_MSC(0x04): scancode = 0x80d821
1473634552.251813: event type EV_SYN(0x00).
1473634552.376940: event type EV_MSC(0x04): scancode = 0x80d821
1473634552.376940: event type EV_SYN(0x00).
1473634552.484285: event type EV_MSC(0x04): scancode = 0x80d821
1473634552.484285: event type EV_SYN(0x00).
1473634552.495393: event type EV_MSC(0x04): scancode = 0x80d821
1473634552.495393: event type EV_SYN(0x00).
1473634552.695346: event type EV_MSC(0x04): scancode = 0x80d821
1473634552.695346: event type EV_SYN(0x00).
1473634552.738179: event type EV_KEY(0x01) key_down: KEY_RIGHT(0x006a)
1473634552.738179: event type EV_SYN(0x00).
1473634552.866084: event type EV_KEY(0x01) key_down: KEY_RIGHT(0x006a)
1473634552.866084: event type EV_SYN(0x00).
1473634552.946080: event type EV_KEY(0x01) key_up: KEY_RIGHT(0x006a)
1473634552.946080: event type EV_SYN(0x00).
1473634555.090156: event type EV_MSC(0x04): scancode = 0x80d821
1473634555.090156: event type EV_KEY(0x01) key_down: KEY_RIGHT(0x006a)
1473634555.090156: event type EV_SYN(0x00).
1473634555.100966: event type EV_MSC(0x04): scancode = 0x80d821
1473634555.100966: event type EV_SYN(0x00).
1473634555.301295: event type EV_MSC(0x04): scancode = 0x80d821
1473634555.301295: event type EV_SYN(0x00).
1473634555.550080: event type EV_KEY(0x01) key_up: KEY_RIGHT(0x006a)
1473634555.550080: event type EV_SYN(0x00).
1473634555.952914: event type EV_MSC(0x04): scancode = 0x80d821
1473634555.952914: event type EV_KEY(0x01) key_down: KEY_RIGHT(0x006a)
1473634555.952914: event type EV_SYN(0x00).
1473634555.963546: event type EV_MSC(0x04): scancode = 0x80d821
1473634555.963546: event type EV_SYN(0x00).
1473

[Touch-packages] [Bug 1623085] Re: source package build is failing

[Max]

Solution is to add the "--resolve-alternatives" flag to sbuild.

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

Title:
  source package build is failing

Status in mountall package in Ubuntu:
  Invalid

Bug description:
  Trying to build the source package using sbuild is failing with the
  following error.

  
+--+
  | Install mountall build dependencies (apt-based resolver)
 |
  
+--+

  Installing build dependencies
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   sbuild-build-depends-mountall-dummy : Depends: plymouth-dev (>= 0.8.5.1) but 
it is not installable
  E: Unable to correct problems, you have held broken packages.
  apt-get failed.
  Package installation failed

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

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

[Touch-packages] [Bug 1623085] [NEW] source package build is failing

[Max]

Public bug reported:

Trying to build the source package using sbuild is failing with the
following error.

+--+
| Install mountall build dependencies (apt-based resolver) |
+--+

Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 sbuild-build-depends-mountall-dummy : Depends: plymouth-dev (>= 0.8.5.1) but 
it is not installable
E: Unable to correct problems, you have held broken packages.
apt-get failed.
Package installation failed

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

** Attachment added: "buildlog"
   https://bugs.launchpad.net/bugs/1623085/+attachment/4740114/+files/buildlog

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

Title:
  source package build is failing

Status in mountall package in Ubuntu:
  New

Bug description:
  Trying to build the source package using sbuild is failing with the
  following error.

  
+--+
  | Install mountall build dependencies (apt-based resolver)
 |
  
+--+

  Installing build dependencies
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   sbuild-build-depends-mountall-dummy : Depends: plymouth-dev (>= 0.8.5.1) but 
it is not installable
  E: Unable to correct problems, you have held broken packages.
  apt-get failed.
  Package installation failed

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

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

[Touch-packages] [Bug 1623073] [NEW] source package build is failing

[Max]

Public bug reported:

Trying to build the source package using sbuild is failing with the
following error.

dh_clean
 debian/rules build
gtkdocize --docdir libkmod/docs
autoreconf --force --install --symlink
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: linking file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: linking file 'm4/libtool.m4'
libtoolize: linking file 'm4/ltoptions.m4'
libtoolize: linking file 'm4/ltsugar.m4'
libtoolize: linking file 'm4/ltversion.m4'
libtoolize: linking file 'm4/lt~obsolete.m4'
configure.ac:13: installing 'build-aux/compile'
configure.ac:19: installing 'build-aux/config.guess'
configure.ac:19: installing 'build-aux/config.sub'
configure.ac:17: installing 'build-aux/install-sh'
configure.ac:17: installing 'build-aux/missing'
Makefile.am: installing 'build-aux/depcomp'
Makefile.am:207: installing 'build-aux/py-compile'
parallel-tests: installing 'build-aux/test-driver'
libkmod/docs/gtk-doc.make:33: error: EXTRA_DIST must be set with '=' before 
using '+='
libkmod/docs/Makefile.am:29:   'libkmod/docs/gtk-doc.make' included from here
autoreconf: automake failed with exit status: 1
debian/rules:60: recipe for target 'configure' failed
make: *** [configure] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2

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

** Attachment added: "buildlog"
   https://bugs.launchpad.net/bugs/1623073/+attachment/4740110/+files/buildlog

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

Title:
  source package build is failing

Status in kmod package in Ubuntu:
  New

Bug description:
  Trying to build the source package using sbuild is failing with the
  following error.

  dh_clean
   debian/rules build
  gtkdocize --docdir libkmod/docs
  autoreconf --force --install --symlink
  libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
  libtoolize: linking file 'build-aux/ltmain.sh'
  libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
  libtoolize: linking file 'm4/libtool.m4'
  libtoolize: linking file 'm4/ltoptions.m4'
  libtoolize: linking file 'm4/ltsugar.m4'
  libtoolize: linking file 'm4/ltversion.m4'
  libtoolize: linking file 'm4/lt~obsolete.m4'
  configure.ac:13: installing 'build-aux/compile'
  configure.ac:19: installing 'build-aux/config.guess'
  configure.ac:19: installing 'build-aux/config.sub'
  configure.ac:17: installing 'build-aux/install-sh'
  configure.ac:17: installing 'build-aux/missing'
  Makefile.am: installing 'build-aux/depcomp'
  Makefile.am:207: installing 'build-aux/py-compile'
  parallel-tests: installing 'build-aux/test-driver'
  libkmod/docs/gtk-doc.make:33: error: EXTRA_DIST must be set with '=' before 
using '+='
  libkmod/docs/Makefile.am:29:   'libkmod/docs/gtk-doc.make' included from here
  autoreconf: automake failed with exit status: 1
  debian/rules:60: recipe for target 'configure' failed
  make: *** [configure] Error 1
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

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

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

[Touch-packages] [Bug 1622089] [NEW] timezone parser in qt-5.5 breaks KDE clock

[Max]

Public bug reported:

For a set of timezones in tzdata-2016*
Qt parser produces wrong result in
Qt versions earlier than 5.6.

In kubuntu-16.04 xenial xerus the most annoying
issue is broken digital clock plasmoid on the default KDE panel
if system timezone is set to e.g. Asia/Novosibirsk.
All Qt programs that attempts to convert time to non-default
timezone are affected as well in xenial and earlier ubuntu released
including ubuntu-14.04 LTS trusty.

I consider the bug is nasty enough for updating Qt in LTS ubuntu
releases.

The upstream bug is https://bugreports.qt.io/browse/QTBUG-53071
"QTimeZone mishandles tzdata 2016b and later in Russia, Kazakhstan".
The direct link to the patch that fixes the problem is
https://codereview.qt-project.org/gitweb?p=qt/qtbase.git;a=patch;h=e9041c7fc1052167f1ec2df0ea9623059e55d00f

I have rebuilt qtbase-opensource-src-5.5.1+dfsg (-16ubuntu7.1)
from sources with the patch applied and the bug has gone away.

A bit more details.

I faced the problem with Kubuntu 16.04.1, x86_64.
Asia/Novosibirsk has UTC+07:00 offset last a couple of months
but KDE clock shows a time that has offset of 14 hours from the actual wall 
time,
so it is rather unusable.
Command line tool "date" reports correct local time.
KDE digital clock works correctly in e.g. Asia/Krasnoyarsk timezone.
It as a workaround if time transition history does not matter.

Some other timezones affected by the bug (tzdata-2106f)
file europe:
Europe/Astrakhan
Europe/Kirov
Europe/Ulyanovsk
Asia/Barnaul
Asia/Novosibirsk
Asia/Tomsk
Asia/Novokuznetsk
file asia:
Asia/Almaty
Asia/Qyzylorda
Asia/Aqtobe
Asia/Aqtau
Asia/Oral

A simple program to demonstrate the problem:

#include 
#include 
#include 

int main() {
QTimeZone tz = QTimeZone(QTimeZone::systemTimeZoneId());
QDateTime current = QDateTime::currentDateTime();
qDebug() << "current offset" << tz.offsetFromUtc(current);
return 0;
}

It reports 0 for incorrectly parsed timezones.

The only thing that bothers me is that I had to disable tests
when was rebuilding libqt5core5a_5.5.1+dfsg-16ubuntu7.1_amd64.deb
using dpg-buildpackage. Otherwise I got error with cmake
in tests/auto/cmake/. Cmake was unable to find qt libraries
in the build tree.

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: patch xenial

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

Title:
  timezone parser in qt-5.5 breaks KDE clock

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

Bug description:
  For a set of timezones in tzdata-2016*
  Qt parser produces wrong result in
  Qt versions earlier than 5.6.

  In kubuntu-16.04 xenial xerus the most annoying
  issue is broken digital clock plasmoid on the default KDE panel
  if system timezone is set to e.g. Asia/Novosibirsk.
  All Qt programs that attempts to convert time to non-default
  timezone are affected as well in xenial and earlier ubuntu released
  including ubuntu-14.04 LTS trusty.

  I consider the bug is nasty enough for updating Qt in LTS ubuntu
  releases.

  The upstream bug is https://bugreports.qt.io/browse/QTBUG-53071
  "QTimeZone mishandles tzdata 2016b and later in Russia, Kazakhstan".
  The direct link to the patch that fixes the problem is
  
https://codereview.qt-project.org/gitweb?p=qt/qtbase.git;a=patch;h=e9041c7fc1052167f1ec2df0ea9623059e55d00f

  I have rebuilt qtbase-opensource-src-5.5.1+dfsg (-16ubuntu7.1)
  from sources with the patch applied and the bug has gone away.

  A bit more details.

  I faced the problem with Kubuntu 16.04.1, x86_64.
  Asia/Novosibirsk has UTC+07:00 offset last a couple of months
  but KDE clock shows a time that has offset of 14 hours from the actual wall 
time,
  so it is rather unusable.
  Command line tool "date" reports correct local time.
  KDE digital clock works correctly in e.g. Asia/Krasnoyarsk timezone.
  It as a workaround if time transition history does not matter.

  Some other timezones affected by the bug (tzdata-2106f)
  file europe:
  Europe/Astrakhan
  Europe/Kirov
  Europe/Ulyanovsk
  Asia/Barnaul
  Asia/Novosibirsk
  Asia/Tomsk
  Asia/Novokuznetsk
  file asia:
  Asia/Almaty
  Asia/Qyzylorda
  Asia/Aqtobe
  Asia/Aqtau
  Asia/Oral

  A simple program to demonstrate the problem:

  #include 
  #include 
  #include 

  int main() {
  QTimeZone tz = QTimeZone(QTimeZone::systemTimeZoneId());
  QDateTime current = QDateTime::currentDateTime();
  qDebug() << "current offset" << tz.offsetFromUtc(current);
  return 0;
  }

  It reports 0 for incorrectly parsed timezones.

  The only thing that bothers me is that I had to disable tests
  when was rebuilding libqt5core5a_5.5.1+dfsg-16ubuntu7.1_amd64.deb
  using dpg-buildpackage. Otherwise I got error with cmake
  in tests/auto/cmake/. Cmake was unable to find qt libraries
  

[Touch-packages] [Bug 1614576] Re: Upgrade from xenial to yakkety fails when install policykit-1

[Max Brustkern]

The end of /var/log/dist-upgrade/main.log is showing a unicode decode error:
2016-09-09 14:21:30,594 DEBUG linux-image-4.4.0-9136-generic (new-install) 
added with 45669149 to boot space
2016-09-09 14:21:31,638 DEBUG dir '/var/cache/apt/archives' needs '180762526' 
of '.FreeSpace 
object at 0x7f94752ca240>' (21087518720.00)
2016-09-09 14:21:31,638 DEBUG dir '/usr' needs '354729984' of 
'.FreeSpace object 
at 0x7f94752ca240>' (20906756194.00)
2016-09-09 14:21:31,639 DEBUG dir '/usr' needs '52428800' of 
'.FreeSpace object 
at 0x7f94752ca240>' (20552026210.00)
2016-09-09 14:21:31,639 DEBUG dir '/boot' needs '91338298' of 
'.FreeSpace object 
at 0x7f94752ca240>' (20499597410.00)
2016-09-09 14:21:31,639 DEBUG dir '/tmp' needs '5242880' of 
'.FreeSpace object 
at 0x7f94752ca240>' (20408259112.00)
2016-09-09 14:21:31,639 DEBUG dir '/' needs '10485760' of 
'.FreeSpace object 
at 0x7f94752ca240>' (20403016232.00)
2016-09-09 14:21:31,640 DEBUG dir '/tmp' needs '0.0' of 
'.FreeSpace object 
at 0x7f94752ca240>' (20392530472.00)
2016-09-09 14:21:31,640 DEBUG dir '/usr' needs '0.0' of 
'.FreeSpace object 
at 0x7f94752ca240>' (20392530472.00)
2016-09-09 14:21:31,643 DEBUG demoted: 'makedev'
2016-09-09 14:21:31,643 DEBUG found components: {'yakkety-security': set(), 
'yakkety': {'multiverse', 'universe', 'restricted', 'main'}, 'yakkety-updates': 
{'multiverse', 'universe', 'restricted', 'main'}
}
2016-09-09 14:21:31,810 DEBUG toinstall: '['btrfs-progs', 'dirmngr', 
'gnupg-agent', 'gnupg-l10n', 'libassuan0', 'libicu57', 'libip4tc0', 
'libip6tc0', 'libiptc0', 'libjson-c3', 'libksba8', 'libnpth0', 'libpng16-16', 
'libprocps6', 'linux-headers-4.4.0-9136', 'linux-headers-4.4.0-9136-generic', 
'linux-image-4.4.0-9136-generic', 'linux-image-extra-4.4.0-9136-generic', 
'pinentry-curses', 'python3-crypto', 'python3-distro-info', 'python3-httplib2', 
'python3-keyring', 'python3-keyrings.alt', 'python3-launchpadlib', 
'python3-lazr.restfulclient', 'python3-lazr.uri', 'python3-oauth', 
'python3-secretstorage', 'python3-setuptools', 'python3-simplejson', 
'python3-wadllib', 'python3-zope.interface']'
2016-09-09 14:21:31,811 DEBUG toupgrade: '['apparmor', 'apport', 'apt', 
'apt-transport-https', 'apt-utils', 'base-files', 'base-passwd', 'bash', 
'bash-completion', 'bind9-host', 'bsdutils', 'btrfs-tools', 
'busybox-initramfs', 'busybox-static', 'byobu', 'bzip2', 'cloud-guest-utils', 
'cloud-initramfs-copymods', 'cloud-initramfs-dyn-netconf', 'console-setup', 
'console-setup-linux', 'cryptsetup-bin', 'curl', 'dash', 'dbus', 'debconf', 
'debconf-i18n', 'debianutils', 'dh-python', 'distro-info-data', 'dmidecode', 
'dmsetup', 'dnsmasq-base', 'dnsutils', 'dosfstools', 'dpkg', 'e2fslibs', 
'e2fsprogs', 'ed', 'ethtool', 'file', 'findutils', 'friendly-recovery', 'fuse', 
'gcc-5-base', 'gcc-6-base', 'geoip-database', 'gettext-base', 
'gir1.2-glib-2.0', 'git-man', 'gnupg', 'gpgv', 'grep', 'groff-base', 
'grub-common', 'grub-legacy-ec2', 'grub-pc', 'grub-pc-bin', 'grub2-common', 
'haveged', 'hdparm', 'hostname', 'ifupdown', 'info', 'init', 
'init-system-helpers', 'initramfs-tools', 'initramfs-tools-bin', 
 'initramfs-tools-core', 'install-info', 'iptables', 'iputils-ping', 
'iputils-tracepath', 'isc-dhcp-client', 'isc-dhcp-common', 'iso-codes', 'kbd', 
'keyboard-configuration', 'klibc-utils', 'kmod', 'krb5-locales', 'less', 
'libaccountsservice0', 'libapparmor-perl', 'libapparmor1', 'libapt-inst2.0', 
'libapt-pkg5.0', 'libasprintf0v5', 'libatm1', 'libaudit-common', 'libaudit1', 
'libbind9-140', 'libblkid1', 'libbsd0', 'libbz2-1.0', 'libc-bin', 'libc6', 
'libcap-ng0', 'libcap2', 'libcap2-bin', 'libcomerr2', 'libcryptsetup4', 
'libcurl3-gnutls', 'libdb5.3', 'libdbus-1-3', 'libdebconfclient0', 
'libdevmapper-event1.02.1', 'libdevmapper1.02.1', 'libdns-export162', 
'libdns162', 'libdrm2', 'libelf1', 'liberror-perl', 'libestr0', 'libexpat1', 
'libfdisk1', 'libfreetype6', 'libfuse2', 'libgcc1', 'libgcrypt20', 'libgdbm3', 
'libgeoip1', 'libgirepository-1.0-1', 'libglib2.0-0', 'libglib2.0-data', 
'libgmp10', 'libgnutls-openssl27', 'libgnutls30', 'libgpg-error0', 'libgpm2', 
'libgssapi-krb5-2', 'libhavege1
 ', 'libidn11', 'libisc-export160', 'libisc160', 'libisccc140', 'libisccfg140', 
'libk5crypto3', 'libkeyutils1', 'libklibc', 'libkmod2', 'libkrb5-3', 
'libkrb5support0', 'libldap-2.4-2', 'liblocale-gettext-perl', 'liblvm2app2.2', 
'liblwres141', 'liblzma5', 'libmagic1', 'libmnl0', 'libmount1', 'libmpfr4', 
'libncurses5', 'libncursesw5', 'libnewt0.52', 'libnuma1', 'libp11-kit0', 
'libpam-systemd', 'libpci3', 'libpcre3', 'libperl5.22', 'libplymouth4', 
'libpolkit-agent-1-0', 'libpolkit-backend-1-0', 'libpolkit-gobject-1-0', 
'libpython3-stdlib', 'libpython3.5-minimal', 'libpython3.5-stdlib', 'librtmp1', 
'libsasl2-2', 'libsasl2-modules', 'libsasl2-modules-db', 'libseccomp2', 
'libselinux1', 'libsemanage-common', 'libsemanage1', 'libsepol1', 
'libsigsegv2', 'libslang2', 'libsmartcols1', 'libsqlite3-0', 'libss2', 
'libssl1.0.

[Touch-packages] [Bug 1614576] Re: Upgrade from xenial to yakkety fails when install policykit-1

[Max Brustkern]

This only appears to occur on unattended upgrades. Additional logs are
attached, and I'll attach some more shortly.

** Attachment added: "dpkg.log"
   
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1614576/+attachment/4737861/+files/dpkg.log

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

Title:
  Upgrade from xenial to yakkety fails when install policykit-1

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  When doing an automated upgrade from xenial to yakkey, I get:
  Preparing to unpack .../policykit-1_0.105-16_amd64.deb ...
  Created symlink /run/systemd/system/polkitd.service auto-upgrade [10:48:43]: 
ERROR: ERROR: Something went wrong with the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: policykit-1 0.105-16
  ProcVersionSignature: User Name 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Thu Aug 18 11:02:06 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to yakkety on 2016-08-18 (0 days ago)

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

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

[Touch-packages] [Bug 1614576] Re: Upgrade from xenial to yakkety fails when install policykit-1

[Max Brustkern]

** Attachment added: "var-log-dist-upgrade.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1614576/+attachment/4737863/+files/var-log-dist-upgrade.tgz

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

Title:
  Upgrade from xenial to yakkety fails when install policykit-1

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  When doing an automated upgrade from xenial to yakkey, I get:
  Preparing to unpack .../policykit-1_0.105-16_amd64.deb ...
  Created symlink /run/systemd/system/polkitd.service auto-upgrade [10:48:43]: 
ERROR: ERROR: Something went wrong with the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: policykit-1 0.105-16
  ProcVersionSignature: User Name 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Thu Aug 18 11:02:06 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to yakkety on 2016-08-18 (0 days ago)

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

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

[Touch-packages] [Bug 1527303] Re: Audio echo instead of call

[Max Kristen]

Turns out the problem was with my SIM-Card, the problem occurs in other
phones to.

** Changed in: dialer-app (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Audio echo instead of call

Status in dialer-app package in Ubuntu:
  Fix Released

Bug description:
  When calling, or being called, there is a chance of about 20% that, when the 
call is accepted, the only thing you hear is your voice as an echo.
  The other person ( I tested it multiple times, with different  setups, e.g. 
Ubuntu phone to Ubuntu Phone, Android to Ubuntu Phone, etc. ) can hear me, but 
I only hear my own voice.
  This bug also affects two other Ubuntu Phone users that I know, and it really 
is annoying.
  If you need further Information (crashdumps, logs etc) I'm happy to help.

  The bug is not fixed in OTA 8,5.

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

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

[Touch-packages] [Bug 1577760] Re: Screen Display 'Apply' fails

[Max Waterman]

Wow, I'm so pleased I was able to help. I used to work for Global
Product Support at Silicon Graphics, and this reminds me of how much I
enjoyed that job :) Now I do web application development, which can be
pleasing at times too.

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

Title:
  Screen Display 'Apply' fails

Status in upower package in Ubuntu:
  Invalid

Bug description:
  Since upgrading to 16.04, when I click on the 'Apply' button of the
  'Screen Display' utility (without setting anything), I get an error
  dialog:

  "Failed to apply configuration: %s
  GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.gnome.SettingsDaemon.XRANDR_2' on object at path 
/org/gnome/SettingsDaemon/XRANDR"

  What I expect to be able to configure multiple monitors - though it
  fails even when I have none connected.

  It is a Lenovo X250 with a docking station (though it doesn't make any
  difference if the docking station is used or not).

  WORKAROUND: sudo ln -s /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0
  /usr/lib/x86_64-linux-gnu/libusbmuxd.so.2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May  3 13:20:37 2016
  DistUpgraded: 2016-04-22 10:05:12,580 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2226]
  InstallationDate: Installed on 2015-05-20 (348 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CM001QUK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (11 days ago)
  dmi.bios.date: 04/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET33W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CM001QUK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET33W(1.12):bd04/06/2015:svnLENOVO:pn20CM001QUK:pvrThinkPadX250:rvnLENOVO:rn20CM001QUK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CM001QUK
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue May  3 12:33:42 2016
  xserver.configfile: default
  xserver.errors:
   intel(0): page flipping failed, on CRTC:25 (pipe=1), disabling synchronous 
page flips
   intel(0): failed to set mode: No such file or directory [2]
   intel(0): Failed to restore display configuration
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1079
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1615491] [NEW] Network Manager Bug After Disabled Networking

[Max Rafiandy]

Public bug reported:

Network Manager can't scan WiFi network after disabling WiFi

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "dmesg.txt"
   https://bugs.launchpad.net/bugs/1615491/+attachment/4725368/+files/dmesg.txt

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

Title:
  Network Manager Bug After Disabled Networking

Status in network-manager package in Ubuntu:
  New

Bug description:
  Network Manager can't scan WiFi network after disabling WiFi

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

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

[Touch-packages] [Bug 1577760] Re: Screen Display 'Apply' fails

[Max Waterman]

Hrm. It's almost like it's not really the same issue (particularly not
the same *cause*).

Can you check that upowerd is actually running? :

$ ps faux | grep upowerd
maxw  4799  0.0  0.0  21296   932 pts/1S+   10:38   0:00
  \_ grep --color=auto upowerd
root  2515  0.0  0.1 354340  3928 ?Ssl  08:52   0:01 
/usr/lib/upower/upowerd

If it is running ok then I'd assume it's not the same cause and perhaps
we should go back to square one. What exactly is happening and what is
common with this bug?

You mention 'the error' so I presume it is the 'failed to apply
configuration' error mentioned in the first comment - is it exactly the
same, ie it's concerning the settings daemon? If so, then perhaps see if
that is actually running :

$ ps faux | grep settings
maxw  2888  0.0  0.8 862212 16576 ?Ssl  08:52   0:01  \_ 
/usr/lib/unity-settings-daemon/unity-settings-daemon
maxw  3062  0.0  0.4 576748  9960 ?Sl   08:52   0:00  |   
\_ /usr/lib/unity-settings-daemon/unity-fallback-mount-helper
maxw  4828  0.0  0.0  21296   972 pts/1S+   10:41   0:00
  \_ grep --color=auto settings

In the above, I presume it is process 2888. If that is not running on
your system, perhaps you should try running it and see what it complains
about. Note it is in /usr/lib, so the ldd tests we did on /usr/bin and
/bin wouldn't have caught that - perhaps try running ldd on it
specifically (that's if running it directly doesn't already tell you
what it fails to link to).

Interestingly, I notice that my trouble was with a binary called 'gnome-
settings-daemon', but on my current system (I no longer have access to
the one I was using when filing this issue) I don't have that binary at
allwhen I attempt to run it, bash suggests I install it. I would
ignore gnome-settings-daemon and try to see what unity-settings-daemon
is having a problem with, if anything - same technique though.

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

Title:
  Screen Display 'Apply' fails

Status in upower package in Ubuntu:
  Invalid

Bug description:
  Since upgrading to 16.04, when I click on the 'Apply' button of the
  'Screen Display' utility (without setting anything), I get an error
  dialog:

  "Failed to apply configuration: %s
  GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.gnome.SettingsDaemon.XRANDR_2' on object at path 
/org/gnome/SettingsDaemon/XRANDR"

  What I expect to be able to configure multiple monitors - though it
  fails even when I have none connected.

  It is a Lenovo X250 with a docking station (though it doesn't make any
  difference if the docking station is used or not).

  WORKAROUND: sudo ln -s /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0
  /usr/lib/x86_64-linux-gnu/libusbmuxd.so.2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May  3 13:20:37 2016
  DistUpgraded: 2016-04-22 10:05:12,580 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2226]
  InstallationDate: Installed on 2015-05-20 (348 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CM001QUK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (11 days ago)
  dmi.bios.date: 04/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET33W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CM001QUK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET33W(1.12):bd04/06/2015:svnLENOVO:pn20CM001QUK:pvrThinkPadX250:rvnLENOVO:rn20CM001QUK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CM001QUK
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-li

[Touch-packages] [Bug 1614576] [NEW] Upgrade from xenial to yakkety fails when install policykit-1

[Max Brustkern]

Public bug reported:

When doing an automated upgrade from xenial to yakkey, I get:
Preparing to unpack .../policykit-1_0.105-16_amd64.deb ...
Created symlink /run/systemd/system/polkitd.service auto-upgrade [10:48:43]: 
ERROR: ERROR: Something went wrong with the upgrade.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: policykit-1 0.105-16
ProcVersionSignature: User Name 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Thu Aug 18 11:02:06 2016
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: policykit-1
UpgradeStatus: Upgraded to yakkety on 2016-08-18 (0 days ago)

** Affects: policykit-1 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug yakkety

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

Title:
  Upgrade from xenial to yakkety fails when install policykit-1

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  When doing an automated upgrade from xenial to yakkey, I get:
  Preparing to unpack .../policykit-1_0.105-16_amd64.deb ...
  Created symlink /run/systemd/system/polkitd.service auto-upgrade [10:48:43]: 
ERROR: ERROR: Something went wrong with the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: policykit-1 0.105-16
  ProcVersionSignature: User Name 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Thu Aug 18 11:02:06 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to yakkety on 2016-08-18 (0 days ago)

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

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

[Touch-packages] [Bug 1577760] Re: Screen Display 'Apply' fails

[Max Waterman]

Is it upowerd that is crashing or something else? I think I noticed
messages in /var/log/syslog. That might identify some other binary that
is failing to load - perhaps grep the logs for 'error while loading
shared libraries'?

Alternatively, you could try ldd on all the binaries in /usr/bin and
/bin and see if any of the give anything in /usr/local. A bit heavy
handed, but something like this? :

$ ldd /usr/bin/* | awk '/:$/ { problemfile=$0 } /local/ { print
problemfile; print $0}'

and on /bin/* too?

...or, just move /usr/local to /usr/local.old and see if that fixes it.
However, I'm not sure if an errant library *has* to be in /usr/local
though - it might be finding one somewhere else (it used to be that you
could add paths to the LD_LIBRARY_PATH environment variable to get ldd
to look in other places - do you have that set by any chance? [printenv
| grep LD_LIBRARY_PATH]).

I'm just guessing...sorry.

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

Title:
  Screen Display 'Apply' fails

Status in upower package in Ubuntu:
  Invalid

Bug description:
  Since upgrading to 16.04, when I click on the 'Apply' button of the
  'Screen Display' utility (without setting anything), I get an error
  dialog:

  "Failed to apply configuration: %s
  GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.gnome.SettingsDaemon.XRANDR_2' on object at path 
/org/gnome/SettingsDaemon/XRANDR"

  What I expect to be able to configure multiple monitors - though it
  fails even when I have none connected.

  It is a Lenovo X250 with a docking station (though it doesn't make any
  difference if the docking station is used or not).

  WORKAROUND: sudo ln -s /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0
  /usr/lib/x86_64-linux-gnu/libusbmuxd.so.2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May  3 13:20:37 2016
  DistUpgraded: 2016-04-22 10:05:12,580 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2226]
  InstallationDate: Installed on 2015-05-20 (348 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CM001QUK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (11 days ago)
  dmi.bios.date: 04/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET33W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CM001QUK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET33W(1.12):bd04/06/2015:svnLENOVO:pn20CM001QUK:pvrThinkPadX250:rvnLENOVO:rn20CM001QUK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CM001QUK
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue May  3 12:33:42 2016
  xserver.configfile: default
  xserver.errors:
   intel(0): page flipping failed, on CRTC:25 (pipe=1), disabling synchronous 
page flips
   intel(0): failed to set mode: No such file or directory [2]
   intel(0): Failed to restore display configuration
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1079
   vendor

[Touch-packages] [Bug 1577760] Re: Screen Display 'Apply' fails

[Max Waterman]

I would do :

[~]$ ls -l /usr/lib/upower/upowerd
-rwxr-xr-x 1 root root 227400 Feb 23 09:07 /usr/lib/upower/upowerd
[~]$ ldd -r !$
ldd -r /usr/lib/upower/upowerd

and look for anything unusual in the output...iirc mine contained a lib
from /use/local, which is non standard, but it could be anywhere.

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

Title:
  Screen Display 'Apply' fails

Status in upower package in Ubuntu:
  Invalid

Bug description:
  Since upgrading to 16.04, when I click on the 'Apply' button of the
  'Screen Display' utility (without setting anything), I get an error
  dialog:

  "Failed to apply configuration: %s
  GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.gnome.SettingsDaemon.XRANDR_2' on object at path 
/org/gnome/SettingsDaemon/XRANDR"

  What I expect to be able to configure multiple monitors - though it
  fails even when I have none connected.

  It is a Lenovo X250 with a docking station (though it doesn't make any
  difference if the docking station is used or not).

  WORKAROUND: sudo ln -s /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0
  /usr/lib/x86_64-linux-gnu/libusbmuxd.so.2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May  3 13:20:37 2016
  DistUpgraded: 2016-04-22 10:05:12,580 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2226]
  InstallationDate: Installed on 2015-05-20 (348 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CM001QUK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (11 days ago)
  dmi.bios.date: 04/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET33W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CM001QUK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET33W(1.12):bd04/06/2015:svnLENOVO:pn20CM001QUK:pvrThinkPadX250:rvnLENOVO:rn20CM001QUK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CM001QUK
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue May  3 12:33:42 2016
  xserver.configfile: default
  xserver.errors:
   intel(0): page flipping failed, on CRTC:25 (pipe=1), disabling synchronous 
page flips
   intel(0): failed to set mode: No such file or directory [2]
   intel(0): Failed to restore display configuration
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1079
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1531184] Re: dnsmasq doesn't start on boot because its interface isn't up yet

[Max Chen]

yeah, Immatix! Thanks so much
added

 After=network-online.target
 Wants=network-online.target

to the [Unit] section of /lib/systemd/system/dnsmasq.service

waiting for the fixed to be release

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

Title:
  dnsmasq doesn't start on boot because its interface isn't up yet

Status in One Hundred Papercuts:
  Confirmed
Status in dnsmasq package in Ubuntu:
  Confirmed

Bug description:
  My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0
  is managed manually in /etc/network/interfaces.

  During boot, dnsmasq is started before br-vz0 is created and this
  causes dnsmasq to exit:

  Jan  5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0
  Jan  5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0
  Jan  5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up
  Jan  5 08:56:17 simon-laptop NetworkManager[937]:   NetworkManager 
(version 1.0.4) is starting...
  ...
  Jan  5 08:56:18 simon-laptop NetworkManager[937]: 
interface-parser: parsing file /etc/network/interfaces
  ...
  Jan  5 08:56:18 simon-laptop NetworkManager[937]:   found bridge ports 
none for br-vz0
  Jan  5 08:56:18 simon-laptop NetworkManager[937]:   adding bridge port 
none to eni_ifaces
  Jan  5 08:56:18 simon-laptop NetworkManager[937]:   management mode: 
unmanaged

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dnsmasq 2.75-1
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan  5 09:53:30 2016
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1464990] Re: Job for dnsmasq.service failed because the control process exited with error code

[Max Chen]

thanks emk2203
In Ubuntu 16.04.1, [Unit] section of dnsmasq.service fixes the problem:
 After=network-online.target
 Wants=network-online.target

I dont know why so long to release the fixed version

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

Title:
  Job for dnsmasq.service failed because the control process exited with
  error code

Status in dnsmasq package in Ubuntu:
  Confirmed

Bug description:
  Got an error while upgrading:

  
  Setting up dnsmasq-base (2.72-3.1build1) ...
  Setting up dnsmasq (2.72-3.1build1) ...
  Job for dnsmasq.service failed because the control process exited with error 
code. See "systemctl status dnsmasq.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript dnsmasq, action "restart" failed.
  ***

  systemctl status dnsmasq.service
  ● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
     Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor 
preset: enabled)
    Drop-In: /run/systemd/generator/dnsmasq.service.d
     └─50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf
     Active: failed (Result: exit-code) since dim. 2015-06-14 12:40:41 CEST; 
1min 11s ago
    Process: 29275 ExecStop=/etc/init.d/dnsmasq systemd-stop-resolvconf 
(code=exited, status=0/SUCCESS)
    Process: 29335 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, 
status=2)
    Process: 29331 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, 
status=0/SUCCESS)
   Main PID: 915 (code=exited, status=0/SUCCESS)

   systemd[1]: Starting dnsmasq - A lightweight DHCP and .
   dnsmasq[29331]: dnsmasq: syntax check OK.
   dnsmasq[29335]: dnsmasq: failed to create listening so...se
   systemd[1]: dnsmasq.service: Control process exited, c...=2
   systemd[1]: Failed to start dnsmasq - A lightweight DH...r.
   systemd[1]: dnsmasq.service: Unit entered failed state.
   systemd[1]: dnsmasq.service: Failed with result 'exit-...'.
  Hint: Some lines were ellipsized, use -l to show in full.

   journalctl -xe
   dnsmasq[29335]: failed to create listening socket for 192.168.1.2: Address 
already in
   dnsmasq[29335]: FAILED to start up
   systemd[1]: dnsmasq.service: Control process exited, code=exited status=2
   systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS 
server.
  -- Subject: L'unité (unit) dnsmasq.service a échoué
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- L'unité (unit) dnsmasq.service a échoué, avec le résultat failed.
   systemd[1]: Dependency failed for Host and Network Name Lookups.
  -- Subject: L'unité (unit) nss-lookup.target a échoué
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- L'unité (unit) nss-lookup.target a échoué, avec le résultat dependency.
   systemd[1]: nss-lookup.target: Job nss-lookup.target/start failed with 
result 'depend
   systemd[1]: dnsmasq.service: Unit entered failed state.
   systemd[1]: dnsmasq.service: Failed with result 'exit-code'.
   polkitd(authority=local)[910]: Unregistered Authentication Agent for 
unix-process:292

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: dnsmasq 2.72-3.1build1
  ProcVersionSignature: Ubuntu 4.0.0-1.2-generic 4.0.5
  Uname: Linux 4.0.0-1-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Jun 14 12:45:55 2015
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1609549] [NEW] [GE60 2OC\2OD\2OE, Realtek ALC892, Speaker, Internal] Underruns, dropouts or crackling sound

[Max]

Public bug reported:

Crackling sound every 5-10 min. Fixed by 
https://wiki.ubuntu.com/Audio/PositionReporting
Turning off PulseAudio timer scheduling

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  max3479 F pulseaudio
 /dev/snd/controlC1:  max3479 F pulseaudio
CurrentDesktop: GNOME
Date: Wed Aug  3 22:42:21 2016
InstallationDate: Installed on 2016-07-29 (5 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [GE60 2OC\2OD\2OE, Realtek ALC892, Speaker, Internal] Underruns, 
dropouts or crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/05/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16GCIMS.520
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-16GC
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:0.B
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16GCIMS.520:bd11/05/2014:svnMicro-StarInternationalCo.,Ltd.:pnGE602OC\2OD\2OE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GC:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
dmi.product.name: GE60 2OC\2OD\2OE
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  [GE60 2OC\2OD\2OE, Realtek ALC892, Speaker, Internal] Underruns,
  dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Crackling sound every 5-10 min. Fixed by 
https://wiki.ubuntu.com/Audio/PositionReporting
  Turning off PulseAudio timer scheduling

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  max3479 F pulseaudio
   /dev/snd/controlC1:  max3479 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Aug  3 22:42:21 2016
  InstallationDate: Installed on 2016-07-29 (5 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [GE60 2OC\2OD\2OE, Realtek ALC892, Speaker, Internal] Underruns, 
dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16GCIMS.520
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16GC
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16GCIMS.520:bd11/05/2014:svnMicro-StarInternationalCo.,Ltd.:pnGE602OC\2OD\2OE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GC:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GE60 2OC\2OD\2OE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Touch-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp

[Max Bowsher]

Acting on Cyril's suggestion above, I downloaded the Debian 8.0-2 source
package, rebuilt it locally, and installed it. It seems to have fixed
the problem for me. So perhaps the problem really is in the Ubuntu
delta?

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

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

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

[Touch-packages] [Bug 1603436] [NEW] Regression in python2.7 SRU breaks python-cassandra

[Max Bowsher]

Public bug reported:

"SRU: backport python 2.7.12 to 16.04 LTS" (bug 1591895) has caused a
regression in (at least) python-cassandra. Any attempt to connect to a
cluster fails due to:

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/cassandra/cluster.py", line 1894, in 
_reconnect_internal
return self._try_connect(host)
  File "/usr/lib/python2.7/dist-packages/cassandra/cluster.py", line 1921, in 
_try_connect
self_weakref = weakref.ref(self, callback=partial(_clear_watcher, 
weakref.proxy(connection)))
TypeError: ref() does not take keyword arguments

It would appear that Python 2.7.12 has made the permitted calling
conventions for weakref.ref() stricter.

See https://github.com/datastax/python-driver/pull/585 for upstream
discussion of the issue.

** Affects: python2.7 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: regression-update

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

Title:
  Regression in python2.7 SRU breaks python-cassandra

Status in python2.7 package in Ubuntu:
  New

Bug description:
  "SRU: backport python 2.7.12 to 16.04 LTS" (bug 1591895) has caused a
  regression in (at least) python-cassandra. Any attempt to connect to a
  cluster fails due to:

  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/cassandra/cluster.py", line 1894, in 
_reconnect_internal
  return self._try_connect(host)
File "/usr/lib/python2.7/dist-packages/cassandra/cluster.py", line 1921, in 
_try_connect
  self_weakref = weakref.ref(self, callback=partial(_clear_watcher, 
weakref.proxy(connection)))
  TypeError: ref() does not take keyword arguments

  It would appear that Python 2.7.12 has made the permitted calling
  conventions for weakref.ref() stricter.

  See https://github.com/datastax/python-driver/pull/585 for upstream
  discussion of the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1603436/+subscriptions

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

[Touch-packages] [Bug 1594814] Re: NetworkManager looking for signal strength in 'wlan0' instead of the apropriate 'wlxc46e1f1abe34"

[Max Lehmann]

** Also affects: network-manager via
   https://bugzilla.gnome.org/show_bug.cgi?id=768433
   Importance: Unknown
   Status: Unknown

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

Title:
  NetworkManager looking for signal strength in 'wlan0' instead of the
  apropriate 'wlxc46e1f1abe34"

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I get this error in my log a lot:
  "Jun 21 15:04:00 basspistol NetworkManager[834]:   [1466514240.9769] 
(wlan0): error getting signal strength: No such device"

  My wireless device (TP-Link 150Mbps Wireless N Nano USB Adapter) is
  getting a very funky name: "wlxc46e1f1abe34". It's not too much of a
  problem since the connection is established and working, but it
  renders the wifi-strength icon as if it was receiving maximum signal
  strength.

  Restarting the network-manager with: "sudo systemctl restart network-
  manager.service" solves the problem.

  Not sure if it is related, but i am also affected by this bug:
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589401
  Even after upgrading to: network-manager-gnome:amd64 (1.2.0-0ubuntu0.16.04.1, 
1.2.0-0ubuntu0.16.04.3) on 2016-06-19

  Let me know if there is any complementary information i can provide.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-lowlatency 4.4.10
  Uname: Linux 4.4.0-24-lowlatency x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun 21 15:04:46 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-21 (60 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 10.42.0.1 dev wlxc46e1f1abe34  proto static  metric 600
   10.42.0.0/24 dev wlxc46e1f1abe34  proto kernel  scope link  src 10.42.0.22  
metric 600
   169.254.0.0/16 dev wlxc46e1f1abe34  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:

  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH
  CONNECTION   CON-UUID  CON-PATH
   wlxc46e1f1abe34  wifi  connected
/org/freedesktop/NetworkManager/Devices/0  sakrecoer 1  
7bfae379-b282-4335-8bfe-f1f55229ad51  
/org/freedesktop/NetworkManager/ActiveConnection/0
   enp3s0   ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/1  --   --  
  --
   lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/2  --   --  
  --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1594814] Re: NetworkManager looking for signal strength in 'wlan0' instead of the apropriate 'wlxc46e1f1abe34"

[Max Lehmann]

I added the bug to the GNOME bugzilla:
https://bugzilla.gnome.org/show_bug.cgi?id=768433

** Bug watch added: GNOME Bug Tracker #768433
   https://bugzilla.gnome.org/show_bug.cgi?id=768433

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

Title:
  NetworkManager looking for signal strength in 'wlan0' instead of the
  apropriate 'wlxc46e1f1abe34"

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I get this error in my log a lot:
  "Jun 21 15:04:00 basspistol NetworkManager[834]:   [1466514240.9769] 
(wlan0): error getting signal strength: No such device"

  My wireless device (TP-Link 150Mbps Wireless N Nano USB Adapter) is
  getting a very funky name: "wlxc46e1f1abe34". It's not too much of a
  problem since the connection is established and working, but it
  renders the wifi-strength icon as if it was receiving maximum signal
  strength.

  Restarting the network-manager with: "sudo systemctl restart network-
  manager.service" solves the problem.

  Not sure if it is related, but i am also affected by this bug:
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589401
  Even after upgrading to: network-manager-gnome:amd64 (1.2.0-0ubuntu0.16.04.1, 
1.2.0-0ubuntu0.16.04.3) on 2016-06-19

  Let me know if there is any complementary information i can provide.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-lowlatency 4.4.10
  Uname: Linux 4.4.0-24-lowlatency x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun 21 15:04:46 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-21 (60 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 10.42.0.1 dev wlxc46e1f1abe34  proto static  metric 600
   10.42.0.0/24 dev wlxc46e1f1abe34  proto kernel  scope link  src 10.42.0.22  
metric 600
   169.254.0.0/16 dev wlxc46e1f1abe34  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:

  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH
  CONNECTION   CON-UUID  CON-PATH
   wlxc46e1f1abe34  wifi  connected
/org/freedesktop/NetworkManager/Devices/0  sakrecoer 1  
7bfae379-b282-4335-8bfe-f1f55229ad51  
/org/freedesktop/NetworkManager/ActiveConnection/0
   enp3s0   ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/1  --   --  
  --
   lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/2  --   --  
  --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1562552] Re: package systemd 225-1ubuntu9.1 failed to install/upgrade: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 2 zurück

[Max M.]

*** This bug is a duplicate of bug 1561467 ***
https://bugs.launchpad.net/bugs/1561467

Hello, I'm the one who got that Error.
I wanted to say that this was a fresh installation directly upgraded. It was 
just an older image.
I previously made a packet update and got an adobe flashplugin-error. Maybe 
that could help you?
Greetings, Max

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

Title:
  package systemd 225-1ubuntu9.1 failed to install/upgrade: Unterprozess
  installiertes pre-removal-Skript gab den Fehlerwert 2 zurück

Status in systemd package in Ubuntu:
  New

Bug description:
  Tried to update from 15.10 Ubuntu Gnome to 16.04 Beta2 Ubuntu Gnome by
  do-release-update -d Did not work

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 225-1ubuntu9.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sun Mar 27 18:32:24 2016
  DuplicateSignature: package:systemd:225-1ubuntu9.1:Unterprozess installiertes 
pre-removal-Skript gab den Fehlerwert 2 zurück
  ErrorMessage: Unterprozess installiertes pre-removal-Skript gab den 
Fehlerwert 2 zurück
  InstallationDate: Installed on 2015-10-30 (148 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: Dell Inc. Precision M4300
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic 
root=UUID=b03abaa8-cf10-474b-a3f6-004b9a1d2a70 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.8
  SourcePackage: systemd
  Title: package systemd 225-1ubuntu9.1 failed to install/upgrade: Unterprozess 
installiertes pre-removal-Skript gab den Fehlerwert 2 zurück
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: Upgraded to xenial on 2016-03-27 (0 days ago)
  dmi.bios.date: 01/20/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0UY141
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd01/20/2010:svnDellInc.:pnPrecisionM4300:pvr:rvnDellInc.:rn0UY141:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Precision M4300
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1472792] Re: evince does not open with broadway backend

[Max Chao]

** Tags added: xenial

** Package changed: gtk+3.0 (Ubuntu) => ubuntu

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

Title:
  evince does not open with broadway backend

Status in Ubuntu:
  Confirmed

Bug description:
  On Lubuntu 15.04, when trying to open Evince with GTK+ Broadway
  backend, Evince reports incomplete errors and then ends.

  In first terminal:

  $ broadwayd -a 127.0.0.1 -p 8889 :2
  Listening on /run/user/1000/broadway3.socket

  In second terminal:

  $ GDK_BACKEND=broadway BROADWAY_DISPLAY=:2 evince
  Unable to init server: Could not connect: Permission denied
  Cannot parse arguments: Cannot open display: 

  (There is nothing more in the output, program ends.)

  gtk3-demo or gitg have GUI in a browser as expected.

  Not sure if related or if it is perhaps expected, but I cannot see the
  socket file (with sudo or without):

  $ ls /run/user/1000/broadway3.socket
  ls: cannot access /run/user/1000/broadway3.socket: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: libgtk-3-0 3.14.13-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Jul  8 17:13:25 2015
  InstallationDate: Installed on 2015-02-09 (149 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to vivid on 2015-05-30 (38 days ago)

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

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

[Touch-packages] [Bug 1577885] Re: 120sec delay during shutdown or reboot with still mounted cifs (via Wifi)

[Max-Ulrich Farber]

In https://wiki.archlinux.org/index.php/talk:NFS#NetworkManager-wait-
online I found a workaround that works for me (ArchLinux has been using
systemd for a long time already):

 * create a file /lib/systemd/system/auto_share.service with the following 
contents:
 After=NetworkManager-wait-online.service
 Before=systemd-user-sessions.service

 * execute the following commands in a terminal:
 systemctl enable NetworkManager-wait-online
 systemctl reenable auto_share.service 

Having done this once, booting and shutdown works fine, even with still
mounted cifs shares. It stays the same after system reboot.

Even if this workaround will work fine for everyone (?), this bug should
be fixed permanently anyhow!

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

Title:
  120sec delay during shutdown or reboot with still mounted cifs (via
  Wifi)

Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu 16.04 Desktop with Unity, used the same approach in 14.04
  with no issue.

  I prepare for mounting with the following entry in /etc/fstab my
  Synology NAS :

  //192.168.178.61/data /media/server/server_data cifs
  
users,uid=1000,gid=1000,username=x,passwd=xx,iocharset=utf8,sec=ntlm,noauto,_netdev
  0

  After login to unity, I mount it with a bash-script (mount -a) which
  is called from ~/.config/autostart/myMounts.desktop

  Doing this, and shuting down or rebooting lead into a very delayed
  shutdown (round about 2 minutes) Pressing ESC Key, showed that the
  process stops at the command "umount /media/server ..."

  I have not tested if this also occurs when I am connected via
  ethernet. I think it is because the (Wifi)Network is already disabled
  prior all umounts are done.

  This issue happens even if I type in a shutdown command into a
  Terminal or if I choose shutdown form the menue, also if I use the
  power-button.

  Failure can be avoided if I umount the network-drives manually
  previouse to reboot.

  Interim solution was, to create an alias for "shutdown" like "sh
  /path/to/umount/script.sh && shutdown" in /etc/bash.bashrc.local.

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

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

[Touch-packages] [Bug 1577760] Re: Screen Display 'Apply' fails

[Max Waterman]

Ah, I think I just 'got' what you were suggesting. If I move the
/usr/local/lib/libimobiledevice* away, and then look at the ldd output
from upowerd, I see that it indeed shows it linked to libusbmuxd.so.4,
rather than .2.

[~]$ ldd -r /usr/lib/upower/upowerd | grep usbmuxd
libusbmuxd.so.4 => /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4 
(0x7f35bc721000)

So, yes, that /usr/local/lib/ library was causing a dependency on the
old version of the libusbmuxd library.

Following that line of thinking, I also removed the workaround and, yes:

[~] gnome-settings-daemon --replace

still runs.

If I then reboot, all works as planned (command line and the Apply button 
itself). I think you're right.
upowerd was being linked to /usr/local/lib/libimobiledevice.so.6 instead of 
/usr/lib/x86_64-linux-gnu/libimobiledevice.so.6, and the former was linked to 
/usr/lib/x86_64-linux-gnu/libusbmuxd.so.2, instead of 
/usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.

So, why is upowerd getting linked to
/usr/local/lib/libimobiledevice.so.6 in the first place?

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

Title:
  Screen Display 'Apply' fails

Status in upower package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to 16.04, when I click on the 'Apply' button of the
  'Screen Display' utility (without setting anything), I get an error
  dialog:

  "Failed to apply configuration: %s
  GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.gnome.SettingsDaemon.XRANDR_2' on object at path 
/org/gnome/SettingsDaemon/XRANDR"

  What I expect to be able to configure multiple monitors - though it
  fails even when I have none connected.

  It is a Lenovo X250 with a docking station (though it doesn't make any
  difference if the docking station is used or not).

  WORKAROUND: sudo ln -s /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0
  /usr/lib/x86_64-linux-gnu/libusbmuxd.so.2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May  3 13:20:37 2016
  DistUpgraded: 2016-04-22 10:05:12,580 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2226]
  InstallationDate: Installed on 2015-05-20 (348 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CM001QUK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (11 days ago)
  dmi.bios.date: 04/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET33W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CM001QUK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET33W(1.12):bd04/06/2015:svnLENOVO:pn20CM001QUK:pvrThinkPadX250:rvnLENOVO:rn20CM001QUK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CM001QUK
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue May  3 12:33:42 2016
  xserver.configfile: default
  xserver.errors:
   intel(0): page flipping failed, on CRTC:25 (pipe=1), disabling synchronous 
page flips
   intel(0): failed to set mode: No such file or directory [2]
   intel(0): Failed to restore display configuratio

[Touch-packages] [Bug 1577760] Re: Screen Display 'Apply' fails

[Max Waterman]

For the record :

[~]$ ls -l /usr/local/lib/libimobiledevice.so.6*
lrwxrwxrwx 1 root root 25 Apr 12 15:32 /usr/local/lib/libimobiledevice.so.6 
-> libimobiledevice.so.6.0.0
-rwxr-xr-x 1 root root 143216 Apr 12 15:32 
/usr/local/lib/libimobiledevice.so.6.0.0

So, those were made 'quite some time ago'.

[~]$ mkdir Backup
[~]$ sudo mv /usr/local/lib/libimobiledevice.* Backup
[sudo] password for davidmaxwaterman: 
[~]$ ls -l /usr/local/lib/libimobiledevice.so.6*
ls: cannot access '/usr/local/lib/libimobiledevice.so.6*': No such file or 
directory
[~]$ ldd -r /usr/lib/upower/upowerd | grep imobile
libimobiledevice.so.6 => 
/usr/lib/x86_64-linux-gnu/libimobiledevice.so.6 (0x7f45cde6e000)

I wonder if it is something to do with one of the mobile development
SDKs I have installed - Android or Tizen?

I'm not completely sure what you mean by 'Does it work' (i've had a few
problems with this upgrade so things are getting a bit blurry). However
:

[~]$ gnome-settings-daemon --replace
^C
[~]$

That seems to run, if that is what you mean.

However, that works when I move the libraries back too :

[Backup]$ sudo mv * /usr/local/lib
[Backup]$ ls -l /usr/local/lib/libimobiledevice*
-rw-r--r-- 1 root root 2330698 Apr 12 15:32 /usr/local/lib/libimobiledevice.a
-rwxr-xr-x 1 root root1041 Apr 12 15:32 /usr/local/lib/libimobiledevice.la
lrwxrwxrwx 1 root root  25 Apr 12 15:32 /usr/local/lib/libimobiledevice.so 
-> libimobiledevice.so.6.0.0
lrwxrwxrwx 1 root root  25 Apr 12 15:32 
/usr/local/lib/libimobiledevice.so.6 -> libimobiledevice.so.6.0.0
-rwxr-xr-x 1 root root  143216 Apr 12 15:32 
/usr/local/lib/libimobiledevice.so.6.0.0
[Backup]$ gnome-settings-daemon --replace
^C
[Backup]$ 

But, as I mentioned, I still have the workaround implemented - ie before
filing this bug, I did :

$ sudo ln -s /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0
/usr/lib/x86_64-linux-gnu/libusbmuxd.so.2

and that is still effective :

[Backup]$ ls -l /usr/lib/x86_64-linux-gnu/libusbmuxd.so.2
lrwxrwxrwx 1 root root 45 May  4 11:03 
/usr/lib/x86_64-linux-gnu/libusbmuxd.so.2 -> 
/usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0

And the ldd output shows it is linked to the .so.2 version :

 libusbmuxd.so.2 => /usr/lib/x86_64-linux-gnu/libusbmuxd.so.2
(0x7f3d97305000)

IMO, the /usr/lib/upower/upowerd binary should be relinked against the
.so.4 version (or plain .so), then it would use a version that is
installed by default :

[Backup]$ ls -l /usr/lib/x86_64-linux-gnu/libusbmuxd.so*
lrwxrwxrwx 1 root root19 Jan  4 23:13 
/usr/lib/x86_64-linux-gnu/libusbmuxd.so -> libusbmuxd.so.4.0.0
lrwxrwxrwx 1 root root45 May  4 11:03 
/usr/lib/x86_64-linux-gnu/libusbmuxd.so.2 -> 
/usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0
lrwxrwxrwx 1 root root19 Jan  4 23:13 
/usr/lib/x86_64-linux-gnu/libusbmuxd.so.4 -> libusbmuxd.so.4.0.0
-rw-r--r-- 1 root root 31224 Jan  4 23:13 
/usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0

You can see the dates there, indicating the manually symlinked version.

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

Title:
  Screen Display 'Apply' fails

Status in upower package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to 16.04, when I click on the 'Apply' button of the
  'Screen Display' utility (without setting anything), I get an error
  dialog:

  "Failed to apply configuration: %s
  GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.gnome.SettingsDaemon.XRANDR_2' on object at path 
/org/gnome/SettingsDaemon/XRANDR"

  What I expect to be able to configure multiple monitors - though it
  fails even when I have none connected.

  It is a Lenovo X250 with a docking station (though it doesn't make any
  difference if the docking station is used or not).

  WORKAROUND: sudo ln -s /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0
  /usr/lib/x86_64-linux-gnu/libusbmuxd.so.2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May  3 13:20:37 2016
  DistUpgraded: 2016-04-22 10:05:12,580 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2226]
  InstallationDate: Installed on 2015-05-2

[Touch-packages] [Bug 1577885] Re: 120sec delay during shutdown or reboot with still mounted cifs (via Wifi)

[Max-Ulrich Farber]

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  120sec delay during shutdown or reboot with still mounted cifs (via
  Wifi)

Status in network-manager package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu 16.04 Desktop with Unity, used the same approach in 14.04
  with no issue.

  I prepare for mounting with the following entry in /etc/fstab my
  Synology NAS :

  //192.168.178.61/data /media/server/server_data cifs
  
users,uid=1000,gid=1000,username=x,passwd=xx,iocharset=utf8,sec=ntlm,noauto,_netdev
  0

  After login to unity, I mount it with a bash-script (mount -a) which
  is called from ~/.config/autostart/myMounts.desktop

  Doing this, and shuting down or rebooting lead into a very delayed
  shutdown (round about 2 minutes) Pressing ESC Key, showed that the
  process stops at the command "umount /media/server ..."

  I have not tested if this also occurs when I am connected via
  ethernet. I think it is because the (Wifi)Network is already disabled
  prior all umounts are done.

  This issue happens even if I type in a shutdown command into a
  Terminal or if I choose shutdown form the menue, also if I use the
  power-button.

  Failure can be avoided if I umount the network-drives manually
  previouse to reboot.

  Interim solution was, to create an alias for "shutdown" like "sh
  /path/to/umount/script.sh && shutdown" in /etc/bash.bashrc.local.

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

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

[Touch-packages] [Bug 1578196] Re: External Display Port monitor not working

[Max Waterman]

I've been testing with 4.6.0 which is more recent...so I'm not sure how
and older kernel could fix it. Is there some way that could happen?

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

Title:
  External Display Port monitor not working

Status in X.Org X server:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have three monitors on my Lenovo X250, one built-in and two
  connected via a Lenovo docking station :

  built-in: 1920x1080
  HP 2335: 1920x1200
  BenQ GW2765: 2560x1440

  The HP is connected via DVI and the BenQ via Display Port.

  In this configuration, I get my HP and built-in ok, but the BenQ
  doesn't show up at all (using xrandr --query).

  If I connect the BenQ via HDMI, then it shows up in xrandr --query,
  but the display is still blank (bandwidth issue?).

  Here's the output with the DVI + DP config :

  $ xrandr --query
  Screen 0: minimum 8 x 8, current 3840 x 1200, maximum 32767 x 32767
  eDP1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 
276mm x 156mm
 1920x1080 60.04*+  59.93  
 1680x1050 59.9559.88  
 1600x1024 60.17  
 1400x1050 59.98  
 1600x900  60.00  
 1280x1024 60.02  
 1440x900  59.89  
 1280x960  60.00  
 1368x768  60.00  
 1360x768  59.8059.96  
 1152x864  60.00  
 1280x720  60.00  
 1024x768  60.00  
 1024x576  60.00  
 960x540   60.00  
 800x600   60.3256.25  
 864x486   60.00  
 640x480   59.94  
 720x405   60.00  
 640x360   60.00  
  DP1 disconnected (normal left inverted right x axis y axis)
  DP2 disconnected (normal left inverted right x axis y axis)
  DP2-1 disconnected (normal left inverted right x axis y axis)
  DP2-2 connected primary 1920x1200+0+0 (normal left inverted right x axis y 
axis) 495mm x 310mm
 1920x1200 59.95*+
 1600x1200 60.00  
 1280x1024 85.0275.0260.02  
 1280x960  60.00  
 1152x864  75.00  
 1024x768  85.0075.0370.0760.00  
 832x624   74.55  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  
  DP2-3 disconnected (normal left inverted right x axis y axis)
  HDMI1 disconnected (normal left inverted right x axis y axis)
  HDMI2 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)

  and with built-in and BenQ only :

  $ xrandr --query
  Screen 0: minimum 8 x 8, current 4480 x 1440, maximum 32767 x 32767
  eDP1 connected primary 1920x1080+0+360 (normal left inverted right x axis y 
axis) 276mm x 156mm
 1920x1080 60.04*+  59.93  
 1680x1050 59.9559.88  
 1600x1024 60.17  
 1400x1050 59.98  
 1600x900  60.00  
 1280x1024 60.02  
 1440x900  59.89  
 1280x960  60.00  
 1368x768  60.00  
 1360x768  59.8059.96  
 1152x864  60.00  
 1280x720  60.00  
 1024x768  60.00  
 1024x576  60.00  
 960x540   60.00  
 800x600   60.3256.25  
 864x486   60.00  
 640x480   59.94  
 720x405   60.00  
 640x360   60.00  
  DP1 disconnected (normal left inverted right x axis y axis)
  DP2 disconnected (normal left inverted right x axis y axis)
  DP2-1 connected 2560x1440+1920+0 (normal left inverted right x axis y axis) 
597mm x 336mm
 2560x1440 59.95*+
 1920x1080 60.0050.0059.94  
 1680x1050 59.88  
 1600x900  59.98  
 1280x1024 75.0260.02  
 1280x800  59.91  
 1152x864  75.00  
 1280x720  60.0050.0059.94  
 1024x768  75.0860.00  
 832x624   74.55  
 800x600   75.0060.32  
 720x576   50.00  
 720x480   60.0059.94  
 640x480   75.0060.0059.94  
 720x400   70.08  
  DP2-2 disconnected (normal left inverted right x axis y axis)
  DP2-3 disconnected (normal left inverted right x axis y axis)
  HDMI1 disconnected (normal left inverted right x axis y axis)
  HDMI2 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)

  This looks relevant :

  

  I'm running kernel 4.6.0-040600rc6-generic (installed as part of the
  debugging process).

  (This bug is the 'next step' from
  )

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.6.0-040600rc6-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPl

[Touch-packages] [Bug 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)

[Max-Ulrich Farber]

Unfortunately, the bug seems to be back in Ubuntu 16.04 (Xenial) now,
probably due to changements in the boot and shutdown sequences. See also
[bug 1577885].

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

Title:
  Network is brought down before network filesystems are unmounted (CIFS
  timeout at shutdown)

Status in dbus package in Ubuntu:
  Fix Released
Status in dhcdbd package in Ubuntu:
  Invalid
Status in netbase package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in sysvinit package in Ubuntu:
  Invalid
Status in wpasupplicant package in Ubuntu:
  Fix Released
Status in dhcdbd source package in Lucid:
  Invalid
Status in dhcdbd source package in Natty:
  Invalid
Status in sysvinit package in Debian:
  New

Bug description:
  IMPORTANT: this bug has enough information; please don't post
  _anything_ unless a developer asks for specific feedback! By posting
  to this bug you only make it harder for a developer to spot the gem
  comments. Please use the "me too feature" of launchpad to signal that
  you are affected and would like to see this fixed.

  I installed smbfs,and then put some entries into /etc/fstab, so they 
automount on startup. An example of this is here:
  ///  /home/hamish/  cifs  
credentials=/home/hamish/.smbcredentials,file_mode=0777,dir_mode=0777,uid=1000,gid=1000
  0  0

  ** note the use of "cifs" in the lines above **

  (The username and password are in the .smbcredentials file)

  On startup, for each entry in the /etc/fstab file, I get the following in 
dmesg:
  [   70.495504]  CIFS VFS: Error connecting to IPv4 socket. Aborting operation
  [   70.495569]  CIFS VFS: cifs_mount failed w/return code = -101
  But the shares are mounted, and a nautilus session opens up (which is also 
annoying...)

  Also logging off with CIFS shares mounted in /etc/fstab, it sits with an 
error message:
  CIFS VFS: server not responding
  CIFS VFS: no response for cmd 50 mid 
  And takes about 2 minutes to timeout. This also happened with Gutsy

  Should the timing of the mounting and dismounting be changed so that
  it works? It is related to the starting of network-manager and CIFS
  shares trying to connect on startup *before* the network is up, and
  dismounting the shares *after* network-manager is stopped.

  Hamish

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

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

[Touch-packages] [Bug 1365375] Re: package libc6-dev-i386 (not installed) failed to install/upgrade: trying to overwrite '/usr/include/gnu', which is also in package libc6-dev-amd64 2.19-0ubuntu6.3

[Max HOHENGARTEN]

I'm having this bug not solved, it happened to me when I tried to install steam 
on 16.04.
The dpkg commands mentionned by #7 and #8 worked, but didn't solve the problem 
for me.

I also tried doing sudo apt-get remove libc6-amd64:i386 libc6-dev-
amd64:i386, but my apt-get is still broken because of gcc-multilib, so
it refuses to do anything.

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

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

Status in eglibc package in Ubuntu:
  Confirmed

Bug description:
  apt-get install gcc-multilib broke it!

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libc6-dev-i386 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Thu Sep  4 08:50:46 2014
  DpkgTerminalLog:
   Preparing to unpack .../libc6-dev-i386_2.19-0ubuntu6.3_amd64.deb ...
   Unpacking libc6-dev-i386 (2.19-0ubuntu6.3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libc6-dev-i386_2.19-0ubuntu6.3_amd64.deb (--unpack):
    trying to overwrite '/usr/include/gnu', which is also in package 
libc6-dev-amd64 2.19-0ubuntu6.3
  DuplicateSignature: package:libc6-dev-i386:(not installed):trying to 
overwrite '/usr/include/gnu', which is also in package libc6-dev-amd64 
2.19-0ubuntu6.3
  ErrorMessage: trying to overwrite '/usr/include/gnu', which is also in 
package libc6-dev-amd64 2.19-0ubuntu6.3
  SourcePackage: eglibc
  Title: package libc6-dev-i386 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/include/gnu', which is also in package 
libc6-dev-amd64 2.19-0ubuntu6.3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1577885] Re: 120sec delay during shutdown or reboot with still mounted cifs (via Wifi)

[Max-Ulrich Farber]

This bug seems to be quite similar to "[Bug 211631] Network is brought
down before network filesystems are unmounted (CIFS timeout at
shutdown)", fixed in 2013. Has Xenial brought back an old problem?

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

Title:
  120sec delay during shutdown or reboot with still mounted cifs (via
  Wifi)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu 16.04 Desktop with Unity, used the same approach in 14.04
  with no issue.

  I prepare for mounting with the following entry in /etc/fstab my
  Synology NAS :

  //192.168.178.61/data /media/server/server_data cifs
  
users,uid=1000,gid=1000,username=x,passwd=xx,iocharset=utf8,sec=ntlm,noauto,_netdev
  0

  After login to unity, I mount it with a bash-script (mount -a) which
  is called from ~/.config/autostart/myMounts.desktop

  Doing this, and shuting down or rebooting lead into a very delayed
  shutdown (round about 2 minutes) Pressing ESC Key, showed that the
  process stops at the command "umount /media/server ..."

  I have not tested if this also occurs when I am connected via
  ethernet. I think it is because the (Wifi)Network is already disabled
  prior all umounts are done.

  This issue happens even if I type in a shutdown command into a
  Terminal or if I choose shutdown form the menue, also if I use the
  power-button.

  Failure can be avoided if I umount the network-drives manually
  previouse to reboot.

  Interim solution was, to create an alias for "shutdown" like "sh
  /path/to/umount/script.sh && shutdown" in /etc/bash.bashrc.local.

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

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

[Touch-packages] [Bug 1577760] Re: Screen Display 'Apply' fails

[Max Waterman]

[~]$ dpkg -l | grep upower
ii  libupower-glib3:amd640.99.4-2   
 amd64abstraction for power management - 
shared library
ii  upower   0.99.4-2   
 amd64abstraction for power management
[~]$ ls -l /usr/lib/upower/upowerd
-rwxr-xr-x 1 root root 227400 Feb 23 09:07 /usr/lib/upower/upowerd
[~]$ ldd -r !$
ldd -r /usr/lib/upower/upowerd
linux-vdso.so.1 =>  (0x7ffcbcffd000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f3d9a214000)
libupower-glib.so.3 => /usr/lib/x86_64-linux-gnu/libupower-glib.so.3 
(0x7f3d99fed000)
libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7f3d99c64000)
libusb-1.0.so.0 => /lib/x86_64-linux-gnu/libusb-1.0.so.0 
(0x7f3d99a4c000)
libgudev-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libgudev-1.0.so.0 
(0x7f3d99842000)
libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7f3d995ee000)
libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7f3d992dd000)
libimobiledevice.so.6 => /usr/local/lib/libimobiledevice.so.6 
(0x7f3d990ba000)
libplist.so.3 => /usr/lib/x86_64-linux-gnu/libplist.so.3 
(0x7f3d98eae000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f3d98ae5000)
/lib64/ld-linux-x86-64.so.2 (0x5602f9826000)
libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 
(0x7f3d988e1000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f3d986c6000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 
(0x7f3d984a4000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7f3d98289000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f3d98268000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f3d9804b000)
libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 
(0x7f3d97e43000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7f3d97bd2000)
libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0 
(0x7f3d97969000)
libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 
(0x7f3d9750e000)
libusbmuxd.so.2 => /usr/lib/x86_64-linux-gnu/libusbmuxd.so.2 
(0x7f3d97305000)
libxml2.so.2 => /usr/lib/x86_64-linux-gnu/libxml2.so.2 
(0x7f3d96f4b000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f3d96d47000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f3d96b3e000)
libicuuc.so.55 => /usr/lib/x86_64-linux-gnu/libicuuc.so.55 
(0x7f3d967aa000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f3d96587000)
libicudata.so.55 => /usr/lib/x86_64-linux-gnu/libicudata.so.55 
(0x7f3d94ad)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f3d9474e000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f3d94537000)
[~]$

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

Title:
  Screen Display 'Apply' fails

Status in upower package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to 16.04, when I click on the 'Apply' button of the
  'Screen Display' utility (without setting anything), I get an error
  dialog:

  "Failed to apply configuration: %s
  GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.gnome.SettingsDaemon.XRANDR_2' on object at path 
/org/gnome/SettingsDaemon/XRANDR"

  What I expect to be able to configure multiple monitors - though it
  fails even when I have none connected.

  It is a Lenovo X250 with a docking station (though it doesn't make any
  difference if the docking station is used or not).

  WORKAROUND: sudo ln -s /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0
  /usr/lib/x86_64-linux-gnu/libusbmuxd.so.2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May  3 13:20:37 2016
  DistUpgraded: 2016-04-22 10:05:12,580 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Sub

[Touch-packages] [Bug 1577760] Re: Screen Display 'Apply' fails

[Max Waterman]

Correct, the problem started when I *upgraded* from 15.10 to 16.04.

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

Title:
  Screen Display 'Apply' fails

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I click on the 'Apply' button of the 'Screen Display' utility
  (without setting anything), I get an error dialog :

  "Failed to apply configuration: %s
  GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.gnome.SettingsDaemon.XRANDR_2' on object at path 
/org/gnome/SettingsDaemon/XRANDR"

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

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

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

  It is the 'Screen Display' utility on the 'System Settings' tool - I
  don't know how to find out what binary that is or the package it is
  in.

  3) What you expected to happen

  I expect to be able to configure multiple monitors - though it fails
  even when I have none connected.

  4) What happened instead

  I get the above error message any time I press 'Apply'.

  I've had this ever since upgrading to 16.04.

  In case this is useful :

  [~]$ lspci
  00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated 
Graphics (rev 09)
  00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
  00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI 
Controller (rev 03)
  00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI 
Controller #1 (rev 03)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3) 
I218-LM (rev 03)
  00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition 
Audio Controller (rev 03)
  00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#6 (rev e3)
  00:1c.1 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#3 (rev e3)
  00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI 
Controller (rev 03)
  00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
  00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller 
[AHCI Mode] (rev 03)
  00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
  00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP 
Thermal Management Controller (rev 03)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI 
Express Card Reader (rev 01)
  03:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
  [~]$ 

  It is a Lenovo X250 with a docking station (though it doesn't make any
  difference if the docking station is used or not).

  IMO, this isn't related to graphics specifically...more to do with
  some DBus service...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May  3 13:20:37 2016
  DistUpgraded: 2016-04-22 10:05:12,580 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2226]
  InstallationDate: Installed on 2015-05-20 (348 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CM001QUK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (11 days ago)
  dmi.bios.date: 04/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET33W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CM001QUK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET33W(1.12):bd04/06/2015:svnLENOVO:pn20CM001QUK:pvrThinkPadX250:rvnLENOVO:rn20CM001QUK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CM001QUK
  dmi.product.

[Touch-packages] [Bug 1578196] Re: External Display Port monitor not working

[Max Waterman]

Perhaps relevant?



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

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

Title:
  External Display Port monitor not working

Status in xorg package in Ubuntu:
  New

Bug description:
  I have three monitors on my Lenovo X250, one built-in and two
  connected via a Lenovo docking station :

  built-in: 1920x1080
  HP 2335: 1920x1200
  BenQ GW2765: 2560x1440

  The HP is connected via DVI and the BenQ via Display Port.

  In this configuration, I get my HP and built-in ok, but the BenQ
  doesn't show up at all (using xrandr --query).

  If I connect the BenQ via HDMI, then it shows up in xrandr --query,
  but the display is still blank (bandwidth issue?).

  Here's the output with the DVI + DP config :

  $ xrandr --query
  Screen 0: minimum 8 x 8, current 3840 x 1200, maximum 32767 x 32767
  eDP1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 
276mm x 156mm
 1920x1080 60.04*+  59.93  
 1680x1050 59.9559.88  
 1600x1024 60.17  
 1400x1050 59.98  
 1600x900  60.00  
 1280x1024 60.02  
 1440x900  59.89  
 1280x960  60.00  
 1368x768  60.00  
 1360x768  59.8059.96  
 1152x864  60.00  
 1280x720  60.00  
 1024x768  60.00  
 1024x576  60.00  
 960x540   60.00  
 800x600   60.3256.25  
 864x486   60.00  
 640x480   59.94  
 720x405   60.00  
 640x360   60.00  
  DP1 disconnected (normal left inverted right x axis y axis)
  DP2 disconnected (normal left inverted right x axis y axis)
  DP2-1 disconnected (normal left inverted right x axis y axis)
  DP2-2 connected primary 1920x1200+0+0 (normal left inverted right x axis y 
axis) 495mm x 310mm
 1920x1200 59.95*+
 1600x1200 60.00  
 1280x1024 85.0275.0260.02  
 1280x960  60.00  
 1152x864  75.00  
 1024x768  85.0075.0370.0760.00  
 832x624   74.55  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  
  DP2-3 disconnected (normal left inverted right x axis y axis)
  HDMI1 disconnected (normal left inverted right x axis y axis)
  HDMI2 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)

  and with built-in and BenQ only :

  $ xrandr --query
  Screen 0: minimum 8 x 8, current 4480 x 1440, maximum 32767 x 32767
  eDP1 connected primary 1920x1080+0+360 (normal left inverted right x axis y 
axis) 276mm x 156mm
 1920x1080 60.04*+  59.93  
 1680x1050 59.9559.88  
 1600x1024 60.17  
 1400x1050 59.98  
 1600x900  60.00  
 1280x1024 60.02  
 1440x900  59.89  
 1280x960  60.00  
 1368x768  60.00  
 1360x768  59.8059.96  
 1152x864  60.00  
 1280x720  60.00  
 1024x768  60.00  
 1024x576  60.00  
 960x540   60.00  
 800x600   60.3256.25  
 864x486   60.00  
 640x480   59.94  
 720x405   60.00  
 640x360   60.00  
  DP1 disconnected (normal left inverted right x axis y axis)
  DP2 disconnected (normal left inverted right x axis y axis)
  DP2-1 connected 2560x1440+1920+0 (normal left inverted right x axis y axis) 
597mm x 336mm
 2560x1440 59.95*+
 1920x1080 60.0050.0059.94  
 1680x1050 59.88  
 1600x900  59.98  
 1280x1024 75.0260.02  
 1280x800  59.91  
 1152x864  75.00  
 1280x720  60.0050.0059.94  
 1024x768  75.0860.00  
 832x624   74.55  
 800x600   75.0060.32  
 720x576   50.00  
 720x480   60.0059.94  
 640x480   75.0060.0059.94  
 720x400   70.08  
  DP2-2 disconnected (normal left inverted right x axis y axis)
  DP2-3 disconnected (normal left inverted right x axis y axis)
  HDMI1 disconnected (normal left inverted right x axis y axis)
  HDMI2 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)

  This looks relevant :

  

  I'm running kernel 4.6.0-040600rc6-generic (installed as part of the
  debugging process).

  (This bug is the 'next step' from
  )

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.6.0-040600rc6-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins

[Touch-packages] [Bug 1578196] [NEW] External Display Port monitor not working

[Max Waterman]

Public bug reported:

I have three monitors on my Lenovo X250, one built-in and two connected
via a Lenovo docking station :

built-in: 1920x1080
HP 2335: 1920x1200
BenQ GW2765: 2560x1440

The HP is connected via DVI and the BenQ via Display Port.

In this configuration, I get my HP and built-in ok, but the BenQ doesn't
show up at all (using xrandr --query).

If I connect the BenQ via HDMI, then it shows up in xrandr --query, but
the display is still blank (bandwidth issue?).

Here's the output with the DVI + DP config :

$ xrandr --query
Screen 0: minimum 8 x 8, current 3840 x 1200, maximum 32767 x 32767
eDP1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 
276mm x 156mm
   1920x1080 60.04*+  59.93  
   1680x1050 59.9559.88  
   1600x1024 60.17  
   1400x1050 59.98  
   1600x900  60.00  
   1280x1024 60.02  
   1440x900  59.89  
   1280x960  60.00  
   1368x768  60.00  
   1360x768  59.8059.96  
   1152x864  60.00  
   1280x720  60.00  
   1024x768  60.00  
   1024x576  60.00  
   960x540   60.00  
   800x600   60.3256.25  
   864x486   60.00  
   640x480   59.94  
   720x405   60.00  
   640x360   60.00  
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP2-1 disconnected (normal left inverted right x axis y axis)
DP2-2 connected primary 1920x1200+0+0 (normal left inverted right x axis y 
axis) 495mm x 310mm
   1920x1200 59.95*+
   1600x1200 60.00  
   1280x1024 85.0275.0260.02  
   1280x960  60.00  
   1152x864  75.00  
   1024x768  85.0075.0370.0760.00  
   832x624   74.55  
   800x600   75.0060.32  
   640x480   75.0059.94  
   720x400   70.08  
DP2-3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

and with built-in and BenQ only :

$ xrandr --query
Screen 0: minimum 8 x 8, current 4480 x 1440, maximum 32767 x 32767
eDP1 connected primary 1920x1080+0+360 (normal left inverted right x axis y 
axis) 276mm x 156mm
   1920x1080 60.04*+  59.93  
   1680x1050 59.9559.88  
   1600x1024 60.17  
   1400x1050 59.98  
   1600x900  60.00  
   1280x1024 60.02  
   1440x900  59.89  
   1280x960  60.00  
   1368x768  60.00  
   1360x768  59.8059.96  
   1152x864  60.00  
   1280x720  60.00  
   1024x768  60.00  
   1024x576  60.00  
   960x540   60.00  
   800x600   60.3256.25  
   864x486   60.00  
   640x480   59.94  
   720x405   60.00  
   640x360   60.00  
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP2-1 connected 2560x1440+1920+0 (normal left inverted right x axis y axis) 
597mm x 336mm
   2560x1440 59.95*+
   1920x1080 60.0050.0059.94  
   1680x1050 59.88  
   1600x900  59.98  
   1280x1024 75.0260.02  
   1280x800  59.91  
   1152x864  75.00  
   1280x720  60.0050.0059.94  
   1024x768  75.0860.00  
   832x624   74.55  
   800x600   75.0060.32  
   720x576   50.00  
   720x480   60.0059.94  
   640x480   75.0060.0059.94  
   720x400   70.08  
DP2-2 disconnected (normal left inverted right x axis y axis)
DP2-3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

This looks relevant :



I'm running kernel 4.6.0-040600rc6-generic (installed as part of the
debugging process).

(This bug is the 'next step' from
)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.6.0-040600rc6-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed May  4 13:39:08 2016
DistUpgraded: 2016-04-22 10:05:12,580 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2226]
InstallationDate: Installed on 201

[Touch-packages] [Bug 1556459] Re: [Lenovo ThinkPad W530] Regression: cannot set up 3 display configuration any more (Optimus)

[Max Waterman]

I moved my issue into a separate bug :

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577760

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

Title:
  [Lenovo ThinkPad W530] Regression: cannot set up 3 display
  configuration any more (Optimus)

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  I cannot set up the third monitor any more (it was working beginning
  of March 2016 with Ubuntu 16.04).

  The configuration with NVIDIA Optimus starts with builtin display (of
  Thinkpad W530) and one of (3K) monitors, the second monitor is
  detected, but not used.

  The unity configuration tool shows me two message boxes:

  "The selected configuration for displays could not be applied
  could not set the configuration for CRTC 64"

  and

  "Failed to apply configuration: %s

  
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2: 
could not set the configuration for CRTC 64
  "

  The first one I have seen at boot time on login screen (with 3
  displays) previously, the second one is new.

  The third monitor works if Optimus gets disabled in  BIOS and the
  machine runs with Nvidia only

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Mar 12 18:44:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.16, 4.4.0-10-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-11-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f5]
   NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5]
  InstallationDate: Installed on 2016-02-25 (15 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225)
  MachineType: LENOVO 2447MU0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-12-generic 
root=UUID=c01ceec8-4b0c-447f-af8f-3e9c4ae90e15 ro rootflags=subvol=@ quiet 
splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2447MU0
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn2447MU0:pvrThinkPadW530:rvnLENOVO:rn2447MU0:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2447MU0
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Mar 12 18:30:45 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.1-1ubuntu4

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

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

[Touch-packages] [Bug 1577760] Re: Screen Display 'Apply' fails

[Max Waterman]

Prompted by all the upowerd errors in syslog, I tried to run it
manually...

[~]$ gnome-settings-daemon --replace

(gnome-settings-daemon:8495): libupower-glib-WARNING **: Couldn't connect to 
proxy: Error calling StartServiceByName for org.freedesktop.UPower: 
GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 
'org.freedesktop.UPower': timed out
Segmentation fault (core dumped)

25000 May  4 11:00:04 mwaterm1-x250 upowerd[8572]: /usr/lib/upower/upowerd: 
error while loading shared libraries: libusbmuxd.so.2: cannot open shared 
object file: No such file or directory
25001 May  4 11:00:04 mwaterm1-x250 systemd[1]: upower.service: Main process 
exited, code=exited, status=127/n/a
25002 May  4 11:00:04 mwaterm1-x250 systemd[1]: Failed to start Daemon for 
power management.
25003 May  4 11:00:04 mwaterm1-x250 systemd[1]: upower.service: Unit entered 
failed state.
25004 May  4 11:00:04 mwaterm1-x250 systemd[1]: upower.service: Failed with 
result 'exit-code'.
25005 May  4 11:00:04 mwaterm1-x250 systemd[1]: upower.service: Service 
hold-off time over, scheduling restart.
25006 May  4 11:00:04 mwaterm1-x250 systemd[1]: Stopped Daemon for power 
management.
25007 May  4 11:00:04 mwaterm1-x250 systemd[1]: Starting Daemon for power 
management...
25008 May  4 11:00:04 mwaterm1-x250 upowerd[8574]: /usr/lib/upower/upowerd: 
error while loading shared libraries: libusbmuxd.so.2: cannot open shared 
object file: No such file or directory

Since that file isn't found, I figured I'd try to link it just like the
libusbmuxd.so.4 (which is installed) to libusbmuxd.so.4.0.0

$ sudo ln -s /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0
/usr/lib/x86_64-linux-gnu/libusbmuxd.so.2

and that fixed this error so I can now use the 'Screen Display' tool
again - ie the 'Apply' button actually works now.

It seems to me like a few binaries are still linked to libusbmuxd.so.2
instead of .4, and they need rebuilding.

However, the 'Screen Display' tool doesn't register all three monitors I
have connected...I presume that is a different problem.

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

Title:
  Screen Display 'Apply' fails

Status in xorg package in Ubuntu:
  New

Bug description:
  When I click on the 'Apply' button of the 'Screen Display' utility
  (without setting anything), I get an error dialog :

  "Failed to apply configuration: %s
  GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.gnome.SettingsDaemon.XRANDR_2' on object at path 
/org/gnome/SettingsDaemon/XRANDR"

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

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

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

  It is the 'Screen Display' utility on the 'System Settings' tool - I
  don't know how to find out what binary that is or the package it is
  in.

  3) What you expected to happen

  I expect to be able to configure multiple monitors - though it fails
  even when I have none connected.

  4) What happened instead

  I get the above error message any time I press 'Apply'.

  I've had this ever since upgrading to 16.04.

  In case this is useful :

  [~]$ lspci
  00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated 
Graphics (rev 09)
  00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
  00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI 
Controller (rev 03)
  00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI 
Controller #1 (rev 03)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3) 
I218-LM (rev 03)
  00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition 
Audio Controller (rev 03)
  00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#6 (rev e3)
  00:1c.1 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#3 (rev e3)
  00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI 
Controller (rev 03)
  00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
  00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller 
[AHCI Mode] (rev 03)
  00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
  00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP 
Thermal Management Controller (rev 03)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI 
Express Card Reader (rev 01)
  03:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
  [~]$ 

  It is a Lenovo X250 with a docking station (though it doesn't make any
  difference if the docking station is used o

[Touch-packages] [Bug 1577760] Re: Screen Display 'Apply' fails

[Max Waterman]

I notice that one of my monitors is 'lost' (the BenQ one) if the laptop
is allowed to go to sleep and then awoken. The 'Screen Display' tool is
still 'non-functional'.

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

Title:
  Screen Display 'Apply' fails

Status in xorg package in Ubuntu:
  New

Bug description:
  When I click on the 'Apply' button of the 'Screen Display' utility
  (without setting anything), I get an error dialog :

  "Failed to apply configuration: %s
  GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.gnome.SettingsDaemon.XRANDR_2' on object at path 
/org/gnome/SettingsDaemon/XRANDR"

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

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

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

  It is the 'Screen Display' utility on the 'System Settings' tool - I
  don't know how to find out what binary that is or the package it is
  in.

  3) What you expected to happen

  I expect to be able to configure multiple monitors - though it fails
  even when I have none connected.

  4) What happened instead

  I get the above error message any time I press 'Apply'.

  I've had this ever since upgrading to 16.04.

  In case this is useful :

  [~]$ lspci
  00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated 
Graphics (rev 09)
  00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
  00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI 
Controller (rev 03)
  00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI 
Controller #1 (rev 03)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3) 
I218-LM (rev 03)
  00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition 
Audio Controller (rev 03)
  00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#6 (rev e3)
  00:1c.1 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#3 (rev e3)
  00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI 
Controller (rev 03)
  00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
  00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller 
[AHCI Mode] (rev 03)
  00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
  00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP 
Thermal Management Controller (rev 03)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI 
Express Card Reader (rev 01)
  03:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
  [~]$ 

  It is a Lenovo X250 with a docking station (though it doesn't make any
  difference if the docking station is used or not).

  IMO, this isn't related to graphics specifically...more to do with
  some DBus service...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May  3 13:20:37 2016
  DistUpgraded: 2016-04-22 10:05:12,580 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2226]
  InstallationDate: Installed on 2015-05-20 (348 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CM001QUK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (11 days ago)
  dmi.bios.date: 04/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET33W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CM001QUK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET33W(1.12):bd04/06/2015:svnLENOVO:pn20CM001QUK:pvrThinkPadX250:rvnLENOVO:rn20CM