[Touch-packages] [Bug 1565567] Re: segv in sudo_getgrgid

[Rafael David Tinoco]

This patch was exposed by:

"also_check_sudo_group.diff"

(since user was in "sudo" group and should have stopped user_in_group
before)

Right after being caused by:

commit a1663632dc5ab7e7c01e17206854b6f0ba0347dd
Author: Todd C. Miller 
Date:   Fri Jan 22 17:04:59 2016 -0700

Additional debugging for pwutil functions.

When debug messages accessed non-referenced pointer (struct passwd)
inside the node.

---

Note:

Users that can't have "struct passwd" solved should explore something
like:

---

commit d0c0662fda02260f8ffa4f59133bfe19ccd075a2
Author: Todd C. Miller 
Date:   Sun Sep 25 06:35:40 2011 -0400

If the invoking user cannot be resolved by uid fake the struct
passwd and store it in the cache so we can delref it on exit.

---

Faking it, so any other function relying on accessing the node's
structure will succeed.

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

Title:
  segv in sudo_getgrgid

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  If the user is in a group with no name (because libnss-db got removed
  and the group was defined there, for example...) then:

  the call to sudo_debug_printf in sudo_getgrgid
  (plugins/sudoers/pwutil.c, line 462) causes a SEGV when trying to get
  item->d.gr->gr_name (since item->d.gr is NULL).

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

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

[Touch-packages] [Bug 1387347] Re: sudo doesn't check for sudo group

[Rafael David Tinoco]

Pls check:

https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1565567

If facing seg-faults in Xenial.

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

Title:
  sudo doesn't check for sudo group

Status in sudo package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu, sudo is built with --enable-admin-flag to create the
  ~/.sudo_as_admin_successful after being run the first time.

  At some point, to align with Debian, the group changed from "admin" to
  "sudo", so this no longer works. A recent bash upload has fixed
  printing the blurb about using sudo in the terminal, but since the
  flag file isn't being created, the blurb always gets printed.

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

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

[Touch-packages] [Bug 1578055] [NEW] display driver

[E-Man31]

Public bug reported:

doesnt work

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.1:
 
ApportVersion: 2.14.1-0ubuntu3.19
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: Tue May  3 22:18:36 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: fglrx-core, 15.201, 4.2.0-35-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7540D] [1002:9991] 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:2aee]
InstallationDate: Installed on 2016-04-11 (22 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
MachineType: Hewlett-Packard 23-b034
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic.efi.signed 
root=UUID=23ce1006-4244-4909-961a-4ffb7c4e3d9e ro vesafb.invalid=1 
plymouth:debug nopat drm.debug=0xe
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/24/2012
dmi.bios.vendor: AMI
dmi.bios.version: 8.10
dmi.board.asset.tag: 3CR23800XM
dmi.board.name: 2AEE
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.03
dmi.chassis.asset.tag: 3CW23800XM
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAMI:bvr8.10:bd09/24/2012:svnHewlett-Packard:pn23-b034:pvr:rvnPEGATRONCORPORATION:rn2AEE:rvr1.03:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: 23-b034
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
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: Tue May  3 20:41:17 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.17.2-1ubuntu9.1~trusty1

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


** Tags: amd64 apport-bug compiz-0.9 trusty 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/1578055

Title:
  display driver

Status in xorg package in Ubuntu:
  New

Bug description:
  doesnt work

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  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: Tue May  3 22:18:36 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx-core, 15.201, 4.2.0-35-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7540D] [1002:9991] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:2aee]
  InstallationDate: Installed on 2016-04-11 (22 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Hewlett-Packard 23-b034
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic.efi.signed 
root=UUID=23ce1006-4244-4909-961a-4ffb7c4e3d9e ro vesafb.invalid=1 
plymouth:debug nopat drm.debug=0xe
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2012
  dmi.bios.vendor: AMI
  dmi.bios.version: 8.10
  dmi.board.asset.tag: 3CR23800XM
  dmi.board.name: 2AEE
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.03
  dmi.chassis.asset.tag: 3CW23800XM
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 

[Touch-packages] [Bug 1577733] Re: package libvirt-bin 1.2.2-0ubuntu13.1.17 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

[Serge Hallyn]

Thanks for that info.  The group file looks fine.  Could you please
check whether either

/etc/group.lock

or

/etc/gshadow.lock

exists?  If so, please remove them and re-try.  If not, please let us
know.

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

Title:
  package libvirt-bin 1.2.2-0ubuntu13.1.17 failed to install/upgrade:
  подпроцесс установлен сценарий post-installation возвратил код ошибки
  1

Status in libvirt package in Ubuntu:
  Incomplete
Status in shadow package in Ubuntu:
  Incomplete

Bug description:
  sudo apt-get install gnome-boxes then oops

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libvirt-bin 1.2.2-0ubuntu13.1.17
  ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
  Uname: Linux 3.13.0-85-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Tue May  3 16:58:15 2016
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2014-09-01 (609 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-3.13.0-85-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: libvirt
  Title: package libvirt-bin 1.2.2-0ubuntu13.1.17 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1578049] [NEW] std::runtime_error executing profile_appstart.sh for dialer app

[Sergio Cazzolato]

Public bug reported:

Getting the following error when profiling the following apps: dialer, 
messaging, webbrowser, system-settings and address-book.
It can be reproduced with the next build too.

phablet@ubuntu-phablet:~$ profile_appstart.sh -p  -a dialer-app
The lttng server is not accesible. Check lttng-relayd or firewall policies.
Falling back to local
Session auto-20160504-044646 created.
Traces will be written in /home/phablet/lttng-traces/auto-20160504-044646
UST event qtmir:firstFrameDrawn created in channel channel0
UST event app:* created in channel channel0
Tracing started for session auto-20160504-044646
x - 1
terminate called after throwing an instance of 'std::runtime_error'
  what():  AppID is empty
/usr/bin/profile_appstart.sh: line 79: 26694 Aborted (core 
dumped) ubuntu-app-stop ${APP_NAME}
x - 2
terminate called after throwing an instance of 'std::runtime_error'
  what():  AppID is empty
/usr/bin/profile_appstart.sh: line 79: 26875 Aborted (core 
dumped) ubuntu-app-stop ${APP_NAME}
x - 3



phablet@ubuntu-phablet:~$ system-image-cli -i

current build number: 321
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-04-27 13:56:49
version version: 321
version ubuntu: 20160427
version device: 20160329-a9bacdb
version custom: 20160324--36-54-vivid

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

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

Title:
  std::runtime_error executing profile_appstart.sh for dialer app

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Getting the following error when profiling the following apps: dialer, 
messaging, webbrowser, system-settings and address-book.
  It can be reproduced with the next build too.

  phablet@ubuntu-phablet:~$ profile_appstart.sh -p  -a dialer-app
  The lttng server is not accesible. Check lttng-relayd or firewall policies.
  Falling back to local
  Session auto-20160504-044646 created.
  Traces will be written in /home/phablet/lttng-traces/auto-20160504-044646
  UST event qtmir:firstFrameDrawn created in channel channel0
  UST event app:* created in channel channel0
  Tracing started for session auto-20160504-044646
  x - 1
  terminate called after throwing an instance of 'std::runtime_error'
what():  AppID is empty
  /usr/bin/profile_appstart.sh: line 79: 26694 Aborted (core 
dumped) ubuntu-app-stop ${APP_NAME}
  x - 2
  terminate called after throwing an instance of 'std::runtime_error'
what():  AppID is empty
  /usr/bin/profile_appstart.sh: line 79: 26875 Aborted (core 
dumped) ubuntu-app-stop ${APP_NAME}
  x - 3
  

  
  phablet@ubuntu-phablet:~$ system-image-cli -i

  current build number: 321
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-04-27 13:56:49
  version version: 321
  version ubuntu: 20160427
  version device: 20160329-a9bacdb
  version custom: 20160324--36-54-vivid

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

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

[Touch-packages] [Bug 1578048] [NEW] oops

[E-Man31]

Public bug reported:

fgrl

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.1:
 
ApportVersion: 2.14.1-0ubuntu3.19
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: Tue May  3 21:47:53 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: fglrx-core, 15.201, 4.2.0-35-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7540D] [1002:9991] 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:2aee]
InstallationDate: Installed on 2016-04-11 (22 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
MachineType: Hewlett-Packard 23-b034
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic.efi.signed 
root=UUID=23ce1006-4244-4909-961a-4ffb7c4e3d9e ro vesafb.invalid=1 
plymouth:debug nopat drm.debug=0xe
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/24/2012
dmi.bios.vendor: AMI
dmi.bios.version: 8.10
dmi.board.asset.tag: 3CR23800XM
dmi.board.name: 2AEE
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.03
dmi.chassis.asset.tag: 3CW23800XM
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAMI:bvr8.10:bd09/24/2012:svnHewlett-Packard:pn23-b034:pvr:rvnPEGATRONCORPORATION:rn2AEE:rvr1.03:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: 23-b034
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
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: Tue May  3 20:41:17 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.17.2-1ubuntu9.1~trusty1

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


** Tags: amd64 apport-bug compiz-0.9 trusty 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/1578048

Title:
  oops

Status in xorg package in Ubuntu:
  New

Bug description:
  fgrl

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  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: Tue May  3 21:47:53 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx-core, 15.201, 4.2.0-35-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7540D] [1002:9991] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:2aee]
  InstallationDate: Installed on 2016-04-11 (22 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Hewlett-Packard 23-b034
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic.efi.signed 
root=UUID=23ce1006-4244-4909-961a-4ffb7c4e3d9e ro vesafb.invalid=1 
plymouth:debug nopat drm.debug=0xe
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2012
  dmi.bios.vendor: AMI
  dmi.bios.version: 8.10
  dmi.board.asset.tag: 3CR23800XM
  dmi.board.name: 2AEE
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.03
  dmi.chassis.asset.tag: 3CW23800XM
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 

[Touch-packages] [Bug 1577435] Re: Reloading Website when switching tabs

[Launchpad Bug Tracker]

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

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

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Reloading Website when switching tabs

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Although there should be enough RAM (only the webbrowser open with
  only two tabs) the webbrowser constantly reloads the website when
  switching between tabs.

  BQ E4.5 with OTA 10.1

  Was also reported on M10, see
  https://plus.google.com/114411737424392267610/posts/4Cm1a3GzMU2

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

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

[Touch-packages] [Bug 1303906] Re: mesa 10 (and 9) has problems with KDE and intel video

[Tommy_CZ]

** Changed in: mesa (Ubuntu)
   Status: Expired => Fix Released

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

Title:
  mesa 10 (and 9) has problems with KDE and intel video

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Hi, I can see white stripes corruption, sometimes it totally break
  (fragments of windows are all over the desktop), in Ubuntu 12.04
  downgrade to mesa 8 helped, here in 14.04 I cannot do that.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libegl1-mesa 10.1.0-4ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: kwin
  CurrentDesktop: KDE
  Date: Mon Apr  7 18:33:56 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: kubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:365e]
  InstallationDate: Installed on 2014-04-07 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140406)
  MachineType: LENOVO 10104
  ProcEnviron:
   LANGUAGE=cs
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic 
root=UUID=abd146fd-217f-4f15-956c-cb4123798539 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ELKT31AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193 STD
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrELKT31AUS:bd03/21/2013:svnLENOVO:pn10104:pvrLenovoC440:rvnLENOVO:rnMAHOBAY:rvr3193STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.name: 10104
  dmi.product.version: Lenovo C440
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Apr  7 18:24:16 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8192 
   vendor LEN
  xserver.version: 2:1.15.0-1ubuntu7

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

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

[Touch-packages] [Bug 1316036] Re: cron package does not install MTA

[Launchpad Bug Tracker]

[Expired for cron (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  cron package does not install MTA

Status in cron package in Ubuntu:
  Expired

Bug description:
  I just did a fresh install of trusty and deliberately made a failing
  entry in the crontab:

  * * * * * mkdir /qwer/qwer

  In /var/syslog, this results in:

  
  May  4 16:04:01 dekker CRON[2395]: (root) CMD (mkdir /qwer/qwer)
  May  4 16:04:01 dekker CRON[2394]: (CRON) info (No MTA installed, discarding 
output)

  When I look in the documentation (https://help.ubuntu.com/14.04
  /installation-guide/amd64/ch08s05.html), it says:

 For this reason the packages exim4 and mutt will be installed by
 default (provided you did not unselect the “standard” task during
 the installation). exim4 is a combination MTA/MDA that is relatively
 small but very flexible. By default it will be configured to only
 handle e-mail local to the system itself and e-mails addressed to
 the system administrator (root account) will be delivered to the
 regular user account created during the installation.

  Still, mutt and exim4 appear not to be installed, although I did not
  exclude or remove any packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cron 3.0pl1-124ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May  5 09:52:04 2014
  InstallationDate: Installed on 2014-03-26 (39 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140325.1)
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1439106] Re: Xorg crashed with SIGABRT in pixman_region_copy()

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Xorg crashed with SIGABRT in pixman_region_copy()

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Unexplainable crashes observed on Xorg.
  Crash occured the last two days.
  Occured since updates from last week.
  Unable to use the documented Apport workflow to Report the BUG.
  Apport workflow was only partielly shown.
  Tried already sudo apport-cli -c /var/crash/_usr_bin_Xorg.0.crash

  
  Annotation 1:
  In the crash file was the package name printed, but Report a bug said:
  "2:1.15.1-0ubuntu2.7" does not exist in Ubuntu. Please choose a different 
package. If you're unsure, please select "I don't know"

  Annotation 2:
  apt-list Xorg printed out the package, but Report a bug said:
  "xorg/trusty-updates,now 1:7.7+1ubuntu8.1 amd64 [installed]" does not exist 
in Ubuntu. Please choose a different package. If you're unsure, please select 
"I don't know
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:309f]
  InstallationDate: Installed on 2014-05-27 (646 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 10BEGE
  Package: xorg 1:7.7+1ubuntu8.1 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-79-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Tags: third-party-packages trusty ubuntu compiz-0.9
  Uname: Linux 3.13.0-79-generic x86_64
  UnreportableReason: Das ist kein offizielles Ubuntu-Paket. Bitte entfernen 
Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKT71AUS
  dmi.board.name: SHARKBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 PRO
  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:bvnLENOVO:bvrFBKT71AUS:bd12/31/2013:svnLENOVO:pn10BEGE:pvrThinkCentreM83:rvnLENOVO:rnSHARKBAY:rvr0B98401PRO:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 10BEGE
  dmi.product.version: ThinkCentre M83
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1.01
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Mar  4 11:45:29 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 767 
   vendor ACR
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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

[Touch-packages] [Bug 1565567] Re: segv in sudo_getgrgid

[Rafael David Tinoco]

(3)

Unfortunately this was caused by patch:

"also_check_sudo_group.diff"

Description: also check the sudo group to create the admin flag file
Author: Marc Deslauriers 
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1387347
Updated: 2016-03-30

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

Title:
  segv in sudo_getgrgid

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  If the user is in a group with no name (because libnss-db got removed
  and the group was defined there, for example...) then:

  the call to sudo_debug_printf in sudo_getgrgid
  (plugins/sudoers/pwutil.c, line 462) causes a SEGV when trying to get
  item->d.gr->gr_name (since item->d.gr is NULL).

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

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

[Touch-packages] [Bug 1550944] Re: Xorg crash

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Since kernel 70.113 came in I have to log in twice at start up. After
  the first log in the desktop screen appears for a few seconds then
  crashes back to a black screen and then the log in screen appears
  again. After the second log in the system works normally. This is
  Ubuntu 14.04LTS 64 bit version

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Feb 28 15:57:17 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0574]
   NVIDIA Corporation GF119 [GeForce GT 620 OEM] [10de:1049] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:0977]
  InstallationDate: Installed on 2014-05-19 (650 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 660s
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-79-generic.efi.signed 
root=UUID=cc041237-8a22-4bc4-9c3d-e7e4419eb999 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0478VN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd08/24/2012:svnDellInc.:pnInspiron660s:pvr:rvnDellInc.:rn0478VN:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: Inspiron 660s
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.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 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sun Feb 28 14:39:14 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 100 
   vendor ACR
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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

[Touch-packages] [Bug 1552343] Re: bug during start-up

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  bug during start-up

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Every time I boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13
  Uname: Linux 3.19.0-51-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  352.63  Sat Nov  7 21:25:42 
PST 2015
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.1)
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Wed Mar  2 18:11:27 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1631]
  InstallationDate: Installed on 2016-01-02 (59 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Hewlett-Packard HP EliteBook 8560w
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-51-generic 
root=UUID=bdf63390-e098-43d3-bbba-b753e160656d ro persistent quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/05/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SVD Ver. F.22
  dmi.board.name: 1631
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 01.39
  dmi.chassis.asset.tag: E7121
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SVDVer.F.22:bd01/05/2012:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.39:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8560w
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  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 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: Wed Mar  2 18:06:58 2016
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.17.1-0ubuntu3.1~trusty1

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

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

[Touch-packages] [Bug 1565567] Re: segv in sudo_getgrgid

[Rafael David Tinoco]

Following execution path I get:



(1)

mode_run -> policy_check -> sudoers_policy_main -> sudoers_policy_init:
 - init_vars (fills global variable sudo_user)
 - sudo_user->pwd (from global struct passwd) will be used in "user_in_group" 
as "struct passwd" of executing user 
 - it will check whether the executing user is in a certain group (pre-reqs for 
sudo execution)

/*
 * Get a local copy of the user's struct passwd if we don't already
 * have one.
 */
if (sudo_user.pw == NULL) {
if ((sudo_user.pw = sudo_getpwnam(user_name)) == NULL) {
/*
 * It is not unusual for users to place "sudo -k" in a .logout
 * file which can cause sudo to be run during reboot after the
 * YP/NIS/NIS+/LDAP/etc daemon has died.
 */
if (sudo_mode == MODE_KILL || sudo_mode == MODE_INVALIDATE) {
sudo_warnx(U_("unknown uid: %u"), (unsigned int) user_uid);
debug_return_bool(false);
}

/* Need to make a fake struct passwd for the call to log_warningx(). */
sudo_user.pw = sudo_mkpwent(user_name, user_uid, user_gid, NULL, NULL);
unknown_user = true;
}
}

so sudo_user->pwd comes from sudo_mkpwent(user_name).

At this time, impossible that sudo_mkpwent has cached values so we have:

...
item = sudo_make_pwitem((uid_t)-1, name);

if (item == NULL) {
const size_t len = strlen(name) + 1;
if (errno != ENOENT || (item = calloc(1, sizeof(*item) + len)) == NULL) {
sudo_warnx(U_("unable to cache user %s, out of memory"), name);
debug_return_ptr(NULL);
}
item->refcnt = 1;
item->k.name = (char *) item + sizeof(*item);
memcpy(item->k.name, name, len);
/* item->d.pw = NULL; */
}
strlcpy(item->registry, key.registry, sizeof(item->registry));
switch (rbinsert(pwcache_byname, item, NULL)) {
...

Since sudo_make_pwitem relies on local authentication, and user is
coming from ldap... item = NULL.

With item being NULL, cache item item->d (union) will be filled of zeroes.
With that, item->d>pw will be a NULL pointer. 

PROBLEM:

In the future, when this cache item is recovered from redblack tree, any
reference to item->d>pw will fail.

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

Title:
  segv in sudo_getgrgid

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  If the user is in a group with no name (because libnss-db got removed
  and the group was defined there, for example...) then:

  the call to sudo_debug_printf in sudo_getgrgid
  (plugins/sudoers/pwutil.c, line 462) causes a SEGV when trying to get
  item->d.gr->gr_name (since item->d.gr is NULL).

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

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

[Touch-packages] [Bug 1565567] Re: segv in sudo_getgrgid

[Rafael David Tinoco]

(2)

Going back to backtrace we have:

mode_run -> policy_check -> sudoers_policy_main -
>create_admin_success_flag -> user_in_group (global sudo_user)

   /* Check whether the user is in the admin group. */
   if (!user_in_group(sudo_user.pw, "admin") &&
   !user_in_group(sudo_user.pw, "sudo"))
   debug_return_int(true);

and then user_in_group calls:

   if ((grlist = sudo_get_grlist(pw)) != NULL) {

if "admin" == pw->pw_gid: matched = 1, goto done.

(gdb) print sudo_user->pw->pw_gid
$5 = 7241
Not the case.

   /*
* Next check the supplementary group vector.
* It usually includes the password db group too.
*/

   for (i = 0; i < grlist->ngroups; i++) {
   if (strcasecmp(group, grlist->groups[i]) == 0) {
   matched = true;
   goto done;
   }
   }

(gdb) frame 1
#1  0x7fa01c0a7ab1 in user_in_group (pw=0x56174c050ca8, 
group=group@entry=0x7fa01c0b14c4 "admin")
at /build/sudo-g3ghsu/sudo-1.8.16/plugins/sudoers/pwutil.c:842
842 if ((grp = sudo_getgrgid(pw->pw_gid)) != NULL) {
(gdb) print grlist->ngroups
$6 = 1
(gdb) print grlist->groups[0]
$7 = 0x56174c050d7f "sudo"

This should have gone to "done" because it is "sudo".
But we are checking for "admin":

(gdb) print group
$12 = 0x7fa01c0b14c4 "admin"

In both cases it should have finished and not continued. If it
continued, it would go to “PROBLEM" (comment #6)

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

Title:
  segv in sudo_getgrgid

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  If the user is in a group with no name (because libnss-db got removed
  and the group was defined there, for example...) then:

  the call to sudo_debug_printf in sudo_getgrgid
  (plugins/sudoers/pwutil.c, line 462) causes a SEGV when trying to get
  item->d.gr->gr_name (since item->d.gr is NULL).

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

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

[Touch-packages] [Bug 1565567] Re: segv in sudo_getgrgid

[Rafael David Tinoco]

It was brought to my attention a crash just like this one. Here is my
analsysis:

## INTRODUCTION

# From plugins/sudoers/pwutil.c:

/*
 * Get a password entry by uid and allocate space for it.
 */
struct passwd *
sudo_getpwuid(uid_t uid)
{
struct cache_item key, *item;
struct rbnode *node;
debug_decl(sudo_getpwuid, SUDOERS_DEBUG_NSS)

key.k.uid = uid;
getauthregistry(IDtouser(uid), key.registry);
if ((node = rbfind(pwcache_byuid, )) != NULL) {
item = node->data;
sudo_debug_printf(SUDO_DEBUG_DEBUG,
"%s: uid %u [%s] -> user %s [%s] (cache hit)", __func__,
(unsigned int)uid, key.registry, item->d.pw->pw_name,
item->registry);
goto done;
}

being the last frame in the debugger:

#0  0x7fa01c0a6944 in sudo_getgrgid (gid=7241) at 
/build/sudo-g3ghsu/sudo-1.8.16/plugins/sudoers/pwutil.c:462
key = {refcnt = 1275378544, registry = 
"\000V\000\000\330\f\005L\027V\000\000\000\000\000", k = {uid = 7241,
gid = 7241, name = 0x28b4cb571c49 }, d = {
pw = 0x7d9d43d0, gr = 0x7d9d43d0, grlist = 0x7d9d43d0}}
item = 0x56174c050700
node = 
sudo_debug_subsys = 0
__func__ = "sudo_getgrgid"

We can see that all local variables are accessible but an union:

/*
 * Generic cache element.
 */
struct cache_item {
unsigned int refcnt;
char registry[16];
/* key */
union {
uid_t uid;
gid_t gid;
char *name;
} k;
/* datum */
union {
struct passwd *pw;
struct group *gr;
struct group_list *grlist;
} d;
};

(gdb) print item
$35 = (struct cache_item *) 0x56174c050700

(gdb) print item->d
$36 = {pw = 0x0, gr = 0x0, grlist = 0x0}

The union pointer "d" could be either a struct passwd, a struct group or
a struct group_list (union nature).

BUT, we can see that, from sudo_getpwuid, it is being used as a struct
passwd (d.pw):

sudo_debug_printf(SUDO_DEBUG_DEBUG,
"%s: uid %u [%s] -> user %s [%s] (cache hit)", __func__,
(unsigned int)uid, key.registry, item->d.pw->pw_name,
item->registry);

Meaning that, probably, the password structure, for this user, wasn't
filled in.

I can tell that because the "node" (from the tree) seems good:

if ((node = rbfind(pwcache_byuid, )) != NULL) {
item = node->data;

(gdb) print item->k
$38 = {uid = 7241, gid = 7241, name = 0x1c49 ""}

since uid 7241 and gid 7241 seems reasonable.

But not the "item->d" union.

So we are only missing:

struct passwd *pw;

>From the node.

"struct passwd" is (from /usr/include/pwd.h):

/* The passwd structure.  */
struct passwd
{
  char *pw_name;/* Username.  */
  char *pw_passwd;  /* Password.  */
  __uid_t pw_uid;   /* User ID.  */
  __gid_t pw_gid;   /* Group ID.  */
  char *pw_gecos;   /* Real name.  */
  char *pw_dir; /* Home directory.  */
  char *pw_shell;   /* Shell program.  */
};

And tells us that it is/was an easy way for the debug message to get
username from uid.

Now, lets check when this struct should have been filled in:
item comes from "node->data", a generic redblack tree node.

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

Title:
  segv in sudo_getgrgid

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  If the user is in a group with no name (because libnss-db got removed
  and the group was defined there, for example...) then:

  the call to sudo_debug_printf in sudo_getgrgid
  (plugins/sudoers/pwutil.c, line 462) causes a SEGV when trying to get
  item->d.gr->gr_name (since item->d.gr is NULL).

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

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

[Touch-packages] [Bug 1565567] Re: segv in sudo_getgrgid

[Rafael David Tinoco]

Summary:

Users coming from LDAP in groups ADMIN or SUDO will experience this
problem.

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

Title:
  segv in sudo_getgrgid

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  If the user is in a group with no name (because libnss-db got removed
  and the group was defined there, for example...) then:

  the call to sudo_debug_printf in sudo_getgrgid
  (plugins/sudoers/pwutil.c, line 462) causes a SEGV when trying to get
  item->d.gr->gr_name (since item->d.gr is NULL).

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

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

[Touch-packages] [Bug 1451728] Re: [master] kde-config-telepathy-accounts package install error

[Scarlett Clark]

Uploaded to same PPA. thanks

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in Kubuntu PPA:
  Fix Released
Status in meta-telepathy:
  Fix Released
Status in kaccounts-integration package in Ubuntu:
  In Progress
Status in kaccounts-providers package in Ubuntu:
  Confirmed
Status in ktp-accounts-kcm package in Ubuntu:
  Triaged
Status in libaccounts-glib package in Ubuntu:
  Fix Released
Status in kaccounts-providers source package in Wily:
  Triaged
Status in ktp-accounts-kcm source package in Wily:
  Triaged

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+subscriptions

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

[Touch-packages] [Bug 1387347] Re: sudo doesn't check for sudo group

[Rafael David Tinoco]

This patch caused a regression that I'm going to fully explain in case:

https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1565567

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

Title:
  sudo doesn't check for sudo group

Status in sudo package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu, sudo is built with --enable-admin-flag to create the
  ~/.sudo_as_admin_successful after being run the first time.

  At some point, to align with Debian, the group changed from "admin" to
  "sudo", so this no longer works. A recent bash upload has fixed
  printing the blurb about using sudo in the terminal, but since the
  flag file isn't being created, the blurb always gets printed.

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

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

[Touch-packages] [Bug 1571640] Re: lightdm changing resolution

[Christopher Annanie]

I am also having this problem while using Thinkpad T460s with a
2560x1440 resolution monitor.

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

Title:
  lightdm changing resolution

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Just after the upgrade to ubuntu 16.04, when lightdm starts the
  resolution is 2560x1600. Then, after about half a second it is
  automatically changed to 1280x800. This happens systematically at each
  boot. No external monitor is connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  Uname: Linux 4.5.0-040500-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 18 14:39:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (525 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago)

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

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

[Touch-packages] [Bug 1578043] [NEW] Disappearing text in certain areas.

[vik]

Public bug reported:

I've experienced this sort of bug twice today on 16.04. Attached is a
screenshot (it was quite difficult to paste a screenshot into a file and
save it with most text missing :) and xserver log/debug info. Sometimes
moving a mouse over the area makes the text appear, sometimes not.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
BootLog: /dev/sda1: clean, 860661/30769152 files, 38107309/123073521 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed May  4 13:52:35 2016
DistUpgraded: 2016-04-23 16:11:36,997 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed
 virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:2217]
InstallationDate: Installed on 2015-12-02 (154 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 20C0S1CWAU
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=bbf6846f-7622-4638-8e7e-286b6badb71d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-04-23 (10 days ago)
dmi.bios.date: 01/14/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: GQET48WW (1.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20C0S1CWAU
dmi.board.vendor: LENOVO
dmi.board.version: 0B98417 PRO
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGQET48WW(1.28):bd01/14/2016:svnLENOVO:pn20C0S1CWAU:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S1CWAU:rvr0B98417PRO:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20C0S1CWAU
dmi.product.version: ThinkPad S1 Yoga
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed May  4 11:51:56 2016
xserver.configfile: default
xserver.errors:
 Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
 Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
 Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1079 
 vendor LGD
xserver.version: 2:1.18.3-1ubuntu2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

** Attachment added: "screenshot"
   https://bugs.launchpad.net/bugs/1578043/+attachment/4654983/+files/text.png

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

Title:
  Disappearing text in certain areas.

Status in xorg package in Ubuntu:
  New

Bug description:
  I've experienced this sort of bug twice today on 16.04. Attached is a
  screenshot (it was quite difficult to paste a screenshot into a file
  and save it with most text missing :) and xserver log/debug info.
  Sometimes moving a mouse over the area makes the text appear,
  sometimes not.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda1: clean, 860661/30769152 files, 38107309/123073521 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed May  4 13:52:35 2016
  DistUpgraded: 2016-04-23 16:11:36,997 DEBUG 

[Touch-packages] [Bug 1578032] Re: package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in ufw package in Ubuntu:
  New

Bug description:
  when i start my computer,it happens the report problem,then i click it
  ,it show that

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ufw 0.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Tue May  3 23:34:43 2016
  DpkgHistoryLog:
   Start-Date: 2016-05-03  23:34:26
   Commandline: aptdaemon role='role-commit-packages' sender=':1.107'
   Upgrade: google-chrome-stable:amd64 (50.0.2661.86-1, 50.0.2661.94-1), 
ubuntu-core-launcher:amd64 (1.0.27, 1.0.27.1)
  DuplicateSignature:
   Setting up ufw (0.35-0ubuntu2) ...
   mv: '/lib/ufw/user.rules' and '/etc/ufw/user.rules' are the same file
   dpkg: error processing package ufw (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-10-30 (186 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: ufw
  Title: package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (12 days ago)
  mtime.conffile..etc.rsyslog.d.20-ufw.conf: 2015-09-09T03:01:36

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

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

[Touch-packages] [Bug 1578032] [NEW] package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[toanGa]

Public bug reported:

when i start my computer,it happens the report problem,then i click it
,it show that

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ufw 0.35-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Tue May  3 23:34:43 2016
DpkgHistoryLog:
 Start-Date: 2016-05-03  23:34:26
 Commandline: aptdaemon role='role-commit-packages' sender=':1.107'
 Upgrade: google-chrome-stable:amd64 (50.0.2661.86-1, 50.0.2661.94-1), 
ubuntu-core-launcher:amd64 (1.0.27, 1.0.27.1)
DuplicateSignature:
 Setting up ufw (0.35-0ubuntu2) ...
 mv: '/lib/ufw/user.rules' and '/etc/ufw/user.rules' are the same file
 dpkg: error processing package ufw (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2015-10-30 (186 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: ufw
Title: package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-04-22 (12 days ago)
mtime.conffile..etc.rsyslog.d.20-ufw.conf: 2015-09-09T03:01:36

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

Title:
  package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in ufw package in Ubuntu:
  New

Bug description:
  when i start my computer,it happens the report problem,then i click it
  ,it show that

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ufw 0.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Tue May  3 23:34:43 2016
  DpkgHistoryLog:
   Start-Date: 2016-05-03  23:34:26
   Commandline: aptdaemon role='role-commit-packages' sender=':1.107'
   Upgrade: google-chrome-stable:amd64 (50.0.2661.86-1, 50.0.2661.94-1), 
ubuntu-core-launcher:amd64 (1.0.27, 1.0.27.1)
  DuplicateSignature:
   Setting up ufw (0.35-0ubuntu2) ...
   mv: '/lib/ufw/user.rules' and '/etc/ufw/user.rules' are the same file
   dpkg: error processing package ufw (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-10-30 (186 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: ufw
  Title: package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (12 days ago)
  mtime.conffile..etc.rsyslog.d.20-ufw.conf: 2015-09-09T03:01:36

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

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

[Touch-packages] [Bug 1577733] Re: package libvirt-bin 1.2.2-0ubuntu13.1.17 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

[Vladimir Gorelov]

[2/3] Requested file(s): All files under /etc/apt/sources.list.d/

** Attachment added: "sources.list.d.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1577733/+attachment/4654950/+files/sources.list.d.tar.gz

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

Title:
  package libvirt-bin 1.2.2-0ubuntu13.1.17 failed to install/upgrade:
  подпроцесс установлен сценарий post-installation возвратил код ошибки
  1

Status in libvirt package in Ubuntu:
  Incomplete
Status in shadow package in Ubuntu:
  Incomplete

Bug description:
  sudo apt-get install gnome-boxes then oops

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libvirt-bin 1.2.2-0ubuntu13.1.17
  ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
  Uname: Linux 3.13.0-85-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Tue May  3 16:58:15 2016
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2014-09-01 (609 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-3.13.0-85-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: libvirt
  Title: package libvirt-bin 1.2.2-0ubuntu13.1.17 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1577733] Re: package libvirt-bin 1.2.2-0ubuntu13.1.17 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

[Vladimir Gorelov]

[3/3] Requested file(s): /etc/group

** Attachment added: "group"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1577733/+attachment/4654964/+files/group

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

Title:
  package libvirt-bin 1.2.2-0ubuntu13.1.17 failed to install/upgrade:
  подпроцесс установлен сценарий post-installation возвратил код ошибки
  1

Status in libvirt package in Ubuntu:
  Incomplete
Status in shadow package in Ubuntu:
  Incomplete

Bug description:
  sudo apt-get install gnome-boxes then oops

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libvirt-bin 1.2.2-0ubuntu13.1.17
  ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
  Uname: Linux 3.13.0-85-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Tue May  3 16:58:15 2016
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2014-09-01 (609 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-3.13.0-85-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: libvirt
  Title: package libvirt-bin 1.2.2-0ubuntu13.1.17 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1577733] Re: package libvirt-bin 1.2.2-0ubuntu13.1.17 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

[Vladimir Gorelov]

[1/3] Requested file(s): /etc/apt/sources.list

This is local mirror of ubuntu repositories.

** Attachment added: "sources.list"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1577733/+attachment/4654949/+files/sources.list

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

Title:
  package libvirt-bin 1.2.2-0ubuntu13.1.17 failed to install/upgrade:
  подпроцесс установлен сценарий post-installation возвратил код ошибки
  1

Status in libvirt package in Ubuntu:
  Incomplete
Status in shadow package in Ubuntu:
  Incomplete

Bug description:
  sudo apt-get install gnome-boxes then oops

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libvirt-bin 1.2.2-0ubuntu13.1.17
  ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
  Uname: Linux 3.13.0-85-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Tue May  3 16:58:15 2016
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2014-09-01 (609 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-3.13.0-85-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: libvirt
  Title: package libvirt-bin 1.2.2-0ubuntu13.1.17 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1543467] Re: Unity8 can't correctly display multi-surface apps (including menus and tooltips)

[Daniel van Vugt]

Even without menus and tooltips, try this test case which should open
three different coloured windows:

mir_demo_client_multiwin -- --desktop_file_hint=unity8

** Summary changed:

- Unity8 can't display multi-surface apps (including menus and tooltips)
+ Unity8 can't correctly display multi-surface apps (including menus and 
tooltips)

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

Title:
  Unity8 can't correctly display multi-surface apps (including menus and
  tooltips)

Status in QtMir:
  Triaged
Status in qtmir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Unity8 can't display multi-surface apps (including menus and
  tooltips).

  Fixing bug 1497085 was a great start. However instead of crashing
  Unity8 now just shows the most recently created window by the app in
  the apps /single window/, and stretches it too. When such a secondary
  window like a menu or tooltip closes, you never get back to the
  original app window. So existing apps still aren't quite usable yet.

  Test case:
  sudo apt-get install mir-demos
  mir_demo_client_multiwin -- --desktop_file_hint=unity8

  Expected: Three windows (red, green, blue)
  Observed: Only the blue window

  You can also experience the same bug with lots of apps via:  Xmir
  -rootless under Unity8.

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

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

[Touch-packages] [Bug 1578027] [NEW] i cannot set hdmi second monitor correctly

[Marcelo Hamra]

Public bug reported:

it was working ok. I've moved to other hdmi device and after that
couldn't configure the screen resolution again returning to the first
hdmi tv that I was using

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed May  4 00:06:28 2016
InstallationDate: Installed on 2016-01-14 (110 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug wily

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

Title:
  i cannot set hdmi second monitor correctly

Status in xorg package in Ubuntu:
  New

Bug description:
  it was working ok. I've moved to other hdmi device and after that
  couldn't configure the screen resolution again returning to the first
  hdmi tv that I was using

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed May  4 00:06:28 2016
  InstallationDate: Installed on 2016-01-14 (110 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1575516] Re: Mir is just a black screen and mouse cursor on Nvidia GTX 900

[Daniel van Vugt]

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

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

Title:
  Mir is just a black screen and mouse cursor on Nvidia GTX 900

Status in Mir:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  New

Bug description:
  Nvidia (using nouveau not binary drivers): Mir servers freeze on
  start-up for 30 seconds, and then you get just a black screen and
  mouse cursor (which at least moves).

  Using lp:mir r3480 ...

  [2016-04-27 15:20:19.369559] mirserver: Selected driver: mir:mesa-kms 
(version 0.22.0)
  nvc0_screen_create:762 - Error allocating PGRAPH context for M2MF: -22
  [2016-04-27 15:20:51.934145] mirserver: Using hardware cursor
  [2016-04-27 15:20:51.937691] mirserver: Initial display configuration:
  [2016-04-27 15:20:51.937703] mirserver:   0.36: unused DVI-I
  [2016-04-27 15:20:51.937713] mirserver:   0.39: DVI-D 24.0" 520x320mm
  [2016-04-27 15:20:51.937722] mirserver: Current mode 1920x1200 59.95Hz
  [2016-04-27 15:20:51.937731] mirserver: Preferred mode 1920x1200 
59.95Hz
  [2016-04-27 15:20:51.937740] mirserver: Logical position +0+0
  [2016-04-27 15:20:51.937781] mirserver:   0.41: unused HDMI-A
  [2016-04-27 15:20:51.937799] mirserver:   0.43: unused DisplayPort
  [2016-04-27 15:20:51.937972] mircommon: Loading modules from: 
bin/../lib/server-modules/
  [2016-04-27 15:20:51.938015] mircommon: Loading module: 
bin/../lib/server-modules/graphics-android.so.9
  [2016-04-27 15:20:51.938107]  mircommon: Failed to load module: 
bin/../lib/server-modules/graphics-android.so.9 (error was:libhardware.so.2: 
cannot open shared object file: No such file or directory)
  [2016-04-27 15:20:51.938119] mircommon: Loading module: 
bin/../lib/server-modules/graphics-mesa-kms.so.9
  [2016-04-27 15:20:51.938142] mircommon: Loading module: 
bin/../lib/server-modules/server-mesa-x11.so.9
  [2016-04-27 15:20:51.938536] mircommon: Loading module: 
bin/../lib/server-modules/input-evdev.so.5
  [2016-04-27 15:20:51.955316] mirserver: Selected input driver: 
mir:evdev-input (version: 0.22.0)
  [2016-04-27 15:20:51.955500] mirserver: Mir version 0.22.0
  [2016-04-27 15:20:51.962627] GLRenderer: EGL vendor: Mesa Project
  [2016-04-27 15:20:51.962645] GLRenderer: EGL version: 1.4 (DRI2)
  [2016-04-27 15:20:51.962651] GLRenderer: EGL client APIs: OpenGL OpenGL_ES 
OpenGL_ES2 OpenGL_ES3
  [2016-04-27 15:20:51.962657] GLRenderer: EGL extensions: EGL_EXT_buffer_age 
EGL_EXT_image_dma_buf_import EGL_KHR_create_context 
EGL_KHR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image 
EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image 
EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_surfaceless_context 
EGL_MESA_configless_context EGL_MESA_image_dma_buf_export
  [2016-04-27 15:20:51.962670] GLRenderer: GL vendor: VMware, Inc.
  [2016-04-27 15:20:51.962679] GLRenderer: GL renderer: Gallium 0.4 on llvmpipe 
(LLVM 3.8, 256 bits)
  [2016-04-27 15:20:51.962688] GLRenderer: GL version: OpenGL ES 3.0 Mesa 11.2.0
  [2016-04-27 15:20:51.962697] GLRenderer: GLSL version: OpenGL ES GLSL ES 3.00

  lspci:
  01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] 
(rev a1)

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

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

[Touch-packages] [Bug 1577208] Re: light-locker-settings crashes

[Robert Ancell]

** Package changed: lightdm (Ubuntu) => light-locker (Ubuntu)

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

Title:
  light-locker-settings crashes

Status in light-locker package in Ubuntu:
  Confirmed

Bug description:
  light-locker-settings is a python program (available from the
  'Preferences' menu) that uses a third-party module called 'psutils'.
  This module at one point had a method named 'get_pid_list()' which was
  renamed to 'pids()'. The old name was deprecated at least two years
  ago and then completely removed in the 3.0 release of psutils last
  June. light-locker-settings uses the old method name in line 219 of
  light-locker-settings.py, resulting in the following exception stack:

  london@england:~$ light-locker-settings 
  
/usr/share/light-locker-settings/light-locker-settings/light-locker-settings.py:29:
 PyGIWarning: Gtk was imported without specifying a version first. Use 
gi.require_version('Gtk', '3.0') before import to ensure that the right version 
gets loaded.
from gi.repository import Gtk, GLib, Gio
  Traceback (most recent call last):
File 
"/usr/share/light-locker-settings/light-locker-settings/light-locker-settings.py",
 line 697, in 
  main = LightLockerSettings()
File 
"/usr/share/light-locker-settings/light-locker-settings/light-locker-settings.py",
 line 98, in __init__
  self.init_settings()
File 
"/usr/share/light-locker-settings/light-locker-settings/light-locker-settings.py",
 line 454, in init_settings
  if self.check_running_process("xfce4-power-manager"):
File 
"/usr/share/light-locker-settings/light-locker-settings/light-locker-settings.py",
 line 219, in check_running_process
  for pid in psutil.get_pid_list():
  AttributeError: 'module' object has no attribute 'get_pid_list'
  london@england:~$ 

  The easy fix is to simply replace 'get_pid_list' with 'pids'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sun May  1 13:20:17 2016
  InstallationDate: Installed on 2016-05-01 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  LightdmConfig:
   [Seat:*]
   autologin-guest=false
   autologin-user=london
   autologin-user-timeout=0
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-05-01 (0 days ago)

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

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

[Touch-packages] [Bug 1556763] Re: [regression] [OTA-10] Touch scrolling the dash is stuttery again, and lag throughout Unity8 higher than it was in OTA-9

[Daniel van Vugt]

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  [regression] [OTA-10] Touch scrolling the dash is stuttery again, and
  lag throughout Unity8 higher than it was in OTA-9

Status in Canonical System Image:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Committed

Bug description:
  Regression in OTA-10: Touch scrolling the dash is stuttery again, and
  lag higher than it was.

  Test case 1: Scroll the dash smoothly with a finger.
  Expected: Dash scrolls smoothly.
  Observed: Dash often jumps abruptly.

  Test case 2: Pull down/up the notification bar quickly with a finger.
  Expected: It closely matches the finger position.
  Observed: It's a long way behind.

  These issues are so familiar, it's rather obviously a regression of
  bug 1486341. And I can see the required QML_NO_TOUCH_COMPRESSION=1 has
  gone missing too.

  $ system-image-cli -i
  current build number: 387
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2016-03-14 06:38:12
  version version: 387
  version ubuntu: 20160312
  version device: 20160304.2
  version custom: 20160312

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

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

[Touch-packages] [Bug 1578015] [NEW] Yet another system hangs at shutdown (16.04)

[Lauren Weinstein]

Public bug reported:

Yet another of the annoying "system hangs at shutdown" bug reports. A
fresh complete install of 16.04. Just like the others, gets down to:

Reached target shutdown

then stops. I've tried all the workarounds discussed, including swapoff
-a, before shutdown attempt, etc. No joy. Have to hold power switch for
hard shutdown very time.

One observation of possible value. I also very recently installed 16.04
server on two other identical boxes. Neither of them exhibit this
problem and both shut down cleanly. Only this system, which is a 16.04
desktop version -- again on an identical box -- is having this problem.

Frankly, it's stuff like this that makes my efforts to move ordinary
consumers over to Linux very difficult!

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

Title:
  Yet another system hangs at shutdown (16.04)

Status in systemd package in Ubuntu:
  New

Bug description:
  Yet another of the annoying "system hangs at shutdown" bug reports. A
  fresh complete install of 16.04. Just like the others, gets down to:

  Reached target shutdown

  then stops. I've tried all the workarounds discussed, including
  swapoff -a, before shutdown attempt, etc. No joy. Have to hold power
  switch for hard shutdown very time.

  One observation of possible value. I also very recently installed
  16.04 server on two other identical boxes. Neither of them exhibit
  this problem and both shut down cleanly. Only this system, which is a
  16.04 desktop version -- again on an identical box -- is having this
  problem.

  Frankly, it's stuff like this that makes my efforts to move ordinary
  consumers over to Linux very difficult!

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

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

[Touch-packages] [Bug 1574884] Re: [webapp-container] For click packages with multiple desktop files, the single instance server prevents each instance to be run

[Alexandre Abreu]

** Branch linked: lp:~abreu-alexandre/webbrowser-app/fix-application-
name-setup

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

Title:
  [webapp-container] For click packages with multiple desktop files, the
  single instance server prevents each instance to be run

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  The container (sharing some code with the webbrowser, uses the package
  name (ignoring the app specific name) to set the application name,
  which is then used in key paths for the running app:

  - writable locations,
  - cache folders,
  - single instance server name, 
  etc.

  The issue is that for click packages with multiple desktop files (that
  are supported by the platform), some of those names prevent the
  individual apps to run properly. the single instance server name is
  wrongly based on the writablelocation folder which is in turn based on
  the applicationname. This application name is set to ignore the app
  specific name and only care about the package name which makes those
  click package file to properly run each app individually.

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

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

[Touch-packages] [Bug 1577806] Re: webbrowser app and webcontainer open under the same instance

[Alexandre Abreu]

** Branch linked: lp:~abreu-alexandre/webbrowser-app/fix-application-
name-setup

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

Title:
  webbrowser app and webcontainer open under the same instance

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  I have on xenial the webbrowser-app as my main browser; if I use the
  webapp-container for anything else it opens as a tab in the main
  browser window. If I open a container instance first, opening the
  webbrowser app opens a new tab in the container instance.

  One webcontainer example to use is
  http://bazaar.launchpad.net/~ogra/+junk/slack-webapp/files

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May  3 11:47:05 2016
  InstallationDate: Installed on 2015-08-17 (259 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: webbrowser-app
  UpgradeStatus: Upgraded to xenial on 2015-11-06 (179 days ago)

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

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

[Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK

[Gunnar Hjalmarsson]

Thanks again, tomoe_musashi and Cheng-Chia Tseng!

On 2016-05-03 18:49, tomoe_musashi wrote:
> It's great that the package install all 7 weights with similar
> required disk space as the Super OTC one.

Yeah, indeed. And it indicates that the bug resides in the "super" OTC
file.

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

Title:
  change default CJK fonts to Noto CJK

Status in Ubuntu Seeds:
  Fix Released
Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  just realize that fonts-noto-cjk is available in the repository, finally its 
packaged.
  i don't really know about korean community.
  But for Chinese and Japanese community, i think that the answer is clear.
  noto-cjk is definitely better what we had before, like fonts- wqy and 
fonts-droid.
  Android community had received these complains for years, finally they got 
them fixed on lollipop.
  Fedora also set it as default chinese font start from F21.
  and of course, i still hope that ubuntu could drop those 69-language-selector 
fontconfig files, just like what F13 did.

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

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

[Touch-packages] [Bug 1578011] [NEW] Laptop sometimes doesn't detect external monitor when docked

[vik]

Public bug reported:

Clone of https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1552040

Lenovo Thinkpad Yoga S1, with a Onelink Pro dock (problem has also
occurred on a OneLink (non-Pro) dock).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
BootLog: /dev/sda1: clean, 860723/30769152 files, 38024704/123073521 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed May  4 11:47:20 2016
DistUpgraded: 2016-04-23 16:11:36,997 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed
 virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:2217]
InstallationDate: Installed on 2015-12-02 (153 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 20C0S1CWAU
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=bbf6846f-7622-4638-8e7e-286b6badb71d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-04-23 (10 days ago)
dmi.bios.date: 01/14/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: GQET48WW (1.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20C0S1CWAU
dmi.board.vendor: LENOVO
dmi.board.version: 0B98417 PRO
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGQET48WW(1.28):bd01/14/2016:svnLENOVO:pn20C0S1CWAU:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S1CWAU:rvr0B98417PRO:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20C0S1CWAU
dmi.product.version: ThinkPad S1 Yoga
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed May  4 08:27:55 2016
xserver.configfile: default
xserver.errors:
 Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
 Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
 Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1079 
 vendor LGD
xserver.version: 2:1.18.3-1ubuntu2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  Laptop sometimes doesn't detect external monitor when docked

Status in xorg package in Ubuntu:
  New

Bug description:
  Clone of https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
  intel/+bug/1552040

  Lenovo Thinkpad Yoga S1, with a Onelink Pro dock (problem has also
  occurred on a OneLink (non-Pro) dock).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda1: clean, 860723/30769152 files, 38024704/123073521 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed May  4 11:47:20 2016
  DistUpgraded: 2016-04-23 16:11:36,997 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: 

[Touch-packages] [Bug 1577637] Re: Unity8 window shadows are too small

[Daniel van Vugt]

The argument that the mobile form factor limits the visual design of
what we see on desktop doesn't add up.

Of course you should have a different design for windowed vs phablet
modes. And of course "strength" of a shadow is not bound by its size,
but moreso by its colour, opacity and penumbra curve.

Please design a nicer shadow for desktop mode at least. Even if mobile
doesn't change.


** Changed in: ubuntu-ux
   Status: Invalid => New

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

Title:
  Unity8 window shadows are too small

Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Unity8 window shadows are too small. They don't look as nice as the
  larger shadows in Unity7 (or OS X).

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

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

[Touch-packages] [Bug 1543467] Re: Unity8 can't display multi-surface apps (including menus and tooltips)

[Daniel van Vugt]

I tested xenial with 8.12+16.04.20160401-0ubuntu1 yesterday. It doesn't
work. As you say in comment #3, smaller surfaces like menus and tooltips
don't work - they take over the whole app window rendering the app
unusable.

** Changed in: qtmir
   Status: Fix Released => Triaged

** Changed in: qtmir (Ubuntu)
   Status: Fix Released => Triaged

** Changed in: unity8 (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  Unity8 can't display multi-surface apps (including menus and tooltips)

Status in QtMir:
  Triaged
Status in qtmir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Unity8 can't display multi-surface apps (including menus and
  tooltips).

  Fixing bug 1497085 was a great start. However instead of crashing
  Unity8 now just shows the most recently created window by the app in
  the apps /single window/, and stretches it too. When such a secondary
  window like a menu or tooltip closes, you never get back to the
  original app window. So existing apps still aren't quite usable yet.

  Test case:
  sudo apt-get install mir-demos
  mir_demo_client_multiwin -- --desktop_file_hint=unity8

  Expected: Three windows (red, green, blue)
  Observed: Only the blue window

  You can also experience the same bug with lots of apps via:  Xmir
  -rootless under Unity8.

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

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

[Touch-packages] [Bug 1577844] Re: don't run ifup@.service before networking.service

[Bug Watch Updater]

** Changed in: ifupdown (Debian)
   Status: Unknown => New

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

Title:
  don't run ifup@.service before networking.service

Status in cloud-init package in Ubuntu:
  New
Status in ifupdown package in Ubuntu:
  In Progress
Status in ifupdown package in Debian:
  New

Bug description:
  ifup@.service can (and often does) run for a particular interface
  before networking.service runs. This is brittle as during early boot
  ifup is prone to fail: / might still be read-only, /var might not yet
  exist or be writable, dhclient-enter-hooks.d/ or if-up.d/ hooks might
  silently fail, etc. It is also unnecessary as networking.service will
  bring up all "auto" and all present "allow-hotplug" interfaces anyway,
  and it runs at the right time.

  We should make either 80-ifupdown.rules or ifup@.service ignore events
  until networking.service is active, or wait until after it has run
  (slower, but avoids race conditions when hotplug events happen while
  networking.service is running). Thus we need to add
  After=networking.service to ifup@.service, so that this only does
  stuff after doing the "coldplug" configuration.

  This also affects cloud-init's setup of networking: this currently
  jumps through a lot of bad hoops to make sure that ifup@ does not run
  until after cloud-init-local.service. This includes blocking udev
  rules for an indefinite time, which is racy, a potential deadlock, and
  highly non-elegant.

  https://bugs.debian.org/752919 is related to this issue.

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

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

[Touch-packages] [Bug 99127] Re: Reschedule crash report if Malone upload fails

[Colin Watson]

** Package changed: ubuntu => launchpad

** Changed in: launchpad
 Assignee: ru_bro (marikstar) => (unassigned)

** Changed in: apport (Ubuntu)
 Assignee: ru_bro (marikstar) => (unassigned)

** Changed in: apport (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Reschedule crash report if Malone upload fails

Status in Launchpad itself:
  Invalid
Status in apport package in Ubuntu:
  Triaged

Bug description:
  Apport had just detected an application crash dump and was in the
  process of uploading the crash file to malone when I encountered a
  urlopen error.

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

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

[Touch-packages] [Bug 99127] Re: Reschedule crash report if Malone upload fails

[ru_bro]

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) => ru_bro (marikstar)

** Project changed: launchpad => ubuntu

** Changed in: ubuntu
 Assignee: (unassigned) => ru_bro (marikstar)

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

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

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

Title:
  Reschedule crash report if Malone upload fails

Status in Ubuntu:
  Invalid
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Apport had just detected an application crash dump and was in the
  process of uploading the crash file to malone when I encountered a
  urlopen error.

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

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

[Touch-packages] [Bug 1577596] Re: ntpd not started by systemd

[Paul Donohue]

** Attachment added: "list-deps.txt"
   
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596/+attachment/4654853/+files/list-deps.txt

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

Title:
  ntpd not started by systemd

Status in ntp package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After updating from 14.04 to 16.04 on a number of my systems, ntpd no
  longer starts at boot on any of those systems.

  `systemctl status ntp` shows:
 ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: inactive (dead)
   Docs: man:systemd-sysv-generator(8)
  May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon.
  May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon.

  Manually starting it using `systemctl start ntp` works fine.  However,
  systemd does not seem to want to start it automatically at boot time.


  As best as I can tell based on trial and error, there is something
  special about the combination of the service being named "ntp.service"
  and the service depending on network.target.  However, I haven't been
  able to identify exactly what is causing this.

  If I copy the init script to any other name, everything works fine:
  cp /etc/init.d/ntp /etc/init.d/ntpd
  Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd"
  systemctl enable ntpd
  # After a reboot, ntpd.service is started, but ntp.service is not.

  If I remove "$network" from the "# Required-Start: $network $remote_fs
  $syslog" line in /etc/init.d/ntp, then systemd starts it automatically
  ... But of course it is started before the network comes up, so it
  fails.

  If I replace /etc/init.d/ntp with a file containing only the following, 
systemd won't try to start it automatically at boot:
  #!/bin/sh
  ### BEGIN INIT INFO
  # Provides: ntp
  # Required-Start: $network
  # Required-Stop: $network
  # Default-Start: 2 3 4 5
  # Default-Stop: 1
  # Short-Description: Start NTP daemon
  ### END INIT INFO
  echo "script was run" >> /ntp.log

  If I rename that same dummy script to /etc/init.d/ntp2, it is started
  automatically at boot.

  However, grepping the systemd source code and my systemd config files for ntp 
doesn't seem to find anything that might cause this behavior:
  /etc/systemd# grep -iR ntp *
  timesyncd.conf:#NTP=
  timesyncd.conf:#FallbackNTP=ntp.ubuntu.com
  /lib/systemd# grep -R ntp *
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd
  Binary file systemd-networkd matches
  Binary file systemd-timedated matches
  Binary file systemd-timesyncd matches

  What else can I do to debug this further?

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

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

[Touch-packages] [Bug 1577596] Re: ntpd not started by systemd

[Paul Donohue]

Attached.

Also attached the output of `systemctl list-dependencies` in case that
helps any.

$ systemctl status ntp
   ntp.service - LSB: Start NTP daemon
   Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
   Active: inactive (dead)
 Docs: man:systemd-sysv-generator(8)

May 03 19:28:45 Fusion systemd[1]: Stopped LSB: Start NTP daemon.
May 03 19:28:48 Fusion systemd[1]: Stopped LSB: Start NTP daemon.

$ systemctl is-enabled ntp
ntp.service is not a native service, redirecting to systemd-sysv-install
Executing /lib/systemd/systemd-sysv-install is-enabled ntp
enabled


** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596/+attachment/4654852/+files/journal.txt

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

Title:
  ntpd not started by systemd

Status in ntp package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After updating from 14.04 to 16.04 on a number of my systems, ntpd no
  longer starts at boot on any of those systems.

  `systemctl status ntp` shows:
 ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: inactive (dead)
   Docs: man:systemd-sysv-generator(8)
  May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon.
  May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon.

  Manually starting it using `systemctl start ntp` works fine.  However,
  systemd does not seem to want to start it automatically at boot time.


  As best as I can tell based on trial and error, there is something
  special about the combination of the service being named "ntp.service"
  and the service depending on network.target.  However, I haven't been
  able to identify exactly what is causing this.

  If I copy the init script to any other name, everything works fine:
  cp /etc/init.d/ntp /etc/init.d/ntpd
  Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd"
  systemctl enable ntpd
  # After a reboot, ntpd.service is started, but ntp.service is not.

  If I remove "$network" from the "# Required-Start: $network $remote_fs
  $syslog" line in /etc/init.d/ntp, then systemd starts it automatically
  ... But of course it is started before the network comes up, so it
  fails.

  If I replace /etc/init.d/ntp with a file containing only the following, 
systemd won't try to start it automatically at boot:
  #!/bin/sh
  ### BEGIN INIT INFO
  # Provides: ntp
  # Required-Start: $network
  # Required-Stop: $network
  # Default-Start: 2 3 4 5
  # Default-Stop: 1
  # Short-Description: Start NTP daemon
  ### END INIT INFO
  echo "script was run" >> /ntp.log

  If I rename that same dummy script to /etc/init.d/ntp2, it is started
  automatically at boot.

  However, grepping the systemd source code and my systemd config files for ntp 
doesn't seem to find anything that might cause this behavior:
  /etc/systemd# grep -iR ntp *
  timesyncd.conf:#NTP=
  timesyncd.conf:#FallbackNTP=ntp.ubuntu.com
  /lib/systemd# grep -R ntp *
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd
  Binary file systemd-networkd matches
  Binary file systemd-timedated matches
  Binary file systemd-timesyncd matches

  What else can I do to debug this further?

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

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

[Touch-packages] [Bug 1565567] Re: segv in sudo_getgrgid

[Eric Desrochers]

The segmentation fault[1] is due to a NULL pointer dereference[2] at :
sudo-1.8.16/plugins/sudoers/pwutil.c[3]

[1] Core was generated by `sudo bash'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7fa01c0a6944 in sudo_getgrgid (gid=7241)
at /build/sudo-g3ghsu/sudo-1.8.16/plugins/sudoers/pwutil.c:462
462 /build/sudo-g3ghsu/sudo-1.8.16/plugins/sudoers/pwutil.c: No such file or 
directory.


[2] (gdb) p item->d.gr
$1 = (struct group *) 0x0

[3] - sudo-1.8.16/plugins/sudoers/pwutil.c:462
449 * Get a group entry by gid and allocate space for it.
450 */
451 struct group *
452 sudo_getgrgid(gid_t gid)
453 {
454 struct cache_item key, *item;
455 struct rbnode *node;
456 debug_decl(sudo_getgrgid, SUDOERS_DEBUG_NSS)
457
458 key.k.gid = gid;
459 getauthregistry(NULL, key.registry);
460 if ((node = rbfind(grcache_bygid, )) != NULL) {
461 item = node->data;
462 sudo_debug_printf(SUDO_DEBUG_DEBUG,
463 "%s: gid %u [%s] -> group %s [%s] (cache hit)", __func__,
464 (unsigned int)gid, key.registry, item->d.gr->gr_name,
465 item->registry);
466 goto done;
467 }


Three months ago, a additional debugging for pwutil functions has been 
introduced[4] upstream.
The addition is exactly where the segfault happen. I think it is worth looking 
this commit as a starting point.

[4] https://www.sudo.ws/repos/sudo/rev/908b83c3acbb

changeset 10331:908b83c3acbb
Additional debugging for pwutil functions.
author Todd C. Miller 
date Fri, 22 Jan 2016 17:04:59 -0700 (3 months ago)
parents 5a2921412663
children 5113a3c04494
files plugins/sudoers/pwutil.c
...


Thanks,
Eric

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

Title:
  segv in sudo_getgrgid

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  If the user is in a group with no name (because libnss-db got removed
  and the group was defined there, for example...) then:

  the call to sudo_debug_printf in sudo_getgrgid
  (plugins/sudoers/pwutil.c, line 462) causes a SEGV when trying to get
  item->d.gr->gr_name (since item->d.gr is NULL).

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

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

[Touch-packages] [Bug 1436330] Fw: new message

[Ghislain Laframboise]

Hello!


You have a new message, please read 


Facebook

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

Title:
  Network Manager doesn't set metric for local networks any more,
  causing connection issues

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

Bug description:
  [Impact]
  NM changed its method of setting routes on systems, and no longer attaches a 
metric value specific to the type of device being used. These values were used 
to prioritize connections, so that for example, when connected to both wired 
and wireless at the same time, wired can be used in priority over wireless 
without incurring packet loss.
  Currently, when connected to both wired and wireless are connected to the 
same subnet, the user may notice connectivity issues since packets are sent in 
a round-robin fashion over all default routes on the same subnet with the same 
metric.

  [Test Case]
  1- Connect to a wireless network.
  2- Connect to the same network over Ethernet both connections should come up 
on the same subnet.
  3- Make sure there is no packet loss, and that there are specific metric 
values for each default route, as displayed by 'ip route'.

  [Regression Potential]
  Since handling default routes properly involves correcting the behavior for 
all device types, VPN behavior may change to pick up the default routes in all 
cases, over a wired connection. It's also possible that a connection pick up 
the default route when it is not meant to.

  ---

  With Vivid, having two connections to the same network subnet is
  unstable due to missing metrics for local networks.

  Example:

  Being connected to 192.168.1.0/24 via both wired and wireless will
  cause connectivity issues as sent packets hop between the two
  interfaces.

  It used to be that this wasn't an issue. I would go between work and
  home and plug in and my machine would automatically connect to
  wireless and it would use the lower metric ethernet interface for all
  communications, while the wlan interface would remain connected but
  unused.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 25 09:17:27 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-25 (58 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-17 (8 days ago)
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1572653] Re: keyboard does not show up on xenial

[Michael Sheldon]

Interesting, I haven't been able to reproduce it any any circumstances
other than with QT_DEVICE_PIXEL_RATIO enabled, could you post your full
"env" output?

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

Title:
  keyboard does not show up on xenial

Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  Expected behaviour:

  Install ubuntu-keyboard, run maliit-server, click on place to enter
  text -> keyboard shows up.

  What happens:

  Running maliit-server after installing ubuntu-keyboard-english in
  terminal shows following error:

  WARNING: void MIMPluginManagerPrivate::_q_setActiveSubView(const
  QString&, Maliit::HandlerState) "libubuntu-keyboard-plugin.so" "en" is
  not enabled

  Clicking on fields for entering text, does not cause the keyboard to
  show up.

  What I tried so far:

  export QT_IM_MODULE=Maliit
  export GTK_IM_MODULE=Maliit

  and

  gconftool-2 -s --type list --list-type string /maliit/onscreen/enabled 
"[llibubuntu-keyboard-plugin.so,en_gb]"
  gconftool-2 -s --type list --list-type string /maliit/onscreen/active 
"[libubuntu-keyboard-plugin.so,en_gb]"

  according to

  https://github.com/maliit/framework

  and

  https://github.com/maliit/plugins

  but it still won't show up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-keyboard 0.99.trunk.phablet2+16.04.20160226.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 20 18:03:03 2016
  InstallationDate: Installed on 2016-04-03 (16 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.maliit.org.server.conf: [modified]
  mtime.conffile..etc.xdg.maliit.org.server.conf: 2016-04-20T17:40:50.856195

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

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

[Touch-packages] [Bug 1577959] Re: Media_Life wallpaper is missing metadata ands screenshot files.

[PJSingh5000]

The correct package should be: kdeartwork-wallpapers

** Package changed: util-linux (Ubuntu) => kdeartwork (Ubuntu)

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

Title:
  Media_Life wallpaper is missing metadata ands screenshot files.

Status in kdeartwork package in Ubuntu:
  New

Bug description:
  The Media Life wallpaper in package kdeartwork-wallpapers is missing the 
following two files:
  /usr/share/wallpapers/Media_Life/metadata.desktop
  /usr/share/wallpapers/Media_Life/contents/screenshot.png

  As a result, the KDE Plasma Desktop Settings dialog in Kubuntu shows
  two thumbnails for this wallpaper.

  One thumbnail is for
  /usr/share/wallpapers/Media_Life/contents/images/2560x1080.jpg
  and the other thumbnail is for
  /usr/share/wallpapers/Media_Life/contents/images/2560x1600.jpg

  This issue affects Kubuntu Xenial Xersus 16.04.

  Distributor ID: Ubuntu
  Description: Ubuntu 16.04 LTS
  Release: 16.04
  Codename:xenial

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

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

[Touch-packages] [Bug 1577959] [NEW] Media_Life wallpaper is missing metadata ands screenshot files.

[PJSingh5000]

Public bug reported:

The Media Life wallpaper in package kdeartwork-wallpapers is missing the 
following two files:
/usr/share/wallpapers/Media_Life/metadata.desktop
/usr/share/wallpapers/Media_Life/contents/screenshot.png

As a result, the KDE Plasma Desktop Settings dialog in Kubuntu shows two
thumbnails for this wallpaper.

One thumbnail is for
/usr/share/wallpapers/Media_Life/contents/images/2560x1080.jpg
and the other thumbnail is for
/usr/share/wallpapers/Media_Life/contents/images/2560x1600.jpg

This issue affects Kubuntu Xenial Xersus 16.04.

Distributor ID: Ubuntu
Description: Ubuntu 16.04 LTS
Release: 16.04
Codename:xenial

** Affects: kdeartwork (Ubuntu)
 Importance: Undecided
 Status: 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/1577959

Title:
  Media_Life wallpaper is missing metadata ands screenshot files.

Status in kdeartwork package in Ubuntu:
  New

Bug description:
  The Media Life wallpaper in package kdeartwork-wallpapers is missing the 
following two files:
  /usr/share/wallpapers/Media_Life/metadata.desktop
  /usr/share/wallpapers/Media_Life/contents/screenshot.png

  As a result, the KDE Plasma Desktop Settings dialog in Kubuntu shows
  two thumbnails for this wallpaper.

  One thumbnail is for
  /usr/share/wallpapers/Media_Life/contents/images/2560x1080.jpg
  and the other thumbnail is for
  /usr/share/wallpapers/Media_Life/contents/images/2560x1600.jpg

  This issue affects Kubuntu Xenial Xersus 16.04.

  Distributor ID: Ubuntu
  Description: Ubuntu 16.04 LTS
  Release: 16.04
  Codename:xenial

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

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

[Touch-packages] [Bug 1577525] Re: CUPS automatically installs EVERY printer on the network

[cement_head]

Issue is ONLY with Firefox after changes made in post #4

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

Title:
  CUPS automatically installs EVERY printer on the network

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 16.04 (and 15.10) CUPS automagically installs EVERY printer
  on the network.  This is idiotic and must stop.  I NEVER want to
  automatically install every printer every time I connect to a network.

  Please make this stop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May  2 14:57:32 2016
  InstallationDate: Installed on 2016-04-28 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:068f Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Lemur
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', 
'/etc/cups/ppd/HL3040CN.ppd', '/etc/cups/ppd/HL3070CW.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied
   grep: /etc/cups/ppd/HL3040CN.ppd: Permission denied
   grep: /etc/cups/ppd/HL3070CW.ppd: Permission denied
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=52cc6985-56fb-43f9-8439-967a49db65bb ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06RS76
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Lemur
  dmi.board.vendor: System76, Inc.
  dmi.board.version: lemu6
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06RS76:bd11/29/2015:svnSystem76,Inc.:pnLemur:pvrlemu6:rvnSystem76,Inc.:rnLemur:rvrlemu6:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.name: Lemur
  dmi.product.version: lemu6
  dmi.sys.vendor: System76, Inc.

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

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

[Touch-packages] [Bug 1522057] Re: DNS resolution stops working after sometime

[Akira Tanaka]

I have the same problem when using Ubuntu 16.04.
After I disabled dnsmasq in /etc/NetworkManager/NetworkManager.conf, the name 
resolution and the Internet connection works fine.

** Tags added: xenial

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

Title:
  DNS resolution stops working after sometime

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  DNS resolution stops working after sometime (usually 10-20 minutes) in
  Lubuntu 15.10

  The problem can be temporarily corrected after restarting network-
  manager using systemctl, but it starts again after 10-20 minutes.
  Looks like network-manager is not configuring dnsmasq properly.

  Output from 'nslookup google.com':
  ~
  Server:   127.0.1.1
  Address:  127.0.1.1#53

  ** server can't find google.com: REFUSED
  ~

  Output from 'tcpdump -i lo port 53' while running above command:
  ~
  20:16:59.235879 IP localhost.38045 > comp0.arhome.info.domain: 28529+ A? 
google.com. (28)
  20:16:59.286851 IP comp0.arhome.info.domain > localhost.38045: 28529 Refused 
0/0/0 (28)
  ~

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CRDA:
   country IN: DFS-JP
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 80), (N/A, 20), (N/A)
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 20), (N/A)
  CurrentDesktop: LXDE
  Date: Wed Dec  2 20:14:32 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-25 (68 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 172.16.84.1 dev wlan0  proto static  metric 600 
   172.16.84.0/22 dev wlan0  proto kernel  scope link  src 172.16.84.50  metric 
600 
   200.1.1.2 via 172.16.84.1 dev wlan0  proto dhcp  metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to wily on 2015-11-06 (25 days ago)
  nmcli-dev:
   DEVICETYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlan0 wifi  connected/org/freedesktop/NetworkManager/Devices/1  
nn0.arhome.info  bab29dc2-8a79-4170-8253-277286712124  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--   ----   
  
   vboxnet0  ethernet  unmanaged/org/freedesktop/NetworkManager/Devices/3  
--   ----   
  
   loloopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1524893] Re: Network manager crashing, fresh install Lubuntu 15.10

[Mörgæs]

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

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

Title:
  Network manager crashing, fresh install Lubuntu 15.10

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Error occurred while connecting to smartphone as access point.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Thu Dec 10 16:59:19 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-11-29 (11 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  IpRoute:
   default via 172.20.10.1 dev wlp12s0  proto static  metric 600 
   172.20.10.0/28 dev wlp12s0  proto kernel  scope link  src 172.20.10.4  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp12s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2  
iPhone  5309ca57-1b6f-4317-a977-431288c42c67  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp9s0   ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1377096] Re: [OSK] Ubuntu Touch should allow alternative keyboard layouts

[Bernard Banko]

Should be possible by ie. having a DIY layout files simlinked to a  ~/.config/ 
folder 
See an example https://plus.google.com/+BernardBanko/posts/f9eFF3rpmtq
Another would be to have different layout in portrait and layout mode.

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

Title:
  [OSK] Ubuntu Touch should allow alternative keyboard layouts

Status in Ubuntu UX:
  Triaged
Status in ubuntu-keyboard package in Ubuntu:
  Triaged

Bug description:
  It would be nice if alternative keyboard layouts were available for
  Ubuntu Touch.

  On Android devices I use the Hacker's Keyboard
  https://code.google.com/p/hackerskeyboard/ from F-Droid
  
https://f-droid.org/repository/browse/?fdfilter=org.pocketworkstation.pckeyboard=org.pocketworkstation.pckeyboard
  as this allows customisation and easy access to keys such as Ctrl,
  Esc, !, : and - and these are keys that take a lot of key presses with
  the current Ubuntu touch keyboard (I use vim). In addition key
  combinations such as Ctrl-n and Ctrl-p (next and previous channel in
  IRSSI) are not possible with the current Ubuntu Touch keyboard.

  Having said the above the gestures, double tap for tab, swipe up, down
  , left and right for the arrow keys is great and I now find myself
  trying to use these gestures on Android devices...

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

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

Re: [Touch-packages] [Bug 1546641] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()

[william]

Em 03/05/2016 07:47, Rick Harris escreveu:
> One last thing...ice in comment #12 said:
> "Some people say it has to do with a ASMedia USB Controller"
>
> Have found that USB enumeration failure can cause a bottleneck in
> systemd getting the upower.service unit to finally start.
>
> You'll know if the system is hit with this as it'll be much slower to boot 
> and the kernel will spew errors of the type:
> kernel: usb 2-1.1: device descriptor read/64, error -110
> kernel: usb 2-1-port1: unable to enumerate USB device
>
> Occasionally after several suspend/resumes, I have a USB device
> (wireless game controller) that must be unplugged/replugged to stop this
> error (simply rebooting does not fix).
>
> Have found on my laptop, if the USB enumeration boots through without
> any error then it's quick enough to have systemd start  upower.service
> in time before u-s-d is started, otherwise the u-s-d segfault occurs as
> above.
>
> Thanks :)

That's my problem. But I will solve. If you have or found an package to 
solve this problem to people that eran less than 15 dollars a day like 
me, I would be glad. I from Brasil, we are in terrible economic crisis. 
And many of us had kids to support to. But I thank you a lot. Thanks for 
care.

GM

>

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

Title:
  unity-settings-daemon crashed with SIGSEGV in
  up_exported_daemon_get_lid_is_closed()

Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in upower package in Ubuntu:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Triaged
Status in upower source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Yakkety:
  Triaged
Status in upower source package in Yakkety:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/8ca9c548fc4e2fc1d4bf827bbd85c72df59313f8

  Ubuntu 16.04 crashes immediately on login. Default settings not
  applied and appearance is a bit ugly (incorrect font hinting, in-
  window menus etc).

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Feb 17 13:52:13 2016
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2016-02-08 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x3aae60fe69 : 
mov(%rbx),%rdi
   PC (0x3aae60fe69) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   up_exported_daemon_get_lid_is_closed () from 
/usr/lib/x86_64-linux-gnu/libupower-glib.so.3
   gsd_power_manager_start () from 
/usr/lib/unity-settings-daemon-1.0/libpower.so
   ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
   gnome_settings_plugin_info_activate ()
   ?? ()
  Title: unity-settings-daemon crashed with SIGSEGV in 
up_exported_daemon_get_lid_is_closed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1546641/+subscriptions

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

[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Benoît Vézina]

Same here dv7, closing lid, nothing happen

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

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

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

[Touch-packages] [Bug 1577940] [NEW] My Bad

[E-Man31]

Public bug reported:

I changed my display driver settings earlier, lemmee change them back b4
wasting your time

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:
 
.tmp.unity.support.test.1:
 
ApportVersion: 2.14.1-0ubuntu3.19
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: Tue May  3 14:05:49 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: fglrx-core, 15.201, 4.2.0-35-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7540D] [1002:9991] 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:2aee]
InstallationDate: Installed on 2016-04-11 (22 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
MachineType: Hewlett-Packard 23-b034
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic.efi.signed 
root=UUID=23ce1006-4244-4909-961a-4ffb7c4e3d9e ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/24/2012
dmi.bios.vendor: AMI
dmi.bios.version: 8.10
dmi.board.asset.tag: 3CR23800XM
dmi.board.name: 2AEE
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.03
dmi.chassis.asset.tag: 3CW23800XM
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAMI:bvr8.10:bd09/24/2012:svnHewlett-Packard:pn23-b034:pvr:rvnPEGATRONCORPORATION:rn2AEE:rvr1.03:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: 23-b034
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
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: Tue May  3 09:56:57 2016
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
 AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
 AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: 
No such file or directory]
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.2-1ubuntu9.1~trusty1
xserver.video_driver: fglrx

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


** Tags: amd64 apport-bug compiz-0.9 trusty 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/1577940

Title:
  My Bad

Status in xorg package in Ubuntu:
  New

Bug description:
  I changed my display driver settings earlier, lemmee change them back
  b4 wasting your time

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  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: Tue May  3 14:05:49 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx-core, 15.201, 4.2.0-35-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7540D] [1002:9991] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:2aee]
  InstallationDate: Installed on 2016-04-11 (22 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: 

[Touch-packages] [Bug 1515821] Re: Recurring Evolution events not shown as coming events in clock's menu

[Ted Gould]

Here is an event that causes this behavior for me.

BEGIN:VEVENT
UID:20151108T020045Z-4971-1001-2621-1@roku
DTSTAMP:20160401T184310Z
CREATED:20151108T020045Z
RRULE:FREQ=WEEKLY;UNTIL=20160630;BYDAY=WE
LAST-MODIFIED:20160401T184310Z
SUMMARY:Rotary
DTSTART;TZID=America/Chicago:20150701T12
DTEND;TZID=America/Chicago:20150701T13
LOCATION:First United Methodist Church\, Allen\, TX
EXDATE:20150826T12
EXDATE:20151125T12
EXDATE:20151021T12
EXDATE:20151118T12
EXDATE:20151028T12
EXDATE:20151104T12
EXDATE:20151223T12
EXDATE:20151230T12
EXDATE:20160120T12
CLASS:PUBLIC
EXDATE:20160420T12Z
END:VEVENT

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

Title:
  Recurring Evolution events not shown as coming events in clock's menu

Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  In Evolution you can make an appointment recur according to a
  specified scheme. As from wily, only the first instance of such a
  recurring event is shown in the clock menu.

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

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

[Touch-packages] [Bug 1375215] Re: System runs out of memory - white screens frequently seen in web renderers

[Michele Giacomoli]

Hi Olivier
I'm experiencing the same problem mentioned by Marcos, from 2/3 OTAs now. In my 
case you don't even need to return from another app, it happens while driving.

Thank you guys

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

Title:
  System runs out of memory - white screens frequently seen in web
  renderers

Status in Canonical System Image:
  Fix Released
Status in oxide-qt package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  [See latest comments for recent repro notes]

  krillin 14.09 #2 + all updates applied

  After running the system for a while (few minutes) the system runs out of 
memory and start killing processes.
  It is very visible with the webbrowser or webapps because it renders the page 
and displays a white page when oxide-render is killed. Although it is not 
specific to oxide, and any app are killed (address-book, system-settings, ...) 
You can clearly notice that other apps are being killed because when you switch 
to the app it's all blurry and take a while to reload, also it loses its state 
(for example, you lose the message you were writing in the messaging-app)

  There is no specific steps to reproduce. I have several scopes enabled
  (photos, nearby, news) You don't have to have tons of apps open to
  reproduce this. Launching the webbrowser or a webapps and navigating
  on the phone between the scopes and the open app seems enough for the
  system to start killing processes.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: liboxideqtcore0 1.2.0-0ubuntu1 [origin: Ubuntu RTM]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Mon Sep 29 12:51:34 2014
  InstallationDate: Installed on 2014-09-24 (5 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140924-030204)
  SourcePackage: oxide-qt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1576726] Re: [SRU]network-manager

[Bartosz Kosiorek]

After install network-manager on Ubuntu 16.04 everything is working
correctly for me:

$ apt-cache policy network-manager
network-manager:
  Zainstalowana: 1.2.0-0ubuntu0.16.04.1
  Kandydująca:   1.2.0-0ubuntu0.16.04.1
  Tabela wersji:
 *** 1.2.0-0ubuntu0.16.04.1 100
100 /var/lib/dpkg/status
 1.1.93-0ubuntu4 500
500 http://pl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages


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

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

Title:
  [SRU]network-manager

Status in network-manager package in Ubuntu:
  Fix Committed
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-openconnect package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager-applet source package in Xenial:
  Fix Committed
Status in network-manager-openconnect source package in Xenial:
  Confirmed

Bug description:
  [Impact]
  Xenial was released with upstream beta2 version of network-manager to keep in 
time for the release schedule, and upstream stable release has been made so 
it's time to update to it.

  [Testcase]
  After upgrading the package, user should still be able to connect to networks 
like Ethernet, Wi-Fi and VPNs.

  [Regression Potential]
  Potential of causing regression is relatively small because there is not big 
changes made during beta2 -> stable process.

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

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

[Touch-packages] [Bug 1202754] Re: update-manager crashed with SystemExit in exit(): 0

[maryho...@hotmail.com]

** Package changed: update-manager (Ubuntu) => click-update-manager
(Ubuntu)

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

Title:
  update-manager crashed with SystemExit in exit(): 0

Status in Ubuntu Kylin:
  Fix Released
Status in Software Updater:
  New
Status in click-update-manager package in Ubuntu:
  Fix Released

Bug description:
  Errors bucket
  
https://errors.ubuntu.com/bucket/?id=/usr/bin/update-manager:SystemExit:commit:_inline_callbacks:_show_transaction:_inline_callbacks:commit:_action_done:exit

  I was going to check for updates, but the Update-Manager has closed
  itself.

  ProblemType: CrashDistroRelease: Ubuntu 13.10
  Package: update-manager 1:0.189
  ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
  Uname: Linux 3.10.0-3-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: i386
  Date: Thu Jul 18 20:46:05 2013
  ExecutablePath: /usr/bin/update-manager
  InterpreterPath: /usr/bin/python3.3
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/update-manager --no-update 
--no-focus-on-map
  PythonArgs: ['/usr/bin/update-manager', '--no-update', 
'--no-focus-on-map']SourcePackage: update-manager
  Title: update-manager crashed with SystemExit in exit(): 0
  UpgradeStatus: Upgraded to saucy on 2013-03-21 (118 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

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

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

[Touch-packages] [Bug 1512100] Re: Blinking screen during the call if you remove the phone from your ear

[GTriderXC]

Is there already a bug for Aquaris? Mine is fully updated and I
experienced the problem yesterday(02.05.2016):

https://www.youtube.com/watch?v=GZLGdf8rZSs

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

Title:
  Blinking screen during the call if you remove the phone from your ear

Status in Canonical System Image:
  Fix Released
Status in android package in Ubuntu:
  Fix Released
Status in powerd package in Ubuntu:
  Invalid
Status in unity-system-compositor package in Ubuntu:
  Invalid

Bug description:
  I have a problem with my Meizu MX4 (Arale r6). 
  During a call if you remove the phone from your ear, sometimes (not always) 
the screen remains turned off. When you try to push the power button to wake up 
the screen, that starts blinking and it's not possible to hang up. The screen 
remains in that condition even after the end of the call.
  When it keeps blinking I try to hold the button down and in few seconds the 
screen turns black and the phone starts working again. Sometimes, instead, it 
starts working again by itself.

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

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

[Touch-packages] [Bug 1571513] Re: Please turn off vibrate on touch/typing by default. It makes the phone feel much more laggy

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: New => Confirmed

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

Title:
  Please turn off vibrate on touch/typing by default. It makes the phone
  feel much more laggy

Status in Canonical System Image:
  Opinion
Status in Ubuntu UX:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Incomplete

Bug description:
  Please turn off vibrate on touch/typing by default. It makes the phone
  feel much more laggy than it really is, which is bad for making a
  first impression on users.

  The reason I think is because the vibration mechanism runs for
  hundreds of milliseconds. Whereas visual and aural feedback is in the
  order of tens of milliseconds. So vibration feedback makes the phone
  feel much more laggy. Please turn it off by default.

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

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

[Touch-packages] [Bug 1202754] [NEW] update-manager crashed with SystemExit in exit(): 0

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Errors bucket
https://errors.ubuntu.com/bucket/?id=/usr/bin/update-manager:SystemExit:commit:_inline_callbacks:_show_transaction:_inline_callbacks:commit:_action_done:exit

I was going to check for updates, but the Update-Manager has closed
itself.

ProblemType: CrashDistroRelease: Ubuntu 13.10
Package: update-manager 1:0.189
ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
Uname: Linux 3.10.0-3-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.10.2-0ubuntu4
Architecture: i386
Date: Thu Jul 18 20:46:05 2013
ExecutablePath: /usr/bin/update-manager
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/update-manager --no-update 
--no-focus-on-map
PythonArgs: ['/usr/bin/update-manager', '--no-update', 
'--no-focus-on-map']SourcePackage: update-manager
Title: update-manager crashed with SystemExit in exit(): 0
UpgradeStatus: Upgraded to saucy on 2013-03-21 (118 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

** Affects: ubuntukylin
 Importance: Undecided
 Assignee: faiz (starone-faiz)
 Status: Fix Released

** Affects: update-manager
 Importance: Undecided
 Assignee: faiz (starone-faiz)
 Status: New

** Affects: click-update-manager (Ubuntu)
 Importance: High
 Assignee: faiz (starone-faiz)
 Status: Fix Released


** Tags: apport-crash i386 saucy trusty ubuntukylin
-- 
update-manager crashed with SystemExit in exit(): 0
https://bugs.launchpad.net/bugs/1202754
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to click-update-manager in Ubuntu.

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

[Touch-packages] [Bug 964705] Re: System policy prevents modification of network settings for all users

[Benoit Grégoire]

Still an issue in Kubuntu 16.04, so apparently it did NOT get merged
into Ubuntu.

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

Title:
  System policy prevents modification of network settings for all users

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

Bug description:
  This seems like a regression? The screen shot is at
  http://thesii.org/Screenshot.jpg The nearest link I can find is from
  the forum area at http://ubuntuforums.org/showthread.php?p=1146

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  Date: Sun Mar 25 19:36:45 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120323)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1534501] Re: [URGENT] dnsmasq errors fills up syslogs extremely fast

[Launchpad Bug Tracker]

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

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

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

Title:
  [URGENT] dnsmasq errors fills up syslogs extremely fast

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Incomplete
Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  snippet of logs.

  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.397836] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.407691] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.419365] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30455]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30455]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq 

[Touch-packages] [Bug 1434986] Re: Not working network connection after boot

[jango]

what did you re-installed?

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

Title:
  Not working network connection after boot

Status in NetworkManager:
  Expired
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Directly after boot the network connections are not working. I am
  connected and have an IP address, but I cannot establish a connection
  with any Internet server.

  I have the impression it is related to thee DNS lookup, which waits
  forever for a result.

  Cycling the connection (disconnect->reconnect) seems to fix the
  problem for some time.

  I am reporting this against network-manager, but I am not sure if it is 
directly in network manager or if it is systemd related.
  With 14.10 everything worked perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 12:38:26 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-30 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.26 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.29
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-16T00:14:50.662693
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Kabelnetzwerkverbindung 1  4a581685-6002-4401-a993-49aa649667eb  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  
4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1567540] Re: ntp crashes everytime the network goes up or down.

[ChristianEhrhardt]

>From the dumps

 এপ্রি 07 15:51:02 nowhere-6 ntpd[6197]: work_thread.c:271: 
INSIST(((void *)0) != req) failed
 এপ্রি 07 15:51:02 nowhere-6 ntpd[6197]: exiting (due to assertion 
failure)

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

Title:
  ntp crashes everytime the network goes up or down.

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  ntp crashes every time the network goes up or down while the system is 
running and also crashes after booting up without network.
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-03-12 (26 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  NtpStatus: ntpq: read: Connection refused
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu4
  PackageArchitecture: amd64
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-17-generic 
root=UUID=306314bc-efcb-4c2d-b0e9-e05ec92ed0f0 ro
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-03-12 (31 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  NtpStatus: ntpq: read: Connection refused
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5
  PackageArchitecture: amd64
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=306314bc-efcb-4c2d-b0e9-e05ec92ed0f0 ro
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-13 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160412)
  NtpStatus: ntpq: read: Connection refused
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5
  PackageArchitecture: amd64
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=13f57794-2e19-4a56-836a-94185bba5ec5 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-13 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160412)
  NtpStatus: ntpq: read: Connection refused
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5
  PackageArchitecture: amd64
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=13f57794-2e19-4a56-836a-94185bba5ec5 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-14 (3 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160412)
  NtpStatus: ntpq: read: Connection refused
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5
  PackageArchitecture: amd64
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-20-generic 
root=UUID=b9c0528f-e81f-4b08-9b31-032f14f72ccd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-20.36-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-14 (3 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160412)
  NtpStatus: ntpq: read: Connection refused
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5
  PackageArchitecture: amd64
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-20-generic 
root=UUID=b9c0528f-e81f-4b08-9b31-032f14f72ccd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-20.36-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-20-generic x86_64
  UpgradeStatus: No upgrade log present 

[Touch-packages] [Bug 1567540] Re: ntp crashes everytime the network goes up or down.

[ChristianEhrhardt]

The system also looks as it is in various problems - the kernel often
reports vblank issues and dumps traces, also it seems that network in
general or at least towards the configured NTP and DNS seems to be down.

Could you share a bit about the configuration related to that
(networking/ntp/dns) - as this might help to recreate the case.

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

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

Title:
  ntp crashes everytime the network goes up or down.

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  ntp crashes every time the network goes up or down while the system is 
running and also crashes after booting up without network.
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-03-12 (26 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  NtpStatus: ntpq: read: Connection refused
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu4
  PackageArchitecture: amd64
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-17-generic 
root=UUID=306314bc-efcb-4c2d-b0e9-e05ec92ed0f0 ro
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-03-12 (31 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  NtpStatus: ntpq: read: Connection refused
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5
  PackageArchitecture: amd64
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=306314bc-efcb-4c2d-b0e9-e05ec92ed0f0 ro
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-13 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160412)
  NtpStatus: ntpq: read: Connection refused
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5
  PackageArchitecture: amd64
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=13f57794-2e19-4a56-836a-94185bba5ec5 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-13 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160412)
  NtpStatus: ntpq: read: Connection refused
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5
  PackageArchitecture: amd64
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=13f57794-2e19-4a56-836a-94185bba5ec5 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-14 (3 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160412)
  NtpStatus: ntpq: read: Connection refused
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5
  PackageArchitecture: amd64
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-20-generic 
root=UUID=b9c0528f-e81f-4b08-9b31-032f14f72ccd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-20.36-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-14 (3 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160412)
  NtpStatus: ntpq: read: Connection refused
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5
  PackageArchitecture: amd64
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-20-generic 

[Touch-packages] [Bug 1546641] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()

[ice]

the bug must have something to do with a boot error.
when I got this bug after next reboot the system hangs for 2 min on post with 
error code 99  and 
this error dissapears only if I shut down the power completly.

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

Title:
  unity-settings-daemon crashed with SIGSEGV in
  up_exported_daemon_get_lid_is_closed()

Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in upower package in Ubuntu:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Triaged
Status in upower source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Yakkety:
  Triaged
Status in upower source package in Yakkety:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/8ca9c548fc4e2fc1d4bf827bbd85c72df59313f8

  Ubuntu 16.04 crashes immediately on login. Default settings not
  applied and appearance is a bit ugly (incorrect font hinting, in-
  window menus etc).

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Feb 17 13:52:13 2016
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2016-02-08 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x3aae60fe69 : 
mov(%rbx),%rdi
   PC (0x3aae60fe69) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   up_exported_daemon_get_lid_is_closed () from 
/usr/lib/x86_64-linux-gnu/libupower-glib.so.3
   gsd_power_manager_start () from 
/usr/lib/unity-settings-daemon-1.0/libpower.so
   ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
   gnome_settings_plugin_info_activate ()
   ?? ()
  Title: unity-settings-daemon crashed with SIGSEGV in 
up_exported_daemon_get_lid_is_closed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1546641/+subscriptions

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

[Touch-packages] [Bug 1534501] Re: [URGENT] dnsmasq errors fills up syslogs extremely fast

[Launchpad Bug Tracker]

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

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

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

Title:
  [URGENT] dnsmasq errors fills up syslogs extremely fast

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Incomplete
Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  snippet of logs.

  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.397836] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.407691] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.419365] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30455]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30455]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq 

[Touch-packages] [Bug 1534501] Re: [URGENT] dnsmasq errors fills up syslogs extremely fast

[Launchpad Bug Tracker]

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

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

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

Title:
  [URGENT] dnsmasq errors fills up syslogs extremely fast

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Incomplete
Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  snippet of logs.

  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.397836] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.407691] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.419365] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30455]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30455]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   

[Touch-packages] [Bug 1577844] Re: don't run ifup@.service before networking.service

[Martin Pitt]

** Bug watch added: Debian Bug tracker #752919
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752919

** Also affects: ifupdown (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752919
   Importance: Unknown
   Status: Unknown

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

Title:
  don't run ifup@.service before networking.service

Status in cloud-init package in Ubuntu:
  New
Status in ifupdown package in Ubuntu:
  In Progress
Status in ifupdown package in Debian:
  Unknown

Bug description:
  ifup@.service can (and often does) run for a particular interface
  before networking.service runs. This is brittle as during early boot
  ifup is prone to fail: / might still be read-only, /var might not yet
  exist or be writable, dhclient-enter-hooks.d/ or if-up.d/ hooks might
  silently fail, etc. It is also unnecessary as networking.service will
  bring up all "auto" and all present "allow-hotplug" interfaces anyway,
  and it runs at the right time.

  We should make either 80-ifupdown.rules or ifup@.service ignore events
  until networking.service is active, or wait until after it has run
  (slower, but avoids race conditions when hotplug events happen while
  networking.service is running). Thus we need to add
  After=networking.service to ifup@.service, so that this only does
  stuff after doing the "coldplug" configuration.

  This also affects cloud-init's setup of networking: this currently
  jumps through a lot of bad hoops to make sure that ifup@ does not run
  until after cloud-init-local.service. This includes blocking udev
  rules for an indefinite time, which is racy, a potential deadlock, and
  highly non-elegant.

  https://bugs.debian.org/752919 is related to this issue.

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

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

[Touch-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

[Jamie Strandboge]

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

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

Title:
  implement 'complain mode' in seccomp for developer mode with snaps

Status in Snappy:
  Confirmed
Status in libseccomp package in Ubuntu:
  Confirmed

Bug description:
  A requirement for snappy is that a snap may be placed in developer
  mode which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make
  developing on snappy easier.

  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while
  we can set complain mode to permit all calls, they are not logged at
  this time. I've discussed this with upstream and we are working
  together on the approach. This may require a kernel patch and an
  update to libseccomp, to filing this bug for now as a placeholder and
  we'll add other tasks as necessary.

  UPDATE: ubuntu-core-launcher now supports the '@complain' directive
  that is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).

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

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

[Touch-packages] [Bug 1577926] [NEW] apt-key works fine, yet apt fails with "Could not execute 'apt-key'"

[pjd]

Public bug reported:

Apt can fail to verify a Release file which verifies just fine when
calling apt-key directly.

Please advise how i can supply further debug information to help fix the
underlying bug.

Expected:
apt-get should only report that a repository is not signed when no such 
signature was found.
If a signature was in fact successfully acquired but not verified, apt-get 
should report failure to verify instead.
apt-get should have a meaningful error message when calling apt-key fails.

Bonus:
Calling apt-key should not fail when the same thing works fine on command line.
A reference to "Debug::Acquire::gpgv" should be in apt-secure(8) documentation.

Observed:

# uname -a
Linux hostname 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 
i686 i686 i686 GNU/Linux
# chroot reproducable
$ uname -a
Linux hostname 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 
armv7l armv7l armv7l GNU/Linux

$ lsb_release -a 2>/dev/null
Distributor ID: Ubuntu
Description:Ubuntu 16.04 LTS
Release:16.04
Codename:   xenial

$ apt-get -o "Debug::Acquire::gpgv=true" update
Get:1 http://ports.ubuntu.com xenial-security InRelease [92.2 kB]
0% [1 InRelease gpgv 92.2 kB]igners 
Preparing to exec:  /usr/bin/apt-key --quiet --readonly verify --status-fd 3 
/tmp/apt.sig.jYGUCG /tmp/apt.data.uTkX1c
gpgv exited with status 111
Summary:
  Good: 
  Bad: 
  Worthless: 
  SoonWorthless: 
  NoPubKey: 
Ign:1 http://ports.ubuntu.com xenial-security InRelease
Fetched 92.2 kB in 1s (79.5 kB/s)
Reading package lists... Done
W: GPG error: http://ports.ubuntu.com xenial-security InRelease: Could not 
execute 'apt-key' to verify signature (is gnupg installed?)
W: The repository 'http://ports.ubuntu.com xenial-security InRelease' is not 
signed.
N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration 
details.

$ /usr/bin/apt-key --quiet --readonly verify --status-fd /dev/stderr 
/tmp/apt.sig.jYGUCG /tmp/apt.data.uTkX1c
gpgv: Signature made Tue May  3 19:02:17 2016 UTC using DSA key ID 437D05B5
[GNUPG:] SIG_ID e53PXRjA/EMb7CuZJtAicvvUm60 2016-05-03 1462302137
[GNUPG:] GOODSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key 

gpgv: Good signature from "Ubuntu Archive Automatic Signing Key 
"
[GNUPG:] VALIDSIG 630239CC130E1A7FD81A27B140976EAF437D05B5 2016-05-03 
1462302137 0 4 0 17 10 01 630239CC130E1A7FD81A27B140976EAF437D05B5
gpgv: Signature made Tue May  3 19:02:17 2016 UTC using RSA key ID C0B21F32
[GNUPG:] SIG_ID kCsrLo9VUm7YcYhhqQUw2fbWoY4 2016-05-03 1462302137
[GNUPG:] GOODSIG 3B4FE6ACC0B21F32 Ubuntu Archive Automatic Signing Key (2012) 

gpgv: Good signature from "Ubuntu Archive Automatic Signing Key (2012) 
"
[GNUPG:] VALIDSIG 790BC7277767219C42C86F933B4FE6ACC0B21F32 2016-05-03 
1462302137 0 4 0 1 10 01 790BC7277767219C42C86F933B4FE6ACC0B21F32

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

Title:
  apt-key works fine, yet apt fails with "Could not execute 'apt-key'"

Status in apt package in Ubuntu:
  New

Bug description:
  Apt can fail to verify a Release file which verifies just fine when
  calling apt-key directly.

  Please advise how i can supply further debug information to help fix
  the underlying bug.

  Expected:
  apt-get should only report that a repository is not signed when no such 
signature was found.
  If a signature was in fact successfully acquired but not verified, apt-get 
should report failure to verify instead.
  apt-get should have a meaningful error message when calling apt-key fails.

  Bonus:
  Calling apt-key should not fail when the same thing works fine on command 
line.
  A reference to "Debug::Acquire::gpgv" should be in apt-secure(8) 
documentation.

  Observed:

  # uname -a
  Linux hostname 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 
i686 i686 i686 GNU/Linux
  # chroot reproducable
  $ uname -a
  Linux hostname 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 
armv7l armv7l armv7l GNU/Linux

  $ lsb_release -a 2>/dev/null
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  $ apt-get -o "Debug::Acquire::gpgv=true" update
  Get:1 http://ports.ubuntu.com xenial-security InRelease [92.2 kB]
  0% [1 InRelease gpgv 92.2 kB]igners 
  Preparing to exec:  /usr/bin/apt-key --quiet --readonly verify --status-fd 3 
/tmp/apt.sig.jYGUCG /tmp/apt.data.uTkX1c
  gpgv exited with status 111
  Summary:
Good: 
Bad: 
Worthless: 
SoonWorthless: 
NoPubKey: 
  Ign:1 http://ports.ubuntu.com xenial-security InRelease
  Fetched 92.2 kB in 1s (79.5 kB/s)
  Reading 

[Touch-packages] [Bug 1576380] Re: Picking a file via content hub breaks OSK input in browser

[Bob Harvey]

I will give it a try in the next day or so (been sick, getting behind at
work

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

Title:
  Picking a file via content hub breaks OSK input in browser

Status in content-hub package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  M10 tablet, OTA 10.1

  1. Create a bug in Launchpad
  2. Use the button to select a file attachment
  3. Navigate to picture gallery, select screengrab

  On return cannot any text in text fields with on-screen keyboard..
  Touch text field, keyboard pops up.. Field is not highlight orange,
  letters typed do not appear.. You /can/ move the insertion point and
  delete with the backspace key, but you can't enter new letters.

  Work-around.. Flip out to another scope e.g today, and enter text
  there e.g. Search box - keyboard works there.. Flipback to browser,
  text field you left already orange bordered, keyboard works.

  Seems to happen on other pages, but easy to reproduce on launchpad

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

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

Re: [Touch-packages] [Bug 1375215] Re: System runs out of memory - white screens frequently seen in web renderers

[costales]

Hi Olivier :)

> @Marcos: what do you mean by "uNav is generating a lot of
> process/second"?

uNav is doing a lot of calculations by second when you're driving.
Then the CPU usage is so high.


> IIRC I once suggested you to monitor the 'webProcessStatus' property of
> the webview, and offer some user feedback when it’s killed or crashed.


We have this log from users and experimented by myself:

file:///opt/click.ubuntu.com/navigator.costales/0.59/qml/Main.qml:103:
TypeError: Type error
ubuntumirclient: Attempted to deliver an event to a non-existent
window, ignoring.

This is because the webview was killed and uNav doesn't find it.

Regenerate the webview could be a solution, but it would lost a current
route.

A hug!

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

Title:
  System runs out of memory - white screens frequently seen in web
  renderers

Status in Canonical System Image:
  Fix Released
Status in oxide-qt package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  [See latest comments for recent repro notes]

  krillin 14.09 #2 + all updates applied

  After running the system for a while (few minutes) the system runs out of 
memory and start killing processes.
  It is very visible with the webbrowser or webapps because it renders the page 
and displays a white page when oxide-render is killed. Although it is not 
specific to oxide, and any app are killed (address-book, system-settings, ...) 
You can clearly notice that other apps are being killed because when you switch 
to the app it's all blurry and take a while to reload, also it loses its state 
(for example, you lose the message you were writing in the messaging-app)

  There is no specific steps to reproduce. I have several scopes enabled
  (photos, nearby, news) You don't have to have tons of apps open to
  reproduce this. Launching the webbrowser or a webapps and navigating
  on the phone between the scopes and the open app seems enough for the
  system to start killing processes.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: liboxideqtcore0 1.2.0-0ubuntu1 [origin: Ubuntu RTM]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Mon Sep 29 12:51:34 2014
  InstallationDate: Installed on 2014-09-24 (5 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140924-030204)
  SourcePackage: oxide-qt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Max Waterman]

I notice that one of my monitors is 'lost' (the BenQ one) if the laptop
is allowed to go to sleep and then awoken. The 'Screen Display' tool is
still 'non-functional'.

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

Title:
  Screen Display 'Apply' fails

Status in xorg package in Ubuntu:
  New

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

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

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  It is the 'Screen Display' utility on the 'System Settings' tool - I
  don't know how to find out what binary that is or the package it is
  in.

  3) What you expected to happen

  I expect to be able to configure multiple monitors - though it fails
  even when I have none connected.

  4) What happened instead

  I get the above error message any time I press 'Apply'.

  I've had this ever since upgrading to 16.04.

  In case this is useful :

  [~]$ lspci
  00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated 
Graphics (rev 09)
  00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
  00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI 
Controller (rev 03)
  00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI 
Controller #1 (rev 03)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3) 
I218-LM (rev 03)
  00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition 
Audio Controller (rev 03)
  00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#6 (rev e3)
  00:1c.1 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#3 (rev e3)
  00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI 
Controller (rev 03)
  00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
  00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller 
[AHCI Mode] (rev 03)
  00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
  00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP 
Thermal Management Controller (rev 03)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI 
Express Card Reader (rev 01)
  03:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
  [~]$ 

  It is a Lenovo X250 with a docking station (though it doesn't make any
  difference if the docking station is used or not).

  IMO, this isn't related to graphics specifically...more to do with
  some DBus service...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May  3 13:20:37 2016
  DistUpgraded: 2016-04-22 10:05:12,580 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2226]
  InstallationDate: Installed on 2015-05-20 (348 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CM001QUK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (11 days ago)
  dmi.bios.date: 04/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET33W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CM001QUK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 

[Touch-packages] [Bug 1577871] Re: Why does taking a screenshot leave grey rectangles on my screen?

[Ace Suares]

Aha! These go away as soon as the screenshot app is closed.


** Attachment added: "Screenshot with two open screenshot apps and two 
rectangles"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577871/+attachment/4654763/+files/Screenshot%20from%202016-05-03%2015-47-03.png

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

Title:
  Why does taking a screenshot leave grey rectangles on my screen?

Status in xorg package in Ubuntu:
  New

Bug description:
  Taking screenshots results in grey rectangles on the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  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: Tue May  3 13:12:40 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04ed]
  InstallationDate: Installed on 2016-04-16 (17 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. Inspiron 620s
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic 
root=UUID=9dd402f9-2db1-450c-b58b-a065f4bcb04f ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0GDG8Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 00
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd04/12/2011:svnDellInc.:pnInspiron620s:pvr00:rvnDellInc.:rn0GDG8Y:rvrA00:cvnDellInc.:ct3:cvr00:
  dmi.product.name: Inspiron 620s
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sat Apr 30 07:39:01 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech M570MOUSE, id 8
   inputBTC USB Multimedia Keyboard KEYBOARD, id 9
   inputBTC USB Multimedia Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Touch-packages] [Bug 1447839] Re: Unity8 mouse cursor never changes when moving over widgets in app windows

[Launchpad Bug Tracker]

** Branch linked: lp:~dandrader/qtmir/mirCursorNames

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

Title:
  Unity8 mouse cursor never changes when moving over widgets in app
  windows

Status in Mir:
  Fix Released
Status in QtMir:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Mouse cursor never changes when moving over widgets in app windows
  (e.g. 'I' cursor for a text editor).

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

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

[Touch-packages] [Bug 1517257] Re: apport-retrace should install and use gdb for target release

[Martin Pitt]

Some preparation to avoid installing gdb-dbg: 
http://bazaar.launchpad.net/~apport-hackers/apport/trunk/revision/3075
Fix: http://bazaar.launchpad.net/~apport-hackers/apport/trunk/revision/3076

** Changed in: apport
   Status: New => Fix Released

** Changed in: apport (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

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

Title:
  apport-retrace should install and use gdb for target release

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Committed

Bug description:
  apport-retrace will use the version of gdb installed on the system
  performing the retrace. This can cause issues retracing crash reports
  from releases that have a newer toolchain revision than the system
  performing the retrace. Subsequently, it would be better if apport-
  retrace were to install gdb into the sandbox being used for retracing
  and used that version of gdb for analyzing the core dump.

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

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

[Touch-packages] [Bug 1447839] Re: Unity8 mouse cursor never changes when moving over widgets in app windows

[Daniel d'Andrada]

** Changed in: unity8 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Unity8 mouse cursor never changes when moving over widgets in app
  windows

Status in Mir:
  Fix Released
Status in QtMir:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Mouse cursor never changes when moving over widgets in app windows
  (e.g. 'I' cursor for a text editor).

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

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

[Touch-packages] [Bug 1447839] Re: Unity8 mouse cursor never changes when moving over widgets in app windows

[Daniel d'Andrada]

** Changed in: unity-system-compositor (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Unity8 mouse cursor never changes when moving over widgets in app
  windows

Status in Mir:
  Fix Released
Status in QtMir:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Mouse cursor never changes when moving over widgets in app windows
  (e.g. 'I' cursor for a text editor).

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

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

[Touch-packages] [Bug 1517257] Re: apport-retrace should install and use gdb for target release

[Launchpad Bug Tracker]

** Branch linked: lp:apport

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

Title:
  apport-retrace should install and use gdb for target release

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Committed

Bug description:
  apport-retrace will use the version of gdb installed on the system
  performing the retrace. This can cause issues retracing crash reports
  from releases that have a newer toolchain revision than the system
  performing the retrace. Subsequently, it would be better if apport-
  retrace were to install gdb into the sandbox being used for retracing
  and used that version of gdb for analyzing the core dump.

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

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

[Touch-packages] [Bug 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

[Steve Arnold]

Okay, I decided to go ahead and create a couple of ppas and this seems a
bit better than attaching a bunch of bin pkgs:
https://launchpad.net/~nerdboy

The fix for this is in the despktop package ppa but it looks like only
x86/x86_64 packages are built (even though I did the deb pkg updates on
ARM) so you'll probably need to build from source package unless I can
find a way to make it build armhf.  Using apt-get source and dpkg-deb
--build on the ppa source should work...

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

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 :   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1577912] [NEW] package account-plugin-facebook (not installed) failed to install/upgrade: a tentar sobre-escrever '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', que tam

[Wagner Lucio de Oliveira]

Public bug reported:

also error in plasmashell when run kde, only appears black screen

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: account-plugin-facebook (not installed)
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic i686
ApportVersion: 2.20.1-0ubuntu2
Architecture: i386
Date: Tue May  3 14:19:10 2016
ErrorMessage: a tentar sobre-escrever 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', que também está no 
pacote kaccounts-providers 4:15.12.3-0ubuntu1
InstallationDate: Installed on 2016-05-03 (0 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: account-plugins
Title: package account-plugin-facebook (not installed) failed to 
install/upgrade: a tentar sobre-escrever 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', que também está no 
pacote kaccounts-providers 4:15.12.3-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: account-plugins (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package account-plugin-facebook (not installed) failed to
  install/upgrade: a tentar sobre-escrever '/etc/signon-ui/webkit-
  options.d/www.facebook.com.conf', que também está no pacote kaccounts-
  providers 4:15.12.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  also error in plasmashell when run kde, only appears black screen

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-facebook (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  Date: Tue May  3 14:19:10 2016
  ErrorMessage: a tentar sobre-escrever 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', que também está no 
pacote kaccounts-providers 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2016-05-03 (0 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: account-plugins
  Title: package account-plugin-facebook (not installed) failed to 
install/upgrade: a tentar sobre-escrever 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', que também está no 
pacote kaccounts-providers 4:15.12.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1576639] Re: memory threshold is too high

[Thomas Voß]

First of all: I agree with the original bug report, relying on % of
total system memory is likely to over- or under-estimate the actual
memory situation. A short-term solution would be to select a fixed
threshold in accordance with the OOM setup configured on our kernels,
thus avoiding the issues presented in #2. Mid-term, I would propose two
adjustments:

(1.) The system should let applications know if a low-on-memory situation is 
encountered, enabling the app to free up memory *before* the kernel OOM handler 
kicks in.
(2.) For the browser specifically: We should fine-tune how memory is freed 
up/tabs are torn down. "Least recently used" is an obvious choice, but we 
should also factor in if a tab is playing audio/video or actively accessing the 
camera/microphone and adjust likelihood of being killed accordingly.

(1.) and (2.) together should solve the issue in a way that handles
memory pressure situations as gracefully as possible.

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

Title:
  memory threshold is too high

Status in Canonical Device Images:
  New
Status in Canonical System Image:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  When opening new tabs in the browser, it decides if it should close
  existing ones based on level of free memory available in the system.
  My understanding is that this is currenly set to 30% percentage of
  memory in the device.

  There are two issues with this approach and setting:
  1) a percentage means that the threshold changes from device to device. While 
theamount of memory needed to open a webpage is not device specific. For 
example at 30%, the browser would close open tabs if there less than 1.2Gb mem 
free in a 4Gb device, but will only need 300Mb free on a 1Gb device. This is a 
very large difference.

  2) In M10 with 2Gb it requires 600mb free. From idle, just opening the
  gmail in the browser, takes the avilable system memory below this.
  This means that in 2gb devices the threshold is never met, and the
  browser never runs more than one tab at the same time.  this impacts
  user experience, specially in desktop mode. For example is not
  possible to open a document in the browser while attending a hangout.

  How to reproduce
  open a tab in the browser, go to youtube and play any video
  then open a new tab

  expected:
  music/sound in the video continues to play

  actual in m10:
  sound stops playing shortly after opening the tab

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-device-images/+bug/1576639/+subscriptions

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

[Touch-packages] [Bug 1577806] Re: webbrowser app and webcontainer open under the same instance

[Alexandre Abreu]

** Changed in: webbrowser-app (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  webbrowser app and webcontainer open under the same instance

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  I have on xenial the webbrowser-app as my main browser; if I use the
  webapp-container for anything else it opens as a tab in the main
  browser window. If I open a container instance first, opening the
  webbrowser app opens a new tab in the container instance.

  One webcontainer example to use is
  http://bazaar.launchpad.net/~ogra/+junk/slack-webapp/files

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May  3 11:47:05 2016
  InstallationDate: Installed on 2015-08-17 (259 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: webbrowser-app
  UpgradeStatus: Upgraded to xenial on 2015-11-06 (179 days ago)

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

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

[Touch-packages] [Bug 1557566] Re: [webapps] Cannot save image

[Alexandre Abreu]

** Branch linked: lp:~abreu-alexandre/webapps-core/content-exchange-
source

** Changed in: webapps-sprint
   Status: Confirmed => In Progress

** Changed in: webapps-core
   Status: Confirmed => In Progress

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [webapps] Cannot save image

Status in Canonical System Image:
  Confirmed
Status in The Webapps-core project:
  In Progress
Status in webapps-sprint:
  In Progress
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Test case.
  - Open Twitter app.
  - Long tap on an image (e.g. an avatar) to display the context menu.
  - Select option to save image.
  - Select Gallery app.

  Expected result.
  - Image is saved in the gallery app.

  Actual result.
  - Nothing happens.

  There are some apparmor denials in the dbus.log:
  http://paste.ubuntu.com/15391947/

  current build number: 280
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

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

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

[Touch-packages] [Bug 1447839] Re: Unity8 mouse cursor never changes when moving over widgets in app windows

[Daniel d'Andrada]

** Changed in: qtmir
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

** Changed in: qtmir
   Status: Confirmed => In Progress

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

Title:
  Unity8 mouse cursor never changes when moving over widgets in app
  windows

Status in Mir:
  Fix Released
Status in QtMir:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Mouse cursor never changes when moving over widgets in app windows
  (e.g. 'I' cursor for a text editor).

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

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

[Touch-packages] [Bug 1448566] Re: Ubuntu 15.04 - Macbook Pro Early 2015 (12, 1) Bluetooth disabled

[Jean-Frédéric]

Posting this in case it would help someone else: I had the same issue
with 15.10 (with kernel 4.2). I upgraded today to 16.04 (with kernel
4.4.0) and the buletooth is working like a charm.

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

Title:
  Ubuntu 15.04 - Macbook Pro Early 2015 (12,1) Bluetooth disabled

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of 15.04 on a Macbook Pro 12,1.

  I get no Bluetooth icon in the status bar, and in System Settings >
  Bluetooth, everything is greyed out (i.e., can't turn it on).

  
  $lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; rfkill list all; 
lsmod | grep bluetooth; hciconfig -a; uname -a

  Bus 002 Device 002: ID 05ac:8406 Apple, Inc.
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 05ac:0273 Apple, Inc.
  Bus 001 Device 004: ID 05ac:8290 Apple, Inc.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [ 32.369395] usb 1-3: Product: Bluetooth USB Host Controller
  [ 32.435743] input: Broadcom Corp. Bluetooth USB Host Controller as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:05AC:8290.0006/input/input7
  [ 32.490662] hid-generic 0003:05AC:8290.0006: input,hidraw5: USB HID v1.11 
Keyboard [Broadcom Corp. Bluetooth USB Host Controller] on 
usb-:00:14.0-3/input0
  [ 32.490750] input: Broadcom Corp. Bluetooth USB Host Controller as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.1/0003:05AC:8290.0007/input/input8
  [ 32.490995] hid-generic 0003:05AC:8290.0007: input,hidraw6: USB HID v1.11 
Mouse [Broadcom Corp. Bluetooth USB Host Controller] on 
usb-:00:14.0-3/input1
  [ 34.866186] Bluetooth: Core ver 2.20
  [ 34.866205] Bluetooth: HCI device and connection manager initialized
  [ 34.866751] Bluetooth: HCI socket layer initialized
  [ 34.866754] Bluetooth: L2CAP socket layer initialized
  [ 34.866759] Bluetooth: SCO socket layer initialized
  [ 0.158493] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
  [ 0.168342] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain  [bus 
00-9b] only partially covers this bridge
  [ 35.003383] brcmfmac :03:00.0: Direct firmware load for 
brcm/brcmfmac43602-pcie.txt failed with error -2
  [ 35.290656] brcmf_c_preinit_dcmds: Firmware version = wl0: Mar 13 2015 
08:11:08 version 7.35.177.36 (r540934) FWID 01-e4dc15b
  0: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no
  bluetooth 491520 1 btusb
  Linux hxn-laptop-linux 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

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

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

[Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones

[ian_hawdon]

Can also confirm the issue is still present on the latest build of
Ubuntu 16.10 with pulseaudio upgraded to version 1:8.0-2ubuntu1

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
Installed: 1:8.0-0ubuntu3
Candidate: 1:8.0-0ubuntu3
Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29 
  Device 44:5E:F3:B4:07:29
Name: BlueBuds X
Alias: BlueBuds X
Class: 0x240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

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

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

[Touch-packages] [Bug 1532899] Re: Group chat sometimes misses messages with Unknown Number Message not found

[James Dearing]

I'm experiencing this bug too. My phone is a BQ Aquaris E5 HD Ubuntu
Edition. My phone service is Consumer Cellular, which I think uses the
AT network. I'd gladly post any log files if I knew how to access
them.

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

Title:
  Group chat sometimes misses messages with Unknown Number Message not
  found

Status in Canonical System Image:
  Confirmed
Status in messaging-app package in Ubuntu:
  Invalid
Status in nuntium package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  Confirmed

Bug description:
  This happened the last two times I received group chat messages.
  Several messages were not listed in the chat but rather under an
  Unknown Number contact with content Message no found.

  I see 4 such entries for the time covered in the log files.

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

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

[Touch-packages] [Bug 1557566] Re: [webapps] Cannot save image

[Alexandre Abreu]

** Also affects: webapps-core
   Importance: Undecided
   Status: New

** Changed in: webapps-core
   Status: New => Confirmed

** Changed in: webapps-core
   Importance: Undecided => High

** Changed in: webapps-core
 Assignee: (unassigned) => Alexandre Abreu (abreu-alexandre)

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

Title:
  [webapps] Cannot save image

Status in Canonical System Image:
  Confirmed
Status in The Webapps-core project:
  Confirmed
Status in webapps-sprint:
  Confirmed
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Test case.
  - Open Twitter app.
  - Long tap on an image (e.g. an avatar) to display the context menu.
  - Select option to save image.
  - Select Gallery app.

  Expected result.
  - Image is saved in the gallery app.

  Actual result.
  - Nothing happens.

  There are some apparmor denials in the dbus.log:
  http://paste.ubuntu.com/15391947/

  current build number: 280
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

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

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

[Touch-packages] [Bug 1546641] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()

[jontyl]

I'm seeing this on a Sony Vaio VPCSB.

I'm also getting a problem with System Settings which may be related.
Clicking on Power, the System Settings window freezes and then
disappears. If I run unity-control-center from a terminal it prints the
following as it dies:

libupower-glib-WARNING **: Couldn't connect to proxy: Error calling
StartServiceByName for org.freedesktop.UPower:
GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate
service 'org.freedesktop.UPower': timed out

(unity-control-center:8939): GLib-GIO-CRITICAL **: 
g_dbus_proxy_call_sync_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed
Segmentation fault (core dumped)

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

Title:
  unity-settings-daemon crashed with SIGSEGV in
  up_exported_daemon_get_lid_is_closed()

Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in upower package in Ubuntu:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Triaged
Status in upower source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Yakkety:
  Triaged
Status in upower source package in Yakkety:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/8ca9c548fc4e2fc1d4bf827bbd85c72df59313f8

  Ubuntu 16.04 crashes immediately on login. Default settings not
  applied and appearance is a bit ugly (incorrect font hinting, in-
  window menus etc).

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Feb 17 13:52:13 2016
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2016-02-08 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x3aae60fe69 : 
mov(%rbx),%rdi
   PC (0x3aae60fe69) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   up_exported_daemon_get_lid_is_closed () from 
/usr/lib/x86_64-linux-gnu/libupower-glib.so.3
   gsd_power_manager_start () from 
/usr/lib/unity-settings-daemon-1.0/libpower.so
   ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
   gnome_settings_plugin_info_activate ()
   ?? ()
  Title: unity-settings-daemon crashed with SIGSEGV in 
up_exported_daemon_get_lid_is_closed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1546641/+subscriptions

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

[Touch-packages] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity

[Christophe]

New information : typing "xset -display :0.0 dpms force off" in the
terminal makes my screen to turn off. Then I can wake it up just by
moving the mouse. So the problem seems related to the "screen saver" of
ubuntu rather than Xorg.

** Package changed: xorg (Ubuntu) => gnome-screensaver (Ubuntu)

** Description changed:

  I did a fresh install off ubuntu 16.04 on my old dell computer in which
  there is an ati radeon X1300 graphics card.
  
-  Whenever the screen goes off due to inactivity, it cannot be woken up
+  Whenever the screen goes off due to inactivity, it cannot be woken up
  by moving the mouse or hit a key.
  
  The same ubuntu 16.04 installed on a laptop with intel graphics card
- doesn't show this problem, so I guess it is related to the radeon
- driver.
+ doesn't show this problem, so I first guessed it was related to the
+ radeon driver. But as there is no problem waking the screen when I type
+ "xset -display :0.0 dpms force off" in a terminal, I think the problem
+ is rather related to  gnome-screensaver.

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

Title:
  screen cannot be turned back on after being switched off after some
  time of inactivity

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  I did a fresh install off ubuntu 16.04 on my old dell computer in
  which there is an ati radeon X1300 graphics card.

   Whenever the screen goes off due to inactivity, it cannot be woken up
  by moving the mouse or hit a key.

  The same ubuntu 16.04 installed on a laptop with intel graphics card
  doesn't show this problem, so I first guessed it was related to the
  radeon driver. But as there is no problem waking the screen when I
  type "xset -display :0.0 dpms force off" in a terminal, I think the
  problem is rather related to  gnome-screensaver.

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

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

[Touch-packages] [Bug 1447839] Re: Unity8 mouse cursor never changes when moving over widgets in app windows

[Daniel d'Andrada]

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

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

Title:
  Unity8 mouse cursor never changes when moving over widgets in app
  windows

Status in Mir:
  Fix Released
Status in QtMir:
  Confirmed
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Mouse cursor never changes when moving over widgets in app windows
  (e.g. 'I' cursor for a text editor).

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

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

[Touch-packages] [Bug 1576364] Re: NetworkManager service stops starting on boot after upgrade to Xenial

[Jeff Lane]

Gonna set this to invalid.  After the third or fourth reboot, NM started
loading on it's own and I no longer needed to manually do so.  I don't
know why, but I'm unable to recreate the original fail state now :(

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

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 762349] Re: Difficult to distinguish which tab is selected

[Will Cooke]

If you want to provide some feedback on the attached branch that would
help.

You can download the relevant CSS for your config (Ambiance for the
default theme, Radiance for the alternative lighter theme) from here:

http://bazaar.launchpad.net/~willcooke/ubuntu-themes/terminal-
tabs/view/head:/Ambiance/gtk-3.0/apps/gnome-terminal.css

or

http://bazaar.launchpad.net/~willcooke/ubuntu-themes/terminal-
tabs/view/head:/Radiance/gtk-3.0/apps/gnome-terminal.css

Then I'd suggest renaming your current
/usr/share/themes/Ambiance/gtk-3.0/apps/gnome-terminal.css to something
like /usr/share/themes/Ambiance/gtk-3.0/apps/gnome-terminal.css.ori and
then copy the file you downloaded above in to that location.

If you dont like it, delete the new file and rename the original back
again.

It's not especially pretty, but it does the job for me.

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

Title:
  Difficult to distinguish which tab is selected

Status in Ayatana Design:
  New
Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress
Status in ubuntu-themes source package in Xenial:
  In Progress

Bug description:
  Binary package hint: unity

  In tabbed interfaces such as in gnome-terminal under unity it is
  difficult to visually distinguish the selected tab from the unselected
  ones.

  In the attached screenshot, gnome-terminal has three tabs open, and
  the third one is selected.  If you look close you can see the text is
  slightly whiter than the other tabs, and the border is a little more
  prominent but to my old man eyes it's really hard to see it at a
  glance.

  Under metacity, the difference is more notable (or at least, the theme
  is different).

  My guess is this is a theme issue rather than unity, but I'm unsure.
  If it is just a theme issue please refile to the right project.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: unity 3.8.8-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell]
  Date: Fri Apr 15 17:41:12 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=C
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to natty on 2011-04-04 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/762349/+subscriptions

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

[Touch-packages] [Bug 1577885] [NEW] 120sec delay during shutdown or reboot with still mounted cifs (via Wifi)

[Matthias Laumer]

Public bug reported:

Using Ubuntu 16.04 Desktop with Unity, used the same approach in 14.04
with no issue.

I prepare for mounting with the following entry in /etc/fstab my
Synology NAS :

//192.168.178.61/data /media/server/server_data cifs
users,uid=1000,gid=1000,username=x,passwd=xx,iocharset=utf8,sec=ntlm,noauto,_netdev
0

After login to unity, I mount it with a bash-script (mount -a) which is
called from ~/.config/autostart/myMounts.desktop

Doing this, and shuting down or rebooting lead into a very delayed
shutdown (round about 2 minutes) Pressing ESC Key, showed that the
process stops at the command "umount /media/server ..."

I have not tested if this also occurs when I am connected via ethernet.
I think it is because the (Wifi)Network is already disabled prior all
umounts are done.

This issue happens even if I type in a shutdown command into a Terminal
or if I choose shutdown form the menue, also if I use the power-button.

Failure can be avoided if I umount the network-drives manually previouse
to reboot.

Interim solution was, to create an alias for "shutdown" like "sh
/path/to/umount/script.sh && shutdown" in /etc/bash.bashrc.local.

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


** Tags: cifs delay nfs shutdown umount

** Description changed:

  I prepare for mounting with the following entry in /etc/fstab my
  Synology NAS :
  
  //192.168.178.61/data /media/server/server_data cifs
  
users,uid=1000,gid=1000,username=x,passwd=xx,iocharset=utf8,sec=ntlm,noauto,_netdev
  0
  
- After login to unity, I mount it with a bash-script (mount -a)
+ After login to unity, I mount it with a bash-script (mount -a) which is
+ called from ~/.config/autostart/myMounts.desktop
  
  Doing this, and shuting down or rebooting lead into a very delayed
  shutdown (round about 2 minutes) Pressing ESC Key, showed that the
  process stops at the comman "umount /media/server ..."
  
  I have not tested if this also appears when I am connected via ethernet.
  I think it is because the Network is already disabled prior all umounts
  are done.
  
  This issue happens even if I type in a shutdown command into a Terminal
  or if I choose shutdown form the menue, also if I use the power-button.
  
- Failure can be avaided if I umount the network-drives manually previouse
+ Failure can be avoided if I umount the network-drives manually previouse
  to reboot.
  
  Interim solution was, to create an alias for "shutdown" like "sh
  /path/to/umount/script.sh && shutdown" in /etc/bash.bashrc.local.

** Description changed:

- I prepare for mounting with the following entry in /etc/fstab my
- Synology NAS :
+ Using Ubuntu 16.04 Desktop with Unity, used the same approach in 14.04
+ with no issue.
+ 
+ 
+ I prepare for mounting with the following entry in /etc/fstab my Synology NAS 
:
  
  //192.168.178.61/data /media/server/server_data cifs
  
users,uid=1000,gid=1000,username=x,passwd=xx,iocharset=utf8,sec=ntlm,noauto,_netdev
  0
  
  After login to unity, I mount it with a bash-script (mount -a) which is
  called from ~/.config/autostart/myMounts.desktop
  
  Doing this, and shuting down or rebooting lead into a very delayed
  shutdown (round about 2 minutes) Pressing ESC Key, showed that the
  process stops at the comman "umount /media/server ..."
  
  I have not tested if this also appears when I am connected via ethernet.
  I think it is because the Network is already disabled prior all umounts
  are done.
  
  This issue happens even if I type in a shutdown command into a Terminal
  or if I choose shutdown form the menue, also if I use the power-button.
  
  Failure can be avoided if I umount the network-drives manually previouse
  to reboot.
  
  Interim solution was, to create an alias for "shutdown" like "sh
  /path/to/umount/script.sh && shutdown" in /etc/bash.bashrc.local.

** Description changed:

  Using Ubuntu 16.04 Desktop with Unity, used the same approach in 14.04
  with no issue.
  
- 
- I prepare for mounting with the following entry in /etc/fstab my Synology NAS 
:
+ I prepare for mounting with the following entry in /etc/fstab my
+ Synology NAS :
  
  //192.168.178.61/data /media/server/server_data cifs
  
users,uid=1000,gid=1000,username=x,passwd=xx,iocharset=utf8,sec=ntlm,noauto,_netdev
  0
  
  After login to unity, I mount it with a bash-script (mount -a) which is
  called from ~/.config/autostart/myMounts.desktop
  
  Doing this, and shuting down or rebooting lead into a very delayed
  shutdown (round about 2 minutes) Pressing ESC Key, showed that the
- process stops at the comman "umount /media/server ..."
+ process stops at the command "umount /media/server ..."
  
- I have not tested if this also appears when I am connected via ethernet.
- I think it is because the Network is already disabled prior all umounts
- are done.
+ I have not tested if this also occurs when I am connected via ethernet.
+ I think it is because the (Wifi)Network is 

[Touch-packages] [Bug 1538703] Re: Playlist next/prev controls only available when player is in foreground

[Jim Hodapp]

** Branch unlinked: lp:~phablet-team/media-hub/fix-1538703

** Branch linked: lp:~phablet-team/media-hub/fix-1538703-take2

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

Title:
  Playlist next/prev controls only available when player is in
  foreground

Status in Canonical System Image:
  In Progress
Status in indicator-sound package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu:
  Fix Committed
Status in qtubuntu-media package in Ubuntu:
  Fix Committed
Status in unity-scopes-shell package in Ubuntu:
  Invalid

Bug description:
  Switch to the dash (i.e. app scope) while music app is playing
  The indicator switches to mediaplayer with controls disabled

  Note also that the media player is shown with controls disabled on a
  fresh boot when no media has ever been played, the indicator should
  only show controls after playback.

  Something in the scopes is incorrectly telling media hub there is a
  new ctive player.

  Install the music app from the store
  Start a playlist in music app
  Switch apps
  Next and Prev are disabled in the indicator

  This was fixed after a reboot.

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

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

[Touch-packages] [Bug 1561195] Re: unattended-upgrades not work in Ubuntu 16.04

[fabianbur]

Está funcionando como se espera desde haca algunos días, supongo que por
las últimas actualizaciones en la versión estable de Ubuntu 16.04

is working as expected for some days, I guess for the latest updates to
the stable release of Ubuntu 16.04

** Changed in: unattended-upgrades (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  unattended-upgrades not work in Ubuntu 16.04

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  This guide've used successfully in Ubuntu 14.04 but something is not
  working in Ubuntu 16.04:

  https://help.ubuntu.com/lts/serverguide/automatic-updates.html

  I detected packages that need to be updated and the log of the
  application appears:

  No packages found that can be upgraded unattended and no pending auto-
  removals

  It never updated one by unattended-upgrades package for weeks that I
  have daily updated manually development version.

  It is necessary that application to run on other machines I need to
  upgrade within a month with the stable version. Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 23 15:46:21 2016
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=es_EC:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-01-26T23:01:12.880608

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

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