[Touch-packages] [Bug 1724919] Re: Bluetooth headphones only use A2DP when connected manually

[Maksim Lin]

Just another confirmation same thing happens to me with Sony ZX770BN
headphones and same disconnect/reconnect work around works.

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

Title:
  Bluetooth headphones only use A2DP when connected manually

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Issue with Sony MDR-1ABT Bluetooth headphones:
  Once paired, the headphones will be connected automatically whenever they are 
switched on. However when connected this way, only the HSP/HFP profile will 
work and trying to change to A2DP in sound settings does nothing.
  If the headphones are then manually disconnected and reconnected from 
Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in 
sound settings will successfully make them use A2DP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   1443 F pulseaudio
   /dev/snd/pcmC0D0c:   neil   1443 F...m pulseaudio
   /dev/snd/controlC0:  neil   1443 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 19:12:59 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: MDR-1ABT
  Symptom_Type: None of the above
  Title: [MDR-1ABT, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270N-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.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z270N-WIFI
  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/1724919/+subscriptions

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

[Touch-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

[Kai-Heng Feng]

Sorry for missing your comment.
Please remove /lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Thanking you in 

[Touch-packages] [Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons

[Daniel van Vugt]

** Description changed:

- 
file:///home/castilhos/Imagens/Captura%20de%20tela%20de%202017-09-19%2012-43-54.png
+ Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  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: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Giant terminal icon is blocking out the Terminal window buttons

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  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: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

[Daniel van Vugt]

Yes, same as in comment #20 with kernel 4.13

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Thanking you in anticipation
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  

[Touch-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

[Kai-Heng Feng]

If you have, AutoEnable=true, you need to remove the udev rule that
turns on HCI devices.


Also, you may need the config file, but I can't find it in upstream 
linux-firmware:
[   14.348128] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin

[   14.439245] bluetooth hci0: Direct firmware load for 
rtl_bt/rtl8821a_config.bin failed with error -2

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 

[Touch-packages] [Bug 1740169] Re: machine sleeps immediately after waking

[Christopher M. Penalver]

ill, given this is issue is HDMI CEC related, there is no evidence this
has anything to do with xorg. Despite this:

1) Could you please advise to the full manufacturer and model of the TV?

2) Is this something that started to happen after an update?

** Tags added: latest-bios-0060

** Package changed: xorg (Ubuntu) => libcec (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/1740169

Title:
  machine sleeps immediately after waking

Status in libcec package in Ubuntu:
  Incomplete

Bug description:
  When connected to a computer and tv that supports hdmi-cec, the tv will 
apparently send more than one sleeps signal upon turning off, queuing this to 
the PC. So upon waking from sleep it will immediately go back to sleep, meaning 
I have to turn the pc back on multiple times until it stays on. There is no 
reason to queue sleep commands.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DistUpgraded: 2017-10-19 14:20:08,250 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-04-22 (292 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: xorg 1:7.7+19ubuntu3
  PackageArchitecture: amd64
  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.13.0-32-generic.efi.signed 
root=UUID=1ea63dd6-7995-4f89-8bf0-abe7f9c7edae ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-19 (112 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0060.2017.1214.2013
  dmi.board.name: NUC7i3BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J22859-303
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0060.2017.1214.2013:bd12/14/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC7i3BNB:rvrJ22859-303:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/libcec/+bug/1740169/+subscriptions

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

[Touch-packages] [Bug 1748240] Re: PulseAudio can not remember my settings between reboots

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 1748240

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.


** Summary changed:

- Puls audio can not remember my settings between reboots
+ PulseAudio can not remember my settings between reboots

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

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

Title:
  PulseAudio can not remember my settings between reboots

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Puls audio can not remember my settings between reboots. I have a usb mic 
named WUP-021-0 Analog Mono and i use for output Built-in Audio Analog Stereo. 
But every time i open my pc or reboot it my output setings will default to my 
mic WUP-021-0 Analog Mono.
  Tested in ubuntu 18.04 daily

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

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

[Touch-packages] [Bug 1748336] [NEW] package systemd 235-3ubuntu3 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon

[cyril rosik]

Public bug reported:

system starting in desktop

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd 235-3ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
Date: Fri Feb  9 03:00:20 2018
ErrorMessage: bloqué en boucle sur le traitement des actions différées (« 
triggers »), abandon
InstallationDate: Installed on 2018-02-09 (0 days ago)
InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
Lsusb:
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f5f615d4-7060-443c-b0d0-f93b92457f59 ro quiet splash
Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.19.0.4ubuntu1
 apt  1.6~alpha7ubuntu1
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.
Title: package systemd 235-3ubuntu3 failed to install/upgrade: bloqué en boucle 
sur le traitement des actions différées (« triggers »), abandon
UpgradeStatus: Upgraded to bionic on 2018-02-09 (0 days ago)
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: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package systemd 235-3ubuntu3 failed to install/upgrade: bloqué en
  boucle sur le traitement des actions différées (« triggers »), abandon

Status in systemd package in Ubuntu:
  New

Bug description:
  system starting in desktop

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  Date: Fri Feb  9 03:00:20 2018
  ErrorMessage: bloqué en boucle sur le traitement des actions différées (« 
triggers »), abandon
  InstallationDate: Installed on 2018-02-09 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f5f615d4-7060-443c-b0d0-f93b92457f59 ro quiet splash
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha7ubuntu1
  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.
  Title: package systemd 235-3ubuntu3 failed to install/upgrade: bloqué en 
boucle sur le traitement des actions différées (« triggers »), abandon
  UpgradeStatus: Upgraded to bionic on 2018-02-09 (0 days ago)
  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/systemd/+bug/1748336/+subscriptions

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

[Touch-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

[Daniel van Vugt]

https://help.ubuntu.com/community/BurningIsoHowto

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Thanking you in anticipation
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  

[Touch-packages] [Bug 1746771] Re: black background drop-down menu

[Daniel van Vugt]

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

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


** Package changed: mesa (Ubuntu) => ubuntu-themes (Ubuntu)

** This bug has been marked a duplicate of bug 1743710
   Since 2018 text in combo boxes is dark and unreadable

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

Title:
  black background drop-down menu

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  The internal drop-down menu for each program is unavailable because
  the text is only visible when I go above the mouse pointer.

  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  kernel: 4.4.113-0404113-lowlatency

  OpenGL version string: 4.5.0 NVIDIA 384.111
  medium version: 17.2.4-0Ubuntu1 ~ 16.04.4
  The very confusing operation - the menu items are not visible! - It was most 
likely that the mesa package was upgraded at the end of January.
  https://i.imgur.com/VNKlTkq.png
  https://i.imgur.com/sBIVQho.png
  https://i.imgur.com/6FdYPcj.png
  https://i.imgur.com/1RGXOlM.png
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1562661] Re: pulseaudio crashed with SIGSEGV in pa_hashmap_remove_all() from pa_hashmap_free() from pa_modargs_free() from module_bluez5_discover_LTX_pa__done() from module_bluez

[Daniel van Vugt]

Thanks. Yeah it stopped happening in Ubuntu 17.10 and later...
https://errors.ubuntu.com/problem/f25f4c78f4ef773f8f3beff66c6779af2927d9f3

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

Title:
  pulseaudio crashed with SIGSEGV in pa_hashmap_remove_all() from
  pa_hashmap_free() from pa_modargs_free() from
  module_bluez5_discover_LTX_pa__done() from
  module_bluez5_discover_LTX_pa__init()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/f25f4c78f4ef773f8f3beff66c6779af2927d9f3

  ---

  It occurred in new branch, so submit it again.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jizhang1755 F pulseaudio
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Mar 28 09:43:37 2016
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  SegvAnalysis:
   Segfault happened at: 0x7fbf00fd96a3 : mov
0x8(%rsi),%rbp
   PC (0x7fbf00fd96a3) ok
   source "0x8(%rsi)" (0x7272452e7375424c) not located in a known VMA region 
(needed readable region)!
   destination "%rbp" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_hashmap_remove_all () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
   pa_hashmap_free () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
   pa_modargs_free () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   module_bluez5_discover_LTX_pa__done () from 
/usr/lib/pulse-8.0/modules/module-bluez5-discover.so
   module_bluez5_discover_LTX_pa__init () from 
/usr/lib/pulse-8.0/modules/module-bluez5-discover.so
  Title: pulseaudio crashed with SIGSEGV in pa_hashmap_remove_all()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin audio cdrom dialout kvm libvirtd lpadmin plugdev pulse 
sambashare video
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: None
  dmi.board.name: TH61
  dmi.board.vendor: BIOSTAR Group
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd05/11/2012:svnBIOSTARGroup:pnTH61:pvr6.0:rvnBIOSTARGroup:rnTH61:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0:
  dmi.product.name: TH61
  dmi.product.version: 6.0
  dmi.sys.vendor: BIOSTAR Group

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

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

[Touch-packages] [Bug 1691556] Re: Can't send audio to Amazon Echo via Bluetooth

[Daniel van Vugt]

Can anyone with an Amazon Echo also try Ubuntu 18.04?

http://cdimages.ubuntu.com/daily-live/current/

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

Title:
  Can't send audio to Amazon Echo via Bluetooth

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Pairing and coupling to Amazon Echo works, but no sound is heard.

  I believe the issue is related to the fact that Amazon Echo is paired
  as a handset (i.e., speaker + microphone) rather than just as a
  speaker.  I believe the critical error is found in a dmesg line such
  as:

  Feb 28 10:59:05 n1 bluetoothd[1025]: a2dp-source profile connect
  failed for 50:F5:DA:A6:3F:EA: Device or resource busy

  as I describe in the askubuntu.com discussion at:

  https://askubuntu.com/questions/871630/cant-send-audio-to-amazon-echo-
  via-bluetooth

  I have clarified there my thinking and the steps I've taken thus far
  on this issue, which includes trying debug bluetooth per the Ubuntu
  wiki page which describes how to do so.

  This is probably an upstream issue, as Mike H-R has commented there
  that the problem also occurs on ArchLinux.

  I and a few others would like to get this resolved, and I am happy to
  help (I'm a software developer).  However, at this point, I'm not sure
  how to proceed without some assistance.  I suppose I could report it
  to Debain, but I've only ever used Debain vis a vis Ubuntu, so I
  thought it best to start here.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 17 22:27:59 2017
  InstallationDate: Installed on 2015-12-26 (507 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2017-02-28 (78 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: DC:53:60:97:55:17  ACL MTU: 1021:5  SCO MTU: 96:6
    UP RUNNING PSCAN
    RX bytes:13547334 acl:58 sco:0 events:1935087 errors:0
    TX bytes:1652407651 acl:1934967 sco:0 commands:76 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240

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

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

[Touch-packages] [Bug 1740169] ProcCpuinfo.txt

[ill]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1740169/+attachment/5051576/+files/ProcCpuinfo.txt

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

Title:
  machine sleeps immediately after waking

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When connected to a computer and tv that supports hdmi-cec, the tv will 
apparently send more than one sleeps signal upon turning off, queuing this to 
the PC. So upon waking from sleep it will immediately go back to sleep, meaning 
I have to turn the pc back on multiple times until it stays on. There is no 
reason to queue sleep commands.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DistUpgraded: 2017-10-19 14:20:08,250 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-04-22 (292 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: xorg 1:7.7+19ubuntu3
  PackageArchitecture: amd64
  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.13.0-32-generic.efi.signed 
root=UUID=1ea63dd6-7995-4f89-8bf0-abe7f9c7edae ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-19 (112 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0060.2017.1214.2013
  dmi.board.name: NUC7i3BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J22859-303
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0060.2017.1214.2013:bd12/14/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC7i3BNB:rvrJ22859-303:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/1740169/+subscriptions

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

[Touch-packages] [Bug 1740169] Lsusb.txt

[ill]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1740169/+attachment/5051575/+files/Lsusb.txt

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

Title:
  machine sleeps immediately after waking

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When connected to a computer and tv that supports hdmi-cec, the tv will 
apparently send more than one sleeps signal upon turning off, queuing this to 
the PC. So upon waking from sleep it will immediately go back to sleep, meaning 
I have to turn the pc back on multiple times until it stays on. There is no 
reason to queue sleep commands.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DistUpgraded: 2017-10-19 14:20:08,250 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-04-22 (292 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: xorg 1:7.7+19ubuntu3
  PackageArchitecture: amd64
  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.13.0-32-generic.efi.signed 
root=UUID=1ea63dd6-7995-4f89-8bf0-abe7f9c7edae ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-19 (112 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0060.2017.1214.2013
  dmi.board.name: NUC7i3BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J22859-303
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0060.2017.1214.2013:bd12/14/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC7i3BNB:rvrJ22859-303:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/1740169/+subscriptions

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

[Touch-packages] [Bug 1740169] Lspci.txt

[ill]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1740169/+attachment/5051574/+files/Lspci.txt

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

Title:
  machine sleeps immediately after waking

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When connected to a computer and tv that supports hdmi-cec, the tv will 
apparently send more than one sleeps signal upon turning off, queuing this to 
the PC. So upon waking from sleep it will immediately go back to sleep, meaning 
I have to turn the pc back on multiple times until it stays on. There is no 
reason to queue sleep commands.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DistUpgraded: 2017-10-19 14:20:08,250 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-04-22 (292 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: xorg 1:7.7+19ubuntu3
  PackageArchitecture: amd64
  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.13.0-32-generic.efi.signed 
root=UUID=1ea63dd6-7995-4f89-8bf0-abe7f9c7edae ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-19 (112 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0060.2017.1214.2013
  dmi.board.name: NUC7i3BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J22859-303
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0060.2017.1214.2013:bd12/14/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC7i3BNB:rvrJ22859-303:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/1740169/+subscriptions

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

[Touch-packages] [Bug 1740169] ProcModules.txt

[ill]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1740169/+attachment/5051579/+files/ProcModules.txt

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

Title:
  machine sleeps immediately after waking

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When connected to a computer and tv that supports hdmi-cec, the tv will 
apparently send more than one sleeps signal upon turning off, queuing this to 
the PC. So upon waking from sleep it will immediately go back to sleep, meaning 
I have to turn the pc back on multiple times until it stays on. There is no 
reason to queue sleep commands.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DistUpgraded: 2017-10-19 14:20:08,250 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-04-22 (292 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: xorg 1:7.7+19ubuntu3
  PackageArchitecture: amd64
  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.13.0-32-generic.efi.signed 
root=UUID=1ea63dd6-7995-4f89-8bf0-abe7f9c7edae ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-19 (112 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0060.2017.1214.2013
  dmi.board.name: NUC7i3BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J22859-303
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0060.2017.1214.2013:bd12/14/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC7i3BNB:rvrJ22859-303:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/1740169/+subscriptions

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

[Touch-packages] [Bug 1740169] ProcCpuinfoMinimal.txt

[ill]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1740169/+attachment/5051577/+files/ProcCpuinfoMinimal.txt

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

Title:
  machine sleeps immediately after waking

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When connected to a computer and tv that supports hdmi-cec, the tv will 
apparently send more than one sleeps signal upon turning off, queuing this to 
the PC. So upon waking from sleep it will immediately go back to sleep, meaning 
I have to turn the pc back on multiple times until it stays on. There is no 
reason to queue sleep commands.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DistUpgraded: 2017-10-19 14:20:08,250 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-04-22 (292 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: xorg 1:7.7+19ubuntu3
  PackageArchitecture: amd64
  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.13.0-32-generic.efi.signed 
root=UUID=1ea63dd6-7995-4f89-8bf0-abe7f9c7edae ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-19 (112 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0060.2017.1214.2013
  dmi.board.name: NUC7i3BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J22859-303
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0060.2017.1214.2013:bd12/14/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC7i3BNB:rvrJ22859-303:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/1740169/+subscriptions

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

[Touch-packages] [Bug 1740169] UdevDb.txt

[ill]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1740169/+attachment/5051580/+files/UdevDb.txt

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

Title:
  machine sleeps immediately after waking

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When connected to a computer and tv that supports hdmi-cec, the tv will 
apparently send more than one sleeps signal upon turning off, queuing this to 
the PC. So upon waking from sleep it will immediately go back to sleep, meaning 
I have to turn the pc back on multiple times until it stays on. There is no 
reason to queue sleep commands.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DistUpgraded: 2017-10-19 14:20:08,250 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-04-22 (292 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: xorg 1:7.7+19ubuntu3
  PackageArchitecture: amd64
  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.13.0-32-generic.efi.signed 
root=UUID=1ea63dd6-7995-4f89-8bf0-abe7f9c7edae ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-19 (112 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0060.2017.1214.2013
  dmi.board.name: NUC7i3BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J22859-303
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0060.2017.1214.2013:bd12/14/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC7i3BNB:rvrJ22859-303:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/1740169/+subscriptions

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

[Touch-packages] [Bug 1740169] ProcInterrupts.txt

[ill]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1740169/+attachment/5051578/+files/ProcInterrupts.txt

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

Title:
  machine sleeps immediately after waking

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When connected to a computer and tv that supports hdmi-cec, the tv will 
apparently send more than one sleeps signal upon turning off, queuing this to 
the PC. So upon waking from sleep it will immediately go back to sleep, meaning 
I have to turn the pc back on multiple times until it stays on. There is no 
reason to queue sleep commands.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DistUpgraded: 2017-10-19 14:20:08,250 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-04-22 (292 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: xorg 1:7.7+19ubuntu3
  PackageArchitecture: amd64
  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.13.0-32-generic.efi.signed 
root=UUID=1ea63dd6-7995-4f89-8bf0-abe7f9c7edae ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-19 (112 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0060.2017.1214.2013
  dmi.board.name: NUC7i3BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J22859-303
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0060.2017.1214.2013:bd12/14/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC7i3BNB:rvrJ22859-303:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/1740169/+subscriptions

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

[Touch-packages] [Bug 1740169] HookError_source_xorg.txt

[ill]

apport information

** Attachment added: "HookError_source_xorg.txt"
   
https://bugs.launchpad.net/bugs/1740169/+attachment/5051572/+files/HookError_source_xorg.txt

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

Title:
  machine sleeps immediately after waking

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When connected to a computer and tv that supports hdmi-cec, the tv will 
apparently send more than one sleeps signal upon turning off, queuing this to 
the PC. So upon waking from sleep it will immediately go back to sleep, meaning 
I have to turn the pc back on multiple times until it stays on. There is no 
reason to queue sleep commands.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DistUpgraded: 2017-10-19 14:20:08,250 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-04-22 (292 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: xorg 1:7.7+19ubuntu3
  PackageArchitecture: amd64
  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.13.0-32-generic.efi.signed 
root=UUID=1ea63dd6-7995-4f89-8bf0-abe7f9c7edae ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-19 (112 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0060.2017.1214.2013
  dmi.board.name: NUC7i3BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J22859-303
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0060.2017.1214.2013:bd12/14/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC7i3BNB:rvrJ22859-303:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/1740169/+subscriptions

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

[Touch-packages] [Bug 1740169] JournalErrors.txt

[ill]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1740169/+attachment/5051573/+files/JournalErrors.txt

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

Title:
  machine sleeps immediately after waking

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When connected to a computer and tv that supports hdmi-cec, the tv will 
apparently send more than one sleeps signal upon turning off, queuing this to 
the PC. So upon waking from sleep it will immediately go back to sleep, meaning 
I have to turn the pc back on multiple times until it stays on. There is no 
reason to queue sleep commands.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DistUpgraded: 2017-10-19 14:20:08,250 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-04-22 (292 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: xorg 1:7.7+19ubuntu3
  PackageArchitecture: amd64
  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.13.0-32-generic.efi.signed 
root=UUID=1ea63dd6-7995-4f89-8bf0-abe7f9c7edae ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-19 (112 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0060.2017.1214.2013
  dmi.board.name: NUC7i3BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J22859-303
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0060.2017.1214.2013:bd12/14/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC7i3BNB:rvrJ22859-303:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/1740169/+subscriptions

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

[Touch-packages] [Bug 1740169] DpkgLog.txt

[ill]

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1740169/+attachment/5051571/+files/DpkgLog.txt

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

Title:
  machine sleeps immediately after waking

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When connected to a computer and tv that supports hdmi-cec, the tv will 
apparently send more than one sleeps signal upon turning off, queuing this to 
the PC. So upon waking from sleep it will immediately go back to sleep, meaning 
I have to turn the pc back on multiple times until it stays on. There is no 
reason to queue sleep commands.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DistUpgraded: 2017-10-19 14:20:08,250 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-04-22 (292 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: xorg 1:7.7+19ubuntu3
  PackageArchitecture: amd64
  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.13.0-32-generic.efi.signed 
root=UUID=1ea63dd6-7995-4f89-8bf0-abe7f9c7edae ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-19 (112 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0060.2017.1214.2013
  dmi.board.name: NUC7i3BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J22859-303
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0060.2017.1214.2013:bd12/14/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC7i3BNB:rvrJ22859-303:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/1740169/+subscriptions

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

[Touch-packages] [Bug 1740169] Dependencies.txt

[ill]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1740169/+attachment/5051570/+files/Dependencies.txt

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

Title:
  machine sleeps immediately after waking

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When connected to a computer and tv that supports hdmi-cec, the tv will 
apparently send more than one sleeps signal upon turning off, queuing this to 
the PC. So upon waking from sleep it will immediately go back to sleep, meaning 
I have to turn the pc back on multiple times until it stays on. There is no 
reason to queue sleep commands.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DistUpgraded: 2017-10-19 14:20:08,250 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-04-22 (292 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: xorg 1:7.7+19ubuntu3
  PackageArchitecture: amd64
  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.13.0-32-generic.efi.signed 
root=UUID=1ea63dd6-7995-4f89-8bf0-abe7f9c7edae ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-19 (112 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0060.2017.1214.2013
  dmi.board.name: NUC7i3BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J22859-303
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0060.2017.1214.2013:bd12/14/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC7i3BNB:rvrJ22859-303:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/1740169/+subscriptions

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

[Touch-packages] [Bug 1740169] Re: machine sleeps immediately after waking

[ill]

apport information

** Tags added: apport-collected artful ubuntu

** Description changed:

- When connected to a computer and tv that supports hdmi-cec, the tv will
- apparently send more than one sleeps signal upon turning off, queuing
- this to the PC. So upon waking from sleep it will immediately go back to
- sleep, meaning I have to turn the pc back on multiple times until it
- stays on. There is no reason to queue sleep commands.
+ When connected to a computer and tv that supports hdmi-cec, the tv will 
apparently send more than one sleeps signal upon turning off, queuing this to 
the PC. So upon waking from sleep it will immediately go back to sleep, meaning 
I have to turn the pc back on multiple times until it stays on. There is no 
reason to queue sleep commands.
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.7
+ Architecture: amd64
+ DistUpgraded: 2017-10-19 14:20:08,250 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
+ DistroCodename: artful
+ DistroRelease: Ubuntu 17.10
+ DistroVariant: ubuntu
+ InstallationDate: Installed on 2017-04-22 (292 days ago)
+ InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
+ Package: xorg 1:7.7+19ubuntu3
+ PackageArchitecture: amd64
+ 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.13.0-32-generic.efi.signed 
root=UUID=1ea63dd6-7995-4f89-8bf0-abe7f9c7edae ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
+ Tags:  artful ubuntu
+ Uname: Linux 4.13.0-32-generic x86_64
+ UpgradeStatus: Upgraded to artful on 2017-10-19 (112 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/14/2017
+ dmi.bios.vendor: Intel Corp.
+ dmi.bios.version: BNKBL357.86A.0060.2017.1214.2013
+ dmi.board.name: NUC7i3BNB
+ dmi.board.vendor: Intel Corporation
+ dmi.board.version: J22859-303
+ dmi.chassis.type: 3
+ dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0060.2017.1214.2013:bd12/14/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC7i3BNB:rvrJ22859-303:cvn:ct3:cvr:
+ version.compiz: compiz N/A
+ version.libdrm2: libdrm2 2.4.83-1
+ version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
+ version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
+ version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
+ version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
+ version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
+ version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
+ version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1740169/+attachment/5051569/+files/CurrentDmesg.txt

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

Title:
  machine sleeps immediately after waking

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When connected to a computer and tv that supports hdmi-cec, the tv will 
apparently send more than one sleeps signal upon turning off, queuing this to 
the PC. So upon waking from sleep it will immediately go back to sleep, meaning 
I have to turn the pc back on multiple times until it stays on. There is no 
reason to queue sleep commands.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DistUpgraded: 2017-10-19 14:20:08,250 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-04-22 (292 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: xorg 1:7.7+19ubuntu3
  PackageArchitecture: amd64
  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.13.0-32-generic.efi.signed 
root=UUID=1ea63dd6-7995-4f89-8bf0-abe7f9c7edae ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-19 (112 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0060.2017.1214.2013
  dmi.board.name: NUC7i3BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J22859-303
  dmi.chassis.type: 3
  dmi.modalias: 

[Touch-packages] [Bug 1734586] Re: Merge NetworkManager with Debian 1.10.0-1

[Jeremy Bicha]

I have re-merged with Debian in the same bionic branch. (Next time I do
a merge like this that gets stuck, I should use a different branch name
so that 'bionic' could actually represent what is currently in
'bionic'.)

dns-manager-don-t-merge-split-DNS-search-domains.patch won't even apply
now.

The merge also includes the postinst fix from 1.8.4-1ubuntu4.

I have dropped the 3 Ubuntu Phone related patches Tony Espy mentioned
today.

And I've dropped the diff that disabled libteam support now that the
libteam MIR was approved.

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

Title:
  Merge NetworkManager with Debian 1.10.0-1

Status in network-manager package in Ubuntu:
  New

Bug description:
  Debian has packaged the latest major release of NetworkManager, 1.10.
  We should update to this version for Ubuntu 18.04 "bionic".

  I have prepared the merge at
  https://git.launchpad.net/network-manager?h=bionic

  The only thing missing is that this patch needs to be rebased or dropped:
  
https://git.launchpad.net/network-manager/tree/debian/patches/dns-manager-don-t-merge-split-DNS-search-domains.patch?h=bionic

  Otherwise, the build will fail:

  src/.libs/libNetworkManagerTest.a(src_libNetworkManager_la-nm-dns-manager.o):
  In function `merge_one_ip_config_data':
  ./src/dns/nm-dns-manager.c:417: undefined reference to
  `nm_ip4_config_get_never_default'
  ./src/dns/nm-dns-manager.c:419: undefined reference to
  `nm_ip4_config_get_never_default'

  There's been a lot of refactoring, but this commit looks important:
  https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=5c29945

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

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

[Touch-packages] [Bug 1746310] Re: Drop fonts-symbola from platform?

[Jeremy Bicha]

There were a few responses on the ubuntu-release mailing list.

https://lists.ubuntu.com/archives/ubuntu-
release/2018-February/004283.html

It looks like we're going to drop fonts-symbola from desktop-common.
Flavors are free to install fonts-noto-color-emoji themselves if they
like since Kubuntu objects to it being in desktop-common.

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

Title:
  Drop fonts-symbola from platform?

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ttf-ancient-fonts-symbola is a recommends in platform.bionic desktop-
  common so it's installed for every Ubuntu desktop flavor (Kubuntu,
  Lubuntu, Ubuntu, etc.).

  It's a transitional package now depending on fonts-symbola.

  The package description is
  "This package includes the Symbola font, which contains special symbols and 
emoji characters which are encoded in the Unicode Standard 9.0."

  It was added to the seeds in LP: #1137630 explicitly for emoji
  support.

  Ubuntu Desktop (and Ubuntu Budgie and Ubuntu MATE) now include fonts-
  noto-color-emoji for this instead.

  GTK+ in Ubuntu 18.04 supports color emoji. Qt does not.

  fonts-symbola has installed-size 3,178 kB according to apt
  fonts-noto-color-emoji has installed-size 7,277 kB

  Should we replace fonts-symbola with fonts-noto-color-emoji? Or should
  we drop it entirely?

  The only other Color Emoji font I expect to be available in Ubuntu
  soon is EmojiTwo. EmojiTwo lags behind in supporting the latest emoji
  standards.

  Screenshots of Noto Color Emoji and EmojiTwo are at
  https://community.ubuntu.com/t/try-color-emoji-in-18-04/1492

  ubuntu-release list proposal:
  https://lists.ubuntu.com/archives/ubuntu-release/2018-February/004276.html

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

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

[Touch-packages] [Bug 311029] Re: curl and pycurl is not compiled with sftp support

[Hugo Gonzalez]

Beginning 2018, want to upload to a webhost (no one supports plain FTP
anymore) and I hit this. Please, can this be put in before the next LTS?
Now it's the time.

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

Title:
  curl and pycurl is not compiled with sftp support

Status in curl package in Ubuntu:
  Triaged
Status in curl package in Debian:
  Fix Released

Bug description:
  Binary package hint: curl

  Running curl --version, I see:
  Protocols: tftp ftp telnet dict ldap ldaps http file https ftps
  SFTP is obviously missing, although it is supported by curl upstream
  The SFTP is also missing from python-pycurl, probably because libcurl doesn't 
have it.

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

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

[Touch-packages] [Bug 1723763] Re: Plasma sort of freezes when link accessed after app removed

[Christopher M. Penalver]

** Package changed: xorg (Ubuntu) => kde-baseapps (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/1723763

Title:
  Plasma sort of freezes when link accessed after app removed

Status in kde-baseapps package in Ubuntu:
  New

Bug description:
  If a link to an application is created on the desktop (from start menu
  drag-n-drop) and then the application is removed, further referencing
  the link as with ouse right click causes the dekstop to not respond.

  The keyboard is still functional so you can alt-F2 and logout and log
  back in. So it appears to be a KDE issue.

  If the link file is manually removed, it disappears from the desktop
  and solves the problem.

  I am using kubuntu arty with latest updates as of 10/14/17.

  I think this is fairly consistent and easily reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sun Oct 15 13:09:09 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: kubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev ca) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Carrizo [103c:823c]
  InstallationDate: Installed on 2017-10-06 (9 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: HP HP ProBook 455 G4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic.efi.signed 
root=UUID=4e60dd5c-ac20-4521-954d-ada9641962e4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P84 Ver. 01.04
  dmi.board.name: 823C
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 37.65
  dmi.chassis.asset.tag: 5CD7376NFH
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP84Ver.01.04:bd06/09/2017:svnHP:pnHPProBook455G4:pvr:rvnHP:rn823C:rvrKBCVersion37.65:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G4
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/kde-baseapps/+bug/1723763/+subscriptions

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

[Touch-packages] [Bug 1724404] Re: VGA Driver

[Christopher M. Penalver]

eduardotomassi, thank you for reporting this and helping make Ubuntu
better.

Could you please run the following command once from a terminal by ensuring you 
have the package xdiagnose installed, and that you click the Yes button for 
attaching additional debugging information:
apport-collect 1724404

When reporting xorg related bugs in the future, please do so via the
above method. You can learn more about this functionality at
https://wiki.ubuntu.com/ReportingBugs.

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

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

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

Title:
  VGA Driver

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I might be having issues with the display driver. the issue that i
  currently have is the fact that the fan is constantly running at max
  speed

  this is the lspci output
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)

  and also i have xserver-xorg-video-intel installed at newest version

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Oct 17 19:51:39 2017
  InstallationDate: Installed on 2017-10-17 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1724663] Re: Ubuntu frozen

[Christopher M. Penalver]

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

** This bug has been marked a duplicate of bug 1725263
   screen freezing

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

Title:
  Ubuntu frozen

Status in xorg package in Ubuntu:
  New

Bug description:
  after several minutes the Computer is "freezing" and i cannot do
  anything anymore. No mouse and no keybord is working any more. It
  looks like the system is frozen!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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: Wed Oct 18 20:50:19 2017
  DistUpgraded: 2017-01-01 17:43:39,218 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] 
[1002:130f] (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems Kaveri [Radeon R7 Graphics] 
[1019:9a18]
  InstallationDate: Installed on 2016-06-22 (483 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: MEDION D3F3-EM
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic 
root=UUID=3ec08b5b-6ced-472a-91eb-d3df3b1cfe0b ro drm.debug=0xe 
vesafb.invalid=1 plymouth:debug nopat
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-01-01 (290 days ago)
  dmi.bios.date: 06/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: D3EMW08.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: D3F3-EM
  dmi.board.vendor: MEDION
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDION
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrD3EMW08.106:bd06/09/2014:svnMEDION:pnD3F3-EM:pvr1.0:rvnMEDION:rnD3F3-EM:rvr1.0:cvnMEDION:ct3:cvr:
  dmi.product.name: D3F3-EM
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDION
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Oct 18 20:48:37 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputDell Dell USB Keyboard KEYBOARD, id 9
   inputLogitech USB Optical Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1725263] Re: screen freezing

[Christopher M. Penalver]

Gustav Goettlinger, given you noted this issue occurs in Windows, this
is likely a hardware issue, in need of a repair via the computer vendor.

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

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

Title:
  screen freezing

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  my screen is freezing after some minutes. I have no idea what the problem 
could be. This Problem does also exist at other BS like windows. So I guess 
this is a HW problem, but what hardware could cause this problem? Any idea?
  with kind regards,
  Gustav

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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: Fri Oct 20 13:58:37 2017
  DistUpgraded: 2017-01-01 17:43:39,218 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] 
[1002:130f] (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems Kaveri [Radeon R7 Graphics] 
[1019:9a18]
  InstallationDate: Installed on 2016-06-22 (484 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: MEDION D3F3-EM
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic 
root=UUID=3ec08b5b-6ced-472a-91eb-d3df3b1cfe0b ro nopat vesafb.invalid=1 
drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-01-01 (291 days ago)
  dmi.bios.date: 06/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: D3EMW08.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: D3F3-EM
  dmi.board.vendor: MEDION
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDION
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrD3EMW08.106:bd06/09/2014:svnMEDION:pnD3F3-EM:pvr1.0:rvnMEDION:rnD3F3-EM:rvr1.0:cvnMEDION:ct3:cvr:
  dmi.product.name: D3F3-EM
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDION
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Oct 20 15:57:27 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputDell Dell USB Keyboard KEYBOARD, id 9
   inputLogitech USB Optical Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1726536] Re: Cant resume after suspend/sleep

[Christopher M. Penalver]

Dario, thank you for reporting this and helping make Ubuntu better.

To advise, 4.14 kernel is not supported in Ubuntu. Also, it looks like
you have a PPA installed which may impact this issue.

To clarify, if you return to the Ubuntu kernel, and uninstall the PPA,
is this still reproducible?

** Tags added: latest-bios-2801

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

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

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

Title:
  Cant resume after suspend/sleep

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  1) 17.10 
  2) 3.26.1-0ubuntu4
  3) Pressing any button wakes computer from suspend/sleep, expecting GDM login 
screen.
  4) Waking up computer from suspend does nothing, screen remains black as it 
doesn't getting any signal (HDD led is blinking as if computer is doing 
something). Need to hard reset computer at that point.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 20:39:29 2017
  DistUpgraded: 2017-10-19 11:49:45,543 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Ellesmere [Radeon RX 470/480/570/580] 
[1682:c580]
  InstallationDate: Installed on 2017-08-25 (59 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=23900d78-4c59-4f7b-a317-4dd19bd68a7e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-19 (4 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-AR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.85+git1710210630.e580be~gd~a
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.2.2-0~z~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.2.2-0~z~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/1726536/+subscriptions

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

[Touch-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

[George Hunter]

for Daniel
I have now downloaded "Ubuntu 18.04 LTS amd64", which appears on my desktop as 
a bootable disc.  but how do I boot it?

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[Touch-packages] [Bug 1552792] Re: gnome software leaves dependencies installed

[AsciiWolf]

The aptcc PackageKit backend developer told me that autoremove is
already supported for more than 5 years, since this commit from 2012:
https://github.com/hughsie/PackageKit/commit/94a5e71ded685720e49f17dc6ee21716b33ac177

But it still does not work when using pkcon or GNOME Software. Maybe it
is not enabled by default?

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

Title:
  gnome software leaves dependencies installed

Status in GNOME Software:
  Invalid
Status in Release Notes for Ubuntu:
  Fix Released
Status in aptdaemon package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  Triaged
Status in packagekit package in Ubuntu:
  New

Bug description:
  Using gnome software (or another PackageKit or aptdaemon based UI) to
  install an application - removal of that package leaves behind
  dependencies

  Installing an application with ubuntu software centre only leaves
  behind config files (seen in synaptic labelled for complete removal).

  After installing and then removing alarm clock with USC -

  sudo apt-get autoremove
  [sudo] password for wolf:
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.

  After cleaning up and then reinstalling with gnome software, followed
  by the removal

  sudo apt-get autoremove
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED
    libappindicator1 libindicator7
  0 to upgrade, 0 to newly install, 2 to remove and 1 not to upgrade.
  After this operation, 184 kB disk space will be freed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.19.92~git20160303.26a927d-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar  3 16:23:45 2016
  InstallationDate: Installed on 2015-10-29 (126 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1730019] Re: Mouse/pointer missing after resume from sleep

[Christopher M. Penalver]

** Tags added: latest-bios-a6cn58ww

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

Title:
  Mouse/pointer missing after resume from sleep

Status in xorg package in Ubuntu:
  New

Bug description:
  After waking the machine up, I am no longer able to use the mouse as
  the pointer does not respond. Only a hard reboot fixes this.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  3 18:19:46 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5300 [17aa:3906]
  InstallationDate: Installed on 2017-11-02 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 048d:8386 Integrated Technology Express, Inc. 
   Bus 001 Device 003: ID 5986:0535 Acer, Inc 
   Bus 001 Device 002: ID 0489:e07a Foxconn / Hon Hai 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80HE
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A6CN58WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 3 Pro-1370
  dmi.modalias: 
dmi:bvnLENOVO:bvrA6CN58WW:bd08/06/2015:svnLENOVO:pn80HE:pvrLenovoYOGA3Pro-1370:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA3Pro-1370:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80HE
  dmi.product.version: Lenovo YOGA 3 Pro-1370
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/1730019/+subscriptions

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

[Touch-packages] [Bug 1730053] Re: Xorg freeze

[Christopher M. Penalver]

Tino Van Audenhove, thank you for reporting this and helping make Ubuntu
better.

1) Is this something that started happening after an update? If so,
which one?

2) Is this still reproducible updating the latest HWE stack as per
https://wiki.ubuntu.com/Kernel/LTSEnablementStack ? If so, could you
please re-test for this via http://cdimage.ubuntu.com/daily-
live/current/ and advise to the results?

** Tags added: latest-bios-1003

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

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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Every time that I want to see a film, Slideshow or other animation on 
full-size screen. There is no way of getting out. Hard reset is only solution.
  Either via Mozilla, Chromium, PDF, PPT and other, problem remains.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  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: Sat Nov  4 09:39:35 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard [1043:82b0]
  InstallationDate: Installed on 2017-04-21 (196 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  MachineType: PRIMINFO unlock install
  ProcEnviron:
   LANGUAGE=nl_BE:nl
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=9c80696a-1672-4789-b222-3d8eb560d3b4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1003
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5KPL-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1003:bd08/23/2010:svnPRIMINFO:pnunlockinstall:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-VM:rvrx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: unlock install
  dmi.product.version: System Version
  dmi.sys.vendor: PRIMINFO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.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
  xserver.bootTime: Sat Nov  4 09:32:55 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputgspca_zc3xx  KEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImPS/2 Logitech Wheel Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13988 
   vendor MED
  xserver.version: 2:1.19.3-1ubuntu1~16.04.4

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

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

[Touch-packages] [Bug 1730160] Re: Red colored vertical stripes on display

[Christopher M. Penalver]

Abhinav, thank you for reporting this and helping make Ubuntu better.

1) Could you please take a picture of this issue and attach it?

2) Is this something that started happening after an update? If so,
which one?

3) Is this still reproducible updating the latest HWE stack as per
https://wiki.ubuntu.com/Kernel/LTSEnablementStack ?

** Tags added: latest-bios-r0240e6

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

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

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

Title:
  Red colored vertical stripes on display

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  there are multiple vertical stripes on my display.
  i tried updating my software and drivers but that didnt help

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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: Sun Nov  5 01:21:07 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] 
[1002:6841] (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Thames [Radeon HD 7550M/7570M/7650M] 
[104d:90ac]
  InstallationDate: Installed on 2017-11-03 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Sony Corporation SVE15116ENB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=a02befa7-840a-44ac-b8b5-bb794f09baeb ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0240E6
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0240E6:bd11/16/2012:svnSonyCorporation:pnSVE15116ENB:pvrC903JZM5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVE15116ENB
  dmi.product.version: C903JZM5
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Nov  5 01:43:54 2017
  xserver.configfile: default
  xserver.errors: AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output  HDMI-0
LVDS   VGA-0
  xserver.version: 2:1.19.3-1ubuntu1~16.04.4
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1426362] Re: logind session files fill up /run space

[Satish Patel]

We have same issue :(

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

Title:
  logind session files fill up /run space

Status in systemd-shim package in Ubuntu:
  Confirmed

Bug description:
  Under Ubuntu 14.10 (server), systemd fills up /run/systemd/sessions directory 
with files.
  The files are 240-260 bytes, but there are many
   As per default install, /run is on tmpfs with 50 MB size. After a couple of 
days, /run/ runs out of free space, which can cause not so funny errors, like 
failed kernel update (kernel postinst tries to create files here, then fails)

  As I see, thesefiles are releated to ssh sesssions, and yes there are
  plenty SSH connection to this host. Shouldn't systemd remove these old
  session files?

  # lsb_release -rd
  Description:Ubuntu 14.10
  Release:14.10

  # apt-cache policy systemd
  systemd:
Installed: 208-8ubuntu8.2
Candidate: 208-8ubuntu8.2
Version table:
   *** 208-8ubuntu8.2 0
  500 http://hu.archive.ubuntu.com/ubuntu/ utopic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   208-8ubuntu8 0
  500 http://hu.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages

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

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

[Touch-packages] [Bug 1744429] Re: [Dell OptiPlex 755] PC freezes while playing vlc or youtube

[Christopher M. Penalver]

gregrwm, to clarify, when you attached xorg log in
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1744429/comments/42
did you reproduce the issue first then attach it?

Also, please attach kern.log after reproduction.

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

Title:
  [Dell OptiPlex 755] PC freezes while playing vlc or youtube

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When watching youtube or vlc, xorg CPU utilization increases, until
  overall CPU utilization pegs at 100%. The sound plays on a bit further
  and then stops. The mouse can move the cursor but cannot interact with
  anything.

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
     Subsystem: Dell OptiPlex 755 [1028:0211]
     Subsystem: Dell OptiPlex 755 [1028:0211]
  InstallationDate: Installed on 2016-10-15 (478 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: Dell Inc. OptiPlex 755
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro 
root=UUID=31a5bed5-4d43-4da3-a094-17c3f23ae8b1 panic=30
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-112-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/30/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1743797] Re: [HP Compaq nc6400] Blank screen on boot

[Christopher M. Penalver]

Greta Regan:

>"I've had trouble trying to capture a boot log with the settings
requested in the last posting."

What are you using to capture the boot log? It shouldn't be too
difficult to record a video of the screen with a cellphone or camera
while it is booting up.

>"Different things have happened on different attempts, including the
boot stopping dead. I'll try for a couple of more days to see if I can
get a complete log to post."

Don't worry about the different variations of bad booting. If it doesn't
boot properly in any way then post a video of the failed boot,
screenshot of when the boot stopped dead, etc. Developers just need
something to get a better sense of the issue.

** Tags added: regression-update

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

Title:
  [HP Compaq nc6400] Blank screen on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  A few months after upgrading to Ubuntu 16.04, I got a black screen
  after booting.

  WORKAROUND: Use kernel parameter:
  radeon.modeset=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  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: Wed Jan 17 10:15:32 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV515/M52 [Mobility Radeon X1300] 
[1002:714a] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company RV515/M52 [Mobility Radeon X1300] 
[103c:30ac]
  InstallationDate: Installed on 2014-04-10 (1378 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MachineType: Hewlett-Packard HP Compaq nc6400 (RB523UA#ABA)
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=123f436f-0331-4097-8a8e-54cc927298c4 ro radeon.modeset=0
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YCD Ver. F.08
  dmi.board.name: 30AC
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 56.34
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YCDVer.F.08:bd12/18/2006:svnHewlett-Packard:pnHPCompaqnc6400(RB523UA#ABA):pvrF.08:rvnHewlett-Packard:rn30AC:rvrKBCVersion56.34:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nc6400 (RB523UA#ABA)
  dmi.product.version: F.08
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Jan 17 08:23:08 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Touch-packages] [Bug 1744429] Re: [Dell OptiPlex 755] PC freezes while playing vlc or youtube

[Christopher M. Penalver]

** Tags added: bionic

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

Title:
  [Dell OptiPlex 755] PC freezes while playing vlc or youtube

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When watching youtube or vlc, xorg CPU utilization increases, until
  overall CPU utilization pegs at 100%. The sound plays on a bit further
  and then stops. The mouse can move the cursor but cannot interact with
  anything.

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
     Subsystem: Dell OptiPlex 755 [1028:0211]
     Subsystem: Dell OptiPlex 755 [1028:0211]
  InstallationDate: Installed on 2016-10-15 (478 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: Dell Inc. OptiPlex 755
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro 
root=UUID=31a5bed5-4d43-4da3-a094-17c3f23ae8b1 panic=30
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-112-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/30/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

[George Hunter]

~ >dmesg>dmesg.txt


** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+attachment/5051467/+files/dmesg.txt

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 

[Touch-packages] [Bug 1727447] Re: arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c li

[Llewelyn Trahaearn]

This issue is with Steam and the Steam runtime libraries. It has been
present for some time https://github.com/ValveSoftware/steam-for-
linux/issues/3831. The problem arises when the legacy libraries included
in the Steam runtime conflict with newer software installed on the
system. This issue affects all Steam users and is not specific to any
distribution or spin. One can easily reproduce it simply by installing
and running Steam on Arch Linux, Debian, Fedora and Ubuntu.

The simplest way to mitigate the issue is to launch Steam with the
prefer host libraries flag set. Disabling the Steam runtime altogether
is another possible solution however, this may prevent some titles from
working properly or cause Steam to misbehave if the system lacks a copy
of the libraries it depends on.

It is also possible to remedy the issue without negatively impacting
Steam or games that depend on Steam's runtime by deleting the links to
the offending libraries from the pinned_libs_* folders Steam creates at
~/.local/share/Steam/ubuntu12_32/steam-runtime. (This does not appear to
be distribution specific.)

pinned_libs_32 contains four links to libraries that must be removed to 
properly mitigate the issue:
libdbus-1.so.3: The direct cause of the reported issue.
libdbusmenu-glib.so.4: Causes the following warning if left after removing 
libdbus-1.so.3 "LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that 
doesn't believe we're it's parent." 
libdbusmenu-gtk.so.4
libgtk-x11-2.0.so.0: If left after removing libdbus-1.so.3, 
libdbusmenu-glib.so.4 and libdbusmenu-gtk.so.4 it will prevent Steam's 
appindicator from working properly.

pinned_libs_64 contains 2 links which should also be removed.
libdbusmenu-glib.so.4
libdbusmenu-gtk.so.4

This is not a permanent fix as Steam will recreate these links during
updates. Valve needs to remove these from the runtime or adopt more
modern versions to permanently fix the issue.

** Bug watch added: github.com/ValveSoftware/steam-for-linux/issues #3831
   https://github.com/ValveSoftware/steam-for-linux/issues/3831

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

Title:
  arguments to dbus_connection_unref() were incorrect, assertion
  "connection->generation == _dbus_current_generation" failed in file
  ../../../dbus/dbus-connection.c line 2824.

Status in dbus package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Confirmed

Bug description:
  Maybe related to my bug report on the steam package, my hard guess is
  that the missing system tray is causing this.

  Sadly enough it really spams the syslog in a way which makes it
  unusable. Have to truncate it every day from a size of around 60MB
  down to 0.

  The PID mentioned is connected to the steam client running. has as well been 
reported here https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1726083 just 
ubuntu-bug did not want to send in a proper bug report on this package.
  (marked the bug report the link goes to as a duplicate of this bug)

  IMHO this is critical, even if SSDs are more stable as people think,
  this produces unnecessary write and delete cycles

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: dbus 1.10.22-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 25 19:19:54 2017
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1744429] Re: [Dell OptiPlex 755] PC freezes while playing vlc or youtube

[gregrwm]

downloaded bionic cdimage yesterday, watched youtube with it today,
20min into a video (at 1.5 speed) it locked up, first the captions
stalled, then the captions caught up, then they stalled again, then the
video stalled but sound was still going, then the sound stalled too, all
quite like what happens under xenial, tho here i couldn't even move the
mouse anymore, hitting various ctl-alt-Fn did nothing, unfortunately i
hadn't installed openssh-server...

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

Title:
  [Dell OptiPlex 755] PC freezes while playing vlc or youtube

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When watching youtube or vlc, xorg CPU utilization increases, until
  overall CPU utilization pegs at 100%. The sound plays on a bit further
  and then stops. The mouse can move the cursor but cannot interact with
  anything.

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
     Subsystem: Dell OptiPlex 755 [1028:0211]
     Subsystem: Dell OptiPlex 755 [1028:0211]
  InstallationDate: Installed on 2016-10-15 (478 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: Dell Inc. OptiPlex 755
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro 
root=UUID=31a5bed5-4d43-4da3-a094-17c3f23ae8b1 panic=30
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-112-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/30/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1691556] Re: Can't send audio to Amazon Echo via Bluetooth

[Preston]

for what it's worth, pavucontrol shows that the Echo is playing music.

I just don't hear anything. :-( (I've turned volume up, too)

** Attachment added: "pavucontrol showing output levels"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1691556/+attachment/5051465/+files/screenshot-2018-02-08-160123_871x277.png

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

Title:
  Can't send audio to Amazon Echo via Bluetooth

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Pairing and coupling to Amazon Echo works, but no sound is heard.

  I believe the issue is related to the fact that Amazon Echo is paired
  as a handset (i.e., speaker + microphone) rather than just as a
  speaker.  I believe the critical error is found in a dmesg line such
  as:

  Feb 28 10:59:05 n1 bluetoothd[1025]: a2dp-source profile connect
  failed for 50:F5:DA:A6:3F:EA: Device or resource busy

  as I describe in the askubuntu.com discussion at:

  https://askubuntu.com/questions/871630/cant-send-audio-to-amazon-echo-
  via-bluetooth

  I have clarified there my thinking and the steps I've taken thus far
  on this issue, which includes trying debug bluetooth per the Ubuntu
  wiki page which describes how to do so.

  This is probably an upstream issue, as Mike H-R has commented there
  that the problem also occurs on ArchLinux.

  I and a few others would like to get this resolved, and I am happy to
  help (I'm a software developer).  However, at this point, I'm not sure
  how to proceed without some assistance.  I suppose I could report it
  to Debain, but I've only ever used Debain vis a vis Ubuntu, so I
  thought it best to start here.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 17 22:27:59 2017
  InstallationDate: Installed on 2015-12-26 (507 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2017-02-28 (78 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: DC:53:60:97:55:17  ACL MTU: 1021:5  SCO MTU: 96:6
    UP RUNNING PSCAN
    RX bytes:13547334 acl:58 sco:0 events:1935087 errors:0
    TX bytes:1652407651 acl:1934967 sco:0 commands:76 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240

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

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

[Touch-packages] [Bug 1707898] Re: systemd translations are not synced with upstream

[Gunnar Hjalmarsson]

I checked out the latest tarball with systemd translations:

https://launchpad.net/ubuntu/bionic/+upload/17531208/+files/systemd_237-1ubuntu2_amd64_translations.tar.gz

Two observations:

1. The template is named incorrectly: "untitled.pot" instead of
   "systemd.pot"

2. The template only includes strings for C files; the strings from
   the policy XML files are missing.

The proposed patch fixes those issues, even if it's in a clumsy manner.
I couldn't figure out how to make intltool-update() extract strings from
the XML files, so I made use of xgettext(). Anyway, I think this would
update LP with the latest translatable strings.

** Patch added: "systemd-translations.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1707898/+attachment/5051466/+files/systemd-translations.debdiff

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

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

** Changed in: systemd (Ubuntu)
 Assignee: Canonical Desktop Team (canonical-desktop-team) => Gunnar 
Hjalmarsson (gunnarhj)

** Changed in: ubuntu-translations
 Assignee: Canonical Desktop Team (canonical-desktop-team) => (unassigned)

** Tags added: patch

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

Title:
  systemd translations are not synced with upstream

Status in Ubuntu Translations:
  New
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Translations for systemd are outdated because they do not seem to be
  synced with the upstream ones.

  For example the Czech one:
  Launchpad: 
https://translations.launchpad.net/ubuntu/artful/+source/systemd/+pots/systemd/cs/+translate
 - 0% translated
  Upstream: https://github.com/systemd/systemd/blob/master/po/cs.po - 100% 
translated

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

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

[Touch-packages] [Bug 1743797] Re: [HP Compaq nc6400] Blank screen on boot

[Greta Regan]

I've had trouble trying to capture a boot log with the settings
requested in the last posting. Different things have happened on
different attempts, including the boot stopping dead. I'll try for a
couple of more days to see if I can get a complete log to post.

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

Title:
  [HP Compaq nc6400] Blank screen on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  A few months after upgrading to Ubuntu 16.04, I got a black screen
  after booting.

  WORKAROUND: Use kernel parameter:
  radeon.modeset=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  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: Wed Jan 17 10:15:32 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV515/M52 [Mobility Radeon X1300] 
[1002:714a] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company RV515/M52 [Mobility Radeon X1300] 
[103c:30ac]
  InstallationDate: Installed on 2014-04-10 (1378 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MachineType: Hewlett-Packard HP Compaq nc6400 (RB523UA#ABA)
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=123f436f-0331-4097-8a8e-54cc927298c4 ro radeon.modeset=0
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YCD Ver. F.08
  dmi.board.name: 30AC
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 56.34
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YCDVer.F.08:bd12/18/2006:svnHewlett-Packard:pnHPCompaqnc6400(RB523UA#ABA):pvrF.08:rvnHewlett-Packard:rn30AC:rvrKBCVersion56.34:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nc6400 (RB523UA#ABA)
  dmi.product.version: F.08
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Jan 17 08:23:08 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Touch-packages] [Bug 1730793] Re: Translations not imported from upstream

[Hans Joachim Desserud]

** Changed in: ubuntu-translations
   Status: New => Fix Released

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

Title:
  Translations not imported from upstream

Status in Ubuntu Translations:
  Fix Released
Status in util-linux package in Ubuntu:
  Fix Released

Bug description:
  The listing of Ubuntu source package translations (for Danish) reveals
  that the last import of translations for util-linux happened in 2011:

  
https://translations.launchpad.net/ubuntu/artful/+lang/da/+index?batch=300=300=300

  The Ubuntu source package version is 2.30, which appears to be from
  2017 (on my Ubuntu 16.04 it is 2.27 which is also relatively new).
  Either way it should have imported the translations from 2017.  Indeed
  util-linux has been translated very well in Danish for quite a few
  years:

  https://translationproject.org/domain/util-linux.html

  More precisely, 4000 translations are available and they have not been
  imported for (apparently) 6 years, leaving Danish at the level of 600
  strings.

  I suspect this is not really an issue with the util-linux source
  package, but rather with the whole Ubuntu/Launchpad translations
  workflow.  I can see that several packages have similar problems, and
  that is probably just the tip of the iceberg.  Unfortunately I have no
  clue how to approach that - at least I cannot file a bug report
  against The Whole Thing.  So if someone could speak to someone who
  could speak to someone who can actually get this to work, it would
  also be extremely good.

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

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

[Touch-packages] [Bug 1742946] Re: "gio monitor" does not work

[sam tygier]

I can confirm that it does not work in ubuntu 17.10, but does work in
Fedora 27 (which has glib 2.54.3
http://ftp.gnome.org/pub/gnome/sources/glib/2.54/glib-2.54.3.news)

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

Title:
  "gio monitor" does not work

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  # ls -l /etc/adduser.conf
  -rw-r--r-- 1 root root 2981 Mar 11  2012 /etc/adduser.conf
  # gio monitor file:///etc/adduser.conf
  gio: No locations given

  Usage:
gio monitor [OPTION…] [LOCATION...]

  Monitor files or directories for changes.

  Options:
-d, --dir=LOCATIONMonitor a directory (default: depends on type)
-f, --file=LOCATION   Monitor a file (default: depends on type)
-D, --direct=LOCATION Monitor a file directly (notices changes made via 
hardlinks)
-s, --silent=LOCATION Monitors a file directly, but doesn’t report 
changes
-n, --no-movesReport moves and renames as simple 
deleted/created events
-m, --mounts  Watch for mount events

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libglib2.0-bin 2.54.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 12 14:29:42 2018
  InstallationDate: Installed on 2012-03-12 (2131 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120311)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/tcsh
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

[Nils Toedtmann]

Observe #1267059 about 'Unattended-Upgrade::Remove-Unused-Dependencies'
not working as expected for old versions of unattended-upgrades, also
resulting e.g. in obsolete kernel packages not getting removed.

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Opinion
Status in update-manager package in Ubuntu:
  In Progress
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  Opinion
Status in update-manager source package in Artful:
  In Progress

Bug description:
  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Touch-packages] [Bug 1739346] Re: Freeze up

[Carlos Hamer]

Reply answers below:

On 02/06/2018 10:45 PM, Christopher M. Penalver wrote:
> Carlos Hamer, thank you for reporting this and helping make Ubuntu
> better.
>
> 1) To clarify, is this something that started happening after an 
> update?_*Correct*_
>
> 2) When the OS freezes up, do you notice any resources pegged at 100% in
> System Monitor?*_No_*
>
> 3) Is the computer completely locking up and unresponsive or does it
> become responsive after a while?_*Completely locking up and unresponsive*_
>
>
> 4) Is there something you do specifically that is correlated to the OS
> freezing up?_*Opening and using Chrome Beta*_
>
> ** Tags added: bios-outdated-2.21
>
> ** Changed in: xorg (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: xorg (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  Freeze up

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  OS freezes up all the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Dec 19 23:16:31 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0649]
  MachineType: Gateway NE56R
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=056e1ca6-0c77-4e90-afee-879313071881 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EG50_HC_HR
  dmi.board.vendor: Gateway
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.13
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.13:bd01/17/2013:svnGateway:pnNE56R:pvrV2.13:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.13:
  dmi.product.family: Type1Family
  dmi.product.name: NE56R
  dmi.product.version: V2.13
  dmi.sys.vendor: Gateway
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sun Nov 12 16:56:54 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2

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

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

[Touch-packages] [Bug 1740902] Re: package libchromaprint0:amd64 1.3-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Sebastian Ramacher]

>From the dpkg log, it looks like you tried to install vlc but something
went wrong. Do you remember the exact error? Otherwise, you're only
option is to force remove (e.g. with dpkg --remove --force-remove-
reinstreq)  the package and reinstall it.

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

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

Title:
  package libchromaprint0:amd64 1.3-1 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in chromaprint package in Ubuntu:
  Incomplete

Bug description:
  Package libchromaprint0:amd64 is not configured yet

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libchromaprint0:amd64 1.3-1
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.14
  AptOrdering:
   libchromaprint0: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Jan  2 21:10:02 2018
  DpkgTerminalLog:
   dpkg: error processing package libchromaprint0:amd64 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-01-02 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: chromaprint
  Title: package libchromaprint0:amd64 1.3-1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1737601] Re: system hangs immediately when keyring error appears

[Christopher M. Penalver]

John A Peters, closing as per your direct email noting a reinstall
resolved this.

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  system hangs immediately when keyring error appears

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Right after the system launches (unity i think) the comoputer hangs.
  I have mouse only. nothing works. Error message on screen is a Keyring
  error dialog but the buttons don't activate. all is dead.

  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 i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  CasperVersion: 1.376
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Dec 11 18:59:47 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7660D] [1043:8526]
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0309
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A/USB 3.1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  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: Mon Dec 11 18:52:50 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1748246] Re: package libv4lconvert0:i386 1.10.0-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libv4lconvert0:i386 1.10.0-1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in v4l-utils package in Ubuntu:
  New

Bug description:
  I don't know about this bug.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libv4lconvert0:i386 1.10.0-1
  ProcVersionSignature: Ubuntu 
4.4.0-103201712311231.0+mediatree+hauppauge-generic 4.4.98
  Uname: Linux 4.4.0-103201712311231-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Feb  8 12:24:48 2018
  DuplicateSignature:
   package:libv4lconvert0:i386:1.10.0-1
   Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
   dpkg: error processing package libv4lconvert0:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-12-24 (46 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: v4l-utils
  Title: package libv4lconvert0:i386 1.10.0-1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to xenial on 2017-12-24 (45 days ago)

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

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

[Touch-packages] [Bug 1748246] [NEW] package libv4lconvert0:i386 1.10.0-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati

[Stephen Poitier]

Public bug reported:

I don't know about this bug.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libv4lconvert0:i386 1.10.0-1
ProcVersionSignature: Ubuntu 
4.4.0-103201712311231.0+mediatree+hauppauge-generic 4.4.98
Uname: Linux 4.4.0-103201712311231-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Thu Feb  8 12:24:48 2018
DuplicateSignature:
 package:libv4lconvert0:i386:1.10.0-1
 Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
 dpkg: error processing package libv4lconvert0:i386 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-12-24 (46 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: v4l-utils
Title: package libv4lconvert0:i386 1.10.0-1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: Upgraded to xenial on 2017-12-24 (45 days ago)

** Affects: v4l-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package libv4lconvert0:i386 1.10.0-1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in v4l-utils package in Ubuntu:
  New

Bug description:
  I don't know about this bug.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libv4lconvert0:i386 1.10.0-1
  ProcVersionSignature: Ubuntu 
4.4.0-103201712311231.0+mediatree+hauppauge-generic 4.4.98
  Uname: Linux 4.4.0-103201712311231-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Feb  8 12:24:48 2018
  DuplicateSignature:
   package:libv4lconvert0:i386:1.10.0-1
   Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
   dpkg: error processing package libv4lconvert0:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-12-24 (46 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: v4l-utils
  Title: package libv4lconvert0:i386 1.10.0-1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to xenial on 2017-12-24 (45 days ago)

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

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

[Touch-packages] [Bug 1748239] [NEW] package libsystemd0:amd64 229-4ubuntu21.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

[Joby]

Public bug reported:

This happened while I tried to install KDE Connect while an upgrade was
in progress.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libsystemd0:amd64 229-4ubuntu21.1
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-lowlatency 4.13.13
Uname: Linux 4.13.0-32-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.15
AptOrdering:
 libsystemd0: Configure
 systemd: Install
 systemd: Configure
 libpam-systemd: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Feb  8 22:26:36 2018
DpkgTerminalLog:
 dpkg: error processing package libsystemd0:amd64 (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-02-04 (3 days ago)
InstallationMedia: Ubuntu-Studio 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: systemd
Title: package libsystemd0:amd64 229-4ubuntu21.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libsystemd0:amd64 229-4ubuntu21.1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in systemd package in Ubuntu:
  New

Bug description:
  This happened while I tried to install KDE Connect while an upgrade
  was in progress.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsystemd0:amd64 229-4ubuntu21.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-lowlatency 4.13.13
  Uname: Linux 4.13.0-32-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  AptOrdering:
   libsystemd0: Configure
   systemd: Install
   systemd: Configure
   libpam-systemd: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Feb  8 22:26:36 2018
  DpkgTerminalLog:
   dpkg: error processing package libsystemd0:amd64 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-02-04 (3 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: systemd
  Title: package libsystemd0:amd64 229-4ubuntu21.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1748240] [NEW] Puls audio can not remember my settings between reboots

[APolihron]

Public bug reported:

Puls audio can not remember my settings between reboots. I have a usb mic named 
WUP-021-0 Analog Mono and i use for output Built-in Audio Analog Stereo. But 
every time i open my pc or reboot it my output setings will default to my mic 
WUP-021-0 Analog Mono.
Tested in ubuntu 18.04 daily

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

** Description changed:

- Puls audio can not remember my settings between reboots. I have a usb mic 
named WUP-021-0 Analog Mono and i use for output Built-in Audio Analog Stereo. 
But every time i open my pc or reboot it my output setings will default to my 
mic WUP-021-0 Analog Mono. 
- Tested in ubuntu 16.04.x ,17.10 and 18.04 daily
+ Puls audio can not remember my settings between reboots. I have a usb mic 
named WUP-021-0 Analog Mono and i use for output Built-in Audio Analog Stereo. 
But every time i open my pc or reboot it my output setings will default to my 
mic WUP-021-0 Analog Mono.
+ Tested in ubuntu 18.04 daily

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

Title:
  Puls audio can not remember my settings between reboots

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Puls audio can not remember my settings between reboots. I have a usb mic 
named WUP-021-0 Analog Mono and i use for output Built-in Audio Analog Stereo. 
But every time i open my pc or reboot it my output setings will default to my 
mic WUP-021-0 Analog Mono.
  Tested in ubuntu 18.04 daily

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

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

[Touch-packages] [Bug 1747488] Re: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA"

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15

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

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

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  

[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

[Launchpad Bug Tracker]

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

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

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Opinion
Status in update-manager package in Ubuntu:
  In Progress
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  Opinion
Status in update-manager source package in Artful:
  In Progress

Bug description:
  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

[Launchpad Bug Tracker]

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

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

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Opinion
Status in update-manager package in Ubuntu:
  In Progress
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  Opinion
Status in update-manager source package in Artful:
  In Progress

Bug description:
  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 940030] Re: rsyslog stops working after logrotate until restarted

[Steve Langasek]

** Also affects: rsyslog (Ubuntu Bionic)
   Importance: Critical
 Assignee: girish (sajjanarg)
   Status: Confirmed

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

Title:
  rsyslog stops working after logrotate until restarted

Status in rsyslog package in Ubuntu:
  Confirmed
Status in rsyslog source package in Bionic:
  Confirmed

Bug description:
  This could otherwise be titled, rsyslog reload does not create log
  files; only restart does.

  This is happening on a number of machines I work on.  It's happening
  on 10.04 and 11.04.  It might be similar to:

  https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/407862

  But in my case after the restart there is no /var/log/syslog being
  created, nor auth.log, kern.log, etc.  The files are rotated, rsyslog
  is reloaded, and none of the log files are created and nothing is
  being logged.  This has been plaguing my systems since moving from
  syslog-ng, which I may return to as it seems it was actually
  production ready.

  Without manually restarting those files don't exist so here's what I
  did on an 11.04 system:

  logrotate --force --verbose /etc/logrotate.conf

  gives:

  rotating pattern: /var/log/syslog
   forced from command line (7 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/syslog
log /var/log/syslog does not exist -- skipping
  not running postrotate script, since no logs were rotated

  rotating pattern: /var/log/mail.info
  /var/log/mail.warn
  /var/log/mail.err
  /var/log/mail.log
  /var/log/daemon.log
  /var/log/kern.log
  /var/log/auth.log
  /var/log/user.log
  /var/log/lpr.log
  /var/log/cron.log
  /var/log/debug
  /var/log/messages
   forced from command line (4 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/mail.info
log /var/log/mail.info does not exist -- skipping
  considering log /var/log/mail.warn
log /var/log/mail.warn does not exist -- skipping
  considering log /var/log/mail.err
log does not need rotating
  considering log /var/log/mail.log
log does not need rotating
  considering log /var/log/daemon.log
log /var/log/daemon.log does not exist -- skipping
  considering log /var/log/kern.log
log /var/log/kern.log does not exist -- skipping
  considering log /var/log/auth.log
log /var/log/auth.log does not exist -- skipping
  considering log /var/log/user.log
log /var/log/user.log does not exist -- skipping
  considering log /var/log/lpr.log
log /var/log/lpr.log does not exist -- skipping
  considering log /var/log/cron.log
log /var/log/cron.log does not exist -- skipping
  considering log /var/log/debug
log /var/log/debug does not exist -- skipping
  considering log /var/log/messages
log /var/log/messages does not exist -- skipping
  not running postrotate script, since no logs were rotated

  Then
  /sbin/reload rsyslog
  logger -i testing

  At this point there is no /var/log/syslog

  Then:
  /sbin/restart rsyslog

  And voila there is a /var/log/syslog beginning with:

  Feb 23 19:24:48 somehost kernel: imklog 4.6.4, log source = /proc/kmsg 
started.
  Feb 23 19:24:48 somehost rsyslogd: [origin software="rsyslogd" 
swVersion="4.6.4" x-pid="2299" x-info="http://www.rsyslog.com;] (re)start
  Feb 23 19:24:48 somehost rsyslogd: rsyslogd's groupid changed to 114
  Feb 23 19:24:48 somehost rsyslogd: rsyslogd's userid changed to 108

  Then to recreate:

  logrotate --force --verbose /etc/logrotate.conf

  
  rotating pattern: /var/log/syslog
   forced from command line (7 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/syslog
log needs rotating
  rotating log /var/log/syslog, log->rotateCount is 7
  dateext suffix '-20120223'
  glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
  compressing log with: /bin/gzip
  renaming /var/log/syslog to /var/log/syslog-20120223
  running postrotate script
  removing old log /var/log/syslog-20111219.gz

  rotating pattern: /var/log/mail.info
  /var/log/mail.warn
  /var/log/mail.err
  /var/log/mail.log
  /var/log/daemon.log
  /var/log/kern.log
  /var/log/auth.log
  /var/log/user.log
  /var/log/lpr.log
  /var/log/cron.log
  /var/log/debug
  /var/log/messages
   forced from command line (4 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/mail.info
log /var/log/mail.info does not exist -- skipping
  considering log /var/log/mail.warn
log /var/log/mail.warn does not exist -- skipping
  considering log /var/log/mail.err
log does not need rotating
  considering log /var/log/mail.log
log does not need rotating
  considering log /var/log/daemon.log
log /var/log/daemon.log does not exist -- skipping
  considering log /var/log/kern.log
log needs rotating
  considering log /var/log/auth.log
 

[Touch-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

[Steve Langasek]

** Tags removed: rls-bb-incoming

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial), please disable LLMNR

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged
Status in glibc source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Triaged

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Touch-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

[Steve Langasek]

** Also affects: apport (Ubuntu Bionic)
   Importance: High
   Status: Triaged

** Tags removed: rls-bb-incoming

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files). This issue was first mentioned in bug 1746653. But
  then I noticed my machine doing it too...

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial), please disable LLMNR

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged
Status in glibc source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Triaged

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Touch-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

[Steve Langasek]

** Also affects: glibc (Ubuntu Bionic)
   Importance: Undecided
   Status: Invalid

** Also affects: linux (Ubuntu Bionic)
   Importance: High
   Status: Invalid

** Also affects: systemd (Ubuntu Bionic)
   Importance: High
   Status: Triaged

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial), please disable LLMNR

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged
Status in glibc source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Triaged

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

-- 
Mailing list: https://launchpad.net/~touch-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] Re: ubuntu-bug does not permit filing bug reports against Ubuntu-managed kernels

[Brian Murray]

Could you please add the output of 'apt-cache policy linux-
image-3.2.0-132-virtual'?  Thanks in advance.

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

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

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

Status in apport package in Ubuntu:
  Incomplete

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 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

[Denis Franco]

@bjbrewster I'm following the patch applying tutorial from here
https://superuser.com/questions/154717/how-to-apply-patch-to-gnome-on-
ubuntu/175743

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

Title:
  NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were 
created by Docker.
  Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged 
under the gnome system tray icon which is kind of annoying.
  I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun May 24 14:22:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-08-29 (632 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
  IpRoute:
   default via 192.168.178.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.42.1 
   192.168.178.0/24 dev wlan0  proto kernel  scope link  src 192.168.178.40
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-08-19T11:46:06.705439
  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/hundredpapercuts/+bug/1458322/+subscriptions

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

[Touch-packages] [Bug 1748216] [NEW] package python-dbus 1.2.0-3 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configure

[Guillaume Vignal]

Public bug reported:

A chaque mise à jour, ce message d'erreur s'affiche.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-dbus 1.2.0-3
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Thu Feb  8 16:19:56 2018
ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  le 
réinstaller avant de tenter de le configurer.
InstallationDate: Installed on 2017-05-19 (264 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: dbus-python
Title: package python-dbus 1.2.0-3 failed to install/upgrade: le paquet est 
dans un état vraiment incohérent; vous devriez  le réinstaller avant de tenter 
de le configurer.
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: dbus-python (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package python-dbus 1.2.0-3 failed to install/upgrade: le paquet est
  dans un état vraiment incohérent; vous devriez  le réinstaller avant
  de tenter de le configurer.

Status in dbus-python package in Ubuntu:
  New

Bug description:
  A chaque mise à jour, ce message d'erreur s'affiche.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-dbus 1.2.0-3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Feb  8 16:19:56 2018
  ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  InstallationDate: Installed on 2017-05-19 (264 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: dbus-python
  Title: package python-dbus 1.2.0-3 failed to install/upgrade: le paquet est 
dans un état vraiment incohérent; vous devriez  le réinstaller avant de tenter 
de le configurer.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1636395] Re: dnsmasq not working with OpenVPN

[Radhwane Chebaane]

Thanks @Nicholas, that fixed the issue for me.

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

Title:
  dnsmasq not working with OpenVPN

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in openvpn-systemd-resolved package in Ubuntu:
  Confirmed

Bug description:
  I'm using OpenVPN configured with Network Manager. My VPN have a DNS
  server configured by OpenVPN and config pushed by it while connecting.
  This server is not registered by dnsmasq so domain names are not
  resolved but pinging by IP address works. When I test name resolving
  by pointing to DNS server (172.16.1.1) from VPN provider it's works.
  For example:

  $ host google.com 172.16.1.1
  Using domain server:
  Name: 172.16.1.1
  Address: 172.16.1.1#53
  Aliases: 

  google.com has address 172.217.0.174
  google.com has IPv6 address 2607:f8b0:400b:807::200e
  google.com mail is handled by 30 alt2.aspmx.l.google.com.
  google.com mail is handled by 20 alt1.aspmx.l.google.com.
  google.com mail is handled by 40 alt3.aspmx.l.google.com.
  google.com mail is handled by 10 aspmx.l.google.com.
  google.com mail is handled by 50 alt4.aspmx.l.google.com.

  But if I test without pointing DNS server is not working:

  $ host google.com
  ;; connection timed out; no servers could be reached

  My /etc/resolv.conf:
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 127.0.1.1

  To repair this bug I have to kill dnsmasq and it's automatically
  reloaded.

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

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

[Touch-packages] [Bug 1714667] Re: please add old hungarian letters

[kixidevel]

** Attachment added: "Old Hungarian Regular Italic patch"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1714667/+attachment/5051291/+files/Csaba-RI.ttf

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

Title:
  please add old hungarian letters

Status in ubuntu-font-family-sources package in Ubuntu:
  Confirmed

Bug description:
  Old Hungarian letters (U10c80-U10cff) missing from font-families

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1714667/+subscriptions

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

[Touch-packages] [Bug 1714667] Re: please add old hungarian letters

[kixidevel]

** Attachment added: "Old Hungarian Bold Italic patch"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1714667/+attachment/5051293/+files/Csaba-BI.ttf

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

Title:
  please add old hungarian letters

Status in ubuntu-font-family-sources package in Ubuntu:
  Confirmed

Bug description:
  Old Hungarian letters (U10c80-U10cff) missing from font-families

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1714667/+subscriptions

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

[Touch-packages] [Bug 1714667] Re: please add old hungarian letters

[kixidevel]

** Attachment added: "Old Hungarian Bold patch"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1714667/+attachment/5051292/+files/Csaba-B.ttf

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

Title:
  please add old hungarian letters

Status in ubuntu-font-family-sources package in Ubuntu:
  Confirmed

Bug description:
  Old Hungarian letters (U10c80-U10cff) missing from font-families

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1714667/+subscriptions

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

[Touch-packages] [Bug 1714667] Re: please add old hungarian letters

[kixidevel]

Here is the Regular version final.

** Attachment added: "Old Hungarian Regular version"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1714667/+attachment/5051290/+files/Csaba-Regular.ttf

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

Title:
  please add old hungarian letters

Status in ubuntu-font-family-sources package in Ubuntu:
  Confirmed

Bug description:
  Old Hungarian letters (U10c80-U10cff) missing from font-families

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1714667/+subscriptions

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

[Touch-packages] [Bug 1748203] Re: package libhogweed4:i386 3.2-1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting conf

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libhogweed4:i386 3.2-1ubuntu0.16.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in nettle package in Ubuntu:
  New

Bug description:
  Every time I switch on my PC this pops up.
  Please repair it ASAP.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libhogweed4:i386 3.2-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun Feb  4 16:37:01 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
   libgmp10 2:6.1.0+dfsg-2
   libnettle6 3.2-1ubuntu0.16.04.1
  DuplicateSignature:
   package:libhogweed4:i386:3.2-1ubuntu0.16.04.1
   Setting up libc6-dev:amd64 (2.23-0ubuntu10) ...
   dpkg: error processing package libhogweed4:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-08-28 (164 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: nettle
  Title: package libhogweed4:i386 3.2-1ubuntu0.16.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1748203] [NEW] package libhogweed4:i386 3.2-1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting co

[Purvesh Rajendra Jain]

Public bug reported:

Every time I switch on my PC this pops up.
Please repair it ASAP.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libhogweed4:i386 3.2-1ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sun Feb  4 16:37:01 2018
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu10
 libgcc1 1:6.0.1-0ubuntu1
 libgmp10 2:6.1.0+dfsg-2
 libnettle6 3.2-1ubuntu0.16.04.1
DuplicateSignature:
 package:libhogweed4:i386:3.2-1ubuntu0.16.04.1
 Setting up libc6-dev:amd64 (2.23-0ubuntu10) ...
 dpkg: error processing package libhogweed4:i386 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-08-28 (164 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: nettle
Title: package libhogweed4:i386 3.2-1ubuntu0.16.04.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package libhogweed4:i386 3.2-1ubuntu0.16.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in nettle package in Ubuntu:
  New

Bug description:
  Every time I switch on my PC this pops up.
  Please repair it ASAP.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libhogweed4:i386 3.2-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun Feb  4 16:37:01 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
   libgmp10 2:6.1.0+dfsg-2
   libnettle6 3.2-1ubuntu0.16.04.1
  DuplicateSignature:
   package:libhogweed4:i386:3.2-1ubuntu0.16.04.1
   Setting up libc6-dev:amd64 (2.23-0ubuntu10) ...
   dpkg: error processing package libhogweed4:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-08-28 (164 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: nettle
  Title: package libhogweed4:i386 3.2-1ubuntu0.16.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1727237] Re: systemd-resolved is not finding a domain

[Axel]

@Mathieu,
Were the logs I sent you of any value to you for the debugging?

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

Title:
  systemd-resolved is not finding a domain

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Xenial:
  Triaged
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Triaged
Status in systemd source package in Bionic:
  Triaged

Bug description:
  I have an odd network situation that I have so far managed to narrow
  down to the inability to resolve a domain via systemd-resolved which
  is resolvable with nslookup. If I use nslookup against the two
  nameservers on this network I get answers for the domain, but ping
  says it is unable to resolve the same domain (as do browsers and
  crucially the captive portal mechanism).

  Here are details:

  NSLOOKUP:

  ~$ nslookup securelogin.arubanetworks.com 208.67.220.220
  Server:   208.67.220.220
  Address:  208.67.220.220#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  ~$ nslookup securelogin.arubanetworks.com 208.67.222.222
  Server:   208.67.222.222
  Address:  208.67.222.222#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  
  PING:

  ~$ ping securelogin.arubanetworks.com
  ping: securelogin.arubanetworks.com: Name or service not known
  mark@mark-X1Y2:~$ 

  
  DIG:

  ~$ dig @208.67.222.222 securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; AUTHORITY SECTION:
  arubanetworks.com.1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400

  ;; Query time: 34 msec
  ;; SERVER: 208.67.222.222#53(208.67.222.222)
  ;; WHEN: Wed Oct 25 10:31:10 CEST 2017
  ;; MSG SIZE  rcvd: 144

  
  MORE DIG:

  ~$ dig securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 25 10:34:01 CEST 2017
  ;; MSG SIZE  rcvd: 58

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

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

[Touch-packages] [Bug 1746771] Re: black background drop-down menu

[csola48]

Currently this mesa version is:
OpenGL version string: 4.5.0 NVIDIA 384.111
medium version: 17.2.4-0Ubuntu1 ~ 16.04.4
They are in the PPA store before, but I do not know how compatible my signaling 
system was when I guessed the reason for two weeks after the previous update 
...?
Another point is that it is not normal to overwrite the gnome for a download 
update  (?!)

see:
https://imgur.com/lPyU9T0

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

Title:
  black background drop-down menu

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  The internal drop-down menu for each program is unavailable because
  the text is only visible when I go above the mouse pointer.

  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  kernel: 4.4.113-0404113-lowlatency

  OpenGL version string: 4.5.0 NVIDIA 384.111
  medium version: 17.2.4-0Ubuntu1 ~ 16.04.4
  The very confusing operation - the menu items are not visible! - It was most 
likely that the mesa package was upgraded at the end of January.
  https://i.imgur.com/VNKlTkq.png
  https://i.imgur.com/sBIVQho.png
  https://i.imgur.com/6FdYPcj.png
  https://i.imgur.com/1RGXOlM.png
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1730793] Re: Translations not imported from upstream

[Launchpad Bug Tracker]

This bug was fixed in the package util-linux - 2.30.2-0.1ubuntu2

---
util-linux (2.30.2-0.1ubuntu2) bionic; urgency=medium

  * No change rebuild to try to resolve an outdated translations issue,
the package was configured on launchpad to share its strings with an
upstream vcs but the corresponding import is failing for some years.
We are trying to go back to use the source package translations
instead now (lp: #1730793)

 -- Sebastien Bacher   Wed, 07 Feb 2018 12:25:02
+0100

** Changed in: util-linux (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Translations not imported from upstream

Status in Ubuntu Translations:
  New
Status in util-linux package in Ubuntu:
  Fix Released

Bug description:
  The listing of Ubuntu source package translations (for Danish) reveals
  that the last import of translations for util-linux happened in 2011:

  
https://translations.launchpad.net/ubuntu/artful/+lang/da/+index?batch=300=300=300

  The Ubuntu source package version is 2.30, which appears to be from
  2017 (on my Ubuntu 16.04 it is 2.27 which is also relatively new).
  Either way it should have imported the translations from 2017.  Indeed
  util-linux has been translated very well in Danish for quite a few
  years:

  https://translationproject.org/domain/util-linux.html

  More precisely, 4000 translations are available and they have not been
  imported for (apparently) 6 years, leaving Danish at the level of 600
  strings.

  I suspect this is not really an issue with the util-linux source
  package, but rather with the whole Ubuntu/Launchpad translations
  workflow.  I can see that several packages have similar problems, and
  that is probably just the tip of the iceberg.  Unfortunately I have no
  clue how to approach that - at least I cannot file a bug report
  against The Whole Thing.  So if someone could speak to someone who
  could speak to someone who can actually get this to work, it would
  also be extremely good.

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

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

[Touch-packages] [Bug 1574354] Re: playing .mp4 in VLC freezes machine

[Michael]

@mahen I can confirm, logging in through ssh and issuing 'killall -9
vlc' unfreezes the desktop after a few seconds.

Jumping back and forth in  the video timeline really encourages a total
freeze.


DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=18.3
DISTRIB_CODENAME=sylvia
DISTRIB_DESCRIPTION="Linux Mint 18.3 Sylvia"
NAME="Linux Mint"
VERSION="18.3 (Sylvia)"
ID=linuxmint
ID_LIKE=ubuntu
PRETTY_NAME="Linux Mint 18.3"
VERSION_ID="18.3"
HOME_URL="http://www.linuxmint.com/;
SUPPORT_URL="http://forums.linuxmint.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/linuxmint/;
VERSION_CODENAME=sylvia
UBUNTU_CODENAME=xenial

00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 
07)
00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16) (rev 07)
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev f1)
00:1b.3 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #20 (rev f1)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 
(rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 
(rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V 
(rev 31)
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b80 (rev a1)
01:00.1 Audio device: NVIDIA Corporation Device 10f0 (rev a1)
03:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller 
(rev 02)
04:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller

i7-6700K
Nvidia GTX 1080 with 387.34-0ubuntu0~gpu16.04.2 via 
http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu xenial/main amd64

VLC media player 2.2.2 Weatherwax (revision 2.2.2-0-g6259d80)

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

Title:
  playing .mp4 in VLC freezes machine

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  VLC was running fine on 15.10 but since upgrading, video files (e.g.
  .mp4) play for a few minutes and then crash the whole machine (i.e. I
  have to power off and on). Possibly linked is that audio (in web pages
  or playing audio files thru Banshee) loops (stutters) for about a
  second every few minutes (but doesn't crash the machine).

  vlc-nox: /usr/bin/vlc

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  vlc:
Installed: 2.2.2-5
Candidate: 2.2.2-5
Version table:
   *** 2.2.2-5 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: vlc 2.2.2-5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 24 19:20:41 2016
  InstallationDate: Installed on 2014-02-17 (797 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: vlc
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

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

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

[Touch-packages] [Bug 1747814] Re: Snapped applications using ubuntu launcher integration needs desktop update

[Treviño]

Hi Lukasz,

While for bug #1747802 this would indeed make sense, for this specific
not really, since this affects mostly the snapcrafter's (as these fixes
will apply to apps running inside snaps built in a xenial-based distro),
and snapcraft isn't supporting artful anyway.

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

Title:
  Snapped applications using ubuntu launcher integration needs desktop
  update

Status in libunity package in Ubuntu:
  Fix Released
Status in libunity source package in Xenial:
  Fix Committed

Bug description:
  [ Impact ]

  Launching a snapped application with ubuntu launcher icon integration
  doesn't properly work as the desktop ID does not use the proper
  namespace.

  Also, a snapped app could decorate other apps outside the snap scope.

  [ Test case ]

  git clone https://github.com/3v1n0/ubuntu-launcher-integration-snap.git
  cd ubuntu-launcher-integration-snap
  snapcraft prime
  snap try prime

  Then launch those (you might do it from dash/activities to get proper 
matching):
   ubuntu-launcher-integration-snap.ubuntu-launcher
   ubuntu-launcher-integration-snap.ubuntu-launcher-2nd
   ubuntu-launcher-integration-snap.ubuntu-launcher-hardcoded

  All these apps should get an icon in the launcher with emblems (of
  different values when they're launched together).

  [ Regression potential ]

  Application with SNAP environments could point to wrong desktop-file
  to decorate

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

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

[Touch-packages] [Bug 1562661] Re: pulseaudio crashed with SIGSEGV in pa_hashmap_remove_all() from pa_hashmap_free() from pa_modargs_free() from module_bluez5_discover_LTX_pa__done() from module_bluez

[Ulf Pretscheck]

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

Title:
  pulseaudio crashed with SIGSEGV in pa_hashmap_remove_all() from
  pa_hashmap_free() from pa_modargs_free() from
  module_bluez5_discover_LTX_pa__done() from
  module_bluez5_discover_LTX_pa__init()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/f25f4c78f4ef773f8f3beff66c6779af2927d9f3

  ---

  It occurred in new branch, so submit it again.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jizhang1755 F pulseaudio
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Mar 28 09:43:37 2016
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  SegvAnalysis:
   Segfault happened at: 0x7fbf00fd96a3 : mov
0x8(%rsi),%rbp
   PC (0x7fbf00fd96a3) ok
   source "0x8(%rsi)" (0x7272452e7375424c) not located in a known VMA region 
(needed readable region)!
   destination "%rbp" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_hashmap_remove_all () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
   pa_hashmap_free () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
   pa_modargs_free () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   module_bluez5_discover_LTX_pa__done () from 
/usr/lib/pulse-8.0/modules/module-bluez5-discover.so
   module_bluez5_discover_LTX_pa__init () from 
/usr/lib/pulse-8.0/modules/module-bluez5-discover.so
  Title: pulseaudio crashed with SIGSEGV in pa_hashmap_remove_all()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin audio cdrom dialout kvm libvirtd lpadmin plugdev pulse 
sambashare video
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: None
  dmi.board.name: TH61
  dmi.board.vendor: BIOSTAR Group
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd05/11/2012:svnBIOSTARGroup:pnTH61:pvr6.0:rvnBIOSTARGroup:rnTH61:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0:
  dmi.product.name: TH61
  dmi.product.version: 6.0
  dmi.sys.vendor: BIOSTAR Group

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

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

[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.8

---
apparmor (2.10.95-0ubuntu2.8) xenial; urgency=medium

  * d/p/0001-Allow-seven-digit-pid.patch:
On 64bit systems, /proc/sys/kernel/pid_max can be set to PID_MAX_LIMIT,
(2^22), which results in seven digit pids. Adjust the @{PID} variable in
tunables/global to accept this. (LP: #1717714)

 -- Seyeong Kim   Mon, 08 Jan 2018 07:43:46
-0800

** Changed in: apparmor (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  @{pid} variable broken on systems with pid_max more than 6 digits

Status in AppArmor:
  Fix Committed
Status in AppArmor 2.11 series:
  Fix Committed
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Trusty:
  Fix Committed
Status in apparmor source package in Xenial:
  Fix Released
Status in apparmor source package in Artful:
  Fix Released
Status in apparmor source package in Bionic:
  Fix Released
Status in apparmor package in Debian:
  Fix Released

Bug description:
  [Impact]

  If PID is larger than 6 digits apparmor denies process which only
  affect 64-bit systems[1] where the PID_MAX_LIMIT can be generated up
  to 7 digits at the maximum.

  This fix is committed, but not released. so all supporting version are
  affected.

  [1] - man 5 proc

  --
  /proc/sys/kernel/pid_max (since Linux 2.5.34)
  This file specifies the value at which PIDs wrap around (i.e., the value in 
this file is one greater than the maximum PID).  PIDs greater than this value 
are not allocated;  thus,  the value  in this file also acts as a system-wide 
limit on the total number of processes and threads.  The default value for this 
file, 32768, results in the same range of PIDs as on ear‐lier kernels.  On 
32-bit platforms, 32768 is the maximum value for pid_max.  On 64-bit systems, 
pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4 
million).
  --

  [Test Case]

  1. making pid over 6 digits
  #!/bin/bash

  for i in {1..100}
  do
    touch t
  done

  2. snap install --dangerous core_16-2.29.4.2_amd64.snap ( snap core
  16-2.30 avoids using /proc/PID/cmdline, so need to use older version

  3. you can see DENIED msgs in syslog

  4. change /etc/apparmor.d/tunables/kernelvars
  5. service apparmor restart
  6. service snapd restart
  7. DENIED is gone

  This is one way, can't reproduce this issue again even if you change
  back to original kernelvars, and restart snapd

  OR

  instead of Seyeong's touch approach, things can be manually change to
  7 digits range via sysctl as long as the values are below
  approximately 4 millions :

  Example:
  $ sysctl -w kernel.pid_max=300
  $ sysctl -w kernel.ns_last_pid=100

  [Regression]
  * This is a minor/trivial fix which changes the pid regex only, allowing 7 
digits PID instead of only 6 digits PID, we don't think there is any potential 
regression.

  * If a regression arise, which we highly doubt, one can quickly revert
  the change manually and restart the service by modifying
  "/etc/apparmor.d/tunables/kernelvars" file to its original state
  (before this SRU).

  [Others]

  * Upstream commit:
   
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
  http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722

  * Debian bug:
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886732

  * commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
  Author: Vincas Dargis 
  Date:   Sat Sep 30 15:28:15 2017 +0300

  Allow seven digit pid

  * Affecting releases : TXZAB
  --
  $ git describe --contains 630cb2a9
  v2.11.95~5^2

  $ rmadison apparmor
   apparmor | 2.8.95~2430-0ubuntu5   | trusty
   apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
   apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
   apparmor | 2.10.95-0ubuntu2   | xenial
   apparmor | 2.10.95-0ubuntu2.6 | xenial-security
   apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
   apparmor | 2.11.0-2ubuntu4| zesty
   apparmor | 2.11.0-2ubuntu17   | artful
   apparmor | 2.11.0-2ubuntu18   | bionic

  $ rmadison -u debian apparmor
   apparmor | 2.11.1-4   | unstable
  --

  [Original Description]

  If your kernel.pid_max sysctl is set higher than the default, say at 7
  digits, the @{pid} variable no longer matches all pids, causing some
  breakage in any profile using it.

  @{pid} is 

[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.11.0-2ubuntu17.1

---
apparmor (2.11.0-2ubuntu17.1) artful; urgency=medium

  * d/p/0001-Allow-seven-digit-pid.patch:
On 64bit systems, /proc/sys/kernel/pid_max can be set to PID_MAX_LIMIT,
(2^22), which results in seven digit pids. Adjust the @{PID} variable in
tunables/global to accept this. (LP: #1717714)

 -- Seyeong Kim   Mon, 08 Jan 2018 07:49:55
-0800

** Changed in: apparmor (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  @{pid} variable broken on systems with pid_max more than 6 digits

Status in AppArmor:
  Fix Committed
Status in AppArmor 2.11 series:
  Fix Committed
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Trusty:
  Fix Committed
Status in apparmor source package in Xenial:
  Fix Released
Status in apparmor source package in Artful:
  Fix Released
Status in apparmor source package in Bionic:
  Fix Released
Status in apparmor package in Debian:
  Fix Released

Bug description:
  [Impact]

  If PID is larger than 6 digits apparmor denies process which only
  affect 64-bit systems[1] where the PID_MAX_LIMIT can be generated up
  to 7 digits at the maximum.

  This fix is committed, but not released. so all supporting version are
  affected.

  [1] - man 5 proc

  --
  /proc/sys/kernel/pid_max (since Linux 2.5.34)
  This file specifies the value at which PIDs wrap around (i.e., the value in 
this file is one greater than the maximum PID).  PIDs greater than this value 
are not allocated;  thus,  the value  in this file also acts as a system-wide 
limit on the total number of processes and threads.  The default value for this 
file, 32768, results in the same range of PIDs as on ear‐lier kernels.  On 
32-bit platforms, 32768 is the maximum value for pid_max.  On 64-bit systems, 
pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4 
million).
  --

  [Test Case]

  1. making pid over 6 digits
  #!/bin/bash

  for i in {1..100}
  do
    touch t
  done

  2. snap install --dangerous core_16-2.29.4.2_amd64.snap ( snap core
  16-2.30 avoids using /proc/PID/cmdline, so need to use older version

  3. you can see DENIED msgs in syslog

  4. change /etc/apparmor.d/tunables/kernelvars
  5. service apparmor restart
  6. service snapd restart
  7. DENIED is gone

  This is one way, can't reproduce this issue again even if you change
  back to original kernelvars, and restart snapd

  OR

  instead of Seyeong's touch approach, things can be manually change to
  7 digits range via sysctl as long as the values are below
  approximately 4 millions :

  Example:
  $ sysctl -w kernel.pid_max=300
  $ sysctl -w kernel.ns_last_pid=100

  [Regression]
  * This is a minor/trivial fix which changes the pid regex only, allowing 7 
digits PID instead of only 6 digits PID, we don't think there is any potential 
regression.

  * If a regression arise, which we highly doubt, one can quickly revert
  the change manually and restart the service by modifying
  "/etc/apparmor.d/tunables/kernelvars" file to its original state
  (before this SRU).

  [Others]

  * Upstream commit:
   
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
  http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722

  * Debian bug:
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886732

  * commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
  Author: Vincas Dargis 
  Date:   Sat Sep 30 15:28:15 2017 +0300

  Allow seven digit pid

  * Affecting releases : TXZAB
  --
  $ git describe --contains 630cb2a9
  v2.11.95~5^2

  $ rmadison apparmor
   apparmor | 2.8.95~2430-0ubuntu5   | trusty
   apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
   apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
   apparmor | 2.10.95-0ubuntu2   | xenial
   apparmor | 2.10.95-0ubuntu2.6 | xenial-security
   apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
   apparmor | 2.11.0-2ubuntu4| zesty
   apparmor | 2.11.0-2ubuntu17   | artful
   apparmor | 2.11.0-2ubuntu18   | bionic

  $ rmadison -u debian apparmor
   apparmor | 2.11.1-4   | unstable
  --

  [Original Description]

  If your kernel.pid_max sysctl is set higher than the default, say at 7
  digits, the @{pid} variable no longer matches all pids, causing some
  breakage in any profile using it.

  @{pid} is 

[Touch-packages] [Bug 1717714] Update Released

[Łukasz Zemczak]

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

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

Title:
  @{pid} variable broken on systems with pid_max more than 6 digits

Status in AppArmor:
  Fix Committed
Status in AppArmor 2.11 series:
  Fix Committed
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Trusty:
  Fix Committed
Status in apparmor source package in Xenial:
  Fix Released
Status in apparmor source package in Artful:
  Fix Released
Status in apparmor source package in Bionic:
  Fix Released
Status in apparmor package in Debian:
  Fix Released

Bug description:
  [Impact]

  If PID is larger than 6 digits apparmor denies process which only
  affect 64-bit systems[1] where the PID_MAX_LIMIT can be generated up
  to 7 digits at the maximum.

  This fix is committed, but not released. so all supporting version are
  affected.

  [1] - man 5 proc

  --
  /proc/sys/kernel/pid_max (since Linux 2.5.34)
  This file specifies the value at which PIDs wrap around (i.e., the value in 
this file is one greater than the maximum PID).  PIDs greater than this value 
are not allocated;  thus,  the value  in this file also acts as a system-wide 
limit on the total number of processes and threads.  The default value for this 
file, 32768, results in the same range of PIDs as on ear‐lier kernels.  On 
32-bit platforms, 32768 is the maximum value for pid_max.  On 64-bit systems, 
pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4 
million).
  --

  [Test Case]

  1. making pid over 6 digits
  #!/bin/bash

  for i in {1..100}
  do
    touch t
  done

  2. snap install --dangerous core_16-2.29.4.2_amd64.snap ( snap core
  16-2.30 avoids using /proc/PID/cmdline, so need to use older version

  3. you can see DENIED msgs in syslog

  4. change /etc/apparmor.d/tunables/kernelvars
  5. service apparmor restart
  6. service snapd restart
  7. DENIED is gone

  This is one way, can't reproduce this issue again even if you change
  back to original kernelvars, and restart snapd

  OR

  instead of Seyeong's touch approach, things can be manually change to
  7 digits range via sysctl as long as the values are below
  approximately 4 millions :

  Example:
  $ sysctl -w kernel.pid_max=300
  $ sysctl -w kernel.ns_last_pid=100

  [Regression]
  * This is a minor/trivial fix which changes the pid regex only, allowing 7 
digits PID instead of only 6 digits PID, we don't think there is any potential 
regression.

  * If a regression arise, which we highly doubt, one can quickly revert
  the change manually and restart the service by modifying
  "/etc/apparmor.d/tunables/kernelvars" file to its original state
  (before this SRU).

  [Others]

  * Upstream commit:
   
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
  http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722

  * Debian bug:
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886732

  * commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
  Author: Vincas Dargis 
  Date:   Sat Sep 30 15:28:15 2017 +0300

  Allow seven digit pid

  * Affecting releases : TXZAB
  --
  $ git describe --contains 630cb2a9
  v2.11.95~5^2

  $ rmadison apparmor
   apparmor | 2.8.95~2430-0ubuntu5   | trusty
   apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
   apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
   apparmor | 2.10.95-0ubuntu2   | xenial
   apparmor | 2.10.95-0ubuntu2.6 | xenial-security
   apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
   apparmor | 2.11.0-2ubuntu4| zesty
   apparmor | 2.11.0-2ubuntu17   | artful
   apparmor | 2.11.0-2ubuntu18   | bionic

  $ rmadison -u debian apparmor
   apparmor | 2.11.1-4   | unstable
  --

  [Original Description]

  If your kernel.pid_max sysctl is set higher than the default, say at 7
  digits, the @{pid} variable no longer matches all pids, causing some
  breakage in any profile using it.

  @{pid} is defined in /etc/apparmor.d/tunables:
  

[Touch-packages] [Bug 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value

[Dimitri John Ledkov]

Zesty is end of life.

** Changed in: procps (Ubuntu Zesty)
   Status: New => Won't Fix

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

Title:
  virsh start of virtual guest domain fails with internal error due to
  low default aio-max-nr sysctl value

Status in Ubuntu on IBM z Systems:
  In Progress
Status in kvm package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  In Progress
Status in procps package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress
Status in procps source package in Xenial:
  New
Status in linux source package in Zesty:
  Won't Fix
Status in procps source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress
Status in procps source package in Artful:
  New

Bug description:
  Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its
  KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with
  the following error:

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038
  error: Failed to start domain zs93kag70038
  error: internal error: process exited while connecting to monitor: 
2017-07-26T01:48:26.352534Z qemu-kvm: -drive 
file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native:
 Could not open backing file: Could not set AIO state: Inappropriate ioctl for 
device

  The previous 17 guests started fine:

  root@zm93k8# virsh start zs93kag70020
  Domain zs93kag70020 started

  root@zm93k8# virsh start zs93kag70021
  Domain zs93kag70021 started

  .
  .

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  We ended up fixing the issue by adding the following line to /etc/sysctl.conf 
: 

  fs.aio-max-nr = 4194304

  ... then, reload the sysctl config file:

  root@zm93k8:/etc# sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 4194304

  
  Now, we're able to start more guests...

  root@zm93k8:/etc# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  The default value was originally set to 65535: 

  root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr
  65536

  
  Note, we chose the 4194304 value, because this is what our KVM on System Z 
hypervisor ships as its default value.  Eg.  on our zKVM system: 

  [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr
  4194304

  ubuntu@zm93k8:/etc$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial
  ubuntu@zm93k8:/etc$

  ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version
  Version: 1:2.5+dfsg-5ubuntu10.8

  Is something already documented for Ubuntu KVM users warning them about the 
low default value, and some guidance as to
  how to select an appropriate value?   Also, would you consider increasing the 
default aio-max-nr value to something much
  higher, to accommodate significantly more virtual guests?  

  Thanks!

  ---uname output---
  ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed 
Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux
   
  Machine Type = z14 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   See Problem Description.

  The problem was happening a week ago, so this may not reflect that
  activity.

  This file was collected on Aug 7, one week after we were hitting the
  problem.  If I need to reproduce the problem and get fresh data,
  please let me know.

  /var/log/messages doesn't exist on this system, so I provided syslog
  output instead.

  All data have been collected too late after the problem was observed
  over a week ago.  If you need me to reproduce the problem and get new
  data, please let me know.  That's not a problem.

  Also, we would have to make special arrangements for login access to
  these systems.  I'm happy to run traces and data collection for you as
  needed.  If that's not sufficient, then we'll explore log in access
  for you.

  Thanks...   - Scott G.

  
  I was able to successfully recreate the problem and captured / attached new 
debug docs. 

  Recreate procedure:

  #  Started out with no virtual guests running.

  ubuntu@zm93k8:/home/scottg$ virsh list
   IdName   State
  

  
  # Set fs.aio-max-nr back to original Ubuntu "out of the box" value in 
/etc/sysctl.conf

  ubuntu@zm93k8:~$ tail -1 /etc/sysctl.conf
  fs.aio-max-nr = 65536

  
  ## sysctl -a shows: 

  fs.aio-max-nr = 4194304

  
  ##  Reload sysctl.

  ubuntu@zm93k8:~$ sudo sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 65536
  ubuntu@zm93k8:~$

  ubuntu@zm93k8:~$ sudo sysctl -a |grep fs.aio-max-nr
  fs.aio-max-nr = 65536

  ubuntu@zm93k8:~$  cat /proc/sys/fs/aio-max-nr
  65536


  # Attempt to start more than 17 qcow2 virtual 

[Touch-packages] [Bug 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value

[Dimitri John Ledkov]

zesty is End Of Life

** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Won't Fix

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

Title:
  virsh start of virtual guest domain fails with internal error due to
  low default aio-max-nr sysctl value

Status in Ubuntu on IBM z Systems:
  In Progress
Status in kvm package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  In Progress
Status in procps package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress
Status in procps source package in Xenial:
  New
Status in linux source package in Zesty:
  Won't Fix
Status in procps source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress
Status in procps source package in Artful:
  New

Bug description:
  Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its
  KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with
  the following error:

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038
  error: Failed to start domain zs93kag70038
  error: internal error: process exited while connecting to monitor: 
2017-07-26T01:48:26.352534Z qemu-kvm: -drive 
file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native:
 Could not open backing file: Could not set AIO state: Inappropriate ioctl for 
device

  The previous 17 guests started fine:

  root@zm93k8# virsh start zs93kag70020
  Domain zs93kag70020 started

  root@zm93k8# virsh start zs93kag70021
  Domain zs93kag70021 started

  .
  .

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  We ended up fixing the issue by adding the following line to /etc/sysctl.conf 
: 

  fs.aio-max-nr = 4194304

  ... then, reload the sysctl config file:

  root@zm93k8:/etc# sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 4194304

  
  Now, we're able to start more guests...

  root@zm93k8:/etc# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  The default value was originally set to 65535: 

  root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr
  65536

  
  Note, we chose the 4194304 value, because this is what our KVM on System Z 
hypervisor ships as its default value.  Eg.  on our zKVM system: 

  [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr
  4194304

  ubuntu@zm93k8:/etc$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial
  ubuntu@zm93k8:/etc$

  ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version
  Version: 1:2.5+dfsg-5ubuntu10.8

  Is something already documented for Ubuntu KVM users warning them about the 
low default value, and some guidance as to
  how to select an appropriate value?   Also, would you consider increasing the 
default aio-max-nr value to something much
  higher, to accommodate significantly more virtual guests?  

  Thanks!

  ---uname output---
  ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed 
Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux
   
  Machine Type = z14 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   See Problem Description.

  The problem was happening a week ago, so this may not reflect that
  activity.

  This file was collected on Aug 7, one week after we were hitting the
  problem.  If I need to reproduce the problem and get fresh data,
  please let me know.

  /var/log/messages doesn't exist on this system, so I provided syslog
  output instead.

  All data have been collected too late after the problem was observed
  over a week ago.  If you need me to reproduce the problem and get new
  data, please let me know.  That's not a problem.

  Also, we would have to make special arrangements for login access to
  these systems.  I'm happy to run traces and data collection for you as
  needed.  If that's not sufficient, then we'll explore log in access
  for you.

  Thanks...   - Scott G.

  
  I was able to successfully recreate the problem and captured / attached new 
debug docs. 

  Recreate procedure:

  #  Started out with no virtual guests running.

  ubuntu@zm93k8:/home/scottg$ virsh list
   IdName   State
  

  
  # Set fs.aio-max-nr back to original Ubuntu "out of the box" value in 
/etc/sysctl.conf

  ubuntu@zm93k8:~$ tail -1 /etc/sysctl.conf
  fs.aio-max-nr = 65536

  
  ## sysctl -a shows: 

  fs.aio-max-nr = 4194304

  
  ##  Reload sysctl.

  ubuntu@zm93k8:~$ sudo sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 65536
  ubuntu@zm93k8:~$

  ubuntu@zm93k8:~$ sudo sysctl -a |grep fs.aio-max-nr
  fs.aio-max-nr = 65536

  ubuntu@zm93k8:~$  cat /proc/sys/fs/aio-max-nr
  65536


  # Attempt to start more than 17 qcow2 virtual 

[Touch-packages] [Bug 1746771] Re: black background drop-down menu

[dino99]

Could be a side effect of the mesa upgrading. As tags does not list 'proposed', 
can you confirm the 17.2.4 mesa version used ?
lp:1747744 

Might affect all the mesa greater than 17.2.3

** Tags added: artful bionic

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

Title:
  black background drop-down menu

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  The internal drop-down menu for each program is unavailable because
  the text is only visible when I go above the mouse pointer.

  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  kernel: 4.4.113-0404113-lowlatency

  OpenGL version string: 4.5.0 NVIDIA 384.111
  medium version: 17.2.4-0Ubuntu1 ~ 16.04.4
  The very confusing operation - the menu items are not visible! - It was most 
likely that the mesa package was upgraded at the end of January.
  https://i.imgur.com/VNKlTkq.png
  https://i.imgur.com/sBIVQho.png
  https://i.imgur.com/6FdYPcj.png
  https://i.imgur.com/1RGXOlM.png
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1747744] Re: [regression] Video playback in totem is corrupted in X11

[dino99]

An other similar issue on Xenial which probably use mesa 17.2.4 (proposed not 
enabled)
lp:1746771

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

Title:
  [regression] Video playback in totem is corrupted in X11

Status in Mesa:
  Confirmed
Status in clutter-gst-3.0 package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  Test case
  Log inti xorg session
  Install gstreamer1.0-vaapi plugin
  Play a supported video (- h.264/avc in .mp4, .mkv or .mov  would suffice

  Expected: hardware decoded playback
  What happens: totally corrupted screen, see screenshots

  Does work ok in a wayland session

  $ vainfo
  libva info: VA-API version 1.0.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.0 (libva 2.0.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  6 14:43:57 2018
  InstallationDate: Installed on 2018-02-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer-vaapi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1746771] Re: black background drop-down menu

[csola48]

This might be the solution --- at least the programs I use often in black 
background unreadable drop-down menus :)
You had to install and configure gtk-theme-config (1.2.1-0ubuntu1) (eg. 
https://imgur.com/XCnzSJr)

Unfortunately, I can not find the root cause, but it is sure that mesa
and nvidia update came in at once, after which it happened.

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

Title:
  black background drop-down menu

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  The internal drop-down menu for each program is unavailable because
  the text is only visible when I go above the mouse pointer.

  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  kernel: 4.4.113-0404113-lowlatency

  OpenGL version string: 4.5.0 NVIDIA 384.111
  medium version: 17.2.4-0Ubuntu1 ~ 16.04.4
  The very confusing operation - the menu items are not visible! - It was most 
likely that the mesa package was upgraded at the end of January.
  https://i.imgur.com/VNKlTkq.png
  https://i.imgur.com/sBIVQho.png
  https://i.imgur.com/6FdYPcj.png
  https://i.imgur.com/1RGXOlM.png
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1747814] Re: Snapped applications using ubuntu launcher integration needs desktop update

[Łukasz Zemczak]

I'm wondering if it makes sense to also get this released for artful?
Unity is not the default experience but the package is still available,
so in theory someone upgrading from xenial to artful and insisting on
staying with Unity as his shell might experience a regression.

What do you think? I'll accept it for now, but maybe it's worth
considering?

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

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

** Tags added: verification-needed verification-needed-xenial

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

Title:
  Snapped applications using ubuntu launcher integration needs desktop
  update

Status in libunity package in Ubuntu:
  Fix Released
Status in libunity source package in Xenial:
  Fix Committed

Bug description:
  [ Impact ]

  Launching a snapped application with ubuntu launcher icon integration
  doesn't properly work as the desktop ID does not use the proper
  namespace.

  Also, a snapped app could decorate other apps outside the snap scope.

  [ Test case ]

  git clone https://github.com/3v1n0/ubuntu-launcher-integration-snap.git
  cd ubuntu-launcher-integration-snap
  snapcraft prime
  snap try prime

  Then launch those (you might do it from dash/activities to get proper 
matching):
   ubuntu-launcher-integration-snap.ubuntu-launcher
   ubuntu-launcher-integration-snap.ubuntu-launcher-2nd
   ubuntu-launcher-integration-snap.ubuntu-launcher-hardcoded

  All these apps should get an icon in the launcher with emblems (of
  different values when they're launched together).

  [ Regression potential ]

  Application with SNAP environments could point to wrong desktop-file
  to decorate

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

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

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

[Łukasz Zemczak]

Hello Marco, or anyone else affected,

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

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

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

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

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

Title:
  Snapped applications using ubuntu launcher integration needs desktop
  update

Status in libunity package in Ubuntu:
  Fix Released
Status in libunity source package in Xenial:
  Fix Committed

Bug description:
  [ Impact ]

  Launching a snapped application with ubuntu launcher icon integration
  doesn't properly work as the desktop ID does not use the proper
  namespace.

  Also, a snapped app could decorate other apps outside the snap scope.

  [ Test case ]

  git clone https://github.com/3v1n0/ubuntu-launcher-integration-snap.git
  cd ubuntu-launcher-integration-snap
  snapcraft prime
  snap try prime

  Then launch those (you might do it from dash/activities to get proper 
matching):
   ubuntu-launcher-integration-snap.ubuntu-launcher
   ubuntu-launcher-integration-snap.ubuntu-launcher-2nd
   ubuntu-launcher-integration-snap.ubuntu-launcher-hardcoded

  All these apps should get an icon in the launcher with emblems (of
  different values when they're launched together).

  [ Regression potential ]

  Application with SNAP environments could point to wrong desktop-file
  to decorate

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

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

[Touch-packages] [Bug 1687015] Re: 229_4ubuntu17 removes group write permissions from /var/log

[Launchpad Bug Tracker]

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

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

Title:
  229_4ubuntu17 removes group write permissions from /var/log

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce (time senstive, once lxd image is updated with
  4ubuntu17, I expect this won't work)

  lxc launch ubuntu:x test
  lxc exec test -- ls -ld /var/log  # shows 775 perms
  lxc exec test -- apt update
  lxc exec test -- apt-cache policy systemd
  lxc exec test -- apt install systemd
  lxc exec test -- ls -ld /var/log  # shows 755 permissions

  straceing the apt install shows no chmod calls to /var/log (only
  /var/log/apt.log, as you'd expect)

  This means syslog cannot write new files in /var/log, and had broken
  some production logging for us as a result.

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

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

[Touch-packages] [Bug 1748147] Re: Upgrading systemd sets incorrect permissions on /var/log/

[Nick Groenen]

Related/similar issues: #1428540, #1687015

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

Title:
  Upgrading systemd sets incorrect permissions on /var/log/

Status in systemd package in Ubuntu:
  New

Bug description:
  Upgrading or reinstalling the systemd package when using rsyslogd
  results in bad permissions (0755 instead of 0775) being set on
  /var/log/. As a consequence of this, rsyslogd can no longer create new
  files within this directory, resulting in lost log messages.

  The default configuration of rsyslogd provided by Ubuntu runs the
  daemon as syslog:syslog and sets ownership of /var/log to syslog:adm
  with mode 0775.

  Systemd's default tmpfiles configuration sets /var/log to 0755 in
  /usr/lib/tmpfiles.d/var.conf, however this is overridden in
  /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package
  rsyslog.

  It looks as though an upgrade of the systemd package fails to take
  /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated
  below. This results in /var/log receiving mode 0755 instead of the
  expected 0775:

  
  nick @ log2.be1.ams1:~ $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  nick @ log2.be1.ams1:~ $ apt policy systemd
  systemd:
Installed: 229-4ubuntu21.1
Candidate: 229-4ubuntu21.1
Version table:
   *** 229-4ubuntu21.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  nick @ log2.be1.ams1:~ $ apt policy rsyslog
  rsyslog:
Installed: 8.16.0-1ubuntu3
Candidate: 8.16.0-1ubuntu3
Version table:
   *** 8.16.0-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf
  d /var/log 0755 - - -
  f /var/log/wtmp 0664 root utmp -
  f /var/log/btmp 0600 root utmp -

  nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf
  # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by
  # the syslog group, so that rsyslog can run as user.
  # See tmpfiles.d(5) for details.

  # Type PathMode UID  GID  Age Argument
  d /var/log 0775 root syslog -

  nick @ log2.be1.ams1:~ $ ls -ld /var/log
  drwxrwxr-x 8 root syslog 4096 Feb  7 13:45 /var/log

  nick @ log2.be1.ams1:~ $ sudo apt install --reinstall systemd
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 7 not upgraded.
  Need to get 3,634 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 systemd 
amd64 229-4ubuntu21.1 [3,634 kB]
  Fetched 3,634 kB in 0s (24.3 MB/s)
  (Reading database ... 86614 files and directories currently installed.)
  Preparing to unpack .../systemd_229-4ubuntu21.1_amd64.deb ...
  Unpacking systemd (229-4ubuntu21.1) over (229-4ubuntu21.1) ...
  Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up systemd (229-4ubuntu21.1) ...
  addgroup: The group `systemd-journal' already exists as a system group. 
Exiting.

  nick @ log2.be1.ams1:~ $ ls -ld /var/log
  drwxr-xr-x 8 root syslog 4096 Feb  7 13:45 /var/log

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

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

[Touch-packages] [Bug 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic

[Andrea Azzarone]

Any news on this?

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

Title:
  [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from
  bionic

Status in httmock package in Ubuntu:
  Fix Released
Status in protobuf package in Ubuntu:
  Fix Released
Status in py-macaroon-bakery package in Ubuntu:
  Fix Released
Status in pymacaroons package in Ubuntu:
  Fix Released
Status in httmock source package in Xenial:
  In Progress
Status in protobuf source package in Xenial:
  In Progress
Status in py-macaroon-bakery source package in Xenial:
  In Progress
Status in pymacaroons source package in Xenial:
  In Progress
Status in httmock source package in Artful:
  Invalid
Status in protobuf source package in Artful:
  Invalid
Status in py-macaroon-bakery source package in Artful:
  In Progress
Status in pymacaroons source package in Artful:
  In Progress

Bug description:
  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:

  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.

  [Test case]
  - for protobuf: $ python3 -c "import google.protobuf"
  - for protobuf: $ python2 -c "import google.protobuf"
  - for python3-macaroonbakery: make sure all the tests pass
  - make sure "snapcraft login" works properly

  [Regression Potential]
  - httmock, none has it's not in xenial
  - protobuf, reduced considering that the code has been backported from master 
(small changes to make it compatabile py3 compatabile)
  - pymacaroons, none has 0.12 is backward compatible with 0.9.2
  - py-macaroon-bakery, none has it's not in xenial.

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

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

[Touch-packages] [Bug 1748147] [NEW] Upgrading systemd sets incorrect permissions on /var/log/

[Nick Groenen]

Public bug reported:

Upgrading or reinstalling the systemd package when using rsyslogd
results in bad permissions (0755 instead of 0775) being set on
/var/log/. As a consequence of this, rsyslogd can no longer create new
files within this directory, resulting in lost log messages.

The default configuration of rsyslogd provided by Ubuntu runs the daemon
as syslog:syslog and sets ownership of /var/log to syslog:adm with mode
0775.

Systemd's default tmpfiles configuration sets /var/log to 0755 in
/usr/lib/tmpfiles.d/var.conf, however this is overridden in
/usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog.

It looks as though an upgrade of the systemd package fails to take
/usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below.
This results in /var/log receiving mode 0755 instead of the expected
0775:


nick @ log2.be1.ams1:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:   xenial

nick @ log2.be1.ams1:~ $ apt policy systemd
systemd:
  Installed: 229-4ubuntu21.1
  Candidate: 229-4ubuntu21.1
  Version table:
 *** 229-4ubuntu21.1 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
100 /var/lib/dpkg/status
 229-4ubuntu4 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

nick @ log2.be1.ams1:~ $ apt policy rsyslog
rsyslog:
  Installed: 8.16.0-1ubuntu3
  Candidate: 8.16.0-1ubuntu3
  Version table:
 *** 8.16.0-1ubuntu3 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf
d /var/log 0755 - - -
f /var/log/wtmp 0664 root utmp -
f /var/log/btmp 0600 root utmp -

nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf
# Override systemd's default tmpfiles.d/var.conf to make /var/log writable by
# the syslog group, so that rsyslog can run as user.
# See tmpfiles.d(5) for details.

# Type PathMode UID  GID  Age Argument
d /var/log 0775 root syslog -

nick @ log2.be1.ams1:~ $ ls -ld /var/log
drwxrwxr-x 8 root syslog 4096 Feb  7 13:45 /var/log

nick @ log2.be1.ams1:~ $ sudo apt install --reinstall systemd
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 7 not upgraded.
Need to get 3,634 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 systemd amd64 
229-4ubuntu21.1 [3,634 kB]
Fetched 3,634 kB in 0s (24.3 MB/s)
(Reading database ... 86614 files and directories currently installed.)
Preparing to unpack .../systemd_229-4ubuntu21.1_amd64.deb ...
Unpacking systemd (229-4ubuntu21.1) over (229-4ubuntu21.1) ...
Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up systemd (229-4ubuntu21.1) ...
addgroup: The group `systemd-journal' already exists as a system group. Exiting.

nick @ log2.be1.ams1:~ $ ls -ld /var/log
drwxr-xr-x 8 root syslog 4096 Feb  7 13:45 /var/log

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

Title:
  Upgrading systemd sets incorrect permissions on /var/log/

Status in systemd package in Ubuntu:
  New

Bug description:
  Upgrading or reinstalling the systemd package when using rsyslogd
  results in bad permissions (0755 instead of 0775) being set on
  /var/log/. As a consequence of this, rsyslogd can no longer create new
  files within this directory, resulting in lost log messages.

  The default configuration of rsyslogd provided by Ubuntu runs the
  daemon as syslog:syslog and sets ownership of /var/log to syslog:adm
  with mode 0775.

  Systemd's default tmpfiles configuration sets /var/log to 0755 in
  /usr/lib/tmpfiles.d/var.conf, however this is overridden in
  /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package
  rsyslog.

  It looks as though an upgrade of the systemd package fails to take
  /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated
  below. This results in /var/log receiving mode 0755 instead of the
  expected 0775:

  
  nick @ log2.be1.ams1:~ $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  nick @ log2.be1.ams1:~ $ apt policy systemd
  systemd:
Installed: 229-4ubuntu21.1
Candidate: 229-4ubuntu21.1
Version table:
   *** 229-4ubuntu21.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main 

[Touch-packages] [Bug 1547647] Proposed package removed from archive

[Łukasz Zemczak]

The version of signon-ui in the proposed pocket of Xenial that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.

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

Title:
  [SRU] please remove libqt5webkit dependency

Status in signon-ui package in Ubuntu:
  Fix Released
Status in signon-ui source package in Xenial:
  Won't Fix
Status in signon-ui source package in Yakkety:
  Fix Released

Bug description:
  This is an SRU request, based on the process documented at
  https://wiki.ubuntu.com/StableReleaseUpdates

  
  [Impact]

   * When declaring online accounts for use by Ubuntu, the system uses a
  webview to authenticate to online services like Facebook or Google.

   * On X11 desktops, that webview currently uses an old qt5webkit
  component that is now unmaintained

   * Backporting this fix will simplify the maintenance work, by
  removing the need for that old component, and will improve the
  coherence of the system by using a supported Oxide webview

  [Test Case]

  To verify the change:

   * Go to system settings > Online Accounts
   * Add account of type Google, Facebook or Twitter (which uses webview for 
authentication)
   * Verify that a webview opens to log onto the online service
   * Verify that the account is listed in the account list at the end of this 
process
   * Verify that the related apps and services can use the online account as 
before (ie Shotwell photo uploads, Photos scope, etc.)

  [Regression Potential]

   * On architectures not supported by Oxide, namely ppc64el and s390x,
  the change will trigger a runtime error when trying to use that part
  of signon-ui.

   * The problem affects users of Ubuntu desktop systems based on X11.
  The change is already in effect on Unity8/Mir devices for a few
  months.

  [Other Info]

   * signon-ui-x11(http://packages.ubuntu.com/xenial/signon-ui-x11)
  depends on libqt5webkit5

   * See also: https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-
  security-updates/

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

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

[Touch-packages] [Bug 1547647] Proposed package removed from archive

[Łukasz Zemczak]

The version of signon-ui in the proposed pocket of Xenial that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.

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

Title:
  [SRU] please remove libqt5webkit dependency

Status in signon-ui package in Ubuntu:
  Fix Released
Status in signon-ui source package in Xenial:
  Won't Fix
Status in signon-ui source package in Yakkety:
  Fix Released

Bug description:
  This is an SRU request, based on the process documented at
  https://wiki.ubuntu.com/StableReleaseUpdates

  
  [Impact]

   * When declaring online accounts for use by Ubuntu, the system uses a
  webview to authenticate to online services like Facebook or Google.

   * On X11 desktops, that webview currently uses an old qt5webkit
  component that is now unmaintained

   * Backporting this fix will simplify the maintenance work, by
  removing the need for that old component, and will improve the
  coherence of the system by using a supported Oxide webview

  [Test Case]

  To verify the change:

   * Go to system settings > Online Accounts
   * Add account of type Google, Facebook or Twitter (which uses webview for 
authentication)
   * Verify that a webview opens to log onto the online service
   * Verify that the account is listed in the account list at the end of this 
process
   * Verify that the related apps and services can use the online account as 
before (ie Shotwell photo uploads, Photos scope, etc.)

  [Regression Potential]

   * On architectures not supported by Oxide, namely ppc64el and s390x,
  the change will trigger a runtime error when trying to use that part
  of signon-ui.

   * The problem affects users of Ubuntu desktop systems based on X11.
  The change is already in effect on Unity8/Mir devices for a few
  months.

  [Other Info]

   * signon-ui-x11(http://packages.ubuntu.com/xenial/signon-ui-x11)
  depends on libqt5webkit5

   * See also: https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-
  security-updates/

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

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

[Touch-packages] [Bug 1547647] Proposed package removed from archive

[Łukasz Zemczak]

The version of signon-ui in the proposed pocket of Xenial that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.

** Changed in: signon-ui (Ubuntu Xenial)
   Status: Fix Committed => Won't Fix

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

Title:
  [SRU] please remove libqt5webkit dependency

Status in signon-ui package in Ubuntu:
  Fix Released
Status in signon-ui source package in Xenial:
  Won't Fix
Status in signon-ui source package in Yakkety:
  Fix Released

Bug description:
  This is an SRU request, based on the process documented at
  https://wiki.ubuntu.com/StableReleaseUpdates

  
  [Impact]

   * When declaring online accounts for use by Ubuntu, the system uses a
  webview to authenticate to online services like Facebook or Google.

   * On X11 desktops, that webview currently uses an old qt5webkit
  component that is now unmaintained

   * Backporting this fix will simplify the maintenance work, by
  removing the need for that old component, and will improve the
  coherence of the system by using a supported Oxide webview

  [Test Case]

  To verify the change:

   * Go to system settings > Online Accounts
   * Add account of type Google, Facebook or Twitter (which uses webview for 
authentication)
   * Verify that a webview opens to log onto the online service
   * Verify that the account is listed in the account list at the end of this 
process
   * Verify that the related apps and services can use the online account as 
before (ie Shotwell photo uploads, Photos scope, etc.)

  [Regression Potential]

   * On architectures not supported by Oxide, namely ppc64el and s390x,
  the change will trigger a runtime error when trying to use that part
  of signon-ui.

   * The problem affects users of Ubuntu desktop systems based on X11.
  The change is already in effect on Unity8/Mir devices for a few
  months.

  [Other Info]

   * signon-ui-x11(http://packages.ubuntu.com/xenial/signon-ui-x11)
  depends on libqt5webkit5

   * See also: https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-
  security-updates/

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

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

[Touch-packages] [Bug 1510570] Re: Bluetooth LE pairing fail

[Łukasz Zemczak]

Since the regression has been resolved, could someone re-validate the
package in -proposed?

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

Title:
  Bluetooth LE pairing fail

Status in OEM Priority Project:
  Confirmed
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  When the Bluetooth adapter is not powered on it is not possible to use
  it in normal way. We used to have a hack to force powering on by using
  an udev rule but this doe snot work anymore. Luckily the BlueZ has
  introduced "AutoEnable" option that makes the stack power on adapters by
  itself.

  Backporting this to xenial will improve life of the desktop users and
  will not require them to hack the solution on their own. The fix itself
  uses the well known solution to this problem that is floating around
  there for a while.

  The upload fixes the bug by enabling the 'AutoEnable' option in the
  bluetoothd config file.

  [Original Report]

  . 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used
  instead of udev rules.

  here is a commit with this parameter:
  http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138

  [Test Case]

  On xenial install from ppa:
  https://launchpad.net/~bluetooth/+archive/ubuntu/bluez

  Now reboot the machine. The BT adapter shall be
  powered on.

  [Regression Potential]

  If things go wrong the adapter will not be powered on after the system
  boots up. Therefore while testing please focus on the adapter state,
  i.e. powered on or off.

  [Other Info]

  This fix is included in the development release, see:
  http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

  [What to upload]

  For xenial as in:

  ) https://launchpad.net/~bluetooth/+archive/ubuntu/bluez
  ) 
https://launchpadlibrarian.net/347480725/bluez_5.37-0ubuntu5_5.37-0ubuntu5.2~build1.diff.gz

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

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

[Touch-packages] [Bug 1747476] Re: apport-collect needs python-qtpy and python-apport dependency issue on kubuntu

[Peridot]

** Changed in: apport (Ubuntu)
   Status: Incomplete => 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/1747476

Title:
  apport-collect needs python-qtpy and python-apport dependency issue on
  kubuntu

Status in apport package in Ubuntu:
  New

Bug description:
  apport-collect did not work until both packages were installed. The
  errors you get are not helpful and I only arrived at this solution
  after searching around online and basically wild guessing.

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

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