[Touch-packages] [Bug 1426399] Re: Sheel freezes for a short time when pressing the Play key on a connected BT keyboard

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/telephony-service

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

Title:
  Sheel freezes for a short time when pressing the Play key on a
  connected BT keyboard

Status in telephony-service package in Ubuntu:
  In Progress

Bug description:
  How to reproduce:

  1) Connect a bluetooth keyboard to your Nexus 4.
  2) Press the Play key on the keyboard.

  What happens:

  Unity8 freezes for some seconds.

  
  phablet@ubuntu-phablet:~$ system-image-cli --info
  current build number: 114
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-02-27 15:25:45
  version version: 114
  version ubuntu: 20150227.1
  version device: 20150210
  version custom: 20150227.1

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

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

[Touch-packages] [Bug 1426036] Re: MultiRecipientFieldStyle should inherit from TextFieldStyle

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/messaging-app

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

Title:
  MultiRecipientFieldStyle should inherit from TextFieldStyle

Status in Messaging App:
  New
Status in messaging-app package in Ubuntu:
  New
Status in messaging-app package in Ubuntu RTM:
  New

Bug description:
  Currently MultiRecipientFieldStyle inherits from TextAreaStyle.
  This might break messaging-app if the value of frameSpacing in TextAreaStyle 
changes for any reason.

  messaging-app is also using MultiRecipientFieldStyle for the TextArea
  in the conversation view, so it needs two changes:

  1) Make MultiRecipientFieldStyle inherit from TextFieldStyle.
  2) Create a local style that inherits from TextAreaStyle and use it in the 
conversation view.

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

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

[Touch-packages] [Bug 1418262] Re: apport hook to detect wayland sessions

[Tim]

** Changed in: ubuntu-gnome
   Status: New = Fix Released

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

Title:
  apport hook to detect wayland sessions

Status in Ubuntu GNOME:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  Now that we have an experimental GNOME wayland session in vivid, it
  would be somewhat useful for apport to detect if a bug report is from
  a wayland session. It probably makes sense for this to be global
  since other projects will eventually offer wayland sessions as well.
  Not sure on the best place for this to live though in apport or in
  wayland packaging or elsewhere?

  detecting WAYLAND_DISPLAY env is probably enough to detect a running
  session, and there may be a few other useful env variables such as
  (GDK/CLUTTER)_BACKEND etc

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.15.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
  Uname: Linux 3.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportLog:
   
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Feb  5 10:51:38 2015
  InstallationDate: Installed on 2012-09-23 (864 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha 
amd64(20120922)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 774290] Re: Can't switch to top-left workspace using keyboard

[Launchpad Bug Tracker]

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

** Changed in: compiz (Ubuntu)
   Status: Incomplete = Expired

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

Title:
  Can't switch to top-left workspace using keyboard

Status in Compiz:
  Expired
Status in Unity:
  Expired
Status in compiz package in Ubuntu:
  Expired
Status in unity package in Ubuntu:
  Expired

Bug description:
  Binary package hint: unity

  I can switch from top right to left bottom workspace, by pressing
  CTRL+ALT+DOWN+RIGHT. I can do the same to the right bottom, left
  bottom and right top, but no to the left top. When I am in the right
  bottom workspace, and I press CTRL+ALT+UP+LEFT, nothing happens (or it
  goes left or top sometimes).

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: unity 3.8.10-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: compiz
  DRM.card0.DIN.1:
   status: disconnected
   enabled: disabled
   dpms: On
   modes: 
   edid-base64:
  Date: Sat Apr 30 20:15:33 2011
  DistUpgraded: Fresh install
  DistroCodename: natty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GdmLog1:
   
  GdmLog2:
   
  GraphicsCard:
   ATI Technologies Inc RV770 [Radeon HD 4870] [1002:9440] (prog-if 00 [VGA 
controller])
 Subsystem: ATI Technologies Inc Device [1002:0502]
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  InstallationMedia_: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  InstallationMedia__: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  MachineType: Gigabyte Technology Co., Ltd. EP35-DS3L
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-8-generic 
root=UUID=1c4098a8-56b8-4d58-af2d-7ecc388c9876 ro quiet splash vt.handoff=7
  ProcVersionSignature_: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  ProcVersionSignature__: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Renderer: Unknown
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: EP35-DS3L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd04/02/2008:svnGigabyteTechnologyCo.,Ltd.:pnEP35-DS3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP35-DS3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EP35-DS3L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.23-1ubuntu6
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
  version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110107+b795ca6e-0ubuntu7

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

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

[Touch-packages] [Bug 774290] Re: Can't switch to top-left workspace using keyboard

[Launchpad Bug Tracker]

[Expired for Unity because there has been no activity for 60 days.]

** Changed in: unity
   Status: Incomplete = Expired

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

Title:
  Can't switch to top-left workspace using keyboard

Status in Compiz:
  Expired
Status in Unity:
  Expired
Status in compiz package in Ubuntu:
  Expired
Status in unity package in Ubuntu:
  Expired

Bug description:
  Binary package hint: unity

  I can switch from top right to left bottom workspace, by pressing
  CTRL+ALT+DOWN+RIGHT. I can do the same to the right bottom, left
  bottom and right top, but no to the left top. When I am in the right
  bottom workspace, and I press CTRL+ALT+UP+LEFT, nothing happens (or it
  goes left or top sometimes).

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: unity 3.8.10-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: compiz
  DRM.card0.DIN.1:
   status: disconnected
   enabled: disabled
   dpms: On
   modes: 
   edid-base64:
  Date: Sat Apr 30 20:15:33 2011
  DistUpgraded: Fresh install
  DistroCodename: natty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GdmLog1:
   
  GdmLog2:
   
  GraphicsCard:
   ATI Technologies Inc RV770 [Radeon HD 4870] [1002:9440] (prog-if 00 [VGA 
controller])
 Subsystem: ATI Technologies Inc Device [1002:0502]
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  InstallationMedia_: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  InstallationMedia__: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  MachineType: Gigabyte Technology Co., Ltd. EP35-DS3L
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-8-generic 
root=UUID=1c4098a8-56b8-4d58-af2d-7ecc388c9876 ro quiet splash vt.handoff=7
  ProcVersionSignature_: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  ProcVersionSignature__: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Renderer: Unknown
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: EP35-DS3L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd04/02/2008:svnGigabyteTechnologyCo.,Ltd.:pnEP35-DS3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP35-DS3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EP35-DS3L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.23-1ubuntu6
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
  version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110107+b795ca6e-0ubuntu7

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

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

[Touch-packages] [Bug 1426058] Re: info dialog not displayed properly and can't be dismissed

[Launchpad Bug Tracker]

This bug was fixed in the package messaging-app -
0.1+15.04.20150228-0ubuntu1

---
messaging-app (0.1+15.04.20150228-0ubuntu1) vivid; urgency=medium

  [ Bill Filler ]
  * Enable MMSDefault for unknown attachment types added:
src/qml/assets/transfer-unsupported01.svg

  [ CI Train Bot ]
  * New rebuild forced.

  [ Tiago Salem Herrmann ]
  * Enable MMSDefault for unknown attachment types added:
src/qml/assets/transfer-unsupported01.svg
  * Show short notification when messages are copied to clipboard. (LP:
#1426058, #1417350)
  * Use the proper style for TextField. (LP: #1426036)
 -- CI Train Bot ci-train-...@canonical.com   Sat, 28 Feb 2015 04:08:32 +

** Changed in: messaging-app (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  info dialog not displayed properly and can't be dismissed

Status in Messaging App:
  New
Status in messaging-app package in Ubuntu:
  Fix Released

Bug description:
  vivid build 110 on mako

  - open messaging-app
  - open a message thread
  - swipe left
  - click the i button

  expected results:
  - dialog should appear centered on screen with message info with a 
close/dismiss button

  actual results:
  - dialog mostly offscreen and not rendered correctly with no way to close it

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

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

[Touch-packages] [Bug 1426036] Re: MultiRecipientFieldStyle should inherit from TextFieldStyle

[Launchpad Bug Tracker]

This bug was fixed in the package messaging-app -
0.1+15.04.20150228-0ubuntu1

---
messaging-app (0.1+15.04.20150228-0ubuntu1) vivid; urgency=medium

  [ Bill Filler ]
  * Enable MMSDefault for unknown attachment types added:
src/qml/assets/transfer-unsupported01.svg

  [ CI Train Bot ]
  * New rebuild forced.

  [ Tiago Salem Herrmann ]
  * Enable MMSDefault for unknown attachment types added:
src/qml/assets/transfer-unsupported01.svg
  * Show short notification when messages are copied to clipboard. (LP:
#1426058, #1417350)
  * Use the proper style for TextField. (LP: #1426036)
 -- CI Train Bot ci-train-...@canonical.com   Sat, 28 Feb 2015 04:08:32 +

** Changed in: messaging-app (Ubuntu)
   Status: New = Fix Released

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

Title:
  MultiRecipientFieldStyle should inherit from TextFieldStyle

Status in Messaging App:
  New
Status in messaging-app package in Ubuntu:
  Fix Released
Status in messaging-app package in Ubuntu RTM:
  New

Bug description:
  Currently MultiRecipientFieldStyle inherits from TextAreaStyle.
  This might break messaging-app if the value of frameSpacing in TextAreaStyle 
changes for any reason.

  messaging-app is also using MultiRecipientFieldStyle for the TextArea
  in the conversation view, so it needs two changes:

  1) Make MultiRecipientFieldStyle inherit from TextFieldStyle.
  2) Create a local style that inherits from TextAreaStyle and use it in the 
conversation view.

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

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

[Touch-packages] [Bug 1417350] Re: [messaging-app] no feedback provided on copy operation

[Launchpad Bug Tracker]

This bug was fixed in the package messaging-app -
0.1+15.04.20150228-0ubuntu1

---
messaging-app (0.1+15.04.20150228-0ubuntu1) vivid; urgency=medium

  [ Bill Filler ]
  * Enable MMSDefault for unknown attachment types added:
src/qml/assets/transfer-unsupported01.svg

  [ CI Train Bot ]
  * New rebuild forced.

  [ Tiago Salem Herrmann ]
  * Enable MMSDefault for unknown attachment types added:
src/qml/assets/transfer-unsupported01.svg
  * Show short notification when messages are copied to clipboard. (LP:
#1426058, #1417350)
  * Use the proper style for TextField. (LP: #1426036)
 -- CI Train Bot ci-train-...@canonical.com   Sat, 28 Feb 2015 04:08:32 +

** Changed in: messaging-app (Ubuntu)
   Status: New = Fix Released

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

Title:
  [messaging-app] no feedback provided on copy operation

Status in the base for Ubuntu mobile products:
  New
Status in Messaging App:
  New
Status in Ubuntu UX bugs:
  Triaged
Status in messaging-app package in Ubuntu:
  Fix Released
Status in messaging-app package in Ubuntu RTM:
  New

Bug description:
  Expected to see 'Copied to clipboard' as a confirmation after clicking
  on the 'Copy' icon

  The testers were not quite sure what happened after they tapped on the
  'Copy' icon. The change of colour does not comfirm the effect of
  users' action effectively.

  We should display a message saying Selection copied to clipboard or
  something like that.

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

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

[Touch-packages] [Bug 1322784]

[Lhenry]

Comment on attachment 8561105
Pad heap allocations passed to flag_qsort() on x86 Linux to work around gcc bug 
affecting Ubuntu packages

Accepting for ESR 31 since it's a topcrash and affects many users.

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

Title:
  Firefox crashes in flag_qsort during spellchecker initialization on
  x86 due to gcc bug

Status in The Mozilla Firefox Browser:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in gcc-4.8 package in Ubuntu:
  Incomplete

Bug description:
  The most common Firefox crash on Linux in Mozilla's crash-stats system
  is crashes in the function flag_qsort.

  These crashes occur:
   * only on x86 architecture
   * only on Ubuntu packages (and not on Mozilla's builds)
   * on precise and saucy and trusty (based on kernel versions reported with 
the crashes)
  and appear to be due to a compiler bug in the compiler used to generate 
Ubuntu's builds.  (It could be a common compiler bug triggered by different 
compiler options or a compiler bug specific to Ubuntu's gcc.)

  The analysis that leads to the conclusion that this is a compiler bug
  is in https://bugzilla.mozilla.org/show_bug.cgi?id=983817 .  In
  particular, the compiler is miscompiling an access to an element of an
  array of unsigned short as a 32-bit read, and when the unsigned short
  in question is the last one in the allocation and that allocation is
  aligned so that the byte following has a different 0x10 bit, this
  can lead to crashes.

  The most recent (whenever you follow the link) 7 days of crash reports
  are available at: https://crash-
  
stats.mozilla.com/report/list?signature=flag_qsortproduct=Firefoxquery_type=containsrange_unit=weeks

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

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

[Touch-packages] [Bug 1322784]

[Ryanvm]

https://hg.mozilla.org/releases/mozilla-esr31/rev/ae1f4d470fd1

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

Title:
  Firefox crashes in flag_qsort during spellchecker initialization on
  x86 due to gcc bug

Status in The Mozilla Firefox Browser:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in gcc-4.8 package in Ubuntu:
  Incomplete

Bug description:
  The most common Firefox crash on Linux in Mozilla's crash-stats system
  is crashes in the function flag_qsort.

  These crashes occur:
   * only on x86 architecture
   * only on Ubuntu packages (and not on Mozilla's builds)
   * on precise and saucy and trusty (based on kernel versions reported with 
the crashes)
  and appear to be due to a compiler bug in the compiler used to generate 
Ubuntu's builds.  (It could be a common compiler bug triggered by different 
compiler options or a compiler bug specific to Ubuntu's gcc.)

  The analysis that leads to the conclusion that this is a compiler bug
  is in https://bugzilla.mozilla.org/show_bug.cgi?id=983817 .  In
  particular, the compiler is miscompiling an access to an element of an
  array of unsigned short as a 32-bit read, and when the unsigned short
  in question is the last one in the allocation and that allocation is
  aligned so that the byte following has a different 0x10 bit, this
  can lead to crashes.

  The most recent (whenever you follow the link) 7 days of crash reports
  are available at: https://crash-
  
stats.mozilla.com/report/list?signature=flag_qsortproduct=Firefoxquery_type=containsrange_unit=weeks

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

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

[Touch-packages] [Bug 1426608] Re: powerd crashed with SIGABRT in ua_sensors_proximity_new()

[ohioplayer1177]

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

bug #1420385 has a broken link. The cause of the issue in bug #1426608
has been identified and resolved. Attachment has details.

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

Title:
  powerd crashed with SIGABRT in ua_sensors_proximity_new()

Status in powerd package in Ubuntu:
  New

Bug description:
  Asus njk550 laptop. can boot into system md

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: powerd 0.16+15.04.20150219-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Feb 27 14:53:18 2015
  ExecutablePath: /usr/bin/powerd
  ExecutableTimestamp: 1424314204
  InstallationDate: Installed on 2015-02-16 (11 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150215)
  ProcCmdline: /usr/bin/powerd
  ProcCwd: /
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: powerd
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2
   ua_sensors_proximity_new () from 
/usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2
   powerd_sensors_init() ()
  Title: powerd crashed with SIGABRT in ua_sensors_proximity_new()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1426608] Re: powerd crashed with SIGABRT in ua_sensors_proximity_new()

[ohioplayer1177]

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


** Attachment added: bug_cause_fix
   
https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1426608/+attachment/4330205/+files/bug_cause_fix.txt

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

Title:
  powerd crashed with SIGABRT in ua_sensors_proximity_new()

Status in powerd package in Ubuntu:
  New

Bug description:
  Asus njk550 laptop. can boot into system md

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: powerd 0.16+15.04.20150219-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Feb 27 14:53:18 2015
  ExecutablePath: /usr/bin/powerd
  ExecutableTimestamp: 1424314204
  InstallationDate: Installed on 2015-02-16 (11 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150215)
  ProcCmdline: /usr/bin/powerd
  ProcCwd: /
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: powerd
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2
   ua_sensors_proximity_new () from 
/usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2
   powerd_sensors_init() ()
  Title: powerd crashed with SIGABRT in ua_sensors_proximity_new()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1351977] Re: New upstream release 0.9.10.0

[Tim]

** Changed in: network-manager (Ubuntu)
   Status: Confirmed = Fix Released

** Changed in: ubuntu-gnome
   Status: New = Fix Released

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

Title:
  New upstream release 0.9.10.0

Status in Ubuntu GNOME:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager package in Debian:
  Fix Released

Bug description:
  Please update package in Utopic to 0.9.10.0.

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

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

[Touch-packages] [Bug 774290] Re: Can't switch to top-left workspace using keyboard

[Launchpad Bug Tracker]

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

** Changed in: unity (Ubuntu)
   Status: Incomplete = Expired

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

Title:
  Can't switch to top-left workspace using keyboard

Status in Compiz:
  Expired
Status in Unity:
  Expired
Status in compiz package in Ubuntu:
  Expired
Status in unity package in Ubuntu:
  Expired

Bug description:
  Binary package hint: unity

  I can switch from top right to left bottom workspace, by pressing
  CTRL+ALT+DOWN+RIGHT. I can do the same to the right bottom, left
  bottom and right top, but no to the left top. When I am in the right
  bottom workspace, and I press CTRL+ALT+UP+LEFT, nothing happens (or it
  goes left or top sometimes).

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: unity 3.8.10-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: compiz
  DRM.card0.DIN.1:
   status: disconnected
   enabled: disabled
   dpms: On
   modes: 
   edid-base64:
  Date: Sat Apr 30 20:15:33 2011
  DistUpgraded: Fresh install
  DistroCodename: natty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GdmLog1:
   
  GdmLog2:
   
  GraphicsCard:
   ATI Technologies Inc RV770 [Radeon HD 4870] [1002:9440] (prog-if 00 [VGA 
controller])
 Subsystem: ATI Technologies Inc Device [1002:0502]
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  InstallationMedia_: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  InstallationMedia__: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  MachineType: Gigabyte Technology Co., Ltd. EP35-DS3L
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-8-generic 
root=UUID=1c4098a8-56b8-4d58-af2d-7ecc388c9876 ro quiet splash vt.handoff=7
  ProcVersionSignature_: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  ProcVersionSignature__: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Renderer: Unknown
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: EP35-DS3L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd04/02/2008:svnGigabyteTechnologyCo.,Ltd.:pnEP35-DS3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP35-DS3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EP35-DS3L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.23-1ubuntu6
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
  version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110107+b795ca6e-0ubuntu7

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

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

[Touch-packages] [Bug 774290] Re: Can't switch to top-left workspace using keyboard

[Launchpad Bug Tracker]

[Expired for Compiz because there has been no activity for 60 days.]

** Changed in: compiz
   Status: Incomplete = Expired

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

Title:
  Can't switch to top-left workspace using keyboard

Status in Compiz:
  Expired
Status in Unity:
  Expired
Status in compiz package in Ubuntu:
  Expired
Status in unity package in Ubuntu:
  Expired

Bug description:
  Binary package hint: unity

  I can switch from top right to left bottom workspace, by pressing
  CTRL+ALT+DOWN+RIGHT. I can do the same to the right bottom, left
  bottom and right top, but no to the left top. When I am in the right
  bottom workspace, and I press CTRL+ALT+UP+LEFT, nothing happens (or it
  goes left or top sometimes).

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: unity 3.8.10-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: compiz
  DRM.card0.DIN.1:
   status: disconnected
   enabled: disabled
   dpms: On
   modes: 
   edid-base64:
  Date: Sat Apr 30 20:15:33 2011
  DistUpgraded: Fresh install
  DistroCodename: natty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GdmLog1:
   
  GdmLog2:
   
  GraphicsCard:
   ATI Technologies Inc RV770 [Radeon HD 4870] [1002:9440] (prog-if 00 [VGA 
controller])
 Subsystem: ATI Technologies Inc Device [1002:0502]
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  InstallationMedia_: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  InstallationMedia__: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  MachineType: Gigabyte Technology Co., Ltd. EP35-DS3L
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-8-generic 
root=UUID=1c4098a8-56b8-4d58-af2d-7ecc388c9876 ro quiet splash vt.handoff=7
  ProcVersionSignature_: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  ProcVersionSignature__: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Renderer: Unknown
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: EP35-DS3L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd04/02/2008:svnGigabyteTechnologyCo.,Ltd.:pnEP35-DS3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP35-DS3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EP35-DS3L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.23-1ubuntu6
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
  version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110107+b795ca6e-0ubuntu7

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

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

[Touch-packages] [Bug 1423942] Re: Replying from the indicator discards messages if invalid SIM is set as default

[Launchpad Bug Tracker]

This bug was fixed in the package telephony-service -
0.1+15.04.20150227-0ubuntu1

---
telephony-service (0.1+15.04.20150227-0ubuntu1) vivid; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.

  [ Tiago Salem Herrmann ]
  * Check if default sim is active before sending messages. (LP:
#1423942)
  * Do not create instance of GreeterContacts to avoid dealock with
unity. (LP: #1426399)
 -- CI Train Bot ci-train-...@canonical.com   Fri, 27 Feb 2015 15:28:57 +

** Changed in: telephony-service (Ubuntu)
   Status: In Progress = Fix Released

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

Title:
  Replying from the indicator discards messages if invalid SIM is set as
  default

Status in the base for Ubuntu mobile products:
  New
Status in telephony-service package in Ubuntu:
  Fix Released
Status in telephony-service package in Ubuntu RTM:
  New

Bug description:
  Using rtm 240 on a bq device
  - use 2 SIMs
  - select SIM 2 as default
  - remove SIM 2
  - receive a call on SIM 1 and miss it
  - reply to the missed call from the messaging menu

  - the reply is discarded without any error or user feedback

  The code should check that the configuration is valid and restore a
  sane default if it's not

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

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

[Touch-packages] [Bug 1426399] Re: Sheel freezes for a short time when pressing the Play key on a connected BT keyboard

[Launchpad Bug Tracker]

This bug was fixed in the package telephony-service -
0.1+15.04.20150227-0ubuntu1

---
telephony-service (0.1+15.04.20150227-0ubuntu1) vivid; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.

  [ Tiago Salem Herrmann ]
  * Check if default sim is active before sending messages. (LP:
#1423942)
  * Do not create instance of GreeterContacts to avoid dealock with
unity. (LP: #1426399)
 -- CI Train Bot ci-train-...@canonical.com   Fri, 27 Feb 2015 15:28:57 +

** Changed in: telephony-service (Ubuntu)
   Status: In Progress = Fix Released

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

Title:
  Sheel freezes for a short time when pressing the Play key on a
  connected BT keyboard

Status in telephony-service package in Ubuntu:
  Fix Released

Bug description:
  How to reproduce:

  1) Connect a bluetooth keyboard to your Nexus 4.
  2) Press the Play key on the keyboard.

  What happens:

  Unity8 freezes for some seconds.

  
  phablet@ubuntu-phablet:~$ system-image-cli --info
  current build number: 114
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-02-27 15:25:45
  version version: 114
  version ubuntu: 20150227.1
  version device: 20150210
  version custom: 20150227.1

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

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

[Touch-packages] [Bug 1426467] Re: Indicator can fail to display panel icon

[Tony Espy]

Note, I just hit another related problem where the phone booted and the
automatic PIN-unlock dialog wasn't displayed.  This is the first time
I've hit this in maybe 75 boots.

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

Title:
  Indicator can fail to display panel icon

Status in indicator-network package in Ubuntu:
  New

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/devel-proposed

  It's possible for the device to boot in such a manner that the
  network-indicator doesn't display an icon on the top panel ( see
  attached screenshot ).

  I was testing a change to ofono ( currently in silo ubuntu-013 ) which
  fixes a MTK-specific bug where the device boots and the 2nd SIM slot
  isn't recognized.  So to test, I continually rebooted the device.  I
  have two SIMs installed, the first unlocked, the second is locked.

  In the case of the missing icon, no PIN unlock screen was displayed
  after booting.

  I checked using 'ps' and an indicator-network process is running,
  however when I checked /home/phablet/.cache/upstart, there only
  indicator-network log files I see are the saved .gz files.  There's no
  unzipped/current indicator-network.log.  The .gz log file with the
  most recent timestamp shows a single log message:

  phablet@ubuntu-phablet:~/.cache/upstart$ less indicator-network.log.1.gz
  void core::dbus::PropertyT::handle_changed(const 
core::dbus::types::Variant) [with PropertyType = 
org::freedesktop::URfkill::Interface::Killswitch::Property::State]: 
org.freedesktop.DBus.Error.UnknownMethod: Method Get with signature ss on 
interface org.freedesktop.DBus.Properties doesn't exist

  I checked and urfkilld is running on the system.

  I also verified that there were no crash files present on the system.

  I also checked and there was nothing relevant in syslog.

  This bug is hard to reproduce as well.  I've hit it 4 or 5 times out
  of a total of maybe 45-50 reboots.

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

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

[Touch-packages] [Bug 1424206] Re: Login into the password set account without asking password during boot up.

[Marc Deslauriers]

Looks to me like the user is in the nopasswdlogin group.

Please remove the user from that group and see if the problem is
resolved.

Thanks!

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

** Information type changed from Private Security to Public Security

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

Title:
  Login into the password set account without asking password during
  boot up.

Status in shadow package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 14.04 on booting

  login's into one of the account without asking for the password.

  though a password is set for all accounts.

  See at this link
  http://youtu.be/vXkAOkW-aUo

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: login 1:4.1.5.1-1ubuntu9
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic i686
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Feb 21 21:13:31 2015
  InstallationDate: Installed on 2015-02-07 (13 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1424195] Re: Config option flat-volumes is set to YES by default

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio - 1:6.0-0ubuntu4

---
pulseaudio (1:6.0-0ubuntu4) vivid; urgency=medium

  * Move the previously tweaked volume config changes from the rules file
to a patch. We are no longer tweaking settings based on architecture,
so such config changes can now be aplied statically. These settings
were also not being applied since the merge with Debian and updating to
pulse 6. (LP: #1424195)
 -- Luke Yelavich them...@ubuntu.com   Mon, 23 Feb 2015 10:03:37 +1100

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

Title:
  Config option flat-volumes is set to YES by default

Status in One Hundred Papercuts:
  Fix Committed
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  
  Config option flat-volumes is set to YES by default, unlike to NO in previous 
Ubuntu releases (=14.10).

  So now global volume level overrides applications' volume level.

  It produces unexpected behavior.

  How to fix:
Change  ; flat-volume = yes  to  flat-volume = no   (delete ' ; '  to 
uncomment)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pulseaudio 1:6.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nemanja4308 F pulseaudio
   /dev/snd/pcmC0D0c:   nemanja4308 F...m pulseaudio
   /dev/snd/pcmC0D0p:   nemanja4308 F...m pulseaudio
   /dev/snd/controlC0:  nemanja4308 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Feb 21 15:24:22 2015
  InstallationDate: Installed on 2014-10-21 (122 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64+mac (20140923)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to vivid on 2015-02-21 (0 days ago)
  dmi.bios.date: 03/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: B75 Pro3-M
  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.:bvrP1.70:bd03/02/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB75Pro3-M: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.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2015-02-21T15:21:07.623536

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

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

[Touch-packages] [Bug 1426370] [NEW] Wrong keyboard layout after suspend

[Raphael Mankin]

Public bug reported:

I use several keyboards on my machine, with different layouts.

After the machine wakes from a sleep it always comes back with the first
configured layout instead of the one I was using before it went to
sleep.

This is an irritation, rather than a stopper.

Description:Ubuntu 12.04.5 LTS
Release:12.04

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-46.75-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom]
CompositorRunning: None
CurrentDesktop: Unity
Date: Fri Feb 27 13:26:25 2015
DistUpgraded: 2014-09-11 22:33:29,890 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo ThinkPad T61p [17aa:20d9]
InstallationDate: Installed on 2014-09-05 (174 days ago)
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
MachineType: LENOVO 6459CTO
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic 
root=UUID=ea8d2b87-e06e-4df4-941a-7ca7dcab5c82 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to trusty on 2014-09-11 (168 days ago)
dmi.bios.date: 05/11/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETC6WW (2.26 )
dmi.board.name: 6459CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr7LETC6WW(2.26):bd05/11/2009:svnLENOVO:pn6459CTO:pvrThinkPadT61p:rvnLENOVO:rn6459CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 6459CTO
dmi.product.version: ThinkPad T61p
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1~ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu Feb 26 13:28:28 2015
xserver.configfile: default
xserver.errors:
 Failed to load module nvidia (module does not exist, 0)
 Failed to load module nvidia (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.7
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug trusty ubuntu

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

Title:
  Wrong keyboard layout after suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  I use several keyboards on my machine, with different layouts.

  After the machine wakes from a sleep it always comes back with the
  first configured layout instead of the one I was using before it went
  to sleep.

  This is an irritation, rather than a stopper.

  Description:  Ubuntu 12.04.5 LTS
  Release:  12.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-46.75-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom]
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Fri Feb 27 13:26:25 2015
  DistUpgraded: 2014-09-11 22:33:29,890 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo ThinkPad T61p [17aa:20d9]
  InstallationDate: Installed on 2014-09-05 (174 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  

[Touch-packages] [Bug 1426354] [NEW] Welcome wizard should show the timezone page to allow the user to set the correct system time

[Nekhelesh Ramananthan]

Public bug reported:

I have noticed several people reporting https://bugs.launchpad.net
/ubuntu-clock-app/+bug/1233986 against the clock app since the system
time set by default is UTC while the clock app shows the correct user
location. Thereby if the user location shown by the clock app is Paris
while the clock app time shown is UTC it creates a conflicting and
confusing situation.

I understand that the clock app needs to fix it on its end to ensure
that if there is discrepancy between the time shown and the user
location then a dialog informing the user to correct the system time be
shown.

But nonetheless this issue wouldn't be present if the welcome wizard
shows the timezone page where the user can set the correct system time
in the first place.

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

** Description changed:

  I have noticed several people reporting https://bugs.launchpad.net
  /ubuntu-clock-app/+bug/1233986 against the clock app since the system
  time set by default is UTC while the clock app shows the correct user
  location. Thereby if the user location shown by the clock app is Paris
- while the time shown is UTC it creates a conflict and confusing
- situation.
+ while the clock app time shown is UTC it creates a conflict and
+ confusing situation.
  
  I understand that the clock app needs to fix it on its end to ensure
  that if there is discrepancy between the time shown and the user
  location then a dialog informing the user to correct the system time be
  shown.
  
  But nonetheless this issue wouldn't be present if the welcome wizard
  shows the timezone page where the user can set the correct system time
  in the first place.

** Description changed:

  I have noticed several people reporting https://bugs.launchpad.net
  /ubuntu-clock-app/+bug/1233986 against the clock app since the system
  time set by default is UTC while the clock app shows the correct user
  location. Thereby if the user location shown by the clock app is Paris
- while the clock app time shown is UTC it creates a conflict and
+ while the clock app time shown is UTC it creates a conflicting and
  confusing situation.
  
  I understand that the clock app needs to fix it on its end to ensure
  that if there is discrepancy between the time shown and the user
  location then a dialog informing the user to correct the system time be
  shown.
  
  But nonetheless this issue wouldn't be present if the welcome wizard
  shows the timezone page where the user can set the correct system time
  in the first place.

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

Title:
  Welcome wizard should show the timezone page to allow the user to set
  the correct system time

Status in unity8 package in Ubuntu:
  New

Bug description:
  I have noticed several people reporting https://bugs.launchpad.net
  /ubuntu-clock-app/+bug/1233986 against the clock app since the system
  time set by default is UTC while the clock app shows the correct user
  location. Thereby if the user location shown by the clock app is Paris
  while the clock app time shown is UTC it creates a conflicting and
  confusing situation.

  I understand that the clock app needs to fix it on its end to ensure
  that if there is discrepancy between the time shown and the user
  location then a dialog informing the user to correct the system time
  be shown.

  But nonetheless this issue wouldn't be present if the welcome wizard
  shows the timezone page where the user can set the correct system time
  in the first place.

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

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

[Touch-packages] [Bug 1426347] Re: [browser] In landscape mode (phone), the app should go full screen

[Giorgio Venturi]

How about: 
IF landscape=true AND height 51 THEN make app window full screen

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

Title:
  [browser] In landscape mode (phone), the app should go full screen

Status in Ubuntu UX bugs:
  Fix Committed
Status in Web Browser App:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  In landscape mode (on the phone form factor) there is a limited real
  estate available, therefore it is beneficial to go full screen and
  free up valuable space for the content.

  On tablet FFs this is not an issue and the behaviour should be the
  default (i.e. indicators are shown)

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

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

[Touch-packages] [Bug 1424308] Re: xkillxkillcompiz crashed with SIGSEGV in xcb_take_socket()

[Marc Deslauriers]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  xkillxkillcompiz crashed with SIGSEGV in xcb_take_socket()

Status in unity package in Ubuntu:
  New

Bug description:
  unity is gone trying to get it back

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150219.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: wl fglrx
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Sat Feb 21 21:35:21 2015
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2015-02-21 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  ProcCmdline: compiz --replace
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fd8f0d23963 xcb_take_socket+19:   mov
(%rdi),%edi
   PC (0x7fd8f0d23963) ok
   source (%rdi) (0x0001) not located in a known VMA region (needed 
readable region)!
   destination %edi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   xcb_take_socket () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XFlush () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XGetRequest () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XGetSelectionOwner () from /usr/lib/x86_64-linux-gnu/libX11.so.6
  Title: compiz crashed with SIGSEGV in xcb_take_socket()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1186662] Re: isc-dhcp-server fails to renew lease file

[DigiAngel]

And continuing to see this:

Feb 27 05:43:17 gateway dhcpd: Can't create new lease file: Permission denied
Feb 27 05:43:17 gateway kernel: [ 4703.128481] type=1400 
audit(1425040997.320:41): apparmor=DENIED operation=capable 
profile=/usr/sbin/dhcpd pid=2189 comm=dhcpd capability=1  
capname=dac_override

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

Title:
  isc-dhcp-server fails to renew lease file

Status in isc-dhcp package in Ubuntu:
  Triaged

Bug description:
  After raring upgrade, the dhcp server fails to renew lease file when
  it tries to (about every hour).

  The syslog says:
  dhcpd: Can't create new lease file: Permission denied

  It looks like a permission problem, because

  # chown -R dhcpd:dhcpd /var/lib/dhcp

  the above command temporarily solves the issue, until dhcpd is
  restarted: at that time, the ownership of the directory and the lease
  file is set back to root:root.

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

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

[Touch-packages] [Bug 1425948] Re: The screen freezes and stop all process.

[Marc Deslauriers]

Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System - 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!


** Information type changed from Private Security to Public

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

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

Title:
  The screen freezes and stop all process.

Status in indicator-sound package in Ubuntu:
  Invalid

Bug description:
  The screen freezes and stop all process.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150219.1-0ubuntu1
  Uname: Linux 4.0.0-04rc1-lowlatency x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Feb 26 11:22:22 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha amd64 (20150224)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  Signal: 5
  SourcePackage: indicator-sound
  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/1425948/+subscriptions

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

[Touch-packages] [Bug 1426358] [NEW] upgrade of whoopsie fails due to report_crashes=false

[Tobias Wolter]

Public bug reported:

Cheers,

I'm using systemd and have set report_crashes=false in
/etc/default/whoopsie.

The systemctl service

$ systemctl status whoopsie.service
whoopsie.service - crash report submission daemon
   Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled)
   Active: failed (Result: start-limit) since Fr 2015-02-27 13:52:53 CET; 7s ago
  Process: 22882 ExecStartPre=/bin/grep -sqi report_crashes=true 
/etc/default/whoopsie (code=exited, status=1/FAILURE)

fails as one would expect; but having these kind of startup requirements
in the systemd service is probably a bad idea, especially as it leaves
the package unconfigured:

$ sudo dpkg --configure --pending
Setting up whoopsie (0.2.39ubuntu0.2) ...
Job for whoopsie.service failed. See 'systemctl status whoopsie.service' and 
'journalctl -xn' for details.
invoke-rc.d: initscript whoopsie, action start failed.
dpkg: error processing package whoopsie (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 whoopsie

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: whoopsie 0.2.39ubuntu0.2
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.2
Architecture: amd64
CrashReports: 640:0:111:272248:2015-02-27 13:37:38.737388070 +0100:2015-02-27 
13:37:38.685387839 +0100:/var/crash/whoopsie.0.crash
CurrentDesktop: GNOME
Date: Fri Feb 27 13:54:04 2015
InstallationDate: Installed on 2013-05-06 (661 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 
(20130424)
RelatedPackageVersions: apport-noui N/A
SourcePackage: whoopsie
UpgradeStatus: Upgraded to utopic on 2014-10-23 (126 days ago)
modified.conffile..etc.default.whoopsie:
 [General]
 report_crashes=false
mtime.conffile..etc.default.whoopsie: 2013-12-15T20:44:50.138659

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


** Tags: amd64 apport-bug autoreport-false utopic

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

Title:
  upgrade of whoopsie fails due to report_crashes=false

Status in whoopsie package in Ubuntu:
  New

Bug description:
  Cheers,

  I'm using systemd and have set report_crashes=false in
  /etc/default/whoopsie.

  The systemctl service

  $ systemctl status whoopsie.service
  whoopsie.service - crash report submission daemon
 Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled)
 Active: failed (Result: start-limit) since Fr 2015-02-27 13:52:53 CET; 7s 
ago
Process: 22882 ExecStartPre=/bin/grep -sqi report_crashes=true 
/etc/default/whoopsie (code=exited, status=1/FAILURE)

  fails as one would expect; but having these kind of startup
  requirements in the systemd service is probably a bad idea, especially
  as it leaves the package unconfigured:

  $ sudo dpkg --configure --pending
  Setting up whoopsie (0.2.39ubuntu0.2) ...
  Job for whoopsie.service failed. See 'systemctl status whoopsie.service' and 
'journalctl -xn' for details.
  invoke-rc.d: initscript whoopsie, action start failed.
  dpkg: error processing package whoopsie (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   whoopsie

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: whoopsie 0.2.39ubuntu0.2
  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.2
  Architecture: amd64
  CrashReports: 640:0:111:272248:2015-02-27 13:37:38.737388070 +0100:2015-02-27 
13:37:38.685387839 +0100:/var/crash/whoopsie.0.crash
  CurrentDesktop: GNOME
  Date: Fri Feb 27 13:54:04 2015
  InstallationDate: Installed on 2013-05-06 (661 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 
(20130424)
  RelatedPackageVersions: apport-noui N/A
  SourcePackage: whoopsie
  UpgradeStatus: Upgraded to utopic on 2014-10-23 (126 days ago)
  modified.conffile..etc.default.whoopsie:
   [General]
   report_crashes=false
  mtime.conffile..etc.default.whoopsie: 2013-12-15T20:44:50.138659

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

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

[Touch-packages] [Bug 1424726] Re: browser cache is under ~/.local/share/

[Olivier Tilloy]

** Changed in: webbrowser-app
   Status: In Progress = Fix Released

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

Title:
  browser cache is under ~/.local/share/

Status in Web Browser App:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu RTM:
  Confirmed

Bug description:
  Browser and webapp’s cache is stored under ~/.local/share/.
  It should go under ~/.cache/.

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

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

[Touch-packages] [Bug 1426307] Re: location is inaccurate

[Łukasz Zemczak]

** Tags added: lt-blocker lt-category-visible

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

Title:
  location is inaccurate

Status in location-service package in Ubuntu:
  New

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-02-25 15:06:29
  version version: 122
  version ubuntu: 20150225
  version device: 20150210-95b6a9f
  version custom: 20150225

  Location is inaccurate, it thinks that I'm several kilometres away
  from my actual location, in the middle of the sea.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubuntu-location-service-bin 2.1+15.04.20150126.1-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  Date: Fri Feb 27 11:10:42 2015
  InstallationDate: Installed on 2015-02-25 (2 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150225-020204)
  SourcePackage: location-service
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.ubuntu.location.service.conf: 2015-02-10T21:38:59

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

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

[Touch-packages] [Bug 1426328] Re: Undocking laptop moves windows to different workspaces they were originally

[Brian Murray]

** Package changed: ubuntu-meta (Ubuntu) = unity (Ubuntu)

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

Title:
  Undocking laptop moves windows to different workspaces they were
  originally

Status in unity package in Ubuntu:
  New

Bug description:
  I use desktop with 2x2 workspaces. As hardware, I use dual-head
  display, i.e. using laptop internal monitor and external monitor
  connected to docking station.

  When I undock laptop, in many cases windows move to another workspace
  they were before undocking. This is a bit annoying as I have windows
  related to each task in their own workspace and I has to move windows
  around each time I undock.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-desktop 1.325
  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.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 27 13:15:40 2015
  InstallationDate: Installed on 2014-09-20 (160 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Charles Kerr]

Also, if you could include the output of

$  gdbus call --session --dest org.freedesktop.DBus --object-path /
--method org.freedesktop.DBus.GetNameOwner
com.canonical.indicator.datetime

that should at least tell us whether or not indicator-datetime-service
reached the point of owning its name on the bus.

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

Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu RTM:
  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 1426454] [NEW] Keyboard layout for Icelandic(Machintosh) is wrong

[Arnkell Logi Pétursson]

Public bug reported:

Hi,

Thank you for a great OS! I found a small bug that affects maybe 10
people in the world but I'm one of them :-)

I'm using the aluminum mac keyboard with an Icelandic layout.

1) I'm using Ubuntu 14.10
2) I'm not sure what package this applies to.
3) Third level selectors are more or less all wrong.
4) Wrong character appears

I've made an xmodmap file that fixes these issues and attached it.

with regards, Logi

** Affects: xkeyboard-config (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: Xmodmap that fixes these issues
   
https://bugs.launchpad.net/bugs/1426454/+attachment/4329545/+files/xmodmap.txt

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

Title:
  Keyboard layout for Icelandic(Machintosh) is wrong

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  Hi,

  Thank you for a great OS! I found a small bug that affects maybe 10
  people in the world but I'm one of them :-)

  I'm using the aluminum mac keyboard with an Icelandic layout.

  1) I'm using Ubuntu 14.10
  2) I'm not sure what package this applies to.
  3) Third level selectors are more or less all wrong.
  4) Wrong character appears

  I've made an xmodmap file that fixes these issues and attached it.

  with regards, Logi

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

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

[Touch-packages] [Bug 1425987] Re: Cellular data connection stops after a while

[Tony Espy]

Note, I see  you attached the output of 'nmcli d' ( nmcli-dev.txt ), but
what's important is the output  after the problem occurs.  The file you
attached shows the initial state when things are working.

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

Title:
  Cellular data connection stops after a while

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-02-25 15:06:29
  version version: 122
  version ubuntu: 20150225
  version device: 20150210-95b6a9f
  version custom: 20150225

  Test Case:
  1. Disable Wifi
  2. Verify that a cellular data connection is established
  3. Wait...

  Actual result
  After a while (several minutes) the cellular data connection stops, 
eventually it'll come back but not always.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Thu Feb 26 16:14:14 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2015-02-25 (1 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150225-020204)
  IpRoute:
   
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  PciNetwork:
   
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 
2015-02-25T03:31:54
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1425987] Re: Cellular data connection stops after a while

[Tony Espy]

@Jean-Baptiste

I'm pretty sure this is a duplicate of bug #1426122.

When your network fails, can you grab the output of the command 'nmcli
d'?

The problem we've seen on arale  krillin with network-manager 0.9.10 is
that the patch that makes network-manager ignore devices owned by rild,
wasn't updated for arale  krillin, and the NM 0.9.10's behavior changed
slightly such that it now will try and manage the rild devices when they
become active.


** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) = Jean-Baptiste Lallement (jibel)

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

Title:
  Cellular data connection stops after a while

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-02-25 15:06:29
  version version: 122
  version ubuntu: 20150225
  version device: 20150210-95b6a9f
  version custom: 20150225

  Test Case:
  1. Disable Wifi
  2. Verify that a cellular data connection is established
  3. Wait...

  Actual result
  After a while (several minutes) the cellular data connection stops, 
eventually it'll come back but not always.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Thu Feb 26 16:14:14 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2015-02-25 (1 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150225-020204)
  IpRoute:
   
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  PciNetwork:
   
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 
2015-02-25T03:31:54
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1419829] Re: [Scope] location settings are enabled by default

[Thomas Strehl]

Possible fix would be to add a page to phone setup wizard asking users
whether they allow, by default, scope to access location data or not.
That setting will also be available via Settings|Privacy. Then, we'd
change the individual scope location settings to provide two states,
system|off (system being default). With this, scopes by default take
the system or rather scopes wide system settings but it still offers the
possibility to disable location for individual scopes. Also note that
changing the location settings value would not require any changes to
existing scopes.

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

Title:
  [Scope] location settings are enabled by default

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  New
Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  This is in contrast to the rest of the system where user have to
  explicitly grant access right upfront.

  Possible solution would be to add a new page in phone setup wizard
  asking for whether scopes are allowed to use location or not and then
  applying this to individual scope location settings.

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

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

[Touch-packages] [Bug 1416043] Re: Expected to be able to select picture in a full screen preview mode before sending it

[Pat McGowan]

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

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

** Changed in: canonical-devices-system-image
Milestone: ww09-2015 = ww13-ota

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

Title:
  Expected to be able to select picture in a full screen preview mode
  before sending it

Status in Camera App:
  In Progress
Status in the base for Ubuntu mobile products:
  Fix Released
Status in Gallery App:
  In Progress
Status in camera-app package in Ubuntu:
  Fix Released
Status in gallery-app package in Ubuntu:
  Fix Released

Bug description:
  When trying to send picture via Gallery (event view) or Telegram or
  Messaging app, it is difficult to select the desired one (especially
  when the pictures were similar). This is because the pictures were not
  displayed in full sizes, and there was no preview mode for them to
  check before committing to send.

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

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

[Touch-packages] [Bug 1426467] Re: Indicator can fail to display panel icon

[Tony Espy]

Forgot to add, when I run ofono's list-modems script, things look
normal, the first SIM is powered, and registered to the network, the
second SIM ( ril_1 ) is PIN locked.

I just hit this a second time, and again no indicator-network.log file
is present.

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

Title:
  Indicator can fail to display panel icon

Status in indicator-network package in Ubuntu:
  New

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/devel-proposed

  It's possible for the device to boot in such a manner that the
  network-indicator doesn't display an icon on the top panel ( see
  attached screenshot ).

  I was testing a change to ofono ( currently in silo ubuntu-013 ) which
  fixes a MTK-specific bug where the device boots and the 2nd SIM slot
  isn't recognized.  So to test, I continually rebooted the device.  I
  have two SIMs installed, the first unlocked, the second is locked.

  In the case of the missing icon, no PIN unlock screen was displayed
  after booting.

  I checked using 'ps' and an indicator-network process is running,
  however when I checked /home/phablet/.cache/upstart, there only
  indicator-network log files I see are the saved .gz files.  There's no
  unzipped/current indicator-network.log.  The .gz log file with the
  most recent timestamp shows a single log message:

  phablet@ubuntu-phablet:~/.cache/upstart$ less indicator-network.log.1.gz
  void core::dbus::PropertyT::handle_changed(const 
core::dbus::types::Variant) [with PropertyType = 
org::freedesktop::URfkill::Interface::Killswitch::Property::State]: 
org.freedesktop.DBus.Error.UnknownMethod: Method Get with signature ss on 
interface org.freedesktop.DBus.Properties doesn't exist

  I checked and urfkilld is running on the system.

  I also verified that there were no crash files present on the system.

  I also checked and there was nothing relevant in syslog.

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

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

[Touch-packages] [Bug 1426467] Re: Indicator fails to start

[Tony Espy]

** Attachment added: no-sim-unlock-no-indicator-lockscreen.png
   
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1426467/+attachment/4329548/+files/no-sim-unlock-no-indicator-lockscreen.png

** Summary changed:

- Indicator fails to start
+ Indicator can fail to display panel icon

** Description changed:

  current build number: 122
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  
  It's possible for the device to boot in such a manner that the network-
  indicator doesn't display an icon on the top panel ( see attached
  screenshot ).
  
  I was testing a change to ofono ( currently in silo ubuntu-013 ) which
  fixes a MTK-specific bug where the device boots and the 2nd SIM slot
  isn't recognized.  So to test, I continually rebooted the device.  I
  have two SIMs installed, the first unlocked, the second is locked.
  
  In the case of the missing icon, no PIN unlock screen was displayed
  after booting.
  
  I checked using 'ps' and an indicator-network process is running,
  however when I checked /home/phablet/.cache/upstart, there only
  indicator-network log files I see are the saved .gz files.  There's no
  unzipped/current indicator-network.log.  The .gz log file with the most
  recent timestamp shows a single log message:
  
- phablet@ubuntu-phablet:~/.cache/upstart$ less indicator-network.log.1.gz 
+ phablet@ubuntu-phablet:~/.cache/upstart$ less indicator-network.log.1.gz
  void core::dbus::PropertyT::handle_changed(const 
core::dbus::types::Variant) [with PropertyType = 
org::freedesktop::URfkill::Interface::Killswitch::Property::State]: 
org.freedesktop.DBus.Error.UnknownMethod: Method Get with signature ss on 
interface org.freedesktop.DBus.Properties doesn't exist
  
  I checked and urfkilld is running on the system.
  
  I also verified that there were no crash files present on the system.
+ 
+ I also checked and there was nothing relevant in syslog.

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

Title:
  Indicator can fail to display panel icon

Status in indicator-network package in Ubuntu:
  New

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/devel-proposed

  It's possible for the device to boot in such a manner that the
  network-indicator doesn't display an icon on the top panel ( see
  attached screenshot ).

  I was testing a change to ofono ( currently in silo ubuntu-013 ) which
  fixes a MTK-specific bug where the device boots and the 2nd SIM slot
  isn't recognized.  So to test, I continually rebooted the device.  I
  have two SIMs installed, the first unlocked, the second is locked.

  In the case of the missing icon, no PIN unlock screen was displayed
  after booting.

  I checked using 'ps' and an indicator-network process is running,
  however when I checked /home/phablet/.cache/upstart, there only
  indicator-network log files I see are the saved .gz files.  There's no
  unzipped/current indicator-network.log.  The .gz log file with the
  most recent timestamp shows a single log message:

  phablet@ubuntu-phablet:~/.cache/upstart$ less indicator-network.log.1.gz
  void core::dbus::PropertyT::handle_changed(const 
core::dbus::types::Variant) [with PropertyType = 
org::freedesktop::URfkill::Interface::Killswitch::Property::State]: 
org.freedesktop.DBus.Error.UnknownMethod: Method Get with signature ss on 
interface org.freedesktop.DBus.Properties doesn't exist

  I checked and urfkilld is running on the system.

  I also verified that there were no crash files present on the system.

  I also checked and there was nothing relevant in syslog.

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

-- 
Mailing list: https://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 1412075] Re: dvd play back

[tom randolph]

it happened that one time . could have something i did stupid while 
playing around with the system. is't running flawless. has been since 
6.06 draper. thank you tom.
On 02/26/2015 06:25 AM, Christopher M. Penalver wrote:
 tom randolph, thank you for taking the time to report this and helping
 to make Ubuntu better. Unfortunately, we cannot work on this bug because
 your description didn't include enough information. You may find it
 helpful to read How to report bugs effectively
 http://www.chiark.greenend.org.uk/~sgtatham/bugs.html and
 https://wiki.ubuntu.com/ReportingBugs . We'd be grateful if you would
 then provide a more complete description of the problem.

 We have instructions on debugging some types of problems at
 http://wiki.ubuntu.com/DebuggingProcedures

 At a minimum, we need:
 1. The specific steps or actions you took that caused you to encounter the 
 problem,
 2. The behavior you expected, and
 3. The behavior you actually encountered (in as much detail as possible).

 Thank you for your understanding.

 ** Tags added: bios-outdated-3.57

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

Title:
  dvd play back

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  was trying to play advd

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.65  Tue Dec  2 09:50:34 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Sat Jan 17 17:28:59 2015
  DistUpgraded: 2014-10-10 11:24:25,254 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation Device [10de:0f02] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Device [196e:1117]
  InstallationDate: Installed on 2014-09-25 (114 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MachineType: Hewlett-Packard HP Z600 Workstation
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic 
root=UUID=44d13d87-248f-409f-9487-7d647bf1000b ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-10-10 (99 days ago)
  dmi.bios.date: 08/19/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G4 v01.17
  dmi.board.name: 0AE8h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA9420NLB
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G4v01.17:bd08/19/2009:svnHewlett-Packard:pnHPZ600Workstation:pvr:rvnHewlett-Packard:rn0AE8h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Z600 Workstation
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58+git20141201.f99522e6-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.5.0~git20150114.efef6c82-0ubuntu0ricotz3~trusty
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.5.0~git20150114.efef6c82-0ubuntu0ricotz3~trusty
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  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+git20141215.99537089-0ubuntu0sarvatt~trusty
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11+git20141030.3fb97d78-0ubuntu0sarvatt~trusty2
  xserver.bootTime: Sat Jan 17 13:53:56 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB OPTICAL MOUSEMOUSE, id 8
   inputCHICONY HP Basic USB Keyboard KEYBOARD, id 9
   inputHP WMI hotkeys   KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.6

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

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

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

[Charles Kerr]

From what aacid's said in IRC and in duplicate bug #1421919, indicator-
datetime-service is still running but is not responding to dbus-send
messages.

If anyone experiences this in the future, a gdb backtrace could be
helpful here -- I'm wondering if the code is deadlocked somewhere s.t.
it's unable to respond to dbus requests.

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

Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu RTM:
  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 1426471] [NEW] Guideline/documentation has no layout recommendation for buttons in dialogs

[Sebastien Bacher]

Public bug reported:

Reading the current documentation there is no real guidance on how to
layout buttons in Dialogs.

The design vision section 4. [1] mentions Positive actions always go
on the right, negative on the left, which suggests an horizontal
alignment for the buttons, but the building blocks section [2] doesn't
mention the topic and the uitk defaults to stacking things vertically,
including the API example [3], while the uitk-gallery example program
does show an horizontal layout by stacking its button in a row (if
that's recommended way, the API example should perhaps reflect that?)

Those lacks lead our applications to be inconsistant, e.g the delete
confirmations actions in gallery or camera have there delete/don't
button vertically stacked, is that the correct way?

http://design.ubuntu.com/apps/getting-started/design-vision
http://design.ubuntu.com/apps/building-blocks/dialog
https://developer.ubuntu.com/api/qml/sdk-14.04/Ubuntu.Components.Popups.Dialog/

** Affects: ubuntu-brand-guidelines
 Importance: Undecided
 Status: New

** Affects: ubuntu-ux
 Importance: Undecided
 Status: New

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

** Also affects: ubuntu-brand-guidelines
   Importance: Undecided
   Status: New

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

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

Title:
  Guideline/documentation has no layout recommendation for buttons in
  dialogs

Status in Ubuntu Brand Guidelines:
  New
Status in Ubuntu UX bugs:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Reading the current documentation there is no real guidance on how to
  layout buttons in Dialogs.

  The design vision section 4. [1] mentions Positive actions always
  go on the right, negative on the left, which suggests an horizontal
  alignment for the buttons, but the building blocks section [2] doesn't
  mention the topic and the uitk defaults to stacking things vertically,
  including the API example [3], while the uitk-gallery example program
  does show an horizontal layout by stacking its button in a row (if
  that's recommended way, the API example should perhaps reflect that?)

  Those lacks lead our applications to be inconsistant, e.g the delete
  confirmations actions in gallery or camera have there delete/don't
  button vertically stacked, is that the correct way?

  http://design.ubuntu.com/apps/getting-started/design-vision
  http://design.ubuntu.com/apps/building-blocks/dialog
  
https://developer.ubuntu.com/api/qml/sdk-14.04/Ubuntu.Components.Popups.Dialog/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-brand-guidelines/+bug/1426471/+subscriptions

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

[Touch-packages] [Bug 1426467] [NEW] Indicator can fail to display panel icon

[Tony Espy]

Public bug reported:

current build number: 122
device name: krillin
channel: ubuntu-touch/devel-proposed

It's possible for the device to boot in such a manner that the network-
indicator doesn't display an icon on the top panel ( see attached
screenshot ).

I was testing a change to ofono ( currently in silo ubuntu-013 ) which
fixes a MTK-specific bug where the device boots and the 2nd SIM slot
isn't recognized.  So to test, I continually rebooted the device.  I
have two SIMs installed, the first unlocked, the second is locked.

In the case of the missing icon, no PIN unlock screen was displayed
after booting.

I checked using 'ps' and an indicator-network process is running,
however when I checked /home/phablet/.cache/upstart, there only
indicator-network log files I see are the saved .gz files.  There's no
unzipped/current indicator-network.log.  The .gz log file with the most
recent timestamp shows a single log message:

phablet@ubuntu-phablet:~/.cache/upstart$ less indicator-network.log.1.gz
void core::dbus::PropertyT::handle_changed(const core::dbus::types::Variant) 
[with PropertyType = 
org::freedesktop::URfkill::Interface::Killswitch::Property::State]: 
org.freedesktop.DBus.Error.UnknownMethod: Method Get with signature ss on 
interface org.freedesktop.DBus.Properties doesn't exist

I checked and urfkilld is running on the system.

I also verified that there were no crash files present on the system.

I also checked and there was nothing relevant in syslog.

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

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

Title:
  Indicator can fail to display panel icon

Status in indicator-network package in Ubuntu:
  New

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/devel-proposed

  It's possible for the device to boot in such a manner that the
  network-indicator doesn't display an icon on the top panel ( see
  attached screenshot ).

  I was testing a change to ofono ( currently in silo ubuntu-013 ) which
  fixes a MTK-specific bug where the device boots and the 2nd SIM slot
  isn't recognized.  So to test, I continually rebooted the device.  I
  have two SIMs installed, the first unlocked, the second is locked.

  In the case of the missing icon, no PIN unlock screen was displayed
  after booting.

  I checked using 'ps' and an indicator-network process is running,
  however when I checked /home/phablet/.cache/upstart, there only
  indicator-network log files I see are the saved .gz files.  There's no
  unzipped/current indicator-network.log.  The .gz log file with the
  most recent timestamp shows a single log message:

  phablet@ubuntu-phablet:~/.cache/upstart$ less indicator-network.log.1.gz
  void core::dbus::PropertyT::handle_changed(const 
core::dbus::types::Variant) [with PropertyType = 
org::freedesktop::URfkill::Interface::Killswitch::Property::State]: 
org.freedesktop.DBus.Error.UnknownMethod: Method Get with signature ss on 
interface org.freedesktop.DBus.Properties doesn't exist

  I checked and urfkilld is running on the system.

  I also verified that there were no crash files present on the system.

  I also checked and there was nothing relevant in syslog.

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

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

[Touch-packages] [Bug 1426058] Re: info dialog not displayed properly and can't be dismissed

[Launchpad Bug Tracker]

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

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

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

Title:
  info dialog not displayed properly and can't be dismissed

Status in Messaging App:
  New
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  vivid build 110 on mako

  - open messaging-app
  - open a message thread
  - swipe left
  - click the i button

  expected results:
  - dialog should appear centered on screen with message info with a 
close/dismiss button

  actual results:
  - dialog mostly offscreen and not rendered correctly with no way to close it

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

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

[Touch-packages] [Bug 1425987] Re: Cellular data connection stops after a while

[Jean-Baptiste Lallement]

I rebooted the device, it established a data connection (H symbol in the
indicator) then after less than 5 minutes it disconnected

$ nmcli d
DEVICE   TYPE  STATE CONNECTION 
ril_0gsm   disconnected  -- 
ril_1gsm   unavailable   -- 
ifb0 ifb   unmanaged -- 
ifb1 ifb   unmanaged -- 
lo   loopback  unmanaged -- 
ip6tnl0  unknown   unmanaged -- 
sit0 unknown   unmanaged -- 
tunl0unknown   unmanaged -- 
ccmni0   wifi  unmanaged -- 
ccmni1   wifi  unmanaged -- 
ccmni2   wifi  unmanaged -- 

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

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

Title:
  Cellular data connection stops after a while

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-02-25 15:06:29
  version version: 122
  version ubuntu: 20150225
  version device: 20150210-95b6a9f
  version custom: 20150225

  Test Case:
  1. Disable Wifi
  2. Verify that a cellular data connection is established
  3. Wait...

  Actual result
  After a while (several minutes) the cellular data connection stops, 
eventually it'll come back but not always.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Thu Feb 26 16:14:14 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2015-02-25 (1 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150225-020204)
  IpRoute:
   
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  PciNetwork:
   
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 
2015-02-25T03:31:54
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1426456] [NEW] Keyboard layout for Icelandic(Machintosh) is wrong

[Arnkell Logi Pétursson]

Public bug reported:

Hi,

Thank you for a great OS! I found a small bug that affects maybe 10
people in the world but I'm one of them :-)

I'm using the aluminum mac keyboard with an Icelandic layout.

1) I'm using Ubuntu 14.10
2) I'm not sure what package this applies to.
3) Third level selectors are more or less all wrong.
4) Wrong character appears

I've made an xmodmap file that fixes these issues and attached it.

with regards, Logi

** Affects: xkeyboard-config (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: Xmodmap that fixes these issues
   
https://bugs.launchpad.net/bugs/1426456/+attachment/4329547/+files/xmodmap.txt

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

Title:
  Keyboard layout for Icelandic(Machintosh) is wrong

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  Hi,

  Thank you for a great OS! I found a small bug that affects maybe 10
  people in the world but I'm one of them :-)

  I'm using the aluminum mac keyboard with an Icelandic layout.

  1) I'm using Ubuntu 14.10
  2) I'm not sure what package this applies to.
  3) Third level selectors are more or less all wrong.
  4) Wrong character appears

  I've made an xmodmap file that fixes these issues and attached it.

  with regards, Logi

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

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

[Touch-packages] [Bug 1400141] Re: Swiping quickly through photo roll causes photo to zoom

[Pat McGowan]

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

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

** Changed in: canonical-devices-system-image
Milestone: ww09-2015 = ww13-ota

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

Title:
  Swiping quickly through photo roll causes photo to zoom

Status in Camera App:
  Fix Released
Status in the base for Ubuntu mobile products:
  Fix Released
Status in Gallery App:
  In Progress
Status in camera-app package in Ubuntu:
  Fix Released
Status in gallery-app package in Ubuntu:
  Fix Released

Bug description:
  Prerequisites
  * Have multiple photos in your photo roll

  What happened:
  * When swiping through the photo roll quickly, it zoomed in rather than 
moving onto the next photo

  Steps:
  1) Open camera app and switch to the photo roll
  2) Ensure the photo roll is single image rather than grid mode
  3) Quickly swipe left to go to the next photo
  4) Repeat the swiping going to the next photo etc until when you swipe it 
thinks you double tapped and therefore zooms into the photo rather than moving 
onto the next

  What was expected:
  * When swiping for the app to always move onto the next photo

  It appears that the swipe event should accept the mouse or the double
  tap event should not be activated if the user has swiped?

  $ system-image-cli -i
  current build number: 144
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/devel-proposed
  alias: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-12-05 04:21:47
  version version: 144
  version ubuntu: 20141205
  version device: 20141119
  version custom: mako-1.1

  $ click list | grep camera
  com.ubuntu.camera 3.0.0.412

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

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

[Touch-packages] [Bug 1426455] [NEW] Keyboard layout for Icelandic(Machintosh) is wrong

[Arnkell Logi Pétursson]

Public bug reported:

Hi,

Thank you for a great OS! I found a small bug that affects maybe 10
people in the world but I'm one of them :-)

I'm using the aluminum mac keyboard with an Icelandic layout.

1) I'm using Ubuntu 14.10
2) I'm not sure what package this applies to.
3) Third level selectors are more or less all wrong.
4) Wrong character appears

I've made an xmodmap file that fixes these issues and attached it.

with regards, Logi

** Affects: xkeyboard-config (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: Xmodmap that fixes these issues
   
https://bugs.launchpad.net/bugs/1426455/+attachment/4329546/+files/xmodmap.txt

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

Title:
  Keyboard layout for Icelandic(Machintosh) is wrong

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  Hi,

  Thank you for a great OS! I found a small bug that affects maybe 10
  people in the world but I'm one of them :-)

  I'm using the aluminum mac keyboard with an Icelandic layout.

  1) I'm using Ubuntu 14.10
  2) I'm not sure what package this applies to.
  3) Third level selectors are more or less all wrong.
  4) Wrong character appears

  I've made an xmodmap file that fixes these issues and attached it.

  with regards, Logi

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

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

[Touch-packages] [Bug 1368787] Re: [camera]+[gallery] Photo roll doesn't have photo editing

[Pat McGowan]

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

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

** Changed in: canonical-devices-system-image
Milestone: ww09-2015 = ww13-ota

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

Title:
  [camera]+[gallery] Photo roll doesn't have photo editing

Status in Camera App:
  In Progress
Status in the base for Ubuntu mobile products:
  Fix Released
Status in Ubuntu UX bugs:
  In Progress
Status in camera-app package in Ubuntu:
  Fix Released
Status in ubuntu-ui-extras package in Ubuntu:
  Fix Released

Bug description:
  All participants (who managed to located the picture on the photo
  roll) expected to be able to edit directly from the photo roll view.
  Without this functionality, they had go to Gallery to refind the
  picture and carry out edit. Three participants failed as they did not
  go the Gallery. 

  Camera app does not currently offer editing capability of photos.
  Investigate whether we can add some basic editing options

  -- UX SOLUTION --
  We need to align the gallery app UX first

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

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

[Touch-packages] [Bug 1408263] Re: Edge gestures still get lost (mako)

[Charles Kerr]

This occurs for me about once a day, so I'm happy to act as a patch
tester or any other way I can help...

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

Title:
  Edge gestures still get lost (mako)

Status in android package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  There are still cases where edge gestures are lost. Over the christmas
  holidays It happened about 5 times to me (in 2 weeks). Only way to
  recover is to reboot the phone. It always happened while the phone was
  in my pocket. When pulling it out of the pocket the edge gestures
  (launcher and right edge) were gone. This is most likely related to
  random taps on the screen, maybe in combination with the display
  toggling on/off.

  Haven't found a way yet to manually trigger it. Will keep on trying.

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

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

[Touch-packages] [Bug 1424117] Re: package cups-daemon 1.7.5-3ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package cups-daemon 1.7.5-3ubuntu3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.10

  package cups-daemon 1.7.5-3ubuntu3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: cups-daemon 1.7.5-3ubuntu3
  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
  CupsErrorLog:
   
  Date: Fri Feb 20 21:19:27 2015
  DuplicateSignature: package:cups-daemon:1.7.5-3ubuntu3:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-01-07 (44 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: LENOVO Lenovo IdeaPad Y580
  Papersize: a4
  PpdFiles:
   Brother-HL-2170W: Brother HL-2170W Foomatic/lj4dith
   Brother-HL-2170W-series: Brother HL-2170W Foomatic/hl1250
   Hewlett-Packard-HP-LaserJet-1020: HP LaserJet 1020 Foomatic/foo2zjs-z1 
(recommended)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=5f67b03e-c274-4953-b487-b67be9d10ae7 ro quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=5f67b03e-c274-4953-b487-b67be9d10ae7 ro quiet splash
  SourcePackage: cups
  Title: package cups-daemon 1.7.5-3ubuntu3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/10/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5DCN40WW(V2.07)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Mainboard version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5DCN40WW(V2.07):bd10/10/2012:svnLENOVO:pnLenovoIdeaPadY580:pvrLenovoIdeaPadY580:rvnLENOVO:rnProductName:rvrMainboardversion:cvnLENOVO:ct10:cvrLenovoIdeaPadY580:
  dmi.product.name: Lenovo IdeaPad Y580
  dmi.product.version: Lenovo IdeaPad Y580
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1418642] Re: GDB hangs at thread join function on Ubuntu 14.10 LE Power

[Thierry FAUCK]

Also verified uner utopic gcc version 4.9.1

$ vi s1.cpp
$ g++ s1.cpp -g -std=c++11 -fgnu-tm -lpthread -D D_STM
$ ./a.out
a=400 b=800 c=1200
ubuntu@fauck4:~$ gdb ./a.out
GNU gdb (Ubuntu 7.8-0ubuntu2) 7.8.0.20141001-cvs
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as powerpc64le-linux-gnu.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type help.
Type apropos word to search for commands related to word...
Reading symbols from ./a.out...done.
(gdb) run
Starting program: /home/ubuntu/a.out 
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/powerpc64le-linux-gnu/libthread_db.so.1.
[New Thread 0x3fffb72bf170 (LWP 15611)]
[New Thread 0x3fffb6abf170 (LWP 15612)]
[New Thread 0x3fffb62bf170 (LWP 15613)]
[New Thread 0x3fffb56af170 (LWP 15614)]
[Thread 0x3fffb6abf170 (LWP 15612) exited]
[Thread 0x3fffb72bf170 (LWP 15611) exited]
[Thread 0x3fffb56af170 (LWP 15614) exited]
a=400 b=800 c=1200
[Thread 0x3fffb62bf170 (LWP 15613) exited]
[Inferior 1 (process 15608) exited normally]

$ gcc --version
gcc (Ubuntu 4.9.1-16ubuntu6) 4.9.1
ubuntu@fauck4:~$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.10
DISTRIB_CODENAME=utopic
DISTRIB_DESCRIPTION=Ubuntu 14.10
$ uname -a
Linux fauck4 3.16.0-20-generic #27-Ubuntu SMP Wed Oct 1 17:24:38 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux

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

Title:
  GDB hangs at thread join function on Ubuntu 14.10 LE Power

Status in gdb package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  GDB hangs at thread join function while trying to debug STM (software 
transacational memory) code.

  ---uname output---
  Linux lep8aVM1 3.16.0-7-generic #12-Ubuntu SMP Sat Aug 9 05:05:32 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Power 8 

  ---Steps to Reproduce---

  Compile:
  -
  g++ s1.cpp -g -std=c++11 -fgnu-tm -lpthread -D D_STM

  sample source: s1.cpp
  ---
  root@lep8aVM1:~/p# cat s1.cpp
  #include iostream
  #include thread

  static const auto THR_NUM = 4;
  static const auto ITER_NUM = 1000 * 1000;

  static auto a = 0, b = 0, c = 0;

  static void thr_func()
  {
  for (auto i = 0; i  ITER_NUM; ++i)
  #ifdef D_STM
   __transaction_atomic {
  ++a;
  b += 2;
  c = a + b;
  }
  #else
  ++a;
  b += 2;
  c = a + b;
  #endif
  }

  
  int main(int argc, char *argv[])
  {
std::thread thr[THR_NUM];

for (auto t : thr)
t = std::thread(thr_func);

for (auto t : thr)
t.join();

  std::cout  a=  a   b=  b   c=  c 
  std::endl;

return 0;
  }

  Debug a.out using gdb:
  
  root@lep8aVM1:~/p# gdb ./a.out 
  GNU gdb (Ubuntu 7.8-0ubuntu1) 7.8
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type show copying
  and show warranty for details.
  This GDB was configured as powerpc64le-linux-gnu.
  Type show configuration for configuration details.
  For bug reporting instructions, please see:
  http://www.gnu.org/software/gdb/bugs/.
  Find the GDB manual and other documentation resources online at:
  http://www.gnu.org/software/gdb/documentation/.
  For help, type help.
  Type apropos word to search for commands related to word...
  Reading symbols from ./a.out...done.
  (gdb) run
  Starting program: /root/p/a.out 
  Can't read symbols from system-supplied DSO at 0x3fffb7fa: File truncated
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library 
/lib/powerpc64le-linux-gnu/libthread_db.so.1.

  Breakpoint 1, main (argc=1, argv=0x36b8) at s1.cpp:27
  27{
  (gdb) list
  22#endif
  23}
  24
  25
  26int main(int argc, char *argv[])
  27{
  28std::thread thr[THR_NUM];
  29
  30for (auto t : thr)
  31t = std::thread(thr_func);
  (gdb) n
  28std::thread thr[THR_NUM];
  (gdb) n
  30for (auto t : thr)
  (gdb) n
  

[Touch-packages] [Bug 1418642] Re: GDB hangs at thread join function on Ubuntu 14.10 LE Power

[Thierry FAUCK]

Verfied in 14.04.2

g++ s1.cpp -g -std=c++11 -fgnu-tm -lpthread -D D_STM
$ ./a.out
a=400 b=800 c=1200

$ gdb ./a.out
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as powerpc64le-linux-gnu.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type help.
Type apropos word to search for commands related to word...
Reading symbols from ./a.out...done.
(gdb) run
Starting program: /home/ubuntu/a.out 
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/powerpc64le-linux-gnu/libthread_db.so.1.
[New Thread 0x3fffb72cf170 (LWP 66956)]
[New Thread 0x3fffb6acf170 (LWP 66957)]
[New Thread 0x3fffb62cf170 (LWP 66958)]
[New Thread 0x3fffb56bf170 (LWP 66959)]
[Thread 0x3fffb72cf170 (LWP 66956) exited]
[Thread 0x3fffb6acf170 (LWP 66957) exited]
[Thread 0x3fffb62cf170 (LWP 66958) exited]
[Thread 0x3fffb56bf170 (LWP 66959) exited]
a=400 b=800 c=1200
[Inferior 1 (process 66953) exited normally]

$ uname -a
Linux fauck3 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:50:31 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
ubuntu@fauck3:~$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION=Ubuntu 14.04.2 LTS

$ gcc --version
gcc-4.8.real (Ubuntu 4.8.2-19ubuntu1) 4.8.2

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

Title:
  GDB hangs at thread join function on Ubuntu 14.10 LE Power

Status in gdb package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  GDB hangs at thread join function while trying to debug STM (software 
transacational memory) code.

  ---uname output---
  Linux lep8aVM1 3.16.0-7-generic #12-Ubuntu SMP Sat Aug 9 05:05:32 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Power 8 

  ---Steps to Reproduce---

  Compile:
  -
  g++ s1.cpp -g -std=c++11 -fgnu-tm -lpthread -D D_STM

  sample source: s1.cpp
  ---
  root@lep8aVM1:~/p# cat s1.cpp
  #include iostream
  #include thread

  static const auto THR_NUM = 4;
  static const auto ITER_NUM = 1000 * 1000;

  static auto a = 0, b = 0, c = 0;

  static void thr_func()
  {
  for (auto i = 0; i  ITER_NUM; ++i)
  #ifdef D_STM
   __transaction_atomic {
  ++a;
  b += 2;
  c = a + b;
  }
  #else
  ++a;
  b += 2;
  c = a + b;
  #endif
  }

  
  int main(int argc, char *argv[])
  {
std::thread thr[THR_NUM];

for (auto t : thr)
t = std::thread(thr_func);

for (auto t : thr)
t.join();

  std::cout  a=  a   b=  b   c=  c 
  std::endl;

return 0;
  }

  Debug a.out using gdb:
  
  root@lep8aVM1:~/p# gdb ./a.out 
  GNU gdb (Ubuntu 7.8-0ubuntu1) 7.8
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type show copying
  and show warranty for details.
  This GDB was configured as powerpc64le-linux-gnu.
  Type show configuration for configuration details.
  For bug reporting instructions, please see:
  http://www.gnu.org/software/gdb/bugs/.
  Find the GDB manual and other documentation resources online at:
  http://www.gnu.org/software/gdb/documentation/.
  For help, type help.
  Type apropos word to search for commands related to word...
  Reading symbols from ./a.out...done.
  (gdb) run
  Starting program: /root/p/a.out 
  Can't read symbols from system-supplied DSO at 0x3fffb7fa: File truncated
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library 
/lib/powerpc64le-linux-gnu/libthread_db.so.1.

  Breakpoint 1, main (argc=1, argv=0x36b8) at s1.cpp:27
  27{
  (gdb) list
  22#endif
  23}
  24
  25
  26int main(int argc, char *argv[])
  27{
  28std::thread thr[THR_NUM];
  29
  30for (auto t : thr)
  31t = std::thread(thr_func);
  (gdb) n
  28std::thread thr[THR_NUM];
  (gdb) n
  30for (auto t : thr)
  (gdb) n
  31t = 

[Touch-packages] [Bug 1291359] Re: multiscreen spanning wallpaper does not span on lock screen

[Sullivan Senechal]

Same problem on Ubuntu 14.10.

Any news about a fix?

Thanks.

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

Title:
  multiscreen spanning wallpaper does not span on lock screen

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  (It has same look as unity-greeter in lightdm but am given to believe
  lock screen is handled by gnome-screensaver; move if i'm wrong!
  lightdm seems to get it wrong a different way.)

  If, having made a wide wallpaper to span multiple monitors, and having
  set it as your wallpaper with type Span in Appearance settings, you
  then go to the new Lock screen...

  ... you will see that instead of that wide wallpaper spanning all
  monitors, you get the image scaled down to be shown whole on *each*
  monitor. As shown in screenshot attached.

  It needs to honour the appearance settings in this regard.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screensaver 3.6.1-0ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 12 13:02:42 2014
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 300
  InstallationDate: Installed on 2014-03-08 (3 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to trusty on 2014-03-10 (1 days ago)

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

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

[Touch-packages] [Bug 1425067] Re: package ca-certificates 20141019ubuntu0.10.04.1 failed to install/upgrade: cannot access archive: No such file or directory

[Marc Deslauriers]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package ca-certificates 20141019ubuntu0.10.04.1 failed to
  install/upgrade: cannot access archive: No such file or directory

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  From uname -a:

  Linux madmod-laptop 2.6.32-60-generic #122-Ubuntu SMP Wed May 7
  20:16:42 UTC 2014 i686 GNU/Linux

  I'm using Ubuntu 10.04 Desktop on this computer.  The update manager 
presented a text page with the certificates change log.
  The only option for the page was Close which I used.  (On my 14.04 Desktop, 
the change log appears in the command screen and I usually just type q to 
bypass it so that the updates can continue.)

  After I clicked on the Close button, the screen didn't close but went
  gray as if it was busy or low on memory.  Meanwhile, on the command
  screen, the update hung with messages such as apt-changelog ... with
  some options.  But this just hung.  I don't think that this utility
  apt-changelog is in my computer as there is no man page for it.
  (probably not in the 10.04 Ubuntu)

  Finally I used the force quit to kill the text page and the command
  screen.  The update manager continued to a normal stop without
  completing the tasks.  I then rebooted the computer and gave the
  command sudo apt-get autoremove to clear whatever junk had piled up.
  It was clean.

  Another attempt at using the update manager failed the same way.  I
  then rebooted, reissued autoremove and got the other updates--
  bypassing the certificate update.  That set of updates installed
  normally and the update manager indicated that I still had
  certificates to go.  At this point I don't remember what happened
  except that the certificates update failed and hung up the same way.
  So I aborted and used autoremove again.

  Otherwise the 10.04 computer is behaving normally.

  Hope that's useful enough info.

  --Dave

  ProblemType: Package
  DistroRelease: Ubuntu 10.04
  Package: ca-certificates 20141019ubuntu0.10.04.1
  ProcVersionSignature: Ubuntu 2.6.32-60.122-generic 2.6.32.61+drm33.26
  Uname: Linux 2.6.32-60-generic i686
  AptOrdering:
   ca-certificates: Install
   ca-certificates: Configure
  Architecture: i386
  Date: Tue Feb 24 07:24:51 2015
  ErrorMessage: cannot access archive: No such file or directory
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  PackageArchitecture: all
  SourcePackage: ca-certificates
  Title: package ca-certificates 20141019ubuntu0.10.04.1 failed to 
install/upgrade: cannot access archive: No such file or directory

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

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

[Touch-packages] [Bug 1426361] Re: Alarms API should expose a unique permanent alarm ID that clock app can use to open an alarm

[Zsombor Egri]

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

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

Title:
  Alarms API should expose a unique permanent alarm ID that clock app
  can use to open an alarm

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

Bug description:
  Alarms API should expose a unique permanent alarm ID that clock app
  can use to open an alarm instead of just the alarm index that varies
  based on the alarm date dynamically.

  Use Case: Bug 1387210 Indicator-datetime will pass the
  QOrganizerItemId (unique alarm ID) to clock app when the user clicks
  on an alarm in the indicator-datetime. But the current Alarms API does
  not allow clock app to open the alarm using that unique ID which
  results in clock app not knowing which alarm to show to the user.

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

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

[Touch-packages] [Bug 1426361] Re: Alarms API should expose a unique permanent alarm ID that clock app can use to open an alarm

[Launchpad Bug Tracker]

** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/expose-alarm-id

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

Title:
  Alarms API should expose a unique permanent alarm ID that clock app
  can use to open an alarm

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

Bug description:
  Alarms API should expose a unique permanent alarm ID that clock app
  can use to open an alarm instead of just the alarm index that varies
  based on the alarm date dynamically.

  Use Case: Bug 1387210 Indicator-datetime will pass the
  QOrganizerItemId (unique alarm ID) to clock app when the user clicks
  on an alarm in the indicator-datetime. But the current Alarms API does
  not allow clock app to open the alarm using that unique ID which
  results in clock app not knowing which alarm to show to the user.

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

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

[Touch-packages] [Bug 1426366] [NEW] Dialer keypad in emergency mode when dialed over Bluetooth

[Michał Sawicz]

Public bug reported:

Steps:
* connect to a Bluetooth set with a keypad (like a car set)
* use the keypad to dial a number

Expected:
* in-call dialer is shown with the contact details

Current:
* dialer keypad is shown with Emergency in the header

ProblemType: Bug
DistroRelease: Ubuntu RTM 14.09
Package: dialer-app 0.1+15.04.20150216~rtm-0ubuntu1
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.7-0ubuntu8
Architecture: armhf
Date: Fri Feb 27 14:18:35 2015
InstallationDate: Installed on 2015-02-19 (7 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150219-205423)
SourcePackage: dialer-app
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug armhf utopic

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

Title:
  Dialer keypad in emergency mode when dialed over Bluetooth

Status in dialer-app package in Ubuntu:
  New

Bug description:
  Steps:
  * connect to a Bluetooth set with a keypad (like a car set)
  * use the keypad to dial a number

  Expected:
  * in-call dialer is shown with the contact details

  Current:
  * dialer keypad is shown with Emergency in the header

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: dialer-app 0.1+15.04.20150216~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Fri Feb 27 14:18:35 2015
  InstallationDate: Installed on 2015-02-19 (7 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150219-205423)
  SourcePackage: dialer-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Launchpad Bug Tracker]

This bug was fixed in the package android-tools -
4.2.2+git20130218-3ubuntu40

---
android-tools (4.2.2+git20130218-3ubuntu40) vivid; urgency=medium

  * add check for screen locking to adbd (LP: #1382559)
 -- Oliver Grawert o...@ubuntu.com   Fri, 27 Feb 2015 11:59:19 +0100

** Changed in: android-tools (Ubuntu)
   Status: In Progress = Fix Released

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

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

Status in the base for Ubuntu mobile products:
  Fix Released
Status in android-tools package in Ubuntu:
  Fix Released
Status in android-tools package in Ubuntu RTM:
  Fix Released

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

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

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

[Touch-packages] [Bug 131523] Re: evince chooses wrong font substitutes

[scruss]

Still present in Ubuntu 14.10. Evince is substituting vastly incorrect
fonts. DejaVu-Serif for Times-Roman is forgivable through ignorance, but
Liberation Sans for ZapfDingbats is in “what is this I don't even”
country.

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

Title:
  evince chooses wrong font substitutes

Status in Poppler:
  Fix Released
Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: evince

  view
  http://www.publications.parliament.uk/pa/ld/lduncorr/stii210207a.pdf
  with evince in current gutsy without having Times NewRoman and Arial
  fonts installed. The metric incompatible DejaVu fonts are choosen,
  instead of metric compatible ones. This is a regression.

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

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

[Touch-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors

[Martin Wimpress]

** Changed in: mate-control-center (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  Changing external screen resolution with dual monitors

Status in GTK+ GUI Toolkit:
  Fix Released
Status in Ubuntu MATE:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in mate-control-center package in Ubuntu:
  Fix Released
Status in gtk+2.0 package in Debian:
  Confirmed

Bug description:
  Changing extrnal screen resolution with dual mon

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: mate-control-center 1.8.1+dfsg1-4
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic i686
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: i386
  CrashCounter: 1
  Date: Sun Aug  3 07:09:21 2014
  ExecutablePath: /usr/bin/mate-display-properties
  InstallationDate: Installed on 2014-08-03 (0 days ago)
  InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731)
  ProcCmdline: mate-display-properties
  SegvAnalysis: Skipped: missing required field Disassembly
  Signal: 11
  SourcePackage: mate-control-center
  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/gtk/+bug/1351890/+subscriptions

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

[Touch-packages] [Bug 1425676] Re: I don't know.

[Marc Deslauriers]

Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System - 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!


** Information type changed from Private Security to Public

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

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

Title:
  I don't know.

Status in indicator-sound package in Ubuntu:
  Invalid

Bug description:
  I don't know.

  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: Thu Feb 26 03:09:57 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha amd64 (20150224)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  Signal: 5
  SourcePackage: indicator-sound
  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/1425676/+subscriptions

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

[Touch-packages] [Bug 1424312] Re: compiz crashed with SIGSEGV in unity::XdndStartStopNotifierImp::DndTimeoutSetup()

[Marc Deslauriers]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  compiz crashed with SIGSEGV in
  unity::XdndStartStopNotifierImp::DndTimeoutSetup()

Status in unity package in Ubuntu:
  New

Bug description:
  problems with unity

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150219.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: fglrx wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Sat Feb 21 22:08:10 2015
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2015-02-21 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  ProcCmdline: compiz
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   unity::XdndStartStopNotifierImp::DndTimeoutSetup() () from 
/usr/lib/compiz/libunityshell.so
   sigc::internal::signal_emit1void, unsigned long, 
sigc::nil::emit(sigc::internal::signal_impl*, unsigned long const) () from 
/usr/lib/compiz/libunityshell.so
   unity::PluginAdapter::Notify(CompWindow*, CompWindowNotify) () from 
/usr/lib/compiz/libunityshell.so
   unity::UnityWindow::windowNotify(CompWindowNotify) () from 
/usr/lib/compiz/libunityshell.so
   CompWindow::windowNotify(CompWindowNotify) () from 
/usr/lib/x86_64-linux-gnu/libcompiz_core.so.ABI-20140123
  Title: compiz crashed with SIGSEGV in 
unity::XdndStartStopNotifierImp::DndTimeoutSetup()
  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/unity/+bug/1424312/+subscriptions

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

[Touch-packages] [Bug 1426361] Re: Alarms API should expose a unique permanent alarm ID that clock app can use to open an alarm

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New = Confirmed

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided = High

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) = Zsombor Egri (zsombi)

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

Title:
  Alarms API should expose a unique permanent alarm ID that clock app
  can use to open an alarm

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

Bug description:
  Alarms API should expose a unique permanent alarm ID that clock app
  can use to open an alarm instead of just the alarm index that varies
  based on the alarm date dynamically.

  Use Case: Bug 1387210 Indicator-datetime will pass the
  QOrganizerItemId (unique alarm ID) to clock app when the user clicks
  on an alarm in the indicator-datetime. But the current Alarms API does
  not allow clock app to open the alarm using that unique ID which
  results in clock app not knowing which alarm to show to the user.

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

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

[Touch-packages] [Bug 1426275] Re: i dont know exactly

[Marc Deslauriers]

Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System - 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!


** Information type changed from Private Security to Public

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

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

Title:
  i dont know exactly

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  my vga card dont worksaround

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Feb 27 16:04:12 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fa41]
  InstallationDate: Installed on 2014-12-04 (85 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  MachineType: TOSHIBA Satellite S55-A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=9285322c-558d-489a-8a2d-6df072507cb9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VG10F
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  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.70:bd04/22/2014:svnTOSHIBA:pnSatelliteS55-A:pvrPSKJJU-018009B:rvnIntel:rnVG10F:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite S55-A
  dmi.product.version: PSKJJU-018009B
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  version.libdrm2: libdrm2 2.4.56-1~ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  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.4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Feb 27 14:09:24 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17477 
   vendor SDC
  xserver.version: 2:1.15.1-0ubuntu2.6

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

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

[Touch-packages] [Bug 1366876] Re: Xorg freeze

[James Ferguson]

... well, I would post an attachment, if Launchpad didn't appear to
crash out on my when I do (Chrome or Firefox browsers.  I'll preserve
the crash dump and try again later.  Meanwhile, below is what's in
syslog for the crash, and:

sudo dmidecode -s bios-version
G2ETA3WW (2.63 )



Feb 27 08:14:58 jferguson-01 kernel: [  603.032698] Watchdog[2620]: segfault at 
0 ip 7f3aee5547b6 sp 7f3adddef770 error 6 in 
chrome[7f3aea865000+510d000]
Feb 27 08:15:01 jferguson-01 CRON[4765]: (root) CMD (command -v debian-sa1  
/dev/null  debian-sa1 1 1)
Feb 27 08:15:15 jferguson-01 kernel: [  620.626713] Watchdog[4769]: segfault at 
0 ip 7fb5967347b6 sp 7fb585fcf770 error 6 in 
chrome[7fb592a45000+510d000]
Feb 27 08:15:24 jferguson-01 kernel: [  629.521811] [drm] stuck on render ring
Feb 27 08:15:24 jferguson-01 kernel: [  629.521820] [drm] GPU crash dump saved 
to /sys/class/drm/card0/error
Feb 27 08:15:24 jferguson-01 kernel: [  629.521821] [drm] GPU hangs can 
indicate a bug anywhere in the entire gfx stack, including userspace.
Feb 27 08:15:24 jferguson-01 kernel: [  629.521822] [drm] Please file a _new_ 
bug report on bugs.freedesktop.org against DRI - DRM/Intel
Feb 27 08:15:24 jferguson-01 kernel: [  629.521823] [drm] drm/i915 developers 
can then reassign to the right component if it's not a kernel issue.
Feb 27 08:15:24 jferguson-01 kernel: [  629.521824] [drm] The gpu crash dump is 
required to analyze gpu hangs, so please always attach it.

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Desktop display freezes temporarily, for (approx) 20s or so, approx
  once a day, with mouse pointer still working.  After that it comes
  back and resumes as normal, seemingly replaying mouse and keyboard
  events from the meantime.  I think it's always happened when using
  Google Chrome (Stable - currently 37.0.2062.94, but I think other
  recent versions).  The desktop is completely unresponsive

  This didn't seem to happen until a few weeks ago.  I tend to pull
  updates fairly regularly.

  In syslog there is:

  kernel: [277415.130771] [drm] stuck on render ring

  I suspect this is a dupe since I see other related bugs, but you'd be
  better placed to decide that than I.

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

  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,place,grid,vpswitch,gnomecompat,mousepoll,session,move,obs,imgpng,snap,regex,animation,expo,ezoom,staticswitcher,workarounds,wall,fade,scale]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Sep  8 12:22:27 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: comedi-adv-pci1724, 0.0.1: added
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:21fa]
  InstallationDate: Installed on 2014-07-11 (59 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=561b4b77-cac6-4abb-a89e-ecf7f1bb8f42 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET82WW (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET82WW(2.02):bd09/11/2012:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  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: 

Re: [Touch-packages] [Bug 1425067] Re: package ca-certificates 20141019ubuntu0.10.04.1 failed to install/upgrade: cannot access archive: No such file or directory

[David Mawdsley]

Hi Marc,

Not to split hairs on this, but I checked the security option because
this patch dealt with certificates which do have security implications
to a limited extent.  I'm always cautious when doing business with
companies whose certs are wrong.  (no use of credit cards, nor transfer
of personal info)

Anyway, thanks for the update.

~Dave

On 02/27/2015 08:10 AM, Marc Deslauriers wrote:
 Thanks for taking the time to report this bug and helping to make Ubuntu
 better. We appreciate the difficulties you are facing, but this appears
 to be a regular (non-security) bug.  I have unmarked it as a security
 issue since this bug does not show evidence of allowing attackers to
 cross privilege boundaries nor directly cause loss of data/privacy.
 Please feel free to report any other bugs you may find.

 ** Information type changed from Private Security to Public


-- 
David Mawdsley - A+, Network+ and Security+ Certified Service Technician
Visit MadMod Computing (madmod.com) for free newsletters or to use the 
appointment calendar. [Microsoft Windows is okay to use, but the Linux 
distribution called Ubuntu makes for a lot nicer computing experience!]

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

Title:
  package ca-certificates 20141019ubuntu0.10.04.1 failed to
  install/upgrade: cannot access archive: No such file or directory

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  From uname -a:

  Linux madmod-laptop 2.6.32-60-generic #122-Ubuntu SMP Wed May 7
  20:16:42 UTC 2014 i686 GNU/Linux

  I'm using Ubuntu 10.04 Desktop on this computer.  The update manager 
presented a text page with the certificates change log.
  The only option for the page was Close which I used.  (On my 14.04 Desktop, 
the change log appears in the command screen and I usually just type q to 
bypass it so that the updates can continue.)

  After I clicked on the Close button, the screen didn't close but went
  gray as if it was busy or low on memory.  Meanwhile, on the command
  screen, the update hung with messages such as apt-changelog ... with
  some options.  But this just hung.  I don't think that this utility
  apt-changelog is in my computer as there is no man page for it.
  (probably not in the 10.04 Ubuntu)

  Finally I used the force quit to kill the text page and the command
  screen.  The update manager continued to a normal stop without
  completing the tasks.  I then rebooted the computer and gave the
  command sudo apt-get autoremove to clear whatever junk had piled up.
  It was clean.

  Another attempt at using the update manager failed the same way.  I
  then rebooted, reissued autoremove and got the other updates--
  bypassing the certificate update.  That set of updates installed
  normally and the update manager indicated that I still had
  certificates to go.  At this point I don't remember what happened
  except that the certificates update failed and hung up the same way.
  So I aborted and used autoremove again.

  Otherwise the 10.04 computer is behaving normally.

  Hope that's useful enough info.

  --Dave

  ProblemType: Package
  DistroRelease: Ubuntu 10.04
  Package: ca-certificates 20141019ubuntu0.10.04.1
  ProcVersionSignature: Ubuntu 2.6.32-60.122-generic 2.6.32.61+drm33.26
  Uname: Linux 2.6.32-60-generic i686
  AptOrdering:
   ca-certificates: Install
   ca-certificates: Configure
  Architecture: i386
  Date: Tue Feb 24 07:24:51 2015
  ErrorMessage: cannot access archive: No such file or directory
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  PackageArchitecture: all
  SourcePackage: ca-certificates
  Title: package ca-certificates 20141019ubuntu0.10.04.1 failed to 
install/upgrade: cannot access archive: No such file or directory

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

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

[Touch-packages] [Bug 1364568] Re: Feature: Option to have the alarm get louder as time goes on.

[Nekhelesh Ramananthan]

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

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

Title:
  Feature: Option to have the alarm get louder as time goes on.

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

Bug description:
  I know a lot of alarms start off quiet, and gradually get louder as
  time goes on. Might be a nice feature. The only con of this is feature
  creep.

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

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

[Touch-packages] [Bug 1426388] [NEW] Move a set of apps and scopes to the custom tarball

[Pat McGowan]

Public bug reported:

Certain apps and scopes will be substituted depending on the target
market and other customizations.

music, video click scopes
other tbd

** Affects: ubuntu-touch-meta (Ubuntu)
 Importance: High
 Assignee: Canonical Phone Foundations (canonical-phonedations-team)
 Status: New

** Summary changed:

- Move a set of apps and scopes to the custom tarbal
+ Move a set of apps and scopes to the custom tarball

** Changed in: ubuntu-touch-meta (Ubuntu)
 Assignee: (unassigned) = Canonical Phone Foundations 
(canonical-phonedations-team)

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

Title:
  Move a set of apps and scopes to the custom tarball

Status in ubuntu-touch-meta package in Ubuntu:
  New

Bug description:
  Certain apps and scopes will be substituted depending on the target
  market and other customizations.

  music, video click scopes
  other tbd

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

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

[Touch-packages] [Bug 1426399] [NEW] Sheel freezes for a short time when pressing the Play key on a connected BT keyboard

[Niklas Wenzel]

Public bug reported:

How to reproduce:

1) Connect a bluetooth keyboard to your Nexus 4.
2) Press the Play key on the keyboard.

What happens:

Unity8 freezes for some seconds.


phablet@ubuntu-phablet:~$ system-image-cli --info
current build number: 114
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-02-27 15:25:45
version version: 114
version ubuntu: 20150227.1
version device: 20150210
version custom: 20150227.1

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

Title:
  Sheel freezes for a short time when pressing the Play key on a
  connected BT keyboard

Status in unity8 package in Ubuntu:
  New

Bug description:
  How to reproduce:

  1) Connect a bluetooth keyboard to your Nexus 4.
  2) Press the Play key on the keyboard.

  What happens:

  Unity8 freezes for some seconds.

  
  phablet@ubuntu-phablet:~$ system-image-cli --info
  current build number: 114
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-02-27 15:25:45
  version version: 114
  version ubuntu: 20150227.1
  version device: 20150210
  version custom: 20150227.1

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

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

[Touch-packages] [Bug 1415958] Re: Laptop + external display does not suspend on lid close

[Christopher M. Penalver]

Colin law, thank you for reporting this and helping make Ubuntu better.
As per http://support.ts.fujitsu.com/Download/ShowFiles.asp an update to
your computer's buggy and outdated BIOS is available (1.18). 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.18

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

Title:
  Laptop + external display does not suspend on lid close

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Running up to date Vivid on laptop with external display, closing the
  lid does not suspend even though suspend is selected in the power
  settings for lid close.  The display flashes and apps move to external
  display.  Syslog shows no attempt to suspend.

  With no external display connected the laptop suspends as expected.

  In the logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30
  There are messages of the form
  i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment
  in syslog at that time but I suspect they may be a different issue.

  Not sure whether xorg is the correct package for this, hopefully
  someone will redirect if appropriate.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 15:04:52 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2014-12-27 (33 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  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: Thu Jan 29 15:00:08 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890 
   vendor SEC
  xserver.version: 2:1.16.2.901-1ubuntu3

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

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

[Touch-packages] [Bug 1423867] Re: init=/lib/systemd/systemd-bootchart on 219 triggers a kernel panic on kvm

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 219-4ubuntu1

---
systemd (219-4ubuntu1) vivid; urgency=medium

  * Merge with Debian experimental. Remaining Ubuntu changes:
- Hack to support system-image read-only /etc, and modify files in
  /etc/writable/ instead.
- Keep our much simpler udev maintainer scripts (all platforms must
  support udev, no debconf).
- initramfs init-top: Drop $ROOTDELAY, we do that in a more sensible way
  with wait-for-root. Will get applicable to Debian once Debian gets
  wait-for-root in initramfs-tools.
- initramfs init-bottom: If LVM is installed, settle udev,
  otherwise we get missing LV symlinks. Workaround for LP #1185394.
- Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv
  dependencies to lvm2 which is handled with udev rules in Ubuntu.
- Provide shutdown fallback for upstart. (LP: #1370329)
- debian/extra/ifup@.service: Additionally run for auto class. We don't
  really support allow-hotplug in Ubuntu at the moment, so we need to
  deal with auto devices appearing after /etc/init.d/networking start
  already ran. (LP: #1374521) Also, check if devices are actually defined
  in /etc/network/interfaces as we don't use Debian's net.agent.
- ifup@.service: Drop dependency on networking.service (i. e.
  /etc/init.d/networking), and merely ensure that /run/network exists.
  This avoids unnecessary dependencies/waiting during boot and dependency
  cycles if hooks wait for other interfaces to come up (like ifenslave
  with bonding interfaces). (LP: #1414544)
- Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In
  Ubuntu we currently keep the setting whether the RTC is in local or UTC
  time in /etc/default/rcS UTC=yes|no, instead of /etc/adjtime.
  (LP: #1377258)
- Put session scopes into all cgroup controllers. This makes unprivileged
  user LXC containers work under systemd. (LP: #1346734)
- Lower Breaks: to plymouth version which has the udev inotify fix in
  Ubuntu.
- Lower libappamor1 dep to the Ubuntu version where it moved to /lib.
- Make failure of boot-and-services NSpawn.test_boot non-fatal for now.
  This currently fails when being triggered by Jenkins, but is totally
  unreproducible when running this manually on the exact same machine.

Upgrade fixes, keep until 16.04 LTS release:
- systemd Conflicts/Replaces/Provides systemd-services.
- Remove obsolete systemd-logind upstart job.
- Clean up obsolete /etc/udev/rules.d/README.

systemd (219-4) experimental; urgency=medium

  * tmpfiles: Avoid creating duplicate ACL entries. Add postinst code to clean
them up on upgrade. (Closes: #778656)
  * bootchart: Fix path to default init. (LP: #1423867)
  * Add bootchart autopkgtest, to spot regressions like the above.
  * autopkgtests: Factorize out assert.sh utility functions, and use them in
the tests for useful failure messages.
  * Downgrade requirement for timedated, hostnamed, localed-locale, and
logind autopkgtests from machine to container isolation.
  * boot-and-services and display-manager autopkgtest: Add systemd-sysv as
proper test dependency instead of apt-get installing it. This works now
also under Ubuntu 15.04.
  * boot-and-services autopkgtest: Check cleanup of temporary files during
boot. Reproduces #779169.
  * Clean up /tmp/ directory again. (Closes: #779169, LP: #1424992)
 -- Martin Pitt martin.p...@ubuntu.com   Fri, 27 Feb 2015 08:48:16 +0100

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

Title:
  init=/lib/systemd/systemd-bootchart on 219 triggers a kernel panic on
  kvm

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  if setting init=/lib/systemd/systemd-bootchart, this one doesn't
  reexecute systemd as expected:

  opening output file '/run/log/bootchart-timestamp': No such file or 
directory
  opening output file '/run/log/bootchart-timestamp': No such file or 
directory
  and then, triggers a kernel panic.

  Had to use init='/lib/systemd/systemd-bootchart -i
  /lib/systemd/systemd' to get it booting.

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

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

[Touch-packages] [Bug 1415420] Re: Xorg freeze

[Danilo Enoque Ferreira de Lima]

Dear Christopher,

I am using an LTS release, which as I understand it means Long Term
Support. This reply does not seem to indicate what the release claims
to be. I need this laptop for work and I cannot simply re-
install/upgrade the operating system.

I have given full reports of all my logs and there was no debugging
attempt on your side. Instead, you mark it as incomplete, even though I
have given all the log files available.

Could you instead only for a small period of time try to help me debug
it and fix it? Or provide any support at all, instead of Please update
the OS?

Best regards,
Danilo

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Dear developers and experts,

  I have a Dell Inspiron 14z, using Ubuntu 14.04.1 LTS, kernel 
3.13.0-44-generic and using i915 as my video driver.
  I tried connecting an external monitor to my laptop using the HDMI output 
while running Unity. I used an HDMI-VGA converter to connect it to the 
monitor's VGA input. When I do that (before I try to type xrandr or try to 
configure the new monitor), I'm back to the login screen, being shown in both 
my laptop screen and the external monitor and both screens are frozen. I can 
only do a hard reboot at that stage.

  This is the first time I tried this. I expect apport will include more
  information from dmesg, Xorg logs, etc, but if it doesn't please let
  me know and I can try to provide more information.

  Best regards,
  Danilo

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  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: Wed Jan 28 11:05:10 2015
  DistUpgraded: 2014-09-10 21:04:23,460 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:057f]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] 
[1002:6841] (rev ff) (prog-if ff)
  MachineType: Dell Inc. Inspiron 5423
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic 
root=UUID=09228176-f703-4c11-af01-cb86d0fe27ae ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to trusty on 2014-09-10 (139 days ago)
  dmi.bios.date: 05/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0Y1P79
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A13
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd05/18/2013:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn0Y1P79:rvrA13:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5423
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  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.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Jan 28 10:50:06 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: OutputDP-0  
HDMI-0   VGA-0
  xserver.version: 2:1.15.1-0ubuntu2.6
  xserver.video_driver: intel

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

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

[Touch-packages] [Bug 1415659] Re: Trackpad not working after restart

[Christopher M. Penalver]

Haterade, thank you for reporting this and helping make Ubuntu better.
As per http://support.lenovo.com/us/en/products/laptops-and-netbooks
/yoga-series/yoga-13-notebook-ideapad an update to your computer's buggy
and outdated BIOS is available (55). 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-55

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

Title:
  Trackpad not working after restart

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My trackpad was working perfectly without any issues. No updates had
  been run. My laptop was in sleep mode and power died during this
  state. Once able to reconnect to power source I turned the laptop back
  on. After logging in my trackpad stopped working.

  lsb_release -rd
  Description:  Ubuntu 14.10
  Release:  14.10

  apt-cache policy pkgname
  N: Unable to locate package pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Jan 28 13:52:45 2015
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
  InstallationDate: Installed on 2014-12-17 (42 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: LENOVO 20175
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-29-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 66CN49WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Yoga 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr66CN49WW:bd09/20/2012:svnLENOVO:pn20175:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13:
  dmi.product.name: 20175
  dmi.product.version: Lenovo IdeaPad Yoga 13
  dmi.sys.vendor: LENOVO
  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.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Wed Jan 28 13:47:48 2015
  xserver.configfile: default
  xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 864 
   vendor LGD
  xserver.version: 2:1.16.0-1ubuntu1.2

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

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

[Touch-packages] [Bug 1424726] Re: browser cache is under ~/.local/share/

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/webbrowser-app

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

Title:
  browser cache is under ~/.local/share/

Status in Web Browser App:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu RTM:
  Confirmed

Bug description:
  Browser and webapp’s cache is stored under ~/.local/share/.
  It should go under ~/.cache/.

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 219-4ubuntu1

---
systemd (219-4ubuntu1) vivid; urgency=medium

  * Merge with Debian experimental. Remaining Ubuntu changes:
- Hack to support system-image read-only /etc, and modify files in
  /etc/writable/ instead.
- Keep our much simpler udev maintainer scripts (all platforms must
  support udev, no debconf).
- initramfs init-top: Drop $ROOTDELAY, we do that in a more sensible way
  with wait-for-root. Will get applicable to Debian once Debian gets
  wait-for-root in initramfs-tools.
- initramfs init-bottom: If LVM is installed, settle udev,
  otherwise we get missing LV symlinks. Workaround for LP #1185394.
- Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv
  dependencies to lvm2 which is handled with udev rules in Ubuntu.
- Provide shutdown fallback for upstart. (LP: #1370329)
- debian/extra/ifup@.service: Additionally run for auto class. We don't
  really support allow-hotplug in Ubuntu at the moment, so we need to
  deal with auto devices appearing after /etc/init.d/networking start
  already ran. (LP: #1374521) Also, check if devices are actually defined
  in /etc/network/interfaces as we don't use Debian's net.agent.
- ifup@.service: Drop dependency on networking.service (i. e.
  /etc/init.d/networking), and merely ensure that /run/network exists.
  This avoids unnecessary dependencies/waiting during boot and dependency
  cycles if hooks wait for other interfaces to come up (like ifenslave
  with bonding interfaces). (LP: #1414544)
- Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In
  Ubuntu we currently keep the setting whether the RTC is in local or UTC
  time in /etc/default/rcS UTC=yes|no, instead of /etc/adjtime.
  (LP: #1377258)
- Put session scopes into all cgroup controllers. This makes unprivileged
  user LXC containers work under systemd. (LP: #1346734)
- Lower Breaks: to plymouth version which has the udev inotify fix in
  Ubuntu.
- Lower libappamor1 dep to the Ubuntu version where it moved to /lib.
- Make failure of boot-and-services NSpawn.test_boot non-fatal for now.
  This currently fails when being triggered by Jenkins, but is totally
  unreproducible when running this manually on the exact same machine.

Upgrade fixes, keep until 16.04 LTS release:
- systemd Conflicts/Replaces/Provides systemd-services.
- Remove obsolete systemd-logind upstart job.
- Clean up obsolete /etc/udev/rules.d/README.

systemd (219-4) experimental; urgency=medium

  * tmpfiles: Avoid creating duplicate ACL entries. Add postinst code to clean
them up on upgrade. (Closes: #778656)
  * bootchart: Fix path to default init. (LP: #1423867)
  * Add bootchart autopkgtest, to spot regressions like the above.
  * autopkgtests: Factorize out assert.sh utility functions, and use them in
the tests for useful failure messages.
  * Downgrade requirement for timedated, hostnamed, localed-locale, and
logind autopkgtests from machine to container isolation.
  * boot-and-services and display-manager autopkgtest: Add systemd-sysv as
proper test dependency instead of apt-get installing it. This works now
also under Ubuntu 15.04.
  * boot-and-services autopkgtest: Check cleanup of temporary files during
boot. Reproduces #779169.
  * Clean up /tmp/ directory again. (Closes: #779169, LP: #1424992)
 -- Martin Pitt martin.p...@ubuntu.com   Fri, 27 Feb 2015 08:48:16 +0100

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

Title:
  files in /tmp not being cleared on boot

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd package in Debian:
  Fix Committed

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 

[Touch-packages] [Bug 1426362] [NEW] systemd session files fills up space

[Daniel GALAMBOS]

Public bug reported:

Under Ubuntu 14.10 (server), systemd fills up /run/systemd/sessions directory 
with files.
The files are 240-260 bytes, but there are many
 As per default install, /run is on tmpfs with 50 MB size. After a couple of 
days, /run/ runs out of free space, which can cause not so funny errors, like 
failed kernel update (kernel postinst tries to create files here, then fails)

As I see, thesefiles are releated to ssh sesssions, and yes there are
plenty SSH connection to this host. Shouldn't systemd remove these old
session files?

# lsb_release -rd
Description:Ubuntu 14.10
Release:14.10

# apt-cache policy systemd
systemd:
  Installed: 208-8ubuntu8.2
  Candidate: 208-8ubuntu8.2
  Version table:
 *** 208-8ubuntu8.2 0
500 http://hu.archive.ubuntu.com/ubuntu/ utopic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 208-8ubuntu8 0
500 http://hu.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages

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

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

Title:
  systemd session files fills up space

Status in systemd package in Ubuntu:
  New

Bug description:
  Under Ubuntu 14.10 (server), systemd fills up /run/systemd/sessions directory 
with files.
  The files are 240-260 bytes, but there are many
   As per default install, /run is on tmpfs with 50 MB size. After a couple of 
days, /run/ runs out of free space, which can cause not so funny errors, like 
failed kernel update (kernel postinst tries to create files here, then fails)

  As I see, thesefiles are releated to ssh sesssions, and yes there are
  plenty SSH connection to this host. Shouldn't systemd remove these old
  session files?

  # lsb_release -rd
  Description:Ubuntu 14.10
  Release:14.10

  # apt-cache policy systemd
  systemd:
Installed: 208-8ubuntu8.2
Candidate: 208-8ubuntu8.2
Version table:
   *** 208-8ubuntu8.2 0
  500 http://hu.archive.ubuntu.com/ubuntu/ utopic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   208-8ubuntu8 0
  500 http://hu.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages

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

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

[Touch-packages] [Bug 1424301] Re: ubuntu

[Marc Deslauriers]

Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System - 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!


** Information type changed from Private Security to Public

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

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

Title:
  ubuntu

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  i worte 4 and a half hours ago and i stilll have not got a answer.3
  days ago this was suppose to be fixed but it was a lie.all my
  files,pictures,music,videos are all missing because of this probelm
  with ubuntu.it still won,t get off guest session,my programs are still
  missing but when i try to redownload them them it says they are still
  on ubuntu but they are not showing up

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  .tmp.unity.support.test.0: Error: [Errno 13] Permission denied: 
'/tmp/unity_support_test.0'
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Sat Feb 21 20:06:15 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:188b]
  InstallationDate: Installed on 2014-09-22 (152 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP 2000 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic.efi.signed 
root=UUID=bb76e6fa-b809-4644-916e-7c9ba635f6f7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.37
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 188B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 69.18
  dmi.chassis.asset.tag: 5CG347876Q
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.37:bd06/26/2013:svnHewlett-Packard:pnHP2000NotebookPC:pvr088613000330591620100:rvnHewlett-Packard:rn188B:rvrKBCVersion69.18:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 2000 Notebook PC
  dmi.product.version: 088613000330591620100
  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.56-1~ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  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.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Feb 21 19:57:17 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.6
  xserver.video_driver: radeon

To manage notifications about this bug go to:

[Touch-packages] [Bug 1424286] Re: bugs

[Marc Deslauriers]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  bugs

Status in xorg package in Ubuntu:
  New

Bug description:
  i was doing a work when i start my laptop the linux grub its see a
  little distorsion on the screen

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8.1
  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: Sat Feb 21 19:04:46 2015
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fde0]
 Subsystem: Toshiba America Info Systems Device [1179:fde0]
  InstallationDate: Installed on 2015-01-27 (25 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: TOSHIBA Satellite C655
  ProcEnviron:
   LANGUAGE=es_PR:es
   PATH=(custom, no user)
   LANG=es_PR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=6bee895c-8dc6-4ee3-aa93-0ddd1bed5b9a ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr1.70:bd07/07/2011:svnTOSHIBA:pnSatelliteC655:pvrPSC08U-061037:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Satellite C655
  dmi.product.version: PSC08U-061037
  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.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Sat Feb 21 18:58:14 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5522 
   vendor CMO
  xserver.version: 2:1.16.0-1ubuntu1.3

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

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

[Touch-packages] [Bug 1424375] Re: package rsyslog-mysql 7.4.4-1ubuntu2.5 failed to install/upgrade: sub-processo script pre-removal instalado retornou estado de saída de erro 1

[Marc Deslauriers]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package rsyslog-mysql 7.4.4-1ubuntu2.5 failed to install/upgrade: sub-
  processo script pre-removal instalado retornou estado de saída de erro
  1

Status in rsyslog package in Ubuntu:
  New

Bug description:
  Não sei explicar o que aconteceu.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: rsyslog-mysql 7.4.4-1ubuntu2.5
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 22 10:40:48 2015
  ErrorMessage: sub-processo script pre-removal instalado retornou estado de 
saída de erro 1
  InstallationDate: Installed on 2015-02-10 (12 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140723)
  SourcePackage: rsyslog
  Title: package rsyslog-mysql 7.4.4-1ubuntu2.5 failed to install/upgrade: 
sub-processo script pre-removal instalado retornou estado de saída de erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1426363] [NEW] I-dt should send the alarm QOrganizerItemId to the clock app when the user clicks on an alarm shown in the indicator

[Nekhelesh Ramananthan]

Public bug reported:

When users press on an alarm shown in the indicator-datetime, the clock
app is supposed to be open with that specific alarm details shown.
However at the moment the clock app does not know which alarm was
pressed. It requires i-dt to send QOrganizerItemId to the clock app when
this happens.

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

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

Title:
  I-dt should send the alarm QOrganizerItemId to the clock app when the
  user clicks on an alarm shown in the indicator

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  When users press on an alarm shown in the indicator-datetime, the
  clock app is supposed to be open with that specific alarm details
  shown. However at the moment the clock app does not know which alarm
  was pressed. It requires i-dt to send QOrganizerItemId to the clock
  app when this happens.

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

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

[Touch-packages] [Bug 141445] Re: Internal microphone not working on intel-hda (Realtek ALC262) in gutsy (and intrepid and ...)

[dino99]

outdated flavor, report about a newer active version if needed

** Changed in: alsa-driver
   Importance: Unknown = Undecided

** Changed in: alsa-driver
 Remote watch: ALSA Bug Tracker (discontinued) #4131 = None

** Changed in: alsa-driver
   Status: New = Invalid

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

Title:
  Internal microphone not working on intel-hda (Realtek ALC262) in gutsy
  (and intrepid and ...)

Status in ALSA driver:
  Invalid
Status in alsa-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in alsa-driver package in Fedora:
  Won't Fix

Bug description:
  Hi!

  After several attempts, both in edgy, feisty and now in gutsy, I am still not 
able to get the internal microphone working.
  This prevents me from using skype and various other recording programs.

  The laptop is a Fujitsu Siemens E8110.

  See attached debug info:
  http://pastebin.ca/705610

  Let me know if you need more info!

  Regards,
  Robert

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

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

[Touch-packages] [Bug 1415472] Re: QML cache prevents the QtCreator profiler (interpreter) from running

[Timo Jyrinki]

This should be fixed in vivid now.

** Changed in: qtdeclarative-opensource-src (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 qtdeclarative-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1415472

Title:
  QML cache prevents the QtCreator profiler (interpreter) from running

Status in the base for Ubuntu mobile products:
  Confirmed
Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu RTM:
  Confirmed

Bug description:
  When on a device that has the QML cache installed, the visual profiler
  from QtCreator cannot run as it relies on falling back to interpreter
  based QML (older, 5.3.1 model) and this does not play ball with the
  cache.

  Fix: Disable cache when instruction selection mode requested != QV4
  JIT.

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

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

[Touch-packages] [Bug 1415420] Re: Xorg freeze

[Christopher M. Penalver]

Danilo Enoque Ferreira de Lima, 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 1415420

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: bios-outdated-a16

** Tags removed: bios-outdated-a16
** Tags added: latest-bios-a13

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Dear developers and experts,

  I have a Dell Inspiron 14z, using Ubuntu 14.04.1 LTS, kernel 
3.13.0-44-generic and using i915 as my video driver.
  I tried connecting an external monitor to my laptop using the HDMI output 
while running Unity. I used an HDMI-VGA converter to connect it to the 
monitor's VGA input. When I do that (before I try to type xrandr or try to 
configure the new monitor), I'm back to the login screen, being shown in both 
my laptop screen and the external monitor and both screens are frozen. I can 
only do a hard reboot at that stage.

  This is the first time I tried this. I expect apport will include more
  information from dmesg, Xorg logs, etc, but if it doesn't please let
  me know and I can try to provide more information.

  Best regards,
  Danilo

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  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: Wed Jan 28 11:05:10 2015
  DistUpgraded: 2014-09-10 21:04:23,460 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:057f]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] 
[1002:6841] (rev ff) (prog-if ff)
  MachineType: Dell Inc. Inspiron 5423
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic 
root=UUID=09228176-f703-4c11-af01-cb86d0fe27ae ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to trusty on 2014-09-10 (139 days ago)
  dmi.bios.date: 05/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0Y1P79
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A13
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd05/18/2013:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn0Y1P79:rvrA13:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5423
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  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.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Jan 28 10:50:06 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: OutputDP-0  
HDMI-0   VGA-0
  

[Touch-packages] [Bug 1424726] Re: browser cache is under ~/.local/share/

[Launchpad Bug Tracker]

This bug was fixed in the package webbrowser-app -
0.23+15.04.20150227-0ubuntu1

---
webbrowser-app (0.23+15.04.20150227-0ubuntu1) vivid; urgency=medium

  [ Olivier Tilloy ]
  * Remove all references to private Qt headers, now that we require Qt
5.4.
  * Specify the cache path on the web context, to avoid caching data
under ~/.local/share/. (LP: #1424726)
  * Update translation template.
 -- CI Train Bot ci-train-...@canonical.com   Fri, 27 Feb 2015 10:08:19 +

** Changed in: webbrowser-app (Ubuntu)
   Status: In Progress = Fix Released

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

Title:
  browser cache is under ~/.local/share/

Status in Web Browser App:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu RTM:
  Confirmed

Bug description:
  Browser and webapp’s cache is stored under ~/.local/share/.
  It should go under ~/.cache/.

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

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

[Touch-packages] [Bug 1421192] Re: Initial boot wizard does not include timezone

[Launchpad Bug Tracker]

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

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

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

Title:
  Initial boot wizard does not include timezone

Status in Ubuntu UX bugs:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  During the initial boot the Ubuntu phone asks information regarding
  various things like language, passcode etc. Timezone or date/time is
  not asked, it always defaults to UTC+0.

  This confirmed with Ubuntu 14.10(r16) and 15.04(r01)

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

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

[Touch-packages] [Bug 1426354] Re: Welcome wizard should show the timezone page to allow the user to set the correct system time

[Michał Sawicz]

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

** This bug has been marked a duplicate of bug 1421192
   Initial boot wizard does not include timezone

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

Title:
  Welcome wizard should show the timezone page to allow the user to set
  the correct system time

Status in unity8 package in Ubuntu:
  New

Bug description:
  I have noticed several people reporting https://bugs.launchpad.net
  /ubuntu-clock-app/+bug/1233986 against the clock app where the system
  time set by default is UTC while the clock app shows the correct user
  location. Thereby if the user location shown by the clock app is Paris
  while the clock app time shown is UTC it creates a conflicting and
  confusing situation.

  I understand that the clock app needs to fix it on its end to ensure
  that if there is discrepancy between the time shown and the user
  location then a dialog informing the user to correct the system time
  be shown.

  But nonetheless this issue wouldn't be present if the welcome wizard
  shows the timezone page where the user can set the correct system time
  in the first place.

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

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

[Touch-packages] [Bug 1426354] Re: Welcome wizard should show the timezone page to allow the user to set the correct system time

[Nekhelesh Ramananthan]

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

** Description changed:

  I have noticed several people reporting https://bugs.launchpad.net
- /ubuntu-clock-app/+bug/1233986 against the clock app since the system
+ /ubuntu-clock-app/+bug/1233986 against the clock app where the system
  time set by default is UTC while the clock app shows the correct user
  location. Thereby if the user location shown by the clock app is Paris
  while the clock app time shown is UTC it creates a conflicting and
  confusing situation.
  
  I understand that the clock app needs to fix it on its end to ensure
  that if there is discrepancy between the time shown and the user
  location then a dialog informing the user to correct the system time be
  shown.
  
  But nonetheless this issue wouldn't be present if the welcome wizard
  shows the timezone page where the user can set the correct system time
  in the first place.

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

Title:
  Welcome wizard should show the timezone page to allow the user to set
  the correct system time

Status in unity8 package in Ubuntu:
  New

Bug description:
  I have noticed several people reporting https://bugs.launchpad.net
  /ubuntu-clock-app/+bug/1233986 against the clock app where the system
  time set by default is UTC while the clock app shows the correct user
  location. Thereby if the user location shown by the clock app is Paris
  while the clock app time shown is UTC it creates a conflicting and
  confusing situation.

  I understand that the clock app needs to fix it on its end to ensure
  that if there is discrepancy between the time shown and the user
  location then a dialog informing the user to correct the system time
  be shown.

  But nonetheless this issue wouldn't be present if the welcome wizard
  shows the timezone page where the user can set the correct system time
  in the first place.

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

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

[Touch-packages] [Bug 1366876] Re: Xorg freeze

[James Ferguson]

Sadly, it happened again this morning.  ~30s of total X freeze.  I think
it's always triggered by google Chrome (currently 40.0.2214.115).

I'll attach the syslog fragment, dmidecode, and it says a GPU crash dump
was saved, so I'll attach that.

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Desktop display freezes temporarily, for (approx) 20s or so, approx
  once a day, with mouse pointer still working.  After that it comes
  back and resumes as normal, seemingly replaying mouse and keyboard
  events from the meantime.  I think it's always happened when using
  Google Chrome (Stable - currently 37.0.2062.94, but I think other
  recent versions).  The desktop is completely unresponsive

  This didn't seem to happen until a few weeks ago.  I tend to pull
  updates fairly regularly.

  In syslog there is:

  kernel: [277415.130771] [drm] stuck on render ring

  I suspect this is a dupe since I see other related bugs, but you'd be
  better placed to decide that than I.

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

  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,place,grid,vpswitch,gnomecompat,mousepoll,session,move,obs,imgpng,snap,regex,animation,expo,ezoom,staticswitcher,workarounds,wall,fade,scale]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Sep  8 12:22:27 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: comedi-adv-pci1724, 0.0.1: added
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:21fa]
  InstallationDate: Installed on 2014-07-11 (59 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=561b4b77-cac6-4abb-a89e-ecf7f1bb8f42 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET82WW (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET82WW(2.02):bd09/11/2012:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  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: Thu Sep  4 16:58:14 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.1

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

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

[Touch-packages] [Bug 1423591] Re: [regression] Platform libraries and packages are not versioned

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed = Fix Released

** Changed in: mir/0.12
   Status: Fix Committed = Fix Released

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

Title:
  [regression] Platform libraries and packages are not versioned

Status in Mir:
  Fix Released
Status in Mir 0.12 series:
  Fix Released
Status in mir package in Ubuntu:
  Triaged

Bug description:
  Our graphics/client platform libraries and packages are not versioned
  and thus are not installable in parallel.

  Since our other libraries are installable in parallel, this can lead
  to problems like the one seen in [1]:

  1. Start with a system that has Mir 0.11 (mirserver19, mirplatform6, 
MIR_GRAPHICS_PLATFORM_1).
  2. Bump mirserver ABI 20 in *trunk*, build and install packages (mirserver20, 
mirplatform7, MIR_GRAPHICS_PLATFORM_2).
  3. Applications that use mirserver19 (e.g. USC) will load the new graphics 
platform modules, try to load a symbol with version 
  MIR_GRAPHICS_PLATFORM_1 (which is what mirserver19 works with) and fail.

  Note that this doesn't happen if we don't bump the mirserver ABI,
  because in that case when installing the new package we replace the
  system mirserver19 with a version that looks for
  MIR_GRAPHICS_PLATFORM_2, which is the correct version for the new
  graphics platform binaries.

  [1] https://code.launchpad.net/~alan-griffiths/mir/test-ABI-bump-
  libmirserver/+merge/250177

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

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

[Touch-packages] [Bug 1421255] Re: [regression] Deadlock in TimeoutFrameDroppingPolicy logic results in frozen unity8

[Kevin DuBois]

** Changed in: mir/0.12
   Status: Fix Committed = Fix Released

** Changed in: mir
   Status: Fix Committed = Fix Released

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

Title:
  [regression] Deadlock in TimeoutFrameDroppingPolicy logic results in
  frozen unity8

Status in Mir:
  Fix Released
Status in Mir 0.12 series:
  Fix Released
Status in mir package in Ubuntu:
  Triaged

Bug description:
  spawning from bug 1417773 Unity8 completely frozen (unable to unlock,
  receive calls, etc)

  See Saviq's comment #4  5, duflu's comment #7 in bug 1417773

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

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

[Touch-packages] [Bug 1425523] Re: Cannot connect to device with MTP

[Łukasz Zemczak]

I just tried on latest vivid krillin and mtp works fine here through
nautilus. I can see and send files to my device through the file
manager.

** Tags added: lt-category-visible

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

Title:
  Cannot connect to device with MTP

Status in mtp package in Ubuntu:
  Confirmed

Bug description:
  From an Ubuntu Vivid host, the device is not visible over MTP. 
Disconnecting/reconnecting the cable doesn't change anything.
  I can connect to the device over adb.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: mtp-server 0.0.4+15.04.20150219-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  Date: Wed Feb 25 14:16:52 2015
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150225-020204)
  SourcePackage: mtp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1425987] Re: Cellular data connection stops after a while

[Łukasz Zemczak]

** Tags added: lt-blocker lt-category-visible

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

Title:
  Cellular data connection stops after a while

Status in network-manager package in Ubuntu:
  New

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-02-25 15:06:29
  version version: 122
  version ubuntu: 20150225
  version device: 20150210-95b6a9f
  version custom: 20150225

  Test Case:
  1. Disable Wifi
  2. Verify that a cellular data connection is established
  3. Wait...

  Actual result
  After a while (several minutes) the cellular data connection stops, 
eventually it'll come back but not always.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Thu Feb 26 16:14:14 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2015-02-25 (1 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150225-020204)
  IpRoute:
   
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  PciNetwork:
   
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 
2015-02-25T03:31:54
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1425625] Re: Vivid image 121: Gps tag is permanently turn off on krillin when the custom tarball is installed

[Łukasz Zemczak]

** Tags added: lt-blocker lt-category-visible

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

Title:
  Vivid image 121: Gps tag is permanently turn off on krillin when the
  custom tarball is installed

Status in indicator-location package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Install image 121 and install the krillin custom tarball
  2. Boot the device and use the recommend here location check box  in the 
location page
  3. Drag down the location indicator
  4. Enable gps
  5. drag down the indicator
  6. enable gps a second time
  7. reboot the device once gps stays on
  8. check the locations indicator again

  EXPECTED:
  I expect to see happen what happens on rtm

  ACTUAL:
  Gps is turned off on reboot, and doesn't function when enabled.

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

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

[Touch-packages] [Bug 346415] Re: Intrepid - Jaunty upgrade error in gnome-session-canberra

[dino99]

outdated flavor, report about a newer active version if needed

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

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

Title:
  Intrepid - Jaunty upgrade error in gnome-session-canberra

Status in libcanberra package in Ubuntu:
  Invalid

Bug description:
  Hi,

  I got the following error when upgrading from Intrepid to Jaunty via apt-get 
dist-upgrade
  Des erreurs ont été rencontrées pendant l'exécution : 
/var/cache/apt/archives/gnome-session-canberra_0.11-1ubuntu2_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Then the update stopped.
  apt-get -f install didn't fix the problem
  but apt-get remove gnome-session-canberra followed by apt-get -f install did

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

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

[Touch-packages] [Bug 40189] Re: autofs needs to be restarted to pick up some shares

[dino99]

outdated flavor, report about a newer active version if needed

** Changed in: upstart (Ubuntu)
   Status: Confirmed = Invalid

** Changed in: autofs5 (Ubuntu)
   Status: Confirmed = Invalid

** Changed in: autofs (Ubuntu)
   Status: Confirmed = Invalid

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

Title:
  autofs needs to be restarted to pick up some shares

Status in autofs package in Ubuntu:
  Invalid
Status in autofs5 package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Invalid

Bug description:
  I am using autofs to access shares on a Windows XP machine from a
  Kubuntu AMD64 machine.  The problems applies in both Breezy and
  Dapper.

  EDIT:  confirmed with similar configuration on Intrepid with a NetApp
  filer hosting NFS.  Server OS removed from summary.

  When I first try to access the mount point via cd or in Konqueror it
  does not exist.  However,  if I then restart autofs
  (/etc/init.d/autofs restart) everythin then works OK.  My config files
  are:

  auto.master

  #
  # $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $
  #
  # Sample auto.master file
  # This is an automounter map and it has the following format
  # key [ -mount-options-separated-by-comma ] location
  # For details of the format look at autofs(5).
  #/misc/etc/auto.misc --timeout=60
  #/misc/etc/auto.misc
  #/net /etc/auto.net

  /petunia /etc/petunia.misc --timeout=60

  
  petunia.misc

  #
  # $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $
  #
  # This is an automounter map and it has the following format
  # key [ -mount-options-separated-by-comma ] location
  # Details may be found in the autofs(5) manpage

  cd  -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom

  tony  -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/tony
  chris -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/chris
  shared-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/SharedDocs
  linuxbackups  -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/linuxbackups

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

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

[Touch-packages] [Bug 1416169] Re: Ubuntu 14.10 [drm:i915_stolen_to_physical] *ERROR* conflict detected with stolen region

[Christopher M. Penalver]

Erkan ÜNLÜTÜRK, 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 1416169

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

Title:
  Ubuntu 14.10 [drm:i915_stolen_to_physical] *ERROR* conflict detected
  with stolen region

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  açılışta sorun yaşıyorum. teşekkürler :)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8.1
  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 Jan 30 01:54:07 2015
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Fujitsu Technology Solutions Device [1734:114c]
  InstallationDate: Installed on 2015-01-29 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: ARCELIK AS 1YA-ARCELIK 5440
  ProcEnviron:
   LANGUAGE=tr
   PATH=(custom, no user)
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-29-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2010
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: 6.00 R1.02.3041.A1
  dmi.board.name: D3041-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3041-A1
  dmi.chassis.asset.tag: 93742010006534
  dmi.chassis.type: 6
  dmi.chassis.vendor: ARCELIK AS
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvr6.00R1.02.3041.A1:bd11/09/2010:svnARCELIKAS:pn1YA-ARCELIK5440:pvrV102:rvnFUJITSU:rnD3041-A1:rvrS26361-D3041-A1:cvnARCELIKAS:ct6:cvr:
  dmi.product.name: 1YA-ARCELIK 5440
  dmi.product.version: V102
  dmi.sys.vendor: ARCELIK AS
  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.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Jan 30 01:40:43 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 04f3:0103KEYBOARD, id 8
   inputHID 04f3:0103KEYBOARD, id 9
   inputSIGMACHIP Usb Mouse  MOUSE, id 10
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id2001
   vendor PTS
  xserver.version: 2:1.16.0-1ubuntu1.2

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

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

[Touch-packages] [Bug 1426361] [NEW] Alarms API should expose a unique permanent alarm ID that clock app can use to open an alarm

[Nekhelesh Ramananthan]

Public bug reported:

Alarms API should expose a unique permanent alarm ID that clock app can
use to open an alarm instead of just the alarm index that varies based
on the alarm date dynamically.

Use Case: Bug 1387210 Indicator-datetime will pass the QOrganizerItemId
(unique alarm ID) to clock app when the user clicks on an alarm in the
indicator-datetime. But the current Alarms API does not allow clock app
to open the alarm using that unique ID which results in clock app not
knowing which alarm to show to the user.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: High
 Assignee: Zsombor Egri (zsombi)
 Status: Confirmed

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

Title:
  Alarms API should expose a unique permanent alarm ID that clock app
  can use to open an alarm

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

Bug description:
  Alarms API should expose a unique permanent alarm ID that clock app
  can use to open an alarm instead of just the alarm index that varies
  based on the alarm date dynamically.

  Use Case: Bug 1387210 Indicator-datetime will pass the
  QOrganizerItemId (unique alarm ID) to clock app when the user clicks
  on an alarm in the indicator-datetime. But the current Alarms API does
  not allow clock app to open the alarm using that unique ID which
  results in clock app not knowing which alarm to show to the user.

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

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

[Touch-packages] [Bug 1412730] Re: DELL U2415 monitor detection issues

[Michiel Janssens]

Christopher,

Vivid with fglrx: none off the reported issues exist. U2415 is detected every 
time, display resolution is right, also dpms powersaving works as expected. In 
ATI control Center all hardware is detected. Also no xrandr issues
Trusty with fglrx: same as with vivid, none of the issues.

The main reason I'm not using fglrx is because it's proprietary, but also 
because the opensource radeon gives much better perfomance.
With fglrx there is lag in windows moving and resizing, also in videos. Next to 
that there is a lot of tearing visible. Whem turning on tear-free in Catalyst 
Control Center the lag gets even worse.

So fglrx is a workaround, but not a pleasant one. The lag and tearing is 
visible too many times during daily work.
At the moment I prefer my own workaround as mentioned above with the radeon 
driver and drm helper kernel parameter.
This way the displays work great without lag, but when booting, switching users 
in Unity or just going in suspend/standby I have to put the screen off and on a 
couple of times to get it out of standby.

One thing I noticed with the radeon driver: switching back and forth
between vt7 and and another vt gets the U2415 out of standby too
(eventually).

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

Title:
  DELL U2415 monitor detection issues

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My Laptop HP Elitebook 8740w has two external screens connected.
  1 DELL U2412M connected to vga connector
  1 DELL U2415 connected to Displayport.

  I worked for about a year with a single external display, just U2412M
  on the displayport without the issue I decribe.

  The first issue:
  When booting up and with screens attatched and active, the 2415 boots in 
1024x768 resolution, the 2412 boots at the same moment in 1920x1200 as it 
should.
  At the point where the login screen appears the 2415 goes in power save mode, 
most of the time.
  The 2412 displays just fine at the moment.
  After logging in, turning the 2415 off and on, sometimes helps the get the 
screen active (out of power save).
  When it gets active, the resoltion is 1024x768, not 1920x1200.
  In unity-control-center in display settings the 2415 is displayed as Unknown 
Display and the maximum resolution I can select is 1024x768.

  Second issue:
  After a laptop suspend the 2415 doenst alway become active again, the 2412 
always.
  Turning off an on the 2415 multiple time mostly helps to get the screen 
active.

  Current partial workaround:
  xorg.conf with monitor section for 1920x1200 as in attatchment.
  This doesn't solve booting in 1024x768, but solves the resolution after 
logging in.
  unity-control-center still lists Unknown Screen

  Another strange behavior:
  when executing xrandr command, most of the time the 2415 stays in 1024, but 
after a number of executions the screen swithes to 1920x1200. At that moment 
xrandr outputs all possible resolutions as it should.
  When executing xrandr another time the 2415 switches back to 1024x768

  Already tried kernel v3.18.3-vivid, no change.
  Also tried Utopic live cd, no change.
  Tried Windows 8.1, no issues with both screens. (however my main OS is Ubuntu 
trusty, so..., just for testing)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Jan 20 10:48:24 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.3.20, 3.13.0-40-generic, x86_64: installed
   vboxhost, 4.3.20, 3.13.0-43-generic, x86_64: installed
   vboxhost, 4.3.20, 3.13.0-44-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Broadway XT [Mobility Radeon HD 5870] 
[1002:68a0] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company FirePro M7820 [103c:1520]
  InstallationDate: Installed on 2014-05-11 (253 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP EliteBook 8740w
  PccardctlStatus:
   Socket 0:
     3.3V
    16-bit
    PC Card
     Subdevice 0 (function 0) bound to driver pata_pcmcia
  ProcKernelCmdLine: BOOT_IMAGE=/@trusty/boot/vmlinuz-3.13.0-44-generic 
root=UUID=cfafe8f3-4766-4fc7-b6f3-857eefcd2aff ro rootflags=subvol=@trusty 
plymouth:debug splash quiet drm.debug=0xe radeon.audio=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Touch-packages] [Bug 1421919] Re: clock is missing ~10% of the time

[Ted Gould]

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

** This bug has been marked a duplicate of bug 1425297
   Sometimes indicator-datetime is not available in the UI after a reboot

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

Title:
  clock is missing ~10% of the time

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  This bug is maybe related to Bug #1239710, as in comment #34 mentioned
  I created a new bug report.

  After start of my pc the clock in the notification area is missing sometimes. 
When you kill the indicator-datetime the clock is displaying again:
  sudo pkill -9 indicator-date

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-datetime 13.10.0+14.04.20140415.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  NonfreeKernelModules: wl tbs6982fe tbs6680fe tbs6923fe tbs6985se tbs6928se 
tbs6982se tbs6991fe tbs6618fe tbs6983fe tbs6922fe tbs6928fe tbs6991se tbs6290fe
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 14 10:26:41 2015
  InstallationDate: Installed on 2014-03-30 (320 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140329)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1386208] Re: Purple overflow panel in SuruGradient theme

[Niklas Wenzel]

** Changed in: ubuntu-filemanager-app
   Status: Fix Committed = Fix Released

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

Title:
  Purple overflow panel in SuruGradient theme

Status in File Manager application for Ubuntu devices:
  Fix Released
Status in Ubuntu UI Toolkit:
  Fix Released
Status in Ubuntu UX bugs:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  New

Bug description:
  While testing the new header on trunk, I noticed that the actions on
  the header are purple. They should be the same colour as the rest of
  the app.

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

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