[Touch-packages] [Bug 1397415] Re: App icons remain in Dash after uninstallation, or total inability to run app from Dash.

[shivaraj naidu]

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

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

Title:
  App icons remain in Dash after uninstallation, or total inability to
  run app from Dash.

Status in Unity:
  New
Status in unity package in Ubuntu:
  Invalid

Bug description:
  I have two icons which remain after unistalling the application. This
  also happened on my previous 32bit Utopic with Skype creating two
  icons: one which worked, and one which was like the screenshot
  attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-26-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Nov 28 19:20:53 2014
  InstallationDate: Installed on 2014-11-14 (14 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1495688] Re: system-image-cli tool fails on dangling symlink

[Launchpad Bug Tracker]

This bug was fixed in the package system-image - 3.0.2-0ubuntu1

---
system-image (3.0.2-0ubuntu1) wily; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.

system-image (3.0.2-0ubuntu1) wily; urgency=medium

  * New upstream release.
- LP: #1495688 - Don't crash when one of the .ini files is a dangling
  symlink.
- d/rules: override_dh_auto_clean because otherwise, pybuild will
  remove the .egg-info files and that causes the Jenkins job in the CI
  train to fail.

 -- Barry Warsaw   Mon, 28 Sep 2015 21:37:45
+

** Changed in: system-image (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  system-image-cli tool fails on dangling symlink

Status in Snappy:
  Fix Released
Status in Ubuntu system image:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Committed
Status in system-image package in Ubuntu:
  Fix Released

Bug description:
  
  (amd64)ubuntu@localhost:~$ system-image-cli -i
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/systemimage/helpers.py", line 253, in 
last_update_date
  timestamp = datetime.fromtimestamp(os.stat(LAST_UPDATE_FILE).st_mtime)
  FileNotFoundError: [Errno 2] No such file or directory: 
'/userdata/.last_update'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/bin/system-image-cli", line 9, in 
  load_entry_point('system-image==3.0.1', 'console_scripts', 
'system-image-cli')()
File "/usr/lib/python3/dist-packages/systemimage/main.py", line 289, in main
  last_update=last_update_date(),
File "/usr/lib/python3/dist-packages/systemimage/helpers.py", line 258, in 
last_update_date
  for path in config.ini_files)
File "/usr/lib/python3/dist-packages/systemimage/helpers.py", line 258, in 

  for path in config.ini_files)
File "/usr/lib/python3.4/pathlib.py", line 1048, in stat
  return self._accessor.stat(self)
File "/usr/lib/python3.4/pathlib.py", line 326, in wrapped
  return strfunc(str(pathobj), *args)
  FileNotFoundError: [Errno 2] No such file or directory: 
'/etc/system-image/config.d/00_default.ini'

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

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

[Touch-packages] [Bug 1501310] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 1.0.7-0ubuntu0.6

---
lxc (1.0.7-0ubuntu0.6) trusty-security; urgency=medium

  * Fix breakage of some configurations where // ends up in the mount
target.  (LP: #1501310) (LP: #1476662)

 -- Serge Hallyn   Wed, 30 Sep 2015 10:38:14
-0500

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

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

Title:
  Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  I got this entry in the config file to mount a folder on the hosts
  filesystem:

  lxc.mount.entry=/media/array/backup/blixten
  /var/lib/lxc/blixten/rootfs/var/backup none bind 0 0

  this is the lxc root: lxc.rootfs = /var/lib/lxc/blixten/rootfs

  Nither /media/array/backup/blixten or
  /var/lib/lxc/blixten/rootfs/var/backup is a symlink.

  Error when starting the container:

  root@mail:/media# lxc-start -n blixten
  lxc-start: utils.c: ensure_not_symlink: 1384 Mount onto 
/usr/lib/x86_64-linux-gnu/lxc//var/backup resulted in 
/usr/lib/x86_64-linux-gnu/lxc/var/backup

  lxc-start: utils.c: safe_mount: 1409 Mount of '/media/array/backup/blixten' 
onto '/usr/lib/x86_64-linux-gnu/lxc//var/backup' was onto a symlink!
  lxc-start: conf.c: mount_entry: 2051 Invalid argument - failed to mount 
'/media/array/backup/blixten' on '/usr/lib/x86_64-linux-gnu/lxc//var/backup'
  lxc-start: conf.c: lxc_setup: 4165 failed to setup the mount entries for 
'blixten'
  lxc-start: start.c: do_start: 688 failed to setup the container
  lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2
  lxc-start: start.c: __lxc_start: 1080 failed to spawn 'blixten'
  lxc-start: lxc_start.c: main: 342 The container failed to start.
  lxc-start: lxc_start.c: main: 346 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  
  I had to revert to the older version of LXC to get the containers running 
again.

  Best regards
  Tobias

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

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

[Touch-packages] [Bug 1448939] Re: tint2 taskbar boots irregularly with xserver-xorg-video-ati, boots fine with proprietary driver

[o9000]

Regarding 3, I tried to fix this problem in the latest version (I'm the
current dev of tint2). However there is no package available for 14.04,
nor a PPA, so if you would like to try it out the only way is to compile
from source.

Normally I don't recommend this unless you know what you are doing, as
it is sometimes difficult to remove from the system software installed
from source and there are other things that can go wrong. In the case of
tint2 it should not be so complicated.

If you want to do it,  here is a page with instructions:
https://gitlab.com/o9000/tint2/wikis/Install#install-from-source

You will have to configure tint2 in your startup applications to run
from the new path (/usr/local/bin/tint2) and remove the sleep then
relog. If it has problems please let me know.

If you don't want to try this it's perfectly fine. I am just curious if
this solves the problem in your case, which is a bit strange -- normally
tint2 should just draw itself without transparency if the compositor is
not detected correctly at startup; it should not dissapear completely.

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

Title:
  tint2 taskbar boots irregularly with xserver-xorg-video-ati, boots
  fine with proprietary driver

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I run a little taskbar app called tint2. I boot it at startup, but
  about 50% of the time it isn't visible after booting. The other 50% it
  is. So I can reboot or logout/login until it sticks. At first I
  thought it was a bug in tint2, but now I have found that I don't get
  this issues when I run the AMD proprietary driver (fglrx). So I think
  it might be a problem in the xserver-xorg-video-ati driver. I have a
  Radeon HD 8600M series in a Lenovo S540.

  Additional note: when it does not display and I power off the
  computer, it is displayed for a brief moment before the computer shuts
  down. That makes me think that it is actually a display problem, not a
  problem of tint2 not booting at all.

  If this is unlikely to be caused by the xserver-xorg-video-ati driver,
  I apologize for reporting it here. If you need additional information,
  please let me know, I will be happy to provide.

  Required info:
  1) Ubuntu 14.04.2 LTS
  2) xserver-xorg-video-ati Installed: 1:7.3.0-1ubuntu3.1
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.3.30, 3.13.0-61-generic, x86_64: installed
   vboxhost, 4.3.30, 3.13.0-62-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:2216]
  InstallationDate: Installed on 2015-02-10 (230 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 20B30064MH
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-62-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Tags:  trusty ubuntu compiz-0.9
  Uname: Linux 3.13.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GPET54WW (1.54 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20B30064MH
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 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:bvrGPET54WW(1.54):bd02/19/2014:svnLENOVO:pn20B30064MH:pvrThinkPadS5-S540:rvnLENOVO:rn20B30064MH:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20B30064MH
  dmi.product.version: ThinkPad S5-S540
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4

[Touch-packages] [Bug 1500444] Re: QLockFile won't notice if the lock pid is re-used by an unrelated process

[Michael Terry]

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

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

Title:
  QLockFile won't notice if the lock pid is re-used by an unrelated
  process

Status in Canonical System Image:
  Fix Committed
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  My desktop webbrowser-app instance no longer seems to be remembering
  the previous session tabs and opening them at startup.

  I don't see any output on the console.  Any tips for helping debug
  this?

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

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

[Touch-packages] [Bug 1428023] Re: indicator-sound-service crashed with signal 5 in main()

[Charles Kerr]

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

** This bug has been marked a duplicate of bug 1427708
   indicator-sound-service crashed with g_error("Unable to get session bus")

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

Title:
  indicator-sound-service crashed with signal 5 in main()

Status in indicator-sound package in Ubuntu:
  Confirmed

Bug description:
  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar  3 08:00:28 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  InstallationDate: Installed on 2013-12-22 (436 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: indicator-sound
  StacktraceTop: main ()
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  Title: indicator-sound-service crashed with signal 5 in main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1429709] Re: indicator-sound-service crashed with signal 5 in main()

[Charles Kerr]

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

** This bug has been marked a duplicate of bug 1427708
   indicator-sound-service crashed with g_error("Unable to get session bus")

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

Title:
  indicator-sound-service crashed with signal 5 in main()

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  This immediatly crash comes after a normal start-up.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Mar  9 05:18:07 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  InstallationDate: Installed on 2015-03-09 (0 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150308)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=de_AT:de
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: indicator-sound
  StacktraceTop: main ()
  Title: indicator-sound-service crashed with signal 5 in main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1501458] [NEW] issues with intel graphics card

[RobG]

Public bug reported:

Tried a few drivers for the graphics - I cant seem to get it to work.
Causing very low fps & good specs on computer.   i'm lost

Intel® Core™ i7-4700MQ CPU @ 2.40GHz × 8
Intel® Haswell Mobile = graphics? 
15.6 GiB
ubuntu 14.04
64 bit

When I run lspci | grep VGA:
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-50.66~14.04.1-generic 3.16.7-ckt16
Uname: Linux 3.16.0-50-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Sep 30 14:38:55 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:1965]
InstallationDate: Installed on 2015-06-16 (106 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-50-generic.efi.signed 
root=UUID=de939647-8d10-41e7-8b39-3526b86290d6 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
XorgConf: Section "Device" Identifier "Card0" Driver "intel" Option 
"AccelMethod" "sna" EndSection
dmi.bios.date: 05/05/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.62
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 1965
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 93.51
dmi.chassis.asset.tag: 5CG4513JHP
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.62:bd05/05/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097E11405E162:rvnHewlett-Packard:rn1965:rvrKBCVersion93.51:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP ENVY 17 Notebook PC
dmi.product.version: 097E11405E162
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.65+git1509290630.4031dc~gd~t
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 Sep 29 15:48:25 2015
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 882 
 vendor LGD
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

Title:
  issues with intel graphics card

Status in xorg package in Ubuntu:
  New

Bug description:
  Tried a few drivers for the graphics - I cant seem to get it to work.
  Causing very low fps & good specs on computer.   i'm lost

  Intel® Core™ i7-4700MQ CPU @ 2.40GHz × 8
  Intel® Haswell Mobile = graphics? 
  15.6 GiB
  ubuntu 14.04
  64 bit

  When I run lspci | grep VGA:
  00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-50.66~14.04.1-generic 3.16.7-ckt16
  Uname: Linux 3.16.0-50-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Sep 30 14:38:55 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: 

[Touch-packages] [Bug 1476662] Re: lxc-start symlink vulnerabilities may allow guest to read host filesystem, interfere with apparmor

[Tyler Hicks]

The regression should be fixed with lxc 1.0.7-0ubuntu0.6. See
http://www.ubuntu.com/usn/usn-2753-2/ for more details.

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

Title:
  lxc-start symlink vulnerabilities may allow guest to read host
  filesystem, interfere with apparmor

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  lxc-start shuffles around mounts using helper directory
  /usr/lib/x86_64-linux-gnu/lxc (guest root fs is mounted here)

  It then modifies mounts operating in guest root directory before
  invoking init. As it does not check if all mount points are
  directories, a malicious guest may modify its internal structure
  before shutdown (or was created using manipulated image) and then when
  started again, guest may

  * Access  the whole host root filesystem

  * Block switching from lxc-start apparmor profile to lxc-container-
  default

  
  # Real putold before pivot-root (root fs will end here)
  mkdir -p /x/lxc_putold

  # Faked putold
  ln -s /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold lxc_putold
  mkdir -p /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold/proc
  touch /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold/proc/mounts

  
  # proc fake
  mkdir -p /x/proc
  umount /proc
  rmdir /proc
  ln -s /usr/lib/x86_64-linux-gnu/lxc/x/proc proc

  mkdir -p /usr/lib/x86_64-linux-gnu/lxc/x/proc/1/attr 
/usr/lib/x86_64-linux-gnu/lxc/x/proc/self
  touch /usr/lib/x86_64-linux-gnu/lxc/x/proc/1/attr/current
  touch /usr/lib/x86_64-linux-gnu/lxc/x/proc/self/status


  The  issue was also found during
  https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.html

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

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

[Touch-packages] [Bug 1441368] Re: After Standby login without password is no more possible

[shivaraj naidu]

** Tags removed: dataloss login
** Tags added: 14.04 3.19 in invalid kernel with

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

Title:
  After Standby login without password is no more possible

Status in Unity:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  I have 2 users installed:

  A | Systemmanager | Login with password
  B | Standard | Login without password

  sudo passwd -Sa :
  a P 08/25/2014 0 9 7 -1
  b NP 08/25/2014 0 9 7 -1

  If running under user B after some time the system automatically suspends to 
Standby, and is waked up later, at the normal login screen the login without 
password is no more possible, I get in red letters: wrong password.
  Only change to another user and then logoff helps to again get to a normal 
working login screen.

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

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

[Touch-packages] [Bug 1501456] [NEW] pytz.country_names UnicodeDecodeError exception

[Robert C Jennings]

Public bug reported:

Wily:
# python3 -c 'from pytz import country_names
for item in country_names.items():
  print(item)'
Traceback (most recent call last):
  File "", line 2, in 
  File "/usr/lib/python3.4/_collections_abc.py", line 497, in __iter__
for key in self._mapping:
  File "/usr/lib/python3/dist-packages/pytz/lazy.py", line 41, in __iter__
self._fill()
  File "/usr/lib/python3/dist-packages/pytz/__init__.py", line 350, in _fill
line = line.decode('US-ASCII')
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 3: ordinal 
not in range(128)

# python -c 'from pytz import country_names
print(country_names)'
Traceback (most recent call last):
  File "", line 2, in 
  File "/usr/lib/python2.7/UserDict.py", line 172, in __repr__
return repr(dict(self.iteritems()))
  File "/usr/lib/python2.7/UserDict.py", line 110, in iteritems
for k in self:
  File "/usr/lib/python2.7/dist-packages/pytz/lazy.py", line 41, in __iter__
self._fill()
  File "/usr/lib/python2.7/dist-packages/pytz/__init__.py", line 350, in _fill
line = line.decode('US-ASCII')
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 3: ordinal 
not in range(128)

# dpkg-query -l python-tz python3-tz tzdata
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  python-tz  2014.10~dfsg all  Python version of the Olson timez
ii  python3-tz 2014.10~dfsg all  Python3 version of the Olson time
ii  tzdata 2015f-1  all  time zone and daylight-saving tim


Also affect trusty and vivid in the same way.  Testing on trusty shows that 
this broke with the release of tzdata=2015f-0ubuntu0.14.04, prior to that 
tzdata version country_names could parse the data.  debdiff shows that 
tzdata=2015f-0ubuntu0.14.04 changes this file, and others to utf-8 from ascii.

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

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

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

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

Title:
  pytz.country_names UnicodeDecodeError exception

Status in python-tz package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  New

Bug description:
  Wily:
  # python3 -c 'from pytz import country_names
  for item in country_names.items():
print(item)'
  Traceback (most recent call last):
File "", line 2, in 
File "/usr/lib/python3.4/_collections_abc.py", line 497, in __iter__
  for key in self._mapping:
File "/usr/lib/python3/dist-packages/pytz/lazy.py", line 41, in __iter__
  self._fill()
File "/usr/lib/python3/dist-packages/pytz/__init__.py", line 350, in _fill
  line = line.decode('US-ASCII')
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 3: 
ordinal not in range(128)

  # python -c 'from pytz import country_names
  print(country_names)'
  Traceback (most recent call last):
File "", line 2, in 
File "/usr/lib/python2.7/UserDict.py", line 172, in __repr__
  return repr(dict(self.iteritems()))
File "/usr/lib/python2.7/UserDict.py", line 110, in iteritems
  for k in self:
File "/usr/lib/python2.7/dist-packages/pytz/lazy.py", line 41, in __iter__
  self._fill()
File "/usr/lib/python2.7/dist-packages/pytz/__init__.py", line 350, in _fill
  line = line.decode('US-ASCII')
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 3: 
ordinal not in range(128)

  # dpkg-query -l python-tz python3-tz tzdata
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  +++-==---=
  ii  python-tz  2014.10~dfsg all  Python version of the Olson timez
  ii  python3-tz 2014.10~dfsg all  Python3 version of the Olson time
  ii  tzdata 2015f-1  all  time zone and daylight-saving tim

  
  Also affect trusty and vivid in the same way.  Testing on trusty shows that 
this broke with the release of tzdata=2015f-0ubuntu0.14.04, prior to that 
tzdata version country_names could parse the data.  debdiff shows that 
tzdata=2015f-0ubuntu0.14.04 changes this file, and others to utf-8 from ascii.

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

-- 
Mailing list: 

[Touch-packages] [Bug 1494442] Re: Turn crash generation off by default for phone on stable channel

[Pat McGowan]

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

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

Title:
  Turn crash generation off by default for phone on stable channel

Status in Canonical System Image:
  In Progress
Status in lxc-android-config package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Committed

Bug description:
  To avoid UI freezes and perceptions of slowness, we would like to turn
  this option off by default for consumers, but leave it on for
  developers and in the proposed channels.

  Once bug #1437633 is fixed, we can put "manual" in the
  whoopsie.override file

  Not sure how to do this conditionally just for stable

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

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

[Touch-packages] [Bug 1500339] Re: "Close tab" button difficult to tap

[Pat McGowan]

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

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

Title:
  "Close tab" button difficult to tap

Status in Canonical System Image:
  Fix Committed
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  current build number: 123
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  webbrowser-app:
Installé : 0.23+15.04.20150922-0ubuntu1

  I don't know if it's either because the tap area is too small or the
  sensible area is misplaced but the "close tab" button is hard to press
  and very often end up in opening the tab instead of closing it.

  To reproduce, open several tabs, reveal them and try to close several
  by tapping the close icon (cross at right of the title)

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

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

[Touch-packages] [Bug 1499394] Re: Webbrowser doesn't play some YouTube videos

[Pat McGowan]

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

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

Title:
  Webbrowser doesn't play some YouTube videos

Status in Canonical System Image:
  Fix Committed
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Test case.
  - Go to Videos scope.
  - Go to popular YouTube videos section.
  - Tap on a video.
  - After the webbrowser opens, tap on the video to play it.

  Expected result.
  - Video starts playing.

  Actual result.
  - Video seems to load, then does nothing.

  Tip: Long tap on the video to display context menu, and open video in
  new tab. The new tab shows the video in HQ and is able to play it
  correctly.

  This problem was happening from time to time in the past days, and
  seems becoming more frequent for me. Today all the videos in the
  popular scope don't play.

  current build number: 121
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

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

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

[Touch-packages] [Bug 1500992] Re: Provide script to enable IP forwarding

[Martin Pitt]

Adjusting bug title after IRC discussion, see upstream issue summary. We
need something like http://paste.ubuntu.com/12625613/ .

** Summary changed:

- networkd: Don't reset forwarding unless told to do so in config
+ Provide script to enable IP forwarding

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

Title:
  Provide script to enable IP forwarding

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  It's been reported by several LXC users that systemd-networkd will
  turn off per-interface forwarding for all network interfaces when it
  starts.

  Presumably upstream expects users to go and manually edit their config
  to allow it when needed.

  This breaks LXC, libvirt, ... anything which ships a bridge that then
  NAT or route outgoing traffic. Requiring the user to do the config
  change would be a massive regression in user friendliness and having
  lxc, libvirt, ... do it for the user would be a policy violation.

  As a result, I'd recommend we patch systemd to not interfere with
  forwarding unless explicitly configured by the user. This will allow
  all our existing scripts to keep setting things up themselves and have
  it all run fine.

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

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

[Touch-packages] [Bug 1308133] Re: Mir cursor is missing/invisible until the client sets it multiple times

[Alan Griffiths]

** Branch linked: lp:~alan-griffiths/mir/first-test-for-cursors-in-
nested

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

Title:
  Mir cursor is missing/invisible until the client sets it multiple
  times

Status in Mir:
  In Progress
Status in Unity System Compositor:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  Triaged

Bug description:
  Mir cursor is missing/invisible until the client sets it multiple
  times

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

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

[Touch-packages] [Bug 1498992] Re: vcard attachment in gmail not recognized correctly by content-hub

[Pat McGowan]

** 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 webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1498992

Title:
  vcard attachment in gmail not recognized correctly by content-hub

Status in Canonical System Image:
  Fix Committed
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Using latest rc-proposed build r120

  Send yourself a .vcf file as an attachment to your gmail account
  Open gmail webbapp
  Open the message an click on the .vcf attachment

  Expected Results:
  - content-hub should show Contacts app as one of the choices to open with

  Actual Results:
  - Contacts app is not shown in the list

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

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

[Touch-packages] [Bug 1368647] Re: GPS and location detection not working on Nexus 4

[jtd]

Ubuntu phone 15.04 (r23) [mako]

Issue still persists (Weather "Scan for location" returns >100km away;
does not ask me if I wish to "Allow" or "Deny" access; Security &
Privacy > "Using GPS only"; Security & Privacy > "Allow access to
location" does not include Weather app)

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

Title:
  GPS and location detection not working on Nexus 4

Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  Mako with MultiROM, utopic r239

  None of the apps I have tried including Weather, Google maps, OSM
  Touch and SensorStatus are able to use the phone's GPS. The
  SensorStatus app actually reports "Found supported backend", but finds
  no position or other GPS data.

  Location detection on the other hand is doing something, but it is
  really far off when it comes to determining the actual location of the
  device. The Weather app suggests my location as Vänsjö, Jämtland,
  which is about 400 km north of Stockholm where I am at. OSM Touch
  reports "no location available" and Google maps "Your location could
  not be determined"

  I don't know if the GPS has to "waken up" somehow, but it has not
  shown any form of life for me on Ubuntu Touch, even though it works
  perfectly fine when booting the phone as Android.

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

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

[Touch-packages] [Bug 1486004] Re: Cannot import contacts from sim card ( ofono crash )

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

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

** Changed in: canonical-devices-system-image
Milestone: None => ww40-2015

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => John McAleely (john.mcaleely)

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

Title:
  Cannot import contacts from sim card ( ofono crash )

Status in Canonical System Image:
  Fix Committed
Status in address-book-app package in Ubuntu:
  Incomplete
Status in ofono package in Ubuntu:
  Fix Committed

Bug description:
  I open a new bug as asked from this bug (last comment #14) :
  https://bugs.launchpad.net/ubuntu/+source/address-book-
  app/+bug/1331346?comments=all

  I've got a meizu mx4 ubuntu phone, but i cannot import contacts from
  the sim card, it makes some wierd messages but never stop, and no
  contact is imported.

  As asked in the previous bug repport, the /var/log/syslog file attached and 
the output :
  Warning: Permanently added '[127.0.0.1]:1' (RSA) to the list of known 
hosts.
  Welcome to Ubuntu 15.04 (GNU/Linux 3.10.35+ armv7l)

   * Documentation:  https://help.ubuntu.com/
  Last login: Mon Jul 20 17:05:07 2015 from localhost.localdomain
  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/test-phonebook /ril_0
  Traceback (most recent call last):
File "/usr/share/ofono/scripts/test-phonebook", line 23, in 
  print(phonebook.Import(timeout=100))
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
  return self._proxy_method(*args, **keywords)
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
  **keywords)
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in 
call_blocking
  message, timeout)
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message 
did not receive a reply (timeout by message bus)
  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/test-phonebook /ril_1
  Traceback (most recent call last):
File "/usr/share/ofono/scripts/test-phonebook", line 23, in 
  print(phonebook.Import(timeout=100))
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
  return self._proxy_method(*args, **keywords)
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
  **keywords)
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in 
call_blocking
  message, timeout)
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownObject: 
Method "Import" with signature "" on interface "org.ofono.Phonebook" doesn't 
exist

  phablet@ubuntu-phablet:~$

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

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

[Touch-packages] [Bug 1499845] Re: Expose whether an app has a visible BottomEdge

[Michael Terry]

Well, this screen is supposed to appear on the tablet or phone.  Desktop
doesn't show it.  So no worries about convergence.

Design wants it to cover the screen because they want to focus the user
on this one thing.

And to your suggestion #2, it's a little tricky to know when it should
be launched.  This screen should only be launched after all the other
shell edge screens have been shown.  And only if it's never been
completed before.  So the app would need to know that.  So the shell
should be able to communicate that somehow to the app.

But you mention a Tutorial component.  I believe that the design team's
future goals involve letting apps use the same design internally for
their own "how to use this app" tutorials.  But that's maybe orthogonal
to this bug.

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

Title:
  Expose whether an app has a visible BottomEdge

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

Bug description:
  == The Design ==

  The edge tutorial that is shown during the first-boot is getting a
  redesign [1].

  As part of it, the bottom edge tutorial screen is intended to only
  appear after a certain amount of time and only if a user is opening or
  switching to an app with a bottom edge to drag up.

  When that happens, a page appears covering the whole screen, pointing
  to the bottom and saying "Swipe from the bottom edge to manage the
  app".  Then when the user does swipe up, it fades out as the bottom is
  swiped.   I've attached a screenshot of an early mockup for this (back
  when it was designed for the App scope, not an actual app).

  Since it must cover the entire screen (and turn off the launcher and
  panel during it), it should probably be rendered by the shell (which
  is rendering the rest of the tutorial anyway).  So we have to
  coordinate between the app and the shell.

  There are two main technical difficulties in implementing this, the
  way I see it.  Detecting if the current page has a valid BottomEdge
  and synchronizing the fade-out with the bottom-edge drag.

  [1] https://docs.google.com/document/d/1pZ-Ro--
  2eaRzjZKNRoYAeDvQHMkCuyvVuPFWFQfPW4s

  == Detecting BottomEdge ==

  We need:
  1) A BottomEdge SDK component
  2) That is enabled
  3) That is attached to the bottom edge of the app
  4) That is currently being rendered (might be in a Page that isn't on top 
right now)
  5) That isn't obscured by some other widget or MouseArea

  #5 is going to be hard to detect in the wild west of apps from the
  store.  But one thing we could do restrict this to known-well-behaved
  apps that are shipped by default anyway.  The user is most likely to
  be in one of those early on in their phone experience anyway.

  Once the SDK can detect this situation, it needs to signal it somehow.
  Maybe the "valid-bottom-edge" state can bubble up to qtmir's
  ApplicationManager and then the shell.  Any ideas on the best way to
  do that?

  == Synchronizing fade transition ==

  I'm thinking there are two ways:

  1) Communicate from the app to the shell how far the bottom edge has
  been dragged, as it is being dragged.  Presumably via the same channel
  as we communicate that there is a valid bottom edge in the first
  place.

  2) Fake it and have the shell track the drag itself.  It then needs to
  mirror the input to the app so that it also receives the drag.

  #2 is probably easier.  Slightly brittle in case for whatever reason
  the app interferes with the drag or does something on its own that
  would desynchronize the animation.  But again, if we limit this to
  well-known apps, we can avoid that.

  == Open tasks ==

  1) Get general feedback on these ideas
  2) Determine how feasible it is for the SDK to detect a valid BottomEdge
  3) Determine the best way to signal that state from the SDK up to the shell
  4) Implement it

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

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

[Touch-packages] [Bug 1451170] Re: [ ASUS N550LF , Realtek ALC668, Speaker, Internal] To much sound

[dubis]

How to compile hdajacksensetest?

 I fetched the alsa-tools branch but I don't get any compile file or
other.

Thanks.

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

Title:
  [ ASUS N550LF , Realtek ALC668, Speaker, Internal] To much sound

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Hi

  My laptop speaker doesn't want to switch off when my headphones is plugged.
  Description:Ubuntu 15.04
  Release:15.04

  alsa-base:
    Installé : 1.0.25+dfsg-0ubuntu4
    Candidat : 1.0.25+dfsg-0ubuntu4
   Table de version :
   *** 1.0.25+dfsg-0ubuntu4 0
  500 http://fr.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  Thanks for your support

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   dubis1793 F...m pulseaudio
   /dev/snd/controlC1:  dubis1793 F pulseaudio
   /dev/snd/controlC0:  dubis1793 F pulseaudio
  CurrentDesktop: KDE
  Date: Sun May  3 13:25:39 2015
  InstallationDate: Installed on 2014-10-16 (198 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Audio interne - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   dubis1793 F...m pulseaudio
   /dev/snd/controlC1:  dubis1793 F pulseaudio
   /dev/snd/controlC0:  dubis1793 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [hostname, Realtek ALC668, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to vivid on 2015-04-26 (6 days ago)
  dmi.bios.date: 01/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N550LF.212
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N550LF
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN550LF.212:bd01/13/2014:svnASUSTeKCOMPUTERINC.:pnN550LF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550LF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N550LF
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-05-01T15:39:09.184568

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

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

[Touch-packages] [Bug 1427640] Re: indicator-sound-service crashed with signal 5 in main()

[Pat McGowan]

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

** This bug has been marked a duplicate of private bug 1499702

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

Title:
  indicator-sound-service crashed with signal 5 in main()

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  N/A

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: i386
  Date: Mon Mar  2 18:45:39 2015
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service
  InstallationDate: Installed on 2014-12-08 (84 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha i386 (20141208)
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service
  Signal: 5
  SourcePackage: indicator-sound
  StacktraceTop: main ()
  Title: indicator-sound-service crashed with signal 5 in main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1500992] Re: networkd: Don't reset forwarding unless told to do so in config

[Martin Pitt]

Ah, thanks for confirming. This indeed applies to interfaces which
networkd configures; man systemd.network documents this quite clearly.

> Having the bridge setup tool, modify the configuration of all
potential outgoing interface to allow forwarding seems completely wrong
to me

Full ack. Such scripts should not touch the configuration of interfaces
that they didn't set up. This is unexpected, leads to race conditions,
and isn't reliable as you wrote.

Setting to wishlist for now as it's currently behaving as documented.
I'll raise this upstream and see if they are willing to change the
default to "kernel".

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

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

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

Title:
  networkd: Don't reset forwarding unless told to do so in config

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  It's been reported by several LXC users that systemd-networkd will
  turn off per-interface forwarding for all network interfaces when it
  starts.

  Presumably upstream expects users to go and manually edit their config
  to allow it when needed.

  This breaks LXC, libvirt, ... anything which ships a bridge that then
  NAT or route outgoing traffic. Requiring the user to do the config
  change would be a massive regression in user friendliness and having
  lxc, libvirt, ... do it for the user would be a policy violation.

  As a result, I'd recommend we patch systemd to not interfere with
  forwarding unless explicitly configured by the user. This will allow
  all our existing scripts to keep setting things up themselves and have
  it all run fine.

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

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

[Touch-packages] [Bug 1153934] Re: Some radio streams which used to play OK don't play after updating to rhythmbox 2.98 or higher due a libsoup bug

[Elbarbudo]

http://www.radioberlin.de/live.m3u  plays in rhythmbox on my
computer

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

Title:
  Some radio streams which used to play OK don't play after updating to
  rhythmbox  2.98 or higher due a libsoup bug

Status in libsoup:
  Fix Released
Status in libsoup2.4 package in Ubuntu:
  Fix Released

Bug description:
  The following stream, which I have saved in "Radio":

  http://radioclasica.rtve.stream.flumotion.com/rtve/radioclasica.mp3.m3u

  used to play perfectly (heard it daily) with the previous version of
  rhythmbox, but after upgrading to Ubuntu 13.04 which brought a new
  version does not play any more. Some other streams still play
  perfectly, for instance:

  http://www.catmusica.cat/directes/catmusica_wm.m3u

  After clicking the radio nothing happens, it doesn't play the stream
  or produces any other message whatsoever

  WORKAROUND: Run the command "sudo killall gvfsd-http" after playing a
  station.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgstreamer0.10-0 0.10.36-1ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: amd64
  Date: Tue Mar 12 08:22:27 2013
  InstallationDate: Installed on 2010-10-25 (868 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MarkForUpload: True
  SourcePackage: gstreamer0.10
  UpgradeStatus: Upgraded to raring on 2013-03-01 (10 days ago)

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

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

[Touch-packages] [Bug 1501189] Re: Don't put 127.0.0.1 in resolvconf when port=0

[Alkis Georgopoulos]

Better regex to avoid a possibly commented #port=0:
grep -qr "^[[:space:]]*port=0" /etc/dnsmasq.d/ /etc/dnsmasq.conf && return

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

Title:
  Don't put 127.0.0.1 in resolvconf when port=0

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  The following function is defined in /etc/init.d/dnsmasq:

  start_resolvconf()
  {
  # If interface "lo" is explicitly disabled in /etc/default/dnsmasq
  # Then dnsmasq won't be providing local DNS, so don't add it to
  # the resolvconf server set.
  for interface in $DNSMASQ_EXCEPT
  do
  [ $interface = lo ] && return
  done

  if [ -x /sbin/resolvconf ] ; then
  echo "nameserver 127.0.0.1" | /sbin/resolvconf -a lo.$NAME
  fi
  return 0
  }

  When someone puts port=0 in dnsmasq.conf, because e.g. he wants to use it 
only as a (proxy)DHCP/TFTP server,
  127.0.0.1 is added to resolvconf, and DNS is broken because nothing listens 
there.

  One workaround is to put DNSMASQ_EXCEPT=lo in /etc/default/dnsmasq.
  But that doesn't make much sense, we don't want to exclude some interface, 
we're not running a DNS server at all.

  So it would be nice if dnsmasq checked if port=0 is defined in its
  configuration, and didn't add 127.0.0.1 to resolvconf then.

  Sample implementation code, to be inserted before `if [ -x /sbin/resolvconf 
]`:
  grep -qr port=0 /etc/dnsmasq.d/ /etc/dnsmasq.conf && return

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

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

[Touch-packages] [Bug 1397685] Re: git gnutls_handshake() failed: A TLS packet with unexpected length was received.

[Launchpad Bug Tracker]

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

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

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

Title:
  git gnutls_handshake() failed: A TLS packet with unexpected length was
  received.

Status in git package in Ubuntu:
  Confirmed
Status in gnutls26 package in Ubuntu:
  Confirmed
Status in gnutls28 package in Ubuntu:
  Confirmed

Bug description:
  Platform: Ubuntu 14.04, ppc64le (Power 8 LE), git version: 1:1.9.1-1
  When accessing a public repository over HTTPS, I get the following error:
  $ git clone --no-checkout https://git.fedorahosted.org/git/lvm2.git lvm2
  Cloning into 'lvm2'...
  fatal: unable to access 'https://git.fedorahosted.org/git/lvm2.git/': 
gnutls_handshake() failed: A TLS packet with unexpected length was received.

  Accessing the same public repository from a different machine running
  in a different network - also Ubuntu 14.04, but running on x86-64, the
  commands executed with no errors. Both platforms have the same git
  version (dpkg -l | grep git)

  I checked online for an explanation. Found this:
  
http://askubuntu.com/questions/186847/error-gnutls-handshake-falied-when-connecting-to-https-servers

  According to that, Gnu TLS may have some issues when proxies
  (firewalls?) are present on the network path to the repositories. The
  recommended solution is to rebuild git using OpenSSL instead of TLS. I
  tried it and got to a different error ("Unknown SSL protocol error").

  Can you please fix git to make it work correctly?

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

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

[Touch-packages] [Bug 1397685] Re: git gnutls_handshake() failed: A TLS packet with unexpected length was received.

[Launchpad Bug Tracker]

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

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

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

Title:
  git gnutls_handshake() failed: A TLS packet with unexpected length was
  received.

Status in git package in Ubuntu:
  Confirmed
Status in gnutls26 package in Ubuntu:
  Confirmed
Status in gnutls28 package in Ubuntu:
  Confirmed

Bug description:
  Platform: Ubuntu 14.04, ppc64le (Power 8 LE), git version: 1:1.9.1-1
  When accessing a public repository over HTTPS, I get the following error:
  $ git clone --no-checkout https://git.fedorahosted.org/git/lvm2.git lvm2
  Cloning into 'lvm2'...
  fatal: unable to access 'https://git.fedorahosted.org/git/lvm2.git/': 
gnutls_handshake() failed: A TLS packet with unexpected length was received.

  Accessing the same public repository from a different machine running
  in a different network - also Ubuntu 14.04, but running on x86-64, the
  commands executed with no errors. Both platforms have the same git
  version (dpkg -l | grep git)

  I checked online for an explanation. Found this:
  
http://askubuntu.com/questions/186847/error-gnutls-handshake-falied-when-connecting-to-https-servers

  According to that, Gnu TLS may have some issues when proxies
  (firewalls?) are present on the network path to the repositories. The
  recommended solution is to rebuild git using OpenSSL instead of TLS. I
  tried it and got to a different error ("Unknown SSL protocol error").

  Can you please fix git to make it work correctly?

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

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

[Touch-packages] [Bug 1397685] Re: git gnutls_handshake() failed: A TLS packet with unexpected length was received.

[Launchpad Bug Tracker]

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

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

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

Title:
  git gnutls_handshake() failed: A TLS packet with unexpected length was
  received.

Status in git package in Ubuntu:
  Confirmed
Status in gnutls26 package in Ubuntu:
  Confirmed
Status in gnutls28 package in Ubuntu:
  Confirmed

Bug description:
  Platform: Ubuntu 14.04, ppc64le (Power 8 LE), git version: 1:1.9.1-1
  When accessing a public repository over HTTPS, I get the following error:
  $ git clone --no-checkout https://git.fedorahosted.org/git/lvm2.git lvm2
  Cloning into 'lvm2'...
  fatal: unable to access 'https://git.fedorahosted.org/git/lvm2.git/': 
gnutls_handshake() failed: A TLS packet with unexpected length was received.

  Accessing the same public repository from a different machine running
  in a different network - also Ubuntu 14.04, but running on x86-64, the
  commands executed with no errors. Both platforms have the same git
  version (dpkg -l | grep git)

  I checked online for an explanation. Found this:
  
http://askubuntu.com/questions/186847/error-gnutls-handshake-falied-when-connecting-to-https-servers

  According to that, Gnu TLS may have some issues when proxies
  (firewalls?) are present on the network path to the repositories. The
  recommended solution is to rebuild git using OpenSSL instead of TLS. I
  tried it and got to a different error ("Unknown SSL protocol error").

  Can you please fix git to make it work correctly?

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

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

[Touch-packages] [Bug 1497170] Re: New file creation - not opening with file editor

[flocculant]

updates this morning - new file still appears to be unknown type when
created, but does open with text editor on double click

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

Title:
  New file creation - not opening with file editor

Status in GLib:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in glib2.0 package in Ubuntu:
  Triaged
Status in xdg-utils package in Ubuntu:
  Invalid

Bug description:
  Create a new file from File - Create Empty File.

  Open new document:

  expected behaviour - document opens in text editor

  actual behaviour - Open With dialogue opens requiring an application
  to open file.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: thunar 1.6.10-1
  ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0
  Uname: Linux 4.2.0-10-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Sep 18 09:05:54 2015
  InstallationDate: Installed on 2015-09-17 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150917)
  SourcePackage: thunar
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2015-09-17 (1 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150917)
  Package: xdg-utils 1.1.0~rc3+git20150907-1ubuntu2
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0
  Tags:  wily
  Uname: Linux 4.2.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1486341] Re: [performance] Touch scrolling is stuttery under Unity8 (but only while you're touching it)

[Daniel van Vugt]

Annoyingly, in order to reliably set QML_NO_TOUCH_COMPRESSION, you have
to do it in the parent process before unity8 or the Qt client is
launched.  Because it's only checked once on static initialization:

static bool qquickwindow_no_touch_compression =
qEnvironmentVariableIsSet("QML_NO_TOUCH_COMPRESSION");

So whatever is launching unity8 (upstart job?) has to set
QML_NO_TOUCH_COMPRESSION. And the same goes for Qt apps.

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

Title:
  [performance] Touch scrolling is stuttery under Unity8 (but only while
  you're touching it)

Status in QtMir:
  New
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Touch scrolling is stuttery under Unity8 (but only while you're
  touching it).

  I noticed that Unity8 is smooth in some parts and stutters in others.
  Turns out the smooth parts of Unity8 like the indicators pull-down and
  app switcher are the parts that don't have to run as clients of the
  nested server. I also noticed that those stuttering clients (like the
  dash) of the nested server only stutter while you're touching them.
  They animate smoothly if you fling them lifting your finger off, but
  stutter while they have to track your finger.

  Turns out the problem is Qt's built-in input resampling introduced in
  Qt 5.4 (commit 6dc8f47bb05a8acb3cbcc697e0dc05356a01d4cf). Turning it
  off in the unity8 process (env QML_NO_TOUCH_COMPRESSION=1) fixes the
  touch scrolling smoothness problem for clients like unity8-dash.

  I suspected this would be the case. It's possible the Qt resampling 
implementation doesn't work when nested. That would be unsurprising, having 
implemented Mir's input resampling I know that can be a problem. Although Mir's 
input resampling is designed in such a way that performance is unaffected by 
nesting. The below test case and also:
    https://bugreports.qt.io/browse/QTBUG-40167 (maybe unrelated)
  both suggest that the Qt input resampling introduced by Jolla is causing 
stuttering, particularly when nested in a situation where the incoming touch 
events are already throttled...

  Measurements from arale:

  restart unity8-dash MIR_CLIENT_PERF_REPORT=log
  tail -f ~/.cache/upstart/unity8-dash.log

  [1439957791.298680] perf: Scopes: 52.42 FPS, render time 17.90ms, buffer lag 
39.37ms (3 buffers)
  [1439957792.303939] perf: Scopes: 54.72 FPS, render time 17.07ms, buffer lag 
37.57ms (3 buffers)
  [1439957793.316036] perf: Scopes: 55.33 FPS, render time 16.82ms, buffer lag 
36.90ms (3 buffers)
  [1439957794.329848] perf: Scopes: 56.26 FPS, render time 16.21ms, buffer lag 
37.69ms (3 buffers)
  [1439957795.335884] perf: Scopes: 52.68 FPS, render time 18.05ms, buffer lag 
38.87ms (3 buffers)
  [1439957796.343125] perf: Scopes: 51.63 FPS, render time 18.03ms, buffer lag 
40.15ms (3 buffers)
  [1439957797.360229] perf: Scopes: 54.08 FPS, render time 17.41ms, buffer lag 
38.04ms (3 buffers)
  [1439957798.370706] perf: Scopes: 54.45 FPS, render time 17.18ms, buffer lag 
37.99ms (3 buffers)
  [1439957799.401308] perf: Scopes: 53.39 FPS, render time 17.79ms, buffer lag 
37.43ms (3 buffers)

  restart unity8 QML_NO_TOUCH_COMPRESSION=1
  restart unity8-dash MIR_CLIENT_PERF_REPORT=log
  tail -f ~/.cache/upstart/unity8-dash.log

  [1439957936.543370] perf: Scopes: 59.64 FPS, render time 15.52ms, buffer lag 
34.48ms (3 buffers)
  [1439957937.543547] perf: Scopes: 59.00 FPS, render time 16.36ms, buffer lag 
34.26ms (3 buffers)
  [1439957938.571699] perf: Scopes: 59.33 FPS, render time 16.26ms, buffer lag 
34.22ms (3 buffers)
  [1439957939.572860] perf: Scopes: 59.94 FPS, render time 15.76ms, buffer lag 
34.32ms (3 buffers)
  [1439957940.581339] perf: Scopes: 62.50 FPS, render time 14.68ms, buffer lag 
33.75ms (3 buffers)
  [1439957941.594696] perf: Scopes: 59.23 FPS, render time 14.81ms, buffer lag 
35.83ms (3 buffers)
  [1439957942.597224] perf: Scopes: 61.87 FPS, render time 14.64ms, buffer lag 
33.96ms (3 buffers)
  [1439957943.612315] perf: Scopes: 61.08 FPS, render time 14.59ms, buffer lag 
34.39ms (3 buffers)
  [1439957944.625835] perf: Scopes: 60.21 FPS, render time 15.79ms, buffer lag 
34.28ms (3 buffers)

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

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

[Touch-packages] [Bug 1153934] Re: Some radio streams which used to play OK don't play after updating to rhythmbox 2.98 or higher due a libsoup bug

[Walter Garcia-Fontes]

http://www.radioberlin.de/live.m3u plays also fine in my system:

$ apt-cache policy rhythmbox
rhythmbox:
  Installed: 3.2.1-1ubuntu3
  Candidate: 3.2.1-1ubuntu3
  Version table:
 *** 3.2.1-1ubuntu3 0
500 http://ftp.caliu.cat/pub/distribucions/ubuntu/archive/ wily/main 
amd64 Packages
100 /var/lib/dpkg/status

I'm using Ubuntu 13.10 development version, but this has been fixed for
a couple of versions already.

@krychek, if you think this is an issue for you try to file a bug with
the information of your system, following the instructions in
https://help.ubuntu.com/community/ReportingBugs

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

Title:
  Some radio streams which used to play OK don't play after updating to
  rhythmbox  2.98 or higher due a libsoup bug

Status in libsoup:
  Fix Released
Status in libsoup2.4 package in Ubuntu:
  Fix Released

Bug description:
  The following stream, which I have saved in "Radio":

  http://radioclasica.rtve.stream.flumotion.com/rtve/radioclasica.mp3.m3u

  used to play perfectly (heard it daily) with the previous version of
  rhythmbox, but after upgrading to Ubuntu 13.04 which brought a new
  version does not play any more. Some other streams still play
  perfectly, for instance:

  http://www.catmusica.cat/directes/catmusica_wm.m3u

  After clicking the radio nothing happens, it doesn't play the stream
  or produces any other message whatsoever

  WORKAROUND: Run the command "sudo killall gvfsd-http" after playing a
  station.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgstreamer0.10-0 0.10.36-1ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: amd64
  Date: Tue Mar 12 08:22:27 2013
  InstallationDate: Installed on 2010-10-25 (868 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MarkForUpload: True
  SourcePackage: gstreamer0.10
  UpgradeStatus: Upgraded to raring on 2013-03-01 (10 days ago)

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

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

[Touch-packages] [Bug 1500992] Re: networkd: Don't reset forwarding unless told to do so in config

[Martin Pitt]

Raising priority; on second thought this is actually interfering with
configuration. Forwarded to
https://github.com/systemd/systemd/issues/1411 , I'd like to change this
upstream if at all possible.

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

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

Title:
  networkd: Don't reset forwarding unless told to do so in config

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  It's been reported by several LXC users that systemd-networkd will
  turn off per-interface forwarding for all network interfaces when it
  starts.

  Presumably upstream expects users to go and manually edit their config
  to allow it when needed.

  This breaks LXC, libvirt, ... anything which ships a bridge that then
  NAT or route outgoing traffic. Requiring the user to do the config
  change would be a massive regression in user friendliness and having
  lxc, libvirt, ... do it for the user would be a policy violation.

  As a result, I'd recommend we patch systemd to not interfere with
  forwarding unless explicitly configured by the user. This will allow
  all our existing scripts to keep setting things up themselves and have
  it all run fine.

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

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

[Touch-packages] [Bug 1476662] Re: lxc-start symlink vulnerabilities may allow guest to read host filesystem, interfere with apparmor

[Daniel Kraft]

We're getting

lxc-start: utils.c: safe_mount: 1409 Mount of 'proc' onto
'/usr/lib/x86_64-linux-gnu/lxc//proc' was onto a symlink!

on all containers since we upgraded to 1.0.7-0ubuntu0.5 and they don't
start. No container has /proc as a symlink. Plese tell me what
information is required from me.

We downgraded to 1.0.6-0ubuntu0.1 which works.

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

Title:
  lxc-start symlink vulnerabilities may allow guest to read host
  filesystem, interfere with apparmor

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  lxc-start shuffles around mounts using helper directory
  /usr/lib/x86_64-linux-gnu/lxc (guest root fs is mounted here)

  It then modifies mounts operating in guest root directory before
  invoking init. As it does not check if all mount points are
  directories, a malicious guest may modify its internal structure
  before shutdown (or was created using manipulated image) and then when
  started again, guest may

  * Access  the whole host root filesystem

  * Block switching from lxc-start apparmor profile to lxc-container-
  default

  
  # Real putold before pivot-root (root fs will end here)
  mkdir -p /x/lxc_putold

  # Faked putold
  ln -s /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold lxc_putold
  mkdir -p /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold/proc
  touch /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold/proc/mounts

  
  # proc fake
  mkdir -p /x/proc
  umount /proc
  rmdir /proc
  ln -s /usr/lib/x86_64-linux-gnu/lxc/x/proc proc

  mkdir -p /usr/lib/x86_64-linux-gnu/lxc/x/proc/1/attr 
/usr/lib/x86_64-linux-gnu/lxc/x/proc/self
  touch /usr/lib/x86_64-linux-gnu/lxc/x/proc/1/attr/current
  touch /usr/lib/x86_64-linux-gnu/lxc/x/proc/self/status


  The  issue was also found during
  https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.html

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

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

[Touch-packages] [Bug 1323586] Re: oneconf crashes if one apt list file is unreadable

[Sebastien Bacher]

That seems to still be an issue, sent to debian, https://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=800500

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

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

Title:
  oneconf crashes if one apt list file is unreadable

Status in python-apt package in Ubuntu:
  Invalid

Bug description:
  oneconf-service will crash if one of the files in
  `/etc/apt/sources.list.d` is unreadable (for example because it has
  been created using sudo and umask 077).

  In my case this is the error message

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/oneconf/packagesethandler.py", 
line 63, in update
  newpkg_list = self.distro.compute_local_packagelist()
File "/usr/lib/python3/dist-packages/oneconf/distributor/Ubuntu.py", 
line 42, in compute_local_packagelist
  with apt.Cache() as apt_cache:
File "/usr/lib/python3/dist-packages/apt/cache.py", line 107, in 
__init__
  self.open(progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 155, in open
  self._list.read_main_list()
  SystemError: E:Opening /etc/apt/sources.list.d/tor.list - 
ifstream::ifstream (13: Permission denied)

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

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

[Touch-packages] [Bug 1498945] Re: [libglib2.0] evolution + evolution-ews

[mangouste06]

** Bug watch added: GNOME Bug Tracker #755075
   https://bugzilla.gnome.org/show_bug.cgi?id=755075

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

Title:
  [libglib2.0] evolution + evolution-ews

Status in GLib:
  Invalid
Status in evolution package in Ubuntu:
  New
Status in evolution-ews package in Ubuntu:
  New
Status in glib2.0 package in Ubuntu:
  New

Bug description:
  I have two different exchange email configurated in evolution through
  evolution-ews.

  With

  libglib2.0-0_2.45.7-1_amd64.deb
  libglib2.0-bin_2.45.7-1_amd64.deb
  libglib2.0-data_2.45.7-1_all.deb

  it's working. I get new mails. I can send mails. Calendar OK.

  But, with the new

  libglib2.0-0_2.45.8-1_amd64.deb
  libglib2.0-bin_2.45.8-1_amd64.deb
  libglib2.0-data_2.45.8-1_all.deb

  I can't even connect to the mail servers.

  I can switch from working/not working and back in the  same unity
  session just by switching libglib versions and restarting evolution.

  I'm in wily uptodate.

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

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

[Touch-packages] [Bug 1501219] [NEW] in ubuntu 14.4.03, package python3.4 version "3.4.3-1ubuntu1~14.04.1" doesn't have the executable pyvenv-3.4

[ardelean vlad-george]

Public bug reported:

On the python changelog, it doesn't say anything that this executable
should be missing, on the  contrary.

The executable is present in the package version "3.4.0-2ubuntu1.1".

Worth mentioning is that I imported a vagrant virtual machine image from here:
https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box

Previously when I had done that, the version "3.4.0-2ubuntu1.1" was
installed, but now, the version "3.4.3-1ubuntu1~14.04.1" came up.

** Affects: python3.4 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: packaging upgrade-software-version

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

Title:
  in ubuntu 14.4.03, package python3.4 version "3.4.3-1ubuntu1~14.04.1"
  doesn't have the executable pyvenv-3.4

Status in python3.4 package in Ubuntu:
  New

Bug description:
  On the python changelog, it doesn't say anything that this executable
  should be missing, on the  contrary.

  The executable is present in the package version "3.4.0-2ubuntu1.1".

  Worth mentioning is that I imported a vagrant virtual machine image from here:
  
https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box

  Previously when I had done that, the version "3.4.0-2ubuntu1.1" was
  installed, but now, the version "3.4.3-1ubuntu1~14.04.1" came up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1501219/+subscriptions

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

[Touch-packages] [Bug 1323586] Re: oneconf crashes if one apt list file is unreadable

[Julian Andres Klode]

This is not a bug. First of all, it's not a bug in python-apt because we
use APT to parse. Secondly, we have no intention of ignoring unreadable
sources.list files as that would present an inconsistent view of the
available sources.

** Changed in: python-apt (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  oneconf crashes if one apt list file is unreadable

Status in oneconf package in Ubuntu:
  Confirmed
Status in python-apt package in Ubuntu:
  Won't Fix

Bug description:
  oneconf-service will crash if one of the files in
  `/etc/apt/sources.list.d` is unreadable (for example because it has
  been created using sudo and umask 077).

  In my case this is the error message

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/oneconf/packagesethandler.py", 
line 63, in update
  newpkg_list = self.distro.compute_local_packagelist()
File "/usr/lib/python3/dist-packages/oneconf/distributor/Ubuntu.py", 
line 42, in compute_local_packagelist
  with apt.Cache() as apt_cache:
File "/usr/lib/python3/dist-packages/apt/cache.py", line 107, in 
__init__
  self.open(progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 155, in open
  self._list.read_main_list()
  SystemError: E:Opening /etc/apt/sources.list.d/tor.list - 
ifstream::ifstream (13: Permission denied)

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

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

[Touch-packages] [Bug 1484470] Re: aptsources.sourceslist or softwareproperties.ppa calling out to system-image-cli erroneously

[Julian Andres Klode]

This is fixed in upstream 1.0, the bug number linked is the wrong one
though unfortunately.

I asked infinity about syncing this half a month ago, as it's the final
release of 1.0, and fixes another important bug that is currently in
vivid for example, namely other tools complaining about invalid PEP440
version numbers for python-apt, which has happened once again since the
last upload to wily.


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

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

Title:
  aptsources.sourceslist or softwareproperties.ppa calling out to
  system-image-cli erroneously

Status in python-apt package in Ubuntu:
  Fix Committed

Bug description:
  daniel@daydream:~$ sudo add-apt-repository ppa:snappy-dev/snapcraft-daily
  usage: system-image-cli [-h] [--version] [-C DIRECTORY] [-b BUILD]
  [-c CHANNEL] [-d DEVICE] [-f FILTER] [-g]
  [--no-reboot] [-i] [-n] [-v] [--progress PROGRESS]
  [-p PERCENTAGE] [--list-channels] [--factory-reset]
  [--production-reset] [--switch CHANNEL]
  [--show-settings] [--set KEY=VAL] [--get KEY]
  [--del KEY]
  system-image-cli: error: 
  Configuration directory not found: /etc/system-image/config.d
  usage: system-image-cli [-h] [--version] [-C DIRECTORY] [-b BUILD]
  [-c CHANNEL] [-d DEVICE] [-f FILTER] [-g]
  [--no-reboot] [-i] [-n] [-v] [--progress PROGRESS]
  [-p PERCENTAGE] [--list-channels] [--factory-reset]
  [--production-reset] [--switch CHANNEL]
  [--show-settings] [--set KEY=VAL] [--get KEY]
  [--del KEY]
  system-image-cli: error: 
  Configuration directory not found: /etc/system-image/config.d
  usage: system-image-cli [-h] [--version] [-C DIRECTORY] [-b BUILD]
  [-c CHANNEL] [-d DEVICE] [-f FILTER] [-g]
  [--no-reboot] [-i] [-n] [-v] [--progress PROGRESS]
  [-p PERCENTAGE] [--list-channels] [--factory-reset]
  [--production-reset] [--switch CHANNEL]
  [--show-settings] [--set KEY=VAL] [--get KEY]
  [--del KEY]
  system-image-cli: error: 
  Configuration directory not found: /etc/system-image/config.d
   Snapcraft daily builds, use only at your own risk!
   Mehr Informationen: 
https://launchpad.net/~snappy-dev/+archive/ubuntu/snapcraft-daily
  Drücken Sie [ENTER], um fortzufahren oder Strg-c, um das Hinzufügen 
abzubrechen

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: python-apt 1.0.0~beta3ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Aug 13 12:48:15 2015
  InstallationDate: Installed on 2015-04-30 (104 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: python-apt
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1489444] Re: ipa-client-install: certmonger failed to stop: [Errno 2] No such file or directory: '/var/run/ipa/services.list'

[Julian Andres Klode]

Well if the file is not there, python-(APT) cannot use it... Since this
is apparently created by a PPA package, and I cannot reassign things
there, I'm closing it.

** Changed in: python-apt (Ubuntu)
   Status: New => Invalid

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

Title:
  ipa-client-install: certmonger failed to stop: [Errno 2] No such file
  or directory: '/var/run/ipa/services.list'

Status in python-apt package in Ubuntu:
  Invalid

Bug description:
  using the FreeIPA PPA

  Weird message when enrolling:
  certmonger failed to stop: [Errno 2] No such file or directory: 
'/var/run/ipa/services.list'
  APart from this, all seems to work quite fine.

  sudo ipa-client-install --enable-dns-updates --server=ipa.example.com
  -p admin --mkhomedir --force-join --domain example.com -N --hostname
  apache.example.com

  Autodiscovery of servers for failover cannot work with this configuration.
  If you proceed with the installation, services will be configured to always 
access the discovered server for all operations and will not fail over to other 
servers in case of failure.
  Proceed with fixed values and no DNS discovery? [no]: yes
  Hostname: apache.example.com
  Realm: example.COM
  DNS Domain: example.com
  IPA Server: ipa.example.com
  BaseDN: dc=example,dc=com

  Continue to configure the system with these values? [no]: yes
  Synchronizing time with KDC...
  Unable to sync time with IPA NTP server, assuming the time is in sync. Please 
check that 123 UDP port is opened.
  Password for ad...@example.com: 
  Successfully retrieved CA cert
  Subject: CN=Certificate Authority,O=example.COM
  Issuer:  CN=Certificate Authority,O=example.COM
  Valid From:  Thu Jul 09 09:41:54 2015 UTC
  Valid Until: Mon Jul 09 09:41:54 2035 UTC

  Enrolled in IPA realm example.COM
  Created /etc/ipa/default.conf
  New SSSD config will be created
  Configured /etc/sssd/sssd.conf
  Configured /etc/krb5.conf for IPA realm example.COM
  Hostname (apache.example.com) not found in DNS
  DNS server record set to: apache.example.com -> 10.0.2.15
  certmonger failed to stop: [Errno 2] No such file or directory: 
'/var/run/ipa/services.list'
  Adding SSH public key from /etc/ssh/ssh_host_dsa_key.pub
  Adding SSH public key from /etc/ssh/ssh_host_ed25519_key.pub
  Adding SSH public key from /etc/ssh/ssh_host_ecdsa_key.pub
  Adding SSH public key from /etc/ssh/ssh_host_rsa_key.pub
  SSSD enabled
  Configured /etc/openldap/ldap.conf
  Configured /etc/ssh/ssh_config
  Configured /etc/ssh/sshd_config
  Client configuration complete.

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

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

[Touch-packages] [Bug 1323586] Re: oneconf crashes if one apt list file is unreadable

[Gioele Barabucci]

It may not be a bug in python-apt, but it is a bug nevertheless. If
unreadable files are not supported, the applications should ignore them
or complain about them, not crash and raise an apport dialog every hour.

Please note that it is very easy to generate files in `sources.list.d`
that are not readable by normal users. Just use `sudo apt-add-
repository` and a 077 umask.

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

Title:
  oneconf crashes if one apt list file is unreadable

Status in oneconf package in Ubuntu:
  Confirmed
Status in python-apt package in Ubuntu:
  Won't Fix

Bug description:
  oneconf-service will crash if one of the files in
  `/etc/apt/sources.list.d` is unreadable (for example because it has
  been created using sudo and umask 077).

  In my case this is the error message

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/oneconf/packagesethandler.py", 
line 63, in update
  newpkg_list = self.distro.compute_local_packagelist()
File "/usr/lib/python3/dist-packages/oneconf/distributor/Ubuntu.py", 
line 42, in compute_local_packagelist
  with apt.Cache() as apt_cache:
File "/usr/lib/python3/dist-packages/apt/cache.py", line 107, in 
__init__
  self.open(progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 155, in open
  self._list.read_main_list()
  SystemError: E:Opening /etc/apt/sources.list.d/tor.list - 
ifstream::ifstream (13: Permission denied)

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

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

[Touch-packages] [Bug 1323586] Re: oneconf crashes if one apt list file is unreadable

[Sebastien Bacher]

The Debian maintainer marked that as wontfix for apt, that should be
handled by the client

"Unreadable sources.list files are an unsupported mode of operation
and will not be supported in neither APT nor python-apt (which
directly calls the functions from APT).

Authentication data should not be stored in sources.list files,
but in a netrc file. Using that, there's no need for unreadable
sources.list files.

If you cannot read a sources.list file, the state would be
inconsistent."

** Changed in: python-apt (Ubuntu)
   Status: Invalid => Won't Fix

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

** Changed in: oneconf (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  oneconf crashes if one apt list file is unreadable

Status in oneconf package in Ubuntu:
  Confirmed
Status in python-apt package in Ubuntu:
  Won't Fix

Bug description:
  oneconf-service will crash if one of the files in
  `/etc/apt/sources.list.d` is unreadable (for example because it has
  been created using sudo and umask 077).

  In my case this is the error message

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/oneconf/packagesethandler.py", 
line 63, in update
  newpkg_list = self.distro.compute_local_packagelist()
File "/usr/lib/python3/dist-packages/oneconf/distributor/Ubuntu.py", 
line 42, in compute_local_packagelist
  with apt.Cache() as apt_cache:
File "/usr/lib/python3/dist-packages/apt/cache.py", line 107, in 
__init__
  self.open(progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 155, in open
  self._list.read_main_list()
  SystemError: E:Opening /etc/apt/sources.list.d/tor.list - 
ifstream::ifstream (13: Permission denied)

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

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

[Touch-packages] [Bug 1476662] Re: lxc-start symlink vulnerabilities may allow guest to read host filesystem, interfere with apparmor

[Roman Fiedler]

Does  https://lists.linuxcontainers.org/pipermail/lxc-
users/2015-September/010131.html point to the same problem?

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

Title:
  lxc-start symlink vulnerabilities may allow guest to read host
  filesystem, interfere with apparmor

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  lxc-start shuffles around mounts using helper directory
  /usr/lib/x86_64-linux-gnu/lxc (guest root fs is mounted here)

  It then modifies mounts operating in guest root directory before
  invoking init. As it does not check if all mount points are
  directories, a malicious guest may modify its internal structure
  before shutdown (or was created using manipulated image) and then when
  started again, guest may

  * Access  the whole host root filesystem

  * Block switching from lxc-start apparmor profile to lxc-container-
  default

  
  # Real putold before pivot-root (root fs will end here)
  mkdir -p /x/lxc_putold

  # Faked putold
  ln -s /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold lxc_putold
  mkdir -p /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold/proc
  touch /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold/proc/mounts

  
  # proc fake
  mkdir -p /x/proc
  umount /proc
  rmdir /proc
  ln -s /usr/lib/x86_64-linux-gnu/lxc/x/proc proc

  mkdir -p /usr/lib/x86_64-linux-gnu/lxc/x/proc/1/attr 
/usr/lib/x86_64-linux-gnu/lxc/x/proc/self
  touch /usr/lib/x86_64-linux-gnu/lxc/x/proc/1/attr/current
  touch /usr/lib/x86_64-linux-gnu/lxc/x/proc/self/status


  The  issue was also found during
  https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.html

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

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

[Touch-packages] [Bug 1476662] Re: lxc-start symlink vulnerabilities may allow guest to read host filesystem, interfere with apparmor

[Daniel Kraft]

The problem lies in the ubuntu patch

http://archive.ubuntu.com/ubuntu/pool/main/l/lxc/lxc_1.0.7-0ubuntu0.5.debian.tar.gz

where this code

+   size_t start = croot ? strlen(croot) : 0;
+   if (strcmp(ws + start, target + start) != 0) {
+   ERROR("Mount onto %s resulted in %s\n", target, ws);
+   goto out;
+   }

in file 0003-CVE-2015-1335.patch checks if ws and start are the same.
According to the given error (which I forgot to paste above), ws and target ARE 
different:

lxc-start: utils.c: ensure_not_symlink: 1384 Mount onto /usr/lib/x86_64
-linux-gnu/lxc//proc resulted in /usr/lib/x86_64-linux-gnu/lxc/proc

So target is

  /usr/lib/x86_64-linux-gnu/lxc//proc

and ws is

   /usr/lib/x86_64-linux-gnu/lxc/proc

Any hints how we could prevent the double slashing? Or would you just
"clean up" the path somehow?

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

Title:
  lxc-start symlink vulnerabilities may allow guest to read host
  filesystem, interfere with apparmor

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  lxc-start shuffles around mounts using helper directory
  /usr/lib/x86_64-linux-gnu/lxc (guest root fs is mounted here)

  It then modifies mounts operating in guest root directory before
  invoking init. As it does not check if all mount points are
  directories, a malicious guest may modify its internal structure
  before shutdown (or was created using manipulated image) and then when
  started again, guest may

  * Access  the whole host root filesystem

  * Block switching from lxc-start apparmor profile to lxc-container-
  default

  
  # Real putold before pivot-root (root fs will end here)
  mkdir -p /x/lxc_putold

  # Faked putold
  ln -s /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold lxc_putold
  mkdir -p /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold/proc
  touch /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold/proc/mounts

  
  # proc fake
  mkdir -p /x/proc
  umount /proc
  rmdir /proc
  ln -s /usr/lib/x86_64-linux-gnu/lxc/x/proc proc

  mkdir -p /usr/lib/x86_64-linux-gnu/lxc/x/proc/1/attr 
/usr/lib/x86_64-linux-gnu/lxc/x/proc/self
  touch /usr/lib/x86_64-linux-gnu/lxc/x/proc/1/attr/current
  touch /usr/lib/x86_64-linux-gnu/lxc/x/proc/self/status


  The  issue was also found during
  https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.html

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

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

[Touch-packages] [Bug 1476740] Re: python-apt ftbfs using GCC 5

[Julian Andres Klode]

Can we close this now?

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

Title:
  python-apt ftbfs using GCC 5

Status in python-apt package in Ubuntu:
  Fix Committed

Bug description:
  see the PPA build in 
  
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-016/+sourcepub/5224902/+listing-archive-extra

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

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

[Touch-packages] [Bug 1497975] Re: systemctl service NetworkManager reports GLib errors in status

[Thilo Cestonaro]

Seems to be fixed with network-manager 1.0.4-0ubuntu4. DBus works again
and systemctl status doesn't show the assertions anymore.

Thanks!

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

Title:
  systemctl service NetworkManager reports GLib errors in status

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Wily (packages updated today latest):

  Visual:
  nm-applet is not showing up
  network not configured

  background:
  sudo systemctl status network-manager -l

  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Mo 2015-09-21 14:07:47 CEST; 18s ago
   Main PID: 5605 (NetworkManager)
 CGroup: /system.slice/NetworkManager.service
 └─5605 /usr/sbin/NetworkManager --no-daemon

  Sep 21 14:07:47 myhost NetworkManager[5605]:   devices added (path: 
/sys/devices/virtual/net/lo, iface: lo)
  Sep 21 14:07:47 myhost NetworkManager[5605]:   device added (path: 
/sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
  Sep 21 14:07:47 myhost NetworkManager[5605]:   end _init.
  Sep 21 14:07:47 myhost NetworkManager[5605]:   Loaded settings plugin 
ifupdown: (C) 2008 Canonical Ltd.  To report bugs please use the NetworkManager 
mailing list. 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-settings-plugin-ifupdown.so)
  Sep 21 14:07:47 myhost NetworkManager[5605]:   Loaded settings plugin 
keyfile: (c) 2007 - 2015 Red Hat, Inc.  To report bugs please use the 
NetworkManager mailing list.
  Sep 21 14:07:47 myhost NetworkManager[5605]: (NetworkManager:5605): 
GLib-GObject-WARNING **: cannot register existing type 'NMSetting'
  Sep 21 14:07:47 myhost NetworkManager[5605]: (NetworkManager:5605): 
GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed
  Sep 21 14:07:47 myhost NetworkManager[5605]: (NetworkManager:5605): 
GLib-GObject-CRITICAL **: g_type_register_static: assertion 'parent_type > 0' 
failed
  Sep 21 14:07:47 myhost NetworkManager[5605]: (NetworkManager:5605): 
libnm-util-CRITICAL **: _nm_register_setting: assertion 'type != 
G_TYPE_INVALID' failed
  Sep 21 14:07:47 myhost NetworkManager[5605]: (NetworkManager:5605): 
GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

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

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

[Touch-packages] [Bug 1500753] Re: [80ES, Realtek ALC233, Black Headphone Out, Right] Playback problem

[Raymond]

Sep 28 15:26:32 username-Lenovo-B50-30 bluetoothd[596]: Unable to get service 
record: Host is down (112)
Sep 28 15:26:35 username-Lenovo-B50-30 NetworkManager[575]:  Connection 
disconnected (reason -4)
Sep 28 15:26:37 username-Lenovo-B50-30 bluetoothd[596]: Host is down (112)
Sep 28 15:27:36 username-Lenovo-B50-30 pulseaudio[1430]: [pulseaudio] 
module-bluez4-device.c: Default profile not connected, selecting off profile
Sep 28 15:27:36 username-Lenovo-B50-30 bluetoothd[596]: Badly formated or 
unrecognized command: AT+BIA=0,0,1,1,1,1,0
Sep 28 15:27:36 username-Lenovo-B50-30 bluetoothd[596]: Badly formated or 
unrecognized command: AT+CSRSF=0,0,0,1,0,0,0
Sep 28 15:27:46 username-Lenovo-B50-30 bluetoothd[596]: Audio connection got 
disconnected
Sep 28 15:31:45 username-Lenovo-B50-30 NetworkMan

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

Title:
  [80ES, Realtek ALC233, Black Headphone Out, Right] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  the sounds works perfectly after every fresh boot, however, if I keep
  it over night and let the computer pause, i have to restart it to use
  the headphones again. Not sure if something breaks when the computer
  pauses or simply after some hours of running.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   kunz   1430 F...m pulseaudio
   /dev/snd/controlC0:  kunz   1430 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Sep 29 10:41:44 2015
  InstallationDate: Installed on 2015-08-13 (46 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Internes Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [80ES, Realtek ALC233, Black Headphone Out, Right] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/06/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9CCN26WW(V2.04)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo B50-30
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvr9CCN26WW(V2.04):bd06/06/2014:svnLENOVO:pn80ES:pvrLenovoB50-30:rvnLENOVO:rnLenovoB50-30:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoB50-30:
  dmi.product.name: 80ES
  dmi.product.version: Lenovo B50-30
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1498945] Re: [libglib2.0] evolution + evolution-ews

[mangouste06]

Hi,

can we test with the proposed patch in
https://bugzilla.gnome.org/show_bug.cgi?id=755075 ?


2015-09-29 18:22 GMT+02:00 Bug Watch Updater
<1498...@bugs.launchpad.net>:

> ** Changed in: glib
>Status: Confirmed => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1498945
>
> Title:
>   [libglib2.0] evolution + evolution-ews
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/glib/+bug/1498945/+subscriptions
>

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

Title:
  [libglib2.0] evolution + evolution-ews

Status in GLib:
  Invalid
Status in evolution package in Ubuntu:
  New
Status in evolution-ews package in Ubuntu:
  New
Status in glib2.0 package in Ubuntu:
  New

Bug description:
  I have two different exchange email configurated in evolution through
  evolution-ews.

  With

  libglib2.0-0_2.45.7-1_amd64.deb
  libglib2.0-bin_2.45.7-1_amd64.deb
  libglib2.0-data_2.45.7-1_all.deb

  it's working. I get new mails. I can send mails. Calendar OK.

  But, with the new

  libglib2.0-0_2.45.8-1_amd64.deb
  libglib2.0-bin_2.45.8-1_amd64.deb
  libglib2.0-data_2.45.8-1_all.deb

  I can't even connect to the mail servers.

  I can switch from working/not working and back in the  same unity
  session just by switching libglib versions and restarting evolution.

  I'm in wily uptodate.

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

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

[Touch-packages] [Bug 1497105] Re: Clients can't get high resolution input in Unity8

[Daniel van Vugt]

Test case for mako (using Mir 0.16 syntax):

   env MIR_CLIENT_PERF_REPORT=log mir_demo_client_target -n --
--desktop_file_hint=dialer-app

Expect: The reported FPS is higher than the display refresh rate (above
90 on mako).

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

Title:
  Clients can't get high resolution input in Unity8

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

Bug description:
  Clients can't get high resolution input in Unity8.

  Using native (non-nested) Mir servers, clients can get the full speed
  input stream if they so choose (MIR_CLIENT_INPUT_RATE=0). And it's
  planned that this will become a formal API feature: bug 1439590

  However in Unity8, because it is a nested server, the client no longer
  has the option of getting this high resolution input.

  Examples of clients that utilize high resolution input for improved visual 
quality:
 mir_demo_client_fingerpaint -w--desktop_file_hint=unity8
 mir_demo_client_target -n--desktop_file_hint=unity8
  You may also want to experiment with those using ultra-high resolution input 
by adding a kernel parameter: usbhid.mousepoll=1

  This is a tricky problem because for touch at least we do want the
  input stream to be throttled to the display rate from the top level
  down. Perhaps the answer is to enhance Unity8 to be a full-speed (non-
  resampled) client and then the clients of Unity8 can then still have a
  choice of whether they get resampling or not.

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

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

[Touch-packages] [Bug 1242112] Re: Shutdown/restart dialogue is not working if Cairo-Dock and its Launcher-API-Deamon are running or if another app is registered to LauncherEntry interface of Unity DB

[Rob]

Mathew,
very sorry but the status updates from you are not so clear to me:
- I encounter the same problem on my Trusty 14.04.3 with "cairo-dock" version 
3.4.0 (Cairo Dock autoloading on bootup, not possible to logout from Cairo)
- is there a fix for these versions (the delayed start suggested doesn't work, 
likely because my Cairo is starting on bootup and not during user 
session-start) ?
- do I need to upgrade to Ubuntu Utopic to have a fix included for Cairo ?

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

Title:
  Shutdown/restart dialogue is not working if Cairo-Dock and its
  Launcher-API-Deamon are running or if another app is registered to
  LauncherEntry interface of Unity DBus

Status in Cairo-Dock Core:
  Invalid
Status in DockbarX:
  Invalid
Status in Plank:
  Confirmed
Status in Unity:
  In Progress
Status in cairo-dock package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  In Progress
Status in cairo-dock source package in Trusty:
  Invalid
Status in unity source package in Trusty:
  Confirmed
Status in unity source package in Utopic:
  Won't Fix

Bug description:
  Unity's shutdown/restart dialogue is not working when another application is 
registered to LauncherEntry interface of Unity DBus.
  It seems we have this bug when Cairo-Dock (and its Launcher-API-Deamon), 
DockbarX or Plank are launched before Unity.

  [How to reproduce this bug]
  Simply launch this script at startup (launched before Unity). It will watch 
'com.canonical.Unity.LauncherEntry' bus interface: 
https://bazaar.launchpad.net/~cairo-dock-team/cairo-dock-plug-ins/plug-ins/view/head:/Dbus/data/cairo-dock-launcher-API-daemon.py

  [Original description]
  Using latest stable release (3.3.1). Just upgraded to Saucy Salamander in 
Ubuntu. When cairo dock is set to automatically run at boot up the options to 
shutdown/restart do not work from the top menu panel next to the clock. When 
run manually after boot the shutdown/restart works fine. The shutdown/restart 
options do work fine from cairo dock/terminal but just mess up the 
shutdown/restart from the top menu panel

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo-dock-core/+bug/1242112/+subscriptions

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

[Touch-packages] [Bug 1497611] Re: navigation through scopes very slow

[Daniel van Vugt]

Might help to fix bug 1494795 first.

** Tags added: performance

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

Title:
  navigation through scopes very slow

Status in unity-scopes-shell package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  I an using a Meizu MX4 with software version 15.04 (r4). Even though this is 
a powerfull phone moving between scopes is still laggy and slow also some auto 
refresh as you move to them. 
  I would like to suggest that auto refresh takes place in the background so 
all scopes are ready when you flick through them. 
  Also I wonder if a scope selection system would be a good idea so you could 
just direct to the scope you want and not have to scroll through many scopes 
before reaching the one you wish to use. 

  Note, The Today scope is improving slowly and the time for each item
  to show is reducing, but basically its still far too slow to be the
  main scope. If you refresh say the BBC news scope it completes in a 2
  seconds, the today scope still takes 10s (even after fixing the delay
  to show calls and texts). I understand people are working very hard to
  improve this key area.

  Thanks for your support

  Regards

  Dave H

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

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

[Touch-packages] [Bug 1201106] Re: horizontal swipe of Videos Carousel makes unity consume as much as 90% cpu

[Daniel van Vugt]

** Tags added: performance

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

Title:
  horizontal swipe of Videos Carousel makes unity consume as much as 90%
  cpu

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Image of: 20130714

  Videos Carousel is CPU hungary, horizontal swipe over the Videos
  Carousel in the videos scope makes unity consume ~90% CPU

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

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

[Touch-packages] [Bug 1500934] Re: The new AdaptivePageLayout should allow replacing primaryPage

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/aplReplacePrimaryPage

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

Title:
  The new AdaptivePageLayout should allow replacing primaryPage

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  The new AdaptivePageLayout does not allow replacing of the
  primaryPage.

  Simplest use case:
  primaryPage: isSignedIn ? masterPage : signInPage

  I've explained in more detail in the #sdk channel, it seems I have
  convinced two developers the limitation of not allowing to replace the
  primaryPage now seems arbitrary. Allowing to replace the primaryPage
  makes the component much more flexible.

  Naturally, replacing the primaryPage means all of the pages will be
  removed, as the primary page is like "tree root" in this situation.

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

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

[Touch-packages] [Bug 1501189] [NEW] Don't put 127.0.0.1 in resolvconf when port=0

[Alkis Georgopoulos]

Public bug reported:

The following function is defined in /etc/init.d/dnsmasq:

start_resolvconf()
{
# If interface "lo" is explicitly disabled in /etc/default/dnsmasq
# Then dnsmasq won't be providing local DNS, so don't add it to
# the resolvconf server set.
for interface in $DNSMASQ_EXCEPT
do
[ $interface = lo ] && return
done

if [ -x /sbin/resolvconf ] ; then
echo "nameserver 127.0.0.1" | /sbin/resolvconf -a lo.$NAME
fi
return 0
}

When someone puts port=0 in dnsmasq.conf, because e.g. he wants to use it only 
as a (proxy)DHCP/TFTP server,
127.0.0.1 is added to resolvconf, and DNS is broken because nothing listens 
there.

One workaround is to put DNSMASQ_EXCEPT=lo in /etc/default/dnsmasq.
But that doesn't make much sense, we don't want to exclude some interface, 
we're not running a DNS server at all.

So it would be nice if dnsmasq checked if port=0 is defined in its
configuration, and didn't add 127.0.0.1 to resolvconf then.

Sample implementation code, to be inserted before `if [ -x /sbin/resolvconf ]`:
grep -qr port=0 /etc/dnsmasq.d/ /etc/dnsmasq.conf && return

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


** Tags: patch

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

Title:
  Don't put 127.0.0.1 in resolvconf when port=0

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  The following function is defined in /etc/init.d/dnsmasq:

  start_resolvconf()
  {
  # If interface "lo" is explicitly disabled in /etc/default/dnsmasq
  # Then dnsmasq won't be providing local DNS, so don't add it to
  # the resolvconf server set.
  for interface in $DNSMASQ_EXCEPT
  do
  [ $interface = lo ] && return
  done

  if [ -x /sbin/resolvconf ] ; then
  echo "nameserver 127.0.0.1" | /sbin/resolvconf -a lo.$NAME
  fi
  return 0
  }

  When someone puts port=0 in dnsmasq.conf, because e.g. he wants to use it 
only as a (proxy)DHCP/TFTP server,
  127.0.0.1 is added to resolvconf, and DNS is broken because nothing listens 
there.

  One workaround is to put DNSMASQ_EXCEPT=lo in /etc/default/dnsmasq.
  But that doesn't make much sense, we don't want to exclude some interface, 
we're not running a DNS server at all.

  So it would be nice if dnsmasq checked if port=0 is defined in its
  configuration, and didn't add 127.0.0.1 to resolvconf then.

  Sample implementation code, to be inserted before `if [ -x /sbin/resolvconf 
]`:
  grep -qr port=0 /etc/dnsmasq.d/ /etc/dnsmasq.conf && return

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

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

[Touch-packages] [Bug 1500580] Re: [HP Compaq dc7700 Small Form Factor, Realtek ALC262, Black Mic, Front] Sound is distorted

[Raymond]

control.25 {
iface CARD
name 'Mic Jack'
value false
comment {
access read
type BOOLEAN
count 1
}
}
control.26 {
iface CARD
name 'Line Jack'
value false
comment {
access read
type BOOLEAN
count 1
}
}


ports:
analog-input: Analog Input (priority 1, latency offset 0 
usec, available: unknown)
properties:

analog-input-microphone: Microphone (priority 8700, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "audio-input-microphone"
analog-input-linein: Line In (priority 8100, latency offset 0 
usec, available: no)
properties:

active port: https://bugs.launchpad.net/bugs/1500580

Title:
  [HP Compaq dc7700 Small Form Factor, Realtek ALC262, Black Mic, Front]
  Sound is distorted

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The microphone inputs dont work, what sound i can get out of them is
  very over driven and cracks. same with the speaker output in the back
  of my computer,  I'm using version 14.04. I can get perfect sound out
  of the headphone jack though.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  Uname: Linux 3.16.0-031600rc4-generic i686
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clint-eastwood   1248 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Sep 28 12:17:10 2015
  InstallationDate: Installed on 2015-09-28 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Black Mic, Front
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Compaq dc7700 Small Form Factor, Realtek ALC262, Black Mic, Front] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786E1 v01.15
  dmi.board.name: 0A54h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786E1v01.15:bd08/05/2008:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.name: HP Compaq dc7700 Small Form Factor
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1323586] Re: oneconf crashes if one apt list file is unreadable

[Sebastien Bacher]

** Changed in: python-apt (Ubuntu)
   Status: New => Triaged

** Changed in: python-apt (Ubuntu)
   Importance: Undecided => High

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

Title:
  oneconf crashes if one apt list file is unreadable

Status in python-apt package in Ubuntu:
  Triaged

Bug description:
  oneconf-service will crash if one of the files in
  `/etc/apt/sources.list.d` is unreadable (for example because it has
  been created using sudo and umask 077).

  In my case this is the error message

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/oneconf/packagesethandler.py", 
line 63, in update
  newpkg_list = self.distro.compute_local_packagelist()
File "/usr/lib/python3/dist-packages/oneconf/distributor/Ubuntu.py", 
line 42, in compute_local_packagelist
  with apt.Cache() as apt_cache:
File "/usr/lib/python3/dist-packages/apt/cache.py", line 107, in 
__init__
  self.open(progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 155, in open
  self._list.read_main_list()
  SystemError: E:Opening /etc/apt/sources.list.d/tor.list - 
ifstream::ifstream (13: Permission denied)

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

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

[Touch-packages] [Bug 1500768] Re: python3.4.3 SRU break requests

[Didier Roche]

Ok, let me clarify some points here.

First, I pointed that change as it's the closest thing that changed in python 
3.4.3 which can have an impact on SNI, it may be something different which 
broke requests.
The invalid certificate tests is a test that is passing (this was to underline 
that I already had verfiy=true and checked that the SSL certificate check was 
done, as I was aware about the non check of it in python)

So, what is broken? I think the target is the SNI support with older request
1. Setup
- Install ubuntu-make from ubuntu-desktop/ubuntu-make ppa
- Have a proxy (squid.internal) for instance, filtering your network
- Export HTTPS_PROXY to point to your squid internal proxy

2. With python 3.4.0:
- Run "umake android" -> android-studio resolve, show the license page and 
install

3. With python 3.4.3 (current 14.04):
-  Run "umake android" -> you will get the hostname 'squid.internal' doesn't 
match either of '*.google.com', '*.android.com', '*.appengine.google.com', 
'*.cloud.google.com', '*.google-analytics.com', '*.google.ca', <…>' message 
(content depending on the allowed site from your proxy).

4. With python 3.4.3 + requests 2.7 backported in my ppa (didrocks/ppa):
- Run "umake android" -> android-studio resolve, show the license page and 
install

As you can see, Ubuntu Make code didn't change at all in any of those
tests, I think requests post 2.2.1 has something that made SNI work with
python 3.4.3.

As long as you have the right proxy config, I think this should simply fail:
import requests
requests.get('https://api.github.com/events')

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

Title:
  python3.4.3 SRU break requests

Status in python3.4 package in Ubuntu:
  Confirmed

Bug description:
  Sicne the upgade to python 3.4.3 on trusty, I'm getting this error when using 
a squid proxy:
  
https://jenkins.qa.ubuntu.com/view/All/job/udtc-trusty-tests/1946/label=ps-trusty-desktop-amd64-1,type=large/testReport/tests.large.test_android/AndroidSDKTests/test_default_android_sdk_install/

  The code is using python-requests, with verify=True for ssl connection
  (default). Some tests are testing that invalid certificates are
  rejected:  https://github.com/ubuntu/ubuntu-
  make/blob/master/umake/network/download_center.py#L129

  Rerunning the same code with previous trusty package (3.4.0~trusty1)
  doesn't show up this issue. It seems that SNI is broken for the trusty
  version of python3-requests with 3.4.3. (See the FAQ http://www
  .python-requests.org/en/latest/community/faq/ with "What are “hostname
  doesn’t match” errors?" and the stackoverflow question.

  I did run a test, grabbing requests 2.7 and backporting it to trusty
  (I needed to as well to take python3-urllib3 willy version).

  So, 3.4.3 has an incompatible change for existing projects and people
  with proxys are starting to see some breakage like in
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-make/+bug/1499890.

  Can we get it fix somehow, reverting the incompatible change breaking
  SNI (I wonder if this is "Changed in version 3.4.3: This class now
  performs all the necessary certificate and hostname checks by default.
  To revert to the previous, unverified, behavior
  ssl._create_unverified_context() can be passed to the context
  parameter." in https://docs.python.org/3/library/http.client.html or
  something else) so that existing code can either get a new compatible
  python-requests or avoid incompatible changes in python 3.4.3?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1500768/+subscriptions

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

[Touch-packages] [Bug 1498775] Re: Greeter auth doesn't unlock unity lockscreen

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.16.3-0ubuntu1

---
lightdm (1.16.3-0ubuntu1) wily; urgency=medium

  * New upstream release:
- Fix compile failing without libinput
- Fix compile failing without Vala
  * debian/lightdm.lightdm-autologin.pam:
  * debian/lightdm.pam:
  * debian/rules:
- Disable libaudit support for now - Unity is not unlocking with these
  changes (LP: #1498775)

 -- Robert Ancell   Wed, 30 Sep 2015
09:30:57 +1300

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

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

Title:
  Greeter auth doesn't unlock unity lockscreen

Status in Unity:
  Confirmed
Status in lightdm package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Using current wily

  - use indicator-session to go to the greeter (e.g pick another user in the 
list)
  - select your normal user back
  - enter your password

  you should go back to an unlocked session but it's still locked...

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

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

[Touch-packages] [Bug 1438465] Re: It's possible to put a window under the top panel

[Daniel van Vugt]

You've always been able to (and should be able to) drag a window under
the Unity7 panel. And you can drag it back out again, just using
Alt+drag. So all that's missing in Unity8 really is Alt+drag and also
correct placement so as to avoid accidental placement under the panel.

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

Title:
  It's possible to put a window under the top panel

Status in canonical-pocket-desktop:
  New
Status in QtMir:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  so many times,when i drag the window to the top, the max-min-button
  will be overlaied by panel,so i can not drag this window back and i
  can not see these buttons

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1438465/+subscriptions

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

[Touch-packages] [Bug 1495554] Re: AbstractButton 1.3 pressAndHold breaks inside a Loader

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-ui-toolkit (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/1495554

Title:
  AbstractButton 1.3 pressAndHold breaks inside a Loader

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

Bug description:
  The attached file shows that AbstractButton pressAndHold signal does
  not trigger if inside a Loader with Ubuntu Components 1.3

  It works fine with Ubuntu Components 1.2 and with MouseArea.

  This blocks unity8 moving to 1.3 since breaks the Dash.

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

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

[Touch-packages] [Bug 1349975] Re: [system settings] OAuth based plug-ins appear to crash under poor network connectivity

[Alberto Mardegan]

** Also affects: signon-plugin-oauth2 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: signon-plugin-oauth2 (Ubuntu)
   Status: New => In Progress

** Changed in: signon-plugin-oauth2 (Ubuntu)
 Assignee: (unassigned) => Alberto Mardegan (mardy)

** Changed in: signon-plugin-oauth2 (Ubuntu)
   Importance: Undecided => High

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

Title:
  [system settings] OAuth based plug-ins appear to crash under poor
  network connectivity

Status in Online Accounts: Account plugins:
  Triaged
Status in Ubuntu UX:
  Fix Committed
Status in webapps-sprint:
  Triaged
Status in account-plugins package in Ubuntu:
  New
Status in signon-plugin-oauth2 package in Ubuntu:
  In Progress

Bug description:
  When going to the Accounts page of System Settings, and attempting to
  add a Google/Twitter/etc… OAuth based account on my Nexus 4, the plug-
  ins are appearing to crash, and I get sent back to the accounts list.
  This appears to be due to poor network connectivity, as I'm on wifi,
  but the AP is at the other end of my house, resulting in poor
  connection which often drops. If I move the phone close to the AP, the
  pages then load and do not seem to crash, as the connectivity is
  greatly improved.

  Instead of crashing/exiting/whatever is happening, I think these plug-
  ins need to show an error or something, to tell the user something is
  wrong. Otherwise, it simply appears the software is very crashy.

  : "If there is
  a networking or HTTP error in loading the page, or in submitting the
  form, the contents of the Web frame should be replaced by the text
  “This service is not available right now. Try again later.” and a “Try
  Again” button."

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1349975/+subscriptions

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

[Touch-packages] [Bug 1500467] Re: Aggregator reloading needs rethinking

[Yuan-Chen Cheng]

** Changed in: today-scope
   Importance: Undecided => High

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

Title:
  Aggregator reloading needs rethinking

Status in Today Scope:
  Opinion
Status in unity-scopes-api package in Ubuntu:
  Confirmed

Bug description:
  The Today scope is basically a place-holder for 'sub scopes'. The
  today scope has three problems which cannot both be resolved under the
  current system. These are:

  1) The scope is reloading at times I do not want it to
  2) The scope has not got the latest data (eg sms message) when I want it
  3) When the Today scope reloads, not only is it slow (BQ 4.5) but it also 
takes down the entire scope system with it for a few seconds.

  The problem is that when the Today scope refreshes/reloads, it reloads
  all sub-scopes. However, Weather and Today do not need to be reloaded
  for 24 hours at a time (maybe weather is an exception here).

  I think the Today scope should be a 'dumb placeholder' and the sub-
  scopes should be responsible for calling for refresh. The parent
  (Today scope) could then refresh an _individual_ sub-scope using ajax
  or similar. This would improve all three issues above but challenge
  some other fundamentals, eg:

  4) Scopes should be stateless (according to current thinking)

  I would challenge this also, as it would solve the issue where the My
  Music scope shows the user their music sorted by artist, even after
  they have changed it to album sorting.

  The Today scope has come a long way since I got the phone in April and
  I now have it enable since the latest update a few weeks ago. But the
  issues I describe above are 'as expected' behaviour and I think this
  itself is the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1500467/+subscriptions

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

[Touch-packages] [Bug 1497828] Re: Clients using swap interval zero in Unity8 freeze occasionally. Need to interact with the shell to unfreeze them.

[Daniel van Vugt]

When the freeze occurs, MIR_CLIENT_PERF_REPORT=log in the affected
client shows the client is then seeing only two buffers despite Mir
being configured for triple buffers. So it would appear the problem
might be QtMir failing to release the one that's on screen.

** Summary changed:

- Clients in Unity8 freeze occasionally. Need to interact with the window or 
launcher to unfreeze them.
+ Clients using swap interval zero in Unity8 freeze occasionally. Need to 
interact with the shell to unfreeze them.

** Description changed:

- Clients in Unity8 freeze occasionally. Need to interact with the window
- or launcher to unfreeze them.
+ Clients using swap interval zero in Unity8 freeze regularly. Need to
+ interact with the shell to unfreeze them.
  
  Test case (on Unity8 wily desktop):
+ $ glmark2-mir -b :title=--desktop_file_hint=unity8
  
- $ glmark2-mir -b :title=--desktop_file_hint=unity8
+ Test case (on a phone):
+ $ mir_demo_client_target -n--desktop_file_hint=unity8

** Summary changed:

- Clients using swap interval zero in Unity8 freeze occasionally. Need to 
interact with the shell to unfreeze them.
+ Clients using swap interval zero in Unity8 freeze regularly. Need to interact 
with the shell to unfreeze them.

** Tags added: performance

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

Title:
  Clients using swap interval zero in Unity8 freeze regularly. Need to
  interact with the shell to unfreeze them.

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

Bug description:
  Clients using swap interval zero in Unity8 freeze regularly. Need to
  interact with the shell to unfreeze them.

  Test case (on Unity8 wily desktop):
  $ glmark2-mir -b :title=--desktop_file_hint=unity8

  Test case (on a phone):
  $ mir_demo_client_target -n--desktop_file_hint=unity8

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

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

[Touch-packages] [Bug 1484527] Re: package python-apt 0.8.3ubuntu7.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 139

[Julian Andres Klode]

Not sure what happened, but definitely not python-apt's problem.

** Changed in: python-apt (Ubuntu)
   Status: New => Invalid

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

Title:
  package python-apt 0.8.3ubuntu7.3 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 139

Status in python-apt package in Ubuntu:
  Invalid

Bug description:
  i was updating and suddenly stop with cresh error and now its not
  working

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: python-apt 0.8.3ubuntu7.3
  ProcVersionSignature: Ubuntu 3.2.0-88.126-generic 3.2.69
  Uname: Linux 3.2.0-88-generic x86_64
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  Date: Thu Aug 13 15:51:44 2015
  ErrorMessage: subprocess new pre-removal script returned error exit status 139
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  SourcePackage: python-apt
  Title: package python-apt 0.8.3ubuntu7.3 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 139
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1501310] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

[Stephen]

/home/ubuntu/nzos/volumes/1.0.0/common/shared
/var/lib/lxc/0002/rootfs/nzos/./__shared__ none ro,bind 0 0

This line is giving the same error. With 1.0.7-0ubuntu0.6 installed.

lxc-start: utils.c: ensure_not_symlink: 1398 Mount onto /usr/lib/x86_64
-linux-gnu/lxc//nzos/./__shared__ resulted in /usr/lib/x86_64-linux-
gnu/lxc/nzos/__shared__

lxc-start: utils.c: safe_mount: 1423 Mount of 
'/home/ubuntu/nzos/volumes/1.0.0/common/shared' onto 
'/usr/lib/x86_64-linux-gnu/lxc//nzos/./__shared__' was onto a symlink!
lxc-start: conf.c: mount_entry: 2051 No such file or directory - failed to 
mount '/home/ubuntu/nzos/volumes/1.0.0/common/shared' on 
'/usr/lib/x86_64-linux-gnu/lxc//nzos/./__shared__'
lxc-start: conf.c: lxc_setup: 4160 failed to setup the mounts for '0002'
lxc-start: start.c: do_start: 688 failed to setup the container
lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2
lxc-start: start.c: __lxc_start: 1080 failed to spawn '0002'
lxc-start: lxc_start.c: main: 342 The container failed to start.
lxc-start: lxc_start.c: main: 346 Additional information can be obtained by 
setting the --logfile and --logpriority options.

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

Title:
  Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  I got this entry in the config file to mount a folder on the hosts
  filesystem:

  lxc.mount.entry=/media/array/backup/blixten
  /var/lib/lxc/blixten/rootfs/var/backup none bind 0 0

  this is the lxc root: lxc.rootfs = /var/lib/lxc/blixten/rootfs

  Nither /media/array/backup/blixten or
  /var/lib/lxc/blixten/rootfs/var/backup is a symlink.

  Error when starting the container:

  root@mail:/media# lxc-start -n blixten
  lxc-start: utils.c: ensure_not_symlink: 1384 Mount onto 
/usr/lib/x86_64-linux-gnu/lxc//var/backup resulted in 
/usr/lib/x86_64-linux-gnu/lxc/var/backup

  lxc-start: utils.c: safe_mount: 1409 Mount of '/media/array/backup/blixten' 
onto '/usr/lib/x86_64-linux-gnu/lxc//var/backup' was onto a symlink!
  lxc-start: conf.c: mount_entry: 2051 Invalid argument - failed to mount 
'/media/array/backup/blixten' on '/usr/lib/x86_64-linux-gnu/lxc//var/backup'
  lxc-start: conf.c: lxc_setup: 4165 failed to setup the mount entries for 
'blixten'
  lxc-start: start.c: do_start: 688 failed to setup the container
  lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2
  lxc-start: start.c: __lxc_start: 1080 failed to spawn 'blixten'
  lxc-start: lxc_start.c: main: 342 The container failed to start.
  lxc-start: lxc_start.c: main: 346 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  
  I had to revert to the older version of LXC to get the containers running 
again.

  Best regards
  Tobias

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

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

[Touch-packages] [Bug 1501310] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

[Stephen]

In reference to above comment - should I open a new bug?

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

Title:
  Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  I got this entry in the config file to mount a folder on the hosts
  filesystem:

  lxc.mount.entry=/media/array/backup/blixten
  /var/lib/lxc/blixten/rootfs/var/backup none bind 0 0

  this is the lxc root: lxc.rootfs = /var/lib/lxc/blixten/rootfs

  Nither /media/array/backup/blixten or
  /var/lib/lxc/blixten/rootfs/var/backup is a symlink.

  Error when starting the container:

  root@mail:/media# lxc-start -n blixten
  lxc-start: utils.c: ensure_not_symlink: 1384 Mount onto 
/usr/lib/x86_64-linux-gnu/lxc//var/backup resulted in 
/usr/lib/x86_64-linux-gnu/lxc/var/backup

  lxc-start: utils.c: safe_mount: 1409 Mount of '/media/array/backup/blixten' 
onto '/usr/lib/x86_64-linux-gnu/lxc//var/backup' was onto a symlink!
  lxc-start: conf.c: mount_entry: 2051 Invalid argument - failed to mount 
'/media/array/backup/blixten' on '/usr/lib/x86_64-linux-gnu/lxc//var/backup'
  lxc-start: conf.c: lxc_setup: 4165 failed to setup the mount entries for 
'blixten'
  lxc-start: start.c: do_start: 688 failed to setup the container
  lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2
  lxc-start: start.c: __lxc_start: 1080 failed to spawn 'blixten'
  lxc-start: lxc_start.c: main: 342 The container failed to start.
  lxc-start: lxc_start.c: main: 346 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  
  I had to revert to the older version of LXC to get the containers running 
again.

  Best regards
  Tobias

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

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

[Touch-packages] [Bug 1500228] Re: When scrolling back up some of the bottom comes up as a sort of sleeve

[Egmont Koblinger]

Vte used to contain such drawing bugs, but we fixed all the known ones
about 1.5 years ago and I haven't seen any display corruption like yours
since then; nor have seen any other user complaining (I keep an eye on
official gnome-terminal bugzilla, Ubuntu, Debian and Red Hat
bugtracker).

I use Wily beta and cannot reproduce your issue.

This gives me a hunch that it's probably something wrong with Gnome3
staging, or perhaps your X driver or something like that.

But of course it can be a gnome-terminal/vte bug which only occurs on
your computer.

Reproducing in a VM with Wily: if you can reproduce then that's
definitely helpful; but if you can't then that means nothing: it still
could be buggy with Wily directly on your computer.

Are you planning to update any time soon? My recommendation is to wait
until you upgrade and use mainstream Wily (no Gnome3 staging) and still
can reproduce it there. If it's still an issue I'd be happy to start
debugging it with you, but I would first like to exclude the possibility
that something in Gnome3 staging is the culprit.

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

Title:
  When scrolling back up some of the bottom comes up as a sort of sleeve

Status in gnome-terminal package in Ubuntu:
  New
Status in less package in Ubuntu:
  New

Bug description:
  I have recently noticed that when viewing a manpage in gnome-terminal
  that if scrolling down, when I scroll back up again some of the bottom
  part of the page comes up too sort of like a sleeve. I have attached
  some example screenshots, so I ran 'man dpkg' and this is what it
  looked like initially dpkg_man_top1.png, but when I scrolled down to
  the bottom of the page and then back up again to the top, the top
  looked somewhat different as you can see: dpkg_man_top2.png. Now, it
  wouldn't matter where I had scrolled down to, nor where I had gone up
  to, the effect witnessed would have been the same.

  ---

  OS Information:

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 15.04
  Release:  15.04
  Codename: vivid
  Flavour: GNOME
  GNOME Version: 3.16

  Package Information:

  manpages:
    Installed: 3.74-1ubuntu1
    Candidate: 3.74-1ubuntu1
    Version table:
   *** 3.74-1ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  less:
Installed: 458-3
Candidate: 458-3
Version table:
   *** 458-3 0
  500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  gnome-terminal:
Installed: 3.16.2-1ubuntu1~vivid1
Candidate: 3.16.2-1ubuntu1~vivid1
Version table:
   *** 3.16.2-1ubuntu1~vivid1 0
  500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu/ 
vivid/main amd64 Packages
  100 /var/lib/dpkg/status
   3.14.2-0ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
   3.12.3-0ubuntu1~utopic2 0
  500 http://ppa.launchpad.net/gnome3-team/gnome3/ubuntu/ 
vivid/main amd64 Packages

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

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

[Touch-packages] [Bug 1500242] Re: Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

[Uranicus]

Simon, thanks for the answer. How can I find out if I am still on OTA5?
I expect to be on OTA6 since I have applied all updates. What can I do
more than:

go to "Settings"
select "Updates"
an the phone tells me "Software is up-to-date"

(I am using the German version of the phone, so my translation might be
not exactly matching with the current English terms)

Matthias

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

Title:
  Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old 
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi 
car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth 
device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that 
pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) 
but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 
model) where the blue tooth pairing etc. works great (except some bugs which 
are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

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

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

[Touch-packages] [Bug 1501491] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.6 on trusty

[Serge Hallyn]

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

Title:
  Unable to start containers after upgrade to 1.0.7-0ubuntu0.6 on trusty

Status in lxc package in Ubuntu:
  New

Bug description:
  A partial fix was made for 1501310 - this case still fails.

  /home/ubuntu/nzos/volumes/1.0.0/common/shared
  /var/lib/lxc/0002/rootfs/nzos/./__shared__ none ro,bind 0 0

  This line is giving the same error. With 1.0.7-0ubuntu0.6 installed.

  lxc-start: utils.c: ensure_not_symlink: 1398 Mount onto
  /usr/lib/x86_64-linux-gnu/lxc//nzos/./__shared__ resulted in
  /usr/lib/x86_64-linux-gnu/lxc/nzos/__shared__

  lxc-start: utils.c: safe_mount: 1423 Mount of 
'/home/ubuntu/nzos/volumes/1.0.0/common/shared' onto 
'/usr/lib/x86_64-linux-gnu/lxc//nzos/./__shared__' was onto a symlink!
  lxc-start: conf.c: mount_entry: 2051 No such file or directory - failed to 
mount '/home/ubuntu/nzos/volumes/1.0.0/common/shared' on 
'/usr/lib/x86_64-linux-gnu/lxc//nzos/./__shared__'
  lxc-start: conf.c: lxc_setup: 4160 failed to setup the mounts for '0002'
  lxc-start: start.c: do_start: 688 failed to setup the container
  lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2
  lxc-start: start.c: __lxc_start: 1080 failed to spawn '0002'
  lxc-start: lxc_start.c: main: 342 The container failed to start.
  lxc-start: lxc_start.c: main: 346 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04
  Codename: trusty

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

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

[Touch-packages] [Bug 1501491] [NEW] Unable to start containers after upgrade to 1.0.7-0ubuntu0.6 on trusty

[Stephen]

Public bug reported:

A partial fix was made for 1501310 - this case still fails.

/home/ubuntu/nzos/volumes/1.0.0/common/shared
/var/lib/lxc/0002/rootfs/nzos/./__shared__ none ro,bind 0 0

This line is giving the same error. With 1.0.7-0ubuntu0.6 installed.

lxc-start: utils.c: ensure_not_symlink: 1398 Mount onto /usr/lib/x86_64
-linux-gnu/lxc//nzos/./__shared__ resulted in /usr/lib/x86_64-linux-
gnu/lxc/nzos/__shared__

lxc-start: utils.c: safe_mount: 1423 Mount of 
'/home/ubuntu/nzos/volumes/1.0.0/common/shared' onto 
'/usr/lib/x86_64-linux-gnu/lxc//nzos/./__shared__' was onto a symlink!
lxc-start: conf.c: mount_entry: 2051 No such file or directory - failed to 
mount '/home/ubuntu/nzos/volumes/1.0.0/common/shared' on 
'/usr/lib/x86_64-linux-gnu/lxc//nzos/./__shared__'
lxc-start: conf.c: lxc_setup: 4160 failed to setup the mounts for '0002'
lxc-start: start.c: do_start: 688 failed to setup the container
lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2
lxc-start: start.c: __lxc_start: 1080 failed to spawn '0002'
lxc-start: lxc_start.c: main: 342 The container failed to start.
lxc-start: lxc_start.c: main: 346 Additional information can be obtained by 
setting the --logfile and --logpriority options.

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.2 LTS
Release:14.04
Codename:   trusty

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

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

Title:
  Unable to start containers after upgrade to 1.0.7-0ubuntu0.6 on trusty

Status in lxc package in Ubuntu:
  New

Bug description:
  A partial fix was made for 1501310 - this case still fails.

  /home/ubuntu/nzos/volumes/1.0.0/common/shared
  /var/lib/lxc/0002/rootfs/nzos/./__shared__ none ro,bind 0 0

  This line is giving the same error. With 1.0.7-0ubuntu0.6 installed.

  lxc-start: utils.c: ensure_not_symlink: 1398 Mount onto
  /usr/lib/x86_64-linux-gnu/lxc//nzos/./__shared__ resulted in
  /usr/lib/x86_64-linux-gnu/lxc/nzos/__shared__

  lxc-start: utils.c: safe_mount: 1423 Mount of 
'/home/ubuntu/nzos/volumes/1.0.0/common/shared' onto 
'/usr/lib/x86_64-linux-gnu/lxc//nzos/./__shared__' was onto a symlink!
  lxc-start: conf.c: mount_entry: 2051 No such file or directory - failed to 
mount '/home/ubuntu/nzos/volumes/1.0.0/common/shared' on 
'/usr/lib/x86_64-linux-gnu/lxc//nzos/./__shared__'
  lxc-start: conf.c: lxc_setup: 4160 failed to setup the mounts for '0002'
  lxc-start: start.c: do_start: 688 failed to setup the container
  lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2
  lxc-start: start.c: __lxc_start: 1080 failed to spawn '0002'
  lxc-start: lxc_start.c: main: 342 The container failed to start.
  lxc-start: lxc_start.c: main: 346 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04
  Codename: trusty

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

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

[Touch-packages] [Bug 1501310] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

[Stephen]

I cannot simply remove those characters as this is fstab generated by
our deployment S/W.  I would think that a patch (assuming last digit in
a version is a patch level)  should not break existing code.

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

Title:
  Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  I got this entry in the config file to mount a folder on the hosts
  filesystem:

  lxc.mount.entry=/media/array/backup/blixten
  /var/lib/lxc/blixten/rootfs/var/backup none bind 0 0

  this is the lxc root: lxc.rootfs = /var/lib/lxc/blixten/rootfs

  Nither /media/array/backup/blixten or
  /var/lib/lxc/blixten/rootfs/var/backup is a symlink.

  Error when starting the container:

  root@mail:/media# lxc-start -n blixten
  lxc-start: utils.c: ensure_not_symlink: 1384 Mount onto 
/usr/lib/x86_64-linux-gnu/lxc//var/backup resulted in 
/usr/lib/x86_64-linux-gnu/lxc/var/backup

  lxc-start: utils.c: safe_mount: 1409 Mount of '/media/array/backup/blixten' 
onto '/usr/lib/x86_64-linux-gnu/lxc//var/backup' was onto a symlink!
  lxc-start: conf.c: mount_entry: 2051 Invalid argument - failed to mount 
'/media/array/backup/blixten' on '/usr/lib/x86_64-linux-gnu/lxc//var/backup'
  lxc-start: conf.c: lxc_setup: 4165 failed to setup the mount entries for 
'blixten'
  lxc-start: start.c: do_start: 688 failed to setup the container
  lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2
  lxc-start: start.c: __lxc_start: 1080 failed to spawn 'blixten'
  lxc-start: lxc_start.c: main: 342 The container failed to start.
  lxc-start: lxc_start.c: main: 346 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  
  I had to revert to the older version of LXC to get the containers running 
again.

  Best regards
  Tobias

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

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

[Touch-packages] [Bug 1310104] Re: No way to trigger fingerprint authentication on lock screen

[Jens Bo]

I have the same issue. Not a solution, but a good work around for me was
to turn on the onscreen keyboard in the universal access settings.

This leads to a (fallback?) old school login screen which has no problem
with the finger print reader.

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

Title:
  No way to trigger fingerprint authentication on lock screen

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  With fprintd/libpam_fprintd installed, the user can in all places 
authenticate via the fingerprint reader. (Command line, login screen, light 
locker screen). However, light locker does not interact well with fingerprint 
authentication:
  Immediately after locking the session, the user can unlock via fingerprint. 
But once the fingerprint authentication times out, light locker waits for a 
password to be typed, and the user cannot re-initiate fingerprint 
authentication. The usual way of pressing ESC does not have effect. There even 
is a state, where light locker does not accept fingerprint nor password 
authentication -- the user is left without any possibility to unlock the 
screen. This is not acceptable.
  Please correct light locker's behavior with respect to libpam-fprintd 
authentication.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: light-locker (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 19 23:21:11 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-12-20 (484 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: light-locker
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (1 days ago)

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

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

[Touch-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp

[Yura]

sorry for the typo,  confirm fix from post #5, ubuntu 15.04

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Confirmed
Status in pulseaudio source package in Vivid:
  Confirmed

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

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

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

[Touch-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp

[Yura]

confirm fix from post #17, ubuntu 15.04

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Confirmed
Status in pulseaudio source package in Vivid:
  Confirmed

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

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

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

[Touch-packages] [Bug 1386553] Re: AMR audio codec not supported

[Pat McGowan]

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

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

Title:
  AMR audio codec not supported

Status in Canonical System Image:
  Fix Committed
Status in gst-libav1.0 package in Ubuntu:
  Invalid
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in ubuntu-touch-meta package in Ubuntu:
  In Progress
Status in ubuntu-touch-meta package in Ubuntu RTM:
  Fix Released

Bug description:
  AMR audio codec is not supported currently. This is relevant for MMS
  videos, as AMR is the default for audio.

  With gstreamer debug env var GST_DEBUG=*:3 I see:

  0:00:39.390824849 23581 0xb3f053b0 WARN uridecodebin
  gsturidecodebin.c:939:unknown_type_cb: warning: No
  decoder available for type 'audio/AMR,
  codec_data=(buffer)001164616d726170706c010085, rate=(int)8000,
  channels

  $ system-image-cli -i
  current build number: 131
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-10-27 15:32:17
  version version: 131
  version ubuntu: 20141027.1
  version device: 20141015-32e0f27
  version custom: 1413941794

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

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

[Touch-packages] [Bug 1501487] [NEW] Pictures can't be cancelled

[Peter Pan]

Public bug reported:

MEIZU MX4, Ubuntu 15.04 (r4), last update 08/30/15


Trying to cancel a picture from the gallery I reach the popup window
with YES and NO button (YES button is marked red) but a click on the YES
button doesn't have any effect - it is ignored. Only the NO button does
close the dialog window.

When marking the picture in the gallery and choosing "delete" from the
menu in the upper right corner, resualt is exactly the same.

** Affects: gallery-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Pictures can't be cancelled

Status in gallery-app package in Ubuntu:
  New

Bug description:
  MEIZU MX4, Ubuntu 15.04 (r4), last update 08/30/15


  Trying to cancel a picture from the gallery I reach the popup window
  with YES and NO button (YES button is marked red) but a click on the
  YES button doesn't have any effect - it is ignored. Only the NO button
  does close the dialog window.

  When marking the picture in the gallery and choosing "delete" from the
  menu in the upper right corner, resualt is exactly the same.

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

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

[Touch-packages] [Bug 1499675] Re: lightdm doesn´t ask for password

[Robert Ancell]

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

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

Title:
  lightdm doesn´t ask for password

Status in lightdm package in Ubuntu:
  Invalid

Bug description:
  For a long time (from previous versions) on my system I had only one
  user - Mark - with admin privileges, a password set and auto-login at
  startup. At boot I went directly to the Mark desktop.

  Now I add another user for my daughter - Carol - normal user but with
  no password. I switch off auto-login for both users. At startup I see
  the lightdm screen with users Carol and Mark, I can access Carol
  correctly by pressing "Log In" but when I choose Mark I am not asked
  for the password, I see the "Log In" button and enter directly in the
  Mark desktop without being asked for a password.

  I can also access Mark directly from the Carol account using the drop-
  down in the top left, again without being asked for a password.

  When I look in "user accounts" I see Carol with "no password" and Mark
  with a password set, neither have autologin set.

  I have looked at all the lightdm config files and can´t see anything
  obvious.

  I need to protect the Mark account from my growing children. I´d
  appreciate your help.

  Regards,

  Mark Rennie

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.5-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Uname: Linux 3.13.0-63-generic i686
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Sep 25 12:03:47 2015
  InstallationDate: Installed on 2011-07-18 (1529 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=unity-greeter
   user-session=ubuntu
   allow-guest=false
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-08-14 (407 days ago)

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

-- 
Mailing list: https://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 1501310] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

[Serge Hallyn]

Quoting Stephen (sajames1...@gmail.com):
> /home/ubuntu/nzos/volumes/1.0.0/common/shared
> /var/lib/lxc/0002/rootfs/nzos/./__shared__ none ro,bind 0 0

Plesae get rid of the "./" in the path.

We could check for this in the paths, but I start to become
concerned at that point that we're begging for parsing errors
to allow new security bugs to come through.

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

Title:
  Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  I got this entry in the config file to mount a folder on the hosts
  filesystem:

  lxc.mount.entry=/media/array/backup/blixten
  /var/lib/lxc/blixten/rootfs/var/backup none bind 0 0

  this is the lxc root: lxc.rootfs = /var/lib/lxc/blixten/rootfs

  Nither /media/array/backup/blixten or
  /var/lib/lxc/blixten/rootfs/var/backup is a symlink.

  Error when starting the container:

  root@mail:/media# lxc-start -n blixten
  lxc-start: utils.c: ensure_not_symlink: 1384 Mount onto 
/usr/lib/x86_64-linux-gnu/lxc//var/backup resulted in 
/usr/lib/x86_64-linux-gnu/lxc/var/backup

  lxc-start: utils.c: safe_mount: 1409 Mount of '/media/array/backup/blixten' 
onto '/usr/lib/x86_64-linux-gnu/lxc//var/backup' was onto a symlink!
  lxc-start: conf.c: mount_entry: 2051 Invalid argument - failed to mount 
'/media/array/backup/blixten' on '/usr/lib/x86_64-linux-gnu/lxc//var/backup'
  lxc-start: conf.c: lxc_setup: 4165 failed to setup the mount entries for 
'blixten'
  lxc-start: start.c: do_start: 688 failed to setup the container
  lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2
  lxc-start: start.c: __lxc_start: 1080 failed to spawn 'blixten'
  lxc-start: lxc_start.c: main: 342 The container failed to start.
  lxc-start: lxc_start.c: main: 346 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  
  I had to revert to the older version of LXC to get the containers running 
again.

  Best regards
  Tobias

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

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

[Touch-packages] [Bug 1501310] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

[Stephen]

I opened 1501491

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

Title:
  Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  I got this entry in the config file to mount a folder on the hosts
  filesystem:

  lxc.mount.entry=/media/array/backup/blixten
  /var/lib/lxc/blixten/rootfs/var/backup none bind 0 0

  this is the lxc root: lxc.rootfs = /var/lib/lxc/blixten/rootfs

  Nither /media/array/backup/blixten or
  /var/lib/lxc/blixten/rootfs/var/backup is a symlink.

  Error when starting the container:

  root@mail:/media# lxc-start -n blixten
  lxc-start: utils.c: ensure_not_symlink: 1384 Mount onto 
/usr/lib/x86_64-linux-gnu/lxc//var/backup resulted in 
/usr/lib/x86_64-linux-gnu/lxc/var/backup

  lxc-start: utils.c: safe_mount: 1409 Mount of '/media/array/backup/blixten' 
onto '/usr/lib/x86_64-linux-gnu/lxc//var/backup' was onto a symlink!
  lxc-start: conf.c: mount_entry: 2051 Invalid argument - failed to mount 
'/media/array/backup/blixten' on '/usr/lib/x86_64-linux-gnu/lxc//var/backup'
  lxc-start: conf.c: lxc_setup: 4165 failed to setup the mount entries for 
'blixten'
  lxc-start: start.c: do_start: 688 failed to setup the container
  lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2
  lxc-start: start.c: __lxc_start: 1080 failed to spawn 'blixten'
  lxc-start: lxc_start.c: main: 342 The container failed to start.
  lxc-start: lxc_start.c: main: 346 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  
  I had to revert to the older version of LXC to get the containers running 
again.

  Best regards
  Tobias

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

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

[Touch-packages] [Bug 1499174] Re: AdaptivePageLayout should load URL pages fully asynchronous

[Pat McGowan]

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

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

Title:
  AdaptivePageLayout should load URL pages fully asynchronous

Status in Canonical System Image:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  When a page is specified as URL to either of the page addition
  functions, AdaptivePageLayout creates the Component synchronously.
  This causes delays and makes UI unresponsive during the time the page
  document is compiled. Therefore pages specified as URL should also be
  loaded asynchronously.

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

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

[Touch-packages] [Bug 1424059] Re: libosmesa6 conflicts with libglapi-mesa-lts-*

[Mathew Hodson]

** Description changed:

- [Description]
- libosmesa6 10.1.3-0ubuntu0.3 amd64 can't be installed because it depends on 
libglapi-mesa (= 10.1.3-0ubuntu0.3), but libglapi-mesa-lts-utopic 
10.3.2-0ubuntu1~trusty2 amd64 is '10.3.2-0ubuntu1' not '10.1.3-0ubuntu0.3'.
+ [Impact]
+ 
+ libosmesa6 10.1.3-0ubuntu0.3 amd64 can't be installed because it depends
+ on libglapi-mesa (= 10.1.3-0ubuntu0.3), but libglapi-mesa-lts-utopic
+ 10.3.2-0ubuntu1~trusty2 amd64 is '10.3.2-0ubuntu1' not
+ '10.1.3-0ubuntu0.3'.
+ 
+ A possible solution is to include Utopic's libosmesa(-dev) in the LTS
+ enablement stack so versions match.
  
  [Test Case]
+ 
  >sudo aptitude install libosmesa6
  The following NEW packages will be installed:
    libglapi-mesa{a} libosmesa6
  0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1,009 kB of archives. After unpacking 3,682 kB will be used.
  The following packages have unmet dependencies:
   xserver-xorg-lts-utopic : Conflicts: libglapi-mesa (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
   libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is 
to be installed.
  
- [Possible solution]
- Include utopic's libosmesa(-dev) in the LTS enablement stack, so versions 
match.
+ Also check that reverse dependencies install and continue to work such
+ as libosmesa6-dev, desmume, crossover, and wine.
  
- [Reverse dependencies]
- libosmesa6-dev
- desmume
- crossover
- wine recommends libosmesa6
- ...
+ [Other Info]
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libglapi-mesa-lts-utopic 10.3.2-0ubuntu1~trusty2
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 20 15:45:52 2015
  Dependencies:
   gcc-4.9-base 4.9.1-0ubuntu1
   libc6 2.19-0ubuntu6.5
   libgcc1 1:4.9.1-0ubuntu1
   multiarch-support 2.19-0ubuntu6.5
  InstallationDate: Installed on 2015-02-08 (12 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150203.2)
  SourcePackage: mesa-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

** Tags removed: regression-release upgrade-software-version

** No longer affects: mesa (Ubuntu)

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

Title:
  libosmesa6 conflicts with libglapi-mesa-lts-*

Status in mesa source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  libosmesa6 10.1.3-0ubuntu0.3 amd64 can't be installed because it
  depends on libglapi-mesa (= 10.1.3-0ubuntu0.3), but libglapi-mesa-lts-
  utopic 10.3.2-0ubuntu1~trusty2 amd64 is '10.3.2-0ubuntu1' not
  '10.1.3-0ubuntu0.3'.

  A possible solution is to include Utopic's libosmesa(-dev) in the LTS
  enablement stack so versions match.

  [Test Case]

  >sudo aptitude install libosmesa6
  The following NEW packages will be installed:
    libglapi-mesa{a} libosmesa6
  0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1,009 kB of archives. After unpacking 3,682 kB will be used.
  The following packages have unmet dependencies:
   xserver-xorg-lts-utopic : Conflicts: libglapi-mesa (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
   libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is 
to be installed.

  Also check that reverse dependencies install and continue to work such
  as libosmesa6-dev, desmume, crossover, and wine.

  [Other Info]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libglapi-mesa-lts-utopic 10.3.2-0ubuntu1~trusty2
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 20 15:45:52 2015
  Dependencies:
   gcc-4.9-base 4.9.1-0ubuntu1
   libc6 2.19-0ubuntu6.5
   libgcc1 1:4.9.1-0ubuntu1
   multiarch-support 2.19-0ubuntu6.5
  InstallationDate: Installed on 2015-02-08 (12 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150203.2)
  SourcePackage: mesa-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1501383] Re: App scope is blank and unresponsive when logging in desktop mode

[kevin gunn]

** Changed in: unity8 (Ubuntu)
   Importance: Undecided => High

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

Title:
  App scope is blank and unresponsive when logging in desktop mode

Status in unity8 package in Ubuntu:
  New

Bug description:
  When logging in to Unity 8 desktop mode, the App scope is blank and
  unresponsive.  I have to close the window and then the new App scope
  window that is automatically started works fine.

  This occurs with Unity 8 on both a Wily machine and a Vivid+overlay
  machine.

  I'll attach unity8.log and unity8-dash.log soon.

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

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

[Touch-packages] [Bug 1501476] [NEW] datetime indicator spins out of control when clicking neighbor-month day

[Chad Miller]

Public bug reported:

Click the date indicator to get a calendar and list of schedule entries
for the highlighted, default day.

Notice the month grid of days. Assuming it doesn't fall evenly on week
boundaries, you'll see days from previous or following month in the
list.

Click on a day from another month.

Watch the selected month change, then rapidly switch to and fro in
months, pulling calendar items from evolution data store, re-rendering,
and burning CPU in three separate processes.

You can also walk ahead one month step, and then click backwards to a
margin day in contemporary month, but choosing the present day does not
trigger the bug, but any other day does.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: indicator-datetime 13.10.0+15.10.20150909-0ubuntu1
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Sep 30 15:17:55 2015
InstallationDate: Installed on 2014-05-07 (510 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: indicator-datetime
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  datetime indicator spins out of control when clicking neighbor-month
  day

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Click the date indicator to get a calendar and list of schedule
  entries for the highlighted, default day.

  Notice the month grid of days. Assuming it doesn't fall evenly on week
  boundaries, you'll see days from previous or following month in the
  list.

  Click on a day from another month.

  Watch the selected month change, then rapidly switch to and fro in
  months, pulling calendar items from evolution data store, re-
  rendering, and burning CPU in three separate processes.

  You can also walk ahead one month step, and then click backwards to a
  margin day in contemporary month, but choosing the present day does
  not trigger the bug, but any other day does.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-datetime 13.10.0+15.10.20150909-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 30 15:17:55 2015
  InstallationDate: Installed on 2014-05-07 (510 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1419829] Re: [Scope] location settings are enabled by default

[Pat McGowan]

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

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

Title:
  [Scope] location settings are enabled by default

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  Opinion
Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  This is in contrast to the rest of the system where user have to
  explicitly grant access right upfront.

  Possible solution would be to add a new page in phone setup wizard
  asking for whether scopes are allowed to use location or not and then
  applying this to individual scope location settings.

  UX comment-

  Potential new project: When scopes will be launched as apps, we'll
  probably need some coach marks // independent onboard experience to
  explain data consumption and location services usage.

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

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

[Touch-packages] [Bug 1492280] Re: Enabling hotspot when Wi-Fi is off breaks Wi-Fi

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

Title:
  Enabling hotspot when Wi-Fi is off breaks Wi-Fi

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  current build number: 105
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-09-04 11:06:40
  version version: 105
  version ubuntu: 20150904
  version device: 20150818-0b38025
  version custom: 20150814-887-8-46

  Reproduce:
  1. Make sure you have a hotspot
  2. Wi-Fi OFF
  3. Hotspot ON
  4. Hotspot OFF

  What happens:
  Indicator toggles are in the correct state, but no access points appear and 
no connection with known networks is established.

  What should happen:
  Should connect to the known network

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

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

[Touch-packages] [Bug 1488569] Re: MPRIS controls don't reflect the current player state

[Pat McGowan]

** Changed in: indicator-sound (Ubuntu)
   Status: Confirmed => In Progress

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

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

Title:
  MPRIS controls don't reflect the current player state

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  Triaged
Status in indicator-sound package in Ubuntu:
  In Progress

Bug description:
  The MPRIS controls (play/pause, next, previous) should reflect the
  current state of the current media player in media-hub. The following
  are what I would expect:

  1. When media-hub reports that CanGoNext/Previous are false, the next
  and previous buttons in the indicator are disabled and visually greyed
  out or something to this effect.

  2. The play button should show when media-hub reports that the current
  player is stopped or pause.

  3. The pause button should show instead of the play button when media-
  hub reports that the current player is playing.

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

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

[Touch-packages] [Bug 1380702] Re: No keyboards shortcuts in QT apps

[Pat McGowan]

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

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

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  In Progress
Status in sni-qt:
  New
Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  In some apps built using QT4 & 5, menu shortcuts are greyed out and
  inoperant. Only alt and FKeys-based shortcuts work. Others, notably
  ctrl+c for copying, do not.

  This is quite serious ; mail me for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions

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

[Touch-packages] [Bug 1501491] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.6 on trusty

[Serge Hallyn]

** Attachment added: "proposed debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1501491/+attachment/4480272/+files/debdiff

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

Title:
  Unable to start containers after upgrade to 1.0.7-0ubuntu0.6 on trusty

Status in lxc package in Ubuntu:
  New

Bug description:
  A partial fix was made for 1501310 - this case still fails.

  /home/ubuntu/nzos/volumes/1.0.0/common/shared
  /var/lib/lxc/0002/rootfs/nzos/./__shared__ none ro,bind 0 0

  This line is giving the same error. With 1.0.7-0ubuntu0.6 installed.

  lxc-start: utils.c: ensure_not_symlink: 1398 Mount onto
  /usr/lib/x86_64-linux-gnu/lxc//nzos/./__shared__ resulted in
  /usr/lib/x86_64-linux-gnu/lxc/nzos/__shared__

  lxc-start: utils.c: safe_mount: 1423 Mount of 
'/home/ubuntu/nzos/volumes/1.0.0/common/shared' onto 
'/usr/lib/x86_64-linux-gnu/lxc//nzos/./__shared__' was onto a symlink!
  lxc-start: conf.c: mount_entry: 2051 No such file or directory - failed to 
mount '/home/ubuntu/nzos/volumes/1.0.0/common/shared' on 
'/usr/lib/x86_64-linux-gnu/lxc//nzos/./__shared__'
  lxc-start: conf.c: lxc_setup: 4160 failed to setup the mounts for '0002'
  lxc-start: start.c: do_start: 688 failed to setup the container
  lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2
  lxc-start: start.c: __lxc_start: 1080 failed to spawn '0002'
  lxc-start: lxc_start.c: main: 342 The container failed to start.
  lxc-start: lxc_start.c: main: 346 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04
  Codename: trusty

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

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

[Touch-packages] [Bug 1481330] Re: Xmir closes when client closes display

[kevin gunn]

** Also affects: canonical-pocket-desktop
   Importance: Undecided
   Status: New

** Changed in: canonical-pocket-desktop
 Assignee: (unassigned) => kevin gunn (kgunn72)

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

Title:
  Xmir closes when client closes display

Status in canonical-pocket-desktop:
  New
Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Xmir crashes when a client loses its connection to Xmir, either
  through XCloseDisplay, or by normal program termination. This affects
  xprop and GTK applications (they temporarily open a connection to the
  X server to obtain the value of the AT_SPI_BUS property on the root
  window).

  This is what is printed in application's upstart log:

  (EE)
  Fatal server error:
  (EE) Failed to connect to Mir: Failed to process connect response: 
/build/mir-3eDTxk/mir-0.14.0+15.10.20150723.1/src/client/probing_client_platform_factory.cpp(37):
 Throw in function virtual std::shared_ptr 
mir::client::ProbingClientPlatformFactory::create_client_platform(mir::client::ClientContext*)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error
  std::exception::what: No appropriate client platform module found

  (EE)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1481330/+subscriptions

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

[Touch-packages] [Bug 1501240] [NEW] Serialport doens't work correctly after ubuntu update?

[green]

Public bug reported:

I have a strange problem with my serial port. It seems that sth has changed 
after ubuntu updates and reboot. 
When I try to open serial port in python I get exception: 

'device reports readiness to read but returned no data (device
disconnected or multiple access on port?)'

przem@przem:~/Pulpit/bat/scripts$ python
Python 2.7.6 (default, Jun 22 2015, 17:58:13) 
[GCC 4.8.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import serial
>>> ser = serial.Serial("/dev/ttyUSB0", 57600)
>>> ser.read()
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/local/lib/python2.7/dist-packages/serial/serialposix.py", line 
475, in read
raise SerialException('device reports readiness to read but returned no 
data (device disconnected or multiple access on port?)')
serial.serialutil.SerialException: device reports readiness to read but 
returned no data (device disconnected or multiple access on port?)
>>> 

I know that there are also different users who has this problem. 
more info:
http://superuser.com/questions/979722/serialport-doenst-work-correctly-after-ubuntu-update

** Affects: python2.7 (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: update-manager (Ubuntu) => python2.7 (Ubuntu)

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

Title:
  Serialport doens't work correctly after ubuntu update?

Status in python2.7 package in Ubuntu:
  New

Bug description:
  I have a strange problem with my serial port. It seems that sth has changed 
after ubuntu updates and reboot. 
  When I try to open serial port in python I get exception: 

  'device reports readiness to read but returned no data (device
  disconnected or multiple access on port?)'

  przem@przem:~/Pulpit/bat/scripts$ python
  Python 2.7.6 (default, Jun 22 2015, 17:58:13) 
  [GCC 4.8.2] on linux2
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import serial
  >>> ser = serial.Serial("/dev/ttyUSB0", 57600)
  >>> ser.read()
  Traceback (most recent call last):
File "", line 1, in 
File "/usr/local/lib/python2.7/dist-packages/serial/serialposix.py", line 
475, in read
  raise SerialException('device reports readiness to read but returned no 
data (device disconnected or multiple access on port?)')
  serial.serialutil.SerialException: device reports readiness to read but 
returned no data (device disconnected or multiple access on port?)
  >>> 

  I know that there are also different users who has this problem. 
  more info:
  
http://superuser.com/questions/979722/serialport-doenst-work-correctly-after-ubuntu-update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1501240/+subscriptions

-- 
Mailing list: https://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 1498945] Re: [libglib2.0] evolution + evolution-ews

[mangouste06]

The changes are :

new libglib2.0, glib-networking, and all evolution-data-server related
packages from PPA.

I rebooted to check.


2015-09-30 11:57 GMT+02:00 Gérard BIGOT :

> I declare success with this stack :
>
>  dpkg -l | egrep 'evolution|libglib|networking-'
> ii  evolution  3.16.5-1ubuntu1
>amd64groupware suite with mail client and
> organizer
> ii  evolution-common   3.16.5-1ubuntu1
>all  architecture independent files for
> Evolution
> ii  evolution-data-server
>  3.16.5-1ubuntu3~ppa0   amd64evolution database
> backend server
> ii  evolution-data-server-common
> 3.16.5-1ubuntu3~ppa0   all  architecture
> independent files for Evolution Data Server
> ii  evolution-ews  3.16.3-1
> amd64Exchange Web Services integration for
> Evolution
> ii  evolution-plugins  3.16.5-1ubuntu1
>amd64standard plugins for Evolution
> ii  glib-networking-common 2.46.0-1
> all  network-related giomodules for GLib -
> data files
> ii  glib-networking-services   2.46.0-1
> amd64network-related giomodules for GLib -
> D-Bus services
> ii  libebackend-1.2-10
> 3.16.5-1ubuntu3~ppa0   amd64Utility library for
> evolution data servers
> ii  libebook-1.2-16
>  3.16.5-1ubuntu3~ppa0   amd64Client library for
> evolution address books
> ii  libebook-contacts-1.2-1
>  3.16.5-1ubuntu3~ppa0   amd64Client library for
> evolution contacts books
> ii  libecal-1.2-18
> 3.16.5-1ubuntu3~ppa0   amd64Client library for
> evolution calendars
> ii  libedata-book-1.2-25
> 3.16.5-1ubuntu3~ppa0   amd64Backend library for
> evolution address books
> ii  libedata-cal-1.2-27
>  3.16.5-1ubuntu3~ppa0   amd64Backend library
> for evolution calendars
> ii  libedataserver-1.2-20
>  3.16.5-1ubuntu3~ppa0   amd64Utility library
> for evolution data servers
> ii  libedataserverui-1.2-1
> 3.16.5-1ubuntu3~ppa0   amd64Utility library for
> evolution data servers
> ii  libevolution   3.16.5-1ubuntu1
>amd64evolution libraries
> ii  libglib-perl   3:1.307-3
>amd64interface to the GLib and GObject
> libraries
> ii  libglib2.0-0:amd64 2.46.0-2
> amd64GLib library of C routines
> ii  libglib2.0-bin 2.46.0-2
> amd64Programs for the GLib library
> ii  libglib2.0-data2.46.0-2
> all  Common files for GLib library
> ii  libglibmm-2.4-1v5:amd64
>  2.45.41.is.2.44.0-0ubuntu2 amd64C++ wrapper for
> the GLib toolkit (shared libraries)
> gerard@FR010611:~$
>
>
> 2015-09-30 10:49 GMT+02:00 Iain Lane :
>
>> On Wed, Sep 30, 2015 at 08:14:01AM -, mangouste06 wrote:
>> > Hi,
>> >
>> > can we test with the proposed patch in
>> > https://bugzilla.gnome.org/show_bug.cgi?id=755075 ?
>>
>> I put in the PPA, please check it in a little bit once it is built.
>>
>> --
>> Iain Lane  [ i...@orangesquash.org.uk ]
>> Debian Developer   [ la...@debian.org ]
>> Ubuntu Developer   [ la...@ubuntu.com ]
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1498945
>>
>> Title:
>>   [libglib2.0] evolution + evolution-ews
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/glib/+bug/1498945/+subscriptions
>>
>
>

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

Title:
  [libglib2.0] evolution + evolution-ews

Status in GLib:
  Invalid
Status in evolution package in Ubuntu:
  New
Status in evolution-ews package in Ubuntu:
  New
Status in glib2.0 package in Ubuntu:
  New

Bug description:
  I have two different exchange email configurated in evolution through
  evolution-ews.

  With

  libglib2.0-0_2.45.7-1_amd64.deb
  libglib2.0-bin_2.45.7-1_amd64.deb
  libglib2.0-data_2.45.7-1_all.deb

  it's working. I get new mails. I can send mails. Calendar OK.

  But, with the new

  libglib2.0-0_2.45.8-1_amd64.deb
  

[Touch-packages] [Bug 1488327] Re: [performance] Indicator bar animation latency is artificially high

[Daniel van Vugt]

** Changed in: qtmir
   Status: New => Won't Fix

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

Title:
  [performance] Indicator bar animation latency is artificially high

Status in QtMir:
  Won't Fix
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  The indicator bar animation latency seems to be artificially high --
  limited to a fixed speed that it uses when you release it.

  I suggest it should be designed to move more quickly while you're
  touching it. Because in a low latency experiment today I've found I
  can make the dash more responsive than the shell's indicator pulldown:

  1. Install devel-proposed (wily) which now has Mir 0.15 and its lower latency.
  2. Lower latency further with these experimental options:
  restart unity8 QML_NO_TOUCH_COMPRESSION=1 MIR_SERVER_NBUFFERS=2

  You may have to use mako to ensure it's got the power to keep up...

  Result: Dash scrolling is now faster and more responsive than the
  indicator pulldown. The dash tracks your finger but the indicator
  pulldown seems to have it's own max speed, which is slower.

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

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

[Touch-packages] [Bug 1476662] Re: lxc-start symlink vulnerabilities may allow guest to read host filesystem, interfere with apparmor

[Stephen Gaito]

Looking through the top Google results on how to bind-mount a directory
from the host-server into the lxc-server I notice that:

* Stéphane Graber's "LXC 1.0: Advanced container usage [3/10]" post (
https://www.stgraber.org/2013/12/21/lxc-1-0-advanced-container-usage/ )
makes use of the **relative** mount point (in the lxc-server's fstab
config file on the host-server)

* Unfortunately the **official**(?) Debian LXC wiki page on "LXC" has
the topic "Bind mounts inside the container" (
https://wiki.debian.org/LXC#Bind_mounts_inside_the_container ) which
uses the lxc.mount.entry line in the config file **and** makes use of an
**absolute** mount point.

So those following the official Debian LXC documentation will be caught
by this security patch. ;-(

Just to be definite: changing all lxc.mount.entry mount points to
**relative** paths is a current workaround.

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

Title:
  lxc-start symlink vulnerabilities may allow guest to read host
  filesystem, interfere with apparmor

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  lxc-start shuffles around mounts using helper directory
  /usr/lib/x86_64-linux-gnu/lxc (guest root fs is mounted here)

  It then modifies mounts operating in guest root directory before
  invoking init. As it does not check if all mount points are
  directories, a malicious guest may modify its internal structure
  before shutdown (or was created using manipulated image) and then when
  started again, guest may

  * Access  the whole host root filesystem

  * Block switching from lxc-start apparmor profile to lxc-container-
  default

  
  # Real putold before pivot-root (root fs will end here)
  mkdir -p /x/lxc_putold

  # Faked putold
  ln -s /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold lxc_putold
  mkdir -p /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold/proc
  touch /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold/proc/mounts

  
  # proc fake
  mkdir -p /x/proc
  umount /proc
  rmdir /proc
  ln -s /usr/lib/x86_64-linux-gnu/lxc/x/proc proc

  mkdir -p /usr/lib/x86_64-linux-gnu/lxc/x/proc/1/attr 
/usr/lib/x86_64-linux-gnu/lxc/x/proc/self
  touch /usr/lib/x86_64-linux-gnu/lxc/x/proc/1/attr/current
  touch /usr/lib/x86_64-linux-gnu/lxc/x/proc/self/status


  The  issue was also found during
  https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.html

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

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

[Touch-packages] [Bug 1495943] Re: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash

[Bug Watch Updater]

** Changed in: glib
   Status: Confirmed => Incomplete

** Changed in: glib
   Importance: Medium => Critical

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

Title:
  gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash

Status in GLib:
  Incomplete
Status in glib2.0 package in Ubuntu:
  New
Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  [System]

  Ubuntu MATE 15.10, fully updated.

  [Steps to reproduce]

  1. Create an empty file: touch ~/test
  2. Move it to trash: gvfs-trash ~/test
  3. Launch some file manager, browse Trash folder and try to restore the file. 
I've tested it with the following file managers: Caja, Nemo, Nautilus and 
Thunar.

  [Expected result]

  The file should be restored to its original location.

  [What happens instead]

  The file manager complains that it can't determine the original
  location of the file, and so doesn't restore it.

  [Details]

  When moving file to Trash, gvfs-trash does not add trash::orig-path
  and trash::deletion-date attributes to it. Without that the file
  manager can't determine the original location of the file, and hence
  can't restore it.

  You can check the file attributes by printing the moved file's info:
  gvfs-info trash:///test

  [Regression description]

  Restoring the files has been working fine in Ubuntu 14.04 and 15.04.
  This bug appeared only in 15.10, so it's a regression.

  You can see the gvfs-info output from 15.04 and 15.10 in the
  attachments below.

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

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

[Touch-packages] [Bug 1314126] Re: Ubuntu logo from login screen remains visible on desktop after login

[d❤vid seaward]

I have since moved on to a new version of Ubuntu and the issue does not
occur there.

** Changed in: unity
   Status: Incomplete => Invalid

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

** Changed in: unity-greeter (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Ubuntu logo from login screen remains visible on desktop after login

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid
Status in unity-greeter package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:

   * Log in to Ubuntu (Unity) session from login screen

  What should happen:

   * On login screen: desktop background appears as background, dots are 
overlayed, Ubuntu logo is overlayed
   * Once logged in: desktop background appears as background, no dots, no 
Ubuntu logo

  What happens instead:

   * Once logged in: desktop background appears, Ubuntu logo is
  overlayed

  Further notes:

   * I disabled the dots on the login screen, so I'm not sure if they appear, 
I'm pretty sure not
   * I am pretty sure that the logo was appearing on the desktop from when I 
first installed 14.04, it has remained after changing the background and 
disabling the dots
   * I have confirmed that the background image itself does not contain the logo

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

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

[Touch-packages] [Bug 1498945] Re: [libglib2.0] evolution + evolution-ews

[Iain Lane]

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

** Changed in: evolution-ews (Ubuntu)
   Status: New => Invalid

** Changed in: glib2.0 (Ubuntu)
   Status: New => Invalid

** Also affects: evolution-data-server (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: evolution-data-server (Ubuntu)
   Status: New => Triaged

** Changed in: evolution-data-server (Ubuntu)
   Importance: Undecided => High

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

Title:
  [libglib2.0] evolution + evolution-ews

Status in GLib:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in evolution-data-server package in Ubuntu:
  Triaged
Status in evolution-ews package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid

Bug description:
  I have two different exchange email configurated in evolution through
  evolution-ews.

  With

  libglib2.0-0_2.45.7-1_amd64.deb
  libglib2.0-bin_2.45.7-1_amd64.deb
  libglib2.0-data_2.45.7-1_all.deb

  it's working. I get new mails. I can send mails. Calendar OK.

  But, with the new

  libglib2.0-0_2.45.8-1_amd64.deb
  libglib2.0-bin_2.45.8-1_amd64.deb
  libglib2.0-data_2.45.8-1_all.deb

  I can't even connect to the mail servers.

  I can switch from working/not working and back in the  same unity
  session just by switching libglib versions and restarting evolution.

  I'm in wily uptodate.

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

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

[Touch-packages] [Bug 1476662] Re: lxc-start symlink vulnerabilities may allow guest to read host filesystem, interfere with apparmor

[Daniel Kraft]

@roman-fiedler
We're using absolute mount targets here, so that might help. Will try this out.

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

Title:
  lxc-start symlink vulnerabilities may allow guest to read host
  filesystem, interfere with apparmor

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  lxc-start shuffles around mounts using helper directory
  /usr/lib/x86_64-linux-gnu/lxc (guest root fs is mounted here)

  It then modifies mounts operating in guest root directory before
  invoking init. As it does not check if all mount points are
  directories, a malicious guest may modify its internal structure
  before shutdown (or was created using manipulated image) and then when
  started again, guest may

  * Access  the whole host root filesystem

  * Block switching from lxc-start apparmor profile to lxc-container-
  default

  
  # Real putold before pivot-root (root fs will end here)
  mkdir -p /x/lxc_putold

  # Faked putold
  ln -s /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold lxc_putold
  mkdir -p /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold/proc
  touch /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold/proc/mounts

  
  # proc fake
  mkdir -p /x/proc
  umount /proc
  rmdir /proc
  ln -s /usr/lib/x86_64-linux-gnu/lxc/x/proc proc

  mkdir -p /usr/lib/x86_64-linux-gnu/lxc/x/proc/1/attr 
/usr/lib/x86_64-linux-gnu/lxc/x/proc/self
  touch /usr/lib/x86_64-linux-gnu/lxc/x/proc/1/attr/current
  touch /usr/lib/x86_64-linux-gnu/lxc/x/proc/self/status


  The  issue was also found during
  https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.html

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

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

[Touch-packages] [Bug 1476662] Re: lxc-start symlink vulnerabilities may allow guest to read host filesystem, interfere with apparmor

[Daniel Kraft]

@roman-fiedler
Might point to the same, but we already have relative mount targets:

  lxc.mount.entry = proc /var/lib/our_containers/123/rootfs/proc proc
nosuid,nodev,noexec 0 0

So that won't help as suggested in the mail.

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

Title:
  lxc-start symlink vulnerabilities may allow guest to read host
  filesystem, interfere with apparmor

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  lxc-start shuffles around mounts using helper directory
  /usr/lib/x86_64-linux-gnu/lxc (guest root fs is mounted here)

  It then modifies mounts operating in guest root directory before
  invoking init. As it does not check if all mount points are
  directories, a malicious guest may modify its internal structure
  before shutdown (or was created using manipulated image) and then when
  started again, guest may

  * Access  the whole host root filesystem

  * Block switching from lxc-start apparmor profile to lxc-container-
  default

  
  # Real putold before pivot-root (root fs will end here)
  mkdir -p /x/lxc_putold

  # Faked putold
  ln -s /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold lxc_putold
  mkdir -p /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold/proc
  touch /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold/proc/mounts

  
  # proc fake
  mkdir -p /x/proc
  umount /proc
  rmdir /proc
  ln -s /usr/lib/x86_64-linux-gnu/lxc/x/proc proc

  mkdir -p /usr/lib/x86_64-linux-gnu/lxc/x/proc/1/attr 
/usr/lib/x86_64-linux-gnu/lxc/x/proc/self
  touch /usr/lib/x86_64-linux-gnu/lxc/x/proc/1/attr/current
  touch /usr/lib/x86_64-linux-gnu/lxc/x/proc/self/status


  The  issue was also found during
  https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.html

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

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

[Touch-packages] [Bug 1434124] Re: [dash] + [scopes] Uninstallation confirmation screen inconsistent with other dialogs

[Grazina]

** Changed in: ubuntu-ux
 Assignee: Grazina (boroskograzina) => Jamie Young (jamiedawsonyoung)

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

Title:
  [dash] + [scopes] Uninstallation confirmation screen inconsistent with
  other dialogs

Status in Ubuntu UX:
  In Progress
Status in unity-scope-click package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  On current rtm trying to uninstall a click from the dash you get a
  confirmation screen with a "confirm" button on the left and an orange
  "cancel" one on the right, that seems inconsistant with the
  guideline/what other part of the system are doing

  - why is "cancel" in orange? 
https://design.ubuntu.com/apps/building-blocks/buttons states that the color is 
for negative actions
  - unsure that "confirm" is conveying what the button does, could it be 
"uninstall" or "confirm uninstallation"?

  it feels like that the left button should be the red one and have
  something in its label stating what you are confirming (since the
  rational is that users tend to not read the text description, so the
  button should summarize the action they are doing)

  -- UX Comment --

  We are currently working on the redesign of scopes previews and design
  patterns for the use of buttons (types, colour, position, behaviour).
  (Page 133:
  
https://docs.google.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw/edit#heading=h.pl3n70ucwqtp).
  The desired resolution and specs will be updated as soon as they are
  available.

  
  - Design comment -
04/09/2015

  We are working on this project. Visuals will be attached asap as we
  have solution.

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

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

[Touch-packages] [Bug 1412780] Re: [Dialogs] Power dialog looks like a tricolor

[Grazina]

** Changed in: ubuntu-ux
 Assignee: Grazina (boroskograzina) => Jamie Young (jamiedawsonyoung)

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

Title:
  [Dialogs] Power dialog looks like a tricolor

Status in Ubuntu UX:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  1. Hold down the Power button.

  What you see: A "Power" dialog appears with a stack of three buttons:
  "Power off" in red, "Restart" in green, and "Cancel" in black. The
  effect is that of a tricolor flag.
  

  What you should see: Something that doesn't look like a tricolor.

  Possible solutions include:
  * Reducing the number of colors.
  * Changing to horizontal icon-only buttons (bug 1377146).
  * Abolishing the dialog somehow.

  - Design comment -
    07/08/2015

  We are working on this project. Visuals will be attached asap as we
  have solution.

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

-- 
Mailing list: https://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 1498945] Re: [libglib2.0] evolution + evolution-ews

[Iain Lane]

On Wed, Sep 30, 2015 at 08:14:01AM -, mangouste06 wrote:
> Hi,
> 
> can we test with the proposed patch in
> https://bugzilla.gnome.org/show_bug.cgi?id=755075 ?

I put in the PPA, please check it in a little bit once it is built.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  [libglib2.0] evolution + evolution-ews

Status in GLib:
  Invalid
Status in evolution package in Ubuntu:
  New
Status in evolution-ews package in Ubuntu:
  New
Status in glib2.0 package in Ubuntu:
  New

Bug description:
  I have two different exchange email configurated in evolution through
  evolution-ews.

  With

  libglib2.0-0_2.45.7-1_amd64.deb
  libglib2.0-bin_2.45.7-1_amd64.deb
  libglib2.0-data_2.45.7-1_all.deb

  it's working. I get new mails. I can send mails. Calendar OK.

  But, with the new

  libglib2.0-0_2.45.8-1_amd64.deb
  libglib2.0-bin_2.45.8-1_amd64.deb
  libglib2.0-data_2.45.8-1_all.deb

  I can't even connect to the mail servers.

  I can switch from working/not working and back in the  same unity
  session just by switching libglib versions and restarting evolution.

  I'm in wily uptodate.

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

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