[Touch-packages] [Bug 2020604] Re: After mesa upgrades, Chrome won't show graphics

[Jesse]

`rm -R ~/.config/google-chrome/Default/GPUCache` (and then restarting
chrome) from the askubuntu post fixed it!

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

Title:
  After mesa upgrades, Chrome won't show graphics

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  After today's Ubuntu 22.04 mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with mesa or Chrome or specific machine
  graphics or an interaction between them.

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


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

[Touch-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

[Jesse Richey]

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

None of these solutions are working and I'm on 22.10 with kernel 5.19.
This is pretty absurd. I used NetworkManager 3 years ago on a Raspberry
Pi to build out a custom LTE solution using a Sierra Wireless CAT6
module... and yet for something I can't have NetworkManager manage wifi
on an intel nuc?

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

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

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


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

[Touch-packages] [Bug 1997178] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver redux

[Jesse Johnson]

Tested and confirmed that wake from sleep results in a black screen 100%
of the time on 5.15.0-53-generic, but only ~10% of the time on
5.15.0-52-generic. Thus on the surface it seems 5.15.0-53-generic caused
a regression.

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

Title:
   Black screen after wake from S3 suspend on Nvidia proprietary driver
  redux

Status in linux package in Ubuntu:
  New

Bug description:
  When resuming from suspend in Ubuntu 22.04 with proprietary Nvidia
  driver 515, screen is black, and never changes after 10 minutes of
  waiting.

  However journalctl shows activity after wake (see attached log
  excerpt, where wake occurs around Nov 20 10:28:37 with black screen,
  followed by forced REISUB reboot a couple minutes later when screen
  failed to update). This makes me think the issue is around Nvidia
  driver <-> Linux kernel communication.

  I [previously
  reported](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987134)
  similar black screen after wake behavior that seemed resolve with a
  Linux kernel update, but subsequent Linux kernel and Nvidia driver
  updates steadily regressed back to the previous behavior. The most
  recent kernel update from a few days ago (5.15.0-53-generic) never
  wakes from suspend (so far out of 5 trials). Previous few kernels
  where regression was first noticed it was 50/50 odds of successful
  wake, so most recent kernel is a noticeable regression.

  Important note: most recent kernel (5.15.0-53) upgrade freezed system
  mid-upgrade (first time this has happened to me on Linux in at least 5
  years!). Damaged GRUB and Nvidia DKMS, requiring reinstallation of
  GRUB, the kernel, Nvidia drivers, and a GRUB update (in that order).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0d.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:  gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 20 11:20:45 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: nvidia/515.65.01, 5.15.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: PNY GM204 [GeForce GTX 970] [196e:1131]
  InstallationDate: Installed on 2022-08-17 (95 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-53-generic 
root=UUID=70074436-a9a5-4212-9b57-7600a7dc6843 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.70
  dmi.board.name: X470 Taichi Ultimate
  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.:bvrP4.70:bd03/29/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470TaichiUltimate:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  v

[Touch-packages] [Bug 1997178] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver redux

[Jesse Johnson]

** Attachment added: "journalctl log of sleep-wake-forced reboot around Nov 20 
10:28:37"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1997178/+attachment/5631722/+files/reboot.txt

** Description changed:

  When resuming from suspend in Ubuntu 22.04 with proprietary Nvidia
  driver 515, screen is black, and never changes after 10 minutes of
  waiting.
  
  However journalctl shows activity after wake (see attached log excerpt,
- where wake occurs around Nov 20 10:28:37). This makes me think the issue
- is around Nvidia driver <-> Linux kernel communication.
+ where wake occurs around Nov 20 10:28:37 with black screen, followed by
+ forced REISUB reboot a couple minutes later when screen failed to
+ update). This makes me think the issue is around Nvidia driver <-> Linux
+ kernel communication.
  
  I [previously
  reported](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987134)
  similar black screen after wake behavior that seemed resolve with a
  Linux kernel update, but subsequent Linux kernel and Nvidia driver
  updates steadily regressed back to the previous behavior. The most
  recent kernel update from a few days ago (5.15.0-53-generic) never wakes
  from suspend (so far out of 5 trials). Previous few kernels where
  regression was first noticed it was 50/50 odds of successful wake, so
  most recent kernel is a noticeable regression.
  
- Important note: most recent kernel (5.15.0-53) upgrade freezed mid-
- upgrade (first time this has happened to me on Linux in at least 5
+ Important note: most recent kernel (5.15.0-53) upgrade freezed system
+ mid-upgrade (first time this has happened to me on Linux in at least 5
  years!). Damaged GRUB and Nvidia DKMS, requiring reinstallation of GRUB,
  the kernel, Nvidia drivers, and a GRUB update (in that order).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0d.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
-  GCC version:  gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
+  GCC version:  gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 20 11:20:45 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: nvidia/515.65.01, 5.15.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
-  NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
-Subsystem: PNY GM204 [GeForce GTX 970] [196e:1131]
+  NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
+    Subsystem: PNY GM204 [GeForce GTX 970] [196e:1131]
  InstallationDate: Installed on 2022-08-17 (95 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/usr/bin/zsh
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-53-generic 
root=UUID=70074436-a9a5-4212-9b57-7600a7dc6843 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.70
  dmi.board.name: X470 Taichi Ultimate
  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.:bvrP4.70:bd03/29/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470TaichiUltimate:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.

[Touch-packages] [Bug 1997178] [NEW] Black screen after wake from S3 suspend on Nvidia proprietary driver redux

[Jesse Johnson]

Public bug reported:

When resuming from suspend in Ubuntu 22.04 with proprietary Nvidia
driver 515, screen is black, and never changes after 10 minutes of
waiting.

However journalctl shows activity after wake (see attached log excerpt,
where wake occurs around Nov 20 10:28:37 with black screen, followed by
forced REISUB reboot a couple minutes later when screen failed to
update). This makes me think the issue is around Nvidia driver <-> Linux
kernel communication.

I [previously
reported](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987134)
similar black screen after wake behavior that seemed resolve with a
Linux kernel update, but subsequent Linux kernel and Nvidia driver
updates steadily regressed back to the previous behavior. The most
recent kernel update from a few days ago (5.15.0-53-generic) never wakes
from suspend (so far out of 5 trials). Previous few kernels where
regression was first noticed it was 50/50 odds of successful wake, so
most recent kernel is a noticeable regression.

Important note: most recent kernel (5.15.0-53) upgrade freezed system
mid-upgrade (first time this has happened to me on Linux in at least 5
years!). Damaged GRUB and Nvidia DKMS, requiring reinstallation of GRUB,
the kernel, Nvidia drivers, and a GRUB update (in that order).

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
Uname: Linux 5.15.0-53-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..0d.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 14:00:58 
UTC 2022
 GCC version:  gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 20 11:20:45 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus: nvidia/515.65.01, 5.15.0-53-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Several times a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Within the last week or two
GraphicsCard:
 NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: PNY GM204 [GeForce GTX 970] [196e:1131]
InstallationDate: Installed on 2022-08-17 (95 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-53-generic 
root=UUID=70074436-a9a5-4212-9b57-7600a7dc6843 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/29/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P4.70
dmi.board.name: X470 Taichi Ultimate
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.:bvrP4.70:bd03/29/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470TaichiUltimate:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug freeze jammy ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 

[Touch-packages] [Bug 1987134] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver

[Jesse Johnson]

Tried installing the Nvidia 390 driver since that is another commonly
cited workaround, but once pass the filesystem encryption password
prompts the screen goes black. No useful error messages in journalctl
that I can see.

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

Title:
  Black screen after wake from S3 suspend on Nvidia proprietary driver

Status in xorg package in Ubuntu:
  New

Bug description:
  An Nvidia driver upgrade in Ubuntu 20.04 caused waking from S3 suspend
  to lead to a black screen.

  Upgrading to Ubuntu 22.04 using latest stable Nvidia driver 515.65.01
  did not resolve the issue.

  There are several Nvidia sleep tickets that at first seem related, but
  mention dmesg entries that I am not seeing which makes me suspect I
  have a different issue:

  * 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1970088
  * 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303

  Workaround dhenry mentions in 1970088 of disabling the nvidia suspend
  and hibernate systemd services makes no difference for me.

  Currrently running Ubuntu 22.04, Nvidia GTX 970 on driver 515.65.01,
  AMD Ryzen 7 5800X.

  Here are journalctl excerpts during the reboot process, with and
  without nvidia systemd suspend services. dmesg and /var/log/kern.log
  show no errors as are mentioned in the above tickets.

  With disabled nvidia suspend systemd services:

  Aug 19 12:42:37 uf-panacea ModemManager[2731]:   [sleep-monitor] system 
is about to suspend
  Aug 19 12:42:37 uf-panacea NetworkManager[2617]:   [1660938157.8491] 
manager: NetworkManager state>
  Aug 19 12:42:37 uf-panacea systemd[1]: Reached target Sleep.
  Aug 19 12:42:37 uf-panacea systemd[1]: Starting Record successful boot for 
GRUB...
  Aug 19 12:42:37 uf-panacea systemd[1]: Starting System Suspend...
  Aug 19 12:42:37 uf-panacea systemd-sleep[13048]: Entering sleep state 
'suspend'...
  Aug 19 12:42:37 uf-panacea systemd[1]: grub-common.service: Deactivated 
successfully.
  Aug 19 12:42:37 uf-panacea systemd[1]: Finished Record successful boot for 
GRUB.

  With enabled nvidia suspend systemd services:

  Aug 19 12:12:25 uf-panacea systemd[1]: Starting NVIDIA system suspend 
actions...
  Aug 19 12:12:25 uf-panacea suspend[15998]: nvidia-suspend.service
  Aug 19 12:12:25 uf-panacea logger[15998]: <13>Aug 19 12:12:25 suspend: 
nvidia-suspend.service
  Aug 19 12:12:25 uf-panacea systemd[1]: grub-common.service: Deactivated 
successfully.
  Aug 19 12:12:25 uf-panacea systemd[1]: Finished Record successful boot for 
GRUB.
  Aug 19 12:12:25 uf-panacea systemd[1]: Starting GRUB failed boot detection...
  Aug 19 12:12:25 uf-panacea systemd[1]: grub-initrd-fallback.service: 
Deactivated successfully.
  Aug 19 12:12:25 uf-panacea systemd[1]: Finished GRUB failed boot detection.
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"40"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event1  - 
Power Button: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"43"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event0  - 
Power Button: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"44"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event4  - 
USB Mouse OKLIC: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"45"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event5  - 
USB Mouse OKLIC Mouse: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"46"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event6  - 
USB Mouse OKLIC System Control: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"47"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event7  - 
USB Mouse OKLIC Consumer Control: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"53"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"53"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event11 - 
Valve Software Steam Controller: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"50"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"50"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event9  - 
Logitech G305: device removed
  Aug 19 12:12:25 uf-panacea rtkit-daemon[3286]: Supervising 10 threads of 4 
processes of 1 users.
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"51"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session

[Touch-packages] [Bug 1987134] [NEW] Black screen after wake from S3 suspend on Nvidia proprietary driver

[Jesse Johnson]

Public bug reported:

An Nvidia driver upgrade in Ubuntu 20.04 caused waking from S3 suspend
to lead to a black screen.

Upgrading to Ubuntu 22.04 using latest stable Nvidia driver 515.65.01
did not resolve the issue.

There are several Nvidia sleep tickets that at first seem related, but
mention dmesg entries that I am not seeing which makes me suspect I have
a different issue:

* 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1970088
* 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303

Workaround dhenry mentions in 1970088 of disabling the nvidia suspend
and hibernate systemd services makes no difference for me.

Currrently running Ubuntu 22.04, Nvidia GTX 970 on driver 515.65.01, AMD
Ryzen 7 5800X.

Here are journalctl excerpts during the reboot process, with and without
nvidia systemd suspend services. dmesg and /var/log/kern.log show no
errors as are mentioned in the above tickets.

With disabled nvidia suspend systemd services:

Aug 19 12:42:37 uf-panacea ModemManager[2731]:   [sleep-monitor] system 
is about to suspend
Aug 19 12:42:37 uf-panacea NetworkManager[2617]:   [1660938157.8491] 
manager: NetworkManager state>
Aug 19 12:42:37 uf-panacea systemd[1]: Reached target Sleep.
Aug 19 12:42:37 uf-panacea systemd[1]: Starting Record successful boot for 
GRUB...
Aug 19 12:42:37 uf-panacea systemd[1]: Starting System Suspend...
Aug 19 12:42:37 uf-panacea systemd-sleep[13048]: Entering sleep state 
'suspend'...
Aug 19 12:42:37 uf-panacea systemd[1]: grub-common.service: Deactivated 
successfully.
Aug 19 12:42:37 uf-panacea systemd[1]: Finished Record successful boot for GRUB.

With enabled nvidia suspend systemd services:

Aug 19 12:12:25 uf-panacea systemd[1]: Starting NVIDIA system suspend actions...
Aug 19 12:12:25 uf-panacea suspend[15998]: nvidia-suspend.service
Aug 19 12:12:25 uf-panacea logger[15998]: <13>Aug 19 12:12:25 suspend: 
nvidia-suspend.service
Aug 19 12:12:25 uf-panacea systemd[1]: grub-common.service: Deactivated 
successfully.
Aug 19 12:12:25 uf-panacea systemd[1]: Finished Record successful boot for GRUB.
Aug 19 12:12:25 uf-panacea systemd[1]: Starting GRUB failed boot detection...
Aug 19 12:12:25 uf-panacea systemd[1]: grub-initrd-fallback.service: 
Deactivated successfully.
Aug 19 12:12:25 uf-panacea systemd[1]: Finished GRUB failed boot detection.
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"40"
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event1  - 
Power Button: device removed
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"43"
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event0  - 
Power Button: device removed
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"44"
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event4  - USB 
Mouse OKLIC: device removed
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"45"
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event5  - USB 
Mouse OKLIC Mouse: device removed
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"46"
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event6  - USB 
Mouse OKLIC System Control: device removed
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"47"
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event7  - USB 
Mouse OKLIC Consumer Control: device removed
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"53"
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"53"
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event11 - 
Valve Software Steam Controller: device removed
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"50"
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"50"
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event9  - 
Logitech G305: device removed
Aug 19 12:12:25 uf-panacea rtkit-daemon[3286]: Supervising 10 threads of 4 
processes of 1 users.
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"51"
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"51"
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event13 - 
Corsair Corsair STRAFE RGB Gaming Keyboard: device removed
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"52"
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event2  - 
C-Media Electronics Inc. USB Audio Device: device removed
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"89"
Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event3  - 
DCMT Technology USB Condenser Microphone: device removed
Aug 19 12:12:25 uf-panace

[Touch-packages] [Bug 1879085] Re: update-initramfs can't handle encrypted swap-files

[Jesse]

** Project changed: cryptsetup => cryptsetup (Ubuntu)

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

Title:
  update-initramfs can't handle encrypted swap-files

Status in cryptsetup package in Ubuntu:
  New
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  OS: Ubuntu 20.04 Mate

  I have an encrypted swap-file, which is working fine:

  # grep cryptswap /etc/fstab
  /dev/mapper/cryptswap none swap  defaults 0 0
  # grep cryptswap /etc/crypttab
  cryptswap /cryptswapfile /dev/urandom swap,cipher=aes-xts-plain64,size=256

  But everytime I update the kernel and update-initramfs is executed, an
  error occurs:

  cryptsetup: ERROR: Couldn't resolve device /cryptswapfile
  cryptsetup: WARNING: Resume target cryptswap uses a key file

  And after the next reboot, the system can't load the cryptswap while
  booting and hangs for several minutes.

  Workaround: Boot into rescue mode and wait until the loading of the
  cryptswapfile timeouts. Go to a shell and comment the lines in the
  fstab and crypttab. Execute # swapoff -a && update-initramfs -u. Now
  uncomment the lines in fstab and crypttab again and reboot. Your
  system should boot fine and you should have an encrypted swapfile.

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

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

[Touch-packages] [Bug 1879085] Re: update-initramfs can't handle encrypted swap-files

[Jesse]

** Also affects: cryptsetup
   Importance: Undecided
   Status: New

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

Title:
  update-initramfs can't handle encrypted swap-files

Status in cryptsetup package in Ubuntu:
  New
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  OS: Ubuntu 20.04 Mate

  I have an encrypted swap-file, which is working fine:

  # grep cryptswap /etc/fstab
  /dev/mapper/cryptswap none swap  defaults 0 0
  # grep cryptswap /etc/crypttab
  cryptswap /cryptswapfile /dev/urandom swap,cipher=aes-xts-plain64,size=256

  But everytime I update the kernel and update-initramfs is executed, an
  error occurs:

  cryptsetup: ERROR: Couldn't resolve device /cryptswapfile
  cryptsetup: WARNING: Resume target cryptswap uses a key file

  And after the next reboot, the system can't load the cryptswap while
  booting and hangs for several minutes.

  Workaround: Boot into rescue mode and wait until the loading of the
  cryptswapfile timeouts. Go to a shell and comment the lines in the
  fstab and crypttab. Execute # swapoff -a && update-initramfs -u. Now
  uncomment the lines in fstab and crypttab again and reboot. Your
  system should boot fine and you should have an encrypted swapfile.

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

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

[Touch-packages] [Bug 1870963] [NEW] Bottom edge of Workspace Switch goes all the way down to screen edge (when it should match the top edge layout?)

[Jesse]

Public bug reported:

BEHAVIOR:
When I press super or activities to go into the Overview, on the right, the 
workspace switcher's bottom edge travels all the way down to the screen's edge, 
unlike the top which its edge breaks a short distance from the top bar. If you 
look at it compared to the gnome shell's default session (see screenshot I'm 
including), both to and bottom edges break shortly before the screen's edge.

If this is by design, it's honestly not a good design, IMO. But if it's
a bug and the bottom edge is supposed to break before the screen's edge
like the top one does, well that is the reason for this bug. :)

Cheers!

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-desktop 1.447
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr  5 10:30:40 2020
InstallationDate: Installed on 2020-04-03 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no username)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot example between default gnome session & 
ubuntu-desktop session"
   
https://bugs.launchpad.net/bugs/1870963/+attachment/5347237/+files/ubuntu-desktop-bug-screenshot-example.jpg

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

Title:
  Bottom edge of Workspace Switch goes all the way down to screen edge
  (when it should match the top edge layout?)

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  BEHAVIOR:
  When I press super or activities to go into the Overview, on the right, the 
workspace switcher's bottom edge travels all the way down to the screen's edge, 
unlike the top which its edge breaks a short distance from the top bar. If you 
look at it compared to the gnome shell's default session (see screenshot I'm 
including), both to and bottom edges break shortly before the screen's edge.

  If this is by design, it's honestly not a good design, IMO. But if
  it's a bug and the bottom edge is supposed to break before the
  screen's edge like the top one does, well that is the reason for this
  bug. :)

  Cheers!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.447
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  5 10:30:40 2020
  InstallationDate: Installed on 2020-04-03 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 395155] Re: Too long and unhelpful notification for ".local" domains

[Jesse Glick]

I am a programmer and I have only the foggiest notion of what Avahi is
or what it is there for, yet I continually receive this irritating
warning popup about something broken that I was not trying to use to
begin with. #327362 is the bug I found years ago. I just want this
notification to go away and stay away unless and until I am using some
application which is actually impaired.

Possibly also related: #80900, #1441008, #1082858, etc.

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

Title:
  Too long and unhelpful notification for ".local" domains

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: avahi-daemon

  When I connect to my home router, I get a notification about avahi
  being unable to use a ".local" domain. This bug is about fixing the
  message so that it is clearer and shorter. I was instructed to report
  such a bug on the ayatana mailing list, so perhaps a bit of discussion
  with them may be useful if the problem is unclear.

  The current message, at least, its Italian translation that I see
  every day, is definitely too long, I had to see it a tenth of times to
  be able to read the whole of it in the short delay of a notification.
  Moreover, even if I think I can be considered an expert in using
  linux, I did not understand at all the meaning of the message, and I
  had to google for it just to get what the point is. The topic is a bit
  technical for the average user. Even if knowing that avahi is "a dns
  service for the local network" I still have no clue of what it is
  actually used for, so I do not know what are the consequences of the
  notification (e.g. will my printer work, and this thing is connected
  with apple perhaps, so will my ipod work - if I had one :)).

  A short message like "The avahi service is disabled, look here for
  more info" would be good, but links can't be put in the notification.
  So I personally can't propose a good solution. Perhaps the message
  should not be shown at all, but rather it should be "embedded" in
  applications when they try to use avahi and fail (e.g. "avahi is
  disabled because your network has a .local domain, click here to know
  more", which is possible inside of an application.

  In any case, the current message is too long to be read; this is the
  easily understandable part of this bug.

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Jesse]

After trying a random assortment of fixes to get my Amazon Echo Show to
connect as a speaker using bluetooth to my Linux Mint 19.2 box I found
the solution far too simple.  The magic reboot!  I rebooted the Echo and
that must have cleared the bluetooth connections... ha

-- 
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 1759836] Re: systemd-udevd consumes 100% of CPU

[Jesse McNichol]

Similar problem for me. Dell E6530, Ubuntu 18.04

Downgraded to 4.13 headers as suggested above, disabled bluetooth in
BIOS as suggested by others. Neither workaround helped. Computer still
producing excess heat and systemd-udevd climbs to nearly 100% CPU usage
gradually from startup.

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

Title:
  systemd-udevd consumes 100% of CPU

Status in Bluez Utilities:
  Unknown
Status in linux:
  Unknown
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  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.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1281846] Re: Temporary black screen after login

[Jesse Knight]

This happens to me too (still) : both VGA and DVI-D (cannot test HDMI).
This happens at both log-in and log-out.

DistroRelease: Ubuntu 16.04
Architecture: amd64
Date: Sat Mar 10 2018

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

Title:
  Temporary black screen after login

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I turn on my laptop, wait lightdm appears, and do login to my user.
  Sometimes i got a black screen, only cursor appears in the screen. I
  can open a terminal with Ctrl+Alt+t, and run firefox using terminal,
  for example. And it is possible to change tty. Then, after 30 seconds,
  or more, like 1 minute, my desktop appears (background, unity
  launcher, top panel...).

  I'm having this problem in my asus laptop, that have nvidia optimus
  (and can confirm with other, a sony laptop with only intel graphics
  card).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Wed Feb 19 00:52:59 2014
  InstallationDate: Installed on 2013-12-13 (67 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1747338] [NEW] package cups-server-common 2.1.3-4ubuntu0.3 failed to install/upgrade: package cups-server-common is not ready for configuration cannot configure (current status '

[Jesse Rowley]

Public bug reported:

Keeps coming on when i log in, just switching back to ubuntu from
windows so unclear if it is because I am removing the windows partition
and maybe their was data loss.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-server-common 2.1.3-4ubuntu0.3
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CupsErrorLog:
 E [04/Feb/2018:22:13:24 -0500] Unable to open listen socket for address 
/var/run/cups/cups.sock:0 - Permission denied.
 E [04/Feb/2018:22:14:37 -0500] Unable to open listen socket for address 
/var/run/cups/cups.sock:0 - Permission denied.
Date: Sun Feb  4 22:21:57 2018
Dependencies:
 
DuplicateSignature:
 package:cups-server-common:2.1.3-4ubuntu0.3
 Processing triggers for man-db (2.7.5-1) ...
 dpkg: error processing package cups-server-common (--configure):
  package cups-server-common is not ready for configuration
ErrorMessage: package cups-server-common is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2018-02-05 (0 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
PackageArchitecture: all
Papersize: letter
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=25d0b994-bf9b-4425-849f-19dd4dee8017 ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=25d0b994-bf9b-4425-849f-19dd4dee8017 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: cups
Title: package cups-server-common 2.1.3-4ubuntu0.3 failed to install/upgrade: 
package cups-server-common is not ready for configuration  cannot configure 
(current status 'half-installed')
UpgradeStatus: Upgraded to xenial on 2018-02-05 (0 days ago)
dmi.bios.date: 03/30/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.10
dmi.board.name: AB350M Pro4
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.:bvrP2.10:bd03/30/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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.

** Affects: cups (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 cups in Ubuntu.
https://bugs.launchpad.net/bugs/1747338

Title:
  package cups-server-common 2.1.3-4ubuntu0.3 failed to install/upgrade:
  package cups-server-common is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in cups package in Ubuntu:
  New

Bug description:
  Keeps coming on when i log in, just switching back to ubuntu from
  windows so unclear if it is because I am removing the windows
  partition and maybe their was data loss.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-server-common 2.1.3-4ubuntu0.3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CupsErrorLog:
   E [04/Feb/2018:22:13:24 -0500] Unable to open listen socket for address 
/var/run/cups/cups.sock:0 - Permission denied.
   E [04/Feb/2018:22:14:37 -0500] Unable to open listen socket for address 
/var/run/cups/cups.sock:0 - Permission denied.
  Date: Sun Feb  4 22:21:57 2018
  Dependencies:
   
  DuplicateSignature:
   package:cups-server-common:2.1.3-4ubuntu0.3
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package cups-server-common (--configure):
package cups-server-common is not ready for configuration
  ErrorMessage: package cups-server-common is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2018-02-05 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  PackageArchitecture: all
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=25d0b994-bf9b-4425-849f-19dd4dee8017 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=25d0b994-bf9b-4425-849f-19dd4dee8017 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubun

[Touch-packages] [Bug 1742744] [NEW] machinectl import-tar hangs when the import file is multi-streamed

[Jesse Pretorius]

Public bug reported:

When trying to use machinectl import-tar to import a compressed rootfs
tarball, if the compression is multi-streamed then the import hangs
after the first stream.

Either the multi-stream import should work, or it should be detected and
an error output.

Environment:
Ubuntu 17.10 (Artful Aardvark)
systemd-container 234-2ubuntu12.1

Steps to reproduce:

# install systemd-container
apt-get update && apt-get install systemd-container

# fetch a multi-stream compressed rootfs
wget 
http://rpc-repo.rackspace.com/lxc-images/ubuntu/xenial/amd64/default-r14.7.0/20180101/rootfs.tar.xz

# verify that it has multiple streams
xz -lvv rootfs.tar.xz

# try to import it
machinectl --verify=no import-tar rootfs.tar.xz test

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

Title:
  machinectl import-tar hangs when the import file is multi-streamed

Status in systemd package in Ubuntu:
  New

Bug description:
  When trying to use machinectl import-tar to import a compressed rootfs
  tarball, if the compression is multi-streamed then the import hangs
  after the first stream.

  Either the multi-stream import should work, or it should be detected
  and an error output.

  Environment:
  Ubuntu 17.10 (Artful Aardvark)
  systemd-container 234-2ubuntu12.1

  Steps to reproduce:

  # install systemd-container
  apt-get update && apt-get install systemd-container

  # fetch a multi-stream compressed rootfs
  wget 
http://rpc-repo.rackspace.com/lxc-images/ubuntu/xenial/amd64/default-r14.7.0/20180101/rootfs.tar.xz

  # verify that it has multiple streams
  xz -lvv rootfs.tar.xz

  # try to import it
  machinectl --verify=no import-tar rootfs.tar.xz test

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

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

[Touch-packages] [Bug 1726571] [NEW] cpu fan speed freezes

[Jesse Geens]

Public bug reported:

cpu fan speed always freezes at 525RPM

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: udev 204-5ubuntu20.24
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Oct 23 22:24:18 2017
InstallationDate: Installed on 2015-08-06 (809 days ago)
InstallationMedia: Linux Mint 17 "Qiana" - Release amd64 20140530
Lsusb:
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 2550W1E
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=nl_BE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=81f09e4c-e8db-48d1-9083-0ef6bfbec68f ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/10/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 81ET48WW (1.24 )
dmi.board.name: 2550W1E
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr81ET48WW(1.24):bd12/10/2010:svnLENOVO:pn2550W1E:pvrThinkPadL512:rvnLENOVO:rn2550W1E:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2550W1E
dmi.product.version: ThinkPad L512
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug qiana third-party-packages

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

Title:
  cpu fan speed freezes

Status in systemd package in Ubuntu:
  New

Bug description:
  cpu fan speed always freezes at 525RPM

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: udev 204-5ubuntu20.24
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Oct 23 22:24:18 2017
  InstallationDate: Installed on 2015-08-06 (809 days ago)
  InstallationMedia: Linux Mint 17 "Qiana" - Release amd64 20140530
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 2550W1E
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=81f09e4c-e8db-48d1-9083-0ef6bfbec68f ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/10/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 81ET48WW (1.24 )
  dmi.board.name: 2550W1E
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr81ET48WW(1.24):bd12/10/2010:svnLENOVO:pn2550W1E:pvrThinkPadL512:rvnLENOVO:rn2550W1E:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2550W1E
  dmi.product.version: ThinkPad L512
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1707831] Re: [enhancement] Replace the "Activities" label with the Ubuntu icon/logo/glyph

[Jesse]

I respect Jeremy's (and other Ubuntu devs') positions that the GNOME
documentation refers to the "Activities" text button for the Overview,
and I think that can be helpful to keep it that way IF the users are
going to go to the GNOME documentation, and not search on Ubuntu's
forums, social media, community website, Askubuntu.com, etc. I'd
probably vote that they're going to go for the latter, searching
anything with the word "Ubuntu" Online, first, since Ubuntu is the
distro they're using. New users might not even realize that the desktop
is developed - primarily - by a different organization, entirely. If
that's the case, why would they search for anything other than "Ubuntu
help".

Back in June '17 I ran a poll on the Ubuntu G+ community, asking if
users preferred the Ubuntu logo in the top-left or the "Activities"
text. 169 members voted, and 87% were in favor of using the Ubuntu logo,
with only 13% in favor of keeping the "Activities" text (here's the poll
so you can see the comments, too:
https://plus.google.com/+JesseDuBordFilms/posts/LEjy6zxmNw3).

I'd personally be in favor of replacing the "Activities" text for the
Ubuntu logo in the Ubuntu-modified GNOME shell.

Reasons being:
(1) Brand recognition. Will better allow users and surveyors to identify Ubuntu 
on a PC they're passing by in the airport, coffee shop, etc.
(2) WAY less ambiguous (I have a hard time trying to understand why they used 
"Activities" for the English word -- can't imagine how it translates in other 
languages). Plasma tried using "Activities" as well, which I think is equally 
ambiguous. At least if users see that it's a symbol, they could click on it, 
see it's behavior, and designate it whatever they want. I feel that makes it 
way easier for the user to adopt the desktop as their own if they can even 
define it better on their terms, you know?

I do think Jeremy is right, though, that some users might not
instinctively feel it's a button. The Antergos guys did a good job of
putting the background in Blue for the "Activities" text on their theme
of the GNOME shell. Maybe doing something like having the background of
the Activities button the Ubuntu orange with the three white people
aligned in the center of the button? I personally think that would look
really cool, IMHO.

(3) With the Ubuntu-modifications to the GNOME shell, anyways, would it
really be a deal-breaker with the GNOME documentation for it to fit to
be modified a little more to fit Ubuntu's needs? I think it's more than
fair for a brand to be recognized, and - not saying this in any way as
criticism - but I imagine even some of the Ubuntu changes might differ
than the GNOME documentation for the vanilla shell? Would it then be
such a big deal to have something a little different? Again, no
criticism intended at all, just bringing it to the table.

(4) With Ubuntu already offering a vanilla shell experience with the
simple install of a package (you guys rock for that, by the way), would
it really be such a bad thing for Ubuntu to make "their version" of the
shell their own? You're offering both, after all. Maybe even a
disclaimer somewhere might be all you need that says, "The default
desktop in this version of Ubuntu uses a modified version of the GNOME
desktop. Behavior may differ slightly from how the GNOME documentation
depicts", something like that.

Alright, that was already a mouthful. Appreciate you all taking the time
to read, and hope this comment helps in deciding how to proceed.

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

Title:
  [enhancement] Replace the "Activities" label with the Ubuntu
  icon/logo/glyph

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

Bug description:
  I suggest replacing the "Activities" label with the Ubuntu icon/logo.

  "Activities" sounds awkward and misleading. It would be more suitably
  vague, and more consistent with the existing Unity7 experience if the
  Gnome Shell "Activities" label was replaced by just the Ubuntu logo.

  Perhaps even a single glyph:  or 

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Tue Aug  1 11:28:08 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-03 (89 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1721116] [NEW] tracker-extract using 700MB-1GB+ of RAM

[Jesse]

Public bug reported:

BEHAVIOR
The tracker service (showing as "tracker-extract" in the GNOME System Monitor) 
shows that it's using anywhere from 700MB to 1.1GB of RAM. This seems like a 
lot.

EXPECTED BEHAVIOR
Tracker uses much less RAM.

Bug reported using:
Tracker 2.0.0
Ubuntu 17.10 beta 2
Linux kernel 4.13.0-12-generic

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


** Tags: artful

** Tags added: artful

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

Title:
  tracker-extract using 700MB-1GB+ of RAM

Status in tracker package in Ubuntu:
  New

Bug description:
  BEHAVIOR
  The tracker service (showing as "tracker-extract" in the GNOME System 
Monitor) shows that it's using anywhere from 700MB to 1.1GB of RAM. This seems 
like a lot.

  EXPECTED BEHAVIOR
  Tracker uses much less RAM.

  Bug reported using:
  Tracker 2.0.0
  Ubuntu 17.10 beta 2
  Linux kernel 4.13.0-12-generic

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

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

[Touch-packages] [Bug 1595695] Re: Bluetooth indicator disappears every time bluetooth is being turned off

[Jesse]

Same problem on a fresh install of 17.04 on a new Thinkpad T470.

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

Title:
  Bluetooth indicator disappears every time bluetooth is being turned
  off

Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 16.04, every time I turn off bluetooth, the indicator icon 
disappears from the top panel.
  Each time I have to re-enable it by system setting or via dash.

  I expect it to behave in a same way as network indicator instead of
  disappearing.

  Here is the link with some info which could be helpful 
  https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1126108

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

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

[Touch-packages] [Bug 1705526] [NEW] Attempting to print any file through libreoffice fails. the print job is "held", and ultimatly aborted. Successfully printed test page though setting.

[Jesse Higley]

Public bug reported:

check summary

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CupsErrorLog:
 E [20/Jul/2017:12:03:52 -0400] [Job 468] Aborting job because it has no files.
 E [20/Jul/2017:12:04:08 -0400] [Job 469] Aborting job because it has no files.
 E [20/Jul/2017:12:11:54 -0400] [Job 471] Aborting job because it has no files.
 E [20/Jul/2017:12:19:00 -0400] [Job 472] Aborting job because it has no files.
CurrentDesktop: Unity
Date: Thu Jul 20 12:20:33 2017
InstallationDate: Installed on 2015-10-26 (633 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
Lpstat: device for HP-ENVY-4500-series2: 
hp:/net/ENVY_4500_series?zc=HP3464A98C1A74
MachineType: Hewlett-Packard p6-2011
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-ENVY-4500-series2.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-ENVY-4500-series2.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=49431aef-63ad-4411-b9ce-5620b8ca8766 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to xenial on 2016-08-06 (347 days ago)
dmi.bios.date: 08/11/2011
dmi.bios.vendor: AMI
dmi.bios.version: 7.14
dmi.board.name: 2AC2
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 2.00
dmi.chassis.asset.tag: MXU1400083
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAMI:bvr7.14:bd08/11/2011:svnHewlett-Packard:pnp6-2011:pvr2.00:rvnPEGATRONCORPORATION:rn2AC2:rvr2.00:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: p6-2011
dmi.product.version: 2.00
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug xenial

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

Title:
  Attempting to print any file through libreoffice fails. the print job
  is "held", and ultimatly aborted. Successfully printed test page
  though setting.

Status in cups package in Ubuntu:
  New

Bug description:
  check summary

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CupsErrorLog:
   E [20/Jul/2017:12:03:52 -0400] [Job 468] Aborting job because it has no 
files.
   E [20/Jul/2017:12:04:08 -0400] [Job 469] Aborting job because it has no 
files.
   E [20/Jul/2017:12:11:54 -0400] [Job 471] Aborting job because it has no 
files.
   E [20/Jul/2017:12:19:00 -0400] [Job 472] Aborting job because it has no 
files.
  CurrentDesktop: Unity
  Date: Thu Jul 20 12:20:33 2017
  InstallationDate: Installed on 2015-10-26 (633 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lpstat: device for HP-ENVY-4500-series2: 
hp:/net/ENVY_4500_series?zc=HP3464A98C1A74
  MachineType: Hewlett-Packard p6-2011
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-ENVY-4500-series2.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-ENVY-4500-series2.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=49431aef-63ad-4411-b9ce-5620b8ca8766 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to xenial on 2016-08-06 (347 days ago)
  dmi.bios.date: 08/11/2011
  dmi.bios.vendor: AMI
  dmi.bios.version: 7.14
  dmi.board.name: 2AC2
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 2.00
  dmi.chassis.asset.tag: MXU1400083
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr7.14:bd08/11/2011:svnHewlett-Packard:pnp6-2011:pvr2.00:rvnPEGATRONCORPORATION:rn2AC2:rvr2.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6-2011
  dmi.product.version: 2.00
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1700743] Re: incorrect /etc/adjtime

[Jesse Massengill]

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

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

Title:
  incorrect /etc/adjtime

Status in util-linux package in Ubuntu:
  New

Bug description:
  On Ubuntu 17.04 I noticed a variation between system time and hardware
  time.

  I ran hwclock to sync them and got:

  hwclock: Warning: unrecognized third line in adjtime file
  (Expected: `UTC' or `LOCAL' or nothing.)

  my system is running
  util-linux:
    Installed: 2.29-1ubuntu2
    Candidate: 2.29-1ubuntu2
    Version table:
   *** 2.29-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  I looked in /etc/adjtime; it does have 'UTC' on the third line...

  There is a similar report and proposed solution at:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706693

  This reporter believed that the problem was a missing newline on the
  end of the third line.

  -There is no newline after 'UTC' in /etc/adjtime on my system.
  -Manually adding a newline does make the warning not appear when invoking 
hwclock, as suggested by the above report.
  -However, the proposed solution (adding a final \n to the printf line in 
hwclock.sh) is already present in my /etc/init.d/hwclock.sh.

  EDIT:
  And yet the faulty line in /etc/adjtime is still present.
  Apparently, this solution is not the entire answer.
  END EDIT.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: util-linux 2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue Jun 27 04:50:29 2017
  InstallationDate: Installed on 2015-11-18 (586 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (68 days ago)

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

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

[Touch-packages] [Bug 1700743] Re: incorrect /etc/adjtime

[Jesse Massengill]

** Description changed:

  On Ubuntu 17.04 I noticed a variation between system time and hardware
  time.
  
  I ran hwclock to sync them and got:
  
  hwclock: Warning: unrecognized third line in adjtime file
- (Expected: `UTC' or `LOCAL' or nothing.)
+ (Expected: `UTC' or `LOCAL' or nothing.)
  
  my system is running
  util-linux:
-   Installed: 2.29-1ubuntu2
-   Candidate: 2.29-1ubuntu2
-   Version table:
-  *** 2.29-1ubuntu2 500
- 500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 2.29-1ubuntu2
+   Candidate: 2.29-1ubuntu2
+   Version table:
+  *** 2.29-1ubuntu2 500
+ 500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  I looked in /etc/adjtime; it does have 'UTC' on the third line...
  
  There is a similar report and proposed solution at:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706693
  
  This reporter believed that the problem was a missing newline on the end
  of the third line.
  
- -There is no newline after 'UTC' in /etc/adjtime on my system. 
- -Manually adding a newline does make the warning not appear when invoking 
hwclock, as suggested by the above report. 
+ -There is no newline after 'UTC' in /etc/adjtime on my system.
+ -Manually adding a newline does make the warning not appear when invoking 
hwclock, as suggested by the above report.
  -However, the proposed solution (adding a final \n to the printf line in 
hwclock.sh) is already present in my /etc/init.d/hwclock.sh.
+ 
+ EDIT:
+ And yet the faulty line in /etc/adjtime is still present.
+ Apparently, this solution is not the entire answer.
+ END EDIT.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: util-linux 2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue Jun 27 04:50:29 2017
  InstallationDate: Installed on 2015-11-18 (586 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (68 days ago)

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

Title:
  incorrect /etc/adjtime

Status in util-linux package in Ubuntu:
  New

Bug description:
  On Ubuntu 17.04 I noticed a variation between system time and hardware
  time.

  I ran hwclock to sync them and got:

  hwclock: Warning: unrecognized third line in adjtime file
  (Expected: `UTC' or `LOCAL' or nothing.)

  my system is running
  util-linux:
    Installed: 2.29-1ubuntu2
    Candidate: 2.29-1ubuntu2
    Version table:
   *** 2.29-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  I looked in /etc/adjtime; it does have 'UTC' on the third line...

  There is a similar report and proposed solution at:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706693

  This reporter believed that the problem was a missing newline on the
  end of the third line.

  -There is no newline after 'UTC' in /etc/adjtime on my system.
  -Manually adding a newline does make the warning not appear when invoking 
hwclock, as suggested by the above report.
  -However, the proposed solution (adding a final \n to the printf line in 
hwclock.sh) is already present in my /etc/init.d/hwclock.sh.

  EDIT:
  And yet the faulty line in /etc/adjtime is still present.
  Apparently, this solution is not the entire answer.
  END EDIT.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: util-linux 2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue Jun 27 04:50:29 2017
  InstallationDate: Installed on 2015-11-18 (586 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (68 days ago)

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

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

[Touch-packages] [Bug 1700743] Re: incorrect /etc/adjtime

[Jesse Massengill]

Obviously not, if it is still happening.

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

Title:
  incorrect /etc/adjtime

Status in util-linux package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 17.04 I noticed a variation between system time and hardware
  time.

  I ran hwclock to sync them and got:

  hwclock: Warning: unrecognized third line in adjtime file
  (Expected: `UTC' or `LOCAL' or nothing.)

  my system is running
  util-linux:
    Installed: 2.29-1ubuntu2
    Candidate: 2.29-1ubuntu2
    Version table:
   *** 2.29-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  I looked in /etc/adjtime; it does have 'UTC' on the third line...

  There is a similar report and proposed solution at:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706693

  This reporter believed that the problem was a missing newline on the
  end of the third line.

  -There is no newline after 'UTC' in /etc/adjtime on my system.
  -Manually adding a newline does make the warning not appear when invoking 
hwclock, as suggested by the above report.
  -However, the proposed solution (adding a final \n to the printf line in 
hwclock.sh) is already present in my /etc/init.d/hwclock.sh.

  EDIT:
  And yet the faulty line in /etc/adjtime is still present.
  Apparently, this solution is not the entire answer.
  END EDIT.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: util-linux 2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue Jun 27 04:50:29 2017
  InstallationDate: Installed on 2015-11-18 (586 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (68 days ago)

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

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

[Touch-packages] [Bug 1700743] [NEW] incorrect /etc/adjtime

[Jesse Massengill]

Public bug reported:

On Ubuntu 17.04 I noticed a variation between system time and hardware
time.

I ran hwclock to sync them and got:

hwclock: Warning: unrecognized third line in adjtime file
(Expected: `UTC' or `LOCAL' or nothing.)

my system is running
util-linux:
  Installed: 2.29-1ubuntu2
  Candidate: 2.29-1ubuntu2
  Version table:
 *** 2.29-1ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
100 /var/lib/dpkg/status

I looked in /etc/adjtime; it does have 'UTC' on the third line...

There is a similar report and proposed solution at:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706693

This reporter believed that the problem was a missing newline on the end
of the third line.

-There is no newline after 'UTC' in /etc/adjtime on my system. 
-Manually adding a newline does make the warning not appear when invoking 
hwclock, as suggested by the above report. 
-However, the proposed solution (adding a final \n to the printf line in 
hwclock.sh) is already present in my /etc/init.d/hwclock.sh.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: util-linux 2.29-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
Uname: Linux 4.10.0-24-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Tue Jun 27 04:50:29 2017
InstallationDate: Installed on 2015-11-18 (586 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: util-linux
UpgradeStatus: Upgraded to zesty on 2017-04-19 (68 days ago)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hwclock util-linux zesty

** Summary changed:

- hwclock creates  incorrect /etc/adjtime
+ incorrect /etc/adjtime

** Tags added: hwclock util-linux

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

Title:
  incorrect /etc/adjtime

Status in util-linux package in Ubuntu:
  New

Bug description:
  On Ubuntu 17.04 I noticed a variation between system time and hardware
  time.

  I ran hwclock to sync them and got:

  hwclock: Warning: unrecognized third line in adjtime file
  (Expected: `UTC' or `LOCAL' or nothing.)

  my system is running
  util-linux:
Installed: 2.29-1ubuntu2
Candidate: 2.29-1ubuntu2
Version table:
   *** 2.29-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  I looked in /etc/adjtime; it does have 'UTC' on the third line...

  There is a similar report and proposed solution at:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706693

  This reporter believed that the problem was a missing newline on the
  end of the third line.

  -There is no newline after 'UTC' in /etc/adjtime on my system. 
  -Manually adding a newline does make the warning not appear when invoking 
hwclock, as suggested by the above report. 
  -However, the proposed solution (adding a final \n to the printf line in 
hwclock.sh) is already present in my /etc/init.d/hwclock.sh.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: util-linux 2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue Jun 27 04:50:29 2017
  InstallationDate: Installed on 2015-11-18 (586 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (68 days ago)

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

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

[Touch-packages] [Bug 1699630] [NEW] package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

[jesse]

Public bug reported:

?

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: isc-dhcp-common 4.3.3-5ubuntu12.7
ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-56-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Tue Jun 20 04:56:26 2017
Dependencies:
 debianutils 4.7
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu9
 libgcc1 1:6.0.1-0ubuntu1
 sensible-utils 0.0.9
DuplicateSignature:
 package:isc-dhcp-common:4.3.3-5ubuntu12.7
 Unpacking linux-headers-generic-hwe-16.04 (4.8.0.56.27) over (4.8.0.54.25) ...
 dpkg: error processing package isc-dhcp-common (--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-04-23 (59 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: isc-dhcp
Title: package isc-dhcp-common 4.3.3-5ubuntu12.7 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: isc-dhcp (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 isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1699630

Title:
  package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-common 4.3.3-5ubuntu12.7
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue Jun 20 04:56:26 2017
  Dependencies:
   debianutils 4.7
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   sensible-utils 0.0.9
  DuplicateSignature:
   package:isc-dhcp-common:4.3.3-5ubuntu12.7
   Unpacking linux-headers-generic-hwe-16.04 (4.8.0.56.27) over (4.8.0.54.25) 
...
   dpkg: error processing package isc-dhcp-common (--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-04-23 (59 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-common 4.3.3-5ubuntu12.7 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/isc-dhcp/+bug/1699630/+subscriptions

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

[Touch-packages] [Bug 1697187] [NEW] package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

[jesse]

Public bug reported:

Not sure happed will configuring samba?

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: isc-dhcp-common 4.3.3-5ubuntu12.7
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
AptOrdering:
 isc-dhcp-common: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Jun 10 09:29:11 2017
Dependencies:
 debianutils 4.7
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu7
 libgcc1 1:6.0.1-0ubuntu1
 sensible-utils 0.0.9
DpkgTerminalLog:
 dpkg: error processing package isc-dhcp-common (--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 2017-04-23 (47 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: isc-dhcp
Title: package isc-dhcp-common 4.3.3-5ubuntu12.7 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: isc-dhcp (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 isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1697187

Title:
  package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  Not sure happed will configuring samba?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-common 4.3.3-5ubuntu12.7
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   isc-dhcp-common: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Jun 10 09:29:11 2017
  Dependencies:
   debianutils 4.7
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
   sensible-utils 0.0.9
  DpkgTerminalLog:
   dpkg: error processing package isc-dhcp-common (--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 2017-04-23 (47 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-common 4.3.3-5ubuntu12.7 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/isc-dhcp/+bug/1697187/+subscriptions

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

[Touch-packages] [Bug 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome

[Jesse]

Confirm on my Ubuntu GNOME 17.04 machines, too. Seems to be stemming
from Google's new sign-on page. GOA, Ephiphany, and Thunderbird 45.8.0
all get similar errors, now, when trying to access a user's Google
account. Tsk tsk, Google.

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

Title:
  Cannot add a Google account using Online Accounts in Ubuntu Gnome

Status in gnome-online-accounts:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13
  laptop), I cannot add a Google account using Online-Accounts. If I
  choose to add a new Google account in Online Accounts, a window
  appears where I can enter my Google email. After entering my email and
  pressing the Next button, a window appears where I can enter my Google
  password. After entering the password and pressing the Next button, an
  empty window appears and nothing else happens. I expected this to show
  something useful, and actually add the Google account to my Gnome
  environment.

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

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

[Touch-packages] [Bug 1684973] [NEW] Crashes (segfault) under Wayland in Ubuntu GNOME 17.04

[Jesse]

Public bug reported:

While trying to run gdebi-gtk to install a .deb package, program won't
open under Wayland session. Running from terminal produces the
following:

No protocol specified
Unable to init server: Could not connect: Connection refused
No protocol specified
Unable to init server: Could not connect: Connection refused
No protocol specified
Unable to init server: Could not connect: Connection refused
Segmentation fault (core dumped)

BUG DISCOVERED RUNNING
Ubuntu GNOME 17.04 x64
GNOME 3.24.0 desktop environment
Wayland session
Linux kernel 4.10.0-19-generic

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

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

Title:
  Crashes (segfault) under Wayland in Ubuntu GNOME 17.04

Status in gdebi package in Ubuntu:
  New

Bug description:
  While trying to run gdebi-gtk to install a .deb package, program won't
  open under Wayland session. Running from terminal produces the
  following:

  No protocol specified
  Unable to init server: Could not connect: Connection refused
  No protocol specified
  Unable to init server: Could not connect: Connection refused
  No protocol specified
  Unable to init server: Could not connect: Connection refused
  Segmentation fault (core dumped)

  BUG DISCOVERED RUNNING
  Ubuntu GNOME 17.04 x64
  GNOME 3.24.0 desktop environment
  Wayland session
  Linux kernel 4.10.0-19-generic

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

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

[Touch-packages] [Bug 1681513] Re: Ubuntu 17.04: New privacy feature in NetworkManager stops some USB WiFi adapters from working (mac address randomization)

[Jesse]

Happy to oblige, Piot! :) And thanks for the update and explanation of
the bug, Simos.

I'm quite curious if a fix will be implemented, somehow, and re-packaged
in an updated ISO for Ubuntu 17.04 or Ubuntu GNOME 17.04? Might be a big
issue if WiFi doesn't work for clients out of the box, yeah?

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

Title:
  Ubuntu 17.04: New privacy feature in NetworkManager stops some USB
  WiFi adapters from working (mac address randomization)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  According to 
  
https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/
  there is a new privacy feature in the new version of NetworkManager.
  This privacy feature can cause some USB WiFi adapters to stop working
  while they used to work with older versions of NetworkManager (Ubuntu 16.10 
or older).

  The purpose of this privacy feature is to get your computer to report a new 
random MAC address whenever you connect to a WiFi network.
  This privacy feature is especially useful when you connect to public WiFi 
networks, so that the operators cannot identify you when you connect multiple 
times.

  The downside of this privacy feature is that some USB WiFi adapters misbehave 
when NetworkManager tries to change their MAC address repeatedly. 
  The result is that those USB WiFi adapters cannot connect anymore to the WiFi 
 network.

  Original report follows:

  My Panda USB wi-fi adapter works just fine on 16.10, but when I try to
  connect to my wi-fi router in 17.04, GNOME network manager reports
  "Connection failed." I did some tinkering, and noticed that my MAC
  address for my wifi adapter, according to GNOME, is DIFFERENT every
  time I make it forget my wifi settings and try to reconnect. Weird,
  right? Any leads on a possible fix or work-around?

  I'm running the latest beta of Ubuntu GNOME 17.04, kernel
  4.10.0-19-generic, GNOME 3.24.0.

  https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-
  networkmanager-1-4-0/

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

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

[Touch-packages] [Bug 1646758] Re: Can't update or install apps

[Jesse]

I'm still encountering this problem on the Nexus 4, rc-proposed channel.
Using the LGE Nexus 4, r582 build.

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

Title:
  Can't update or install apps

Status in Canonical System Image:
  Fix Released
Status in ubuntu-download-manager package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  bq M10 rc-proposed r243

  When trying to update an app this morning, I got an error about destination 
path not being writable. The app is YouTube by Mateo Salta. 
  Screenshot with the error attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1646758/+subscriptions

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

[Touch-packages] [Bug 1562269] Re: On Ubuntu touch start bluetooth / stop bluetooth hangs

[Jesse]

+1 Anyone find a workaround?

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

Title:
  On Ubuntu touch start bluetooth / stop bluetooth hangs

Status in bluez package in Ubuntu:
  New

Bug description:
  When trying to start or stop the bluetooth subsystem, the start or
  stop command just hangs.

  A couple of upgrades back, we already *had* a similar situation, now
  it re-appeared.

  However, when Control-C'ing the start command, and then trying it
  again, it says "start: Job is already running: bluetooth"

  Likewise, when Control-C'ing the stop command and then trying it
  again, it says:  "stop: Job has already been stopped: bluetooth"

  
  root@alains-pocket-penguin:~# lsb_release -rd
  Description:Ubuntu 15.04
  Release:15.04
  root@alains-pocket-penguin:~# apt-cache policy bluez
  bluez:
Installed: 5.37-0ubuntu5~overlay1
Candidate: 5.37-0ubuntu5~overlay1
Version table:
   *** 5.37-0ubuntu5~overlay1 0
 1001 
http://ppa.launchpad.net/ci-train-ppa-service/emergency-snapshot/ubuntu/ 
vivid/main armhf Packages
  100 /var/lib/dpkg/status
   4.101-0ubuntu25 0
  500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages

  What I expected to happen
   start bluetooth should start the bluetooth subsystem, and then return as 
quickly as possible
   stop bluetooth should stop the bluetooth subsystem, and then return as 
quickly as possible

  What happened instead
start bluetooth hangs... and after control-C'ing it, status bluetooth is 
"bluetooth start/starting"
stop bluetooth hangs... and after control-C'ing it, status bluetooth is 
"bluetooth stop/starting"

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

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

[Touch-packages] [Bug 1618282] Re: libgl1-mesa-dri install error

[Jesse]

** Attachment removed: "XorgLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1618282/+attachment/4730382/+files/XorgLog.txt

** Attachment removed: "XorgLogOld.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1618282/+attachment/4730383/+files/XorgLogOld.txt

** Attachment removed: "LightdmDisplayLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1618282/+attachment/4730371/+files/LightdmDisplayLog.txt

** Attachment removed: "Df.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1618282/+attachment/4730364/+files/Df.txt

** Attachment removed: "BootDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1618282/+attachment/4730360/+files/BootDmesg.txt

** Attachment removed: "Dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1618282/+attachment/4730366/+files/Dmesg.txt

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1618282/+attachment/4730380/+files/UdevDb.txt

** Attachment removed: "UdevLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1618282/+attachment/4730381/+files/UdevLog.txt

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

Title:
  libgl1-mesa-dri install error

Status in mesa package in Ubuntu:
  New

Bug description:
  Package libgl1-mesa-dri 10.1.3-0ubuntu0.6 failed to install/upgrade
  with the following error message:

  trying to overwrite shared '/etc/drirc', which is different from other
  instances of package libgl1-mesa-dri:i386

  Platform: Ubuntu 14.04 LTS.

  I was installing it as a dependency while installing
  libqt5opengl5-dev.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-66-generic x86_64
  NonfreeKernelModules: openafs
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.21
  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: Mon Aug 29 21:00:55 2016
  DistUpgraded: 2016-08-04 00:14:27,819 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: package:libgl1-mesa-dri:10.1.3-0ubuntu0.6:trying to 
overwrite shared '/etc/drirc', which is different from other instances of 
package libgl1-mesa-dri:i386
  ErrorMessage: trying to overwrite shared '/etc/drirc', which is different 
from other instances of package libgl1-mesa-dri:i386
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: Dell Radeon HD 6450 [1028:2120]
  MachineType: Dell Inc. OptiPlex 790
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-66-generic 
root=/dev/mapper/gs11709-root ro splash quiet vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 10.1.3-0ubuntu0.6 failed to install/upgrade: 
trying to overwrite shared '/etc/drirc', which is different from other 
instances of package libgl1-mesa-dri:i386
  UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 127: /usr/lib/nux/unity_support_test: error while 
loading shared libraries: libGL.so.1: cannot open shared object file: No such 
file or directory
  UpgradeStatus: Upgraded to trusty on 2016-08-04 (25 days ago)
  dmi.bios.date: 05/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0HY9JP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  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: Mon Aug 29 20:48:06 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   input  

[Touch-packages] [Bug 1618282] [NEW] libgl1-mesa-dri install error

[Jesse]

Public bug reported:

Package libgl1-mesa-dri 10.1.3-0ubuntu0.6 failed to install/upgrade with
the following error message:

trying to overwrite shared '/etc/drirc', which is different from other
instances of package libgl1-mesa-dri:i386

Platform: Ubuntu 14.04 LTS.

I was installing it as a dependency while installing libqt5opengl5-dev.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libgl1-mesa-dri 10.1.3-0ubuntu0.6
ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22
Uname: Linux 3.19.0-66-generic x86_64
NonfreeKernelModules: openafs
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.21
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: Mon Aug 29 21:00:55 2016
DistUpgraded: 2016-08-04 00:14:27,819 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DuplicateSignature: package:libgl1-mesa-dri:10.1.3-0ubuntu0.6:trying to 
overwrite shared '/etc/drirc', which is different from other instances of 
package libgl1-mesa-dri:i386
ErrorMessage: trying to overwrite shared '/etc/drirc', which is different from 
other instances of package libgl1-mesa-dri:i386
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
   Subsystem: Dell Radeon HD 6450 [1028:2120]
MachineType: Dell Inc. OptiPlex 790
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-66-generic 
root=/dev/mapper/gs11709-root ro splash quiet vt.handoff=7
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.14
SourcePackage: mesa
Title: package libgl1-mesa-dri 10.1.3-0ubuntu0.6 failed to install/upgrade: 
trying to overwrite shared '/etc/drirc', which is different from other 
instances of package libgl1-mesa-dri:i386
UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 127: /usr/lib/nux/unity_support_test: error while 
loading shared libraries: libGL.so.1: cannot open shared object file: No such 
file or directory
UpgradeStatus: Upgraded to trusty on 2016-08-04 (25 days ago)
dmi.bios.date: 05/28/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0HY9JP
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 790
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
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: Mon Aug 29 20:48:06 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputDell Dell USB Entry Keyboard KEYBOARD, id 8
 inputUSB Optical MouseMOUSE, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3.1~trusty1.1
xserver.video_driver: radeon

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


** Tags: amd64 apport-package compiz-0.9 package-conflict trusty ubuntu

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

Title:
  libgl1-mesa-dri install error

Status in mesa package in Ubuntu:
  New

Bug description:
  Package libgl1-mesa-dri 10.1.3-0ubuntu0.6 failed to install/upgrade
  with the following error message:

  trying to overwrite shared '/etc/drirc', which is different from other
  instances of package libgl1-mesa-dri:i386

  Platform: Ubuntu 14.04 LTS.

  I was installing it as a dependency while installing
  libqt5opengl5-dev.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-66-generic x86_64
  NonfreeKernelModules: openafs
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouve

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

[Jesse Hawkins]

The package name is "webbrowser-app" version
0.23+16.04.20160413-0ubuntu1

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

Title:
  Browser hangs Ubuntu 16.04

Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  When I activate Browser or click on Amazon button (which activates Browser), 
Ubuntu 16.04 hangs. This occurrence should not happen.
  An exception to this problem is that the mouse pointer is movable initially. 
In the extreme case, the mouse pointer hangs also. 

  This problem does not occur when activating Firefox or Chromium.
  Occurs in a freshly installed Ubuntu 16.04 system.
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  N: Unable to locate package pkgname

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

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

[Touch-packages] [Bug 1591510] Re: lxc-copy: unrecognized option '--backingstorage'

[Jesse Pretorius]

** Description changed:

  Description:Ubuntu 16.04 LTS
  Release:16.04
  
  lxc:
    Installed: 2.0.1-0ubuntu1~16.04.1
  linux-image-virtual:
-   Installed: 4.4.0.24.25
+   Installed: 4.4.0.24.25
  linux-image-extra-virtual:
-   Installed: 4.4.0.24.25
+   Installed: 4.4.0.24.25
  
  Man ref:
  http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html
  
  Problem:
  The man package references '-B' and '--backingstorage' as aliases of one 
another, but when the following command is executed:
  
- lxc-copy --name=cache --newname overlayfs1 --backingstorage overlay
- --snapshot
+ lxc-copy --name=cache --newname container1 --backingstorage dir
  
  The result is:
  lxc-copy: unrecognized option '--backingstorage'
  
  Expected result:
  '--backingstorage' and '-B' should be aliases and both execute correctly
  
  Existing workaround:
  Use '-B' instead.
  
  Steps to recreate:
  apt-get update && apt-get install -y lxc
  lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
- lxc-copy --name=cache --newname overlayfs1 --backingstorage overlay --snapshot
+ lxc-copy --name=cache --newname container1 --backingstorage dir

** Description changed:

  Description:Ubuntu 16.04 LTS
  Release:16.04
  
  lxc:
    Installed: 2.0.1-0ubuntu1~16.04.1
  linux-image-virtual:
    Installed: 4.4.0.24.25
  linux-image-extra-virtual:
    Installed: 4.4.0.24.25
  
  Man ref:
  http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html
  
  Problem:
  The man package references '-B' and '--backingstorage' as aliases of one 
another, but when the following command is executed:
  
+ lxc-copy --name=cache --newname container1 --backingstorage=dir
+ # as a test I also tried
  lxc-copy --name=cache --newname container1 --backingstorage dir
  
  The result is:
  lxc-copy: unrecognized option '--backingstorage'
  
  Expected result:
  '--backingstorage' and '-B' should be aliases and both execute correctly
  
  Existing workaround:
- Use '-B' instead.
+ #Use '-B' instead.
+ lxc-copy --name=cache --newname container1 -B dir
  
  Steps to recreate:
  apt-get update && apt-get install -y lxc
  lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
- lxc-copy --name=cache --newname container1 --backingstorage dir
+ lxc-copy --name=cache --newname container1 --backingstorage=dir

** Description changed:

  Description:Ubuntu 16.04 LTS
  Release:16.04
  
  lxc:
    Installed: 2.0.1-0ubuntu1~16.04.1
  linux-image-virtual:
-   Installed: 4.4.0.24.25
- linux-image-extra-virtual:
    Installed: 4.4.0.24.25
  
  Man ref:
  http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html
  
  Problem:
  The man package references '-B' and '--backingstorage' as aliases of one 
another, but when the following command is executed:
  
  lxc-copy --name=cache --newname container1 --backingstorage=dir
  # as a test I also tried
  lxc-copy --name=cache --newname container1 --backingstorage dir
  
  The result is:
  lxc-copy: unrecognized option '--backingstorage'
  
  Expected result:
  '--backingstorage' and '-B' should be aliases and both execute correctly
  
  Existing workaround:
  #Use '-B' instead.
  lxc-copy --name=cache --newname container1 -B dir
  
  Steps to recreate:
  apt-get update && apt-get install -y lxc
  lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
  lxc-copy --name=cache --newname container1 --backingstorage=dir

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

Title:
  lxc-copy: unrecognized option '--backingstorage'

Status in lxc package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 16.04 LTS
  Release:16.04

  lxc:
    Installed: 2.0.1-0ubuntu1~16.04.1
  linux-image-virtual:
    Installed: 4.4.0.24.25

  Man ref:
  http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html

  Problem:
  The man package references '-B' and '--backingstorage' as aliases of one 
another, but when the following command is executed:

  lxc-copy --name=cache --newname container1 --backingstorage=dir
  # as a test I also tried
  lxc-copy --name=cache --newname container1 --backingstorage dir

  The result is:
  lxc-copy: unrecognized option '--backingstorage'

  Expected result:
  '--backingstorage' and '-B' should be aliases and both execute correctly

  Existing workaround:
  #Use '-B' instead.
  lxc-copy --name=cache --newname container1 -B dir

  Steps to recreate:
  apt-get update && apt-get install -y lxc
  lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
  lxc-copy --name=cache --newname container1 --backingstorage=dir

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

-- 
Mailing list: https://launchpad.net/~touch-packag

[Touch-packages] [Bug 1591513] Re: lxc-copy: bdev/bdev.c: bdev_copy: 381 no such block device type: overlay

[Jesse Pretorius]

After some experimentation I've found that with no 'linux-image-extra-
virtual' package installed (whether it's installed or not makes no
difference) and all other package versions at the same level the command
does work when the backing store is specified as 'overlayfs' instead of
'overlay'.

root@lxchost-xenial3:~# lxc-copy --name=cache --newname overlayfs1 -B overlayfs 
--snapshot
root@lxchost-xenial3:~# grep rootfs /var/lib/lxc/overlayfs1/config
lxc.rootfs = overlayfs:/var/lib/lxc/cache/rootfs:/var/lib/lxc/overlayfs1/delta0
lxc.rootfs.backend = overlayfs
root@lxchost-xenial3:~# grep overlay /proc/filesystems
nodev   overlayfs
nodev   overlay
root@lxchost-xenial3:~# lxc-copy --name=cache --newname overlayfs2 -B overlay 
--snapshot
lxc-copy: bdev/bdev.c: bdev_copy: 381 no such block device type: overlay
lxc-copy: lxccontainer.c: copy_storage: 2844 Error copying storage.
clone failed

So it would appear that the backing store is supported, but the man page
and the tooling do not match in functionality.

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

Title:
  lxc-copy: bdev/bdev.c: bdev_copy: 381 no such block device type:
  overlay

Status in lxc package in Ubuntu:
  New

Bug description:
  Description: Ubuntu 16.04 LTS
  Release: 16.04

  lxc:
    Installed: 2.0.1-0ubuntu1~16.04.1
  linux-image-virtual:
Installed: 4.4.0.24.25
  linux-image-extra-virtual:
Installed: 4.4.0.24.25

  Man ref:
  http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html

  Problem:
  The man package references 'overlay' as a backing storage type, but when the 
following command is executed:

  lxc-copy --name=cache --newname overlayfs1 -B overlay --snapshot

  The result is:
  lxc-copy: bdev/bdev.c: bdev_copy: 381 no such block device type: overlay
  lxc-copy: lxccontainer.c: copy_storage: 2844 Error copying storage.
  clone failed

  Expected result:
  An overlay snapshot should be created.

  Existing workaround:
  Use the deprecated lxc-clone command instead:
  lxc-clone --snapshot --backingstore overlayfs --orig cache --new overlayfs1

  Steps to recreate:
  apt-get update && apt-get install -y lxc
  lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
  lxc-copy --name=cache --newname overlayfs1 -B overlay --snapshot

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

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

[Touch-packages] [Bug 1591510] Re: lxc-copy: unrecognized option '--backingstorage'

[Jesse Pretorius]

** Description changed:

  Description:Ubuntu 16.04 LTS
  Release:16.04
  
- linux-image-virtual:
-   Installed: 4.4.0.22.23
  lxc:
    Installed: 2.0.1-0ubuntu1~16.04.1
+ linux-image-virtual:
+   Installed: 4.4.0.24.25
+ linux-image-extra-virtual:
+   Installed: 4.4.0.24.25
  
  Man ref:
  http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html
  
  Problem:
  The man package references '-B' and '--backingstorage' as aliases of one 
another, but when the following command is executed:
  
  lxc-copy --name=cache --newname overlayfs1 --backingstorage overlay
  --snapshot
  
  The result is:
  lxc-copy: unrecognized option '--backingstorage'
  
  Expected result:
  '--backingstorage' and '-B' should be aliases and both execute correctly
  
  Existing workaround:
  Use '-B' instead.
  
  Steps to recreate:
  apt-get update && apt-get install -y lxc
  lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
  lxc-copy --name=cache --newname overlayfs1 --backingstorage overlay --snapshot

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

Title:
  lxc-copy: unrecognized option '--backingstorage'

Status in lxc package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 16.04 LTS
  Release:16.04

  lxc:
    Installed: 2.0.1-0ubuntu1~16.04.1
  linux-image-virtual:
Installed: 4.4.0.24.25
  linux-image-extra-virtual:
Installed: 4.4.0.24.25

  Man ref:
  http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html

  Problem:
  The man package references '-B' and '--backingstorage' as aliases of one 
another, but when the following command is executed:

  lxc-copy --name=cache --newname overlayfs1 --backingstorage overlay
  --snapshot

  The result is:
  lxc-copy: unrecognized option '--backingstorage'

  Expected result:
  '--backingstorage' and '-B' should be aliases and both execute correctly

  Existing workaround:
  Use '-B' instead.

  Steps to recreate:
  apt-get update && apt-get install -y lxc
  lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
  lxc-copy --name=cache --newname overlayfs1 --backingstorage overlay --snapshot

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

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

[Touch-packages] [Bug 1591513] Re: lxc-copy: bdev/bdev.c: bdev_copy: 381 no such block device type: overlay

[Jesse Pretorius]

** Description changed:

  Description: Ubuntu 16.04 LTS
  Release: 16.04
  
  lxc:
    Installed: 2.0.1-0ubuntu1~16.04.1
  linux-image-virtual:
-   Installed: 4.4.0.22.23
+   Installed: 4.4.0.24.25
+ linux-image-extra-virtual:
+   Installed: 4.4.0.24.25
  
  Man ref:
  http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html
  
  Problem:
  The man package references 'overlay' as a backing storage type, but when the 
following command is executed:
  
  lxc-copy --name=cache --newname overlayfs1 -B overlay --snapshot
  
  The result is:
  lxc-copy: bdev/bdev.c: bdev_copy: 381 no such block device type: overlay
  lxc-copy: lxccontainer.c: copy_storage: 2844 Error copying storage.
  clone failed
  
  Expected result:
  An overlay snapshot should be created.
  
  Existing workaround:
  Use the deprecated lxc-clone command instead:
  lxc-clone --snapshot --backingstore overlayfs --orig cache --new overlayfs1
  
  Steps to recreate:
  apt-get update && apt-get install -y lxc
  lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
  lxc-copy --name=cache --newname overlayfs1 -B overlay --snapshot

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

Title:
  lxc-copy: bdev/bdev.c: bdev_copy: 381 no such block device type:
  overlay

Status in lxc package in Ubuntu:
  New

Bug description:
  Description: Ubuntu 16.04 LTS
  Release: 16.04

  lxc:
    Installed: 2.0.1-0ubuntu1~16.04.1
  linux-image-virtual:
Installed: 4.4.0.24.25
  linux-image-extra-virtual:
Installed: 4.4.0.24.25

  Man ref:
  http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html

  Problem:
  The man package references 'overlay' as a backing storage type, but when the 
following command is executed:

  lxc-copy --name=cache --newname overlayfs1 -B overlay --snapshot

  The result is:
  lxc-copy: bdev/bdev.c: bdev_copy: 381 no such block device type: overlay
  lxc-copy: lxccontainer.c: copy_storage: 2844 Error copying storage.
  clone failed

  Expected result:
  An overlay snapshot should be created.

  Existing workaround:
  Use the deprecated lxc-clone command instead:
  lxc-clone --snapshot --backingstore overlayfs --orig cache --new overlayfs1

  Steps to recreate:
  apt-get update && apt-get install -y lxc
  lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
  lxc-copy --name=cache --newname overlayfs1 -B overlay --snapshot

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

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

[Touch-packages] [Bug 1591510] Re: lxc-copy: unrecognized option '--backingstorage'

[Jesse Pretorius]

** Description changed:

  Description:Ubuntu 16.04 LTS
  Release:16.04
  
+ linux-image-virtual:
+   Installed: 4.4.0.22.23
  lxc:
    Installed: 2.0.1-0ubuntu1~16.04.1
  
  Man ref:
  http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html
  
  Problem:
  The man package references '-B' and '--backingstorage' as aliases of one 
another, but when the following command is executed:
  
  lxc-copy --name=cache --newname overlayfs1 --backingstorage overlay
  --snapshot
  
  The result is:
  lxc-copy: unrecognized option '--backingstorage'
  
  Expected result:
  '--backingstorage' and '-B' should be aliases and both execute correctly
  
  Existing workaround:
  Use '-B' instead.
  
  Steps to recreate:
  apt-get update && apt-get install -y lxc
  lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
  lxc-copy --name=cache --newname overlayfs1 --backingstorage overlay --snapshot

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

Title:
  lxc-copy: unrecognized option '--backingstorage'

Status in lxc package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 16.04 LTS
  Release:16.04

  lxc:
    Installed: 2.0.1-0ubuntu1~16.04.1
  linux-image-virtual:
Installed: 4.4.0.24.25
  linux-image-extra-virtual:
Installed: 4.4.0.24.25

  Man ref:
  http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html

  Problem:
  The man package references '-B' and '--backingstorage' as aliases of one 
another, but when the following command is executed:

  lxc-copy --name=cache --newname overlayfs1 --backingstorage overlay
  --snapshot

  The result is:
  lxc-copy: unrecognized option '--backingstorage'

  Expected result:
  '--backingstorage' and '-B' should be aliases and both execute correctly

  Existing workaround:
  Use '-B' instead.

  Steps to recreate:
  apt-get update && apt-get install -y lxc
  lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
  lxc-copy --name=cache --newname overlayfs1 --backingstorage overlay --snapshot

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

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

[Touch-packages] [Bug 1591513] Re: lxc-copy: bdev/bdev.c: bdev_copy: 381 no such block device type: overlay

[Jesse Pretorius]

** Description changed:

  Description: Ubuntu 16.04 LTS
  Release: 16.04
  
  lxc:
    Installed: 2.0.1-0ubuntu1~16.04.1
+ linux-image-virtual:
+   Installed: 4.4.0.22.23
  
  Man ref:
  http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html
  
  Problem:
  The man package references 'overlay' as a backing storage type, but when the 
following command is executed:
  
  lxc-copy --name=cache --newname overlayfs1 -B overlay --snapshot
  
  The result is:
  lxc-copy: bdev/bdev.c: bdev_copy: 381 no such block device type: overlay
  lxc-copy: lxccontainer.c: copy_storage: 2844 Error copying storage.
  clone failed
  
  Expected result:
  An overlay snapshot should be created.
  
  Existing workaround:
  Use the deprecated lxc-clone command instead:
  lxc-clone --snapshot --backingstore overlayfs --orig cache --new overlayfs1
  
  Steps to recreate:
  apt-get update && apt-get install -y lxc
  lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
  lxc-copy --name=cache --newname overlayfs1 -B overlay --snapshot

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

Title:
  lxc-copy: bdev/bdev.c: bdev_copy: 381 no such block device type:
  overlay

Status in lxc package in Ubuntu:
  New

Bug description:
  Description: Ubuntu 16.04 LTS
  Release: 16.04

  lxc:
    Installed: 2.0.1-0ubuntu1~16.04.1
  linux-image-virtual:
Installed: 4.4.0.24.25
  linux-image-extra-virtual:
Installed: 4.4.0.24.25

  Man ref:
  http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html

  Problem:
  The man package references 'overlay' as a backing storage type, but when the 
following command is executed:

  lxc-copy --name=cache --newname overlayfs1 -B overlay --snapshot

  The result is:
  lxc-copy: bdev/bdev.c: bdev_copy: 381 no such block device type: overlay
  lxc-copy: lxccontainer.c: copy_storage: 2844 Error copying storage.
  clone failed

  Expected result:
  An overlay snapshot should be created.

  Existing workaround:
  Use the deprecated lxc-clone command instead:
  lxc-clone --snapshot --backingstore overlayfs --orig cache --new overlayfs1

  Steps to recreate:
  apt-get update && apt-get install -y lxc
  lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
  lxc-copy --name=cache --newname overlayfs1 -B overlay --snapshot

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

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

[Touch-packages] [Bug 1591510] Re: lxc-copy: unrecognized option '--backingstorage'

[Jesse Pretorius]

** Description changed:

  Description:Ubuntu 16.04 LTS
  Release:16.04
  
  lxc:
    Installed: 2.0.1-0ubuntu1~16.04.1
  
  Man ref:
  http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html
  
  Problem:
  The man package references '-B' and '--backingstorage' as aliases of one 
another, but when the following command is executed:
  
  lxc-copy --name=cache --newname overlayfs1 --backingstorage overlay
  --snapshot
  
  The result is:
  lxc-copy: unrecognized option '--backingstorage'
  
  Expected result:
  '--backingstorage' and '-B' should be aliases and both execute correctly
  
  Existing workaround:
  Use '-B' instead.
  
  Steps to recreate:
+ apt-get update && apt-get install -y lxc
  lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
  lxc-copy --name=cache --newname overlayfs1 --backingstorage overlay --snapshot

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

Title:
  lxc-copy: unrecognized option '--backingstorage'

Status in lxc package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 16.04 LTS
  Release:16.04

  lxc:
    Installed: 2.0.1-0ubuntu1~16.04.1

  Man ref:
  http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html

  Problem:
  The man package references '-B' and '--backingstorage' as aliases of one 
another, but when the following command is executed:

  lxc-copy --name=cache --newname overlayfs1 --backingstorage overlay
  --snapshot

  The result is:
  lxc-copy: unrecognized option '--backingstorage'

  Expected result:
  '--backingstorage' and '-B' should be aliases and both execute correctly

  Existing workaround:
  Use '-B' instead.

  Steps to recreate:
  apt-get update && apt-get install -y lxc
  lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
  lxc-copy --name=cache --newname overlayfs1 --backingstorage overlay --snapshot

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

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

[Touch-packages] [Bug 1591513] [NEW] lxc-copy: bdev/bdev.c: bdev_copy: 381 no such block device type: overlay

[Jesse Pretorius]

Public bug reported:

Description: Ubuntu 16.04 LTS
Release: 16.04

lxc:
  Installed: 2.0.1-0ubuntu1~16.04.1

Man ref:
http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html

Problem:
The man package references 'overlay' as a backing storage type, but when the 
following command is executed:

lxc-copy --name=cache --newname overlayfs1 -B overlay --snapshot

The result is:
lxc-copy: bdev/bdev.c: bdev_copy: 381 no such block device type: overlay
lxc-copy: lxccontainer.c: copy_storage: 2844 Error copying storage.
clone failed

Expected result:
An overlay snapshot should be created.

Existing workaround:
Use the deprecated lxc-clone command instead:
lxc-clone --snapshot --backingstore overlayfs --orig cache --new overlayfs1

Steps to recreate:
apt-get update && apt-get install -y lxc
lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
lxc-copy --name=cache --newname overlayfs1 -B overlay --snapshot

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

** Description changed:

  Description: Ubuntu 16.04 LTS
  Release: 16.04
  
  lxc:
-   Installed: 2.0.1-0ubuntu1~16.04.1
+   Installed: 2.0.1-0ubuntu1~16.04.1
  
  Man ref:
  http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html
  
  Problem:
  The man package references 'overlay' as a backing storage type, but when the 
following command is executed:
  
  lxc-copy --name=cache --newname overlayfs1 -B overlay --snapshot
  
  The result is:
  lxc-copy: bdev/bdev.c: bdev_copy: 381 no such block device type: overlay
  lxc-copy: lxccontainer.c: copy_storage: 2844 Error copying storage.
  clone failed
  
  Expected result:
  An overlay snapshot should be created.
  
  Existing workaround:
  Use the deprecated lxc-clone command instead:
  lxc-clone --snapshot --backingstore overlayfs --orig cache --new overlayfs1
  
  Steps to recreate:
+ apt-get update && apt-get install -y lxc
  lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
  lxc-copy --name=cache --newname overlayfs1 -B overlay --snapshot

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

Title:
  lxc-copy: bdev/bdev.c: bdev_copy: 381 no such block device type:
  overlay

Status in lxc package in Ubuntu:
  New

Bug description:
  Description: Ubuntu 16.04 LTS
  Release: 16.04

  lxc:
    Installed: 2.0.1-0ubuntu1~16.04.1

  Man ref:
  http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html

  Problem:
  The man package references 'overlay' as a backing storage type, but when the 
following command is executed:

  lxc-copy --name=cache --newname overlayfs1 -B overlay --snapshot

  The result is:
  lxc-copy: bdev/bdev.c: bdev_copy: 381 no such block device type: overlay
  lxc-copy: lxccontainer.c: copy_storage: 2844 Error copying storage.
  clone failed

  Expected result:
  An overlay snapshot should be created.

  Existing workaround:
  Use the deprecated lxc-clone command instead:
  lxc-clone --snapshot --backingstore overlayfs --orig cache --new overlayfs1

  Steps to recreate:
  apt-get update && apt-get install -y lxc
  lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
  lxc-copy --name=cache --newname overlayfs1 -B overlay --snapshot

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

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

[Touch-packages] [Bug 1591510] [NEW] lxc-copy: unrecognized option '--backingstorage'

[Jesse Pretorius]

Public bug reported:

Description:Ubuntu 16.04 LTS
Release:16.04

lxc:
  Installed: 2.0.1-0ubuntu1~16.04.1

Man ref:
http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html

Problem:
The man package references '-B' and '--backingstorage' as aliases of one 
another, but when the following command is executed:

lxc-copy --name=cache --newname overlayfs1 --backingstorage overlay
--snapshot

The result is:
lxc-copy: unrecognized option '--backingstorage'

Expected result:
'--backingstorage' and '-B' should be aliases and both execute correctly

Existing workaround:
Use '-B' instead.

Steps to recreate:
lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
lxc-copy --name=cache --newname overlayfs1 --backingstorage overlay --snapshot

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

** Description changed:

  Description:Ubuntu 16.04 LTS
  Release:16.04
  
  lxc:
-   Installed: 2.0.1-0ubuntu1~16.04.1
+   Installed: 2.0.1-0ubuntu1~16.04.1
  
  Man ref:
  http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html
  
  Problem:
  The man package references '-B' and '--backingstorage' as aliases of one 
another, but when the following command is executed:
  
  lxc-copy --name=cache --newname overlayfs1 --backingstorage overlay
  --snapshot
  
  The result is:
  lxc-copy: unrecognized option '--backingstorage'
  
  Expected result:
  '--backingstorage' and '-B' should be aliases and both execute correctly
  
  Existing workaround:
  Use '-B' instead.
+ 
+ Steps to recreate:
+ lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
+ lxc-copy --name=cache --newname overlayfs1 --backingstorage overlay --snapshot

** Summary changed:

- Ubuntu Xenial: lxc-copy: unrecognized option '--backingstorage'
+ lxc-copy: unrecognized option '--backingstorage'

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

Title:
  lxc-copy: unrecognized option '--backingstorage'

Status in lxc package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 16.04 LTS
  Release:16.04

  lxc:
    Installed: 2.0.1-0ubuntu1~16.04.1

  Man ref:
  http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html

  Problem:
  The man package references '-B' and '--backingstorage' as aliases of one 
another, but when the following command is executed:

  lxc-copy --name=cache --newname overlayfs1 --backingstorage overlay
  --snapshot

  The result is:
  lxc-copy: unrecognized option '--backingstorage'

  Expected result:
  '--backingstorage' and '-B' should be aliases and both execute correctly

  Existing workaround:
  Use '-B' instead.

  Steps to recreate:
  lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
  lxc-copy --name=cache --newname overlayfs1 --backingstorage overlay --snapshot

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

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

[Touch-packages] [Bug 1578488] [NEW] package shared-mime-info 1.5-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

[Jesse Gonzalez]

Public bug reported:

This appeared after a do-release upgrade.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shared-mime-info 1.5-2
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Thu May  5 00:13:38 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 127
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.5-2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 127
UpgradeStatus: Upgraded to xenial on 2016-05-05 (0 days ago)

** Affects: shared-mime-info (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 shared-mime-info in
Ubuntu.
https://bugs.launchpad.net/bugs/1578488

Title:
  package shared-mime-info 1.5-2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 127

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

Bug description:
  This appeared after a do-release upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shared-mime-info 1.5-2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May  5 00:13:38 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.5-2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 127
  UpgradeStatus: Upgraded to xenial on 2016-05-05 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1578488/+subscriptions

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

[Touch-packages] [Bug 1549363] Re: Unprivileged LXC will not start after today's updates

[Jesse Sung]

Unprivileged LXC still fails to start here...

kernel: 4.4.0-9.24
lxc: 2.0.0~rc4-0ubuntu1

$ lxc-start -d -n i386-trusty-gui 
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 346 To get more details, run the container in 
foreground mode.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.

$ lxc-start -F -n i386-trusty-gui 
lxc-start: cgfs.c: lxc_cgroupfs_create: 882 Could not set clone_children to 1 
for cpuset hierarchy in parent cgroup.
lxc-start: cgfs.c: cgroup_rmdir: 208 Permission denied - cgroup_rmdir: failed 
to delete /sys/fs/cgroup/memory/user.slice
lxc-start: cgfs.c: cgroup_rmdir: 208 Read-only file system - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/perf_event/
lxc-start: cgfs.c: cgroup_rmdir: 208 Read-only file system - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/net_cls,net_prio/
lxc-start: cgfs.c: cgroup_rmdir: 208 Read-only file system - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/freezer/
lxc-start: cgfs.c: cgroup_rmdir: 208 Permission denied - cgroup_rmdir: failed 
to delete /sys/fs/cgroup/cpu,cpuacct/user.slice
lxc-start: cgfs.c: cgroup_rmdir: 208 Permission denied - cgroup_rmdir: failed 
to delete /sys/fs/cgroup/blkio/user.slice
lxc-start: cgfs.c: cgroup_rmdir: 208 Read-only file system - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/cpuset/
lxc-start: cgfs.c: cgroup_rmdir: 208 Read-only file system - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/hugetlb/
lxc-start: cgfs.c: cgroup_rmdir: 208 Permission denied - cgroup_rmdir: failed 
to delete /sys/fs/cgroup/devices/user.slice
lxc-start: cgfs.c: cgroup_rmdir: 208 Permission denied - cgroup_rmdir: failed 
to delete /sys/fs/cgroup/pids/user.slice/user-1000.slice/session-c2.scope
lxc-start: cgfs.c: cgroup_rmdir: 208 Permission denied - cgroup_rmdir: failed 
to delete /sys/fs/cgroup/systemd/user.slice/user-1000.slice/session-c2.scope
lxc-start: start.c: lxc_spawn: 1033 failed creating cgroups
lxc-start: start.c: __lxc_start: 1276 failed to spawn 'i386-trusty-gui'
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.

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

Title:
  Unprivileged LXC will not start after today's updates

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  After today's (Feb. 24, 2016) updates, unprivileged LXC's will no
  longer start.  Attaching 'start_lxc.out' debug log as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 2.0.0~rc2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
  Uname: Linux 4.4.0-7-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb 24 11:16:57 2016
  InstallationDate: Installed on 2013-03-18 (1072 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (119 days ago)
  modified.conffile..etc.apparmor.d.lxc.lxc.default.with.nesting: [modified]
  modified.conffile..etc.default.lxc: [modified]
  mtime.conffile..etc.apparmor.d.lxc.lxc.default.with.nesting: 
2016-02-22T17:39:08
  mtime.conffile..etc.default.lxc: 2016-02-22T17:39:08

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

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

[Touch-packages] [Bug 1441570] [NEW] System becomes unresponsive during normal usage

[Jesse Mazis]

Public bug reported:

The system becomes unresponsive (including stuttering audio, slow mouse
cursor, freezing) after an hour or so of usage (sometimes more and
sometimes less). Usage at the time was a web browser idling (observed
with both Chromium and Firefox) and a music player (Clementine) in the
background. There were no CPU intensive applications running at the
time.

I was able to capture cpu usage during an episode with the following command 
(nice set to -20).:
'while true; do ps -eo pcpu,pid,user,args | sort -k 1 -nr | head -30 >> 
logfile; echo -e "\n"`date` >> logfile; sync; sleep 1; done'
Attached is an excerpt from the generated log file.


Ubuntu Version:
Ubuntu Vivid Vervet (development branch) 15.04

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic x86_64
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Apr  8 20:15:52 2015
EcryptfsInUse: Yes
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug fonts kubuntu vivid

** Attachment added: "Logfile output"
   
https://bugs.launchpad.net/bugs/1441570/+attachment/4369312/+files/cpuusage.txt

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

Title:
  System becomes unresponsive during normal usage

Status in Ubuntu:
  New

Bug description:
  The system becomes unresponsive (including stuttering audio, slow
  mouse cursor, freezing) after an hour or so of usage (sometimes more
  and sometimes less). Usage at the time was a web browser idling
  (observed with both Chromium and Firefox) and a music player
  (Clementine) in the background. There were no CPU intensive
  applications running at the time.

  I was able to capture cpu usage during an episode with the following command 
(nice set to -20).:
  'while true; do ps -eo pcpu,pid,user,args | sort -k 1 -nr | head -30 >> 
logfile; echo -e "\n"`date` >> logfile; sync; sleep 1; done'
  Attached is an excerpt from the generated log file.

  
  Ubuntu Version:
  Ubuntu Vivid Vervet (development branch) 15.04

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr  8 20:15:52 2015
  EcryptfsInUse: Yes
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1412758] Re: mirror method should with with file location

[Jesse Pretorius]

@r0lf Agreed that it is easy enough to workaround, so I wouldn't call it
an urgent requirement - however, having to stand up a web server to host
a file in the environment is an overhead which could be avoided if using
a file was an option. When using configuration management tooling like
ansible, chef, puppet, etc the placement and changing of a local file is
useful and carries very little overhead.

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

Title:
  mirror method should with with file location

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  It'd be really great if the mirror method could be configured to use a
  local file for the mirror list.

  eg in /etc/apt/source.list.d/mysoftware.list
  deb mirror://file://apt/mirrors/mysoftware.txt trusty main

  Instead of pulling the file via http (as per current behaviour) and
  choosing a mirror from that list, apt should read the local file and
  choose from the list in the same way.

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  apt:
Installed: 1.0.1ubuntu2.6
Candidate: 1.0.1ubuntu2.6
Version table:
   *** 1.0.1ubuntu2.6 0
  500 http://mirror.rackspace.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.1ubuntu2.5 0
  500 http://mirror.rackspace.com/ubuntu/ trusty-security/main amd64 
Packages
   1.0.1ubuntu2 0
  500 http://mirror.rackspace.com/ubuntu/ trusty/main amd64 Packages

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

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

[Touch-packages] [Bug 1412758] [NEW] mirror method should with with file location

[Jesse Pretorius]

Public bug reported:

It'd be really great if the mirror method could be configured to use a
local file for the mirror list.

eg in /etc/apt/source.list.d/mysoftware.list
deb mirror://file://apt/mirrors/mysoftware.txt trusty main

Instead of pulling the file via http (as per current behaviour) and
choosing a mirror from that list, apt should read the local file and
choose from the list in the same way.

Description:Ubuntu 14.04.1 LTS
Release:14.04

apt:
  Installed: 1.0.1ubuntu2.6
  Candidate: 1.0.1ubuntu2.6
  Version table:
 *** 1.0.1ubuntu2.6 0
500 http://mirror.rackspace.com/ubuntu/ trusty-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1.0.1ubuntu2.5 0
500 http://mirror.rackspace.com/ubuntu/ trusty-security/main amd64 
Packages
 1.0.1ubuntu2 0
500 http://mirror.rackspace.com/ubuntu/ trusty/main amd64 Packages

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

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

Title:
  mirror method should with with file location

Status in apt package in Ubuntu:
  New

Bug description:
  It'd be really great if the mirror method could be configured to use a
  local file for the mirror list.

  eg in /etc/apt/source.list.d/mysoftware.list
  deb mirror://file://apt/mirrors/mysoftware.txt trusty main

  Instead of pulling the file via http (as per current behaviour) and
  choosing a mirror from that list, apt should read the local file and
  choose from the list in the same way.

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  apt:
Installed: 1.0.1ubuntu2.6
Candidate: 1.0.1ubuntu2.6
Version table:
   *** 1.0.1ubuntu2.6 0
  500 http://mirror.rackspace.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.1ubuntu2.5 0
  500 http://mirror.rackspace.com/ubuntu/ trusty-security/main amd64 
Packages
   1.0.1ubuntu2 0
  500 http://mirror.rackspace.com/ubuntu/ trusty/main amd64 Packages

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

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

[Touch-packages] [Bug 1315369]

[Jesse Barnes]

I guess this one is either fixed or dead.

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

Title:
  Log in not available after lock screen with multi-monitor

Status in Unity:
  Invalid
Status in X.org xf86-video-intel:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed
Status in unity source package in Trusty:
  Confirmed

Bug description:
  After the screen locks I am unable to log back in because the screen
  with the login prompt is black, and the screen on my laptop just shows
  the Ubuntu logo.

  Furthermore, if I then unplug the external monitor (in an attempt to
  force the log in option to be displayed on the laptop)  the laptop
  screen then goes black and I can't do anything at all.

  I can't reproduce this if I select "lock screen" from the UI, but it
  happens reliably if it locks due to inactivity.

  Other info:
  - I am running a fresh install of 14.04
  - I have it set to lock after 5 min of inactivity, and require login after 
lock
  - I have an external monitor, configured to be on the left side of the laptop 
screen
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jane   2184 F pulseaudio
   /dev/snd/controlC0:  jane   2184 F pulseaudio
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=61f52096-031e-4e3d-b1ae-e504b3b3edec
  InstallationDate: Installed on 2014-05-01 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: Dell Inc. Dell System XPS L321X
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  PackageArchitecture: i386
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  Tags:  trusty trusty
  Uname: Linux 3.13.0-24-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 085X6F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd04/09/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L321X
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1361065] [NEW] [Satellite C855, Realtek ALC269VB, Black Headphone Out, Right] Underruns, dropouts or crackling sound

[Jesse Partridge]

Public bug reported:

While watching Amazon Instant Video, and Youtube, sound would go silent
for a half second, at intervals ranging from 10 to 30 seconds.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pulseaudio 1:4.0-0ubuntu11
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  immovableforce   2583 F pulseaudio
CurrentDesktop: Unity
Date: Mon Aug 25 00:18:24 2014
InstallationDate: Installed on 2014-08-02 (23 days ago)
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Right
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_SpeakerTestPulseStderr: W r i t e   e r r o r :   - 3 2 , B r o k e n   
p i p e
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [Satellite C855, Realtek ALC269VB, Black Headphone Out, Right] 
Underruns, dropouts or crackling sound
UpgradeStatus: Upgraded to trusty on 2014-08-15 (10 days ago)
dmi.bios.date: 01/14/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.60
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: MP
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.60:bd01/14/2013:svnTOSHIBA:pnSatelliteC855:pvrPSC72U-011008:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite C855
dmi.product.version: PSC72U-011008
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug trusty

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

Title:
  [Satellite C855, Realtek ALC269VB, Black Headphone Out, Right]
  Underruns, dropouts or crackling sound

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  While watching Amazon Instant Video, and Youtube, sound would go
  silent for a half second, at intervals ranging from 10 to 30 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  immovableforce   2583 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Aug 25 00:18:24 2014
  InstallationDate: Installed on 2014-08-02 (23 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_SpeakerTestPulseStderr: W r i t e   e r r o r :   - 3 2 , B r o k e n 
  p i p e
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Satellite C855, Realtek ALC269VB, Black Headphone Out, Right] 
Underruns, dropouts or crackling sound
  UpgradeStatus: Upgraded to trusty on 2014-08-15 (10 days ago)
  dmi.bios.date: 01/14/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.60
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.60:bd01/14/2013:svnTOSHIBA:pnSatelliteC855:pvrPSC72U-011008:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C855
  dmi.product.version: PSC72U-011008
  dmi.sys.vendor: TOSHIBA

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

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

[Touch-packages] [Bug 446657] Re: Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that bluetoothd sends

[Jesse Michael]

It's kind of depressing that this bug is still not fixed four and a half
years later in trusty.

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

Title:
  Bluetooth's on/off status doesn't update from the SetProperty D-Bus
  method that bluetoothd sends

Status in GNOME Bluetooth:
  New
Status in The Ubuntu Power Consumption Project:
  New
Status in “bluez” package in Ubuntu:
  Confirmed
Status in “linux” package in Ubuntu:
  Invalid
Status in “bluez” package in Fedora:
  Unknown

Bug description:
  Binary package hint: gnome-bluetooth

  Gnome's bluetooth applet should get a bluetooth device's on/off status
  through dbus from SetProperty setting sent by bluetoothd. This
  information was given in
  http://permalink.gmane.org/gmane.linux.bluez.kernel/4302 There is a
  setting controlling this feature: RememberPowered=true in
  /etc/bluetooth/main.conf

  Questions:
  Is the dbus message is even sent? If it is sent, why gnome-bluetooth doesn't 
do anything for it? Does bluez's SetProperty actually find the last (if even 
saved) bluetooth status?

  ProblemType: Bug
  Architecture: i386
  Date: Thu Oct  8 20:54:15 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: wl
  Package: gnome-bluetooth 2.28.1-0ubuntu1
  ProcEnviron:
   PATH=(custom, user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
  SourcePackage: gnome-bluetooth
  Uname: Linux 2.6.31-12-generic i686

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

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