date:20141023

I don't think this was ever SRUed to trusty, so the the Trusty task
shouldn'e be marked Fix Released.

The fix was released in Utopic with apparmor 2.8.96~2541-0ubuntu1, but
Trusty is still on 2.8.95~2430-0ubuntu5.

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

Title:
  aa-genprof will crash when select scan on Ubuntu 14.04 server

Status in AppArmor Linux application security framework:
  Fix Released
Status in “apparmor” package in Ubuntu:
  Fix Released
Status in “apparmor” source package in Trusty:
  Fix Released

Bug description:
  Operating system : Ubuntu 14.04 LTS x86_64 server

  Command used :

  sudo aa-genprof suricata

  I will be asked to scan or finish, I selected "scan".  Then it
  crashes.

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

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

[Touch-packages] [Bug 1294797] Re: aa-genprof traceback with apparmor 2.8.95

The fix has not been released for trusty, so that task should be changed
back to Triaged.

apparmor is still 2.8.95~2430-0ubuntu5 in trusty

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

Title:
  aa-genprof traceback with apparmor 2.8.95

Status in AppArmor Linux application security framework:
  Fix Released
Status in “apparmor” package in Ubuntu:
  Fix Released
Status in “apparmor” source package in Trusty:
  Fix Released

Bug description:
  In a terminal, I run:

  $ sudo aa-genprof /usr/bin/empathy
  ...
  [(S)can system log for AppArmor events] / (F)inish

  
  At this point, I start empathy, then stop it.

  Now I go back to the terminal:
  
  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  Traceback (most recent call last):
File "/usr/sbin/aa-genprof", line 150, in 
  lp_ret = apparmor.do_logprof_pass(logmark, passno)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2240, in 
do_logprof_pass
  read_profiles()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2558, in 
read_profiles
  read_profile(profile_dir + '/' + file, True)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2584, in 
read_profile
  profile_data = parse_profile_data(data, file, 0)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2689, in 
parse_profile_data
  filelist[file]['profiles'][profile][hat] = True
  TypeError: 'bool' object does not support item assignment

  
  If I run it again, I get a different traceback:
  Traceback (most recent call last):
File "/usr/sbin/aa-genprof", line 150, in 
  lp_ret = apparmor.do_logprof_pass(logmark, passno)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2240, in 
do_logprof_pass
  read_profiles()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2558, in 
read_profiles
  read_profile(profile_dir + '/' + file, True)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2584, in 
read_profile
  profile_data = parse_profile_data(data, file, 0)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3031, in 
parse_profile_data
  raise AppArmorException(_('Syntax Error: Unknown line found in file: %s 
line: %s') % (file, lineno + 1))
  apparmor.common.AppArmorException: 'Syntax Error: Unknown line found in file: 
/etc/apparmor.d/zz-unconfined line: 3'

  
  /etc/apparmor.d/zz-unconfined contains:
  # v2 compatible wildly permissive profile
  profile "zz_unconfined" {
capability,
network,
/** rwlkm,
/** pix,

# TODO: when dbus hits:
dbus,
  }

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

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

[Touch-packages] [Bug 1364630] Re: init: Error while reading from descriptor: Broken pipe

2014-10-23 Thread kbngmal

Confirmed. It seems to be something to do with xconsole :

one@one-P35:/var/log$ cat syslog|grep pipe
Oct 24 12:17:24 one-P35 rsyslogd-2039: Could no open output pipe 
'/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct 24 12:26:58 one-P35 kernel: [   24.812375] init: Error while reading from 
descriptor: Broken pipe
Oct 24 12:26:58 one-P35 rsyslogd-2039: Could no open output pipe 
'/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct 24 12:36:40 one-P35 kernel: [   23.837473] init: Error while reading from 
descriptor: Broken pipe
Oct 24 12:36:40 one-P35 rsyslogd-2039: Could no open output pipe 
'/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]

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

Title:
  init: Error while reading from descriptor: Broken pipe

Status in “init-system-helpers” package in Ubuntu:
  Confirmed

Bug description:
  [   16.934379] init: Error while reading from descriptor: Broken pipe

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: init 1.20ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1
  Uname: Linux 3.16.0-11-generic x86_64
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep  2 17:23:15 2014
  InstallationDate: Installed on 2014-04-27 (128 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: init-system-helpers
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1303516] Re: ubiquity crashed with SIGSEGV in _int_malloc()

** Bug watch removed: Red Hat Bugzilla #998812
   https://bugzilla.redhat.com/show_bug.cgi?id=998812

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

Title:
  ubiquity crashed with SIGSEGV in _int_malloc()

Status in HarfBuzz:
  Fix Released
Status in “graphite2” package in Ubuntu:
  Invalid
Status in “harfbuzz” package in Ubuntu:
  Fix Released
Status in “graphite2” source package in Trusty:
  Invalid
Status in “harfbuzz” source package in Trusty:
  Fix Released

Bug description:
  [ Description ]

  Memory corruption when rendering Myanmar text leeds to a crash

  [ Test case ]

  IMPORTANT NOTE: below will modify currently running locale/keyboard be
  prepared to restore it, e.g. by enabling keyboard indicator to change
  keyboard back to normal.

  1. Install ubiquity on a desktop or boot from an ISO
    $ sudo apt-get install ubiquity-frontend-gtk
  2. If you run on a desktop start ubiquity with:
    $ ubiquity --greeter
  3. Scroll to the bottom of the language list, click on 5th or 4th from the 
bottom

  ACTUAL RESULT
  python3 segmentation fault:
  *** Error in `/usr/bin/python3': malloc(): memory corruption: 
0x03b33d80 ***
  Segmentation fault (core dumped)

  EXPECTED RESULT
  No crash

  [ QA ]

  Check that the test case doesn't crash after applying the SRU

  [ Original Report ]

  I was testing a daily imagine of Ubuntu Gnome 14.04 (Live Image test),
  and was just checking out the languages on the initial boot up. When i
  was trying to click on the 4th language from the bottom ubiquitity
  crashed to give me this error.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: ubiquity 2.17.10
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.339
  Date: Mon Apr  7 00:06:38 2014
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  InterpreterPath: /usr/bin/python3.4
  LiveMediaBuild: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Daily amd64 (20140406)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --greeter --only
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f3d8a71dd71 <_int_malloc+689>:  mov
%r14,0x10(%r9)
   PC (0x7f3d8a71dd71) ok
   source "%r14" ok
   destination "0x10(%r9)" (0x18001210) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: ubiquity
  StacktraceTop:
   _int_malloc (av=0x7f3d8aa5c760 , bytes=1824) at malloc.c:3489
   __GI___libc_malloc (bytes=1824) at malloc.c:2891
   ?? () from /usr/lib/x86_64-linux-gnu/libgraphite2.so.3
   gr_make_font_with_ops () from /usr/lib/x86_64-linux-gnu/libgraphite2.so.3
   gr_make_font_with_advance_fn () from 
/usr/lib/x86_64-linux-gnu/libgraphite2.so.3
  Title: ubiquity crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartUbiquity: debconf: DbDriver "templatedb": 
/var/cache/debconf/templates.dat is locked by another process: Resource 
temporarily unavailable
  UserGroups:

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

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

[Touch-packages] [Bug 805769] Re: [MS-1727, Realtek ALC888, Speaker, Internal] low volume & "muddy" sound

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

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [MS-1727, Realtek ALC888, Speaker, Internal] low volume & "muddy"
  sound

Status in “alsa-driver” package in Ubuntu:
  Expired

Bug description:
  Ubuntu 11.04

  Volume set to 100% in alsamixer (master, speaker & pcm). Sound CAN be
  heard, but it is very low/quiet and "muddy" sounding... Almost sounds
  like too much bass.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: alsa-base 1.0.24+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  reishka1405 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd660 irq 43'
 Mixer name : 'Realtek ALC888'
 Components : 'HDA:10ec0888,1462100f,00100202 
HDA:11c11040,11c10001,00100200'
 Controls  : 29
 Simple ctrls  : 16
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xd004 irq 44'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Mon Jul  4 22:37:44 2011
  InstallationMedia:
   
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Internal Audio - HDA Intel
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [MS-1727, Realtek ALC888, Speaker, Internal] Background noise or low 
volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1727IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1727
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1727IMS.106:bd02/01/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-1727:pvrREV1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-1727:rvrREV1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrN/A:
  dmi.product.name: MS-1727
  dmi.product.version: REV:1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

[Touch-packages] [Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-10-23 Thread Станислав

For me the solution to the problem was the move to systemd. Like here
http://askubuntu.com/questions/420917/how-can-i-replace-upstart-with-
systemd

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

Title:
  Not authorized to perform operation / Unable to determine the session
  we are in: No session for pid

Status in “gdm” package in Ubuntu:
  Confirmed
Status in “lightdm” package in Ubuntu:
  Confirmed
Status in “lxdm” package in Ubuntu:
  Confirmed
Status in “policykit-desktop-privileges” package in Ubuntu:
  Confirmed

Bug description:
  After a new install of 64 bit Ubuntu 13.10 on my second partition, I
  used dpkg to reinstall all the same packages I had on my 32 bit 13.04
  partition.  I copied all my home directory files over and updated all
  the packages.  I now find that I don't have permissions to change the
  network settings; I can't mount my other hard drive or any USB stick
  using nautilus, or (udisks without using sudo)' I can't run synaptic
  by clicking on the GUI (I have to go to a terminal and sudo synaptic);
  etc.  I can't find any documentation on the configuration of
  policykit-desktop-privileges, so I'm filing this bug.  For me it
  appears to be totally broken.  Maybe someone can help me out.

  Thanks,

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: policykit-desktop-privileges 0.16
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:20:55 2013
  InstallationDate: Installed on 2013-10-09 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-desktop-privileges
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1350910] Re: blank screen after suspend resume

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

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

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

Title:
  blank screen after suspend resume

Status in “xorg” package in Ubuntu:
  Expired

Bug description:
  Mouse and keyboard not working, still able to ssh into system and
  reboot. Xorg.0.log saved from ssh session after a problem appear
  attached.

  WORKAROUND: It seems no problem with fglrx proprietary drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.3
  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
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu Jul 31 19:19:59 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7420G] [1002:9992] 
(prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:194e]
  InstallationDate: Installed on 2014-07-06 (25 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP ProBook 455 G1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=3cc3893f-1a34-4d21-8304-52e841a9dbef ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CPE Ver. F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 194E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.0B
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CPEVer.F.21:bd09/05/2013:svnHewlett-Packard:pnHPProBook455G1:pvrA2018CD200:rvnHewlett-Packard:rn194E:rvrKBCVersion91.0B:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 455 G1
  dmi.product.version: A2018CD200
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Jul 31 19:19:05 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.1
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1059872] Re: Error formatting disk using disk utility

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

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

Title:
  Error formatting disk using disk utility

Status in “udisks2” package in Ubuntu:
  Invalid
Status in “util-linux” package in Ubuntu:
  Fix Released
Status in “udisks2” source package in Trusty:
  Invalid
Status in “util-linux” source package in Trusty:
  Triaged
Status in “util-linux” package in Debian:
  Fix Released

Bug description:
  Formatting a SD card using the disk utility fails with an error
  message

  "Error formatting disk - Error synchronizing after initial wipe: Timed
  out waiting for object (udisks-error-quark, 0)"

  Steps to repro:
  Launch the disk utility
  Plug a SD card into the computer
  Select the SD card and click on the gears icon at the top right of the 
application
  From the drop down menu, select "Format Disk"
  maintain the default setting and select Format
  Acknowledge warnings
  After format process has been going for a while, the error message shown 
above pops up

  Workaround: 
  After selecting the SD card, instead of clicking the gear icon to format, 
click the partition in the "Volumes" section.
  Delete the partition ("minus" icon)
  Create a new partition

  -

  The underlying problem is that the "wipefs" tool from util-linux does
  not work any more.

  === TEST CASE ===
  $ sudo modprobe scsi_debug dev_size_mb=200
  # this creates a new /dev/sdX, usually /dev/sdb; check dmesg!

  # now create a partition table
  $ cat

[Touch-packages] [Bug 1350598] Re: AppArmor policy compile improvements

** Description changed:

  apparmor_parser can take a long time to compile policy especially when there 
is a lot of policy, so we want to utilize compiled cache profile as much as 
possible. Cache files will have to be regenerated in the following cases:
   * the kernel .features file is updated (eg, new features are added to
     apparmor in the new kernel)
   * apparmor itself is updated
   * on devices with click packages, apparmor-easyprof-ubuntu and/or
-click-apparmor is updated
+    click-apparmor is updated
  
  As of 2014-10-02, what can be expected is:
  
  - Systems with system-image updates (eg, Ubuntu Touch):
    - First boot will use the precompiled cache files in the rootfs or custom
  tarball and be fast
    - Reboots will use the cache files on the device and be fast
    - First boots after upgrades will use the cache files on the device if the
  above conditions are not met and be fast
    - Production devices will not meet any of those conditions except under
  exceptional and rare circumstances (eg, major OS upgrades like 14.10 to
  15.04) and be fast
    - First boots after upgrades that meet one of the conditions will need to
  regenerate the cache. This can happen on development releases where the
  kernel features file, apparmor, apparmor-easyprof-ubuntu or
- click-apparmor are still under development and getting updates
+ click-apparmor are still under development and getting updates
  - Systems with apt updates (eg, current Ubuntu Desktop and Server):
    - First boot will compile cache files
    - Reboots will use the cache files on the machine and be fast
    - First boots after upgrades will use the cache files on the machine if the
  above conditions are not met and be fast
    - Stable releases of Ubuntu will not meet any of those conditions except
  under exceptional and rare circumstances (eg, major OS upgrades like
  14.10 to 15.04) and be fast
    - First boots after upgrades that meet one of the above conditions will
  need to regenerate the cache. This can happen on development releases
  where the kernel features file, apparmor, apparmor-easyprof-ubuntu or
  click-apparmor are still under development and getting updates
  
  In addition to the above, updates to only apparmor-easyprof-ubuntu will
  regenerate the cache files for only the policy that is affected (eg, if
  there is a change to the location policy group in policy version 1.2,
  only apps using this policy version and this policy group will need to
  be recompiled).
  
  Planned improvements (in order of most likely to be done first):
  1. Finetuning the checks to invalidate the cache (eg, .md5sums could only
     be for /etc/apparmor.d/abstractions, ...) - WONTFIX (will want an
     md5sum on apparmor_parser since it could change the cache and the md5sum
     will always change. Furthermore, apparmor-easyprof-ubuntu is all policy
     so there is no gain there. click-apparmor could possibly benefit, but
     it doesn't change often and when it does, it is typically for policy)
  2. Investigate ways to utilize the custom tarball and rootfs precompiled
     cache files on upgrades when apparmor, apparmor-easyprof-ubuntu and
-click-apparmor are updated
+    click-apparmor are updated
  3. Improve cache handling for app store apps (eg, having the app store
-    server precompile them so that the device can download them when it needs
-    to rather than having to regenerate them itself)
- 4. For systems with apt upgrades, compile the policy either during install or
-    on kernel upgrade rather than on boot
- 5. Support cache files per kernel .features file (or kernel version). This
-    will allow people to boot into a previous kernel without having to
-    recompile policy
+    server precompile them so that the device can download them when it 
+needs to rather than having to regenerate them itself): WONTFIX 
+(doesn't scale)
+ 4. For systems with apt upgrades, compile the policy either during 
+install or on kernel upgrade rather than on boot
+ 5. Support cache files per kernel .features file (or kernel version). 
+This will allow people to boot into a previous kernel without having 
+to recompile policy
  6. Improve parser compile time
  7. Investigate how to utilize profile composition and profile stacking to
     decrease compile and load times (eg, one idea is that the policy template
     is compiled once and each policy group once such that the parser need
     only stitch the already compiled bits together)
  
  Work is planned for the medium term for '1-3' with '4' and '5' coming as
  needed. '6' and '7' will be handled in the long term.
  
  Original description:
  Just updated my Nexus 7 2013 from #160 to #161. It's been sat at the Google 
logo for 15 minutes now. It looks and feels like it's hung. As a user I'd be 
rebooting it thinking it had crashed by now. I shell in and find 
apparmor_parser  using a lot of c

[Touch-packages] [Bug 1215092] Re: please add support to run postinst-style code on first boot after upgrades

Marking click-apparmor as Won't Fix. We are going to handle this another
way.

** Changed in: click-apparmor (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  please add support to run postinst-style code on first boot after
  upgrades

Status in Ubuntu system image (server/client/updater):
  In Progress
Status in “click-apparmor” package in Ubuntu:
  Won't Fix
Status in “lxc-android-config” package in Ubuntu:
  Fix Released
Status in “click-apparmor” source package in Saucy:
  Won't Fix
Status in “lxc-android-config” source package in Saucy:
  Fix Released
Status in “click-apparmor” source package in Trusty:
  Won't Fix

Bug description:
  Currently updates to system packages are run on the server with postinst, 
triggers, etc running there such that when an image based update is delivered, 
all of this already done. This a great for the vast majority of cases but there 
are times when this is not enough, for example, updating click package apparmor 
profiles after the system has apparmor policy updates. Consider this scenario:
   1. user uses RO Ubuntu image on a device
   2. user install 15 click packages
   3. bug is found in apparmor policy for the ubuntu-sdk apparmor template
   4. apparmor-easyprof-ubuntu is updated to correct the template
   5. image based upgrades picks this up and include the new 
apparmor-easyprof-ubuntu in its update
   6. the update is delivered to users

  At this point, newly installed click packages will get the apparmor
  policy fixes, but not the original 15. It is a requirement for
  application confinement that we are able to update policy for already
  installed click packages. Currently, policy updates may happen via
  apparmor, apparmor-easyprof-ubuntu and/or click-apparmor.

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

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

[Touch-packages] [Bug 1377338] Re: apparmor may fail to load some profiles if one is corrupted

14.10 had workaround in place in 2.8.98-0ubuntu2

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

** Changed in: apparmor
   Status: New => Triaged

** Changed in: apparmor
   Importance: Undecided => Medium

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

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

Title:
  apparmor may fail to load some profiles if one is corrupted

Status in AppArmor Linux application security framework:
  Triaged
Status in “apparmor” package in Ubuntu:
  Fix Released
Status in “click-apparmor” package in Ubuntu:
  Fix Released
Status in “apparmor” package in Ubuntu RTM:
  Fix Released
Status in “click-apparmor” package in Ubuntu RTM:
  Fix Released

Bug description:
  Steps to reproduce (on the emulator):
  1. sudo sh -c 'echo foo > 
/var/lib/apparmor/profiles/click_com.ubuntu.music_music_1.3.638'
  2. sudo start apparmor ACTION=teardown
  3. sudo start apparmor
  start: Job failed to start
  4. sudo aa-status|egrep '^ '|grep -v '('| sort -u > /tmp/aa-status.music_bad
  5. sudo rm -f /var/lib/apparmor/profiles/click_com.ubuntu.music_music_1.3.638
  6. sudo aa-clickhook # regenerates the missing profile to had a good one
  7. sudo start apparmor ACTION=teardown
  8. sudo start apparmor
  9. sudo aa-status|egrep '^ '|grep -v '('| sort -u > /tmp/aa-status.music_good
  10. diff -Naur /tmp/aa-status.music_bad /tmp/aa-status.music_good
  --- /tmp/aa-status.music_bad  2014-10-03 22:47:52.890906744 +
  +++ /tmp/aa-status.music_good 2014-10-03 22:49:54.372739381 +
  @@ -13,6 +13,10 @@
  
com.ubuntu.developer.webapps.webapp-twitter_webapp-twitter_1.0.18//oxide_helper
  com.ubuntu.developer.webapps.webapp-twitter_webapp-twitter-helper_1.0.18
  com.ubuntu.dropping-letters_dropping-letters_0.1.2.2.66
  +   com.ubuntu.music_music_1.3.638
  +   com.ubuntu.shorts_shorts_0.2.330
  +   com.ubuntu.sudoku_sudoku_1.1.292
  +   com.ubuntu.weather_weather_1.1.374
  lxc-container-default
  lxc-container-default-with-mounting
  lxc-container-default-with-nesting

  Expected results: only com.ubuntu.music_music_1.3.638 should be
  missing.

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

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

[Touch-packages] [Bug 1375195] Re: webapp-container fails to inhibit screen blanking

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  webapp-container fails to inhibit screen blanking

Status in Webapps for Ubuntu Touch:
  New
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Won't Fix

Bug description:
  When watching a video in the youtube webapp, the screen eventually
  blanks while the video is playing. I’m seeing this in the app’s log:

  [0929/113347:ERROR:logging.h(739)] Failed to call method: 
com.canonical.Unity.Screen.keepDisplayOn: object_path= 
/com/canonical/Unity/Screen: org.freedesktop.DBus.Error.AccessDenied: An 
AppArmor policy prevents this sender from sending this message to this 
recipient, 0 matched rules; type="method_call", sender=":1.110" (uid=32011 
pid=11942 comm="webapp-container --webappUrlPatterns=https?://*.yo") 
interface="com.canonical.Unity.Screen" member="keepDisplayOn" error 
name="(unset)" requested_reply="0" destination="com.canonical.Unity.Screen" 
(uid=0 pid=2166 comm="unity-system-compositor --disable-overlays=false -")
  [0929/113347:ERROR:oxide_power_save_blocker.cc(109)] Failed to inhibit screen 
blanking

  Playing the same video in the webbrowser app does prevent the screen
  from blanking.

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-touch/+bug/1375195/+subscriptions

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

[Touch-packages] [Bug 1197134] Re: All SDK applications require access to /dev/binder

** Changed in: apparmor-easyprof-ubuntu (Ubuntu Utopic)
   Status: Triaged => Won't Fix

** Changed in: lxc-android-config (Ubuntu Utopic)
   Status: Confirmed => Won't Fix

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Importance: Undecided => High

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Status: Triaged => Confirmed

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

Title:
  All SDK applications require access to /dev/binder

Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Confirmed
Status in “lxc-android-config” package in Ubuntu:
  Confirmed
Status in “apparmor-easyprof-ubuntu” source package in Saucy:
  Won't Fix
Status in “lxc-android-config” source package in Saucy:
  Won't Fix
Status in “apparmor-easyprof-ubuntu” source package in Trusty:
  Won't Fix
Status in “lxc-android-config” source package in Trusty:
  Won't Fix
Status in “apparmor-easyprof-ubuntu” source package in Utopic:
  Won't Fix
Status in “lxc-android-config” source package in Utopic:
  Won't Fix

Bug description:
  SDK applications sometimes need the following AppArmor policy to run:

    /dev/binder rw,

  The writes to /dev/binder allow applications to attack binder directly
  which weakens our application confinement policy because there is no
  mediation between binder services.

  The following are the binder services that Ubuntu currently uses:
  - camera
  - media playback service (used by media-hub)

  location was in this group but is already moved away. surface flinger
  was used as a fallback but has been removed. vibrate is not
  implemented but when it is it will only use our API (ie, not binder).
  sensors was implemented as usensors in 14.10. Of the remaining binder
  services listed above, camera is still present for video recording and
  media playback service implements a subset of the android API for
  media playback (it is used by media-hub).

  This bug will be resolved when /dev/binder is no longer used or it is
  only used by one service and therefore the /dev/binder access can move
  into the appropriate policy group.

  Right now, because all apps needs access to /dev/binder, all apps end
  up with access to the camera and media playback services even when
  these policy groups are not specified. Getting rid of /dev/binder
  access is for fine-grained application confinement to work correctly.

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

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

[Touch-packages] [Bug 1378823] Re: apparmor denial for bind on name="org.freedesktop.Application"

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
Milestone: None => ubuntu-15.04

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

Title:
  apparmor denial for bind on name="org.freedesktop.Application"

Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Triaged
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Triaged

Bug description:
  apparmor="DENIED" operation="dbus_bind"  bus="session"
  name="org.freedesktop.Application" mask="bind" pid=NNN
  profile="com.ubuntu.gallery_gallery_2.9.1.1084"

  This looks to be similar to bug #1342129 and bug #1357371, but for the
  gallery. We won't be adding a rule to apparmor-easyprof-ubuntu to bind
  on org.freedesktop.Application because we can't mediate dbus message
  contents and adding this rule would mean apps could bind on each
  other's names. I'm not sure why the gallery app is doing this, but you
  may want to see the comments in bug 1342129 on how the webapps team
  solved this.

  Marking priority as Critical since this is likely representing broken
  functionality and ota-1 since it is unlikely it can be fixed in time
  for rtm. Please feel free to adjust.

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

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

[Touch-packages] [Bug 1385015] [NEW] adjust dbus policy to specify peer

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

Public bug reported:

Add 'peer=(label=unconfined)' to policy.

** Affects: apparmor-easyprof-ubuntu (Ubuntu)
 Importance: High
 Status: Triaged

** This bug has been marked a duplicate of bug 1383824
   add peer=(label=unconfined) to existing dbus rules

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

Title:
  adjust dbus policy to specify peer

Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Triaged

Bug description:
  Add 'peer=(label=unconfined)' to policy.

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

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

[Touch-packages] [Bug 1385013] [NEW] proper fix for apparmor mediation of lower (encrypted) filesystem

Public bug reported:

This is the proper fix for LP: #359338 which is needed for user data
encryption.

** Affects: apparmor (Ubuntu)
 Importance: Critical
 Status: New

** Affects: ecryptfs-utils (Ubuntu)
 Importance: Critical
 Status: New


** Tags: aa-kernel aa-policy ecryptfs-kernel

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

** Changed in: apparmor (Ubuntu)
   Importance: Undecided => Critical

** Changed in: ecryptfs-utils (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  proper fix for apparmor mediation of lower (encrypted) filesystem

Status in “apparmor” package in Ubuntu:
  New
Status in “ecryptfs-utils” package in Ubuntu:
  New

Bug description:
  This is the proper fix for LP: #359338 which is needed for user data
  encryption.

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

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

[Touch-packages] [Bug 1385010] [NEW] unexpected behavior: make_resolv_conf not undefined

2014-10-23 Thread Alan

Public bug reported:

The resolvconf package comes with /etc/dhcp/dhclient-enter-
hooks.d/resolvconf which convieniently undefines make_resolve_conf
(previously defined by dhclient-script) and calls resolvconf.

However, the hook checks if /etc/resolv.conf is a symlink even though
/sbin/resolvconf already handles this.

This is problematic because it never undefines the make_resolv_conf
function which dhclient-script defines itself.

For me, the expect behavior would be /etc/resolv.conf never changing if
resolvconf is installed and the file is not a symlink.

At the very least, I think this behavior should be documented in the man
pages for resolvconf.  Furthermore, debian does not implement this patch
and it exists starting in 12.04 until current.

As far as I can tell, there's absolutely no reason to check it twice if
resolvconf already implements it.

It was introduced by: http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/trusty/resolvconf/trusty/revision/32/etc/dhcp/dhclient-
enter-hooks.d/resolvconf

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

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

Title:
  unexpected behavior: make_resolv_conf not undefined

Status in “resolvconf” package in Ubuntu:
  New

Bug description:
  The resolvconf package comes with /etc/dhcp/dhclient-enter-
  hooks.d/resolvconf which convieniently undefines make_resolve_conf
  (previously defined by dhclient-script) and calls resolvconf.

  However, the hook checks if /etc/resolv.conf is a symlink even though
  /sbin/resolvconf already handles this.

  This is problematic because it never undefines the make_resolv_conf
  function which dhclient-script defines itself.

  For me, the expect behavior would be /etc/resolv.conf never changing
  if resolvconf is installed and the file is not a symlink.

  At the very least, I think this behavior should be documented in the
  man pages for resolvconf.  Furthermore, debian does not implement this
  patch and it exists starting in 12.04 until current.

  As far as I can tell, there's absolutely no reason to check it twice
  if resolvconf already implements it.

  It was introduced by: http://bazaar.launchpad.net/~ubuntu-
  branches/ubuntu/trusty/resolvconf/trusty/revision/32/etc/dhcp
  /dhclient-enter-hooks.d/resolvconf

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

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

[Touch-packages] [Bug 1379541] Re: Named sockets should use 'unix' rules instead of 'file'

** Tags added: aa-kernel aa-parser

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

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

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

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

Title:
  Named sockets should use 'unix' rules instead of 'file'

Status in AppArmor Linux application security framework:
  Triaged
Status in “apparmor” package in Ubuntu:
  Confirmed
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Move to unix rules for named sockets. This solves a number of issues
  surrounding getopt, setopt and listen and removes an inconsistency in
  our policy. needs abi bump

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

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

[Touch-packages] [Bug 1347321] Re: Inherited shadows in GtkPopover text cause readability problems

2014-10-23 Thread Jim Nelson

We're seeing a similar issue with Geary, which uses a progress bar in
the GtkHeaderBar to indicate index progress.  More information and
screenshot at https://bugzilla.gnome.org/show_bug.cgi?id=734309

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

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

Title:
  Inherited shadows in GtkPopover text cause readability problems

Status in California GNOME 3 Calendar:
  Confirmed
Status in Themes for Ubuntu:
  In Progress
Status in “ubuntu-themes” package in Ubuntu:
  Triaged

Bug description:
  I'm currently developing an application which uses GtkPopovers.  It
  works fine under GNOME Shell on Utopic 14.10 but under Unity text
  inside the popover is blurry.  I will attach screenshots indicating
  what I'm talking about.

  Oddly, the text inside a GtkButton displays fine.  It's the text
  labels elsewhere (GtkLabels, combo boxes, etc.) that are blurred.

To manage notifications about this bug go to:
https://bugs.launchpad.net/california-calendar/+bug/1347321/+subscriptions

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

[Touch-packages] [Bug 1369113] Re: Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

2014-10-23 Thread Pablo

got the same problem now with 14.10 official release.

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

Title:
  Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

Status in “steam” package in Ubuntu:
  Confirmed
Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  I am cross-posting this issue, which I reported to Valve's Source GIT
  issue tracker, because it was suggested that the regression may be due
  to Ubuntu Xorg changes rather than changes on the Steam end.

  Link: https://github.com/ValveSoftware/Source-1-Games/issues/1822


  Symptom --
  DoD:Source loads normally. But after a few minutes of playing (not a specific 
time as far as I can tell), the game freezes in place. A short clip (maybe a 
quarter of a second) of the last audio that played then repeats over and over 
on a loop. The process has to be killed manually with a QUIT or HUP signal for 
good measure. This is a new issue that just arose today.

  I have included system info, kernel log, and output when game is run
  from terminal and crashes.

  X info --
  X.Org X Server 1.16.0
  Release Date: 2014-07-16
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.2.0-61-generic x86_64 Ubuntu
  Current Operating System: Linux adam-x360-lin 3.16.0-14-generic #20-Ubuntu 
SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-14-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro drm.debug=0xe plymouth:debug
  Build Date: 10 September 2014  01:10:01PM
  xorg-server 2:1.16.0-1ubuntu1 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.32.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.

  
  System --

  OS: Ubuntu 14.10 (latest updates)
  Kernel: 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Model: HP Envy x360
  lspci:
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
  00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev 
e4)
  00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev 
e4)
  00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev 
e4)
  00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev 
e4)
  00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
  00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 AHCI 
mode
  00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI 
Express Card Reader (rev 01)
  08:00.0 Network controller: Intel Corporation Wireless 7260 (rev 9b)
  09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)


  Kernel log excerpt (from game start through crash end) --

  Sep 12 19:11:20 kernel: [ 4443.221907] [drm:i915_gem_open]
  Sep 12 19:11:20 kernel: [ 4443.266851] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
  Sep 12 19:11:21 kernel: [ .169675] [drm:i915_gem_context_destroy_ioctl] 
HW context 1 destroyed
  Sep 12 19:11:21 kernel: [ .486704] [drm:i915_gem_open]
  Sep 12 19:11:21 kernel: [ .550210] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
  Sep 12 19:11:25 kernel: [ 4447.852792] [drm:drm_mode_getconnector] 
[CONNECTOR:14:?]
  Sep 12 19:11:25 kernel: [ 4447.852796] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1]
  Sep 12 19:11:25 kernel: [ 4447.852800] [drm:intel_dp_detect] 
[CONNECTOR:14:eDP-1]
  Sep 12 19:11:25 kernel: [ 4447.852804] [drm:_edp_panel_vdd_on] Turning eDP 
VDD on
  Sep 12 19:11:25 kernel: [ 4447.852809] [drm:_edp_panel_vdd_on] PP_STATUS: 
0x8008 PP_CONTROL: 0xabcd000f
  Sep 12 19:11:25 kernel: [ 4447.853257] [drm:intel_dp_probe_oui] Sink OUI: 
00e04c
  Sep 12 19:11:25 kernel: [ 4447.853695] [drm:intel_dp_probe_oui] Branch OUI: 
00e04c
  Sep 12 19:11:25 kernel: [ 4447.853708] [drm:drm_edid_to_eld] ELD: no CEA 
Extension found
  Sep 12 19:11:25 kernel: [ 4447.853711] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1] 
probed modes :
  Sep 12 19:11:25 kernel: [ 4447.853715] [drm:drm_mode_debug_printmodeline] 
Modeline 15:"1920x1080"

[Touch-packages] [Bug 1384431] Re: libapparmor's aa_query_label() needs man page documentation

** Changed in: apparmor
   Importance: Medium => Low

** Changed in: apparmor (Ubuntu)
   Importance: Medium => Low

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

Title:
  libapparmor's aa_query_label() needs man page documentation

Status in AppArmor Linux application security framework:
  Triaged
Status in “apparmor” package in Ubuntu:
  Confirmed

Bug description:
  The aa_query_label() interface should be documented with a new man
  page.

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

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

[Touch-packages] [Bug 1381706] Re: Support file delegation for confined processes

** Tags added: aa-kernel

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

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

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

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

Title:
  Support file delegation for confined processes

Status in AppArmor Linux application security framework:
  Triaged
Status in “apparmor” package in Ubuntu:
  Confirmed

Bug description:
  Right now, delegation only works correctly for unconfined to
  [un]confined, we want to support delegation from one confined process
  to another:

  kernel support


  parser support


  tools support 


  man update


  testing (kernel, parser, tools)   


  policy update

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

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

[Touch-packages] [Bug 1381713] Re: Support policy query interface for file

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

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

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

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

Title:
  Support policy query interface for file

Status in AppArmor Linux application security framework:
  Triaged
Status in “apparmor” package in Ubuntu:
  Confirmed

Bug description:
  This bug tracks the work needed to support querying if a label can
  access a file. This is particularly useful with trusted helpers where
  an application requests access to a file and the trusted helper does
  something with it. For example, on Ubuntu when an app wants to play a
  music file, it (eventually) goes through the media-hub service. The
  media-hub service should be able to query if the app's policy has
  access to the file.

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

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

[Touch-packages] [Bug 1045081] Re: child Cx transition to grandchild transition silently fails, and child Px to sibling transition silently fails

** Tags added: aa-parser

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

Title:
  child Cx transition to grandchild transition silently fails, and child
  Px to sibling transition silently fails

Status in “apparmor” package in Ubuntu:
  Triaged

Bug description:
  I noticed that apparmor does not transition from a child to a
  grandchild. Eg:

  /tmp/foo {
    /tmp/bar Cx -> bar, # works

    profile bar {
  /tmp/baz Cx -> baz, # does not work

  profile baz {
  }
    }
  }

  The following child to a sibling also fails:
  /tmp/foo {
    /tmp/bar Cx -> bar, # works

    profile bar {
  /tmp/baz Px -> baz, # does not work
    }
    profile baz {
    }
  }

  Attached is a tarball that shows how transitions work for ix, px, px to an 
uncle, px to a sibling, and cx to a grandchild. Run it with:
  $ tar -zxf ./apparmor.tar.gz
  $ cd ./apparmor
  $ ./poc.sh
  = profile-ix =
  start
  foo
  bar
  baz
  pass

  = profile-px =
  start
  foo
  bar
  baz
  pass

  = profile-px-sibling =
  start
  foo
  /tmp/bug/bar: /tmp/bug/baz: /bin/sh: bad interpreter: No such file or 
directory
  FAIL

  = profile-px-uncle =
  start
  foo
  bar
  baz
  pass

  = profile-cx-grandchild =
  apparmor_parser: Unable to replace "baz".  Profile doesn't exist
  start
  foo
  /tmp/bug/bar: /tmp/bug/baz: /bin/sh: bad interpreter: No such file or 
directory
  FAIL

  Cleaning up
    removing profile-cx-grandchild
    removing profile-ix
    removing profile-px
    removing profile-px-sibling
    removing profile-px-uncle
  [1]
  $

  Also, these transitions fail silently (both at compile and runtime),
  which might be related to bug #1045074

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

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

[Touch-packages] [Bug 387657] Re: aa-logprof: doesn't handle large logs

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

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

Title:
  aa-logprof: doesn't handle large logs

Status in AppArmor Linux application security framework:
  Triaged
Status in “apparmor” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: apparmor

  Ubuntu 8.04.2
  Package: apparmor-utils
  Version: 2.1+1075-0ubuntu9.2

  My first experience with AppArmor was finding a kernel log file that
  was full of 800 MB of AppArmor warnings from Samba and CUPS. I'm not
  sure what suddenly enabled AppArmor on this LTS system, but while
  fixing the problem I noticed

  aa-logprof, while processing an 800 MB log file, drove the load
  average up into the high 40's. I suspect it was trying to load the
  whole thing into memory (on a system with 1 GB of RAM). I'd recommend
  revising the architecture so that it processes the lines as it sees
  them.

  I worked around the problem by splitting the file into a dozen 75MB
  chunks.

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

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

[Touch-packages] [Bug 316042] Re: Adding MinorFS package to ubuntu.

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

** Changed in: apparmor
   Status: New => Triaged

** Changed in: apparmor
   Importance: Undecided => Wishlist

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

Title:
  Adding MinorFS package to ubuntu.

Status in AppArmor Linux application security framework:
  Triaged
Status in “apparmor” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: apparmor

  MinorFs is a (capability based) discretionary access control extension to 
AppArmor implemented as a set of cooperating userspace (fuse) filesystems. The 
latest version (0.3.5) has a howto as to installation on ubuntu 8.10.
  MinorFs depends on a few cpan perl modules not currently packaged for ubuntu.
  I'm not sure if this is the right channel, but I (as the minorfs author) 
would like to work with an experienced ubuntu package maintainer on getting and 
keeping MinorFs packaged for ubuntu.

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

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

[Touch-packages] [Bug 692218] Re: add man page for pam_apparmor

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

** Changed in: apparmor
   Status: New => Triaged

** Changed in: apparmor
   Importance: Undecided => Low

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

Title:
  add man page for pam_apparmor

Status in AppArmor Linux application security framework:
  Triaged
Status in “apparmor” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: apparmor

  Please add a man page for pam_apparmor-- it only contains a README
  file which is too terse and doesn't give the overall picture on how to
  use pam_apparmor.

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

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

[Touch-packages] [Bug 1379538] Re: Better support for docker.io

** Tags added: aa-kernel

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

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

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

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

Title:
  Better support for docker.io

Status in AppArmor Linux application security framework:
  Triaged
Status in “apparmor” package in Ubuntu:
  Confirmed
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  This tracks the proper fix for bug #1371310.

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

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

[Touch-packages] [Bug 1370218] Re: Fine-grained shm mediation (confined applications need access to /run/shm/shmfd*)

** Tags added: aa-kernel

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

** Changed in: linux (Ubuntu)
   Status: New => Triaged

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

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

Title:
  Fine-grained shm mediation (confined applications need access to
  /run/shm/shmfd*)

Status in AppArmor Linux application security framework:
  Triaged
Status in “apparmor” package in Ubuntu:
  Confirmed
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Fix Released
Status in “linux” package in Ubuntu:
  Triaged
Status in “qtbase-opensource-src” package in Ubuntu:
  New
Status in “qtmultimedia-opensource-src” package in Ubuntu:
  New
Status in “apparmor-easyprof-ubuntu” package in Ubuntu RTM:
  Fix Released

Bug description:
  QAudioRecoder needed the following rules:
   owner /{run,dev}/shm/shmfd* rwk,

  but then it was discovered that confined apps on utopic also need:
   owner /{run,dev}/shm/shmfd* rwk,

  The rules are this way because the shared memory files are not app
  specific and is possible for one app to access another app's shared
  memory file. Please update qtbase-opensource-src so the files are app-
  specific to better isolation the apps (this is something we are doing
  elsewhere).

  Longer term we'd like to have shared memory file mediation in
  AppArmor.

  Original report:
  I recently wrote a small application[1] to spot an ancient issue I had using 
QAudioRecorder on Ubuntu devices.

  After I have installer gstreamer0.10-pulseaudio (otherwise "pulseaudio:" is 
not listed as available source), I tried to start a record through 
QAudioRecorder but it failed, giving me this output:
  "shm_open() failed: Permission denied"

  I've checked for some denials from apparmor (using 'dmesg | grep
  DEN'), but none was found.

  If I change the apparmor profile[2], so that my test application is
  launched in a unconfined environment, QAudioRecorder works properly as
  expected.

  I run this test on my Nexus 5 (utopic-devel-proposed #185), but this
  problem with shm happens also on i386 ubuntu-emulator (utopic-devel
  #206).

  Just for reference, this is the link to the original mail, stored in the 
ubuntu-phone team mailing list archive:
  http://lists.launchpad.net/ubuntu-phone/msg09842.html

  [1] - 
http://bazaar.launchpad.net/~verzegnassi-stefano/+junk/recorder-test/files
  [2]
  {
  "policy_version": 1.2,
  "template": "unconfined",
  "policy_groups": []
  }

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

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

[Touch-packages] [Bug 1379537] Re: Fine-grained kernel keyring mediation

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

** Changed in: linux (Ubuntu)
   Status: New => Triaged

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

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

** Tags added: aa-kernel

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

Title:
  Fine-grained kernel keyring mediation

Status in AppArmor Linux application security framework:
  Triaged
Status in “apparmor” package in Ubuntu:
  Confirmed
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Tracking bug to support fine-grained kernel keyring mediation.

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

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

[Touch-packages] [Bug 1339099] Re: AppArmor file permission 'append' denies file creation

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

** Changed in: apparmor
   Status: New => Confirmed

** Changed in: apparmor
   Importance: Undecided => Low

** Tags added: aa-kernel aa-parser

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

Title:
  AppArmor file permission 'append' denies file creation

Status in AppArmor Linux application security framework:
  Confirmed
Status in “apparmor” package in Ubuntu:
  Confirmed

Bug description:
  This bug started as a question, to make sure I know how to computer
  before filing a bug:
  https://answers.launchpad.net/ubuntu/+source/apparmor/+question/251315

  All this work is being done on an up-to-date 14.04 server running
  apparmor{-profiles,-utils} 2.8.95~2430-0ubuntu5.

  While trying to sort out the appropriate AppArmor bits to control
  logging, I'm seeing the file permission 'append' deny create access to
  a file, where I would have expected this to not be denied. It also
  denies 'file_perm', but it's unclear if this would be expected to
  work. I can fix the situation by updating the profile to use the
  'write' permission instead of 'append', but this is less than ideal.

  http://manpages.ubuntu.com/manpages/trusty/en/man5/apparmor.d.5.html
  indicates that the 'append' file permission "Allows the program to
  have a limited appending only write access to the file."

  In addition,
  http://wiki.apparmor.net/index.php/AppArmor_Core_Policy_Reference
  explicitly states that 'append' grants "permission to create, and
  extend a file. The append permission is limited that it only gives
  permission for applications to open a file with O_APPEND, it can not
  be used to enforce a generic file write is append only."

  From
  https://en.opensuse.org/Archive:AppArmor_2_3_changes#Minor_Semantic_Changes,
  it appears as though granting 'create' permissions to 'append' is new
  in AppArmor 2.3.

  However, in writing up a simple test program in Go, I'm seeing
  AppArmor deny create permissions where 'append' is allowed.

  The Go code:
  -
  func main() {
  logFile, err = os.OpenFile("/opt/test/log/test.log", 
os.O_WRONLY|os.O_CREATE|os.O_APPEND, 0644)
  n, err := logFile.WriteString("direct write\n")
  if err != nil {
  fmt.Println(n, err)
  }
  log.SetOutput(logFile)
  log.Println("Log file initialized.")
  logFile.Close()
  }
  -

  The AppArmor profile:
  -
  #include 

  /opt/test/bin/test {
#include 

/opt/test/log/test.log a,
  }
  -

  When set to enforce, the program spits out an error:
  -
  % /opt/test/bin/test
  0 invalid argument
  %
  -

  And AppArmor logs the DENIED message:
  -
  kernel: [ 5687.957758] type=1400 audit(1404743687.548:92): apparmor="DENIED" 
operation="open" profile="/opt/test/bin/test" name="/opt/test/log/test.log" 
pid=7766 comm="test" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
  -

  When set to complain, the program works as expected (as expected):
  -
  % /opt/test/bin/test
  %
  -

  And AppArmor logs three calls with which it has an issue:
  -
  kernel: [ 5949.505626] type=1400 audit(1404743948.872:98): apparmor="ALLOWED" 
operation="open" profile="/opt/test/bin/test" name="/opt/test/log/test.log" 
pid=8158 comm="test" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
  kernel: [ 5949.505643] type=1400 audit(1404743948.872:99): apparmor="ALLOWED" 
operation="file_perm" profile="/opt/test/bin/test" 
name="/opt/test/log/test.log" pid=8158 comm="test" requested_mask="w" 
denied_mask="w" fsuid=1000 ouid=1000
  kernel: [ 5949.505758] type=1400 audit(1404743948.872:100): 
apparmor="ALLOWED" operation="file_perm" profile="/opt/test/bin/test" 
name="/opt/test/log/test.log" pid=8158 comm="test" requested_mask="w" 
denied_mask="w" fsuid=1000 ouid=1000
  -

  I'm not sure what's going on with the 'file_perm' stuff either -- I
  thought that would have required 'chmod', but that doesn't appear to
  be the case.

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

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

[Touch-packages] [Bug 1315469] Re: apparmor_parser should reject pivot_root rules containing non-directory arguments

** Tags added: aa-parser

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

** Changed in: apparmor
   Status: New => Triaged

** Changed in: apparmor
   Importance: Undecided => Low

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

Title:
  apparmor_parser should reject pivot_root rules containing non-
  directory arguments

Status in AppArmor Linux application security framework:
  Triaged
Status in “apparmor” package in Ubuntu:
  Triaged

Bug description:
  The pivot_root rule arguments corresponding to pivot_root(2)'s put_old
  and new_root arguments must always end with a '/' character. This is
  due to the paths being directories and not regular files. If the paths
  do not end in a '/', the kernel will fail to match the paths during a
  pivot_root(2) and the pivot will always be denied.

  I think that the parser should reject all pivot_root rules containing
  paths that do not end in '/', to avoid the confusion at run-time.

  Here's a simple test case that should fail:

  $ echo "/t { pivot_root oldroot=/new/old /new, }" | apparmor_parser
  -qQ

  Here's a simple test case that should pass:

  $ echo "/t { pivot_root oldroot=/new/old/ /new/, }" | apparmor_parser
  -qQ

  Currently, both test result in apparmor_parser returning 0.

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

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

[Touch-packages] [Bug 1306781] Re: Kernel to userspace communication is needed to notify trusted helpers of profile changes

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

** Changed in: linux (Ubuntu)
   Status: New => Triaged

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

** Tags added: aa-kernel

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

Title:
  Kernel to userspace communication is needed to notify trusted helpers
  of profile changes

Status in AppArmor Linux application security framework:
  Triaged
Status in “apparmor” package in Ubuntu:
  Triaged
Status in “dbus” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  It is common for trusted helpers to cache information about a profile,
  such as the profile name and enforcement mode, when they're making
  AppArmor policy decisions. However, there's currently no way for the
  trusted helper to receive notification when changes are made to the
  profile.

  For example, dbus-daemon caches the profile name and enforcement mode
  when an application connects to the bus. If the profile is in enforce
  mode when the application connects but the system administrator moves
  the profile to complain mode, dbus-daemon does not find out about the
  change and continues to enforce the profile.

  The opposite is true, as well. If a profile is in complain mode when
  an application connects to the bus and is then moved to enforce mode,
  dbus-daemon continues to treat the profile as if it were in complain
  mode until the application reconnects to the bus.

  To solve this, there are two options that immediately come to mind:

1. dbus-daemon checks with the kernel before every permission query.
  It would get the latest profile information and then decide what to do
  (query and enforce if the profile is in enforce mode, query and allow
  if in complain mode, don't query if unconfined). This results in an
  extra round trip per query and would hurt performance.

2. The kernel could notify trusted helpers when profile changes are
  made, such as when an enforcement mode changes, a new profile is
  loaded, a profile is removed, a profile is renamed, etc. Userspace
  would need to be able to receive the notification and invalidate its
  cached information for that profile. This could become complicated in
  some trusted helper implementations.

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

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

[Touch-packages] [Bug 1350324] Re: Incorrect warning with ubuntu-scope-network template: Character - was quoted unnecessarily, dropped preceding quote ('\') character

** Tags added: aa-parser

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

** Changed in: apparmor
   Status: New => Confirmed

** Changed in: apparmor
   Importance: Undecided => Low

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

Title:
  Incorrect warning with ubuntu-scope-network template: Character - was
  quoted unnecessarily, dropped preceding quote ('\') character

Status in AppArmor Linux application security framework:
  Confirmed
Status in “apparmor” package in Ubuntu:
  Confirmed

Bug description:
  $ cat /tmp/profile 
  profile "foo" {
owner /run/user/[0-9]*/zmq/{[^c]**,c[^\-]**}-r  rw,
  }

  $ apparmor_parser -QTK /tmp/profile 
  Warning from /tmp/profile (/tmp/profile line 4): Character - was quoted 
unnecessarily, dropped preceding quote ('\') character

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

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

[Touch-packages] [Bug 1302735] Re: downgrade and not enforced rule messages

** Changed in: apparmor (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 apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1302735

Title:
  downgrade and not enforced rule messages

Status in “apparmor” package in Ubuntu:
  Fix Released

Bug description:
  Встановлення нової версії файлу налаштувань (install new version file 
setings) /etc/apparmor.d/abstractions/base ...
   * Starting AppArmor profiles 
   
Warning from profile /sbin/dhclient (/etc/apparmor.d/sbin.dhclient) ptrace 
rules not enforced
  Warning from profile /sbin/dhclient (/etc/apparmor.d/sbin.dhclient) signal 
rules not enforced
  Warning from profile /usr/lib/NetworkManager/nm-dhcp-client.action 
(/etc/apparmor.d/sbin.dhclient) ptrace rules not enforced
  Warning from profile /usr/lib/NetworkManager/nm-dhcp-client.action 
(/etc/apparmor.d/sbin.dhclient) signal rules not enforced
  Warning from profile /usr/lib/connman/scripts/dhclient-script 
(/etc/apparmor.d/sbin.dhclient) ptrace rules not enforced
  Warning from profile /usr/lib/connman/scripts/dhclient-script 
(/etc/apparmor.d/sbin.dhclient) signal rules not enforced
  Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
  Warning from profile /usr/lib/telepathy/mission-control-5 
(/etc/apparmor.d/usr.lib.telepathy) ptrace rules not enforced
  Warning from profile /usr/lib/telepathy/mission-control-5 
(/etc/apparmor.d/usr.lib.telepathy) signal rules not enforced
  Warning from profile /usr/lib/telepathy/telepathy-* 
(/etc/apparmor.d/usr.lib.telepathy) ptrace rules not enforced
  Warning from profile /usr/lib/telepathy/telepathy-* 
(/etc/apparmor.d/usr.lib.telepathy) signal rules not enforced
  Warning from profile pxgsettings (/etc/apparmor.d/usr.lib.telepathy) ptrace 
rules not enforced
  Warning from profile pxgsettings (/etc/apparmor.d/usr.lib.telepathy) signal 
rules not enforced
  Warning from profile sanitized_helper (/etc/apparmor.d/usr.lib.telepathy) 
ptrace rules not enforced
  Warning from profile sanitized_helper (/etc/apparmor.d/usr.lib.telepathy) 
signal rules not enforced
  Warning from profile /usr/lib/telepathy/telepathy-ofono 
(/etc/apparmor.d/usr.lib.telepathy) ptrace rules not enforced
  Warning from profile /usr/lib/telepathy/telepathy-ofono 
(/etc/apparmor.d/usr.lib.telepathy) signal rules not enforced
  Warning from profile /usr/sbin/cups-browsed 
(/etc/apparmor.d/usr.sbin.cups-browsed) ptrace rules not enforced
  Warning from profile /usr/sbin/cups-browsed 
(/etc/apparmor.d/usr.sbin.cups-browsed) signal rules not enforced
  Warning from profile /usr/lib/cups/backend/cups-pdf 
(/etc/apparmor.d/usr.sbin.cupsd) ptrace rules not enforced
  Warning from profile /usr/lib/cups/backend/cups-pdf 
(/etc/apparmor.d/usr.sbin.cupsd) signal rules not enforced
  Warning from profile /usr/sbin/cupsd (/etc/apparmor.d/usr.sbin.cupsd) ptrace 
rules not enforced
  Warning from profile /usr/sbin/cupsd (/etc/apparmor.d/usr.sbin.cupsd) signal 
rules not enforced
  Warning from profile /usr/sbin/mysqld (/etc/apparmor.d/usr.sbin.mysqld) 
ptrace rules not enforced
  Warning from profile /usr/sbin/mysqld (/etc/apparmor.d/usr.sbin.mysqld) 
signal rules not enforced
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
  Warning from profile /usr/bin/evince (/etc/apparmor.d/usr.bin.evince) ptrace 
rules not enforced
  Warning from profile /usr/bin/evince (/etc/apparmor.d/usr.bin.evince) signal 
rules not enforced
  Warning from profile /usr/sbin/tcpdump (/etc/apparmor.d/usr.sbin.tcpdump) 
ptrace rules not enforced
  Warning from profile /usr/sbin/tcpdump (/etc/apparmor.d/usr.sbin.tcpdump) 
signal rules not enforced
  Warning from profile sanitized_helper (/etc/apparmor.d/usr.bin.evince) ptrace 
rules not enforced
  Warning from profile sanitized_helper (/etc/apparmor.d/usr.bin.evince) signal 
rules not enforced
  Warning from profile /usr/bin/evince-previewer 
(/etc/apparmor.d/usr.bin.evince) ptrace rules not enforced
  Warning from profile /usr/bin/evince-previewer 
(/etc/apparmor.d/usr.bin.evince) signal rules not enforced
  Warning from profile sanitized_helper (/etc/apparmor.d/usr.bin.evince) ptrace 
rules not enforced
  Warning from profile sanitized_helper (/etc/apparmor.d/usr.bin.evince) signal 
rules not enforced
  Warning from profile /usr/bin/evince-thumbnailer 
(/etc/apparmor.d/usr.bin.evince) ptrace rules not enforced
  Warning from profile /usr/bin/evince-thumbnailer 
(/etc/apparmor.d/usr.bin.evince) signal rules not enforced
  Warning from profile sanitized_helper (/etc/apparmor.d/usr.bin.evince) ptrace 
rules not enforced
  Warning from profile sanitized_helper (/etc/apparmor.d/usr.bin.evince) signal 
rules not enforced

[Touch-packages] [Bug 1260090] Re: apparmor_parser complains about '.' and '"' in child profile names

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

** Tags added: aa-parser

** Changed in: apparmor
   Status: New => Triaged

** Changed in: apparmor
   Importance: Undecided => Low

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

Title:
  apparmor_parser complains about '.' and '"' in child profile names

Status in AppArmor Linux application security framework:
  Triaged
Status in “apparmor” package in Ubuntu:
  Triaged

Bug description:
  The following fails to compile:
  profile "com.ubuntu.developer.jdstrand.test-oxide_test-oxide_0.1" 
(attach_disconnected) {
/usr/lib/@{multiarch}/oxide-qt/chrome-sandbox cx -> chrome_sandbox,
/usr/lib/@{multiarch}/oxide-qt/oxide-renderer Cx -> oxide_renderer,

profile chrome_sandbox {
  /usr/lib/@{multiarch}/oxide-qt/oxide-renderer Px -> 
com.ubuntu.developer.jdstrand.test-oxide_test-oxide_0.1//oxide_renderer,
}

profile oxide_renderer { }
  }

  $ apparmor_parser -p /tmp/foo >/dev/null
  AppArmor parser error for /tmp/foo in /tmp/foo at line 6: Found unexpected 
character: '.'

  I can also quote the child profile like so:
profile chrome_sandbox {
  /usr/lib/@{multiarch}/oxide-qt/oxide-renderer Px -> 
"com.ubuntu.developer.jdstrand.test-oxide_test-oxide_0.1//oxide_renderer",
}

  $ apparmor_parser -p /tmp/bar >/dev/null
  AppArmor parser error for /tmp/bar in /tmp/bar at line 6: Found unexpected 
character: '"'

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

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

[Touch-packages] [Bug 1364630] Re: init: Error while reading from descriptor: Broken pipe

2014-10-23 Thread Kaspar Tint

Can confirm, this messes up my Plymouth splash also.

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

Title:
  init: Error while reading from descriptor: Broken pipe

Status in “init-system-helpers” package in Ubuntu:
  Confirmed

Bug description:
  [   16.934379] init: Error while reading from descriptor: Broken pipe

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: init 1.20ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1
  Uname: Linux 3.16.0-11-generic x86_64
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep  2 17:23:15 2014
  InstallationDate: Installed on 2014-04-27 (128 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: init-system-helpers
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1255424] Re: include of dir fails when the number of files in the dir approaches or exceeds the processes fd limit

** Tags added: aa-parser

** Changed in: apparmor
   Status: Confirmed => Triaged

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

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

Title:
  include of dir fails when the number of files in the dir approaches or
  exceeds the processes fd limit

Status in AppArmor Linux application security framework:
  Triaged
Status in “apparmor” package in Ubuntu:
  Triaged

Bug description:
  The apparmor parser handles directory includes in an odd way, where
  each file in the directory is opened and the pushed as a flex buffer
  state before any files in the directory are actually processed. The
  flex buffers and associated fds are then processed one by one and the
   handling pops the buffer (and closes the fd) to get to the next
  file to process.

  This means that if a directory contains a lot of files the include
  could fail as the parser will run out of available fds.

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

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

[Touch-packages] [Bug 1293439] Re: Apparmor prevents icedtea-7-plugin from creating necessary files

** Changed in: apparmor (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 apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1293439

Title:
  Apparmor prevents icedtea-7-plugin from creating necessary files

Status in “apparmor” package in Ubuntu:
  Fix Released

Bug description:
  Apparmor prevents icedtea-7-plugin from creating
  /run/user//icedteaplugin--/, needed to work:

  Mar 17 10:48:52 ad2 kernel: [2831863.964092] type=1400
  audit(1395046132.183:851): apparmor="DENIED" operation="mkdir"
  parent=6425 profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
  name="/run/user/1000/icedteaplugin-pseudo-7DURO0/" pid=30285 comm
  ="plugin-containe" requested_mask="c" denied_mask="c" fsuid=1000
  ouid=1000

  ~> lsb_release -rd
  Description:  Ubuntu 13.10
  Release:  13.10

  ~> apt-cache policy apparmor
  apparmor:
Installed: 2.8.0-0ubuntu31.1
Candidate: 2.8.0-0ubuntu31.1
Version table:
   *** 2.8.0-0ubuntu31.1 0
  500 http://archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.8.0-0ubuntu31 0
  500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: apparmor 2.8.0-0ubuntu31.1
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Mar 17 10:59:53 2014
  MarkForUpload: True
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=16001ea5-4e94-44ae-9838-da89b0f3f88e ro
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: Upgraded to saucy on 2013-09-10 (187 days ago)

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

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

[Touch-packages] [Bug 1384980] Re: mesa issue, crashed window appear from the installation process screen and first booting after fresh installation

2014-10-23 Thread Jung-Kyu Park

screenshot of case for Kubuntu 14.04


** Attachment added: "snapshot1(1).png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1384980/+attachment/4242778/+files/snapshot1%281%29.png

** Package changed: xorg (Ubuntu) => xserver-xorg-video-nouveau (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/1384980

Title:
  mesa issue, crashed window appear from the installation process screen
  and first booting after fresh installation

Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  New

Bug description:
  Kubuntu 14.04 and 14.10 have the same issue of mesa
  I think that it is the same issue with this report for Unity
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1232940

  whenever attempting to install Kubuntu 14.10 and kubuntu 14.04 ,and first 
booting after fresh installation
  it always occurs crashed or blurred windows in the screen  
  plesase see the screentshot

  I always remove xserver-xorg-video-nouveau on first booting both of the the 
installation process, after installation process
  and also installing nvidia-current works for it

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  CurrentDesktop: KDE
  Date: Fri Oct 24 08:32:06 2014
  InstallationDate: Installed on 2014-10-23 (0 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
  ProcEnviron:
   LANGUAGE=ko
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ko_KR.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1384980/+subscriptions

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

[Touch-packages] [Bug 1384980] [NEW] mesa issue, crashed window appear from the installation process screen and first booting after fresh installation

2014-10-23 Thread Jung-Kyu Park

Public bug reported:

Kubuntu 14.04 and 14.10 have the same issue of mesa
I think that it is the same issue with this report for Unity
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1232940

whenever attempting to install Kubuntu 14.10 and kubuntu 14.04 ,and first 
booting after fresh installation
it always occurs crashed or blurred windows in the screen  
plesase see the screentshot

I always remove xserver-xorg-video-nouveau on first booting both of the the 
installation process, after installation process
and also installing nvidia-current works for it

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8
Architecture: i386
CurrentDesktop: KDE
Date: Fri Oct 24 08:32:06 2014
InstallationDate: Installed on 2014-10-23 (0 days ago)
InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
ProcEnviron:
 LANGUAGE=ko
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ko_KR.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xserver-xorg-video-nouveau (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 kubuntu utopic

** Attachment added: "snapshot1.png"
   
https://bugs.launchpad.net/bugs/1384980/+attachment/4242776/+files/snapshot1.png

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

Title:
  mesa issue, crashed window appear from the installation process screen
  and first booting after fresh installation

Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  New

Bug description:
  Kubuntu 14.04 and 14.10 have the same issue of mesa
  I think that it is the same issue with this report for Unity
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1232940

  whenever attempting to install Kubuntu 14.10 and kubuntu 14.04 ,and first 
booting after fresh installation
  it always occurs crashed or blurred windows in the screen  
  plesase see the screentshot

  I always remove xserver-xorg-video-nouveau on first booting both of the the 
installation process, after installation process
  and also installing nvidia-current works for it

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  CurrentDesktop: KDE
  Date: Fri Oct 24 08:32:06 2014
  InstallationDate: Installed on 2014-10-23 (0 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
  ProcEnviron:
   LANGUAGE=ko
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ko_KR.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1384980/+subscriptions

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

[Touch-packages] [Bug 1191858] Re: Skype doesn't fully work in enforce mode

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

** Changed in: apparmor
   Status: New => Triaged

** Changed in: apparmor
   Importance: Undecided => Low

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

Title:
  Skype doesn't fully work in enforce mode

Status in AppArmor Linux application security framework:
  Triaged
Status in “apparmor” package in Ubuntu:
  Triaged

Bug description:
  When usr.bin.skype profile from apparmor-profiles package is enabled
  Skype doesn't fully work in enforce mode: changing the default
  location for downloaded files does not work. The file dialogue only
  allows to select my home folder but it does not show/list any folders
  (including hidden) inside it. The dialogue does not allow to create
  new folders to inside my home folder either. It should at least allow
  to select the Desktop and Downloads folders.

  In addition there are error messages that appear in kern.log when I
  login to Skype and make a test call but they don't seem to influence
  Skype's functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: apparmor 2.8.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
  Uname: Linux 3.8.0-23-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Mon Jun 17 16:22:47 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-05-23 (24 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-23-generic 
root=UUID=7a6374d8-dc25-4457-b7ba-b1929c574b73 ro persistent quiet splash 
vt.handoff=7
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1360303] Re: [SB-XFi - Creative X-Fi, playback] No automute when headphones are plugged in

2014-10-23 Thread Nick

Seems to be a regression in alsa support as alsamixer has no jack sense
toggle

This problem persists into 14.10

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

Title:
  [SB-XFi - Creative X-Fi, playback] No automute  when headphones are
  plugged in

Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 720.  fresh install 14.04 all updates.   10.04 was previous
  OS and did not have this problem.  plugging in headphones has no
  effect on the sound coming from the speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 22 10:41:50 2014
  InstallationDate: Installed on 2014-08-22 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Juniper HDMI Audio [Radeon HD 5700 Series] - HDA ATI HDMI
  Symptom_Type: No auto-mute between outputs
  Title: [SB-XFi - Creative X-Fi, playback] No automute
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0YU822
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd04/01/2008:svnDellInc.:pnDellXPS720:pvr:rvnDellInc.:rn0YU822:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Dell XPS720
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1192965] Re: user-mail abstraction refers to /var/spool/mail rather than /var/mail

This will be fixed in Ubuntu 15.04.

** Changed in: apparmor (Ubuntu)
Milestone: None => ubuntu-15.04

** Changed in: apparmor (Ubuntu)
 Assignee: (unassigned) => Steve Beattie (sbeattie)

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

Title:
  user-mail abstraction refers to /var/spool/mail rather than /var/mail

Status in “apparmor” package in Ubuntu:
  In Progress

Bug description:
  Nowadays /var/spool/mail is a symlink to /var/mail.

  /etc/apparmor.d/abstractions/user-mail should be updated to reflect
  this.

  Patch attached...

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

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

[Touch-packages] [Bug 1160569] Re: [regression] GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed

** Also affects: glib via
   https://bugzilla.gnome.org/show_bug.cgi?id=687763
   Importance: Unknown
   Status: Unknown

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

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

Title:
  [regression] GLib-CRITICAL **: g_slice_set_config: assertion
  `sys_page_size == 0' failed

Status in The Mozilla Firefox Browser:
  Confirmed
Status in The "G" Library - GLib:
  Unknown
Status in “apport” package in Ubuntu:
  Confirmed
Status in “firefox” package in Ubuntu:
  Triaged
Status in “thunderbird” package in Ubuntu:
  Triaged

Bug description:
  Have a look at the screen-shot for more details.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: firefox 19.0.2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.9.2-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20130308124351
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Channel: Unavailable
  Date: Tue Mar 26 21:48:57 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-03-26 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64+mac (20130326)
  IpRoute:
   default via 10.0.1.1 dev eth0  proto static
   10.0.1.0/24 dev eth0  proto kernel  scope link  src 10.0.1.16  metric 1
   169.254.0.0/16 dev eth0  scope link  metric 1000
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MarkForUpload: True
  Plugins:
   Windows Media Player Plug-in 10 (compatible; Videos) - 
/usr/lib/mozilla/plugins/libtotem-gmp-plugin.so (totem-mozilla)
   VLC Multimedia Plugin (compatible Videos 3.6.3) - 
/usr/lib/mozilla/plugins/libtotem-cone-plugin.so (totem-mozilla)
   DivX® Web Player - /usr/lib/mozilla/plugins/libtotem-mully-plugin.so 
(totem-mozilla)
   QuickTime Plug-in 7.6.6 - 
/usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so (totem-mozilla)
   iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=19.0.2/20130308124351
  RelatedPackageVersions:
   totem-mozilla 3.6.3-0ubuntu4
   rhythmbox-mozilla 2.98-0ubuntu3
  RfKill:

  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Touch-packages] [Bug 1384958] Re: "Ubuntu Desktop" title is moved right as the window buttons were there

** Attachment added: "Example of the wrong behavior"
   
https://bugs.launchpad.net/unity/+bug/1384958/+attachment/4242723/+files/Schermata%20da%202014-10-23%2018%3A09%3A04.png

** Description changed:

  1. Open a maximized window
  2. Hit Super+s
+ 3. The "Ubuntu Desktop" title is moved some pixels to the right, as shown in 
the attached screenshot

** Changed in: unity/7.2
   Importance: Undecided => Low

** Changed in: unity/7.2
   Status: New => In Progress

** Changed in: unity/7.2
Milestone: None => 7.2.3

** Changed in: unity/7.2
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

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

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  "Ubuntu Desktop" title is moved right as the window buttons were there

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  1. Open a maximized window
  2. Hit Super+s
  3. The "Ubuntu Desktop" title is moved some pixels to the right, as shown in 
the attached screenshot

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

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

[Touch-packages] [Bug 1379692] Re: unimplemented command "evaluate" in QtCreator's QML/JS console

** Also affects: ubuntu-ui-toolkit
   Importance: Undecided
   Status: New

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

Title:
  unimplemented command "evaluate" in QtCreator's QML/JS console

Status in Ubuntu UI Toolkit:
  New
Status in “qtdeclarative-opensource-src” package in Ubuntu:
  New

Bug description:
  With Qt 5, the QML/JS console in QtCreator is quite useless. It always
  displays 'unimplemented command "evaluate"'. I wonder how the Ubuntu
  Touch developers manage to debug their code under such conditions.
  This bug is reported upstream  and reported to be "fixed by
  6333e0913fc0078c0221a8909ced8df03a568992" in Qt 5.4. I suppose this is
  commit
  
.
  Could you please check if it is possible to backport this commit?

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

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

[Touch-packages] [Bug 1380683] Re: Web app requiring account, and "Online Accounts" account screen, disappear without explanation

2014-10-23 Thread David Barth

We were able to reproduce the issue on multiple devices during the
sprint. It prevents any account from being created and blocks the first
start of all webapps requiring an account, like: Facebook, Twitter and
Gmail.

The problem affects phones operating under difficult network conditions.
It can be observed on both makon and krillin.

** Tags added: touch-2014-10-30

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

Title:
  Web app requiring account, and "Online Accounts" account screen,
  disappear without explanation

Status in “qtbase-opensource-src” package in Ubuntu:
  Incomplete
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.10 r279

  1. Launch a Web app that requires an online account, e.g. Twitter or Facebook.
  2. Launch System Settings, and choose an account type.

  What happens:
  1. The app opens, shows an Online Accounts prompt with a spinner for a few 
seconds, then disappears.
  2. An account screen appears for a few seconds, then you're returned to 
Online Accounts.

  What should happen:
  1. You see the sign-in page.
  2. You see the sign-in page.

  [Originally reported by Patricia Davila.]

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

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

[Touch-packages] [Bug 1372254] Re: New Event in Calendar app not scheduled for the correct time zone.

2014-10-23 Thread Charles Kerr

** Attachment added: "Eeet werks!"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1372254/+attachment/4242722/+files/2014-10-23%2017.59.19.jpg

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

Title:
  New Event in Calendar app not scheduled for the correct time zone.

Status in Calendar application for Ubuntu devices:
  Confirmed
Status in “indicator-datetime” package in Ubuntu:
  Invalid

Bug description:
  Phone - LGE Nexus 4
  OS Version - Ubuntu 14.10 (r48)
  Time zone - America/Los Angeles - UTC-7
  Steps to reproduce: 
  Calendar view is for the month.
  1 - select 'New Event' in the calendar app
  2 - enter event information, set the date as the current date (21-Sep-2014)
  3 - enter a start time = 21:30
  4 - enter an end time = 22:30
  5 - use 'Personal' calendar
  6 - save the event
  An event is created for 'Tomorrow at 4:30 am', not 21:30 for the current date

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

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

[Touch-packages] [Bug 1380683] Re: Web app requiring account, and "Online Accounts" account screen, disappear without explanation

I only understand certain keywords I notice in the comments, but I
wonder if bug #1357321 has anything to do with this?

This could be a good bug to test against Qt 5.3.2. You can update your
device by adding https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/landing-015 to it and dist-upgrading (note: it's
Ubuntu PPA so you can easily only test by upgrading from utopic image,
since otherwise not all versions of eg unity8 would be correct).

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Web app requiring account, and "Online Accounts" account screen,
  disappear without explanation

Status in “qtbase-opensource-src” package in Ubuntu:
  Incomplete
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.10 r279

  1. Launch a Web app that requires an online account, e.g. Twitter or Facebook.
  2. Launch System Settings, and choose an account type.

  What happens:
  1. The app opens, shows an Online Accounts prompt with a spinner for a few 
seconds, then disappears.
  2. An account screen appears for a few seconds, then you're returned to 
Online Accounts.

  What should happen:
  1. You see the sign-in page.
  2. You see the sign-in page.

  [Originally reported by Patricia Davila.]

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

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

[Touch-packages] [Bug 1377418] Re: Touch events are ignored

This didn't now get worked before utopic release. I plan to release
5.3.2 to vivid quite soon, and you can already test it on utopic by
adding the following PPA: https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/landing-015. In the current 5.3.2 packaging just
the upstream code is used as is.

ppa-purge tool can be used to revert later.

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

Title:
Touch events are ignored

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

Bug description:
On Kubuntu 14.10 running Qt 5.3.0 (from the regular repository) touch
events are ignored in Qt 5 based applications. It works fine when I
run an application against Qt 5.3.2, see QTBUG-38625 and qtbase change
id I30d36397aa4ff2fb7a8ad2bbb94c2a13abd472b4.

Qt 4 applications work fine (however, they just emulate a mouse event
afaics), Chrome is fine (if you manually tell it the xinput device
id), but Qt 5 applications don't handle touch events. I can scroll
through, for example systemsettings, with two fingers, but "clicking"
is not possible. The mouse moves and the button is hovered but never
actually triggered. It affects both QML-based applications (like
Plasmashell) as well as traditional widget-based apps.

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

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

[Touch-packages] [Bug 1380683] Re: Web app requiring account, and "Online Accounts" account screen, disappear without explanation

2014-10-23 Thread David Barth

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

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Confirmed

** Changed in: qtbase-opensource-src (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
   Importance: Undecided => High

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

Title:
  Web app requiring account, and "Online Accounts" account screen,
  disappear without explanation

Status in “qtbase-opensource-src” package in Ubuntu:
  Incomplete
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.10 r279

  1. Launch a Web app that requires an online account, e.g. Twitter or Facebook.
  2. Launch System Settings, and choose an account type.

  What happens:
  1. The app opens, shows an Online Accounts prompt with a spinner for a few 
seconds, then disappears.
  2. An account screen appears for a few seconds, then you're returned to 
Online Accounts.

  What should happen:
  1. You see the sign-in page.
  2. You see the sign-in page.

  [Originally reported by Patricia Davila.]

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

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

[Touch-packages] [Bug 1372254] Re: New Event in Calendar app not scheduled for the correct time zone.

2014-10-23 Thread Charles Kerr

I've just re-run the previous test with Renatu's
https://code.launchpad.net/~renatofilho/qtorganizer5-eds/fix-1311165
branch and it does indeed seem to fix this problem.

That branch has already been merged but hasn't landed yet.

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

Title:
  New Event in Calendar app not scheduled for the correct time zone.

Status in Calendar application for Ubuntu devices:
  Confirmed
Status in “indicator-datetime” package in Ubuntu:
  Invalid

Bug description:
  Phone - LGE Nexus 4
  OS Version - Ubuntu 14.10 (r48)
  Time zone - America/Los Angeles - UTC-7
  Steps to reproduce: 
  Calendar view is for the month.
  1 - select 'New Event' in the calendar app
  2 - enter event information, set the date as the current date (21-Sep-2014)
  3 - enter a start time = 21:30
  4 - enter an end time = 22:30
  5 - use 'Personal' calendar
  6 - save the event
  An event is created for 'Tomorrow at 4:30 am', not 21:30 for the current date

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

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

[Touch-packages] [Bug 1384942] Re: qt5-qmake reports that it could not exec qt4 qmake

Hi. Please use one of the following options:
1. Use qmake -qt5
2. Install qt5-default package
3. Add environment variable: export QT_SELECT=qt5

The fallback to the (possibly installed) Qt 4 version is by design in
qtchooser in case none of the above is in use.

I'll mark the bug as "Invalid". Not that the problem wouldn't be valid,
but because it's working as intended by the qtchooser tool. See 'man
qtchooser' for details.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Invalid

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

Title:
  qt5-qmake reports that it could not exec qt4 qmake

Status in “qtbase-opensource-src” package in Ubuntu:
  Invalid

Bug description:
  When installing only qt5-qmake (which has no dependency on qt4-qmake
  as far as I can tell), it shows:

  qmake ubuntu 14.04 qmake: could not exec '/usr/lib/x86_64-linux-
  gnu/qt4/bin/qmake': No such file or directory

  When I install qt4-qmake it runs, but then it runs qt4 qmake.

  I only want to have qt5 qmake (or at least be able to only run that).

  My workaround is to create a soft link from /usr/lib/x86_64-linux-
  gnu/qt4/bin/qmake to '/usr/lib/x86_64-linux-gnu/qt5/bin/qmake, but
  that's not a proper solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: qt5-qmake 5.2.1+dfsg-1ubuntu14.2
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct 23 23:19:27 2014
  InstallationDate: Installed on 2013-03-13 (588 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (186 days ago)

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

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

[Touch-packages] [Bug 1381041] Re: Network indicator is sometimes blank

2014-10-23 Thread Antti Kaijanmäki

OK, after getting a partial log, I saw a lot of dbus timeouts on i-network side.
The attached branches fix these issues and prevent i-network from hitting the 
upstart respawn limit.

** Branch linked: lp:~unity-api-team/indicator-network/increase-dbus-
timeouts

** Branch linked: lp:~jpakkane/indicator-network/quickexit

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

Title:
  Network indicator is sometimes blank

Status in “indicator-network” package in Ubuntu:
  In Progress
Status in “indicator-network” package in Ubuntu RTM:
  In Progress

Bug description:
  This is on krillin r103, but it has been happening for a while.

  See attached photo. I am not certain what triggers it. but I think it
  may happen when wifi APs become in and out of range while walking
  around town (as if the list does not refresh reliably).

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

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

[Touch-packages] [Bug 1384419] Re: com.canonical.UnityGreeter.HideGreeter defeats password requirement

2014-10-23 Thread Seth Arnold

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

Thanks Michael and Christian; the intention is that connecting via adb
will require the screen to be unlocked.

Thanks

** This bug has been marked a duplicate of bug 1382559
   adbd does not check the screen state before allowing a connection

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

Title:
  com.canonical.UnityGreeter.HideGreeter defeats password requirement

Status in “unity8” package in Ubuntu:
  Incomplete

Bug description:
  I have enabled developer mode in my phone(s). I'm required to have a
  password to enable developer mode. However, it's still possible to
  call com.canonical.UnityGreeter.HideGreete via adb to unlock without
  the password. This to me seems to defeat the purpose of the
  requirement of the password.

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

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

[Touch-packages] [Bug 1384942] Re: qt5-qmake reports that it could not exec qt4 qmake

I agree that it's a problem that could have a better upstream solution
or error output, but that's what we currently have.

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

Title:
  qt5-qmake reports that it could not exec qt4 qmake

Status in “qtbase-opensource-src” package in Ubuntu:
  Invalid

Bug description:
  When installing only qt5-qmake (which has no dependency on qt4-qmake
  as far as I can tell), it shows:

  qmake ubuntu 14.04 qmake: could not exec '/usr/lib/x86_64-linux-
  gnu/qt4/bin/qmake': No such file or directory

  When I install qt4-qmake it runs, but then it runs qt4 qmake.

  I only want to have qt5 qmake (or at least be able to only run that).

  My workaround is to create a soft link from /usr/lib/x86_64-linux-
  gnu/qt4/bin/qmake to '/usr/lib/x86_64-linux-gnu/qt5/bin/qmake, but
  that's not a proper solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: qt5-qmake 5.2.1+dfsg-1ubuntu14.2
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct 23 23:19:27 2014
  InstallationDate: Installed on 2013-03-13 (588 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (186 days ago)

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

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

[Touch-packages] [Bug 1382559] Re: adbd does not check the screen state before allowing a connection

2014-10-23 Thread Marc Deslauriers

** Information type changed from Public to Public Security

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

Title:
  adbd does not check the screen state before allowing a connection

Status in “android-tools” package in Ubuntu:
  Confirmed

Bug description:
  according to
  https://wiki.ubuntu.com/SecurityAndPrivacySettings/ProtectingUserData
  adbd should only allow a connection attempt to succeed when teh screen
  is unlocked. adbd currently does not do this and needs to be fixed.

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

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

[Touch-packages] [Bug 1379777] Re: [Dash] Allow applications to specify the orientations supported

2014-10-23 Thread Gerry Boland

Just found https://bugs.launchpad.net/mir/+bug/1382209 "[Enhancement] Add an 
API to lock surface orientation"
so a UX decision would help clarify what we really need

** Summary changed:

- [Dash] Allow applications to specify the orientations supported
+ Allow applications to specify the orientations supported

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

Title:
  Allow applications to specify the orientations supported

Status in Qt integration with the Mir display server:
  New
Status in Ubuntu UI Toolkit:
  Triaged
Status in Ubuntu UX bugs:
  Triaged
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  Currently unity8 shell has a partial implementation of orientation
  support. It trusts applications to rotate their own contents, if they
  want to. The shell doesn't reposition the panel (at the top) though,
  so a landscape app still has a portrait panel on the side.

  For proper orientation support in the shell, shell needs to know if
  the application wants to rotate its contents or not. To animate
  correctly, we really need shell to be responsible for rotating the app
  surface, not the app itself.

  Therefore an application needs to tell shell what orientations it
  supports, so shell can respect its wishes.

  A hint in the desktop file may be sufficient.

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

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

[Touch-packages] [Bug 1355173] Re: Switching windows with a Trusted Prompt Session active loses the trusted prompt session

Adding tasks for all the affected parties: to fix this, we will not
terminate the trusted sessions on unfocus any more. Your trusted helper
needs to decide what to do (do nothing, close, close after a timeout,
close when another session opened etc.).

Caveat is that we need to make sure it's clear whether it's unfocused
because the whole application got unfocused, or because there was
another prompt open on top (an idea is to use the active property of the
app).

Note that we also have bug #1384950 in store for the future, when
trusted helpers will have to adjust behaviour as well.

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

Title:
  Switching windows with a Trusted Prompt Session active loses the
  trusted prompt session

Status in Qt integration with the Mir display server:
  Triaged
Status in Online Accounts setup for Ubuntu Touch:
  Confirmed
Status in “pay-service” package in Ubuntu:
  New
Status in “trust-store” package in Ubuntu:
  New
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  
  When we create a trusted prompt session over an application, let's say a 
small dialog, and then switch applications, when we switch back to the original 
application the dialog is not overlayed on top of the original application. The 
program providing the dialog seems happy, and is still running, but visually it 
is not there.

  We notice this when using the payments UI which overlays ontop of the
  dash. In some cases we need to show Online Accounts which runs as an
  independent application and causes a switching behavior. When
  returning back to the dash the Payment UI is not visible. It also
  happens if the Payment UI is visible and you switch applications using
  the right swipe.

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

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

[Touch-packages] [Bug 1384952] [NEW] USB Soundcard no microphone (input) device

2014-10-23 Thread Alper Gürel

Public bug reported:

My Asus Xonar U7 Echelon External sound device working without input/capture 
device.
No input device , Nothing recording with my usb soundcard. 

~$ arecord -l
 List of CAPTURE Hardware Devices 
card 1: Ed [Xonar U7 Echelon Ed.], device 1: USB Audio [USB Audio #1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

~$ lsusb
Bus 002 Device 002: ID 1043:85c1 iCreate Technologies Corp.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
Uname: Linux 3.17.1-031701-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  alper  2249 F pulseaudio
 /dev/snd/pcmC1D0p:   alper  2249 F...m pulseaudio
 /dev/snd/controlC1:  alper  2249 F pulseaudio
CurrentDesktop: Unity
Date: Fri Oct 24 00:46:11 2014
InstallationDate: Installed on 2014-10-07 (16 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageArchitecture: all
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/04/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 970A-G46 (MS-7693)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.2:bd02/04/2013:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0:
dmi.product.name: MS-7693
dmi.product.version: 2.0
dmi.sys.vendor: MSI
modified.conffile..etc.modprobe.d.alsa.base.conf: [modified]
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-10-23T19:38:42.156766

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


** Tags: amd64 apport-bug trusty

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

Title:
  USB Soundcard no microphone (input) device

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  My Asus Xonar U7 Echelon External sound device working without input/capture 
device.
  No input device , Nothing recording with my usb soundcard. 

  ~$ arecord -l
   List of CAPTURE Hardware Devices 
  card 1: Ed [Xonar U7 Echelon Ed.], device 1: USB Audio [USB Audio #1]
Subdevices: 1/1
Subdevice #0: subdevice #0

  ~$ lsusb
  Bus 002 Device 002: ID 1043:85c1 iCreate Technologies Corp.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  Uname: Linux 3.17.1-031701-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alper  2249 F pulseaudio
   /dev/snd/pcmC1D0p:   alper  2249 F...m pulseaudio
   /dev/snd/controlC1:  alper  2249 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Oct 24 00:46:11 2014
  InstallationDate: Installed on 2014-10-07 (16 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-G46 (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.2:bd02/04/2013:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7693
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.modprobe.d.alsa.base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-10-23T19:38:42.156766

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

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

[Touch-packages] [Bug 1384950] [NEW] Trusted prompts need to be part of the lifecycle

Public bug reported:

After we fix bug #1355173, we'll be "leaking" trusted prompts in the
sense that when an app gets unfocused (and potentially killed
subsequently), the trusted prompts will be left running, not suspended
with the app. We should apply the same rules to the whole app container
(can we use ual? add the prompts to the pgroup/cgroup?).

This needs an escape route, too, for trusted helpers to be able to kill
prompts as they need to.

** Affects: pay-service (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: trust-store (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: ubuntu-system-settings-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: unity8 (Ubuntu)
 Importance: Medium
 Assignee: Nick Dedekind (nick-dedekind)
 Status: Triaged

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

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Nick Dedekind (nick-dedekind)

** Also affects: trust-store (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-system-settings-online-accounts (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: pay-service (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Trusted prompts need to be part of the lifecycle

Status in “pay-service” package in Ubuntu:
  New
Status in “trust-store” package in Ubuntu:
  New
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  After we fix bug #1355173, we'll be "leaking" trusted prompts in the
  sense that when an app gets unfocused (and potentially killed
  subsequently), the trusted prompts will be left running, not suspended
  with the app. We should apply the same rules to the whole app
  container (can we use ual? add the prompts to the pgroup/cgroup?).

  This needs an escape route, too, for trusted helpers to be able to
  kill prompts as they need to.

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

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

[Touch-packages] [Bug 1355173] Re: Switching windows with a Trusted Prompt Session active loses the trusted prompt session

** Also affects: trust-store (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: pay-service (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-system-settings-online-accounts
   Status: Fix Released => Confirmed

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  Switching windows with a Trusted Prompt Session active loses the
  trusted prompt session

Status in Qt integration with the Mir display server:
  Triaged
Status in Online Accounts setup for Ubuntu Touch:
  Confirmed
Status in “pay-service” package in Ubuntu:
  New
Status in “trust-store” package in Ubuntu:
  New
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  
  When we create a trusted prompt session over an application, let's say a 
small dialog, and then switch applications, when we switch back to the original 
application the dialog is not overlayed on top of the original application. The 
program providing the dialog seems happy, and is still running, but visually it 
is not there.

  We notice this when using the payments UI which overlays ontop of the
  dash. In some cases we need to show Online Accounts which runs as an
  independent application and causes a switching behavior. When
  returning back to the dash the Payment UI is not visible. It also
  happens if the Payment UI is visible and you switch applications using
  the right swipe.

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

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

[Touch-packages] [Bug 1379777] Re: [Dash] Allow applications to specify the orientations supported

2014-10-23 Thread Gerry Boland

For iteration 1, the SDK team team agreed that setting the supported
orientation in a desktop file hint is sufficient. Should we need more
granularity, we can create an API for applications to set it themselves.
But the lack of an existing API in Qt's QScreen class means that API
would be custom to the UITK.

Awaiting UX decision

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

Title:
  [Dash] Allow applications to specify the orientations supported

Status in Qt integration with the Mir display server:
  New
Status in Ubuntu UI Toolkit:
  Triaged
Status in Ubuntu UX bugs:
  Triaged
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  Currently unity8 shell has a partial implementation of orientation
  support. It trusts applications to rotate their own contents, if they
  want to. The shell doesn't reposition the panel (at the top) though,
  so a landscape app still has a portrait panel on the side.

  For proper orientation support in the shell, shell needs to know if
  the application wants to rotate its contents or not. To animate
  correctly, we really need shell to be responsible for rotating the app
  surface, not the app itself.

  Therefore an application needs to tell shell what orientations it
  supports, so shell can respect its wishes.

  A hint in the desktop file may be sufficient.

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

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

[Touch-packages] [Bug 1382595] Re: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Asser

2014-10-23 Thread Antti Kaijanmäki

i-network needs a rebuild as well.

** Changed in: indicator-network (Ubuntu)
   Status: Invalid => Triaged

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

Title:
  [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-
  network-service:indicator-network-service: pthread_mutex_lock.c:80:
  __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed.

Status in DBus C++:
  Confirmed
Status in “dbus-cpp” package in Ubuntu:
  Confirmed
Status in “indicator-network” package in Ubuntu:
  Triaged
Status in “location-service” package in Ubuntu:
  Confirmed
Status in “dbus-cpp” package in Ubuntu RTM:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding indicator-network.  This problem was most recently seen with
  version 0.5.1+14.10.20141015-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/ecc14b5d54f3e0a0f1720cad0c623f81c8a16988
  contains more details.

  steps to reproduce: (need to trigger race condition)
  1. pull down network indicator
  2. toggle flight mode on and off quickly a few times
  3. click sim card 1 and 2
  4. toggle flight mode
  5. swipe up close indicators
  6. repeat steps 1-5 until crash occurs

  expected results:
  no crash happens

  actual results:
  Bluetooth indicator blinks (appear and disappear) in indicator bar at top of 
screen, and network indicator crashes. 

  additional info:
  eventually the bluetooth indicator appears stable in the indicators at the 
top of the screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus-cpp/+bug/1382595/+subscriptions

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

[Touch-packages] [Bug 1381041] Re: Network indicator is sometimes blank

2014-10-23 Thread Antti Kaijanmäki

** Changed in: indicator-network (Ubuntu)
   Status: Incomplete => In Progress

** Branch linked: lp:~thomas-voss/dbus-cpp/fix-1361642

** Branch linked: lp:~thomas-voss/dbus-cpp/robustify-against-dead-
objects-hanging-around

** Also affects: indicator-network (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: indicator-network (Ubuntu RTM)
   Importance: Undecided => Critical

** Changed in: indicator-network (Ubuntu RTM)
   Status: New => In Progress

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

Title:
  Network indicator is sometimes blank

Status in “indicator-network” package in Ubuntu:
  In Progress
Status in “indicator-network” package in Ubuntu RTM:
  In Progress

Bug description:
  This is on krillin r103, but it has been happening for a while.

  See attached photo. I am not certain what triggers it. but I think it
  may happen when wifi APs become in and out of range while walking
  around town (as if the list does not refresh reliably).

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

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

[Touch-packages] [Bug 1384910] Re: Switching maximized windows using the spread might lead to wrong title and positioning

** Changed in: unity/7.2
   Importance: Undecided => Medium

** Changed in: unity/7.2
   Status: New => In Progress

** Changed in: unity/7.2
Milestone: None => 7.2.3

** Changed in: unity/7.2
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

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

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Switching maximized windows using the spread might lead to wrong title
  and positioning

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  1. Open at least two maximized windows
  2. Select one of the windows (last opened seems better)
  3. Hit Super + W
  4. Start writing to select the other(s) window opened
  5. Select it, hitting enter.

  The title will be wrong (the one of the previous title) while the
  window buttons will be in the wrong position (see attached sreenshot,
  in LIM mode, or empty panel otherwise).

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

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

[Touch-packages] [Bug 1368688] Re: Inconsistence between /etc/init and /etc/init.d files

2014-10-23 Thread Joi Ellis

I just upgraded a 12.04 to 14.04.1 and discovered my server now boots
three instances of dhcpd, one with -6, which dies because there is no
config file for it, and two instances of -4, one reading from
/etc/dhcp/dhcpd.conf, and the other from /etc/dhcp3/dhcpd.conf.

>From my reading, it appears the Sys V script should now be following the
format described in the page
https://wiki.ubuntu.com/UpstartCompatibleInitScripts (Upstart Compatible
Init Scripts) IE it should be testing for is_upstart_job in the case
actions, but it is not doing so.

Also note that the Upstart script is ignoring the information in
/etc/default/isc-dhcp-server, and providing its own locations for things
like the conf file and the pid file.  It should be honoring the defaults
file!

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

Title:
  Inconsistence between /etc/init and /etc/init.d files

Status in “isc-dhcp” package in Ubuntu:
  Confirmed

Bug description:
  After upgrade Ubuntu server from 12.04 LTS to 14.04 LTS (with 
do-release-upgrade) I found a strange behavior in /var/log/messages from 
isc-dhcp-server. It had doubled DHCPREQUESTS/OFFERS/ACKs... It was like:
  ~~
  dhcpd: DHCPDISCOVER from 00:0b:82:27:be:d1 via eth0
  dhcpd: DHCPDISCOVER from 00:0b:82:27:be:d1 via eth0
  DHCPREQUEST for 192.168.1.102 (10.112.1.252) from 00:0b:82:27:be:d1 via eth0
  DHCPREQUEST for 192.168.1.102 (10.112.1.252) from 00:0b:82:27:be:d1 via eth0
  DHCPACK on 192.168.1.102 to 00:0b:82:27:be:d1 via eth0
  DHCPACK on 192.168.1.102 to 00:0b:82:27:be:d1 via eth0
  ~~

  Futher investigation show that there was actually two dhcpd processes:
  ~~
  dhcpd -q -cf /etc/dhcp/dhcpd.conf -pf /var/run/dhcp-server/dhcpd.pid
  /usr/sbin/dhcpd -q -cf /etc/dhcp/dhcpd.conf -pf /var/run/dhcpd.pid
  ~~

  The first one was executed from "/etc/init/isc-dhcp-server.conf" and second 
from "/etc/init.d/isc-dhcp-server".
  Looking inside "init/isc-dhcp-server.conf" I found:
  ~~
  respawn
  script
     . /etc/default/isc-dhcp-server
    ..
   exec dhcpd -user dhcpd -group dhcpd -f -q -4 -pf /run/dhcp-server/dhcpd.pid 
-cf $CONFIG_FILE $INTERFACES
  ~~

  As you can see path to PID file is hardcoded.

  But in "init.d/isc-dhcp-server" startup script:
  ~~
  # try to read pid file name from config file, with fallback to 
/var/run/dhcpd.pid
  if [ -z "$DHCPD_PID" ]; then
  DHCPD_PID=$(sed -n -e 's/^[ \t]*pid-file-name[ \t]*"(.*)"[ 
\t]*;.*$/\1/p' < "$DHCPD_CONF" 2>/dev/null | head -n 1)
  fi
  DHCPD_PID="${DHCPD_PID:-/var/run/dhcpd.pid}"
    ..
  case "$1" in
  start)
  test_config
  log_daemon_msg "Starting $DESC" "$NAME"
  start-stop-daemon --start --quiet --pidfile "$DHCPD_PID" \
  --exec /usr/sbin/dhcpd -- \
  -q $OPTIONS -cf "$DHCPD_CONF" -pf "$DHCPD_PID" 
$INTERFACES
  ~~

  
  So obivous is to either change init script to NOT use hardcoded path to PID 
file and use $DHCP_PID (from /etc/default/isc-dhcp-server, which is sourced 
inside this script), or at least change it to "default" one: /var/run/dhcpd.pid

  OR

  change init.d script to fallback to "/run/dhcp-server/dhcpd.pid"
  instead of "/var/run/dhcpd.pid"

  P.S. /var/run is a link to /run

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

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

[Touch-packages] [Bug 1372254] Re: New Event in Calendar app not scheduled for the correct time zone.

2014-10-23 Thread Charles Kerr

To test this, I created a calendar event for tomorrow (Fri Oct 24) going from 
4:55 PM (16:55) to 5:55 PM (17:55).
My timezone: America/New York (UTC-4).

Given this setup and set of inputs, calendar-app creats this entry in
~/.local/share/evolution/calendar/system/calendar.ics:

BEGIN:VCALENDAR
CALSCALE:GREGORIAN
PRODID:-//Ximian//NONSGML Evolution Calendar//EN
VERSION:2.0
X-EVOLUTION-DATA-REVISION:2014-10-23T20:54:03.819474Z(0)
BEGIN:VEVENT
UID:20141023T205403Z-16928-32011-1353-1@ubuntu-phablet
DTSTAMP:20141023T205403Z
DTSTART:20141024T205500
DTEND:20141024T215500
X-LIC-ERROR;X-LIC-ERRORTYPE=VALUE-PARSE-ERROR:Can't parse as RECUR value
 in RRULE property. Removing entire property: ERROR: No Value
SUMMARY:Some event
DESCRIPTION:Description
CREATED:20141023T205403Z
LAST-MODIFIED:20141023T205403Z
BEGIN:VALARM
X-EVOLUTION-ALARM-UID:20141023T205403Z-16928-32011-1353-2@ubuntu-phablet
ACTION:AUDIO
TRIGGER;VALUE=DURATION;RELATED=START:-P1D
REPEAT:3
DURATION:PT2M
END:VALARM
BEGIN:VALARM
X-EVOLUTION-ALARM-UID:20141023T205403Z-16928-32011-1353-3@ubuntu-phablet
ACTION:DISPLAY
DESCRIPTION:Some event
TRIGGER;VALUE=DURATION;RELATED=START:-P1D
REPEAT:3
DURATION:PT2M
END:VALARM
END:VEVENT
END:VCALENDAR

DTSTART is set to "20141024T205500", which is a 'floating' value not
bound to any particular timezone -- that is, it should fire 20:55:00 no
matter which time zone the user is in.

indicator-datetime shows this as:

"Tomorrow 8:55 PM"

which is the correct rendering (on 2014-10-23) for an event which starts
at 20141024T205500.

In summary:

- Since clock-app's "New Event" form doesn't contain a timezone chooser, 
clock-app is correct to store DTSTART, DTEND as floating dates.
- calendar-app appears to have a bug that converts the date's value to UTC 
before saving it as a local time.
- since calendar-app still shows the date & time as matching the user's input 
even after calendar-app restarts, it must also have the same bug in reverse 
when loading events from EDS.
- 

** Changed in: indicator-datetime (Ubuntu)
   Status: New => Invalid

** Changed in: ubuntu-calendar-app
   Status: Invalid => Confirmed

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

Title:
  New Event in Calendar app not scheduled for the correct time zone.

Status in Calendar application for Ubuntu devices:
  Confirmed
Status in “indicator-datetime” package in Ubuntu:
  Invalid

Bug description:
  Phone - LGE Nexus 4
  OS Version - Ubuntu 14.10 (r48)
  Time zone - America/Los Angeles - UTC-7
  Steps to reproduce: 
  Calendar view is for the month.
  1 - select 'New Event' in the calendar app
  2 - enter event information, set the date as the current date (21-Sep-2014)
  3 - enter a start time = 21:30
  4 - enter an end time = 22:30
  5 - use 'Personal' calendar
  6 - save the event
  An event is created for 'Tomorrow at 4:30 am', not 21:30 for the current date

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

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

[Touch-packages] [Bug 1384941] [NEW] Incoming SMS while on a phone call turns screen on

2014-10-23 Thread Tony Espy

Public bug reported:

While testing krillin RTM image #120 I noticed that if an incoming SMS
is received while on the phone, and the phone is held to your ear, the
incoming SMS will cause the screen to come on.

** Affects: powerd (Ubuntu)
 Importance: High
 Status: New


** Tags: rtm14

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

** Tags added: rtm14

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

Title:
  Incoming SMS while on a phone call turns screen on

Status in “powerd” package in Ubuntu:
  New

Bug description:
  While testing krillin RTM image #120 I noticed that if an incoming SMS
  is received while on the phone, and the phone is held to your ear, the
  incoming SMS will cause the screen to come on.

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

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

[Touch-packages] [Bug 1384942] [NEW] qt5-qmake reports that it could not exec qt4 qmake

2014-10-23 Thread dah bien-hwa

Public bug reported:

When installing only qt5-qmake (which has no dependency on qt4-qmake as
far as I can tell), it shows:

qmake ubuntu 14.04 qmake: could not exec '/usr/lib/x86_64-linux-
gnu/qt4/bin/qmake': No such file or directory

When I install qt4-qmake it runs, but then it runs qt4 qmake.

I only want to have qt5 qmake (or at least be able to only run that).

My workaround is to create a soft link from /usr/lib/x86_64-linux-
gnu/qt4/bin/qmake to '/usr/lib/x86_64-linux-gnu/qt5/bin/qmake, but
that's not a proper solution.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: qt5-qmake 5.2.1+dfsg-1ubuntu14.2
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Oct 23 23:19:27 2014
InstallationDate: Installed on 2013-03-13 (588 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
SourcePackage: qtbase-opensource-src
UpgradeStatus: Upgraded to trusty on 2014-04-20 (186 days ago)

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


** Tags: amd64 apport-bug trusty

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

Title:
  qt5-qmake reports that it could not exec qt4 qmake

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

Bug description:
  When installing only qt5-qmake (which has no dependency on qt4-qmake
  as far as I can tell), it shows:

  qmake ubuntu 14.04 qmake: could not exec '/usr/lib/x86_64-linux-
  gnu/qt4/bin/qmake': No such file or directory

  When I install qt4-qmake it runs, but then it runs qt4 qmake.

  I only want to have qt5 qmake (or at least be able to only run that).

  My workaround is to create a soft link from /usr/lib/x86_64-linux-
  gnu/qt4/bin/qmake to '/usr/lib/x86_64-linux-gnu/qt5/bin/qmake, but
  that's not a proper solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: qt5-qmake 5.2.1+dfsg-1ubuntu14.2
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct 23 23:19:27 2014
  InstallationDate: Installed on 2013-03-13 (588 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (186 days ago)

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

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

[Touch-packages] [Bug 1384776] Re: Occasional hang in unity 8 dash on the phone

2014-10-23 Thread Lorn Potter

QNAM uses QtBearer, which means those are handled by the NetworkManager
backend, which I am currently trying to fix up.

There are two ways of diserning online status with QtNetwork.

1) QNetworkConfigurationManager has isOnline() method, this can be done
on the defaultConfiguration().

2) QNetworkConfigurationManager has allConfigurations which can take an 
argument of 
QNetworkConfiguration::Active which will give a list of all active (online) 
configurations.

Both of which are a bit heavy if only being used for discovering online
status.

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

Title:
  Occasional hang in unity 8 dash on the phone

Status in “network-manager” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  The dash is sometimes hanging on the phone.

  See the attached backtrace.

  The issue is as follows: we are maintaining a client-side tree of all
  NetworkManager devices.  When we see that a new device has been added,
  we query its properties in order to build our local proxy.  Doing this
  means that we are making QtDBus calls from a signal handler.  Due to a
  bug in QtDBus this is not safe.

  libdbus-1 has a recursive lock on its DBusConnection.  When the signal
  arrives, the lock is acquired and the sginal handler is run.  The
  signal handler can make DBus calls (which also require the lock)
  because the lock is recursive.  QtDBus also has a lock that is always
  acquired before the libdbus-1 connection lock is acquired.

  Unfortuntaely, the QtDBus lock is not acquired in the case of the
  incoming call from DBus -- only the DBus lock is.

  
  If another thread tries to do an unrelated DBus call meanwhile, it will 
acquire the QtDBus lock first and then the DBus lock (which is held because of 
the signal that arrived).  Once the signal handler gets to the point of wanting 
to make a DBus call (in order to query the properties of the just-added network 
device) it will attempt to acquire the QtDBus lock.  This is a lock-inversion 
deadlock.

  There are at least three bugs here:

  1) QtDBus should be fixed in order to avoid this sort of lock
  inversion problem.  Even if we fix this one situation, it seems quite
  likely that issues like this will arise again.

  2) QNetworkManager should avoid the issue in QtDBus until such a time
  as it is fixed.  This could be done by dispatching to a worker thread
  on receipt of signals so that the queries are done in a fresh call
  stack (without the libdbus-1 lock held).

  3) Apparently the only reason we are using NetworkManager at all is in
  order to know if we are on a 3G connection or not (in order to avoid
  too much data charges).  This would be much easier to do if
  NetworkManager provided a property that we could watch directly
  instead of bringing up an entire tree of objects in order to answer a
  very simple question.  To that end I've filed
  https://bugzilla.gnome.org/show_bug.cgi?id=739080 which we can
  hopefully get addressed relatively quickly.

  
  I consider 3) to be the real fix as far as we are concerned, but we should 
probably ensure that the Qt people know about 1) and 2).  Either of those could 
function as a workaround for us in the meantime, but the idea that we are 
creating this complex object tree to answer a simple question is ridiculous, so 
we should really fix that directly.

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

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

[Touch-packages] [Bug 1384930] Re: package linux-image-3.16.0-23-generic 3.16.0-23.31 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2014-10-23 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-3.16.0-23-generic 3.16.0-23.31 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in “initramfs-tools” package in Ubuntu:
  New

Bug description:
  After upgrade from 14.04 I restarted laptop and noticed that I am still 
running 3.13 kernel.
  Then tried 
  sudo apt-get -V install linux-generic linux-image-generic 
linux-headers-generic

  ... and end up here

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-23-generic 3.16.0-23.31
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  palo   2937 F pulseaudio
   /dev/snd/pcmC1D0p:   palo   2937 F...m pulseaudio
   /dev/snd/controlC0:  palo   2937 F pulseaudio
  Date: Thu Oct 23 21:55:10 2014
  DuplicateSignature: 
package:linux-image-3.16.0-23-generic:3.16.0-23.31:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=3554a881-b5dc-4afb-8ef7-9a6e316cc195
  InstallationDate: Installed on 2014-05-16 (160 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP ProBook 6465b
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic 
root=UUID=1df998fd-1e25-4da5-8cfa-9cbaee2a9ee7 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-15
  SourcePackage: initramfs-tools
  Title: package linux-image-3.16.0-23-generic 3.16.0-23.31 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to utopic on 2014-10-23 (0 days ago)
  dmi.bios.date: 07/27/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68LTU Ver. F.03
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1633
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 03.18
  dmi.chassis.asset.tag: CNU1432MJM
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68LTUVer.F.03:bd07/27/2011:svnHewlett-Packard:pnHPProBook6465b:pvrA0001C02:rvnHewlett-Packard:rn1633:rvrKBCVersion03.18:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 6465b
  dmi.product.version: A0001C02
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1384776] Re: Occasional hang in unity 8 dash on the phone

2014-10-23 Thread Albert Astals Cid

I would like to find who is creating those dbus connections to
networkmanager. There are two candidates:

 a) QNetworkConfigurationManager used in src/CachingNetworkManagerFactory.cpp
 b) NetworkingStatus.limitedBandwith used in plugins/Dash/CardCreator.js

If it is only a) and not b) we should switch
src/CachingNetworkManagerFactory.cpp use over to
ubuntu::connectivity::NetworkingStatus that also has the hability to
provide wheter if we are online or not

Of course the original Qt bug should be still fixed so that other people
don't step on that problem.

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

Title:
  Occasional hang in unity 8 dash on the phone

Status in “network-manager” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  The dash is sometimes hanging on the phone.

  See the attached backtrace.

  The issue is as follows: we are maintaining a client-side tree of all
  NetworkManager devices.  When we see that a new device has been added,
  we query its properties in order to build our local proxy.  Doing this
  means that we are making QtDBus calls from a signal handler.  Due to a
  bug in QtDBus this is not safe.

  libdbus-1 has a recursive lock on its DBusConnection.  When the signal
  arrives, the lock is acquired and the sginal handler is run.  The
  signal handler can make DBus calls (which also require the lock)
  because the lock is recursive.  QtDBus also has a lock that is always
  acquired before the libdbus-1 connection lock is acquired.

  Unfortuntaely, the QtDBus lock is not acquired in the case of the
  incoming call from DBus -- only the DBus lock is.

  
  If another thread tries to do an unrelated DBus call meanwhile, it will 
acquire the QtDBus lock first and then the DBus lock (which is held because of 
the signal that arrived).  Once the signal handler gets to the point of wanting 
to make a DBus call (in order to query the properties of the just-added network 
device) it will attempt to acquire the QtDBus lock.  This is a lock-inversion 
deadlock.

  There are at least three bugs here:

  1) QtDBus should be fixed in order to avoid this sort of lock
  inversion problem.  Even if we fix this one situation, it seems quite
  likely that issues like this will arise again.

  2) QNetworkManager should avoid the issue in QtDBus until such a time
  as it is fixed.  This could be done by dispatching to a worker thread
  on receipt of signals so that the queries are done in a fresh call
  stack (without the libdbus-1 lock held).

  3) Apparently the only reason we are using NetworkManager at all is in
  order to know if we are on a 3G connection or not (in order to avoid
  too much data charges).  This would be much easier to do if
  NetworkManager provided a property that we could watch directly
  instead of bringing up an entire tree of objects in order to answer a
  very simple question.  To that end I've filed
  https://bugzilla.gnome.org/show_bug.cgi?id=739080 which we can
  hopefully get addressed relatively quickly.

  
  I consider 3) to be the real fix as far as we are concerned, but we should 
probably ensure that the Qt people know about 1) and 2).  Either of those could 
function as a workaround for us in the meantime, but the idea that we are 
creating this complex object tree to answer a simple question is ridiculous, so 
we should really fix that directly.

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

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

[Touch-packages] [Bug 1384930] [NEW] package linux-image-3.16.0-23-generic 3.16.0-23.31 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2014-10-23 Thread Pavol Celuch

Public bug reported:

After upgrade from 14.04 I restarted laptop and noticed that I am still running 
3.13 kernel.
Then tried 
sudo apt-get -V install linux-generic linux-image-generic linux-headers-generic

... and end up here

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-23-generic 3.16.0-23.31
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  palo   2937 F pulseaudio
 /dev/snd/pcmC1D0p:   palo   2937 F...m pulseaudio
 /dev/snd/controlC0:  palo   2937 F pulseaudio
Date: Thu Oct 23 21:55:10 2014
DuplicateSignature: 
package:linux-image-3.16.0-23-generic:3.16.0-23.31:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=3554a881-b5dc-4afb-8ef7-9a6e316cc195
InstallationDate: Installed on 2014-05-16 (160 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Hewlett-Packard HP ProBook 6465b
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic 
root=UUID=1df998fd-1e25-4da5-8cfa-9cbaee2a9ee7 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-15
SourcePackage: initramfs-tools
Title: package linux-image-3.16.0-23-generic 3.16.0-23.31 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to utopic on 2014-10-23 (0 days ago)
dmi.bios.date: 07/27/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68LTU Ver. F.03
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1633
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 03.18
dmi.chassis.asset.tag: CNU1432MJM
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68LTUVer.F.03:bd07/27/2011:svnHewlett-Packard:pnHPProBook6465b:pvrA0001C02:rvnHewlett-Packard:rn1633:rvrKBCVersion03.18:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 6465b
dmi.product.version: A0001C02
dmi.sys.vendor: Hewlett-Packard

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package utopic

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

Title:
  package linux-image-3.16.0-23-generic 3.16.0-23.31 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in “initramfs-tools” package in Ubuntu:
  New

Bug description:
  After upgrade from 14.04 I restarted laptop and noticed that I am still 
running 3.13 kernel.
  Then tried 
  sudo apt-get -V install linux-generic linux-image-generic 
linux-headers-generic

  ... and end up here

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-23-generic 3.16.0-23.31
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  palo   2937 F pulseaudio
   /dev/snd/pcmC1D0p:   palo   2937 F...m pulseaudio
   /dev/snd/controlC0:  palo   2937 F pulseaudio
  Date: Thu Oct 23 21:55:10 2014
  DuplicateSignature: 
package:linux-image-3.16.0-23-generic:3.16.0-23.31:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=3554a881-b5dc-4afb-8ef7-9a6e316cc195
  InstallationDate: Installed on 2014-05-16 (160 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP ProBook 6465b
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic 
root=UUID=1df998fd-1e25-4da5-8cfa-9cbaee2a9ee7 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-15
  SourcePackage: initramfs-tools
  Title: package linux-image-3.16.0-23-generic 3.16.0-23.31 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to utopic on 2014-10-23 (0 days ago)
  dmi.bios.date: 07/27/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68LTU Ver. F.03
  dmi.board.asset.tag: Base Board

[Touch-packages] [Bug 1384776] Re: Occasional hang in unity 8 dash on the phone

2014-10-23 Thread John McAleely

@mathieu - I've just duped #1381500, which we saw in the dogfooding of
krillin often enough not to reject as a one-off. Do its logs match the
data above? I took a quick look, and couldn't find data I could directly
compare. I don't know what I'm looking for though.

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

Title:
  Occasional hang in unity 8 dash on the phone

Status in “network-manager” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  The dash is sometimes hanging on the phone.

  See the attached backtrace.

  The issue is as follows: we are maintaining a client-side tree of all
  NetworkManager devices.  When we see that a new device has been added,
  we query its properties in order to build our local proxy.  Doing this
  means that we are making QtDBus calls from a signal handler.  Due to a
  bug in QtDBus this is not safe.

  libdbus-1 has a recursive lock on its DBusConnection.  When the signal
  arrives, the lock is acquired and the sginal handler is run.  The
  signal handler can make DBus calls (which also require the lock)
  because the lock is recursive.  QtDBus also has a lock that is always
  acquired before the libdbus-1 connection lock is acquired.

  Unfortuntaely, the QtDBus lock is not acquired in the case of the
  incoming call from DBus -- only the DBus lock is.

  
  If another thread tries to do an unrelated DBus call meanwhile, it will 
acquire the QtDBus lock first and then the DBus lock (which is held because of 
the signal that arrived).  Once the signal handler gets to the point of wanting 
to make a DBus call (in order to query the properties of the just-added network 
device) it will attempt to acquire the QtDBus lock.  This is a lock-inversion 
deadlock.

  There are at least three bugs here:

  1) QtDBus should be fixed in order to avoid this sort of lock
  inversion problem.  Even if we fix this one situation, it seems quite
  likely that issues like this will arise again.

  2) QNetworkManager should avoid the issue in QtDBus until such a time
  as it is fixed.  This could be done by dispatching to a worker thread
  on receipt of signals so that the queries are done in a fresh call
  stack (without the libdbus-1 lock held).

  3) Apparently the only reason we are using NetworkManager at all is in
  order to know if we are on a 3G connection or not (in order to avoid
  too much data charges).  This would be much easier to do if
  NetworkManager provided a property that we could watch directly
  instead of bringing up an entire tree of objects in order to answer a
  very simple question.  To that end I've filed
  https://bugzilla.gnome.org/show_bug.cgi?id=739080 which we can
  hopefully get addressed relatively quickly.

  
  I consider 3) to be the real fix as far as we are concerned, but we should 
probably ensure that the Qt people know about 1) and 2).  Either of those could 
function as a workaround for us in the meantime, but the idea that we are 
creating this complex object tree to answer a simple question is ridiculous, so 
we should really fix that directly.

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

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

[Touch-packages] [Bug 1336715] Re: switch-items in indicators sometimes get out of sync with system-settings

** Branch linked: lp:~nick-dedekind/ubuntu-system-
settings/lp1336715.check.sync

** Branch linked: lp:~nick-dedekind/ubuntu-settings-
components/lp1336715.check.sync

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

Title:
  switch-items in indicators sometimes get out of sync with system-
  settings

Status in Display Indicator:
  Invalid
Status in Indicator Location:
  Invalid
Status in Network Menu:
  Invalid
Status in Sound Menu:
  Invalid
Status in “ubuntu-system-settings” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  I noticed when testing flightmode with indicator-network that the
  switch items sometimes get out of sync from what GActions states on
  dbus are and stop updating their states when action states on dbus
  change.

  This seems to happen randomly and I have no procedure to reproduce
  reliably.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-display/+bug/1336715/+subscriptions

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

[Touch-packages] [Bug 1372973] Re: [Call]There should be a audible feedback(e.g beep) when the caller hangs up first

2014-10-23 Thread Bill Filler

The screen needs to turn on as well when the call ends so user knows
when the phone is removed from ear

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

** Changed in: powerd
   Status: New => In Progress

** Changed in: powerd
   Importance: Undecided => High

** Changed in: powerd
 Assignee: (unassigned) => Michael Frey (mfrey)

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

Title:
  [Call]There should be a audible feedback(e.g beep) when the caller
  hangs up first

Status in Dialer app for Ubuntu Touch:
  Invalid
Status in PowerD:
  In Progress
Status in Telephony Service:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “dialer-app” package in Ubuntu:
  Invalid
Status in “powerd” package in Ubuntu:
  New
Status in “telephony-service” package in Ubuntu:
  New
Status in “telephony-service” package in Ubuntu RTM:
  New

Bug description:
  [Procedures]
  1.there is a voice call
  2.the other party hangs up first
  3.the conversation view exit automatically

  [Expect results]
  There should be a audible feedback (e.g beeps) when the conversation view 
exit automatically

  [Actual results]
  Nothing

  [Reproduce]
  Always

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

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

[Touch-packages] [Bug 1372973] Re: [Call]There should be a audible feedback(e.g beep) when the caller hangs up first

** Branch linked: lp:~mfrey/powerd/display-fix

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

Title:
  [Call]There should be a audible feedback(e.g beep) when the caller
  hangs up first

Status in Dialer app for Ubuntu Touch:
  Invalid
Status in PowerD:
  In Progress
Status in Telephony Service:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “dialer-app” package in Ubuntu:
  Invalid
Status in “powerd” package in Ubuntu:
  New
Status in “telephony-service” package in Ubuntu:
  New
Status in “telephony-service” package in Ubuntu RTM:
  New

Bug description:
  [Procedures]
  1.there is a voice call
  2.the other party hangs up first
  3.the conversation view exit automatically

  [Expect results]
  There should be a audible feedback (e.g beeps) when the conversation view 
exit automatically

  [Actual results]
  Nothing

  [Reproduce]
  Always

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

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

[Touch-packages] [Bug 1358760] Re: Sync installed apps with store on departments change

2014-10-23 Thread James Tait

This API will be part of the click-metadata API, which is used by
ubuntu-system-settings/system-update plugin. This is being moved to
Click Package Index to support filtering of updates based on the
device's available frameworks and architecture, in the same way package
searches are filtered. The first part of this work has landed in CPI,
but still needs to be rolled out.

The next step in enabling the department updates is to return packages'
department in that response so that the store scope can make any
adjustments necessary.

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

Title:
  Sync installed apps with store on departments change

Status in Click Package metadata search service:
  Confirmed
Status in “unity-scope-click” package in Ubuntu:
  New

Bug description:
  The relationship between installed apps and their departments need to
  be updated when departments change on the server. Ubuntu store server
  will implement a new API call to get department ids for installed apps
  (list of apps will be send with the request), and we should make the
  call whenever we see changes in the departments tree returned by
  initial bootstrap call.

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-package-index/+bug/1358760/+subscriptions

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

[Touch-packages] [Bug 1358760] Re: Sync installed apps with store on departments change

2014-10-23 Thread James Tait

** Also affects: unity-scope-click
   Importance: Undecided
   Status: New

** Project changed: unity-scope-click => click-package-index

** Changed in: click-package-index
   Importance: Undecided => Medium

** Changed in: click-package-index
   Status: New => Confirmed

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

Title:
  Sync installed apps with store on departments change

Status in Click Package metadata search service:
  Confirmed
Status in “unity-scope-click” package in Ubuntu:
  New

Bug description:
  The relationship between installed apps and their departments need to
  be updated when departments change on the server. Ubuntu store server
  will implement a new API call to get department ids for installed apps
  (list of apps will be send with the request), and we should make the
  call whenever we see changes in the departments tree returned by
  initial bootstrap call.

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-package-index/+bug/1358760/+subscriptions

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

[Touch-packages] [Bug 1376443] Re: Default ACL not inherited as Access ACL on copy and move

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

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

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

Title:
  Default ACL not inherited as Access ACL on copy and move

Status in “coreutils” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Desktop 14.04 fresh default installation
  Default ACL and gid are set OK on parent folder (/srv/parent). (ext4)
  mkdir child /srv/parent
  and
  touch /srv/parent/file /srv/parent/child/file
  OK Both /srv/parent/file, /srv/parent/child/,  /srv/parent/child/file show 
correct same acl as /srv/parent (getfacl)

  cp -r /media///SomeTree ends in corrupted ACL where Access ACL 
mask::--- instead of rwx, resulting in acl set for named users and groups are 
ineffective. KO
  Although, default:mask::rwx is ok.

  For regular (i.e. non dir) files in the copied SomeTree,  Access ACL
  mask::r-- instead of rwx, resulting in only r out of the set
  permissions for named users and groups will survive. KO

  setfacl --set or -m reports no error

  Workaround : grant permissions to users that would not have them, eg.
  o+rX or adduser reader writersgroup

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

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

[Touch-packages] [Bug 1380683] Re: Web app requiring account, and "Online Accounts" account screen, disappear without explanation

2014-10-23 Thread Alberto Mardegan

** Attachment added: "Test application"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1380683/+attachment/4242660/+files/test.tar.gz

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

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

Title:
  Web app requiring account, and "Online Accounts" account screen,
  disappear without explanation

Status in “qtbase-opensource-src” package in Ubuntu:
  New
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
  New

Bug description:
  Ubuntu 14.10 r279

  1. Launch a Web app that requires an online account, e.g. Twitter or Facebook.
  2. Launch System Settings, and choose an account type.

  What happens:
  1. The app opens, shows an Online Accounts prompt with a spinner for a few 
seconds, then disappears.
  2. An account screen appears for a few seconds, then you're returned to 
Online Accounts.

  What should happen:
  1. You see the sign-in page.
  2. You see the sign-in page.

  [Originally reported by Patricia Davila.]

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

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

[Touch-packages] [Bug 1380683] Re: Web app requiring account, and "Online Accounts" account screen, disappear without explanation

2014-10-23 Thread Alberto Mardegan

This is a very interesting bug. It happened on David's device as well,
and I could finally debug the situation.

The problem is that constructing a QNetworkAccessManager takes 10
seconds.

I'm attaching a trace log (with timestamp, and 256 bytes of string data)
which is taken from a minimal test application.

** Attachment added: "strace.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1380683/+attachment/4242659/+files/strace.log

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

Title:
  Web app requiring account, and "Online Accounts" account screen,
  disappear without explanation

Status in “qtbase-opensource-src” package in Ubuntu:
  New
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
  New

Bug description:
  Ubuntu 14.10 r279

  1. Launch a Web app that requires an online account, e.g. Twitter or Facebook.
  2. Launch System Settings, and choose an account type.

  What happens:
  1. The app opens, shows an Online Accounts prompt with a spinner for a few 
seconds, then disappears.
  2. An account screen appears for a few seconds, then you're returned to 
Online Accounts.

  What should happen:
  1. You see the sign-in page.
  2. You see the sign-in page.

  [Originally reported by Patricia Davila.]

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

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

[Touch-packages] [Bug 1384776] Re: Occasional hang in unity 8 dash on the phone

2014-10-23 Thread Ryan Lortie

The patch already went upstream in NetworkManager and now we have an
Ubuntu package landing soon.

The upshot is that we now have a simple DBus property:

  system
  org.freedesktop.NetworkManager
  /org/freedesktop/NetworkManager
  org.freedesktop.NetworkManager.PrimaryConnectionType

which is a string like '802-11-wireless' or 'bluetooth'.  If there is no
connection then it is an empty string.

We don't have normal D-Bus property change notification here but rather
a custom-rolled signal from NetworkManager itself (PropertiesChanged).

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

Title:
  Occasional hang in unity 8 dash on the phone

Status in “network-manager” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  The dash is sometimes hanging on the phone.

  See the attached backtrace.

  The issue is as follows: we are maintaining a client-side tree of all
  NetworkManager devices.  When we see that a new device has been added,
  we query its properties in order to build our local proxy.  Doing this
  means that we are making QtDBus calls from a signal handler.  Due to a
  bug in QtDBus this is not safe.

  libdbus-1 has a recursive lock on its DBusConnection.  When the signal
  arrives, the lock is acquired and the sginal handler is run.  The
  signal handler can make DBus calls (which also require the lock)
  because the lock is recursive.  QtDBus also has a lock that is always
  acquired before the libdbus-1 connection lock is acquired.

  Unfortuntaely, the QtDBus lock is not acquired in the case of the
  incoming call from DBus -- only the DBus lock is.

  
  If another thread tries to do an unrelated DBus call meanwhile, it will 
acquire the QtDBus lock first and then the DBus lock (which is held because of 
the signal that arrived).  Once the signal handler gets to the point of wanting 
to make a DBus call (in order to query the properties of the just-added network 
device) it will attempt to acquire the QtDBus lock.  This is a lock-inversion 
deadlock.

  There are at least three bugs here:

  1) QtDBus should be fixed in order to avoid this sort of lock
  inversion problem.  Even if we fix this one situation, it seems quite
  likely that issues like this will arise again.

  2) QNetworkManager should avoid the issue in QtDBus until such a time
  as it is fixed.  This could be done by dispatching to a worker thread
  on receipt of signals so that the queries are done in a fresh call
  stack (without the libdbus-1 lock held).

  3) Apparently the only reason we are using NetworkManager at all is in
  order to know if we are on a 3G connection or not (in order to avoid
  too much data charges).  This would be much easier to do if
  NetworkManager provided a property that we could watch directly
  instead of bringing up an entire tree of objects in order to answer a
  very simple question.  To that end I've filed
  https://bugzilla.gnome.org/show_bug.cgi?id=739080 which we can
  hopefully get addressed relatively quickly.

  
  I consider 3) to be the real fix as far as we are concerned, but we should 
probably ensure that the Qt people know about 1) and 2).  Either of those could 
function as a workaround for us in the meantime, but the idea that we are 
creating this complex object tree to answer a simple question is ridiculous, so 
we should really fix that directly.

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

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

[Touch-packages] [Bug 1384776] Re: Occasional hang in unity 8 dash on the phone

** Changed in: unity8 (Ubuntu)
 Assignee: Michał Sawicz (saviq) => Gerry Boland (gerboland)

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

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

Title:
  Occasional hang in unity 8 dash on the phone

Status in “network-manager” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  The dash is sometimes hanging on the phone.

  See the attached backtrace.

  The issue is as follows: we are maintaining a client-side tree of all
  NetworkManager devices.  When we see that a new device has been added,
  we query its properties in order to build our local proxy.  Doing this
  means that we are making QtDBus calls from a signal handler.  Due to a
  bug in QtDBus this is not safe.

  libdbus-1 has a recursive lock on its DBusConnection.  When the signal
  arrives, the lock is acquired and the sginal handler is run.  The
  signal handler can make DBus calls (which also require the lock)
  because the lock is recursive.  QtDBus also has a lock that is always
  acquired before the libdbus-1 connection lock is acquired.

  Unfortuntaely, the QtDBus lock is not acquired in the case of the
  incoming call from DBus -- only the DBus lock is.

  
  If another thread tries to do an unrelated DBus call meanwhile, it will 
acquire the QtDBus lock first and then the DBus lock (which is held because of 
the signal that arrived).  Once the signal handler gets to the point of wanting 
to make a DBus call (in order to query the properties of the just-added network 
device) it will attempt to acquire the QtDBus lock.  This is a lock-inversion 
deadlock.

  There are at least three bugs here:

  1) QtDBus should be fixed in order to avoid this sort of lock
  inversion problem.  Even if we fix this one situation, it seems quite
  likely that issues like this will arise again.

  2) QNetworkManager should avoid the issue in QtDBus until such a time
  as it is fixed.  This could be done by dispatching to a worker thread
  on receipt of signals so that the queries are done in a fresh call
  stack (without the libdbus-1 lock held).

  3) Apparently the only reason we are using NetworkManager at all is in
  order to know if we are on a 3G connection or not (in order to avoid
  too much data charges).  This would be much easier to do if
  NetworkManager provided a property that we could watch directly
  instead of bringing up an entire tree of objects in order to answer a
  very simple question.  To that end I've filed
  https://bugzilla.gnome.org/show_bug.cgi?id=739080 which we can
  hopefully get addressed relatively quickly.

  
  I consider 3) to be the real fix as far as we are concerned, but we should 
probably ensure that the Qt people know about 1) and 2).  Either of those could 
function as a workaround for us in the meantime, but the idea that we are 
creating this complex object tree to answer a simple question is ridiculous, so 
we should really fix that directly.

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

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

[Touch-packages] [Bug 1384909] [NEW] "Always on top" windows go into the background after the dialog

2014-10-23 Thread Volodya

Public bug reported:

Here i will us specific applications as an example, but i have checked
with others as well. Using specific ones for clarity.

To replicate:

Open a file manager
Start a video in VLC
Set "Always on top" on VLC window
Observe that you can continue browsing files in the file manager, and the VLC 
window will remain on top of the file manager
Press delete on any file
The dialog box to confirm the deletion will open

What happens:

VLC window will go below the file manager window, and will stay below
even after the dialog will go away

What i expect to happen:

Dialog should go over the VLC window, but the file manager should not go
over it.

alternatively if that isn't possible

VLC window should become visible again as soon as the dialog gets
dismissed.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Fri Oct 24 00:20:15 2014
InstallationDate: Installed on 2014-10-02 (21 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  "Always on top" windows go into the background after the dialog

Status in “unity” package in Ubuntu:
  New

Bug description:
  Here i will us specific applications as an example, but i have checked
  with others as well. Using specific ones for clarity.

  To replicate:

  Open a file manager
  Start a video in VLC
  Set "Always on top" on VLC window
  Observe that you can continue browsing files in the file manager, and the VLC 
window will remain on top of the file manager
  Press delete on any file
  The dialog box to confirm the deletion will open

  What happens:

  VLC window will go below the file manager window, and will stay below
  even after the dialog will go away

  What i expect to happen:

  Dialog should go over the VLC window, but the file manager should not
  go over it.

  alternatively if that isn't possible

  VLC window should become visible again as soon as the dialog gets
  dismissed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Oct 24 00:20:15 2014
  InstallationDate: Installed on 2014-10-02 (21 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 970647] Re: Denials due to "deleted" are not being logged

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

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

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

** Changed in: apparmor (Ubuntu)
 Assignee: John Johansen (jjohansen) => (unassigned)

** Changed in: apparmor
 Assignee: John Johansen (jjohansen) => (unassigned)

** Tags added: aa-kernel

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

Title:
  Denials due to "deleted" are not being logged

Status in AppArmor Linux application security framework:
  Confirmed
Status in The Linux Kernel:
  Confirmed
Status in “apparmor” package in Ubuntu:
  Confirmed
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  When apparmor is enforcing a profile the default mode is to handle deleted 
files through file labeling and delegation.  However there are currently cases 
when this is not sufficient and will result in an access denial that should 
have an an info field of
info="Failed name lookup - deleted entry"

  However these log messages are not being generated, and apparmor is
  rejecting accesses based on deleted entries being mediated.  See Bug
  #969299 as one case where this is happening.

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

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

[Touch-packages] [Bug 1045985] Re: support environment filtering

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

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

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

** Tags added: aa-kernel

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

Title:
  support environment filtering

Status in AppArmor Linux application security framework:
  Triaged
Status in “apparmor” package in Ubuntu:
  Confirmed
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Confined applications have too much control over executables due to a
  lack of environment filtering in AppArmor. Bug #851986 is one such
  example. While we have employed the sanitized_helper to help, it
  should not be considered the final solution as it causes usability
  issues and is limited in what it can achieve. This bug is to track the
  environment filtering work.

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

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

[Touch-packages] [Bug 1316265] Re: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+W (window spread) filtering

** Changed in: unity/7.2
   Status: Triaged => In Progress

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

Title:
  Maximized Window's Title Bar Does Not Merge into Menu Bar after
  Performing Super+W (window spread) filtering

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  A maximized application's title bar does not merge into the menu bar
  once a user has performed Super + W (window slide). Note that if one
  does not do Super+E, then the bars to merge together. However, once
  Super+E has been performed, this bug persists for the lifetime of the
  windowed application. If the application is restarted after doing
  Super+E, then the bug is gone. Thus, it seems like Super+E introduces
  this bug for the lifetime of the windowed application.

  Expected behavior: Maximized window's title bar is merged into menu bar.
  Observed: Does not occur after Super+W is performed.

  Try this out using Terminal.

  ProblemType: BugDistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon May  5 14:48:01 2014
  InstallationDate: Installed on 2013-09-08 (239 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130424)SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-04 (0 days ago)

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

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

[Touch-packages] [Bug 1372847] Re: [SRU] New stable release 2.40.1

I have been using libglib2.0-0 2.40.2-0ubuntu1 for the past twenty days,
and I haven't noticed any regressions.

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

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

Title:
  [SRU] New stable release 2.40.1

Status in “glib2.0” package in Ubuntu:
  Fix Released
Status in “glib2.0” source package in Trusty:
  Fix Committed

Bug description:
  We'd like to update glib2.0 using the GNOME MRE.

  [ Description ]

  Upstream have released a new stable, fixing some bugs.

  glib2.0 (2.40.2-0ubuntu1) UNRELEASED; urgency=medium

* New upstream stable release, fixing bugs
  + gobject: try to link with -Wl,-z,nodelete to prevent unloading
  + g_file_copy: Don't set GError when we intend to ignore errors
  + gapplication-tool: ensure object paths are valid
  + gtlscertificate: fix certificate list parsing with trailing comments
  + g_str_has_prefix: improve efficiency with long strings
  + Added type check to GPermission public functions.
  + GApplication: Don't decrease use_count below 0
  + networkmonitornetlink: fix IPv6 issues on Android
  + gresolver: Ensure GThreadedResolver always sets an error if resolution
fails
  + gmacros.h: add G_GNUC_*_IGNORE_DEPRECATIONS macros for clang
  + networkaddress: fix parsing of uri with @ after authority
  + gvariant tests: workaround libc/compiler "issue"

   -- Iain Lane   Tue, 23 Sep 2014 10:27:17
  +0100

  [ QA ]

  Under the terms of the MRE, you can assume the bugs are fixed. I
  suggest installing the update and then using your system as normal for
  the 10 day verification time.

  [ Regression potential ]

  One of the fixes could be bad. This is the first stable in this series
  and is a new release, so hasn't had much testing on its own, even if
  all of the fixes are in the unstable release.

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

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

[Touch-packages] [Bug 1384776] Re: Occasional hang in unity 8 dash on the phone

2014-10-23 Thread Bill Filler

** Tags added: rtm14

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michał Sawicz (saviq)

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

Title:
  Occasional hang in unity 8 dash on the phone

Status in “network-manager” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  New

Bug description:
  The dash is sometimes hanging on the phone.

  See the attached backtrace.

  The issue is as follows: we are maintaining a client-side tree of all
  NetworkManager devices.  When we see that a new device has been added,
  we query its properties in order to build our local proxy.  Doing this
  means that we are making QtDBus calls from a signal handler.  Due to a
  bug in QtDBus this is not safe.

  libdbus-1 has a recursive lock on its DBusConnection.  When the signal
  arrives, the lock is acquired and the sginal handler is run.  The
  signal handler can make DBus calls (which also require the lock)
  because the lock is recursive.  QtDBus also has a lock that is always
  acquired before the libdbus-1 connection lock is acquired.

  Unfortuntaely, the QtDBus lock is not acquired in the case of the
  incoming call from DBus -- only the DBus lock is.

  
  If another thread tries to do an unrelated DBus call meanwhile, it will 
acquire the QtDBus lock first and then the DBus lock (which is held because of 
the signal that arrived).  Once the signal handler gets to the point of wanting 
to make a DBus call (in order to query the properties of the just-added network 
device) it will attempt to acquire the QtDBus lock.  This is a lock-inversion 
deadlock.

  There are at least three bugs here:

  1) QtDBus should be fixed in order to avoid this sort of lock
  inversion problem.  Even if we fix this one situation, it seems quite
  likely that issues like this will arise again.

  2) QNetworkManager should avoid the issue in QtDBus until such a time
  as it is fixed.  This could be done by dispatching to a worker thread
  on receipt of signals so that the queries are done in a fresh call
  stack (without the libdbus-1 lock held).

  3) Apparently the only reason we are using NetworkManager at all is in
  order to know if we are on a 3G connection or not (in order to avoid
  too much data charges).  This would be much easier to do if
  NetworkManager provided a property that we could watch directly
  instead of bringing up an entire tree of objects in order to answer a
  very simple question.  To that end I've filed
  https://bugzilla.gnome.org/show_bug.cgi?id=739080 which we can
  hopefully get addressed relatively quickly.

  
  I consider 3) to be the real fix as far as we are concerned, but we should 
probably ensure that the Qt people know about 1) and 2).  Either of those could 
function as a workaround for us in the meantime, but the idea that we are 
creating this complex object tree to answer a simple question is ridiculous, so 
we should really fix that directly.

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

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

[Touch-packages] [Bug 583400] Re: Gateway Profile 5 No Sound through Speakers, Sound through Headphones

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

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

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

Title:
  Gateway Profile 5 No Sound through Speakers, Sound through Headphones

Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  I have "unmuted" pretty much everything in alsa-mixer.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe1474 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'ICH5'/'Intel ICH5 with STAC9758,59 at irq 17'
 Mixer name : 'SigmaTel STAC9758,59'
 Components : 'AC97a:83847658'
 Controls  : 50
 Simple ctrls  : 37
  Date: Thu May 20 11:57:29 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  dmi.bios.date: 08/05/2004
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: P08.865G
  dmi.board.name: Desktop System
  dmi.board.vendor: Gateway
  dmi.board.version: PROFILE 5
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 13
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: SEI04B09
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrP08.865G:bd08/05/2004:svnGateway:pnPROFILE52901001:pvr4000944:rvnGateway:rnDesktopSystem:rvrPROFILE5:cvnGateway:ct13:cvrSEI04B09:
  dmi.product.name: PROFILE5 2901001
  dmi.product.version: 4000944
  dmi.sys.vendor: Gateway

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

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

[Touch-packages] [Bug 1384877] Re: Can't run on device since rtm image 123

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

** Changed in: ubuntu-touch-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  Can't run on device since rtm image 123

Status in Ubuntu UI Toolkit:
  Invalid
Status in “ubuntu-touch-meta” package in Ubuntu:
  Confirmed
Status in “ubuntu-touch-meta” package in Ubuntu RTM:
  Confirmed

Bug description:
  autopilot was just removed from the images, which also removed gir1.2
  -ubuntu-app-launch-2.  The script to run on the device needs that
  package.

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

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

[Touch-packages] [Bug 1384877] Re: Can't run on device since rtm image 123

2014-10-23 Thread Zoltan Balogh

** Changed in: ubuntu-ui-toolkit
   Status: New => Invalid

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

Title:
  Can't run on device since rtm image 123

Status in Ubuntu UI Toolkit:
  Invalid
Status in “ubuntu-touch-meta” package in Ubuntu:
  Confirmed
Status in “ubuntu-touch-meta” package in Ubuntu RTM:
  Confirmed

Bug description:
  autopilot was just removed from the images, which also removed gir1.2
  -ubuntu-app-launch-2.  The script to run on the device needs that
  package.

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

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

[Touch-packages] [Bug 884770] Re: When a window is maximized, there is no way to send it to another virtual desktop by using the mouse.