[Touch-packages] [Bug 1301015] Re: Networking does not restart

[Piotr Żurek]

** Changed in: ifupdown (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Networking does not restart

Status in ifupdown package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu Server 14.04 it appears it is not possible to restart
  networking. This is fresh install from ISO.

  wirehive@ubuntu:~$ sudo /etc/init.d/networking restart
  wirehive@ubuntu:~$ echo $?
  1
  wirehive@ubuntu:~$ sudo service networking restart
  stop: Job failed while stopping
  start: Job is already running: networking
  wirehive@ubuntu:~$ sudo bash -x /etc/init.d/networking restart
  + PATH=/sbin:/bin
  + RUN_DIR=/run/network
  + IFSTATE=/run/network/ifstate
  + STATEDIR=/run/network/state
  + '[' -x /sbin/ifup ']'
  + '[' -x /sbin/ifdown ']'
  + . /lib/lsb/init-functions
  +++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
  ++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 
2>/dev/null)'
  ++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']'
  ++ . /lib/lsb/init-functions.d/20-left-info-blocks
  ++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 
2>/dev/null)'
  ++ '[' -r /lib/lsb/init-functions.d/50-ubuntu-logging ']'
  ++ . /lib/lsb/init-functions.d/50-ubuntu-logging
  +++ LOG_DAEMON_MSG=
  ++ FANCYTTY=
  ++ '[' -e /etc/lsb-base-logging.sh ']'
  ++ true
  + CONFIGURE_INTERFACES=yes
  + EXCLUDE_INTERFACES=
  + VERBOSE=no
  + '[' -f /etc/default/networking ']'
  + verbose=
  + '[' no = yes ']'
  + case "$1" in
  + init_is_upstart
  + '[' -x /sbin/initctl ']'
  + /bin/grep -q upstart
  + /sbin/initctl version
  + return 0
  + exit 1
  wirehive@ubuntu:~$ sudo bash -x service networking restart
  ++ basename service
  + VERSION='service ver. 0.91-ubuntu1'
  ++ basename service
  + USAGE='Usage: service < option > | --status-all | [ service_name [ command 
| --full-restart ] ]'
  + SERVICE=
  + ACTION=
  + SERVICEDIR=/etc/init.d
  + OPTIONS=
  + '[' 2 -eq 0 ']'
  + cd /
  + '[' 2 -gt 0 ']'
  + case "${1}" in
  + '[' -z '' -a 2 -eq 1 -a networking = --status-all ']'
  + '[' 2 -eq 2 -a restart = --full-restart ']'
  + '[' -z '' ']'
  + SERVICE=networking
  + shift
  + '[' 1 -gt 0 ']'
  + case "${1}" in
  + '[' -z networking -a 1 -eq 1 -a restart = --status-all ']'
  + '[' 1 -eq 2 -a '' = --full-restart ']'
  + '[' -z networking ']'
  + '[' -z '' ']'
  + ACTION=restart
  + shift
  + '[' 0 -gt 0 ']'
  + '[' -r /etc/init/networking.conf ']'
  + which initctl
  + grep -q upstart
  + initctl version
  + case "${ACTION}" in
  + stop networking
  stop: Job failed while stopping
  + :
  + exec start networking
  start: Job is already running: networking
  wirehive@ubuntu:~$

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

-- 
Mailing list: https://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 1326513] Re: Applications are orphaned when unity8 crashes

[Michał Sawicz]

> We already have a stop on application-end or desktop-end. I think one of
> those should be enough if we want to kill all the applications. I'm a
> bit surprised they survive Mir dying though. Perhaps libmir-client
> should issue a shutdown when it sees the other end die.

That happens already, but when the app is suspended, it doesn't get the
memo that mir died. And if unity8 dies, it will just respawn, so there's
no desktop-end or application-end emitted.

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

Title:
  Applications are orphaned when unity8 crashes

Status in Mir:
  Expired
Status in Qt integration with the Mir display server:
  Triaged
Status in ubuntu-app-launch package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  For some reason Unity8 crashed on me. The applications I had open are
  now orphaned. They're still running but you can't get to it as it no
  longer shows up under the recent applications. In addition if I
  attempt to start the app, it fails to run or come back from orphaned
  state, so I have to restart.

  My unity process where Unity8 died an hour or two back.

  lightdm   1871  0.0  0.0   1392   464 ?Ss   10:06   0:00 /bin/sh 
/usr/lib/lightdm/lightdm-greeter-session /usr/bin/unity8-greeter-wrapper 
/usr/bin/unity8-greeter
  lightdm   1875  0.0  0.0   1392   472 ?S10:06   0:00 /bin/sh 
/usr/bin/unity8-greeter-wrapper /usr/bin/unity8-greeter
  lightdm   2362  0.2  5.0 343724 95000 ?Sl   10:06   1:47 
/usr/bin/unity8-greeter
  phablet  22852  0.4  5.6 452692 105852 ?   Ssl  19:03   0:34 unity8

  The application:-

  phablet   8503 10.3  8.6 297792 161652 ?   Ssl  11:33  59:33
  /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene ubuntu-calculator-
  app.qml

  Now when I start calculator it just white-screens.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.87+14.10.20140603.1-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  Date: Wed Jun  4 21:04:34 2014
  InstallationDate: Installed on 2014-06-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140604)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1390393] Re: It's too easy to trigger a volume notification when taking a screenshot

[Michał Sawicz]

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

Title:
  It's too easy to trigger a volume notification when taking a
  screenshot

Status in the base for Ubuntu mobile products:
  Fix Released
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu RTM:
  Fix Released

Bug description:
  On Mako, I'm unable to take a screenshot (Vol up + Vol down) without
  changing the volume, which causes a notification to appear on the
  screenshot, and changes the volume when taking a screenshot.

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

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

[Touch-packages] [Bug 1393447] Re: Launcher over greeter should remain on screen if the left edge gesture did not swipe the greeter away

[Michał Sawicz]

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

Title:
  Launcher over greeter should remain on screen if the left edge gesture
  did not swipe the greeter away

Status in the base for Ubuntu mobile products:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  Fix Released

Bug description:
  Preconditions:
  * Have the screen lock method configured to use a PIN code

  Steps:
  * swipe from the left edge so that the welcome screen (Greeter) is moved, but 
springs back into place

  Expected:
  * launcher remains on screen

  Current:
  * launcher hides

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.01+15.04.20141107.2-0ubuntu2
  Uname: Linux 3.18.0-031800rc4-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 17 16:01:43 2014
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1411751] Re: Attribute in news section of today scope has wrong aspect ratio depending on grid size

[Michał Sawicz]

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

Title:
  Attribute in news section of today scope has wrong aspect ratio
  depending on grid size

Status in the base for Ubuntu mobile products:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  Fix Released

Bug description:
  Open the Today scope in Arale
  Go to News section
  BBC attribute aspect ratio is not correct.

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

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

[Touch-packages] [Bug 1418060] Re: [FFe] QML compilation cache patch needs adaptation for Qt 5.4

[Timo Jyrinki]

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  [FFe] QML compilation cache patch needs adaptation for Qt 5.4

Status in qtdeclarative-opensource-src package in Ubuntu:
  In Progress

Bug description:
  -- FFe --

  Since we're past the feature freeze, bringing this patch back needs an 
exception, even though it's a regression fix at the same time. Summary:
  - The patch allows opt-in, environment variable controlled use of storing 
some cache data when loading QML files. Without the environment variable there 
are no changes.
  - Not having the patch is a performance regression on application startup 
time on the phones from Qt 5.3.2.
  - The patch already shipped in Qt 5.3.2, but needed adjustments for 5.4 that 
were not done on time when Qt 5.4 was otherwise ready to land before feature 
freeze, so the patch was commented out.
  - The patch is also shipping on the sold Bq phones.
  - The proposed changes are in the MP below, that is uncommenting the patch in 
debian/patches/series and the rebasing (the full patch is 25 files changed, 703 
insertions(+), 14 deletions(-)).

  As usual, we have a wide testing being done also on this rebased-to-
  Qt-5.4.0 patch.

  Upstreaming is being considered now that the patch seems to work for
  our purposes. It might need more than code discussions since upstream
  developer is also selling a proprietary product that offers somewhat
  similar benefits.

  -- Original bug report --

  The environment variable controlled new functionality provided by QML
  compilation cache patch (landed for Qt 5.3.2) needs adaptation for Qt
  5.4, as it does not currently apply.

  Attachment shows a summary of the patch applying problems.

  More information about Qt 5.4 at
  https://wiki.ubuntu.com/Touch/QtTesting

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

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

[Touch-packages] [Bug 1418060] Re: QML compilation cache patch needs adaptation for Qt 5.4

[Timo Jyrinki]

** Description changed:

+ -- FFe --
+ 
+ Since we're past the feature freeze, bringing this patch back needs an 
exception, even though it's a regression fix at the same time. Summary:
+ - The patch allows opt-in, environment variable controlled use of storing 
some cache data when loading QML files. Without the environment variable there 
are no changes.
+ - Not having the patch is a performance regression on application startup 
time on the phones from Qt 5.3.2.
+ - The patch already shipped in Qt 5.3.2, but needed adjustments for 5.4 that 
were not done on time when Qt 5.4 was otherwise ready to land before feature 
freeze, so the patch was commented out.
+ - The patch is also shipping on the sold Bq phones.
+ - The proposed changes are in the MP below, that is uncommenting the patch in 
debian/patches/series and the rebasing (the full patch is 25 files changed, 703 
insertions(+), 14 deletions(-)).
+ 
+ As usual, we have a wide testing being done also on this rebased-to-
+ Qt-5.4.0 patch.
+ 
+ Upstreaming is being considered now that the patch seems to work for our
+ purposes. It might need more than code discussions since upstream
+ developer is also selling a proprietary product that offers somewhat
+ similar benefits.
+ 
+ -- Original bug report --
+ 
  The environment variable controlled new functionality provided by QML
- compilation cache patch (being landed for Qt 5.3.2) needs adaptation for
- Qt 5.4, as it does not currently apply.
+ compilation cache patch (landed for Qt 5.3.2) needs adaptation for Qt
+ 5.4, as it does not currently apply.
  
- Attachment shows a summary of the problems.
+ Attachment shows a summary of the patch applying problems.
  
  More information about Qt 5.4 at https://wiki.ubuntu.com/Touch/QtTesting

** Summary changed:

- QML compilation cache patch needs adaptation for Qt 5.4
+ [FFe] QML compilation cache patch needs adaptation for Qt 5.4

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

Title:
  [FFe] QML compilation cache patch needs adaptation for Qt 5.4

Status in qtdeclarative-opensource-src package in Ubuntu:
  Triaged

Bug description:
  -- FFe --

  Since we're past the feature freeze, bringing this patch back needs an 
exception, even though it's a regression fix at the same time. Summary:
  - The patch allows opt-in, environment variable controlled use of storing 
some cache data when loading QML files. Without the environment variable there 
are no changes.
  - Not having the patch is a performance regression on application startup 
time on the phones from Qt 5.3.2.
  - The patch already shipped in Qt 5.3.2, but needed adjustments for 5.4 that 
were not done on time when Qt 5.4 was otherwise ready to land before feature 
freeze, so the patch was commented out.
  - The patch is also shipping on the sold Bq phones.
  - The proposed changes are in the MP below, that is uncommenting the patch in 
debian/patches/series and the rebasing (the full patch is 25 files changed, 703 
insertions(+), 14 deletions(-)).

  As usual, we have a wide testing being done also on this rebased-to-
  Qt-5.4.0 patch.

  Upstreaming is being considered now that the patch seems to work for
  our purposes. It might need more than code discussions since upstream
  developer is also selling a proprietary product that offers somewhat
  similar benefits.

  -- Original bug report --

  The environment variable controlled new functionality provided by QML
  compilation cache patch (landed for Qt 5.3.2) needs adaptation for Qt
  5.4, as it does not currently apply.

  Attachment shows a summary of the patch applying problems.

  More information about Qt 5.4 at
  https://wiki.ubuntu.com/Touch/QtTesting

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

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

[Touch-packages] [Bug 1418060] Re: QML compilation cache patch needs adaptation for Qt 5.4

[Timo Jyrinki]

** Branch linked: lp:~timo-jyrinki/kubuntu-packaging/qtdeclarative-
opensource-src_reenable_qmlcache

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

Title:
  QML compilation cache patch needs adaptation for Qt 5.4

Status in qtdeclarative-opensource-src package in Ubuntu:
  Triaged

Bug description:
  The environment variable controlled new functionality provided by QML
  compilation cache patch (being landed for Qt 5.3.2) needs adaptation
  for Qt 5.4, as it does not currently apply.

  Attachment shows a summary of the problems.

  More information about Qt 5.4 at
  https://wiki.ubuntu.com/Touch/QtTesting

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

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

[Touch-packages] [Bug 508522] Re: Mic is not available with A2DP Bluetooth profile

[floeschie]

+1

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

Title:
  Mic is not available with A2DP Bluetooth profile

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pulseaudio

  I'm testing a Nokia BH-905i headset (see 
http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The 
Bluetooth module correctly identifies the headset and the both audio profiles 
"HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music 
playback only A2DP is suitable (HSP/HFP sounds like listening to music played 
through an old telephone). A2DP does not have an INPUT mode, so use of the 
headset for VoiP isn't possible.
  What would be needed is a separate selection to allow to select A2DP for 
output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do 
that (or they switch on the fly?).

  Formal structure:
  1) Ubuntu 10.10
  2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  consisting og pluseaudio, pulseaudio-esound-compat, 
pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, 
pulseaudio-utils
  3) Select high quality audio output and still use the Bluetooth microphone
  4) Had to choose: either high quality audio or "telephone quality" with 
microphone

  I can change the profile without the Bluetooth connection dropping,
  but that's ridiculous. E.g. listening to music, a call comes in. Then
  I would need to switch the profile before answering. Please note that
  in Windows, Mac OS, iOS, Android, and Windows Mobile it's done
  automatically.

  Check out attached screencast.

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oivasyuv   2309 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17'
     Mixer name : 'Analog Devices AD1984A'
     Components : 'HDA:11d4194a,103c30e8,00100400'
     Controls  : 22
     Simple ctrls  : 14
  Date: Sat Jan 16 22:31:41 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: pulseaudio 1:0.9.19-0ubuntu4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-17-generic-pae i686

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

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

[Touch-packages] [Bug 1424992] Re: files in /tmp not being cleared on boot

[Bug Watch Updater]

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

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

Title:
  files in /tmp not being cleared on boot

Status in systemd package in Ubuntu:
  In Progress
Status in systemd package in Debian:
  New

Bug description:
  My system has been booted for 2 1/2 hours and yet /tmp contains old
  files from 2015-02-19.

  $ sudo systemctl|grep tmpfiles
  systemd-tmpfiles-setup-dev.service
 loaded active exited
Create Static Device Nodes in /dev
  systemd-tmpfiles-setup.service
 loaded active exited
Create Volatile Files and Directories
  systemd-tmpfiles-clean.timer  
 loaded active waiting   
Daily Cleanup of Temporary Directories

  $ sudo journalctl -a|grep tmpfiles
  Feb 24 07:27:08 faire systemd-tmpfiles[701]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  Feb 24 07:41:38 faire systemd-tmpfiles[31258]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.

  $ sudo du -sh /tmp
  481M/tmp
  $ sudo SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --clean 
/usr/lib/tmpfiles.d/tmp.conf
  Reading config file "/usr/lib/tmpfiles.d/tmp.conf".
  Running clean action for entry v /tmp
  Running clean action for entry X 
/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*/tmp
  Running clean action for entry x 
/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*
  Running clean action for entry x 
/var/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*
  Running clean action for entry X 
/var/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*/tmp
  $ sudo du -sh /tmp
  481M/tmp
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-3ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 24 09:55:29 2015
  InstallationDate: Installed on 2014-04-11 (318 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409)
  MachineType: LENOVO 20AQCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro init=/lib/systemd/systemd quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-05-08 (291 days ago)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQCTO1WW
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1423359] Re: taking screenshots with mirscreencast fails if env locale does not exist

[Martin Pitt]

** Summary changed:

- taking screenshots with mirscreencast fails if locale is not C.
+ taking screenshots with mirscreencast fails if env locale does not exist

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

Title:
  taking screenshots with mirscreencast fails if env locale does not
  exist

Status in Mir:
  New
Status in autopkgtest package in Ubuntu:
  Fix Released
Status in mir package in Ubuntu:
  Triaged

Bug description:
  From autopilot we see this when there is a failed test.

  21:40:25.138 ERROR testcase:387 - Taking screenshot failed: Command
  '['mirscreencast', '-m', '/run/mir_socket', '-n', '1', '-f', '/tmp/ap-
  screenshot-data-1424295625.rgba']' returned non-zero exit status 1

  I tried setting the LC_ALL env var to C, and it works.

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

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

[Touch-packages] [Bug 1424992] Re: files in /tmp not being cleared on boot

[Martin Pitt]

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

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

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

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

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

Title:
  files in /tmp not being cleared on boot

Status in systemd package in Ubuntu:
  New
Status in systemd package in Debian:
  Unknown

Bug description:
  My system has been booted for 2 1/2 hours and yet /tmp contains old
  files from 2015-02-19.

  $ sudo systemctl|grep tmpfiles
  systemd-tmpfiles-setup-dev.service
 loaded active exited
Create Static Device Nodes in /dev
  systemd-tmpfiles-setup.service
 loaded active exited
Create Volatile Files and Directories
  systemd-tmpfiles-clean.timer  
 loaded active waiting   
Daily Cleanup of Temporary Directories

  $ sudo journalctl -a|grep tmpfiles
  Feb 24 07:27:08 faire systemd-tmpfiles[701]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  Feb 24 07:41:38 faire systemd-tmpfiles[31258]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.

  $ sudo du -sh /tmp
  481M/tmp
  $ sudo SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --clean 
/usr/lib/tmpfiles.d/tmp.conf
  Reading config file "/usr/lib/tmpfiles.d/tmp.conf".
  Running clean action for entry v /tmp
  Running clean action for entry X 
/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*/tmp
  Running clean action for entry x 
/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*
  Running clean action for entry x 
/var/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*
  Running clean action for entry X 
/var/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*/tmp
  $ sudo du -sh /tmp
  481M/tmp
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-3ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 24 09:55:29 2015
  InstallationDate: Installed on 2014-04-11 (318 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409)
  MachineType: LENOVO 20AQCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro init=/lib/systemd/systemd quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-05-08 (291 days ago)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQCTO1WW
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1424992] Re: files in /tmp not being cleared on boot

[Martin Pitt]

** Changed in: systemd (Ubuntu)
   Status: New => 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/1424992

Title:
  files in /tmp not being cleared on boot

Status in systemd package in Ubuntu:
  In Progress
Status in systemd package in Debian:
  Unknown

Bug description:
  My system has been booted for 2 1/2 hours and yet /tmp contains old
  files from 2015-02-19.

  $ sudo systemctl|grep tmpfiles
  systemd-tmpfiles-setup-dev.service
 loaded active exited
Create Static Device Nodes in /dev
  systemd-tmpfiles-setup.service
 loaded active exited
Create Volatile Files and Directories
  systemd-tmpfiles-clean.timer  
 loaded active waiting   
Daily Cleanup of Temporary Directories

  $ sudo journalctl -a|grep tmpfiles
  Feb 24 07:27:08 faire systemd-tmpfiles[701]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  Feb 24 07:41:38 faire systemd-tmpfiles[31258]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.

  $ sudo du -sh /tmp
  481M/tmp
  $ sudo SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --clean 
/usr/lib/tmpfiles.d/tmp.conf
  Reading config file "/usr/lib/tmpfiles.d/tmp.conf".
  Running clean action for entry v /tmp
  Running clean action for entry X 
/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*/tmp
  Running clean action for entry x 
/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*
  Running clean action for entry x 
/var/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*
  Running clean action for entry X 
/var/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*/tmp
  $ sudo du -sh /tmp
  481M/tmp
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-3ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 24 09:55:29 2015
  InstallationDate: Installed on 2014-04-11 (318 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409)
  MachineType: LENOVO 20AQCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro init=/lib/systemd/systemd quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-05-08 (291 days ago)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQCTO1WW
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1004792] Re: unattended-upgrade crashed with IOError: [Errno 9] Bad file descriptor

[Launchpad Bug Tracker]

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

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

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

Title:
  unattended-upgrade crashed with IOError: [Errno 9] Bad file descriptor

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Always happens as i logon

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: unattended-upgrades 0.76
  Uname: Linux 3.4.0-030400-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  CrashCounter: 1
  Date: Fri May 25 01:09:56 2012
  ExecutablePath: /usr/bin/unattended-upgrade
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/unattended-upgrade
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/sh
  PythonArgs: ['/usr/bin/unattended-upgrade']
  SourcePackage: unattended-upgrades
  Title: unattended-upgrade crashed with IOError: [Errno 9] Bad file descriptor
  Traceback: IOError: [Errno 9] Bad file descriptor
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1004792] Re: unattended-upgrade crashed with IOError: [Errno 9] Bad file descriptor

[Tuomas Heino]

Fyi, crash reporter claimed two instances of running out of space being
DuplicateOf this bug.

In case of running out of inodes or disk space, crash reporter's "If you
notice further problems, try restarting the computer." advice sounds
rather harmful. Maybe a topic for another bug report though.

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

Title:
  unattended-upgrade crashed with IOError: [Errno 9] Bad file descriptor

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Always happens as i logon

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: unattended-upgrades 0.76
  Uname: Linux 3.4.0-030400-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  CrashCounter: 1
  Date: Fri May 25 01:09:56 2012
  ExecutablePath: /usr/bin/unattended-upgrade
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/unattended-upgrade
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/sh
  PythonArgs: ['/usr/bin/unattended-upgrade']
  SourcePackage: unattended-upgrades
  Title: unattended-upgrade crashed with IOError: [Errno 9] Bad file descriptor
  Traceback: IOError: [Errno 9] Bad file descriptor
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

-- 
Mailing list: https://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 1333140] Re: Fix udev rules to consider mmc rpmb partitions

[Martin Pitt]

Hello Simon,

simon thunder [2015-02-25  5:47 -]:
> I'm a Linux beginner and I'd like to know how to install the patch. Can
> anybody tell me how? Thank you!

See comment #42 in this bug report. It's documented here:
https://wiki.ubuntu.com/Testing/EnableProposed

Thanks!

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

Title:
  Fix udev rules to consider mmc rpmb partitions

Status in systemd package in Ubuntu:
  Fix Released
Status in udev package in Ubuntu:
  Invalid
Status in udisks package in Ubuntu:
  Triaged
Status in udev source package in Precise:
  Triaged
Status in udisks source package in Precise:
  Confirmed
Status in systemd source package in Trusty:
  Fix Committed
Status in udisks source package in Trusty:
  Confirmed

Bug description:
  As per JEDEC 4.5 spec for eMMC devices,
  There is a new partitions as part of eMMC storage devices it self. (Further 
details please refer eMMC spec)

  *In Linux Kernel@ 3.10.33, mmc driver has created a new partitions
  with "mmcblkXrpmb" if device expresses it support of RPMB.

  Issues observed:

  issue 1:
  RPMB (Replay Protected Memory Block), A signed access to a Replay Protected 
Memory Block is provided. This function provides means for the system to store 
data to the specific memory area in an authenticated and replay protected 
manner.
  In that case, any read/write access to this partition device will report 
errors.

  issue 2:
  The by-path, line is wrongly mapping to platform-sdhci-tegra.1  -> 
mmcblk2rpmb were as
  it should be platform-sdhci-tegra.1  -> mmcblk2

  ls -l /dev/disk/by-path/
  total 0
  lrwxrwxrwx 1 root root 17 Jan  3  2000 platform-sdhci-tegra.1 -> 
../../mmcblk2rpmb
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.1-part1 -> 
../../mmcblk2p1
  lrwxrwxrwx 1 root root 13 Jan  3  2000 platform-sdhci-tegra.2 -> ../../mmcblk1
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.2-part1 -> 
../../mmcblk1p1
  lrwxrwxrwx 1 root root 17 Jan  3  2000 platform-sdhci-tegra.3 -> 
../../mmcblk0rpmb
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.3-part1 -> 
../../mmcblk0p1
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.3-part2 -> 
../../mmcblk0p2

  We have locally resolved in our platform in this file 60-persistent-
  storage.rules

  For issue 1: (with this rule)
  # skip block read for partitions of type rpmb
  KERNEL=="mmcblk[0-9]rpmb", SUBSYSTEM=="block", GOTO="persistent_storage_end"

  For issue 2:
  ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL=="mmcblk[0-9]rpmb", 
SYMLINK+="disk/by-path/$env{ID_PATH}-rpmb"
  ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL!="mmcblk[0-9]rpmb", 
SYMLINK+="disk/by-path/$env{ID_PATH}"

  Please consider this issues fix in next udev release .

  
  SRU INFO: This is mostly an issue with running backported kernels on 12.04 
and 14.04. There is no test case which would reproduce this on arbitrary 
hardware, but there are several reporters which are in a position to verify a 
proposed update.

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

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

[Touch-packages] [Bug 1425398] Re: Apparmor uses rsyslogd profile for different processes

[Pavel Malyshev]

I can confirm that the audit message is gone from /var/log/syslog after
I got back to the original 3.13.0-46 Ubuntu 14.04.2 kernel.

** Summary changed:

- Apparmor uses rsyslogd profile for different processes
+ Apparmor uses rsyslogd profile for different processes - utopic HWE

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

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

Title:
  Apparmor uses rsyslogd profile for different processes - utopic HWE

Status in apparmor package in Ubuntu:
  New
Status in linux-lts-utopic package in Ubuntu:
  New

Bug description:
  Hi.

  I've noticed that apparmor loads /usr/sbin/rsyslogd profile for
  completely unrelated processes:

  Feb 25 08:36:19 emma kernel: [  134.796218] audit: type=1400 
audit(1424842579.429:245): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/rsyslogd" name="/dev/log" pid=4002 comm="sshd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Feb 25 08:36:23 emma kernel: [  139.330989] audit: type=1400 
audit(1424842583.965:246): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/rsyslogd" name="/dev/log" pid=4080 comm="sudo" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Feb 25 08:35:42 emma kernel: [   97.912402] audit: type=1400 
audit(1424842542.565:241): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/rsyslogd" name="/dev/log" pid=2436 comm="whoopsie" 
requested_mask="r" denied_mask="r" fsuid=103 ouid=0
  Feb 25 08:34:43 emma kernel: [   38.867998] audit: type=1400 
audit(1424842483.546:226): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/rsyslogd" name="/dev/log" pid=3762 comm="ntpd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  
  I'm not sure how apparmor decides which profile to use for which task, but is 
shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc.

  
  I'm running:
  # lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  # dpkg -l | grep apparmor
  ii  apparmor2.8.95~2430-0ubuntu5.1   
amd64User-space parser utility for AppArmor
  ii  apparmor-profiles   2.8.95~2430-0ubuntu5.1   
all  Profiles for AppArmor Security policies
  ii  apparmor-utils  2.8.95~2430-0ubuntu5.1   
amd64Utilities for controlling AppArmor
  ii  libapparmor-perl2.8.95~2430-0ubuntu5.1   
amd64AppArmor library Perl bindings
  ii  libapparmor1:amd64  2.8.95~2430-0ubuntu5.1   
amd64changehat AppArmor library
  ii  python3-apparmor2.8.95~2430-0ubuntu5.1   
amd64AppArmor Python3 utility library
  ii  python3-libapparmor 2.8.95~2430-0ubuntu5.1   
amd64AppArmor library Python3 bindings

  # uname -a
  Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

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

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

[Touch-packages] [Bug 1425398] Re: Apparmor uses rsyslogd profile for different processes

[Pavel Malyshev]

This errors started appearing in the log since Feb 21 when I've rebooted to 
complete Utopic HWE installation:
# dpkg -l | grep utopic
ii  linux-generic-lts-utopic3.16.0.31.24 
amd64Complete Generic Linux kernel and headers
ii  linux-headers-generic-lts-utopic3.16.0.31.24 
amd64Generic Linux kernel headers
ii  linux-image-generic-lts-utopic  3.16.0.31.24 
amd64Generic Linux kernel image

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

Title:
  Apparmor uses rsyslogd profile for different processes

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi.

  I've noticed that apparmor loads /usr/sbin/rsyslogd profile for
  completely unrelated processes:

  Feb 25 08:36:19 emma kernel: [  134.796218] audit: type=1400 
audit(1424842579.429:245): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/rsyslogd" name="/dev/log" pid=4002 comm="sshd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Feb 25 08:36:23 emma kernel: [  139.330989] audit: type=1400 
audit(1424842583.965:246): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/rsyslogd" name="/dev/log" pid=4080 comm="sudo" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Feb 25 08:35:42 emma kernel: [   97.912402] audit: type=1400 
audit(1424842542.565:241): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/rsyslogd" name="/dev/log" pid=2436 comm="whoopsie" 
requested_mask="r" denied_mask="r" fsuid=103 ouid=0
  Feb 25 08:34:43 emma kernel: [   38.867998] audit: type=1400 
audit(1424842483.546:226): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/rsyslogd" name="/dev/log" pid=3762 comm="ntpd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  
  I'm not sure how apparmor decides which profile to use for which task, but is 
shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc.

  
  I'm running:
  # lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  # dpkg -l | grep apparmor
  ii  apparmor2.8.95~2430-0ubuntu5.1   
amd64User-space parser utility for AppArmor
  ii  apparmor-profiles   2.8.95~2430-0ubuntu5.1   
all  Profiles for AppArmor Security policies
  ii  apparmor-utils  2.8.95~2430-0ubuntu5.1   
amd64Utilities for controlling AppArmor
  ii  libapparmor-perl2.8.95~2430-0ubuntu5.1   
amd64AppArmor library Perl bindings
  ii  libapparmor1:amd64  2.8.95~2430-0ubuntu5.1   
amd64changehat AppArmor library
  ii  python3-apparmor2.8.95~2430-0ubuntu5.1   
amd64AppArmor Python3 utility library
  ii  python3-libapparmor 2.8.95~2430-0ubuntu5.1   
amd64AppArmor library Python3 bindings

  # uname -a
  Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

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

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

[Touch-packages] [Bug 1333140] Re: Fix udev rules to consider mmc rpmb partitions

[simon thunder]

I Have the same problem with my new netbook using Trisquel 7 (based on
Ubuntu 14.04).

I'm a Linux beginner and I'd like to know how to install the patch. Can
anybody tell me how? Thank you!

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

Title:
  Fix udev rules to consider mmc rpmb partitions

Status in systemd package in Ubuntu:
  Fix Released
Status in udev package in Ubuntu:
  Invalid
Status in udisks package in Ubuntu:
  Triaged
Status in udev source package in Precise:
  Triaged
Status in udisks source package in Precise:
  Confirmed
Status in systemd source package in Trusty:
  Fix Committed
Status in udisks source package in Trusty:
  Confirmed

Bug description:
  As per JEDEC 4.5 spec for eMMC devices,
  There is a new partitions as part of eMMC storage devices it self. (Further 
details please refer eMMC spec)

  *In Linux Kernel@ 3.10.33, mmc driver has created a new partitions
  with "mmcblkXrpmb" if device expresses it support of RPMB.

  Issues observed:

  issue 1:
  RPMB (Replay Protected Memory Block), A signed access to a Replay Protected 
Memory Block is provided. This function provides means for the system to store 
data to the specific memory area in an authenticated and replay protected 
manner.
  In that case, any read/write access to this partition device will report 
errors.

  issue 2:
  The by-path, line is wrongly mapping to platform-sdhci-tegra.1  -> 
mmcblk2rpmb were as
  it should be platform-sdhci-tegra.1  -> mmcblk2

  ls -l /dev/disk/by-path/
  total 0
  lrwxrwxrwx 1 root root 17 Jan  3  2000 platform-sdhci-tegra.1 -> 
../../mmcblk2rpmb
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.1-part1 -> 
../../mmcblk2p1
  lrwxrwxrwx 1 root root 13 Jan  3  2000 platform-sdhci-tegra.2 -> ../../mmcblk1
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.2-part1 -> 
../../mmcblk1p1
  lrwxrwxrwx 1 root root 17 Jan  3  2000 platform-sdhci-tegra.3 -> 
../../mmcblk0rpmb
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.3-part1 -> 
../../mmcblk0p1
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.3-part2 -> 
../../mmcblk0p2

  We have locally resolved in our platform in this file 60-persistent-
  storage.rules

  For issue 1: (with this rule)
  # skip block read for partitions of type rpmb
  KERNEL=="mmcblk[0-9]rpmb", SUBSYSTEM=="block", GOTO="persistent_storage_end"

  For issue 2:
  ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL=="mmcblk[0-9]rpmb", 
SYMLINK+="disk/by-path/$env{ID_PATH}-rpmb"
  ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL!="mmcblk[0-9]rpmb", 
SYMLINK+="disk/by-path/$env{ID_PATH}"

  Please consider this issues fix in next udev release .

  
  SRU INFO: This is mostly an issue with running backported kernels on 12.04 
and 14.04. There is no test case which would reproduce this on arbitrary 
hardware, but there are several reporters which are in a position to verify a 
proposed update.

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

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

[Touch-packages] [Bug 1425398] [NEW] Apparmor uses rsyslogd profile for different processes

[Pavel Malyshev]

Public bug reported:

Hi.

I've noticed that apparmor loads /usr/sbin/rsyslogd profile for
completely unrelated processes:

Feb 25 08:36:19 emma kernel: [  134.796218] audit: type=1400 
audit(1424842579.429:245): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/rsyslogd" name="/dev/log" pid=4002 comm="sshd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Feb 25 08:36:23 emma kernel: [  139.330989] audit: type=1400 
audit(1424842583.965:246): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/rsyslogd" name="/dev/log" pid=4080 comm="sudo" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Feb 25 08:35:42 emma kernel: [   97.912402] audit: type=1400 
audit(1424842542.565:241): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/rsyslogd" name="/dev/log" pid=2436 comm="whoopsie" 
requested_mask="r" denied_mask="r" fsuid=103 ouid=0
Feb 25 08:34:43 emma kernel: [   38.867998] audit: type=1400 
audit(1424842483.546:226): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/rsyslogd" name="/dev/log" pid=3762 comm="ntpd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0


I'm not sure how apparmor decides which profile to use for which task, but is 
shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc.


I'm running:
# lsb_release -rd
Description:Ubuntu 14.04.2 LTS
Release:14.04

# dpkg -l | grep apparmor
ii  apparmor2.8.95~2430-0ubuntu5.1   
amd64User-space parser utility for AppArmor
ii  apparmor-profiles   2.8.95~2430-0ubuntu5.1   
all  Profiles for AppArmor Security policies
ii  apparmor-utils  2.8.95~2430-0ubuntu5.1   
amd64Utilities for controlling AppArmor
ii  libapparmor-perl2.8.95~2430-0ubuntu5.1   
amd64AppArmor library Perl bindings
ii  libapparmor1:amd64  2.8.95~2430-0ubuntu5.1   
amd64changehat AppArmor library
ii  python3-apparmor2.8.95~2430-0ubuntu5.1   
amd64AppArmor Python3 utility library
ii  python3-libapparmor 2.8.95~2430-0ubuntu5.1   
amd64AppArmor library Python3 bindings

# uname -a
Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

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

** Attachment added: "/var/log/syslog since boot"
   
https://bugs.launchpad.net/bugs/1425398/+attachment/4326921/+files/syslog-since-boot

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

Title:
  Apparmor uses rsyslogd profile for different processes

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi.

  I've noticed that apparmor loads /usr/sbin/rsyslogd profile for
  completely unrelated processes:

  Feb 25 08:36:19 emma kernel: [  134.796218] audit: type=1400 
audit(1424842579.429:245): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/rsyslogd" name="/dev/log" pid=4002 comm="sshd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Feb 25 08:36:23 emma kernel: [  139.330989] audit: type=1400 
audit(1424842583.965:246): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/rsyslogd" name="/dev/log" pid=4080 comm="sudo" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Feb 25 08:35:42 emma kernel: [   97.912402] audit: type=1400 
audit(1424842542.565:241): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/rsyslogd" name="/dev/log" pid=2436 comm="whoopsie" 
requested_mask="r" denied_mask="r" fsuid=103 ouid=0
  Feb 25 08:34:43 emma kernel: [   38.867998] audit: type=1400 
audit(1424842483.546:226): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/rsyslogd" name="/dev/log" pid=3762 comm="ntpd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  
  I'm not sure how apparmor decides which profile to use for which task, but is 
shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc.

  
  I'm running:
  # lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  # dpkg -l | grep apparmor
  ii  apparmor2.8.95~2430-0ubuntu5.1   
amd64User-space parser utility for AppArmor
  ii  apparmor-profiles   2.8.95~2430-0ubuntu5.1   
all  Profiles for AppArmor Security policies
  ii  apparmor-utils  2.8.95~2430-0ubuntu5.1   
amd64Utilities for controlling AppArmor
  ii  libapparmor-perl2.8.95~2430-0ubuntu5.1   
amd64AppArmor library Perl bindings
  ii  libapparmor1:amd64  2.8.95~2430-0ubuntu5.1   
amd64changehat AppArmor library
  ii  python3-apparmor2.8.95~2430-0ubuntu5.1   
amd64  

[Touch-packages] [Bug 1425297] Re: Sometimes indicator-datetime is not available in the UI after a reboot (vivid/mako)

[Charles Kerr]

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

Title:
  Sometimes indicator-datetime is not available in the UI after a reboot
  (vivid/mako)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  current build number: 110
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-02-24 04:34:45
  version version: 110
  version ubuntu: 20150224
  version device: 20150210
  version custom: 20150224

  See the attached picture.

  The only log entry I have for it:
  Indicator-Datetime-Message: static gboolean 
unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond(gint, 
GIOCondition, gpointer) triggered at 2015-02-24 20:24:48.605449 by GIOCondition 
1, read -1 bytes, found 0 interrupts

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

-- 
Mailing list: https://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 1424253] [NEW] RFE: procps tools should support lxc

[Serge Hallyn]

You can use /proc/pid/ns and /proc/pid/cgroup to group results into
containers.  One example shown today on the lxc-users mailing list is

ps -eo pidns,cgroup:50,pid,user,args --sort pidns

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

Title:
  RFE: procps tools should support lxc

Status in lxc package in Ubuntu:
  New

Bug description:
  Container management/monitoring is currently a pain, because procps do
  not support container, i.e. there is no way to tell the tools to
  "filter" the output wrt. a certain zone or to add a column, which
  shows the zone name a process belongs to.

  E.g. for what is needed:
  {ps|pgrep|pkill|top} ... -z $myzone 
  # show zone name as well
  {ps|top} -Z

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

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

[Touch-packages] [Bug 1420630] Re: indicator-sound menu icon disappeared after volume down to zero

[Ted Gould]

** Changed in: indicator-sound (Ubuntu)
   Status: New => Triaged

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

Title:
  indicator-sound menu icon disappeared after volume down to zero

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in indicator-sound package in Ubuntu:
  Triaged

Bug description:
  On the HP commercial notebooks, there're function keys to control volume.
  The menu volume icon will be disappeared if we volume down
  (with key combination: Fn+F6, you can also emulate the keys with "xdotool key 
XF86AudioLowerVolume") to zero then logout and back in.
  But if we just zero down volume(with the single volume on/off button), then 
logout and back in, the volume icon is still there.

  This issue is fixed with installing indicator-
  sound_12.10.2+14.10.20141010-0ubuntu1(Utopic)

  Package: indicator-sound_12.10.2+14.04.20140401-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-38.65stella1-generic 3.13.11.8
  Uname: Linux 3.13.0-38-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Wed Feb 11 14:18:50 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-datong140729-trusty-amd64-20150114-3
  InstallationDate: Installed on 2015-01-29 (13 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150114-08:50
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1420630/+subscriptions

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

[Touch-packages] [Bug 1418032] Re: "High volume" warning shown when no media playing

[Ted Gould]

TODO: Need to check this on the latest image, many notification changes.

** Changed in: indicator-sound (Ubuntu)
   Status: New => Incomplete

** Changed in: indicator-sound (Ubuntu)
   Importance: Undecided => High

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

Title:
  "High volume" warning shown when no media playing

Status in indicator-sound package in Ubuntu:
  Incomplete

Bug description:
  Steps:
  * connect a headset
  * increase the volume to maximum

  Expected:
  * volume notification shown without "High volume"  warning

  Current:
  * volume shown with "High volume" warning

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150129.1-0ubuntu1
  Uname: Linux 3.4.0-6-mako armv7l
  ActionStates: ({'mute': (true, signature '', []), 'phone-settings': 
(true, '', []), 'mic-volume': (true, '', [<1.0>]), 'scroll': (true, 'i', []), 
'high-volume': (true, '', []), 'desktop-settings': (true, '', []), 
'volume': (true, 'i', [<0.51995849609375>]), 'indicator-shown': (true, '', 
[]), 'root': (true, '', [<{'title': <'Dźwięk'>, 'accessible-desc': 
<'Głośność (silent 51%)'>, 'icon': <('themed', <['audio-volume-muted-panel', 
'audio-volume-muted', 'audio-volume', 'audio']>)>, 'visible': }>]), 
'silent-mode': (true, '', [])},)
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: armhf
  Date: Wed Feb  4 14:01:42 2015
  InstallationDate: Installed on 2015-02-02 (2 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150202-020204)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1418494] Re: volume bar thinks mouse is pressed if released outside area

[Ted Gould]

** Package changed: indicator-sound (Ubuntu) => ido (Ubuntu)

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

Title:
  volume bar thinks mouse is pressed if released outside area

Status in ido package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  - Open indicator-sound (click on volume icon)
  - Press the mouse in volume slide (don't release)
  - Move mouse to outside the slide widget (not on another button, or outside 
indicator-sound)
  - Release the mouse
  - Optional: click on the indicator-sound window where there is no button. 
Nothing happens, but you can click as much as you want. (Even if there is a 
button, the behavior is the same)
  - Move mouse back to volume slide

  Expected behavior: volume slider doesn't change with mouse motion

  Observed behavior: volume slider follows mouse motion as if mouse is
  still pressed

  ---

  I am reporting this bug here because particularly with indicator-
  sound, the volume slider is quite thin, so if you are not precise, you
  could release the mouse easily outside the area. What's more,
  sometimes you want to lower the volume because some music you don't
  want starts playing, so this could happen:

  - Lower the volume with a focus on changing the music
  - Moving fast, the mouse button release happens outside the slider area
  - Change the music
  - Move back to the slider with the intention of raising volume
  - BAM, the slider still thinks the mouse is pressed, and the volume may 
potentially be raised to maximum depending on where your mouse is.

  ---

  If I may suggest (based on guessing completely), the slider widget
  needs to check the state of the mouse button on mouse motion event.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-sound 12.10.2+14.10.20141010-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb  5 12:02:30 2015
  SourcePackage: indicator-sound
  UpgradeStatus: Upgraded to utopic on 2014-11-01 (95 days ago)

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

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

[Touch-packages] [Bug 1421943] Re: sometimes it is not shown after boot

[Ted Gould]

Could you please attach the indicator sound log for when this happens.
~/.cache/upstart/indicator-sound.log

** Changed in: indicator-sound (Ubuntu)
   Status: New => Incomplete

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

Title:
  sometimes it is not shown after boot

Status in indicator-sound package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 15.04 r99 on mako with indicator-sound 12.10.2+15.04.20150205

  
  You boot your phone, then the following happen to the sound-indicator:

  What I expected to happen:
  Normally, the sound-indicator should show you a speaker with the name sound 
and there are tools (mute, loudness) under it.

  What happen instead:
  But sometimes, it shows only a gear and it is named "indicator-sound" and 
there are no tools like mute-switch and loudness-control.

  (I didn't see it in the last 4 releases, but I didn't restart it
  often, so the possibility, to get the bug was not high enough. But as
  far as I remember, it was in < r60, too.)

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

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

[Touch-packages] [Bug 1425362] Re: unity8 crashed with SIGSEGV in QLightDM::GreeterImpl::authenticateWithPam() when logging in

[Treviño]

** Description changed:

  I'm trying to run unity8 in a vivid vmware session (mir works fine here).
  But unity8 crashes when logging in, and it happens again everytime I insert 
my password in the u8 lockscreen.
+ ---
+ The only way to successfully log in unity8 was to add myself to the 
"nopasswdlogin" group. This made the unity8 pam module checks, and thus no 
crash.
  
- ProblemType: Crash
- DistroRelease: Ubuntu 15.04
+ ProblemType: CrashDistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150224-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Feb 24 18:09:32 2015
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  ProcCmdline: unity8
  SegvAnalysis:
-  Segfault happened at: 0x7fb33b34c3a9 <_IO_vfprintf_internal+5561>:   repnz 
scas %es:(%rdi),%al
-  PC (0x7fb33b34c3a9) ok
-  source "%es:(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
-  destination "%al" ok
-  Stack memory exhausted (SP below stack segment)
+  Segfault happened at: 0x7fb33b34c3a9 <_IO_vfprintf_internal+5561>:   repnz 
scas %es:(%rdi),%al
+  PC (0x7fb33b34c3a9) ok
+  source "%es:(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
+  destination "%al" ok
+  Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
- Signal: 11
- SourcePackage: unity8
+ Signal: 11SourcePackage: unity8
  StacktraceTop:
-  _IO_vfprintf_internal (s=s@entry=0x7fb2ea5b69d0, format=, 
format@entry=0x7fb2f7a8f2d3 "%s(%s:%s):", ap=ap@entry=0x7fb2ea5b6b08) at 
vfprintf.c:2039
-  __GI___vasprintf_chk (result_ptr=0x7fb2ea5b6be8, flags=1, 
format=0x7fb2f7a8f2d3 "%s(%s:%s):", args=args@entry=0x7fb2ea5b6b08) at 
vasprintf_chk.c:66
-  __asprintf_chk (result_ptr=, flags=, 
format=) at asprintf_chk.c:32
-  pam_vsyslog () from /lib/x86_64-linux-gnu/libpam.so.0
-  pam_syslog () from /lib/x86_64-linux-gnu/libpam.so.0
+  _IO_vfprintf_internal (s=s@entry=0x7fb2ea5b69d0, format=, 
format@entry=0x7fb2f7a8f2d3 "%s(%s:%s):", ap=ap@entry=0x7fb2ea5b6b08) at 
vfprintf.c:2039
+  __GI___vasprintf_chk (result_ptr=0x7fb2ea5b6be8, flags=1, 
format=0x7fb2f7a8f2d3 "%s(%s:%s):", args=args@entry=0x7fb2ea5b6b08) at 
vasprintf_chk.c:66
+  __asprintf_chk (result_ptr=, flags=, 
format=) at asprintf_chk.c:32
+  pam_vsyslog () from /lib/x86_64-linux-gnu/libpam.so.0
+  pam_syslog () from /lib/x86_64-linux-gnu/libpam.so.0
  Title: unity8 crashed with SIGSEGV in _IO_vfprintf_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

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

Title:
  unity8 crashed with SIGSEGV in
  QLightDM::GreeterImpl::authenticateWithPam() when logging in

Status in unity8 package in Ubuntu:
  New

Bug description:
  I'm trying to run unity8 in a vivid vmware session (mir works fine here).
  But unity8 crashes when logging in, and it happens again everytime I insert 
my password in the u8 lockscreen.
  ---
  The only way to successfully log in unity8 was to add myself to the 
"nopasswdlogin" group. This made the unity8 pam module checks, and thus no 
crash.

  ProblemType: CrashDistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150224-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Feb 24 18:09:32 2015
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7fb33b34c3a9 <_IO_vfprintf_internal+5561>:   repnz 
scas %es:(%rdi),%al
   PC (0x7fb33b34c3a9) ok
   source "%es:(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%al" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11SourcePackage: unity8
  StacktraceTop:
   _IO_vfprintf_internal (s=s@entry=0x7fb2ea5b69d0, format=, 
format@entry=0x7fb2f7a8f2d3 "%s(%s:%s):", ap=ap@entry=0x7fb2ea5b6b08) at 
vfprintf.c:2039
   __GI___vasprintf_chk (result_ptr=0x7fb2ea5b6be8, flags=1, 
format=0x7fb2f7a8f2d3 "%s(%s:%s):", args=args@entry=0x7fb2ea5b6b08) at 
vasprintf_chk.c:66
   __asprintf_chk (re

[Touch-packages] [Bug 1382857] Re: No way to swipe away sound notification

[Ted Gould]

** Package changed: indicator-sound (Ubuntu) => unity-notifications
(Ubuntu)

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

Title:
  No way to swipe away sound notification

Status in unity-notifications package in Ubuntu:
  Confirmed

Bug description:
  Using RTM 5 on Mako, there is no way to swipe away the new sound
  notification overlay. While it doesn't last very long, this is
  annoying. Touching it, or swiping it away, would be a preferable way
  to dismiss this.

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

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

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

[Ted Gould]

** Changed in: indicator-sound (Ubuntu)
   Importance: Medium => Low

** Summary changed:

- indicator-sound-service crashed with signal 5 in main()
+ indicator-sound-service can't connect to DBus under gnome-shell

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

Title:
  indicator-sound-service can't connect to DBus under gnome-shell

Status in indicator-sound package in Ubuntu:
  Confirmed

Bug description:
  Got that crash on opening a gnome-shell session after a cold boot with
  systemd-sysv

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150219.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0
  Uname: Linux 3.19.0-5-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  Date: Sat Feb 21 05:11:24 2015
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service
  Signal: 5
  SourcePackage: indicator-sound
  StacktraceTop: main ()
  Title: indicator-sound-service crashed with signal 5 in main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1424966] Re: /usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service:5:reset_timer:unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond:g_main_dispatch

[Launchpad Bug Tracker]

** Branch linked: lp:~charlesk/indicator-datetime/lp-1424966-fix-
ecanceled-errno-rtm-14.09

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

Title:
  /usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-
  
service:5:reset_timer:unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate

Status in the base for Ubuntu mobile products:
  New
Status in indicator-datetime package in Ubuntu:
  In Progress

Bug description:
  It happened randomly but several time on RTM/krillin. According to
  errors.u.c it started with 13.10.0+15.04.20150213.1-0ubuntu1 on vivid
  and 13.10.0+15.04.20150213~rtm-0ubuntu1 on RTM.

[ Charles Kerr ]
* change the WallClock to detect time changes from
  TFD_TIMER_CANCEL_ON_SET, e.g. when ntp<-->manual is toggled

  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
indicator-datetime.  This problem was most recently seen with version 
13.10.0+15.04.20150213.1-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/3b8aefe51ab8eae0b64a89605ae01d5433da3000 
contains more details.

  current build number: 242
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-02-23 08:07:23
  version version: 242
  version ubuntu: 20150223
  version device: 20150216-fe747ac
  version custom: 20150216-561-29-186

  Trace:
  
https://errors.ubuntu.com/bucket/?id=/usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service%3A5%3Areset_timer%3Aunity%3A%3Aindicator%3A%3Adatetime%3A%3ALiveClock%3A%3AImpl%3A%3Aon_timerfd_cond%3Ag_main_dispatch%3Ag_main_context_dispatch%3Ag_main_context_iterate

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

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

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

[Ted Gould]

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

** This bug has been marked a duplicate of bug 1425024
   indicator-sound-service can't get DBus in greeter session

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

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

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  sorry, no more information, because this come up from the system-
  crash-notifier, sorry for this

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150219.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-14.15-generic 3.18.7
  Uname: Linux 3.18.0-14-generic i686
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  Date: Sun Feb 22 20:30:01 2015
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service
  InstallationDate: Installed on 2015-01-18 (35 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723)
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: indicator-sound
  StacktraceTop: main ()
  Title: indicator-sound-service crashed with signal 5 in main()
  UpgradeStatus: Upgraded to vivid on 2015-02-01 (21 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1425379] [NEW] touch browser crashes when copying text in landscape mode

[Michael]

Public bug reported:

copy text works fine in portrait, crashes in landscape..

to reproduce exactly, was looking up how to sync my google calendar on
https://help.ubuntu.com/community/SyncEvolution

tried to copy one of the text boxes containing terminal commands -
crashes every time in landscape mode

---

1 - OS version 15.04 r111 (has been occurring over several updates though)
1a- installed on nexus 4 via multirom

2 - webbrowser-app version 0.23+15.04.20150217.1-0ubuntu1

3 - i expected to get the selected text copied to the clipboard so i
could paste it into the terminal

4 - browser shut down and i was returned to the apps launcher

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  touch browser crashes when copying text in landscape mode

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  copy text works fine in portrait, crashes in landscape..

  to reproduce exactly, was looking up how to sync my google calendar on
  https://help.ubuntu.com/community/SyncEvolution

  tried to copy one of the text boxes containing terminal commands -
  crashes every time in landscape mode

  ---

  1 - OS version 15.04 r111 (has been occurring over several updates though)
  1a- installed on nexus 4 via multirom

  2 - webbrowser-app version 0.23+15.04.20150217.1-0ubuntu1

  3 - i expected to get the selected text copied to the clipboard so i
  could paste it into the terminal

  4 - browser shut down and i was returned to the apps launcher

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

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

[Touch-packages] [Bug 1425199] Re: when trying to launch unity8-in-lxc sesssion, indicator-sound-service crashed with signal 5 in main()

[Ted Gould]

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

I think this crash is probably the same as the one in bug 1425024. I
assigned that one to unity-greeter, I think that's probably where
indicator-sound is getting started before DBus?

** This bug has been marked a duplicate of bug 1425024
   indicator-sound-service can't get DBus in greeter session

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

Title:
  when trying to launch unity8-in-lxc sesssion, indicator-sound-service
  crashed with signal 5 in main()

Status in indicator-sound package in Ubuntu:
  New
Status in unity8-lxc package in Ubuntu:
  Triaged

Bug description:
  When trying to launch the "Unity 8 in LXC" session from the official
  packages, lightdm freezes after logging in with the user's data.

  After launching into the regular (Xubuntu, in this case) session, a
  crash of indicator-sound is reported.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150219.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
  Uname: Linux 3.18.0-12-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Tue Feb 24 18:21:32 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  InstallationDate: Installed on 2015-02-05 (18 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150205)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: indicator-sound
  StacktraceTop: main ()
  Title: indicator-sound-service crashed with signal 5 in main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1405650] Re: no sound and input pépriphériques are not detected, the computer crashes unexpectedly.

[Launchpad Bug Tracker]

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

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

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

Title:
  no sound and input pépriphériques are not detected, the computer
  crashes unexpectedly.

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
   input pépriphériques are not detected, the computer crashes
  unexpectedly.  Can not connect via wifi

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: pulseaudio 1:4.0-0ubuntu22
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  NonfreeKernelModules: psmouse ahci libahci i915 tg3 wmi video i2c_algo_bit 
drm_kms_helper sdhci_pci drm sdhci ptp pps_core
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  Date: Thu Dec 25 15:44:24 2014
  InstallationDate: Installed on 2014-08-31 (116 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to utopic on 2014-10-28 (58 days ago)
  dmi.bios.date: 03/11/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EG50_HC_CR
  dmi.board.vendor: Packard Bell
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.15
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.15:bd03/11/2013:svnPackardBell:pnEasyNoteTE11HC:pvrV2.15:rvnPackardBell:rnEG50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.15:
  dmi.product.name: EasyNote TE11HC
  dmi.product.version: V2.15
  dmi.sys.vendor: Packard Bell

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

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

[Touch-packages] [Bug 1425024] Re: indicator-sound-service can't get DBus in greeter session

[Ted Gould]

Reassigning to unity-greeter, I think it's pretty valid for indicator-
sound to crash if it can't get DBus…

** Summary changed:

- indicator-sound-service crashed with signal 5 in main()
+ indicator-sound-service can't get DBus in greeter session

** Package changed: indicator-sound (Ubuntu) => unity-greeter (Ubuntu)

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

Title:
  indicator-sound-service can't get DBus in greeter session

Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  Crashed in the greeter (lightdm).

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150219.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Tue Feb 24 21:50:39 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  InstallationDate: Installed on 2015-01-31 (24 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_AU:en
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: indicator-sound
  StacktraceTop: main ()
  Title: indicator-sound-service crashed with signal 5 in main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1425297] Re: Sometimes indicator-datetime is not available in the UI after a reboot (vivid/mako 110)

[Ted Gould]

For a data point, I've seen this a couple times before the timerfd stuff
landed. So I'm pretty sure that isn't the culprit.

I've not been able to recreate it reliably. But with U8 in Vivid, I've
been rebooting a lot :-)

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => High

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

** Summary changed:

- Sometimes indicator-datetime is not available in the UI after a reboot 
(vivid/mako 110)
+ Sometimes indicator-datetime is not available in the UI after a reboot 
(vivid/mako)

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

Title:
  Sometimes indicator-datetime is not available in the UI after a reboot
  (vivid/mako)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  current build number: 110
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-02-24 04:34:45
  version version: 110
  version ubuntu: 20150224
  version device: 20150210
  version custom: 20150224

  See the attached picture.

  The only log entry I have for it:
  Indicator-Datetime-Message: static gboolean 
unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond(gint, 
GIOCondition, gpointer) triggered at 2015-02-24 20:24:48.605449 by GIOCondition 
1, read -1 bytes, found 0 interrupts

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

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

[Touch-packages] [Bug 1425362] Re: unity8 crashed with SIGSEGV in QLightDM::GreeterImpl::authenticateWithPam() when logging in

[Treviño]

Full stacktrace, including u8 symbols (missing in the automatic
retrace).

Unity seems fine actually, but crash happens when calling
pam_authenticate where the pamHandle is something like:

{authtok = 0x7fb3 , 
  caller_is = 3944807584, pam_conversation = 0x, oldauthtok = 0x0, 
prompt = 0x0, 
  service_name = 0x0, user = 0x0, rhost = 0x0, 
  ruser = 0x , tty = 
0x0, 
  xdisplay = 0x0, authtok_type = 0x0, data = 0x0, env = 0x0, fail_delay = {set 
= PAM_FALSE, 
delay = 0, begin = 0, delay_fn_ptr = 0x0}, xauth = {namelen = 0, 
name = 0x , 
datalen = 36901392, 
data = 0x0001 }, 
  handlers = {module = 0x232d370, modules_allocated = 36855568, modules_used = 
0, 
handlers_loaded = 36898784, conf = {authenticate = 0x0, setcred = 0x21, 
  acct_mgmt = 0x6d6f6e675f6d6170, open_session = 0x6e697279656b5f65, 
  close_session = 0x7f006f730067, chauthtok = 0x21}, other = {
  authenticate = 0x6c61776b5f6d6170, setcred = 0x6f730074656c, acct_mgmt = 
0x0, 
  open_session = 0xd1, close_session = 0x7fb3, chauthtok = 0x0}}, 
former = {
choice = -1, depth = 0, impression = 0, status = 0, substates = 0x0, 
fail_user = 0, 
want_user = 0, prompt = 0x0, update = PAM_FALSE}, 
  mod_name = 0x , 
mod_argc = 0, 
  mod_argv = 0x0, choice = 0, audit_state = 0}

Not sure if it might be a threading issue

** Summary changed:

- unity8 crashed with SIGSEGV in _IO_vfprintf_internal() - When logging in
+ unity8 crashed with SIGSEGV in QLightDM::GreeterImpl::authenticateWithPam() 
when logging in

** Attachment added: "Stacktrace with symbols"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1425362/+attachment/4326859/+files/Stacktrace

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

Title:
  unity8 crashed with SIGSEGV in
  QLightDM::GreeterImpl::authenticateWithPam() when logging in

Status in unity8 package in Ubuntu:
  New

Bug description:
  I'm trying to run unity8 in a vivid vmware session (mir works fine here).
  But unity8 crashes when logging in, and it happens again everytime I insert 
my password in the u8 lockscreen.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150224-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Feb 24 18:09:32 2015
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7fb33b34c3a9 <_IO_vfprintf_internal+5561>:   repnz 
scas %es:(%rdi),%al
   PC (0x7fb33b34c3a9) ok
   source "%es:(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%al" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   _IO_vfprintf_internal (s=s@entry=0x7fb2ea5b69d0, format=, 
format@entry=0x7fb2f7a8f2d3 "%s(%s:%s):", ap=ap@entry=0x7fb2ea5b6b08) at 
vfprintf.c:2039
   __GI___vasprintf_chk (result_ptr=0x7fb2ea5b6be8, flags=1, 
format=0x7fb2f7a8f2d3 "%s(%s:%s):", args=args@entry=0x7fb2ea5b6b08) at 
vasprintf_chk.c:66
   __asprintf_chk (result_ptr=, flags=, 
format=) at asprintf_chk.c:32
   pam_vsyslog () from /lib/x86_64-linux-gnu/libpam.so.0
   pam_syslog () from /lib/x86_64-linux-gnu/libpam.so.0
  Title: unity8 crashed with SIGSEGV in _IO_vfprintf_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1219912] Re: [FFe] Allow excluding specific files or directories when building a click package

[Scott Kitterman]

Ack.  Approved.

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

Title:
  [FFe] Allow excluding specific files or directories when building a
  click package

Status in click package in Ubuntu:
  Triaged

Bug description:
  We are past feature freeze, so this requires a FFe:
  - this feature changes click build to have a "--ignore" options
  - we want this as its useful for the SDK/ubuntu-touch and als for the appstore
  - low risk, small branch
  - the full diff is the MP below, but its mostly shuffling existing code 
around, the small amount of real code is line 185 and the following tests :)

  "click build" should have an option for specifying files or folders
  that should not be included in the package, either using command-fline
  flags ( -I.bzr) or in the manifest.json, or both.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: click 0.4.0
  ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic i686
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: i386
  Date: Mon Sep  2 12:38:46 2013
  InstallationDate: Installed on 2012-06-04 (454 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MarkForUpload: True
  SourcePackage: click
  UpgradeStatus: Upgraded to saucy on 2013-06-08 (85 days ago)

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

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

[Touch-packages] [Bug 1423342] Re: SDCard fake needed for filemanager autopilot tests

[Christopher Lee]

(Following on from previous comment that I posted too early :-))
Autopilot is the wrong place to have a fake SDCard, the proper place is
either in the project itself, the toolkit or another (new?) project.

** Changed in: autopilot
   Status: New => Invalid

** Changed in: autopilot
   Status: Invalid => Won't Fix

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

Title:
  SDCard fake needed for filemanager autopilot tests

Status in Autopilot:
  Won't Fix
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Faking SDCard is needed for writing autopilot tests for filemanager
  app: https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1406988.

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

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

[Touch-packages] [Bug 1105232] Re: Save file dialog causes programme crash when renaming a folder

[Bug Watch Updater]

** Changed in: nautilus
   Status: New => Invalid

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

Title:
  Save file dialog causes programme crash when renaming a folder

Status in Nautilus:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  Here is how to reproduce this bug:
  * Open gedit
  * Type something and click Save as...
  * Then click Create New Folder button
  * Type the name of the folder and click on it in the dialogue, then go back 
to the folder above it
  * Now open nautilus, navigate to the folder and rename it

  Gedit should now crash. This is repeatable on my system. I am guessing
  the same bug can also be found in other programmes that use the
  nautilus interface for saving files (have not tested this, but it
  seems more than likely). The Create New Folder step above can be
  skipped, simply renaming an already existing folder.

  This problem is made worse because the Save file dialogue does not
  include the option for renaming files there without launching a
  separate nautilus instance.

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

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

[Touch-packages] [Bug 1425362] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1425362/+attachment/4326849/+files/ThreadStacktrace.txt

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1425362/+attachment/4326835/+files/CoreDump.gz

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

** Tags removed: need-amd64-retrace

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

Title:
  unity8 crashed with SIGSEGV in _IO_vfprintf_internal() - When logging
  in

Status in unity8 package in Ubuntu:
  New

Bug description:
  I'm trying to run unity8 in a vivid vmware session (mir works fine here).
  But unity8 crashes when logging in, and it happens again everytime I insert 
my password in the u8 lockscreen.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150224-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Feb 24 18:09:32 2015
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7fb33b34c3a9 <_IO_vfprintf_internal+5561>:   repnz 
scas %es:(%rdi),%al
   PC (0x7fb33b34c3a9) ok
   source "%es:(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%al" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   _IO_vfprintf_internal (s=s@entry=0x7fb2ea5b69d0, format=, 
format@entry=0x7fb2f7a8f2d3 "%s(%s:%s):", ap=ap@entry=0x7fb2ea5b6b08) at 
vfprintf.c:2039
   __GI___vasprintf_chk (result_ptr=0x7fb2ea5b6be8, flags=1, 
format=0x7fb2f7a8f2d3 "%s(%s:%s):", args=args@entry=0x7fb2ea5b6b08) at 
vasprintf_chk.c:66
   __asprintf_chk (result_ptr=, flags=, 
format=) at asprintf_chk.c:32
   pam_vsyslog () from /lib/x86_64-linux-gnu/libpam.so.0
   pam_syslog () from /lib/x86_64-linux-gnu/libpam.so.0
  Title: unity8 crashed with SIGSEGV in _IO_vfprintf_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1425362] Stacktrace.txt

[Apport retracing service]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1425362/+attachment/4326847/+files/Stacktrace.txt

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

Title:
  unity8 crashed with SIGSEGV in _IO_vfprintf_internal() - When logging
  in

Status in unity8 package in Ubuntu:
  New

Bug description:
  I'm trying to run unity8 in a vivid vmware session (mir works fine here).
  But unity8 crashes when logging in, and it happens again everytime I insert 
my password in the u8 lockscreen.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150224-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Feb 24 18:09:32 2015
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7fb33b34c3a9 <_IO_vfprintf_internal+5561>:   repnz 
scas %es:(%rdi),%al
   PC (0x7fb33b34c3a9) ok
   source "%es:(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%al" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   _IO_vfprintf_internal (s=s@entry=0x7fb2ea5b69d0, format=, 
format@entry=0x7fb2f7a8f2d3 "%s(%s:%s):", ap=ap@entry=0x7fb2ea5b6b08) at 
vfprintf.c:2039
   __GI___vasprintf_chk (result_ptr=0x7fb2ea5b6be8, flags=1, 
format=0x7fb2f7a8f2d3 "%s(%s:%s):", args=args@entry=0x7fb2ea5b6b08) at 
vasprintf_chk.c:66
   __asprintf_chk (result_ptr=, flags=, 
format=) at asprintf_chk.c:32
   pam_vsyslog () from /lib/x86_64-linux-gnu/libpam.so.0
   pam_syslog () from /lib/x86_64-linux-gnu/libpam.so.0
  Title: unity8 crashed with SIGSEGV in _IO_vfprintf_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1425362] StacktraceSource.txt

[Apport retracing service]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1425362/+attachment/4326848/+files/StacktraceSource.txt

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

Title:
  unity8 crashed with SIGSEGV in _IO_vfprintf_internal() - When logging
  in

Status in unity8 package in Ubuntu:
  New

Bug description:
  I'm trying to run unity8 in a vivid vmware session (mir works fine here).
  But unity8 crashes when logging in, and it happens again everytime I insert 
my password in the u8 lockscreen.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150224-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Feb 24 18:09:32 2015
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7fb33b34c3a9 <_IO_vfprintf_internal+5561>:   repnz 
scas %es:(%rdi),%al
   PC (0x7fb33b34c3a9) ok
   source "%es:(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%al" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   _IO_vfprintf_internal (s=s@entry=0x7fb2ea5b69d0, format=, 
format@entry=0x7fb2f7a8f2d3 "%s(%s:%s):", ap=ap@entry=0x7fb2ea5b6b08) at 
vfprintf.c:2039
   __GI___vasprintf_chk (result_ptr=0x7fb2ea5b6be8, flags=1, 
format=0x7fb2f7a8f2d3 "%s(%s:%s):", args=args@entry=0x7fb2ea5b6b08) at 
vasprintf_chk.c:66
   __asprintf_chk (result_ptr=, flags=, 
format=) at asprintf_chk.c:32
   pam_vsyslog () from /lib/x86_64-linux-gnu/libpam.so.0
   pam_syslog () from /lib/x86_64-linux-gnu/libpam.so.0
  Title: unity8 crashed with SIGSEGV in _IO_vfprintf_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1425362]

[Apport retracing service]

StacktraceTop:
 _IO_vfprintf_internal (s=s@entry=0x7fb2ea5b69d0, format=, 
format@entry=0x7fb2f7a8f2d3 "%s(%s:%s):", ap=ap@entry=0x7fb2ea5b6b08) at 
vfprintf.c:2039
 __GI___vasprintf_chk (result_ptr=0x7fb2ea5b6be8, flags=1, 
format=0x7fb2f7a8f2d3 "%s(%s:%s):", args=args@entry=0x7fb2ea5b6b08) at 
vasprintf_chk.c:66
 __asprintf_chk (result_ptr=result_ptr@entry=0x7fb2ea5b6be8, 
flags=flags@entry=1, format=format@entry=0x7fb2f7a8f2d3 "%s(%s:%s):") at 
asprintf_chk.c:32
 asprintf (__fmt=0x7fb2f7a8f2d3 "%s(%s:%s):", __ptr=0x7fb2ea5b6be8) at 
/usr/include/x86_64-linux-gnu/bits/stdio2.h:178
 pam_vsyslog (pamh=0x2330710, priority=3, fmt=0x7fb2f7a8dc38 "application 
failed to re-exec stack [%d:%d]", args=args@entry=0x7fb2ea5b6c40) at 
pam_syslog.c:81

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

Title:
  unity8 crashed with SIGSEGV in _IO_vfprintf_internal() - When logging
  in

Status in unity8 package in Ubuntu:
  New

Bug description:
  I'm trying to run unity8 in a vivid vmware session (mir works fine here).
  But unity8 crashes when logging in, and it happens again everytime I insert 
my password in the u8 lockscreen.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150224-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Feb 24 18:09:32 2015
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7fb33b34c3a9 <_IO_vfprintf_internal+5561>:   repnz 
scas %es:(%rdi),%al
   PC (0x7fb33b34c3a9) ok
   source "%es:(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%al" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   _IO_vfprintf_internal (s=s@entry=0x7fb2ea5b69d0, format=, 
format@entry=0x7fb2f7a8f2d3 "%s(%s:%s):", ap=ap@entry=0x7fb2ea5b6b08) at 
vfprintf.c:2039
   __GI___vasprintf_chk (result_ptr=0x7fb2ea5b6be8, flags=1, 
format=0x7fb2f7a8f2d3 "%s(%s:%s):", args=args@entry=0x7fb2ea5b6b08) at 
vasprintf_chk.c:66
   __asprintf_chk (result_ptr=, flags=, 
format=) at asprintf_chk.c:32
   pam_vsyslog () from /lib/x86_64-linux-gnu/libpam.so.0
   pam_syslog () from /lib/x86_64-linux-gnu/libpam.so.0
  Title: unity8 crashed with SIGSEGV in _IO_vfprintf_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1423342] Re: SDCard fake needed for filemanager autopilot tests

[Christopher Lee]

Where else is it expected that this helper would be used? I imagine that 
initially it'll be only used in the filemanager app?
If so it should go there and if it's needed in other tests than the toolkit is 
a better place than autopilot for it.

Thoughts?

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

Title:
  SDCard fake needed for filemanager autopilot tests

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

Bug description:
  Faking SDCard is needed for writing autopilot tests for filemanager
  app: https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1406988.

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

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

[Touch-packages] [Bug 1425362] [NEW] unity8 crashed with SIGSEGV in _IO_vfprintf_internal() - When logging in

[Treviño]

Public bug reported:

I'm trying to run unity8 in a vivid vmware session (mir works fine here).
But unity8 crashes when logging in, and it happens again everytime I insert my 
password in the u8 lockscreen.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: unity8 8.02+15.04.20150224-0ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Tue Feb 24 18:09:32 2015
ExecutablePath: /usr/bin/unity8
InstallationDate: Installed on 2015-02-25 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
ProcCmdline: unity8
SegvAnalysis:
 Segfault happened at: 0x7fb33b34c3a9 <_IO_vfprintf_internal+5561>: repnz 
scas %es:(%rdi),%al
 PC (0x7fb33b34c3a9) ok
 source "%es:(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
 destination "%al" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity8
StacktraceTop:
 _IO_vfprintf_internal (s=s@entry=0x7fb2ea5b69d0, format=, 
format@entry=0x7fb2f7a8f2d3 "%s(%s:%s):", ap=ap@entry=0x7fb2ea5b6b08) at 
vfprintf.c:2039
 __GI___vasprintf_chk (result_ptr=0x7fb2ea5b6be8, flags=1, 
format=0x7fb2f7a8f2d3 "%s(%s:%s):", args=args@entry=0x7fb2ea5b6b08) at 
vasprintf_chk.c:66
 __asprintf_chk (result_ptr=, flags=, 
format=) at asprintf_chk.c:32
 pam_vsyslog () from /lib/x86_64-linux-gnu/libpam.so.0
 pam_syslog () from /lib/x86_64-linux-gnu/libpam.so.0
Title: unity8 crashed with SIGSEGV in _IO_vfprintf_internal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash need-amd64-retrace vivid

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

Title:
  unity8 crashed with SIGSEGV in _IO_vfprintf_internal() - When logging
  in

Status in unity8 package in Ubuntu:
  New

Bug description:
  I'm trying to run unity8 in a vivid vmware session (mir works fine here).
  But unity8 crashes when logging in, and it happens again everytime I insert 
my password in the u8 lockscreen.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150224-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Feb 24 18:09:32 2015
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7fb33b34c3a9 <_IO_vfprintf_internal+5561>:   repnz 
scas %es:(%rdi),%al
   PC (0x7fb33b34c3a9) ok
   source "%es:(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%al" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   _IO_vfprintf_internal (s=s@entry=0x7fb2ea5b69d0, format=, 
format@entry=0x7fb2f7a8f2d3 "%s(%s:%s):", ap=ap@entry=0x7fb2ea5b6b08) at 
vfprintf.c:2039
   __GI___vasprintf_chk (result_ptr=0x7fb2ea5b6be8, flags=1, 
format=0x7fb2f7a8f2d3 "%s(%s:%s):", args=args@entry=0x7fb2ea5b6b08) at 
vasprintf_chk.c:66
   __asprintf_chk (result_ptr=, flags=, 
format=) at asprintf_chk.c:32
   pam_vsyslog () from /lib/x86_64-linux-gnu/libpam.so.0
   pam_syslog () from /lib/x86_64-linux-gnu/libpam.so.0
  Title: unity8 crashed with SIGSEGV in _IO_vfprintf_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1332555] Re: xprop WM_CLASS returns not foudn for unity launcher when clicking on unity launcher

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1332555

** Tags added: iso-testing

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

Title:
  xprop WM_CLASS returns not foudn for unity launcher when clicking on
  unity launcher

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

Bug description:
  To reproduce open a terminal and type xprop WM_CLASS and then click on
  the launcher that is on the left of your screen it will return not
  found.

  I expected it to return unity-launcher or something similar. Instead
  the command returned not found.

  
  unity:
Installed: 7.2.1+14.04.20140513-0ubuntu2
Candidate: 7.2.1+14.04.20140513-0ubuntu2
Version table:
   *** 7.2.1+14.04.20140513-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   7.2.0+14.04.20140423-0ubuntu1.2 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   7.2.0+14.04.20140416-0ubuntu1 0
   

 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.1+14.04.20140513-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Jun 20 06:50:40 2014
  InstallationDate: Installed on 2014-05-26 (25 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1425221] Re: [OptiPlex 9020, Realtek ALC280, Green Line Out, Rear] tinny sound

[Raymond]

as your desktop have line out, headphone and internal speaker but only
two playback volume control

you need yo use latest alsa driver and pulseaudio which use LO+Speaker
Playback volume instead of PCM Playback volume


Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
  Control: name="PCM Playback Volume", index=0, device=0
ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Device: name="ALC280 Analog", type="Audio", device=0
  Amp-Out caps: ofs=0x57, nsteps=0x57, stepsize=0x02, mute=0
  Amp-Out vals:  [0x24 0x24]
  Converter: stream=8, channel=0
  PCM:
rates [0x560]: 44100 48000 96000 192000
bits [0xe]: 16 20 24
formats [0x1]: PCM
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
  Control: name="Headphone Playback Volume", index=0, device=0
ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Amp-Out caps: ofs=0x57, nsteps=0x57, stepsize=0x02, mute=0
  Amp-Out vals:  [0x24 0x24]
  Converter: stream=8, channel=0
  PCM:
rates [0x560]: 44100 48000 96000 192000
bits [0xe]: 16 20 24
formats [0x1]: PCM
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0

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

Title:
  [OptiPlex 9020, Realtek ALC280, Green Line Out, Rear] tinny sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound equalization is normal when using jack in front of computer, but
  is "tinny" (i.e., low/nonexistent bass and midtones) when using rear
  output jack  with simple two channel headphones.

  Jack sense is working correctly because the internal speaker cuts out
  when a cable is plugged into the rear jack (or front jack, for that
  matter).

  Note Dell's website says this computer has a Realtek ALC3220, as
  opposed to the ALC280 which is detected by linux.  This is a clean
  install of 14.04, so I unfortunately I can't boot into Windows to
  observe its behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 24 12:31:49 2015
  InstallationDate: Installed on 2015-01-30 (25 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 successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [OptiPlex 9020, Realtek ALC280, Green Line Out, Rear] Background noise 
or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/20/2014:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1390959] Re: Two mouse pointers with external display.

[Launchpad Bug Tracker]

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

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

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

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

Title:
  Two mouse pointers with external display.

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when switching the cursor between displays the mouse pointer
  will duplicate itself on the main display but the second cursor will
  appear below the primary cursor and rotated 90° counter-clockwise (the
  external display is also rotated 90° counter-clockwise).

  This bug will go away on reboot, or sometimes by itself.

  Attached is a photo of the effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  .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: None
  CurrentDesktop: GNOME
  Date: Sun Nov  9 13:54:42 2014
  DistUpgraded: 2014-11-03 14:27:23,822 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Zenbook Prime UX31A [1043:1517]
  InstallationDate: Installed on 2013-10-23 (382 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: ASUSTeK COMPUTER INC. UX31A
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=ba953fd4-0d7d-4e73-89e0-5a4a44f9b188 ro quiet splash pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to utopic on 2014-11-03 (5 days ago)
  dmi.bios.date: 06/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX31A.219
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX31A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX31A.219:bd06/14/2013:svnASUSTeKCOMPUTERINC.:pnUX31A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX31A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX31A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  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.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: Sun Nov  9 09:53:00 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16455 
   vendor DEL
  xserver.version: 2:1.16.0-1ubuntu1

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

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

[Touch-packages] [Bug 1425307] Re: Exception when running phablet-screenshot (mako/vivid 110)

[Daniel van Vugt]

I think Mir's at fault here.

It's unreasonable to expect a client or shell to know it's being
screencast and avoid setting swap interval. Mir should handle (or
ignore) this transparently.

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

** Summary changed:

- Exception when running phablet-screenshot (mako/vivid 110)
+ Exception when running phablet-screenshot (mako/vivid 110) 
[std::exception::what: Attempt to set swap interval on screencast is invalid]

** Tags added: screencast

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

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

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

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

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

Title:
  Exception when running phablet-screenshot (mako/vivid 110)
  [std::exception::what: Attempt to set swap interval on screencast is
  invalid]

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Triaged

Bug description:
  current build number: 110
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-02-24 22:35:35
  version version: 110
  version ubuntu: 20150224
  version device: 20150210
  version custom: 20150224

  rsalveti@evasys:~$ phablet-screenshot /tmp/foo.png
  I: Dumping fb0 ...
  [1424817826.846470] Loader: Loading modules from: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/
  [1424817826.847569] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/mesa.so
  [1424817826.848393] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/android.so
  [1424817826.849583] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/dummy.so
  [1424817826.944654]  mircommon: Caught exception at Mir/EGL driver 
boundary (in setSwapInterval): 
/build/buildd/mir-0.11.0+15.04.20150209.1/src/client/buffer_stream.cpp(283): 
Throw in function virtual void 
mir::client::BufferStream::request_and_wait_for_configure(MirSurfaceAttrib, int)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_error
  std::exception::what: Attempt to set swap interval on screencast is invalid

  3004 KB/s (3932160 bytes in 1.278s)
  I: Done

  phablet-tools - 1.1+15.04.20150218-0ubuntu1

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

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

[Touch-packages] [Bug 1390474] Re: "Volume element PCM has 6 channels. That's too much!" - PA doesn't support elements with more than two channels

[Bug Watch Updater]

** Changed in: pulseaudio
   Status: Incomplete => Fix Released

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

Title:
  "Volume element PCM has 6 channels. That's too much!" - PA doesn't
  support elements with more than two channels

Status in PulseAudio sound server:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the 
error "Volume element PCM has 6 channels. That's too much! I can't handle 
that!"  and the card fails to show up in Sound Settings.
  Everything is fine with 24/48 mode (2 channels).

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

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

[Touch-packages] [Bug 1423359] Re: taking screenshots with mirscreencast fails if locale is not C.

[Daniel van Vugt]

** Summary changed:

- taking screenshots with mirscreencast fails
+ taking screenshots with mirscreencast fails if locale is not C.

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

Title:
  taking screenshots with mirscreencast fails if locale is not C.

Status in Mir:
  New
Status in autopkgtest package in Ubuntu:
  Fix Released
Status in mir package in Ubuntu:
  Triaged

Bug description:
  From autopilot we see this when there is a failed test.

  21:40:25.138 ERROR testcase:387 - Taking screenshot failed: Command
  '['mirscreencast', '-m', '/run/mir_socket', '-n', '1', '-f', '/tmp/ap-
  screenshot-data-1424295625.rgba']' returned non-zero exit status 1

  I tried setting the LC_ALL env var to C, and it works.

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

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

[Touch-packages] [Bug 1390474]

[David Henningsson]

Ok. So the "high channel count" part is fixed with 6.0.

The "non interleaved access" was never a problem (emulated by alsa plug
layer).

Tsched=0 workarounds...should in general be fixed in ALSA rather than
PulseAudio. Raymond's patch is probably correct but I'm not qualified to
review it. Raymond, could you turn the patch into a proper commit (git
commit -s ) and then send it upstream on the alsa-devel mailinglist
(using git send-email or git format-patch)? Thanks.

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

Title:
  "Volume element PCM has 6 channels. That's too much!" - PA doesn't
  support elements with more than two channels

Status in PulseAudio sound server:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the 
error "Volume element PCM has 6 channels. That's too much! I can't handle 
that!"  and the card fails to show up in Sound Settings.
  Everything is fine with 24/48 mode (2 channels).

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

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

[Touch-packages] [Bug 1394454] Re: Documentation for service_type in OnlineAccountClient is misleading

[Michi Henning]

I was looking at
https://developer.ubuntu.com/api/scopes/sdk-14.10/index/

See the "Example .service file" section.

The page you linked is indeed wrong, thanks for pointing that out. I'll
reassign the bug.

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

Title:
  Documentation for service_type in OnlineAccountClient is misleading

Status in Ubuntu App Developer site:
  New

Bug description:
  The documentation for the service_type argument in the
  OnlineAccountClient is, 'The type of service (E.g. "sharing").'  But
  in examples of .service files, the service type is specified using the
  a reverse-domain-name-esque string.  The documentation should be
  updated to reflect this usage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/developer-ubuntu-com/+bug/1394454/+subscriptions

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

[Touch-packages] [Bug 1394454] Re: Documentation for service_type in OnlineAccountClient is misleading

[Michi Henning]

Please see comment #1; the correct example can be found in the unity-
scopes-api doc.

** Package changed: unity-scopes-api (Ubuntu) => developer-ubuntu-com

** Changed in: developer-ubuntu-com
   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/1394454

Title:
  Documentation for service_type in OnlineAccountClient is misleading

Status in Ubuntu App Developer site:
  New

Bug description:
  The documentation for the service_type argument in the
  OnlineAccountClient is, 'The type of service (E.g. "sharing").'  But
  in examples of .service files, the service type is specified using the
  a reverse-domain-name-esque string.  The documentation should be
  updated to reflect this usage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/developer-ubuntu-com/+bug/1394454/+subscriptions

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

[Touch-packages] [Bug 1425334] [NEW] Crackling when increasing default-sample-rate

[Nazar Mokrynskyi]

Public bug reported:

I'm on Ubuntu 15.04 x64.
Just bought Creative Sound Blaster Omni Surround 5.1 USB sound card which is 
capable of 24bit 96kHz.
I'm editing sudo gedit /etc/pulse/daemon.conf changing:
default-sample-format = s24le
default-sample-rate = 96000

When I put first line everything is fine, while I'm putting second, even
192000 - I'm getting random crackling all the time when something is
playing.

Without second line everything works fine.
I've tried many tricks found in Internet, different kernels (stock 3.18, 
manually compiled 3.19.0 and 4.0-rc1) - the same result everywhere.

** Affects: pulseaudio (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/1425334

Title:
  Crackling when increasing default-sample-rate

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm on Ubuntu 15.04 x64.
  Just bought Creative Sound Blaster Omni Surround 5.1 USB sound card which is 
capable of 24bit 96kHz.
  I'm editing sudo gedit /etc/pulse/daemon.conf changing:
  default-sample-format = s24le
  default-sample-rate = 96000

  When I put first line everything is fine, while I'm putting second,
  even 192000 - I'm getting random crackling all the time when something
  is playing.

  Without second line everything works fine.
  I've tried many tricks found in Internet, different kernels (stock 3.18, 
manually compiled 3.19.0 and 4.0-rc1) - the same result everywhere.

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

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

[Touch-packages] [Bug 1388556] Re: screen resolution and graphical problems

[Christopher M. Penalver]

synalp, thank you for reporting this and helping make Ubuntu better. As
per
http://h20564.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=5428369&swLangOid=8&swEnvOid=4158
an update to your computer's buggy and outdated BIOS is available
(1.30). If you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything?

If it doesn't, could you please both specify what happened, and provide the 
output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful. As well, you don't
have to create a new bug report.

Once the BIOS is updated, and the information above is provided, then
please mark this report Status New.

Thank you for your understanding.

** Tags added: bios-outdated-1.30

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

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

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

Title:
  screen resolution and graphical problems

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes after restarting the computer in starts the screen with a really 
low resolution 640x480 (it is no possible to work on it), ant it is not 
possibile to change it at all.  Sometimes it has a higher resolution 
((1024x768) but then the screen is blinking ... sometimes everything is ok.
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Nov  2 13:35:45 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK208GLM [Quadro K610M] [10de:12b9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:197b]
  InstallationDate: Installed on 2014-09-09 (53 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP ZBook 15
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic 
root=UUID=3cfd59fc-c4db-45f9-9a8d-bc25cf0ebcee ro vesafb.invalid=1 
plymouth:debug nopat drm.debug=0xe
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L70 Ver. 01.07
  dmi.board.name: 1909
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 94.50
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL70Ver.01.07:bd01/10/2014:svnHewlett-Packard:pnHPZBook15:pvrA3009CD10002:rvnHewlett-Packard:rn1909:rvrKBCVersion94.50:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ZBook 15
  dmi.product.version: A3009CD10002
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sun Nov  2 13:34:46 2014
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.1

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

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

[Touch-packages] [Bug 1388512] Re: system running on low graphic mode

[Christopher M. Penalver]

tushar, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal as it will automatically gather
and attach updated debug information to this report:

apport-collect -p xorg 1388512

Please ensure you have xdiagnose installed, and that you click the Yes
button for attaching additional debugging information.

As well, given the information from the prior release is already
available, testing a release prior to the development one would not be
helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

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

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

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

Title:
  system running on low graphic mode

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Reinstalled lightdm and installed gdm but problem still persist.no
  space problem.even installed Ubuntu desktop but it is of no use.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Nov  2 11:42:04 2014
  DistUpgraded: 2014-10-28 20:59:15,991 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] 
(rev 18) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:2ab4]
  InstallationDate: Installed on 2014-03-18 (228 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  LightdmGreeterLog: Failed to open PAM session: Error in service module
  LightdmGreeterLogOld: Failed to open PAM session: Error in service module
  MachineType: Hewlett-Packard CQ3540IX
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic 
root=UUID=e6d34c60-c872-49e2-a1fe-33a65bdb06f1 ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-10-28 (4 days ago)
  dmi.bios.date: 11/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.07
  dmi.board.name: 2AB4
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: INA110WD99
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.07:bd11/29/2010:svnHewlett-Packard:pnCQ3540IX:pvrxxx0204GR0:rvnMSI:rn2AB4:rvr2.0:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: CQ3540IX
  dmi.product.version: xxx0204GR0
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58+git20141006.00847fa4-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.4.0~git20141023.065256df-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.4.0~git20141023.065256df-0ubuntu0ricotz~trusty
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.916+git20141016.6b98f162-0ubuntu0sarvatt~trusty
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11+git20140904.3cd4c849-0ubuntu0sarvatt~trusty
  xserver.bootTime: Sun Nov  2 11:33:41 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputNOVATEK USB Keyboard KEYBOARD, id 8
   inputNOVATEK USB Keyboard KEYBOARD, id 9
   inputUSB Optical MouseMOUSE, id 10
  xserver.errors:
   intel: Failed to load module "dri3" (module does not exist, 0)
   intel: Failed to load module "present" (module does not exist, 0)
   Server terminated successfully (0). Closing log file.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.1

To manage notifications about this

[Touch-packages] [Bug 1388412] Re: Not all the screen displays

[Christopher M. Penalver]

Ayeshah, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal as it will automatically gather
and attach updated debug information to this report:

apport-collect -p xorg 1388412

Please ensure you have xdiagnose installed, and that you click the Yes
button for attaching additional debugging information.

As well, given the information from the prior release is already
available, testing a release prior to the development one would not be
helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

** Tags added: latest-bios-a11

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

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

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

Title:
  Not all the screen displays

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I recently upgraded to Trusty Tahr 14.04 and feel I may have a slight
  issue with the screen size.  Such an example would be like dialogue
  boxes or messages from certain softwares or programs don't completely
  display.

  It would be nice to use System Testing to maybe work out how to deal
  with the screen size but I'm unable to proceed past the start page -
  where it requires you to press continue, but I'm guessing the button
  is at the far bottom of the dialogue box which I cannot press and
  there's no way to scroll or tab to the button.

  Any answers or help is much appreciated!

  I'm hoping I've reported this minor issue to the right place.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic i686
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Nov  1 17:17:41 2014
  DistUpgraded: 2014-10-05 18:00:02,335 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation System Controller Hub (SCH Poulsbo) Graphics Controller 
[8086:8108] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:02c6]
  InstallationDate: Installed on 2014-03-10 (236 days ago)
  InstallationMedia: Linux Lite 1.0.8 32-bit - Release i386
  MachineType: Dell Inc. Inspiron 1010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=685f5713-3db4-4ff0-b97a-0dca69b9e08a ro splash quiet vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-10-05 (27 days ago)
  dmi.bios.date: 10/27/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: **
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.asset.tag: **
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd10/27/2009:svnDellInc.:pnInspiron1010:pvrA11:rvnDellInc.:rn**:rvrA11:cvnDellInc.:ct8:cvrA11:
  dmi.product.name: Inspiron 1010
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Nov  1 16:58:23 2014
  xserver.configfile: default
  xserver.devices:
   inputVideo BusKEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputIntegrated WebcamKEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputETPS/2 Elantech Touchpad TOUCHPAD, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.1

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

-- 
Mailing list: https://launchpad

[Touch-packages] [Bug 1388336] Re: Browser is disabled easily

[Christopher M. Penalver]

Will, thank you for reporting this and helping make Ubuntu better. As
per http://support.toshiba.com/support/modelHome?freeText=127480 an
update to your computer's buggy and outdated BIOS is available (1.80).
If you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything?

If it doesn't, could you please both specify what happened, and provide the 
output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful. As well, you don't
have to create a new bug report.

Once the BIOS is updated, and the information above is provided, then
please mark this report Status New.

Thank you for your understanding.

** Tags added: bios-outdated-1.80

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

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

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

Title:
  Browser is disabled easily

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My wifi is fine I cant do anything.  Chrome doesnt start sometimes it
  pops up and crashes.  Firefox does the same.  Can you recommend a good
  browser for free

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  .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
  Date: Fri Oct 31 22:57:14 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   asic0x, 1.0.1, 3.16.0-23-generic, x86_64: installed
   asic0x, 1.0.1, 3.16.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8280 / R3 Series] 
[1002:9836] (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fa26]
  InstallationDate: Installed on 2014-09-14 (48 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: TOSHIBA Satellite C55D-A
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=77cfc2d2-00ca-4b21-b2ae-9ef137c88a8d ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.60:bd11/15/2013:svnTOSHIBA:pnSatelliteC55D-A:pvrPSCFWU-03H02X:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C55D-A
  dmi.product.version: PSCFWU-03H02X
  dmi.sys.vendor: TOSHIBA
  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.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: Fri Oct 31 22:02:28 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1394454] Re: Documentation for service_type in OnlineAccountClient is misleading

[Robert Schroll]

I have no idea what I was looking at three months ago that had the
error.  But a quick googling turns up this page,
https://developer.ubuntu.com/en/apps/platform/guides/online-accounts-
developer-guide/, which has the example service file:


  ubuntu.com.developer.me.MyClick_MyApp
  facebook


I can't find the example you're pointing out, but I'm probably looking
in the wrong places.

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

Title:
  Documentation for service_type in OnlineAccountClient is misleading

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  The documentation for the service_type argument in the
  OnlineAccountClient is, 'The type of service (E.g. "sharing").'  But
  in examples of .service files, the service type is specified using the
  a reverse-domain-name-esque string.  The documentation should be
  updated to reflect this usage.

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

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

[Touch-packages] [Bug 1338068] Re: Wrong color depth on Radeon HD 6770

[Christopher M. Penalver]

Michael P, does using fglrx provide a WORKAROUND to this issue?

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

Title:
  Wrong color depth on Radeon HD 6770

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Graphics card is  Radeon HD 6770. X.Org drivers. Clean install, video
  works but color depth is < 24bpp. I tried adding DefaultDepth
  parameter on xorg.conf. Secondary card is integrated on the
  motherboard (Intel E3-1200 chipset). Delivers 24bpp right away, no
  tinkering required.

  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.351
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroRelease: Ubuntu 15.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: Foxconn International, Inc. Device [105b:0d78]
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 6770] 
[1002:68ba] (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2142]
  LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent 
file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet 
splash -- BOOT_IMAGE=/casper/vmlinuz.efi
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Tags:  vivid ubuntu single-occurrence reproducible compiz-0.9
  Uname: Linux 3.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/13/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C12F1P01
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61MXV/H61MXV-LE/H67MXV
  dmi.board.vendor: Foxconn
  dmi.board.version: FAB 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC12F1P01:bd03/13/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnFoxconn:rnH61MXV/H61MXV-LE/H67MXV:rvrFAB1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.12.1+15.04.20150213-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0~rc1-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0~rc1-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu4
  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.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Tue Feb 24 18:41:50 2015
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.2.901-1ubuntu4

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

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

[Touch-packages] [Bug 1421060] Re: Boost log uses all inodes if file system is full

[Michi Henning]

The linked branch implements a work-around for the bug in boost log.
This means we won't need a patched boost log lib.

Also, I don't think system image is affected because the RTM release
does not use boost log. (We added that functionality later.)

Pat, I think this means that Canonical System Image is not affected. If
you agree could you remove it from the bug?

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

Title:
  Boost log uses all inodes if file system is full

Status in the base for Ubuntu mobile products:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  boost::log, if file rotation happens while the file system is full,
  creates hundreds of empty log files per log directory, eventually
  consuming all available inodes.

  But reported here: https://svn.boost.org/trac/boost/ticket/11016

  We need to track this.

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

-- 
Mailing list: https://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 1391149] Re: greeter not reacting to swipes

[Ricardo Salveti]

On Tue, Feb 24, 2015 at 10:42 AM, Daniel d'Andrada
 wrote:
> I can reproduce it with ubuntu-touch/ubuntu-rtm/14.09-proposed using
> (roughly) the steps from comment #9 but not with vivid-proposed.
>
> Maybe that's due to different versions of Qt as I cannot spot any
> relevant difference in that part of unity8 code (greeter and launcher).
>
> Since we're about to move Vivid to stable, I guess it's not worth the
> effort of finding and backporting whatever fixed it?

"about" here is still unclear, we might still have 1-2 months of RTM.

Pat should be able to answer if high enough for a backport/fix.

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

Title:
  greeter not reacting to swipes

Status in the base for Ubuntu mobile products:
  New
Status in unity8 package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  i had this a few times over the weekend with images 150-153, suddenly
  the greeter does not react to right/left swipes on the wallpaper to
  reveal the PIN unlock dialog ... swiping in the launcher from the left
  makes the greeter go away and reveals the PIN unlock dialog then.

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

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

[Touch-packages] [Bug 1332824] Re: [Samsung XE700T1C-A01FR] Smartpad not properly recognised

[Christopher M. Penalver]

u0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Jun 21 15:48:56 2014
  xserver.configfile: default
  xserver.errors:
   Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 116
   vendor ACR
  xserver.version: 2:1.15.1-0ubuntu2
  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.351
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroRelease: Ubuntu 15.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd Device [144d:c0e1]
  LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 700T1C
  Package: xorg 1:7.7+7ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Tags:  vivid ubuntu reproducible compiz-0.9
  Uname: Linux 3.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P10AAT.050.140215.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: XE700T1C-A01FR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP10AAT.050.140215.dg:bd02/15/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn700T1C:pvrP10AAT:rvnSAMSUNGELECTRONICSCO.,LTD.:rnXE700T1C-A01FR:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct8:cvrN/A:
  dmi.product.name: 700T1C
  dmi.product.version: P10AAT
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.1+15.04.20150213-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0~rc1-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0~rc1-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu4
  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.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Tue Feb 24 20:25:35 2015
  xserver.configfile: default
  xserver.errors:
   Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12637
   vendor AUO
  xserver.version: 2:1.16.2.901-1ubuntu4

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

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

[Touch-packages] [Bug 1421060] Re: Boost log uses all inodes if file system is full

[Michi Henning]

** Branch linked: lp:~michihenning/unity-scopes-api/fix-inode-leak

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

Title:
  Boost log uses all inodes if file system is full

Status in the base for Ubuntu mobile products:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  boost::log, if file rotation happens while the file system is full,
  creates hundreds of empty log files per log directory, eventually
  consuming all available inodes.

  But reported here: https://svn.boost.org/trac/boost/ticket/11016

  We need to track this.

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

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

[Touch-packages] [Bug 1421060] Re: Boost log uses all inodes if file system is full

[Michi Henning]

** Changed in: unity-scopes-api (Ubuntu)
 Assignee: (unassigned) => Michi Henning (michihenning)

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

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

Title:
  Boost log uses all inodes if file system is full

Status in the base for Ubuntu mobile products:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  boost::log, if file rotation happens while the file system is full,
  creates hundreds of empty log files per log directory, eventually
  consuming all available inodes.

  But reported here: https://svn.boost.org/trac/boost/ticket/11016

  We need to track this.

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

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

[Touch-packages] [Bug 1332824] Re: Samsung XE700T1C Keyboard and touchpad not properly recognised

[Christopher M. Penalver]

ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P10AAT.050.140215.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: XE700T1C-A01FR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP10AAT.050.140215.dg:bd02/15/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn700T1C:pvrP10AAT:rvnSAMSUNGELECTRONICSCO.,LTD.:rnXE700T1C-A01FR:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct8:cvrN/A:
  dmi.product.name: 700T1C
  dmi.product.version: P10AAT
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Jun 21 15:48:56 2014
  xserver.configfile: default
  xserver.errors:
-  Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
-  Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
-  Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
+  Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
+  Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
+  Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id 116 
-  vendor ACR
+  product id 116
+  vendor ACR
  xserver.version: 2:1.15.1-0ubuntu2
- --- 
+ ---
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.351
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroRelease: Ubuntu 15.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: Samsung Electronics Co Ltd Device [144d:c0e1]
+  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Samsung Electronics Co Ltd Device [144d:c0e1]
  LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 700T1C
  Package: xorg 1:7.7+7ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Tags:  vivid ubuntu reproducible compiz-0.9
  Uname: Linux 3.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P10AAT.050.140215.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: XE700T1C-A01FR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP10AAT.050.140215.dg:bd02/15/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn700T1C:pvrP10AAT:rvnSAMSUNGELECTRONICSCO.,LTD.:rnXE700T1C-A01FR:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct8:cvrN/A:
  dmi.product.name: 700T1C
  dmi.product.version: P10AAT
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.1+15.04.2015021

[Touch-packages] [Bug 1338068] Re: Wrong color depth on Radeon HD 6770

[Christopher M. Penalver]

** Description changed:

- Potentially a duplicate of Bug #1322413 (but different architecture and
- video card)
- 
  Graphics card is  Radeon HD 6770. X.Org drivers. Clean install, video
  works but color depth is < 24bpp. I tried adding DefaultDepth parameter
- on xorg.conf.
+ on xorg.conf. Secondary card is integrated on the motherboard (Intel
+ E3-1200 chipset). Delivers 24bpp right away, no  tinkering required.
  
- Secondary card is integrated on the motherboard (Intel E3-1200 chipset).
- Delivers 24bpp right away, no  tinkering required.
+ ---
+ .tmp.unity.support.test.0:
  
- Thanks in advance
- 
- Michael
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 14.04
- Package: xorg 1:7.7+1ubuntu8
- ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
- Uname: Linux 3.13.0-30-generic x86_64
- ApportVersion: 2.14.1-0ubuntu3.2
- Architecture: amd64
- CurrentDesktop: XFCE
- Date: Sat Jul  5 17:12:34 2014
- InstallationDate: Installed on 2014-06-04 (30 days ago)
- InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
- SourcePackage: xorg
- Symptom: display
- UpgradeStatus: No upgrade log present (probably fresh install)
- --- 
- ApportVersion: 2.14.1-0ubuntu3.7
- Architecture: amd64
- DistroRelease: Ubuntu 14.04
- InstallationDate: Installed on 2014-06-04 (264 days ago)
- InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
- Package: xorg 1:7.7+1ubuntu8.1
- PackageArchitecture: amd64
- ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
- Tags:  trusty
- Uname: Linux 3.13.0-45-generic x86_64
- UpgradeStatus: No upgrade log present (probably fresh install)
- UserGroups:
-  
- _MarkForUpload: True
- --- 
- ApportVersion: 2.14.1-0ubuntu3.7
- Architecture: amd64
- DistroRelease: Ubuntu 14.04
- InstallationDate: Installed on 2014-06-04 (264 days ago)
- InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
- Package: xorg 1:7.7+1ubuntu8.1
- PackageArchitecture: amd64
- ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
- Tags:  trusty
- Uname: Linux 3.13.0-45-generic x86_64
- UpgradeStatus: No upgrade log present (probably fresh install)
- UserGroups:
-  
- _MarkForUpload: True
- --- 
- .tmp.unity.support.test.0:
-  
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.351
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroRelease: Ubuntu 15.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Subsystem: Foxconn International, Inc. Device [105b:0d78]
-  Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 6770] 
[1002:68ba] (prog-if 00 [VGA controller])
-Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2142]
+  Subsystem: Foxconn International, Inc. Device [105b:0d78]
+  Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 6770] 
[1002:68ba] (prog-if 00 [VGA controller])
+    Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2142]
  LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent 
file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet 
splash -- BOOT_IMAGE=/casper/vmlinuz.efi
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Tags:  vivid ubuntu single-occurrence reproducible compiz-0.9
  Uname: Linux 3.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
-  
+ 
  _MarkForUpload: True
  dmi.bios.date: 03/13/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C12F1P01
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61MXV/H61MXV-LE/H67MXV
  dmi.board.vendor: Foxconn
  dmi.board.version: FAB 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC12F1P01:bd03/13/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnFoxconn:rnH61MXV/H61MXV-LE/H67MXV:rvrFAB1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.12.1+15.04.20150213-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58-2
  ve

[Touch-packages] [Bug 1424696] Re: package libva1 1.3.1-3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libva1/changelog.Debian.gz', which is different from other instances of

[Launchpad Bug Tracker]

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

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

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

Title:
  package libva1 1.3.1-3 failed to install/upgrade: trying to overwrite
  shared '/usr/share/doc/libva1/changelog.Debian.gz', which is different
  from other instances of package libva1:i386

Status in libva package in Ubuntu:
  Confirmed

Bug description:
  I get this error after logging in

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: libva1 1.3.1-3
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  Date: Sun Feb 22 15:29:59 2015
  DuplicateSignature: package:libva1:1.3.1-3:trying to overwrite shared 
'/usr/share/doc/libva1/changelog.Debian.gz', which is different from other 
instances of package libva1:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libva1/changelog.Debian.gz', which is different from other 
instances of package libva1:i386
  InstallationDate: Installed on 2014-09-15 (160 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: libva
  Title: package libva1 1.3.1-3 failed to install/upgrade: trying to overwrite 
shared '/usr/share/doc/libva1/changelog.Debian.gz', which is different from 
other instances of package libva1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1424723] Re: Wrong doc for PreviewHeader widget

[Michi Henning]

Not clear to me whether this is a bug in the scopes API doc, or a bug in
the shell. Saviq, which one do you think?

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

Title:
  Wrong doc for PreviewHeader widget

Status in unity-scopes-api package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Hi,

  in the current doc at
  https://developer.ubuntu.com/api/scopes/sdk-14.10/previewwidgets/#header

  I read:

  ```
  The header widget displays basic infomation about the result.

  List of attributes:

  title A string specifying the title
  subtitle A string specifying the subtitle
  mascot A URI specifying the mascot
  emblem A URI specifying the emblem
  ```

  Unfortunately, that is wrong... Right now PreviewHeader widget
  supports only:

  ```
  /*! This preview widget shows a header
   * The title comes in widgetData["title"]
   * The mascot comes in widgetData["mascot"]
   * The subtitle comes in widgetData["subtitle"]
   * The attributes comes in widgetData["attributes"]
   */
  ```
  From the code: 
http://bazaar.launchpad.net/~unity-team/unity8/trunk/view/1621/qml/Dash/Previews/PreviewHeader.qml

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: libunity-scopes-doc 0.6.14+15.04.20150213-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Feb 23 17:35:17 2015
  Dependencies:
   
  InstallationDate: Installed on 2014-09-18 (157 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140917)
  PackageArchitecture: all
  SourcePackage: unity-scopes-api
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: Upgraded to vivid on 2015-01-23 (31 days ago)

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

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

[Touch-packages] [Bug 1394454] Re: Documentation for service_type in OnlineAccountClient is misleading

[Michi Henning]

Could you be a bit more specific? You are right, the OnlineAccountClient
doc says that the service type is a string such as "sharing". And in the
generated doc, the example for a .service file shows:



sharing
youtube
YouTube

So, that seems all in order. Exactly where are you seeing the .service
example that is wrong?

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

Title:
  Documentation for service_type in OnlineAccountClient is misleading

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  The documentation for the service_type argument in the
  OnlineAccountClient is, 'The type of service (E.g. "sharing").'  But
  in examples of .service files, the service type is specified using the
  a reverse-domain-name-esque string.  The documentation should be
  updated to reflect this usage.

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

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

[Touch-packages] [Bug 1399037] Re: apt-get can not simulate

[Svivi]

Thanks for the advice but the position of the -s option had no effect:
$ LANG="C" apt-get dselect-upgrade -s
E: Command line option 's' [from -s] is not known.

The issue occures with and without sudo.

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

Title:
  apt-get can not simulate

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I just noticed that apt can not simulate in Ubuntu 14.04.1.

  
  Updated:

  sudo apt-get -s dselect-upgrade
  E: Command line option 's' [from -s] is not known.

  sudo apt-get --dry-run dselect-upgrade
  E: Command line option --dry-run is not understood

  sudo apt-get --recon dselect-upgrade
  E: Command line option --recon is not understood

  sudo apt-get --no-act dselect-upgrade
  E: Command line option --no-act is not understood

  sudo apt-get --simulate dselect-upgrade
  E: Command line option --simulate is not understood

  sudo apt-get --just-print dselect-upgrade
  E: Command line option --just-print is not understood

  The issue occures with at least the following versions of apt: 
1.0.1ubuntu2.4.1, 1.0.1ubuntu2.5, 1.0.1ubuntu2.6
  and 1.3.1 version of apt-offline.

  It works fine on Ubuntu 12.04 with:  apt 0.8.16~exp12ubuntu10.22 and
  without apt-offline.

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

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

[Touch-packages] [Bug 1308170] Re: [dash] Need annotations for the "did you mean" results from scopes scope

[Michi Henning]

** No longer affects: unity-scopes-api (Ubuntu)

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

Title:
  [dash] Need annotations for the "did you mean" results from scopes
  scope

Status in Ubuntu UX bugs:
  Fix Committed

Bug description:
  This way, we could offer those results without the user being able to
  ask for a preview (and also they probably will look better than now).

  Thanks!

  Solution
  Annotations won't be available for RTM but we are building cards that link to 
a canned query. You should be able to use those for "did you mean" suggestions, 
once they land.

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

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

[Touch-packages] [Bug 1422578] Re: segfault in QSearchQueryBase test

[Michi Henning]

** Changed in: unity-scopes-api (Ubuntu)
   Status: New => Fix Committed

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

Title:
  segfault in QSearchQueryBase test

Status in unity-scopes-api package in Ubuntu:
  Fix Committed

Bug description:
  Just got this on Jenkins CI for arm:

  The following tests FAILED:
 82 - QSearchQueryBaseAPI (SEGFAULT)

  That's from the output at the end of the console log.

  The actual test run output is:

  test 82
  Start  82: QSearchQueryBaseAPI

  82: Test command: 
/tmp/buildd/unity-scopes-api-0.6.14+15.04.20150213bzr316pkg0vivid102/obj-arm-linux-gnueabihf/test/gtest/scopes/qt/qt-bindings/QSearchQueryBaseAPI_test
  82: Test timeout computed to be: 1500
  82: Running main() from gmock_main.cc
  82: [==] Running 1 test from 1 test case.
  82: [--] Global test environment set-up.
  82: [--] 1 test from TestSetup
  82: [ RUN  ] TestSetup.bindings
  82: SetUp()
  82: Starting qt application
  82: Thread id is: 0xb3a3b320
  82: 
  82: GMOCK WARNING:
  82: Uninteresting mock function call - returning default value.
  82: Function call: event(0x803668)
  82:   Returns: false
  82: Stack trace:
   82/102 Test  #82: QSearchQueryBaseAPI 
.***Exception: SegFault  0.60 sec
  Running main() from gmock_main.cc
  [==] Running 1 test from 1 test case.
  [--] Global test environment set-up.
  [--] 1 test from TestSetup
  [ RUN  ] TestSetup.bindings
  SetUp()
  Starting qt application
  Thread id is: 0xb3a3b320

  GMOCK WARNING:
  Uninteresting mock function call - returning default value.
  Function call: event(0x803668)
Returns: false
  Stack trace:

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

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

[Touch-packages] [Bug 1424723] Re: Wrong doc for PreviewHeader widget

[Michi Henning]

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

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

Title:
  Wrong doc for PreviewHeader widget

Status in unity-scopes-api package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Hi,

  in the current doc at
  https://developer.ubuntu.com/api/scopes/sdk-14.10/previewwidgets/#header

  I read:

  ```
  The header widget displays basic infomation about the result.

  List of attributes:

  title A string specifying the title
  subtitle A string specifying the subtitle
  mascot A URI specifying the mascot
  emblem A URI specifying the emblem
  ```

  Unfortunately, that is wrong... Right now PreviewHeader widget
  supports only:

  ```
  /*! This preview widget shows a header
   * The title comes in widgetData["title"]
   * The mascot comes in widgetData["mascot"]
   * The subtitle comes in widgetData["subtitle"]
   * The attributes comes in widgetData["attributes"]
   */
  ```
  From the code: 
http://bazaar.launchpad.net/~unity-team/unity8/trunk/view/1621/qml/Dash/Previews/PreviewHeader.qml

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: libunity-scopes-doc 0.6.14+15.04.20150213-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Feb 23 17:35:17 2015
  Dependencies:
   
  InstallationDate: Installed on 2014-09-18 (157 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140917)
  PackageArchitecture: all
  SourcePackage: unity-scopes-api
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: Upgraded to vivid on 2015-01-23 (31 days ago)

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

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

[Touch-packages] [Bug 1324142] Re: Support providing fallback images

[Michi Henning]

** Changed in: unity-scopes-api (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Support providing fallback images

Status in Thumbnail generator for all kinds of files:
  New
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity-scopes-shell package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  If the URI for a scope result icon can not be loaded, the scope result
  is not easily visible.

  To counter this, the shell should replace the result image with a
  fallback image if the Image QML component changes to the Error state.
  At a minimum a single standard fallback image would be sufficient, but
  letting the scope pick a custom fallback via the category renderer
  template would be better.

  One reason I'd like to see this is so we can switch the album art
  image provider to stop returning a fallback image.  This has been
  requested by the music-app guys, and seems sensible since we might
  want different fallbacks in different contexts:

  https://code.launchpad.net/~jamesh/thumbnailer/no-fallback-
  albumart/+merge/219460

  It might also be useful for remote scopes using http: URIs for result
  icons.

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

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

[Touch-packages] [Bug 1425307] Re: Exception when running phablet-screenshot (mako/vivid 110)

[Ricardo Salveti]

(gdb) catch throw
Catchpoint 1 (throw)
(gdb) r -m /run/mir_socket -n1 -f /tmp/mir_screencast_768x1280.rgba
Starting program: /usr/bin/mirscreencast -m /run/mir_socket -n1 -f 
/tmp/mir_screencast_768x1280.rgba
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[1424819317.052580] Loader: Loading modules from: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/
[1424819317.055296] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/mesa.so
[1424819317.067687] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/android.so
[1424819317.181522] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/dummy.so
[New Thread 0xb63fb440 (LWP 5734)]
Catchpoint 1 (exception thrown), __cxxabiv1::__cxa_throw (obj=0x4a258, 
tinfo=0xb6fc56c4 
 >>, 
dest=0xb6f97921 

 >::~clone_impl()>) at ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:63
63  ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc: No such file or 
directory.
(gdb) bt full
#0  __cxxabiv1::__cxa_throw (obj=0x4a258, tinfo=0xb6fc56c4 
 >>, 
dest=0xb6f97921 

 >::~clone_impl()>) at ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:63
globals = 
#1  0xb6f98228 in 
boost::throw_exception
 > (e=...) at /usr/include/boost/throw_exception.hpp:70
No locals.
#2  0xb6f982ce in boost::exception_detail::throw_exception_ 
(x=..., 
current_function=0xb6fadef4 
 "virtual void 
mir::client::BufferStream::request_and_wait_for_configure(MirSurfaceAttrib, 
int)", 
file=0xb6fadfe4 
"/build/buildd/mir-0.11.0+15.04.20150209.1/src/client/buffer_stream.cpp", 
line=line@entry=283) at /usr/include/boost/throw_exception.hpp:87
No locals.
#3  0xb6f97660 in mir::client::BufferStream::request_and_wait_for_configure 
(this=, attrib=mir_surface_attrib_swapinterval, value=1) at 
/build/buildd/mir-0.11.0+15.04.20150209.1/src/client/buffer_stream.cpp:283
lock = {_M_device = 0xb5a00ac0, _M_owns = true}
__PRETTY_FUNCTION__ = "virtual void 
mir::client::BufferStream::request_and_wait_for_configure(MirSurfaceAttrib, 
int)"
setting = 
result = 
#4  0xb6485690 in mir::graphics::android::MirNativeWindow::setSwapInterval 
(this=, interval=) at 
/build/buildd/mir-0.11.0+15.04.20150209.1/src/common/graphics/android/mir_native_window.cpp:158
__FUNCTION__ = "setSwapInterval"
#5  0xb68be7f6 in ?? ()
No symbol table info available.
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 mir in Ubuntu.
https://bugs.launchpad.net/bugs/1425307

Title:
  Exception when running phablet-screenshot (mako/vivid 110)

Status in mir package in Ubuntu:
  New

Bug description:
  current build number: 110
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-02-24 22:35:35
  version version: 110
  version ubuntu: 20150224
  version device: 20150210
  version custom: 20150224

  rsalveti@evasys:~$ phablet-screenshot /tmp/foo.png
  I: Dumping fb0 ...
  [1424817826.846470] Loader: Loading modules from: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/
  [1424817826.847569] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/mesa.so
  [1424817826.848393] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/android.so
  [1424817826.849583] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/dummy.so
  [1424817826.944654]  mircommon: Caught exception at Mir/EGL driver 
boundary (in setSwapInterval): 
/build/buildd/mir-0.11.0+15.04.20150209.1/src/client/buffer_stream.cpp(283): 
Throw in function virtual void 
mir::client::BufferStream::request_and_wait_for_configure(MirSurfaceAttrib, int)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_error
  std::exception::what: Attempt to set swap interval on screencast is invalid

  3004 KB/s (3932160 bytes in 1.278s)
  I: Done

  phablet-tools - 1.1+15.04.20150218-0ubuntu1

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

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

[Touch-packages] [Bug 1249777] Re: libsss-sudo generated nsswitch.conf leads to error messages upon sudo invocation

[pdf]

Well, darn, I seem to have screwed up the status for the sudo package,
and now Launchpad won't let me change it back.

** No longer affects: sudo (Ubuntu)

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

Title:
  libsss-sudo generated nsswitch.conf leads to error messages upon sudo
  invocation

Status in sssd package in Ubuntu:
  Confirmed
Status in sudo package in Fedora:
  Unknown

Bug description:
  Hello,

  the postinst script for libsss-sudo adds the following line to
  /etc/nsswitch.conf:

  sudoers:files sss

  On my LDAP+krb5 setup, this leads to the following error message when
  either LDAP or local users invoke sudo:

  Nov  9 17:34:41 charon sudo:   oliver : problem with defaults entries
  ; TTY=pts/0 ; PWD=/etc ;

  The sudo invocation succeeds nonetheless, so this is mainly an
  annoying cosmetic issue, since a mail is sent to root everytime
  someone runs sudo.

  Running a debug trace on sudo shows the following:

  Nov  9 17:34:41 sudo[3297] <- update_defaults @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/defaults.c:528 := true
  Nov  9 17:34:41 sudo[3297] <- sudo_file_setdefs @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/parse.c:146 := 0
  Nov  9 17:34:41 sudo[3297] -> sudo_sss_open @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/sssd.c:243
  Nov  9 17:34:41 sudo[3297] <- sudo_sss_open @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/sssd.c:298 := 0
  Nov  9 17:34:41 sudo[3297] -> sudo_sss_parse @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/sssd.c:319
  Nov  9 17:34:41 sudo[3297] <- sudo_sss_parse @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/sssd.c:320 := 0
  Nov  9 17:34:41 sudo[3297] -> sudo_sss_setdefs @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/sssd.c:331
  Nov  9 17:34:41 sudo[3297] Looking for cn=defaults
  Nov  9 17:34:41 sudo[3297] handle->fn_send_recv_defaults: != 0, 
sss_error=32570
  Nov  9 17:34:41 sudo[3297] <- sudo_sss_setdefs @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/sssd.c:343 := -1
  Nov  9 17:34:41 sudo[3297] -> log_error @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/logging.c:473
  Nov  9 17:34:41 sudo[3297] -> vlog_error @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/logging.c:421
  Nov  9 17:34:41 sudo[3297] -> set_perms @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/set_perms.c:116
  Nov  9 17:34:41 sudo[3297] set_perms: PERM_ROOT: uid: [0, 0, 0] -> [0, 0, 0]
  Nov  9 17:34:41 sudo[3297] -> sudo_grlist_addref @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/pwutil.c:770
  Nov  9 17:34:41 sudo[3297] <- sudo_grlist_addref @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/pwutil.c:772
  Nov  9 17:34:41 sudo[3297] <- set_perms @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/set_perms.c:350 := true
  Nov  9 17:34:41 sudo[3297] -> new_logline @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/logging.c:746
  Nov  9 17:34:41 sudo[3297] <- new_logline @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/logging.c:867 := problem with 
defaults entries ; TTY=pts/0 ; PWD=/etc ; 
  Nov  9 17:34:41 sudo[3297] -> send_mail @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/logging.c:524
  Nov  9 17:34:41 sudo[3297] -> do_syslog @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/logging.c:138

  I have found a similar report in Redhat's Bugzilla, but I'm not
  entirely sure if it's the same problem. There are slight differences
  in the debug trace: https://bugzilla.redhat.com/show_bug.cgi?id=879633

  Removing the "sss" statement from the sudoers line in nsswitch.conf
  works around the problem.

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

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

[Touch-packages] [Bug 1425307] Re: Exception when running phablet-screenshot (mako/vivid 110)

[Ricardo Salveti]

Seems it's not a fatal issue though, as the png was extracted correctly.

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

Title:
  Exception when running phablet-screenshot (mako/vivid 110)

Status in mir package in Ubuntu:
  New

Bug description:
  current build number: 110
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-02-24 22:35:35
  version version: 110
  version ubuntu: 20150224
  version device: 20150210
  version custom: 20150224

  rsalveti@evasys:~$ phablet-screenshot /tmp/foo.png
  I: Dumping fb0 ...
  [1424817826.846470] Loader: Loading modules from: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/
  [1424817826.847569] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/mesa.so
  [1424817826.848393] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/android.so
  [1424817826.849583] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/dummy.so
  [1424817826.944654]  mircommon: Caught exception at Mir/EGL driver 
boundary (in setSwapInterval): 
/build/buildd/mir-0.11.0+15.04.20150209.1/src/client/buffer_stream.cpp(283): 
Throw in function virtual void 
mir::client::BufferStream::request_and_wait_for_configure(MirSurfaceAttrib, int)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_error
  std::exception::what: Attempt to set swap interval on screencast is invalid

  3004 KB/s (3932160 bytes in 1.278s)
  I: Done

  phablet-tools - 1.1+15.04.20150218-0ubuntu1

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

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

[Touch-packages] [Bug 1425307] [NEW] Exception when running phablet-screenshot (mako/vivid 110)

[Ricardo Salveti]

Public bug reported:

current build number: 110
device name: mako
channel: ubuntu-touch/vivid-proposed
last update: 2015-02-24 22:35:35
version version: 110
version ubuntu: 20150224
version device: 20150210
version custom: 20150224

rsalveti@evasys:~$ phablet-screenshot /tmp/foo.png
I: Dumping fb0 ...
[1424817826.846470] Loader: Loading modules from: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/
[1424817826.847569] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/mesa.so
[1424817826.848393] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/android.so
[1424817826.849583] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/dummy.so
[1424817826.944654]  mircommon: Caught exception at Mir/EGL driver 
boundary (in setSwapInterval): 
/build/buildd/mir-0.11.0+15.04.20150209.1/src/client/buffer_stream.cpp(283): 
Throw in function virtual void 
mir::client::BufferStream::request_and_wait_for_configure(MirSurfaceAttrib, int)
Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_error
std::exception::what: Attempt to set swap interval on screencast is invalid

3004 KB/s (3932160 bytes in 1.278s)
I: Done

phablet-tools - 1.1+15.04.20150218-0ubuntu1

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

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

Title:
  Exception when running phablet-screenshot (mako/vivid 110)

Status in mir package in Ubuntu:
  New

Bug description:
  current build number: 110
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-02-24 22:35:35
  version version: 110
  version ubuntu: 20150224
  version device: 20150210
  version custom: 20150224

  rsalveti@evasys:~$ phablet-screenshot /tmp/foo.png
  I: Dumping fb0 ...
  [1424817826.846470] Loader: Loading modules from: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/
  [1424817826.847569] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/mesa.so
  [1424817826.848393] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/android.so
  [1424817826.849583] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/dummy.so
  [1424817826.944654]  mircommon: Caught exception at Mir/EGL driver 
boundary (in setSwapInterval): 
/build/buildd/mir-0.11.0+15.04.20150209.1/src/client/buffer_stream.cpp(283): 
Throw in function virtual void 
mir::client::BufferStream::request_and_wait_for_configure(MirSurfaceAttrib, int)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_error
  std::exception::what: Attempt to set swap interval on screencast is invalid

  3004 KB/s (3932160 bytes in 1.278s)
  I: Done

  phablet-tools - 1.1+15.04.20150218-0ubuntu1

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

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

[Touch-packages] [Bug 1408106] Re: attach_disconnected not sufficient for overlayfs

[Jamie Strandboge]

** Description changed:

  With the following use of overlayfs, we get a disconnected path:
  
  $ cat ./profile
  #include 
  profile foo {
    #include 
  
    capability sys_admin,
    capability sys_chroot,
    mount,
    pivot_root,
  }
  
  $ cat ./overlay.c
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  
  int main(int argc, char* argv[]) {
  int i = 0;
  int len = 0;
  int ret = 0;
  char* options;
  
  if (geteuid())
  unshare(CLONE_NEWUSER);
  unshare(CLONE_NEWNS);
  
  for (i = 1; i < argc; i++) {
  if (i == 1) {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/", argv[i]);
  }
  else {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/mnt") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/mnt", 
argv[i]);
  }
  
  mount("overlayfs", "/mnt", "overlayfs", MS_MGC_VAL, options);
  }
  
  chdir("/mnt");
  pivot_root(".", ".");
  chroot(".");
  
  chdir("/");
  execl("/bin/bash", "/bin/bash", NULL);
  }
  
  $ sudo apparmor_parser -r ./profile && aa-exec -p foo -- ./a.out /tmp
  [255]
  ...
  Dec 12 14:31:38 localhost kernel: [57278.040216] audit: type=1400 
audit(1418387498.613:712): apparmor="DENIED" operation="exec" info="Failed name 
lookup - disconnected path" error=-13 profile="foo" name="/bin/bash" pid=18255 
comm="a.out" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
  
  With the above, the expectation was for the denial to be /mnt/bin/bash. There 
are three ways forward:
- 1. the correct solution is to patch overlayfs to properly track the loopback, 
but this will take a while, may ultimately be unachievable (investigation is 
needed) and is likely non-upstreamable
+ 1. the correct solution is to patch overlayfs to properly track the loopback, 
but this will take a while, may ultimately be unachievable (investigation is 
needed)
  2. we could rely on the fact that overlayfs creates a private unshared 
submount, and provide a way to not mediate the path when that is present, and 
tagged. This would take a bit of time, and might be the preferred method over 1 
longer term
- 3. we could extend attach_disconnected so that we can define the attach root. 
Eg, we can use profile foo (attach_disconnected=/mnt) {} such that '/bin/bash' 
maps to '/mnt/bin/bash'.
- 
- While attach_disconnected should in general be discouraged, this method:
-  * is doable in a short time frame,
-  * is generally useful even when the proper fix is in place
-  * would help lxc in a few cases
-  * would be sufficient for snappy
+ 3. we could extend attach_disconnected so that we can define the attach root. 
Eg, we can use profile foo (attach_disconnected=/mnt) {} such that '/bin/bash' 
maps to '/mnt/bin/bash'. UPDATE: THIS IS NOT VIABLE

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

Title:
  attach_disconnected not sufficient for overlayfs

Status in AppArmor Linux application security framework:
  In Progress
Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With the following use of overlayfs, we get a disconnected path:

  $ cat ./profile
  #include 
  profile foo {
    #include 

    capability sys_admin,
    capability sys_chroot,
    mount,
    pivot_root,
  }

  $ cat ./overlay.c
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(int argc, char* argv[]) {
  int i = 0;
  int len = 0;
  int ret = 0;
  char* options;

  if (geteuid())
  unshare(CLONE_NEWUSER);
  unshare(CLONE_NEWNS);

  for (i = 1; i < argc; i++) {
  if (i == 1) {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/", argv[i]);
  }
  else {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/mnt") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/mnt", 
argv[i]);
  }

  mount("overlayfs", "/mnt", "overlayfs", MS_MGC_VAL, options);
  }

  chdir("/mnt");
  pivot_root(".", ".");
  chroot(".");

  chdir("/");
  execl("/bin/bash", "/bin/bash", NULL);
  }

  $ sudo apparmor_parser -r ./profile && aa-exec -p foo -- ./a.out /tmp
  [255]
  ...
  Dec 12 14:31:38 localhost kernel: [57278.040216] audit: type=1400 
audit(1418387498.613:712): apparmor="DENIED" operation="exec" info="Failed name 
lookup - disconnected path" error=-13 profile="foo" name="/bin/bash" pid=18255 
comm="a.out" req

[Touch-packages] [Bug 1425297] Re: Sometimes indicator-datetime is not available in the UI when rebooting vivid/mako 110

[Ricardo Salveti]

Was also able to reproduce this with krillin.

** Summary changed:

- Sometimes indicator-datetime is not available in the UI when rebooting 
vivid/mako 110
+ Sometimes indicator-datetime is not available in the UI after a reboot 
(vivid/mako 110)

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

Title:
  Sometimes indicator-datetime is not available in the UI after a reboot
  (vivid/mako 110)

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  current build number: 110
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-02-24 04:34:45
  version version: 110
  version ubuntu: 20150224
  version device: 20150210
  version custom: 20150224

  See the attached picture.

  The only log entry I have for it:
  Indicator-Datetime-Message: static gboolean 
unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond(gint, 
GIOCondition, gpointer) triggered at 2015-02-24 20:24:48.605449 by GIOCondition 
1, read -1 bytes, found 0 interrupts

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

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

[Touch-packages] [Bug 1249777] Re: libsss-sudo generated nsswitch.conf leads to error messages upon sudo invocation

[pdf]

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

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

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

Title:
  libsss-sudo generated nsswitch.conf leads to error messages upon sudo
  invocation

Status in sssd package in Ubuntu:
  Confirmed
Status in sudo package in Ubuntu:
  Fix Released
Status in sudo package in Fedora:
  Unknown

Bug description:
  Hello,

  the postinst script for libsss-sudo adds the following line to
  /etc/nsswitch.conf:

  sudoers:files sss

  On my LDAP+krb5 setup, this leads to the following error message when
  either LDAP or local users invoke sudo:

  Nov  9 17:34:41 charon sudo:   oliver : problem with defaults entries
  ; TTY=pts/0 ; PWD=/etc ;

  The sudo invocation succeeds nonetheless, so this is mainly an
  annoying cosmetic issue, since a mail is sent to root everytime
  someone runs sudo.

  Running a debug trace on sudo shows the following:

  Nov  9 17:34:41 sudo[3297] <- update_defaults @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/defaults.c:528 := true
  Nov  9 17:34:41 sudo[3297] <- sudo_file_setdefs @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/parse.c:146 := 0
  Nov  9 17:34:41 sudo[3297] -> sudo_sss_open @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/sssd.c:243
  Nov  9 17:34:41 sudo[3297] <- sudo_sss_open @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/sssd.c:298 := 0
  Nov  9 17:34:41 sudo[3297] -> sudo_sss_parse @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/sssd.c:319
  Nov  9 17:34:41 sudo[3297] <- sudo_sss_parse @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/sssd.c:320 := 0
  Nov  9 17:34:41 sudo[3297] -> sudo_sss_setdefs @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/sssd.c:331
  Nov  9 17:34:41 sudo[3297] Looking for cn=defaults
  Nov  9 17:34:41 sudo[3297] handle->fn_send_recv_defaults: != 0, 
sss_error=32570
  Nov  9 17:34:41 sudo[3297] <- sudo_sss_setdefs @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/sssd.c:343 := -1
  Nov  9 17:34:41 sudo[3297] -> log_error @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/logging.c:473
  Nov  9 17:34:41 sudo[3297] -> vlog_error @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/logging.c:421
  Nov  9 17:34:41 sudo[3297] -> set_perms @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/set_perms.c:116
  Nov  9 17:34:41 sudo[3297] set_perms: PERM_ROOT: uid: [0, 0, 0] -> [0, 0, 0]
  Nov  9 17:34:41 sudo[3297] -> sudo_grlist_addref @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/pwutil.c:770
  Nov  9 17:34:41 sudo[3297] <- sudo_grlist_addref @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/pwutil.c:772
  Nov  9 17:34:41 sudo[3297] <- set_perms @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/set_perms.c:350 := true
  Nov  9 17:34:41 sudo[3297] -> new_logline @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/logging.c:746
  Nov  9 17:34:41 sudo[3297] <- new_logline @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/logging.c:867 := problem with 
defaults entries ; TTY=pts/0 ; PWD=/etc ; 
  Nov  9 17:34:41 sudo[3297] -> send_mail @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/logging.c:524
  Nov  9 17:34:41 sudo[3297] -> do_syslog @ 
/build/buildd/sudo-1.8.6p3/plugins/sudoers/logging.c:138

  I have found a similar report in Redhat's Bugzilla, but I'm not
  entirely sure if it's the same problem. There are slight differences
  in the debug trace: https://bugzilla.redhat.com/show_bug.cgi?id=879633

  Removing the "sss" statement from the sudoers line in nsswitch.conf
  works around the problem.

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

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

[Touch-packages] [Bug 139067] Re: Openning gif file with causes the system freezing

[Launchpad Bug Tracker]

** Branch linked: lp:debian/experimental/gdk-pixbuf

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

Title:
  Openning gif file with causes the system freezing

Status in GTK+ GUI Toolkit:
  Invalid
Status in gdk-pixbuf package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu 7.10
  Eye of gnome 2.19.92
  When I use eog to view this gif file, the whole system is freezing.  Both 
mouse and keyboard  do not response either.

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

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

[Touch-packages] [Bug 1424263] Re: Broken dependencies

[Nick Bagios]

Thank you Infektedpc it is work for me too.

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

Title:
  Broken dependencies

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  I can not install Steam from Steam website because reported package
  has broken dependencies. This bug affect any user that will install
  Ubuntu 14.04.2. Please fix it fast, cause i can not play my games on
  Linux.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgl1-mesa-dri:i386 (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  346.35  Sat Jan 10 21:27:15 
PST 2015
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 21 21:40:49 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 346.35, 3.16.0-30-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ac]
  InstallationDate: Installed on 2015-02-20 (1 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed 
root=UUID=ea315497-1076-4f76-a2da-dc65caca572f ro quiet splash loglevel=0 
vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H87 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd07/09/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Feb 21 17:22:09 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

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

[Touch-packages] [Bug 1425297] [NEW] Sometimes indicator-datetime is not available in the UI after a reboot (vivid/mako 110)

[Ricardo Salveti]

Public bug reported:

current build number: 110
device name: mako
channel: ubuntu-touch/vivid-proposed
last update: 2015-02-24 04:34:45
version version: 110
version ubuntu: 20150224
version device: 20150210
version custom: 20150224

See the attached picture.

The only log entry I have for it:
Indicator-Datetime-Message: static gboolean 
unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond(gint, 
GIOCondition, gpointer) triggered at 2015-02-24 20:24:48.605449 by GIOCondition 
1, read -1 bytes, found 0 interrupts

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

** Attachment added: "missing-indicator-datetime.jpg"
   
https://bugs.launchpad.net/bugs/1425297/+attachment/4326711/+files/missing-indicator-datetime.jpg

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

Title:
  Sometimes indicator-datetime is not available in the UI after a reboot
  (vivid/mako 110)

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  current build number: 110
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-02-24 04:34:45
  version version: 110
  version ubuntu: 20150224
  version device: 20150210
  version custom: 20150224

  See the attached picture.

  The only log entry I have for it:
  Indicator-Datetime-Message: static gboolean 
unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond(gint, 
GIOCondition, gpointer) triggered at 2015-02-24 20:24:48.605449 by GIOCondition 
1, read -1 bytes, found 0 interrupts

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

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

[Touch-packages] [Bug 1425297] Re: Sometimes indicator-datetime is not available in the UI after a reboot (vivid/mako 110)

[Ricardo Salveti]

The process was active and running, just not showing in the UI. After
killing the service it worked fine on the following respawn.

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

Title:
  Sometimes indicator-datetime is not available in the UI after a reboot
  (vivid/mako 110)

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  current build number: 110
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-02-24 04:34:45
  version version: 110
  version ubuntu: 20150224
  version device: 20150210
  version custom: 20150224

  See the attached picture.

  The only log entry I have for it:
  Indicator-Datetime-Message: static gboolean 
unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond(gint, 
GIOCondition, gpointer) triggered at 2015-02-24 20:24:48.605449 by GIOCondition 
1, read -1 bytes, found 0 interrupts

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

-- 
Mailing list: https://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 1424951] [NEW] the setting for PCM db control keeps jumping to max db every boot up

[Luke Yelavich]

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

You are probably experiencing bug #1424195, marking this bug as a
duplicate of that.

 duplicate 1424195


** This bug has been marked a duplicate of bug 1424195
   Config option flat-volumes is set to YES by default

** This bug has been marked a duplicate of bug 1424195
   Config option flat-volumes is set to YES by default

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

Title:
  the setting for PCM db control keeps jumping to max db every boot up

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  the setting for PCM db control keeps jumping to max db every boot up
  until I edit default.pa manually changing:

  "#load-module module-alsa-sink"

  to

  "load-module module-alsa-sink control=PCM"

  Because in other way my Ubuntu 14.04 boots up every boot with pcm
  setting set to max db (100%) which makes my sound distorted.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  successor   5536 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Feb 24 10:07:33 2015
  InstallationDate: Installed on 2015-02-20 (3 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: LakePort
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/22/2006:svn:pn:pvr:rvn:rnLakePort:rvr:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 1403112] Re: There's no way to refund purchases

[Rodney Dawes]

** Changed in: unity-scope-click (Ubuntu)
   Importance: Medium => High

** Summary changed:

- There's no way to refund purchases
+ No user interface for requesting refund of app purchases

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

Title:
  No user interface for requesting refund of app purchases

Status in the base for Ubuntu mobile products:
  New
Status in unity-scope-click package in Ubuntu:
  Triaged

Bug description:
  After a purchase is completed there needs to be a short window of time
  when the user can decide to get a refund, eg: for the cases where the
  purchase happened by mistake.  Something like 15 minutes is customary.

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

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

[Touch-packages] [Bug 1422797] Re: MIR refuses the app to connect

[kevin gunn]

** No longer affects: unity-mir (Ubuntu)

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

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

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

Title:
  MIR refuses the app to connect

Status in Autopilot:
  Incomplete
Status in Mir:
  New
Status in qtmir package in Ubuntu:
  New

Bug description:
  When running several camera-app tests in a sequence, randomly we have the 
application crash.
  Tracing the crash leads to a fatal error in qtubuntu when trying to connect 
to MIR. The stack trace follows below.

  According to elopio this might be because the app has not exited yet from the 
previous tests when running the next one.
  I am attaching the AP log as well.

  #0  0xb62298e6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb6237e5e in raise () from /lib/arm-linux-gnueabihf/libc.so.6
  #2  0xb6238b4e in abort () from /lib/arm-linux-gnueabihf/libc.so.6
  #3  0xb6bfe7d6 in qt_message_fatal (context=..., message=...) at 
global/qlogging.cpp:1340
  #4  QMessageLogger::fatal (this=, 
  msg=0xb3f7a02c "UbuntuClientIntegration: connection to Mir server failed. 
Check that a Mir server is\nrunning, and the correct socket is being used and 
is accessible. The shell may have\nrejected the incoming connectio"...) at 
global/qlogging.cpp:669
  #5  0xb3f67356 in ?? () from 
/usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #6  0xb3f69bc4 in ?? () from 
/usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #7  0xb670620a in loadIntegration (argv=0xbeeed2a4, argc=@0xbeeed12c: 1, 
parameters=..., key=..., loader=) at 
kernel/qplatformintegrationfactory.cpp:64
  #8  QPlatformIntegrationFactory::create (platform=..., paramList=..., 
argc=@0xbeeed12c: 1, argv=argv@entry=0xbeeed2a4, platformPluginPath=...) at 
kernel/qplatformintegrationfactory.cpp:81
  #9  0xb670dc34 in init_platform (argv=0xbeeed2a4, argc=@0xbeeed12c: 1, 
platformThemeName=..., platformPluginPath=..., pluginArgument=...) at 
kernel/qguiapplication.cpp:980
  #10 QGuiApplicationPrivate::createPlatformIntegration (this=) 
at kernel/qguiapplication.cpp:1128
  #11 0xb670e396 in QGuiApplicationPrivate::createEventDispatcher 
(this=) at kernel/qguiapplication.cpp:1143
  #12 0xb6d6df20 in QCoreApplication::init (this=this@entry=0xbeeed130) at 
kernel/qcoreapplication.cpp:734
  #13 0xb6d6dfa6 in QCoreApplication::QCoreApplication (this=0xbeeed130, p=...) 
at kernel/qcoreapplication.cpp:657
  #14 0xb670ee06 in QGuiApplication::QGuiApplication (this=0xbeeed130, 
argc=@0xbeeed12c: 1, argv=0xbeeed2a4, flags=328448) at 
kernel/qguiapplication.cpp:532
  #15 0x00014480 in CameraApplication::CameraApplication(int&, char**) ()
  #16 0x00016c82 in main ()

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

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

[Touch-packages] [Bug 1343970] Re: gst-plugins-good pkg-config file issues

[Marc Mance]

Is this the same bug?  I get same error while configuring gnolin 1.4.0
from git.

configure: using GStreamer Base Plugins in /usr/local/lib/gstreamer-1.0
checking for GST_PLUGINS_GOOD... yes
configure: error: no pluginsdir set in GStreamer Good Plugins pkg-config file
  configure failed

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

Title:
  gst-plugins-good pkg-config file issues

Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released

Bug description:
  Came across a small bug while trying to build the gst-rtsp-server-1.2.3. 
  Using Ubuntu 14.04, and  gst-plugins installed from the official ubuntu 
repositories. 
  While building, it tries to use the gstreamer-plugins-good-1.0.pc pkg-config 
file (which has pluginsdir missing). 
  1. If  libgstreamer-plugins-good1.0-dev_1.2.4-1~ubuntu1_i386.deb is removed 
(which removes the .pc file too), the rtsp-server builds fine. 
  2. Another fix will be to add the pluginsdir in the .pc file (The debian 
package should be modified ). After reading up a bit more, I came across this 
in gst-check.m4 "dnl Will set GST_PLUGINS_GOOD_DIR for use in Makefile.am. Note 
that this will dnl only be set in an uninstalled setup, since -good ships no 
.pc file and in dnl an installed setup all plugins will be found in 
GST_PLUGINS_DIR anyway." Hence there shouldn't be a .pc file for 
gst-plugins-good anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1343970/+subscriptions

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

[Touch-packages] [Bug 1419072] Re: Ubuntu sdk devices tab empty

[Pietro Albini]

After updating the SDK to the latest version, the devices tab is now
showing correctly for me.

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

Title:
  Ubuntu sdk devices tab empty

Status in ubuntu-touch-meta package in Ubuntu:
  Confirmed

Bug description:
  OS: Ubuntu 14.04.1 LTS
  Ubuntu-SDK version: 3.1.1
  Ubuntu SDK shows empty window when I click on Devices tab.

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

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

[Touch-packages] [Bug 1414039] Re: App logging should be off by default

[Ted Gould]

** Package changed: upstart-app-launch (Ubuntu) => ubuntu-app-launch
(Ubuntu)

** Changed in: ubuntu-app-launch (Ubuntu)
   Importance: Undecided => High

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

** Changed in: ubuntu-app-launch (Ubuntu)
 Assignee: (unassigned) => Ted Gould (ted)

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

Title:
  App logging should be off by default

Status in the base for Ubuntu mobile products:
  In Progress
Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  We are creating 100s of MBs in log files which are generally unused on
  production systems

  Propose to turn app logging off by default and add an option under developer 
mode to enable it along with additional logging levels like debug.
  Also, apps and shell should examine their logging to become far less verbose

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

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

[Touch-packages] [Bug 1333215] Re: "Unable to find keyfile for application": clicks installed in current session don't create UAL cache, and UAL does not look for .desktop files in click pkgdir

[Ted Gould]

I don't think this is a UAL bug. I think the click hook should be run on
install which it isn't. I think that it's reasonable for UAL to depend
on its click hook running.

** No longer affects: ubuntu-app-launch

** Changed in: ubuntu-app-launch (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  "Unable to find keyfile for application": clicks installed in current
  session don't create UAL cache, and UAL does not look for .desktop
  files in click pkgdir

Status in click package in Ubuntu:
  New
Status in ubuntu-app-launch package in Ubuntu:
  Invalid

Bug description:
  For testing/autopkgtest I want/need to run click apps and their tests
  in a schroot or container, as the turnaround with real phones and the
  emulator is way too large. But in a container, ubuntu-app-launch fails
  with

  $ ubuntu-app-launch `ubuntu-app-triplet com.ubuntu.calculator`

  ** (process:766): WARNING **: Unable to find keyfile for application 
'com.ubuntu.calculator_calculator_1.3.283'
  init: application-legacy 
(com.ubuntu.calculator_calculator_1.3.283-1403523098604203) pre-start process 
(770) terminated with status 1

  In strace I see that it looks for the .desktop file in the following
  locations:


/home/ubuntu/.cache/ubuntu-app-launch/desktop/com.ubuntu.calculator_calculator_1.3.283.desktop

/home/ubuntu/.local/share/applications/com.ubuntu.calculator_calculator_1.3.283.desktop

/usr/local/share/applications/com.ubuntu.calculator_calculator_1.3.283.desktop
/usr/share/applications/com.ubuntu.calculator_calculator_1.3.283.desktop

  but not in the click dir:

  $ click pkgdir com.ubuntu.calculator
  /opt/click.ubuntu.com/.click/users/@all/com.ubuntu.calculator

  The workaround is to create the symlink manually, then it works:

  $  ln -s `click pkgdir com.ubuntu.calculator`/*.desktop 
.cache/ubuntu-app-launch/desktop/`ubuntu-app-triplet 
com.ubuntu.calculator`.desktop
  $ ubuntu-app-launch `ubuntu-app-triplet com.ubuntu.calculator`

  But that's certainly not something that autopkgtest should do.

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

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

[Touch-packages] [Bug 1362640] Re: Remove qtwebkit from touch image

[Olivier Tilloy]

As of today, com.ubuntu.developer.daker.x-type has been updated to use
Oxide.

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

Title:
  Remove qtwebkit from touch image

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Cordova Ubuntu:
  Fix Released
Status in Web Browser App:
  Triaged
Status in signon-ui package in Ubuntu:
  Triaged
Status in ubuntu-html5-theme package in Ubuntu:
  Triaged
Status in ubuntu-touch-meta package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  The argument to remove this is based on the following:

  The qtwebkit webview is deprecated for our sdk and we will not be supporting 
it long term
  We are supporting an Oxide/Chromium solution for the Ubuntu.Webview
  This was done largely for security reasons
  The qtwebkit package is large and we would like to reduce image and install 
size 
  We want to discourage app devs from using this api any longer, the review 
tools have indicated this for several months

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

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

[Touch-packages] [Bug 1326513] Re: Applications are orphaned when unity8 crashes

[Ted Gould]

We already have a stop on application-end or desktop-end. I think one of
those should be enough if we want to kill all the applications. I'm a
bit surprised they survive Mir dying though. Perhaps libmir-client
should issue a shutdown when it sees the other end die.

** Changed in: ubuntu-app-launch (Ubuntu)
   Status: New => Invalid

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

Title:
  Applications are orphaned when unity8 crashes

Status in Mir:
  Expired
Status in Qt integration with the Mir display server:
  Triaged
Status in ubuntu-app-launch package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  For some reason Unity8 crashed on me. The applications I had open are
  now orphaned. They're still running but you can't get to it as it no
  longer shows up under the recent applications. In addition if I
  attempt to start the app, it fails to run or come back from orphaned
  state, so I have to restart.

  My unity process where Unity8 died an hour or two back.

  lightdm   1871  0.0  0.0   1392   464 ?Ss   10:06   0:00 /bin/sh 
/usr/lib/lightdm/lightdm-greeter-session /usr/bin/unity8-greeter-wrapper 
/usr/bin/unity8-greeter
  lightdm   1875  0.0  0.0   1392   472 ?S10:06   0:00 /bin/sh 
/usr/bin/unity8-greeter-wrapper /usr/bin/unity8-greeter
  lightdm   2362  0.2  5.0 343724 95000 ?Sl   10:06   1:47 
/usr/bin/unity8-greeter
  phablet  22852  0.4  5.6 452692 105852 ?   Ssl  19:03   0:34 unity8

  The application:-

  phablet   8503 10.3  8.6 297792 161652 ?   Ssl  11:33  59:33
  /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene ubuntu-calculator-
  app.qml

  Now when I start calculator it just white-screens.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.87+14.10.20140603.1-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  Date: Wed Jun  4 21:04:34 2014
  InstallationDate: Installed on 2014-06-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140604)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1422486] Re: latest edge tutorial gets stuck with n7 landscape mode

[Daniel d'Andrada]

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

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

Title:
  latest edge tutorial gets stuck with n7 landscape mode

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  If you try the vivid silo 0 on N7, it puts N7 in landscape mode
  unfortunately the new edge tutorial gets stuck on the second step (right edge 
swipe)

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

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

[Touch-packages] [Bug 1332824] LightdmLog.txt

[V. Beau]

SION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct8:cvrN/A:
  dmi.product.name: 700T1C
  dmi.product.version: P10AAT
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Jun 21 15:48:56 2014
  xserver.configfile: default
  xserver.errors:
   Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 116 
   vendor ACR
  xserver.version: 2:1.15.1-0ubuntu2
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.351
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroRelease: Ubuntu 15.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Device [144d:c0e1]
  LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 700T1C
  Package: xorg 1:7.7+7ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Tags:  vivid ubuntu reproducible compiz-0.9
  Uname: Linux 3.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P10AAT.050.140215.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: XE700T1C-A01FR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP10AAT.050.140215.dg:bd02/15/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn700T1C:pvrP10AAT:rvnSAMSUNGELECTRONICSCO.,LTD.:rnXE700T1C-A01FR:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct8:cvrN/A:
  dmi.product.name: 700T1C
  dmi.product.version: P10AAT
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.1+15.04.20150213-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0~rc1-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0~rc1-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu4
  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.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Tue Feb 24 20:25:35 2015
  xserver.configfile: default
  xserver.errors:
   Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12637 
   vendor AUO
  xserver.version: 2:1.16.2.901-1ubuntu4

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

-- 
Mailing list: https://launc

[Touch-packages] [Bug 1332824] Lsusb.txt

[V. Beau]

SION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct8:cvrN/A:
  dmi.product.name: 700T1C
  dmi.product.version: P10AAT
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Jun 21 15:48:56 2014
  xserver.configfile: default
  xserver.errors:
   Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 116 
   vendor ACR
  xserver.version: 2:1.15.1-0ubuntu2
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.351
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroRelease: Ubuntu 15.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Device [144d:c0e1]
  LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 700T1C
  Package: xorg 1:7.7+7ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Tags:  vivid ubuntu reproducible compiz-0.9
  Uname: Linux 3.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P10AAT.050.140215.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: XE700T1C-A01FR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP10AAT.050.140215.dg:bd02/15/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn700T1C:pvrP10AAT:rvnSAMSUNGELECTRONICSCO.,LTD.:rnXE700T1C-A01FR:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct8:cvrN/A:
  dmi.product.name: 700T1C
  dmi.product.version: P10AAT
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.1+15.04.20150213-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0~rc1-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0~rc1-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu4
  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.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Tue Feb 24 20:25:35 2015
  xserver.configfile: default
  xserver.errors:
   Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12637 
   vendor AUO
  xserver.version: 2:1.16.2.901-1ubuntu4

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

-- 
Mailing list: https://launc