[Touch-packages] [Bug 1389305] Re: sudo doesn't work on unprivileged lxc container

2014-11-19 Thread Adam Ryczkowski
I really don't know how to tell you, which Trusty's 64bit minimal cd I
used. I didn't even know that there are more than one.

I just downloaded the fresh minimal cd about week before posting this
bug. When opening the minimal cd in file browser I see no files with
names version, changelog or anything similar. The best I found a
contents of the .disk/mini-info:

Ubuntu 14.04 trusty - amd64 (20101020ubuntu318)

uname -r
3.13.0-39-generic

Host's home lies on ecryptfs on top of btrfs:

$ mount
/dev/mapper/sdalvm-root on / type btrfs (rw,noatime,subvol=@)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
/dev/mapper/sdalvm-root on /home type btrfs (rw,noatime,subvol=@home)
/dev/sda1 on /boot type ext3 (rw)
systemd on /sys/fs/cgroup/systemd type cgroup 
(rw,noexec,nosuid,nodev,none,name=systemd)
/home/zosia/.Private on /home/zosia type ecryptfs 
(ecryptfs_check_dev_ruid,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs,ecryptfs_sig=65ba6ff1cded08ed,ecryptfs_fnek_sig=e9a5867908bf1b34)

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

Title:
  sudo doesn't work on unprivileged lxc container

Status in “lxc” package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 14.04 64 bit, after adding a user into an unprivileged
  container, the sudo complains that:

  $ sudo su
  sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 
'nosuid' option set or an NFS file system without root privileges?

  To reproduce:

  1. Download and install the Ubuntu amd64 minimalcd
  2. Install lxc on it and openssh for convenience.
  3. follow 
https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged-containers/ ; 
specifically do:
   a) sudo usermod --add-subuids 10-165536 $USER
   b) sudo usermod --add-subgids 10-165536 $USER
   c) sudo chmod +x $HOME
   d) create the file  ~/.config/lxc/default.conf with the following 
contents:
  lxc.include = /etc/lxc/default.conf
  lxc.id_map = u 0 10 65536
  lxc.id_map = g 0 10 65536
   e) echo $USER veth lxcbr0 10 | sudo tee /etc/lxc/lxc-usernet
  (restart is not required)
  4. Create the container with
  lxc-create -t download -n p1 -- -d ubuntu -r trusty -a amd64
  5. Install openssh-server in the container:
  lxc-start -d -n p1
  lxc-attach -n p1 -- apt-get install openssh-server
  6. Add a user adam with the group sudo
  lxc-attach -n p1 -- adduser adam sudo
  7. Set a password for the user
  8. Log in via ssh (and provide the password from step 7)
  ssh p1@adam
  9. On the p1:
  adam@p1$ sudo su
  sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 
'nosuid' option set or an NFS file system without root privileges?

  I expected it to make change the user to root.

  lxc version: 1.0.3-0ubuntu3
  $cat ~/.cache/lxc/download/ubuntu/trusty/amd64/default/build_id
  20141101_03:49

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

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


[Touch-packages] [Bug 1393542] Re: SRU: exfat not detected by blkid

2014-11-19 Thread Martin Matuska
** Description changed:

  [Impact]
  
  Due to a upstream bug blkid is unable to detect exfat partitions. This
  breaks proper detection and automount of exfat formatted partitions
  (e.g. SD cards or USB sticks)  in Ubuntu 14.10.
  
  [Test Case]
  
  Insert an exfat formatted SD Card (card is neither detected nor automounted)
  or
  run as root: blkid [partition]
  
  [Regression Potential]
  
  None known, the bugfix is simple and part of already released upstream
  stable release (2.25.2).
  
  [Other Info]
  
- Bug reference: 
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1389021
+ Bug reference: #1389021
  Upstream issue: https://github.com/karelzak/util-linux/issues/119
  Upstream bugfix commit: 
https://github.com/karelzak/util-linux/commit/98b539c25caede8534ffaf06e67a694eeb3bc6cb

** Description changed:

  [Impact]
  
  Due to a upstream bug blkid is unable to detect exfat partitions. This
  breaks proper detection and automount of exfat formatted partitions
  (e.g. SD cards or USB sticks)  in Ubuntu 14.10.
  
  [Test Case]
  
  Insert an exfat formatted SD Card (card is neither detected nor automounted)
  or
  run as root: blkid [partition]
  
  [Regression Potential]
  
  None known, the bugfix is simple and part of already released upstream
  stable release (2.25.2).
  
  [Other Info]
  
- Bug reference: #1389021
+ Bug reference: bug #1389021
  Upstream issue: https://github.com/karelzak/util-linux/issues/119
  Upstream bugfix commit: 
https://github.com/karelzak/util-linux/commit/98b539c25caede8534ffaf06e67a694eeb3bc6cb

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

Title:
   SRU: exfat not detected by blkid

Status in “util-linux” package in Ubuntu:
  New
Status in “util-linux” source package in Trusty:
  Invalid
Status in “util-linux” source package in Utopic:
  New

Bug description:
  [Impact]

  Due to a upstream bug blkid is unable to detect exfat partitions. This
  breaks proper detection and automount of exfat formatted partitions
  (e.g. SD cards or USB sticks)  in Ubuntu 14.10.

  [Test Case]

  Insert an exfat formatted SD Card (card is neither detected nor automounted)
  or
  run as root: blkid [partition]

  [Regression Potential]

  None known, the bugfix is simple and part of already released upstream
  stable release (2.25.2).

  [Other Info]

  Bug reference: bug #1389021
  Upstream issue: https://github.com/karelzak/util-linux/issues/119
  Upstream bugfix commit: 
https://github.com/karelzak/util-linux/commit/98b539c25caede8534ffaf06e67a694eeb3bc6cb

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

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


[Touch-packages] [Bug 1231368] Re: Can't select a background anymore since the 2013-09-25 update

2014-11-19 Thread Bedňa
I test Ubuntu Touch 14.09, 14.10 and 15.04 background can`t change.

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

Title:
  Can't select a background anymore since the 2013-09-25 update

Status in “content-hub” package in Ubuntu:
  Fix Released
Status in “gallery-app” package in Ubuntu:
  Fix Released
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released

Bug description:
  Using the current ubuntu touch image (65) on grouper or mako,
  selecting a background in system-settings doesn't work anymore

  It seems to be due to that update:
  https://launchpad.net/ubuntu/+source/content-hub/0.0+13.10.20130925-0ubuntu1

  Downgrading back to the content-hub version of 2013-09-20 makes it
  work

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

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


[Touch-packages] [Bug 1394105] [NEW] Sometimes significant lag between snap dialog and ringtone start

2014-11-19 Thread Alfonso Sanchez-Beato
Public bug reported:

Version: ubuntu-touch/ubuntu-rtm/14.09-proposed r140 krillin

When testing a large number of phone calls it could be seen that on
certain calls there would be a significant delay between the snap
decision dialog being displayed and the ringtone beginning to play.

In extreme circumstances this could cause calls to be missed as there
would not be enough time to answer.

** Affects: indicator-messages (Ubuntu)
 Importance: Undecided
 Status: New

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

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

** Affects: telepathy-ofono (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: telepathy-ofono (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Sometimes significant lag between snap dialog and ringtone start

Status in “indicator-messages” package in Ubuntu:
  New
Status in “ofono” package in Ubuntu:
  New
Status in “pulseaudio” package in Ubuntu:
  New
Status in “telepathy-ofono” package in Ubuntu:
  New

Bug description:
  Version: ubuntu-touch/ubuntu-rtm/14.09-proposed r140 krillin

  When testing a large number of phone calls it could be seen that on
  certain calls there would be a significant delay between the snap
  decision dialog being displayed and the ringtone beginning to play.

  In extreme circumstances this could cause calls to be missed as there
  would not be enough time to answer.

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

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


[Touch-packages] [Bug 1394105] Re: Sometimes significant lag between snap dialog and ringtone start

2014-11-19 Thread Alfonso Sanchez-Beato
See LP bug #1388899 for more information.

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

Title:
  Sometimes significant lag between snap dialog and ringtone start

Status in “indicator-messages” package in Ubuntu:
  New
Status in “ofono” package in Ubuntu:
  New
Status in “pulseaudio” package in Ubuntu:
  New
Status in “telepathy-ofono” package in Ubuntu:
  New

Bug description:
  Version: ubuntu-touch/ubuntu-rtm/14.09-proposed r140 krillin

  When testing a large number of phone calls it could be seen that on
  certain calls there would be a significant delay between the snap
  decision dialog being displayed and the ringtone beginning to play.

  In extreme circumstances this could cause calls to be missed as there
  would not be enough time to answer.

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

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


[Touch-packages] [Bug 1393438] Re: Enable location data string displays untranslated

2014-11-19 Thread Albert Astals Cid
Why is the shell responsible of any of this? It's a string that is not
showing at all in our code, so we should not be responsible of
translating it.

As Sebastian says it comes from unity-scopes-api so it is unity-scopes-
api that should make it translatable.

./src/scopes/internal/IniSettingsSchema.cpp:297:Setting 
s(internal.location, boolean, Enable location data, VariantArray(), 
Variant(true));
./src/scopes/internal/JsonSettingsSchema.cpp:418:Setting 
s(internal.location, boolean, Enable location data, VariantArray(), 
Variant(true));


** Changed in: unity8 (Ubuntu)
   Status: New = Invalid

** Changed in: unity-scopes-api (Ubuntu)
   Status: Invalid = New

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

Title:
  Enable location data string displays untranslated

Status in “unity-scopes-api” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  Using rtm 162 on krillin, several of the dash screens have a enable
  location data option, that strings seems to not be translatable

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

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


[Touch-packages] [Bug 1393915] Re: uuidgen --random requires an argument

2014-11-19 Thread Kurt Huwig
Sorry for missing the release. I am using 14.04 LTS.

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

Title:
  uuidgen --random requires an argument

Status in “util-linux” package in Ubuntu:
  Fix Released

Bug description:
  The man page of 'uuidgen' reports the options -r and --random as
  equivalent:

 -r, --random
Generate a random-based UUID.  This method creates a UUID 
consisting  mostly  of  random
bits.   It  requires that the operating system have a high 
quality random number genera‐
tor, such as /dev/random.

  But --random requires an argument:

  kurt@rodin:~$ uuidgen -r
  4aca676a-a3f1-4217-a35d-031c376c6274
  kurt@rodin:~$ uuidgen --random
  uuidgen: option '--random' requires an argument

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

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


[Touch-packages] [Bug 1393410] Re: [TOPBLOCKER] Apps with prices are not shown by default

2014-11-19 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/vivid-proposed/unity-scope-click

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

Title:
  [TOPBLOCKER] Apps with prices are not shown by default

Status in “unity-scope-click” package in Ubuntu:
  In Progress
Status in “unity-scope-click” package in Ubuntu RTM:
  Fix Released

Bug description:
  The current default in the scope is to not show apps with prices, and
  they are only shown after running a special script. This was done like
  that so the payments feature could be tested in a more controlled
  environment.

  Now it needs to be enabled so the default is to show apps with prices
  to everybody.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1393410/+subscriptions

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


[Touch-packages] [Bug 1389021] Re: Does not detect hotplugged storage device (exfat)

2014-11-19 Thread Martin Matuska
SRU utopic: bug #1393542

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

Title:
  Does not detect hotplugged storage device (exfat)

Status in “util-linux” package in Ubuntu:
  Fix Released

Bug description:
  It used to work then stopped for some reason.

  Disk /dev/sdb: 232.9 GiB, 250059350016 bytes, 488397168 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x7c367968

  Device Boot Start   End   Sectors   Size Id Type
  /dev/sdb1  63 488392064 488392002 232.9G  7 HPFS/NTFS/exFAT

  
  exfatfsck /dev/sdb1 finds no error

  mount -t exfat works, it's just auto-mounting that doesn't. 
  '-t' is required though, not sure if that's normal:
  mount: /dev/sdb1: more filesystems detected. This should not happen,
 use -t type to explicitly specify the filesystem type or
 use wipefs(8) to clean up the device.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gvfs 1.20.2-1ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  4 00:39:03 2014
  HotplugNewDevices: /dev/sdb1 /dev/sdb
  HotplugNewMounts:
   
  InstallationDate: Installed on 2014-10-03 (31 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: gvfs
  Symptom: storage
  Title: Does not detect hotplugged storage device
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (10 days ago)

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

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


[Touch-packages] [Bug 1377332] Re: [TOPBLOCKER] UI randomly freezes

2014-11-19 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/vivid-proposed/ubuntu-app-launch

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

Title:
  [TOPBLOCKER] UI randomly freezes

Status in “cgmanager” package in Ubuntu:
  Incomplete
Status in “ubuntu-app-launch” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Opinion
Status in “ubuntu-app-launch” package in Ubuntu RTM:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  Opinion

Bug description:
  Summary
  UI randomly freezes

  steps:
  1. unlock greeter
  2. open app
  3. pull down random indicator
  4. close indicator
  5. open app
  6. swipe to view all open apps
  7. open launcher
  8. close some open apps
  9. repeat until ui freezes

  device info:
  [service]
  base: system-image.ubuntu.com
  http_port: 80
  https_port: 443
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  device: krillin
  build_number: 79
  version_detail: 
ubuntu=20141002,device=20141002-d5938d7,custom=1412208099,version=79

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

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


[Touch-packages] [Bug 1391498] Re: [TOPBLOCKER] [Dash] In the app scope, replace the Ubuntu icon in the header with the word Apps

2014-11-19 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/vivid-proposed/unity-scope-click

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

Title:
  [TOPBLOCKER] [Dash] In the app scope, replace the Ubuntu icon in the
  header with the word Apps

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity-scope-click” package in Ubuntu:
  In Progress
Status in “unity-scope-click” package in Ubuntu RTM:
  Fix Released

Bug description:
  [Dash] In the app scope, replace the Ubuntu icon in the header with
  the word Apps

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

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


[Touch-packages] [Bug 1309680] Re: Building Unity fails with Nux: [GraphicsDisplay::CreateOpenGLWindow] GLX is not supported.

2014-11-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unity (Ubuntu)
   Status: New = Confirmed

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

Title:
  Building Unity fails with Nux: [GraphicsDisplay::CreateOpenGLWindow]
  GLX is not supported.

Status in Unity:
  New
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  $ sudo apt-get build-dep unity
  $ apt-get source unity
  $ cd unity-*
  $ dpkg-buildpackage -b -nc -us -uc
  // …
  Scanning dependencies of target check-headless
  make[5]: Leaving directory 
`/home/pcworld/Downloads/ubtrusty/unity-7.2.0+14.04.20140416/obj-x86_64-linux-gnu'
  make -f tests/CMakeFiles/check-headless.dir/build.make 
tests/CMakeFiles/check-headless.dir/build
  make[5]: Entering directory 
`/home/pcworld/Downloads/ubtrusty/unity-7.2.0+14.04.20140416/obj-x86_64-linux-gnu'
  cd 
/home/pcworld/Downloads/ubtrusty/unity-7.2.0+14.04.20140416/obj-x86_64-linux-gnu/tests
  export NUX_FALLBACK_TEXTURE=TRUE  
/home/pcworld/Downloads/ubtrusty/unity-7.2.0+14.04.20140416/tests/dummy-xorg-test-runner.sh
 ./test-gtest --gtest_output=xml:./test-gtest.xml  
/home/pcworld/Downloads/ubtrusty/unity-7.2.0+14.04.20140416/tests/dummy-xorg-test-runner.sh
 ./test-gtest-slow --gtest_output=xml:./test-gtest-slow.xml  
./test-gtest-xless --gtest_output=xml:./test-gtest-xless.xml  
./test-gestures/test-gestures --gtest_output=xml:./test-gestures.xml  
dbus-test-runner --max-wait=300 --task ./test-gtest-service --task-name 
test-service --task=./test-gtest-dbus --task-name=test-dbus 
--wait-for=com.canonical.Unity.Test.Scope 
--parameter=--gtest_output=xml:./test-gtest-dbus.xml 
--parameter=--gtest_filter=-TestCategoriesChanging*
  WARN  2014-04-18 20:11:41 unity.screen UScreen.cpp:114 
UScreen::GetMonitorName: Failed to get monitor name for monitor0
  Xlib:  extension GLX missing on display :1994.
  Nux: [GraphicsDisplay::CreateOpenGLWindow] GLX is not supported.
  Segmentation fault (core dumped)
  make[5]: *** [tests/CMakeFiles/check-headless] Error 139
  make[5]: Leaving directory 
`/home/pcworld/Downloads/ubtrusty/unity-7.2.0+14.04.20140416/obj-x86_64-linux-gnu'
  make[4]: *** [tests/CMakeFiles/check-headless.dir/all] Error 2
  make[4]: Leaving directory 
`/home/pcworld/Downloads/ubtrusty/unity-7.2.0+14.04.20140416/obj-x86_64-linux-gnu'
  make[3]: *** [tests/CMakeFiles/check-headless.dir/rule] Error 2
  make[3]: Leaving directory 
`/home/pcworld/Downloads/ubtrusty/unity-7.2.0+14.04.20140416/obj-x86_64-linux-gnu'
  make[2]: *** [check-headless] Error 2
  make[2]: Leaving directory 
`/home/pcworld/Downloads/ubtrusty/unity-7.2.0+14.04.20140416/obj-x86_64-linux-gnu'
  make[1]: *** [override_dh_auto_test] Error 2
  make[1]: Leaving directory 
`/home/pcworld/Downloads/ubtrusty/unity-7.2.0+14.04.20140416'
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  
  Expected result: Unity builds without errors from the source package.

  $ glxinfo
  name of display: :0
  display: :0  screen: 0
  direct rendering: Yes
  server glx vendor string: NVIDIA Corporation
  server glx version string: 1.4
  server glx extensions:
  GLX_ARB_create_context, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_multisample, GLX_EXT_buffer_age, 
  GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
  GLX_EXT_framebuffer_sRGB, GLX_EXT_swap_control, 
GLX_EXT_swap_control_tear, 
  GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
  GLX_NV_float_buffer, GLX_NV_multisample_coverage, GLX_SGIX_fbconfig, 
  GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync
  client glx vendor string: NVIDIA Corporation
  client glx version string: 1.4
  client glx extensions:
  GLX_ARB_create_context, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, 
  GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
  GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
  GLX_EXT_import_context, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, 
  GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
  GLX_NV_copy_image, GLX_NV_float_buffer, GLX_NV_multisample_coverage, 
  GLX_NV_present_video, GLX_NV_swap_group, GLX_NV_video_capture, 
  GLX_NV_video_out, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
  GLX_SGI_swap_control, GLX_SGI_video_sync
  GLX version: 1.4
  GLX extensions:
  GLX_ARB_create_context, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, 
  

[Touch-packages] [Bug 1386709] Re: Queries to remote scopes don't include location data (even if the scope needs it)

2014-11-19 Thread Pawel Stolowski
** Tags added: rtm14

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

Title:
  Queries to remote scopes don't include location data (even if the
  scope needs it)

Status in “unity-scopes-api” package in Ubuntu:
  In Progress

Bug description:
  The query to weatherchannel is not including lat/long, even if the
  remote-scopes listing have the needs_location_data in true:
  https://pastebin.canonical.com/119512/

  The server try to guess user location using geo-ip, but it's not
  always as accurate as we need for a user service (it depends heavily
  on your IP being representative of where you really are, which may not
  be the case for hotel proxys, weird ISPs, etc).

  Plase, send user's latitude and longitude for the remote scopes that
  need this information.

  Thanks!

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

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


[Touch-packages] [Bug 1394105] Re: Sometimes significant lag between snap dialog and ringtone start

2014-11-19 Thread Sebastien Bacher
Doesn't look like an indicator issue to me, it's the ringing which is
delayed and that is coming from the telephony service rather

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

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

Title:
  Sometimes significant lag between snap dialog and ringtone start

Status in “indicator-messages” package in Ubuntu:
  Invalid
Status in “ofono” package in Ubuntu:
  New
Status in “pulseaudio” package in Ubuntu:
  New
Status in “telepathy-ofono” package in Ubuntu:
  New

Bug description:
  Version: ubuntu-touch/ubuntu-rtm/14.09-proposed r140 krillin

  When testing a large number of phone calls it could be seen that on
  certain calls there would be a significant delay between the snap
  decision dialog being displayed and the ringtone beginning to play.

  In extreme circumstances this could cause calls to be missed as there
  would not be enough time to answer.

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

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


[Touch-packages] [Bug 1387090] Re: boot breaks if /etc/machine-id is missing

2014-11-19 Thread Didier Roche
FYI, discussing it at http://lists.freedesktop.org/archives/systemd-
devel/2014-November/025334.html

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

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

Title:
  boot breaks if /etc/machine-id is missing

Status in “systemd” package in Ubuntu:
  In Progress

Bug description:
  When no /etc/machine-id file is present the boot breaks.

  Once this bug is fixed we can modify live-build so that it remove /etc
  /machine-id from the generated live rootfs instead of truncating it to
  a zero file.

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

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


[Touch-packages] [Bug 1386709] Re: Queries to remote scopes don't include location data (even if the scope needs it)

2014-11-19 Thread Thomas Strehl
** Changed in: unity-scopes-api (Ubuntu)
   Importance: Undecided = High

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

Title:
  Queries to remote scopes don't include location data (even if the
  scope needs it)

Status in “unity-scopes-api” package in Ubuntu:
  In Progress

Bug description:
  The query to weatherchannel is not including lat/long, even if the
  remote-scopes listing have the needs_location_data in true:
  https://pastebin.canonical.com/119512/

  The server try to guess user location using geo-ip, but it's not
  always as accurate as we need for a user service (it depends heavily
  on your IP being representative of where you really are, which may not
  be the case for hotel proxys, weird ISPs, etc).

  Plase, send user's latitude and longitude for the remote scopes that
  need this information.

  Thanks!

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

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


[Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script

2014-11-19 Thread Gunnar Hjalmarsson
Thanks for looking at it, Martin.

Actually I may have found a relatively trivial solution using trap();
please see attached diff.

** Patch added: possible-fix.diff
   
https://bugs.launchpad.net/ubuntu/trusty/+source/lightdm/+bug/678421/+attachment/4263541/+files/possible-fix.diff

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

Title:
  Error message for a faulty ~/.profile script

Status in GDM: The Gnome Display Manager:
  New
Status in “gdm” package in Ubuntu:
  In Progress
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “gdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Trusty:
  In Progress
Status in “gdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Utopic:
  Fix Committed

Bug description:
  trusty and utopic SRU requests
  ==

  [Impact]

  In case of a syntax error in either of ~/.profile or a few other
  similar files, the Xorg login is interrupted, and the user is taken
  back to the login screen without an explanation. Debugging this
  problem may be a time consuming exercise, especially for non-
  experienced users.

  With the proposed change, lightdm/gdm does not try to load such a
  file, but shows a warning dialog instead. (A warning dialog is also
  shown in case of some other type of error, which would not have caused
  the login to fail.)

  [Test Case]

  To reproduce:

  * Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
  * Log out and find that you can't log in to a graphical session.

  After installing the proposed lightdm/gdm version, you'll instead see
  the dialog and can log in.

  [Regression Potential]

  Since this is only about improved exception handling, it does not at
  all affect users with correct configuration files. The regression risk
  ought to be minimal.

  [Original description]

  Binary package hint: gdm

  After adding function AddPath { PATH=$1:$PATH } to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in .profile
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user .profile and .xprofile scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

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

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


[Touch-packages] [Bug 1387231] Re: [regression][clock] alarm still rings once it's been disabled or deleted

2014-11-19 Thread Pat McGowan
** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) = Charles Kerr (charlesk)

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

Title:
  [regression][clock] alarm still rings once it's been disabled or
  deleted

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

Bug description:
  (r135)

  Steps to reproduce:

  1. Create a single type alarm to ring in the next 5 minutes.
  2. Wait for the alarm to ring.
  3. After dismissing the alarm, delete it from the clock app.

  Actual behaviour:

  Once the alarm's been deleted, it still rings!

  Expected behaviour:

  Once you delete the alarm, this shouldn't ring anymore.

  

  Mako, Image #5 ubuntu rtm,

  Steps to reproduce:

  1. Create an alarm to ring in the next 5 minutes.
  2. Disable the alarm after it is created.

  Actual Behaviour:

  Alarm still rings!

  Expected Behaviour:

  Once you disable an alarm, it shouldn't ring anymore.

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

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


[Touch-packages] [Bug 1391498] Re: [TOPBLOCKER] [Dash] In the app scope, replace the Ubuntu icon in the header with the word Apps

2014-11-19 Thread Launchpad Bug Tracker
This bug was fixed in the package unity-scope-click -
0.1.1+15.04.20141118-0ubuntu1

---
unity-scope-click (0.1.1+15.04.20141118-0ubuntu1) vivid; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Alejandro J. Cura ]
  * Enable purchases by default (LP: #1393410)
  * Remove ubuntu logo from apps scope (LP: #1391498)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Tue, 18 Nov 2014 
15:05:15 +

** Changed in: unity-scope-click (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 unity-scope-click in
Ubuntu.
https://bugs.launchpad.net/bugs/1391498

Title:
  [TOPBLOCKER] [Dash] In the app scope, replace the Ubuntu icon in the
  header with the word Apps

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity-scope-click” package in Ubuntu:
  Fix Released
Status in “unity-scope-click” package in Ubuntu RTM:
  Fix Released

Bug description:
  [Dash] In the app scope, replace the Ubuntu icon in the header with
  the word Apps

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

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


[Touch-packages] [Bug 1393846] Re: Screen Lock shows wrong wallpaper

2014-11-19 Thread Gunnar Hjalmarsson
Maybe you should take a look at the config files in /etc/lightdm and
/usr/share/lightdm.

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

Title:
  Screen Lock shows wrong wallpaper

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Hi,

  after locking my screen the login screen displays the standard XFCE-
  Backgroung wallpaper. However, I am not using XFCE and I expect it to
  display either the standard wallpaper for the login screen or my
  personal wallpaper to be displayed.

  This is only one bug of a series of bugs concerning the screen lock.
  They are probably all related. I will provide the links to the bug
  reports later, until then you can find them in my personal profile.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Nov 18 17:12:00 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-13 (673 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2)
  LightdmConfig:
   [SeatDefaults]
   user-session=ubuntu
   greeter-session=unity-greeter
   allow-guest=true
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-09-14 (64 days ago)

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

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


[Touch-packages] [Bug 1393410] Re: [TOPBLOCKER] Apps with prices are not shown by default

2014-11-19 Thread Launchpad Bug Tracker
This bug was fixed in the package unity-scope-click -
0.1.1+15.04.20141118-0ubuntu1

---
unity-scope-click (0.1.1+15.04.20141118-0ubuntu1) vivid; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Alejandro J. Cura ]
  * Enable purchases by default (LP: #1393410)
  * Remove ubuntu logo from apps scope (LP: #1391498)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Tue, 18 Nov 2014 
15:05:15 +

** Changed in: unity-scope-click (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 unity-scope-click in
Ubuntu.
https://bugs.launchpad.net/bugs/1393410

Title:
  [TOPBLOCKER] Apps with prices are not shown by default

Status in “unity-scope-click” package in Ubuntu:
  Fix Released
Status in “unity-scope-click” package in Ubuntu RTM:
  Fix Released

Bug description:
  The current default in the scope is to not show apps with prices, and
  they are only shown after running a special script. This was done like
  that so the payments feature could be tested in a more controlled
  environment.

  Now it needs to be enabled so the default is to show apps with prices
  to everybody.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1393410/+subscriptions

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


[Touch-packages] [Bug 1357321] Re: QNetworkAccessManager doesn't support roaming on Ubuntu

2014-11-19 Thread Łukasz Zemczak
** Tags removed: lt-blocker lt-category-visible

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

Title:
  QNetworkAccessManager doesn't support roaming on Ubuntu

Status in Platform API:
  Invalid
Status in The Savilerow project:
  New
Status in “network-manager” package in Ubuntu:
  Invalid
Status in “ofono” package in Ubuntu:
  Invalid
Status in “qtbase-opensource-src” package in Ubuntu:
  In Progress
Status in “qtbase-opensource-src” package in Ubuntu RTM:
  New

Bug description:
  scope images load fine in wifi, but not on hsdpa even when there is
  good connectivity and browsing works well. Results are return, but
  images do not load.

To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions

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


[Touch-packages] [Bug 1394114] [NEW] [SVS13A3W9ES, Realtek ALC275, no sound from internal speaker and very low sound from headset

2014-11-19 Thread Guillaume
Public bug reported:

Problem: There is no sound from the internal sepaker and it is very low when 
headset is plugged in.
There is a dual boot with windows 8.1 and the sound is working just fine on 
W8.1.

I have tried to:
- Update the driver https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS
- Play around with sound level in alsamixer

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  guta   2564 F pulseaudio
CurrentDesktop: Unity
Date: Wed Nov 19 10:08:53 2014
InstallationDate: Installed on 2014-11-17 (1 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  guta   2564 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [SVS13A3W9ES, Realtek ALC275, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/13/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R1021C8
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BZHDH:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: SVS13A3W9ES
dmi.product.version: C60BZHDH
dmi.sys.vendor: Sony Corporation

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

Title:
  [SVS13A3W9ES, Realtek ALC275, no sound from internal speaker and very
  low sound from headset

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

Bug description:
  Problem: There is no sound from the internal sepaker and it is very low when 
headset is plugged in.
  There is a dual boot with windows 8.1 and the sound is working just fine on 
W8.1.

  I have tried to:
  - Update the driver https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS
  - Play around with sound level in alsamixer

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guta   2564 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov 19 10:08:53 2014
  InstallationDate: Installed on 2014-11-17 (1 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guta   2564 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [SVS13A3W9ES, Realtek ALC275, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R1021C8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BZHDH:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS13A3W9ES
  dmi.product.version: C60BZHDH
  dmi.sys.vendor: Sony Corporation

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

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


[Touch-packages] [Bug 1393698] Re: Cross qmake to the chroots

2014-11-19 Thread Michael Vogt
Thanks for your bugreport.

I'm happy to add this, but some changes are required:

Rename the package to qt5-qmake-arm-linux-gnueabihf so that it follows
the same convention as the other tools, this way click chroot.py can
install it in the same way as g++/pkg-config and does the right thing
for host-arch == target-arch.

The multi-arch: same header for qt5-qmake-cross-armhf is wrong and needs
fixing, the package can not be co-installed.

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

Title:
  Cross qmake to the chroots

Status in “click” package in Ubuntu:
  New

Bug description:
  The https://launchpad.net/ubuntu/+source/qtbase-opensource-src/5.3.2
  +dfsg-4ubuntu3 release of the QtBase module provides the new qt5
  -qmake-cross-armhf package and so the /usr/bin/qt5-qmake-cross-armhf
  binary.

  This qmake binary is made for x86 chroots with armhf development
  target.

  This change is to enable the build of qmake project type  in the click
  chroot.

  In order to support qmake projects we need this package installed in
  the click chroot. The qt5-qmake-cross-armhf  is not a multiarch
  package, it is made exclusively  for i386 and amd64 targets.

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

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


[Touch-packages] [Bug 1384460] Re: Delegate unhandled URL schemes to the system

2014-11-19 Thread Olivier Tilloy
** Changed in: webbrowser-app (Ubuntu RTM)
   Status: Confirmed = In Progress

** Changed in: webbrowser-app (Ubuntu RTM)
 Assignee: (unassigned) = Olivier Tilloy (osomon)

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

Title:
  Delegate unhandled URL schemes to the system

Status in Oxide Webview:
  Fix Released
Status in Oxide 1.3 series:
  Fix Released
Status in “webbrowser-app” package in Ubuntu:
  Fix Released
Status in “webbrowser-app” package in Ubuntu RTM:
  In Progress

Bug description:
  We currently ignore any URL's with a scheme that is unrecognised. We
  should be delegating these to the system so that it can try to find a
  handler for it

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

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


[Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script

2014-11-19 Thread Martin Pitt
Hah, nice! Works for me, too.

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

Title:
  Error message for a faulty ~/.profile script

Status in GDM: The Gnome Display Manager:
  New
Status in “gdm” package in Ubuntu:
  In Progress
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “gdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Trusty:
  In Progress
Status in “gdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Utopic:
  Fix Committed

Bug description:
  trusty and utopic SRU requests
  ==

  [Impact]

  In case of a syntax error in either of ~/.profile or a few other
  similar files, the Xorg login is interrupted, and the user is taken
  back to the login screen without an explanation. Debugging this
  problem may be a time consuming exercise, especially for non-
  experienced users.

  With the proposed change, lightdm/gdm does not try to load such a
  file, but shows a warning dialog instead. (A warning dialog is also
  shown in case of some other type of error, which would not have caused
  the login to fail.)

  [Test Case]

  To reproduce:

  * Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
  * Log out and find that you can't log in to a graphical session.

  After installing the proposed lightdm/gdm version, you'll instead see
  the dialog and can log in.

  [Regression Potential]

  Since this is only about improved exception handling, it does not at
  all affect users with correct configuration files. The regression risk
  ought to be minimal.

  [Original description]

  Binary package hint: gdm

  After adding function AddPath { PATH=$1:$PATH } to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in .profile
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user .profile and .xprofile scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

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

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


[Touch-packages] [Bug 1393438] Re: Enable location data string displays untranslated

2014-11-19 Thread Pete Woods
Michi, the shell doesn't add this - it's done inside the scopes runtime.
If the shell was responsible, then another client wouldn't see the
location setting. It seems to be like unity-scopes-api needs to add
localisation support in order to be able to translate any user-visible
strings. I guess this is the first one, though?

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

Title:
  Enable location data string displays untranslated

Status in “unity-scopes-api” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  Using rtm 162 on krillin, several of the dash screens have a enable
  location data option, that strings seems to not be translatable

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

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


[Touch-packages] [Bug 1390191] Re: Department not shown if there is only one app and it uses X-Ubuntu-Default-Department-ID key

2014-11-19 Thread Pawel Stolowski
** Changed in: unity-scope-click (Ubuntu)
   Status: Confirmed = In Progress

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

Title:
  Department not shown if there is only one app and it uses X-Ubuntu-
  Default-Department-ID key

Status in “unity-scope-click” package in Ubuntu:
  In Progress
Status in “unity-scope-click” package in Ubuntu RTM:
  Confirmed

Bug description:
  Department is not shown in Apps department drop-down menu if it has
  only one application which declares X-Ubuntu-Default-Department-ID=...
  department mapping (and is preinstalled, ie. wasn't installed from
  store).

  This is caused by too restrictive behavior of
  DepartmentsDb::get_children_departments(..), which filters out
  subdepartments that don't have any apps in the local departments db
  (which means that department will never be shown in the departments
  menu if it has no app installed from the store). This restriction
  should probably be removed from that method after careful verification
  if it has no undesired side effects.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1390191/+subscriptions

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


[Touch-packages] [Bug 1357321] Re: QNetworkAccessManager doesn't support roaming on Ubuntu

2014-11-19 Thread Oliver Grawert
it is tagged ota-1, so it will land, just not in one of the next two
promoted images, which just delays it by two weeks

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

Title:
  QNetworkAccessManager doesn't support roaming on Ubuntu

Status in Platform API:
  Invalid
Status in The Savilerow project:
  New
Status in “network-manager” package in Ubuntu:
  Invalid
Status in “ofono” package in Ubuntu:
  Invalid
Status in “qtbase-opensource-src” package in Ubuntu:
  In Progress
Status in “qtbase-opensource-src” package in Ubuntu RTM:
  New

Bug description:
  scope images load fine in wifi, but not on hsdpa even when there is
  good connectivity and browsing works well. Results are return, but
  images do not load.

To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions

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


[Touch-packages] [Bug 1394136] Re: if statement with pipe to grep randomly fails if pipefail is set

2014-11-19 Thread Michael Kerrin
We can also see the following result:

errin@kerrin-HP-Z620-Workstation:~/ce_build$ lsmod | grep -q -e ^kvm_amd -e 
^kvm_intel; echo $?
141
kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ lsmod | grep -q -e ^kvm_amd -e 
^kvm_intel; echo $?
141
kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ lsmod | grep -q -e ^kvm_amd -e 
^kvm_intel; echo $?
141
kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ lsmod | grep -q -e ^kvm_amd -e 
^kvm_intel; echo $?
0
kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ lsmod | grep -q -e ^kvm_amd -e 
^kvm_intel; echo $?
141
kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ lsmod | grep -q -e ^kvm_amd -e 
^kvm_intel; echo $?
141

One out of a lot passed.

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

Title:
  if statement with pipe to grep randomly fails if pipefail is set

Status in “bash” package in Ubuntu:
  Confirmed

Bug description:
  The following bash script will fail randomly on trusty but when tested
  on saucy it worked all the time. On the system we test we have kvm
  installed and the if statement should evaluate to false and we should
  see ten PASS lines and no Error. And this should happen all the time.

  ==
  #!/bin/bash 

  set -eu
  set -o pipefail

  if ! lsmod | grep -q -e ^kvm_intel -e ^kvm_amd ; then
  echo 'Error: check that virtualisation is enabled in your BIOS'
  else
  echo PASS
  fi
  ===

  As can be seen if I run it 10 times I get 2 PASS and 8 failures

  ===
  kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ for i in $(seq 0 9) ; do bash 
test-simple.bash ; done
  PASS
  PASS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  ===

  Now if I turn off the pipefail then the script passes all the time and
  just prints out 10 PASS lines.

  The script uses bash, grep and lsmod and I have the following versions
  on trusty of them

  kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ dpkg -l | grep bash
  ii  bash  4.3-7ubuntu1.5  
amd64GNU Bourne Again SHell
  ii  bash-completion   1:2.1-4 
all  programmable completion for the 
bash shell
  ii  command-not-found 0.3ubuntu12 
all  Suggest installation of packages 
in interactive bash sessions
  kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ dpkg -l | grep grep
  ii  grep  2.16-1  
amd64GNU grep, egrep and fgrep
  kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ dpkg -l | grep kmod
  ii  kmod  15-0ubuntu6 
amd64tools for managing Linux kernel 
modules
  ii  libkmod2:amd6415-0ubuntu6 
amd64libkmod shared library
  ii  module-init-tools 15-0ubuntu6 
all  transitional dummy package 
(module-init-tools to kmod)

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

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


[Touch-packages] [Bug 1394136] [NEW] if statement with pipe to grep randomly fails if pipefail is set

2014-11-19 Thread Michael Kerrin
Public bug reported:

The following bash script will fail randomly on trusty but when tested
on saucy it worked all the time. On the system we test we have kvm
installed and the if statement should evaluate to false and we should
see ten PASS lines and no Error. And this should happen all the time.

==
#!/bin/bash 

set -eu
set -o pipefail

if ! lsmod | grep -q -e ^kvm_intel -e ^kvm_amd ; then
echo 'Error: check that virtualisation is enabled in your BIOS'
else
echo PASS
fi
===

As can be seen if I run it 10 times I get 2 PASS and 8 failures

===
kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ for i in $(seq 0 9) ; do bash 
test-simple.bash ; done
PASS
PASS
Error: check that virtualisation is enabled in your BIOS
Error: check that virtualisation is enabled in your BIOS
Error: check that virtualisation is enabled in your BIOS
Error: check that virtualisation is enabled in your BIOS
Error: check that virtualisation is enabled in your BIOS
Error: check that virtualisation is enabled in your BIOS
Error: check that virtualisation is enabled in your BIOS
Error: check that virtualisation is enabled in your BIOS
===

Now if I turn off the pipefail then the script passes all the time and
just prints out 10 PASS lines.

The script uses bash, grep and lsmod and I have the following versions
on trusty of them

kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ dpkg -l | grep bash
ii  bash  4.3-7ubuntu1.5
  amd64GNU Bourne Again SHell
ii  bash-completion   1:2.1-4   
  all  programmable completion for the bash 
shell
ii  command-not-found 0.3ubuntu12   
  all  Suggest installation of packages in 
interactive bash sessions
kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ dpkg -l | grep grep
ii  grep  2.16-1
  amd64GNU grep, egrep and fgrep
kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ dpkg -l | grep kmod
ii  kmod  15-0ubuntu6   
  amd64tools for managing Linux kernel 
modules
ii  libkmod2:amd6415-0ubuntu6   
  amd64libkmod shared library
ii  module-init-tools 15-0ubuntu6   
  all  transitional dummy package 
(module-init-tools to kmod)

** Affects: bash (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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

Title:
  if statement with pipe to grep randomly fails if pipefail is set

Status in “bash” package in Ubuntu:
  Confirmed

Bug description:
  The following bash script will fail randomly on trusty but when tested
  on saucy it worked all the time. On the system we test we have kvm
  installed and the if statement should evaluate to false and we should
  see ten PASS lines and no Error. And this should happen all the time.

  ==
  #!/bin/bash 

  set -eu
  set -o pipefail

  if ! lsmod | grep -q -e ^kvm_intel -e ^kvm_amd ; then
  echo 'Error: check that virtualisation is enabled in your BIOS'
  else
  echo PASS
  fi
  ===

  As can be seen if I run it 10 times I get 2 PASS and 8 failures

  ===
  kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ for i in $(seq 0 9) ; do bash 
test-simple.bash ; done
  PASS
  PASS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  ===

  Now if I turn off the pipefail then the script passes all the time and
  just prints out 10 PASS lines.

  The script uses bash, grep and lsmod and I have the following versions
  on trusty of them

  kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ dpkg -l | grep bash
  ii  bash  4.3-7ubuntu1.5  
amd64GNU Bourne Again SHell
  ii  bash-completion   1:2.1-4 
all  programmable completion for the 
bash shell
  ii  command-not-found 0.3ubuntu12 
all  Suggest 

[Touch-packages] [Bug 1394136] Re: if statement with pipe to grep randomly fails if pipefail is set

2014-11-19 Thread Michael Kerrin
But this seems to work

kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ echo kvm_intel xxx | grep -q -e 
^kvm_amd -e ^kvm_intel; echo $?
0

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

Title:
  if statement with pipe to grep randomly fails if pipefail is set

Status in “bash” package in Ubuntu:
  Confirmed

Bug description:
  The following bash script will fail randomly on trusty but when tested
  on saucy it worked all the time. On the system we test we have kvm
  installed and the if statement should evaluate to false and we should
  see ten PASS lines and no Error. And this should happen all the time.

  ==
  #!/bin/bash 

  set -eu
  set -o pipefail

  if ! lsmod | grep -q -e ^kvm_intel -e ^kvm_amd ; then
  echo 'Error: check that virtualisation is enabled in your BIOS'
  else
  echo PASS
  fi
  ===

  As can be seen if I run it 10 times I get 2 PASS and 8 failures

  ===
  kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ for i in $(seq 0 9) ; do bash 
test-simple.bash ; done
  PASS
  PASS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  ===

  Now if I turn off the pipefail then the script passes all the time and
  just prints out 10 PASS lines.

  The script uses bash, grep and lsmod and I have the following versions
  on trusty of them

  kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ dpkg -l | grep bash
  ii  bash  4.3-7ubuntu1.5  
amd64GNU Bourne Again SHell
  ii  bash-completion   1:2.1-4 
all  programmable completion for the 
bash shell
  ii  command-not-found 0.3ubuntu12 
all  Suggest installation of packages 
in interactive bash sessions
  kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ dpkg -l | grep grep
  ii  grep  2.16-1  
amd64GNU grep, egrep and fgrep
  kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ dpkg -l | grep kmod
  ii  kmod  15-0ubuntu6 
amd64tools for managing Linux kernel 
modules
  ii  libkmod2:amd6415-0ubuntu6 
amd64libkmod shared library
  ii  module-init-tools 15-0ubuntu6 
all  transitional dummy package 
(module-init-tools to kmod)

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

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


[Touch-packages] [Bug 1394136] Re: if statement with pipe to grep randomly fails if pipefail is set

2014-11-19 Thread Nicholas Randon
** Changed in: bash (Ubuntu)
   Status: New = Confirmed

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

Title:
  if statement with pipe to grep randomly fails if pipefail is set

Status in “bash” package in Ubuntu:
  Confirmed

Bug description:
  The following bash script will fail randomly on trusty but when tested
  on saucy it worked all the time. On the system we test we have kvm
  installed and the if statement should evaluate to false and we should
  see ten PASS lines and no Error. And this should happen all the time.

  ==
  #!/bin/bash 

  set -eu
  set -o pipefail

  if ! lsmod | grep -q -e ^kvm_intel -e ^kvm_amd ; then
  echo 'Error: check that virtualisation is enabled in your BIOS'
  else
  echo PASS
  fi
  ===

  As can be seen if I run it 10 times I get 2 PASS and 8 failures

  ===
  kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ for i in $(seq 0 9) ; do bash 
test-simple.bash ; done
  PASS
  PASS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  ===

  Now if I turn off the pipefail then the script passes all the time and
  just prints out 10 PASS lines.

  The script uses bash, grep and lsmod and I have the following versions
  on trusty of them

  kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ dpkg -l | grep bash
  ii  bash  4.3-7ubuntu1.5  
amd64GNU Bourne Again SHell
  ii  bash-completion   1:2.1-4 
all  programmable completion for the 
bash shell
  ii  command-not-found 0.3ubuntu12 
all  Suggest installation of packages 
in interactive bash sessions
  kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ dpkg -l | grep grep
  ii  grep  2.16-1  
amd64GNU grep, egrep and fgrep
  kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ dpkg -l | grep kmod
  ii  kmod  15-0ubuntu6 
amd64tools for managing Linux kernel 
modules
  ii  libkmod2:amd6415-0ubuntu6 
amd64libkmod shared library
  ii  module-init-tools 15-0ubuntu6 
all  transitional dummy package 
(module-init-tools to kmod)

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

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


Re: [Touch-packages] [Bug 1393438] Re: Enable location data string displays untranslated

2014-11-19 Thread Michał Sawicz
W dniu 19.11.2014 o 10:47, Pete Woods pisze:
 Michi, the shell doesn't add this - it's done inside the scopes runtime.
 If the shell was responsible, then another client wouldn't see the
 location setting. It seems to be like unity-scopes-api needs to add
 localisation support in order to be able to translate any user-visible
 strings. I guess this is the first one, though?

I totally see the problem with enabling translations for a single string
(though I imagine there could be more in the future?).

Maybe we need to come up with a better approach? I.e. you telling the
shell this is a setting item for location and we'll handle the whole
thing on our side then?

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

Title:
  Enable location data string displays untranslated

Status in “unity-scopes-api” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  Using rtm 162 on krillin, several of the dash screens have a enable
  location data option, that strings seems to not be translatable

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

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


[Touch-packages] [Bug 1394143] [NEW] hook /usr/share/apport/package-hooks/source_xorg.py crashed

2014-11-19 Thread dino99
Public bug reported:

Here is the terminal output when ubuntu-bug is used:

oem@u32:~$ ubuntu-bug compiz-gnome
ERROR: hook /usr/share/apport/package-hooks/source_xorg.py crashed:
Traceback (most recent call last):
  File /usr/lib/python3/dist-packages/apport/report.py, line 197, in _run_hook
symb['add_info'](report, ui)
  File /usr/share/apport/package-hooks/source_xorg.py, line 677, in add_info
attach_nvidia_info(report, ui)
  File /usr/share/apport/package-hooks/source_xorg.py, line 521, in 
attach_nvidia_info
attach_file(report, logfile)
  File /usr/lib/python3/dist-packages/apport/hookutils.py, line 115, in 
attach_file
report[key] = read_file(path, force_unicode=force_unicode)
  File /usr/lib/python3/dist-packages/problem_report.py, line 563, in 
__setitem__
assert k.replace('.', '').replace('-', '').replace('_', '').isalnum()
AssertionError
oem@u32:~$ [904:950:1119/112815:ERROR:nss_util.cc(821)] After loading Root 
Certs, loaded==false: NSS error code: -8018

**
/var/crash/ does not show a crash file, and the report have been made/sent as 
usual; maybe a false positive.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: apport 2.14.7-0ubuntu10
ProcVersionSignature: Ubuntu 3.18.0-3.4-generic 3.18.0-rc4
Uname: Linux 3.18.0-3-generic i686
NonfreeKernelModules: nvidia
ApportLog:

ApportVersion: 2.14.7-0ubuntu10
Architecture: i386
CurrentDesktop: GNOME
Date: Wed Nov 19 11:47:31 2014
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 vivid

** Description changed:

  Here is the terminal output when ubuntu-bug is used:
  
  oem@u32:~$ ubuntu-bug compiz-gnome
  ERROR: hook /usr/share/apport/package-hooks/source_xorg.py crashed:
  Traceback (most recent call last):
-   File /usr/lib/python3/dist-packages/apport/report.py, line 197, in 
_run_hook
- symb['add_info'](report, ui)
-   File /usr/share/apport/package-hooks/source_xorg.py, line 677, in add_info
- attach_nvidia_info(report, ui)
-   File /usr/share/apport/package-hooks/source_xorg.py, line 521, in 
attach_nvidia_info
- attach_file(report, logfile)
-   File /usr/lib/python3/dist-packages/apport/hookutils.py, line 115, in 
attach_file
- report[key] = read_file(path, force_unicode=force_unicode)
-   File /usr/lib/python3/dist-packages/problem_report.py, line 563, in 
__setitem__
- assert k.replace('.', '').replace('-', '').replace('_', '').isalnum()
+   File /usr/lib/python3/dist-packages/apport/report.py, line 197, in 
_run_hook
+ symb['add_info'](report, ui)
+   File /usr/share/apport/package-hooks/source_xorg.py, line 677, in add_info
+ attach_nvidia_info(report, ui)
+   File /usr/share/apport/package-hooks/source_xorg.py, line 521, in 
attach_nvidia_info
+ attach_file(report, logfile)
+   File /usr/lib/python3/dist-packages/apport/hookutils.py, line 115, in 
attach_file
+ report[key] = read_file(path, force_unicode=force_unicode)
+   File /usr/lib/python3/dist-packages/problem_report.py, line 563, in 
__setitem__
+ assert k.replace('.', '').replace('-', '').replace('_', '').isalnum()
  AssertionError
  oem@u32:~$ [904:950:1119/112815:ERROR:nss_util.cc(821)] After loading Root 
Certs, loaded==false: NSS error code: -8018
  
  **
- /var/crash/ does not show a crash file, and the report have made/sent as 
usual; maybe a false positive.
+ /var/crash/ does not show a crash file, and the report have been made/sent as 
usual; maybe a false positive.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.14.7-0ubuntu10
  ProcVersionSignature: Ubuntu 3.18.0-3.4-generic 3.18.0-rc4
  Uname: Linux 3.18.0-3-generic i686
  NonfreeKernelModules: nvidia
  ApportLog:
-  
+ 
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Wed Nov 19 11:47:31 2014
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  hook /usr/share/apport/package-hooks/source_xorg.py crashed

Status in “apport” package in Ubuntu:
  New

Bug description:
  Here is the terminal output when ubuntu-bug is used:

  oem@u32:~$ ubuntu-bug compiz-gnome
  ERROR: hook /usr/share/apport/package-hooks/source_xorg.py crashed:
  Traceback (most recent call last):
    File /usr/lib/python3/dist-packages/apport/report.py, line 197, in 
_run_hook
  symb['add_info'](report, ui)
    File /usr/share/apport/package-hooks/source_xorg.py, line 677, in add_info
  attach_nvidia_info(report, ui)
    File /usr/share/apport/package-hooks/source_xorg.py, line 521, in 
attach_nvidia_info
  attach_file(report, logfile)
    File 

[Touch-packages] [Bug 1388239] Re: CPU: 1 PID: 11025 at /build/buildd/linux-3.16.0/drivers/media/v4l2-core/videobuf2-core.c:2120 __vb2_queue_cancel+0x116/0x180 [videobuf2_core]()

2014-11-19 Thread Serhiy Zahoriya
The camera freezes while using skype. Also, it's definitely not the
upgrader bug.

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

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

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

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Confirmed = Invalid

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

Title:
  CPU: 1 PID: 11025 at
  /build/buildd/linux-3.16.0/drivers/media/v4l2-core/videobuf2-core.c:2120
  __vb2_queue_cancel+0x116/0x180 [videobuf2_core]()

Status in “linux” package in Ubuntu:
  Confirmed
Status in “ubuntu-release-upgrader” package in Ubuntu:
  Invalid
Status in “v4l-utils” package in Ubuntu:
  New

Bug description:
  Found theses warnings when using the webcam on flash site under
  firefox.

  
  [418114.773634] [ cut here ]
  [418114.773674] WARNING: CPU: 1 PID: 11025 at 
/build/buildd/linux-3.16.0/drivers/media/v4l2-core/videobuf2-core.c:2120 
__vb2_queue_cancel+0x116/0x180 [videobuf2_core]()
  [418114.773677] Modules linked in: btrfs xor raid6_pq ufs qnx4 hfsplus hfs 
minix ntfs msdos jfs xfs libcrc32c xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
nf_conntrack ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables bridge stp 
llc snd_hrtimer nfsv3 rpcsec_gss_krb5 nfsv4 ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr bnep iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi rfcomm bluetooth 6lowpan_iphc nfsd auth_rpcgss binfmt_misc 
nfs_acl nfs lockd sunrpc fscache dm_crypt ir_lirc_codec lirc_dev ir_rc5_decoder 
ir_mce_kbd_decoder ir_sharp_decoder ir_jvc_decoder ir_sony_decoder 
ir_sanyo_decoder ir_rc6_decoder ir_nec_decoder rc_rc6_mce mceusb rc_core pl2303 
usbserial snd_hda_codec_realtek uvcvideo videobuf2_vmalloc
  [418114.773763]  videobuf2_memops snd_hda_codec_generic snd_usb_audio 
videobuf2_core v4l2_common snd_hda_intel videodev snd_hda_controller media 
joydev snd_usbmidi_lib snd_hda_codec snd_hwdep coretemp snd_pcm kvm_intel 
snd_seq_midi dm_multipath kvm snd_seq_midi_event scsi_dh snd_rawmidi snd_seq 
snd_seq_device serio_raw snd_timer cuse snd lpc_ich parport_pc soundcore ppdev 
mac_hid lp parport i915 hid_generic e1000e ptp video i2c_algo_bit 
drm_kms_helper usbhid drm firewire_ohci hid pata_acpi firewire_core crc_itu_t 
pps_core
  [418114.773829] CPU: 1 PID: 11025 Comm: plugin-containe Tainted: GW   
  3.16.0-23-lowlatency #31-Ubuntu
  [418114.773833] Hardware name: AOpen i965GMx-IF/i965GMx-IF, BIOS 6.00 PG 
10/03/2008
  [418114.773836]  0009 8800115c7c00 8177ec5d 

  [418114.773843]  8800115c7c38 8107183d  

  [418114.773848]  88008b044af0 88008b0448d8 8801215cb180 
8800115c7c48
  [418114.773854] Call Trace:
  [418114.773867]  [8177ec5d] dump_stack+0x4d/0x6f
  [418114.773875]  [8107183d] warn_slowpath_common+0x7d/0xa0
  [418114.773881]  [8107191a] warn_slowpath_null+0x1a/0x20
  [418114.773893]  [c0701596] __vb2_queue_cancel+0x116/0x180 
[videobuf2_core]
  [418114.773905]  [c0702cf5] vb2_internal_streamoff+0x35/0x90 
[videobuf2_core]
  [418114.773916]  [c0702db5] vb2_streamoff+0x65/0x70 [videobuf2_core]
  [418114.773928]  [c075e855] uvc_queue_enable+0x65/0xa0 [uvcvideo]
  [418114.773939]  [c076360a] uvc_video_enable+0x4a/0x1b0 [uvcvideo]
  [418114.773958]  [c07601e2] uvc_v4l2_do_ioctl+0x962/0x14b0 
[uvcvideo]
  [418114.773962]  [81192373] ? copy_page_from_iter_iovec+0x183/0x2d0
  [418114.773976]  [c06e02c6] video_usercopy+0x366/0x600 [videodev]
  [418114.773979]  [811e4bd9] ? __sb_start_write+0x49/0xf0
  [418114.773985]  [c075f880] ? uvc_v4l2_open+0x150/0x150 [uvcvideo]
  [418114.773988]  [811e4b61] ? __sb_end_write+0x31/0x60
  [418114.773992]  [811eaad3] ? pipe_write+0x393/0x450
  [418114.773997]  [c075ec3f] uvc_v4l2_ioctl+0x2f/0x70 [uvcvideo]
  [418114.774004]  [c06da734] v4l2_ioctl+0x154/0x190 [videodev]
  [418114.774008]  [811f6468] do_vfs_ioctl+0x2c8/0x4a0
  [418114.774011]  [812007de] ? __fget+0x6e/0xb0
  [418114.774029]  [811f66c1] SyS_ioctl+0x81/0xa0
  [418114.774039]  [8178666d] system_call_fastpath+0x1a/0x1f
  [418114.774084] ---[ end trace 36d13fa659268ece ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-release-upgrader-core 1:14.10.9
  ProcVersionSignature: Ubuntu 3.16.0-23.31-lowlatency 3.16.4
  Uname: Linux 3.16.0-23-lowlatency x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Fri Oct 31 20:35:55 2014
  InstallationDate: Installed on 

[Touch-packages] [Bug 1393846] Re: Screen Lock shows wrong wallpaper

2014-11-19 Thread Burko
Good point. I will do that later.

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

Title:
  Screen Lock shows wrong wallpaper

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Hi,

  after locking my screen the login screen displays the standard XFCE-
  Backgroung wallpaper. However, I am not using XFCE and I expect it to
  display either the standard wallpaper for the login screen or my
  personal wallpaper to be displayed.

  This is only one bug of a series of bugs concerning the screen lock.
  They are probably all related. I will provide the links to the bug
  reports later, until then you can find them in my personal profile.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Nov 18 17:12:00 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-13 (673 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2)
  LightdmConfig:
   [SeatDefaults]
   user-session=ubuntu
   greeter-session=unity-greeter
   allow-guest=true
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-09-14 (64 days ago)

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

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


[Touch-packages] [Bug 1394155] Re: Deadlock / crash of the dash possible through Today scope

2014-11-19 Thread Oliver Grawert
** Changed in: unity-scopes-shell (Ubuntu)
   Status: New = Confirmed

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

Title:
  Deadlock / crash of the dash possible through Today scope

Status in “unity-scopes-shell” package in Ubuntu:
  Confirmed

Bug description:
  On krillin:

  1) Go to the Today scope
  2) Scroll to the bottom
  3) Tap Tell me more...
  4) Scroll to the bottom again
  5) Tap Finished

  Hard lock / sometimes crash.

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

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


[Touch-packages] [Bug 1394155] [NEW] Deadlock / crash of the dash possible through Today scope

2014-11-19 Thread Pete Woods
Public bug reported:

On krillin:

1) Go to the Today scope
2) Scroll to the bottom
3) Tap Tell me more...
4) Scroll to the bottom again
5) Tap Finished

Hard lock / sometimes crash.

** Affects: unity-scopes-shell (Ubuntu)
 Importance: Critical
 Status: Confirmed


** Tags: rtm14

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

Title:
  Deadlock / crash of the dash possible through Today scope

Status in “unity-scopes-shell” package in Ubuntu:
  Confirmed

Bug description:
  On krillin:

  1) Go to the Today scope
  2) Scroll to the bottom
  3) Tap Tell me more...
  4) Scroll to the bottom again
  5) Tap Finished

  Hard lock / sometimes crash.

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

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


[Touch-packages] [Bug 1377258] Re: /etc/default/rcS: UTC=no: Utopic time is off by 4 hours after boot

2014-11-19 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 215-6ubuntu1

---
systemd (215-6ubuntu1) vivid; urgency=medium

  * Merge with Debian unstable. Remaining Ubuntu changes:
- Create disk/by-partlabel links for mmcblk partitions.
- Hack to support system-image read-only /etc, and modify files in
  /etc/writable/ instead.
- debian/rules: Drop doc dir symlinking. It creates havoc with dpkg
  upgrades, and we already have the automatic per-file symlinking.
- debian/rules: Add an epoch to libgudev.
- Don't install 80-networking.rules and the Debian *.agent scripts, we
  never supported them in Ubuntu. Instead, extend systemd's net device
  udev rule to trigger ifup@.service on network devices.
- Keep our much simpler udev maintainer scripts (all platforms must
  support udev, no debconf).
- Add udev Apport package hook.
- debian/extra/initramfs.top: Drop $ROOTDELAY, we do that in a more
  sensible way with wait-for-root. Will get applicable to Debian once
  Debian gets wait-for-root in initramfs-tools.
- debian/extra/initramfs.bottom: If LVM is installed, settle udev,
  otherwise we get missing LV symlinks. Workaround for LP #1185394.
- Add 40-hyperv-hotadd.rules: Workaround for LP #1233466.
- Mark graphics devices as PRIMARY_DEVICE_FOR_DISPLAY so that we can wait
  for those in plymouth.
- Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv
  dependencies to lvm2 which is handled with udev rules in Ubuntu.
- Add /run/shm - /dev/shm symlink in debian/tmpfiles.d/debian.conf
  (LP: #1320534, Closes: #674755).
- Lower Breaks: to lvm2 again. Our lvm2 package has always used udev for
  device setup, and thus is be compatible with systemd, too.
- Lower Breaks: to plymouth version which has the udev inotify fix in
  Ubuntu.
- Add HP ProLiant Server Cartridge power control support.
- Provide shutdown fallback for upstart. (LP: #1370329)
- Add boot-and-services autopkgtest to check booting with systemd-sysv and
  that the most crucial services behave as expected.
- debian/ifup@.service: Additionally run for auto class. We don't really
  support allow-hotplug in Ubuntu at the moment, so we need to deal with
  auto devices appearing after /etc/init.d/networking start already
  ran.  (LP: #1374521)

Upgrade fixes, keep until 16.04 LTS release:
- systemd Conflicts/Replaces/Provides systemd-services.
- Remove obsolete systemd-logind upstart job.

  * Clean up obsolete /etc/udev/rules.d/README on upgrades. (LP: #1381655)
  * Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In Ubuntu
we currently keep the setting whether the RTC is in local or UTC time
in /etc/default/rcS UTC=yes|no, instead of /etc/adjtime. (LP: #1377258)
  * Add systemd Apport hook for adding systemd-delta and information about
failed units.

systemd (215-6) unstable; urgency=medium

  [ Martin Pitt ]
  * Cherry-pick upstream patch to fix udev crash in link_config_get().
  * Cherry-pick upstream patch to fix tests in limited schroot environments.
  * Add d/p/Add-env-variable-for-machine-ID-path.patch: Allow specifying an
alternate /etc/machine-id location. This is necessary for running tests
as long as it isn't in our base images (see Debian #745876)
  * Run tests during package build. For the first round don't make them fatal
for now (that will happen once we see results from all the architectures).
  * Drop our Check-for-kmod-binary.patch as the upstream patch
units-conditionalize-static-device-node-logic-on-CAP.patch supersedes it.
  * Drop Use-comment-systemd.-syntax-in-systemd.mount-man-pag.patch, as
our util-linux is now recent enough. Bump dependency to = 2.21.
  * Adjust timedated and hostnamed autopkgtests to current upstream version.
  * Replace our Debian hwdb.bin location patch with what got committed
upstream. Run hwdb update with the new --usr option to keep current
behaviour.
  * debian/README.Debian: Document how to debug boot or shutdown problems with
the debug shell. (Closes: #766039)
  * Skip-99-systemd.rules-when-not-running-systemd-as-in.patch: Call path_id
under all init systems, to get consistent ID_PATH attributes. This is
required so that tools like systemd-rfkill can be used with SysVinit or
upstart scripts, too. (LP: #1387282)
  * Switch libpam-systemd dependencies to prefer systemd-shim over
systemd-sysv, to implement the CTTE decision #746578. This is a no-op on
systems which already have systemd-sysv installed, but will prevent
installing that on upgrades. (Closes: #769747)
  * Remove Tollef from Uploaders: as per his request. Thanks Tollef for all
you work!
  * net.agent: Properly close stdout/err FDs, to avoid long hangs during udev
settle. Thanks to Ben Hutchings! (Closes: #754987)
  * Bump Standards-Version to 3.9.6 (no changes necessary).

  [ Didier Roche ]
 

[Touch-packages] [Bug 1319582] Re: emulator: 'Failed to start RenderThread' after opening/closing applications

2014-11-19 Thread Loïc Molinari
On the (Qt) client side, if quit() is called on the QGuiApplication,
QtUbuntu releases all the allocated resources. At least it's been
designed and implemented like that when I started the project.

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

Title:
  emulator: 'Failed to start RenderThread' after opening/closing
  applications

Status in Mir:
  Triaged
Status in “android” package in Ubuntu:
  Confirmed
Status in “qtubuntu” package in Ubuntu:
  New

Bug description:
  Using:
  ubuntu-emulator  0.2+14.10.20140429.1-0ubuntu1
  ubuntu-emulator-runtime  20140501-2310-0ubuntu3

  Emulator starts fine, but after a few opening/closing apps in a row (a
  bunch of times, at least 20), emulator gives the 'Failed to start
  RenderThread' error.

  At that point the emulator can't do much more, and you need to abort
  and run it again.

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

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


[Touch-packages] [Bug 1394155] Re: Deadlock / crash of the dash possible through Today scope

2014-11-19 Thread Victor Tuson Palau
** Changed in: unity-scopes-shell (Ubuntu)
   Importance: Undecided = Critical

** Tags added: rtm14

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

Title:
  Deadlock / crash of the dash possible through Today scope

Status in “unity-scopes-shell” package in Ubuntu:
  Confirmed

Bug description:
  On krillin:

  1) Go to the Today scope
  2) Scroll to the bottom
  3) Tap Tell me more...
  4) Scroll to the bottom again
  5) Tap Finished

  Hard lock / sometimes crash.

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

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


[Touch-packages] [Bug 1079011] Re: stellarium assert failure: nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

2014-11-19 Thread Rebecca Palmer
** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  stellarium assert failure:  nv10_state_fb.c:50: get_rt_format:
  Assertion `0' failed.

Status in “flightgear” package in Ubuntu:
  New
Status in “mesa” package in Ubuntu:
  New
Status in “stellarium” package in Ubuntu:
  Confirmed

Bug description:
  Stellarium crashes a few seconds after displaying the startup screen
  with this message in terminal:

  nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

  I have an nvidia GeForce4 MX 4000 video card, and have installed
  libgl1-mesa-dri and libgl1-mesa-dri-experimental, version
  9.0-0ubuntu1.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: stellarium 0.11.3-1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Wed Nov 14 22:52:36 2012
  InstallationDate: Installed on 2012-04-05 (224 days ago)
  InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: stellarium
  UpgradeStatus: Upgraded to quantal on 2012-10-20 (25 days ago)

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

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


[Touch-packages] [Bug 1374040] Re: Searches in Ubuntu App Store aren't localized

2014-11-19 Thread James Tait
** Tags removed: touch-2014-11-13
** Tags added: touch-2014-11-20

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

Title:
  Searches in Ubuntu App Store aren't localized

Status in Click Package metadata search service:
  Fix Committed
Status in “unity-scope-click” package in Ubuntu:
  Invalid

Bug description:
  Core-app Calendar is now available in the Ubuntu App Store. Until
  recently, it was available in RTM image, as its name appeared
  localized (e.g. Calendario in Spanish). However, in order to install
  it, the app only appears in the Store in English.

  Test case.
  - Switch the phone to Spanish.
  - Reboot.
  - Go to Ubuntu App Store.
  - Search for Calendario.

  Expected result.
  - Calendar shows, with its translated name (.desktop file).

  Actual result.
  - No result.

  So, searches and results must support .desktop localization.

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-package-index/+bug/1374040/+subscriptions

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


[Touch-packages] [Bug 1260977] [NEW] No spellchecking in TextArea and TextField

2014-11-19 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Title say it all. There is no spellcheck like in normal Qt or GTK+
applications when doing text input.

Ubuntu already ships with some SDK apps -- e.g. Friends -- so please fix
this for 14.04 as this is a major regression.

** Affects: qtdeclarative-opensource-src (Ubuntu)
 Importance: Low
 Status: Confirmed


** Tags: text-input
-- 
No spellchecking in TextArea and TextField
https://bugs.launchpad.net/bugs/1260977
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to qtdeclarative-opensource-src in Ubuntu.

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


[Touch-packages] [Bug 1215686] Re: Some Chinese characters unreadable

2014-11-19 Thread Zoltan Balogh
** Project changed: ubuntu-ui-toolkit = qtdeclarative-opensource-src
(Ubuntu)

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

Title:
  Some Chinese characters unreadable

Status in “friends-app” package in Ubuntu:
  Confirmed
Status in “qtdeclarative-opensource-src” package in Ubuntu:
  Confirmed

Bug description:
  Some characters are unreadable in Twitter and Facebook posts that are written 
in Chinese.
  I am attaching the screenshot. The rectangles are supposed to be characters.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: friends-app 0.90.0bzr13.04.17-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Fri Aug 23 08:48:47 2013
  InstallationDate: Installed on 2012-08-12 (375 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: friends-app
  UpgradeStatus: Upgraded to raring on 2013-04-26 (118 days ago)

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

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


[Touch-packages] [Bug 1260977] Re: No spellchecking in TextArea and TextField

2014-11-19 Thread Zoltan Balogh
Sadly this problem is something what the UITK project can not address.

** Project changed: ubuntu-ui-toolkit = qtdeclarative-opensource-src
(Ubuntu)

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

Title:
  No spellchecking in TextArea and TextField

Status in “qtdeclarative-opensource-src” package in Ubuntu:
  Confirmed

Bug description:
  Title say it all. There is no spellcheck like in normal Qt or GTK+
  applications when doing text input.

  Ubuntu already ships with some SDK apps -- e.g. Friends -- so please
  fix this for 14.04 as this is a major regression.

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

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


[Touch-packages] [Bug 1356516] Re: consider shipping apparmor profile for webbrowser-app

2014-11-19 Thread Olivier Tilloy
I set the importance to Critical for the project task, as it’s required
to fix bug #1393515.

** Also affects: webbrowser-app
   Importance: Undecided
   Status: New

** Changed in: webbrowser-app
   Status: New = Triaged

** Changed in: webbrowser-app
 Assignee: (unassigned) = Olivier Tilloy (osomon)

** Changed in: webbrowser-app
   Importance: Undecided = Critical

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

Title:
  consider shipping apparmor profile for webbrowser-app

Status in Web Browser App:
  Triaged
Status in “webbrowser-app” package in Ubuntu:
  Confirmed

Bug description:
  It would be nice if webbrowser-app itself could ship an apparmor
  profile. Since we are already confining webapps, we can leverage aa-
  easyprof to generate the apparmor profile. Eg, in debian/rules could
  have a target :

  apparmor:
  aa-easyprof --policy-version=1.2 --policy-vendor=ubuntu \
  -t ubuntu-webapp \
  
--policy-groups=accounts,audio,content_exchange,content_exchange_source,location,networking,push-notification-client,video,webview
 \
   --template-var=@{APP_ID_DBUS}=webbrowser_2dapp \
   --template-var=@{APP_PKGNAME_DBUS}=webbrowser_2dapp \
   --template-var=@{APP_PKGNAME}=webbrowser-app \
   --template-var=@{CLICK_DIR}=/usr/share/webbrowser-app \
   --abstraction=user-tmp \
   --read-path=/usr/share/applications/ \
   --read-path=@{HOME}/.local/share/applications/ \
   --profile-name=webbrowser-app \
   --no-verify /usr/bin/webbrowser-app | \
   grep -v CLICK_DIR | \
   sed 's/signal peer=@{APP_PKGNAME}_\*_@{APP_VERSION},/signal 
peer=@{APP_PKGNAME},/g' \
    ./debian/usr.bin.webbrowser-app
   apparmor_parser -QTK ./debian/usr.bin.webbrowser-app

  In this manner, you could this to update the apparmor profile:
  $ debian/rules apparmor

  I use '--no-verify' because we need to very lightly tidy up the
  profile with the 'grep -v' and the 'sed', which is why after it is
  cleaned I run 'apparmor_parser -QTK' on the profile to verify it. This
  could probably be done as part of the build too. Once the profile is
  in place, you can simply do something along the lines of
  http://bazaar.launchpad.net/~jdstrand/ubuntu-system-settings/ubuntu-
  system-settings-lp1296415/revision/748.

  I have lightly tested this on the phone for the following:
   * http
   * https
   * sharing to messaging app
   * url-dispatcher via messaging-app to open a link (with the browser open and 
closed)
   * maps.google.com (prompted for access)
   * youtube (one denial: apparmor=DENIED operation=dbus_method_call  
bus=system path=/com/canonical/Unity/Screen 
interface=com.canonical.Unity.Screen member=keepDisplayOn mask=send 
name=com.canonical.Unity.Screen pid=12566 profile=webbrowser-app 
peer_pid=1575 peer_profile=unconfined)
   * html5.grooveshark.com
   * grooveshark via music scope

  I also even more lightly tested it on the desktop, and it appears to
  work ok.

  Note: there is one denial on startup, but this is expected:
  Aug 13 13:21:33 localhost dbus[10795]: apparmor=DENIED 
operation=dbus_bind  bus=session name=org.freedesktop.Application 
mask=bind pid=18407 profile=webbrowser-app

  I may be out of date on me phone (it only has promoted), but this
  should go away when the webbrowser-app portion of bug #1342129 is
  fixed.

  Note2: the youtube denial will go away when oxide has media-hub
  integration. If we really want this profile for rtm and oxide doesn't
  have media-hub integration, I would need to either update aa-easyprof
  to allow adding dbus rules, or we can add an additional sed to add a
  rule for this.

  Note3: instead of specifying all the command line args to aa-easyprof,
  we can also supply a json file for it to use.

  Note4: it might be simpler to supply a easyprof json manifest file, which 
does the same as the above command line version. Here is an updated command to 
create the file, which also adds a rule for controlling the display:
  apparmor:
  aa-easyprof -m ./debian/webbrowser-app-apparmor.manifest \
  --no-verify | \
  egrep -v '(# Click packages|CLICK_DIR)' | \
  sed 's/signal peer=@{APP_PKGNAME}_\*_@{APP_VERSION},/signal 
peer=@{APP_PKGNAME},/g' | \
  sed 's:^}:  dbus (receive,send) bus=system 
path=/com/canonical/Unity/Screen,\n}:g' \ 
./debian/usr.bin.webbrowser-app
   apparmor_parser -QTK ./debian/usr.bin.webbrowser-app

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

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


[Touch-packages] [Bug 1079011] Re: stellarium assert failure: nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

2014-11-19 Thread Rebecca Palmer
That message means invalid/unsupported buffer format (
http://sources.debian.net/src/mesa/10.3.2-1/src/mesa/drivers/dri/nouveau/nv10_state_fb.c
), and as it appears to refer to an internal nouveau buffer rather than
a passed-in texture, I suspect this is actually a mesa/nouveau bug.

As I do not have the hardware to test this myself, please do (in a
terminal):

$ sudo apt-get install libgl1-mesa-dri-dbg gdb
$ gdb --args fgfs
[or gdb --args stellarium, whichever is easier to reproduce the crash in]
(gdb) set pagination 0
(gdb) run
[wait for crash]
(gdb) thread apply all bt full

and post the ouput here.

** Changed in: mesa (Ubuntu)
   Status: New = Incomplete

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

Title:
  stellarium assert failure:  nv10_state_fb.c:50: get_rt_format:
  Assertion `0' failed.

Status in “flightgear” package in Ubuntu:
  New
Status in “mesa” package in Ubuntu:
  Incomplete
Status in “stellarium” package in Ubuntu:
  Confirmed

Bug description:
  Stellarium crashes a few seconds after displaying the startup screen
  with this message in terminal:

  nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

  I have an nvidia GeForce4 MX 4000 video card, and have installed
  libgl1-mesa-dri and libgl1-mesa-dri-experimental, version
  9.0-0ubuntu1.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: stellarium 0.11.3-1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Wed Nov 14 22:52:36 2012
  InstallationDate: Installed on 2012-04-05 (224 days ago)
  InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: stellarium
  UpgradeStatus: Upgraded to quantal on 2012-10-20 (25 days ago)

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

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


[Touch-packages] [Bug 1319542] Re: Unity urgent animation needs an adjustable time length.

2014-11-19 Thread josh
This actually is a massive issue at work for me. I recently switched
from Windows to Ubuntu and my colleagues now regularly complain about me
not answering their Jabber requests.

If anyone knows of a workaround for Psi (as long as this is not fixed),
i would be more than happy to be informed.

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

Title:
  Unity urgent animation needs an adjustable time length.

Status in Ayatana Design:
  New
Status in Unity:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 14.04, fully up to date, Unity Version:
  7.2.0+14.04.20140416-0ubuntu1

  The Unity launcher in my setup is not hidden. It is always visible.

  The current behavior of the urgent animation goes like this:

  1) An application needs attention (such as an instant message through Empathy 
or Skype)
  2) Icon wiggles for about one second
  3) Once the wiggle is over, the icon remains highlighted

  The problem is with step 2. The icon never reinitializes any sort of
  motion to catch the user's eye. People are busy. People are frequently
  multitasking. In a lot of cases, people are using multiple monitors or
  very widescreen monitors and their field of vision is in an entirely
  different place altogether. There really should be some sort of
  repeated motion that takes place to grab the users attention, thereby
  signifying that an application needs attention.

  A few possible solutions would be:

  A) Let the icon wiggle indefinitely until the user clicks on it. This
  is a bit obnoxious, because you have to consider the situations where
  a user might notice it, but might be too deep in a specific project to
  address it right away. This would stand as a potential distraction
  and/or annoyance, though it *would* eliminate the chances of the
  notification going missed.

  B) To allow the user to adjust the time frame in which the wiggle
  animation takes place. That way instead of one second, perhaps the
  user might want it to last 10 seconds, or 30 seconds, etc. There are
  times where I am engaging in an active conversation but switching to
  another application frequently. At times, I miss a message altogether
  despite the fact I'm looking at the screen. This is entirely due to
  the short time frame in which the urgent animation is moving. The
  length of time in which it moves is, more times than not, simply not
  long enough to be noticed. If the one second span could be adjusted,
  and say I have it set to 5 seconds, or 10 seconds, surely I would
  notice it.

  C) The most optimum solution in my opinion is to make the urgent
  animation continually come up over a specified span of time. Example,
  I receive a notification from Empathy, but I miss it. It wiggles and
  shortly thereafter stops wiggling, thereby just sitting idle but with
  the icon highlighted. A short time later, perhaps 30 seconds later, it
  wiggles again, and continues onward in 30 second intervals
  indefinitely until the user gives attention to the application
  requesting it.

  Option C would circumvent a potential annoyance factor of option A,
  and it would work around the fact that option B) would require another
  thing to change in the settings menu. All in all, there *really*
  should be a way for a user to more easily see that an application
  needs attention. A simple one second wiggle is not enough. A
  background highlight is not enough as it does not move to be noticed.
  You only notice a background highlight if you specifically look at the
  icon, whereas a motion-based notification (wiggle, etc) actually
  'grabs' your attention to be noticed.

  Thank you for your time, consideration, and hard work. If I can be of
  any further assistance please let me know. Thank you again!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed May 14 15:28:24 2014
  InstallationDate: Installed on 2014-04-04 (40 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140330)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1319542/+subscriptions

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


[Touch-packages] [Bug 1335002] Re: Chinese input method does not work after enable Chinese keyboard in Ubuntu Phone

2014-11-19 Thread Michael Sheldon
** Changed in: ubuntu-keyboard
   Status: Confirmed = In Progress

** Changed in: ubuntu-keyboard (Ubuntu RTM)
   Status: New = In Progress

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New = In Progress

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

Title:
  Chinese input method does not work after enable Chinese keyboard in
  Ubuntu Phone

Status in Ubuntu Keyboard:
  In Progress
Status in “ubuntu-keyboard” package in Ubuntu:
  In Progress
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  In Progress

Bug description:
  Reproduce steps:

  1, enable Chinese keyboard in system settings
  2, launch an app can input text like notes
  3, long press global icon and switch Chinese

  Expecting:
  user can input Chinese like press 'n' and 'i' then 你 should show up on 
candidate bar

  Actual:
  no candidate bar, so still input English

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

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


[Touch-packages] [Bug 1393487] Re: swiping word ribbon to right causes words to be repeated

2014-11-19 Thread Launchpad Bug Tracker
** Branch linked: lp:~michael-sheldon/ubuntu-keyboard/fix-1393487

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

Title:
  swiping word ribbon to right causes words to be repeated

Status in Ubuntu Keyboard:
  New
Status in “ubuntu-keyboard” package in Ubuntu:
  New
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  rtm build 162 on krillin

  Steps to reproduce:
  - open messaging app
  - type Hello in the message field
  - see the word Hello show up by itself in the list
  - swipe word ribbon to the right and release
  - now there are 2 Hello words in the ribbon
  - continue to swipe and release the word ribbon and you get a repeated word 
each time

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

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


[Touch-packages] [Bug 1393915] Re: uuidgen --random requires an argument

2014-11-19 Thread Kurt Huwig
It does also happen in 12.04.5 LTS

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

Title:
  uuidgen --random requires an argument

Status in “util-linux” package in Ubuntu:
  Fix Released

Bug description:
  The man page of 'uuidgen' reports the options -r and --random as
  equivalent:

 -r, --random
Generate a random-based UUID.  This method creates a UUID 
consisting  mostly  of  random
bits.   It  requires that the operating system have a high 
quality random number genera‐
tor, such as /dev/random.

  But --random requires an argument:

  kurt@rodin:~$ uuidgen -r
  4aca676a-a3f1-4217-a35d-031c376c6274
  kurt@rodin:~$ uuidgen --random
  uuidgen: option '--random' requires an argument

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

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


[Touch-packages] [Bug 1388239] Re: CPU: 1 PID: 11025 at /build/buildd/linux-3.16.0/drivers/media/v4l2-core/videobuf2-core.c:2120 __vb2_queue_cancel+0x116/0x180 [videobuf2_core]()

2014-11-19 Thread Serhiy Zahoriya
And it doesn't work at all with 3.18.0-031800rc5-generic kernel:

[  592.517167] uvcvideo: Failed to set UVC commit control : -32 (exp. 26).
[  592.517173] [ cut here ]
[  592.517187] WARNING: CPU: 1 PID: 3390 at 
/home/apw/COD/linux/drivers/media/v4l2-core/videobuf2-core.c:2135 
__vb2_queue_cancel+0x1d0/0x240 [videobuf2_core]()
[  592.517188] Modules linked in: snd_hda_codec_hdmi intel_rapl 
x86_pkg_temp_thermal snd_hda_codec_realtek intel_powerclamp 
snd_hda_codec_generic coretemp kvm_intel gpio_ich kvm hid_generic snd_hda_intel 
snd_usb_audio snd_hda_controller snd_usbmidi_lib snd_hda_codec snd_hwdep 
crct10dif_pclmul crc32_pclmul snd_seq_midi snd_seq_midi_event 
ghash_clmulni_intel snd_rawmidi aesni_intel aes_x86_64 uvcvideo lrw gf128mul 
glue_helper videobuf2_vmalloc ablk_helper cryptd videobuf2_memops 
videobuf2_core usbhid snd_pcm v4l2_common snd_seq serio_raw hid videodev media 
snd_seq_device lpc_ich snd_timer snd mei_me mei soundcore 8250_fintek 
tpm_infineon shpchp mac_hid rfcomm bnep bluetooth binfmt_misc parport_pc ppdev 
lp parport nouveau mxm_wmi video i2c_algo_bit ttm drm_kms_helper drm ahci r8169 
libahci mii wmi
[  592.517243] CPU: 1 PID: 3390 Comm: guvcview Not tainted 
3.18.0-031800rc5-generic #201411162035
[  592.517245] Hardware name: MSI MS-7681/P67A-GD53 (MS-7681), BIOS V1.9 
03/02/2011
[  592.517247]  0857 8800b9913b78 8179f8d5 
0007
[  592.517249]   8800b9913bb8 8106eafc 
841aa000
[  592.517251]  8800b9f868d8  8800b9f86b18 
88022f3a2540
[  592.517254] Call Trace:
[  592.517260]  [8179f8d5] dump_stack+0x46/0x58
[  592.517265]  [8106eafc] warn_slowpath_common+0x8c/0xc0
[  592.517268]  [8106eb4a] warn_slowpath_null+0x1a/0x20
[  592.517272]  [c051f8a0] __vb2_queue_cancel+0x1d0/0x240 
[videobuf2_core]
[  592.517276]  [c05212f5] vb2_internal_streamoff+0x35/0xc0 
[videobuf2_core]
[  592.517280]  [c05213b5] vb2_streamoff+0x35/0x60 [videobuf2_core]
[  592.517284]  [c0554055] uvc_queue_enable+0x75/0xb0 [uvcvideo]
[  592.517288]  [c0559463] uvc_video_enable+0x133/0x150 [uvcvideo]
[  592.517292]  [c0555d5c] uvc_v4l2_do_ioctl+0x85c/0x1300 [uvcvideo]
[  592.517296]  [811a14e0] ? do_linear_fault.isra.61+0x70/0x80
[  592.517298]  [811a15f6] ? handle_pte_fault+0x76/0x1b0
[  592.517304]  [c045fadc] video_usercopy+0x29c/0x4a0 [videodev]
[  592.517308]  [c000] ? uvc_ioctl_ctrl_map+0x1c0/0x1c0 [uvcvideo]
[  592.517310]  [811a1d71] ? handle_mm_fault+0xb1/0x160
[  592.517314]  [8105c24c] ? __do_page_fault+0x28c/0x550
[  592.517318]  [c05547d4] uvc_v4l2_ioctl+0x34/0x70 [uvcvideo]
[  592.517323]  [c045b723] v4l2_ioctl+0x133/0x160 [videodev]
[  592.517326]  [811fc2c5] do_vfs_ioctl+0x75/0x2c0
[  592.517329]  [812068f5] ? __fget_light+0x25/0x70
[  592.517332]  [811fc5a1] SyS_ioctl+0x91/0xb0
[  592.517335]  [817ad12d] system_call_fastpath+0x16/0x1b
[  592.517337] ---[ end trace a7062800a721293e ]---
[  592.740716] uvcvideo: Failed to set UVC commit control : -32 (exp. 26).
[  592.741339] uvcvideo: Failed to set UVC commit control : -32 (exp. 26).

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

Title:
  CPU: 1 PID: 11025 at
  /build/buildd/linux-3.16.0/drivers/media/v4l2-core/videobuf2-core.c:2120
  __vb2_queue_cancel+0x116/0x180 [videobuf2_core]()

Status in “linux” package in Ubuntu:
  Confirmed
Status in “ubuntu-release-upgrader” package in Ubuntu:
  Invalid
Status in “v4l-utils” package in Ubuntu:
  New

Bug description:
  Found theses warnings when using the webcam on flash site under
  firefox.

  
  [418114.773634] [ cut here ]
  [418114.773674] WARNING: CPU: 1 PID: 11025 at 
/build/buildd/linux-3.16.0/drivers/media/v4l2-core/videobuf2-core.c:2120 
__vb2_queue_cancel+0x116/0x180 [videobuf2_core]()
  [418114.773677] Modules linked in: btrfs xor raid6_pq ufs qnx4 hfsplus hfs 
minix ntfs msdos jfs xfs libcrc32c xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
nf_conntrack ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables bridge stp 
llc snd_hrtimer nfsv3 rpcsec_gss_krb5 nfsv4 ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr bnep iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi rfcomm bluetooth 6lowpan_iphc nfsd auth_rpcgss binfmt_misc 
nfs_acl nfs lockd sunrpc fscache dm_crypt ir_lirc_codec lirc_dev ir_rc5_decoder 
ir_mce_kbd_decoder ir_sharp_decoder ir_jvc_decoder ir_sony_decoder 
ir_sanyo_decoder ir_rc6_decoder ir_nec_decoder rc_rc6_mce mceusb rc_core pl2303 
usbserial snd_hda_codec_realtek uvcvideo videobuf2_vmalloc
  [418114.773763]  videobuf2_memops 

[Touch-packages] [Bug 1394155] Re: Deadlock / crash of the dash possible through Today scope

2014-11-19 Thread Pete Woods
Program received signal SIGSEGV, Segmentation fault.
0xb634af9c in std::basic_stringchar, std::char_traitschar, 
std::allocatorchar ::basic_string(std::string const) ()
   from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
(gdb) bt
#0  0xb634af9c in std::basic_stringchar, std::char_traitschar, 
std::allocatorchar ::basic_string(std::string const) ()
   from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#1  0xadac54be in unity::scopes::Category::title() const () from 
/usr/lib/arm-linux-gnueabihf/libunity-scopes.so.3
#2  0xadb6dfa2 in title (this=optimized out)
at 
/build/buildd/unity-scopes-shell-0.5.4+14.10.20141029.1~rtm/src/Unity/categories.cpp:83
#3  scopes_ng::Categories::data (this=optimized out, index=..., 
role=optimized out)
at 
/build/buildd/unity-scopes-shell-0.5.4+14.10.20141029.1~rtm/src/Unity/categories.cpp:520
#4  0xb652ee4a in QSortFilterProxyModel::data (this=optimized out, index=..., 
role=1)
at itemmodels/qsortfilterproxymodel.cpp:1955
#5  0xb6ab80de in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

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

Title:
  Deadlock / crash of the dash possible through Today scope

Status in “unity-scopes-shell” package in Ubuntu:
  Confirmed

Bug description:
  On krillin:

  1) Go to the Today scope
  2) Scroll to the bottom
  3) Tap Tell me more...
  4) Scroll to the bottom again
  5) Tap Finished

  Hard lock / sometimes crash.

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

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


[Touch-packages] [Bug 1394155] Re: Deadlock / crash of the dash possible through Today scope

2014-11-19 Thread Pete Woods
Program received signal SIGSEGV, Segmentation fault.
unity::scopes::Category::title (this=0x50) at 
/build/buildd/unity-scopes-api-0.6.7+15.04.20141107.1~rtm/src/scopes/Category.cpp:56
56  
/build/buildd/unity-scopes-api-0.6.7+15.04.20141107.1~rtm/src/scopes/Category.cpp:
 No such file or directory.
(gdb) bt
#0  unity::scopes::Category::title (this=0x50)
at 
/build/buildd/unity-scopes-api-0.6.7+15.04.20141107.1~rtm/src/scopes/Category.cpp:56
#1  0xadd9dfa2 in title (this=optimized out)
at 
/build/buildd/unity-scopes-shell-0.5.4+14.10.20141029.1~rtm/src/Unity/categories.cpp:83
#2  scopes_ng::Categories::data (this=optimized out, index=..., 
role=optimized out)
at 
/build/buildd/unity-scopes-shell-0.5.4+14.10.20141029.1~rtm/src/Unity/categories.cpp:520
#3  0xb652ee4a in QSortFilterProxyModel::data (this=optimized out, index=..., 
role=1)
at itemmodels/qsortfilterproxymodel.cpp:1955
#4  0xb6ab80de in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

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

Title:
  Deadlock / crash of the dash possible through Today scope

Status in “unity-scopes-shell” package in Ubuntu:
  Confirmed

Bug description:
  On krillin:

  1) Go to the Today scope
  2) Scroll to the bottom
  3) Tap Tell me more...
  4) Scroll to the bottom again
  5) Tap Finished

  Hard lock / sometimes crash.

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

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


[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically

2014-11-19 Thread Marc Deslauriers
** Description changed:

+ [SRU Request]
+ 
+ Due to a change in Upstart behaviour, the statd daemon no longer starts
+ automatically at boot, resulting in nfs mounts not being mounted at
+ boot.
+ 
+ This has been corrected by modifying the statd upstart job to wait for
+ the rpcbind job to start, instead of waiting for the compatibility
+ portmap event.
+ 
+ [Test Case]
+ 1- set up an NFS mount in /etc/fstab
+ 2- Reboot, notice the directory didn't get mounted
+ 3- Install update
+ 4- Reboot, notice the directory is mounted
+ 
+ [Regression Potential]
+ The upstart jobs to get the proper daemons started up at boot have complex 
relationships, and have suffered from race conditions in the past. Although 
this change is small, it may slightly change previous behaviour. Of course, not 
having it work at all is worse than having a possible race condition, so this 
fix is unlikely to be any worse than the broken behaviour.
+ 
+ 
+ Original description: 
+ 
  After upgrading to 14.10 (fresh install) my NFS drive does no longer
  mounts automatically at boot when the network is up and running.
  Manually running mount -a mounts the drive as expected and hacking a
  mount -a command into mountall-net.conf makes my system function
  normally again. Trying to manually to killall -USR1 mountall does not
  work.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: mountall 2.54build1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 10 20:37:39 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (1 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161

** Changed in: nfs-utils (Ubuntu Utopic)
   Status: Confirmed = In Progress

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

Title:
  14.10: NFS drives in fstab not mounted automatically

Status in “nfs-utils” package in Ubuntu:
  Fix Released
Status in “upstart” package in Ubuntu:
  Confirmed
Status in “nfs-utils” source package in Utopic:
  In Progress
Status in “upstart” source package in Utopic:
  Confirmed
Status in “nfs-utils” source package in Vivid:
  Fix Released
Status in “upstart” source package in Vivid:
  Confirmed

Bug description:
  [SRU Request]

  Due to a change in Upstart behaviour, the statd daemon no longer
  starts automatically at boot, resulting in nfs mounts not being
  mounted at boot.

  This has been corrected by modifying the statd upstart job to wait for
  the rpcbind job to start, instead of waiting for the compatibility
  portmap event.

  [Test Case]
  1- set up an NFS mount in /etc/fstab
  2- Reboot, notice the directory didn't get mounted
  3- Install update
  4- Reboot, notice the directory is mounted

  [Regression Potential]
  The upstart jobs to get the proper daemons started up at boot have complex 
relationships, and have suffered from race conditions in the past. Although 
this change is small, it may slightly change previous behaviour. Of course, not 
having it work at all is worse than having a possible race condition, so this 
fix is unlikely to be any worse than the broken behaviour.

  
  Original description: 

  After upgrading to 14.10 (fresh install) my NFS drive does no longer
  mounts automatically at boot when the network is up and running.
  Manually running mount -a mounts the drive as expected and hacking a
  mount -a command into mountall-net.conf makes my system function
  normally again. Trying to manually to killall -USR1 mountall does not
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: mountall 2.54build1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 10 20:37:39 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (1 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post 

[Touch-packages] [Bug 1308338] Re: Ubuntu 12.04 LTS - 14.04 LTS upgrade fails if Flight Gear installed

2014-11-19 Thread Rebecca Palmer
This isn't a flightgear bug, it's an apt/ubuntu-release-upgrader bug,
and according to #8 is already fixed (in later releases, obviously this
won't help 12.04 - 14.04).

Removing flightgear and reinstalling it after the upgrade should be fine
as a workaround, since flightgear would be being upgraded anyway.

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

** Changed in: apt (Ubuntu)
   Status: New = Fix Released

** Changed in: flightgear (Ubuntu)
   Status: Triaged = Invalid

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

Title:
  Ubuntu 12.04 LTS - 14.04 LTS upgrade fails if Flight Gear installed

Status in Release Notes for Ubuntu:
  Fix Released
Status in “apt” package in Ubuntu:
  Fix Released
Status in “flightgear” package in Ubuntu:
  Invalid

Bug description:
  Removing Flight Gear fixes the issue.

  ---
  Broken flightgear:amd64 Riippuvuudet on libopenscenegraph99 [ amd64 ]  none 
- 3.2.0~rc1-4  ( universe/libs )
Considering libopenscenegraph99:amd64 3 as a solution to flightgear:amd64 -1
MarkKeep flightgear [ amd64 ]  2.4.0-1 - 3.0.0-1  ( universe/games ) FU=0
Holding Back flightgear:amd64 rather than change libopenscenegraph99:amd64
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: update-manager 1:0.156.14.13
  ProcVersionSignature: Ubuntu 3.11.0-19.33~precise1-generic 3.11.10.5
  Uname: Linux 3.11.0-19-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Wed Apr 16 09:10:48 2014
  GsettingsChanges:
   com.ubuntu.update-manager first-run false
   com.ubuntu.update-manager launch-time 1397628529
   com.ubuntu.update-manager window-height 636
   com.ubuntu.update-manager window-width 600
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: update-manager
  Symptom: ubuntu-release-upgrader-core
  UpgradeStatus: Upgraded to precise on 2014-04-16 (0 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1308338/+subscriptions

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


[Touch-packages] [Bug 1394178] [NEW] [EG45M-UD2H, Realtek ALC889A, Pink Mic, Front] Recording problem, only SPDIF input available

2014-11-19 Thread Eugene
Public bug reported:

I'm using Ubuntu 14.04.1 LTS.
There is only Digital input in Input section and no Analog input. I can not use 
my microphone.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  eugene 2690 F pulseaudio
CurrentDesktop: Unity
Date: Wed Nov 19 14:31:06 2014
InstallationDate: Installed on 2014-07-16 (125 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_Jack: Pink Mic, Front
Symptom_Type: Only some of inputs are working
Title: [EG45M-UD2H, Realtek ALC889A, Pink Mic, Front] Recording problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/09/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F3
dmi.board.name: EG45M-UD2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd04/09/2009:svnGigabyteTechnologyCo.,Ltd.:pnEG45M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEG45M-UD2H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EG45M-UD2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

Title:
  [EG45M-UD2H, Realtek ALC889A, Pink Mic, Front] Recording problem, only
  SPDIF input available

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

Bug description:
  I'm using Ubuntu 14.04.1 LTS.
  There is only Digital input in Input section and no Analog input. I can not 
use my microphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eugene 2690 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov 19 14:31:06 2014
  InstallationDate: Installed on 2014-07-16 (125 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Pink Mic, Front
  Symptom_Type: Only some of inputs are working
  Title: [EG45M-UD2H, Realtek ALC889A, Pink Mic, Front] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F3
  dmi.board.name: EG45M-UD2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd04/09/2009:svnGigabyteTechnologyCo.,Ltd.:pnEG45M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEG45M-UD2H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EG45M-UD2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Touch-packages] [Bug 1394178] Re: [EG45M-UD2H, Realtek ALC889A, Pink Mic, Front] Recording problem, only SPDIF input available

2014-11-19 Thread Eugene
** Attachment added: pulseverbose.log
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1394178/+attachment/4263700/+files/pulseverbose.log

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

Title:
  [EG45M-UD2H, Realtek ALC889A, Pink Mic, Front] Recording problem, only
  SPDIF input available

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

Bug description:
  I'm using Ubuntu 14.04.1 LTS.
  There is only Digital input in Input section and no Analog input. I can not 
use my microphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eugene 2690 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov 19 14:31:06 2014
  InstallationDate: Installed on 2014-07-16 (125 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Pink Mic, Front
  Symptom_Type: Only some of inputs are working
  Title: [EG45M-UD2H, Realtek ALC889A, Pink Mic, Front] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F3
  dmi.board.name: EG45M-UD2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd04/09/2009:svnGigabyteTechnologyCo.,Ltd.:pnEG45M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEG45M-UD2H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EG45M-UD2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Touch-packages] [Bug 1291696] Re: sshd does not pass DISPLAY even if adviced to forward X11 connections

2014-11-19 Thread David
I was also affected. But the solution posted by Dmitry Mn solved it.

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

Title:
  sshd does not pass DISPLAY even if adviced to forward X11 connections

Status in “openssh” package in Ubuntu:
  Confirmed

Bug description:
  sshd does not set DISPLAY-variable even if using ssh -l user -X
  serveraddr connecting the server.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssh-server 1:6.5p1-6
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  Date: Thu Mar 13 01:45:19 2014
  InstallationDate: Installed on 2014-01-31 (40 days ago)
  InstallationMedia: Ubuntu-Server 13.10 Saucy Salamander - Release amd64 
(20131016)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssh
  UpgradeStatus: Upgraded to trusty on 2014-01-31 (40 days ago)

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

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


[Touch-packages] [Bug 1394187] [NEW] package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

2014-11-19 Thread dust
Public bug reported:

after reboot the error message came up

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: shared-mime-info 1.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
Date: Sun Nov 16 07:59:11 2014
DuplicateSignature: package:shared-mime-info:1.2-0ubuntu3:subprocess installed 
post-installation script returned error exit status 139
ErrorMessage: subprocess installed post-installation script returned error exit 
status 139
InstallationDate: Installed on 2014-10-04 (45 days ago)
InstallationMedia: Lubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
UpgradeStatus: Upgraded to utopic on 2014-10-23 (26 days ago)

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

Title:
  package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 139

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

Bug description:
  after reboot the error message came up

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: shared-mime-info 1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  Date: Sun Nov 16 07:59:11 2014
  DuplicateSignature: package:shared-mime-info:1.2-0ubuntu3:subprocess 
installed post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2014-10-04 (45 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
  UpgradeStatus: Upgraded to utopic on 2014-10-23 (26 days ago)

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

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


[Touch-packages] [Bug 1394187] Re: package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

2014-11-19 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 shared-mime-info in
Ubuntu.
https://bugs.launchpad.net/bugs/1394187

Title:
  package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 139

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

Bug description:
  after reboot the error message came up

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: shared-mime-info 1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  Date: Sun Nov 16 07:59:11 2014
  DuplicateSignature: package:shared-mime-info:1.2-0ubuntu3:subprocess 
installed post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2014-10-04 (45 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
  UpgradeStatus: Upgraded to utopic on 2014-10-23 (26 days ago)

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

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


[Touch-packages] [Bug 1394178] Re: [EG45M-UD2H, Realtek ALC889A, Pink Mic, Front] Recording problem, only SPDIF input available

2014-11-19 Thread Raymond
ports:
analog-input-microphone-front: Front Microphone (priority 8500, 
latency offset 0 usec, available: no)
properties:
device.icon_name = audio-input-microphone
analog-input-microphone-rear: Rear Microphone (priority 8200, 
latency offset 0 usec, available: no)
properties:
device.icon_name = audio-input-microphone
analog-input-linein: Line In (priority 8100, latency offset 0 
usec, available: no)


front mic is not plugged 


control.41 {
iface CARD
name 'Front Mic Jack'
value false
comment {
access read
type BOOLEAN
count 1
}
}
control.42 {
iface CARD
name 'Rear Mic Jack'
value false
comment {
access read
type BOOLEAN
count 1
}
}
control.43 {
iface CARD
name 'Line Jack'
value false
comment {
access read
type BOOLEAN
count 1
}
}

control.50 {
iface CARD
name 'SPDIF In Phantom Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}


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

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

Title:
  [EG45M-UD2H, Realtek ALC889A, Pink Mic, Front] Recording problem, only
  SPDIF input available

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

Bug description:
  I'm using Ubuntu 14.04.1 LTS.
  There is only Digital input in Input section and no Analog input. I can not 
use my microphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eugene 2690 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov 19 14:31:06 2014
  InstallationDate: Installed on 2014-07-16 (125 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Pink Mic, Front
  Symptom_Type: Only some of inputs are working
  Title: [EG45M-UD2H, Realtek ALC889A, Pink Mic, Front] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F3
  dmi.board.name: EG45M-UD2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd04/09/2009:svnGigabyteTechnologyCo.,Ltd.:pnEG45M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEG45M-UD2H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EG45M-UD2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Touch-packages] [Bug 1388239] Re: CPU: 1 PID: 11025 at /build/buildd/linux-3.16.0/drivers/media/v4l2-core/videobuf2-core.c:2120 __vb2_queue_cancel+0x116/0x180 [videobuf2_core]()

2014-11-19 Thread Serhiy Zahoriya
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/media/v4l2-core/videobuf2-core.c?id=refs/tags/v3.18-rc5#n2135

 __vb2_queue_cancel() - cancel and stop (pause) streaming
 Removes all queued buffers from driver's queue and all buffers queued by
 userspace from videobuf's queue. Returns to state after reqbufs.

Why does it want to stop  streaming in the first place?

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

Title:
  CPU: 1 PID: 11025 at
  /build/buildd/linux-3.16.0/drivers/media/v4l2-core/videobuf2-core.c:2120
  __vb2_queue_cancel+0x116/0x180 [videobuf2_core]()

Status in “linux” package in Ubuntu:
  Confirmed
Status in “ubuntu-release-upgrader” package in Ubuntu:
  Invalid
Status in “v4l-utils” package in Ubuntu:
  New

Bug description:
  Found theses warnings when using the webcam on flash site under
  firefox.

  
  [418114.773634] [ cut here ]
  [418114.773674] WARNING: CPU: 1 PID: 11025 at 
/build/buildd/linux-3.16.0/drivers/media/v4l2-core/videobuf2-core.c:2120 
__vb2_queue_cancel+0x116/0x180 [videobuf2_core]()
  [418114.773677] Modules linked in: btrfs xor raid6_pq ufs qnx4 hfsplus hfs 
minix ntfs msdos jfs xfs libcrc32c xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
nf_conntrack ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables bridge stp 
llc snd_hrtimer nfsv3 rpcsec_gss_krb5 nfsv4 ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr bnep iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi rfcomm bluetooth 6lowpan_iphc nfsd auth_rpcgss binfmt_misc 
nfs_acl nfs lockd sunrpc fscache dm_crypt ir_lirc_codec lirc_dev ir_rc5_decoder 
ir_mce_kbd_decoder ir_sharp_decoder ir_jvc_decoder ir_sony_decoder 
ir_sanyo_decoder ir_rc6_decoder ir_nec_decoder rc_rc6_mce mceusb rc_core pl2303 
usbserial snd_hda_codec_realtek uvcvideo videobuf2_vmalloc
  [418114.773763]  videobuf2_memops snd_hda_codec_generic snd_usb_audio 
videobuf2_core v4l2_common snd_hda_intel videodev snd_hda_controller media 
joydev snd_usbmidi_lib snd_hda_codec snd_hwdep coretemp snd_pcm kvm_intel 
snd_seq_midi dm_multipath kvm snd_seq_midi_event scsi_dh snd_rawmidi snd_seq 
snd_seq_device serio_raw snd_timer cuse snd lpc_ich parport_pc soundcore ppdev 
mac_hid lp parport i915 hid_generic e1000e ptp video i2c_algo_bit 
drm_kms_helper usbhid drm firewire_ohci hid pata_acpi firewire_core crc_itu_t 
pps_core
  [418114.773829] CPU: 1 PID: 11025 Comm: plugin-containe Tainted: GW   
  3.16.0-23-lowlatency #31-Ubuntu
  [418114.773833] Hardware name: AOpen i965GMx-IF/i965GMx-IF, BIOS 6.00 PG 
10/03/2008
  [418114.773836]  0009 8800115c7c00 8177ec5d 

  [418114.773843]  8800115c7c38 8107183d  

  [418114.773848]  88008b044af0 88008b0448d8 8801215cb180 
8800115c7c48
  [418114.773854] Call Trace:
  [418114.773867]  [8177ec5d] dump_stack+0x4d/0x6f
  [418114.773875]  [8107183d] warn_slowpath_common+0x7d/0xa0
  [418114.773881]  [8107191a] warn_slowpath_null+0x1a/0x20
  [418114.773893]  [c0701596] __vb2_queue_cancel+0x116/0x180 
[videobuf2_core]
  [418114.773905]  [c0702cf5] vb2_internal_streamoff+0x35/0x90 
[videobuf2_core]
  [418114.773916]  [c0702db5] vb2_streamoff+0x65/0x70 [videobuf2_core]
  [418114.773928]  [c075e855] uvc_queue_enable+0x65/0xa0 [uvcvideo]
  [418114.773939]  [c076360a] uvc_video_enable+0x4a/0x1b0 [uvcvideo]
  [418114.773958]  [c07601e2] uvc_v4l2_do_ioctl+0x962/0x14b0 
[uvcvideo]
  [418114.773962]  [81192373] ? copy_page_from_iter_iovec+0x183/0x2d0
  [418114.773976]  [c06e02c6] video_usercopy+0x366/0x600 [videodev]
  [418114.773979]  [811e4bd9] ? __sb_start_write+0x49/0xf0
  [418114.773985]  [c075f880] ? uvc_v4l2_open+0x150/0x150 [uvcvideo]
  [418114.773988]  [811e4b61] ? __sb_end_write+0x31/0x60
  [418114.773992]  [811eaad3] ? pipe_write+0x393/0x450
  [418114.773997]  [c075ec3f] uvc_v4l2_ioctl+0x2f/0x70 [uvcvideo]
  [418114.774004]  [c06da734] v4l2_ioctl+0x154/0x190 [videodev]
  [418114.774008]  [811f6468] do_vfs_ioctl+0x2c8/0x4a0
  [418114.774011]  [812007de] ? __fget+0x6e/0xb0
  [418114.774029]  [811f66c1] SyS_ioctl+0x81/0xa0
  [418114.774039]  [8178666d] system_call_fastpath+0x1a/0x1f
  [418114.774084] ---[ end trace 36d13fa659268ece ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-release-upgrader-core 1:14.10.9
  ProcVersionSignature: Ubuntu 3.16.0-23.31-lowlatency 3.16.4
  Uname: Linux 3.16.0-23-lowlatency x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Fri Oct 31 20:35:55 2014
  InstallationDate: 

[Touch-packages] [Bug 1381583] Re: imported pictures should show in Event for today

2014-11-19 Thread Arthur Mello
** Changed in: gallery-app (Ubuntu RTM)
   Status: In Progress = Fix Released

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

Title:
  imported pictures should show in Event for today

Status in Gallery App:
  In Progress
Status in Ubuntu UX bugs:
  New
Status in “gallery-app” package in Ubuntu:
  Fix Released
Status in “gallery-app” package in Ubuntu RTM:
  Fix Released

Bug description:
  When pictures are imported into the gallery, via content-hub, we
  should always display them in the Event for the current day. Right
  now, the picture is played in the Event that corresponds to the
  metadata creation date which is very confusing because after the
  picture is imported you can't find it easily.

  Arthur and I discussed modifiying one of the standard exif tags (like
  DateTime, but don't modify CreationDate) with the current date of
  import as the gallery already sorts by a series of tags. Another
  solution would be to add a custom tag like (importDate) and change the
  sort to use that if it exists before falling back to other tags.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gallery-app/+bug/1381583/+subscriptions

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


[Touch-packages] [Bug 1394155] Re: Deadlock / crash of the dash possible through Today scope

2014-11-19 Thread Pete Woods
** Changed in: unity-scopes-shell (Ubuntu)
 Assignee: (unassigned) = Pete Woods (pete-woods)

** Branch linked: lp:~unity-api-team/unity-scopes-shell/today-scope-
crash

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

Title:
  Deadlock / crash of the dash possible through Today scope

Status in “unity-scopes-shell” package in Ubuntu:
  Confirmed

Bug description:
  On krillin:

  1) Go to the Today scope
  2) Scroll to the bottom
  3) Tap Tell me more...
  4) Scroll to the bottom again
  5) Tap Finished

  Hard lock / sometimes crash.

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

-- 
Mailing list: https://launchpad.net/~touch-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-11-19 Thread Timo Jyrinki
Please give ppa:ci-train-ppa-service/landing-027 (package versions 5.3.2
+dfsg-4ubuntu4 ) a try on top of vivid and report back so that I can
proceed on validating/testing the landing otherwise.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: In Progress = Incomplete

-- 
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:
  Fix Released
Status in “qtbase-opensource-src” package in Ubuntu:
  Incomplete
Status in “unity8” package in Ubuntu:
  Opinion
Status in “unity8” package in Ubuntu RTM:
  Opinion

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 1394178] Re: [EG45M-UD2H, Realtek ALC889A, Pink Mic, Front] Recording problem, only SPDIF input available

2014-11-19 Thread Eugene
Thank you, Raymond.
I plugged mic into rear pink mic jack and it was detected and works fine!
So, there is no automatic jack detection for front jacks, i remembered i set 
checkbox under windows in realtek driver configuration to force front jacks 
enabled.
Is there any way to force front jacks to be plugged in ubuntu ?

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

Title:
  [EG45M-UD2H, Realtek ALC889A, Pink Mic, Front] Recording problem, only
  SPDIF input available

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

Bug description:
  I'm using Ubuntu 14.04.1 LTS.
  There is only Digital input in Input section and no Analog input. I can not 
use my microphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eugene 2690 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov 19 14:31:06 2014
  InstallationDate: Installed on 2014-07-16 (125 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Pink Mic, Front
  Symptom_Type: Only some of inputs are working
  Title: [EG45M-UD2H, Realtek ALC889A, Pink Mic, Front] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F3
  dmi.board.name: EG45M-UD2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd04/09/2009:svnGigabyteTechnologyCo.,Ltd.:pnEG45M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEG45M-UD2H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EG45M-UD2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Touch-packages] [Bug 1394194] [NEW] package gstreamer1.0-fluendo-mp3:amd64 0.10.23.debian-3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before att

2014-11-19 Thread Tommaso Martini
Public bug reported:

...

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: gstreamer1.0-fluendo-mp3:amd64 0.10.23.debian-3
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
Date: Wed Nov 19 08:44:58 2014
DuplicateSignature: 
package:gstreamer1.0-fluendo-mp3:amd64:0.10.23.debian-3:package is in a very 
bad inconsistent state; you should  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2014-05-29 (173 days ago)
InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2)
SourcePackage: gst-fluendo-mp3
Title: package gstreamer1.0-fluendo-mp3:amd64 0.10.23.debian-3 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gst-fluendo-mp3 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package gstreamer1.0-fluendo-mp3:amd64 0.10.23.debian-3 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in “gst-fluendo-mp3” package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gstreamer1.0-fluendo-mp3:amd64 0.10.23.debian-3
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Wed Nov 19 08:44:58 2014
  DuplicateSignature: 
package:gstreamer1.0-fluendo-mp3:amd64:0.10.23.debian-3:package is in a very 
bad inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2014-05-29 (173 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  SourcePackage: gst-fluendo-mp3
  Title: package gstreamer1.0-fluendo-mp3:amd64 0.10.23.debian-3 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-fluendo-mp3/+bug/1394194/+subscriptions

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


[Touch-packages] [Bug 1391560] Re: [themes] [design] Develop a strategy to keep fonts readable wherever we allow the user setting his own background image

2014-11-19 Thread Oliver Grawert
in case someone needs an example http://people.canonical.com/~ogra
/greeter-wallpaper.png (the screenshot is even more readable than the
real thing, the date below the time is completely unreadable on the
display with such a noisy wallpaper)

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

Title:
  [themes] [design] Develop a strategy to keep fonts readable wherever
  we allow the user setting his own background image

Status in Ubuntu UX bugs:
  New
Status in “unity8” package in Ubuntu:
  Incomplete

Bug description:
  As discussed with Olga, we need to develop a strategy on keeping the
  fonts readable when we allow the user to change the background. This
  is currently the case on the Greeter and the Lockscreens.

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

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


[Touch-packages] [Bug 1390191] Re: Department not shown if there is only one app and it uses X-Ubuntu-Default-Department-ID key

2014-11-19 Thread Pawel Stolowski
** Branch linked: lp:~unity-team/unity-scope-click/fix-1390191-rtm

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

Title:
  Department not shown if there is only one app and it uses X-Ubuntu-
  Default-Department-ID key

Status in “unity-scope-click” package in Ubuntu:
  In Progress
Status in “unity-scope-click” package in Ubuntu RTM:
  Confirmed

Bug description:
  Department is not shown in Apps department drop-down menu if it has
  only one application which declares X-Ubuntu-Default-Department-ID=...
  department mapping (and is preinstalled, ie. wasn't installed from
  store).

  This is caused by too restrictive behavior of
  DepartmentsDb::get_children_departments(..), which filters out
  subdepartments that don't have any apps in the local departments db
  (which means that department will never be shown in the departments
  menu if it has no app installed from the store). This restriction
  should probably be removed from that method after careful verification
  if it has no undesired side effects.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1390191/+subscriptions

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


[Touch-packages] [Bug 1391560] Re: [themes] [design] Develop a strategy to keep fonts readable wherever we allow the user setting his own background image

2014-11-19 Thread Sebastien Bacher
What the current desktop (with nautilus) is doing is to have a border
around the text in an opposite color, this way you always get
contrast, if it's not with the border it's with the font one ... could
be an approach to take here

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

Title:
  [themes] [design] Develop a strategy to keep fonts readable wherever
  we allow the user setting his own background image

Status in Ubuntu UX bugs:
  New
Status in “unity8” package in Ubuntu:
  Incomplete

Bug description:
  As discussed with Olga, we need to develop a strategy on keeping the
  fonts readable when we allow the user to change the background. This
  is currently the case on the Greeter and the Lockscreens.

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

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


[Touch-packages] [Bug 1394194] Re: package gstreamer1.0-fluendo-mp3:amd64 0.10.23.debian-3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attem

2014-11-19 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 gst-fluendo-mp3 in Ubuntu.
https://bugs.launchpad.net/bugs/1394194

Title:
  package gstreamer1.0-fluendo-mp3:amd64 0.10.23.debian-3 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in “gst-fluendo-mp3” package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gstreamer1.0-fluendo-mp3:amd64 0.10.23.debian-3
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Wed Nov 19 08:44:58 2014
  DuplicateSignature: 
package:gstreamer1.0-fluendo-mp3:amd64:0.10.23.debian-3:package is in a very 
bad inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2014-05-29 (173 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  SourcePackage: gst-fluendo-mp3
  Title: package gstreamer1.0-fluendo-mp3:amd64 0.10.23.debian-3 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-fluendo-mp3/+bug/1394194/+subscriptions

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


[Touch-packages] [Bug 1394193] [NEW] 114 instances of indicator-sound-service running

2014-11-19 Thread tp
Public bug reported:

I have at the moment 114 instances of indicator-sound-service running.
I can get rid of them by running sudo killall indicator-sound-service.
After which, in about two seconds, 114 new indicator-sound-service processes 
are started.

$ ps aux | grep indicator-sound-service | grep lightdm | wc -l
114

$ ps aux | grep indicator-sound-service | grep lightdm | wc -l
lightdm  32320  0.0  0.0  54320   612 ?Ds   15:17   0:00 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm  32321  0.0  0.0  54320   612 ?Ds   15:17   0:00 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm  32322  0.0  0.0  54320   616 ?Ds   15:17   0:00 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm  32323  0.0  0.0  54320   616 ?Ds   15:17   0:00 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm  32324  0.0  0.0  54320   612 ?Ds   15:17   0:00 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm  32325  0.0  0.0  54320   612 ?Ds   15:17   0:00 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm  32326  0.0  0.0  54320   616 ?Ds   15:17   0:00 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
etc...

I'm not an expert, but I don't think I need 114 instances of indicator-
sound-service.


ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ActionStates: ({'mute': (true, signature '', [false]), 'phone-settings': 
(true, '', []), 'next.gmusicbrowser.desktop': (true, '', []), 'mic-volume': 
(true, '', [0.14678955078125]), 'scroll': (true, 'i', []), 
'play-playlist.gmusicbrowser.desktop': (true, 's', []), 
'gmusicbrowser.desktop': (true, '', [{'running': false, 'state': 
'Paused'}]), 'desktop-settings': (true, '', []), 'volume': (true, 'i', 
[0.8486785888671875]), 'root': (true, '', [{'title': 'Sound', 
'accessible-desc': 'Volume (84%)', 'icon': ('themed', 
['audio-volume-high-panel', 'audio-volume-high', 'audio-volume', 'audio']), 
'visible': true}]), 'previous.gmusicbrowser.desktop': (true, '', []), 
'play.gmusicbrowser.desktop': (true, '', ['Paused'])},)
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Nov 19 15:20:57 2014
InstallationDate: Installed on 2013-05-20 (548 days ago)
InstallationMedia: Xubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120817.3)
SourcePackage: indicator-sound
UpgradeStatus: Upgraded to trusty on 2014-04-29 (204 days ago)
upstart.indicator-sound.log:
 (process:2208): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed

 ** (process:32533): CRITICAL **: volume_control_set_volume_internal:
assertion '_tmp1_ == PA_CONTEXT_READY' failed

 ** (process:32533): CRITICAL **: file /build/buildd/indicator-
sound-12.10.2+14.04.20140401/obj-x86_64-linux-gnu/src/volume-control.c:
line 1775: uncaught error:
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface (g
-dbus-error-quark, 16)

** Affects: indicator-sound (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

** Description changed:

  I have at the moment 114 instances of indicator-sound-service running.
  I can get rid of them by running sudo killall indicator-sound-service.
  After which, in about two seconds, 114 new indicator-sound-service processes 
are started.
+ 
+ 
+ lightdm  32320  0.0  0.0  54320   612 ?Ds   15:17   0:00 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
+ lightdm  32321  0.0  0.0  54320   612 ?Ds   15:17   0:00 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
+ lightdm  32322  0.0  0.0  54320   616 ?Ds   15:17   0:00 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
+ lightdm  32323  0.0  0.0  54320   616 ?Ds   15:17   0:00 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
+ lightdm  32324  0.0  0.0  54320   612 ?Ds   15:17   0:00 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
+ lightdm  32325  0.0  0.0  54320   612 ?Ds   15:17   0:00 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
+ lightdm  32326  0.0  0.0  54320   616 ?Ds   15:17   0:00 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
+ etc...
+ 
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ActionStates: ({'mute': (true, signature '', [false]), 'phone-settings': 
(true, '', []), 'next.gmusicbrowser.desktop': (true, '', []), 'mic-volume': 
(true, '', [0.14678955078125]), 'scroll': (true, 'i', []), 
'play-playlist.gmusicbrowser.desktop': 

[Touch-packages] [Bug 1391560] Re: [themes] [design] Develop a strategy to keep fonts readable wherever we allow the user setting his own background image

2014-11-19 Thread Michał Sawicz
Nautilus actually uses a small drop-shadow, not a border. Attached a
snapshot of how it looks.

** Attachment added: nautilus desktop.png
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1391560/+attachment/4263739/+files/nautilus%20desktop.png

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

Title:
  [themes] [design] Develop a strategy to keep fonts readable wherever
  we allow the user setting his own background image

Status in Ubuntu UX bugs:
  New
Status in “unity8” package in Ubuntu:
  Incomplete

Bug description:
  As discussed with Olga, we need to develop a strategy on keeping the
  fonts readable when we allow the user to change the background. This
  is currently the case on the Greeter and the Lockscreens.

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

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


[Touch-packages] [Bug 1393024] Re: Graphical corruption with hidpi scaling

2014-11-19 Thread Steffen Coenen
** Also affects: unity
   Importance: Undecided
   Status: New

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

Title:
  Graphical corruption with hidpi scaling

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

Bug description:
  With a hidpi scaling greater or equal than 2 there is graphical
  corruption of the window borders in gtk3 apps.

  Steps to reproduce:

  1. Set hidpi scaling to 2.
  2. Enlarge a window for nautilus or eye of gnome. Probably it is necessary to 
do resize the window more than one time to spot the problem.
  3. See corrupted window border on the right and/or the bottom.

  Expected behavior:
  Clean rendering

  Ubuntu 14.10 64 Bit
  Compiz 0.9.12+14.10.20140918-0ubuntu1
  Unity 7.3.1+14.10.20141016-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.89  Tue Jul  1 13:30:18 
PDT 2014
   GCC version:  gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6)
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Nov 15 16:36:40 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Device [1458:354e]
  InstallationDate: Installed on 2014-11-12 (2 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-D3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=2a652086-a4da-44ed-ae7f-7b994401ef8b ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7
  dmi.board.name: GA-990FXA-D3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-D3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-990FXA-D3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Sat Nov 15 15:00:14 2014
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.16.0-1ubuntu1

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

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


[Touch-packages] [Bug 1394201] [NEW] package libsystemd-login0:amd64 208-8ubuntu8.1 failed to install/upgrade: package libsystemd-login0:amd64 is already installed and configured

2014-11-19 Thread anamnisia
*** This bug is a duplicate of bug 1394199 ***
https://bugs.launchpad.net/bugs/1394199

Public bug reported:

shows every time i start my laptop

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: libsystemd-login0:amd64 208-8ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8
AptdaemonVersion: 1.1.1+bzr980-0ubuntu1
Architecture: amd64
Date: Sat Nov 15 21:26:11 2014
Dependencies:
 gcc-4.9-base 4.9.1-16ubuntu6
 libc6 2.19-10ubuntu2
 libgcc1 1:4.9.1-16ubuntu6
 multiarch-support 2.19-10ubuntu2
DuplicateSignature: package:libsystemd-login0:amd64:208-8ubuntu8.1:package 
libsystemd-login0:amd64 is already installed and configured
ErrorMessage: package libsystemd-login0:amd64 is already installed and 
configured
InstallationDate: Installed on 2014-10-27 (23 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 
(20141022.1)
SourcePackage: systemd
Title: package libsystemd-login0:amd64 208-8ubuntu8.1 failed to 
install/upgrade: package libsystemd-login0:amd64 is already installed and 
configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed amd64 apport-package package-from-proposed utopic

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

Title:
  package libsystemd-login0:amd64 208-8ubuntu8.1 failed to
  install/upgrade: package libsystemd-login0:amd64 is already installed
  and configured

Status in “systemd” package in Ubuntu:
  New

Bug description:
  shows every time i start my laptop

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: libsystemd-login0:amd64 208-8ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  AptdaemonVersion: 1.1.1+bzr980-0ubuntu1
  Architecture: amd64
  Date: Sat Nov 15 21:26:11 2014
  Dependencies:
   gcc-4.9-base 4.9.1-16ubuntu6
   libc6 2.19-10ubuntu2
   libgcc1 1:4.9.1-16ubuntu6
   multiarch-support 2.19-10ubuntu2
  DuplicateSignature: package:libsystemd-login0:amd64:208-8ubuntu8.1:package 
libsystemd-login0:amd64 is already installed and configured
  ErrorMessage: package libsystemd-login0:amd64 is already installed and 
configured
  InstallationDate: Installed on 2014-10-27 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 
(20141022.1)
  SourcePackage: systemd
  Title: package libsystemd-login0:amd64 208-8ubuntu8.1 failed to 
install/upgrade: package libsystemd-login0:amd64 is already installed and 
configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1394201] Re: package libsystemd-login0:amd64 208-8ubuntu8.1 failed to install/upgrade: package libsystemd-login0:amd64 is already installed and configured

2014-11-19 Thread Apport retracing service
*** This bug is a duplicate of bug 1394199 ***
https://bugs.launchpad.net/bugs/1394199

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1394199
   package libsystemd-login0:amd64 208-8ubuntu8.1 failed to install/upgrade: 
package libsystemd-login0:amd64 is already installed and configured

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

Title:
  package libsystemd-login0:amd64 208-8ubuntu8.1 failed to
  install/upgrade: package libsystemd-login0:amd64 is already installed
  and configured

Status in “systemd” package in Ubuntu:
  New

Bug description:
  shows every time i start my laptop

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: libsystemd-login0:amd64 208-8ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  AptdaemonVersion: 1.1.1+bzr980-0ubuntu1
  Architecture: amd64
  Date: Sat Nov 15 21:26:11 2014
  Dependencies:
   gcc-4.9-base 4.9.1-16ubuntu6
   libc6 2.19-10ubuntu2
   libgcc1 1:4.9.1-16ubuntu6
   multiarch-support 2.19-10ubuntu2
  DuplicateSignature: package:libsystemd-login0:amd64:208-8ubuntu8.1:package 
libsystemd-login0:amd64 is already installed and configured
  ErrorMessage: package libsystemd-login0:amd64 is already installed and 
configured
  InstallationDate: Installed on 2014-10-27 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 
(20141022.1)
  SourcePackage: systemd
  Title: package libsystemd-login0:amd64 208-8ubuntu8.1 failed to 
install/upgrade: package libsystemd-login0:amd64 is already installed and 
configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1381970] Re: unity8-dash segfaults when using click store

2014-11-19 Thread Pawel Stolowski
*** This bug is a duplicate of bug 1394155 ***
https://bugs.launchpad.net/bugs/1394155

** This bug has been marked a duplicate of bug 1394155
   Deadlock / crash of the dash possible through Today scope

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

Title:
  unity8-dash segfaults when using click store

Status in “unity-scopes-api” package in Ubuntu:
  New
Status in “unity-scopes-shell” package in Ubuntu:
  New

Bug description:
  Using rtm 109 on krillin, clicking through the click store pages it's
  easy enough to hit a segfault (e.g look at some softwares, go back to
  the list, repeat)

  backtrace

  #0  unity::scopes::Category::title (this=0x30)
  at 
/build/buildd/unity-scopes-api-0.6.7+14.10.20141010.1/src/scopes/Category.cpp:56
  No locals.
  #1  0xadd9de02 in scopes_ng::Categories::data(QModelIndex const, int) const 
()
     from /usr/lib/arm-linux-gnueabihf/unity8/qml/Unity/libUnity-qml.so
  No symbol table info available.
  #2  0xb6531e4a in QSortFilterProxyModel::data(QModelIndex const, int) const 
()
     from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
  No symbol table info available.
  #3  0xb6a9e0de in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5
  No symbol table info available.

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

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


[Touch-packages] [Bug 1335002] Re: Chinese input method does not work after enable Chinese keyboard in Ubuntu Phone

2014-11-19 Thread Bill Filler
approved

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

Title:
  Chinese input method does not work after enable Chinese keyboard in
  Ubuntu Phone

Status in Ubuntu Keyboard:
  In Progress
Status in “ubuntu-keyboard” package in Ubuntu:
  In Progress
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  In Progress

Bug description:
  Reproduce steps:

  1, enable Chinese keyboard in system settings
  2, launch an app can input text like notes
  3, long press global icon and switch Chinese

  Expecting:
  user can input Chinese like press 'n' and 'i' then 你 should show up on 
candidate bar

  Actual:
  no candidate bar, so still input English

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

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


[Touch-packages] [Bug 1186381] Re: Can not paste into web forms

2014-11-19 Thread Alexandre Abreu
@Mitchell: yes there is ongoing work to fix this and properly address
the issue (in Oxide, the webengine backend for webapps),

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

Title:
  Can not paste into web forms

Status in Web Browser App:
  Confirmed
Status in “webbrowser-app” package in Ubuntu:
  Confirmed

Bug description:
  I can copy text from one app, and paste it into the URL field of the
  browser, but I don't get a Paste option for input fields in the
  webpage itself.

  I found this when trying to log into an internal website, where SSO
  prompted me to perform 2-factor authentication.  I generated the one
  time password using CanonicalAuth, and was able to copy it into the
  clipboard.  However, I was unable to paste it into the 2fa field in
  the web browser.

  I could paste it into the URL field, so I know it was in the
  clipboard.  When long-pressing on the web form input field, I was
  given a menu with Share, Save and Copy, but not Paste.

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

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


[Touch-packages] [Bug 341928] Re: Consistently reproducible device or resource busy error on partitioning

2014-11-19 Thread Martin Pitt
** Bug watch added: Debian Bug tracker #569290
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569290

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

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

Title:
  Consistently reproducible device or resource busy error on
  partitioning

Status in “lvm2” package in Ubuntu:
  Fix Released
Status in “lvm2” source package in Jaunty:
  Fix Released
Status in “lvm2” package in Debian:
  Unknown

Bug description:
  Upon partitioning during install, I receive the following message:

  Error informing the kernel about modifications to partition
  /dev/cciss/c0d0p1 -- Device or resource busy.  This means Linux won't
  know about any changes you made to /dev/cciss/c0d0p1 until you reboot
  -- so you shouldn't mount it or use it in any way before rebooting.

  I can reliably reproduce this about 75% of the time.  I believe it is
  so reproducible as this machine is being reimaged with a different
  partitioning scheme each time before I run the installer.

  I will attach syslog and partman and can reproduce this as necessary
  to get additional information.  These logs are from an HP Proliant
  DL320s G1 with the Jaunty server amd64 image from March 10 2009 but it
  is occurring on multiple different machines and disc images.

  Per cjwatson I am creating a new bug rather than attaching this to an
  existing similar bug.

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

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


[Touch-packages] [Bug 1384810] Re: Next key is too big for keyboard and doesn't translate well

2014-11-19 Thread Launchpad Bug Tracker
** Branch linked: lp:~michael-sheldon/ubuntu-keyboard/fix-1384810

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

Title:
  Next key is too big for keyboard and doesn't translate well

Status in Address Book App:
  Fix Committed
Status in Ubuntu Keyboard:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in “address-book-app” package in Ubuntu:
  New
Status in “ubuntu-keyboard” package in Ubuntu:
  New
Status in “address-book-app” package in Ubuntu RTM:
  New
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  In the address book, we replace the enter button with the text Next
  as it automatically navigates you to the next field.

  A better solution would be to use an icon that represents Next (some
  kind of forward arrow).

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1384810/+subscriptions

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


[Touch-packages] [Bug 1390191] Re: Department not shown if there is only one app and it uses X-Ubuntu-Default-Department-ID key

2014-11-19 Thread Pawel Stolowski
** Branch linked: lp:~unity-team/unity-scope-click/fix-1390191

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

Title:
  Department not shown if there is only one app and it uses X-Ubuntu-
  Default-Department-ID key

Status in “unity-scope-click” package in Ubuntu:
  In Progress
Status in “unity-scope-click” package in Ubuntu RTM:
  Confirmed

Bug description:
  Department is not shown in Apps department drop-down menu if it has
  only one application which declares X-Ubuntu-Default-Department-ID=...
  department mapping (and is preinstalled, ie. wasn't installed from
  store).

  This is caused by too restrictive behavior of
  DepartmentsDb::get_children_departments(..), which filters out
  subdepartments that don't have any apps in the local departments db
  (which means that department will never be shown in the departments
  menu if it has no app installed from the store). This restriction
  should probably be removed from that method after careful verification
  if it has no undesired side effects.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1390191/+subscriptions

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


Re: [Touch-packages] [Bug 1389305] Re: sudo doesn't work on unprivileged lxc container

2014-11-19 Thread Serge Hallyn
Ah, the ecryptfs $HOME might be the problem.  I haven't tested that
and wouldn't be surprised if ecryptfs prevented the console from
looking ok.  Could you try something like:

rm -rf $HOME/.config/lxc $HOME/.local/share/lxc
sudo mkdir /opt/lxc
sudo chown -R $USER /opt/lxc
mkdir /opt/lxc/config /opt/lxc/store
ln -s /opt/lxc/store $HOME/.local/share/lxc
ln -s /opt/lxc/config $HOME/.config/lxc

Then re-try the container create/setup.  This will create the
container rootfs on a non-ecryptfs filesystem.

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

Title:
  sudo doesn't work on unprivileged lxc container

Status in “lxc” package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 14.04 64 bit, after adding a user into an unprivileged
  container, the sudo complains that:

  $ sudo su
  sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 
'nosuid' option set or an NFS file system without root privileges?

  To reproduce:

  1. Download and install the Ubuntu amd64 minimalcd
  2. Install lxc on it and openssh for convenience.
  3. follow 
https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged-containers/ ; 
specifically do:
   a) sudo usermod --add-subuids 10-165536 $USER
   b) sudo usermod --add-subgids 10-165536 $USER
   c) sudo chmod +x $HOME
   d) create the file  ~/.config/lxc/default.conf with the following 
contents:
  lxc.include = /etc/lxc/default.conf
  lxc.id_map = u 0 10 65536
  lxc.id_map = g 0 10 65536
   e) echo $USER veth lxcbr0 10 | sudo tee /etc/lxc/lxc-usernet
  (restart is not required)
  4. Create the container with
  lxc-create -t download -n p1 -- -d ubuntu -r trusty -a amd64
  5. Install openssh-server in the container:
  lxc-start -d -n p1
  lxc-attach -n p1 -- apt-get install openssh-server
  6. Add a user adam with the group sudo
  lxc-attach -n p1 -- adduser adam sudo
  7. Set a password for the user
  8. Log in via ssh (and provide the password from step 7)
  ssh p1@adam
  9. On the p1:
  adam@p1$ sudo su
  sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 
'nosuid' option set or an NFS file system without root privileges?

  I expected it to make change the user to root.

  lxc version: 1.0.3-0ubuntu3
  $cat ~/.cache/lxc/download/ubuntu/trusty/amd64/default/build_id
  20141101_03:49

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

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


Re: [Touch-packages] [Bug 1389305] Re: sudo doesn't work on unprivileged lxc container

2014-11-19 Thread Serge Hallyn
Quoting Adam Ryczkowski (adam.ryczkow...@statystyka.net):
 I really don't know how to tell you, which Trusty's 64bit minimal cd I

The full url.

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

Title:
  sudo doesn't work on unprivileged lxc container

Status in “lxc” package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 14.04 64 bit, after adding a user into an unprivileged
  container, the sudo complains that:

  $ sudo su
  sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 
'nosuid' option set or an NFS file system without root privileges?

  To reproduce:

  1. Download and install the Ubuntu amd64 minimalcd
  2. Install lxc on it and openssh for convenience.
  3. follow 
https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged-containers/ ; 
specifically do:
   a) sudo usermod --add-subuids 10-165536 $USER
   b) sudo usermod --add-subgids 10-165536 $USER
   c) sudo chmod +x $HOME
   d) create the file  ~/.config/lxc/default.conf with the following 
contents:
  lxc.include = /etc/lxc/default.conf
  lxc.id_map = u 0 10 65536
  lxc.id_map = g 0 10 65536
   e) echo $USER veth lxcbr0 10 | sudo tee /etc/lxc/lxc-usernet
  (restart is not required)
  4. Create the container with
  lxc-create -t download -n p1 -- -d ubuntu -r trusty -a amd64
  5. Install openssh-server in the container:
  lxc-start -d -n p1
  lxc-attach -n p1 -- apt-get install openssh-server
  6. Add a user adam with the group sudo
  lxc-attach -n p1 -- adduser adam sudo
  7. Set a password for the user
  8. Log in via ssh (and provide the password from step 7)
  ssh p1@adam
  9. On the p1:
  adam@p1$ sudo su
  sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 
'nosuid' option set or an NFS file system without root privileges?

  I expected it to make change the user to root.

  lxc version: 1.0.3-0ubuntu3
  $cat ~/.cache/lxc/download/ubuntu/trusty/amd64/default/build_id
  20141101_03:49

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

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


[Touch-packages] [Bug 1359439] Re: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service

2014-11-19 Thread Serhiy Zahoriya
Affects Kubuntu 14.10 too. Both updated and fresh.

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

Title:
  [7.287663] systemd-logind[1057]: Failed to start unit
  user@126.service: Unknown unit: user@126.service

Status in “systemd-shim” package in Ubuntu:
  In Progress
Status in “systemd-shim” package in Debian:
  New

Bug description:
  [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: 
Unknown unit: user@126.service
  [7.287677] systemd-logind[1057]: Failed to start user service: Unknown 
unit: user@126.service
  [7.293871] systemd-logind[1057]: New session c1 of user lightdm.
  [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to 
/run/user/126/X11-display.
  [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team
  [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
  [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready
  [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec
  [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3)
  [9.920181] wlan0: authenticated
  [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3)
  [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 
status=0 aid=2)
  [9.927753] wlan0: associated
  [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [   12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope
  [   12.677122] systemd-logind[1057]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2dc1_2escope
  [   12.683902] systemd-logind[1057]: Failed to start unit user@1000.service: 
Unknown unit: user@1000.service
  [   12.683912] systemd-logind[1057]: Failed to start user service: Unknown 
unit: user@1000.service
  [   12.685157] systemd-logind[1057]: New session c2 of user caravena.
  [   12.685190] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to 
/run/user/1000/X11-display.
  [  234.494462] systemd-logind[1057]: Failed to abandon scope session-c2.scope
  [  234.494478] systemd-logind[1057]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2dc2_2escope
  [  235.514349] systemd-logind[1057]: New session c3 of user lightdm.
  [  244.245908] systemd-logind[1057]: Failed to abandon scope session-c3.scope
  [  244.245923] systemd-logind[1057]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2dc3_2escope

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd 208-7ubuntu4 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Aug 20 18:26:06 2014
  InstallationDate: Installed on 2014-04-27 (115 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1394244] [NEW] pycurl gives 'gnutls_handshake() warning: The server name sent was not recognized', curl on command line and wget work with same URL

2014-11-19 Thread Till Kamppeter
Public bug reported:

From a Python program (system-config-printer) I need to access an https
URL (on OpenPrinting) assuring that the answer really comes from
OpenPrinting and not from an attacker. This serves for automatically
downloading and installing driver packages for detected and locally
unsupported printers.

A typical URL sent by system-config-printer to find driver packages for
a detected printer is

https://www.openprinting.org/query.cgi?moreinfo=1showprinterid=1onlynewestdriverpackages=0architectures=amd64noobsoletes=1onlyfree=0onlymanufacturer=0onlydownload=1packagesystem=debonlysigneddriverpackages=0format=xmltype=driversprinter=MFG:EPSON;MDL
:EP-805A%20Series;DES:EPSON%20EP-805A%20Series;CLS:PRINTER;

The https://...; allows for checking whether the answer really comes
from OpenPrinting. It is no problem accessing this URL with a browser or
by the command line:

curl
'https://www.openprinting.org/query.cgi?moreinfo=1showprinterid=1onlynewestdriverpackages=0architectures=amd64noobsoletes=1onlyfree=0onlymanufacturer=0onlydownload=1packagesystem=debonlysigneddriverpackages=0format=xmltype=driversprinter=MFG:EPSON;MDL
:EP-805A%20Series;DES:EPSON%20EP-805A%20Series;CLS:PRINTER;'

wget
'https://www.openprinting.org/query.cgi?moreinfo=1showprinterid=1onlynewestdriverpackages=0architectures=amd64noobsoletes=1onlyfree=0onlymanufacturer=0onlydownload=1packagesystem=debonlysigneddriverpackages=0format=xmltype=driversprinter=MFG:EPSON;MDL
:EP-805A%20Series;DES:EPSON%20EP-805A%20Series;CLS:PRINTER;'

In all cases I get an XML data set in a reasonable amount of time (so
server performance is OK). The XML data set tells about a driver package
from Epson with all info to download it and to establish automatic
updates via the facilities of the distro. RPM- and DEB-based distros
with 32-bit or 64-bit Intel architectures are supported.

system-config-printer is written completely in Python and uses the
pycurl library to call the URL with verification that the communication
is done with the actual OpenPrinting server. This does not work any
more. If I run the following simple Python code it fails:

--
import pycurl
def collect_data(result):
   print(result)
   return len(result)

curl = pycurl.Curl()
curl.setopt(pycurl.SSL_VERIFYPEER, 1)
curl.setopt(pycurl.SSL_VERIFYHOST, 2)
curl.setopt(pycurl.WRITEFUNCTION, collect_data)
curl.setopt(pycurl.URL, 
'https://www.openprinting.org/query.cgi?moreinfo=1showprinterid=1onlynewestdriverpackages=0architectures=amd64noobsoletes=1onlyfree=0onlymanufacturer=0onlydownload=1packagesystem=debonlysigneddriverpackages=0format=xmltype=driversprinter=MFG:EPSON;MDL:EP-805A%20Series;DES:EPSON%20EP-805A%20Series;CLS:PRINTER;')
status = curl.perform()
repr(status)
quit()
--

You can paste the lines into a text editor to get a Python program or
run python or python3 (Python version seems not to matter) and paste
the bunch of lines to the prompt.

The result is always the same, the status = curl.perform() line gives:

Traceback (most recent call last):
  File stdin, line 1, in module
pycurl.error: (51, 'gnutls_handshake() warning: The server name sent was not 
recognized')

For me it looks like that something has changed, as formerly this Python
code worked correctly.

If I change https://...; to http://...; all works correctly and I get
the XML data, but then there is no verification any more that the
communication is really done with OpenPrinting.

See also

http://stackoverflow.com/questions/568247/pycurl-fails-but-curl-from-
bash-works-in-ubuntu

This all looks like a bug in pycurl.

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

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

Title:
  pycurl gives 'gnutls_handshake() warning: The server name sent was not
  recognized', curl on command line and wget work with same URL

Status in “pycurl” package in Ubuntu:
  New

Bug description:
  From a Python program (system-config-printer) I need to access an
  https URL (on OpenPrinting) assuring that the answer really comes from
  OpenPrinting and not from an attacker. This serves for automatically
  downloading and installing driver packages for detected and locally
  unsupported printers.

  A typical URL sent by system-config-printer to find driver packages
  for a detected printer is

  
https://www.openprinting.org/query.cgi?moreinfo=1showprinterid=1onlynewestdriverpackages=0architectures=amd64noobsoletes=1onlyfree=0onlymanufacturer=0onlydownload=1packagesystem=debonlysigneddriverpackages=0format=xmltype=driversprinter=MFG:EPSON;MDL
  :EP-805A%20Series;DES:EPSON%20EP-805A%20Series;CLS:PRINTER;

  The https://...; allows for checking whether the answer really comes
  from OpenPrinting. It is no problem accessing this URL with a browser
  or by the command line:

  curl
  

[Touch-packages] [Bug 1357321] Re: QNetworkAccessManager doesn't support roaming on Ubuntu

2014-11-19 Thread kevin gunn
@lorn - per ogra's comment, it's still a top-blocker in spirit (folks
were using the title for some reporting visibility)

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

Title:
  QNetworkAccessManager doesn't support roaming on Ubuntu

Status in Platform API:
  Invalid
Status in The Savilerow project:
  New
Status in “network-manager” package in Ubuntu:
  Invalid
Status in “ofono” package in Ubuntu:
  Invalid
Status in “qtbase-opensource-src” package in Ubuntu:
  In Progress
Status in “qtbase-opensource-src” package in Ubuntu RTM:
  New

Bug description:
  scope images load fine in wifi, but not on hsdpa even when there is
  good connectivity and browsing works well. Results are return, but
  images do not load.

To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions

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


[Touch-packages] [Bug 1390919] Re: Scope template cannot be running for devel emulator

2014-11-19 Thread Michael Vogt
Thanks for your bugreport.

I just created a click chroot with sudo click chroot -a i386 -f ubuntu-
sdk-15.04-dev1 and checked what is installed there. Both libnet-cpp-dev
and libprocess-cpp-dev are installed. Same for -f ubuntu-sdk-14.10. Is
the SDK creating the chroot in a different way?

** Changed in: click (Ubuntu)
 Assignee: Michael Vogt (mvo) = Zoltan Balogh (bzoltan)

** Changed in: click (Ubuntu)
   Status: Confirmed = Incomplete

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

Title:
  Scope  template cannot be running for devel emulator

Status in “click” package in Ubuntu:
  Incomplete

Bug description:
  Some libs are missing in the chroot, and the scope cannot be running
  for emulator (devel i386). Attached please find the captured screen.

  -- package 'process-cpp' not found
  -- package 'net-cpp=1.1.0' not found
  -- package 'net-cpp=1.1.0' not found

  

  -- The CXX compiler identification is GNU 4.9.1
  -- Check for working CXX compiler: /usr/bin/i686-linux-gnu-g++
  -- Check for working CXX compiler: /usr/bin/i686-linux-gnu-g++ -- works
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Found PkgConfig: /usr/bin/pkg-config (found version 0.28)
  -- Boost version: 1.55.0
  -- checking for modules 'libunity-scopes=0.6.0;net-cpp=1.1.0'
  --   package 'net-cpp=1.1.0' not found
  CMake Error at /usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:283 (message):
A required package was not found
  Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:337 
(_pkg_check_modules_internal)
CMakeLists.txt:34 (pkg_check_modules)
  -- Found Gettext: /usr/bin/msgmerge (found version 0.19.2)
  -- Found XGettext: /usr/bin/xgettext (found version 0.19.2)
  CMake Error at cmake/FindGMock.cmake:6 (add_subdirectory):
add_subdirectory given source /usr/src/gmock which is not an existing
directory.
  Call Stack (most recent call first):
tests/CMakeLists.txt:3 (include)
  -- checking for module 'process-cpp'
  --   package 'process-cpp' not found
  -- Configuring incomplete, errors occurred!
  See also 
/home/liuxg/release/build-scopetest1-UbuntuSDK_for_i386_GCC_ubuntu_sdk_14_10_utopic-Default/CMakeFiles/CMakeOutput.log.
  CMake Error at /usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:283 (message):
A required package was not found
  Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:337 
(_pkg_check_modules_internal)
tests/CMakeLists.txt:6 (pkg_check_modules)

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

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


[Touch-packages] [Bug 1392615] Re: OA sign-in should not block

2014-11-19 Thread Marcus Tomlinson
Sorry, I'm not marking the bug as Invalid, I'm marking it as
Incomplete as this bug may need more info. Perhaps I'm not correctly
reproducing the issue?

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

Title:
  OA sign-in should not block

Status in “unity-scopes-api” package in Ubuntu:
  Incomplete

Bug description:
  If I login with my Google account and authorise YouTube access it
  appears that when I get 'near' to the Video scope (i.e. which includes
  YouTube) the Dash starts to become unresponsive. This manifests itself
  in swipes that take a few seconds to get actioned and scrolling
  freezes when moving between scopes. Removing YouTube access appears to
  cure this.

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

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


[Touch-packages] [Bug 1364292] Re: [Toshiba Portégé R600-10Q] VGA output doesn't work with Intel GM45 chipset

2014-11-19 Thread Oliver Woodford
I did not test it on a release prior to 14.04. However, the following resources 
suggest this bug has existed since at least release 10.04:
http://askubuntu.com/questions/121228/laptop-with-intel-graphics-external-vga-monitor-only-gets-signal-on-boot-no-h
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1218224

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

Title:
  [Toshiba Portégé R600-10Q] VGA output doesn't work with Intel GM45
  chipset

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  I have just installed Ubuntu 14.04 64-bit on my Toshiba Portege
  R600-10Q laptop (a model from 2009). I am now trying to display the
  desktop on a BenQ Senseye3 22 monitor, via the vga output, but it's
  not working - the monitor says No Signal Detected!.

  What I've done:
  I have gone into Screen Display, where I can see the monitor is detected by 
the laptop.
  The monitor has a 1920 x 1080 native resolution, which I have tried to use, 
but I have also set it to lower resolutions, e.g. 1024 x 576.
  I have tried to use the monitor in dual screen, mirrored and single screen 
mode - none work.
  I have tried pressing Fn + F5 to get single screen output - the laptop screen 
goes blank, but still no output on the monitor.
  I have tried several monitors (of the same type, and also of a different 
make), so I don't think it's that.

  If I plug the vga cable in after boot up, then the monitor receives no
  signal.

  WORKAROUND: If, and only if, the monitor was plugged in to the PC's
  VGA output during boot up, then the display outputs to the monitor
  correctly.

  The laptop has the Intel® GS45 Express chipset for graphics acceleration. I 
installed mesa-utils and ran glxinfo in a terminal. Amongst the output was:
  OpenGL renderer string: Mesa DRI Mobile Intel® GM45 Express Chipset

  Also, in the About This Computer window I see:
  Graphics: Mobile Intel® GM45 Express Chipset

  I wonder if the problem is that my chipset is GS45 not GM45.

  The output of sudo lshw -C video is:
  *-display:0
  description: VGA compatible controller
  product: Mobile 4 Series Chipset Integrated Graphics Controller
  vendor: Intel Corporation
  physical id: 2
  bus info: pci@:00:02.0
  version: 07
  width: 64 bits
  clock: 33MHz
  capabilities: msi pm vga_controller bus_master cap_list rom
  configuration: driver=i915 latency=0
  resources: irq:44 memory:ff40-ff7f memory:e000-efff 
ioport:cff8(size=8)
  *-display:1 UNCLAIMED
  description: Display controller
  product: Mobile 4 Series Chipset Integrated Graphics Controller
  vendor: Intel Corporation
  physical id: 2.1
  bus info: pci@:00:02.1
  version: 07
  width: 64 bits
  clock: 33MHz
  capabilities: pm bus_master cap_list
  configuration: latency=0
  resources: memory:ffc0-ffcf

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-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
  Date: Tue Sep  2 10:00:57 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Toshiba America Info Systems Device [1179:000c]
     Subsystem: Toshiba America Info Systems Device [1179:000c]
  InstallationDate: Installed on 2014-08-28 (4 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: TOSHIBA PORTEGE R600
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=fe977943-4013-472e-b627-f7184c9e190f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2008
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.60
  dmi.board.asset.tag: 00
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.60:bd11/27/2008:svnTOSHIBA:pnPORTEGER600:pvrPPR61E-00Q00CEN:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE R600
  dmi.product.version: PPR61E-00Q00CEN
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 

[Touch-packages] [Bug 1392615] Re: OA sign-in should not block

2014-11-19 Thread Marcus Tomlinson
I've been playing around with the phone, trying to reproduce this issue
using multiple configurations:

* Youtube scope signed in.
* Youtube scope not signed in.
* YouTube favourited.
* YouTube not favourited.
* YouTube and Videos scopes at different positions in the favourited scopes.
* Even Online Accounts completely removed from the Youtube scope code.

Granted, the Youtube scope (either loaded directly or indirectly via
Videos) seems to lag more when started than other scopes. However,
regardless of the configuration, I always seem to get the same amount of
lag when scrolling.

I then noticed that the Vimeo scope seemed to also produce a
considerable lag (I'm talking 500ms up to 1.5s). So I tried the above
configurations with the Vimeo scope this time (yes, even removing OA
completely from the scope), but I still could not see any noticeable
change in lag between each configurations.

I'm marking this bug as invalid as I can't see (from my tests, and my
colleges trying this too) that OA sign-in is the reason behind the
lagging issue.

** Changed in: unity-scopes-api (Ubuntu)
   Status: In Progress = Incomplete

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

Title:
  OA sign-in should not block

Status in “unity-scopes-api” package in Ubuntu:
  Incomplete

Bug description:
  If I login with my Google account and authorise YouTube access it
  appears that when I get 'near' to the Video scope (i.e. which includes
  YouTube) the Dash starts to become unresponsive. This manifests itself
  in swipes that take a few seconds to get actioned and scrolling
  freezes when moving between scopes. Removing YouTube access appears to
  cure this.

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

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


[Touch-packages] [Bug 1337407] Comment bridged from LTC Bugzilla

2014-11-19 Thread bugproxy
--- Comment From vcd...@us.ibm.com 2014-11-19 15:16 EDT---
(In reply to comment #10-11)
Please take a look at the attachment for how the service facility in Linux 
correctly handles a service.
If a system utility can NOT do the normal system-wide management, what value 
does it really have? I personally think upstart in Ubuntu has miles to go 
from the average expectation.

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

Title:
  Upstart can NOT handle service/job started by others

Status in “upstart” package in Ubuntu:
  New

Bug description:
  -- Problem Description --
  Upstart can not see a service/job/process that has been started and running 
by someone else. Old style init.d/systemd fully/partially handle start/stop 
correctly (on other Linux systems without Upstart), no matter who started the 
process.

  Our PMLinux collecting agent daemon_PMLnx was designed to start/run
  by root with any means, such as crontab, inittab, service, or even
  command line at a terminal. The program itself will quit immediately
  at the beginning if finds the process already running.

  Generally, we prefer to organize PMLinux as a service, plus create a
  start hook in the crontab to run daemon_PMLnx at 3am every day, in
  order to guarantee a restart won't be forgot if someone ever stopped
  the job.

  Here are some command outputs from Ubuntu/Upstart:

  # uname -a
  Linux ubuntu 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:09:21 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux

  # dpkg -l upstart
  Name Version  Architecture  Description
  -===--=-
  ii  upstart  1.12.1-0ubuntu4  ppc64el   event-based init daemon

  # ps -ef | grep -e PMLnx$ -e CRON$
  root 10263   771  0 17:59 ?00:00:00 CRON
  root 10264 10263  0 17:59 ?00:00:00 /bin/sh -c 
/var/perf/pm/bin/daemon_PMLnx (bug!)  
  root 10265 10264  0 17:59 ?00:00:00 /var/perf/pm/bin/daemon_PMLnx

  # start PMLinux
  PMLinux stop/waiting   --- bad!

  # status PMLinux
  PMLinux stop/waiting   --- bad!

  # stop PMLinux
  stop: Unknown instance:   --- bad!

  # kill -2 10265

  # start PMLinux
  PMLinux start/running, process 10562

  # ps -ef | grep -e PMLnx$
  root 10562 1  0 19:49 ?00:00:00 /var/perf/pm/bin/daemon_PMLnx

  # start PMLinux
  start: Job is already running: PMLinux

  # stop PMLinux
  PMLinux stop/waiting

  # stop PMLinux
  stop: Unknown instance:

  # cat /etc/init/PMLinux.conf
  # daemon_PMLnx - Collecting Agent of IBM Performance Management for Power 
Linux (PMLinux)
  #
  # daemon_PMLnx collects PMLinux data at periodic scheduled times
  # working HOME directory - /var/perf/pm

  description IBM PMLinux collecting daemon
  author IBM PMLinux Team, Rochester, USA

  start on runlevel [2345]
  stop on runlevel [!2345]

  # console output  
  # not works as expected: output to the working terminal (instead of 
system console)
  pre-start script
  unset myErrMSG
  if [ ! -x /var/perf/pm/bin/daemon_PMLnx ]; then
  export myErrMSG='Daemon programs disappeared; please 
re-install ibmPMLinux'
  #   elif ps -C daemon_PMLnx /dev/null; then
  #   export myErrMSG='PMLinux collecting daemon is already 
running!'
  elif [ ! -L /var/adm/perfmgr ] || [ ! -d /var/adm/perfmgr ]; then
  export myErrMSG='PMLinux was NOT enabled; Please run 
config.PMLnx to activate'
  fi
  if [ -n $myErrMSG ]; then
  echo -n `date +'%D %T'` ;  stop;
  echo`date +'%D %T'` $myErrMSG; exit 0
  fi
  end script

  post-start script
  if ps -C daemon_PMLnx /dev/null; then
  echo `date +'%D %T'` PMLinux collecting daemon running...
  else
  echo `date +'%D %T'` FAILED: Could NOT start PMLinux 
collecting daemon!!!
  fi
  end script

  post-stop script
  echo `date +'%D %T'` PMLinux collecting daemon stopped.
  end script

  exec /var/perf/pm/bin/daemon_PMLnx

  The attachment is a screenshot to demonstrate an old init under a
  different distro 1 that can find/stop PMLinux daemon started from user
  terminal.

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

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


[Touch-packages] [Bug 1394249] [NEW] lxc package dependencies over-constrained

2014-11-19 Thread Jens Elkner
Public bug reported:

Obviously lxc does NOT depend on dnsmasq-base and thus this dependency
should be lowered to optional or recommended.

Today entities using containers already have proper DNS as well as DHCP
servers and thus do not need at all another point of failure/possible
weak software/redundant aka non-green services like the dnsmasq stuff.

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

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

Title:
  lxc package dependencies over-constrained

Status in “lxc” package in Ubuntu:
  New

Bug description:
  Obviously lxc does NOT depend on dnsmasq-base and thus this dependency
  should be lowered to optional or recommended.

  Today entities using containers already have proper DNS as well as
  DHCP servers and thus do not need at all another point of
  failure/possible weak software/redundant aka non-green services like
  the dnsmasq stuff.

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

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


[Touch-packages] [Bug 1390919] Re: Scope template cannot be running for devel emulator

2014-11-19 Thread Zoltan Balogh
And a `dpkg -l| egrep libnet-cpp-dev|libprocess-cpp-dev` would tell
the truth about the chroot in question

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

Title:
  Scope  template cannot be running for devel emulator

Status in “click” package in Ubuntu:
  Incomplete

Bug description:
  Some libs are missing in the chroot, and the scope cannot be running
  for emulator (devel i386). Attached please find the captured screen.

  -- package 'process-cpp' not found
  -- package 'net-cpp=1.1.0' not found
  -- package 'net-cpp=1.1.0' not found

  

  -- The CXX compiler identification is GNU 4.9.1
  -- Check for working CXX compiler: /usr/bin/i686-linux-gnu-g++
  -- Check for working CXX compiler: /usr/bin/i686-linux-gnu-g++ -- works
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Found PkgConfig: /usr/bin/pkg-config (found version 0.28)
  -- Boost version: 1.55.0
  -- checking for modules 'libunity-scopes=0.6.0;net-cpp=1.1.0'
  --   package 'net-cpp=1.1.0' not found
  CMake Error at /usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:283 (message):
A required package was not found
  Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:337 
(_pkg_check_modules_internal)
CMakeLists.txt:34 (pkg_check_modules)
  -- Found Gettext: /usr/bin/msgmerge (found version 0.19.2)
  -- Found XGettext: /usr/bin/xgettext (found version 0.19.2)
  CMake Error at cmake/FindGMock.cmake:6 (add_subdirectory):
add_subdirectory given source /usr/src/gmock which is not an existing
directory.
  Call Stack (most recent call first):
tests/CMakeLists.txt:3 (include)
  -- checking for module 'process-cpp'
  --   package 'process-cpp' not found
  -- Configuring incomplete, errors occurred!
  See also 
/home/liuxg/release/build-scopetest1-UbuntuSDK_for_i386_GCC_ubuntu_sdk_14_10_utopic-Default/CMakeFiles/CMakeOutput.log.
  CMake Error at /usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:283 (message):
A required package was not found
  Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:337 
(_pkg_check_modules_internal)
tests/CMakeLists.txt:6 (pkg_check_modules)

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

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


[Touch-packages] [Bug 1390919] Re: Scope template cannot be running for devel emulator

2014-11-19 Thread Zoltan Balogh
From the QtC we create click chroot with this command:

$ click chroot -a $ARCHITECTURE -f $FRAMEWORK -n $NAME create

It is imortant to note that there is no reliable update mechanism for
the click chroots other than logging in and apt-get update  apt-get
dist-upgrade. But even apt does not automatically bring these packages
if the chroot is an old one.

I would suggest to destroy recreate the click chroot.

** Changed in: click (Ubuntu)
 Assignee: Zoltan Balogh (bzoltan) = (unassigned)

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

Title:
  Scope  template cannot be running for devel emulator

Status in “click” package in Ubuntu:
  Incomplete

Bug description:
  Some libs are missing in the chroot, and the scope cannot be running
  for emulator (devel i386). Attached please find the captured screen.

  -- package 'process-cpp' not found
  -- package 'net-cpp=1.1.0' not found
  -- package 'net-cpp=1.1.0' not found

  

  -- The CXX compiler identification is GNU 4.9.1
  -- Check for working CXX compiler: /usr/bin/i686-linux-gnu-g++
  -- Check for working CXX compiler: /usr/bin/i686-linux-gnu-g++ -- works
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Found PkgConfig: /usr/bin/pkg-config (found version 0.28)
  -- Boost version: 1.55.0
  -- checking for modules 'libunity-scopes=0.6.0;net-cpp=1.1.0'
  --   package 'net-cpp=1.1.0' not found
  CMake Error at /usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:283 (message):
A required package was not found
  Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:337 
(_pkg_check_modules_internal)
CMakeLists.txt:34 (pkg_check_modules)
  -- Found Gettext: /usr/bin/msgmerge (found version 0.19.2)
  -- Found XGettext: /usr/bin/xgettext (found version 0.19.2)
  CMake Error at cmake/FindGMock.cmake:6 (add_subdirectory):
add_subdirectory given source /usr/src/gmock which is not an existing
directory.
  Call Stack (most recent call first):
tests/CMakeLists.txt:3 (include)
  -- checking for module 'process-cpp'
  --   package 'process-cpp' not found
  -- Configuring incomplete, errors occurred!
  See also 
/home/liuxg/release/build-scopetest1-UbuntuSDK_for_i386_GCC_ubuntu_sdk_14_10_utopic-Default/CMakeFiles/CMakeOutput.log.
  CMake Error at /usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:283 (message):
A required package was not found
  Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:337 
(_pkg_check_modules_internal)
tests/CMakeLists.txt:6 (pkg_check_modules)

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

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


[Touch-packages] [Bug 655619] [NEW] Hinting: tilde/macron confusion at small sizes (ãñõÕ)

2014-11-19 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

1. Copy and paste this line into the address field of a Web browser:
data:text/html;charset=UTF-8,p style=font-family:Ubuntu;font-size:20;  
ñĀÃāãŌÕōõ/p

2. Reduce the font-size until the tildes ˜ become indistinguishable from
the macrons ¯.

Rendered in 13pt Regular

Sample Glyphs:

õ

Description:

At size 18 and less õ looks o that doesn't have tilde but simple line on
it. I don't know if it's a bug but there may be different similar
letters in other languages. Õ is estonian font.

UA String:

Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.10) Gecko/20100915
Ubuntu/10.04 (lucid) Firefox/3.6.10

** Affects: freetype (Ubuntu)
 Importance: Medium
 Status: Triaged

-- 
Hinting: tilde/macron confusion at small sizes (ãñõÕ)
https://bugs.launchpad.net/bugs/655619
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to freetype in Ubuntu.

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


[Touch-packages] [Bug 1394253] [NEW] Bluetooth discoverability confusing

2014-11-19 Thread Michał Sawicz
Public bug reported:

Steps to reproduce:
1. go to Bluetooth in Settings
2. go out of the Bluetooth pane

When going in, the page says Discoverable and lists the name. When you
go out... is it still discoverable? Was it already discoverable before?

The indicator icon (or menu) doesn't change, either, so there's
basically no way to know if you're discoverable when outside of the
settings page.

** Affects: ubuntu-ux
 Importance: Undecided
 Status: New

** Affects: indicator-bluetooth (Ubuntu)
 Importance: Undecided
 Status: New

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

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

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

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

Title:
  Bluetooth discoverability confusing

Status in Ubuntu UX bugs:
  New
Status in “indicator-bluetooth” package in Ubuntu:
  New
Status in “ubuntu-system-settings” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. go to Bluetooth in Settings
  2. go out of the Bluetooth pane

  When going in, the page says Discoverable and lists the name. When
  you go out... is it still discoverable? Was it already discoverable
  before?

  The indicator icon (or menu) doesn't change, either, so there's
  basically no way to know if you're discoverable when outside of the
  settings page.

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

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


  1   2   3   >