date:20150308

This bug was fixed in the package ubuntu-meta - 1.332

---
ubuntu-meta (1.332) vivid; urgency=medium

  * Refreshed dependencies
  * Added systemd-sysv to standard (LP: #1427654)
 -- Martin PittMon, 09 Mar 2015 06:20:44 +0100

** Changed in: ubuntu-meta (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

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

Title:
  FFE: switch system init to systemd [not touch] in 15.04

Status in init-system-helpers package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Vivid:
  Fix Committed
Status in ubuntu-meta source package in Vivid:
  Fix Released

Bug description:
  As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411
  -systemd-migration we aimed for switching the system (not session)
  init from upstart to systemd this cycle. As this was by and large a
  1.2 man show, this took a little longer. One of the remaining blockers
  for switching the default was to fix NFS (bug 1312976) which is now
  ready to be uploaded. There is also juju (bug 1409639, landed upstream
  now) and maas (bug 1423613, scheduled), but for those we can work
  around missing systemd support by installing upstart on instances.

  We are a few days past feature freeze now, bug Steve and I discussed
  last week, and we still want to aim for switching the default in
  vivid. To be clear, this will affect Ubuntu desktop/server/cloud and
  the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to
  systemd is blocked on touch (too old kernels, some unported jobs), and
  was not scheduled for vivid. For that we need to ensure to keep
  upstart on Touch (there is a work item on the spec).

  I know from at least Kubuntu and Ubuntu GNOME that they are pushing
  for switching to systemd. We should get an ack from the others
  (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of
  vivid users are running systemd already, and I believe we shook out
  the worst bugs now.

  So if/once the release team generally agrees, these are the things
  which need to  happen before switching:

    * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE
    * Land NFS (bug 1312976) - DONE
    * Ensure Touch keeps upstart (bug 1428026) - DONE

  Operationally, the switch is merely to change s/upstart/systemd-sysv/
  in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that
  in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed
  ureadahead, and verified that upgrades from trusty and utopic cleanly
  upgrade to vivid+PPA with removing upstart and installing systemd-
  sysv.

  Around that time I will send a mail to ubuntu-devel-announce@ to warn
  about the impending switch, and give some pointers how to boot with
  upstart (from grub menu or reinstalling upstart), how to debug
  boot/shutdown issues, etc.

  Contingency plan: This will trigger wider testing, and most certainly
  uncover more integration issues. I'll try to keep up with them, but if
  we get to a point where we find that there are too many/too serious
  regressions, we can flip the seed back to upstart and get back to the
  situation today.

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

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

[Touch-packages] [Bug 1429098] Re: systemd[1]: ureadahead.service failed.

> ureadahead: Error al tracear: No existe el archivo o el directorio

Can you please give me the output of

  ls -l /var/lib/ureadahead

?

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

Title:
  systemd[1]: ureadahead.service failed.

Status in NULL Project:
  Invalid
Status in ureadahead package in Ubuntu:
  Incomplete

Bug description:
  dmesg:
  [4.717252] systemd[1]: ureadahead.service failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu3
  Uname: Linux 4.0.0-04rc2-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar  6 08:55:40 2015
  InstallationDate: Installed on 2014-09-25 (162 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.0.0-04rc2-generic 
root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 init=/lib/systemd/systemd
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/null-and-void/+bug/1429098/+subscriptions

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

[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04

** Branch linked: lp:ubuntu/vivid-proposed/ubuntu-meta

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

Title:
  FFE: switch system init to systemd [not touch] in 15.04

Status in init-system-helpers package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in init-system-helpers source package in Vivid:
  Fix Committed
Status in ubuntu-meta source package in Vivid:
  Fix Committed

Bug description:
  As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411
  -systemd-migration we aimed for switching the system (not session)
  init from upstart to systemd this cycle. As this was by and large a
  1.2 man show, this took a little longer. One of the remaining blockers
  for switching the default was to fix NFS (bug 1312976) which is now
  ready to be uploaded. There is also juju (bug 1409639, landed upstream
  now) and maas (bug 1423613, scheduled), but for those we can work
  around missing systemd support by installing upstart on instances.

  We are a few days past feature freeze now, bug Steve and I discussed
  last week, and we still want to aim for switching the default in
  vivid. To be clear, this will affect Ubuntu desktop/server/cloud and
  the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to
  systemd is blocked on touch (too old kernels, some unported jobs), and
  was not scheduled for vivid. For that we need to ensure to keep
  upstart on Touch (there is a work item on the spec).

  I know from at least Kubuntu and Ubuntu GNOME that they are pushing
  for switching to systemd. We should get an ack from the others
  (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of
  vivid users are running systemd already, and I believe we shook out
  the worst bugs now.

  So if/once the release team generally agrees, these are the things
  which need to  happen before switching:

    * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE
    * Land NFS (bug 1312976) - DONE
    * Ensure Touch keeps upstart (bug 1428026) - DONE

  Operationally, the switch is merely to change s/upstart/systemd-sysv/
  in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that
  in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed
  ureadahead, and verified that upgrades from trusty and utopic cleanly
  upgrade to vivid+PPA with removing upstart and installing systemd-
  sysv.

  Around that time I will send a mail to ubuntu-devel-announce@ to warn
  about the impending switch, and give some pointers how to boot with
  upstart (from grub menu or reinstalling upstart), how to debug
  boot/shutdown issues, etc.

  Contingency plan: This will trigger wider testing, and most certainly
  uncover more integration issues. I'll try to keep up with them, but if
  we get to a point where we find that there are too many/too serious
  regressions, we can flip the seed back to upstart and get back to the
  situation today.

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

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

[Touch-packages] [Bug 1302090] Re: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged

2015-03-08 Thread Guy

Finally finally finally I got that salad to work but not the same way,
here the details :

In fact they are to pins disconnected that I had to connect, the 0x1a
and THE 0x18, the connections in hdajackretask are now :

0x1a = Line out (back)
0x18 = (Center/LFE)

Which gives in alsamixer :

Master = Master fonction.
Headphone (Headphone) = Adjustable volume for the headphone jack (first one).
Headphone (Headphone 1) = [00] Not adjustable (probably the headset jack ?).
Speaker (Speaker) = [00] Not adjustable.
Front (Front) = Adjustable and corresponding to front speakers (if on 00 you 
ear only the subwoofer).
Surround (Surround) = seems to correspond to the subwoofer (if on 00 you ear 
high front frequency).
Mic (Mic) = Mic adjustable.
Mic Boost (Mic Boost) = Adjustable but no idee what for.
Auto-Mute (Auto-mute Mode) > (line out, speaker, disable) = If line out 
selected it mute all speakers, if speaker selected it mute only the "tweeters" 
but the subwoofer is still active.

So I hope that it will be usefull to others that were fyghting to get
that "crap" working.

P.S. I didn't try if the headset nor mic are fonctionnal but the
headphone are, no problem.

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

Title:
  Dell Alienware 14, Speaker sound output is mono until a headphone jack
  is plugged

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Here's the required release and package information:

  Description:Ubuntu Trusty Tahr (development branch)
  Release:14.04

  Package: linux-image-extra-3.13.0-19-generic
  Version: 3.13.0-19.40

  When playing audio through speakers on my Alienware 14 2014, the sound
  output is in mono until I plug a headphone in any of the two available
  headphone jacks (obviously, the auto-mute option must be disabled).
  When I do so, the sound starts to play in stereo.

  I would love the sound output to be stereo by default and not be
  forced to plug anything to achieve that.

  Attached is the alsa-info.sh output for my machine.

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

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

[Touch-packages] [Bug 1413865] Re: No default setting for "When power is critically low" in Power settings

2015-03-08 Thread F.J Kong

** Patch added: "patch"
   
https://bugs.launchpad.net/ubuntukylin/+bug/1413865/+attachment/4338505/+files/battery-critical-low.patch

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

Title:
  No default setting for "When power is critically low" in Power
  settings

Status in Ubuntu Kylin:
  Confirmed
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  No default setting for "When power is critically low" in Power
  settings.

  电源设置中”电量严重不足时“没有默认选项

  Steps:
  1. Install the latest Ubuntu kylin Vivid x64 OS
  2. Enter into System settings-->Power
  3. Check the default value of "When power is critically low"
  -->Failed. No default value for it

  Configuration:
  OS: Ubuntu Kylin vivid Daily build 20150122 x64

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

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

[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04

** Changed in: ubuntu-meta (Ubuntu Vivid)
   Status: In Progress => Fix Committed

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

Title:
  FFE: switch system init to systemd [not touch] in 15.04

Status in init-system-helpers package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in init-system-helpers source package in Vivid:
  Fix Committed
Status in ubuntu-meta source package in Vivid:
  Fix Committed

Bug description:
  As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411
  -systemd-migration we aimed for switching the system (not session)
  init from upstart to systemd this cycle. As this was by and large a
  1.2 man show, this took a little longer. One of the remaining blockers
  for switching the default was to fix NFS (bug 1312976) which is now
  ready to be uploaded. There is also juju (bug 1409639, landed upstream
  now) and maas (bug 1423613, scheduled), but for those we can work
  around missing systemd support by installing upstart on instances.

  We are a few days past feature freeze now, bug Steve and I discussed
  last week, and we still want to aim for switching the default in
  vivid. To be clear, this will affect Ubuntu desktop/server/cloud and
  the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to
  systemd is blocked on touch (too old kernels, some unported jobs), and
  was not scheduled for vivid. For that we need to ensure to keep
  upstart on Touch (there is a work item on the spec).

  I know from at least Kubuntu and Ubuntu GNOME that they are pushing
  for switching to systemd. We should get an ack from the others
  (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of
  vivid users are running systemd already, and I believe we shook out
  the worst bugs now.

  So if/once the release team generally agrees, these are the things
  which need to  happen before switching:

    * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE
    * Land NFS (bug 1312976) - DONE
    * Ensure Touch keeps upstart (bug 1428026) - DONE

  Operationally, the switch is merely to change s/upstart/systemd-sysv/
  in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that
  in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed
  ureadahead, and verified that upgrades from trusty and utopic cleanly
  upgrade to vivid+PPA with removing upstart and installing systemd-
  sysv.

  Around that time I will send a mail to ubuntu-devel-announce@ to warn
  about the impending switch, and give some pointers how to boot with
  upstart (from grub menu or reinstalling upstart), how to debug
  boot/shutdown issues, etc.

  Contingency plan: This will trigger wider testing, and most certainly
  uncover more integration issues. I'll try to keep up with them, but if
  we get to a point where we find that there are too many/too serious
  regressions, we can flip the seed back to upstart and get back to the
  situation today.

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

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

[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04

** Branch linked: lp:ubuntu/vivid-proposed/init-system-helpers

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

Title:
  FFE: switch system init to systemd [not touch] in 15.04

Status in init-system-helpers package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in init-system-helpers source package in Vivid:
  Fix Committed
Status in ubuntu-meta source package in Vivid:
  Fix Committed

Bug description:
  As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411
  -systemd-migration we aimed for switching the system (not session)
  init from upstart to systemd this cycle. As this was by and large a
  1.2 man show, this took a little longer. One of the remaining blockers
  for switching the default was to fix NFS (bug 1312976) which is now
  ready to be uploaded. There is also juju (bug 1409639, landed upstream
  now) and maas (bug 1423613, scheduled), but for those we can work
  around missing systemd support by installing upstart on instances.

  We are a few days past feature freeze now, bug Steve and I discussed
  last week, and we still want to aim for switching the default in
  vivid. To be clear, this will affect Ubuntu desktop/server/cloud and
  the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to
  systemd is blocked on touch (too old kernels, some unported jobs), and
  was not scheduled for vivid. For that we need to ensure to keep
  upstart on Touch (there is a work item on the spec).

  I know from at least Kubuntu and Ubuntu GNOME that they are pushing
  for switching to systemd. We should get an ack from the others
  (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of
  vivid users are running systemd already, and I believe we shook out
  the worst bugs now.

  So if/once the release team generally agrees, these are the things
  which need to  happen before switching:

    * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE
    * Land NFS (bug 1312976) - DONE
    * Ensure Touch keeps upstart (bug 1428026) - DONE

  Operationally, the switch is merely to change s/upstart/systemd-sysv/
  in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that
  in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed
  ureadahead, and verified that upgrades from trusty and utopic cleanly
  upgrade to vivid+PPA with removing upstart and installing systemd-
  sysv.

  Around that time I will send a mail to ubuntu-devel-announce@ to warn
  about the impending switch, and give some pointers how to boot with
  upstart (from grub menu or reinstalling upstart), how to debug
  boot/shutdown issues, etc.

  Contingency plan: This will trigger wider testing, and most certainly
  uncover more integration issues. I'll try to keep up with them, but if
  we get to a point where we find that there are too many/too serious
  regressions, we can flip the seed back to upstart and get back to the
  situation today.

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

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

[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04

** Branch linked: lp:~ubuntu-core-dev/ubuntu-seeds/platform.vivid

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

Title:
  FFE: switch system init to systemd [not touch] in 15.04

Status in init-system-helpers package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in init-system-helpers source package in Vivid:
  Fix Committed
Status in ubuntu-meta source package in Vivid:
  In Progress

Bug description:
  As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411
  -systemd-migration we aimed for switching the system (not session)
  init from upstart to systemd this cycle. As this was by and large a
  1.2 man show, this took a little longer. One of the remaining blockers
  for switching the default was to fix NFS (bug 1312976) which is now
  ready to be uploaded. There is also juju (bug 1409639, landed upstream
  now) and maas (bug 1423613, scheduled), but for those we can work
  around missing systemd support by installing upstart on instances.

  We are a few days past feature freeze now, bug Steve and I discussed
  last week, and we still want to aim for switching the default in
  vivid. To be clear, this will affect Ubuntu desktop/server/cloud and
  the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to
  systemd is blocked on touch (too old kernels, some unported jobs), and
  was not scheduled for vivid. For that we need to ensure to keep
  upstart on Touch (there is a work item on the spec).

  I know from at least Kubuntu and Ubuntu GNOME that they are pushing
  for switching to systemd. We should get an ack from the others
  (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of
  vivid users are running systemd already, and I believe we shook out
  the worst bugs now.

  So if/once the release team generally agrees, these are the things
  which need to  happen before switching:

    * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE
    * Land NFS (bug 1312976) - DONE
    * Ensure Touch keeps upstart (bug 1428026) - DONE

  Operationally, the switch is merely to change s/upstart/systemd-sysv/
  in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that
  in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed
  ureadahead, and verified that upgrades from trusty and utopic cleanly
  upgrade to vivid+PPA with removing upstart and installing systemd-
  sysv.

  Around that time I will send a mail to ubuntu-devel-announce@ to warn
  about the impending switch, and give some pointers how to boot with
  upstart (from grub menu or reinstalling upstart), how to debug
  boot/shutdown issues, etc.

  Contingency plan: This will trigger wider testing, and most certainly
  uncover more integration issues. I'll try to keep up with them, but if
  we get to a point where we find that there are too many/too serious
  regressions, we can flip the seed back to upstart and get back to the
  situation today.

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

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

[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04

** Changed in: init-system-helpers (Ubuntu Vivid)
   Status: In Progress => Fix Committed

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

Title:
  FFE: switch system init to systemd [not touch] in 15.04

Status in init-system-helpers package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in init-system-helpers source package in Vivid:
  Fix Committed
Status in ubuntu-meta source package in Vivid:
  In Progress

Bug description:
  As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411
  -systemd-migration we aimed for switching the system (not session)
  init from upstart to systemd this cycle. As this was by and large a
  1.2 man show, this took a little longer. One of the remaining blockers
  for switching the default was to fix NFS (bug 1312976) which is now
  ready to be uploaded. There is also juju (bug 1409639, landed upstream
  now) and maas (bug 1423613, scheduled), but for those we can work
  around missing systemd support by installing upstart on instances.

  We are a few days past feature freeze now, bug Steve and I discussed
  last week, and we still want to aim for switching the default in
  vivid. To be clear, this will affect Ubuntu desktop/server/cloud and
  the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to
  systemd is blocked on touch (too old kernels, some unported jobs), and
  was not scheduled for vivid. For that we need to ensure to keep
  upstart on Touch (there is a work item on the spec).

  I know from at least Kubuntu and Ubuntu GNOME that they are pushing
  for switching to systemd. We should get an ack from the others
  (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of
  vivid users are running systemd already, and I believe we shook out
  the worst bugs now.

  So if/once the release team generally agrees, these are the things
  which need to  happen before switching:

    * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE
    * Land NFS (bug 1312976) - DONE
    * Ensure Touch keeps upstart (bug 1428026) - DONE

  Operationally, the switch is merely to change s/upstart/systemd-sysv/
  in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that
  in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed
  ureadahead, and verified that upgrades from trusty and utopic cleanly
  upgrade to vivid+PPA with removing upstart and installing systemd-
  sysv.

  Around that time I will send a mail to ubuntu-devel-announce@ to warn
  about the impending switch, and give some pointers how to boot with
  upstart (from grub menu or reinstalling upstart), how to debug
  boot/shutdown issues, etc.

  Contingency plan: This will trigger wider testing, and most certainly
  uncover more integration issues. I'll try to keep up with them, but if
  we get to a point where we find that there are too many/too serious
  regressions, we can flip the seed back to upstart and get back to the
  situation today.

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

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

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

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

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

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

Status in indicator-sound package in Ubuntu:
  New

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

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

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

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

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

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

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

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

** Tags removed: need-amd64-retrace

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

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

Status in indicator-sound package in Ubuntu:
  New

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

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

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

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

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

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

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

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

Status in indicator-sound package in Ubuntu:
  New

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

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

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

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

[Touch-packages] [Bug 1429709]

StacktraceTop: main (argc=, argv=) at
/build/buildd/indicator-sound-12.10.2+15.04.20150227.1/src/main.c:53

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

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

Status in indicator-sound package in Ubuntu:
  New

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

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

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

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

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

2015-03-08 Thread Thomas Hotz

Public bug reported:

This immediatly crash comes after a normal start-up.

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

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


** Tags: amd64 apport-crash vivid

** Information type changed from Private to Public

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

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

Status in indicator-sound package in Ubuntu:
  New

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

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

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

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

[Touch-packages] [Bug 1413865] Re: No default setting for "When power is critically low" in Power settings

2015-03-08 Thread F.J Kong

from gsd-power-manager.c we get as follows
/* this is only used on critically low battery where
* hibernate is not available and is marginally better
* than just powering down the computer mid-write */

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

Title:
  No default setting for "When power is critically low" in Power
  settings

Status in Ubuntu Kylin:
  Confirmed
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  No default setting for "When power is critically low" in Power
  settings.

  电源设置中”电量严重不足时“没有默认选项

  Steps:
  1. Install the latest Ubuntu kylin Vivid x64 OS
  2. Enter into System settings-->Power
  3. Check the default value of "When power is critically low"
  -->Failed. No default value for it

  Configuration:
  OS: Ubuntu Kylin vivid Daily build 20150122 x64

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

-- 
Mailing list: https://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 1193238] Re: Xorg freeze

2015-03-08 Thread Hồng Quân

Hello

My laptop which encounters this bug has been lost (stolen). I cannot
support debugging anymore.

On Sun, Feb 15, 2015 at 6:14 AM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> Hồng Quân, could you please capture the crash via
> https://help.ubuntu.com/community/DebuggingSystemCrash ?
>
> ** Changed in: xorg (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1193238
>
> Title:
>   Xorg freeze
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1193238/+subscriptions
>

-- 
Quân
***
* Nguyễn Hồng Quân*
* Y!M: ng_hquan_vn*
* Facebook: ng.hong.quan  *
* Web: quan.hoabinh.vn*
***

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  This occurs a couple of times per day.
  When it occurs, the sound is noisy, keyboard and mouse do not work. I have to 
press Power button to turn it off.
  Attached is the photo of screen when the bug happens

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
  Uname: Linux 3.8.0-25-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.9.2-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 Jun 21 15:05:50 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1652]
  InstallationDate: Installed on 2013-04-25 (56 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: ASUSTeK Computer Inc. K43E
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic 
root=UUID=e9b9ae42-e5a4-4231-a673-a0bc16b188ec 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/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K43E.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K43E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK43E.216:bd09/26/2011:svnASUSTeKComputerInc.:pnK43E:pvr1.0:rvnASUSTeKComputerInc.:rnK43E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K43E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.43-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Fri Jun 21 10:17:00 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.3-0ubuntu6
  xserver.video_driver: intel
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  InstallationDate: Installed on 2013-11-03 (62 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  Package: xorg 1:7.7+1ubuntu6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Tags: third-party-packages saucy
  Uname: Linux 3.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroup

[Touch-packages] [Bug 1399223] Re: python-testtools should be upgraded to version 1.5.0

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

** Changed in: python-testtools (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  python-testtools should be upgraded to version 1.5.0

Status in python-testtools package in Ubuntu:
  Expired

Bug description:
  We are using an old version of testtools on ubuntu which prevents us
  from running all dashboard tests and keeping the dashboard from being
  green.

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

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

[Touch-packages] [Bug 1406006] Re: [HP Pavilion Sleekbook 15 PC, IDT 92HD99BXX, Black Headphone Out, Right] No sound at all

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

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

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

Title:
  [HP Pavilion Sleekbook 15 PC, IDT 92HD99BXX, Black Headphone Out,
  Right] No sound at all

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  I can hear souds from my speackers but not on my headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  parissa1697 F pulseaudio
   /dev/snd/pcmC0D0p:   parissa1697 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Sat Dec 27 22:25:40 2014
  InstallationDate: Installed on 2014-12-27 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Audio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  parissa1697 F pulseaudio
   /dev/snd/pcmC0D0p:   parissa1697 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Right
  Symptom_Type: No sound at all
  Title: [HP Pavilion Sleekbook 15 PC, IDT 92HD99BXX, Black Headphone Out, 
Right] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.05
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 18FE
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 82.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.05:bd10/04/2012:svnHewlett-Packard:pnHPPavilionSleekbook15PC:pvr087E103B590320100:rvnHewlett-Packard:rn18FE:rvr82.13:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Sleekbook 15 PC
  dmi.product.version: 087E103B590320100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1408376] Re: [HDA-Intel - HDA ATI SB, playback] Playback problem

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

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

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

Title:
  [HDA-Intel - HDA ATI SB, playback] Playback problem

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  Solo puedo escuchar el audio atraves de auriculares

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-43.72~precise1-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-43-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  victor 2800 F pulseaudio
   /dev/snd/pcmC0D0p:   victor 2800 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0x9230 irq 16'
 Mixer name : 'Conexant CX20585'
 Components : 'HDA:14f15069,1179fdf4,00100302'
 Controls  : 11
 Simple ctrls  : 6
  CheckboxSubmission: e45f082e2d24f59b336f1a596b97f898
  CheckboxSystem: 5202e7ee197af4942baf4f50cf4120c6
  Date: Wed Jan  7 14:33:54 2015
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=es_PY:es
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_PY.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed
  Symptom_Card: Audio Interno - HDA ATI SB
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA ATI SB, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2011
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: No 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: AMD
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.70:bd01/27/2011:svnTOSHIBA:pnSatelliteC645D:pvrPSC04U-011LM5:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone:
  dmi.product.name: Satellite C645D
  dmi.product.version: PSC04U-011LM5
  dmi.sys.vendor: TOSHIBA
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-01-07T13:33:52.953873

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

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

[Touch-packages] [Bug 1190344] Re: lightdm is leaking FDs -fix

2015-03-08 Thread Robert Ancell

** Changed in: lightdm/1.2
   Status: Fix Released => Fix Committed

** Changed in: lightdm/1.2
Milestone: 1.2.9 => 1.2.10

** Changed in: lightdm/1.12
   Status: Fix Released => Fix Committed

** Changed in: lightdm/1.12
Milestone: 1.12.2 => 1.12.3

** Changed in: lightdm/1.10
   Status: Fix Released => Fix Committed

** Changed in: lightdm/1.10
Milestone: 1.10.4 => 1.10.5

** Changed in: lightdm
   Status: Fix Released => Fix Committed

** Changed in: lightdm
Milestone: 1.13.0 => 1.13.2

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

** Changed in: lightdm (Ubuntu Utopic)
   Status: Fix Committed => Triaged

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

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

Title:
  lightdm is leaking FDs -fix

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.12 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm source package in Precise:
  Triaged
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Utopic:
  Triaged
Status in lightdm source package in Vivid:
  Triaged
Status in Fedora:
  Unknown

Bug description:
  [Impact]
  LightDM doesn't close the server side end of the pipes used to communicate 
with session processes. This means each session that is created leaks two file 
descriptors eventually leading to the system stopping it from creating new 
pipes.

  [Test Case]
  1. Start LightDM
  2. Check how many pipes are open
  # lsof -p {lightdm_pid} | grep FIFO | wc -l
  3. Create sessions by either cycling between users in Unity Greeter or 
logging in and out
  4. Check how many pipes exist using step 2.
  Expected result:
  No more pipes should be open
  Observed result:
  Many pipes remain open

  [Regression Potential]
  Low. Fix is to close pipes when finished with them. Tested with regression 
tests.

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

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

[Touch-packages] [Bug 1190344] Re: lightdm is leaking FDs -fix

2015-03-08 Thread Robert Ancell

Hmm, turns out I only committed the session leak from the attached patch
and not the greeter leak. I've committed that fix now.

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

Title:
  lightdm is leaking FDs -fix

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Light Display Manager 1.12 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Triaged
Status in lightdm source package in Trusty:
  Confirmed
Status in lightdm source package in Utopic:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Released
Status in Fedora:
  Unknown

Bug description:
  [Impact]
  LightDM doesn't close the server side end of the pipes used to communicate 
with session processes. This means each session that is created leaks two file 
descriptors eventually leading to the system stopping it from creating new 
pipes.

  [Test Case]
  1. Start LightDM
  2. Check how many pipes are open
  # lsof -p {lightdm_pid} | grep FIFO | wc -l
  3. Create sessions by either cycling between users in Unity Greeter or 
logging in and out
  4. Check how many pipes exist using step 2.
  Expected result:
  No more pipes should be open
  Observed result:
  Many pipes remain open

  [Regression Potential]
  Low. Fix is to close pipes when finished with them. Tested with regression 
tests.

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

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

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

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1429303, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1429697/+attachment/4338423/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1429697/+attachment/4338425/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1429697/+attachment/4338426/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1429697/+attachment/4338427/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1429697/+attachment/4338428/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1429697/+attachment/4338429/+files/ThreadStacktrace.txt

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Crash report appeared at login.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Sun Mar  8 15:51:33 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  InstallationDate: Installed on 2014-11-30 (98 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  Signal: 5
  SourcePackage: indicator-sound
  StacktraceTop: main ()
  Title: indicator-sound-service crashed with signal 5 in main()
  UpgradeStatus: Upgraded to vivid on 2015-02-09 (27 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1316777] Re: Translation template has full path to source files

2015-03-08 Thread Rodney Dawes

** Changed in: intltool
Milestone: None => 0.51.0

** Changed in: intltool
   Status: Fix Committed => Fix Released

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

Title:
  Translation template has full path to source files

Status in Internationalization Tool Collection:
  Fix Released
Status in intltool package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  Fix Released

Bug description:
  The translation template currently has full paths to source files.
  This needs to be fixed so that only relative paths are encoded in the
  template.

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

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

[Touch-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

2015-03-08 Thread Pablo180

After an upgrade to 14.10 the workaround stopped working (restarting
network manager each resume). Due to another problem I had to reinstall
14.10 and the problem is no longer present for me after the reinstall. I
am not sure whether this has been fixed in 14.10 or whether it was the
re-installation that fixed it, but either way the problem has been fixed
for me.

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

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

Status in NetworkManager:
  New
Status in wicd:
  Invalid
Status in systemd-shim package in Ubuntu:
  Confirmed
Status in systemd-shim source package in Saucy:
  Won't Fix
Status in systemd-shim source package in Trusty:
  Confirmed

Bug description:
  As per request from bug #1184262, this is a new report, along with
  dbus (to be attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: systemd-services 204-0ubuntu19
  Uname: Linux 3.12.0-custom x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 20:24:41 2013
  MarkForUpload: True
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

  SRU INFORMATION:
  FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty 
already)

  Regression potential: Low. Flushing the session bus was introduced in
  version 4 and is obviously bogus as in a system D-BUS service there is
  no session bus. This causes lots of confusing error messages and
  unnecessary overhead like trying to start dbus-launch. Flushing the
  system bus is low-risk, in most cases it's a no-op and it would
  otherwise prevent losing signals after waking up. No known
  regressions.

  TEST CASE: Run several suspend/resume cycles with the lid, session
  indicator menu, and verify that the network comes back up. It is known
  that this fix is necessary but not sufficient, so it is not expected
  to fix all cases. But it should not make things worse, so if network
  now does not come up any more on a machine where it previously worked
  this would count as failure/regression.

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

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

[Touch-packages] [Bug 1427804] Re: Mouse pointer disappears after upgrade to kernel 3.19

2015-03-08 Thread blmv...@gmail.com

Same here on Ubuntu 3.19 Kernel and on 3.19pf1 custom kernel. So I think
it has something to do with a specific device or class of devices.

I'm using a Satelite C875-S7132NR

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

Title:
  Mouse pointer disappears after upgrade to kernel 3.19

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrade to kernel 3.19, the mouse pointer disappears.
  The mouse is fully functional, just cannot see its pointer, which makes it 
pretty useless...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  Uname: Linux 3.19.0-031900-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Mar  3 19:23:30 2015
  DistUpgraded: 2014-11-04 19:50:17,092 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.16.0-31-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.19.0-031900-generic, x86_64: installed
   vboxhost, 4.3.18, 3.16.0-30-generic, x86_64: installed
   vboxhost, 4.3.18, 3.16.0-31-generic, x86_64: installed
   vboxhost, 4.3.18, 3.19.0-031900-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
  InstallationDate: Installed on 2014-10-24 (129 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-031900-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to utopic on 2014-11-04 (118 days ago)
  dmi.bios.date: 09/30/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2012
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO(Wi-Fi ac)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2012:bd09/30/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  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: Tue Mar  3 19:21:19 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4121 
   vendor WAC
  xserver.version: 2:1.16.0-1ubuntu1.3

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

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

[Touch-packages] [Bug 1429678] Re: media player "fail to connect"

2015-03-08 Thread Glen Ditchfield

** Attachment added: "syslog with apparmor messages around 16:35:32"
   
https://bugs.launchpad.net/ubuntu/+source/mediaplayer-app/+bug/1429678/+attachment/4338380/+files/syslog

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

Title:
  media player "fail to connect"

Status in mediaplayer-app package in Ubuntu:
  New

Bug description:
  Sometimes (three occasions in the last month) my Nexus 7 can't play
  media files. If I select a video in the Video scope, the player
  launches but displays a dialog saying "Error playing video \n Fail to
  connect with playback backend". If I select an audio file in the Music
  scope, the music app opens, but th file doesn't play and the user
  interface does nothing.

  On the last two occasions I noticed apparmor messages in syslog. I
  will attach the most recent syslog.

  The players have played these audio and video files successfully at
  other times.

  On the most recent occasion, I powered the device off twice without
  fixing the problem but another power cycle three days later fixed it.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: mediaplayer-app 0.20.5+14.10.20141015-0ubuntu1
  Uname: Linux 3.4.0-3-flo armv7l
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: armhf
  Date: Sun Mar  8 20:04:02 2015
  InstallationDate: Installed on 2014-12-01 (97 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20141201-020204)
  SourcePackage: mediaplayer-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1429678] [NEW] media player "fail to connect"

2015-03-08 Thread Glen Ditchfield

Public bug reported:

Sometimes (three occasions in the last month) my Nexus 7 can't play
media files. If I select a video in the Video scope, the player launches
but displays a dialog saying "Error playing video \n Fail to connect
with playback backend". If I select an audio file in the Music scope,
the music app opens, but th file doesn't play and the user interface
does nothing.

On the last two occasions I noticed apparmor messages in syslog. I will
attach the most recent syslog.

The players have played these audio and video files successfully at
other times.

On the most recent occasion, I powered the device off twice without
fixing the problem but another power cycle three days later fixed it.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: mediaplayer-app 0.20.5+14.10.20141015-0ubuntu1
Uname: Linux 3.4.0-3-flo armv7l
ApportVersion: 2.14.7-0ubuntu10
Architecture: armhf
Date: Sun Mar  8 20:04:02 2015
InstallationDate: Installed on 2014-12-01 (97 days ago)
InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20141201-020204)
SourcePackage: mediaplayer-app
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug armhf vivid

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

Title:
  media player "fail to connect"

Status in mediaplayer-app package in Ubuntu:
  New

Bug description:
  Sometimes (three occasions in the last month) my Nexus 7 can't play
  media files. If I select a video in the Video scope, the player
  launches but displays a dialog saying "Error playing video \n Fail to
  connect with playback backend". If I select an audio file in the Music
  scope, the music app opens, but th file doesn't play and the user
  interface does nothing.

  On the last two occasions I noticed apparmor messages in syslog. I
  will attach the most recent syslog.

  The players have played these audio and video files successfully at
  other times.

  On the most recent occasion, I powered the device off twice without
  fixing the problem but another power cycle three days later fixed it.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: mediaplayer-app 0.20.5+14.10.20141015-0ubuntu1
  Uname: Linux 3.4.0-3-flo armv7l
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: armhf
  Date: Sun Mar  8 20:04:02 2015
  InstallationDate: Installed on 2014-12-01 (97 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20141201-020204)
  SourcePackage: mediaplayer-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1429644] Re: [ENS1371 - Emulated Ensoniq AudioPCI inside VMware, playback] Sound is distorted

2015-03-08 Thread Raymond

** Summary changed:

- [ENS1371 - Ensoniq AudioPCI, playback] Sound is distorted
+ [ENS1371 - Emulated Ensoniq AudioPCI inside VMware, playback] Sound is 
distorted

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

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

Title:
  [ENS1371 - Emulated Ensoniq AudioPCI inside VMware, playback] Sound is
  distorted

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  sound quality poor.

  distoted sound

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaditya   15448 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar  9 01:58:35 2015
  InstallationDate: Installed on 2015-03-06 (2 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:AudioPCI 
successful
  Symptom_Card: Creative Sound Blaster AudioPCI64V, AudioPCI128 - Ensoniq 
AudioPCI
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [ENS1371 - Ensoniq AudioPCI, playback] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2015-03-07T12:55:40.634974

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

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

[Touch-packages] [Bug 1248642] Re: dynamic library inconsistencies with OpenGL/C++

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

** Changed in: nvidia-graphics-drivers-331 (Ubuntu Trusty)
   Status: New => Confirmed

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

Title:
  dynamic library inconsistencies with OpenGL/C++

Status in binutils package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-319 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in binutils source package in Trusty:
  In Progress
Status in nvidia-graphics-drivers-319 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Confirmed
Status in binutils package in Debian:
  Fix Released

Bug description:
  While using the nvidia-319 driver, the following C++ program won't
  run:

  $ cat > test.cpp << EOF
  #include 
  #include 
  int main(int argc, char *argv[]) {
std::string s;
glEnable(GL_LIGHT0);
  }
  EOF

  Instead, it fails with the following error message:
  $ g++ test.cpp -lGL
  $ ./a.out
  Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_versions: 
Assertion `needed != ((void *)0)' failed!

  Using the xserver-xorg-video-nouveau driver, the problem does not
  occur. Also, when std::string is not used, the program runs without
  problems. Using OpenGL from pure C programs is also not a problem. The
  problem can be reproduced with both g++-4.6 and g++-4.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nvidia-319 319.32-0ubuntu7
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: openafs nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Wed Nov  6 18:25:48 2013
  InstallationDate: Installed on 2013-11-01 (5 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MarkForUpload: True
  SourcePackage: nvidia-graphics-drivers-319
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia.319.hybrid.conf: [deleted]

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

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

[Touch-packages] [Bug 1248642] Re: dynamic library inconsistencies with OpenGL/C++

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

** Changed in: nvidia-graphics-drivers-319 (Ubuntu Trusty)
   Status: New => Confirmed

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

Title:
  dynamic library inconsistencies with OpenGL/C++

Status in binutils package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-319 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in binutils source package in Trusty:
  In Progress
Status in nvidia-graphics-drivers-319 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Confirmed
Status in binutils package in Debian:
  Fix Released

Bug description:
  While using the nvidia-319 driver, the following C++ program won't
  run:

  $ cat > test.cpp << EOF
  #include 
  #include 
  int main(int argc, char *argv[]) {
std::string s;
glEnable(GL_LIGHT0);
  }
  EOF

  Instead, it fails with the following error message:
  $ g++ test.cpp -lGL
  $ ./a.out
  Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_versions: 
Assertion `needed != ((void *)0)' failed!

  Using the xserver-xorg-video-nouveau driver, the problem does not
  occur. Also, when std::string is not used, the program runs without
  problems. Using OpenGL from pure C programs is also not a problem. The
  problem can be reproduced with both g++-4.6 and g++-4.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nvidia-319 319.32-0ubuntu7
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: openafs nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Wed Nov  6 18:25:48 2013
  InstallationDate: Installed on 2013-11-01 (5 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MarkForUpload: True
  SourcePackage: nvidia-graphics-drivers-319
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia.319.hybrid.conf: [deleted]

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

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

[Touch-packages] [Bug 1424074] Re: Vivid Unity Wallpaper horizontally hashed

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

Do not create new bug reports for the exact same issue. This is also not
unity’s fault, as I can reproduce the issue in GNOME Shell as well, so
the bug must be somewhere else.

** This bug has been marked a duplicate of bug 1406802
   Vivid Unity Wallpaper horizontally hashed

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

Title:
  Vivid Unity Wallpaper horizontally hashed

Status in unity package in Ubuntu:
  New

Bug description:
  Wallpaper still hashed on this Lenovo M58P

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=15.04
  DISTRIB_CODENAME=vivid
  DISTRIB_DESCRIPTION="Ubuntu Vivid Vervet (development branch)"
  Linux Lenovo2 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
  model name: Intel(R) Core(TM)2 Duo CPU E8400  @ 3.00GHz
  model name: Intel(R) Core(TM)2 Duo CPU E8400  @ 3.00GHz
  00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03)

  Files > Pictures > select picture > set as wallpaper will correct the
  image - may have to do this several times.

  Settings - Appearance - wallpaper did not correct the image.

  See attachment.

  Note, this does not occur on my other test systems which have
  different graphic controllers.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150219.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.1-0ubuntu2
  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 Feb 20 16:45:20 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkCentre M6258 [17aa:3048]
 Subsystem: Lenovo Device [17aa:3048]
  InstallationDate: Installed on 2015-02-20 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150219)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-13-generic 
root=UUID=733dbf2f-324c-4185-820a-512e6f8a6a7b ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5CKT69AUS
  dmi.board.name: LENOVO
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE:
  dmi.product.name: 6234A1U
  dmi.product.version: ThinkCentre M58p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.1+15.04.20150213-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0~rc1-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0~rc1-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Feb 20 16:44:26 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.16.2.901-1ubuntu4

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

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

[Touch-packages] [Bug 1420514] Re: scrollbar sees reduced mouse movement

This is a GTK+ “feature” which has nothing to do with unity.

** Package changed: unity (Ubuntu) => gtk+3.0 (Ubuntu)

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

Title:
  scrollbar sees reduced mouse movement

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  I am not using overlay scrollbar, so just normal scrollbars.

  Steps to reproduce the issue:

  - Open a program with large scrollable content, where handle is small (for 
example, a long pdf in evince, or even the sound volume scrollbar of 
indicater-sound - It doesn't happen with Firefox)
  - Take the scrollbar (left mouse press on scrollbar handle)
  - **Very slowly** start moving the mouse for a second or two
  - Move the mouse normally

  Expected behavior: The scrollbar handle moves with the mouse with the
  same speed

  Observed behavior: The scrollbar handle moves with greatly reduced
  speed compared to the movement of the mouse

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,place,grid,mousepoll,compiztoolbox,vpswitch,regex,gnomecompat,imgpng,snap,move,unitymtgrabhandles,resize,session,wall,animation,workarounds,fade,expo,scale,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Tue Feb 10 21:40:21 2015
  ExecutablePath: /usr/bin/compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to utopic on 2014-11-01 (100 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1420514/+subscriptions

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

[Touch-packages] [Bug 1319789] Re: Trackpad not working on 14.04

2015-03-08 Thread Christopher M. Penalver

varun, could you please provide the product number of your computer?

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

Title:
  Trackpad not working on 14.04

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  ever since the laptop was updated to 14.04 lts from 12.04 lts, the
  tracpad has not been working, and is not recognised. there is no
  trackpad option under mouse and trackpad settings. i have tried many
  attempts to fix it, but has not worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 15 17:02:52 2014
  DistUpgraded: 2014-05-11 18:24:24,169 DEBUG enabling apt cron job
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-puli-precise-amd64-20130925-0
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:2166]
 Subsystem: Hewlett-Packard Company Device [103c:2166]
  InstallationDate: Installed on 2013-11-28 (168 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130925-02:34
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=856eced2-cdd1-459e-8b1e-55b1ed18f5ac ro i915.modeset=1 quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-05-11 (3 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2166
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.34
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd10/31/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr09921100410600080:rvnHewlett-Packard:rn2166:rvr29.34:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 09921100410600080
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu May 15 16:37:20 2014
  xserver.configfile: default
  xserver.errors:
   module ABI major version (18) doesn't match the server's version (20)
   Failed to load module "syntp" (module requirement mismatch, 0)
   module ABI major version (18) doesn't match the server's version (20)
   Failed to load module "syntp" (module requirement mismatch, 0)
   No input driver matching `syntp'
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Touch-packages] [Bug 1427700] Re: Nautilus icon in launcher creates seperate icon when clicked

** Package changed: unity (Ubuntu) => bamf (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/1427700

Title:
  Nautilus icon in launcher creates seperate icon when clicked

Status in bamf package in Ubuntu:
  Confirmed

Bug description:
  Sometimes clicking the Nautilus icon in the launcher opens Nautilus
  with a seperate additional Nautilus icon in the launcher below the
  original 'locked' icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150219.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Mar  3 14:18:52 2015
  InstallationDate: Installed on 2015-03-03 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150303)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1427876] Re: bug

I mean, please add a description of the bug that prompted you to file
this ticket.

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

Title:
  bug

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  ProblemType: Compiz Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-46.77-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: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Mar  3 22:58:18 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.10, 3.13.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd Device [144d:c708]
  InstallationDate: Installed on 2015-02-25 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E5EV/300E4EV/270E5EV/270E4EV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic 
root=UUID=95d32bd4-7502-4fa5-b6ab-75a2503aefdd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P05RBD
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP270E5V-K03DZ
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP05RBD:bd05/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E5EV/300E4EV/270E5EV/270E4EV:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP270E5V-K03DZ:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 300E5EV/300E4EV/270E5EV/270E4EV
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 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: Tue Mar  3 21:11:24 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5539
   vendor CMO
  xserver.version: 2:1.15.1-0ubuntu2.7

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

-- 
Mailing list: https://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 1319789] Re: Trackpad not working on 14.04

2015-03-08 Thread varun

I thank you for your support and am sorry for the delayed response. The
sticker on the laptop sys HP Pavillion 15 Notebook PC. Not too sure of
the model no.

Thanks,
Varun.
  Original Message  
From: Christopher M. Penalver
Sent: Thursday, 19 February 2015 16:51
To: varun19...@gmail.com
Reply To: Bug 1319789
Subject: [Bug 1319789] Re: Trackpad not working on 14.04

varun, could you please provide the full computer model as noted on the
sticker of the computer itself (not from the Bug Description)?

** Tags added: needs-full-computer-model

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

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

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1319789

Title:
Trackpad not working on 14.04

Status in xorg package in Ubuntu:
Incomplete

Bug description:
ever since the laptop was updated to 14.04 lts from 12.04 lts, the
tracpad has not been working, and is not recognised. there is no
trackpad option under mouse and trackpad settings. i have tried many
attempts to fix it, but has not worked.

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

ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CompizPlugins: 
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu May 15 17:02:52 2014
DistUpgraded: 2014-05-11 18:24:24,169 DEBUG enabling apt cron job
DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-stella-puli-precise-amd64-20130925-0
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device [103c:2166]
Subsystem: Hewlett-Packard Company Device [103c:2166]
InstallationDate: Installed on 2013-11-28 (168 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130925-02:34
MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=856eced2-cdd1-459e-8b1e-55b1ed18f5ac ro i915.modeset=1 quiet splash 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-05-11 (3 days ago)
dmi.bios.date: 10/31/2013
dmi.bios.vendor: Insyde
dmi.bios.version: F.34
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2166
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 29.34
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd10/31/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr09921100410600080:rvnHewlett-Packard:rn2166:rvr29.34:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion 15 Notebook PC
dmi.product.version: 09921100410600080
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu May 15 16:37:20 2014
xserver.configfile: default
xserver.errors:
module ABI major version (18) doesn't match the server's version (20)
Failed to load module "syntp" (module requirement mismatch, 0)
module ABI major version (18) doesn't match the server's version (20)
Failed to load module "syntp" (module requirement mismatch, 0)
No input driver matching `syntp'
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 17900 
vendor AUO
xserver.version: 2:1.15.1-0ubuntu2

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

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

Title:
  Trackpad not working on 14.04

Status in xorg package in Ubunt

[Touch-packages] [Bug 1429670] [NEW] Desktop reverts to defaults, can't be changed

2015-03-08 Thread James Ferguson

Public bug reported:

All of a sudden my launcher icons, wallpaper image etc, reverted to
default, and when I "unlock from launcher" on the defaults, they
disappear after about a second, and then reappear when I tried to re-
arrange the icon order.

I think there's perhaps something screwy with gconf (? - isn't that
where the personal launcher app list is?) because another setting went
away and can't be restored (I use caps lock as another control).
However, I don't know how to test this or where to look for logs, and
the *symptoms* turn up in Unity.

If anyone can help with places to look for diagnostics etc., I'd
appreciate it.  Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.4+14.04.20141217-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.7
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]
CurrentDesktop: Unity
Date: Sun Mar  8 18:06:28 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-05-21 (290 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140310)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Desktop reverts to defaults, can't be changed

Status in unity package in Ubuntu:
  New

Bug description:
  All of a sudden my launcher icons, wallpaper image etc, reverted to
  default, and when I "unlock from launcher" on the defaults, they
  disappear after about a second, and then reappear when I tried to re-
  arrange the icon order.

  I think there's perhaps something screwy with gconf (? - isn't that
  where the personal launcher app list is?) because another setting went
  away and can't be restored (I use caps lock as another control).
  However, I don't know how to test this or where to look for logs, and
  the *symptoms* turn up in Unity.

  If anyone can help with places to look for diagnostics etc., I'd
  appreciate it.  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.4+14.04.20141217-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  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]
  CurrentDesktop: Unity
  Date: Sun Mar  8 18:06:28 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-05-21 (290 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140310)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1242918] Re: Writing metadata is not supported for CR2

2015-03-08 Thread Alan Pater

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

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

Title:
  Writing metadata is not supported for CR2

Status in exiv2 package in Ubuntu:
  Fix Released

Bug description:
  I tried to write metadata to RAW CR2 files in digikam, but without
  success (it worked for JPG).

  When I started digikam from console I got the following:
  digikam(4116)/KEXIV2 KExiv2Iface::KExiv2::Private::printExiv2ExceptionError: 
Cannot find Xmp key 'Xmp.mwg-rs.Regions/mwg-rs:RegionList[0]/mwg-rs:Name' into 
image using Exiv2 (Error # 35 : No namespace info available for XMP prefix 
`mwg-rs' digikam(4116)/KEXIV2 KExiv2Iface::KExiv2::getXmpTagStringSeq: XMP 
String Seq ( Xmp.digiKam.TagsList ): ("Betti", "Próba") digikam(4116)/KEXIV2 
KExiv2Iface::KExiv2::setIptcKeywords: /home/kisben/Képek/új/IMG_2590.CR2 ==> 
Iptc Keywords: Betti,Emberek,Próba digikam(4116)/KEXIV2 
KExiv2Iface::KExiv2::save: KExiv2::metadataWritingMode 0 digikam(4116)/KEXIV2 
KExiv2Iface::KExiv2::save: Will write Metadata to file "IMG_2590.CR2" 
digikam(4116)/KEXIV2 KExiv2Iface::KExiv2::Private::saveOperations: Writing 
metadata is not supported for file "IMG_2590.CR2" digikam(4116)/KEXIV2 
KExiv2Iface::KExiv2::save: Metadata for file "IMG_2590.CR2" written to file.

  NOTE:
  I already reported the problem to digikam 
(https://bugs.kde.org/show_bug.cgi?id=326408), but they closed as the problem 
is in libexiv2.

  If this is not the right place to report, pls write me where I can
  report the problem.

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

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

[Touch-packages] [Bug 818102] Re: Wrong filename when renaming from the Exif create timestamp

2015-03-08 Thread Alan Pater

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

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

Title:
  Wrong filename when renaming from the Exif create timestamp

Status in exiv2 package in Ubuntu:
  Fix Released

Bug description:
  The name of the file is one hour ahead than the Exif creation
  timestamp.

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

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

[Touch-packages] [Bug 601555] Re: Error: Directory NikonPreview, entry 0xb3b2 has invalid size 3115890614*1; skipping entry.

2015-03-08 Thread Alan Pater

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

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

Title:
  Error: Directory NikonPreview, entry 0xb3b2 has invalid size
  3115890614*1; skipping entry.

Status in The GNU Image Manipulation Program (GIMP):
  Unknown
Status in exiv2 package in Ubuntu:
  Fix Released
Status in exiv2 package in Debian:
  Confirmed

Bug description:
  Binary package hint: exiv2

  When I start digikam from the command line, it bombs it with
  (thousands?) of messages like:

  [...]
  Warning: Directory NikonPreview, entry 0xb3b2 has unknown Exif (TIFF) type 
46516; setting type size 1.
  Error: Directory NikonPreview, entry 0xb3b2 has invalid size 3115890614*1; 
skipping entry.
  [...]
  Error: Offset of directory NikonPreview, entry 0x00c4 is out of bounds: 
Offset = 0x01010101; truncating the entry
  Warning: Directory NikonPreview, entry 0x0504 has unknown Exif (TIFF) type 
1798; setting type size 1.
  [...]

  According to http://mail.kde.org/pipermail/digikam-
  users/2009-July/007947.html

  It's a problem of libexiv2
  *t

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: libexiv2-6 0.19-1
  ProcVersionSignature: Ubuntu 2.6.31-21.59-generic
  Uname: Linux 2.6.31-21-generic x86_64
  Architecture: amd64
  Date: Sun Jul  4 11:08:10 2010
  ProcEnviron:
   LANGUAGE=de_CH:de
   PATH=(custom, user)
   LANG=de_CH.utf8
   SHELL=/bin/bash
  SourcePackage: exiv2

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

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

[Touch-packages] [Bug 1429529] Re: Package resolver can't find *-lts-utopic package dependencies, aborts

2015-03-08 Thread Tholl1989

** Attachment added: "apport.libgles2-mesa-dev-lts-utopic.m_aroj3l.apport"
   
https://bugs.launchpad.net/ubuntu/+source/mesa-lts-utopic/+bug/1429529/+attachment/4338327/+files/apport.libgles2-mesa-dev-lts-utopic.m_aroj3l.apport

** Description changed:

  [Description]
  On Ubuntu 14.04.2 with updated kernel and X stack (LTS Enablement Stacks) 
package resolver fails to find *-lts-utopic package dependencies, aborts.
  
  [Test case]
  $ sudo apt-get -o debug::pkgproblemresolver=true install qtbase5-dev
  (Log attached as apt.log)
  
  [Workaround]
  Manually resolve:
  $ sudo apt-get install qtbase5-dev libgles2-mesa-dev-lts-utopic
  
  Possible catch all solution:
  $ sudo apt-get install .*-dev-lts-utopic
  
  [Speculation]
- Control file of libgles2-mesa-dev-lts-utopic do look right:
+ Control file of libgles2-mesa-dev-lts-utopic 10.3.2-0ubuntu1~trusty2 does 
look right imho:
  http://debian-handbook.info/browse/stable/sect.package-meta-information.html
  
  Guess APT just get overwhelmend by the possibilies and aborts before
  finding the right one.
  
  Is there some SAT-solver, which could conform? Aptitude's resolver fails, too.
  Could control files be tweaked to make resolving easier?
  
  [Possible affected packages]
  Possible all packages which have dependencies on *-mesa-dev for which there's 
an updated version in the LTS Enablement Stacks.
  Roughly:
  $ apt-cache rdepends .*-mesa-dev

** Description changed:

  [Description]
  On Ubuntu 14.04.2 with updated kernel and X stack (LTS Enablement Stacks) 
package resolver fails to find *-lts-utopic package dependencies, aborts.
  
  [Test case]
  $ sudo apt-get -o debug::pkgproblemresolver=true install qtbase5-dev
  (Log attached as apt.log)
  
  [Workaround]
  Manually resolve:
  $ sudo apt-get install qtbase5-dev libgles2-mesa-dev-lts-utopic
  
  Possible catch all solution:
  $ sudo apt-get install .*-dev-lts-utopic
  
  [Speculation]
  Control file of libgles2-mesa-dev-lts-utopic 10.3.2-0ubuntu1~trusty2 does 
look right imho:
  http://debian-handbook.info/browse/stable/sect.package-meta-information.html
  
- Guess APT just get overwhelmend by the possibilies and aborts before
+ Guess APT just get overwhelmed by the possibilies and aborts before
  finding the right one.
  
  Is there some SAT-solver, which could conform? Aptitude's resolver fails, too.
  Could control files be tweaked to make resolving easier?
  
  [Possible affected packages]
  Possible all packages which have dependencies on *-mesa-dev for which there's 
an updated version in the LTS Enablement Stacks.
  Roughly:
  $ apt-cache rdepends .*-mesa-dev

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

Title:
  Package resolver can't find *-lts-utopic package dependencies, aborts

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  [Description]
  On Ubuntu 14.04.2 with updated kernel and X stack (LTS Enablement Stacks) 
package resolver fails to find *-lts-utopic package dependencies, aborts.

  [Test case]
  $ sudo apt-get -o debug::pkgproblemresolver=true install qtbase5-dev
  (Log attached as apt.log)

  [Workaround]
  Manually resolve:
  $ sudo apt-get install qtbase5-dev libgles2-mesa-dev-lts-utopic

  Possible catch all solution:
  $ sudo apt-get install .*-dev-lts-utopic

  [Speculation]
  Control file of libgles2-mesa-dev-lts-utopic 10.3.2-0ubuntu1~trusty2 does 
look right imho:
  http://debian-handbook.info/browse/stable/sect.package-meta-information.html

  Guess APT just get overwhelmed by the possibilies and aborts before
  finding the right one.

  Is there some SAT-solver, which could conform? Aptitude's resolver fails, too.
  Could control files be tweaked to make resolving easier?

  [Possible affected packages]
  Possible all packages which have dependencies on *-mesa-dev for which there's 
an updated version in the LTS Enablement Stacks.
  Roughly:
  $ apt-cache rdepends .*-mesa-dev

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

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

[Touch-packages] [Bug 1429529] Re: Package resolver can't find *-lts-utopic package dependencies, aborts

2015-03-08 Thread Tholl1989

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

Title:
  Package resolver can't find *-lts-utopic package dependencies, aborts

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  [Description]
  On Ubuntu 14.04.2 with updated kernel and X stack (LTS Enablement Stacks) 
package resolver fails to find *-lts-utopic package dependencies, aborts.

  [Test case]
  $ sudo apt-get -o debug::pkgproblemresolver=true install qtbase5-dev
  (Log attached as apt.log)

  [Workaround]
  Manually resolve:
  $ sudo apt-get install qtbase5-dev libgles2-mesa-dev-lts-utopic

  Possible catch all solution:
  $ sudo apt-get install .*-dev-lts-utopic

  [Speculation]
  Control file of libgles2-mesa-dev-lts-utopic 10.3.2-0ubuntu1~trusty2 does 
look right imho:
  http://debian-handbook.info/browse/stable/sect.package-meta-information.html

  Guess APT just get overwhelmed by the possibilies and aborts before
  finding the right one.

  Is there some SAT-solver, which could conform? Aptitude's resolver fails, too.
  Could control files be tweaked to make resolving easier?

  [Possible affected packages]
  Possible all packages which have dependencies on *-mesa-dev for which there's 
an updated version in the LTS Enablement Stacks.
  Roughly:
  $ apt-cache rdepends .*-mesa-dev

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

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

[Touch-packages] [Bug 1429529] Re: Package resolver can't find *-lts-utopic package dependencies, aborts

2015-03-08 Thread Tholl1989

** Summary changed:

- Unsolvable LTSEnablementStack Mesa package dependency
+ Package resolver can't find *-lts-utopic package dependencies, aborts

** Description changed:

  [Description]
- On 14.04.2 aptitude/APT determinates non-LTSEnablementStack Mesa packages 
instead of *lts-utopic pendants as dependencies. This leads to unsolvable 
conflicts with the already installed *lts-utopic packages.
+ On Ubuntu 14.04.2 with updated kernel and X stack (LTS Enablement Stacks) 
package resolver fails to find *-lts-utopic package dependencies, aborts.
  
- 
- [Test Case]
- [a] libgles2-mesa (10.1.3-0ubuntu0.3) instead of libgles2-mesa-lts-utopic 
(10.3.2-0ubuntu1~trusty2)
- $ sudo aptitude install qtbase5-dev
- The following NEW packages will be installed:
-   libglapi-mesa{a} libgles2-mesa{ab} libgles2-mesa-dev{a} libglu1-mesa-dev{a} 
libqt5concurrent5{a} libqt5opengl5-dev{a} qt5-qmake{a} 
-   qtbase5-dev qtbase5-dev-tools{a} 
- 0 packages upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
- Need to get 4,439 kB of archives. After unpacking 27.9 MB will be used.
- The following packages have unmet dependencies:
-  xserver-xorg-lts-utopic : Conflicts: libglapi-mesa (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
-Conflicts: libgles2-mesa (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
-  libgles2-mesa : Conflicts: libgles2 which is a virtual package.
-  libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is 
to be installed.
-  libgles2-mesa-lts-utopic : Conflicts: libgles2 which is a virtual package.
- Conflicts: libgles2-mesa but 10.1.3-0ubuntu0.3 is 
to be installed.
- 
- libglapi-mesa conflicts due to libgles2-mesa having a dependency on
- libglapi-mesa (= 10.1.3-0ubuntu0.3).
- 
- [b] libgl1-mesa-dev (10.1.3-0ubuntu0.3) instead of libgl1-mesa-lts-utopic 
(10.3.2-0ubuntu1~trusty2)
- $ sudo aptitude install freeglut3-dev
- The following NEW packages will be installed:
-   freeglut3{a} freeglut3-dev libdrm-dev{a} libgl1-mesa-dev{a} 
libgl1-mesa-dri{a} libgl1-mesa-glx{ab} libglapi-mesa{a} libglu1-mesa-dev{a} 
-   libice-dev{a} libllvm3.4{a} libpthread-stubs0-dev{a} libsm-dev{a} 
libx11-dev{a} libx11-doc{a} libx11-xcb-dev{a} libxau-dev{a} 
-   libxcb-dri2-0-dev{a} libxcb-dri3-dev{a} libxcb-glx0-dev{a} 
libxcb-present-dev{a} libxcb-randr0-dev{a} libxcb-render0-dev{a} 
-   libxcb-shape0-dev{a} libxcb-sync-dev{a} libxcb-xfixes0-dev{a} 
libxcb1-dev{a} libxdamage-dev{a} libxdmcp-dev{a} libxext-dev{a} 
-   libxfixes-dev{a} libxshmfence-dev{a} libxt-dev{a} libxxf86vm-dev{a} 
mesa-common-dev{a} x11proto-core-dev{a} x11proto-damage-dev{a} 
-   x11proto-dri2-dev{a} x11proto-fixes-dev{a} x11proto-gl-dev{a} 
x11proto-input-dev{a} x11proto-kb-dev{a} x11proto-xext-dev{a} 
-   x11proto-xf86vidmode-dev{a} xorg-sgml-doctools{a} xtrans-dev{a} 
- 0 packages upgraded, 45 newly installed, 0 to remove and 68 not upgraded.
- Need to get 16.6 MB of archives. After unpacking 88.2 MB will be used.
- The following packages have unmet dependencies:
-  libgl1-mesa-dri-lts-utopic : Conflicts: libgl1-mesa-dri but 
10.1.3-0ubuntu0.3 is to be installed.
-  libgl1-mesa-glx-lts-utopic : Conflicts: libgl1 which is a virtual package.
-   Conflicts: libgl1-mesa-glx but 
10.1.3-0ubuntu0.3 is to be installed.
-  xserver-xorg-lts-utopic : Conflicts: libgl1-mesa-dri (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
-Conflicts: libgl1-mesa-glx (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
-Conflicts: libglapi-mesa (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
-  libgl1-mesa-glx : Conflicts: libgl1 which is a virtual package.
-  libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is 
to be installed.
+ [Test case]
+ $ sudo apt-get -o debug::pkgproblemresolver=true install qtbase5-dev
+ (Log attached as apt.log)
  
  [Workaround]
- [a]
- $ sudo aptitude install qtbase5-dev libgles2-mesa-lts-utopic
+ Manually resolve:
+ $ sudo apt-get install qtbase5-dev libgles2-mesa-dev-lts-utopic
  
- [b]
- $ sudo aptitude install -s freeglut3-dev libgl1-mesa-dev-lts-utopic
+ Possible catch all solution:
+ $ sudo apt-get install .*-dev-lts-utopic
+ 
+ [Speculation]
+ Control file of libgles2-mesa-dev-lts-utopic do look right:
+ http://debian-handbook.info/browse/stable/sect.package-meta-information.html
+ 
+ Guess APT just get overwhelmend by the possibilies and aborts before
+ finding the right one.
+ 
+ Is there some SAT-solver, which could conform? Aptitude's resolver fails, too.
+ Could control files be tweaked to make resolving easier?
+ 
+ [Possible affected packages]
+ Possible all packages which have dependencies on *-mesa-dev for which there's 
an updated version in the LTS Enablement Stacks.
+ Roughly:
+ $ apt-cache rdepends .*-mesa-dev

** Attachment added: "apt.log"
   
https://bugs.launchpad.net/ubuntu/+source/mesa-lts-utopic/+bug/1429529/+attachment/

[Touch-packages] [Bug 1411643] Re: Automatic brightness toggle switch missing on krillin/vivid

2015-03-08 Thread Michał Sawicz

I can still see this with emulator devel-proposed #130. Krillin seems
fine.

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

Title:
  Automatic brightness toggle switch missing on krillin/vivid

Status in indicator-power package in Ubuntu:
  Incomplete

Bug description:
  I noticed that on my krillin device with devel-propsed (r70), the
  automatic display brightness toggle switch is missing in the battery
  indicator.

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

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

[Touch-packages] [Bug 1429661] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1380982, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1429661/+attachment/4338286/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1429661/+attachment/4338288/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1429661/+attachment/4338289/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1429661/+attachment/4338290/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1429661/+attachment/4338291/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1429661/+attachment/4338292/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1380982
   ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()

Status in ibus package in Ubuntu:
  New

Bug description:
  Happened on startup

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: ibus 1.5.9-1ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Sun Mar  8 22:06:35 2015
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2014-04-19 (323 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to vivid on 2015-03-02 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1424460] Re: package lightdm 1.12.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

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

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

Title:
  package lightdm 1.12.2-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  trying to install updates on ubuntu 14.10, reports package
  installation failed

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: lightdm 1.12.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  Date: Sat Feb 21 21:10:43 2015
  DuplicateSignature: package:lightdm:1.12.2-0ubuntu1:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-11-12 (102 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: lightdm
  Title: package lightdm 1.12.2-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1424460] Re: package lightdm 1.12.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-03-08 Thread Peter Bauer

This happend after adding proposed updates to Ubuntu 14.10 on my Ugoos
UT3 RK3288 device.

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

Title:
  package lightdm 1.12.2-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  trying to install updates on ubuntu 14.10, reports package
  installation failed

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: lightdm 1.12.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  Date: Sat Feb 21 21:10:43 2015
  DuplicateSignature: package:lightdm:1.12.2-0ubuntu1:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-11-12 (102 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: lightdm
  Title: package lightdm 1.12.2-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1323837] Re: Sim toolkit is not available on UT

2015-03-08 Thread taiebot65

up on this bug.

I have been in holidays abroad again and could not get any network
connection.

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

Title:
  Sim toolkit is not available on UT

Status in ofono package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  E.g. of SIm toolkit is http://support.vodafone.com.au/articles/FAQ
  /SIM-Toolkit

  While a lot of those addons are completely crap and useless, the SIm
  toolkit is sometimes used by some phone provider to set your sim card
  to roaming mode when you are abroad which makes it a must have.

  For the moment i need to borrow a second phone put my sim card in it,
  go to the Sim-toolkit, enable my sim card for roaming and put the sim
  card back in my UT to get my phone working while i am abroad. I need
  to do the same when i go back home.

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

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

[Touch-packages] [Bug 215341] Re: Add some visual feedback when hover mouse over menubar

2015-03-08 Thread Fred

** Also affects: human-theme (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Add some visual feedback when hover mouse over menubar

Status in GTK+ GUI Toolkit:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in human-theme package in Ubuntu:
  New

Bug description:
  Binary package hint: human-theme

  Add some (subtle) visual feedback that appears when you hover the
  mouse over a menu in the menubar.

  I think this would improve usability, and make the system feel more
  responsive.

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

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

[Touch-packages] [Bug 1429644] [NEW] [ENS1371 - Ensoniq AudioPCI, playback] Sound is distorted

2015-03-08 Thread Anshuman

Public bug reported:

sound quality poor.

distoted sound

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pulseaudio 1:4.0-0ubuntu11
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  aaditya   15448 F pulseaudio
CurrentDesktop: Unity
Date: Mon Mar  9 01:58:35 2015
InstallationDate: Installed on 2015-03-06 (2 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:AudioPCI successful
Symptom_Card: Creative Sound Blaster AudioPCI64V, AudioPCI128 - Ensoniq AudioPCI
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: Digital clip or distortion, or "overdriven" sound
Title: [ENS1371 - Ensoniq AudioPCI, playback] Sound is distorted
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2013
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2015-03-07T12:55:40.634974

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


** Tags: amd64 apport-bug third-party-packages trusty

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

Title:
  [ENS1371 - Ensoniq AudioPCI, playback] Sound is distorted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  sound quality poor.

  distoted sound

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaditya   15448 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar  9 01:58:35 2015
  InstallationDate: Installed on 2015-03-06 (2 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:AudioPCI 
successful
  Symptom_Card: Creative Sound Blaster AudioPCI64V, AudioPCI128 - Ensoniq 
AudioPCI
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [ENS1371 - Ensoniq AudioPCI, playback] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2015-03-07T12:55:40.634974

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

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

[Touch-packages] [Bug 1426942] Re: Kubuntu Vivid - unable to display Gujarati Text

2015-03-08 Thread Timo Jyrinki

There's Qt 5.4.1 brewing, but since it's currently blocked by a bug I'll
include this in another 5.4.0 qtbase upload if it seems the blocker bug
isn't seeing a fix soon.

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

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

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

Title:
  Kubuntu Vivid - unable to display Gujarati Text

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

Bug description:
  Applications built with qt5/KDE Framework 5 on Kubuntu Vivid Beta 1
  can no longer render Gujarati script. This is probably due to

  https://bugreports.qt.io/browse/QTBUG-44568

  My Platform:
  Kubuntu Vivid Beta 1

  Packages affected: Any package built with Qt5 5.4 (e.g. konsole, Muon
  Package Manager etc)

  Expected:
  Render Gujarati script correctly (as was the case in Kubuntu versions prior 
to 15.04)

  Actual Results:
  Gujarati glyphs are displayed as squares

  
  The above Qt bug is scheduled to be fixed in Qt 5.5. If Kubuntu Vivid is 
going to ship with Qt 5.4, will it be possible to include a patched Qt5.4 to 
resolve this specific bug?

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

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

[Touch-packages] [Bug 215341] Re: Add some visual feedback when hover mouse over menubar

2015-03-08 Thread Bug Watch Updater

** Changed in: gtk
   Status: New => 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/215341

Title:
  Add some visual feedback when hover mouse over menubar

Status in GTK+ GUI Toolkit:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: human-theme

  Add some (subtle) visual feedback that appears when you hover the
  mouse over a menu in the menubar.

  I think this would improve usability, and make the system feel more
  responsive.

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

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

[Touch-packages] [Bug 1429641] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1380982, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1429641/+attachment/4338230/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1429641/+attachment/4338231/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1429641/+attachment/4338232/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1429641/+attachment/4338233/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1429641/+attachment/4338234/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1429641/+attachment/4338235/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1380982
   ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()

Status in ibus package in Ubuntu:
  New

Bug description:
  Occurred in Xubuntu 15.04

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: ibus 1.5.9-1ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  Date: Sun Mar  8 16:36:56 2015
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2015-01-11 (56 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140225)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to vivid on 2015-02-18 (17 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare 
sudo tape video

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

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

[Touch-packages] [Bug 1425891] Re: Xorg radeon freezes if firefix loads big images

2015-03-08 Thread Christopher M. Penalver

Christoph, have you tried upgrading your install to the Utopic
enablement stack as outlined in
https://wiki.ubuntu.com/Kernel/LTSEnablementStack to see if the issue is
resolved?

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

Title:
  Xorg radeon freezes if firefix loads big images

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  If I open each of this URLs

  
http://canon-premium.webcdn.stream.ne.jp/www09/canon-premium/eosd/samples/eos5dsr/downloads/02.jpg
  
http://canon-premium.webcdn.stream.ne.jp/www09/canon-premium/eosd/samples/eos5ds/downloads/02.jpg

  in a firefox 36.0 on a Xorg Server of 1.15.1 with a R9 270 and a
  Ubuntu 14.04.1  AMD64 the desktop freezes. I can only move the mouse
  pointer, although the the login via SSH is still possible and works
  fine. By restarting the Xorg Server I can gain control over the local
  terminal again.

  This happens with the radeon driver, but not with the fglrx driver.
  The problem did not manifest itself with other applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  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:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  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: Thu Feb 26 11:19:49 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R9 270] 
[1002:6811] (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3050]
  InstallationDate: Installed on 2014-04-22 (309 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-45-generic 
root=UUID=e0df56bb-b5a5-4b2c-9f89-ce5ff2e3b019 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 12/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: Z97 Extreme6
  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:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 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 11:18:17 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.7
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1428711] Re: indicator-sound-service crashed with SIGSEGV in g_variant_is_trusted()

2015-03-08 Thread Charles Kerr

Yep, it looks like we're getting a player with a NULL state somehow,
which is crashing when we try to convert that into a variant for sending
over the bus. (1) we should sanitize our inputs better, ie modify the
state property setter to disallow NULLs. More importantly, (2) we need
to figure out where this NULL state is coming from.

** Information type changed from Private to Public

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

Title:
  indicator-sound-service crashed with SIGSEGV in g_variant_is_trusted()

Status in indicator-sound package in Ubuntu:
  Confirmed

Bug description:
  Crash seemed to happen when I opened both rhythmbox and banshee at the
  same time.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  5 10:50:51 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  InstallationDate: Installed on 2011-07-08 (1336 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f072b0e3b80:mov0x20(%rdi),%eax
   PC (0x7f072b0e3b80) ok
   source "0x20(%rdi)" (0x0020) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-sound
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_builder_add_value () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   accounts_service_user_set_player ()
   _start ()
  Title: indicator-sound-service crashed with SIGSEGV in 
g_variant_builder_add_value()
  UpgradeStatus: Upgraded to vivid on 2015-01-19 (45 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare 
sbuild vboxusers

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

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

[Touch-packages] [Bug 1112466] Re: ffmpeg(libav) cannot encode dvd

2015-03-08 Thread Sebastian Ramacher

Ugh, there has been no response to this for more than two years. Is this
still an issue with recent versions of libav?

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

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

Title:
  ffmpeg(libav) cannot encode dvd

Status in libav package in Ubuntu:
  Incomplete

Bug description:
  When using k9copy to resize the dvd, the resultant files are not
  playable.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: ffmpeg 6:0.8.5-0ubuntu0.12.10.1
  ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Fri Feb  1 13:51:07 2013
  InstallationDate: Installed on 2012-12-23 (40 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libav
  UpgradeStatus: Upgraded to quantal on 2013-02-01 (0 days ago)

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

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

[Touch-packages] [Bug 1194550] Re: [gallery] Gallery should not be fullscreen on thumbnail view

2015-03-08 Thread Sam Bull

** Changed in: gallery-app (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: platform-api (Ubuntu)
   Status: New => Fix Released

** Changed in: qtubuntu
   Status: In Progress => Fix Released

** Changed in: platform-api
   Status: In Progress => Fix Released

** Changed in: ubuntu-ux
   Status: Fix Committed => Fix Released

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

Title:
  [gallery] Gallery should not be fullscreen on thumbnail view

Status in Platform API:
  Fix Released
Status in QT Ubuntu:
  Fix Released
Status in Ubuntu UX bugs:
  Fix Released
Status in gallery-app package in Ubuntu:
  Fix Released
Status in platform-api package in Ubuntu:
  Fix Released
Status in qtubuntu package in Ubuntu:
  Fix Released

Bug description:
  As indicated in the design screenshots (http://design.ubuntu.com/apps
  /global-patterns/content-views#full-screen-view), the gallery app
  should only enter fullscreen mode (hiding the menu bar) when
  displaying an image, not when on the thumbnail overview.

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

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

[Touch-packages] [Bug 1425891] Re: Xorg radeon freezes if firefix loads big images

2015-03-08 Thread Christoph

I tested the vivid-desktop-amd64.iso of march 6th as a live cd and the
firefox loads the big images without a problem.

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

Title:
  Xorg radeon freezes if firefix loads big images

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  If I open each of this URLs

  
http://canon-premium.webcdn.stream.ne.jp/www09/canon-premium/eosd/samples/eos5dsr/downloads/02.jpg
  
http://canon-premium.webcdn.stream.ne.jp/www09/canon-premium/eosd/samples/eos5ds/downloads/02.jpg

  in a firefox 36.0 on a Xorg Server of 1.15.1 with a R9 270 and a
  Ubuntu 14.04.1  AMD64 the desktop freezes. I can only move the mouse
  pointer, although the the login via SSH is still possible and works
  fine. By restarting the Xorg Server I can gain control over the local
  terminal again.

  This happens with the radeon driver, but not with the fglrx driver.
  The problem did not manifest itself with other applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  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:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  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: Thu Feb 26 11:19:49 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R9 270] 
[1002:6811] (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3050]
  InstallationDate: Installed on 2014-04-22 (309 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-45-generic 
root=UUID=e0df56bb-b5a5-4b2c-9f89-ce5ff2e3b019 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 12/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: Z97 Extreme6
  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:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 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 11:18:17 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.7
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1411643] Re: Automatic brightness toggle switch missing on krillin/vivid

2015-03-08 Thread Charles Kerr

I'm not able to confirm this in krillin 14.10 r252.

The strange thing is wasn't any work done on the brightness controls in
the last two months, and there's nothing in the changelog indicating
anything related to it landed since this bug was reported.

Michael, Saviq, are either of you still seeing this bug?

** Changed in: indicator-power (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Automatic brightness toggle switch missing on krillin/vivid

Status in indicator-power package in Ubuntu:
  Incomplete

Bug description:
  I noticed that on my krillin device with devel-propsed (r70), the
  automatic display brightness toggle switch is missing in the battery
  indicator.

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

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

[Touch-packages] [Bug 1429636] Re: indicator-sound-service crashed with SIGSEGV in g_variant_builder_add_value()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1428711, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1429636/+attachment/4338208/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1429636/+attachment/4338210/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1429636/+attachment/4338211/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1429636/+attachment/4338212/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1429636/+attachment/4338213/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1429636/+attachment/4338214/+files/ThreadStacktrace.txt

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  indicator-sound-service crashed with SIGSEGV in
  g_variant_builder_add_value()

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Happened on login. Sound indicator is there, but is non working (every
  menu item is greyed out).

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar  8 20:04:14 2015
  EcryptfsInUse: Yes
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  InstallationDate: Installed on 2014-05-05 (307 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  SegvAnalysis:
   Segfault happened at: 0x7f2905480b80:mov0x20(%rdi),%eax
   PC (0x7f2905480b80) ok
   source "0x20(%rdi)" (0x0020) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-sound
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_builder_add_value () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   accounts_service_user_set_player ()
   _start ()
  Title: indicator-sound-service crashed with SIGSEGV in 
g_variant_builder_add_value()
  UpgradeStatus: Upgraded to vivid on 2015-03-06 (1 days ago)
  UserGroups: bumblebee cdrom debian-tor dip juner libvirtd lpadmin plugdev 
sambashare sudo vboxusers wireshark

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

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

[Touch-packages] [Bug 1274115] Re: snd_pcm_avail() returned a value that is exceptionally large

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

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

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

Title:
  snd_pcm_avail() returned a value that is exceptionally large

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Sometimese sound begins stutter while listen to music or watching youtube. In 
syslog I see:
  Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] 
alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 
866944 bytes (4914 ms).
  Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] 
alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. 
Please report this issue to the ALSA developers.

  I'm using Kubuntu 13.10
  $ uname -a
  Linux bazilio-laptop 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:17:04 UTC 
2013 x86_64 x86_64 x86_64 GNU/Linux
  $ kde4-config --version
  Qt: 4.8.4
  KDE Development Platform: 4.12.0
  kde4-config: 1.0
  $ pulseaudio --version
  pulseaudio 4.0
  $ alsactl --version
  alsactl version 1.0.27.1

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

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

[Touch-packages] [Bug 1274115] Re: snd_pcm_avail() returned a value that is exceptionally large

2015-03-08 Thread Boomer

I also have similar issue.

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

Title:
  snd_pcm_avail() returned a value that is exceptionally large

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Sometimese sound begins stutter while listen to music or watching youtube. In 
syslog I see:
  Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] 
alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 
866944 bytes (4914 ms).
  Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] 
alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. 
Please report this issue to the ALSA developers.

  I'm using Kubuntu 13.10
  $ uname -a
  Linux bazilio-laptop 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:17:04 UTC 
2013 x86_64 x86_64 x86_64 GNU/Linux
  $ kde4-config --version
  Qt: 4.8.4
  KDE Development Platform: 4.12.0
  kde4-config: 1.0
  $ pulseaudio --version
  pulseaudio 4.0
  $ alsactl --version
  alsactl version 1.0.27.1

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

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

[Touch-packages] [Bug 1427672] Re: System doesn't power off when shutting down

Ah, thanks. I misunderstood you then.

Can you say with certain confidence that the kernel/graphics driver
crash (that's what it seems to be) only happens with systemd, but not
with upstart? Perhaps there's some difference in how we shut down
X.org/lightdm under either. Can you reliably switch users or just
start/stop your session under upstart and systemd? (The latter is the
part that causes graphics driver/kernel crashes on my machine
occasionally, but it doesn't seem init specific)

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

Title:
System doesn't power off when shutting down

Status in systemd package in Ubuntu:
Confirmed

Bug description:
1. Open the session indicator (cog in top-right)
2. Shut Down...
3. Shut Down
4. The monitors go blank
5. The system doesn't power off (waited > 5 minutes)

Things which do work

- poweroff -f
- Changing to a debug shell and shutting down using login1.Manager PowerOff

I can't use the system-shutdown/ functionality since shutdown doesn't
get that far. I can't SSH in since network is down. I can't switch VT
when it's in this state so I'm not able to interact with the system. I
can't see anything on the monitors since they are turned off.

Any tips on how to get useful debugging information? I'll attach
journalctl from the previous boot but the last message is the journal
shutting down so it's not that useful I don't think. Also syslog.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-4ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
ApportVersion: 2.16.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar 3 12:57:33 2015
InstallationDate: Installed on 2012-10-07 (876 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic
root=UUID=980689ca-e7d9-4a99-8230-33b8b6e917cd ro nomdmonddf nomdmonisw
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf
nomdmonisw systemd.debug-shell nomdmonddf nomdmonisw
SourcePackage: systemd
UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago)
dmi.bios.date: 08/17/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1201
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-V LX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1201:bd08/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

2015-03-08 Thread Yanpas

Hello guys! The bug seems to be fixed on my PC. There were lots of changes 
since the last check, but the last I did was disabling ACPI HPET Table in BIOS. 
Also I got rid of indicators.
Other BIOS settings:

suspend to ram - auto
check ready bit - auto
away mode support - disabled

restore on AC - power off
Ring-in power on - disabled
PCI devices power on - disabled
PS/2 Keyboard power on - disabled
RTC alarm - by OS

ACPI HPET Table  -  disabled

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

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

Status in NetworkManager:
  New
Status in wicd:
  Invalid
Status in systemd-shim package in Ubuntu:
  Confirmed
Status in systemd-shim source package in Saucy:
  Won't Fix
Status in systemd-shim source package in Trusty:
  Confirmed

Bug description:
  As per request from bug #1184262, this is a new report, along with
  dbus (to be attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: systemd-services 204-0ubuntu19
  Uname: Linux 3.12.0-custom x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 20:24:41 2013
  MarkForUpload: True
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

  SRU INFORMATION:
  FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty 
already)

  Regression potential: Low. Flushing the session bus was introduced in
  version 4 and is obviously bogus as in a system D-BUS service there is
  no session bus. This causes lots of confusing error messages and
  unnecessary overhead like trying to start dbus-launch. Flushing the
  system bus is low-risk, in most cases it's a no-op and it would
  otherwise prevent losing signals after waking up. No known
  regressions.

  TEST CASE: Run several suspend/resume cycles with the lid, session
  indicator menu, and verify that the network comes back up. It is known
  that this fix is necessary but not sufficient, so it is not expected
  to fix all cases. But it should not make things worse, so if network
  now does not come up any more on a machine where it previously worked
  this would count as failure/regression.

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

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

[Touch-packages] [Bug 464442] Re: alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large: -4496252 bytes (-25488 ms).

2015-03-08 Thread Boomer

Looks like it pretty old but also affects me.
Some details:
Lenovo G50-45 laptop.
3.13.0-46-generic #77-Ubuntu SMP Mon Mar 2 18:23:39 UTC 2015 x86_64 x86_64 
x86_64 GNU/Linux
Sound delayed and some echo played when I changes sound volume. Only reboot 
helps to fix it but only for some time.
Usually sound breaks when I change volume level using Fn keys.

Let me know if you need additional details to investigate.

Thanks.

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

Title:
  alsa-util.c: snd_pcm_delay() returned a value that is exceptionally
  large: -4496252 bytes (-25488 ms).

Status in The Linux Kernel:
  New
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Audio hanged while using espeak TTS to read a large chuck of text.
  While playing other parallel audio notifications.  The quality of
  audio is proper with lot of static and abberrations


  E: alsa-util.c:   avail_min: 352
  E: alsa-util.c:   period_event : 1
  E: alsa-util.c:   start_threshold  : -1
  E: alsa-util.c:   stop_threshold   : 1845493760
  E: alsa-util.c:   silence_threshold: 0
  E: alsa-util.c:   silence_size : 0
  E: alsa-util.c:   boundary : 1845493760
  E: alsa-util.c: Slave: Hardware PCM card 0 'HDA Intel' device 0 subdevice 0
  E: alsa-util.c: Its setup is:
  E: alsa-util.c:   stream   : PLAYBACK
  E: alsa-util.c:   access   : MMAP_INTERLEAVED
  E: alsa-util.c:   format   : S16_LE
  E: alsa-util.c:   subformat: STD
  E: alsa-util.c:   channels : 2
  E: alsa-util.c:   rate : 44100
  E: alsa-util.c:   exact rate   : 44100 (44100/1)
  E: alsa-util.c:   msbits   : 16
  E: alsa-util.c:   buffer_size  : 3520
  E: alsa-util.c:   period_size  : 352
  E: alsa-util.c:   period_time  : 7981
  E: alsa-util.c:   tstamp_mode  : ENABLE
  E: alsa-util.c:   period_step  : 1
  E: alsa-util.c:   avail_min: 352
  E: alsa-util.c:   period_event : 1
  E: alsa-util.c:   start_threshold  : -1
  E: alsa-util.c:   stop_threshold   : 1845493760
  E: alsa-util.c:   silence_threshold: 0
  E: alsa-util.c:   silence_size : 0
  E: alsa-util.c:   boundary : 1845493760
  E: alsa-util.c:   appl_ptr : 18557793
  E: alsa-util.c:   hw_ptr   : 19713488
  E: alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large: 
-4496252 bytes (-25488 ms).
  E: alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. 
Please report this issue to the ALSA developers.
  E: alsa-util.c: snd_pcm_dump():
  E: alsa-util.c: Soft volume PCM
  E: alsa-util.c: Control: PCM Playback Volume
  E: alsa-util.c: min_dB: -51
  E: alsa-util.c: max_dB: 0
  E: alsa-util.c: resolution: 256
  E: alsa-util.c: Its setup is:
  E: alsa-util.c:   stream   : PLAYBACK
  E: alsa-util.c:   access   : MMAP_INTERLEAVED
  E: alsa-util.c:   format   : S16_LE
  E: alsa-util.c:   subformat: STD
  E: alsa-util.c:   channels : 2
  E: alsa-util.c:   rate : 44100
  E: alsa-util.c:   exact rate   : 44100 (44100/1)
  E: alsa-util.c:   msbits   : 16
  E: alsa-util.c:   buffer_size  : 3520
  E: alsa-util.c:   period_size  : 352
  E: alsa-util.c:   period_time  : 7981
  E: alsa-util.c:   tstamp_mode  : ENABLE
  E: alsa-util.c:   period_step  : 1
  E: alsa-util.c:   avail_min: 352
  E: alsa-util.c:   period_event : 1
  E: alsa-util.c:   start_threshold  : -1
  E: alsa-util.c:   stop_threshold   : 1845493760
  E: alsa-util.c:   silence_threshold: 0
  E: alsa-util.c:   silence_size : 0
  E: alsa-util.c:   boundary : 1845493760
  E: alsa-util.c: Slave: Hardware PCM card 0 'HDA Intel' device 0 subdevice 0
  E: alsa-util.c: Its setup is:
  E: alsa-util.c:   stream   : PLAYBACK
  E: alsa-util.c:   access   : MMAP_INTERLEAVED
  E: alsa-util.c:   format   : S16_LE
  E: alsa-util.c:   subformat: STD
  E: alsa-util.c:   channels : 2
  E: alsa-util.c:   rate : 44100
  E: alsa-util.c:   exact rate   : 44100 (44100/1)
  E: alsa-util.c:   msbits   : 16
  E: alsa-util.c:   buffer_size  : 3520
  E: alsa-util.c:   period_size  : 352
  E: alsa-util.c:   period_time  : 7981
  E: alsa-util.c:   tstamp_mode  : ENABLE
  E: alsa-util.c:   period_step  : 1
  E: alsa-util.c:   avail_min: 352
  E: alsa-util.c:   period_event : 1
  E: alsa-util.c:   start_threshold  : -1
  E: alsa-util.c:   stop_threshold   : 1845493760
  E: alsa-util.c:   silence_threshold: 0
  E: alsa-util.c:   silence_size : 0
  E: alsa-util.c:   boundary : 1845493760
  E: alsa-util.c:   appl_ptr : 18589473
  E: alsa-util.c:   hw_ptr   : 19713536
  I: alsa-sink.c: Underrun!

  ProblemType: Bug
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS CO

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

paolo, do you have the "udisks" package installed? If so, see above. If
not, please file a new bug with the output of "sudo udevadm test
/block/mmcblk0rpmb". Thanks!

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

Title:
  Fix udev rules to consider mmc rpmb partitions

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

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

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

  Issues observed:

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

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

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

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

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

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

  Please consider this issues fix in next udev release .

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

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

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

[Touch-packages] [Bug 1429529] Re: Unsolvable LTSEnablementStack Mesa package dependency

2015-03-08 Thread Doug McMahon

And possibly - 
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1428972

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

Title:
  Unsolvable LTSEnablementStack Mesa package dependency

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  [Description]
  On 14.04.2 aptitude/APT determinates non-LTSEnablementStack Mesa packages 
instead of *lts-utopic pendants as dependencies. This leads to unsolvable 
conflicts with the already installed *lts-utopic packages.

  
  [Test Case]
  [a] libgles2-mesa (10.1.3-0ubuntu0.3) instead of libgles2-mesa-lts-utopic 
(10.3.2-0ubuntu1~trusty2)
  $ sudo aptitude install qtbase5-dev
  The following NEW packages will be installed:
libglapi-mesa{a} libgles2-mesa{ab} libgles2-mesa-dev{a} libglu1-mesa-dev{a} 
libqt5concurrent5{a} libqt5opengl5-dev{a} qt5-qmake{a} 
qtbase5-dev qtbase5-dev-tools{a} 
  0 packages upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
  Need to get 4,439 kB of archives. After unpacking 27.9 MB will be used.
  The following packages have unmet dependencies:
   xserver-xorg-lts-utopic : Conflicts: libglapi-mesa (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
 Conflicts: libgles2-mesa (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
   libgles2-mesa : Conflicts: libgles2 which is a virtual package.
   libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is 
to be installed.
   libgles2-mesa-lts-utopic : Conflicts: libgles2 which is a virtual package.
  Conflicts: libgles2-mesa but 10.1.3-0ubuntu0.3 is 
to be installed.

  libglapi-mesa conflicts due to libgles2-mesa having a dependency on
  libglapi-mesa (= 10.1.3-0ubuntu0.3).

  [b] libgl1-mesa-dev (10.1.3-0ubuntu0.3) instead of libgl1-mesa-lts-utopic 
(10.3.2-0ubuntu1~trusty2)
  $ sudo aptitude install freeglut3-dev
  The following NEW packages will be installed:
freeglut3{a} freeglut3-dev libdrm-dev{a} libgl1-mesa-dev{a} 
libgl1-mesa-dri{a} libgl1-mesa-glx{ab} libglapi-mesa{a} libglu1-mesa-dev{a} 
libice-dev{a} libllvm3.4{a} libpthread-stubs0-dev{a} libsm-dev{a} 
libx11-dev{a} libx11-doc{a} libx11-xcb-dev{a} libxau-dev{a} 
libxcb-dri2-0-dev{a} libxcb-dri3-dev{a} libxcb-glx0-dev{a} 
libxcb-present-dev{a} libxcb-randr0-dev{a} libxcb-render0-dev{a} 
libxcb-shape0-dev{a} libxcb-sync-dev{a} libxcb-xfixes0-dev{a} 
libxcb1-dev{a} libxdamage-dev{a} libxdmcp-dev{a} libxext-dev{a} 
libxfixes-dev{a} libxshmfence-dev{a} libxt-dev{a} libxxf86vm-dev{a} 
mesa-common-dev{a} x11proto-core-dev{a} x11proto-damage-dev{a} 
x11proto-dri2-dev{a} x11proto-fixes-dev{a} x11proto-gl-dev{a} 
x11proto-input-dev{a} x11proto-kb-dev{a} x11proto-xext-dev{a} 
x11proto-xf86vidmode-dev{a} xorg-sgml-doctools{a} xtrans-dev{a} 
  0 packages upgraded, 45 newly installed, 0 to remove and 68 not upgraded.
  Need to get 16.6 MB of archives. After unpacking 88.2 MB will be used.
  The following packages have unmet dependencies:
   libgl1-mesa-dri-lts-utopic : Conflicts: libgl1-mesa-dri but 
10.1.3-0ubuntu0.3 is to be installed.
   libgl1-mesa-glx-lts-utopic : Conflicts: libgl1 which is a virtual package.
Conflicts: libgl1-mesa-glx but 
10.1.3-0ubuntu0.3 is to be installed.
   xserver-xorg-lts-utopic : Conflicts: libgl1-mesa-dri (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
 Conflicts: libgl1-mesa-glx (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
 Conflicts: libglapi-mesa (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
   libgl1-mesa-glx : Conflicts: libgl1 which is a virtual package.
   libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is 
to be installed.

  [Workaround]
  [a]
  $ sudo aptitude install qtbase5-dev libgles2-mesa-lts-utopic

  [b]
  $ sudo aptitude install -s freeglut3-dev libgl1-mesa-dev-lts-utopic

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

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

[Touch-packages] [Bug 1429529] Re: Unsolvable LTSEnablementStack Mesa package dependency

2015-03-08 Thread Doug McMahon

To a lesser extent - 
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1424491

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

Title:
  Unsolvable LTSEnablementStack Mesa package dependency

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  [Description]
  On 14.04.2 aptitude/APT determinates non-LTSEnablementStack Mesa packages 
instead of *lts-utopic pendants as dependencies. This leads to unsolvable 
conflicts with the already installed *lts-utopic packages.

  
  [Test Case]
  [a] libgles2-mesa (10.1.3-0ubuntu0.3) instead of libgles2-mesa-lts-utopic 
(10.3.2-0ubuntu1~trusty2)
  $ sudo aptitude install qtbase5-dev
  The following NEW packages will be installed:
libglapi-mesa{a} libgles2-mesa{ab} libgles2-mesa-dev{a} libglu1-mesa-dev{a} 
libqt5concurrent5{a} libqt5opengl5-dev{a} qt5-qmake{a} 
qtbase5-dev qtbase5-dev-tools{a} 
  0 packages upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
  Need to get 4,439 kB of archives. After unpacking 27.9 MB will be used.
  The following packages have unmet dependencies:
   xserver-xorg-lts-utopic : Conflicts: libglapi-mesa (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
 Conflicts: libgles2-mesa (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
   libgles2-mesa : Conflicts: libgles2 which is a virtual package.
   libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is 
to be installed.
   libgles2-mesa-lts-utopic : Conflicts: libgles2 which is a virtual package.
  Conflicts: libgles2-mesa but 10.1.3-0ubuntu0.3 is 
to be installed.

  libglapi-mesa conflicts due to libgles2-mesa having a dependency on
  libglapi-mesa (= 10.1.3-0ubuntu0.3).

  [b] libgl1-mesa-dev (10.1.3-0ubuntu0.3) instead of libgl1-mesa-lts-utopic 
(10.3.2-0ubuntu1~trusty2)
  $ sudo aptitude install freeglut3-dev
  The following NEW packages will be installed:
freeglut3{a} freeglut3-dev libdrm-dev{a} libgl1-mesa-dev{a} 
libgl1-mesa-dri{a} libgl1-mesa-glx{ab} libglapi-mesa{a} libglu1-mesa-dev{a} 
libice-dev{a} libllvm3.4{a} libpthread-stubs0-dev{a} libsm-dev{a} 
libx11-dev{a} libx11-doc{a} libx11-xcb-dev{a} libxau-dev{a} 
libxcb-dri2-0-dev{a} libxcb-dri3-dev{a} libxcb-glx0-dev{a} 
libxcb-present-dev{a} libxcb-randr0-dev{a} libxcb-render0-dev{a} 
libxcb-shape0-dev{a} libxcb-sync-dev{a} libxcb-xfixes0-dev{a} 
libxcb1-dev{a} libxdamage-dev{a} libxdmcp-dev{a} libxext-dev{a} 
libxfixes-dev{a} libxshmfence-dev{a} libxt-dev{a} libxxf86vm-dev{a} 
mesa-common-dev{a} x11proto-core-dev{a} x11proto-damage-dev{a} 
x11proto-dri2-dev{a} x11proto-fixes-dev{a} x11proto-gl-dev{a} 
x11proto-input-dev{a} x11proto-kb-dev{a} x11proto-xext-dev{a} 
x11proto-xf86vidmode-dev{a} xorg-sgml-doctools{a} xtrans-dev{a} 
  0 packages upgraded, 45 newly installed, 0 to remove and 68 not upgraded.
  Need to get 16.6 MB of archives. After unpacking 88.2 MB will be used.
  The following packages have unmet dependencies:
   libgl1-mesa-dri-lts-utopic : Conflicts: libgl1-mesa-dri but 
10.1.3-0ubuntu0.3 is to be installed.
   libgl1-mesa-glx-lts-utopic : Conflicts: libgl1 which is a virtual package.
Conflicts: libgl1-mesa-glx but 
10.1.3-0ubuntu0.3 is to be installed.
   xserver-xorg-lts-utopic : Conflicts: libgl1-mesa-dri (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
 Conflicts: libgl1-mesa-glx (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
 Conflicts: libglapi-mesa (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
   libgl1-mesa-glx : Conflicts: libgl1 which is a virtual package.
   libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is 
to be installed.

  [Workaround]
  [a]
  $ sudo aptitude install qtbase5-dev libgles2-mesa-lts-utopic

  [b]
  $ sudo aptitude install -s freeglut3-dev libgl1-mesa-dev-lts-utopic

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

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

[Touch-packages] [Bug 1427487] Re: Kubuntu Vivid 1 Beta 15.04 login screen

Please:
- Report to .
- Copy the new report URL here.
- Set this bug status back to "confirmed".

Thank you.

** Package changed: xorg (Ubuntu) => kde4libs (Ubuntu)

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

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

** Summary changed:

- Kubuntu Vivid 1 Beta 15.04 login screen
+ Shutdown buttons aren't responsible

** Summary changed:

- Shutdown buttons aren't responsible
+ Shutdown buttons aren't unresponding

** Summary changed:

- Shutdown buttons aren't unresponding
+ Shutdown buttons are unresponding

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

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

** Changed in: hundredpapercuts
   Importance: Undecided => Critical

** Summary changed:

- Shutdown buttons are unresponding
+ Shutdown buttons are unresponsive

** Summary changed:

- Shutdown buttons are unresponsive
+ Shutdown screen is unresponsive

** Changed in: hundredpapercuts
   Status: Confirmed => Incomplete

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

** Tags added: asked-to-upstream

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

Title:
  Shutdown screen is unresponsive

Status in One Hundred Papercuts:
  Incomplete
Status in kdelibs:
  New
Status in kde4libs package in Ubuntu:
  Incomplete

Bug description:
  Hardware Profile - 
  https://gist.github.com/anonymous/2c98a06b53d1729e2907

  When you start up and are at the login menu and you click shutdown, where the 
timer is counting down, you can not click the shutdown button.  It is not 
responsive.
  -- The reboot command, at the login window does the same thing.

  See attachments

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Mar  2 22:24:03 2015
  InstallationDate: Installed on 2015-03-03 (0 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224.1)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1429529] Re: Unsolvable LTSEnablementStack Mesa package dependency

2015-03-08 Thread Doug McMahon

There seems to be quite a number of devel packages that can't be installed or 
installed via normal means.
Maybe can be considered dupes of this bug - 
https://bugs.launchpad.net/ubuntu/+source/freeglut/+bug/1424466
https://bugs.launchpad.net/ubuntu/+source/glew/+bug/1429464
https://bugs.launchpad.net/ubuntu/+source/libsdl2/+bug/1429623
https://bugs.launchpad.net/ubuntu/+source/libsdl1.2/+bug/1429625

likely more could be found...

** Changed in: mesa-lts-utopic (Ubuntu)
   Status: New => Confirmed

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

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

Title:
  Unsolvable LTSEnablementStack Mesa package dependency

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  [Description]
  On 14.04.2 aptitude/APT determinates non-LTSEnablementStack Mesa packages 
instead of *lts-utopic pendants as dependencies. This leads to unsolvable 
conflicts with the already installed *lts-utopic packages.

  
  [Test Case]
  [a] libgles2-mesa (10.1.3-0ubuntu0.3) instead of libgles2-mesa-lts-utopic 
(10.3.2-0ubuntu1~trusty2)
  $ sudo aptitude install qtbase5-dev
  The following NEW packages will be installed:
libglapi-mesa{a} libgles2-mesa{ab} libgles2-mesa-dev{a} libglu1-mesa-dev{a} 
libqt5concurrent5{a} libqt5opengl5-dev{a} qt5-qmake{a} 
qtbase5-dev qtbase5-dev-tools{a} 
  0 packages upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
  Need to get 4,439 kB of archives. After unpacking 27.9 MB will be used.
  The following packages have unmet dependencies:
   xserver-xorg-lts-utopic : Conflicts: libglapi-mesa (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
 Conflicts: libgles2-mesa (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
   libgles2-mesa : Conflicts: libgles2 which is a virtual package.
   libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is 
to be installed.
   libgles2-mesa-lts-utopic : Conflicts: libgles2 which is a virtual package.
  Conflicts: libgles2-mesa but 10.1.3-0ubuntu0.3 is 
to be installed.

  libglapi-mesa conflicts due to libgles2-mesa having a dependency on
  libglapi-mesa (= 10.1.3-0ubuntu0.3).

  [b] libgl1-mesa-dev (10.1.3-0ubuntu0.3) instead of libgl1-mesa-lts-utopic 
(10.3.2-0ubuntu1~trusty2)
  $ sudo aptitude install freeglut3-dev
  The following NEW packages will be installed:
freeglut3{a} freeglut3-dev libdrm-dev{a} libgl1-mesa-dev{a} 
libgl1-mesa-dri{a} libgl1-mesa-glx{ab} libglapi-mesa{a} libglu1-mesa-dev{a} 
libice-dev{a} libllvm3.4{a} libpthread-stubs0-dev{a} libsm-dev{a} 
libx11-dev{a} libx11-doc{a} libx11-xcb-dev{a} libxau-dev{a} 
libxcb-dri2-0-dev{a} libxcb-dri3-dev{a} libxcb-glx0-dev{a} 
libxcb-present-dev{a} libxcb-randr0-dev{a} libxcb-render0-dev{a} 
libxcb-shape0-dev{a} libxcb-sync-dev{a} libxcb-xfixes0-dev{a} 
libxcb1-dev{a} libxdamage-dev{a} libxdmcp-dev{a} libxext-dev{a} 
libxfixes-dev{a} libxshmfence-dev{a} libxt-dev{a} libxxf86vm-dev{a} 
mesa-common-dev{a} x11proto-core-dev{a} x11proto-damage-dev{a} 
x11proto-dri2-dev{a} x11proto-fixes-dev{a} x11proto-gl-dev{a} 
x11proto-input-dev{a} x11proto-kb-dev{a} x11proto-xext-dev{a} 
x11proto-xf86vidmode-dev{a} xorg-sgml-doctools{a} xtrans-dev{a} 
  0 packages upgraded, 45 newly installed, 0 to remove and 68 not upgraded.
  Need to get 16.6 MB of archives. After unpacking 88.2 MB will be used.
  The following packages have unmet dependencies:
   libgl1-mesa-dri-lts-utopic : Conflicts: libgl1-mesa-dri but 
10.1.3-0ubuntu0.3 is to be installed.
   libgl1-mesa-glx-lts-utopic : Conflicts: libgl1 which is a virtual package.
Conflicts: libgl1-mesa-glx but 
10.1.3-0ubuntu0.3 is to be installed.
   xserver-xorg-lts-utopic : Conflicts: libgl1-mesa-dri (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
 Conflicts: libgl1-mesa-glx (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
 Conflicts: libglapi-mesa (>= 0~) but 
10.1.3-0ubuntu0.3 is to be installed.
   libgl1-mesa-glx : Conflicts: libgl1 which is a virtual package.
   libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is 
to be installed.

  [Workaround]
  [a]
  $ sudo aptitude install qtbase5-dev libgles2-mesa-lts-utopic

  [b]
  $ sudo aptitude install -s freeglut3-dev libgl1-mesa-dev-lts-utopic

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

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

[Touch-packages] [Bug 1429627] [NEW] When ibus-pinyin is activated, selecting text in firefox deletes text

2015-03-08 Thread Rongcui Dong

Public bug reported:

I have tested some other GTK programs, only a combination of Firefox and
ibus-pinyin causes this problem. I am on Ubuntu 14.10, and this bug is
always reproducible. I think both ibus and firefox has upgraded for
several times, but the problem persists. Before I upgrade to 14.10, I
did not encounter this problem in 14.04. I upgraded long before using
the update manager.

ibus-pinyin:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
 *** 1.5.0-3ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
100 /var/lib/dpkg/status

ibus:
  Installed: 1.5.8-2ubuntu2
  Candidate: 1.5.8-2ubuntu2
  Version table:
 *** 1.5.8-2ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
100 /var/lib/dpkg/status

firefox:
  Installed: 36.0+build2-0ubuntu0.14.10.4
  Candidate: 36.0+build2-0ubuntu0.14.10.4
  Version table:
 *** 36.0+build2-0ubuntu0.14.10.4 0
500 http://us.archive.ubuntu.com/ubuntu/ utopic-updates/main amd64 
Packages
500 http://us.archive.ubuntu.com/ubuntu/ utopic-security/main amd64 
Packages
100 /var/lib/dpkg/status
 33.0+build2-0ubuntu0.14.10.1 0
500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: ibus 1.5.8-2ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-31.41-lowlatency 3.16.7-ckt5
Uname: Linux 3.16.0-31-lowlatency x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Mar  8 14:07:46 2015
InstallationDate: Installed on 2014-10-28 (130 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: ibus
UpgradeStatus: Upgraded to utopic on 2015-01-30 (37 days ago)

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


** Tags: amd64 apport-bug utopic

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

Title:
  When ibus-pinyin is activated, selecting text in firefox deletes text

Status in ibus package in Ubuntu:
  New

Bug description:
  I have tested some other GTK programs, only a combination of Firefox
  and ibus-pinyin causes this problem. I am on Ubuntu 14.10, and this
  bug is always reproducible. I think both ibus and firefox has upgraded
  for several times, but the problem persists. Before I upgrade to
  14.10, I did not encounter this problem in 14.04. I upgraded long
  before using the update manager.

  ibus-pinyin:
Installed: 1.5.0-3ubuntu1
Candidate: 1.5.0-3ubuntu1
Version table:
   *** 1.5.0-3ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

  ibus:
Installed: 1.5.8-2ubuntu2
Candidate: 1.5.8-2ubuntu2
Version table:
   *** 1.5.8-2ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

  firefox:
Installed: 36.0+build2-0ubuntu0.14.10.4
Candidate: 36.0+build2-0ubuntu0.14.10.4
Version table:
   *** 36.0+build2-0ubuntu0.14.10.4 0
  500 http://us.archive.ubuntu.com/ubuntu/ utopic-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu/ utopic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   33.0+build2-0ubuntu0.14.10.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ibus 1.5.8-2ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-31.41-lowlatency 3.16.7-ckt5
  Uname: Linux 3.16.0-31-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar  8 14:07:46 2015
  InstallationDate: Installed on 2014-10-28 (130 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to utopic on 2015-01-30 (37 days ago)

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

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

[Touch-packages] [Bug 1414516] Re: Ubuntu 14.10 sees logitech k810 bluetooth keyboard battery as a system/laptop battery

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

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

Title:
  Ubuntu 14.10 sees logitech k810 bluetooth keyboard battery as a
  system/laptop battery

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  This is a HP desktop computer using a IOGEAR USB Bluetooth dongle.
  When I enable the logitech k810 keyboard the OS behaves like it's on
  battery power.

  Inside the power management GUI under "Power Settings" the "What to do
  when power is critically low" selection is set to Power Off, and I
  can't select another option.

  Here's the output of "upower -d"

  rob@hp-ubuntu:~$ upower -d
  Device: /org/freedesktop/UPower/devices/battery_hid_00o1fo20o92o1bo18_battery
native-path:  hid-00:1f:20:92:1b:18-battery
model:Logitech K810
power supply: no
updated:  Sun 25 Jan 2015 07:02:46 PM CST (5 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   discharging
  energy:  0 Wh
  energy-empty:0 Wh
  energy-full: 0 Wh
  energy-full-design:  0 Wh
  energy-rate: 0 W
  percentage:  85%
  capacity:100%

  Daemon:
daemon-version:  0.9.23
can-suspend: yes
can-hibernate:   no
on-battery:  no
on-low-battery:  no
lid-is-closed:   no
lid-is-present:  no
is-docked:   no

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upower 0.9.23-2ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan 25 18:57:04 2015
  InstallationDate: Installed on 2015-01-14 (11 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2015-03-08 Thread paolo

On my HP stream 11 with xubuntu 14.04, the 204.5ubuntu20.11 did not solve the 
issue.
(I do not know how to tag it as not working).

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

Title:
  Fix udev rules to consider mmc rpmb partitions

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

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

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

  Issues observed:

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

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

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

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

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

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

  Please consider this issues fix in next udev release .

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

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

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

[Touch-packages] [Bug 1427487] Re: Kubuntu Vivid 1 Beta 15.04 login screen

@ Mustang

When reporting a bug try to guess what the package is, instead of
reporting by default to "xorg".

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

Title:
  Kubuntu Vivid 1 Beta 15.04 login screen

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hardware Profile - 
  https://gist.github.com/anonymous/2c98a06b53d1729e2907

  When you start up and are at the login menu and you click shutdown, where the 
timer is counting down, you can not click the shutdown button.  It is not 
responsive.
  -- The reboot command, at the login window does the same thing.

  See attachments

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Mar  2 22:24:03 2015
  InstallationDate: Installed on 2015-03-03 (0 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224.1)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1214352] Re: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses

@ Norbert

I'm unsuscribing the Ubuntu Bug Control team from this bug.  If you
think there's a good reason for the team to be subscribed, please email
me.

Thanks.

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

Title:
  [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in
  parentheses

Status in LibreOffice Productivity Suite:
  Fix Released
Status in The "G" Library - GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in gvfs package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New

Bug description:
  [Impact]
   * This bug affects Glib-dependent packages, one of them is modern version of 
LibreOffice 4.x from PPA 
(https://launchpad.net/~libreoffice/+archive/ubuntu/ppa).
  * LibreOffice is very important software. Modern versions are more 
functional. Without them Ubuntu is nothing, it is a toy.

  [Test Case]
   1. Place OpenDocument file (for example 'test.odt') on SMB/CIFS server 
(Samba on GNU/Linux, or from Windows). Make this share available for read-write.
   2a.1. Open Nautilus, navigate it to 'smb://server_name/share_name/', wait 
the share to be mounted with GVFS.
   2a.2. Double click on 'test.odt'
   2b. Launch terminal and send 'libreoffice 
smb://server_name/share_name/test.odt' command.
   3. Get error message from LibreOffice:
   "The file 'test.odt' is corrupt and therefore cannot be opened.
   LibreOffice can try to repair the file.

  The corruption could be the result of document manipulation or of
   structural document damage due to data transmission.
   We recommend that you do not trust the content of the repaired document.
   Execution of macros is disabled for this document.

  Should LibreOffice repair the file?

  Yes No"
   4a. If I click 'Yes', the file is opened, but the title of the document
    is "Untitled 1 (repaired document)", not original name.
   4b. If I click 'No', the dialog 'LibreOffice 4.4' is opened with text:
    The file 'test.odt' could not be repaired and therefore cannot be 
opened.
  OK"

  I click 'OK' here, the next window "LibreOffice 4.4.1.2" is opened 
with text:
  "General Error.
  General input/output error.

  OK"

  If I click OK here - no files are opened.

  While step 3 gvfsd-smb process eats CPU then terminates with error.
  This error is caused by bug in Glib (wrong type conversion in macros).

  [Regression Potential]

   * This functionality is essential. Please fix this bug.
  I (and you) can't tell Windows users, that they should not open office files 
from network shares in GNU/Linux.

   * The patch has two lines
  
(https://git.gnome.org/browse/glib/commit/?id=255c65f83c1515a7e3fc4609b36e72acc08a79e4)
  and well-tested at upstream.

   * This bug may cause potential loss of data.

  [Other Info]

   * Corresponding links to LibO bugs are:
     https://bugs.freedesktop.org/show_bug.cgi?id=67527
     https://bugs.documentfoundation.org/show_bug.cgi?id=72337

  [Original description]
  On 12.04 LTS precise GUINT32/64_SWAP_LE_BE macros do not enclose val argument 
in parentheses, causing trouble down the stack in gvfs and LibreOffice (and 
possibly in lots of obscure bugs elsewhere).
  There is a patch available, but as this touches the header, it needs a full 
recompile of rdepends.
  see: https://lists.fedoraproject.org/pipermail/devel/2013-March/180302.html 
ff. for details

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1214352/+subscriptions

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

[Touch-packages] [Bug 1429472] Re: Kubuntu Vivid 1 Beta 15.04 installation: Progress bar is missing german translation

2015-03-08 Thread Hans Joachim Desserud

Thanks for taking your time to report this issue and help making Ubuntu
better.

I believe the string in question is not part of ubiquity (the Ubuntu
installer) itself, but rather a program ubuquity uses when installing
the packages for setting up the installed system. Digging a bit, I was
able to find this string [1] which seems to be the one in question.
However, this seems to have been translated a while back, so I'm not
sure why the original would still be shown.

[1]
https://translations.launchpad.net/ubuntu/vivid/+source/aptdaemon/+pots/aptdaemon/de/196/+translate

** Package changed: xorg (Ubuntu) => aptdaemon (Ubuntu)

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

** Tags added: vivid

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

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

Title:
  Kubuntu Vivid 1 Beta 15.04 installation: Progress bar is missing
  german translation

Status in Ubuntu Translations:
  New
Status in aptdaemon package in Ubuntu:
  Confirmed

Bug description:
  At some point of the installation the progress bar at the bottom of the 
screen is missing german translation.
  Screenshot attached

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

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

[Touch-packages] [Bug 1429470] Re: Kubuntu Vivid 1 Beta 15.04 installation: Partition table altered before user agreed according to german text

2015-03-08 Thread Hans Joachim Desserud

Thanks for taking your time to report this issue and help making Ubuntu
better.

>From what I can find, the string in question seems to be this one [1],
which also originally states "The partition tables of the following
devices are changed:". Though from the context this appears in, I would
guess this is the list of changes which will take place _if_ the user
proceeds.

(Marking confirmed based on your screenshot)


[1] 
https://translations.launchpad.net/ubuntu/utopic/+source/debian-installer/+pots/debian-installer/de/491/+translate

** Package changed: xorg (Ubuntu) => debian-installer (Ubuntu)

** Changed in: debian-installer (Ubuntu)
   Status: New => Confirmed

** Tags added: vivid

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

Title:
  Kubuntu Vivid 1 Beta 15.04 installation: Partition table altered
  before user agreed according to german text

Status in debian-installer package in Ubuntu:
  Confirmed

Bug description:
  At first: I didn't check whether the partition table really was
  altered.

  When the user clicks on "Install now", the installer shows the user what will 
be happen if he agrees to install kubuntu.
  In german it reads in the summary "The partition table of the following 
devices _have been_ altered".

  Is the partition table really altered without the users agreement or is this 
just a translation fault?
  Screenshot attached.

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

-- 
Mailing list: https://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 1427672] Re: System doesn't power off when shutting down

2015-03-08 Thread Iain Lane

On Sun, Mar 08, 2015 at 10:33:40AM -, Martin Pitt wrote:
> Indeed rsyslog will stop too early. You might have better luck with
> actually looking at the journal from the last boot, with
> 
>   sudo journalctl -b -1 > /tmp/journal.txt
> 
> and attaching that.

I think one of my previous attachments is from journalctl --- anyway,
the journal is also stopped too early. I was suggesting modifying one of the
jobs so that {journal,rsyslog} stays up as long as possible.

> 
> > poweroff from a vt (as opposed to a debug shell, so there should have
> been an Active=yes session) worked.
> 
> poweroff not working from a debug shell is worrying. The debug shell
> runs as root, and poweroff is supposed to work fine there. What happens
> exactly?

It *does* work from a debug shell, which means that it does *not*
reproduce this bug there. It also *does* work from a vt, so having an
Active session isn't enough, there's something in the user session
causing this problem.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  System doesn't power off when shutting down

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  1. Open the session indicator (cog in top-right)
  2. Shut Down...
  3. Shut Down
  4. The monitors go blank
  5. The system doesn't power off (waited > 5 minutes)

  Things which do work

   - poweroff -f
   - Changing to a debug shell and shutting down using login1.Manager PowerOff

  I can't use the system-shutdown/ functionality since shutdown doesn't
  get that far. I can't SSH in since network is down. I can't switch VT
  when it's in this state so I'm not able to interact with the system. I
  can't see anything on the monitors since they are turned off.

  Any tips on how to get useful debugging information? I'll attach
  journalctl from the previous boot but the last message is the journal
  shutting down so it's not that useful I don't think. Also syslog.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  3 12:57:33 2015
  InstallationDate: Installed on 2012-10-07 (876 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=980689ca-e7d9-4a99-8230-33b8b6e917cd ro nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw systemd.debug-shell nomdmonddf nomdmonisw
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago)
  dmi.bios.date: 08/17/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1201
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1201:bd08/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 936968] Re: rsyslog-gnutls requires rsyslog=4.2.0-2ubuntu8 which is not latest

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

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

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

Title:
  rsyslog-gnutls requires rsyslog=4.2.0-2ubuntu8 which is not latest

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  Installing rsyslog-gnutls requires rsyslog which is at
  4.2.0-2ubuntu8.1 but rsyslog-gnutls depends on == 4.2.0-2ubuntu8

  20/02/12 13:27:13 david@rim-aus-syd-exm-a1 ~: sudo apt-get install 
rsyslog-gnutls
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
rsyslog-gnutls: Depends: rsyslog (= 4.2.0-2ubuntu8) but 4.2.0-2ubuntu8.1 is 
to be installed
  E: Broken packages

  20/02/12 13:44:57 david@rim-aus-syd-exm-a1 ~: lsb_release -rd
  Description:  Ubuntu 10.04.4 LTS
  Release:  10.04

  20/02/12 13:44:59 david@rim-aus-syd-exm-a1 ~: apt-cache policy rsyslog-gnutls
  rsyslog-gnutls:
Installed: 4.2.0-2ubuntu8
Candidate: 4.2.0-2ubuntu8
Version table:
   *** 4.2.0-2ubuntu8 0
  500 http://au.archive.ubuntu.com/ubuntu/ lucid/universe Packages
  100 /var/lib/dpkg/status

  20/02/12 13:45:16 david@rim-aus-syd-exm-a1 ~: apt-cache policy rsyslog   
  rsyslog:
Installed: 4.2.0-2ubuntu8
Candidate: 4.2.0-2ubuntu8.1
Version table:
   4.2.0-2ubuntu8.1 0
  500 http://au.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
   *** 4.2.0-2ubuntu8 0
  500 http://au.archive.ubuntu.com/ubuntu/ lucid/main Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: rsyslog-gnutls 4.2.0-2ubuntu8
  Uname: Linux 2.6.34.10-xenU x86_64
  Architecture: amd64
  Date: Mon Feb 20 13:41:30 2012
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
  SourcePackage: rsyslog

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

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

[Touch-packages] [Bug 1422521] Re: mmap of ...mir/client-platform/mesa.so DENIED

2015-03-08 Thread Staffan Ulfberg

Thanks -- just to say I can confirm this works now.

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

Title:
  mmap of ...mir/client-platform/mesa.so DENIED

Status in AppArmor Linux application security framework:
  In Progress
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released

Bug description:
  I'm running ubuntu touch vivid-vervet:

  root@ubuntu-phablet:/home/phablet# lsb_release -rd
  Description:Ubuntu Vivid Vervet (development branch)
  Release:15.04

  root@ubuntu-phablet:/home/phablet# system-image-cli  -i
  current build number: 101
  device name: hammerhead
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 1970-01-22 15:43:01
  version version: 101
  version keyring: archive-master
  version device: 20150210
  version custom: 3

  This bug is similar to #658135 but in this case it is the files in
  /usr/lib/arm-linux-gnueabihf/mir/client-platform that cannot be
  loaded.

  root@ubuntu-phablet:/home/phablet# apt-cache policy apparmor
  apparmor:
Installed: 2.8.98-0ubuntu4
Candidate: 2.8.98-0ubuntu4
Version table:
   *** 2.8.98-0ubuntu4 0
  500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages
  100 /var/lib/dpkg/status

  
  Most of my installed apps do not start, giving errors similar to this in 
syslog:

  root@ubuntu-phablet:/home/phablet# grep DENIED /var/log/syslog | tail -1
  Feb 16 23:11:56 ubuntu-phablet kernel: [28314.176317] type=1400 
audit(1424124716.747:217): apparmor="DENIED" operation="file_mmap" 
profile="com.ubuntu.calculator_calculator_1.3.339" 
name="/usr/lib/arm-linux-gnueabihf/mir/client-platform/mesa.so" pid=5864 
comm="qmlscene" requested_mask="m" denied_mask="m" fsuid=32011 ouid=0

  Setting apparmor to complain mode makes the app run, and so does
  adding the following line to /etc/apparmor.d/abstractions/base:

/usr/lib/@{multiarch}/**/*.so* mr,
  (just before the line saying "/usr/lib/@{multiarch}/**/lib*.so* mr,")

  So, mesa.so (and dummy.so and android.so) are not matched because they
  do not contain the file name prefix "lib". (Since the file system is
  read only I copied the files elsewhere and ran apparmor_parser on the
  modified files.)

  I do not know if this is the correct fix, but at least it points to a
  problem. (Maybe the library name should be different, the change made
  to another file, like abstractions/X, or maybe the profile for
  calculator is incorrect -- but if it is then lots of profiles are
  incorrect.)

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

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

[Touch-packages] [Bug 1214352] Re: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses

2015-03-08 Thread Norbert

Dear LocutusOfBorg (costamagnagianfranco)!

I'm on Ubuntu 12.04.5 (Precise Pangolin) LTS, not on 10.04 (Lucid Lynx)
LTS.

I tried to apply patch locally on my 12.04.5, but got into dependency
problems.

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

Title:
  [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in
  parentheses

Status in LibreOffice Productivity Suite:
  Fix Released
Status in The "G" Library - GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in gvfs package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New

Bug description:
  [Impact]
   * This bug affects Glib-dependent packages, one of them is modern version of 
LibreOffice 4.x from PPA 
(https://launchpad.net/~libreoffice/+archive/ubuntu/ppa).
  * LibreOffice is very important software. Modern versions are more 
functional. Without them Ubuntu is nothing, it is a toy.

  [Test Case]
   1. Place OpenDocument file (for example 'test.odt') on SMB/CIFS server 
(Samba on GNU/Linux, or from Windows). Make this share available for read-write.
   2a.1. Open Nautilus, navigate it to 'smb://server_name/share_name/', wait 
the share to be mounted with GVFS.
   2a.2. Double click on 'test.odt'
   2b. Launch terminal and send 'libreoffice 
smb://server_name/share_name/test.odt' command.
   3. Get error message from LibreOffice:
   "The file 'test.odt' is corrupt and therefore cannot be opened.
   LibreOffice can try to repair the file.

  The corruption could be the result of document manipulation or of
   structural document damage due to data transmission.
   We recommend that you do not trust the content of the repaired document.
   Execution of macros is disabled for this document.

  Should LibreOffice repair the file?

  Yes No"
   4a. If I click 'Yes', the file is opened, but the title of the document
    is "Untitled 1 (repaired document)", not original name.
   4b. If I click 'No', the dialog 'LibreOffice 4.4' is opened with text:
    The file 'test.odt' could not be repaired and therefore cannot be 
opened.
  OK"

  I click 'OK' here, the next window "LibreOffice 4.4.1.2" is opened 
with text:
  "General Error.
  General input/output error.

  OK"

  If I click OK here - no files are opened.

  While step 3 gvfsd-smb process eats CPU then terminates with error.
  This error is caused by bug in Glib (wrong type conversion in macros).

  [Regression Potential]

   * This functionality is essential. Please fix this bug.
  I (and you) can't tell Windows users, that they should not open office files 
from network shares in GNU/Linux.

   * The patch has two lines
  
(https://git.gnome.org/browse/glib/commit/?id=255c65f83c1515a7e3fc4609b36e72acc08a79e4)
  and well-tested at upstream.

   * This bug may cause potential loss of data.

  [Other Info]

   * Corresponding links to LibO bugs are:
     https://bugs.freedesktop.org/show_bug.cgi?id=67527
     https://bugs.documentfoundation.org/show_bug.cgi?id=72337

  [Original description]
  On 12.04 LTS precise GUINT32/64_SWAP_LE_BE macros do not enclose val argument 
in parentheses, causing trouble down the stack in gvfs and LibreOffice (and 
possibly in lots of obscure bugs elsewhere).
  There is a patch available, but as this touches the header, it needs a full 
recompile of rdepends.
  see: https://lists.fedoraproject.org/pipermail/devel/2013-March/180302.html 
ff. for details

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1214352/+subscriptions

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

[Touch-packages] [Bug 1214352] Re: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses

2015-03-08 Thread LocutusOfBorg

Hi Norbert, did you try to download glib 2.24.1-0ubuntu2 and try to
apply the patch?

I tried, but the file is completely different, so you need to ask
somebody to rebase the patch if you really want the bug fixed in lucid.

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

Title:
  [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in
  parentheses

Status in LibreOffice Productivity Suite:
  Fix Released
Status in The "G" Library - GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in gvfs package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New

Bug description:
  [Impact]
   * This bug affects Glib-dependent packages, one of them is modern version of 
LibreOffice 4.x from PPA 
(https://launchpad.net/~libreoffice/+archive/ubuntu/ppa).
  * LibreOffice is very important software. Modern versions are more 
functional. Without them Ubuntu is nothing, it is a toy.

  [Test Case]
   1. Place OpenDocument file (for example 'test.odt') on SMB/CIFS server 
(Samba on GNU/Linux, or from Windows). Make this share available for read-write.
   2a.1. Open Nautilus, navigate it to 'smb://server_name/share_name/', wait 
the share to be mounted with GVFS.
   2a.2. Double click on 'test.odt'
   2b. Launch terminal and send 'libreoffice 
smb://server_name/share_name/test.odt' command.
   3. Get error message from LibreOffice:
   "The file 'test.odt' is corrupt and therefore cannot be opened.
   LibreOffice can try to repair the file.

  The corruption could be the result of document manipulation or of
   structural document damage due to data transmission.
   We recommend that you do not trust the content of the repaired document.
   Execution of macros is disabled for this document.

  Should LibreOffice repair the file?

  Yes No"
   4a. If I click 'Yes', the file is opened, but the title of the document
    is "Untitled 1 (repaired document)", not original name.
   4b. If I click 'No', the dialog 'LibreOffice 4.4' is opened with text:
    The file 'test.odt' could not be repaired and therefore cannot be 
opened.
  OK"

  I click 'OK' here, the next window "LibreOffice 4.4.1.2" is opened 
with text:
  "General Error.
  General input/output error.

  OK"

  If I click OK here - no files are opened.

  While step 3 gvfsd-smb process eats CPU then terminates with error.
  This error is caused by bug in Glib (wrong type conversion in macros).

  [Regression Potential]

   * This functionality is essential. Please fix this bug.
  I (and you) can't tell Windows users, that they should not open office files 
from network shares in GNU/Linux.

   * The patch has two lines
  
(https://git.gnome.org/browse/glib/commit/?id=255c65f83c1515a7e3fc4609b36e72acc08a79e4)
  and well-tested at upstream.

   * This bug may cause potential loss of data.

  [Other Info]

   * Corresponding links to LibO bugs are:
     https://bugs.freedesktop.org/show_bug.cgi?id=67527
     https://bugs.documentfoundation.org/show_bug.cgi?id=72337

  [Original description]
  On 12.04 LTS precise GUINT32/64_SWAP_LE_BE macros do not enclose val argument 
in parentheses, causing trouble down the stack in gvfs and LibreOffice (and 
possibly in lots of obscure bugs elsewhere).
  There is a patch available, but as this touches the header, it needs a full 
recompile of rdepends.
  see: https://lists.fedoraproject.org/pipermail/devel/2013-March/180302.html 
ff. for details

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1214352/+subscriptions

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

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

2015-03-08 Thread jerrylamos

Comment #11 found earlier vivid wallpaper works fine.  (as does 14.10, 14.04, 
...)
Nov. 10 vivid .iso fresh install on another partition.
Boots with wallpaper O.K. every time.

Vivid as of mid December updated/installed wallpaper screwed up on every boot.
This is a vivid apt-get update, apt-get dist-upgrade as of early March.
Wallpaper still screwed up on every boot.  
Files > Pictures > Select jpg > set as wallpaper 
has to be done maybe twice and then wallpaper O.K.
Kernel 4-RC2 or 3.19-7 no difference, wallpaper screws up on boot, then set 
wallpaper a couple times to get good wallpaper.

Both the older good vivid and the latest vivid are installed in separate
partitions.

Any way to tell what packages are involved in "set wallpaper" and how to
tell what changed?

Thanks.

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

Title:
  Vivid Wallpaper hashed

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
   After update this week wallpaper hashed.  See attachment.

  Settings Appearance change wallpaper to a different wallpaper O.K.,
  then back to original restores proper image.

  Reboot, wallpaper hashed again.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.15-0ubuntu3
  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 Dec 19 08:43:46 2014
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkCentre M6258 [17aa:3048]
 Subsystem: Lenovo Device [17aa:3048]
  InstallationDate: Installed on 2014-11-25 (23 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141125)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic 
root=UUID=285177a7-5498-4980-a3f2-7e3f655ca886 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5CKT69AUS
  dmi.board.name: LENOVO
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE:
  dmi.product.name: 6234A1U
  dmi.product.version: ThinkCentre M58p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1
  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.916+git20141119-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Dec 19 08:43:04 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.16.2.901-1ubuntu3

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

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

[Touch-packages] [Bug 1429594] [NEW] Sound card in iBook G4 not detected in 14.04

2015-03-08 Thread golisp

Public bug reported:

Hello,
After installing 14.04, sound card PowerMac Snapper (Dev 38) was not detected. 
I had try to use both combination of drivers (snd-powermac or 
snd-aoa-codec-tas), but without success. Previous LTS version 12.04 worked with 
this sound card without any issue.

Thanks for support,
Peter.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-47.78-powerpc-smp 3.13.11-ckt16
Uname: Linux 3.13.0-47-powerpc-smp ppc
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: powerpc
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: LXDE
Date: Sun Mar  8 16:08:15 2015
InstallationDate: Installed on 2015-03-07 (1 days ago)
InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release powerpc 
(20140722.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: Upgraded to trusty on 2015-03-07 (0 days ago)

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


** Tags: apport-bug powerpc trusty

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

Title:
  Sound card in iBook G4 not detected in 14.04

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,
  After installing 14.04, sound card PowerMac Snapper (Dev 38) was not 
detected. I had try to use both combination of drivers (snd-powermac or 
snd-aoa-codec-tas), but without success. Previous LTS version 12.04 worked with 
this sound card without any issue.

  Thanks for support,
  Peter.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-47.78-powerpc-smp 3.13.11-ckt16
  Uname: Linux 3.13.0-47-powerpc-smp ppc
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: LXDE
  Date: Sun Mar  8 16:08:15 2015
  InstallationDate: Installed on 2015-03-07 (1 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release powerpc 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: Upgraded to trusty on 2015-03-07 (0 days ago)

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

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

[Touch-packages] [Bug 1429171] Re: systemd-fsckd[232]: Couldn't connect to plymouth: Connection refused

2015-03-08 Thread dino99

note2: as fschk has not been used since that error, this error has not
then been seen indeed. But i suppose there is an issue connecting to
plymouth in such a case.

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

Title:
  systemd-fsckd[232]: Couldn't connect to plymouth: Connection refused

Status in systemd package in Ubuntu:
  New

Bug description:
  get that error logged many times into journalctl on that vivid booting
  with systemd-sysv

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Fri Mar  6 16:11:58 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Touch-packages] [Bug 1429171] Re: systemd-fsckd[232]: Couldn't connect to plymouth: Connection refused

2015-03-08 Thread dino99

that systemd-fsck have appeared after having upgraded an other vivid 
installation (64 bits) on its own partition, sharing the swap partition but not 
/home.
Booting back on that vivid 32 bits, systemd-fschk was ran and terminated as 
expected, excepted for that plymouth error.

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429171/+attachment/4338045/+files/journal.txt

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

Title:
  systemd-fsckd[232]: Couldn't connect to plymouth: Connection refused

Status in systemd package in Ubuntu:
  New

Bug description:
  get that error logged many times into journalctl on that vivid booting
  with systemd-sysv

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Fri Mar  6 16:11:58 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Touch-packages] [Bug 1414516] Re: Ubuntu 14.10 sees logitech k810 bluetooth keyboard battery as a system/laptop battery

2015-03-08 Thread scruss

Looks related to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/1391555

A fresh reinstall of 14.10 brought this problem back for me; an
effective hard lockout because the system interprets my Magic Mouse
battery as the laptop's one …

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

Title:
  Ubuntu 14.10 sees logitech k810 bluetooth keyboard battery as a
  system/laptop battery

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  This is a HP desktop computer using a IOGEAR USB Bluetooth dongle.
  When I enable the logitech k810 keyboard the OS behaves like it's on
  battery power.

  Inside the power management GUI under "Power Settings" the "What to do
  when power is critically low" selection is set to Power Off, and I
  can't select another option.

  Here's the output of "upower -d"

  rob@hp-ubuntu:~$ upower -d
  Device: /org/freedesktop/UPower/devices/battery_hid_00o1fo20o92o1bo18_battery
native-path:  hid-00:1f:20:92:1b:18-battery
model:Logitech K810
power supply: no
updated:  Sun 25 Jan 2015 07:02:46 PM CST (5 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   discharging
  energy:  0 Wh
  energy-empty:0 Wh
  energy-full: 0 Wh
  energy-full-design:  0 Wh
  energy-rate: 0 W
  percentage:  85%
  capacity:100%

  Daemon:
daemon-version:  0.9.23
can-suspend: yes
can-hibernate:   no
on-battery:  no
on-low-battery:  no
lid-is-closed:   no
lid-is-present:  no
is-docked:   no

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upower 0.9.23-2ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan 25 18:57:04 2015
  InstallationDate: Installed on 2015-01-14 (11 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1414516] Re: Ubuntu 14.10 sees logitech k810 bluetooth keyboard battery as a system/laptop battery

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

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

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

Title:
  Ubuntu 14.10 sees logitech k810 bluetooth keyboard battery as a
  system/laptop battery

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  This is a HP desktop computer using a IOGEAR USB Bluetooth dongle.
  When I enable the logitech k810 keyboard the OS behaves like it's on
  battery power.

  Inside the power management GUI under "Power Settings" the "What to do
  when power is critically low" selection is set to Power Off, and I
  can't select another option.

  Here's the output of "upower -d"

  rob@hp-ubuntu:~$ upower -d
  Device: /org/freedesktop/UPower/devices/battery_hid_00o1fo20o92o1bo18_battery
native-path:  hid-00:1f:20:92:1b:18-battery
model:Logitech K810
power supply: no
updated:  Sun 25 Jan 2015 07:02:46 PM CST (5 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   discharging
  energy:  0 Wh
  energy-empty:0 Wh
  energy-full: 0 Wh
  energy-full-design:  0 Wh
  energy-rate: 0 W
  percentage:  85%
  capacity:100%

  Daemon:
daemon-version:  0.9.23
can-suspend: yes
can-hibernate:   no
on-battery:  no
on-low-battery:  no
lid-is-closed:   no
lid-is-present:  no
is-docked:   no

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upower 0.9.23-2ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan 25 18:57:04 2015
  InstallationDate: Installed on 2015-01-14 (11 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1366406] Re: Virtualbox capture error webm(vp8)

2015-03-08 Thread bob

Ooops: I've installed Virtualbox 4.3.24 under my ubuntu 14.04 system:
IDEM! My WEBM video is "Green".

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

Title:
  Virtualbox capture error webm(vp8)

Status in libvpx package in Ubuntu:
  Confirmed

Bug description:
  virtualbox libvpx used to capture video in webm format, in ubuntu the file 
created is corrupt using the relevant library.
  Ubuntu 14.04.1
  Virtualbox Version: 4.3.14 r95030

  Forum virtualbox
  https://forums.virtualbox.org/viewtopic.php?f=7&t=63487.

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

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

[Touch-packages] [Bug 1366406] Re: Virtualbox capture error webm(vp8)

2015-03-08 Thread bob

I've installed Virtualbox 4.3.22 under my ubuntu 14.04 system: IDEM! My
WEBM video is "Green".

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

Title:
  Virtualbox capture error webm(vp8)

Status in libvpx package in Ubuntu:
  Confirmed

Bug description:
  virtualbox libvpx used to capture video in webm format, in ubuntu the file 
created is corrupt using the relevant library.
  Ubuntu 14.04.1
  Virtualbox Version: 4.3.14 r95030

  Forum virtualbox
  https://forums.virtualbox.org/viewtopic.php?f=7&t=63487.

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

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

[Touch-packages] [Bug 704123] Re: Network Manager asks for the PIN even if it is memorized

2015-03-08 Thread Felix

Also affected by the bug. It's annoying, especially since I'm using the
GSM modem only from time to time.

lsusb
Bus 003 Device 015: ID 0bdb:193e Ericsson Business Mobile Networks BV

I'm on Ubuntu 14.04

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

Title:
  Network Manager asks for the PIN even if it is memorized

Status in One Hundred Papercuts:
  Triaged
Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager package in Debian:
  New

Bug description:
  
  HOW TO REPRODUCE
  

  1. Plug the USB modem into a port.

  2. When you are asked to enter the modem's PIN, do along with the
  "automatically unlock this device" option.

  3. Unplug the modem, and plug it again.

  **
  EXPECTED BEHAVIOUR
  **

  - The modem to be automatically unlocked.

  **
  REAL BEHAVIOUR
  **

  - You are asked to enter the PIN again.

  
  WORK-AROUNDS
  

  - Changing the SIM's PIN to empty.

  - Renaming the "/usr/share/nm-applet/gsm-unlock.ui" file.

  
  
  RELEVANT DETAILS
  

  - The same behaviour when configuring the PIN from the "Network
  Connections" menu.

  - Even if the PIN is stored in "/etc/NetworkManager/system-
  connections/", Network Manager cannot retrieve it.

  - The bug makes the device to become locked as soon as network
  connectivity is lost for a while.

  - This bug forces administrators to tell the PIN to other users, while
  they will rather want to keep it in secret and just allow themselves
  to be able to configure the connectivity in specific devices.

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

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

[Touch-packages] [Bug 1429143] Re: Slow shutdown after booting with systemd

2015-03-08 Thread Colin Law

Yes, I understand that.  Still analysing, but I think it is probably an
error in my custom init.d script.  Haven't done much with init.d so not
sure what is going on yet.  Will confirm what it was when I find out.

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

Title:
  Slow shutdown after booting with systemd

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When running vivid booted with systemd kernel, shutdown consistently
  takes around 90 seconds.  With the normal kernel it is about 15
  seconds.

  In the log, shutdown started (from the cog) at 13:50:20, Mar 6th.  The
  purple Ubuntu screen with dots appears after a few seconds and then
  sits there.  It actually powered off at 13:51:55.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-7-generic 3.19.0-7.7
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  colinl 1948 F pulseaudio
   /dev/snd/controlC1:  colinl 1948 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Mar  6 13:54:29 2015
  InstallationDate: Installed on 2014-10-21 (135 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro quiet splash vt.handoff=7 
init=/lib/systemd/systemd
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (8 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1429475] Re: Kubuntu Vivid 1 Beta 15.04 installation: Slideshow is missing german translation

2015-03-08 Thread Hans Joachim Desserud

Thanks for taking your time to report this issue and help making Ubuntu
better.

This looks a bit odd, because the string itself seems to have been
translated long ago
(https://translations.launchpad.net/ubuntu/vivid/+source/ubiquity-
slideshow-ubuntu/+pots/ubiquity-slideshow-
kubuntu/de/+translate?batch=10&show=all&search=designed+to+be+easy)

I took a quick look at some of the other translation bugs you've filed
recently, and while I don't think they belong to the xorg package, I
don't know where to move them either.

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

** Package changed: xorg (Ubuntu) => ubiquity-slideshow-ubuntu (Ubuntu)

** Tags added: vivid

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

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

Title:
  Kubuntu Vivid 1 Beta 15.04 installation: Slideshow is missing german
  translation

Status in Ubuntu Translations:
  New
Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  During copying and installing the users sees a slideshow which is missing 
german translation.
  Screenshot attached.

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

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

[Touch-packages] [Bug 1429571] Re: package linux-image-3.16.0-32-generic 3.16.0-32.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-3.16.0-32-generic 3.16.0-32.42 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  i notice that when i use chrome to much , my laptop need to restart
  and if I don't do it , the Ubuntu force my laptop to .

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-32-generic 3.16.0-32.42
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ahmadalkaid   2998 F pulseaudio
   /dev/snd/controlC0:  ahmadalkaid   2998 F pulseaudio
  Date: Sun Mar  8 02:35:16 2015
  DuplicateSignature: 
package:linux-image-3.16.0-32-generic:3.16.0-32.42:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=696dd809-7429-49b0-97e0-88e45dc9318a
  InstallationDate: Installed on 2014-11-09 (119 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Sony Corporation VPCF111FX
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=9d4dfa20-1332-46fe-b809-81d7d4372b07 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-15
  SourcePackage: initramfs-tools
  Title: package linux-image-3.16.0-32-generic 3.16.0-32.42 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0280Y6
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0280Y6:bd05/14/2010:svnSonyCorporation:pnVPCF111FX:pvrC603MAKW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCF111FX
  dmi.product.version: C603MAKW
  dmi.sys.vendor: Sony Corporation

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

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

[Touch-packages] [Bug 1429571] [NEW] package linux-image-3.16.0-32-generic 3.16.0-32.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2015-03-08 Thread ahmadalkaid

Public bug reported:

i notice that when i use chrome to much , my laptop need to restart and
if I don't do it , the Ubuntu force my laptop to .

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-32-generic 3.16.0-32.42
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ahmadalkaid   2998 F pulseaudio
 /dev/snd/controlC0:  ahmadalkaid   2998 F pulseaudio
Date: Sun Mar  8 02:35:16 2015
DuplicateSignature: 
package:linux-image-3.16.0-32-generic:3.16.0-32.42:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=696dd809-7429-49b0-97e0-88e45dc9318a
InstallationDate: Installed on 2014-11-09 (119 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Sony Corporation VPCF111FX
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=9d4dfa20-1332-46fe-b809-81d7d4372b07 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-15
SourcePackage: initramfs-tools
Title: package linux-image-3.16.0-32-generic 3.16.0-32.42 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/14/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R0280Y6
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0280Y6:bd05/14/2010:svnSonyCorporation:pnVPCF111FX:pvrC603MAKW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VPCF111FX
dmi.product.version: C603MAKW
dmi.sys.vendor: Sony Corporation

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package linux-image-3.16.0-32-generic 3.16.0-32.42 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  i notice that when i use chrome to much , my laptop need to restart
  and if I don't do it , the Ubuntu force my laptop to .

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-32-generic 3.16.0-32.42
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ahmadalkaid   2998 F pulseaudio
   /dev/snd/controlC0:  ahmadalkaid   2998 F pulseaudio
  Date: Sun Mar  8 02:35:16 2015
  DuplicateSignature: 
package:linux-image-3.16.0-32-generic:3.16.0-32.42:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=696dd809-7429-49b0-97e0-88e45dc9318a
  InstallationDate: Installed on 2014-11-09 (119 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Sony Corporation VPCF111FX
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=9d4dfa20-1332-46fe-b809-81d7d4372b07 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-15
  SourcePackage: initramfs-tools
  Title: package linux-image-3.16.0-32-generic 3.16.0-32.42 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0280Y6
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0280Y6:bd05/14/2010:svnSonyCorporation:pnVPCF111FX:pvrC603MAKW:rvnSonyCorporation:r

[Touch-packages] [Bug 1429569] Re: package linux-image-3.13.0-46-generic 3.13.0-46.77 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 255

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-3.13.0-46-generic 3.13.0-46.77 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 255

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  -

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-46-generic 3.13.0-46.77
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  adilson2019 F pulseaudio
   /dev/snd/controlC0:  adilson2019 F pulseaudio
  Date: Sat Mar  7 08:53:28 2015
  DuplicateSignature: 
package:linux-image-3.13.0-46-generic:3.13.0-46.77:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 255
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 255
  HibernationDevice: RESUME=UUID=f63ee586-c464-414c-a272-1c4647f36edc
  InstallationDate: Installed on 2014-11-06 (121 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: ECS A880GM-M6
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic 
root=UUID=de9c63c5-6c2b-4ef0-a4c2-dbf1a5938ccf ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-3.13.0-46-generic 3.13.0-46.77 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 255
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.name: A880GM-M6
  dmi.board.vendor: ECS
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd08/11/2010:svnECS:pnA880GM-M6:pvr1.0:rvnECS:rnA880GM-M6:rvr1.0:cvnECS:ct3:cvr:
  dmi.product.name: A880GM-M6
  dmi.product.version: 1.0
  dmi.sys.vendor: ECS

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

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

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